Dotstar questions?

siblues

I love that HUD you made that was a very cool idea.I will have the Dotstars handy for my next project.I must have almost 40 feet of leds here for my multirotors and other projects and I have tons of Teensy's and Nano's laying around so I am sure I will use them eventually.I guess I will pick up a set of 5v dumb led's for the simple on off set up I need.

dc42

We have some code for driving DotStar LEDs. It's in the src/Fans subfolder of the RRF source. However, it's written to use a USART directly. For the Duet WiFi, it would be better to use the SharedSPI subsystem.

In terms of hardware, the DotStar doesn't have a CS input. Therefore if you are sharing the SPI signals with other devices, you need to gate the clock signal. I would use a 74HCT02 as a driver for the DotStar. Use two of the gates in the package connected in series to level-shift the MOSI signal to 5V. Use the 3rd gate to invert the SCL signal, then use the 4th gate to gate the output of the 3rd gate with your chosen CS signal.

I'd be happy to enable that code on in the standard build of RRF for the Duet WiFi, connected as described above.

Caution: DotStar LEDs can take a lot of current, up to around 80mA per LED if you turn all of RGBW on. So you shouldn't use the 5V power output of the Duet to power more than about 15 of them.

siblues

I am still trying to grasp learning how to use the Duet which is a steep learning curve for me.The gates you are referring to and wiring them up correctly without frying something are probably a bit beyond my know how at the moment.I will probably stick to a strip of 5v white leds for simple on/off control in order to light the bed.

TKWARD

@dc42

David,

Was this code ever implemented ?

I presume connection is via the Therm Board connector ?

I have a circuit diagram fleshed out based on your notes above ..... with CS jumpered to either CS1 through 4.

The obvious caveat is that the thermocouple usage wold be limited to 2 max ?

Also, what would the M150 command look like ? Eg .... for using CS3

( I have working discrete 24v LED driver strips working on other machines via the fan outputs .... I just fancy having a go at this.... maybe make a PCB if enough people are interested .... )

Thanks
Keith

dc42

@TKWARD said in Dotstar questions?:

Was this code ever implemented ?

Yes, in the standard firmware build for Duet 3. Not in the Duet 2 build. It could be added to the Duet 2 build but you would need some external gating and level shifting hardware to interface with the DotStar strip.

TKWARD

That's what I was alluding to. I can design a cheap pcb with the 74HCT02 and some connectors ( with a set of jumper to select an appropriate CS ).

Would the firmware changes be added just for this project ? Or, does it need to be added to the features 'wishlist' for Duet 2 firmware ?

I'll post a circuit diagram in the coming days for the potential design.

TKWARD

@dc42

Will this work ?

Did you see my previous questions ?

Duet-LED-Driver.pdf

TKWARD

@dc42

See replies below ...miss-tagged them ... there is a pdf with potential circuit diagram of addon board

dc42

I wouldn't use as much as 1000uF between Vcc and ground (100uF should be enough), but otherwise that should be OK. However, if you will be using a separate 5V supply to power the DotStar then you should take precautions against the Duet being powered but not the DotStar, or vice versa. A resistor of about 3K3 in series with each of Duet CS, SCLK and MOSI and the corresponding 74HCT02 connection should be sufficient.

Also the Duet and DotStar PSUs need a common ground, so it's probably best to link the grounds on that board.

TKWARD

@dc42 Thanks David.

The ground is definitely commoned.

I'll add the resistors as per your suggestion.

Would the firmware changes be added just for this project ? Or, does it need to be added to the features 'wishlist' for Duet 2 firmware ?

How would this be operated in terms of G code ? with M150 command ?

Also, assume that if a thermocouple board is used, only 2 of the CS would be available anyway ?

Thanks,

Keith

dc42

@TKWARD said in Dotstar questions?:

@dc42 Thanks David.

Would the firmware changes be added just for this project ? Or, does it need to be added to the features 'wishlist' for Duet 2 firmware ?

if you do ahead with this then I will enable DotStar support in RRF3. It will need a new configuration command (probably a variant of M150) to specify which CS line to use.

How would this be operated in terms of G code ? with M150 command ?

Yes.

Also, assume that if a thermocouple board is used, only 2 of the CS would be available anyway ?

Yes. So you might want to omit the jumper block and just wire it to use CS1. If you stack it on top of a daughter board then it would use CS3 instead automatically, because CS3 feeding into the daughter board is routed to the corresponding pin for CS1 on the top connector.

TKWARD

@dc42

I'm going ahead with it.

Jumpers removed.
CS is set to CS_1.
Tank Capacitor value changed, and resistors added as per your suggestion.

Just waiting on an assembly price from Chinese supplier.

I'd like to send you a few boards to test with the firmware. ( Take this offline and get address etc via pm ?? )

Thanks
Keith

nikscha

Any updates on the project so far? I'd be interested in the schematics for the board

CanDo415

Is it possible to skip some LEDs in the settings?
Lets say LEDs 1-10 are set to different colors.
I want to change LED2 without changing LED1.

T3P3Tony

@cando415 no, just send the same setting again for the LEDS who do not change.

CanDo415

can you store that info somewere? which LED should get what state?

Phaedrux

@cando415 said in Dotstar questions?:

can you store that info somewere? which LED should get what state?

Possibly as a variable

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

CanDo415

@phaedrux
Oh! I have to upgrade my knolagebase!
That makes it much better.
Thx

CanDo415

@phaedrux
is there a good tutorial for the metacommands somewere?

Phaedrux

I'm not aware of a tutorial, but between the wiki page and the meta command forum section you can find some examples and ask questions.

https://forum.duet3d.com/category/34/gcode-meta-commands