Make the limit mode of Motor
input configurable
#87
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.
This PR does...
limit_mode
toMotor
. Default value is1
to remain backwards compatible. This kwarg allows the class to be configurable for energized limits (1
), de-energized limits (2
), or not limits (3
).limit_mode
setting up through theAxis
andDrive
classes so the setting gets properly passed through toMotor
MotionGroupConfig
to handle both required and optional metadata during every call to_handle_user_meta()
.bapsf_motion.toml
andbenchtop_run.toml
to include thelimit_mode
setting.DriveConfigOverlay
(actually added toAxisConfigWidget
to allow for setting of the limit mode.closes #86