Hi,
thank you for the fast respond
Here is the M122:
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0 (2022-03-15 18:57:24) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956BA-NA3TJ-6JKF0-3S86Q-1V9GT
Used output buffers: 1 of 40 (25 max)
=== RTOS ===
Static ram: 151000
Dynamic ram: 95932 of which 0 recycled
Never used RAM 103740, free system stack 206 words
Tasks: NETWORK(ready,26.6%,251) ETHERNET(notifyWait,0.2%,168) HEAT(notifyWait,0.0%,347) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,333) TMC(notifyWait,7.9%,92) MAIN(running,65.3%,1087) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:04:11 ago, cause: power up
Last software reset at 2022-05-02 13:15, reason: User, GCodes spinning, available RAM 103596, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 126
MCU temperature: min 42.6, current 42.9, max 43.0
Supply voltage: min 24.5, current 24.5, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, max 12.1, under voltage events: 0
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, mspos 8, reads 19616, writes 0 timeouts 0
Driver 1: standstill, SG min n/a, mspos 8, reads 19616, writes 0 timeouts 0
Driver 2: standstill, SG min n/a, mspos 8, reads 19617, writes 0 timeouts 0
Driver 3: standstill, SG min n/a, mspos 8, reads 19617, writes 0 timeouts 0
Driver 4: standstill, SG min n/a, mspos 8, reads 19617, writes 0 timeouts 0
Driver 5: standstill, SG min n/a, mspos 8, reads 19616, writes 0 timeouts 0
Date/time: 2022-05-03 09:37:30
Slowest loop: 2.90ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.3ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, 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 -1 -1 -1 -1 -1 -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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== CAN ===
Messages queued 31, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 17/0/0
Tx timeouts 0,0,17,0,0,14 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 1.92ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0
M98:
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Yes I tried to use only one motor for the X Axis on the other drivers, still only working on driver 0.1.
I bought the duet some month ago from a german reseller CR3D. Use the duet since one week or so.
When I use the Z motors on the working Driver 0.1 i get this message:
Warning: Driver 0.1 warning: phase A short to Vin, phase B may be disconnected
3.5.2022, 09:48:57 Error: Driver 0.1 error: phase A short to Vin
Changed the steps, acceleration etc. to the suitable values for the Z axis.
Is it even possible to run the Nema 34 with the board or do I need a extension board or something?
Also thought about going back to the external drivers, so I will need the extension board anyway...
Here are the pictures of the board: