Monthly
$10 / month
THE MODBUS DEVICE WORKSPACE
Every signal.Understood.
Connect, inspect, and simulate your devices.
A dedicated
workspace for Modbus RTU & TCP.
01 A LITTLE ORDER IN EVERY BYTE
Your entire bench.
Finally in view.
Connections, registers, and conversations.
Keep the details
together, so you can
focus on what the device is telling you.
A real workspace, with simulated
devices.
08
Core Modbus function codes.
Read and write with intent.
Explicit confirmation for writes.
A little more peace of mind.
Connections, models, captures, tests.
Saved as one local project.
02 FOLLOW THE SIGNAL
From a raw register
to the whole picture.
Start with one value. Follow the bytes.
Build the device you
wish you had on hand.
Register ExplorerINTERACTIVE DEMO
Simulated device · Slave 1ILLUSTRATIVE DATA
03 THE BENCH, WITHOUT THE
BOTTLENECKS
Less setup.
More figuring things out.
Move from a physical device to a repeatable virtual test.
Keep
the knowledge. Bring it to the next project.
Connect your device.
Open RTU or TCP. Configure your transport and find the responding slaves.
SERIAL / ETHERNETUnderstand its data.
Decode values, check traffic, and build a register map you can keep.
REGISTERS / FRAMESTake it with you.
Record a session. Clone observed device responses into your virtual bench.
RECORD / REPLAYMake it repeatable.
Write, wait, read, assert. Run a sequence and keep its PASS/FAIL report.
SCENARIOS / REPORTSBUILT AROUND THE DETAILS
Serious tools.
A quieter workspace.
Your data, correctly interpreted.
Integer, floating point, HEX, ASCII, and bit fields. Configure byte order, word order, scale, and offset.
Plan for the imperfect response.
Test delay, timeout, dropped responses, exceptions, and virtual CRC errors before they surprise you.
Bring your register maps.
Import CSV, Excel, or JSON. Export device definitions and captures to keep your work portable.
A foundation that can grow.
An independent Rust core, plus SNMP v2c GET. MQTT, REST, and OPC UA are on the roadmap.
Choose your
ModbusLab license.
Target platforms
- macOS
- Windows
- Linux
USD pricing. Each license covers up to 3 devices. Online activation is required, with up to 7 days offline within your paid period.
Linux, Windows, and macOS validation builds pass in CI. Production installers are not yet signed or notarized. Physical RS-485 validation is pending.
A FEW THINGS TO KNOW
Before you
plug in.
Can I use ModbusLab without a physical device?
Yes. The application starts with a labeled virtual bus and three simulated Slave IDs. The simulator also exposes a TCP server for external masters. An external RTU slave server is not included in this version.
What does Device Clone reproduce?
It copies observed values and cycles matching reads through captured responses and their latency. It does not infer vendor logic or behavior that was never captured.
How are writes handled?
Manual writes, replay, and scenarios containing writes require explicit confirmation. ModbusLab never retries a write automatically. A timeout does not prove that a device did not apply the write.
Does the program need a cloud connection?
Licensed builds need online activation and periodic renewal. A signed offline entitlement lasts up to 7 days, capped by the paid subscription period. Projects, register maps, Modbus values, and communication logs stay on your computer and are never sent to the licensing server.