Labs · Sensors and cameras

LI-COR Odyssey Classic 9120 infrared imager (CGI over HTTP)

LI-COR Odyssey Classic 9120 infrared imager (CGI over HTTP), adapted from vcjdeboer/odyssey-app-hap. It reads state, progress_percent, time_remaining, current_user and 2 more; sets scan_name, scan_group, resolution, quality and 9 more; runs control_scan, safe_stop and capture. control_scan: start, pause, stop or cancel the configured scan through command.pl. A hardware driver: the market serves its fake backend, so no instrument is needed.

hardwareRisk R2MITcontract_checkedserved on the fake backend
openai4s lab add labs/vcjdeboer__odyssey-app-hap

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/vcjdeboer__odyssey-app-hap

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/vcjdeboer__odyssey-app-hap --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": {
    "odyssey-app-hap": {
      "command": "python3",
      "args": [
        "-m",
        "mhs",
        "serve",
        "labs/vcjdeboer__odyssey-app-hap",
        "--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

  • state
  • progress_percent
  • time_remaining
  • current_user
  • lid_open
  • instrument_info

Adjusts

  • scan_name
  • scan_group
  • resolution
  • quality
  • intensity_700
  • intensity_800
  • channel_700
  • channel_800
  • origin_x_cm
  • origin_y_cm
  • width_cm
  • height_cm
  • focus_offset_mm

Actions

control_scan
Start, pause, stop or cancel the configured scan through command.pl
safe_stop
Send the status-page Stop and confirm the status page then reports Idle or Stopped
capture
Capture a single image from a named camera with a declared resolution and exposure and return an image artifact reference.

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/vcjdeboer__odyssey-app-hap
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
4dffe3a3ed0b
Licence
MIT
Stars
0
Evidence
contract_checked on the fake backend
Backends
fake, hardware

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