Pixel Connector Compatibility: Wiring, Adapters and First Tests

A reliable connection matches more than the plug. The lights need the right voltage, the right signal, the right conductor arrangement, and a cable that can carry the intended load. Work through those checks once on the bench, then label the working combination for setup day.

Start with our Pigtail Identification Guide if you need help naming an end. This guide explains what must agree between the devices you are connecting.

Know which connection you are making

Scroll sideways to see all columns.

An RJ45-shaped socket can be used for several different jobs. Read the port label and equipment manual before connecting it to a switch, receiver, or fixture. A pixel extension and an Ethernet cable also belong to different parts of the system.

Check six things from controller to prop

1. Voltage: read the actual strand and supply labels. A connector adapter does not convert 12V into 5V.
2. Signal: confirm that the controller output supports the pixel protocol. The network protocol arriving at the controller and the pixel protocol leaving it are separate settings.
3. Conductors: identify positive, ground, primary data, and any additional signal required by the product. Four wires may serve different functions on different products.
4. Pinout: compare each function at both mating ends, with the connector orientation clearly stated.
5. Direction: route pixel data into the documented input. Follow the strand markings through every connection.
6. Load and distance: check the supply, output, cable, connector, and distribution ratings for the intended installation. A cable's available length is not a guaranteed operating distance for every pixel load.

On a Baldrick8, the manufacturer identifies the pixel terminal positions as G, D, and +. Read the printed labels and manual for your board when landing a pigtail. This terminal order does not tell you the contact positions inside an unrelated molded connector. See the Baldrick8 manual for the board's wiring and network setup.

Adapters: solve the specific mismatch

Our adapter range identifies Ray-to-xConnect, DIY 15 mm-to-xConnect, and LOR 15 mm-to-xConnect options separately. Select the adapter for both ends of your actual equipment. A combined LOR/DIY label on a cap or mechanical part does not establish identical electrical wiring.

Also distinguish a connector-family adapter from the special input arrangement supplied for a pixel design. The standard EVO+ listing specifies a three-wire-to-four-wire xConnect input adapter. Follow the instructions for the supplied strand and keep its required interconnections intact. The fourth EVO+ conductor serves the dual-data design; it should not be treated as a clock wire simply because another four-wire pixel uses a clock.

For Kraken Flex or EVO Lux Dome with Mconnect, use the matching Mconnect connections or an explicitly supported adapter. Do not choose an xConnect part solely because it appears similar in a product photo.

Trace an unknown loose cable with power removed

A continuity check can identify which contact connects to which conductor. It cannot establish the intended voltage, protocol, or current rating. Use the product documentation for those.

1. Completely disconnect the cable or adapter from power supplies, controllers, pixels, and other equipment. Test the isolated cable only.
2. Set up the meter for continuity according to its manual. Touch the probes together to check that the meter responds.
3. Place one probe on a contact and find the matching conductor or contact at the other end. Record the result with a sketch and the viewing direction.
4. Check every conductor and check for unexpected connections between different conductors. A power tee may intentionally join or isolate wires; compare it with that tee's documented design.
5. Label the verified mapping. If it does not match the intended circuit, resolve the mismatch before connecting equipment.

Continuity mode is for a de-energized, isolated part. Follow your meter's instructions; Fluke's continuity guide explains the basic method. Do not push oversized probes into sockets and damage their contacts.

Prove one complete connection

With wiring complete and power still disconnected, inspect the pins, seals, keys, strain relief, and bare-wire terminals. Confirm the supply setting and circuit protection using the equipment instructions. Start with a short, known-good compatible strand and a known-good cable.

Run separate red, green, and blue tests, then a chase. Add the intended extension and repeat. Finally test the completed section under the highest load you plan to use. If it passes with the short cable but fails with the installed route, compare cable connections, power at the load, and the data path before changing unrelated software settings.

Read the symptom before replacing parts

• Nothing lights: check output selection, power, input direction, connector mapping, and the first pixel.
• Colors are consistently swapped: check color order and channel mapping with a primary-color test.
• Problems appear as brightness increases: investigate the power path and voltage drop.
• Moving the cable changes the fault: inspect and substitute that connection with power removed between changes.

Record the working controller port, pixel count, connector family, extension length, and brightness setting. Send those details with a short test video to Support@MattosDesigns.com if you need help.

See the whole route: Baldrick8 and 100 EVO pixels

This example uses the 12V MD1500 Baldrick8 xConnect package, a matching xConnect extension, and the 100-node black-wire xConnect EVO option. Keep the supplied controller assembly intact and make the pixel connections with power removed.

1. Start at the player: for this test, choose either xLights output from the computer or a configured FPP player. The MD1500's Ethernet connection receives show data; it is not a pixel extension connection.
2. Follow output 1: use the numbered physical output and the same port assignment in the controller and xLights. The matching extension ends at the strand input, identified by its data direction.
3. Close the unused end: fit a cap intended for that exact strand output. Cap unused controller outputs with their matching caps too.
4. Prove colors and direction: use a small test at conservative brightness, then a moving-pixel pattern. Check every node, not just the first one.
5. Add distance as its own test: if the direct strand works, test the actual extension. Record the length and brightness that passed. A longer cable changes the power and data conditions.

If your project needs power injection

Complete the power-distribution plan before adding a feed. Record the exact supply, branch protection, conductor sizes, connector ratings and any separation between power supplies. The drawing above is a controller-fed bench connection; it is not an injection diagram. For a project-specific drawing, use our wiring-diagram service.

Continue with Baldrick setup · Review the matching project parts · Compare connector photos

Keep building

• Identify your pigtail and output cap
• xConnect and M-Connect: match the selected variant
• Mattos power and wiring reference
• Choose a pixel extension
• Full setup and troubleshooting guides