Phrog30 wrote:Power injection doesn't help this issue, I've tried with and without. This really looks like a data issue.I'm running power from the controller.
When I tried power injection I did it at the end and between the two windows.
If you have a couple spare pixels, you may want to try a single pixel every 5’ of distance between elements. These pixels act as repeaters, but you will need to account for them in sequencing. I.e. If you use 2 pixels, your 70 is now 72. If this fixes your issue, you'll know what you are dealing with
You might want to try a couple of null pixels in your 40' lead and maybe a null pixel or 2 between your windows (or the Uamps Travis has suggested - first time I've heard of them). I'm guessing either should do the trick. I only have shorter runs off my Pixlite 4 but had some much longer runs off my e6804's and didn't experience issues, apart from the issue with crossing data I mentioned earlier. I use HLS as my sequencer, so adding null pixels is very easy. I'm not sure how other sequencers handle adding null pixels. I can't remember if you can add null in the middle of the string with Pixlite 4 or not.
I had a very similar issue. Take a look at this video...does this look like what you're seeing?
I am using 10' extensions for my pixels and found the problem in the resistance I was using on my E682. On the advise of another member I put in another resistor in series with the data signal on the controller side and it completely went away. No other changes.
The flickering happened when I powered up the controller and after I had run a sequence.
OregonLights wrote:I had a very similar issue. Take a look at this video...does this look like what you're seeing?
I am using 10' extensions for my pixels and found the problem in the resistance I was using on my E682. On the advise of another member I put in another resistor in series with the data signal on the controller side and it completely went away. No other changes.The flickering happened when I powered up the controller and after I had run a sequence.
/div>
Did you do this on the controller itself? Not sure I'd be comfortable modifying the controller.
Travis
Sent from my iPhone using Tapatalk
uzelessknowledge wrote:Sounds like the issue I had. It came down to a data issue and having too much wire between elements. I was able to get it down to about 6-7' and the problem went away.
On Facebook in the Introduction to RGB on July 25 there is a post about it.
I contacted Advatek for help and we were able to narrow down that it was too much distance from one set of lights to the next.
I went in on the group by and have some uAmps on the way.Travis
Sent from my iPhone using Tapatalk
We probably had the same issue. If I shorten the cable between elements to 5 feet, no problem. However, I can't go this short because my windows are about 10 ft apart.
I'm going to try null pixels first.
Thanks for all of the help.
James
