Skip to content

encoder functionality implemented #5

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Chaliuz
Copy link

@Chaliuz Chaliuz commented Feb 7, 2025

This update lets manage the step motor position with a encoder.

@redoxcode
Copy link
Owner

redoxcode commented Mar 30, 2025

I am a bit hesitant with this PR since I think when you want to use a closed-loop configuration you should go for a more complex control scheme (PID).
I see the value of using an encoder to compensate lost steps, however I think stuff like acceleration and deceleration should be implemented first to reduce steplos in the first place.
Also I think with your implementation one could run into an issue where the stepper keeps stepping one step back and forth trying to reach the target position indicated by the encoder, if the encoder has a higher resolution than the stepper.

Edit: Here is an publication on that topic: https://www.galil.com/download/whitepapers/wp_closed_loop_stepper_motor_performance_gains.pdf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants