Adding a data container
OPC UA data containers allow access to the information model of OPC UA servers. The node IDs of the data to be collected are combined in a data container and recorded in connected servers via a corresponding subscription.
To add a data container, proceed as follows:
- At least one OPC UA server and one endpoint have been created.
- Open the "Data container" tab.
- Click [+ Add].
- The "Data container configuration" dialog window opens.
- The data container can be configured via the following setting fields:
Setting field | Description |
|---|---|
Name | Enter a name for the data container. The name is used in the tool configuration process and in the file structure when storing the JSON files. |
Identifier (ID) | Unique identifier of the data container that is generated automatically by the software and used internally for further processing. This identifier forms part of the name of the target directory on the associated endpoint. |
Description | Add optional description text. The description text is displayed on the "Data containers" tab. |
Update strategy | Specify the update strategy of the data container:
|
Update interval | Specify the update interval for cyclic data acquisition. The update interval describes the time between two successive cycles. Each cycle consists of reading and transferring data and takes about 100 ms. For example, an update interval of 5 ms results in a cyclical output interval of approx. 105 ms. The maximum value for the update interval is 31 days. |
Options | |
Enable data container | Activate or deactivate data recording by the data container. |
Transmit the data events of this data container to the endpoint | Activate or deactivate data transmission from this data container to the selected endpoints. |
Endpoints for storing data events | Select one or more of the configured endpoints as the storage location for the recorded data. All entries created in the "Endpoints" menu are available here. |
Read asset ID from the device and publish | Enable the asset ID reading function of data nodes. |
Read asset ID from a data node | Select the data node for reading the asset ID. |
Alternative external ID | Specify an alternative external ID. |
Server | |
[+ Add] button | Add an OPC UA server to read data for data acquisition. All of the entries that are created under the "Servers" tab are available here. |
Trigger | |
Enable trigger event | Activate a trigger event, the occurrence of which should cause data to be published, and use the choice boxes that appear to enter the data node ID, the first edge value, the second edge value, and the delay between the values. |
Force a cyclic trigger | Activate the forcing of a cyclic trigger. A cyclic job writes periodically configured edges to the trigger node and causes a change in the added subscription item, which triggers the OPC UA server to publish the data for the subscription. |
Data transfer and volume estimates | |
Estimation of the collected data volume at field level (OT network) and the transferred data volume (IT network) | |
