In short. Protocols decide what data moves, how fast, and how reliably. Modbus is simple and common on generators and meters. DNP3 and IEC 60870-5-104 suit utility-style telemetry. IEC 61850 suits substation automation. Good integration depends on the point map, update rates and failure behaviour as much as on the protocol name.
Comparison
| Protocol | Typical use | Strength | Watch for |
|---|---|---|---|
| Modbus RTU / TCP | Meters, generator controllers, UPS, drives | Simple, widely supported | Polled, limited time stamping, register maps vary |
| DNP3 | SCADA to remote sites, utilities | Event reporting, time stamps, unsolicited messages | More engineering effort |
| IEC 60870-5-104 | Telecontrol over IP | Utility interface standard in many regions | Configuration of information objects |
| IEC 61850 | Substations and protection | Data model, GOOSE, engineering tools | Network design and skill. See IEC 61850 |
| OPC UA | Plant to enterprise integration | Rich data model, security | Not for fast protection |
| SNMP | UPS and network device monitoring | Easy for IT systems | Limited control, security configuration |
Engineering the point map
- List each point: name, units, scaling, source device, update rate.
- Define status, measurement, alarm and command points separately.
- Check byte and word order, scaling and signed values.
- Define data quality: valid, stale, comm fail.
- Decide who time-stamps events: device or master.
Polling and performance
Modbus polling time depends on baud rate, number of devices and points per request. Slow serial networks with many devices may take many seconds to complete a scan. Group registers and prioritise critical points. Avoid polling control-critical data over slow paths.
Failure behaviour
- Mark stale data and alarm on communication loss.
- Do not let controllers act on stale values without a defined fall-back.
- Provide watchdog or heartbeat points between controllers.
Security
Many legacy protocols have no authentication. Protect with network segmentation, firewalls and controlled remote access. See OT network architecture.
Troubleshooting
Use a protocol analyser or software tool to see requests and responses. Typical faults: wrong address, wiring polarity or termination on serial links, duplicate addresses, scaling errors and congested networks.
Illustrative example
A SCADA reading shows generator frequency of 5,000 instead of 50.00. The register stores hundredths of hertz; the point map missed the scaling factor of 0.01. A review of the point map for all devices finds two more scaling errors, which are corrected before commissioning.
Protocols compared
| Protocol | Typical use | Strength | Limit |
|---|---|---|---|
| Modbus RTU/TCP | Meters, controllers, drives, gensets | Simple, universal | No time stamps, no data model, polling only |
| IEC 61850 | Substation devices and protection | Rich data model, fast GOOSE, SCL | Engineering effort |
| DNP3 | Utility SCADA, remote sites | Time-stamped events, report by exception | More complex than Modbus |
| IEC 60870-5-104 | Utility telecontrol | Widespread in utilities | Limited device modelling |
| OPC UA | Plant integration and IT | Secure, modelled | Not for protection speed |
| CAN / J1939 | Engine electronics | Engine data and control | Local network only |
Selecting
- Match the protocol to the devices that exist; avoid converters where possible.
- Require a register or object list for every device.
- Use gateways with documented mappings.
- Do not send protection commands over a link that is not designed for them.
Common integration issues
- Different byte or word order between devices.
- Scaling factors and units unclear.
- Polling too fast, loading slow serial links.
- Duplicate addresses.
Good practice
Keep a point list as a controlled document, with each point’s source, scaling and alarm limits. Test every point at SAT. See IEC 61850 architecture.
The master engineering question
For each value that a controller or operator relies on, how old can it be, how do we know it is valid and what happens when it is not?
What to send us
Send device lists and protocol documents. Send your application details.
Questions engineers ask
Which protocol should I use?
The one both ends support well, matching the speed and reliability required.
Is Modbus secure?
Not by itself. Protect it with network design.
Can protocols be mixed?
Yes, with gateways, but each conversion adds failure modes.
What is a heartbeat?
A signal that changes regularly to prove the link and the device are alive.
This guide gives general principles. Follow device documentation.