fix(api, shared-data): Disable tip presence on single tip pickup with 96ch and update press distance #16248
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Covers RABR-617
In order to support effective single tip pick up with the 96ch, this PR disables the tip presence sensor when the 96ch pipette is in single tip pickup configuration. This PR also bumps the press distance values for 1000/200/50 uL down to 10.5mm, the original values identified by hardware testing when tested without the tip presence sensor.
Test Plan and Hands on Testing
Rerun testing rounds on single tip pickup of the 96ch with all tip types.
Changelog
Review requests
Risk assessment
Low-Medium: This only effects a new feature that is launching with 8.0.0. The primary risk is that without tip presence sensing we're assuming the tips attached successfully. This has a low risk of failure, given the values identified by hardware testing had a good performance rate.