Repository navigation
Failures
Note
Failures are only available beginning version 2.3
The KLN 90B can fail the way a real unit does, so that you can practice what the Pilot's Guide expects of you: notice the failure, read the message, and carry on with other means of navigation. Failures are opt-in. With the random rate off (the default) and nothing failed, the unit behaves exactly as before.
Failures act on the KLN only. A failure never degrades the other GPS units of the aircraft, the sim's own GPS or a Working Title GNS in a hot swap. For hardware failures that is the real behavior, because every unit has its own antenna, receiver and wiring. GPS jamming and spoofing, would reach every receiver of an aircraft in reality, so they are best practiced without a second GPS unit to cross-check with.
- the ARINC 429 output (the driven course pointer, roll steering, the digital cross track, and the nav data and the
RMI bearing when they are routed there). It is always offered, whatever the routing:
ARINC 429 OUTPUT FAIL - the RS-232 output*:
RS-232 OUTPUT ERROR - the RMI output*: no message
- the OBS input (the unit can no longer read the course from the indicator): no message
- the RS-232 input, lost or garbled:
NO RS-232 DATA,RS-232 DATA ERROR - the ARINC 429 air data input:
ARINC 429 AIR DATA FAIL - the altitude input:
ALTITUDE FAIL - the to/from flag:
NAV SUPER FLAG FAILURE - the EEPROM, calibration data cannot be read on power up, the screen and CDI will be displaced:
EEPROM FAILURE: IC1045 EXTERNAL D-BAR INVALID - Annunciators*, lamps, their wiring or the driver can fail:
* ANNUNCIATOR FAILorCHECK * ANNUNCIATORor no message at all for a burnt out bulb (keep an eye on the self-test page!) - the GPS receiver:
NO RCVR DATAorRCVR HARDWARE ERROR. Some failures might be transient and turning the KLN-90B off and on again might clear the error. The receiver may fail completely or it might just take longer to find a signal, depending on the nature of the failure. Antenna coax or connection problems will not show a message, instead the SNR on the STA 1 will drop and RAIM messages may occur. - GPS jamming (manually only, not with MTBF). This takes a while to show their effect while the aircraft enters the range of the jammer. Satellites will slowly drown in noise and loose their signal.
RAIM NOT AVAILABLE CROSS CHECK POSITIONand related messages may be shown. EventuallySATELLITE COVERAGE INADEQUATE FOR NAVwill be shown. - GPS spoofing (manually only, not with MTBF). This takes a while to show their effect while the aircraft enters the range of the spoofer. The spoofer will overpower real signals and the STA 1 page will eventuall display fake satellite data. At that point the KLN will display a wrong location and is unusable for navigation.
RAIM NOT AVAILABLE CROSS CHECK POSITION,SATELLITE COVERAGE INADEQUATE FOR NAV,SYSTEM TIME UPDATED TO GPS TIMEand related messages may be shown during the transition to a the faked position. If the aircraft is equipped with an altimeter, RAIM may detect the faked position and displayRAIM POSITION ERROR CROSS CHECK POSITION. - GPS Satellite failure (manually only, not with MTBF), the strongest satellite will fail, degrading navigation performance:
RAIM POSITION ERROR CROSS CHECK POSITION. Other RAIM and navigation related messages may be shown. - The battery. The battery health will slowly degrade over 3 to 5 years. The current battery health can be viewed on the FLR 1 page. A few weeks before the battery becomes unusable
BATTERY LOW: SERVICE REQUIRED TO PREVENT LOSS OF USER DATAwill be shown. If the battery degraded to 0%, then it is allowed to randomly fail under the MTBF rules. You can always fail the battery manually on the FLR 3 page. DO NOT let the battery fail, it will really delete all user data permanently and that data cannot be recovered. The battery health can only be restored by using the SERVICE button on the FLR 1 page.
* indicates this failure must be enabled by the aircraft developer
A failure only applies to a part your aircraft has. The RS-232 failures, for example, exist only when a fuel computer,
RS-232 air data, a baro source or an RS-232 heading is configured in the panel.xml. The Self Test page shows a flashing TEST FAIL instead of
ANNUN ON while a failure that the real unit's self-test would find is active.
A failed output port sends nothing, so the equipment on that port loses its data: a GPS-coupled autopilot loses its guidance, and with it a flight plan that other equipment read from the unit.
The failure pages are fictional: the real unit has none. Open SET 10 and press ENT on FAILURES. The inner knob moves
between FLR 1, FLR 2 and FLR 3; the outer knob leaves them.
-
FLR 1:
MTBFis the mean time between random failures, from 1 to 999 hours (OFF is the default; 0 or CLR sets it to OFF). The unit fails one of its failable parts at random, on average once per MTBF of flight time (sim time, only while the unit is on).BATTERYshows the health of the battery in percent.SERVICE?repairs all failures, restores the battery to 100% and corrects the GPS epoch. - FLR 2: the failures that are active. CLR on an entry repairs this failure.
- FLR 3: the failures that can happen on this aircraft and are not active. ENT on an entry fails it at once, also with the MTBF off.
Failures persist between flights, per aircraft, until you repair them.