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.
LESSON
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.3
[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. I have two gateways connected over the network. Those are my local gateway ignition A and my remote gateway ignition B. Both of the gateways have the alarm notification module installed, but 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 remote gateway's alarming capabilities. To get started, we'll navigate to my local gateway's services tab and click the notification page under the alarming section. Next, we'll create an alarm notification profile by clicking the create profile button, alarm notification profiles are tools that know how to connect and send a message via email, SMS or voice, depending on which modules you have installed.
[01:06] This local gateway is only able to create email notifications as I don't have the SMS or voice notification modules. However, we can choose a remote notification profile to access any of the notification profiles that have been configured on ignition B. We'll go ahead and click on next, and on this page, we need to fill out some information. Let's go ahead and give this a name. I'll go ahead and name it ignition B remote SMS. We then need to select both the gateway and the notification profile we want to use. I only have one connected gateway, so I'll choose ignition B. Ignition B does have the voice and SMS modules installed, and I've already created both kinds of notification profiles on ignition B, so if I wanted to use either one of them, I would simply pass the name of the profile into this notification profile 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.
[02:08] I'm going to 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. Now that the profile is set up, I'll switch to the designer for my local gateway to show how to utilize the profile. Here in the designer, we are looking at my notification pipeline. With this notification block, I can use 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 others that are configured on remote gateways.