NeoPixel Duet 3 support - two questions

dc42

I already increased it to 60 so that you can have a complete ring (4 quadrants of 15).
Yes it would be possible to support those. RGBW DotStar LEDs are already supported.

Please note, the maximum current draw is 60mA per LED for the RGB version, and 80mA per LED for the RGBW version. So if you use the full 60 LEDs, you should provide a PSU that can supply 3.6A for the RGB version, or 4.8A for the RGBW version.

oozeBot

@dc42 60 was my magic number.. thanks! I understand the need for powering them externally. Was this part of the latest release? Or is it upcoming? And would be an enhancement to add support for the RGBW? Or am I misunderstanding how that works?

One last thing- does dotstar have the same number of addressable LEDs?

dc42

@oozeBot said in NeoPixel Duet 3 support - two questions:

@dc42 60 was my magic number.. thanks! I understand the need for powering them externally. Was this part of the latest release? Or is it upcoming?

I changed it quite some time ago, but later than the 3.1.1 release AFAIR.

And would be an enhancement to add support for the RGBW? Or am I misunderstanding how that works?

Yes it would need additional code and an additional value for the mode parameter.

One last thing- does dotstar have the same number of addressable LEDs?

With DotStar there should be almost no limit, because RRF doesn't need to buffer up all the data in one go.

oozeBot

@dc42 said in NeoPixel Duet 3 support - two questions:

With DotStar there should be almost no limit, because RRF doesn't need to buffer up all the data in one go.

Thanks again - I'm thinking making the jump to DotStar is the way to go..!

oozeBot

@dc42 - I picked up a roll of DotStar LEDs and am only having partial success. I can't find the documentation on how to properly set them up. What should Q be in M150 X0 Q??

I can get random results by setting various values, but nothing is accurate..

Thanks

dc42

The value of the Q parameter should not matter for DotStar LEDs, except that too high a value will not work if the wires are very long. I've updated the documentation to make it clear that the Q parameter is optional and not normally required.

Make sure that you have the clock and data wires the right way round. If they are the wrong way round, you will get strange results, but no damage will be done.

oozeBot

@dc42 no luck so far, but this is not an urgent request of any sort and very likely just my ignorance showing through with Dotstar. The data and clock wires are in the correct order.

However, I do see two variants: SK9822 and APA102. I see the strand I bought is APA102, but I don't really know too much more about this yet. Is Duet's implementation
APA102 compatible"?

One note: I can get the strand to at least respond by setting Q between 26000000-37000000. Outside of that, or not setting Q at all, the strand does not respond at all.

MikeS

@dc42 so only an idea: why not add the ability to command already running leds (for example look at WLED) that are running on an esp module? D1 Mini is really cheap and cand drive a lots of WS2812 (mine is running 4mt on my desk where the printer is placed). It is connected with wifi and is opensource, in fact i'm controlling it right now via HomeAssistant that has an integration for it. That would be cool and keep cycle time / memory free for duet.

jaygrovr

@dc42 where is the documentation for this? I am actually trying to connect dotstars to the PI board that is running DWC. WHen I try to send a M150 I get an error "M150 does not support X and Q parameters in this mode. Refer to the DHC config instead.

dc42

https://duet3d.dozuki.com/Wiki/Neopixel_and_DotStar_LEDs