[3.6.0.Beta.1] Halted due to step timing error

Notepad

HI all,

Simple error during a regular print about 20/25 minutes in

Error: Movement halted because a step timing error occurred (code 3). Please reset the controller.
Error: Existing: start=1789869067 length=8828, new: start=1789876874, overlap=1021 time now=1789871627

M122 Report

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: 0JD2M-9F8TA-GJ4TD-6J1D6-3SD6P-16PG6
Used output buffers: 11 of 26 (24 max)
=== RTOS ===
Static ram: 23360
Dynamic ram: 66884 of which 0 recycled
Never used RAM 11944, free system stack 100 words
Tasks: NETWORK(2,ready,14.7%,181) HEAT(3,nWait 5,0.1%,307) Move(4,invalid,0.5%,266) MAIN(2,running,84.7%,713) IDLE(0,ready,0.0%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 27:19:22 ago, cause: power up
Last software reset at 2024-09-01 17:47, reason: User, Gcodes spinning, available RAM 30728, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 20.1, current 30.4, max 32.1
Supply voltage: min 24.5, current 24.9, max 25.5, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/816/768, gc cycles 0
Events: 0 queued, 0 completed
Date/time: 2024-11-10 18:19:10
Slowest loop: 376.85ms; fastest: 0.11ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 44.5ms, write time 118.3ms, max retries 0
=== Move ===
Segments created 662, maxWait 60410311ms, bed comp in use: mesh, height map offset 0.000, hiccups added 42 (1.25ms), max steps late 1, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 34135.00/33905/0.92 3194.00/2900/0.16 1881.00/1885/-0.81
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 18362, completed 18332, LaErrors 0, Underruns [5, 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.2
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Movement locks held by null
HTTP is ready with "m122#" in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X233.739 Y193.061" 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
Q0 segments left 1
Code queue 0 is empty
=== Network ===
Slowest loop: 667.84ms; fastest: 0.00ms
Responder states: HTTP(4) HTTP(0) HTTP(4) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 5, noresp 1
Firmware version 2.1.0
MAC address a4:e5:7c:03:da:81
Module reset reason: Hardware watchdog, Vcc 3.40, flash size 2097152, free heap 42392
WiFi IP address 192.168.1.197
Signal strength -52dBm, channel 6, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 3 5 3 0 0 0 0 0

config.g
printfile_PETG_1h6m.gcode

droftarts

@Notepad One for @dc42.

(Along with these ones: https://forum.duet3d.com/search?in=posts&term=Halted+due+to+step+timing+error&matchWords=all)

Ian

Notepad

@droftarts
Not to worry, just logging incase and of the information is helpful.

dc42

@Notepad thanks for your report. I fixed a cause of Code 3 halts in 3.6beta2. Please upgrade to that version if you haven't already. There are updated post-beta2 binaries for some boards at https://www.dropbox.com/scl/fo/kaxbpbsyq2lxbae4tmzpk/AAPVUAh6CO_FMO-cG9ttX6U?rlkey=f0aesppc8d2p7bzwwi2s1jayo&dl=0.

Notepad

@dc42 Good to know, Ill deploy it to the farm and see if anything pings up an error!