Industrial Gateways and Protocol Conversion
To collect data from machines that use different protocols, we review the existing interfaces, manufacturer support and open data maps. On the gateway, we check the address, data type, byte order, unit and scale mapping against the source values. If gateway data is to be passed to business applications, define the data fields and error handling on the ERP and API integration side.
Modbus RTU / TCPSerial communicationOPC UA / MQTTEdge management
What problem does this service solve?
A machine fleet with no common language
Machines from different years and manufacturers, each requiring its own software and its own know-how.
Uncertainty on serial lines
Problems on RS-485 lines such as address conflicts, missing termination or wrong timeouts are often undocumented.
Forgotten gateways
Intermediate devices installed in a cabinet years ago, with unknown passwords, no backup and no updates ever.
Loss of meaning in conversion
If a register address is carried without unit, scale and data type, the value is misread. Is 2350 a temperature, or 23.50?
What we cover, and within what limits
An edge gateway is a device or software that reads one or more field protocols (e.g. Modbus RTU, Modbus TCP, PROFIBUS, proprietary protocols) and converts them to another protocol (e.g. OPC UA, MQTT), pre-processing and buffering the data where needed. A simple protocol converter only does table mapping; an edge platform can also take on naming, unit conversion, event generation and store-and-forward. Which one to choose depends on the technical characteristics of the source protocols, data volume, environmental conditions and who will operate the gateway. Carrying control-related (safety or interlock) signals through a gateway is a design decision to be assessed separately; it is not part of our default design.
Technical scope
Source protocol analysis
Each machine’s interface, address map, data types and communication parameters are identified one by one.
Gateway / edge selection
A list of technical criteria based on protocol support, environmental resistance, buffering capacity, and management and update capabilities.
Mapping and data model
Register/variable mapping table: address, data type, unit, scale and naming. Checklist items: byte/word order, signed/unsigned and scale. Each is verified by comparing it with the source value.
Serial line cleanup
The address plan, termination, cabling and timeout settings are documented.
Secure management
The default password is changed; the configuration backup, update procedure and network access rules are written down.
Testing and monitoring
Source and target values are compared, connection loss is tried in a planned test and gateway health is added to monitoring.
Common conversion scenarios
| Source | Target | Note |
|---|---|---|
| Modbus RTU (RS-485) | Modbus TCP or OPC UA | Address conflicts and timeout settings; serial line quality is decisive |
| Modbus TCP | MQTT | No authentication at the source; the gateway must be kept in a separate zone |
| Existing PROFIBUS DP devices | PROFINET controller (via proxy) | The proxy represents the PROFIBUS devices it supports on the PROFINET side; device support and configuration are verified from the manufacturer’s documentation |
| Two separate networks or projects | Mapped input/output data (with a coupler) | On suitable products, a coupler provides mapped data exchange between two networks/projects; it does not move devices to the other network. The product name and capability are matched with the manufacturer’s documentation |
| Proprietary protocol | OPC UA | Driver/protocol support and licensing must be verified with the gateway manufacturer |
Prerequisites: what we need to get started
We list missing information and access together in the first meeting and complete them during the survey.
- List of machines and their existing communication interfaces
- Protocol and address map documents obtainable from the manufacturer
- The cabinet/location where the gateway will be installed, and power availability
- Information on the target system (OPC UA server, MQTT broker, SCADA)
- A decision on who will operate the gateway
Deliverables
Machine and protocol inventory
Gateway/edge technical criteria list
Mapping table and data model
Serial line address and cabling document
Configuration backups and update procedure
Value validation and test report
Representative scenario: collecting data from energy analysers and an old compressor
Energy analysers on a Modbus RTU line and a compressor controller with only a serial interface are to be brought into the common data layer. First, the line is cleaned up: address conflicts are resolved and termination is completed. Then unit and scale conversion is done on the gateway and the data is published via OPC UA or MQTT. Values are compared with the device displays over a defined period and the result is written into the test report.
This is a representative project flow; it is not a completed customer reference.
Service summary
OPC UA, MQTT and Data Integration
We read the data model a machine exposes via OPC UA and, in projects that need MQTT, distribute this data to applications through a broker.
Scope limit
For proprietary protocols, access depends on the manufacturer’s documentation and licence terms; we do not do reverse engineering. Warranty and support for gateway devices are subject to the terms of the relevant manufacturer or authorised reseller.
How do we proceed?
No step that affects production is carried out until the maintenance window, configuration backup and rollback plan are written down.
Analysis
Protocols and address maps are collected.
Choice
The gateway/edge is selected according to technical criteria.
Mapping
The data model and mapping table are written.
Implementation
Installation, configuration and value validation.
Management
Backup, updates and monitoring are put into operation.
Questions about Edge Gateways and Protocol Conversion
Is a separate gateway needed for each machine?
No. A gateway usually reads several devices. But group them carefully: connecting everything to a single gateway creates a single point of failure; capacity and physical location also come into it.
Can values be written to the PLC through the gateway?
It is technically possible. However, writing control and safety-related signals through a gateway requires a separate risk assessment. Our default design is read-only data collection.
Can open tools such as Node-RED be used?
Yes, where appropriate; they offer flexibility in data flow and transformation. The condition: responsibility for versions, backups, access and maintenance must belong to someone in writing.
How is the gateway secured?
The default password is changed, unnecessary services are disabled and the device is placed in a separate network zone; a configuration backup and update procedure are written down. The gateway is included in the inventory and in monitoring.
Work that can be planned together
OPC UA, MQTT and Data Integration
We read the data model a machine exposes via OPC UA and, in projects that need MQTT, distribute this data to applications through a broker.
IIoT and Production Data Collection
We determine the signals and sampling rates needed for production, quality, energy or maintenance.
PLC–PLC and PLC–Server Integration
We carry line status and coordination information between PLCs, and monitoring and reporting data between PLCs and servers.
Knowledge Center
Technical guides for this service
Let's plan a technical survey for edge gateways and protocol conversion
Briefly describe your machine list, the protocols you use and where the data needs to go; we will respond with a written proposal covering scope, assumptions and deliverables.