modbus-studio
An open-source Modbus master that runs in your browser. It polls Modbus TCP, RTU and RTU-over-TCP devices, decodes their registers into engineering values, writes coils and registers, and shows every frame on the wire. Run it on your laptop, or on a gateway or Raspberry Pi on the plant network and open it from any browser.
Install and run
pipx install modbus-studio # or: pip install modbus-studio
modbus-studio # open http://127.0.0.1:8000
The package includes the web UI; no Node.js is needed. A slave simulator comes with it, to try everything without hardware:
modbus-studio-sim # Modbus TCP on :5020, RTU over TCP on :5021
Then, in the UI, + Connection → Modbus TCP, 127.0.0.1, port 5020, and
+ Window. Serial ports (RTU) are listed in the connection dialog.
What it does
- Modbus TCP, RTU over TCP and RTU on a serial port; FC01–FC04 reads, FC05/06/15/16 writes.
- 16, 32 and 64-bit integers and floats in the four byte orders, scale and unit per register, aliases, CSV register maps.
- Several polling windows with their own scan rates, a traffic monitor with the raw frames, a real-time chart, writes with a confirmation dialog and a write log.
- Export to InfluxDB 2.x and publishing over MQTT, configured from the UI.
- REST API and WebSocket (OpenAPI at
/docs), JSON workspaces saved automatically.
On a network
The server listens on 127.0.0.1 only. To open it to other machines, set a token:
MODBUS_STUDIO_HOST=0.0.0.0 MODBUS_STUDIO_TOKEN="$(openssl rand -hex 24)" modbus-studio
Anyone who can reach the API can write to your devices: do not expose it without a
token, and preferably keep it behind a VPN or a reverse proxy with TLS.
modbus-studio --help lists the settings.
More
Documentation, the Docker image (ghcr.io/electrolabopen/modbus-studio, amd64 and
arm64), the changelog and the issue tracker: https://github.com/electrolabopen/modbus-studio
(español).
MIT licensed. modbus-studio is an independent project, not affiliated with, endorsed by or sponsored by Witte Software. "Modbus" is a trademark of Schneider Electric USA, Inc.
Metadata
Release files for modbus-studio 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| modbus_studio-0.2.0.tar.gz | 198.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| modbus_studio-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 378.3 kB
Release files / modbus_studio-0.2.0.tar.gz
| Download URL | modbus_studio-0.2.0.tar.gz |
|---|---|
| Size | 198.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
11f16de95676ae2deefda16fdbb6f9e595dfe55cedb3d15ec16e0127aaaa6c97
|
|
BLAKE2b-256 checksum How to use checksums |
2311ef0d1cfe8f375fa6302315a658a564b90a70e6f5b3056b3f4a070a9af8a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logRelease files / modbus_studio-0.2.0-py3-none-any.whl
| Download URL | modbus_studio-0.2.0-py3-none-any.whl |
|---|---|
| Size | 179.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
adbdbf4dba10fe296b4b6b297161babdd7e4a6699f09825a9a34f8286a88ec6b
|
|
BLAKE2b-256 checksum How to use checksums |
64cf06b3eb42b11b9edc2367045a11429f03b67736febf8b3ebb99f2fc00fbe1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logSecurity for modbus-studio 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for modbus_studio-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.