Labs · Electronics and measurement

RIGOL DS1000Z-series oscilloscope (RigolDs1000z)

RIGOL DS1000Z-series oscilloscope (RigolDs1000z), adapted from masahiro-999/oscilloscope-mcp. It reads identity, active_channel_count, acquire_memory_depth, acquire_sample_rate and 3 more; sets channel_1_scale, channel_1_offset, channel_1_probe, channel_1_coupling and 8 more; runs measure and run_control. measure: read the scope-side automatic measurements for one or more items on a channel. 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/masahiro-999__oscilloscope-mcp

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/masahiro-999__oscilloscope-mcp

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/masahiro-999__oscilloscope-mcp --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": {
    "oscilloscope-mcp": {
      "command": "python3",
      "args": [
        "-m",
        "mhs",
        "serve",
        "labs/masahiro-999__oscilloscope-mcp",
        "--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

  • identity
  • active_channel_count
  • acquire_memory_depth
  • acquire_sample_rate
  • trigger_mode
  • trigger_status
  • trigger_holdoff

Adjusts

  • channel_1_scale
  • channel_1_offset
  • channel_1_probe
  • channel_1_coupling
  • channel_1_display
  • timebase_scale
  • timebase_offset
  • timebase_mode
  • acquire_type
  • acquire_averages
  • trigger_sweep
  • trigger_coupling

Actions

measure
Read the scope-side automatic measurements for one or more items on a channel
run_control
Start, stop, arm a single acquisition, or force a trigger

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/masahiro-999__oscilloscope-mcp
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
e45773551e2b
Licence
MIT
Stars
3
Evidence
contract_checked on the fake backend
Backends
fake, hardware

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