Missing Steps - Cant Print SpreadCycle StealthChop tuning help

carcamerarig

@sputnikoc3d
@sputnikoc3d
I ordered an SKR board yesterday with 2209 steppers to run klipper on, I feel uneasy about all the radio silence if I’m honest... I’m really hoping it gets resolved over the next week or two after which I think I’ll return the mini.

Argo

@sputnikoc3d

Not really reduced. I have a cartesian / bed slinger printer. I could do travel moves up to 200 mm/s but I don't because at those bed speeds I add additional cooling and also it's quite noisy. But doable without losing steps. We do btw almost have the same printer. He has Caribou, I have a Bear.

TMC2209 are a huge upgrade compared to TMC2130 (EINSY). Much less VFA and comparing the print results of 1.8 motors to 0.9 motors are (to me) only visible when making photos with a macro lens. You can also increase your steps to 200/mm and interpolate from 32 microstepping which the TMC2130 can't.

The Mini 5+ can handle 0.9 motors up to 120 mm/s but with much more noise during my tests. That issue I also have with Marlin 2. So it's a general problem with TMC2209 in my opinion.

The problem with the "bangs" and missing steps is a different chapter though and should not happen with 1.8 motors nor with 0.9 motors.

fulg

Hello @droftarts, one interesting data point we seem to have found, the problem is apparently much much more likely to happen if you use bed mesh compensation. Even @oc_geek who was quoted earlier as not having isssues, enabled a bed mesh and instantly started having the same layer shifts issue.

I looked at the start of the thread and @carcamerarig is also using a bed mesh (as shown in his M122 dump). So am I.

So perhaps that is the key to reproduce this issue. Personally I use a 11x11 mesh to correct a 0.1mm variation in my bed (not a lot but more than enough to ruin prints!)...

carcamerarig

@fulg I turned off my mesh bed leveling for a few prints and it’s was a lot worse.

droftarts

Apologies for the lack of updates, mainly because there have been no updates. Thanks for additional information. I’m planning on spending all Thursday looking at this issue (during school holidays I’m only available one day a week), and hopefully @carcamerarig will be joining me for the fun.

@Argo is low jerk high acceleration really the norm? Prusa3D disagrees with you:
https://github.com/prusa3d/Prusa-Firmware/blob/eb4cf1a77f57b0825b72c5209d48fceaa8c0ec58/Firmware/Configuration.h#L424
https://github.com/prusa3d/Prusa-Firmware/blob/eb4cf1a77f57b0825b72c5209d48fceaa8c0ec58/Firmware/variants/1_75mm_MK3S-EINSy10a-E3Dv6full.h#L100
Segmented curves will tend to print slow with low jerk.
Also your stealthchop tuning isn’t right, see page 35 and 36 here https://www.trinamic.com/fileadmin/assets/Products/ICs_Documents/TMC2209_Datasheet_V103.pdf#page35
(If you need more info or an example, let me know and I’ll write it up when I’m at my desk and not on mobile.)

Ian

Argo

@droftarts

Default Prusa slicer profile uses 8 mm/s jerk. But yes, still rather high.

I first stepped over low jerk recommendation in the Duet gcode dictionary.
M593 suggets "High X and Y jerk values reduce the effectiveness of DAA; therefore you should set the X and Y jerk limits only as high as necessary to allow curves to be printed smoothly."

So I did some testing and found 4 mm/s (or 240 mm/min) works very well without having issues with curves.

Also the Klipper input shaper documentation suggests to use low jerk and high acceleration
"If square_corner_velocity parameter was changed, revert it back to 5.0. It is not advised to increase it when using the input shaper because it can cause more smoothing in parts - it is better to use higher acceleration value instead."
https://www.klipper3d.org/Resonance_Compensation.html

What would you suggest to improve the StealthChop tuning procedure?

carcamerarig already told me about your plans. Very nice offer from you I hope you'll find a solution for his issues.

oc_geek

@fulg ...for some reason my account login had issues and i wasn't able to login neither to change password...back now

On my end (and i'm on the THIRD Duet 3 Mini 5+...)

i'm running Stand Alone
Have OMC 0.9 motors (but extruder)
Tried all releases including betas

Always had and have the bangs during prints; was able to "print" but had layer shits on a bunch (3-4) prints (which i attributed at that time to some other cause)
Since a few days i tried to enable mesh. Total disaster ...i started to get 25mm+ layer shifts

I really hope these issue get fixed and the Duet team takes it on cse i think there are severe issues at the moment to be solved... which make the card almsot unusable...

It is good that there is discussion and people contribute but the way this thread is turned... it is like users are doing debugging or finding caveats and work arounds to let things do not break apart.... i honestly think is not the way.... i counted few replies from the Duet team... ok take more time...analyze....test ....but come up with something or people will start moving / looking elsewhere (me included)

dc42

@fulg said in Missing Steps - Cant Print SpreadCycle StealthChop tuning help:

One thing that was suggested to me (outside of this forum) is that I am not doing M17 and G4 P100 before moving motors the first time, reading the docs this seems to say that the required stealthChop/spreadCycle calibration of the TMC2209 will not occur. I would have expected RRF to do this implicitly, but perhaps it does and I am misunderstanding.

RRF does not do this automatically. However, if you are switching to spreadCycle mode then it should not be necessary.

dc42

All who are experiencing the issue of occasional banging/layer shifting during a print, after it has happened please post:

A brief description of what happened, including the axis or axes affected if known
A M122 report
A M569 P# report for each relevant driver number #
Your config.g file

carcamerarig

@dc42 mine are all contained in this thread from the various modes in both standalone and sbc.

Argo

@carcamerarig said in Missing Steps - Cant Print SpreadCycle StealthChop tuning help:

@dc42 mine are all contained in this thread from the various modes in both standalone and sbc.

So he does not have to search for it as the thread has quite exploded:
https://forum.duet3d.com/post/223138

droftarts

@oc_geek thanks for the report. Did the other boards have the same problem?

What firmware versions is everyone using? Did you notice the problem in earlier firmware versions, eg 3.2 betas?

Ian

oc_geek

@droftarts yes they did
on my side i've been in 3.2.2, 3.3 beta 1 and 3.3beta2

I'll post the files that dc42 indicated later (can't now)

Thanks for your support and looking into it. We all appreciate

edit: As a head up... a simple mesh enable (corrections are within +/- 0.05) and movement from e.g. X150 Y290 Z5 to X150 Y5 Z150 causes a tremendous shift in Z (it landed at 60 instead of 150...) it shall not be difficult to reproduce... thanks again

edit: @dc42 as requested including dumps

dc42

@argo said in Missing Steps - Cant Print SpreadCycle StealthChop tuning help:

@carcamerarig said in Missing Steps - Cant Print SpreadCycle StealthChop tuning help:

@dc42 mine are all contained in this thread from the various modes in both standalone and sbc.

So he does not have to search for it as the thread has quite exploded:
https://forum.duet3d.com/post/223138

Thanks!

carcamerarig

Config

; General preferences
G90                                         ; Send absolute coordinates...
M83                                         ; ...but relative extruder moves

; Network
M550 P"Duet Caribou 420"                        	; Set machine name
M552 S1                                     	; Enable network
;*** Access point is configured manually via M587
;M586 P0 S1                                  ; Enable HTTP
;M586 P1 S0                                  ; Disable FTP
;M586 P2 S0                                  ; Disable Telnet
M575 P1 S1 B57600							; Panel Due

; Drive Mappings
M569 P0.0 S0 V0                             ; Drive 0: X Axis
M569 P0.1 S0 V0                             ; Drive 1: Y Axis
M569 P0.2 S0 V0                             ; Drive 2:  Z Axis
M569 P0.3 S0 V0                             ; Drive 3: E Axis
M569 P0.4 S0 V0                             ; Drive 4: E1 used for Z1

; Motor remapping for dual Z and axis Limits
M584 X0 Y1 Z2:4 E3				; two Z motors connected to driver outputs Z and E1
M671 X-37:287 Y0:0 S4			; leadscrews at left (connected to Z) and right (connected to E1) of X axis

; Micrpstepping and Speed
M350 X32 Y32 E16 Z16 I1                     ; Configure microstepping with interpolation
M92 X200.00 Y200.00 Z400.00 E830.00         ; Set steps per mm

; Speeds, Acceleration and Jerk
M566 X900 Y900 Z25.00 E600.00 P1      ; Set maximum instantaneous speed changes (mm/min)
M203 X7500.00 Y7500.00 Z720.00 E1200.00     ; Set maximum speeds (mm/min)
M201 X1500.00 Y1500.00 Z1200.00 E4000.00     ; Set accelerations (mm/s^2)

; Motor currents
M906 X700.00 Y700.00 Z700.00 E700.00 I20    ; Set motor currents (mA) and motor idle factor in percent X,Y,Z=1000/1.414 E=1400/1.414
M84 S30                                     ; Set idle timeout

; Printer geometry
M208 X0:250 Y-4:215 Z-0.5:410               ; Axis Limits
M564 H0							            ; allow unhomed movement

; Endstops for each Axis
M574 X1 S3								 	; Set endstops controlled by motor load detection
M574 Y1 S3                               	; Set endstops controlled by motor load detection

; Stallgaurd Sensitivy
M915 X S-2 F0 H200 R0		                ; Set X axis Sensitivity  
M915 Y S-1 F0 H200 R0		                ; Set y axis Sensitivity 

; Input Shaper
;M593 F58.5 P4 S0.2  ; Input Shaping 3.3/3.4
;M593 F54.26

; Z-Probe Super PINDA
M574 Z1 S2														; Set endstops controlled by probe
M558 P5 C"^io3.in" I1 H1 F500 T4800 A30 S0.004

; Mesh Grid 
M557 X24:221 Y10:195 P8	                         ; Define mesh grid for probing

; Sheets
;G31 P1000 X23 Y5 Z1.730 	                    ; Satin Sheet
G31 P1000 X23 Y5 Z1.91 	  	                  ; Textured Sheet 
;G31 P1000 X23 Y5 Z1.445 					    ; PEI Sheet
;G31 P1000 X23 Y5 Z1.445 					    ; PEI Sheet 0.6 nozzle -10 offset


; Heatbed Heaters and Thermistor Bed 
M308 S0 P"temp0" Y"thermistor" T100000 B4725 C7.060000e-8       ; Set thermistor + ADC parameters for heater 0 Bed
M950 H0 C"out0" T0 Q10					                        ; Creates Bed Heater Qnn PWM frequency in Hz. Valid range: 0-65535, default: 500. (optional) 10hz stopped clicking
M307 H0 R0.273 C345.3 D10.89 S1.00 V23.8						; PID 3.2
M140 H0										                    ; Bed uses Heater 0
M143 H0 S120                                                    ; Set temperature limit for heater 0 to 120C Bed

; HotEnd Heaters and Thermistor HotEnd      
M308 S1 P"temp1" Y"thermistor" T500000 B4725 C1.19622e-7	       	; define E0 temperature sensor e3d
M950 H1 C"out1" T1 						                            ; Create HotEnd Heater
M307 H1 R2.383 C178.5:130.6 D5.32 S1.00 V23.9						; PID
M143 H1 S285                                                    	; Set temperature limit for heater 1 to 285C HotEnd
M302 S185 R185

; Fans
M950 F1 C"out5" Q250				; Creates HOTEND Fan
M106 P1 T45 S235 H1                 ; HOTEND Fan Settings
M950 F0 C"out6" Q100				; Creates PARTS COOLING FAN
M106 P0 H-1                         ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off PARTS COOLING FAN

; Tools
M563 P0 D0 H1 F0                            ; Define tool 0
G10 P0 X0 Y0 Z0                             ; Set tool 0 axis offsets
G10 P0 R0 S0                                ; Set initial tool 0 active and standby temperatures to 0C

; StealthCop calibration
M17
G4 P150
G1 X1 Y1 Z1 	
G4 S2
M84 ; disable motors

; Filament Sensor Logic
M98 P"0:/macros/02_Functions/StartupFilamentSensorCheck"  ; Runout Sensor Logic: Startup with filament = runout sensor active   Startup without filament = autoload active

M569 P0.1
Drive 1 runs in reverse, active low enable, timing fast, mode stealthChop, ccr 0x00053, toff 3, tblank 0, tpwmthrs 0 (inf mm/sec), pwmScaleSum 11, pwmScaleAuto 4, pwmOfsAuto 255, pwmGradAuto 39, pos 68

M569 P0.0
Drive 0 runs in reverse, active low enable, timing fast, mode stealthChop, ccr 0x00053, toff 3, tblank 0, tpwmthrs 0 (inf mm/sec), pwmScaleSum 12, pwmScaleAuto 5, pwmOfsAuto 255, pwmGradAuto 50, pos 764

Pre print M122

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3beta2 running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: Z9NZN-A296U-D65J0-40KM4-LY03Z-ZPQPD
Used output buffers: 3 of 40 (18 max)
=== RTOS ===
Static ram: 99720
Dynamic ram: 106476 of which 24 recycled
Never used RAM 34628, free system stack 112 words
Tasks: NETWORK(ready,227) HEAT(delaying,317) CanReceiv(notifyWait,943) CanSender(notifyWait,358) CanClock(delaying,340) TMC(notifyWait,109) MAIN(running,363) IDLE(ready,20) AIN(delaying,269)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:04:51 ago, cause: power up
Last software reset at 2021-04-08 23:50, reason: User, GCodes spinning, available RAM 34628, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00446000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
Supply voltage: min 0.0, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/782/782, gc cycles 3
Driver 0: position 39400, standstill, SG min/max 0/416, read errors 0, write errors 0, ifcnt 15, reads 41502, writes 15, timeouts 101, DMA errors 0, failedOp 0x6a
Driver 1: position 19000, standstill, SG min/max 0/440, read errors 0, write errors 0, ifcnt 17, reads 41598, writes 17, timeouts 3, DMA errors 0, failedOp 0x01
Driver 2: position 20000, standstill, SG min/max 0/282, read errors 0, write errors 0, ifcnt 16, reads 41602, writes 16, timeouts 0, DMA errors 0
Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 11, reads 41606, writes 11, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, SG min/max 0/284, read errors 0, write errors 0, ifcnt 16, reads 41602, writes 16, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-04-13 10:58:56
Cache data hit count 494597420
Slowest loop: 5.57ms; fastest: 0.07ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 1.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 145592ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 42, completed moves 42, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 4], 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, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle 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.
=== Filament sensors ===
Extruder 0 sensor: ok
=== CAN ===
Messages queued 2640, send timeouts 2636, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 16)
Last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 10.41ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.25beta0
WiFi MAC address f4:cf:a2:6f:e9:78
WiFi Vcc 3.36, reset reason Power up
WiFi flash size 2097152, free heap 24936
WiFi IP address 192.168.1.226
WiFi signal strength -43dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

Post incident M122 (mini bangs during infill

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3beta2 running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: Z9NZN-A296U-D65J0-40KM4-LY03Z-ZPQPD
Used output buffers: 3 of 40 (26 max)
=== RTOS ===
Static ram: 99720
Dynamic ram: 106476 of which 200 recycled
Never used RAM 34452, free system stack 108 words
Tasks: NETWORK(ready,227) HEAT(delaying,293) CanReceiv(notifyWait,943) CanSender(notifyWait,358) CanClock(delaying,340) TMC(delaying,109) MAIN(running,363) IDLE(ready,20) AIN(delaying,260)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:30:14 ago, cause: power up
Last software reset at 2021-04-08 23:50, reason: User, GCodes spinning, available RAM 34628, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00446000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
Supply voltage: min 23.4, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/1076/1022, gc cycles 21
Driver 0: position 32245, ok, SG min/max 0/510, read errors 0, write errors 0, ifcnt 21, reads 6782, writes 6, timeouts 1380, DMA errors 0, failedOp 0x71
Driver 1: position 22305, ok, SG min/max 0/494, read errors 0, write errors 0, ifcnt 23, reads 8094, writes 6, timeouts 67, DMA errors 0, failedOp 0x41
Driver 2: position 582, ok, SG min/max 0/286, read errors 0, write errors 0, ifcnt 21, reads 8139, writes 5, timeouts 23, DMA errors 0, failedOp 0x41
Driver 3: position 0, ok, SG min/max 0/486, read errors 0, write errors 0, ifcnt 13, reads 8148, writes 2, timeouts 18, DMA errors 0, failedOp 0x6a
Driver 4: position 0, ok, SG min/max 0/286, read errors 0, write errors 0, ifcnt 21, reads 8163, writes 5, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-04-13 11:24:19
Cache data hit count 2624084504
Slowest loop: 114.04ms; fastest: 0.09ms
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 90.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 278053ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 8766, completed moves 8726, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 233, 0], CDDA state 3
=== 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, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.5
Heater 1 is on, I-accum = 0.6
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X182.190 Y111.523 E0.01708" 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.
=== Filament sensors ===
Extruder 0 sensor: ok
=== CAN ===
Messages queued 13708, send timeouts 13708, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17)
Last cancelled message type 4514 dest 127
=== Network ===
Slowest loop: 200.28ms; fastest: 0.08ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 1
WiFi firmware version 1.25beta0
WiFi MAC address f4:cf:a2:6f:e9:78
WiFi Vcc 3.36, reset reason Power up
WiFi flash size 2097152, free heap 23248
WiFi IP address 192.168.1.226
WiFi signal strength -40dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

Post travel bang ( large)

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3beta2 running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: Z9NZN-A296U-D65J0-40KM4-LY03Z-ZPQPD
Used output buffers: 3 of 40 (26 max)
=== RTOS ===
Static ram: 99720
Dynamic ram: 106476 of which 200 recycled
Never used RAM 34452, free system stack 108 words
Tasks: NETWORK(ready,225) HEAT(delaying,293) CanReceiv(notifyWait,943) CanSender(notifyWait,358) CanClock(notifyWait,340) TMC(notifyWait,100) MAIN(running,363) IDLE(ready,20) AIN(notifyWait,260)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:43:12 ago, cause: power up
Last software reset at 2021-04-08 23:50, reason: User, GCodes spinning, available RAM 34628, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00446000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
Supply voltage: min 23.4, current 23.5, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/1748/1694, gc cycles 30
Driver 0: position 16627, assumed not present
Driver 1: position 17876, assumed not present
Driver 2: position 1882, ok, SG min/max 0/288, read errors 0, write errors 0, ifcnt 21, reads 38565, writes 0, timeouts 17, DMA errors 0, failedOp 0x6a
Driver 3: position 0, ok, SG min/max 0/498, read errors 0, write errors 0, ifcnt 13, reads 38581, writes 0, timeouts 1, DMA errors 0, failedOp 0x41
Driver 4: position 0, ok, SG min/max 0/228, read errors 0, write errors 0, ifcnt 21, reads 38581, writes 0, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-04-13 11:37:17
Cache data hit count 3697243847
Slowest loop: 76.79ms; fastest: 0.09ms
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 76.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 47674, completed moves 47666, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 603, 0], CDDA state 3
=== 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, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.5
Heater 1 is on, I-accum = 0.6
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 F4800.000" 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.
=== Filament sensors ===
Extruder 0 sensor: ok
=== CAN ===
Messages queued 7006, send timeouts 7006, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17)
Last cancelled message type 4514 dest 127
=== Network ===
Slowest loop: 202.00ms; fastest: 0.08ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 2
WiFi firmware version 1.25beta0
WiFi MAC address f4:cf:a2:6f:e9:78
WiFi Vcc 3.36, reset reason Power up
WiFi flash size 2097152, free heap 23136
WiFi IP address 192.168.1.226
WiFi signal strength -42dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

dc42

@carcamerarig, thanks for that. The M122 report shows a large number of timeouts in the driver status. On the last one, the communication has failed so badly that the firmware has flagged drivers 0 and 1 as "assumed not present". So it's possible that the problem is caused by communication errors between the processor and the stepper drivers.

carcamerarig

@dc42 Does that point to a faulty board or corrupt fw? Im going to Ian's on Thursday is this something he can investigate further, fix or replace the board?

fulg

@dc42 The requested info was already posted but unfortunately everything is scattered about in this thread, so here are direct links:

M122 reports:
https://forum.duet3d.com/post/224293 (only the driver bits)
https://forum.duet3d.com/post/224581

I always see these timeout errors, it is quite worrisome...

Full config + repro file:
https://forum.duet3d.com/post/224661

@droftarts I was running RRF 3.2.2 but upgraded to 3.3b2 to see if it would help, no difference.

Argo

@dc42

I'm in middle of a print and did a M122 report just out curiosity.

Driver 0: position 31835, assumed not present
Driver 1: position 16605, assumed not present
Driver 2: position 23041, assumed not present

But I do not observe bangs or layer shifts.

I did use your "preview" build from this posting: https://forum.duet3d.com/post/225143

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3beta2+1 (2021-04-11 10:20:02) running on Duet 3 Mini5plus Ethernet (standalone mode)
Board ID: ZDWF8-8296U-D65J0-40KMU-J603Z-77MM8
Used output buffers: 3 of 40 (40 max)
=== RTOS ===
Static ram: 100072
Dynamic ram: 103000 of which 176 recycled
Never used RAM 37600, free system stack 100 words
Tasks: NETWORK(ready,204) ETHERNET(notifyWait,557) ACCEL(notifyWait,345) HEAT(delaying,300) CanReceiv(notifyWait,944) CanSender(notifyWait,357) CanClock(notifyWait,332) TMC(notifyWait,99) MAIN(running,312) IDLE(ready,20) AIN(notifyWait,259)
Owned mutexes:
=== Platform ===
Last reset 14:52:29 ago, cause: software
Last software reset at 2021-04-13 00:05, reason: User, GCodes spinning, available RAM 37776, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU revision 3, ADC conversions started 63542814, completed 63542813, timed out 0, errs 0
tnd=0 rnd=0 wrd=0 wtd=0 war=0
Supply voltage: min 22.6, current 23.7, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/610/576, gc cycles 634
Driver 0: position 31835, assumed not present
Driver 1: position 16605, assumed not present
Driver 2: position 23041, assumed not present
Driver 3: position 0, assumed not present
Driver 4: position 0, standstill, SG min/max 0/354, read errors 0, write errors 0, ifcnt 141, reads 59413, writes 0, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-04-13 14:57:52
Cache data hit count 4294967295
Slowest loop: 16.75ms; fastest: 0.09ms
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 14.3ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 112179, completed moves 112166, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
=== 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, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.2
Heater 1 is on, I-accum = 0.8
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X158.218 Y83.922 E0.04566" 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 not empty:
Queued 'M106 S255' for move 112171
Queued 'M106 S216.75' for move 112171
Queued 'M106 S255' for move 112171
Queued 'M106 S216.75' for move 112178
Queued 'M106 S255' for move 112179
5 of 16 codes have been queued.
=== Filament sensors ===
Extruder 0 sensor: ok
=== CAN ===
Messages queued 49339, send timeouts 49339, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17)
Last cancelled message type 4514 dest 127
=== Network ===
Slowest loop: 16.10ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 0 0 0
Socket states: 2 2 2 2 2 0 0 0

M569 P0.0
Drive 0 runs forwards, active low enable, timing fast, mode stealthChop, ccr 0x00053, toff 3, tblank 0, tpwmthrs 0 (inf mm/sec), pwmScaleSum 76, pwmScaleAuto 2, pwmOfsAuto 232, pwmGradAuto 19, pos 612

M569 P0.1
Drive 1 runs in reverse, active low enable, timing fast, mode stealthChop, ccr 0x00053, toff 3, tblank 0, tpwmthrs 0 (inf mm/sec), pwmScaleSum 161, pwmScaleAuto 1, pwmOfsAuto 254, pwmGradAuto 40, pos 190

M569 P0.2
Drive 2 runs forwards, active low enable, timing fast, mode stealthChop, ccr 0x00053, toff 3, tblank 0, tpwmthrs 0 (inf mm/sec), pwmScaleSum 89, pwmScaleAuto 26, pwmOfsAuto 255, pwmGradAuto 52, pos 595

;config.g

; General preferences
G90                                         ; Send absolute coordinates...
M83                                         ; ...but relative extruder moves

; Network
M550 P"Pruset II MK3s"                        	; Set machine name
M552 S1                                     	; Enable network
;*** Access point is configured manually via M587
M586 P0 S1                                  ; Enable HTTP
M586 P1 S0                                  ; Disable FTP
M586 P2 S0                                  ; Disable Telnet
M575 P1 S1 B57600							; Panel Due

; Drive Mappings
M569 P0.0 S1 V0                             ; Drive 0: X Axis
M569 P0.1 S0 V0                             ; Drive 1: Y Axis
M569 P0.2 S1 V0                             ; Drive 2:  Z Axis
M569 P0.3 S1 V0                             ; Drive 3: E Axis
M569 P0.4 S1 V0                             ; Drive 4: E1 used for Z1

; Motor remapping for dual Z and axis Limits
M584 X0 Y1 Z2:4 E3				; two Z motors connected to driver outputs Z and E1
M671 X-37:287 Y0:0 S10			; leadscrews at left (connected to Z) and right (connected to E1) of X axis

; Micrpstepping and Speed
M350 X32 Y32 E16 Z16 I1                     ; Configure microstepping with interpolation
M92 X200.00 Y200.00 Z400.00 E415.00         ; Set steps per mm

; Speeds, Acceleration and Jerk
M566 X240.00 Y240.00 Z25.00 E600.00 P1      ; Set maximum instantaneous speed changes (mm/min)
M203 X7500.00 Y7500.00 Z730.00 E1200.00     ; Set maximum speeds (mm/min)
M201 X2000.00 Y2000.00 Z1200.00 E5000.00     ; Set accelerations (mm/s^2)

; Motor currents
M906 X600.00 Y600.00 Z600.00 E450.00 I20    ; Set motor currents (mA) and motor idle factor in percent
M84 S30                                     ; Set idle timeout

; Printer geometry
M208 X0:250 Y-4:215 Z-0.5:205               ; Axis Limits
M564 H0							            ; allow unhomed movement

; Endstops for each Axis
M574 X1 S3								 	; Set endstops controlled by motor load detection
M574 Y1 S3                               	; Set endstops controlled by motor load detection

; Stallgaurd Sensitivy
M915 X S2 F0 H200 R0		                ; Set X axis Sensitivity  
M915 Y S2 F0 H200 R0		                ; Set y axis Sensitivity 

; Input Shaper and Accelerometer
M955 P0 C"io2.out+io2.in"
M593 F42.6 S0.3

; Z-Probe Super PINDA
M574 Z1 S2                                      	; Set endstops controlled by probe
M558 P5 C"^io3.in" I1 H0.7 F520 T6000 A50 S0.005  	; PINDA 

; Mesh Grid 
M557 X24:233 Y15:195 P8                         ; Define mesh grid for probing

; Sheets
G31 P1000 X23 Y5 Z1.715 	                    ; Satin Sheet
;G31 P1000 X23 Y5 Z1.630 	                    ; Textured Sheet 
;G31 P1000 X23 Y5 Z1.450 					    ; PEI Sheet
;G31 P1000 X23 Y5 Z1.440 					    ; PEI Sheet 0.6 nozzle -10 offset


; Heatbed Heaters and Thermistor Bed 
M308 S0 P"temp0" Y"thermistor" T100000 B4725 C7.060000e-8       ; Set thermistor + ADC parameters for heater 0 Bed
M950 H0 C"out0" T0 Q100					                        ; Creates Bed Heater
M307 H0 R0.276 C365.2 D12.50 S1.00 V24.0 B0						; PID 3.2
M140 H0										                    ; Bed uses Heater 0
M143 H0 S120                                                    ; Set temperature limit for heater 0 to 120C Bed

; HotEnd Heaters and Thermistor HotEnd      
M308 S1 P"temp1" Y"thermistor" T100000 B4725 C7.060000e-8       	; define E0 temperature sensor e3d
M950 H1 C"out1" T1 Q100					                            ; Create HotEnd Heater
M307 H1 R2.301 C162.7:122.2 D7.10 S1.00 V24.3 B0					; PID
M143 H1 S285                                                    	; Set temperature limit for heater 1 to 285C HotEnd
M302 S185 R185

; Fans
M950 F1 C"out5" Q100				; Creates HOTEND Fan
M106 P1 T45 S200 H1                 ; HOTEND Fan Settings
M950 F0 C"out6" Q100				; Creates PARTS COOLING FAN
M106 P0 H-1                         ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off PARTS COOLING FAN

; Tools
M563 P0 D0 H1 F0                            ; Define tool 0
G10 P0 X0 Y0 Z0                             ; Set tool 0 axis offsets
G10 P0 R0 S0                                ; Set initial tool 0 active and standby temperatures to 0C

; StealthCop calibration
M17
G4 P150
G1 X1 Y1 Z1 	
G4 S2
M84 ; disable motors

; Filament Sensor Logic
M98 P"0:/macros/02_Functions/StartupFilamentSensorCheck"  ; Runout Sensor Logic: Startup with filament = runout sensor active   Startup without filament = autoload active

oc_geek

@dc42 it seems the timeouts are a common thing. Everyone i spoke with had those in the drivers report, me included (see files i posted earlier)