@dc42 Thanks for the reply - Dotstars have a pleasing non-flickering warm glow that is easy on my eyes . I have wired my printer with these for the last 2 years & they're awesome.

Looks like SUPPORT_BITBANG_NEOPIXEL is the only path for DUET_NG which I'm guessing aliases duet wifi based on other usages. The rest are SUPPORT_DMA_* (exception being PCCB_10 which I'm not sure I know what it is). I guess the Wifi only supports bitbang? These preprocessor definitions are dense & I'm not quite sure yet what needs to happen to add neopixel bitbang for DUET_NG!

FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.4.0 ELECTRONICS: Duet WiFi 1.02 or later + DueX2 FIRMWARE_DATE: 2022-03-15 18:58:33

I'm trying to connect a DotStar strip to a Duet2 as documented here for neopixels: https://docs.duet3d.com/en/User_manual/Connecting_hardware/IO_Neopixel_DotStar

When sending M150 X0 P255 S20 I receive Error: M150: Unsupported LED strip type.

I have an external 5v PSU and have been historically driving these LEDs via a CircuitPython m4 but I'm trying to simplify the wiring and maintenance burden of my printer. Is there any way we can get DotStar allowed on Duet2?

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..

How do I set the connection string for my printer when running DWC remotely?

It spins connecting on my raspberry pi, trying to GET /rr_connect?password=reprap&time=2020-5-30T22%3A11%3A30 which results in 404 because how should it know where my printer is! I'm reading the code for dwc but I haven't found any printer connection query parameters or anything like I'd naively expect to see (or a machine connection selection box on dwc in the Machine Specific submenu)

Removing the WiFi module looks doable. I'm using multiple Z probes with 3.1.1 though, which I think is not as well supported on 3.02 (K parameter on homing probe command).

Running DWC on the pi might be enough for now, and when I finally burn up my Duet I'll reach for a 3 and direct-wire to an SBC. Thanks!

I have a Duet 2 Wifi + Duex and would like to use a Raspberry Pi to host DWC and other external printer functions. Is there a pin breakout of what to connect where between a 2 and a Pi, and what to do to safely remove the web code from the Duet?

@TLAS Thanks for the ideas! I'm not sure this will do what I'm after - for now I will just use 20% pwm while printing and hope temperatures stay relatively steady then amp up to 100% for a few minutes after printing to evacuate fumes through the charcoal. Might be a neat new gcode, I'll keep it in mind in case I get the urge to contribute to rrf.

I have an enclosed chamber with a large bed. There is a filtered vent on the back and I'd like to modulate the speed of the extraction fan to hold a target temperature (e.g., 50c) in the chamber. On a previous printer I made a microcontroller, display and rotary encoder to set it by hand. With a Duet 2 Wifi I'd expect to be able to set this up via gcode.
Reading the GCode page I don't see an affordance for it, but I'm new to RRF. How do people configure this kind of behavior?

@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!

The firmware configuration tool spat out m587 into config.g yes. Through trial and much error I took it out and ran that via serial. The m587 seems to have been somehow poisoning the startup of the wifi chip.