If the name of the database connection on the central gateway is identical to the history provider that is defined for the remote tags, Seeq will automatically find the correct connection to use for historical data queries. Otherwise, errors will appear in Seeq Workbench when you attempt to access that tag data. If you are utilizing the Gateway Network features of the Ignition system and have the Seeq Ignition Module installed on a "central" gateway that accesses tags on a remote gateway via the Remote Tag Provider feature, Seeq can access data from such tags if the central gateway has a database connection to the historical data. Remote Tag Providers and Tag History Splitters are supported in Seeq Ignition Module R19.0.36.02 and later. In the Tag Providers section, add a comma-delimited list of all tag providers you want Seeq to index. In the Ignition Gateway configuration site, browse to the SEEQ section at the bottom of the configuration section list on the left hand side. To filter the set of providers, take the following steps:
You may wish to filter down to a particular set of providers, perhaps because you don't need to see all the providers in Seeq or because some of the providers are unavailable. If more than one tag provider is indexed, then the asset tree in Seeq Workbench will include the tag providers near the top. Filtering Tag Providersīy default, Seeq will index all tag providers that are defined on the gateway. Jump to the Browsing Ignition Tags from Seeq Workbench section below. Indexing all the tags may take some time. Refresh your Seeq Workbench screen and you should see your Ignition tags in the Data tab. Copy it to your clipboard and then paste it into the Agent Key section of the SEEQ → Settings section on the Ignition Gateway. In Seeq Workbench, go to the Administration page (from the upper-right "hamburger" menu) and you'll see a Seeq Agent Key in the upper right. Copy the seeq-cert.pem file in that folder to the identical location on the Ignition Gateway machine. The certificates are stored on the Seeq Server in the Seeq data folder under the keys subfolder. If you're connecting to a Seeq Server which is running with a self-signed certificate, you need to copy the Seeq Server's certificate to the Ignition Gateway machine by hand.
#Inductive automation ignition tags windows
(Instructions for Windows Firewall configuration here.) In the Seeq Server Hostname textbox, enter the hostname or IP address of the Seeq SaaS service or the Seeq Server machine you commissioned.Įnsure that the port number specified in Seeq Server Port is not blocked by a firewall on the Seeq Server machine. modl file you downloaded in Step 1.Ĭlick Install and allow the module to load.Īfter installing the module, you may need to log out and log back in to the Ignition configuration site so that the SEEQ settings area appears in the bottom left of the page.
#Inductive automation ignition tags install
Scroll to the bottom of the page and click the Install or Upgrade a module link.Ĭlick Choose File and browse to the. In a web browser, open the Ignition Gateway configuration site and log in with administrator credentials.
You will have to use Windows Explorer to change the extension to. Some browsers like Internet Explorer 11 may rename the module file such that it has a. 12 Upgrading Seeq and the Ignition Module.11 Embedding a Seeq Visualization in an Ignition Vision Window or Template.10 Adding a "Show in Seeq" Button to an Ignition Vision Window or Template.9 Browsing Ignition tags from Seeq Workbench.8.7.2 Default Transaction Isolation Level.8.3 Unable to Connect to Server When Seeq Is Using a Self-Signed Certificate.8.2 Unable to Connect to Server because of Corporate Firewall SSL Certificate Replacement.4 Remote Tag Providers and Tag History Splitters.
0 kommentar(er)
