Every integration job on a PV, wind or storage site comes down to one decision: how do you get values off the controller and into something you can store and act on. In practice the choice narrows to two protocols. Modbus is on almost every device ever shipped; OPC UA is on almost every datasheet printed in the last decade. They are not interchangeable, and treating them as if they were is where projects quietly go wrong.
Modbus tells you what is in register 40001; OPC UA tells you it is the active power of inverter 3, in kilowatts, and that it went stale four seconds ago.
Flat register maps against information models
Modbus is a flat, addressable memory space: coils and discrete inputs for bits, holding and input registers for 16-bit words. No type, no unit, no name. Register 40001 might be active power in kilowatts or a fault code, and the only thing that tells you which is a vendor document, usually a PDF. Anything wider than 16 bits — a 32-bit float for power, a 64-bit energy counter — is split across consecutive registers, so you also need the word and byte order, and vendors disagree on that constantly.
OPC UA carries the meaning with the value. The server exposes an address space of typed nodes with browsable names, engineering units, data types and timestamps, organised into an information model. Companion specifications standardise that model per domain, so an inverter or meter looks broadly the same across makers. You read ActivePower as a typed, named node, not a guessed offset. That structure is the real difference; the wire protocol is secondary.
Polling, subscriptions and the security gap
Modbus is strictly request-response: the client polls, the device answers. To catch a tripped breaker you poll until the new value appears, trading network and CPU load against latency, and you can still miss a transient between polls. OPC UA adds subscriptions — you register the nodes you care about and the server pushes changes on a deadband or sampling interval, so a state change arrives as an event instead of something you catch on the next sweep. Across thousands of points that difference compounds fast.
Security is the sharper line. Classic Modbus has none: no authentication, no encryption, no integrity check, so it must stay on a trusted, segmented OT network and never face anything routable. OPC UA builds security into the protocol — X.509 certificates for mutual authentication, message signing and encryption, and per-node access control. Certificate handling is the part teams underestimate: trust lists, rotation and expiry are ongoing operational work, and an expired certificate is a silent outage waiting to happen.
A pragmatic migration path
You rarely choose on a clean slate. Older inverters, meters and RTUs speak Modbus and will for years; newer kit and most modern SCADA expose OPC UA. So read each device on what it natively speaks and converge on one canonical model on your side — a normalisation layer that maps raw Modbus registers and OPC UA nodes alike into a single typed, unit-correct schema before anything reaches your time-series store. The point of truth is your model, not the protocol of the day.
Done that way, swapping a Modbus device for an OPC UA one later is a connector change behind a stable interface, not a downstream rewrite. That decoupling — plus getting unit conversions, byte order and stale-data handling right at the edge — is most of the work and most of the value.
There is no universally right answer, only the right fit for the device, the network and the data rate in front of you. Modbus is simple, ubiquitous and fine on a segmented OT network; OPC UA earns its weight where meaning, events and security matter. Getting the boundary between them right is the kind of integration work we build for energy and renewables operators.