@dc42 I experimented some more and came up with testing routine. Trying to set StealthChop to SpreadCycle at low speed. No luck... Or maybe at 10mm/s is all I can get?

Accel/jerk are halved in comparison to normal operation.

Each testing sequence consists of:

Configuration Homing with tuning Three sets of moves of Y and U separately Each set has different speed - 10, 50 and 100mm/s

It runs five tests with different configuration each:

StealthChop to SpreadCycle with switch at 10.4 mm/s StealthChop to SpreadCycle with switch at 52.1 mm/s StealthChop to SpreadCycle with switch at 93.8 mm/s Pure SpreadCycle Pure StealthChop

I've recorded a routine with first 3 sequences. Every time movement is above switch speed then "clack" happens. Its visibly less noticeable at low setting, but is still there. As it's increased then it gets much worse.

If you could look if I did homing/tuning correctly, please.

I'll proceed to experimenting with different speeds. Previously when I picked different values for M569 and M915 I've got some improvement - clacking was getting less and less visible.

Thanks for your time and input.

Video (last two removed for brevity):
https://youtu.be/yojaNXBJG9s

Macros:
stealthChop.home.g

; Homing and tuning M18 X U Y Z ; Disable motors M17 X U Y Z ; Enable motors G4 P100 ; Wait G91 ; Relative positioning G1 Z5 F1000 H2 ; Lift Z relative to current position G1 X-999 U999 Y-999 F3000 H1 ; Move and Tune G1 X5 U-5 Y5 F6000 H2 ; Go back a few mm G1 X-999 U999 Y-999 F360 H1 ; Move again G1 Z-5 F1000 H2 ; Return Z to previous height G90 ; BLTouch preperation M280 P0 S160 ; Precautionary alarm release M280 P0 S90 ; Ensure the pin is raised ; Home Z using the Z-Probe G91 ; Relative positioning G1 Z10 F1000 H2 ; Lift Z relative to current position G90 ; Absolute positioning G1 X-130 Y-115 F6000 ; Move T0 to probing point, including probe offset G30 ; Probe the bed and set Z to the probe offset G1 Z10 F1000 ; Raise Z off the bed

stealthChop.test.g

; Initial settings var distance = 30 ;mm var speed_high = 100 ;mm/s var speed_high_min = 60 * var.speed_high; var speed_med = 50 ;mm/s var speed_med_min = 60 * var.speed_med; var speed_low = 10 ;mm/s var speed_low_min = 60 * var.speed_low; G1 X-999 U0 Y0 F3000 ; Prepare for test G4 P1000 ; Test Low Speed while iterations < 3 G1 U{var.distance/4} F{var.speed_low_min} G1 U{-(var.distance/4)} F{var.speed_low_min} while iterations < 3 G1 Y{var.distance/4} F{var.speed_low_min} G1 Y{-(var.distance/4)} F{var.speed_low_min} ; Test Medium Speed while iterations < 3 G1 U{var.distance/2} F{var.speed_med_min} G1 U{-(var.distance/2)} F{var.speed_med_min} while iterations < 3 G1 Y{var.distance/2} F{var.speed_med_min} G1 Y{-(var.distance/2)} F{var.speed_med_min} ; Test High Speed while iterations < 3 G1 U{var.distance} F{var.speed_high_min} G1 U{-(var.distance)} F{var.speed_high_min} while iterations < 3 G1 Y{var.distance} F{var.speed_high_min} G1 Y{-(var.distance)} F{var.speed_high_min}

stealthChop.spreadCycle.test.g

; RR VCast IDEX (Cartesian) ; Duet 3 6HC TMC5160 ; Testing U and Y ; XUY using 2.5A/3.1V LDO-42STH47-2504AC ; https://www.ratrig.com/nema-17-stepper-motor.html ; 1. Load StealthChop to SpreadCycle settings ; 2. Tune drivers ; 3. Run test for StealthChop to SpreadCycle ; 4. Run test for StealthChop only ; 5. Run test for SpreadCycle only G4 S5 ; Time to start recording :) ; Accel/Jerk are halved in comparison to normal operation M906 X2125 U2125 Y2125 Z1600:1600 E350:350 I50 ; set currents M566 X350 U350 Y350 Z60:60 E300:300 ; set maximum instantaneous speed changes (mm/min) M203 X6000 U6000 Y6000 Z1800:1800 E3600:3600 ; set maximum speeds (mm/min) M201 X400 U400 Y450 Z100:100 E600:600 ; set accelerations (mm/s^2) M204 P400 T400 ;------------------------------------ ;---- StealthChop to SpreadCycle ---- ;------------------------------------ echo "Enable StealthChop to SpreadCycle settings (Switch Speed - 10.4 mm/s)" ; Reset Coolstep M915 P0.0:0.1:0.2:0.3:0.4:0.5 T1 ; disable coolstep M915 P20.0:21.0 T1 ; disable coolstep ; Set U M569 P0.1 S0 D3 V900 H900 M915 P0.1 T900 ; Set Y M569 P0.2 S0 D3 V900 H900 M915 P0.2 T900 ; Homing and tuning M98 p"/macros/stealthChop.home.g" M98 p"/macros/stealthChop.test.g" echo "Enable StealthChop to SpreadCycle settings (Switch speed - 52.1 mm/s)" ; Reset Coolstep M915 P0.0:0.1:0.2:0.3:0.4:0.5 T1 ; disable coolstep M915 P20.0:21.0 T1 ; disable coolstep ; Set U M569 P0.1 S0 D3 V180 H180 M915 P0.1 T180 ; Set Y M569 P0.2 S0 D3 V180 H180 M915 P0.2 T180 ; Homing and tuning M98 p"/macros/stealthChop.home.g" M98 p"/macros/stealthChop.test.g" echo "Enable StealthChop to SpreadCycle settings (Switch speed - 93.8 mm/s)" ; Reset Coolstep M915 P0.0:0.1:0.2:0.3:0.4:0.5 T1 ; disable coolstep M915 P20.0:21.0 T1 ; disable coolstep ; Set U M569 P0.1 S0 D3 V100 H100 M915 P0.1 T100 ; Set Y M569 P0.2 S0 D3 V100 H100 M915 P0.2 T100 ; Homing and tuning M98 p"/macros/stealthChop.home.g" M98 p"/macros/stealthChop.test.g" ;------------------------------------ ;---- SpreadCycle only ---- ;------------------------------------ echo "Enable SpreadCycle settings" ; Reset Coolstep M915 P0.0:0.1:0.2:0.3:0.4:0.5 T1 ; disable coolstep M915 P20.0:21.0 T1 ; disable coolstep ; Set U (Factory values) M569 P0.1 S0 D2 H200 M915 P0.1 T2000 ; Set Y M569 P0.2 S0 D2 H200 M915 P0.2 T2000 ; Homing and tuning M98 p"/macros/stealthChop.home.g" M98 p"/macros/stealthChop.test.g" ;------------------------------------ ;---- StealthChop only ---- ;------------------------------------ echo "Enable StealthChop settings" ; Reset Coolstep M915 P0.0:0.1:0.2:0.3:0.4:0.5 T1 ; disable coolstep M915 P20.0:21.0 T1 ; disable coolstep ; Set U (Above 100mm/s) M569 P0.1 S0 D3 V50 H50 M915 P0.1 T50 ; Set Y M569 P0.2 S0 D3 V50 H50 M915 P0.2 T50 ; Homing and tuning M98 p"/macros/stealthChop.home.g" M98 p"/macros/stealthChop.test.g"

The realTime field will be zero until you connect to the Duet from DWC, at which time DWC sends the current time to the Duet. Until then, the Duet doesn't know the time.

@Joe said in Duet 3 dual z axis wiring:

I would definitely be interested in finding the solution of this issue and absolutely pleased if you could help me. Leading through my problem. 😊

As I said above:

You would start with a single z axis configuration using the web tool, and then manually add the second driver to the Z axis configuration in M584.

To show you exactly what to change you'd need to share your existing config for the single driver and then tell us which additional driver you want to use.

The tool can only create a basic setup. Adding the second Z driver is quite easy though, we just need to know which drivers you are connected to.

When wiring up the motors, verify the phases first.

https://duet3d.dozuki.com/Wiki/Choosing_and_connecting_stepper_motors#Section_Identifying_the_stepper_motor_phases

I don't have any particular complain about the connectors, I'm pretty easy going on that regard. The very small beige ones are tedious to crimp but fortunately I've purchased the wire-kit.

I know it's already pretty small but what I would love is for it to be with one side 40mm max, even sacrificing a connector (or using a smaller one) or dropping the switches.

I'm doing a magnetic toolchange with very small heads and I'm having troubles positioning the toolboard (I'm actually thinking of using an expansion 3HC instead of the toolboard).

@1997alex said in Trouble with first test print:

M208 X-0 Y-0 Z-0 S1

Set this to M208 X0 Y0 Z0 S1. Don't use '-' between parameters unless you actually mean "negative-something".

I'm not sure if my offset is correct to the actual position of the hot end or z probe.

Your current setting seems to be:

G31 P500 X45 Y40 Z0.15

From your picture, and assuming that X0 Y0 is front left of your bed, the probe is to the left and behind the nozzle. To work out the probe offset values, imagine the nozzle is at X0 Y0. Where would the probe be? In your case, X-45 Y40 I think. So try G31 P500 X-45 Y40 Z0.15.

M557 X0:900 Y0:700 S40

Because of the probe offset, and the bed limits you have set with M208, some points are unreachable by the probe. With the above probe offset, you can't get to the 45mm on the right hand side of the bed (because the probe is at X-45), or the front 40mm of the bed (because probe is at Y40). Then give the edge a couple of mm clearance. So set M557 to M557 X5:850 Y45:700 S40.

If your nozzle can reach points outside the bed, you can adjust M208, eg if it can go off the front by 20mm, change M208 to M208 X0 Y-20 Z0 S1. Then adjust M557 so that the probe can get closer to the edge, eg M557 X5:850 Y25:700 S40

This is also covered here: https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe#Section_Measuring_Probe_X_Y_Offset
https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensation

Ian

@whopping-pochard This is my current wiring for my SSR and PS_ON
SSR terminal 1: connected to switch NO and PSU neutral
SSR terminal 2: connected to switch C and power in neutral
SSR terminal 3+: +5V
SSR terminal 4-: PS_ON

With the Duet 2 I can hold the button for less than 1 second and the board will power up. With the Duet 3 I have to hold the button for 20-30 seconds. My goal is to figure out how to get the Duet 3 setup so I don't have to hold the button down for that long. The only way I figured that would work is if the raspberry pi was already powered on

I don't really understand what you mean, but if you've got it figured out, that's awesome.

@jay_s_uk I am using the latest update

@elixirtrip well some info is already here. For now there is a board that can go to can bus without a driver and you can attach your own external closed loop (leadshine, odrive ..):

https://forum.duet3d.com/topic/16257/ac-servo-motor-driver-control-by-duet-3-mb6hc-help/5

https://forum.duet3d.com/topic/17148/duet-3-expansion-1xd-can-fd-single-external-driver-controller?_=1592917797395

https://forum.duet3d.com/topic/15975/duet-3-nema-23-closed-loop-with-z-axis-also-using-elec-brake/16

@dc42 Thank you, sir!

@smarshall Can you share some more info about what you're experiencing? hardware and firmware used? Perhaps starting a new thread with all your details would be best. Link back to this thread if you think it's related.