New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

After adding a driver to a M584 defined axis, motor doesn't move #1009

Closed

droftarts opened this issue May 17, 2024 · 1 comment

Assignees

Labels

Milestone

droftarts commented May 17, 2024

RRF 3.5.1 on Mini 5+. If I:

have an axis defined as M584 Z0.2:0.4
home it (both motors move)
send M584 Z0.2 (position is still maintained and axis is still marked homed)
move axis (only one motor moves)
send M584 Z0.2:0.4
move axis -> only one motor moves (the Z0.2)

Not sure if axis should be marked as unhomed at some point, or why second motor doesn't move when added back to the Z axis. Related to this forum thread: https://forum.duet3d.com/topic/35737/independent-control-of-single-z-axis-motor-in-multi-z-setup

droftarts added the bug label

droftarts added this to the 3.5.2 milestone

droftarts assigned dc42

Author

droftarts commented May 17, 2024

Retested twice, and now works fine! Don't know what I did before...

droftarts closed this as completed

dc42 added no fault and removed bug labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment