800xA alarm event list configuration problem
I am working on 800xA system, and I have a problem to show alarm and event in object faceplate's alarm list/event list.
For example, I am closing the air line and sending open signal to the valve. Of course, it is not oppening and blinking red on the operator workplace, but I can't see any alarm on the list when I click on the Alarm List button to acknowledge the alarm. So, I can't control the valve until remove the alarm from code block.
I used AlarmCond function to create alarm in function blocks for the objects. As I've read on the document it should show on the alarm list. What am I missing? What should I do? What can be the problem?
If someone could help, I would be appriciate.
Voted best answer
You can check 2 major settings in 800xA.
1. I hope you have configured controller IP address in the OPC Configuration panel under OPC AE tab. You should see Smily icon once the OPC AE connection is healthy.
2. And then check in Engineering Workplace > Service Structure > Event Collector Service >FInd the Service group for OPC AE and check in Specical configuration "Collection Definition" configured properly.
For example if you are using AC800M controller you should select "OPC AE Server for AC800M"
I hope this will help you.
1) OPC AE configuration is required in the system. Read in the user's guides what to do (connect AC 800M processor over AE protocol on the second tab of AC 800 OPC Server panel, verify "smiley faces", create & configure Event Collector service group in 800xA system, etc).
2) Study the Alarm Owner concept of AC 800M, e.g. in the OnLine Help of CBM. The alarm must be owned by the object having the faceplate, not its parent nor the application.
3) Alarm lists can be filtered incorrectly. Verify that the "Process Condition Event" category is included in your list's filter, or use the Common Alarm List filter shipped with the system (which from factory, *but not always later* on have all categories enabled)
4) When in On-Line with the application from Control Builder M, use the Alarm Conditions context menu of the suspect object. If your AlarmCond block is reporting state 0 something is wrong (illegal parameter, bad name, too long name, name not unique) or the alarm is simply not enabled.
There are plenty of threads on AKS visualizing what you need to check. Please Google for keywords and see what has already been mentioned on this topic.