Escolar Documentos
Profissional Documentos
Cultura Documentos
FLIGHTLINE MAINTENANCE
MANUAL
KFC 500
SINGLE FLIGHT CONTROL
SYSTEM INSTALLATION
FOR BELL 430
MANUAL NUMBER 006--15546--0000
REVISION 0, DECEMBER, 1997
The binder(s) required to hold this publication(s) are available and may be ordered from:
AlliedSignal Commercial Avionics Systems
400 N. Rogers Road
Olathe, Kansas, 66062--1294
Telephone 1--800--764--8999
Orders must specify part number, description, and the quantity. Use the following list to
complete the order
PART NUMBER DESCRIPTION
006--03140--0001 (1) inch Binder.
006--03140--0002 (1.5) inch Binder.
006--03140--0003 (2) inch Binder.
006--03140--0004 (3) inch Binder.
006--03140--0005 (4) inch Post Binder.
WARNING
INFORMATION SUBJECT TO THE EXPORT CONTROL LAWS.
THIS DOCUMENT, WHICH INCLUDES ANY ATTACHMENTS AND
EXHIBITS HERETO, CONTAINS INFORMATION SUBJECT TO IN-
TERNATIONAL TRAFFIC IN ARMS REGULATION (ITAR) OR EX-
PORT ADMINISTRATION REGULATION (EAR) OF 1979, WHICH
MAY NOT BE EXPORTED, RELEASED OR DISCLOSED TO FOR-
EIGN NATIONALS INSIDE OR OUTSIDE THE U.S. WITHOUT
FIRST OBTAINING AN EXPORT LICENSE. VIOLATORS OF ITAR
OR EAR MAY BE SUBJECT TO A PENALTY OF 10 YEARS IM-
PRISONMENT AND A FINE OF $1,000,000 UNDER 22 U.S.C.
2778 OR SECTION 2410 OF THE EXPORT ADMINISTRATION
ACT OF 1979. INCLUDE THIS NOTICE WITH ANY REPRO-
DUCED PORTION OF THIS DOCUMENT.
COPYRIGHT NOTICE
TABLE OF CONTENTS
SECTION I
GENERAL INFORMATION
Paragraph Page
Paragraph Page
Paragraph Page
Paragraph Page
SECTION V
THEORY OF OPERATION
Paragraph Page
Paragraph Page
6. GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--1
6.1 Navigating the Remote Terminal Interface Screens . . . . . . . . . . . . . . . . . . . 6--1
6.1.1 Normal Mode Main Menu Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--1
6.1.2 Time and Temperature Information Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--2
6.1.3 History Log Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--2
6.1.4 Logged Data Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--3
6.1.5 Diagnostic Mode Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--5
6.2 Problems Accessing the Remote Terminal Interface Screens . . . . . . . . . . 6--22
6.3 Problems Entering Diagnostic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--22
6.3.1 Diagnostic Mode for FD Processor with AP processor lock out . . . . . . . . . . . . 6--23
6.4 Input/Output Signals Accessible Using the Remote Terminal Interface . 6--23
6.4.1 AP Processor Discrete Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--24
6.4.2 AP Processor Discrete Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--25
6.4.3 FD Processor Discrete Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--27
6.4.4 AP Processor Analog Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--27
6.4.6 ARINC 429 Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--29
6.5 System Configuration Using the Remote Terminal Interface . . . . . . . . . . . 6--30
SECTION VII
MAINTENANCE
Paragraph Page
Paragraph Page
ILLUSTRATIONS
Figure Page
Figure Page
TABLES
Table Page
SECTION I
GENERAL INFORMATION
1.1 INTRODUCTION
This flight line Maintenance Manual will be used to supplement the Bell Textron Maintenance
Manual for the Bell 430 Helicopter for maintenance of the Bendix/King KFC 500 Automatic Flight
Control System. The information contained herein supplements the basic Bell Maintenance Manual
only in those areas listed herein. For Limitations, Procedures and Performance Data not contained
in this manual, consult the basic Bell 430 Helicopter Maintenance Manual.
This manual provides general system maintenance instructions and theory of operation for the KFC
500 Automatic Flight Control System for the Bell 430 Helicopter.
This manual is intended to be a supplement to the aircraft maintenance manual provided by Bell
Helicopter for the model 430. The information provided here is to assist in more detailed flight line
check out and trouble shooting of suspected problems in the KFC 500 Flight Control System. This
manual will supersede information from Bell Helicopter only for the specific items addressed.
Abbreviations used in this manual are defined below.
Abbreviation Equivalent
ADI Attitude Director Indicator
AFCS Automatic Flight Control System
ALT Altitude
AP Autopilot
APR Approach
BL Bank angle Limit
C Centigrade (or Celsius)
CBT Cyclic Beep Trim
cm centimeters
DMA Direct Memory Access
ECAL Embedded Control Algorithm Language
EFIS Electronic Flight Instrument System
EPROM Erasable Programmable Read Only Memory
FCC Flight Control Computer
FD Flight Director
FIFO First In, First Out (queue)
FTE Force Trim Enable
FTR Force Trim Release
G constant for acceleration of gravity (approximately
9.81 meters/second2 or 32.2 feet/second2)
GA Go Around
GS Glideslope
HDG Heading
HSI Horizon Situation Indicator
IAS Indicated Airspeed
Abbreviation Equivalent
IIDS Integrated Instrument Information Display System
in. inches
IP Interprocessor
kg kilograms
knots nautical miles per hour
LNAV Long--range Navigation
LOC Localizer
MAI Maintenance
MLS Microwave Landing System
ms milliseconds
MSP Mode Select Panel
MUX Multiplexer
NAV Navigation
PAH Pitch Attitude Hold
PFT Pre--flight Test
PIC Pilot In Control
RAH Roll Attitude Hold
RAM Random Access Memory
Ref Reference
ROM Read Only Memory
RTI Remote Terminal Interface
SCAS Stability Control Augmentation System
SDI Source/Destination Identifier
sec seconds
SSM Sign Status Matrix
TAS True Airspeed
V Volts
VDC Volts -- DC (direct current)
VOR VHF (Very High Frequency) Omni Range
VS Vertical Speed
YBT Yaw Beep Trim
Optional
equipment, KRA 405 KVG 350 KCS 305
Only needed for Radar Vertical compass
flight director
system
Altimeter Gyro system
(KMS 540/
KMS 541) mode switch request information
pitch axis
servo feedback
KSM 575
roll axis
KMC 100 installation data to be stored
servo commands
linear actuator
configuration (roll axis)
installation data (servo stop
module positions, audio volume, etc.) KCP 520 roll axis
servo feedback
FLIGHT
engaged mode information KSA 572 roll axis
KAD 480 COMPUTER trim servo control position
Air Data vertical speed, altitude, selected yaw axis
altitude, indicated airspeed servo commands
(roll axis) resolver
System
engaged mode information,
command bar information
collective axis
Force aircraft KRG 333 collective
control position feedback
Trim speaker acceleration/ control position
System rate sensor resolver
Approach (ILS, VOR & RNAV) Roll and Pitch command to capture and track
LOS and GS beams, VOR and RNAV ap-
proach course.
Pitch Attitude Hold Pitch command to maintain pitch attitude.
Altitude Hold Pitch command to hold altitude.
Vertical Speed Hold Pitch command to maintain ascent or descent
rate.
Indicated Airspeed Hold Pitch command to maintain airspeed.
Airspeed Limit Mode Pitch command to reduce airspeed and return
to previous mode.
Glideslope Pitch commands to track glideslope
Go Around Commands aircraft to wings level and ascent
of 750 FPM.
SCAS The autopilot processor control the pitch, roll
and yaw servoes to dampen aircraft rates on
these axis.
AP (Autopilot) Controls attitude and/or flight path depending
on mode.
FUNCTION CHARACTERISTICS
Altitude Stability 50 Feet
Directional Stability 3
Maximum Bank Angles Approach 20
Heading modes Others 25
NAV and APPR modes
Maximum Pitch Commands 15
Pitch Attitude Hold
Altitude Hold
Glideslope
Vertical Trim Rates 0.1g
Pitch Attitude Hold
Alt Hold
Analog Inputs
Accelerometer
Radar Altimeter
Control Position Resolvers
26VAC 400Hz Reference
Vertical Gyro
Directional Gyro
KRG 333 Rate Sensor or KRG 333 Rate Gyro
KLA 570/KSM 575 LVDT Position Feedback
Sensors.
Analog Inputs spares
Analog Outputs
Servo Amplifier Output to KLA 570/KSM 575
Linear Actuator
Servo Amplifier Output to KSA 572 Rotary Ac-
tuator
KLA 570/KSM 570 LVDT Sensor Excitation
Voltages
LVDT Common
Aural Alert Audio Output
Actuator Position Indicators
VSCS Command to VSCS Actuator
String Pot Excitation
1 z ---------------------------------------- AP DATA BF
2 z ---------------------------------------- +5V AP
3 z ---------------------------------------- +15V AP
4 z ---------------------------------------- --15V AP
5 z ---------------------------------------- KEY PIN
6 z ---------------------------------------- APA VAL BF
7 z ---------------------------------------- COM DATA BF
8 z ---------------------------------------- FD DATA BF
9 z ---------------------------------------- +5V FD P
10 z ---------------------------------------- +12V FD P
11 z ---------------------------------------- --12V FD P
12 z ---------------------------------------- +28FD PROT P
13 z ---------------------------------------- +5V FD CP
14 z ---------------------------------------- +12V FD CP
15 z ---------------------------------------- --12V FD CP
16 z ---------------------------------------- +28FD PROT CP
17 z ---------------------------------------- RS232 TX
18 ---------------------------------------- ! RS232 RX
19 z ---------------------------------------- RS232 RTS
20 ---------------------------------------- ! RS232 CTS
21 z ---------------------------------------- RS232 COMMON
22 z ---------------------------------------- DAC TEST OUT
23 z ---------------------------------------- DAC TEST GND
24 z ---------------------------------------- DIO SPARE2
25 z ---------------------------------------- DIO SPARE1
26 z ---------------------------------------- AUDIO RESET
27 z ---------------------------------------- APB VAL BF
28 z ---------------------------------------- +VOFFSET AUD
29 z ---------------------------------------- AP SPARE2
30 z ---------------------------------------- +28V PROT AUD
31 z ---------------------------------------- AP SPARE1
32 z ---------------------------------------- FD SPARE1
33 z ---------------------------------------- AIO SPARE1
34 z ---------------------------------------- AIO SPARE2
35 z ---------------------------------------- BTE1
36 z ---------------------------------------- S/A SPARE1
37 z ---------------------------------------- S/A SPARE2
SPECIFICATION CHARACTERISTIC
SIZE: Width: 3.375(85.72mm)
Height: 3.375(85.72mm)
Length: to back of faceplate 6.418(163.02mm)
WEIGHT: 1.9lbs(85kg)
MOUNTING: Four black FHP 6--32x3/4 screws
MATING CONNECTOR PN 030--02583--0005
TSO COMPLIANCE: C9c, C52a
DO--138 ENVIRONMENTAL CATEGORIES
POWER INPUTS: +28VDC @ 2.0A Max
Backlighting Power +5, 5.0 VRMS, 28VDC @
10ma
Dim Bus Common <3.0VDC
POWER OUTPUTS:
NOTE
The annunciations can be tested by placing the BRT/DIM/TEST
switch on the overhead panel in the test position.
SPECIFICATION CHARACTERISTIC
SIZE: Length (clevis mtg hole to first rodend hole
with piston centered)
Roll: 29.34 (745.20 mm)
Pitch: 27.03 (686.60 mm)
Yaw: 41.63 (1057.40 mm)
Width: 2.188(55.575mm)
WEIGHT: Roll: 3.13 lbs (1.42kg)
Pitch: 3.10 lbs (1.41 kg)
Yaw: 3.17 lbs (1.44kg)
MOUNTING: Per aircraft manufacturing specifications
MATING CONNECTOR PN 030--03227--0000
TSO COMPLIANCE: C9c
DO--160C ENVIRONMENTAL CATEGORIES F2--ACYE1RFDXSB(BZ)(AB)(BZ)ZYZ[A3XX]
XA
POWER INPUTS: NONE
SPECIFICATION CHARACTERISTIC
SIGNAL INPUTS: LVDT Excitation, 1.7 VAC, 3.5KHz
Brake Disengage, 28 VDC, 0.425 A
Motor, 28VDC, 1.3A
SIGNAL OUTPUTS: Piston Position, 0--1.5 VAC, 400Hz, 2--wire
SPECIFICATION CHARACTERISTIC
SIZE: Length: 7.64(194.1mm)
Width: 3.71(94.2mm)
Height: 3.58(90.0mm)
WEIGHT: 3.1lbs(1.406kg)
MOUNTING: Per aircraft manufacturing specifications
MATING CONNECTOR PN 030--03235--0000 & 030--03236--0000
TSO COMPLIANCE: C9c
DO--160C ENVIRONMENTAL CATEGORIES [A2F2]--BA(YLM)E1WXXXSB(BZ)(AB)(BZ)AR
Z[A3XX]XB
POWER INPUTS: Clutch Engage: 28VDC, 0.76A
SIGNAL INPUTS: Motor: 28VDC, 0.9A
Brake Disengage: 28VDC, 0.5A
SIGNAL OUTPUTS: None
SPECIFICATION CHARACTERISTIC
SIZE: Width: 4.61(117.1mm)
Height: 2.46(62.4mm)
Length: 7.77(197.3mm)
WEIGHT: 2.6lbs (1.12kg)
MOUNTING: Four #6 screws
MATING CONNECTOR PN 030--01175--0000
TSO COMPLIANCE: C9c, C52a
DO--138 ENVIRONMENTAL CATEGORIES
POWER INPUTS: +28vdc @ .475A nom
POWER OUTPUTS: +5 precision (test only)
+15VDC (test only)
+5 monitor (test only)
+15 monitor (test only)
Lateral Excitation
SIGNAL INPUTS: Test Input (ground=Test)
SIGNAL OUTPUTS: Laterial Acceleration
Normal Acceleration
Longitudinal Acceleration
Roll Rate
Pitch Rate
Yaw Rate
Rate Valid #1
Acceleration Valid
Rate Valid #2
SPECIFICATION CHARACTERISTIC
SIZE: Width: 3.356(85.24mm)
Height: 6.156(156.36mm)
Length: 7.1(180.34mm)
with connector 9.06(230.12mm)
WEIGHT: 3.5lbs(1.59mm)
MOUNTING: Four #6--32 X .75 screws
MATING CONNECTOR PN 030--02607--0014
TSO COMPLIANCE: C8c, C10b
DO--138 ENVIRONMENTAL CATEGORIES
POWER INPUTS: +28VDC Bezel Light < 264ma
+5VDC Bezel Light < 1.053A
POWER OUTPUTS: +5VDC Test
+12VDC Test
--12 VDC test
+6 VDC Test
--6 VDC Test
SIGNAL INPUTS: Discrete Inputs
200/300 Ft Alert Band Strap
20/50 FT Resolution
Alt Sel Master
System 1/2 Select
Alternate Input Select
Ext RSC Test
SIGNAL OUTPUTS: Discrete Outputs
Ext Alert Ann
Alt Sonalert
Audio Out
Aural Alert
SYMBOL CAS PART NBR DESCRIPTION [UOM] -0000 -0001 -0002 -0050
SECTION II
INSTALLATION
CAUTION
IT IS PARTICULARLY IMPORTANT THAT THE GYRO
INSTRUMENTS OF THE KFC 500 SYSTEM BE REPACKED
IN THEIR FACTORY SHIPPING CONTAINERS WHEN BEING
RETURNED FOR REPAIR OR EXCHANGE. THESE UNITS
ARE THE KRG 333, KSG 105 AND KVG 350.
SECTION III
OPERATION
3.1 GENERAL
Due to the complexity of this system, anyone having any questions about the operation of this
system should refer to the KFC 500 Pilots Guide, PN 006--08769--0000, and the approved aircraft
Flight Manual.
SECTION IV
STC APPROVALS AND SYSTEMS INTERCONNECTS
4.1 GENERAL
For TC approval and system interconnects consult the appropriate Bell Document package for the
type of aircraft; or contact:
Product Support Department
AlliedSignal Aerospace
400 N Rogers Road
Olathe, Kansas 66062
Phone: Area Code (913) 782--0600
SECTION V
THEORY OF OPERATION
NOTE
The processor functions are partitioned so that each processor
group performs independent functions. The maintenance
processor provides the maintenance/diagnostic interface. The FD
processor provides fight director information to the pilot via
command bars. The AP processors provide servo control for
coupled flight operations and SCAS damping.
There are three separate power supplies used in the FCC. This also helps to maintain the
independence of the various processors in the unit. There is one power supply for the maintenance
processor. The FD processor receives its power from a second power supply. The third power
supply provides power to the AP processors.
The information contained in this paragraph only pertains to systems which include the flight
director function. Either one or two EFISs are used to collect navigation system and attitude
information and transmit that information to the FCCs FD processor. Mode selection and cockpit
switch information is transmitted by the MSP to the FD processor. The FD processor also receives
altitude and vertical speed information from the air data system and vertical acceleration via the
internal bus from the AP processors. Using the Pilot In Command switch input, it selects which EFIS
is to be used for data input and calculates pitch and roll flight director commands based on mode
selection. Mode selection information from the flight director and information received on an internal
bus from the AP processors is transmitted to the EFIS and the MSP for display. The flight director
commands are transmitted to the EFIS for display as pilot command bars and to the AP processors
for use in coupled modes.
The AP processors receive ARINC 429 air data information for scheduling of control gains. The
remaining external inputs to the AP processors are analog in nature. The AP processors receive
pitch and roll attitude from the vertical gyro, heading from the directional gyro, and body attitude
rates and accelerations from the KRG 333 triaxial rate gyro/accelerometer. The AP processors
control the KSM 575 and KSA 572 actuators. To ensure that the AP processors work together to
provide servo control, one processor (labeled AP A) provides the analog commands for the servos
and the other processor (labeled AP B) provides the discrete control for servo power and
engagement and disengagement of servo brakes. However, each AP processor computes servo
commands and determines power and brake engagement status and communicates its status to
the other AP processor for monitoring purposes. Various cockpit discrete annunciations are also
controlled by the AP processors. For coupled modes, the flight director commands received from
the FD processor via an internal bus are used, or the AP computes a default attitude--hold mode
based on the information received from the vertical gyro and enhanced by the directional gyro and
air data information if available.
The maintenance processor communicates with the other processors of the FCC for maintenance
procedures, allowing FCC inputs to be monitored and outputs to be controlled through a Remote
Terminal Interface (RTI). During normal operation, it retrieves data from the configuration module
on power up and transmits it to the FD and AP processors over internal busses. Codes of errors
detected and transmitted by the other processors are stored by the maintenance processor in
non--volatile memory for later analysis.
The configuration module is used to store installation specific data used by the FCC. This includes
extended and retracted stop positions for the linear actuators, normal control position ranges for
each of the control position resolvers, desired audio volume and frequency for autopilot aural
annunciations, number of EFIS tubes in the EFIS configuration, and whether the system is a
SCAS/ATT only system.
Figure 5--2 details the discrete signals that are input or output from the FCC. This diagram describes
the interface of the force trim system to the FCC, the Go Around switch input to the FCC, and beep
trim inputs to the FCC. In addition, the discrete annunciation outputs from the FCC for AP mode
on, SCAS mode on, AP fail, SCAS fail, and individual axis failures are also included in the diagram.
Page 5--4
SCAS FAIL
ANNUN AP SCAS PILOT CO--PILOT
FIG7430A.VSD
I AP FAIL L R
ON ON GA SWITCHES
ANNUN
AFCS DISC
COLLECTIVE
I ANNUN
YAW SWITCH
MISTRIM
PITCH TRIM UP
YAW FTE EN
PILOT FTR
FT -- CB
PILOT
FLIGHT CONTROL SYSTEM
CO--PILOT YAW
CYCLIC FTR SWITCHES
PIC FTR
SWITCH
YAW DETENT
AFCS
SWITCH
NOTE
The FCC will engage/disengage AP or SCAS in response to these
button presses if the FCC is in normal mode. Turning the AP
MASTER off while using MSP diagnostic mode is suggested.
Backlighting intensity may be adjusted by pressing the CBT roll, left to increase, right to decrease.
Mode indication intensity may be adjusted by pressing CBT pitch, up to increase, down to decrease.
To save the settings in non--volatile RAM in the MSP, exit the installation mode by pressing and
holding AP and SCAS simultaneously.
Mode indication intensity should respond to covering and uncovering the photocell above and
midway between the APR and NAV buttons. These indications should still be visible when the
photocell is totally blocked from the ambient light.
5.1.1.4 MSP Diagnostic Mode
To enter MSP diagnostic mode, the MSP ARINC 429 outputs should be connected to the MSP
ARINC 429 inputs (the following pins on the MSP connector should be tied together : pin Z to pin
W and pin Y to pin X). Also, the SDI input pins on the MSP connector should be grounded (pins h
and i). While in this mode, pressing the AP and SCAS buttons simultaneously should cause all mode
annunciators on the MSP to be illuminated. A possible stuck button on the MSP front panel is
indicated by the IAS mode annunciator not being illuminated when the AP and SCAS buttons are
pressed together. A possible stuck cockpit switch read in by the MSP is indicated by the FD mode
annunciator not being illuminated when the AP and SCAS buttons are pressed together. Internal
failures in the MSP are indicated by other mode annunciators not being illuminated when the AP
and SCAS buttons are pressed together. Pressing the AP and SCAS buttons simultaneously again
will cause all mode annunciations to be turned off. Also, when in diagnostic mode, each mode button
on the MSP can be pressed individually to toggled the mode annunciation associated with it. To exit
MSP diagnostic mode, the connection between the MSP ARINC 429 output and MSP ARINC 429
input must be removed.
NOTE
Certain buttons are not available on the KMS 541 (i.e., IAS
button). But, the annunciator above the blank button on the KMS
541correspondingtowhereabuttonwouldbeonaKMS540(see
Figure 1--4 and Figure 1--5) will function similarly for the KMS 541.
For example, if a button on the KMS 541 front panel is possibly
stuck, the annunciator above the blank button on the KMS 541
corresponding to the IAS button on the KMS 540 will not be
illuminated when the AP and SCAS buttons are pressed at the
same time.
NOTE
If both sources of configuration data are invalid (internal to the FD
processor and from the configuration module), configuration
information is undefined. This situation can result in incorrect
operation of the FD processor. But, an error will be logged in the
FCC error log when the configuration information is undefined.
NOTE
If AP disconnect circuit breaker is pulled to enter diagnostic mode
is must be reset prior to servo amp tests.
On entering diagnostic mode, the FD processor turns off its outputs including ARINC 429
transmission. In this mode, the FD processor accepts commands from the maintenance processor
to set its outputs and report the state of its inputs.
The interface with the KRG 333 is verified by asserting a test discrete to the KRG 333.
The KRG 333 is expected to set its rate and acceleration validity signals to an invalid state
and set its rate and acceleration outputs to values outside of their normal operating range.
This test verifies the reasonability of the KRG 333 power supplies and most of its circuitry
as well as the continuity of the signal paths from the KRG 333 output stages through the
harness to the FCC and the AP processors. This test does not exercise the acceleration
and rate sensors.
After removing the KRG 333 test discrete signals, the rate and acceleration validity
signals are expected to return to their valid state. The acceleration and rate signals are
expected to return to values consistent with an undisturbed KRG 333 which is reasonably
level (up to 0.5 gs of lateral acceleration is allowed, which corresponds to approximately
26 degrees from level)
At the end of the test, the visual and aural disconnect warnings are activated briefly.
NOTE
A linear actuator or trim servo is not commanded to move at any
time during preflight test unless the brake is engaged (when
testing for stall current as part of the brake test). Also, servo
currents are monitored throughout the test to prevent hardware
damage that could result from excessive power demands for a
shorted servo motor. AP mode and SCAS mode engagement can
be inhibited even if preflight test passes when the AP monitors
have failed as a part of AP Normal mode.
In the event of a detected failure during pre--flight test, the units where a failure was detected may
be retested up to two more times. If such a failure is detected during all three attempts, the unit under
test is considered to have failed. At the end of pre--flight test, if failures were detected affecting an
individual axis, one or two of the PITCH FAIL, ROLL FAIL, or YAW FAIL annunciations on the IIDS
will be on as appropriate to indicate which axis(axes) has(have) failed. At the end of pre--flight test,
if failures were detected affecting all three axes of operation, AP FAIL and/or SCAS FAIL
annunciations on the IIDS will be on as appropriate for failures preventing control of all axis in the
corresponding mode. If a failure was detected during preflight test, an error will be logged in the FCC
error log. The error log can be useful in determining why preflight test failed.
The AP processors are ready to perform their task of controlled flight (AP mode or SCAS mode),
if other requirements are met (i.e., completion of pre--flight test without detection of a failure
preventing engagement of the requested mode in at least one axis). AP and SCAS mode operation
are described in detail in section 5.3.
If requested by the maintenance processor, the AP processors will enter diagnostic mode provided
that:
A. They are in Normal mode (PFT completed, although not necessarily passed) and no
mode is engaged
B. Force trim circuit breaker is on
C. Cyclic FTR switch is pressed
D. AFCS disconnect switch is pressed, or AFCS DISC circuit breaker is pulled
NOTE
The AFCS DISC circuit breaker is pulled to enter diagnostic mode,
the circuit breaker should be reset after diagnostic mode is
entered to allow all functions to work. If the circuit breaker is not
reset servos cannot be engaged and tested when in diagnostic
mode.
On entering diagnostic mode, all outputs are initially turned off. Due to the set up in the aircraft
harness, this will cause the annunciators on the IIDS to be illuminated. In this mode, the AP
processors accept commands from the maintenance processor to set their outputs and report the
state of their inputs.
While in diagnostic mode, detected motion of the collective position will cause the AP processors
to leave diagnostic mode unless the AP and SCAS buttons on the MSP are simultaneously pressed
during the motion.
After its power--up operation, which is similar to that of the other processors, the maintenance
processor reads the data from the configuration module for transmission to the FD and AP
processors when requested.
In its Normal mode, it logs temperature statistical data and error codes reported by the other
processors. It provides the Remote Terminal Interface (RTI) for maintenance operations. Various
screens of menus and display data are available. These displays are described in greater detail
later in this manual.
When diagnostic mode engagement is requested via the RTI, the maintenance processor sends
a diagnostic mode request to the FD processor and the AP processors. Each processor is expected
to respond to the request with a denial or approval of the request. If a processor does not respond
within the allotted response time, the maintenance processor will display a message on the RTI that
the processor did not respond (this will always happen for FD B in the Bell 430 installation, since
there are not two FD processors in the FCC). But, the processors that responded will be allowed
to enter diagnostic mode in this instance as long as all responding processors responded with an
approval of the request. If any processor responds denying diagnostic mode engagement,
diagnostic mode engagement is not allowed and a failure screen will be displayed on the RTI (see
Figure 41).
When diagnostic mode is engaged, the maintenance processor provides the interface between the
FD processor and AP processors and the user using the RTI. The maintenance processor relays
requests to the FD processor and AP processors for current input status and displays the
information on the RTI. The maintenance processor also relays requests to the FD processor and
AP processors to set outputs based on user input from the RTI.
5.1.5 MONITORS
During normal operation, the FD processor and AP processors will perform monitoring functions
to ensure proper performance. Failures detected by monitors will in most cases inhibit/disconnect
mode engagements either totally or on a partial basis. Error codes are reported to the maintenance
processor, which will log (store) these codes in non--volatile memory for maintenance access via
the RTI.
The operation of the monitors is dependent on the mode of operation. Reporting of certain error
codes is turned off when the aircraft is determined to be on the ground to minimize the number of
logged errors which may be due to the operation of other systems. Logging of errors by the
maintenance processor is limited in that only the first occurrence of a particular error is logged within
each power cycle.
A more detailed explanation of error codes that could be logged and possible failures detected is
provided as Appendix A. Appendix A also details the monitor that generated the error for the AP
monitoring error codes and lists which error codes, when logged, will disable AP mode or SCAS
mode engagement.
The force trim system interacts with the FCC to provide two main functions in the aircraft:
A. Provides a force feel to the pilot when FORCE TRIM is activated by pressing the FORCE
TRIM switch on the upper portion of the pedestal.
B. Provides a reference position for the controls for coupled flight.
The force trim system is supplied by the aircraft and is monitored by the FCC to provide mode
disengagement when appropriate. The force trim system consists of a spring cartridge and an
engage clutch in each axis. The engage clutch is contained in the KSA 572 trim servo and 28 VDC
to the clutch engage solenoid locks the output shaft of the actuator. When the shaft locks, the pilot
is still able to move the control but the spring cartridge deflects providing a force feel to the pilot.
When 28 VDC is removed from the engage clutch solenoid, the actuator shaft is no longer locked
and movement of the control will freely move the shaft through the spring cartridge.
The operation of the force trim system is controlled via a series of switches. The states of these
switches are monitored by both the FD and AP processors and will affect the operation of the flight
director and autopilot functions as described in section 5.3.3. Refer to Figure 5--2 for a diagram
including the interface of the force trim system with the FCC.
Pulling the force trim circuit breaker or turning off force trim power removes the 28 VDC to the pitch,
roll and yaw KSA 572 engage clutches and allows the controls to move freely. Activating Cyclic FTR
will also do this in the pitch and roll axis, and activating Yaw FTR will do this in the yaw axis. Cyclic
FTR is activated by pressing the FTR button on the cyclic grip one half--way, deflecting it fully will
also activate Yaw FTR. Yaw FTR may also be activated via a switch on the collective control.
The pilot can override the servo control provided by the FCC when AP mode is engaged. When the
pilot controls are operated, the spring cartridge will cause the appropriate detent switch to be
engaged. When engagement of a detent switch occurs AP mode is temporarily disengaged and
SCAS mode is engaged to allow the pilot control. When the detent switch is disengaged AP mode
will be reengaged. If a detent switch is active prior to AP engagement it will prevent the AP mode
from engaging.
The FCC provides motor drive, LVDT excitation, servo power, and brake release solenoid control
for each of the primary (linear) servos in the system and receives LVDT position information. The
FCC provides motor drive, servo power, and brake release solenoid control for each of the trim
servos in the system. The FCC receives control position input information from four control position
synchro resolvers (one for pitch, roll, yaw, and collective control position) attached to the control
linkages.
NOTE
When no mode is engaged and any mode switch is pressed that
mode will be engaged (if mode engagement criteria is met -- i.e.,
all mode inputs valids). This will provide control in the axis for that
mode (i.e., vertical axis for altitude hold -- ALT button) and the
default mode in the other axis will be activated.
The flight director has horizontal and vertical steering command modes that generally operate
independently but in some cases interact. The different modes select different sensors to be used
to provide steering commands to the EFIS display and possibly the autopilot. A mode sequences
through the following stages:
A. Arm -- The sensors used for the mode are monitored to determine the proper time to begin
the maneuver to the new flight path.
B. Capture -- The FCC is providing commands to maneuvering the aircraft to the new flight
path.
C. Track -- The FCC is providing commands to maintain the desired flight path after it has
been acquired.
In some instances, the sequencing to Track will appear instantaneous, since the FCC will be able
to acquire the desired flight path upon engagement of the mode. It is possible to be in two vertical
or horizontal modes simultaneously. While tracking in one mode, a second mode can be armed.
When the aircraft nears the flight path for the second mode, the first mode is disengaged and the
capture stage of the second mode is entered.
An FD mode (vertical or horizontal) is deselected by:
A. Pressing the appropriate button on the MSP or KAV 485 for the mode when the mode
is engaged.
B. Sequencing to another mode in the same axis through a normal transition (i.e.,
pressing another mode switch or transition from Arm to Capture of a previously
selected mode).
C. Pressing the FD Off switch on the cyclic control.
D. Reversion to default mode or disengagement due to the loss of a sensor, whether
caused by a failure or by pilot action.
E. Moving the position of the PIC switch.
F. Pressing cyclic FTR for the pilot not selected by the PIC switch.
FD mode annunciation information is transmitted on the FD processor ARINC 429 output channel.
This information is transmitted to the EFIS for mode annunciation display and to the MSP for mode
engagement acknowledgment. The FD processor transmits unique annunciation information to
differentiate between arm and capture phase for modes having a separate arm and capture phase
(i.e., NAV mode).
This mode is the default horizontal mode. It is entered when the FD button on the MSP is pressed,
when a button on the MSP is pressed that only engages a vertical mode (i.e., ALT), or when the
button for the currently engaged horizontal mode is disengaged by pressing the button on the MSP
corresponding to that mode. The reference attitude is the roll attitude present when the mode is
initially engaged. Upon engagement, if roll attitude is less than 6 degrees, level attitude will be
commanded and a command to maintain the heading present when level attitude is attained will
be generated. During RAH mode, the FD processor will generate commands to maintain the
reference roll attitude or reference heading as appropriate.
This mode is entered when the HDG button on the MSP is pressed. During HDG select mode, the
FD processor will generate commands to maintain the selected heading on the HSI. The maximum
roll attitude that will be commanded when in HDG select mode is limited by the BL selection (see
section 4.1.2.1 MSP Buttons, for more information on selecting the bank angle limit).
This mode is entered when the NAV button on the MSP is pressed. The navigational sensor to be
coupled to for NAV command computation is selected by the EFIS. Allowed NAV sensors are VOR,
LOC, or LNAV. If the FD processor is computing a command to Capture or Track a NAV sensor and
the selected sensor is changed on the EFIS, NAV mode will be disengaged and the FD processor
will revert to RAH. During NAV Track mode, the FD processor will generate commands to maintain
the course for the selected NAV sensor. The maximum roll attitude that will be commanded when
in NAV mode is limited by the BL selection (see section 4.1.2.1 MSP Buttons, for more information
on selecting the bank angle limit).
This mode is similar to NAV mode mentioned in the previous paragraph, but is used for category
I command computations when approaching a runway for landing. It is entered when the APR
button on the MSP is pressed. The navigational sensor to be coupled to for APR command
computation is selected by the EFIS. Allowed APR sensors are VOR, LOC, or LNAV. If the FD
processor is computing a command to Capture or Track an APR sensor and the selected sensor
is changed on the EFIS, APR mode will be disengaged and the FD processor will revert to RAH.
During APR Track mode, the FD processor will generate commands to maintain the course for the
selected APR sensor. When aircraft heading is more than 105_ from the selected course heading
for the APR sensor selected, APR mode becomes back course mode, using inverted commands
to Capture or Track the selected course.
This mode is the default vertical mode. It is entered when the FD button on the MSP is pressed,
when a button on the MSP is pressed that only engages a horizontal mode (i.e., HDG), when the
button for the currently engaged vertical mode is disengaged by pressing the button on the MSP
or KAV 485 corresponding to that mode (except for Go Around Mode), or when the selected vertical
mode becomes invalid. The reference attitude is the pitch attitude present when the mode is initially
engaged. During PAH mode, the FD processor will generate commands to maintain the reference
pitch attitude.
This mode is entered when the ALT button on the MSP is pressed or when the altitude selected on
the KAV 485 is attained when in altitude select mode. During ALT hold mode, the FD processor will
generate commands to maintain the altitude present on the KAV 485 when the mode is engaged.
NOTE
The selected altitude value may be changed while in ALT hold
mode without causing disengagement of the mode. But, another
vertical mode (i.e., vertical speed hold) will need to be established
to capture the newly armed selected altitude. Alt Hold mode also
uses vertical acceleration as a sensor. The AP has to be
operational as well as KRG 333 acceleration valid to obtain a valid
vertical acceleration.
This mode is entered when the VS button on the MSP is pressed or when the VS ENG button on
the KAV 485 is pressed. During VS hold mode, the FD processor will generate commands to
maintain the selected vertical speed on the KAV 485.
NOTE
The selected vertical speed value may be changed while in VS
Hold mode without causing disengagement of the mode. VS hold
mode also uses vertical acceleration as a sensor. The AP has to
be operational as well as KRG 333 acceleration valid to obtain a
valid vertical acceleration.
This mode is entered when the IAS button on the MSP is pressed. The reference airspeed is the
IAS present when the mode is initially engaged. During IAS hold mode, the FD processor will
generate commands to maintain the reference airspeed.
This mode is entered automatically to prevent the aircraft from exceeding maximum operating
velocity (Vmo). This mode is engaged when IAS exceeds Vmo or IAS is predicted to exceed Vmo
within 5 seconds based on current IAS and rate of IAS change. During airspeed limit mode, the FD
processor will generate commands to cause the aircraft to pitch up, thus reducing airspeed. Once
the overspeed condition has been addressed, airspeed limit mode will disengage and the vertical
mode that was engaged before airspeed limit mode was engaged will be reengaged, unless a
failure was detected during airspeed limit mode that would cause loss of the previously engaged
mode (then PAH mode would be engaged).
This mode is a vertical submode of the horizontal APR mode. Whenever the selected APR sensor
is LOC and the APR mode is not in back course mode, GS Arm will be engaged when APR mode
is coupled. Once the horizontal localizer course is being tracked in APR mode, GS capture will be
engaged. Glideslope capture may also become active if the system approaches a valid GS beam.
Upon GS capture, the system will command the aircraft to maneuver to follow the GS beam. When
the system is centered on the GS beam, it will transition from GS capture to GS track mode. When
in GS track mode, the FD processor will generate pitch commands to follow the GS beam to bring
the aircraft to proper altitude for landing. If the radar altitude input to the AP processors is valid, the
FD processor will generate an autolevel command to maintain an altitude of 50 feet when this
altitude is reached in GS mode.
NOTE
Radar Altitude is used to schedule gain on GS. If Radar Altitude
is invalid, a backup gain schedule will give reduced performance.
Vertical acceleration is required for GS mode. The AP has to be
operational and KRG 333 acceleration valid for GS mode.
This mode is entered when the Go Around switch is pressed. Unlike other modes, GA mode is not
disengaged when the Go Around switch is pressed and GA mode is engaged. Go Around mode
can only be disengaged by selecting another vertical mode or when the FD processor receives an
FD Off request from the MSP. During GA mode, the FD processor will generate commands to cause
the aircraft to enter a climb of 750 feet per minute.
NOTE
When GA mode is initially engaged as the vertical mode, wings
level is engaged as the horizontal mode. After GA mode has been
engaged, a different horizontal mode may be engaged, like
heading select mode, for lateral steering if desired.
The reference for certain FD modes may be changed using the CBT. Reference adjustment may
be performed with the CBT in one of two ways:
A. Discrete reference changes -- short, discrete clicks of the CBT will cause a discrete step
change in the reference
B. Slewing reference changes -- holding the CBT in a given direction will cause a continuous
change in the reference at a set rate while the CBT switch contact is maintained
Mode references can be adjusted when one of the following modes is engaged:
vertical -- Pitch Attitude Hold, Altitude Hold, IAS Hold, Vertical Speed Hold
horizontal -- Roll Attitude Hold, Heading Select
The reference may be adjusted only while the engaged mode is being tracked. When slewing the
pitch attitude reference in PAH, the reference will synchronize to the current aircraft pitch attitude
when the slewing is completed (CBT switch is released).
The cyclic FTR switch for the pilot selected with the PIC switch can be used to adjust the reference
for certain FD modes. When the cyclic FTR switch is pressed and then released, the reference for
any of the following modes, if engaged, will be synchronized to the current aircraft state (i.e., current
altitude if in ALT hold mode):
vertical -- Pitch Attitude Hold, Altitude Hold, IAS Hold, Vertical Speed Hold
horizontal -- Roll Attitude Hold
The detent switches are not used for reference adjustment for any FD mode. Instead, they provide
a fly--through function for the pilot. When the spring cartridges in the control stick cause a detent
switch to be activated, control of the aircraft is returned to the pilot. When the detent switch is no
longer active, the FD commands generated (and displayed via the command bars) will provide
guidance to the previously selected flight path with no change to the reference caused from detent
switch activity.
The following paragraphs summarize the inputs required to acquire or maintain the various FD
modes. See sections 6.4.6, 7.9, and 7.12 for details regarding the ARINC 429 information
presented.
Engagement of any FD mode will be inhibited or engaged modes will be disconnected if any of the
following conditions exist:
1. EFIS label 277 bit 25 (ADI valid) indicates ADI is invalid (bit is 0).
2. FD Off Input (label 271 bit 16 from the MSP) is active (bit is 1).
3. The FTR switch for the pilot not selected with the PIC switch is active.
4. EFIS label 324 (Pitch Attitude) is invalid, as indicated by its SSM.
5. EFIS label 325 (Roll Attitude) is invalid, as indicated by its SSM.
Table 5--1 and Table 5--2 indicate the inputs used for the flight director modes. Should one of the
required sensors for a vertical mode become invalid when that mode is engaged, the mode will
disengage and the default vertical mode (PAH) will be engaged if possible. Should one of the
required sensors for a horizontal mode become invalid when that mode is engaged, the mode will
disengage and the default horizontal mode (RAH) will be engaged if possible.
Vertical mode glideslope capture will not occur unless the horizontal mode is in localizer
track.
For vertical acceleration to be valid, the AP processor must receive valid pitch and roll
attitude from the KVG 350 and valid normal acceleration from the KRG 333.
Indicated airspeed must be reasonable (less than 200 knots) for engagement of this
mode.
Legend:
R -- required input to engage mode or maintain mode engagement
D -- desired input, but mode engagement with degraded performance allowed if not present
This mode will be engaged for any of the following reasons if SCAS mode is not inhibited:
A. SCAS button on the MSP is pressed and SCAS mode is not presently engaged.
NOTE
This information can be received by the AP processors in two
ways: (1) SCAS engage discrete input tied directly to the MSP
switch via the aircraft harness, (2) MSP switch information
received via ARINC 429 input to the FD processor and relayed to
the AP processor on the internal bus.
NOTE
Loss of control position synchro information will not result in
disengagement of SCAS mode. But, in this condition the AP
processors in the FCC will attempt to control the aircraft to
maintain attitude rates of zero. This will cause the FCC to oppose
any attempts by the pilot to change the aircraft attitude.
NOTE
If individual failures occur in the primary servo for all three axes,
this will cause SCAS mode to be disengaged in all axes.
Disengagement of SCAS mode in each axis would occur when a
failure was detected in the primary servo for that axis until the
failure in the third axis primary servo would result in
disengagement of SCAS mode altogether.
5.3.2 AP MODE
This mode is entered when the AP button on the MSP is pressed if AP mode is not inhibited.
NOTE
This information can be received by the AP processors in two
ways: (1) AP engage discrete input tied directly to the MSP switch
via the aircraft harness, B. MSP switch information received via
ARINC 429 input to the FD processor and relayed to the AP
processor on the internal bus.
In AP mode, the AP processors control the aircraft to a desired flight path in the pitch and roll axis.
If a FD mode is engaged, the commands received from the FD processor for the pitch axis (vertical
FD mode) and the roll axis (horizontal FD mode) will be used to determine the desired flight path
(within operational limits). If no FD mode is engaged or the system is configured as a SCAS/ATT
system, the AP processors will enter default AP attitude hold mode. In default AP attitude hold mode
the pitch attitude present when AP mode was engaged will be used as a reference and the AP
processors will command the aircraft to maintain the reference pitch attitude or to slew to a desired
pitch attitude with the CBT switch. In default AP attitude hold mode the AP processors will command
the aircraft to maintain a reference roll attitude or to slew to a desired roll attitude with the CBT
switch. When AP mode is engaged, the aircraft rolls to wings level and then reverts to heading hold
when level roll attitude is attained. The cyclic beep trim inputs can then be used to hold a specific
roll attitude if they are beeped beyond 6_ of roll attitude. Any amount less than the 6_ limit will result
in the aircraft rolling back to wings level and reverting to heading hold when the level roll attitude
is attained once again. If IAS or TAS is valid, it can be used to schedule the gains when in default
AP attitude hold mode, thus providing a smoother transition to the reference attitudes at lower
airspeeds. Engagement of AP mode in the pitch and roll axis will be inhibited if information received
from the KRG 333 is invalid or information received from the KVG 350 is invalid.
In AP mode, if airspeed is valid and below 50 knots, the AP processors control the aircraft to
maintain the current heading or to slew to a desired heading with the YBT switch (reference heading
will change at a rate of 3_ per second when slewing). If airspeed is above 50 knots, the AP
processors control the aircraft to maintain a reference lateral acceleration. The reference lateral
acceleration is 0 G, but this value can also be slewed to a new value using the YBT switch.
Engagement of AP mode in the yaw axis will be inhibited if information received from the KRG 333
is invalid, information received from the KVG 350 is invalid, or hydraulic pressure is not valid.
In a SCAS/ATT system, airspeed scheduling of AP command gains is not performed. This is
because the system does not include an air data computer and air data information is not available.
AP mode will be disengaged/inhibited in all axes by the following conditions:
A. AP button on the MSP is pressed.
B. SCAS button on the MSP is pressed.
C. The AFCS DISC switch on the cyclic control for either pilot is pressed.
D. A failure occurs that inhibits AP mode engagement in all axes. In this instance, the AP
FAIL annunciation on the IIDS will be turned on. These failures include loss of validity
from the KRG 333, commanded attitude from the FD processor exceeding +20_/--15_ in
the pitch axis or 31_ in the roll axis (commanded attitude is current attitude plus the FD
command for an axis), internal failures in the FCC, loss of excitation to the KVG 350, a
simultaneous failure of all three primary servo axes, and a simultaneous failure of all three
trim servo axes.
E. Certain force trim system operations are performed, resulting in temporary engagement
of SCAS mode. AP mode will automatically be reengaged when the force trim system
operation is completed. For mode details, see section 5.3.3.
AP mode will be disengaged/inhibited in an individual axis by the following conditions:
A. Hydraulic pressure is not valid -- affects yaw axis only.
B. Primary servo actuator failure detected -- affects axis that has failed primary servo.
C. Trim servo actuator failure detected -- affects axis that has failed trim servo.
D. Rate input from the KRG 333 does not match attitude rate derived from the KVG 350 input
-- affects axis that has the rate miscomparison.
E. Rate or acceleration input from the KRG 333 exceeds control limits -- affects axis that has
the unusual rate or acceleration (i.e., normal acceleration failure would affect pitch axis
only).
F. Acceleration inputs from the KRG 333 invalid -- affects pitch and yaw axes only.
5.3.3 FORCE TRIM SYSTEM INTERACTION WITH AP MODE AND SCAS MODE
The force trim system is monitored by the AP processors. While any of the following conditions exist,
AP mode engagement will be inhibited. Also, if AP mode is engaged when any of the following
conditions occur, AP mode will be disengaged and SCAS mode will temporarily be engaged until
the condition is removed:
A. Force Trim Circuit Breaker not on (AP discrete input port 1, bit 13, set to 1).
B. Cyclic Force Trim Enable not on (AP discrete input port 2, bit 10, set to 1).
C. Cyclic Force Trim Release button pressed (AP discrete input port 2, bit 13, set to 1).
D. Yaw Force Trim Release button pressed (AP discrete input port 2 bit 14, set to 1).
E. Spring cartridge deflection causes a detent switch to be active (registered as Cyclic FTR
for pitch or roll detent and Yaw FTR for yaw detent)
Autotrim occurs in AP mode in an axis when the primary servo is deflected more than 40 % (pitch
and roll axis) or 25 % (yaw axis) of its control authority. The trim servo is turned on and driven in
the direction of the primary servo deflection. Motion of the control system as sensed through the
control position resolver is used to command the primary servo to oppose the motion caused by
the trim servo. A failure of the control position resolver will not prevent AP engagement or autotrim
but will degrade system performance. When a condition requiring autotrim exists continuously for
more than 10 seconds, the AUTOTRIM FAIL annunciation will be turned on.
When AP mode or SCAS mode is engaged, the AP processors will send out a discrete AP ON and
SCAS ON annunciation signal, causing the AP ON or SCAS ON annunciation on the IIDS to be
turned on. In a SCAS/ATT system, this is the only indication to the pilot of engagement of these
modes (although the annunciator above the button corresponding to the engaged mode on the KMS
541 should also be illuminated, this should not be used to verify mode engagement). Also when AP
mode or SCAS mode is engaged, the AP processors will transmit mode engagement information
to the FD processor. The FD processor transmits this information to the MSP on the ARINC 429
bus for annunciation of the mode engagement on the MSP front panel. This annunciation can be
used as a secondary indication of mode engagement.
Engagement of AP mode requires at least one operational control axis (no failures that would affect
AP mode control in an axis -- see section 5.3.2 AP Mode). When AP mode engagement is inhibited
by failures affecting all three axes of operation, the AP FAIL annunciation on the IIDS will be turned
on.
Engagement of SCAS mode requires at least one operational control axis (no failures that would
affect SCAS mode control in an axis -- see section 5.3.1 SCAS Mode). When SCAS mode
engagement is inhibited by failures affecting all three axes of operation, the SCAS FAIL
annunciation on the IIDS will be turned on.
When AP or SCAS mode is engaged and there is a failure that prevents control in an axis, the failure
annunciation corresponding to the failed axis will be annunciated when the mode is engaged. For
pitch axis failures, the PITCH FAIL annunciation on the IIDS will be turned on. For roll axis failures,
the ROLL FAIL annunciation on the IIDS will be turned on. For yaw axis failures, the YAW FAIL
annunciation on the IIDS will be turned on.
If a failure occurs in a sensor that prevents AP or SCAS mode operation in an axis, engagement
of the affected mode is inhibited for the axis(axes) affected. If the sensor information becomes valid
after the failure has occurred, engagement of the previously affected mode in the axis(axes)
affected will be allowed. If a failure occurs in a servo that prevents AP or SCAS mode operation in
an axis, engagement of the affected mode is inhibited for the axis(axes) affected. Reengagement
of the affected mode will be inhibited for the affected axis(axes) until a successful pre--flight test by
the AP processors has been completed.
SECTION VI
REMOTE TERMINAL INTERFACE
6. GENERAL
The FCC provides an RS232 interface for diagnostic and installation capabilities. This interface
should be used for setting up installation parameters for any new installation or when a control
position synchro or linear actuator is replaced in the system. The RS232 interface is provided at
the Ground Maintenance Connector at the cockpit center pedestal. Pin 25 of this connector
provides transmitted data from the FCC, pin 26 is ground, and pin 27 is the receive data input for
the FCC from a terminal.
The terminal should have the following configuration options:
A. 9600 bits per second, 8 data bits, 1 stop bit, no parity bits
B. VT--100 terminal emulation
C. XON/XOFF protocol is used
NOTE
The example screens shown throughout this discussion may
include sample data which will not necessarily be seen by the
user.
Upon initial power--up of the Maintenance processor in the FCC, the message shown in Figure 6--1
will be briefly displayed, followed by the Normal Mode Main Menu screen, shown in Figure 6--2.
KCP 520 Flight Computer
NOTE
If the terminal is turned on after the power is applied to the
maintenance processor, the terminal screen will be redrawn when
the ENTER key is pressed. If this method does not cause a
maintenance screen to appear, refer to section 6.2 Problems
Accessing the Remote Terminal Interface Screens. Whenever a
maintenance screen other than the Normal Mode Main Menu
Screen is active, the Normal Mode Main Menu Screen can be
returned to by continually pressing the ENTER key, pausing long
enough between key presses to allow a new screen to be
displayed on the terminal.
Time at Temperatures
--------------------
Below -65 : 0.0 Between -65 and -55 : 0.0
Between -55 and -45 : 0.0 Between -45 and -35 : 0.0
Between -35 and -25 : 0.0 Between -25 and -15 : 0.0
Between -15 and -5 : 0.0 Between -5 and 5 : 0.0
Between 5 and 15 : 0.0 Between 15 and 25 : 4.4
Between 25 and 35 : 1330.2 Between 35 and 45 : 0.0
Between 45 and 55 : 0.0 Between 55 and 65 : 0.0
Between 65 and 75 : 0.0 Between 75 and 85 : 0.0
Between 85 and 95 : 0.0 Between 95 and 105 : 0.0
Between 105 and 115 : 0.0 Over 115 : 0.0
and recorded in the history every 0.1 hour (6 minutes). A temperature entry of ------ in the history
table indicates that valid temperature data was not received by the maintenance processor at the
time the temperature reading was taken. In the example screen shown, the most recent sample in
the history log is sequence number 60, taken in power cycle number 1164, with a recorded
temperature of 27_ C.
KCP 520 History Log
-------------------
# pwr cyc temp # pwr cyc temp # pwr cyc temp # pwr cyc temp
-- ------- ---- -- ------- ---- -- ------- ---- -- ------- ----
1 1137 28 16 1137 28 31 1146 24 46 1153 26
2 1137 28 17 1137 28 32 1147 24 47 1154 26
3 1137 28 18 1137 28 33 1148 24 48 1155 26
4 1137 28 19 1137 28 34 1149 26 49 1156 25
5 1137 28 20 1137 27 35 1149 26 50 1156 27
6 1137 28 21 1137 27 36 1150 26 51 1156 28
7 1137 28 22 1137 27 37 1150 27 52 1157 26
8 1137 28 23 1138 23 38 1150 26 53 1158 23
9 1137 28 24 1139 24 39 1150 26 54 1159 24
10 1137 28 25 1140 24 40 1150 26 55 1160 24
11 1137 28 26 1141 24 41 1150 26 56 1161 26
12 1137 28 27 1142 ---- 42 1150 26 57 1162 ----
13 1137 28 28 1143 ---- 43 1150 26 58 1163 25
14 1137 28 29 1144 24 44 1151 24 59 1163 27
15 1137 27 30 1145 25 45 1152 23 60 1164 27
Pressing L when the Normal Mode Main Menu screen is displayed will cause the Logged Data
Main Menu screen, as shown in Figure 6--5, to be displayed. Pressing C while the Logged Data
Main Menu screen is displayed will clear all errors stored in non--volatile memory. Pressing R while
the Logged Data Main Menu screen is displayed will clear all errors stored in non--volatile memory
and reset the power cycle number to zero (0). Both of these actions require confirmation by the user
before being performed (a confirmation message is displayed, the user must respond by pressing
Y for yes to confirm that the requested action is desired).
Logged data
-----------
Pressing D when the Logged Data Main Menu screen is displayed will cause the Error Log Dump
screen, similar to Figure 6--6, to be displayed. The top of this screen indicates the total number of
errors stored in non--volatile memory (available for display), the current power cycle number and
the amount of elapsed time between the beginning of the current power cycle and pressing of the
D key to display the Error Log Dump screen (in hours:minutes:seconds format). The power cycle
number is incremented each time the maintenance processor power is cycled or when diagnostic
mode is exited (see section 6.1.5).
The error log dump table displayed on this screen contains one line (row) of information for each
error stored. The most recent error stored in the error log is the last error in the table (has the highest
sequence number). The first column (#) contains the error sequence number. The second column
(Power cycle) contains the power cycle number in which the error occurred and was recorded.
The third column (Delta Time) contains the elapsed time (in hours:minutes:seconds format) since
the beginning of the power cycle in which the error was recorded until the time the error occurred.
The fourth column (Proc) indicates which processor in the FCC detected and logged the error (AP
A is AP processor # 1, AP B is AP processor # 2, FD A is the FD processor, MAI is the maintenance
processor). The fifth column (Error) contains the error number. The sixth column (Description)
contains a brief description of the error. For more details on a particular error logged, see Appendix
A, Error Codes.
A maximum of seventeen (17) errors can be displayed on this screen at any one time. The error
log table may be scrolled one line (row) at a time with the up or down arrow keys, or 17 lines (rows)
at a time with the right or left arrow keys.
Pressing F when the Logged Data Main Menu screen is displayed will allow the user to capture
the logged error code data to a file. When F is pressed the following two lines will appear at the
bottom of the Logged Data Main Menu screen:
Setup for file capture now.
press <CR> to dump error log, any other key to abort.
At this point, the communication program used for the RTI should be configured to receive a file.
Once this is done, the ENTER key should be pressed to start the file transfer. Once the file transfer
is complete (new error log information will stop being scrolled on the display), the file transfer should
be terminated using the communication program. The file set up by the file transfer configuration
will then contain the error log information as text. To return to the Logged Data Main Menu screen,
the ENTER key should be pressed once more.
KCP 520 error log
Number of errors: 55; Current power cycle and delta time: 1164, 00:01:23
up/down arrow: prev/next item; left/right arrow: prev/next page; <CR> to exit
System mode: Normal
In order to enter diagnostic mode, sufficient time must be allowed for the preflight test sequence
to finish, successfully or otherwise. Successful completion of PFT is indicated by the extinguishing
of the AP FAIL light on the IIDS. Unsuccessful completion of PFT will require longer than a
successful completion since the preflight test sequence may be reattempted in the event of an error.
Diagnostic mode is inhibited for the FD processor if FD mode is engaged and for the AP processors
if AP mode or SCAS mode is engaged. Pressing D while the Normal Mode Main Menu is displayed
will bring up the diagnostic mode confirmation message on the terminal (see Figure 6--7). At this
point, the user should type in KCP520 (upper or lower case) without pressing the ENTER key.
Then, to enter diagnostic mode, the Force Trim Release and AP Disconnect switches on the pilot
control stick should be depressed and held and the ENTER key should be pressed. If successful,
the screen shown in Figure 6--8 should be displayed (since the Bell 430 installation does not include
a second FD processor, this message is normal). If this screen does not appear, refer to section
6.3 Problems Entering Diagnostic Mode for more information. At this point, any key can be pressed
to display the Diagnostic Mode Main Menu screen, as shown in Figure 6--9.
NOTE
Pressing the ENTER key at the Diagnostic Mode Main Menu
screen will cause diagnostic mode to be exited. Also, if sensed
collective position changes too much (25 % of travel from stop to
stop on collective position resolver) when in diagnostic mode,
diagnostic mode will be exited. Sensed collective position change
can also be caused by loss of excitation power to the collective
position resolver or collective position detection circuitry missing.
The AP and SCAS buttons on the MSP should be depressed
when changing collective position to remain in diagnostic mode.
When diagnostic mode is exited in the AP processors, normal
mode will be entered and the pre--flight test sequence will be
initiated.
KCP 520 Flight Computer
-----------------------
FD B
Diagnostic mode
---------------
A - Automated tests
M - Manual tests
I - Setup installation
L - Logged data
S - Software identification
D - Download AP dump & engage data
P - Primitive interface
Pressing A when the Diagnostic Mode Main Menu screen is displayed will cause the Automated
Test Selection screen, shown in Figure 6--10, to be displayed. Pressing the ENTER key at this point
will return the user to the Diagnostic Mode Main Menu screen. Pressing a key corresponding to a
particular test on the Automated Test Selection screen will cause that test to be performed for all
applicable processors in the FCC.
Pressing A when the Automated Test Selection screen is displayed will cause the processors to
sequence through all of the automated tests listed. It will take about 2 minutes to perform all of the
automated tests, most of which only test circuits internal to the FCC. At the end of the test sequence,
a screen similar to the one shown in Figure 6--11 should appear. Pressing any key at this point will
return the user to the Automated Test Selection screen.
R - Test ROM
M - Test RAM
N - Test non-volatile memory
T - Test timers
D - Test DMA
C - Test CPU
S - Test serial I/O (IP bus)
4 - Test ARINC 429 I/O - internal
P - Test power supply
F - Test configuration module
A - Sequence through all tests
Pressing M when the Diagnostic Mode Main Menu screen is displayed will cause the Manual Test
Selection screen, shown in Figure 6--12, to be displayed. Pressing the ENTER key at this point will
return the user to the Diagnostic Mode Main Menu screen. Pressing a key corresponding to a
particular test on the Manual Test Selection screen will cause that test to be performed for all
applicable processors in the FCC.
System mode: Diagnostic
Selected processors: AP A, AP B, FD A, MAI
D - Discrete I/O
4 - ARINC 429 I/O
A - Analog I/O
Select processor
----------------
A - Autopilots
1 - Autopilot A
2 - Autopilot B
F - Flight directors
M - Maintenance
Select processor
----------------
A - Autopilots
1 - Autopilot A
2 - Autopilot B
F - Flight directors
M - Maintenance
output, which will be output once the ENTER key is pressed. The output value entered has a range
of --1 to +1, corresponding to an output voltage of --10 VDC to +10 VDC (i.e., if an output voltage
of +3.25 VDC is desired, a value of 0.325 should be entered).
Eight analog input values are displayed on the right side of the analog input/output screen at any
one time. The legend above the group of columns for analog inputs indicates which AP processor
input is being displayed and which MUX is being monitored. Pressing P will change the AP
processor selection (i.e., if inputs from AP A are being displayed, the inputs from AP B will be
displayed when P is pressed). The first column in the input section of the screen indicates the
number of the MUX channel input being displayed. The value directly to the right of the channel
number is the raw data input (in hexadecimal). A raw data input value of 000 indicates the input is
at --10 VDC, 800 indicates the input is at 0 VDC, and FFF indicates the input is at +10 VDC. The
last column in the input section of the screen displays the converted input value. This value will
either be the raw input voltage for the input or the input value as scaled by the AP processor (in
Figure 6--17, the scaled input value is being displayed and the value for MUX 0 input 1 has been
converted to 0 amps). Display of analog input values can be toggled between the raw input voltage
display and the scaled input value display by pressing T. To select a particular MUX to monitor,
the number key corresponding to the MUX should be pressed (i.e., to select MUX 3, press the 3
key). There are 6 input multiplexers numbered from 0 through 5. Each MUX has sixteen (16) analog
inputs, displayed on the screen by one--half of the inputs at a time (inputs 0 to 7 or inputs 8 to 15).
To switch between which half of the MUX inputs are being displayed for a particular MUX, the
number key for the MUX should be pressed again (i.e., if the display is showing inputs 8 to 15 for
MUX 4, pressing the 4 key will cause the screen to display inputs 0 to 7 for MUX 4).
System mode: Diagnostic
Selected processors: AP A, AP B
>: selected output; a, b: no response; *: stale data
sample AP processor ARINC 429 input/output screen, which is navigated similarly to the FD
processor screen, as described in the following paragraph. This screen shows the current values
being output to the ARINC 429 outputs for the selected processor(s), which can be changed by the
user. It also displays which ARINC 429 input information for one received label, which can be
changed by the user, per ARINC 429 input channel. Pressing ENTER when this screen is
displayed returns the user to the Manual Test Selection screen.
The left side of the ARINC 429 input/output screen displays information about the ARINC 429
outputs and the ARINC 429 wraparound that is internal to the FCC. The top half of the left side
displays information about the ARINC 429 outputs from the FCC. There is one line for each output
channel for all the ARINC 429 chips available (for the FD processor, there are two ARINC 429 chips,
labeled as ASIC 0 and ASIC 1), with one output channel per chip. Each line indicates the chip
number (ASIC 0 or ASIC 1) followed by raw data being output on that channel for the last label for
which information was entered. The ARINC 429 wraparound information and output baud rate
section is located underneath the output information section. It indicates which output channels are
currently enabled for loopback of output information to all input channels on the same ARINC 429
chip, and whether the selected baud rate is HI or LO (HI is 100 kilohertz, LO is 12.5 kilohertz).
Pressing S moves the > next to the output list to select the desired output channel to change
output information. Once the desired output channel is indicated with the >, pressing V will allow
the user to enter a hexadecimal value to be continuously output on the selected output. This value
will have the label information encoded in it. The C key cycles the output value through the values
of 000000, 555555, AAAAAA, and FFFFFF (all hexadecimal). The W key performs a walking one
bit through the output value (all bits 0, then a 1 bit is placed in the least significant bit and shifted
through one bit at a time to the most significant bit each time the key is pressed, the performs a
walking zero bit through the output value (all bits 1, then a 0 is placed in the least significant bit
and shifted through one bit at a time to the most significant bit each time the key is pressed).
Pressing E toggles the wraparound enable for the selected output from enabled to disabled.
Pressing B toggles the baud rate for the selected output from LO to HI.
The right side of the ARINC 429 input/output screen displays information about the ARINC 429
inputs to the FCC. The legend at the top of the inputs section indicates which processor inputs are
being displayed. For each processor, there is one line for each input channel for all the ARINC 429
chips available (for the FD processor, there are two ARINC 429 chips, labeled as ASIC 0 and ASIC
1), with four input channels per chip. Each line indicates the chip number (ASIC 0 or ASIC 1), then
the channel number designated with a ch, followed by the raw input value for the channel in
hexadecimal. If there is no information received on an input channel, the value is indicated as
------------. If no new information is received from a channel within one second, the displayed value
is preceded by a * to indicate the data displayed is not fresh. Pressing I moves the > next to
the input list to select the desired input channel to monitor a certain label on. Once the desired input
channel is indicated with the >, pressing L will allow the user to enter the label to be monitored
for that channel. The label should be entered as a 3--digit octal number with leading 0s if necessary
(i.e., enter 053 if label 53 is desired) followed by pressing the ENTER key to start reception of the
requested label only. If monitoring of all labels received on a channel is desired, the channel should
be selected (using I) and then pressing M will toggle between label match (receiving only the label
entered in) and no label match, with label match indicated by an m following the channel number
on the display.
Figure 6--19 shows the result of setting up the ARINC 429 input/output for the AP processors. AP
A processor ASIC 0 channel 2 was set up for label match to receive label 204 from the air data
system. AP B processor ASIC 0 channel 2 was set up for label match to receive label 207 from the
air data system.
General interpretation of ARINC 429 information displayed in hexadecimal form can be found in
Table 6--1, Table 6--2, and Table 6--3. Information for a hexadecimal ARINC 429 word can be
interpreted using the information in Table 6--1. Bits 30 and 31 of the ARINC 429 word make up the
Sign Status Matrix (SSM), which can be interpreted using Table 6--2. Conversion of any
Hexadecimal digit to its binary equivalent can be accomplished using Table 6--3.
Section 6.4.6 contains general information about the ARINC 429 inputs/outputs for the FCC. For
information regarding the specific ARINC 429 information expected for each FCC input, refer to one
of the following sections as appropriate for the interface (i.e., ARINC 429 input channel) being
tested :
A. Section 7.9, Interface with the MSP, and section 7.10, Cockpit Switches Interface, for the
MSP.
B. Section 7.11, Air Data Interface, for the KDC 481 Air Data Computer.
C. Section 7.12, EFIS Interface, for the EFIS.
Bit Number 3 3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0
2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1
Bit Value (binary values) p S S s d d d d d d d d d d d d d d d d d d i i L L L L L L L L
Bit Value (discrete word) p S S d d d d d d d d d d d d d d d d d d d i i L L L L L L L L
Legend :
p -- parity bit set so that the word has an odd number of 1 bits.
d -- data field bits, varies depending on data type.
S --Sign Status Matrix bits (see table below for explanation of SSM)
s -- sign bit: 0 indicates plus, up, right, north, east; 1 indicates minus, down, left, south,
west
i -- source/destination index code
L -- ARINC 429 label. An ARINC 429 label is normally expressed as an octal value. This value
is converted to binary and coded in the label field in reverse order.
For example : Label 207 is binary 10 000 111. This would be coded in bits 8 through 1
of the ARINC 429 word as 1110 0001 (hexadecimal value of E1 -- this would be seen on
diagnostic screen as the label received)
Binary equivalent
Hexadecimal Most Least
digit significant bit significant bit
0 0 0 0 0
1 0 0 0 1
2 0 0 1 0
3 0 0 1 1
4 0 1 0 0
5 0 1 0 1
6 0 1 1 0
7 0 1 1 1
8 1 0 0 0
9 1 0 0 1
A 1 0 1 0
B 1 0 1 1
C 1 1 0 0
D 1 1 0 1
E 1 1 1 0
F 1 1 1 1
TABLE 6--3 Conversion of Hexadecimal to Binary
screen without saving. When S is pressed, an Installation data saved OK message will be
displayed at the top of screen when saving of installation data is complete. Pressing ENTER when
this screen is displayed returns the user to the Installation Processor Selection screen.
NOTE
Failure to save installation data to the configuration module (by
pressing S) may cause incorrect operation of the FCC.
System mode: Diagnostic
Selected processor: FD A
Installation setup
------------------
>EFIS configuration
JAR AWO
NOTE
Failure to save installation data to the configuration module (by
pressing S) may cause incorrect operation of the FCC.
Particularly, pre--flight test will probably fail if LVDT position
information is not updated when a linear actuator is replaced or
control position information is not updated when a control position
resolver is replaced.
Installation setup
------------------
>Audio volume
Audio frequency
JAR AWO
3-axis FD/AP
LVDT position
Collective position
Pitch cyclic position
Roll cyclic position
Pedal position
NOTE
Installation data should be saved to the configuration module (as
described in section 6.1.5.3.2) when LVDT position information for
the linear servos is updated.
Installation setup
------------------
Audio volume
Audio frequency
JAR AWO
3-axis FD/AP
>LVDT position
Collective position
Pitch cyclic position
Roll cyclic position
Pedal position
NOTE
Moving the Collective position will cause an exit of diagnostic
mode. Therefore, when collective position is being installed, it is
required that the AP and SCAS buttons be pressed on the MSP
when collective is being moved to prevent premature exit of
diagnostic mode.
NOTE
Installation data should be saved to the configuration module (as
described in section 6.1.5.3.2) when control position information is
updated.
Installation setup
------------------
Audio volume
Audio frequency
JAR AWO
3-axis FD/AP
LVDT position
>Collective position
Pitch cyclic position
Roll cyclic position
Pedal position
A - Autopilot A
B - Autopilot B
FIGURE 6--25 Data Dump Processor Selection Screen (no processors selected)
System mode: Diagnostic
Selected processor: AP A
Select processor
----------------
A - Autopilot A
B - Autopilot B
FIGURE 6--26 Data Dump Processor Selection Screen (AP A processor selected)
System mode: Diagnostic
Selected processor: AP A
Press any key to download AP dump and engage data, <ESC> to abort
The Logged Data Screens detailed in section 6.1.4, Logged Data Screens, can be accessed directly
from the Diagnostic Mode Main Menu screen by pressing the L key as they are accessed from the
Normal Mode Main Menu screen.
When the Logged Data Main Menu screen is displayed, the F key can be pressed to allow file
capture of logged error data information to a file if requested, using a similar interface with the
terminal emulation software as described in section 6.1.5.4, Diagnostic Information Screens. The
F key can also be used for capturing the history log and Time and Temperature log as well. Section
6.1.4 contains a more detailed description of how to capture the logged error data information to
a file. The history log and Time and Temperature log can be captured to a file in a similar manner.
AP A
AP B
FD A
and
The FD processor can be made to go into diagnostic mode by itself when there is no power to the
AP processors. In this instance, the maintenance processor will not receive any information from
the AP processors on the internal bus and allow the FD processor to go into diagnostic mode alone.
The FD processor monitors the switch information received from the MSP, so the Force Trim
Release and AP Disconnect switches must still be depressed when entering diagnostic mode.
The FD processor can enter diagnostic mode without pressing the Force Trim Release and AP
Disconnect switches if the bench strap for the FD processor is active. This can be accomplished
by connecting pins 32 and 23 on the diagnostic connector under the cover plate on the front of the
FCC. When diagnostic mode is entered in this manner, executing the automated test of the
configuration module will perform an 80 second test on the interface between the FCC and the
configuration module. Interruption of this test will corrupt the data stored in the configuration
module, thus requiring installation to be performed again to restore configuration module
information. See section 6.1.5.3 for more information on the installation screens.
When the AP processors are locked out of diagnostic mode (i.e., no power to AP processors), the
signal voltages listed in Table 6--4 may be monitored for correctness. Due to switch interconnects
in the harness, the first two items in Table 6--4 should be verified in the order listed.
Signal / Condition Measurement point
Force Trim Circuit Breaker FCC connector section B, pin 56 = 28 VDC
ON
Cyclic FTR FCC connector section A, 28 VDC not present at
pin 103 when switch pressed
AFCS Disconnect FCC connector section B, 28 VDC not present at
pin 30 when switch pressed
TABLE 6--4 Signals to Monitor for FD Processor Only Diagnostic Mode
The AP Processor Discrete Inputs are listed in Table 6--5 and some are part of Figure 5--2. For
open/ground signals, ground is interpreted as a 1 and open is interpreted as a 0 by the FCC. For
28 VDC/open signals, 28V is interpreted as a 0 and open is interpreted as a 1 by the FCC. Where
applicable, unit pins are shown in brackets in the table with a format of [section letter -- pin
number].
bit port A port 0 port 1 port 2 port 3
0 [output] GA Engage Perf Strap 0 RALT1 Strap [spare] (re-
[9A1P1--A104] [9A1P1--A46] (reserved) served)
(gnd = not (normally open)
pressed)
1 [output] YD Engage (re- Perf Strap 1 RALT2 Strap [spare] (re-
served) [9A1P1--A45] (reserved) served)
(gnd)
2 [output] AP Engage Perf Strap 2 RALT1 Valid [spare] (re-
Pressed [9A1P1--A71] [9A1P1--A93] served)
[9A1P1--A64] (normally open) (28VDC)
(gnd)
3 [output] SCAS Engage Perf Strap 3 RALT2 Valid RG Valid (re-
Pressed [9A1P1--A73] (reserved) served)
[9A1P1--A106] (normally open)
(gnd)
4 proc ID0: COLL Engage Perf Strap 4 VG1 Valid AP Valid
AP A=0, AP (reserved) [9A1P1--A75] [9A1P1--A51]
B=1 (normally open) (28 VDC)
5 proc ID1: AP Disconnect KRG 333 Rate VG2 Valid (re- Pitch Trim
AP A=1, AP [9A1P1--B30] Valid served) Clutch Current
B=0 (28VDC = not [9A1P1--A79] (reserved)
pressed) (gnd)
6 [spare] YD Disconnect PFT Switch DG Valid Roll Trim Clutch
(reserved) Pressed [9A1P1--A50] Current (re-
[9A1P1--A77] (28 VDC) served)
(gnd)
7 brownout de- SCAS Discon- spare (re- KRG 333 Accel Yaw Trim
tector nect (reserved) served) Valid Clutch Current
[9A1P1--A47] (reserved)
(gnd)
8 not available AP Disable (nor- spare (re- [spare] (re- Collective
mally open) served) served) Clutch Current
(reserved)
9 not available YD Disable (re- FD SELECT [spare] (re- Pitch Brake
served) (reserved) served) Current
10 not available COLL Disable DIO_IN1 (re- Cyclic FTE Roll Brake Cur-
(reserved) served) [9A1P1--A103] rent
(28 VDC = cy-
clic FTR not ac-
tivated and FTE
switch on)
11 not available Audio Reset DIO_IN2 (re- Yaw FTE Yaw Brake Cur-
served) [9A1P1--A101] rent
(28 VDC = yaw
FTR not acti-
vated and FTE
switch on)
12 not available AP Disc Reset DIO_IN3 (re- Coll FTE (re- Pitch Trim
(reserved) served) served) Brake Current
13 not available Yaw Interrupt (re- Force Trim CB Cyclic FTR Roll Trim Brake
served) On [9A1P1--A102] Current
[9A1P1--B56] (28 VDC = cy-
(28VDC) clic detent not
activated)
14 not available DIO_IN4 (re- PC1 Hydraulics Yaw FTR Yaw Trim Brake
served) Pressure [9A1P1--B18] Current
[9A1P1--B47] (28 VDC = yaw
(gnd) detent not acti-
vated)
15 not available DIO_IN5 (re- [spare] (re- Coll FTR (re- Collective
served) served) served) Brake Current
(reserved)
TABLE 6--5 AP Processor Discrete Inputs
The FD Processor Discrete Inputs and Outputs are listed in Table 6--7 and the Pilot In Command
selection input is shown as a part of Figure 5--2. Bits 0 to 3 of Port A are designated as outputs and
bits 4 to 7 of Port A are designated as inputs. Port 0 is used as a discrete input port. Where
applicable, unit pins are shown in brackets in the table with a format of [section letter -- pin
number].
Bit Port A Port 0
0 (reserved output) (reserved spare input)
1 (reserved output) (reserved spare input)
2 (reserved output) (reserved spare input)
3 (reserved output) (reserved spare input)
4 Processor ID = 1 (reserved spare input)
5 Processor ID = 0 (reserved spare input)
6 Power Supply Valid (reserved spare input)
7 (reserved input) (reserved spare input)
8 (not available) (reserved spare input)
9 (not available) (reserved spare input)
10 (not available) (reserved spare input)
11 (not available) Pilot In Command Select
Left =1 Right = 0 [B--27]
12 (not available) (reserved spare input)
13 (not available) (reserved spare input)
14 (not available) (reserved spare input)
15 (not available) (reserved spare input)
TABLE 6--7 FD Processor Discrete Inputs/Outputs
The AP Processor Analog Inputs are listed in Table 6--8. These inputs are available to both AP
processors. There are 96 possible analog inputs, with 16 inputs per input MUX. Therefore, the
analog input information is organized as channel 0 to 15 for each MUX (labeled 0 to 5).
MU Channel Signal Name MUX Channel Signal Name
X
0 0 Pitch Servo Voltage 3 0 Pitch Control Position COS
1 Pitch Servo Current 1 Pitch Control Position SIN
2 Pitch Position Rate 2 Roll Control Position COS
3 Pitch Position 3 Roll Control Position SIN
4 Pitch Servo Command 4 Yaw Control Position COS
5 Roll Servo Voltage 5 Yaw Control Position SIN
6 Roll Servo Current 6 Collective Control Position COS
7 Roll Position Rate 7 Collective Control Position SIN
8 Roll Position 8 VG1 Pitch
9 Roll Servo Command 9 VG1 Pitch Rate
10 Yaw Servo Voltage 10 VG1 Roll
0 spare (reserved)
1 Yaw servo position (reserved)
2 Roll servo position (reserved)
3 Pitch servo position (reserved)
4 spare (reserved)
5 spare (reserved)
6 spare (reserved)
7 spare (reserved)
8 DAC Test Channel 14 of MUX 0
9 Yaw Servo Position Command Channel 0 of MUX 1
10 Roll Servo Position Command Channel 9 of MUX 0
11 Pitch Servo Position Command Channel 4 of MUX 0
12 Collective Command (re-
served)
13 Yaw Trim Servo Voltage Com- Channel 9 of MUX 1
mand
14 Roll Trim Servo Voltage Com- Channel 6 of MUX 1
mand
15 Pitch Trim Servo Voltage Com- Channel 3 of MUX 1
mand
TABLE 6--9 AP PROCESSOR ANALOG OUTPUTS
The FD processor has the capability of receiving ARINC 429 information from eight different
sources, since the FD processor has two ARINC 429 chips with four receivers each. The two ARINC
429 chips for the FD processor are labeled as ASIC 0 and ASIC 1. The four inputs channels from
ASIC 0 are not used in the Bell 430 installation. All four input channels of ASIC 1 can be used with
the Bell 430 as follows:
A. Channel 0 is connected to the MSP bus to receive mode request information from the
MSP.
B. Channel 1 is connected to the pilot side EFIS bus to receive heading/navigation source
information in a FD/SCAS/AP system (it is not used in a SCAS/ATT system).
C. Channel 2 is connected to the co--pilot side EFIS bus to receive heading/navigation
source information in a FD/SCAS/AP system with 4--tube EFIS (it is not used in a
FD/SCAS/AP system with 2--tube EFIS or in a SCAS/ATT system).
D. Channel 3 is connected to the air data bus to receive air data information in a
FD/SCAS/AP system (it is not used in a SCAS/ATT system).
The FD processor has the capability of transmitting ARINC 429 information on two output channels,
one per ARINC 429 chip. The output channel on ASIC 1 is not used in the Bell 430 installation. The
output channel on ASIC 0 is used to transmit mode acknowledgment information to the MSP and
mode engagement/command bar information to the EFIS (if available). Even though the
information is transmitted from one ARINC 429 transmit channel, it is buffered to two separate
outputs for transmission to the MSP and EFIS.
NOTE
Installation information is stored in non--volatile storage in the
configuration module. Therefore, installation only needs to be
performed when a linear actuator or a control position resolver is
replaced in the system.
SECTION VII
MAINTENANCE
Setting output port A, bit 0, for the AP processors to a value of 0 will inhibit normal operation of the
servos. Also, normal operation of the lo side brake and enable of the servo amplifier will be inhibited
when the AFCS Disconnect switch is pressed. This condition will cause the midpoint voltage
monitor described in the previous paragraph to trip.
NOTE
To prevent nuisance monitor failures from occurring when in
diagnostic mode, it is recommended that any changes to discrete
outputs be done on both AP processors simultaneously (press A
at the Processor Selection Screen to select both AP processors).
The input/output ports associated with the primary servos are summarized in Table 7--2 for easy
reference. Setting the Servo Amplifier Power bit to 1 turns on the servo amplifier. When the servo
amplifier is powered, the LVDT Sense value should increase to above 0.5 VDC, thus verifying that
the excitation voltage is present at the servo actuator LVDT primary and the LVDT secondary is
connected back to the servo amplifier. The LVDT excitation signal is a nominal 1.7 VRMS at 3.5
kilohertz referenced to approximately of the 28 VDC supply. The LVDT excitation signal can be
measured between pins M and N of the servo actuator connector.
If the Servo Amplifier Power bit is 0, the Midpoint Voltage value for the servo should be near 0 volts.
When the Servo Amplifier Power bit is 1, the Midpoint Voltage value for the servo should be at one
of the following levels:
(1) Approximately the value of the aircraft 28 VDC power (AP processor analog input MUX
2 channel 1) if the Brake Solenoid Lo--Side is not turned on. In this case, the motor drive
lines measurable at pins A and B of the servo actuator connector should correspond to
the 28 VDC supply power reading with respect to aircraft ground.
(2) Approximately the value of the aircraft 28 VDC power (AP processor analog input MUX
2 channel 1) if the Brake Solenoid Lo--Side is turned on. In this case, the motor drive lines
measurable at pins A and B of the servo actuator connector should vary between ground
and the 28 VDC supply power reading with respect to aircraft ground depending on the
drive condition. Servo drive condition is determined by the command and position signals
to the servo amplifier.
The Brake Solenoid Lo--Side also activates the drive on the ground side of the servo actuator brake
solenoid. The Brake Solenoid Hi--Side activates the supply side of the actuator brake solenoid.
When the Brake Solenoid Hi--Side is turned on, the supply side of the actuator brake solenoid will
have the 28 VDC supply power applied to it. When the Brake Solenoid Lo--Side and Brake Solenoid
Hi--Side are both turned on and the current path through the brake solenoid is complete, the Brake
Current Monitor Bit will become a 1. When the Brake Solenoid Lo--Side and Brake Solenoid
Hi--Side are both turned off, the voltage measured at the Lo and Hi side Brake output pins will be
approximately of the 28 VDC aircraft supply voltage when the servo is connected in the harness.
Any value entered for the Position Command Output Channel for a servo (in the range of --1 to +1
on the AP processor analog input/output screen) should be reflected on the Command Monitor input
channel listed in the table. The value reflected on the input should be 10 times the value entered
for the output (i.e., an output value of --0.25 should be reflected on the input as -- 2.5 volts when
looking at raw data). If the Servo Amplifier Power is turned on and the Brake Solenoid Lo--Side and
Brake Solenoid Hi--Side are on, the LVDT Position value in volts should be approximately the same
as the value seen at the Command Monitor input when the servo is commanded to a position
between its mechanical stops. The range of values between a mechanical stop for a servo is from
+5.75 VDC (nominal) for the retracted stop of the servo and the value indicated in the table for the
extended stop of the servo. If the servo is commanded to a position outside of its mechanical stop
range, the servo should reach a mechanical stop and the magnitude of Servo Voltage and Servo
Current values should increase due to the error difference between commanded position for the
servo and actual LVDT position. A similar error can occur when commanding within the mechanical
stop range if the Brake Solenoid Hi--Side is off.
NOTE
For more information on navigating the AP Processor Discrete
Input/Output screen, see section 6.1.5.2.2. For more information
on navigating the AP Processor Analog Input/Output screen, see
section 6.1.5.2.3.
Nominal motor stall current with 25 VDC of servo amplifier drive voltage is 1.2 amps.
Figure 7--1 shows a portion of the AP Processor Discrete Input/Output screen with the Pitch Servo
Amplifier powered and the Brake Solenoid Lo--Side and Brake Solenoid Hi--Side on to release the
brake. The Brake Current Monitor bit has been bolded in the figure for ease of reference. Figure
7--2 shows a portion of the AP Processor Analog Input/Output screen with the pitch primary servo
activated and the position commanded beyond the retracted stop, thus causing an error voltage to
be produced on input channel 0 and an error current to be produced on input channel 1. Figure 7--3
shows the same screen after T was pressed. Note that the commanded position value in channel
4 is larger than the LVDT position value in channel 3 since that command is beyond the stop range.
NOTE
If the primary servos have been pre--positioned for aircraft control
rigging purposes, then the rigging should be completed before any
testing which disturbs this positioning is performed. Also, it is
recommended that the primary servos be repositioned to the
center values shown in Table 7--2 after testing is completed.
Before depowering the servo channel and re--engaging the servo
brake, select the appropriate Position Command Output Channel
and type in one--tenth the value for LVDT Position Voltage at
Center from the table (i.e. 0.27 for pitch and roll) and verify from
the LVDT Position Voltage that the servo has repositioned.
An example sequence for testing the pitch primary servo for proper operation is presented below.
Similar operations can be performed for the roll or yaw primary servo to verify proper operation of
those servos.
(1) Verify servo amplifier is not powered and not selected (set discrete output ports 0, 1, and
2 to a value of 0).
(2) Verify that the servo midpoint voltage read in is 0 volts (analog input MUX 2, channel 2)
and the LVDT sense input is below 0.5 VDC (analog input MUX 0, channel 15) and the
servo brake is engaged (discrete input port 3, bit 9 should be 0).
(3) Power the servo (set discrete output port 2 to a value of 0010).
(4) Record the value for the +28 VDC power input value (analog input MUX 2, channel 1).
(5) Verify that the servo midpoint voltage read in is near the value recorded for + 28 VDC
power input (analog input MUX 2, channel 2) and the LVDT sense input is above 0.5 VDC
(analog input MUX 0, channel 15).
(6) Select the servo by setting the brake solenoid lo side output (set discrete output port 1
to a value of 0001).
(7) Verify that the servo midpoint voltage read in is near of the value recorded for + 28 VDC
power input (analog input MUX 2, channel 2) and the servo brake remains engaged
(discrete input port 3, bit 9 should be 0).
(8) Disengage the servo brake by setting the brake solenoid hi side output (set discrete
output port 0 to a value of 0010).
(9) Verify that the servo brake is released (discrete input port 3, bit 9 should be 1).
(10) Command the servo to a position of 1.5 volts (set analog output 11 to a value of 0.15).
(11) Verify the servo command input is approximately 1.5 volts (analog input MUX 0, channel
4 should be 1.5 volts when viewed as raw data), the servo position is approximately 1.5
volts (analog input MUX 0, channel 3 should be 1.5 volts when viewed as raw data), and
servo current is near 0 amps (analog input MUX 0, channel 1).
(12) Command the servo to a position of 7 volts (set analog output 11 to a value of 0.7).
(13) Verify the servo command input is approximately 7 volts (analog input MUX 0, channel
4 should be 7 volts when viewed as raw data), the servo position is approximately 5.75
volts (analog input MUX 0, channel 3 should be 5.75 volts when viewed as raw data), and
absolute servo current is greater than 1.0 amp.
(14) Command the servo to a position of 0.0 volts (set analog output 11 to a value of 0.0).
(15) Verify the servo command input is approximately 0 volts (analog input MUX 0, channel
4 should be 0 volts when viewed as raw data), the servo position is approximately 0 volts
(analog input MUX 0, channel 3 should be 0 volts when viewed as raw data), and servo
current is near 0 amps (analog input MUX 0, channel 1).
(16) Deselect the servo amp by clearing the brake solenoid lo side output (set discrete output
port 1 to a value of 0000).
(17) Verify that the servo brake is engaged (discrete input port 3, bit 9 should be 0).
This sequence of test steps can be used to verify that the servo is moving when commanded and
the brake is released. It also verifies that the servo amplifier bridge is outputting proper voltage
values to the servo and that the servo brake is operating correctly.
The input/output ports associated with the trim servos are summarized in Table 7--3 for easy
reference. Operation of trim servos is similar to operation of the primary servos, as discussed in
section 7.2.1 Primary Servo Axis Interfaces, except that there is no LVDT position feedback.
Therefore, servo command is a drive voltage command instead of a position command.
Nominal motor stall current with 26 VDC of servo amplifier drive voltage is 0.12 amps.
Pitch Trim Roll Trim Yaw Trim
Axis Axis Axis
Discrete Input/Output
Servo Amplifier Power Out Port 0, 8000 Out Port 2, 0008 Out Port 2, 0080
Brake Solenoid Lo--Side Out Port 1, 0100 Out Port 1, 0200 Out Port 1, 0400
Brake Solenoid Hi--Side Out Port 0, 0800 Out Port 0, 1000 Out Port 0, 2000
Brake Current Monitor In Port 3, Bit 12 In Port 3, Bit 13 In Port 3, Bit 14
Analog Input/Output
Position Command Out- Output Output Output
put Channel Channel 15 Channel 14 Channel 13
Command Monitor Mux 1, Ch 3 Mux 1, Ch 6 Mux 1, Ch 9
Servo Amplifier Voltage Mux 1, Ch 1 Mux 1, Ch 4 Mux 1, Ch 7
Servo Current Mux 1, Ch 2 Mux 1, Ch 5 Mux 1, Ch 8
Midpoint Voltage Mux 2, Ch 5 Mux 2, Ch 6 Mux 2, Ch 7
To turn on both Pitch Trim Servo Amplifier Power and Brake Solenoid Hi--Side, set Output Port 0
to 8800.
The AP processor discrete output port values that are required to illuminate or extinguish the cockpit
discrete visual annunciators are listed in Table 7--4.
Discrete Output Value Value to Port value to illumi-
to nate
Annunciation Port Bit illumi- extinguish individually
nate
AFCS DISCONNECT 0 10 0 1 0000
(IIDS)
AP FAIL (IIDS) 1 12 0 1 8000
AP ON 1 13 1 0 B000
SCAS ON 1 14 1 0 D000
SCAS FAIL (IIDS) 1 15 0 1 1000
AUTOTRIM FAIL (IIDS) 2 1 0 1 0004
PITCH FAIL (IIDS) 2 2 0 1 0002
ROLL FAIL (IIDS) 3 0 0 1 0002
YAW FAIL (IIDS) 3 1 0 1 0001
These outputs are all open/ground. Therefore, a 1 indicates that the output is grounded and a
0 indicates that the output is open.
Port 0 Port 1 Port 2 Port 3
Turn all annunciations off 0400 9000 0006 0003
Turn all annunciations on 0000 6000 0000 0000
The control position resolver analog inputs channels are all located on AP processor analog input
MUX 3 as detailed in Table 7--5. Resolver position angle is obtained by trigonometric calculations
using both the Sin and Cos values of the angle. For any of the resolver position angle inputs to be
present, the excitation reference voltage of 26 VAC nominal must be present at both the resolver
and the FCC. The reference input to the FCC may be monitored at AP processor analog input MUX
5 channel 1. The scaled value next to the COS input for each resolver on the AP processor analog
input/output screen (channels 0, 2, 4, and 6) corresponds to the resolver mechanical angle. The
scaled value next to the SIN input for each resolver on the AP processor analog input/output screen
(channels 1, 3, 5, and 7) corresponds to the equivalent control surface movement. If installation of
the control position resolvers has not been performed (see sections 6.1.5.3 and 6.1.5.3.4) the
control surface values will be invalid and should be ignored. If the raw value of the SIN and COS
inputs for the control position resolvers is displayed (see section 6.1.5.2.3), the voltage input for the
SIN and COS is displayed. As a control is moved, both the SIN and COS signals will change for that
control. Due to the nature of the trigonometric functions, the SIN and COS values will change most
rapidly when the value is near zero.
NOTE
To verify activity on both the SIN and COS inputs for a control
position resolver, it is recommended that the control should be
moved throughout its entire range of motion so that changes can
be detected for both inputs.
Channel # Signal Description/Notes
0 Pitch Control Position COS scaled value shows resolver mechanical angle
1 Pitch Control Position SIN
2 Roll Control Position COS scaled value shows resolver mechanical angle
3 Roll Control Position SIN
4 Yaw Control Position COS scaled value shows resolver mechanical angle
5 Yaw Control Position SIN
6 Collective Control Position COS scaled value shows resolver mechanical angle
7 Collective Control Position SIN
NOTE
The derived pitch and roll attitude rates are used in the AP
processor during normal mode for monitoring purposes. These
rates are compared with the rates received from the KRG 333 for
reasonability.
MUX # Channel # Signal Name
3 8 VG1 Pitch Attitude
3 9 VG1 Pitch Rate
3 10 VG1 Roll Attitude
3 11 VG1 Roll Rate
NOTE
Someof thecockpit switchstates arealso readin bythe MSPand
transmitted to the FCC on the MSP ARINC 429 bus. These
ARINC 429 inputs can also be monitored to determine cockpit
switch input states (see section 7.9 Interface with the MSP).
Loss of the Force Trim Circuit breaker will cause 28 VDC to be removed from the Force Trim Circuit
Breaker, the Cyclic Force Trim Enable, the Yaw Force Trim Enable, and the Trim Release inputs.
Activating Cyclic FTR will cause 28 VDC to be removed from the Cyclic FTR and the Cyclic FTE.
Moving the cyclic control with the force trim system engaged will result in opening of the cyclic detent
switch, thus removing 28 VDC from the Cyclic FTR. Activating Yaw FTR will cause 28 VDC to be
removed from the Yaw FTR and the Yaw FTE. Moving the pedals with the force trim system
engaged will result in opening of the yaw detent switch, thus removing 28 VDC from the Yaw FTR.
Turning the Force Trim Power switch off results in removal of 28 VDC from the Yaw FTE and the
Cyclic FTE. For more information about the Force Trim system controls, refer to section 5.1.6.
Switch Name AP Processor Discrete In- State information
put
Go Around Switch Port 0 Bit 0 0 means switch is pressed
KMS 540 AP Engage Switch Port 0 Bit 2 0 means switch is pressed
KMS 540 SCAS Engage Port 0 Bit 3 0 means switch is pressed
Switch
AFCS Disconnect Port 0 Bit 5 0 means 28 VDC is pres-
ent
Self Test Port 1 Bit 6 0 means switch is pressed
Force Trim Circuit Breaker Port 1 Bit 13 0 means 28 VDC is pres-
ent
Cyclic FTE Port 2 Bit 10 0 means 28 VDC is pres-
ent
Cyclic FTR Port 2 Bit 13 0 means 28 VDC is pres-
ent
Yaw FTE Port 2 Bit 11 0 means 28 VDC is pres-
ent
Yaw FTR Port 2 Bit 14 0 means 28 VDC is pres-
ent
Labeled AFCS Ground Test on the pedestal.
Cyclic FTE and Yaw FTE can be controlled together using the Force Trim Off switch
mounted on the upper portion of the center pedestal.
See section 5.1.6 for information on activating this input.
TABLE 7--9 Cockpit Switches Discrete Inputs to AP Processor
NOTE
The Air Data interface is NOT present in SCAS/ATT only systems.
The easiest method for verifying that the FCC is receiving information from the air data system is
to attempt IAS hold mode. To verify operation of KAV 485 interface to FCC attempt IAS hold mode
engagement using the IAS ENG button on the KMS 540 when in normal mode (see section 1.6.2.3
for more information). If IAS hold mode engagement is successful, the FD processor is receiving
information from the KDC 481. To verify operation of FCC to KAV 485 interface attempt VS hold
mode engagement using the VS ENG button on the KAV 485. If VS hold mode engagement causes
the vertical speed bug on the KAV 485 to come into view the air data system is also receiving
information from the FCC. However, this method of verification does not verify that all labels
received from the KDC 481 are valid (i.e., True Airspeed, which could degrade FCC operation) and
does not verify that the AP processors are receiving air data information directly from the air data
system.
Air data information is received by the FD processor on ARINC 429 ASIC 1 channel 3 and by the
AP processors on ARINC 429 ASIC 0 channel 2. Table 7--11 shows the air data labels used by the
KFC 500 followed by a legend for the label formats that can be received. This information can be
displayed using the ARINC 429 input/output screen in diagnostic mode (see section 6.1.5.2.4
ARINC 429 Input/Output Screen).
Label Label Description Format (See legend below)
102 Selected Altitude B
104 Selected Vertical Speed E
203 Pressure Altitude A
204 Baro Corrected Altitude A
206 Indicated Air Speed D
207 VMO D
210 True Air Speed C
271 Discrete #2 Bit 29 = Vert Speed Select/Deselect
Bit 28 = Alt Select Arm
TABLE 7--11 ARINC 429 Information Received from the Air Data System
(Sheet 1 of 2)
LEGEND
BIT Format A Format B Format C Format D Format E
29 SIGN SIGN SIGN = 0 SIGN = 0 SIGN
0 = above 0 = above 0 = Climb
sea level sea level 1 = Descent
28 65636 FT 32768 FT 1024 KT 512 KT 8192 FT/MIN
27 32768 FT 16384 Ft 512 KT 256 KT 4096 FT/MIN
26 16384 Ft 8192 FT 256 KT 128 KT 2048 FT/MIN
25 8192 FT 4096 FT 128 KT 64 KT 1024 FT/MIN
24 4096 FT 2048 FT 64 KT 32 KT 512 FT/MIN
23 2048 FT 1024 FT 32 KT 16 KT 256 FT/MIN
22 1024 FT 512 FT 16 KT 8 KT 128 FT/MIN
21 512 FT 256 FT 8 KT 4 KT 64 FT/MIN
20 256 FT 128 FT 4 KT 2 KT 32 FT/MIN
19 128 FT 64 FT 2 KT 1 KT 16 FT/MIN
18 64 FT 32 FT 1 KT 0.5 KT 0
17 32 FT 16 FT 0.5 KT 0.25 KT 0
16 16 FT 8 FT 0.25 KT 0.125 KT 0
15 8 FT 4 FT 0.125 KT 0.0625 KT 0
14 4 FT 2 FT 0.0625 KT 0 0
13 2 FT 1 FT 0 0 0
12 1 FT 0 0 0 0
11 0 0 0 0 0
All label formats are binary and can be decoded similarly. As an example,
when looking at label 203 (pressure altitude) bits 16, 17, and 19 are set to
a 1 on the diagnostic screen, while the other bits from 11 to 28 are set to a
0. Since label 203 is format A, bit 19 corresponds to 128 ft, bit 17 corre-
sponds to 32 ft, and bit 16 corresponds to 16 ft from the table. Adding
these three values together gives a pressure altitude reading of 176 feet.
TABLE 7--11 ARINC 429 Information Received from the Air Data System
(Sheet 2 of 2)
LEGEND
BIT Format A Format B Format C Format D Format E Format F
29 SIGN 0 SIGN 0 0= Fly Right 0=Fly Down 1 = Mag SIGN 0
1= Fly Left 1=Fly Up 0 = True
28 4096 FT 90 Deg 0.2 DDM 0.4 DDM 0 = DG 1 Sel 256 NM
27 2048 FT 45 Deg 0.1 DDM 0.2 DDM 0 = VG 1 Sel 128 NM
26 1024 FT 22.5 Deg 0.05 DDM 0.1 DDM 0 64 NM
25 512 FT 11.25 Deg 0.025 DDM 0.05 DDM 1 = LNAV Sel 32 NM
24 256 FT 5.625 Deg 0.0125 DDM 0.025 DDM 1=ILS Sel 16 NM
23 128 FT 2.813 Deg 0.00625 DDM 0.0125 DDM 1=BRG SRC Sel 8 NM
22 64 FT 1.406 Deg 0.00313 DDM 0.00625 DDM 1= Test Mode 4 NM
TABLE 7--13 AP Processor Discrete Output Values for Setting Aural Tone Frequency
Volume in Watts Output Port 2 Bit 13 Output Port 2 Bit 12 Output Port Bit 11
1.25 mW 0 0 0
2.5 mW 0 0 1
5.0 mW 0 1 0
10 mW 0 1 1
20 mW 1 0 0
40 mW 1 0 1
80 mW 1 1 0
100 mW 1 1 1
TABLE 7--14 AP Processor Discrete Output Values for Setting Aural Tone Amplitude
APPENDIX A
ERROR CODES
GENERAL INFORMATION
Each error has a unique number and text message that is displayed on the Remote Terminal
Interface error log screen (see section 6.1.4). Since the error log only allows for an error description
of 30 characters, this appendix gives additional information about logged errors, including a more
detailed description of the error and possible reasons for the error.
Errors 0 through 342 cause the processor that logged the error to be reset when the error occurs.
Errors 360 through 363 and 381 are logged after a reset occurs for the reason indicated. Other
errors should not cause the processor to be reset when they are logged, but will affect operation
of the processor as indicated.
Error Code Categories
The following lists the general categories that the FCC errors are grouped in. It includes a category
name, a description of the category, and the range of error code numbers contained in that category.
Category Error range Description
Exception Vectors 0 -- 299 Related to unintended interrupts (exceptions)
detected by the common kernel interrupt ser-
vice routine (generic interrupt handler which
is used in all FCC processors)
CPU/Kernel 300 -- 399 Related to failures in the microprocessor or
operating system
Interprocessor Bus 400 -- 499 Related to failures in the IP communication
bus
RS 232 500 -- 599 Related to failures in the RS232 serial inter-
face to a remote terminal or the configuration
module (some of these failures may make
the RTI interface not operate properly)
Direct Memory Access 600 -- 699 Related to failures in the DMA transfer
ARINC 429 ASIC 700 -- 799 Related to failures in the ARINC 429 chip
Flight Director 800 -- 899 Related to failures detected by the FD proc-
essor when an improper mode change se-
1900 -- 1999
quence is requested
Input/Output 900 -- 999 Related to generic input and output failures
Embedded Control Algorithm 1000 -- 1099 Related to failures in the ECAL algorithms
Language
Autopilot monitoring 1100 -- 1199 Related to failures detected by the system
monitors in the AP processor
Analog input 1200 -- 1299 Related to failures when inputting analog
data
Floating point 1300 -- 1399 Related to failures detected when performing
floating point arithmetic operations
Installation 1400 -- 1499 Related to installation parameters that are
invalid upon powerup initialization
Pre Flight Test 1500 -- 1699 Related to failures detected during the auto-
matic powerup or pilot initiated system test
NOTE
When more than one unit is listed as a possibly source of the error
there is also a possibility that the harness interconnection between
any of the units listed failed.
A system bus fault was detected. Either there has been a failure in the hardware bus
structure in the KCP 520 or the software processing the bus has failed.
The processor attempted to fetch an instruction or multi--byte data packet from an odd
(byte) address, instead of from an even (word) address.
The processor attempted an integer division by zero. There will probably also be float-
ing point errors logged when this failure occurs.
The processor trapped an instruction. Traps are normally used for debugging pur-
poses. The processor has tried to trap an instruction (to stop the processor) when op-
erating normally.
An attempt was made to execute a privileged instruction when not in supervisor mode
(i.e., changing the value of the stack pointer when in user mode).
The processor encountered a trace (used for debugging purposes) during normal op-
eration.
The hardware in the KCP 520 incorrectly requested a breakpoint in software to occur.
The math coprocessor improperly communicated with the processor. Since there is no
math coprocessor, this error should not occur.
The processor found an invalid format code in the stack control operations or an inter-
rupt vector that was not initialized.
A spurious interrupt occurred in the processor. This can indicate a software problem or
the KCP 520 hardware incorrectly requested an interrupt.
An exception (interrupt) occurred at the indicated priority level (1 -- 7) that could not be
properly identified or serviced. This can indicate a missing interrupt service routine or
other software problem or the KCP 520 hardware incorrectly requested an interrupt.
An unexpected trap instruction occurred to switch from user mode to supervisor mode.
The math coprocessor detected an arithmetic error during operation. Since there is no
math coprocessor, this error should not occur.
Hardware exceptions (interrupts) that are unimplemented in the processor. This can
indicate a software problem or the KCP 520 hardware incorrectly requested an inter-
rupt.
Powerup routines detected a failure in the EPROM memory during the CRC check-
sum test of the ROM.
Powerup routines detected a failure when testing the processor interval timer.
The task number passed to CK_save_async routine as a parameter exceeds the total
number of synchronous and asynchronous tasks defined.
Powerup routines detected a failure with the software watchdog. The software watch-
dog failed to interrupt the processor within a given time period.
Reserved error number, used as a base for following frame overrun errors.
The frame time was exceeded while executing task x (task number in error task). The
processor ran out of time to complete all required tasks during a frame time.
A second bus exception occurred while still processing a previous bus exception (in-
terrupt). This indicates a failure with the interprocessor communication bus.
Processor system clock has lost its crystal input signal, indicating a possible malfunc-
tion in the crystal oscillator.
The processor was reset due to a RESET instruction or other undiscriminated cause.
The watchdog circuitry was not reset within the watchdog time--out period, so the
watchdog reset the processor.
The error logging routines detected a checksum error in the non--volatile RAM.
Powerup routines detected a generic fault in the serial input/output capability of the
processor which affects all interprocessor communications.
The status of a received communication packet was invalid. If the error occurred once,
probably noise on the bus caused a packet to get corrupted.
The count byte in a received packet was improper for the data type (i.e., ARINC 429
data type should have 4 bytes, but count byte says there are 5 bytes in the packet). If
the error occurred once, probably noise on the bus caused a packet to get corrupted.3
The buffer used to store received data from the interprocessor bus has been filled be-
fore it could be serviced. The communication bus is overloaded with transmitted data,
the processor cannot process the data as rapidly as it is being received.3,
The buffer used to store received text from the interprocessor bus has been filled be-
fore it could be serviced. The communication bus is overloaded with transmitted data,
the processor cannot process the data as rapidly as it is being received.3,4
Data was received on the interprocessor bus while the processor reporting the error
had control of the bus.3
Another processor tried to take bus control while the reporting processor had bus con-
trol.3
A start of end of serial break was detected on the interprocessor bus. If the error oc-
curred once, probably noise on the bus caused a packet to get corrupted.3
The interprocessor bus changed state (from inactive to active, etc.) unexpectedly.3
The buffer used to store data to be transmitted on the interprocessor bus has been
filled before it could be serviced. Possibly another processor is babbling (transmitting
data on the bus almost constantly, not allowing another processor to gain control of
the bus).
The buffer used to store text data to be transmitted on the interprocessor bus during
diagnostic mode has been filled before it could be serviced. Possibly another proces-
sor is babbling (transmitting data on the bus almost constantly, not allowing another
processor to gain control of the bus).
An unrecognized text label was received on the interprocessor bus. If the error oc-
curred once, probably noise on the bus caused a packet to get corrupted.3
During the interrupt service routine for the interprocessor bus, the size of a data pack-
et exceeded the maximum size (count in bytes).3
An error occurred when trying to execute the switch statement on packet type in the
interrupt service routine for the interprocessor bus. This is a software failure that
should not occur.
A break character was received on the interprocessor communication bus. If the error
occurred once, probably noise on the bus caused a packet to get corrupted.3
The receive buffer for RS 232 serial information received has filled before it could be
serviced. Possibly the RS 232 bus became overloaded with incoming data and the
processor could not keep up.4
An interrupt was requested for RS 232 interface, but it was not caused by the trans-
mitter or the receiver.
Powerup routines detected a failure to receive a transmitted byte within the allowed
time period by the RS 232 receiver. There may be nothing connected to the RS 232
receive port.
Powerup routines detected that the RS 232 transmitter was unavailable within the al-
lowed time period.
Powerup routines detected a failure in the RS 232 data wraparound test. The proces-
sor did not receive back what was transmitted.
The buffer used for receiving ARINC 429 data from the ASIC has filled before it could
be serviced. Possibly the processor cannot keep up with data received from the
ARINC 429 inputs.4,
Powerup routines detected that the indicated DMA channel failed to transfer all of its
requested data.5
There was a bus error while attempting to read from the indicated DMA source.4,5
There was a bus error while attempting to write data input from the ARINC 429 ASIC
into the RAM buffer.4,5
The port size specified for the source or destination address does not match the ad-
dress used (e.g. odd address used with 16--bit port).5
The DMA transfer had not completed when the DMA controller interrupted the proces-
sor.4,5
Powerup routines detected an invalid label or data received on the indicated ARINC
429 chip and channel (i.e., invalid data on 429 chip number 1, channel 1 for error
703).
Powerup routines detected no received data on the indicated ARINC 429 chip and
channel.
Powerup routines detected that transmitted data for the indicated ARINC 429 chip was
not received on any channel during loopback testing.
Powerup routines detected that the transmitter for the indicated ARINC 429 chip did
not become available in the allotted time.
There was an invalid lateral mode requested based on the current lateral mode (i.e.,
for error 800, NAVTRK mode was requested, but cannot be engaged when in lateral
default mode).
The requested roll (lateral) coupled mode is not allowed in the current configuration.
There was an invalid lateral track or approach mode requested based on the current
lateral mode (i.e., for error 820, NAV track or approach was requested, but cannot be
engaged when in a no arm mode condition).
The requested roll (lateral) arm mode is not allowed in the current configuration.
There was an invalid vertical mode requested based on the current vertical mode (i.e.,
for error 830, VNAV coupled was requested, but cannot be engaged when in VNAV
capture).
The requested pitch (vertical) mode is not allowed in the current configuration.
There was an invalid vertical track or approach mode requested based on the current
vertical mode (i.e., for error 851, VNAV track or approach was requested, but cannot
be engaged when in a no arm mode condition).
The requested pitch (vertical) mode is not allowed in the current configuration.
The EFIS symbol generator indicated that the EFIS ADI is invalid or unavailable.
The EFIS symbol generator indicated that the EFIS HSI is invalid or unavailable.
The EFIS symbol generator detected a significant difference between its two attitude
sources.
The EFIS symbol generator valid output is not being received by the flight computer
via the ARINC 429 input.
Mode Select Panel information is not being received by the flight computer via the
ARINC 429 input.
The mode select panel detected a ROM memory checksum failure during testing of its
EPROM memory.
The mode select panel has detected a RAM memory failure during testing of its RAM
memory.
The mode select panel detected a CPU timing failure during testing of its CPU.
The mode select panel detected a CPU instruction execution problem when perform-
ing its internal instruction test.
The mode select panel received ARINC 429 data from the flight computer that had
invalid sign/status matrix (SSM).
The mode select panel received ARINC 429 data from the flight computer that had an
invalid source/destination identifier (SDI). The received SDI did not match the ex-
pected SDI.
The mode select panel did not receive ARINC 429 data from the flight computer.
The indicated power supply (+5 VDC, +12 VDC, --12 VDC, or +28 VDC) in the mode
select panel is out of tolerance.
The mode select panel detected that one of its front panel switches is stuck.
The mode select panel detected that one of the cockpit mounted switches is stuck.
The sensors associated with the flight computer Heading Select mode are not valid
(i.e., directional gyro inputs).
The sensors associated with the flight computer NAV or Approach mode are not valid
(i.e., directional gyro inputs or NAV information from EFIS).
The sensors associated with the flight computer Altitude Arm mode are not valid (i.e.,
altitude input). This could also indicate that altitude capture was requested when in
glideslope coupled mode
The sensors associated with the flight computer Vertical NAV mode are not valid. This
error should not occur, since VNAV is not available as a mode.
The sensors associated with the flight computer Altitude Hold mode are not valid (i.e.,
altitude input)
The sensors associated with the flight computer Indicated Airspeed Hold mode are not
valid (i.e., pressure altitude input or airspeed input).
The sensors associated with the flight computer Vertical Speed Hold mode are not
valid (i.e., altitude input or vertical speed input).
The sensors associated with the flight computer Go Around mode are not valid (i.e.,
altitude input or pitch attitude input).
The sensors for inputting attitude information for the flight computer are not valid (i.e.,
vertical gyro inputs).
The flight director disable discrete input indicates that the flight director should be dis-
abled.
The flight director pitch mode was aborted due to an invalid sensor. If this error is
logged individually, it indicates an internal failure in the flight computer. Otherwise, the
accompanying error should identify the sensor input that failed.
The flight director roll mode was aborted due to an invalid sensor. If this error is
logged individually, it indicates an internal failure in the flight computer. Otherwise, the
accompanying error should identify the sensor input that failed.
The sensors associated with the flight computer Altitude Arm or Altitude Capture
mode are not valid (i.e., altitude input).
The sensors associated with the flight computer Roll Arm mode are not valid (i.e., di-
rectional gyro inputs, roll attitude input).
The sensor associated with the flight computer Vertical NAV mode or Glideslope Arm
mode are not valid (i.e., glideslope/VNAV deviation input from EFIS).
The sensor associated with maximum operating velocity limiting are not valid (i.e., in-
dicated airspeed input or mach input).
This is a dummy error code marking the end of the FF error code section. This error
should not occur.
The buffer used to store received data from the interprocessor bus has been filled be-
fore it could be serviced. The communication bus is overloaded with transmitted data,
the processor cannot process the data as rapidly as it is being received.4
The buffer used to store data to be transmitted on the interprocessor bus has been
filled before it could be serviced. Possibly another processor is babbling (transmitting
data on the bus almost constantly, not allowing another processor to gain control of
the bus).
A source identifier was received on the interprocessor bus that was invalid. If the error
occurred once, probably noise on the bus caused a packet to get corrupted.4
The common input/output routines received a request to transmit ARINC 429 informa-
tion on the maintenance processor, which does not have an ARINC 429 ASIC avail-
able for use.
An unexpected label was received on one of the ARINC 429 input channels, this label
should have been masked by the ARINC 429 ASIC.
A label (interprocessor or ARINC 429) was not received within its update period. This
is a generic error that should not occur.
The ARINC 429 channel receiving information from the air data computer did not re-
ceive data within its update period.
The specified channel did not receive data on the interprocessor bus within its update
period.
The specified channel did not receive data on the interprocessor bus within its update
period.
The ARINC 429 channel receiving information from the air data computer did not re-
ceive data within its update period.
The ARINC 429 channel receiving information from EFIS did not receive data within
its update period.
The ARINC 429 channel receiving information from the flight management system did
not receive data within its update period.
The ARINC 429 channel receiving information from the mode select panel did not re-
ceive data within its update period.
The specified channel did not receive data on the interprocessor bus within its update
period.
The specified channel did not receive data on the interprocessor bus within its update
period.
The specified channel did not receive data on the interprocessor bus within its update
period.
The specified channel did not receive data on the interprocessor bus within its update
period.
An error occurred while processing one of the ECAL nodes (i.e., a required input to an
ECAL node was undefined).
An ECAL stack or FIFO call was made with an improper data type (data type must be
boolean or floating point).
An error occurred in the processor when trying to access the FIFO buffer used by
ECAL (FIFO corrupted).
An error occurred in the processor when trying to access the ECAL stack (stack cor-
rupted).
An attempt was made to reference a node outside the ECAL data block (i.e., node
pointer not initialized properly).
The ECAL data block being processed does not match the selected mode (i.e., proc-
essing Heading Hold block when in Roll Attitude Hold mode).
An ECAL function was called with too few input parameters (i.e., one when function
requires at least two).
A generic error occurred while processing the ECAL node or block data.
One of the node records in an ECAL node block is not valid (i.e., improper number of
parameters for block type specified).
The pointer to a block in the ECAL data block is not valid (i.e., ECAL data pointer is
corrupt).
The ECAL mode index is indicating a mode number that does not exist.
The directional gyro excitation is insufficient for proper operation. Directional gyro ex-
citation is currently not monitored, therefore this error should not occur.
A control position was detected to be out of the installed control position range. The
control position input is monitored to be between the stored control position stop posi-
tions, determined during installation, for the indicated axis. This control position was
outside of the control position stop position range by more than 20 % of the total con-
trol position range for that axis for 400 ms. This failure will be cleared when the control
position is within the control position range for 500 ms.
A pitch or roll attitude rate discrepancy was detected, the difference between attitude
rate from the primary and secondary rate sources was excessive. The absolute differ-
ence between primary and secondary attitude rate exceeded 2 degrees/second for
pitch rate or 2.5 degrees/second for roll rate for 500 ms. This failure will be cleared
when the rate difference is below the threshold for 500 ms.
The vertical gyro validity input for roll or pitch attitude was invalid. The roll or pitch atti-
tude input was invalid for 400 ms. This failure will be cleared when the attitude input
source is valid for 500 ms.
The pitch command received from the FD processor exceeded the indicated direction
limit. The pitch axis command from the flight director either was greater than +20_,
causing a pitch up error, or less than --15_, causing a pitch down error, for 600 ms.
This failure will be cleared when the pitch axis command from the flight director is be-
tween --15_ and +20_ for 500 ms.
The roll command received from the FD processor exceeded the indicated direction
limit. The roll axis command from the flight director either was greater than +31_,
causing a roll right error, or less than --31_, causing a roll left error, for 600 ms. This
failure will be cleared when the roll axis command from the flight director is between
--31_ and +31_ for 500 ms.
The DAC wraparound value for the indicated servo does not match the value calcu-
lated by the reporting processor. The absolute difference between the computed com-
mand for the servo and the analog servo command input exceeded 205 bits (1 volt)
for 50 ms on AP A or 820 bits (4 volts) for 325 ms on AP B while the command differ-
ence did not change polarity (i.e., computed command was continually greater than
analog command input). Also, for AP B, the change in output command in a 25 ms
interval did not exceed 102 bits (0.5 volt) during the failure time. This failure can only
be cleared by executing preflight test again.
The indicated servo amplifier midpoint voltage input failed. The absolute difference
between the expected value for the midpoint voltage and the analog midpoint voltage
input exceeded 4.2 volts for 400 ms. The expected midpoint voltage is 0 volts when
the servo is not powered, one--half of the +28 VDC input value when the servo is pow-
ered and enabled, and the +28 VDC input value when the servo is powered and not
enabled (see section 7.2.1 Primary Servo Axis Interfaces). This failure can only be
cleared by executing preflight test again.
The indicated servo amplifer failed. The servo amplifer for the KLA 570 is modeled in
software using the following equation.
Vm = ---20.5 x(Vcmd --- p ---0.3452 x Ar)
Vm -- servo motor voltage
Vcmd -- servo command (in volts)
p -- LVDT position (in volts)
Ar -- LVDT position rate (in inches/second)
The servo amplifer for a KSA 572 is modeled in software using the following equation:
Vm = ---4.1 x Vcmd
The computed servo motor voltage obtained using the above equations is then limited
to an absolute maximum value (+28 VDC input value minus 2 volts) and compared
with input servo motor voltage. The absolute difference between computed servo mo-
tor voltage and input servo motor voltage exceeded 8.4 volts for 500ms. This failure
can only be cleared by executing preflight test again.
The indicated servo motor was drawing excessive current. The absolute input motor
current for the indicated servo was greater than 1 amp for a KLA 570 servo or 0.5 amp
for a KSA 572 servo for 60 sec. This failure can only be cleared by executing preflight
test again.
The LVDT position validity for the indicated servo failed. The voltage input for LVDT
validity for the indicated servo was below 0.5 volt for 400 ms when the servo was pow-
ered. This failure can only be cleared by executing preflight test again.
An LVDT position was detected to be out of the installed LVDT position range. The
LVDT position input is monitored to be between the stored LVDT stop positions, deter-
mined during installation, for the indicated axis. This LVDT position was outside of the
LVDT stop position range by more than 20% of the total LVDT position range for that
axis for 400 ms. This failure can only be cleared by executing preflight test again.
The indicated servo amplifer failed. The servo amplifier for a KLA 570 is modeled in
software using the following equation:
The brake for the indicated servo did not release as requested The brake release in-
put for the servo did not indicate the brake was released for 400 ms when the brake
release hi and brake release lo outputs for the servo were both active. This failure can
only be cleared by executing preflight test again.
The brake for the indicated servo did not engage as requested. The brake release
input for the servo did not indicate the brake was engaged for 400 ms for AP A or
300 ms for AP B when either the brake release hi or brake release lo output for the
servo was inactive. This failure can only be cleared by executing preflight test again.
S 1
attp = att + att x ------
s+1
The indicated acceleration value was detected to be at an unusual value when the
autopilot was engaged. For lateral acceleration, the primary yaw servo command was
driving the aircraft left and lateral acceleration was less than --16.1 feet/second2 or the
primary yaw servo command was driving the aircraft right and lateral acceleration was
greater than 16.1 feet/second2 for 600 ms. This failure will be cleared when lateral
acceleration is between --16.1 feet/second2 and 16.1 feet/second2 for 500 ms. For
normal acceleration, the primary pitch servo command was driving the aircraft down
and normal acceleration was less than --19.3 feet/second2 or the primary pitch servo
command was driving the aircraft up and normal acceleration was greater than
22.5 feet/second2 for 600 ms. This failure will be cleared when normal acceleration is
between --19.3 feet/second2 and 22.5 feet/second2 for 500 ms.
The hydraulic pressure sensor indicated that the hydraulic pressure is low. The hy-
draulic pressure valid input was at an invalid state for 600 ms. This failure will be
cleared when the hydraulic pressure valid input is valid for 500 ms.
These errors should not occur, since the collective axis servo is not installed in the
Bell 430 installation.
A stalled servo was detected, the servo stopped at a position other than the mechani-
cal stop. When the servo motor current for the servo actuator exceeds 0.6 amp for
500 ms, the servo is considered to be stalled. At that time, the input servo LVDT posi-
tion is compared with the stored stop position, determined during installation, for that
servo. The difference between these two values was greater than 20% of the full scale
travel for that servo (absolute difference between both stop positions as determined
during installation), indicating that the servo stalled at a position other than the normal
mechanical stop. This failure can only be cleared by executing preflight test again.
A stalled servo was detected, servo stopped at a position other than the mechanical
stop. When the servo motor current for the servo actuator exceeds 0.08 amp for
500 ms, the servo is considered to be stalled. At that time, the input synchro position
from the control position resolver for that axis is compared with the stored stop posi-
tion, determined during installation, for that servo. The difference between these two
values was greater than 20% of the full scale travel for that servo (absolute difference
between both stop positions as determined during installation), indicating that the ser-
vo stalled at a position other than the normal mechanical stop. This failure can only be
cleared by executing preflight test again.
1184 Pit position synchro exc mon 1. Indicated control position resolver
1185 Rol position synchro exc mon 2. KCP 520
1186 Yaw position synchro exc mon
1187 Col position synchro exc mon
The excitation voltage for the indicated control position resolver is inadequate for
proper operation. The validity for the indicated axis position was invalid (indicating in-
valid excitation). This failure will be cleared when the validity is valid for 500 ms.
The roll or pitch command received from the FD processor was invalid. The command
received on the interprocessor bus from the FD processor for the indicated axis was
invalid (validity indicated invalid) for 300 ms. This failure will be cleared when the com-
mand is valid for 500 ms.
Monitoring of an LVDT was attempted in an axis that does not have an LVDT. This
error indicates that the ROM servo information table in the processor code has been
corrupted. This failure can only be cleared by executing preflight test again.
The DAC wraparound values for servo commands for at least two axes did not match
the values calculated by the reporting processor. The absolute difference between the
computed commands for the servos and their corresponding analog command inputs
exceeded 205 bits (1 volt) for 25 ms on AP A or 820 bits (4 volts) for 100 ms on AP B
Also, for AP B, the change in output command for the servos did not exceed 102 bits
(0.5 volt) in a 25 ms interval during the failure time. This failure can only be cleared by
executing preflight test again.
The reference voltage for the vertical gyro was inadequate for proper operation. The
reference voltage for the vertical gyro was either below 15 volts or above 40 volts for
50 ms while AP mode was engaged. This failure can only be cleared by executing
preflight test again.
The body rate input for the indicated axis is invalid. Either the body rate input validity
indicated the rate was invalid or the absolute body rate was above 10 degrees/second
for pitch rate, 15 degrees/second for roll rate, or 15 degrees/second for yaw rate for
1 sec. This failure will be cleared when the body rate is valid and absolute body rate is
below the rate limit for 500 ms.
A monitor or preflight test failure was detected while input +28 VDC power was con-
sidered at a low voltage. This error is logged instead of the normal monitoring or pre-
flight test error when +28 VDC input value is below 17.5 volts. This error will be logged
when +28 VDC input value is below 17.5 volts and will not be logged when +28 VDC
input is above 17.5 volts.
The MUX address associated with an analog input was incorrect. This probably indi-
cates that the MUX sequencer for the analog inputs failed. All modes will dump when
this error occurs and the failure can only be cleared by executing preflight test again.
The analog inputs used for testing each analog to digital converter were out of toler-
ance. There is one input on each analog to digital converter that is used to check for
proper operation of the converter (normally one of the power inputs, like + 5 V DC).
One of these inputs when read in was out of tolerance (i.e., + 5 V DC was read in at a
+ 10 V level). All modes will dump when this error occurs and the failure can only be
cleared by executing preflight test again.
The analog input for loopback did not match the analog loopback output. A test signal
is output to a digital to analog converter and then input into the analog to digital con-
verter for a wraparound comparison. This test signal is changed every 25 milliseconds
so that the entire analog input voltage range can be tested. The input signal read in
and the signal output did not match. All modes will dump when this error occurs and
the failure can only be cleared by executing preflight test again.
The indicated analog input (from one analog to digital converter) was outside of the
normal analog input range. The analog input (when converted to the corresponding
input voltage) was either less than --9.5 V or greater than + 9.5 V.
The indicated analog input (from one analog to digital converter) was outside of the
normal analog input range. The analog input (when converted to the corresponding
input voltage) was either less than --9.5 V or greater than + 9.5 V.
The indicated analog input (from one analog to digital converter) was outside of the
normal analog input range. The analog input (when converted to the corresponding
input voltage) was either less than --9.5 V or greater than + 9.5 V.
The indicated analog input (from one analog to digital converter) was outside of the
normal analog input range. The analog input (when converted to the corresponding
input voltage) was either less than --9.5 V or greater than + 9.5 V.
The indicated analog input (from one analog to digital converter) was outside of the
normal analog input range. The analog input (when converted to the corresponding
input voltage) was either less than --9.5 V or greater than + 9.5 V.
The indicated analog input (from one analog to digital converter) was outside of the
normal analog input range. The analog input (when converted to the corresponding
input voltage) was either less than --9.5 V or greater than + 9.5 V.
A floating point math routine was called with a value that does not represent a valid
number.
A floating point math routine computation resulted in a number which exceeds the rep-
resented number range. This is normally caused by dividing a large number by a very
small number.
This error has been reserved for use by installation when detecting failures during
installation of the primary servos (LVDTs). At present, it is not used and should not
occur.
These errors have been reserved for use by installation when detecting failures during
installation of the trim servos. At present, they are not used and should not occur.
This error has been reserved for use by installation when detecting a failure while at-
tempting to write installation data to the configuration module. At present, it is not used
and should not occur.
This error has been reserved for use by installation when the maintenance processor
was not ready to transmit installation data when requested by the reporting processor.
At present, it is not used and should not occur.
This error has been reserved for use by installation when the maintenance processor
does not receive any requests for installation data during powerup initialization. At
present, it is not used and should not occur.
Installation configuration data was not received from the maintenance processor after
being requested. The reporting processor requested installation data from the mainte-
nance processor, but did not receive any installation data from the maintenance proc-
essor.
A checksum error occurred when installation data was received from the maintenance
processor. The calculated checksum for the data did not match the checksum byte
transmitted for the data.
The calculated checksum for installation data in both autopilot processors does not
match. Each autopilot processor computes a checksum for its installation data and
these two checksum values were not the same.
An invalid checksum for the installation data being used was detected. The reporting
processor did not receive installation data from the maintenance processor and the
checksum computed for its local installation data did not match the stored checksum
for that data.
Both autopilot processors believe they have the same processor ID. During preflight
test, the autopilot processors read their performance strap configuration to determine
their AP identification (either AP A or AP B). When they compared identifications, they
both thought they were the same AP.
The other autopilot processor did not respond to the reporting processor when re-
questing synchronization of processors for preflight test. At the beginning of preflight
test, each processor sends out a preflight test synchronization request on the interpro-
cessor bus and waits for a reply from the other processor to begin preflight test. The
other processor did not respond within 1.5 sec.
The indicated processor was unable to turn off power or set the brake for at least one
servo when it set its processor valid discrete to invalid. The indicated processor was
unable to disable power to primary servos (KLA 570) or set the brake on trim servos
(KSA 572) when it set its valid discrete to invalid. Each processor tests for this capa-
bility individually.
The performance strap inputs do not match stored strap configuration. During preflight
test, the performance strap configuration is read in and compared with a performance
strap configuration value stored in ROM memory. The stored value for the Bell 430
installation corresponds to perf strap inputs 0, 2, 3, and 4 open and perf strap input 1
grounded. The value read in during preflight test did not match the value stored in
memory.
The accelerometer valid input did not return to a normal value during preflight test.
During preflight test, the accelerometer test output is set to normal after checking for
test values. After setting this output to normal (not in test), the processor waits for
1 second before reading the acceleration validity. The accelerometer valid input indi-
cated that the accelerometer was invalid at that time.
The indicated acceleration value was not at the expected test value during preflight
test. During preflight test, the accelerometer test output is set to test to indicate testing
of the accelerometer values. After setting this output to test, the processor waits for
500 ms before reading the acceleration values. Lateral acceleration input was not be-
low --25.76 feet/second2 for error 1521. Normal acceleration was not above
86.94 feet/second2 for error 1523.
The indicated acceleration value did not return to a value within its normal range of
operation during preflight test. During preflight test, the accelerometer test output is
set to normal after checking for test values. After setting this output to normal (not in
test), the processor waits for 1 second before reading the acceleration values. For
error 1524, lateral acceleration was either below --16.1 feet/second2 or above
16.1 feet/second2. For error 1526, normal acceleration was either below 0.0 feet/sec-
ond2 or above 64.4 feet/second2.
The accelerometer valid input was not at the expected test value during preflight test.
During preflight test, the accelerometer test output is set to test to indicate testing of
the accelerometer validity. After setting this output to test, the processor waits for
500 ms before reading the acceleration validity. The accelerometer valid input indi-
cated that the accelerometer was valid at that time.
The value read in on the analog to digital converter for a servo command did not
match the value output to the digital to analog converter for that servo during preflight
test. During preflight test, all servos are first verified to be unpowered. Then, each ser-
vo is individually commanded to --1640 bits (--8 volts) and then commanded to
1640 bits (8 volts). All other servos are commanded with a 0 command (0 bits, 0
volts). At each test instance, each servo command is input from the analog to digital
converter (from the hardware wraparound) and compared with the value output. The
absolute difference between the input and output servo command values for the indi-
cated servo was greater than 205 bits (1 volt) at some point during this test.
The indicated servo amplifier midpoint voltage input failed during preflight test. The
absolute difference between the expected value for the midpoint voltage and the ana-
log midpoint voltage input exceeded 4.2 volts for the indicated axis. The expected
midpoint voltage is 0 volts when the servo is not powered, one--half of the +28 VDC
input value when the servo is powered and selected, and the +28 VDC input value
when the servo is powered and not selected (see section 7.2.1 Primary Servo Axis
Interfaces). All three midpoint voltage conditions are tested for each installed servo at
some point during preflight test.
The indicated servo LVDT sense (power) failed during preflight test. Either the LVDT
sense voltage was above 0.5 volts when the indicated servo was not powered or the
LVDT sense voltage was below 0.5 volts when the indicated servo was powered.
The indicated servo LVDT position failed during preflight test. The LVDT position input
is monitored to be between the stored LVDT stop positions, determined during instal-
lation, for the indicated axis. This LVDT position was outside of the LVDT stop position
range by more than 20% of the total LVDT position range for that axis.
The indicated servo control position failed during preflight test. The control position
input is monitored to be between the stored control position stop position, determined
during installation, for the indicated axis. This control position was outside of the con-
trol position stop position range by more than 20% of the total control position range
for that axis.
The indicated servo LVDT position rate failed during preflight test. The LVDT position
rate input is tested when the indicated servo is powered with the brake engaged (posi-
tion rate should be zero at this time, since the servo is not moving). The LVDT position
rate was above 0.11 inches/second for that axis when tested.
The motor current for the indicated servo failed during preflight test. Each servo is
commanded to its present position as read in from the analog inputs (a zero command
is output for the trim servos). At that time, the motor current for the indicated servo is
tested (motor offset current should be zero at this time, since there is no servo drive).
The motor current was above 0.1 amp for a KLA 570 servo or 0.025 amp for a KSA
572 servo.
The motor voltage for the indicated servo failed during preflight test. Each servo is
commanded to its present position as read in from the analog inputs (a zero command
is output for the trim servos). At that time, the motor voltage for the indicated servo is
tested (motor offset voltage should be zero at this time, since there is no servo drive).
The motor voltage was above 2.0 volts for the indicated servo.
Motor stall current for the indicated servo failed during preflight test when testing the
servo brake. The indicated servo was commanded to a position other than its present
position as read in from the analog inputs with the servo brake engaged. KLA 570 ser-
vos are commanded 25% of full--scale servo travel from their present position and
KSA 572 servos are commanded 50% of their full command value with the servo
brake engaged. The motor current for the indicated servo was not above the stall cur-
rent (0.5 amps for KLA 570 servos, 0.02 amps for KSA 572 servos) within 300 ms af-
ter the servo command was applied.
A servo monitor failure was detected during preflight test. Some of the monitors for the
servos are executed throughout the preflight test period. One of these monitors de-
tected a failure for the indicated servo. There should be an Autopilot Monitor failure
(error code 1200 -- 1299) logged in conjunction with this error.
Servo movement was detected for the indicated servo (if KLA 570) when the brake
was engaged during preflight test or the servo brake was not engaged. The indicated
KLA 570 servo moved from its original position by more than 0.01 inch while the brake
for that servo was engaged or the brake engaged input indicated that the servo brake
was not engaged when either the brake release hi or brake release lo output for the
servo was inactive.
The body rate valid input did not return to a normal value during preflight test. During
preflight test, the body rate test output is set to normal after checking for test values.
After setting this output to normal (not in test), the processor waits for 1 second before
reading the body rate validity. The body rate valid input indicated that the rate sensor
was invalid at that time.
The indicated body rate value was not at the expected test value during preflight test.
During preflight test, the body rate test output is set to test to indicate testing of the
body rate values. After setting this output to test, the processor waits for 500 ms be-
fore reading the body rate values. Pitch body rate was not above 30 degrees/second
for error 1631. Roll body rate was not above 30 degrees/second for error 1632. Yaw
body rate was not below --30 degrees/second for error 1633.
The indicated body rate value did not return to a value within its normal range of op-
eration during preflight test. During preflight test, the body rate test output is set to nor-
mal after checking for test values. After setting this output to normal (not in test), the
processor waits for 1 second before reading the body rate values. For error 1634,
pitch body rate was either below --8 degrees/second or above 8 degrees/second. For
error 1635, roll body rate was either below --12 degrees/second or above 12 degrees/
second. For error 1636, yaw body rate was either below --12 degrees/second or above
12 degrees/second.
The body rate valid input was not at the expected test value during preflight test. Dur-
ing preflight test, the body rate test output is set to test to indicate testing of the body
rate validity. After setting this output to test, the processor waits for 500 ms before
reading the body rate validity. The body rate valid input indicated that the rate sensor
was valid at that time.
An error was detected when translating autopilot gains from ROM constants to RAM
values. Either the gain index was out of range (larger than total number of translation
gains) or there was an invalid translation type indicated in the table (i.e., a filter
translation for a monitor gain).
The indicated primary servo was detected to be in a mistrim condition. The position for
the indicated primary servo was not near the center of servo travel in the same direc-
tion for 10 sec. For error 1710, the pitch primary servo position must be more than
40% of the full--scale pitch primary servo travel from center. For error 1711, the roll
primary servo position must be more than 40% of the full--scale roll primary servo trav-
el from center. For error 1712, the yaw primary servo position must be more than 25%
of the full--scale yaw primary servo travel from center.
The 10 Hz task frame in the autopilot processor lost sync with the 40 Hz task frame.
There was an invalid vertical mode requested based on the current vertical mode (i.e.,
for error 1900, autolevel mode was requested, but cannot be engaged when in Pitch
Attitude Hold (PAH) mode).
NOTE
When the aircraft is considered to be on the ground, the AP
monitoring errors (error codes 1100 through 1199 will not be
logged when the error occurs. This prevents ground checkout of
the system from causing errors to be logged that do not indicate
an actual system failure. The aircraft is considered to be on the
ground when indicated airspeed is less than 50 knots and is valid,
collective input is valid, and radar altitude is less than 15 feet if it is
valid (radar altitude is ignored for aircraft on ground determination
when it is invalid). When the aircraft is on the ground and AP
monitoring codes need to be logged (i.e., preflight test fails with no
error logged or testing for servo failures), the airdata circuit
breaker can be pulled to simulate the aircraft not on the ground.
Failure Annunciation
When a monitoring or preflight test error is logged, the failure is also annunciated to the pilot. Failure
to pass preflight test prevents future engagement of AP and SCAS mode, depending on the failure
detected, in the axis where the failure occurred. If a preflight test failure affecting a single axis is
detected during each of three test attempts, future engagement of AP mode is prevented in the
affected axis. If the detected failure was a primary servo failure, future engagement of SCAS mode
is also prevented in the affected axis. When this occurs, the failure light for the failed axis will be
illuminated on the IIDS (i.e., a pitch axis failure during PFT will cause the pitch axis fail light on the
IIDS to be illuminated). The failure discrete will remain illuminated until SCAS mode is engaged and
the failure was not a primary servo failure or pre--flight test is initiated. If a preflight test failure
affecting all axes is detected during each of three test attempts, future engagement of AP mode is
prevented. If the failure affected SCAS mode operation (i.e., performance strap miscompare),
future engagement of SCAS mode is also prevented. When this occurs, the AP fail light will be
illuminated on the IIDS.
When a monitoring error resulting in loss of AP mode occurs in only one axis (i.e., roll trim servo
failure), AP mode is dumped for the affected axis (if AP mode is engaged when the failure occurs),
the failure light for the failed axis is illuminated on the IIDS, and the disconnect aural alert tone will
sound for approximately 5 seconds. When AP mode is disengaged, the axis/axes failure light(s) will
be cleared. If possible, AP mode will revert to SCAS mode in the affected axis/axes (i.e., for failure
of a trim servo). This will occur for any error code listed here, but not listed for loss of SCAS mode
for the same axis below.
The following monitoring and preflight test error codes will result in the loss of AP mode in the pitch
axis only:
1119 pitch pri svo midpoint volt
1122 pitch trm svo midpoint volt
1125 pitch pri svo amplifier model
1128 pitch trm svo amplifier model
1131 pitch pri svo current monitor
1134 pitch trm svo current monitor
1137 pitch svo LVDT valid monitor
1140 pit svo LVDT pos rsnable mon
1143 pitch pri svo motor model
1146 pitch pri svo--no sol engage
1152 pitch trm svo--no sol engage
1155 pitch pri svo--no sol disengage
1158 pitch trm svo--no sol disengage
1167 XS normal accel monitor
1177 pitch pri servo stalled
1180 pitch trm servo stalled
1194 Pitch body rate monitor
1523 accelerometer norm tst val bad
1526 accelerometer norm value error
1530 PFT pitch cmd DAC or ADC error
1533 PFT pit trm cmd DAC or ADC err
1540 PFT pitch midpoint error
1543 PFT pitch trim midpoint error
1550 PFT pitch LVDT sense error
1560 PFT pitch servo position err
The following monitoring and preflight test error codes will result in the loss of SCAS mode in the
pitch axis only:
1119 pitch pri svo midpoint volt
1125 pitch pri svo amplifier model
1131 pitch pri svo current monitor
1137 pitch svo LVDT valid monitor
1140 pit svo LVDT pos rsnable mon
1143 pitch pri svo motor model
1146 pitch pri svo--no sol engage
1155 pitch pri svo--no sol disengage
1177 pitch pri servo stalled 7
1194 Pitch body rate monitor
1530 PFT pitch cmd DAC or ADC error
1540 PFT pitch midpoint error
1550 PFT pitch LVDT sense error
1560 PFT pitch servo position err
1570 PFT pitch LVDT rate too high
1580 PFT pit offset crnt too high
1590 PFT pit offset volt too high
1600 PFT pitch drive err
1610 PFT pitch monitor error
1620 PFT pitch brake err
1631 PFT pitch rate test value bad
1634 PFT pitch rate out of range
The following monitoring and preflight test error codes will result in the loss of SCAS mode in the
roll axis only:
1120 roll pri svo midpoint volt
1126 roll pri svo amplifier model
1132 roll pri svo current monitor
1138 roll svo LVDT valid monitor
1141 rol svo LVDT pos rsnable mon
1144 roll pri svo motor model
1150 roll pri svo--no sol engage
1156 roll pri svo--no sol disengage
1178 roll pri servo stalled
1195 Roll body rate monitor7
1531 PFT roll cmd DAC or ADC error
1541 PFT roll midpoint error
1551 PFT roll LVDT sense error
1561 PFT roll servo position err
1571 PFT roll LVDT rate too high
1581 PFT rol offset crnt too high
1591 PFT rol offset volt too high
1601 PFT roll drive err
1611 PFT roll monitor error
1621 PFT roll brake err
1632 PFT roll rate test value bad
1635 PFT roll rate out of range
The following monitoring and preflight test error codes will result in the loss of SCAS mode in the
yaw axis only:
1121 yaw pri svo midpoint volt
1127 yaw pri svo amplifier model
1133 yaw pri svo current monitor
1139 yaw svo LVDT valid monitor
1142 yaw svo LVDT pos rsnable mon
1145 yaw pri svo motor model
1151 yaw pri svo--no sol engage
1157 yaw pri svo--no sol disengage
1170 hydraulic pressure switch
1179 yaw pri servo stalled
1193 Yaw body rate monitor7
1532 PFT yaw cmd DAC or ADC error
1542 PFT yaw midpoint error
1552 PFT yaw LVDT sense error
1562 PFT yaw servo position err
1572 PFT yaw LVDT rate too high
1582 PFT yaw offset crnt too high
1592 PFT yaw offset volt too high
1602 PFT yaw drive err
1612 PFT yaw monitor error
1622 PFT yaw brake err
1633 PFT yaw rate test value bad
1636 PFT yaw rate out of range
When a monitoring error resulting in loss of AP mode for all axes occurs (i.e., vertical gyro failure),
the AP mode will dump, the AP annunciation will flash for approximately 5 seconds, and the AP
disconnect aural alert tone will sound for approximately 5 seconds. Some of the monitoring errors
will cause the AP fail light on the IIDS to be illuminated, but others will not, as described below. If
possible, AP mode will revert to SCAS mode for all available axes (axes that do not have a failure
affecting SCAS operation). This will occur for any error code listed here, but not listed for loss of
SCAS mode for all three axes listed below.
The following monitoring and preflight test error codes will result in the loss of AP mode in pitch,
roll, and yaw axes and illumination of the AP fail light on the IIDS:
1109 FD cmd monitor--pitch up
1110 FD cmd monitor--pitch down
1111 FD cmd monitor--roll left
1112 FD cmd monitor--roll right
1113 pitch pri svo DAC compare
1114 roll pri svo DAC compare
1115 yaw pri svo DAC compare
1116 pitch trm svo DAC compare
1117 roll trm svo DAC compare
1118 yaw trm svo DAC compare
1171 collect svo DAC compare
1191 Multi axis DAC compare
1510 PFT sync err waiting for AP A
1511 PFT sync err waiting for AP B
1512 AP A output control invalid
Common Errors
There are some error codes that can be logged in the error code log frequently. Some error codes
do not necessarily mean that the FCC is not operating properly when logged in the error log. The
following error codes may be logged in the error code log because of a transient (i.e., voltage spike
on an input), a unit not connected to the FCC when powered (i.e., no RTI interface set up, so RS
232 communications initially fails -- of course, if the error code log can be accessed these failures
are not currently a problem), or other similar problems that are not true system failures :
Error # Text Message When failure appears to occur most often
412 CIP RX ARINC queue full transition from diagnostic mode to normal mode
414 CIP RX text queue full transition from diagnostic mode to normal mode
422 CIP detect break transition from diagnostic mode to normal mode
920 CI Update Timing randomly (occurs potentially anytime)
921 Update timing 429_ADC during power--up and power--down of system
components (dependent on power application/re-
moval sequence for each unit)
929 Update timing CIP_APIN during power--up and power--down of system
components (dependent on power application/re-
moval sequence for each unit)
930 Update timing CIP_FDIN during power--up and power--down of system
components (dependent on power application/re-
moval sequence for each unit)
931 Update timing CIP_MAIIN during power--up and power--down of system
components (dependent on power application/re-
moval sequence for each unit)
935 Update timing A429_XMIT during power--up and power--down of system
components (dependent on power application/re-
moval sequence for each unit)
936 Update timing A429_ADC during power--up and power--down of system
components (dependent on power application/re-
moval sequence for each unit)
938 Update timing A429_EFIS during power--up and power--down of system
components (dependent on power application/re-
moval sequence for each unit)
940 Update timing A429_MSP during power--up and power--down of system
components (dependent on power application/re-
moval sequence for each unit)
947 Update timing CIP_APIN during power--up and power--down of system
components (dependent on power application/re-
moval sequence for each unit)
948 Update timing CIP_FDIN during power--up and power--down of system
components (dependent on power application/re-
moval sequence for each unit)
949 Update timing CIP_MAIIN during power--up and power--down of system
components (dependent on power application/re-
moval sequence for each unit)
955 Update timing A429_XMIT during power--up and power--down of system
components (dependent on power application/re-
moval sequence for each unit)
NOTES
1 If this error is logged by an AP processor, the failure occurred in the AP IP communication
bus. If this error is logged by an FD or maintenance processor, the failure occurred in
the FD IP communication bus.
2 The failure occurred in the common IP communication bus.
3 This failure is detected by the interrupt service routine that processes the
communications. An receive error (i.e. RX status) will cause the received
communication packet to be ignored by the receiving processor.
4 When this error occurs, data may have been lost.
5 Since the AP processor uses DMA channel 2 for analog input, a DMA 2 failure logged
by an AP processor could indcate that the analog input service routine or analog input
hardware has failure instead of the ARINC 429 ASIC.
6 This error will not be logged if both pitch and roll commmands are invlaid or if the system
is configed as a SCAS/ATT system.
7 Only if this monitor was caused by a body rate validity failure and not a body rate out of
range failure.