3.5.1 - 'Error: Pop(): stack underflow on Aux'
-
@omtek Another series of errors, this time using the PanelDue to put the tool into standby.
Six errors in the console in DWC, along with a message on the PanelDue. The printer was idle at the time (I was changing filament).
M122 generated immediately after the error
M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.1 (2024-04-19 14:41:25) running on Duet 3 Mini5plus WiFi (SBC mode) Board ID: NTK2Z-J196U-D65J0-40KMN-1V03Z-ZJMGF Used output buffers: 1 of 40 (40 max) === RTOS === Static ram: 103232 Dynamic ram: 108140 of which 208 recycled Never used RAM 26116, free system stack 120 words Tasks: SBC(2,ready,25.2%,313) HEAT(3,nWait 6,0.5%,326) Move(4,nWait 6,38.2%,241) CanReceiv(6,nWait 1,0.8%,774) CanSender(5,nWait 7,2.5%,327) CanClock(7,delaying,0.1%,348) TMC(4,nWait 6,18.7%,68) MAIN(2,running,3.1%,595) IDLE(0,ready,0.2%,30) AIN(4,delaying,10.7%,256), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 10:23:35 ago, cause: software Last software reset at 2024-05-02 23:14, reason: User, none spinning, available RAM 26452, slot 1 Software reset code 0x6013 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task SBC Freestk 0 n/a Error status: 0x04 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 37417259, completed 37417257, timed out 0, errs 0 MCU temperature: min 29.8, current 30.4, max 54.6 Supply voltage: min 24.3, current 24.3, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/9, heap memory allocated/used/recyclable 2048/1252/1100, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 88, reads 58510, writes 31, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 86, reads 58510, writes 31, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 86, reads 58511, writes 30, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 87, reads 58510, writes 30, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 89, reads 58510, writes 31, timeouts 0, DMA errors 0, CC errors 0 Driver 5: standstill, SG min 0, read errors 0, write errors 1, ifcnt 32, reads 58531, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 6: standstill, SG min 0, read errors 0, write errors 1, ifcnt 32, reads 58530, writes 10, timeouts 0, DMA errors 0, CC errors 0 Date/time: 2024-05-03 09:37:42 Cache data hit count 4294967295 Slowest loop: 301.99ms; fastest: 0.09ms === Storage === Free file entries: 20 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, segments created 36, maxWait 7801823ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 === DDARing 0 === Scheduled moves 2738422, completed 2738422, hiccups 0, stepErrors 0, LaErrors 1, Underruns [2, 0, 10], CDDA state -1 === DDARing 1 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.2 === GCodes === Movement locks held by null, 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 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 0, axes/extruders owned 0x0000000 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 3055271, received 1048884, lost 0, errs 0, boc 0 Longest wait 6ms for reply type 6033, peak Tx sync delay 441, free buffers 26 (min 24), ts 187079/187078/0 Tx timeouts 0,0,0,0,0,0 === SBC interface === Transfer state: 5, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 58463/58463 SPI underruns 0, overruns 0 State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x0d344 Buffer RX/TX: 0/0-0, open files: 0 === Duet Control Server === Duet Control Server version 3.5.1 (2024-04-19 16:30:56, 32-bit) HTTP+Executed: > Executing M122 Code buffer space: 4096 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0 Full transfers per second: 38.35, max time between full transfers: 106.2ms, max pin wait times: 73.8ms/5.7ms Codes per second: 5.43 Maximum length of RX/TX data transfers: 4441/7656
I was going to downgrade the PanelDue firmware to rc8 to see if that changed anything, but I see that PanelDue 3.5.0 was released yesterday so I'm going to try upgrading to that to see if that resolves this.
-
@omtek whats in your pause.g?
-
pause.g
M83 ; relative extruder moves G1 E-10 F3600 ; retract 10mm of filament G91 ; relative positioning G1 Z5 F360 ; lift Z by 5mm G90 ; absolute positioning G1 X150 Y280 F6000 ; go to X150 Y280
EDIT: I forgot to add that the error occured after updating the PanelDue to 3.5.0 and pausing a print from the PanelDue
.
Here is the M122 from shortly after:
M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.1 (2024-04-19 14:41:25) running on Duet 3 Mini5plus WiFi (SBC mode) Board ID: NTK2Z-J196U-D65J0-40KMN-1V03Z-ZJMGF Used output buffers: 1 of 40 (40 max) === RTOS === Static ram: 103232 Dynamic ram: 108200 of which 260 recycled Never used RAM 26004, free system stack 120 words Tasks: SBC(2,ready,23.2%,294) HEAT(3,nWait 6,0.5%,326) Move(4,nWait 6,5.0%,241) CanReceiv(6,nWait 1,0.8%,774) CanSender(5,nWait 7,0.2%,327) CanClock(7,delaying,0.1%,348) TMC(4,nWait 6,18.2%,68) MAIN(2,running,37.9%,595) IDLE(0,ready,3.7%,30) AIN(4,delaying,10.5%,256), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 12:07:24 ago, cause: software Last software reset at 2024-05-02 23:14, reason: User, none spinning, available RAM 26452, slot 1 Software reset code 0x6013 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task SBC Freestk 0 n/a Error status: 0x04 Aux0 errors 0,1,0 MCU revision 3, ADC conversions started 43646447, completed 43646447, timed out 0, errs 0 MCU temperature: min 29.6, current 46.6, max 52.6 Supply voltage: min 24.3, current 24.3, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/9, heap memory allocated/used/recyclable 2048/180/28, gc cycles 1 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 98, reads 41982, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 96, reads 41981, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 97, reads 41980, writes 11, timeouts 0, DMA errors 0, CC errors 0 Driver 3: ok, SG min 0, read errors 0, write errors 0, ifcnt 100, reads 41979, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 4: ok, SG min 0, read errors 0, write errors 0, ifcnt 99, reads 41982, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 5: standstill, SG min 0, read errors 0, write errors 0, ifcnt 32, reads 41991, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 6: standstill, SG min 0, read errors 0, write errors 0, ifcnt 32, reads 41992, writes 0, timeouts 0, DMA errors 0, CC errors 0 Date/time: 2024-05-03 11:21:31 Cache data hit count 4294967295 Slowest loop: 1102.09ms; fastest: 0.13ms === Storage === Free file entries: 20 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, segments created 36, maxWait 4397359ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00 next step interrupt due in 8 ticks, enabled Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 === DDARing 0 === Scheduled moves 13, completed 11, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 7], CDDA state 3 === DDARing 1 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.2 Heater 1 is on, I-accum = 0.0 === GCodes === Movement locks held by File, null HTTP* is doing "M122" in state(s) 0 Telnet is idle in state(s) 0 File* is doing "G30" in state(s) 0 5 0 0, running macro 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 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 0, axes/extruders owned 0x0000807 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 88125, received 176272, lost 0, errs 0, boc 0 Longest wait 6ms for reply type 6033, peak Tx sync delay 282, free buffers 26 (min 24), ts 31146/31146/0 Tx timeouts 0,0,0,0,0,0 === SBC interface === Transfer state: 5, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 37955/37955 SPI underruns 0, overruns 0 State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x0d344 Buffer RX/TX: 228/424-0, open files: 0 === Duet Control Server === Duet Control Server version 3.5.1 (2024-04-19 16:30:56, 32-bit) HTTP+Executed: > Executing M122 File+ProcessInternally: >>> Macro bed.g: Executing echo "Current rough pass deviation: " ^ move.calibration.initial.deviation >>>> Macro homeall.g: Idle File 0:/gcodes/BalloonFlower_Pot_0.2mm_PLA_VC3_300_11h10m.gcode is selected, processing File: Buffered code: G30 ; home Z by probing the bed Buffered code: M402 Buffered code: M98 P"0:/sys/setMaxSpeed.g" Buffered code: G91 ; relative positioning Buffered code: G1 H2 Z5 F120 ; lift Z relative to current position Buffered code: G90 ; absolute positioning Buffered codes: 196 bytes total >> Doing macro start.g, started by system >> Suspended code: M703 ; load filament-specific config.g >> Suspended code: M98 P"0:/sys/setInputShaping.g" ; pull in input shaping parameters >> Suspended code: G90 ; absolute Positioning >> Suspended code: M83 ; extruder relative mode >> Suspended code: M98 P"0:/sys/setDefaultProbePoints.g" ; reset probe points, just in case >>> Doing macro bed.g, started by G32 ; 3-point bed leveling >>> Suspended code: M401 >>> Suspended code: G30 P0 X20 Y20 Z-99999 ; probe near a leadscrew >>> Suspended code: G30 P1 X170 Y275 Z-99999 ; probe near a leadscrew >>> Suspended code: G30 P2 X280 Y40 Z-99999 S3 ; probe near a leadscrew and calibrate 3 motors >>> Number of flush requests: 1 >>>> Doing macro homeall.g, started by G28 Code buffer space: 3672 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0 Full transfers per second: 38.79, max time between full transfers: 83.1ms, max pin wait times: 65.1ms/3.5ms Codes per second: 0.84 Maximum length of RX/TX data transfers: 4442/7656
-
@omtek i asked in case there were a lot of nested macros in your pause.g
Does it happen everytime when you paus eon PanelDue? Also every happen when you pause from DWC?
-
@T3P3Tony So far, it only seems to happen when using the PanelDue. Just now, I was able to pause and resume a print using DWC, and then again on the PanelDue and got the same behavior both times (on pause, the filament retracts, Z lifts, head moves to the "back" of the printer; on resume, the head returns to the previous position, Z lowers, 10mm of filament is extruded, and the print resumes as normal.)
I've been unable to recreate the initial unresponsiveness I encountered in my initial post and though the error is concerning, it doesn't appear to adversely affect the printers operation.
So far I've had the error occur the following ways:
- Pressing the pause button on the PanelDue
- Putting an at-temperature T0 into standby (turning the icon on the PanelDue from red to yellow, as seen here)
If I can get the error to occur again, is there any specific commands I should run or behavior to watch out for that would tease out more information?
-
-
@T3P3Tony I'm having this issue also, maybe it's related to why my tools are crashing??
-
@gnydick do you have a PanelDue and does it happen when you are pausing?
-
@T3P3Tony I do have PanelDue. It happens at different times, I don't remember exactly what the situation is. I will let you know next time.
-
@T3P3Tony yep, it is when pausing a print.
-
-
Adding a new issue that I happened to notice:
- After the error occurs, I am unable to see any files populated in the SD card section, or the Macro section on the PanelDue.
- Additionally, and likely related, the 'Print Again' button on the PanelDue does nothing (I can hear the beep when I press it, but the printer doesn't repeat the last print). I am able to repeat the print in DWC using the "Status - Print Again" button.
After restarting the print using DWC, I went to pause the printer again. I pressed the pause button on the PanelDue, and nothing happened. I press pause again, and the printer paused. The PanelDue then gave a series of errors that don't show up in the DWC console (M25, because of the second pause command and M32 because of the "Print Again" button from before, I'm guessing).
After cancelling the print, I am able to browse the files in the SD card menu as well as my macros on the PanelDue.
M122 taken after the cancelled print.
m122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.1 (2024-04-19 14:41:25) running on Duet 3 Mini5plus WiFi (SBC mode) Board ID: NTK2Z-J196U-D65J0-40KMN-1V03Z-ZJMGF Used output buffers: 1 of 40 (40 max) === RTOS === Static ram: 103232 Dynamic ram: 108224 of which 236 recycled Never used RAM 25908, free system stack 118 words Tasks: SBC(2,ready,75.6%,294) HEAT(3,nWait 6,5.2%,326) Move(4,nWait 6,88.3%,241) CanReceiv(6,nWait 1,9.0%,772) CanSender(5,nWait 7,5.1%,327) CanClock(7,delaying,1.1%,348) TMC(4,nWait 6,20.7%,68) MAIN(2,running,153.0%,580) IDLE(0,ready,0.2%,30) AIN(4,delaying,121.8%,256), total 480.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 181:48:17 ago, cause: software Last software reset at 2024-05-02 23:14, reason: User, none spinning, available RAM 26452, slot 1 Software reset code 0x6013 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task SBC Freestk 0 n/a Error status: 0x04 Aux0 errors 0,2,0 MCU revision 3, ADC conversions started 654509289, completed 654509288, timed out 0, errs 0 MCU temperature: min 29.9, current 33.6, max 53.9 Supply voltage: min 24.2, current 24.4, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/9, heap memory allocated/used/recyclable 2048/2012/1860, gc cycles 3 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 2, write errors 0, ifcnt 167, reads 61817, writes 29, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 166, reads 61818, writes 29, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 168, reads 61817, writes 30, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 167, reads 61820, writes 28, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 1, write errors 0, ifcnt 166, reads 61817, writes 29, timeouts 0, DMA errors 0, CC errors 0 Driver 5: standstill, SG min 0, read errors 2, write errors 0, ifcnt 32, reads 61845, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 6: standstill, SG min 0, read errors 0, write errors 0, ifcnt 32, reads 61848, writes 0, timeouts 0, DMA errors 0, CC errors 0 Date/time: 2024-05-10 13:02:24 Cache data hit count 4294967295 Slowest loop: 383.36ms; fastest: 0.10ms === Storage === Free file entries: 20 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, segments created 40, maxWait 356176223ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 === DDARing 0 === Scheduled moves 13675, completed 13675, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 20], CDDA state -1 === DDARing 1 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.1 Heater 1 is on, I-accum = 0.0 === GCodes === Movement locks held by null, 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 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 0, axes/extruders owned 0x0000803 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 9346425, received 12112084, lost 0, errs 0, boc 0 Longest wait 2ms for reply type 6013, peak Tx sync delay 546, free buffers 26 (min 25), ts 2162545/2162545/0 Tx timeouts 0,0,0,0,0,0 === SBC interface === Transfer state: 5, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 818/818 SPI underruns 0, overruns 0 State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x0d344 Buffer RX/TX: 0/0-0, open files: 0 === Duet Control Server === Duet Control Server version 3.5.1 (2024-04-19 16:30:56, 32-bit) HTTP+Executed: > Executing M122 Aux: Buffered code: M121 Buffered codes: 24 bytes total Code buffer space: 4096 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0 Full transfers per second: 38.46, max time between full transfers: 172.4ms, max pin wait times: 172.1ms/7.0ms Codes per second: 1.94 Maximum length of RX/TX data transfers: 4499/7656
-
@T3P3Tony I now experienced it after issuing
T-1
. Machine had been freshly rebooted. No pause was issued. The only unusual behavior was thatT0 P0
was issued to load the tool. -
@gnydick So what exactly did you do to produce this situation?
reboot T0 P1 T-1
Did you issue any other commands? How did you issue the commands (from the panelDue?). Is this error repeatable?
-
@gloomyandy there were a couple of commands between the T0 P0 and T-1. I was basically just selecting the tool so I could load more filament.
I'm 99% sure it was all through PanelDue. I will try to reproduce it and let you know.
-
@gnydick If you can get a set of commands that is reproducible and they are issued via the panelDue it might also be useful to check if the same set of commands produces an error if they are issued via the DWC console or perhaps via a USB connection.
-
@gloomyandy It seems like if the command from the PanelDue runs a predefined macro, then it's likely to generate the error message.
So far I've encountered the error when doing the following:
-
Pausing a print (runs pause.g)
-
Putting an active tool into standby (runs the toolchange macros)
What other commands besides those two trigger a predefined macro? The only other one I can think of is 'Cancel', but that won't show up unless the printer is paused.
-
-
@omtek any homing command (G28 X/Y/Z), as well as triggering a bed level (G32) or a bed mesh (G29). Main difference between these and pause/tool change is that pause and tool change may interact with the extruder for retract/unretracts?
-
@oliof You're right. I hadn't considered the homing macros. That's something else to try.
Getting the error when pausing during print seems to occur fairly consistently, as does putting a tool into standby. So far the printer appears to be unaffected, and the only additional error messages I'm getting in DWC appear to be when the PanelDue manages to correct itself and sends the commands that were queued up from the then non-working buttons.
-
@omtek as this is on an SBC setup, @chrishamm could you have a look at this?
Ian
-
@gloomyandy I issue those same commands from DWC all of the time and it hasn't happened.