Publicité
Safety risk due to direct connection to the Internet or the company net-
work!
The AES module has not been designed for connection to the Internet or a
company network and is not adequately protected against unauthorized ac-
cess.
Devices that are connected to the Internet or a company network, have to be
adequately protected against unauthorized access, e.g. by using a firewall and
network segmentation. The AES module has only been designed for operation
in an Ethernet-based fieldbus network.
Do not connect the AES module directly to the Internet or a company net-
u
work.
AVENTICS GmbH is not liable for any damages resulting from improper use. The
user alone bears the risks of improper use of the product.
2.4 Personnel qualifications
The work described in this documentation requires basic electrical and pneu-
matic knowledge, as well as knowledge of the appropriate technical terms. In or-
der to ensure safe use, these activities may therefore only be carried out by quali-
fied technical personnel or an instructed person under the direction and supervi-
sion of qualified personnel.
Qualified personnel are those who can recognize possible dangers and institute
the appropriate safety measures, due to their professional training, knowledge,
and experience, as well as their understanding of the relevant regulations per-
taining to the work to be done. Qualified personnel must observe the rules rele-
vant to the subject area.
2.5 General safety instructions
• Observe the safety notes found in your bus coupler's system description.
2.6 Damage due to control network malfunction
Products with Ethernet connection are designed to be used on specific industrial
control networks. Observe the following safety measures:
• Always follow industry best practices for network segmentation.
• Avoid exposing products with Ethernet connection directly to the Internet.
• Minimize internet and business network exposure for all control system de-
vices and/or control systems.
• Ensure that products, control system devices and/or control systems are not
accessible from the Internet.
• Locate control networks and remote devices behind firewalls and isolate them
from the business network.
• If remote access is required, only use secure methods such as Virtual Private
Networks (VPNs).
NOTICE! Recognize that VPNs and other software-based products may have
vulnerabilities. A VPN is only as secure as the connected devices it serves. Al-
ways use the current version of the VPN, the firewall and other software-based
products.
• Ensure that the latest released software and firmware versions are installed on
all products connected to the network.
3 About this product
OPC-UA is the interoperability standard for secure and reliable data exchange in
industrial automation and other industries. OPC-UA is a protocol with a semantic
component, which describes each data point in more detail. For example, OPC-
UA describes if the data points are provided with a unit or a range. The OPC-UA
protocol fulfills the functions of the Micro Embedded Device Server Profiles.
4 OPC-UA connection
4.1 Establishing an OPC-UA connection with the AES module
In addition to the fieldbuses on port 4840, the AES-Gen2 module with the proto-
cols Profinet IO and EtherNet/IP provide an OPC-UA server. The OPC-UA clients
can connect to the OPC-UA server in the AES module.
AVENTICS™ AES OPC-UA | R412028203-BAL-001-AB | English
NOTICE
Requirement:
In order to establish a connection, the device that is supposed to connect to the
AES module via OPC-UA must be located in the same subnet. Alternatively, a
gateway has to exist that connects the subnets of the two devices to each other.
It is then possible to establish a connection to the AES module on port 4840 via
OPC-UA.
1. To find the IP address of the AES module, use the protocol-specific tools or the
Ethernet "Device Configuration Tool".
2. Establish OPC-UA connection with the AES module.
4.2 OPC-UA structure
4.2.1 Module data
Each module connected to the AES unit has its own entry in the OPC UA object
model. This depends on whether it is an I/O module or a valve module.
The modules can be found at the following point in the object module:
IoModules-> IoModules-> ModuleXX
ValveModules-> ValveModules-> ModuleXX
XX thereby corresponds to the position of the module in the configuration. The
entries in the object vary depending on the module type. A list of all possible en-
tries can be seen in the following table:
Table 3: List of all entries of a module in the OPC UA object model
BrowseName
Contents
Diagnosis
Diagnosis information
of this module
Input16BitNrX
Analog input data in
the 16Bit format from
input X
Input8BitNrX
Analog input data in
the 8Bit format from
input X
InValueBin
Digital 4Byte input
data as ByteString
InValueUnit32
Digital input data as
Uint32
MaterialNumber
Material number of
the module (number
of the electronic
module for valve
modules)
Output16BitNrX
Analog output data in
the 16Bit format from
output X
Output8BitNrX
Analog output data in
the 8Bit format from
output X
OutValueBin
Digital 4Byte output
data as ByteString
OutValueUnit32
Digital output data as
Uint32
Type
Name of module
Values
Input data and output
data in a JSON-for-
matted String S (see
g 4.2.2 Value de-
scription)
4.2.2 Value description
Value
Per module, a JSON string is generated in the "Value" entry, where output and in-
put data are output at the update time. In large systems these are not always up-
dated with the minimum sampling rate (50 ms). If an update interval of 50 ms is
required for these systems, the RawValue can be used. This is updated preferen-
tially with a sampling interval of approx. 50 ms even in large systems.
Structure of the JSON string:
The string is structured as follows:
1. Opening brace: {.
2. If input data is available: "i":[ with the respective values.
If output data is available: "o":[ with the respective values.
3. Each value is output as a hex-encoded value with a leading "0x".
Data type
Number
Enum
1
Unit16
0 ... 2
Byte
0 ... 4
ByteString
0 ... 1
Uint32
0 ... 1
String
1
Unit16
0 ... 2
Byte
0 ... 4
ByteString
0 ... 1
Uint32
0 ... 1
Enum
1
String
1
12
Publicité
