Diagnostics Missing?
-
@generisi said in Diagnostics Missing?:
When I enter M122, I don't get any information. I also don't see "diag" files in the list of assets. What am I missing? Thanks!
Just upgraded to 3.4.0beta2 (2021-08-03) and Duet Web Control 3.4.0-b2 and can confirm M122 does not return diagnostics.
Its actually a little trickier (tested Firefox and Chrome). If I send M122 on my PC, it only confirms the event in green. If I have console opened at the same time on mobile (Safari) the results of M122 are shown there. If I send M122 on mobile (Safari) the inverse is true, event is returned as green but on PC the diagnostics are printed.
-
@sebkritikel Make sure you have only one active DWC tab/session per device.
-
@chrishamm Seeing no change
-
Closed out of all active DWC sessions (mobile, PC, etc)
-
Rebooted printer
-
M122 -> no diag output on PC/session that sent M122
-
Opened DWC on PC and Mobile
-
Rebooted printer
-
M122 on PC -> no output on PC/session that sent M122, output visible on mobile
-
M122 on mobile -> no output on mobile/session that sent M122, output visible on PC
-
-
@sebkritikel That's odd, it sounds like you access DWC through a network tunnel. Can you check how many HTTP sessions are reported by M122? It should be two, one for your mobile and another one for the PC.
-
@chrishamm said in Diagnostics Missing?:
@sebkritikel That's odd, it sounds like you access DWC through a network tunnel. Can you check how many HTTP sessions are reported by M122? It should be two, one for your mobile and another one for the PC.
It reports two sessions (with mobile and PC connected). FWIW the mobile device is connected to the same WiFi network.
I was previously running one of the latest Input Shaping binaries and definitely did not notice this behavior.
=== Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0beta2 (2021-08-03 12:41:37) running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DGM-917DA-G4MSD-6JTDD-3SN6L-1STR9 Used output buffers: 3 of 24 (24 max) === RTOS === Static ram: 23932 Dynamic ram: 79136 of which 0 recycled Never used RAM 9012, free system stack 186 words Tasks: NETWORK(notifyWait,14.3%,233) ACCEL(notifyWait,0.0%,348) HEAT(delaying,0.0%,326) Move(notifyWait,0.0%,364) DUEX(notifyWait,0.0%,24) MAIN(running,85.6%,443) IDLE(ready,0.0%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:00:59 ago, cause: software Last software reset at 2021-08-05 11:06, reason: User, GCodes spinning, available RAM 9012, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x04 Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 34.0, current 34.3, max 34.8 Supply voltage: min 23.9, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Driver 0: position 0, standstill, SG min/max not available Driver 1: position 0, standstill, SG min/max not available Driver 2: position 0, standstill, SG min/max not available Driver 3: position 0, standstill, SG min/max not available Driver 4: position 0, standstill, SG min/max not available Driver 5: position 0, standstill, SG min/max not available Driver 6: position 0, standstill, SG min/max not available Driver 7: position 0, standstill, SG min/max not available Driver 8: position 0, standstill, SG min/max not available Driver 9: position 0, standstill, SG min/max not available Driver 10: position 0 Driver 11: position 0 Date/time: 2021-08-05 11:07:02 Cache data hit count 2152506680 Slowest loop: 6.23ms; fastest: 0.17ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 1.0ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 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 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === DueX === Read count 0, 0.00 reads/min === Network === Slowest loop: 205.64ms; fastest: 0.09ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 2 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 1 WiFi firmware version 1.23 WiFi MAC address cc:50:e3:0d:25:4b WiFi Vcc 3.40, reset reason Turned on by main processor WiFi flash size 4194304, free heap 20968 WiFi IP address 192.168.0.8 WiFi signal strength -40dBm, mode none, reconnections 0, sleep mode modem Clock register ffffffff Socket states: 4 0 0 0 0 0 0 0 -
@generisi When I enter M122 on the Paneldue, I get the first few lines on its' screen.
-
@sebkritikel Thanks for the confirmation!
-
@generisi Unfortunately the PanelDue doesn't have enough ram and display capacity to show the entire M122 report on it's screen.
Can yu confirm that you are using 3.4 beta 2 and are experiencing the same symptoms as @sebkritikel ?
-
@phaedrux Yes, I am running 3.4beta2. I haven't tried opening two browsers from two different IP addresses; should I ?
-
You could. You might see the same behaviour as seb did and see the output of M122 at least.
-
@phaedrux I just tried 2 different browsers on same PC.Diagnostic info shows on first duet web session and browser when entered into the second web browser session. It does not appear to work the other way around
=== Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0beta2 (2021-08-03 12:41:37) running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DGM-9T6BU-FG3SJ-6JKF4-3SD6L-TUXRF Used output buffers: 3 of 24 (24 max) === RTOS === Static ram: 23932 Dynamic ram: 79440 of which 0 recycled Never used RAM 4940, free system stack 98 words Tasks: NETWORK(ready,14.0%,227) ACCEL(notifyWait,0.0%,348) HEAT(delaying,0.1%,326) Move(notifyWait,1.7%,285) DUEX(notifyWait,0.0%,24) MAIN(running,84.1%,381) IDLE(ready,0.0%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 03:58:03 ago, cause: software Last software reset at 2021-08-05 09:23, reason: User, GCodes spinning, available RAM 8916, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00417000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x0c Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 37.1, current 37.6, max 38.1 Supply voltage: min 24.1, current 24.3, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/12/0, gc cycles 0 Driver 0: position 24822, ok, SG min/max 0/1023 Driver 1: position 4516, ok, SG min/max 0/1023 Driver 2: position 90248, standstill, SG min/max 0/1023 Driver 3: position 3300, ok, SG min/max 0/1023 Driver 4: position 0, standstill, SG min/max not available Driver 5: position 0, standstill, SG min/max not available Driver 6: position 0, standstill, SG min/max not available Driver 7: position 0, standstill, SG min/max not available Driver 8: position 0, standstill, SG min/max not available Driver 9: position 0, standstill, SG min/max not available Driver 10: position 0 Driver 11: position 0 Date/time: 2021-08-05 13:21:32 Cache data hit count 4294967295 Slowest loop: 12.86ms; fastest: 0.18ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 9 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 1.3ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 38, maxWait 0ms, bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves 168818, completed moves 168778, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 Heater 0 is on, I-accum = 0.0 Heater 1 is on, I-accum = 0.5 === GCodes === Segments left: 1 Movement lock held by null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is doing "G1 X140.012 Y77.042 E0.0100" in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === DueX === Read count 0, 0.00 reads/min === Network === Slowest loop: 201.01ms; fastest: 0.08ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 2 WiFi firmware version 1.26 WiFi MAC address ec:fa:bc:25:34:dd WiFi Vcc 3.34, reset reason Turned on by main processor WiFi flash size 4194304, free heap 24632 WiFi IP address 192.168.123.68 WiFi signal strength -69dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
Thanks for confirming.
-
@phaedrux And it only displays the diagnostics issues once. After that, all it shows in the console on both browsers is "M122"
-
@chrishamm I just upgraded to DWC and RRF 3.4.0-b3/3.4.0beta3 (2021-08-24) and am still having this issue.
=== Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0beta3 (2021-08-24 13:56:10) running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DGM-917DA-G4MSD-6JTDD-3SN6L-1STR9 Used output buffers: 3 of 24 (24 max) === RTOS === Static ram: 23940 Dynamic ram: 77256 of which 44 recycled Never used RAM 10840, free system stack 184 words Tasks: NETWORK(ready,15.8%,227) HEAT(notifyWait,0.0%,326) Move(notifyWait,0.0%,364) DUEX(notifyWait,0.0%,24) MAIN(running,84.1%,441) IDLE(ready,0.1%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:01:03 ago, cause: software Last software reset at 2021-08-25 15:58, reason: User, GCodes spinning, available RAM 10840, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x04 Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 31.2, current 31.8, max 31.8 Supply voltage: min 23.9, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Driver 0: position 0, standstill, SG min/max not available Driver 1: position 0, standstill, SG min/max not available Driver 2: position 0, standstill, SG min/max not available Driver 3: position 0, standstill, SG min/max not available Driver 4: position 0, standstill, SG min/max not available Driver 5: position 0, standstill, SG min/max not available Driver 6: position 0, standstill, SG min/max not available Driver 7: position 0, standstill, SG min/max not available Driver 8: position 0, standstill, SG min/max not available Driver 9: position 0, standstill, SG min/max not available Driver 10: position 0 Driver 11: position 0 Date/time: 2021-08-25 15:59:56 Cache data hit count 2383346339 Slowest loop: 6.10ms; fastest: 0.16ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 1.0ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 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 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === DueX === Read count 0, 0.00 reads/min === Network === Slowest loop: 201.10ms; fastest: 0.09ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 2 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 2 WiFi firmware version 1.23 WiFi MAC address cc:50:e3:0d:25:4b WiFi Vcc 3.40, reset reason Turned on by main processor WiFi flash size 4194304, free heap 23960 WiFi IP address 192.168.0.8 WiFi signal strength -39dBm, mode none, reconnections 0, sleep mode modem Clock register ffffffff Socket states: 0 0 0 0 0 0 0 0 -
@sebkritikel we've identified an issue in DWC that prevents the M122 response from a Duet WiFi being displayed in some situations. It looks like it may have been triggered by the response getting a little longer.
