IBH Link UA:Description: Difference between revisions

From IBHsoftec Wiki English
Jump to navigation Jump to search
Updated description to the current released feature set
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
== Integrating S5 and S7 controllers in the OPC UA world ==
== Overview ==


The slogan "Industry 4.0" introduces more and more new communication and information technologies into industry automation. In order to implement these requirements efficiently and as quickly as possible must be tried to reduce the complexity by modularization and standardization. In this context, OPC UA has proven to be the pioneering communication standard. With OPC UA the industry 4.0 requirements for independence from manufacturer- industry- and company-communication-system are fulfilled.
The '''IBH Link UA''' connects PLCs and industrial devices to OPC UA, IIoT and cloud applications. Depending on the hardware version, it provides an OPC UA server and client, protocol gateways, certificate management, firewall functions and edge services in a compact DIN-rail device.


Since OPC UA is not only transferring machine data, i.e. process values and measured values, but also allows the semantic description, OPC UA is becoming increasingly important to transfer machine data to higher level controllers systems.But how it is accomplished to read process data from Siemens SIMATIC controllers and integrated into the OPC UA communication?
[[Image:IBH_Link_UA.png|400px|thumb|center|IBH Link UA]]


The solution to this is the [http://www.ibhsoftec.com/IBH-Link-UA-Eng IBH Link UA].
== Configuration and administration ==


[[Image:IBH_Link_UA.png|400px]]
The device is administered through its web interface. PLC variables and address spaces can be configured using:


The IBH Link UA, OPC UA server / client module with firewall, is designed to connect the SIMATIC controllers S5, S7-200, S7-300, S7-400, S7-1200 and S7-1500 into the OPC UA communication. The IBH Link UA is a compact device with four Ethernet ports and a 24V power supply for DIN rail mounting. Configuration is accomplished with the original Siemens STEP 7 tool or the TIA Portal. No special software must be installed on the programming device. The variable definitions are transferred by the programming software via Ethernet into the IBH Link UA. The variable attributes (e.g. read-only or limits) are directly defined within the PLC project. Thus a symbolic access to variables and data block structures is possible. A direct call of a PLC client functions can be done in the PLC program. This allows the PLC to communicate with controllers from other manufacturers via OPC UA. The IBH Link UA has three Ethernet ports for the machine level and one Ethernet port for the management level. On the management level only OPC access are possible. The integrated firewall between the two levels prevent possible manipulation out of the management level. The device has a certificate management for secure communication. The configuration of the security levels and the certificates management is easily accomplished via a web browser. The communication with the control takes place using TCP / IP. If the control has no Ethernet port available, the function can be achieve by using the proven communication adapter [http://www.ibhsoftec.com/IBH-Link-S7-PP-Eng IBH Link S7++] or [http://www.ibhsoftec.com/IBH-Link-S5-PP-Eng IBH Link S5++].
* the free [[IBH Link UA:Configuration with IBH OPC UA Editor|IBH OPC UA Editor]]
* Siemens STEP7
* Siemens TIA Portal


==Operation and configurationn==
Projects and variable definitions are transferred to the IBH Link UA over Ethernet. Symbolic access, data-block structures and variable attributes can be included in the OPC UA address space.


As already mentioned, the IBH Link is UA is configured with the original Siemens STEP7 or the TIA Portal. No special software must be installed on the programming system. Thus, the IBH Link UA is seamlessly integrated into the PLC project. The variable definitions of the programming software are transferred into the IBH Link UA via Ethernet. The variable attributes (e.g. read-only or limits) are defined directly in the PLC project. Symbolic access to variables and data block structures therefore are possible.
== OPC UA server and client ==


Configuration is done as followed:
The IBH Link UA can operate as an OPC UA server and client at the same time. As a server it makes PLC and device data available to OPC UA clients such as SCADA, MES and ERP systems. The integrated client can exchange data with external OPC UA servers and connect devices from different manufacturers.


1. Create a PC.
Supported functions include historical data, Alarms & Conditions, custom variables, methods and custom information models.


2. Inserted the OPC server (SW8.2) into slot 1.
== IIoT, edge and cloud ==


3. Inserted the Ethernet interface (IE General SW8.2) into slot 2.
Depending on the device and configuration, the IBH Link UA supports:


[[Image:IBH_Link_UA_S7_DB_tags.png|803px]]
* MQTT publish/subscribe and Sparkplug B
* Python methods and custom data models
* connections to cloud services such as AWS and Microsoft Azure
* [[IBH Link UA:Docker|Docker]] on supported quad-core devices
* TeamViewer IoT remote access


4. Next the S7 connection to the required controls are established.
== Network and firewall ==


5. The variables are easily configured in the properties of the OPC server.
The network interfaces can separate the machine network from the management network. The integrated firewall restricts communication between these levels. Depending on the hardware revision, the device provides four Fast Ethernet ports or two Gigabit Ethernet ports.


6. Subsequently the configuration is transferred via Ethernet into the IBH Link UA. The IBH Link UA then immediately knows the access paths to the controls and puts the required variables in the OPC client. All done!
Network settings, firewall rules and OPC UA endpoint URLs are configured in the web interface.


==Communication with the controllers==
== Security and certificates ==


The communication with the control takes place using TCP / IP. If the control has no Ethernet port available, the function can be achieve by using the proven communication adapter [http://www.ibhsoftec.com/IBH-Link-S7-PP-Eng IBH Link S7++] or [http://www.ibhsoftec.com/IBH-Link-S5-PP-Eng IBH Link S5++]. The IBH Link UA has three Ethernet ports for the machine level and one Ethernet port for the management level. On the management level only OPC access are possible. A firewall between the two levels is integrated. The configuration of the ports is accomplished via a standard web browser.
OPC UA security includes user authentication, message signing, encryption and certificate-based trust. The device supports current OPC UA security policies and centralized certificate management through a [[IBH Link UA:GDS|Global Discovery Service (GDS)]].


[[Image:IBH_Link_UA_ports_eng.png|600px]]
See [[IBH Link UA:Startup operations#Security|Security]] and [[IBH Link UA:Startup operations#Certificates|Certificates]] for commissioning details.


==OPC Data Access==
== Operation and monitoring ==


OPC Data Access, also known as OPC DA, is a set of standards providing the specifications for the transmission of real-time data from data processed devices such as PLCs to display and interface devices such as Human Machine Interfaces (HMI). The IBH Link UA can be accessed by multiple OPC UA clients. This provides a data source for any OPC UA compliant applications such as SAP, MES and ERP systems available.
The web interface provides system status, diagnostics, logs, configuration backup and restore, and firmware administration. The device can also be integrated into a monitoring system through [[IBH Link UA:Nagios|Nagios/NRPE]].


[[Image:IBH_Link_UA_Address_space.PNG|916px]]
== Further information ==


==Historical Data==
* [[IBH Link UA:Startup operations|Startup operations]]
 
* [[IBH Link UA:Technical data|Technical data]]
While OPC Data Access allows the access to data in real time, supports OPC Historical Access, also called OPC HDA access, access to already stored data. From simple data logging systems to complex SCADA systems historical data can be queried on standardized manner. The activation of the Historical data is easily performed using the web browser.
* [https://www.ibhsoftec.com/en/p/ibh-link-ua IBH Link UA product page]
 
* [https://www.ibhsoftec.com/en/p/ibh-link-ua-quad-core-64-bit IBH Link UA Quad Core 64-bit product page]
[[Image:IBH_Link_UA_HDA_Web_Eng.PNG|1240px]]
 
[[Image:IBH_Link_UA_HDA.png|1146px]]
 
==Safety==
 
The IBH Link UA provides a certificate management for secure communication. For this purpose, an appropriate software interface is provided, which can be displayed in any web browser. In this configuration the security levels and to the certificates are managed. This is placed onto the mechanisms defined by the OPC Foundation. OPC UA Security includes authentication and authorization, encryption, and data integrity by signing. Therefore the control will be protected of the uncontrolled access by a superior system.
 
[[Image:IBH_Link_UA_Security.png|880px]]
 
There are different levels of encryption '''None, Basic128Rsa15''' and '''Basic256'''
 
{|
 
|-
 
| '''None''' || No encryption
 
|-
 
| '''Basic128Rsa15''' || 128 Bit encryption
 
|-
 
| '''Basic256''' || 256 Bit encryption
 
|}
 
The IBH Link UA supports the level '''Sign''', '''Sign and Encrypt''' and '''Sign + Sign and Encrypt'''
 
{|
 
|-
 
| '''Sign''' || The messages contain signed certificates
 
|-
 
| '''Sign and Encrypt''' || The messages contain signed certificates and are encrypted
 
|-
 
| '''Sign + Sign and Encrypt''' || The messages may contain only signed certificates, or can be signed and are encrypted as well
 
|}
 
<br />
 
<br />
 
<br />
 
== Certificates ==
 
Exchange of Certificates is another important security level of OPC UA.
 
A communication is only possible, if both Server and Client have a valid certificate assigned by the respective partners.
 
[[Image:IBH_Link_UA_Server_Client.png|700px]]
 
[[Image:IBH_Link_UA_Trust_Certificate.png|880px]]
 
<br />
 
<br />
 
<br />
 
==OPC Client==
 
One of the advantages of the IBH Link UA from IBHsoftec is, that the IBH Link UA supports Client and Server functions simultaneously.
 
This allows data exchange between different OPC UA Servers.
 
For example control systems and other equipment with OPC UA servers from different manufacturers can exchange data with each other.
 
 
The configuration of the client functions will be made using a standard web browser.
 
 
[[Image:IBH_Link_UA_Client_Read_Status.png|1041px]]
 
==Additional advantages==
 
The gateway can optionally use a MicroSD memory card to save the data temporary locally. In the case of an exchange of the device, it offers the advantage of faster new configuration. Another important aspect of the compact device is that it is an independent assembly and does not require a Windows PC.

Latest revision as of 12:28, 5 August 2026

Overview

The IBH Link UA connects PLCs and industrial devices to OPC UA, IIoT and cloud applications. Depending on the hardware version, it provides an OPC UA server and client, protocol gateways, certificate management, firewall functions and edge services in a compact DIN-rail device.

IBH Link UA

Configuration and administration

The device is administered through its web interface. PLC variables and address spaces can be configured using:

Projects and variable definitions are transferred to the IBH Link UA over Ethernet. Symbolic access, data-block structures and variable attributes can be included in the OPC UA address space.

OPC UA server and client

The IBH Link UA can operate as an OPC UA server and client at the same time. As a server it makes PLC and device data available to OPC UA clients such as SCADA, MES and ERP systems. The integrated client can exchange data with external OPC UA servers and connect devices from different manufacturers.

Supported functions include historical data, Alarms & Conditions, custom variables, methods and custom information models.

IIoT, edge and cloud

Depending on the device and configuration, the IBH Link UA supports:

  • MQTT publish/subscribe and Sparkplug B
  • Python methods and custom data models
  • connections to cloud services such as AWS and Microsoft Azure
  • Docker on supported quad-core devices
  • TeamViewer IoT remote access

Network and firewall

The network interfaces can separate the machine network from the management network. The integrated firewall restricts communication between these levels. Depending on the hardware revision, the device provides four Fast Ethernet ports or two Gigabit Ethernet ports.

Network settings, firewall rules and OPC UA endpoint URLs are configured in the web interface.

Security and certificates

OPC UA security includes user authentication, message signing, encryption and certificate-based trust. The device supports current OPC UA security policies and centralized certificate management through a Global Discovery Service (GDS).

See Security and Certificates for commissioning details.

Operation and monitoring

The web interface provides system status, diagnostics, logs, configuration backup and restore, and firmware administration. The device can also be integrated into a monitoring system through Nagios/NRPE.

Further information