Você está na página 1de 231

ELECTRONIC AND AVIONICS SYSTEMS

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

E 1997 ALLIEDSIGNAL, INC.

REPRODUCTION OF THIS PUBLICATION OR ANY PORTION


THEREOF BY ANY MEANS WITHOUT THE EXPRESS WRITTEN
PERMISSION OF ALLIEDSIGNAL COMMERCIAL AVIONICS
SYSTEMS IS PROHIBITED. FOR FURTHER INFORMATION
CONTACT THE MANAGER, TECHNICAL PUBLICATIONS, AL-
LIEDSIGNAL COMMERCIAL AVIONICS SYSTEMS, 400 NORTH
ROGERS ROAD, OLATHE, KANSAS, 66062. TELEPHONE: (913)
768--2398.
BENDIX/KING
KFC 500
FLIGHT COMPUTER

TABLE OF CONTENTS

SECTION I
GENERAL INFORMATION

Paragraph Page

1.1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--1


1.2 SYSTEM DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--3
1.3 MODES OF OPERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--8
1.4 SYSTEM TECHNICAL CHARACTERISTICS . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--9
1.5 KFC500 FLIGHT CONTROL SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--10
1.6 UNIT TECHNICAL CHARACTERISTICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--11
1.7 UNITS AND INSTALLATION KITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--45
1.8 ACCESSORIES REQUIRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--50
1.9 ACCESSORIES REQUIRED BUT SUPPLIED SEPARATELY . . . . . . . . . . . . . 1--50
1.10 GOVERNMENT APPROVAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--50
SECTION II
INSTALLATION

Paragraph Page

2.1 GENERAL INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--1


2.2 UNPACKING AND INSPECTING EQUIPMENT . . . . . . . . . . . . . . . . . . . . . . . . . 2--1
2.3 MOUNTING INSTRUCTIONS AND ILLUSTRATIONS . . . . . . . . . . . . . . . . . . . . 2--1
SECTION III
OPERATION

Paragraph Page

3.1 GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--1


SECTION IV
STC APPROVALS AND SYSTEMS INTERCONNECTS

Paragraph Page

4.1 GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--1

Revision 0, Dec 1997


CS:15546M00.IDU i
BENDIX/KING
KFC 500
FLIGHT COMPUTER

SECTION V
THEORY OF OPERATION

Paragraph Page

5.1 SYSTEM OPERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--1


5.1.2 FCC FD Processor Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--7
5.1.3 FCC AP Processor Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--8
5.1.4 FCC Maintenance Processor Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--10
5.1.5 Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--11
5.1.6 Force Trim System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--11
5.1.7 Interface to Servos and Control Positions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--12
5.2 Flight Director Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--13
5.2.1 Horizontal FD Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--15
5.2.2 Vertical FD Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--16
5.2.3 FD Modes Reference Adjustments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--18
5.2.4 FD Mode Engagement/Disengagement Requirements . . . . . . . . . . . . . . . . . . . 5--19
5.3 AP and SCAS Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--22
5.3.1 SCAS Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--22
5.3.2 AP Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--23
5.3.3 Force Trim System Interaction with AP Mode and SCAS Mode . . . . . . . . . . . . 5--25
5.3.4 Autotrim in AP Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--25
5.3.5 Annunciation of AP Mode and SCAS Mode Engagement . . . . . . . . . . . . . . . . . 5--25
5.3.6 Annunciation of AP Mode and SCAS Mode Failures . . . . . . . . . . . . . . . . . . . . . 5--26
5.3.7 Clearing AP and SCAS Mode Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--26
SECTION VI
REMOTE TERMINAL INTERFACE

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

Revision 0, Dec 1997


ii CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT COMPUTER

SECTION VII
MAINTENANCE

Paragraph Page

7.1 The Maintenance Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--2


7.2 Servo Axis Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--2
7.2.1 Primary Servo Axis Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--3
7.2.2 Trim Servo Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--7
7.3 Cockpit Annunciators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--8
7.4 Control Position Resolvers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--8
7.5 Analog Input of Radar Altitude . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--9
7.6 KRG 333 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--9
7.7 Directional Gyro Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--10
7.8 Vertical Gyro Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--10
7.9 Interface with the MSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--11
7.10 Cockpit Switches Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--11
7.11 Air Data Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--13
7.12 EFIS Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--15
7.13 Aural Annunciator Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--17
APPENDIX A
ERROR CODES

Paragraph Page

General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A--1

Revision 0, Dec 1997


CS:15546M00.IDU iii
BENDIX/KING
KFC 500
FLIGHT COMPUTER

ILLUSTRATIONS

Figure Page

1--1 KFC 500 SYSTEM BLOCK DIAGRAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--5


1--2 KFC 500 POWER DISTRIBUTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--6
1--3 P5201 CONNECTOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--17
1--4 P5202 CONNECTOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--20
1--5 P5203 CONNECTOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--23
1--6 P8001 CONNECTOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--24
1--7 KCP 520 FLIGHT CONTROL COMPUTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--25
1--8 KMS 540 Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--28
1--9 KMS 541 FRONT PANEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--28
1--10 KSM 575 LINEAR ACTUATOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--33
1--11 KSA 572 TRIM SERVO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--36
1--12 CONTROL POSITION SYNCHRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--38
1--13 KRG 333 RATE/ACCELERATION SENSOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--42
1--14 KAV 485 Altitude/Vertical Speed Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--44
2--1 KA 51B OUTLINE AND MOUNTING DRAWING . . . . . . . . . . . . . . . . . . . . . . . . 2--3
2--2 KCM 100 OUTLINE AND MOUNTING DRAWING . . . . . . . . . . . . . . . . . . . . . . . 2--5
2--3 KSG 105 OUTLINE AND MOUNTING DRAWING . . . . . . . . . . . . . . . . . . . . . . . 2--7
2--4 KMT 112 OUTLINE AND MOUNTING DRAWING . . . . . . . . . . . . . . . . . . . . . . . 2--9
2--5 KRG 333 OUTLINE AND MOUNTING DRAWING . . . . . . . . . . . . . . . . . . . . . . . 2--11
2--6 KVG 350 OUTLINE AND MOUNTING DRAWING . . . . . . . . . . . . . . . . . . . . . . . 2--13
2--7 KRA 405 OUTLINE AND MOUNTING DRAWING . . . . . . . . . . . . . . . . . . . . . . . 2--15
2--8 KDC 481 OUTLINE AND MOUNTING DRAWING . . . . . . . . . . . . . . . . . . . . . . . 2--17
2--9 KAV 485 OUTLINE AND MOUNTING DRAWING . . . . . . . . . . . . . . . . . . . . . . . 2--19
2--10 KCP 520 OUTLINE AND MOUNTING DRAWING . . . . . . . . . . . . . . . . . . . . . . . 2--21
2--11 KMS 540/541 OUTLINE AND MOUNTING DRAWING . . . . . . . . . . . . . . . . . . . 2--25
2--12 KSA 572 OUTLINE AND MOUNTING DRAWING . . . . . . . . . . . . . . . . . . . . . . . 2--27
2--13 KSM 575 OUTLINE AND MOUNTING DRAWING . . . . . . . . . . . . . . . . . . . . . . . 2--29
2--14 KSM 575 OUTLINE AND MOUNTING DRAWING . . . . . . . . . . . . . . . . . . . . . . . 2--31
2--15 KSM 575 OUTLINE AND MOUNTING DRAWING . . . . . . . . . . . . . . . . . . . . . . . 2--33
5--1 KCP520 BLOCK DIAGRAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--3
5--2 KCP 520 DISCRETE INPUT/OUTPUT BLOCK DIAGRAM . . . . . . . . . . . . . . . 5--4
6--1 Power--up Message Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--1
6--2 Normal Mode Main Menu Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--1
6--3 Time and Temperature Information Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--2
6--4 History Log Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--3
6--5 Logged Data Main Menu Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--3
6--6 Error Log Dump Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--4
6--7 Diagnostic Mode Confirmation Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--5
6--8 Normal Diagnostic Mode Entry Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--6
6--9 Diagnostic Mode Main Menu Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--6
6--10 Automated Test Selection Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--7
6--11 Automated Test Results Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--7
6--12 Manual Test Selection Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--8
6--13 Processor Selection Screen (no processors selected) . . . . . . . . . . . . . . . . . . . . 6--8
6--14 Processor Selection Screen (AP processors selected) . . . . . . . . . . . . . . . . . . . 6--9
6--15 AP Processor Discrete Input/Output Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--10
6--16 FD Processor Discrete Input/Output Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--10

Revision 0, Dec 1997


iv CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT COMPUTER

Figure Page

6--17 AP Processor Analog Input/Output Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--11


6--18 FD Processor ARINC 429 Input/Output Screen . . . . . . . . . . . . . . . . . . . . . . . . . . 6--13
6--19 AP Processor ARINC 429 Input/Output Screen . . . . . . . . . . . . . . . . . . . . . . . . . 6--13
6--20 Installation Processor Selection Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--16
6--21 FD Processor Installation Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--17
6--22 AP Processor Installation Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--18
6--23 Primary Servo LVDT Installation Pass/Fail Message Screen . . . . . . . . . . . . . . 6--19
6--24 Control Position Installation Pass/Fail Message Screen . . . . . . . . . . . . . . . . . . 6--20
6--25 Data Dump Processor Selection Screen (no processors selected) . . . . . . . . . 6--21
6--26 Data Dump Processor Selection Screen (AP A processor selected) . . . . . . . . 6--21
6--27 Data Dump Start Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--21
6--28 Data Dump Completion Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--21
6--29 Diagnostic Mode Entry Failure Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--22
7--1 DISCRETE INFORMATION FOR PITCH SERVO . . . . . . . . . . . . . . . . . . . . . . . . 7--5
7--2 ANALOG INFORMATION FOR PITCH SERVO (PROCESSED DATA) . . . . . 7--5
7--3 ANALOG INFORMATION FOR PITCH SERVO (RAW DATA) . . . . . . . . . . . . . 7--6

Revision 0, Dec 1997


CS:15546M00.IDU v
BENDIX/KING
KFC 500
FLIGHT COMPUTER

TABLES

Table Page

1--1 KFC 500 System Components and Support Equipment . . . . . . . . . . . . . . . . . . 1--10


1--2 KCP 520 (P5201) PIN FUNCTION LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--14
1--3 KCP 520 (P5202) PIN FUNCTION LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--18
1--4 KCP 520 (P5203) PIN FUNCTION LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--21
1--5 KCP 520 (J8001) PIN FUNCTION LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--24
5--1 FLIGHT DIRECTOR HORIZONTAL MODES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--20
5--2 FLIGHT DIRECTOR VERTICAL MODES INPUTS . . . . . . . . . . . . . . . . . . . . . . . 5--21
6--1 ARINC 429 WORD HEXADECIMAL GROUPINGS BY BIT NUMBER . . . . . . 6--15
6--2 ARINC 429 SIGN STATUS MATRIX INTERPRETATION . . . . . . . . . . . . . . . . . . 6--15
6--3 Conversion of Hexadecimal to Binary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--16
6--4 Signals to Monitor for FD Processor Only Diagnostic Mode . . . . . . . . . . . . . . . 6--23
6--5 AP Processor Discrete Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--25
6--6 AP Processor Discrete Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--26
6--7 FD Processor Discrete Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--27
6--8 AP PROCESSOR ANALOG INPUTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--28
6--9 AP PROCESSOR ANALOG OUTPUTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--29
7--1 UNIT DIANOSTIC CONNECTOR SIGNAL PINS . . . . . . . . . . . . . . . . . . . . . . . . 7--2
7--2 PRIMARY SERVO CONTROL INPUT/OUTPUTS FROM THE FCC . . . . . . . . 7--5
7--3 Trim Servo Control Input/Outputs from the FCC . . . . . . . . . . . . . . . . . . . . . . . . . 7--7
7--4 AP Processor Discrete Port Values for Cockpit Annunciators . . . . . . . . . . . . . . 7--8
7--5 Control Position Resolver Analog Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--9
7--6 KRG 333 Analog Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--9
7--7 Vertical Gyro Analog Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7--10
7--8 ARINC 429 Information Received from the MSP . . . . . . . . . . . . . . . . . . . . . . . . . 7--11
7--9 Cockpit Switches Discrete Inputs to AP Processor . . . . . . . . . . . . . . . . . . . . . . . 7--12
7--10 Cockpit Switches Discrete Inputs to FD processor . . . . . . . . . . . . . . . . . . . . . . . 7--12
7--11 ARINC 429 Information Received from the Air Data System . . . . . . . . . . . . . . 7--13
7--12 ARINC 429 Information Received from the EFIS . . . . . . . . . . . . . . . . . . . . . . . . 7--16
7--13 AP Processor Discrete Output Values for Setting Aural Tone Frequency . . . . 7--17
7--14 AP Processor Discrete Output Values for Setting Aural Tone Amplitude . . . . 7--17

Revision 0, Dec 1997


vi CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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

Revision 0, Dec 1997 Page 1--1


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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

Page 1--2 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

1.2 SYSTEM DESCRIPTION


This section provides a description of the KFC 500 Automatic Flight Control System as installed on
the Bell 430 helicopter. The AFCS is composed of one KCP 520 Flight Control Computer, one KMS
540 or KMS 541 Mode Select Panel, one KCM 100 configuration module, three KSM 575 linear
actuator assemblies, three KSA 572 trim actuators, three spring cartridge assemblies, four control
position synchros, and one KRG 333 Triaxial Rate/Acceleration sensor.
Table 1--1 lists the components and part numbers that comprise the KFC 500 system. Figure 1--1
shows a block diagram of the KFC 500 system as installed on the Bell 430. Figure 1--2 shows power
distribution for the AFCS.
The KFC 500 system is a three axis (pitch, roll, and yaw) flight control system with flight director.
The heart of the system is the KCP 520 Flight Control Computer. The KCP 520 receives mode
requests and engages valid AFCS flight modes. Servo motor commands are also generated by the
KCP 520 when in coupled flight to provide aircraft control. The three KSM 575 linear actuators form
part of the basic aircraft control rods for control of the helicopter. The three KSA 572 trim actuators
are used for autopilot autotrim and provide the basic ship force trim system.
The AFCS flight modes are requested by the KMS 540 or KMS 541 mode select panel. The KMS
540 and KMS 541 are microcontroller based push button control panels used to select and display
selected flight modes. The KMS 540 provides both AFCS and Flight Director mode control and the
KMS 541 is used in systems without Flight Director to provide basic AP and SCAS mode
annunciation and control.
The KCP 520 receives inputs from one KVG 350 vertical gyro, one KCS 305 compass system, and
one KRG 333 rate/acceleration sensor in all system configurations. Also, a KCM 100 configuration
module is installed with the system to maintain configuration information which is specific to a
particular aircraft. Additional inputs are required from an airdata source, a radar altimeter, and an
electronic flight control indicator system for flight director modes. The KAD 480 airdata system
provides airdata information to the KFC 500 system.
A KRA 405 Radar Altimeter provides radar altitude information to the KFC 500 system. The
Rogerson and Kratos EFIS provides the display for flight director command bars and attitude, as
well as heading and navigation inputs required.
The KAD 480 system and the KRA 405 Radar Altimeter are not considered part of the basic system
and are not required in a basic AP and SCAS mode system configuration.

Revision 0, Dec 1997 Page 1--3


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

1.2.1. PRODUCT SUPPORT


When the KFC 500 AFCS system exhibits a failure not described in the following sections, it must
be taken to an ASCAS Approved Sales and Service Center for repair. For the KFC 500 system, the
Approved Sales and Service Center must have an ASCAS service category rating of 5H. These
Approved Sales and Service Centers have maintenance manuals, test sets, tools and trained
personnel approved by ASCAS to perform troubleshooting and repair on the equipment on which
they are rated. Maintenance and troubleshooting information that would normally be available at
these Approved Sales and Service Centers is not duplicated in this document. A list of ASCAS
Approved Sales and Service Centers can be obtained from ASCAS Product Services, (USA)
913--782--0600.
1.2.2 AIRWORTHINESS LIMITATIONS
There are no components in the KFC 500 system that have a limit to the number of hours before
retirement from service. All units are repaired/replaced on a failure basis.

Page 1--4 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Optional
equipment, KRA 405 KVG 350 KCS 305
Only needed for Radar Vertical compass
flight director
system
Altimeter Gyro system

pitch axis KSM 575


pitch
servo commands linear actuator
attitude heading/ (pitch axis)
radar
compass
altitude
roll information
attitude

KSA 572 pitch axis


trim servo control position
Mode
(pitch axis) resolver
Controller engaged mode information

(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

Electronic NAV deviation, heading,


KSM 575
Flight selected course, etc.
linear actuator
Instrument
(yaw axis)
System
yaw axis
servo feedback

KSA 572 yaw axis


mode/failure test trim servo control position
Optional
annunciations signal pitch, roll,
equipment, (yaw axis) resolver
IIDS Display during and yaw
Only needed for
PFT body rates
flight director
system
AFCS lateral and
Aural normal
Trim/detent
Warning accelerations
switch
information

collective axis
Force aircraft KRG 333 collective
control position feedback
Trim speaker acceleration/ control position
System rate sensor resolver

Note : Servo feedback includes motor voltage, motor current,


servo position (LVDT position for KSM 575 or control position
for KSA 572), and brake engagement status

FIGURE 1--1 KFC 500 SYSTEM BLOCK DIAGRAM


(Sheet 1 of 1)

Revision 0, Dec 1997 Page 1--5


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 1--2 KFC 500 POWER DISTRIBUTION


(Sheet 1 of 2)

Page 1--6 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 1--2 KFC 500 POWER DISTRIBUTION


(Sheet 2 of 2)

Revision 0, Dec 1997 Page 1--7


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

1.3 MODES OF OPERATION

MODE GUIDANCE DISPLAY PROVIDED


Roll Attitude Hold Will maintain current roll attitude unless less
than 6. At less than 6 autopilot will return to
level attitude and maintain.
Heading Select Will maintain selected heading on HSI.
Navigation (VOR, LOC & LNAV) Provides Roll commands to capture and track
navigational beams.

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.

Page 1--8 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

1.4 SYSTEM TECHNICAL CHARACTERISTICS


The KFC 500 Flight Control System technical characteristics are listed as follows:
1.4.1 PERFORMANCE LIMITS AND ACCURACIES.

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

Revision 0, Dec 1997 Page 1--9


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

1.5 KFC500 FLIGHT CONTROL SYSTEM


1.5.1 Components

KFC500 SYSTEM COMPONENTS


Unit Description Model No. Part No.
Flight Control Computer KCP 520 065--00158--0202
Mode Select Panel KMS 540 065--00159--0501
Mode Select Panel KMS 541 065--00168--0101
Linear Actuator Assembly (Pitch) KSM 575 065--00167--0200
Linear Actuator Assembly (Roll) KSM 575 065--00167--0100
Linear Actuator Assembly (Yaw) KSM 575 065--00167--0500
Trim Actuator (Roll) KSA 572 065--00162--0100
Trim Actuator (Pitch and Yaw) KSA 572 065--00162--0200
Triaxial Rate/Accelerometer Sensor KRG 333 060--00040--0100
Configuration Module KCM 100 071--00073--5000
Vertical Gyro KVG 350 060--00026--0000
Slaved Gyro (part of KCS 305) KSG 105 060--00013--0001
Flux Valve (part of KCS 305) KMT 112 071--01052--0000
Slaving Accessory (part of KCS 305) KA 51B 071--01242--0003
Control Position Synchros 148--00091--0000
ADDITIONAL REQUIRED EQUIPMENT FOR FLIGHT DIRECTOR
Unit Description Model No. Part No.
Air Data Computer KDC 481T 065--00082--0012
SW--02 or greater
Air Data Adapter Module 065--05041--0021
Altimeter Vertical Speed Indicator KAV 485 066--03077--0064
Radar Altimeter KRA 405 066--01048--0002
TABLE 1--1 KFC 500 System Components and Support Equipment

Page 1--10 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

1.6 UNIT TECHNICAL CHARACTERISTICS


This section provides an illustration and a brief description of each component used in the KFC 500
AFCS.
1.6.1 KCP 520 FLIGHT CONTROL COMPUTER
1.6.1.1 Description
The KCP 520 FCC is a remote mounted flight control computer for the KFC 500 and contains all
of the mode logic, command computations, servo control, and critical hardware and software
monitors for flight director and SCAS/AP coupled flight. It interfaces with the systems and
equipment listed in Table 1--1 of this document. The FCC is housed in a remote rack mounted, 3/8
ATR form factor chassis for ease of rack and aircraft harness design. The FCC uses rear--mounted
ARINC style connectors for interface to the aircraft harness. A front--mounted connector is provided
on the unit for test and maintenance without the requirement of removing the unit from the aircraft
harness.
NOTE
The test connector on the FCC is generally covered by a front
cover plate in the aircraft. This cover plate should be removed to
access the test connector. The RS232 bus interface is also
supplied in the Bell 430 installation inside the cabin for easy
connection to the diagnostic computer.
1.6.2.2 Technical Characteristics
SPECIFICATION CHARACTERISTIC
SIZE: Length: 14.65(372.10mm)
with rack 17.63(447.8mm)
Height: 7.63(193.29mm)
with rack 8.24(209.30mm)
Width: 3.66(92.96mm)
with rack 3.821(97.05mm)
WEIGHT: 10.6lbs(4.8kg)
MOUNTING: Rack mount with four #8--32 screws
MATING CONNECTOR PN 030--03039--0001
TSO COMPLIANCE: C9c, C52a
DO--160C ENVIRONMENTAL CATEGORIES A2F2/Z/BA/MNYB/E1XXXXXA/BZ/AB/BZ/
ZYZ/A3XX/XX
POWER INPUTS: 28VDC FD Pilot/Man .25A nom/2.0A Max
28VDC Audio .1A nom/.2A Max
28VDC AP 5.0A nom/10.0A Max
28VDC Power Return <.3V drop max
@ 6.0A nom/15.0A Max
POWER OUTPUTS: +5V and Ground for Configuration Module.

Revision 0, Dec 1997 Page 1--11


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

SIGNAL INPUTS:-- Discrete Inputs


Open/Ground and Open/+28VDC

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

Page 1--12 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

SIGNAL OUTPUTS: Discrete Outputs


Brake Soleniod Drivers (source)
V(5203 6,22,24,28,52,54) -- Vout<1.2V @ test
load
Brake Solenoid Drivers (Sink)
V(5203 7,12,23,27,42,53) Vout< .8VDC

Engage Solenoid Drivers (source)


V(5202 17,26,28) -- Vout < 1.2V @ test load
Engage Solenoid Drivers (Sink)
V(5203 21,27,29) -- Vout <1.2V @ test load

SCAS Fail (sink) 5201--74


KRG 333 PFT Test (sink) 5201--78
Roll Fail (sink) 5202--51
Pitch Fail (sink) 5202--52
Yaw Fail (sink) 5202--39
AP Fail (sink) 5203--37
AP ON Annunciators 5203--38
AP Fail Annunciation 5203--40
SCAS ON Annunciators 5203--50

Annunciator Drivers Vout<.5VDC


Relay Solenoid Drivers (source)
V(5202 4,5) -- Vout<1.2V

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

Revision 0, Dec 1997 Page 1--13


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

P5201 O I Pin Name


Pin No U N
T

1 ---------------------------------------- ! PILOT FLT DIR XSIDE 429 REC B


2 ---------------------------------------- ! FMS 2 429 REC A
3 ---------------------------------------- ! FMS 1 429 REC A
4 ---------------------------------------- ! FMS 1 429 REC B
5 ---------------------------------------- ! SPARE AP DISCRETE INPUT/OUTPUT 4
6 ---------------------------------------- ! PILOT FLT DIR DISABLE
7 ---------------------------------------- ! LAT ACCEL HI
8 ---------------------------------------- ! LAT ACCEL LO
9 ---------------------------------------- ! NORM ACCEL HI
10 ---------------------------------------- ! NORM ACCEL LO
11 ---------------------------------------- ! LONG ACCEL HI
12 ---------------------------------------- ! LONG ACCEL LO
13 ---------------------------------------- ! PILOT FLT DIR XSIDE 429 REC A
14 ---------------------------------------- ! PILOT DISPLAY ONSIDE 429 REC A
15 ---------------------------------------- ! PILOT DISPLAY ONSIDE 429 REC B
16 ---------------------------------------- ! FMS 2 429 REC B
17 ---------------------------------------- ! DG HEADING Z
18 ---------------------------------------- ! DG REFERENCE +
19 ---------------------------------------- ! Collective Position SIN
20 ---------------------------------------- ! YAW Pedal Position SIN
21 ---------------------------------------- ! YAW Pedal Position COSIN
22 ---------------------------------------- ! Roll Cyclic Position COSIN
23 ---------------------------------------- ! Roll Cyclic Position REFERENCE
24 ---------------------------------------- ! Pitch Cyclic Position REFERENCE
25 ---------------------------------------- ! Pitch Cyclic Position SIN
26 ---------------------------------------- ! PILOT ATT/HDG 429 REC A
27 ---------------------------------------- ! PILOT ATT/HDG 429 REC B
28 ---------------------------------------- ! COPILOT ATT/HDG 429 REC A (RESERVED)
29 ---------------------------------------- ! COPILOT ATT/HDG 429 REC B (RESERVED)
30 ---------------------------------------- ! AP SPARE 1 429 REC B
31 ---------------------------------------- ! DG HEADING X
32 ---------------------------------------- ! DG HEADING Y
33 ---------------------------------------- ! POSITION REFERENCE +
34 ---------------------------------------- ! POSITION REFERENCE --
35 ---------------------------------------- ! Collective Position COSIN
36 ---------------------------------------- ! Collective Position REFERENCE
37 ---------------------------------------- ! YAW Pedal Position REFERENCE
38 ---------------------------------------- ! Roll Cyclic Position SIN
39 ---------------------------------------- ! Pitch Cyclic Position COSIN
40 ---------------------------------------- ! COPILOT DISPLAY XSIDE 429 REC B (RESERVED)
41 ---------------------------------------- ! COPILOT DISPLAY XSIDE 429 REC A (RESERVED)
42 ---------------------------------------- ! PILOT DISPLAY XSIDE 429 REC A
43 ---------------------------------------- ! PILOT DISPLAY XSIDE 429 REC B
44 ---------------------------------------- ! DG REFERENCE --
45 ---------------------------------------- ! PERFORMANCE STRAP 1

TABLE 1--2 KCP 520 (P5201) PIN FUNCTION LIST

Page 1--14 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

P5201 O I Pin Name


Pin No U N
T
46 ---------------------------------------- ! PERFORMANCE STRAP 0
47 ---------------------------------------- ! ACCEL VALID
48 ---------------------------------------- ! RG SENSE --15V
49 ---------------------------------------- ! RG SENSE +15V
50 ---------------------------------------- ! DG VALID
51 ---------------------------------------- ! VG1 VALID
52 ---------------------------------------- ! VG2 VALID
53 ---------------------------------------- ! PILOT FLT DIR SPARE1 429 REC B
54 ---------------------------------------- ! PILOT FLT DIR SPARE1 429 REC A
55 ---------------------------------------- ! COPILOT DISPLAY ONSIDE 429 REC A (RESERVED)
56 ---------------------------------------- ! COPILOT DISPLAY ONSIDE 429 REC B (RESERVED)
57 ---------------------------------------- ! AP SPARE1 429 REC 1
58 z ---------------------------------------- PILOT GENERAL 429 XMTR B
59 z ---------------------------------------- PILOT CONTROL 429 XMTR B
60 ---------------------------------------- ! ROLL RATE 1 Hi
61 ---------------------------------------- ! ROLL RATE 1 Lo
62 z ---------------------------------------- AURAL ALERT HI
63 ---------------------------------------- FLT DIR SELECT
64 ---------------------------------------- ! AP ENGAGE SWITCH
65 ---------------------------------------- ! YAW DAMP ENGAGE SWITCH
66 z ---------------------------------------- AURAL ALERT LO
67 ---------------------------------------- ! PILOT AIRDATA 429 REC B
68 ---------------------------------------- ! PILOT AIRDATA 429 REC A
69 ---------------------------------------- ! COPILOT AIRDATA 429 REC A (RESERVED)
70 ---------------------------------------- ! COPILOT AIRDATA 429 REC B (RESERVED)
71 ---------------------------------------- ! PERFORMANCE STRAP 2
72 z ---------------------------------------- MISTRIM (IIDS)
73 ---------------------------------------- ! PERFORMANCE STRAP 3
74 z ---------------------------------------- SCAS FAIL (IIDS)
75 ---------------------------------------- ! PERFORMANCE STRAP 4
76 ---------------------------------------- ! RADAR ALTITUDE 2 VALID
77 ---------------------------------------- ! SELF TEST
78 z ---------------------------------------- ACCEL/RATE TEST
79 ---------------------------------------- ! RATE VALID
80 ---------------------------------------- ! COPILOT FLT DIR SPARE1 429 REC B (RESERVED)
81 ---------------------------------------- ! COPILOT FLT DIR SPARE1 429 REC A (RESERVED)
82 ---------------------------------------- ! COPILOT FLT DIR SPARE2 429 REC B (RESERVED)
83 ---------------------------------------- ! COPILOT FLT DIR SPARE2 429 REC A (RESERVED)
84 ---------------------------------------- ! GROUND CONFIGURATION MODULE
85 z ---------------------------------------- PILOT FLT DIR XSIDE/COPILOT GENERAL 429 XMTR B
(RESERVED)
86 z ---------------------------------------- PILOT FLT DIR XSIDE/COPILOT GENERAL 429 XMTR A
(RESERVED)
87 z ---------------------------------------- PILOT CONTROL 429 XMTR A
88 ---------------------------------------- ! PILOT CONTROL 429 REC B
89 ---------------------------------------- ! PILOT CONTROL 429 REC A
90 ---------------------------------------- ! RADAR ALTITUDE 1 STRAP
91 ---------------------------------------- ! RADAR ALTITUDE 2 STRAP
92 ---------------------------------------- ! STRAP PARITY
93 ---------------------------------------- ! RADAR ALTITUDE 1 VALID

Revision 0, Dec 1997 Page 1--15


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

P5201 O I Pin Name


Pin No U N
T
94 z ---------------------------------------- AP XSIDE XMTR A
95 z ---------------------------------------- AP XSIDE XMTR B
96 ---------------------------------------- ! AP XSIDE REC A
97 ---------------------------------------- ! AP XSIDE REC B
98 z ---------------------------------------- PILOT GENERAL 429 XMTR A
99 ---------------------------------------- ! SPARE ANALOG INPUT LO
100 ---------------------------------------- ! SPARE ANALOG INPUT HI
101 ---------------------------------------- ! YAW FTE
102 ---------------------------------------- ! CYCLIC FTR
103 ---------------------------------------- ! CYCLIC FTE
104 ---------------------------------------- ! GA ENGAGE SWITCH
105 ---------------------------------------- ! COLLECT ENGAGE SWITCH
106 ---------------------------------------- ! SCAS ENGAGE SWITCH

Page 1--16 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 1--3 P5201 CONNECTOR

Revision 0, Dec 1997 Page 1--17


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

P5202 O I Pin Name


Pin No U N
T
1 z ---------------------------------------- YAW LVDT EXCITATION +
2 ---------------------------------------- ! ROLL LVDT Position +
3 ---------------------------------------- ! AIRCRAFT GROUND
4 ---------------------------------------- ! +28VDC AP
5 ---------------------------------------- ! +28VDC AP
6 z ---------------------------------------- PITCH LVDT EXCITATION +
7 ---------------------------------------- ! PILOT COMPOSITE
8 ---------------------------------------- ! SCAS DISCONNECT SWITCH
9 ---------------------------------------- ! YAW LVDT POSITION --
10 z ---------------------------------------- YAW LVDT EXCITATION --
11 z ---------------------------------------- ROLL LVDT EXCITATION --
12 ---------------------------------------- ! PITCH LVDT Position --
13 z ---------------------------------------- FCS RS232 TX
14 ---------------------------------------- ! FCS RS232 COMMON
15 ---------------------------------------- ! PILOT FLT DIR HDG/NAV DISABLE
16 ---------------------------------------- ! JAR AWO
17 z ---------------------------------------- +5V CONFIGURATION MODULE
18 ---------------------------------------- ! YAW FTR
19 ---------------------------------------- ! ROLL LVDT Position --
20 ---------------------------------------- ! ROLL LVDT COMMON
21 ---------------------------------------- ! COLLECT FTE
22 ---------------------------------------- ! PITCH LVDT COMMON
23 ---------------------------------------- ! COLLECT FTR
24 z ---------------------------------------- FCS RS232 RTS
25 ---------------------------------------- ! FCS RS232 RX
26 ---------------------------------------- ! PILOT ALTERNATE AIRDATA
27 ---------------------------------------- ! FD DISPLAY SELECT
28 ---------------------------------------- ! PILOT FLT DIR SPARE INPUT 1
29 ---------------------------------------- ! PILOT ADI DOWN
30 ---------------------------------------- ! AP DISCONNECT SWITCH
31 ---------------------------------------- ! YAW LVDT COMMON
32 ---------------------------------------- ! YAW DAMP DISCONNECT SWITCH
33 ---------------------------------------- ! YAW LVDT POSITION +
34 z ---------------------------------------- ROLL LVDT EXCITATION +
35 ---------------------------------------- ! PITCH LVDT Position +
36 z ---------------------------------------- PITCH LVDT EXCITATION --
37 ---------------------------------------- ! AP DISABLE
38 ---------------------------------------- ! FCS RS232 CTS
39 z ---------------------------------------- YAW FAIL (IIDS)
40 z ---------------------------------------- ! DATA CONFIGURATION MODULE
41 z ---------------------------------------- ENABLE CONFIGURATION MODULE
42 z ---------------------------------------- PITCH API
43 ---------------------------------------- ! YAW DAMP DISABLE
44 ---------------------------------------- ! COLLECT DISABLE
45 ---------------------------------------- ! AP DISCONNECT RESET
46 ---------------------------------------- ! YAW INTERRUPT
47 ---------------------------------------- ! HYDRAULIC PRESSURE VALID (PC1)
48 ---------------------------------------- ! SPARE DISCRETE INPUT 1

TABLE 1--3 KCP 520 (P5202) PIN FUNCTION LIST

Page 1--18 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

P5202 O I Pin Name


Pin No U N
T
49 ---------------------------------------- ! SPARE DISCRETE INPUT 2
50 z ---------------------------------------- YAW API
51 z ---------------------------------------- ROLL FAIL (IIDS)
52 z ---------------------------------------- PITCH FAIL (IIDS)
53 z ---------------------------------------- CLOCK CONFIGURATION MODULE
54 z ---------------------------------------- ROLL API
55 ---------------------------------------- ! SPARE DISCRETE INPUT 3
56 ---------------------------------------- ! FORCE TRIM CB
57 ---------------------------------------- ! +28VDC AUDIO
58 z ---------------------------------------- PITCH DRIVE +
59 z ---------------------------------------- PITCH DRIVE --
60 z ---------------------------------------- ROLL DRIVE +
61 z ---------------------------------------- ROLL DRIVE --
62 z ---------------------------------------- SPARE FD DISCRETE OUTPUT 2
63 z ---------------------------------------- SPARE FD DISCRETE OUTPUT 3
64 ---------------------------------------- ! +28VDC FLT DIR PILOT
65 z ---------------------------------------- FD DISPLAY COPILOT
66 z ---------------------------------------- FD DISPLAY PILOT
67 ---------------------------------------- ! +28VDC FLT DIR COPILOT/MAINTENANCE

Revision 0, Dec 1997 Page 1--19


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 1--4 P5202 CONNECTOR

Page 1--20 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

P5203 O I Pin Name


Pin No U N
T

1 ---------------------------------------- ! PITCH RATE 1 Hi


2 ---------------------------------------- ! PITCH RATE 1 Lo
3 z ---------------------------------------- AIRCRAFT GROUND
4 z ---------------------------------------- AIRCRAFT GROUND
5 z ---------------------------------------- AIRCRAFT GROUND
6 z ---------------------------------------- ROLL BRAKE RELEASE HI
7 z ---------------------------------------- ROLL BRAKE RELEASE LO
8 ---------------------------------------- ! RADAR ALTITUDE 2 LO
9 ---------------------------------------- ! RADAR ALTITUDE 2 HI
10 ---------------------------------------- ! VG2 ROLL ATTITUDE X
11 ---------------------------------------- ! VG2 ROLL ATTITUDE Y
12 z ---------------------------------------- PITCH BRAKE RELEASE LO
13 z ---------------------------------------- COLLECTIVE BRAKE RELEASE HI
14 z ---------------------------------------- COLLECTIVE BRAKE RELEASE LO
15 z ---------------------------------------- COLLECTIVE ENGAGE CLUTCH HI
16 z ---------------------------------------- COLLECTIVE ENGAGE CLUTCH LO
17 z ---------------------------------------- YAW TRIM ENGAGE CLUTCH HI
18 ---------------------------------------- ! RADAR ALTITUDE 1 LO
19 ---------------------------------------- ! RADAR ALTITUDE 1 HI
20 ---------------------------------------- ! VG2 PITCH ATTITUDE Z
21 z ---------------------------------------- YAW TRIM ENGAGE CLUTCH LO
22 z ---------------------------------------- YAW TRIM BRAKE RELEASE HI
23 z ---------------------------------------- YAW TRIM BRAKE RELEASE LO
24 z ---------------------------------------- ROLL TRIM ENGAGE CLUTCH HI
25 z ---------------------------------------- ROLL TRIM ENGAGE CLUTCH LO
26 z ---------------------------------------- ROLL TRIM BRAKE RELEASE HI
27 z ---------------------------------------- ROLL TRIM BRAKE RELEASE LO
28 z ---------------------------------------- PITCH TRIM ENGAGE CLUTCH HI
29 z ---------------------------------------- PITCH TRIM ENGAGE CLUTCH LO
30 ---------------------------------------- ! ROTOR TORQUE LO
31 ---------------------------------------- ! YAW RATE HI
32 ---------------------------------------- ! VG2 PITCH ATTITUDE Y
33 ---------------------------------------- ! ROTOR TORQUE HI
34 ---------------------------------------- ! VG2 ROLL ATTITUDE Z
35 ---------------------------------------- ! VG1 PITCH ATTITUDE Z
36 ---------------------------------------- ! VG1 PITCH ATTITUDE Y
37 z ---------------------------------------- AP FAIL (IIDS)
38 z ---------------------------------------- AP ON
39 z ---------------------------------------- AP DISC AUDIO--ALERT OUT
40 z ---------------------------------------- AP FAIL ANNUNCIATOR
41 z ---------------------------------------- PITCH TRIM BRAKE RELEASE HI
42 z ---------------------------------------- PITCH TRIM BRAKE RELEASE LO
43 ---------------------------------------- ! YAW RATE LO
44 ---------------------------------------- ! VG2 REFERENCE +
45 ---------------------------------------- ! VG2 REFERENCE --
46 ---------------------------------------- ! VG2 PITCH ATTITUDE X
47 ---------------------------------------- ! VG1 REFERENCE +

TABLE 1--4 KCP 520 (P5203) PIN FUNCTION LIST

Revision 0, Dec 1997 Page 1--21


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

P5203 O I Pin Name


Pin No U N
T
48 ---------------------------------------- ! VG1 REFERENCE --
49 ---------------------------------------- ! VG1 PITCH ATTITUDE X
50 z ---------------------------------------- SCAS ON ANNUNCIATOR
51 z ---------------------------------------- AFCS DISC (IIDS)
52 z ---------------------------------------- YAW BRAKE RELEASE HI
53 z ---------------------------------------- YAW BRAKE RELEASE LO
54 z ---------------------------------------- PITCH BRAKE RELEASE HI
55 ---------------------------------------- ! VG1 ROLL ATITITUDE Z
56 ---------------------------------------- ! VG1 ROLL ATTITUDE Y
57 ---------------------------------------- ! VG1 ROLL ATTITUDE X
58 z ---------------------------------------- YAW DRIVE +
59 z ---------------------------------------- YAW DRIVE --
60 z ---------------------------------------- PITCH TRIM DRIVE +
61 z ---------------------------------------- PITCH TRIM DRIVE --
62 z ---------------------------------------- ROLL TRIM DRIVE +
63 z ---------------------------------------- ROLL TRIM DRIVE --
64 z ---------------------------------------- YAW TRIM DRIVE +
65 z ---------------------------------------- YAW TRIM DRIVE --
66 z ---------------------------------------- COLLECTIVE DRIVE +
67 z ---------------------------------------- COLLECTIVE DRIVE --

Page 1--22 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 1--5 P5203 CONNECTOR

Revision 0, Dec 1997 Page 1--23


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

J8001 O I Pin Name


Pin No U N
T

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

TABLE 1--5 KCP 520 (J8001) PIN FUNCTION LIST


(Test Outputs Only)

FIGURE 1--6 P8001 CONNECTOR

Page 1--24 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 1--7 KCP 520 FLIGHT CONTROL COMPUTER


(Sheet 1 of 1)

Revision 0, Dec 1997 Page 1--25


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

1.6.2 KMS 540 MODE SELECT PANEL


1.6.2.1 Description
The KMS 540 MSP and KMS 541 MSP are panel mounted mode selectors for the KFC 500 system.
The KMS 540 MSP contains all of the mode switches for flight director and coupled flight. The KMS
541 MSP contains only mode switches for coupled flight (AP and SCAS mode control). The MSP
also interfaces with several cockpit mounted switches as detailed in section 7.10 of this document.
The MSP is housed in a 3 ATI panel mount package. It houses the pushbuttons described in the
following paragraphs, as noted. A rear mounted circular connector is provided for harness
interconnect.
1.6.2.2 Technical Characteristics

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:

Page 1--26 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

SIGNAL INPUTS: Discrete Inputs


Cyclic Beep Trim (CBT) Switch
Open/Gnd
Yaw and Collective Beep Trim Switches
Open/Gnd
GA, FDC/NAV STBY and Test Switches
Gnd/Open
FTE and Cyclic FTR Switches
+28/Open
Lamp Test Switch
Open/Gnd
SDI Strap Pins
Gnd/Open

SIGNAL OUTPUTS: Discrete Outputs


#9 thru #12 Engage
+12/Gnd
Analog Outputs
+5V Logic Monitor (test only)
+5+3%
Lamp_MNTR PWM voltage (test only)
+5V pulse width Modulated
Back_MNTR PWM voltage (test only)
+5V pulse width modulated
ARINC 429 Transmitter
ARINC 429 Receiver

Revision 0, Dec 1997 Page 1--27


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 1--8 KMS 540 Front Panel


(Sheet 1 of 1)

FIGURE 1--9 KMS 541 FRONT PANEL


(Sheet 1 of 1)

Page 1--28 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

1.6.2.3 MSP Buttons


The following are brief descriptions of the button operations for the MSP. For more detailed
information on mode engagement/disengagement, see sections 5.2 and 5.3 and their
sub--sections. The MSP relays button press information to the FCC. Actual mode
engagement/disengagement is performed by the FCC.
HDG BUTTON (1)
When this button is pressed, the HDG select mode will be engaged. Pressing this button when HDG
select mode is engaged will disengage HDG select and revert to the default horizontal mode (roll
attitude hold or heading hold). Note : This button is only present on the KMS 540 MSP.
NAV BUTTON (2)
When this button is pressed, the NAV mode will be armed. Pressing this button when NAV mode
is armed will disengage NAV arm (remaining in the engaged horizontal mode). Pressing this button
when NAV mode is engaged will disengage NAV mode and revert to the default horizontal mode
(roll attitude hold or heading hold). Note : This button is only present on the KMS 540 MSP.
APR BUTTON (3)
When this button is pressed, the APR mode will be armed. Pressing this button when APR mode
is armed will disengage APR arm (remaining in the engaged horizontal mode). Pressing this button
when APR mode is engaged will disengage APR mode and revert to the default horizontal mode
(roll attitude hold or heading hold). Note : This button is only present on the KMS 540 MSP.
BL BUTTON (4)
This button is used to select the maximum bank angle for non--approach flight director operation.
Each time this button is pressed, the BL value will change. The selected BL value can be 10, 15,
20 (default value), or 25 degrees. Note : This button is only present on the KMS 540 MSP.
ALT BUTTON (5)
When this button is pressed, ALT mode will be engaged. Pressing this button when ALT mode is
engaged will disengage ALT and revert to the default vertical mode (pitch attitude hold). Note : This
button is only present on the KMS 540 MSP.
VS BUTTON (6)
When this button is pressed, VS hold mode will be engaged. Pressing this button when VS hold
mode is engaged will disengage VS hold and revert to the default vertical mode (pitch attitude hold).
Note : This button is only present on the KMS 540 MSP.
IAS BUTTON (7)
When this button is pressed, IAS hold mode will be engaged. Pressing this button when IAS hold
mode is engaged will disengage IAS hold and revert to the default vertical mode (pitch attitude hold).
Note : This button is only present on the KMS 540 MSP.
AP BUTTON (8)
When this button is pressed, AP mode will be engaged (automatic flight control) in pitch, roll, and
yaw axes. Pressing this button with AP mode engaged will transfer system to the SCAS mode in
pitch, roll, and yaw axes.

Revision 0, Dec 1997 Page 1--29


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

SCAS BUTTON (9)


When this button is pressed, SCAS mode will be engaged (providing aircraft stabilization
assistance to the pilot) in pitch, roll, and yaw axes. Pressing this button with SCAS mode engaged
will disengage SCAS mode.
FD BUTTON (10)
When this button is pressed, the default horizontal mode (RAH or heading hold) and the default
vertical mode (PAH) are engaged. Pressing this button when the default horizontal mode and
default vertical mode are engaged will disengage the default horizontal and vertical modes, thus
removing flight director operation. Note : This button is only present on the KMS 540 MSP.
1.6.2.4 MSP Mode annunciators
Green mode annunciators are located directly above each mode select button on the MSP. When
a mode is engaged and the MSP is powered, the mode annunciation for the engaged mode
(corresponding to the button) will be annunciated. For example, if HDG select mode is engaged,
the green light above the HDG button on the MSP will be on. The mode annunciators dim
automatically with light intensity changes (see section 5.1.1.3 MSP Installation Mode for more
information).

NOTE
The annunciations can be tested by placing the BRT/DIM/TEST
switch on the overhead panel in the test position.

Page 1--30 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

1.6.3 KSM 575 LINEAR ACTUATOR ASSEMBLY


1.6.3.1 Description
The KSM 575 Linear Actuator assembly consists of a linear actuator, clevis, and control tube. The
linear actuator contains a DC torque motor, an LVDT position sensor, and a brake release solenoid.
All drive signals are generated in the FCC. The actuator assembly is in series with the control
system and is used as an actuator during active control by the autopilot and as a rigid control link
during pilot operation. The KSM 575s are supplied as assemblies from the factory with a
predetermined length established. This length is NOT field adjus and the actuator assembly should
NOT be disassembled in the field.
When modifying aircraft rigging, it is recommended that the actuator be replaced with a calibrated
rigging link since it is difficult to ensure that the actuator piston is in the correct position for aircraft
rigging.
The LVDT provides position feedback to the FCC to close the servo control loop for each of the linear
actuators. The external AC excitation is provided by the FCC.
The brake release solenoid is energized (to release the brake) whenever the autopilot is engaged.
Otherwise, the actuator is locked to provide manual control. The actuator design has sufficient
internal friction such that the aircraft hydraulic actuator can be driven without backdriving the
actuator motor when the brake is not engaged. This reduces the failure criticality of the brake
release solenoid.
The actuators have stroke lengths assigned by part number and must be installed as specified in
the installation data. Actuator motor brake wiring is coded to the connector pins for each axis. This
prevents operation of an actuator installed or connected in an incorrect position.
1.6.3.2 Technical Characteristics

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

Revision 0, Dec 1997 Page 1--31


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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

Page 1--32 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 1--10 KSM 575 LINEAR ACTUATOR


(Dwg No 300--05574--0000 R0, Sheet 1 of 1)

Revision 0, Dec 1997 Page 1--33


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Page 1--34 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

1.6.4 KSA 572 TRIM SERVO


1.6.4.1 Description
The KSA 572 Trim Actuator applies a force to the aircraft linkages about a clutch--fitted anchoring
point. It also allows displacing the anchoring point via an electrical drive system. The KSA 572
contains a DC motor, a brake release solenoid, and an engage clutch. Motor drive and brake
solenoid signals are generated in the FCC. The clutch is engaged whenever the force trim system
is turned on. The brake is engaged (i.e., the brake release solenoid is not powered) anytime the
autotrim function is not being used. The KFC 500 system controls only the brake and the motor
drive. Therefore, removal of the FCC does not prevent operation of the servo as a Magnetic Brake
system. There are three trim servos used in the KFC 500 system. The clutch and brake are
necessary to provide force trim for the helicopter.
1.6.4.2 Technical Characteristics

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

*In flight loss of cooling; Not applicable

Revision 0, Dec 1997 Page 1--35


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 1--11 KSA 572 TRIM SERVO


(Sheet 1 of 1)

Page 1--36 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

1.6.5 CONTROL POSITION SYNCHROS


1.6.5.1 Description
The control position synchros are used in the pitch, roll, yaw and collective axis for position sensing
of the controls. They are six wire (sine, cos, excitation) resolvers that converts mechanical
movement of the controls to electrical signals used by the FCC.
1.6.5.2 Technical Characteristics
Refer to figure 1--12.

Revision 0, Dec 1997 Page 1--37


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 1--12 CONTROL POSITION SYNCHRO


(Dwg No 148--00091--0000 R3, Sheet 1 of 3)

Page 1--38 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 1--12 CONTROL POSITION SYNCHRO


(Sheet 2 of 3)

Revision 0, Dec 1997 Page 1--39


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 1--12 CONTROL POSITION SYNCHRO


(Sheet 3 of 3)

Page 1--40 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

1.6.6 KRG 333 RATE/ACCELERATION SENSOR


1.6.6.1 Description
The KRG 333 provides normal and lateral acceleration outputs and pitch, roll, and yaw axis rate
outputs to the FCC. The gradient for normal (vertical) acceleration is 3 volts per G. The gradient
for lateral acceleration is 7.81 volts per G. The gradient for pitch, roll, and yaw axis rate is 200
millivolts per degree/second. All outputs signals from the KRG 333 are differential DC voltage
signals referenced to the KRG 333 signal ground. A positive signal with respect to the KRG 333
signal ground represents acceleration or rate in the forward, right, or upward direction. The KRG
333 valids are capable of sinking 0.030 milliamps maximum to less than 2 volts. The KRG 333 has
a test input which is exercised during the FCC preflight test mode. The test input is used to verify
that the KRG 333 inputs are being received by the FCC. See section 5.1.3.2 for more information
on the KRG 333 test.
1.6.6.2 Technical Characteristics

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

Revision 0, Dec 1997 Page 1--41


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 1--13 KRG 333 RATE/ACCELERATION SENSOR


(Sheet 1 of 1)

Page 1--42 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

1.6.7 KAV 485 ALTITUDE/VERTICAL SPEED INDICATOR


1.6.7.1 Description
The KAV 485 altitude/vertical speed indicator provides inputs to the flight director as described
below. For additional information on the KAV 485, see EFS 40/KAD 480 Maintenance Manual
Supplement 155--09646--0003 Rev 1 or later.
1.6.7.2 Technical Characteristics

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

Revision 0, Dec 1997 Page 1--43


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 1--14 KAV 485 Altitude/Vertical Speed Indicator


(Sheet 1 of 1)

Page 1--44 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

1.6.7.3 KAV 485 Buttons and Knobs


The following are brief descriptions of the button operations for the KAV 485. For more detailed
information on mode engagement/disengagement, see sections 5.2.2.3 and 5.2.4. As with the
MSP, the button press information from the KAV 485 is relayed to the FCC, which provides actual
mode engagement/disengagement.
VS ENG BUTTON (1)
When this button is pressed, VS hold mode will be engaged. Pressing this button when VS hold
mode is engaged will disengage VS hold and revert to the default vertical mode (pitch attitude hold).
ALT SEL BUTTON (2)
When this button is pressed, ALT mode will be armed to capture the altitude displayed in the altitude
select display. Pressing this button when ALT mode is armed will disengage ALT mode being armed
(i.e., selected altitude will not be captured when attained by the aircraft).
ALTITUDE SELECT/VERTICAL SPEED SELECT KNOB (3)
When this knob is pressed in, the selected altitude for engagement of ALT mode will be changed
when the knob is turned. When this knob is pulled out, the selected vertical speed for VS hold mode
will be changed when the knob is turned. When the selected altitude is changed using this knob
when the flight director is active (i.e., there is a vertical mode engaged), ALT mode will be armed
to capture the newly selected altitude automatically.
BARO CORRECTION ADJUST KNOB (4)
When this knob is turned, the correction factor for barometric pressure is adjusted to give correct
altitude readings based on the barometric pressure.
In HG/Hpc BUTTON (5)
Pressing this button toggles baro correction display between the two modes. Inches of mercury
(HG) and hecto pascal (HPc).

1.7 UNITS AND INSTALLATION KITS


The following is a listing of all installation kits and the content:
KA51B INSTALLATION KIT
050--01928--0000
050--01928--0001

SYMBOL CAS PART NBR DESCRIPTION [UOM] -0000 -0001

_ 030-02421-0000 CONNECTOR 9P [EA] 1

_ 030-02423-0000 CONNECTOR 5P [EA] 1 1

_ 047-05759-0002 MTG RING W/H [EA] 1

_ 047-05760-0002 MOUNTING PLATE W/H [EA] 1 1

_ 089-06163-0008 SCR FHP 4-40X1/2 [EA] 2

_ 200-02846-0000 COMPENSATOR ASSY [EA] 1

Revision 0, Dec 1997 Page 1--45


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

KAV 485 INSTALLATION KIT


050--02319--0000
050--02319--0001

SYMBOL CAS PART NBR DESCRIPTION [UOM] -0000 -0001

_ 030-02607-0014 PLG CONN 41P STRGT [EA] 1

_ 030-02656-0014 PLG CONN 41P STRGT [EA] 1

_ 073-05123-0002 MOORING PLT W/HDW [EA] 1 1

_ 089-05115-0012 SCR FHP 6-32X3/4 [EA] 4 4

_ 089-06461-0012 SCR FHP 6-32X3/4 [EA] 4 4

REF 1 155-05615-0000 INSTL DWG KAV485 [RF] 0 0

KCM 100 INSTALLATION KIT


050--03245--0000

SYMBOL CAS PART NBR DESCRIPTION [UOM] -0000

_ 030-01157-0011 SOCKET CRMP 20G [EA] 10

_ 030-02351-0005 HOOD/LVR ASSY SD E [EA] 1

P 1010 030-01171-0000 CONN SUB-D HSG 9S [EA] 1

REF 1 155-06008-0000 KCM100 INSTALL DWG [RF] 0

KCP 520 INSTALLATION KIT


050--03174--0000

SYMBOL CAS PART NBR DESCRIPTION [UOM] -0000

_ 030-01094-0006 CONNECTOR 25/50 P [EA] 2

_ 030-01432-0000 TERMINAL CONN [EA] 100

_ 047-09171-0001 COVER PLT W/F [EA] 1

_ 047-10407-0002 CONNECTOR BRKT [EA] 1

_ 047-10454-0002 COVER RACK [EA] 1

_ 071-00099-0000 MTG RK ASSY KCP520 [EA] 1

_ 089-02140-0000 NUT LOCK 4-40 [EA] 2

_ 089-05903-0008 SCR PHP 4-40X1/2 [EA] 4

_ 089-06008-0006 SCR FHP 4-40X3/8 [EA] 14

_ 089-06012-0006 SCR FHP 6-32X3/8 [EA] 4

_ 089-06493-0006 SCR SHC 6-32X3/8 [EA] 4

_ 090-00959-0000 .6251DX1 PLUG [EA] 2

_ 150-00042-0010 SHRINK TUBING .187 [IN] 35

P 520 030-03039-0001 CONN PLUG DPX3 [EA] 1

REF 1 155-05997-0000 INSTALL DWG KCP520 [RF] 0

Page 1--46 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

KDC 481 INSTALLATION KIT


050--02310--0000 SOLDER
050--02310--0001 SOLDER
050--02310--0002 CRIMP

SYMBOL CAS PART NBR DESCRIPTION [UOM] -0000 -0001 -0002

_ 030-01157-0011 SOCKET CRMP 20G [EA] 15

_ 030-01172-0000 CONN SUB-D HSG 15S [EA] 1

_ 030-01428-0002 EMI HOOD W/LCK 15P [EA] 1

_ 030-02105-0010 CONN PLUG 61P [EA] 1

_ 030-02564-0004 CONN PLUG 24-61CS [EA] 1 1

_ 047-09787-0002 GRND STRP FRT W/HW [EA] 1 1 1

_ 047-09787-0004 GRND STRP BK W/F [EA] 1 1 1

_ 071-04038-0000 3 MTG RACK [EA] 1 1 1

_ 089-02015-0037 NUT FLAT 8-32 [EA] 2 2 2

_ 089-08017-0037 WSHR INTL LK #8 [EA] 2 2 2

REF 1 155-05603-0000 KDC 481 INSTALL [RF] 0 0

REF 1 155-05603-0001 INST DWG-KDC 481T [RF] 0

KMS 540/541 INSTALLATION KIT


050--03173--0000

SYMBOL CAS PART NBR DESCRIPTION [UOM] -0000

_ 073-00044-0001 PLATE MOORING [EA] 1

_ 089-06372-0012 SCR FHP 6-32X3/4 [EA] 4

P 5401 030-02563-0005 CONN PLG 22-55SN [EA] 1

REF 1 155-05991-0000 INSTAL DWG KMS540 [RF] 0

KMT 112 INSTALLATION KIT


050--01361--0000

SYMBOL CAS PART NBR DESCRIPTION [UOM] -0000

_ 030-02190-0000 CONN 5 PIN W/HOOD [EA] 1

_ 089-02157-0015 NUT LOCK 6-32 [EA] 3

_ 089-07009-0010 SCR PHS 6-32 X 5/8 [EA] 3

_ 089-08036-0019 WSHR FLT STD #6 [EA] 6

Revision 0, Dec 1997 Page 1--47


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

KRA 405 INSTALLATION KIT


050--01401--0002

SYMBOL CAS PART NBR DESCRIPTION [UOM] -0002

_ 030-02210-0012 CONN [EA] 1

_ 035-01448-0014 6X10 PLSTC BAG [EA] 1

_ 057-02029-0008 LABEL [EA] 1

_ 057-02029-0009 LABEL [EA] 1

_ 073-00044-0001 PLATE MOORING [EA] 1

_ 073-00045-0000 ADAPTOR PLATE [EA] 1

_ 073-00045-0001 ADAPTOR PLATE [EA] 1

_ 089-05115-0012 SCR FHP 6-32X3/4 [EA] 4

_ 089-06461-0012 SCR FHP 6-32X3/4 [EA] 4

KRA 405 INSTALLATION KIT


050--01391--0000
050--01391--0001

SYMBOL CAS PART NBR DESCRIPTION [UOM] -0000 -0001

_ 030-02211-0000 CONNECTOR [EA] 1

_ 030-02211-0002 CONN [EA] 1

_ 057-02029-0007 LABEL [EA] 1 1

_ 071-04003-0000 MTG RACK 3 [EA] 1 1

KSA 572 INSTALLATION KIT


050--03241--0000

SYMBOL CAS PART NBR DESCRIPTION [UOM] -0000

_ 030-03235-0000 MS 3740W12-10S [EA] 1

_ 030-03236-0000 MS 3112E8-4S [EA] 1

_ 155-06007-0000 INSTALL DWG KS572 [RF] 0

Page 1--48 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

KSG 105 INSTALLATION KIT


050--01410--0000
050--01410--0001
050--01410--0002
050--01410--0050

SYMBOL CAS PART NBR DESCRIPTION [UOM] -0000 -0001 -0002 -0050

_ 030-01080-0000 CONN FM CRMP 20AWG [EA] 37

_ 030-02154-0000 HOOD CONN 24P [EA] 1 1 1 1

_ 030-02221-0000 CONN 37 PIN [EA] 1 1 1

_ 030-02272-0000 CONN 41P SHELL [EA] 1

_ 057-01611-0000 GYRO SHK-MNT TMPLT [EA] 1 1 1

_ 071-04025-0000 VBRTN RACK ASSY [EA] 1

_ 071-04025-0001 VIB MTG RACK ASSY [EA] 1 1

_ 089-05909-0009 SCR PHP 8-32X9/16 [EA] 2 2 2

_ 155-02001-0000 GROUND STRAP [EA] 1 1 1

_ 155-05118-0000 INST DWG KG102 [RF] 0 0

_ 155-05158-0000 INST DWG KSG105 [RF] 0 0

KSM 575 INSTALLATION KIT


050--03218--0000

SYMBOL CAS PART NBR DESCRIPTION [UOM] -0000

_ 030-03227-0000 CONN BH MT 14-19S [EA] 1

REF 1 155-01638-0000 KLA 570 INST DWG [RF] 0

KVG 350 INSTALLATION KIT


050--01873--0000

SYMBOL CAS PART NBR DESCRIPTION [UOM] -0000

_ 030-02402-0001 CONN PLUG 55P OD [EA] 1

KRG 333 INSTALLATION KIT


050--03290--0000

SYMBOL CAS PART NBR DESCRIPTION [UOM] -0000

_ 030-01157-0011 SOCKET CRMP 20G [EA] 20

_ 030-01428-0004 EMI HOOD W/LCK 37P [EA] 1

P 3331 030-01175-0000 CONN SUB-D HSG 37S [EA] 1

REF 1 155-06015-0000 INSTAL DWG KRG333 [RF] 0

REF 5 006-10524-0000 KRG333 INSTAL MAN [RF] 0

Revision 0, Dec 1997 Page 1--49


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

1.8 ACCESSORIES REQUIRED


1.8.1 ASSOCIATED EQUIPMENT

1.9 ACCESSORIES REQUIRED BUT SUPPLIED SEPARATELY


1.9.1 KFC 500 Flight Control System Installation Manual and Flight Manual Supplements.

1.10 GOVERNMENT APPROVAL


In most countries, government approval is required before the components of the
KFC 500 System may be installed in an aircraft.

Page 1--50 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

SECTION II
INSTALLATION

2.1 GENERAL INFORMATION


This section provides general information for installing the KFC 500 Flight Control System. The
approved installation is covered by Type Authorization (TA) granted by Transport Canada
certification authorities to Bell Helicopter. Installation must conform to the approved data.

2.2 UNPACKING AND INSPECTING EQUIPMENT


Exercise extreme care when unpacking each unit. Make a visual inspection of each unit for
evidence of damage incurred during shiipment. If a claim for damage is to be made, save the
shipping container to substantiate the claim. When all equipment is removed, place in the shipping
container all packing materials for use in unit storage or reshipment.

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.

2.3 MOUNTING INSTRUCTIONS AND ILLUSTRATIONS


Listed below are suggestions and factors to consider before installing each component of the KFC
500 System.
2.3.1 KA 51B SLAVING ACCESORY
The KA 51B must be mounted as prescribed in the certification data.
Figure 2--1 provides the outline and mounting dimensions.
2.3.2 KCM 100 CONFIGURATION MODULE
The KCM 100 must be mounted as prescribed in the certification data.
Figure 2--2 provides the outline and mounting dimensions.
2.3.3 KSG 105 SLAVED GYRO
The KSG 105 must be mounted as prescribed in the certification data.
Figure 2--3 provides the outline and mounting dimensions.
2.3.4 KMT 112 FLUX VALUE
The KMT 112 must be mounted as prescribed in the certification data.
Figure 2--4 provides the outline and mounting dimensions.
2.3.5 KRG 333 ACCELERATION/RATE SENSOR
The KRG 333 must be mounted as prescribed in the certification data.
Figure 2--5 provides the outline and mounting dimensions.

Revision 0, Dec 1997 Page 2--1


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

2.3.6 KVG 350 VERTICAL GYRO


The KVG 350 must be mounted as prescribed in the certification data.
Figure 2--6 provides the outline and mounting dimensions.
2.3.7 KRA 405 RADAR ALTIMETER
The KRA 405 must be mounted as prescribed in the certification data.
Figure 2--7 provides the outline and mounting dimensions.
2.3.8 KDC 481T AIR DATA COMPUTER
The KDC 481T is rack mounted to the airframe as prescribed in the certification data.
Figure 2--8 provides the outline and mounting dimensions.
2.3.9 KAV 485 ALTIMETER AND VERTICAL SPEED INDICATOR
The KAV 485 Configuration module must be mounted as prescribed in the certification data.
Figure 2--9 provides the outline and mounting dimensions.
2.3.10 KCP 520 FLIGHT CONTROL COMPUTER
The KCP 520 Configuration module must be mounted as prescribed in the certification data.
Figure 2--10 provides the outline and mounting dimensions.
2.3.11 KMS 540/541 MODE CONTROLLERS
The KMS 540/541 Model Controller must be mounted as prescribed in the certification data.
Figure 2--11 provides the outline and mounting dimensions.
2.3.12 KSA 572 TRIM SERVO
The KSA 572 Configuration module must be mounted as prescribed in the certification data.
Figure 2--12 provides the outline and mounting dimensions.
2.3.13 KSM 575 LINEAR ACTUATOR
The KSM 575 Configuration module must be mounted as prescribed in the certification data.
Figure 2--13, 2--14 and 2--15 provides the outline and mounting dimensions.

Page 2--2 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 2--1 KA 51B OUTLINE AND MOUNTING DRAWING


(Dwg No 155--05371--0000 R4, Sheet 1 of 1)

Revision 0, Dec 1997 Page 2--3


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Page 2--4 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 2--2 KCM 100 OUTLINE AND MOUNTING DRAWING


(Dwg No 155--06008--0000 R1, Sheet 1 of 1)

Revision 0, Dec 1997 Page 2--5


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Page 2--6 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 2--3 KSG 105 OUTLINE AND MOUNTING DRAWING


(Dwg No 155--05158--0000 R3, Sheet 1 of 1)

Revision 0, Dec 1997 Page 2--7


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Page 2--8 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 2--4 KMT 112 OUTLINE AND MOUNTING DRAWING


(Dwg No 155--05130--0100 R1, Sheet 1 of 1)

Revision 0, Dec 1997 Page 2--9


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Page 2--10 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 2--5 KRG 333 OUTLINE AND MOUNTING DRAWING


(Dwg No 155--06015--0000 R1, Sheet 1 of 1)

Revision 0, Dec 1997 Page 2--11


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Page 2--12 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 2--6 KVG 350 OUTLINE AND MOUNTING DRAWING


(Dwg No 155--05362--0000 R0, Sheet 1 of 1)

Revision 0, Dec 1997 Page 2--13


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Page 2--14 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 2--7 KRA 405 OUTLINE AND MOUNTING DRAWING


(Dwg No 155--01153--0000 R9, Sheet 1 of 1)

Revision 0, Dec 1997 Page 2--15


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Page 2--16 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 2--8 KDC 481 OUTLINE AND MOUNTING DRAWING


(Dwg No 155--05603--0000 R7, Sheet 1 of 1)

Revision 0, Dec 1997 Page 2--17


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Page 2--18 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 2--9 KAV 485 OUTLINE AND MOUNTING DRAWING


(Dwg No 155--05615--0000 R2, Sheet 1 of 1)

Revision 0, Dec 1997 Page 2--19


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Page 2--20 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 2--10 KCP 520 OUTLINE AND MOUNTING DRAWING


(Dwg No 155--05997--0000 R2, Sheet 1 of 2)

Revision 0, Dec 1997 Page 2--21


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Page 2--22 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 2--10 KCP 520 OUTLINE AND MOUNTING DRAWING


(Dwg No 155--05997--0000 R2, Sheet 2of 2)

Revision 0, Dec 1997 Page 2--23


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Page 2--24 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 2--11 KMS 540/541 OUTLINE AND MOUNTING DRAWING


(Dwg No 155--05991--0000 R2, Sheet 1 of 1)

Revision 0, Dec 1997 Page 2--25


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Page 2--26 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 2--12 KSA 572 OUTLINE AND MOUNTING DRAWING


(Dwg No 155--06007--0000 R3, Sheet 1 of 1)

Revision 0, Dec 1997 Page 2--27


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Page 2--28 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 2--13 KSM 575 OUTLINE AND MOUNTING DRAWING


(Dwg No 155--01638--0100 R1, Sheet 1 of 1)

Revision 0, Dec 1997 Page 2--29


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Page 2--30 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 2--14 KSM 575 OUTLINE AND MOUNTING DRAWING


(Dwg No 155--01638--0200 R0, Sheet 1 of 1)

Revision 0, Dec 1997 Page 2--31


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Page 2--32 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 2--15 KSM 575 OUTLINE AND MOUNTING DRAWING


(Dwg No 155--01638--0500 R0, Sheet 1 of 1)

Revision 0, Dec 1997 Page 2--33


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Page 2--34 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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.

Revision 0, Dec 1997 Page 3--1


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Page 3--2 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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

Revision 0, Dec 1997 Page 4--1


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Page 4--2 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

SECTION V
THEORY OF OPERATION

5.1 SYSTEM OPERATION


The FCC is the heart of the KFC 500 system. It collects information necessary to perform the flight
control task and performs flight control calculations.
Figure 5--1 shows a block diagram of the KCP 520 FCC. The FCC contains four processors: one
FD processor which calculates flight director commands, two AP processors which control servo
actuators, and a maintenance processor. The FD processor provides take--off guidance, cruise
modes, and category I approach capabilities. The AP processors are redundant processors
providing AP, YD and SCAS control logic, computing servo commands and level one monitoring
providing coupled cruise control and coupled category I approach maneuvers. The maintenance
processor assists in diagnostics and maintenance. These processors communicate with each other
via internal busses.

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

Revision 0, Dec 1997 Page 5--1


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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--2 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

FIGURE 5--1 KCP520 BLOCK DIAGRAM


(Sheet 1 of 1)

Revision 0, Dec 1997 Page 5--3


CS:15546M00.IDU
CO--PILOT
CBT
PIC SWITCH
PILOT
OPEN/GND

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

ROLL TRIM LEFT


ANNUN

ROLL TRIM RIGHT


PITCH TRIM DOWN
PITCH FAIL OPEN/GND
D SCAS FAIL ANNUN
ANNUN PILOT
AP FAIL ANNUN GO AROUND
ROLL FAIL CBT YAW TRIM RGHT
AFCS DISC ANNUN
ANNUN SWITCH YAW TRIM LEFT
S MISTRIM ANNUN GO AROUND
YAW FAIL PITCH TRIM UP
PITCH FAIL ANNUN KCP 520 OPEN/GND
ANNUN PITCH TRIM DOWN
ROLL FAIL ANNUN
ROLL TRIM RIGHT
YAW FAIL ANNUN KMS 540
FLIGHT
ROLL TRIM LEFT
CONTROL
MODE
COMPUTER
SELECT
PANEL LAMP TEST
AFCS DISC SWITCHES FCC
AP (MSP)
PILOT CO--PILOT
SCAS FD CLEAR SWITCHES
EMER. BUS #2
+28 VDC AFCS DISC

PC 1 ROLL PITCH PILOT CO--PILOT


HYDRAULIC
DETENT DETENT
PRESSURE
SWITCH SWITCH
SWITCH
CYCLIC FTR
PC 1 CYCLIC FTE EN
CO--PILOT FTR
KFC 500

YAW FTE EN
PILOT FTR
FT -- CB

SELF TEST FORCE TRIM


YAW FTR
CB
AFCS TEST FT--CB
AFCS DISC CO--PILOT PILOT
BENDIX/KING

DISC WARN HORN

WARN +28 VDC


FTE
HORN

PILOT
FLIGHT CONTROL SYSTEM

CO--PILOT YAW
CYCLIC FTR SWITCHES
PIC FTR
SWITCH
YAW DETENT
AFCS
SWITCH

(Dwg No xxx--xxxxx--xxxx R0, Sheet 1 of 1)


DISC
WARN
HORN

PITCH AND ROLL TRIM


CLUTCH ENGAGE

YAW TRIM CLUTCH ENGAGE } TO TRIM SERVO CLUTCHES

FIGURE 5--2 KCP 520 DISCRETE INPUT/OUTPUT BLOCK DIAGRAM

Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

5.1.1 MSP (Mode Select Panel) Modes of Operation


The MSP operates in the following four (4) modes:
A. Power--up
B. Normal
C. Installation
D. Diagnostic
5.1.1.1 MSP Power--up Mode
When the 28 VDC power to the MSP is greater than 15 VDC, the MSP begins its power--up
sequence, testing the CPU and memory. A brief test of all mode lamps is performed at this time.
During the power--up sequence the front panel buttons (except for AP and SCAS) and the external
switches for Go Around and FD Off are checked for being in an active (pressed) state. If the switches
are active at that time, the MSP will record them as being strapped and they will be disabled (this
will occur if the switch is pressed, stuck, or not available). The disabled switches will remain disabled
until the MSP is powered up again, at which time their state is checked again (if they are still active,
they will remain disabled).
5.1.1.2 MSP Normal Mode
The MSP is ready to perform its normal task of mode selection and mode acknowledgment. The
MSP mode indications may be turned on by pressing the lamp test switch mounted in the cockpit.
During normal mode, the MSP transmits mode request information to the FCC FD processor serially
using the ARINC 429 interface.
First, pressed status of the buttons on the MSP front panel is transmitted to the FCC as discretes.
Second, pressed status of the following cockpit mounted switches is transmitted to the FCC: CBT
switch, YBT switch, FTR switches, and the force trim circuit breaker.
Third, stuck switch information is transmitted to the FCC. The MSP monitors most switch inputs to
determine if the switch is stuck in the on position. Since mode engagement requests are normally
performed by pressing a button momentarily, the MSP determines that a switch is stuck in the on
position if a switch has been pressed for more than 5 seconds. This stuck switch monitoring is not
performed for the CBT switch, the YBT switch, or the FTR switches, since these switches can be
held in an on state for greater lengths of time when the pilot is adjusting aircraft references.
The AP and SCAS button inputs from the MSP are sent directly to the AP processor in the FCC.
This allows for engagement and disengagement of the AP and SCAS modes even when the MSP
or the FD processor in the FCC have failed.
All ARINC 429 serial data transmitted by the MSP has a source/destination identifier transmitted
as part of the data packet (bits 9 and 10 of the ARINC 429 word, with bit 10 being most significant).
The MSP in the Bell 430 is hard--wired in the harness to have an SDI code of 10, set by leaving ZI
on the MSP rear connector open and connecting ZH on the MSP rear connector to ground. The SDI
code can be verified from the ARINC 429 Input/Output Screen for the FD processor of the FCC by
monitoring the ARINC 429 information received from the MSP by the FCC (see sections 6.1.5.2.4,
6.4.6, and 7.9 for more information).
The MSP receives mode annunciation information from the FD processor of the FCC serially using
the ARINC 429 interface during normal mode. Mode annunciation information received is used by
the MSP to annunciate appropriate mode lights on the MSP front panel.

Revision 0, Dec 1997 Page 5--5


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

5.1.1.3 MSP Installation Mode


To enter the MSP installation mode, power off the MSP by pulling its circuit breaker. Then, reapply
power to the MSP while pressing the AP and SCAS buttons until all indications turn off.

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.

Page 5--6 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

5.1.2 FCC FD PROCESSOR MODES OF OPERATION

The FD processor operates in the following three (3) modes:


A. Power--up
B. Normal
C. Diagnostic
5.1.2.1 FD Power--up Mode
The FD processor tests its CPU and memory. At the end of power--up tests, it requests the
configuration data from the maintenance processor. If valid, it is stored in FD--local non--volatile
memory and used for computations. If invalid, the data stored in the FD processors non--volatile
memory from previous operations is used if valid.

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.

5.1.2.2 FD Normal Mode


The FD processor is ready to perform its normal tasks of performing flight director function. This
operation is described in detail in section 5.2.
5.1.2.3 FD Diagnostic Mode
If requested by the maintenance processor, the FD processor will enter diagnostic mode provided
that:
A. It is in Normal mode (power--up mode completed) and no mode is engaged
B. AP disconnect circuit breaker is pulled.
C. Cyclic FTR switch is pressed or the bench strap for the FD processor is active (see
section 6.3.1)

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.

Revision 0, Dec 1997 Page 5--7


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

5.1.3 FCC AP PROCESSOR MODES OF OPERATION


The two AP processors operate in the following four (4) modes in synchronization (both processors
will be in the same mode at the same time):
A. Power--up
B. Pre--flight Test
C. Normal
D. Diagnostic
5.1.3.1 AP Power--up Mode
Each AP processor tests its CPU and memory. During this test, all failure annunciations to the IIDS
are commanded on. At the end of power--up tests, it requests the configuration data from the
maintenance processor. If valid, it is stored in AP--local non--volatile memory and used for
computations. If the data in the configuration module is invalid, the AP--local data from previous
operation is used if it is valid. Also, the checksum computed from the configuration information is
compared between the two AP processors. If the computed checksums do not match, engagement
of AP mode and SCAS mode will be prevented and an error will be logged in the FCC error log.
NOTE
If both sources of configuration data are invalid (internal to the AP
processor and from the configuration module), configuration
information is undefined. This situation will result in prevention of
AP mode and SCAS mode engagement. Also, an error will be
logged in the FCC error log when the configuration information is
undefined.

5.1.3.2 AP Pre--flight Test Mode


Pre--flight test mode is entered automatically after the power--up sequence. During the test all IIDS
indications are commanded off except for AP FAIL and SCAS FAIL. Pre--flight test may also be
entered by pressing the TEST button located on the pedestal near the upper right hand corner of
the MSP (this button is labeled AFCS GROUND TEST) if neither the AP or SCAS mode is engaged.
Preflight test consists of the following kinds of tests:
The strap code in the harness is verified.
The ability for each AP processor to independently disable all servos using the AP fail
discrete output is verified.
The ability of the high--side and low--side drivers to individually interrupt drive to the brake
solenoid of each linear actuator and each trim servo is verified.
The ability to command and control each servo amplifier is verified individually.
The midpoint voltage for each servo amplifier is verified for each of the three midpoint
voltage states (see section 7.2.1).
The servo command wrap around is continuously monitored for each servo to verify that
the digital to analog converter is producing the correct voltage for servo commands
generated.

Page 5--8 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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.

5.1.3.3 AP Normal Mode

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.

Revision 0, Dec 1997 Page 5--9


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

5.1.3.4 AP Diagnostic Mode

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.

5.1.4 FCC MAINTENANCE PROCESSOR OPERATION

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

Page 5--10 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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.

5.1.6 FORCE TRIM SYSTEM

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

Revision 0, Dec 1997 Page 5--11


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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.

5.1.7 INTERFACE TO SERVOS AND CONTROL POSITIONS

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.

Page 5--12 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

5.2 FLIGHT DIRECTOR OPERATION


A flight director mode is selected by pressing the desired mode button on the MSP (i.e., press the
FD button for default horizontal and vertical modes) -- see section 1.6.2.3 MSP Buttons, for mode
buttons available on the MSP. Two vertical modes may also be selected by pressing the VS and
ALT SEL buttons on the KAV 485, or by dialing a new value for the Selected Altitude on the KAV
485 -- see section 1.6.7.3 KAV 485 Buttons and Knobs, for mode buttons available on the KAV 485).

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.

Revision 0, Dec 1997 Page 5--13


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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).

Page 5--14 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

5.2.1 HORIZONTAL FD MODES

5.2.1.1 Roll Attitude Hold 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.

5.2.1.2 Heading Select Mode

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).

5.2.1.3 Navigation Mode

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).

5.2.1.4 APPROACH MODE

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.

Revision 0, Dec 1997 Page 5--15


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

5.2.2 VERTICAL FD MODES

5.2.2.1 Pitch Attitude Hold Mode

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.

5.2.2.2 Altitude Hold Mode

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.

5.2.2.3 Vertical Speed Hold Mode

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.

5.2.2.4 Indicated Airspeed Hold Mode

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.

Page 5--16 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

5.2.2.5 Airspeed Limit Mode

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).

5.2.2.6 Glideslope Mode

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.

5.2.2.7 Go Around 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.

Revision 0, Dec 1997 Page 5--17


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

5.2.3 FD MODES REFERENCE ADJUSTMENTS

5.2.3.1 Reference Adjustment Using Cyclic Beep Trim

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).

5.2.3.2 Reference Adjustment Using Force Trim Release

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

5.2.3.3 Detent Switches Effect on FD Mode Reference

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.

Page 5--18 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

5.2.4 FD MODE ENGAGEMENT/DISENGAGEMENT REQUIREMENTS

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.

Revision 0, Dec 1997 Page 5--19


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Flight Director Horizontal


Modes
Sensor Input RAH HDG APR APR NAV NAV NAV
VOR LOC VOR LOC FMS
Roll Attitude R R R R R R R
EFIS label 325
Heading Command R
EFIS label 101
Heading D R R R R R R
EFIS label 320 (mag-
netic),
or label 314 (true)
HSI Valid R R R R R R
EFIS label 277 bit 26
Course Command R R R R
EFIS label 100
Lateral Deviation R R R R R
EFIS label 173
Radar Altitude D
from EFIS
DME Distance D D
EFIS label 202
Roll Steering R
True Air Speed D D D D D D
Air Data label 210
Roll Steering label 121 is used if present, otherwise Lateral Deviation is used.
VOR Lateral Deviation gain--scheduled by DME
If True Air Speed is invalid, will be approximated using Indicated Air Speed and Pressure
Altitude if available.
Only one of the heading labels is transmitted as indicated EFIS label 300 bit 29, 1=Mag,
0= True
Legend:
R -- required input to engage mode or maintain mode engagement
D -- desired input, but mode engagement with degraded performance allowed if not present

TABLE 5--1 FLIGHT DIRECTOR HORIZONTAL MODES

Page 5--20 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Flight Director Vertical Modes


Sensor Input PAH ALT VS IAS Airspeed GA GS
Limit
Pitch Attitude R R R R R R R
EFIS label 324
ILS Vertical Deviation R
EFIS label 174
Vertical Acceleration R R R R
from AP processors
Selected Vertical Speed R
Air Data label 104
Indicated Air Speed D D R R D D
Air Data label 206
True Air Speed D
Air Data label 210
Radar Altitude D
from EFIS
VMO R
Air Data label 207
Collective position D
from AP processors
Pressure Altitude R R R
Air Data label 203
Baro Altitude R
Air Data label 204
Selected Altitude R
Air Data label 102

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

TABLE 5--2 FLIGHT DIRECTOR VERTICAL MODES INPUTS

Revision 0, Dec 1997 Page 5--21


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

5.3 AP AND SCAS OPERATION


Coupled flight modes are selected by pressing the desired mode button on the MSP (i.e., press the
AP button for AP mode and the SCAS button for SCAS mode) -- see section 4.1.2.1 MSP Buttons,
for mode buttons available on the MSP.

5.3.1 SCAS MODE

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.

B. AP button on the MSP is pressed when AP mode is engaged.


C. AP mode is engaged and a failure causing AP mode to disengage occurs, but SCAS
engagement is not inhibited by the failure.
D. AP mode is engaged and certain force trim system operations are performed
(reengagement of AP will be automatic when the force trim system operation is
completed). For more details, see section 5.3.3.
In SCAS mode, the AP processors control the pitch, roll, and yaw primary (linear) servos to dampen
aircraft rates in the pitch, roll, and yaw axes when engaged. The control position synchro inputs are
used, when valid, to detect pilot input into the aircraft control system, allowing the aircraft orientation
to change with reduced damping authority. This is accomplished by monitoring the rate inputs from
the KRG 333 and commanding the primary servos to stabilize aircraft motion by maintaining desired
attitude command rates. Desired attitude command rates are attained by monitoring changes in
control positions with the control position synchro resolvers. This helps to stabilize aircraft response
to pilot control motion. Engagement of SCAS mode will be inhibited if information received from the
KRG 333 is invalid.

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.

Page 5--22 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

SCAS mode will be disengaged/inhibited in all axes by the following conditions:


A. AP button on the MSP is pressed and AP mode engagement is not inhibited.
B. SCAS button on the MSP is pressed (disengages all coupled control modes).
C. The AFCS DISC switch on the cyclic control for either pilot is pressed.
D. A failure occurs that inhibits SCAS mode engagement in all axes. In this instance, the
SCAS FAIL annunciation on the IIDS will be turned on. These failures include loss of
validity from the KRG 333, internal failures in the FCC, and a failures affecting all three
primary servo axes.
SCAS mode will be disengaged/inhibited in an individual axis by the following conditions:
A. Hydraulic pressure (Primary Hydraulics) is not valid -- affects yaw axis only.
B. Primary servo actuator failure detected -- affects axis that has failed primary servo.

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

Revision 0, Dec 1997 Page 5--23


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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.

Page 5--24 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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)

5.3.4 AUTOTRIM IN AP MODE

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.

5.3.5 ANNUNCIATION OF AP MODE AND SCAS MODE ENGAGEMENT

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.

Revision 0, Dec 1997 Page 5--25


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

5.3.6 ANNUNCIATION OF AP MODE AND SCAS MODE FAILURES

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.

5.3.7 CLEARING AP AND SCAS MODE FAILURES

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.

Page 5--26 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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

6.1 NAVIGATING THE REMOTE TERMINAL INTERFACE SCREENS


This discussion assumes that a properly configured terminal is connected to the RTI. If there are
problems getting any screen to appear on the terminal, refer to section 6.2 Problems Accessing the
Remote Terminal Interface Screens.

NOTE
The example screens shown throughout this discussion may
include sample data which will not necessarily be seen by the
user.

6.1.1 NORMAL MODE MAIN MENU SCREEN

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

Requesting AP A, AP B, FD A, FD B, MAI processors to enter Normal mode

FIGURE 6--1 Power--up Message Screen

KCP 520 Flight Computer


-----------------------

D - Enter Diagnostic mode


L - Logged data
T - TTR data
H - History log

Press key for desired option :

FIGURE 6--2 Normal Mode Main Menu Screen

Revision 0, Dec 1997 Page 6--1


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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.

6.1.2 TIME AND TEMPERATURE INFORMATION SCREEN


Pressing T when the Normal Mode Main Menu screen is displayed will cause the Time and
Temperature Information screen, similar to Figure 6--3, to be displayed. The Present Temperature
value is continually updated from a sensor internal to the FCC. A temperature history is also
displayed on this screen. This information is for factory use and should not be changed. To return
to the Normal Mode Main Menu screen from this screen, press the ENTER key once.
Time and Temperature recorder
All temperatures in degrees C, all times in hours

Part number : 123-45678-9012 Serial number : 1000

Sensor : 0 Present temperature : 27


Elapsed time : 1334.6 Error counter : 0
Minimum temperature : -55 Maximum temperature : 85

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

C: clear TTR data; F: dump for file capture


P: initialize part number; S: initialize serial number; <CR>: exit

FIGURE 6--3 Time and Temperature Information Screen

6.1.3 HISTORY LOG SCREEN


Pressing H when the Normal Mode Main Menu screen is displayed will cause the History Log
screen, similar to Figure 6--4, to be displayed. Each major column group is divided into 3 columns
(headed by #, pwr cyc, and temp). The # column is a sequence number. The pwr cyc column
is the power cycle number when the temperature was recorded. The temp column is the
temperature in degrees centigrade that was sensed at the time the history reading was recorded.
The first temperature reading for a given power cycle is obtained from the AP processor
approximately 10 seconds after power--up. After that time, another temperature reading is taken

Page 6--2 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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
-------------------

number of history entries: 60

# 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

F: Dump for file capture; C: clear history log; <CR>: Exit


System mode: Normal

FIGURE 6--4 History Log Screen

6.1.4 LOGGED DATA SCREENS

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
-----------

D - Display logged data


F - Dump logged data for file capture
C - Clear logged data
R - Clear logged data & reset power cycle

Press key for desired option (<CR> to exit) :

FIGURE 6--5 Logged Data Main Menu Screen

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

Revision 0, Dec 1997 Page 6--3


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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

# Power cycle Delta Time Proc Error Description


--- ----------- ---------- ---- ----- ------------------------------
1 1155 00:04:44 AP A 1192 VG # 1 reference volt mon
2 1155 00:04:44 AP B 1192 VG # 1 reference volt mon
3 1155 00:04:44 AP A 1261 SEC PTCH rate range err
4 1155 00:04:44 AP B 1261 SEC PTCH rate range err
5 1156 00:00:02 AP A 1184 Pit position synchro exc mon
6 1156 00:00:02 AP B 1184 Pit position synchro exc mon
7 1156 00:00:02 AP A 1185 Rol position synchro exc mon
8 1156 00:00:02 AP B 1185 Rol position synchro exc mon
9 1156 00:00:02 AP A 1186 Yaw position synchro exc mon
10 1156 00:00:02 AP B 1186 Yaw position synchro exc mon
11 1156 00:00:02 AP A 1187 Col position synchro exc mon
12 1156 00:00:02 AP B 1187 Col position synchro exc mon
13 1156 00:00:02 AP A 1261 SEC PTCH rate range err
14 1156 00:00:02 AP B 1261 SEC PTCH rate range err
15 1156 00:04:03 FD A 884 ALT Mode Disallowed
16 1156 00:04:05 FD A 895 VMO limit Sensor Invalid
17 1156 00:04:07 FD A 886 VS Mode Disallowed

up/down arrow: prev/next item; left/right arrow: prev/next page; <CR> to exit
System mode: Normal

FIGURE 6--6 Error Log Dump Screen

Page 6--4 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

6.1.5 DIAGNOSTIC MODE SCREENS

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
-----------------------

D - Enter Diagnostic mode


L - Logged data
T - TTR data
H - History log

Press key for desired option :

Please confirm your request to enter diagnostic mode


by entering KCP520: kcp520

FIGURE 6--7 Diagnostic Mode Confirmation Screen

Revision 0, Dec 1997 Page 6--5


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

The following processor did not respond:

FD B

The system will be allowed to enter diagnostic mode.

Press any key to continue

FIGURE 6--8 Normal Diagnostic Mode Entry Screen


System mode: Diagnostic
Selected processors: AP A, AP B, FD A, MAI

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

Press key for desired option (<CR> to exit) :

FIGURE 6--9 Diagnostic Mode Main Menu Screen

6.1.5.1 Automated Diagnostic Test Screens

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.

Page 6--6 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

System mode: Diagnostic


Selected processors: AP A, AP B, FD A, MAI

Automated Diagnostic tests


--------------------------

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

Press key for desired option (<CR> to exit) :

FIGURE 6--10 Automated Test Selection Screen


System mode: Diagnostic
Selected processors: AP A, AP B, FD A, MAI

Diagnostic test AP A AP B FD A MAI


-------------------- ----------- ----------- ----------- -----------
ROM PASS PASS PASS PASS
RAM PASS PASS PASS PASS
Non-volatile memory PASS PASS PASS PASS
Timers PASS PASS PASS PASS
DMA PASS PASS PASS N/A
CPU PASS PASS PASS PASS
Serial I/O (IP bus) PASS PASS PASS PASS
Internal ARINC 429 PASS PASS PASS N/A
Power supply PASS PASS PASS PASS
Configuration module N/A N/A N/A ignored

Press any key to continue

FIGURE 6--11 Automated Test Results Screen

Revision 0, Dec 1997 Page 6--7


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

6.1.5.2 Manual Diagnostic Test Screens

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

Manual Diagnostic tests


-----------------------

D - Discrete I/O
4 - ARINC 429 I/O
A - Analog I/O

Press key for desired option (<CR> to exit) :

FIGURE 6--12 Manual Test Selection Screen

6.1.5.2.1 Processor Selection Screens


Pressing D or 4 when the Manual Test Selection screen is displayed will cause a Processor
Selection screen with no processors selected, shown in Figure 6--13, to be displayed. Pressing a
key corresponding to the processor(s) desired to perform the requested manual test on the
Processor Selection screen will cause the desired processor(s) to be selected (Figure 6--14 shows
the Processor Selection screen after A has been pressed to select all AP processors). Once all
of desired processors have been selected, pressing the ENTER key on the Processor Selection
screen will cause the screen for the desired manual test to appear (see sections 6.1.5.2.2 and
6.1.5.2.4 for details about each manual test screen).
System mode: Diagnostic
Selected processor: None

Select processor
----------------

A - Autopilots
1 - Autopilot A
2 - Autopilot B
F - Flight directors
M - Maintenance

Press key to select processor, <CR> to continue :

FIGURE 6--13 Processor Selection Screen (no processors selected)

Page 6--8 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

System mode: Diagnostic


Selected processors: AP A, AP B

Select processor
----------------

A - Autopilots
1 - Autopilot A
2 - Autopilot B
F - Flight directors
M - Maintenance

Press key to select processor, <CR> to continue :

FIGURE 6--14 Processor Selection Screen (AP processors selected)

6.1.5.2.2 Discrete Input/Output Screen


After pressing D when the Manual Test Selection screen is displayed and selecting the
processor(s) to test the discrete inputs and outputs, a Discrete Input/Output screen will be displayed
for the desired processor(s). Figure 6--15 shows a sample AP processor discrete input/output
screen, which is explained in the following two paragraphs. Figure 6--16 shows a sample FD
processor discrete input/output screen, which is navigated similarly to the AP processor screen, as
described in the following two paragraphs. This screen shows the current values being output to
the discrete output ports for the selected processor(s), which can be changed by the user. It also
displays the current states for all the discrete inputs to the selected processor(s), with a zero
indicating a cleared state and a one indicating a set state. Pressing A switches to the Analog
Input/Output screen for the desired processor directly (see section 6.1.5.2.3 for details on this
screen). Pressing ENTER returns the user to the Manual Test Selection screen.
The left side of the discrete input/output screen displays information about the discrete outputs.
There is one line for each discrete output port. Each line indicates the port identifier (number or
letter) followed by the current value (in hexadecimal) being output to that port. Pressing S moves
the > symbol to indicate which output port is selected for modification. Pressing C or W causes
a predefined output sequence to be output to the selected port. Each time one of these keys is
pressed, the next value in the sequence is output to the port. The C key cycles the output value
through the values of 0000, 5555, AAAA, and FFFF (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), then
performs a walking zero bit through the output value (all bits 1, then a 0 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). Pressing V allows the user to enter a hexadecimal value to be output to the selected
output port (can be up to 4 hexadecimal digits long), which will be output once the ENTER key is
pressed.
The right side of the discrete input/output screen displays information about the discrete inputs.
There is one line for each input port for all processors selected. Each line indicates the processor
(AP A or AP B for AP processors) and input port being monitored, followed by the input value read
in hexadecimal and then in binary. In the binary display of port input information, the most significant
bit (bit 15) is displayed on the far left and the least significant bit (bit 0) is displayed on the far right.
For port A, which only has four input bits, the binary value is displayed in the far right to indicate the
four bits of input on that port.

Revision 0, Dec 1997 Page 6--9


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

System mode: Diagnostic


Selected processors: AP A, AP B
>: selected output; a, b: no response; *: stale data

Discrete outputs Discrete inputs


---------------- -----------------------------------
>Port 0: 0000H AP A Port 0: C801H 1100100000000001
Port 1: 0000H AP B Port 0: C801H 1100100000000001
Port 2: 0000H AP A Port 1: 4022H 0100000000100010
Port 3: 0000H AP B Port 1: 4022H 0100000000100010
Port A: 1H AP A Port 2: 0088H 0000000010001000
AP B Port 2: 0088H 0000000010001000
AP A Port 3: 0010H 0000000000010000
AP B Port 3: 0010H 0000000000010000
AP A Port A: 6H 0110
Discrete output commands: AP B Port A: 5H 0101
S : Select output
C : Cycle output patterns (0000, 5555, AAAA, FFFF)
W : Walking ones and zeros output patterns
V : Enter user-defined output value in hex
A : Goto analog I/O screen
<CR> : Exit
NOTE : Port A output bits 1 and 3 are used by the autopilot software;
they cannot be controlled by the user.

FIGURE 6--15 AP Processor Discrete Input/Output Screen


System mode: Diagnostic
Selected processor: FD A
>: selected output; a, b: no response; *: stale data

Discrete outputs Discrete inputs


---------------- -----------------------------------
>Port A: 0H FD A Port 0: 105EH 0001000001011110
FD A Port A: 5H 0101

Discrete output commands:


S : Select output
C : Cycle output patterns (0000, 5555, AAAA, FFFF)
W : Walking ones and zeros output patterns
V : Enter user-defined output value in hex
<CR> : Exit

FIGURE 6--16 FD Processor Discrete Input/Output Screen

6.1.5.2.3 Analog Input/Output Screen


Pressing A when the Manual Test Selection screen is displayed will cause the AP Processor
Analog Input/Output screen, similar to Figure 6--17, to be displayed. This screen shows the current
values being output to the AP processor analog outputs, which can be changed by the user. It also
displays the current values for the selected AP processor analog inputs, which can be changed by
the user. Pressing ENTER when this screen is displayed returns the user to the Manual Test
Selection screen.
The left side of the analog input/output screen displays information about the analog outputs. This
section is divided into two main columns, each holding eight output values, with each main column
divided into two sub--columns. The first sub--column in each column is the analog output number
(0 to 15). The second sub--column is the current output value for that output, in the range of --1 to
+ 1. Pressing the arrow keys when this screen is displayed moves the > symbol to indicate which
output is selected for modification. Pressing V allows the user to enter a new value for the selected

Page 6--10 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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

Analog outputs AP A Mux 0 Analog inputs


--------------------------------------- ---------------------------------
> 0: 0.000 8: 0.000 0: 801H 0.020 volts
1: 0.000 9: 0.000 1: 800H 0.000 amps
2: 0.000 10: 0.000 2: 8B2H 1.259 in/sec
3: 0.000 11: 0.000 3: 8B3H -0.532 degrees
4: 0.000 12: 0.000 4: 800H 0.000 volts
5: 0.000 13: 0.000 5: 801H 0.020 volts
6: 0.000 14: 0.000 6: 7FEH -1.502e-03 amps
7: 0.000 15: 0.000 7: 8B2H 1.259 in/sec

Analog I/O commands:


Up/Down/Left/Right Arrows :Select output
0 - 5 :Select input mux / mux half
P :Select next input processor
V :Enter output value (-1.0 to 1.0)
T :Toggle between converted data and volts
D :Goto discrete I/O screen
<CR> :Exit
System mode: Diagnostic
Selected processors: AP A, AP B, FD A, MAI

FIGURE 6--17 AP Processor Analog Input/Output Screen

6.1.5.2.4 ARINC 429 Input/Output Screen


After pressing 4 when the Manual Test Selection screen is displayed and selecting the
processor(s) to test the ARINC 429 inputs and outputs, an ARINC 429 Input/Output screen will be
displayed for the desired processor(s). Figure 6--18 shows a sample FD processor ARINC 429
input/output screen, which is explained in the following two paragraphs. Figure 6--19 shows a

Revision 0, Dec 1997 Page 6--11


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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.

Page 6--12 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

System mode: Diagnostic


Selected processor: FD A
>: selected output/input; a, b: no response: *: stale data; m: label match

ARINC 429 outputs FD A ARINC 429 inputs


-------------------- -----------------------
>ASIC 0: 600AA87DH ASIC 0 ch 0: *--------H
ASIC 1: 00000000H ASIC 0 ch 1: *--------H
ASIC 0 ch 2: *--------H
Internal wrap & baud ASIC 0 ch 3: *--------H
-------------------- ASIC 1 ch 0:m 6000021DH
ASIC 0: Disabled, LO ASIC 1 ch 1:m F088B003H
ASIC 1: Disabled, LO ASIC 1 ch 2:m 60000002H
>ASIC 1 ch 3:m 60DC0011H
ARINC 429 commands:
S/I : Select output/input
C : Cycle output patterns (0000, 5555, AAAA, FFFF)
W : Walking ones and zeros output patterns
V : Enter user-defined output value in hex
E : Enable/disable internal wrap-around
B : Toggle HI/LO baud
M : Toggle label match on and off
L : Specify label match in hex (xx) or octal (xxx)
<CR> : Exit

FIGURE 6--18 FD Processor ARINC 429 Input/Output Screen


System mode: Diagnostic
Selected processors: AP A, AP B
>: selected output/input; a, b: no response: *: stale data; m: label match

ARINC 429 outputs AP A ARINC 429 inputs AP B ARINC 429 inputs


-------------------- ----------------------- -----------------------
>ASIC 0: 00000000H ASIC 0 ch 0: *7FFFFFFFH ASIC 0 ch 0: *7FFFFFFFH
ASIC 0 ch 1: *7FFFFFFFH ASIC 0 ch 1: *7FFFFFFFH
ASIC 0 ch 2:m E03E8021H >ASIC 0 ch 2:m 623000E1H
Internal wrap & baud ASIC 0 ch 3: *--------H ASIC 0 ch 3: *--------H
--------------------
ASIC 0: Disabled, LO

ARINC 429 commands:


S/I : Select output/input
C : Cycle output patterns (0000, 5555, AAAA, FFFF)
W : Walking ones and zeros output patterns
V : Enter user-defined output value in hex
E : Enable/disable internal wrap-around
B : Toggle HI/LO baud
M : Toggle label match on and off
L : Specify label match in hex (xx) or octal (xxx)
<CR> : Exit

FIGURE 6--19 AP Processor ARINC 429 Input/Output Screen

Interpretation of the ARINC 429 information


Figure 6--18 shows the result of setting up the ARINC 429 input/output for the FD processor to have
label match on all used inputs enabled and an output value on ASIC 0 of 600AA87D (hexadecimal).
The label match has been set up to receive label 270 from the MSP on ASIC 1 channel 0, label 300
from an EFIS on ASIC 1 channel 1, label 100 from a secondary EFIS on ASIC 1 channel 2, and label
210 from the air data system on ASIC 1 channel 3. The value of 600AA87D output on ASIC 0 was
entered by pressing V, then entering 600AA87D, and pressing the ENTER key. Since the output
from ASIC 0 goes to the MSP, this would transmit label 276 to the MSP. Since none of the inputs
from ASIC 0 are used in the Bell 430 installation, this is indicated by the *------------ value for each
input.

Revision 0, Dec 1997 Page 6--13


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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.

Page 6--14 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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)

TABLE 6--1 ARINC 429 WORD HEXADECIMAL GROUPINGS BY BIT NUMBER

Bit 31 Bit 30 Code


1 1 Normal Operation *
1 0 Functional Test
0 1 No Computed Data
0 0 Failure Warning *
* The following labels have the codes for Normal Operation and Failure
Warning exchanged: MSP 353, 354, 371, and 377, FCC 371 and 377, and Air
Data 234, 235, 235, 237, 273
TABLE 6--2 ARINC 429 SIGN STATUS MATRIX INTERPRETATION

Revision 0, Dec 1997 Page 6--15


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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

6.1.5.3 Installation Procedure Screens


Pressing I when the Diagnostic Mode Main Menu screen is displayed will cause the Installation
Processor Selection screen, shown in Figure 6--20, 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 processor on the Installation Processor Selection Screen will cause
the installation screen for that processor to be displayed.
Installation Setup
------------------

A - Installation setup for autopilot


F - Installation setup for flight director

Press key for desired option (<CR> to exit) :

FIGURE 6--20 Installation Processor Selection Screen

6.1.5.3.1 FD Processor Installation Screens


Pressing F when the Installation Processor Selection screen is displayed will cause the FD
Processor Installation screen , shown in Figure 6--21, to be displayed. Pressing the arrow keys
when this screen is displayed moves the > symbol to indicate which installation parameter is to
be changed. Pressing E will increase the selected parameter and pressing D will decrease the
selected parameter. If the selected parameter is a value that can be toggled, pressing either E or
D will cause the parameter value to be toggled (i.e., JAR AWO option will toggle from selected to
not selected when E or D is pressed). Once all desired installation changes have been made, the
user can press S to save the installation data or press ENTER to exit the FD Processor Installation

Page 6--16 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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

Data value (0 - 5 Tubes) : 2

Installation setup
------------------
>EFIS configuration
JAR AWO

>: selected item


up/down arrow: prev/next item; left/right arrow : prev/next screen
E/D: increase/decrease data one step or begin installation process
S: save installation data; <CR>: exit
System mode: Diagnostic
Selected processor: FD A

FIGURE 6--21 FD Processor Installation Screen

6.1.5.3.2 AP Processor Installation Screens


Pressing A when the Installation Processor Selection screen is displayed will cause the AP
Processor Installation screen, shown in Figure 6--22, to be displayed. Pressing the arrow keys when
this screen is displayed moves the > symbol to indicate which installation parameter is to be
changed. Pressing E will increase the selected parameter and pressing D will decrease the
selected parameter. If the selected parameter is a value that can be toggled, pressing either E or
D will cause the parameter value to be toggled (i.e., JAR AWO option will toggle from selected to
not selected when E or D is pressed). Once all desired installation changes have been made, the
user can press S to save the installation data or press ENTER to exit the AP Processor Installation
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.
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.

Revision 0, Dec 1997 Page 6--17


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

System mode: Diagnostic


Selected processors: AP A, AP B

Data value (1 (min) - 8 (max)) : 8

Installation setup
------------------
>Audio volume
Audio frequency
JAR AWO
3-axis FD/AP
LVDT position
Collective position
Pitch cyclic position
Roll cyclic position
Pedal position

>: selected item


up/down arrow: prev/next item; left/right arrow : prev/next screen
E/D: increase/decrease data one step or begin installation process
S: save installation data; <CR>: exit

FIGURE 6--22 AP Processor Installation Screen

6.1.5.3.3 Installation of LVDT Position


When the user has selected the LVDT position installation parameter in the AP Processor
Installation Screen parameter list, the E and D keys function differently. When either key is
pressed, the FCC will command all three primary servos to move from stop to stop so that the end
points of servo travel can be measured and stored. Once the test is complete, a pass/fail message
is displayed for all three servos, similar to Figure 6--23. Pass/fail criteria is determined by comparing
actual servo travel with expected servo travel.

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.

Page 6--18 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

System mode: Diagnostic


Selected processors: AP A, AP B

pitch stroke length: actual = 0.4166, expected = 0.3349 to 0.4531: PASS


roll stroke length: actual = 0.4195, expected = 0.3349 to 0.4531: PASS
yaw stroke length: actual = 0.4857, expected = 0.4012 to 0.5428: PASS

Installation setup
------------------
Audio volume
Audio frequency
JAR AWO
3-axis FD/AP
>LVDT position
Collective position
Pitch cyclic position
Roll cyclic position
Pedal position

>: selected item


up/down arrow: prev/next item; left/right arrow : prev/next screen
E/D: increase/decrease data one step or begin installation process
S: save installation data; <CR>: exit

FIGURE 6--23 Primary Servo LVDT Installation Pass/Fail Message Screen

6.1.5.3.4 Installation of Control Positions


When the user has selected any of the last four items in the AP Processor Installation Screen
parameter list, the E and D keys function differently. When either key is pressed, the FCC will
prompt the installer to position a control in one direction and press the SPACE bar once positioned,
then position the control in the other direction and press the SPACE bar once positioned. The end
points of control position travel will be measured and stored by the FCC during this process. Once
the test is complete, a pass/fail message is displayed for the control position being tested, similar
to Figure 6--24. Pass/fail criteria is determined by comparing actual control position travel with
expected control position travel.

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.

Revision 0, Dec 1997 Page 6--19


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

System mode: Diagnostic


Selected processors: AP A, AP B

expected range = 51.67 to 77.50


endpoints = -46.59, -102.44; actual range = 55.85: PASS

Installation setup
------------------
Audio volume
Audio frequency
JAR AWO
3-axis FD/AP
LVDT position
>Collective position
Pitch cyclic position
Roll cyclic position
Pedal position

>: selected item


up/down arrow: prev/next item; left/right arrow : prev/next screen
E/D: increase/decrease data one step or begin installation process
S: save installation data; <CR>: exit

FIGURE 6--24 Control Position Installation Pass/Fail Message Screen

6.1.5.4 Diagnostic Information Screens


The FCC stores diagnostic information internally to aid in determining the cause of disconnects due
to detected failures. If this information is requested by AlliedSignal to aid in determining cause of
failure, the steps outlined below can be used to provide the requested information:
A. Press D when the Diagnostic Mode Main Menu screen is displayed will cause the Data
Dump Processor Selection screen, shown in Figure 6--25, to be displayed.
B. Press A to select the AP A processor, as shown in Figure 6--26.
C. Press the ENTER key to obtain the data dump start screen, shown in Figure 6--27.
D. Set up the terminal emulation software to capture displayed data to a file (refer to the
users manual for the terminal emulation software being used for more information) and
then press the SPACE bar. The data will scroll on the screen and then stop, similar to
Figure 6--28.
E. Once the scrolling of data has stopped, perform the steps required to stop the capture
of data and close the data file with the terminal emulation software. Then, press the
SPACE bar and a Press any key to continue message will be displayed on the screen.
Press the SPACE bar again to return to the Diagnostic Mode Main Menu screen.
F. Press D to cause the Data Dump Processor Selection screen, shown in Figure 6--25,
to be displayed.
G. Press B to select the AP B processor, similar to Figure 6--26.

Page 6--20 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

H. Repeat steps (3) through (5) to capture the data for AP B.


Select processor
----------------

A - Autopilot A
B - Autopilot B

Press key to select processor, <CR> to continue :

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

Press key to select processor, <CR> to continue :

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

FIGURE 6--27 Data Dump Start Screen


S1130100047F00003700047F000038004284162971
S11301103E1444F100000000000000000000000054
S1130120000000000000000000000000048B047FB9
S113013000010200047F0001020042841629BD1060
S1130140EDD80000000000000000000000000000E6
S113015000000000000000000000048C047F000187
S11301600200047F00010200428416293E01CA3EB7
S1130170000000000000000000000000000000007B
S11301800000000000000000048B047F0002040053
S1130190047F0002040042805D8DBD14F80100005C
S11301A0000000000000000000000000000000004B
S11301B0000000000000048C047F00020400047F9F
S11301C00002040042800EC33E048D7A0000000049
S11301D0000000000000000000000000000000001B
S10701E00000000017
S9030000FC

FIGURE 6--28 Data Dump Completion Screen

Revision 0, Dec 1997 Page 6--21


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

6.1.5.5 Other Aids in Troubleshooting Failures

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.

6.2 PROBLEMS ACCESSING THE REMOTE TERMINAL INTERFACE SCREENS


If the RTI screen cannot be obtained by pressing the ENTER key, check the terminal connections
and that the terminal is configured for VT100 emulation, 9600 bits per second, 8 bits per word, 1
stop bit, no parity, and flow control set for Xon/Xoff. Verify that the computer connected as the
terminal has the proper Comm Port selected and that it is set up for RS 232 communication. To reset
communications, the Ctrl key and W can be pressed simultaneously. Resetting communication
should cause the terminal screen to be cleared and redrawn.
Power to the maintenance processor can be verified at the FCC diagnostic connector. Refer to the
description of the diagnostic connector in section 7.1.

6.3 PROBLEMS ENTERING DIAGNOSTIC MODE


When attempting to enter diagnostic mode, an error screen similar to Figure 6--29 may be displayed
if set up conditions for diagnostic mode are not met. Figure 6--29 shows all processors inhibited from
entering diagnostic mode. It is possible for some processors to enter diagnostic mode and not
others. But, the maintenance processor will not sequence to any diagnostic mode menu screens
if it detects that any processor has been inhibited from entering diagnostic mode. If diagnostic mode
entry is unsuccessful, the user can verify that all conditions are being met for successful entry into
diagnostic mode in section 6.1.5, Diagnostic Mode Screens, and try again.
The following processors did not enter diagnostic mode:

AP A
AP B
FD A

The following conditions are required to enter diagnostic mode:

all modes off

and

Force trim circuit breaker on


Cyclic force trim release pressed
AFCS disconnect switch circuit breaker pulled (autopilot only)
or
Bench strap active

Press any key to continue

FIGURE 6--29 Diagnostic Mode Entry Failure Screen

Page 6--22 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

6.3.1 DIAGNOSTIC MODE FOR FD PROCESSOR WITH AP PROCESSOR LOCK


OUT

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

6.4 INPUT/OUTPUT SIGNALS ACCESSIBLE USING THE REMOTE TERMINAL


INTERFACE
The following sections describe the input and output signals available for viewing and control via
the remote terminal interface. This information is presented by class (discrete input, discrete output,
analog input, etc.) and then by type of interface.

Revision 0, Dec 1997 Page 6--23


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

6.4.1 AP PROCESSOR DISCRETE INPUTS

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

Page 6--24 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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

6.4.2 AP PROCESSOR DISCRETE OUTPUTS


The AP Processor Discrete Outputs are listed in Table 6--6 and some are part of Figure 5--2. Writing
a 1 to the output port bit activates the output drive. Outputs not designated as Hi in the table are
active ground. Outputs designated as Hi in the table are active 28 VDC. 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 processor val- Pitch Trim Pitch Brake Lo KRG 333 Test ROLL FAIL
id Clutch Hi (re- [9A1P1--C12] [9A1P1--A78] Annunciation
served) [9A1P1--B51]
1 MUX reset* Roll Trim Clutch Roll Brake Lo AUTOTRIM YAW FAIL
Hi (reserved) [9A1P1--C7] FAIL Annunci- Annunciation
ation [9A1P1--B39]
[9A1P1--A72]
2 [spare] Audio Alert Dis- Yaw Brake Lo PITCH FAIL DIO_In/Out4
arm [9A1P1--C53] Annunciation (reserved)
[9A1P1--B52]
3 10Hz sync Collective Collective Roll Trim Power [spare] (re-
Clutch Hi (re- Brake Lo (re- served)
served) served)

Revision 0, Dec 1997 Page 6--25


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

4 [input] Pitch Brake Hi Pitch Trim Pitch Power [spare] (re-


[9A1P1--C54] Clutch Lo (re- served)
served)
5 [input] Roll Brake Hi Roll Trim Clutch Roll Power [spare] (re-
[9A1P1--C6] Lo (reserved) served)
6 [input] Yaw Brake Hi Yaw Trim Yaw Power [spare] (re-
[9A1P1--C52] Clutch Lo (re- served)
served)
7 [input] Collective Collective Yaw Trim Pow- [spare] (re-
Brake Hi (re- Clutch Lo (re- er served)
served) served)
8 not available Aural Alert Pitch Trim Audio Alert Arm not available
Brake Lo
[9A1P1--C42]
9 not available Tone Alert (re- Roll Trim Brake [spare] (re- not available
served) Lo served)
[9A1P1--C27]
10 not available Dicsonnect Yaw Trim Brake [spare] (re- not available
Visual Alert An- Lo served)
nunciation [9A1P1--C23]
11 not available Pitch Trim (reserved) Vol_Adj_0 not available
Brake Hi
[9A1P1--C41]
12 not available Roll Trim Brake AP FAIL An- Vol_Adj_1 not available
Hi nunciation
[9A1P1--C26] [9A1P1--C37]
13 not available Yaw Trim Brake AP Engage An- Vol_Adj_2 not available
Hi nunciation
[9A1P1--C22] [9A1P1--C38]
14 not available Coll Power (re- SAS Engage Freq_Sel_0 not available
served) Annunciation
[9A1P1--C50]
15 not available Pitch Trim Pow- SCAS FAIL An- Freq_Sel_1 not available
er nunciation
[9A1P1--A74]
TABLE 6--6 AP Processor Discrete Outputs

Page 6--26 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

6.4.3 FD PROCESSOR DISCRETE INPUTS/OUTPUTS

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

6.4.4 AP PROCESSOR ANALOG INPUTS

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

Revision 0, Dec 1997 Page 6--27


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

11 Yaw Servo Current 11 VG1 Roll Rate


12 Yaw Position Rate 12 DG Heading Sin
MU Channel Signal Name MUX Channel Signal Name
X
13 Yaw Position 13 DG Heading Cos
14 DAC Test 14 Radar Altitude #2
15 Pitch LVDT Sense 15 +5 VDC Sense
1 0 Yaw Servo Command 4 0 VG2 Pitch Sin
1 Pitch Trim Servo Voltage 1 VG2 Pitch Cos
2 Pitch Trim Servo Current 2 VG2 Roll Cos
3 Pitch Trim Command 3 VG2 Roll Sin
4 Roll Trim Servo Voltage 4 Lateral Acceleration
5 Roll Trim Servo Current 5 Long Acceleration
6 Roll Trim Command 6 Normal Acceleration
7 Yaw Trim Servo Voltage 7 Yaw Rate, body
8 Yaw Trim Servo Current 8 Radar Altitude #1
9 Yaw Trim Command 9 Rotor Torque
10 Collective Servo Voltage 10 Pitch rate, body
11 Collective Servo Current 11 Roll rate, body
12 Collective Servo Command 12 VG1 Reference
13 Roll LVDT Sense 13 VG2 Reference
14 Yaw LVDT Sense 14 Temperature
15 --15 VDC Sense 15 +15 VDC Sense
2 0 +15 VDC Sense 5 0 --15VDC sense
1 +28 VDC AP Sense 1 Control Position Reference
2 Pitch Midpoint Voltage 2 spare
3 Roll Midpoint Voltage 3 spare
4 Yaw Midpoint Voltage 4 spare
5 Pitch Trim Midpoint Voltage 5 spare
6 Roll Trim Midpoint Voltage 6 spare
7 Yaw Trim Midpoint Voltage 7 spare
8 Collective Midpoint Voltage 8 spare
9 +5 VDC Sense 9 spare
10 spare 10 spare
11 spare 11 spare
12 spare 12 spare
13 spare 13 spare
14 spare 14 spare
15 spare 15 spare
Notes: scaled value shows resolver mechanical angle
wraparound from DAC channel 8 internal to FCC
reserved
nominally 0 ft/sec2, varies with aircraft leveling
normally 32.2 ft/sec2
normally 26 VAC
internal temperature of FCC
unscaled voltage is 1/2 actual value
unscaled voltage is 1/4 actual value

TABLE 6--8 AP PROCESSOR ANALOG INPUTS

Page 6--28 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

6.4.5 AP Processor Analog Outputs


The AP Processor Analog Outputs are listed in Table 6--9. These output signals are produced by
both AP processors. The servo command outputs are directly connected to the analog inputs listed
in the table internally in the FCC. This internal command wraparound is for monitoring of the analog
output and input channels.
Port Signal Name Analog Input Wraparound
Channel
(if applicable)

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

6.4.6 ARINC 429 INPUTS/OUTPUTS


Each AP processor has the capability of receiving ARINC 429 information from four different
sources, since the AP processors have one ARINC 429 chip with four receivers. Only one of these
channels is used in the Bell 430 installation. Channel 2 of the AP Processor ARINC 429 ASIC is
used to receive air data information from the air data computer. Each AP processor has the
capability of transmitting ARINC 429 information on one output channel available on the ARINC 429
chip, but the output is not used in the Bell 430 installation.
NOTE
Only the ARINC 429 transmit channel from AP B is actually
available at the unit connector.

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

Revision 0, Dec 1997 Page 6--29


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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.

6.5 SYSTEM CONFIGURATION USING THE REMOTE TERMINAL INTERFACE


The RTI 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. Before installation configuration
can be performed, the following set--up steps should be taken:
A. The EFIS or mechanical instruments for displaying mode engagement and command bar
information should be installed, tested, and configured properly for the autopilot.
B. The harness installation should be checked and verified.
C. FCC should be powered.
D. Force Trim System should be powered.
Once these steps have been completed, the user should be able to use the RTI to enter installation
mode for the AP processor as described in section 6.1.5.3.2 AP Processor Installation Screens. The
AP Processor installation screen should be used to install/update the LVDT position limits for the
primary servos and control position limits and can be used to adjust audio volume and frequency.
Once the installation information has been updated, it should be saved.

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.

Page 6--30 Revision 0, Dec 1997


CS:15546M00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

SECTION VII
MAINTENANCE

7. TROUBLESHOOTING THE KFC 500 IN THE FLIGHT--LINE ENVIRONMENT


The Remote Terminal Interface is an important resource for troubleshooting problems involving the
KFC 500 system. To access information supplied by the Remote Terminal Interface, the RTI may
be connected to the Bell supplied cockpit diagnostic connector or directly to the 37 pin D connector
on the front of the KCP 520 FCC. A description of the problem as viewed from the cockpit together
with the logged errors accessible via the RTI will help to narrow the focus. The time that the problem
occurred should be correlated with the power cycle time in the error log. A more detailed description
of the error codes is contained in APPENDIX A. Some system faults can lead to multiple error codes
being logged. In these instances, usually the first error logged is the most significant. It should also
be kept in mind that only the first occurrence of an error code is logged within a power cycle. Also,
logging of certain error codes can be disabled when the aircraft is determined to be on the ground
(radar altitude less than 15 feet and valid, IAS less than 50 knots and valid) to reduce logging of
errors when performing ground checks on the system and errors generated during the power up
sequence of the FCC.
The following sections describe the required inputs for flight director operation and for flight control
operation. Descriptions are then given for various interfaces to the KFC 500 system as seen through
the RTI in diagnostic mode (see section 6.1.5, Diagnostic Mode Screens, and its sub--sections for
more information on accessing diagnostic mode). These descriptions assume that all equipment
is connected properly, powered, and operating normally. Use of this information, wiring harness
diagrams, and a multimeter should allow diagnosis of most system problems. Throughout this
discussion, a familiarity with the maintenance environment and ability to perform required actions
as appropriate (i.e., connecting a hydraulic mule) is assumed. Nominal values presented here are
for reference only, actual values may be slightly different.

Revision 0, Dec 1997 Page 7--1


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

7.1 THE MAINTENANCE CONNECTOR


External power to the FCC and the operation of power supplies internal to the FCC can be verified
by measuring at the 37--pin D connector under the plate on the front of the FCC. Measurements
are made with respect to pin 23, which is an internal ground reference. A list of pins containing useful
signal information is in Table 7--1. The voltages listed as 28 VDC in the table are derived from the
power to the FCC from the circuit breaker, which is limited to 32 VDC. Absence of voltage at a 28
VDC pin can be due to lack of power to the FCC or a failure of the voltage limiting circuit.
Unit Diagnostic Connector
Pin num- Signal
ber
2 AP Processor 5 VDC
3 AP Processor 15 VDC
4 AP Processor --15 VDC
9 FD Processor 5 VDC
10 FD Processor 12 VDC
11 FD Processor --12 VDC
12 FD Processor 28 VDC
13 Maintenance Processor 5 VDC
14 Maintenance Processor 12 VDC
15 Maintenance Processor --12 VDC
16 Maintenance Processor 28 VDC
23 Ground
30 Audio power 28 VDC
32 FD Bench Strap

TABLE 7--1 UNIT DIANOSTIC CONNECTOR SIGNAL PINS

7.2 SERVO AXIS CONTROL


Most software monitoring is turned off while in diagnostic mode. But, two monitors do remain active.
The first monitor senses servo actuator current, and will turn off the servo amplifier if servo current
is excessive for 60 seconds. This monitor is intended to protect the actuator. The second monitor
compares the midpoint voltage sensed from the H--bridge in the servo amp to an expected value
based on the servo commands. If sensed midpoint voltage and expected midpoint voltage do not
agree for one second, the servo amplifier will be turned off. The midpoint voltage can be affected
by a servo drive line fault to ground, but is also affected by pressing the AP Disconnect switch. If
one of these monitors is tripped, an error code will be stored in the error log if it is the first occurrence
of the error during the power cycle. The monitor shutdown of the servo amplifiers may be removed
by exiting the AP Processor Analog Input/Output screen or AP Processor Discrete Input/Output
screen and then reentering the screen.

Page 7--2 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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).

7.2.1 PRIMARY SERVO AXIS INTERFACES

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

Revision 0, Dec 1997 Page 7--3


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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.

Page 7--4 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Pitch Roll Yaw


Axis Axis Axis
Discrete Input/Output
Servo Amplifier Power Out Port 2, 0010 Out Port 2, 0020 Out Port 2, 0040
Brake Solenoid Lo--Side Out Port 1, 0001 Out Port 1, 0002 Out Port 1, 0004
Brake Solenoid Hi--Side Out Port 0, 0010 Out Port 0, 0020 Out Port 0, 0040
Brake Current Monitor In Port 3, Bit 9 In Port 3, Bit 10 In Port 3, Bit 11
Analog Input/Output
Position Command Out- 11 10 9
put Channel
Command Monitor Mux 0, Ch 4 Mux 0, Ch 9 Mux 1, Ch 0
LVDT Position Mux 0, Ch 3 Mux 0, Ch 8 Mux 0, Ch 13
LVDT Position Rate Mux 0, Ch 2 Mux 0, Ch 7 Mux 0, Ch 12
LVDT Sense Mux 0, Ch 15 Mux 1, Ch 13 Mux 1, Ch 14
Servo Amplifier Voltage Mux 0, Ch 0 Mux 0, Ch 5 Mux 0, Ch 10
Servo Current Mux 0, Ch 1 Mux 0, Ch 6 Mux 0, Ch 11
Midpoint Voltage Mux 2, Ch 2 Mux 2, Ch 3 Mux 2, Ch 4
Servo Position Ranges
LVDT Position Voltage --0.3 V --0.3 V --1.5 V
at Extend Stop (un-
scaled)
LVDT Position Voltage 2.7 V 2.7 V 2.1 V
at Center (unscaled)

TABLE 7--2 PRIMARY SERVO CONTROL INPUT/OUTPUTS FROM THE FCC

Discrete outputs Discrete inputs


---------------- -----------------------------------
Port 0: 0010H AP A Port 0: C801H 1100100000000001
Port 1: 0001H AP B Port 0: C801H 1100100000000001
Port 2: 0010H AP A Port 1: 4022H 0100000000100010
>Port 3: 0000H AP B Port 1: 4022H 0100000000100010
Port A: 1H AP A Port 2: 0088H 0000000010001000
AP B Port 2: 0088H 0000000010001000
AP A Port 3: 0210H 0000001000010000
AP B Port 3: 0210H 0000001000010000
AP A Port A: 6H 0110
Discrete output commands: AP B Port A: 5H 0101

FIGURE 7--1 DISCRETE INFORMATION FOR PITCH SERVO

Analog outputs AP A Mux 0 Analog inputs


--------------------------------------- ---------------------------------
0: 0.000 8: 0.000 0: 609H -9.907 volts
1: 0.000 9: 0.000 1: 91CH 0.427 amps
2: 0.000 10: 0.000 2: 800H 0.000 in/sec
3: 0.000 >11: 0.670 3: CE8H 0.825 degrees
4: 0.000 12: 0.000 4: D5DH 6.704 volts
5: 0.000 13: 0.000 5: 801H 0.020 volts
6: 0.000 14: 0.000 6: 7FEH -1.502e-03 amps
7: 0.000 15: 0.000 7: 8B2H 1.259 in/sec

FIGURE 7--2 ANALOG INFORMATION FOR PITCH SERVO (PROCESSED DATA)

Revision 0, Dec 1997 Page 7--5


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Analog outputs AP A Mux 0 Analog inputs


--------------------------------------- ---------------------------------
0: 0.000 8: 0.000 0: 5F9H -2.539 volts
1: 0.000 9: 0.000 1: 924H 1.426 volts
2: 0.000 10: 0.000 2: 800H 0.000 volts
3: 0.000 >11: 0.670 3: CE5H 6.118 volts
4: 0.000 12: 0.000 4: D5DH 6.704 volts
5: 0.000 13: 0.000 5: 801H 0.005 volts
6: 0.000 14: 0.000 6: 7FFH -0.005 volts
7: 0.000 15: 0.000 7: 8B2H 0.869 volts

FIGURE 7--3 ANALOG INFORMATION FOR PITCH SERVO (RAW DATA)

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).

Page 7--6 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

(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.

7.2.2 TRIM SERVO INTERFACES

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.

TABLE 7--3 Trim Servo Control Input/Outputs from the FCC

Revision 0, Dec 1997 Page 7--7


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

7.3 COCKPIT ANNUNCIATORS

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

TABLE 7--4 AP Processor Discrete Port Values for Cockpit Annunciators

7.4 CONTROL POSITION RESOLVERS

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.

Page 7--8 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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

TABLE 7--5 Control Position Resolver Analog Inputs

7.5 ANALOG INPUT OF RADAR ALTITUDE


The analog radar altitude signal may be monitored at AP processor analog input MUX 4 channel
8. If the 28 VDC radar altitude valid is present (AP processor discrete input port 2 bit 2 should be
0) the scaled value units of feet should be displayed on the analog input/output screen. Otherwise,
the scaled value units will be displayed as invalid. The input circuits in the FCC add an offset to
the radar altitude signal before it is read in by the analog--to--digital converter, making an input
voltage of --9.00 VDC correspond to an altitude of 0 feet.

7.6 KRG 333 INTERFACE


The analog inputs from the KRG 333 are all part of the AP processor analog input MUX 4. Table
7--6 summarizes channel numbers for the inputs received from the KRG 333 and gives an
appropriate value for the input during test mode (KRG 333 in test). Testing for these values during
test mode and for non--test values during normal mode is an easy way to determine that the
signals are being received by the FCC. Test mode can be activated by setting the AP processor
discrete output port 2 bit 0 to 1.
The KRG 333 sends valid discretes to the FCC for Acceleration Valid and Rate Valid (composite
for all acceleration sources and all rate sources). These valids are an active ground signal. The Rate
Valid is input by the AP processors on discrete input port 1 bit 5. The Acceleration Valid is input by
the AP processors on discrete input port 2 bit 7. If a validity signal indicates invalid data, the scaled
analog inputs units will be displayed as invalid on the analog input/output screen. When the KRG
333 is in test mode, the validity signals will be set to indicate the acceleration and rate inputs are
invalid.
Channel # Signal Value in Test Mode
4 Lateral Acceleration < --6 VDC
6 Normal Acceleration > +6 VDC
7 Yaw Rate < --7 VDC
10 Pitch rate, body > +7 VDC
11 Roll rate, body > +7 VDC

TABLE 7--6 KRG 333 Analog Inputs

Revision 0, Dec 1997 Page 7--9


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

7.7 DIRECTIONAL GYRO INTERFACE


The directional gyro information is received in 3--wire synchro format and converted to Sin and Cos
values by the FCC. The Sin value is displayed on AP processor analog input MUX 3 channel 12
and the Cos value is displayed on AP processor analog input MUX 3 channel 13. Directional gyro
validity is a 28 VDC input signal read in on AP processor discrete input port 2 bit 6 (when the bit
is 0 the directional gyro is valid).

7.8 VERTICAL GYRO INTERFACE


Pitch and roll attitude information is received in 3--wire synchro format and converted to a voltage
representing the tangent of the angle of attitude in the FCC. The FCC also filters the attitude
information to produce derived pitch and roll attitude rate. Table 7--7 shows the AP processor analog
inputs used to display this information. When displaying scaled values, the attitude information is
displayed in degrees and the rate information is displayed in degrees/second. When displaying raw
data, the voltage representing the tangent of the attitude angles is displayed and the attitude rates
are converted to a raw voltage value.

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

TABLE 7--7 Vertical Gyro Analog Inputs

Page 7--10 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

7.9 INTERFACE WITH THE MSP


The FD processor receives ARINC 429 information from the MSP on ARINC 429 ASIC 1 channel
0. These labels can be examined in the FD Processor ARINC 429 input/output screen (see section
6.1.5.2.4 ARINC 429 Input/Output Screen) to monitor pressed and released states of various
cockpit switches and MSP switches. The information received from the MSP is summarized in Table
7--8 for easy reference.
BIT Label 270 Label 271 Label 272 Label 350
29 0 0 CPU NVM Fail
28 0 0 Backlighting Power Fail
27 0 CBT Down Sw 5 VDC Ind Pwr Fail
26 AP ENG Sw CBT Up Sw Cockpit Switch Stuck
25 0 0 MSP Powerup Fail
24 FD ENG Sw 0 429 Wraparound Test Fail
23 HDG Sw 0 MSP Invalid MSP Internal Switch Stuck
22 NAV Sw 0 MSP 28VDC Fail
21 APR Sw ALT Sw MSP --12VDC Fail
20 BL Sw 0 MSP +12VDC Fail
19 SCAS Sw VS Sw MSP 5VDC Fail
18 GA Sw IAS Sw FCC Bus Activity Fail
17 0 0 FCC Bus SDI Fail
16 Pilot FTR Sw FD Off Sw FCC Bus SSM Fail
15 0 0 0
14 YBT Left Sw 0 CPU Fail
13 YBT Right Sw Copilot FTR Sw CPU Fail
12 CBT Left Sw 0 CPU Fail
11 CBT Right Sw FT CB En- CPU Fail
gaged
When in diagnostic mode it is normal for Label 350 bit 18 to indicate FCC Bus Activity
Fail since entering diagnostic mode turns off ARINC 429 transmission by the FD
processor. Selecting ASIC 0 and setting the output value to 60000017D should cause
the KMS 540 to set label 350 bit 18 to zero.

TABLE 7--8 ARINC 429 Information Received from the MSP

7.10 COCKPIT SWITCHES INTERFACE


Table 7--9 lists the AP processor discrete inputs corresponding to various cockpit mounted
switches. Table 7--10 lists the FD processor discrete inputs corresponding to various cockpit
mounted switches. Figure 5--2 gives a block diagram of the interface of these switches with the
FCC. The AP processor discrete input/output screen or FD processor discrete input/output screen
(see section 6.1.5.2.2 Discrete Input/Output Screen) can be used to verify that the FCC is receiving
correct information about the state of these switches.

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).

Revision 0, Dec 1997 Page 7--11


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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

Switch Name FD Processor Discrete In- State information


put
Pilot--in--Control Port 0 Bit 11 0 means right (pilot) side EFIS selected
Switch 1 means left (co--pilot) side EFIS
selected

TABLE 7--10 Cockpit Switches Discrete Inputs to FD processor

Page 7--12 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

7.11 AIR DATA INTERFACE

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)

Revision 0, Dec 1997 Page 7--13


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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)

Page 7--14 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

7.12 EFIS INTERFACE


The easiest method for verifying that the FCC is receiving information from the EFIS is to attempt
mode engagement of any mode (except AP and SCAS) using the MSP. If mode engagement is
successful, the FD processor is receiving information from the EFIS. If command bars are displayed
on the EFIS ADI display when a flight director mode is engaged the EFIS is also receiving
information from the FCC. Also, in a properly configured EFIS, a red FD will be displayed whenever
the EFIS is not receiving ARINC 429 information from the FCC. However, this method of verification
does not verify that all labels received from the EFIS are valid (i.e., Heading, which would prevent
engagement of HDG select mode).
NOTE
In systems that have a dual EFIS, only AP and SCAS mode will
be annunciated on the inactive EFIS. The PIC switch determines
which EFIS is active. Only the active EFIS will display engaged
flight director modes and command bar information.
EFIS information is received by the FD processor on ARINC 429 ASIC 1 channel 1 from the left EFIS
and ARINC 429 channel 2 from the right EFIS (if available). Table 7--12 shows the EFIS labels used
by the FD processor 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)


100 Selected Course B, Bit 13 is knob active
101 Selected Heading B, Bit 13 is knob active
121 Horizontal Command B
164 Radar Altitude A
173 Lateral Deviation C
174 Vertical Deviation D
202 DME Distance F
277 EFIS Built--in Test Only bit 25 and bit 26 used by FCC
300 EFIS Mode Status E
314 True Heading B, Sign 0 = 0 to 180 Deg
320 Magnetic Heading B, Sign 0 = 0 to 180 Deg
324 Pitch Attitude B, Sign 0 = Up
325 Roll Attitude B, Sign 0 = Right Bank

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

Revision 0, Dec 1997 Page 7--15


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

BIT Format A Format B Format C Format D Format E Format F


21 32 FT 0.703 Deg 0.00156 DDM 0.00313 DDM SelSide1 2 NM
20 16 FT 0.352 Deg 0.00078 DDM 0.00156 DDM SelSide0 1 NM
19 8 FT 0.176 Deg 0.00039 DDM 0.00078 DDM SelSnsr5 0.5 NM
18 4 FT 0.088 Deg 0.00020 DDM 0.00039 DDM SelSnsr4 0.25 NM
17 0 0.043 Deg 0.00010 DDM 0.00020 DDM SelSnsr3 0.125 NM
16 0 0.022 Deg 0 0 SelSnsr2 0.0625 NM
15 0 0.011 Deg 0 0 SelSnsr1 0.0313 NM
14 0 0.005 Deg 0 0 SelSnsr0 0.0156 NM
13 0 0 0 1= Approach 0.0078 NM
Mode Sensor is
ILS
12 0 0 0 0 1= NAV SRC 0
Keys Active
11 0 0 0 0 0 0
Only one of labels 314 of 320 is transmitted at any time as indicated by label 300 bit 29.
The selected sensor bits are used to determine the selected sensor mode. In the sensor codes
listed below, SelSnsr5 is the most significant bit (leftmost) and SelSnsr0 is the least significant
be (rightmost). Some sensor modes available to the EFIS are not used in the FCC for the Bell
430, but they are listed here since they can be selected:
Sensor Code Selected Sensor
000000 No Mode
000001 Test
000010 VOR
000011 ADF
000100 TACAN
000101 LOC
000110 MLS
000111 Not Used
001000 NAV
001100 RNAV
001101 FMS
010000 GPS
Other codes Not Defined for this certification

TABLE 7--12 ARINC 429 Information Received from the EFIS

Page 7--16 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

7.13 AURAL ANNUNCIATOR INTERFACE


The amplitude (volume) and frequency of the aural disconnect warning tone can be selected on the
AP processor installation screen (see section 6.1.5.3.2 AP Processor Installation Screens). Table
7--13 and Table 7--14 show the relationship of the AP processor discrete outputs to the amplitude
and frequency of the aural disconnect warning tone generated. The aural annunciator interface can
also be monitored and controlled (for testing) in diagnostic mode. Audio power is input as AP
processor discrete input port 0 bit 11, which will be a 0 if audio power is not present. The aural
warning tone can be simulated, when audio power is present, using one of the following two
methods:
(1) Set AP processor discrete output port 0 bit 8 to a 1 (Port 0 value is 100). The tone will
be present until this bit is set to a 0 (Port 0 value is 000).
(2) Set AP processor discrete output port 0 bit 2 to a zero. Then, set AP processor discrete
output port 2 bit 8 to a 1. Set bits 11 through 15 of AP processor discrete output port 0
to produce the desired volume and frequency for the tone. Finally, set output port 2 bit
8 to a 0 to generate the tone. The tone will not be generated when output port 2 bit 8
transitions from 1 to 0 if output port 0 bit 2 is set to 1 instead of 0.

Frequency Output Port 2 Bit 15 Output Port 2 Bit 14


4 KHz 0 0
3 KHz 0 1
2 KHz 1 0
1 KHz 1 1

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

Revision 0, Dec 1997 Page 7--17


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Page 7--18 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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

Revision 0, Dec 1997 Page A--1


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Category Error range Description


Gains 1700 -- 1709 Related to failures detected when translating
gain information from ROM to RAM for AP
processor use
Mistrim 1710 -- 1799 Related to primary servo in an aircraft axis
not being trimmed correctly
Frame synchronization 1800 -- 1899 Related to 10 Hz task frame losing synchro-
nization with the 40 Hz task frame
Error Code Descriptions
The following lists the error code number, text message, unit(s) where the failure may have occurred
and a description for each error logged by the FCC.

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.

Error #(s) Text Message(s) Possible failed unit(s)

0 SSP VBR 0 1. KCP 520


1 PC VBR 1

A processor reset occurred due to an unknown cause.

2 BUS ERROR 1. KCP 520

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.

3 ADDRESS ERROR 1. KCP 520

The processor attempted to fetch an instruction or multi--byte data packet from an odd
(byte) address, instead of from an even (word) address.

4 ILLEGAL INSTRUCTION 1. KCP 520

An illegal or unimplemented instruction code was fetched by the processor.

5 ZERO DIVIDE 1. KCP 520

The processor attempted an integer division by zero. There will probably also be float-
ing point errors logged when this failure occurs.

6 CHK, CHK2 INSTRUCTIONS 1. KCP 520


7 TRAPcc, TRAPV INSTRUCTIONS

Page A--2 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

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.

8 PRIVILEGE VIOLATION 1. KCP 520

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).

9 TRACE 1. KCP 520

The processor encountered a trace (used for debugging purposes) during normal op-
eration.

10 LINE 1010 EMULATION 1. KCP 520


11 LINE 1111 EMULATION

The processor encountered an exception (interrupt) that is reserved for an emulator.

12 HARDWARE BREAKPOINT 1. KCP 520

The hardware in the KCP 520 incorrectly requested a breakpoint in software to occur.

13 COPROCESSOR PROTOCOL VIOLATION 1. KCP 520

The math coprocessor improperly communicated with the processor. Since there is no
math coprocessor, this error should not occur.

14 FORMAT ERROR 1. KCP 520


15 UNINITIALIZED INTERRUPT

The processor found an invalid format code in the stack control operations or an inter-
rupt vector that was not initialized.

16 -- 23 EXCEPTION RESERVED x 1. KPC 520


where x is the error number

Reserved exceptions (interrupts) that are unimplemented in the processor.

24 SPURIOUS INTERRUPT 1. KCP 520

A spurious interrupt occurred in the processor. This can indicate a software problem or
the KCP 520 hardware incorrectly requested an interrupt.

Revision 0, Dec 1997 Page A--3


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

25 AUTO--VECTOR LEVEL 1 1. KCP 520


26 AUTO--VECTOR LEVEL 2
27 AUTO--VECTOR LEVEL 3
28 AUTO--VECTOR LEVEL 4
29 AUTO--VECTOR LEVEL 5
30 AUTO--VECTOR LEVEL 6
31 AUTO--VECTOR LEVEL 7 NMI

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.

32 TRAP 0 1. KCP 520


33 TRAP 1
34 TRAP 2
35 TRAP 3
36 TRAP 4
37 TRAP 5
38 TRAP 6
39 TRAP 7
40 TRAP 8
41 TRAP 9
42 TRAP A
43 TRAP B
44 TRAP C
45 TRAP D
46 TRAP E
47 TRAP F

An unexpected trap instruction occurred to switch from user mode to supervisor mode.

Page A--4 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

48 COPROC UNORDERED CONDITION 1. KCP 520


49 COPROC INEXACT RESULT
50 COPROC DIVIDE BY ZERO
51 COPROC UNDERFLOW
52 COPROC OPERAND ERROR
53 COPROC OVERFLOW
54 COPROC NAN
55 COPROC RESERVED 55
56 COPROC RESERVED 56
57 COPROC RESERVED 57
58 COPROC RESERVED 58

The math coprocessor detected an arithmetic error during operation. Since there is no
math coprocessor, this error should not occur.

59 -- 63 EXCEPTION RESERVED x 1. KCP 520


where x is the error number

Reserved exceptions (interrupts) that are unimplemented in the processor.

64 -- 255 HW INTERRUPT x 1. KCP 520


where x is the error number

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.

300 RAM test failure 1. KCP 520

Powerup routines detected a failure in the RAM memory.

301 ROM test failure 1. KCP 520

Powerup routines detected a failure in the EPROM memory during the CRC check-
sum test of the ROM.

302 CPU32 test failre 1. KCP 520

Powerup routines detected a failure when testing performance of operations in the


processor instruction set.

Revision 0, Dec 1997 Page A--5


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

303 Timer test failure 1. KCP 520

Powerup routines detected a failure when testing the processor interval timer.

304 Task number out of range 1. KCP 520

The task number passed to CK_save_async routine as a parameter exceeds the total
number of synchronous and asynchronous tasks defined.

305 Watchdog test failure 1. KCP 520

Powerup routines detected a failure with the software watchdog. The software watch-
dog failed to interrupt the processor within a given time period.

310 Kernel frame overrun 1. KCP 520

Reserved error number, used as a base for following frame overrun errors.

311 -- Kernel task x frame overrun 1. KCP 520


342
where x is the error number -- 310

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.

360 Watchdog reset 1. KCP 520

The watchdog circuitry caused a reset that was not expected.

361 Double bus fault reset 1. KCP 520

A second bus exception occurred while still processing a previous bus exception (in-
terrupt). This indicates a failure with the interprocessor communication bus.

362 Loss of clock reset 1. KCP 520

Processor system clock has lost its crystal input signal, indicating a possible malfunc-
tion in the crystal oscillator.

363 CPU fail 1. KCP 520

The processor was reset due to a RESET instruction or other undiscriminated cause.

380 No processor ID 1. KCP 520

Page A--6 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

The processor ID discrete input has not been set properly.

381 Software watchdog reset 1. KCP 520

The watchdog circuitry was not reset within the watchdog time--out period, so the
watchdog reset the processor.

390 NVRAM error queue checksum 1. KCP 520

The error logging routines detected a checksum error in the non--volatile RAM.

400 IP powerup fail 1. KCP 520

Powerup routines detected a generic fault in the serial input/output capability of the
processor which affects all interprocessor communications.

401 NCIP powerup test 1. KCP 520


402 CIP powerup test

Powerup routines detected a failure in indicated channel of the serial interprocessor


bus (channel A for CIP, channel B for NCIP).

403 NCIP RX status1 1. KCP 520


404 CIP RX status2

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.

405 NCIP RX count1 1. KCP 520


406 CIP RX count2

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

407 NCIP RX invalid type 1. KCP 520


408 CIP RX invalid type
409 NCIP RX checksum
410 CIP RX checksum

These errors should not be logged when they occur.

Revision 0, Dec 1997 Page A--7


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

411 NCIP RX ARINC queue full1 1. KCP 520


412 CIP RX ARINC queue full2

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,

413 NCIP RX text queue full1 1. KCP 520


414 CIP RX text queue full2

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

415 NCIP RX CTS active 1. KCP 520


416 CIP RX CTS active

These errors should not be logged when they occur.

417 NCIP RX and TX conflict1 1. KCP 520


418 CIP RX and TX conflict2

Data was received on the interprocessor bus while the processor reporting the error
had control of the bus.3

419 NCIP TX bus conflict1 1. KCP 520


420 CIP TX bus conflict2

Another processor tried to take bus control while the reporting processor had bus con-
trol.3

421 NCIP detect break1 1. KCP 520


422 CIP detect break2

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

423 NCIP RX wrong char. type 1. KCP 520


424 CIP RX wrong char. type

These errors should not be logged when they occur.

Page A--8 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

425 IP change of state 1. KCP 520

The interprocessor bus changed state (from inactive to active, etc.) unexpectedly.3

426 CIP TX IP queue full2 1. KCP 520


427 NCIP TX IP queue full1

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).

428 CIP IP send txt queue full2 1. KCP 520


429 NCIP IP send txt queue full1

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).

430 Unknown text lbl rxd on CIP2 1. KCP 520


431 Unknown text lbl rxd on NCIP1

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

432 NCIP bus ISR exceed max. count1 1. KCP 520


433 CIP bus ISR exceed max. count2

During the interrupt service routine for the interprocessor bus, the size of a data pack-
et exceeded the maximum size (count in bytes).3

440 IP bus ISR switch error 1. KCP 520

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.

450 NCIP RX break1 1. KCP 520


451 CIP RX break2

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

Revision 0, Dec 1997 Page A--9


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

452 NCIP RX framing error 1. KCP 520


453 CIP RX framing error
454 NCIP RX overrun error
455 CIP RX overrun error

These errors should not be logged when they occur.

500 RS232 status register 1. KCP 520


2. Unit connected to RS 232 port
(i.e., PC for interface)

This error should not be logged when it occurs.

501 RS232 receive queue full 1. KCP 520

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

502 RS232 unknown interrupt source 1. KCP 520

An interrupt was requested for RS 232 interface, but it was not caused by the trans-
mitter or the receiver.

503 RS232 Receive time out 1. KCP 520

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.

504 RS232 Transmit time out 1. KCP 520

Powerup routines detected that the RS 232 transmitter was unavailable within the al-
lowed time period.

505 RS232 test data mismatch 1. KCP 520

Powerup routines detected a failure in the RS 232 data wraparound test. The proces-
sor did not receive back what was transmitted.

600 DMA 1 queue full 1. KCP 520


601 DMA 2 queue full

Page A--10 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

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,

602 DMA 1 transfer not complete 1. KCP 520


603 DMA 2 transfer not complete

Powerup routines detected that the indicated DMA channel failed to transfer all of its
requested data.5

604 DMA 1 bus source 1. KCP 520


605 DMA 2 bus source

There was a bus error while attempting to read from the indicated DMA source.4,5

606 DMA 1 bus dest 1. KCP 520


607 DMA 2 bus dest

There was a bus error while attempting to write data input from the ARINC 429 ASIC
into the RAM buffer.4,5

608 DMA 1 configuration 1. KCP 520


609 DMA 2 configuration

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

610 DMA 1 transfer 1. KCP 520


611 DMA 2 transfer

The DMA transfer had not completed when the DMA controller interrupted the proces-
sor.4,5

Revision 0, Dec 1997 Page A--11


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

700 ARINC 429 #1 CH 0 label 1. KCP 520


701 ARINC 429 #1 CH 0 data
702 ARINC 429 #1 CH 1 label
703 ARINC 429 #1 CH 1 data
704 ARINC 429 #1 CH 2 label
705 ARINC 429 #1 CH 2 data
706 ARINC 429 #1 CH 3 label
707 ARINC 429 #1 CH 3 data
708 ARINC 429 #2 CH 0 label
709 ARINC 429 #2 CH 0 data
710 ARINC 429 #2 CH 1 label
711 ARINC 429 #2 CH 1 data
712 ARINC 429 #2 CH 2 label
713 ARINC 429 #2 CH 2 data
714 ARINC 429 #2 CH 3 label
715 ARINC 429 #2 CH 3 data

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).

716 ARINC 429 #1 CH 0 receive 1. KCP 520


717 ARINC 429 #1 CH 1 receive
718 ARINC 429 #1 CH 2 receive
719 ARINC 429 #1 CH 3 receive
720 ARINC 429 #2 CH 0 receive
721 ARINC 429 #2 CH 1 receive
722 ARINC 429 #2 CH 2 receive
723 ARINC 429 #2 CH 3 receive

Powerup routines detected no received data on the indicated ARINC 429 chip and
channel.

724 ARINC 429 #1 TX error 1. KCP 520


725 ARINC 429 #2 TX error

Page A--12 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

Powerup routines detected that transmitted data for the indicated ARINC 429 chip was
not received on any channel during loopback testing.

726 ARINC 429 #1 TX timeout 1. KCP 520


727 ARINC 429 #2 TX timeout

Powerup routines detected that the transmitter for the indicated ARINC 429 chip did
not become available in the allotted time.

800 NAVTRK input--LCPLD Default mde 1. KCP 520


801 APRTRK input--LCPLD Default mde
802 NAVTRK input--LCPLD HDGSEL mode
803 APRTRK input--LCPLD HDGSEL mode
804 NAVCAP input--LCPLD NAVCAP mode
805 APRCAP input--LCPLD NAVCAP mode
806 APRTRK input--LCPLD NAVCAP mode
807 NAVTRK input--LCPLD NAVTRK mode
808 APRCAP input--LCPLD NAVTRK mode
809 APRTRK input--LCPLD NAVTRK mode
810 NAVCAP input--LCPLD APRCAP mode
811 NAVTRK input--LCPLD APRCAP mode
812 APRCAP input--LCPLD APRCAP mode
813 NAVCAP input--LCPLD APRTRK mode
814 NAVTRK input--LCPLD APRTRK mode
815 APRTRK input--LCPLD APRTRK mode
816 NAVTRK input--LCPLD GA mode
817 APRTRK input--LCPLD GA mode

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).

818 Illegal Lateral Coupled mode 1. KCP 520

The requested roll (lateral) coupled mode is not allowed in the current configuration.

Revision 0, Dec 1997 Page A--13


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

820 NTA Req input--LARM NOARM mode 1. KCP 520


821 ATA input--LARM NOARM mode
822 ATA Req input--LARM NAVCapArm
823 NTA Req input--LARM NAVTrkArm
824 ATA Req input--LARM NAVTrkArm
825 NTA Req input--LARM AprCapArm
826 NTA Req input--LARM AprTrkArm
827 ATA Req input--LARM AprTrkArm

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).

828 Illegal Lateral Arm mode 1. KCP 520

The requested roll (lateral) arm mode is not allowed in the current configuration.

Page A--14 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

830 VNVC Req input--VCPLD VNAVCap 1. KCP 520


831 VNVT Req input--VCPLD PAH mode
832 VNVT Req input--VCPLD AltC mode
833 VNVT Req input--VCPLD AltH mode
834 VNVT Req input--VCPLD VS mode
835 VNVT Req input--VCPLD IAS mode
836 VNVT Req input--VCPLD VNAVTrk
837 VNVT Req input--VCPLD GSCap mde
838 VNVT Req input--VCPLD GSTrk mde
839 VNVT Req input--VCPLD GA mode
840 GST Req input--VCPLD PAH mode
841 GST Req input--VCPLD AltC mode
842 GST Req input--VCPLD AltH mode
843 GST Req input--VCPLD VS mode
844 GST Req input--VCPLD IAS mode
845 GST Req input--VCPLD VNAV Cap
846 GST Req input--VCPLD VNAV Trk
847 GST Req input--VCPLD GS Trk mde
848 GST Req input--VCPLD GA mode
849 GSC Req input--VCPLD GS Trk mde

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).

850 Illegal Vertical Coupled mode 1. KCP 520

The requested pitch (vertical) mode is not allowed in the current configuration.

851 VNVTA Req input--VARM2 NOARM 1. KCP 520


852 VNVTA Req input--VARM2 GSCapArm 2. KMS 540/541
853 VNVTA Req input--VARM2 GSTrkArm
854 GSTA Req input--VARM2 NOARM mde
855 GSTA Req input--VARM2 VNVCapArm
856 GSTA Req input--VARM2 VNVTrkArm

Revision 0, Dec 1997 Page A--15


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

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).

857 Illegal Vertical Arm #2 mode 1. KCP 520


858 Illegal Vertical Arm #1 mode
859 Illegal Vertical Cpld #2 mode

The requested pitch (vertical) mode is not allowed in the current configuration.

860 EFIS ADI invalid 1. EFIS ADI


2. EFIS symbol generator

The EFIS symbol generator indicated that the EFIS ADI is invalid or unavailable.

861 EFIS HSI invalid 1. EFIS HSI


2. EFIS symbol generator

The EFIS symbol generator indicated that the EFIS HSI is invalid or unavailable.

862 EFIS ATT miscompare 1. EFIS symbol generator


2. One of the attitude sources for the
EFIS

The EFIS symbol generator detected a significant difference between its two attitude
sources.

863 EFIS invalid 1. KCP 520


2. EFIS symbol generator

The EFIS symbol generator valid output is not being received by the flight computer
via the ARINC 429 input.

864 MSP invalid 1. KCP 520


2. KMS 540/541

Mode Select Panel information is not being received by the flight computer via the
ARINC 429 input.

865 MSP LABEL350 PRGMMEM 1. KMS 540/541

Page A--16 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

The mode select panel detected a ROM memory checksum failure during testing of its
EPROM memory.

866 MSP LABEL350 RAMMEM 1. KMS 540/541

The mode select panel has detected a RAM memory failure during testing of its RAM
memory.

867 MSP LABEL350 CPUTMNG 1. KMS 540/541

The mode select panel detected a CPU timing failure during testing of its CPU.

868 MSP LABEL350 CPUINSTR 1. KMS 540/541

The mode select panel detected a CPU instruction execution problem when perform-
ing its internal instruction test.

869 MSP LABEL350 BUSSSM 1. KCP 520


2. KMS 540/541

The mode select panel received ARINC 429 data from the flight computer that had
invalid sign/status matrix (SSM).

870 MSP LABEL350 BUSSDI 1. KCP 520


2. KMS 540/541

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.

871 MSP LABEL350 BUSACT 1. KCP 520


2. KMS 540/541

The mode select panel did not receive ARINC 429 data from the flight computer.

872 MSP LABEL350 POS5V 1. KMS 540/541


873 MSP LABEL350 POS12V
874 MSP LABEL350 NEG12V
875 MSP LABEL350 POS28V

The indicated power supply (+5 VDC, +12 VDC, --12 VDC, or +28 VDC) in the mode
select panel is out of tolerance.

Revision 0, Dec 1997 Page A--17


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

876 MSP LABEL350 STUCKSW 1. KMS 540/541

The mode select panel detected that one of its front panel switches is stuck.

877 MSP LABEL350 PWRUP 1. KMS 540/541

Power up testing in the mode select panel failed.

878 MSP LABEL350 CKPTSW 1. KMS 540/541


2. aircraft switch panel

The mode select panel detected that one of the cockpit mounted switches is stuck.

879 HDG Mode Disallowed 1. KCS 305


2. KCP 520

The sensors associated with the flight computer Heading Select mode are not valid
(i.e., directional gyro inputs).

880 NAV Mode Disallowed 1. KCS 305


881 APR Mode Disallowed 2. EFIS symbol generator
3. KCP 520

The sensors associated with the flight computer NAV or Approach mode are not valid
(i.e., directional gyro inputs or NAV information from EFIS).

882 ALT_SEL Mode Disallowed 1. KAD 480 system components


2. KCP 520

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

883 VNAV Mode Disallowed 1. KCP 520

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.

884 ALT Mode Disallowed 1. KAD 480 system components


2. KCP 520

Page A--18 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

The sensors associated with the flight computer Altitude Hold mode are not valid (i.e.,
altitude input)

885 IAS Mode Disallowed 1. KAD 480 system components


2. KCP 520

The sensors associated with the flight computer Indicated Airspeed Hold mode are not
valid (i.e., pressure altitude input or airspeed input).

886 VS Mode Disallowed 1. KAD 480 system components


2. KCP 520

The sensors associated with the flight computer Vertical Speed Hold mode are not
valid (i.e., altitude input or vertical speed input).

887 GA Mode Disallowed 1. KAD 480


2. KVG 350
3. KCP 520

The sensors associated with the flight computer Go Around mode are not valid (i.e.,
altitude input or pitch attitude input).

888 Attitude Invalid 1. KVG 350


2. KCP 520

The sensors for inputting attitude information for the flight computer are not valid (i.e.,
vertical gyro inputs).

889 FD Disabled Strap 1. KCP 520

The flight director disable discrete input indicates that the flight director should be dis-
abled.

890 PITCH Mode Sensor Invalid 1. KCP 520

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.

891 ROLL Mode Sensor Invalid 1. KCP 520

Revision 0, Dec 1997 Page A--19


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

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.

892 ALT ARM Sensor Invalid 1. KAD 480


2. KCP 520

The sensors associated with the flight computer Altitude Arm or Altitude Capture
mode are not valid (i.e., altitude input).

893 ROLL ARM Sensor Invalid 1. KCS 305


2. KVG 350
3. KCP 520

The sensors associated with the flight computer Roll Arm mode are not valid (i.e., di-
rectional gyro inputs, roll attitude input).

894 VNAV/GS ARM Sensor Invalid 1. EFIS symbol generator


2. KCP 520

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).

895 VMO limit Sensor Invalid 1. KAD 480


2. KCP 520

The sensor associated with maximum operating velocity limiting are not valid (i.e., in-
dicated airspeed input or mach input).

896 FF last 1. KCP 520

This is a dummy error code marking the end of the FF error code section. This error
should not occur.

900 CI parity 1. KCP 520

This error should not be logged when it occurs.

901 CI recv queue overflow 1. KCP 520

Page A--20 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

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

902 CI send queue overflow 1. KCP 520

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).

903 CI unused source 1. KCP 520

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

910 No ASIC XMIT 1. KCP 520

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.

911 Unwanted label 1. KCP 520

An unexpected label was received on one of the ARINC 429 input channels, this label
should have been masked by the ARINC 429 ASIC.

920 CI update timing 1. KCP 520

A label (interprocessor or ARINC 429) was not received within its update period. This
is a generic error that should not occur.

921 Update timing 429_ADC 1. KCP 520


2. KAD 480 system components

The ARINC 429 channel receiving information from the air data computer did not re-
ceive data within its update period.

Revision 0, Dec 1997 Page A--21


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

923 Update timing CIP_ALLPR 1. KCP 520


924 Update timing CIP_APALL
925 Update timing CIP_APOUT
926 Update timing CIP_FDALL
927 Update timing CIP_FDOUT
928 Update timing CIP_MAIOUT

These errors should not occur.

929 Update timing CIP_APIN 1. KCP 520


930 Update timing CIP_FDIN
931 Update timing CIP_MAIIN

The specified channel did not receive data on the interprocessor bus within its update
period.

932 Update timing NCIP_APALL 1. KCP 520


933 Update timing NCIP_APOUT

These errors should not occur.

934 Update timing NCIP_APIN 1. KCP 520

The specified channel did not receive data on the interprocessor bus within its update
period.

935 Update timing A429_XMIT 1. KCP 520

This error should not occur.

936 Update timing A429_ADC 1. KCP 520


2. KAD 480 system components

The ARINC 429 channel receiving information from the air data computer did not re-
ceive data within its update period.

938 Update timing A429_EFIS 1. KCP 520


2. EFIS symbol generator

Page A--22 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

The ARINC 429 channel receiving information from EFIS did not receive data within
its update period.

939 Update timing A429_FMS 1. KCP 520


2. Flight Management System com-
puter

The ARINC 429 channel receiving information from the flight management system did
not receive data within its update period.

940 Update timing A429_MSP 1. KCP 520


2. KMS 540/541

The ARINC 429 channel receiving information from the mode select panel did not re-
ceive data within its update period.

941 Update timing CIP_ALLPR 1. KCP 520


942 Update timing CIP_APALL
943 Update timing CIP_APOUT
944 Update timing CIP_FDALL
945 Update timing CIP_FDOUT
946 Update timing CIP_MAIALL

These errors should not occur.

947 Update timing CIP_APIN 1. KCP 520


948 Update timing CIP_FDIN
949 Update timing CIP_MAIIN

The specified channel did not receive data on the interprocessor bus within its update
period.

950 Update timing NCIP_FDALL 1. KCP 520


951 Update timing NCIP_FDOUT
952 Update timing NCIP_MAIOUT

These errors should not occur.

953 Update timing NCIP_FDIN 1. KCP 520


954 Update timing NCIP_MAIIN

Revision 0, Dec 1997 Page A--23


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

The specified channel did not receive data on the interprocessor bus within its update
period.

955 Update timing A429_XMIT 1. KCP 520


956 Update timing CIP_ALLPR
957 Update timing CIP_APALL
958 Update timing CIP_APOUT
959 Update timing CIP_FDALL
960 Update timing CIP_FDOUT

These errors should not occur.

961 Update timing CIP_APIN 1. KCP 520


962 Update timing CIP_FDIN

The specified channel did not receive data on the interprocessor bus within its update
period.

963 Update timing NCIP_FDALL 1. KCP 520


964 Update timing NCIP_FDOUT

These errors should not occur.

965 Update timing NCIP_FDIN 1. KCP 520

The specified channel did not receive data on the interprocessor bus within its update
period.

1000 ECAL Node error 1. KCP 520

An error occurred while processing one of the ECAL nodes (i.e., a required input to an
ECAL node was undefined).

1001 ECAL Type error 1. KCP 520

An ECAL stack or FIFO call was made with an improper data type (data type must be
boolean or floating point).

1002 ECAL FIFO error 1. KCP 520

Page A--24 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

An error occurred in the processor when trying to access the FIFO buffer used by
ECAL (FIFO corrupted).

1003 ECAL Stack error 1. KCP 520

An error occurred in the processor when trying to access the ECAL stack (stack cor-
rupted).

1004 ECAL Initial Condition error 1. KCP 520

A filter or other function allowing initialization options received an illegal initialization


code.

1005 ECAL Index error 1. KCP 520

An attempt was made to reference a node outside the ECAL data block (i.e., node
pointer not initialized properly).

1006 ECAL Block error 1. KCP 520

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).

1007 ECAL Bad sign input to summer 1. KCP 520

The FE_summer function was called with an illegal input parameter.

1008 ECAL Not enough node inputs 1. KCP 520

An ECAL function was called with too few input parameters (i.e., one when function
requires at least two).

1009 ECAL Filtering out of range 1. KCP 520

An ECAL filter routine generated an arithmetic overflow condition.

1010 ECAL Default error 1. KCP 520

A generic error occurred while processing the ECAL node or block data.

1011 ECAL Bad Node Record error 1. KCP 520

Revision 0, Dec 1997 Page A--25


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

One of the node records in an ECAL node block is not valid (i.e., improper number of
parameters for block type specified).

1012 ECAL Bad Block Pointer error 1. KCP 520

The pointer to a block in the ECAL data block is not valid (i.e., ECAL data pointer is
corrupt).

1013 ECAL Mode Index out of range 1. KCP 520

The ECAL mode index is indicating a mode number that does not exist.

1100 dir gyro excitation monitor 1. KCS 305


2. KCP 520

The directional gyro excitation is insufficient for proper operation. Directional gyro ex-
citation is currently not monitored, therefore this error should not occur.

1101 Pit cntrl pos rsnable mon 1. KCP 520


1102 Rol cntrl pos rsnable mon 2. Indicated control position resolver
(or loss of excitation voltage)
1103 Yaw cntrl pos rsnable mon
1104 Col cntrl pos rsnable mon

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.

1105 XS VG pitch att rate mon 1. KVG 350


1106 XS VG roll att rate mon 2. KRG 333
3. KCP 520

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.

1108 vert gyro validity mon 1. KVG 350


2. KCP 520

Page A--26 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

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.

1109 FD cmd monitor--pitch up 1. KCP 520


1110 FD cmd monitor--pitch down

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.

1111 FD cmd monitor--roll left 1. KCP 520


1112 FD cmd monitor--roll right

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.

1113 pitch pri svo DAC compare 1. KCP 520


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

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.

Revision 0, Dec 1997 Page A--27


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

1119 pitch pri svo midpoint volt 1. KCP 520


1120 roll pri svo midpoint volt 2. Indicated servo
1121 yaw pri svo midpoint volt
1122 pitch trm svo midpoint volt
1123 roll trm svo midpoint volt
1124 yaw trm svo midpoint volt

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.

1125 pitch pri svo amplifier model 1. KCP 520


1126 roll pri svo amplifier model 2. LVDT position sensor for indi-
cated servo (if KLA 570)
1127 yaw pri svo amplifier model
1128 pitch trm svo amplifier model
1129 roll trm svo amplifier model
1130 yaw trm svo amplifier model

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.

Page A--28 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

1131 pitch pri svo current monitor 1. KCP 520


1132 roll pri svo current monitor 2. Indicated servo
1133 yaw pri svo current monitor
1134 pitch trm svo current monitor
1135 roll trm svo current monitor
1136 yaw trm svo current monitor

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.

1137 pitch svo LVDT valid monitor 1. KCP 520


1138 roll svo LVDT valid monitor 2. Indicated servo
1139 yaw svo LVDT valid monitor 3. LVDT position sensor for indi-
cated servo

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.

1140 pit svo LVDT pos rsnable mon 1. KCP 520


1141 rol svo LVDT pos rsnable mon 2. Indicated servo
1142 yaw svo LVDT pos rsnable mon 3. LVDT position sensor for indi-
cated servo

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.

1143 pitch pri svo motor model 1. KCP 520


1144 roll pri svo motor model 2. Indicated servo
1145 yaw pri svo motor model 3. LVDT position sensor for indi-
cated servo

The indicated servo amplifer failed. The servo amplifier for a KLA 570 is modeled in
software using the following equation:

Revision 0, Dec 1997 Page A--29


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

Vm = ---9.34 x Ar --- 21.5 x Im


The computed servo motor voltage obtained using this equation is compared with in-
put servo motor voltage. When the absolute difference between computed servo mo-
tor voltage and input servo motor voltage exceeded 8.4 volts for 600ms it is consid-
ered a failure. This failure can only be cleared by executing preflight test again.

1146 pitch pri svo--no sol engage 1. KCP 520


1150 roll pri svo--no sol engage 2. Indicated servo
1151 yaw pri svo--no sol engage
1152 pitch trm svo--no sol engage
1153 roll trm svo--no sol engage
1154 yaw trm svo--no sol engage

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.

1155 pitch pri svo--no sol disengage 1. KCP 520


1156 roll pri svo--no sol disengage 2. Indicated servo
1157 yaw pri svo--no sol disengage
1158 pitch trm svo--no sol disengage
1159 roll trm svo--no sol disengage
1160 yaw trm svo--no sol disengage

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.

1163 XS pitch attitude monitor 1. KVG 350


1164 XS roll attitude monitor 2. KCP 520

S 1
attp = att + att x ------
s+1

attp -- predicted attitude


att -- current attitude (in degrees)
S
att -- attitude rate (in degrees/second)

Page A--30 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

1165 XS lateral accel monitor 1. KRG 333


1167 XS normal accel monitor 2. KCP 520

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.

1170 hydraulic pressure switch 1. No hydraulic pressure


2. Hydraulic pressure sensor
3. KCP 520

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.

1171 collect svo DAC compare 1. KCP 520


1172 collect svo midpoint volt
1173 collect svo amplifier model
1174 collect svo current monitor
1175 collect svo--no sol engage
1176 collect svo--no sol disengage

These errors should not occur, since the collective axis servo is not installed in the
Bell 430 installation.

Revision 0, Dec 1997 Page A--31


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

1177 pitch pri servo stalled 1. Indicated servo


1178 roll pri servo stalled 2. KCP 520
1179 yaw pri servo stalled

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.

1180 pitch trm servo stalled 1. Indicated servo


1181 roll trm servo stalled 2. Indicated axis control position re-
solver
1182 yaw trm servo stalled
3. KCP 520
1183 collect servo stalled

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.

Page A--32 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

1188 Invalid pitch cmd from FD 1. KCP 520


1189 Invalid roll cmd from FD6

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.

1190 LVDT detected in wrong axis 1. KCP 520

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.

1191 Multi axis DAC compare 1. KCP 520

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.

1192 VG # 1 reference volt mon 1. KCP 520


2. KVG 350

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.

1193 Yaw body rate monitor 1. KCP 520


1194 Pitch body rate monitor 2. KRG 333
1195 Roll body rate monitor

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.

1198 Low power system failure 1. KCP 520

Revision 0, Dec 1997 Page A--33


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

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.

1200 Analog input MUX address error 1. KCP 520

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.

1201 MUX test inputs out of range 1. KCP 520

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.

1202 Analog loopback failed 1. KCP 520

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.

Page A--34 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

1204 PTCH srv voltage range err 1. KCP 520


1205 PTCH srv current range err
1206 PTCH SNS rate range err
1207 PTCH SNS position range err
1208 PTCH CMD range err
1209 ROL srv voltage range err
1210 ROL srv current range err
1211 ROL SNS rate range err
1212 ROL SNS position range err
1213 ROL CMD range err
1214 YAW srv voltage range err
1215 YAW srv current range err
1216 YAW SNS rate range err
1217 YAW SNS position range err
1218 AD test range err
1219 PTCH LVDT range err

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.

Revision 0, Dec 1997 Page A--35


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

1220 YAW CMD range err 1. KCP 520


1221 PTCH TRM srv voltage range err
1222 PTCH TRM srv current range err
1223 PTCH TRM CMD range err
1224 ROL TRM srv voltage range err
1225 ROL TRM srv current range err
1226 ROL TRM CMD range err
1227 YAW TRM srv voltage range err
1228 YAW TRM srv current range err
1229 YAW TRM CMD range err
1230 COLL srv voltage range err
1231 COLL srv current range err
1232 COLL CMD range err
1233 ROL LVDT range err
1234 YAW LVDT range err
1235 Servo BD --15VDC range err

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.

Page A--36 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

1236 Servo BD 15VDC range err 1. KCP 520


1237 AP power range err
1238 PTCH MIDPOINT range err
1239 ROL MIDPOINT range err
1240 YAW MIDPOINT range err
1241 PTCH TRM MIDPOINT range err
1242 ROL TRM MIDPOINT range err
1243 YAW TRM MIDPOINT range err
1244 COLL MIDPOINT range err
1245 Servo BD 5VDC range err
1246 Unused input #43 range err
1247 Unused input #44 range err
1248 Unused input #45 range err
1249 Unused input #46 range err
1250 Unused input #47 range err
1251 Unused input #48 range err

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.

Revision 0, Dec 1997 Page A--37


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

1252 PTCH POS COS range err 1. KCP 520


1253 PTCH POS SIN range err
1254 ROL POS COS range err
1255 ROL POS SIN range err
1256 YAW POS COS range err
1257 YAW POS SIN range err
1258 COLL POS COS range err
1259 COLL POS SIN range err
1260 VG1 PTCH TAN range err
1261 SEC PTCH rate range err
1262 VG1 ROL TAN range err
1263 SEC ROL rate range err
1264 DG HDG SIN range err
1265 DG HDG COS range err
1266 RADAR ALT 2 range err
1267 ANALOG BD 5VDC range err

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.

Page A--38 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

1268 VG2 PTCH SIN range err 1. KCP 520


1269 VG2 PTCH COS range err
1270 VG2 ROL COS range err
1271 VG2 ROL SIN range err
1272 LAT ACCEL range err
1273 LONG ACCEL range err
1274 NORM ACCEL range err
1275 RG YAW rate range err
1276 RADAR ALT 1 range err
1277 ROTOR TORQUE range err
1278 PRI PTCH rate range err
1279 PRI ROL rate range err
1280 VG1 REF range err
1281 VG2 REF range err
1282 INTERNAL TEMP range err
1283 ANALOG BD 15VDC range err

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.

Revision 0, Dec 1997 Page A--39


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

1284 Unused input #81 range err 1. KCP 520


1285 Unused input #82 range err
1286 Unused input #83 range err
1287 Unused input #84 range err
1288 Unused input #85 range err
1289 Unused input #86 range err
1290 Unused input #87 range err
1291 Unused input #88 range err
1292 Unused input #89 range err
1293 Unused input #90 range err
1294 Unused input #91 range err
1295 Unused input #92 range err
1296 Unused input #93 range err
1297 Unused input #94 range err
1298 Unused input #95 range err
1299 Unused input #96 range err

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.

1300 Floating point Not a Number 1. KCP 520

A floating point math routine was called with a value that does not represent a valid
number.

1301 Floating point overflow 1. KCP 520

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.

1400 LVDT installation error 1. KCP 520

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.

Page A--40 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

1401 FA cyclic installation error 1. KCP 520


1402 LAT cyclic installation error
1403 pedal installation error
1404 collective installation error

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.

1405 config installation data error 1. KCP 520

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.

1406 AP install checksum error 1. KCP 520


1407 FD install checksum error 2. installation configuration module

A checksum error occurred when the maintenance processor attempted to retrieve


installation data from the configuration module for the indicated processor information.

1408 MAI processor not ready 1. KCP 520

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.

1409 no processor request error 1. KCP 520

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.

1410 no install data rx from MAI 1. KCP 520

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.

1411 receiving data checksum error 1. KCP 520

Revision 0, Dec 1997 Page A--41


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

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.

1412 AP cross side compare error 1. KCP 520

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.

1413 NVM checksum error 1. KCP 520

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.

1500 PFT -- 2 AP--As or 2 AP--Bs found 1. KCP 520

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.

1510 PFT sync err waiting for AP A 1. KCP 520


1511 PFT sync err waiting for AP B

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.

1512 AP A output control invalid 1. KCP 520


1513 AP B output control invalid 2. one of the servos (KLA 570 or
KSA 572)

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.

Page A--42 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

1514 PFT perf strap miscompare 1. KCP 520


2. Harness strap module configura-
tion

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.

1520 PFT accel valid norm mode fail 1. KRG 333


2. KCP 520

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.

1521 accelerometer lat tst val bad 1. KRG 333


1523 accelerometer norm tst val bad 2. KCP 520

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.

1524 accelerometer lat value error 1. KRG 333


1526 accelerometer norm value error 2. KCP 520

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.

1527 PFT accel valid test mode fail 1. KRG 333


2. KCP 520

Revision 0, Dec 1997 Page A--43


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

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.

1530 PFT pitch cmd DAC or ADC error 1. KCP 520


1531 PFT roll cmd DAC or ADC error
1532 PFT yaw cmd DAC or ADC error
1533 PFT pit trm cmd DAC or ADC err
1534 PFT rol trm cmd DAC or ADC err
1535 PFT yaw trm cmd DAC or ADC err
1536 PFT collect cmd DAC or ADC err

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.

1540 PFT pitch midpoint error 1. KCP 520


1541 PFT roll midpoint error 2. Indicated servo
1542 PFT yaw midpoint error 3. AP DISC switch pressed
1543 PFT pitch trim midpoint error
1544 PFT roll trim midpoint error
1545 PFT yaw trim midpoint error
1546 PFT collect midpoint error

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.

Page A--44 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

1550 PFT pitch LVDT sense error 1. KCP 520


1551 PFT roll LVDT sense error 2. Indicated servo
1552 PFT yaw LVDT sense error 3. LVDT position sensor for indi-
cated servo

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.

1560 PFT pitch servo position err 1. KCP 520


1561 PFT roll servo position err 2. Indicated servo
1562 PFT yaw servo position err 3. LVDT position sensor for indi-
cated servo

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.

1563 PFT pit trm srv position err 1. KCP 520


1564 PFT rol trm srv position err 2. Indicated control position resolver
1565 PFT yaw trm srv position err
1566 PFT collect srv position err

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.

1570 PFT pitch LVDT rate too high 1. KCP 520


1571 PFT roll LVDT rate too high 2. Indicated servo
1572 PFT yaw LVDT rate too high 3. LVDT position sensor for indi-
cated servo

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.

Revision 0, Dec 1997 Page A--45


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

1580 PFT pit offset crnt too high 1. Indicated servo


1581 PFT rol offset crnt too high 2. KCP 520
1582 PFT yaw offset crnt too high
1583 PFT pit trm offset crnt high
1584 PFT rol trm offset crnt high
1585 PFT yaw trm offset crnt high
1586 PFT collect offset crnt high

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.

1590 PFT pit offset volt too high 1. Indicated servo


1591 PFT rol offset volt too high 2. KCP 520
1592 PFT yaw offset volt too high
1593 PFT pit trm offset volt high
1594 PFT rol trm offset volt high
1595 PFT yaw trm offset volt high
1596 PFT collect offset volt high

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.

1600 PFT pitch drive err 1. Indicated servo


1601 PFT roll drive err 2. KCP 520
1602 PFT yaw drive err
1603 PFT pitch trm drive err
1604 PFT roll trm drive err
1605 PFT yaw trm drive err
1606 PFT collect drive err

Page A--46 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

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.

1610 PFT pitch monitor error 1. Indicated servo


1611 PFT roll monitor error 2. KCP 520
1612 PFT yaw monitor error
1613 PFT pitch trm monitor error
1614 PFT roll trm monitor error
1615 PFT yaw trm monitor error
1616 PFT collect monitor error

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.

1620 PFT pitch brake err 1. Indicated servo


1621 PFT roll brake err 2. KCP 520
1622 PFT yaw brake err
1623 PFT pitch trm brake err
1624 PFT roll trm brake err
1625 PFT yaw trm brake err
1626 PFT collect brake err

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.

1630 PFT rate valid norm mode fail 1. KRG 333


2. KCP 520

Revision 0, Dec 1997 Page A--47


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

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.

1631 PFT pitch rate test value bad 1. KRG 333


1632 PFT roll rate test value bad 2. KCP 520
1633 PFT yaw rate test value bad

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.

1634 PFT pitch rate out of range 1. KRG 333


1635 PFT roll rate out of range 2. KCP 520
1636 PFT yaw rate out of range

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.

1637 PFT rate valid test mode fail 1. KRG 333


2. KCP 520

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.

1700 Monitor gain translation type 1. KCP 520


1701 Invalid translation gain index

Page A--48 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Error #(s) Text Message(s) Possible failed unit(s)

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).

1710 Pitch Mistrim 1. KCP 520


1711 Roll Mistrim 2. Trim servo for indicated axis
1712 Yaw Mistrim 3. LVDT position sensor for indi-
cated
primary servo

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.

1800 Powerup 10hz sync error 1. KCP 520


1801 10hz frame sync error

The 10 Hz task frame in the autopilot processor lost sync with the 40 Hz task frame.

1900 Autolevel input in PAH mode 1. KCP 520


1901 Autolevel input in ALTC mode
1902 Autolevel input in ALTH mode
1903 Autolevel input in VS mode
1904 Autolevel input in IAS mode
1905 Autolevel input in GA mode
1906 Autolevel input in VNAV_Cap
1907 Autolevel input in VNAV_Track
1908 GS_Cpt input in Autolevel
1909 GS_Trt input in Autolevel

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).

Revision 0, Dec 1997 Page A--49


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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.

Page A--50 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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

Revision 0, Dec 1997 Page A--51


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

1563 PFT pit trm srv position err


1570 PFT pitch LVDT rate too high
1580 PFT pit offset crnt too high
1583 PFT pit trm offset crnt high
1590 PFT pit offset volt too high
1593 PFT pit trm offset volt high
1600 PFT pitch drive err
1603 PFT pitch trm drive err
1610 PFT pitch monitor error
1613 PFT pitch trm monitor error
1620 PFT pitch brake err
1623 PFT pitch trm 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 AP mode in the roll
axis only:
1120 roll pri svo midpoint volt
1123 roll trm svo midpoint volt
1126 roll pri svo amplifier model
1129 roll trm svo amplifier model
1132 roll pri svo current monitor
1135 roll trm 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
1153 roll trm svo--no sol engage
1156 roll pri svo--no sol disengage
1159 roll trm svo--no sol disengage
1178 roll pri servo stalled
1181 roll trm servo stalled
1195 Roll body rate monitor
1531 PFT roll cmd DAC or ADC error
1534 PFT rol trm cmd DAC or ADC err
1541 PFT roll midpoint error
1544 PFT roll trim midpoint error
1551 PFT roll LVDT sense error
1561 PFT roll servo position err
1564 PFT rol trm srv position err
1571 PFT roll LVDT rate too high
1581 PFT rol offset crnt too high
1584 PFT rol trm offset crnt high
1591 PFT rol offset volt too high
1594 PFT rol trm offset volt high
1601 PFT roll drive err
1604 PFT roll trm drive err
1611 PFT roll monitor error
1614 PFT roll trm monitor error
1621 PFT roll brake err
1624 PFT roll trm brake err

Page A--52 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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 AP mode in the yaw
axis only:
1121 yaw pri svo midpoint volt
1124 yaw trm svo midpoint volt
1127 yaw pri svo amplifier model
1130 yaw trm svo amplifier model
1133 yaw pri svo current monitor
1136 yaw trm 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
1154 yaw trm svo--no sol engage
1157 yaw pri svo--no sol disengage
1160 yaw trm svo--no sol disengage
1165 XS lateral accel monitor
1170 hydraulic pressure switch
1179 yaw pri servo stalled
1182 yaw trm servo stalled
1193 Yaw body rate monitor
1521 accelerometer lat tst val bad
1524 accelerometer lat value error
1532 PFT yaw cmd DAC or ADC error
1535 PFT yaw trm cmd DAC or ADC err
1542 PFT yaw midpoint error
1545 PFT yaw trim midpoint error
1552 PFT yaw LVDT sense error
1562 PFT yaw servo position err
1565 PFT yaw trm srv position err
1572 PFT yaw LVDT rate too high
1582 PFT yaw offset crnt too high
1585 PFT yaw trm offset crnt high
1592 PFT yaw offset volt too high
1595 PFT yaw trm offset volt high
1602 PFT yaw drive err
1605 PFT yaw trm drive err
1612 PFT yaw monitor error
1615 PFT yaw trm monitor error
1622 PFT yaw brake err
1625 PFT yaw trm brake err
1633 PFT yaw rate test value bad
1636 PFT yaw rate out of range
When a monitoring error resulting in loss of SCAS mode occurs in only one axis (i.e., roll primary
servo failure), SCAS mode is dumped for the affected axis (if SCAS 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 SCAS mode is disengaged, the axis/axes
failure light(s) will be cleared.

Revision 0, Dec 1997 Page A--53


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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

Page A--54 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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

Revision 0, Dec 1997 Page A--55


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

1513 AP B output control invalid


1514 PFT perf strap miscompare
1520 PFT accel valid norm mode fail
1630 PFT rate valid norm mode fail
The following monitoring error codes will result in the loss of AP mode in pitch, roll, and yaw axes,
but the AP fail light on the IIDS will not be illuminated:
1105 XS VG pitch att rate mon
1106 XS VG roll att rate mon
1108 vert gyro validity mon
1163 XS pitch attitude monitor
1164 XS roll attitude monitor
1192 VG # 1 reference volt mon
When a monitoring error resulting in loss of SCAS mode for all three axes occurs (i.e., DAC
command comparison), SCAS mode will dump, the SCAS annunciation will flash for approximately
5 seconds, the SCAS disconnect aural alert tone will sound for approximately 5 seconds, and the
SCAS fail light on the IIDS will be illuminated.
The following monitoring and preflight test error codes will result in the loss of SCAS mode in pitch,
roll, and yaw axes:
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
1513 AP B output control invalid
1514 PFT perf strap miscompare
1630 PFT rate valid norm mode fail
When an AP mode failure affecting one axis occurs and it is the only axis engaged in AP mode, AP
mode will dump, the AP annunciation will flash for approximately 5 seconds, the AP disconnect
aural alert tone will sound for approximately 5 seconds, and the AP fail light on the IIDS will be
illuminated. When AP dumps, SCAS mode will be engaged for any axis that does not have a failure
affecting SCAS mode operation and failure lights for any axis that is engaged in SCAS mode on
the IIDS will not be illuminated. If SCAS mode cannot be engaged in any axis, the SCAS fail light
on the IIDS will be illuminated and the individual axis failure lights on the IIDS will be cleared.
When a SCAS mode failure affecting one axis occurs and it is the only axis engaged in SCAS mode
with no axes engaged in AP mode, SCAS mode will dump, the SCAS annunciation will flash for
approximately 5 seconds, the SCAS disconnect aural alert tone will sound for approximately 5
seconds, the SCAS fail light on the IIDS will be illuminated, and the individual axis failure lights on
the IIDS will be cleared.

Page A--56 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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)

Revision 0, Dec 1997 Page A--57


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

961 Update timing CIP_APIN during power--up and power--down of system


components (dependent on power application/re-
moval sequence for each unit)
962 Update timing CIP_FDIN during power--up and power--down of system
components (dependent on power application/re-
moval sequence for each unit)
1410 no install data rx from MAI MAI power is applied after AP or FD power is ap-
plied or the AP or FD processors exit diagnostic
mode before the maintenance processor exits
diagnostic mode

Page A--58 Revision 0, Dec 1997


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

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.

Revision 0, Dec 1997 Page A--59


CS:15546S00.IDU
BENDIX/KING
KFC 500
FLIGHT CONTROL SYSTEM

Page A--60 Revision 0, Dec 1997


CS:15546S00.IDU
THE END

Você também pode gostar