User Documentation

System overview
System manual
2696790000/02/04.2020
24
3.7.3 OPC UA interface
The u-create system offers the opportunity to access to IEC variables of the
control via an OPC UA interface. Therefore an OPC UA client which must be
installed on a PC is needed. OPC UA clients are offered for download in the
internet.
To establish a connection with the OPC UA client to the OPC UA server on
the control the IP address or the hostname of the control with the port num-
ber 4842 first have to be input into the client. If a server has been found the
endpoint "None - None" must be selected. Then the connection to the server
can be established and the data available on the OPC UA server (variables,
functions, ...) are shown. For a detailled description see the help of the OPC
UA client.
The server/endpoint URLs delivered of the OPC UA server always contain
the hostname. For this reason it must be possible for the OPC UA client to
solve the hostname. Some OPC UA clients do not offer his functionality. If
this is not the case the control must be inserted manually into the file C:
\Windows\System32\drivers\etc\hosts on the PC. Therefore a new line
with the IP address and the hostname must be added in this file (e.g.
10.150.48.40<Hostname of control>).
3.7.4 REST-API (Representational state transfer)
The u-create system offers the possibility of a visualization connection via
REST-API (Representational state transfer) interface. The interface descrip-
tion is available as OpenAPI specification in YAML format.
The API can be accessed via an Internet browser at the following address:
<Control IP address>/api
The current version of the REST API is displayed via this address. By ap-
pending the version to the address, the supported interface is displayed (e.g.
192.68.1.1/api/v3)
The following services are offered and listed as interface file:
● configuration.yaml: Specifing basic configurations (e.g. network ac-
cess, date and time, ...)
● device-service.yaml: Executing basic commands of the control (e.g.
start, stop, ...)
● diagnostics.yaml: Supporting of diagnosis information (e.g. statusre-
port, ...)
● license-text.yaml: Reading "Open Source" license texts of the con-
trol
● licensing.yaml: Performing licensing (e.g. activating licenses, license
overview, ...)
● report-system.yaml: Connection to the report system (e.g. reading out
error, acknowledge error, ...)
● update-service.yaml: Performing a backup or restoring this
● variables.yaml: Reading and writing of released variables