...
This section provides the user-level configuration details of an OPC UA server, once a client-server secured connection is established.
The endpoint (see "transport_layer.url
") is an OPC UA interface and provides several means of use by a client (Browse, Read, Write, Subscribe). The following items allow any connected client to access directly all server data without required use of browsing, provided that it has knowledge of the PIVOT object it needs.
...
- As a standard OPC UA server, all functional data are organized under the
Root.Objects
node of namespace 0 ( nodeId =i=85
). - For each PIVOT data, there is one node under
Root.Objects
with:- NodeClass =
Object
- NodeId=
ns=1;s=
<PIVOT_ID>
, with<PIVOT_ID>
as provided inexchanged_data.datapoints[].pivot_id
section configuration. - BrowseName= namespace =1, name =
<PIVOT_ID>
- DisplayName =
<PIVOT_ID>
- References:
- HasTypeDefinition:
FolderType
- HasComponent:
<...>
, one for each variable below
- HasTypeDefinition:
- NodeClass =
NodeId | BrowseName/ DisplayName | IsOrganizedBy | NodeClass | Type | Details |
---|---|---|---|---|---|
| <PIVOT_ID> |
...
(= "i=85") |
| N.A | |||
ns=1;s= <PIVOT_ID>/Cause | Cause | ns=1;s= <PIVOT_ID> | Variable | UInt32 | |
With <PIVOT_ID>
as provided in exchanged_data.datapoints[].pivot_id
section configuration.
Requirements
The following requirements aim at providing a clear
...