800xA 4.1; Individual I/O point not in alarm but should be
I have an analog input going to a Transmitter4L object inside of an object level module. This object level module is instanced 6 times throughout various modules. The problem is an analog point is configured to alarm when its level falls below the L Limit. I have one instance of the object level where it works, and one where it doesn't. Both are using the same object level instance and the same aspect properties configuration. So in this example, our system is shut down, so the particular analog measurements are both below the L Limit alarm level. One is in alarm, one isn't. I checked alarm services, etc. and everything appears to be OK. BTW - this isn't new code, its about 10 yrs old, so it's been running for a while. The operator said 'it's been like this forever'.
Any help greatly appreciated.
Any help greatly appreciated.
Asked 1 year ago
Answers
0
You did not specify brand & type of controller (don't know "Transmitter4L" by heart) so I assume ABB AC 800M.
A prerequisite for all alarms from AC 800M is a unique combination of SourceName + ConditionName. Furthermore the combination must not be too long (<25 characters, IIRC) and not contain any forbidden characters (spaces, etc). There are two more parameters, Class (1-9999) and Severity (1-1000) which must be set with valid values.
The gatekeeper is the AC 800M OPC server (with a global view of all downloaded items) that will reject emitting alarms where the above criteria is not met.
In older versions, an AlmDefErr is sent to the controller log when downloading the application. The log can be pulled from the Remote System dialog of Control Builder M. In recent versions, the AlmDefErr is sent to the [Workplace Structure]Web System Workplace:System Event List
Make sure neither of those become with said messages at download.
After download, you can use the Control Builder M's Alarm Conditions menu command at any alarm owning object; the CondState must not be 0. Zero (0) means "inhibited by application" or "illegal configuration". The alarm block itself has a Status and Error outputs that will give more distinct error codes which you can translate with the Control Builder M online help.
A prerequisite for all alarms from AC 800M is a unique combination of SourceName + ConditionName. Furthermore the combination must not be too long (<25 characters, IIRC) and not contain any forbidden characters (spaces, etc). There are two more parameters, Class (1-9999) and Severity (1-1000) which must be set with valid values.
The gatekeeper is the AC 800M OPC server (with a global view of all downloaded items) that will reject emitting alarms where the above criteria is not met.
In older versions, an AlmDefErr is sent to the controller log when downloading the application. The log can be pulled from the Remote System dialog of Control Builder M. In recent versions, the AlmDefErr is sent to the [Workplace Structure]Web System Workplace:System Event List
Make sure neither of those become with said messages at download.
After download, you can use the Control Builder M's Alarm Conditions menu command at any alarm owning object; the CondState must not be 0. Zero (0) means "inhibited by application" or "illegal configuration". The alarm block itself has a Status and Error outputs that will give more distinct error codes which you can translate with the Control Builder M online help.
Add new comment