Labs · Motion control

Thorlabs TPZ001 piezo controller (piezo.PiezoController)

Thorlabs TPZ001 piezo controller (piezo.PiezoController), adapted from azdagkas/kinesis-piezo. It reads units, reader_reading, reader_units and zeroing; sets value and closed_loop; runs move_to_home, jog_up, jog_down, calibrate_position and 2 more. move_to_home: drive the piezo travel to zero with the native move_to_home (the safe state). 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/azdagkas__kinesis-piezo

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/azdagkas__kinesis-piezo

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/azdagkas__kinesis-piezo --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": {
    "kinesis-piezo": {
      "command": "python3",
      "args": [
        "-m",
        "mhs",
        "serve",
        "labs/azdagkas__kinesis-piezo",
        "--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

  • units
  • reader_reading
  • reader_units
  • zeroing

Adjusts

  • value
  • closed_loop

Actions

move_to_home
Drive the piezo travel to zero with the native move_to_home (the safe state)
jog_up
Step the controller value up by one configured jog step (the native moveup)
jog_down
Step the controller value down by one configured jog step (the native movedown)
calibrate_position
Run the native calibration: drive 10 and 70 percent and fit percentage travel to the strain gauge reader
move_to_position
Move to a strain gauge reader position with the stored calibration (the native move_to_pos)
zero_reader
Zero the strain gauge reader with the native reader set_zero

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/azdagkas__kinesis-piezo
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
ecfe0586cef3
Licence
BSD-3-Clause
Stars
5
Evidence
contract_checked on the fake backend
Backends
fake, hardware

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