Topics created by krohelm

@krohelm to support Dotstar in bit-bang mode you would first need to define which additional pin to use, since Dotstar needs 2 pins instead of just one. Then it's just a matter of using bit-banged SPI to send the data.

Caution, RRF3.4 uses almost all the available flash memory on Duet 2. Adding this support will probably push it over the limit unless something else is removed. In RRF3.5 I have already removed support for M667 to make a little more space available.

Ah I was trying to access DWC on the pi from my pc (or phone or laptop). I guess I could set up a reverse proxy to localhost to trick DWC into thinking the request came in locally and offer up a connect dialog..

If you have a spare heater output (or you use RRF3, which allows you to configure a fan pin as a heater output), you can connect the fan to it. Then use the M307 I parameter for that heater to invert the sense of operation, i.e. the PWM will increase as the temperature rises. Is that what you need?

@dc42 said in Wifi 2 SPI Timeout:

Leaving your network password on the SD card is a security risk. Don't do it.

In fact this is the only reason it occurred to me to remove from config.g. If that data were not somewhat sensitive I would have left it and never found the solution.

A oneshot.g or something could work though - read once and deleted by the firmware. Or just decline to provide the m587 at all and let users find the command. 🤷 I'm sure you're more than capable of doing the right thing for rrf on this minor issue. Thanks for looking into it!