3.6.0 B4 threw an error

Aurimas

@dc42 @T3P3Tony Mid print
6HC+1LC for toolhead
printer didn't reset
It was still reporting as "Printing" no actions performed
Errror and M122 outputs below

5/02/2025, 00:01:43	Error: Code 7 move error: info=-5.405e+11, seg: s=4294966906 t=4833 d=-540478439424.00 u=-1.1183e+8 a=0.0000e+0 f=08

Debug from 121: Code 7 move error: info=5.319e+11, seg: s=596 t=4294966310 d=531
Debug from 121: 916193792.00 u=0.0000e+0 a=5.7670e-8 f=18

Code 7 move error: in
Debug from 121: fo=-3.424e+11, seg: s=4294966906 t=4833 d=-342447161344.00 u=-7.
Debug from 121: 0856e+7 a=0.0000e+0 f=18

Code 7 move error: info=-1.219e+11, se
Debug from 121: g: s=4443 t=1721 d=-121943228416.00 u=-7.0856e+7 a=0.0000e+0 f=1
Debug from 121: 8

Code 7 move error: info=-6.753e+10, seg: s=6164 t=953 d=-6752
Debug from 121: 5804032.00 u=-7.0856e+7 a=0.0000e+0 f=18

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.6.0-beta.4 (2025-02-11 09:51:22) running on Duet 3 MB6HC v1.02 or 1.02a (standalone mode)
Board ID: 08DLM-9K6R1-L8MSJ-6JTDD-3S46N-TDW1N
Used output buffers: 1 of 40 (34 max)
=== RTOS ===
Static ram: 137396
Dynamic ram: 128312 of which 0 recycled
Never used RAM 62436, free system stack 108 words
Tasks: NETWORK(1,ready,30.3%,169) ETHERNET(5,nWait 7,0.1%,311) HEAT(3,nWait 6,0.0%,323) Move(4,invalid,1.2%,213) TMC(4,nWait 6,3.1%,341) CanReceiv(6,nWait 1,0.0%,598) CanSender(5,nWait 7,0.1%,325) CanClock(7,delaying,0.0%,348) MAIN(1,running,65.0%,103) IDLE(0,ready,0.0%,29) USBD(3,blocked,0.0%,144), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 15:03:33 ago, cause: power up
Last software reset at 2025-02-24 13:31, reason: User, Gcodes spinning, available RAM 77616, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
=== Storage ===
Free file entries: 19
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 4.0ms, write time 63.4ms, max retries 0
=== Move ===
Segments created 663, maxWait 509874ms, bed comp in use: mesh, height map offset 0.000, hiccups added 0/0 (0.00/354.03ms), max steps late 1, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 20680.00/20359/-1.00 22193.00/21761/-1.00 237834.00/237833/0.76
Next step interrupt due in 243 ticks, disabled
Driver 0: standstill, SG min 0, mspos 1016, reads 29400, writes 1082 timeouts 102
Driver 1: standstill, SG min 0, mspos 488, reads 29409, writes 1073 timeouts 102
Driver 2: standstill, SG min 0, mspos 488, reads 29409, writes 1073 timeouts 102
Driver 3: standstill, SG min 0, mspos 136, reads 29401, writes 1081 timeouts 102
Driver 4: standstill, SG min 0, mspos 888, reads 29401, writes 1081 timeouts 102
Driver 5: standstill, SG min n/a, mspos 8, reads 29426, writes 1056 timeouts 102
Phase step loop runtime (us): min=0, max=225, frequency (Hz): min=476, max=46875
=== DDARing 0 ===
Scheduled moves 2821376, completed 2821317, LaErrors 0, Underruns [0, 0, 0]
Segments left 1, axes/extruders owned 0x80000007, drives owned 0x80000007
Code queue is empty
=== DDARing 1 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
Segments left 0, axes/extruders owned 0x00000000, drives owned 0x00000000
Code queue is empty
=== Heat ===
Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1 -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null, null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X272.16 Y285.153 E.0023" 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
=== CAN ===
Messages queued 3267068, received 1085162, lost 0, ignored 0, errs 1, boc 0
Longest wait 4ms for reply type 6029, peak Tx sync delay 506, free buffers 50 (min 48), ts 256939/256938/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 207.56ms; fastest: 0.03ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 3 of 8
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0
= Ethernet =
Interface state: active
Error counts: 0 0 0 1 0 0
Socket states: 6 6 2 2 2 0 0 0 0
=== WiFi ===
Interface state: disabled
Module is disabled
Failed messages: pending 0, notrdy 0, noresp 0
Socket states: 0 0 0 0 0 0 0 0

dc42

@Aurimas thanks, that's valuable feedback. If it happens again, please post the result of sending M122 B121 too.

Aurimas

@dc42 will do

Adrian52

I just got a stop error too. duet2wifi standalone. First time this has happened with b4.

27/02/2025, 16:12:59 	Error: Code 7 move error: info=-4.970e+10, seg: s=1940 t=2912 d=-49701994496.00 u=-1.7068e+7 a=0.0000e+0 f=18

27/02/2025, 16:16:37 	M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.6.0-beta.4 (2025-02-11 09:50:40) running on Duet WiFi 1.0 or 1.01
Board ID: 08DAM-999TL-MQ4SD-6J9FD-3SJ6J-K593W
Used output buffers: 1 of 26 (24 max)
=== RTOS ===
Static ram: 24016
Dynamic ram: 68004 of which 12 recycled
Never used RAM 17140, free system stack 68 words
Tasks: NETWORK(1,ready,17.1%,183) LASER(5,nWait 6,1.3%,214) HEAT(3,nWait 5,0.1%,328) Move(4,invalid,2.7%,261) MAIN(1,running,78.8%,846) IDLE(0,ready,0.1%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 01:19:58 ago, cause: power up
Last software reset at 2025-02-25 11:50, reason: User, Gcodes spinning, available RAM 26092, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 13.3ms, write time 18.7ms, max retries 0
=== Move ===
Segments created 451, maxWait 685715ms, bed comp in use: none, height map offset 0.000, hiccups added 0/79 (2.63ms), max steps late 1, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 65603.00/65475/-0.92 59572.00/59500/-0.29 67651.00/67588/0.19
No step interrupt scheduled
Driver 0: standstill, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min 0
Driver 3: standstill, SG min 0
Driver 4: standstill, SG min 0
Driver 5: 
Driver 6: 
Driver 7: 
Driver 8: 
Driver 9: 
Driver 10: 
Driver 11: 
=== DDARing 0 ===
Scheduled moves 375305, completed 375265, LaErrors 0, Underruns [0, 0, 0]
Segments left 1
Code queue is empty
=== Heat ===
Bed heaters 0 -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 doing "G1 X-46.241 Y12.008 E.00958" 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
=== Filament sensors ===
Driver 11: pos 0.00, brightness 18, shutter 97, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
=== Network ===
Slowest loop: 203.29ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.2.1
Module reset reason: Turned on by main processor, Vcc 3.38, flash size 4194304, free heap 39440
MAC address 5c:cf:7f:2c:24:6b
IP address 192.168.1.16
Signal strength -48dBm, channel 8, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0code_text

T3P3Tony

@Adrian52 thanks for reporting it. We will have a new build out shortly which h we would like you to test.

dc42

@Adrian52 thanks for your report. Code 7 step timing errors were the last critical error we needed to fix before 3.6.0-rc.1. Thanks to the feedback from @Aurimas I was able to identify the area of code and the bug that is the probable cause of these errors. The data you posted helps confirm that as the cause. We now hope to release rc.1 early next week.