Warning: motor phase A may be disconnected reported by driver(s)
-
Getting these warnings while running my homing
6:48:33 PMWarning: motor phase A may be disconnected reported by driver(s) 4
Warning: motor phase B may be disconnected reported by driver(s) 4
6:48:19 PMWarning: motor phase A may be disconnected reported by driver(s) 4
Warning: motor phase B may be disconnected reported by driver(s) 4
6:46:39 PMWarning: motor phase A may be disconnected reported by driver(s) 4
Warning: motor phase B may be disconnected reported by driver(s) 4
6:46:22 PMWarning: motor phase A may be disconnected reported by driver(s) 4
Warning: motor phase B may be disconnected reported by driver(s) 4
6:46:15 PMWarning: motor phase A may be disconnected reported by driver(s) 4
Warning: motor phase B may be disconnected reported by driver(s) 4Nothing seems to be failing, just flashing all over my screen
Hypercube Evolution 300x300x400 dual zed
(moved complete config to reply below, as i had my config mirrored and corrected that for another issue but still see these warnings all the time during homing/movement)
sometimes #2 motor does it as well - #2 and #4 i believe are my Z motors.
Diagnostics isn't showing much warning
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MSJ-6JTD6-3SN6L-1TRR9
Used output buffers: 1 of 20 (17 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98596 of which 0 recycled
Exception stack ram used: 512
Never used ram: 6440
Tasks: NETWORK(ready,648) HEAT(blocked,1232) MAIN(running,3844) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:03:52 ago, cause: software
Last software reset at 2019-04-30 18:27, reason: User, spinning module GCodes, available RAM 6520 bytes (slot 1)
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 33.0, current 33.3, max 33.6
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 0/833
Driver 1: standstill, SG min/max 16/855
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: 2019-04-30 18:31:24
Cache data hit count 866051605
Slowest loop: 3.22ms; fastest: 0.08ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 238, MaxWait: 156687ms, Underruns: 0, 0
Scheduled moves: 16, completed moves: 16
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 2 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: 202.49ms; fastest: 0.08ms
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 1
WiFi firmware version 1.22
WiFi MAC address 80:7d:3a:3f:f3:25
WiFi Vcc 3.41, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 28032
WiFi IP address 192.168.50.56
WiFi signal strength -68dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
-
have you checked the crimping work with a multimeter?
-
Please post your complete config.g file and your homing files.
-
; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2 on Fri Nov 30 2018 17:18:07 GMT-0700 (Mountain Standard Time); General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder movesM667 S1 ; Select CoreXY mode
; Network
M550 P"HEVO" ; Set machine name
M551 P"noway" ; Set password
M552 S1 ; Enable network
M587 S"not" P"real" ; 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 S1 ; Drive 0 goes backwards
M569 P1 S0 ; Drive 1 goes backwards
M569 P2 S1 ; Drive 2 goes backwards
M569 P3 S0 ; Drive 3 goes backwards
M569 P4 S1 ; Drive 4 goes backwards
M584 X0 Y1 Z2:4 E3 ; Drive 0 controls X, Drive 1 controls Y, Drive 2:4 controls Z, Drive 3 controls E
; Motor order: Left (1), Right (2)
M671 X-35:335 Y150:150 S3 ; Location of the Lead Screws
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80 Y80 Z400 E804 ; Set steps per mm
M566 X600.00 Y600.00 Z120.00 E120.00 ; Set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z180.00 E1200.00 ; Set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z20.00 E550.00 ; Set accelerations (mm/s^2)
M906 X1000.00 Y1000.00 Z1400.00 E800.00 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S50 ; Set idle timeout; Axis Limits
M208 X5 Y5 Z0 S1 ; Set axis minima
M208 X285 Y295 Z390 S0 ; Set axis maxima; Endstops
M574 X1 S3 F0 R0 ; Set active High endstops (S1=SENSORED) (X-MIN(1)) (S3=SENSORLESS)
M574 Y1 S1 ; Set active High endstops (S1=SENSORED) (Y-MIN(1)) (S3=SENSORLESS)
M574 X1 S3 ; Set endstops controlled by motor load detection
M574 Z1 S2 ; Use zprobe and home to min
M915 X Y S7 R0 F0 ; set X and Y to sensitivity 7, do nothing when stall, unfiltered; Z-Probe
M574 Z1 S2 ; Set endstops controlled by probe
M307 H3 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
M558 P9 H5 F120 T6000 ; Set Z probe type to bltouch and the dive height + speeds
G31 P25 X-24 Y-19 Z0.27 ; Set Z probe trigger value, offset and trigger height
M557 X25:250 Y25:250 S75:75 ; Define mesh grid; Heaters
;M140 H-1 ; Disable heated bed
M305 P0 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S280 ; Set temperature limit for heater 1 to 280C; Fans
M106 P0 S1 I0 F500 H1 T30 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off M106 P0 T45 H1
M106 P1 S1 I0 F500 H1 T30 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off; 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
-- homeall
; homeall.g
; called to home all axes
;; Home Y First
M400 ; make sure everything has stopped before we make changes
M913 X55 Y55 ; reduce motor current to 55% to prevent belts slipping
G91 ; relative positioning
G1 Z10 F4800 S2 ; lift Z relative to current position
G4 P500 ; wait 500msec
M400
G1 S1 Y-430 F4800 ; move quickly to X or Y endstop and stop there (first pass)
M400
G4 P500 ; wait 500msec
G1 Y10 ; Move Away 10mm X axis
M400
G4 P500 ; wait 500msec
;G1 Z-5 F6000 S2 ; lift Z relative to current position
;G90 ; absolute positioning
;M400 ; make sure everything has stopped before we reset the motor currents
;M913 X100 Y100 ; motor currents back to normal; Home X Second
M400 ; make sure everything has stopped before we make changes
G1 S1 X-305 F4800 ; move quickly to X or Y endstop and stop there (first pass)
M400
G4 P500 ; wait 500msec
G1 X10 ; Move Away 10mm X axisG90 ; absolute positioning
M400 ; make sure everything has stopped before we reset the motor currents
M913 X100 Y100 Z100 ; motor currents back to normal;Home Z Last
G1 X150 Y150 F6400 ; go to first probe point
M400
G4 P500 ; wait 500msec
G30 ; home Z by probing the bed--
; homex.g
; called to home the X axis
;
M400 ; make sure everything has stopped before we make changes
M913 X45 Y45 ; reduce motor current to 45% to prevent belts slipping
G91 ; relative positioning
G1 Z10 F4800 S2 ; lift Z relative to current position
G4 P500 ; wait 500msec
M400
G1 S1 X-305 F4800 ; move quickly to X or Y endstop and stop there (first pass)
M400
G4 P500 ; wait 500msec
G1 X10 ; Move Away 10mm X axis
M400
G4 P500 ; wait 500msec
G1 Z-10 F6000 S2 ; lift Z relative to current position
G90 ; absolute positioning
M400 ; make sure everything has stopped before we reset the motor currents
M913 X100 Y100 Z100 ; motor currents back to normal; homex.g
; called to home the X axis
;
M400 ; make sure everything has stopped before we make changes
M913 X45 Y45 ; reduce motor current to 45% to prevent belts slipping
G91 ; relative positioning
G1 Z10 F4800 S2 ; lift Z relative to current position
G4 P500 ; wait 500msec
M400
G1 S1 X-305 F4800 ; move quickly to X or Y endstop and stop there (first pass)
M400
G4 P500 ; wait 500msec
G1 X10 ; Move Away 10mm X axis
M400
G4 P500 ; wait 500msec
G1 Z-10 F6000 S2 ; lift Z relative to current position
G90 ; absolute positioning
M400 ; make sure everything has stopped before we reset the motor currents
M913 X100 Y100 Z100 ; motor currents back to normal; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v2 on Fri Nov 30 2018 17:18:08 GMT-0700 (Mountain Standard Time)
G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
G90 ; absolute positioning
G1 X150 Y150 F6400 ; go to first probe point
G30 ; home Z by probing the bed
G1 Z10 F6000 ; Rapidly move the Z axis to Z=10.; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 S2 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning -
@veti going to check this now, that was recommended by someone on facebook
-
I don't see anything in your config.g or homing files that would explain the problem, but you have a higher Z motor current than X and Y. What is the specification of your Z motors?
-
1.7 A/phase 82gcm2 1.8hms 3.06v from Zyltech. I'll drop the ma down to match the rest and see if that helps.
I disconnected the Z rods and did flags on them to make sure i wasn't missing anything obvious and they spin the right way (but 4 still complains)
When you have dual z - does #2 and #4 match any of the pins on the duet specifically? like is it the top or bottom pins or right or left motor by convention?
-
i printed benchy and i don't see this error while printing - only before and after. I have a different nema 17 I'll experiment with and see if a potential wiring problem is internal to motor. i recrimped ends to make sure it wasnt the plug directly to duet
-
Same problem here. 2 nema 17 in series, duet maestro, 12v, with all the currents, speeds and firmware versions.
Warning: motor phase A may be disconnected reported by driver(s) 2 going UP
Warning: motor phase B may be disconnected reported by driver(s) 4 going DOWN
Only stops whe using M569 P2 V670 or bigger value. But the motors are too noise to keep that value. -
@cata said in Warning: motor phase A may be disconnected reported by driver(s):
Only stops whe using M569 P2 V670 or bigger value.
I guess that stealthChop is interfering with the open-load detection then. Can you confirm that you are running firmware 2.02 or later? Do you have the specification of the motors? If they are low-current motors then to keep them quiet, you may need to connect them in parallel instead of in series, or connect them to separate stepper drivers.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 tested in all 2.03 betas and 2.02 stable.
Motors are low current, no data of the model or manofacturer.
Connected in parallel today, same warning with some "largue movements", 25 - 50 mm in one command.
Cant use another driver, dual extruder is setted -
@cata
try reducing the maximum speed of the z axis. -
@dc42 I am running latest firmware when i get this warning - only on faster movements. WHile printing i'm not seeing it.
-
@veti from 360 to 180 and now dont see the warning.
Then i cant use motors in series? Whats the point of the warning if my motors works well? -
stealthchop2 has drastically reduced torque on 12v. you will need to upgrade to 24v.
there is an extensive video about it. https://www.youtube.com/watch?v=GVs2d-TOims -
I'm already 24v
-
@cata said in Warning: motor phase A may be disconnected reported by driver(s):
Same problem here. 2 nema 17 in series, duet maestro, 12v, with all the currents, speeds and firmware versions.
Warning: motor phase A may be disconnected reported by driver(s) 2 going UP
Warning: motor phase B may be disconnected reported by driver(s) 4 going DOWN
Only stops whe using M569 P2 V670 or bigger value. But the motors are too noise to keep that value.Driver 4 is the E1 motor output. What do you have connected to that output?
When you connected the motors in parallel instead of in series, were you able to use a larger M569 P2 V parameter without the motors becoming too noisy?
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 said in Warning: motor phase A may be disconnected reported by driver(s):
Driver 4 is the E1 motor output. What do you have connected to that output?
Mistiping, both warnings are for driver 2
@dc42 said in Warning: motor phase A may be disconnected reported by driver(s):
When you connected the motors in parallel instead of in series, were you able to use a larger M569 P2 V parameter without the motors becoming too noisy?
No, same noise
-
I've changed the code in firmware 2.03RC1 to disable the open load detection when in stealthChop mode. I expect to release that version later today or tomorrow.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Thanks, i dont run for this but prefer to avoid the warning flood.
I will test again the conbinations when release the new firm.
