modbus-adapter
com.mbreissi.edgecommons.ModbusAdapter connects to Modbus devices (TCP, serial RTU, or RTU-over-TCP) and
bridges their registers onto a message bus: it polls a configured register map and republishes value
changes as structured messages, and serves on-demand reads, writes, and management queries. Built on
the edgecommons (edgecommons) library, it runs wherever you deploy it — a Greengrass v2
component, a standalone process, or a Kubernetes pod. It is the Python reference southbound
adapter and the poll-based counterpart to the (Java) OPC UA reference adapter.
| Doc | Start here when you want to… |
|---|---|
| Tutorial | learn by doing — bring the adapter up against a simulator, end to end |
| How-to guides | accomplish a task — define signals, tune rates, read/write, add a second device, deploy |
| Reference | look up an exact option, topic, payload, or type |
| Explanation | understand how it works and why — polling, the type layer, the two planes |
Quick routing
Section titled “Quick routing”- “I’m new here.” → Tutorial.
- “What config option does X?” → Reference — Configuration.
- “How is a register turned into a value?” → Reference — Data Types.
- “What message on which topic?” → Reference — Messaging Interface.
- “What does this metric mean?” → Reference — Metrics.
- “Why poll instead of subscribe?” → Explanation.
Audience
Section titled “Audience”These docs are for integrators and operators — people who deploy the adapter and write clients that consume or command it. They do not cover modifying the adapter’s own source.