Error: Driver 0.4 error: phase A short to Vin
-
Hi all,
We are using Duet 3 Mini5+ Wifi with Panel Due 4.3
CoreXY Architecture
X&Y - Motech MT-1704HSM168RE (0.9deg, 4.4kg Torque)
Z (Left and Right) - MT-1705HS200AE (1.8, 8.2kg Torque)9mm Belt Driven Hiwin C7 12mm Ball screws with 40teeth pulley.
We are using for last 45 days without any issues. This is planned for high speed machine targeting 300mm/s print speed.
Since 2 days the Right side Z was giving issue. Withy any given 3d print, the right side was having gaps. We thought of slicer issue. Checked with S3d and Cura. Still the same issue.
Yesterday, we got this warning issue 'Error: Driver 0.4 error: phase A short to Vin'.
We read in the forum and someone told the driver may be a problem.
We changed some config values
M566 X1000.00 Y1000.00 Z18.00 E300.00 ; Previously Z42
M203 X18600.00 Y18600.00 Z300.00 E7200.00 ; Didnt change
M201 X6000.00 Y6000.00 Z120.00 E10000.00 ; Previously Z300Then we gave another print. We received another warning 'Warning: Driver 0.4 warning: over temperature warning'
This is how we have attached a cooling fan to the board. Today we replaced the board cooling fan and one more test print was given.
It starts printing normally. After 3-4mm height, Z Right was giving issues.
'Driver 0.4 warning: phase B may be disconnected'
Another time 'Warning: Driver 0.4 warning: phase A may be disconnected'Now when moving, it behaves oddly. Moving up, makes it move up and down randomly
M122 Report:
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.0 (2022-03-15 18:59:15) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 3QG0R-2396U-D65J0-40KMU-3V03Z-7M8BT
Used output buffers: 9 of 40 (29 max)
=== RTOS ===
Static ram: 103684
Dynamic ram: 110356 of which 180 recycled
Never used RAM 27420, free system stack 158 words
Tasks: NETWORK(ready,15.0%,226) HEAT(notifyWait,0.0%,358) Move(notifyWait,0.0%,292) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,372) CanClock(delaying,0.0%,339) TMC(notifyWait,0.7%,114) MAIN(running,83.4%,414) IDLE(ready,0.1%,29) AIN(delaying,0.8%,273), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:07:27 ago, cause: software
Last software reset at 2022-07-01 12:23, reason: User, GCodes spinning, available RAM 27420, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 447755, completed 447754, timed out 0, errs 0
Step timer max interval 1489
MCU temperature: min 36.1, current 36.8, max 37.0
Supply voltage: min 23.9, current 24.0, max 24.0, 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: 0 queued, 0 completed
Driver 0: standstill, SG min 2, read errors 0, write errors 1, ifcnt 67, reads 23542, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 2, read errors 0, write errors 1, ifcnt 67, reads 23542, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 88, reads 23535, writes 16, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 59, reads 23541, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 88, reads 23535, writes 16, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2022-07-01 12:31:21
Cache data hit count 840517802
Slowest loop: 19.47ms; fastest: 0.13ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.3ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 3, maxWait 204771ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 32, completed 32, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 32], 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 0 -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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== CAN ===
Messages queued 4028, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 2239/0/0
Tx timeouts 0,0,2238,0,0,1788 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 21.50ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 2 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.26
WiFi MAC address f0:08:d1:03:81:f4
WiFi Vcc 3.35, reset reason Power up
WiFi flash size 2097152, free heap 25440
WiFi IP address 192.168.29.205
WiFi signal strength -56dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
We interchanged from Z-Left to Right. Drive 4 to 2 and 2 to 4.
We started the print.
It gave this error
'Warning: Driver 0.2 warning: over-temperature warning, phase B short to Vin
Error: Driver 0.2 error: over-temperature shutdown, phase B short to Vin
Error: Driver 0.2 error: over temperature shutdown'The motor which was connected previously in 4 is now in 2. So, the error is showing for Drive 0.2
We changed the motor cable and we tried.
It is now creating another issue . 'Error: Driver 0.3 error: phase B short to Vin' (3 goes to extruder)
Oops.. Tired.
- WiFi -
-
-
@selva_tvi if the previous one followed the motor rather than the driver then that definitely points to a wiring/motor issue and it could well be the same for the extruder.
I suggest revisiting your wiring to ensure all crimps are correct, there's no continuity issues etc -
@jay_s_uk XY motors are from Motech (bought from E3d) and the Extruder motor is Orbiter 2.
It came with the proper wiring and we used as it is. And it was working with out any issues.
So, theissue is only with motor?
All the issues are suddenly occurring.
It was observed by Wednesday night.
Yesterday we added an accelerometer. All the wires were properly checked and connected. Installed the Input shaping plugin also. It recorded the motion. While recording the Z was somewhat abnormal.
After that the issues started.
'phase B short to Vin' - what exactly is the issue? After running for 45 days suddenly one by one issues are coming.
Is there any changes I have to make with Config?
-
@jay_s_uk ok. Finally got the solution. The wire was the problem. After changing the wires the issue was solved.
Is there any link which will show all the errors and solutions?
These words 'phase B short to Vin' just threatened me.Thanks for your support.
-
@selva_tvi short to vin and short to ground pretty much point to an issue with wiring, unless you've managed to damage the driver.
I'm not sure there's an exhaustive list of issues and fixes
