Mattos MD1500 Baldrick8 & Baldrick17: First-Start Guide
Your first goal is one predictable result: the controller opens in a browser and one matching pixel strand responds to a local test. Once that works, you have a reliable starting point for xLights, more props and outdoor setup.
Reviewed October 29, 2026. This guide covers the Mattos MD1500 Baldrick8 and Baldrick17 ready-to-run packages. A bare board needs a completed, checked enclosure build first. A Cosmic Pro-Series package has different enclosure connections; use its own product details.
1. Match the controller, strand and cable
Check the order and the labels on the delivered equipment. The MD1500 packages covered here contain installed 12V supplies. A board's broader DC input specification does not change the voltage of that finished controller.
Scroll sideways to see all columns.
| Check | What you want to establish |
|---|---|
| Controller | Baldrick8 or Baldrick17, MD1500 enclosure, and the selected xConnect or Mconnect output option. |
| Pixels | Correct voltage, supported pixel protocol, actual node count and clearly identified data input. |
| Cable | A matching connector family, verified wiring and a short route for the first test. |
| Network | An Ethernet cable to a working router, or to a network switch connected to that router. |
For a simple Mattos bench example, use one 12V three-wire EVO strand with the same connector option as the controller. An EVO+ four-wire strand has a different connection arrangement; establish that arrangement separately. Use our connector identification and compatibility guide if the ends are uncertain.
2. Identify the external connections
Find the AC cord, numbered pixel output leads and Ethernet bulkhead. The current MD1500 listings specify one external Ethernet connection. The Baldrick17 board inside has two Ethernet sockets, and some Baldrick8 revisions do too; that does not mean the MD1500 enclosure exposes both.

The controller arrives assembled. You should be able to make this first test through its installed external connections. Disconnect power before changing pixel connections. Do not open power-supply terminal covers or alter the internal wiring to follow this guide.
Set the enclosure in its intended upright orientation. For installation, the MD1500 requires vertical mounting with the output cables leaving downward. Keep the first test accessible so you can read labels and follow the complete cable route.
3. Reach the controller before starting xLights
- With power disconnected, connect the matching strand's input to the lead labeled 1. Leave the other outputs unused and protected with their correct caps.
- Connect the Ethernet bulkhead to your router or its switch. Put the setup computer on the same local network; a guest network can isolate it from the controller.
- Power the assembled controller from its intended AC supply. Allow it to start.
- Use Baldrick Buddy or the router's connected-device list to find its address. With only one Baldrick present,
http://baldrickboard.localmay also work. If that name fails, use the actual IP address. - Open the board's page. Record its identity, IP address and firmware version. Confirm you opened the board you just connected.
Expected result: you can reopen that board's page and identify it again. The Baldrick8/17 connection is wired Ethernet; a phone or laptop can reach it over the same LAN's Wi-Fi, but that does not give the controller its own Wi-Fi link.
If the first-firmware installation screen appears, follow its Lets Go prompt while the board has internet access and allow the installation to finish. A tested ready-to-run package may already have firmware installed. Do not factory-reset a working unit just to make it look like an online tutorial.
4. Prove the strand with the controller's test
Stop any show player that is sending to this board. Open Test Mode, choose only the connected port and begin at a low brightness appropriate for the strand and supply. A modest test brightness is a starting condition, not proof that a larger load is suitable.

Use separate red, green and blue tests, followed by a moving pattern. The test scope matters: the interface can target a limited pixel count or configured models. If you select a 50-pixel test on a 100-pixel strand, an unlit second half is expected. Configure the actual strand count before using an all-configured-pixels test.
Check the first node, the last node in the chosen test range and the direction of travel. If a requested red appears green, record that result for the color-order check. If the response is random or unstable, work through Baldrick troubleshooting before adding another strand.
5. Save the result and move to xLights
Write down the strand name, connector, count, tested output and successful settings. Label both ends of any extension. Turn the controller's test mode off when you finish; it must be off for the next stage of testing from a show player.
This local test proves a small hardware path. It does not yet verify xLights channel assignments or the final display's power demand. Continue with Baldrick and xLights setup, then expand one tested section at a time.
Need a matching package? Choose the actual connector: Baldrick8 xConnect, Baldrick8 Mconnect, Baldrick17 xConnect or Baldrick17 Mconnect.
Sources and next steps
- Baldrick8 manual
- Baldrick17 manual
- Baldrick network troubleshooting
- Baldrick Buddy
- Mattos MD1500 Baldrick8 package
- Mattos MD1500 Baldrick17 package
Explore the Mattos Baldrick Learning Center · All Mattos guides
