Z motor issues (burning!)

Mogal · 18 Jan 2021, 15:41

Thanks, Here is my Current config:

; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up
;------------------------------------------------------------------------------------------------------------------
; Custom Configuration - Set drive mapping
M584 X0 Y1 Z4 E3 ; Set X to Drive 0 - Set Y to Drive 1 - Set Z motor to drive 4 - Extruder to Drive 3
;------------------------------------------------------------------------------------------------------------------
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M667 S1 ; Select CoreXY mode
;------------------------------------------------------------------------------------------------------------------
; Network
M550 P"Mogal's CoreXY"\ ; Set machine name
M552 S1 ; Enable network
M587 S"MyFi" P"********" ; Configure access point. You can delete this line once connected
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet
;------------------------------------------------------------------------------------------------------------------
; Drives
M569 P0 S0 ; Drive 0 goes backwards (X) ; MM/Sec MM/Min
M569 P1 S0 ; Drive 1 goes backwards (Y) ; 1 60
M569 P4 S0 ; Drive 4 goes backwards (Z) ; 10 600
M569 P3 S0 ; Drive 3 goes backwards (E) ; 20 1200
M350 X16 Y16 Z16 E16 I1 ; Configure micro stepping with interpolation ; 30 1800
M92 X200.00 Y200.00 Z4,816.665 E320 ; Set steps per mm 4,816.665 9,633.33 ; 40 2400
M566 X500 Y500 Z20 E3600 ; Set maximum instantaneous speed changes (mm/min) -This is Jerk- ; 50 3000
M203 X12000.00 Y12000.00 Z300.00 E12000.00 ; Set maximum speeds (mm/min) ; 60 3600
M201 X3600.00 Y3600.00 Z50.00 E10000.00 ; Set accelerations (mm/s^2) ; 70 4200
;M204 P1000 T3000 ; Print and Travel accelerations ; 80 4800
M906 X1200.00 Y1200.00 Z1200.00 E1200.00 I30 ; Set motor currents (mA) and motor idle factor in per cent ; 90 5400
M84 S10 ; Set idle timeout (10 Seconds) ; 100 6000
;M572 D0 S0.15 ; Pressure advance (Original Value: 0.15)
;------------------------------------------------------------------------------------------------------------------
; Axis Limits
M208 X0 Y20 Z0 S1 ; Set axis minimal
M208 X310 Y350 Z400 S0 ; Set axis maximum
;------------------------------------------------------------------------------------------------------------------
; Endstops
M574 X1 Y2 S1 ; Set active high endstops

; Z-Probe
M574 Z2 S2 ; Set endstops controlled by probe
M558 P5 H5 Z1 I1 F200 T6000 ; Set Z probe type to modulated and the dive height + speeds
G31 P500 X30 Y00 Z2.72 ; Set Z probe trigger value, offset(X, Y) and trigger height <-- Higher number brings closer to bed, Lower Number is further away!
M557 X30:330 Y30:360 S50 ; Define mesh grid
;------------------------------------------------------------------------------------------------------------------
; Heaters
;M140 H-1 ; tells the firmware there is no bed heater
M305 P0 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 0 <-- This is the BED heater
M307 H0 A295.1 C361.0 D1.7 V 11.8 B0 ; Heater 0 model: gain 295.1, time constant 361.0, dead time 1.7, max PWM 1.00, calibration voltage 11.8, mode PID, inverted no, frequency default (FROM AUTO TUNE)

M143 H0 S140 ; Set temperature limit for heater 0 to 140C

M305 P1 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 1 <-- This is the Extruder heater
M307 H1 A534.6 C162.1 D4.8 V23.9 B0 ; Heater 1 model: gain 330.0, time constant 93.7, dead time 3.9, max PWM 1.00, calibration voltage 23.9, mode PID, inverted no, frequency default
;M307 H1 A330.0 C93.7 D3.9 V23.9 B0 <-- this is origional

gain 534.6, time constant 162.1, dead time 4.8, max PWM 1.00, calibration voltage 23.9, mode PID, inverted no, frequency default

M143 H1 S240 ; Set temperature limit for heater 1 to 245C
;------------------------------------------------------------------------------------------------------------------
; Fans
M106 P1 T45 H1 B5 ; Set Fan 1 (Hot end fan) Thermostatic Control set to 45c
;------------------------------------------------------------------------------------------------------------------
; Tools
M563 P0 D0 H1 ; 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
;------------------------------------------------------------------------------------------------------------------
; Automatic saving after power loss is not enabled
; Custom settings are not configured
;------------------------------------------------------------------------------------------------------------------

Mogal · 18 Jan 2021, 15:43

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3S8-6J1FJ-3S06L-18JHD
Used output buffers: 3 of 24 (12 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93140 of which 416 recycled
Exception stack ram used: 320
Never used ram: 11484
Tasks: NETWORK(ready,628) HEAT(blocked,1232) MAIN(running,3736) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:04:13 ago, cause: power up
Last software reset at 2021-01-17 21:18, reason: User, spinning module GCodes, available RAM 11324 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 19.3, current 27.4, max 27.5
Supply voltage: min 23.9, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2021-01-18 07:43:07
Cache data hit count 774763253
Slowest loop: 20.72ms; fastest: 0.06ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 20.89ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8

WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address bc:dd:c2:25:a9:f9
WiFi Vcc 3.40, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25024
WiFi IP address 10.0.0.174
WiFi signal strength -37dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0

Mogal · 18 Jan 2021, 15:45

Oh! after all this time I never knew this...??

M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 320C.
Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 559C.
Error: Bad command: gain 534.6, time constant 162.1, dead time 4.8, max PWM 1.00, calibration voltage 23.9, mode PID, inverted no, frequency default
Error: Bad command: gain 534.6, time constant 162.1, dead time 4.8, max PWM 1.00, calibration voltage 23.9, mode PID, inverted no, frequency default
Error: Bad command: gain 534.6, time constant 162.1, dead time 4.8, max PWM 1.00, calibration voltage 23.9, mode PID, inverted no, frequency default

Phaedrux · 18 Jan 2021, 16:55

@Mogal said in Z motor issues (burning!):

; Heaters
;M140 H-1 ; tells the firmware there is no bed heater
M305 P0 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 0 <-- This is the BED heater
M307 H0 A295.1 C361.0 D1.7 V 11.8 B0 ; Heater 0 model: gain 295.1, time constant 361.0, dead time 1.7, max PWM 1.00, calibration voltage 11.8, mode PID, inverted no, frequency default (FROM AUTO TUNE)
M143 H0 S140 ; Set temperature limit for heater 0 to 140C
M305 P1 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 1 <-- This is the Extruder heater
M307 H1 A534.6 C162.1 D4.8 V23.9 B0 ; Heater 1 model: gain 330.0, time constant 93.7, dead time 3.9, max PWM 1.00, calibration voltage 23.9, mode PID, inverted no, frequency default
;M307 H1 A330.0 C93.7 D3.9 V23.9 B0 <-- this is origional
gain 534.6, time constant 162.1, dead time 4.8, max PWM 1.00, calibration voltage 23.9, mode PID, inverted no, frequency default

Remove the extra text after the M307 commands. I think there's a line break in there that is putting the text on a separate line that isn't commented out.

@Mogal said in Z motor issues (burning!):

Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 320C.
Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 559C.

These are just a warning.

https://duet3d.dozuki.com/Wiki/FAQ#Section_M307_Heater_1_appears_to_be_over_powered_If_left_on_at_full_power_its_temperature_is_predicted_to_reach_521C

I don't see anything else in your config that would lead to Z axis problems. Only odd thing I notice is the steps per mm for the Z axis: M92 Z4,816.665. That's oddly specific. How is it arrived at? What is your z axis like? What are the stats on the motors? Is 1200ma the right current for the motor?

Mogal · 18 Jan 2021, 17:46

Thanks for helping.

As for the Z axis steps, I have a belted gear reduction and that is what the math (and testing) worked out to be. (The Z height is very accurate)

My (now fried) stepper was: 17HM19-2004S Rated at 2.0A.
at 1200ma, the stepper produced enough power and stayed cool. (could the lower current do damage?)
I'm now using my older 1.8 stepper to get it going again. (It also worked well at 1200ma)

At this point I can only assume its the board. (disclaimer - it is a cloned board but worked great up to this point)
The 0.9 stepper is toast, the replacement 1.8 stepper is good, but only locks up (and wont turn)

When using driver #4, do I have to disable driver 2? How? Jumper pins on one/both Z motor outputs?
(Currently have jumpers on ZB, but not ZA - Z stepper plugged into Drive 4)

Thanks, That fixed the error. It was an extra line break
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 320C.
Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 559C.

A Former User · 18 Jan 2021, 17:52

@Mogal said in Z motor issues (burning!):

When using driver #4, do I have to disable driver 2? How? Jumper pins on one/both Z motor outputs?

don't have to but could be handy to supress any errors see R-1 parameter https://duet3d.dozuki.com/Wiki/Gcode#Section_M569_Set_motor_driver_direction_enable_polarity_and_step_pulse_timing

Also the jumpers on the Zb are just there because Za and Zb are in series for dual Z motors. When using just the one motor the jumpers are essentially bypassing Zb in order to get the current to Za. Doesn't affect the other drivers.

Mogal · 18 Jan 2021, 18:46

So weird.

Okay, I have disconnected all my belts for safety sake.

For more testing, I've switched the steppers around (Z to X)
Z motor moves (from the X driver(0) and X doesn't (on Driver 2 or 4 with appropriate config changes) so steppers are good, but the commands doesn't seem to follow on either driver 2 or 4 (just locks up)

At this point, I know the motors are good, but for whatever reason driver 2 and driver 4 just wont drive the Z axis anymore (just locks up)

So I'm going to conclude its a bad board as I am lost on how to test further.
I've ordered another clone. At the least this board could (and will) get used for a Sable table (only need XY)
Hopefully the new board will put the printer back in operation. But it'll be down for a month till the board arrives

Thanks again.

Phaedrux · 18 Jan 2021, 18:53

Please share your current config.g

It doesn't make sense that the X motor will work on the X drive when configured as X, but not when configured as Z.

Mogal · 18 Jan 2021, 22:05

Here is the current config. (Note the very last line?)

And thanks again!

Board: Duet WiFi 1.02 or later
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.05.1 (2020-02-09b1)
Duet WiFi Server Version: 1.23

;-----

; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up

;------------------------------------------------------------------------------------------------------------------

; Custom Configuration - Set drive mapping
M584 X0 Y1 Z4 E3 ; Set X to Drive 0 - Set Y to Drive 1 - Set Z motor to drive 4 - Extruder to Drive 3

;------------------------------------------------------------------------------------------------------------------
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M667 S1 ; Select CoreXY mode
;------------------------------------------------------------------------------------------------------------------
; Network
M550 P"Mogal's CoreXY"\ ; Set machine name
M552 S1 ; Enable network
M587 S"MyFi" P"********" ; Configure access point. You can delete this line once connected
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet
;------------------------------------------------------------------------------------------------------------------
; Drives
M569 P0 S0 ; Drive 0 goes backwards (X) ; MM/Sec MM/Min
M569 P1 S0 ; Drive 1 goes backwards (Y) ; 1 60
M569 P4 S0 ; Drive 4 goes backwards (Z) ; 10 600
M569 P3 S0 ; Drive 3 goes backwards (E) ; 20 1200
M350 X16 Y16 Z16 E16 I1 ; Configure micro stepping with interpolation ; 30 1800
M92 X200.00 Y200.00 Z4,816.665 E320 ; Set steps per mm 4,816.665 9,633.33 ; 40 2400
M566 X500 Y500 Z20 E3600 ; Set maximum instantaneous speed changes (mm/min) -This is Jerk- ; 50 3000
M203 X12000.00 Y12000.00 Z300.00 E12000.00 ; Set maximum speeds (mm/min) ; 60 3600
M201 X3600.00 Y3600.00 Z50.00 E10000.00 ; Set accelerations (mm/s^2) ; 70 4200
;M204 P1000 T3000 ; Print and Travel accelerations ; 80 4800
M906 X1200.00 Y1200.00 Z1800.00 E1200.00 I30 ; Set motor currents (mA) and motor idle factor in per cent ; 90 5400
M84 S10 ; Set idle timeout (10 Seconds) ; 100 6000
;M572 D0 S0.15 ; Pressure advance (Original Value: 0.15)
;------------------------------------------------------------------------------------------------------------------
; Axis Limits
M208 X0 Y20 Z0 S1 ; Set axis minimal
M208 X310 Y350 Z400 S0 ; Set axis maximum
;------------------------------------------------------------------------------------------------------------------
; Endstops
M574 X1 Y2 S1 ; Set active high endstops

; Z-Probe
M574 Z2 S2 ; Set endstops controlled by probe
M558 P5 H5 Z1 I1 F200 T6000 ; Set Z probe type to modulated and the dive height + speeds
G31 P500 X30 Y00 Z2.72 ; Set Z probe trigger value, offset(X, Y) and trigger height <-- Higher number brings closer to bed, Lower Number is further away!
M557 X30:330 Y30:360 S50 ; Define mesh grid
;------------------------------------------------------------------------------------------------------------------
; Heaters
;M140 H-1 ; tells the firmware there is no bed heater
M305 P0 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 0 <-- This is the BED heater
M307 H0 A295.1 C361.0 D1.7 V 11.8 B0 ; Heater 0 model: gain 295.1, time constant 361.0, dead time 1.7, max PWM 1.00, calibration voltage 11.8, mode PID, inverted no, frequency default (FROM AUTO TUNE)

M143 H0 S140 ; Set temperature limit for heater 0 to 140C

M305 P1 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 1 <-- This is the Extruder heater
M307 H1 A534.6 C162.1 D4.8 V23.9 B0 ; Heater 1 model: gain 330.0, time constant 93.7, dead time 3.9, max PWM 1.00, calibration voltage 23.9, mode PID, inverted no, frequency default
;M307 H1 A330.0 C93.7 D3.9 V23.9 B0 <-- this is origional gain 534.6, time constant 162.1, dead time 4.8, max PWM 1.00, calibration voltage 23.9, mode PID, inverted no, frequency default

M143 H1 S240 ; Set temperature limit for heater 1 to 245C
;------------------------------------------------------------------------------------------------------------------
; Fans
M106 P1 T45 H1 B5 ; Set Fan 1 (Hot end fan) Thermostatic Control set to 45c
;------------------------------------------------------------------------------------------------------------------
; Tools
M563 P0 D0 H1 ; 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
;------------------------------------------------------------------------------------------------------------------
; Automatic saving after power loss is not enabled
; Custom settings are not configured
;------------------------------------------------------------------------------------------------------------------

Phaedrux · 18 Jan 2021, 22:38

Add M569 P2 R-1 to disable driver2 and keep it from sending any error messages.

Now with your Z axis connected to driver 4 (E1) it should be able to be driven if the motor is working.

If you still have problems driving it in this configuration, capture another M122 after trying to move it and post it.

Mogal · 19 Jan 2021, 00:43

@Mogal said in Z motor issues (burning!):

M92 X200.00 Y200.00 Z4,816.665 E320 ; Set steps per mm 4,816.665 9,633.33 ; 40 2400

OMG I am such an idiot!

See the comma in that 4,816.666?!?! I guess its recognized a 4 NOT 4,816.666!
So the motor WAS turning, but so slowly I couldn't tell. ( thought it was just locked up)
I thought I would wait for the homing timeout on Z, but it never happened, so upon closer look I was able to tell what was happening...

Sorry... I'll go hang my head in shame now!

Thanks!

Phaedrux · 19 Jan 2021, 00:44

That's a touch one to spot. Glad you figured it out.

Sending M92 might have been informative.