Phase A may be disconnected.
-
Whenever I try to home the x/y axis it gives me an error message: Warning: motor phase A may be disconnected reported by driver(s)
anI checked all the connections and the polarity is correct(I will attach the sheet and picture to verify this). I tried different motors to no avail and I made sure that my config is correct which I will also attach.
The only thing that happens is that when I home from the duet web control, one of the motors starts to vibrate but not on the paneldue control
Here are the images
-
@mrcat07 does your motor have a connector on it or is it hardwired? either you have a broken wire, bad connector/crimp or your motor plug is wired incorrectly at a guess.
-
@jumpedwithbothfeet Yes it has a connector. It does come it out when I yank it even when crimped properly because of the fact that the spring on the crimp end is not very strong. But even when i replace it with a precrimped motor from filastruder, nothing works.
If you looked at the diagram I put in the imgur as well as the image, all of the connections are properly done so this issue is very frustrating for me.
-
I suggest you use this method for identifying which wire pairs are which and then wire accordingly.
-
@Phaedrux I did that and all the connections are correct, the motor is hard to rotate when the polarities are on either side just like on the wiring guide. Still doesnt work.
-
What do your crimps look like?
Is this a new build or was this previously working?
-
@Phaedrux This is a new build.
When I put a motor that already that connector out of the box, it still doesnt work which indicates that with good crimps it still isnt working.
When I connect the motor that is on the actual machine itself and I put the command to home x, it moves slightly forward, stops then says the phase error.
-
Have you tried remapping the X axis to a different driver and testing to see if the problem remains?
-
@Phaedrux Did that - still doesnt work unfortunently
-
@mrcat07 said in Phase A may be disconnected.:
Your image shows the motor plugged into driver 4 on the Duet board, but your config.g shows no M569 command for driver 4, and that driver 4 is not assigned to any axis with M584. Most likely you have mis-identified where the motors driver outputs are, and don't have a motor plugged into Driver 0. Note driver 0 (defined as the X axis by config.g) is the driver output furthest from the SD card socket. See the wiring diagram https://docs.duet3d.com/Duet3D_hardware/Duet_3_family/Duet_3_Mini_5+_Hardware_Overview#wiring-diagram
... ; Smart Drivers M569 P0.0 S1 D2 ; driver 0.0 goes forwards (X axis) M569 P0.1 S1 D2 ; driver 0.1 goes forwards (Y axis) M569 P0.2 S1 D2 ; driver 0.2 goes forwards (Z axis) M569 P0.3 S1 D2 ; driver 0.3 goes forwards (extruder 0) ... ; Axes M584 X0.0 Y0.1 Z0.2 ; set axis mapping ...Ian
-
Even when I switch those around to allow for the driver near the sd card, I still see no movement unfortunently. I did think that this was the problem earlier and still had no luck.
