Edge Computing, Data Collection, and HMI Software for the Network’s Edge
Extend Your Network, Not Your Budget
Capturing, processing, and visualizing critical data at the remote edge of the network can be difficult and expensive. Ignition Edge by Inductive Automation® is a line of limited, lightweight Ignition software solutions designed specifically for devices used in the field and OEM devices at the edge of the network. With Ignition Edge, edge computing is easier and more affordable than ever, so you can extend your data collection, visualization, and system management all the way to the edge of your network.Ignition Edge Product Sheet
Ignition Edge Products:
Each Edge product includes Ignition Edge Core and limited versions of some Ignition modules, bundled together to perform a specific function. Products can be mixed and matched on an edge device to create powerful solutions at the edge of the network.
Publish field-device data through MQTT
Create local HMIs for field devices
Add true edge computing to your network
Synchronize data from the edge of the network
Combine with other Edge products for central management
“Having the power of Ignition extend down to edge devices in the field offers a disruptive approach to how industrial network infrastructures are designed, deployed, and managed.”
– Arlen Nipper
Co-Inventor of MQTT
Ignition Edge Core
The Solid Foundation of Ignition Edge Solutions
All Ignition Edge solutions are built on Ignition Edge Core, which includes powerful features ideal for edge computing.
Works on Any Device
Ignition Edge solutions work on a wide variety of operating systems such as Linux, Windows (any version), macOS, and more. Ignition Edge comes pre-installed on a range of edge-of-network devices that are IIoT-ready right out of the box, and Ignition Edge can also be installed on virtually any industrial device. With support for ARM processors, Ignition Edge can run on devices like a Raspberry Pi or the latest generation of edge-of-network devices.Explore devices with Edge pre-installed
Runs on Linux, Windows (any version), macOS, and supports ARM processors to run on devices like Raspberry Pi.
OPC UA Connectivity
For easy PLC connections, all Ignition Edge solutions come with unlimited tags and are equipped with native drivers. Ignition Edge acts as an OPC UA server when used with the included Ignition native drivers and can connect to an OPC UA server as an OPC UA client. External access (from a third party) to Ignition Edge’s OPC UA server requires Edge IIoT.
Included Ignition Native Drivers
- UDP and TCP Drivers
- BACnet Driver
- Allen-Bradley Driver Suite
- Siemens Driver
- Modbus Driver
- DNP3 Driver
- Omron Driver
- Opto 22 SNAP PAC Driver
(with Edge IIoT only)
- ABB Totalflow Driver
(with Edge IIoT only)
- Emerson ROC Driver
(with Edge IIoT only)
Poll Data at the Source
Ignition Edge makes edge computing easy. Install Edge right onto, or next to, devices on the plant floor or in the field so you can process data as close to the source as possible. This allows you to make device data the one source of truth, improving data reliability and reducing latency.
Works Seamlessly with Ignition
Ignition Edge is designed to be installed on devices at the edge of the network. The Ignition platform is designed to work on central servers and to be deployed to multiple clients. Using Ignition and Ignition Edge together, you can build scalable and affordable enterprise-wide systems.
Limitations of Ignition Edge Core
Two Device and External OPC UA Connections
Edge Core has a limit of two native driver device connections and two external OPC UA connections. (Additional connections are available for purchase.)
Modules Licensed for Standard Ignition Won’t Run on Edge
Edge products and additional Edge modules must be licensed for Ignition Edge in order to function.
Gateway Network Limitations
Services available over the Gateway Network vary by each Edge product or module. No services are available in Edge Panel.
Gateway level scripting is disabled (unless using Edge Compute).
No Database Connectivity
External database access is not available.
Only allows for one Ignition Project.
One-week Data Buffer
Data storage for up to one week.
One Tag Provider
Only allows for one tag provider.
OPC UA Client Restrictions
By default, third-party OPC UA clients are restricted without the use of Edge IIoT.
Ignition Edge Products
Mix and Match to Create Powerful Solutions
There are multiple Ignition Edge products for edge computing needs such as HMIs, MQTT data transmission, and easy extension of large-scale enterprise architectures. Ignition Edge products are made up of a collection of limited versions of some Ignition modules, bundled together to perform a specific function. Each product can be used as a single solution or can be installed in combination with other Edge products and modules on a single device.
Ignition Edge Products
Ignition Edge IIoT
Turn any device into an edge gateway that publishes data to an MQTT broker.Learn more about Edge IIoT
Ignition Edge Panel
Implement a standalone browser-based or dedicated application HMI at the edge of the network.Learn more about Edge Panel
Ignition Edge Compute
Remotely run scripts and create REST APIs for interfacing with third-party applications.Learn more about Edge Compute
Ignition Edge Sync Services
Synchronize data from the edge of the network to a central Ignition server.Learn more about Edge Sync Services
Additional Modules Available for Ignition Edge
In addition to the Edge products, there are also some additional modules that work on Ignition Edge. (All modules below require an Ignition Edge License to function and are subject to all the limitations of Ignition Edge Core.)
Inductive Automation Modules Made for Ignition Edge
OPC COM DA Module for Ignition Edge
Connect to classic OPC servers using COM or DCOM.
Cirrus Link Modules Made for Ignition Edge
Cirrus Link MQTT Engine Module for Ignition Edge
Bidirectionally communicate with edge devices via an MQTT server.
Cirrus Link AWS Engine for SiteWise Module for Ignition Edge
Interface with AWS IoT SiteWise service to automatically discover assets and create tags.
Cirrus Link MQTT Distributor Module for Ignition Edge
An MQTT server to connect, publish, and subscribe to device data.
Cirrus Link AWS Injector Module for Ignition Edge
Send Ignition tag data into the Amazon Web Services (AWS) cloud.
Cirrus Link Azure Injector Module for Ignition Edge
Send Ignition tag data into the Azure IoT Hub.
Cirrus Link IBM Cloud Injector Module for Ignition Edge
Send Ignition tag data into IBM Cloud.
Cirrus Link Google Cloud Platform Injector Module for Ignition Edge
Send Ignition tag data into the Google Cloud Platform.
Ignition Edge Onboard
Ignition Edge is powerful, MQTT-enabled, and designed specifically for use in industrial devices. That’s why a growing number of OEMs are pre-installing and pre-licensing Ignition Edge on their products as part of the Ignition Onboard program.Browse devices with Ignition Edge Onboard
Do Even More with Ignition Edge
Perfect for OEMs
Engineered and priced ideally for embedded applications
Edge is simple to implement: just install it and go.
Optimized for Embedded Devices
Edge is optimized for peak performance on constrained, embedded devices.
Full Integration with the Ignition EAM
Adds powerful functions when combined with the Ignition Enterprise Administration Module.
Built on Trusted IT Standards
MQTT, OPC UA, and Python.
Works on Windows, Linux, macOS, and more.
Exponentially improve your data collection with unlimited tags.
What are the use cases for Ignition Edge?
Ignition Edge has two primary use cases: local I/O with store-and-forward to a central
system, and local HMI or fallback client for visibility and control of data.
- Local I/O with Store-and-Forward: Easily deploy Ignition Edge IIoT or Sync Services to provide local I/O with store-and-forward to a central Ignition system.
- Local HMI or Fallback Client: Easily deploy Ignition Edge Panel to provide on-site local visibility and control of your data.
When do I use Ignition Edge versus a standard Ignition server?
Ignition Edge is perfect for distributing out I/O, providing local visibility of data, efficiently collecting data from remote sites over slow connections, and for robust fiber networks to offer more scalability, access to data, and distribution of I/O. It is limited and designed to work in tandem with a central Ignition system. Ignition Edge is not suitable to run an entire facility or site as a SCADA system, nor is it designed to act as an unlimited I/O server for all of your PLCs. If you need local functionality and have a use case that requires features beyond Ignition Edge, a standard Ignition server is recommended.
Can I mix and match Ignition Edge products?
Yes. With multiple Ignition Edge products to choose from, you can use any one of them or mix and match them to create a more robust solution on a single device.
Is Ignition Edge meant to be used as a standalone solution?
No. Ignition Edge is designed to work seamlessly with a central Ignition server for optimal performance, and to synchronize data to a centralized system and provide critical functionality.
How does Ignition Edge communicate to a central Ignition server?
Ignition Edge can communicate with a central Ignition server in two ways: through the
Gateway Network and MQTT. You can configure both connection methods at the same time.
For more information about how to configure the Gateway Network and the MQTT protocol, please visit the user manual: https://docs.inductiveautomation.com/
Is Ignition Edge a good option for data collection in my industry?
It depends on your needs. For many industries such as manufacturing, oil & gas, automotive, and food & beverage, Edge can be a great option for local data collection. In industries with large numbers of simple devices, Ignition Edge typically isn’t a good fit. Examples of these are applications like inverter connections in the solar industry, certain municipality connections, power distribution, building automation, or other industries where connections to hundreds of simple devices are standard. For these industries, a full version of Ignition is a better alternative to Edge.
Does Ignition Edge support OPC UA?
Yes. Ignition Edge supports OPC UA as a server and client. Ignition Edge can communicate to any external OPC UA (or OPC COM) server to bring in data. Ignition Edge can also expose data through OPC UA locally. However, Ignition Edge is not designed to be a full-blown OPC UA server.
Does Ignition Edge support scripting?
Yes, but only with specific Edge products. Ignition Edge Compute is the product that provides scripting in general and can be added to any solution. Ignition Edge Panel by itself does support on-screen scripting, but Edge Compute is often paired with Panel as well as for more advanced Edge Gateway scripting for things like an automatic reaction to tag changes or periodic tasks. Specifically, Edge Compute enables Gateway scripting, including tag change scripts, timer, startup and shutdown scripts, Gateway Network message handling, etc.
Where can I deploy Ignition Edge to?
Here are some of the many devices, services, and systems on which you can deploy Ignition
- Devices: Embedded PCs, laptops, desktops, high-grade servers, fog computing
- Managed Services: AWS EC2, AWS ECS, AWS Outposts, Azure Virtual Machines, Azure Containers, Google Compute Engine
- Virtual Machines & Containers: VMware, Parallels, VirtualBox, Hyper-V, Docker
Does Ignition Edge support ARM?
Yes. With support for ARM processors (32-bit HF and 64-bit), Ignition Edge can run on devices like Raspberry Pi or the latest generation of edge devices.
Can Ignition Edge work with SQL databases?
No, Ignition Edge cannot communicate to external SQL databases. It is designed to synchronize data to a central Ignition server that is communicating with a SQL database. Ignition Edge has everything built-in to store and forward data to a central Ignition server with ease.
Can I deploy Ignition through Docker or orchestration platforms?
Yes. Inductive Automation has an official Docker hub image that allows you to quickly
deploy Ignition or Ignition Edge on any device. You can also use orchestration platforms
such as Zededa, Balena, Azure Stack Edge, edgeIQ, and more.
For more information on Ignition’s official Docker hub image: https://hub.docker.com/r/inductiveautomation/ignition
Is it possible to upgrade Ignition Edge to a standard Ignition server?
Yes, it is possible. Ignition and Ignition Edge share the same basic technology.
To learn more about how you can upgrade, please contact our sales representatives at 1-800-266-7798.
Where can I purchase Ignition Edge?
You can purchase Edge directly through Inductive Automation or from an Ignition Onboard
partner. When purchasing from Inductive Automation, you will be responsible for installing
Ignition. When purchasing from an Onboard partner, Ignition Edge will come preinstalled on
your device for faster development.
For more details on the Ignition Onboard program, go to: https://inductiveautomation.com/onboard/about