Page History

Understanding

TagProvider Connections

TagProviders allows connections with external System, to read our write from those system, without the need the create local Tags. Displays and other modules can directly access the data from remote systems, which can have its structure changing dynamicalu.

Automatic & Tagless Connections!

• Connect to external data sources and consume their Data Models in Unified Namespace.
• Automatically access all tags and data structures by connecting to the provider with a simple configuration
• The connected provider’s Tags and Data model will be available for use in various Modules (Displays, Scripts, Reports, and more)
• Providers to various systems: Protocols, Historians or Devices
• When connecting with Historians, you can easily plot Trend Charts, as well archived data on that external Historian.

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

All TagProviders have common configuration items: Provider, Access Mode, Name, Description, and Test. The Provider specifies the platform the TagProvider will interface with. Access Mode determines permissions for tag interaction: Read allows data reading, Write permits data writing, and ReadWrite enables both. The Name is a user-defined identifier for the TagProvider instance, aiding in identifying the specific configuration within the software platform. The Description explains the TagProvider's purpose or the platform it interfaces with, providing context for its usage. The Test button verifies the connection settings to ensure successful communication with the specified device or data source.

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.

Configuration Workflow

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

Step 1: Identify the appropriate External TagProviders based on the communication protocol of the external data source (e.g., OPC UA, Modbus, Custom).

Step 2: In the software, navigate to the External TagProviders configuration section and create a new instance. Provide necessary information such as the provider's name, communication settings, and any required authentication credentials.

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

Step 4: Create a New AssetFolder in the AssetTree, selecting that folder use toolbar command Insert Link to TagProvider, selecting the initial node on the TagProvider data that will be incorporated to the AssetTree.

Step 5: You can customize the Alias for that Node

Creating a new TagProvider Source

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:

• 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).
• Access: AccessType for this connection (Read/Write/ReadWrite).
• ReadTime: Read Pooling Rate.
• WriteTime: Write Rate.

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

For more information, please refer to the specific protocol documentation.

Using TagProviders as Historian Storage Location

Some TagProvider, can be used in connection 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.

Browsing the values

Go to Unified Namespace → AssetsTree

You can browse the tree, the right side tables will updated showing the contents of 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: