Working with third party simulation and alarm acknowledge not working
These problem we are facing is very specific to merging 800xA system with a third party simulation. We have something called IC(initial conditons file ) which when loaded into system will push values into third party system as well as 800xA system. So before we load these ICs into system everything seems to run fine, but after loading ICs alarm aknwoledge stops working , niether do we get new alarms. One more problem associated is that alarm acknowledgement problem is limited to PCDL library and some more objects. Need suggestions.
What does loading an IC file constitute to the system? Please explain in detail.
The alarm system must be handled properly - are you sure loading an IC follows what the PLC, OPC server and HMI was built and tested for?
Since you mention PCDL I assume you are using AC 800M controllers and AC 800 OPC Server.
- The controller is central in the alarm state handling
- The OPC Server, 800xA Event Collector and Alarm Manager services attempts to "slave" to the controller's alarm state machine.
- For acknowledgement to work, the following must take place:
a) The alarm must have the "AckRequired" bit set and be unacknowledged in 800xA
b) The OPC server must accept the acknowledge (800xA must pass exact matching parameters e.g. SrcName, EventTime, Condition, Cookie (a serial number))
c) The controller must accept the acknowledge when passed from the OPC server
d) The controller must issue a "Return To Normal", RTN event to the OPC server
e) When the RTN event is received by 800xA, the alarm will transit to RTN or idle (=clear from alarm list) if alarm state was inactive prior the acknowledge.
Some suggestions how to continue the troubleshooting:
- The alarm state in the controller can be viewed from the Alarm Conditions window in Control Builder M while being online with the application.
State 0 usually indicates a problem. States 1 through 6 are "normal" states. Refer to the Control Builder M online help, Acknowledgement Rules.
- The OPC server can be viewed and traced with a 3rd party OPC AE client
- The interactions between 800xA and the OPC server can be logged with the internal AfwAppLogViewer tool* and the Events and Acknowledges log on the Event Collector service provider in service state.
*) This is something we teach on our E143 Troubleshooting 800xA Expert Workshops.