Skip to content
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

Leaping Movers #98

Open
Jcbmtz opened this issue Feb 5, 2025 · 1 comment
Open

Leaping Movers #98

Jcbmtz opened this issue Feb 5, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@Jcbmtz
Copy link
Collaborator

Jcbmtz commented Feb 5, 2025

Mediator branch with the sample code.
Sequence to recreate:
Enable>Start>Stop>Drop Enable signal>Enable
some movers leap like mover one when its enabled without doing mover 1 detection

@netbymatt netbymatt added the bug Something isn't working label Feb 5, 2025
@netbymatt
Copy link
Collaborator

I have an idea of what may be happening here:
Stop and enable are happening very quickly one after another and/or we're not waiting for all movers to report halted before disabling. This leaves the movers with some wind-up in the set position that is not cleared via a axis reset on the next startup. It should be pretty easy to tell if this exact scenario is happening by comparing the mover's set points to their actual positions after the "drop enable signal" step above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants