Labs · Sensors and cameras

Thorlabs BC207/BC210 beam profiler (TLBC2.py)

Thorlabs BC207/BC210 beam profiler (TLBC2.py), adapted from thorlabs/light_analysis_examples. It reads sensor_pixels_x, sensor_pixels_y, pixel_pitch_horizontal, pixel_pitch_vertical and 5 more; sets exposure_time, wavelength, precision_mode and binning; runs capture and measure_beam. capture: capture a single image from a named camera with a declared resolution and exposure and return an image artifact reference. 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/thorlabs__light_analysis_examples

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

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/thorlabs__light_analysis_examples --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": {
    "light-analysis-examples": {
      "command": "python3",
      "args": [
        "-m",
        "mhs",
        "serve",
        "labs/thorlabs__light_analysis_examples",
        "--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

  • sensor_pixels_x
  • sensor_pixels_y
  • pixel_pitch_horizontal
  • pixel_pitch_vertical
  • roi_left
  • roi_top
  • roi_width
  • roi_height
  • sensor_temperature

Adjusts

  • exposure_time
  • wavelength
  • precision_mode
  • binning

Actions

capture
Capture a single image from a named camera with a declared resolution and exposure and return an image artifact reference.
measure_beam
Request a new measurement and return the 4-sigma beam widths, centroid, peak, saturation and total power the instrument calculated

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/thorlabs__light_analysis_examples
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
1e7f3aa6fe29
Licence
MIT
Stars
67
Evidence
contract_checked on the fake backend
Backends
fake, hardware

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