fix(api): use motion lock when updating firmware #14431
Merged
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
The 96-channel pipette is reported to drop after a firmware update in testing. This is because while the update is happening, the pipette cannot respond to any other CAN requests. If the hardware controller probes the network at this time, it would not be able to detect the presence of the 96-channel pipette and mistakenly lower the Z-axis motor current required to hold the pipette in place.
This PR fixes this by making sure the update firmware call block other motion tasks until all firmware has been updated.