BMI Library in System 800xA 6.0.3-2 version: Alarm displayed on Faceplate only
Hi Everyone,
I've created an object of type Group (from BMI Library) and its faceplate has showed an alarm. This alarm isn't displayed on any System alarm list and no equipment in this group has an alarm.
I cannot acknowledge, delete or inhibit this alarm.
Please, have you seen this?
I've created an object of type Group (from BMI Library) and its faceplate has showed an alarm. This alarm isn't displayed on any System alarm list and no equipment in this group has an alarm.
I cannot acknowledge, delete or inhibit this alarm.
Please, have you seen this?
Asked 10 months ago
Voted best answer
2
I don't know how the BMI AlarmControl is designed.
The default AlarmControl trigger on Alarm Global Properties which requires alarms received over OPC AE interface. Some connects have additional requirements, e.g. 800xA for Advant Master have requirement to show alarms, also when not having OPC AE connection.
In your case, I suggest starting with using the Alarm Conditions feature of Control Builder M in Online mode to query your suspect objects if they are in alarm or not.
What CondStates do you see? 0 = alarm is disabled by logic, or failed to produce an alarm due to incorrect parameters (out of range severity/class or illegal or too many characters in SrcName/Condition)
The CondState may also be exposed in your function blocks, but it may also be hidden by BMI standard.
In 800xA, you can subscribe for Alarm Global Properties on any object by right clicking it, select Details... then select the Property View tab and finally enable Subscribe for live data. What are the values for IsAlarmActive and IsAlarmActive_Descendants?
If everything is OK, you should have an AC 800M CondState signalling an alarm in the controller followed by an alarm in the 800xA HMI (in lists and via Alarm Global Properties)
Maybe the BMI AlarmControl trigger alarm over something else?
If your Control Builder M application configuration is incorrect, e.g. a SrcName,ConditionName combination having an illegal character or not unique combination an AlmDefErr system event is generated by the AC 800M OPC Server every time you download the application. This system event may have passed unnoticed in the [Workplace Structure]Web System Workplace:System Event List?
The default AlarmControl trigger on Alarm Global Properties which requires alarms received over OPC AE interface. Some connects have additional requirements, e.g. 800xA for Advant Master have requirement to show alarms, also when not having OPC AE connection.
In your case, I suggest starting with using the Alarm Conditions feature of Control Builder M in Online mode to query your suspect objects if they are in alarm or not.
What CondStates do you see? 0 = alarm is disabled by logic, or failed to produce an alarm due to incorrect parameters (out of range severity/class or illegal or too many characters in SrcName/Condition)
The CondState may also be exposed in your function blocks, but it may also be hidden by BMI standard.
In 800xA, you can subscribe for Alarm Global Properties on any object by right clicking it, select Details... then select the Property View tab and finally enable Subscribe for live data. What are the values for IsAlarmActive and IsAlarmActive_Descendants?
If everything is OK, you should have an AC 800M CondState signalling an alarm in the controller followed by an alarm in the 800xA HMI (in lists and via Alarm Global Properties)
Maybe the BMI AlarmControl trigger alarm over something else?
If your Control Builder M application configuration is incorrect, e.g. a SrcName,ConditionName combination having an illegal character or not unique combination an AlmDefErr system event is generated by the AC 800M OPC Server every time you download the application. This system event may have passed unnoticed in the [Workplace Structure]Web System Workplace:System Event List?
Answers
1
I guess from the Faceplate Screenshot there is no Alarm only an Interlock, so it looks like you have connected the Group PCC in a loop as otherwise you cannot have PCC linking to itself?
Maybe you have a GroupStep or PCC_Threshold configured with the Tagname of the Group, or some wrong connection on a PCC_Connect. Does it go away when you, for a try, disconnect all PCC Signals from the Group in the Application?
Maybe you have a GroupStep or PCC_Threshold configured with the Tagname of the Group, or some wrong connection on a PCC_Connect. Does it go away when you, for a try, disconnect all PCC Signals from the Group in the Application?
Add new comment