Find the mapping error in the lab, not on the skid.
One bench where devices, tags and protocols are engineered, exercised against a simulator and watched at the wire level — with the test evidence captured, not screenshotted.
Remove the integration guesswork before commissioning.
A Modbus server, live in your browser.
This is the traffic monitor. A client polls holding registers 40001–40010 once a second; every request and response is decoded at the frame level. Use the write console to push a value — it is an FC06 frame, encoded exactly as on the wire.
- Real Modbus TCP framing: MBAP header + PDU
- FC03 polls, FC06 writes, exception on a bad address
- Simulated in the page — nothing leaves your browser
Projects, devices and tag maps, importable from the metering-skid spreadsheets integrators already use.
Run as a Modbus server with patterned data, or connect as a client to a live device.
Protocol-level visibility of every poll and write, with a write console for manual test cases.
Captured test evidence rather than a screenshot in a notebook.
Exercised against third-party Modbus masters and simulators and an OPC explorer, with the results recorded.
Modbus TCP and the OPC DA bridge are qualified end to end. RTU is flagged in the tool itself as not yet field-qualified.
The pre-FAT test chain
Integration risk retired in three steps, each producing its own capture. Nothing is signed off on the strength of a demo.
Client polling a Modbus slave on localhost — status healthy.
DA bridge browsed, UA endpoint exposed on the same project.
Holding registers read back over Modbus TCP.
Imported straight into the project as tags.
The write path proven, not just the read path.
Across 4 Modbus object types.
Modbus TCP, UDP, RTU · OPC UA, DA.