Edge Architecture


Ignition Edge can be used to expand existing architectures to reach even the most remote edge of network areas.

Video recorded using: Ignition 7.9


(open in window)

[00:00] In this video, we're going to take a look at the three Ignition Edge plugins and the different architectures they offer. Understanding what each plugin does is crucial to figuring out which plugins you'll need to add to your Edge gateway. While each Edge plugin offers a wide range of functionality, you may notice that in each of these slides the Edge gateway is best paired with a central Ignition gateway, allowing you to take full advantage of the functionality that Edge has to offer. First we have our panel plugin. The panel plugin allows you to create a local HMI for your field devices. It allows you to launch one local client as well as one remote client. The panel plugin also offers one week of local internal storage, perfect for trending your tags or for setting up local client fallback, if you ever lost connection to the main central gateway. Finally, the panel plugin also offers a one way email notification for your alarms. Next we have the Enterprise plugin. The Enterprise plugin provides access to the gateway network. Allowing you to make the Edge gateway a target for Ignition's distributed services as well as allowing EAM functionality, turning the Edge gateway into an agent in your EAM system. With the Enterprise plugin, other Ignition gateways can use the distributed services to query tag values, tag history, and even alarms from your Edge gateway. Turning the Edge gateway into an EAM agent allows you to do things like monitor and manage your edge system, from a central Ignition server. The Enterprise plugin also offers one week of internal storage, allowing you to store tag history for up to a week without any database. Finally, the Enterprise plugin introduces something new, called tag history synchronization. What this does is pushes the tag history saved in your Edge gateway, to a history provider on a central Ignition system. That central Ignition gateway, will then store that tag history data into its connected database. Allowing you to store more than the limited one weeks worth of data. If the connection to the central Ignition gateway ever goes down, that one week of data storage internal to the Edge gateway, will then act like a store and forward system. Storing up to one weeks worth of data, and then pushing it back to the central Ignition system when the connection is restored. Last but not least is the MQTT plugin. The MQTT plugin essentially turns your Edge gateway into a remote MQTT publisher. Allowing you to push data directly into an MQTT broker, using the fast and lightweight data transfer protocol. The MQTT plugin operates in exactly the same way that the MQTT modules work on a standard Ignition system. Allowing you to easily and quickly get started.

You are editing this transcript.

Make any corrections to improve this transcript. We'll review any changes before posting them.