Duet crashes just after starting
-
Hi, just having some issues since today. Running Duet 2 with deux 5 with RRF 3.3 (voron 2.4). Loaded a file to print, and after some lines it just resets itself. Tried second time, again, and looks to me on the same spot. I made a new file (SS) and uploaded. Then after starting the file, the machine resets right away without doing anything.
Tried a smaller file, and that worked ok. But no changes on SS. This is the M122:
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later + DueX5
Board ID: 0JD0M-9P6M2-NWNS4-7J1D2-3S86S-TB1MM
Used output buffers: 3 of 24 (11 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 82620 of which 0 recycled
Never used RAM 7920, free system stack 188 words
Tasks: NETWORK(ready,9.7%,252) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,340) DUEX(notifyWait,0.0%,24) MAIN(running,87.4%,441) IDLE(ready,2.8%,29), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:26 ago, cause: software
Last software reset at 2021-08-02 21:22, reason: HardFault unaligned, none spinning, available RAM 7712, slot 0
Software reset code 0x4072 HFSR 0x40000000 CFSR 0x01000000 ICSR 0x0041f803 BFAR 0xe000ed38 SP 0x200031e8 Task NETW Freestk 352 ok
Stack: a5a5a5a9 20009610 200034a8 00448f13 ffffffff 004064db 004060d8 810e0000 200034a8 20006e88 200034a8 004110cd 20003230 200198fd 00000026 00000002 004748a0 00000000 00000004 ffffa5a5 00000000 004748d0 20006e88 00406de5 20006e88 004712af 00448f13
Error status: 0x00
Step timer max interval 0
MCU temperature: min 23.2, current 23.9, max 24.1
Supply voltage: min 24.1, current 24.2, max 24.5, 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-02 21:23:20
Cache data hit count 988430184
Slowest loop: 3.95ms; fastest: 0.18ms
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 2.1ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, 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
Heater 1 is on, I-accum = 0.0
=== 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 1, 2.23 reads/min
=== Network ===
Slowest loop: 15.45ms; fastest: 0.00ms
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 0
WiFi firmware version 1.26
WiFi MAC address f4:cf:a2:ea:56:7f
WiFi Vcc 3.38, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25040
WiFi IP address 192.168.2.38
WiFi signal strength -66dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
I thought maybe a bad SD card, but M20 and M21 without a problem. I can not found what error it is.
Thanks in advance for helping!
Marc
- WiFi -
-
@marcfischer said in Duet crashes just after starting:
Last reset 00:00:26 ago, cause: software
Last software reset at 2021-08-02 21:22, reason: HardFault unaligned, none spinning, available RAM 7712, slot 0
Software reset code 0x4072 HFSR 0x40000000 CFSR 0x01000000 ICSR 0x0041f803 BFAR 0xe000ed38 SP 0x200031e8 Task NETW Freestk 352 ok
Stack: a5a5a5a9 20009610 200034a8 00448f13 ffffffff 004064db 004060d8 810e0000 200034a8 20006e88 200034a8 004110cd 20003230 200198fd 00000026 00000002 004748a0 00000000 00000004 ffffa5a5 00000000 004748d0 20006e88 00406de5 20006e88 004712af 00448f13Thanks for your report. Please can you start the board and let it crash a few more times and see if the section of the M122 report I have reproduced above is consistent, except of course for the "Last software reset at" date/time. If it is consistent then that suggests a firmware bug, which I will investigate.
Are you using a lot of variables?
-
Ok.
First:
Last software reset at 2021-08-02 22:20, reason: HardFault unaligned, none spinning, available RAM 7712, slot 1
Software reset code 0x4072 HFSR 0x40000000 CFSR 0x01000000 ICSR 0x0041f803 BFAR 0xe000ed38 SP 0x200031e8 Task NETW Freestk 352 ok
Stack: a5a5a5a9 20009610 200034a8 00448f13 ffffffff 004064db 004060d8 810e0000 00463640 21070000 200034a8 004110cd 20003230 200198fd 00000026 00000002 00000000 00000000 00000004 ffffa5a5 200031b0 004748d0 20007fa8 00406de5 20007fa8 004712af 00448f13Second:
Last software reset at 2021-08-02 22:21, reason: HardFault unaligned, none spinning, available RAM 7712, slot 2
Software reset code 0x4072 HFSR 0x40000000 CFSR 0x01000000 ICSR 0x0041f803 BFAR 0xe000ed38 SP 0x200031e8 Task NETW Freestk 352 ok
Stack: a5a5a5a9 20009610 200034a8 00448f13 ffffffff 004064db 004060d8 810e0000 200034a8 20007318 200034a8 004110cd 20003230 200198fd 00000026 00000002 004748a0 00000000 00000004 ffffa5a5 00000000 004748d0 20007318 00406de5 20007318 004712af 00448f13Third:
Last software reset at 2021-08-02 22:23, reason: HardFault unaligned, none spinning, available RAM 7712, slot 0
Software reset code 0x4072 HFSR 0x40000000 CFSR 0x01000000 ICSR 0x0041f803 BFAR 0xe000ed38 SP 0x200031e8 Task NETW Freestk 352 ok
Stack: a5a5a5a9 20009610 200034a8 00448f13 ffffffff 004064db 004060d8 810e0000 00448f26 010e0000 200034a8 004110cd 20003230 200198fd 00000026 00000002 00411168 00000000 00000004 ffffa5a5 00000000 004748d0 20007d60 00406de5 20007d60 004712af 00448f13Fourth:
Last software reset at 2021-08-02 22:24, reason: HardFault unaligned, none spinning, available RAM 7712, slot 1
Software reset code 0x4072 HFSR 0x40000000 CFSR 0x01000000 ICSR 0x0041f803 BFAR 0xe000ed38 SP 0x200031e8 Task NETW Freestk 352 ok
Stack: a5a5a5a9 20009610 200034a8 00448f13 ffffffff 004064db 004060d8 810e0000 200079f0 000000cb ffffffff 00411145 00406df4 61060000 00000026 00000002 b5ddd98d 00000000 00000004 ffffa5a5 3f800000 004748d0 20007318 00406de5 20007318 004712af 00448f13 -
@marcfischer thanks, that's consistent enough. I'm looking into it.
-
@dc42 That is one file that crashes right away (blue2). It seems from a certain point, because the first file (blue1) that this happend, it printed 1-2 minutes. It whas the same, only saved again in SS. I did look into the gcode, nothing unusual. And I thought maybe size, but on Saterday i printed a 66mb file. These to that giving the error are 33mb. And the small one that printed whas 7mb without issues. Only change from saterday file whas black filament to blue, so a different extrusion multiplier.
-
@marcfischer are you using any macros that use global variables?
-
@dc42 you mean like print_start and speed_printing/speed_probing? yes, those
-
@marcfischer please share those macros.
-
Print_start:
; Start a print V2.1661
;G29 S1
M220 S100 ; reset speed multiplier
M221 S100 ; reset extruder factor to 100%
M290 R0 S0 ; clear babystepping
G10 P0 S235 ; set temperatureM83 ; set extruder to relative mode
G21 ; set units to mmT0 ; select tool 0
G32 ; level the gantry while everything is hot
G29 S1 ; Load previously probed bed mesh (optional, use only if you know your bed is warped)
;M98 P"/macros/print_scripts/goto_bed_center.g"
G28 Z ; Final z height adjustG1 X10 Y30 Z1 F5000 ; move z up little to prevent scratching of surface
G92 E0 ; reset extruder
G1 X10 Y30 Z0.2 F5000.0 ; move to start-line position
G1 X10 Y200.0 Z0.2 F1500.0 E15 ; draw 1st line
G1 E-0.05 F3600 ; quick retract
G1 Z5 ; go away from bed because of temperature
G92 E0 ; reset extruder
G21 ; set units to millimeters
G90 ; use absolute coordinates
M83 ; use relative distances for extrusionsetup_printing:
; called to set up current, speed & accel for printing moves
M566 X500 Y500 Z60 E8000 ; Set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z3000 E15000 ; Set maximum speeds (mm/min)
M201 X2000 Y2000 Z250 E2000 ; Set maximum accelerations (mm/s^2)
M204 P1200 T2000 ; Set printing acceleration and travel accelerations
M913 X100 Y100 Z100 ; restore current to 100%setup_probing:
M566 X900 Y900 Z20 E3600 ; Set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z3000 E5000 ; Set maximum speeds (mm/min)
M201 X2000 Y2000 Z100 E800 ; Set maximum accelerations (mm/s^2)
M913 X60 Y60 Z40 ; Set reduced current for probing/homing to reduce damageFirst file (Blue1) does probing, starts printing and resets after 1-2 minutes (tested twice, stopped at the same place)
Second file (Blue2) resets right away after i start it. -
@marcfischer are you using a daemon.g file?
-
g-code blue 1:
M486 T32
; plater:{"center":[174.804136,148.969664,0.000000],"boundingbox_center":[174.804136,148.969664,9.000084],"boundingbox_size":[205.643462,186.200349,18.000168]}M140 S100 ; set bed temperature
G10 P0 R235 ; sets the standby temperature
;TYPE:Custom
M98 P"/macros/print_scripts/print_start.g"
G21 ; set units to millimeters
G90 ; use absolute coordinates
M83 ; use relative distances for extrusion
G10 P0 S235 ; set temperature
M116 ; wait for temperature to be reached
M190 S100 ; set bed temperature and wait for it to be reached
;LAYER_CHANGE
;Z:0.2
;HEIGHT:0.2
; 0.2mm layer, 8 bands 5mm each, total height 40mm
;
G1 Z0.200000 F18000
;AFTER_LAYER_CHANGE
;0.2
G1 E-0.60000 F3000
G1 Z0.800000 F18000
G1 X64.613 Y50.951
G1 Z0.200000
G1 E0.60000 F1800
;TYPE:Skirt
;WIDTH:0.44
G1 F1200G-code blue 2:
M486 T32
; plater:{"center":[174.804136,148.969664,0.000000],"boundingbox_center":[174.804136,148.969664,9.000084],"boundingbox_size":[205.643462,186.200349,18.000168]}M140 S100 ; set bed temperature
G10 P0 R235 ; sets the standby temperature
;TYPE:Custom
M98 P"/macros/print_scripts/print_start.g"
G21 ; set units to millimeters
G90 ; use absolute coordinates
M83 ; use relative distances for extrusion
G10 P0 S235 ; set temperature
M116 ; wait for temperature to be reached
M190 S100 ; set bed temperature and wait for it to be reached
;LAYER_CHANGE
;Z:0.2
;HEIGHT:0.2
; 0.2mm layer, 8 bands 5mm each, total height 40mm
;
G1 Z0.200000 F18000
;AFTER_LAYER_CHANGE
;0.2
G1 E-0.60000 F3000
G1 Z0.800000 F18000
G1 X64.613 Y50.951
G1 Z0.200000
G1 E0.60000 F1800
;TYPE:Skirt
;WIDTH:0.44
G1 F1200etc
-
@marcfischer thanks. There is a known issue with M486 in RRF 3.3 when the number of objects on the build plate is >20. This is fixed in RRF 3.4beta1. We will probably do a 3.3.1 release with this and a few other fixes.
-
-
@dc42 said in Duet crashes just after starting:
@marcfischer thanks. There is a known issue with M486 in RRF 3.3 when the number of objects on the build plate is >20. This is fixed in RRF 3.4beta1. We will probably do a 3.3.1 release with this and a few other fixes.
A, ok! That's why the big saturday print prints without problems, 12h..... only 16 parts.
-
@marcfischer a workaround is to tell your slicer not to generate M486 labels, if you can. RRF doesn't need them if the file includes object labels as comments. Or you could post-process all the M486 lines into comments.
-
Ok, thanks. Weird thing is, they just showed up. But fount it in SuperSlicer:
Print Settings > Output options > Output File > Label Objects. When off, it doesn't make the M486 anymore.
Thnx for all help!