4G remote monitoring of unmanned sites: architecture and checklist
How to connect an unmanned site over 4G: outgoing connections or VPN, power, alarms, buffering when offline, and which ICP DAS devices fit.
How MQTT and OPC UA differ in communication model, data description and security, and which ICP DAS devices support each protocol.
Udgivet
Most automation projects eventually have to deliver machine data to systems outside the control network: a SCADA server, an MES, a database or a cloud platform. Two protocols dominate that task. This article compares MQTT vs OPC UA in practical terms: how each one communicates, how data is described and secured, and which systems typically receive it. It ends with an overview of ICP DAS devices that support one or both protocols.
MQTT is a publish/subscribe protocol. Devices connect as clients to a central broker and publish messages to topics such as site1/line2/press4/temperature. Applications that subscribe to a topic receive its messages. Publishers and subscribers do not need to know about each other. The default ports are 1883 for plain TCP and 8883 for MQTT over TLS.
OPC UA is mostly used as client/server. The device or gateway runs an OPC UA server, and a client such as a SCADA system connects to it, browses the address space, reads and writes values and subscribes to changes. The default port is 4840. The specification also defines a publish/subscribe mode, but most installed servers and clients use client/server.
This matters for network design. With MQTT the field device opens the connection, which suits sites behind NAT or a firewall that only allows outgoing traffic. With OPC UA client/server, the client must be able to reach the server, so both are usually on the same network or connected through a VPN.
MQTT transports bytes. The protocol does not define what a message contains, so topic structure, payload format (often JSON), units and timestamps must be agreed between sender and receiver. Conventions such as Sparkplug B add a defined payload, but only if both sides support them.
OPC UA includes an information model. Each value is a node with a data type, a timestamp, a status code and optional attributes such as engineering unit and description. A client can browse the server to find out what is available, without a separate register list.
In practice, MQTT is quick to set up and flexible, but documenting topics and payloads is your job. OPC UA takes more configuration on both sides, but the data describes itself.
MQTT relies on TLS for encryption, user name and password or client certificates for authentication, and access rules in the broker that control who may publish or subscribe to which topics. OPC UA has security built into the protocol: application certificates, the security modes None, Sign and SignAndEncrypt, and user authentication. In both cases the protection only works when it is configured. A broker on port 1883 without authentication, or an OPC UA endpoint with security mode None, is open to anyone who can reach it.
| MQTT | OPC UA | |
|---|---|---|
| Model | Publish/subscribe through a broker | Client/server (PubSub optional) |
| Connection direction | Device connects out to the broker | Client connects to the server in the device |
| Default ports | 1883, 8883 (TLS) | 4840 |
| Data description | Topics and payload defined by the user | Information model with types, units, timestamps and status |
| Delivery options | QoS 0, 1 and 2, retained messages, last will | Subscriptions with sampling and publishing intervals |
| Typical receivers | Brokers, cloud IoT services, databases, IT applications | SCADA, MES, historians, HMIs with an OPC UA client |
Check what the receiving system supports before choosing field hardware. The receiver usually decides the protocol.
The UA series communication servers (UA-2241M, UA-2841M, UA-5231M and UA-7231M) read data over Modbus TCP, Modbus RTU/ASCII, MQTT and EtherNet/IP and provide it through an OPC UA server, MQTT and SNMP at the same time. They include an MQTT broker, write data to databases such as MS SQL, MySQL and MariaDB with offline data recovery, and support HTTPS, an OpenVPN client and IP whitelists.
ICP DAS OPC UA I/O modules such as the U-7526M (AI, AO, DI and DO) and U-7544M (8 DI and 8 DO), combine built-in I/O with an OPC UA server and client, an MQTT client and a RESTful API that can run simultaneously. They have a two-port Ethernet switch, can be powered over PoE and support IF-THEN-ELSE rules.
On the receiving side, BRK-2841M is a dedicated MQTT broker for MQTT 3.1, 3.1.1 and 5.0 with QoS, retained messages, last will, authentication, encryption and bridging. It writes to databases such as MySQL and buffers data on microSD during outages.
Win-GRAF PACs such as XP-9188-IoT and RPAC-2658M run IEC 61131-3 programs and include an OPC UA server, so control and data access are handled in one device.
Send us a description of your data sources and the receiving system, and our technical sales team will suggest a suitable combination.
The PET-7017-10 is a PoE-powered Ethernet analog input module for engineers who need voltage or current measurement on a networked I/O node. Its inputs can be set as 10 differential or 20 single-ended channels in software, and each channel can be given its own range, so one module can serve mixed sensor types on the same network.Each channel offers a choice of voltage ranges from ±150 mV to ±10 V and current ranges of ±20 mA, 0 ~ 20 mA and 4 ~ 20 mA, selected with jumpers. Resolution is 16-bit, and the module has two sampling modes: normal mode at 10 Hz total and fast mode at 50 Hz total. Open wire detection is available for 4 ~ 20 mA inputs, and differential channels are rated for 240 Vrms overvoltage protection.Configuration and monitoring are handled through a built-in web server with Web HMI, and the module supports Modbus TCP and Modbus UDP. Access is controlled by ID, password and IP filter. The unit is powered either from PoE (IEEE 802.3af, Class 1) or from a +12 ~ +48 VDC terminal block, and it mounts on a DIN rail.ApplicationsBuilding automationFactory automationMachine automationRemote maintenanceRemote diagnosisTesting equipment
AR-200 CR is a dynamic signal acquisition module for vibration monitoring and analysis. It accepts two IEPE accelerometers, each supplied with a built-in 3 mA excitation current, and digitises the signals with a 16-bit converter. Sampling of both channels runs simultaneously, at rates up to 200 kHz per channel.Recordings are written to a Micro SD card, so data can be taken away and analysed offline. Capture can be started by a push button, a schedule, an analog threshold, a digital input or a remote command from the supplied utility on a host PC, which also lets you set the sampling rate and scheduling for each application. A single relay output and one digital input add basic event handling to the unit.The logger suits panel or machine installations that need to run unattended. It works from a wide +10 to +30 VDC supply, operates from -25 to +75 °C, and provides 4 kV contact ESD protection on all terminals. Mounting is by wall or DIN-rail.ApplicationsVibration monitoring and analysisIndustrial automationFactory automationProcess automation
The AR-400 is a dynamic signal acquisition module for vibration monitoring and analysis. It samples four channels simultaneously with 16-bit resolution and supplies a built-in 3 mA excitation current for IEPE accelerometers, so compatible sensors can be connected directly without an external supply.Acquired data is written to a micro SDHC card (4 to 32 GB), allowing offline analysis after capture. Recording can be started by push button, schedule, analog threshold, digital input or remote trigger from the utility software installed on a host PC, which also handles sample rate and sampling schedule settings.Suited to condition monitoring setups where vibration data must be captured at defined times or on defined events.Includes a relay output (Form A, 5A@250 VAC) and a digital input for use within trigger or control logic.ApplicationsVibration monitoring and analysisIndustrial automationFactory automationProcess automation
The CA-LLD-DC100-L300 is a 30 m liquid leak detection cable designed to cover larger areas where the path a leak might take is hard to predict. It suits open spaces with several possible leak points and can be fixed directly to water supply and return lines.Built with a 6 mm fluoropolymer carrier and two 30 AWG sensing wires enclosed in a conductive fluoropolymer jacket, the cable is rated for a maximum continuous operating temperature of 70 °C. This ordering code is the version without position detection.The cable is RoHS and WEEE compliant.ApplicationsWater leak detection over open or large surface areasMonitoring multiple potential leak pointsFixing to water supply and return lines
How to connect an unmanned site over 4G: outgoing connections or VPN, power, alarms, buffering when offline, and which ICP DAS devices fit.
How the browser-configured IF-THEN-ELSE rules on WISE modules handle local logic, logging and alarms, with a worked example and the limits.
Vi kender ICP DAS-sortimentet og hjælper jer med at finde det rigtige modul, tilbehør eller reservedel.
Kontakt teknisk salg