Configure 2nd Z Axis Stepper
-
@SonnyD1 said in Configure 2nd Z Axis Stepper:
M350 X16 Y16 Z16:16 E16 I1
Remove the second 16 value from Z. You only need to set it per axis, not motor.
Can you share a photo of the wiring at the duet side just to confirm which drivers you're actually using?
-
@Phaedrux
Not sure if you can make it out in that mess. Working progress and all. They are plugged in as follows:
X axis - Xstep
Y axis - Ystep
Left Z - Zstep
Right Z - E1step
Extruder - E0step -
SO I think I've managed to isolate the issue. I tried another stepper I had that I know works on the same driver and it did't work either. So I tried that motor on the one that I know that does to confirm. The wiring is good and all motors are good. The only thing left that I can't check is the driver. Is there a way that I can confirm that I have a bad driver?
-
Do you get any error messages after trying to move the suspect driver?
Can you share the results of M122 after trying to move the driver?
Did you remove that duplicate 16 value from M350? -
@Phaedrux I don't get any error messages when moving the Z axis. One motor (Z Left) moves and the one on the right does nothing. I've confirmed that it's not the motor or the wiring by running both motors with both cables on the Zstep driver. I cant get anything to work on the E1step driver. I removed the duplicate 16 value from the M350 line before running the tests. Here are the results from the M122 taken immediately after tests:
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.6 (2023-07-21 14:08:28) running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6M2-NWNS0-7J9D4-3SD6K-1V33L
Used output buffers: 1 of 26 (14 max)
=== RTOS ===
Static ram: 23896
Dynamic ram: 74944 of which 0 recycled
Never used RAM 13240, free system stack 184 words
Tasks: NETWORK(notifyWait,13.3%,242) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) MAIN(running,86.2%,436) IDLE(ready,0.4%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:03:35 ago, cause: software
Last software reset at 2023-10-10 21:49, reason: User, GCodes spinning, available RAM 13168, 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
Step timer max interval 0
MCU temperature: min 31.5, current 32.3, max 32.8
Supply voltage: min 24.1, current 24.3, max 24.7, 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: 2023-10-10 21:52:41
Cache data hit count 4294967295
Slowest loop: 5.77ms; 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 3.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
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 ===
Segments left: 0
Movement lock 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
Code queue is empty
=== Network ===
Slowest loop: 12.68ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
= WiFi =
Interface state: active
Module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.27
WiFi MAC address f4:cf:a2:71:b4:05
WiFi Vcc 3.35, reset reason Power up
WiFi flash size 2097152, free heap 19896
WiFi IP address 192.168.1.137
WiFi signal strength -52dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0 -
@moth4017 I've isolated the issue to the E1step driver that my right Z stepper is plugged into. Swapping wires and motors the fault stays on the same driver. I do not have another driver that I can try.
-
When and where did you purchase the board?
-
@Phaedrux I ordered it from Filastruder on June 13 (#95005). I had some life events come up which is why I'm only just now working on it.
-
Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.
-
@Phaedrux I did as you advised and sent that email. I haven't yet received a reply.
