The tower motors ..... H E L P

tecno

M669 K3 S1 T1

rc2

No difference, M119 not stopped LED on or off and axis do not move but Z position is counting up on G28

dc42

@tecno have you tested movement of the tower motors individually using G1 H2 moves? See https://docs.duet3d.com/en/User_manual/Machine_configuration/Configuration_linear_delta#testing-the-motors-and-endstops-individually.

Have you configured the delta parameters using M665? M669 is not used for delta printers.

Please post your config.g file.

tecno

@dc42
config.g

tecno

@dc42
G1 H2 X5

Error: G0/G1: attempt to move individual motors of a delta machine to absolute positions

dc42

@tecno the instructions on the page I linked to tell you to put the printer into relative movement mode first.

tecno

@dc42
Missed G91

But still no movement

tecno

Now that my endstops are working I hope I can get help with motors.

tecno

@phaedrux said in The tower motors ..... H E L P:

drivers might work if segmentation is enabled

So how do I activate segmentation if M669 is not to be used on Delta?

dc42

@tecno use M665 to set delta kinematics and the delta parameters first. Then use M669 with just S and T parameters (no K parameter) to enable segmentation.

tecno

@dc42
; General preferences
M575 P1 S0 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"BigDelta" ; set printer name
M665 R300 L615 B275 H570 ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them
M669 S1 T1 ; kinematics linear delta
M564 H0 S0 ; allow axis movement not homed

Still nothing

gloomyandy

@tecno Do your drivers/motors work at all? What happens if you simply set them up using standard cartesian kinematics, can you move them then?

tecno

@gloomyandy

What lines to change?

gloomyandy

@tecno As I asked above, have you ever had your motors/drivers working with your current control board at all?

A Former User

This post is deleted!

tecno

@gloomyandy

Mini5 eth + 3pcs 1XD to DM556, so not with that configuration.

tecno

@arnold_r_clark

Can be done but the motors need high current so the Mini is not up to the task

dc42

@tecno said in The tower motors ..... H E L P:

@dc42
Missed G91

But still no movement

It could mean that the enable polarity is wrong. Some questions:

How did you wire the external drivers to the 1XD boards?
Before you power up the drivers and the Duet, do the tower carriages move freely?
After you power up and before you send any commands, do the carriages move freely or are they locked?
After you command a motor using a G91 G1 H2 command, does the carriage move freely or is it locked?

tecno

@dc42
https://docs.duet3d.com/duet_boards/duet_3_can_expansion/duet_3_1xd_v1.0_wiring_03.png

Yes
Same as above
Same as above

tecno

My motors are the last listed -2804

dc42

@tecno said in The tower motors ..... H E L P:

@dc42
https://docs.duet3d.com/duet_boards/duet_3_can_expansion/duet_3_1xd_v1.0_wiring_03.png

Yes
Same as above
Same as above

Thanks. Your wiring link suggests that you have connected the Enable inputs of the drivers to the 1XD boards. So if you have set the Enable polarity correctly, the carriages should move freely before you command them to move, and after that (or when you use M17) they should lock. The fact that they are not locking suggests one of the following:

Power is not being supplied to your external drivers
Motor is not connected correctly to external driver
Configuration of external driver incorrect
Configuration of RRF is incorrect, so that it is not commanding the 1XD boards to move the motors

Please run the following command and report any error messages that you see:

M98 P"config.g"