OpenMHS family: serial

Serial line instruments as SerialDriver command maps

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

• bridge_status: available
• helper: SerialDriver
• exemplar: MHS/drivers/labs/thinksrs__srsinst.sr860

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: 58
• Decisions: bridge-runtime 1, direct-driver 33, family-config 3, reference 4, skip 17
• Waves: 1: 6, 3: 28, 5: 2, 9: 22
• Dispatchable now: 0
• Modes: hardware 37, simulated 10

Applicability

The repo imports pyserial (or an equivalent) and has no strong Python device class: triage rule 9, family:serial. It copies the command-map structure of the sr860 exemplar.

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. A serial line can drive pumps, heaters and motors. Port names and baud rates are deployment-specific and are never guessed at run time.

Fidelity

A transcript fake proves the framing and the command map, not the physics.

Pitfalls

Line endings and checksums vary; unbounded reads hang; USB re-enumeration renames ports; error replies are vendor-specific.

First task cards

• gh.amsikking/thorlabs_mcm3000: direct-driver, wave 1, rank 39, MHS/registry/tasks/labs/amsikking__thorlabs_mcm3000.json
• gh.amsikking/asi_ms_2000_500_cp: direct-driver, wave 1, rank 41, MHS/registry/tasks/labs/amsikking__asi_ms_2000_500_cp.json
• gh.fretchen/synqs_devices: direct-driver, wave 1, rank 45, MHS/registry/tasks/labs/fretchen__synqs_devices.json
• gh.mattgbiz/velmex-xyz-stagecontrol-python: direct-driver, wave 1, rank 46, MHS/registry/tasks/labs/mattgbiz__velmex-xyz-stagecontrol-python.json
• gh.amsikking/zaber_x_adr130: direct-driver, wave 1, rank 49, MHS/registry/tasks/labs/amsikking__zaber_x_adr130.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/.