Labs · Electronics and measurement

INSTRUSTAR ISDS205B USB oscilloscope (instrustar.Scope)

INSTRUSTAR ISDS205B USB oscilloscope (instrustar.Scope), adapted from gridinwork/ai-oscilloscope-isds205b. It reads available, ch1_voltage_resolution_v, ch2_voltage_resolution_v, ch1_coupling_ac and 8 more; sets sample_rate_hz, generator_waveform, trigger_mode, trigger_style and 3 more; runs capture, set_input_range and generator_enable. capture: capture one waveform on both channels and return per-channel scalar measurements. 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/gridinwork__ai-oscilloscope-isds205b

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/gridinwork__ai-oscilloscope-isds205b

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/gridinwork__ai-oscilloscope-isds205b --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": {
    "ai-oscilloscope-isds205b": {
      "command": "python3",
      "args": [
        "-m",
        "mhs",
        "serve",
        "labs/gridinwork__ai-oscilloscope-isds205b",
        "--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

  • available
  • ch1_voltage_resolution_v
  • ch2_voltage_resolution_v
  • ch1_coupling_ac
  • ch2_coupling_ac
  • generator_enabled
  • has_hard_trigger
  • has_dds
  • has_io
  • has_pretrigger_percent
  • has_roll_mode
  • memory_length_kb

Adjusts

  • sample_rate_hz
  • generator_waveform
  • trigger_mode
  • trigger_style
  • trigger_source
  • trigger_level_mv
  • trigger_pretrigger_percent

Actions

capture
Capture one waveform on both channels and return per-channel scalar measurements
set_input_range
Request one channel's input range in mV and read back the voltage resolution the device reports
generator_enable
Enable or disable the DDS generator output

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/gridinwork__ai-oscilloscope-isds205b
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
cb1bdda97869
Licence
MIT
Stars
0
Evidence
contract_checked on the fake backend
Backends
fake, hardware

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