Posts made by krohelm

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

https://duet3d.dozuki.com/Wiki/Gcode#Section_M588_Forget_WiFi_host_network

I just went through all the network library again and saw this little footnote. So I read the gcode that came out of the configurator and noticed that it does not use a M552 S0. So I added

; Network
M552 S0                                  ; Put wifi in idle mode.  If you don't do this apparently it does not start up.

and it does connect now. I don't know why the module does not seem to turn on with the configurator-provided M552 S1 but hey it turns on now and I can reach the web interface.

This morning I downgraded the main firmware to 2.03 just to rule out any weirdness with a mismatched function from the 2.03 wifi firmware. Same sad state unfortunately. What information can I provide to help?

Hi Duet people! I'm trying to get started with my first Duet Wifi 2 and struggling to get my wifi working. The SPI error is concerning to me - I was unable to get the Duet to via the original firmware, so I tried updating.
Here's a log I captured after updating the both the Duet2CombinedFirmware.bin at 2.04RC1 and DuetWiFiServer.bin at 2.03:

RepRapFirmware for Duet 2 WiFi/Ethernet Version 2.04RC1 dated 2019-07-14b1

Executing config.g...Error: M587: Failed to add SSID to remembered list
HTTP is enabled on port 80
FTP is enabled on port 21
TELNET is disabled
Warning: Macro file config-override.g not found.

Done!
RepRapFirmware for Duet 2 WiFi/Ethernet is up and running.
WiFi module started
Error: Temperature reading fault on heater 1: sensor open circuit
WiFi reported error: no known networks found
WiFi module is idle
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.04RC1 running on Duet WiFi 1.02 or later + DueX2
Board ID: 08DGM-917DA-G4MSJ-6JKFJ-3SJ6N-TBRB9
Used output buffers: 1 of 24 (9 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 94104 of which 460 recycled
Exception stack ram used: 288
Never used ram: 10540
Tasks: NETWORK(ready,1244) HEAT(blocked,916) DUEX(suspended,156) MAIN(running,3844) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:09:33 ago, cause: power up
Last software reset details not available
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 29.0, current 31.3, max 31.5
Supply voltage: min 1.6, current 1.7, max 1.8, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Driver 5: ok, SG min/max not available
Driver 6: ok, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 1140769362
Slowest loop: 0.28ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is ready with "M122" in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.24ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8
- WiFi -
Network state is changing mode
WiFi module is idle
Failed messages: pending 0, notready 0, noresp 1
WiFi firmware version 1.23
WiFi reported error: no known networks found
WiFi module is idle
WiFi MAC address ec:fa:bc:25:34:8f
WiFi Vcc 3.43, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 26088
Socket states: 0 0 0 0 0 0 0 0
ok
Error retrieving WiFi status message: SPI timeout

WiFi reported error: no known networks found
WiFi module is idle

M587: Failed to retrieve network list
ok
Error retrieving WiFi status message: bad reply format version

Edit:
I found M111 S1 P14 lists wifi networks around the printer, however M587 S"mywifinetwork" P"my wifi password" gives: Executing config.g...Error: M587: Failed to add SSID to remembered list
and a bare M587 claims

M587: Failed to retrieve network list
ok
Error retrieving WiFi status message: bad reply format version

then returns to the every couple seconds spewing

WiFi reported error: no known networks found
WiFi module is idle