Machine data acquisition: Modbus or OPC UA?

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

DimensionChoose ModbusChoose OPC UA
Installed equipmentMostly older machines with serial or Modbus TCP onlyNewer PLCs with UA support, or budget for a gateway
Scale & roadmapFew points, the system only needs to report upwardMixed vendors, MES or a data platform planned
Security & operationsSecurity must be added at the network layerEncryption, authentication and subscriptions built in
Retrofit costLow: existing devices connect directlyMedium: firmware upgrades or protocol gateways may be needed

2 · What we actually do on line projects

  1. 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.
  2. 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.
  3. 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.

Planning a similar production line or enterprise system?

Start with our pricing logic, then let's talk requirements — cost structure, technology comparison and acceptance criteria, all laid out in the open.