Page History

Understanding TagProvider Connections

TagProviders allows allow connections with external System, systems to read our write from those system, without the need the create local Tagsor write data without creating local tags. Displays and other modules can directly access the data from remote systems, which can have its structure changing dynamicalueven if their structure changes dynamically.

Automatic & Tagless Connections!:

• Connect to external data sources and consume their Data Models in Unified Namespace.

• Access all tags and data structures

• automatically with a simple configuration.
• The connected provider’s

• tags and data models are available for use in various

• modules (Displays, Scripts, Reports,

• etc.).
• Providers to various systems: Protocols, Historians, or Devices

• .
• Easily plot trend charts and access archived data from external Historians.

Supported TagProviders

Integration with Historian Systems

• Canary Labs
• InfluxDB
• OSIsoft PI Systems
• GE Proficy
• SQL Databases

Integration with Communication Protocols

• MQTT (standard and SparkPlugB)
• OPC-UA
• Rockwell ControlLogix
• Codesys enabled PLCs

Integration with other Applications

• Server to Server
• Line Monitor

Configuring  TagProviders

Common Configuration Items:

• Provider: Specifies the platform the TagProvider will interface with.
• Access Mode

• : Determines permissions (Read, Write, ReadWrite).
• Name: User-defined identifier for the TagProvider instance

• .
• Description: Explains the purpose or platform it interfaces with

• .
• Test button

• : Verifies the connection settings

While some parameters address common needs like connection settings and data access modes, others are unique in that they cater to each system's particular functionalities and technical characteristics. Each External TagProvider has its own configuration parameters tailored to meet specific technical requirements and specifications. These unique parameters ensure that each TagProvider can interface with the platform, enabling data integration according to individual operational requirements.

• .

Unique Configuration Parameters:

Each TagProvider has specific parameters tailored to its functionalities and technical requirements, ensuring proper data integration.

Configuration Workflow

• Identify the TagProvider: Based on the communication protocol

Configuration Workflow

To connect to external data sources to use its data definitions models, follow the steps below:

• (e.g., OPC UA, Modbus

• ).

• Create a New Instance: Navigate to the External TagProviders

• section and

Step 3: Test the Connection, exploring the Data. (You can perform it directly at the Unified Namespace AssetsTree page)

• provide necessary information.
• Test the Connection: Verify and explore the data.
• Create a New AssetFolder

• : In the AssetTree,

• use the toolbar command

• “Insert Link to TagProvider

Step 5: You can customize the Alias for that Node

The Step to Create is an AssetFolder and Insert a Link to a node from the TagProvider is necessary to use the TagProvider data within the solution. 

• .”
• Customize the Alias: For the selected node.

Creating a new TagProvider

Connection

Steps:

1.Navigate: Go In your Engineering Environment, navigate to Unified Namespace / External TagProviders. 

Click on the 'New Item' button to launch a dialog window titled 'Create New External TagProvider'. From the provided list, select a Communication Protocol and assign an appropriate name.

After you select a Protocol, you will see a configuration table with columns that are similar to the ones in the Channels, Nodes, and Points pages. However, the columns will all be grouped on a single page. For this example, we will use MQTTspB.

The configuration settings are detailed below:

→ TagProvider Connections.
2.New Item: Click the ‘New Item’ button to open the ‘Create New TagProvider’ dialog.
3.Select Protocol: Choose a communication protocol and assign a name.
4.Configure: Fill out the configuration table with:

• Name: Identifier for the provider.
• Provider: Chosen communication protocol
• Name: Name of the provider. This will be used to access elements from this namespace.
• Provider: Communication Protocol of choice.
• Parameters: Char separator for the communication protocol of choice.
• Primary/Backup Station: Connection String information used to establish a communication (same as on Devices / Nodes)string information.
• Access: AccessType for this connection Access type (Read/Write/ReadWrite).
• ReadTime: Read Pooling Ratepooling rate in ms.
• WriteTime: Write Rate.

The Primary/Backup Station will be configured according to the communication protocol.

• rate in ms.

For example, using MQTTspB, the settings will be detailed similarly to Channels, Nodes, and PointsFor more information, please refer to the specific protocol documentation.

Using TagProviders as Historian Storage Location:

Some TagProvider, TagProviders can be used in connection with the Historian Module . 

The Historian, by default, archives the data in a SQL Database.

That can be extended, using a TagProvider to define where the data will be save. 

Not all TagProviders can be used for Historian, typically the ones connecting to Historian tools, or MQTT.

For more information, go to section Historian ? Storage Locations.

Working with TagProviders

Access Elements in Engineering

Once you finish your configuration and establish a successful connection, you will be able to access the variables from the Device in various places within the Engineering Environment.

to define data storage locations. Typically, TagProviders for historian tools or MQTT can be used as Storage Locations.

By default, the Historian archives data in an SQL Database, but this can be extended with TagProviders.

→ See Historian Storage Locations for more information

Working with TagProviders

Browsing Values

At Unified Namespace → AssetsTree, after using linking some folder to the data from the TagProvider Connection, ou

Browsing the values

Go to Unified Namespace → AssetsTree

You can browse the tree, the right side tables will updated showing the contents value of the Selected Foldervariables in the selected folder.

Reading and Writing values from other Modules 

After including TagProvider in the AssetTree nodes, you can access that in using the Asset() method.

.E.g.:,if using ControlLogix, the final part of the AssetPath is the address, using same syntax used in Devices / Points: <ProviderName>.("<Type>:<Address>")

• Asset("/Folder1/DINT:MyPlcTag")
• Asset("/Area1/Line1/DINT:MyArray1DimDINT[0]")

You can use the Asset() syntax, not only in scripts, but on Displays, and in all fields in the software where a Tag is expected, including:

• On Displays, mapping Symbol properties, linking Dynamic properties,
• On Alarms, creating Alarm events
• On Historian, archiving the data

In this section: