OpenMHS family: opentrons

Opentrons robots and protocols (helper:http, planned)

Generated by MHS/registry/build_registry.py on 2026-10-20T00:00:00Z from 40 registry records and their task cards. A plan, not a conformance claim.

• bridge_status: planned (blocked_on: helper:http)
• helper: none
• exemplar: none

Launch

Every driver package starts the same way; per-repo configuration (environment id, model path, port, baud rate, VISA resource) lives in the package's driver.py, never in launch flags:

mhs serve <driver-dir>

A package is done when python3 -m mhs.driver check <driver-dir> --backend fake exits 0 (evidence contract_checked; a fake never yields an MHS-Device level).

Registry coverage

• Repos: 40
• Decisions: bridge-runtime 2, reference 14, skip 24
• Waves: 9: 40
• Dispatchable now: 0
• Modes: hardware 1, simulated 2

Applicability

Robot-server runs and commands: aspirate and dispense map to cap.fluid.aspirate.v1 and cap.fluid.dispense.v1, transfer to cap.fluid.transfer.v1; tip pick-up and drop map to x-cap.<owner>.tip_pickup.v1 and x-cap.<owner>.tip_drop.v1 until a class exists; protocol simulation is the fake.

Capability mapping

The mapping is fixed when the helper lands; the applicability section lists its rules.

Class ids come from python3 -m mhs.driver catalog search <words>. The deprecated classes cap.device.describe.v1, cap.world.state.v1, cap.world.snapshot.v1 and cap.world.restore.v1 are replaced by the protocol methods mhs.devices.get, mhs.resource.read, mhs.snapshot and mhs.restore.

Safety

The risk floor of a device is the highest catalogue risk_class of its classes (CAP-017); a driver may declare a higher risk, never a lower one. Hardware at R1 or above needs an @estop and a non-empty safe state. A real OT-2 or Flex pipettes and moves labware; tip tracking and contamination are the driver's job.

Fidelity

Bridge only; the fidelity belongs to the service, simulator or hardware behind it.

Pitfalls

Protocol Engine versions differ; the simulator models deck logic, not liquid physics.

First task cards

• gh.opentrons/opentrons: bridge-runtime, wave 9, rank 22, MHS/registry/tasks/labs/opentrons__opentrons.json
• gh.noel-research-group/robochem_flex: reference, wave 9, rank 466, MHS/registry/tasks/labs/noel-research-group__robochem_flex.json
• gh.opentrons/ot3-firmware: skip, wave 9, rank 519, MHS/registry/tasks/labs/opentrons__ot3-firmware.json
• gh.nvidiagameworks/flex: skip, wave 9, rank 524, MHS/registry/tasks/robots/nvidiagameworks__flex.json
• gh.tanaes/opentrons_functions: skip, wave 9, rank 575, MHS/registry/tasks/labs/tanaes__opentrons_functions.json

Sources

• Task cards: MHS/registry/tasks/<track>/<owner>__<repo>.json (schema/taskcard.schema.json).
• Triage rules and the helper table: MHS/registry/triage.py; curated decisions: MHS/registry/overrides/.
• Driver API and gate: MHS/sdk/docs/driver-authoring.md; exemplars: MHS/drivers/.