The NETx Servers provide a standardized OPC UA (Unified Architecture) interface. OPC UA is one of the most important communication protocols for Industry and the IoT.
OPC UA installation
The OPC UA extension is available through the Extension Manager. When the server is stopped, the Extension Manager can be started from the studio menu Extensions / Manager / Start extension manager...
...
.
...
After
...
Finally, close the studio and reopen it again. This is required before the extension can be used.
OPC UA as Server
After having installed the OPC UA extension, some basic settings have to be done. To do so, start the studio and open the menu entry Modules / > OPC UA / > OPC UA server configuration...
First of all, enable the OPC UA driver has to be enabled (option "by ticking Enable OPC UA"). Then, a username / password for connecting to the OPC UA interface can be set. As an alternative, "Anonymous Access" can be enabled. . Find more information about the remaining configuration options in the reference manual.
After having changed the required settings, the server must needs to be restarted.
...
After the server restart, the Now the Server Items of the NETx Server will are available through OPC UA. To connect from an OPC UA client, the an OPC UA connection URL for the NETx Server has to be entered. These server URLs can be found within is required. Find the configured server URLs in the System Log Messages after server startup. Open the system log file and search for the following entries:
| Code Block |
|---|
Plugin.OPCUA The following Endpoint URLs are available: Plugin.OPCUA opc.tcp://<host name>:48400/UA/NETxBMSPlatform Security: http://opcfoundation.org/UA/SecurityPolicy#None Plugin.OPCUA opc.tcp://<host name>:48400/UA/NETxBMSPlatform Security: http://opcfoundation.org/UA/SecurityPolicy#Basic256Sha256 Plugin.OPCUA opc.tcp://<host name>:48400/UA/NETxBMSPlatform Security: http://opcfoundation.org/UA/SecurityPolicy#Basic256Sha256 Plugin.OPCUA https://<host name>:48401/UA/NETxBMSPlatform/ Security: http://opcfoundation.org/UA/SecurityPolicy#Basic256Sha256 Plugin.OPCUA OPC UA started |
Using these URLs, you can connect from any OPC UA client can connect to our NETx Server.
Access rights and permissions
If an OPC UA client is connecting to an OPC UA server, a secure transport channel is established. In addition, the OPC UA client must authenticate to the OPC UA server using a username and password. In the OPC UA server configuration it is possible to define one user (i.e. username and password) who has full access to the whole OPC UA address space:
As an alternative, anonymous authentication (i.e. connection without username / password) can be enabled:
For our NETx BMS Platform, a more sophisticated authentication scheme is possible. If enabled, the user database of the NETx BMS Platform can be used:
This means that the same username and password combinations are used as for the visualization and Web Manager login. Starting with NETx BMS Platform R2 Build 1000, for each BMS user, the role permission for OPC UA can be configured within the Web Manager:
| Role | Permission |
|---|---|
| Super Administrator | full access to the OPC UA address space |
| Administrator | full access to the OPC UA address space |
| Manager | full access to the OPC UA address space |
| Viewer | read-only access to the OPC UA address space |
| Info |
|---|
For troubleshooting, the log level of the OPC UA driver can be increased. The corresponding log entries are stored in a separate log file (<WorkspaceDirectory>\LogFiles\xio.OpcUa.log). More information about the configuration can be found in the OPC UA driver configuration. |
Article applies to the following products:
- NETx BMS Platform
- NETx Multi Protocol Server
- NETx BMS Server 2.0
...