You can help by commenting or suggesting your edit directly into the transcript. We'll review any changes before posting them. All comments are completely anonymous. For any comments that need a reply, consider emailing docs@inductiveautomation.com.
Version:
Supplemental Videos
-
2:31Edge Architecture
-
3:31Edge Overview
-
4:15Local Client Fallback
-
4:39Setting up Edge Sync Services
LESSON
Edge Architecture
Description
Ignition Edge can be used to expand existing architectures to reach even the most remote edge of network areas.
Video recorded using: Ignition 8.1
Transcript
(open in window)[00:00] In this lesson, we'll take a look at some architecture diagrams that demonstrate some of the options that can be achieved with Ignition Edge. Edge is a more lightweight version of the Standard Ignition installation and is perfect for filling in on edge of the network solutions. While Edge can be deployed in standalone solutions, it can also be paired with a standard Ignition gateway to take advantage of its full functionality. The main functionality of Edge is achieved through the different products that are made available through the two product offerings Panel and IIoT. Let's take a look at Panel first. Panel enables standalone HMI functionality for one local client and one remote client at the edge of the network. Panel allows you to choose between the Vision or Perspective visualization modules. Setup can be as simple as connecting to a local PLC and building a basic screen. When paired with a central Ignition gateway, Edge can also act as a local client fallback. This way if network connection to the central site is lost, control will be retained at the Edge site. On top of visualization, Panel also includes all of the features that are included with the other offering, IIoT. The IIoT product allows Edge to push MQTT data from the edge of the network directly to an MQTT broker. IIoT also allows OPC UA clients to connect to the OPC UA server on Edge.
[01:18] This means that a standalone Edge gateway can be connected to multiple types of devices and act as a remote MQTT publisher and it also allows connection to a greater IIoT architecture that can synchronize with a central Ignition installation as well. Coupling IIoT and Panel together allows the ability to publish data to an MQTT broker, while also providing a local client at the edge of the network. Ignition Edge doesn't allow for database connections, but with Sync Services, which is included with IIoT, it does have internal storage that provides a one week buffer for the alarm journal and audit logs, as well as up to 35 days of tag history data to be retained locally. This data can then be forwarded and synchronized with a central gateway or can then send the edge of the network data to your central database.
[02:02] Finally, EAM also provided by IIoT, allows for an edge gateway to act as an agent in an EAM architecture. EAM enables the ability to bring diagnostics, automatic backup and recovery, central licensing, and project and tag synchronization to your edge of network device. These functionalities are what make Edge a flexible addition that can fill multiple roles at your edge of the network and help bridge the gap between different architectures.