Dtic: HI111111!ll - 111111 - 1111
Dtic: HI111111!ll - 111111 - 1111
NRLJFR15530-92-9194
_DTIC
ELECTE
1992
S SEP2 3
* A
IQ 92-2571
'I
Public reportri buirdmn for this collection of ejformstion is simted to averag 1 hour perremporne. kicludwil; the tWe for reviekwin euctimwt. serwg extet data saurs.
gathering wid m omrgil the date needed, end coipns'if-g id reviewingl the collection of inotion. Send communit regrdil; de birden aetimaste or wn otte epec of te
colctioin of'iformato, icludingl ouggeetwu for reduing thie buaden, to Washngton lHeadquoitsre Services. Directorate for Information Opertorm and Flopo-rte. 1216 .Jefferson
Davie Highwmay. Sute 1204, Arlington. VA 22202-4302. and to the Office of Management mid Budget. Paperwork Reoduction Proiect 10704-199). Wsolwten. DC 20603.
1. AGENCY USE ONLY ILeeve Mebnki 2. REPORT DATE j3. RPORT TYPE AND DATES COVERED
34. TITLE AND SUBTITLE
I August 31. 1992Fia
he -7E ircaftPE
SoftareRequremntsfor
6. FUNDING NUMBERS
0602234N
The Software Cost Reduction (SCR) research project introduced a new approach to specifying requirements for real-time
embedded systems. The principles were applied in the development of the Software Requirements of 1he A-7E Aircraft, as an example
3 The system software requirements specification document comprises the first product in a series of products which the SCR
methodology produces. The methodology is intended to be adaptable for various types of systems.
Specification properties which it supports include: (1) conciseness, (2) preciseness, (3) aids to completeness, (4) avoidance of
redundancy, (5) descriptions of all externally visible behavior, (6) ease of change, (7) good reference tool, (8) record of fundamental
assumptions which might otherwise be only implicit, (9) record of responses to error conditions, (10) specification of constraints on
the system, and (11) separation of concerns; that is, a division of the information into distinct, independent parts.
17. SECURITY CLASSIFICATION 18. SECU91TY CLASSIFICATION 19. SECURITY CLASSIFICATION 20. LIMITATION OF ABSTRACT
i 18-102
*Acknowledgments
I
£ ~
We would like to thank all the people at the Naval Weapons Center at China Lake, California.
who helped us. but especially the following people who answered questions patiently and reviewed the
document carefully.
~Bob Westbrook
I Lee Thomson
Mark Jacobson
Ivan Harnage
Dan Allen
Jim Hall
Terry Moore
Charles Hill
Jack Willbur
We would like to thank Stan Wilson for his integral support of the A7 project.
u We would like to thank P. Clements who coptributed more than any other non-author to the
contents of this document, both in his time spent updating the document, and in his invaluable discus-
sions of the relevant issues.
We would like to thank John Kallander. who contributed to the original version of this docu-
ment.
We would like to thank Georgine Spisak. Louise Alekna and Katherine Tyer for their assistance
in the preparation of the original version of this document.
We would like to thank Bruce Labaw. who has worked yery hard to uncover and correct factual
errors and ambiguities in this document.
We would like to thank Jean Tschohl for her work in maintaining this document under
configuration control.
In addition, we would like to thank all other members of the A7 team, who over the course of
10 or more years have contributed to the refinement of this document.
I•I MI
...
.. ..,..., ... . . .
0:;
iA.. .
I
I
I
Preface
1
This document is the second published release of the Software Requirements of the A-7E Air-
craft [ref NRL Memorandum Report 38761. The first release. published in November 1978, introduced
a new approach to specifying requirements for real-time embedded systems in the form of an engineer-
ing model. That document has been perhaps the most successful of the publications of NRL's
Software Cost Reduction project in terms of the interest generated and the number of copies
requested since its introduction.
I
In spite of its success (in a sense, because of it) the specification has changed in many details
over the years. This is not the result of flaws in its design, but the fulfillment of its creators' vision
that the requirements should be a "living document;" i.e.. that it would serve as the primary reference
I
document for system designers. as well as the authoritative "test to" document for program valida-
tion, and be useful throughout the system development process. Because the document has served
these purposes as well. it has changed over the years as requirements became better understood.
U
Further. since the document is intended to serve as a model document, we have felt free to change it
as better specifications techniques have been developed. This release represents the accumulation of
those changes from the original publication in November 1978 to the end of the SCR project in
December 1988.
In spite of many changes in its particulars. the reader will find the document remarkably
unchanged in its overall structure and approach. One of the principles guiding the original design was
that because requirements change, the requirements specification should be easy to change. As a
result, incremental changes and improvements have been easy to accommodate over the years without
disrupting the essential document structure.[Chmu82]
This remainder of this preface gives a brief overview of the software requirements specification
methodology developed as part of the Software Cost Reduction (SCR) project at the Naval Research
Laboratory. A good description of the role of requirements specification in the development process is
given in 1Heni80 and [Hest81i.
PROCESS
In the SCR methodology., the first product of the software development process is the the system
software requirements specification document. Initially, the requirements document provides a skele-
ton framework of sections and templates. Filling in the framework requires answering increasingly
detailed questions regarding system requirements. At any point in the process, gaps in information
indicate unresolved issues.
I
Since different types of systems have different characteristics, no single rigid framework or set of
techniques will yield the best specification for all aspects of all systems. Rather than attempting to fit
all specifications to a single mold, the SCR approach defines (1) a set of objectives that the
I
specification must meet and (2) a set of principles to guide choices among possible specification tech-
SPECIFICATION PROPERTIES
The primary objective is to provide a complete specification of required system behavior. In its
final form the specification, and any documents to which it refers, should contain all of the informa-
tion necessary to build an acceptable software system. All significant externally visible behavior of the
software should be constraiiied to acceptable alternativeb iW ,he requirements document. Other
iv I
U
I
objectives for the requirements documentation are:
(1) Specify external behavior only: The purpose of the document is to state only what behavior the
system must have; it should not imply a particular implementation or constrain the set of imple-
mentations unnecessarily.
(2) Be easy to change: Software requirements can be expected to change both during development
and as the system evolves into subsequent versions. The requirements document should be easy
to change.
(3) Serve as a reference tool: The primary purpose of the document is to answer specific questions
quickly and easily. It should be obvious where to put or find a given piece of information. It
should be obvious where information is missing or incomplete.
(4) Record forethought about the system life cycle: We assume that system software should be
designed for ease of subsetting and ease of change. Design for either requires forethought. The
requirements should record (1) fundamental assumptions, characteristics of the system that are
not expected to change, (2) changes anticipated or planned for subsequent releases, and (3)
required subsets, subsets of the system functions that are expected to be useful for development,
early release, or subsequent versions.
(5) Specify responses to undesired events: The systems response to undesired events such as
hardware failure or user errors should be specified as part of the requirements and not left to the
possibly arbitrary discretion of system implementors.
(6) Specify constraints on implementation: The requirements must specify any constraints on the
set of possible implementations. For instance, the design may be constrained by the need to
interface with specific hardware, meet certain timing and accuracy requirements, or even to use
a particular algorithm or language.
In summary, the objective for producing the software requirements document is to produce a
yardstick by which the acceptability of the delivered system may be judged. If the software meets all
the constraints (behavioral and otherwise) imposed by the document, then it shall be considered
acceptable by definition. Conversely, constraints not included in the requirements document shall not
be considered to apply to the builders.
(3) Avoid redundancy: Requirements should be stated only once. Where there is redundant infor-
mation. the document is more difficult to change since the document must be changed in more
than one place; failure to find all instances of redundant information leads to ambigvities.
'Explanatory" material that repeats information included elsewhere in the specification belongs
n a separate section or should be clearly labeled as not specifying a requirement.
g These principles have been applied to the specification of the Navy A-7E avionics system. The
following section gives a brief overview of the techniques used in that specification.
v
I
I
SUMMARY DESCRIPTION OF THE METHOD
In the NRL method, the externally visible behavior of the software is described in the form of "a
set of functions associated with output data items." A data item is associated with each input or out-
put of the software that can change value independently of the others. For instance, an input data
item might be the barometric altitude or the setting of a cockpit switch: an output data item might
denote a signal that turns a light on or off in the cockpit, or positions a symbol on a display. For each
data item, a template gives the information necessary to write software that can read the inputs and
write the outputs. For example, template entries for input data items include a description of the
physical quantity or state that it represents, its range, resolution, how fast it can change, its accuracy,
and its ahardware
stitute definitionrepresentation.
of the interface The setembedding
to the of templates for all the
hardware withdata items
which thetaken as a interacts.
software collection con-
I
Associated with each output data item is a function. Each function determines the possible
values for one or more output data items. The possible values for a given output data item are deter-
mined by exactly one function.
Rather than describing output values as mathematical functions of the input values, the values
are specified as functions of the external environment. For instance, in the specifications for the A-7E
avionics system. conditions describe aircraft operating conditions such as the aircraft being at an alti-
tude of 30,000 feet or having an airspeed of 500 knots. To describe the outputs in terms of external
values, a language of conditions and events is created. A condition is defined to be a predicate that
characterizes some aspect of the system for a measurable period of time. For instance, "barometric
I
altitude > 5,000 feet" might be a condition. An event refers to a moment in time and is said to occur
when the value of a condition changes from true to false or vice versa. Output functions are then
written in terms of conditions and events. A consistent notation for expressing predicates concerning
I
external conditions is developed as well.
By separating concerns, this approach simplifies the specification and avoids overspecifying the
system. Concern for the output value produced is separated from concern for which inputs will be
I
used by the code to produce that value. Inputs are considered only a means for obtaining the neces-
sary values. This avoids overspecifying software because one need not dictate the choice between
alternative sources of a value where more than one is available and because no particular sequence of
transformations from input to an output need be specified.
The output functions are simplified by writing them in terms of system modes. Often a func-
tion describing an output data item will be affected by several external conditions. Describing the out-
put value for all possible cases will require lengthy and complicated Boolean expressions of the condi-
tion values to adequately characterize the relevant system states. To keep the output value function
descriptions simple the notion of a mode is introduced. A mode corresponds to a subset of the possible
system states. Instead of giving the output value functions solely in terms of conditions, they are
I
defined in terms of modes as well.
Since a mode describes the states of many conditions, the function descriptions are simpler in
terms of modes than in terms of conditions alone. A separate section of the document describes the
relationship between the modes and the condition values. This section describes the system modes by
specifying the events that cause transition between system modes. A mode class is described as a set
of modes between which transitions may occur. The set of modes in a mode class completely and
uniquely partitions the system state space. The abstract model for a mode class is a finite state
machine for which events are "input" and modes are machine states.
The technique of writing system output functions in terms of modes simplifies the specification
and makes state information manageable by separating concerns. Concern for the details of exactly
I
which conditions determine a particular system state is separated from concern for the system
behavior in that state. Details of the relationship between conditions and system states are encapsu-
lated in the specifications of the system modes.
I
I
The "heart" of the document consists of the data item templates, the output functions, and the
mode definitions. Other information called for by the SCR methodology includes timing and accuracy
requirements for each output function, a description of likely changes that should be anticipated in the
design, and a specification of the computer or computing environment to be used.
CONCLUSIONS
Requirements specification is the process of answering the question "what should the software
do?" Two kinds of information essential to answering that question are (1) what (specific) questions
remain to be answered about the software and (2) how complete is the specification, i.e., how do we
know when the job is done?
The SCR requirements method provides a framework for a requirements tpecification document
and a set of document design principles. The document framework, from the table of contents to the
formats of specific tables, guides the requirements analyst in determining what questions concerning
system requirements remain to be answered. The document structure makes it evident where infor-
mation is missing or inadequately specified. The design principles provide guidance for extending or
otherwise modifying the structures used for the A-7E example.
The document structure and accompanying formalisms also provide a variety of checks for com-
pleteness. The completeness of the specification is often obvious from the degree to which the
chapters, sections, tables, etc. are filled out. In addition, underlying formalisms provide checks for log-
ical completeness and consistency of many parts of the specification. Often the consistency checks
proceed downward in a hierarchical fashion. For example, there is exactly one function for each out-
put data item; since the number of output data items may be easily determined, we immediately know
at most how many functions are necessary. Within a function, the list of mode classes and modes
within each class may be used as a checklist to assure that behavioral changes within each mode are
accounted for. Recall that a mode class partitions the system state space completely; therefore, speci-
fying the behavior of an output in each mode fully specifies it for all system states.
REFERENCES
[Chmu82l
L.J. Chmura and D.M. Weiss. "The A-7E Software Requirements Document: Three Years of
Change Data." NRL Memorandum Report 4938. Nov., 1982.
3Faul871
S. Faulk and P. Clements. "The NRL Software Cost Reduction (SCR) Requirements
Specification Methodology," Workshop Notes. Fourth International Workshop on Software
Specification and Design. April 3-4, 1987.
VHeni801
K.B. Heninger, "Specifying Software Requirements for Complex Systems: New Techniques and
Their Application," IEEE Trans. Software Eng. SE-8(1), 2-13. 1980.
'Hest811
S. Hester. D. Parnas, and D. Utter. "Using Documentation as a Software Design Medium," Bell
Sys. Tech. J. 00(8), 1941-1977, 1981.
I
Mill80j
H.D. Mills. "How to Make Exceptional Performance Dependable and Manageable in Software
Engineering," Proceedings of the COM1PSAC Conference. Oct. 1980. pp. 19-23.
vii
I
I
I
CONTENTS
I
1
Chapter 0: Introduction
Mode Index
3 01: OVERVIEW.....................................................................................
0.1.1: Document Purpos6e............................................................................. 1
30.1.3:
0.1.2: Document Design Decisions ...................................................................
Document Structure ...........................................................................
I
2
£0.2.1:
0.2: NOTATION................................4
0.2.2:
Bracketing Symbols............................................................................
Operators........................................................................................
4
5
0.2.3: Conditions and Events ........................................................................ 5
0.3.3:
Condition Tables...........................................................................
Event Tables ................................................................................
6
7
8
B0.3.4.0:
0.3.4: Mode Tables................................................................................. 9
Initial Modes Table....................................................................... 9
0.3.4.1: Mode Transition tables .................................................................. 9
Ii
I
I
Detailed Contents
1
1.0: INTR ODU CTIO N .............................................................................................................. 11
1.1: M EM O RY ........................................................................................................................... 11
x
2.0.3: Coordinate Systems ....................................................................
19
.0.4: Definition of Data Item Classes ............................................................
19
2.0.5: Data Items for More than One Device .......................................................
-0
2.0.6: Data Items That Affect Signal Converter Tests .................................................
.20
I2.1.2.2:
2.1.2.1: ADC failure .....................................................................
ADC barometric altitude ............................................................
2.1.2.3: ADC Mach number ................................................................
. 41
40
42
2.1.2.4: ADC true airspeed ................................................................. 43
2.1.2.5: Test select ADC/FLR .............................................................. 44
2.1.3: Forward Looking Radar (FLR) ............................................................ 45
2.1.3.1: FL R locked-on .................................................................... 46
2.1.3.2: Slant range to target ................................................................ 47
2.1.3.3: Antenna slave command ........................................... 48
2.1.3.4: Computer system fail .......................... ................. 49
2.1.3.5: C ursor azim uth ................................................................... ..
..... 50
2.1.3.6: FLR cursor enable ................................................................ 51
2.1.3.7: FLR cursor position ................................................ 52
2 .1.3 .8 : F ligh t p ath an g le .................................................................. 53
2.1.3.9: FLR ground track velocity ...................................... A
I2.1.3.10:
2.1.3.11:
Steering commands ...............................................................
Test select ADC/FLR .......................
55
57
2.1.4: Head-Up Display (HUD) ................................................................ 58
2.1.4 .1: H U D reliab le ..................................................................... ............ ...... 61
2.1.4.2: HUD AS,ASL, FPM.LSC.PUAC.and USC ................................. 62
xi
I
I
2.1.4.3: Azim uth steering line angle and roll angle ....................................................... 63
2.1.4.4: HUD barom etric :'itude ...................................................................................
U
64
2.1.4.5: HUD Flight director ......................................................................................... 65
2.1.4.6: HUD sym bol controls .......................................................................................
2.1.4.7:
2.1.4.8:
HUD magnetic heading .....................................................................................
HUD pitch angle ................................................................................................
66
67
68
1
2.1.4.9: HUD vertical velocity/acceleration ....................................................................
2.1.5:
2.1.5-1:
Arm am ent Station Control Unit (ASCU) .................................................................
Bom b drag .......................................................................................................
69
70
71
5
2.1.5.2: Guns selected .................................................................................................... 72
2.1.5.3:
2.1.5.4:
M aster arm switch ...........................................................................................
M ultiple rack switch .........................................................................................
73
74
5
2.1.5.5: Stations ready .................................................................................................... 75
2.1.5.6:
2.1.5.7:
W eapon type .....................................................................................................
Bom b release .....................................................................................................
. 76 I
77
2.1.5.8: Fire ready ........................................................................................................ . 78
2.1.6: Projected M ap Display Set (PMDS) .........................................................................
2.1.6.1: PMDS decenter switch ......................................................................................
79
81
U
2.1.6.2: PM DS hold switch ............................................................................................ 82
2.1.6.3:
2.1.6.4:
PMDS north-up switch .....................................................................................
PMD S scale switch .......................................................................................
83
84
I
2.1.6.5: PMD S landing switch ....................................................................................... 85
2.1.6.6: Azimuth ring angle ............................................................................................ 86
2.1.6.7: Destination pointer angle ................................................................................... 87
2.1.6.8: M ap orientation angle ....................................................................................... 88
2.1.6.9: Range digits ...................................................................................................... 89
2.1.6.10: Hor..ontal m ap position com m ands ................................................................ 90
2.1.6.11: Vertical m ap position com m and ...................................................................... 91.
2.1.7: _-2 P nel ............................................................................................................... 92
2.!.7.1: Enter button ...................................................................................................... 93
2.1.7.2: Fly-to thum bwheel ............................................................................................ 94
2.1.7.3: Fly-to toggle ................................................................................................ 95
2.1.7.4: K eyboard enable s- tch ..................................................................................... 96
2.1.7.5:
2.1.7.6:
N -vboard integer buttons .................................................................................
M ark button .......................................................................................................
97
98
I
2.1.7.7: Mode rotary switch ................................................ 99
2.1.7.8:
2.1.7.9:
Panel self-test ................. ...................................
Present position toggle ......................................................................................
100 I
101
2.1.7.10: Update thum bwheel ...................................................................................... 102
2.1.7.11:
2.1.7.12:
Lower window digits .......................................................................................
Nfark window ..................................................................................................
103
105
I
2.1.7.13: O ther panel lights ............................................................................................ 106
2.1.7.14: Upper window digits ....................................................................................... 108
2.1.8: Built-In Test Equipm ent (BITE) .............................................................................. 109
I
I
xii
2.1.8.1: Introduction ....................................................................................................... 109
2.1.8.2: BITE functions .................................................................................................. 109
2.1.8.3: GO/NO-GO counter ......................................................................................... 109
2.1.8.4: Storage protect violation detection .................................................................... 109
2.1.8.5: Signal converter hardware-generated values ...................................................... 109
2.1.8.6: AC self-test ........................................................................................................ 110
2.1.8.7: DC self-test ........................................................................................................ 112
2.1.8.8: Discrete input words 1-3 .................................................................................... 113
2.1.8.9: Serial wrap I ...................................................................................................... 114
2.1.8.10: Serial wrap 2 ................................................................................................... 115
2.1.8.11: Accelerometer tests .......................................................................................... 116
2.1.8.12: Discrete output words 1-3 ................................................................................ 117
2.1.8.13: BITE register function 1 .................................................................................. 118
2.1.8.14: BITE register function 2 .................................................................................. 119
2.1.8.15: Cycle steal channel A ....................................................................................... 120
2.1.8.16: Cycle steal channel B ....................................................................................... 121
2.1.8.17: Spare synchro outputs ...................................................................................... 122
2.1.8.18: Gyro torque tests ............................................................................................ 123
xiii
2.2.9.1: Aircraft airborne......................................................................... 144
2.2.10: Pilot Grip Stick (PGS) ...................................................................... 1451
2.2.10.1: Release enable button.................................................................. 146
2.2.10.2: Target designate button ............................................................ 147
2.2.11: Waypoint Data System...................................................................... 148
xiv
3.3: NAVIGATION MODES............................................................................. 188
3.3.2:
Doppler Inertial Gyrocompassing ('DIG*) .................................................
Doppler Inertial (*DI') .......................................................................
188
189
190
I3.3.4:3.3.3:
3.3.5:
Inertial (*I*).................................................................................
Magnetic Slave (*Mag sI')....................................................................
Grid (*Grid*) ....... ....................................... I................................
191
192
193
3.3.6: Unaligned Doppler Inertial (*'UDI*)......................................................... 194
3.3.7: Open Loop ('OLB') ........................................................................ 195
3.3.8: IMS failure (*IMS fail').................................................................... 196
3.3.9: Polar Doppler Inertial ('PolarDI') .......................................................... 197
3.3.10: Polar Wander Azimuth. Inertial (*PolarI') ............................................... 198
33.4: TRANSITIONS BETWEEN ALIGNMENT/NAVIGATION /TEST MODES ............. 199
I3.6.8:3.6.7:
3.6.9:
Air to Ground Guns/Rockets ('A/G Guns') ..............................................
Air to Air Guns ('A,/A Guns')..............................................................
Mlanual Ripple ('Mlanrip')...................................................................
223
223
223
I3.6.11:
3.6.10: Normal Attack. HIUD unreliable ('HUTDdawnl') ........................................
Backup HUD Mode for Normal Offset ('HUJDdown2') ................................
3.6.12: Walleye ('Walleye')........................................................................
223
224
224
3.6,13: Special mode overviews ..................................................................... 225
3.6-14: Backup HUD) mode for Special Normal Attack ('SHUDdowni') ..................... 225
3.6.15: Backup HUD Mode for Special Normal Offset ('SHULDdown2')...................... 226
3.6.16: Extended Weapon Delivery Modes......................................................... 226
I
4.2.1: Enable Radar C ursors ............................................................................................... 254
4.2.2: Placem ent of R adar C ursors .................................................................................... . 255
4.2.2.0: Reference points indicated by radar cursors ...................................................... 255
4.2.2.1: Update Azim uth-C ursor Position ...................................................................... 256
4.2.2.2: U pdate Range-C ursor Position .......................................................................... 257
4.2.3: Slave or Release the FLR A ntenna ........................................................................... 258
4.2.4: U pdate Antenna Elevation ........................................................................................ 259
4.2.5: U pdate A ntenna A zim uth/D rift Angle ..................................................................... 260
4.2.6: Update G round Track Velocity ................................................................................
4.2.7: U pdate Flight Path Angle (AD I and FLR ) ...............................................................
262
263 5
4.3: HEAD UP D ISPLAY FU N CTIO N S ................................................................................. 265
4.3.1: U pdate A im ing Symbol Coordinates ......................................................................... 265
4.3.2: A zim uth Steering Line Functions .............................................................................. 269
4.3.2.1: U pdate A zim uth Ste ering Line Coordinates ...................................................... 269
I xvii
I
4.6.29:
4.6.30:
Update DATA 21-22 (area A, area B)....................................................................
Update DA TA 23 ................................................................................................... .
338
339
I
4.6.31: U pdate DA TA 24 ................................................................................................... . 340
4.6.32: U pdate DA TA 25 ................................................................................................... . 341
4.6.33: U pdate DA TA 26 ................................................................................................... . 342
4.6.34: U pdate DA TA 70 ................................................................................................... . 343
4.6.35: U pdate DA TA 71 ................................................................................................... . 344
4.6.36: U pdate DA TA 72 ................................................................................................... . 345
4.6.37: U pdate DA TA 73 ................................................................................................... . 346
4.6.38: Update DATA 80 ................................................................................................... . 347 l
4.6.39: Update DA TA 81 ................................................................................................... . 350
4.6.40: U pdate DA TA 82 ................................................................................................... . 352
4.6.41: Update DATA 83 ................................................................................................... . 354 i
4.6.42: Update DA TA 84 ................................................................................................... . 355
4.6.43: Update DA TA 85 ................................................................................................... . 356
4.6.44: Update DATA 88 ................................................................................................... . 357
4.6.45: Update DA TA 89 ................................................................................................... . 358
4.6.46: Update DATA 90 .................................................................. 359
4.6.47: Update DA TA 91 ................................................................................................... . 360
4.6.48: Update DATA 92 (north) and 93 (east).................................................................. 361
4.6.49:
4.6.50:
Update DA TA 94 ...................................................................................................
U pdate DA TA 95 ................................................................................................... .
.
362
363
i
4.6.51: Update D ATA 96 ................................................................................................... . 364
4.6.52:
4.6.53: U pdate DATA
Update DA TA 97 ...................................................................................................
98............................................................................ . 365
366
4.6.54: Update DATA 99............................................................................ 367 i
I
4.7.0: Reference Points for HSI Functions .......................................................................... 368
4.7.1: Update HSI Bearing Indicator ................................................................................... 369
4.7.2: Update HSI G round Track ........................................................................................
4.7.3: Update Range Indicator (Map and HSI) ....................................................................
370
371 3
4.8: ATTITUDE DIRECTION INDICATOR FUNCTIONS ...................................................
4.8.1: Update ADI Azimuth Steering Needle Position ..............................
373
373 3
xviii
I
4.9: GO/NO-GO COUNTER FUNCTIONS ............................................................................ 374
4.9.1: Resetting the GO/NO-GO Counter .......................................................................... 374
i .9
EXPECTED TYPES OF CHANGES .............................. ............. 388
xix
I
I
9.3.2: FLR ........................................................................................................................... 389
9.3.3: H UD .......................................................................................................................... 389
9.3.4: O ther Uses of Flight R ecorder .................................................................................. 389
9.3.5: A .SCU........................................................................................................................ 389
9.3.6: PM D S ........................................................................................................................ 389
9.3.7: TC-2 Panel ................................................................................................................ 389
9.3.8:
9.3.9:
9.3.10:
Slew Control ..............................................................................................................
D oppler R adar Set .....................................................................................................
Weapon Characteristic Parameters Are Subject to Change (Frequently) ...............
389
389
389
5
9.4: FUN CTIO N CHAN G ES ....................................................................................................
9.4.1: G eneral ......................................................................................................................
389
389
5
9.4.2: HUD .....................................................................................
390
9.4.3: Panel .......................................................................................................................... 390
9.4.4: N ew W eapons Functions ........................................................................................... 390
9.4.5: RECO N Functions ....................................................................................................
I
390
9.4.6: In-flight A /C M onitoring Functions .......................................................................... 390
9.4.7: SYSG EN Capability Shipboard ................................................................................ 390
9.4.8: Suspension of Low Priority Activities to Allow Special Functions ........................... 390
9.4.9: Internal A /C Com m unications Functions .................................................................
9.4.10: Accept Information Over Data Link While Airborne .............................................
391 I
391
I
9.4.11: Lateral Control of Aircraft ...................................................................................... 391
9.4.12: Parallel Processing of Release/Impact Points. Etc. for Several Weapons ............... 391
9.4.13: Calculations for Two Destinations (One a Target) (Already Planned) ................... 391
9.4.14: M ore Support for M oving T argets ........................................................................... 391
9.4.15: M ulti-step Flight Path Navigation .......................................................................... 391
9.4.16:
9.4.17:
Electronic W arfare Counter M easures ....................................................................
Com puter Self-test D uring Flight ............................................................................
391
391 3
10: GLOSSARY OF ABBREVIATIONS, ACRONYIS, AND TECHNICAL TERMS ........... 392
CHAPTER 0
Introduction
0.1. OVERVIEW
2I I
NRL REPORT 9194 Introduction
I
I
I
Chapter 0 ALSPAUGH. FAULK. BRITTON. PARKER, PARNAS, AND SHORE g
Chapter 11: References and Sources of Further Information
This chapter is an annotated list of other reference material and personnel. The information
that is specifically referenced in Chapters 1 to 9 is considered a part of the requirements defined by
3
this document.
Indices 3
Three alphabetical indices are provided:
(1) an index of data item acronyms; m
(2) an index by mode name acronyms; and
(3) an index of output data items affected by functions.
These indexes appear after the Dictionary.
Dictionary of Terms
this section, along with their definitions.
0.2. NOTATION I
0.2.1. Bracketing Symbols In order to be both brief and precise, the document contains
many abbreviations, acronyms and symbols. These are used to refer to a broad variety of objects:
definitions, input data item, output data items, mnemonic itames for data item values, system modes
etc. To make it easier to recognize the type of object referred to by an abbreviation or acronym, we
use special symbols to bracket them.
/input/ /SAP/ indicates that SAP is the name of one of the hardware inputs to the TC-2.
These items are described in Chapter 2.
//output// //SOUP// indicates that SOUP is the name of one of the hardware outputs from
the TC-2. These items are described in Chapter 2. 1
Svalue$ If /SAP/ and //SOUP// are non-numeric data items, we have defined mnemonic
names for values. These mnemonic names are enclosed in "S" brackets. Thus possi-
ble values for /SAP/ might be defined as SDaveS, $John$, and SKarin$, while
SBean$ and SPea$ might be possible values for //SOUP//. A condition (a state-
I
ment about the system that is always either true or false) would then be given as
/SAP/ff SDave$. However, /SAP/ = SPea$ is clearly an error because SPea$ is not
a legal value for /SAP/. To indicate that we assign the output data item
I
//SOUP// the value denoted by SPEAS, we would write //SOUP//:- SPea$. We
may also refer to the value of an output data item in a condition (e.g.
//SOUP//--SBean$).
!term! When an expression is complex and is used repeatedly, we have given it a mnemonic
name and included it in a dictionary at the end of the document. Such items are
enclosed in "!" brackets. Thus, !Dictionary Term! would be found in the dictionary
as an entry with an explanation such as "a term that is defined in this section." 3
*mode* We have described our systems in terms of classes of system states called modes.
Mode names are always enclosed in "" brackets. Thus, the appearance of 3
41
NRL REPORT 9194 Introduction
*SEARCH* would indicate that SEARCH was the name of one of the system
modes. Chapter 3 con -,ins a definition for eacz, system mode.
**mode** Certain system modes are described in terms of other modes. These so-called
"extended modes" are defined in Chapter 3.
0.2.2. Operators
To describe conditions of numeric items we use the following relational operators:
Operator Meaning
< less than
< less than or equal to
> greater than
> greater than or equal
0 not equal to
We use the following logical operators to form compound conditions in the standard way:
AND
OR
NOT
@T(condition 1)
describes any moment that condition I becomes true. For example, the expression @T(/RADALT,
< 0) denotes the eveii" "'ab the ii, ut RADALT no longer shows a positive value. It refers to
moments in time when this condition changes from false to true. Similarly, the expression
@F(condition 2)
describes the moment that condition 2 becomes false. For example. (F(/MOTOR =$On$) refers to
..
...
..
|I
Chapter 0 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE 3
the event of the condition /MOTOR/=$On$ changing :rom true to false. To describe an event in
which one condition changes at a time when another is true we write m
For example, @T(!Wheels Retracted!) WHEN (/RADALT/ = 0) refers to the event that the pilot
retracted the wheels while at zero altitude. This event only occurs if he condition !Wheels Retracted!
3
changes. For contrast consider @T(/RADALT/=O) WHEN (!Wheels Retracted!). The latter would
refer to events in which the value of /RADALT/ changes and the wheels are already retracted.* 3
Note the difference between
@T(Conditionl OR Condition2)
and
@T(Conditionl) OR @T(Condition2)
The former event occurs when the disjunction of the two conditions becomes true. Note that the
event does NOT occur when one condition becomes true if the other condition is already true. The
3
latter specifies a disjunction that is true whenever either event occurs.
Format:
Selector Table x: Description of ACT and BE
*LASTLNG* X SWarm$
I7
U
Chapter 0 ALSPAUGH. FAULK, BRITTON, PARKER, PARNAS. AND SHORE 3
Format:
Condition Table x: Definition of !Point!
MODE CONDITIONS
*Mi* A B
*M2*
*M3*
C D 3
*M4* E F
!Point! Vi V2
Two events appear so frequently that they are worth mentioning here: 3
@T(n mode) \VHEN(condition A)
- the event that condition A is true when the mode is entered.
@F(In mode)
- occurrence of one of the events that causes exit from the mode. These exit events are listed in
Chapter 3.
If either of these events occurs on a row corresponding to more than one mode. they refer to the
event of entering or leaving the modes taken as a group. Thus, if *Mi* and *M2* occur on the same
row of an event table, and @T(In mode) appears as one of the events on that row, then leaving *MI*
and entering *M2* does not count as an occurrence of that event (assuming no other mode transitions
took place in the interim).
I
I
I
NRL REPORT 9194 Introduction
Format:
Event Table x: When Zip is Turned On/Off
MODES EVENTS
*Mode2l* X @T(Condition B)
In *Mode24*, the function is requested at mode entry if condition E is true, and the Zip is turned off.
It is also requested at mode exit, when Zip is turned on. Zip is never turned on in *Mode21*.
Format:
MODES DEFINING CONDITIONS
*Model* A
*Mode2* B
I
0.3.4.1. Mode Transition tables
The Mode Transition tables describe the possible transitions between system modes. Each row
of the table describes an event that will cause a mode transition. To find the event(s) causing a transi-
tion from a mode *A* to a mode *B*. first find the entry for *A* under the left column labeled
"Current Mode." Then, in the *A* section of the table, find the row(s) with *B* in the righthand
column labeled "New Mode." Each row in that section describes an event causing a transition from
.A* to *B*.
Chapter 0 ALSPAUGH. FAULK, BRITTON, PARKER, PARNAS, AND SHOREI
The event corresponding to each row of the table is interpreted by looking at the column head-
ings. Each column heading names a condition. The entry in a row under a condition denotes how
that condition will be used in the expression of the event. An entry of "@T" under a condition X
means "@T(X)." An entry of "@F" means "@F(X)." Other entries correspond to the WHEN clause
of an event. An entry of "t" means "WHEN(X)". An entry of "f" means "WHEN(NOT X)". There
may be two or more "t" and/or 'f" entries in a row; this means that the WHEN clause is the con-U
junction of the corresponding conditions. Column entries that are not used for a particular event are
marked with a ..
oV 40
Current 4OOp.~~9
Mode ~ '4 '~~New Mode
OIMS fail*.......................................t - - - 'Kiag sl*
f -- -- t - 3a
= . . .. . t - - ____ ____I__I
The first row in the example above specifies a transition from mode *MAS fail* to mode 'Mlag si'
when the event
@T(/IMSFAIL/ = $Yes$) WHEN(/IMlSMODE/=SMag AI)
occurs. Similarly, the third row specifies a transition from 'IPo[ar*' to *Landaln' when the event
@T(!present position entered!)
WHTEN( !Data 23!0SSea$ AND /IM4SMODE/=$GndalS)
occurs.
10I
I
I
CHAPTER 1
1.0. INTRODUCTION
The A-7 software is required to run on the IBM 4PI TC-2 computer. This section provides an
introduction for those unfamiliar with the TC-2. A more complete description is given in references
(18,20).
II.I. MEMORY
The organization of the TC-2 memory is given in the diagram below: all addresses there are
hexadecimal. Each memory location is 16 bits long. Three-quarters of the locations are protected, or
read-only. Certain areas of memory may be used for special purposes. All of memory may be
addressed using base registers; the first one-sixteenth may also be addressed directly. Only the first
one-sixty-fourth, whose addresses may be expressed using just 8 bits, may be used by certain instruc-
tions.
100-IFF
I Unprotected 0-FFF
Unprotected 0-FFF
Direct addressed 0-3FF Registerstorage
IProtected 1000-3FFF
11
Chapter I ALSPAUGH, FAULK, BRITTON. PARKER, PARNAS, AND SHORE
1.2. ACCUMULATOR
The accumulator is in two parts, called the Areg and Qreg. The Areg is the accumulator for
single-precision instructions, and the Aeg and Qreg together are the accumulator for double-precision
instructions, with the Qreg acting as the low-order half of the accumulator. Most instructions take
U
one operand in memory and the other in the accumulator, and leave the result of the instruction in
the accumulator.
Subroutine linkage may be done using BIAL (branch indirect and link). It is like BIA but addi-
tionally places the current address in a base or link register, so that a return from the subroutine may
be done with a BIA or B using that pointer.
C (compare) is a three-way conditional branch; if the Areg is greater than. less than. or equal to
the contents of a location in memory, it branches to the next instruction, the second instruction fol-
lowing, or the third instruction following, respectively.
T (tally) is an instruction for indexed loops. It increments the contents of a location in memory;
if the result is zero, it branches to the second succeeding instruction, otherwise it continues to the next
instruction.
1.11. INTERRUPTS
The TC-2 has two levels of interrupts, level 0 and level 1: if two interrupts are simultaneous, the
level 0 is accepted first. When an interrupt occurs, a number of things occur if it is not masked:
(1) A bit that identifies the cause of the interrupt is set: these bits may be read with an I/0 com-
mand (see "Synchronous L"O", below).
(2) The wait state bit in the CPU status word is cleared to 0.
(3) The current value of the instruction counter is saved at location 10 (level 0) or 12 (level 1) hexa-
decimal.
13
U
Chaptcr 1 ALSPAUGH, FAULK. BRITTON. PARKER. PARNAS. AND SHORE
(4) The next instruction executed is the one whose address is given at location 11 (level 0) or 13
(level 1) hexadecimal.
Masked interrupts remain pending until they are unmasked using the CPU status word.
I
14
I
I
NRL REPORT 9194 The TC-2 Computer
TC-2 I/O is most unusual. It was designed specifically for the A-7 and the channels are tailored
to specific I/O devices; instruction sequences for each channel are distinctly different. Some I/O dev-
ices require a succession of commands; some require a relatively long wait for input or output, and
some have their data available for input for only a short time.
Some I/O devices are part of the TC-2 itself. Interrupts set identifying bits that may only be
read by an I/O instruction. The "Go/No Go counter" (see "Built-in test equipment and the DL4G-
NOSE instruction", above) may only be set with a WRITE command. Two other counters and the
IMS control registers are only accessible through READ and WRITE commands.
Of the eight channels, four are currently used for output (0,4,6,7) and seven for input (all but 5).
Two channels may be used in communicating with a single device; e.g., channel 0 is used to send sin-
gle discretes to the Doppler Radar, and channel 1 is used to receive numerical inputs from the same
device. The remainder of this section summarizes each channel.
1 1.15.1. Channel 0
Channel 0 is used for communication with relatively low speed discretes such as LMS mode
switches. It is also used to read and write the interrupt status registers and to communicate with the
* various counters.
1.15.2. Channel 1
Channel 1 is used for communication with the Serial Input Data Register (SIDR). This register
is connected with the Doppler Radar, Forward Looking Radar, and digital Shipboard Inertial Naviga-
tion System (SINS). Any one of those devices can write data into the SIDR but will do so only on
request. The request is made over Channel 0, and it is vital to make only one request and wait for the
complete response before making another. If two devices try to write into the SIDR at once, no error
will be detected but meaningless data will be produced. When data are written into the SIDR, identi-
fying data are written into the Serial Input Address Register, which is read over Channel 2. Reading
the SIDR transfers the contents to the accumulator and clears the contents of the SIDR. To obtain
useful data, the contents of the SIDR should be cleared before a data request.
Interrupts are generated during the read sequences for the following input data items. The
interrupts indicate that the device has loaded the Serial Input Data Register and the Serial Input
Address Register.
Reading from the Doppler radar over Channel 1 is especially complex because the Doppler
always sends its data in sets of three words. It may be necessary to read the register three times even
if only one of the items is wanted. Further. the data arrive at a rate that is independent of the com-
puter. The need to clear the register before the next word arrives imposes severe time constraints on
the programs.
I
I
Chapter I ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
1.15.3. Channel 2
Channel 2 is used for communication with the Serial Input Address Register (SIAR). The SIAR
contains bits that identify the source of the data in the Serial Input Data Register. Unfortunately, the
address bits do not unambiguously identify the data source; to determine the source, one must also use
information about the most recent request made over Channel 0. 3
Bit 0: Data Valid Set to 1 when SIDR contains a valid data word.
Bit 1: Data Parity Set to 1 hen the Data Word in the SIDR has passed
1.15.5. Channel 4 i
Channel 4 is used for the IMS torque and accelerometer registers.
Dealing with the torque registers is difficult for two reasons. First, there is never a zero torque $
on the IMS. One must alternate between positive and negative torques to maintain the IMS in its
present state. Second, one must be aware of the values in the torque counters before setting new
values. These values change periodically. If the count is about to change, it is necessary to wait
before sending data to the counters. A Channel 0 input bit /DIMWC/ warns of this possibility and
U
must be checked before changing the torque counters.
Each READ of an accelerometer register clears it. 3
1.15.6. Channel 5
Channel 5 is intended for Loran communication. Channel 5 is not used presently.
1.15.7. Channel 6 3
Channel 6 is devoted to communication with the TC-2 panel. Pushing a digit, I-YBD,
MARK, or ENTER button generates an interrupt signal and sets a bit to indicate which button has
been pushed. A bit will be I for each button that has been pushed since the last time the bits were
read. The bits are cleared when read. Response is time critical although the time periods involved
I
are relatively long. Delays in reading can result in missing a Panel Interrupt. There can be ambiguity
about the sequence in which buttons were pushed if two buttons have been pushed since the last time
that the interrupt was serviced.
1
I
16
I
I
NRL REPORT 9194 The TC-2 Computer
1.15.8. Channel 7
Channel 7 is used for reading data that come from other aircraft systems in analog form. To
read one of these signals one must transmit a request to the signal converter with a READ command,
wait for a Data Ready interrupt, and then issue a READ that transfers the data into the accumulator.
Because the data received by the last READ in the sequence are determined by the request expressed
in the first READ, care must be taken to assure exclusive use of the device during the period of time it
takes to complete a sequence. For angle inputs, the second READ gets the sine and an additional
READ gets the cosine. In this case, there is no delay for conversion before the additional READ.
The signal converter data conversion times for the two types of signals requiring input conver-
sion are 1.373 to 3.0 ms for synchro to digital data and 135 to 300 ps for DC voltage to digital data.
These timing characteristics apply to the following data items, which generate Data Ready interrupts:
3 Channel 7 Output is somewhat simpler: data are transferred to the converter by a channel 7
W\RITE command that specifies the destination device. One must wait for completion of the conver-
sion before starting another output operation. Conversion Complete is signaled by an interrupt.
5 The Signal Converter data conversion times for the two types of signals requiring output conver-
sion are .188 to 1.8 milliseconds for digital to synchro data and 1.46 to 3.2 milliseconds for digital to
3 DC voltage data. These timing characteristics apply to the following data items. which generate
conversion complete interrupts:
17
I
I
CHAPTER 2
I
Input and Output Data Items
I
I
2.0. INTRODUCTION
This chapter describes the individual data items communicated between the TC-2 and other
3
devices in the aircraft. There is a separate subsection for each hardware device. Within each subsec-
tion, input items precede output items. The data items are alphabetized within each category.
Provided for each data item are (a) a standard acronym enclosed in brackets (/input/ and
3
//output//) to be used throughout the document and during system development; (b) a verbal
description of its significance or meaning in terms of the device with which it is associated; (c) charac-
teristics of each numerical data item, such as range, accuracy or mnemonic names enclosed in brackets
($value$) for the possible values of each non-numerical data item; (d) the format of the data represen-
tation; and (e) the TC-2 instruction sequence that must be executed in order to read the item in or
transmit it to the external device. For numerical data items, the range gives the maximum and
minimum values encountered in actual use. This may be smaller than the range of values that can be
I
represented. Where such information is available and meaningful, the document describes any timing
restrictions that must be observed. 3
2.0.1. Accumulator as Default Data Item Location
An input data item is always located in the accumulator after an input instruction sequence.
Except for cycle-steal outputs, an output instruction starts with the output value in the accumulator.
18
NRL REPORT gg4 Introduction
stating values for scale and offset. In all cases, the least significant bit of a numerical bit field is the
highest-numbered (rightmost) bit, and that bit represents one indicated unit.
In some cases, the exact scale factor for an input data item is not known, but an approximate
value of 1/scale is available. In these cases, we will give the approximate value for 1/scale using the
symbol :-: to mean "approximately equals."
For example, the indicated representation of the Doppler Drift Angle input data item.
/DRFTANG/, is a 14 bit positive count with scale - 175 and offset = 9375/175. The standard units
of /DRFTANG/ are degrees. Thus, an indicated value of 9375 corresponds to 0", and a value of 9200
corresponds to -1 *.
Many of the data items are described in terms of particular units of measurement, such as
degrees, feet/second, or knots. It should be clear that by altering the scale (and offset) the data items
could be described in different units. The units used here were chosen for convenience in writing this
document. The implementor of programs using these data items should alter the scale to produce the
values in the appropriate units.
19
Chapter 2 ALSPAUGH. FAULK, BRITTON, PARKER, PARNAS, AND SHORE
The following data items affect the values read in for /ACTESTCOS/ and /ACTESTSIN/. I
After the WRITE instruction for these data items, if the conversion -omplete interrupt does not occur
within 3.2 msec, a hardware error is indicated.
//RNGUNIT// /'/RNGTEN//
//RNGHND// //ANTSLAVE//
,/STEERAZ// //GNDTRK//
//STEEREL// !/BRGDEST//
//SPAREI// //SPARE2// 3
I
I
I
I
I
I
I
I
I
20
NRL REPORT 914 Inertial Measuremeift Set (MS)
1 3 2
G N071.INERTIAL
WMA GVA R
OQO10ENI W- E
GNO
G.~ MAG SLS
-ALIGN 0 LATITUDZ PUSH
OFF--- GRID T
I ( N\ TURN"4
2
I
21
1
Chapter 2 ALSPAUGH. FAULK. BRITTON, PARKER, PARNAS. AND SHORE
I
I
I
I
I
I
I
U
I
I
INRL REPORT 9194 Inertial Measurement Set (IMSJ
I Description: /XGYCNT/, /YGYCNT/, and /ZGYCNT/ indicate the current value of the two least
significant two bits of the corresponding torque counters. See ,/XGYCOM//, ,',YGYCOMI//, and
/ZGYCQM// for more information.
Characteristics of values:
I Value encoding:
Value Bit reresentation Toraue counter bits
I WM
BS
SOS
10
11
00
00
01
10
SDS 01 11
Instruction sequence: READ # (Channel 4) (valid only if /DIMWC/ = $Ready$)
# = 144 for XAxis
#= 136 for YAxis
#= 152 for Z Axis
Data representation: Bits 13-14
Timing characteristics: See /DIWC/ and //XGYCOM//, //YGYCOM//, ///ZGYCOM.k//
Comments: When the torque counter is toggling (see //XGYCONI//, etc.), the values SASkand $D$
will be read when the torque counter values are 0 and -1 respectively.
I2
Chapter 2 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS. AND SHORE
24I
3NRL REPORT 9194 Inertial Measurement Set IS)
Characteristics of values:
Value encoding:
SOffnone$ (00000) Occurs when the switch is off or between two positions.
SGndal$ (10000)
$Norm$ (01000)
$InerS (00100)
$Grid$ (00010)
SMagslS (00001)
Instruction sequence: READ 24 (Channel 0)
I2
I
Chapter 2 ALSPAUGH, FAULK. BRITTON, PARKER, PARNAS. AND SHORE
I
U
U
I
I
I
I
I
26
I
I
I NRL REPORT 9194 Inertial Measurement Set (DIS)
I
I
I
I
I
I 27
I
Chapter 2 ALSPAUGH, FAULK. BRITTON, PARKER, PARNAS, AND SHORE
After @T(//COMPCTR// = SOffS), these data items are not updated by the IMS. Hence. /XVEL/.
/YVEL/, and /ZVEL/ remain 0 after they are read.
Characteristics of values:
Units: fps I
Range: varies based on particular IMS and scale.
Max for coarse: -19.456 to 19.418.
Max for fine: -. 19456 to .19418.
Maximum derivative: varies per IMS
Max for coarse: 380 fps2
2
3
Max for fine: 3.8 fps
Instruction sequence: READ * (Channel 4) valid only if //COMPCTR//ff SOnS
• 129 for Xp Axis
3
• = 130 for Yp Axis
• 132 for Zp Axis
Data representation: 10-bit two's complement number, bits 6-15; scale = !inc vel scale!: offset -
!acc bias!. (See //IMSSCAL// for scale factors to calculate incremental velocities.)
2
I
I
I
I
28
I
NRL REPORT 9194 Inertial Measurement Set ILMS)
Angular Accuracy:
Magnetic Heading: ±0.25
Pitch Angle: ±0.1"
Roll Angle: ±0.1
True Heading: ±0.1
Maximum derivative:
Roll: 300 degis;
29
Chapter 2 ALSPAUGH, FAULK. BRITTON, PARKER, PARNAS, AND SHORE U
Pitch: 60 deg/s;
Heading 200 deg/s 3
Maximum second derivative:
13 bit two's complement number, bits 0-12; bits 13-15 - 0. Scale - 4096; offset - 0.
Timing characteristies: Sychro (analog) to digital conversion (see §1.15.8). I
Comments: If the Xp axis and Yp axis are aligned with (true) East, and North respectively, then
/THDGCOS/ and /THDGSIN/ determine true A/C heading. If the Zp axis is aligned with vertical
(Z positive in the Up direction), then /ROLLCOSI/ and /ROLLSINI/ determine A/C roll angle and
/PCHCOS/ and /PCHSIN/ determine A/C pitch. Roll is positive when the right wing is down and
I
pitch is positive when the nose is up.
The factor K, which is close to 1, is introduced by the synchro converter. Techniques to recover A
from K x SIN(A) and K x COS(A) for small angles A are discussed in Ref. 6, §2.
I
The scale is given assuming K - 1. 1
I
I
I
I
30
I
NRL REPORT g194 Inertial Measurement Set (MItS)
3 Class: DOW2
Acronym: //AUTOCAL//
Hardware: Inertial Measurement Set
U Description: //AUTOCAL // =
Supply in the left hand avionics bay.
Characteristics of values:
$On$ turns on the AUTO /CAL light on the IMS Adapter/Power
I3
I
Chapter 2 ALSPAUGH. FAULK. BRITTON. PARKER. PARNAS. AND SHCRE
33
I
Chapter 2 ALSPAUGH, FAULK, BRrrTON, PARKER, PARNAS. AND SHORE
I
2.1.1.12. Gyro-torquing commands
while true do
begin
if (count > 0)
then torque:- positive: count:- count -1;
else torque:= negative: count:= count +1 fi
pause until @T(/DIMVC/ = $Changing$)
end;
34
I
I
NRL REPORT gg4 Inertial Measurement Set (IS)
Resolution: I
Instruction sequence: WRITE * (Channel 4) (valid only when iDIVC/ = $Ready$) (where * -
129 for X Axis, 130 for Y Axis, 132 for Z Axis)
Data representation: 4 bit two's complement number. bits 11-14; bits 0-10 and bit 15 are not used.
Scale = 1, offset = 0.
Timing characteristics: See /DIMWC/. See also Description and Comments.
Comments: Because //XGYCOM//, !/YGYCOM//, and //ZGYCOM// reset the current values of
the torque counters, and since only two bits of information are available about the current values of
the four bit counters, pulses can be "lost" if care is not taken. (See /XGYCNT/, /YGYCNT/. and
/ZGYCNT/ for more information.) In general, it is easiest to wait until a counter is toggling before
resetting it.
An additional problem is the need to make sure that an equal number of positive and negative
torquing pulses are output during toggling so as not to introduce an unintentional bias. This can be
accomplished by determining the current value of the torque counter (-1 or 0) and resetting the
counter so that the desired number of positive or negative pulses is output prior to the counter return-
ing to the value it had at the time it was reset. The action to be taken in each case is given in the fol-
lowing table:
This table can be understood by referring back to the pseudo-code and diagram given in the Descrip-
tion. In each case, the time required to return to the starting value (left most column) is 5n ms.
From the table, it can be seen that the appropriate reset value is equal to the sum of the desired
number of pulses and the current (toggling) value of the counter. During toggling, the current value
of a torque counter (-1 or 0) can be determined through use of /XGYCNT/, /YGYCNT/, or
/ZGYCNT/. For example. if the X axis torque counter is toggling, !,.GYCNT/ = $A$ will hold
when the counter value is zero, and /XGYCNT/ = $D$ will hold when the counter value is -1. Note
that when the counter is not toggling. ,'XGYCNT/ does not contain sufficient information to deter-
mine the reset value.
Note: In the current OFP. the IMS equations assume an opposite rotation sense for X and Y than
defined undpr Description. The results of the calculation are negated (thus converting into the present
standard reference frame) before being output to the device.
35
I
Chapter 2 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS. AND SHORE
Note: The above example of velocity calculation does not show the adjustment required for accelerom-
eter bias. I
3
U
U
I
I
I
I
36
I
RLREPORT 9194 Inertial Measurement Set (IMS)
37
Chapter 2 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
38I
NRL REPORT g194 Inertial Measurement Set (IMS)
39
I
Chapter 2 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
I
I
I
I
I
I
I
40
I
NRL REPORT g2g4 Air Dus Computer (ADC)
41
I
Chapter 2 ALSPAUGH. FAULK. BRITTON. PARKER, PARNAS, AND SHORE
I
U
I
U
I
I
I
I
42
I
NRL REPORT 9194 Air Daa Computer (ADC)
I
I
I
I
I
I
I
I
! 43
I
Chapter 2 ALSPAUGH, FAULK, BRITTON. PARKER, PARNAS, AND SHORE
I
I
I
I
i
I
I
I
I
I
44I
NRL REPORT 9194 Forward Looking Radar (FLR)
ERIEVDGAIN BI 0
Figure c.1.3-a
420
Chapter 2 ALSPAUGH. FAULK, BRITTON, PARKER, PARNAS, AND SHORE
I
I
I
I$
Il
I
46
I
NRL REPORT 9194 Forward Looking Radar (FLR)
Data representation: 13-bit positive number, bits 0-12; bits 13-15 = 0. Scale = 1/20 = .05; offset
-=0.
Comments: Note that the FLR Slant Range and the DRS status have the same device address
(00001).
47
I
Chapter 2 ALSPAUGH, FAULK, BRITTON. PARKER, PARNAS. AND SHORE
I
I
U
I
I
I
I
I
I
I
I
48
i
NRL REPORT 9194 Forward Looking Radar (FLR)
49
I
Chapter 2 ALSPAUGH. FAULK. BRITTON, PARKER. PARNAS. AND SHORE 1
2.1.3.5. Cursor azimuth
The display range is only -45 to +45 *. The azimuth cursor is removed from the display when
//CURAZCOS// is set to -1. Has no effect unless //CURENABL// = SOnS.
Characteristics of values:
Units: None
3
I
Range: -1 to +1
Resolution: 1/4096
Data representation: 13-bit two's complement number, bits 0-12; bits 13-15 not used. Scale =
4096: offset = 0.
Instruction sequence: Cycle Steal Channel B. Word Identity Code: i
//CURAZCOS//: OC
//CURAZSIN//: 08 3
I
I
I
I
I
I
I
50i
|I
I
3 NRL REPORT 9194 Forward Looking Radar (FLR)
I
I
i
I
I
I
I
I
I
1
I
I 51
I
Chapter 2 ALSPAUGH, FAULK. BRITTON. PARKER. PARNAS. AND SHORE I
2.1.S.7. FLR cursor position
53
i
Chapter 2 ALSPAUGH. FAULK, BRITTON. PARKER. PARNAS. AND SHORE
IU
I
U
I
NRL REPORT 9194 Forward Looking Radar (FLR)
55
I
Chapter 2 ALSPAUGH. FAULK. BRITTON. PARKER. PARNAS. AND SHORE
II
I
I
!
I
I
I
.56
1
INRL REPORT 9194 Forward Looking Radar (FLR)
57
I
Chapter 2 ALSPAUGH. FAULK, BRITTON, PARKER, PARNAS, AND SHORE I
2.1.4. Head-Up Display (HUD)
The Head-Up Display (HUD) (Fig. 2.1.4-a.) is an electro-optical device that projects attack and
flight information in symbolic form into the pilot's forward field of view. All azimuth and elevation
angles of HIUD symbols are defined with respect to the HUD Optical Reference Axis (ORA). The
HUJD is mounted so that the pilot sees the ORA as parallel to A/C boresight. The HUD displays all
symbols so that they appear to be at infinite distance from the A/C. The position of the center of
each symbol is described in terms of a line from a point on the ORA to the apparent location of the
symbol. The azimuth is the angle between the projection of this line on the X.-Y. plane and the
ORA. The elevation is the angle between the projection of this line on the Y Z. plane and the ORA.
Because the points are apparently at infinite distance, the angles are not sensitive to the exact location
of the reference point on the ORA and one may assume that it coincides with the pilot's eyes.
The HUD refreshes display symbols at the rate of 50 times/s. and does not display symbols that
are out of the display range.
I
Point on the I
ORA
3
Off Altitude
SCAM S At? TIST Switch
~I iiLi
Head-up display
Figure 2.1.4-a j
I
I
58!
NRL REPORT g194
Head-Up Display (HUD)
Ii
E1-Upper Solution
Cue
+----Z4er Soluti
0 , Cue
0 4 -- Aimtng Symbol
HUfD cues
Figure 2 1.4-c
i
Chapter 2 ALSPAUGH. FAULK. BRITTON. PARKER, PARNAS. AND SHORE
E xFlashing
Pullup Cue
HUD pullup
Figure cue
2.1.4-d
t
S I
Warning
Symbol o Barometric Altitude Indicator
ai (3750 feet)
60
NRL REPORT 9194 Head-Up Display (HUD)
..
.....
.
I
Chapter 2 ALSPAUGH. FAULK. BRITTON. PARKER. PARNAS, AND SHORE
Elevation angles are angles in the A/C Y1-Za plane and are positive if upward from the ORA when I
looking at the HUD from the pilot's viewpoint.
Azimuth angles are in the A/C X 8-Y,plane and are positive if to the right of the ORA when looking
at the HUD from the pilot's viewpoint. See Fig. 2.1.4-c for pictures of the symbols and Ref. 33g for
more information.
Characteristics oa values:
Units: Degrees
Range: ±16
Accuracy: ±5 milliradians (worst case)
Resolution: 1/128
Maximum derivative: ±30 deg's
Instruction sequence: Cycle Steal Channel A. Word Identity Code:
/ASAZ//: 03. ,,,.' /: 04. I
,'ASLAZ, 07. ,'ASLEL/': 08.
'FPMAZ
'LSOLCUAZ,',"
'PUACAZ '
01.
09.
OD,
/FP.fELi,':
'LSOLCUEL,,
'PUACEL,' .
02.
OA.
OE.
I
,USOLC'UAZ,',: OB /USOLCUEL/,. OC
Data representation: 12-bit two's complement number, bits 0-11: bits 12-15 nc. used. bcale
offset = 0.
= 128; 1
62
NRL REPORT g194 Head-Up Display (HUD)
//ROLLCOSH// and //ROLLSINH// control the angular rotation of the horizon and pitch lines, the
flight director symbol, and the landing director. The angles of the horizon/pitch lines are zero when
the lines are horizontal (parallel to A/C X.-Y1 plane) with the strike marks on the ends pointing up.
They are measured CCW when looking at the HUD from the pilot's point of view. See Fig. 2.1.4-f for
a picture of the horizon/pitch lines, and Ref. 33g for more information.
Characteristics of values:
Units: None
Range: -1 to +1
Accuracy: ±5 milliradians (worst case)
Resolution: 1/2048
Maximum derivative:
ASL Angle: ±180 deg/s
Roll Angle: ±120 deg/s.
Data representation: 12-bit twos complement number, bits 0-I1: bits 12-15 not used. Scale =
2048: offset = 0.
63
I
Chapter 2 ALSPAUGH, FAULK. BRITTON. PARKER. PARNAS. AND SHORE
The bar height indicates (//BAROHUD// MOD 1000) on a scale from 0 to 1000. 1
Characteristics of values:
Units: None 3
Range: -1.000 to +50.000
Resolution: 12.207
Maximum derivative: :10.000/min. I
Instruction sequence: Cycle Steal Channel A. Word Identity Code 18
Data representation: 13-bit two's complement number, bits 0-12; bits 13-15 not used. Scale =
U
I
I
645 I
I
I
I
(34
I
NRL REPORT 9194 Head-Up Display (HUD)
Output data item(s): Flight Director - Azimuth (Heading Error Cue Azimuth)
Acronym: //FLTDIRAZ//
Hardware: Head Up Display
Description: //FLTDIRAZ// controls the azimuthal placement of the Flight Director symbol. The
azimuthal angle is measured in the X -Y plane and is positive if the Flight Director symbol is to the
right of the ORA when looking at the HUD from the pilot's viewpoint. The Flight Director Symbol is
shown in Fig. 2.1.4-b.
Because of hardware constraints, the flight director is not displayed if a master function switch is
selected.
Characteristics of values:
Units: Degrees
Range: -8 to +8
Accuracy: ±5 milliradians (worst case)
Resolution: 1/256
Maximum derivative: ±30 deg/s
Instruction sequence: Cycle Steal Channel A, Word Identity Code: OF
Data representation: 12-bit two's complement number, bits 0-11: bits 12-15 not used. Scale = 256:
offset - 0.
65
I
Chapter 2 ALSPAUGH, FAULK, BRITTON. PARKER, PARNAS, AND SHORE
Value encoding:
//HUDWARN// SOnS (1); SOS (0) bit 0
//HUDPUC//
//HUDVEL/,i
//HUDFPM//
SBlink$ (1);
SOffS (1);
$Blink$ (1);
SOffS (0)
$On$ (0)
$ConstantS (0)
bit
bit
bit
1
2
3
I
/"/HUDAS/i $Of$ (1); SOnS (0) bit 4
//HUDSCUE/, SOffS (1); $On$ (0) bit 5
/ /HUDASL/ SOfS (1): SOnS (0) bit 6
I
I
I
66
I
NRL REPORT 9194 Head-Up Display (HUD)
67
I
Chapter 2 ALSPAUGH. FAULK. BRITTON, PARKER, PARNAS. AND SHORE
I
I
I
I
I
I
I
I
I
68
NRL REPORT 9194 Head-Up Display (HUD)
The pointer displacement from the bottom of the vertical velocity scale is a linear function of the out-
put values. The value -1000 results in zero displacement, and the value +1000 results in maximum
displacement. The value that may be output has a range of ±10,000. but only ±1000 is displayed.
That is, the pointer on the HUD moves off the - ale if the value is greater than 1000, but is limited to
the field of view.
Data representation: 12-bit two's complement number, bits 0-11; bits 12-15 not used. Scale =
2048/10000 = .2048; offset = 0.
Comments: //VERTVEL/i is displayed when the HUD detects landing mode (not a software condi-
tion). //VTVELAC// is displayed at all other times.
69
I
Chapter 2 ALSPAUGH, FAULK. BRITTON, PARKER. PARNAS, AND SHORE 3
2.1.5. Armament Station Control Unit (ASCU)
The Armament Station Control Unit (ASCU) provides control and release functions for weapons
and external stores.
Also included in this section are several cockpit switches that provide input to both the TC-2
and the ASCU. These switches are shown in Fig. 2.1.5-a. 5
I
Stations Master Guns Retarded
selected Arm Selected Weapon
1
I
I
I
Cockpit switches
Figure 2.1.5-a
1
I
I
I
70 I
NRL REPORT 9194 Armament Station Control Unit
71
I
Chapter 2 ALSPAUGH. FAULK. BRITTON, PARKER, PARNAS. AND SHORE
I
I
I
I
I
I
I
I
I
I
I
I
NRL REPORT 9194 Armament Station Control Unit
73
I
Chapter 2 ALSPAUGH, FAULK. BRITTON. PARKER. PARNAS. AND SHORE
I
I
I
I
I
I
I
I
I
I
i-I
NRL REPORT 9194 Armament Station Control Unit
75
I
Chapter 2 ALSPAUGH. FAU'LK, BRITTON. PARKER. PARNAS. AND SHORE
I
I
I
I
I
I
I
I
1
76 I
1
NRL REPORT 9194 Armament Station Control Unit
iI
I
I
I
I
I
I 7
I
Chapter 2 ALSPAUGH, FAULK. BRITTON, PARKER. PARNAS, AND SHORE
8
I
I
1
I
I
U
I
I
1
I
78
I NRL REPORT g194 Projected Map Display Set
Cassettes within this specification are characterized by six parameters giving for Area A and
Area B the following information: longitude of the center of the map area, the latitude of the south-
ernmost part, and the map orientation (whether long axis is north-south or east-west).
I
!
i
I
I
I
I
I
I
I
I
I 7
Chapter 2 ALSPAUGH. FAULK. BRITTON, PARKER. PARNAS. AND SHORE
IMOLES
N UP
VAN NORM %3 .
801
NRL REPORT 9194 Projected Map Display Set
81
Ch&pter 2 ALSPAUGH. FAULK, BRrrTON, PARKER. PARNAS, AND SHORE
8
I
I
I
I
0
I
I
I
1
I
NRL REPORT 9194 Projected Map Display Set
83
Chapter 2 ALSPAUGH. FAULK. BRITTON, PARKER. PARNAS. AND SHORE
Characteristics of values:
Value encoding: $20$ (0); $80S (1) 3
Instruction sequence: READ 16 (Channel 0)
Data representation: Discrete input word 6. bit 0. i
8
I
I
I
I
II
I
I
I
84
ii
NRL REPORT 9194 Projected Map Display Set
85
Chapter 2 ALSPAUGH. FAULK. BRITTON, PARKER. PARNAS. AND SHORE
87
Chapter 2 ALSPAUGH. FAULK. BRITTON. PARKER. PARNAS. AND SHORE
8
I
I
!
I
I
U
I
U
U
88
• iI
• m |
I
I NRL REPORT 9194 Projected Map Displ, - -t
I
I
I
I
I
I
I
I 89
Chapter 2 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
I
3
I
I
I
I
U
U
gO
I
I
,NRL REPORT 9194 Projected Map Display Set
I described in Ref. 33h. 0.510464 inches is the vertical center of the filmstrip.
1
I
I
I
I
I
I
I
I
• •mm
• 91 ll
Chapter 2 ALSPAUGH. FAULK, BRITTON, PARKER, PARNAS, AND SHORE
Digits N MARKIJ~rD
Peet ALAT *LONG DEST, I RNG/BRG Mode
Windw ElPushbutton
Mark Fl-o
Pushbut ton '- ~ , ~ FLY TO ThIute
Inlftestr
Switche
KeOFF
Figure 2.1.7-aI
92
NRL REPORT 9194 TC-2 Panel
I
I
I
I
I
I
I
I
I
I
Chapter 2 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
$4 (1011);
$55 (1010);
$6$(1001);
75 (1000);
1
$85 (0111);
$95 (0110)
I
(Channel 6)
Instruction sequence: READ 200
Data representation: TC-2 Panel Input Word 2, bits 2-5
Timing characteristics: When the thumbwheel is moved, the previous setting is retained until the
next position is reached. There is no momentary "0"value.
II
I
I
l
l
U
94
I
NRL REPORT 9194 TC-2 Panel
95
I
Chapter 2 ALSPAUGH, FAULK, BRITTON. PARKER, PARNAS. AND SHORE
aa I II I II
NRL REPORT 9194 TC-2 Panel
97
Chapter 2 ALSPAUIGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
98I
N'RL REPORT 9194 TC-2 Panel
Value encoding:
$None$ (000000),
SPRESPOSS (100000),
$DEST$ (010000),
MARKS (001000),
SRNG/BRG$ (000100),
SDBHTS (000010),
gALTMSLP$ (000001)
99
I
Chapter 2 ALSPAUGH, FAULK, BRITTON. PARKER, PARNAS, AND SHORE
1
I
I
I
I
I
I
I
I
I
I
100
-n =.=,
iNlin. ilmnml
I An I II l
NRL REPORT 9194 TC-" Panel
Characteristics of values:
Value encoding:
101
I
Chapter 2 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
Value encoding: ;
$DATA$ (1111);
$1HDS (1110);
$RADARS (1101);
SFLYOVER$ (1100);
$LORAN$ (1011);
STACL-L$ (1010);
$TACMV$ (1001);
$SMS-HUDS (1000);
SSINSX-Y$ (0111);
$Z-DHDGS (0110)
C, G. and F are horizontal line segments. A. B. D and E are vertical line segments.
Characteristics of values: Each data item has 27 possible values, each represented by ${string}$,
where string is a string composed of any subset of the seven letter codes (above) in alphabetic order.
For example, //LWVDIGI// = ${CDEFG}$ displays a 3 in the first digit.
For convenience, we also define the following synonyms for commonly occurring values of the
data items namely, for displaying the ten digits and the twenty-six letters: $05, 15. $ ... $95, $A$,
$13$, S$ ... Z. See Ref. 18, Table 5.2-14 and Fig. 5.2-3 for segment definitions of the synonyms.
The special value SBank$ means that no segment. are lit.
Timing characteristics: The lights for a digit stay lit until the next WRITE a for the digit. or till
the next WRITE 192 (see below).
Instruction sequence: WRITE 192 (Channel 6)
U 103
Chapter 2 ALSPAUGH, FAULK, BRITTON, PARKER. PARNAS. AND SHORE
The instruction above causes the value in the accumulator to be written out to all Channel 6
outputs simultaneously. Thus, it acts as a simultaneous execution of WRITE *, where * is 194, 196.
198 200, 202, 204, 206, 208, 210. 212, and 214. Other output data items affected by this instruction
are //UWDIGn//, //MARKWIN//, the other panel lights.
I
I
I
U
I
I
I
U
I
i
U
I
I
U
I
104
• m m| |I
NRL REPORT 9194 TC-2 Panel
I
I
I
I
I
1
I
I
I
I
I
i 105
Chapter 2 ALSPAUGH. FAULK, BRITTON, PARKER, PARNAS. AND SHORE
10I
I
NRL REPORT g914 TC-2 Panel
I 3 'i5£r.7
3 73
I '
I
Lights on TC-2 panel
* Figure 2.1.7-b
I Characteristics of values:
Timing characteristics: The specified lights stay on until the next WRITE 200 or WRITE 192.
Comments: Light 14 is tuined on if either 'ENTLIT/ 1 f SOnS or .'/KELIT = .On$
See L\\rDIGI//, etc.
I
I
I
I
i 107
Chaptar 2 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
Data representation: The seven bits are located in the output data word according to the
table below:I
bits TC-2 Panel Output WVord
//UWDIGI// 0-6 6
///UWDIG2// 8-14 6I
//UWDIG3// 0-6 7
//UWDIG4// 8-14 7
//UWDIG5// 0-6 8
//UWtDIG6// 8-14 81
Timing characteristics: The lights for a digit stay lit until the next WRITE Sfor the digit, or until
the next WRITE 192.I
Comments: See I/LWDIG 1//, etc.
108
NIRL REPORT 9194 Built-In Test Equipment (BITE)
2.1.8.1. Introduction
The Built-In Test Equipment hardware provides features that allow programs to test for and
identify TC-2 computer and hardware interface malfunctions. The BITE hardware also has functions
that operate automatically and independently of any written program code: they will not be described
here. Further information about BITE hardware can be found in Refs. 18. 19, and 20.
The BITE interface to the software consists of the following:
* A set of commands to cause the BITE to wrap IO data. to turn on computer fail displays. to send
computer fail indicators to other hardware, and to set certain output data items to failsafe values.
e A GO/NO-GO counter that signals situations where program control may be lost.
* A circuit that signals when the program attempts to write into the protected area of storage.
i Check values generated by the hardware from sets of outputs.
2.1.8.2. BITE functions
The Input/Output Wrap causes an output data path to be connected or "wrapped" to an input
data path. This allows both paths to be tested by writing out a value on the output path and check-
ing to see that the same value can be read on the input path.
In case of computer malfunction, the failsafe feature prevents dangerous output signals from
being sent inadvertently by setting critical output data items to a predetermined state. The critical
output data items are !/FIRRDY/,. ,/BMBREL/i, 'CURENABL/i, . 'ANTSLAVE//,
.'//IMSNA//, and //COMPCTR,'./.
A GO/NO-GO Counter is a real-time readable and resettable timing counter that increments
indr idently of any program action. This counter can be used both as a system clock and as a
time- detector. The counter will overflow after 1.3 seconds if it is not reset. This overflow condi-
tion au matically generates a level-one interrupt and has the same hardware effect as BITEL :=
$FORCEFAILS and //BITE2// - SDETECTNMkL$, except that the LRU malfunction flag is not
tripped. This counter is used to detect improper OFP execution sequences. infinite iterative loops, and
I 109
Chapter 2 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS. AND SHORE
2.1.8.6. AC self-test
1
I
3
110
I
I
NrRL REPORT 9194 Built-In Test Equipment (BITE)
A, Octant N. D.
0' - 45" 1 tan A, 1
45' - 90" 2 1 cot A.
90" - 135" 3 1 -cotA,
135' - 180' 4 tan A. -1
180" - 225" 5 -tanA -1
225' - 270" 6 -1 -cot A.
270 - 315 7 -1 cotA.
315 - 360" 8 -tan A 1
Characteristics of values:
Units: None
Range: -1 to +1
Resolution: 1/4096
Instruction sequence:
READ 255 (Channel 7) (Reset Signal Converter if not already done)
READ 224 (Channel 7) (Request Signal Converter to start conversion)
Test Carry Indicator for 0 - Request acknowledged.
If not, read sequence not successfully initiated
When DATA READY interrupt occurs, conversion complete
READ 225 (Channel 7) (SIN)
Save Accumulator value
READ 255 (Channel 7) (COS) (Also resets Signal Converter)
Data representation: 13-bit two's complement number, bits 0-12; bits 13-15 Scale - 4096, offset =
0.
Timing characteristics: Synchro (analog) to digital conversion, see §1.15.8.
Comments: A delay of 4 seconds should be allowed between writing out //RNGUNIT//,
/RNGTEN//, and //RNGHND// and reading in /ACTESTCOS/ and /ACTESTSIN/. to allow the
servos to settle down. If they haven't settled. !AC test angle! will not reflect the expected value.
A hardware error is indicated if the DATA READY interrupt does not occur in 3.2 msec after READ
224 or if the request is not acknowledged after READ 224.
I
I
I
I
I
I 111
I
Chapter 2 ALSPAUGH. FAULK, BRITTON, PARKER, PARNAS. AND SHORE
2.1.8.7. DC self-test
Characteristics of values:
Units: None 3
Range: -2 to +2
Resolution: 1/1024
Instruction sequence:
READ 255 (Channel 7) (Reset Signal Converter if not already done)
READ 232 (Channel 7) (Request Signal Converter start conversion)
Test Carry Indicator for 0 - request acknowledged
If not, read sequence not successfully initiated
I
When DATA READY interrupt occurs, conversion complete
READ 255 (Channel 7) (Also resets Signal Converter)
0.|
Data representation: 12-bit two's complement number, bits 1-12; bit 0 used. Scale - 1024: offset -
Timing characteristics: Analog (DC voltage) to Digital conversion, see §1.15.8.
Comments: A hardware error is indicated if the DATA READY interrupt does not occur in 280 Psec
after READ 232. 3
1
N
I
N
I
I
112!
t| •' 'I
I
3 NRL REPORT g194 Built-In Test Equipment (BITE)
Data representation: bits 0 - 15 for /DIWI/ and /DIW2/, bits 4 - 7 for /DIW3/
Comments: In the rest of this document, the values are represented in hexadecimal. Thus. /'DIW1/
- HEX(O000) means all the bits in iDIWI/ are zero and /DIW3/= HEX(0) means bits 4 - 7 are zero.
1
!
I
!
i
I
U
I
I
I
i 113
I
Chapir 2 ALSPAUGH, FAULK. BRITTON, PARKER. PARNAS. AND SHORE
I
!
I
I
I
a
U
114
I
NRL REPORT 0194 Built-In Test Equipment (BITE)
Data representation: 22-bit bit string, bits 10-31; bits 0-9 unused.
Timing characteristics: See timing characteristics for //CSADATAn!/.
Comments: A hardware error is indicated if the external control interrupt fails to occur within 800
psec of WRITE 2.
/SERIAL2/ - HEX(000000) means all bits are set to 0. The first he;, digit represents 2 bits. The
succeeding hex digits each represent 4 bits.
115
Chapter 2 ALSPAUGH, FAULK. BRITTON, PARKER. PARNAS. AND SHOREg
111
I
NRL REPORT 9194 Built-In Test Equipment (BITE)
Data representation: bits 0 - 15 for //DOWi //and /,/DOW2/!/, bits 4 - 7 for I/DOV3//.
I
i
I
I
I
i
I
I
I 117
Chapter 2 ALSPAUGH, FAULK. BRITTON, PARKER, PARNAS, AND SHOREg
$WRAP13$:
SWRP12:
prfomsSWRPDICR
hiscodanUVAPER12I
This code wraps //CSADATA// to /SERL1/.
118
I
NRL REPORT 9194 Built-In Test Equipment (BITE)
$DETECTMAL$: This code sets a mechanical malfunction latch, trips the computer LRU
malfunction flag, and causes //COMPFAIL//:= SOnS. The computer
must be reset manually before the program can resume running.
i
I
I
a
i
I
i 119
Chaptr 2 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS. AND SHORE 9
2.1.8.15. Cycle steal channel A
. . .m. .mm| |I
f, NRL REPORT 9194 Built-In Test Equipment (BITE)
I
t
3
I
I
£
i
I
I
I 121
Chapter 2 ALSPAUGH. FAULK, BRITTON, PARKER. PARNAS, AND SHORE5 I
2.1.8.17. Spare synchro outputs
1
g
U
I
I
i
I
a
122
!
INRL REPORT 9194 Built-In Test Equipment (BITE)
I WVRITE
Unt:None
Instruction sequence:
* (Channel 4) (valid only if /DIMW\C / $Ready$)
I
*-132~
12
I
Chapter 2 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS. AND SHORE
I
I
I
I
I
124I
SlwCoto
I Slew control
1125
Chapter 2 ALSPAUGH. FAULK. BRITTON, PARKER. PARNAS. AND SHORE
Description: The Slew Control is a cube shaped control located forward on the cockpit left console.
The input value is proportional to the displacement from center. Positive values of /SLEWRL/ and
/SLEWUD/ indicate displacements to the right and up respectively.
Characteristics of values:
I
Units: None
Range: -4 to +4
Resolution: 1/1024
Instruction sequence:
READ 255 (Channel 7) (Reset Signal Converter if not already reset)
I
READ * (Channel 7) (Request Signal Converter to start conversion)
Test Carry Indicator for 0 - request acknowledged
If not, start again
When DATA READY interrupt occurs, conversion complete
READ 255 (Channel 7) (Also resets Signal Converter) I
• = 240 for Slew Right-Left
* 239 for Slew Up-Down
Data representation: 13-bit two's complement number, bits 0-12; bits 13-15 = 0. Scale - 2048/2
= 1024; offset = 0.
Timing characteristics: Analog (DC voltage) to digital conversion. See §1.15.8. 1
Comments: The Slew control "snaps back" to central position. The values of /SLENVRL/ and
/SLEWUD/ are not always 0 in this position. Slew values less than .148 are known to be a reliable
indication that the control is in the central position. 9
1
I
I
I
I
I
I
128
NRL REPORT 9194 Master Function Selectors
NORM
BOC TF
ATTACK
DATA
LINK CCIP OFFSET LDG
127
I
Chapter 2 ALSPAUGH, FAULK, BRITTON, PARKER. PARNAS, AND SHORE 5
2.2.3.1. Master function switches
1
I
I
I
1
I
I
a
1o.8 i
i promif 128
NRL REPORT 9194 Master Function Selectors
Single-Pairs -Simuxltaneous.p.ockets
Switch
ARP _____
Thumbwheel AR
129
Chapter 2 ALSPAUGH, FAULK. BRITTON, PARKER, PARNAS, AND SHORE
I
I
I
I
!
130i
l I I II
I
SNRL REPORT g194 Master Function Selectors
I
I
!
I
I
I
I
I
I
I
I 131
I
Chapter 2 ALSPAUGH. FAULK, BRITTON, PARKER, PARNAS, AND SHORE a
2.2.4.8. ARP quantity
1
a
I
I
I
a
i
I
I
132
--- nn imiiiBm~mam
•I nnnnn
NRL REPORT g194 Doppler Radar Set (DRS)
l Doppler
Se lector
I Knob ON TEST
:o L R S D
I
I
5 Doppler control panel
Figure 2.2.5-a
I
I
$
I
$
I
I 133
I
U
Chapter 2 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE g
2.2.5.1. Doppler drift angle
1
a
I
a
I
134!
3 NRL REPORT 9194 Doppler Radar Set (DRS)
Units: Knots
Range: 100 to 999
Accuracy: -(.11% GS + .081) to +(.i%GS + .081)
Resolution: .129
Maximum derivative: 999 knots/s
Maximum second derivative: ± 250 ft/s 2 .
Instruction sequence:
Data representation: 14-bit positive number, bits 1-14; bits 0 and 15 - 0. 1/scale :-: .129032:
offset - 0;
Timing characteristics: See §2.2.5.
Comments: /DGNDSP/ is a current estimate only if /DRSMEM/ = $No$. It is valid only if
/DRSREL/ = SYes$. /DGNDSP/ is not true doppler ground speed, which is given by !DGNDSP!.
1
I
I
I
I
I
! 135
Chapter 2 ALSPAUGH, FAULK, BRITTON, PARKER. PARNAS. AND SHORE
5
Data representation: DRS Status Word, bits 4-6
Comments: A hardware interlock currently prevents iDRSFUN/= $Test$ when A/C airborne.
Note that the DRS Status Word and the FLR Slant Range both have the same identity code (00001).
I
I
I
I
I
1316
I
I
NRL REPORT 9194 Doppler Radar Set (DRS)
Characteristics of values:
Value encoding: $Yes$ (1); $No$ (0)
Instruction sequence:
LA'8000' HEX (Discrete Output Word 3)
WRITE 2 (Channel 0) (Enable DRS)
Wait for external control interrupt
READ 64 (Channel 2) (Read Serial Input Address)
Save address data to verify identity code = 00001
Check if !Serial Input OK!
If not, try again in 20 to 400 microseconds
READ 32 (Channel 1) (Read Serial Input Data)
I
1 3
Chapter 2 ALSPAUGH, FAULK. BRITTON, PARKER, PARNAS. AND SHORE 3
2.2-.5.5. Doppler reliable
Note that the DRS Status Word and the FLR Slant Range have the same identity code (00001). '1
II
I
I
I
I
138
..... mu
... ars....
mm nal
............
a3 ....
I
j NRL REPORT 9194 Doppler Radar Set (DRS)
Instruction sequence:
LA '8000' HEX (Discrete output word 3)
WRITE 2 (Channel 0) (Enable DRS)
Wait for external control interrupt
READ 64 (Channel 2) (Read serial input address)
Save address data to verify identity code = 00001
Check if !Serial Input OK!
If not, try again in '20to 400 microseconds
READ 32 (Channel 1) (Read Serial Input Data)
Data representation:
/ANTGOOD/: DRS Status Word, bit 2
/ELECGOOD/: DRS Status Word, bit 3
iI
I
I
1139
Chptar 2 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE 3
2.2.6. Tactical Air Navigation (TACAN)
The Tactical Air Navigation (TACAN) system provides bearing and range from a selected !
TACAN station.
I
2.2.6.1. Bearing from station
Data representation: 11-bit positive number, bits 4-14; bit 0 = 0, bits 1-3 not used, bit 15 vali-
dity bit. Scale - 1/.25 = 4; offset - 0.
Timing characteristics: READM. READ sequence delays the required 5 microseconds for TACAN
to place the requested data into the output shift register.
Comments: Bit 15 equals I when data is valid.
I
I
I
i
1
I
140
NR' REPORT 914 TACAN
Data representation: 14-bit positive number, bits 1-14; bit 0 = 0, bit 15 - validity bit. Scale =
I
I
I
I
I
I
I
i 141
I
Chapter 2 ALSPAUGH. FAULK. BRnTTON, PARKER, PARNAS, AND SHORE
Angle of attack measured with respect to waterline rather than boresight (Ya), is given by: .76 X 1
/AOA/ - 5.68 (see Ref. 6, p. 3-3)
If the corrected value is less than -5.6 *, then the AOA vane has stopped sending values to the
TC-2 in order to send them to the Automatic Power control.
1
Characteristics of values: 1
Units: Degrees
Range: I to 31
Accuracy: -0.18 (at speeds above 115 knots) 1
Resolution: .0073
Instruction sequence:
READ 255 (Channel 7) (Reset Signal Converter if not already reset)
READ 237 (Channel 7) (Request Signal Converter start conversion)
Test Carry Indicator for 0 - request acknowledged
If not, start again
When DATA READY interrupt occurs. conversion complete
READ 255 (Channel 7) (Also resets Signal Converter)
Data representation: 12-bit positive number, bits 1-12; bits 0 and 13-15
132.12903; offset = 0.
0. Scale = 4096/31 I
Timing characteristics: DC voltage to digital conversion, see §1.15.8.
II
142
I
NRL REPORT 9194 SINS
/SINLAT/
/SINLON/
/SINHDG/
/SINPTH/
/SINROL/
/SINEVEL/
/SINNVEL/
143
i
Chapter 2 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
.JInm~n
nl• unun u m ,-
3NRL REPORT 9194 Pilot Grip Stick (PGS)
*:. Target
Release
Enable
- Switch
IlI1
145
Chapter 2 ALSPAUGH. FAULK. BRITTON, PARKER. PARNAS, AND SHORE
U 1
I
I
U
I
I
I
I
i 147
I
Chapter 2 ALSPAUGH. FAULK. BRITTON, PARKER, PARNAS, AND SHORE
/VAYLAT/
/WAYNUMI/ 5
/WAYNLTM2/
1I
I
I
I
i
I
3
Ii
I,
148 I
....• •• • • •m| II I i III | II-- a
I
3 NRL REPORT 9194 Horizontai Situation Ind
I Range
Indicators Vertical lubber
line
3 Pointer #1
Pointer #2
IA _IC/
I
I
I
I
I
£ 149
I
Chapter 2 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS. AND SHORE
1I
I
I
I
I
U
U
150
U
3 NRL REPORT 9194 Horizontal Situation Ind
1
I
U
U
I
I
I
I
3 151
I
Chapter 2 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
I
I 15
| 153
Chapter 2 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
I
I
Vertical
Pointer
1
Attitude director indicator
Figure 2.3.2-a
154
I
I
I
...154
, , I
NRL REPORT g1g4 Attitude Director (nd (ADI)
1Comments:
Description: When //COMPFAIL// = $Yes$, the vertical pointer alarm flag is in view.
//'COMPFAIL// is defined in the IMIS section. ,'CONMPFAEL// is also output to the
FLR and the Caution and Advisory Panel.
15
Chapter 2 ALSPAUGH. FAULK. BRITTON, PARKER. PARNAS, AND SHORE
//FPANGL// is not assumed to be Flight Path Angle by the ADI. Other quantities can be displayed
provided the FLR is not in Terrain Following mode.
I
I
i
!
I
U
I
I
I
156
NRL REPORT 9194 Attitude Director Ind (ADI)
I
I
I
I
I
I
i 157
Chapter 2 ALSPAUGH, FAULK. BRITTON. PARKER. PARNAS. AND SHORE 3
2.3.3. Flight Recorder (FLTREC)
The Flight Recorder (FLTREC) is a magnetic tape recording device. It was intended for flight
testing of the A/C system units in its early versions and is available in some production models. It
records blocks of 100 words periodically.
I
2.3.8.1. Flight recorder data
1
I
I
I
I
I
I
I
158 1
I
3 NRL REPORT g194 Bomb Tone (BMBTON)
1
I
I
1
1
I
I
I
I
1I59
I
Chapter 2 ALSPAUGH. FAULK, BRITTON, PARKER, PARNAS. AND SHORE
UU
0I
160
I
3 NRL REPORT 9194 Caution Advisory PnI
1
U
I
i
I
i
i
I
I
U
l
I
! 161
Chaper 2 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS. AND SHORE
I
I
I
I
I
I
I
I
I
I
I
162
I
1
3.NML REPORT g194 Weapon Characteristics
3Table
2.4. WEAPON CHARACTERISTICS
2
.4-a gives characteristics of the different weapons that are used with the A-7 aircraft.
The first three columns give parameters identifying the type of delivery, i.e.. the weapon. the
drag characteristics, and the rack mounting. These parameters are communicated to the computer by
the input data items /\\APTYPi'. /BNBDRAG/. and ,7I_-LTRACK/. NOTE: For safety rea-
sons. in the case of $OD$ and $SL weapons. the OFP will ignore the setting of the i TULTRACKi
switch and assume it is $Yes$ if the number of weapons selected exceeds the number of stations
selected (i.e.. if the OFP deduces that a multiple or triple ejector rack is loaded on one of the selected
stations). The number of weapons is taken to be the value of /ARPQUANT/, doubled if
'A-%RPP.MRS /=$Y'es$.
The last four columns provide characteristics associated with the identified type of delivery.
Column 4 gives the two-letter code and the common name associated with the weapon.
Column 5 (Fire Pulse Width) gives the time in milliseconds that (i/BvBREL $SOn$) must
be true to eject the weapon.
Column 6 (!Weapon Class!) specifies to which of the following classes each weapon belongs.
Column 7 (MIRI Class) assigns each weapon, where applicable, a number referring to one of the
three Minimum-release-interval curves in Fig. 2.4-a. These curves give the mirimum safe time inter-
val between release of two weapons of that type. See alo Ref. 24. part 1. §5.6.
I
I
U
U
I
I
I
Chapter 2 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
I
3
31 X X (DL) Mk 52 mine 24 SMFS
32 X X (DM) Mk 55 mine 24 SMFS 1
33 X X (DN) Mk 56 mine 24 $MFS I
41 X X (EL) NUKE 24 $SODS N/A
42 X X (EM) NUKE 24 $SODS N/A
43 X X (EN) NUKE (retard only) 24 $SSiHS N/A
44 X X (EO) NUKE 24 $SOD$ N/A
45 X X (EP) NUKE (retard only) 24 $SSHS N/A
46 X X (EQ) NUKE 24 $SODS N/A
47 X X (ER) NUKE 24 $SOD$ N/A
48 X X (ES) NUKE 24 $SODS N/A
50
so
53
X
X
X
$No$
Ses$
$No$
(FK) M 117 AL
(FK) M 117 AL
(FN) Mk 83 and DST 40 SEFF
24
27
24
SSLS
SSLS
SSLS
III
II
Ill
I
53 X SYes$ (FN) Mk 83 and DST 40 SEFF 27 SSLS II
55
55
56
SHigh$
SLows
X
X
X
X
(FP) Practice NUKE-Mk
(FP} Practice NUKE-Mk
(FQ) Mk 83 SEHD
106
76
27
.-7
24
$SODS
$SODS
SMDS
N/A
N/A
1
I
57 X X (FR) DST 40 SEHD 24 $MF$ 1
58 X X (FS) DST 36 SEHD 24 27 SMFS I
-5 X X (FT) Mk 77 24 ISMS I
60 X $No$ (GK) Mk 8l LDGP 24 SSL$ IlI
60 X IVes$ (GK)Mk81LDGP 27 $SLS f
61 X SNo$ (GL) Mk 81 SEFF 24 SSLS mI
61 x $Yes$ GL) Mk 81 SEFF 27 SSLS II
62 X $No$ (GM) Mk 81 SEHD 24 SMDS Ii
62 X $Yes$ (GM) Mk 81 SEID 27 SMD$ I
63 SLowS SNo$ (GN) Mk 81 SEFF 24 SODS III
63 SLowS SYesS (GN) Mk 81 SEFF 27 SODS II
63 SHigh$ SNoS (GN) Mk 81 SEHD 24 SODS II
63 SHigh$ SYes$ (GN) Mk 81 SEHD 27 SODS I
E4 X $No$ (GO) Mk82, Mk124 (blunt nose). DST 36 LDGP 24 SSLS Ii
64 X $'es$ (GO) Mk82. Mk124 (blunt nose). DST 36 LDGP 27 SSLS 11
65 X $NoS (GP) Mk 82. Mk 124 and DST 36 SEFF 24 SSL$ MI
65 X $Yes$ (GP) Mk 82. Mk 124 and DST 36 SEFF 27 SSLS II
I
INRL REPORT 9194 WVeapon Characteristics
I67 66
67
x
SHigh$
$High$
$Yes$
SVesS
$No$
(GQ) NIk 82 and Mk 124 SEFH
(OR) Mk 82 and Mk 124 SEHD (pilot option)
(OR) Mk 82 and Mkl 124 SEHD (pilot option)
2
27
24
SIMWSI
SOD$S
SODS If
I67 87
68
SLowS
SLowS
x
$Yes$
SNoS
$No$S
(OR) Mk 82 and Mk 124 SEFF (pilot option)
(OR) k~k 82 and Mk 124 SEFF (pilot option)
(OS) Mk 83 and DST 40 LDOP
27
24
24
SODS
SODS
SSLS
11
IlI
I
68 x $)'es$ (OS) hMk83 and DST 40 LDOP 27 SSLS H-
I69 69
70
x
x
x
$Yes$
$No$
x
(OT) NIk 84
(OT) Mk 84
(H-K) Mk 86 WSF
24
24
24 27
SSLS
SSLS
SSLS
Hl
III
11
I73 72
73
x
x
x
x
$No$
$Yes$
(HM) Mk 88WSF
(HN) Mk 83 LDOP (electric fuze only)
(HN) Mk 83 LDOP (electric fuze only)
24 27
24
27
SSLS
SSLS
SSL$
if
I
11
74 x X (HO) Mk 82. 83. and 84 LOB3 24 27 SSLS 11
75 X x (HP) Nik 106 27 SSM$
77 x x (HR) hk 76 27 SSL$ 11
78 x $No$ (HS) Mk 81 LDOP (electric fuze only) 24 SSLS III
I79 78
79
X
X
X
$Yes$
$No$
SYesS
(HS) Mk 81 LDOP (electric fuze only)
IHT) Mk 82 thermal coated
(HT) hMk82 ta.ermai coated
27
24
27
SSLS
SSLS
SSLS
11
Ill
11
90 X $No$ PJK) CBU-24/N9/49. 5.0-sec fuze 24 SMDS 11
90 x SVes$ 0JK0 CBU-24/2-9149. 5.0-sec fuze 27 $MDSI
91 X $No$ (JL) Mk 2-0Rockeye, 1.2-sec fuze 24 SNIDS I
(taI fuze selected)I
I 01
93
x
x
SYesS
$No$
IJL) Nik 2.0 Rockeve. 1.2-sec fuze
(tail ruze selected)
(iN) Mk 20 Rockeve, 4.0-sec fuze
27
24
SII)S
$ISNSI
(nose and tail fuse selected)
93 X SYesS OJN) 161k2.0 Rockeyc 4.0-sec fuze 2 ND
(nose and tai fuse selected)
94 TLowS $No$ (JO) NIk 20 Rockeye 4.0-sec fuze 24 SORS I
(nose and tail ruse selected)
94 $High$ SNoS (JO)IMk 20 Rockeye 1.2-sec fuze '24 $OR$ I
I 94
94
SLowS
$High$
SWess
S) esS
(JO) M6k2-0Rockeve 4 0-see fuze
(nose and tall ruse selected)
(JO) hik 20 Rorkeye 12-sec fuse
27
27
SORS
MOR$
ftail fuze selected)I
I 95
95 x
x
No$
$Yes$
)JP( Mkh82 LDOP )(ectric fuse
only) Nik 124 LDOP (sharp nose)
)JP) Kik 82 LDOP (electric fuse)
21
27
SSLSIl
SSL'S
I07 x $No$
Mk 124i(sharp nose). Mkh87
(JR) APAM 1.2-sec fuze (tail
fuze selected)
2 NSIf
165
Chapter 2 ALSPAUGH, FAULK. BRITTON, PARKER, PARNAS. AND SHORE
99 SLowS SNoS
tail ruze selected)
(JT) APAM 4.0-sec fuze (nose and
tail, uze selected)
24 $OR$ fl II
99 SHigh$ SNoS (JT) APAM 1.2-sec fuze (tail 24 SORS 11
fuze selected)
99 SLowS SYes$ (JT) APAM 4.0-sec fuze (nose and 27 $OR$ I
tail fuze selected)
99
All
SHigh$ SYesS (JT) APAM 1.2-sec fuze (tail
fuze selected)
27 $OR$ I
I
others X X Uncataiogued N/A SUNS N/A
I
I
I
I
I
I
I
I
I
I
166
I
5 NRL REPORT 9194 Weapon Characteristics
500
. 300
I z
Lr
200
100
i ." 65 ms CLASS n1 (SEE NOTE 2)
s
i 25 m CLASS = (SEE NOTE 3)
0I I I
0 +1.0 +2.0 +3.0 +4.0 +5.0
AIRPLANE NORMAL ACCELERATION, g
INOTEI
1. CLASS L BELOW +1.98g; MRI - 470m%-170ms/g
ABOVE +1.98g; MRI - 134ms
i
167
Chapter 2 ALSPAUGH, FAULK, BRITTON, PARKER. PARNAS, AND SHORE
PSAD
I /MCL
Discrete Output Word
DOW1 /IANTSLAVE//
//CURENABL//
//BMvBREL/f
//FIRRDY/
//BMBTON//
3
Discrete Output Word 2
DOW2 I/AUTOCAL 1/ //COMPCTR/ / //COIPrAIL/ /
j/MSNAI/ //lMSSCAL// //LATGT7o/,/I
j/LFTDIG// //TSTADCFLRI1/ / /XSLEW / /
/ /XSLSENI/ //YSLEW // //YSLSEN //
//ZSLEW// //ZSLSEN//5
HUD Control
HUDCTL //HUDASI/ //HUDASL// //HUDFPM//
,,/HUDPUC// //HUDSCUE/,! j/HUDNVELI
//HUDWARN//
Magnetic Heading
IM.AGH /MAGI-COS/ /MAGHSIN/I
Pitch
IPCH /PCHCOS/ /PCHSIN/I
168
NRL REPORT g194 Dats, Item Clase
I True Heading
I)G /THDGCOSI /THDGSIN/
IPTW2
Panel Input Word 2
/FLYTOTOG/ /FLYTOTW/ /UPDATTW/
IPIW3
Panel Input Word 3
/MODEROT/ /PRESPOS/
Panel Output-Al
POALL //ENTLrr// //KELrT// //LLITDEC//
//LLlTE/f //LLITW// //LLrr322//
//LWDIGI// //LWDIG2// //LWDIG3//
(//LWDIG4// //LWDIG6// //LWDIG6//
IPanel POW2
utput Word 2 /r32/
/ILWDIG1// //LWDIG2//'
IPOW6
Panel Output Word 6
//UWD[Gl// //UNNDIG2//
3POW7
Panel Output Word 7
//UWDIG3// //UWDIG4//
3POWs
Panel Output Word 8
//UWDIG5// //UWDIG6//
169
Chapter 2 ALSPAUGH. FAULK(, BRITTON. PARKER. PARNAS. AND SHORE
/SINROLI
170
I
NRL REPORT 9194 Unused Inputs and Output-s
(h) The reference is to the LORAN words or bits defined in Ref. 18, §5.
(i) The reference is to the Lower Window 7 word defined in Ref. 18, pp. 5-56.
(j) The reference is to the Mark Window word defined in Ref. 18, pp. 5-56.
(k) The reference is to the self-test signals defined in Ref. 18, pp. 5-60 and 5-62.
(1) The reference is to the SINS analog data defined in Ref. 18, pp. 5-59 and 5-60.
(m) The reference is to the spare signals defined in Ref. 18, pp. 5-59, 5-62, 5-71, 5-73, and 5-74.
(n) The reference is to the signal converter defined in Ref. 18, pp. 5-60.
The third column (Bit(s)) gives the bit(s) of the I/O Item that are unused.
The last column (Descripticn) gives a description of the I/O Item. The number in parentheses
describes why the bits of the I/O Item are unused. The definition of the numbers follows:
(1) Used by the USAF version of the OFP.
(2) Not used by the Navy version of the OFP.
(3) Bit always set to 1. Not used by the Navy version of the OFP.
(4) Not physically implemented.
171
PI
Chapter 2 ALSPAUGH, FAULK, BRITTON. PARKER, PARNAS, AND SHORE
READ/WRITE 18
Level 1(b). _-
Interrupt 4 SPARE LORAN (2)
I
Level 0(b)
READ/WRITE 18 Interrupt 5
Level 0(b)
READ/WRITE 18 Interrupt 6-15 ZERO (4)
Level 0(b)
READ 22 TW Encoder(c) 0-7, 11-15 THUMBWHEEL ENCODER (2)
READ 22 TW Encoder(€) 8-10 ZERO (4)
WRITE 8 DOWI(a) 0-7, 11, 15
WRITE 8
WRITE 4
DOWl(a)
DOW2(a)
14
11, 15
NAV/WD PANEL MAL.IND. (2) I
WRITE 2 SIR-DOW3(a) 2 ENAB. LASER (2)
WRITE 2 SIR-DOW3(a) 4-6 AGE TEST EQUIPMENT (2)
WRITE 2 SIR-DOW3(a) 7 LIFT STO. PRO (2)
WRITE 2 SIR-DOW3(a) 8-15
WRITE 24 10-bit Counter(b) 10-15
READ 32 DRS STATUS(d) 0, 8-15
READ 32 /DGNDSP/te) 0 SIGN ALWAYS SET TO 1
READ 32 /DGNDSP/(e) 15 ZERO (4)
READ 32 /DRFTANG/(e) 0 SIGN ALWAYS SET TO I
READ
READ 32
32 /DRFTANG/(e)
/SLTRNGie) 15 ZERO (4)
13-15 ZERO (4)
READ 32 LASER(f) - 0-15
READ 64 SIA Word(g) 5 LASER ENABLE (2)
READM 97 ?? ?? /RNGSTA/ADDRESS
READM 96 ?? ?? /BRGSTA/ADDRESS
READ 129 /XVEL/(e) 0-5
READ 130 /YVEL/(e) "0-5
READ 132 /ZVEL/(e) 0-5
READ 144 /XGYCNT/(e) 0-12,15
READ 136 /GYCNT/(e) 0-12, 15
READ 152 /ZGYCNT/(e) 0-12, 15
WRITE 129 //XGYCOM//(e) 0-10. 15
WRITE 130 //YGYCOM//(e) 0-10, 15
WRITE 132 //ZGYCOM//(e) 0-10, 15
READ 161 LORAN(h) 0-13 LORAN (4)
READ 161 LORAN(h) . . 14-15 ZERO (4)
READ 162 LORAN(h) 0-13 LORAN (4)
READ 162 LORAN(h) 14-15 ZERO (4)
WRITE 161 LORAN(h) 0-13 LORAN (4)
WRITE 161 LORAN(h) 14-15 ZERO (4)
READ 208 PIWI(a) 13-15 ZERO (4)
READ 200 PIW2(a) 10-15 ZERO (4)
READ 196 PIW3(a) 6-7 /MODEROT/ SPARE (2)
READ 196 PIW3(a) 11-13 /PRESPOS/ SPARE (2)
READ 196 PIW3(a) 14 NOT KBD (2)
READ 196 PIW3(a) 15 ZERO (4)
READ 194 LORAN(h) 0-13 LORAN (4)
READ 194 LORAN(h) 14-15 ZERO (4)
WRITE 200 POWl(a) 12-15
172
I
NRL REPORT 9194 Unused Inputs and Outputs
173
I
Chapter 2 ALSPAUGH, FAULK, BRrrTON, PARKER. PARNAS, AND SHORE
I
Instruction I/O ITEM Bit(s) Description
WRITE 224 //RNGUNIT//(e) 8-12
WRITE 224 //RNGUNIT//(e) 13-15 ZERO (4)
WRITE 225 //RNGTEN//(e) 8-12
WRITE 225
WRITE 226
WRITE 226
//RNGTEN//(e)
//RNGHND//(e)
//RNGHND//(e)
13-15
8-12
13-15
ZERO (4)
ZERO (4)
I
WRITE 227 //GNDTRVEL//(e) 1-2
WRITE 227 //GNDTRVEL//(e) 13-15 ZERO (4)
WRITE 228 //FPANGL//(e) 1-2
WRITE 228 //FPANGL//(e) 13-15 ZERO (4)
WRITE 229 //STERROR//(e) 1-2
WRITE 229
WRITE 230
//STERROR//(e)
SPARE(m)
13-15
0-12
ZERO (4) i
WRITE 230 SPARE(m) 13-15 ZERO (4)
WRITE 231 SPARE(m) 0-12
WRITE 231 SPARE(m) 13-15 ZERO (4)
WRITE 232 '/BRGDEST//(e) 13-15 ZERO (4)
WRITE 233
WRITE 234
WRITE 235
//GNDTRK//(e)
//STEEREL/i'(e)
//STEERAZ//(e)
13-15
13-15
13-15
ZERO
ZERO
ZERO
(4)
(4)
(4)
I
WRITE 236 /SPAREI/(e) 13-15 ZERO (4)
WRITE 237 /SPARE2/(e) 13-15 ZERO (4)
WRITE 238 SPARE(m) 0-12
WRITE 238 SPARE(m) 13-15 ZERO (4)
WRITE 239 SPARE(m) 0-12
WRITE 239 SPARE(m) 13-15 ZERO (4)
WRITE 240 SPARE(m) 0-12
WRITE 240 SPARE(m) 13-15 ZERO (4)
1
I
I
I
1
I
1"74
I
CHAPTER 3
Modes of Operation
I
I
I 3.0. INTRODUCTION
3.0.1. Overview
We have grouped the possible states of the OFP into modes that correspond to A/C operating
conditions. Because the functions performed by the OFP differ greatly in different modes, a descrip-
tion of the OFP requirements on a mode-by-mode basis is simpler than a general description.
We chose our modes to correspond as closely as possible to the modes mentioned in other A-7
documentation. However, none of the documents contain a definitive list of modes; nor do the docu-
ments agree precisely with each other. Therefore, to fill gaps and reconcile inconsistencies, we devi-
ated occasionally from the current documentation.
Five classes of modes are described in this chapter: alignment, navigation, navigation update.
weapon delivery, and test. The system can be in more than one mode at one time, provided the
modes are in different mode classes. Exclusion relations among modes in different classes are described
in Chapter 4.
The alignment modes correspond to different procedures for aligning the IMS platform X, Y. Z
frame with Earth's east, north, vertical coordinate system. These modes are primarily distinguished
by the reference data used to determine the amount of platform misalignment. Among the alignment
modes are three calibration modes, which calculate the rate of drift of the axes of the particular IMS
platform. The drift is compensated for during navigation. The seven alignment modes are listed
below, with the shorter, mnemonic names that are used to refer to them in the rest of the document.
I The navigation modes correspond to different procedures for calculating position. velocity and
wind data and for maintaining the IMS platform in alignment. The ten navigation modes are listed
below, with their mnemonic names.
175
I
Chpter 3 ALSPAUGH, FAULK. BRITTON. PARKER. PARNAS. AND SHORE 3
Doppler inertial *DI*
Inertial *I*
Unaligned Doppler inertial *UDI*
Open loop *OLB*
Magnetic slave *Mag sl*
Grid
Polar Doppler inertial
*Grid*
*PolarDI*
[
Polar inertial
IMS failed
*PolarI*
*IMS fail* 3
The navigation update modes correspond to different procedures for obtaining a correction for
the A/C present position. Obtaining a navigation update is like setting a watch: an outside reference
is used to get an initial correct value. The six navigation update modes are listed below, with their
mnemonic names.
The weapon delivery modes correspond to different procedures for identifying and tracking tar-
gets and for determining the moment at which a weapon should be released. Many of the displays,
especially on the HUD, vary considerably from one weapon delivery mode to another. The weapon
delivery modes are listed below with their mnemonic names.
I
Air-to-air guns *A,/A Guns*
Air-to-ground guns/rockets *A/G Guns*
Bomb on coordinates *BOC*
Bomb on coordinates, Fly-to-O *BOCFlytoO*
Bomb on coordinates, offset *BOCoffset*
Continuously computed impact point *CCIP*
Manual ripple
Normal attack
Normal offset
*\anrip*
*Nattack*
*Noffset*
I
Normal attack with HUD unreliable *HUDdownl*
Normal offset with HUD unreliable *HUDdown2*
Special bomb on coordinates *SBOC*
Special BOC, Fly-to-O *SBOCFytoO*
Special BOC offset *SBOCoffset*
Special normal attack *Snattack*
Special normal offset *Snoffset*
Special normal attack with HUD unreliable *SHUDdownl*
Special normal offset with HUD unreliable *SHUDdown2*
Walleye *Walleye*
A sequence of tests is run in a single test mode-Ground Test (*Grtest*)- to make sure the
computer and its interfaces to other hardware components are operating correctly.
I
17/6
I
NRL REPORT g194 Introduction
3.0.2. Organization
Following the definition of legal mode combinations, the five classes of modes are described in
the following order: alignment modes, navigation modes, navigation update modes, weapon delivery
modes, and test modes. Each respective section has an overview of a mode. The mode overviews are
not meant to be complete user-level descriptions of the mode characteristics. Instead, they summarize
briefly and informally the characteristics that distinguish the modes in a given class from each other.
The overviews are meant to be introductory in nature and not necessarily authoritative. If there is a
conflict between information in an overview and information presented elsewhere, the latter should
be considered correct. For more narrative descriptions, see Refs. 14, 15, 17, 24, 26, 27, and 28.
After the mode overviews for a class, we indicate the mode in that class that the system will be
in when started up. We then indicate the events that will cause the system to change from one mode
to another. This fully specifies the mode of the system, provided that we know the history of events.
There is a single transition table for alignment, navigation, and test modes because the transi-
tions are so interrelated.
*Airaln* *Grid*
*RAS fail*
*PolarDI*
*Polarl*
(2) The system may be in at most one of the following modes at a time:
*HUDUpd* *Nattack* *Walleye*
*RadarUpd* *Noffset* *Snattack*
*MapUpd* *BOC* *Snoffset*
*TacUpd* *BOCFiyto0* *SBOC*
*FlyUpd* *BOCoffset* *SBOCFlytoO*
*CCIP* *SBOCoffset*
*A/G Guns* *SHUDdownl*
*HLUDdownl* *SHUDdown2*
*HUDdown2*
.
(3) The system may only be in *AflyUpd* when it is in either *BOC* or *SBOC'
(4) The system may be in *A/A Guns* and *Manrip* separately or together.
(5) The system may not be in any of the following modes if the navigation mode is *NS fail*.
*Mag sl*, Dr *Grid* and the condition !ADC Up! is false:
177
Chapter 3 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
*SHTJDdown2*
1781
NRL REPORT 9194 Alignment modes
!CL stage! Coarse level Platform X and Y axes are roughly aligned to local
horizontal-tilt errors are allowed to accumulate
and are then slewed out. Heading corrections are
not applied. The duration given for !CL stage! in
the table for each mode is that required by the er-
ror accumulation phase. However, the total dura-
tion of !CL stage! is the sum of this time and the
time needed to correct and remove the errors. Er-
!IHL stage! Hi-gain level Refined alignment of X and Y axes to local hor-
izontal occurs-tilt errors are continuously torqued
out. Heading corrections are not applied.
!CA stage! Coarse azimuth Z axis is roughly aligned to the local meridian.
errors aoHeading
are allowed to accumulate and are
-- slewed out if large or torqued out if smaller. X
and Y axis errors are allowed to accumulate and
179
Chapter 3 ALSPAUGH, FAULK. BRITTON. PARKER. PARNAS, AND SHORE
!FG stage! Fine gyrocompass Z-axis is fine-aligned to local meridian. Fine align-
ment of X and Y axes continues. X and Y axis er-
rors are allowed to accumulate and are removed by
torquing at the end of the stage. Heading errors
are allowed to accumulate and are slewed out if
I
large or torqued out if smaller. The duration given
for FG stage! in this chapter for each mode is that
required by the error accumulation phase. Howev-
I
er, the total duration of !FG stage! is the sum of
this time and the time needed to correct and re-
move the errors. Errors have been removed when
!slewing complete! occurs.
!ED stage! East drift East gyro drift bias is calculated and Data 02 is I
updated; heading and level alignments are refined.
!ND stage! North drift North gyro drift bias is calculated and Data 01 is
updated; heading and level alignments are refined.
3
!HS stage! Heading slew Z axis is slewed until heading equals a computed
heading. (*SINSaln*: SINS heading + !Delta
heading!; *HUDaln*: !azimuth reference heading!
+ //ASAZ//).
!TS stage! Alignment test Errors are allowed to accumulate and are then
compared to a threshold, to see if they are within
acceptable limits. The duration given for !TS
stage! in this chapter for each mode is that re-
quired by the error accumulation operation. How-
ever, the total duration of !TS stage! is the sum of
this time and the time needed to correct and re-
move the errors. For *Landaln* mode. errors have
I
been removed when !Land velocity test passed! OR
!Land velocity test failed! occurs.
I
I
180I
NRL REPORT 9194 Alignment modes
Refe-ence data:
Horizontal velocities: 0 corrected by Earth's rate
Latitude and longitude: values most recently entered by pilot
I Stages:
S Coarse level 50 seconds !CL stage!
Coarse azimuth 100 seconds !CA stage!
Fine gyrocompassing 150 seconds !FG stage!
Coarse azimuth 2 200 seconds !CA stage!
East drift - 02 update 260 seconds !ED stage!
Coarse azimuth 3 50 seconds !CA stage!
North drift - 01 update 200 seconds !ND stage!
Comments:
The first three stages allow the platform enough time to become thermally stabilized.
181
I
Chapter 3 ALSPAUGH, FAULK. BRrrTON, PARKER, PARNAS. AND SHORE
Reference data: I
Horizontal velocities: SINS velocities, with corrections for A/C displacement from SINS source (!SINS
offsets!) and !Delta heading!.
Heading: Ship's heading, corrected by !Delta heading!
Latitude and longitude: ship's coordinates
Stages.:
Coarse level 50 seconds !CL stage!
Coarse azimuth 200 seconds !CA stage!
Coarse azimuth 2 600 seconds !CA stage!
East drift - 02 update 1860 seconds !ED stage!
Coarse azimuth 3 50 seconds !CA stage!
North drift - 01 update 1800 seconds !ND stage!
Interruptions:I
If SINS velocity and heading invalid for 2 seconds, the mode is exited and a full *SNSaln* mode must
be executed before *Sautocal* may be restarted. 5
Accuracy test: None.
I
I
I
I
I
I
I
182
I
NRL REPORT 9194 Alignment modes
Reference data:
Horizontal velocities: 0, corrected by Earth's rate
U Stages:
Fine gyrocompassing 200 seconds !FG stage!
Alignment test 30 seconds !TS stage!
Accuracy test:
Velocity test: north and east velocities < 1/8 fps for 30 seconds
DeltaOi test: difference between old and new Y axis drift rate values <0.049.
183
I
Chapter 3 ALSPAUGH. FAULK. BRITTON, PARKER, PARNAS, AND SHORE
Reference data: I
Horizontal velocities: 0 corrected by Earth's rate
Stages:I
Coarse level 50 seconds !CL stage!
Coarse azimuth 100 seconds !CA stage!
Fine gyrocompasbing 150 seconds FG stage!
Fine gyrocompassing 200 seconds !FGstage!
Alignment test 30 seconds !TS stage!
The last two stages are repeated until the mode is exited. The duration of the error accumulation
phase of the !FG stage! that follows a !TS stage! depends upon the outcome of the Land velocity test
at the end of the preceding !TS stage!. If !Land velocity test passed!, the duration is 200 seconds. If
NOT !Land velocity test p,-ssed!, the duration is 170 seconds.
Accuracy test: North and east velocities: less than 1/8 fps after 30 seconds.
1
I
I
I
I
I
I
I
I,
184
NRL REPORT 9194 Alignment modes
Reference data:
Not all the reference data are required: alignment may proceed even if the optional data
become not available.
Horizontal velocities: SINS velocities, with corrections for A/C displacement from SINS source
(!SINS offsets!) (required) and !Delta heading!
Heading: Ship's heading, corrected by !Delta heading! (required)
Latitude and longitude: ship's coordinates (optional)
SINS heading, pitch and roll (required)
*Stages:
Heading slew varies !HS stage!
Coarse level 50 seconds !CL stage!
Coarse azimuth 200 seconds !CA stage!
Fine gyrocompassing 600 seconds !FG stage!
Alignment test 30 seconds !TS stage!
I Interruptions: SINS data interrupt greater than 5 seconds--current stage restarted power
interrupt less than 30 seconds-continues where left off otherwise stage restarted.
Accuracy teat: difference between [MS and corrected SINS north and east velocities: < I fps
after 30 seconds.
185
I1
Chapter 3 ALSPAUGH. FAULK. BRITTON, PARKER, PARNAS. AND SHORE
Reference data:
Azimuth of known reference point
HUD coordinates of known reference point
(For other reference data, see *Landaln* overview.)
I
I
I
I
I
I
I
I
I
I
186
!I i i I !I
NRL REPORT 9194 Alignment modes
Reference data:
Horizontal velocities: !DGNDSP!. resolved into north and east components, using /DRFTANG/.
Stages:
S Fast magnetic heading update 30 deg/min !FM stage!
Coarse level 50 seconds !CL stage!
High gain level 180 seconds !HL stage!
High gain gyrocompassing 420 seconds !HG stage!
Fine gyrocompassing and test 300 seconds !FG stage!
If !CL stage! was completed in an earlier mode. *Airaln* starts with !HL stage!; if !CA stage! was
completed, *Airaln* starts with !FG stage!. The last stage is repeated until the test is passed.
Interruptions:
!T'Mstage!:-interrupted when roll greater than 5.
Power interrupts-extend alignment time by the time the power is down.
Doppler interrupts-
during !CL stage! - starts over (*OLB* during interruptions)
all other stages - extend alignment time by time Doppler is down (*I* during interruptions)
Accuracy test: East and north velocity differences from Doppler: less than 5 fps.
187
Chapter 3 ALSPAUGH, F'AULK. BRITTON, PARKER, PARNAS. AND SHORE I
3.3. NAVIGATION MODES
3.3.0. IntroductionI
The two major aspects that distinguish navigation modes are (1) the data sources used in the
velocity, heading, and attitude calculations, and (2) whether any adjustments are applied to the plat-
form axes, and if so, how they are calculated. These two main areas are covered in the navigation
mode overviews.
The modes are also grouped into two classes: Primary and backup. The primary purpose of the
classification is continuity with existing documentation. Also the Data 98 display distinguishes
between modes in this way.
I
In the overviews, vertical velocity is frequently calculated from AOA. IMS attitudes, and either
horizontal velocity or true airspeed (total velocity). In these cases, the following steps are followed to
calculate vertical velocity:
I
(1) The angle of the A/C velocity vector relative to horizontal is calculated from AOA, pitch, and
roll. I
(2) Side v of the triangle below is solved, given that angle f (see step I) is known and either
side h (horizontal velocity) or side t (total velocity) is known. 3
h angle f
We distinguish between "IMS corrections" and "VIS adjustments." Both involve torquing the
platform axes. However, the angle to be torqued is calculated differently in the two cases:
(1) Correction angles are calculated by comparing platform velocities to Doppler velocities to deter-
mine the magnitude of platform misalignment. For the Z axis, this is called Doppler gyrocorn-
panning, since the IMS heading is corrected. For the X and Y axes, this is called Doppler level-
ing, since platform tilt errors are removed.
(2) Adjustment angles are calculated by applying fixed corrections: a reference velocity is not
needed. Adjustment maintains the platform in alignment with Earth axes, accounting for Earth
curvature and for the ongoing drift occurring in each axis.
I
I
I
I
I
188
I
NRL REPORT 9194 Navigation modes
Horisontal velocities used: IMS north and east velocities damped by Doppler groundspeed
I1
I
I
I
I
I
I
I
I
I 189
I
Chapter 3 ALSPAUGH, FAULK. BRrrTON, PARKER, PARNAS, AND SHORE
I
I
I
I
I
I
I
I
I
I
I
190I
mm mm~mmmm m ¢ W===ii= I
NRL REPORT 9194 Navigazion modes
Clam: Primary
I
I
I
I
I
I
I
191
U
Chapter 3 ALSPAUGH. FAULK. BRITTON, PARKER, PARNAS, AND SHORE
Clas: Backup i
Horizontal velocities used:
Not airborne: 0 fps
Airborne and Doppler reasonable: Doppler groundspeed
Airborne, Doppler not reasonable, ADC reasonable: ADC velocities and wind
Airborne, Doppler and ADC unreasonable: stale value
I
I
I
I
I
I
I
I
I
192
NRL REPORT 9194 Navigtion modes
I
I9 1
Chapter 3 ALSPAUGH. FAULK, BRITTON, PARKER, PARNAS. AND SHORE
I
I
I
I
I
I
1
I
I
I
I
194
! I! I Ii !I
NRL REPORT 194 Navigation modes
Clas: Backup
195
I
Chapter 3 ALSPAUGH. FAULK, BRrTTON. PARKER. PARNAS. AND SHORE
Claw: Backup I
Horizontal velocities used:
Not airborne: 0 fps
Airborne and Doppler reasonable: Doppler groundspeed
Airborne, Doppler not reasonable, ADC reasonable: ADC velocities and wind
Airborne, Doppler and ADC unreasonable: stale value
Clas: Primary
197
I
Chapter 3 ALSPAUGH. FAULK, BRITTON. PARKER. PARNAS. AND SHORE
Class: Primary
1
U
I
I
I
I
I
I
I
198!
I
I NRL REPORT 9194 Align/Nay/Test
Modes Conditions
*Landaln* !IMS Up! AND /IMSMODE/=$Gndal$ AND !Data 23!-!Land!
I9
Chapter 3 ALSPAUGH, FAULK, BRITTON. PARKER. PARNAS. AND SHORE
Table 3.4-b
Transitions Between Alignment. Navigation, and Test Modes
While the Aircraft Is Not Airborne (/ACAIRB/=$No$)
%
%U
%
CA '- -
Current0
Mode NewMod
Lautoca
@1....................%o----------------------------------_"Il
N.........@r 0 r---------------I
-1--- -----------------------------------------------
----------------------------------------------------- asri
-------- -- - -- - - - - --- ---- ---- --- ---- --- ---- ---- ------------
--------------------------------------------------------- NanI
------------ r:-----------------------------------------------*~Srt
- - -
-----------------
-- - - t - t-- ----
@1------------------------------------------Gtt
--- --- Pola,1 I
--Ca .. -. .... .. *rt qI
---
0sautocaI
@r - -
-------------
- -
------------------- - - - - - - - - - *200dn
NEL REPORT 9194 Align/N,.v/Test
0 % e5.~~4
3
% ~ ~ 0/ 4~~
- .04
'3
*Landaln*
- ---.-.-.-.-.. . .-.-.-. . . . . . . . t e Lautoesis
*----------------------------------------------------Han
@r @- - - - - - - - - - r
-
r- @ .............
---------------------------------.
r........r........
-----------------------------------
*-- @r -...............................
- @r- - t - - - - .................................- - o
........ t -- - [email protected]
------------- - --- . - --- ---- ---- ---- ---- ----
-r - -- - - -- - - CT - G-r--e-t
. .. - - - -@ r - - - - -20-1
Chapter 3 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS. AND SHORE3
4 4.4
01
q, 4g
A
Current5rAr
Mode 4 4VC e Mode
*SINSaln* 9 - - r----
- - ------ - - - Sautocal I
- -------- ------------------------------------ Ladl
---- - ------------------------------- 1
- - - - t - - r f - - r - - - -* I
----------------------------------------------------
- tt . - r - - ----- r r (9F- - - -
-------------------- @1-----------------------Ma 1
...... @1-----------------------------------------------Gret
CaT
-- - -- - *olrU
- ------
tt- -.rr (9.
202
NRL REPORT 9194 Align/Nay/Test
Vm .04
4 P0 P
'0
Current
Mode ' I$ NewMode
Ol1Update*
---- --- ---- --- --- ------- LautocaiO
@-------------------------------------------------------------------Ldan
-----------------------------------------
--------------------------......--- -- ---------------- -
-- -- -- - - - f @F - - - ..... -.-.-.-.-...........
- - -- - - -- - - - - - - - - - - - -- - - - - -- - -- - -- -
203
Chapter 3 ALSPAUGH. FAULK, BRITTON, PARKER, PARNAS. AND SHORE
bI
4% ' 1
OHUDain*C - - - - - - - - - - - - - - - - t - - *Luoa
a oc l
*-1------------------------------------------------------- - -
@-
@T - - - t--
t - -*--
- - r.......................*-
r-- @r I
- - - - - - t - - r - -
-T - - - - - - -- -
-@r--------r------------------------------------
W.-.-.-. -. -. -. -@ - - - - t - - - - - - - -
r ~~ ~ ----~ ~ t ~ M taI--@
-- - - t -- t---------------------------------------------------Par
. .. .. CaT. - - - - - - - - - Grtest*
204
NRL REPORT 9194 Align/Nsv/Test
b' N'8b
--, %%6 b1%b
a'A'
-~~~~~~~~ - 0 0 A,---------r........adl
- ~ ~~~~~~~~ % 4
A................K b I~
........................................... @-------------------Gd
W- - - t -....-.............................. LD*l
@ - - - .- - .- .- - .- . .- .- . .t .- - - - - - -S! ai
-91 - - -r t.........................................- -
-----------
--- ---- --- ---- --- ---- --- ---- ---
-- -- - - (T - - - - *Mg 91d
-~~ - --.-.-.--.-.---.-.----------------------------
.................. @-'.................................Grid*t
- ----
- -- -- --- -- -- --- -- --- -- -- --- -- --
Chapter 3 ALSPAUGH. FAULK, BRITTON. PARKER, PARNAS, AND SHORE3
4.; 9 4'',
II&
CurrentI
Mode New Mode
'%lag .1*
- -..............--------------------------------------
Lnan
Ladin
1
---------------------
--
- -- - - - *G
-------MT
-------------------------------------------------------
id @1----------------------'rd
-- M taI
----------------------------------------------- @..............LD3
W - -t
---------------------------------------------------- 'Pt al
- ----- 1
-------------------------------------------------- 'Lnan
-- ---------- - t----------------------------------OD
t - F
@ -- -- - - - --- OP I
..
...CT..
---t - - -- OLI
.0
- --aT
-
a
--
.1
- - - -U
NRL REPORT 9194 Afign/Na/Test
t_ -&- t~
~c
N
N%
Curret
Mad~ _
*Poar5
_110 --------- @'-------------- adl
X3-- r--------------------
t------------------------- - - - t - SI~aP
@r -- t -- - - - 1 Gr-d-
------------------------------------------------------ Tral
-------------------------------------------------
- -- -- - - - - f 207 - - - - - - - - - - -* [ I fa l
m
Chapter 3 ALSPAUGH, FAULK. BRITTON, PARKER, PARNAS, AND SHORE
Table 3.4-c
Transitions Between Alignment, Navigation, and Test Modes
While the Aircraft Is Airborne (/ACAIRB/=$Yes$)
mI
51,
Abb
Current
Mode
) '7
. \S: \ \ New Mod
I
*A i r ln * Ca - f t - - - - - - - -* A i ral n *
C~iaie 1----------- -------------------------------------------- Aian
S - t f - - - - - - - - -
t f - f - - @
-~ ~ - f (9FI - t - - -71- - - -
f - - - - t - r - - -U t I
~- ------- OL
I
- ---------------------------------
@ Ff - - - - - - - - - -- *OL B O
-- - -- ------------------------------
f - - - ---- @- - -
ff - - -Magsl I
@1' - Grid"
( F- IMS rail* I
f - -t-tt - - - -PoarDI*
- F t --------------------------------------------
- t PorI
t t t -~l *P
- - I,
~~ t ~ @fCO
- - - -
I
t
I
I
U
208m
NRL REPORT 9194 Afign/Nay/Test
:N,
4.p
Current
Mode Neod
D1 1'------------------------------------------------------irn
t t -r - - - *DI
f--------- ------------------
@F
- - - - - - -r- - - - *1
f@1'-- - - - - M g s
- - -- - - - - @1'r- -Gr d
W - - - - - t t - -
-------------------------------------- *1
f t @ - t F - t - - - - -
- - - - - - - - - -- t - t- - - - - -
'----------------------------------------
--- --- u~
-
@71------------------ -- -- - - - - *I*
@F- -Ma- - -
@F-------------------------------------------*ISri
--------------------------------------------- PoaD
209
Chapter 3 ALSPAUGH, FAULK. BRITTON, PARKER, PARNAS. AND SHORE3
% 4'
CurrentI
Mode 17 '7VNew Mode
S f ---- --- --- --- --- ----- t----- --- --- ---- --------- Landaln*
tt f @1'
t12 - - - -
t f O r t- - - - - - -
f---- --- --- -------- f Ct@1- t- - - - -
O0LB N
-~~~1 - a MagI 31
------- @------------------------------------Par
lJD---I-------------------------------------- Y2..........ian
- - -- - - - -
-- -- --- -------------------
-- --
-- --
-- -- -- -- - -------------------- 0L
@F
- -- - -@ - - - - -M gI
- - - - -- - @ - - - @- - -
---~ ~ ~
- ~ ~ -----
- - ~~
- -- - -- - - M
2101
NRL REPORT 9194 Aign/Nav!Test
Cl6 ~%
Current % e~d
Mode
CI
CIO -V t -Y
A 0
4 4 1'4Zags
-T -
*OL
- *- -- - - - - CT t - - - - - GArald*
Maa---------------------------- @I--------------------------Arn
- --
-- -- -CTtt @--------- M
t @r - ~t - - - t UD
- -- - - - - - - - 0L1
- -- - - - - - - - s - a - - - * a l
-- -- -- - - - - - - 1a - - *G rid *
-& - - - - - - - - - IM S fail*
*Magsl*
- - - - - - - Ca - - - - - *A211n
Chapter 3 ALSPAUGH, FAULK. BRITTON, PARKER. PARNAS. AND SHORE3
J.4$
Current
Mode New Mode
'Grd'----------------------------- 1----------------------Aiin
-- - - - - t t - Ca 1'- - - t
-- - - - - f - - - Or1'- - - - *OLB'
- -- -- - - - f C- -@ 1- - - -
- - -- - f - ra @
- - - - -
- - -- - - @-
Ca - - - Mag 9l'
'IMfil-----------------7'---t------------------------------Arin
- - - - - - * I S fa l
*I S -f i*- -- @ Y- - - - -
-71------------- t - - t---- - - t M gs
--------------------------------------- -- 'rd
- - - CaT
---- -t ---- OLI
CaT ---
t ---U
---t
- - -CaT- -I
- -ft- -CaT -- -
2121
INRL REPORT 9194 Align/Nay/Test
NN
10
A 'x
*PolarDI* @'---
Ca -- ------ - - t t------------------*Airaln*
-- -- - -- - --- ---------------------------
Or t t 0M-
-71-------------------------------- --- f L
- - - - - - -(9 - - - - - - - PolarI*
(WF t - - - -
1~a ------------------------- t -
-- -- - -- - -- - --------------------------
- - - L1
CaT - -- -- - f - - - - ' - -
-----------------------------------------------
IM
-- -- - - - - - -t - - -. CT - - -* a
I - - - - - CT - t - - -
213
Chapter 3 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
A/C
angle d
hI
5:
Reference point
214
NRL REPORT g194 Navig&Uon update modes
TACAN estimate: position calculated from TACAN station coordinates. /RNGSTA/ and
'BRGSTA/, as Fig. 3.5-b indicates. h is the horizontal distance from the a/c to the TACAIN station.
calculated from /RNGSTA/ and the angle d.
215
I
Chapter 3 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS. AND SHORE
North I
I
angle /BRGSTA/
TACAN station
/RNGSTA/
A/C
Figure 3.5-b 5
Update initiation: Target designation button - as long as depressed, TACAN sampling and filter-
ing occurs.I
Update accepted: ENTER key depressed
Ranging: From sensor defined by !Data 24! (/RADALT/ or !Baro altitude above target!
I
I
U
I
216 3
NEL REPORT 9194 Navigation update modes
Table 3.5-a
Transitions between Navigation Update Modes
C'
Current
Mode New Mode
*UNone* f t t t - - - f - - t -@r1 - HUDUpd*
f t t t - - t f - - - t -iT - - RadarUpd*
f it t t - f - t -@1 -
---
-- --- -- --------------------------------- @' - --- fy~d
f - @ t 1 t - -
f t t t - - - - F I
f - t t Or - - - - f f - - - - - - -
* ~ ~~ ~ ~ ~ ~ ~ ~-HUDUpd* Uoe
___________j- - @1--------------------
- - - - - - - ----
@ 217 - - -
Chapter 3 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
~~~~-1---------------
- - - - - - - ----- M3
--- - - -- -- - -- - - - - ---
218
NRL REPORT g1g4 Navigation update modes
N,
CurrentI 0
Mode 0 T INew Mode
*AflyUpd* -- F---- -------- ------ --------- UNone*
- - -- - - - - - - - ~ ~ p
TacUpd----------------------------------------UNone*
- - - ---------------------------------------------- Mpd
-- - - - 219pd
- - - - - @T -
I
Chapter 3 ALSPAUGH, FAULK, BRITTON, PARKER. PARNAS. AND SHORE I
3.6. WEAPON DELIVERY MODES
3.6.0. Introduction I
The weapon delivery modes differ primarily in the way the target location is identified to the
OFI. In normal modes (*Nattack* *Noffset*, *BOCFIytoO*, *HUDdownl*. and *HUDdown2*), the
pilot sees the target or a landmark near the target and identifies the point to the OFP by designating
when the aiming symbol or standby reticle overlays the point.
In bomb-on-coordinates modes (*BOC*, *BGCoffset*). the OFP computes the location of the
target or landmark by comparing Fly-to coordinates to present position coordinates.
I
In *CCIP* mode, the pilot may release a weapon at any time. The OFP displays HUD symbols
to show the pilot the location that would be hit if a weapon were released now. U
The offset modes (*Noffset*, *HUDdown2*, and *BOCoffset*) identify a target by its posi-
tion relative to a landmark, as the following figure shows.
North
3
Landmark (OAP) Offset bearing to target
Target m
In *Manrip* and *Walleye*. the pilot may release the weapon at any time. In *Manrip*, the
OFP calculates release time to space a stik correctly.
The weapon modes also differ in the pilot displays, especially HUD symbols, and the type of
ranging used to calculate horizontal and vertical components of the distance to target. Ranging is dis-
I
cussed in the navigation update mode overview.
The special weapon modes operate essentially the same as the parent mode (e.g.., *BOC* is the U
parent mode of *SBOC*).
These points are summarized in the overviews that follow. 3
3.6.1. Normal Attack (*Nattack*) g
How target location identified: Visually by the pilot. The TC-2 is notified by the position of the
aiming symbol at designation or after each slew.
Additional target information: Burst height. If baroaltimeter highest priority available sensor:
altitude, MSLP.
I
220m
l
NRL REPORT 91g4 Weapon delivery modes
Additional target information source: DEST 1-9, OR IF MARK 0-9 OR DEST 0: Altitude
default (0 ft), burst height default (0 ft) and MSLP default (29.92)
Designation signaled by: Target designate button or release button or first slew or retained from
*BOC*, *BOCFlytoO*, or *BOCoffset* modes
Air to ground ranging used: Ranging is started on mode entry. There is no sampling until the
first slew or until designation. Thereafter, the sampling is done when a target is designated and at the
end of each slew.
Sources for Target ranging: Upon designation and after each slew, the priority sensor is used as
the source. At other times, the target is dead reckoned.
How target location identified: Offset from a landmark (offset aimpoint) that is identified visually
by the pilot. The landmark is identified to TC-2 by the position of the aiming symbol at designation.
Additional target information: Burst height, delta height (difference in altitude between landmark
and target), range (distance from offset aimpoint to target), bearing (direction from offset aimpoint to
target); if baroaltimeter highest priority sensor: altitude, MSLP
Air to ground ranging used: Started on mode entry no sampling until first slew sampling at desig-
nation and after each slew
Sources for Target ranging: Upon designation and after each slew. the priority sensor is used as
the source. At other times, the target is dead reckoned.
Additional target information: Burst height if baroaltimeter highest priority available sensor: alti-
tude, MSLP
Additional target information source: DEST 1-9. or IF MARK 1-9: Altitude default (0 ft), burst
height default (0 ft) and MSLP default (29.92)
221
I
Chapter 3 ALSPAUGH. FAULK. BRITTON, PARKER, PARNAS, AND SHORE I
Air to ground ranging used: None
Designation signaled by: Target designate button or release button or first slew 5
Undesignation by: Target designate button if already designated
Additional target information: Burst height, delta height (difference in altitude between offset
aimpoint and target), range (distance from offset aimpoint-to target), bearing (direction from offset
aimpoint to target), if baroaltimeter highest priority sensor: altitude. MSLP
Sources for Target ranging: After each slew, the priority sensor is used as the source. At other
times, the target is dead reckoned.
I
222 I
NRL REPORT 9194 WeLpon delivery modes
How target location identified: Impact point at the moment the release enable pressed; release is
allowed any time in mode; HUD shows where bomb would hit if released now.
Additional target information: If baroaltimeter highest priority available sensor: altitude, MSLP;
burst height always 0
Additional target information source: DEST 1-9, OR IF MARK 1-9 OR DEST 0: Altitude
default (0 ft), MSLP default (29.92)
Air to ground ranging used: On mode entry, antenna slaved to intersection of ASL and solution
cue.
How target location identified: First weapon released when release enable pressed-TC-2 com-
putes spacing of remaining weapons in the stik.
How target location identified: Visually by the the pilot-TC-2 notified by the position of the
standby reticle at designation. which it assumes at HUD ORA.
Additional target information: Burst height; if baroaltimeter highest priority available sensor:
altitude. MSLP.
Additional target information source: DEST 1-9, OR IF MARK 1-9 OR DEST 0: Altitude
223
I
Chapter 3 ALSPAUGH. FAULK. BRITTON, PARKER. PARNAS. AND SHORE 3
default (0 ft), burst height default (0 ft), and MSLP default (29.92)
Air to ground ranging used: Started on mode entry; no sampling until designated; sampling at
designation
How target location identified: The A/C is flown to place the aiming reticle over the target,
which should place the target within the Walleye seeker field of view, causing the target to appear on
I
the radar scope television display. The A/C is then flown to place the target at the center of the
television display. I
Additional target information: Altitude. MSLP
Designation signaled by: Same as parent mode, except release enable button will not designate
Additional target information: Burst height; if baroaltimeter highest priority available sensor:
altitude, MSLP
Additional target information source: DEST 1-9, OR IF MARK 1-9 OR DEST 0: Altitude
default (0 ft), burst height default (0 ft), and MSLP default (29.92)
225
Chapter 3 ALSPAUGH. FAULK, BRITTON. PARisER, PARNAS. AND SHORE
How target location identified- Offset from a landmark that is identified visually by the pilot -
landmark identified to TC-2 by position of the standby reticle at designation, wvhich it assumes is at
H-U'D ORA3
Additional target iritormation: burst height, delta height (difference in altitude between landmark
and target), range (distance from landmark-offset aimpoint-target), bearing (direction from offset
aimpoint to target), if baroaltimeter highest priority sensor: altitude. NISLP
Additional target information source: DEST 1-9
226
NRL REPORT 9194 Weapon delivery modes
Current S c
.
'WNone-
I~~~
--
- - - - -
--------- ------------------
- -----------
F---------------
T-------------------------
-I~- - - - - ------------------
------------- f-----------------------------
~~ -------------- T - WD-.MFS
..........................................- -------------
.......... ...................... T-------------
.I T -- -- -------
---------- ---------------------- T---------
.--.--.--.--.--.--.--.--.--.------------------------- T- -------
F----- --- -- ----- t------- -------
* T----- ------ t------- ---- -----
T ------- t----------------
T - -- - t--------------
OFF-MFS
- - - ------ r -- -- --- ----------- T - 'VNone*
t--------------------------------------------------------------
I Note: In this table, "T" and "F" are used to represent "@T" and "@F", respectiveljy.
227
Chapter 3 ALSPAUGH. FAULK. BRITTON, PARKER. PARNAS. AND SHORE
Current <Ik
Mode \ ;9 o V. "-P \ ' \ New Mode
WD...MFS
-----
- - -
-- - - - - -t --
-
-t
-
----
-- --
------
-- --
---------
-- -- T
T
OWVZone U
------------------------------------------------
t .. . . . . . . . . . t ---- - - - - - ------ T N tak
-------------------------------------------------
-- t---------------------------------------------------------- atc
t -------.........------- t------------------------------- ofe
-t ft ~t -t.-t-----O 8coffseto
---------------------------------------------------- T-C-
-- t---------------------------------------------------------- I~on
--------------------------------------------------------
t - - ----------------------- - t -
- -
- -
- t
- - t - -- -- --- ---- T *IIUattacks
t ------------- t----------------------------------
-----
t-
- -t---
- t ----------
--
-
-I---I---------------------t-------------------BCFvo
-- ---
-
-
-
t--
t------------T
--
-------------
--
-S-O-
-- t-- --
. .eT
-- T IS
---------- -- -- t-------------------------------------
228
NRL REPORT 9194 Weapon delivery modes
Current It b%,\~\
Mode 0NwMd
*Nattack*
--------------------- t--------------- - *WNone'
------------------------------------------------------
-------------- F------------------OFF-.MFs
- - ------------------------------
F - - ------------------------- ---
-------------------------------------------------------
-------------- T-------------- -
- - Nattawk*
-------------------------------------- T----------------
- F---------------------------------UDdownl*
Noffset*
---------------------------- F - -WNone*
---------------------------------------------------
-------------------------- F-------------------------------------
---------------------------------------------------------
- - ---------------------------------------------------
- T--------------------------- ---- ---------------------
----------------------- T-----------------------------------------Noffset*
--------------------------------------- T----------------
F------------------r
F - - IIUDdown2*
229
Chapter 3 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
Current 4
Mode ,\ INIO\$N New Mfode
OBOCS
- ---
------------------------------
------- -- -- --t - -.-- T--- F - - WNone 3
. . .--------------------------------------------------
- - - -- -- -- -- - - - - - - - - - OFFJVIFSI
- ---------- T--------------------------I
-- -------------------------------- -- --
- - ---------------------------------
------------ -- T----------------------------------------
------------------------------------ t----------------
-- T-------------------------------------------------
.--.-.-.-.-.-.--.-.-.-.-.--- F- ------------ -- -- -- ---- OFF--NFS
F - - -T---------------------------
-----------------------------------------
F------ B0
--------------------------------- BCytO
230
NRL REPORT 9194 Weapon delivery modes
*BOCoffset*
--------------------------- F - WNone*
............--------------------------------------------
............................. F------------------OFF-N1FS
--------------------------------- T-----------------------
F---------------------------- - - ---
- - --------------------------- -- --
- - -----------------------------
T........................................................... - - Won
------ T----------------------------------------------
- - ---------------------------- -- -
F----------------------------------------------------
- -T----------------------------------------------------
- --
- - - - - - T - - - - - - -23--1
Chapter 3 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE5
ff IQI\ 4 ap O
C~q0
Current ' kP
Mode N4 ,~ : * \, \$\iNONON New Mode
*HUDdownl*
---------- - - --
-- -- -- -F - VNone*
. . . . . . .T-
-------------------
------------------------
-- -
F-----------------------------------------OF
- -- -- - ----------------
-T-------------------------------
-
S
IFSI
- - ----------------------------- -- ---
- - ------------------------ -- - - - --- -- -- ---
------ T--------------------------------------------------
- ----------------------------- f---------------------------Ntak
-..-.-.-..-.-.-..-.-.-..-.-.-..-.-.-.......- -- -- ---------- HUDdownl*
*HUDdown2*
......................................................... F * WNone*
-----------------------------------------------
----------- T----------------------------- - --
-- -- - - - ---
- F--------------------------------------------OF2F
--- -- T - -- -- --------------
------------ WD-AfFS
- T- ----------------------- - - -- -- -- -- -- ---
- T ---------------------------- -
-T --------------------- f----------------------------No~e
. . ... .. . . . . . .T - HUDdown2 3
232
NRL REPORT 9194 Weapon delivery modes
'A/G Guns*
.--.-.-.-.-.--.-.-.-.-.--.-.-.-.-.--.-.-.-.-.--.--------- F *WNone*
------------------- F-----------------------------------------OF2F
- - -T---------------------------- F - - - -----
---- - - - - ----- FS
----------------------------------------------------------
'A/A Guns*
------------------------- -- - - -- --
-- -- ----- - - 'WNone*
---------- F---------------------------------------------
- - -------------------------------------- OFF24FS
- -T--------------------------------------------------
........------------------------------------------------
---------------------------------------------
--------------------- T---------- - -- - - - -----
*\anrlp*
F------------------------------------ - - Voe
-- ------------------------------------------------------
-------------------- T------------------------------OFF2%!FS
------------------------- T-------------------------------
-------------------------.----- T------------- - - - - - - - -- '
233
Chapter 3 ALSPAUGH, FAULK,. BRITTON, PARKER, PARNAS, AND SHORE
Current R i>0
Mode %-C \\, O $ NwMode
*A/A Mazirip*
- -- -------------------- - OWNone I
F.............................................................OFF2-fFS
------ F----------------------------------------
..........................-- -- -- ------------- WD...MFS
*Snattack*
Woe
--
F-------- --
-- - - - -- - - ~~n
F----------------------------------------------------
-- -------------------------------
- -- ------------ F---------- -- -- ---
ID
-
-~~~~ - -
------- T-------------------- - ---- -- -- -- -- ---
T----------------------------------------------I
II
234
,NRL REPORT 9194 WVeapon delivery modes
.YfIAc 4o AV4 4t
0' 0~ 0 t '5 A
Mode NwMd
*Snoffset'
--------------------------- F - WNone*
--------------------------------- - -- - -----
------
------------------------------------------------
--------------------------- - - - ---
---------------------------------
------------- - - - -- -- --...............................
-~~~~ - - -T--------------------------- - - - --
- -- --
----------------------------------- -- - - ---- -- --
------- T--------------------------------------------------
------------- T---------------------Snoffset*
OSBOCO
-------------------------------------------------------- FF. - WNone*
-------------------------- T-----------------------------
- -- ----------------------------
---------------------------------- T----------- -- -- -
- T ---------------------------------------------------
------------------------------- - - - SOC
-------------- T-----------------------------------------
._____
.[-.-- ..-- .T---------------
.-- - -- -- --- - - - -
235
Chapter 3 ALSPAUGH, FAULK. BRITTON, PARKER, PARNAS. AND SHORE
Current Ne ModA'A~
Mode *\4,'oc 41cO Nwde
*SBOCFlytoO*
---------- - ---- -- -- - - None I
----------------------
-- -- -- F------------------------------------
-- ------------------------------------------------
----------------- -T----- ------------------------
*SBOCoffset
---------- - ---- -- -- - - VtNone'
I
-------------------------------- -- - - -T
----------- F------------------ - - --- -- -- ---
-------------------- F------------------------------------
- -- - -- -- - - - - - - - - - - - - - - W D...MFS
- -
.--.-.-.-.-.--.-.-.-.---
T-----------------------------------------------I
T---- -- --- -- -- --- -------- SBOCoffsetO
236
NRL REPORT 9194 Weapon delivery modes
Current COC
Mode sp NewMode
*Waiieye
------- -- -- -- -- --
- - --- - -
I None*
------------------------ T-------------------------------
----------------------------- - - - - ---
------------------------------- T------------------------
--------------------------- - - ----
- - -------------------------------
- - ----------------------------- -- ---
--------------------------- ------
F.........T------------------------ - - - - -----
--- -- --
------------------- -T------------------------------
-..-.-.-..-.-.-.- ..-.-...- -- - - - -- ---- -- ----- ---
237
I
Chapter 3 ALSPAUGH. FAULK. BRITTON, PARKER. PARNAS. AND SHORE
!TMTstage! Timer The 10 and 16 bit counters are checked against the
GO/NO-GO counter to make sure they generate
3
interrupts at the proper time. If this test is correct,
the 10 and 16 bit counters, as well as the
GO/NO-GO counter, are assumed to be operating
correctly.
!GA Tstage! Gyro Accelerometer Using the BITE command to wrap output signals
to inputs, values are written to the gyro counters
3
and read back from the accelerometers. The input
values should match the output values. i
DIO Tstage! Discrete I/O Using the BITE command to wrap output signals
to inputs, values are written to discrete output
words 1 and 2 and read back from discrete input
words 1 and 2, respectively. The input values
I
should match the output values.
!SC Tstage! Serial Channel Using the BITE command to wrap output signals
to inputs, values are written to the cycle steal
I
channels and read back from the serial input chan-
nels. The input values should match the output
values. The HUD attack test pattern is displayed
For each of the three Signal Converter test stages listed below, the following occurs: the associated i
output channels are loaded with specific values. An input value, hardware-generated as a function of
the output values, is read in. An error occurs when this input value is not equivalent to an expected
value (different in each stage). This test verifies the accuracy of conversions. The timing of the 'Data
Ready" interrupt is also checked.
I
I
I
238
NRL REPORT g194 Test mode
UStage sequence:
Coresum !CS Tstage!
Timer !TM Tstage!
Gyro Accelerometer !GA Tstage!
Discrete I/0 !DIO Tstage!
Serial Channel !SC Tstage!
DC Signal Converter !DC Tstage!
AC Signal Converter I !AC1 Tstage!
AC Signal Converter 2 !AC2 Tstage!
Panel Display !PD Tstage!
HUD: attack test pattern displayed at the end of !SC Tstage!. The pattern displayed depends on the
value of the master function switch (see Figure 3.7.1-a). The left pattern is displayed when no func-
tion is selected. The right pattern is displayed when any function is selected.
I
I
I
I
I Figure 3.7.1-a: HUD test patterns
I
239
Chapter 3 ALSPAUGH, FALLK, BRiTTON, PARKER, PARNAS, AND SHOREI
240
I
I
CHAPTER 4
I
I
4.0. INTRODUCTION
4.0.1. Overview
I- This section gives the values of the output d-.ta items as a function of A/C situation. In most
cases, we do not .- ,ecify how the output values are related to the input values; the requirements state
that output values must bear a certain relationship to the actual flight conditions, and the input values
are considered only a means for acquiring the correct values. However, in some situations, the pilot
must have the ability to choose from alternative sources of similar information (e.g., a barometric
altimeter or a radar altimeter) or the system must choose from alternative data sources on the basis of
external conditions. In these cases, the requirements must be expressed by naming the sources of
input data appropriate for different conditions. In short, where the system implementor is free to
choose his input data sources, we do not name them. Where requirements dictate the input data
sources, output values are expressed as functions of input values.
The services required of the OFP are described in terms of a set of functions. Each function
determines the value for one or more output data items. For example, the values of //FPMAZ// and
,//FPNEL//areboth determined by the function called "Update Flight Path Marker Coordinates."
The display windows on the TC-2 panel are used to display so many different values that we
have described the computation of each value as a separate function. In effect, we have described each
function as if it had its own continuously available display window and its own set of output data
items. Ve are then able to describe separately the rules that determine which information is actually
displayed aPd the rules that determine the various values.
4.0.2. Organization
Each function is described in a section that (a) lists the modes in which the function must be
performed. (b) names the output data items affected. (c) describes the conditions under which the
function must be performed, and (d) includes one or more tables giving a detailed description of the
output values in terms of aircraft situations or input values. The functions are described without the
timing requirements, which are given in Chapter 5.
Every function is classified as either periodic or demand. A periodic function will be per-
formed repeatedly at regular intervals. If it is not required all the time. the section lists the events
that initiate and terminate performance. A demand function is initiated by a specific event, such as a
button being pushed. For a demand function, we describe the events that cause it to be executed and
the action required after each event.
Each function is also classified by the hardware device associated with its output data items.
For example, there are IMS functions to provide values IMS output data items. Chapter 4 is
'"
241
I
Chapter 4 ALSPAUGH. FAULK. BRITTON, PARKER. PARNAS, AND SHORE
organized by hardware devices, with all the functions for one device in the same subsection. The sub-
sections are given in the order that the devices are described in chapter 2. Within each subsection, the
functions are given in the same order as in Chaptei 2. However, even if an output data item is
transmitted to more than one hardware device, the function associated with it is only described in one
place in Chapter 4.
II
I
I
I
I
I
U
I'
I
I
I
I
242
NML RPORT 9194 RAfS Functions
MODES EVENTS
*Luoa* @T(nmoe @F(In mode)
*Sauoal*
ACTION /AUTOCAL//:=$OnS /.AUTOCAL! :=$Of1S
2-I
Chapter 4 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
MODES EVENTS3
@T(!roll large!) @F(!roll large!)
VV
WHEan*
N (!FM stage!) 'WHEN (!FM stage! AND
OR //COMPCTR//-$On$)
@T(!FM stage complete!) ORI
OR @T(!FM stage!)
@T(In mode) WHIEN(NOT !FM stage! WHEN (NOT !roll large!
AND //COMPCTR//=$OflS) AND //COMPCTR//=On$)I
*DI*
*I* @T(In mode) X
*TDI* WHEN(//COMPCTR//=$Off$)
*OLB*
*PolarDI*
*PolarI*3
*Mag Sl*
*Grid* X @T(ln mode)
*IMJS fail* WHEN (I CONPCTR / /=$OnS)-
ACTION Computer controlled Not computer controlled
_______/ /COM1PCTR / /:=SOnS //COM1PCTR //:=$Off$
244
I
NRL REPORT 9194 IMS Functions
3Output
Output data item(s) affected: //COMPFAIL//
description:
Event Table 4.1-c: When
Computer System Fails
MODES EVENTS
All modes except X @T(!power up!)
*Grtest*
*Grtest* @T(!Checksum test failed! X
I OR !Interface test failed!)
ACTION //COMPFAIL./ /:=$Yes$ //COMPFAIL //:=$No$
I
I
I
I
I
I
I
I
I
I
I
I 245
I
Chapter 4 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
I
4.1.4. Torque Platform X, Y, and Z Axes
(Periodic function)
Table 4.1-e shows the alignment stages in which Z axis errors are removed by slewing or torqu-
ing. Z axis errors larger than the !slew-torque cutoff! are slewed out (see Section 4.1.6), and smaller
3
adjustments are made by torquing.
Selector Table 4.1-e:
In some modes, the platform axes are only maintained in alignment, that is, compensations are
made for Earth's rotation, A/C movement, and the known drift bias for the particular gyros in the
particular A/C (see Sections 4.6.19 through 4.6.21).
In other modes, the TC-2 corrects the axes for misalignment by comparing the MS velocities to
reference velocities, and using the differences to calculate the platform misalignment. The reference
246
NRL REPORT gi94 IS Functions
velocities used in different modes are shown in Table 4.1-g. Table 4.1-f shows when the axes are only
maintained and when they are also corrected.
IMODES *Lautocal*
X AXIS ACTION Y AXIS ACTION Z.AXIS ACTION
I*Sauoal**Landaln*
*SINSaln*
Maintained and
Corrected
Maintained and
Corrected
Maintained and
Corrected
*OlUpdate*
*Aran
*HUDaln*
!latitude! < 80
**Maintained Maintained Maintained
*UTDI* OLB* !ltitude! > 80:.
247
Chapter 4 ALSPAUGH, FAULK, BRITTON. PARKER, PARNAS, AND SHORE3
MODES EVENTS
*Lautocal*
*Landaln* @T(In mode) WHEN x
*OlUpdate* (//UMSSCAL //=$Coarse$)a
*HUjlJ)nf* @T(In mode) WH1EN @T(In mode) WHEN
(/lMSMODE/ = SGndal$ (/IMSMODE/ = ($Norm$ OR SInerS)
AND / /M SSCAL //= $Coarse$) AND //IMlSSCAL// - $Fine$)
___________________n
248
I
NRL REPORT 9194 IMS Functions
i
4.1.6. Switch X,Y,Z Slewing On/Off
(Demand function)
Note: Platform slewing can only occur when //COMPCTR// = SOnS; (Section 4.1.2).
I Zaxis slewing occurs (a) when Z axis errors are to be removed during the alignment stages
shown in Table 4.1-e if the velocity error calculations show that the Z axis is out of alignment by more
than the !slew-torque cutofP (b) in *Lautocal* and *Sautocal*, to rotate the north-pointing axis so
that it points east, and later to move it back. and (c) to remove heading errors in *SINSaln* and
*HUDaln* modes. The second two kinds of slewing are summarized in Table 4.1.j.
I
I
I
I
249
I
I
Chapter 4 ALSP4UGH. FAULK. BRITTON. PARKER, PARNAS, AND SHORE 3
Event Table 4.1-j: Z Axis Slews i
MODES EVENTS
*Lautocal* @T(!ED stage!) @F(!ED stage!) X x
*Sautocal*_______
*SINSaln* X X @T(In mode) X
@T(/TD/--$On$) WHEN
*HUDaln* X X X (NOT !during
platform slewing!)
AMOUNT OF
SLEWING
90" CCW 90' CW + error
in !ED stage!
!SINS-
error!'
!Az-reference
error!2 3
PERFORMED (see Table 4.1-e)
"SINS error! is the error calculated by comparing !IMS heading! to !SINS heading! corrected by !Delta I
heading!
2!Az-reference error! is the error calculated by comparing the !IMS heading! to the heading calculated
from the !azimuth reference heading! corrected by the Aiming Symbol azimuth displacement at desig-
nation.
I
I
I
I
i
I
I
I
I
I
25C i
NRL REPORT 9194 IM Funcuions
MODES EVENTS
All Alignment and @T(In mode @T(In mode
Navigation Modes AND !latitude! > 70 1AND flatitude! <0
ACTION /LATGT7O //:=$Yes$ //LATGT7O / / :-No$
25 1
Chapter 4 ALSPAUGH, FAULK. BRITTON. PARKER. PARNAS. AND SHORE3
Note: Blinking takes precedence (see Table 4.1-rn). At the termination of blinking, the light
goes to the state for which the condition has most recently been met. (The state may have changed
*
several times while the light was blinking.)I
252
NRL REPORT 9194 MI4S Funenions
Output description:
Event Table 4.1-rn:
When [MIS Non-Aligned Light Flashed
MODES EVENT.S
*SINSaln* @T(In mode AND !SINS down!) @F(!SINS down!)
*Airaln*
*DIG* @T(In mode AND @T(!IMLS-Dop Reasonable!
*DI* (NOT !IS-DOP Reasonable! OR AND !IS-ADC Reasonable!
UDMI* NOT !IS-ADC Reasonable! OR AND !TMS Reasonable!)
*PolarDl* NOT !IS Reasonable!))
*1*
*Polarl*
ACTION Initiation Termination
//ISNA,// alternated between //IM NA// returned to
$On$ and SOfYS state specified by tbl 4.1-1
set by other INA function
______________
___________________________ (Section 4.1.8.1)
253
Chapter 4 ALSPAUGH. FAUJLK. BRITTON. PARKER. PARNAS, AND SHORE
MODES EVENTS3
*RadarUT d* @T(In mode AND !ground range' @T(None of listed modes)
__________to !fixpoint! <22nmi) OR @T(/MFSW/=STFS)
254
NRL Report 9194 FLR Functions
I position. The reference point varies. depending on the mode and prevailing conditions, as shown in
the tables below.
_____________
_____________
!target! !OAP!
__________in
a point on the
!ground track! 8 nmi
front ofA/C
25
I
Chapter 4 ALSPAUGH. FAULK, BRITTON. PARKER. PARNAS. AND SHORE
U
4.2.2.1. Update Azimuth-Cursor Position
(Periodic function)
CURSOR
POSITION
out of
view
left edge BRG" from
center
right edge
3
Whenever the cursor is displayed, the pilot can move it. using the slew control. Inputs from
'SLE\\rRL/ affect the azimuth-cursor position changing it at the !Radar rate!. The slew control dis-
placement from center indicates the rate and direction of movement.
2
U
I
I
I
256
NRL Report 9194 FLR Functions
Initiation and termination: This function is performed when and only when
'/CURENABL//=$On$.
Output data item(s) affected: //CLRPOS//
Output description:
The output is required in the following modes: *RadarUpd*, *BOC*, *BOCFlytoO*,
*BOCoffset*, *SBOC*, *SBOCFytoO* and *SBOCoffset*
The value output for //CURPOS/! is the !slant range! from the A/C to the reference point
defined in Tables 4.2-b and 4.2-c. The !i1 CURPOS// output value is limited in the following way:
//CURPOS//:=MIN(!slant range!, 20 nmi)
If the azimuth cursor is out of view (see Section 4.2.2.1), i/CURPOS/,i:- 0.
Whenever the cursor is displayed, the pilot can move it, using the slew control. Inputs from
/SLEWUD/ affect the //CURPOSi'i value, changing it at the !Radar rate!. The slew control dis-
placement from center indicates the rate and direction of movement.
Note: The value output by this function is !slant range! even though the cursor actually shows
!ground range!. The conversion from !slant range! to !ground range! is performed by the FLR (see
Section 2.1.3.7).
257
I
Chapter 4 ALSPAUGH, FAULK. BRITTON, PARKER, PARNAS, AND SHORE 3
I
4.2.3. Slave or Release the FLR Antenna
(Demand function) 5
Output data item(s) affected: //ANTSLAVE//
Output description:
MODES EVENTS I
*HUDUpd* @T(In mode) @F(In mode)
*Nattack*'I OR @T(/MFSW/=STFS)
*Noffset*
*CCIP*
*HUDdownl* @T(In mode) @F(In mode)
*H-UDdown2* OR @T(/MFSW/-$TFS)
*Snattack*
*Snoffset*
*SHUDdownl*
*SHUDdown2*
@T(/GUNSSEL/= SYes$)
*A/G Guns* OR @F(hu made)
"A/_______@T(In mode AND !Rockets!) OR @T(MFSW/=STFS)
*Grtest* @T(ACI Tstage!) @F(!AC2 Tstage!)
OR @T(!AC2 Tstage!) OR -T(/MFSW/--$TF)
ACTION //ANTSLAVE//:=$OnS //ANTSLAVE//:-$Off$
Note: In the software, (//ANTSLAVE// = SOnS AND //CURENABL//'= SOnS) does not occur. 3
I
I
I
I
U
258I
NRL Report 91g4 FLR Functions
Initiation and termination: This function is performed when and only when /' /ANTSLAVE/''
259
Chapter 4 ALSPAUGH, FAULK. BRITTON. PARKER. PARNAS, AND SHORE3
MODES EVENTS
All Alignment @T(In mode) @T(No listed mode)3
and Navigation
*HUTDUpd*
*RadarUpd*
*Noffset*
*NattaI
*CCIP*
*Snattack*U
*A/G Guns*
*HUJDdownl*
*HlJDdown 2 *I
*SHUDdown I*
*SHUDdown2* ______________
260
NRL Report 9194 FLR Functions
MODES CONDITIONS
Alignment /ACAIRB/ ACAIRB/ X X X
Navigation =$No$ =$Yes$
with no modes
listed below
*tIUDUpd*
*Nattack* X '.ANTSLAVE/, //ANTSLAVE/ X X
*Noffset* =$Of1s =$On$
*A/G Guns*
*HUDdownl*
*HUDdown2*
*SHUDdownl*
*SHUTDdown2*
*Snattack*
*Snoffset*
*CCIP* X X X Always X
*Grtest* X X X X !AC1 Tstage!
!AC2 Tstage!
261
I
Chapter 4 ALSPAUGH. FAULK, BRITTON. PARKER. PARNAS. AND SHORE 3
I
4.2.8. Update Ground Track Velocity
(Periodic function) 3
Initiation and termination:
Event Table 4.2-i: When Ground Track Velocity Must Be Output I
MODES EVENTS
All Alignment @T(/MFSW/=$TFS) @F(/MFSW/=$TF$)
and Navigation modes
*Grtest* @T(!DC Tstaxe!) @F(!DC Tstage!)
ACTION Initiation Termination
Must be output Output is ignored by FLR'
I
I
I
I
$
I
II
U
262 3
NRL Report 9194 FLR Functions
MODES EVENTS
All Alignment and
Navigation modes
Nattack*, *Noffset*
*BOC*, *BOCFlytoO* @T(In mode) X
*BOCoffset*, *Snattack*
*Snoffset*, *SBOC*
*SBOCFlyto0*
*SBOCoftset*
*HUDdownl*. *HUDdown2*
*SHUDdownl*
*SHUDdown2*
*Grtest* @T(!DC Tstage!) @T(In mode) OR
_@FEL!DC Tstage!)
ACTION Initiation Termination
Must be output
263
Chapter 4 ALSPAUGH. FAULK. BRITTON, PARKER, PARNAS. AND SHORE3
'MODES CONDITIONS
*Ajraln*, *DIG', *DI* /IWSW /=STFS (NOT /AMFSW/=$TF$) X
*'I' UDI*' AND ORI
'PolarDI' 'PolarI' /ACAIRB/=$Yes$ /AGAIRB/=$No$
No applicable weapon
modes' ____________
'The applicable weapons modes are: 'Nattack'. *Noffset*' 'BOG', *BOCFlytoO*, *BOCoffset*,
'Snattack'. *Snoffset*, 'SBOC*, *SBOCFlvtoO*, *SBOCoffset*, 'HUDdownl', *HUDdown2*,
*SHUDdownl', *SHUDdown2*.
2
!limited flight path angle! = SIGN (Mfight path angle!) X MIN(ABS(!flight path angle!), 21.6')
MODES ______CONDITIONS______
264
INRL REPORT 9194 HUD Functions
I Initiation and termination: In Table 4.3.1-a. !Range! refers to the ground range from the A/C
present position to the reference point defined in Tables 4.3.1-b and 4.3.1-c.
MODES EVENTS
U *A/A Guns*
*A/G Guns*
*BOCFlyto3*
*H1TDdowni* @T(In mode) X
*HUDdown2*
3 *SHTJDdown1*
*SHUTDdown2*
*Snattack*
*Snoffset*
*Grtest*
*BOC* @T(In mode AND !Range! < @T(In mode AND !Range!
*BOCoffset* 30 nmi) > 30 nmi)
*SBOC* @T(In mode AND !Range! < @T(In modeA-ND !Range!
*SBOCoffset* 30 nmi) > 42 nmi)
*RadarUpd* @T(In mode AND !Range! < @T(Jn mode AND !Range!
_______________ 20 nmi) > 20 nmi)
*HUDUpd* @T(ln mode AND !Range! < @T(Ln mode AN!)D !Range!
_______________ 22 nmi) > 22 nmi)
U *Walleve*
*OlUpdate*
CaT(ln mode)
_dln
x
*1* *OLB*
*PolarP ______________
265
Chapter 4 ALSPAUGH, FAULK. BRITTON. PARKER. PARNAS. AND SHORE3
4.3.1-c. In sonme cases, the original position of the symbol is determined by comparing the known
coordinates of the reference point to the A/C present positions. In other cases, the pilot moves the
symbol by slewing to overlay a point that he sees. When the Aiming Symbol is "ground stabilized,"
that is, it overlays a fixed point on the ground, the symbol is moved on the HUD to compensate for
A/C movement.
At other times, rather than following a fixed point, the Aiming Symbol shows a point that bearsI
a particular relationship to the A/C position. such as being a fixed distance away from it. In this case,
the point changes as the A/C moves. The main example is given in Table 4.3.1-d; when the Aiming
Symbol overlays !imnpact point!, it shows the location that would be hit if the gun were fired now.I
In most modes, the pilot can change the AS placement by slewing. The slewing rate depends on
the chosen mode - either the !HUD rate!, or the faster !Radar rate!. !During slewing!, the AS symbol
placement is derived from its previous placement and inputs from the slew controls (/SLEW~RL/ and
/SLEW!JD/), which give a rate and direction of movement. Table 4.3.1-f shows wvhen slewing is
allowed and at which of the two rates.
*HfJDaln*
*Landaln* X X !Before !After
Ol1Update* slewing! slewing!3
*1*1
*OLB*
*Grtest* X X Always; X
1
REFERENCE !Called-upi !fixpoint! HUD !adjustedI
POINT point! center point!
(ground (ground
_______________stabilized) stabilized) _______________U
'In *HUDUpd* mode the following limiting occurs, where !ASAZ! and !ASEL! are the values before3
limiting:
','ASAZi': SIGN(!ASAZ!) x NIIN(ABS(!ASAZ!), 5.5)
266
NRL REPORT 9194 HUD Functions
I*Snattack*
*Nattack*
*LWDdownl *
NOT !Desig! x X !Desig! X
*SHUDdownl*______ ______
I*BOC*
*SHUrDdown2*
*SBOC*
_____________________
X
________slewing'
!Before X
_______
_____________
!After
slewing!
X
_______
IPOINT
REFERENCE HUD
Airnsight
(see
!fly-to
point!
(ground
!OAP!
(ground
stabilized)
!target!
(ground
stabilized)
point on
!ground track!
8 nmi in front
_elow) stabilized) of A/C
MODES CONDITIONS
*Nattack*
*H T5 dwnl* 'Shrike! NOT !hie
*Snattack* x Always
*Snoffset*
HIJDdown2*
*SHUTDdownl*
*SHUrDdown 2 * ____________
*Walleve* Awy
HUD Aimnsight !weapon boresight! Point overlaid bv FPM
267
Chapter 4 ALSPAUGH. FAUJLK, BRITTON. PARKER. PARNAS. AN"D SHORE3
MODES CONDITIONS
(NOT !release (!release possible!
possible! AND A.ND NOT !Shrike!)I
*Nattack* NOT !Shrike!) X OR
OR (NOT !designation
(!designation retention! AND
retention! AND !Shrike!) ______________!Shrike!)
*Landaln*
*0IUpdate* Always XN5
*OLB*
PolarI* I___________
2683
I
NRL REPORT 9194 HUD Functions
3 MODES EVENTS
*Nattack*, *Noffset*
*BOC*, *BOCFyto0*
*BOCoffset*, *CCIP*
*HUDdownl*, *RI-UDdown2* @T(In mode) @F(In mode)
*Snattack*, *Snoffset*
*SBOC*
*SBOCFytoO*
*SBOCoffset*
*SHUDdown 1*
*SHUDdown2*
*Grtest* @T(!WVD MFS! AND @T(In mode) OR @F(!\WD MFS!)
end of !SC Tstae!) OR @F1In mode)
ACTIONS !//HUDASL//:=$OnS //HUTDASL// :=$OffS
OR placed out of view
II
I
I
Chapter 4 ALSPAUGH. FAULK. BRITTON, PARKER. PARNAS, AND SHORE 5
Imaginary line parallel to pitcb lines
I
" FPM I
Figure 4.3-a
The ASL position is limited by the software in the following way, where !ASLEL! and !ASLAZ! are
the values before limiting:
//ASLAZ// := SIGN(tASLAZ!) x JffN( ABS(!ASLAZ!), 6.7")) I
I
I
I
U
I
I
270I
NRL REPORT 9194 HUD Functions
MODES ______-CONDITIONS -
*Nattack*
Jdon*SnaLLack*
*HUDdown2* X NOT !Desig! !steering !OTS! !GAS!
I *Noffset*
*BOCFlytoO*
*Snoffset*
to target!
*SBOCFlytoO*
*SHUDdownI
_ __ _ __ _ _
*SHUDdown 2 * ________
I *BOC* !Range!' X
k.ange! <
30 nmi AND
!steering !OTS! !GAS!
AND
!Desig!
to target!
!Range! <
30 nmi AND
*BOCoffset* !Range! !Range! < !steering !OTS! !GAS!
IASL SBOCoffset*
PLACEMENT
> 30 nmi
!steering
error!
30 nmi
ASL Line
Intersects
to target!
!alternate
steering!
_______
-(half of
!steering
edge of
HUD to
from FPM AS2 display' error!) closest
(same as from FPM return
___________ //FLTDIRAZ,/ _____ ____ __
"!Range! means ground distance from A/C present position to the aiming symbol reference point.
Itered Iln *Nattack* and *Snattack*, the AS is centered in the FPM, so the ASL center would also be cen-
in the FPM: in *BOCFlyo*, *SBOCFlvtoo*. *Noffset*. and *Snoffset*. the AS may be dis-
placed from the FPM. causing the ASL center also to be moved.
3
I 'Ajternate steering! has two substages. When the horizontal range to the target is > 48.000 feet. the
steering error is calculated to cause the A/C to fly over the target. WVithin 48.000 feet. the steering
error is calculated to take the A/C to the proper place to release the weapon. which may not be
directly over the target.
When the A/C pitch gets large. the steering error is multiplied by the weighting factor showvn
below, because otherwise the error growvs too large to display.
271
Chapter 4 ALSPAUGH. FAULK, BRITTON. PARKER. PARNAS. AND SHORE5
In other modes, the ASL placement depends on other conditions, shown in the table below.U
MODES CONDITIONS
!CIP
impact angle elevation! !impact angle elevation!
> 20 *below A/C boresight < 20 *below A/C boresigh.
*Grtest* Always X
ASL ASL center in FPM ASL center 4' below FPM,
PLACEMENT _______________ ASL intersecting the FPM
MODES CONDITIONS
*Nattack*
*SHUTDdownl*
*SHLUDdown2*
*Snattack*
*Snoffset* Always
*SBOCit*
272
NRL REPORT 9194 HUD Functions
U
4.3.2.2. Update Azimuth Steering Line Angle
(Periodicfunction)
Initiation and termination: This function is performed whenever the ASL is in view (see Section
4.3.2.1)
Output data item(s) affected: ,',ASLCOS// i'ASLSIN//
Output description:
3 MODES
*Nattack*
CONDITIONS
*Noffset*
*BOC*
*BOCFlytoO*
*BOCoffset*
*Snattack* X Always X
*Snoffset*
*SBOC*
*SBOCFiytoO*
*SBOCoffset*
*HUDdownl*
*HUDdown2*
*SHUDdownl*
U
*SHUDdown2* _________________
2
I
I
I
U
'273
I
I
Chapter 4 ALSPAUGH. FAULK, BRITTON, PARKER. PARNAS, AND SHORE 5
I
4.3.3. Update HUD Barometric Altitude
(Periodic function) 5
Initiation and termination: None: always done
Output data item(s) affected: //BAROHUD// 3
Output description:
Condition Table 4.3.3-a: Barometric Altitude Display Values 3
MODES CONDITIONS
All modes LADC Up! AND LADC Up! AND NOT !AL)C Up'
except !Dest 1-9! (.Mark!
*Grtest*l OR !Dest 0!)
BAROMETRIC /BAROADC/ /BAROADC/ 4500
ALTITUDE corrected for corrected for
!FLY-TO mslp! 29.92 MSLP
I
'In *Grtest* mode, the HUD displays a fixed value, the value of /iBAROHUD// at mode entry time.
2
I
I
I
I
I
U
I
I
274 5
NRL REPORT 9194 HUD Functions
MODES EVENTS
All modes @T(!power up!) OR @T(!WD MFS!)
______________ F(!WD MFS!)
ACTION Initiation Termination
I FD moved in view FD out of view
MODES CONDITIONS
NOT *Grtest* /FLYTOTW/'0 /FLYTOTW/=O
*Grtest* X Alwavs
/FLTDIRAZ// SIGN(azimuth steering error) X 0
MIN(ABS(azimuth steering error).5 )
275
I
Chapter 4 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE 3
4.3.5. Flight Path Marker Functions
I
I
U
U
I
I
275 5
NRL REPORT 9194 HUD Functions
I MODES
*Airaln* X
CONDITIONS
!FM stage complete!
-
IAlignment modes
except *Airaln*
Always
OR !ADC Up!
X
AND NOT !ADC Up!
X
*Grtest* ____________
27
U
Chapter 4 ALSPAUGH. FAULK, BRrrTON, PARKER, PARNAS, AND SHORE
U
4.3.5.2. Start FPM Flashing
(Demand function) 3
Output data item(s) affected: //HUDFPM//
Output description: 3
Event Table 4.3.5-b: When FPM Flashed
MODES
*Nattack*, *Nofset*
EVENTS 3
*BOC*, *BOCFytoO*
*BOCoflset*, *CCIP* @T(!rls pts passed! @T(sufficient time elapsed'
*Walleye*, *Snattack* -!stik quantity!) after @T(//HUDFPM// = $Blink$))
*SnofIset*, *SBOC*
*SBOCFytoO*, *SBOCoffset*
*Manri_*
ACTION //HUDFPM //:=SBIink$ //HUDFPM // :=$Constant$
I
'The value of //HUDFPM// should be reset to $Constant$ as soon as the OFP can be sure the HU)
received the SBlink$ value. See Section 2.1.4.6 for timing characteristics relative to this function. 3
I
I
I
I
I
I
I
278
NRL REPORT 9194 HUD Functions
MODES CONDITIONS
All alignment and
navigation modes Always X
,except *IMS fail*
*IMS Fail'IMSMODE/ SOffnone$ /MSMODE/=$Offnone$
*Grtest* X Always
i/MAGH.DGH// !magnetic heading! 0' (North)
279
Chaptr 4 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
U
4.3.7. Update HUD Pitch Angle
(Periodic function) I
Initiation and termination: None; always performed
Output data item(s) affected: //PTCHANG//
Output description: In all modes but *Grtest*, the HUD displays !system pitch!. In *Grtest*
mode, the HUD displays a fixed value, the current value of !IMS pitch! at mode entry time.
I
I
I
I
I
I'
U
I
I
I
I
I
280
NRL REPORT 9194 HMD Functions
In the following table, !Range! refers to ground range to the !Fly-to point!.
MODES EVENTS
*Nattack*, *Noffset*, @T(In mode) X
*BOCFlytoO*, *CIP*,
*A/C Guns*. *WVa1eve* _____________
I Output description:
In most modes, the PUAC shows the pilot how far he is from the "pullup point": the point
where he must execute a 4g pullup to avoid either the ground or the blast radius of a released weapon.
281
Chapter 4 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
MODES CONDITIONS
*Nattack* !slant range! to !slant range! to
*Noffset* !ground pullup point! !ground pullup point!
*BOC* > 5000 ft AND < 5000 ft OR
*BOCFytoO* !slant range! to !slant range! to
*BOCoffset* !blast pullup point! !blast pullup point!
*CCIP* > 5000 ft < 5000 ft
*A/G Guns* (!Rockets!)
*Walleye*
*A/G Guns* (!Guns!) !slant range! to !slant range! to
!ground pullup point! !ground pullup point!
> 5000 ft < 5000 ft
*SBOC* Always X
*SBOCFlytoO*
*SBOCoffset*
*Snattack*
*Snoffset*
*SHUDdownl*
*SHUDdown2*
PUAC ELEVATION 3.5' below FPM 0.7 below FPM
per 1000 ft to
closest pullup point
I
Selector Table 4.3.8-c: PUAC Azimuth
Note: The ground avoidance calculations are based on the assumption that terrain around a target is
fiat.i
The purpose of the ground avoidance calculations
is to keep the A/C above the target altitude
by at least a safety margin of 98 feet. It is assumed to be unnecessary to calculate ground avoidance
unless the A/C is moving down with a vertical velocity of at least 3 fps.
The purpose of the blast avoidance calculations is to keep the A/C outside of a blast sphere of
radius 1500 feet around each bomb burst point in a stik. It is unnecessary to calculate the blast
avoidance if any of the following conditions holds:
(1) slant range to designated target greater than 16,400 ft
3
282I
I
NRL REPORT 9194 HMJ Functions
(2) NOT !Desig!, in one of the following modes: *Nattak*, *NofEset*, *BOCFlytoJ*, *BOCoffset*
(3) *A/G Guns* AND NOT !Rockets!
(4) Wrs pts passed! = !stik quantity!
(5) !overfln!
(6) *Snattack*, *Snoffset*, *SBOC*, *SBOCFlytoo*, and *SBOCoffset*
(7) A/C greater than 1500 feet past impact paint at time of impact
I The target altitude used in these calculations is given in Table 4.3.8-d below.
*Nattack* !Mark!
*BOC* !Dest 1-9! X OR
*CCIP* !Dest, 0!
*A/G Guns*
I*BOCoffset*
*Walleve*
*Noffset*_________________
X Always
____
ITarget *BOCFYto*
altitude:
_________
!Destaltitude!
______________
X
!Destaltitude! +
!Delta Height!________
Alwavs
28
I
Chapter 4 ALSPAUGH. FAULK, BRITTON, PARKER. PARNAS, AND SHORE
I
4.3.8.2. Flash PUAC
(Periodicfunction)
Output description:
Event Table 4.3.8-e: When PUAC Flashed 5
MODES EVENTS
*BOCoffset*, *CCIP*,
*Nattack*, *Noffset* @T(In mode @T(/MA/ = $On$) OR
*BOC*, *BOCFlytoO*. AND /MA/ SOftS) @F(In mode)
*Walleve* _
I
I
I
I
I
I
284
I
NRL REPORT 9194 HUD Functions
I
4.3.0. Flash Pullup Cue
I (Demand function)
Termination: The Pullup Cue stops flashing (i.e., //HUDPUC//:=$Off$) when the pilot pulls
up sufficiently to remove the A/C from danger, or has been flashed for two seconds when !low
drag! AND !Special!.
I
I
I
I
I
I
I
I 285
Chapter 4 ALSPAUGH, FAULK. BRrTTON, PARKER. PARNAS. AND SHORE
286
5 NRL REPORT 9194 HMD Functions
5 >0 When".
sp 5Ou
MODES EVENTS
@T(!target in range! @F(!target in range!)
I Note: If the pitch of the A/C is near 42 *when the target is designated. the Solution Cue is displayed
1 second before the target comes within !maximum range! to give the pilot warning that a release
point is imminent.
287
Chapter 4 ALSPAUGH, FAULK. BRITTON, PARKER, PARNAS. AND SHORE3
MODES CONDITIONSI
*Nattack*
*Noffset* !OTS! !low drag! NOT !low drag!
*BOC* AND NOT OTS! AN!) NOT !OTS!
*BOCFlytoO*
*BOCoffset*
*HUDdownl*
*HU~down2*____________
LOWER 4- SIGN(!dive pullup!) x SIGN(!distance-to-release!)
SOLUTION CUE 'NUN (4', 1 *x 1/8 X MIN(4,'JXI100
DISTANCE FROM X ABS(!dive pullup!)) X ABS(!distance-to-release!))
ASL CENTER
POINT________________ __
ILSC
OR AND
___________________NOT !A IC facing target! !A/C facing tar et!
DISPLACEM\ENT out of view MIN(4 '.1 * X 1/ 1000 X
FROM FPN1 ABS(!range to Rmax!))
288
NRL REPORT 9194 HUD Functions
MODES CONDITIONS
Selector Table 4.3.11-e: Other Positions for the Lower Solution Cue
2
I
I
I
I
U
I
I
289
I
Chapter 4 ALSPAUGH. FAULK. BRITTON. PARKER. PARNAS. AND SHORE3
MODES EVENTS3
MODES CONDITIONS3
**NBnotShrike**
*Snattack*
*SBOC* !OTS! NOT !OTS!
*SBOCFlytoO*
*SBOCoffset*
*SHU'Ddown2 _________________________
290
NRL REPORT 0194 HUD Functions
MODES EVENTS
*Nattack* @T(FLR sampled' AND NOT @T(FLR sampled AND
*Noffset* !Slant range reasonable!) !Slant range reasonable!)
*HUDdownlI*
*HUDdown2*
*SHyJDdown1*
*SHUD down 2 *
*Snattack*
Note: Even though FLR is sampled constantly in *CCTP* mode, the Solution Cue is never flashed
because it is used as an aiming indicator, so that the flashing would be confusing.
'@T(FLR sampled) occurs when @T(!Desig!) occurs, or when @TC'slewing finished!) WHEN(!Desig') occurs.
291
I
Chapter 4 ALSPAUGH, FAULK. BRITTON. PARKER. PARNAS, AND SHORE I
4.3.12. Vertical Velocity and Acceleration Indicators g
4.3.12.0. When the Velocity Indicators are Updated
Output data item(s) affected: / /HUDVEL/,
Output description:
Table 4.3.12-a shows when the program updates the values for the two vertical velocity indica-
tors and the Flight Path Marker position (see Section 4.3.5).
MODES
*Airaln* @T(!FM stage complete!)
EVENTS
@F(!AOA reasonable!) WHEN
3
OR (NOT !FM stage complete!)
@T(!AOA reasonable!)
*Mag Sl* @T (!AOA reasonable!) @F(!AOA reasonable! AND
*Grid*
*IMS fail*
*OLB* _
OR
@T(/ACAIRB, =$No$)
'ACAIRB '=$Yes$)
3
All other @T(None of above modes) x
modes __
ACTIONS Initiation Termination
I //HUDVEL., :=$On$ '/HUDXEL/:= $Off$3
Comment: Hardware constraints cause both the vertical derivative and the Flight Path Marker func-
tions to be initiated and terminated by the value of //HUDVEL//. See the description of
/ IIUDVEL// in Chapter 2.
I
2
I
U
I
I
.9. I
NRL REPORT 9194 HUD Functions
MODES CONDITIONS
NOT
*Grtest* Always X
*Grtest* X Always
OUTPUT !System vertical velocity! 0
1 in feet per second
293
U
Chapter 4 ALSPAUGH. FAULK. BRITTON, PARKER. PARNAS. AND SHORE 3
Condition Table 4.3.12-c: Vertical Derivative Value u
MODES CONDITIONS
All modes except Always X
those below _
*Snattack* *Snoffset* *SBOC*
*SBOCFlytoO* *SBOCoffset* NOT !low drag! !low drag!
*SHUJDdownl* *SHUDdown2*
OUTPUT id2/VERTNEL// value !normal acceleration!.
''1 ,VERTVEL// and /,VTVELAC / govern the position of a pointer on a scale (see Chapter 2).
When reading an acceleration, the pilot interprets the bottom of the scale as 0 g's and the top of the
scale as +8 g's. Thus, the actual value to be sent to the data item is -1000 + 250 x the acceleration
in g's.
I
U
I
U
I
U
I
U
I
I
294 1
MRL RPORT g1g4 Bomb Release Functions
**NBot~hrike*
*Walleye* @T(//FIRRDY//=$On$) @T(!fire pulse width
*Snattack* elapsed!)
*Snoffset*
*SHTJDdown2*___________
,Manrip* @T(//FIRRDY//=-$OnS) WHEN(NOT !Shrike!) @T(!fire pulse width
OR elapsed!)
@T(//FIRRDY//=SOn$ AND !time elapsed!
since //FIRRDY//=$OnS > 2.31 s)
_______________ HEN(!Shrike!)
ACTION //BMvffREL / /:=$On$ /BMBREL :, $Ofi3
29
Chapter 4 ALSPAUGH, FAULK, BRITTON. PARKER. PARNAS. AND SHORE3
@T(//BM1BREL //=$Ofl3)
*Manrip* @T(/RE/-SOnS) OR
@T(/RE/=$OfYS) WHENI
(//FIRRDY//=$On$ AND
______________
_______________________________ !Shrike!)
__________ @Tf/RE/=SOnS) @T(/ /BMBREL / /=$OflS)
296
NRL REPORT g1g4 Bomb Release Funetions
MODES EVENTS
*Nattack* @T(!ground range! from @T(//BMBREL//=SOff3)
!iffet
mpact point! of last release OR
*BOC* to impact point! of present @T(/RE/=$OflS)
*BOCFlytoO* = !bomb spacing!) WHEN W;HEN(!Shrike! AND
*BOCoffset* (!rls pts passed! //FIRRDY,//=$On$)
*CCIPAN!stik quantity!
*Mannip* AD/E=O$
29
Chapter 4 ALSPAUGH. FAULK, BRITTON. PARKER, PARNAS, AND SHORE3
MODES EVENTS
*Nattack*
*Noffset* @T(//FIRRDY,'//=4On$) WVHEN(//'BMBTON //=$On$)
*BOC* @T(/RE/=$On$) OR3
*BOCFlvtoO* WHEN (!Desig!) @T(/RE/=Of1$) WHEN(//BMBTON//=On$)
*BOCoffset*
*HUDdownl*I
*HUTDdown2*____________________________
*WaIleye* @T(/RE/=SOn$) @T(!time elapsed! since
@T(/BMTON //=$OnS)=l -z)
*Snattack* @T(!Rmax!) OR @T(!time elapsed! since @T(!Rmax!)=I s) OR1
*Snoffset* @T( !Rmin!) OR @T(!Rmin+6000!) WH7EN(//BNMTON//=$On$) OR
*SBOC* @T(/RE /=SOnS) @T(//BMBREL//=OnS) WHTEN(//BMBTON/,/-SOn$) OR
*SBOCFlytoO* WHEN (!Desig!) @T(!IS pitch!> 15 *AND /RE/=$Off%)I
*SBOCoffset* WHEN(!low drag!) OR
*SHlJDdownl* @T(/RE/ =$00l) WHTEN(//BMBTON//=$On$ AND
*SHTJDdown2* Nhigh drag!)
298
INRL REPORT 9194 Bomb Release Functions
times per second. The rate is given by the dictionary entry !beep rate!.
MODES EVENTS
*Snatak*
II *Snoffset*
*SBOC*
*SBOCFlytoO* @T(!R65!) @T(!elapsed time! since
*SBOCoffset* beeping :tarted > 2 seconds)
*SHUJDdownl*_______________________________
29
Ch pter 4 ALSPAUGH, FAULK. BRITTON, PARKER. PARNAS, AND SHORE 3
4.5. PROJECTED MAP DISPLAY SET FUNCTIONS
I
I
i
I
I
I
I
NRL REPORT 9194 PMDS Functions
MODES CONDITIONS
NOT /PMNORUP/ - $Yes$ /PMNORUP/ = $No$ /PMHOLD/ - $Yes$
*Grtest* AND AND
_______/PMHOLD/= $No$ !PMHOLD/= $NO$
//MAPOR// 0 !ground track angle! last value of
VALUE //MAPOR// before
_@T(/PMHOLD/ = $Yes$)
301
I
Chapter 4 ALSPAUGH. FAULK, BRiTTON. PARKER, PARNAS, AND SHORE 3
U
I
1
NRL REPORT 9194 PMDS Functons
MODES CONDITIONS
All Navigation /PMNORUP/ = $Yes$ /PMNORUP/ = $No$
and Alignment OR AND
*MaDUDd* /PMDCTR/ = $No$ /PMDCTR/ = $Yes$
DISPLAY
POSITION: center reference circle bottom center of display
Notes
(1) With current maps, this cannot happen since the A area is included in the B area. However,
this is not required by the NAVAIR filmstrip specification.
(2) With current maps, this cannot happen, since area B is only in scale $80$. However, this is not
required by the NAVAIR filmstrip specification.
303
U
Chapter 4 ALSPAUGH. FAULK. BRITTON. PARKER, PARNAS, AND SHORE 3
Panel Service Functions I
J'LLITDEC//
iiLWDIG2//
//LWDIG7//
*//LLITE//
//LWDIG3//
*//ULITN//
*!/LLITW//
/ILWDIG4//
*,!/ULITS//
*//LLIT322/,
//LWDIG5//
*//ULIT222//
//LWDIGI//
!LW)DIG6//
I/'/ULIT321//
I
TTWDIG I// i'/UWDIG2// '/LVDIG3/' //UWDIG4// , /UWDIG5//
,Nw% IG6//
, //KELIT//
304
NRL REPORT 9194 Panel Functions
The panel data that can be entered by the pilot also play the role of input data items. Both the
panel data name and the mnemonic names for the possible values can be !items! appearing in the dic-
tionary, if they are referred to in other parts of the document. For example, !Data 23! = !Sea! refers
to the condition that the most recent value entered for the Update Data 23 function was -000000,
which signifies that the A/C is based on a ship.
305
Chapter 4 ALSPAUGH, FAULK. BRITTON. PARKER, PARNAS. AND SHORE3
MODES EVENTS3
*HUDUpd*
*FlvUpd* @T(In mode) OR @T(!Dest called up!) @T(/'TD/=$On$)
*RadarUpd* @T(/ENTERSW,/-S$On$)
*Ta___________ _________
Table 4.6-c shows what is displayed in other modes when switches on the panel are changed
The /UPDATTW/, /MODEROT/, /PMHOLD/, and /PRESPOS/ switches may be set in any order,
but the keyed-in value must be entered after the other switches are set. It is not necessary to reset
the switches before another keyed-in value is entered if a different display is desired in the same mode.
In Table 4.6-c, the number in parentheses gives the subsection where the Panel Display Function
is described. Thus, Present Position (5) indicates that the Present Position Panel Display Function is
306
NRL REPORT 9194 Panel Functions
Table 4.6-c
Panel Display Functions in Non-Ul iate Modes
Special Cames:
In the special cases listed below, the Panel Display Functions are interrupted and the panel is
temporarily set to a fixed display.
(1) Most of the Panel Display Function are identified by the setting of the switches /UPDATT W/,
/PRESPOS/ and /MODEROT/. For some displays, a number must be keyed in by the pilot to
complete the identification. During the time between when the switches are set and the number
307
U
Chapter 4 ALSPAUGH. FAULK, BRITTON. PARKER. PARNAS. AND SHORE 3
is entered, the panel is blank.
(2) In *Grtest* mode, no Panel Display Functions control the panel. Instead, the panel displays the
data it was showing at mode entry. When !PD Tstage! is entered (indicating that all tests have
1
passed), all lights are turned on - the windows display $8S and !format lights on!. When the
mode is exited the Panel Display Function defined by the switch settings resumes.
(3) @T(//COMPFAIL//=SYesS), all panel lights are turned on.
(4) If the pilot makes an error during data entry, an error display (described in Section 4.6.2) is
shown momentarily before the Panel Display Function defined by the switch settings resumes.
(5) If an update mode is exited without the update being accepted (i.e., the exit is caused by I
changes in one of the following inputs: /UPDATTW/, /PRESPOS/, /MODEROT/,
/FLYTOTW/ or /FLYTOTOG/), the panel is blank momentarily before the panel display
function defined by the switch settings resumes.
(6) @T(/PN HOLD/=$Off$) the panel is blank momentarily before the Panel Display Function
defined by the switch settings resumes. 3
(7) During the stages of data entry, the panel display is described in Section 4.6.2.
(8) All 9's are displayed if any of the following conditions occurs during *TacUpd*: NOT !TAC.AN
valid! OR /RNGSTA/ < /BAROADC/ OR /ISMODE/ = $Grid$
(9) In an update mode, all 9's are displayed if the number keyed in for !Dest called up! is 0.
(H1)
Panel Display: !echo!
IF error in format or range, GO TO 1. See associated Panel Display Function for restrictions
I
on the values.
Panel Display: All 9's. south, west. and all format lights flashed. Then display of step I
(5)
(6)
resumed.
IF /KBDENBL/ = SOnS GOTO 1
ENTERSV/ = SOnS
3
IKELIT'/ := SOff$
I0
Chapter 4 ALSPAUGH. FAULK, BRITTON, PARKER, PARNAS, AND SHORE3
Ode
utp crip
t ion:Event Table 4.6-d: M ark W indow Display
310
I NRL REPORT 9194 Panel Functions
Event Table 4.6-e: When Panel ENTER light switched on and off
below
listed
data displayed!
AND
//ENTLIT// = $Mfl)
WHEN (//ENTLIT//=SOn$)
OR @T(!power up!)
*HUDUpd*
*RadarUpd* @T(/TD/ = $On$) @T(!Panel switch changed!
*TacUpd* WHEN OR !Keyboard input!
*FlyUpd* (//ENTLIT//=$Off$) OR !FLY-TO changed!)
IACTION *MavUvd*
_____________
________________
Switched on
//ENTLIT//:= $On$
WHEN (//ENTLIT//=On'
Switched off
//ENTLIT//:= $0fl
31
I
Chapter 4 ALSPAUGH. FAULK. BRITTON. PARKER. PARNAS. AND SHORE 3
I
4.6.5. Update Present Position Coordinates Display
(Periodic function) 5
UPPER WINDOW: Present position latitude
When value initialized: OFP loaded 3
Initial value: 0'
Units: degrees, minutes, seconds
Range: N 89 59' 59" to S89 59' 59"
Display resolution: I second
Characterization of value: latitude of A/C position 3
Display format: !lat!
BOTH WINDOWS:
When value changed: 3
3
I
I
I
I
I
312 3
INRL REPORT 9194 Panel Functions
MODES EVENTS
*Sautocal* @T(!pilot entry!) OR
*SINSaln* @T(!New SINS coordinates!)
*Lauoa*
31
Chapter 4 ALSPAUGH, FAULK, BRITTON. PARKER. PA4RNAS, AND SHORE
BOTH WINDOWS:
When value changed:I
Event Table 4.6.6-a: When Panel Wind Display Changed
MODES EVENTS
All alignment @T(!Displayable difference!) WHEN (!ADC Up!)
except_*Airaln*____________________________
*.kiraln* @T(!Displayable difference!) WVHEN (!ADC Up!)
*DIG*, *DI* OR
*UJD)*, *PolarDI* @T(!pilot entry!) WHEN (NOT !ADC Up!)
@T(!Displayable difference!) WHEN (!ADC Up!)I
*1*. *PolajrJ* OR
@T(!pilot entry!) WHEN (/ACAIRB /=$Yes$
_________________ AND NOT !ADC Up!)
@T(!Displayable difference!) WHENU
*Mag sl*. *Grid* (!Doppler Up! AND !ADC Up!)
OR
*OLB*, *JI45 fail* @T(!pilot entry!) WHEN (/AGAIRB/=$Yes$
_________________ AND (NOT !ADC Up! OR NOT !Doppler Up!))
3141
i NRL REPORT 9194 Panel Functions
I
!
I
I
I
315
I
Chapter 4 ALSPAUGH, FAULK. BRITTON, PARKER. PARNAS. AND SHORE 3
I
4.6.8. Update SINS Z Offset and Delta Heading
(Periodic function) 5
UPPER WINDOW: SINS Z offset
When value initialized: OFP loaded 3
Initial value: 0
Units: feet
Range: -2047 to +2047
Display resolution: 1 ft
Characterisation of value: Z offset is the A/C Z coordinate in the SINS coordinate system. I
See Addendum for discussion of the SINS coordinate system. The pilot enters the value, and it
is never calculated by the OFP.
Display format: 'signed integer!
When value changed: @T(!pilot entry!)
1
LOWER WINDOW: SINS delta heading
When value initialized: OFP loaded
3
Initial value: 0
Units: degrees, minutes
Range: 0 to 360
Display resolution: I minute I
Characterization of value: Angle between the Ys axis of the SINS coordinate system and the
Ya axis projected into the Xs-Ys plane. The angle is measured clockwise, looking down, from
the Ya axis. The pilot enters the value, and it is never calculated by the OFP.
Display format: !angle - Lwindow!
When value changed: @T(!pilot entry!) 1
I
U
I
I
U
316
NRL REPORT 9194 Panel Functions
317
I
Chapter 4 ALSPAUGH, FAULK. BRITTON, PARKER. PARNAS, AND SHORE 3
I
4.6.10. Update Platform Heading and Reference Heading Display
(Periodic function) 5
UPPER WINDOW: Platform heading
When value initialised: OFP loaded I
Initial value: 0
Units: degrees, minutes
Range: 0 to 360
Display resolution: 1 minute
Characterisation of value: !IMS heading! I
Display format: !angle - Uwindow!
When value changed: @T(!Displayable difference!)
I
I
I
I
318I
NRL REPORT 094 Panel Functions
BOTH WINDOWS:
Characterization of value: Coordinates of a location that the pilot wants eit:,er to fly
toward, to use as a navigation update reference point, to use as a target or to use as an offset
aimpoint to locate a target.
When value changed: @T(!pilot entry!) OR (@aT(!map destination entry!) OR @T(!data link
waypoint coordinates! received) (see also Addendum).
After the last step. the coordinates of the filmstrip location under the reference point becomes
the coordinates of the destination identified in step 4.
Note: Nine sets of coordinates can be stored as destinations at one time. The particular set to
be displayed or altered is identified by the single non-zero digit keyed in by the pilot (see Table
4.6-c).
319
I
Chapter 4 ALSPAUGH, FAULK. BRITTON, PARKER, PARNAS, AND SHORE 3
I
4.6.12. Update Destination Altitude and MSLP Display
(Periodic function) 3
UPPER WINDOW: Altitude
When value initialised: OFP loaded 3
Initial value: 0
Units: feet
Range: * 5535
Display resolution: 2 feet (!rounded down!)
Characterization of value: altitude of associated location above or below sea level; positive:
above sea level
3
Display format: !signed integer!
BOTH WINDOWS:
When value changed: @T(!pilot entry!)
Note: Nine sets of altitude-MSLP may be stored at one time. The particular set to be
displayed or altered is identified by the single non-zero digit keyed in by the pilot (see Table
3
4.6-c).
I
32
NRL REPORT 9194 Panel Functions
BOTH WINDOWS:
When value changed: @T(!pilot entry!)
Note: Nine offset range-bearing sets may be stored at one time. The particular set to be
displayed or altered is identified by the single non-zero digit keyed in by the pilot (see Table
4.6-c).
321
I
Chapter 4 ALSPAUGH. FAULK, BRrrTON, PARKER. PARNAS, AND SHORE 3
I
4.6.14. Update Offset Delta Height and Burst Height
(Periodic function) 3
UPPER WINDOW: Delta height
When value initialized: OFP loaded 3
Initial value: 0
Units: feet
Range: ±65535
Display resolution: 2 feet (!rounded down!)
Characterization of value: difference in altitude between Offset aimpoint (!OAP!) and !tar-
get!; positive value means !OAP! below !target!, negative value means !OAP! above !target!.
Display format: !signed integer!
When value changed: @T(!pilot entry!) 3
LOWER WINDOW: Burst height
When value initialized: OFP loaded
Initial value: 0
Units: feet
Range: 0 - 65535
Display resolution: 2 feet (!rounded down!)
Characterization of value: height above ground where bomb to burst for that destination 3
Display format: !unsigned integer!
When value changed: @T(!pilot entry!) 3
Note: Nine delta-height/burst-height sets may be stored at one time. The particular set to be
displayed or altered is identified by the single non-zero digit keyed in by the pilot (see Table
4.6-c).
3
I
I
I
U
I
322
NRL REPORT 9194 Panel Functions
BOTH WINDOWS:
Characterization of value: !Mark location! coordinates.
323
Chapter 4 ALSPAUGH. FAULK. ERrrTON, PARKER. PARNAS, AND SHORE3
BOTH WINDOWS: I
Characterization of value: coordinates of position under reference point of PMDS (see Sec-
tion 4.5.4)
When value changed: @T(/PMHOLD/ = SYes$) OR @T(!Displayable difference!) WHEN
(/PMHOLD/=SYes$)
Note: The differences will be caused by slew control inputs (/SLEWUD/ and /SLEWRL/ at I
.Map rate!. Because the values are only changed when (/PMHOLD/ VYes$), the A/C move-
ment does not change the values.
I
I
U
I
I
U
324 3
NRL REPORT 9194 Panel Functions
BOTH WINDOWS:
Characterization of value: The position error is the difference between the coordinates of the
two reference points given in Table 4.6.17-a. The position error is measured from the first refer-
ence point to the second. The direction of the error is shown by the format lights. For exam-
U
ple, //ULITN// = $On$ and //LLITE// = SOnS means the error is north east, that is, the
-cond point is northeast of the first.
I*MapUpd*
___/RNGSTA,
A/C present position !fixpoint!
and !BRGSTA
325
Chapter 4 ALSPAUGH, FAULK, BRITTON. PARKER. PARNAS. AND SHORE3
MODES EVENTS3
326
I
IIRL REPORT 9194 Panel Functions
I
4.6.18. Update DATA 00
(Periodic function)
UPPER WINDOW: 00
Display format: !label!
I
I
I
I
I
327
U
Chapter 4 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE 3
U
4.8.1g. Update DATA 01
(Periodic function) 3
UPPER WINDOW: 01
Display format: !label! 3
LOWER WINDOW: !north gyro drift!
When value initialized: OFP loaded
Initial value: 0
Units: deg/hour
Range: -1 to +I
Display resolution: 0.001
Characterization of value: Rate of drift of the gyro associated with the Y axis. Positive is
CW looking along the Y axis from the origin in the positive direction.
3
Display format: !signed fraction!
When value changed: I
Event Table 4.6.19-a: When Panel Data 01 Changed 3
MODES EVENTS
*Lautocal* @T(!ND stage complete!) OR
*Sautocal* @T(!pilot entry!)
@T(!TS stage complete!) WHEN
*OUpdate*
_______________________@T(!pilot
(!New 01 test passed!) OR
entry')
Other alignment
and
navigation modes
@T(!pilot entry!)
3
I
I
I
I
I
328I
NRL REPORT 9194 Panel Functions
UPPER WINOW: 02
Display format: !label!
I Units: deg/hour
to +1
Range: -1
Display resolution: .001
Characterization of value: Rate of drift of the gyro associated with the X axis. Positive is
OW looking along the X axis from the origin in the positive, lirection.
Display format: !signed fraction!
j When value changed:
IMODES *Lautoal*
EVENTS
@T(!ED stage complete!) OR
I *Sautocal*
Other navigation
or
@TPilot entry!)
@T(!pilot entry!)
alignment modes_______ _______
32
I
Chapter 4 ALSPAUGH, FAULK, BRITTON. PARKER, PARNAS. AND SHORE 3
I
4.6.21. Update DATA 03
(Periodic function) 3
UPPER WINDOW: 03
Display format: !label!
331
! I
I
4.6.23. Update DATA 07-09 (North, East, Vertical)
(Periodic function)
Data 07, 08: The increment in velocity represented by each /*VEL/ count when /IMSSCAL/
= $Coarse. * is Y for north (07) and X for east (08). 3
Data 09: The increment in velocity represented by each /ZVEL/ count.
These numbers are specific to an individual IMU and are never calculated by the OFP.
Display format: !unsigned fraction!
3
When value changed: @T(!pilot entry!)
Note: Although 0 is displayed as the initial value, the value loaded is a large number to prevent
the platform from operating almost normally before the maintenance personnel load the correct
parameters.I
3
I
I
I
I
I
332 3
NRL REPORT g1, Panel Functions
Note: Although 0 is displayed as the initial value, the value loaded is a large number to prevent
the platform from operating almost normally before the maintenance personnel load the correct
parameters.
333
Chapter 4 ALSPAUGH. FAULK. BRITTON, PARKER. PARNAS, AND SHORE
I
4.6.25. Update DATA 12-14 (north, east, vertical)
(Periodic function)
I
I
I
I
I
I
I
I
334 U
Nn REPORT 9194 Panel Functions
335
3
Chapter 4 ALSPAUGH, FAULK. BRTON. PARKER. PARNAS, AND SHORE
I
4.6.27. Update DATA 17-18 (area A, area B)
(Periodic function) 3
UPPER WINDOW: 17,18
Display format: !Iabel!
I
I
I
I
I
I
I
I
336
NRL REPORT 9194 Panel Functions
3
I
I
I
I
I
I
I
I
3.37
I
Chapter 4 ALSPAUGH, FAULK, BRITTON. PARKER, PARNAS, AND SHORE
I
4.6.29. Update DATA 21-22 (area A, area B)
(Periodic function)
I
U
I
I
I
U
I
I
I
338
I
NRL REPORT 9194 Panel Functions
i
4.6.30. Update DATA 23
(Periodic function)
UPPER WINDOW: 23
Display format: !label!
339
I
Chapter 4 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS. AND SHORE 3
i
4.6.31. Update DATA 24
(Periodic function)
UPPER WINDOW: 24
Display format: !label!
I
LOWER WINDOW: vertical ranging priority
When value initialised: @T(!power up!) WHEN (/IMSREDY/= $No$ AND /ACAIRB/ =
I
I
I
U
I
I
II
I
I
340I
NRL REPORT 9194 Panel Functions
UPPER WINDOW: 25
Display format: !label!
*entry! cities and to calculate platform corrections when /INIvSMODE/ = $InerS. A display or !pilot
of !positive! (!negative!) indicates that Doppler should (should not) be used.
When value changed: @T(!pilot entry!)
3
U
I
I
I
I
I
I
I
341
I
Chapter 4 ALSPAUGH. FAULK, BRrTTON. PARKER, PARNAS, AND SHORE3
UPPER WINDOW: 26
Display format: !label!I
342
I
NRL REPORT g194 Panel Functions
i
a 4.6.34. Update DATA 70
(Periodic function)
Characterization of value: Data 70 shows the state of the following input discretes. in the
pattern shown below the list. Given after each input data item is the value that causes the
corresponding panel window to show a 1$: the other value causes the window to show a SO$. A
'-'in a diagram means the window is always $Blank$.
I i'STAIRDY/ $Yes$
2 'STA2RDY/ SYes$
3 ,STA3RDY/ SYes$
4 /STA6RDY/ SYes$
5 /STA7RDY/ SYes$
6 !STA8RDY/ SYes$
7 'GUNSSEL/ SYes$
8 /RE/ SOnS
£ 9
10
/MULTRACK/
,TD/
SYes$
SOnS
1 78
1 2
9
3
10
4
-
5
-
6 UPPER WINDOW
LOWER WINDOW
3
I
I
343
I
I
Chapter 4 ALSPAUGH. FAULK, BRITTON, PARKER, PARNAS. AND SHORE 3
I
4.6.35. Update DATA 71
(Periodic function)
Characterisation of value: Data 71 shows the state of the following input discretes, in the
pattern shown below the list. Given after the input data item is the value that causes the
corresponding panel window to show a $I$; the other value causes the window to show a $0S. A
'-' in a diagram means the window is always $Blank$.
I
I
2
/BMBDRAG/
/NFfSW/
SHigh$
SNATTS OR SNATTOFFS
I
3
4
5
/MFSW/
/MFSW/
I'MFSW/
SNATTOFF$ OR $BOCOFF$
$BOC$ OR SBOCOFF$
$CCIP$
I
6
7
8
/MFSW /
/PMSCAL/
./PMHOLD./
$TF$
$80$
$Yes$
I
9 /PMDCTR/ $Yes$
10
11
12
/PMNORUP/
/PMSLAND/
/HUDREL/
SYes$
SYes$
$Yes$
I
1 2 3 4 5 6 UPPER WLNDOW I
7 8 9 10 11 12 - LOWER WINT DOW
I
I
I
3-44 1
NRL REPORT 9194 Panel Functions
Characterization of value: Data 72 shows the state of the following input discretes, in the
pattern shown below the list. Given after each input data item is the value that causes the
corresponding panel window to show $1$; other values cause the window to show a SMS. A in
a diagram means the window is always $Blank$.
I /IMSREL / $Yes$
2 ,'ACAIRB/ $Yes$
3 MvA/ $On$
4 /'MSMODE/ $Gndal$
5 'IMSMODE/ $Norm$
6 'IMSMODE/ $Iner$
7 /IMSMODE/ $Grid$
8 !IMSMODE/ $MagslS
9 /IMSREDY/ $No$
10 *'ISAUTOC/ SMnS
1I ADCFAIL / $Yes$
12 ARPPAIRS/ $Yes$
1 2 3 4 5 6 UPPER WINDOW
7 8 9 10 11 12 - LOWER WINDOW
345
Chapter 4 ALSPAUGH, FAULK. BRrrTON. PARKER. PARNAS. AND SHORE1
346
NRL REPORT 9194 Panel Functions
347
Chapta 4 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
MODES EVENTS
*Nattack* @T(In mode) OR @T(!Desig!) OR
*Snaf~tt* @F(!Desig!) @T(!slewing finished!) WHENI
*Snatack*(!rls pts passd! = 0) OR
*Snoffset* @T(!Slant range reasonable!)
*HUDdownl* WHEN (!Desig!
*SHUTDdown1* AND !rls pts passed! 0)I
SHUDdown2* _____________ ______________
The altitude shown in the lower window of Data 80 is either above ground level or above sea
level, as shown in Table 4.6.38-c. The table also shows the actual value used under different
348
NRL REPORT 9194 Panel Functions
conditions.
MODES CONDITIONS
*Nattack* !Slant range NOT !Slant range NOT !Slant range
*Noffset* reasonable! reasonable! AND reasonable! AND
*CI*!Data 24!=!Radalt! !Data 24!=!Baro!
*Snattack*
* Snoffset*
*HUTDdownl*
*SL1* T Ddownl* ___________
349
Chapter 4 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE5
*Nattack*j
*Noffset*
*BOC*
*BOCFlytoO* X @T(!rls pts passd!=1) X3
*BOCoffset*
*Snattack*
SBOCFlytoO*
*SBOCoffset*
*HUDdown1*U
*HUrDdown2*
*SHlJDdownl*
*SHUDdown2* ____________________ __________
350
INRL REPORT 9194 Panel Functions
Chaaterization of value: Above ground level altitude, from highest priority available sen-
sor:
IMODES*Nattak*
CONDITIONS
I*CCff)*
*Noffiet*
*Snattack*
!Slant range
reasonable!
(NOT !Slant range
reasonable!) AND
!Data 24!=!Radalt!
(NOT !Slant range
reasonable!) AXND
!Data 24!=!Baro!
*Snoffset*
*HUDdownI *
*SHUDdownl
_ _ __ __ __ _ _
* BOC *
I *BOCFlyto3*
*BOCoffset*
*Manrip* x !Data 24!=!Radalt! !Data 24!=!Baro!
*SBOC*
*SBOCFlytoJ*
*SBOCoffset*
*HUDdown2*
3 SHU~~~down2*
ALTITUDE
_________
!Altitude from
___________
down2*)
35
I
Chapter 4 ALSPAUGH, FAULK. BRITTON, PARKER, PARNAS, AND SHORE
I
4.6.40. Update DATA 82
(Periodic function) j
UPPER WINDOW: !azimuth miss distance!
When value initialized: OFP loaded I
Initial value: 0
Units: feet
Range: 0 to 65535
Display resolution: I foot
Display format. !unsigned integer!
Value description and when value changed:
MODES
*Nattack*
EVENTS 1
*Noffset* x @T(!rls pts passed! =1)
*BOC*
*BOCFlytoO*
*BOCoffset*
*HUDdownl*
*HUDdown2*
3
*Snattack*
*Snoffset*
*SBOC*
*SBOCFIytoO*
*SBOCoffset*
*SHUDdownl*
*SHUDdown 2 *
*CCIP* *Manrip* qT(In mode) X
VALUE 0 !azimuth miss distance!
352 1
.NRL REPORT 9194 Panel Functions
j *BOC*
*BOCFlyto)*
@T(!rls pts passed! =1
SBOCoffset*
*CoIP*
*Manrip*
3 *HUDdown2*
*Snattack*
*Snoff*set*
* SBO C
*SBOCFlyt,4J*
*SBOCoflset*
*SHWJDdownI*
*SHUDdown2*
35
Chapter 4 ALSPAUGH, FAULK, BRfTTON, PARKER, PARNAS, AND SHORE3
BOTH WINqDOWS:
When value changed:
*Nattack*, *Nofiset*
BOC, BOCFlytoO* @T(!rls pts passed! =1
*BOCoffset*
*CCIP*, *Manrip*
*Sflattack*, *Snoffset*I
*SBOC*, *SBOCFlytoo*
*SBOCoffset*
*HUDdownI*, *HLDdown2*,
*SHU~downi* . SHU~down2*
3541
I
I NRL REPORT 9194 Panel Functions
I
4.6.42. Update DATA 84
I (Periodic function)
35
I
I
I
Chapter 4 ALSPAUGH. FAULK, BRTTON. PARKER,. PARNAS. AND SHORE
I
4.6.43. Update DATA 85
(Periodic function) I
UPPER WINDOW: Blank
I
I
I
I
I
I
I
I
I
I
I
356I
I NRL REPORT 9194 Panel Functions
I
I(Periodic
4.6.44. Update DATA 88
function)
Initial value: 0
Units: hours, minutes, seconds
Range: 0 to 6 hr 45 min
Display resolution: I second
1Characterization of value: !time elapsed!
Display format: !angle - Lwindow!
When value changed: @T(!Displayable difference!)
I
357
Chapter 4 ALSPAUGH, FAULK BRITTON, PARKER, PARNAS. AND SHORE
358
NRL REPORT 9194 Panel Functions
BOTH WINDOWS:
Characterization of value: ship's coordinates received over SINS data link
When value changed: *Sautocal*, *SINSaln*: @T(!New SINS coordinates!)
359
I
Chapter 4 ALSPAUGH. FAULK. BRITTON. PARKER. PARNAS. AND SHORE 3
I
4.6.47. Update DATA 91
(Periodic function) 5
UPPER WINDOW: IMS heading
Units: degrees, minutes
Range: 0 to 360 degrees
3
Display resolution: 1 minute
Characterization of value:
Condition Table 4.6.47-a: Data 91 Upper Window Display
MODES CONDITIONS I
All modes !IMS U! NOT !MMvS Up!
HEADING !IMS heading! !magnetic heading! +
VALUE IS magnetic variation!
3
I
I
I
360
NRL REPORT 9194 Panel Functions
Initial value: 0
Units: knots
MODES EVENTS
*SINSan* @T(!New stage!) @T(!Displayable difference!)
*Sautocal*
All other
navigation X @T(!Displayable difference!)
or alignment
modes
DATA 92 VALUE !SINS NVeI! !IMS NVeI!
DATA 93 VALUE !SINS EVeI! !IMS EVeI!
361
I
Chapter 4 ALSPAUGH, FAULK. BRITTON, PARKER. PARNAS. AND SHORE
I
4.6.4g. Update DATA 94
(Periodic function) 5
BOTH WINDOWS: SINS status
When value initialized: OFP loaded
Initial value: all zeros
3
Units: discrete I
Characterization of value: During *Sautocal* and *SLNSaIn*. Data 94 shows the validity of
the various data received over the SINS data link. The classified addendum explains how the
validity of each datum is determined. The display is arranged in the pattern shown below; a
$1 in the window indicates the datum is invalid while a $0$ indicates that it is valid. A '-' indi-
cates that the window is always blank.
I !SINS heading!
2 !SINS NVel!
3 !SINS roll!
4 !SINS EVeI!
5 !SINS pitch!
6 !SINS latitude!
7 !SINS longitude!
2 - 3 - UPPER WINDOW
4- 5 - 6 - 7 LOWER WINDOW
During all other modes, the non-blank windows above are all set to $1$. 3
Display format: !no lights!
'When value changed: *Sautocal*. *SINSaln*: @T(one of the conditions changes) OR @F(In
mode) I
I
I
I
I
362
NRL REPORT 9194 Panel Function
MODES EVENTS
All Davigation or
alignment modes @T(!Displayable difference!) X
except *EMS fail*
*RM4 fail* X @T(In mode)
GROUNDSPEED magnitude of vector sum of
VALUE !IMS NVel! and !IMS EVel! 0
_______________________ (see §4.6.48)
363
I
Chapter 4 ALSPAUGH. FAULK. BRITTON, PARKER, PARNAS. AND SHORE 3
I
4.6.51. Undate DATA 96
(Periodic function) 5
UPPER WINDOW: IMS drift angle
Value description and when value changed: 3
Event Table 4.6.51-a: Data 96 Upper Window Values
MODES EVENTS
All navigation or @T(!Displayable difference!) X
alignment modes
except [MS fail*
X (ThT(In mode)
3
*IMS fail*
DRIFT ANGLE VALUE !IMS drift angle! 0
3
I
364
3NRL REPORT 9194 Panel Functions
3 Unite: knots
Range: 0 to 1214
Display resolution: I knot
Display format: !unsigned intege0'
All navigation or
alignment modes @T(!Displayable difference!) X
exce-pt *lMS fail*_____________________ __ _______
3 VALUE
~
!D&S NVel!, !MS EVel!, !IMS Vvel!
~~~~(see
§4.6.48)_________
0
365
I
Chapter 4 ALSPAUGH, FAULK. BRITTON. PARKER. PARNAS. AND SHORE
I
4.6.53. Update DATA 98
(Periodic function) 3
Both windows and Mark window: Navigation status
Characterization of value: Data 98 shows the operating status of the 3 main sensors used for
navigation: the ADC, the 1IS and the Doppler. It shows whether the following conditions are
true or false. The pattern below shows how the conditions are indicated in the windows. If a
condition is true, the corresponding window is $15, otherwise it is $05. The windows shown with
''arealways $Blank$.
1 /ACAIRB/--$No$
2 *Magsl* OR *Grid* OR *LISfail* OR (*Airaln* AND !FM stage!)
3 /IMSREDY/=$No$
4 /IMSREDY/=$No$ OR /IMSREL/=SNo$
5 NOT !IMlS Reasonable!
6 /DRSREL/=$No$
7 NOT !Doppler Reasonable!
8 NOT !ADC Reasonable!
- - 3 - UPPER WINDOW
7 LOWER WINDOW
8 MARK WINDOW
Note: The value of the mark window is given here for completeness. though Section 4.6.3 I
completely defines the value shown in the mark window.
3
I
I
I
I
366
I
NRL REPORT 914 Panel Functions
I
4.6.54. Update DATA 99
(Periodic function)
I
U
I
I
I
I
I
I
I
U
I
I
367
I
Chapter 4 ALSPAUGH, FAULK, BRITTON, PARKER. PARNAS. AND SHORE
MODES CONDITIONS
All alignment
and nay modes,
none of the /FLYTOTW/=O /FLYTOTW/00) X X
modes below;
*WValleye*
*A/G Guns* _______ ______
368
NRL REPORT 9194 HSI Functions
3No MODES
NOT *Grtest*
reference
point defined
CONDITIONS
X Reference point
defined
36
I
Chapter 4 ALSPAUGH. FAULK, BRITTON. PARKER. PARNAS. AND SHORE
I
4.7.2. Update HSI Ground Track
(Periodic function) 3
Initiation and termination:
Event Table 4.7-d: When HSI Ground Track Updated
MODES
*SINSaln* @T(In mode)
EVENTS
@F(!CA stage!) OR
@F(In mode)
3
*Grtest*
@T(/ACAIRB/ = $Yes$)
@T(In mode) OR
@F!AC2 Tstawe!)
@T(/ACAIRB/=SNo$)
3
ACTION Initiation Termination: needle set to 0
3
I
i
I
I
I
U
370I
I
NRL REPORT 9194 HSI Functions
I
4.7.3. Update Range Indicator (Map and HSI)
(Periodic function)
MODES CONDITIONS
All modes except !Range! > !Range! < X
when overridden 1000 nmi 1000 nmi
by modes below
i*NBShrike**
**NBnotShrike**
*Snattack*
*Snoffset* NOT !Desig! OR !Desig! AND
*SBOC* X ('Desig! AND !Range! < 10 nmi
*SBOCFlyto0* !Range! > 10 nmi)
*SBOCoffset*
*SHUDdownl *
*SHUDdown2*
*Grtest* X Always X
RANGE UNITS: nmi nmi 1000 ft
ACTION: //LFTDIG/./:fi$One$ 1/!LFTDIG / /:=$Blank$ //LFTDIG / / :=$One$
II
I
U
371
Chapter 4 ALSPAUGH, FAULK, BRITTON. PARKER. PARNAS. AND SHORE
MODES CONDITIONS
All modes
except *Grtest* X X Always
*Grtest* !AC1 Tstage! !AC2 Tstage! x
VALUE 555 553 !limited range!
Note: The range indicator value must be set to 555 actually in !DC Tstage! to allow the servos
to settle in time for 'AC1 Tstage!. 3
I
I
I
I
I
I
I
I
I1
II
I
372
NRL REPORT 9194 ADI Functons
I MODES
*Airaln*
____
/ACAIRB/-=SNoS
___CONDITIONS
/AOAIRB/=SYes$
_____
X X
IAny *Waleye*
Nay mode;
None of modes
OR
/FLYTOTW/ = 0
AND
/FLYTOTW/0O
below: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ ______
3SL~dwi *Snattack*
SB0C*
__________
X x Always x
*SBOC* ________ ____
373
I
Chapter 4 ALSPAUGH. FAULK. BRITTON. PARKER. PARNAS. AND SHORE
Periodic and demand functions are separated because the relevant timing information is
Maximum
Minimum Useful or
Current Allowable Allowable
Function Name Rate Rate Rate
3 IMS:
Torque platform X axis 20 ms 40 ins current
Torque platform Y axis 20 ms 40 ms current
Torque platform Z axis 20 ms 40 ms current
Flash INA light not significant
FLR:
Update azimuth-cursor position' 80 ms current 40 ms
Update range-cursor position 80 ms current 40 ms
Update antenna azimuth 40 ms current current
Update antenna elevation 40 ms current current
Output ground track velocity 200 ms current current
Update flight path angle 200 ms current current
i HUD:
Update AS coordinates' 40 ins 40 ms 40 ins
Update ASL coordinates 67 ms 80 ms 40 ms
Update ASL angle 67 ms 80 ms 40 ms
Update barometric altitude 40 ias 80 ins current
Update flight director coordinates 67 ms 80 ms 40 ins
Update FPM coordinates 67 ins 80 ms 40 ms
Update HUD magnetic heading 200 ms current 40 ms
Update HUD pitch angle 40 ms current current
Update PUAC coordinates 200 ms current 40 ins
Flash PUAC 40 ms
Update HUD roll angle 40 ms 80 ins current
Update lower solution cue coordinates 200 ms current 40 ms
Update upper solution cue coordinates 200 ins currert 40 ms
Flash solution cues 200 Ins
I
I 375
1
Chapter 5 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
Maximum
Minimum Useful or
Current Allowable Allowable
Function Name Rate Rate Rate
Update HUD vertical velociry 40 ms current current
Update HUD vertical derivative 40 ms current current
Map:
Output azimuth ring ai.gle 200 ms current 40 ms
Output destination pointer angle 200 ms clrrent 40 ms
Output orientation angle 200 ms current 40 ms
Update filmstrip position' 200 ms current 40 ms
Panel:
Panel display functions 1000 ins 1000 ms 100 ins
HSI:
Update bearing indicator 200 ms current current
Update ground track angle 200 nis current current
Update range indicator 200 ms current current
ADI-
Update azimuth steering needle 67 s 80 ms current
position
I
5.2. TIMING REQUIREMENTS FOR DEMAND FUNCTIONS
For all the demand functions, the rate of demand is so low that it will not constitute a
significant CPU-load.
3
For the starred entrie the desired maximum delay is not known; thb entry is the maximum
delay in the c, rrent OFP, which we will use as an approximation. In oue case, both the current and
desired values are given. The current value would be good enough to satisfy requirements, but the
"sired rate would oe pre'-"-red.
'When these display items are skwed, the rnly timing requirement is that their movement appear to a human to be con-
tinuous.
3
3
376
I
I
I NRL REPORT 9194
HUD:
Switch AS on/off *200 ms
Switch ASL on/off 200 ms
Flash FPM 40 ms
Switch pullup cue on/off 40 ms
Switch both solution cues on/off *40 ms
Switch velocity indicators on/off *1000 ms
ASCU:
Switch bomb release on/off 2 ms
Switch fire ready on/off 2 ms
Switch bomb tone on/off concurrent with
release enable
Panel:
Change window display 300 ms (desired);
1000 ms (current)
Accept pilot data entry 40 ms
Change panel MARK display 200 ms
Switch panel ENTER light on/off 40 ms
I
I
I
I
I
I
U
I
I
377
I
I
I
CHAPTER 6
[
The purpose of Chapter 6 is to state the acceptable errors or tolerances for each of the functions
described in Chapter 4. Accuracy requirements vary with A/C situation, weapon type, mode of
operation and other factors.
Our original intention was to have Chapter 6 contain tables defining the tolerances in a way
analogous to the tables defining the output values in Chapter 4. Unfortunately, the data necessary to
complete such tables are not available to us. In a development of a totally new weapon system, the
mission analysis necessary to determine these requirements would have been justified. Knowledge of
the tolerances would be necessary to make rational choices of computation methods, data representa-
tion and resource allocation. In the present system. we have available a model with acceptable perfor-
mance, and we know that the methods and representations used in that model are adequate to the
task. For that reason, we have omitted Chapter 6 from this document and take as our requirement
that we must meet or exceed the accuracy of the present system.
[
I
I
I
I
I
I
I
I
378
I
I
CHAPTER 7
7.0. INTRODUCTION
I This chapter describes system responses to undesired events, such as hardware malfunctioning.
It includes both responses made by the current OFP and hypothetical responses considered reasonable
by system engineers. If our only purpose were to duplicate the current OFP, this chapter would be
redundant, since the current responses are described in Chapter 4. However, we are also concerned
with making the system easy to change. One very common change to a system is an improved
response to an undesired event. To anticipate these changes, we have sketched the kinds of responses
that might be considered useful.
For each response, we have indicated in the two columns to the right a) whether it is performed
in the current OFP, and b) the system engineers' judgment of its usefulness. Responses are classified
"'Y1' (Yes), "'N"' (no) and "'M'. (maybe). We included some responses judged not useful in order to
I Current Desired
self checks
UFA detected by periodic
379
I
Chapter 7 ALSPAUGH, FAULK, BRITTON, PARKER. PARNAS. AND SHORE
Current Desired
3) Use other sources of velocity and altitude. Y Y
4) Do not do baroaltitude damping of vertical velocity. Y Y
5) Allow pilot to enter winds in keyboard. Y Y
1) Inform pilot.
2) Revert to barometric altimeter ranging.
N
Y
M
Y U
f. Memory checksum incorrect
1) Stop - Force failsafe and switch computer Y M
fail light on.
2) Run in a "restricted state." Navigate, no
computed weapon release, warn pilot.
If function performed by faulty memory
area can be identified, leave out that function.
N M
I
g. SINS data bad I
1) Inform pilot by wiggling HSI #2 needle. Y Y
380
I
I NRL REPORT 9194
Current Desired
(Training and human factors problems.)
3 1) Rejection acknowledged.
2) Pilot may start over.
Y
Y
Y
Y
3 c.
IMS producing bad data
1 1)
Pilot turns it
Off. Y Y
I
381
I
I
Chapter 7 ALSPAUGH, FAULK. BRITTON. PARKER, PARNAS, AND SHORE
Current Desired
1) Pilot turns it off. Y Y
2) Revert to baroaltimeter ranging. Y Y
382
I
I
I NRL REPORT 9194
Current Desired
1 1) Save data.
2) Pilot informed by 8's in window.
N
Y
Y
Y
3 None.
1) Y M
b. Power interruption
I
I
I
I
I
I
I
I
383
I
I
I
CHAPTER 8
Required Subsets
U
8.0. INTRODUCTION
Chapter 4 characterizes the functions of the A-7 OFP. The primary requirement is that the
OFP be able to perform all of these functions. In addition, we require that the program be structured
to facilitate the development of a set of function subsets that will:
(a) perform only a subset of the services performed by the whole OFP;
(b) be obtained by the removal of clearly identified sections of code and data structures without
modification* of the remaining programs.
(c) use an amount of memory space and execution time roughly comparable to that which would
have been used if the program had been originally developed to perform only that subset of the
functions.
Note that these requirements cannot be satisfied by simply "turning off" the unneeded functions.
The space and time consumed by the implementation of those functions would not be made available
for other purposes.
These requirements can be reformulated by saying that when the subset systems are needed,
they should use time and space in proportion to the complexity of the services, and the bigger subsets
3
and the OFP itself should be obtained by adding code to the smaller subsets without modifying the
code of the smaller subsets.
A subset is required for each HUD symbol. for IMS-slew for each axis, for IMS-torque for each axis, for I
FLR antenna control, for FLR cursor display, for bomb release and fire ready, for PM])S display posi-
tioning, for panel display, for HSI bearing to destination, ground track, range to destination, for bomb 3
It may be neesary to reassemble, using new assembly-time constants.
I
384
I
I
NRL REPORT 9194
I 385
I
Chapter 8 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
possible to provide navigation information to the pilot through either the HUD, the HSI, the PMDS,
or the panel even if the software used to display information on the other three devices is not avail-
able. Similarly, there shall be subsets available to perform navigation services using only a subset of
the normal input devices wherever alternate means of obtaining the necessary input are available.
386
I
I
NRL REPORT 9194
5 Only the following !Weapon Class! members shall be included: SGN$, $HDS, SMDS, SSLS. $SHS, $SMS,
SUNS. All others shall be returned as SUNS.
8.2.1.2. Modes
Only the following modes shall be included. Actions which would cause an entry into one of the
deleted modes shall cause no transition:
Alignment: *Landaln*
Navigation: *1*, *DIG*
Nay Update: *HUDUpd*, *UNone*
Weapon: *Nattack*, *Noffset*, *Manrip*, **NBnotShrike**, *\VNone*
5 Test: none
8.2.1.3. Functions
The following functions are not included:
A function to drive a deleted output item:
Update SINS X and Y Offsets Display;
Update SINS Z Offset and Delta Heading Display;
Update Map Coordinates Display;
Update DATA 03 through Update DATA 22:
Update DATA 26; !Land! shall always be true;
Update DATA 71 (lower window);
Update DATA 90;
Update DATA 91 (lower window);
Update DATA 92/93 (lower window);
Update DATA 94.
I
I
I
I
I
I
I
387
I
I
I
CHAPTER 9
I
Expected Types of Changes
I
9.0. INTRODUCTION
This chapter characterizes the requirement changes that can be expected in the future. It is
impossible to give specific details of any particular change, but we wish to point out the aspects of this
document that cannot be considered fundamental when designing the system. However. there are a
few fundamental assumptions about the system that are not expected to change whatever enhance-
ments are made. These are listed in Section 9.1.
I
388
I
NRL REPORT 9194
9.3.2. FLR
(a) Display symbology may be changed.
(b) Range characteristics could be improved.
3 9.3.3. HUD
(a) Data Item Identity codes could be changed.
(b) Symbols could be added.
(c) Computer controlled intensity or color could be added with a new HUD.
9.3.5. ASCU
(a) ASCU might be replaced by computer controllable unit.
9.3.6. PMDS
3 (a)
(b)
Map might be replaced by a unit that can be positioned more quickly (unlikely).
Other film-strip formats and scaling might be used.
9.4.1. General
(a) Improved processing algorithms might be added (e.g., Kalman filters).
3
389
I
i
Chapter 9 ALSPAUGH, FAULK, BRITTON. PARKER, PARNAS, AND SHORE 3
(b) Performance rates and time limits are considered subject to change.
(c)
(d)
New display information might be added (includes all pilot displays).
More accuracy might be required.
5
(e) Comparison of redundant inputs (e.g., barometric vs. FLR slant range) may be added to detect
major errors. I
(f) New sensors (e.g., Forward Looking Infra-Red (FLIR)) may be added.
9.4.2. HUD
(a)
(b)
Additional information might be provided by flashing, intensity (unlikely), color (unlikely), or
new symbols.
Meaning associated with symbols could be changed (Flight Path Marker, PUC are not allowed
U
to change).
9.4.3. Panel
(a)
(b)
Data entered by pilot could be displayed after ENTER pushed, so that he can verify (likely).
Display before entering could be omitted.
£
9.4.4.
(a)
New Weapons Functions
Some weapons might require computer control after release (not likely).
I
(b) Some new weapons might require programming just before release (already planned). i
(c) Some weapons might transmit data to computer after release.
(d) Some weapons might be tracked by A/C sensors after release and their positions displayed to
pilot (not likely).
390
I
NRL REPORT 9194
I
[
I
I
I
I
391
[
I
I
CHAPTER 10!
These acronyms and terms are used in the A-7 community to describe various aspects of the I
Navigation Weapon Delivery System (NWDS), that is, the complete system including the computer.
software and all the hardware displays and sensors used for navigation and weapon delivery.
-A-
a/c Aircraft I
A/C Aircraft 3
ACL Automatic carrier landing
ADL Aircraft datum line; the longitudinal center reference line of the a/c
weapons system (3 degrees down from water line 100)
392
3
I
NRL REPORT 9194
alignment Causing the IMS platform axes to point toward the Earth's local east, the
projection in the local horizontal plane of the north vector, and the perpen-
dicular to the local horizontal plane away from the Earth's center.
angle of attack Angle of wing (or other reference horizontal) to air flow
ANT Antenna
AUTO Automatic
AZ See azimuth
3 azimuth Horizontal direction; for example, angle between a/c heading and the line
projected into the horizontal plane from the a/c to a destination
3 azimuth steering error Angular difference between actual ground track and desired ground track
azimuth steering line Straight-line HUD symbol; also called bomb fall line (BFL)
* -B-
Backup reticle Also called standby reticle - symbol displayed by the HUD when the HUD
not reliable
I 393
I
U
Chapter 10 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE 5
BCN Beacon integration - radar mode
Bearing Angle between projection of Y axis onto the horizontal plane and projec- I
tion onto the horizontal plane of the line from the A/C to a destination or
target 3
BDU Bomb dummy unit
-C-
CADU Control and display unit: used to debug programs on the TC-2 1
CAL Calibration
CDCE Computer-driven cursor enable; when the OFP enables the cursors on the
I radarscope
CEP Circular error probable - radius of circle in which 5075 of bombs fall; meas-
ured in feet
CG Center of gravity
5 CHAN Channel
CIR Circular
crab Difference between ground track angle and the heading as measured by
I IMS; see also drift angle
I CW Clockwise
3
DA See drift angle
DC Direct current
3 delta heading Angular difference between a/c heading and ship heading
DEOB Deck edge outlet box - used to connect A/C to source of SINS data: each
DEOB is marked with its offsets from the SINS source on the ship
designate A pilot action that ground stablizes the HUD aiming symbol or radar cur-
sors on the selected aiming point and records the aiming point location in
the Tactical Computer. Used in update modes and weapons delivery
modes
destination A location whose coordinates are entered in the Tactical Computer by the
pilot
U 395
I
Chapter 10 ALSPAUGH. FAULK. BRITTON. PARKER. PARNAS, AND SHORE
DF Direction-finding
DLV Delivery I
DME Distance measuring equipment
DOP Doppler
drift angle Angle between the projections into the horizontal plane of the Y. axis and
the A/C velocity vector. The angle is usually measured from the Y. axis.
3
dpositive
direction in the CW direction, looking down, and negative in the CCW
DU Display unit I
E East
ELEC Electric i
Enter Inserting information (pilot selected or update) into the TC-2 via the Enter
pushbutton
ET Elapsed time
-F- 3
396
I
NRL REPORT 9194
flight path angle Angle between aircraft velocity vector and its projection into the horizontal
plane: pitch corrected for angle of attack. The angle is usually measured
from the horizontal line, positive in the up direction, negative in the down
direction
flight path marker HUD symbol showing direction of A/C velocity vector
FREQ Frequency
3 FWD Forward
-G-
I GND Ground
grazing angle Angle between the line defined by the direction that the FLR antenna
points and its projection into the horizontal plane
3
397
I
Chapter 10 ALSPAUGH, FAULK. BRrrTON, PARKER, PARNAS, AND SHORE 3
Grid Grid mode - an IMS mode; also an OFP navigatior mode
ground track Line defined by projection of the A/C velocity vector onto the ground 3
ground track angle Angle between ground track and the line from the A/C to true north (true
heading + drift angle). The angle is usually measured CW from north look-
ing down
GS Ground speed
-H-
heading Line defined by the projection of the Y. axis into the horizontal plane; or
the angle between this line and the line from the A/C to north. See also
true heading and magnetic heading
Hg Mercury
HW Head wind
IAS Indicated air speed: not corrected for temperature and air pressure 1
impact angles Angles measured from the a/c Y, axis to the line from the A/C to the
impact point projected into the X.-Y3 plane (azimuth) or into the Ya-Z a
~plane (elevation)
3 impact point Point where bomb would hit the ground if released now
I N PANEL Tactical Computer Control Panel (TCCP). Also called NWDS Panel
IP Identification point (also initial point; also impact point). See offset aim-
U point
IR Infrared
3 -K-
K YBD Keyboard
I KIAS Knots indicated airspeed; not corrected for temperature and air pressure
-Kt Knots
KTAS Knots true airspeed: corrected for temperature and air pressure
3 LAT Latitude
LB Pounds
LD Low drag
399
i
Chapter 10 ALSPAUGH, FAULK, BRITTON. PARKER. PARNAS, AND SHORE
LDG Landing
LIN Linear i
LONG Longitude
Magnetic heading Angle between the projection of the Y axis into the horizontal plane and i
the line from the a/c to magnetic north. The angle is usually measured
CW from north looking down 5
MAG SL Magnetic slave - IMS mode; also OFP Navigation mode
Mil Milliradian
MIN Minimum 5
400
NRL REPORT g194
MN Mach number
ms Milliseconds
MSL ALT Height of A/C above sea level: AGL + target altitude
MV Magnetic variation
-N-
N North
NAV Navigation
nm Nautical miles
NORM Normal - [MS mode; also used as another name for DIG
401
I
Chapter 10 ALSPAUGH, FAULK. BRITTON. PARKER, PARNAS, AND SHORE
offset aimpoint Landmark used to identify a target in an offset weapon delivery mode
ORA Optical Reference Axis: see introduction to the HUD data items (see Sec- I
tion 2.1.4)
-P-I
PGS Pilot's grip stick
POS Position 3
POT Potentiometer
PPI Plan position indicator; another name for the radarscope cursors U
PRC Program reloadable counter
PRES Present
PWR Power
QTY Quantity
-R-
RAD Radar
Radar range cursor An internal electronic radar signal recurringly generated at some specific
time after each radar pulse transmission, appearing on the scope as a solid
arc representing a specific range
Radar range sweep The motion of the electron beam in a cathode ray tube that permits target
3 blips and range cursors to be distributed across the face of the tube in pro-
portion to their slant ranges
Range Distance
RCVR Receiver
I RDR Radar
reflective target An area that presents prominent returns for radarscope interpretation
REL Release
RF Radio frequency
RH Right hand
403
I
Chapter 10 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
RKTS Rockets
SIMtJLT Simultaneous 3
SING Single
SL Sea level I
slant range Line-of-sight distance from the aircraft to the target 3
slew control Pilot joystick, used to control up-down and right-left movement of a
display symbol. Also called Bullpup control
solution cue HUD symbol providing pilot with release anticipation and appearing on I
screen when a/c within range of a target. WVeapons delivery can oc..ur
when either cue crosses the flight path marker. 3
404
U
NRL REPORT 9194
3 solution cue, lower Solution cue used for level, dive and dive-toss deliveries
3 STA Station
3 STBY Standby
steering command A fly-to indication to center the vertical and horizontal command pointers
3 or the flight director symbol on the HUD to achieve proper pitch and
azimuth flight corrections
5 STI. lengtn Distance between first and last weapon release in a stik delivery.
3 TAC Tactical
4
405
U
3
Chapter 10 ALSPAUGH, FAULK, BRITTON. PARKER, PARNAS, AND SHORE n
TGT Target I
TM Telemetry 3
TOF Time of fall
true heading Angle between the projection of the Y. axis into the horizontal plane and
the line from the a/c to true north. The angle is usually measured CW
from north looking down
undesignate Pilot action in weapons delivery modes. The HUD aiming symbol or radar
cursors are released from ground stablization I
uphill bombing Lofting a bomb up to a burst height set above a/c AGL altitude 3
UTM Universal transverse Mercator
VAR Variation 3
vdc Volts direct current
I
406
I
I
NRL REPORT 9194
VEL Velocity
VERT Vertical
NV West
3 WD Weapon delivery
WPN Weapon
I WPNS Weapons
VT Weight
* Y.
I-z.
Z - DHDG See Z offset and delta heading
3 -Other-
A Delta
4
I
I
I
407
I
I
I
CHAPTER 11
I
11.1. DOCUMENTATION
This section contains an annotated list of documents germane to the A-7 Operational Flight
Program (OFP). The r4erences are listed in order of accession. Each document is assigned to one of
3
the subject categories given in Table 11-a. The subject abbreviation comes below the reference
number in the document description. Table 11-a also gives the reference numbers of the documents
that belong to each category.
(1) NWDS: Conf document System Specification for A-7E Navigation/Weapon Delivery System
(NWDS), AS-4195, I Feb. 1975
3
408
I
NRL REPORT 9194
Functional requirements of the entire NWDS system (not just the software requirements).
Requirements for each of the following components: Digital Computer and panel, ASCU, HUD,
PMDS, Doppler, ADI, IMS, HSI. ADC, and FLR
Description of NWC-1 modes and functions, including the following information for each of the
attack modes: how initiated, aiming, designation, delivery, backup operation, and pictures of
HUD symbology
Over 100 pages of tables and figures, including the following: Equipment used in different modes.
signals between components broken down by navigation and attack modes, pictures and expla-
nations of cockpit controls (over 90 pages)
A very brief performance requirements section.
1 (2) HARD: Conf document Procurement Specification for Navigation/Weapon Delivery Digital
Computer System for A-7D/E Airplane, 204-16-29g, Nov. 1968
Primarily covers the computer and panel. Many hardware details. Function description mostly
superseded by Refs. 1 and 4 Computer interface descriptions superseded by Ref. 3 except the
following charts:
3 (3) NWDS: Conf document A-7 Navigation and Weapon Delivery System and Subsystem Charac-
teristics:Accuracies and Tolerances, VSD #2-54150/5R-5790, 8 May 1975
Computer-device tables, with the following information: signal names, types, ranges, accuracies,
scales, modes, etc. for each of the following devices: Doppler, FLR, HSI, ADI, HUD, ADC.
PMDS, AOA, IMS.
(4) NWDS: Conf document A-7 Navigation and Weapon Delivery System. VSD #2-14000/5R-5 I
May 1975
Narrative presentation of system specified in Ref. 1. Table summarizing tactical computer
characteristics. Table showing memory space allocation of OFP to 5 major modules. Radar
mode descriptions with pictures of associated displays. HUD displays with explanatory captions
for navigation and weapon delivery.
(5) NWDS: Performance Specifications for the Weapon Delivery Function of the OFP (U), IBM #
68-L68-012, 3 Dec. 1968
I 409
N
Chapter 11 ALSPAUGH, FAULK, BRITTON. PARKER, PARNAS, AND SHORE
(6) MATH: A-7D/E Aircraft Navigation Functions (U), by L. Crews and Carl Hall, NWC, TN
404-176, Mar. 1975
I
Derivation and explanation of navigation equations, including justification for selected methods.
Each section includes (a) a brief description of the calculation, relating it to the whole navigation
process and (b) a list of input and output quantities.
(7) MATH: A-7E Aircraft Weapon Delivery Equations (U), by R. George, NWC TM 2926, Sept. 3
1976
Similar to Ref. 6 for weapon delivery functions. 3
(8) OFP-1: WS8506 Documentation for OFP NWC-1 (U), by SCI (5 volumes and reference guide),
NWC TN 404-223, Dec. 1975
These volumes contain a great deal of information, but the organization and size make it
I
difficult to find answers to specific questions. Since they cover NWC-1, some of the software
function is out-of-date.
(9) OFP-2: OFP NWC-2 Glossary of Terms for A-7E Navigation and Weapon Delivery OFP (U),
for Tape 7, revision B, I Feb. 1977
Alphabetical list of program variables and constants, each described by some of the following:
value type (logical, single precision, double precision)
3
explanation of use
range, units, meaning of value
value (constant) or initial value (variable)
U
timing (how often updated/referenced)
scaling
(10) OFP-2: A-7E OFP Math Flow Description - NWC-2 (U), for Tape 7, revision C. 1977
Prose to accompany flowcharts (Refs. 12 and 13) Algorithms described in terms of program vari-
ables, constants and labels. Sections: Navigation, Weapons delivery, Interrupt processor and
control, NAV/WD Panel Processor, Self Test
(11) OFP-2: Conf document A-7E Math Flow Description - NWC-2 Special Weapons. SIIKE and
WALLEYE (C), for tape 7, revision C, 1977
Similar to Ref. 10 3
410
I3
I
NRL REPORT gg4
5 (12a) OFP-2: OFP NWC-2 Math Flow (U), for Tape 7, revision C, 1977
Low-level flowcharts, with a close correspondence to the code.
(12b) OFP-2: System Flow for the TA-7C Navigation and Weapon Delivery OFP (U), Mar. 1977
fHigher level flowcharts, expressing in English the information that Ref. 12a expresses in pro-
gram terms.
Warning: these flowcharts were written for the two-seater (TA-7C) version of the OFP, so that
there are some differences (e.g., the one-seater does not include the digital scan converter func-
tions.) See Ref. 12c. for a list of differences.
(13) OFP-2: Conf document OFP NWC-2 Math Flow - Special Weapons, SHRIKE and WALLEYE
(U), for Tape 7, revision C, 1977
Low-level flowcharts, with a close correspondence to the code.
(14a) PILOT: NATOPS Flight Manual A-7C, A-7E Aircraft (U), NAVAIR 01-45AAAE-1. 15 March
1975; change 4, 1 Sept. 1976
Pilot's manual containing information about all aspects of the aircraft, except details of weapons
delivery, which are contained in Ref. 15. Warning: this source describes NWC-1. See Ref. 14b.
for an update. Important sections:
pp. 1-158 thru 1-222 Avionics Subsystems pictures and descriptions of
principle components and their operating modes
pp. 1-236 thru 1-237 Avionics System Integration table showing
functions of components
pp. 1-251 thru 1-253 TACAN system
8-1 thru 8-22 Navigation/Weapon Delivery System (NWC-1 OFP)
User's manual for navigation, alignment, position updating.
8-23 thru 8-58 component descriptions and pictures for weapons
delivery subsystem
(14b) PILOT: NATOPS Flight Manual Interim Change No. 65 (U) NAVAIR 01-45AAAE-1, 1 May
3 1977
Update to Ref. 14a, Section 8, reflecting NWC-2 navigation and diagnostic aid changes.
5 (15a) PILOT: Conf document A-7C, A-7E Tactical Manual (C), NAVAIR 01-45AAE-1T, Oct. 1974
Pilot's manual, containing weapons' delivery details. Warning: NWC-1.
(15b) PILOT: Sec document Secret supplement to Tactical Manual (S), NAVAIR 01-45AAE-ITA
5 Specific information about special weapons.
(15c) PILOT: Conf document NWC-2 OFP Characteristics: Temporary Addendum No. TBD to
Ref. 15a (C), (preliminary)
Update to Tactical Manual reflecting N WC-2 weapons delivery changes. Moding, control,
display changes and diagnostic aids for weapons delivery monitoring. Ballistics calculation
I
3 411
I
Chapter 11 ALSPAUGH. FAULK. BRITTON, PARKER. PARNAS, AND SHORE 3
changes for special weapons.
(16) OFP-2: OFP NWC-2 ProgramListing and Cross References (U), NWC-2 Tape 7 Revision C, 3
Oct. 1977
Secret parts encoded. 3
(17) PILOT: OFP A7 NWC-2 Viewgraph Presentation(U), 22 April 1977
Presentation prepared for pilots, showing the differences between NWC-1 and NWC-2, particu-
larly weapon's delivery: moding, display, diagnostics
(18) TC-2: Introduction to TC- Assembly Language Programming for A-7D/E Programmers(U),
SCI, by G. Abels, Feb. 1976
3
Compilation of Refs. 19, 20. and Assembler Language manuals, written by a tech writer. (NOT
RELIABLE). Confuses TC-2 and TC-2A in places.
(19) TC-2: A.7D/E Programmers Guide to Input/Output for the TC-2 (U), IBM #6870158-3, 25
May 1970
For each input and output channel, it gives: information items, associated devices, data format.
Explanation of cycle-stealing I/O and the BITE instruction. Some corrections have been made
in our copy based on Lee Thomson's marginal notes. I
(20) TC-2: A-7 D/E Programmer'sReference Manual (U), IBM #67-506-001, 14 Sept. 1967
Data and instruction formats, registers, interrupt processing, addressing. For each instruction:
opcode and mnemonic, operands, timing, formats, affected indicators
(21) SIM: A-7C/E Simulation Computer Program Documentation (U), Parts 1-6, NWC TM 3105,
Feb. 1977
Documentation for the V & V simulation laboratory (Sigma 5, VG, etc.). Pts. I and 2 provide
an indirect description of the OFP, since they contain models of most of the interfaces - they
show what assumptions had to be made about the OFP and other components to simulate the
I
Avionics system.
(22) SIM: A-7E Simulator Software Capabilities(U), NWVC TN 404-186, May 1974 1
Simulator description superseded by Ref. 21. Brief description of other software support on the
SIGMA 5 and PDP 11, including the assembler and Tape merge, punch and verify program 3
(23) VAL: A-7 Simulation Facility - Cursory Validation Plan for OFP NWC-2 (U), NWC TM 3159,
Jan. 1977
Description of the short, 40-hour version of formal validation. Mostly derived from Ref. 24.
(24) VAL: .4-7 OFP Validation Plan and Proceduresfor Simulation Facilities (U), OFP NWC-2. I
Parts 1 and 2, NWC TM 3204, Mar. 1977
Part I gives background and justification for the test approach. Part I appendix: user's manual
for entering and displaying data on the NWDC panel, including units, accuracy and meaning of I
various panel quantities. Part 2 shows how the OFP should behave in a large number of test
cases.
I
412
I
NRL REPORT 9194
(25) MATH: A.7D/E Mathematical Subroutine Description(U), IBM #6870156-3, 25 May 1970
For each of the 16 subroutines:
flowchart
interfaces (in parameters, calling routines, called routines, etc.)
data organization
limitations (e.g. register contents destroyed, max size of input)
storage required
execution time
The descriptions should be checked against the code, but they should still be substantially
correct.
1 (26) PILOT: A Pilot's Guide to the Use and Understanding of the A-7E Avionics System (U), VA-
122, 29 Jan. 1973 Update
This manual should not be trusted for facts - it covers an earlier version of the OFP, and it was
never formally released. However, it does provide background information and explanation
which may aid understanding.
I (27a) OFP-I: Technical Description of NWC First A7E OperationalFlight Program (OFP) (U) by R.
R. Bruckman, NWC Reg Memo 40408, 31 Aug. 1973, Rev. A
Describes changes to be made to an earlier version of the OFP. Mostly focuses on weapons
delivery changes.
(27b) OFP-2: Technical Description of NWC-2 Operation Flight Program (U), Preliminary, rev. F, 21
Apr. 1976
Describes changes between NWC-l and NWC-2. Mostly focuses on weapons delivery changes.
I (28) OFP-2: Advanced Organizational Maintenance Data to be incorporated into NAVAIR 01-
45AAE-2-17.2 (U). 15 Aug. 1977
Update to maintenance manual, reflecting NWC-2 changes. More complete description of diag-
nostic panel displays than Ref. 29. Discussions of alignment, updating, and weapons delivery.
3 weapons delivery and maintenance diagnostics. Page 8 summarizes the pilot procedures for
navigation updates. Page 9 explains when the INA should be steady or flashing.
(31) SIM: Weapons Station Simulator (U), by Jack Williams, NWC 2706, Sept. 1976
3 Physical characteristics, components and operation of the Weapons Station Simulator laboratory
(downstairs in hangar 3). Includes wiring diagrams and detailed signal descriptions.
(32) SIM: Weapons Management Simulation and Control (U), by Jack Williams, NWC 3029, Dec.
3 1976
I 413
I
Chapter 11 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS. AND SHORE
Description of the weapons simulation laboratory focusing on the weapons delivery controls and
components (ASCU, ARP, etc.). Wiring diagrams, decoder logic, and signal descriptions. Some
prose which explains the use of the controls.
(33a-h)
HARD: Procurement Specifications for NWDS components.
a. Inertial Measurement Set AN/ASN-90(V) (U)
b. Navigation Set, RadarAN/APN-190(V (U) (Doppler) Includes:
One paragraph description of operation
Operational limits
Electrical outputs: range, probable error form
Data transmission and word format
Resolution and timing
c. Air Data Computer (U)
d. Transducer,Angle of Attack (U)
e. Forward Looking Radar System (AN/APQ-126) (U)
f. ProjectedMap Display Set (U)
g. Head Up Display (U) Includes:
3.3.29 Discussion of symbology functions
Paragraphs per symbol, showing meaning, scale, limits, etc.
(34) HARD: A/7D/E Head Up Display (U), by W. N. Carroll, IBM 68-L88-099, 8 Apr. 1968 I
(35) HARD: General Description of the Head Up Display (An/A VQ-7) for the A-7D/E Airplane (U),
by I. S. Glickstein, IBM 69-M93-001, 14 Feb. 1969
(36) HARD: General Description of the Projected Afap Display Set for the A-7E Airplane (U), by
Ira S. Glickstein, IBM 69-M93-003, 10 June 1969
(37) HARD: Addendum No. 6, Projected-Map Display Set Functional and Performance Require-
mento for A-7E Airplane Navigation/Weapon Delivery System (NWDS) (U), IBM 209-18-67b, 9
July 1968
b. Head-Up Display Set AN/AVQ-7 (V): NAVAIR 05-35FAB-I, 15 Apr. 1972, Change 7 - 15 Oct.
1977
c. Projected Map Display Set AN/ASN-99 (V): NAVAIR 05-35FAC-1, 15 Aug. 1971, Change 4 -
15 Jan. 1977
I (39) SINS: Conf document Shipboard Data Link System Requirements for Aircraft Inertial Naviga-
tion System Alignment and Waypoint Insertion Naval Air Systems Command, AR-57A, 3 May
1971
(49) MATH: A Ballistic Trajectory Algorithm for Digital Airborne Fire Control (U) by Duke,
Brown, Burke, and Seeley, NWC TP 5416, 17 Aug. 1972
(41) MATH: Coordinate Systems Analyst Manual (BLSIM5) (U) by Kobaly (Systems Consultants,
Inc.), Renta and Breisch (NWC A-7D Project Office), July 1979.
I
I
I
I
I
I
I
415
I
I
Chapter 11 ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
I
I
I
I
I
I
I
I
I
I
I
I
416
I
I
!A/C facing target! True if the angle between the line from the A/C to the target and
the A/C Y axis (both projected into horizontal plane) is less than
90*.
I/RNGUNIT//:=
J/BRGDEST!/:= 225 (see also Section 4.7.1),
3 (see also Section 4.7.3),
and the values set in LAC Test 1 failed! do not change.
Failure criteria: (a) a hardware error occurred during the instruc-
tion sequence for any of the outputs (refer to Section 2.0.6); (b)
any interrupt occurs before CONVERSION COMPLETE besides
I
I 417
I
Dictionary ALSPAUGH, FAULK. BRITTON, PARKER, PARNAS, AND SHORE 3
IN PANEL; (c) a hardware error occurred during the instruction
sequence for /ACTESTCOS/ and /ACTESTSIN/ (refer to AC
Self-Test, Section 2.1.8.6); (d) 1AC test angle! < 49.14 or >
52.0 *.
Clean-up: None
!Altitude from slant range! Above ground altitude can be calculated from /SLTRNG/ and the
depression angle from horizontal to the point on the ground that
the FLR is aimed at since they provide the length of a side and an
I
I
NRL REPORT 9194 Dictionary
!Amax! Maximum release angle for low drag special weapons (weapon
dependent. associated with ASCU code)
!Amin! Minimum release angle for low drag special weapons (weapon
dependent, associated with ASCU code)
!Any destination entered! Pilot enters the coordinates for any one of the 9 destinations
through the panel. See Section 4.6.2 for panel entry rules.
!ASAZ!
!ASEL! Values for Aiming Symbol coordinates, before limiting. See Sec-
tion 4.3.1.
!ASLAZ!
!A3LEL! Values for Azimuth Steering Line Center Point coordinates before
limiting. See Section 4.3.2.
5 !axis aligned! True when the alignment error value given in the table below is
no longer exceeded for a particular axis in the specified stage:
X-axis Y-axis Z-axis
!CA stage!
!CL stage! , , n/a
!FG stage! , *
!azimuth miss distance! The perpendicular distance between the !target! and the ima-
I ginary line drawn from the a/c through the !impact point!.
!azimuth reference heading! The heading entered by the pilot of a known reference point. See
Section 4.6.10 for more information.
!Baro! One of the values of !Data 24!, indicating the pilot has chosen the
baroaltimeter o the ADC as the priority backup ranging sensor.
Panel value - .- Section 4.6.31.
!BAROADC!
adjusted /BAROADC/ IF !Data 26! = !L-probe! THEN /BAROADC' z 1 - /MACH!'
X (.02032 - 7.5148 X 10-7 ft X /BAROADC/)] + [!system vertical
I 419
I
Dictiony ALSPAUGH, FAULK, BRITTON. PARKER, PARNAS, AND SHORE 3
velocity! X .4375 s] - 1056 ft
ELSE /BAROADC/ + 560 ft x (/MACH/ - 0.2)
This definition is device-dependent and likely to change if the
current ADC is replaced.
!Before slewing! The stage in a weapons delivery or update mode after mode entry
but before !During slewing!. In modes *Landaln*, *01Update*,
U
*1*, *OLB*, and *PolarI*, becomes true when the event
@T(!aiming switches set!) occurs and false when !During slewing!. I
!blank! Panel format - See Table 4.6-a
!blast pullup point! The point where the A/C must immediately begin a 4 G pullup to I
keep out of the blast radius of an exploding weapon. This pullup
includes 1.3 seconds aircraft/pilot reaction time before the 4 G
portion of the maneuver. The blast radius is assumed to be 1500
ft around the blast point of the weapon.
!bomb fall line! Imaginary line on the ground along which a ballistic weapon
would travel if released now. I
!bomb-spacing! The distance between !impact points! for the bombs in a stik:
IF !Shrike! THEN 1 nmi;
IF .Mines! then
U
MAX(Minimum-release-distance-for-mines,
MRI-for-mines, /ARPINT/ X 10);
IF NOT !Shrike! AND NOT Mines! THEN
MAX(Minimum release distance-for-weapon-type,
/ARPINT/).
Minimum release distances are figured from Minimum Release
5
Intervals (MRI), given in Section 2.4. During a multiple release a
change in /ARPINT/ is not accepted when /RE/=$On$.
!Checksum test failed! The OFP periodically performs a check on the portions of memory
I that store program and fixed data by computing a checksum. The
!CL stage complete! Initially false. Because false on entry to *Lautocal*, *Sautocal*,
*Landaln*, *SINSaln*, *HUDaln*, *UJDI*, *OLB*, *Mag sl*,
*Grid, *IMS fail*, *Grtest*. Becomes true when (lX-axis
corrected! AND IY-axis corrected!).
!coarse scale factor! A value of Data 07, Data 08, or Data 09. See Section 4.6.23.
!Coord entered! Coordinates have been entered for the called up destination. See
also !Dest called up!.
5 !data link waypoint coordinates! Coordinates have been received from the Waypoint System.
!Data 01! !north gyro drift!. Panel value - See Section 4.6.19.
!Data 23! Whether a/c is land or carrier based. Panel value - See Section
4.6.30.
!Data 24! Priority sensor for vertical ranging. Panel value - See Section
4.6.31.
!Daa 25! Whether Doppler coupled. Panel value - See Section 4.6.32.
!Data 26! Which equations to use to calculate true airspeed. Panel value -
See Section 4.6.33.
!Data 98 displayed! Update Data 98 is the Panel Display Function currently control-
ling the panel output data items.
3 !DC Test failed! Setup.
!/STERROR//:= !Test Value 3!
(see also Section 4.8.1),
//FPANGL//:= !Test Value 2! (see also Section 4.2.7),
//GNDTRVEL//:= !Test Value 1! (see also Section 4.2.6).
Test Steps: None
Failure criteria: (a) any hardware error occurred during the
instruction sequence for any of the outputs (refer to Section 2.0.6);
(b) a hardware error occurred during the instruction sequence for
'DCTEST/ (Refer to DC Self-Test, Section 2.1.8.7): (c)
,DCTEST/ < -1.24 or > -1.16.
Clean-up: None
I 421
I
I
Dictionary ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE 1
!Delta heading! Angle entered by pilot indicating difference between A/C heading
and ship heading. Panel value - See Section 4.6.8.
!Delta height! Difference in altitude between the OAP and the target. Panel
value - See Section 4.6.14. 1
!Desig!
!Designation-retention!
The pilot has identified a target to the computer. Initial value:
false. Table D-d shows when !Desig! changes value.
!Dest called up! During update modes, the pilot keys in the single non-zero digit I
that identiies the destination to be used as the update reference
point. !Dest called up! becomes true when @T(!Non-zero digit
entered!) occurs while in an update mode. It becomes false upon
exit from the current update mode.
!DEST displayed! Update Destination Coordinates Display (see Section 4.6.11) is the
Panel Display Function currently controlling the panel output data
items.
I
!Dest 0! /FLYTOTOG/ = $Dest$ AND /FLYTOTW/= 0
!Dest 1-9! /FLYTOTOG/ff= gDest$ AND /FLYTOTW/# 0
Clean-up:
//DOW1//:= 00001, I
//DOW2//:= 000016,
i/BITEI//:= $None$,
422
I iNRL REPORT 9194 Dictionary
I //BITE2//:- SNone.
!Displayable difference! Some of the Update Panel Functions are concerned with values
that change continuously, such as the A/C position when it is air-
borne. The functions update the values to be displayed on the
panel at discrete intervals. !Displayable difference! occurs when
the difference between the most recent update value and the
current value is greater than the resolution for that function.
!distance to release! With !high drag! weapons, the !ground range! the A/C must travel
to reach the point where it should release the first weapon in the
stik. Measured in feet.
!dive pullup! If the A/C is close enough to the target, there exist two pitch
angles (one greater than the pitch for maximum range, one less
than this pitch) from which the aircraft, at present position and
airspeed, would release a !low drag! weapon, and the weapon
would reach burst height at the target. If the aircraft is close
enough for these two angles to be calculated, !dive pullup! is the
lower of the two pitch angles minus the !system pitch!. Otherwise,
!dive pullup! is 42' minus !system pitch!.
!Doppler coupled! One of the values of !Data 25!, used by the pilot to select or
deselect the use of the Doppler radar when in an inertial naviga-
tion mode. This value indicates Doppler should be used. Panel
value - See Section 4.6.32.
'drift angle! IF !Doppler Up! THEN /DRFTANGi ELSE !IMS drift angle!
U 423
I
Dictionary ALSPAUGH, FAULK, BRITTON, PARKER. PARNAS, AND SHORE 3
NOT /SLEWRL/ - 0). Since the slew control is not perfect, see
Section 2.2.2 for reliable indications of displacement.
!echo! The characters typed in by the pilot are echoed in the panel win-
dow. Exactly what is displayed depends on the format of the
display that he is entering. For example, when a display of format
!lat! is displayed, the first /KBDINT/ must be either $S or $N$,
U
or else an error has been made. If the first input is correct, either
/ /ULITN//=--$On$ or //ULITS//:--$On$. Subsequent
/KBDINT/ values are shown in panel windows.
!fine scale factor! A value of Data 10 or Data 11. See Section 4.6.24. 3
!fire pulse width! Length of time that //BMBREL//=$On$ should be true to cause
the ASCU to release a particular weapon. The fire pulse widths
vary from weapon to weapon and are given in Table 2.4-a.
U
!fixpoint! In Update modes after @T(!Dest called up!) occurs, the reference
point is one of the nine destinations, until the pilot slews the aim-
ing symbol or radar cursors to show his idea of the reference point
I
location. After he slews, the aiming symbol or cursors track the
point the pilot left them over when he finished slewing. This
refined point is the fixpoint.
!FLY-TO MSLP! See Section 4.3.3 The MSLP associated with the location indi-
cated by /FLYTOTOG/ and /FLYTOTW/.
I
!Fly-to point! Destination or Mark indicated by settings of /FLYTOTOG/ and m
/FLYTOTW/.
---- !FM stage complete! Initially false. Becomes false on entry to *Airaln*, *HUDaln*,
*1UDI*, *OLB*, *Mag sl*, *Grid*, *IMS fail*, *Grtest*. Becomes
true when the difference between 2 averages of 3 readings each is
less than 10 deg per minute.
!format lights on! The following data items are set to SOnS: //ULITN//,
S//ULITS//, //ULIT222//, //ULIT321//, //ENTLIT//,
//KELIT//, //LLITE//, //LLITW//, //LLIT322//, //LLIT-
-- DEC//.
!FPMAZ!
!FPMEL! Values for Flight Path Marker coordinates before limiting. See
Section 4.3.5.
!GAS! Go-around steering. See Table D-e to see when Go-around steer-
ing is in progress. The purpose of GAS is to show the pilot cues
for the quickest return to a target that he has overflown by more
I, than 13000 ft.
!Grazing angle! The elevation angle that the FLR antenna is pointed down from
local horizontal. This angle is positive when the antenna is aimed
below horizontal.
!ground pullup point! The point where the A/C must execute a 4 g pullup to avoid hit-
ting the ground, assuming a safety margin of ... This pullup
includes 1.3 seconds of aircraft/pilot reaction time before the 4 g
portion of the maneuver.
!ground tests finished! Initialized to false. Becomes true after 4 seconds elapsed in !PD
Tstage! of *Grtest* mode. Becomes false when *Grtest* exited.
!ground track! Line defined by projection of A/C velocity vector into horizontal
plane.
!ground track angle! Angle (clockwise from North looking down) between !ground
track! and the line from the A/C to true north.
425
I
Dictionary ALSPAUGH, FAULK, BRITTON, PARKER. PARNAS, AND SHORE 1
Clean-up: //BITE2//:= SNoneS.
!HS stage complete! Initially false. Becomes false on entry to *SINSaln*, *HUDaln*,
*UDI*, *OLB*, *Mag sl*, *Grid*, *IMS fail*, *Grtest*. Becomes
true when !Z-axis corrected!. I
!HUD rate! Azimuth displacement, in degrees per second:
(25/256) X /SLEWRL/ X (/SLEWRL/ 2 -.1482 + 9) I
elevation displacement, in degrees per second:
(25/256) X /SLEWUD/ x (/SLEW0UD/ 2 -. 1482 + 9)
!impact angle azimuth! The angle between the A/C Ya axis and the line projected into
the Xa-Ya plane from the a/c nose to the !impact point!. Looking
in the -Za direction, it is positive clockwise from Ya.
!impact angle elevation! The angle between the A/C Ya axis and the line projected into
the Ya-Za plane from the A/C nose to the !impact point!. Mea-
sured from the Ya axis in the positive Za direction (up).
I
!impact point! The point on the ground that would be hit by a weapon released
now or a gun fired now, in any weapon delivery mode. At
different times, different compensations are made in impact point
caicul.ions. (a) *A/G Guns* with !Guns!: wind, parallax, gravity
drop, and AOA. (b) *A/G Guns* with !Rockets!: wind and grav-
ity. (c) *A/A Guns*: A/C acceleration and platform angles.
I
'IMS-ADCReasonable! ABS(!IMS total velocity! - /TAS/) :_ 191 kt OR !ADC down!. 5
IMS-Dop Reasonable! ABS(!IMS groundspeed! - !DGNDSP!) < 62 kt OR !Doppler
down!. I
!MS drift angle! Drift angle calculated by subtracting !IMS heading! from the
ground track angle derived from !IMS NVe!! and !IMS EVeI!.
!IMS EVeI! Velocity calculated from /XVEL/ history - speed of A/C in the
east direction (assuming platform aligned). It is set to 0 when
@T(in mode) for *IMS fail* and when @F(in mode) for
426 g
NRL REPORT 9194 Dictionary
!IMS ground speed! Magnitude of the horizontal component of the velocity vector, cal-
culated from !IMS NVeI! and !IMS EVel! - length of vector g in
figure D-a.
!IMS magnetic variation! Magnetic variation received through the IMS true heading inputs,
/THDGCOS/ and /THDGSIN/ (angular range: 0 to 360),
when !IMS down! See Section 2.1.1.8.
!IMS NVeI! Velocity calculated from /YVEL/ history - speed of the A/C in
the north direction (assuming platform aligned). It is set to 0
when @T(in mode) for *IMS fail* and when @F(in mode) for
*SINSaln*, *Sautocal*, *Landaln*, and *Lautocal*.
!IMS pitch! Angle determined by /PCHCOS/ and /PCHSIN/ (angular range:
±180"). (see !system pitch!)
!IMS total velocity! 3-dimensional vector sum of !IMS NVel!, !IMS EVel! and !IMS
Wei!
!IMS VVe! Velocity calculated from /ZVEL/ history - speed of the A/C mov-
ing towards or away from the ground (assuming IMS aligned).
!IN A!
!IN B! See Section 4.5.3.
!In-time test failed! The OFP is required to reset the TC-2 GO/NO GO counter every
1.3 seconds. This test is failed if the OFP fails to do this.
!inc vel scale! X and Y axes: IF //IMSSCAL// = $Coarse$ THEN !coarse scale
factor! ELSE !fine scale factor!
Z axis: !coarse scale factor!
!Interface test failed! !Timer Test failed! OR !Gyro Accel Test failed! OR !Discrete
I/O Test failed! OR !DC Test failed! OR !Serial Channel Test
failed! OR 'AC Test I failed! OR !AC Test 2 failed!
427
I
Dictionary ALSPAUGH, FAULK. BRITTON. PARKER, PARNAS, AND SHORE I
!Land! One of the values of !Data 23!, indicating A/C based on land.
Panel value - See Section 4.6.30. I
!Land velocity test passed! Initial value: false. Becomes false on entry into one of the follow-
ing modes: *Lautocal*, *Sautocal*, *Landaln*, SINSan*,
*HUDaln*. *UDI*, *OLB*, *Mag sl*, *Grid*, *IMS fail*,
I
*Grtest*. Becomes true when land test passed, i.e. when !IMS
NVel! and !IMS EVel! both less than 1/8 fps at the end of the TS
alignment stage.
!Mach Unreasonable! fMACH/ more than .0195 different from last value read
!mag var entered! Magnetic variation has been entered for the destination to be used
for reference data during a TACAN update. Panel value -
Section 4.6.9.
See
3
!magnetic heading! Angle determined by /MAGHCOS/
range: 0 to 360').
and /MAGHSIN/ (angular
3
428 g
NRL REPORT 9194 Dictionary
!Mark! /FLYTOTOG/-4MarkS
.rMARK displayed! Update Mark Coordinates Display (see Section 4.6.15) is the Panel
Display Function currently controlling the panel output data
items.
!Mark location! The coordinates of a location that the aircraft has flown over, and
that the pilot has chosen to be stored for later recall. Nine sets of
coordinates can be stored as mark locations at one time. A new
set is stored whenever @T(/MARKSW/ = $On$ occurs. Each set
is identified by the !Mark number! assigned to it when it is stored.
The set of coordinates to be displayed as the !Mark location! is
determined by the single non-zero digit keyed in by the pilot (see
Table 4.6-c).
!Mark number! Number associated with each set of Mark coordinates as they are
stored. The number is initialized to 0 when the OFP is loaded
and incremented by I whenever @T(/MARKSW/--$On$) occurs.
The successor of 9 is 1.
!maximum range! If the aircraft continues with its present pitch and velocity for 1.3
seconds, then goes through a 4 g pullup trajectory (measured in
the plane of a/c velocity and Zp) until the plane has a pitch of 42
degrees, then release a !low drag! weapon, the bomb will be at a
Iwhen !ground range! from the aircraft equal to the !maximum range!
it falls to its burst height.
!Nav velocity test failed! Difference between !IMS NVei! and !Doppler NVeI! > 10 fps OR
difference between !IMS EVel! and !Doppler EVe!! > 10 fps in
*DI*, *DIG*, or *PolarDI* modes.
I 429
1
Dictionary ALSPAUGH, FAULK. BRITTON, PARKER. PARNAS, AND SHORE 3
!ND stage complete! Initially false. Becomes false on entry to *Lautocal*, *Sautocal*,
*HUJDaln*, *UDI*, *OLB*, *Mag sl*, *Grid*, *MS fail*,
*Crtest*. Becomes true when !Data 01! has been calculated and
(X-axis corrected!
corrected!).
AND .Y-axis corrected! AND !Z-axis
3
!negative! Panel value:
Upper window: - 0 0 0 0 0
Lower window: - 0 0 0 0 0 0
!New SINS coordinates! SINS coordinates received, valid, and more than 1 second different
from previous SINS coordinates. n
!New SINS heading! SINS heading received, valid, and more than 1 minute different
from previous SINS heading. 3
!New SINS velocities! SINS velocities received, valid, and more than I knot different
from previous SINS velocities. n
!New 01 test passed! Difference between old !Data 01! value and new !Data 01! value <
0.049. See Section 4.6.19. I
!No intervening takeoff! @T(/ACAIRB/--$YesS) has not occurred since latest exit from
*Landaln* mode. I
!no lights! Panel format - See Table 4.6-a.
Non L-probe! One of the values of !Data 26!, indicating that L-probe equations I
should not be used for true airspeed calculations. Panel value -
See Section 4.6.33. 3
'Non-zero digit entered! Any single /KBDINT/ value is entered, except SO$.
!normal acceleration! Acceleration along the Za axis. Positive in the positive Za direc- '3
tion.
!NS! One of two values of Data 19 and Data 20. indicating that the
associated map area is oriented North-South. See Section 4.6.28.
5
!OAP! Offset aimpoint - used in *BOCoffset*, *Noffset*, *HUJDdown2*.
*SBOCofEset*, *Snoffset*, and *SHUDdown2* modes. The OAP
is a landmark close to a target, and the target is defined by its
position relative to the OAP. In these modes, the !Fly-to point! is
the original OAP. which may be changed by slewing. I
!offset bearing! Panel value - see Section 4.6.13.
430
I SNRL REPORT 9194 Dictionary
!OTS! Over the shoulder steering, used for loft and over-the-shoulder
maneuvers. See Table D-e to see when Over the shoulder steering
Iis in progress.
!OTS pullup! With !low drag! weapons and !OTS!, the angle the A/C must
pullup to reach the correct release angle in an OTS maneuver. In
the first portion of the pullup 'A/C facing target! is not true. Dur-
ing this time interval the !loft pullup! is calculated for a !low drag!
weapon to an imaginary target that is the same !ground range! as
the !target! from the aircraft, but at a bearing from the aircraft
that is 180" from the bearing of the !target!. The !OTS pullup! is
180" minus this !loft pullup! minus ( 2 X !system pitch!). When
!A/C facing target! and !OTS!, !OTS pullup! is equal to !loft
pullup!.
Ioverflown
!overflown exit! True if last weapon mode was exited because the target was
without a release.
!Overfln! The A/C has passed the last release point in a stik. If the !stik
quantity! is 1, the last release point is the target. If the !stik
quantity! is 2, the last release point is one-half the stik interval
past the target. If the !stik quantity! is 3, the last release point is
one stik interval past the target, and so forth.
!pilot entry! The pilot goes through the procedure outlined in Section 4.6.2 to
enter data. The only data that can be affected by this procedure
are the ones associated with the Update Panel Display function
431
U
Dictionary ALSPAUGH, FAULK. BRITTON. PARKER, PARNAS, AND SHORE 1
!present position entered! Pilot enters coordinates for A/C present position. For rules of
data entry, see Section 4.6.2. 3
!pullup point! Either !ground pulbip point! or !blast pullup point!, whichever is
closer. 3
!R65! Desig! AND low drag! AND !Special! AND !A/C facing target! at
optimum pullup range for a 65-degree !flight path angle! at release.
!Radalt! One of the values of !Data 24!, indicating the pilot has chosen the I
radar altimeter as the priority backup ranging sensor. Panel value
- See Section 4.6.31. 1
!RADALT reasonable! 50 ft < /RADALT/ < 4990 ft AND -30" <!system roll! < 30
!range to Rmax! The !Range! to the point where !Rmax! will be true. 3
!Ready station! !Station selected!
class!#$UNS
AND /WEAPTYP/#00 AND !weapon
3
!Redesignate! (/TD/=$On$ OR !Non-zero digit entered!) AND *AflyUpd*
432 1
NRL REPORT 9194 Dictionary
!Rmax! !Desig! AND flow drag! AND !Special! AND !A/C facing target!
!Rmax6000!!Desig!
ANIgon ag!t agti mxmmrne
AND Hlow drag! AND !Special! AND !A/C facing target!
AND !ground range! to target is equal to !maximumn range! plus
* 6000 feet.
!Rmin! !Desig! AND flow drag! AND !Special! AND !A/C facing target!
AND a/c at minimum pullup range that would result in weapon
impact on target.
!Rmin+6000! !Desig! AND flow drag! AND !Special! AND !A/C facing target!
AND a/c at pullup range that would result in weapon impact 6000
feet long of target.
!roll small! ABS(!system roll!) <! 30' (only relevant for determining whether
system in *OLB* or *UDI* modes)
I !rounded down! If the resolucion for a panel function is greater than 1, the pilot
can enter a value between the values the panel can display, but
when it is displayed back to him, it will be rounded down to the
close-,t value the function can maintain.
I !Sea! One of the values of !Data 23%, indicating that A/C based on sea.
Panel value - See Section 4.6.30.
U
!Serial Channel Test failed! Setup:
//BITEI//:= $XVRAP23$, //BITE2//:= SMone$,
//CSADATA1//:= 0055AA1 6, /'/CSBDATAI/'/:= 1555AAIO
/ /CSADATAI//:= 2AAA55,,
2AAA55 1 .,
//CSBDATA2//:= 2AAA55 1 ,
//CSBDATA3//:= A 55,
.433
a
Dictionary ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE 3
//CSADATA3//. /SERIALI/ is read. Failure criteria:
a. a hardware error occurs in the instruction sequence for /SERIAL1I. I
b. /SERIALI/ # 2AAA55,, (same as //CSADATA3//).
!SINS down! No SINS received OR All SINS invalid OR SINS velocity invalid
for more than I second OR SINS attitude and heading invalid for
more than 3 seconds. 3
!SINS error! Heading error calculated for !HS Stage! - Defined in Section 4.1.6
4
434 1
NRL REPORT 9194 Dictionary
!SINS velocity test passed! Initial value: false. Becomes false on entry into one of the follow-
ing modes: *Lautocal*, *Sautocal*, *Landaln*, SINSaln*,
*HUDaln*, *UDI*, *OLB*, *Mag sl*, *Grid*, *IMS fail*,
*Grtest*. Becomes true when SINS test passed, i.e. when
difference between !IMS NVeI! and !SINS NVe! 1_<fps after 30 s
AND difference between !IMS EVel! and !SINS EVeI! 1< fps at
the end of the TS alignment stage.
!Slant range reasonable! !Grazing angle! > 4 AND -40 *< !system roll! < 40 AND FLR
Antenna Azimuth and Elevation within 16 of Ya axis AND 1700
ft < /SLTRNG/< 54000 ft
!slewed-to point! If /PMHOLD/ = $Yes$, this is the filmstrip point under the
display marker of the map when @T(!slewing finished!) occurs.
The display marker varies, as shown in Section 4.5.4.
!slew-torque cutoffl 20 arcminutes, which is the minimum platform Z axis error worth
slewing out - Z axis errors smaller than this are torqued out.
!Special in range! IF !low drag! THEN !Range to target! < 10 nmi; IF !high drag!
THEN !target in range!.
'steering error! Angle measured from !ground track! to the line from the A/C to
the destination; positive value show destination line to left of
!ground track!, looking down.
435
I
Dictionary ALSPAUGH, FAULK, BRITTON. PARKER, PARNAS, AND SHORE 3
!stik quantity! IF !Shrike! AND *Manrip* THEN 1;
IF !Shrike! AND
MIN(/ARPQUANT/,4));
NOT *Manrip* THEN MIAX(I, I
IF !Special! THEN 1;
IF Mines! THEN MAX(1, MIN(/ARPQUANT/,20));
IF none of above weapons THEN MAX(/ARPQUANT/,j) U
During a multiple release a change in /ARPQUANT/ is not
accepted when /RE/=$On$. 3
!System horizontal velocity! Total velocity along the ground. See !System velocities! and
Tables D-a and D-b.
!system pitch! IF !IMS up! THEN !IMS pitch! ELSE !True AOA! I
!system roll! IF !IMS up! THEN !IMS roll! ELSE 0. 3
!System velocities! System velocities are the most recently calculated velocities from
the most reliable available sensors. Tables D-a through D-c show
the input data items are used at different times to compute the
velocities.
!System vertical velocity! Total velocity away from or toward the ground. See !System velo-
cities! and Table D-c.
!TACAN valid! Section 2.2.6 indicates how the validity of TACAN data is deter-
mined.
!target in range! Target-in-range criteria for different modes are defined in Table
D-g. For the definition of !target in range! for *Waleye*, see
I
Reference 11.
!target return to view! False initially. Becomes true when @T(!impact angle elevation! <
16 deg) WHEN(!target view lost!) occurs. Becomes false when
@T(!impact angle elevation! > 16 deg) OR @T(*CCIP*) OR
@F(*CCIP*) occurs.
!target view lost! False initially. Becomes true when @T(!impact angle elevation!
> 16") WHEN(in *CCIP*) occurs. Becomes false when
@T(*CCIP*) OR @F(*CCIP*) occurs.
3
!Test Value I! Indicated: 512. Standard: 450". The indicated value is the
most useful to the Self-Test use of the data item. The standard
value is given for compatibility with the respective data item table
and is obtained by applying the scale and offset to the indicated
value.
!Test Value 3! Indicated: 320. Standard: 1.25 (see !Test Value 1!)
!time elapsed! Clock time from some moment 5
436 3
NRL REPORT 9194 Dictionary
I !TOS! Tail on steering, used to steer the A/C away from a weapon blast
with the tail of the A/C pointing at the blast.
!TS stage complete! Initially false. Becomes false on entry to *HUDaln*. *Landaln*,
*SINSaln*, *UDI*. *OLB*, *Mag sl*, *Grid*, *M fail*,
*Grtest*. Becomes true when (TBD).
!True AOA! The smoothed value of .76 X /AOA/ - 8.68. The smoothing is a
simple lag filter with time constant 3.125 seconds. The device is
read every 0.025 seconds.
This definition is device-dependent and likely to change if the
current AOA sensor is replaced.
!weapon class! Weapons are classified by drag and other characteristics in Table
2.4-a.
437
I
Dictionary ALSPAUGH, FALK, BR=NON. PARKER, PARNAS, AND SHORE3
!weapons released! Number of weapons in the latest stik that have actually been
released. Angle of weapon velocity vector to earth horizontal.
down negative.
!weapon release angle! Angle between weapon velocity vector and earth horizontal, down
negative.
!within grace period! Less than 1.6 seconds elapsed since one of the following modes
exited: *BOC*, *BOCFlytoO*, *BOCoffset*3
!X--axis corrected! Initially false. Becomes false on entry to !CL stage!, !CA stage!,
!HL stage!, !HC stage!, WFC stage!, WND stage! or !HS stage!.
Becomes true when the IMS X axis has been torqued or slewedI
(see Tables 4.1-d and 4.1-i) such that the condition !axis aligned!
!Yai orce!holds.3
'Y-ais crreced!Initially false. Becomes false on entry to !CL stage!, !CA stage!,
!HL stage!, !HC stage!, !FC stage!, !ND) stage! or !HS stage!.
Becomes true when the IS Y axis has been torqued or slewed
(see Tables 4.1-d and 4.1-i) such that the condition !axis aligned!I
!Z-axis corrected! Initially false. Becomes false on entry to !CA stage!, !HC stage!,3
!FC stage!, !ED stage!, !ND stage!, and !HS stage!. Becomes true
when the IMVS-Z axis has been torqued or slewed (see Tables 4.1-e
and 4.1-j) such that the condition !axis aligned! holds.3
*Dl*
*DIG* Always X X X
*PolarDI' ________
*Polarl' X Alwavs X X X3
*Magsl*
*Grid* X X !Doppler !Doppler !Doppler
*OLB* Up! Down! AND Down! AND
*_____
fail*__ _______ !ADC Up! !.ADC Down!
VELOCITY !IMS NVeI! WIS NVeI! !DGNDSP! /TAS/ stale /TAS/
SOURCES !IMS EVeI! WIS EVeI! drift angle !True AOA! !True AOA!
damped by heading !system pitch! stale windI
_________ !DGNDSP! _______ _______wind !svstem pitch!
438
NRL REPORT 9194 Dictionary
3 *Lautocal*
*Landaln*
*OlUpdate* Constant (0)
*HUDalD* ________________
Alignment
*DIG*, *DI*
*1*, *UDIP /ADCFAEL/=-$No$ /ADCFAIL/=$Yes$ X x
*PolarI*__________
I
___________ ______ ___
Mag s*
*Grid*, 0LB* X X !ADC Up! NOT !ADC Up!
*IMSfail* __ __ _ X Always
3 IMS VVeI!
damped by
!System horizontal
velocities!
/TAS/,
!flight path angle!
0
43
Dictionary ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE3
MODES NTS1
EVE-Q
All nay @T(/TD/=40On$) @T(In mode) OR
update modes @F(In mode)
*Landaln*
*OlUpdate* @T(/TD/=S$On$) X
*I*, *()LB* WHEN~aiming switches set!)
*HlJDaln* X @F(!aiming switches set!)
________
____________________OR @F(Tn mode)
*Nattack* @T(/TD/=SOnS OR /RE/=$On$ @F(In mode) OR
(Not !Shrike!) OR !After slewing!) @T(/TD/ = $On$)I
WHEN(NOT !Desig!) WHEN (!Desig!)
@T(In mode) WHEN (Not
____________
____________________________!within grace period!)
*Noffset* @T(/TD/=40n$ OR /RE/= $On$) @T(Jn mode) OR @F(In mode)I
(Not !Shrike!) WIHEN (NOT !Desig!) OR @T(/TD/ --$On$)
WHEN(!Desig!)
@T(ln mode) WHEN (Not
_____________________________!within grace period!)
*BOC* @T(In mode) X
*SBOC*
(Not !Shrike!)_______________
*BOCFlyto)* @T(/TD/=$On$ OR /RE/ =$On$ @T(In mode) OR
(Not !Shrike!) OR !After slewing!) @T(/TD/-$OnS) WHEN(!Desig!)
*BOCofrset* @T(/TD/-=40n$ OR /RE/ = $On$) @T(In mode) OR
(Not !Shrike!) WHEN(NOT !Desig!) @T(/TD/=S$OnS) WHEN(!Desigl)
*Snattack* @T(/TD/=SOn$ OR @F(ln mode)U
!After slewing!) WHEN
(NOT !Desig!)
*Snoffset* @T(/TD/--$On$) WHEN @T(Tn mode) OR @F(In mode)
(NOT !Desig!)
*SBOCFlytoO* @T(/TD /-$On$ OR tAfter slewing!) @T(In mode)
__________ IHEN (NOT !Desig!)
*SBOCoffset* @TITD /-$On$) WHEN (NOT !Desiq! @T(In mode)
**1N4BShrike** @T(/TD/=SOnS OR /RE/=SOn$) @F(In mode) OR
WHEN (NOT !Desig!) @T(/TD /=$On$) WHEN M!esig!)
*WValleye* @T(/TD/=SOn$) @F(In mode) OR
WHEN (NOT !Desig!) @T(/TD/=OnS) WHEN
_ _ __ __ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
4410
INRL REPORT 9194 Dictionary
I MODES
**LoNuke**
____
@T(!Desig!) OR
___EVENTS
@T(!Overfln!) @T(!weapons
______
@T(!A/C facing
@T(!Range! to WHEFN(!Desig! released!=1) target!)
!target! < AND Iweapons WVHEN(!OF-range!
500 ft OR released!uO) 42 nmi)
!steering error!
< 20 deg)
_________ WHEEN !GAS!)_____
**iue* @T(!Desig!) OR @T(!Overfln!) @T(!OF-range!
@T(!Range! to X WHMEN(!Desig!) > 13000 ft)
!target! < OR WHEN(!Desig! AND
5000 ft OR @T(!weapons, !Overfln! AND
!steering error! released!=1) !weapons
< 20 deg) released! = 0)
WHEMN(!GAS!) OR
@T(!A/C facing
I ______________~~_______<42
target!)
W'HEN(!OF-range!
nmi)
I~ _________
!steering error!
<20 deg)
WHN(!GAS!)___ __________
I 5000 ft OR
!steering error!
< 20 deg)
WH N !GAS!)_______
jSTEERIN G
__________
441
Dictionary ALSPAUGH, FAULK, BRrTTON, PARKER, PARNAS, AND SHORE
MODES - !tarmet!
*Nattack* location on ground overlaid by AS at designation and after
*BOCFlytoO* each slewU
*Snattack*
*SBOCFlytoO*
*HUDdownl* location on ground intersecting the HUD ORA at designation
*SHUDdownl* __________________________
*HUDdown2* OAP is the point on the ground intersecting the HUD ORA at
*SHUDdown2* designation; target is a point on the line drawn from the
OAF in the direction defined by !Offset bearing!; the
target is !Offset range! nmi from the OAF.
*Noffset* OAP is the point on the ground overlaid by AS at
*Snoffset* designation and after each slew; target is a point on theI
line drawn from the OAP in the direction defined by
!Offset bearing!; the target is !Offset range! nrni from
the OAF.
*BOC* Before slewing, the target is the 'Fly-to point!; afterI
*SBOC* slewing, it is the point defined by the radar cursors when
@T(!slewing finished!) occurs.
*BO~offset* OAF is defined in the same way the target is defined inI
*SBOCoffst* *BOC* (*SBOC*); target position relative to OP.P is
defined in *Noffret* (*Snoffset*)
*Walleve* location on ground overlaid by AS at designation
*Nattak*
*Noffset* !high drag! !low drag! X x
*BOCoffset* ___________
____
_ ______ ___
___ __
___ ____ ___ ___ ___ ____ ___ ___ ___ 14366 ft
4421
NRL REPORT 9194
I /ARPQUANT/ .......................................................................................
'/ASAZ//................................................................................................
//ASEL// ................................................................................................
132
62
62
//ASLAZ// ................................................................................. ........... 62
//ASLCOS// ......................................................................................... 63
,//ASLEL//........................................................................................... 62
//ASLSIN// .......................................................................................... 63
//AUTOCAL// ...................................................................................... 31
//A.ZRING//......................................................................................... 86
/BAROADC/ ......................................................................................... 41
//BAROHUD// ...................................................................................... 64
//BITE1// ........................................................................................... 118
//BITE2// ........................................................................................... 119
/BNMDRAG/ ........................................................................................ 71
//7BMREL//................................................................ ........................ 77
I ,/BNMTON// ........................................................................................
,/BRGDEST// .......................................................................................
159
150
I//COMPCTR//
/BRGSTA/ ..........................................................................................
......................................................................................
J'/CO PFAEL// ......................................................................................
140
32
155
I'/COMPFAIL//
/,/COMPFAIL//......................................................................................
......................................................................................
//COMPFAIL//......................................................................................
161
33
49
/CSADATAn// ...................................................................................... 120
/CSBDATAn// ...................................................................................... 121
/CURAZCOS// ..................................................................................... 50
//CLTRAZSIN//..................................................... ................................. 50
'/CLMENABL//.................I.......I............................................................. 51
/CU~POS// ......................................................................................... 52
"DCTEST/ .......................................................................................... 112
/ /DESTPNT//...................................................................... ................. 87
443
..
.I.
I
Indexes ALSPAUGH, FAULK. BRrrTON. PARKER, PARNAS, AND SHORE 5
"9I
I
444
I
NRL REPORT 9194
445
I
Indexes ALSPAUGH. FAULK, BRITTON, PARKER, PARNAS. AND SHORE 5
//RNGUN IT// ........................................................................................................................... 153
//RNGUNIT // .......................................................................................................................... 89
//ROLLCOSH// ......................................................................................................................... 63
/ROLLCOSI/ .............................................................................................................................. 29
//RO SINH // .......................................................................................................................... 63
/ROLL I ............................................................................................................................... 29
/SERIALI/ .................................................................................................................................. 114
/SERIAL2/ ................................................................................ 11I
/SINEVEL/ ................................................................................................................................. 143
/SINHDG / .................................................................................................................................. 143
/SINLAT/ ................................................................................................................................... 143
/SINLONG / ................................................................................................................................ 143
/S NVEL/ ............................................................................... 143
/SINPTH / ................................................................................................................................... 143
/SINROL/ ................................................................................................................................... 143
/SLEWRL/ ........................................ ............................................................. 125
/SLEWUD/ ................................................................................ 125
/SLTRNG/ ............................................................................................................ ................... 47
//SPA REI// ............................................................................... 122
//SPARE2// ............................................................................................................................... 122
/STA IRDY/ .......................................................................................................................... 75
/STA2RDY/ ............................................................................................................................... 75
/STA3RDY / .............................................................................................................................. 75
/STA6RDY/ ............................................................................................................................... 75
/STA7RDY/ ............................................................................................................................... 75
/STA8RDY/....................................75
//ST EERA Z// .......................................................................................................................... 5
//ISTEER EL// ......................................................................................................................... 55
//STERRO R //. .........................................................................................................................
. . 157
i'TAS/ ....... ...................................................... .................................................... 43
/TD / ...................................................................................................................................... I 147
/THD GCOS/ ............................................................................................................................. 29
/THDGSIN / .............................................................................................................................. 29
//TSTADCFLR// ......................................... .............................. .. . ..................... I 44
/'TSTAD CFLR// ........................................................................ ...................................... . 57
/UL T222//.. ...................................................................................................................... 106
/ULIT 32 i/.//
/UrLIT32/ ...............................................................................................................................
..................................................................................... .......................................... 1I
106
/ULITN// .............................................................................................................................. 106
!UJLITSII.................................................................................................. 106
446
NRL REPORT 9194
I
I
I
U
447
I
I
Indexes ALSPAUGH, FAULK, BRrnON, PARKER, PARNAS, AND SHORE
Mode Index
I
*0 U pdate * ................................................................................................................................ 183
*A/A G un* ................................................................................................................................ 223
*AfMyUpd s* ................................................................................................................................ 215
*A /G G un.*................................................................................................................................ . 223
*A raln* ....................................................................................................................................... 187
*BOC*..... ............................................................................................................................... . 221
*BOC Fy * ..............................................................................................................................
.. 222
*BOCofI t** ................................................................................................................................ . 222 I
*C I * ........................................................................................................................................ 223
*DI* ....................................................................... . . . .
* D .................. ................................................................................................................... 19
*GI d* ......................................................................................................................................... 19
*Griy d * ..................................................................................................................................... 23
. . . 181
*Lau i l* ...................................................................................................................................
* ................................................................................................................................
*L oN ukeda 226
448
NRL REPORT g194
*W alleye* .................................................................................
224
449
I
Indexes ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
//LLITW// .........................................................................
304
288
//LSOLCUA Z// .............................................................................
S//LSOLCUEL// 288
.............................................................................
//LW DIG 1// ...............................................................................
304
//LWDIG2// ...............................................................................
304
304
//LWDIG3// ...............................................................................
//LW DIDIG4// ...............................................................................
304
//LW DIG 5// ...............................................................................
304
//LW D 304
...............................................................................
.IG6//
//LWDIG7// ...............................................................................
304
279
//MAAGHDGH// .............................................................................
//M APOR // ...............................................................................
301
/ iMARKW IN //.............................................................................
310
S//PTCHAN 280
G // .............................................................................
//PUACAZ// ..............................................................................
281
281
/./PUACEL//...............................................................................
371
//RNGHND //,..............................................................................
371
//RNGTEN //,..............................................................................
//RNGUNIT//.......................................................................371
286
//ROLLCOSH// .............................................................................
//ROLLSINH// .............................................................................
286
//STEERAZ// ..............................................................................
260
259
//STEEREL// ..............................................................................
//STERROR// ..............................................................................
373
//ULIT222// ...............................................................................
304
304
//ULTLIT321// ...............................................................................
//ULITN// .........................................................................
304
'/.ULITS// .................................................................................
304
290
/USOLCUAZ//.............................................................................
/USOLCUEL// .............................................................................
290
/UWDIG1// ............................................................... 304
UWDIG2// ...............................................................................
304
/UW DIG3// ...............................................................................
304
304
'L rDIG4,// ...............................................................................
'UW DIG5// ...............................................................................
304
,'UWDIG6// ...............................................................................
304
rVERTVEL// ..............................................................................
293
,'rTVELAC / / ..............................................................................
293
XCON14MC .......... 302
..........................................................................
I'XCOMM F!/ ...............................................................................
302
XGYCOM // .......................................................................
246
XSLE\V / ............................ 249
...................................................................
249
'XSLSEN// ...............................................................................
CO // ...............................................................................
302.
I 451
I
Indexes ALSPAUGH, FAULK, BRITTON, PARKER, PARNAS, AND SHORE
45I