3.5B1 2209 in spread cycle reporting stalling

moth4017

Firmware: RepRapFirmware for Duet 3 Mini 5+ 3.5beta1 (2022-12-23)
Duet WiFi Server Version: 1.27

If my motors are in spreadcycle should they be reporting a stall?
datasheet for the 2209 I don't think stall detection is valid in spreadcycle mode....

just check while printing, M569 P0.0
Drive 0 runs forwards, active low enable, timing fast, mode spreadCycle, ccr 0x00000, toff 0, tblank 0, hstart/hend/hdec 0/0/0, pos 24

1/21/2023, 9:42:52 PM Warning: Driver 0 stalled at Z height 7.55

Driver 0 is the A motor of a core X/Y

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5beta1 (2022-12-23 18:25:34) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 3R9YY-6T9RL-D65J0-40KMN-2UW2Z-RHYT0
Used output buffers: 3 of 40 (40 max)
=== RTOS ===
Static ram: 102208
Dynamic ram: 117360 of which 108 recycled
Never used RAM 17980, free system stack 112 words
Tasks: NETWORK(notifyWait,13.6%,206) HEAT(notifyWait,0.0%,321) Move(notifyWait,2.1%,261) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,325) CanClock(delaying,0.0%,334) TMC(notifyWait,1.3%,71) MAIN(running,82.1%,411) IDLE(ready,0.1%,30) AIN(delaying,0.8%,263), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 02:53:20 ago, cause: software
Last software reset at 2023-01-21 19:16, reason: User, GCodes spinning, available RAM 17776, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
MCU revision 3, ADC conversions started 10400187, completed 10400187, timed out 0, errs 0
Step timer max interval 1479
MCU temperature: min 36.6, current 40.8, max 41.7
Supply voltage: min 23.7, current 23.8, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/12, heap memory allocated/used/recyclable 2048/1308/1068, gc cycles 2
Events: 0 queued, 0 completed
Driver 0: ok, SG min 0, read errors 0, write errors 0, ifcnt 99, reads 25834, writes 21, timeouts 0, DMA errors 0, CC errors 0
Driver 1: ok, SG min 0, read errors 0, write errors 0, ifcnt 100, reads 25833, writes 22, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 54, reads 25855, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 3: ok, SG min 0, read errors 0, write errors 0, ifcnt 103, reads 25852, writes 3, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 32, reads 25841, writes 15, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 0, read errors 0, write errors 0, ifcnt 32, reads 25840, writes 15, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 0, read errors 0, write errors 0, ifcnt 31, reads 25839, writes 15, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x72
Date/time: 2023-01-21 22:09:25
Cache data hit count 4294967295
Slowest loop: 148.78ms; fastest: 0.07ms
=== Storage ===
Free file entries: 8
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 4.8ms, write time 139.5ms, max retries 0
=== Move ===
DMs created 83, segments created 50, maxWait 84429ms, bed compensation in use: none, comp offset 0.000
next step interrupt due in 107 ticks, enabled
=== DDARing 0 ===
Scheduled moves 67719, completed 67679, hiccups 0, stepErrors 0, LaErrors 0, Underruns [227, 0, 0], CDDA state 3
=== DDARing 1 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters 2 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.1
Heater 1 is on, I-accum = 0.8
=== 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 X48.384 Y45.385 F21000" 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, sync state 1
Queue2 is idle in state(s) 0
Q0 segments left 1, axes/extruders owned 0x0000807
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== Filament sensors ===
Extruder 0 sensor: ok
=== CAN ===
Messages queued 28514, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 15841/0/0
Tx timeouts 0,0,15841,0,0,12673 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 243.12ms; fastest: 0.06ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
= WiFi =
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 10
WiFi firmware version 1.27
WiFi MAC address f0:08:d1:02:a1:0b
WiFi Vcc 3.34, reset reason Power up
WiFi flash size 2097152, free heap 26440
WiFi IP address 192.168.0.19
WiFi signal strength -56dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

dc42

@moth4017 that is indeed unusual! Did it happen just once, or has it repeated? Did the print look normal?

The datasheet reads "StallGuard4 is optimized for operation with StealthChop, its predecessor StallGuard2 works with SpreadCycle". That phraseology suggests that although StallGuard4 is intended to work best in stealthChop mode, it may work in other modes too.

moth4017

@dc42

hi Prints look normal but this happens very often ,

1/30/2023, 7:48:50 PM Warning: Driver 0 stalled at Z height 2.30

dc42

@moth4017 did you deliberately enable stall detection during printing on your M915 commands? You can enable stall detection for homing without enabling stall detection during printing too.

moth4017

@dc42
Not sure i may have miss understood the disabling of stall detection..
i do this to disable it

;revert back
echo "after revert back"
M915 P0.0 S128 F0 R1 H550 ; Configure Z-Axis Stall Detection
M915 P0.1 S128 F0 R1 H550 ; Configure Z-Axis Stall Detection
M913 X100 Y100 ; Reset motor current %
M569 P0.0 S1 D2 ; reset motors back to spread cycle,
M569 P0.1 S1 D2 ; reset motors back to spread cycle,
M569 P0.0 ; Check status in console
M569 P0.1 ; Check status in console

but from your comments i may be incorrect, how do you disable it?

dc42

@moth4017 just don't enable reporting of stalls in the first place. I'm guessing that you use R1 in the M915 command that sets up stall detection for homing. Use R0 there instead.