OpenMHS family: python-object

Python device SDKs as OpenMHS drivers (direct Driver class)

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

• bridge_status: available
• helper: PythonObjectDriver
• exemplar: MHS/drivers/labs/tiagocoutinho__julabo

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: 467
• Decisions: bridge-runtime 18, direct-driver 212, reference 43, skip 194
• Waves: 0: 2, 1: 28, 2: 62, 3: 82, 5: 13, 6: 25, 9: 255
• Dispatchable now: 0
• Modes: hardware 211, simulated 92

Applicability

A Python package with an AST-parsed device class (score at least 9, at least three device API members) and device evidence: triage rule 10, PY_SDK_WITH_ENTRY. Exemplars: tiagocoutinho/julabo (instruments) and xArm-Developer/xArm-Python-SDK (robot SDKs).

Capability mapping

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. Importability says nothing about hazards. Heaters, motors, pumps, lasers and high-voltage outputs are common; cite every limit from the vendor documentation or the upstream code, or use Limit.operator_required.

Fidelity

A fake backend (a recording fake, or the upstream simulator when the repo ships one) yields contract_checked evidence only.

Pitfalls

Constructors often open ports or start threads: keep them in the hardware backend factory. Optional heavy imports belong in the backend module. Do not claim capabilities from class names alone; confirm each native call in the code.

First task cards

• gh.tiagocoutinho/julabo: direct-driver, wave 0, rank 3, MHS/registry/tasks/labs/tiagocoutinho__julabo.json
• gh.xarm-developer/xarm-python-sdk: direct-driver, wave 0, rank 4, MHS/registry/tasks/robots/xarm-developer__xarm-python-sdk.json
• gh.martinhjelmare/leicacam: direct-driver, wave 1, rank 1, MHS/registry/tasks/labs/martinhjelmare__leicacam.json
• gh.benpruitt/tecancavro: direct-driver, wave 1, rank 2, MHS/registry/tasks/labs/benpruitt__tecancavro.json
• gh.pymeasure/pymeasure: direct-driver, wave 1, rank 5, MHS/registry/tasks/labs/pymeasure__pymeasure.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/.