User Documentation
Table Of Contents
- Table of contents
- 1 Introduction
- 2 Safety instructions
- 3 System overview
- 4 Operating behavior
- 5 Software installation
- 6 Configuration
- 7 Program development
- 8 Licensing
- 9 Device Administration (DevAdmin)
- 10 Software units
- 11 OPC UA Server
- 12 Node-RED
- 13 LongtermDiagnosticMonitor
- 14 Data recorder
- 15 Diagnostics
- 16 Maintenance
- 17 Technical data
- 18 Directives and standards
- 19 Appendix: Tutorial - creating an IEC project
- 20 Appendix: Addressing in the Ethernet (basics)
- 21 Appendix: Tutorial FoE
- 22 Appendix: Tutorial - call C function from IEC
- Index

OPC UA Server
System manual
2696790000/02/04.2020
70
Node-based XML rights
The globally declared authorizations of a role can be extended or restricted
for each node.
The following example overwrites the authorization of the "Operator" role for
the "Var1" variable node. In the global authorization definition "Browse", the
role "Operator". can perform read and write accesses. For the "Var1" vari-
able node the access to browse and read is now restricted.
<Variable
DataType="0:Types.0:DataTypes.0:BaseDataType.0:Boolean" NodeId="i=5000"
BrowseName="Var1" DisplayName="Var1" AccessLevel="0x03" ValueRank="1">
<NodeRolePermissions>
<RolePermission RoleName="Operator" Permissions="0x21"/>
</NodeRolePermissions>
</Variable>
11.6 Logging of server operation
The OPC UA server protocols information and errors about startup and exe-
cution at runtime. This information is either integrated into the general log-
ging of the control and thus displayed in the trace monitor (in the u-create
studio) or managed by the server as a separate file. This file is stored on the
controller in the directory /opt/kecontrol/protocol/OpcUa/. The mes-
sages outputs here can provide useful information, in particular, for trou-
bleshooting during information model creation (incorrect variable mapping,
typing errors, already existing NodeIds, etc.).
Logging can be configured via expert entries (in u-create studio). If there is a
general logging of the control, only the TraceMask parameter is taken into
account. If a separate file is managed, the TraceFileSizeKbMax parameter
can be additionally specified.
The value of the TraceMask configures the granularity of the output and is
executed as a bit field. By default, the configuration is set to TraceMask = 5.
The value to be set results from the bitwise addition of the following partial
masks:
Bit
Partial
mask
Logging
0 1 Startup information and error, configured by default
1 2 More detailed information and error output during startup
2 4
Runtime error (internal failures e.g. memory bottleneck, unex-
pected types for read/write etc.), configured by default
3 8 Detailed output about runtime errors
The TraceMask is interpreted as a decimal number. To activate all outputs,
the TraceMask can be set to the value -1.
The TraceFileSizeKbMax parameter specifies the maximum file size in kB.
The default value is 4096 kB. Once the maximum size has been reached, a
further log file with suffix .1 is created. The log files are then overwritten.
Example