Skip to content

Use of multiple motion systems causes Code 3 halts in 3.6 beta1 and beta2 releases #1064

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.

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

Closed
dc42 opened this issue Nov 27, 2024 · 2 comments
Closed
Assignees
Labels
bug Bug that has been reproduced
Milestone

Comments

@dc42
Copy link
Collaborator

dc42 commented Nov 27, 2024

See https://forum.duet3d.com/topic/36866/multiple-motion-system. Reproduced on a Duet 3 Mini using no expansion boards, XYZUE all assigned to local drivers..

@dc42 dc42 added the bug Bug that has been reproduced label Nov 27, 2024
@dc42 dc42 added this to the 3.6.0 milestone Nov 27, 2024
@dc42 dc42 self-assigned this Nov 27, 2024
@dc42 dc42 changed the title Use of multiple motion systems caused Code 3 halts in 3.6beta releases Use of multiple motion systems causes Code 3 halts in 3.6 beta1 and beta2 releases Nov 27, 2024
@dc42
Copy link
Collaborator Author

dc42 commented Nov 27, 2024

Fix implemented in 3.6-dev and tested locally. Binary for Duet 3 Mini made available to user for confirmation of fix.

@dc42
Copy link
Collaborator Author

dc42 commented Apr 12, 2025

We have had one further Code 3 report but it was caused by using a very low input shaping frequency, not because of multiple motion systems.

@dc42 dc42 closed this as completed Apr 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug that has been reproduced
Projects
None yet
Development

No branches or pull requests

1 participant