-
Notifications
You must be signed in to change notification settings - Fork 178
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(api): bump y max bounds to match robot geometry
We now helpfully check that jogs don't overlap the maximum motion range of each axis, at least in the positive direction, using the home positions. This works pretty well for Z and X since it straightforwardly prevents hard limit errors from unintentional endstop triggers, which happen at the home position as one might expect. Unfortunately, the robot geometry makes this approach completely invalid for Y. When homing, the Y endstop (which is located on the back of the head) actually interacts with a post projecting from the back of the robot, which is located on the right side of the robot. This is the reason we must always home X before homing Y: to make sure the head is in the correct position for the Y endstop to interact with the post. If the head is _not_ all the way to the right, it can actually go much farther back - past the home location, past where the switch would interact with the post. And the deck layout is designed to take advantage of this; the position that A1 of most labware lives in is farther back than the post, and thus customers would get spurious jog failures when calibrating labwares in slots 10 and 11 using single channel pipettes (because multi channels are wider in Y, the gantry doesn't go far enough back to trigger the issue). The fix is to create a different bound in the Y. Closes #6886
- Loading branch information
Showing
4 changed files
with
26 additions
and
13 deletions.
There are no files selected for viewing
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
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
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
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