Search

User Manual

Getting Started


Modules and Platform


Appendix


Tutorials & Helpful Tricks


Glossary


Strategic Partner Links

Sepasoft - MES Modules
Cirrus Link - MQTT Modules

Resources

Inductive University
Ignition Demo Project
Knowledge Base Articles
Forum
IA Support
SDK Documentation
SDK Examples

All Manual Versions

Ignition 8
Ignition 7.9
Ignition 7.8

Deprecated Pages

Skip to end of metadata
Go to start of metadata

 

Tag Providers and Drivers

At the highest level of Tag configuration is the Tag Provider. A provider is a Tag database (a collection of Tags) and a name. An Ignition Gateway can have any number of Tag providers, and therefore the name is used to distinguish which provider a Tag comes from. Tag Providers can be set up with security or even disabled independent of each other.

Every copy of Ignition has its own Tags. With the Remote Tag provider, Ignition can also see the Tags on another Gateway, as long as the two Gateways connected through a Gateway Network.

All Tags reside in a Tag Provider and have realtime values. Additionally, there is the concept of Tag historian providers, which can store and query historical data for Tags. Each Tag can optionally have a historian provider assigned to it to whom it will report value changes for historical storage.

Realtime Provider Types

There are no differences between the two types of Tag Providers other than where the Tag's configuration is stored and executed. You can have as many Tag providers as you want, and there are security settings to either lock them or open them to the network. 

In these examples we refer to two copies of Ignition. The "local" Ignition is the Ignition that you are currently configuring. The "remote" Ignition is another installation of Ignition somewhere on you network.

Internal Tag Provider

Internal Tag Providers store all configuration and do any execution (read, write, history, alarms) through the local Ignition Gateway. Every new Ignition installation automatically creates an Internal Tag Provider named "default." You can add as many Internal Tag Providers as you want.

This provider can be exposed or hidden from other Gateways on the network through the Gateway's OPC-UA settings. 

Remote Tag Provider

Remote Tag Providers connect a remote installation of Ignition and access those Tags. The Remote Tag Provider works by creating a link from the local Gateway to a Tag provider on a remote Gateway using a Gateway Network connection. The local Ignition may be allowed to read and write to the remote Tags, but any execution is handled by the remote Gateway. So, things like writing to a PLC, alarms, and history will still be handled by the remote Ignition.

By default, a Remote Tag Provider will fall under the Default Security Zone and be read only.

On this page ...

IULocgo


Tag Providers

IULocgo


Remote Tag Provider

 

Configuring Realtime Providers

Realtime Tags providers are configured in the Gateway's Config section under Tags > Realtime. After installation, the Ignition Gateway will start with an internal provider defined. You can edit its name and settings by selecting edit to the right of its entry in the table, or create new providers by selecting Create new Realtime Tag Provider below the table.


There are two types of Realtime Tag Providers that you can choose from:

  • Standard Tag Provider
  • Remote Tag Provider

Standard Tag Provider

Tags are stored inside of Ignition and executed by the system.

NameThe name of the provider.
DescriptionThe description of the provider.
Tag Editing Role (s)Users must belong to one of these roles in order to edit this provider's tags in the Designer. Multiple roles can be specified by separating them with commas. If blank, tag editing for this provider will not be restricted in the Designer.
Default DatabaseThe default database connection to use for expression tags that run SQL queries. All query tags with default database providers selected with run their queries against this database source.

Remote Tag Provider

Tag Provider from one Gateway is brought in to another Gateway.

Name

The name of the provider.
DescriptionThe description of the provider
Tag Editing Role (s)Users must belong to one of these roles in order to edit this provider's tags in the Designer. Multiple roles can be specified by separating them with commas. If blank, tag editing for this provider will not be restricted in the Designer.
GatewayThe name of the Gateway on the Gateway Network that this provider is coming from.
ProviderThe name of the provider as it is on the remote Gateway. This does not have to be the same as its name on the new Gateway.
History Access ModeThis setting dictates how tag history is queried for remote tags. Gateway Network will go through the Gateway Network to query history. Database will query the database directly.
History DatasourceThe datasource to query when History Access Mode is set to Database.
History Driver

If querying the database directly, this is the gateway name of the remote system. It is used to identify data from that system in the database.

History ProviderIf querying the database directly, this is the name of the tag provider on the remote system. It is used along with driver name to identify the correct tags in the database.
Alarms EnabledIf true, alarms configured on the remote gateway will be enabled on the new Gateway.
Alarm ModeHow alarm state should be monitored. In 'queried', state will be queried through the gateway network when necessary. In 'subscribed', the state will be subscribed, and updates will be sent asynchronously. Subscribed provides better performance, but uses more memory.

 


 

  • No labels