OPC UA Server CNS

Configuration

The ID of the view which shall be mapped to the address space must be specified using the Plantmodel Editor. With this the corresponding View ID is mapped to the internal data point element Config.CNSView of the _OPCUAPvssServer DP. Only one view can be assigned to each server.

The OPC UA server checks the Config.CNSView data point element only on starting. If another view shall be mapped to the address space, the other view ID must be defined on the data point element. After that the server must be restarted. In case of an invalid view ID the server is shut down and the following error message is displayed::

SEVERE, 54, Unexpected state, CNSViewBrowser, Constructor, View 'View13' doesn't exist!

The WinCC OA system name and the view name are not part of the server's address space. The first level of the address space is always the first level of the defined CNS view which means the first node.

AccessLevel

The AccessLevel attribute must be used to define how the value of a variable can be accessed (read/write). The OPC UA server only represents nodes for which an appropriate AccessLevel is defined.

To define the AccessLevel for a node, the keyword OA:OPC with a value of data type UINTEGER_VAR must be stored in the node's UserData (either automatically via Plantmodel Editor - OPC or cnsSetProperty). All child notes for which the AccessLevel is not explicitly set inherit the AccessLevel of the parent node.

Mapping to the server address space

Data points can be assigned to nodes of a CNS view. If a data point element is assigned to a node and the AccessLevel is defined, the object for this CNS node has the NodeClass "Variable" and represents the current value of the linked data point element.

CNS Nodes without any linked data point element are represented by objects with NodeClass "Object".

Consider the following information:

• A node without AccessLevel is not represented in the server address space unless the AccessLevel of at least one child nodes is defined and the child node is assigned to a data point element
• A node with defined AccessLevel but without an assigned data point element is not mapped to the address space, unless there is at least one child node with an assigned data point element.
• A parent node with assigned data point element but without defined AccessLevel is mapped with NodeClass "Object" if the AccessLevel is defined for one of the child nodes.
• The structure of objects in the address space equates to the linked data point structure. If a data point element structure is assigned to a node, the OPC UA server appends all elements of the linked structure to the CNS node.

  The data point element names of the linked structure are used for the OPC UA node ID. If the data point element names of the linked structure are conflicting with CNS nodes with the same ID, the OPC UA server displays an error message in the LogViewer. In this case the nodes which are already existing in the address space remain unchanged and the new conflicting nodes are not added to the address space.

• Data point elements that are linked to a node must have a _alert_hdl config before creating the corresponding link. If the config is not available the required alarm conditions cannot be created.

  Adding the config after linking the elements is not sufficient. The link to the node must be removed and newly added.

The attributes of a CNS view are mapped to the address space in the following way:

Additional information

Changes to the CNS view

Following changes to the used CNS view are applied dynamically to the address space at runtime:

• Creating new nodes
• Deleting existing nodes
• Changing the node ID
• Linkage of data point elements with nodes
• Deleting data point element assignments
• Changing the AccessLevel of nodes

Modifications to the WinCC OA data point types (e.g. adding a new node to an existing data point type or changing the element type) are not applied to the address space at runtime. Therefore the server must be restarted after changing the data point type of a data point element (structure) which is linked to a CNS node.

Separator

On creating a CNS view an arbitrary separator can be defined. This character is also used as separator for the ID path. The CNS ID path is used by the server to create the OPC UA NodeId. In this case the character "." is always used as separator. If a data point element structure is linked to a CNS node the character "." is also used for adding the individual data point element names of the structure to the NodeId.

Example for mapping a CNS view to the server

The following example shows how a CNS view can be mapped to the address space of a OPC UA server.