3.4.0 & Web Control Connection
-
I am running a Duet 3 MB6HC with 3.4.0 firmware in standalone mode with the corresponding DWC version. (Uploaded the zip file when doing the firmware update). I am now seeing that if the machine sits idle (say 10-20 minutes), I am unable to connect via DWC. Pinging the IP address shows its connected to the network, but when I try to open the DWC page in chrome it will return a white page or some times the chrome connection error page. If I reset the Duet DWC will open without issue until the machine is left idle.
I don't remember running into this with the previous versions. Any one else experiencing this?
M122 when I'm unable to connect:
M122<LF> === Diagnostics ===<LF> RepRapFirmware for Duet 3 MB6HC version 3.4.0 (2022-03-15 18:57:24) running on Duet 3 MB6HC v1.01 or later (standalone mode)<LF> Board ID: 08DJM-956BA-NA3TN-6JTD0-3S46R-1BAGS<LF> Used output buffers: 1 of 40 (28 max)<LF> === RTOS ===<LF> Static ram: 151000<LF> Dynamic ram: 94952 of which 0 recycled<LF> Never used RAM 104720, free system stack 192 words<LF> Tasks: NETWORK(ready,27.1%,175) ETHERNET(notifyWait,0.1%,163) HEAT(notifyWait,0.0%,371) Move(notifyWait,0.5%,248) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,333) TMC(notifyWait,8.1%,92) MAIN(running,64.2%,925) IDLE(ready,0.1%,30), total 100.0%<LF> Owned mutexes: USB(MAIN)<LF> === Platform ===<LF> Last reset 00:41:32 ago, cause: reset button<LF> Last software reset at 2022-05-05 08:12, reason: User, GCodes spinning, available RAM 104044, slot 0<LF> Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a<LF> Error status: 0x00<LF> Aux0 errors 0,0,0<LF> Step timer max interval 352<LF> MCU temperature: min 30.7, current 32.0, max 32.1<LF> Supply voltage: min 24.3, current 24.3, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes<LF> 12V rail voltage: min 11.9, current 12.0, max 12.1, under voltage events: 0<LF> Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0<LF> Events: 0 queued, 0 completed<LF> Driver 0: standstill, SG min n/a, mspos 8, reads 8133, writes 0 timeouts 0<LF> Driver 1: standstill, SG min n/a, mspos 8, reads 8134, writes 0 timeouts 0<LF> Driver 2: standstill, SG min n/a, mspos 8, reads 8134, writes 0 timeouts 0<LF> Driver 3: standstill, SG min n/a, mspos 8, reads 8133, writes 0 timeouts 0<LF> Driver 4: standstill, SG min n/a, mspos 8, reads 8133, writes 0 timeouts 0<LF> Driver 5: standstill, SG min n/a, mspos 8, reads 8133, writes 0 timeouts 0<LF> Date/time: 2022-05-18 08:37:56<LF> Slowest loop: 247.31ms; fastest: 0.05ms<LF> === Storage ===<LF> Free file entries: 10<LF> SD card 0 detected, interface speed: 25.0MBytes/sec<LF> SD card longest read time 3.0ms, write time 114.2ms, max retries 0<LF> === Move ===<LF> DMs created 125, segments created 0, maxWait 339407ms, bed compensation in use: none, comp offset 0.000<LF> === MainDDARing ===<LF> Scheduled moves 76867, completed 76867, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1<LF> === AuxDDARing ===<LF> Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1<LF> === Heat ===<LF> Bed heaters -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0<LF> === GCodes ===<LF> Segments left: 0<LF> Movement lock held by null<LF> HTTP is idle in state(s) 0<LF> Telnet is idle in state(s) 0<LF> File is idle in state(s) 0<LF> USB is ready with "M122" in state(s) 0<LF> Aux is idle in state(s) 0<LF> Trigger is idle in state(s) 0<LF> Queue is idle in state(s) 0<LF> LCD is idle in state(s) 0<LF> SBC is idle in state(s) 0<LF> Daemon is idle in state(s) 0<LF> Aux2 is idle in state(s) 0<LF> Autopause is idle in state(s) 0<LF> Code queue is empty<LF> === CAN ===<LF> Messages queued 11898, received 0, lost 0, boc 0<LF> Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 11898/0/0<LF> Tx timeouts 0,0,11898,0,0,0 last cancelled message type 30 dest 127<LF> === Network ===<LF> Slowest loop: 868.60ms; fastest: 0.02ms<LF> Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions<LF> HTTP sessions: 0 of 8<LF> - Ethernet -<LF> State: active<LF> Error counts: 6 0 0 195 0<LF> Socket states: 2 2 2 2 2 0 0 0<LF> ok<LF>M122 when I can connect:
M122<LF> === Diagnostics ===<LF> RepRapFirmware for Duet 3 MB6HC version 3.4.0 (2022-03-15 18:57:24) running on Duet 3 MB6HC v1.01 or later (standalone mode)<LF> Board ID: 08DJM-956BA-NA3TN-6JTD0-3S46R-1BAGS<LF> Used output buffers: 1 of 40 (19 max)<LF> === RTOS ===<LF> Static ram: 151000<LF> Dynamic ram: 94952 of which 0 recycled<LF> Never used RAM 104720, free system stack 184 words<LF> Tasks: NETWORK(ready,26.4%,209) ETHERNET(notifyWait,0.2%,168) HEAT(notifyWait,0.0%,373) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,333) TMC(notifyWait,8.2%,92) MAIN(running,65.3%,925) IDLE(ready,0.0%,30), total 100.0%<LF> Owned mutexes: USB(MAIN)<LF> === Platform ===<LF> Last reset 00:01:29 ago, cause: reset button<LF> Last software reset at 2022-05-05 08:12, reason: User, GCodes spinning, available RAM 104044, slot 0<LF> Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a<LF> Error status: 0x00<LF> Aux0 errors 0,0,0<LF> Step timer max interval 127<LF> MCU temperature: min 31.6, current 31.8, max 32.0<LF> Supply voltage: min 24.3, current 24.3, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes<LF> 12V rail voltage: min 12.0, current 12.0, max 12.0, under voltage events: 0<LF> Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0<LF> Events: 0 queued, 0 completed<LF> Driver 0: standstill, SG min n/a, mspos 8, reads 39322, writes 0 timeouts 0<LF> Driver 1: standstill, SG min n/a, mspos 8, reads 39322, writes 0 timeouts 0<LF> Driver 2: standstill, SG min n/a, mspos 8, reads 39322, writes 0 timeouts 0<LF> Driver 3: standstill, SG min n/a, mspos 8, reads 39323, writes 0 timeouts 0<LF> Driver 4: standstill, SG min n/a, mspos 8, reads 39323, writes 0 timeouts 0<LF> Driver 5: standstill, SG min n/a, mspos 8, reads 39323, writes 0 timeouts 0<LF> Date/time: 2022-05-18 08:40:33<LF> Slowest loop: 9.88ms; fastest: 0.05ms<LF> === Storage ===<LF> Free file entries: 10<LF> SD card 0 detected, interface speed: 25.0MBytes/sec<LF> SD card longest read time 3.0ms, write time 0.0ms, max retries 0<LF> === Move ===<LF> DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000<LF> === MainDDARing ===<LF> Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1<LF> === AuxDDARing ===<LF> Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1<LF> === Heat ===<LF> Bed heaters -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0<LF> === GCodes ===<LF> Segments left: 0<LF> Movement lock held by null<LF> HTTP is idle in state(s) 0<LF> Telnet is idle in state(s) 0<LF> File is idle in state(s) 0<LF> USB is ready with "M122" in state(s) 0<LF> Aux is idle in state(s) 0<LF> Trigger is idle in state(s) 0<LF> Queue is idle in state(s) 0<LF> LCD is idle in state(s) 0<LF> SBC is idle in state(s) 0<LF> Daemon is idle in state(s) 0<LF> Aux2 is idle in state(s) 0<LF> Autopause is idle in state(s) 0<LF> Code queue is empty<LF> === CAN ===<LF> Messages queued 212, received 0, lost 0, boc 0<LF> Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 212/0/0<LF> Tx timeouts 0,0,212,0,0,0 last cancelled message type 30 dest 127<LF> === Network ===<LF> Slowest loop: 1.77ms; fastest: 0.02ms<LF> Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions<LF> HTTP sessions: 1 of 8<LF> - Ethernet -<LF> State: active<LF> Error counts: 0 0 0 0 0<LF> Socket states: 2 2 2 2 2 0 0 0<LF> ok<LF> -
Can you try this release?
https://github.com/Duet3D/RepRapFirmware/releases/tag/3.4.1rc1
That would mean uploading these files
https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.1rc1/DuetWebControl-SD.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.1rc1/Duet3Firmware_MB6HC.bin -
@that-guy-e Can you say if the problem is reproducible from a different device and/or browser? The error counters from your first diagnostics looks odd but at first glance it's hard to tell why (
Error counts: 6 0 0 195 0). -
@chrishamm I can confirm that connection issue with a couple PC's and mobile device all using chrome on the network.
-
Initial testing of 3.4.1rc1 looks promising. Able to connect after being idle for an hour. I'll continue to monitor it and see how it goes. I didn't see anything in the release notes regarding the web server. Were there tweaks there.
-
After some additional time idle I'm back to not being able to load DWC from 2 PC's. Whats interesting is I then tried to open DWC from a mobile device on the network and it worked. After opening it from mobile both PC's were able to load the page. Both PC's were on ethernet while the mobile device was on wifi.
-
Do you often have multiple connections open from different devices?
-
Rarely if ever do I have multiple connections. I was just trying from a few different devices to see if the results were consistent.
-
What kind of switch/router do you have? What does the network topology look like between Duet and your PCs compared to your phone? Perhaps it's overly aggressive power control on the Duet port or something.
-
Its all business class hardware on the network side. I'll have to check with my IT group and see if they are seeing anything odd on there end.
I can also try rolling back to a pre 3.4 version. Perhaps the issue is on my end and I didn't notice till I updated to 3.4.0
-
I don't know if it would be possible for you, but could you try a direct network connection between the Duet and your PC just to eliminate the network hardware entirely?
https://docs.duet3d.com/en/User_manual/Machine_configuration/Networking#wired-direct-connection
-
sorry for the late reply, I just saw this. I'll do a direct connection and see what happens.