Rigol DHO824 Oscilloscope
io.github.aimoda由 GitHub 账号 aimoda 发布v0.1.143-main.2b177ae更新于 Oct 28, 2026
Control and query Rigol DHO824 oscilloscope for waveform capture and measurements
概览
让助手通过 VISA 控制并查询 Rigol DHO824/DHO804 示波器,进行波形采集、截图和测量。
- 可以做什么
- 采集示波器各通道的波形并保存为临时文件
- 对仪器屏幕截图,可选择在每次工具调用后自动截图
- 通过 VISA 连接查询和控制示波器,包括蜂鸣器设置
- 把容器内路径转换为宿主机路径,便于直接打开采集文件
- 适用场景
- 当你的网络中有 Rigol DHO804/DHO824 示波器,并希望助手在实验台调试时自动抓取波形、截图和读取测量结果时使用。
- 运行要求
- 以 Docker(推荐)或 Python 包在本地运行。需要能访问仪器的网络,以及 RIGOL_RESOURCE 指定的 VISA 资源字符串(例如 TCPIP 地址)。Docker 方式还需 RIGOL_TEMP_DIR 与挂载的宿主机目录一致;可选 VISA_TIMEOUT、RIGOL_BEEPER_ENABLED、RIGOL_AUTO_SCREENSHOT。示波器须刷成 DHO824 固件 00.01.04。
安装
在 SourceWeft 中
- 打开 控制台中的 Rigol DHO824 Oscilloscope,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
Rigol DHO824 MCP Server
An MCP (Model Context Protocol) server for controlling and querying the Rigol DHO824 oscilloscope.
[Demo of oscilloscope in action]
Built by ai.moda.
Hardware Requirements
Supported Models
This project only supports DHO804/DHO824 oscilloscopes (identical hardware). We recommend purchasing a DHO804.
Firmware Requirements
IMPORTANT: The DHO804 must be flashed to DHO824 firmware before using this MCP server. Use the rigol_vendor_bin project to flash your oscilloscope.
Supported Firmware Version: 00.01.04
This is the only firmware version we test and support. Other firmware versions may work but are not guaranteed.
Compatibility Note
Other Rigol oscilloscope models may work with this MCP server, but we have no way to test them or guarantee functionality. Use with other models at your own risk.
Installation
The recommended way to use this MCP server is via Docker, which eliminates dependency management and provides isolation.
Quick Start
Pull the pre-built image from GitHub Container Registry:
Using Environment Variables with Docker
IMPORTANT: You must provide the RIGOL_RESOURCE environment variable with your oscilloscope's IP address (e.g., TCPIP0::192.168.1.100::inst0::INSTR).
You can configure the Docker container with environment variables in two ways:
- Hardcoded values (shown in examples below):
-e RIGOL_RESOURCE="TCPIP0::192.168.1.100::inst0::INSTR" - Pass-through from host (recommended):
-e RIGOL_RESOURCE(without=value)
When you use -e VARIABLE_NAME without a value, Docker automatically passes through the variable from your host environment. This is useful if you have environment variables already set in your shell (e.g., in ~/.bashrc or ~/.zshrc).
Environment Variables
RIGOL_RESOURCE: Required - VISA resource string for connecting to the oscilloscope (e.g.,TCPIP0::192.168.1.100::inst0::INSTR)RIGOL_TEMP_DIR: Required for Docker - Host-side path for returned file paths. The container always writes to/tmp/rigolinternally and translates paths to this value in responses. Must match the host path in your-vmount. Outside Docker, this sets the directory for temporary files (waveforms, screenshots); if not set, uses system default temp directory.VISA_TIMEOUT: Communication timeout in milliseconds (default: 30000)RIGOL_BEEPER_ENABLED: Enable/disable oscilloscope beeper sounds (default: false)RIGOL_AUTO_SCREENSHOT: Automatically capture screenshot after each MCP tool execution for visualization/debugging (default: false). Screenshots are saved with human-readable timestamp format (e.g.,auto_screenshot_20251030_143045_123.png) for chronological sorting.
MCP Client Configuration
Claude Code
Option 1: Using .mcp.json file
Create a .mcp.json file in your project directory (or copy from .mcp.json.example):
Option 2: Using CLI
Replace 192.168.1.100 with your oscilloscope's IP address.
Codex
Replace 192.168.1.100 with your oscilloscope's IP address.
Note: After adding the server to your MCP client, restart the client to load the MCP server. The server will translate container paths (/tmp/rigol/*) to host paths (/tmp/rigol-data/*) in all returned file paths.
Your first prompt
Enter the following prompt in your MCP Client to verify your setup:
Your MCP client should connect to the oscilloscope and capture the waveform data.
Accessing Temp Files in Docker
The container writes temporary files (waveform captures, screenshots) to /tmp/rigol internally. To access these files from your host machine:
-
Create a directory on your host for storing temporary files:
-
Mount this directory as a volume and set
RIGOL_TEMP_DIRin your Docker configuration:
The server automatically translates all returned file paths from the container path (/tmp/rigol/*) to the host path (/tmp/rigol-data/*), so you can directly access files at the paths shown in tool responses.
Important notes:
- The host directory (
/tmp/rigol-datain examples) must exist before starting the server RIGOL_TEMP_DIRmust match the host-side path in your-vmount- Temporary files are not automatically cleaned up
- You are responsible for manually cleaning up old waveform and screenshot files
- Files will be organized in subdirectories like
waveform_capture_<timestamp>/for waveforms andscreenshot_<timestamp>.pngfor screenshots
Example: Manual cleanup
Troubleshooting
Container exits immediately
- Ensure you're using the
-iflag (interactive mode) - Verify
RIGOL_RESOURCEis set correctly
Cannot connect to oscilloscope
- Verify oscilloscope IP address and network connectivity (
ping <ip-address>) - Check oscilloscope's remote control settings are enabled
Environment variables not working
- Ensure you're using
-e VARIABLE_NAMEin the Docker args array - Set the actual values in the
envfield of.mcp.json
Building Locally
To build the Docker image yourself:
Then use rigol-dho824-mcp:local as the image name in your configuration.
Development Setup
For local development and contributions, you can install the MCP server in a Python virtual environment.
Create and activate virtual environment
Install the package
Add to MCP Client
After completing the setup steps above, add the local development MCP server to your MCP client:
Claude Code:
Codex CLI:
Replace:
<path-to-this-repo>with the actual path to this repository192.168.1.100with your oscilloscope's IP address
Note: Unlike Claude Code, Codex requires explicit environment variables via --env flags (before the server name) as it runs MCP servers in a sanitized environment.
Development Scripts
The scripts/ directory contains utilities for development:
convert_png_to_webp.sh- Convert PNG frame sequences to animated WebP (e.g.,./scripts/convert_png_to_webp.sh "~/screenshots/*.png" output.webp)
Development Configuration
The server can be configured using environment variables. Create a .env file from the example:
Then edit .env to set your configuration:
RIGOL_RESOURCE: VISA resource string for the oscilloscope (required)- Example:
TCPIP0::192.168.1.100::inst0::INSTR
- Example:
VISA_TIMEOUT: Communication timeout in milliseconds (default: 5000)
Running the Server (Development)
For local development and testing, you can run the server directly with Python:
STDIO Transport
HTTP Transport
来源:README.md,提交 2b177ae
工具
0版本历史
1- v0.1.143-main.2b177ae最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分