Every factory connectivity project starts with the same argument. Here is the short version we give clients: Modbus gets the data out; OPC UA makes the data usable. Your budget decides where you start, your architecture decides where you end up.
1 · The honest comparison
| Dimension | Choose Modbus | Choose OPC UA |
|---|---|---|
| Installed equipment | Mostly older machines with serial or Modbus TCP only | Newer PLCs with UA support, or budget for a gateway |
| Scale & roadmap | Few points, the system only needs to report upward | Mixed vendors, MES or a data platform planned |
| Security & operations | Security must be added at the network layer | Encryption, authentication and subscriptions built in |
| Retrofit cost | Low: existing devices connect directly | Medium: firmware upgrades or protocol gateways may be needed |
2 · What we actually do on line projects
- Normalise at the gateway. Whichever protocol you pick, protocol adaptation happens at the acquisition gateway: the upper layers only see one data interface, so a protocol change below does not touch MES or dashboards.
- Semantics must be stored. Even with Modbus, map every register to a semantic data point (machine – component – quantity – unit) at the gateway. Otherwise nobody remembers what register 3 was a year later.
- Keep an upgrade path. Require OPC UA in the purchase contract for new equipment, use Modbus for the installed base, and plan the switch within five years. It is the cheapest evolution path available.
In one sentence: Modbus solves "can we get the data at all", OPC UA solves "can we use it properly".
If you are evaluating machine connectivity or line data acquisition, bring the equipment list: we start with a reachability audit (what connects directly, what needs a gateway) and then quote the work.