Login / Signup

Automatic acknowledge of NOACKOFF alarms

 
Alarm Data mgt
Last Post by n.kunzer 8 years ago
6 Posts
3 Users
0 Likes
31 Views
RSS
f.cubattoli
 f.cubattoli
(@f-cubattoliarcinfo-com)
Posts: 167
Reputable Member
Topic starter
 

Hello!!

A good question from one Italian customer in the Wind power market.

In case an alarm disappear without acknowledge (NOACKOFF) customer wants this alarm be automatically acknowledged by the system.

As far as I know the options in PcVue are:

  1. Alarm message type on Variable Setting : No acknowledge at all for that tag
  2. Alarm acknowledge on both ON and OFF status : In Project general properties

Maybe I miss a magic checkbox somewhere to say "Don't require acknowledge when an alarm is NOACKOFF"? :unsure:

I proposed a workaround based on events (one event for each alarm tag), but the customer refused due of the configuration workload (it's an old fashion project with 150k tags developed with Excel&AE).

Any other idea or we really don't have this possibility embedded?

Thanks a lot!!

 
Posted : 01/02/2018 4:35 pm
 r.buisson@arcinfo.com
(@r.buisson@arcinfo.com)
Posts: 0
New Member Guest
 

Hi Filippo,

Have a look on this article KB785

 
Posted : 01/02/2018 4:40 pm
f.cubattoli
 f.cubattoli
(@f-cubattoliarcinfo-com)
Posts: 167
Reputable Member
Topic starter
 

Thanks a lot Romain !!!!

 
Posted : 01/02/2018 5:02 pm
f.cubattoli
 f.cubattoli
(@f-cubattoliarcinfo-com)
Posts: 167
Reputable Member
Topic starter
 

Hellooo,

just a note, apparently there's a little error in the KB article (tested with v11.2.6058.21818)

Meaning of values 4 and 2 is just reversed:

- with 2 : auto acknowledge for NOACKOFF
- with 4 : auto acknowledge for NOACKON

Maybe someone can make a double check and then update the KB article?

Thankyou!!

 
Posted : 01/02/2018 11:05 pm
f.cubattoli
 f.cubattoli
(@f-cubattoliarcinfo-com)
Posts: 167
Reputable Member
Topic starter
 

Hello all,

#neverendingstory

Regarding the manual editing of PARAM.DAT in order to auto acknowledge NOACKOFF alarms (see KB785), it seems that this causes bad behaviours when there're thousand of alarms to be acknowledged in a short time (typically at station startup).

I remember something similar happens with the 

ALARM("ACKALL");

function in case of thousand alarms active to be acknowledged shortly, but I don't remember if never already solved and in which way.

Can be linked to Flow regulation?
Customer told me that many alarms are not automatically acknowledged neither on the producer station.

Thanks a lot for any light.

 
Posted : 27/02/2018 7:14 pm
n.kunzer
 n.kunzer
(@n-kunzerarcinfo-com)
Posts: 1236
Member Moderator
 

Hi Filipo,
No experience on that.
I think you should try reproducing on a platform.

Nico

 
Posted : 28/02/2018 11:59 am
Forum Jump:
  Previous Topic
Next Topic