Stepper motors vibrating but not turning

percar

connect up the motor directly to the stepper driver
Check the continuity of the wires while not connected to anything
There will be two pairs of wires that have continuity. The one pair will be A (A1 wire and A2 wire) coil and the other pair will be the B (B1 wire and B2 wire) coil

The wiring will be for the pair A1 and A2 and the B1 an B2 The connector is in that order
If the motor runs when connected directly then the may be an issue with the other wires
If you have self crimped make sure that the crimp is good and that the pins have been pushed in all the way. IF one of the wires is not making contact then it will just vibrate

droftarts

@terrytao your firmware is RRF 2.02, but your config.g is for RRF 3. Either update the firmware, or create a config.g for RRF2. To update, download 3.0 zip first from https://github.com/Duet3D/RepRapFirmware/releases/tag/3.0, update that, then get 3.1.1 zip from https://github.com/Duet3D/RepRapFirmware/releases/tag/3.1.1, and update that. Don’t unzip, just send whole zip file to Duet in DWC.

However the motors should still work (most motor gcodes have not changed between versions), though with you current config, they won’t work in CoreXY mode (M669 is RRF2.03 or later). How are you testing them? Don’t use the ‘test motors’ macro on the SD card (or any of those), they are for factory testing and use different settings; if you have clicked this macro, you will need to reset the Duet to revert the motor settings. For testing motor movement and direction, see https://duet3d.dozuki.com/Wiki/Test_axes_or_motors_individually

For motor wiring (which I think is less likely to be the issue) see https://duet3d.dozuki.com/Wiki/Choosing_and_connecting_stepper_motors#Section_Connecting_stepper_motors

Be aware that setting a high motor current, having the motor incorrectly wired (ie phases crossed) and then asking for a high speed move (lots of voltage) can destroy the Duet motor driver and/or motor.

Ian

terrytao

@droftarts

I just updated to version 3.0 then 3.1.1 and the motors still don't turn. I've been using the "home x" button to test the motors.

peter247

@terrytao
You only on one of the phases .
Check you your cables .

I would check each motor on it's own driver to see if you have a faulty cable or even a faulty motor.

terrytao

I just disabled the homing check using M564 H0 command then ran a G1 X-10 F6000 command and the motor kept vibrating and didn't stop until I pressed the emergency stop button. I then plugged one of the motors into the z axis driver and sent a M564 H0 followed by a G1 Z-10 F6000. This ran well, and the motor moved. I then set all the parameters of X and Y drives to the same as Z drive in reprap configurator then ran G1 X-10 F6000 again. This time, the motor moved but only moved a fraction of the amount that it moved when it was plugged into the Z driver. Also, after it finished moving "10 mm", the motor kept making a sound. Any ideas on why this might be?

droftarts

@terrytao It does sound like a potential issue with the board. Can you check that the pins the motor connects to are fully soldered? You'll need to turn the board over, and check from the back. Can you post a picture of the board and wiring?

Ian

terrytao

@droftarts

The continuity between the solder joints and other end of wire is good.

droftarts

@terrytao said in Stepper motors vibrating but not turning:

Warning: motor phase A may be disconnected reported by driver(s) 2
Warning: motor phase B may be disconnected reported by driver(s) 2

Just realised... is this the only motor phase disconnection message? Driver 2 is the Z driver (X=0, Y=1, Z=2), and you don't have a motor plugged in! homex.g has a Z move in it, to move the bed down, so the nozzle is clear to move. So that's why you get that message.

Not sure about the motor issue. Realistically, if the motors work correctly on another driver, and no motor works correctly on X or Y, it sounds like a faulty board. Where and when did you buy it? Unfortunately, warranty for Duet3D boards is only 6 months.

Ian

terrytao

@droftarts

Ohhh I get it now, I always thought that 2 referred to the number of drivers that reported the error. It makes sense. I ordered it on April 8 of this year from Filastruder.

droftarts

@terrytao Okay, that's within 6 months. I approve a warranty replacement. Please contact Filastruder, follow their warranty process, and quote this thread for reference and warranty aproval. Apologies for the inconvenience.

Ian

terrytao

@droftarts

Will do, thanks for all the help!