Skip to content
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

feat: Door interlock in robot server mode #35

Open
pbeaucage opened this issue Jul 3, 2022 · 1 comment · May be fixed by #52
Open

feat: Door interlock in robot server mode #35

pbeaucage opened this issue Jul 3, 2022 · 1 comment · May be fixed by #52
Assignees

Comments

@pbeaucage
Copy link
Collaborator

Robot server should have a pre_execute that checks for the door switch before beginning an action.

One annoyance is that you can't access the robot gpios when the robot server is running. So the startup script would need to stop the opentrons robot server and somehow restart it after our server starts successfully so we grab the gpios.

See #34 as well. Lots of reasons to take the GPIOs during execution.

@pbeaucage
Copy link
Collaborator Author

While looking at other things, I found that the Opentrons Robot Server API already has an endpoint for the door status, like so:

$ curl -H "Opentrons-Version: 2" -H  "accept: application/json" -X GET "http://piot2:31950/robot/door/status"
{"data": {"status": "open", "doorRequiredClosedForProtocol": false}}

This is now very easy to implement on the robot.

@pbeaucage pbeaucage self-assigned this Mar 6, 2024
@pbeaucage pbeaucage linked a pull request Mar 6, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant