DWC intermittently stops tracking job data
-
On occasion while running a print job the DWC stops displaying job related data and all the fields are blank except for the slicer job time. Its been kind of annoying but hardly a big deal until it happened on hour 3 of a 72 hour print.
I'm assuming there is nothing I can do on this print job but any ideas when its complete ?
-
@kingofthegeeks
You could configure auto-safe on power failure (M911).
When it happens next time, just pull the plug and restart everything (including browser, just to be sure)
If the duet board had enough time to safe the data, you can see a resurrect.g file in /sys folder.
Run it, or send M916 or use the 'resume print' button to start from there.It's a good idea to test pause/resume and power failure behaviour on a less important print
-
@o_lampe seems like a reasonable solution, so I guess this is a common occurrence and to be expected then?
-
@kingofthegeeks
I can't tell if this is to be expected. I have used it during printer setup a few times ( after I hit 'pause' but not 'cancel job')I've lost DWC connection twice last week on a Maestro-ethernet with 12864 LCD. (*)
It would be cool to write a daemon.g job, which checks for interrupted connections ( WiFi, ethernet and LCD/PanelDue) and calls pause -macro. But I guess that would trigger too when I close the DWC window. @chrishamm or @OwenD is there a way to detect a real connection lost error?
*) RRF3.3b2 and DWC 3.3b -
@kingofthegeeks What firmware and DWC version?
When this happens is DWC completely disconnected from the Duet? Are you able to reload the page?
If this is a Duet Wifi is the blue LED on the module still lit up?
Can you provide the results of M122?
-
I can reload the page, everything seems to be reported as expected with regard to positioning, tool and temps but there is no job specific data available such as time to completion or layer data etc.
Board: Duet 3 MB6HC (MB6HC)
DSF Version: 3.2.2
Firmware: RepRapFirmware for Duet 3 MB6HC 3.2.2 (2021-02-11)M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2.2 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956L2-G43S8-6JTDG-3S86Q-KB3QF
Used output buffers: 1 of 40 (11 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 62576 of which 152 recycled
Never used RAM 146316, free system stack 120 words
Tasks: Linux(ready,75) HEAT(blocked,272) CanReceiv(blocked,809) CanSender(blocked,335) CanClock(blocked,352) TMC(blocked,17) MAIN(running,1203) IDLE(ready,19)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 29:47:21 ago, cause: software
Last software reset at 2021-04-09 09:12, reason: User, GCodes spinning, available RAM 146416, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 53.3, current 55.6, max 58.1
Supply voltage: min 23.6, current 23.7, max 23.7, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0
Driver 0: position 16765, ok, reads 57299, writes 29 timeouts 0, SG min/max 0/402
Driver 1: position 5172, ok, reads 57300, writes 29 timeouts 0, SG min/max 0/1023
Driver 2: position 57831, ok, reads 57300, writes 29 timeouts 0, SG min/max 0/1023
Driver 3: position 0, ok, reads 57300, writes 29 timeouts 0, SG min/max 0/1023
Driver 4: position 0, standstill, reads 57318, writes 11 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 57318, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2021-04-10 14:59:56
Slowest loop: 250.71ms; fastest: 0.03ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 276356ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 1266272, completed moves 1266266, 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 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.2
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP* is doing "M122" in state(s) 0
Telnet is idle in state(s) 0
File* is doing "G1 X207.841003 Y51.576000 E30.824800" 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 1660960, send timeouts 0, received 1344545, lost 0, longest wait 2ms for reply type 6049, free buffers 48
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 1ms ago
RX/TX seq numbers: 18689/18689
SPI underruns 13, overruns 0
Number of disconnects: 0, IAP RAM available 0x2c8a8
Buffer RX/TX: 2784/216-4080
=== Duet Control Server ===
Duet Control Server v3.2.2
File:
Buffered code: G1 X207.841 Y51.576 E30.8248
Buffered code: G1 X207.350 Y51.547 E30.8338
Buffered code: G1 X207.248 Y51.547 E30.8357
Buffered code: G1 X181.543 Y77.252 E31.5007
Buffered code: G1 X181.543 Y76.630 E31.5121
Buffered code: G1 X206.626 Y51.547 E32.1610
Buffered code: G1 X206.003 Y51.547 E32.1724
Buffered code: G1 X181.543 Y76.008 E32.8052
Buffered code: G1 X181.543 Y75.386 E32.8165
Buffered code: G1 X205.352 Y51.576 E33.4325
Buffered code: G1 X204.691 Y51.615 E33.4446
Buffered code: G1 X181.543 Y74.763 E34.0435
Buffered code: G1 X181.543 Y74.141 E34.0549
Buffered code: G1 X204.009 Y51.674 E34.6361
Buffered code: G1 X203.303 Y51.758 E34.6491
Buffered code: G1 X181.543 Y73.519 E35.2120
Buffered code: G1 X181.543 Y72.897 E35.2234
Buffered code: G1 X202.580 Y51.859 E35.7677
Buffered code: G1 X201.822 Y51.995 E35.7818
Buffered code: G1 X181.543 Y72.274 E36.3064
Buffered code: G1 X181.543 Y72.036 E36.3107
Buffered code: G1 X181.651 Y71.544 E36.3200
Buffered code: G1 X201.041 Y52.153 E36.8216
Buffered code: G1 X200.221 Y52.352 E36.8370
Buffered code: G1 X181.851 Y70.721 E37.3123
Buffered code: G1 X182.085 Y69.865 E37.3285
Buffered code: G1 X199.359 Y52.592 E37.7754
Buffered code: G1 X198.463 Y52.865 E37.7925
Buffered code: G1 X182.380 Y68.948 E38.2086
Buffered code: G1 X182.635 Y68.194 E38.2232
Buffered code: G1 X182.719 Y67.987 E38.2272
Buffered code: G1 X197.478 Y53.228 E38.6091
==> 1532 bytes
Code buffer space: 2568
Configured SPI speed: 8000000 Hz
Full transfers per second: 42.34
Maximum length of RX/TX data transfers: 2796/1400
File /opt/dsf/sd/gcodes/2554-028 v1.gcode is selected, processing -
@phaedrux
As for disconnecting, I am unsure, when I set up the print and started it everything appeared to be working fine, when I returned a couple hours later there was no job specific data. I really appreciate the attention to the matter but its not a critical thing for me.Thank you.
-
@kingofthegeeks said in DWC intermittently stops tracking job data:
I can reload the page, everything seems to be reported as expected with regard to positioning, tool and temps but there is no job specific data available such as time to completion or layer data etc.
It sounds like DWC tab has been slept or something and the data for the layers etc isn't being captured during that time.
