fix(api): only send moves to moving axes, unless specified otherwise #13933
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.
Overview
This allows us to keep certain axes disengaged while we command other axes to move.
Instead of sending moves to all present motor nodes all the time, regardless of
whether they actually need to move or not, we are only sending the move requests to
the axes that are defined in the moves.
Most of the time we're ordering a mount to move (see various move methods in ot3api).
This guarantees that the axes pertaining to that mount (X, Y, and Z) will be receiving the moves
together but the other idle mounts will be left alone.