[3.6.0-beta.3] DWC connection issues Duet2 / Duex5

timschneider

timschneider

@chrishamm
Damn! This really looks promising!

https://github.com/Duet3D/RepRapFirmware/commit/a3498d31aa746d0486e5a109c091f15a8b8e41c0

This could explain all the issues we and our customers have been facing – what could be described as DWC instability.
We use object labels in every print, most of our customers have a large file list, most print jobs take longer than a day, often 3-5 days. I am really excited and looking forward to trying this out!

0

chrishamm committed to Duet3D/RepRapFirmware

Fix for too long G-code replies (#1073)

Added extra parameter to OutputBuffer::Allocate to specify if the buffer
to be allocated may be taken from the output buffer reserve. This is
always true except if appending to an existing output buffer chain or
when the request may be repeated without downsides.
Also reduced the number of reserved output buffers to 2 on Duet 2 series

chrishamm

@timschneider Please give it a try then. Do you need a firmware binary for testing?

timschneider

@chrishamm if you have one at hand, that would be nice. If not, I can compile my own withing the next days.

timschneider

@chrishamm
Hi Chris,Thank you for your prompt reply and the in-depth solution. The fix does indeed help alleviate the ‘M122 M122 M122’ issue. Calling ‘M122 M122 M122 M122 M122 M122 M122’ sometimes still causes the web server to crash (will not recover), and calling ‘M98 P"0:/macros/test-bufferoverflow4.g"’ twice resets the connection. With 3 open sessions, all DWC.

With only two open DWC sessions it can still recover the M122 M122 M122 M122 M122 M122 M122. Calling M98 P"0:/macros/test-bufferoverflow4.g" will still reconnect DWC.
With only one session it will just reconnect with the M122 bomb and I'm unable to get it disconnected with the M98 P"0:/macros/test-bufferoverflow4.g".

So I think part of the problem is fixed and it feels like 80% fixed – 20% left and it is somehow related to multiple client sessions.

I will be in the office tomorrow to get some usb logs.

It is maybe worth to consider if RRF is low on OutputBuffers not to concat the gcode replys of multiple requests but instead drop the previos reply.

Btw. with my special python client connected (calling rr_reply as fast as possible when receiving the first HTTP 503) I am not able to get it crashed nor disconnected now.

Edit:
I stumbled over the MinimumBuffersForObjectModel and the rr_model request is checking if there are free buffers available, but what will happen the other way around? Like, query a rr_model and then from another socket a rr_gcode with large response in rr_reply?

Tim

chrishamm

@timschneider said in [3.6.0-beta.3] DWC connection issues Duet2 / Duex5:

It is maybe worth to consider if RRF is low on OutputBuffers not to concat the gcode replys of multiple requests but instead drop the previos reply.

That's what happens. For the same reason the last M122 output is likely truncated if you send multiple M122s at once.

@timschneider said in [3.6.0-beta.3] DWC connection issues Duet2 / Duex5:

I stumbled over the MinimumBuffersForObjectModel and the rr_model request is checking if there are free buffers available, but what will happen the other way around? Like, query a rr_model and then from another socket a rr_gcode with large response in rr_reply?

rr_model waits half a second if it cannot allocate enough memory for the response and if it fails, HTTP 503 is returned. In that case a client should request the reply to free up the buffers again ASAP. I still think it would be good to add a new parameter to rr_connect to make RRF discard G-code replies for particular clients.

timschneider

@chrishamm hm i don't know -

@chrishamm said in [3.6.0-beta.3] DWC connection issues Duet2 / Duex5:

rr_model waits half a second if it cannot allocate enough memory for the response and if it fails, HTTP 503 is returned. In that case a client should request the reply to free up the buffers again ASAP. I still think it would be good to add a new parameter to rr_connect to make RRF discard G-code replies for particular clients.

that would solve the problem with bot clients - but I was connected with two or three DWC sessions only.
Maybe add a timeout to rr_reply, after 500ms or 1s the reply will be discarded regardless of if it was fetched or not?! But anyhow maybe the problem is somewhere else, I was just speculating, because the problem now appears only with multiple sessions.

timschneider

@chrishamm said in [3.6.0-beta.3] DWC connection issues Duet2 / Duex5:

That's what happens. For the same reason the last M122 output is likely truncated if you send multiple M122s at once.

i tried to digg deeper into it and it looks like this is working even with multiple clients, but there is a behaviour I would not expect from RRF. It will serve the reply even after a reconnect / 3 timeouts (HTTP 503 on rr_model).

Maybe the firmware can drop pending gcode replies if it is short on memory and not able to serve multiple rr_model requests?
Maybe instead of dropping, turncat and leave a message why this happend. Like, "This is your response ... (turncated due to low memory)" that the pending reply will fit into exactly one output buffer.

Or maybe concider setting clientsServed++; on connect of new clients, why whould a new client be interested in an old pending reply?

Guess that would help and only minor impack normal operation (will not happen on single client connections, and on multi client connections just sometimes for large replies)

timschneider

@chrishamm
Today I was able to get new USB logs - the SPI timeout is still present in the last release.

Printer was idle with one open session.

Error: failed to retrieve WiFi status message: SPI timeout<\n>
=== Diagnostics ===<\n>
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.6.0-beta.3+4 (2025-02-05 09:48:00) running on Duet WiFi 1.02 or later + DueX5v0.11<\n>
Board ID: 08DJM-9178L-L4MSJ-6J1FL-3S86J-TB2LN<\n>
Used output buffers: 1 of 26 (21 max)<\n>
=== RTOS ===<\n>
Static ram: 23776<\n>
Dynamic ram: 69864 of which 0 recycled<\n>
Never used RAM 25444, free system stack 130 words<\n>
Tasks: NETWORK(1,nWait 6,10.1%,211) HEAT(3,nWait 5,0.1%,283) Move(4,nWait 5,0.0%,264) DUEX(5,nWait 5,0.0%,23) MAIN(1,running,89.0%,698) IDLE(0,ready,0.8%,29), total 100.0%<\n>
Owned mutexes: WiFi(NETWORK) USB(MAIN)<\n>
=== Platform ===<\n>
Last reset 24:55:18 ago, cause: power up<\n>
Last software reset at 2025-02-03 20:56, reason: User, Gcodes spinning, available RAM 24764, slot 1<\n>
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a<\n>
Error status: 0x00<\n>
MCU temperature: min 26.2, current 29.5, max 30.4<\n>
Supply voltage: min 23.7, current 24.0, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes<\n>
Heap OK, handles allocated/used 99/7, heap memory allocated/used/recyclable 2048/256/120, gc cycles 4227<\n>
Events: 0 queued, 0 completed<\n>
Date/time: 1970-01-01 00:00:00<\n>
Slowest loop: 202.01ms; fastest: 0.12ms<\n>
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0<\n>
=== Storage ===<\n>
Free file entries: 9<\n>
SD card 0 detected, interface speed: 20.0MBytes/sec<\n>
SD card longest read time 28.9ms, write time 101.0ms, max retries 0<\n>
=== Move ===<\n>
Segments created 38, maxWait 41665760ms, bed comp in use: none, height map offset 0.000, hiccups added 0/0 (0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00<\n>
Pos req/act/dcf: 40320.00/40320/-0.00 -24320.00/-24320/-0.00 400.00/400/0.00<\n>
no step interrupt scheduled<\n>
Driver 0: standstill, SG min 177<\n>
Driver 1: standstill, SG min 167<\n>
Driver 2: standstill, SG min n/a<\n>
Driver 3: standstill, SG min n/a<\n>
Driver 4: standstill, SG min n/a<\n>
Driver 5: standstill, SG min n/a<\n>
Driver 6: standstill, SG min n/a<\n>
Driver 7: standstill, SG min n/a<\n>
Driver 8: standstill, SG min n/a<\n>
Driver 9: standstill, SG min n/a<\n>
Driver 10: <\n>
Driver 11: <\n>
=== DDARing 0 ===<\n>
Scheduled moves 15, completed 15, LaErrors 0, Underruns [0, 0, 0]<\n>
Segments left 0<\n>
Code queue is empty<\n>
=== Heat ===<\n>
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0<\n>
=== GCodes ===<\n>
Movement locks held by null<\n>
HTTP is idle in state(s) 0 0 0 0<\n>
Telnet is idle in state(s) 0<\n>
File is idle in state(s) 0<\n>
USB is ready with "M122" in state(s) 0<\n>
Aux is idle in state(s) 0<\n>
Trigger is idle in state(s) 0<\n>
Queue is idle in state(s) 0<\n>
LCD is idle in state(s) 0<\n>
Daemon is idle in state(s) 0<\n>
Autopause is idle in state(s) 0<\n>
=== Filament sensors ===<\n>
check 0 clear 319057472<\n>
Extruder 0: pos 2160.00, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0<\n>
=== DueX ===<\n>
Read count 1, 0.00 reads/min<\n>
=== Network ===<\n>
Slowest loop: 201.38ms; fastest: 0.00ms<\n>
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)<\n>
HTTP sessions: 0 of 8<\n>
=== WiFi ===<\n>
Interface state: active<\n>
Module is connected to access point <\n>
Failed messages: pending 0, notrdy 5, noresp 261465<\n>
Failed to get WiFi status<\n>
Socket states: 0 0 0 6 0 0 0 0<\n>
ok<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
Error: failed to retrieve WiFi statu

I was able to reset the WIFI module via USB with

M552 S-1
M552 S0
M552 S1

WiFi module stopped<\n>
ok<\n>
Error: failed to retrieve WiFi status message: SPI timeout<\n>
ok<\n>
WiFi module started<\n>
=== Diagnostics ===<\n>
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.6.0-beta.3+4 (2025-02-05 09:48:00) running on Duet WiFi 1.02 or later + DueX5v0.11<\n>
Board ID: 08DJM-9178L-L4MSJ-6J1FL-3S86J-TB2LN<\n>
Used output buffers: 1 of 26 (21 max)<\n>
=== RTOS ===<\n>
Static ram: 23776<\n>
Dynamic ram: 69864 of which 0 recycled<\n>
Never used RAM 25444, free system stack 130 words<\n>
Tasks: NETWORK(1,ready,0.9%,211) HEAT(3,nWait 5,0.1%,283) Move(4,nWait 5,0.0%,264) DUEX(5,nWait 5,0.0%,23) MAIN(1,running,97.5%,698) IDLE(0,ready,1.5%,29), total 100.0%<\n>
Owned mutexes: USB(MAIN)<\n>
=== Platform ===<\n>
Last reset 24:57:54 ago, cause: power up<\n>
Last software reset at 2025-02-03 20:56, reason: User, Gcodes spinning, available RAM 24764, slot 1<\n>
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a<\n>
Error status: 0x00<\n>
MCU temperature: min 28.7, current 29.7, max 30.2<\n>
Supply voltage: min 23.9, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes<\n>
Heap OK, handles allocated/used 99/7, heap memory allocated/used/recyclable 2048/1164/1028, gc cycles 4234<\n>
Events: 0 queued, 0 completed<\n>
Date/time: 1970-01-01 00:00:00<\n>
Slowest loop: 99.34ms; fastest: 0.22ms<\n>
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0<\n>
=== Storage ===<\n>
Free file entries: 9<\n>
SD card 0 detected, interface speed: 20.0MBytes/sec<\n>
SD card longest read time 2.3ms, write time 4.7ms, max retries 0<\n>
=== Move ===<\n>
Segments created 38, maxWait 0ms, bed comp in use: none, height map offset 0.000, hiccups added 0/0 (0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00<\n>
Pos req/act/dcf: 40320.00/40320/-0.00 -24320.00/-24320/-0.00 400.00/400/0.00<\n>
no step interrupt scheduled<\n>
Driver 0: standstill, SG min n/a<\n>
Driver 1: standstill, SG min n/a<\n>
Driver 2: standstill, SG min n/a<\n>
Driver 3: standstill, SG min n/a<\n>
Driver 4: standstill, SG min n/a<\n>
Driver 5: standstill, SG min n/a<\n>
Driver 6: standstill, SG min n/a<\n>
Driver 7: standstill, SG min n/a<\n>
Driver 8: standstill, SG min n/a<\n>
Driver 9: standstill, SG min n/a<\n>
Driver 10: <\n>
Driver 11: <\n>
=== DDARing 0 ===<\n>
Scheduled moves 15, completed 15, LaErrors 0, Underruns [0, 0, 0]<\n>
Segments left 0<\n>
Code queue is empty<\n>
=== Heat ===<\n>
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0<\n>
=== GCodes ===<\n>
Movement locks held by null<\n>
HTTP is idle in state(s) 0 0 0 0<\n>
Telnet is idle in state(s) 0<\n>
File is idle in state(s) 0<\n>
USB is ready with "M122" in state(s) 0<\n>
Aux is idle in state(s) 0<\n>
Trigger is idle in state(s) 0<\n>
Queue is idle in state(s) 0<\n>
LCD is idle in state(s) 0<\n>
Daemon is idle in state(s) 0<\n>
Autopause is idle in state(s) 0<\n>
=== Filament sensors ===<\n>
check 0 clear 319632530<\n>
Extruder 0: pos 2160.00, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0<\n>
=== DueX ===<\n>
Read count 0, 0.00 reads/min<\n>
=== Network ===<\n>
Slowest loop: 200.20ms; fastest: 0.00ms<\n>
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)<\n>
HTTP sessions: 0 of 8<\n>
=== WiFi ===<\n>
Interface state: idle<\n>
Module is idle<\n>
Failed messages: pending 0, notrdy 0, noresp 0<\n>
Firmware version 2.2.1<\n>
MAC address 00:00:00:00:00:00<\n>
Module reset reason: Turned on by main processor, Vcc 3.47, flash size 4194304, free heap 53932<\n>
Clock register 00002002<\n>
Socket states: 0 0 0 6 0 0 0 0<\n>
ok<\n>
ok<\n>
WiFi module is connected to access point Meltingplot, IP address 10.42.0.2<\n>

As this is a different bug than the large response one, should we keep track in a different thread, @chrishamm @T3P3Tony ?

T3P3Tony

@timschneider yes please