Missing Steps - Cant Print SpreadCycle StealthChop tuning help

fulg

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

More generally: is anyone else apart from @carcamerarig still having this issue, using this firmware?

Initially I could also reproduce the issue at will. I won't be able to confirm for a couple of weeks as I no longer have a working Mini5+ to test with (amazingly my replacement was dead on arrival, this is being handled separately by @T3P3Tony I believe).

This will of course be one of my first tests once I get a working board in my hands again.

oc_geek

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

Would you be able to tell if there was a problem if you air-printed a few cm above the bed, to avoid the risk of nozzle hits?

Loaded the Beta 3.3 beta 2+2 as per your indication

spreadcycle forced (D2)
mesh active

it apperas to be working fine
i made two prints: one 1st layer and 4 corners prints, no issues of sort

thanks

oc_geek

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

This will of course be one of my first tests once I get a working board in my hands again.

We all hope it will be history by then

dc42

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

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

Would you be able to tell if there was a problem if you air-printed a few cm above the bed, to avoid the risk of nozzle hits?

Loaded the Beta 3.32+2 as per your indication

spreadcycle forced (D2)

mesh active

it apperas to be working fine
i made two prints: one 1st layer and 4 corners prints, no issues of sort

Thanks for the report! It may be that fixing the stepper driver comms timeout errors has fixed this issue.

I have just added a new M569.2 command to RRF so that if this issue still occurs, we can read the actual values of the stepper driver registers.

carcamerarig

@dc42 Fairly productive day with Ian using the new fw as you know, we couldn't replicate the bangs (large travel bangs causing layer shifts) and Ian explained the mini bangs during infill are the switchovers (these never caused layer shifts, mini bangs was just how described them) Had some fun and games with homing but I think we've got something like with maybe just a bit of fine tuning.
Need to check through the config later / tomorrow and see if I can rattle off a couple of prints, fingers crossed no bangs I did mention yesterday under the 2+2 fw I couldn't get it to bang air printing. Only just back home so ill update later / tomorrow.

Ian and Dave thanks for the support both.

droftarts

@carcamerarig Yes, good day! Can you share a copy of your config.g and homeall.g? I forgot to get a copy, and I think it contains a good example of stealthchop tuning.

Ian

SputnikOC3d

@droftarts - any chance of elaborating on the mods and changes and focus of how to sort this ?

What did we discover was happening that was corrected ?

carcamerarig

@droftarts The fruits of todays efforts.

; 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 D3 V0                             ; Drive 0: X Axis
M569 P0.1 S0 D3 V0                             ; Drive 1: Y Axis
M569 P0.2 S0 D3 V0                             ; Drive 2:  Z Axis
M569 P0.3 S0 D3 V0                             ; Drive 3: E Axis
M569 P0.4 S0 D3 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 X18000.00 Y18000.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 X2 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  MOVED TO HOMEALL.G
;M915 Y S15 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 S0 ; 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 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" 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 B0						; 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 - MOVED TO HOMEALL.G
; M17
; G4 P150
; G1 X2 Y2 Z2 F2000 	
; 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

; homeall.g
; called to home all axes

M400
M18

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


; StealthCop calibration
M17
G4 P150
G91
G1 H2 X2 Y2 Z2 F2000 	
G90
G4 S1

M913 X80 Y80 Z100 ; set X Y Z motors to 50% of their normal current

G91                     ; relative positioning
G1 H2 Z5 F800          ; lift Z relative to current position
G1 H1 X255 F3600 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H1 Y-225 F3600 ; move quickly to X and Y axis endstops and stop there (first pass)
G90

M913 X100 Y100 Z100 ; set X Y Z motors to 100% of their normal current

G1 X104 Y100 F3800 ; put head over the centre of the bed, or wherever you want to probe
G30 ; lower head, stop when probe triggered and set Z to trigger height

carcamerarig

@droftarts Could you post links with a short description to explain how we configured the stall detection, sensor less homing and the trinamic flowchart. The way you explained it made more sense than the dozuki.l and I think many would understand it better.

droftarts

@sputnikoc3d We spent a large part of the day testing @carcamerarig Mini 5+ setup. I was able to reproduce the 'small bangs' he talked about, by setting the changeover from stealthchop to spreadcycle to around 32mm/s, and it was particularly noticeable on gyroid fill sections of the test print, just like his video. If set to one or the other mode in config.g, by using M569 D(2 or 3) parameter, it stayed in the set mode and did not bang (was not using stall homing at this point, so did not need to change M569 parameters after power on). I was unable to reproduce the large bang in either mode with the latest firmware (14/4), or in 3.2.2. I ran out of time to test 3.3b2, but have set up my machine to try it out when I get the chance.

Also tested movement with bed mesh on, and with high jerk (900mm/min or 15mm/s) but didn’t push acceleration, which was set at 1500mm/s^2.

I recommended and setup for him to use stealthchop all the time, as the printer was happy to run at up to 300mm/s in stealthchop. I spent some time setting up what I regard as a good stealthchop tuning series of commands, and tuning the stall homing, which was pretty finicky to get right, and I'm still not 100% confident with.

I moved the M915 stall setup to homeall.g, and the stealthchop tuning commands (see posted homeall.g). It follows the recommendations from the Trinamic datasheet; see page 35 and 36 here https://www.trinamic.com/fileadmin/assets/Products/ICs_Documents/TMC2209_Datasheet_V103.pdf#page35
If anyone has more questions about this, please do ask, though it may be a couple of days before I get back to you.

I have set up my printer now with 24V and motors that are very similar in spec to the LDO 0.9 motors. I ran a quick test in stealthchop, with the latest firmware (14/4) and found motors quiet and no banging. In our testing today with the latest firmware, we had no driver errors reported by M122.

Kind of annoying we couldn’t replicate the big bangs today, but maybe switching to an older 3.3b2 firmware will provoke it.

If anyone wants me to test a different setup eg with stealthchop/spreadcycle changeover, please let me know.

Any other questions, please ask and I’ll get back to you when I can; I’m a busy family man, as @carcamerarig experienced today!

Ian

oc_geek

This post is deleted!

droftarts

@oc_geek please post config.g. Looks like you have a low changeover speed to spreadcycle, does it mostly print in spreadcycle?

Ian

oc_geek

This post is deleted!

oc_geek

@droftarts something broken my config... deleting post...

Apology ... i realize the drivers went back to stealthchop.... damn

droftarts

@oc_geek nope, standstill is in stealthchop, changeover is at 0.5mm/s. From your M569 report:

mode stealthChop, ccr 0x00053, toff 3, tblank 0, tpwmthrs 2000 (0.5 mm/sec)

That’s still a changeover. What motors do you have? Please just post your config, hard to find it on a phone in a thread that is so long.

Ian

droftarts

@oc_geek However, a low changeover speed should still work, just be quiet when not moving. I tested that as well, yesterday, couldn’t provoke skipping.

Ian

droftarts

@oc_geek do you change the mode after config.g is run? @dc42 is not sure that M569 reports the current state of the driver, but the one before. So if you set spreadcycle in config with M569 D2, but switch to stealthchop for stall homing, then back to spreadcycle, M569 may still report the stealthchop mode. I didn’t get a chance yesterday to check this, instead sent command to set mode twice, just in case.

Ian

dc42

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

@oc_geek do you change the mode after config.g is run? @dc42 is not sure that M569 reports the current state of the driver, but the one before.

I have verified that M569 does report the correct state, at least in the firmware at https://www.dropbox.com/sh/dupd9u1xppr1om5/AADYg4guuj2n8LJokVqtK-C7a?dl=0.

oc_geek

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

@oc_geek do you change the mode after config.g is run?

Ian

No i don't.
I had force spread-cycle in config.g (or to say i did but it got messed up...) via M569 D2
I now restated it in config.g...
will continue trying that mode and report if anything happens (hope not)

I have a Voron 2.4, it doesn't run any stall homing thing...

thanks

Argo

@droftarts

So it does look like the main issue was solved with the new beta FW.
Interesting that he needs V2 in his config to put the drivers into StealthChop. With my Mini5+ StealthChop mode is by default on and I do not have to set any “V” parameter.
Still I’m curious why this hasn’t been in issue with my Mini5+ as we have quite similar Prusa Styles printer’s.
Maybe revision of the MCU? I remember having a skipping extruder with 3.3b2 which after flashing and compiling firmwares back and forth wasn’t reproducible anymore. During that time I also had timeouts but the fact that I could not reproduce it was annoying from a debugging standpoint.
I’m also glad you confirmed the capabilities of TMC2209s StealthChop (300 mm/s). Here and there you can hear voices that assume it’s only usable for low speeds but for belt driven 3D printer’s it’s well beyond what we need and what will also produce decent prints in terms of ringing.

Nevertheless I’m glad we have a working firmware version now. I also will continue testing the LDO 0.9 motors with the new FW version but that’s maybe worth a new thread then?