[3.3 RC3] All tools heaters appears to be overpowered

[psychotik2k3]

@alex-cr no they are all different, a bmg clone with nf crazy plus (mosquito clone)
a biqu H2 and a bondtech LGX FF
i got 2 types of thermistor and 3 different configurations for that.
and it's not only a warning as it stopped my tool change in the middle with the code of tpost1.g not finished.

[gloomyandy]

@psychotik2k3 said in [3.3 RC3] All tools heaters appears to be overpowered:
That looks like your board may have reset (so the messages will have been generated when re-reading your config.g file). The M122 is reporting a reset due to an AssertionFailed which I suspect @dc42 may want to take a look at. It may help for you to post your tool change macros.

[psychotik2k3]

@gloomyandy of course here are my files and the complete config.
i launch the torture test macro. and it happened in the middle of the first T1

[1_1622311463966_sys.zip](Uploading 100%) [0_1622311463964_macros.zip](Uploading 100%)

[Phaedrux]

You cannot upload zip files to the forum. Can you upload the .g files directly?

[psychotik2k3]

@phaedrux oh crap... there are a lot of files....

torture_test_tool_change.g
move_square.g
config.g
homez.g homey.g homex.g homeall.g
tpre2.g tpre1.g tpre0.g
tpost2.g tpost1.g tpost0.g
tfree2.g tfree1.g tfree0.g

[psychotik2k3]

@psychotik2k3 i had to rename my macros with a .g to be able to uplaod it. so it's allright that the macro file does not match the M98 exactly

[psychotik2k3]

@dc42 any news about this bug and the bad command on the panel due ?
do you want some debug logs ?

because for now the 3.3 is unusable as i got interruption even for a simple job taht cycle through my 3 tools.

[Phaedrux]

So you're getting bad command errors on the paneldue during prints?

[psychotik2k3]

@phaedrux yes wasn't able to finish my torture_test_tool_change file
or sometimes even when just laucnhing a bed align through the button on the panel due

[Phaedrux]

This has been noted a few times in RRF3. There's something that makes it more sensitive to picking up interference as bad commands, or rather, it used to be rejected and now it's being interpreted as a bad command. In most cases improving the wiring for the Paneldue solved the problem.

Can you show us what your wiring is like for the Panel?

I've also asked DC42 to check the assertion failed error report.

[psychotik2k3]

@phaedrux i do have a cable that's near motor but as i didn't had problem with 3.2 never thought it could be that.
gonna try to rewire elsewhere and wheck if it fixes or not.
an i suppose i have to do the same thing for the can bus wire between my mainboard and my h3c ?

[Phaedrux]

Which paneldue firmware version btw?

[dc42]

@psychotik2k3 please try the new firmware .bin file at https://www.dropbox.com/sh/nmpsl9a3jfsumm5/AAA6adSjEcd1AM_j5_tVberGa?dl=0. I expect this to fix the asssertion failure.

[psychotik2k3]

@dc42 ok i will try that because i rerouted my panel due wires and canbus cable to be away from motor and motor cables and it fixed nothing.
here is the point where the panel due is the closest to a motor/wire motor:

[psychotik2k3]

@dc42 seems better but i still faced one on "home all" after a reset, and i faced a warning message "M9 command is not supported" at the end of a G32 (14:46) initiated from the bed button on the panel due.

and i just have a reset of the whole board in the middle of a movement.
so it seems a little better but still not good.

here is the debug log i have and the M122 for both cards

05/06/2021, 14:53:49	M122 B0
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3RC3+3 (2021-06-04 09:11:55) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956BA-NA3TN-6JTD8-3S86J-1UB2T
Used output buffers: 1 of 40 (20 max)
=== RTOS ===
Static ram: 150896
Dynamic ram: 93376 of which 100 recycled
Never used RAM 109820, free system stack 188 words
Tasks: NETWORK(ready,29.3%,254) ETHERNET(notifyWait,0.1%,124) HEAT(delaying,0.0%,325) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,774) CanSender(notifyWait,0.0%,373) CanClock(delaying,0.0%,349) TMC(notifyWait,7.1%,90) MAIN(running,63.1%,924) IDLE(ready,0.2%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:00:52 ago, cause: software
Last software reset at 2021-06-05 14:52, reason: AssertionFailed, Platform spinning, available RAM 106704, slot 1
Software reset code 0x4120 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0042783c BFAR 0x00000000 SP 0x2045ff8c Task NETW Freestk 66282 ok
Stack: 000002e8 00498a28 0047a2eb 00000000 0047b8e5 187c4844 2042e320 20428338 20421b10 40000002 00000000 e000e000 004781e1 204298d8 00000000 00000000 00473689 00004858 187c484a 10000000 ffffffed 00000000 00f00000 e000e000 c0000000 00000000 0047a285
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 132
MCU temperature: min 40.8, current 41.3, max 41.5
Supply voltage: min 23.4, current 23.7, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, reads 33373, writes 15 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 33373, writes 15 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 33373, writes 15 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 33373, writes 15 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 33378, writes 11 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 33378, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2021-06-05 14:53:48
Slowest loop: 6.43ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.1ms, write time 2.0ms, max retries 0
=== Move ===
DMs created 125, 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 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 2 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is ready with "M122 B0" 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
Code queue is empty.
=== CAN ===
Messages queued 510, send timeouts 0, received 670, lost 0, longest wait 1ms for reply type 6018, peak Tx sync delay 59, free buffers 49 (min 48), ts 265/264/0
=== Network ===
Slowest loop: 2.88ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 0 0 0
Socket states: 5 2 2 2 2 0 0 0

M122 B1
Diagnostics for board 1:
Duet EXP3HC firmware version 3.3RC3 (2021-05-26 13:46:00)
Bootloader ID: not available
Never used RAM 158144, free system stack 4392 words
Tasks: Move(notifyWait,0.0%,160) HEAT(delaying,0.0%,101) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.0%,83) CanClock(notifyWait,0.0%,74) TMC(notifyWait,22.8%,63) MAIN(running,75.7%,303) IDLE(ready,0.0%,40) AIN(delaying,1.4%,263), total 100.0%
Last reset 00:10:05 ago, cause: software
Last software reset time unknown, reason: AssertionFailed, available RAM 159320, slot 0
Software reset code 0x0120 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x20004754 Task HEAT Freestk 142 bad marker
Stack: 00000544 0002ebf8 000261ef 42000400 00022423 2002f020 00000000 2002f038 2000151c 00000000 0001d6c1 0002dde4 0002de9c 0002d4a0 00025035 2000159c 00000000 2002f020 00015609 00000000 000009c4 000009c4 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 00025035
Driver 0: position 0, 424.9 steps/mm,  standstill, reads 45106, writes 23 timeouts 0, SG min/max 0/0, steps req 0 done 0
Driver 1: position 0, 917.4 steps/mm,  standstill, reads 45109, writes 23 timeouts 0, SG min/max 0/0, steps req 0 done 0
Driver 2: position 0, 400.0 steps/mm,  standstill, reads 45113, writes 23 timeouts 0, SG min/max 0/0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 0/8, peak Rx sync delay 180, resyncs 0/1, no step interrupt scheduled
VIN: 23.8V, V12: 12.2V
MCU temperature: min 36.5C, current 36.7C, max 37.1C
Ticks since heat task active 61, ADC conversions started 605593, completed 605593, timed out 0, errs 0
Last sensors broadcast 0x0000000e found 3 66 ticks ago, loop time 0
CAN messages queued 7384, send timeouts 0, received 5562, lost 0, free buffers 37, min 37, error reg 210000
dup 0, oos 0/0/0/0, bm 0, wbm 0

2021-06-05 14:43:58 [info] Event logging started at level debug
2021-06-05 14:43:58 [info] Running: Duet 3 MB6HC v1.01 or later: 3.3RC3+3 (2021-06-04 09:11:54)
2021-06-05 14:44:55 [debug] X homed: true  Y Homed: true
2021-06-05 14:44:55 [debug] Homing Z axis
2021-06-05 14:45:17 [debug] {"err":-1}

2021-06-05 14:45:17 [debug] {"err":-1}

2021-06-05 14:45:17 [debug] {"err":-1}

2021-06-05 14:45:17 [debug] {"err":-1}

2021-06-05 14:45:17 [debug] {"err":-1}

2021-06-05 14:45:17 [debug] {"err":-1}

2021-06-05 14:45:17 [debug] {"err":-1}

2021-06-05 14:45:17 [debug] {"err":-1}

2021-06-05 14:45:17 [debug] {"err":-1}

2021-06-05 14:45:17 [debug] {"err":-1}

2021-06-05 14:45:17 [debug] {"err":-1}

2021-06-05 14:45:17 [debug] {"err":-1}

2021-06-05 14:45:17 [debug] {"err":-1}

2021-06-05 14:45:17 [debug] {"err":-1}

2021-06-05 14:45:17 [debug] {"err":-1}

2021-06-05 14:45:17 [debug] {"err":-1}

2021-06-05 14:45:17 [debug] {"err":-1}

2021-06-05 14:45:17 [debug] {"err":-1}

2021-06-05 14:45:17 [debug] {"err":-1}

2021-06-05 14:45:31 [debug] G32 bed probe heights: 0.023, mean 0.023, deviation from mean 0.000
2021-06-05 14:46:04 [warn] Leadscrew adjustments made: -0.021 0.081, points used 2, (mean, deviation) before (0.030, 0.032) after (-0.000, 0.000)
2021-06-05 14:46:04 [debug] Leadscrew adjustments made: -0.021 0.081, points used 2, (mean, deviation) before (0.030, 0.032) after (-0.000, 0.000)
2021-06-05 14:46:04 [debug] {"err":-1}

2021-06-05 14:46:04 [debug] {"err":-1}

2021-06-05 14:46:04 [debug] {"err":-1}

2021-06-05 14:46:04 [debug] {"err":-1}

2021-06-05 14:46:04 [debug] {"err":-1}

2021-06-05 14:46:04 [debug] {"err":-1}

2021-06-05 14:46:04 [debug] {"err":-1}

2021-06-05 14:46:04 [debug] {"err":-1}

2021-06-05 14:46:04 [debug] {"err":-1}

2021-06-05 14:46:04 [debug] {"err":-1}

2021-06-05 14:46:04 [debug] {"err":-1}

2021-06-05 14:46:04 [debug] {"err":-1}

2021-06-05 14:46:04 [debug] {"err":-1}

2021-06-05 14:46:04 [debug] {"err":-1}

2021-06-05 14:46:05 [warn] Warning: M9: Command is not supported
2021-06-05 14:51:02 [debug] Writing to file: /sys/SetTool.g
2021-06-05 14:51:35 [debug] X homed: true  Y Homed: true
2021-06-05 14:51:35 [debug] Homing Z axis
2021-06-05 14:51:56 [debug] {"err":-1}

2021-06-05 14:51:56 [debug] {"err":-1}

2021-06-05 14:51:56 [debug] {"err":-1}

2021-06-05 14:51:56 [debug] {"err":-1}

2021-06-05 14:51:56 [debug] {"err":-1}

2021-06-05 14:51:56 [debug] {"err":-1}

2021-06-05 14:51:56 [debug] {"err":-1}

2021-06-05 14:51:56 [debug] {"err":-1}

2021-06-05 14:51:56 [debug] {"err":-1}

2021-06-05 14:51:56 [debug] {"err":-1}

2021-06-05 14:51:56 [debug] {"err":-1}

2021-06-05 14:51:56 [debug] {"err":-1}

2021-06-05 14:51:56 [debug] {"err":-1}

2021-06-05 14:51:56 [debug] {"err":-1}

2021-06-05 14:51:56 [debug] {"err":-1}

2021-06-05 14:51:56 [debug] {"err":-1}

2021-06-05 14:51:56 [debug] {"err":-1}

2021-06-05 14:52:07 [debug] Writing to file: /sys/SetTool.g
2021-06-05 14:52:15 [debug] iteration: 0
2021-06-05 14:52:20 [debug] Writing to file: /sys/SetTool.g
2021-06-05 14:52:42 [debug] Writing to file: /sys/SetTool.g
2021-06-05 14:53:18 [info] Event logging started at level debug
2021-06-05 14:53:18 [info] Running: Duet 3 MB6HC v1.01 or later: 3.3RC3+3 (2021-06-04 09:11:54)
2021-06-05 14:53:26 [info] Event logging stopped

[dc42]

@psychotik2k3 thanks. The M122 B1 report shows that the EXP3HC reset 10 minutes before you generated the report. Was that board already running 3.3RC3 at that time?

PS - I've put new main board firmware at https://www.dropbox.com/sh/nmpsl9a3jfsumm5/AAA6adSjEcd1AM_j5_tVberGa?dl=0 to fix the cause of the main board reset.

PPS - I've also put new EXP3HC firmware at the same location, in case a fix in it is relevant to the assertion failure.

[psychotik2k3]

@dc42 thanks i gonna try that. i think the board was resetted 10 minutes ago by me on a general abort. but yes it was already in RC3.
i get back to 3.2.2 to do some tests so i go back to this new rc3+1

[psychotik2k3]

@dc42 ok just get back from 3.2.2 to your 3.3 rc3+1, updated dwc, then sdiap then mb6hc, then H3C. power off and on.
jsut after power up here are my M122 for the boards

05/06/2021, 18:18:43	M122 B0
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3RC3+4 (2021-06-05 16:20:17) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956BA-NA3TN-6JTD8-3S86J-1UB2T
Used output buffers: 3 of 40 (20 max)
=== RTOS ===
Static ram: 150896
Dynamic ram: 93272 of which 112 recycled
Never used RAM 109912, free system stack 200 words
Tasks: NETWORK(ready,29.1%,266) ETHERNET(notifyWait,0.1%,124) HEAT(delaying,0.0%,331) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,799) CanSender(notifyWait,0.0%,373) CanClock(delaying,0.0%,340) TMC(notifyWait,7.2%,93) MAIN(running,63.4%,924) IDLE(ready,0.1%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:01:51 ago, cause: power up
Last software reset details not available
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 130
MCU temperature: min 39.0, current 43.4, max 43.5
Supply voltage: min 23.4, current 23.7, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, reads 32474, writes 15 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 32474, writes 15 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 32474, writes 15 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 32474, writes 15 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 32478, writes 11 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 32479, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2021-06-05 18:18:43
Slowest loop: 3.71ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, 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 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is ready with "M122 B0" 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
Code queue is empty.
=== CAN ===
Messages queued 1035, send timeouts 0, received 1366, lost 0, longest wait 1ms for reply type 6042, peak Tx sync delay 277, free buffers 49 (min 48), ts 557/556/0
=== Network ===
Slowest loop: 2.99ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0

	M122 B1
Diagnostics for board 1:
Duet EXP3HC firmware version 3.3RC3+1 (2021-05-29 10:22:51)
Bootloader ID: not available
Never used RAM 158144, free system stack 4400 words
Tasks: Move(notifyWait,0.0%,160) HEAT(delaying,0.0%,117) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.0%,83) CanClock(notifyWait,0.0%,74) TMC(notifyWait,22.8%,63) MAIN(running,75.7%,303) IDLE(ready,0.0%,40) AIN(delaying,1.4%,263), total 100.0%
Last reset 00:02:17 ago, cause: power up
Last software reset time unknown, reason: AssertionFailed, available RAM 159320, slot 0
Software reset code 0x0120 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x20004754 Task HEAT Freestk 142 bad marker
Stack: 00000544 0002ebf8 000261ef 42000400 00022423 2002f020 00000000 2002f038 2000151c 00000000 0001d6c1 0002dde4 0002de9c 0002d4a0 00025035 2000159c 00000000 2002f020 00015609 00000000 000009c4 000009c4 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 00025035
Driver 0: position 0, 424.9 steps/mm,  standstill, reads 44381, writes 17 timeouts 0, SG min/max 0/0, steps req 0 done 0
Driver 1: position 0, 917.4 steps/mm,  standstill, reads 44383, writes 17 timeouts 0, SG min/max 0/0, steps req 0 done 0
Driver 2: position 0, 400.0 steps/mm,  standstill, reads 44387, writes 17 timeouts 0, SG min/max 0/0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 0/7, peak Rx sync delay 178, resyncs 0/0, no step interrupt scheduled
VIN: 23.8V, V12: 12.2V
MCU temperature: min 37.3C, current 37.8C, max 37.9C
Ticks since heat task active 216, ADC conversions started 137304, completed 137303, timed out 0, errs 0
Last sensors broadcast 0x0000000e found 3 221 ticks ago, loop time 0
CAN messages queued 1707, send timeouts 0, received 1274, lost 0, free buffers 37, min 37, error reg 110000
dup 0, oos 0/0/0/0, bm 0, wbm 0

but after that i faced a bad command just at the end of my home all once the home is finished , i was able to reproduce the bad command if i do some stuffs movement tool change etc and if i do a home all again.
here is the error and the home all gcode:

Homeall.g

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Thu May 13 2021 17:38:36 GMT+0200 (heure d’été d’Europe centrale)
G91                    ; relative positioning
M98 P"retractprobe.g" 
G1 H2 Z5 F6000         ; lift Z relative to current position



G1 H1 X-358 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 X5 F6000       ; go back a few mm
G1 H1 X-358 F360  ; move slowly to X axis endstop once more (second pass)
G1 X179 F6000     ; go to the middle

G1 H1 Y369 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 Y-5 F6000     ; go back a few mm
G1 H1 Y369 F360  ; move slowly to Y axis endstop once more (second pass)
G1 Y-50 F6000     ; go back a 50 mm to leave belts

G90                    ; absolute positioning
M98 P"homez.g" 
; Uncomment the following lines to lift Z after probing
;G91                   ; relative positioning
;G1 Z5 F100            ; lift Z relative to current position
;G90                   ; absolute positioning

HomeZ.g

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Thu May 13 2021 17:38:36 GMT+0200 (heure d’été d’Europe centrale)
M98 P"retractprobe.g"                                                       ; force a retract in case of restart when pin deployed
echo "X homed:", (move.axes[0].homed=true), " Y Homed:", (move.axes[1].homed=true)
if (move.axes[0].homed=false ) 
	echo "homing X axis"
	M98 P"homex.g"
if (move.axes[1].homed=false ) 
	echo "homing Y axis"
	M98 P"homey.g"
echo "Homing Z axis"
M400
G91                    ; relative positioning
G1 H2 Z5 F6000         ; lift Z relative to current position
G90                    ; absolute positioning
 ; go to middle of bed
G1 X{155 - sensors.probes[0].offsets[0]} Y{155 - sensors.probes[0].offsets[1]} F6000
M558 F250 			   ; Set the probing speed
G30
M558 F30 			   ; Set the probing speed
G30

; Uncomment the following lines to lift Z after probing
G91                   ; relative positioning
G1 Z5 F100            ; lift Z relative to current position
G90                   ; absolute positioning

[psychotik2k3]

@dc42 But the good news is taht the board didn't reset itself at all, i was able to perform 4 times my torture test while i couldn't finish even one before.
So yes i validate the assertion that reset the board fix.

M122 B1
Diagnostics for board 1:
Duet EXP3HC firmware version 3.3RC3+1 (2021-05-29 10:22:51)
Bootloader ID: not available
Never used RAM 158144, free system stack 4392 words
Tasks: Move(notifyWait,0.0%,160) HEAT(delaying,0.0%,88) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.0%,83) CanClock(notifyWait,0.0%,74) TMC(notifyWait,22.8%,63) MAIN(running,75.7%,303) IDLE(ready,0.0%,40) AIN(delaying,1.4%,263), total 100.0%
Last reset 00:30:51 ago, cause: power up
Last software reset time unknown, reason: AssertionFailed, available RAM 159320, slot 0
Software reset code 0x0120 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x20004754 Task HEAT Freestk 142 bad marker
Stack: 00000544 0002ebf8 000261ef 42000400 00022423 2002f020 00000000 2002f038 2000151c 00000000 0001d6c1 0002dde4 0002de9c 0002d4a0 00025035 2000159c 00000000 2002f020 00015609 00000000 000009c4 000009c4 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 00025035
Driver 0: position 0, 424.9 steps/mm,  standstill, reads 14312, writes 0 timeouts 0, SG min/max not available, steps req 0 done 0
Driver 1: position 0, 917.4 steps/mm,  standstill, reads 14311, writes 0 timeouts 0, SG min/max not available, steps req 0 done 0
Driver 2: position 0, 400.0 steps/mm,  standstill, reads 14310, writes 0 timeouts 0, SG min/max not available, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 0/8, peak Rx sync delay 180, resyncs 0/0, no step interrupt scheduled
VIN: 23.8V, V12: 12.2V
MCU temperature: min 37.3C, current 37.8C, max 38.4C
Ticks since heat task active 229, ADC conversions started 1851316, completed 1851316, timed out 0, errs 0
Last sensors broadcast 0x0000000e found 3 234 ticks ago, loop time 0
CAN messages queued 20737, send timeouts 0, received 15594, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0

[dc42]

@psychotik2k3 thanks. Please post the result of M122 for the main board after you have that "Bad command" message.