COMPONENT MAINTENANCE MANUAL
AVIATION RECORDERS
FA2100CVR
Rev. 15 Page 52
Apr. 14/16
Description and Operation
23–70–04
Use or disclosure of information on this sheet is subject
to the restrictions on the cover page of this document.
Any detected fault condition asserts the fault output from the CVR. Some faults are
“latched’ meaning that the fault indication will continue to be asserted (regardless of
power cycling) until it is cleared by maintenance action. Other faults may relent, al-
lowing normal CVR operation to continue. In such a case, the fault condition is not
“latched“ and the fault output from the CVR will be de
−
asserted. Of the latched
faults, some may be severe enough to halt and then restart recorder operation.
Such faults are considered fatal. Any active or latched fault condition is also re-
ported by a “not passed” indication in response to the push
−
to
−
test command.
The task ID indicates which module within the software organization detected the re-
ported condition. The “type of event“ field categorizes the general nature of the fault
conditions. Reported categories include:
Table 8.
Fault Processing Event Types and Descriptions
Type of Event
Description
Internal Faults
illegal or unexpected software errors
CSMU flash memory errors
flash memory write or erase errors
BITE errors
detected power supply faults
Communications errors
illegal or unexpected GSE messages
While fault conditions are detected throughout the CVR software modules, the condi-
tions are all reported and logged through the Fault Manager task which executes on
the SMP. It provides the common interface for fault output control and fault history
log management. The fault history log is accessed via GSE commands for down-
loading and analysis of the fault log entries. Likewise, the latched fault condition and
the fault log itself are cleared by GSE commands by using the Portable Interface
Unit. Refer to the Testing and Troubleshooting, Section 100, for the corrective action
to be taken if any of these fault codes should appear in the status report.
The document reference is online, please check the correspondence between the online documentation and the printed version.
