3.5.0-B3 Reboot in Laser mode
-
M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-beta.3 (2023-04-14 11:27:37) running on Duet WiFi 1.02 or later Board ID: 0JD0M-9P6M2-NW4SS-6JKDD-3S86R-KAZ7L Used output buffers: 1 of 26 (15 max) === RTOS === Static ram: 22192 Dynamic ram: 74716 of which 244 recycled Never used RAM 15992, free system stack 184 words Tasks: NETWORK(nWait,11.0%,238) HEAT(nWait,0.0%,386) Move(nWait,0.0%,364) MAIN(running,80.9%,559) IDLE(ready,8.1%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:00:11 ago, cause: software Last software reset at 2023-06-09 12:21, reason: HardFault bfarValid precise, Gcodes spinning, available RAM 15492, slot 2 Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x0041f803 BFAR 0x6b4bd9b0 SP 0x20003b38 Task Move Freestk 379 ok Stack: 20008908 00000001 00000270 6b4bd450 a5a5a5a5 0042a6e3 0043cee0 a1000000 00000000 00000000 00000000 00000000 3f800000 00000000 00000000 00000000 2000bcf8 00000000 00000001 2000bcfc 2000487c 00000000 00000000 a5a5a5a5 0042a6e3 a5a5a5a5 a5a5a5a5 Error status: 0x00 Aux0 errors 0,0,19 MCU temperature: min 23.8, current 24.1, max 24.4 Supply voltage: min 23.6, current 23.7, max 23.8, 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 Events: 0 queued, 0 completed Driver 0: standstill, SG min n/a Driver 1: standstill, SG min n/a Driver 2: standstill, SG min n/a Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Date/time: 2023-06-09 12:21:49 Cache data hit count 418033720 Slowest loop: 8.31ms; fastest: 0.19ms 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: 12.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 no step interrupt scheduled === DDARing 0 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === GCodes === Movement locks 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 assembling a command 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 Q0 segments left 0 Code queue 0 is empty === Filament sensors === Extruder 0 sensor: ok === Network === Slowest loop: 111.47ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 = WiFi = Network state is active Module is connected to access point Failed messages: pending 0, notready 0, noresp 0 Firmware version 1.27 MAC address bc:ff:4d:45:e0:c1 Module reset reason: Power up, Vcc 3.39, flash size 4194304, free heap 27176 WiFi IP address 10.0.0.120 Signal strength -59dBm, channel 0, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
@cichaczech as we're in the process of releasing 3.5.0-beta4 please can you test it again using that release and report back. If it happens in beta4 then please post a M122 report after the reset again.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Ok, will do.
Thank you. -
@dc42 still the same
M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-beta.4 (2023-06-08 23:39:39) running on Duet WiFi 1.02 or later Board ID: 0JD0M-9P6M2-NW4SS-6JKDD-3S86R-KAZ7L Used output buffers: 1 of 26 (15 max) === RTOS === Static ram: 23236 Dynamic ram: 74836 of which 244 recycled Never used RAM 14828, free system stack 184 words Tasks: NETWORK(2,nWait,12.2%,238) HEAT(3,nWait,0.0%,385) Move(4,nWait,0.0%,364) MAIN(1,running,81.7%,819) IDLE(0,ready,6.1%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:00:15 ago, cause: software Last software reset at 2023-06-09 17:27, reason: HardFault bfarValid precise, Gcodes spinning, available RAM 14328, slot 0 Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x0041f803 BFAR 0x6b4bddd0 SP 0x20003f60 Task Move Freestk 379 ok Stack: 20008d28 00000001 00000270 6b4bd870 a5a5a5a5 004291c3 0043c218 a1000000 00000000 00000000 00000000 00000000 3f800000 00000000 00000000 00000000 2000c168 00000000 00000001 2000c16c 20004bb4 00000000 00000000 a5a5a5a5 004291c3 a5a5a5a5 a5a5a5a5 Error status: 0x00 Aux0 errors 0,0,18 MCU temperature: min 22.9, current 23.5, max 23.6 Supply voltage: min 23.6, current 23.7, max 23.9, 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 Events: 0 queued, 0 completed Driver 0: standstill, SG min n/a Driver 1: standstill, SG min n/a Driver 2: standstill, SG min n/a Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Date/time: 2023-06-09 17:28:13 Cache data hit count 558914657 Slowest loop: 8.27ms; fastest: 0.19ms 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: 12.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, height map offset 0.000, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled === DDARing 0 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === GCodes === Movement locks 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 assembling a command 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 Q0 segments left 0 Code queue 0 is empty === Filament sensors === Extruder 0 sensor: ok === Network === Slowest loop: 111.94ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 = WiFi = Interface state: active Module is connected to access point Failed messages: pending 0, notready 0, noresp 0 Firmware version 1.27 MAC address bc:ff:4d:45:e0:c1 Module reset reason: Power up, Vcc 3.39, flash size 4194304, free heap 27096 WiFi IP address 10.0.0.120 Signal strength -59dBm, channel 0, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
@cichaczech please try again. The stack trace in your M122 report doesn't match the 3.4.0-beta.4 code, so I suspect you were running different firmware when that last reset happened.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Today I tried delete old FW and instal beta4 with BOSSA, but it still keeps rebooting when I try to home it.
For now I am moving back to last stable release
this is my latest M122
=== Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-beta.4 (2023-06-08 23:39:39) running on Duet WiFi 1.02 or later Board ID: 0JD0M-9P6M2-NW4SS-6JKDD-3S86R-KAZ7L Used output buffers: 13 of 26 (20 max) === RTOS === Static ram: 23236 Dynamic ram: 74836 of which 244 recycled Never used RAM 14828, free system stack 186 words Tasks: NETWORK(2,nWait,12.5%,238) HEAT(3,nWait,0.0%,383) Move(4,nWait,0.0%,364) MAIN(1,running,78.8%,819) IDLE(0,ready,8.7%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:00:10 ago, cause: software Last software reset at 2023-06-12 09:11, reason: HardFault bfarValid precise, Gcodes spinning, available RAM 14328, slot 2 Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x0041f803 BFAR 0x6b4bddd0 SP 0x20003f60 Task Move Freestk 379 ok Stack: 20008d28 00000001 00000270 6b4bd870 a5a5a5a5 004291c3 0043c218 a1000000 00000000 00000000 00000000 00000000 3f800000 00000000 00000000 00000000 2000c168 00000000 00000001 2000c16c 20004bb4 00000000 00000000 a5a5a5a5 004291c3 a5a5a5a5 a5a5a5a5 Error status: 0x00 Aux0 errors 0,0,18 MCU temperature: min 22.2, current 22.7, max 23.0 Supply voltage: min 23.7, current 23.7, max 23.9, 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 Events: 0 queued, 0 completed Driver 0: standstill, SG min n/a Driver 1: standstill, SG min n/a Driver 2: standstill, SG min n/a Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Date/time: 2023-06-12 09:11:56 Cache data hit count 397729243 Slowest loop: 9.39ms; fastest: 0.19ms 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: 12.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, height map offset 0.000, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled === DDARing 0 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === GCodes === Movement locks 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 assembling a command 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 Q0 segments left 0 Code queue 0 is empty === Filament sensors === Extruder 0 sensor: ok === Network === Slowest loop: 114.56ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(2) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 3 of 8 = WiFi = Interface state: active Module is connected to access point Failed messages: pending 0, notready 0, noresp 0 Firmware version 2.1beta3 MAC address bc:ff:4d:45:e0:c1 Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 38084 WiFi IP address 10.0.0.120 Signal strength -54dBm, channel 1, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
@cichaczech please can you provide your config.g and homing files, so that I can try to reproduce this.
-
@cichaczech I haven't managed to reproduce the problem, but I believe I have identified the issue. It's specific to laser mode. Please try the Duet 2 firmware binary at https://www.dropbox.com/sh/c4aatfdsejjjab0/AACGuZ4qUBvZz49zxErkhmnWa?dl=0 and see if it resolves the problem.
I think a workaround for this issue using the original 3.5.0-beta4 firmware binary would be to issue a G1 move with an S parameter after switching to laser mode with M452 but before doing the very first real move (i.e. before homing). Even G1 S0 with no other parameters should be sufficient.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Both of your solutions work.
3.5.0-beta4 -> you have to send G1 S0 after switching laser mode
3.5.0-beta4+ -> works normally in laser mode, without any additional commandsThank you.
-
@cichaczech thanks for confirmation! The fix will be included in 3.5.0-rc.1. I'll mark the Github issue I created at https://github.com/Duet3D/RepRapFirmware/issues/869 solved.
