OPC UA Client¶
On this page, you can configure everything to get data from an OPC UA Server into the CMTK and display that data in Grafana. To install the OPC UA Client, download the APP and install it on the CMTK.
The client settings can then be found under Settings > IoT Communication > OPC UA Client
Activate OPC UA client¶
To activate the client:
- Activate the toggle OPC UA Client enabled
- Set the OPC UA Server enpoint
- Select the security policy and the message security for the connection
- Select the Authentication method
-
Save the changes by cliking the Save button
-
(Optional) Server Certificate validation. It is possible to upload the Server Certificate to add another layer of security. This prevents a man-in-the-middle attack.
Note
The CMTK can connect to 1 OPC UA Server.
Authentication methods¶
Select the authentication method for the client. Only one method can be used simultaneously.
Anonymous¶
If this authentication method is enabled, an OPC UA server can connect without a separate login.
Username/Password¶
This authentication method requires a user name and password to connect to the OPC UA server. You can specify these in the input mask and activate them by saving.
Certificate¶
Use the CA certificate to establish a secure connection. The CA certificate can be found in Certificates section.
Nodes¶
A total of 10 nodes can be configured to get data from the server.
- Configure the Node Id
- Select mode. Subscribe The readout takes place with every value change. This can also be done faster than 1x per second. Cycle reading The values are read in a fixed interval. You can define the readout interval in seconds in the field cyclic readout interval. The minimum is 1 s.
You can copy the MQTT Topic for every Node Id to the clipboard by clicking the copy button.
Note
You can get the Node Id of a specific signal from the server using tools like UAExpert.
Note
The time setting on the OPC-UA Server should be checked and updated if necessary, since the time stamp of the data is determined by the server.
Note
The Node Id does not support special characters like @, "".