Unsolved DotStar behavior changed with 3.2
JT last edited by
just updated my machine to 3.2, running on a Duet 3 MB6HC.
With the last release i turned on my LEDs via the short following command:
M150 X0 M150 R255 U255 B255 S120 F0 Y31
With 3.2 this won´t work anymore. By try and error i found out that when i change the command to X1 i can turn on the LEDs again.
But to turn them off i have to stay with X0. So something strange happens here. Anyone faced the same behavior?
Luke'sLaboratory last edited by
Per the release notes, the default behavior for LED's is to expect that they are Neopixel, not Dotstar.
@JT I have added this to my list to test/investigate. The Neopixel/DotStar driver was changed in 3.2 and unfortunately I did not have a working DotStar strip to test with.
I confirm that the DotStar driver was not working. I have now fixed it. The fix will be in the 3.3beta3 release. A preview 3.2beta2+ build including the fix is available at https://www.dropbox.com/sh/dupd9u1xppr1om5/AADYg4guuj2n8LJokVqtK-C7a?dl=0.