Error "Driver x.x error: phase A to Vin"
-
I'm getting some odd behavoir with a couple of motors on my 3D printer. One displays this message with corresponding judder of the motor. The other doesnt give a message but the motor doesn't move or make make a noise.
I know there will be shouts of Check Your Wiring. But I've checked all phases on the motor, checked the cables and physical condition of connectors and nothing seems wrong, I understand that it could be a transient problem.
But here's the thing: these problems only happen occasionally and only during homing and other startup routines. If I switch off and restart, then (so far) everything is fine until maybe a few days later when I see it again. It has never happened during a print.
Surely if it was a wiring problem then the problem is more likely to occur during the hours of printing rather than restricted to the few minutes of startup?
I have a Rat-Rig core XY printer which has three Z motors The problem is occurs on one of the XY motosr and one of the Z motors. The error in the title is attributed only to the XY motor. The Z axis motor just doesnt move and so the bed levels unevenly with no warning message.
I have a Duet 3 Mini with latest firmware.
-
Please post your config.g and the results of M122.
Do you have the specs of the motors?
Are you able to reproduce the error consistently? Can you post the macros used that produce it?
-
Here are the files:
Config.txt
HomeAll.txt
M122.txtThe motors are NEMA 17, 48mm. Specs:
- Manufacturer: LDO
- Model: LDO-42STH48-2504AC
- Holding Torque: 5.5 Kgf-cm - 76oz-in
- Shaft: 5mm
- Voltage rating: 3.1V
- Stepping angle:1.8 degrees
- Current rating: 2.5A/Phase
- Connector type: JST PH-6
The problem is not repeatable. The motor faults as described happen independently and infrequently. They have only happened during a homing routine. Once the fault occurs, I have to reset the machine and then everything is okay for a few more days. I have never had the faults during a print. I have checked the motor phases and cables but I can't see anything problemmatic.
-
You have the 2+ driver expansion for the Duet3mini?
I don't see anything obvious from your files.
Can you try copying and pasting the contents of your homeall.g one at a time into the gcode console and executing it? Can you tell where in the file it seems to generate an error?
If I had to guess I would say that it sounds like there is a intermittent cable break that only comes into play based on the position of the print head.
Since it only seems to happen during homing you may want to use the config tool to generate a fresh set of config files and giving those a try.