Help needed with Duet 3 6hc TMC5160 StealthChop config

danym21 · 11 May 2020, 20:52

yes like I wrote.
all above 119mm/min goes to spreadcycle
also with V34 (110mm/s) parameter in M569.
and I can not understand why, it looks like the V parameter does not realy change the tpwmthrs.
but when I check this with m569 P0 as example it gives me
Drive 0 runs in reverse, active low enable, step timing fast, mode stealthChop, ccr 0x08053, toff 3, tblank 1, hstart/hend/hdec 5/0/0, pos 56, tpwmthrs 34 (110.3 mm/sec) , thigh 200 (18.8 mm/sec)
so it sould be on 110mm/sec and not 2mm (120mm/min) /sec
I have still not understand what the H parameter (thigh 200 (18.8 mm/sec)) means maby someone can explain it.
I have tried higher H and lover H parameter nothing changed for me.
when I search for "stealthchop" in the Forum it looks like some others has the same problem, but not found a solution for.

danym21 · 12 May 2020, 19:17

has some bring StealthChop running on a Duet 3?
when I search here in the forum it looks like only problems with a maestro was fixed the issues with the duet 3 looks all
still open.
has someone the maestro running with RR 3?
@dc42 do you have some tips that I can try or what is wrong with my configuration?

dc42 · 13 May 2020, 12:50

I am not aware of any bugs in this area, but have added this to my list of things to test prior to the 3.01 release of RRF.

danym21 · 13 May 2020, 19:34

@dc42 this means I have nothing wrong in my config?
I was hoping that I have done something wrong.

dc42 · 13 May 2020, 19:37

I don't see anything wrong with your config, and M569 P0 says the threshold speed for changing to spreadCycle should be around 110mm/sec. That speed won't be exactly right because it depends on the accuracy of the 12MHz clock in the TMC5160.

danym21 · 13 May 2020, 19:40

@dc42 ok then I have to wait for your tests and hope we can find a solution.
let me know when I can help here with testing etc.

dc42 · 13 May 2020, 19:54

From my reading of the datasheet, you should always have THIGH < TPWMTHRS. Have you tried setting THIGH to values below 34?

danym21 · 13 May 2020, 19:55

@dc42 said in Help needed with Duet 3 6hc TMC5160 StealthChop config:

THIGH

I think I had done is the H parameter right?
I will try again.

dc42 · 13 May 2020, 19:56

@danym21 said in Help needed with Duet 3 6hc TMC5160 StealthChop config:

@dc42 said in Help needed with Duet 3 6hc TMC5160 StealthChop config:

THIGH

I think I had done is the H parameter right?
I will try again.

Yes. Use M569 with just a P parameter to check that you have set it.

danym21 · 13 May 2020, 20:17

@dc42 I have tried with H10 for X and Y achses (P0.0 and P0.1) nothing changed, StealthChop only works below F119 all above only Spreadcycle from the noise.

M569 P0.0
Drive 0 runs in reverse, active low enable, step timing fast, mode stealthChop, ccr 0x08053, toff 3, tblank 1, hstart/hend/hdec 5/0/0, pos 548, tpwmthrs 34 (110.3 mm/sec), thigh 10 (375.0 mm/sec)
M569 P0.1
Drive 1 runs in reverse, active low enable, step timing fast, mode stealthChop, ccr 0x08053, toff 3, tblank 1, hstart/hend/hdec 5/0/0, pos 884, tpwmthrs 34 (110.3 mm/sec), thigh 10 (375.0 mm/sec)

to be sure also tested :

; Drives
M569 P0.0 S0 D3 V34 H50                            ; physical drive 0 goes forwards D2=Spread cycle (x-achses)
M569 P0.1 S0 D3 V34 H50                            ; physical drive 1 goes forwards D2=Spread cycle (y-achses)

13.5.2020, 22:17:07 	M569 P0.1
Drive 1 runs in reverse, active low enable, step timing fast, mode stealthChop, ccr 0x08053, toff 3, tblank 1, hstart/hend/hdec 5/0/0, pos 972, tpwmthrs 34 (110.3 mm/sec), thigh 50 (75.0 mm/sec)
13.5.2020, 22:17:01 	M569 P0.0
Drive 0 runs in reverse, active low enable, step timing fast, mode stealthChop, ccr 0x08053, toff 3, tblank 1, hstart/hend/hdec 5/0/0, pos 540, tpwmthrs 34 (110.3 mm/sec), thigh 50 (75.0 mm/sec)
13.5.2020, 22:16:07 	G0 X130 Y130 F90
13.5.2020, 22:15:51 	G0 X135 Y135 F90

now also G0 X130 Y130 F90 runs only in SpreadCycle

danym21 · 28 May 2020, 19:16

@dc42 was you able to test?
I have also tried to change the D settings on a test print to hear some changes, but nearly nothing has changed only on D0 (constant off-time)
he goes a little bit louder but not much. D1 (random off-time) is not supported by TMC5160.
can it be that my board is faulty or that the Firmware has a Bug and only shows the corect mode but not send to the stepper drivers?

danym21 · 28 May 2020, 21:29

I have seen the source code "/src/Movement/StepperDrivers/TMC51xx.cpp"

constexpr float SenseResistor = 0.050;

when I right on other firmware´s I use 0.075, can this create a difference?
Is it possible to play with over the M569 command or is it needed to compile new, have not found in the Duet documentation.

cjackson234 · 30 May 2020, 16:25

I'm experiencing the same thing @danym21.

cjackson234 · 2 Jun 2020, 23:17

Are there any updates on this?

danym21 · 3 Jun 2020, 10:19

@cjackson234
still not

dc42 · 3 Jun 2020, 17:55

I'm sorry for the delay. This is still on my list to continue investigating. As it's a noise issue not a functionality issue, it has lower priotity then some others on my list.

Alex_Z · 27 Jun 2020, 13:49

Hello! The same thing on my CoreXY using Duet3. Does anyone have found a solution?

danym21 · 1 Jul 2020, 16:46

no sorry

dc42 · 7 Jan 2020, 17:01

My suspicion is that the issue is not following the tuning sequence specified by Trinamic. In particular, you are supposed to energise the motors, keep them still for a short while (but less than 130ms), then execute a medium speed move such as a homing move. Here is an extract from the datasheet:

Typically, homeall.g does something like this:

G91
G1 H2 Z5 Fxxx
G1 H1 X-400 Fxxx
...

The initial pause at standstill is after powering up the motors is not present. So perhaps this would be better:

G91
G1 H2 Z0.02 Fxxx
G4 P50
G1 H2 Z5
G1 H2 X0.02 Fxxx
G4 P50
G2 H1 X-400

Similarly for Y. The 0.02mm figure should be adjusted so that it is at least one microstep, but preferably not much more than that.

danym21 · 9 Jul 2020, 21:04

@dc42
it looks like it does not help, I have created the following test macro file, but I can´t hear any difference only on still stand after moves I can hear the motors a little bit when Spread cycle (D2) is enabled.
maybe I have done something wrong?

; first test with stealh enabled
M18						   ; disable all motors to reset the stepper drivers
M569 P0.0 S0 D3 V34                                ; physical drive 0 goes forwards D2=Spread cycle (x-achses)
M569 P0.1 S0 D3 V34                                ; physical drive 1 goes forwards D2=Spread cycle (y-achses)
M569 P0.2 S0 D3 V34                                ; physical drive 2 goes backwards D2=Spread cycle (Z1)
M569 P0.3 S0 D3 V34                                ; physical drive 3 goes backwards D2=Spread cycle (Z2)
M569 P0.4 S1 D3 V34                                ; physical drive 4 goes backwards D2=Spread cycle (extruder)
M569 P0.5 R-1                                      ; physical drive 4 goes backwards D2=Spread cycle (empty)
M584 X0.0 Y0.1 Z0.2:0.3 E0.4                       ; Driver 0 For X, 1 for Y, Z=2:3 U=4, Extruder 4
M350 X32 Y32 Z16 E16 I1                            ; configure microstepping with interpolation - working
M92 X400.00 Y400.00 Z400 E412.00                   ; set steps per mm
M566 X300.00 Y300.00 Z24.00 E300.00                ; set maximum instantaneous speed changes (mm/min) from config file thingiverse 
M203 X14000 Y14000 Z4520 E7000                     ; set maximum speeds (mm/min) new test Z800 old
M201 X1000 Y1000 Z1400.00 E5000                    ; set accelerations (mm/s^2) own
M906 X1150 Y1150 Z850 E600 I50                     ; set motor currents (mA) and motor idle factor in per cent

G91                     ; relative positioning
G1 H2 Z0.02 F3000		; enable the Motor move at least one mircostep  -- Problem Stealthchop?
G4 P50					; make a 50ms pause for the drivers  -- Problem Stealthchop?
G1 H2 Z15 F6000         ; lift Z relative to current position
G1 H2 X0.02				; enable the Motor move at least one mircostep -- Problem Stealthchop?
G4 P50					; make a 50ms pause for the drivers  -- Problem Stealthchop?
G1 H2 Y0.02				; enable the Motor move at least one mircostep -- Problem Stealthchop?
G4 P50					; make a 50ms pause for the drivers  -- Problem Stealthchop?
G1 H1 X-355 Y355 F9000  ; move quickly to X or Y endstop and stop there (first pass)
G1 H1 X-355             ; home X axis
G1 H1 Y355              ; home Y axis
G1 X5 Y-5 F9000         ; go back a few mm
G1 H1 X-355 F360        ; move slowly to X axis endstop once more (second pass)
G1 H1 Y355              ; then move slowly to Y axis endstop
G90                     ; absolute positioning
G1 X177.713 Y144.526 F9000 ; go to first bed probe point and home Z --> own direct system
G30                     ; home Z by probing the bed

G91                    ; relative positioning
G1 Z15 F6000           ; lift Z relative to current position
G90                    ; absolute positioning
;smal test moves
G0 X0 Y0 F3000
G0 X0 Y310 F3000
G0 X310 Y310 F3000
G0 Y0 Y0 F3000

; now again with Spread cycle
M18							  ; disable all motors to reset the stepper drivers
M569 P0.0 S0 D2                                    ; physical drive 0 goes forwards D2=Spread cycle (x-achses)
M569 P0.1 S0 D2                                    ; physical drive 1 goes forwards D2=Spread cycle (y-achses)
M569 P0.2 S0 D2                                    ; physical drive 2 goes backwards D2=Spread cycle (Z1)
M569 P0.3 S0 D2                                    ; physical drive 3 goes backwards D2=Spread cycle (Z2)
M569 P0.4 S1 D2                                    ; physical drive 4 goes backwards D2=Spread cycle (extruder)
M569 P0.5 R-1                                      ; physical drive 4 goes backwards D2=Spread cycle (empty)
M584 X0.0 Y0.1 Z0.2:0.3 E0.4                       ; Driver 0 For X, 1 for Y, Z=2:3 U=4, Extruder 4
M350 X32 Y32 Z16 E16 I1                            ; configure microstepping with interpolation - working
M92 X400.00 Y400.00 Z400 E412.00                   ; set steps per mm
M566 X300.00 Y300.00 Z24.00 E300.00                ; set maximum instantaneous speed changes (mm/min) from config file thingiverse 
M203 X14000 Y14000 Z4520 E7000                     ; set maximum speeds (mm/min) new test Z800 old
M201 X1000 Y1000 Z1400.00 E5000                    ; set accelerations (mm/s^2) own
M906 X1150 Y1150 Z850 E600 I50                     ; set motor currents (mA) and motor idle factor in per cent

G91                     ; relative positioning
G1 H2 Z0.02 F3000		; enable the Motor move at least one mircostep  -- Problem Stealthchop?
G4 P50					; make a 50ms pause for the drivers  -- Problem Stealthchop?
G1 H2 Z15 F6000         ; lift Z relative to current position
G1 H2 X0.02				; enable the Motor move at least one mircostep -- Problem Stealthchop?
G4 P50					; make a 50ms pause for the drivers  -- Problem Stealthchop?
G1 H2 Y0.02				; enable the Motor move at least one mircostep -- Problem Stealthchop?
G4 P50					; make a 50ms pause for the drivers  -- Problem Stealthchop?
G1 H1 X-355 Y355 F9000  ; move quickly to X or Y endstop and stop there (first pass)
G1 H1 X-355             ; home X axis
G1 H1 Y355              ; home Y axis
G1 X5 Y-5 F9000         ; go back a few mm
G1 H1 X-355 F360        ; move slowly to X axis endstop once more (second pass)
G1 H1 Y355              ; then move slowly to Y axis endstop
G90                     ; absolute positioning
G1 X177.713 Y144.526 F9000 ; go to first bed probe point and home Z --> own direct system
G30                     ; home Z by probing the bed

G91                    ; relative positioning
G1 Z15 F6000           ; lift Z relative to current position
G90                    ; absolute positioning
;smal test moves
G0 X0 Y0 F3000
G0 X0 Y310 F3000
G0 X310 Y310 F3000
G0 Y0 Y0 F3000