I have a question on how to correctly only use the data signal output from the controller and use power distribution boards to power the pixel string at the beginning and at any power injection locations.
I found some posts on this saying to just use the Data and V- outputs on the controller board, and to not use the V+ output on the board. I am a little unclear on the use of/need for the V- wire at the board output port.
What is the need for that V- wire? If i run an 18-3 cable from the first pixel (connecting all 3 wires there), and in the controller box hook up the V+ and V- to the distro board for power, can i simply run the Data wire to the data out at the board and everything will work? Everything is on the same power supply. I am trying to compare this to 120v wiring in that every circuit you have a positive & negative (neutral) wire, the neutral wire is the return path/reference point.
If the board output does need the V- wire connected here too, can i simply splice onto the V- wire at the distro board and then connect it to the V- on the board output? Is the V- connection on the board output to simply to make sure the "circuit" has the same V- reference point?
Thanks for the help,
Tim
As long as the controller and the pixels are being powered off the same power supply you should not need to connect the V- output of the controller board.
It's there primarily for convenience and to ensure the controller and pixels have the same ground reference.
The data line "is with reference to" something. In our case that something is the V- line. Every mm of wire changes the reference and the signal. Every mm of difference between the reference and signal increases the potential for the target pixel to misinterpret the signal when it compares the signal to the reference. Hence my general rule: Where goes data, so goes V-. The V- that travels with the data should NOT be handling the real power used to drive the pixels. For example, in my matrix I have a 24AWG wire pair (Data, V-) that goes from the controller to the first pixel. I also have a 16AWG wire pair (V+, V-) going to the first pixel. The Data wire is 4m long and carries almost no current. That means the Data and its reference arrive at the first pixel together. Those two wires also experience environmental conditions together which mean the common mode rejection effect on the input side of the pixels have a chance to ignore that noise (motors starting, TV on/off, garage door opening etc). If the reference wire did not travel with the data signal then that built in noise rejection would not work.Next issue is current through the V- wire going from the controller to the pixel (no matter which path you take). The more current through the reference wire, the more the reference value is skewed. This causes a drop in noise immunity and signal integrity (the reference at the controller is very different than the reference at the first pixel when current flows through the V- wire).FYI: Some people have found that they do not need the controller V-. Their wires are short enough or the electrical environment is clean enough that things seem to work. For the large majority of the rest of us, things do not work that well. For me it is best to have a good design rather than depending on hope.Hope this helps a bit.Martin
Heldwhat Christmas wrote:As long as the controller and the pixels are being powered off the same power supply you should not need to connect the V- output of the controller board.
It's there primarily for convenience and to ensure the controller and pixels have the same ground reference.
I would say I disagree with this in a big way.
If you run power injection into the very first pixel, then no, you don't need to run V- from the port as well. Doesn't hurt, though. But if your first injection point is at pixel 51 (and not pixel 1), there could be some ground drift, so in that case it would be better to connect V-.
Connecting V+ is fine if you're testing; especially if you're only testing 50 pixels. It's just that out in the elements, things can go wrong and cause a short without you being there to know. It's safer for the controller.
