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

RFC: Rethinking how we store stepping configuration #79

Open
Jeff-Ciesielski opened this issue Dec 22, 2016 · 0 comments
Open

RFC: Rethinking how we store stepping configuration #79

Jeff-Ciesielski opened this issue Dec 22, 2016 · 0 comments

Comments

@Jeff-Ciesielski
Copy link

For the sake of simplicity, it would be nice if we made a few changes to how we store step parameters:

  • Steps/mm can be stored in terms of full steps, and the 'active' steps/mm can be derived from full_steps_mm * microstepping multiplier
  • Microstepping config can be stored as a whole multiplier (1, 2, 4, 16...etc) per axis rather than a mask The mask will become irrelevant with the SPI drivers and it would be nice if we had a unified way of describing this config (also, the new drivers support far more microstepping options that can't be encoded in 2 bits/axis)
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

No branches or pull requests

1 participant