Moreover, the exception stack frame data, which includes very important
information needed when analysing the real root cause of the SW exception, is
available on the DEBUG port.
Examples of SW exceptions are:
*
access error
*
address error
*
illegal instruction
*
Fatal errors
Fatal errors are faults detected by the internal error checking functionality that, if
it fails, compromises the system reliability (e.g. RTOS errors). The REF 542plus
fatal error handler stores a fatal error description string in the internal memory.
The description string contains a reference to the SW function that generated the
fatal error and a description of the cause. Fatal errors always produce a HW reset.
At start-up, the fatal error is signalled through a HMI and SPA event.
The following table describes signalling/handling of the reset faults:
Faults/Errors Signalling
Level
HW watchdog HMI event “Reset!! Watchdog"
SPA event “0E37”
DEBUG port command ‘4’ shows SW trace logs before
reset (Special REF542 SW)
2
SW exception HMI event “Reset!! SW exception"
SPA event “0E37”
DEBUG port command ‘1’ shows SW exception stack
frame data
2
Fatal Error HMI event “Reset!! Fatal error"
SPA event “0E37”
DEBUG port command ‘1’ shows fatal error description
string
2
Configuration
The configuration is stored in FLASH. At start-up or after a configuration
download, REF 542plus makes a consistency check on it. It consists of:
*
•Version checking
There are separate versions for protection and control functions (FUPLA) and
COM configuration functions.
*
•Function checking
Every installed function must be implemented in the firmware and must have the
expected configuration data/parameters format.
*
•Hardware checking
If a function requires a hardware component, this has to be installed and detected
by the start-up procedure.
120
REF 542plusREF 542plus
Multifunction Protection and Switchgear Control Unit
Operator's manual
1MRS755869
To Next Page
Loading...
