Results 1 to 12 of 12
Thread: Niagara LON 'ping fail' alarms
01-10-2013, 10:28 AM #1
Niagara LON 'ping fail' alarms
Some of my sites generate ping fail alarms on the LON networks. In most cases the ping returns to normal within a second or two.
Is there a way to delay the ping response time of to make the system generate the alarm after maybe 2 or 3 ping failures?"Controls is a lifestyle not a job" -klrogers
01-10-2013, 12:49 PM #2
I don't know of anyway to do that, but you could increase the ping frequency up from the default of 5 minutes.Go Rangers!
01-10-2013, 06:31 PM #3
Look at the poll scheduler statistics, what's the dibs bucket doing?
01-10-2013, 06:50 PM #4Regular Guest
- Join Date
- Nov 2012
- Sydney, Australia
Have you got your EOL terminations done?
01-10-2013, 07:10 PM #5
Assuming the LON Utilities Manager yields no errors.... and No one needs to know immediately on ?.... why not just change the alarm class?
From there you could do something with an active alarm count or something along those lines to indicate a comm failure to the default/whatever alarm class. Including a delay.
01-10-2013, 07:17 PM #6
01-10-2013, 07:20 PM #7
01-10-2013, 10:47 PM #8
01-11-2013, 06:51 AM #9
Thanks for the replies guys. EOLs are all installed, Dibs are at 0%, points are polled. Will try some of the other suggestions and see if something works. Chris, most devices are not critical but a ping failure is the only way to tell if a unit goes down from a tripped breaker or blown fuse etc. All controllers use the unit 24v for power."Controls is a lifestyle not a job" -klrogers
01-11-2013, 10:05 AM #10
Once you change the Alarm classes and by adding status demux to each critical device, from there you can do many things with the Boolean outputs to COV a alarm.
01-15-2013, 03:11 PM #11
01-16-2013, 02:08 PM #12
Thanks Matrix, I have since bound all the points."Controls is a lifestyle not a job" -klrogers