Dual Z Issues for Ender 3 w/ Duet 2 Wifi

Hello everyone. So I recently upgraded my Ender 3 to Duet. I managed to get everything working except Dual Z. Now, I had to reposition the pins of my X & Y motors to work with the Ender Pro settings in the config manager as I had the wires the opposite way of what they should have been. I thought I copied the original wiring configuration right, but it seems I hadn't at the time. Those two work fine homing to where they should now.

Then I tried that with each Z motor (separate wires running to each motor & the Z ports on the board). And it doesn't
seem to work right. I did try looking this up online to try to narrow down what it could be.

The Z axis seems to semi work. Getting a CM or two in one direction. Although it feels like one motor is doing more work as it sort of hops up. Also, homing seems to send it up? Then it seems to get stuck, as powering it off drops the x-gantry slightly.

The wiring is what it should be for one Z motor. The second motor has the middle two wires swapped on the motor connector to turn it in the opposite direction. As that was the only way to get it to work on the old board. [Note: If they're both wired the same on the creality board, then one side of the x-gantry goes up and the other side goes down. But that was merged into one cable.] On the Duet, if try the exact same wiring by using X & Y cables from Z ports to Z motors it seems to repeat the same results (homing moves the gantry up). Either way, I get the impression that one motor is doing more work then the other. But I've tested both motors finding that they do both power up and turn (at least individually, when they're both hooked up I am unsure if they're both getting the power needed).

Tested a few gcode commands:

- M906 to see if power is getting to the motors, it reads 100% on Z. Though it only shows it once, rather then twice.
-I tried G1 S2 Z10 F100 this to get Z to move without homing. The X gantry moves up like it does with Z homing.

**edited after more testing***

board	"duetwifi10"
firmware	3
nvram	false
auto_save	
enabled	true
save_threshold	10
resume_threshold	11
gcodes_to_run	"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000"
display	
type	1
encoder_steps	4
spi_frequency	2000000
menus	
0	
name	"main"
value	"text C10 R20 \"Powered by Duet3D\""
images	[]
geometry	
type	"cartesian"
mins	
0	0
1	0
2	0
maxes	
0	235
1	235
2	250
delta_radius	105.6
homed_height	250
low_dive_height	false
max_carriage_travel	260
print_radius	85
rod_length	215
z_min	0
drives	
0	
direction	0
microstepping	16
microstepping_interpolation	true
steps_per_mm	80
instant_dv	20
max_speed	150
acceleration	500
current	800
driver	0
endstop_type	1
endstop_location	1
driver_v3	"0.0"
endstop_pin	"xstop"
1	
direction	0
microstepping	16
microstepping_interpolation	true
steps_per_mm	80
instant_dv	20
max_speed	150
acceleration	500
current	800
driver	1
endstop_type	1
endstop_location	1
driver_v3	"0.1"
endstop_pin	"ystop"
2	
direction	1
microstepping	16
microstepping_interpolation	true
steps_per_mm	400
instant_dv	0.4
max_speed	3
acceleration	100
current	800
driver	2
endstop_type	1
endstop_location	1
endstop	null
driver_v3	"0.2"
endstop_pin	"zstop"
3	
direction	1
microstepping	16
microstepping_interpolation	true
steps_per_mm	410
instant_dv	5
max_speed	100
acceleration	5000
current	1000
driver	3
driver_v3	"0.3"
idle	
used	true
factor	50
timeout	30
homing_speed_fast	50
homing_speed_slow	4
travel_speed	100
z_dive_height	5
slow_homing	false
probe	
type	"noprobe"
recovery_time	0.4
trigger_height	2.5
trigger_value	500
x_offset	0
y_offset	0
speed	2
deploy	false
points	[]
pwm_channel	64
pwm_inverted	false
pwm_pin	null
input_pin	"zprobe.in"
modulation_pin	null
bed_is_nozzle	false
bed	
present	true
heater	0
use_pid	false
chamber	
present	false
heater	2
use_pid	false
heaters	
0	
temp_limit	150
scale_factor	100
series	4700
thermistor	100000
beta	4092
c	0
channel	0
sensor	0
output_pin	"bedheat"
sensor_type	"thermistor"
sensor_pin	"bedtemp"
1	
temp_limit	290
scale_factor	100
series	4700
thermistor	100000
beta	4092
c	0
channel	1
sensor	1
output_pin	"e0heat"
sensor_type	"thermistor"
sensor_pin	"e0temp"
num_nozzles	1
toolchange_wait_for_temperatures	true
generate_t_code	false
tools	
0	
mix_ratio	[]
number	0
name	""
extruders	
0	0
heaters	
0	1
fans	
0	0
x_offset	0
y_offset	0
z_offset	0
compensation_x_offset	15
compensation_y_offset	15
peripheral_points	3
halfway_points	0
calibration_factors	3
probe_radius	85
mesh	
x_min	15
x_max	215
y_min	15
y_max	195
radius	85
spacing	20
home_first	false
orthogonal	
compensation	false
height	50
deviations	
0	0
1	0
2	0
network	
enabled	true
mac_address	""
name	""
password	""
ssid	""
ssid_password	""
dhcp	true
ip	""
netmask	""
gateway	""
protocols	
http	true
ftp	false
telnet	false
fans	
0	
name	""
value	0
inverted	false
frequency	500
thermostatic	false
heaters	[]
trigger_temperature	45
output_pin	"fan0"
1	
name	""
value	100
inverted	false
frequency	500
thermostatic	true
heaters	
0	1
trigger_temperature	45
output_pin	"fan1"
2	
name	""
value	100
inverted	false
frequency	500
thermostatic	true
heaters	
0	1
1	0
trigger_temperature	45
output_pin	"fan2"
custom_settings	""
expansion_boards	[]
standalone	true
panelDue	false

Edited 1 time(s). Last edit at 04/26/2021 01:38PM by Ripeds_O3P.

Perhaps the two Z motors are trying to move in opposite directions, and getting stuck as a result?

It will be easier for us to check your settings if you post the config.g file, homeall.g file and homez.g file.

For faster responses to your questions, post at [forum.duet3d.com].

Edited 3 time(s). Last edit at 04/26/2021 02:44AM by dc42.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Fair enough. I've reposted there with the files mentioned. Thank you.

[forum.duet3d.com]