Glossary · System coordination, integration and orchestration
Protocol conversion
Also known as: Protocol translation
German: Protokollkonvertierung
In industrial communication, protocol conversion is the translation of data and services from one communication protocol to another, for example from Modbus RTU to OPC UA or from PROFINET to EtherNet/IP, so that devices using different protocols can exchange information.
- System integration
In one sentence
Protocol conversion translates data and services from one communication protocol to another so devices with different protocols can exchange information.
Example
A gateway converts the Modbus registers of legacy energy meters into OPC UA variables with engineering units, so the energy management system can read them.
How it applies
- Engineering: Protocol conversion is more than moving bytes: data types, byte order, scaling, units, timestamps and quality information must be mapped. Document the mapping table for every converted value.
- Performance: Conversion adds latency and can lose features such as diagnostics or deterministic timing. Don't route time-critical or safety-related communication through a generic converter unless it is designed and assessed for that purpose.
- Security: Converters connect networks and are therefore part of the attack surface; place them deliberately in the zone and conduit model.
- Documentation: Keep the mapping (source address, target node or tag, data type, unit, scaling) in the integration documentation. Service technicians need it when values look wrong.
Protocol conversion vs. data model mapping
Protocol conversion changes how data is transported. Mapping to a Data model changes what the data means and how it is structured. A register value converted to OPC UA is still just a number until it is mapped to a meaningful object with a unit; see Protocol (communication) vs. data model.