TOPIC HUB

Industrial protocols: Modbus, OPC UA and MQTT

Most integration problems are protocol problems in disguise: a register address that is off by one, a 32-bit value with its words swapped, an OPC UA endpoint that rejects an untrusted certificate, an MQTT session that loses data on reconnect. These guides explain how Modbus, OPC UA and MQTT actually behave on the wire, and how to choose and validate them before commissioning.

19 articles3 tools1 PDF
START HERE

A suggested reading order

PDF RESOURCES

Take it to the meeting.

All resources
PDF · 2 pages

Validate a Modbus register map before commissioning

A practical sequence for checking offsets, signedness, byte order and scaling before register values reach a dashboard.

ALL ARTICLES

Every article on this topic

Open in the article list
COMMON QUESTIONS

Short answers.

Modbus, OPC UA or MQTT?

They suit different jobs: Modbus for simple device access, OPC UA for client/server communication with an information model and security, and MQTT for lightweight publish/subscribe data distribution. Many projects use them together.

Why are my Modbus register addresses off by one?

Documentation may use 1-based (40001) or 0-based addresses, while the frame carries a 0-based offset. Our register addressing article explains the details.

OTHER TOPICS
THE NEXT STEP

From calculation to implementation.

Let’s look at your machine, your data flow or your production goal together. Describe your situation in a few sentences and the ASP Dijital team will reply by email.

Talk to ASP Dijital