IIoT Communication Server: UA Series
Connect IT with OT, Integrate Cloud and Web APPs
System Architecture
Key features
- Simultaneous Writing for Remote Database and Local Data Logger
- Offline Data Recovery Mechanism for Remote Database
- Enable OPC UA, MQTT, SNMP, and RESTful at the Same Time
- Information Protection - HTTPS, SNMP v3, Communication Encryption, Dynamic Blocklist, Whitelist
- IoT Cloud Platform - MS Azure, Amazon Web Services, IBM Bluemix, Alibaba Cloud
- IFTTT Logic Control Triggers the APP Notification Function
- PID Logic Operation Function
IT Integration Technology
• OPC UA:
|
The Industrial Communication Standard.
|
• MQTT:
|
The IoT Active Transmission Technology.
|
• Data Logger:
|
I/O data save directly to the Local LOG file or Remote Database.
|
• IFTTT:
|
The Cloud Logic Control (IF This Then That).
|
• Cloud:
|
The IIoT Cloud Connection Technology.
|
• SNMP Agent:
|
Simple Network Management Protocol Real-time monitoring device data |
OT Integration Technology
• OPC UA:
|
The New Industrial Communication Standard.
|
• MQTT:
|
The IoT Active Transmission Technology.
|
• Modbus:
|
A protocol widely used within Industrial Automation Systems.
|
• EtherNet/IP:
|
Industrial Ethernet protocol, based on TCP/IP protocol and compatible with factory and enterprise networks.
|
Features:
-
Built-in OPC UA Server Service
-
Built-in MQTT Broker Service
-
Provide SNMP Agent function (For UA-2800)
-
Provide RESTful API service interface (For UA-2800)
-
Support to Enable OPC UA, MQTT, SNMP and RESTful at the Same Time
-
Support device communication protocol: Ethernet and Serial Communication Modules
► Ethernet : UA supports Modbus TCP, MQTT , and ICP DAS EtherNet/IP modules
► Serial : UA supports Modbus RTU/ASCII modules (Max. 3 Serial ports)
► UA Web UI : users can quickly set up the modules and display the real-time I/O status.
► Max. modules supported by each connection:
-
Sensor Data Upload with Information Security
-
Save I/O Data Directly into Remote Database & Local Side
-
Offline Data Recovery Mechanism
-
Support IoT Cloud Platforms Connection
-
Support IFTTT Logic Control & Mobile Notifications (LINE, Twitter... APPs)
-
Provide Function Wizard Web UI for easy step-by-step setup
Step Box Example of Function Wizard
-
Provide Internal Module that can create virtual variables as an intermediary for reading, writing, or data exchange
* Create internal variables: 8 Internal virtual modules can be set, each module has 100 Internal internal variables (points).
* Communication protocol conversion: Provides Internal to OPC UA Server communication conversion.
-
OPC UA
The main purpose of the Control Room SCADA is to provide visual information to plant managers to maintain the normal operation of the plant. Designed and deployed with AVEVA™ Edge, the Control Room SCADA can present real-time information and images of production lines, plant services, IP equipment security topology, and cameras, and display alarm messages when equipment is out of order, allowing managers to quickly troubleshoot abnormalities. In addition, the storage and utilization of real-time information is also an important function of the Control Room SCADA. The source of real-time information in the plant and production of the Control Room SCADA is obtained through the OPC UA protocol of TCP/IP, which is different from the map control architecture that uses Modbus TCP protocol, and the following is a list of the common differences of the protocols.
- OPC UA has two communication modes, Client/Server and Publish-Subscribe, while Modbus uses a One Question One Answer Client/Server architecture for communication.
- OPC UA incorporates security features like encryption, authentication, and access control, whereas Modbus does not.
- Modbus is designed for industrial control systems and is typically used to access data from devices like programmable controllers, drives, and sensors.
- OPC UA communicates based on the TCP/IP protocol, can be deployed on any hardware and software platform that supports this protocol and can interact with a variety of devices and systems regardless of their manufacturer or location. In comparison, Modbus is designed to work with a limited number of devices and systems that support the Modbus protocol.
The UA-2241M UA communication server, in this case, collects the data of the production line and factory equipment and then converts it to OPC UA protocol before providing it to the Control Room. There are two main benefits of switching to the OPC UA protocol, one is to reduce the number of communication packets, and the other is to ensure the security of data transmission at the TCP layer.
The UA I/O series U-7555M is used for factory lighting control. In addition to the advantages of the OPC UA protocol mentioned above, it also utilizes the logic control within the UA I/O to determine the actual on and off status of the lights, reducing the need to write development logic for the TPD-703. In addition, the scheduling function of the UA I/O can also schedule the factory lights to be turned off, avoiding the situation where the lights are not turned off during off-duty hours.
Ans: OPC UA Client is an application program that connects to the OPC UA Server and reads data. OPC UA Client is designed to communicate with a common industrial automation protocol called "OPC UA". The purpose of this protocol is to gain interconnectivity between different systems (e.g. workstations, tools, production machines, etc.) so that they can be exchanged and controlled within the same system. The main function of the OPC UA Client is to read data (e.g. sensor data, production data, etc.) from the OPC UA Server and display it in a readable form on the user interface.
OPC UA Client can fulfill the needs of the following systems, devices, or scenarios:
A. Industrial Automation Systems B. Smart Homes C. Micro Controllers D. IoT Systems E. Monitoring and Control Systems F. Production Automation Systems
Since the OPC UA Client can read and display data from many devices and equipment, it can be used as a cross-platform and cross-device data display application that is compatible with the latest industry standards. Before setting up an OPC UA Client, it is important to ensure that the communication adapter associated with the client is connected to the OPC UA Server to be accessed, which is usually a data network based on a computer networking protocol such as TCP/IP. By configuring the necessary connection parameters (e.g. URL, exchange protocol, etc.), the client can connect to Server.
Ans: OPC UA Server is an application program that provides data and information and is the core of OPC UA technology. In OPC UA, it is responsible for managing, collecting, storing, and distributing data. The role of OPC UA Server is similar to that of a hub controller, which can be connected to a variety of different clients to provide data access and exchange.
The main task of the OPC UA Server is to manage the data model, which describes the relationships between the different data items in the system. By integrating data into a unified data model, OPC UA Server can acquire data from a variety of different data sources. For example, an OPC UA Server can take data from PLCs, meters, sensors, and other devices, convert it to a uniform data format, and send it to the client.
In addition, the OPC UA Server is responsible for security and privilege management. It can ensure the security of data in the transmission process through encryption, access control, and authentication mechanisms. In addition, users can assign different privileges to different users through privilege management to protect the security of data.
Ans: The Client/Server communication model of OPC UA is the traditional communication architecture of OPC. The process starts with the Client sending a connection request to the Server, and then the Server verifies the identity and responds with the connection result. When the Client needs to get data from the Item on the Server side, it can send a request to the Server to subscribe and monitor the Item data, and when there is a change in the data on the Server side, it will actively respond to the Client, and when the Client needs to change the Item data, it needs to actively send a data write request to the Server, and the Server will respond to the right result. The Server will respond with the written result.
Company | Client Name | Platform | License | Download link | Last version |
---|---|---|---|---|---|
Unified Automation | UA Expert | Windows | Free | http://bit.ly/UaExpert | 1.7.0 (2023-07-13) |
Prosys | OPC UA Browser | All (java) | Free | http://bit.ly/ProsysOpcUaClient | 4.4.0 (2022-11-28) |
Softing | OPC UA Demo-Client | Windows | Free | http://bit.ly/SoftingOpcUa | 2.30.0 (2022-01-13) |
Free OPC UA | OPC UA Client GUI | All (Python) | Free | http://bit.ly/FreeOpcUA | 0.8.4 (2022-01-31) |
Kepware | OPC UA Client Driver | Windows | Commercial | http://bit.ly/KepwareOpcUa | |
Node OPC UA | OPC UA Commander | All (JS) | Open-source | http://bit.ly/NodeOpcUaClient | 0.31.0 (2023-07-20) |
UA I/O Series | UA Communication Server | |||
---|---|---|---|---|
U-7000 Series | UA-2841M | UA-5231/UA-2241 Series | UA-7231M | |
OPC UA Server Session | 3 | 50 | 20 | 20 |
OPC UA Client Session | 1 | unsupported | unsupported | unsupported |
UA I/O Series | UA Communication Server | |||
---|---|---|---|---|
U-7000 Series | UA-2841M | UA-5231/UA-2241 Series | UA-7231M | |
OPC UA Server | O | O | O | O |
OPC UA Client | O | X | X | X |
MQTT Broker | X | O | O | O |
MQTT Client | O | O | O | O |
MQTT JSON | O | O | O | O |
Modbus RTU Master | X | O | O | O |
Modbus TCP Master | X | O | O | O |
EtherNet/IP | X | O | O | O |
SNMP V3 Agent | X | O | X | X |
RESTful API | O | O | X | X |
Remote SQL Data Log | X (Note 1) | O | O | O |
Local Data Log | O | O | O | O |
IFTTT | X | O | O | O |
IoTstar | O | X | X | X |
This application has been adopted by many petrochemical industries and is working well.
Ans: Please refer to the following link for the operation of different devices and databases.
https://www.icpdas.com/en/faq/index.php?kind=326#950
|
||||||||||||||||||||||
UA-2x00 / UA-5200 / UA-7200 Series (Built-in OPC UA Server and MQTT Broker/Client Service)
More UA hardware and software specifications, you can find on UA Comparison List. For related products, please refer to: OPC UA I/O Module, MQTT Broker BRK Series. |
||||||||||||||||||||||
Model | OS | CPU | SDRAM | Flash | Non-Volatile Memory | microSD Card | Ethernet Port | RS-232/ RS-485 |
Port Expansion |
Wireless | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
UA-2841M
|
Linux Kernel 5.10.72 |
ARM Quad-core CPU, 1.6 GHz/Core |
DDR4 2 GB |
8 GB | FRAM 64 KB MRAM 128 KB |
4 GB (Max. 32 GB microSDHC or 2 TB microSDXC) |
2 | 1 x RS-232 (console) 1 x RS-232 2 x RS-485 (2500VDC Isolated) |
1 | - | ||||||||||||
UA-2641M
|
Linux Kernel 4.1.15 |
ARM Quad-core CPU, 1.0 GHz/Core |
DDR3 1 GB |
|||||||||||||||||||
UA-2241M
|
Linux Kernel 3.2.14 |
ARM CPU, 1.0 GHz |
DDR3 512 MB |
512 MB | FRAM 64 KB |
4 GB (Max. 32 GB microSDHC) |
1 (*1) |
- | ||||||||||||||
UA-2241MX-4GE
|
4G (*2) |
|||||||||||||||||||||
UA-2241MX-4GC
|
||||||||||||||||||||||
UA-5231
|
8 GB | 1 | 1 (*1) |
- | ||||||||||||||||||
UA-5231M
|
||||||||||||||||||||||
UA-5231M-3GWA | 3G | |||||||||||||||||||||
UA-5231M-4GE
|
4G (*2) |
|||||||||||||||||||||
UA-5231M-4GC
|
||||||||||||||||||||||
UA-7231M
|
1 PoE | 1 x RS-232 (console) 1 x 5-wire RS-232/485 Isolated) |
- | - |
*1. UA series supports one optional XV-board module for I/O or RS-485 expansion, please refer to the "Supported List" web page. Note: -4GE/4GC and -3G model DO NOT support the XV511i model of XV-board series, please do not buy it as an optional board. *2. 4G System Note: UA-2241MX-4GE: Support 4G LTE (FDD) Communication (Asia Only, Except China) UA-2241MX-4GC/UA-5231M-4GC: Support 4G LTE (FDD, TDD) Communication (For China only) |
Type Name | Advanced Communication Server |
Standard Communication Server |
Compact Communication Server |
||
---|---|---|---|---|---|
Server Series/Name | UA-2841M | UA-2241 Series | UA-5231 Series | UA-7231M | |
Security Functions | |||||
Firewall Whitelist | List IP addresses and ranges allowed through the firewall to prevent unauthorized access and system attacks (UA-2841M not supported) | ||||
Firewall Dynamic Blocklist | Set conditions to put abnormal IPs into the dynamic block list | ||||
HTTPS | Enable https and provide X.509 certificate and key upload for verification use | ||||
OPC UA Server | Authentication: Username/Password, X.509 Certificate Security Policy: > Basic128Rsa15 (Sign / Sign & Encrypt) > Basic256 (Sign / Sign & Encrypt) > Basic256Sha256 (Sign / Sign & Encrypt) > Aes128_Sha256_RsaOaep (Sign / Sign & Encrypt) > Aes256_Sha256_RsaPss (Sign / Sign & Encrypt) |
||||
MQTT Broker | Provides SSL and TLS encryption and security authentication | ||||
Supports TLS 1.3 and below | Supports TLS 1.2 and below | ||||
MQTT Client | Provides SSL and TLS encryption and security authentication can be checked through Microsoft Azure, Amazon Web Services, etc. |
||||
Supports TLS 1.3 and below | Supports TLS 1.2 and below | ||||
SNMP(V3) Agent | TLS authentication | - | |||
Hardware Specification | |||||
CPU | ARM Quad-core, 1.6 GHz/Core | 32 bits, 1 GHz | |||
SDRAM | DDR4 2 GB | DDR3 512 MB | |||
Flash | 8 GB | 512 MB | 8 GB | ||
Ethernet | 10/100/1000 Base-TX × 2 |
10/100/1000 Base-TX × 2 |
10/100/1000 Base-TX × 1 |
10/100 Base-TX × 1 PoE |
|
MicroSD | Yes (Max. 2TB) | Yes (Max. 32GB) | |||
RS-232/RS-485 | 1 x RS-232 (console) 1 x RS-232 2 x RS-485 (2500 VDC Isolated) |
1 x RS-232 (console) 1 x 5-wire RS-232/485 (2500 VDC Isolated) |
|||
XV-board Expansion | 1 optional XV511i, expands 4 RS-485 ports or 1 optional XV107/107A/110/111/111A/116/119/303/306/307/310, expands I/Os |
- | |||
USB | 2 | 1 | - | ||
Wireless Communication | - | With 4G Models | With 4G, 3G Models | - | |
Dimensions (mm) | 42 x 164 x 130 | 35 x 167 x 119 | 117 x 126 x 58 | 97 x 114 x 38 | |
Software Specification: Protocol (*1, *2) | |||||
OPC UA Server | Max. 50 Sessions Max. 8000 Tags |
Max. 20 Sessions Max. 8000 Tags |
|||
MQTT Broker | non-SSL & SSL / WebSocket | ||||
Max. 2100 | Max. 400 | ||||
MQTT Client | non-SSL & SSL | ||||
Max. 500 | Max. 200 | ||||
Modbus RTU/ASCII Master |
32 * 3 Ports = 96 Devices | 32 * 1 Port = 32 Devices | |||
Modbus TCP Master |
Max. 250 Devices | Max. 100 Devices | |||
EtherNet/IP | Max. 125 Devices | Max. 50 Devices | |||
Support ICP DAS EIP-2000 series and Universal Robots products | |||||
SNMP v3 Agent | Max. 10 Read / 10 Write | - | |||
RESTful | Max. 20 Read / 1 Write | - | |||
Software Specification: Data Storage (*2) | |||||
MS SQL / My SQL Data log |
Max. 3 Databases per Time, Max. 1000 Tags per link |
1 Databases per Time, Max. 1000 Tags |
|||
Local Data log | Stored in the local MicroSD card or SSD (CSV format) | Stored in the local MicroSD card (CSV format) | |||
Software Specification: Function (*2) | |||||
Internal | Can create virtual variables as an intermediary for reading, writing, or data exchange for OPC UA Client to Client. | ||||
PID | Combine the remote I/O devices for the PID logic control system. | ||||
Software Specification: IoT Cloud Platforms and Function (*2) | |||||
MQTT JSON Function |
Microsoft Azure, Amazon Web Services, IBM Bluemix | ||||
MQTT Custom Function |
ThingSpeak | ||||
IFTTT Condition Trigger Function |
IFTTT Logic Trigger APP (Line, Twitter, Gmail ...) | ||||
*1: The specifications are the maximum number of connections or usage when using a single Protocol. *2: When using multiple protocols or functions, the user must adjust the actual usage to control the CPU Usage below 80%. Please refer to the CPU data on the UA web interface. |
XV-board Expansion Module Supported List
UA Model | Support Insert One XV-board Expansion Module | ||
---|---|---|---|
XV-board Type | XV-board Model | ||
UA All Series (UA-2200 / 5200 / 2800 Series) |
I/O Expansion | XV107, XV107A, XV110, XV111, XV111A, XV116, XV119, XV303, XV306, XV307, XV310 |
|
UA-2241M, UA-2841M UA-5231, UA-5231M |
RS-485 Expansion | XV511i |
-
IIoT Communication Server: UA Series Applications
The IT system has to record the fl ow, pressure, and water quality data of the water fi lter. It’s diffi cult to read the contents of the PLC in the fi lter tray. By deploying UA-5231M, the UA-5231M can convert PLC data into OPC UA service, which can reduce the diffi culty of equipment and system integration.
* Advantages: Replaces computers, uses OPC UA to connect to OPC Classic
The UA-5231 is an embedded IIoT server with the advantages of smaller size, less heat dissipation, and long-term operation than a PC, and provides the latest version of OPC UA Server function of the industrial communication standard protocol OPC. Compared with OPC Classic, OPC UA provides fi rewall-friendly cross-domain communication and SSL/TLS encryption communication capabilities.
Application Features:
• Fast Deployment (Small Broker)• Cloud Communication (Guaranteed Delivery)
Application Features:
• DI or Switch Status Change Notification• Message to Personal/Group of LINE APP
• More APPs: Facebook, Twitter, Skype, Weibo, etc.
Application Features:
• Dead Band Boundary Trigger (High: Danger Alert, Low: Safety Notification)• PC/Mobile Mail Notification (Gmail, e-mail, Office 365 Mail, Dropbox, etc.)
Application Features:
• Convenient for System Integration• Unified Access Interface
Application Features:
• Cross Web Domain• Security
Application Features:
• Asynchronous Transmission• Mobile Monitoring
If there happens a special situation, UA can quickly trigger the event, send a message to notify the Web APP (ex: LINE, Weibo, Twitter, etc.). The dual UA architecture can reduce the system burden.
Application Features:
• Reduce System Burden• APP Message Notify
Live Demo of UA IIoT Communication Server
-
UA-5231M + I/O Modules
Username: root
Password: root