Top Banner
AAGin 11 BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY AIRPL--ETC F/G 9/2 COMPUTER PROGRAM DEVE.MET SPECFICATION FOR IDAMST OPERATIOM--ETCIO) NOV 76F33615-76-C-1099 UNCLASSIFIED SPEC-SG-404Z AFAL-TR-76-20G-AOO-2 ML
272

BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

Oct 25, 2020

Download

Documents

dariahiddleston
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

AAGin 11 BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY AIRPL--ETC F/G 9/2COMPUTER PROGRAM DEVE.MET SPECFICATION FOR IDAMST OPERATIOM--ETCIO)NOV 76F33615-76-C-1099

UNCLASSIFIED SPEC-SG-404Z AFAL-TR-76-20G-AOO-2 ML

Page 2: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

08, Addendum #24r AF L-TR w 76 I208

SB 4042

~N/ MPI R JORMNVELOPHET ~CFCTOFOR I= E TIDNAL.&IO U4,ORAMS,?

A J U IJJL7 PPL IC ATIONS -FIAirI

Prepared byTHE BOEING AEROSPACE COMPANY

'vBOEING MILITARY AIRPLANE DEVELOPMENT

SEATTLE, WASHINGTON_ ,,

iv

APPROVED FOR PUBLIC RELEASE; DISTRIBUTION UNLIMITED

PREPARED FORAIR FORCE AVIONICS LABORATORY )T IC

AIR FORCE SYSTEM COMMAND L C E kUNITED STATES AIR FORCE LECTEWRIGHT-PATTERSON AFB, OHIO 45433 APR 1 7 1980

T.IS DYCUMsENT IS BEST QUALITY I PE A NU.__ THE COPY F uRNIzfflD TO DDC CONTAI D A E

SIGBhIICAST NW.!BF Of PAIGM 1=, DO RNiLLJ NNPROAMi L,,IBil, 0Ao-

80 4 15 059'cm

Page 3: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

DISCLAIMER NOTICE

THIS DOCUMENT IS BEST QUALITYPRACTICABLE. THE COPY FURNISHEDTO DTIC CONTAINED A SIGNIFICANTNUMBER OF PAGES WHICH DO NOTREPRODUCE LEGIBLY.

0

Page 4: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

FORE WORD

* This document establishes performiance and design requirements for the IDAMSTOperational Flight Program Applications Software.

VA t was prepared for the Air Force Avionics Laboratory under Contract NumberF33615-76-C-1099, in fulfillment of Contract Data Requirement List item 0001,sequence number 7.

Accer,;Icn For

RTIS GFIA&i-

DIC

DIS'RIB! :')N '

A

Page 5: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

IRITABLE OF CONTENTS

Section Title Page

Foreword iiTable of Contents iiiList of Figures viList of Tables 04Abbreviations viii

1.0 SCOPE I1.1 Identi ficati on I1.2 Functional Summary 1

2.0 APPLICABLE DOCUMENTS 22.1 Government Documents 2

3.0 REQUIREMENTS 33.1 Computer Program Definition 33.1.1 Interface Requirements 33.1.1.1 Interface Block Diagram 33.1.1.2 Detailed Interface Definition 73.1.1.2.1 IDAMST System Hardware Interfaces 73.1.1.2.2 Function Identification 73.1.1.2.2.1 Flight and Propulsion 73.1.1.2.2.2 Communication 203.1.1.2.2.3 Navigation and Guidance 203.1.1.2.2.4 Payload 243.1.1.2.2.5 Aircraft Systems 273.1.1.2.2.6 Defense 30

3.1.1.2.3 Software Interfaces 303.1.1.2.3.1 Executive Software Interface 31

3.1.2 Applications Software Architecture 413.1.2.1 Software Structure 413.1.2.2 Software Relationships 5

3.2 Detailed Functional Requirements 623.2.1 System Control Modules 623.2.1.1 Master Sequencer 623.2.1.2 Request Processor 623.2.1.3 Configurator 643.2.1.4 Subsystem Status Monitor 653.2.2 Operational Sequencers 663.2.3 Specialist Functions 673.2.3.1 Brute Force Specialist Functions 673.2.3.2 Computational 69

iii

Page 6: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

TABLE OF CONTENTS (Continued)

Section Title Page

3.2.3.3 Tailored Mode Specialist Functions 79

3.2.3.4 Handler Specialist Functions 873.2.4 Display Processes 903.2.4.1 Lights Display Process 903.2.4.2 Instruments Display Process 913.2.4.3 HUD Display Process 913.2.4.4 HSD Display Process 92

3.2.4.5 MPD Checklist Display Process 943.2.4.6 MPD Parameters/Status Display Process 953.2.4.7 Eri'or/Warning Display Process 953.2.4.8 IMK Fixed Text Display Process 993.2.4.9 DEK Mark Display Process 993.2.4.10 IMK Status Display Process 101

3.2.5 Equipment Processes 103UHF-AM Equipment Process 103

3.2112VHF-AM Equipment Process 1053.2.5.3 VHF-FM Equipment Process 1063.2.5.4 HF/SSB Equipment Process 1073.?.5.5 ICS Equipment Process 108

Public Address Equipment Process 1093.5.7 Secure Voice Equipment Process 1093.2.5.6 DEK Equipment Process 1103.2.5.9 DSMU Equipment Process I113.2.5.10 TACAN Equipment Process 1122.5.11 HCU Equipment Process 1132,. OME-A Equipment Process 114

3.2 5. 3 CCA Equipment Process 1163.2 5.14 Flight Control System Equipment Process 116

. IFlares Dispenser System Equipment Process 118,-Meter Equipment Process 118

, INS Equipment Process 119.5.1 SKE/ZM Equipment Process 120

; 9' LF ADF Equipment Process 121I UHF ADF Equipment Process 122

Rdar Altimeter" Equipment Process 1243.9-5.2? ILS Equipment Process 126

5 23 Compass Equipment Process 1273.. 5. "-4 Long Range Radar Equipment Process 128.. " 5. 5 IRD & W System Equipment Process 1293. 5. ?6 RHAW System Equipment Process 129.e.. 5. I Flight Surfaces Equipment Process 1303. . Aircraft Sensors Equipment Process 1303. ..5.,9 Bakes/Gear/Caution Equipment Process 1313 2. 5.20 Avionics On/Off Equipment Process 132

iv

SV n . .. . . .I i

Page 7: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

7*W .

TABLE OF CONTENTS (Continued)

Section Title Page

3.2.5.31 FDR Equipment Process 133

3.2.6 Special Requirements 134

3.3 Adaptation 1353.3.1 General Environment 1353.3.2 System Parameters 1353.3.3 System Capacities 135

4.0 Quality Assurance Provisions 1384.1 Introduction 138

* 4.2 Computer Program Verification 1394.2.1 Program Element Tests 1394.2.2 CPCI Integration Tests 140

° 4.2.3 Formal Software Testing 140

5.0 Preparation for Delivery 141

6.0 Notes 1426.1 Growth Items 1426.1.1 JTIDS 1426.1.2 TF/TA 1456.1.3 GPS 146

10.0 Appendix I: Hardware/Software Signal List 147

v

, 9 .

Page 8: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

LIST OF FIGURES

Nuiiber Title Page

3.0-1 IDAMST Composite Mission Requirements 4

3.1-1 IDAMST OFP Interfaces 53.1-2 IDAMST System Block Diagram 63.1-3 IDAMST Signal List for Applications Software/Examp'e 93.1-4 IDAMST Function Identification List 103.1-5 IDAMST Cockpit Instrument Panel 123.1-6 IMK-DEK-HCM 153.1-7 Avionics - Flight Control System Interface 193.1-8 Communication Equipment Control Requirements 213.1-9 INS Block Diagram 223.1-10 Navigation Control Requirements 253.1-11 Task States and Control 323.1-12 Application Software Organization 423.1-13 Master Sequencer Interface 43

* 3.1-14 Request Processor Interface 443.1-15 Configurator Interface 45

. 1-iF Subsystem Status Monitor Interface 46Operational Sequencer Interface 47

3.1-18 Computational Specialist Function Interface 493.1-19 Brute Force Specialist Function Interface 507.!-20 Tailored Mode Specialist Function Interface 51

handler Specialist Function Interface 52-isp'ay Processes Interface 53

3L-2, Equipment Processes Interface 54".1-24 Applications Software Control/Data Interfaces 56

' I Applications Software Components 63IK (Uflg A,i) Software Function 80

.- 3 MFFYi Software Function 83i.2-4 CCA (Pushbutton) Software Function 85

- HCH Software Function 86-, Sample PD Display Combined NAV/COMM Status 98

,- Sample I,11K Fixed - Text Display 100'-I Sample IMK Status Display 102

-,, so~.i ,' I P Transient/Receive Functions 143

vi I

Ip

Page 9: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

LIST OF TABLES

Number Title Page

3.1-1 Display Parameters 133.1-2 Categories of Compool Blocks 36

3.2-1 HUD Parameters 933.2-2 Nominal Display vs. MPD Assignment 963.2-3 Normal Displays at Beginning of Mode 973.2-4 EQUIP Summary 104

3.3-1 IDAMST Storage/Timing Estimates 136

I

' I.

vii

vll

Page 10: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

ABBREVIATIONS

ADC Air Data Computer

ADF Automatic Direction Finder

AFAL Air Force Avionics Laboratory

AMST Advanced Medium STOL Transport

BCIU Bus Controller Interface Unit

CARP Computed Air Release Point

CCA Column Control Assembly

CCIP Continually Computed Impact Point

CCT Combat Control Team

CRT Cathode Ray Tube

DAIS Digital Avionics Information System

" DEK Data Entry Keyboard

DITS Digital Integrated Test System

DS/MU Display Switch/Memory Unit

ECM Electronic Counter Measure

EFCS Electronic Flight Control System

EHARS Error Handling and Recovery Software

FcS Flight Control System

GMT Greenwich Mean Time

IOAMST Integrated Digital Avionics for a Medium STOL Transport

IFF,'SIF Identification Friend or Foe/Selective Identification Feature

ILS Instrument Landing System

HCU Hand-Controller Unit

HP/SSB High Frequency/Single Side Band

HSU Horizontal Situation Display

HUD Head-Up Display

IMK Integrated Multifunction Keyboard

INS Inertial Navigation System

LAPES Low Altitude Parachute Extraction System

v CL Master Caution Light

MDSL Modular Digital Scan Converter

viii

Page 11: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

MFDC iulti-Function Display Controls

MMK Master Mode Keyboard

MMU Mass Memory Unit

MPD Multi-Purpose Display

MPDG Modular Programmable Display Generator

OFP Operational Flight Program (Software)

OPS Operational Sequencer

RF Radio Frequency

RTU Remote Terminal Unit

SCP Sensor Control Panel

SKE Station Keeping Equipment

* STOL Short Take-Off and Landing

° TACAN Tactical Air Navigation

TM Tailored Mode

T/R Transmi t/Receive

T/R+G Transmit/Receive Plus Guard

UHF Ultra High Frequency

VHF Very High Frequency

VLF Very Low Frequency

ZM Zone Marker

ix

Page 12: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

1.0 SCOPE

1.1 IDENTIFICATION

This part of this specification establishes the requirements for performance,design, test, and qualification of a computer program identified as IDAMSTOperational Flight Program Applications Software.

1.2 FUNCTIONAL SUMMARY

-. This document specifies the software functional requirements for the AMSTMission Scenario,4efied ift-Referee 2-.4.l(a), Appendix Af. ApplicationsSoftware functions consist of providing the calculation and control capabilitynecessary for the following mission/operations task areas:

0 Flight and Propulsion,0 Communications,0 Navigation and Guidance

* d PayloadJ , Aircraft Systems *,

, @ ~Defense, __.

Section 2.0 contains a list of government/non-government documents which con-trini, . to this specification.

Section 3.0 describes the design and structure of the Applications Software,

and details the hardware/software interface and functional requirements.

,,tic< 4.0 contains procedures to test and verify the Applications Software.

Section 5.0 (Preparation and Delivery) is not applicable.

Section 6.0 contains a description of identified growth areas: JTIDS, TF/TA,

Section 10.0 contains a complete IDAMST signal list.

Page 13: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

2.0 Applicable Documents

2.1 Government Documents

2.1.1 Appendices to Contract F33615-76-C-1099 Statement of Work (SOW).

(a) Appendix A - "AMST Mission Profile and Scenario (updated)".

(b) Appendix C - "System Architecture".

(c) Appendix E - "DAIS Mission Software, OFP Applications (SA-201-303)",17 Jan 74.

(d) Appendix F - "DAIS Mission Software, Executive (SA-201-320)",26 Dec 75.

(e) Appendix H - "Software Management Plan".

(f) Appendix M - "TRW System Backup and Recovery Strategy (TRW6404-5-6-06)", Sept 75.

2.1.2 DAIS Documents (Reference)

2.1.2.1 ICD - Mission Operation Sequence

Pilot/Controls and Displays/Interface with Application Software (SA-803-200),

15 March 76.

2.1.2.2 Mission Software/Controls and Displays Interface (SA-802-301),12 March 76

2.1.2.3 DAIS System Control Procedures, (SA-IO0-101 Appendix A), 7 Nov 75.

2.1.3 IDAMST Documents (Program generated).

2.1.3.1 Computer Program Development Specification, IDAMST OFP Executive(SB 4041), July 76.

2.1.3.2 Computer Program Development Specification, IDAMST OFP ErrorHandling and Recovery (SB 4043) July 76.

2.1.4 IDAMST Documents (Reference)

The following documents, because of release dates, serve only as referencedocumentation for this specification; however, are considered prime to furtherdefinition of the IDAMST system design.

2.1.4.1 System Specification for IDAMST, Type A (SI-lOO), June 76.

2.1.4.2 Prime Item Development Specification, IDAMST Processor, TypeBl (S1-4030), June 76. I

2.1.4.3 System Segment Specification, IDAMST Control/Display Subsystem,

Type A (Sl-5020), June 76.

2

Page 14: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.0 REQUIREMENTS

This section contains interface and functional requirements for the IDAMST OFPApplications Software.

The AMST mission defined in Reference 2.1.1, Appendix A "AMST Mission Profileand Scenario" requires avionics software support in the areas of flight andpropulsion, communications, navigation and guidance, payload, aircraft systems,and defense. The Applications Software provides the support necessary to sat-isfy the design and performance requirements for these mission areas. Thesesupport functions include:

o C&D controlo Sensor controlo Specialized calculations (e.g., navigation, CARP)o Equipment health monitoringo Status maintenanceo Mission mode controlo Limited software reconfiguration

, An overview scena-io of the AMST mission is shown in Figure 3.0-1.

3.1 COMPUTER PROGRAM DEFINITIONr3.1.1 Interface Requirements

This section describes interface requirements imposed on the Applications Soft-ware design by other IDAMST equipment/computer programs.

Fiqu-e j.l- identifies the three computer program configuration items compris-ing the OFP software subsystem for IDAMST. The Applications Software function-ally interfaces with the AMST hardware subsystems integrated into IDAMST. Thisf rctional interface is shown by dashed lines on Figure 3.1-1 as a part of theF' [xecutive Software. Overall control of interface operations is provided

by d- xecutive.

The basic IDAMST software design and core element hardware design (provessors,jaT- hu remote terminals and control/displays core elements) are influenced!, Lr!e Dgital Avionics Information System (DAIS) design currently beingdeveloped by the Air Force Avionics Laboratory (AFAL). This is evidenced byc.c, tc architectural design requirements stated in this specification (Sec-

-). Also imposed on the OFP software as design considerations are-s and techniques for structured software design as noted in Sections

o,'ic ii of Reference 2.1.1, Appendix H "Software Management Plan".

-,i. 'ant characteristics of the IDAMST core element hardware effecting the' ,i:C2 cdticns software design are defined in Reference 2.1.1, Appendix C

L!,tr Arch itec ture".

Interfaice Block Diagram

l r - R.l-? is a block diagram of the IDAMST system. Three mission processorsarc e ' yed in wh.ch the OFP Applications Software resides in support of theAMST m-ssion, Overall system control is directed by the Executive Software,

3

Page 15: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

0 0

Cc zLLW( IL L)

z ~z aO cc -

oz w c

0 c

L a

U) -

IIr

> < I x 4(

0 LA.U. xa 04

ZA.Z 04

L) n LU 4

0 ' U4

Page 16: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

~r A

U)U

0

W4-4

0

Page 17: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

I.

litl

'4

tS

CI

I

cd I U

0. .I

m~.cc IiiI~i~tII DLA. LL.

rc6

--~ -

Page 18: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

including control of the functional interfaces between the Applications Soft-ware and the IDAMST system hardware. The task of the Executive with respectto these hardware/software interfaces is to make the mechanization of datatransfer transparent to the Applications Software and thereby decouple thesystem core element hardware programming considerations from the purely func-tional Applications Software tasks. To the Applications Software, the task of

communicating with IDAMST system hardware is essentially the formattinq, order-ing, and generation or interpretation of avionics hardware parameter (signal)lists.

3.1.1.2 Detailed Interface Definition

The intent of this paragraph and subparagraphs is to define the functionalrelationships of the Applications Software to the IDAMST system hardware andassociated OFP software (Executive and EHARS).

3.1.1.2.1 IDAMST System Hardware Interfaces

, Figure 3.1-2 illustrated the IDAMST system hardware in block diagram form.Figure 3.1-2.1 is the complete IDAMST equipment/disposition list.

The Executive software is tasked with the responsibility of making the mechan-i n frequency of communication transparent to the Applications Software.

Programming considerations imposed by the core element design are not apparentto the Applications Software. Therefore the Applications Software/hardwareinterfaces can be described by a signal list. Figure 3.1-3 is an example ofS,,-h a ;ist which is required to define the functional interface to the avionics

r r'ar n . The Application Software/IDAMST Hardware interface shall be as listedin iection 10.3.1.1.2.2 Function Identification

Ficure 3.1-4 identifies the selected functions for IDAMST requiring Applica-t.nrs Software support. These functions are categorized into six basic mission/i)lerations task areas:

o Flight and Propulsiono Communicationso Navigation and Guidanceo Payload. Aircraft Systemsc Defense

3.1.1.2.2.1 Flight and Propulsion

7nt !DA.IST functions in this category are those associated with pilot/copilot-3.t,-ol and management of the AMST flight. Five subcategories are identified:

c Crew Displayso Crew Controls

n Flight Control SystemD Weights and Balanceo Energy Management

7'.I

Page 19: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

@l ae ral ! @Iue e, Is |

------.- -- -....: .'

ip to IIIi I lllI !i l 'C; I glII li .ll. ll l il

...... ... ..... ...

4 11' :: : m :: : :: . . .. . .......... . . . . . . . . .

q . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . .

---------"-------- '"'"-"i noI IIIIII 11 IIl I

,,.I l, ...,,, ,,, Il lilllll

[ .. .. it , ss .II . ......s

S i I""'"'"'"'

IIIIII IIIt llll Illllll ll

IIIIIIIIII

IIII I I I iiiiiillllllllllI

giiiiii

,i i • I ii N ll~ jj • SISi IIj I 1,,11 s Ii IIIuIIIIe,,se

_ . , , ,, l.,

: ., , ,, ,,,,, ,,,,,,,Il , , ,! , i. , . . ,, ,, , .,, ,, , ,,,

I.l

*e.

Page 20: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

if~ ~ AP . a 4 0 Pd d 0

at 4 ' 9 0 L

'A a a a a a .. .d . CDL61J

00

40 af..,L.

6) ~ UA W610f. a 0.

-1 13 0 0o

0 4 D a V4 0 0

LI)

a 0

4: a- 5

o o 0 0

ts 0 0 0 0

(L 0 0 0 0

0-0

ifidLf ;f. ;-

ID 0 to Ziif I if *' K .4 ' 4/

a a aNo=

Page 21: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

! I

C za

Tzz

J 0

I--- t-

z

-T--r

z2LI4

U -11 11 1 LL--TI

z I

'10

Page 22: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

Figure 3.1-5 is a cockpit layout of the controls and displays integrated intothe IDAMST system.

3.1.1.2.2.1.1 Crew Displays

The Application Software shall transfer formatted parameter lists andcontrol commands to the various IDAMST display devices. These devices aredivided into two categories:

o CRT displays

o Dedicated displays

CRT Displays

CRT-type displays integrated into the IDAM*ST system are:

o HUD (pilot's, co-pilot's)

o HSD (pilot's, co-pilot's)

o MPD (pilot's, co-pilot's, center)

o IMK (pilot's, co-pilot's)

Funrtinnally the interface between the HUD, HSD, MPD displays and the Appli-cations Software shall be a list of ordered parameters and control datatransmitted to the Modular Programmable Display Generator (MPDG). Displayfo,- 3tting and symbol generation is the task of the MPDG. Table 3.1-1 lists

r- Nr iieters and types of information to be displayed on the HUD, HSD, andPL.

The interface between the IMK CRT and the Applications Software shall be.or.trol and page identification transmitted to the Alpha/Numeric Symbol Gen-P'n 'i()r.

Dedicateo Dispjlas

* il ledicated displays have been integrated into the [DAMST system. The'c Iowinq displays shall be controlled by the Applications Software.

0 PCrlc

o irsoeed

a 1titude

Verticdl Velocity

, Meter

a Wirning Lights

EFCSSpeel LowGround Proximity Warning

o lat'ker Beacon Lights

11

Page 23: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

II LI IElI

- El I [iIW]Wo

fij

0

M&i

Page 24: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

I.0)4-4-

n 4.- €o L - 4(A 4-E) L. . 0-

C) (0 'S CU 4.0 0-4-t- .-. -0)0) >, 00 .4J S- t a.o - L.

0 10 E 4-0 L, -. 4= L =z L-- E W r 4-) M M -9- 4- r -Er

4J 4-4-'EU4-' L) e M4-' C0 > - V)(0." 4-'i O I 4 - 0,. 0I u0 " -- - m (% O ..-) (0 4-) V) A S- 4- . ) LC . . t" o . r- CL.,- a-

* .- 0o

Er- 0 4.-

*u tA L. 0Lfl U4-'- s- o S-(o o > (a- GJ :€ faS..-LI ) D - -

V) m o. L!w<: i )C L

(A CL~~r~W4)

* m 4- "0 r0 0)

.. A "- .(aLL 0 .a" ---

13 -o

. a) & AC

fu4- In Q -

> 0 0 ' 0

tto WS-w~ -

0 4-'O0C5.-S-0)0)1JC4 4)J) V

- C-

~0) C-~j -0) 4-

- ~ ~ ~ ~ ~ C c S- 5-1.0 ) i- )0~..) 0-C I m 0~C M( 0 .J.r E-

. C, V U0) *C0) 'Z; = in-LS- c -.- 0a ) u no.- a>C:v~ -n40 ,, 5 e - - : :r S- 0)a

4ZC 40) 0))000.1-C-) o- ) c

4r-. ~C f~ - 4'- W ' 0 a) CCC4-)JCCrS

U 0 ) n0) W S-J 0) U 0- E -)~ mi 0 (M-

C -WC =C 4 4 4 M 4) X13

0 0

Page 25: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.1.1.2.2.1.2 Crew Controls

The controls shown on Figures 3.1-5 and 3.1-6 are as follows:

o Integrated Multifunction Keyboard - IMK (pilot's, co-pilot's)

o Data Entry Keyboard - DEK (pilot's, co-pilot's)

o Column Control Assembly - CCA (pilot's, co-pilot's)

o Multifunction Display Controls - MFDC (pilot's HSD and MPD, co-pilot'sHSD and MPD, center MPD)

o Hand Controller Unit - HCU

o Master Mode Keyboard - MMK

The Applications Software shall accept input from these devices, andafter processing display requested information and/or acknowledgereceipt of control action.

14

Page 26: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

~~WWWWfo E1mWRIMI

WPw lw0

TwilM III WWWWWWO

FliwL 0LJ

F 11 __

IHro E P'EE

15

Page 27: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

.I- ' '

Integrated Multifunction Keyboard (IMK)

The two IMKs (pilot's and co-pilot's) are the primary crew control devices.The IMK (Figure 3.1-6) consists of two sets of keys and a CRT. There areeight keys across the top of the IMK. These top keys allow the crew to selectspecial functions that do not normally occur during a current mission phase.These functions are:

o Communications - used to control the radio equipmento Navigation - used to control the navigation equipment

and steering modes.o Sensors - provides sensor mode control.o Systems - provides the crew with various system functions.o Library - allows the crew to activate several special

function that do not fit into other functional areas.o Checklist - enables the crew to request MPD checklists.o Payload - provides control for loading and dropping of

cargo.o DITS - provides access to test system.

The functions implied by the ten IMK side keys depend upon the current stateof the IMK. Each side key has a corresponding legend on the IMK CRT whichindicates the current meaning of the key. There are one or more IMK pages foreach mission phase and for each special function invoked by one of the eightIMK top keys.

The eight IMK top Keys are backlighted green (active) or yellow (inactive).The ten side keys are backlighted white.

The IMK CRT was discussed as a display device in Section 3.1.1.2.2.1.1.

Data Entry Keyboard (DEK)

The two DEKs (pilot's and co-pilot's) provide data entry capability and allowcrew to perform MPD checklist functions.

The DEK (Figure 3.1-6) consists of 16 pushbuttons used as follows:

o Data Entry

digits 0 through 9CASE upper/lower caseENTER : indicating end of data to softwareCLEAR : indicating restart to software

o Checklist

CHECK : check off itemSPACE : skip itemPAGE : advance page

The identification of each key depressed is sent (one at a time) to the Applica-tions Software and shall be processed upon receipt of an ENTER.

16

Page 28: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

Column Control Assembly (CCA)

The two CCAs (pilot's and co-pilot's) allow microphone control by crew members.Shaker commands to the CCAs shall be generated by tl;e Application Software when-ever a stall condition becomes imminent.

Multi-Function Display Controls (MFDC)

The MFDC consists of the six pushbuttons functionally attached to each MPD/HSD device. These pushbuttons are used by the crew to:

o Switch a display from one device to another.o Request sub-types of a display.o Vary the display scale.o Request sensor video.o Etc.

The selected pushbutton(s) are backlighted.

Hand Controller Unit (HCU)

The HCU is used for: 1) navigation data entry and 2) radar antenna control.Figure 3.1-6 shows its layout.

HCU control consists of:

o Seven pushbuttons allowing selection of the CRT where cursoris applicable.

o A hand control to move cursor.o A button on the hand control which activates output of cursor

displacement (lst push) and terminates or designates to softwarethe final cursor position (2nd push).

The pushbuttons are backlighted green (active) or white (inactive).

Master Mode Keyboard (MMK)

The MMK (Figure 3.1-6 ) allows crew members to select high-level missionmodes. These mo, es determine the parameters to be displayed and the controlcaoability to be offered by the Application Software. Only one Master Modecan be active at any time.

MMK pushbuttons are backlighted green (active) or yellow (inactive).

The Master Modes are:

START Includes flight crew preflightTAKEOFF Taxi, takeoff, area departureENROUTE Later climb, cruise, early descentAIR REFUEL Rendeqvous, acquisition, refuelTF/TA Terrain Following/Terrain AvoidanceAIR DROP All except LAPES

17

I...

Page 29: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

LAPESLAND Approach, land, taxiGO AROUNDSHUTDOWN Includes flight crew post flightGROUND TEST Ground crew preflight and postflight

3.1.1.2.2.1.3 Flight Control System

The Flight Control System is assumed to be flight critical; therefore it wasmechanized in a triplex configuration. The air data and aircraft attitudeinformation is required for flight control and assumed to be available for useby the avionics. In addition, the avionics system shall provide steeringsignals to the flight control system and monitor the flight control status.

The IDAMST - Flight Control System interface is shown in Figure 3.1-7.

3.1.1.2.2.1.4 Weights and Balance

* •A simple weight atid balance function is assumed, whereby aircraft grossweight, total fuel, and calculated center of gravity (c.g.) is displayed viaan MPD. The crew must input aircraft gross weight and c.g. position priorto takeoff and decremented weight and c.g. shift after cargo drop. Themission processors will maintain current estimated gross weight and c.g.position prior to takeoff and decremented weight and c.g. shift after cargodrop. The mission processors will maintain current estimated gross weightand c.g. position throughout the flight, based upon crew inputs, remainingfuel, and fuel distribution. Cargo weight decrements and c.g. shifts maybe pre-stored and only the drop event need be signalled to the processors viathe IMK.

3.1.1.2.2.1.5 Fnergy Management

Ehgine performance and airplane operations can be optimized by energy manage-ment technique. Energy management has been noted only as a potential growthitem.

18

Page 30: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

Isivis EN OW i =C m

t 4I

asnivis aow NO

IailtLA

I _ _ _ _ _ _toViabI

IINI OI I

SAIVS GN 30O

1 14

Page 31: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.1.1.2.2.2 Communications

IDAMST provides the flight crew with the capability to control variouscommunication devices for air-ground, air-air, and internal communications.A description of the function(s) associated with each device is given below.

The Intercommunication Set (AN/AIC-18) provides:

o two-way voice communication between crew stations

o interfaces with radio tranceivers, navigation receivers, publicaddress amplifier, and maintenance intercom outlets

The ICS allows for selection, control, and distribution of radio systems forairborne/ground station communication and monitoring.

The P.A. System (AN/AIC-13) is used for voice announcements in the cargoareas.

The two UHF-AM (AN/ARC-164) are used for military communications and asbackup ADF receivers. They provide short-range, line-of- sight, two-waysimplex voice communication with ground systems and other aircraft, operatingin the 225-399.95 mHz frequency band. When the radio is in backup ADF mode,bearing is obtained via the ADF EQUIP.

The VHF-AM radio (Wilcox-807A) is used for (CT and civilian communications.It provides two-way simplex 160 nautical mile voice communication in the118 - 135.975 mHz frequency band over line-of-site propagation paths.

The VHF-FM radio (FI4622A) is used primarily for military/CCT communications.It provides short-range line-of-sight, two way simplex voice communication inthe 30 - 75.95 mHz frequency range.

The HF/SSB radio (AN/ARC-123) is used for long-rwige military communications.It provides two-way simplex voice communications at distances up to 2,500nautical miles, operating in the 2 - 30 mHz frequency band.

The Secure Voice System (TSEC/KY-58)encrypts and decrypts VHF/UHF voicecommunication.

The IFF/SIF (AN/APX-1Ol) is used for automatic radar identification andposition/altitude reporting in the civil air traffic control system andsimilar data in the tactical traffic control environment. Its operationalfrequency band is 1030 - 1090 mHz.

Control is implemented by the flight crew via IMK. The particular controlassociated with each device shall be as shown in Figure 3.1-8.

3.1.1.2.2.3 Navigation and Guidance

IDAMST provides an Integrated Navigation System (Figure 3.1-9 ) which per-forms the following functions:

20

Page 32: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

LL.

C-1)

Z:C).

CDA

cc LU 2

LL. L- ~j (A LIUiCr 0 r C0 0LUCA-

CLLU LLJ LJ =D(M - -

2:~c~0 OL'-

C) C)

U- I

I-, LU w )

2D: fr- L)D

2:1C M:C

UJ :D LU_ 0

2:1 w CD CA)~ IUCU- D L- 2:.-

HUJLUQCD~ C)D

C -

-J V) X:L CD+~Q 0-L): L)rZ -=i

= Y U- - : =C)-iUD U -- m ::D CI = ID

CD F- -,U V CDi L U

2: t-

><L' U =) L2

+ CY LU Or-2: M -_, LU Of a. Mr C-

CD L)U- LU ) O l wC) 0 JC)2 CD

+ ~2:C:LU 21

Page 33: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

A 40

so~* ~ 14 - 0 - -

C,-Q *zw a ' CK14 -C zi- zJ *

>, 0~ 0>

a. .

o 0 o

00

2 W22

Page 34: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

Area Navigation

The following enroute and terminal navigation functions are provided:

o Automatic three dimensional navigation and guidance within theATC environments

o TACAN slant range correction

o Automatic tuning of navigation radio receivers

o Great circle navigation and optimization of navigation position

o Route and terminal navigation data storage capacity adaptable toAir Force requirements

o Simple reversion to VORTAC or Inertial navigation

o Offset track capability

Computed Air Release Point (CARP)

Automatic CARP calculation capability shall be provided. Means of enteringload characteristics, wind data, relative target location, and positionupdate capability shall be designed for pilot ease of operation.

Rendezvous

4avigation data will be processed to compute guidance and steering data toenable rendezvous with other aircraft.

Flight Director

Fliaht Director Command Signals are provided for display on the pilots'Altitude Director Indicator.

Steering

Steering signals are provided for the Flight Control System.

rc 3ccomplish the above functions, the following sensors are provided:

o The TACAN System (AN/ARN-118) furnishes data relative to a selectedTACAN facility operating in the 962 - 1213 mHz frequency band.

o The two Radar Altimeters (AN/APN-194) are range tracking radars whichprovide altitude information from 0 - 5000 feet.

o The OMEGA Radio Navigation System (AN/ARN- ) provides airplaneposition fixes using the worldwide network of VLF ground transmitters.

23

Page 35: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

o The Magnetic Compass (C-12) provides heading information fornavigation.

o The LF/ADF (DF-206) provides the navigation calculation with bearingto a selected low frequency radio station.

o The UHF/ADF (DF-301E) provides the navigation calculation withbearing to a selected ultra-high frequency radio station.

o The INS (Carousel IV) is a self-contained inertial navigation system(including a digital computer) which provides worldwide aircraftnavigation entirely independent of ground communication.

o The Instrument Landing System (AN/ARN-108) is used in conjunctionwith ground transmitting equipment and airplane flight directorcalculations to provide display capability for marker beacon, glide-slope, and localizer signals.

o The Station Keeping Equipment (AN/APN-169) is a cooperative air-to-air station keeping system for flights of up to 36 aircraft. Itenables these aircraft to locate and identify one another; and tomaintain formation/rendezvous regardless of visibility. The SKEinterfaces with the MDSC to provide a formation display.

o The Long Range Radar (AN/APQ-122) provides precise navigationcapabilities for long-range ground mapping, weather detection,and beacon interrogation. A high-resolution CRT radar displiyis available to the crew upon request. Data is input into thenavigation function via HCU in conjunction with the CRT display.

o The Flight Control System provides air data, attitude, and modeand status information. This information is processed by theavionics system to provide steering data for the flight controlsystem.

Sensor control is implemented by the flight crew via IMK. The particular

control associated with each sensor shall be as shown in Figure 3.1-10.

3.1.1.2.2.4 Payload

IDAMST functions in this area consist of providing payload status reportingand automatic load release control.

Status

The Applications Softwareshallmonitor, maintain and report (via CRT display)status of-

o Ramp and cargo door

o Chute release

o Caution signal

24

a *Id

Page 36: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

L~LLj

ctx L"

CD =-. -

2 -j 0 LU)L -x -C '

L D : ) V) CF - IL)i LU V

LU __ L o (/AC) I- -i CC X

~-jcc LU- I- -w F-> IA I- LU -J

X-- LU 2 Fp- <,- .) - : LU :OC) D - ~ -- w .- C-- L CD I.-$ --. ( L V) uj M j x :

C)

I- LL. .

C>J 44 ) L/X

C)DX:j .j C)i V)(L(

C :) i- 21z -u~- LQ L ULJ L

LULU = (/ I- I-CD wU LU LLLU > i LnL( ... J :3 :or L-U V)-- Cm

cX ci un Ll I< C) LD w >: - r

LUU0-I- C 3 'L Lu C -: cc -E(C cL b ~-L = VI--L LUJ

C) LcLU LL w r,4 L(_) '~t-:XLU = C :

u =I ~LU L

LL C:) C, L- VM: I - - F- L) L-_

a:~f CDU-

C)~ ~Cc

cf-L

7) <l LU I (D L"

C)- ( -j <t: -jL) )

LjL

C) C",CD

25

Page 37: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

0L cr L -C) ~ LLJ

V)Z- V LJ J LA

C) Z I- MV -

=D >- > ' m i - L v)znC3 < -r (x C)L- - tit

wf0~~! :] 3 L ) ;- .

LAJ

u-J Ifx CC- l C)

C orC L LO- Q- YEo C~A C C) C.J ~JQ)

CIO. L L' U -i cZ-(A (uCDU- (D = = C i j - (-j

cc ~ ~ ~ II1~ CI LIfLU.. L C jC LJ -WLL C y- C) LnCXW L 7 LA-~j .V) -o .

-- ~ O - A - - T0'>

L. -X -r C)< w= (- !g

C) :m:x -:w /) ujuj V Z.;

U-1J

U- V) A LA.LA- ~ ~ ~ 0 L -

(z)cy :D c C)CD

PC:,~~ I~ uiV - r WLCD ui CDj

uj LL D ::.cr LA

Page 38: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

o Jump signal

o Paratroop alarm

o Aft door deflection

Release Control

Cargo delivery control consists of a load release signal output from theCARP function.

3.1.1.2.2.5 Aircraft Systems

T he IDAMST functions relating to this area include warning, caution/monitor-

ing, electrical control, and test of the various subsystems.

Warning

IDAMST incorporates either copied or generated warning functions. Copiedwarning functions are monitored at the flight crew's hardwired (dedicated)indicators and their status copied into IDAMST processors. Warnings aresubsequently displayed on the c,,'s primary flight displays and appropriateemergency checklist procedures are selected for display on the pilot'scopilot's MPD. Copied warning functions do not have responsibility fororiginating the warning signal. This is the responsibility of the affectedsystem or equipment. Generated warning signals originate within the IDAMSTsystem. Primary responsibility for detection and warning is an IDAMST

Ccpied Warning functions shall be

F h

Stabilizer Trim

,eng.,rated Warning functions:

'rc,,nd proximi warning shall be generated on the basis of aircraft altitudeve round, vertical velocity, gear position, and flight mode. Visual

:rd 3ural warnings will be commanded.

-all- warning shall be generated on the basis of flap position, angle ofit,-lf-k, and thrust computations in the STOL configuration. Visual,-dcout on flight instruments and the "stick shaker" command shall beinitiated by the IDAMST system.

'I peed warning shall be generated when the computed airspeed approaches';,ninum airplane requirements. A visual warning will be provided.

27

Page 39: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

Overspeed warning shall be generated when the computed airspeed exceeds theairplane maximum speeas (VH/MH). Aural warning (clacker) and visual displayshall beprovided.

EFCS warning shall be generated when the IDAMST processor is error status isreceived from the Flight Control System. Aural warning and visual displayshall beprovided.

Caution Monitoring

IDAMST provides seccndary control for caution functions: It shall copy currentstatus and provide (on request) an MPD procedure checklist display to assistthe crew in determining the cause of the caution message. Monitored functionsare derived from monitor sensors, and displays of significant parameters areprovided to the crew via MPD display.

Copied Caution Functions shall consist of

* Electrical _SystemHyd raul i c S ys tenF ueISj s_temBoundar'y Layer ControlAir- Condi ti on i n2Anti- Ic eOverhead Caution AnnunciatorBrakes

Monitored Functions shall consist of

Enjine Parameters (Nl, EGT, N2, FF, oil pressure and oil quantity)Flap_ Position (left USB, right USB, left outboard flap, left inboardflap, right inboard flap, and right inboard flap).Control Surfaces Position (spoiler elevator and rudder)Avionics Systems Hardware Status

Electrical Control

Control is included in the IDAMST processor to provide automatic on/off controlof the remote power controllers. Avionics power management is maintaineibased on the following criteria:

o "anual crew entry

o Automatic start-up

o "1aster mode

'-il-idl [oove.- requirements for overload conditions

utoitic res,, of nuisance trips

28

Page 40: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

IDAMST provides on/off control for the following:

Instruments and Aircraft Systems Navigation and Guidance

o counting accelerometer o long range radaro gear-up and locked-left o radar altimeter 1o gear-up and locked-right o radar altimeter 2o weight on gear - left o magnetic compasso weight on gear - right o INSo stick shaker I o OMEGAo stick shaker 2 o ILS 1o stab. trim position o ILS 2o flap position - left o LF ADFo flap position - riaht o UHF ADFo fuel totalizer o TACANo engine 1 o SKEo engine 2

Communications Controls and DisplAays

o public address o HUD 1o intercommunication set o HUD 2, HF/SSB radio o HSD 1o VHF-AM radio o HSD 2o VHF-FM radio o MPD 1o UHF-AM radio I o M.PD 2o UHF-AM radio 2 o MPD 3o IFF o IIPDG Io secure voice o MPDG 2

o DSMUDefensive Measures o MDSO

o MFDCo IRD & W o HCUo rz ! &4 o MMKo flares dispenser

29

Page 41: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

Test

IDAMST shall incorporate a limited, in-flight test capability by virtue ofBITE, software redsonableness test on input data or associated computedvalues, and correlation of sensor data by direct comparison with redundanthardware or similar hardware. The extent of in-flight testing which willbe practical is TbD. Test data shall be recorded on the DITS recorder.Selected data shall also be input to the Crash Data Recorder.

3.1.1.2.2.6 Defense

The IDAMST functions in this area are those associated with threat detection,warning, display, and flare dispensing.

Infrared Detection and Warning System

The IRD & W System is a defensive countermeasure which detects heat sources.A quadrant-oriented threat display is produced automatically on an MPD upondetection. IRD & W crew control consists of on/off.

Radar Homing and darning System

The RHAW System is a defensive countermeasure which detects radar sources. Aquadrant-oriented threat display is produced automatically on an MPD upondetection. RHAW crew control consists of on/off.

Flares Dispenser System

The Flares Dispenser System contains four volleys of flares which are used asa defensive measure against infrared seeker threats. Crew control consistsof on/off, and the capability to drop flare volleys in any combination,either individually or as a group. Flare status is displayed on request.

Simultaneous threat information from the IRD & W and RHAW Systems will be

merged into one display.

3.1.1.2.3 Software Interfaces

The only external software interface defined for the Applications Softwareis with the OFF JxEcutive Software. The Executive Software providesservices for the ex.cution of real-time applications, sharing of common data,interprocessor cornurication, and communication with and between remoteterminal units.

Those EHARS functions relating to the Applications Software are performed bycode imbedded in The Appliations Software. This interface is described indetail in Rpference .1.3.2.

30 i

Page 42: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.1.1.2. 3.1 Executive Software Interface

The Applications Software consists of Tasks, Comsubs, Compool Blocks, andEvents.

Tasks and Comsubs are processing modules, containing executable code and localdata. Compool Blocks are data modules used for communication between Tasks.Events are boolean values used for control interactions between Tasks.

Tasks interact with the Executive through Real Time Pseudo-Declarations and

Real Time Pseudo-Statements.

3.1.1.2.3.1.1 Tasks

Tasks are the principal components of the Applications Software.

At any time, any Task in the system has a "state". The possible states of* a Task are shown in Figure 3.1-11 . Note that not all states are

mutually exclusive; thus, a Task which is "executing" is also dispatchable,active and invoked.

Immediately following system initialization, one Task, the Master Sequencer,is Invoked by the Executive, and all other Tasks are in Uninvoked state.Thereafter, Tasks can be put into Invoked state (Scheduled) or put intoUninvoked state (Cancelled) only by Real-Time Pseudo-Statements executedwithin other Tasks.

imediately after beinq Scheduled, a Task is Inactiv2; however, it has thepotential to become Active, depending upon its Event Codition Set. TheEvent Condition Set is a collection of Conditions, each of which may beeither "on" or "off". Each Condition has a "desired" value. When all theconditions in the Event Condition Set have their desired values, if thETask is Inactive, the Lxecutive will put it into Active state. A Task mayhav'e a null Event Condition Set, in which case it can only be Inactivenomentar i I y.

Ea-h Condition in an Event Condition Set is associated with a set of Events.Aren any of these Events is set on, the Condition is set on; when any ofthese Events is set off, the Condition is sce off. One Event may beassociated with more-t7an one Condition in an Event Condition Set. Indidition, one Condition may be associated with a "Minor Cycle Event". Theseare Executive-qenerated Events which are set "on" at certain specified timesand are otherwise inaccessible to the Application Software. If a Conditionis associated with a Minor Cycle Event, it may not be associated with any

,er Event.

A ondition may be either Latched or Unlatched. A Condition associated witha 4i. nr Cycle Event must be Unlatched. The sole difference between a Latcheda:.d an Unlatched Condition is that upon the Schedulinq or Activation of aTask, the Unlatched Conditions are set to the undesired value. Thus, a Taskcan only be Activated by an Unlatched Condition when the value of thatconoition is changed to the desired value subsequent to the last Scheduling:,;r Activation of the Task. By contrast, Latched Conditions are chanqed only

31

Page 43: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

La c

vi

C-~ul =1 0- -

Ln I-

LAi

L LAJ ci

Li'

-F-

ML C-iC-

I--

L'Li

Cl

Li~

32

Page 44: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

when one of their associated Events is changed. Therefore, a Task with onlyLatched Conditions in its Condition Set will be immediately Activated afterit is Scheduled if all the Conditions were satisfied before the ScheduleStatement.

A Task may return from Active to Inactive state from twc causes: eitherbecause it completes execution, or because it is forcibly Terminated byanother Task. In either case, immediately after it returns to Inactivestate, the Event Condition Set is evaluated, and if all the Conditionshave their desired values, the Task is immediately re-Activated.

When a Task is Activated, it is immediately put into Dispatchable state.If, at any point during its execution, a Task executes a Wait Statement,the Executive will place it into Wait state until the specified conditionis satisfied, upon which the Task will again become Dispatchable.

All Dispatchable Tasks should theoretically be executed immediately. However,since there may be more than one Dispatchable Task at any time within any

* one of the Processors, Tasks are ordered by Priority to resolve possibleconflicts. Whenever the Executive in any Processor is not called upon forimmediate action, it selects the highest Priority Dispatchable Task, and

* causes the Processor to execute it.

if i Task is Active but has not yet been executed, it is said to be Ready.If it has been in the process of execution, but has been interrupted by ahigher priority Task, it is said to be Suspended. If it is executing, it issaid to be Executing.

Any given Task may only be Scheduled by one Task, which is called its Controller.Two Tasks with a common Controller are said to be "siblings". The TasksScheduled by any Task are said to be its "sons". If a Task has no sons,it is said to have no "descendents:" otherwise, its descendents are itsso, and all the descendents of its sons.

Only a Task's Controller may Cancel or Terminate it; however, when a Task isCancelled or Terminated, all of its descendents are Cancelled or Terminated.If a Task attempts to Cancel or Terminate itself, it will Cancel or Terminateall of its descendents, but will leave its own state unchanged.3.1.1.2.3.1.2 Comsubs

In diddition to Tasks, the Applications Software may include another kind ofpr,,:essinq module, known as the "Comsub". A Comsub may be called fromrany Tasks; there is a copy of each Comsub in any processor containing aTac s' from which the Comsub may be called.

A Comsub communicates with a Task which calls it only through its parametersand/or function result. No Comsub may execute any Real-Time Pseudo-Statements;however, one Comsub may call another.

When a Task calls a Comsub, the Task is considered to be executing within thecode of the Comsub. Thus, it is possible for one Task to be suspended withinthe code of a Comsub at the same time that another Task is executing within

33

"N

Page 45: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

r " ..

the same Comsub. In other words, A Comsub must be re-entrant. To implementthis, every Task has a Comsub Local Storage Area assigned by PALEFAC forstorage of local data by the Comsubs which it calls. At any time, there isa Comsub Stack Pointer which points to the area available for storage tothe next called Comsub. This Comsub Stack Pointer is considered to be partof the process state of the Task, and is saved upon the occurrence of anInterrupt.

3.1.1.2. 3.1.3 Compool Blocks

All communication of data between Tasks or between Tasks and the externalenvironment (RT's) is done by means of "Compool Blocks".

Conceptually, a Compool Block is a Block existing outside of any T'sk. NoTask may directly access a Compool Block when a GLOBAL Copy is declared;instead, a Task references a "Local Copy" which has size and attributesidentical to the Compool Block. A Task may copy the Compool Block into itsLocal Copy by a READ Statement, or copy the Local Copy into the CompoolBlock by a WRITE or TRIGGER statement. From the point of view of theApplication Software, READs, WRITEs, and TRIGGERs occur instantaneously,so a Compool Bl.:k can never be read when it has been partially updated by

* •a WRITE. If a Global Copy has been declared, then the task in which the Compoolis declared Global Copy is allowed to access the Global Data Block directly,rather than using Executive Read and Write Requests into and out of localcopies of Global data blocks. The Executive Read and Write Requests willnot actually move the data if the requesting task has declared the GlobalData Block as a GLOBAL'COPY rather than as a LOCAL'COPY. The GLOBAL'COPYprovides for the same central control of table formats as the LOCAL'COPYdoes.

Compool Blocks are divided into three classes: Input, Output, and Intertask.Input Compool Blocks can only be accessed by Tasks in a READ statement. Theirvalues are determined by RT's. Output Compool Blocks can only be accessed byTasks in a WRITE or TRIGGER statement; their values are "received" only byRT's. Intertask Compool Blocks are used solely for communication betweentasks.

Since a Compool Block may be accessed in more than one processor and also,possibly, in an RT, Compool Blocks may exist in multiple copies. Anyprocessor in which a Compool Block is read has a Physical Copy of the Block;any RT which references the Block, or any processor which only WRITEs or TRIGGERsthe Compool Block, is considered to have a Virtual Copy of the Block. Tomaintain consistency between the various copies of a Compool Block, theExecutive must send Compool Update Messages across the Data Bus. Compool Blocksare further classified according to when these Update Messages are sent as:Synchronous, Asynchronous, and Critically Timed.

Synchronous Compool Blocks are updated from a single authoritative Copy,

whether in a processor or an RT, at a specified rate and phase. All copiesof an Asynchronous Compool Block are updated when any of those copies arechanged, either by the hardware of an RT or by a WRITE statement within a

processor. Critically Timed Compool Blocks are a special category used onlyfor Output. They may only be TRIGGERed within a Task. A TRIGGER statementincludes a "time to go". The Master Executive sends the Update to theappropriate RT at the specified time.

34

Page 46: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

The various categories of Compool Blocks are shown in Table 3.1-2, alongwith the ways which they may be referenced in a Task.

The first word of each Physical Copy of a Compool Block is a "Minor CycleTime Tag" which indicates the last time the Physical Copy was updated.

3.1.1.2.3.1.4 Events

Events are used for control communication between Tasks. An Event has twopossible values: on and off. A Task may READ the value of an Event, mayWAIT on an Event, and an Event may appear in the Event Condition Set of aTask.

There are two general classes of Events: Application Events and SystemEvents. Application Events are set on and off explicitly by Tasks. SystemEvents are set on and off by the Executive upon certain occurrences. Theinitial value of all events is off.

* System Events are further classified as:

o Task Activation Events,o Compool Update Events,o Minor Cycle Events.

Any Task may have an associated Task Activation Event. Such an Event is seton when the Task is Activated and set off when the Task returns to Inactiveor Uninvoked state. The Activation Event associated with a Task must havethe same name as the Task.

Any Compool Block may have an associated Compool Update Event. Such an Eventis set on when the Compool Block is updated, either by a Task or an RT.The Update Event associated with a Compool Block must have the same nameas the Compool Block.Minor Cycle Events are set on by the Executive according to specified rates

and phases. They may only be referenced in Event Condition Sets.

3.1.1.2.3.1.5 Time

The Application Software may interact with time in two ways: it mayreference absolute time, or it may specify that certain occurrences shouldhappen cyclically. Absolute time is measured in seconds from the initiali-zation of the system. Cyclic time is maintained in terms of Minor Cycles andMajor Frames.

A '4inor Cycle is the shortest period of time at which a cyclic occurrencemay be specified. A Major Frame is the longest period of time at which acyclic occurrence may be specified. There are a fixed number of MinorCycles to a Major Frame (currently 64), and each Major Frame has a fixedduration (currently one second). Every Minor Cycle is numbered in order ofits occurrence within a Major Frame, starting with zero.

35

Page 47: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

SYNCHRONOUS ASYNCHRONOUS CRITICALLY TIMED

INPUT May be READ in May be READ inin many Tasks one Task

OUTPUT May be written May be written May be triggered inin one Task. in many Tasks. in many Tasks.

INTERTASK May be written May be writtenin one Task, in many Tasks,read in many read in manyTasks. Tasks.

Table 3.1-2 Categories of Compool Blocks

* Cyclic occurrences are specified by period and phase. Period is theo number of Minor Cycles between successive occurrences; phase is the Minor

Cycle number of the first occurrence within any Major Frame. Clearly, 0phase period.

In practice, Minor Cycles will not always occur exactly when they theoreticallyshould, partly because of the inherent latency of a federated system; partlybecause the Data Bus may be overloaded in any given Minor Cycle. However,the Executive guarantees that these errors are not cumulative; it will alwaysgenerate the next Minor Cycle as close as possible to the theoretical time,regardless of when the previous Minor Cycle occurred.

With one exception, the Minor Cycle is the finest granularity of timeknowable with the system. Thus, when a Task reads the absolute time, itreceives the theoretical time of the last Minor Cycle. The sole exceptionto this rule is the Critically Timed Compool Block. When a Task TRIGGERssuch a Compool Block, the Executive will attempt to send the Update Messageto the RT at the precise time specified.

3.1.1.2.3.1.6 Real Time Pseudo-Declarations

Real Time Pseudo-Declarations are used to declare the real time entitiesreferred to within a Task. There are four kinds of Real Time Pseudo-Declarations:

o Task Declarations,o Event Declarations,o Compool Block Declarations,o Comsub Declarations.

Task Declarations are used to declare Tasks referred to in Real TimePseudo-Statements. They create a reference to the Task Table A entry forthe appropriate Task.

36

Page 48: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

Event Declarations are used to declare Events referred to in Real TimePseudo-Statements. They create a reference to the Event Table entry forthe appropriate Event. If the Event is a Compool Update or Task ActivationEvent, it must be declared as such in this Declaration.

Compool Block Declarations are used to declare any Compool Blocks referencedin READ, WRITE, or TRIGGER statements. They do two things:

o They create a reference to the Data Descriptor Block for theCompool Block,

o They access the Compool within which the Compool Block is declared,and from it create a declaration for the Local Copy of the CompoolBlock.

A Compool Block Declaration must indicate whether a Compool Block is read,written updated (both read and written) or triggered within the Task.

Comsub Declarations are used to declare Comsubs called within the Task. They

simply generate the appropriate REF PROC declaration.

3.1.1.2.3.1.7 Real Time Pseudo-Statements

The Applications Software requests the services of the Executive throughReal Time Pseudo-Statements. There are 8 kinds of Real Time Pseudo-Statements:

o Schedule Statementso Cancel Statementso Terminate Statementso Wait Statementso Signal Statementso Read Statementso Write Statementso Trigger Statementso EREADo INVOKEDo TIME

Real Time Pseudo-Statements compile as calls to Executive routines, passingthe appropriate information as parameters.

Schedule Statements

Schedule Statements are used by one Task to Schedule another Task. A Schedule)td:ement includes the following information:

o The name of the Scheduled Task,o The priority of the Scheduled Task,o The Latched Conditions (if any) in the Event. Condition Set of the

Task.o The Unlatched Conditions (if any) in the Event Condition Set of

the Task.o The period and phase of a Minor Cycle Event (if any) in the

Event Condition Set of the Task.

37

Page 49: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

The Latched and Unlatched parts of the Condition Sets are defined byevent expressions . The syntax for event expression is:

< event expression >: :=<condition>Kcondition > AND<event expression >

< condition>: :=<event set >INOT <event set>

< event set> ::=<eveni(<or set>)<or set>: :=<event><event> OR <or set>

Each condition in this expression corresponds to a Condition in the EventCondition Set. The presence of a NOT indicates that the desired value is off;the absence indicates that the desired value is on. The Events named inthe event set are the Events associated with th-e Condition. Note thatalthough multiple Events associated with a single condition are combinedwith ORs, the actual value of the Condition is not necessarily the OR ofthe value of the Events. Thus, for instance, the Condition denoted by (AOR B) will be set off if Event A is set off, regardless of the value ofEvent B.

Cancel Statements

The Cancel Statement is used by one Task to put another Task into Uninvokedstate. The Cancel Statement includes the name of the Task to be Cancelled.This Task must either be the Task within which the Statement is executed,of a son of that Task. If a son is cancelled, all the descendents of theson are also cancelled automatically. If a Task attempts to Cancel itself,it will not affect its own state, but will Cancel all of its descendents.If a Task specifies itself in a Cancel Statement, it must be declared in aTask Declaration within itself.

Terminate Statements

The Terminate Statement functions identically to the Cancel Statement,except that it de-Activates instead of de-Invoking Tasks. When the eventcondition set for the terminated task becomes true, the Task will becomedispatchable.

S!

Wait Statements

Wait Statements are used by Tasks to place themselves into Wait State pendingcertain occurrences. There are four kinds of Wait statements:

o Absolute Time Waits,o Relative Time Waits,o Latched Waits,o Unlatched Waits.

An Absolute Time Wait places the Task into Wait state until a specifiedabsolute time. IH the specified time has already occurred, this statement isa No-Op.A Relative Time Wait places the Task into Wait state for a specified period

of time. If the specified period is non-positive, this statement is a No-Op.

38

Page 50: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

A Latched Wait places the Task into Wait state until a specified Eventreaches a specified "desired value". If the Event already has the desiredjlue, this statement is a No-Op.

An Unlatched Wait places the Task into Wait state until the specified Event

is changed to the specified value. This statement is never a No-Op.

Signal Statement

A Signal Statement sets a specified Event to a specified value.

Read Statement

A Read Statement copies the value of a specified Compool Block into thecorresponding Local Copy. If the Compool Block is a Global Copy, then nodata transfer occurs.

Write Statement

A Write Statement copies the corresponding Local Copy into the specifiedCompool Block. If the Compool Block is a Global Copy, then no data transferoccurs.

Trigger Statement

A Trigger Statement requests the Executive to send the Local Copy of thespecified Compool Block to the appropriate RT in a specified time. The speci-fied time must be between two Minor Cycles and one Major Frame from thetime the Trigger Statement is executed.

EREAD

EREAD yields the value of the Event which has been passed as an argument.This Event must have been previously declared in an Event Declaration.

INVOKED

INVOKED is applied to a Task. This function yields the value TRUE if thetask is Invoked, FALSE if it is not.

rIME

TIME returns the absolute time as a 31 bit signed integer signifying theelapsed time since system initialization.

3.1..2.3.1.8 Master Executive Interfaces

Master Sequencer Interface

At the end of Master Initialization or Master Re-Initialization, the MasterExecutive schedules the Master Sequencer task. This task then schedulesthe other Applications Tasks.

39

FI

Page 51: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

Application ystea Error Interface

Applications Software can detect error conditions and communicate the con-ditions to the Subsystem Status Monitor. The primary source of errors will bethe Equips functions. These functions will determine any errant status withequipment and sensors and communicate the errors to the Subsystem StatusMonitor.

The Subsystem Status Monitor records the error and gathers error statistics.If the last error was within t(o short a time or there were too many sucherrors, the Subsystem Status Monitor invokes the Configurator. The Configura-tor will cancel errant functions if appropriate. If the errors are of sucha magnitude to warrant reconfiguration, the Configurator can invoke the Recon-figuration function via the 10 device function.

40

I

A

Io

p.. ..- . .. ... 4 0_ i

Page 52: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.1.2 Applications Software Architecture

3.1.2.1 Software Structure

The Applications Software is organized into:

o System Control Moduleso Operational Sequencers (OPSs)o Specialist Functions (SPECs)o Display Processes (DISPs)o Equipment Processes (EQUIPs)

as shown in Figure 3.1-12 , A brief functional description of each is qivenbelow.

System Control Modules

The four System Control Modules (Master Sequencer, Request Processor, Con-figurator, Subsystem Status Monitor) are responsible for initializinq andcontrolling the Applications Software.

The Master Sequencer, the first Application's Software task activated by theExecutive Software, performs data initialization and schedules tie otherSystem Control Modules. Its control interfaces are shown in Fiqure 3 . 1-13.

The Request Processor receives and interprets control panel input requests.It will activate appropriate software tasks to handle legal requests; illegalrequests are ignored. Request Processor control intertaces are shown inFigure 3.1-14.

The Configurator controls the operation of application tasks. It is activatedwhenever a new Operational Sequencer or Brute Force Specialist Function is tobe initiated, or when a severe equipment health problem is detected. Con-ficurator controi inter-faces are shown in Figure 3.1-15.

The Subsystem Status Monitor maintains status of the avionics subsystems.If a subsystem has failed or is generating degraded data, it determines thetype and severity of the problem, and activates the configurator if theseverity is significantly high. The Subsystem Status Monitor control interfaceis shown in Figure 3.1-16.

0 pe-ationa_ Sequencers

Operational Sequencers are responsible for the control of a particular missionph2se. They are activated by the Configurator as a result of master modeselections. and by the current Handler Specialist Function whenever a newdisplay page is requested. Operational Sequencer interface control isshown in Fiqure 3.1-17.

Specialist Functions

Specialist Functions carry out computational and control functions requiredby an OPS or by the crew. The four categories are Computational, Brute Force,Tailored Mode, and Handler.

41

Page 53: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

CdC,

LU 0

:)

UC)

LL.U:)

oc. - L Uo)

U)C)

LAJ

I-L

LJJ

LLLL

42

Page 54: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

LU~L LL =

zL z

LLJLI

0-L

LL

N.- u_ LLU- ae

LL LU i

-j 0

>L

-J I

LU LU~u IC/3 C/) I-LUL

Page 55: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

LAJ

(DLU cr

C)LL. 2=Li2

CL.

wz 0

< L)_jg U < -I

0 LLU

o -

LU -

C~ I'* ~AJC) L L

C) LU LU

V= z< < eC--LUJ

Q)~ =) V)I- :

LU Z zIA /CL;m V)L-

C/)ULWUi i

LLJ I- z i 44

Page 56: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

LU -UC/

I J L& -C - j C :) CO L J /

cU 9=_ -" t)

CU LA = (L) -L C L

QcjL)uj 0C LLJ a-0ui

UL) CL LL

w z w

< Ric .- I-

* - La - - - oL

Z3 U

LU LU

- zL

LL. O LL

ww

o -L

CLL

_ LUJ

-J LL. L~- C OU) U

-- L

Page 57: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

LUU

LU LU

go U-) < i

U L dt L-)

LLJ

LL) w

-CT V) LU n

CF, UV LUI r Cm

W/ C/))L

;P C z L LLU

LU -Lj LU G

1:~~ 0 m

C=*

UJ w<Z 0

CL< LU -C

jU <U

C)u

LO

C) LL.LLLU LU

=U LU c/a. L

cLJ LUL = = 0)

46

Page 58: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

LAU

co')

LUL)r

LL

P4J Ca Lw C.- LUJ- LL CL z~ m z-

-j L- J uj0 ')U. X 2

4c 19- M OW 00 C3 LLUC> u-J = cO'lC (A 0 l:< 91Z CI

acU a w < P- I- 4--4~~ ~ ~ j _(: M- z 0_ _

a_~ Li.

LLU

t0z

W L

Ar Li

CLU

A= LL

C)-

47

Page 59: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

Computational Specialist Functions carry out cyclic processing and areusually active throughout most of the mission (e.g., navigation). Computa-tional SPEC interface control is shown in Figure 3.1-18.

Brute Force Specialist Functions allow the pilot to initiate, sequence, andterminate mission operations that are not automatically available in thecurrent OPS (e.g., sensor moding). They are accessed via the top keys onthe IMK. Brute Force SPEC interface control is shown in Figure 3.1-19.

Tailored Mode Specialist Functions primarily perform those functions necessaryto process selections by the crew via control devices (IMK, MFDC, HCU, CCA).They are activated by the current Handler Specialist Function to process IMK/DEK inputs, and by the Configurator to process other control requests.Tailored Mode SPEC interface control is shown in Figure 3.1-20.

Handler Specialist Functions perform the control processinq involved withdisplay pages. There is a Handler SPEC for each device: IMK, lIPD. HandlerSPEC interface control is shown in Figure 3.1-21.

Display Processes

Display Processes control cockpit disolays. They obtain data generated byvarious Application Software tasks, perform required scaling/formatting, andoutput the resulting data messages to comoools for subsequent transmission todisplay hardware. Interface control for Display Processes is shown in Fiqure3.1-22.

yipment Processes

Equipment Processes represent the Applications Software interface with IDAMSTsensors.

Input Equipment Processes receive data generated by the sensors, performrequired selection scaling, etc., and output the resulting parameters to acompool for use by other Applications Software tasks. They also monitorequipment status and initiate action when failure or deqraded data isdetected.

Output Equipment Processes receive data qenerated by various ApolicationSoftware tasks, format corresponding sensor data/control messaqes, and outputthese messages to a compool for subsequent transfer to the sensor.

Interface control for Equipment Processes is shown in Fiqure 3.1-23.

48

Page 60: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

C) m

'-~~~i CD # ~z-C) Cl-

C/)~~I LL L

LLJ

LLU

CL,

LLU

C-

UI-

CD-

490

Page 61: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

- = -U

I-L

n - I-

LU <

LL- - CD to go

LU (j) a--I-- C-) C..) -

LWJ CD

go cn - I--u.

uj w

50-

Page 62: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

LAJQJ

OLUJLL 0 (n(

LLj LL

-L -L 0-LL

U LU W L

LUJ

C) L.>

LU

= LL-

C:) -c~

~C:-

WU Lu L

ILA-

LA-U

C/ LU -

05

Page 63: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

- CI, U3 L)

LU w .jaCL. f..j

L. CL

L7Uui -. )

LU LU

C/, LUIJ 4 -)i

C). iJ u

~ L I

1= _j C)LLJ n CL* L < =_ _ _ _ ( J -Cj

LLIJ LLDCL- Li

IL 0-

uw LA..

U-J

C4% C) LLU( LU O L

C)CLI.-~ V) C) j CD- cnV) V) :: 52

LL L0

Page 64: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

(D

zCL

0Iix

cc z z*L 0 0

LLU

LUJ

4n C/,

>- C/3 (/ C

0I- (UQ j-)LLJ~ u 2!

Oi . 0 0

CA- CCL

C'4

L)L

LCNJ

I-- C/C= 4U (= 0 4mC/

U~ UU i (. 3

U.J LULUL

_L a= L C-a. ~ ~ LJ LL LU.= nLL .

CL c L- 0-

53

Page 65: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

LJ C,, W f

Ka C, L* (-.) Cl- t,

W CZI CL. =C> C/) C:

>LUj

-

~z n9- 9 ui

C) -JOU

LU~ ~ 0L-

W -)

0 -5c

Page 66: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.1.2.2 Software Relationships

This section describes the control and data relationships of the varioussoftware components comprising the Application Software.

Figure 3.1.2-12 shows the primary control/data interfaces for the ApplicationsSoftware. Appearing below is a more detailed explanation of each controlinterface:

1. Cyclic activation via Executive initiated by the Configurator. Activa-tion of cyclic mode-dependent Computational Specialist Functions andDisplay Processes is initiated by the Configurator during transitionfrom one mission mode to another.

The Computational Specialist Functions access data residing in aCompool for their calculations, and store the results in another softwarecompool.

2. Cyclic activation initiated and cancelled by the Configurator. Activa-tion of cyclic Equipment Processes, Air Data Display Processes, andcertain Computational Specialist Functions is initiated by theConfigurator during transition from the INITIALIZE mode.

Each input Equipment Process will access data moved by the Executiveto a Compool, check the device status word, check for validity/reasonable-ness, generate substitute data (if necessary), convert/format the data,and store the result in an Applications Software Compool. If the devicestatus has changed or if the deice is generating incorrect/degraded data,the Subsystem Status Monitor is notified.

Each output Equipment Process will access data residing in an Applica-tions Software Compool, scale/format the data, and store the result ina Compool for subsequent output.

Each output Display Porcess will access data residing in an ApplicationsSoftware Compool, scale/format the data, and store the resulting para-meter in a Compool for subsequent output.

3. Cyclic activation by the Executive, initiated when the Request Processoris scheduled by the Master Sequencer.

The Request Processor will access control panel data residing in aCoipool, check the panel status word, decode/interpret any crew input,and store the result in an Applications Software Compool. It will thenactivate the Subsystem Status Monitor (if panel status has changed) orthe IMK Handler Specialist Function (if IMK side key input) or theConfigurator (other input).

55

Page 67: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

~8~~**~--------- - --

0 I -

I (Del;

rz

U-

56

Page 68: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

4. Synchronous activation by the Executive, initiated by the HandlerSpecialist Function; this cyclic activation is initiated when a side

key select is received which requires DEK input, and is terminated whenan Enter Key is recognized.

The DEK input Equipment Process will access data residing in a Compool,check device status word, and check data for Erter Key indication. Ifdevice status has changed, the Subsystem Status Monitor is notified.If an Enter Key is recognized, the input buffer is converted and storedin an Applications Software Compool and the Handler Specialist Functionis activated.

5. Demand activation by Tailored Mode Specialist Functions.

Each output Equipment Process will access data residing in an Applica-tions Software Compool, scale/format the data, and store the result ina Compool for subsequent output to the device.

6. Demand activation by Tailored Mode Specialist Functions.

Each output Display Process will access data resiging in an ApplicationsSoftware Compool, scale/format the data, and store the resultingparameter in a Compool for subsequent output.

7. Demand activation by DEK input Equipment Process indicating receipt ofan Enter Key.

The Handler Specialist Function will access data residing in an Appli-cations Software Compool pertaining to the IMK activity leading up tothe DEK input request, and activate the appropriate Tailored ModeSpecialist Function for action. A Display Process will be activatedto note on the IMK that required DEK input is complete.

8. Demand activation by the Request Processor indicating receipt of an IMKside key.

The Handler Specialist Function will access data residing in a Compool,and if the indicated side key requires DtK input, cyclic activation ofthe DEK input Equipment Process will be initiated (via request toExecutive Software), and a Display Process will be activated to noteon the IMK that input is required.

If the side key requires a new IMK CRT page to be displayed, thecurrent Brute Force Specialist Function, or if none, the currentOperational Sequence, is activated to accomplish this.

IMK key status/history and other status pertaining to the IMK HandlerSpecialist Function is stored in an Applications Software Compool.

57

Page 69: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

9. Demand activation by the Handler Specialist Function indicating thatprocessing of crew input selections (IMK side key and/or DEK input)is required.

The tailored Mode Specialist Function will access data residing in anApplications Software Compool (both input and status data), determinevalidity, perform processing, and store results in an ApplicationsSoftware Compool. The proper Equipment Process will be activ"-d tocomplete the data transfer to the device.

Further, if the data requires an update of a current display, a DisolayProcess is activated.

10. Demand activation by the Handler Specialist Functi.n requesting a newCRT page.

The Operational Sequencer or Brute Force Specialist Function will accessdata residing in an Applications Software Compool and display the newCRT page.

11. Demand activation by the Handler Specialist Function to display parametervalues or to indicate DEK activity.

The Display Process will access data residing in an Applications Soft-ware Compool, scale/format the data if necessary, and store the resultin an Executive Software Compool for subsequent output.

12. Demand activation by the Brute Force Specialist Function or OperationalSequencer to display the new display page.

The Display Process will access data residing in an Applications Soft-ware Compool, scale/format the data if necessary, and store the resultin an Executive Software Compool for subsequent output.

13. Demand activation by the Request Processor because of a control panelinput.

The Configurator will access the input data residing in an ApplicationsSoftware Compool and activate the appropriate Tailored Mode SpecialistFunction, Brute Force Specialist Function, or Operational Sequencer toperform the necessary processing.

14. Demand activation by the Configurator because of control panel input.

The Tailored Mode Specialist Function corresponding to the type of input(HCU, CCA, MFDC) will access data residing in an Applications SoftwareCompool, and perform the processing required to satisfy the request. ADisplay Process will be activated to control panel lamp configuration.

58

Page 70: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

The Operational Sequencer associated with the MMK selection will performthe necessary processing and control to establish the new mission mode.Display Processes will be activated to control new IMK/MPD pages, aswell as panel lamp configuration.

The Brute Force Specialist Function associated with the IMK top key willperform the necessary processing to satisfy the request. The requestmay be to cancel the current Brute Force Specialist Function, change toanother one, or establish a new one. Display Processes will be acti-vated to control CRT pages on the IMK(s) and to control the top keylamp configuration.

15. Demand activation by input Equipment Processes or by the RequestProcessor.

The Subsystem Status Monitor will access data residing in an ApplicationsSoftware Compool and store, if appropriate, in an Applications SoftwareCompool to maintain the equipment status. If current status indicatesa failure requiring a different software configuration, the configuratoris activated.

16, Demand activation by the Subsystem Status Monitor indicating an equip-ment health problem.

The Configurator will access data residing in an Applications SoftwareCompool and etermine requires action. The Executive Software will benotified if the equipment failure is severe. Software re-configurationbecause of less severe failures will be handled by the Configurator.

17. One-time-only activation by the Executive to start the ApplicationsSoftware.

The Master Sequencer will perform required initialization processing,and activate the Configurator to mode the Applications Software.

18. One-time-only activation by the Master Sequencer for Applications Soft-ware startup.

The Configurator will perform any required processing, and activate anOperational Processor to put the Application Software into anINITIALIZE mission mode.

19. Demand activation by the IMK Handler Specialist Function indicating theselection of a master mode from the MMK backup pages on the IMK.

Request Processor will process the input as it would MMK pushbuttoninput.

20. The Configurator will notify an Executive task for failures it cannothandle.

59

Page 71: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

T

21. Demand activation by an EQUIP which determines a situation requiring

a "WARN" act;on (e.g., CCA Shaker, Low Speed Warning Light, etc.).

22. Demand activation by the Executive when a device failure is detected.

23. Demand activation by Handler SPECs for IMK or MPD functions relatingto DEK input, MPD checklist activity, new display pages.

60

Page 72: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

This paqe intentionally left blank.

61

Page 73: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2 Detailed Functional Requirements

This section specifies the detailed functional requirements for the Applica-tions Software.

The software components identified to satisfy these requirements are shownin Figure 3.2-1.

3.2.1 System Control Modules

3.2.1.1 Master SequencerThe Master Sequencer performs data initialization, and initiates the schedul-ing and execution of the other System Control Modules.

3.2.1.1.1. Inputs

Input shall be TBD data required for initialization of the ApplicationsSoftware.

3.2.1.1.2 Processing

Upon activation by the Executive, the Master Sequencer shall

o initialize mission data and carry out other initialization tasksfor the particular software configuration

o schedule the request processor, configurator, and sub-systemstatus monitor tasks

o activate the configurator

3.2.1.1.3 Outputs

None.

3.2.1.2 Request Processor

The Request Processor receives and interprets control panel input requests.It is activated 8 times per second.

3.2.1.2.1 Inputs

Input shall consist of

o MMK Status, Pushbutton # (2 words)

o IMK Status, Top/Side Key # (2 words)o MFDC Pushbutton # (I word)o CCA Status, Pushbutton # (2 words)o HCU Status, Pushbutton # (2 words)o MMK Backup Mode Select (I word)

62

Page 74: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

%-n wc 1i

-jW -. 4A ca

ccW4 -C~ C.i U- Li.&L - uZ. LO iQ:C 34 - - -cc cc

t 4. u.. a Z.:2 : : r - '3 0 -

eI-C6L

V) CC I., --I0mC-a :X A

n L i x X i X: X: j

7: LE ca w jmV -- cc

2:U..D j (Il

4n cc -#-- "j

C), LJ<L):Li I Ne ... Jvi () !5 M Is

cc0rd * C) 0L. -13 .W v)-0fJL-fr71JF ,-

Li L.i - A j .

W: 2:L M - : L

A :RMX -C -xCL

2: I

"J L.a

C> 6- --aQ

41 ftt IA e C- -cc V) I. 2: ix 9.J LM

W ti g~. u L Ln -v1 L>UC3-CL=3 1 en V' , L 2

CF L3 I

C J kaJ ..J CIA, A- C

ctu 1- 0 A-L0C LI F

ri.. W Vl W _j:Cc U

63

Page 75: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.1.2.2 Processing

The Request Processor shall access the input panel data to determine if anydata has changed. It no change has occurred since the last activation, theRequest Processor shall terminate.

If the input data from an IMK shows a side key select, the IMK Handler Spe-cialist Function shall be activated; the Configurator shall be activated forIMK top key selections.

Valid pushbutton input from other source devices shall also cause the Config-urator to be activated. The following pushbutton input shall be ignored:

o non-supported pushbuttons (spares)o MMK input which would result in an out-of-sequence Master Mode situa-

tion (TBD)o MMK input identical to current MMK setting (i.e., repeated selection

of same pushbutton)

The Request Processor is activated by the IMK Handler Specialist Functionwhenever the Master Mode backup capability is used. The processing shall bethe same as the MMK input.

The Request Processor shall activate the Subsystem Status Monitor wheneverthe panel mode/health status changes.

3.2.1.2.3 Outputs

None.

3.2.1.3 Configurator

The Configurator controls the moding/operation of the application tasks.

3.2.1.3.1 Inputs

Input shall consist of:

o control panel input-pushbutton numbers (4 words)o equipment failure message (2 words)

3.2.1.3.2 Processing

Upon activation by the Master Sequencer, the Configurator shall schedule andactivate the INITIALIZE Operational Sequencer.

I664

Page 76: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

When activated by the Request Processor because of MMiK select, the

Configurator shall

o cancel the current Operational Sequencer0 set up the task configuration necessary for the new modeo activate the new Operational Sequencer

When activated by the Request Processor because of an HCU, CCA, or MFDCrequest, the CONFIG shall activate the appropriate Tailored Mode SpecialistFunction.

When activated by the Request Processor because of an IMK top key select,the CONFIG shall determine whether the new key select is identical tothe previous one. If the new key select is different, the Configuratorshall

o cancel the current Brute Force Specialist Functiono set up the necessary task configurationo activate the new Brute Force Specialist Function

If the key select is the same as the previous one (i.e., the IMK top keyselected by the crew was backlighted green), the Configurator shall

o cancel the corresponding Brute Force Specialist Functiono set up the task configuration necessary for full resumption

of the Operational Sequencer corresponding to the currentMaster Mode

o activate the Operational Sequencer to initialize IMK CRT displays

When the Configurator is notified by the Sub-System Status Monitor of anequipment health problem, the Configurator shallinform the crew via MPDand either 1) re-configure to a backup or perhaps degraded mode forsevere failures or 2) request the crew to take action. The Configuratorshall signal the Master Executive for failures that it cannot properlyhandle.

3.2.1.3.3 Outputs

Output shall consist of

o Equipment failure message ID (I word), MPDo Equipment failure notification (I word), EXEC

3.2.1.4 Subsystem Status Monitor

The Subsystem Status Monitor maintains status of the avionics subsystems,and monitors changes in status.

3 2.1.4.1 Inputs

Input shall consist of

65

: .. . .

Page 77: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

o Control panel status (4 words)o Device/sensor status (I word)

3.2.1.4.2 Processing

The Subsystem Status Monitor is activated by the Request Processor upon acontrol panel failure or status change, or by an Equipment Process whenevera sensor has failed or is producing invalid/degraded data.

The Subsystem Status Monitor shall store the status. to maintain errorhistory and statistics. If an analysis of the data indicates a criticalerror, the Configurator shall be activated to perform error recovery.

3.2.1.4.3 Outputs

Output shall be a one word message to the Configurator indicating the changein status of the subsystem.

* o Status change message (n words)

3.2.2 Operational Sequencers

An Operational Sequencer (OPS) is a task responsible for the control of aparticular mission phase, as determined by "Master Mode". It is scheduled,activated, and cancelled by the Configurator, as a result of crew MasterMode selections.

Operational Sequencers have been identified for the following IDAMST missionmodes.

o Initialize o Go-Aroundo Start o Air Refuelo Takeoff o TF/TAo Enroute o Lando Air Drop o Shutdowno Lapes o Ground Test

3.2.2.1 Inputs

Input shall consist of

o Next Display ID (1 word)

3.2.2.2 Processing

OPS control processing begins when the pilot selects a mission mode by depress-ing an MMK pushbotton or by depressing an MMK pushbotton or by depressing anIMK side key associated with the master mode backup display page. Processingcontinues until another master mode is selected or until the OPS isinterrupted (suspended) by selecting a Brute Force Spec.

66

Page 78: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

Initial processing common to all Operational Sequencers upon activation bythe Configurator because of MMK input shall be

o Commanding MMK light configuration to correspond to the MasterMode selection

o Commanding IMK top key light configuration to OFFo Initiating tasks to generate those HUD, HSD, MPD displays defined

for the master modeo Setting a DISP flag to change Master Mode in the MPDGo Cancelling the IMK Status DISP if activeo Displaying a control page on each IMK CRT (this page contains the

top level control capability available for the Master Mode)o Activating the IMK Status DISP if necessary

Further, OPS processing depends on subsequent IMK side-key activation. TheOPSshalldisplay other (lower level) control pages as directed by thecrew via side key selection.

When the OPS is notified by the IMK Handler to put up another display page(because of an "advance page" indicaLor or side key #), the OPS shall

o Cancel the IMK Status DISP if necessaryo Display the requested page by activating the IMK Fixed Test DISPo Activate the IMK Status DISP if necessary

When a Brute Force Specialist Function is cancelled, the OPS is activated bythe Configurator and shall

:; Cancel the IMK Status DISP if activeo Display the top-level control page on the IMK CRTo Activate the IMK Status DISP if necessaryo Set IMK top key lamps OFF

3.2.2.3 Outputs

Output shall consist of

o MMK lamp on/off message (I word)o IMK lamp off message (1 word)

3.2.3 Specialist Functions

3.?.3.1 Brute Force Specialist Functions

Brute Force Specialist Functions allow the crew to perform certain missionoperdtions not automatically available to the Current OPS processing. Thesefunction,, are scheduled, activated, and cancelled by the Configurator as aresult of IMK top key selection by the crew.

67

Page 79: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

imBrute Force Specialist Functions have been identified for the followingIDAMST functions:

o Navigation o Libraryo Communications o Checklisto Sensors o Payloado Systems o DITS

3.2.3.1.1 Inputs

Input to any Brute Force Specialist Function shall consist of

o Next display ID (I word)

3.2.3.1.2 Processing

Brute Force Specialist Function processing begins after being activated bythe Configurator as a result of an IMK top key selection. Processingcontinues until there ;s another top key selection or until there is a

* Master Mode change. Initial processing common to all Brute ForceSpecialist Functions upon activation by the Configurator shall consist of

o Commanding IMK top key lamp configurationo Cancelling the IMK Status DISP if activeo Initiating tasks to generate any HUD, HSD, MPD displays defined for

the particular Brute Force SPECo Displaying a control page on the requesting IMK CRT and activating

the IMK Status DISP if necessary; this page contains the top levelcapability available for the function (i.e., Communication).

Further, Brute Force SPEC processing depends on subsequent IMK side-keyactivation. The Brute Force SPECshall display other (loqer level) controlpages as directed by the crew via side key selection.

When the Brute Force SPEC is notified by the IMK Handler to put up anotherdisplay page (because of an "Advance Page" indicator or side key #), it shall

o Cancel the TMK Status DISP if activeo Display the required page on the IMK CRTo Activate the IMK Status DISP if necessary

3.2.3.1.3 Outputs

Output shall consist of

o IMK lamp control (I word)

68

Page 80: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.3.2 Computational Specialist Functions

Computational Specialist Functions carry out cyclic processing, and are eitheractive throughout the mission (e.g., navigation) or throughout a particularmission mode (e.g., CARP).

Computational Specialist Functions have been identified for the followingIDAMST functions:

o navigationo steeringo wind calculationo weights and balances

3.2.3.2.1 Navigation Computational Specialist Function

1he Navigation SPEC is responsible for keeping track of the aircraft state,using input data from various sensor sources and from the crew. It is acti-

* vated by the Configurator upon a Master Mode selection by the crew.

The Applications Software navigation function consists of the following sub-* functions:

o controlo navigation modes:

- auto- INS- OMEGA

o manual update (position)o flight directoro OMEGAo magnetic headingo CARPo rendezvouso go-around

3 2.3.2.1.1 Control Subfunction

This subfunction provides overall control of aircraft navigation computation.:t is activated four times a second throughout most of tne flight.

,.....l.l.l Inputs

Input shall consist of

n status (n words)o device moding (n words)o master mode (0 word)o navigation mode (1 word)

3.2.3.2.1.1.2 Processing

This subfunction shall control the navigation computation procedure by de-

69

Page 81: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

termining from Master Mode, device status, device moding, etc., the appropri-

ate operational sequence.

3.2.3.2.1.1.3 Outputs

None.

3.2.3.2.1.2 Auto Mode

The Auto Mode subfunction provides for automatic (computer controlled) inte-grated navigation. The following functions are included:

o Flight planningo subsystem managemento optimum position calculation/updateo horizontal, vertical guidance calculationo performance monitoringo map display parameter updateo augmented ILS

3.2.3.2.1.2.1 Inputs

Inputs for the various Auto mode subfunctions shall consist of

o navigation subsystem data, as applicable (n words)

LF ADF - bearingUHF ADF - bearingVOR/ILS - bearing, loc/GS deviationRadar Alt - altitudeOMEGA - position, velocityCompass - headingTACAN - bearing, distanceINS - position, velocity, attitudeSKE/ZM - range, bearingFlight Controls - pitch, roll, turn rate, altitude, airspeed,TAS, altitude rate, vertical speed

o IMK input data (n words)Initialization dataFlight plan modificationsSubsystem controlPosition update

o HCU position update (n words)o Marker beacon data (n words)o Device status/moding (n words)

3.2.3.2.1.2.2 Processing

Auto navigation processing shall include the following capability:

70

Page 82: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

Flight Planning

o organize/store appropriate Standard Instrument Departure (SID) andflight plan

o execute/modify the flight plan as directed

Subsystem Management'

o perform initializationo tune radios from flight plan datao verify subsystem performance

Optimum Position Calculation/Update

o combine various NAVAID data to derive optimum positiono auto updateo update optimum position with manual input data

Horizontal, Vertical Guidance Calculation

o compare present position with flight plan to derive guidance informa-tion

Performance Monitoring

o establish and monitor subsystem performance criteriao estimate navigation accuracy and compare with mission requirements

MapDsay Parameter Update

o update present position and map display requirements

Augmented ILS (Land Mode)

o synthesize and smooth ILS datao computationally construct approach NAVAID

),2.3.2.1.2.3 Outputs

Output shall consist of

o flight instrument display parameters

3.2.3.2.1.3 INS Mode

This sjbfunction provides navigation capability using only input from INS.Updctes can be performed manually.

It 's ictivated by the Control subfunction four times per second whenever theINS mode has been selected.

71

Page 83: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.3.2.1.3.1 Inputs

Input shall consist of

o INS data - position, velocity, acceleration (n words)o flight plan information (n words)o radar updates (n words)o visual updates (n words)

3.2.3.2.1.3.2 Processing

Subfunction processing shall provide capability to

o maintain INS positiono execute/maintain flight plan and calculate INS guidance outputso INS manual update, including reasonableness tests

3.2.3.2.1.3.3 Outputs

Output shall be inertial position and velocity from which INS guidancesignals are derived and are available for display:

o position and velocity (n words)o guidance parameters (n words)

3.2.3.2.1.4 OMEGA Mode

This subfunction provides navigation capability using only input from OMEGA.

It is activated four times per second by the Control subfunction whenever theOMEGA mode has been selected.

3.2.3.2.1.4.1 Inputs

Input shall consist of

o OMEGA position, velocity (n words)o TAS (1 word,o heading (I word)o fliqht plan information (n words)

3.2.3.2.1.4.2 Processing

Subfunction processing shall provide capability to

o maintain OMEGA psoitiono execute/maintain flight plan and calculate OMEGA guidance outputso perform OMEGA smoothing with TAS and heading

3.2.3.2.1.4.3 OutpuLS

Output shall be OMEGA position and velocity from which OMEGA guidance

72

....i i.

Page 84: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

signals are derived and are available for display:

o position, velocity (n words)o guidance parameters (n words)

3.2.3.2.1.5 Manual Position Update

This subfunction generates update information from HCU, SKE/ZM, or IMK inputs.

It is activated by the Control subfunction whenever an update is requested.

3.2.3.2.1.5.1 Inputs

Input shall consist of present position

o latitude, longitude (2 words)

3.2.3.2.1.5.2 Processing

This subfunction shall update position with the input data.

3.2.3.2.1.5.3 Outputs

None.

3.?.3.2.1.6 Flight Director

T<is subfunction generates flight director commands compatible with HUD toprovide guidance to maintain designated flight path.

It is activated by the Control subfunction four times a second throughout themission if the flight director is functionally switc-r-I on."

3.2.2.2.1.6.1 Inputs

Input shall consist of navigation subsystem data

o navigation data (n words)

".?.3.2.1.6.2 Processing

This ;ubfunction shall calculate flight director commands compatiblewiti The HUD.

j.2.j.2.l.6.3 Outputs

Otput shall consist of

J pitch command (I word)o roll command (I word)o sFeed command (I word)

73

Page 85: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.3.2.1.7 OMEGA

The OMEGA subfunction converts OMEGA RF input data to airplane position andvelocity parameters. It is activated eight times per second by the Controlsubfunction if the data is used in the navigation calculations, as determinedby current navigation moding.

3.2.3.2.1.7.1 Inputs

Input shall consist of

o three channels RF (n words)o navigation mode (I word)

3.2.3.2.1.7.2 Processing

This subfunction shall convert the input RF input data to OMEGA position and

velocity.

3.2.3.2.1.7.3 Outputs

output shall consist of

o position, velocity (n words)

3.2.3.2.1.8 Magnetic Heading

This subfunction calculates magnetic heading.

It is activated four times per second throughout the flight by the Controlsubfunction.

3.2.3.2.1.8.1 Inputs

Input shall consist of

o present position (n words)o stabilized heading (1 word)o stored magnetic variation (n words)

3.2.3.2.1.8.2 Processing

This subfunction shall compute magnetic heading for use in referencingradio navigation aids and displays.

3.2.3.2.1.8.3 Outputs

Output shall consist of

o magnetic heading (I word)

74

Page 86: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.3.2.1.9 CARP

The CARP subfunction calculates the air release point for delivering cargo toa ground target.

It is activated four times per second whenever the AIR DROP Master Mode hasbeen selected.

3.2.3.2.1.9.1 Inputs

Input shall consist of

o ground target-latitude, longitude, altitude (3 words)o cargo type (n words)o cargo weight (n words)o wind (2 words)o relative fix-range, bearing (2 words)o aircraft parameters (n words)

3.2.3.2.1.9.2 Processing

CARP shall perform ballistic calculations to derive guidance and dis-play parameters pertaining to a specified airplane-cargo-target situition.

Additionally, CARP shall perform CCIP calculations for display purposesas an aid to pilot when selecting drop point.

J.2.3.2.1.9.3 Outputs

Output shall consist of

o guidance data (n words)o display parameters (n words)

3.2.3.2.1.10 Rendezvous

The Rendezvous subfunction computes guidance and steering parameters to enablerendezvous with other aircraft.

It is activated four times per second whenever the AIR REFUEL Master Mode isin effect.

3.2.3.2.1.10.1 Inputs

Input shall consist of

o LR radar cursor position - range, bearing (2 words)o UHF ADF - beari g (I word)o TACAN - range, bearing (2 words)o IMK - heading, position, air speed, etc. (n words)

75

Page 87: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.3.2.1.10.2 Processing

This subfunction shall determine the availability/applicability of navigationdata sources. For limited data, it shall perform necessary processing toobtain display information for manual steering.

When sufficient data is available, the subfunction shall:

o calculate target position and associated display parameterso perform guidance calculation for intercepts and output flight control

system and flight director steering data

3.2.3.2.1.10.3 Outputs

Output shall consist of target data and steering commands:

o target (n words)o steering (n words)

3.2.3.2.1.11 Go-Around

The Go-Around subfunction provides information which enables the pilot to per-, form a go-around during a missed approach. The missed approach parameters

are pre-selected prior to the approach.

This subfunction is activated whenever the GO-AROUND Master Mode is in effect.

3.2.3.2.1.11.1 Inputs

Input shall consist of the missed approach parameters:

o heading set (I word)o altitude set (I word)o course set (I word)o minimum climb gradient (1 word)o course-to-fix (I word)

3.2.3.2.1.11.2 Processing

Processing shall consist of incorporating the pre-selected, missed approachparameters into the navigation-guidance calculations. Parameters subsequentlycomputed for display shall reflect this change in mode.

3.2.3.2.1.11.3 Outputs

Output shall consist of the selected parameter(s) being stored in a Compool:

o parameters (n words)

3.2.3.2.2 Steering Computational Specialist Function

The Steering function provides guidance signals to the flight control system.It is activated 16 times per second throughout the flight.

76

Page 88: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.3.2.2.1 Inputs

Input shall consist of pertinent navigation data

o navigation data (n words)

3.2.3.2.2.2 Processing

The processing consists of calculating steering signals compatible with theflight control system.

3.2.3.2.2.3 Outputs

Output shall consist of

o pitch steer (1 word)o roll steer (1 word)o speed command (1 word)

3.2.3.2.3 Wind Computational Specialist Function

*The Wind Computational SPEC calculates wind velocities, used in air dropalgorithms and various displays. It is activated eight times per secondthroughout most of the flight.

3.2.3.2.3.1 Inputs

InpuL; shall consist of

o true airspeed (1 word)o aircraft velocity components (2 words)o heading (1 word)

3.2.3.2.3.2 Processing

The Wind SPEC shall calculate North and East wind velocity components.

3.2.3.2.3.3 Outputs

Output shall consist of

o North wind velocity component (1 word)o West wind velocity component (1 word)

3.2.'.2.4 Weights and Balances Computational Specialist Function

This SPEC calculates weight and balance information for display purposes. Itis activated four times per second throughout the flight.

77

Page 89: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

13.2.3.2.4.1 Inputs

Input shall consist of

o aircraft weight (n words)o cargo data (n wcrds)o fuel (n words)o etc.

3.2.3.2.4.2 Processing

Current aircraft weight and center of gravity shall be calculated based on fuel,fuel distribution, cargo data, etc.

3.2.3.2.4.3 Outputs

Output shall consist of

o airplane weight (I word)o center of gravity (I word)

I78

Page 90: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.3.3 Tailored Mode Specialist Functions

Tailored Mode Specialist Functions perform those functions necessary to pro-cess crew control requests via IMK (primarily), MFDC, CCA, and HCU. They areactivated by the current Handler Specialist Function to process IMK/DEK inputand by the Configurator to process other control requests.

The following paragraphs describe identified IMK, MFDC, CCA, and HCU relatedTailored Mode SPECS. Complete definition of LIBRARY, CHECKLIST, PAYLOAD,and DITS IMK control functions will result in the identification of addi-tional Tailored Mode SPECS.

3.2.3.3.1 IMK Tailored Mode Specialist Functions

IMK Tailored Mode SPECS are activated by the current Handler SPEC followingthe receipt of input (either DEK or IMK side key) requiring processing.

IMK Tailored Mode Specialist Functions have been identified for the followingIDAMST functions:

o INS controlo OMEGA controlo ILS controlo radar altimeter controlo TACAN controlo ADF controlo navigation data entryo navigation data displayo manual navigation modingo flight director controlo avionics on/off controlo CCA controlo UHF-AM controlo VHF-AM controlo VHF-FM controlo HF/SSB controlo LR radar controlo compass controlo SKE controlo counter measures controlo status monitor and controlo airdrop data entryo MFDC controlo HCU control

The UHF-AM Tailored Mode SPEC, considered representative of the processingperformed by IMK Tailored Mode SPECS, is described below. This SPEC processesrequests for UHF-AM control, input via IMK. An example of the IMK softwarefunction using this SPEC is shown in Figure 3.2-2.

79

Page 91: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

8/ecPUSHBUTTON CONFIG, IMK STATUS COMPOOL

RE /JsTc EIEhE (FO AP.)-S PE

I(STATUN

J _ CARGE - SS M * MAK SA U

CURET/RY OU ID KY

a E INRUTBFE

DEK ~ ~ ~ ~ ~ 1ffA CONTCT-ROL ,r IE E UF DSLY OTOT.MODE ERRO FLAG HNDE

IVAIO SPEC

(ENER EQIP CONLDAT

MAR MAARNSDISP (TO PDG) )

CURRN ENT/PEU BUFFEREY

-EQUIP UPDAT D INPUT BUFFER _____

FIGUR 3.2- IMKUHF-AM OTAEFNTO

(ENTR EQIP CMMAN

Page 92: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.3.3.1.1 Inputs

Input shall consist of IMK side key history and, if applicable, a DEK inputbuffer:

o present and previous IMK side keys (2 words)o DEK input buffer (n words)

Additionally, certain Tailored Mode SPECS shall need status data and/or otherdata for its processing. The UHF-AM Tailored Mode SPEC, for example, shallrequire a channel versus frequency table for certain processing.

3.2.3.3.1.2 Processing

The last side key selected shall determine the type oF processing required.For the UHF-AM Tailored Mode SPEC, the side keys represent the following con-trol:

1. off2. T/R3. T/R+G4. ADF5. Guard Xmit6. channel select7. frequency select8. channel preset9. squelch disable

10. volume

The previous side key shall determine the particular radio to be referenced.For the UHF-AM Tailored Mode SPEC, they represent:

1. UHF-AM #16. UHF-AM #2

Processing for side key numbers 1, 2, 3, 5, 9 shall consist of activating theUHF-AM EQUIP to send the proper control message.

Side key number 4 (ADF) select shall cause the status of the normal ADF capa-bility to be checked. If normal ADF is operational, the control request shallbe rejected. Otherwise, the UHF-AM EQUIP shall be activated to send the ADFwode control message.

Side key numbers 6, 7, 8, 10 have associated DEK input. The DEK input buffershall be decoded with respect to the specific side key and checked. If in-valid (e.g., out-of-range) the control request shall be rejected. If valid,processing shall consist of:

o Side key 6 (channel select) - The frequency corresponding to the

selected channel is obtained from a frequency versus channel tableresiding in a Compool. The UHF-AM EQUIP is then requested to sendthis frequency to the radio.

81

Page 93: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

o Side key 7 (frequency select) - The UHF-AM EQUIP is requested to sendthe input frequency to the radio.

o Side key 8 (channel preset) - DEK input for this side key consists ofchannel number and frequency. The Tailored Mode SPEC replaces thefrequency value currently tabled versus channel number with the inputfrequency. Side key 8 results only in a Compool update; the UHF-AMEQUIP is not referenced.

o Side key 10 (volume) - The UHF-AM EQUIP is activated to send the inputvolume to the radio.

Upon receipt of valid input, the IMK symbol (displayed to indicate that DEKinput was necessary) shall be removed by activating the DEK Mark DISP.

3.2.3.3.1.3 Outputs

Output shall be the desired control message to the EQUIP and/or Compool up-dates:

o EQUIP control kI word)

o update data (n words)

3.2.3.3.2 MFDC Tailored Mode Specialist Function

The MFDC Tailored Mode SPEC provides the logic necessary to control MFDCpushbutton input. It is activated by the configurator when an MPD/HSD push-button is pressed. Pigure 3.2-3 shows overall MFDC software function.

3.2.3.3.2.7 Inputs

Input shall consist of:

o pushbutton status, each device (5 words)o current pushbutton select (1 word)

3.2.3.3.2.2 Processing

The MFDC Tailored Mode SPEC shall determine whether the input is legal and,if so, implement the desired display control.

The DSMU EQUIP shall be activated if display switching is requested (e.g.,switching HSD #1 display to the MPD #1 device).

The HSD DISP shall be activated if display revision is requested (e.g., HSDscaling).

The MDSC EQUIP shall be activated if a video display is requested (e.g.,radar).

The LIGHTS DISP shall be activated to command the lamp configuration corres-ponding to the pushbutton status (as updated with new one).

If the pushbutton request is illegal (TBD) or if it cannot be satisfied

82

Page 94: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

(PUSHBUTTON 1 CHANGE) SSSMCHANGE)

LIGHTS CURRENT LIGHT ON/OFF CONFIG

OISP LIGHT ON/OFF CONFIG

ERROR!* WARN

I ois~~~ ILLEGALINUMS

IIS LT MDSCUTMS

833

Page 95: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

(e.g., radar turned off), an appropriate message shall be output to MPD #3.

3.2.3.3.2.3 Outputs

Output shall be the following control messages to be acted on by an EQUIP:

o display switching (1 word)

o display scaling (I word)

o radar/SKE/ECM display request (I word)

o MPD messages ID (I word)

3.2.3.3.3 ('CA Tailored Mode Specialist Function

The CCA Tailored Mode SPEC provides control logic to handle CCA pushbuttoninput. It is activated by the configurator whenever the CCA pushbutton ispressed. Figure 3.2-4 shows the overall CCA (pushbutton) software function.

3.2.3.3.3.1 Inputs

Input shall consist of

o pushbutton identification (I word)

o current button status (0 word)

3.2.3.3.3.2 Processing

The CCA Tailored Mode SPEC shall activate theICS EQUIP to implement the desired control:

o if hot-mic is "on," the EQUIP is requested to switch it "off"

o if hot-mic is "off," the EQUIP is requested to turn it "on"

3.2.3.3.3.3 Outputs

Output shall consist of

c hot-mic on/off control (1 word)

3.2.3.3.4 HCU Tailored Mode Specialist Function

The HCU Tailored Mode SPEC provides control logic to handle HCU display orradar antenna functions. It is activated by the configurator whenever con-trol is requested via the pushbutton selects. Figure 3.2-5 shows the over-all HCU software function.

84

Page 96: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

81 sec EQ 4 PUSHBUTTON, STATUS OPL

CSTANGE) sssm CCA STATUS

(PUSHBUTTON ICHANGE)

*CONF IGCURN-- ~ USHBUTTON STATUS

E C HOT-MIC ON/OFF _

EQUIP HOT-MIC COMM N.D(To ics)-

L FIGURE 3.2-4 CCA(PUSHBUTTON) SOFTWARE FUNCTION

85 N

Page 97: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

PUSHBUTTON, STATUS COMPOOL8/secR (FROM HCU)

PRO --CHNGAE--U SSSM HCU STATUS

(PUSHBUTTONI LIGHTS CURRENT LIGHT CONFIGCHANGE) DISP LIGHT ON/OFF CMD

(TO HCU)

CONFTG

HCU CURRENT PUSHBUTTONS

T-."OIDE rPREVIOUS PUSHBUTTONSREQUEST EXEC SPEC! NEW LIGHT CONFIG..-"-S/W TO "EIT'-ER

ACTIVATE OR IDEACTIVATE THEHCU EQUIP

RADAR DISPLACEMENTST .MODE

. SPEC RADAR CONTROL

(DISP ACEMENTCHA E) RADAR RAAR CONTROL

EQUIP COMMANDSI (-TO RADAR)

,,_CURSOR POSITION, ACT/DESIG P'USHBUTTON

16fsec HCUEQUIP DISPLACEMENTS

DISP CURSOR POSITION & OTHER

(e) PARAMETERS (TO IPDG7'

F1

FIGURE 3.2-5 HCU SOFTWARE FUNCTION

86

Page 98: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

" AA8G 113 BOEING AEROSPACE CO SEATTLE WA BOEING MILITARY AIRPL--CTC F/B 9/2

COMPUTER PROGRAM DEVELOPMENT SPECIFICATION FOR IDAMST OPERATION--ETC(U)NOV 76 F33615-76-C-1099

UNCLASSIFIED SPEC-SB-4042 AFAL-TR-76-208-ADO-2 NL

E IIIIEIIEEEEE-EIhIEEIhEIhE

I InnnnIInIInIIInIIIIIIInIn-IIIEEIIIIEI-EIIIEIIIEII

Page 99: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.3.3.4.1 Inputs

Input shall consist of

o pushbutton number (1 word)

o pushbutton status (1 word)

3.2.3.3.4.2 Processing

When activated by the configurator, this function shall determinewhether the pushbutton input represents a change in the current status fromoff-to-on. If so, it shall:

o request cyclic activation of the HCU EQUIP (if inactive)

o activate the LIGHTS DISP to command the proper light configuration

If the pushbutton input indicates a change in the current status from on-to-off, the HCU Tailored Mode SPEC shall

o request deactivation of the HCU EQUIP (if active)

o activate the LIGHTS DISP to turn off the light

3.2.3.3.4.3 Outputs

Output shall consist of

o light on/off configuration (I word)

3.2.3.4 Handler Specialist Functions

Handler Specialist Functions control processing for crew-IMK/DEK and crew-MPD/DEK interfaces. They provide the logic to control the display pagesassociated with the particular device.

There are always two Handler SPECS active: One for the IMK and one for theMPD (for checklist processing).

3.2.3.4.1 IMK Handler SPEC

The IMK Handler SPEC controls processing for all IMK display pages. It isscheduled by the configurator and activated by the request processor (forside key inputs) or by the DEK input EQUIP.

3.2.3.4.1.1 Inputs

Input shall consist of

o IMK side key number (I word)

o table of control information for the page (10 x 2 words)

87

Page 100: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.3.4.1.2 Processing

When activated by the request processor because of a side key, the IMK HandlerSpecialist Function shall determine from the display control informationwhether:

o DEK input is requiredo a Tailored Mode SPEC should be activatedo the current OPS or Brute-Force SPEC should be activated to change

displays

If DEK input is required for the specific side key number, the IMK Handlershall request cyclic activation of the DEK input EQUIP and displays a symbolon the IMK indicating that DEK input is required. If DEK input is not re-quired for the side key number (and a new display is not requested), the IMKHandler shall activate the appropriate Tailored Mode SPEC. If the side keynumber is a request for a new display page (advance to lower level, return

*to higher level), the current OPS or Brute-Force SPEC task shall be notified.(If the DEK EQUIP is active when a side key input is received, it shall be

* deactivated.)

When activated by the DEK EQUIP, the IMK Handler shall activate the appropriateTailored Mode SPEC to process the DEK input buffer, and then shall deactivatethe DEK EQUIP.

The IMK Handler SPEC shall activate the request processor when the M14K backupcapability is used.

3.2.3.4.1.3 Outputs

Output shall consist of:

o IMK/MPO message ID noting that DEK input is required (1 word)o DEK mark control message (I word)o Next display 10 (1 word)

3.2.3.4.2 MPD Handler SPEC

The MPD Handler SPEC controls processing for all MPD checklist display pages.It is scheduled by the configurator and activated by the DEK input EQUIP.

3.2.3.4.2.1 Inputs

Input shall consist of:

o DEK input buffer (n words)o table of control information for display page (n x 2 pages)

88

Page 101: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.3.4.2.2 Processing

When activated by the DEK input EQUIP, the MPD Handler SPEC shall determine

the required processing:

o item checkoffo skip itemo advance page

MPD Handler processing for item checkoff shall consist of displaying anext to the item checked ofT7-and then a "f---" opposite the next item in the

Skip items shall advance the "---" without checking off the item.

For advance page, the MPD Handler shall activate the MPD Checklist DISP todisplay the next checklist page.

3.2.3.4.2.3 Outputs

Output shall consist of:

o DEK mark control messageo next display ID (1 word)

89

Page 102: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.4 Display Processes

Display Processes (DISPS) control cockpit displays. When activated, theyobtain data/signals generated by the Application Software, perform requiredformatting, and output the resulting data messages to compools for subse-quent transmission to display hardware.

Ten Display Processes have been identified for IDAMST:

o LIGHTS - Controls lamp on/off for the MMK, HCU, MFDC, IMK, MarkerBeacon, Low Speed Warning, Ground Proximity Warning, EFCS Warning

o INSTRUMENTS - Controls dedicated cockpit instruments: Mach, AirSpeed, Vertical Velocity, Altimeter, Accelerometer

o HUD - Controls HUD for given Master Mode

o HSD - Controls HSD for given Master Mode

o MPD CHECKLIST - Controls MPD checklist display pages

o MPD PARAMETERS/STATUS - Controls processing for the various MPD func-tional display pages

o ERROR/WARNING MESSAGES - Controls the outputting of error and warningmessages to the crew

o IMK FIXED TEXT - Controls the display of IMK fixed text pages

o DEK MARK - Controls DEK check/mark processing pertaining to checklistand data input functions on MPD/IMK

o IMK STATUS - Controls status displays output to the IMK center par-tition

3.2.4.1 Lights Display Process

The Lights DISP commands lamp on/off configuration for: a) control panels,b) marker beacon, and c) warning lights. It is activated by the ApplicationSoftware task responsible for controlling the lamp status of the particulardisplay device.

3.2.4.1.1 Inputs

Input shall consist of

o device ID (1 word)

o desired configuration (1 word)

3.2.4.1.2 Processing

The Lights DISP shall format a message to command the desired on/

off configuration, and store the message in a compool to be sent to thedevice.

90

Page 103: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.4.1.3 Outputs

Output shall consist of

o lamp on/off command (1 word)

3.2.4.2 Instruments Display Process

The Instruments DISP updates the dedicated cockpit instruments:

o mach and air speed indicator

o vertical speed indicator

o baro altitude indicator

o g-meter

It is activated 16 times per second throughout the flight.

3.2.4.2.1 Inputs

Input shall consist 9f

o flight control system data (n words)

o minimum/maximum acceleration since reset (2 words)

3.2.4.2.2 Processing

The Instruments DISP shall obtain the input from a compool, calculatethe parameters, perform scaling as required, and output the result to acompool for subsequent transfer to the instruments.

3.2.4.2.3 Outputs

Output shall consist of

o mach number

o air speed

o vertical speed

o baro altitude

o acceleration (minimum, maximum, current)

3.2.4.3 HUD Display Process

The HUD DISP provides parameters to the MPDG for display on the HUD. It isactivated 16 times per second throughout the flight except for Shutdown Mode.

i91!

_i

Page 104: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.4.3.1 Inputs

Input shall consist of:

o parameter data (n words)o cursor position (2 words)

3.2.4.3.2 Processing

Upon activation, the HUD DISP shall calculate and/or scale those parametersrequired for all Master Modes. It then shall process those additional para-meters required for the current Master Mode (except those purged by a de-clutter request). The particular parameters calculated for each Mode shallbe as shown in Table 3.2-1.

3.2.4.3.3 Outputs

* Output shall consist of:

*o parameters corresponding to Master Mode (n words)

4 3.2.4.4 HSD Display Process

The HSD DISP provides parameters to the MPDG for display on the HSD. It isactivated 16 times per second throughout the flight except for Shutdown Mode.

3.2.4.4.1 Inputs

Input shall consist of:

o parameter data (n words)o cursor position (2 words) J

3.2.4.4.2 Processing

Upon activation, t1e HUD DISP shall determine if an HSI display is "assigned"to any MPD. If so, those parameters required by the MPDG to generate the HSIdisplay shall be calculated and/or scaled.

The HUD DISP shall then determine if a MAP display is "assigned" to any MPD.If so, those parameters required by the MPDG to generate the MAP display shallbe calculated and/or scaled.

The parameter/functions provided by the MPDG shall consist of:

HSI

distance to waypoirttime to goheading and heading annunciatorbearing pointers (2)bearing identifiers

92

Page 105: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

*~ ~X 0 0 @ 0*@ S : : --n S1 S 0 w w )v 0 5 I * x*

- -C, *

-Jd-t --

CA:

"* - -- Li -

030

"J. I (/L.Jr f

-,j 0i 7 *=93 e w

Page 106: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

HSI (Continued)

selected headingselected courseto-fromdeviationvertical deviation path pointervertical track change alertlateral track change alertoffset annunciatornav. mode annunciatorheading warnnavigation warn

MAP

, map scaleway pointsnavaids

* key elevationsprojected A/C position"killer" dataalternate trackairport/target location(cursor position)

3.2.4.4.3 Outputs

Output shall consist of

o HSI display parameters (n words)

o MAP display parameters (n words)

3.2.4.5 MPD Checklist Display Process

The MPD Checklist DISP displays requested checklists. It is activated by theMPD Handler Specialist Function whenever a checklist is to be displayed on anMPD.

3.2.4.5.1 Inputs

Input shall consist of

o device identification (1 word)

o checklist identification (I word)

3.2.4.5.2 Processing

The MPU checklist DISP shall format the MPDG message for displaying thespecified checklist on the specified MPD.

94

Page 107: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.4.5.3 Outputs

Output consists of a control message:

o MPDG control (1 word)

3.2.4.6 MPO Parameters/Status Display Process

The MPD Parameters/Status DISP controls the various MPD displays. It is acti-vated once per second.

Table 3.2-6 gives the Display numbers which can be displayed on each MPD(e.g., Display #3 can only be shown on MPD #3). Tables 3.2-2 and 3.2-3 showthe normal display configuration at the start of a given mission mode. Figure3.2-6 is an example of a combined nav/comm display page.

3.2.4.6.1 Inputs

* Input shall consist of:

o display requests (2 words)o display status (3 words)o parameter status (n words)

3.2.4.6.2 Processing

Displays are changed via IMK request; the IMK Handler SPEC processes andstores these requests. At each activation, the MPD Parameters/Status DISPshall check the requests and update the MPD display status (Display numberversus MPD number) table.

The DISP shall then obtain the current status for the parameters contained inthe up-to-three displays and store them in a Compool for later transfer to theMPDG.

3.2.4.6.3 Outputs

Output shall consist of a) an output buffer to the MPDG containing displayID and parameter status Tor each and b) updated display status:

o MPDG data buffer (n words)o display status (3 words)

3.2.4.7 Error/Warning Display Process

The Error/Warning DISP controls the outputting of MPD error and warning mess-ages. It is activated by the task which either detects the error or deter-mines the severity of the warning. The messages normally appear on thebottom two lines of the center MPD.

95

" '. . ... . . .... . , . .... . . . .. .. ..-. ..

Page 108: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

MPD #1 MPD #2

Display Pilot MPD #3 Copilot

Nav Status I

Comm Status I

System Status I

Engine Parameters I

Departure Area Data

Take Off Parameters

Cruise Parameters

Refuel Status /

Air Drop Flight Parameters J

Air Drop Area Data I

Approach Data I

Landing Area Data I

Weight and Balance Data I

Weight and Fuel Data I

Flare Inventory I

Low Speed Parameters

Aircraft Systems Readout I

Warning/Caution I

Flight Data I

LAPES Area Data I

Rendezvous Data I

SID /

STAR I

Delivery System Status

TABLE 3.2-2 NOMINAL DISPLAY VERSUS MPD ASSIGNMENT

96

Page 109: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

oc LeLL~ CdX

CL F- LAC) L L i

(-)LI LLl) II -A ICA IC -A I0l CA w C/) ) ) CI) 1/) 1/) ~)

<C CL CC- CC- CC CC CCC< t

'Ci ~ - XI-:o, 0I- X -E .2- > :> X CXLi A C) wCA CC C ) CC C/CI C "I'/ C

4 ~ ~ ~ ~ ~ ~ ~ C "0 - ~ ~ L-l-QI C)O

CC wC CA.LD = m. w. 0. I - 0.> - =. 0. = .w .W t =-m

=- Z j L L LU Z- L) LU LU LU LU LU LU LU LU<-

CC ~ ~ ~ / V. ) ~ ~ ~ ~ L)L

-o m .- 0- >- iL =3 - - -

Cd D w~ C-j C~ CD (D ( (D~ fL-)

Ic LU LU LU CC Oj LMC LuCC Lu LUJ wL aC

C3)

C1

F- im <s C5 V Cm) C LU C3C c C <C V)

-'- C- m - <- F-<\ E - C CC CCJ

*i Cl F- I-CCICCCC) <C< 0 . < >.L CDL I I (

< I- ce. CC ~ r14

V) (x L'C C3 CCV) C LI (=CC LO LU m czC cm re L06 -CC 1 - 0.JC .. L 2!t C. 2!:

< uj -J -J < J LU .< V

LU C

Ir IL Ch LU II _ I

Page 110: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

w% cc .. L. d

%D oC)l 00aCDQc

fn P*) .-4 U) -4

LA-JU--

Uvftb < CC C

IL- J LA - LA- H.3- m X Li- U. ,, U

0 U~. j

~ Ia.o

CLI98

Page 111: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.4.7.1 Inputs

Input shall consist of

o message number (1 word)

3.2.4.7.2 Processing

Using the input identifier, the Error/Warning DISP shall obtain themessage from a compool and add current status, if necessary.

3.2.4.7.3 Outputs

Output shall consist of

o error/warning message (n words)

3.2.4.8 IMK Fixed Text Display Process

The IMK Fixed Text DISP controls the display of fixed-formatted pages on theIMK. It is activated by an Operational Sequencer or Brute Force SpecialistFunction wherever a new IMK page is to be displayed. Figure 3.2-7 shows asample IMK Fixed-Text display.

3.2.4.8.1 Inputs

Input shall consist of

o page number (I word)

3.2.4.8.2 Processing

This function shall format a message containing the page ID, and store

it for transfer to the A/NSG. The actual "pages" are pre-stored in the A/NSG.

3.2.4.8.3 Outputs

Output shall consist of

o page number (1 word)

3.2.4.9 DEK Mark Display Process

The DEK Mark DISP provides the capability to add a symbol to a specified lineon the IMK or MPD indicating required action, and to delete the symbol whenthe action has been completed.

The symbol may be a "d" on the IMK to denote required DEK input, which isthen removed when valid DEK input is entered. The symbol may be a " V" ontne MPD to denote a checked off item or a "---" to denote the next item in acheckoff sequence.

99

Page 112: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

LUa

NJJ

I In

Uu-

Li.

100

Page 113: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

It is usually activated by the IMK or MPD Handler Specialist Function to con-trol the symbol display. It is sometimes activated by a Tailored Mode SPECwhich determines the successful completion of a data entry.

3.2.4.9.1 Inputs

Input shall consist of:

o device number (1 word)o action - insert, delete (1 word)o CRT row, column (1 word)

3.2.4.9.2 Processing

Given the device and requested action, the DEK Mark DISP shall store theappropriate message in a Compool to be sent to the A/NSG or MPDG.

3.2.4.9.3 Outputs

* Output shall consist of the A/NSG or MPDG message:

o control message (1 word)

3.2.4.10 IMK Status Display Process

The IMK Status DISP controls the display of status information in the centerpartition of the IMK. It is activated once per second to update parameterstatus if there is an active display. Figure 3.2-8 shows a sample IMK statusdisplay.

3.2.4.10.1 Inputs

Input shall consist of the status display ID:

o display number (1 word)

3.2.4.10.2 Processing

The IMK Status DISP shall access a table which identifies the parameters forthe display number. Current status for these parameters shall be obtainedfrom a Compool, formatted and stored in an output bdffer for transfer to theA/NSG.

3.2.4.10.3 Outputs

Output shall consist of the A/NSG buffer:

o parameter status (n words)

101

--

Page 114: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

cr w

ELLL.

LL..

102

Page 115: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.5 Equipment Processes

The Applications Software interfaces with IDAMST equipment via EquipmentProcesses (EQUIPS).

For each sensor providing data to the Application Software, the correspondinginput EQUIP will:

o monitor equipment status and initiate action when a health problem ordegraded data is detected

o perform the processing required to make the parameter(s) available

for use by Applications Software tasks

o generate substitute data values if necessary

* Those EQUIPS which output control data to equipment will:

o perform the processing required to format the appropriate control4message

The Equipment Processes identified for IDAMST are shown in Table 3.2-4.

3.2.5.1 UHF-AM Equipment Process

The two UHF-AM radios (AN/ARC-164) are used for military communications andas backup ADF receivers. They provide short-range, line-of-sight, two-waysimplex voice communication with ground systems and other aircraft, operatingin the 225-399.95 mHz frequency band. When the radio is in backup ADF mode,bearing is obtained via the ADF EQUIP.

The UHF EQUIP is activated by the UHF-AM Tailored Mode SPEC whenever a for-matted control message is to be sent to the radio.

3.2.5.1.1 Inputs

Input shall be a message containing radio ID and desired control:

o radio ID, control input (2 words)

Control capability consists of one of the following:

o frequency channel pre-set, alligning frequency tuning by channelselect

o manual frequency selection

o pre-set guard frequency selection

o operational mode selction (T/R, TR+G, ADF, OFF)

103

Page 116: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

TABLE 3.2-4 EQUIP SUMMARY

Equipment Activation Rate (per second)

DEK 8* (Input)TACAN 8 (Input)HCU 16* (Input)OMEGA 8 (Input)FCS 32 (Input)G-Meter 4 (Input)INS 4 (Input)SKE/ZM 4 (Input)LF/ADF 4 (Input)UHF/ADF 4 (Input)Radar ALT 4 (Input)ILS 4 (Input)Compass 4 (Input)Flight Surfaces 2 (Input)Aircraft Systems 2 (Input)Caut/Brakes/Gear 2 (Input)UHF-AM Demand (output)VHF-AM Demand (Output)VHF-FM Demand (Output)HB/SSB Demand (Output)DSMU Demand (Output)

Secure Voice Demand (Output)TACAN Demand (Output)OMEGA Demand (Output)CCA Demand (Output)FCS 16 (Output)Flares Demand (Output)INS Demand (Output)SKE/ZM Demand (Output)LF/ADF Demand (Output)UHF/ADF Demand (Output)Radar ALT Demand (Output)ILS Demand (Output)Compass Demand (Output)Radar Demand (Output)IRD&W Demand (Output)RHAWS Demand (Output)Avionics On/Off Demand (Output)ICS 8 (Input/Output)P.A. 8 (Input/Output)FDR TBD (Output)

* Continuous activation only when being used.

104

- *s.

Page 117: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

o squelch disable

o volume control

3.2.5.1.2 Processing

When activated by the UHF-AM Tailored Mode SPEC, the EQUIP shall determinethe type of control desired, format the required message, and store it ina compool for subsequent transfer to the radio. Input control data will havebeen checked by the activating task for invalid/out-of-range conditions, scEQUIP processing shall assume valid data.

3.2.5.1.3 Outputs

Output shall be control messages corresponding to the request, and statusupdates:

* o control command (I word)

o status update (I word)

3.2.5.2 VHF-AM Equipment Process

The VHF-AM radio (Wilcox-807A) is used for CCT and civilian communications.It provides two-way simplex 160 nautical mile voice communication in the 118 -

135.975 mHz frequency band over line-of-site propagation paths.

The VHF-AM EQUIP is activated by the VHF-AM Tailored Mode SPEC whenever a

formatted control message is to be sent to the radio.

3.2.5.2.1

Input shall be a message containing the desired control:

o control input (I word)

Control capability consists of one of the following:

o manual frequency selection

o squelch disable

o volume control

o on/off control

3.2.5.2.2 Processing

When activated by the VHF-AM Tailored Mode SPEC, the EQUIP shall determinethe type of control desired, format the required message, and store it ina compool for subsequent transfer to the radio. Input control data will havebeen checked by the activating task for invalid/out-of-range conditions, soEQUIP processing shall assume valid data.

105

Page 118: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.5.2.3 Outputs

Output shall be control messages corresponding to the request, and statusupdates:

o control command (1 word)

o status update (1 word)

3.2.5.3 VHF-FM Equipment Process

The VHF-FM radio (FM622A) is used primarily for military/CCT communications.It provides short-range line-of-sight, two-way simplex voice communicationin the 30 - 75.95 mHz frequency range.

The VHF-FM EQUIP is activated by the VHF-FM Tailored Mode SPEC whenever a* formatted control message is to be sent to the radio.

3.2.5.3.1

Input shall be a message containing the desired control:

o control input (I word)

Control capability consists of one of the following:

o on/off control

o manual frequency selection

o volume control

o T/R contro4

o re-transmit control

o home control

o squelch disable

o squelch carrier

o squelch tone

3.2.5.3.2 Processing

When activated by the VHF-FM Tailored Mode SPEC, the EQUIP shall determinethe type of control desired, format the required message, and store it ina compool for subsequent transfer to the radio. Input control data will havebeen checked by the activating task for invalid/out-of-range conditions, soEQUIP processing shall assume valid data.

106 *

* o .

Page 119: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.5.3.3 Outputs

Output shall be control messages corresponding to the request, and statusupdates:

o control command (1 word)

o status update (I word)

3.2.5.4 HF/SSB Equipment Process

The HF/SSB radio (AN/ARC-123) is used for long-range military communications.It provides two-way simplex voice communications at distances up to 2,500nautical miles, operating in the 2 - 30 mHz frequency band.

The HF/SSB EQUIP is activated by the HF/SSB Tailored Mode SPEC whenever aformatted control message is to be sent to the radio.

* 3.2.5.4.1

Input shall be a message containing the desired control:

o control input (1 word)

Control capability consists of one of the following:

o on/off control

o manual frequency selection

o SSB

o amplitude modulation equivalent

o frequency shift key

o continuous wave

o volume control

o squelch disable

o noise blank

o RF gain control

3.2.5.4.2 Processing

Wnen activated by the HF/SSB Tailored Mode SPEC, the EQUIP shall determinethe type of control desired, format the required message, and store it ina compool for subsequent transfer to the radio. Input control data will havebeen checked by the activating task for invalid/out-of-range conditions, soEQUIP processing shall assume valid data.

1..

* 107

-, - - _ ..... a *

Page 120: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.5.4.3 Outputs

Output shall be control messages corresponding to the request, and status

updates:

o control command (I word)

o status update (I word)

3.2.5.5 ICS Equipment Process

The Intercommunication Set (AN/AIC-18) provides:

o two-way voice communication between crew stations

o interfaces with radio tranceivers, navigation receivers, public ad-dress amplifier, and maintenance intercom outlets

, The ICS allows for selection, control, and distribution of radio systems forairborne/ground station communication and monitoring.

The ICS EQUIP is activated cyclically eight times per second from startup.

3.2.5.5.1 Inputs

Input shall be ICS control panel ID and settings, and hot-mic select fromthe CCA:

o hot-mic selection (CCA) (1 word)

o monitoring (mixer) switches with individual volume controls (n words)

o hot-listen selection (I word)

o mic-talk selection (panel) (I word)

o call selection (I word)

o aux listen selection (1 word)

3.2.5.5.2 Processing

The EQUIP shall determine If panel setting has changed since the lastactivation. If the settings are the same, the EQUIP shall terminate.If changed, the EQUIP shall format/store corresponding ICS control messages.

3.2.5.5.3 Outputs

Output shall be control messages corresponding to the request, and statusupdates:

108

Page 121: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

o control command (I word)

o status update (1 word)

3.2.5.6 Public Address Equipment Process

The P.A. System (AN/AIC-13) is used for voice announcements in the cargo areas.

The P.A. EQUIP is activated cyclically eight times per second from startup.

3.2.5.6.1 Inputs

Input shall be the P.A. control panel output buffer to be monitored by theEQUIP:

, o on/off control

o speaker selection

o mixer switch control

o volume control

3.2.5.6.2 Processing

The EQUIP shall determine if panel setting has changed since the lastactivation. If the settings are the same, the EQUIP shall terminate.If changed, the EQUIP shall format/store corresponding P.A. controlmessages.

3.2.5.6.3 Outputs

Output shall be control messages corresponding to the request, and P.A.status updates:

o control command (1 word)

o status update (1 word)

3.2.5.7 Secure Voice Equipment Process

The Secure Voice System (TSEC/KY-58) encrypts and decrypts VHF/UHF voicecoriunication.

The secure voice EQUIP is activated by the Secure Voice Tailored Mode SPECwhenever on/off control is to be sent to the unit.

3.2.5.7.1 Input

Input shall be a message containing desired control:

o on/off indication (1 word)

109

Page 122: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.5.7.2 Processing

This EQUIP shall store the on (or off) control message in a compoolfor subsequent transfer to the unit.

3.2.5.7.3 Outputs

Output shall be control messages corresponding to the request, and statusupdates:

o control command (1 word)

o status update (1 word)

3.2.5.8 DEK Equipment Process

The DEK Equipment Process controls the DEK input procedure. An eight-times-per-second activation rate is initiated by a Handler Specialist Functionwhenever DEK input is required for a particular IMK side key function or MPDchecklist function. It is deactivated when an ENTER is received or whenthere is no further need for the input.

i3.2.5.8.1 Inputs

Input shall be one character:

o character (I word)

which may represent any of the following:

o digits 0 through 9

o CLEAR (re-set)

o CHECK (checklist checkoff - MPD)

o SPACE (checklist skip function - MPD)

o PAGE (advance page - MPD)

o ENTER (end-of-data)

o NULL (no input)

3.2.5.8.2 Processing

When activated, the DEK EQUIP shall initialize the input buffer. Eachactivation thereafter (eight/second) the EQUIP shall determineinput status, and terminate if there was no input since the last activation.

If the input was a 0 - 9 digit (or its upper case equivalent), and the inputbuffer isn't full, the character shall be stored; otherwise, the buffer shall

110

Page 123: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

be cleared and a message displayed on the center MPD via the Error/

Warning DISP. The maximum size of the input buffer is[r-characters.

If the input is CLEAR, the EQUIP shall clear the buffer.

CHECK, SPACE, PAGE are used for MPD checklist functions; the MPD HandlerSpecialist Function is activated to control the processing of the inputbuffer. If the DEK EQUIP is assigned to an IMK Handler, these keys shall beignored.

ENTER indicates the end of the input data string; the Handler Specialist Func-tion shall be activated to process the input buffer.

3.2.5.8.3 Outputs

Output shall be the final DEK input buffer:

o input buffer (1 - n word)

o packed two characters per word.

3.2.5.9 DSMU Equipment Process

The DSMU controls display distribution and refresh functions. It containsmodules which provide five independent raster memory channels to refresh theMPD's, and two independent stroke channels for the HUD's. The display memoryis loaded/updated from the MPDG. Switching commands allow sensor video to bedisplayed in lieu of a display stored in a memory module.

The DSMU EQUIP is activated by the OSMU Tailored Mode SPEC whenever a switch-ing command is to be sent to the DSMU as a result of a crew request via theIMK.

3.2.5.9.1 Inputs

Input shall consist of

o DSMU switching request (1 wrd)

3.2.5.9.2 Processing

The DSMU EQUIP shall format the switching command and storein -in output buffer for transfer to the DSMU.

3.2 5.9.3 Outputs

Output shall consist of

o DSMU switching command (I word)

o Switching status (1 word)

111

Page 124: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.5.10 TACAN Equipment Processes

The TACAN System (AN/ARN-118) furnishes data relative to a selected TACANfacility operating in the 962 - 1213 mHz frequency band.

Two TACAN EQUIPS are provided. The input EQUIP is activated cyclically toreceive data; the output EQUIP formats TACAN commands to satisfy controlrequests.

3.2.5.10.1 TACAN Input EQUIP

This EQUIP processes data from the TACAN system. It is activated eight timesper second.

3.2.5.10.1.1 Inputs

Input shall be TACAN data and previous status:

o bearing (I word)

, o range (1 word)

o range rate, to-from indication (1 word)

o status (1 word)

o previous status (1 word)

3.2.5.10.1.2 Processing

The input EQUIP shall format and scale the data as necessary, and store theresults in a compool. if status has changed, the SSSM shall be activated.

3.2.5.10.1.3 Outputs

Output shall be the formatted data:

o bearing (I word)

o distance (1 word)

o range rate (1 word)

o to-from indicator (I word)

o co"-se deviation signal (1 word)

3.2.5.10.2 TACAN Output EQUIP

This EQUIP formats control messages to the TACAN. It is activated by theTACAN Tailored Mode SPEC whenever control is requested by a crew member viathe IMK.

112

Page 125: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.5.10.2.1 Inputs

Input shall be control type/value data:

o on/off

o channel select

o mode select

o receiveo transmit/receiveo A/A receiveo A/A transmit

o auto/manual tuning

o volume

o course select

o test capability

3.2.5.10.2.2 Processing

The input EQUIP shall generate the control message corresponding to the type/value input data.

3.2.5.10.2.3 Outputs

Output shall be the control message and status:

o TACAN control (1 word)

o Control status update (I word)

3.2 5.11 HCU Equipment Process

The Hand Controller Unit provides crew memebers with: 1) the capability topoint the radar antenna and 2) data update capability via display cursorpositioning.

Th( HCU EQUIP is activated 16 times per second (whenever an HCU display-selectpushbutton is in effect) to process cursor displacements.

3.2.5.11.1 Inputs

input shall be activate/designate pushbutton and X, Y displacement:

o pushbutton (1 word)

o Lxy (2 words)

113

Page 126: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.5.11.2 Processing

The HCU EQUIP shall keep track of the "null", "activate", or "designate"state of the controller pushbutton. The state is initially "null". Nocalculations are performed until the controller pushbutton is pressed for thefirst time, changing the state to "activate".

When the state is "activate", the EQUIP shall evaluate the effective cursorposition with respect to the selected display, and store these displacementsfor use by the particular DISP that is to use them. If the antenna controlpushbutton is active, and the displacements represent a change from the pre-vious, the Radar Tailored Mode SPEC shall be activated.

When the controller pushbutton is pressed a second time, the state changes to"designate" and no further calculations are performed; the last calculateddisplacement is left in a compool to be used, for example, in a navigationdata update procedure.

* 3.2.5.11.3 Outputs

Output shall consist of displacement data and pushbutton state:

o L X, AY (2 words)

o state - null, activate, designate (1 word)

3.2.5.12 OMEGA Equipment Processes

The OMEGA Radio Navigat&ion System (AN/ARN- ) provides airplane positionfixes using the worldwide network of VLF ground transmitters.

Two OMEGA EQUIPS are provided. The input EQUIP is activated cyclically toreceive data; the output EQUIP formats OMEGA commands to satisfy controlrequests.

3.2.5.12.1 OMEGA input EQUIP

This EQUIP processes dat . from the OMEGA system. It is activated eight timesper second.

3.2.5.12.1.1 Inputs

Input shall consist of:

o three channels of RF information

3.2.5.12.1.2 Processing

The OMEGA input EQUIP shall format/scale RF data as

114

Page 127: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

necessary, and store in a compool for use in navigation calculations.

3.2.5.12.1.3 Outputs

Output shall be the OMEGA parameters, properly formatted and scaled, to bestored in a compool:

o parameters (n words)

3.2.5.12.2 OMEGA Output EQUIP

This EQUIP formats control messages to the OMEGA system. It is activated bythe OMEGA Tailored Mode SPEC whenever control is requested by a crew membervia the IMK.

115

Page 128: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.5.12.2.1 Inputs

Input shall consist of

o On/Off (1 word)o Auto/Manual Tuning (1 word)o GMT, Date, Latitude, Longitude (4 words)

3.2.5.12.2.2 Processing

The output EQUIP shall generate the control message corresponding to thetype/value input data.

3.2.5.12.2.3 Outputs

Output shall be the control message and status.

* o OMEGA Control (1 word), o Status Update (1 word)

3.2.5.13 CCA Equipment Process

The Column Control Assembly provides a shaker capability for imminent stallconditions.

The CCA EQUIP is activated by the FCS EQUIP whenever shaker control (on oroff) is required.

3.2.5.13.1 Inputs

Input shall consist of

o Shaker Control Request

3.2.5.13.2 Processing

The CCA EQUIP shall store the control message ir a Compool forsubsequent transfer to the CCA, and update the CCA status accordingly.

3.2.5.13.3 Outputs

Output shall be control commands and status updates.

o CCA Shaker On/Off Control (1 word)o On/Off Status (I word)

3.2.5.14 FCS Equipment Process

The Flight Control System provides air data, attitude, and mode and statusinformation. This information is processed by the avionics system toprovide steering data for the flight control system.

116

Page 129: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

Two FCS EQUIP's are provided. The input EQUIP is activated cyclically toreceive data; the output EQUIP is activated cyclically to send steeringdata.

3.2.5.14.1 FCS Input EQUIP

The FCS input EQUIP processes data from the flight control system. It is

activated 32 times per second.

3.2.5.14.1.1 Inputs

Input shall be FCS output data, and previous status.

o Air Data (10 words), 3 channelso Attitude (5 words), 3 channelso Mode and Status (I word), 3 channelso Previous Status (I word)

3.2.4.14.1.2 Processing

The Equip shall process the data as necessary, and store the results ina Compool. If the status has changed, the SSSM shall be activated. TheLIGHTS DISP shall be activated for on/off control of the EFCS WarningLight, as necessary.

Data processing may include scaling, signal source selection, smoothing,

algorithm calculations, etc.

3.2.5.14.1.3 Outputs

Output shall consist of

o Air Data (10 words)o Attitude Data (5 words)o Mode/Status (I word)o EFCS Light Control (1 word)

3.2.5.14.2 FCS Output EQUIP

The FCS Output EQUIP controls the sending of steering signals to the FCS.It is activated cyclically 16 times per second.

3.2.5.14.2.1 Inputs

Input shall consist of

o Steering Requests (4 words)

3.2.5.14.2.2 Processing

The output EQUIP shall qeneratethe steering messages and outputs them toa Compool.

117

,a- ---

Page 130: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.5.14.2.3 Outputs

Output shall consist of

o Steering Signals (4 words)

3.2.5.15 Flares Dispenser System Equipment Process

The Flares Dispenser System contains four sets of flares which may bedropped as a defensive measure against infrared seeker threats.

The Flares Dispenser System EQUIP is activated by the Flares Dispensertailored Model SPEC whenever a formatted control message is to be sentto the system.

3.2.5.15.I Inputs

Input shall be control requests and status.

o On/Off (1 word)*o Flare Set # (I word)

o Flare Status (2 words)

3.2.5.15.2 Processing

The Flares Dispensar System EQUIP shall generate control messagesand store them in a Compool for transmission. The software flare statusshall be updated.

3.2.5.15.3 Outputs

Output shall be control commands to the Flares Dispenser System andstatus.

o On/Off Command (1 word)o Flare Drop Command (I word)o Current Flare Status (2 words)

3.2.5.16 G-Meter Equipment Process

The G-Meter displays 1) current vertical acceleration, 2) the low verticalacceleration since last reset, and 3) the high vertical acceleration sincelast reset.

The G-Meter EQUIP is activated 4 times per second to monitor the resetbutton.

3.2.5.16.1 Inputs

Input shall consist of

o Reset Button Status (I word)

HRI

Page 131: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.5.16.2 Processing

If the reset button shows a change in status, the low vertical accelerationand high vertical acceleration shall be set equal to 1.

3.2.5.16.3 Output

Output shall be new low and high vertical acceleration values.

o Accelerations (2 words)

3.2.5.17 INS Equipment Processes

The INS (Carousel IV) is a self-contained inertial navigation system (includinga digital computer) which provides worldwide aircraft navigation entirelyindependent of ground communication.

Two INS EQUIP's are provided. The input EQUIP is activated cyclically toreceive data; the output EQUIP formats INS commands to satisfy controlrequests.

3.2.5.17.1 INS Input EQUIP

This EQUIP processes data from the INS. It is activated 4 times per second.

3.1.5.17.1.1 Inputs

Input shall consist of

o Aircraft Position and Velocity (6 words)o Pitch and Roll (2 words)o Calculated Digital Data ( n words)o Status (1 word)

3.2.5.17.1.2 Processing

The EQUIP shall format and scale the data as necessary, and storethe results in a Compool. If the status has changed, the SSSM Shall beactivated.3.2.5.17.1.3 Outputs

Output shall consist of

o Position and Velocity (2 words)o Pitch and Roll (2 words)o Other Data (n words)

3.2.5.17.2 INS Output EQUIP

This EQUIP formats control messages to the INS. It is activated by the INSTailored Mode SPEC whenever control is requested by a crew member via the IMK.

119

Page 132: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.5.17.2.1 Inputs

Input shall consist of

o Mode (1 word)o Auto/Manual Select (I word)o Initial Position (2 words)o Way Point Loading (n words)

3.2.5.17.2.2 Processing

The EQUIP shall generate the control message corresponding to the type/value input data.

3.2.5. 17.2.2. Outputs

Output shall be the control message and updated control status:

, o INS Control (1 word)and Status (1 word)

3.2.5.18 SKE/ZM Equipment Processes

The Station Keeping Equipment (AN/APN-169) is a cooperative air-to-airstation keeping system for flights of up to 36 aircraft. It enables theseaircraft to locate and identify one another; and to maintain formation/rendezvous regardless of visibility. The SKE interfaces with the MDSC toprovide a formation display.

Two SKE EQUIP's are provided. The input EQUIP is activated cyclically toreceive data; the output EQUIP formats SKE commands to satisfy controlrequests.

3.2.5.18.1 SKE Input EQUIP

This EQUIP processes data from the SKE. It is activated 4 times per second.

3.2.5.18.1.1 Inputs

Input shall consist of

o Aircraft Range and Bearing (n words)o SKE Status (1 word)

3.2.5.18.1.2 Processing

The EQUIP shall format and scale the data as necessary, and store theresults in a Compoel. If the status has changed, the SSSM shall be activated.

3.2.5.18.1.3 Outputs

Output shall consist of

o Aircraft Range and Bearing (n words)

120

Page 133: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.5.18.2 SKE Output EQUIP

This EQUIP formats control messages to the SKE. It is activated whenevercontrol is requested by a crew member via the IMK.

3.2.5.18.2.1 Inputs

Input shall be control type/value data:

o On/Off (I word)o Freq A/B (1 word)o In Track Offset (I word)o Altitude Offset (1 word)o Cross-Track Offset (I word)o Leader Select (I word)o Proximity Warning Range (1 word)o Proximity Warning Tone On/Off (1 word)o Master-Follow Select (I word)o Master Indicator (1 word)o BITE Test (0 word)o ID Function Select (I word)o Range Scale (I word)o Range Mark (1 word)o Display Centering (1 word)o Blanking (1 word)

3 2.5.18.2.2 Processing

The EQUIP shall generate the control message corresponding to the type/value of the input request.

3.2.5.18.2.3 Outputs

Output shall be the control message and updated control status.

o SKE Command (I word) and Status (1 word)

3.2.5.19 LF/ADF Equipment Processes

The LF/ADF (OF-206) provides the navigation calculation with bearing to aselected low frequency radio station.

Two LF/ADF EQUIP's are provided. The input EQUIP is activated cyclically toreceive data; the output EQUIP formats LF/ADF commands to satisfy controlrequests.

3.2.5.19.1 LF/ADF Input EQUIP

This EQUIP processes data from the LF/ADF unit. It is activated four timesper second.

121

. . . . . '. . . . . . . . . . . . . . . .I

Page 134: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.5.19.1.1 Inp'its

Input shall consist of

o Bearing (I word)o Status (1 word)

3.2.5.19.1.2 Processing

The input EQUIP shall format and scale the bearing input data, and storeit in a Compool. If the status has changed, the SSSM shall be activated.

3.2.5.19.1.3 Outputs

Output shall consist of

o Bearing (1 word;

3.2.5.19.2 LF/ADF Output EQUIP

This EQUIP formats control messages to the LF/ADF. It is activated whenevercontrol is requested by a crew member via the IMK.

3.2.5.19.2.1 Inputs

Input shall be control type/value data.

o On/Off (1 word)o Auto/Manual Select (I word)o Frequency Select (1 word)o Test Select (I word)o Volume (1 word)

3.2.5.19.2.2 Processing

The output EQUIP shall generate the control message correspondina to thetype/value of the input request.

3.2.5.19.2.3 Outputs

Output shall be the control message and updated control status.

o LF/ADF CommanG (I word) and Status (I word)

3.2.5.20 UHF/ADF Equipmnent Processes

The UHF/ADF (DF-301E) provides the navigation calculation with bearing to aselected ultra-high frequency radio station.

Two UHF/ADF EQUIP's are provided. The input EQUIP is activated cyclically toreceive data; the output EQUIP formats UHF/ADF commands to satisfy controlrequests.

122

6,

Page 135: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.5.20.1 UHF/ADF Input EQUIP

This EQUIP processes data from the UHF/ADF unit. It is activated four timesper second.

123

t *.

Page 136: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.5.20.1.1 Inputs

Input shall consist of

o Bearing (1 word)o Status (1 word)

3.2.5.20.1.2 Processing

The input EQUIP shall format and scale the bearing input data, and storeit in a Compool. If status has changed, the SSSM shall be activated.

3.2.5.20.1.3 Outputs

Output shall consist of

* o Bearing (1 word)

3.2.5.20.2 UHF/ADF Output EQUIP

This EQUIP formats control messages to the UHF/ADF. It is activated whenevercontrol is requested by a crew member via the IMK.

1.2.5.20.2.1 Inputs

Input shall be control type/value data.

o On/Off (1 word)o Auto/Manual Select (1 word)o Frequency Select (I word)o Test Select (1 word)o Volume (I word)

3.2.5.20.2.2 Processing

The output EQUIP shall generate the control message corresponding to thetype/value of the input request.

3.2.5.20.2.3 Outputs

Output shall be the control message and updated control status.

o IJHF/ADF Command (1 word) and Status (1 word)

3.2.5.21 Rade.r Altimeter Equipment Processes

The two Radar Altimeters (AN/APN-194) are range tracking radars which providealtitude information from 0 - 5000 feet.I

Two Radar Altimeter EQJIPS are provided. The input EQUIP is activatedLyclically to receive data; the output EQUIP formats Radar Altimeter commandsto satisfy tontrol requests.

124

Page 137: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.5.21.1 Radar Altimeter Input EQUIP

This EQUIP processes data from the Radar Altimeter. It is activated four

times per second.

3.2.5.21.1.1 Inputs

Input shall consist of

o Status (1 word)o Altitude (1 word)o Radar altimeter ID (I word)

3.2.5.21.1.2 Processing

The input EQUIP shall format and scale the altitude input data,and store it in a Compool. If the status has changed, the SSSM shall beactivated

3.2.5.21.1.3 Outputs

Output shall consist of

o Altitude (1 word)

3.2.5.21.2 Radar Altimeter Output EQUIP

This EQUIP formats control messages to the Radar Altimeter. It is activatedwhenever control is requested by a crew member via the IMK.

3.2.5.21.2.1 Inputs

Input shall consist of

o On/off (1 word)o Low altitude select (I word)o ID (I word)o Test select (1 word)

3.2.5.21.2.2 Processing

The output EQUIP shall generate the control message correspondingto the type/value of the input request, and store it in a Compool.

3.2.5.21.2.3 OutputsDtput shaTl consist of

o radar altimeter command (1 word)

125

Page 138: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.5.22 ILS Equipment Processes

The Instrument Landing System (AN/ARN-108) is used in conjunction withground transmitting equipment and airplane flight director calculations toprovide display capability for marker beacon, glideslope, and localizersignals.

Two ILS EQUIPS are provided. The input EQUIP is activated cyclically toreceive data; the output EQUIP formats ILS commands to satisfy controlrequests.

3.2.5.22.1 ILS Input EQUIP

This EQUIP processes data from the ILS unit. It is activated four times persecond.

3.2.5.22.1.1 Inputs

Input shall consist of

o Bearing (1 wcrd)o Status (I word)o Localizer/glide slope deviation (2 words)o ILS ID (1 word)

3.2.5.22.1.2 Processing

The EQUIP shall format and scale the bearing data, and store it ina Compool. If the status has changed, the SSSM shall be activated,

3.2.5.22.1.3 Outputs

Output shall consist of

o Bearing (I word)n Localizer/olide slope deviations (2 words)

3.2.5.22.3 ILS Output EQUIP

This EQUIP formats control messages to the ILS. It is activated whenevercontrol is requested by a crew member via the IMK.

3.2.5.22.2.1 Inputs

Input shall consist of

o On/off (1 word)o Auto/manual select (I word)o Frequency select (I word)o Course selecto MDA selecto ILS ID

126

Page 139: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.5.22.2.2 Processing

The EQUIP shall generate the control message corresponding to the

type/value of the input request.

3.2.5.22.2.3 Outputs

Output shall consist of

o ILS command (I word) and Status (1 word)

3.2.5.23 Compass Equipment Processes

The Magnetic Compass (C-12) provides heading information for navigation.

Two Compass EQUIPs are provided. The input EQUIP is activated cyclicallyto receive data; the output EQUIP formats Compass Commands to satisfycontrol requests.

3.2.5.23.1 Comoass Input EQUIP

This EQUIP processes data from the Compass unit. It is activated four timesper second.

3.2.5.23.1.1 Inputs

Input shall consist of

Heading (1 word)a Status (1 word)

3.2.5.23.1.2 Processing

The input EQUIP shall format and scale the heading data, and store it ina Conpool. If the status has changed, the SSSM shall be activated.

3.2.5.23.1.3 Outputs

Output shall consist of

o Heading (1 word)

3.2.5,23.2 Compass Output EQUIP

This EQUIP formats control messages to the Compass. It is activated whenevercontrol is requested by a crew member via the IMK.

.1.2.5.23.2.1 Inputs

Input shall consist of

127

Page 140: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

o On/off (1 word)o Slaved option (1 word)o D.G. (1 word)

o Set heading (1 word)o Set latitude (I word)

3.2.5.23.2.2 Processing

The output EQUIP shall generate the control message corresponding to thetype/value of the input request.

3.2.5.23.2.3 Outputs

Output shall consist of

o Compass command (1 word)o Status (I word)

3.2.5.24 LR Radar Equipment Processes

The Long Range Radar (AN/APQ-122) provides precise navigation capabilitiesfor long-range grourd mapping, weather detection, and beacon interrogation.A high-resolution CRT radar display is available to the crew upon request.

The Radar EQUIP is activated by the Radar Tailored Mode SPEC whenever aformatted control message is to be sent to the unit.

3.2.5.24.1 Inputs

Input shall consist of

o Mode select (I word)o Frequency select (1 word)o Magnetic variation select (1 word)o RF power, gain (2 words)o Beam (1 word)o Azimuth stabilizer (I word)o ISO echo (1 word)o Scan select (I word)o Range select (1 word)o Fast time on/off (I word)o Sens. time (1 wurd)o Frequency agile mode on/off (1 word)o Heading marker intensity (I word)o Range marker intensity (1 word)o Sweep intensity (1 word)

3.2.5.24.2 Processing

The EQUIP shall generate the cuntrol message corresponding to the type/value of the input request, and store it in a Compool for subsequenttransmission to the Long Range Radar.

1,28

Page 141: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.5.24.3 Outputs

Output shall consist of

o Radar command (1 word) and status (1 word)

3.2.5.25 IRD&W Equipment Processes

The Infrared Detection and Warning System is a defensive countermeasurewhich provides threat information. It interfaces with the MDSC to providea quadrant-orientated threat display.

The IRDW EQUIP is activated by the IRDW Tailored Mode SPEC whenever aformatted control message is to be sent to the unit.

3.2.5.25.1 Inputs

* Input shall consist of

o on/off (1 word)

3.2.5.25.2 Processing

The EQUIP shall store the on (or off) control message in a Compool forsubsequent transfer to the device.

3.2.5.25.3 Outputs

Output shall consist of

o on/off command

3.2.5.26 RHAWS Equipment Process

The Radar Homing and Warning System (AN/APR-36/37) is a radar-detecting,defensive countermeasure which provides threat information to the crew viaMPD display.

The RHAWS EQUIP is activated by the RHAWS Tailored Mode SPEC whenever a

formatted control message is to be sent to the unit.

3.2 5.26.1 Inputs

Input shall consist of

o on/off (1 word)

3.2.5.26.2 Processing

The EQUIP shall store the on (or off) control message in a Compool forsubsequent transfer to the device.

129

Page 142: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

I"3.2.5.26.2 Processing

The EQUIP shall store the on (or off) control message in a Compool forsubsequent transfer to the device.

3.2.5.26.3 Outputs

Output shall consist of

o On/Off Command (I word)

3.2.5.27 Flight Surfaces Equipment Process

The current positions of controllable flight surfaces (e.g., flaps) aremonitored for display and algorithm purposes.

The Flight Surfaces EQUIP is activated 2 times per second to read current* position settings of the surfaces.

3.2.5.27.1 Inputs

Input shall consist of

o Elevator Trim Positions (9 words)o Left-Wing Flap/Spoiler Positions (7 words)o Right Wing Flaps/Spoiler Positions (7 words)

3.2.5.27.2 Processing

The EQUIP shall process the input data as required, and storethe result in a Compool.

3.2.5.27.3 Outputs

Output shall consist of

o Elevator Trim Positions (9 words)o Left Flap Positions (7 words)o Right Flap Positions (7 words)

3.2.5.28 Aircraft Sensors Equipment Process

Aircraft sensors provide current status of -

o Fuelo Engineso Powero Accelerometer

for display.

130

Page 143: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

The Aircraft Sensors EQUIP is activated 2 times a second to read thecurrent sensor output.

3.2.5.28.1 Inputs

Input shall consist of

o Fuel (n words)o Engines (n words)o Power (n words)o Accelerometer ( 1 word)

3.2.5.28.2 Processing

The EQUIP shall process the input data as required, and storethe results in a Compool.

3.2.5.28.3 Outputs

Output shall consist of

o Fuel (n words)o Engines (n words)o Power (n words)o Accelerometer (I word)

3.2.5.29 Brakes/Gear/Caution Equipment Process

The current status of the brake and landing gear systems, and the cautionpanel, is monitored for display and algorithm purposes.

The Brake/Gear/Caution EQUIP is activated 2 times a second to copy the

current status.

3.2.5.29.1 Inputs

Input shall consist of

o Weight-On-Gear (1 word)o Caution Lights (n words)o Master Caution Light (1 word)o Landing Gear (1 word)o Brakes (1 word)o Gear-Up and Locked (1 word)o Previous Values for the Above (n words)

3.2.5.29.2 Processing

The EQUIP shall process the input data as required, andstore the results in a Compool. Changes in the status of any item from itsprevious value may result in the activation of the Error/Warning DISP.

131

Page 144: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.5.29.3 Outputs

Output shall consist of

o Weight-On-Gear (I word)o Caution Lights (n words)o Master Caution Light (1 word)o Landing Gear (1 word)o Brakes (1 word)o Gear-Up and Locked (1 word)o Message ID (I word)

3.2.5.30 Avionics On/Off Equipment Process

On/off control is provided for the following avionics equipment.

o Counting Accelerometer o HUD 1o Gear-Up and Locked - left o HUD 2

* o Gear-Up and Locked - right o HSD 1o Weight on Gear - left o HSD 2o Weight on Gear - right o MPD 1o Stick Shaker 1 o MPD 2o Stick Shaker 2 o MPD 3o Stab. Trim Position o MPDG 1o Flap Position - left o MPDG 2o Flap Position - right o DSMUo Fuel Totalizer o MDSCo Engine 1 o MFDCo Engine 2 o HCUo IRD & W o MMKo RH & W o TACANo Flares Dispenser o SKEo Long Range Radar o HF/SSB Radioo Radar Altimeter o VHF-AM Radioo Radar 2 o VHF-FM Radioo Magnetic Compass o UHF-AM Radio 1o INS o UHF-AM Radio 2o OMEGA o IFFo ILS 1 o Secure Voiceo ILS 2 o Public Addresso LF ADF o Intercommunicdtion Seto UHF ADF

The Avionics On/Off EQUIP is activated by the Avionics On/Off Tailored ModeSPEC whenever On/Off control is requested from the IMK.

3.2.5.30.1 Inputs

Input shall consist of

o Equipment ID (i word)o On/Off Control (1 word)

132

Page 145: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

I3.2.5.30.2 Processing

The EQUIP shall generate the on (or off) message and store in a Compoolfor subsequent transfer to the specified device.

3.2.5.30.3 Outputs

Output shall consist of

o On/Off Command (1 word)

3.2.5.31 FDR Equipment Process

The Flight Data Recorder (AN/ASH-31V) is a survivable recorder used forstoring a current 30-minute history of voice communications and flight data.A beacon transmitter facilitates recovery after deployment.

, The FDR EQUIP in activated cyclically TBD times per second.

3.2.5.31.1 Inputs

Input shall be Compool data to be recorded.

o Data (n words)

3.2.5.31.2 Processing

At each activation, the FDR EQUIP shall format two channels of data and storeit in a Compool for transfer to the FDR.

3.2.5.31.3 Outputs

Output shall be data to be sent to FDR.

o Data (n words)

133

Page 146: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

3.2.6 Special Requirements

This section contains special requirements imposed on Application Softwaredevelopment.

3.2.6.2 JOVIAL J73

All Applications Software will De coded in the JOVIAL J73 higher orderlanguage.

3.2.6.1 Structured Programming

Top-down, structured programming concepts will be used throughout ApplicationsSoftware development. Software elements will be established which correspondto functions defined in this document.

-13

"134

Page 147: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

I. ..3.3 Adaptation

This section summarizes the Applications Sofiware requirements with resoect

to the operatinq facility, system parameters, and system capacities.

3.3.1 General Environment

Further definition of the IDAMST system design is required prior to completingthis portion of the specification. Pendinq definition the followinq assump-tions are made.

3.3.1.1 IDAMST Core Elements

IDAMST core element hardware including the core element control/displays areassumed to be identical in all AMST aircraft and require no modification orvariations in software to adapt the IDAMST OFP and OTP software.

3.3.1.2 Other IDAMST Integrated Hardware

* Variations in AMST equipment complement associated with the IDAMST system isexpected. It is assumed that the IDAMST OFP and OTP software till be auto-

*matically adaptable to hardware variations in the AMST. This will beaccomplished through the use of an equipment status word frum the IDAMSTavionic hardware which identifies the existing hardware configuration. TheOFP and OTP software will subsequently adapt to the actual configuration byomitting software functions associated with non-existent avionics hardwareelements. The OFP and OTP software will compile a list of active andinstalled avionic equipment hardware and display list upon command and alsowrite list on DITS recorder for a maintenance record.

3.3.2 System Parameters

Constants and other data pertaining to the particular mission must be avail-able at load time for the Application Software to function at full capability.

3.3.3 System Capacities

Estimated capacity requirements of the Applications Software is summarizedin Table 3.3-1. These estimates arerelated to an IDAMST processor like that described in Reference 2.2(c),"Prime Item Product Fabrication Specification for DAIS Processor", and allowa 25 growth margin.

135

Page 148: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

L'i-

C)) ~~ Ul

4n~

<1R Ln M Ln 0 m C OC M LAO ICn G'-l. c L Ch %& fO mfO D Lf r-. m~ m mCD~ c'. C, C- C) 'a

q:.c 0C i ( ,J, * .--:r . cli m f-)(i

0 A

iS 4'

C'Ic

Ul CDCo Dc f C DP C

U 0)

0oo ra'A 0o M~ OO A O 0 Ito CUOC/IC

CL CL 41

>U a) > 4 0)

4.)1 d)C U u a) OC-CC- E 4 L > - C

OOr0 0 o () . Q

Page 149: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

This page intentionally left blank.

137

Page 150: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

4.0 QUALITY ASSURANCE PROVISIONS

This section identifies the basic method for accomolishing software verifica-tion.

4.1 Introduction

IDAMST CPCIs will incorporate top-down, structured concepts, described brief-ly below:

Structured Program

A structured program is a computer program constructed of a basic set of con-trol logic figures which provide at least the following: Sequence of two ormore operations, conditional branch to one of two operations and returnrepetition of an operation. A structured proaram has only one entry and oneexit point. A path will exist froIi the entry to each node and from each'nodeto the exit. In addition, certain practices are associated, such as indenta-tion of source code to represent logic levels, use of intelliaent data namesand descriptive commentary.

To- D own P roarammi9n

Top-down programming is tne concept of Derformino in hierarchical sequence adetailed design, code, integration and test as concurrent operations.

Top-Down Struc tured regrams

A top-down structured Program is a structured proqram with the additionalcharacteristics of the surce code being lonically but not physically seg-mented in a hierarchical manner and only dependent on code already written.Control of execution between segments is restricted to transfers betweenvertically adjacent hierarhical segments.

Top-down codinq and verification is an ordering of system development whichallows for continual integration of the system parts as they are developedand provides for interfaces prior to the parts being developed. At eachstage, the code already tested drives the new code, and only external datais required.

In top-down programmng, the system is organized into a tree structure ofsegments. The top segmerts contain the highest level of control logic anddecisions within the program, and either passes control to the next levelsegments or identifies the next level segments for in-line inclusions. Thenext level may include stlbs. Stubs which are to be replaced eventually withrunning code may conta'n a "no operation" instruction or possibly a displaystatement to the effect that control has been received. The process ofreplacement of successively lower level stubs with operational code continuesuntil all fun(tions within a system are coded and verified.

In top-down coding arod verification, the highest level element is coded first.Coding, checkout, and integration proceed down the hierarchy until the lowestlevels have been intoIratod. This does not imply that all elements at agiven level are developer in parallel. Some branches will intentionally he

138

Page 151: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

*i 'developed early, e.g., to permit early training and early development ofcritical functions or hardware/software integration.

Many systems interfaces occur through the data base defintion in addition tocalling sequence parameters. Top-down programming requires that sufficientdata definition statements be coded and that data records be generated beforeexercisinq any segment which references them. Ideally, this leads to a sinqleset of definitions serving all the programs in a given application.

This approach provides the ability to evolve the product in a manner thatmaintains the characteristic of always being operable, extremely modular andalways available for successive levels of testing that accompany the corres-ponding levels of implementation. Exception to the top-down coding and integ-ration approach will be considered on a case-by-case basis.

Each computer program will be coded in a higher order language. Use ofassembly or machine language will be restricted to coding of certain executivefunctions where the higher order language cannot be used.

Real Time Structured Programs

An additional complexity in the IDAMST system is the Real Time, asynchronouscommunication of structured programs as tasks. Tasks are also organized as ahierarchy. Each task has a Controller Task which is the only task permittedto schedule or cancel the lower level task. However, any task is permittedto activate any other task in IDAMST.

4.2 Computer Program Verification

Computer program verification is the process of determining whether theresults of executing a computer program in a test environment agree with thespecification requirements. Verification is usually only concerned with thelogical correctness of the computer program (i.e., satisfying the functional/performance requirements) and may be a manual or a computer-based process(i.e., testing software by executing it on a computer).

The use of top-down structured programming techniques provide certain programcharacteristics that may lead to a simplification of the computer programverification process. Top-down integration of the program elements in a CPCIminimizes the use of complex driver routines and replaces them with actualproqram elements and simple program stubs. It also provides a system inwhich the computer program is continually being tested as successively lowerlevel; of proqram elements are integrated and the interfaces between proqramelements are verified prior to the integration of the next lower level.

4.2.1 Program Element Tests

Program elements are coded in the sequence required for top-down integration.When coding and code review are completed, each proqram element shall befunctionally tested in a stand-alone configuration by the programmer toassure that the element can be executed and that the specified functions areperformed. Since proqram elements are small and are restricted to one entrypoint and one exit point, the test environment is relatively simple.

139

Page 152: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

4.2.2 CPCI Integration Tests

Following successful completion of the Program Element Tests, the programelements are entered into the Computer Program Library where they are subjectedto configuration control procedures. Controlled program elements are compiled/assembled, link-edited and the current CPCI version is made available forintegration testing. Integration tests are dynamic tests designed to verifyprogram functions and interfaces between program elements and with the database. The result is a complete CPCI for which all design features have beenverified.

The integration of program elements or tasks into the compiete computer pro-gram shall be accomplished in a top-down sequence. The highest level elementswhich contain the highest level controller tasks shall be tested and integratedfirst. These tasks are the Master Sequencer, Configurator, Request Processor,and Subsystem Status Monitor. Testing and integration shall proceed down thehierarchy until all program elements (e.g., equipment interface functions),have been integrated and the design completely verified.

An important aspect of integration testing of IDAMST will be the invocationand synchronization of the tasks, since these functions do not fall under thestructured programming rules.

4.2.3 Formal Software Testing

The purpose of formal testing is to confirm that the computer program performs

the functions and satisfies the performance requirement contained in the soft-ware requirements specification. Formal testing consists of PreliminaryQualification Tests (PQT) and Formal Qualification Tests (FQT), and are con-ducted in accordance with Air Force approved test plans.

Pre-Qualification Testinq (PQT)

PQT is an incremental process which provides visibility and control of theCPC development during the time period between the Critical Design Reviewand Formal Qualification Testing.

PQT consists of functional level tests, conducted at the development facility,and using Air Force approved test plans. These tests will use documented pro-cedures, completed by the contractor, and submitted to the Air Force Sufficient-ly in advance of the scheduled test session to permit review and analysis.They will typically use cootrolled inputs specifically prepared for the testpurpose.

A Pre-Qualification test will generally be conducted for each CPCI function.If a test's cost or time consumption estimates are significantly high, thetest will be deferred to FQT unless it is time-critical or performance-criticalto the development of the CPCI.

14U

Page 153: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

5.0 PREPARATION FOR DELIVERY

Not applicable.

141

Page 154: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

6.0 NOTES

6.1 Growth Items

The specified growth items were evaluated and the impact to the IDAMST con-figuration was assessed.

6.1.1 Joint Tactical Information Distribution System (JTIDS)

The Joint Tactical Information Distribution System (JTIDS) is a digital,secure, jam-resistant, communication system for real-time command and controlof combat operations. JTIDS is planned to interconnect the tactical and airdefense elements of all services, including surface and airborne command,control, surveillance and intelligence centers, Navy ships and combat andsupport aircraft. JTIDS will provide a high degree of interoperability bet-ween data collection elements, combat elements and command and control centerswithin a military theater of operations. Precise signal time-of-arrivalmeasurements, coupled with the transmission of emitter location, are used togenerate a common grid coordinate system containing the location of all activenet participants. The system uses Time Division Multiple Access (TDMA) tointerconnect all system users into one common channel, or network, for distri-

rbution of information. Each authorized network element is allocated a dynamicnumber of transmit time slots within the network reporting cycle as needed forits mission. When not transmitting, each element monitors the transmissionsof the other elements and extracts the information as needed. Since the sys-tem is nodeless, survivability is enhanced and the system exists as long astwo or more elements exist.

The basic JTIDS system for any aircraft will receive, process and display in-formation to the crew and collect, convert and format its own data for broad-cast distribution to the net. The baseline JTIDS functions are shown inFigure 6.1-1.

As can be seen from Figure 6.1-1, the two obvious major categories are trans-mit and receive. Common to both of these functions are the elements of voice,relative navigation and Built-in-Test (BIT). A brief description of the re-maining functional elements is contained in the following sections:

Transmit Manual: These are the functions that would require pilot actions inorder to initiate transmission. Throughout this study, the functions underthis category were deliberately limited due to the constraint of a two-mancrew. The only two arcas recommended are:

o Mission Words - These elements are to provide key transmissions tocommand and control agencies. The messages would concern essentialmission decisions.

o Weather - This element would allow PIREPS from targets or criticalrendezvous areas. The pilot would only initiate inputs for visibility,cloud cover and cloud height. The other elements under this functionwould automatically be formatted from the navigation computer.

142

Page 155: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

U21L. 10611W

19*1m uopllm TINll )

-so (out M) a All-11111 AM- I1 a

fa Aim M aT1la

mm ".m 411111111.

WTI"GUR 6.1-1m-1

L sum1"3Palm MaA4

Page 156: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

Transmit Automatic: These are the functions that would be transmitted auto-matically as long as the system is operating. The major elements are:

o Radar (Air Target) - This transmission would provide the net informa-tion on a heretofore unknown hostile aircraft. The message would besent only after the pilot has locked-on an airborne target that is notbeing reported on the JTIDS network.

o RHAW - Any RHAW threat received that does not correlate with the threatsignals being reported on the JTIDS net would constitute a new messageto be formatted and transmitted.

o Status - The Elements under this function would automatically be trans-mitted, either continuously or intermittently, as the situation dic-tates.

Receive Tracks: All hostile, unknown and friendly tracks and positions aregrouped under this major function. The elements would be received, stored andformatted for display upon pilot commands.

Receive Status: The functions in this category reflect formatted commandmessages and information concerning the status and weather of various areasof interest. These elements would also be received, stored and formatted fordisplay upon pilot commands.

Unformatted: This category is for received messages that are free text alpha-numeric and meet no structured format. The functional area of these messagescannot be categorized as they are unlimited as to content.

The JTIDS computational requirements were analyzed and assessed as follows:

Words

JTIDS Network Processing 4,250JTIDS Message Processing 2,925JTIDS Message Control 1,525JTIDS Self Test 1,200

Estimated throughpuL requirements = 110 KOPS.

It is recommended that the JTIDS function be implemented with a dedicated pro-cessor because of the computation requirements. Additionally, developmentalefforts and interface requirements would be reduced with a dedicated pro-cessor.

Assuming a dedicated processor in the JTIDS system, the impact of interfacingJTIDS with the IDAMST system as a growth item is as follows:

o Data link between JTIDS and IDAMST processors via the multiplexeddata bus.

o IMK and DEK functions will have to be expanded to include JTIDS manualdata entry functions.

144

r-

Page 157: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

o JTIDS display requirements will have to be incorporated into theIDAMST specified displays. Displays requirements fall within threecategories: 1) command data; 2) MAP data; and 3) miscellaneousmission data.

o IDAMST navigation subfunction will have to be modified to utilize therelative navigation capability of the JTIDS system. The accuracy ofJTIDS data will be dependent upon the accuracy of the transmittedposition and relative navigation calculation. The expected error ofthe JTIDS mechanization is expected to be insignificant; therefore,JTIDS relative navigation data may be used for updating if JTIDSstation positions are accurately known.

6.1.2 Terrain Following/Terrain Avoidance (TF/TA)

A limited TF/TA capability is reflected in the ground proximity warning systemmechanization which utilizes radar altimeter data and barometric altituderate. For a truly effective TF/TA system mechanization, a forward looking,TF/TA type radar is required to sense the terrain over which the airplane isexpected to fly. Assuming that some type of TF/TA radar would be installedto provide TF/TA capability, the following will be required to integrate TF/TA capability into the IDAMST configuration:

o TF/TA radar system control panel requirements have to be allocated toIMK functions or dedicated control panels.

o TF/TA radar display data would be interfaced with the digital scanconverter for formatting compatible with IDAMST CRT display devices.

o Interface between TF/TA radar and avionics system would include sta-bilization data to TF/TA radar, TF command data for input to theflight director command calculations for display.

o TF command data to the flight controls would be routed directly tothe flight control system to minimize data lag to enable close coup-ling with the flight control system.

145

Page 158: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

6.143 Global Positioning System (GPS)

The Global Positioning System (GPS) is a satellite navigation system currentlyin development by the Department of Defense. In its operational deployment,24 satellites wili be orbited at about 11,000 nautical miles to provide Earthcoverage for navigation and weapon delivery. At least six satellites will bein view from any location. The satellites will broadcast their identity,position, and highly accurate time. User equipment will select the four mostappropriate satellites and solve four equations in four unknowns to displayto the user his position in three dimensions and time.

It is presently anticipated that the GPS will be developed as a TACAN hard-ware replacement with installation and interface requirements to be compatiblewith the AN/ARN 118 TACAN set. The GPS system will be self-contained with adedicated processor in the GPS system. A dedicated processor will minimizeGPS developmental activities in individual applications by specifying a stand-ard computer interface. Integrating the GPS into the IDAMST configuration

* will have the following impact:

o GPS controls and status will have to be integrated into the IMK func-tions.

o Data link between GPS and IDAMST processors via the multiplexed databus. Hardware impact to be minimal if TACAN provisions are utilized.

o IDAMST naviqation subfunction will have to be modified to utilize theGPS data, position and velocity, in determining the aircraft position.The expected accuracy of 100 meters of the low cost GPS will increasethe operational capability of the IDAMST configuration.

o Advanced GPS concepts to provide higher anti-jam capability if re-quired, for the AMST airplane, will increase interface requirementsfor directional antenna and inertial reference information.

146

Page 159: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

10.0 APPENDIX I: HARDWARE/SOFTWARE SIGNAL LIST

The functional interface between avionics hardware and the mission softwareis defined in terms of a hardware/software interface. The hardware involvedin this interface is listed below:

Air/Ground SystemApproach Indicating SystemFire Warning SystemAutomatic Braking SystemFlight Surfaces Status SystemFuel Measurement SystemAvionics Power Control Logic SystemEngine TransducersMaster Caution SystemFlight Control/Avionics SubsystemsLong Range RadarRadar Altimeters

* Magnetic Compass* Inertial Navigation System

OMEGA Navigation System* Public Address Systemr HF/SSB Radio

VHF/FM RadioUHF/AM RadioIntercommunication SetUHF/AM RadioInstrument Landing SystemsLF ADFIntraformation Positioning Set (SKE)TACANUHF ADFInfrared Detection and Warning SystemFlares Dispenser UnitRadar Homing and Warning SystemIDAMST Controls and DisplaysIDAMST Core Elements

A detailed signal-by-signal printout for each hardware system is providedwith the following data available from each signal.

INPUT: Signals originating in the avionic hardware

OUTPUT: Signals originating in the mission software

SIG1NAL NAME: Brief description of signal

SIGID: Signal identification number - used for bookkeeping purposes

147

r

Page 160: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

TYPE: Characteristic of signal interface

01 single ended discrete02 differential discrete03 switch closure open/gnd04 switch closure open 28V05 single ended dc analog06 differential dc analog07 single ended ac analog08 differential ac analog09 synchro10 serial digital11 pulse converter18 resolver

VOLTAGE RANGE: The electrical voltage minimum and maximum

PARAMETER RANGE: The particular parameter characteristics minimum andmaximum

SCALE FACTOR: The parameter relation to the electrical range

RESOLUTION: The percent accuracy of the signal

QUANTIZATION: The number of bits to which the signal is resolved

U/R: The signal update rate is a per second quantity

B/R: The bit rate is the total number of bits per second

The hardware/software interfaces were obtained by examining each hardware unitand listing its characteristics when the following conditions were satisfied:

o Avionic hardware signals which interfaces with other avionic hardwarelocated in subsystems other than its own.

o Avionic hardware signals which interface with mission software.

o Mission software signals which interface with avionic hardware, in-cluding controls and displays.

148

Page 161: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

II

*1

- .4 - .-. -.

2 .4 CV .4 .4 .4 .4

a -

2

-C* 0

2,14 2

* 2 2

14- C,

~ 0 14C- U.

- 0

14 -3

74 II2

2 1.1U.4 0

14C,2

2

2

74

K

42 7*0.

C, C

* C C

0

Or ,~ 0.

C 4 7* - 77.

C C C' C' C C- C4. - 0.. C.. -

- iv - iv

.0 C C IU. 4* 7*

C' ~) C7 C' :' -,- t ~ 7

* it .-. , C, r

- S 4 , C C*4 .i -.7 *1

-. C.' V C' '*' 7.770 C it ,J .. .7

14~

Page 162: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

I.

.:,

. -o ,,

I- F

r nI 0 , , ,

-J

'150

Page 163: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

z -r -- -......

0|

0i

Q7 -

4

L,

I. C

* ftff

Lo C

.. . . ... . . . .. S S

L f - N . * |

Page 164: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

II

q 0

r -7

* .4

7 4'

LU

7 52

-- - m -,

Page 165: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

& N S S - -- * * S * - - - - * a1

'4. N NN N N NN N N

N NN N N N '

• a o

-

p .4

O. 4Y- 4 ' 4 -'4 4 .. ..4" S 4 4 D 4

- -' t O - -. ,4 C .4 .-' ' (4 44 44 . " 4 0 0 C 44 44

I ! 0 C 0 C' C C 4 C C 4 4 4 . C C 003 ' Cif -. ta C _ -

Page 166: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

* C

a

- a,?C C

. > u n un uua

Page 167: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

C ,= w 0c

-- - -o

155 ,

* . . ...... L

A C C . C C C t C) C C . II CII II I II II C- II . . . I[ II

Page 168: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

IX 0 0D 0 W 0 40 .0 W V 0 0 W 10 C 0 0 C C C

m

w 0 In 0 a 0 0 0

- - -- - - - - - - -C

0

a C.

a

iL

o 5

..9

* A C. N N ~ ' N 90 9 0 90 '0 90 90 9~ 9 9 9 90 0 09 09 '0569

Page 169: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

l

S.

0

* ~I.

a

- .

Page 170: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

2~ .. "I * . . . . . . . . - - -

0

44

0v

1.4.

415

Page 171: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

14

w

u

.7

C

44

m i

D. m

v

2 .- g

159

Page 172: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

j7

W o W 0 AD 0 0 CD eN .0 0 0 0 10 40 Q o o 0 0 0 0 0 0 0 0 0 El 0

ca

f 0 0 0 0 0 0 El 0 0 0 0 0 0 0 - 0 0 0 D 0 0 0 0 0 0 a a a

. -w ,4 ,; .4 .4.4i.' 4 .- -.- - - 4 - - -

C -

in

aa

4r,

jk

,.NC a,.J . .J .j_ .J

o C-

a.

UNJ

LI C - ' NC N'- - C N'. U' - U' I 16 0 ' . I C- O .4 I I P- U - 0) 4

Page 173: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

- - -

--

161 "

01 i

Page 174: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

.

i, Li

'r f:

Z 1

iiiii. i-i i II

Page 175: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

IL

-i - C- N- C- N- - -' -0 - -n - -' - - - - -. - - - - . - - - -'

Jr ~ ~ ~ ~ ~ ~ ~ 0 ClN , N a J a' N ( L ' a

al L i ~ ' ' ' ' ' f 0 a V 0

'- I N a ' a ' a

v I ~c'. a a a -163

Page 176: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

'3

o L,

43Lc

3':

C

C .

a8

!3.3

Page 177: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

-II.

(C - (C

* C'

,

.

*4

L+''

a-,, , , , + ,. , -

( " ? 4 - s , a- C . . . ..-

OC a- - a-a

65 "'

4. A3 CC 0' , Ci C C' .7 3 C ' Ci

C - ' - C 'C C C - C C' ' C -, 4 ' C C - C' ' I

Page 178: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

-

:2

a

c 0

-.. J

Page 179: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

~~ N N 0 0II, 0 0 0 0 0 0 N ' NN ?N, N0000000AD- - tIt Kt) , it )) ) "a ,t . .

it N N 0 0 0 0 .0 0 N N N N N N N N N N N 0 .0 10 000

N , i, it t t t t .

C- In)

C a- a a) - ait) * 4) 4) a

t aeat t

& Z -N * 00 0

a a- It

:t i167

Page 180: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

-I,

~ C N N C C C- * N N *1) *

& N N N C C 4'

D

2 74.4-4.4 a

7a

4 21

Cii,

r -21 0a. a34 ~

IL

C0'

a-

0.

C

23 Li

4.4 *J- 00' 0'C

> 4,0' -- t- 4, ~' 0'

C 0' 7' N 4 o *0'- ,'. N 44, 43 41 N

I 4-'. 4-) 4-' C' C '4I'a I '-. 4 A

'i0

168

Page 181: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

+r -- . . .]. . .. . C, . . . . . ..0. . . .= . . .. . -L _ - ., .. . . ... . . -N 4 4•

4 4 4

I

N V~ ~12 C C

C C C

0m

Cm

ai- C

S-

o .4

-J -!

0.

.1 t

- }, C- _--

- 0

.. 6

+ r=1w

Page 182: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

I.

4 0 0 C" N F--. '~ S S * * S S N N N N N N C 'aN , ,_ -- - --- 'C' N ~ F' F~ C~ ~ s- a-

N ~

S e.~ F-.j CN~ c~ CLi N j- ~ * S * * (C) N N N N N C *N NN~rr'~N-) *C' F) a' F- ~.,

2 a a ~C fl oC 'Cr '0 - - -*

* 0)'0 4 - N 4 N 4 4 a a- 2 z -: 2 2 2 2 2 2

C C

0~ -a C, Lia a.

CI N CC N 114 I L Li N7 0 C CC 4 7 7' 7Li&t44L0L Na-NCa N a a' N aN a C a>00 ONONON.

0

S

a: C4 4 N N 4 4 4 < 4 a a 4a 2 2 2 2 2 2 a-

o oN - a a

- Ci C N Li Li '0 Li LiC C' Fl N C) C' C C 4C C' N N N N NC' 4 4 Li Li Li -.- 0 Cl N C' Li4 X Li C. C Ci C C a C ~*, C' C. (, ~j'N N N N N N 4

2 LiN C' N N N C) -fl 2 C~ 2-C' C 0 -

* C- 0 a. a N a a -----

* -. 0 C Li C N C C. a. '0 '0 '0 '-C 0* C

a S a a aC.

C, c N C'

4 1 0 ~

O"Li0NCr N N "1 F-C .-C .-C S S S C CC 5-

C N -, S C 4 F- C) C~ .5 N Q' C- N C- S N N S N4 'C 4 4 '0 2 a F-) N N (C F-- S

- *' N *~C - S 1) *-~ -L~ N N N. N N N C'. N. C'. N. -' 'N N N N N

C- - ~- C a' C- C- a-C' N C- Li C.' - I

C- - - ,,, F-* C:

- I I *- .- I 0-. ---) 4 . -4 - . -Z -,C., - --------- I- - -- N N C- IC -'

'S Cl F- 7 CC) .. Ul4'.- IC 1 N* -, C- -' N N 'Li -~) Ci 'A ,-n 4

170

Page 183: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

* I -,4 , -

o

,)

Sl

...

a C

a C ,)

- -

,-.i C - o-

a - 7 -. 'C' .

171 ~ ' '> C'

Page 184: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

4

a a

N

C, ; - .- 4-,,o '-; .. . 4 . ..

Li C72

I- C I I-

Page 185: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

07. - - . .

> )

In)W

C) CL CL Li ci L

1 1

~173

Page 186: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

7 -,

. 0

L C

C Cr

r --

s. 04C CC

CC li7t

Page 187: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

a - .. o-

- - -a

Lit

z

- 0

o Li

CI'

U

: In

Page 188: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

0j c0 . 0 . 0 . 0 MC 0 .0

C~ C, In -, .4 .

V5 4 0 4 . 4 C 0 N N .

N L44 .4 .

2 ~ ~ ~ ~ ~ C C 4 * * 4 S - N 4 .

C~ ~ -1 4 4 0 4

e4

17

Page 189: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

2 C N N0 2

16

- N

ar

u

0w C

I.,

it a

A- 0

177 "

Page 190: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

*1>0 S S

C 41

0 N N

3 Aj NC C~ C'

a

a

04,U'0

0. 07 -

-J

4,

4-. 5.C7

r

0.

C

0

4. 4..

01

2~0

4- 54

ID 4- *1

3 44 vs a

o .- '2 '4Us O~

178

Page 191: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

;fl

C -

a

0

• -* 79

Page 192: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

I

C,180

Page 193: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

U N N N N N N N N N N N N N N N N N N N N N N y N, IV f.

of N N N N N N N N N N N N N

ot

ti to t oto$ o .1 I 1

Li w , L o w L

0. Ca C. a -a a a. a. aCa a a aL a. a a a_ a0 aII 0 0 C 0 0 0 0 0 0 0 0 0 0 0 0 N 0 0 0 0

-1 it 11 1 I 1 1 o t 1

ID 0D a z r a a o a a 0 0 0 0 0 0 b 0 9 C oL

to 13 1 1 C ZC - L, Z3* 1 3 13 1 3 1 3 13 C 1 1, 3 13 1

LII

118

Page 194: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

* a-g

p at,

-a

a

Li i- C

Li Li,_N

a- C C *- C- l

N i i a': "

Page 195: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

FPAD-AO83 113 BOE ING AEROSPACE CO SEATTLE WA BOEING MILITARY AIRPL-;ETC F/6 /

COMPUTER PROGRAM DEVELOPMENT SPECIFICATION FOR IDAMST OERATION- ETCU

NOV 76 F33615 76-C-1G99

UNCLASSIFI1ED SPEC-SB-4042 AFAL-TR-76-2GB ADD 2 NL3 hhhhh.

-E[7hhEEE

Page 196: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

= xw- -. - .4 - - 9* -j .4 .4 .4 - 314

w Iu( u0uI

r w411 2 4l Z I 2 C 2a 2. 2. 27 (1 z & -, 2 22 2.

)LO C 00. 4

I u I . ' - ~ A - A . . - Ar a~ u U U U L 54 54 1 U 54 I0z . i L . i Li L . i 54 L i L

4 5 ~ L Li f~f Li U L L 4 I 4 i U L

61 2 z 2 2 . z5 zs fz I z 2 z z 2IH 25 2 zto Lil :.) z D Z) n n = = Z) z :) m =iO~.1 c24 a c4Z 24O4 424oc2424242424295 0. O4 4 5 2D 5 3 51 C 02 5 C O D W It

ce'a' c c ct 3 4- 6 o 0 p t D u

ty L, t ai r w w cQ )0 0 0 a

0 c 1 .ll ol 4 . Ix . a- 0. . lL CL 01. It 0 C

V. In In t"' 1. m ~ InC C ) C C C f C )

4 4

*~ v f C C C l 0 0 C 0 0 I

o -.4 .4 .4 4 .4 .4 u.4 IV .4 . 4 . 4 . 4 .

4

r 0 C5. V, V- V- - V.

1. ) 40 . ; C w w. v. L0 0s x

S . .4 .4 4 ' .4 '4 . 5) . '4 5ff '4 4183 A

Page 197: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

4 N 4 y em N y N 4 N 4 N N j N II y N N N N I" IV if N " N 4 ft i " C4

C tv m N Y N y N N N N fm N Nm N N N N N N N ft if Nf i

CL

a

40 C4. IVIM- 'C

In ttI V

184

Page 198: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

4 * f~t. p

U E~i S

S

£ ftO

2 - -

4

0

ft 0

*-j0

hi

4 UI-

U0. 0U S.-- U

4S..

I..-J4US

hi

74U

UhiI-Li5.

C.

0a0

hiin 0C Li

a- Li .5 5hi 5, 0. ftift 4 0

- '. U~ .-j C., I~o e~ .~ 0.- , 0 0

4

C. ~ -~2 5-~ -&So 0 ~ -)Li ft t

s~ 0 0hi ** * *5-

5t it, -,

p

K-J ~

- *~, S

* *C C- 0

C, .* S -C, C.

.5 5* 4Ci 5 ft

75 .- 1.3 iii IA U- 5 i

CC IA

185

Page 199: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

IIa

w

C

41 .

c aU C 1

a n 4l.l t

m A I

lc- 1a aU

'186

Page 200: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

...... ......

W)

w .4 14 -Ir. 10 a n-

-I

4

4-1

C to

13 o

Page 201: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

4. A

£

4 0 6

* -

q 0g

-.-€,

0 U f ¢

4lS.8

Page 202: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

for 0 v 0 c 0 C S Q c 0 c 0Q Pc aV cd P d P 4 P d P

0 0' 0' ' a' a' 0' 0' 0' 0 a

0' a' ' a' a' 0' ai 0' a

az z - .z .5 z4 - z z .S - - u S - u 5 u S ' p 4 - 4 - p 4

z 4 - . . P 4 .

IL

IL 1It 1 A z 9 z z z z z0

vs w W . ) J WW- W Ww w 4

a. In -n Ci In -1 Wb q - '1 a .9 x . a Cv 1& .0 I C- n I

4A 00 00 v 0 0 0 0 s v & a 0 a 0 0

. 0 c. a wC a I0 0 a00 0 0 Q 6.

K

.18

Page 203: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

It on 0" 33 N N 43

61N N N 0 N N N ~ 0

of of It 11 toN 0 4

z z 2 z z z 3

0a

N 0

a 30 3 0 30 30 a

It.

N( 3.

OU 0., C

A19

Page 204: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

'A6j

a d C d C ~ d d C d C d C

Ar - c - 0-- - - - Cof I 1 I 1 of i 1 1 1 1

q La

a . 0 C

4 - 2 0 2 0 z 2 z 2O 2 z 211 Li Li LI L i L i L i L i

cll o 0 t o - C) .4

w1 I S N I I I I I I I I S

L

10

I.L i

& & (. & 0

z c zz zzo 0 0

0) I 0a W ) 0 m W

00 0.0m4 D

-9 R 6 C C

-aW O - J " "w A

fo wLNJ of , N I t, I

N 1.3

a.191

Page 205: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

4 "4.

--0

45

hi'

- Li

Page 206: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

S ~ ~~~~ It 11 .4 1 l i 4 - - - . 0 c 4 N N N Nit% is of

2rz zzoj La .4 W4 >4 >4 .4 w4 w4 .4 . 4 - . 4 - - . w N

ILC. CL 0 0 0 nC

*~ ~ 0 .4 11 %4 % .4 a4 .4 . 4 . 4 . 4 . 4 - 4 . 4 . 4 . 4 -% % .40 0 4

z 4

a .4

% C I II I iC

. 0 If s u u ui u i 0 uI ui u

4 0 0 a 0 .44 0 0 0>. > w. or mn wn 0 in0 0 a 0 0 0. 0.

inn urn nr L) Vrn on I+ + + + ) + C) C' C 0 0

In m 4 W) n4 In W) wo 01 In on In 'oI In

Lo i I " . 1, t WC V M, W

1- V

C2j

m Li 1 s L-j0

0 z c .Sil W -w Z:l n4

C3 c l : 2

4 5 4-. 4 C.

192

Page 207: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

14

II0, C, it4

-1 it 4

0

0. C

4194

Page 208: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

a

.j C . 4 . 4 - . . 4 . 4 46 . 4 . . 4 . '4%

-

N4 0 1 o

10 1.-1o 1 19u u u uis i 1 If 1 t i

z z

%a 4 D0a-D 0 0 aI

* .4 4 .4 .4 . - .

or4 . 4 4 4 4 4 4 4 . ( . C (r C 4 U U U U U 4 B 4 44 44 4 4

- C C) :3a u 0 w w v uIof Z. le 44 Z, a: C, 44* 0 4I4,C

0. '4% a0 -a v -6 06 In 0.. S N

.4 M IL 0, m C C C CCIL 4 4 0 44 a a 0 0a 0 0 0 0 0 0 0 9 44 40

44.

C.A w n m mS

cc

a4 0 - 1

In a.- 2 1 1 . wcCX4 (L

(A J4 4.4I C y ) -i a 0 C

195

Page 209: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

4 NN NN NN NN NN IN N m N N N N N N N N N N N N N

I -- 44 - . -. .4 . . . . . . . . .

atJ 0 c c ac c 0 a a 4 c 0 a 0 a c1-

v La 10 0 00 a 0 C3 40 0 1-1 a40 44 0 04 40 40 0 z z z .

I N N N N .0 If, 9 N N N 0 0 In N In N N n A N % 4

It 4 It 1 4 46 It I 44 Li 0 It 1 I t to 11 I t It If 01 1 04 1. it u4 L i 4 ul C, 0 c) 0 c ) ) a C) ) 0 a C, C) c c c 0 Cl c 0 0 0 c Ci 0 0

u 2 2 z z z z z z = z 4 2 2 :T 2 2 z 2 2 2444 lb 444 0 4 1.4 444 14 4 42 1.4 42 4.4 42 .2 2 144 44 44 44 4 42 4.5 40 44 0 In

44

cc4

19

4 t0 ,0 r Q c

0 4

N 0 0aa

444, z l' 2 1 0 c a. 2 0 2 t- 0 2l 2

o~1 u ,L ~CC5' 40 40 444 40 40 U to U ~C1 U o t o t o 0 4 0 4 0

4- L- C. 1 ItC ) C C 2 2 2 2 2 2 C C C1.0 .l 2 4- - 4- 4 - 4. 4. 4- - po~~~~~~~~ Q3 44 ) 4 0 40 4 0 4 0 0 4 n 4

a 2 4. 4 4 C 0 44 4 4 * 44 44 44 44 * 4 4 4 4 4 4 1960

Page 210: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

I£ Pd Pd P4 Pd Pd

- - lii WI 10* - - WI iS

£ , 'C Pd Pd Pd- - WI WI

* C. P.. - - -4 - -

a

8C

S S.

0Uhi

p..

ft £* I- 0

~ I-O Li

4I,.

-i4UWI

Li157

4 8W' LI'a P.-i LI* 8

2' 4ft U4 .05. 82

0 LIWI LI

I,U, 7., 4

O LII,

- 4S..

o 0C.

LI0- C. - - WI .0 .0- ,. - -4 P.KUo 0 .0 S.. WI WII.. -. WI 4 10 Wi -~ 'I'.4 e 0 0 CI C CK C, C) CI CI WI

VI $ K * S K

ft

ftI- I- ~

o a -

p ft .~ .. N.

* LI 4 LI LIft K - LI -~.4 0 .1 ~J.W 0 I.. 0 ii U.2 - *~ S. LI U'

V C' 0 . tI II (.1- 7 4 LIWI ft U 10 4 P.

197

-C-

Page 211: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

2 - - - *

U) 0

K -. *4 ~-S

2 - - - *4 (II

0

5 2a*

a10Li

rI-

KQ. 02 I~- U

4

10

LU24K

KLi

K

Li1~7 'I.U) InK I

LI 4I~ *

* II- ~ $4- .J - .4I CI2 > C'2

-. Li.4 WI -,- a

* ~-* *. 4 - 1$* - -~ ~I -

~ C. C' C C4 - .h 4 4 ~I'LI LA * S I S

Z1V -

'9 IU J

.1 *4 L~'4 I.' II I WI

4 119 19 CS .3 Li *.. -.

.4C - 'I

LA I'

9- *- 1 CIK Li C

'198

Page 212: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

£ if if

Si 0 0

£ 4 4% - -

~ if if00

30

-Iq 0

Shi

* £

I.

~ S- 0~o U

4

hi-I40U

hi

24S

Shi

S

S

A.

* hi

a,

hi U Li', C C

4 4 ~

- -J a, a,* 0 S S

S

2 ~ 0 0* S- - -

* ~ p.. 5

2 '~ ~. 04 - .~ .0Li 50 4 9

-J -J

4 00 0

* 4 7

* 7 Li hi

7 0 .5

- hi hi

*55 5-5- '399

- *~ .

Page 213: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

14 44 6 6 0 6 .0S.

* - * a a * * -* -C - - .4 - - .4

0

C,

o-JU,wa

~ aL 0I I

4CL,

I4

a

V. C.9- 1

*24 C.4 a

4

aW 1.1

0 CC C~.4

C. CL

.4 LI

CC CC'

U ~i

C.C 0

C,

LI a 4. 0. .4 .4 .4~ 0 C'

c C- .4 9- 0, C~ 4.C. 01 .4 .4 * I'

- lb C.. 4. 0 0. 0 C 0* -. p.. p. 9- 9. - 9- 9.

14 .4 9 1 * * p 0

-r 7 C N LI4. .4

4 0 Ca o 4-

fl C. 1 4 1 r -

IA A 1) CA V CL

- C. .4 4. 4- .4 p. -)

200

Page 214: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

U Cd Cd

4

U U Cd

N0

04

qU

I-

a. s4 S. 0

~ 5-a U

4hi.

-J4'4

.4U

U5~N4U

UUC-U

C. K* 4

ii.o 44 C.

24

UU U Ua ~ C

0 7 7 ~

ii. U C

2 '4 4o ~- 4 ~.,I- 5- L~U -~ ~~.J 4,

C

U 4. J J

4

o a 5 WI- - c~ 04

44 C4 - F. C.

U

I.

- 44

aC ~ ~

* 0. -

* 4. 4-F, U

.3 -4 . .4* U .~

-4- .4 ~ U S

201

Page 215: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

a,.0 t

A 0

cc0

2 7

or0

16.~

Page 216: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

to 4. c 41 V

0 4 0 0 L

W- - - w

u z CL za0 z V- wa 0

3Z2Li 0 0 I0 i0lI

L 000 030 Oi0 C,

2~~~ ~~ 32C)5. 0. m m

.2203

Page 217: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

cr .0 10 In In mi W

01 It lt it ItI

1 0 1 0 in C0 P0 1 N N N

It Vi Vt B

0 ~ . - > > , > 4 - I

"a

ri 0

20

Page 218: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

J a ,

a>

C

61

9L

6 0

z0 a

P~~9 1 - 0 0

,

Si II

mc

i | I 2I 5

-J 0 0o- o

U , C C

Li EUN-

U

' 205 I2q

Page 219: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

it 1

c i

_j

f- 0 a

mI No IIo

a.

o ~~ Vcm (i Ci i i

4A'

i20

Page 220: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

II-. 0 0 f

-j a 0 0ti

CL

hi

91

a20

Page 221: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

- - - -

61

> m~ a 4i 6C w (LCC CL M 0 m M a. CL a. . a. M V) :3 D = m

C, Z. 2 L a a Z 7 C. 2 Z 2 0 Z Q 0 0 0 ccCL C 04 0 a lc w4 =. m x 4 I C 1 .. la 1.

4~~~ 0. 14 1 0 0 f 0 0 c. 0 0 0 wl 0 0

0. 0 a, a, z 0 0 4 2

u .- 0 C, c Q 0 0 0 1 0 0 0 0 0

D 7) 0 m D 2 2 z0 0 c C w 0 'C a 0 0 0 0 61

0 0 C1 0 0 0 0 0 u 0 C 0 C m W 0 0 C 0

Cli 0 C I. in , ~ 0 0 10 0 O 0 I~0 CI 0 1 0 0 0 0 0 0a

Co C .-cT I

0 a

20

Page 222: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

cc 4 4 'A 4

C,

61

L2

* 0nor

0. 0r) Wr a- ne

.20

Page 223: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

I

M IL CLc a

2 2

LL u

II.

1210

Page 224: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

i if of z .

4a 0 LO

61

ta

In 0

* 211

Page 225: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

I

1C 0 0 0 .~I 0 0 0 0 0 0 0 0 0 0 0 0'. 0 C N 112 4 N C 0 N N02 - - - -

C 0 0 0 0 .4 0 0' 0 0 0 0 0 0 0 0 0

2 - - .0 - - .4 .4 .4 %0 .4 = - I' - .4 -O II - ..I .4 .4 .4 .4 .1 *.4 ..I

0

20

oIn1.2C

a4 C a

- 0~ -o *.I

-j412 1U'

1.2

7

C

- LIIII *!'

4 I~O .4LI -

II ~J

C C. 41 .4 0 LI Ifl 0 .4 4) .4 0 0 0 .4 .4 .4)

0 UN .4 .4 0. 01 ~ N 111 0 .4 4~ C U' C .4 09 CC N I~ N .4 .4 Ia IN #2 .4C C Cl C. C~ C C C Cj 0 C C a. .4, C LI S C

'A. C 21 11 21 12 2~ .4 .4 10 N *C .4 .4

Cl IN 21.4012

Cl C)'4 ~ U C. LI C LI

* 1- - , VI IN 0 4) It,S ., -~ a a. .' - *- 1.2

- '4 *. I, .2 .1 ~ IA. IL IL IL IL

III .4 .4 L 4 *t 211 .4 1.1 L.L ..1 l.A

212

a'-..

Page 226: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

..

28 .4 it .0 It It 0 4z

li w L w t

0

-j0 f 1 1 t 1 f i

IL

M.a a a a Q. C- CL m m.

~ 0 0 0 0 0 0 0

U z 2 2 z Z! z 2

21

41

Page 227: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

IIIDI

Li w 4 0 0 6 4 0 4 4 C

11

13S A 4

44rE

4 L

C35

x I > 04

0

sr CC c e

LIn

2214

Page 228: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

I- * * * * * * * * * * * * * * a a a a a a a a a a a a a a

U

K 0 0 0 0 a a a a a a a a a a a a a a a a a a a 40 U * C U*1~

* - - .~ .4 - - - .4 - - .4 - - .4 .4 CI r4 .4 .4 .4 .4 .4 .4 .4 - .4 .4 -

0

.40

-I0

A IAhi

4 P.

0.0a ~-4 LI

4

hi-J4UIn

4.1

3.4IC

KLi4-4.,

4

4

C

146 43

2

.4

44Lb4

- .2

K0

.4 14C. .4 vi .4 .4 .4 .4 .4 .4 .4 .4 .4 - .4 .4 .4 .4 .4 .4 .4 .4 .4 .4 .4 .4 .4 CI - .4

44 IoICC

Cl *1 .4 4 IV .4 .4 49 4- IV VI .4 49 4. IV' - .4 .4 4- .4 .4 49 hi F. 49 - .4 .4 4.C. .4 49 .4 .4 .4 .4 ID ID III U'- 4. 4. 4- 4- 49 49 144 a 0' .4 49 SI 01 .4 .4 .4 .4

114 43 .4 Cl C C~ C C CI 0 Ci C Cl 0 0 0 .41 0 0 3 0 0 C Cl .4 .4 .4 .4 - -* C. 14'. .4 .4 .4 49 CI .4 49 IV, 49 .4 .4 .4 .4 .4 vl 49 .4 49 49 .4 .4 vi .4 .4 .4 49 IV.4--------.4 - .4 .4 .4

.4 .4 4 0 0 .4 4 4 0 .1 CI 4 0 0 4 Cl .4 4 0 CI 4 .4 C' .0 4. a aS 3 4~ .4 - .4 .4 - CI 3 .4 .4 .4

LI LI - LI 441 (14 LI Li LI LI II. Li 141 IV LI 4)4 14 LI CV 49 44 CI .4LI .4

.4 U 44 U 4 4 LI 14 Li .4 U 4 U .4 4 LI .4 4 LI 4 4 Li .4 .4 .2 .4 4 4

IC 4. 14 4. 4- 1, 1. .. I~ 4.- LI

* .4 .4 LI Ii Ci 4.1 4143 Cl LI II Ci LI II 41 414144 (1 44 1.1 42 41 41 44 Li CIl - - I, A fl A 41 C 49 II C A 14 VI A fl II .4 A II - C 11 A a a n

.4 43 CI - 4 £ IC S .4 49 .4 .4 .4. 49 .4 .4 .4 3 .4. .4 IV 4 49 IC .14 .4 3 .44 Il 4.9 41 4) 41 49 49 149 LI

.4 14 4 Li - LI - .. - 41 .. C ~4 Li Li .L IL iC U LI LI LI LI Li CI 49* 1) 4. Ci C - - *l .4 I- I C A 0 - CI C - Cl 13 - C) Ii C' 41 4.1

-. -- 49 C v> 4 4 .4 .4 S 49 49 . 49IV C I 1 1 1 t I 1Cl .4 CV C) C Cl .4 0 CC CC 6' 1~ C) C. 0 C' C C) .3 C .4 Cl C 141 39 .4, .4 49 -

4.1 .4 CV 414 III .4 CI C) .4 .4 CI .4 .4 .4 .4 .4 .4 .4 44 441 144 CI .4 141 114 Ci .4

215

.4..

Page 229: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

4* 4* -D D* 4 .0 4* 4 40 0 .0 4* 40 * .0 .0 4* a* a* D* 4* 4* 4* go

z~~- - -- -4 -4 -4 - - - - - -

In .

*C )V u i

In 4, I

IV I V t

It N, I

4 21.

Page 230: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

.

* n ~~~- - - - - - -f4. - - 4 .- -

CL

W

6A

hiiUv

5217

Page 231: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

.r o

a f

* I 4

20

01

Page 232: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

II

* .4 .4 .4 .4 - .4 .4 .4 - .4 .4 .4 .4 .4 .4 - .4 .4 .4 .4 - .4 Cd.4 - .) Cd

41

U .4 .4 .4 .4 .4 .4 .4 .4 .4 .4 - .4 .4 .4 .4 .4 .4 .4 .4 .4 .4 .4 .4 .4 .4 .4 - Cd

2 .4 .4 - . .4 .4 . 4 .4 .4 .4 .4 .4 .4 .1 - .4 .4 - .4 .4 .441 - - .4 -

a

20

4 .4C-U4.1U

4 I-

ft UC- 0~ -o 4.)

'4.

a41U.4

U

4.1U

if

'ifP

41.4 .-4 ft U- C--. ~' C P

- 1 * ~I * 41 0

'I C C-. 4 C' 4 0C- p

.4 a. -~ 4 C, ICC CC CC -~ Cl ~ ~ ) '~) ~ ~ C' 4 41 0 CC CC CC 4 0 .4 'IC CC ft

C. -PC.

C. 0' IC - A. tC~ ICC 0 a .C (S ICC S Ifl 4 CC C C- 0. .0 C N 41 Cl 04CC CC C C---------------------04 N -

CA 3 CC C C' C. C C' C.. CC CC CI C C' 4.. Cl 4.. 44 C C' C CS IC 0 CC IC, C C' 0 CC*----------C-'----------C S * S * * S S S S S S *

. ..I -J .4 4.1

C C. I 'C C. A 'C 4 I C V 4 4 C., 4 C' '.1 IC 4 LI 4CC 0 IC) 1. 44 CC C if - ~.C if - 1.1 CC

C - ICC . CC .1 CS C- , Li I/C - CC C4 CC' .4- IC IC C "C 'C C 4 C IC

*IC .' IC C a C '-'I .1 C ..C. . . . - *I - ..* 'C IC~ 4~ *~ -4 C' IC -, I 13 -C C.) C. CC . 5 44 L~ .4 4 ~. C

-, C C C CC. . . C - 'C C'C I' IC .~ - C'- .1 .4 C 4 .4 .4 '- - - - - - - - '4 C. N 0 0. .4

C, IC C - 4 *C IC* CI C..C. 1.4 ..C CC IC' .IA 4 -4 .4 4 4 Cl -.... 144-.S.4-.I A ..

219

IC-

Page 233: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

1ft N CCC N N N N N N N o o C C 0 0 C C 0 0 C C C 0 C C C C CN CCC N N N N N N CC. N ft ft ft C C C CftC

r N N N N N N N N N n ~ C 0 0 C C C 0 0 0 C C C C C C C CN

ft 0 0 .'C - - - - - - -

a

0

C

ft

a a- CC2 C-

a u IftCC

L IK

CC ft C C C C-ft CC C. ft C' -' ft

~ ft * ft C CCCC- CC- a ft ft C) C CC' C ftPC - CC JC JC

- .j a U * - - C C N N C~

* CC C. C C. C C

- C) CC. Ct ft ft C ft CCC ft ft PC CC ft CCC ft 0 CCC

ft I S P C - S N - N .. C. 'P CC -' N * CCC C CCC C~ * CO ft CC N g- N - C * C) C CCC- C-C C C~CC 0 0 ft N N N

C C- CC C C C ' 0C.,C~CC-CC'CCC-.C.C C C C- CC CC C CI .' C - C A 'C . ' C. C. PC ft PC ft PC

- * CCC CCC N

o C C

C 'C C~ CC CC' CC' CCC CCC 'CC CA C-' CA CCCC *-, - .-. CC C C A ft C C P N C C N

PC .' - - A - - C-ft - CC C I S4CCCCCICCCCCC C C

C C' C -, C- -' . ' C/C CC) C -CC C/C CC' CCC ft CA CA CA 0)

CC C ' - - CC C - CC CC I CC C) CC 'C CL CC C) 0 a- -. C- A p C C . C t'C C C J CCC 'C' ft CC

220

Page 234: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

I

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

0

K 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 .4 0 0 0 0 0 0 0 0

2 - .4 - ~4 - - - - .4 - .4 .4 .4 PC .4 - .4 .4 .4 .4 .4 .4

a

I

0

4-

-J0.4

K

a-

a. ~

o U

I'

I-

.4U.4

.4

.4K

K

'-4K

K

4.4

wK

4.~

0K U0.444, 4.44.3 4 44, .4 44 .4 444 441 .4 144 .4 V4 40 .4 '0 "4 ~4 144 .4 '4 44 40 .4 40 .4 4 .4 4 .4 .4o 4.-

Ka o .4' 0 0 N * .4' a C. N S .4, 54 .4 N S ~44.4 C 444 N 44 .0 444 4-' 44 4,4 .0 0 C4- '.4 40 4> .4 .4 .4 .4 .4 0 0 44 44 44 442 4(4 444. (4 .,U n4 .4' .444 .44 4.444 0 (2 C C- C 4. C 'C C. C 4. C.' C. C 4. C 42 4-4 C. C. C 4- 0 C. 0 0 0f0 4 0 'p 4 V n 4 0 V 444 44, 4', C; 444 -, 4n. 42 424 V 14. 40 .4 40 444 142 .4 4.4 .4 .4 .4

C.

.4 .4 444- ... N 44' 0 0 C) 0 C 0 0 44 C C'

.44 .4 .4.4.4.4.44.4.4 .4 .4 * ,.4 .4 - 42. 01 .4. N 4.4 N ('4 424 N 0. 444 N 444 N

V .4 44 44 ~4 Zn 424 24 nO '44 C. 4 24 01- - .n 4- - - S .- .2 -, - 4- C

4. in 444 4.44 4-4454 4- -- C -C .4 -.- *44 LA 44~ .4. 42 44 444 24 144 (C 04 4,4' I'S - - 4.- A A 01 424 44, 01 4.- ... - - -

44 4444 .4 4.) 4.4 4-4 4,4 4.4 4-4 nn 4-, .. 4' 44 44 .4 44 4 .4 '4 4 4..4 4.. - '4 n) 4-4 '1 42 44 4- '4 4~ 4-4 4- 4..4 On .4 .4. 44 .. a nr n 44 44 .4- 4 2. 4 .44 0 01 04 4, .244. 42,

444 5 C V 44 .44-' (4 4-4 4.4 - 4. .4 .4 . 4 4 4 4.4.4(4 C. C) 4- 4.4 L~ 44 4.4 4-

C C. S - N 4. - .4 4. 7 .4 4,4 nfl - .- .4. nx C K 44. 4 -'4 * a a a444 44' 44 4. 444 U .4 4.4 CL 0 4.. 4 . U 4-n 3 4.44 444 .4 444a44 44. 2(4.1 .44 4 44

221

4.- -- --

Page 235: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

]lr .! "

.. . . . . .. *-r1 l . - - - " • . . r . ... .

C c C C .i C C C 0o Co C C C o ,C C C, Co C Co C Co Cz Co Co C C C

CI

,,,r. tt C C C C C C C C C C C

Mi Mi-i .

S,

to

*222

Page 236: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

16

IL

0 0o 0D 0p C 4 0 C C 0 4 0 0 0 0 0 0 0 C EM 0 0 0 0 0 0 0 "

.

£ 0 D a k 0 0 0 a m0 n D

- g-

223

.. . .... . , = ,, .... . i

Page 237: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

cc . C "D C 0 C 0 Q 0 C C C a C C a C C C a C C.

cc.4

t-6a

2

C

Li

SI-"

o O

S-

CM

'42

CI..4 N . W

o "... ..4 S, .. m)

%i - - - - - - -4 .

&&

o 4 ~' C ii. S '0 0) 0 ('4 C t ~ i , it 0 10 0 S 0 &1 I l~ . C f

Ln4 n c c a ~ r .. 0 - i~ 2 .4 i) F - .. t L

(4 . S I I LI I 5- 24 . C) 0 C 0 i 0 0 0-

Page 238: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

1 @4 44 I 4 1 4 4 14 44 C 4 4t 4 Nm -% fu 4 Y -l N4 -y ft ft N r

a

2.

C,

a a4

4225

Page 239: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

C a /

2 I- z z 0 0 a 0 0 0 0

CLa 0. IL In In In 0 'n 44 0, ,

c4 C3 a4 C3 0 0 a c a 0

LAz z

7

1. 0

I I a AC z 0 . 2 2 2 2 C

V, .0 . a C ,4 44 A' I' .4 . A 44 .

4- 2 2 7 . 0 0 0 0 0 0

LC LL1 X

-~ ~~~ ~~ ~~~~~ -j" C l * 4 ( l .4 . AC

0 22-

Page 240: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

.. . . . .. . ... ... . . .

CL N Nt Nf N N N N N N N N N,r z.z

ta

w

La

ID IDIo

InLiW

cc

0. 0 A VI V) V) W 1I 44 'A DI if

7 T UI I1 i av C

227

Page 241: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

CK 4 N4 N Ny ft N N N N N N NY N N Nt N N4 NY Ny l N NV N #4 #4 N mii

tiI 1 tza

w w w N w NL 9 N N N N N N N #

a - .. - -, -0 -0 -. 0 0 0

2) 99 C C t i. t a C C L m C a a L

6 0 0 C0 , 0 0 0, 0- 0 0 0 a 0

- 4j

1' '

*

a 2 2 2 2 .2 2 .2 2 2 28 aa 2

Page 242: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

to If t f i t 11 1 0 1 f 1

IL. C. C. & a. > > > > >0 & 0 II 44 44 II C44 IS 04 II II In 04 I

t 0 Q 0 0 0 0U 2 z z z z 2 n 2 2 7

to In Li 40 3 5 50 SD 1 0 1 0 0 w0 0 4D

.

01

u V

tUw>r, >

& CL t r 0 0 0 0 u0 C, t'5 2 a 2

ed n. C, r. C , r0 z z k d. z 2. L 0 I

49 > 0 S 11 Z I:" In c; rl V) .U J U U U U 55 .0 25

C C. 0. N C C 0. V 5 2'. 0 C C C UV, c 0Q ) 0 0 N U U 4, L .5 U U U 2 5

W, T

ho 2 S 2 .5 2 14 7 7 7 7 * 5 7 7 7 4 2 55 4 2 .2294

Page 243: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

- 4 . 4.4 - - - - - .4 . . 4 .

0 0

* ag

a

22

g - -

Page 244: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

S S ° a a a a " a a S " " " :. . : :: :. : .: .:

r

* hJ£

r - a

-;-l, 4 . . . . • ,, . .

_ i= ..

Page 245: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

I ~~~ ~ 0 ** 0 W~ 0 0 0 40 V 0D V0 C 4)0 V a w 0a

• ,J

cc 2 It I Q .0 44 ' 0 0 0 0 0 0 0 0 00

o0

o .. 1

01-'

-4m) 2

CL

.. .. 91 . .. le,

232

0!' 0

Page 246: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

.. . . . . . . . . . . .- - - - - - - - - - - - - - - - - - - - - - - -- - - - -

u

a a - a a a a a a a a 'a a a ' a a a a

a.0%. ao c CILzC xz L2mz0 7 -- Ltoo o o oo& 0

z z z.

wi w w w w CK w m w a m w w m w 7 w w

z a, z 22 2 7 7 z z? 0

QI. a, t" a- L - m - Il 0. C t & a m C.

0 D 0mm 1- M-4i~ -Lf -,..- C

9, '1 I L ii a I I a II C9 2 ii 2 I .2 i . . . i2 I

23

Page 247: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

C. C'

m 04

0r

10 10 1 C I'e

C C C C 42

C 7 7 C234

Page 248: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

pp

~ :: eU * .0 6 .0 6 6 6 iS .0 .0 .0 0 .0 '0 .0 .0 40 .0 .0 .0 .0 .0 .0 4 .0 10

4... .4

2 - - S ~ * S ft .0 iS N ft 4 .4 - - .-. - .. - - .-. s * N N 5* - - - - - - - - 4.4 05 ii) 0 - - .4 .4 -, V)

*4443

C

-JC'444.4

* S

a'4 0. Ca -

- Li.4

I--I4U'ii

24

U'4

4.K4a'

0.

hJN N

S 7 74 0 -U 'I a-

* S0! Li Li0 Li L4 Li C)* 4 4 Li a. N0- 5 5 0

ft 4 N Ii, V)o 4 4* N N N Ci S S

~i 0. 4 .0 0" 0' 0' 0' a o 0 0 0 0 N C, fl C, A ' N N 4- 0' 0' 0 0 - - V

0.C N N 0 0' C 0' VI 0' 4.1 N - N N ir C 4-- 4 a- 1 it' N 0) 4 N. N

Li - Si S' N .4 4., V 4 0 41 - N - 0 ft a ci N 0' 0' tO N - 0 N 0 N N N44'. 445 0 0 0.400.404.. C) C 0 Li C. 0 Li .4 C. C - - C C Li Li C Vift -. 0' 0' * ± 4.21 0 0 0 in C, 0 4 .21 .0 a-i a-iN 441 -, .4' N N * s C a' 5' 0' a, C N N N N N N N N N N N S S S S N

CN Cf

4. 4 0 - Li.4 4- . &

Li L Li Z .4 C .4 .4 -

Li. - - C :4 C)C. 441 .4 U. 0 it 0 141

4., 4. C. - 4., 4.. i'I C I.. -* C '~ a- -4 .4 II' Li a 41 -. Ci aS - 5 44 a - .. 4' 4-. i.e 5 4' - - .4 6-. C, f~4 Ii a- a-C .. CS ~ A C) .4 ir a '- - I Li C' V 4 LI Li N

(4 441 I (V (41--------I r 0 C ' 1> 0 .44 4' 44 .- 44 u .0 4 I.~ .. ' .- II 4- 4.-4 C. ( - a * .-4 N Cl V C. -. 4. 4- 4 a V 4-, LI 3C V. Ii. (1 4) C 21 1 - V 4 . C, .4 4 .. 4 - I LiO .4 .1 4 4 - i'I * 414.4 Viidt., 4.- .....- fl .3 - C' a iJ A 4 1 ~ ~ Li 4- 4- Li fl '4 NJ .4 .* I .w C.. .1 N

Cf i.' .4 Li. Cci 5' (4 r, 3 . - .4 A iA 3i C -. C .4 V C. 4.- 4.. 4- 4- 0. 4) V

235

Page 249: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

at N N N V C C CI . - -r ., in 4% .0 n! '0: nN '' - - i

ae .. . .iC. C

-~~~e e z n .

a C

ci C, c C, 0 1

S~~ ~ -. Q0Z 4 % 4

C236

Page 250: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

0

0 .3

I' ,L

- 0 4 44 II 1i Li Li 33

W u0 C 0 0 La

04 t: 0 0 , N4> N N I C 0

C 00 0 0 0 L

23

Page 251: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

'Io

N~~ IN N N N N N N N ', C Y m c C% N N N

IJ

a

IN I

> >

. U, C C C C

16

c ~0 0 44 0i 44 4 4 I

-5 2 7 2 7 z z

C , ,

L , 0 £ l'

n > I U, 2 21 w>4 c a- 0 a >

44 Li

44j £2J

1 71" t, U

a. - 4 C £ I C238

Page 252: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

0 le ID 4 * ' 8 8 0 0 C 0 V 0 ID D 0 ID 0 D ty 0 NI- .4 .0 91 In o~ '

. . . . . . . . . . . . . . 4 - . 4 .

s s a 2 - - - - N .

19

c- 0 XC 2I 4 I 4 I I

J Lc U4 Ui LX a- L r- a- a00 n , 0 000 00 0

Ha .,.

.4 03 0 LI OU ~ a it 11 44. I I< > 6' 4. 0( C3 0 c 0 C, 0 0Li c 0 > 0 7 7 2 7 4

o

0 C a a- 4N >

> C,

cc 0 C C , Q

-00

2

zaW w

61 I

7 C-i

* Li a Li Li r

cc Ci 0239

Page 253: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

I 0 N L D ~ 0 0

'.~~~ - 1 -. -1 N 1 c 4 0 '102 1. -. It. .1 .4 - N N

C 0 C- c' 0' cC))

.- z

Li

'I I 2 I I I. XI~ ItC Id C ~ CC

02'0 4 4 , C .r. i"' a a ... "0 0" a ' ...0 0' 01 C . . .. ...V

,4 .1 .. - - • .. . .. .. . _ _ ,I C_ = ; :: -CI , . C . 2 I - I CC C. C C C . C I CCl 4 2 , CC 4 1 -. C C~ o4'C I . C 4. /

Page 254: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

4.

U 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 N N N N N C44- 44. 44. 44- 44- 4444 r w' '44 ~ (420 - - .4 .4 - 4, 4444 -' 4, 4444 -

2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 'a 0 0 0 0 N N N N 4444 N'4 4, 4, 4, 4, 4, 44444

2 .4 - - - 4 .4 .4 .4 .4 4 .4 .4 .4 .4 - .4 .4 .4 .4 .4 .4 Ci.4 .4

a

44

'4 '4C

-4444- 44. 44

44- 4.4 N.4 0 '.4 444 0 44)o 2 444 '44444 4 * 4, ~'.4 44' 44 . . 4

* 4, 4, U44 4, ..4 N 44 0 '4 2

44-

44. .4 4444 44. 0 '4

44 .4 44. .4I. o 44.) - .4 i3 ~* 4 0 4.4 4

.1 44- 0' U 2'4 . - 0 '4

4 4 4 4 4 N ~ 4,2 2 2 2 .4 '4 .4 .4 4

4.4 r Li4.!.'4 o o4 0 '4 4 44442 '4 0 -

o v 4.4 44. 4, N

4(40 N '4.44 44- 4- 44 .444

.4 '4 0 0U2 4 '4 44 -* .4 4, 4 .4 .4 - 0 .4.4 2 2 2 2 2 .4 - '4 '4 2

4.4 4.44444 0 Li

Li Li Li 4.. ~ r* 4 4.. 0 C C 4.4 Li 4 LI

2 4 4 4 4 0 C (444 ~4 4 * 4, 4

44 4444 4, 4, 44, N .4444 '4 N (I N * a 44 44 444444. 0 0 C 0 0 0 0 0 2

N .4 - S.. 44. - - ~ 4.. - o0

44 2 4.' 444 '4 '4 44. 0 '4 '4 '4

*.4 44. 444 44. 4, 4444 4, 4444 4, 4, 4, 4, 4, 4, 44) 4, 4, 4, 4, 4, 4, 4.44 4, 4, 4, j*4 4, 4, 4, '4

4.44- - 4C.

C (4~ 34 .4 '4 4 44. 4~ 3' 0 - (4. '4 .4 4444 44 44. - .4 4 4- '4 0' - N 44' N 4, 4,- P- (4.. 44- 44- 4- 44- 44- '4 4 1. '(4 .4. 0 4' Li .1 4444 44 '4 '4 34 - - .4 4. 34 3'4444 0 4 444 4) '4 C C '4 Li C 4.- C. Li C C Ci C '4 44 (44 C. C '4..4......'4C. 444

- (47 42. 4) (44 C, ~. Cx C. C 4tO t4C ,'~C 4 '4 (4, 4- 44 444 4, 4, N (4- (4. 34 44. 444.4 44444 34 0 0, 4444 '4 41' 0 44' 34 34 C 4, '4 44. 34 C 34 t 44, (ii 4, 4, CC N N N (4. N

ft

4421

'4 2' 0 0 t -Cx 44.. '-2 .4 - - 13 .4 LI

00~....~ ~ ~ .. ~ : : : :: ~ z- .-' -. .4 U .4 .4 fl t - 2' 2' :.t 2) 4 -* 44- (4' Li t~

4.4 144(44. 4> 1 *, 1'. 4, .4 (4. (444 44' (444 C. 4.4044 444444 4,4 4.*----------------------4- Li 4.4 4.4 4.4 444 Li fl 44-C . 0.4144. 4, 44 .4 0 (4. '0 '4 '. .4 44 1 (4 444 44 .4 (4. Li 44. .44 44 - 4.4.4 S***4****4 44 44 4 4 44 C 4~ C' C' C. C 4.4 44. 4. C A

-...-. - - .4....- 1' 4.~* C' 444 4.4 4., 4.4 Li Li Li 4. 4.' 4.4 44.4 Lit. 4.' CI Li (4 .4 0444 -' .~i xi 44 . '' 4. ', 7 , . 4 - - 4. 44 444 4, .4, 2' .. Li 44 4. 4- (4 44 I~44 44 Li 444 44 44 44 44. 44. 44. 44. 4.. 44. 4d 22 444' NJ .4 4, .4 4 - - 44< '44444 44 & 4 44 44 4 I 4 44 S 44 & 4. 4 LI 4- .4 (4. 444 .4 44. 4.4 4 = 4) 4:2

241 44.

Page 255: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

Cy N Ny NNI

o L. Lo

oo

'U 4-i 44 11 1

c,-vt-4>

C, c. CC Z 0 w

,.W.

- C, " C, CN

rD 0 0 CI c

_j a LL-- ,, I

o LYC a a z .

242

fi l I I .. I 1I ... ..a '° '' '

Page 256: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

II

4

.1 0c

Lo t

0 v 0 7r

C24

Page 257: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

U N N N Y N N N N N N N N N4 N NY N CY N N N NY N N cy

z Z? z0 7 c0 0

. 1.- I.- , 4CI

Q. d. .1 CrL i 1 i bc ' - .. C C C, C. 0 C.- C, C 0 C. C., 6) C. I.

2 2 2 2 2 0~~ ~ ~~~~~ 7UU U 2 N U U U U U U i U

0 ~~~ ~~~ 0 9 99 4D i 9 9 2 2 9 9 9 t I 9 I 9 9 9 * 9 3 i *

N N Ci N N N N N ( 4 N N N N N N N \ N N al

Li~ ~~ ~~~~ -d -a - i - - I I * 9

24

Page 258: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

. . . . . . .

0 I1I.. C d C 0 0 0 0 0 0 0 0 0 0

S. C

It

CC

0I

-- - - - -

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

'24

Page 259: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

4.

.4 C C 0 '0

-' C -. 0' N N 49 49 '0 .4

-. C - - N N N A.- C'"4 CdI, In

C C C C C C C C C C C C C C ~10 10

C'

2 - .4 .4 - .4 2 2 N .0 .0 N N .0 Cd Ci4 li 09 09 41 N -

C' 49 ~' ~'C

C,

C'

0

IA

C' C0~ 02 A-

1..

1.4 $.4

U09

I:Si I2' I1.' Is

I.4 32

9-

I -

lId'9 4

It

'9

0) .4C'

2 C,o

I.' A - - .-I N 0 2' 0 0 0 0 0 t. 0 0Li C .4

L 4-A 2' 0 -. AS - 2' 2' N - 2 2' .n C US ?~

'9 .4' .4 .41 $ ~A - .4 $9 - C, .'I 'C

IA C'S N Al CS 0 I' C~ '.' C C'S *. A' C 0 I.. II S S C' C) CI C) .1 '4 CC 0 It C It A 1' Ci Ci C .5 Li .4 C S 5 2'

.1 I fl - - -. A '' - -'C' '''~* .9 5 .~ .~. - ., A

A. C, 04 0. ~i 1.' 1- - -* .'.' 44 III I' 0 . -' -. I~ I'.4 C' C IS C, .i 4 - Ci

Is. Is 1. 1. I I) 5) Li '9 ~ ~ I A '1 0.S C' 4 59 Li Li IA 1 4 - - U C

246

Page 260: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

K N J N N N N N N N N N N N N N v N N N ft N N N

K N N N N N N N N ( N N N N N N N N N N Nm

2 - - .4 4 .4 .- -- - -4 -4 - -- - - -4

4. C 0' .5OL M

41 aC . ( a c v

In i0w

V. w w w w w w w m

N- D 00 W4 I D 0 0

9L K z z U

2 40 u4~~~~ 64 7 .4 u q 0 9o~~ ~ >. C. z4 U K K K S

*~~~~~ >0 0 0 . N ' C 40 4 40 40 .

Q m =w D I

24

Page 261: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

N N N N N N N N N IV N NY N * S * S * *

°"

t a

C C S Cf I L' 21 c C. C, C

c c

C- I

248 -

. . . . .. . . . ... . 3 3. " ' - . ...C O ' C. . . . . . . .I - 1i . . . g l l

Page 262: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

IL c

0. ft C. 0 0 c' c e L- C: a c

ff i f, 1.

01 I 0 0 0 C C C 0 0 C . C C L~

(L z

0

z z z z xr z Z -4Li w . Ci I., I4 I3 Li 4. 4C f . a ol 0 a al a a i -4 0 0 0 Cl n 0 0 C 0 .4 c Ci ui

#1 44 0 Ca0 U U 0 Ci 2 -

Cl~~~ ~~ ~ 0 Y 4 I I 'C' C C C 0 2 0 * 4 0 .

- ~ ~ ~ ~ ~ z Sb 1 .1 ' 0 1 N " l- 4 * * A N S 41 I 4, i .3 4)

aL

C, 0 1'. 0 II P. 4 0 4 ' 2 4 249 4 ' I, \ U C '. P

Page 263: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

C 0 . 0 C C C i) C C C C

* C-t0

,

0 N

4 4 4

2 ' 0 C - C C -C O C C N C C C N N N C

L' X 0 C . 4 - 0 N - . C . 0 N 0 0C 0 ] C- N - - 4 ','0

CC C C C -. C C C' C C- C> C' CS C C

it 0 a- X C t C C C C - .. C C V 4 C C C250 "ta. C C C

* C - -. - ' . C C 2' 'it' Ci CCC CC C C (3I

Page 264: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

II

4-4

0

-- 0

25

Page 265: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

N '0 S Ii. N N N N N CC N N N N N iC N N N N N N * ~N I. CC 4' C C) N 01 N N 0) 0) N 0) N 0' - N CCC') .-i N C. 0 C N Ci C'. lfl CC N C' ir~ N CC 'Ci iii c o

X Si .0 IN N N C-iC N N CC N N N N N Ci N N Ci N Ci * ~N -i N N C) Ci Ci N Ci N N C N Ci Cii" C) CC CiCi i-i

'C - N N ~C N N N NC - - N

0

-J *' ii LiC .2.Cii N 4)Li * A 'C N - N c .3 N CN C~ C) .2 2 2 Cl 2 7 2 2 2 2 2

C .1

C I-01.) 00..

0- a- 0 'CU.D - N YIiCL. - 00o 0 0 - - Li

'C 1.. N Ii "0 .2 DC)Li. t' Cl Liii' 1.. 05)- C. IILi " -- Cl .., ii i. '. II II4 4.' 2 LiN () iJ i CL I C UC'.0 0 C 0-aN,. C

1

C N N N N Cin .4 .3

011)2 .2 tC

- ii Ci I-.

.3 'C C C C C N N C C

'C Li i-C Li *1~C) 44 44 44 C) C'. 2 2 .2 2 -. 2

I)

* Li C-C '1, ti C)0 4.. C) Ci C C.iS N C N N iCi -. .. Li Li 4 C) Ci 14 Lu CiCC C, C 'ii Cl .7 44 t is Ci C. is

* C C .0 Ci C C Ci N CiC) C .o C C N A,0 C C Ci * * ') Ifl Ci N N U) N U)

C- C il 4) 5' Ci 0 a a 0 a N N Cr NN .4 LI LI C) - Cr - C. C C. i.J 0 i.i 0 0CA C 0-

C A' fl 4. C CS NiL' C. Li C C' C

Cl N CC C .-. .~ 4) Ci 0 2 .2 .0 N .1 ii - 4.) CA C' -u ., 0 0Ci C' i "' *'i'i'i.3 N -

CCo S C C - 4 N .-. C, .. C C .0 C' 3. it ii)- "C C) - - C' C- ii .0 .0 .0 .0 iN' '~ ~' N ii ~ii ~ Co

in C ." - Ci C. CC N Ci N N C) C0 . - - C' ii C .. C C .1' I' ii) ii ii. C. C C.N it iN l\ it C

0 I. ni C. iN IN i'. Ci C)

C' a -

'C - I'

1.1 Ci -I. - -

.4 C" u Li A 1 N N L' -

.4 - CC 4 C C A iC ,L . C.

3 '; 'C I 5 .4 Cl 'C

i .1 ii 0 'iiii C 'I C .t a a C £

.i ' ill C C i ~tC i S

252

6

Page 266: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

I.0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0

Cli N N N 41 IC .11 41 'C 41 li' .0 .0 .0 C) N 0)N N N N * N N IV ~ - -

Cl .0 .0 .0 Cl .0 Cl .0 .0 Cl Cl .0 Cl Cl Cl IC .0 Cl Cl Cl Cl Cl Cl Cl Cl Cl .0 Cl

Z .0 Cl .0 .0 N N N N .0 IV N .0 .0 .0 .0 .0 -. .4 i i inCl' WI C' C' C' - C' 0' 0' - .- - - -

0

4.0

CCC hi

.0

I'-n0. 0z -- Li

-i

C,

.0hi

0'

.0

a

WI Li0- *~

0 4%

~ .0

- 14

o ~,

C)4% -C.0 0

o ~C. 0 0 0 0 0 0 0 0 C) .4 C> C) Cl Cl C) .i 1 -) 01 'CI .0 'CI Cl 'Cl 4) .0 'C. P 0

0

r .0 'Cl C N * 'C Cl N C' C. S )C II) N S .o a S Cl .4, I'. Cl 0' IV N "'I'-5 .0 .0.4.4nlC l*4N C ' CV IV IV N Cl - - 'C S s 4. 4. s 1 41 41 III Ii) IC

Ct .0 - - 0 0 .0 0-' 0 C 'O C C )tIC Ii CC C' C. C' C) C, Ci C) C' Li 0 0 0 -* - 0 0 C .4 C) 0 C) C) 0I*11 C' .3C*CI C) C~ C' C, Cl II Ci C Cl C)'I in 4. Cl Cl 0 Cl 10 Cl Cl C 0 11 Cl IC C 'C C C CC IC Cl C .0 C C 0 Cl 4. CC

C C C C C C, Ii - i CO C C. ' C

CI ~ 'N .11 4. 41 .0 N .0 3% C. - -

* - - - C- I. C- 1- I- C I I I 2 I 4 A A .i I 1 >3

Cl .. .7 1 ~ ~ C 0 .3 1. C' 1. C) .3 .3' .

Cl C) 0 CC -, 2----------4 1 3, II C Cit C) C 12 C C) C)

- C %~ C Li 1>3 12 I.? Lit CI C.' Is c LI CC CI N N '3. Cl . N /3 in

/3 .3 1' C, ,. Cl CC I, LA C. C .a .3 .31C II C C .V .w . I C C . -- Li C~ in C 3 ~ U ~ '.1 0 0 CC 1., b~ ~ Cl 4 CC .4 '2 4 1 CC C .1 1 11in 'C) I" Ci C I Cl .4 C *. C) 3. C) C I .1. 1 I I 2. .L C 1 .1. I C

253

Page 267: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

I-I

u.4

a

0

.-

a.o

.25

oI

Page 268: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

CL"f

7

0

C

0

44

-J

S;7N v I

N N 0c m ' , 5 4 5 4 4 1 .

If IL IF 21 a 1 oI

ft 0 0 0 e 4 0 0 5 0 0 4 0 .4 5 0 0 -2550

IN4 4 0 0 0 0 4 0 04 5 4 4 0 0 4 4 0 0 0 4 0 0 0

Page 269: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

VI a

VI

3

I-

Can

0. C

-J

an

II

C

VI'a

IC.

ill Li0- PC- ..~a CC 0.

- hOo a,0 N2 a0 0

2 -a-, a.

0 (ii

U, a, C-I- - 0-t Va t.<

C 0

a* 31

256

Vs

Page 270: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

I...

-~~~ ~~ la cu a a a a a a a a a a

u 4 . 4 . 4 . a W

a . 4 - 4 F ,

a iA

2 61 N . 4 a~ 4 . . 4 - 4 - . .4 I . - 4 . 4 .4 F 4 U C

Ln D. uWNIf,

to 0 NI

C,

Inx0 L a A F a

.25

Page 271: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

0 .. C

IL wC7 A- S

C,258

Page 272: BEIN AEROSPACE CO SEATTLE WA BOEING M ILITARY ...3.1-7 Avionics -Flight Control System Interface 19 3.1-8 Communication Equipment Control Requirements 21 3.1-9 INS Block Diagram 22

.

w

I-

CL

A. i

S- 0

CL

zzIL 0 li

W

11 r

41u u ,

LLU L U t L & L L Li-)r-2f T