OpenMHSindependent draft 0.9
Playground
Open menu

Labs · Motion control

Flamingo stage position controller (PositionController)

Flamingo stage position controller (PositionController), adapted from uw-loci/flamingo_control. It reads position_x, position_y, position_z and rotation; sets home_x, home_y, home_z and home_rotation; runs move_stage and stop_motion. move_stage: move all four stage axes to an absolute position with the controller's move_to_position; a target outside the configured stage limits is refused instead of clamped. A hardware driver: the market serves its fake backend, so no instrument is needed.

hardwareRisk R1MITcontract_checkedserved on the fake backend
openai4s lab add labs/uw-loci__flamingo_control
All install options REFERENCE.md Upstream repository Registry record

Install

Three ways to run this device. Each one serves its fake backend: no instrument, no simulator install and no upstream checkout.

OpenAI4S (one command)

shell
openai4s lab add labs/uw-loci__flamingo_control

Installs the device into the OpenAI4S Lab on its fake backend and starts it. First time? See setup below.

Or, in the workbench, open the Lab tab → Market → Install.

Standalone MHS endpoint

shell
git clone --depth 1 https://github.com/PKU-YuanGroup/OpenMHS.git && cd OpenMHS
PYTHONPATH=MHS/sdk/src python3 -m mhs serve labs/uw-loci__flamingo_control --port 7400
# in a second terminal, from the same directory:
PYTHONPATH=MHS/sdk/src python3 -m mhs describe --endpoint http://127.0.0.1:7400

Serves the device as an MHS endpoint on port 7400 from an OpenMHS clone (Python 3.10 or later, standard library only); describe prints what it offers.

Any MCP host (Claude Desktop, Cursor, …)

mcp configuration
{
  "mcpServers": {
    "flamingo-control": {
      "command": "python3",
      "args": [
        "-m",
        "mhs",
        "serve",
        "labs/uw-loci__flamingo_control",
        "--mcp"
      ],
      "env": {
        "PYTHONPATH": "/path/to/OpenMHS/MHS/sdk/src"
      }
    }
  }
}

Add this server to the host's MCP configuration and replace /path/to/OpenMHS with the path of your OpenMHS clone. The host starts the server and talks to it on stdin and stdout.

What it does

Measures

  • position_x
  • position_y
  • position_z
  • rotation

Adjusts

  • home_x
  • home_y
  • home_z
  • home_rotation

Actions

move_stage
Move all four stage axes to an absolute position with the controller's move_to_position; a target outside the configured stage limits is refused instead of clamped
stop_motion
Stop all motion on the resource with a declared deceleration profile and report the stopping position. This capability is always cancellable=false and is exempt from rate limiting.

Names as the driver declares them. Units, limits and the safety declaration are in the package's REFERENCE.md.

First-time setup

The OpenAI4S workbench with the OpenMHS lab, from a source checkout:

shell
# OpenAI4S workbench with the OpenMHS lab (source checkout)
git clone --recursive https://github.com/PKU-YuanGroup/OpenAI4S.git
cd OpenAI4S && ./setup.sh && source .venv/bin/activate
openai4s lab add labs/uw-loci__flamingo_control
openai4s serve        # open the Lab tab

The standalone endpoint and the MCP server need only an OpenMHS clone and Python 3.10 or later. More in the market's getting-started guide and on the OpenAI4S host page.

Source and evidence

Pinned commit
0eee5dac8e54
Licence
MIT
Stars
2
Evidence
contract_checked on the fake backend
Backends
fake, hardware

The driver package MHS/drivers/labs/uw-loci__flamingo_control wraps the upstream code at the pinned commit. Its REFERENCE.md documents the full contract: every value, action, unit, limit and the safety declaration.