duex 2 steppers not working

andrewjl

~~undefined~~So, I just had my duet 2 wifi replaced via warranty. Old board started smoking from the SD card and the main chip. No 3.3v.
I have the new board installed with my duex 2 but the stepper motors on the duex 2 aren't working. The Z steppers are configured in a 3 independent Z configuration. I swapped the z stepper connectors around and the problem follows the duex2.
Also connected to the duex2 is a BLTouch, which works fine. BLTouch is configured on the "duex.pwm1" channel.

What can I test to see if the stepper drivers are somehow dead? Also, duex2's seem to be nonexistent these days. I can't find any to buy if I need to.



G90                                                ; send absolute coordinates...
M83                                                ; ...but relative extruder moves
M550 P"HEVO"                                       ; set printer name
M584 X0 Y1 Z2:5:6 E3; three Z motors connected to driver outputs 2, 5 and 6
M669 K1                                            ; select CoreXY mode

; Network
M551 P"--"                                   ; set password
M552 S1                                            ; enable network
M586 P0 S1                                         ; enable HTTP
M586 P1 S0                                         ; disable FTP
M586 P2 S0                                         ; disable Telnet

; Drives
M569 P0 S1                                         ; physical drive 0 goes forwards
M569 P1 S1                                         ; physical drive 1 goes forwards
M569 P2 S1                                         ; physical drive 2 goes forwards
M569 P3 S1                                         ; physical drive 3 goes forwards
M569 P5 S1
M569 P6 S1
M350 X32 Y32 I1                                    ; configure microstepping with interpolation
M350 Z16 E16 I1                                    ; configure microstepping with interpolation
M92 X160.00 Y160.00 Z400.00 E420.00                ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00                ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00            ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00                ; set accelerations (mm/s^2)
M906 X800 Y800 Z1200 E800 I30                       ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                            ; Set idle timeout



M671 X60:150:215 Y420:-10:420 S7 ; leadscrews at rear left, front middle and rear right

; Axis Limits
M208 X0 Y0 Z0 S1                                   ; set axis minima
M208 X265 Y265 Z280 S0                             ; set axis maxima

; Endstops
M574 X1 S1 P"xstop"                                ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop"                                ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2                                         ; configure Z-probe endstop for low end on Z

; Z-Probe
M950 S0 C"duex.pwm1"                               ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T12000               ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X30 Y0 Z2.5                               ; set Z probe trigger value, offset and trigger height
;M557 X15:215 Y15:195 S20                           ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138     ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0                              ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B0 S1.00                                   ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                            ; map heated bed to heater 0
M143 H0 S120                                       ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138      ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1                               ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00                                   ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S300                                       ; set temperature limit for heater 1 to 300C

; Fans
M950 F0 C"fan0" Q500                               ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1                                     ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500                               ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45                                  ; set fan 1 value. Thermostatic control is turned on

; Tools
M563 P0 D0 H1 F0                                   ; define tool 0
G10 P0 X0 Y0 Z0                                    ; set tool 0 axis offsets
G10 P0 R0 S0                                       ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined

; Miscellaneous
M501                                               ; load saved parameters from non-volatile memory
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

SIam

@andrewjl said in duex 2 steppers not working:

M584 X0 Y1 Z2:5:6 E3; three Z motors connected to driver outputs 2, 5 and 6

Is used before you have configured the drivers, inset this before line 23

M350 X32 Y32 I1

You can only use 16 steps with interpolation, so s
set this to 16 Steps

after that execute

M98 P"config.g"

If there are errors reported than post it here if not test if the motors now running

Also, duex2's seem to be nonexistent these days. I can't find any to buy if I need to

As far as I know is the production of duet 2 discontinued

Phaedrux

@siam said in duex 2 steppers not working:

As far as I know is the production of duet 2 discontinued

There was not enough demand for duex2 any more. Duex5 is still available.

andrewjl

@siam I modified the config.g as you showed and it still doesn't move the steppers plugged into the Duex2.

Phaedrux

Can you post photos of the Duex2 board? Was it connected at the time the Duet wifi board had it's incident?

andrewjl

@phaedrux
Yes, it was connected during the “incident”. Which has me worried. I’m wondering if it’s a matter of replacing stepper drivers or if I can tell it’s another component on the board.

andrewjl

@andrewjl
Sorry here’s a better lit photo.

Phaedrux

I don't see any smoldering craters. What does M122 report when you try to move those motors?

andrewjl

@phaedrux I'm not that familiar with using M122. M122 P101 to print the status of an attached Duex just sits there thinking for a few minutes, then spits out "Expander status 0000" . I'm not sure if the plain M122 should show the drives on the duex. It only shows drives 0-4 This is what it shows

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6B2-NJ4S8-6JKF2-3SJ6N-KA42K
Used output buffers: 1 of 24 (20 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 93920 of which 208 recycled
Exception stack ram used: 568
Never used ram: 8396
Tasks: NETWORK(ready,316) HEAT(blocked,1224) MAIN(running,1816) IDLE(ready,80)
Owned mutexes:
=== Platform ===
Last reset 00:14:39 ago, cause: power up
Last software reset at 2021-09-08 21:29, reason: User, spinning module GCodes, available RAM 7852 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 40.4, current 42.0, max 42.5
Supply voltage: min 24.7, current 24.9, max 25.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 2021-09-09 20:03:40
Cache data hit count 1457745491
Slowest loop: 604.68ms; fastest: 0.13ms
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.8ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 168, MaxWait: 661ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 18, completed moves: 18, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is ready with "m122 " 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 201.62ms; fastest: 0.07ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 3
WiFi firmware version 1.26
WiFi MAC address 48:3f:da:a6:c0:72
WiFi Vcc 3.38, reset reason Unknown
WiFi flash size 2097152, free heap 24400
WiFi IP address 192.168.1.136
WiFi signal strength -51dBm, reconnections 0, sleep mode unknown
Socket states: 0 0 0 0 0 0 0 0

Phaedrux

Yes the normal M122 should be reporting the Duex and the drivers, which it appears to not be doing. It is connected, right?

Please try updating your firmware to 3.3 by uploading this zip file to the system tab in DWC and then check M122 again.

https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip