From 29d7e87bf4f3bf5b92eb14febadcbe64a9261c0a Mon Sep 17 00:00:00 2001
From: Ryan Howard <ryan.howard@opentrons.com>
Date: Tue, 19 Nov 2024 16:44:40 -0500
Subject: [PATCH] fix(shared-data): extents update from hardware (#16895)

<!--
Thanks for taking the time to open a Pull Request (PR)! Please make sure
you've read the "Opening Pull Requests" section of our Contributing
Guide:


https://github.com/Opentrons/opentrons/blob/edge/CONTRIBUTING.md#opening-pull-requests

GitHub provides robust markdown to format your PR. Links, diagrams,
pictures, and videos along with text formatting make it possible to
create a rich and informative PR. For more information on GitHub
markdown, see:


https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax

To ensure your code is reviewed quickly and thoroughly, please fill out
the sections below to the best of your ability!
-->

# Overview
Hardware got back to me with some updated numbers.
<!--
Describe your PR at a high level. State acceptance criteria and how this
PR fits into other work. Link issues, PRs, and other relevant resources.
-->

## Test Plan and Hands on Testing

<!--
Describe your testing of the PR. Emphasize testing not reflected in the
code. Attach protocols, logs, screenshots and any other assets that
support your testing.
-->

## Changelog

<!--
List changes introduced by this PR considering future developers and the
end user. Give careful thought and clear documentation to breaking
changes.
-->

## Review requests

<!--
- What do you need from reviewers to feel confident this PR is ready to
merge?
- Ask questions.
-->

## Risk assessment

<!--
- Indicate the level of attention this PR needs.
- Provide context to guide reviewers.
- Discuss trade-offs, coupling, and side effects.
- Look for the possibility, even if you think it's small, that your
change may affect some other part of the system.
- For instance, changing return tip behavior may also change the
behavior of labware calibration.
- How do your unit tests and on hands on testing mitigate this PR's
risks and the risk of future regressions?
- Especially in high risk PRs, explain how you know your testing is
enough.
-->
---
 .../definitions/2/general/ninety_six_channel/p200/3_0.json  | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/shared-data/pipette/definitions/2/general/ninety_six_channel/p200/3_0.json b/shared-data/pipette/definitions/2/general/ninety_six_channel/p200/3_0.json
index 5719bb3437c..5f3fa397dc8 100644
--- a/shared-data/pipette/definitions/2/general/ninety_six_channel/p200/3_0.json
+++ b/shared-data/pipette/definitions/2/general/ninety_six_channel/p200/3_0.json
@@ -624,8 +624,8 @@
   "plungerPositionsConfigurations": {
     "default": {
       "top": 0.5,
-      "bottom": 68.5,
-      "blowout": 73.5,
+      "bottom": 67.5,
+      "blowout": 72.5,
       "drop": 80
     }
   },
@@ -649,7 +649,7 @@
   "channels": 96,
   "shaftDiameter": 2,
   "shaftULperMM": 3.14159,
-  "backlashDistance": 3.0,
+  "backlashDistance": 0.3,
   "quirks": [],
   "plungerHomingConfigurations": {
     "current": 0.8,