-
Notifications
You must be signed in to change notification settings - Fork 149
Add Legacy Starlet Support #1002
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
har1eyk
wants to merge
3
commits into
PyLabRobot:main
Choose a base branch
from
har1eyk:fix/starlet-old-firmware-compat
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why would the max y be lower than min y? i do not understand why they are being compared here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Normally it should not be. This is handling a legacy STARlet firmware quirk we observed on hardware: the extended configuration can report invalid/reversed PIP Y bounds, for example
left_arm_min_y_position = 606.5andpip_maximal_y_position = 6.0.That bad interval made
ensure_can_reach_position()reject valid CORE8 positions during tip pickup._normalize_extended_configuration_y_bounds()fixes the known invalid values during setup, and_pip_y_bounds()defensively returns the bounds as an ordered(min_y, max_y)tuple for reachability/safety call sites.So the comparison is not because max is expected to be lower than min on valid firmware; it is there to tolerate bad legacy firmware-reported bounds without disabling the reachability guard entirely.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is that the only problem or are the channels actually reversed as originally reported? does higher y still mean towards the back of the robot? is channel 0 still the backmost channel?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I ran a hardware confirmation script on the legacy STARlet to answer the channel/Y-axis questions directly.
This PR does not reverse channel order or change the deck coordinate model. After setup, the legacy firmware-reported PIP Y bounds were normalized to:
left_arm_min_y_position:6.00 mmpip_maximal_y_position:606.50 mm(6.00, 606.50) mmSo the change is only correcting invalid firmware-reported bounds before reachability checks.
For CORE8 channel mapping, PLR mapped
tip_rack_1000["A8:H8"]withuse_channels=[0..7]as:337.8 mm328.8 mm319.8 mm310.8 mm301.8 mm292.8 mm283.8 mm274.8 mmThis confirms:
I also checked that the reachability guard was not bypassed. Valid A8:H8 pickup targets all returned
reachable=True, while deliberately invalid targets still failed:y=-20.0 mm:reachable=Falsey=800.0 mm:reachable=FalseSo
ensure_can_reach_position()remains active. This PR fixes bad legacy firmware inputs to the reachability logic; it does not suppress the guard or change channel numbering/direction.