Movement halted because of step timing [version 3.6.0-beta.1]

[OwenD]

Just had this error occur again.
It's not 100% repeatable as I've had it fail twice on the same print (with two firmware versions) but print successfully the next try.
Both failures were 5-6 hours into the print.

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.6.0-beta.1 (2024-09-24 10:07:04) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917NK-F2MS4-7J1DA-3S86T-TZTWD
Used output buffers: 10 of 26 (26 max)
=== RTOS ===
Static ram: 23360
Dynamic ram: 71876 of which 12 recycled
Never used RAM 8860, free system stack 100 words
Tasks: NETWORK(2,nWait 6,15.7%,181) ACCEL(6,nWait 5,0.0%,345) HEAT(3,nWait 5,0.1%,307) Move(4,invalid,3.6%,266) MAIN(1,running,80.1%,630) IDLE(0,ready,0.5%,29), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 09:14:16 ago, cause: software
Last software reset at 2024-09-22 17:49, reason: User, Gcodes spinning, available RAM 22200, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x1c
Aux0 errors 0,0,0
MCU temperature: min 19.6, current 26.3, max 26.7
Supply voltage: min 0.4, current 24.2, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/22, heap memory allocated/used/recyclable 2048/596/212, gc cycles 945
Events: 0 queued, 0 completed
Date/time: 2024-09-28 16:07:45
Slowest loop: 1122.06ms; fastest: 0.10ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 8
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 13.0ms, write time 417.1ms, max retries 0
=== Move ===
Segments created 582, maxWait 3825401ms, bed comp in use: mesh, height map offset 0.000, hiccups added 0 (0.00ms), max steps late 1, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 8937.00/8893/0.97 7099.00/7144/-0.16 48408.00/48408/0.00
no step interrupt scheduled
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min 201
Driver 2: standstill, SG min 0
Driver 3: standstill, SG min 0
Driver 4: standstill, SG min 228
Driver 5: 
Driver 6: 
Driver 7: 
Driver 8: 
Driver 9: 
Driver 10: 
Driver 11: 
=== DDARing 0 ===
Scheduled moves 2520037, completed 2520035, LaErrors 0, Underruns [21, 0, 0]
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.3
Heater 1 is on, I-accum = 0.3
=== 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) 3
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 doing "G4 S2" in state(s) 0 0, running macro
Autopause is idle in state(s) 0
Q0 segments left 9
Code queue 0 is empty
=== Filament sensors ===
check 107327487 clear 16019414
Extruder 0 sensor: ok
=== Network ===
Slowest loop: 1253.54ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(4) 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, notrdy 0, noresp 0
Firmware version 2.1.0
MAC address bc:dd:c2:89:a0:bb
Module reset reason: Power up, Vcc 3.38, flash size 4194304, free heap 40588
WiFi IP address 192.168.1.163
Signal strength -41dBm, channel 6, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

EDIT
One difference this time is that when I shut the power off, no resurrect.g was created, so it looks like I've lost this print.

[dc42]

@OwenD thanks for your report. Please provide your config.g file. If you were using input shaping different from whatever is set n the config.g file, then please tell me what M593 command you used.

[OwenD]

@dc42
I have attached the config.g and the other macros called.
Also the filament config.g as that is where I am setting pressure advance if that's relevant.

config(ABS).g
set_max_speeds.g
config.g
setInputShaping.g
config-override.g
daemon.g

[dc42]

@OwenD thanks. I've identified a cause of Code 3 errors and I am currently testing a fix.

[Alva]

the same ocurred to me but it happened when i was experimenting with the second motion system. While the machine was printing , i wanted to move the unused axes. i have trigerred a flag in daemon.g to select the next motion system and move W axes and machine started moving to a different place and stopped. and the machine is still in printing state

[dc42]

@Alva please try beta 2 which includes a fix for a cause of Code 3 halts.

[Alva]

@dc42 I have tried beta2 and same error happened. I think you are already working on it. I have another topic on multiple motion system active now. Thank you .