OPC UA communication
9.3 Using the S7-1500 as an OPC UA server
Communication
Function Manual, 11/2019, A5E03735815-AH
205
●
Node type
Type of the OPC UA node, for example BOOL, BYTE, INT.
These node types were defined by Siemens, not by the OPC Foundation. For example,
the OPC Foundation uses the Boolean node type for BOOL. BOOL is directly derived
from Boolean.
The specified node type cannot be changed in this dialog: If you want to use a different
node type, you must change the type of the respective PLC tags in the STEP 7 project.
●
Data type
The SIMATIC data type used in the STEP 7 project is specified, for example, Bool, Byte,
Int. etc.
●
Access level
–
If an OPC UA node is a tag (UAVariable type), the node can only be readable (RD) or
readable and writable (RD/WR).
–
If an OPC UA node is a method (UAMethod type), this node can always be called.
●
Local data
The SIMATIC data type of the data block in the CPU, from which the value of an OPC UA
node (UAVariable type) is read, or to which a value is written.
Consistency check
You have the option to check the server interface.
During the consistency check, STEP 7 checks whether the OPC UA nodes of the server
interface are each assigned to a suitable OPC UA element (identical data type) or whether
the used element still exists in the CPU.
To check the consistency of the server interface, click on the following icon in the toolbar of
the OPC UA server interface editor:
Figure 9-32 "Consistency check" button
Export interface
You have the option of exporting the OPC UA server interface as an XML file. This XML file
contains all data type definitions referenced by the server interface.
To export the OPC UA server interface, click on the following icon in the toolbar of the OPC
UA server interface editor:
Figure 9-33 "Export interface" button
See also
Summary of Contents for SIMATIC ET 200SP
Page 1: ...Communication ...
