ABB AC 800M

Section 6 Program Code Issues Error Handling
3BSE042835-600 97
Error Handling
If there is any risk that the type may end up in an error state or have a malfunction, it
should have error handling.
If case of error, an ErrorIcon should appear in layer 1 of the module. An ErrorIcon
should also appear in all operator windows.
If an error occurs there should also be an output, called Error from the module. This
output should be boolean and be reset when the malfunction ends. In a program unit
the Error output may be connected to an AlarmCond.
Some control modules, which utilize more complex functions, may require a more
advanced error diagnostics. For these modules, an error display shall be included in
an interaction window. This error display should contain a text explaining the error
and the error code. The error code can come from a failed procedure call, or from
the code itself (Number range -5000 to -6000 for standard library objects). It may
also contain information about where the error has occurred in the code.
Alarm and Event Handling
If no specific reason exists, the more efficient type AlarmCondBasic shall be used.
If an object has alarm handling, the property Alarm Owner should be set.
The AEConfig parameter is used to define whether a supervised condition should
generate an alarm or event. The possible settings are:
AEConfig = 0, Supervision disabled.
AEConfig = 1, Alarm.
AEConfig = 2, Event generated both on condition activation and deactivation.
AEConfig = 3, Event generated on condition activation only.
AEConfig = 4, Supervision only, that is neither alarm nor event generated.
There can be more than one AEConfig parameter per object. It is then possible to
define different configuration for different condition within the object. For example;
the AEConfigH parameter configures the High condition, the AEConfigHH
parameter configures the High High condition etc.