Skip to main content

PLC Data to Cloud Gateway: Modbus and OPC UA Without Touching the Machine Program

· 6 min read
Mative Marketing Engine
AI Marketing Automation Platform
PLC Data to Cloud Gateway: Modbus and OPC UA Without Touching the Machine Program

Introduction​

The data a factory needs is often already inside its machines. The PLC knows whether the machine is running, how many pieces it has made and which alarm stopped it. Getting that data to the cloud does not have to mean rewriting the PLC program or stopping the line.

A PLC data to cloud gateway sits next to the machine, talks to the PLC in the protocols it already speaks, such as Modbus and OPC UA, and sends the data to the company system. This article explains how the connection works with Synapsis ISBC Gateway and Mative Cloud TC – Things Connector, what to check on the machine before you start, how to keep the plant network safe, and when data needs to travel in both directions.

What a PLC already exposes​

Most PLCs already publish their data, in one of two ways:

  • Modbus, in its serial (RTU) or Ethernet (TCP) version. Values sit in numbered registers, and the gateway reads the registers it needs at the interval you choose.
  • OPC UA. The PLC, or a server next to it, exposes named variables with their type, and the gateway reads them by name.

If the data you need is already in the Modbus register map or among the OPC UA variables, nothing changes in the machine program: the gateway only reads. If it is not, whoever programmed the machine has to expose it. It is usually a small configuration job, but it is a job, and it is better to know before starting.

How the connection works​

[PLC: Modbus RTU/TCP or OPC UA]
|
[Synapsis ISBC Gateway, on a DIN rail in the electrical panel]
|
[Mative Cloud TC – Things Connector]
|
[Mative Cloud TC: SCADA Module, alarms, reports]

Synapsis ISBC Gateway is the industrial computer Mative developed with Industrial Shields. It mounts on a DIN rail in the electrical panel and talks to the PLC through industrial protocols such as Modbus, OPC UA and BACnet. It reads the values, gives each one a name and sends them to Mative Cloud TC – Things Connector, which receives and stores them.

From there the data becomes useful to the people who work with the machine. The SCADA Module of Mative Cloud TC, built on request for each plant, shows what is running, what is stopped and why, machine by machine.

Reading, and when to write​

For monitoring, reading is enough. The gateway reads, the PLC keeps doing its job, and its program is not touched.

For interconnection, one direction is not enough. In Italy, to benefit from the iperammortamento on 4.0 investments, a machine must exchange data with the company system in both directions: it sends its data and receives instructions, such as parameters, orders or programs, loaded remotely. A machine that only sends data is monitored, not interconnected. Mative Cloud TC can send parameters and commands back to the machine through the same gateway.

Writing is decided machine by machine. Which values can be written, by whom and within which limits is agreed with whoever is responsible for the machine. A PLC that accepts any write from the network is a risk; a PLC where only agreed parameters can be written is a tool.

Keeping the plant network safe​

Three practical rules:

  • The connection goes out, not in. The gateway opens the connection towards Mative Cloud, so no port has to be opened from the internet towards the factory. Commands, when enabled, come back over that same connection.
  • Keep the machines on their own network. If the PLCs sit on a separate network segment, reachable only from the gateway, a mistake or an attack on the office network does not reach the machines.
  • Only what is needed. Read only the registers or variables you actually use, and enable writing only on the parameters agreed for interconnection.

Before you start: five checks​

  1. Which PLC it is, which model, and which protocol it speaks: Modbus RTU, Modbus TCP or OPC UA.
  2. Whether the data is already exposed: ask for the Modbus register map or the list of OPC UA variables.
  3. Where the gateway goes: space on the DIN rail, 24 V power, the network cable or serial line to the PLC, and an internet connection.
  4. Who is responsible for the machine program, in case something has to be exposed, or a parameter has to become writable.
  5. Which data comes first, and how often: states, piece counters and alarms are usually the place to start.

What you can do with the data​

  • Stops and efficiency: states and piece counters are the basis for measuring availability, performance and quality, the three factors of OEE.
  • Alarms: every alarm code arrives with the time it happened: you can see which ones repeat and on which machine.
  • Energy: if the PLC or a meter measures consumption, the Smart Metering Module of Mative Cloud TC shows energy produced and consumed, department by department.
  • Maintenance: on the history of the data, Synapsis ML, Mative's artificial intelligence platform, trains specific machine learning models to recognize anomalies and the first signs of wear. A model learns from data, so the history has to be collected well first.

Limits, said plainly​

  • A gateway does not make a machine interconnected on its own. Interconnection needs the exchange in both directions, and the machine must be able to receive instructions.
  • No gateway can read what the PLC does not publish. If the data is not exposed, someone has to expose it.
  • Mative does not sign technical appraisals. We build the connection and keep the evidence: when each machine was connected, which data it exchanges, which instructions it received. The appraisal is the work of a qualified engineer.

Conclusion​

Bringing PLC data to the cloud starts from what the machine already exposes. Synapsis ISBC Gateway reads it over Modbus or OPC UA without touching the program, Mative Cloud TC receives and stores it, and, when interconnection requires it, sends parameters and commands back to the machine.

Want to know what your PLCs already expose and what is missing? Request a demo: in 20 minutes we look at it together.