No movement with any command

[zecreton]

@Phaedrux M569 PO R1

[Phaedrux]

@zecreton said in No movement with any command:

@Phaedrux M569 PO R1

You have a 6XD so this won't work.

What position is your enable polarity jumper in?

https://docs.duet3d.com/duet_boards/duet_3_mb6xd/duet_3_mb6xd_wiring_latest.png

1 x 3-pin Jumper Driver Enable Polarity A jumper in the "left" position is used for external drivers which are enabled when a voltage is applied to the enable connection (Active Enable). A jumper in the "right" position is used for external drivers which are disabled when a voltage is applied to the enable connection (Active Disable) (Note the v0.1 boards have the silkscreen reversed).

https://docs.duet3d.com/Duet3D_hardware/Duet_3_family/Duet_3_Mainboard_6XD_Hardware_Overview#connecting-external-motor-drivers

[droftarts]

@Phaedrux said in No movement with any command:

You have a 6XD so this won't work.

Is that in the documentation somewhere? On Slack @dc42 said:

M569 R parameter does have an effect on the 6XD. The jumper just sets the default value in case a M569 command with R parameter isn't seen. The main aim of this is to power up with the drivers disabled.

I've updated the documentation here to make it clearer: https://docs.duet3d.com/en/Duet3D_hardware/Duet_3_family/Duet_3_Mainboard_6XD_Hardware_Overview#connecting-external-motor-drivers

However...

@zecreton said in No movement with any command:

M569 PO R1

You have used an upper case letter 'o' for the P parameter, it should be a zero 0. Did it not report an error? Should be:
M569 P0 R1

Ian

[zecreton]

@droftarts

You have used an upper case letter 'o' for the P parameter, it should be a zero 0. Did it not report an error? Should be:
M569 P0 R1

Ian

i made an error in the message but i did send M569 P0 R1, sorry

[droftarts]

@zecreton Are you sure the axes are homed? You cannot move any axis if it is not homed. Though you should get an error message if you try and move an axis and it isn't homed. If you're still bench testing this, you could also send M564 H0 S0. This allows movement of axes that have not been homed, and allows movement outside boundaries set by M208. Add it to your config.g.

When you command a move, does DWC update the X position to show this change? If it does, then it is most likely sending the step and direction pulses.

Did you disconnect the ENA wires? If you do, you will still need to supply 5V to DIR+ and PUL+. Maybe post new pictures of how it is wired now.

Ian

[dc42]

@zecreton here are some common reasons for external drivers not working (most or all of these have been covered in previous replies):

1. Enable polarity is wrong. On many external drivers, the ENA input disables the driver instead of enabling it. So disconnect at least one of ENA+/ENA- and see if that helps. If that gets it working, move the enable polarity jumper on the 6XD to the other position and reconnect ENA+ and ENA-.

Another way to test if the enable polarity is correct is to use M17 to enable the axis that the driver controls (which should enable the motor, locking the rotor in place) and M18 to disable it (which should make the rotor free to turn by hand).

2. No power to the external driver. If it has a power indication LED, check that it is illuminated.

3. Step pulses too short. Try adding T10 to the M569 command for that driver. If that gets it working, you can then work on finding what timing the driver needs (using T10 will reduce the maximum step rate significantly).

4. Machine not homed. Use G91 to select relative movement, and H2 on the G1 commands to select direct motor moves (which ignore homing). For example, if the motor is configured (using M584) as the X drive, use:

G91 G1 H2 X10

5. Wiring issues.

6. Blown STEP output on the 6XD. This should only be the case if at some time you have shorted that connection to +5V or to some higher voltage. Double check your wiring, then try using a different driver output on the 6XD.

[zecreton]

@Phaedrux it is in the active enable position

[zecreton]

@droftarts yes the x position does show the change

[zecreton]

@dc42 M17 and M18 don't change anything, the rotor stays locked even with the ena disconnected

[dc42]

@zecreton OK, so ENA disables the motor when driven. Leave ENA disconnected until you get the motor moving. Did you try my previous suggestion to try using parameter T10 in the M569 command for that motor?

[zecreton]

@dc42 yea, i don't see any changes

[zecreton]

@dc42 do you think there is a person i could pay to come see it irl and fix the problem?

[zecreton]

@dc42 can i have an answer please?