This is a great video and I wish it was here last year when I was fighting a flicker on my tree. I have been discovering the importance of the grounding rather than just adding more positive voltage injection points, so this video re-enforces a theory I was developing. Great Video! And, I sent you a message about your (assuming yours) injection web tool on xLights forum. Another great tool! Please keep adding more tips as I have subscribed to see what else you have to offer :)
Another way to explain your Grounding fix is that there was actually a voltage (floating upwards) on the ground line. That makes the voltage difference between the Data line (5v nominal) and ground becomes too small as the ground line's voltage rises (and you get flicker). About the only way to show that would be with a long Voltmeter probe back to the power source ground (actual Zero volts).
Good informative video!!! Ya gotta try this with 5vdc pixels like I have with variations of cable length between the individual props and (LOR) cards. Most of my cards can only have 175 max unless running a LOR PixiCon card (Just like the Falcon). No matter what, I always add PI (+ and -) every 50 Pixels regardless of if the lights are doing ok or not. I never do PI at the end due to the nature of forward bias versus reverse bias of LEDs. Normally do liquid tape seal on the last pixel so water does not get in. Had that happen on a few of my props. So far everything lights up well and can crank it up to 100% if need to. I run 30% most of the time unless there is a part in the sequence that needs an increase for emphasis. Like to keep my neighbors happy since in a older (most retirees) community. BTW, LOR wants a different setup of PI than XLights and will agree with XLights form of PI over LOR.
I myself am a 5v guy, the principle is the same for them. Post this video I did create the pixel power calculator: spikerlights.com/calcpower.aspx you can use it to estimate the draw based on "virtual" power injection points. In my behinds the scenes this year you will see where I did this on my matrix and mega trees.
I've got three questions (I'm watching on a computer with horrible sound, so that is part of the issue): 1. I think you're saying that the solution is to also run PI at the first string, so I am assuming the first time you were starting at the second? 2. Am I correct that you are just running one PI line, and connecting it at the multiple points? and 3. Let's say you're connecting two small props that wouldn't need PI on their own, but the second one does. Would you still need to connect your PI at the beginning of the first prop, rather than running PI directly to the second?
Your grounding fix .. so you jumped from +/- at pixel 1 to each node 51, 101 etc or 1 to 51 then 51 to 101 etc? Rather +/- on the last node back to 200something etc?
It is jumped from 1-51, then 51-101 etc, the reason I do it from pixel 1 is that is where the data line is coming in and wanted to ensure it had proper ground.
Everyone need to watch this video. Perfectly explained...
This is a great video and I wish it was here last year when I was fighting a flicker on my tree. I have been discovering the importance of the grounding rather than just adding more positive voltage injection points, so this video re-enforces a theory I was developing. Great Video! And, I sent you a message about your (assuming yours) injection web tool on xLights forum. Another great tool! Please keep adding more tips as I have subscribed to see what else you have to offer :)
Another way to explain your Grounding fix is that there was actually a voltage (floating upwards) on the ground line. That makes the voltage difference between the Data line (5v nominal) and ground becomes too small as the ground line's voltage rises (and you get flicker).
About the only way to show that would be with a long Voltmeter probe back to the power source ground (actual Zero volts).
Good informative video!!! Ya gotta try this with 5vdc pixels like I have with variations of cable length between the individual props and (LOR) cards. Most of my cards can only have 175 max unless running a LOR PixiCon card (Just like the Falcon). No matter what, I always add PI (+ and -) every 50 Pixels regardless of if the lights are doing ok or not. I never do PI at the end due to the nature of forward bias versus reverse bias of LEDs. Normally do liquid tape seal on the last pixel so water does not get in. Had that happen on a few of my props. So far everything lights up well and can crank it up to 100% if need to. I run 30% most of the time unless there is a part in the sequence that needs an increase for emphasis. Like to keep my neighbors happy since in a older (most retirees) community. BTW, LOR wants a different setup of PI than XLights and will agree with XLights form of PI over LOR.
I myself am a 5v guy, the principle is the same for them. Post this video I did create the pixel power calculator: spikerlights.com/calcpower.aspx you can use it to estimate the draw based on "virtual" power injection points. In my behinds the scenes this year you will see where I did this on my matrix and mega trees.
They sell injection tees with connectors btw.
LOL .. yes, but back in 2018 those were not as available and people didn't understand what power balancing was.
How many amps are you pulling in the two spinner configuration? By my calculations it should be over 5 amps.
I've got three questions (I'm watching on a computer with horrible sound, so that is part of the issue): 1. I think you're saying that the solution is to also run PI at the first string, so I am assuming the first time you were starting at the second? 2. Am I correct that you are just running one PI line, and connecting it at the multiple points? and 3. Let's say you're connecting two small props that wouldn't need PI on their own, but the second one does. Would you still need to connect your PI at the beginning of the first prop, rather than running PI directly to the second?
Your grounding fix .. so you jumped from +/- at pixel 1 to each node 51, 101 etc or 1 to 51 then 51 to 101 etc? Rather +/- on the last node back to 200something etc?
It is jumped from 1-51, then 51-101 etc, the reason I do it from pixel 1 is that is where the data line is coming in and wanted to ensure it had proper ground.