Support ESP300 for non-ESP motors without encoders #23
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We had an ESP-300 controller with one ESP-compatible motor and two non-ESP compatible motors.
The limit switches on our non-ESP stages were not connected. We used the ZH command to determine if the axes have active limit switches.
To get the number of axes we could not use the ZU command as given in the existing code. Instead we query each axis until we get an invalid axis error.
The scaling factor between movement distance and motor pulse did not work for non-ESP compatible motors without encoders. We added a condition for open loop with no encoder feedback to set the scale from full step resolution without a microstep correction.
Better error handling: