Ignition 8
Ignition 7.9
Ignition 7.8
Sepasoft - MES Modules
Cirrus Link - MQTT Modules
Inductive University
Ignition Demo Project
Knowledge Base Articles
Forum
IA Support
Deprecated Pages
SDK Documentation
FactoryPMI Reporting Manual
FactorySQL
Ignition 8.1. Offline Version (04/2021)
Edge can create OPC UA client connections. The internal OPC UA server in the Edge Gateway acts only as a client and not as a server. This means Edge can connect to other outside OPC servers as a client to fetch data, but can not act as an OPC UA server for outside programs to connect to. Adding the IIoT product extends this functionality.
By default, Edge Gateways can have two device connections. Once two devices have been configured, the “add device” UI on the Gateway’s Devices config page will be hidden. Speak to your sales representative for more details on increasing the device limit.
An Edge installation can store certain historical data inside Ignition.
Tag History -
Alarm Journal - The alarm journal will store all alarm events locally for one week of events. There are limited configuration options; the Alarm Journal can be accessed via the Edge Alarm Journal profile. The Edge alarm journal and audit log can sync under EAM.
Audit Logs - Like the Alarms, the Audit log is limited to one week of local storage. It cannot be configured.
Edge installations have just one project. This project is created automatically if it did not exist, and it cannot be removed. The default project name is "Edge" and can be renamed. For more information, see Edge Gateway Config section.
Two Edge Gateways can be set up with redundancy. An Edge Gateway can only failover to another Edge Gateway (not a standard Ignition Gateway).
Edge gateways can make use of a Simple One-Way Email Notification Profile, allowing the gateway to send out email notifications.
The Edge product line was reconfigured to combine the five previous Edge products into two updated Edge products. Users with an existing Ignition Edge license and Upgrade Protection may have upgrades available, contact your account representative for more information.
Pages detailing features of the previous Edge products can be found in Deprecated Ignition Features.
| Ignition Edge IIoT turns virtually any field device, such as a touch panel or a client terminal, into a lightweight, MQTT-enabled Edge Gateway that works seamlessly with Ignition IIoT and other common IIoT platforms, providing remote data acquisition and optional secured feedback and control. It’s ideal for polling data at the device location and publishing data to an MQTT server that business systems and applications can access. Ignition Edge IIoT includes unlimited tags and device connections for included drivers, the ability to run scripts, create REST APIs, synchronize data to a central server, and act as an EAM Agent Gateway. |
| Ignition Edge Panel includes everything in Ignition Edge IIoT plus local visualization functionality for your HMIs. Choose between Perspective (2 sessions) or Vision (1 local client, 1 remote client) as your visualization system for Edge Panel. Build future-proof, robust local control systems that are Industry 4.0-compatible. It’s ideal for standalone HMIs and providing a local-client fallback for field HMIs if the network connection is lost. Ignition Edge Panel includes unlimited tags and device connections for included drivers, the ability to publish MQTT data, run scripts, create REST APIs, synchronize data to a central server, and act as an EAM Agent Gateway. Additionally, both the Web Browser module and Symbol Factory image library are included in Edge Panel. |
All Edge installations are a limited version of the Ignition platform for a significantly reduced cost. This helps keep things simple, and these installations always work with other full versions of Ignition if you need additional functionality. In an Edge installation there are a lot of visual changes to the Gateway Webpage, and some pages have been removed to avoid confusion. You can see below that after installing Edge, the traditional orange Ignition logos are replaced with new green Edge logos so a Gateway can be easily identified. For more information, see Edge Gateway.
Because Edge is a lean solution, it does have some functionality limitations compared to full Ignition. Ignition and Ignition Edge share the same basic platform, but Edge is a leaner version of Ignition made specifically for use in on edge-of-network devices. Ignition comes with unlimited Tags, Clients, and database connections, while Ignition Edge comes with unlimited Tags, two Clients (one local and one remote) and no database connectivity.
Database access is disabled. This means that any database queries or bindings will not work, and the user sources that require a database connection will not be available. The Status and Configure pages of the Gateway Webpage have been updated to remove these features and reduce confusion. Despite this restriction, some historical storage can happen inside of Ignition.
All Gateway level scripting is disabled including Gateway Event Scripts and Tag Event Scripts. This does not affect project or Client-scoped scripts. If you wanted to take advantage of Gateway Events Scripts and Tag Events Scripts with an Edge installation, you can do so through the use of the Compute product. Keep in mind that you will not see the Gateway Events menu item in the Designer on unlicensed Gateways. Applying a compute license will require a Designer restart before the menu item will appear.
A Gateway backup made in an Edge installation will work in other Edge installations, or if needed, Standard Edition Gateways as well. Although restoring a Standard Edition Gateway backup is possible in an Edge installation, it is not recommended due to the limitations of the Edge platform. You can, however, still export tags, windows, and other project resources in the Designer from Standard Edition Gateways and import them into an Edge project, or vice versa.
Edge Gateways only contain a single active Realtime tag provider. Additional providers may not be created.
Edge Gateways contain a single historian provider, which is an instance of an internal historian provider (named the Edge Historian Provider)
Edge's core functionality and products largely determine which modules run on the platform. Third-party modules will not run on an Edge Gateway, with the exception of any third-party module explicitly stated by a product, such as the Edge IIoT Product.
