Warning: phase A may be disconnected...
-
I am busy upgrading to v3.4.4 from v2 and after doing so (via V3.0.0) I get the warning above whenever I use the Dashboard to move an axis by 50mm. I don't see to get this warning when moving 1mm or 10mm.
What is the cause of this warning and how can I resolve this?
"Warning: Driver 1 warning: phase A may be disconnected, phase B may be disconnected"
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.4 (2022-10-20 16:17:41) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MS8-6J9D4-3SN6P-1TV39
Used output buffers: 1 of 26 (12 max)
=== RTOS ===
Static ram: 23860
Dynamic ram: 72964 of which 68 recycled
Never used RAM 15044, free system stack 134 words
Tasks: NETWORK(notifyWait,14.6%,211) HEAT(notifyWait,0.0%,388) Move(notifyWait,0.0%,304) MAIN(running,85.0%,456) IDLE(ready,0.4%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:04:23 ago, cause: software
Last software reset at 2022-11-29 17:46, reason: User, GCodes spinning, available RAM 15044, 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
Step timer max interval 0
MCU temperature: min 28.0, current 28.9, max 29.2
Supply voltage: min 24.0, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 4 queued, 4 completed
Driver 0: standstill, SG min 136
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min 0
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2022-11-29 17:50:44
Cache data hit count 4294967295
Slowest loop: 9.65ms; fastest: 0.18ms
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 1.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 6, maxWait 29726ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 51, completed 51, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 41], 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 -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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Network ===
Slowest loop: 12.58ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
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.27
WiFi MAC address cc:50:e3:0d:1c:38
WiFi Vcc 3.35, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25632
WiFi IP address 10.0.1.2
WiFi signal strength -78dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0 -
@duncang its usually wiring. best to re-check the crimping for that motor
-
@jay_s_uk Thanks - dumber than that - drive not connected !! Was running a test on Drive 0 so not sure why Drive 1 was throwing a Warning since it was not used at all.
Anyway thanks - just need to make sure Drive 0 and Drive 1 are connected. Doesn't seem to mind not having Z axis connected.
-
undefined dc42 marked this topic as a question
-
undefined dc42 has marked this topic as solved
