Print aborted after resume
-
@nikscha said in Print aborted after resume:
Weirdly enough, M122 still reports RRF 3.2.2 ....
If it still says 3.2.2 then something didn't get updated correctly.
Can you please share the results of M122?
-
=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus WiFi (SBC mode) Board ID: YD4DK-V296U-D65J0-40KM0-4503Z-HUP34 Used output buffers: 1 of 40 (40 max) === RTOS === Static ram: 98732 Dynamic ram: 95260 of which 48 recycled Never used RAM 51176, free system stack 122 words Tasks: Linux(ready,95) HEAT(blocked,291) CanReceiv(blocked,947) CanSender(blocked,358) CanClock(blocked,362) TMC(blocked,97) MAIN(running,152) IDLE(ready,20) AIN(blocked,260) Owned mutexes: HTTP(MAIN) === Platform === Last reset 07:33:22 ago, cause: software Last software reset at 2021-05-14 11:45, reason: User, GCodes spinning, available RAM 51176, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task Linu Freestk 0 n/a Error status: 0x04 Aux0 errors 0,0,0 Aux1 errors 0,0,0 Supply voltage: min 23.6, current 24.2, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: position 134598, standstill, SG min/max 0/48, read errors 0, write errors 0, ifcnt 123, reads 26797, writes 1, timeouts 20, DMA errors 0, failedOp 0x6a Driver 1: position 134600, standstill, SG min/max 0/50, read errors 0, write errors 0, ifcnt 123, reads 26908, writes 1, timeouts 20, DMA errors 0, failedOp 0x06 Driver 2: position 134602, standstill, SG min/max 0/52, read errors 0, write errors 0, ifcnt 123, reads 26923, writes 1, timeouts 4, DMA errors 0, failedOp 0x01 Driver 3: position 0, standstill, SG min/max 0/510, read errors 0, write errors 0, ifcnt 94, reads 26084, writes 1, timeouts 20, DMA errors 0, failedOp 0x06 Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 71, reads 26928, writes 0, timeouts 0, DMA errors 0 Driver 5: position 0, assumed not present Driver 6: position 0, assumed not present Date/time: 2021-05-14 19:18:59 Cache data hit count 4294967295 Slowest loop: 188.14ms; fastest: 0.08ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 0.0MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 83, maxWait 200ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 150511, completed moves 150511, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 933, 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, chamberHeaters = -1 -1 Heater 0 is on, I-accum = 0.1 Heater 1 is on, I-accum = 0.7 === GCodes === Segments left: 0 Movement lock held by null HTTP* is doing "M122" 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 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 0, running macro Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === CAN === Messages queued 209763, send timeouts 209763, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 16 === SBC interface === State: 4, failed transfers: 0 Last transfer: 1ms ago RX/TX seq numbers: 2931/2931 SPI underruns 0, overruns 0 Number of disconnects: 1, IAP RAM available 0x10eec Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.2.2 Code buffer space: 4096 Configured SPI speed: 8000000 Hz Full transfers per second: 37.52 Maximum length of RX/TX data transfers: 2960/1664 -
Looks like you're up to date on the stable branch, but nothing from unstable has been applied. 3.3 final should be coming soon though.
What is the status of the original problem though?
-
@phaedrux
everything works as expected now, the M226 command now invokes pause.g as expected.And the only thing I changed (that I am aware of) is the switch to the unstable release. When executing apt update/upgrade, files were downloaded and installed as well....
-
@nikscha said in Print aborted after resume:
When executing apt update/upgrade, files were downloaded and installed as well....
Perhaps you were on an older version before and have now updated to the latest stable. I don't think you're on the unstable branch at all, or if you are it hasn't actually updated any of your software as it reports both the firmware and DCS running 3.2.2
-
@phaedrux
But it definitely says unstable release here...
-
Hmm, also says 7 not upgraded.
-
@phaedrux lol! You're right I didn't see that at all.
Do you happen to know how I can force an update? -
Well if things are working now I'd say maybe wait for 3.3 final next week rather than updating to a release candidate unless you really want to do some testing.
If you do, I'd go through the steps for adding the unstable branch again and see if it will update after.
https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Software_Installation
-
@phaedrux will do, thank you for your help I appreciate it!
