Search

User Manual

GETTING STARTED


MODULES AND PLATFORM


APPENDIX


TUTORIALS & HELPFUL TRICKS


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 USER MANUAL VERSIONS

Ignition 8.1
Ignition 7.9
Ignition 7.8

Deprecated Pages

Employees

Sign In

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

 

Tag Providers and Drivers

At the highest level of 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 Ignition can also see the tags on another Gateway, as long as the two Gateways are linked.

All Tags reside in a Tag provider and provide 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 Providers

The Tags "tag database", or how Tag's tag configuration is stored, can take a few different forms. For internal Tags, the configuration is stored in the Ignition Gateway. With the database form, Tags are stored in a SQL database, outside of the Ignition Gateway. Finally, Remote Tag Providers allow Tag Providers of one Gateway to be accessed on a different Gateway. The different storage mechanisms have different pro and cons, and so it is a good idea to acquaint yourself with each of them.

On this page ...

Internal Tag Provider

The Internal Tags Provider manages the Tags inside the Ignition Gateway. This is the most common method and is optimized for the best scaling and performance. It is possible to create multiple internal providers per Gateway. The Tags can be exposed to other Gateways on the network through the Gateway's OPC-UA settings.

Remote Tag Provider

The Remote Tag Provider works by creating a link from the current Gateway to a Tag provider on another Gateway in the Gateway Network. The two Gateways must be linked through the Gateway Network. However, unlike an OPC connection which pulls Tags from the OPC server, a remote provider will keep all of the Tag's settings intact. So, things like alarms and history will still be present and can be used in the Gateway. By default, the remote Tag provider will fall under the Default Security Zone and be read only.

 

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. Normally requests are sent through the gateway network, but if access to the historian database is available, you can choose to query that directly.
History DatasourceThis setting dictates how tag history is queried for remote tags. Normally requests are sent through the gateway network, but if access to the historian database is available, you can choose to query that directly.
History DriverThis setting dictates how tag history is queried for remote tags. Normally requests are sent through the gateway network, but if access to the historian database is available, you can choose to query that directly.
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 ModeIf 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.

 


 

  • No labels