Replies: 1 comment
-
I come from the future. I fixed a bug in the LED counting code just a few days ago that would have almost explained this. The overcount doesn't quite match, but I didn't roll the code back to 2011 to compare. I think the trunk as of 8/2023 has this fixed. No reason to spend our time budget wiggling wires that are just going to be shifted right off the end of the wire, right? Your analyzer is very cool. I haven't seen one that decoded WS281x. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have given the demo env a go. The good news is that it more or less worked out of the box on Win10 x64 on a Ryzen processor. I connected a logic analyzer with WS2812b decoder and it says that even though I told it to do 14 LEDs it counts up the index to 2B. Is this intentional? The initialization says 14 LEDs

but the logic analyzer says... no mate it is addressing to 2B. This does not cause issues on a single strip but I would imagine break matrix arrangements... or I am missing something...
(Noteworthy to mention it takes clicking build twice by the time the project successfully builds for some reason for me anyway. Clean + Build 1 fails on a missing file + Build 2 succeeds.)
Beta Was this translation helpful? Give feedback.
All reactions