Neopixel issue D3+rpi 3.2b1

[oozeBot]

We are using Duet3/RPI and currently running 3.2b1. I have the following in my config:

M150 X1 F3000000
M150 R0 U85 B255 P64 S57
M150 R0 U85 B255 P64 S57

Note the two lines with the same command - if I send it once (in the config or through the console), it never works the first time, I have to send it a second to get them to start working.

This feels wrong, but again, it could be I don't know what I'm doing. Thanks

[dc42]

If you insert a short G4 delay command between the M150 X1 command and the second M150 command, does it work without the third M150 command?

[oozeBot]

@dc42 No - that doesn't correct it. I just tried several times up to 1 second but it still does not enable unless I run a second command.

[dc42]

Thanks, I'll look into this.

[dc42]

The F3000000 in your M150 command parameter is wrong. If you want to set the frequency to 3MHz, it should be Q3000000.

I am working to try to fix this, however I am finding that my Neopixels don't respond correctly to the first command they see.

[oozeBot]

@dc42 hmm - not sure where I got the "F' from.. I just just updated my config to the following and it worked. I started a print but can try after it is complete to see if it still works after removing the G4..

M150 X1 Q3000000		; sets LED type to NeoPixel and SPI frequency to 3MHz
G4 P1000
M150 R0 U85 B255 P64 S57

[dc42]

I spent quite a while investigating this today. As it happens, a change in the firmware earlier this week caused an almost identical symptom on Duet 3 MB6HC, even with the F parameter corrected to Q! Without your report I would not have tested it. Anyway, it's fixed now.