Labs · Motion control

Zaber stage (zaber_device.ZaberStage)

Zaber stage (zaber_device.ZaberStage), adapted from janelia-python/zaber_device_python. It reads x_position, y_position, z_position, x_actuator_id and 3 more; sets x_microstep_size, y_microstep_size, z_microstep_size, x_travel and 2 more; runs home, stop_motion, move_absolute, move_relative and 2 more. home: home every device in the chain and report the home status of the configured axes. A hardware driver: the market serves its fake backend, so no instrument is needed.

hardwareRisk R1BSD-3-Clausecontract_checkedserved on the fake backend
openai4s lab add labs/janelia-python__zaber_device_python

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/janelia-python__zaber_device_python

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/janelia-python__zaber_device_python --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": {
    "zaber-device-python": {
      "command": "python3",
      "args": [
        "-m",
        "mhs",
        "serve",
        "labs/janelia-python__zaber_device_python",
        "--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

  • x_position
  • y_position
  • z_position
  • x_actuator_id
  • y_actuator_id
  • z_actuator_id
  • homed

Adjusts

  • x_microstep_size
  • y_microstep_size
  • z_microstep_size
  • x_travel
  • y_travel
  • z_travel

Actions

home
Home every device in the chain and report the home status of the configured axes
stop_motion
Stop every device in the chain immediately (the native stop, the safe state)
move_absolute
Move the x, y and z axes to absolute positions in the stage unit
move_relative
Move the x, y and z axes by relative distances in the stage unit
move_to_stored_position
Move the x, y and z axes to the positions stored at an address
store_position
Store the current x, y and z positions at an address and return the stored positions

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/janelia-python__zaber_device_python
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
2fec6746359b
Licence
BSD-3-Clause
Stars
3
Evidence
contract_checked on the fake backend
Backends
fake, hardware

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