OPC UA communication
9.3 Using the S7-1500 as an OPC UA server
Communication
Function Manual, 12/2017, A5E03735815-AF
211
To minimize risks in the case of an extension or adaptation of the server address space,
follow these steps:
1. Protect the project (project navigation: Security settings > Settings).
2. Export the corresponding server interface before the extension or adaptation.
3. Revise this OPC UA XML file.
4. Import the file again as a server interface.
The table below shows the compatible SIMATIC data type for each OPC UA data type.
Assign the data types as shown below (SIMATIC data type – OPC UA data type). Other
assignments are not permitted. STEP 7 does not check the observance of this rule and does
not prevent an incorrect assignment. You are responsible for the rule-compliant selection
and assignment of the data types.
You can also use the listed data types, for example, as elements of structures/UDTs for input
and output parameters of self-created server methods (UAMethod_InParameters and
UAMethod_OutParameters).
Table 9- 10 Mapping of data types
SINT SByte
Enumeration (Encoding Int32) and all derived data types
User-defined data type required (UDT,
user-defined data type)
The user-defined data type must be
created with the prefix "Union_", for ex-
ample "Union_MyDatatype"; see exam-
ple below table.
The first element (Selector) in this UDT
must have the data type "UDINT".
UNION and all derived data types
To Next Page
Loading...
