DeviceHub Add a Tag
Estimated reading time: 4 minutes
Once you connect a PLC to OT Link Platform DeviceHub, you can define the PLC registers that DeviceHub will collect data from. Every PLC has memory registers that store sensor and system values, such as the timer counter. The list of registers includes the analog input, the analog output, the digital input, and the digital output.
DeviceHub Data Publishing Formats contains detailed information about Topic formats.
DeviceHub Tag Overview
A DeviceHub Tag enables data collection from a specific memory location (register) in a PLC. The DeviceHub Tag generates a Raw Topic for publishing data to a message broker for further distribution. OT Link Platform can publish data to Workload Orchestrator through IPSO topics and Cloud Connectors.
The OT Link Platform message brokering system allows for subscribing from and publishing to local and IPSO (Internet Protocol for Smart Objects) Topics.
- A DeviceHub Tag generates a Raw Topic, the Topic for publishing and subscribing through the local message broker.
- The Raw Topic will be used to configure a DataHub Cloud Connector and Topics to connect to Workload Orchestrator.
- In lieu of Workload Orchestrator, collected data can be viewed at the edge using OT Link Platform Flows. See Use OT Link Platform Flows to Visualize Data Flows.
The above example shows the tag attributes to configure
- Tag Name - User-defined name
- Polling Interval - Elapsed time in seconds to poll the PLC register
- Address - Register in the PLC to poll.
- Value Type - Data type of the value stored in the register.
- Raw Topic - Local message broker topic.
- IPSO Topic - After OMA binding is applied, DeviceHub creates an IPSO topic to publish data in the OMA format. (See DeviceHub OMA Binding)
Make sure to choose a polling interval greater than 1 second to ensure that the OT Link Platform network will not be flooded with unnecessary data.
Add a Tag to DeviceHub
You can add a tag for a single PLC register, or upload tag details with a comma-separated values (.csv) file. This procedure lists the steps for a single register.
A DeviceHub PLC device connection. See DeviceHub Add, Monitor, or Delete Device.
After a PLC device is connected to the OT Link Platform Converged edge system using DeviceHub, create tags to define the device registers from which data will be collected.
Note: These steps show an example of a Modbus configuration. Each device driver will have its own specific fields to be configured.
To add a tag for a single register:
- Click DeviceHub from the navigation panel.
- Click Tags from the sidebar.
- Click to the right of the Tags list.
- Select Add One.
Select the Device from the drop-down list. Only devices created in DeviceHub will be listed.
The fields displayed in this Add Tag dialog depend on the PLC device driver type.
- Select the Value Type: string, integer, float, or bit.
Enter a Tag Name and Polling Interval (in seconds).
- Select/enter a Register Name (Scroll to reference the register table listed at the bottom of the form) and click Add Tag.
Free Tag and OPCUA Driver information:
Certain PLC device drivers, such as Allen-Bradley CompactLogix, will not have a list of register names in the Add Tag form. These are referred to as Free Tags.
- You must enter case-sensitive register names exactly how they are defined in the PLC.
- Devices will not display a Connected status until a tag with a correct register name is created. See Troubleshoot Device Connectivity Status.
- For OPC UA, map the OPC server tags to the client. Enter the Register Name using this format, where the semicolon is significant:
OT Link Platform can publish data obtained on the local message topic (raw topic) to Workload Orchestrator through local message topics connected to the DataHub cloud connector. You can also directly connect PLC device data to cloud connectors. See DataHub: Add a Cloud Connector
Subscribing to DeviceHub Topics
To receive data from device registers, you will need to subscribe to Topics. OT Link Platform Flows provides ways to Subscribe to All Topics or to Individual Topics. You can also use DataHub Cloud Connectors to view data from subscribed Topics in Workload Orchestrator.
Wildcards allow you to easily subscribe to multiple topics and receive data from each one.
When you start adding DeviceHub Tags, you will notice that each topic starts with similar characters. Topics support the following Wildcard characters for subscribing to multiple topics:
> Wildcard Character: To subscribe to multiple topics, you can use the > character. You can use devicehub.raw.75B8BB04> to subscribe to the 3 topics in the above screenshot, for example. This allows you to receive the messages from multiple Tags.
* Wildcard Character: You can use the *** wildcard character in order to match a single token between. characters in tags. Thus, using devicehub.raw.*.* will match all topics that start with devicehub.raw and have two character sequences after each of the two **. characters.