I'm building a rather large printer at the moment and one issue I have is that when / if the printer looses power the Z axis drops (it's got quite some weight to it). This wouldn't be a problem if both sides would drop equally, however one side is slightly heavier than the other.

It's a typical core XY build for reference.

My plan is to set up the second Z Axis motor on E0 (Drive 3) but I just wanted to run things by here to check I'm doing it correctly as I can't find a easy way to do it with the config tool.

I've gone into my config.g and changed / added the below:

M584 X0 Y1 Z2:3 E4 ; set drive mapping
M671 X-50:550 Y250:250 S4

I assume this is correct but wanted to check with others / anyone who's done similar.

I assume I also need to do the same for my endstop but uncertain as to where I would need to do this. I've wired my second end stop to E0 STOP but can't figure out where I tell the board that it's not actually a E Stop

@Phaedrux Yeah it's just clicked it'll be my Z axis, I've not set the bed up as of yet so don't even have those motors connected

@Phaedrux Unfortunately I've checked the wires already and have replaced them all, the motors are moving as expected however when it's homing multiple axis at once (X and Y) it seems to encounter an issue and starts skipping on the belt.

I'm assuming it's a issue with the driver then?

If so I assume there's nothing I can really do to repair it? I'm running two Z motors and a X and Y so won't have a free one once I add the extruder also

Thanks again for the help!

@Phaedrux It's also now giving me this error, not sure if it's possibly related?

20/04/2024, 18:20:07 Error: in file macro line 7: G1: Failed to enable endstops

@Phaedrux Tried this and still getting the same error message

@Phaedrux Motors are cold to the touch

Motors model number is:
JK42HS40-1704-13A

@Bewaren M98
P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled

@Phaedrux said in Duet2 Firmware Upgrade Issue:

M122

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.1 (2024-04-19 14:40:46) running on Duet Ethernet 1.02 or later
Board ID: 08DGM-917DA-G4MSD-6JKDA-3SN6Q-TST39
Used output buffers: 1 of 26 (14 max)
=== RTOS ===
Static ram: 23256
Dynamic ram: 67932 of which 0 recycled
Never used RAM 21956, free system stack 184 words
Tasks: NETWORK(1,ready,27.9%,220) HEAT(3,nWait 5,0.0%,330) Move(4,nWait 5,0.0%,359) MAIN(1,running,72.0%,761) IDLE(0,ready,0.1%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:27:25 ago, cause: software
Last software reset at 2024-04-19 22:48, reason: User, Gcodes spinning, available RAM 21812, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 35.4, current 36.7, max 37.3
Supply voltage: min 24.2, current 24.3, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2024-04-19 23:15:40
Cache data hit count 4294967295
Slowest loop: 15.20ms; fastest: 0.18ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 13.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Q0 segments left 0
Code queue 0 is empty
=== Network ===
Slowest loop: 6.92ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex
Socket states: 5 2 2 2 2 2

M98 "config.g"
Error: M98: No P or R parameter

Nema 17 Specs:
Motor Type: Bipolar Stepper.
Step Angle: 1.8°
Holding Torque: 26Ncm(36.8oz.in)
Rated Current/phase: 0.4A.
Phase Resistance: 30ohms.
Inductance: 37mH+/-20%(1KHz)

Config.g:
config (1).g

@Phaedrux Alright I've checked all the wiring is correct and I've updated the firmware. Both motors are moving the correct direction now but when the axis are homing I'm now getting a issue with Driver 2

'Warning: Driver 2 warning: phase A may be disconnected, phase B may be disconnected'

There's nothing grounding on the board and I can't figure out what else it could be, the motors maybe?

@Phaedrux How do I go about updating the DWC Files?