Yep, did that just in case I had a bad output from the Pico or HCTs. Always stayed with the cable wire in question.You could also try swapping channels 4,5,12,13 (that you said were faulty) with working channels, and see if the fault moves with the LED string, or stays with the I/O pin.
I'm not sure if I changed which strip cable lines 4,5,12,13 went to, but then when I connected a dedicated 300 pixel strip directly to the transmission cable, problem appeared on those 4, not so much if at all on the other 12.
Again, if my current transmission cable behaves the same with the production display and 40A power supply, I'm going to move on in trying CAT5.
What I also want to do is program the Pico to continually display red and blue as quicky as it can, scope channel 4 and a more stable channel, then have the scope show a 3rd view of a difference between the two channels. That way if normally the scope shows nearly nothing from the difference, then I can trigger when a scoped row acts up.
There's already that bouncing between red/blue in the code to test FPS.
As it is now, I'm probably seeing mostly behaved signaling and missing out on the moments it acts up. It acts up only about 1/2 to 2 seconds at a time, and depends on what is being displayed.
Statistics: Posted by DanMan32 — Sun Feb 04, 2024 1:20 am