Just finished setting up this years display whoo-hooo. Yes I might be bragging LOL.............
I had a weird thing happen this year. On one of my six arches. After a bunch of troubleshooting I determined that one of my 6 arches was sending weird downstream signals haphazardly.
Each arch worked perfect independently, but; after figuring out which one was the bad arch (which was difficult in itself), the arch that came "DOWNSTREAM" of the bad arch would light up, but after warming up a bit would twinkle the wrong multi colors and not actuate per the music. The bad arch worked fine, only the DOWNSTREAM arch was impacted.
After changing power injection tees, power isolators, mixing and matching all of the six arches, replacing first and last pixels and Connectors on the suspect arch, I FINALLY fixed the problem by replacing ALL of the pixels on the suspect arch.
All works fine NOW.
Does anyone have any idea what might have been goin on. Has this ever happened to you folks? Have any idea on best way I might go about troubleshooting if this ever happens again. I burned WAY too much time troubleshooting and figuring out which arch was causing the problem before I just decided to replace all of he pixels on the arch.
Thanks
Steve
There really is no way to tell without seeing the probkem. Most good troubleshooters learn from YEARS OF EXPERIENCE. There is no substitute for experience. Having said that, connectors and tees are probably the last thing to fail once they have been proven to work. Most often the micro electronics within the pixels fail.
Yes, i'm sure that's what it was. But it was so weird that everything worked fine on the "bad" arch, and only sent a screwy signal downstream. I kept thinking something was wrong with the downstream arch until i started moving the arches around and found out the bad arch was actually the good arch. I never even considered that the arch that worked fine was the problem. That is a super screwy failure mode for the pixels. I was hopin there was some way to isolate a pixel on a string somehow to try to determine which pixel was causing the problem. It obviously was NOT the first or last because I replaced those with no change, but it was one of the pixels on that string. So strange.
