Remote Alarming allows a Gateway to access the notification profile of another Gateway on the Gateway Network. This allows any Gateway in the network to use the SMS or Voice Notification capabilities of other Gateways. This also allows access to the Alarm Notification Pipelines of other Gateways that they share a Notification Profile with. All of this means the majority of Alarm Notifications can happen at one central location in the network.

Video recorded using: Ignition 8.1


(open in window)

[00:00] In this lesson, we'll look at remote alarming. Remote alarming allows one gateway to utilize the alarm notification capabilities of another gateway via the gateway network. I've already done some setup on my end to prepare for this, but in order to get this to work on your end, you'll need to meet the following prerequisites. You'll need two Ignition gateways, those gateways need to be connected via the gateway network, and each gateway will need to have the alarm notification module installed. My remote gateway also has other modules installed that my local gateway does not, but we'll see that in a moment. I want my local gateway to be able to utilize the other gateways alarming capabilities. To get started, I'll navigate to my local gateway's config page, scroll down to alarming, and then click notification. Next, I'll click Create New Alarm Notification Profile. The next page will show the available notification profile options I have on this gateway. This gateway is only able to create email notifications as I don't have the SMS or voice notification modules installed.

[01:03] However, if I choose a remote notification profile, I can choose the remote gateway that's connected to this local gateway via the Gateway Network, and then I have access to any of the notification profiles that have been configured on that remote gateway. My remote gateway has the SMS and Voice notification modules installed and already has a profile created for email SMS and Voice. So each of those profiles are available to me here on my local gateway. I'll select the SMS notification profile and click next. This next page contains the settings for this remote profile. It pre-populates a name based on the connected gateway and the notification profile that was selected, which can be seen and changed in the remote gateway section. There are also some advanced properties for the delay between retries of a failed synchronization and for the size of the queued alarm transitions. I'm gonna leave these alone and create the profile, and then I'll see a running remote notification profile that gives me SMS notification capabilities on this gateway thanks to remote profiles.

[02:02] Now that the profile is set up, I'll switch to the designer for my local gateway to show how to utilize this profile. First, I'll navigate to the alarm notification pipelines where I have an existing pipeline with a notification block. I can click the notification dropdown and choose the remote profile that I just created to use SMS notification in this pipeline. Furthermore, if I open up an alarm on one of my tags, I can choose one of the notification pipeline dropdowns and select any of the pipelines I have configured on this gateway, as well as any that are configured on the remote gateway. These features allow you to set up any hardware or software that you need on a central gateway, and then utilize those resources on any remote gateways via the Gateway Network.

You are editing this transcript.

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