I've completed my build now and it's very nice. I have a suggestion for an improvement to the push-button functionality.
In the released code, each press of the push button increments or decrements the step target by 1 step. As noted in the documentation, this is very slow (excessively so if you have a stepper with a very high steps per revolution such as the NEMA17-PG27). I tweaked my copy of the code so that each press causes a change in the step target by 20, which is about half the width of the CFZ on my setup, and it makes the push buttons much more responsive without any concern that you might step right through the CFZ.
I'm content with my solution and it's an easy tweak to make, but for wider usability it would be nice if the number of steps moved per push-button press could be exposed as an interface so that it could be set via the ASCOM or INDI drivers.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've completed my build now and it's very nice. I have a suggestion for an improvement to the push-button functionality.
In the released code, each press of the push button increments or decrements the step target by 1 step. As noted in the documentation, this is very slow (excessively so if you have a stepper with a very high steps per revolution such as the NEMA17-PG27). I tweaked my copy of the code so that each press causes a change in the step target by 20, which is about half the width of the CFZ on my setup, and it makes the push buttons much more responsive without any concern that you might step right through the CFZ.
I'm content with my solution and it's an easy tweak to make, but for wider usability it would be nice if the number of steps moved per push-button press could be exposed as an interface so that it could be set via the ASCOM or INDI drivers.