Labs · Sensors and cameras

Thorlabs DCx (UC480) camera (Instrumental UC480_Camera)

Thorlabs DCx (UC480) camera (Instrumental UC480_Camera), adapted from mabuchilab/instrumental. It reads trigger_mode, trigger_level, auto_gain, auto_framerate and 9 more; sets trigger_delay, exposure_time, gamma and auto_exposure; runs configure_trigger, capture, start_live_video, stop_live_video and 1 more. configure_trigger: set the camera trigger mode and, for hardware triggering, the edge. A hardware driver: the market serves its fake backend, so no instrument is needed.

hardwareRisk R1GPL-3.0contract_checkedserved on the fake backend
openai4s lab add labs/mabuchilab__instrumental

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/mabuchilab__instrumental

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

  • trigger_mode
  • trigger_level
  • auto_gain
  • auto_framerate
  • auto_whitebalance
  • auto_sensor_exposure
  • auto_sensor_framerate
  • auto_sensor_gain
  • auto_sensor_whitebalance
  • bytes_per_line
  • width
  • height
  • is_open

Adjusts

  • trigger_delay
  • exposure_time
  • gamma
  • auto_exposure

Actions

configure_trigger
Set the camera trigger mode and, for hardware triggering, the edge
capture
Capture one finite sequence and report the frame dimensions; the pixel array is not carried
start_live_video
Start continuous acquisition
stop_live_video
Stop continuous acquisition
close_camera
Close the camera and release its image memory (the native safe state); it takes no input

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/mabuchilab__instrumental
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
642728325949
Licence
GPL-3.0
Stars
137
Evidence
contract_checked on the fake backend
Backends
fake, hardware

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