What is the best way to destroy the Duet2 motor driver?

A Former User

This post is deleted!

kotuo

@phaedrux Thank you for your reply.
I am getting the following error statement for all motors when I do a home-all.
Warning: Motor phase A may be disconnected as reported by driver 2.
Warning: Motor phase B may be disconnected as reported by driver 2.
The extruder drivers (E0, E1) have not been checked.
Results of M122 investigation

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9X6JA-JUNSN-6JKDJ-3S86N-TTRRU
Used output buffers: 3 of 24 (11 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 73360 of which 24 recycled
Never used RAM 15236, free system stack 191 words
Tasks: NETWORK(ready,173) HEAT(blocked,308) MAIN(running,467) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:30 ago, cause: software
Last software reset at 2021-06-12 12:40, reason: User, GCodes spinning, available RAM 15200, slot 1
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.1, max 36.5
Supply voltage: min 23.8, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-06-12 12:40:32
Cache data hit count 35451813
Slowest loop: 4.01ms; fastest: 0.21ms
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 0.6ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.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: 15.60ms; fastest: 0.00ms
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 0
WiFi firmware version 1.25
WiFi MAC address 3c:61:05:d2:7a:4f
WiFi Vcc 3.39, reset reason Power up
WiFi flash size 4194304, free heap 24600
WiFi IP address 192.168.1.101
WiFi signal strength -41dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

My config.g

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat Jun 12 2021 11:49:21 GMT+0900 (日本標準時)

; General preferences
G90                                            ; send absolute coordinates...
M83                                            ; ...but relative extruder moves
M550 P"＊＊＊＊＊"                                ; set printer name

; Network
M551 P"kotuo"                                  ; 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 S0                                     ; physical drive 1 goes backwards
M569 P2 S0                                     ; physical drive 2 goes backwards
M569 P3 S1                                     ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3                               ; set drive mapping
M350 X32 Y32 Z32 I0                            ; configure microstepping without interpolation
M350 E16 I1                                    ; configure microstepping with interpolation
M92 X160.00 Y160.00 Z8000.00 E369.00           ; set steps per mm
M566 X600.00 Y600.00 Z60.00 E300.00            ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z300.00 E6000.00        ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z100.00 E500.00           ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30                   ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                        ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1                               ; set axis minima
M208 X300 Y300 Z300 S0                         ; set axis maxima

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

; Z-Probe
M558 P0 H5 F120 T6000                          ; disable Z probe but set dive height, probe speed and travel speed
M557 X10:220 Y10:220 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 B1 S1.00                               ; enable 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 S260                                   ; set temperature limit for heater 1 to 260C

; Fans
M950 F0 C"fan0" Q500                           ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0.8 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 S"PLA" 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
M575 P1 S1 B57600                              ; enable support for PanelDue
M501                                           ; load saved parameters from non-volatile memory
T0                                             ; select first tool

I have not set up any macros, so
When I run M98P "config.g", I get an error.

M98P "config.g"
Warning: Macro file  "config.g" not found

Maximum voltage of the motor
Nidec [KV4239/KF4242] is not listed in the current datasheet, so I guessed from the latest version of the model number: 2A.

C17HD2020, no datasheet found, probably: ２A

dc42

@kotuo please measure the resistance of each motor phase, also measure the length of the motors. From those figures we can estimate the motor characteristics by comparing them with other similar motors.

Is this ab existing 3D printer than you have upgraded to Duet? If not, where did the motors come from?

Are you using 12V or 24V power?

kotuo

@dc42 Thank you for your reply.
The motor I'm using is an existing motor.
The power supply is 24v.

Nidec : KV4239 A,0.64Ω　B,0.64 Ω

C17HD02 A, 0.63Ω　B,0.63 Ω

Nidec: KF4242 A,11.6Ω　B,11.6Ω

dc42

@kotuo thanks. What is the length of those motors, not counting the shaft?

The Nidec KF4242 motor has a high per-phase resistance. It is either not suitable for use in a 3D printer, or it needs a low current. If connected to a Duet with the current set too high, the Duet might well give "phase may be disconnected" warnings for the driver it is connected to.

BoA

@kotuo I see disconnection reported only for driver 2 - which drives Z axis. Do You have jumpers on the second Z motor connector?

kotuo

@dc42 Thank you for your reply.
Size of the motor

KV4239
Red line 42mm
Blue line 42mm
Green dot (length without shaft) 38mm

C17
Red line 42.4mm
Blue line 42.4mm
Green point (length excluding shaft) 39mm

KF4242
Red line 43mm
Blue line 43mm
Green line (length excluding shaft) 39mm

kotuo

@boa Thanks for your reply.
I have the jumper on the second Z-axis.

Phaedrux

@kotuo said in What is the best way to destroy the Duet2 motor driver?:

M98P "config.g" Warning: Macro file "config.g" not found

You have the space in the wrong place, should be M98 P"config.g"

kotuo

@phaedrux Thank you very much.
It was a short sentence, so typing it by hand was a big mistake.
Here is the result
M98 P "config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled

Veti

@kotuo
are you sure that red and green are one phase?
because normally red and blue are one phase

kotuo

@veti Thank you for pointing this out.
I have no choice but to change the order of the cables because the cables I am using are twisted on the motor side and I do not have the terminals on the motor side.

dc42

@kotuo said in What is the best way to destroy the Duet2 motor driver?:

Green point (length excluding shaft) 39mm

Thanks, it's a 39mm Nema 17 motor then.

To get an idea of the characteristics, go to https://www.omc-stepperonline.com/nema-17-stepper-motor/. Set he unipolar/bipolar filter to Unipolar, the Body Length filter to a range that is close to the motor length e.g. 39 to 40mm, and set the Phase Resistance filter to a value that covers the 11.6 ohm resistance that you measured.

The closest one I found was this one https://www.omc-stepperonline.com/nema-17-stepper-motor/nema-17-bipolar-1-8deg-36ncm-51oz-in-0-85a-5-4v-42x42x39mm-4-wires. It has the same length but the phase resistance is 6.3 ohms.

To account for the different in phase resistance, we can assume that for the same motor size, inductance is proportional to phase resistance, rated current is inversely proportional to the square root of phase resistance, and phase voltage is proportional to the square root of phase resistance. This suggests the following approximate values for that motor:

Inductance 18.4mH
Phase voltage at rated current 7.3
Rated phase current 0.63A

EDIT: is that the Z motor? Is there just one Z motor, or are there two? If there are two, how have you connected them to the Duet?

dc42

@kotuo said in What is the best way to destroy the Duet2 motor driver?:

@veti Thank you for pointing this out.
I have no choice but to change the order of the cables because the cables I am using are twisted on the motor side and I do not have the terminals on the motor side.

There are at least two different phase pinouts used on stepper motors with 6-pin JST connectors. This means that if the cable was not supplied with the motor, the colours may well be wrong, as you have discovered.

kotuo

@dc42 Thank you for your reply.
I am using only one Z axis.

dc42

@kotuo what motor current have you set for the Z axis in your M906 command in config.g? You will need to use 600mA or less with that motor. If you set a much higher current, then you can expect to see those "phase may be disconnected" warnings, because the drivers will be unable to provide the requested current to that high resistance motor.

kotuo

@dc42 Thank you for your reply!
I will lower the motor current to 600 with RRF and upload the zip file to Duet.