How can I set up my Edge tags to work with my central server alarm pipeline?

[alexmohney]

Hi, I am setting up an alarm notification system that uses a set of Ignition Edge devices that collect tags from a controller and sends them to a central server for storage and visualization. I have the alarm notification module and wish to set up my Edge tags to use the alarm notification pipeline that I create within my central server. I don't see a way to link together my edge tags and the pipeline, do I have to mirror the tags within the central server designer or is there another way to accomplish this that I am missing?

[pturmel]

@alexmohney

mirror the tags within the central server designer

This, as reference tags. Tags can only send alarms to pipelines in the same system.

[Chris_Bingham]

What versions of Ignition are you using (both Edge & Full / Central)?

On 8.1 within Edge Gateway Config webpage (Config > Alarming > Remote Notification), you'll need to enable remote alarm notification & select the remote gateway where you'd like to send the alarm event to. Following, you should be able to select the desired remote pipeline directly from an Edge tag's alarm configuration.

Setting up the outgoing connections on my Edge gateway to my central gateway

You should only need to establish the connection once. After that, communication is bidirectional. I speculate that your fault is related to creating an outbound connection when you already have an inbound connection established with same gateway, but -disclaimer- I have never tried this myself. I recommend that you always create an outbound connection from the Edge --> Full gateway, and have only inbound connections (from Edge gateways) at your central gateway. Regarding setting up the remote…

[alexmohney]

I am using version 8.3.4 on both Edge and Full. I'll mess around with the remote alarm notifications and see if that can help accomplish this. Thanks.

[Chris_Bingham]

In 8.3, the process is obscured a bit...in that Alarm Pipelines are now exposed by creating a Remote Notification Profile on the Edge gateway, pointing to the Full gateway (even if the profile does not exist on the Full gateway). The pipeline configuration settings on the gateway have changed from 8.1 to 8.3, but the designer configuration remains the same.

From my experience (Full & Edge gateways @ 8.3.7):

• On Full Gateway:
  • Web Config > Services > Alarming > Pipelines: Create an Alarm Pipeline
  • Note: Creation of a Notification Profile is NOT necessary.
• On Edge gateway:
  • Web Config > Services > Alarming > Notification > EdgeRemoteNotification: Edit the existing profile to point to Gateway = <FullGateway>. For the required "Notification Profile" field, enter "N/A" (or any other text indicating that the profile need-not exist). Enable the profile, Save.

After creating a remote notification profile, all of the Full gateway pipelines are exposed to the Edge gateway. In the Edge designer (or Full designer @ remote tag provider), you will be able to select the Full GW's pipelines when you configure an alarm on the Edge tag.

In either 8.1 or 8.3, there might be additional Service Security settings which block the alarm pipelines from being exposed.

[alexmohney]

Thanks Chris! Very odd that this is how it works but you are correct, now it seems as though I can set my alarm pipeline into my edge tag alarms.