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

Investigate detecting that target speed can't be reached #119

Open
hannobraun opened this issue Mar 17, 2021 · 0 comments
Open

Investigate detecting that target speed can't be reached #119

hannobraun opened this issue Mar 17, 2021 · 0 comments
Labels
topic: motion control Issues concerning the software-based motion control implementation. type: enhancement New feature or request

Comments

@hannobraun
Copy link
Owner

SoftwareMotionControl will quite happily accept a high target speed, and then just never reach it. I haven't investigated what all the limiting factors are, but I do know that compiling in development mode on a weak microcontroller limits the maximum speed that can be reached.

In any case, just silently not reaching the target speed seems undesirable. It would be great, if SoftwareMotionControl can detect this case and maybe return an error.

@hannobraun hannobraun added type: enhancement New feature or request topic: motion control Issues concerning the software-based motion control implementation. labels Mar 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: motion control Issues concerning the software-based motion control implementation. type: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant