krakenfan69
Lifetime Supporting Member
Hi guys.
I have a system we work on. It's a SLC 5/05 at a battery connected through CH0 to a serial radio to a L61 Control Logix processor at a satellite. The alarms at the Sat are all dropped into an array that was designed to mimic data table addresses from whenever it was upgraded. So they all land in an N40 Array. Those 100 words are read back to the plant into an N47 data table in the SLC that FTView 11 is using for alarming. (Alarm & Events Server) Every few months, every alarm form this site rings in. All of them at the same time. H2S fault and the 4 hour SD for the same bit ring at the same time. Analog values go wild too. When operations logs in the Sat is running fine. A quick ack/reset clears the alarms. I can't find anything writing to those registers at the plant so I am wondering if the message instruction itself may be the culprit. It gets something crossed and reports the entire array as a Zero value which triggers the alarms and callouts. The next read seems to pull valid data as they can always reset right away. Anyone seen anything like this before?
Thanks,
****** Fan #69
I have a system we work on. It's a SLC 5/05 at a battery connected through CH0 to a serial radio to a L61 Control Logix processor at a satellite. The alarms at the Sat are all dropped into an array that was designed to mimic data table addresses from whenever it was upgraded. So they all land in an N40 Array. Those 100 words are read back to the plant into an N47 data table in the SLC that FTView 11 is using for alarming. (Alarm & Events Server) Every few months, every alarm form this site rings in. All of them at the same time. H2S fault and the 4 hour SD for the same bit ring at the same time. Analog values go wild too. When operations logs in the Sat is running fine. A quick ack/reset clears the alarms. I can't find anything writing to those registers at the plant so I am wondering if the message instruction itself may be the culprit. It gets something crossed and reports the entire array as a Zero value which triggers the alarms and callouts. The next read seems to pull valid data as they can always reset right away. Anyone seen anything like this before?
Thanks,
****** Fan #69