MARK 33 DIGITAL INFORMATION

TRANSFER SYSTEM (DITS)

PART 1
FUNCTIONAL DESCRIPTION, ELECTRICAL
INTERFACE, LABEL ASSIGNMENTS AND
WORD FORMATS

ARINC SPECIFICATION 429PART1-16

PUBLISHED: SEPTEMBER 27, 2001

AN DOCUMENT
Prepared by
AIRLINES ELECTRONIC ENGINEERING COMMITTEE
Published by
AERONAUTICAL RADIO, INC.
2551 RIVA ROAD, ANNAPOLIS, MARYLAND 21401
This document is based on material submitted by various
participants during the drafting process. Neither AEEC nor ARINC
has made any determination whether these materials could be
subject to valid claims of patent, copyright or other proprietary
rights by third parties, and no representation or warranty, express or
implied, is made in this regard. Any use of or reliance on this
document shall constitute an acceptance thereof “as is” and be
subject to this disclaimer.
 Copyright 2001 by
AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401-7465 USA

ARINC SPECIFICATION 429PART1-16©

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)
PART 1
FUNCTIONAL DESCRIPTION, ELECTRICAL INTERFACE,
LABEL ASSIGNMENTS AND WORD FORMATS

Published: September 27, 2001

Prepared by the Airlines Electronic Engineering Committee

Specification 429 Adopted by the Airlines Electronic Engineering Committee: July 21, 1977
Specification 429 Adopted by the Industry: September 15, 1977
Summary of Document Supplements

Supplement Adoption Date Published

Specification 429-1 April 11, 1978 June 1, 1978
Specification 429-2 December 6, 1978 March 1, 1979
Specification 429-3 August 31, 1979 November 1, 1979
Specification 429-4 June 17, 1980 August 1, 1980
Specification 429-5 March 12, 1981 April 4, 1981
Specification 429-6 December 9, 1981 January 22, 1982
Specification 429-7 November 4, 1982 January 3, 1983
Specification 429-8 November 4, 1983 December 3, 1984
Specification 429-9 October 11, 1984 April 30, 1985
Specification 429-10 November 7, 1985 November 17, 1986
Specification 429-11 June 15, 1988 July 22, 1988
Specification 429-12 October 25, 1989 July 1, 1990
Specification 429-13 October 8, 1991 December 30, 1991
Specification 429-14 November 4, 1992 January 4, 1993
Specification 429-15 April 18, 1995 September 1, 1995
Specification 429-16 November 14, 2000 September 27, 2001

A description of the changes introduced by each supplement is included on goldenrod paper at the end of this document.
 FOREWORD
Activities of AERONAUTICAL RADIO, INC. (ARINC)
and the
Purpose of ARINC Reports and Specifications

Aeronautical Radio, Inc. is a corporation in which the United States scheduled airlines are the
principal stockholders. Other stockholders include a variety of other air transport companies, aircraft
manufacturers and non-U.S. airlines.

Activities of ARINC include the operation of an extensive system of domestic and overseas
aeronautical land radio stations, the fulfillment of systems requirements to accomplish ground and
airborne compatibility, the allocation and assignment of frequencies to meet those needs, the
coordination incident to standard airborne communications and electronics systems and the exchange
of technical information. ARINC sponsors the Airlines Electronic Engineering Committee (AEEC),
composed of airline technical personnel. The AEEC formulates standards for electronic equipment
and systems for the airlines. The establishment of Equipment Characteristics is a principal function of
this Committee.

It is desirable to reference certain general ARINC Specifications or Report which are

applicable to more than one type of equipment. These general Specifications and Reports may be
considered as supplementary to the Equipment Characteristics in which they are referenced. They are
intended to set forth the desires of the airlines pertaining to components and general design,
construction and test criteria, in order to insure satisfactory operation and the necessary
interchangeability in airline service. The release of a Specification or Equipment Characteristics
should not be construed to obligate ARINC or any airline insofar as the purchase of any components or
equipment is concerned.

An ARINC Report ( Specification or Characteristic) has a twofold purpose, which is:

(1) To indicate to the prospective manufacturers of airline electronic equipment the

considered opinion of the airline technical people, coordinated on an industry basis,
concerning requisites of new equipment, and

(2) To channel new equipment designs in a direction which can result in the maximum
possible standardization of those physical and electrical characteristics which influence
interchangeability of equipment without seriously hampering engineering initiative.

ii
 ARINC SPECIFICATION 429
TABLE OF CONTENTS

ITEM SUBJECT PAGE

1.0 INTRODUCTION 1
1.1 Purpose of this Document 1
1.2 Organization of ARINC Specification 429 1
1.3 Relationship to ARINC Specification 419 1
1.4 “Mark 33 Digital Information Transfer System” Basic Philosophy 1
1.4.1 Numeric Data Transfer 1
1.4.2 ISO Alphabet No. 5 Data Transfer 1
1.4.3 Graphic Data Transfer 1

2.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS 2

2.1 Message Related Elements 2
2.1.1 Direction of Information Flow 2
2.1.2 Information Element 2
2.1.3 Information Identifier 2
2.1.4 Source/Destination Identifier 3
2.1.5 Sign/Status Matrix 3
2.1.5.1 BCD Numeric 4
2.1.5.2 BNR Numeric Data Words 4
2.1.5.3 Discrete Data Words 5
2.1.6 Data Standards 5
2.2 Electrically Related Elements 6
2.2.1 Transmission System Interconnect 6
2.2.2 Modulation 6
2.2.3 Voltage Levels 6
2.2.3.1 Transmitter Voltage Levels 6
2.2.3.2 Receiver Voltage Levels 7
2.2.4 Impedance Levels 7
2.2.4.1 Transmitter Output Impedance 7
2.2.4.2 Receiver Input Impedance 7
2.2.5 Fault Tolerance 7
2.2.5.1 Receiver External Fault Voltage Tolerance 7
2.2.5.2 Transmitter External Fault Voltage 8
2.2.5.3 Transmitter External Fault Load Tolerance 8
2.2.6 Fault Isolation 8
2.2.6.1 Receiver Fault Isolation 8
2.2.6.2 Transmitter Fault Isolation 8
2.3 Logic Related Elements 8
2.3.1 Digital Language 8
2.3.1.1 Numeric Data 8
2.3.1.2 Discretes 8
2.3.1.3 Maintenance Data (General Purpose) 8
2.3.1.4 AIM Data 8
2.3.1.5 File Data Transfer 8
2.3.1.5.1 Bit-Oriented Protocol Determination 9
2.3.2 Transmission Order 9
2.3.3 Data Bit Encoding Logic 9
2.3.4 Error Detection/Correction 9
2.4 Timing Related Elements 9
2.4.1 Bit Rate 9
2.4.1.1 High Speed Operation 9
2.4.1.2 Low Speed Operation 9
2.4.2 Information Rates 10
2.4.3 Clocking Method 10
2.4.4 Word Synchronization 10
2.4.5 Timing Tolerances 10

3.0 MARK 33 DITS APPLICATIONS NOTES 11

3.1 Radio Systems Management 11
3.1.1 Word Format and Digital Language 11
3.1.2 Update Rate 11
3.1.3 Sign/Status Matrix 11
3.1.4 Frequency Ranges and Switching Functions 11
3.1.4.1 ADF 11
3.1.4.2 DME 11
iii
 ARINC SPECIFICATION 429
TABLE OF CONTENTS

ITEM SUBJECT PAGE

3.1.4.3 HF Communications 11
3.1.4.4 ILS 11
3.1.4.5 VOR/ILS 11
3.1.4.6 VHF Communications 11
3.1.4.7 ATC Transponder 11
3.2 AIM Information Transfer 12

ATTACHMENTS
1-1 Label Codes 13
1-2 Equipment Codes 44
2 Data Standards 48
3 Voltage Levels 76
4 Input/Output Circuit Standards 77
5 International Standards Organization Code #5 78
6 General Word Formats and Encoding Examples 79
7 Data Bit Encoding Logic 114
8 Output Signal Timing Tolerances 115
9A General Aviation Labels and Data Standards 116
9B General Aviation Word Examples 118
9C General Aviation Equipment Identifiers 125
10 Manufacturer Specific Status Word 126
11 System Address Labels 127

APPENDICES
A Laboratory Verification of ARINC 429 DITS Electrical Characteristics 129
B An Approach to a Hybrid Broadcast-Command/Response Data Bus Architecture 162
C Digital Systems Guidance (Part 1) 167
D Digital Systems Guidance (Part 2) 174
E Guidelines for Label Assignments 179
X Chronology & Bibliography 181

iv

1.0 INTRODUCTION
1.1 Purpose of this Document
This document defines the air transport industry’s standards
for the transfer of digital data between avionics systems
elements. Adherence to these standards is desired for all
inter-systems communications in which the system line
replaceable units are defined as unit interchangeable in the
relevant ARINC characteristics. Their use for intra-system
communications in systems in which the line replaceable
units are defined in the ARINC characteristics as system
interchangeable is not essential, although it may be
convenient.
1.2 Organization of ARINC Specification 429
ARINC Specification 429 was originally published in a
single volume through version 14 (429-14). The size of the
document and the need for improved organization dictated
the division of the document into three parts. Those three
parts include:
Part 1 Functional Description, Electrical Interface, Label
Assignments and Word Formats
Part 2 Discrete Word Data Formats
Part 3 File Data Transfer Techniques
c-15 Part 1 provides the basic description of the functions and
the supporting physical and electrical interfaces for the data
transfer system. Data word formats, standard label and
address assignments, and application examples are defined.
Part 2 lists discrete word bit assignments in label order. Part
3 describes protocols and message definitions for data
transferred in large blocks and/or file format. For
convenience of the user, the section and attachment
numbering has been retained for the material moved from
the original Specification to Part 3.
Updates to each part of future releases of ARINC 429 will
be independent of the other parts to accommodate timely
revisions as industry needs dictate. The dash numbers for
each Part will NOT be synchronized with the other Parts as
time passes. Users of ARINC Specification 429 should
ensure that the latest version of each Part is used when
designing or procuring equipment.
1.3 Relationship to ARINC Specification 419
ARINC Specification 419, “Digital Data System
Compendium”, is a catalog of the elements of the several
digital data transmission systems that have found
application during the “emergent” period of digital avionics
technology. The maturing of this technology, now evident
in the scope of its planned use on aircraft of the 1980s and
beyond, has shown the need for a generally applicable
digital information transfer system having capabilities not
provided by any combination of the elements presently
defined in Specification 419. In defining such a system, this
document draws on the experience gained in the preparation
of Specification 419 but is otherwise separate and distinct
from it. Addition of the element specifications of the
system defined herein to the Specification 419 catalog is not
anticipated.
ARINC SPECIFICATION 429, PART 1 - Page 1
1.4 “Mark 33 Digital Information Transfer System”
- Basic Philosophy
This “Mark 33 Digital Information Transfer System
(DITS)” specification describes a system in which an
avionics system element having information to transmit
does so from a designated output port over a single twisted
and shielded pair of wires to all other system elements
having need of that information. Bi-directional data flow on
a given twisted and shielded pair of wires is not permitted.
1.4.1 Numeric Data Transfer
The Mark 33 DITS numeric data transmission
characteristics have been developed from those of
successful predecessor air transport industry digital
information transfer systems. Data for transmission,
encoded in either twos complement fractional binary
notation or binary coded decimal notation, is supplied from
source systems at rates sufficiently high to ensure small
incremental value changes between updates. Transmission
is made “open loop”, i.e., sinks are not required to inform
sources that information has been received. A parity bit is
transmitted as part of each data word to permit simple error
checks to be performed by the sinks. These, together with
data reasonableness checks which may also be performed
by the sinks, may be used to prevent the display or other
utilization of a erroneous or suspect word. The inherently
high integrity of the twisted and shielded wire transmission
medium ensures that such drop-outs are few. The low rates
of change of the data ensure that when one does occur, it is
of no consequence.
1.4.2 ISO Alphabet No. 5 Data Transfer
In addition to the transfer of BNR and BCD numeric data as
just described, the Mark 33 DITS handles alpha and
numeric data encoded per ISO Alphabet No. 5. The same
“broadcast” transmission philosophy is used, although the c-1
“housekeeping” aspects of system operation differ in order
to accommodate particular needs associated with this type
of data. These differences will be addressed individually in
this document as they arise.
1.4.3 Graphic Data Transfer
A third type of data which may eventually be handled by the
Mark 33 DITS is graphic data, i.e., the lines, circles,
randomly positioned alpha/numeric text and other symbols
used on CRT map and similar displays. The technique
employed for this purpose can be basically similar to that c-1
used for ISO Alphabet No. 5 alpha/numeric data transfer.
However, because a need for graphic data handling
capability has not yet emerged, the air transport industry has
decided not to be specific concerning this technique for the
moment. When the need for graphic data handling is
established, appropriate specification material will be
developed.
 ARINC SPECIFICATION 429, PART 1 - Page 2
2.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS
2.1 Message Related Elements
This section describes the digital data transfer system
elements considered to be principally related to the message
itself or the manner in which it is handled.
2.1.1 Direction of Information Flow
The information output of an avionics system element
should be transmitted from a designated port (or ports) to
which the receiving ports of other system elements in need
of that information are connected. In no case does
information flow into a port designated for transmission.
COMMENTARY
A separate data bus (twisted and shielded pair of wires
per Section 2.2.1) for each direction is used when data
is required to flow both ways between two avionics
systems elements.
2.1.2 Information Element
The basic information element is a digital word containing
32 bits. There are five application groups for such words,
BNR data, BCD data, Discrete data, Maintenance data
(general) and Acknowledgement, ISO Alphabet No. 5 and
Maintenance (ISO Alphabet No. 5) data (AIM). Word
formats for these different applications are depicted in
c-2 Attachment 6 while the relevant data handling rules are set
forth in Section 2.3.1. When less than the full data field is
needed to accommodate the information conveyed in a
word in the desired manner, the unused bit positions should
be filled with binary zeros or, in the case of BNR/BCD
numeric data, valid data bits. If valid data bits are used, the
resolution possible for the information may exceed that
called for in this Specification. The Commentary following
Section 2.1.6 of this document refers.
COMMENTARY
To permit the use of identical error-checking hardware
elements in the handling of BNR and BCD numeric
c-1 data words, the format for the Mark 33 DITS BCD
word differs from that used formerly for this type of
data. Bit No. 32 is assigned to parity, Bit Nos. 31 and
30 to the sign/status matrix, Bit No. 29 is the most
significant bit of the data field, and the maximum
decimal value of the most significant character is 7.
Previously, the BCD word contained no parity bit, the
sign/status matrix occupied Bit Nos. 32 and 31, Bit
No. 30 was the most significant data bit and the
maximum decimal value of the most significant
character was 3. This format made the word 8-bit byte
oriented with respect to the data. This characteristic is
not retained in the Mark 33 system.
Also, latitude and longitude can only be encoded in the
Mark 33 DITS word with the formerly specified
resolution of 0.1 minute of arc if Bit Nos. 9 and 10 are
used for data rather than the SDI function described in
Section 2.1.4 of this document, and the word is
c-1 structured differently from the standard shown in
Attachment 6. Restructuring the word involves
limiting the maximum value of the most significant
character to 1 and moving the remaining BCD
characters towards the MSB by two bit positions. It is
possible, however, that future latitude and longitude
displays will not be the simple, dedicated read-out type
for which BCD data is intended. More likely is the use c-1
of some form of multiple-message display, such as a
CRT, which will be backed by its own data processor
and prefer inputs of BNR data. If this proves to be the
case, these special provisions for BCD-encoding will
not be required.
2.1.3 Information Identifier
The type of information contained in a word is identified by c-2
a six-character label. The first three characters are octal
characters coded in binary in the first eight bits of the word.
The eight bits will: c-4
a. identify the information contained within BNR and
BCD numeric data words (e.g., DME distance, static
air temperature, etc.) and
c-2
b. identify the word application for Discrete, Maintenance
and AIM data.
The last three characters of the six-character label are
hexadecimal characters used to provide for identification of
ARINC 429 bus sources. Each triplet of hexadecimal
characters identifies a “black box” with one or more DITS c-12
ports. Each three character code (and black box) may have
up to 255 eight bit labels assigned to it. The code is used
administratively to retain distinction between unlike
parameters having like labels assignments.
COMMENTARY
Some users have expressed a desire to have means for
identifying label sets and buses associated with a
particular equipment ID code. Octal label 377 has
been assigned for this purpose. (The code appears in
the 3 LSDs of the BCD Word format). The
transmission of the equipment identifier word on a bus c-4
will permit receivers attached to the bus to recognize
the source of the DITS information. Since the
transmission of the equipment identifier word is
optional, receivers should not depend on that word for
correct operation.
Label code assignments are set forth in Attachment 1 to c-2
this document.
Special Note:
In some ARINC 429 DITS applications, a bus will be
dedicated to delivering a single information element from a
source to one or more identical sink devices. In such
circumstances, the sink device designer might be tempted to
assume that decoding the word label is not necessary.
Experience has shown, however, that system developments c-1
frequently occur that result in the need for additional
information elements to appear on the bus. If a sink device
designed for service prior to such a development cannot
decode the original word label, it cannot differentiate
between this word and the new data in the new situation.
The message for sink designers should therefore be quite
clear - provide label decoding from the outset, no matter
how strong the temptation to omit it might be.

2.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS
COMMENTARY
Adherence to the label code assignments of
Attachment 1 is essential in inter-system
communications and in intra-system communications
where the system elements are defined as “unit
interchangeable” per ARINC Report 403. The
assignment of label codes for all such communications
must be coordinated with the air transport industry if
chaos is to be avoided. A manufacturer who finds that
Attachment 1 does not specify the label he needs for
such system application must not simply choose one
from those unassigned and “drive on”. He should
contact AEEC Staff for assistance.
2.1.4 Source/Destination Identifier
Bit Nos. 9 and 10 of numeric data words should be reserved
for a data source/destination identification function. They
are not available for this function in alpha/numeric (ISO
Alphabet No. 5) data words (see Section 2.3.1.3 of this
document) or when the resolution needed for numeric
(BNR/BCD) data necessitates their use of valid data. The
source/destination identifier function may find application
c-1 when specific words need to be directed to a specific system
of a multi-system installation or when the source system of
a multi-system installation needs to be recognizable from
the word content. When it is used, a source equipment
should encode its aircraft installation number in Bit Nos. 9
and 10 as shown in the table below. A sink equipment
should recognize words containing its own installation
number code and words containing code “00”, the “all-call”
code.
COMMENTARY
Equipment will fall into the categories of source only,
sink only, or both source and sink. Use of the SDI bits
by equipment functioning only as a source or only as a
sink is described above. Both the source and sink texts
above are applicable to equipment functioning as both
a source and a sink. Such equipment should recognize
the SDI bits on the inputs and should also encode the
SDI bits, as applicable, on the outputs. DME, VOR,
c-8 ILS and other sensors, are examples of source and sink
equipment generally considered to be only source
equipment. These are actually sinks for their own
control panels. Many other types of equipment are also
misconstrued as source only or sink only. A simple
rule of thumb is: if a unit has a 429 input port and a
429 output port, it is a source and sink! With the
increase of equipment consolidation, e.g., centralized
control panels, the correct use of the SDI bits cannot be
overstressed.
Bit No.
Installation No.
10 9 excluded) should be coded for “Functional Test”. Pass
0 0 See Note Below
0 1 1
1 0 2
1 1 3 When the SSM code is used to transmit status and more
Note: In certain specialized applications of the SDI
function the all-call capability may be forfeited so that
code “00” is available as an “installation no. 4” identifier.
ARINC SPECIFICATION 429, PART 1 - Page 3
When the SDI function is not used, binary zeros or valid
data should be transmitted in Bit Nos. 9 and 10.
COMMENTARY
This document does not address the practical question
of how the SDI bits will be set in those multi-
installation systems in which the source/destination
function is desired. One way would be to use program
pins on the individual installation black boxes which c-1
would be wired to set up the appropriate code. The
ARINC Characteristics devoted to the individual
systems will define the method actually to be used.
2.1.5 Sign/Status Matrix
This section describes the coding of the Sign/Status Matrix
(SSM) field. In all cases the SSM field uses Bits 30 and 31.
For BNR data words, the SSM field also includes Bit 29.
The SSM field may be used to report hardware equipment
condition (fault/normal), operational mode (functional test),
or validity of data word content (verified/no computed
data).
The following definitions apply in this Specification:
Invalid Data - is defined as any data generated by a source
system whose fundamental characteristic is the inability to
convey reliable information for the proper performance of a
user system. There are two categories of invalid data,
namely, “No Computed Data” and “Failure Warning”.
No Computed Data - is a particular case of data invalidity
where the source system is unable to compute reliable data
for reasons other than system failure. This inability to
compute reliable data is caused exclusively by a definite set
of events or conditions whose boundaries are uniquely
defined in the system characteristic.
Failure Warning - is a particular case of data invalidity
where the system monitors have detected one or more c-12
failures. These failures are uniquely characterized by
boundaries defined in the system characteristic.
The system indicators should always be flagged during a
“Failure Warning” condition.
When a “No Computed Data” condition exists, the source
system should annunciate its outputs to be invalid by setting
the sign/status matrix of the affected words to the “No
Computed Data” code, as defined in the subsections which
follow. The system indicators may or may not be flagged,
depending on system requirements.
While the unit is in the functional test mode, all output data
words generated within the unit (i.e., pass through words are
through data words are those words received by the unit and
retransmitted without alteration.
than one reportable condition exists, the condition with the
highest priority should be encoded in Bit Nos. 30 and 31.
The order of condition priorities to be used is shown in the
table below.
 ARINC SPECIFICATION 429, PART 1 - Page 4
2.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS

2.1.5 Sign/Status Matrix (cont’d) BCD NUMERIC SIGN/STATUS MATRIX

Failure Warning Priority 1 Bit No.

No Computed Data Priority 2 Meaning
31 30
Functional Test Priority 3
Normal Operation Priority 4 0 0 Plus, North, East, Right, To, Above
0 1 No Computed Data
Each data word type has its own unique utilization of the 1 0 Functional Test
SSM field. These various formats are described in the 1 1 Minus, South, West, Left, From, Below
following subsections.

2.1.5.1 BCD Numeric

When a failure is detected within a system which would
cause one or more of the words normally output by that
system to be unreliable, the system should stop transmitting
the affected word or words on the data bus.
2.1.5.2 BNR Numeric Data Words
The status of the transmitter hardware should be encoded in
the Status Matrix field (Bit Nos. 30 and 31) of BNR
Numeric Data words as shown in the table below.

Some avionic systems are capable of detecting a fault
condition which results in less than normal accuracy. In
these systems, when a fault of this nature (for instance,
partial sensor loss) which results in degraded accuracy is
detected, each unreliable BCD digit should be encoded
“1111” when transmitted on the data bus. For equipments
having a display, the “1111” code should, when received,
be recognized as representing an inaccurate digit and a
“dash” or equivalent symbol should be displayed in place of
the inaccurate digit. Parameters for which such a degraded
mode of operation is possible are identified in the Note
column of the tables in Attachment 2.
A source system should annunciate any detected failure that
causes one or more of the words normally output by that
system to be unreliable by setting Bit Nos. 30 and 31 in the
affected word(s) to the “Failure Warning” code defined in
the table below. Words containing this code should
continue to be supplied to the data bus during the failure
condition.
The “No Computed Data” code should be annunciated in
the affected BNR Numeric Data word(s) when a source
system is unable to compute reliable data for reasons other
than system failure.

The sign (plus/minus, north/south, etc.) of BCD Numeric
c-12
Data should be encoded in bit numbers 30 and 31 of the
word as shown in the table below. Bit Nos. 30 and 31 of
BCD Numeric Data words should be “zero” where no sign
is needed.
The “No Computed Data” code should be annunciated in
the affected BCD Numeric Data word(s) when a source
system is unable to compute reliable data for reasons other
than system failure.
When the “Functional Test” code appears in Bits 30 and 31
of an instruction input data word, it should be interpreted as
a command to perform a functional test.
When it appears as a system output, the “Functional Test”
code should be interpreted as advice that the data in the c-12
word results from the execution of a functional test. A
functional test should produce indications of 1/8 of positive
full-scale values unless indicated otherwise in an ARINC
equipment characteristic.
If, during the execution of a functional test, a source system
detects a failure which causes one or more of the words
normally output by that system to be unreliable, it should
immediately change the states of Bit Nos. 30 and 31 in the
affected words such that the “Functional Test” annunciation
is replaced with “Failure Warning” annunciation.

COMMENTARY BNR STATUX MATRIX

A typical instruction input to a radio, for example, Bit No.

would be a channel change command word. When this Meaning
31 30
command word is received with the “Functional Test” 0 0 Failure Warning
coding in the SSM field, the radio should exercise its 0 1 No Computed Data
functional test.
1 0 Functional Test
When the “Functional Test” code appears as a system 1 1 Normal Operation
output, it should be interpreted as advice that the data in the
BCD Numeric Data word contents are the result of the
execution of a functional test. A functional test should The sign (plus, minus, north, south, etc.) of BNR Numeric
produce indications of 1/8 of positive full-scale values Data words should be encoded in the Sign Matrix field (Bit
unless indicated otherwise in the associated ARINC No. 29) as shown in the table below. Bit No. 29 should be
Equipment Characteristic. “zero” when no sign is needed.

2.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS
SIGN MATRIX
Bit No.
Meaning
29
0 Plus, North, East, Right, To, Above
1 Minus, South, West, Left, From, Below
Some avionic systems are capable of detecting a fault
condition which results in less than normal accuracy. In
these systems, when a fault of this nature (for instance,
partial sensor loss) which results in degraded accuracy is
detected, the equipment should continue to report “Normal”
for the sign status matrix while indicating the degraded
performance by coding bit 11 as follows:
ACCURACY STATUS
Bit No.
Meaning
11
0 Nominal Accuracy
1 Degraded Accuracy
This implies that degraded accuracy can be coded only in
BNR words not exceeding 17 bits of data. Parameters for
which such a degraded mode of operation is possible are
c-12 identified in the notes column of the tables in Attachment 2.
2.1.5.3 Discrete Data Words
A source system should annunciate any detected failure that
could cause one or more of the words normally output by
that system to be unreliable. Three methods are defined.
The first method is to set Bit Nos. 30 and 31 in the affected
word(s) to the “Failure Warning” code defined in the table
below. Words containing the “Failure Warning” code
should continue to be supplied to the data bus during the
failure condition. When using the second method, the
equipment may stop transmitting the affected word or words
on the data bus. Designers should use this method when the
c-15 display or use of the discrete data by a system is
undesirable. The third method applies to data words which
are defined such that they contain failure information within
c-12 the data field. For these applications, refer to the associated
ARINC equipment characteristic to determine proper SSM
c-15 reporting. Designers should preclude mixing operational
and BITE data in the same word.
The “No Computed Data” code should be annunciated in
the affected Discrete Data word(s) when a source system is
unable to compute reliable data for reasons other than
system failure.
When the “Functional Test” code appears as a system
output, it should be interpreted as advice that the data in the
Discrete Data word contents are the result of the execution
of a functional test.
c-12
DISCRETE DATA WORDS
Bit No.
Meaning
31 30
0 0 Verified Data, Normal Operation
0 1 No Computed Data
1 0 Functional Test
1 1 Failure Warning
ARINC SPECIFICATION 429, PART 1 - Page 5
2.1.6 Data Standards
The units, ranges, resolutions, refresh rates, number of
significant bits, pad bits, etc. for the items of information to
be transferred by the Mark 33 DITS are tabulated in
Attachment 2 to this document.
COMMENTARY
Note that Section 2.3.1.1 of this document calls for
numeric data to be encoded in BCD and binary, the
latter using twos complement fractional notation. In
this notation, the most significant bit of the data field
represents one half of the maximum value chosen for
the parameter being defined. Successive bits represent
the increments of a binary fraction series. Negative
numbers are encoded as the twos complements of
positive value and the negative sign is annunciated in
the sign/status matrix.
In establishing a given parameter’s binary data
standards for inclusion in Attachment 2, the units
maximum value and resolution are first determined in
that order. The least significant bit of the word is then
given a value equal to the resolution increment, and the
number of significant bits is chosen such that the
maximum value of the fractional binary series just
exceeds the maximum value of the parameter, i.e.,
equals the next whole binary number greater than the
maximum parameter value less one least significant bit
value. For example, if the Mark 33 DITS is required to
transfer altitude in units of feet over a range of zero to
100,000 feet with a resolution of one foot, the number
of significant bits is 17 and the maximum value of the
fractional binary series is 131,071 (i.e., 131,072 - 1).
Note that because accuracy is a quality of the
measurement process and not the data transfer process,
it plays no part in the selection of word characteristics.
Obviously, the resolution provided in the DITS word
should equal or exceed the accuracy in order not to
degrade it.
For the binary representation of angular data, othe Mark
33 DITS employs “degrees divided by 180 ” as the c-1
unit of data transfer and ±1 (semicircle) as the range
for twos complement fractional notation encoding
(ignoring, for the moment, the subtraction of the least
significant bit value). Thus the angular range 0
through 359.XXX degrees is encoded as 0 through
±179.XXX degrees, the value of the most significant
bit is one half semicircle and there are no
discontinuities in the code.
This may be illustrated
o
as follows.
o o
Consider encoding
the angular range 0 to 360 in 1 increments. Per the
general encoding rules o
above,
o
the positive semicircle
will cover the range 0 to 179 (one least significant bit
less than fullorange). All the bitso of the code will be
“zeros” for 0 and “ones” for 179 , and the sign/status
c-3
matrix will indicate the positive sign.
o
Theo negative
semicircle will cover the range 180 to 359 . All the
o
bits will be o“zeros” ofor 180 . The codes for angles
between 181 to 359 will be determined by taking the
twos complements of the fractional binary series for
 ARINC SPECIFICATION 429, PART 1 - Page 6
2.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS
2.1.6 Data Standards (cont’d)
COMMENTARY (cont’d)
the result of subtracting
o
each value from 360. Thus,
c-3 the codeo for 181 is the twos complement of the code
for 179 . Throughout
o
the negative semicircle, which
includes 180 , the sign/status matrix contains the
negative sign.
For convenience, all binary word ranges in
Attachment 2 are shown as whole binary numbers
rather than such numbers less one least significant
bit value. Also, the resolutions shown are
approximate only. Accurate resolutions can be
determined, if required, by reference to the range
values and numbers of significant bits for the words of
interest.
It should be noted that in all applications of the twos
complement fractional notation, the maximum value of
the word, once chosen, cannot be changed by the use of
more bits in the data field. The number of bits in the
word affects only the resolution of the data, not its
range.
Binary Coded Decimal (BCD) data is encoded per the
numeric subset of the ISO Alphabet #5 code (see
Attachment 5 to this document) using Bit Nos. 1
through 4 of the seven-bit-per-character code.
Alpha/numeric data is encoded using all seven bits per
character of the ISO Alphabet #5 code and is
transmitted using the special word format described in
Section 2.3.1.3 of this document.
2.2 Electrically Related Elements
This section describes the digital transfer system elements
considered to be principally related to the electrical aspects
of the signal circuit.
2.2.1 Transmission System Interconnect
A data source should be connected to the data sink(s) by
means of a single twisted and shielded pair of wires. The
c-5 shields should be grounded at both ends to an aircraft
ground close to the rack connector and at all production
breaks in the cable.
COMMENTARY
In practical wire line digital information transmission
systems, cable characteristics and electrical mismatches
can produce distortion of the digital data pulses. Also,
noise due to electrical interference perturbs digital
signals.
The performance of a digital receiver depends upon the
receiver input signal characteristics (data with
distortion and noise) and the receiver design.
Prior to the selection of the voltage and impedance
parameters set forth in this section of this document, the
pulse distortion likely to be encountered in systems
built around them in existing size commercial aircraft
was evaluated and judged to be acceptable for a well-
designed receiver. No restriction is placed by this
specification, therefore, on the number or length of
stubs for installations on aircraft no larger than those
existing, e.g., B 747. See Appendix 1 to this document
for a report of this investigation.
Tests have shown that some receivers continue
decoding data properly when one side of the c-4
transmission line is open or shorted to ground. When
this condition exists noise immunity decreases and
intermittent operation may occur. Users desire
protection against non-annunciated system operation in
this mode. This protection may consist of additional
circuitry to detect and annunciate the fault, or to c-5
increase the receiver threshold to above 5.5 volts,
which is the maximum signal level under this one-wire
fault condition.
Most ARINC Characteristics now contain text
specifying that DITS receivers should discontinue
operation when the voltage thresholds fall into the
undefined regions between “Null” and “Hi” or “Null”
and “Lo”. Manufacturers building DITS receivers are
urged to incorporate this feature in their circuitry
whether it is to be used in ARINC 7XX-series c-5
equipment or Non-ARINC devices.
2.2.2 Modulation
RZ bipolar modulation should be used. This is tri-level
state modulation consisting of “HI”, “NULL” and “LO”
states.
2.2.3 Voltage Levels
2.2.3.1 Transmitter Voltage Levels
The differential output signal across the specified output
terminals (balanced to ground at the transmitter) should be
as given in the following table when the transmitter is open
circuit:
HI (V) NULL (V) LO (V)
Line A
to +10 +1.0 0 +0.5 -10 +1.0
Line B
Line A
c-4
to +5 +0.5 0 +0.25 -5 +0.5
Ground
Line B
to -5 +0.5 0 +0.25 +5 +0.5
Ground

2.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS
2.2.3.2 Receiver Voltage Levels
The differential voltage presented at the receiver input
terminals will be dependent upon line length, stub
configuration and the number of receivers connected. In the
absence of noise, the normal ranges of voltages presented to
the receiver terminals (A and B) would be:
“HI” +7.25V to +11V
c-5 “NULL” +0.5V to -0.5V
“LO” -7.25V to -11V
In practice, these nominal voltages will be perturbed by
noise and pulse distortion. Thus, receivers should associate
the following voltage ranges with the three states indicated:
“HI” +6.5V to 13V
c-4 “NULL” +2.5V to -2.5V
“LO” -6.5V to -13V
COMMENTARY
Receiver reaction is currently undefined herein for
voltages that fall in the range just above and below the
“Null” range. Respective equipment characteristics
should be referenced for desired receiver response in
this range. However, it is desirable that all DITS
receivers will discontinue operation when the voltage
levels fall into the undefined regions. Manufacturers
are urged, as new equipment is developed, to “design
in” the rejection capability.
The opinion is held by some people that conditions on
transmission lines will be encountered which will
require receivers to operate with less than the above
defined minimum difference of 4.0V between the
NULL and HI and NULL and LO states. Receiver
designers are encouraged to investigate the
possibilities and problems of working with a minimum
difference of 1 volt between these states and to report
their findings.
Receiver input common mode voltages (terminal A to
ground and terminal B to ground) are not specified
because of the difficulties of defining ground with any
c-4 satisfactory degree of precision. Receiver
manufacturers are encouraged to work with the
differential input voltage (line A to line B) and not line-
to-ground voltages.
2.2.4 Impedance Levels
2.2.4.1 Transmitter Output Impedance
The transmitter output impedance should be 75 ±5 ohms,
divided equally between line A and line B to provide an
impedance balanced output. This output impedance should
c-4 be present for the “HI”, “NULL” and “LO” transmitter
output conditions and also during transitions between these
levels.
COMMENTARY
The output impedance of the transmitter is specified as
75 ± 5 ohms to provide an approximate match to the
characteristic impedance of the cable. The match can
only be approximate due to the wide range of
ARINC SPECIFICATION 429, PART 1 - Page 7
characteristic impedances which may be encountered
due to the variety of conductor wire gauges and
insulation properties. Measurements on a few samples
of wire showed a spread of characteristic impedance of
63 to 71 ohms. An extrapolation over the wire gauges
20 to 26 for wrapped and extruded insulation indicate
an expected characteristic impedance spread of 60 to
80 ohms approx. Twisted shielded wire specifications
do not control the characteristic impedance of the
cable, thus future developments in insulation
techniques may result in cables having characteristic
impedances outside the range estimated.
2.2.4.2 Receiver Input Impedance
The receiver should exhibit the following characteristics,
measured at the receiver input terminals:
Differential Input Resistance RI = 12,000 ohms minimum c-4
Differential Input Capacitance CI = 50pF maximum
Resistance to Ground RH and RG ≥ 12,000 ohms
Capacitance to Ground CH and CG ≤ 50pF.
The total receiver input resistance including the effects of
RI, RH and RG in parallel should be 8,000 ohms minimum c-4
(400 ohms minimum for twenty receiver loads).
No more than twenty receivers should be connected on to
one digital data bus and each receiver should incorporate
isolation provisions to ensure that the occurrence of any
reasonably probable failure does not cause loss of data to
the others.
See Attachment 4 to this document for a pictorial
representation of the input and output circuit standards.
COMMENTARY
The above characteristics apply to differential
amplifier receivers. Opto-isolator technology is
progressing and may soon find application in digital
data receivers. Opto-isolator receivers impose slightly
greater loads on data buses than differential amplifier
receivers and the way in which they are characterized is
different. It is probable, however, that a future revision
of this Specification will include material specifically
related to their use.
2.2.5 Fault Tolerance
2.2.5.1 Receiver External Fault Voltage Tolerance
Receivers should withstand without sustaining damage the
following steady-state voltages being applied to their
terminals, superimposed upon a normally operating bus.
Operation within specification limits is not required under
these conditions.
c-4
a. 30 Vac RMS applied across terminals A and B, or
b. ±29 Vdc applied between terminal A and ground, or
c. ±29 Vdc applied between terminal B and ground.
 ARINC SPECIFICATION 429, PART 1 - Page 8
2.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS
2.2.5.2 Transmitter External Fault Voltage
Transmitter failures caused by external fault voltages should
not cause other transmitters or other circuitry in the unit to
function outside of their specification limits or to fail.
2.2.5.3 Transmitter External Fault Load Tolerance
c-4
Transmitters should indefinitely withstand without
sustaining damage a short circuit applied:
a. across terminals A and B, or
b. from terminal A to ground, or
c. from terminal B to ground, or
d. b and c above, simultaneously.
2.2.6 Fault Isolation
2.2.6.1 Receiver Fault Isolation
Each receiver should incorporate isolation provisions to
c-4 ensure that the occurrence of any reasonably probable
internal LRU or bus receiver failure does not cause any
input bus to operate outside of its specification limits (both
undervoltage or overvoltage).
2.2.6.2 Transmitter Fault Isolation
Each transmitter should incorporate isolation provisions to
ensure that it does not under any reasonably probable LRU
fault condition provide an output voltage in excess of:
a. a voltage greater than 30 Vac RMS between terminal A
and B, or
c-4
b. greater than ±29 Vdc between A and ground, or
c. greater than ±29 Vdc between B and ground.
2.3 Logic Related Elements
This section describes the digital transfer system elements
considered to be principally related to the logic aspects of
the signal circuit.
2.3.1 Digital Language
2.3.1.1 Numeric Data
The Mark 33 DITS should accommodate numeric data
encoded in two digital languages, (i) BNR expressed in
twos complement fractional notation and (ii) BCD per the
numerical subset of ISO Alphabet No. 5 (see Attachment 5
to this document). An information item encoded in both
languages will be assigned a unique address for each (see
Section 2.1.3 and Attachment 1). Word formats are
illustrated in Attachment 6 to this document.
2.3.1.2 Discretes
In addition to handling numeric data as specified above, the
Mark 33 DITS should also be capable of accommodating
discrete items of information either in the unused (pad) bits
c-2
of data words or, when necessary, in dedicated words. Any
discrete information contained in a numeric data word
c-14
c-2
assigned a label in Attachment 1 is specified in the
definition for that word in Attachment 6.
The rule to be followed in the assignment soft bits to
discrete in numeric data words is to start with the least
significant bit of the word and to continue towards the most
significant bit available in the word. Attachment 6 shows
its against the background of the generalized word structure.
There are two types of discrete words. These are general
purpose discrete words, and dedicated discrete words. c-2
Seven labels (270 XXX-276 XXX) are assigned to the
general purpose words in Attachment 1. These words
should be used in ascending label order (starting with 270 c-4
XXX) when the system receiving the data can identify its
source by reference to the port at which it arrives.
2.3.1.3 Maintenance Data (General Purpose)
The general purpose maintenance words are assigned labels
in sequential order as are the labels for the general purpose
discrete words. The lowest octal value label assigned to the
maintenance words should be used when only one
maintenance word is transmitted. When more than one c-2
word is transmitted the lowest octal value label should be
used first and the other labels used sequentially until the
message has been completed. The general purpose
maintenance words may contain discrete, BCD or BNR
numeric data but should never contain ISO Alphabet No. 5
messages. The general purpose maintenance words should
be formatted according to the layouts of the corresponding c-12
BCD/BNR/discrete data words shown in Attachment 2.
2.3.1.4 AIM Data
The information previously contained in this section is no
longer applicable to ARINC Specification 429. For
reference purposes, the section header is retained and the
original contents of this section are located in Part 3 of this
Specification.
2.3.1.5 File Data Transfer
This section previously described a character-oriented file
data transfer protocol. This definition was used as guidance
for the character-oriented file transfer protocol descriptions
incorporated into many ARINC equipment characteristics.
The original contents of this section are located in Part 3 of
this Specification.
The protocol defined in Part 3 is preferred for new
applications. The purpose of this bit-oriented com-
munications protocol is to provide for the transparent
transfer of data files using the ARINC 429 data bus.
c-13
COMMENTARY
The data transparent protocol described in Part 3 was
developed in order to facilitate the communications of
the ACARS Management Unit (MU) and the Satellite
Data Unit (SDU). Its viability as a universal protocol
was recognized by the Systems Architecture and
Interfaces (SAI) Subcommittee, which recommended
its inclusion herein as the standard means of file data
transfer.
The process for determining the protocol (character-
oriented or bit-oriented) to be used in the interaction

2.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS
between two units, where this information is not pre-
determined is described in Section 2.5.19.
2.3.1.5.1 Bit-Oriented Protocol Determination
The ALO word should be sent by any system which
supports the bit-oriented Link Layer protocol just after the
system powers-up, or performs a re-initialization for any
reason. The ALO/ALR protocol process may also be used
when a bit-oriented Link Layer protocol system needs to
determine if any of its interfaces support the bit-oriented
protocol. All systems which support the Link Layer bit-
oriented protocol must be able to respond to the initiation of
this process. Attachment 11C shows the ALO and ALR
c-13 word formats.
When a system with a bit-oriented Link Layer protocol has
the need to make this determination, it should construct the
ALO word and transmit this word to the device in question.
The system should then wait for a maximum period of time
defined by T12. If the device in question has not responded
within T12, the initiating system should initiate another ALO
word and again delay up to T12. An initiating system will
attempt a maximum of N6 ALO word operations before
declaring the device in question as “Not bit-oriented” or
“Not able to respond”.
2.3.2 Transmission Order
The Least Significant Bit (LSB) and Least Significant
Character (LSC) of each word should be transmitted first. It
may be noted that the least significant bit of the word is the
most significant bit of the label and that the label is
transmitted ahead of the data in each case. This “reversed
label” characteristic is a legacy from past systems in which
the octal coding of the label field was, apparently, of no
significance.
2.3.3 Data Bit Encoding Logic
A “HI” state after the beginning of the bit interval returning
to a “NULL” state before the end of the same bit interval
signifies a logic “one”.
A “LO” state after the beginning of the bit interval returning
to a “NULL” state before the end of the same bit interval
signifies a logic “zero”. This is represented graphically in
Attachment 7 to this document.
2.3.4 Error Detection/Correction
The last bit of each word should be encoded such that word
c-5 parity is rendered odd to allow error detection in receivers.
Note that the parity calculation encompasses all 31 label
and information bits of the word.
COMMENTARY
Air transport industry experience with digital
information transfer systems pre-dating the Mark 33
DITS has shown that the twisted shielded pair of wires
can be regarded as a high integrity link unlikely to
introduce bit errors into the data passing through it. It
is for this reason that no means for error correction are
specified in this document. The error detection
capability specified above may be used as desired in
ARINC SPECIFICATION 429, PART 1 - Page 9
receiving terminals. BNR data, for example, may be
checked for parity by reference to the binary state of
Bit No. 32 of each word. Also, the data may be
submitted to reasonableness checks. BCD may be
submitted to reasonableness checks. BCD data
intended for human consumption in the cockpit is
normally smoothed before transmission to ensure
tolerable levels of display jitter. As this process
eliminates any obviously wild data points, the need for
further error detection is questionable. As pointed out
in the Commentary following Section 2.1.2 of this
document, the parity bit was added to the BCD word
for reasons related to BCD/BNR transmitter hardware
commonality, not because a need for it existed for error
detection.
2.4 Timing Related Elements
This section describes the digital data transfer system
elements considered to be principally related to the timing
aspects of the signal circuit.
2.4.1 Bit Rate
2.4.1.1 High Speed Operation
The bit rate for high speed operation of the system should
be 100 kilobits per second ±1%.
2.4.1.2 Low Speed Operation
The bit rate for low speed operation of the system should be
within the range 12.0 to 14.5 kilobits per second. The
selected rate should be maintained within 1%.
NOTE:
High bit rate and low bit rate messages will not be
intermixed on the same bus.
COMMENTARY
Although the bit rates specified above should be held
within the stated tolerances over the long term,
individual bit lengths may fall outside the limits
expected from these tolerances. Bit symmetry and jitter
should be within the tolerances specified in Attachment
8.
Also, notwithstanding the RFI performance of the
ARINC 429 DITS reported in Appendix 1 to this
document, system designers are advised to avoid
selection of 13.6 kilobits per second for low speed
operations and precisely 100 kilobits per second for c-5
high speed operations to ensure that the system is not
responsible for interference to LORAN C systems with
which the aircraft might be equipped.
 ARINC SPECIFICATION 429, PART 1 - Page 10
2.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS

2.4.2 Information Rates COMMENTARY

The minimum and maximum transmit intervals for each RF interference radiated by the Mark 33 DITS using
c-4 item of information transferred by the Mark 33 DITS are the waveform characteristics specified in this section
specified in the tables of Attachment 2. Words with like has been shown not to exceed that permitted by Figure
labels but with different SDI codes should be treated as 21-5 of RTCA Document DO-160, “Environmental
unique items of information. Each and every unique item Conditions and Test Procedures for Airborne
of information should be transmitted once during an Electronic/Electrical Equipment and Instruments”.
c-5 interval bounded in length by the minimum and maximum Also, conducted RF interference is within the limits
values specified in Attachment 2. Stated another way, a specified in Figure 21-2 of DO-160. Appendix 1 to
word having the same label and four different SDI codes this document refers.
should appear on the bus four times (once for each SDI
code) during that time interval.
COMMENTARY
There are no values given for refresh rates in this
Specification. However, it is desirable that data be
refreshed at least once per transmission. Those data
actually requiring long processing times or a large
number of samples are the only types not expected to
be refreshed with every transmission.

Discretes contained within data words should be transferred

at the bit rate and repeated at the update rate of the primary
data. Words dedicated to discretes should be repeated
continuously at the rates defined in Attachment 2.
COMMENTARY

The time intervals between successive transmissions of

a given BCD word specified in table 1 of Attachment 2
to this document are, in general, too short for the signal
to be of use in driving a display device directly. If the
signal was so used the least significant character of the
display, would change too rapidly for human
perception. Considerations other than human factors
demand the time intervals specified. Thus, display
designers should incorporate into their devices means
for selecting those words to be used for updating the
display from the greater quantity delivered.

2.4.3 Clocking Method

Clocking is inherent in the data transmission. The

identification of the bit interval is related to the initiation of
either a “HI” or “LO” state from a previous “NULL” state
in a bipolar RZ code.

2.4.4 Word Synchronization

The digital word should be synchronized by reference to a
gap of four bit times (minimum) between the periods of
word transmissions. The beginning of the first transmitted
bit following this gap signifies the beginning of the new
word.

2.4.5 Timing Tolerances

The waveform timing tolerances should be as shown in
Attachment 8 to this document.
 ARINC SPECIFICATION 429, PART 1 - Page 11

3.0 MARK 33 DITS APPLICATIONS NOTES

3.1 Radio Systems Management 3.1.4.3 HF Communications

One special application of the Mark 33 DITS is to radio Frequency Range: 2.8MHz to 24MHz
systems frequency selection and function switching. The Frequency Selection Increment: 1kHz or .1kHz
following paragraphs set forth the rules which should be Characters encoded in DITS words: 10MHz, 1MHz, 0.1MHz,
followed in the application of the DITS to ensure 0.01MHz, 0.001MHz, 0.1kHz
interchangeability of radios and control sources.
Switching Functions: USB/LSB mode selection
3.1.1 Word Format and Digital Language SB/AM mode selection

The standard DITS 32-bit BCD word should be used, of which

Bit Nos. 1 through 8 constitute the label, Bit Nos. 9 and 10 are Note: Two words may be transmitted for HF frequency
reserved for a source/destination identifier code, bit nos. 11 selection to facilitate frequency resolution of 0.1kHz.
through 29 constitute the data, Bit Nos. 30 and 31 form the
sign/status matrix and Bit No. 32 is the word parity bit. The
data field should contain the frequency to which the radio 3.1.4.4 ILS
defined by the label field is to tune encoded in BCD characters,
together with the discretes required for function switching for Frequency Range: 108.00MHz to 111.95MHz
that radio. Attachment 6 shows how the word should be Frequency Selection Increment: 50kHz
structured for each radio system requiring the DITS Characters encoded in DITS words: 10MHz, 1MHz, 0.1MHz,
management service. 0.01MHz, (100MHz character is
always decimal 1)
3.1.2 Update Rate
Switching Functions: None
The nominal update rate for all radio systems management
words should be five times per second. 3.1.4.5 VOR/ILS

3.1.3 Sign/Status Matrix Frequency Range: 108.00 MHz to 117.95MHz

Frequency Selection Increment: 50kHz
Since sign is not a characteristic of radio systems management Characters encoded in DITS words: 10MHz, 1MHz, 0.1MHz, 0.01MHz,
information, the normal states of the sign/status matrix bits will (100MHz character is always
be binary “zeros”. However, the radios should recognize the decimal 1)
codes for “functional test” and “no computed data”, (see
Section 2.1.5 of this document). They should interpret the Switching Functions: ILS Mode
former as an instruction to perform a functional test or
functional test sequence. They should regard the latter as an
instruction to remain tuned to the frequency contained in the 3.1.4.6 VHF Communications
last valid word received until either another valid word is
decoded or their primary power is removed. Frequency Range: 118.000 MHz to 135.975MHz
Frequency Selection Increment: 25kHz
3.1.4 Frequency Ranges and Switching Functions Characters encoded in DITS words: 10MHz, 1MHz, 0.1MHz, 0.01MHz,
(100MHz character is always
3.1.4.1 ADF decimal 1)

Frequency Range: 190kHz to 1750kHz Switching Functions: None

Frequency Selection Increment:
Characters encoded in DITS word:
Switching Functions:
3.1.4.2 DME
Frequency Range:
(VOR/ILS)
Frequency Selection Increment:
(VOR/ILS)
Characters encoded in DITS word:
Switching Functions:
Display Control
0.5kHz
1000kHz, 100kHz, 10kHz, 1kHz
0.5kHz on/off, BFO on/off,
ADF/ANT mode selection
108.00MHz to 135.95MHz
50kHz
10Mhz, 1Mhz, 0.1MHz
0.05MHz (VOR/ILS only)
(100MHz character is 1
for VOR/ILS, 10MHz character
is limited to 7)
VOR/ILS/MLS
Frequency, DME modes,
Directed Frequency Numbers,
3.1.4.7 ATC Transponder
Note: The ATC Transponder operates on two frequencies
(one receive and one transmit) which do not require
selection. Reply code selection, however, is
required and it is this that the Mark 33 DITS
accommodates).
Reply Code Ranges: 0-7 in four independent groups
Code increments: 1 decimal digit per group
No. of characters encoded
in DITS words: ALL
Switching Functions: Ident. Pulse Select, Altitude
Reporting On/Off, Altitude Source
Select, X-pulse Select (reserved),
VFR/IFR Select (reserved),
IRS/FMC Input Select (reserved).
ARINC SPECIFICATION 429, PART 1 - Page 12

3.0 MARK 33 DITS APPLICATIONS NOTES

3.2 AIM Information Transfer
The information previously contained in this section is no
longer applicable to ARINC Specification 429. For reference
purposes, the section header is retained and the original
contents of this section are located in Part 3.
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 13
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 X X 0 0 0 0 0 0 0 0 Not Used
0 0 2 0 0 0 0 0 0 0 1 Distance to Go X 6-25
0 0 1 0 5 6 0 0 0 0 0 0 0 1 Distance to Go X
0 6 0 0 0 0 0 0 0 0 1 Distance to Go X
0 0 2 0 0 0 0 0 0 1 0 Time to Go X 6-25
0 5 6 0 0 0 0 0 0 1 0 Time to Go X
0 0 2
0 6 0 0 0 0 0 0 0 1 0 Time to Go X
1 1 5 0 0 0 0 0 0 1 0 Time to Station X
0 0 3 0 0 2 0 0 0 0 0 0 1 1 Cross Track Distance X 6-25
0 0 4 0 0 1 0 0 0 0 0 1 0 0 Runway Distance to Go X
0 0 5 0 D 0 0 0 0 0 0 1 0 1 Engine Discrete X
0 0 6 0 D 0 0 0 0 0 0 1 1 0 Engine Discrete X
0 0 7 0 0 0 0 0 0 1 1 1 Spare
0 0 2 0 0 0 0 1 0 0 0 Present Position - Latitude X 6-25-1
0 1 0 0 0 4 0 0 0 0 1 0 0 0 Present Position - Latitude X
0 3 8 0 0 0 0 1 0 0 0 Present Position - Latitude X
0 0 2 0 0 0 0 1 0 0 1 Present Position - Longitude X 6-25-1
0 1 1 0 0 4 0 0 0 0 1 0 0 1 Present Position - Longitude X
0 3 8 0 0 0 0 1 0 0 1 Present Position - Longitude X
0 0 2 0 0 0 0 1 0 1 0 Ground Speed X 6-25
0 0 4 0 0 0 0 1 0 1 0 Ground Speed X
0 0 5 0 0 0 0 1 0 1 0 Ground Speed X
0 2 5 0 0 0 0 1 0 1 0 Ground Speed X
0 1 2
0 3 8 0 0 0 0 1 0 1 0 Ground Speed X
0 4 D 0 0 0 0 1 0 1 0 QTY-LD SEL (LB) X
0 5 6 0 0 0 0 1 0 1 0 Ground Speed X
0 6 0 0 0 0 0 1 0 1 0 Ground Speed X
0 0 2 0 0 0 0 1 0 1 1 Track Angle - True X 6-25
0 0 4 0 0 0 0 1 0 1 1 Track Angle - True X
0 1 3 0 3 8 0 0 0 0 1 0 1 1 Track Angle - True X
0 4 D 0 0 0 0 1 0 1 1 QTY-FLT Deck (LB) X
0 B 8 0 0 0 0 1 0 1 1 Control Panel Set X
0 0 4 0 0 0 0 1 1 0 0 Magnetic Heading X
0 1 4 0 0 5 0 0 0 0 1 1 0 0 Magnetic Heading X
0 3 8 0 0 0 0 1 1 0 0 Magnetic Heading X
0 0 2 0 0 0 0 1 1 0 1 Wind Speed X
0 0 4 0 0 0 0 1 1 0 1 Wind Speed X
0 1 5
0 0 5 0 0 0 0 1 1 0 1 Wind Speed X
0 3 8 0 0 0 0 1 1 0 1 Wind Speed X
0 0 4 0 0 0 0 1 1 1 0 Wind Direction - True X
0 1 6 0 3 8 0 0 0 0 1 1 1 0 Wind Direction - True X
0 B 8 0 0 0 0 1 1 1 0 TCAS Mode/Sens X
0 1 0 0 0 0 0 1 1 1 1 Selected Runway - True X
0 4 D 0 0 0 0 1 1 1 1 Total-FLT Deck (LB) X
0 1 7 0 5 5 0 0 0 0 1 1 1 1 Selected Runway Heading X
0 A 0 0 0 0 0 1 1 1 1 Selected Runway Heading X
0 B 0 0 0 0 0 1 1 1 1 Selected Runway Heading X
0 2 0 0 0 0 1 0 0 0 0 Selected Vertical Speed X 6-25
0 4 D 0 0 0 1 0 0 0 0 TNK-LD SEL (LB) X
0 2 0
0 6 D 0 0 0 1 0 0 0 0 Landing Gear Position Infor & System Status X
0 A 1 0 0 0 1 0 0 0 0 Selected Vertical Speed X
0 0 2 0 0 0 1 0 0 0 1 Selected EPR X 6-25
0 0 2 0 0 0 1 0 0 0 1 Selected N1 X 6-25
0 2 0 0 0 0 1 0 0 0 1 Selected EPR X
0 2 1 0 2 0 0 0 0 1 0 0 0 1 Selected N1 X
0 6 D 0 0 0 1 0 0 0 1 Landing Gear Position Infor & System Status X
0 A 1 0 0 0 1 0 0 0 1 Selected EPR X
0 A 1 0 0 0 1 0 0 0 1 Selected N1 X
0 2 0 0 0 0 1 0 0 1 0 Selected Mach X 6-25
0 4 D 0 0 0 1 0 0 1 0 QTY-LD SEL (KG) X
0 2 2
0 6 D 0 0 0 1 0 0 1 0 Landing Gear Position Infor & System Status X
0 A 1 0 0 0 1 0 0 1 0 Selected Mach X
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 14
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 2 0 0 0 0 1 0 0 1 1 Selected Heading X 6-25

0 4 D 0 0 0 1 0 0 1 1 QTY-LD SEL (KG) X
0 2 3
0 6 D 0 0 0 1 0 0 1 1 Landing Gear Position Infor & System Status X
0 A 1 0 0 0 1 0 0 1 1 Selected Heading X
0 1 1 0 0 0 1 0 1 0 0 Selected Course #1 X 6-25
0 2 0 0 0 0 1 0 1 0 0 Selected Course #1 X
0 2 4 0 6 D 0 0 0 1 0 1 0 0 Landing Gear Position Infor & System Status X
0 A 1 0 0 0 1 0 1 0 0 Selected Course #1 X
0 B 1 0 0 0 1 0 1 0 0 Selected Course #1 X
0 2 0 0 0 0 1 0 1 0 1 Selected Altitude X 6-25
0 2 5 0 4 D 0 0 0 1 0 1 0 1 Load SEL Control X
0 A 1 0 0 0 1 0 1 0 1 Selected Altitude X
0 0 3 0 0 0 1 0 1 1 0 Selected Airspeed X 6-25
0 2 6 0 2 0 0 0 0 1 0 1 1 0 Selected Airspeed X
0 A 1 0 0 0 1 0 1 1 0 Selected Airspeed X
0 0 2 0 0 0 1 0 1 1 1 TACAN Selected Course X
0 1 1 0 0 0 1 0 1 1 1 Selected Course # 2 X
0 2 0 0 0 0 1 0 1 1 1 Selected Course # 2 X
0 4 D 0 0 0 1 0 1 1 1 Total-FLT Deck (KG) X
0 2 7
0 5 6 0 0 0 1 0 1 1 1 TACAN Selected Course X
0 6 0 0 0 0 1 0 1 1 1 TACAN Selected Course X
0 A 1 0 0 0 1 0 1 1 1 Selected Course # 2 X
0 B 1 0 0 0 1 0 1 1 1 Selected Course # 2 X
0 2 0 0 0 0 1 1 0 0 0 VHF COM Frequency X 6-45
0 2 4 0 0 0 1 1 0 0 0 VHF COM Frequency X
0 3 0
0 4 D 0 0 0 1 1 0 0 0 TNK-LD SEL (KG) X
0 B 6 0 0 0 1 1 0 0 0 VHF COM Frequency X 6-45
0 2 0 0 0 0 1 1 0 0 1 Beacon Transponder Code X 6-46
0 3 1
0 B 8 0 0 0 1 1 0 0 1 Beacon Transponder Code X
0 1 2 0 0 0 1 1 0 1 0 ADF Frequency X 6-40
0 3 2 0 2 0 0 0 0 1 1 0 1 0 ADF Frequency X 6-40
0 B 2 0 0 0 1 1 0 1 0 ADF Frequency X 6-40
0 0 2 0 0 0 1 1 0 1 1 ILS Frequency X 6-44
0 1 0 0 0 0 1 1 0 1 1 ILS Frequency X
0 2 0 0 0 0 1 1 0 1 1 ILS Frequency X
0 3 3 0 5 5 0 0 0 1 1 0 1 1 Landing System Mode/Frequency X Note 2
0 5 6 0 0 0 1 1 0 1 1 ILS Frequency X
0 6 0 0 0 0 1 1 0 1 1 ILS Frequency X
0 B 0 0 0 0 1 1 0 1 1 ILS Frequency X
0 0 2 0 0 0 1 1 1 0 0 VOR/ILS Frequency X
0 0 6 0 0 0 1 1 1 0 0 Baro Correction (mb) #3 X
0 1 1 0 0 0 1 1 1 0 0 VOR/ILS Frequency X
0 2 0 0 0 0 1 1 1 0 0 VOR/ILS Frequency X
0 3 4
0 2 5 0 0 0 1 1 1 0 0 VOR/ILS Frequency X
0 5 6 0 0 0 1 1 1 0 0 VOR/ILS Frequency X
0 6 0 0 0 0 1 1 1 0 0 VOR/ILS Frequency #1 X
0 B 0 0 0 0 1 1 1 0 0 VOR/ILS Frequency X
0 0 2 0 0 0 1 1 1 0 1 DME Frequency X 6-41
0 0 6 0 0 0 1 1 1 0 1 Baro Correction (ins of Hg) #3 X
0 0 9 0 0 0 1 1 1 0 1 DME Frequency X 6-41
0 2 0 0 0 0 1 1 1 0 1 DME Frequency X
0 3 5 0 2 5 0 0 0 1 1 1 0 1 DME Frequency X
0 5 5 0 0 0 1 1 1 0 1 Paired DME Frequency X
0 5 6 0 0 0 1 1 1 0 1 DME Frequency X
0 6 0 0 0 0 1 1 1 0 1 DME Frequency #1 X
0 A 9 0 0 0 1 1 1 0 1 DME Frequency X
0 0 2 0 0 0 1 1 1 1 0 MLS Frequency X
0 2 0 0 0 0 1 1 1 1 0 MLS Frequency X
0 5 5 0 0 0 1 1 1 1 0 MLS Channel Selection X
0 3 6
0 5 6 0 0 0 1 1 1 1 0 MLS Frequency Channel X
0 6 0 0 0 0 1 1 1 1 0 MLS Frequency Channel X
0 C 7 0 0 0 1 1 1 1 0 MLS Frequency X
0 0 2 0 0 0 1 1 1 1 1 HF COM Frequency X 6-42-1
0 3 7
0 B 9 0 0 0 1 1 1 1 1 HF COM Frequency X
0 4 0 0 0 0 1 0 0 0 0 0 Spare
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 15
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 2 0 0 1 0 0 0 0 1 Set Latitude X
0 0 4 0 0 1 0 0 0 0 1 Set Latitude X
0 2 0 0 0 1 0 0 0 0 1 Set Latitude X
0 4 1
0 5 6 0 0 1 0 0 0 0 1 Set Latitude X
0 6 0 0 0 1 0 0 0 0 1 Set Latitude X
0 A 4 0 0 1 0 0 0 0 1 Set Latitude X
0 0 2 0 0 1 0 0 0 1 0 Set Longitude X
0 0 4 0 0 1 0 0 0 1 0 Set Longitude X
0 2 0 0 0 1 0 0 0 1 0 Set Longitude X
0 4 2
0 5 6 0 0 1 0 0 0 1 0 Set Longitude X
0 6 0 0 0 1 0 0 0 1 0 Set Longitude X
0 A 4 0 0 1 0 0 0 1 0 Set Longitude X
0 0 2 0 0 1 0 0 0 1 1 Set Magnetic Heading X
0 0 4 0 0 1 0 0 0 1 1 Set Magnetic Heading X
0 2 0 0 0 1 0 0 0 1 1 Set Magnetic Heading X
0 4 3
0 5 6 0 0 1 0 0 0 1 1 Set Magnetic Heading X
0 6 0 0 0 1 0 0 0 1 1 Set Magnetic Heading X
0 A 4 0 0 1 0 0 0 1 1 Set Magnetic Heading X
0 0 4 0 0 1 0 0 1 0 0 True Heading X
0 4 4
0 3 8 0 0 1 0 0 1 0 0 True Heading X
0 4 5 0 0 3 0 0 1 0 0 1 0 1 Minimum Airspeed X
0 3 3 0 0 1 0 0 1 1 0 Engine Serial No. (LSDs) X 6-15
0 4 6 1 0 A 0 0 1 0 0 1 1 0 Engine Serial No. (LSDs) X 6-15
1 0 B 0 0 1 0 0 1 1 0 Engine Serial No. (LSDs) X 6-15
0 2 0 0 0 1 0 0 1 1 1 VHF COM Frequency X
0 2 4 0 0 1 0 0 1 1 1 VHF COM Frequency X
0 3 3 0 0 1 0 0 1 1 1 Engine Serial No. (MSDs) X 6-16
0 4 7
0 B 6 0 0 1 0 0 1 1 1 VHF COM Frequency X
1 0 A 0 0 1 0 0 1 1 1 Engine Serial No. (MSDs) X 6-16
1 0 B 0 0 1 0 0 1 1 1 Engine Serial No. (MSDs) X 6-16
0 5 0 0 0 0 1 0 1 0 0 0 Spare
0 5 1 0 0 0 1 0 1 0 0 1 Spare
0 0 4 0 0 1 0 1 0 1 0 Body Pitch Acceleration X
0 5 2 0 3 7 0 0 1 0 1 0 1 0 Longitude Zero Fuel CG X
0 3 8 0 0 1 0 1 0 1 0 Body Pitch Acceleration X
0 0 4 0 0 1 0 1 0 1 1 Body Roll Acceleration X
0 5 3 0 0 5 0 0 1 0 1 0 1 1 Track Angle - Magnetic X
0 3 8 0 0 1 0 1 0 1 1 Body Roll Acceleration X
0 0 4 0 0 1 0 1 1 0 0 Body Yaw Acceleration X
0 5 4 0 3 7 0 0 1 0 1 1 0 0 Zero Fuel Weight (KG) X
0 3 8 0 0 1 0 1 1 0 0 Body Yaw Acceleration X
0 5 5 0 0 0 1 0 1 1 0 1 Spare
0 0 2 0 0 1 0 1 1 1 0 Estimated Time of Arrival X
0 0 5 0 0 1 0 1 1 1 0 Wind Direction - Magnetic X
0 5 6 0 3 7 0 0 1 0 1 1 1 0 Gross Weight (KG) X
0 5 6 0 0 1 0 1 1 1 0 ETA (Active Waypoint) X
0 6 0 0 0 1 0 1 1 1 0 ETA (Active Waypoint) X
0 5 7 0 0 0 1 0 1 1 1 1 Spare
0 2 5 0 0 1 1 0 0 0 0 S/G Hardware Part No X 6-36
0 6 0 0 3 7 0 0 1 1 0 0 0 0 Tire Loading (Left Body Main) X
0 3 C 0 0 1 1 0 0 0 0 Tire Pressure (Left Inner) X
0 0 2 0 0 1 1 0 0 0 1 ACMS Information X 6-29
0 0 B 0 0 1 1 0 0 0 1 Pseudo Range X
0 2 5 0 0 1 1 0 0 0 1 S/G Hardware Part No X 6-37
0 6 1 0 3 7 0 0 1 1 0 0 0 1 Tire Loading (Right Body Main) X
0 3 C 0 0 1 1 0 0 0 1 Tire Pressure (Left Outer) X
0 5 6 0 0 1 1 0 0 0 1 ACMS Information X
0 6 0 0 0 1 1 0 0 0 1 ACMS Information X
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 16
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 2 0 0 1 1 0 0 1 0 ACMS Information X 6-29

0 0 B 0 0 1 1 0 0 1 0 Pseudo Range Fine X
0 3 7 0 0 1 1 0 0 1 0 Tire Loading (Left Wing Main) X
0 6 2
0 3 C 0 0 1 1 0 0 1 0 Tire Pressure (Right Inner) X
0 5 6 0 0 1 1 0 0 1 0 ACMS Information X
0 6 0 0 0 1 1 0 0 1 0 ACMS Information X
0 0 2 0 0 1 1 0 0 1 1 ACMS Information X 6-29
0 0 B 0 0 1 1 0 0 1 1 Range Rate X
0 3 7 0 0 1 1 0 0 1 1 Tire Loading (Right Wing Main) X
0 6 3
0 3 C 0 0 1 1 0 0 1 1 Tire Pressure (Right Outer) X
0 5 6 0 0 1 1 0 0 1 1 ACMS Information X
0 6 0 0 0 1 1 0 0 1 1 ACMS Information X
0 0 B 0 0 1 1 0 1 0 0 Delta Range X
0 6 4 0 3 7 0 0 1 1 0 1 0 0 Tire Loading (Nose) X
0 3 C 0 0 1 1 0 1 0 0 Tire Pressure (Nose) X
0 0 3 0 0 1 1 0 1 0 1 Gross Weight X
0 6 5 0 0 B 0 0 1 1 0 1 0 1 SV Position X X
0 3 7 0 0 1 1 0 1 0 1 Gross Weight X
0 0 2 0 0 1 1 0 1 1 0 Longitudinal Center of Gravity X
0 6 6 0 0 B 0 0 1 1 0 1 1 0 SV Position X Fine X
0 3 7 0 0 1 1 0 1 1 0 Longitudinal Center of Gravity X
0 6 7 0 3 7 0 0 1 1 0 1 1 1 Lateral Center of Gravity X
0 0 2 0 0 1 1 1 0 0 0 Reference Airspeed (Vref) X
0 0 B 0 0 1 1 1 0 0 0 SV Position Y X
0 2 9 0 0 1 1 1 0 0 0 AC Frequency (Engine) X
0 7 0 0 3 7 0 0 1 1 1 0 0 0 Hard landing Magnitude #1 X
0 5 6 0 0 1 1 1 0 0 0 Reference Airspeed (Vref) X
0 6 0 0 0 1 1 1 0 0 0 Reference Airspeed (Vref) X
0 C C 0 0 1 1 1 0 0 0 Brakes - Metered Hydraulic Pressure L (Normal) X
0 0 2 0 0 1 1 1 0 0 1 Take-Off Climb Airspeed (V2) X
0 0 B 0 0 1 1 1 0 0 1 SV Position Y Fine X
0 2 9 0 0 1 1 1 0 0 1 AC Frequency (Alt. Sources) X
0 7 1
0 3 3 0 0 1 1 1 0 0 1 VBV X
0 3 7 0 0 1 1 1 0 0 1 Hard Landing Magnitude #2 X
0 C C 0 0 1 1 1 0 0 1 Brakes - Metered Hydraulic Pressure L (Alt) X
0 0 2 0 0 1 1 1 0 1 0 VR (Rotation Speed) X
0 0 B 0 0 1 1 1 0 1 0 SV Position Z X
0 1 C 0 0 1 1 1 0 1 0 Stator Vane Angle X
0 7 2 0 2 9 0 0 1 1 1 0 1 0 AC Voltage (Engine) X
0 2 F 0 0 1 1 1 0 1 0 Stator Vane Angle X
0 3 3 0 0 1 1 1 0 1 0 Stator Vane Angle X
0 C C 0 0 1 1 1 0 1 0 Brakes - Metered Hydraulic Pressure R (Normal) X
0 0 2 0 0 1 1 1 0 1 1 V1 (Critical Engine Failure Speed) X
0 0 B 0 0 1 1 1 0 1 1 SV Position Z Fine X
0 1 C 0 0 1 1 1 0 1 1 Oil Quantity X
0 7 3 0 2 9 0 0 1 1 1 0 1 1 Oil Quantity X
0 A 2 0 0 1 1 1 0 1 1 V2 (Critical Engine Failure Speed) X
0 C C 0 0 1 1 1 0 1 1 Brakes - Metered Hydraulic Pressure R (Alt.) X
0 D 0 0 0 1 1 1 0 1 1 Engine Oil Quantity X
0 0 2 0 0 1 1 1 1 0 0 Zero Fuel Weight X
0 0 B 0 0 1 1 1 1 0 0 UTC Measure Time X
0 2 C 0 0 1 1 1 1 0 0 Zero Fuel Weight X
0 3 3 0 0 1 1 1 1 0 0 LP Compressor Bleed Position (3.0) X
0 7 4
0 3 7 0 0 1 1 1 1 0 0 Zero Fuel Weight (lb) X
0 5 6 0 0 1 1 1 1 0 0 Zero Fuel Weight X
0 6 0 0 0 1 1 1 1 0 0 Zero Fuel Weight X
1 1 4 0 0 1 1 1 1 0 0 Zero Fuel Weight X
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 17
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 2 0 0 1 1 1 1 0 1 Gross Weight X
0 0 3 0 0 1 1 1 1 0 1 Gross Weight X
0 0 8 0 0 1 1 1 1 0 1 Maximum Hazard Alert Level Output X
0 0 B 0 0 1 1 1 1 0 1 Geodetic Altitude X
0 7 5 0 2 9 0 0 1 1 1 1 0 1 AC Voltage (Alt. Sources) X
0 2 C 0 0 1 1 1 1 0 1 Gross Weight X
0 3 7 0 0 1 1 1 1 0 1 Gross Weight X
0 3 E 0 0 1 1 1 1 0 1 Gross Weight X
1 1 4 0 0 1 1 1 1 0 1 Aircraft Gross Weight X
0 0 8 0 0 1 1 1 1 1 0 Hazard Azimuth Output X
0 0 B 0 0 1 1 1 1 1 0 GNSS Altitude (MSL) X
0 2 9 0 0 1 1 1 1 1 0 AC Voltage (Bus Bar) X
0 7 6
0 3 7 0 0 1 1 1 1 1 0 Longitudinal Center of Gravity X
0 3 E 0 0 1 1 1 1 1 0 Longitudinal Center of Gravity X
1 1 4 0 0 1 1 1 1 1 0 Aircraft Longitudinal Center of Gravity X
0 0 2 0 0 1 1 1 1 1 1 Target Airspeed X
0 0 8 0 0 1 1 1 1 1 1 Hazard Azimuth Output X
0 0 B 0 0 1 1 1 1 1 1 GPS Hor/Vert Deviation X
0 2 9 0 0 1 1 1 1 1 1 AC Load (Engine) X
0 7 7
0 3 7 0 0 1 1 1 1 1 1 Lateral Center of Gravity X
0 5 6 0 0 1 1 1 1 1 1 Target Airspeed X
0 6 0 0 0 1 1 1 1 1 1 Target Airspeed X
1 1 4 0 0 1 1 1 1 1 1 Zero Fuel Center of Gravity X
0 0 1 0 1 0 0 0 0 0 0 Selected Course #1 X 6-27
0 0 2 0 1 0 0 0 0 0 0 Selected Course #1 X
0 1 1 0 1 0 0 0 0 0 0 Selected Course #1 X
0 2 0 0 1 0 0 0 0 0 0 Selected Course #1 X
0 2 9 0 1 0 0 0 0 0 0 AC Load (Alt. Source) X
1 0 0 0 3 7 0 1 0 0 0 0 0 0 Gross Weight (Kilogram) X
0 5 6 0 1 0 0 0 0 0 0 Selected Course #1 X
0 6 0 0 1 0 0 0 0 0 0 Selected Course #1 X
0 A 1 0 1 0 0 0 0 0 0 Selected Course #1 X
0 B 1 0 1 0 0 0 0 0 0 Selected Course #1 X
0 B B 0 1 0 0 0 0 0 0 Outbound Flaps - PDU X
0 0 2 0 1 0 0 0 0 0 1 Selected Heading X 6-27
0 0 B 0 1 0 0 0 0 0 1 HDOP X
0 2 0 0 1 0 0 0 0 0 1 Selected Heading X
0 2 5 0 1 0 0 0 0 0 1 Selected Heading X
1 0 1
0 2 9 0 1 0 0 0 0 0 1 DC Current (TRU) X
0 A 1 0 1 0 0 0 0 0 1 Selected Heading X
0 B B 0 1 0 0 0 0 0 1 Inboard Flaps - PDU X
1 1 4 0 1 0 0 0 0 0 1 C/G Target X
0 0 2 0 1 0 0 0 0 1 0 Selected Altitude X 6-27
0 0 B 0 1 0 0 0 0 1 0 VDOP X
0 2 0 0 1 0 0 0 0 1 0 Selected Altitude X
1 0 2 0 2 9 0 1 0 0 0 0 1 0 DC Current (Battery) X
0 5 6 0 1 0 0 0 0 1 0 Selected Altitude X
0 6 0 0 1 0 0 0 0 1 0 Selected Altitude X
0 A 1 0 1 0 0 0 0 1 0 Selected Altitude X
0 0 1 0 1 0 0 0 0 1 1 Selected Airspeed X 6-27
0 0 2 0 1 0 0 0 0 1 1 Selected Airspeed X
0 0 3 0 1 0 0 0 0 1 1 Selected Airspeed X
0 0 B 0 1 0 0 0 0 1 1 GNSS Track Angle X
0 1 B 0 1 0 0 0 0 1 1 Left/PDU Flap X
1 0 3 0 2 0 0 1 0 0 0 0 1 1 Selected Airspeed X
0 2 9 0 1 0 0 0 0 1 1 DC Voltage (TRU) X
0 5 6 0 1 0 0 0 0 1 1 Selected Airspeed X
0 6 0 0 1 0 0 0 0 1 1 Selected Airspeed X
0 A 1 0 1 0 0 0 0 1 1 Selected Airspeed X
0 B B 0 1 0 0 0 0 1 1 Left Outboard Flap Position X
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 18
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 1 0 1 0 0 0 1 0 0 Selected Vertical Speed X 6-27

0 0 2 0 1 0 0 0 1 0 0 Selected Vertical Speed X
0 1 B 0 1 0 0 0 1 0 0 Right/PDU Flap X
0 2 0 0 1 0 0 0 1 0 0 Selected Vertical Speed X
0 2 9 0 1 0 0 0 1 0 0 DC Voltage (Battery) X
1 0 4
0 2 B 0 1 0 0 0 1 0 0 Selected Vertical Speed X
0 5 6 0 1 0 0 0 1 0 0 Selected Vertical Speed X
0 6 0 0 1 0 0 0 1 0 0 Selected Vertical Speed X
0 A 1 0 1 0 0 0 1 0 0 Selected Vertical Speed X
0 B B 0 1 0 0 0 1 0 0 Right Outboard Flap Position X
0 0 2 0 1 0 0 0 1 0 1 Selected Runway Heading X
0 1 0 0 1 0 0 0 1 0 1 Selected Runway Heading X
0 1 B 0 1 0 0 0 1 0 1 Left/PDU Slat X
0 2 0 0 1 0 0 0 1 0 1 Selected Runway Heading X
0 2 9 0 1 0 0 0 1 0 1 Oil Temperature Input (IDG/CSD) X
1 0 5 0 5 5 0 1 0 0 0 1 0 1 Selected Runway Heading X
0 5 6 0 1 0 0 0 1 0 1 Selected Runway Heading X
0 6 0 0 1 0 0 0 1 0 1 Selected Runway Heading X
0 A 1 0 1 0 0 0 1 0 1 Selected Runway Heading X
0 B 0 0 1 0 0 0 1 0 1 Selected Runway Heading X
0 B B 0 1 0 0 0 1 0 1 Left Inboard Flap Position X
0 0 2 0 1 0 0 0 1 1 0 Selected Mach X 6-27
0 1 B 0 1 0 0 0 1 1 0 Right/PDU Slat X
0 2 0 0 1 0 0 0 1 1 0 Selected Mach X
0 2 9 0 1 0 0 0 1 1 0 Oil Temperature Input (IDG/CSD) X
1 0 6
0 5 6 0 1 0 0 0 1 1 0 Selected Mach X
0 6 0 0 1 0 0 0 1 1 0 Selected Mach X
0 A 1 0 1 0 0 0 1 1 0 Selected Mach X
0 B B 0 1 0 0 0 1 1 0 Right Inboard Flap Position X
0 0 2 0 1 0 0 0 1 1 1 Selected Cruise Altitude X
0 1 B 0 1 0 0 0 1 1 1 Flap/Slat Lever X
0 3 7 0 1 0 0 0 1 1 1 Longitude Zero Fuel C/G X
1 0 7
0 5 6 0 1 0 0 0 1 1 1 Selected Cruise Altitude X
0 6 0 0 1 0 0 0 1 1 1 Selected Cruise Altitude X
0 B B 0 1 0 0 0 1 1 1 Flap Lever Position - Median Value X
0 0 1 0 1 0 0 1 0 0 0 Selected Course #2 X
0 0 2 0 1 0 0 1 0 0 0 Selected Course #2 X
0 0 B 0 1 0 0 1 0 0 0 GNSS Latitude X
0 1 0 0 1 0 0 1 0 0 0 Selected Course #2 X
1 1 0 0 1 1 0 1 0 0 1 0 0 0 Selected Course #2 X
0 2 0 0 1 0 0 1 0 0 0 Selected Course #2 X
0 A 1 0 1 0 0 1 0 0 0 Selected Course #2 X
0 B 1 0 1 0 0 1 0 0 0 Selected Course #2 X
0 B B 0 1 0 0 1 0 0 0 Flap Lever Position - Center X
0 0 1 0 1 0 0 1 0 0 1 Test Word A X
1 1 1 0 0 B 0 1 0 0 1 0 0 1 GNSS Longitude X
0 1 D 0 1 0 0 1 0 0 1 Test Word A X
0 0 2 0 1 0 0 1 0 1 0 Runway Length X
0 0 B 0 1 0 0 1 0 1 0 GNSS Ground Speed X
1 1 2 0 A 1 0 1 0 0 1 0 1 0 Selected EPR X
0 A 1 0 1 0 0 1 0 1 0 Selected N1 X
0 B B 0 1 0 0 1 0 1 0 Flap Lever Position - Left
1 1 3 0 0 1 0 0 1 0 1 1 Spare
0 0 2 0 1 0 0 1 1 0 0 Desired Track X 6-27
0 2 9 0 1 0 0 1 1 0 0 Brake Temperature (Left Inner L/G) X
0 2 F 0 1 0 0 1 1 0 0 Ambient Pressure X
0 3 F 0 1 0 0 1 1 0 0 Pamb Sensor X
0 5 6 0 1 0 0 1 1 0 0 Desired Track X
1 1 4 0 6 0 0 1 0 0 1 1 0 0 Desired Track X
0 B B 0 1 0 0 1 1 0 0 Flap Lever Position - Right X
0 C C 0 1 0 0 1 1 0 0 Wheel Torque Output X
1 0 A 0 1 0 0 1 1 0 0 Selected Ambient Static Pressure X
1 0 B 0 1 0 0 1 1 0 0 Selected Ambient Static Pressure X
1 3 A 0 1 0 0 1 1 0 0 Ambient Pressure X
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 19
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 2 0 1 0 0 1 1 0 1 Waypoint Bearing X
0 2 9 0 1 0 0 1 1 0 1 Brake Temperature (Left Outer L/G) X
0 2 F 0 1 0 0 1 1 0 1 Fuel Temperature X
0 3 F 0 1 0 0 1 1 0 1 Fuel Temperature X
1 1 5
0 5 6 0 1 0 0 1 1 0 1 Waypoint Bearing X
0 6 0 0 1 0 0 1 1 0 1 Waypoint Bearing X
0 B C 0 1 0 0 1 1 0 1 Fuel Temperature X
0 C C 0 1 0 0 1 1 0 1 Wheel Torque Output X 6-26
0 0 2 0 1 0 0 1 1 1 0 Cross Track Distance X 6-27
0 0 B 0 1 0 0 1 1 1 0 Horizontal GLS Deviation Rectilinear X
0 2 9 0 1 0 0 1 1 1 0 Brake Temperature (Right Inner L/G) X
1 1 6 0 5 5 0 1 0 0 1 1 1 0 Horizontal GLS Deviation Rectilinear X
0 5 6 0 1 0 0 1 1 1 0 Cross Track Distance X
0 6 0 0 1 0 0 1 1 1 0 Cross Track Distance X
0 C C 0 1 0 0 1 1 1 0 Wheel Torque Output X 6-26
0 0 2 0 1 0 0 1 1 1 1 Vertical Deviation X 6-27
0 0 B 0 1 0 0 1 1 1 1 Vertical GLS Deviation Rectilinear X
0 2 9 0 1 0 0 1 1 1 1 Brake Temperature (Right Inner L/G) X
1 1 7 0 5 5 0 1 0 0 1 1 1 1 Vertical GLS Deviation Rectilinear X
0 5 6 0 1 0 0 1 1 1 1 Vertical Deviation X
0 6 0 0 1 0 0 1 1 1 1 Vertical Deviation X
0 C C 0 1 0 0 1 1 1 1 Wheel Torque Output X 6-26
0 0 2 0 1 0 1 0 0 0 0 Range to Altitude X
0 0 B 0 1 0 1 0 0 0 0 GNSS Latitude Fine X
1 2 0 0 2 9 0 1 0 1 0 0 0 0 Pack Bypass Turbine Position X
0 5 6 0 1 0 1 0 0 0 0 Range to Altitude X
0 6 0 0 1 0 1 0 0 0 0 Range to Altitude X
0 0 2 0 1 0 1 0 0 0 1 Horizontal Command Signal X
0 0 B 0 1 0 1 0 0 0 1 GNSS Longitude Fine X
0 2 5 0 1 0 1 0 0 0 1 Pitch Limit X
1 2 1
0 2 9 0 1 0 1 0 0 0 1 Pack Outlet Temperature X
0 5 6 0 1 0 1 0 0 0 1 Horizontal Command Signal X
0 6 0 0 1 0 1 0 0 0 1 Horizontal Command Signal X
0 0 2 0 1 0 1 0 0 1 0 Vertical Command Signal X
0 2 9 0 1 0 1 0 0 1 0 Pack Turbine Inlet Temperature X
1 2 2
0 5 6 0 1 0 1 0 0 1 0 Vertical Command Signal X
0 6 0 0 1 0 1 0 0 1 0 Vertical Command Signal X
1 2 3 0 0 2 0 1 0 1 0 0 1 1 Throttle Command X
1 2 4 0 0 B 0 1 0 1 0 1 0 0 Digital Time Mark X
0 0 2 0 1 0 1 0 1 0 1 Universal Time Coordinated (UTC) X 6-25
0 0 B 0 1 0 1 0 1 0 1 Universal Time Coordinated (UTC) X
1 2 5 0 3 1 0 1 0 1 0 1 0 1 Universal Time Coordinated (UTC) X 6-25
0 5 6 0 1 0 1 0 1 0 1 Universal Time Coordinated (UTC) X
0 6 0 0 1 0 1 0 1 0 1 Universal Time Coordinated (UTC) X
0 0 2 0 1 0 1 0 1 1 0 Vertical Deviation (wide) X
0 2 6 0 1 0 1 0 1 1 0 FWC Word X
1 2 6 0 2 9 0 1 0 1 0 1 1 0 Pack Flow X
0 5 6 0 1 0 1 0 1 1 0 Vertical Deviation (Wide) X
0 6 0 0 1 0 1 0 1 1 0 Vertical Deviation (Wide) X
0 0 2 0 1 0 1 0 1 1 1 Selected Landing Altitude X
0 1 B 0 1 0 1 0 1 1 1 Slat Angle X 6-11
1 2 7 0 3 3 0 1 0 1 0 1 1 1 P14 X
1 0 A 0 1 0 1 0 1 1 1 Fan Discharge Static Pressure X
1 0 B 0 1 0 1 0 1 1 1 Fan Discharge Static Pressure X
0 0 B 0 1 0 1 1 0 0 0 Aut Horiz Integ Limit X
0 1 A 0 1 0 1 1 0 0 0 Fan Inlet Total Temperature X
0 1 C 0 1 0 1 1 0 0 0 Fan Inlet Total Temperature X
0 2 F 0 1 0 1 1 0 0 0 Fan Inlet Total Temperature X
1 3 0 0 3 5 0 1 0 1 1 0 0 0 Intruder Range X 6-21
0 3 F 0 1 0 1 1 0 0 0 Fan Inlet Total Temperature X
1 0 A 0 1 0 1 1 0 0 0 Selected Total Air Temperature X
1 0 B 0 1 0 1 1 0 0 0 Selected Total Air Temperature X
1 3 A 0 1 0 1 1 0 0 0 Inlet Temperature X
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 20
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 1 A 0 1 0 1 1 0 0 1 Fan Inlet Total Pressure X

0 1 C 0 1 0 1 1 0 0 1 Fan Inlet Total Pressure X
0 2 D 0 1 0 1 1 0 0 1 Fan Inlet Total Pressure X
1 3 1 0 2 F 0 1 0 1 1 0 0 1 Fan Inlet Total Pressure X
0 3 3 0 1 0 1 1 0 0 1 Fan Inlet Total Pressure X
0 3 5 0 1 0 1 1 0 0 1 Intruder Altitude X 6-22
1 3 A 0 1 0 1 1 0 0 1 Inlet Pressure X
0 1 A 0 1 0 1 1 0 1 0 Exhaust Gas Total Pressure X
0 1 C 0 1 0 1 1 0 1 0 Exhaust Gas Total Pressure X
1 3 2
0 3 3 0 1 0 1 1 0 1 0 Exhaust Gas Total Pressure X
0 3 5 0 1 0 1 1 0 1 0 Intruder Bearing X 6-23
0 0 B 0 1 0 1 1 0 1 1 Aut Horiz Integ Limit X
0 1 A 0 1 0 1 1 0 1 1 Thrust Lever Angle X
0 2 F 0 1 0 1 1 0 1 1 Thrust Lever Angle X
1 3 3
0 3 F 0 1 0 1 1 0 1 1 Thrust Lever Angle X
1 0 A 0 1 0 1 1 0 1 1 Selected Throttle Lever Angle X
1 0 B 0 1 0 1 1 0 1 1 Selected Throttle Lever Angle X
0 1 C 0 1 0 1 1 1 0 0 Power Lever Angle X
1 0 A 0 1 0 1 1 1 0 0 Throttle Lever Angle X
1 3 4
1 0 B 0 1 0 1 1 1 0 0 Throttle Lever Angle X
1 3 A 0 1 0 1 1 1 0 0 Throttle Lever Angle X
0 1 C 0 1 0 1 1 1 0 1 Engine Vibration #1 X
1 3 5 0 2 9 0 1 0 1 1 1 0 1 Engine Fan Vibration X
0 5 A 0 1 0 1 1 1 0 1 ACT 1 Fuel Quantity Display X
0 0 B 0 1 0 1 1 1 1 0 Vertical Figure of Merit X
0 1 C 0 1 0 1 1 1 1 0 Engine Vibration #2 X
1 3 6
0 2 9 0 1 0 1 1 1 1 0 Engine Turbine Vibration X
0 5 A 0 1 0 1 1 1 1 0 ACT 2 Fuel Quantity Display X
0 1 B 0 1 0 1 1 1 1 1 Flap Angle X 6-11
0 2 A 0 1 0 1 1 1 1 1 Flap Angle X 6-11
0 2 F 0 1 0 1 1 1 1 1 Thrust Reverser Position Feedback X
0 3 F 0 1 0 1 1 1 1 1 Thrust Reverser Position Feedback X
1 3 7
0 5 A 0 1 0 1 1 1 1 1 Center+ACT1+ACT2 FQ Display X
1 0 A 0 1 0 1 1 1 1 1 Selected Thrust Reverser Position X
1 0 B 0 1 0 1 1 1 1 1 Selected Thrust Reverser Position X
1 4 0 0 1 0 1 1 1 1 1 Flap Angle X 6-11
0 0 1 0 1 1 0 0 0 0 0 Flight Director - Roll X 6-27
0 0 B 0 1 1 0 0 0 0 0 UTC Fine X
0 2 5 0 1 1 0 0 0 0 0 Flight Director - Roll X
1 4 0
0 2 9 0 1 1 0 0 0 0 0 Precooler Output Temperature X
0 5 A 0 1 1 0 0 0 0 0 Actual Fuel Quantity Display X
1 1 4 0 1 1 0 0 0 0 0 Pump Contactor States X
0 0 1 0 1 1 0 0 0 0 1 Flight Director - Pitch X 6-27
0 0 B 0 1 1 0 0 0 0 1 UTC Fine Fractions X
0 2 5 0 1 1 0 0 0 0 1 Flight Director - Pitch X
1 4 1
0 2 9 0 1 1 0 0 0 0 1 Precooler Input Temperature X
0 5 A 0 1 1 0 0 0 0 1 Preselected Fuel Quantity Display X
1 1 4 0 1 1 0 0 0 0 1 Pump Contactor and Pushbutton States X
0 0 2 0 1 1 0 0 0 1 0 Flight Director - Fast/Slow X 6-27
0 0 3 0 1 1 0 0 0 1 0 Flight Director - Fast/Slow X
1 4 2 0 2 5 0 1 1 0 0 0 1 0 Flight Director - Fast/Slow X
0 5 A 0 1 1 0 0 0 1 0 Left Wing Fuel Quantity Display X
1 1 4 0 1 1 0 0 0 1 0 Pump Push Button and LP Switch State X
0 0 1 0 1 1 0 0 0 1 1 Flight Director - Yaw X
0 4 1 0 1 1 0 0 0 1 1 HPA Command Word X
1 4 3 0 5 A 0 1 1 0 0 0 1 1 Center Wing Fuel Quantity Display X
1 1 4 0 1 1 0 0 0 1 1 Pump LP Switch State and FCMC Commands X
2 4 1 0 1 1 0 0 0 1 1 HPA Response Word X
0 2 B 0 1 1 0 0 1 0 0 Altitude Error X
0 4 1 0 1 1 0 0 1 0 0 ACU/BSU Contorl Word X
1 4 4 0 5 A 0 1 1 0 0 1 0 0 Right Wing Fuel Quantity Display X
1 1 4 0 1 1 0 0 1 0 0 Valve Feedback X
3 4 1 0 1 1 0 0 1 0 0 ACU/BSU Contorl Word X
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 21
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 2 0 1 1 0 0 1 0 1 TACAN Control X 6-30

0 2 5 0 1 1 0 0 1 0 1 Discrete Status 2 EFIS X
1 4 5 0 2 9 0 1 1 0 0 1 0 1 Discrete Status 2 EFIS X
0 A 1 0 1 1 0 0 1 0 1 AFS DFDR Discretes #1 X
1 1 4 0 1 1 0 0 1 0 1 Valve Feedback X
0 2 5 0 1 1 0 0 1 1 0 Discrete Status 3 EFIS X
0 2 9 0 1 1 0 0 1 1 0 Discrete Data #9 X
1 4 6 0 A 1 0 1 1 0 0 1 1 0 AFS DFDR Discretes #2 X
1 1 2 0 1 1 0 0 1 1 0 TACAN Control X 6-47
1 1 4 0 1 1 0 0 1 1 0 Valve Feedback X
0 2 5 0 1 1 0 0 1 1 1 Discrete Status 4 EFIS X
0 2 9 0 1 1 0 0 1 1 1 Discrete Data #10 X
1 4 7 0 A 1 0 1 1 0 0 1 1 1 AFS DFDR Discretes #3 X
1 1 4 0 1 1 0 0 1 1 1 Valve Feedback X
X X X 0 1 1 0 0 1 1 1 TACAN Control Word X 6-48/Note 1
0 0 2 0 1 1 0 1 0 0 0 Universal Time Constant (UTC) X 6-12/6-27
0 0 B 0 1 1 0 1 0 0 0 Universal Time Constant (UTC) X
0 2 9 0 1 1 0 1 0 0 0 Cabin Altitude Rate X
1 5 0 0 3 1 0 1 1 0 1 0 0 0 Universal Time Constant (UTC) X 6-12/6-27
0 5 6 0 1 1 0 1 0 0 0 Universal Coordinated Time X
0 6 0 0 1 1 0 1 0 0 0 Universal Coordinated Time X
1 1 4 0 1 1 0 1 0 0 0 FCMC Valve Commands X
0 0 2 0 1 1 0 1 0 0 1 Localizer Bearing (True) X
0 2 7 0 1 1 0 1 0 0 1 MLS Azimuth Deviation X
0 2 9 0 1 1 0 1 0 0 1 Cabin Altitude X
0 5 5 0 1 1 0 1 0 0 1 MLS Azimuth Deviation X
1 5 1
0 5 6 0 1 1 0 1 0 0 1 Localizer Bearing (True) X
0 5 A 0 1 1 0 1 0 0 1 LB/KG Control Word X
0 6 0 0 1 1 0 1 0 0 1 Localizer Bearing (True) X
1 1 4 0 1 1 0 1 0 0 1 FCMC Valve Commands X
0 2 7 0 1 1 0 1 0 1 0 MLS Elevation Deviation X
0 2 9 0 1 1 0 1 0 1 0 Cabin Pressure X
0 4 1 0 1 1 0 1 0 1 0 Open Loop Steering X
1 5 2 0 5 5 0 1 1 0 1 0 1 0 MLS GP Deviation X
Overhead Panel Switch/Pushbutton & Refuel Panel Battery
1 1 4 0 1 1 0 1 0 1 0 X
Power Supply Switch States
0 1 1 0 1 0 1 0 777 Cabin Interphone System - System Address Label X See Attachment 11
0 0 2 0 1 1 0 1 0 1 1 Maximum Altitude X
0 2 7 0 1 1 0 1 0 1 1 Flare X
0 2 9 0 1 1 0 1 0 1 1 Pressurization Valve Position (Gr. #1) X
1 5 3
0 4 1 0 1 1 0 1 0 1 1 Closed Loop Steering X
0 5 5 0 1 1 0 1 0 1 1 MLS Selected Azimuth X
1 1 4 0 1 1 0 1 0 1 1 Level States X
0 0 2 0 1 1 0 1 1 0 0 Runway Heading (True) X
0 2 7 0 1 1 0 1 1 0 0 MLS Auxilliary Data X
0 2 9 0 1 1 0 1 1 0 0 Pressurization Valve Position (Gr. #2) X
1 5 4 0 5 5 0 1 1 0 1 1 0 0 MLS Max Selectable GP X
0 5 6 0 1 1 0 1 1 0 0 Runway Heading (True) X
0 6 0 0 1 1 0 1 1 0 0 Runway Heading (True) X
1 1 4 0 1 1 0 1 1 0 0 Level States and Low Warning and Transfer Indications X
0 1 C 0 1 1 0 1 1 0 1 Maintenance Data #6 X
0 2 5 0 1 1 0 1 1 0 1 Discrete Status 5 EFIS X
0 2 7 0 1 1 0 1 1 0 1 MLS Selected GP Angle X
0 2 9 0 1 1 0 1 1 0 1 Discrete #1 X
0 3 3 0 1 1 0 1 1 0 1 Maintenance Data #6 X
1 5 5
0 5 5 0 1 1 0 1 1 0 1 MLS Selected Glide Path X
0 B B 0 1 1 0 1 1 0 1 Maintenance Data #6 X
1 0 A 0 1 1 0 1 1 0 1 Maintenance Data #6 X
1 0 B 0 1 1 0 1 1 0 1 Maintenance Data #6 X
1 1 4 0 1 1 0 1 1 0 1 XFR Pump Faults & Wing Imbalance Warning X
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 22
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 1 C 0 1 1 0 1 1 1 0 Maintnance Data #7 X
0 2 7 0 1 1 0 1 1 1 0 MLS Dataword 1 X
0 2 9 0 1 1 0 1 1 1 0 Discrete #12 X
0 3 3 0 1 1 0 1 1 1 0 Maintenance Data #7 X
0 4 D 0 1 1 0 1 1 1 0 L Tank Faults X
1 5 6
0 5 5 0 1 1 0 1 1 1 0 MLS Basic Data Wd 1 X
0 B B 0 1 1 0 1 1 1 0 Maintenance Data #7 X
1 0 A 0 1 1 0 1 1 1 0 Maintenance Data #7 X
1 0 B 0 1 1 0 1 1 1 0 Maintenance Data #7 X
1 1 4 0 1 1 0 1 1 1 0 Refuel Panel Switch States X
0 1 1 0 1 1 1 1 System Address Label for CVR X See Attachment 11
0 1 C 0 1 1 0 1 1 1 1 Maintenance Data #8 X
0 2 7 0 1 1 0 1 1 1 1 MLS Dataword 2 X
0 3 3 0 1 1 0 1 1 1 1 Maintenance Data #8 X
0 4 D 0 1 1 0 1 1 1 1 R Tank Faults X
1 5 7
0 5 5 0 1 1 0 1 1 1 1 MLS Basic Data Wd 2 X
0 B B 0 1 1 0 1 1 1 1 Maintenance Data #8 X
1 0 A 0 1 1 0 1 1 1 1 Maintenance Data #8 X
1 0 B 0 1 1 0 1 1 1 1 Maintenance Data #8 X
1 1 4 0 1 1 0 1 1 1 1 Trim Tank Probe Capacitance X
0 1 C 0 1 1 1 0 0 0 0 Maintenance Data #9 X
0 2 5 0 1 1 1 0 0 0 0 Discrete Status 6 EFIS X
0 2 7 0 1 1 1 0 0 0 0 MLS Dataword 3 X
0 3 3 0 1 1 1 0 0 0 0 Maintenance Data #9 X
0 4 D 0 1 1 1 0 0 0 0 C Tank Faults X
1 6 0
0 5 5 0 1 1 1 0 0 0 0 MLS Basic Data Wd 3 X
0 B B 0 1 1 1 0 0 0 0 Maintenance Data #9 X
1 0 A 0 1 1 1 0 0 0 0 Maintenance Data #9 X
1 0 B 0 1 1 1 0 0 0 0 Maintenance Data #9 X
1 1 4 0 1 1 1 0 0 0 0 Valve Feedback X
0 1 C 0 1 1 1 0 0 0 1 Maintenance Data #10 X
0 2 5 0 1 1 1 0 0 0 1 Discrete Status 7 EFIS X
0 2 7 0 1 1 1 0 0 0 1 MLS Dataword 4 X
0 3 3 0 1 1 1 0 0 0 1 Maintenance Data #10 X
1 6 1 0 4 D 0 1 1 1 0 0 0 1 A Tank Faults X
0 5 5 0 1 1 1 0 0 0 1 MLS Basic Data Wd 4 X
1 0 A 0 1 1 1 0 0 0 1 Maintenance Data #10 X
1 0 B 0 1 1 1 0 0 0 1 Maintenance Data #10 X
1 1 4 0 1 1 1 0 0 0 1 Indicated Pump Status X
0 1 2 0 1 1 1 0 0 1 0 ADF Bearing X
0 2 5 0 1 1 1 0 0 1 0 ADF Bearing Left/Right X
0 2 7 0 1 1 1 0 0 1 0 MLS Dataword 5 X
0 2 9 0 1 1 1 0 0 1 0 Crew Oxygen Pressure X
1 6 2
0 5 5 0 1 1 1 0 0 1 0 MLS Basic Data Wd 5 X
0 D E 0 1 1 1 0 0 1 0 Stick Shaker Margin Proportional Signal X
1 1 4 0 1 1 1 0 0 1 0 Indicated Pump Status X
1 4 0 0 1 1 1 0 0 1 0 Density Altitude X
0 2 7 0 1 1 1 0 0 1 1 MLS Dataword 6 X
0 3 7 0 1 1 1 0 0 1 1 Zero Fuel Weight (lb) X
1 6 3 0 5 5 0 1 1 1 0 0 1 1 MLS Basic Data Wd 6 X
1 1 4 0 1 1 1 0 0 1 1 Indicated Pump Status X
0 1 1 1 0 0 1 1 747 DFDR & A330/340 SSFDR - System Address Label X See Attachment 11
0 0 2 0 1 1 1 0 1 0 0 Minimum Descent Altitude (MDA) X
0 0 3 0 1 1 1 0 1 0 0 Target Height X
0 0 7 0 1 1 1 0 1 0 0 Radio Height X 6-13/6-27
0 2 5 0 1 1 1 0 1 0 0 Radio Height X 6-13/6-27
1 6 4
0 2 7 0 1 1 1 0 1 0 0 MLS Dataword 7 X
0 3 B 0 1 1 1 0 1 0 0 Radio Height X
0 5 5 0 1 1 1 0 1 0 0 MLS ABS GP Angle X
1 1 4 0 1 1 1 0 1 0 0 Indicated Pump Status X
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 23
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 7 0 1 1 1 0 1 0 1 Radio Height X 6-25

0 0 B 0 1 1 1 0 1 0 1 Vertical Velocity X
1 6 5 0 2 7 0 1 1 1 0 1 0 1 MLS Dataword 8 X
0 5 5 0 1 1 1 0 1 0 1 MLS ABS Azimuth Angle X
1 1 4 0 1 1 1 0 1 0 1 Indicated Valve Status X
0 0 7 0 1 1 1 0 1 1 0 RALT Check Point Dev. X
1 6 6 0 0 B 0 1 1 1 0 1 1 0 North/South Velocity X
1 1 4 0 1 1 1 0 1 1 0 Indicated Valve Status X
0 0 2 0 1 1 1 0 1 1 1 EPU Estimate Position Uncertainty/ (ANP) Actual Navi. Perf. X
1 6 7
1 1 4 0 1 1 1 0 1 1 1 Indicated Valve Status X
0 2 5 0 1 1 1 1 0 0 0 Decision Height Selected (EFI) X 6-25
0 C 5 0 1 1 1 1 0 0 0 Decision Height Selected (EFI) X 6-25
1 7 0
1 1 4 0 1 1 1 1 0 0 0 Wing Imbalance and FQI Failure Warning X
0 1 1 1 1 0 0 0 DFDAU - System Address Label X See Attachment 11
0 0 2 0 1 1 1 1 0 0 1 RNP Required Navigation Performance X
0 5 6 0 1 1 1 1 0 0 1 Current RNP X
1 7 1
0 6 0 0 1 1 1 1 0 0 1 Current RNP X
X X X 0 1 1 1 1 0 0 1 Manufacturer Specific Status Word X See Attachment 10
1 7 2 X X X 0 1 1 1 1 0 1 0 Subsystem Identifier 6-34/Note 1
0 1 0 0 1 1 1 1 0 1 1 Localizer Deviation X 6-6/6-27
0 2 5 0 1 1 1 1 0 1 1 Localizer Deviation X 6-6/6-27
0 2 9 0 1 1 1 1 0 1 1 Hydraulic Quantity X
0 3 B 0 1 1 1 1 0 1 1 Localizer Deviation X
1 7 3
0 5 5 0 1 1 1 1 0 1 1 Localizer Deviation X
0 B D 0 1 1 1 1 0 1 1 Hydraulic Quantity X
0 D 0 0 1 1 1 1 0 1 1 Hydraulic Oil X
0 1 1 1 1 0 1 1 SDU #2 - System Address Label X See Attachment 11
0 0 3 0 1 1 1 1 1 0 0 Delayed Flap Approach Speed (DFA) X
0 0 B 0 1 1 1 1 1 0 0 East/West Velocity X
0 1 0 0 1 1 1 1 1 0 0 Glideslope Deviation X 6-6/6-27
0 2 9 0 1 1 1 1 1 0 0 Hydraulic Pressure X
1 7 4
0 3 B 0 1 1 1 1 1 0 0 Glideslope Deviation X 6-6/6-27
0 5 5 0 1 1 1 1 1 0 0 Glideslope Deviation X
0 D 0 0 1 1 1 1 1 0 0 Hydraulic Oil Pressure X
0 1 1 1 1 1 0 0 RFU - System Address Label X See Attachment 11
0 0 3 0 1 1 1 1 1 0 1 Economical Speed X
0 2 9 0 1 1 1 1 1 0 1 EGT (APU) X
1 7 5
0 3 3 0 1 1 1 1 1 0 1 Hydraulic Pump Case Drain Temperature X
0 1 1 1 1 1 0 1 HGA/HPA Top/Port - System Address Label X See Attachment 11
0 0 3 0 1 1 1 1 1 1 0 Economical Mach X
0 2 9 0 1 1 1 1 1 1 0 RPM (APU) X
0 3 8 0 1 1 1 1 1 1 0 Left Static Pressure Uncorrected, mb X
1 7 6 0 5 A 0 1 1 1 1 1 1 0 Fuel Temperature - Set to Zero X
0 A D 0 1 1 1 1 1 1 0 Static Pressure Left, Uncorrected, mb X
1 1 4 0 1 1 1 1 1 1 0 Left Outer Tank Fuel Temp & Advisory Warning X
0 1 1 1 1 1 1 0 HGA/HPA Starboard - System Address Label X See Attachment 11
0 0 3 0 1 1 1 1 1 1 1 Economical Flight Level X
0 2 9 0 1 1 1 1 1 1 1 Oil Quantity (APU) X
0 3 8 0 1 1 1 1 1 1 1 Right Static Pressure Uncorrected, mb X
0 5 5 0 1 1 1 1 1 1 1 Distance To Runway Threshold X
1 7 7
0 5 A 0 1 1 1 1 1 1 1 Fuel Temperature Left Wing Tank X
0 A D 0 1 1 1 1 1 1 1 Static Pressure Right, Uncorrected, mb X
1 1 4 0 1 1 1 1 1 1 1 Inner Tank 1 Fuel Temp & Advisory Warning X
0 1 1 1 1 1 1 1 LGA/HPA - System Address Label X See Attachment 11
0 0 2 1 0 0 0 0 0 0 0 Drift Angle X
0 0 4 1 0 0 0 0 0 0 0 Drift Angle X
2 0 0 0 5 6 1 0 0 0 0 0 0 0 Drift Angle X
0 6 0 1 0 0 0 0 0 0 0 Drift Angle X
1 1 4 1 0 0 0 0 0 0 0 Inner Tank 2 Fuel Temp & Advisory Warning X
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 24
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 9 1 0 0 0 0 0 0 1 DME Distance X 6-1-1

0 5 A 1 0 0 0 0 0 0 1 Fuel Temperature Right Wing Tank X
1 1 2 1 0 0 0 0 0 0 1 TACAN Distance X
1 1 4 1 0 0 0 0 0 0 1 Inner Tank 3 Fuel Temp & Advisory Warning X
2 0 1
1 1 5 1 0 0 0 0 0 0 1 DME X 6-25
1 4 0 1 0 0 0 0 0 0 1 Mach Maximum Operation (Mmo) X
1 4 2 1 0 0 0 0 0 0 1 Projected Future Latitude X
1 0 0 0 0 0 0 1 GPS/GNSS Sensor - System Address Label X See Attachment 11
0 0 2 1 0 0 0 0 0 1 0 Energy Management (clean) X
0 0 9 1 0 0 0 0 0 1 0 DME Distance X 6-7/6-27
0 2 9 1 0 0 0 0 0 1 0 Cabin Compartment Temperature (Group #1) X
2 0 2 0 5 A 1 0 0 0 0 0 1 0 Fuel Temperature - Set to Zero X
1 1 4 1 0 0 0 0 0 1 0 Inner Tank 4 Fuel Temp & Advisory Warning X
1 4 0 1 0 0 0 0 0 1 0 Mach Rate X
1 4 2 1 0 0 0 0 0 1 0 Projected Future Latitude Fine X
0 0 2 1 0 0 0 0 0 1 1 Energy Management Speed Brakes X
0 0 6 1 0 0 0 0 0 1 1 Altitude (1013.25mB) X
0 1 8 1 0 0 0 0 0 1 1 Altitude X 6-24/6-27
0 2 9 1 0 0 0 0 0 1 1 Cabin Compartment Temperature (Group #2) X
0 3 5 1 0 0 0 0 0 1 1 Own A/C Altitude X
2 0 3 0 3 8 1 0 0 0 0 0 1 1 Altitude (1013.25mB) X
0 5 A 1 0 0 0 0 0 1 1 Fuel Tank #6 Temperature X
1 0 A 1 0 0 0 0 0 1 1 Ambient Static Pressure X
1 0 B 1 0 0 0 0 0 1 1 Ambient Static Pressure X
1 1 4 1 0 0 0 0 0 1 1 Trim Tank Fuel Temp & Advisory Warning X
1 4 0 1 0 0 0 0 0 1 1 Altitude X
0 0 2 1 0 0 0 0 1 0 0 Utitlity Airspeed X
0 0 6 1 0 0 0 0 1 0 0 Baro Corrected Altitude #1 X
0 2 9 1 0 0 0 0 1 0 0 Cabin Duct Temperature (Group #1) X
0 3 8 1 0 0 0 0 1 0 0 Baro Corrected Altitude #1 X
2 0 4 0 5 6 1 0 0 0 0 1 0 0 Baro Altitude X
0 5 A 1 0 0 0 0 1 0 0 Fuel Tank #7 Temperature X
0 6 0 1 0 0 0 0 1 0 0 Baro Altitude X
1 1 4 1 0 0 0 0 1 0 0 Right Outer Tank Fuel Temp & Advisory Warning X
1 4 0 1 0 0 0 0 1 0 0 Baro Corrected Altitude X
0 0 2 1 0 0 0 0 1 0 1 HF COM Frequency (New Format) X 6-43
0 0 6 1 0 0 0 0 1 0 1 Mach X 6-27
0 1 A 1 0 0 0 0 1 0 1 Mach X 6-27
0 2 9 1 0 0 0 0 1 0 1 Cabin Duct Temperature (Group #2) X
0 3 8 1 0 0 0 0 1 0 1 Mach X
2 0 5
0 5 A 1 0 0 0 0 1 0 1 Fuel Tank #8 Temperature X
0 B 9 1 0 0 0 0 1 0 1 HF COM Frequency (New Format) X
1 0 A 1 0 0 0 0 1 0 1 Mach Number X
1 0 B 1 0 0 0 0 1 0 1 Mach Number X
1 4 0 1 0 0 0 0 1 0 1 Mach X
0 0 6 1 0 0 0 0 1 1 0 Computed Airspeed X 6-27
0 1 8 1 0 0 0 0 1 1 0 Altitude (Variable Resolution) X 6-20
0 2 9 1 0 0 0 0 1 1 0 Cabin Temp. Reg. Valve Position (Group #1) X
0 3 8 1 0 0 0 0 1 1 0 Computed Airspeed X 6-27
2 0 6
0 5 6 1 0 0 0 0 1 1 0 Computed Airspeed X
0 6 0 1 0 0 0 0 1 1 0 Computed Airspeed X
0 C C 1 0 0 0 0 1 1 0 Taxi Speed X
1 4 0 1 0 0 0 0 1 1 0 Computed Airspeed (CAS) X
0 0 2 1 0 0 0 0 1 1 1 HF Control Word X See Attachment 11
0 0 6 1 0 0 0 0 1 1 1 Max. Allowable Airspeed X
0 0 A 1 0 0 0 0 1 1 1 Max. Allowable Airspeed X
0 2 5 1 0 0 0 0 1 1 1 OP. Software Part Number X 6-37
2 0 7
0 2 9 1 0 0 0 0 1 1 1 Cabin Temp. Reg. Valve Position (Group #2) X
0 3 8 1 0 0 0 0 1 1 1 Max. Allowable Airspeed X
0 B 9 1 0 0 0 0 1 1 1 HF Control Word X See Attachment 11
1 4 0 1 0 0 0 0 1 1 1 Airspeed Maximum Operating (VMO) X
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 25
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 6 1 0 0 0 1 0 0 0 True Airspeed X 6-27

0 2 9 1 0 0 0 1 0 0 0 Cargo Compartment Temperature X
2 1 0 0 3 8 1 0 0 0 1 0 0 0 True Airspeed X 6-27
1 4 0 1 0 0 0 1 0 0 0 True Airspeed X
1 0 0 0 1 0 0 0 FCMC Com A340-500/600 X
0 0 2 1 0 0 0 1 0 0 1 Total Air Temperature X 6-27
0 0 3 1 0 0 0 1 0 0 1 Total Air Temperature X
0 0 6 1 0 0 0 1 0 0 1 Total Air Temperature X
0 1 A 1 0 0 0 1 0 0 1 Total Air Temperature X
0 2 9 1 0 0 0 1 0 0 1 Cargo Duct Temperature X
0 3 8 1 0 0 0 1 0 0 1 Total Air Temperature X
2 1 1
0 A D 1 0 0 0 1 0 0 1 Total Air Temperature Indicated X
1 0 A 1 0 0 0 1 0 0 1 Total Fan Inlet Temperature X
1 0 B 1 0 0 0 1 0 0 1 Total Fan Inlet Temperature X
1 4 0 1 0 0 0 1 0 0 1 Total Air Temp (TAT) X
1 4 2 1 0 0 0 1 0 0 1 Projected Future Longitude X
1 0 0 0 1 0 0 1 FCMC Mon A340-500/600 X
0 0 4 1 0 0 0 1 0 1 0 Altitude Rate X 6-27
0 0 5 1 0 0 0 1 0 1 0 Altitude Rate X
0 0 6 1 0 0 0 1 0 1 0 Altitude Rate X
0 2 9 1 0 0 0 1 0 1 0 Cargo Temp. Reg. Valve Position X
0 3 8 1 0 0 0 1 0 1 0 Altitude Rate X
2 1 2 0 3 B 1 0 0 0 1 0 1 0 Altitude Rate X
0 5 6 1 0 0 0 1 0 1 0 Altitude Rate X
0 6 0 1 0 0 0 1 0 1 0 Altitude Rate X
1 4 0 1 0 0 0 1 0 1 0 Altitude Rate X
1 4 2 1 0 0 0 1 0 1 0 Projected Future Longitude Fine X
1 0 0 0 1 0 1 0 FCMC Int A340-500/600 X
0 0 2 1 0 0 0 1 0 1 1 Static Air Temperature X 6-27
0 0 6 1 0 0 0 1 0 1 1 Static Air Temperature X 6-27
0 3 8 1 0 0 0 1 0 1 1 Static Air Temperature X
2 1 3
0 8 D 1 0 0 0 1 0 1 1 Fuel Used X 6-27
1 4 0 1 0 0 0 1 0 1 1 Static Air Temp (SAT) X
1 4 2 1 0 0 0 1 0 1 1 Veritical Time Interval X
2 1 4 X X X 1 0 0 0 1 1 0 0 ICAO Aircraft Address (Part 1) X 6-39/Note 1
0 0 6 1 0 0 0 1 1 0 1 Impacted Pressure, Uncorrected, mb X
0 1 A 1 0 0 0 1 1 0 1 Impact Pressure X
0 2 9 1 0 0 0 1 1 0 1 N1 Actual (EEC) X
2 1 5 0 2 9 1 0 0 0 1 1 0 1 EPR Actual (EEC) X
0 3 8 1 0 0 0 1 1 0 1 Impacted Pressure, Uncorrected, mb X
0 A D 1 0 0 0 1 1 0 1 Impacted Pressure, Uncorrected, mb X
1 4 0 1 0 0 0 1 1 1 1 Impact Pressure Subsonic X
2 1 6 X X X 1 0 0 0 1 1 1 0 ICAO Aircraft Address (Part 2) X Note 1
0 0 2 1 0 0 0 1 1 1 1 Geometric Vertical Rate X
0 0 6 1 0 0 0 1 1 1 1 Static Pressure, Corrected (In. Hg) X
0 2 9 1 0 0 0 1 1 1 1 N1 Limit (EEC) X
2 1 7
0 2 9 1 0 0 0 1 1 1 1 EPR Actual (EEC) X
0 3 8 1 0 0 0 1 1 1 1 Static Pressure, Average, Corrected (In. Hg) X
1 4 0 1 0 0 0 1 1 1 1 Static Pressure Corrected (In. Hg) X
0 0 6 1 0 0 1 0 0 0 0 Baro Corrected Altitude #2 X
0 3 8 1 0 0 1 0 0 0 0 Baro Corrected Altitude #2 X
2 2 0
1 4 0 1 0 0 1 0 0 0 0 Baro Corrected Altitude #2 X
1 0 0 1 0 0 0 0 MCDU #1 - System Address label (Recipient) X See Attachment 11
0 0 6 1 0 0 1 0 0 0 1 Indicated Angle of Attack (Average) X
0 3 8 1 0 0 1 0 0 0 1 Indicated Angle of Attack (Average) X
0 A D 1 0 0 1 0 0 0 1 Indicated Angle of Attack (Average) X
2 2 1
1 2 C 1 0 0 1 0 0 0 1 Indicated Angle of Attack (Average)
1 4 0 1 0 0 1 0 0 0 1 Angle of Attach Indicated Average X
1 0 0 1 0 0 0 1 MCDU #2 - System Address label (Recipient) X See Attachment 11
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 26
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 6 1 0 0 1 0 0 1 0 Indicated Angle of Attack (#1 Left) X

0 1 1 1 0 0 1 0 0 1 0 VOR Omnibearing X 6-10
1 1 2 1 0 0 1 0 0 1 0 TACAN Bearing X
2 2 2 1 1 5 1 0 0 1 0 0 1 0 Bearing X
1 2 C 1 0 0 1 0 0 1 0 Indicated Angle of Attack (#1 Left) X
1 4 0 1 0 0 1 0 0 1 0 Angle of Attack, Indicated (#1 Left) X
1 0 0 1 0 0 1 0 MCDU #3 - System Address Label X See Attachment 11
0 0 6 1 0 0 1 0 0 1 1 Indicated Angle of Attack (#1 Right) X
1 2 C 1 0 0 1 0 0 1 1 Indicated Angle of Attack (#1 Right) X
2 2 3
1 4 0 1 0 0 1 0 0 1 1 Angle of Attack, Indicated (#1 Right) X
1 0 0 1 0 0 1 1 Printer #1 - System Address Label X See Attachment 11
0 0 6 1 0 0 1 0 1 0 0 Indicated Angle of Attack (#2 Left) X
1 2 C 1 0 0 1 0 1 0 0 Indicated Angle of Attack (#2 Left) X
2 2 4
1 4 0 1 0 0 1 0 1 0 0 Angle of Attack, Indicated (#2 Left) X
1 0 0 1 0 1 0 0 Printer #2 - System Address Label X See Attachment 11
0 0 2 1 0 0 1 0 1 0 1 Min. Maneuvering Airspeed X
0 0 6 1 0 0 1 0 1 0 1 Indicated Angle of Attack (#2 Right) X
0 2 B 1 0 0 1 0 1 0 1 Compensated Altitude Rate X
0 5 6 1 0 0 1 0 1 0 1 Minimum Maneuvering Airspeed X
2 2 5
0 6 0 1 0 0 1 0 1 0 1 Minimum Maneuvering Airspeed X
1 2 C 1 0 0 1 0 1 0 1 Indicated Angle of Attack (#2 Right) X
1 4 0 1 0 0 1 0 1 0 1 Angle of Attack, Indicated (#2 Right) X
1 0 0 1 0 1 0 1 System Address Label for HUD X See Attachment 11
0 0 2 1 0 0 1 0 1 1 0 Min. Op. Fuel Temp (non-conflicting) X
2 2 6
1 0 0 1 0 1 1 0 Data Loader System Addess Label (High Speed) X See Attachment 11
0 1 9 1 0 0 1 0 1 1 1 CFDS Bite Command Summary for HFDR X
0 3 D 1 0 0 1 0 1 1 1 AVM Command X 6-28
2 2 7
0 5 3 1 0 0 1 0 1 1 1 CFDS Bite Command Summary for HFDR X
0 7 E 1 0 0 1 0 1 1 1 BITE Command Word X
0 0 6 1 0 0 1 1 0 0 0 True Airspeed X 6-25
0 3 8 1 0 0 1 1 0 0 0 True Airspeed X 6-25
2 3 0
1 1 4 1 0 0 1 1 0 0 0 Left Outer Probes Capacitance X
1 0 0 1 1 0 0 0 MCDU #4 - System Address Label X See Attachment 11
0 0 6 1 0 0 1 1 0 0 1 Total Air Temperature X 6-25
2 3 1 0 3 8 1 0 0 1 1 0 0 1 Total Air Temperature X
1 1 4 1 0 0 1 1 0 0 1 Inner 2 Tank Probe Capacitance X
0 0 4 1 0 0 1 1 0 1 0 Altitude Rate X 6-25
0 0 5 1 0 0 1 1 0 1 0 Altitude Rate X
2 3 2 0 0 6 1 0 0 1 1 0 1 0 Altitude Rate X
0 5 5 1 0 0 1 1 0 1 0 GLS Airport ID X
1 1 4 1 0 0 1 1 0 1 0 Inner 4 Tank Probe Capacitance X
0 0 2 1 0 0 1 1 0 1 1 ACMS Information X 6-31
0 0 6 1 0 0 1 1 0 1 1 Static Air Temperature X 6-25
0 3 8 1 0 0 1 1 0 1 1 Static Air Temperature X 6-25
2 3 3
0 5 6 1 0 0 1 1 0 1 1 ACMS Information X
0 6 0 1 0 0 1 1 0 1 1 ACMS Information X
1 1 4 1 0 0 1 1 0 1 1 Right Outer Probe Capacitance X
0 0 2 1 0 0 1 1 1 0 0 ACMS Information X 6-31
0 0 6 1 0 0 1 1 1 0 0 Baro Correction (mb) #1 X
0 3 8 1 0 0 1 1 1 0 0 Baro Correction (mb) #1 X
2 3 4
0 5 6 1 0 0 1 1 1 0 0 ACMS Information X
0 6 0 1 0 0 1 1 1 0 0 ACMS Information X
1 0 0 1 1 1 0 0 System Address Label for EIVMU 1 X See Attachment 11
0 0 2 1 0 0 1 1 1 0 1 ACMS Information X 6-31
0 0 6 1 0 0 1 1 1 0 1 Baro Correction (ins. Hg) #1 X 6-25
0 3 8 1 0 0 1 1 1 0 1 Baro Correction (ins. Hg) #1 X 6-25
2 3 5
0 5 6 1 0 0 1 1 1 0 1 ACMS Information X
0 6 0 1 0 0 1 1 1 0 1 ACMS Information X
1 0 0 1 1 1 0 1 System Address Label for EIVMU 2 X See Attachment 11
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 27
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 2 1 0 0 1 1 1 1 0 ACMS Information X 6-31

0 0 6 1 0 0 1 1 1 1 0 Baro Correction (mb) #2 X
0 3 8 1 0 0 1 1 1 1 0 Baro Correction (mb) #2 X
2 3 6
0 5 6 1 0 0 1 1 1 1 0 ACMS Information X
0 6 0 1 0 0 1 1 1 1 0 ACMS Information X
1 0 0 1 1 1 1 0 System Address Label for EIVMU 3 X See Attachment 11
0 0 2 1 0 0 1 1 1 1 1 ACMS Information X
0 0 6 1 0 0 1 1 1 1 1 Baro Correction (ins. Hg) #2 X
0 0 B 1 0 0 1 1 1 1 1 Horizontal Uncertainty Level X
2 3 7 0 3 8 1 0 0 1 1 1 1 1 Baro Correction (ins. Hg) #2 X
0 5 6 1 0 0 1 1 1 1 1 ACMS Information X
0 6 0 1 0 0 1 1 1 1 1 ACMS Information X
1 0 0 1 1 1 1 1 System Address Label for EIVMU 4 X See Attachment 11
2 4 0 0 1 0 1 0 0 0 0 0 Spare
0 0 2 1 0 1 0 0 0 0 1 Min. Airspeed for Flap Extension X
0 0 6 1 0 1 0 0 0 0 1 Corrected Angle of Attack X
0 2 C 1 0 1 0 0 0 0 1 Reserved (Special Use) X
0 3 8 1 0 1 0 0 0 0 1 Corrected Angle of Attack X
0 4 D 1 0 1 0 0 0 0 1 FQIS System Data X 6-35
2 4 1
0 5 6 1 0 1 0 0 0 0 1 Min. Airspeed for Flap Extension X
0 6 0 1 0 1 0 0 0 0 1 Min. Airspeed for Flap Extension X
1 4 0 1 0 1 0 0 0 0 1 Angle of Attack, Corrected X
1 6 0 1 0 1 0 0 0 0 1 Tank Unit Data X 6-38
1 0 1 0 0 0 0 1 System Address Label for APM-MMR X See Attachment 11
0 0 6 1 0 1 0 0 0 1 0 Total Pressure X
0 0 9 1 0 1 0 0 0 1 0 Ground Station ID (Word #1) X
0 1 0 1 0 1 0 0 0 1 0 Ground Station ID (Word #1) X
0 1 1 1 0 1 0 0 0 1 0 Ground Station ID (Word #1) X
1 1 2 1 0 1 0 0 0 1 0 Ground Station ID (Word #1) X
2 4 2 0 1 A 1 0 1 0 0 0 1 0 Total Pressure X
0 3 8 1 0 1 0 0 0 1 0 Total Pressure X
0 3 B 1 0 1 0 0 0 1 0 Speed Deviation X
0 A D 1 0 1 0 0 0 1 0 Total Pressure, Uncorrected, mb X
1 4 0 1 0 1 0 0 0 1 0 Total Pressure X
1 0 1 0 0 0 1 0 System Address Label for MMR X See Attachment 11
0 3 7 1 0 1 0 0 0 1 1 Zero Fuel Weight (kg) X
2 4 3 0 5 5 1 0 1 0 0 0 1 1 GLS Runway Selection X
X X X 1 0 1 0 0 0 1 1 Simulator to Avionics Control Word X Note 1
0 0 9 1 0 1 0 0 1 0 0 Ground Station ID (Word #2) X
0 1 0 1 0 1 0 0 1 0 0 Ground Station ID (Word #2) X
0 1 1 1 0 1 0 0 1 0 0 VOR Ground Station Ident Word #2 X
0 1 2 1 0 1 0 0 1 0 0 Ground Station ID (Word #2) X
0 1 C 1 0 1 0 0 1 0 0 Fuel Flow (Engine Direct) X
0 3 3 1 0 1 0 0 1 0 0 Fuel Flow (Wf) X
2 4 4
0 3 B 1 0 1 0 0 1 0 0 Mach Error X
0 8 D 1 0 1 0 0 1 0 0 Fuel Flow Rate X
1 0 A 1 0 1 0 0 1 0 0 Fuel Mass Flow X
1 0 B 1 0 1 0 0 1 0 0 Fuel Mass Flow X
1 4 0 1 0 1 0 0 1 0 0 Angle of Attack, Normalized X
1 0 1 0 0 1 0 0 System Address Label for ILS X See Attachment 11
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 28
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 2 1 0 1 0 0 1 0 1 Minimum Airspeed X
0 0 3 1 0 1 0 0 1 0 1 Minimum Airspeed X
0 0 A 1 0 1 0 0 1 0 1 Minimum Airspeed X
0 2 9 1 0 1 0 0 1 0 1 N3 (Engine) X
0 3 8 1 0 1 0 0 1 0 1 Average Static Pressure mb, Uncorrected X
2 4 5 0 3 B 1 0 1 0 0 1 0 1 EPR Error X
0 5 6 1 0 1 0 0 1 0 1 Minimum Airspeed X
0 6 0 1 0 1 0 0 1 0 1 Minimum Airspeed X
0 A D 1 0 1 0 0 1 0 1 Average Static Pressure mb, Uncorrected X
1 4 0 1 0 1 0 0 1 0 1 Static Pressure, Uncorrected X
1 0 1 0 0 1 0 1 System Address Label for MLS X See Attachment 11
0 0 2 1 0 1 0 0 1 1 0 General Maximum Speed (VCMAX) X
0 0 6 1 0 1 0 0 1 1 0 Average Static Pressure X
0 0 9 1 0 1 0 0 1 1 0 DME Ground Station Ident Word #1 X
0 1 C 1 0 1 0 0 1 1 0 N1 (Engine Direct) X
2 4 6
0 2 9 1 0 1 0 0 1 1 0 N1 (Engine Direct) X
0 3 8 1 0 1 0 0 1 1 0 Average Static Pressure mb, Corrected X
0 3 B 1 0 1 0 0 1 1 0 Angle of Attack Error X
1 0 1 0 0 1 1 0 System address Label for AHRS X See Attachment 11
0 0 2 1 0 1 0 0 1 1 1 Control Minimum Speed (VCMIN) X
0 0 9 1 0 1 0 0 1 1 1 DME Ground Station Ident Word #1 X
0 0 B 1 0 1 0 0 1 1 1 Horizontal Figure of Merit X
0 1 F 1 0 1 0 0 1 1 1 Total Fuel X
0 2 C 1 0 1 0 0 1 1 1 Total Fuel X
0 3 B 1 0 1 0 0 1 1 1 Speed Error X
2 4 7 0 4 D 1 0 1 0 0 1 1 1 Total Fuel X
0 5 6 1 0 1 0 0 1 1 1 Control Minimum Speed (VCMIN) X
0 5 A 1 0 1 0 0 1 1 1 Total Fuel X
0 6 0 1 0 1 0 0 1 1 1 Control Minimum Speed (VCMIN) X
0 E B 1 0 1 0 0 1 1 1 Fuel to Remain X
1 1 4 1 0 1 0 0 1 1 1 Fuel on Board X
1 4 0 1 0 1 0 0 1 1 1 Airspeed Minimum Vmc X
0 0 2 1 0 1 0 1 0 0 0 Continuous N1 Limit X
0 2 B 1 0 1 0 1 0 0 0 Maximum Continuous EPR Limit X
0 2 C 1 0 1 0 1 0 0 0 Preselected Fuel Quantity X
0 3 8 1 0 1 0 1 0 0 0 Indicated Side Slip Angle X
2 5 0
0 5 A 1 0 1 0 1 0 0 0 Preselected Fuel Quantity X
0 A D 1 0 1 0 1 0 0 0 Indicated Side Slip Angle or AOS X
1 1 4 1 0 1 0 1 0 0 0 Preselected Fuel Quantity X
1 2 B 1 0 1 0 1 0 0 0 Temperature Rate of Change X
0 0 1 1 0 1 0 1 0 0 1 Distance to Go X
0 0 2 1 0 1 0 1 0 0 1 Distance to Go X
0 0 6 1 0 1 0 1 0 0 1 Baro Corrected Altitude #3 X
2 5 1
0 1 A 1 0 1 0 1 0 0 1 Flight Leg Counter X 6-19
0 3 8 1 0 1 0 1 0 0 1 Baro Corrected Altitude #3 X
1 0 1 0 1 0 0 1 System Address Label VDR #1 X See Attachment 11
0 0 1 1 0 1 0 1 0 1 0 Time to Go X
0 0 2 1 0 1 0 1 0 1 0 Time to Go X
0 0 6 1 0 1 0 1 0 1 0 Baro Corrected Altitude #4 X
0 1 A 1 0 1 0 1 0 1 0 EPR Idle X
2 5 2 0 2 F 1 0 1 0 1 0 1 0 EPR Idle Reference X
0 3 8 1 0 1 0 1 0 1 0 Baro Corrected Altitude #4 X
0 3 F 1 0 1 0 1 0 1 0 EPR Idle Reference X
0 E B 1 0 1 0 1 0 1 0 Time Until Jettison Complete X
1 0 1 0 1 0 1 0 System Address Label VDR #2 X See Attachment 11
0 0 2 1 0 1 0 1 0 1 1 Go-Around N1 Limit X
0 1 E 1 0 1 0 1 0 1 1 Go-Around EPR Limit X
2 5 3
0 3 8 1 0 1 0 1 0 1 1 Corrected Side Slip Angle X
1 0 1 0 1 0 1 1 System Address Label VDR #3 X See Attachment 11
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 29
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 2 1 0 1 0 1 1 0 0 Cruise N1 Limit X
0 1 2 1 0 1 0 1 1 0 0 ADF Ground Station Ident Word #1 X
0 1 E 1 0 1 0 1 1 0 0 Cruise EPR Limit X
2 5 4 0 4 D 1 0 1 0 1 1 0 0 Actual Fuel Quantity (test) X
0 5 5 1 0 1 0 1 1 0 0 GBAS ID X
1 3 A 1 0 1 0 1 1 0 0 N1 Cruise X
1 4 0 1 0 1 0 1 1 0 0 Altitude Rate X
0 0 2 1 0 1 0 1 1 0 1 Climb N1 Limit X
0 1 2 1 0 1 0 1 1 0 1 ADF Ground Station Ident Word #2 X
0 1 E 1 0 1 0 1 1 0 1 Climb EPR Limit X
0 2 F 1 0 1 0 1 1 0 1 Max. Climb EPR Rating X
0 3 F 1 0 1 0 1 1 0 1 Max. Climb EPR Rating X
2 5 5
0 4 D 1 0 1 0 1 1 0 1 Fuel Quantity (gal) X
0 5 5 1 0 1 0 1 1 0 1 GBAS ID/ Airport ID X
0 8 E 1 0 1 0 1 1 0 1 Spoiler Position X
1 3 A 1 0 1 0 1 1 0 1 N1 Climb X
1 4 0 1 0 1 0 1 1 0 1 Impact Pressure X
0 0 2 1 0 1 0 1 1 1 0 Time for Climb X
0 0 A 1 0 1 0 1 1 1 0 V Stick Shaker X
0 2 7 1 0 1 0 1 1 1 0 MLS Ground Station Ident Word #1 X
0 2 C 1 0 1 0 1 1 1 0 Fuel Quantity (Tanks) #1 X
0 4 D 1 0 1 0 1 1 1 0 Fuel Discretes X
2 5 6 0 5 5 1 0 1 0 1 1 1 0 MLS Station ID #1 X
0 5 6 1 0 1 0 1 1 1 0 Time for Climb X
0 5 A 1 0 1 0 1 1 1 0 Fuel Quantity - Left Outer Cell X
0 6 0 1 0 1 0 1 1 1 0 Time for Climb X
1 1 4 1 0 1 0 1 1 1 0 Left Outer Tank Fuel Quantity X
1 4 0 1 0 1 0 1 1 1 0 Equivalent Airspeed X
0 0 2 1 0 1 0 1 1 1 1 Time for Descent X
0 2 7 1 0 1 0 1 1 1 1 MLS Ground Station Ident Word #2 X
0 2 C 1 0 1 0 1 1 1 1 Fuel Quantity (Tanks) #2 X
0 5 5 1 0 1 0 1 1 1 1 MLS Station ID #2
2 5 7 0 5 6 1 0 1 0 1 1 1 1 Time for Descent X
0 5 A 1 0 1 0 1 1 1 1 Fuel Quantity Left W/T Tank X
0 6 0 1 0 1 0 1 1 1 1 Time for Descent X
1 1 4 1 0 1 0 1 1 1 1 Inner Tank 1 Fuel Quantity X
1 4 0 1 0 1 0 1 1 1 1 Total Pressure (High Range) X
0 0 2 1 0 1 1 0 0 0 0 Date/Flight Leg X 6-8
0 0 B 1 0 1 1 0 0 0 0 Date X
0 2 C 1 0 1 1 0 0 0 0 Fuel Quantity (Tanks) #3 X
0 3 1 1 0 1 1 0 0 0 0 Date (No Flight Leg) X 6-18
0 3 3 1 0 1 1 0 0 0 0 T5 X
0 5 6 1 0 1 1 0 0 0 0 Date/Flight Leg X
2 6 0
0 5 A 1 0 1 1 0 0 0 0 Fuel Quantity Center Tank X
0 6 0 1 0 1 1 0 0 0 0 Date/Flight Leg X 6-8
0 A 2 1 0 1 1 0 0 0 0 Date/Flight Leg X 6-8
1 0 A 1 0 1 1 0 0 0 0 LP Turbine Discharge Temperature X
1 0 B 1 0 1 1 0 0 0 0 LP Turbine Discharge Temperature X
1 1 4 1 0 1 1 0 0 0 0 Collector Cell 1 and 2 Fuel Quantity X
0 0 2 1 0 1 1 0 0 0 1 Flight Number X 6-9
0 2 C 1 0 1 1 0 0 0 1 Fuel Quantity (Tanks) #4 X
0 3 3 1 0 1 1 0 0 0 1 P49 X
0 5 6 1 0 1 1 0 0 0 1 Flight Number (BCD) X
0 5 A 1 0 1 1 0 0 0 1 Fuel Quantity Right I/C or W/T Tank X
2 6 1
0 6 0 1 0 1 1 0 0 0 1 Flight Number (BCD) X
0 A 2 1 0 1 1 0 0 0 1 Flight Number X 6-9
1 0 A 1 0 1 1 0 0 0 1 LP Turbine Inlet Pressure X
1 0 B 1 0 1 1 0 0 0 1 LP Turbine Inlet Pressure X
1 1 4 1 0 1 1 0 0 0 1 Fuel On Board At Engine Start X
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 30
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 2 1 0 1 1 0 0 1 0 Documentary Data X 6-14

0 0 A 1 0 1 1 0 0 1 0 Predictive Airspeed Variation X
0 1 C 1 0 1 1 0 0 1 0 LP Compressor Exist Pressure (PT3) X
0 2 C 1 0 1 1 0 0 1 0 Fuel Quantity (Tanks) #5 X
0 3 3 1 0 1 1 0 0 1 0 LP Compressor Exist Pressure X
0 4 D 1 0 1 1 0 0 1 0 T/U CAP-L Tank 1-4 X
2 6 2
0 5 6 1 0 1 1 0 0 1 0 Documentary Data X
0 5 A 1 0 1 1 0 0 1 0 Fuel Quantity - Right Outer Cell X
0 6 0 1 0 1 1 0 0 1 0 Documentary Data X
1 0 A 1 0 1 1 0 0 1 0 HP Compressor Inlet Total Pressure X
1 0 B 1 0 1 1 0 0 1 0 HP Compressor Inlet Total Pressure X
1 1 4 1 0 1 1 0 0 1 0 Center Tank Fuel Quantity X
0 0 2 1 0 1 1 0 0 1 1 Minimum Airspeed for Flap Retraction X
0 0 A 1 0 1 1 0 0 1 1 Minimum Airspeed for Flap Retraction X
0 1 0 1 0 1 1 0 0 1 1 ILS Ground Station Ident Word #1 X
0 1 C 1 0 1 1 0 0 1 1 LP Compressor Exit Temperature X
0 2 C 1 0 1 1 0 0 1 1 Fuel Quantity (Tanks) #6 X
0 3 3 1 0 1 1 0 0 1 1 LP Compressor Exit Temperature X
2 6 3 0 4 D 1 0 1 1 0 0 1 1 T/U CAP-L Tank 5-8 X
0 5 5 1 0 1 1 0 0 1 1 Ground Station/Approach X
0 5 6 1 0 1 1 0 0 1 1 Minimum Airspeed For Flap Retraction X
0 6 0 1 0 1 1 0 0 1 1 Minimum Airspeed For Flap Retraction X
1 0 A 1 0 1 1 0 0 1 1 Selected Compressor Inlet Temperature (Total) X
1 0 B 1 0 1 1 0 0 1 1 Selected Compressor Inlet Temperature (Total) X
1 1 4 1 0 1 1 0 0 1 1 Collector Cell 3 and 4 Fuel Quantity X
0 0 2 1 0 1 1 0 1 0 0 Time to Touchdown X
0 0 A 1 0 1 1 0 1 0 0 Minimum Airspeed for Slats Retraction X
0 1 0 1 0 1 1 0 1 0 0 ILS Ground Station Ident Word #2 X
0 1 C 1 0 1 1 0 1 0 0 HP Compressor Exit Pressure X
0 2 C 1 0 1 1 0 1 0 0 Fuel Quantity (Tanks) #7 X
0 2 F 1 0 1 1 0 1 0 0 Burner Pressure X
0 3 3 1 0 1 1 0 1 0 0 HP Compressor Exit Pressure X
0 3 F 1 0 1 1 0 1 0 0 Burner Pressure X
2 6 4
0 4 D 1 0 1 1 0 1 0 0 T/U CAP-L Tank 9-12 X
0 5 5 1 0 1 1 0 1 0 0 Ground Station/Approach X
0 5 6 1 0 1 1 0 1 0 0 Time to Touchdown X
0 6 0 1 0 1 1 0 1 0 0 Time to Touchdown X
1 0 A 1 0 1 1 0 1 0 0 Selected Compressor Discharge Temperature X
1 0 B 1 0 1 1 0 1 0 0 Selected Compressor Discharge Temperature X
1 1 4 1 0 1 1 0 1 0 0 Fuel Quantity (Tanks) #7 X
1 3 A 1 0 1 1 0 1 0 0 Burner Pressure X
0 0 2 1 0 1 1 0 1 0 1 Minimum Buffet Airspeed X
0 0 4 1 0 1 1 0 1 0 1 Integrated Vertical Acceleration X
0 0 A 1 0 1 1 0 1 0 1 Maneuvering Airspeed X
0 1 C 1 0 1 1 0 1 0 1 HP Compressor Exit Temperature (TT4.5) X
0 2 C 1 0 1 1 0 1 0 1 Fuel Quantity (Tanks) #8 X
0 3 3 1 0 1 1 0 1 0 1 HP Compressor Exit Temperature X
2 6 5 0 3 8 1 0 1 1 0 1 0 1 Integrated Vertical Acceleration X
0 4 D 1 0 1 1 0 1 0 1 T/U CAP-L Tank 13-14 X
0 5 6 1 0 1 1 0 1 0 1 Minimum Buffet Airspeed X
0 6 0 1 0 1 1 0 1 0 1 Minimum Buffet Airspeed X
1 0 A 1 0 1 1 0 1 0 1 Selected Compressor Discharge Temperature X
1 0 B 1 0 1 1 0 1 0 1 Selected Compressor Discharge Temperature X
1 1 4 1 0 1 1 0 1 0 1 Inner Tank 3 Fuel Quantity X
0 0 1 1 0 1 1 0 1 1 0 Test Word B X
0 1 D 1 0 1 1 0 1 1 0 Test Word B X
2 6 6 0 4 D 1 0 1 1 0 1 1 0 T/U CAP-C Tank 1-4 X
1 1 4 1 0 1 1 0 1 1 0 Inner Tank 2 Fuel Quantity X
1 0 1 1 0 1 1 0 Cabin Video System - System Address Label X See Attachment 11
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 31
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 2 1 0 1 1 0 1 1 1 Maximum Maneuver Airspeed X

0 0 A 1 0 1 1 0 1 1 1 Predictive Maximum Maneuver Speed X
0 2 B 1 0 1 1 0 1 1 1 Throttle Position Command X
0 3 3 1 0 1 1 0 1 1 1 Spare T/C X
0 4 D 1 0 1 1 0 1 1 1 T/U CAP-C Tank 5-8 X
2 6 7
0 5 6 1 0 1 1 0 1 1 1 Maximum Maneuver Airspeed X
0 6 0 1 0 1 1 0 1 1 1 Maximum Maneuver Airspeed X
1 0 A 1 0 1 1 0 1 1 1 HP Compressor Inlet Temperature (Total) X
1 0 B 1 0 1 1 0 1 1 1 HP Compressor Inlet Temperature (Total) X
1 1 4 1 0 1 1 0 1 1 1 Inner Tank 4 Fuel Quantity X
0 0 1 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 0 2 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 0 4 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 0 5 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 0 6 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 0 B 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 1 A 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 1 B 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 1 C 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 1 E 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 2 4 1 0 1 1 1 0 0 0 MU Output Data Word, Communication Link Status X
0 2 5 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 2 7 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 2 9 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 2 F 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 3 0 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 3 1 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 3 3 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 3 5 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 3 7 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 3 8 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 3 9 1 0 1 1 1 0 0 0 MCDU Normal Discrete Word X
0 3 A 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 3 B 1 0 1 1 1 0 0 0 Discrete Data #1 X
2 7 0 0 3 D 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 3 E 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 3 F 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 4 1 1 0 1 1 1 0 0 0 SDU To ACARS MU/CMU Status Word X
0 4 A 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 4 D 1 0 1 1 1 0 0 0 T/U CAP-C Tank 9 X
0 5 0 1 0 1 1 1 0 0 0 VDR Status Word X
0 5 3 1 0 1 1 1 0 0 0 HFDL Status Word X
0 5 5 1 0 1 1 1 0 0 0 MLS Discrete X
0 5 6 1 0 1 1 1 0 0 0 Status Discretes X
0 5 8 1 0 1 1 1 0 0 0 Output Status Word #1 X
0 5 A 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 6 0 1 0 1 1 1 0 0 0 Intent Status X
0 6 0 1 0 1 1 1 0 0 0 Status Discretes X
0 6 0 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 A 2 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 A 8 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 A D 1 0 1 1 1 0 0 0 Discrete Data #1 X
0 C 5 1 0 1 1 1 0 0 0 Discrete Data #1 X
1 0 A 1 0 1 1 1 0 0 0 Discrete Data #1 X
1 0 B 1 0 1 1 1 0 0 0 Discrete Data #1 X
1 1 4 1 0 1 1 1 0 0 0 Unusable, and Empty Warning X
1 1 5 1 0 1 1 1 0 0 0 Stored TACAN Control Word X
1 4 0 1 0 1 1 1 0 0 0 Discrete Data #1 X
1 4 2 1 0 1 1 1 0 0 0 Aircraft Category (Disc Data 1) X
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 32
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 2 1 0 1 1 1 0 0 1 Discrete Data #2 X
0 0 6 1 0 1 1 1 0 0 1 Discrete Data #2 X
0 1 8 1 0 1 1 1 0 0 1 Discrete Data #2 X
0 1 A 1 0 1 1 1 0 0 1 Discrete Data #2 X
0 1 C 1 0 1 1 1 0 0 1 Discrete Data #2 X
0 1 E 1 0 1 1 1 0 0 1 Discrete Data #2 X
0 2 9 1 0 1 1 1 0 0 1 Discrete Data #2 X
0 2 F 1 0 1 1 1 0 0 1 Discrete Data #2 X
0 3 0 1 0 1 1 1 0 0 1 Discrete Data #2 X
0 3 1 1 0 1 1 1 0 0 1 Discrete Data #2 X
0 3 3 1 0 1 1 1 0 0 1 Discrete Data #2 X
0 3 5 1 0 1 1 1 0 0 1 Discrete Data #2 X
0 3 8 1 0 1 1 1 0 0 1 Discrete Data #2 X
0 3 A 1 0 1 1 1 0 0 1 Discrete Data #2 X
0 3 B 1 0 1 1 1 0 0 1 Discrete Data #2 X
2 7 1 0 3 F 1 0 1 1 1 0 0 1 Discrete Data #2 X
0 4 1 1 0 1 1 1 0 0 1 SDU To ACARS MU/CMU Join/Leave Message X
0 4 D 1 0 1 1 1 0 0 1 T/U CAP-A Tank 1-4 X
0 5 5 1 0 1 1 1 0 0 1 MMR Discrete X
0 5 6 1 0 1 1 1 0 0 1 Discrete Data #2 X
0 5 A 1 0 1 1 1 0 0 1 Fuel Density X
0 6 0 1 0 1 1 1 0 0 1 Discrete Data #2 X
0 A 2 1 0 1 1 1 0 0 1 Discrete Data #2 X
0 A 8 1 0 1 1 1 0 0 1 Discrete Data #2 X
0 A D 1 0 1 1 1 0 0 1 Discrete Data #2 X
0 C 5 1 0 1 1 1 0 0 1 Discrete Data #2 X
1 0 A 1 0 1 1 1 0 0 1 Discrete Data #2 X
1 0 B 1 0 1 1 1 0 0 1 Discrete Data #2 X
1 1 4 1 0 1 1 1 0 0 1 Fuel Transfer Indication X
1 4 0 1 0 1 1 1 0 0 1 Discrete Data #2 X
1 4 2 1 0 1 1 1 0 0 1 Altitude Filter Limits (Disc Data 2) X
0 0 1 1 0 1 1 1 0 1 0 Discrete Data #3 X
0 0 2 1 0 1 1 1 0 1 0 Discrete Data #3 X
0 0 3 1 0 1 1 1 0 1 0 Discrete Data #3 X
0 1 8 1 0 1 1 1 0 1 0 Discrete Data #3 X
0 1 A 1 0 1 1 1 0 1 0 Discrete Data #3
0 1 C 1 0 1 1 1 0 1 0 Discrete Data #3 X
0 2 5 1 0 1 1 1 0 1 0 Discrete Data #3 X
0 2 9 1 0 1 1 1 0 1 0 Discrete Data #3 X
0 2 F 1 0 1 1 1 0 1 0 Discrete Data #3 X
0 3 5 1 0 1 1 1 0 1 0 Discrete Data #3 X
0 3 8 1 0 1 1 1 0 1 0 Discrete Data #3 X
0 3 A 1 0 1 1 1 0 1 0 Discrete Data #3 X
2 7 2 0 3 B 1 0 1 1 1 0 1 0 Discrete Data #3 X
0 3 F 1 0 1 1 1 0 1 0 Discrete Data #3 X
0 4 D 1 0 1 1 1 0 1 0 T/U CAP-A Tank 5-8 X
0 5 3 1 0 1 1 1 0 1 0 HFDL Slave (Disc Data 2) X
0 5 6 1 0 1 1 1 0 1 0 Discrete Data #3 X
0 5 A 1 0 1 1 1 0 1 0 Fuel Density X
0 6 0 1 0 1 1 1 0 1 0 Discrete Data #3 X
0 A D 1 0 1 1 1 0 1 0 Discrete Data #3 X
0 C 5 1 0 1 1 1 0 1 0 Discrete Data #3 X
1 0 A 1 0 1 1 1 0 1 0 Discrete Data #3 X
1 0 B 1 0 1 1 1 0 1 0 Discrete Data #3 X
1 1 4 1 0 1 1 1 0 1 0 Fuel Transfer Indication X
1 4 0 1 0 1 1 1 0 1 0 Discrete Data #3 X
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 33
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 1 1 0 1 1 1 0 1 1 Discrete Data #4 X
0 0 3 1 0 1 1 1 0 1 1 Discrete Data #4 X
0 0 B 1 0 1 1 1 0 1 1 GNSS Sensor Status X
0 1 8 1 0 1 1 1 0 1 1 Discrete Data #4 X
0 1 C 1 0 1 1 1 0 1 1 Discrete Data #4 X
0 2 5 1 0 1 1 1 0 1 1 Discrete Data #4 X
0 2 9 1 0 1 1 1 0 1 1 Discrete Data #4 X
0 2 F 1 0 1 1 1 0 1 1 Discrete Data #4 X
0 3 3 1 0 1 1 1 0 1 1 Discrete Data #4 X
2 7 3 0 3 5 1 0 1 1 1 0 1 1 Discrete Data #4 X
0 3 B 1 0 1 1 1 0 1 1 Discrete Data #4 X
0 3 F 1 0 1 1 1 0 1 1 Discrete Data #4 X
0 4 D 1 0 1 1 1 0 1 1 T/U CAP-A Tank 9-11 X
0 5 5 1 0 1 1 1 0 1 1 GNSS Status X
0 5 A 1 0 1 1 1 0 1 1 Sensor Valves Left Wing Tank X
0 C 5 1 0 1 1 1 0 1 1 Discrete Data #4 X
1 0 A 1 0 1 1 1 0 1 1 Discrete Data #4 X
1 0 B 1 0 1 1 1 0 1 1 Discrete Data #4 X
1 1 4 1 0 1 1 1 0 1 1 Memos and Status X
0 0 1 1 0 1 1 1 1 0 0 Discrete Data #5 X
0 0 3 1 0 1 1 1 1 0 0 Discrete Data #5 X
0 0 A 1 0 1 1 1 1 0 0 Discrete Data #5 X
0 1 8 1 0 1 1 1 1 0 0 Discrete Data #5 X
0 1 C 1 0 1 1 1 1 0 0 Discrete Data #5 X
0 2 5 1 0 1 1 1 1 0 0 Discrete Data #5 X
0 2 9 1 0 1 1 1 1 0 0 Discrete Data #5 X
0 2 F 1 0 1 1 1 1 0 0 Discrete Data #5 X
0 3 3 1 0 1 1 1 1 0 0 Discrete Data #5 X
2 7 4
0 3 5 1 0 1 1 1 1 0 0 Discrete Data #5 X
0 3 B 1 0 1 1 1 1 0 0 Discrete Data #5 X
0 3 F 1 0 1 1 1 1 0 0 Discrete Data #5 X
0 4 D 1 0 1 1 1 1 0 0 T/U CAP-R Tank 1-4 X
0 5 A 1 0 1 1 1 1 0 0 Sensor Valves Right Wing Tank X
0 C 5 1 0 1 1 1 1 0 0 Discrete Data #5 X
1 0 A 1 0 1 1 1 1 0 0 Discrete Data #5 X
1 0 B 1 0 1 1 1 1 0 0 Discrete Data #5 X
1 1 4 1 0 1 1 1 1 0 0 Fuel Transfer Indications X
0 0 1 1 0 1 1 1 1 0 1 Discrete Data #6 X
0 0 2 1 0 1 1 1 1 0 1 Discrete Data #6 X
0 0 3 1 0 1 1 1 1 0 1 Discrete Data #6 X
0 1 8 1 0 1 1 1 1 0 1 Discrete Data #6 X
0 1 C 1 0 1 1 1 1 0 1 Discrete Data #6 X
0 2 5 1 0 1 1 1 1 0 1 Discrete Data #6 X
0 2 9 1 0 1 1 1 1 0 1 Discrete Data #6 X
0 2 B 1 0 1 1 1 1 0 1 Discrete Data #6 X
0 2 F 1 0 1 1 1 1 0 1 Discrete Data #6 X
0 3 5 1 0 1 1 1 1 0 1 Discrete Data #6 X
2 7 5 0 3 8 1 0 1 1 1 1 0 1 IR Discrete Word #2 X
0 3 B 1 0 1 1 1 1 0 1 Discrete Data #6 X
0 3 F 1 0 1 1 1 1 0 1 Discrete Data #6 X
0 4 A 1 0 1 1 1 1 0 1 T/U CAP-R Tank 5-8 X
0 4 D 1 0 1 1 1 1 0 1 Discrete Data #6 X
0 5 A 1 0 1 1 1 1 0 1 Discrete Data #6 X
0 5 6 1 0 1 1 1 1 0 1 Discrete Data #6 X
0 6 0 1 0 1 1 1 1 0 1 Discrete Data #6 X
1 0 A 1 0 1 1 1 1 0 1 Discrete Data #6 X
1 0 B 1 0 1 1 1 1 0 1 Discrete Data #6 X
1 1 4 1 0 1 1 1 1 0 1 Miscellaneous Warning X
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 34
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 2 1 0 1 1 1 1 1 0 Discrete Data #7 X
0 1 8 1 0 1 1 1 1 1 0 Discrete Data #7 X
0 1 C 1 0 1 1 1 1 1 0 Discrete Data #7 X
0 2 5 1 0 1 1 1 1 1 0 Discrete Status 8 EFIS X
0 2 9 1 0 1 1 1 1 1 0 Discrete Data #7 X
0 2 F 1 0 1 1 1 1 1 0 Discrete Data #7 X
0 3 F 1 0 1 1 1 1 1 0 Discrete Data #7 X
0 4 D 1 0 1 1 1 1 1 0 T/U CAP-R Tank 9-12 X
2 7 6 0 5 6 1 0 1 1 1 1 1 0 Discrete Data #7 X
0 5 8 1 0 1 1 1 1 1 0 Output Status Word #2 X
0 5 A 1 0 1 1 1 1 1 0 Discrete Data #7 X
0 6 0 1 0 1 1 1 1 1 0 Discrete Data #7 X
0 B B 1 0 1 1 1 1 1 0 Discrete Data #7 X
1 1 4 1 0 1 1 1 1 1 0 Discrete Data #7 X
0 0 1 1 0 1 1 1 1 1 0 FCC to Simulator Control Word - Simulator Use Only X
0 0 2 1 0 1 1 1 1 1 0 FMC to Simulator Control Word - Simulator Use Only X
0 0 3 1 0 1 1 1 1 1 0 TCC to Simulator Control Word - Simulator Use Only X
X X X 1 0 1 1 1 1 1 1 General Test Word X Note 1
0 0 4 1 0 1 1 1 1 1 1 IRS Maintenance Discrete X
0 1 8 1 0 1 1 1 1 1 1 Discrete Data #8 X
2 7 7
0 3 8 1 0 1 1 1 1 1 1 IR Test X
0 4 D 1 0 1 1 1 1 1 1 T/U CAP-R Tank 13-14 X
1 1 4 1 0 1 1 1 1 1 1 Fuel Transfer and CG Status X
0 0 1 1 1 0 0 0 0 0 0 Application Dependent X
0 1 A 1 1 0 0 0 0 0 0 Application Dependent X
0 3 D 1 1 0 0 0 0 0 0 Application Dependent X
0 5 A 1 1 0 0 0 0 0 0 Internal Parameter for SPATIAAL X
3 0 0
1 0 A 1 1 0 0 0 0 0 0 ECU Internal Temperature X
1 0 B 1 1 0 0 0 0 0 0 ECU Internal Temperature X
T B D 1 1 0 0 0 0 0 0 Data Loader Address Label (Low Speed) X
1 1 0 0 0 0 0 0 System Address Label for FMC 1 X See Attachment 11
0 0 1 1 1 0 0 0 0 0 1 Application Dependent X
0 0 2 1 1 0 0 0 0 0 1 Application Dependent X
0 1 A 1 1 0 0 0 0 0 1 Application Dependent X
0 5 6 1 1 0 0 0 0 0 1 Application Dependent X
3 0 1 0 5 A 1 1 0 0 0 0 0 1 Internal Parameter for SPATIAAL X
0 6 0 1 1 0 0 0 0 0 1 Application Dependent X
1 0 A 1 1 0 0 0 0 0 1 Demanded Fuel Metering Valve Position X
1 0 B 1 1 0 0 0 0 0 1 Demanded Fuel Metering Valve Position X
1 1 0 0 0 0 0 1 System Address Label for FMC 2 X See Attachment 11
0 0 1 1 1 0 0 0 0 1 0 Application Dependent X
0 0 2 1 1 0 0 0 0 1 0 Application Dependent X
0 1 A 1 1 0 0 0 0 1 0 Application Dependent X
0 5 6 1 1 0 0 0 0 1 0 Application Dependent X
3 0 2 0 5 A 1 1 0 0 0 0 1 0 Internal Parameter for SPATIAAL X
0 6 0 1 1 0 0 0 0 1 0 Application Dependent X
1 0 A 1 1 0 0 0 0 1 0 Demanded Variable Stator Vane Position X
1 0 B 1 1 0 0 0 0 1 0 Demanded Variable Stator Vane Position X
1 1 0 0 0 0 1 0 System Address Label for AIDS (DFDAU) X See Attachment 11
0 0 1 1 1 0 0 0 0 1 1 Application Dependent X
0 0 2 1 1 0 0 0 0 1 1 Application Dependent X
0 1 A 1 1 0 0 0 0 1 1 Application Dependent X
0 5 6 1 1 0 0 0 0 1 1 Application Dependent X
3 0 3 0 5 A 1 1 0 0 0 0 1 1 Internal Parameter for SPATIAAL X
0 6 0 1 1 0 0 0 0 1 1 Application Dependent X
1 0 A 1 1 0 0 0 0 1 1 Demanded Variable Bleed Valve Position X
1 0 B 1 1 0 0 0 0 1 1 Demanded Variable Bleed Valve Position X
1 1 0 0 0 0 1 1 System Address Label for CFDIU X See attachment 11
0 0 1 1 1 0 0 0 1 0 0 Application Dependent X
0 1 A 1 1 0 0 0 1 0 0 Application Dependent X
0 5 A 1 1 0 0 0 1 0 0 Internal Parameter for SPATIAAL X
3 0 4
1 0 A 1 1 0 0 0 1 0 0 Demanded HPT Clearance Valve Position X
1 0 B 1 1 0 0 0 1 0 0 Demanded HPT Clearance Valve Position X
1 1 0 0 0 1 0 0 System Address Label for ACARS X See Attachment 11
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 35
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 1 1 1 0 0 0 1 0 1 Application Dependent X
0 1 A 1 1 0 0 0 1 0 1 Application Dependent X
0 5 A 1 1 0 0 0 1 0 1 Internal Parameter for SPATIAAL X
3 0 5
1 0 A 1 1 0 0 0 1 0 1 Demanded LPT Clearance Valve Position X
1 0 B 1 1 0 0 0 1 0 1 Demanded LPT Clearance Valve Position X
1 1 0 0 0 1 0 1 System Address Label for Weight/Balance System X See Attachment 11
0 0 1 1 1 0 0 0 1 1 0 Application Dependent X
0 1 A 1 1 0 0 0 1 1 0 Application Dependent X
3 0 6
0 5 A 1 1 0 0 0 1 1 0 Internal Parameter for SPATIAAL X
1 1 0 0 0 1 1 0 System Address Label for TCAS X See Attachment 11
0 0 1 1 1 0 0 0 1 1 1 Application Dependent X
0 1 A 1 1 0 0 0 1 1 1 Application Dependent X
3 0 7
0 5 A 1 1 0 0 0 1 1 1 Internal Parameter for SPATIAAL X
1 1 0 0 0 1 1 1 System Address Label for Satellite Data Unit (SDI) X See Attachment 11
0 0 2 1 1 0 0 1 0 0 0 Present Position - Latitude X 6-27
0 0 4 1 1 0 0 1 0 0 0 Present Position - Latitude X
0 2 9 1 1 0 0 1 0 0 0 Aileron Position X
0 3 8 1 1 0 0 1 0 0 0 Present Position - Latitude X
0 4 D 1 1 0 0 1 0 0 0 COMP CAP - TANK X
3 1 0
0 5 6 1 1 0 0 1 0 0 0 Present Position Latitude X
0 5 A 1 1 0 0 1 0 0 0 Internal Parameter for SPATIAAL X
0 6 0 1 1 0 0 1 0 0 0 Present Postion Latitude X
1 1 4 1 1 0 0 1 0 0 0 Right Outer Tank Fuel Quantity X
1 1 0 0 1 0 0 0 System Address Label for GPWS X See Attachment 11
0 0 2 1 1 0 0 1 0 0 1 Present Position - Longitude X 6-27
0 0 4 1 1 0 0 1 0 0 1 Present Position - Longitude X
0 2 9 1 1 0 0 1 0 0 1 Aileron Trim X
0 3 8 1 1 0 0 1 0 0 1 Present Position - Longitude X
0 3 B 1 1 0 0 1 0 0 1 Control Wheel Roll Force X
3 1 1
0 5 6 1 1 0 0 1 0 0 1 Present Postion Longitude X
0 5 A 1 1 0 0 1 0 0 1 Internal Parameter for SPATIAAL X
0 6 0 1 1 0 0 1 0 0 1 Present Position Longitude X
1 1 4 1 1 0 0 1 0 0 1 Right Outer Tank Fuel Quantity X
1 1 0 0 1 0 0 1 System Address Label for GNLU 1 X See Attachment 11
0 0 2 1 1 0 0 1 0 1 0 Ground Speed X 6-27
0 0 4 1 1 0 0 1 0 1 0 Ground Speed X
0 0 5 1 1 0 0 1 0 1 0 Ground Speed X
0 2 9 1 1 0 0 1 0 1 0 Rudder Position X
0 3 8 1 1 0 0 1 0 1 0 Ground Speed X
3 1 2
0 5 6 1 1 0 0 1 0 1 0 Ground Speed X
0 5 A 1 1 0 0 1 0 1 0 Fuel Quantity ACT 1 X
0 6 0 1 1 0 0 1 0 1 0 Ground Speed X
1 1 4 1 1 0 0 1 0 1 0 Additional Center Tank (Act 1) Fuel Quantity X
1 1 0 0 1 0 1 0 System Address Label for GNLU 2 X See Attachment 11
0 0 2 1 1 0 0 1 0 1 1 Track Angle - True X
0 0 4 1 1 0 0 1 0 1 1 Track Angle - True X
0 2 5 1 1 0 0 1 0 1 1 Track Angle - True X
0 2 9 1 1 0 0 1 0 1 1 Rudder Trim X
0 3 8 1 1 0 0 1 0 1 1 Track Angle - True X
3 1 3
0 5 6 1 1 0 0 1 0 1 1 Track Angle - True X
0 5 A 1 1 0 0 1 0 1 1 Fuel Quantity ACT 2 X
0 6 0 1 1 0 0 1 0 1 1 Track Angle - True X
1 1 4 1 1 0 0 1 0 1 1 Additional Center Tank (Act 2) Fuel Quantity X
1 1 0 0 1 0 1 1 System Address Label for GNLU 3 X See Attachment 11
0 0 2 1 1 0 0 1 1 0 0 Stabilizer Position Indication (B747-400) X
0 0 4 1 1 0 0 1 1 0 0 True Heading X
0 2 5 1 1 0 0 1 1 0 0 True Heading X
0 2 9 1 1 0 0 1 1 0 0 Elevator Position X
3 1 4 0 3 8 1 1 0 0 1 1 0 0 True Heading X
0 3 B 1 1 0 0 1 1 0 0 Control Wheel Pitch Force X
0 5 A 1 1 0 0 1 1 0 0 Internal Parameter for SPATIAAL X
1 1 4 1 1 0 0 1 1 0 0 Rear Center Tank (RCT) Fuel Quantity X
1 1 0 0 1 1 0 0 System Address Label for GNU 1 X See Attachment 11
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 36
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 1 1 1 0 0 1 1 0 1 Stabilizer Position X
0 0 2 1 1 0 0 1 1 0 1 Wind Speed X
0 0 4 1 1 0 0 1 1 0 1 Wind Speed X
0 0 5 1 1 0 0 1 1 0 1 Wind Speed X
0 2 9 1 1 0 0 1 1 0 1 Stabilizer Position X
3 1 5 0 3 8 1 1 0 0 1 1 0 1 Wind Speed X
0 5 6 1 1 0 0 1 1 0 1 Wind Speed X
0 5 A 1 1 0 0 1 1 0 1 Internal Parameter for SPATIAAL X
0 6 0 1 1 0 0 1 1 0 1 Wind Speed X
0 A 1 1 1 0 0 1 1 0 1 Stabilizer Position X
1 1 0 0 1 1 0 1 System Address Label for GNU 2 X See Attachment 11
0 0 2 1 1 0 0 1 1 1 0 Wind Direction (True) X
0 0 4 1 1 0 0 1 1 1 0 Wind Angle X
0 2 9 1 1 0 0 1 1 1 0 Oil Temperature (Engine) X
0 3 8 1 1 0 0 1 1 1 0 Wind Angle X
0 5 6 1 1 0 0 1 1 1 0 Wind Direction (True) X
3 1 6 0 5 A 1 1 0 0 1 1 1 0 Internal Parameter for SPATIAAL X
0 6 0 1 1 0 0 1 1 1 0 Wind Direction (True) X
0 D 0 1 1 0 0 1 1 1 0 Engine Oil Temperature X
1 0 A 1 1 0 0 1 1 1 0 Engine Oil Temperature X
1 0 B 1 1 0 0 1 1 1 0 Engine Oil Temperature X
1 1 0 0 1 1 1 0 System Address Label for GNU 3 X See Attachment 11
0 0 2 1 1 0 0 1 1 1 1 Track Angle - Magnetic X
0 0 4 1 1 0 0 1 1 1 1 Track Angle - Magnetic X
0 0 5 1 1 0 0 1 1 1 1 Track Angle - Magnetic X
0 2 5 1 1 0 0 1 1 1 1 Track Angle - Magnetic X
0 2 9 1 1 0 0 1 1 1 1 Oil Pressure (Engine) X
3 1 7
0 3 8 1 1 0 0 1 1 1 1 Track Angle - Magnetic X
0 5 6 1 1 0 0 1 1 1 1 Track Angle - Magnetic X
0 5 A 1 1 0 0 1 1 1 1 Internal Parameter for SPATIAAL X
0 6 0 1 1 0 0 1 1 1 1 Track Angle - Magnetic X
0 D 0 1 1 0 0 1 1 1 1 Oil Pressure (Engine) X
0 0 4 1 1 0 1 0 0 0 0 Magnetic Heading X
0 0 5 1 1 0 1 0 0 0 0 Magnetic Heading X
0 2 5 1 1 0 1 0 0 0 0 Magnetic Heading X
0 2 9 1 1 0 1 0 0 0 0 Engine Fuel Pressure X
0 3 5 1 1 0 1 0 0 0 0 Own Aircraft Magnetic Heading X
3 2 0
0 3 8 1 1 0 1 0 0 0 0 Magnetic Heading X
0 4 D 1 1 0 1 0 0 0 0 Density - Tank X
0 5 A 1 1 0 1 0 0 0 0 Fuel Quantity Act 3 X
0 5 6 1 1 0 1 0 0 0 0 Magnetic Heading X
0 6 0 1 1 0 1 0 0 0 0 Magnetic Heading X
0 0 2 1 1 0 1 0 0 0 1 Drift Angle X
0 0 4 1 1 0 1 0 0 0 1 Drift Angle X
0 0 5 1 1 0 1 0 0 0 1 Drift Angle X
0 2 9 1 1 0 1 0 0 0 1 Engine Fuel Temperature X
0 3 8 1 1 0 1 0 0 0 1 Drift Angle X
3 2 1
0 5 6 1 1 0 1 0 0 0 1 Drift Angle X
0 6 0 1 1 0 1 0 0 0 1 Drift Angle X
1 0 A 1 1 0 1 0 0 0 1 Exhaust gas Temperature (Total) X
1 0 B 1 1 0 1 0 0 0 1 Exhaust gas Temperature (Total) X
1 1 0 1 0 0 0 1 System Address label for Autothrottle Computer X See Attachment 11
0 0 2 1 1 0 1 0 0 1 0 Flight Path Angle X
0 0 4 1 1 0 1 0 0 1 0 Flight Path Angle X
0 0 5 1 1 0 1 0 0 1 0 Flight Path Angle X
0 2 9 1 1 0 1 0 0 1 0 Engine Nacelle Temperature X
0 3 8 1 1 0 1 0 0 1 0 Flight Path Angle X
3 2 2
0 5 6 1 1 0 1 0 0 1 0 Flight Path Angle X
0 6 0 1 1 0 1 0 0 1 0 Flight Path Angle X
1 0 A 1 1 0 1 0 0 1 0 Total Compressor Discharge Temperature X
1 0 B 1 1 0 1 0 0 1 0 Total Compressor Discharge Temperature X
1 1 0 1 0 0 1 0 System Address Label for FCC 1 X See Attachment 11
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 37
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 2 1 1 0 1 0 0 1 1 Geometric Altitude X
0 0 4 1 1 0 1 0 0 1 1 Flight Path Acceleration X 6-27
0 0 5 1 1 0 1 0 0 1 1 Flight Path Acceleration X
0 3 8 1 1 0 1 0 0 1 1 Flight Path Acceleration X
3 2 3 0 5 6 1 1 0 1 0 0 1 1 Geometric Altitude X
0 6 0 1 1 0 1 0 0 1 1 Geometric Altitude X
1 0 A 1 1 0 1 0 0 1 1 Variable Stator Vane Position X
1 0 B 1 1 0 1 0 0 1 1 Variable Stator Vane Position X
1 1 0 1 0 0 1 1 System Address Label for FCC 2 X See Attachment 11
0 0 4 1 1 0 1 0 1 0 0 Pitch Angle X
0 0 5 1 1 0 1 0 1 0 0 Pitch Angle X
0 2 5 1 1 0 1 0 1 0 0 Pitch Angle X
0 3 8 1 1 0 1 0 1 0 0 Pitch Angle X
0 4 D 1 1 0 1 0 1 0 0 Tank VSO Quantity X
3 2 4
0 5 A 1 1 0 1 0 1 0 0 Effective Pitch Angle X
1 0 A 1 1 0 1 0 1 0 0 Selected Fuel Metering Valve Position X
1 0 B 1 1 0 1 0 1 0 0 Selected Fuel Metering Valve Position X
1 1 4 1 1 0 1 0 1 0 0 Effective Pitch Angle X
1 1 0 1 0 1 0 0 System Address Label for FCC 3 X See Attachment 11
0 0 4 1 1 0 1 0 1 0 1 Roll Angle X
0 0 5 1 1 0 1 0 1 0 1 Roll Angle X
0 1 A 1 1 0 1 0 1 0 1 Engine Control Trim Feedback X
0 2 5 1 1 0 1 0 1 0 1 Roll Angle X
0 2 F 1 1 0 1 0 1 0 1 Stator Vane Feedback X
0 3 8 1 1 0 1 0 1 0 1 Roll Angle X
3 2 5
0 3 F 1 1 0 1 0 1 0 1 Stator Vane Feedback X
0 5 A 1 1 0 1 0 1 0 1 Effective Roll Angle X
1 0 A 1 1 0 1 0 1 0 1 Selected Fuel Metering Vane Position X
1 0 B 1 1 0 1 0 1 0 1 Selected Fuel Metering Vane Position X
1 1 4 1 1 0 1 0 1 0 1 Effective Roll Angle X
1 1 0 1 0 1 0 1 System Address Label for APU X See Attachment 11
0 0 4 1 1 0 1 0 1 1 0 Body Pitch Rate X
0 0 5 1 1 0 1 0 1 1 0 Body Pitch Rate X
0 3 8 1 1 0 1 0 1 1 0 Body Pitch Rate X
0 4 D 1 1 0 1 0 1 1 0 Uplift Quantity X
3 2 6
0 5 A 1 1 0 1 0 1 1 0 Maintenance Word X
1 0 A 1 1 0 1 0 1 1 0 Compressor Discharge Static Pressure X
1 0 B 1 1 0 1 0 1 1 0 Compressor Discharge Static Pressure X
1 1 0 1 0 1 1 0 System Address Label for APU Controller X See Attachment 11
0 0 4 1 1 0 1 0 1 1 1 Body Roll Rate X
0 0 5 1 1 0 1 0 1 1 1 Body Roll Rate X
0 3 8 1 1 0 1 0 1 1 1 Body Roll Rate X
3 2 7 0 4 D 1 1 0 1 0 1 1 1 Uplift Density X
1 0 A 1 1 0 1 0 1 1 1 Fuel Metering Valve Position X
1 0 B 1 1 0 1 0 1 1 1 Fuel Metering Valve Position X
1 1 0 1 0 1 1 1 SAL Mode Control Panel (MCP) X
0 0 4 1 1 0 1 1 0 0 0 Body Yaw Rate X
0 0 5 1 1 0 1 1 0 0 0 Body Yaw Rate X
0 2 F 1 1 0 1 1 0 0 0 HC/TC Cooling Valve Position Feedback X
0 3 8 1 1 0 1 1 0 0 0 Body Yaw Rate X
3 3 0
0 3 F 1 1 0 1 1 0 0 0 HC/TC Cooling Valve Position Feedback X
1 0 A 1 1 0 1 1 0 0 0 Selected HPT Clearance Valve Postion X
1 0 B 1 1 0 1 1 0 0 0 Selected HPT Clearance Valve Postion X
1 1 0 1 1 0 0 0 System Address Label for FMC 3 X See Attachment 11
0 0 4 1 1 0 1 1 0 0 1 Body Longitudinal Acceleration X
0 0 5 1 1 0 1 1 0 0 1 Body Longitudinal Acceleration X
0 2 F 1 1 0 1 1 0 0 1 LTC Cooling Valve Position Feedback X
0 3 8 1 1 0 1 1 0 0 1 Body Longitudinal Acceleration X
3 3 1
0 3 F 1 1 0 1 1 0 0 1 LTC Cooling Valve Position Feedback X
1 0 A 1 1 0 1 1 0 0 1 Selected LPT Clearance Valve Position X
1 0 B 1 1 0 1 1 0 0 1 Selected LPT Clearance Valve Position X
1 1 0 1 1 0 0 1 System Address Label for ATC Transponder X See Attachment 11
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 38
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 4 1 1 0 1 1 0 1 0 Body Lateral Acceleration X

0 0 5 1 1 0 1 1 0 1 0 Body Lateral Acceleration X
0 2 F 1 1 0 1 1 0 1 0 A/O Heat Exchanger Valve Postion Feedback X
3 3 2
0 3 8 1 1 0 1 1 0 1 0 Body Lateral Acceleration X
0 3 F 1 1 0 1 1 0 1 0 A/O Heat Exchanger Valve Postion Feedback X
1 1 0 1 1 0 1 0 System Address Label for DADC X See Attachment 11
0 0 4 1 1 0 1 1 0 1 1 Body Normal Acceleration X
0 0 5 1 1 0 1 1 0 1 1 Body Normal Acceleration X
3 3 3 0 2 F 1 1 0 1 1 0 1 1 Acceleration Fuel Flow Limit X
0 3 8 1 1 0 1 1 0 1 1 Body Normal Acceleration X
0 3 F 1 1 0 1 1 0 1 1 Acceleration Fuel Flow Limit X
0 0 4 1 1 0 1 1 1 0 0 Platform Heading X
0 0 5 1 1 0 1 1 1 0 0 Platform Heading X
0 2 F 1 1 0 1 1 1 0 0 Fuel Flow Command X
3 3 4
0 3 8 1 1 0 1 1 1 0 0 Platform Heading X
0 3 F 1 1 0 1 1 1 0 0 Fuel Flow Command X
1 1 0 1 1 1 0 0 CTU - System Address Label X See Attachment 11
0 0 2 1 1 0 1 1 1 0 1 Track Angle Rate X
0 0 4 1 1 0 1 1 1 0 1 Track Angle Rate X
0 0 5 1 1 0 1 1 1 0 1 Track Angle Rate X
0 2 F 1 1 0 1 1 1 0 1 2.5 Bld Actuator Postion X
0 3 8 1 1 0 1 1 1 0 1 Track Angle Rate X
3 3 5
0 3 F 1 1 0 1 1 1 0 1 2.5 Bld Actuator Postion X
0 5 6 1 1 0 1 1 1 0 1 Track Angle Rate X
0 6 0 1 1 0 1 1 1 0 1 Track Angle Rate X
1 0 A 1 1 0 1 1 1 0 1 Selected Variable Bleed Valve Position X
1 0 B 1 1 0 1 1 1 0 1 Selected Variable Bleed Valve Position X
0 0 2 1 1 0 1 1 1 1 0 Maximum Climb Angle X
0 0 4 1 1 0 1 1 1 1 0 Inertial Pitch Rate X
0 0 5 1 1 0 1 1 1 1 0 Inertial Pitch Rate X
0 1 A 1 1 0 1 1 1 1 0 Engine Torque X
3 3 6 0 2 F 1 1 0 1 1 1 1 0 N2 Corrected to Sta. 2.5 X
0 3 8 1 1 0 1 1 1 1 0 Inertial Pitch Rate X
0 3 F 1 1 0 1 1 1 1 0 N2 Corrected to Sta. 2.5 X
1 0 A 1 1 0 1 1 1 1 0 Variable Bleed Value Position X
1 0 B 1 1 0 1 1 1 1 0 Variable Bleed Value Position X
0 0 2 1 1 0 1 1 1 1 1 EPR - Required for Level Flight X
0 0 2 1 1 0 1 1 1 1 1 N1 - Required for Level Flight X
0 0 4 1 1 0 1 1 1 1 1 Inertial Roll Rate X
0 0 5 1 1 0 1 1 1 1 1 Inertial Roll Rate X
3 3 7
0 1 A 1 1 0 1 1 1 1 1 Engine Rating X
0 3 8 1 1 0 1 1 1 1 1 Inertial Roll Rate X
1 0 A 1 1 0 1 1 1 1 1 HPT Clearance Valve Position X
1 0 B 1 1 0 1 1 1 1 1 HPT Clearance Valve Position X
0 0 3 1 1 1 0 0 0 0 0 EPR Actual X
0 0 4 1 1 1 0 0 0 0 0 Inertial Yaw Rate X
0 0 4 1 1 1 0 0 0 0 0 Track Angle Rate X
0 0 5 1 1 1 0 0 0 0 0 Inertial Yaw Rate X
0 1 A 1 1 1 0 0 0 0 0 EPR Actual X
0 2 9 1 1 1 0 0 0 0 0 EPR Actual (Engine Direct) X
3 4 0 0 2 D 1 1 1 0 0 0 0 0 EPR Actual X
0 2 F 1 1 1 0 0 0 0 0 EPR Actual X
0 3 3 1 1 1 0 0 0 0 0 EPR Actual X
0 3 F 1 1 1 0 0 0 0 0 EPR Actual X
1 3 A 1 1 1 0 0 0 0 0 N1 Take Off X
1 4 0 1 1 1 0 0 0 0 0 Pressure Ratio (Pt/Ps) X
1 1 1 0 0 0 0 0 HF DATA Radio/Data #1 - System Address Label X See Attachment 11
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 39
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 2 1 1 1 0 0 0 0 1 Target N1 X
0 0 3 1 1 1 0 0 0 0 1 N1 Command X
0 0 3 1 1 1 0 0 0 0 1 EPR Command X
0 0 4 1 1 1 0 0 0 0 1 Grid Heading X
0 1 A 1 1 1 0 0 0 0 1 N1 Command X
0 1 A 1 1 1 0 0 0 0 1 EPR Command X
0 2 9 1 1 1 0 0 0 0 1 N1 Command (Engine) X
0 2 9 1 1 1 0 0 0 0 1 EPR Command (Engine) X
3 4 1 0 2 F 1 1 1 0 0 0 0 1 N1 Command X
0 2 F 1 1 1 0 0 0 0 1 EPR Command X
0 3 8 1 1 1 0 0 0 0 1 Grid Heading X
0 3 F 1 1 1 0 0 0 0 1 EPR Command X
0 4 D 1 1 1 0 0 0 0 1 I/O S/W REV 1&2 X
1 0 A 1 1 1 0 0 0 0 1 Command Fan Speed X
1 0 B 1 1 1 0 0 0 0 1 Command Fan Speed X
1 3 A 1 1 1 0 0 0 0 1 N1 Reference X
1 4 0 1 1 1 0 0 0 0 1 Pressure Ratio (Ps/Pso) X
0 0 2 1 1 1 0 0 0 1 0 N1 Bug Drive X
0 0 3 1 1 1 0 0 0 1 0 N1 Limit X
0 0 3 1 1 1 0 0 0 1 0 EPR Limit X
0 1 A 1 1 1 0 0 0 1 0 N1 Maximum X
0 1 A 1 1 1 0 0 0 1 0 EPR Maximum X
0 2 9 1 1 1 0 0 0 1 0 N1 Limit (TCC) X
0 2 9 1 1 1 0 0 0 1 0 EPR Limit (TOC) X
3 4 2 0 2 F 1 1 1 0 0 0 1 0 Maximum Available EPR X
0 3 B 1 1 1 0 0 0 1 0 N1 Limit X
0 3 B 1 1 1 0 0 0 1 0 EPR Limit X
0 3 F 1 1 1 0 0 0 1 0 Maximum Available EPR X
0 4 D 1 1 1 0 0 0 1 0 S/W Rev-Tank X
1 0 A 1 1 1 0 0 0 1 0 Maximum Allowed Fan Speed X
1 0 B 1 1 1 0 0 0 1 0 Maximum Allowed Fan Speed X
1 4 0 1 1 1 0 0 0 1 0 Air Density Ratio X
0 0 3 1 1 1 0 0 0 1 1 N1 Derate X
0 0 3 1 1 1 0 0 0 1 1 EPR Rate X
3 4 3 0 1 A 1 1 1 0 0 0 1 1 N1 Demand X
1 0 A 1 1 1 0 0 0 1 1 N1 Command vs. TLA X
1 0 B 1 1 1 0 0 0 1 1 N1 Command vs. TLA X
0 1 A 1 1 1 0 0 1 0 0 N2 X
0 1 C 1 1 1 0 0 1 0 0 N2 X
0 2 9 1 1 1 0 0 1 0 0 N2 X
0 2 F 1 1 1 0 0 1 0 0 N2 X
0 3 3 1 1 1 0 0 1 0 0 N2 X
0 3 F 1 1 1 0 0 1 0 0 N2 X
3 4 4
0 4 D 1 1 1 0 0 1 0 0 Fuel Discretes X
0 D 0 1 1 1 0 0 1 0 0 N2 X
1 0 A 1 1 1 0 0 1 0 0 Selected Actual Core Speed X
1 0 B 1 1 1 0 0 1 0 0 Selected Actual Core Speed X
1 3 A 1 1 1 0 0 1 0 0 N2 Speed X
1 1 1 0 0 1 0 0 HF DATA Radio/Data #2 - System Address Label X See Attachment 11
0 0 2 1 1 1 0 0 1 0 1 NDB Effectivity X
0 1 A 1 1 1 0 0 1 0 1 Exhaust Gas Temperature X
0 1 C 1 1 1 0 0 1 0 1 Exhaust Gas Temperature X
0 2 9 1 1 1 0 0 1 0 1 Exhaust Gas Temperature X
0 2 F 1 1 1 0 0 1 0 1 Exhaust Gas Temperature X
0 3 3 1 1 1 0 0 1 0 1 Exhaust Gas Temperature X
3 4 5
0 3 F 1 1 1 0 0 1 0 1 Exhaust Gas Temperature X
0 4 D 1 1 1 0 0 1 0 1 Discretes Status 1&3 X
0 D 0 1 1 1 0 0 1 0 1 EGT X
1 0 A 1 1 1 0 0 1 0 1 Selected Exhaust Gas Temperature (Total) X
1 0 B 1 1 1 0 0 1 0 1 Selected Exhaust Gas Temperature (Total) X
1 3 A 1 1 1 0 0 1 0 1 EGT Trimmed X
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 40
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 3 1 1 1 0 0 1 1 0 N1 Actual X
0 1 A 1 1 1 0 0 1 1 0 N1 Actual X
0 2 F 1 1 1 0 0 1 1 0 N1 Actual X
0 3 3 1 1 1 0 0 1 1 0 N1 Actual X
0 3 F 1 1 1 0 0 1 1 0 N1 Actual X
3 4 6
0 4 D 1 1 1 0 0 1 1 0 Cable Cap-Hi-Z X
0 D 0 1 1 1 0 0 1 1 0 N1 X
1 0 A 1 1 1 0 0 1 1 0 Selected Actual Fan Speed X
1 0 B 1 1 1 0 0 1 1 0 Selected Actual Fan Speed X
1 3 A 1 1 1 0 0 1 1 0 N1 Speed Actual X
0 1 8 1 1 1 0 0 1 1 1 Antenna Control X
0 2 9 1 1 1 0 0 1 1 1 Fuel Flow (Engine) X
0 3 0 1 1 1 0 0 1 1 1 Sector Control X
0 3 5 1 1 1 0 0 1 1 1 Antenna Control X
3 4 7
0 D 0 1 1 1 0 0 1 1 1 Fuel Flow X
1 0 A 1 1 1 0 0 1 1 1 LPT Clearance Valve Position X
1 0 B 1 1 1 0 0 1 1 1 LPT Clearance Valve Position X
1 3 A 1 1 1 0 0 1 1 1 Fuel Flow X
0 0 3 1 1 1 0 1 0 0 0 Maintenance Data #1 X
0 0 4 1 1 1 0 1 0 0 0 IRS Maintenance Discrete X
0 0 6 1 1 1 0 1 0 0 0 Maintenance Data #1 X
0 0 B 1 1 1 0 1 0 0 0 GPS Test Word (manufacturer specific) X
0 1 8 1 1 1 0 1 0 0 0 Maintenance Data #1 X
0 1 9 1 1 1 0 1 0 0 0 CFDS Bite Fault Summary Word for HFDR X
0 1 A 1 1 1 0 1 0 0 0 Maintenance Data #1 X
0 1 C 1 1 1 0 1 0 0 0 Maintenance Data #1 X
0 2 3 1 1 1 0 1 0 0 0 Maintenance Data #1 X
0 2 4 1 1 1 0 1 0 0 0 MU Output Data Word Failure Status X
0 2 5 1 1 1 0 1 0 0 0 Maintenance Data #1 X
0 2 7 1 1 1 0 1 0 0 0 Maintenance Data #1 X
0 2 9 1 1 1 0 1 0 0 0 Maintenance Data #1 X
0 2 F 1 1 1 0 1 0 0 0 Maintenance Data #1 X
0 3 2 1 1 1 0 1 0 0 0 Maintenance Data #1 X
0 3 5 1 1 1 0 1 0 0 0 Maintenance Data #1 X
3 5 0 0 3 8 1 1 1 0 1 0 0 0 IRS Maintenance Word #1 X
0 3 D 1 1 1 0 1 0 0 0 Maintenance Data #1 X
0 3 E 1 1 1 0 1 0 0 0 Maintenance Data #1 X
0 3 F 1 1 1 0 1 0 0 0 Maintenance Data #1 X
0 4 0 1 1 1 0 1 0 0 0 Maintenance Data #1 X
0 4 D 1 1 1 0 1 0 0 0 Maintenance Data FQIS 1-3 X
0 5 0 1 1 1 0 1 0 0 0 VDR Fault Summary Word X
0 5 3 1 1 1 0 1 0 0 0 CFDS Bite Fault Summary Word for HFDR X
0 5 5 1 1 1 0 1 0 0 0 ILS Maintenance Word X
0 5 8 1 1 1 0 1 0 0 0 Maintenance Word #1 X
1 0 A 1 1 1 0 1 0 0 0 Maintenance Data #1 X
1 0 B 1 1 1 0 1 0 0 0 Maintenance Data #1 X
1 1 4 1 1 1 0 1 0 0 0 Fuel Density X
1 1 5 1 1 1 0 1 0 0 0 Maintenance Data #1 X
1 4 0 1 1 1 0 1 0 0 0 Maintenance Data #1 X
2 4 1 1 1 1 0 1 0 0 0 Maintenance Data #1 X
3 4 1 1 1 1 0 1 0 0 0 Maintenance Data #1 X
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 41
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 6 1 1 1 0 1 0 0 1 Maintenance Data #2 X
0 0 B 1 1 1 0 1 0 0 1 SRU Test Word (manufacturer specific) X
0 1 A 1 1 1 0 1 0 0 1 Maintenance Data #2 X
0 1 C 1 1 1 0 1 0 0 1 Maintenance Data #2 X
0 2 4 1 1 1 0 1 0 0 1 MU Output Data Word Failure Status X
0 2 5 1 1 1 0 1 0 0 1 Maintenance Data #2 X
0 2 9 1 1 1 0 1 0 0 1 Maintenance Data #2 X
0 2 E 1 1 1 0 1 0 0 1 Maintenance Data #2 X
0 2 F 1 1 1 0 1 0 0 1 Maintenance Data #2 X
3 5 1 0 3 1 1 1 1 0 1 0 0 1 Maintenance Data #2 X
0 3 8 1 1 1 0 1 0 0 1 IRS Maintenance Word #2 X
0 3 F 1 1 1 0 1 0 0 1 Maintenance Data #2 X
0 4 D 1 1 1 0 1 0 0 1 Maintenance Data FQIS 1&3 X
0 5 5 1 1 1 0 1 0 0 1 MMR Maintenance Word X
0 5 8 1 1 1 0 1 0 0 1 Maintenance Word #2 X
1 0 A 1 1 1 0 1 0 0 1 Maintenance Data #2 X
1 0 B 1 1 1 0 1 0 0 1 Maintenance Data #2 X
1 1 4 1 1 1 0 1 0 0 1 Inner Tank 1 Probe Capacitance X
1 4 0 1 1 1 0 1 0 0 1 Maintenance Data #2 X
0 1 A 1 1 1 0 1 0 1 0 Maintenance Data #3 X
0 1 C 1 1 1 0 1 0 1 0 Maintenance Data #2 X
0 2 5 1 1 1 0 1 0 1 0 Maintenance Data #2 X
0 2 E 1 1 1 0 1 0 1 0 Maintenance Data #2 X
0 2 F 1 1 1 0 1 0 1 0 Maintenance Data #2 X
0 3 F 1 1 1 0 1 0 1 0 Maintenance Data #2 X
3 5 2 0 4 D 1 1 1 0 1 0 1 0 Maintenance Data FQIS 1-4 X
0 5 5 1 1 1 0 1 0 1 0 MLS Bite Status X
0 5 8 1 1 1 0 1 0 1 0 Maintenance Word X
1 0 A 1 1 1 0 1 0 1 0 Maintenance Data #2 X
1 0 B 1 1 1 0 1 0 1 0 Maintenance Data #2 X
1 1 4 1 1 1 0 1 0 1 0 Center, ACT & RCT Probe Capacitance X
1 4 0 1 1 1 0 1 0 1 0 Maintenance Data #3 Flight Count X
0 1 A 1 1 1 0 1 0 1 1 Maintenance Data #4 X
0 1 C 1 1 1 0 1 0 1 1 Maintenance Data #4 X
0 2 5 1 1 1 0 1 0 1 1 Maintenance Data #4 X
0 2 F 1 1 1 0 1 0 1 1 Maintenance Data #4 X
0 3 8 1 1 1 0 1 0 1 1 IRS Maintenance Word #3 X
0 3 D 1 1 1 0 1 0 1 1 Maintenance Data #4 X
3 5 3
0 3 F 1 1 1 0 1 0 1 1 Maintenance Data #4 X
0 4 D 1 1 1 0 1 0 1 1 Maintenance Data FQIS 1-4 X
0 D 0 1 1 1 0 1 0 1 1 Vibration X
1 0 A 1 1 1 0 1 0 1 1 Maintenance Data #4 X
1 0 B 1 1 1 0 1 0 1 1 Maintenance Data #4 X
1 1 4 1 1 1 0 1 0 1 1 Inner Tank 1 Probe Capacitance X
0 0 2 1 1 1 0 1 1 0 0 Maintenance Data #5 X
0 1 A 1 1 1 0 1 1 0 0 Maintenance Data #5 X
0 1 C 1 1 1 0 1 1 0 0 Maintenance Data #5 X
0 2 F 1 1 1 0 1 1 0 0 Maintenance Data #5 X
0 3 D 1 1 1 0 1 1 0 0 N1 Vibration X
0 3 F 1 1 1 0 1 1 0 0 Maintenance Data #5 X
3 5 4
0 4 D 1 1 1 0 1 1 0 0 FQIS Tank ID X
0 5 6 1 1 1 0 1 1 0 0 Maintenance Data #5
0 6 0 1 1 1 0 1 1 0 0 Maintenance Data #5
0 B B 1 1 1 0 1 1 0 0 Maintenance Data #5 X
1 0 A 1 1 1 0 1 1 0 0 Maintenance Data #5 X
1 0 B 1 1 1 0 1 1 0 0 Maintenance Data #5 X
0 0 B 1 1 1 0 1 1 0 1 GNSS Fault Summary X
0 2 7 1 1 1 0 1 1 0 1 MLS Maintenance Data X
0 3 8 1 1 1 0 1 1 0 1 IRS Maintenance Word #4 X
3 5 5
0 3 D 1 1 1 0 1 1 0 1 N2 Vibration X
0 4 D 1 1 1 0 1 1 0 1 Maintenance Data FQIS 2-4 X
X X X 1 1 1 0 1 1 0 1 Acknowledgement X 6-5/Note 1
0 3 D 1 1 1 0 1 1 1 0 N3 Vibration X
3 5 6 X X X 1 1 1 0 1 1 1 0 Maintenance ISO #5 Message X 6-3/Note 1
Y Y Y 1 1 1 0 1 1 1 0 BITE Status Word X Note 1
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 42
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 2 1 1 1 0 1 1 1 1 ISO Alphabet #5 Message X 6-3

0 1 7 1 1 1 0 1 1 1 1 ISO Alphabet #5 Message X
0 2 4 1 1 1 0 1 1 1 1 ISO Alphabet #5 Message X
0 3 5 1 1 1 0 1 1 1 1 TCAS Intruder Data File X
3 5 7 0 3 7 1 1 1 0 1 1 1 1 ISO Alphabet #5 Message X
0 3 D 1 1 1 0 1 1 1 1 BB Vibration X
0 4 D 1 1 1 0 1 1 1 1 Maintenance Data FQIS 2-3 X
0 5 6 1 1 1 0 1 1 1 1 ISO Alphabet #5 Message
0 6 0 1 1 1 0 1 1 1 1 ISO Alphabet #5 Message
0 0 2 1 1 1 1 0 0 0 0 Flight Information X 6-33
0 0 4 1 1 1 1 0 0 0 0 Potential Vertical Speed X
0 0 5 1 1 1 1 0 0 0 0 Potential Vertical Speed X
0 3 8 1 1 1 1 0 0 0 0 Potential Vertical Speed X
0 3 D 1 1 1 1 0 0 0 0 N1 Rotor Imbalance Angle X
3 6 0 0 5 6 1 1 1 1 0 0 0 0 Flight Information X
0 6 0 1 1 1 1 0 0 0 0 Flight Information X
1 0 A 1 1 1 1 0 0 0 0 Throttle Rate of Change X
1 0 B 1 1 1 1 0 0 0 0 Throttle Rate of Change X
1 4 2 1 1 1 1 0 0 0 0 RAIM Status Word X
1 1 1 1 0 0 0 0 ACESS System Address Label X See Attachment 11
0 0 4 1 1 1 1 0 0 0 1 Altitude (Inertial) X
0 0 5 1 1 1 1 0 0 0 1 Altitude (Inertial) X
0 3 8 1 1 1 1 0 0 0 1 Altitude (Inertial) X
3 6 1 0 3 D 1 1 1 1 0 0 0 1 LPT Rotor Imbalance Angle (737 only) X
1 0 A 1 1 1 1 0 0 0 1 Derivative of Thrust vs. N1 X
1 0 B 1 1 1 1 0 0 0 1 Derivative of Thrust vs. N1 X
1 1 1 1 0 0 0 1 EFIS System Address Label X See Attachment 11
0 0 4 1 1 1 1 0 0 1 0 Along Track Horizontal Acceleration X
0 3 8 1 1 1 1 0 0 1 0 Along Track Horizontal Acceleration X
1 0 A 1 1 1 1 0 0 1 0 Derivative of Thrust vs. TLA X
3 6 2
1 0 B 1 1 1 1 0 0 1 0 Derivative of Thrust vs. TLA X
1 1 5 1 1 1 1 0 0 1 0 Range Rate X
1 1 1 1 0 0 1 0 System Address Label for PSS X See Attachment 11
0 0 4 1 1 1 1 0 0 1 1 Cross Track Acceleration X
0 3 8 1 1 1 1 0 0 1 1 Cross Track Acceleration X
3 6 3 1 0 A 1 1 1 1 0 0 1 1 Corrected Thrust X
1 0 B 1 1 1 1 0 0 1 1 Corrected Thrust X
1 1 1 1 0 0 1 1 System Address Label for CSS X See Attachment 11
0 0 4 1 1 1 1 0 1 0 0 Vertical Acceleration X
0 0 5 1 1 1 1 0 1 0 0 Vertical Acceleration X
3 6 4 0 3 8 1 1 1 1 0 1 0 0 Vertical Acceleration X
1 3 A 1 1 1 1 0 1 0 0 N1 APR Rating X
1 1 1 1 0 1 0 0 System Address Label for AES X See Attachment 11
0 0 4 1 1 1 1 0 1 0 1 Inertial Vertical Velocity (EFI) X
0 0 5 1 1 1 1 0 1 0 1 Inertial Vertical Velocity (EFI) X
3 6 5 0 3 8 1 1 1 1 0 1 0 1 Inertial Vertical Velocity (EFI) X
1 3 A 1 1 1 1 0 1 0 1 N1 Max Reverse X
1 1 1 1 0 1 0 1 Engine Indication Unit - System Address Label X See Attachment 11
0 0 4 1 1 1 1 0 1 1 0 North-South Velocity X 6-2-1
0 3 8 1 1 1 1 0 1 1 0 North-South Velocity X
3 6 6
1 3 A 1 1 1 1 0 1 1 0 IGV Position X
1 1 1 1 0 1 1 0 System Address Label for Multicast X See Attachment 11
0 0 4 1 1 1 1 0 1 1 1 East-West Velocity X
0 3 8 1 1 1 1 0 1 1 1 East-West Velocity X
3 6 7
1 3 A 1 1 1 1 0 1 1 1 EGV Request X
1 1 1 1 0 1 1 1 System Address Label for Bridge X See Attachment 11
 ATTACHMENT 1-1 ARINC SPECIFICATION 429, PART 1 - Page 43
LABEL CODES

Transmission Order Bit Position Data Notes & Cross

Code No. Eqpt. ID
Parameter Ref. to Tables in
(Octal) (Hex)
Att. 6
1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 0 0 0 0 4 1 1 1 1 1 0 0 0 g X
0 0 5 1 1 1 1 1 0 0 0 g X
3 7 0 0 0 B 1 1 1 1 1 0 0 0 GNSS Height WGS-84 (HAE) X
0 2 5 1 1 1 1 1 0 0 0 Decision Height Selected (EFI) X
0 C 5 1 1 1 1 1 0 0 0 Decision Height Selected (EFI) X
3 7 1 0 0 0 1 1 1 1 1 0 0 1 General Aviation Equipment Identifier X See Attachment 9B
0 0 5 1 1 1 1 1 0 1 0 Wind Direction - Magnetic X
1 0 A 1 1 1 1 1 0 1 0 Actual Fan Speed X
3 7 2
1 0 B 1 1 1 1 1 0 1 0 Actual Fan Speed X
1 1 1 1 1 0 1 0 Cabin Terminal #3 - System Address Label X See Attachment 11
0 0 5 1 1 1 1 1 1 0 0 North-South Velocity - Magnetic X
1 0 A 1 1 1 1 1 1 0 0 Actual Core Speed X
3 7 3
1 0 B 1 1 1 1 1 1 0 0 Actual Core Speed X
1 1 1 1 1 1 0 0 Cabin Terminal #4 - System Address Label X See Attachment 11
0 0 5 1 1 1 1 1 1 0 0 East-West Velocity - Magnetic X
1 0 A 1 1 1 1 1 1 0 0 Left Thrust Reverser Position X
3 7 4
1 0 B 1 1 1 1 1 1 0 0 Left Thrust Reverser Position X
1 1 1 1 1 1 0 0 Cabin Terminal #1 - System Address Label X See Attachment 11
0 0 4 1 1 1 1 1 1 0 1 Along Heading Acceleration X
0 0 5 1 1 1 1 1 1 0 1 Along Heading Acceleration X
0 3 3 1 1 1 1 1 1 0 1 Spare DC1 X
0 3 8 1 1 1 1 1 1 0 1 Along Heading Acceleration X
3 7 5
1 0 A 1 1 1 1 1 1 0 1 Right Thrust Reverser Position X
1 0 B 1 1 1 1 1 1 0 1 Right Thrust Reverser Position X
X X X 1 1 1 1 1 1 0 1 GPS Differential Correction Word A X
1 1 1 1 1 1 0 1 Cabin Terminal #2 - System Address Label X See Attachment 11
0 0 4 1 1 1 1 1 1 1 0 Cross Heading Acceleration X
0 0 5 1 1 1 1 1 1 1 0 Cross Heading Acceleration X
3 7 6 0 3 3 1 1 1 1 1 1 1 0 Spare DC2 X
0 3 8 1 1 1 1 1 1 1 0 Cross Heading Acceleration X
X X X 1 1 1 1 1 1 1 0 GPS Differential Correction Word B X
0 3 0 1 1 1 1 1 1 1 1 Equipment Identification X X
3 7 7
X X X 1 1 1 1 1 1 1 1 Equipment Identification X X 6-17/Note 1

Notes
[1] XXX or YYY is applicable to all Equipment IDs.
[2] The label does not adhere to ARINC 429 standard signal format and contains both BCD and BNR bit encoding depending on the selected
mode.
 ARINC SPECIFICATION 429, PART 1 - Page 44

ATTACHMENT 1-2
EQUIPMENT CODES

Equip Equipment Equip Equipment

ID Type ID Type
(Hex) (Hex)

000 Not Used 03A Propulsion Discrete Interface Unit c-11

001 Flight Control Computer (701) 03B Autopilot Buffer Unit c-6
002 Flight Management Computer (702) 03C Tire Pressure Monitoring System c-8
003 Thrust Control Computer (703) 03D Airborne Vibration Monitor (737/757/767) c-9
004 Inertial Reference System (704) 03E Center of Gravity Control Computer
c-7
005 Attitude and Heading Ref. System (705) 03F Full Authority EEC-B
006 Air Data System (706) 040 Cockpit Printer (740) c-11
007 Radio Altimeter (707) 041 Satellite Data Unit
008 Airborne Weather Radar (708) 042
009 Airborne DME (709) 043
c-5 00A FAC (A310) 044
c-10 00B Global Positioning System (743) 045
00C 046 CTU
c-14
c-7 00D AIDS Data Management Unit 047 Digital Flight Data Recorder
00E 048
00F 049
010 Airborne ILS Receiver (710) 04A Landing Gear Position Interface Unit
011 Airborne VOR Receiver (711) 04B Main Electrical System Controller c-9
012 Airborne ADF System (712) 04C Emergency Electrical System Controller
013 04D Fuel Qty. Indicating System (757/767)
c-10
014 04E Fuel Qty. Indicating System (747)
015 04F
c-14
016 Airborne VHF COM receiver (716) 050 VDR (750)
017 DEFDARS-AIDS (717) 051
018 ATC Transponder (718) 052
019 Airborne HF/SSB System (719) 053 HF Data Unit
c-5 01A Electronic Supervisory Control [1] 054
01B Digital Slat/Flap Computer (A310) 055 Multi-Mode Receiver (MMR) (755)
01C Engine Parameter Digitizer (Engine) 056 GNSS Navigation Landing Unit (GNLU)(756)
c-16
01D A/P & F/D Mode Control Panel (757/767) 057 Cockpit Voice Recorder (CVR) (757)
01E Performance Data Computer (Boeing 737) 058 Communication Management Unit Mark 2 (758)
01F Fuel Quantity Totalizer 059
020 DFS System (720) 05A Fuel Quan. Indicating System (A-320/A-321)
021 05B Cargo Smoke Detection Unit (A-320)
022 05C Cabin Pressure Unit (A-320)
c-10
023 Ground Prox. Warning System (723) 05D Zone Controller (A-320)
024 ACARS (724) 05E Cargo Heat (A-320)
025 Electronic Flt. Instruments (725) 05F CIDS (A-320)
026 Flight Warning Computer (726) 060 GNSS Navigation Unit (GNU) (760)
c-16
027 Microwave Landing System (727) 061 Satellite Terminal Unit (STU) (761)
028 062
029 ADDCS (729) and EICAS 063
02A Thrust Management Computer 064
02B Perf. Nav. Computer System (Boeing 737) 065
c-6 02C Digital Fuel Gauging System (A310) 066
c-5 02D EPR Indicator (Boeing 757) 067
c-6 02E Land Rollout CU/Landing C & LU 068
02F Full Authority EEC-A 069
c-7
030 Airborne Separation Assurance System 06A AMU (A-320)
c-10
031 Chronometer (731) 06B Battery Charge Limiter (A-320)
032 Pass. Entertainment Tape Reproducer (732) 06C Flt. Cont. Data Concentrator (A-320)
c-6 033 Propulsion Multiplexer (PMUX)(733) 06D Landing Gear Prox. Control (A-320)
034 Fault Isolation & Detection System (734) 06E Brake Steering Unit (A-320)
035 TCAS (735) 06F Bleed Air (A-320)
036 Radio Management System (736) 070
037 Weight and Balance System (737) 071
c-10
038 ADIRS (738) 072
039 MCDU (739) 073

c-5 [1] “Electronic Engine Control” and “Power Management Control” are two other names for equipment identified by “1A”.
 ARINC SPECIFICATION 429, PART 1 - Page 45

ATTACHMENT 1-2
EQUIPMENT CODES

Equip Equipment Equip Equipment

ID Type ID Type
(Hex) (Hex)

074 0B0 Airborne ILS Controller (710)

075 0B1 Airborne VOR Controller (711)
076 0B2 Airborne ADF Controller (712)
077 0B3
079 0B4
07A APU Engine Control Unit (A-320) 0B5
07B Engine Interface Unit (A-320) 0B6 VHF COM Controller (716)
07C FADEC Channel A (A-320) 0B7
c-10
07D FADEC Channel B (A-320) 0B8 ATC Transponder Controller (716)
07E Centralized Fault Data Interface Unit 0B9 HF/SSB System Controller (719)
07F Fire Detection Unit (A-320) 0BA Power Supply Module (B-747-400) c-11
080 0BB Flap Control Unit (B-747-400) c-16
081 Flap Slat Electronics Unit (B767-400)
082 0BC Fuel System Interface Card (B-747-400)
083 0BD Hydraulic Quantity Monitor Unit (B-747-400)
c-11
084 0BE Hydraulic Interface Module (B-747-400)
085 0BF Window Heat Control Unit (B-747-400)
086 0C0
087 0C1
088 0C2 PVS Control Unit c-11
089 0C3 GPWS Controller (723) c-10
08A Window Heat Computer (A-320) 0C4
08B Probes Heat Computer (a-320) 0C5 EFI Controller (725)
c-10
08C Avionics Cooling Computer (A-320) 0C6
08D Fuel Flow Indicator (B-747) 0C7 MLS Controller
c-14
08E Surface Position Digitizer (B-747-400) 0C8
c-11
08F Vacuum System Controller 0C9
090 0CA Brake Temperature Monitor Unit (B-747-400)
091 0CB Autostart (B-747-400)
093 0CC Brake System Control Unit (B-747-400)
094 0CD Pack Temperature Controller (B-747-400) c-11
095 0CE EICAS/EFIC Interface Unit (B-747-400)
096 0CF Para Visual Display Computer (B-747-400)
097 0D0 Engine Instrument System (737)
c-10 098 0D1
099 0D2
09A 0D3 Thermal Monitoring Unit (General)
09B 0D4 c-14
09C 0D5 TCAS Control Panel
09D 0D6
09E 0D7
09F 0D8
0A0 0D9
0A1 FCC Controller (701) 0DA Prox. Switch Electronics Unit (B-747-400)
0A2 FMC Controller (702) 0DB APU Controller (B-747-400)
0A3 Thrust Rating Controller (703) 0DC Zone Temperature Controller (B-747-400)
c-11
0A4 IRS Controller (704) 0DD Cabin Pressure Controller (B-747-400)
0A5 0DE Windshear Computer (Sperry)
0A6 0DF Equipment Cooling Card (B-747-400)
0A7 0E0 Crew Rest Temp. Controller (747-400)
0A8 Airborne WXR Controller (708) 0E1
0A9 Airborne DME Controller (709) 0E2
0AA Generator Control Unit (A-320) 0E3
c-11 0AB Air Supply Control & Test Unit (B-747-400) 0E4
0AC Bus Control Unit (B-747-400) 0E5
c-10 0AD ADIRS Air Data Module 0E6
0AE Yaw Damper Module (B-747-400) 0E7
c-11
0AF Stabilizer Trim Module (B-747-400) 0E8
 ARINC SPECIFICATION 429, PART 1 - Page 46

ATTACHMENT 1-2
EQUIPMENT CODES

Equip Equipment Equip Equipment

ID Type ID Type
(Hex) (Hex)

0E9 123 Ground Power Control Unit (A-330/A-340)

0EA Misc. Environment Control (B-747) 124 Fuel Management Computer (A-330/A-340)
0EB Fuel Jettison Control Card (B-747) 125 Center of Gravity Fuel Control Comp.(A-330/A-340)
0EC Advance Cabin Entertainment Serv. Sys. 126 Circuit breakers Monitoring Unit (A-330/A-340) c-12
c-11
0ED Fuel System Controller (MD-11) 127 Electrical Contractor Management Unit (A-330/A-340)
0EE Hydraulic System Controller (MD-11) 128 Hydraulic Electrical Generator Control Unit (A-330/A-340)
0EF Environmental System Controller (MD-11) 129 Hydraulic System Monitoring Unit (A-330/A-340)
0F0 12A Cargo Bay Conditioning Card (B-747)
c-11
0F1 12B Predictive Windshear System Sensor
0F2 12C Angle of Attack Sensor c-14
0F3 12D Logic Drive Control Computer (B747/B767)
0F4 12E Cargo Control Logic Unit (B767)
c-16
0F5 12F Cargo Electronics Interface Unit (B767)
0F6 130 Load Management Unit (LMU) Airbus
0F7 131
0F8 132
0F9 133
0FA Misc. System controller (MD-11) 134
0FB Anti-Skid System (MD-11) 135
0FC Cabin Pressure Control Sys. (MD-11) 136 Audio Management System c-11
c-11
0FD Air Condition Control System (MD-11) 137
0FE Pneumatic Control System (MD-11) 138
0FF Manifold Failure Detection System (MD-11) 139
100 13A Full Authority Engine Control (P&W) c-14
101 13B Audio Entertainment System (AES) Controller (Boeing) c-16
102 13C Boarding Music Machine (B-777)
103 13D Passenger In Flight Info Unit (Airshow) c-14
104 13E Video Interface Unit (B-777)
105 13F Camera Interface Unit (A340/B777)
c-16
106 140 Supersonic Air Data Computer
107 141 Satellite RF Unit c-11
108 Electronic Engine Control (EEC) Channel A (B737-700) 142 ADS-B Link Display Processor Unit (LPDU)
c-16 c-16
109 Elect Eng Control (EEC) Channel B (B737-700) 143 Vertical/Horizontal Gyro
10A Full Authority Engine Control A (GE) 144
10B Full Authority Engine Control B (GE) 145
10C APU Controller 146
c-11
10D Data Loader 147
10E Fire Detection Unit (MD-11) 148
10F Auto Brake Unit (MD-11) 149
101 Multiplexer PES (A-320) 14A
111 14B
c-14 112 TACAN Adapter Unit (TAU) 14C
113 Stall Warning Card (B-747-400) 14D
114 Fuel Unit Management System (A330/A340) 14E
115 TACAN 14F
116 Eng Interface Vibration Monitoring Unit (A-330/A-340) 150 AIMS Gen. Pur. Bus #1 (B-777)
c-12
117 Engine Control Unit Channel A (A-330/A-340) 151 AIMS Gen. Pur. Bus #2 (B-777)
118 Engine Control Unit Channel B (A-330/A-340) 152 AIMS Digital Comm. Mgmt. (B-777)
119 Centralized Maintenance Computer (A-330/A-340) 153 AIMS Gen. Pur. Bus #3 (B-777)
c-14
11A Multi-Disk Drive Unit (A-330/A-340) 154 Central Maintenance Computer (B-777)
11B 155 AIMS EFIS Control Panel (B-777)
11C 156 AIMS Display Unit (B-777)
11D 157 AIMS Cursor Control Device (B-777)
11E 158 AIMS General Purpose Bus #4 c-16
11F 159
120 15A Flight Data Interface Unit (A-330/A-340)
121 15B Flight Control Unit (A-330/A-340) c-12
c-16 122 Ground Auxiliary Power Unit (A320/319/321) 15C Flight Control Primary Computer (A-330/A-340)
 ARINC SPECIFICATION 429, PART 1 - Page 47

ATTACHMENT 1-2
EQUIPMENT CODES

Equip Equipment Equip Equipment

ID Type ID Type
(Hex) (Hex)

15D Flight Control Secondary Computer (A-330/A-340) 19F Cade Environment System
c-12
15E Flight Mgmt Guidance Env Comp (A-330/A-340) 200 Versatile Integrated Avionics Unit (B717/MD-10)
15F 201 Electronic Spoiler Control Unit (B717)
160 Special Fuel Quan. Sys. (Boeing) 202 Brake Control Unit (B717)
161 203 Pneumatic Overheat Detection Unit (B717) c-16
162 204 Proximity Switch Electronics Unit (B717)
163 205 APU Electronic Control Unit (B717)
164 206 Aircraft Interface Unit (MD-10)
165 207 Fuel Quantity Gauging Unit (MD-10)
166
167 Air Traffic Service Unit (Airbus)
c-16 168 Integ Standby Instr System (A340/330,A320/319/321)
169 Data Link Control and Display Unit (A340/330)
16A Display Unit (A-330/A-340)
16B Display Management Computer (A-330/A-340) 241 High Power Amplifier c-11
c-12 16C Head-Up Display Computer (A-330/A-340)
16D ECAM Control Panel (A-330/A-340)
16E Clock (A-330/A-340)
16F Cabin Interphone System (B-777)
c-14
170 Radio Tuning Panel (B-777)
171
172 341 Satellite ACU c-11
173
174
175
176
177
178
179
17A Cabin Ventilation Controller (A-330/A-340)
c-12 17B Smoke Detection Control Unit (A-330/A-340)
17C Proximity Sensor Control Unit (A-330/A-340)
17D
17E
17F
180
181
182
183
184
185
186
187
188
189
18A Audio Control Panel (A-330/A-340)
18B Cockpit Voice recorder (A-330/A-340)
18C Passenger Entertainment Sys Main MUX (A330/A340)
c-11
18D Passenger Entertainment Sys Audio Repro.(A330/A340)
18E Pre-recorded Announcement Music Repro (A-330/A340)
18F Video Control Unit (A-330/A-340)
ARINC SPECIFICATION 429, PART 1 - Page 48
ATTACHMENT 2
DATA STANDARDS
TABLE 1 - BCD DATA

Min Max Max

Eqpt Parameter Range Sig Pos Reso- Transit Transit Trans-
Label ID Name Units (Scale) Bits Sense lution Interval Interval port Notes
(Hex) (msec) 2 (msec) 2 Delay
(msec) 3

001 0 0 2 Distance to Go N.M. ±3999.9 5 0.1 100 200

0 5 6 Distance to Go N.M. ±3999.9 5 0.1 100 200
0 6 0 Distance to Go N.M. ±3999.9 5 0.1 100 200

002 002 Time to Go Min 0-399.9 4 0.1 100 200

056 Time to Go Min 0-399.9 4 0.1 100 200
060 Time to Go Min 0-399.9 4 0.1 100 200
115 Time to Station Min 0-399.9 4 0.1 50 50

003 0 0 2 Cross Track Distance N.M. 0-399.9 4 0.1 100 200

004 0 0 1 Runway Distance to Go Feet 0-79900 3 100.0 100 200

010 0 0 2 Present Position - Latitude Deg:Min 180N-180S 6 N 0.1 250 500 See Section 2.1.2
0 0 4 Present Position - Latitude Deg:Min 180N-180S 6 N 0.1 250 500 See Section 2.1.2
0 3 8 Present Position - Latitude Deg:Min 180N-180S 6 N 0.1 250 500

011 0 0 2 Present Position - Longitude Deg:Min 180E-180W 6 E 0.1 250 500

0 0 4 Present Position - Longitude Deg:Min 180E-180W 6 E 0.1 250 500
0 3 8 Present Position - Longitude Deg:Min 180E-180W 6 E 0.1 250 500

012 002 Ground Speed Knots 0-7000 4 1.0 250 500

004 Ground Speed Knots 0-7000 4 1.0 250 500
04D Qty-LD SEL (LB) Lbs. 0-79999 5 1.0
005 Ground Speed Knots 0-7000 4 1.0 250 500
025 Ground Speed Knots 0-7000 4 1.0 125 250
038 Ground Speed Knots 0-7000 4 1.0 250 500
056 Ground Speed Knots 0-7000 4 1.0 250 500
060 Ground Speed Knots 0-7000 4 1.0 250 500

013 002 Track Angle - True Deg 0-359.9 4 0.1 250 500
004 Track Angle - True Deg 0-359.9 4 0.1 250 500
04D Qty-Flt. Deck (LB) Lbs. 0-79999 5 1.0
038 Track Angle - True Deg 0-359.9 4 0.1 250 500

014 0 0 4 Magnetic Heading Deg 0-359.9 4 0.1 250 500

0 0 5 Magnetic Heading Deg 0-359.9 4 0.1 250 500
0 3 8 Magnetic Heading Deg 0-359.9 4 0.1 250 500

015 002 Wind Speed Knots 0-799 3 1.0 250 500

004 Wind Speed Knots 0-799 3 1.0 250 500
005 Wind Speed Knots 0-799 3 1.0 250 500
038 Wind Speed Knots 0-799 3 1.0 250 500

016 0 0 4 Wind Direction - True Deg 0-359 3 1.0 250 500

0 3 8 Wind Direction - True Deg 0-359 3 1.0 250 500

017 010 Selected Runway Heading Deg 0-359.9 4 0.1 167 333
04D Total-Flt. Deck (LB) Lbs. 0-79999 5 1.0
055 Selected Runway Heading Deg 0-359.9 4 0.1
0A0 Selected Runway Heading Deg 0-359.9 4 0.1 167 333
0B0 Selected Runway Heading Deg 0-359.9 4 0.1 167 333

020 0 2 0 Selected Vertical Speed Ft/Min ±6000 4 1.0 100 200

0 4 D Tnk-LD SEL (LB) Lbs. 0-79999 5 1.0
0 A 1 Selected Vertical Speed Ft/Min ±6000 4 Up 1.0 100 200

021 002 Selected EPR EPR 0-3 4 0.001 100 200

002 Selected N1 RPM 0-3000 4 1 100 200
020 Selected EPR EPR 0-3 4 0.001 100 200
020 Selected N1 RPM 0-3000 4 1 100 200
0A1 Selected EPR EPR 0-3 3 0.001 100 200
 ARINC SPECIFICATION 429, PART 1 - Page 49
ATTACHMENT 2
DATA STANDARDS
TABLE 1 - BCD DATA

Min Max Max

Eqpt Parameter Range Sig Pos Reso- Transit Transit Trans-
Label ID Name Units (Scale) Bits Sense lution Interval Interval port Notes
(Hex) (msec) 2 (msec) 2 Delay
(msec) 3

0 A 1 Selected N1 RPM 0-3000 4 1 100 200

022 0 2 0 Selected Mach Mach 0-4 4 0.001 100 200

0 4 D Qty-LD SEL (KG) Kg 0-79999 5 1.0
0 A 1 Selected Mach Mach 0-4 4 0.001 100 200

023 0 2 0 Selected Heading Deg 0-359 3 1.0 100 200

0 4 D Qty-Flt Deck (KG) Kg 0-79999 5 1.0
0 A 1 Selected Heading Deg 0-359 3 1.0 100 200

024 011 Selected Course #1 Deg 0-359 3 1.0 167 333

020 Selected Course #1 Deg 0-359 3 1.0 167 333
0A1 Selected Course #1 Deg 0-359 3 1.0 167 333
0B1 Selected Course #1 Deg 0-359 3 1.0 167 333

025 0 2 0 Selected Altitude Feet 0-50000 5 1.0 100 200

0 A 1 Selected Altitude Feet 0-50000 5 1.0 100 200

026 0 0 3 Selected Airspeed Knots 30-450 3 1.0 100 200

0 2 0 Selected Airspeed Knots 30-450 3 1.0 100 200
0 A 1 Selected Airspeed Knots 30-450 3 1.0 100 200

027 002 TACAN Selected Course Deg 0-359 3 1.0 167 333
011 Selected Course #2 Deg 0-359 3 1.0 167 333
020 Selected Course #2 Deg 0-359 3 1.0 167 333
04D Total-Flt Deck (KG) Kg 0-79999 5 1.0
056 TACAN Selected Course Deg 0-359 3 1.0 167 333
060 TACAN Selected Course (BCD) Deg 0-359 3 1.0 167 333
0A1 Selected Course #2 Deg 0-359 3 1.0 167 333
0B1 Selected Course #2 Deg 0-359 3 1.0 167 333

030 020 VHF COM Frequency See Chapter 3 100 200

024 VHF COM Frequency See Chapter 3 100 200
04D TNK-LD SEL (KG) Kg 0-79999 5 1.0
0B6 VHF COM Frequency See Chapter 3 100 200

031 0 2 0 Beacon Transponder Code See Chapter 3 100 200

0 B 8 Beacon Transponder Code See Chapter 3 100 200

032 0 1 2 ADF Frequency See Chapter 3 100 200

0 2 0 ADF Frequency See Chapter 3 100 200
0 B 2 ADF Frequency See Chapter 3 100 200

033 002 ILS Frequency See Chapter 3 167 333

010 ILS Frequency See Chapter 3 167 333
020 ILS Frequency See Chapter 3 167 333
056 ILS Frequency See Chapter 3 167 333
060 ILS Frequency See Chapter 3 167 333
0B0 ILS Frequency See Chapter 3 167 333

034 002 VOR/ILS Frequency See Chapter 3 167 333

006 Baro Correction (mb) #3 mb 745-1050 5 0.1 62.5 125
011 VOR/ILS Frequency See Chapter 3 167 333
020 VOR/ILS Frequency See Chapter 3 167 333
056 VOR/ILS Frequency See Chapter 3 167 333
060 VOR/ILS Frequency #1 See Chapter 3 167 333
0B0 VOR/ILS Frequency See Chapter 3 167 333

035 002 DME Frequency See Chapter 3 100 200

006 Baro Correction (ins of Hg) #3 ins Hg 22-31 5 0.001 62.5 125
009 DME Frequency See Chapter 3 100 200
020 DME Frequency See Chapter 3 100 200
ARINC SPECIFICATION 429, PART 1 - Page 50
ATTACHMENT 2
DATA STANDARDS
TABLE 1 - BCD DATA

Min Max Max

Eqpt Parameter Range Sig Pos Reso- Transit Transit Trans-
Label ID Name Units (Scale) Bits Sense lution Interval Interval port Notes
(Hex) (msec) 2 (msec) 2 Delay
(msec) 3

055 Paired DME Frequency MHz 108-135.9 4 0.05

056 DME Frequency See Chapter 3 100 200
060 DME Frequency See Chapter 3 100 200
0A9 DME Frequency See Chapter 3 100 200

036 002 MLS Frequency See Chapter 3 100 200

020 MLS Frequency See Chapter 3 100 200
055 MLS Channel Selection 500-600 3 1
056 MLS Frequency Channel See Chapter 3 100 200
060 MLS Frequency Channel See Chapter 3 100 200
0C7 MLS Frequency See Chapter 3 100 200

037 0 2 0 HF COM Frequency See Chapter 3 100 200

0 B 9 HF COM Frequency See Chapter 3 100 200

041 002 Set Latitude Deg/Min 180N/180S 6 N 0.1 250 500

004 Set Latitude Deg/Min 180N/180S 6 N 0.1 250 500
020 Set Latitude Deg/Min 180N/180S 6 N 0.1 250 500
056 Set Latitude Deg/Min 180N/180S 6 N 0.1 250 500
060 Set Latitude Deg/Min 180N/180S 6 N 0.1 250 500
0A4 Set Latitude Deg/Min 180N/180S 6 N 0.1 250 500

042 002 Set Longitude Deg/Min 180E/180W 6 E 0.1 250 500

004 Set Longitude Deg/Min 180E/180W 6 E 0.1 250 500
020 Set Longitude Deg/Min 180E/180W 6 E 0.1 250 500
056 Set Longitude Deg/Min 180E/180W 6 E 0.1 250 500
060 Set Longitude Deg/Min 180E/180W 6 E 0.1 250 500
0A4 Set Longitude Deg/Min 180E/180W 6 E 0.1 250 500

043 002 Set Magnetic Heading Deg 0-359 3 1.0 250 500
004 Set Magnetic Heading Deg 0-359 3 1.0 250 500
020 Set Magnetic Heading Deg 0-359 3 1.0 250 500
056 Set Magnetic Heading Deg 0-359 3 1.0 250 500
060 Set Magnetic Heading Deg 0-359 3 1.0 250 500
0A4 Set Magnetic Heading Deg 0-359 3 1.0 250 500

044 0 0 4 True Heading Deg 0-359.9 4 0.1 250 500

0 3 8 True Heading Deg 0-359.9 4 0.1 250 500

045 0 0 3 Minimum Airspeed Knots 0-259.9 4 0.1 62.5 125

046 0 3 3 Engine Serial No. (LSDs) 500 1000 See Att. 6

1 0 A Engine Serial No. (LSDs) 500 1000 See Att. 6
1 0 B Engine Serial No. (LSDs) 500 1000 See Att. 6

047 020 VHF Com Frequency See Chap. 3 100 200

024 VHF Com Frequency See Chap. 3 100 200
033 Engine Serial No. (MSDs) 500 1000 See Att. 6
10A Engine Serial No. (MSDs) 500 1000 See Att. 6
10B Engine Serial No. (MSDs) 500 1000 See Att. 6
0B6 VHF Com Frequency See Chap. 3 100 200

052 0 3 7 Long. Zero Fuel CG % MAC 0-100.00 5 0.01 100 200

053 0 0 5 Track Angle-Magnetic Deg 0-359 3 1.0 250 500

056 002 Estimated Time of Arrival Hr:Min 0-23.59.9 5 0.1 250 500
005 Wind Direction - Magnetic Deg 0-359 3 1.0 250 500
037 Gross Weight (Kilograms) 100 kg 0-19999 5 1.0 100 200
056 ETA (Active Waypoint) Hr:Min 0-23.59.9 5 0.1 250 500
060 ETA (Active Waypoint) Hr:Min 0-23.59.9 5 0.1 250 500
 ARINC SPECIFICATION 429, PART 1 - Page 51
ATTACHMENT 2
DATA STANDARDS
TABLE 1 - BCD DATA

Min Max Max

Eqpt Parameter Range Sig Pos Reso- Transit Transit Trans-
Label ID Name Units (Scale) Bits Sense lution Interval Interval port Notes
(Hex) (msec) 2 (msec) 2 Delay
(msec) 3

060 0 3 7 Tire Loading (Left Body Main) % 0-299.9 4 0.1 100 200

061 0 3 7 Tire Loading (Right Body Main) % 0-299.9 4 0.1 100 200

062 0 3 7 Tire Loading (Left Wing Main) % 0-299.9 4 0.1 100 200

063 0 3 7 Tire Loading (Right Wing Main) % 0-299.9 4 0.1 100 200

064 0 3 7 Tire Loading (Nose) % 0-299.9 4 0.1 100 200

065 0 0 3 Gross Weight 100 lb. 0-12000 5 1.0 100 200

0 3 7 Gross Weight 100 lb. 0-19999 5 1.0 100 200

066 0 0 2 Longitudinal Center of Gravity % MAC 0-100.00 5 0.01 500 1000

0 3 7 Longitudinal Center of Gravity % MAC 0-100.00 5 0.01 100 200

067 0 3 7 Lateral Center of Gravity % MAC 0-100.00 5 0.01 100 200

125 0 0 2 Universal Coordinate Time Hr-Min 0-23.59.9 4 0.1 100 200

0 0 B UTC Hr:Min 23:59.9 5 0.1 200 1200
Min
0 3 1 Universal Coordinate Time Hr:Min 0-23.59.9 5 0.1 100 200
0 5 6 Universal Coordinate Time Hr-Min 0-23.59.9 4 0.1 100 200
0 6 0 Universal Coordinated Time (UTC) Hr-Min 0-23.59.9 4 0.1 100 200

135 0 5 A ACT 1 Fuel Quan. Display Kg/Lb 0-9999 4 100 100 200

136 0 5 A ACT 2 Fuel Quan. Display Kg/Lb 0-9999 4 100 100 200

137 0 5 A Center+Act1+Act2 FQ Display Kg/Lb 0-9999 4 100 100 200

140 0 5 A Actual Fuel Quan. Display Kg/Lb 0-9999 4 100 100 200

141 0 5 A Preselect Fuel Quan. Display Kg/Lb 0-9999 4 100 100 200

142 0 5 A Left Wing Fuel Quan. Display Kg/Lb 0-9999 4 100 100 200

143 0 5 A Center Wing Fuel Quan. Display Kg/Lb 0-9999 4 100 100 200

144 0 5 A Right Wing Fuel Quan. Display Kg/Lb 0-9999 4 100 100 200

155 0 2 7 MLS Selected GP Angle Deg 0-359.9 4 0.1 100 200

157 1 1 4 Trim Tank Probe Capacitance pf 0-400 14 0.1

163 0 3 7 Zero Fuel Weight (lb) Lbs. 0-19999 5 1.0 100 200

165 0 0 7 Radio Height Feet ±7999.9 5 0.1 25 200

170 0 2 5 Decision Height Selected (EFI) Feet ±7000 4 1.0 100 200
0 C 5 Decision Height Selected (EFI) Feet ±7000 4 1.0 100 200

200 002 Drift Angle Deg ±180 4 0.1 100 200

004 Drift Angle Deg ±180 4 0.1 100 200
056 Drift Angle Deg ±180 4 0.1 100 200
060 Drift Angle Deg ±180 4 0.1 100 200

201 0 0 9 DME Distance N.M. -1-399.99 5 0.01 83.3 167

1 1 2 TACAN Distance N.M. 0-399.99 5 0.01 190 210
1 1 5 DME Distance N.M. 0-399.99 5 0.01 50 50
ARINC SPECIFICATION 429, PART 1 - Page 52
ATTACHMENT 2
DATA STANDARDS
TABLE 1 - BCD DATA

Min Max Max

Eqpt Parameter Range Sig Pos Reso- Transit Transit Trans-
Label ID Name Units (Scale) Bits Sens lution Interval Interval port Notes
(Hex) e (msec) 2 (msec) 2 Delay
(msec) 3
205 0 0 2 HF COM Freq (New Format) See Figure 3-1
0 B 9 HF COM Freq (New Format) See Figure 3-1

230 0 0 6 True Airspeed Knots 100-599 3 1.0 250 500

0 3 8 True Airspeed Knots 100-599 3 1.0 250 500

231 0 0 6 Total Air Temperature Deg C -060-+099 3 1.0 250 500

0 3 8 Total Air Temperature Deg C -060-+099 3 1.0 250 500
1 1 4 Inner 2 Tank Probe Capacitance pf 0-400 14 0.1

232 004 Altitude Rate Ft/Min ±20000 4 Up 10.0 31.3 62.5

005 Altitude Rate Ft/Min ±20000 4 Up 10.0 31.3 62.5
006 Altitude Rate Ft/Min ±20000 4 Up 10.0 31.3 62.5
114 Inner 4 Tank Probe Capacitance pf 0-400 14 0.1

233 0 0 6 Static Air Temperature Deg C -099-+060 3 1.0 250 500

0 3 8 Static Air Temperature Deg C -099-+060 3 1.0 250 500
1 1 4 Right Outer Probe Capacitance pf 0-400 14 0.1

234 0 0 6 Baro Correction (mb) #1 mb 745-1050 5 0.1 62.5 125

0 3 8 Baro Correction (mb) #1 mb 745-1050 5 0.1 62.5 125

235 0 0 6 Baro Correction (ins of Hg) #1 ins Hg 22-31 5 0.001 62.5 125
0 3 8 Baro Correction (ins of Hg) #1 ins Hg 22-31 5 0.001 62.5 125

236 0 0 6 Baro Correction (mb) #2 mb 745-1050 5 0.1 62.5 125

0 3 8 Baro Correction (mb) #2 mb 745-1050 5 0.1 62.5 125

237 0 0 6 Baro Correction (ins of Hg) #2 ins Hg 22-31 5 0.001 62.5 125
0 3 8 Baro Correction (ins of Hg) #2 ins Hg 22-31 5 0.001 62.5 125

243 0 3 7 Zero Fuel Weight (kg) Kg 0-19999 5 1.0 100 200

260 002 Date/Flight Leg N/A 500 1000

00B Date dd:mo:yr dd:mm:yr 15 4
031 Date (No Flight Leg) N/A 100 200
056 Date/Flight Leg N/A 500 1000
060 Date/Flight Leg N/A 500 1000
0A2 Date/Flight Leg N/A 500 1000

261 002 Flight Number N/A 0-9999 4 1.0 500 1000

0A2 Flight Number N/A 0-9999 4 1.0 500 1000
056 Flight Number N/A 0-9999 4 1.0 500 1000
060 Flight Number N/A 0-9999 4 1.0 500 1000

272 0 5 A Fuel Density Kg/cu.m. 0-9999 16 0.0001 100 200

273 0 5 A Sensor Values Left Wing Tank pF 0-100 13 100 200

274 0 5 A Sensor Values Center Wing Tank pF 0-100 13 0.1 100 200

275 0 5 A Sensor Values Right Wing Tank pF 0-100 13 0.1 100 200

345 0 0 2 NDB Effectivity 1000 See Attachment 6

350 1 1 4 Fuel Density kg/l 0-.999 4 0.01

351 1 1 4 Inner Tank 1 Probe Capacitance pf 0-400 14 0.1

352 1 1 4 Center, ACT &RCT Probe Capac. pf 0-400 14 0.1

353 1 1 4 Inner Tank 3 Probe Capacitance pf 0-400 14 0.1

 ARINC SPECIFICATION 429, PART 1 - Page 53
ATTACHMENT 2
DATA STANDARDS
TABLE 1 - BCD DATA

Min Max Max

Eqpt Parameter Range Sig Pos Reso- Transit Transit Trans-
Label ID Name Units (Scale) Bits Sens lution Interval Interval port Notes
(Hex) e (msec) 2 (msec) 2 Delay
(msec) 3

377 0 3 0 Equipment Identification 1000 See Attachment 6

X X X Equipment Identification 1000 See Attachment 6
 ARINC SPECIFICATION 429, PART 1 - Page 54
ATTACHMENT 2
DATA STANDARDS
TABLE 2 - BNR DATA

Min Max Max

Eqpt Transit Transit Trans-
Label ID Parameter Units Range Sig Pos Resolution Interval Interval port Notes
(Hex) Name (Scale) Bits Sense (msec) (msec) Delay
2 2 (msec)
3

Bit 11-Chan. A/
005 0 D 0 Engine Discrete
Bit 12-Chan. B

025 0 4 D Load SEL Control NA 204700 11 100

034 0 2 5 VOR/ILS Frequency 125 250

035 0 2 5 DME Frequency 125 250

052 0 0 4 Body Pitch Acceleration Deg/Sec2 ± 64 15 0.002 50 Hz 117 Hz

0 3 8 Body Pitch Acceleration Deg/Sec2 ± 64 15 0.002 50 Hz 117 Hz

053 0 0 4 Body Roll Acceleration Deg/Sec2 ± 64 15 0.002 50 Hz 117 Hz

0 3 8 Body Roll Acceleration Deg/Sec2 ± 64 15 0.002 50 Hz 117 Hz

054 0 0 4 Body Yaw Acceleration Deg/Sec2 ± 64 15 0.002 50 Hz 117 Hz

0 3 7 Zero Fuel Weight (Kg) Kg 655360 15 20 100 200
0 3 8 Body Yaw Acceleration Deg/Sec2 ± 64 15 0.002 50 Hz 117 Hz

060 0 2 5 S/G Software Part Number See Attachment 6

0 3 C Tire Pressure (Left Outer) PSIA 1024 10 1.0 50 250 See Attachment 6

061 002 ACMS Information See Attachment 6

00B Pseudo Range Meters ± 268435456 20 256 200 1200
025 S/G Hardware Part Number See Attachment 6
03C Tire Pressure (Left Inner) PSIA 1024 10 1.0 50 250 See Attachment 6
056 ACMS Information See Attachment 6
060 ACMS Information See Attachment 6

062 002 ACMS Information See Attachment 6

00B Pseudo Rang Fine Meters 256 11 0.125 200 1200 See Attachment 6
03C Tire Pressure (Right Inner) PSIA 1024 10 1.0 50 250 See Attachment 6
056 ACMS Information See Attachment 6
060 ACMS Information See Attachment 6

063 002 ACMS Information See Attachment 6

00B Range Rate M/S ± 4096 20 0.0039 200 1200
03C Tire Pressure (Right Outer) PSIA 1024 10 1.0 50 250 See Attachment 6
056 ACMS Information See Attachment 6
060 ACMS Information See Attachment 6

064 0 0 B Delta Range Meters ± 4096 20 0.0039 200 1200

0 3 C Tire Pressure (Nose) PSIA 1024 10 1.0 50 250 See Attachment 6

065 0 0 B SV Position X Meters ±67108864 20 64 200 1200

066 0 0 B SV Position X Fine Meters 64 14 0.0039 200 1200

070 002 Reference Airspeed (Vref) Knots 512 11 0.25 500 1000 1000
00B SV Position X Meters ±67108864 20 64 200 1200
029 AC Frequency (Engine) Hz 512 11 .25 100 200
037 Hard Landing Magnitude #1 Lbs. 12 - 100 200
056 Reference Airspeed (Vref) Knots 512 11 0.25 500 1000 1000
060 Reference Airspeed (Vref) Knots 512 11 0.25 500 1000 1000
Brakes - Metered Hyd. Pres. L
0CC PSIG 4096 12 1 50 100 #1 & 2 coded in SDI
(Normal)

071 002 Take-Off Climb Airspeed (V2) Knots 512 11 0.25 500 1000 50
00B SV Position Y Fine Meters 64 14 0.0039 200 1200
029 AC Frequency (Engine) Hz 512 11 0.25 100 200
033 VBV Deg 64 12 0.016 150 250
037 Hard Landing Magnitude #2 Lbs. 12 - 100 200
0CC Brakes-Metered Hyd.Pres.L (alt.) PSIG 4096 12 1 50 100 #1 & 2 coded in SDI
 ARINC SPECIFICATION 429, PART 1 - Page 55
ATTACHMENT 2
DATA STANDARDS
TABLE 2 - BNR DATA

Min Max Max

Eqpt Transit Transit Trans-
Label ID Parameter Units Range Sig Pos Resolution Interval Interval port Notes
(Hex) Name (Scale) Bits Sense (msec) (msec) Delay
2 2 (msec)
3

072 002 Rotation Speed (VR) Knots 512 11 0.25 500 1000 1000 Revised by Supp 11
00B SV Position Z Meters ±67108864 20 64 200 1200
01C Stator Vane Angle Deg/180 ±180 11 0.1 100 200
029 AC Voltage (Engine) Volts 256 10 0.25 100 200
02F Stator Vane Angle Deg/180 ±180 11 0.1 100 200
033 Stator Vane Angle Deg 64 12 0.016 150 250 See Note [4]
0CC Brakes-Metered Hyd.Pres.R (normal) PSIG 4096 12 1 50 100 #1 &2 coded in SDI

073 002 V1 (critical engine failure speed) Knots 512 11 0.25 100 200
00B SV Position Z Fine Meters 64 14 0.0039 200 1200
01C Oil Quantity cc 32768 8 128 100 200
029 Oil Quantity US Pint 128 9 0.25 100 200
0A2 V2 (critical engine failure speed) Knots 512 11 0.25 100 200
0CC Brakes-Metered Hyd.Pres.R (alt.) PSIG 4096 12 1 50 100 #1 & 2 coded in SDI
0D0 Engine Oil Quantity US Pint 128 9 0.25 SDI 1=L/SDI 2=R

074 002 Zero Fuel Weight Lbs. 1310720 15 40 500 1000 1000
00B UTC Measure Time Seconds 10.0 20 9.536743µs 200 1200
02C Zero Fuel Weight Lbs. 1310720 15 40 100 400
033 LP Compressor Bleed Pos. (3.0) Inches 4 10 0.004 100 200 See Note [5]
037 Zero Fuel Weight (lb) Lbs. 1310720 15 40 100 200
056 Zero Fuel Weight Lbs. 1310720 15 40 500 1000 1000
060 Zero Fuel Weight Lbs. 1310720 15 40 500 1000 1000
114 Zero Fuel Weight Lbs. 1310720 15 40 100 400

075 002 Gross Weight Lbs. 1310720 15 40 100 200

003 Gross Weight Lbs. 1310720 15 40 100 200
00B Geodetic Altitude Feet 131072 17 1.0 500 1000
029 AC Voltage (Alt. Sources) Volts 256 10 0.25 100 200
02C Gross Weight Lbs. 1310720 15 40 100 200
037 Gross Weight Lbs. 1310720 15 40 100 200
03E Gross Weight Lbs. 1310720 15 40 100 200
114 Aircraft Gross Weight Lbs. 1310720 15 40 100 400

076 00B GPS Height Above Ref.Ellipsoid Feet 131072 17 1.0 25 50

00B GNSS Altitude (Msl) Feet ±131072 20 0.125 200 1200
029 AC Voltage (Bus Bar) Volts 256 10 0.25 100 200
037 Longitudinal Center of Gravity % MAC 163.84 14 0.01 100 200
03E Longitudinal Center of Gravity % 164 14 0.01 100 200
Aircraft Longitudinal Center of
114 Percent 163.84% 14 0.01% 100 200
Gravity

077 0-- Lateral Center of Gravity MLb-in 128 17 0.001 100 200
002 Target Airspeed Knots 512 11 0.25 100 200
00B GPS Hor/Vert Deviation % F.S. 128 8 0.8 25 50 Revised by Supp 11
029 AC Load (Engine) % 256 8 1.0 100 200
037 Lateral Center of Gravity % MAC 131.072 17 0.01 100 200
056 Target Airspeed Knots 512 11 0.25 100 200
060 Target Airspeed Knots 512 11 0.25 100 200
114 Zero Fuel Center of Gravity Percent 163.84% 14 0.01% 100 200

100 001 Selected Course #1 Deg/180 ±180 12 0.05 167 333

002 Selected Course #1 Deg/180 ±180 12 0.05 167 333
011 Selected Course #1 Deg/180 ±180 12 0.05 167 333
020 Sleected Course #1 Deg/180 ±180 12 0.05 167 333
029 AC Load (Alt. Source) % 128 8 1.0 100 200
056 Selected Course #1 Deg/180 ±180 12 0.05 167 333
060 Selected Course #1 Deg/180 ±180 12 0.05 167 333
037 Gross Weight (Kilogram) Kilograms 655360 15 20 100 200
0A1 Selected Course #1 Deg/180 ±180 12 0.05 167 333
0B1 Selected Course #1 Deg/180 ±180 12 0.05 167 333
0BB Outboard Flaps - PDU Deg/180 ±180 12 0.05 20 100
 ARINC SPECIFICATION 429, PART 1 - Page 56
ATTACHMENT 2
DATA STANDARDS
TABLE 2 - BNR DATA

Min Max Max

Eqpt Transit Transit Trans-
Label ID Parameter Units Range Sig Pos Resolution Interval Interval port Notes
(Hex) Name (Scale) Bits Sense (msec) (msec) Delay
2 2 (msec)
3
101 002 Selected Heading Deg/180 ±180 12 0.05 31.3 62.5
00B HDOP N/A 1024 15 0.031 200 1200
020 Selected Heading Deg/180 ±180 12 0.05 31.3 62.5
025 Selected Heading Deg/180 ±180 12 0.05 125 250
029 DC Current (TRU) Amperes 256 8 1.0 100 200
0A1 Selected Heading Deg/180 ±180 12 0.05 31.3 62.5
0BB Inboard Flaps - PDU Deg/180 ±180 12 0.05 20 100
114 C/G Target % 164 8 0.01 100 200

102 002 Selected Altitude Feet 65536 16 1.0 100 200

00B VDOP N/A 1024 15 0.031 200 1200
020 Selected Altitude Feet 65536 16 1.0 100 200
029 DC Current (Battery) Amperes 256 8 1.0 100 200
056 Selected Altitude Feet 65536 16 1.0 100 200
060 Selected Altitude Feet 65536 16 1.0 100 200
0A1 Selected Altitude Feet 65536 16 1.0 100 200

103 001 Selected Airspeed Knots 512 11 0.25 100 200

002 Selected Airspeed Knots 512 11 0.25 100 200
003 Selected Airspeed Knots 512 11 0.25 100 200
00B GNSS Track Angle Deg ±108 15 0.0055 200 1200
01B Left/PDU Flap Deg/180 ±180 18 0.000687 100 200
020 Selected Airspeed Knots 512 11 0.25 100 200
029 DC Voltage (TRU) Volts 128 9 0.25 100 200
056 Selected Airspeed Knots 512 11 0.25 100 200
060 Selected Airspeed Knots 512 11 0.25 100 200
0A1 Selected Airspeed Knots 512 11 0.25 100 200
0BB Left Outboard Flap Position Deg/180 ±180 12 0.05 20 100

104 001 Selected Vertical Speed Ft/Min 16384 10 UP 16 100 200

002 Selected Vertical Speed Ft/Min 16384 10 UP 16 100 200
01B Right/PDU Flap Deg/180 ±180 18 0.000687 100 200
020 Selected Vertical Speed Ft/Min 16384 10 UP 16 100 200
029 DC Voltage (Battery) Volts 128 9 0.25 100 200
02B Selected Vertical Speed Ft/Min 16384 14 UP 1 100 200
056 Selected Vertical Speed Ft/Min 16384 10 UP 16 100 200
060 Selected Vertical Speed Ft/Min 16384 10 UP 16 100 200
0A1 Selected Vertical Speed Ft/Min 16384 10 UP 16 100 200
0BB Right Outboard Flap Position Deg/180 ±180 12 0.05 20 100

105 002 Selected Runway Heading Deg/180 ±180 11 0.1 167 333
010 Selected Runway Heading Deg/180 ±180 11 0.1 167 333
01B Left/PDU Slat Deg/180 ±180 18 0.000687 100 200
020 Selected Runway Heading Deg/180 ±180 11 0.1 167 333
029 Oil Temp. Input (IDG/CSD) Deg C 2048 12 0.5 100 200
055 Selected Runway Heading Deg ±180 11 0.1
056 Selected Runway Heading Deg/180 ±180 11 0.1 167 333
060 Selected Runway Heading Deg/180 ±180 11 0.1 167 333
0A1 Selected Runway Heading Deg/180 ±180 11 0.1 167 333
0B0 Selected Runway Heading Deg/180 ±180 11 0.1 167 333
0BB Left Inboard Flap Position Deg/180 ±180 12 0.05 20 100

106 002 Selected Mach Mach 4096 12 1 31.3 200

01B Right/PDU Slat Deg/180 ±180 18 0.000687 100 200
020 Selected Mach Mach 4096 12 0.5 100 200
029 Oil Temp. Input (IDG/CSD) Deg C 2048 12 0.5 100 200
056 Selected Mach Mach 4096 12 1 31.3 200
060 Selected Mach Mach 4096 12 1 31.3 200
0A1 Selected Mach Mach 4096 12 1 31.3 62.5
0BB Right Inboard Flap Position Deg/180 ±180 12 0.05 20 100

107 0 0 2 Selected Cruise Altitude Feet 65536 16 UP 1 100 200

0 1 B Flap/Slat Lever Deg/180 ±180 18 0.000687 100 200
0 B B Flap Lever Position-median value Deg/180 ±180 18 0.000687 100 200
 ARINC SPECIFICATION 429, PART 1 - Page 57
ATTACHMENT 2
DATA STANDARDS
TABLE 2 - BNR DATA

Min Max Max

Eqpt Transit Transit Trans-
Label ID Parameter Units Range Sig Pos Resolution Interval Interval port Notes
(Hex) Name (Scale) Bits Sense (msec) (msec) Delay
2 2 (msec)
3
0 3 7 Long. Zero Fuel Ctr of Gravity % MAC 163.84 14 0.01 100 200
0 5 6 Selected Cruise Altitude Feet 65536 16 UP 1 100 200
0 6 0 Selected Cruise Altitude Feet 65536 16 UP 1 100 200

110 001 Selected Course #2 Deg/180 ±180 12 0.05 167 333

002 Selected Course #2 Deg/180 ±180 12 0.05 167 333
00B GNSS Latitude Deg ±180 20 0.000172 200 1200
010 Selected Course #2 Deg/180 ±180 12 0.05 167 333
011 Selected Course #2 Deg/180 ±180 12 0.05 167 333
020 Selected Course #2 Deg/180 ±180 12 0.05 167 333
0A1 Selected Course #2 Deg/180 ±180 12 0.05 167 333
0B1 Selected Course #2 Deg/180 ±180 12 0.05 167 333
0BB Flap Lever Position - Center Deg/180 180 18 0.000687 80 160

111 0 0 B GNSS Longitude Deg ±180 20 0.000172 200 1200

112 002 Runway Length Feet 20480 11 10 250 500

00B GNSS Ground Speed Knots 4096 15 0.125 200 1200
0A1 Selected EPR 4 12 0.001 100 200
0A1 Selected N1 RPM 4096 12 1 100 200
0BB Flap Lever Position - Left Deg/180 ±180 18 0.000687 80 160

114 002 Desired Track Deg/180 ±180 12 0.05 100 200

029 Brake Temp. (Left Inner L/G) Deg C 2048 11 1 100 200
02F Ambient Pressure PSIA 32 14 0.002 100 200
03F Pamb Sensor PSIA 32 14 0.002 100 200
056 Desired Track Deg/180 ±180 12 0.05 100 200
060 Desired Track Deg/180 ±180 12 0.05 100 200
0BB Flap Lever Position - Right Deg/180 ±180 18 0.000687 80 160
0CC Wheel Torque Output Lb./Ft. 16384 12 4 50 100 No. 5 to 8 in SDI
10A Selected Ambient Static Pressure PSIA 1.5-20.0 11 0.016 100 500
10B Selected Ambient Static Pressure PSIA 1.5-20.0 11 0.016 100 500
13A Ambient Pressure PSIA 32 14 0.002 100 200

115 002 Waypoint Bearing Deg/180 ±180 12 0.05 31.3 62.5

029 Brake Temp. (Left Outer L/G) Deg C 2048 11 1 100 200
02F Fuel Temperature Deg C 512 11 0.25 100 200
03F Fuel Temperature Deg C 512 11 0.25 100 200
056 Waypoint Bearing Deg/180 ±180 12 0.05 31.3 62.5
060 Waypoint Bearing Deg/180 ±180 12 0.05 31.3 62.5
0BC Fuel Temperature Deg C 256 8 1 500 1000
0CC Wheel Torque Output Lb./Ft. 16384 12 4 50 100 No. 1 to 4 in SDI

116 002 Cross Track Distance N.M. 128 15 0.004 31.3 62.5
00B Horizontal GLS Deviation Rectilinear Feet 24000 18 .00915 100
029 Brake Temp. (Right Inner L/G) Deg C 2048 11 1 100 200
055 Horizontal GLS Deviation Rectilinear Feet 24000 18 .00915 100
056 Cross Track Deviation N.M. 128 15 0.004 31.3 62.5
060 Cross Track Deviation N.M. 128 15 0.004 31.3 62.5
0CC Wheel Torque Output Lb./Ft. 16384 12 4 50 100 No. 9 to 12 in SDI

117 002 Vertical Deviation Feet 2048 11 1.0 31.3 62.5

00B Vertical GLS Deviation Rectilinear Feet 1024 14 .0625 100
029 Brake Temp. (Right Outer L/G) Deg C 2048 11 1 100 200
055 Vertical GLS Deviation Rectilinear Feet 1024 14 .0625 100
056 Vertical Deviation Feet 2048 11 1.0 31.3 62.5
060 Vertical Deviation Feet 2048 11 1.0 31.3 62.5
0CC Wheel Torque Output Lb./Ft. 16384 12 4 50 100 No. 13 to 16 in SDI

120 0 0 2 Range to Altitude N.M. 512 15 0.016 25 50

0 0 B GNSS Latitude Fine Deg 0.000172 11 8.38-E-8 o 200 1200
0 5 6 Range to Altitude N.M. 512 15 0.016 25 50
 ARINC SPECIFICATION 429, PART 1 - Page 58
ATTACHMENT 2
DATA STANDARDS
TABLE 2 - BNR DATA

Min Max Max

Eqpt Transit Transit Trans-
Label ID Parameter Units Range Sig Pos Resolution Interval Interval port Notes
(Hex) Name (Scale) Bits Sense (msec) (msec) Delay
2 2 (msec)
3
0 6 0 Range to Altitude N.M. 512 15 0.016 25 50

121 002 Horizontal Command Signal Deg/180 ±180 14 0.01 50 100

00B GNSS Longitude Fine Degrees 0.000172 11 8.38-E-8 o 200 1200
025 Pitch Limit Deg/180 ±180 14 0.01 125 250
056 Horizontal Command Signal Deg/180 ±180 14 0.01 50 100
060 Horizontal Command Signal Deg/180 ±180 14 0.01 50 100

122 0 0 2 Vertical Command Signal Deg/180 ±180 12 0.05 500 100

0 5 6 Vertical Command Signal Deg/180 ±180 12 0.05 500 100
0 6 0 Vertical Command Signal Deg/180 ±180 12 0.05 500 100

123 0 0 2 Throttle Command Deg/Sec 256 18 0.001 50 100

above
126 0 0 2 Vertical Deviation (wide) Feet 32768 15 1.0 31.3 62.5
sel alt
above
0 5 6 Vertical Deviation Feet 32768 15 1.0 31.3 62.5
sel alt
above
0 6 0 Vertical Deviation Feet 32768 15 1.0 31.3 62.5
sel alt

127 002 Selected Landing Altitude Feet 65536 16 UP 1 100 200

01B Slat Angle Deg/180 ±180 12 0.05 100 200
033 P14 PSIA 32 14 0.002 100 200
10A Fan Discharge Static Pressure PSIA 1.5 - 30.0 11 0.016 100 500
10B Fan Discharge Static Pressure PSIA 1.5 - 30.0 11 0.016 100 500

130 00B Aut Horiz Integ Limit N.M. 16 17 1.2E-4 200 1200
01A Fan Inlet Total Temperature Deg C 128 11 0.06 100 200
01C Fan Inlet Total Temperature Deg C 128 11 0.06 100 200
02F Fan Inlet Total Temperature Deg C 128 11 0.06 100 200
See Att. 6 and
0 3 5 Intruder Range 500
ARINC 735
03F Fan Inlet Total Temperature Deg C 128 11 0.06 100 200
10A Selected Total Air Temperature Deg C -80 - +90 10 0.125 100 500
10B Selected Total Air Temperature Deg C -80 - +90 10 0.125 100 500
13A Inlet Temperature Deg C 128 11 0.0625 100 200

131 01A Fan Inlet Total Pressure PSIA 32 13 0.004 100 200
01C Fan Inlet Total Pressure PSIA 32 13 0.004 100 200
02D Fan Inlet Total Pressure PSIA 32 13 0.004 100 200
02F Fan Inlet Total Pressure PSIA 32 13 0.004 100 200
033 Fan Inlet Total Pressure PSIA 32 13 0.004 100 200
See Att. 6 and
0 3 5 Intruder Altitude 500
ARINC 735
13A Inlet Pressure PSIA 32 13 0.004 100 200
132 01A Exhaust Gas Total Pressure PSIA 32 13 0.004 100 200
01C Exhaust Gas Total Pressure PSIA 32 13 0.004 100 200
033 Exhaust Gas Total Pressure PSIA 32 14 0.002 100 250
See Att. 6 and
0 3 5 Intruder Bearing 500
ARINC 735

133 00B Aut Vert Integ Limit Feet 32,768 18 0.125 200 1200
01A Thrust Lever Angle Deg/180 ±180 12 0.05 100 250
02F Thrust Lever Angle Deg/180 ±180 12 0.05 25 50
03F Thrust Lever Angle Deg/180 ±180 12 0.05 25 50
10A Selected Throttle Lever Angle Deg 90 11 0.088 31.3 100
10B Selected Throttle Lever Angle Deg 90 11 0.088 31.3 100

134 01C Power Lever Angle Deg/180 ±180 12 0.05 100 200
10A Throttle Lever Angle Deg ±128 11 0.088 500 1000
10B Throttle Lever Angle Deg ±128 11 0.088 500 1000
13A Throttle Lever Angle Deg/180 ±180 12 0.05 25 50
 ARINC SPECIFICATION 429, PART 1 - Page 59
ATTACHMENT 2
DATA STANDARDS
TABLE 2 - BNR DATA

Min Max Max

Eqpt Transit Transit Trans-
Label ID Parameter Units Range Sig Pos Resolution Interval Interval port Notes
(Hex) Name (Scale) Bits Sense (msec) (msec) Delay
2 2 (msec)
3
135 0 1 C Engine Vibration #1 in/sec 8 12 0.002 100 200
0 2 9 Engine Fan Vibration % FS 128 7 1 100 200

136 0 0 B Vertical Figure of Merit Feet 32,768 18 0.125 200 1200

0 1 C Engine Vibration #2 in/sec 8 12 0.002 100 200

137 01B Flap Angle Deg/180 ±180 12 0.05 100 200 See Attachment 6
02A Flap Angle Deg/180 ±180 12 0.05 100 200 See Attachment 6
02F Thrust Reverser Position Feedback % 128 12 0.03 100 200
03F Thrust Reverser Position Feedback % 128 12 0.03 100 200
10A Selected Thrust Reverser Position % -5 - +105 11 0.063 62.5 250
10B Selected Thrust Reverser Position % -5 - +105 11 0.063 62.5 250
140 Flap Angle Deg 180 12 0.05 62.5 200

140 0 0 1 Flight Director - Roll Deg/180 ±180 12 0.05 50 100

0 0 B UTC Fine Seconds 1 20 0.953674µs 200 1200
0 2 5 Flight Director - Roll Deg/180 ±180 10 0.02 125 250

141 0 0 1 Flight Director - Pitch Deg/180 ±180 12 0.05 50 100

0 0 B UTC Fine Fractions Seconds 0.9536743µs 10 0.953674µs 200 1200
0 2 5 Flight Director - Pitch Deg/180 ±180 10 0.02 125 250

142 0 0 2 Flight Director - Fast/Slow Knots 32 12 0.008 31.3 62.5

0 0 3 Flight Director - Fast/Slow Knots 32 12 0.008 31.3 62.5
0 2 5 Flight Director - Fast/Slow Knots 32 8 0.125 125 250

143 0 0 1 Flight Director - Yaw Deg/180 ±180 12 0.05 50 100

0 4 1 HPA Command Word See ARINC 741
2 4 1 HPA Response Word See ARINC 741

Above
144 0 2 B Altitude Error Feet 8192 14 Cmd 1.0 25 50
Alt
0 4 1 ACU/BSU Control Word See ARINC 741
3 4 1 ACU/BSU Response Word See ARINC 741

145 0 0 2 TACAN Control See Sec. 3.1.4 180 220 See Attachment 6

146 1 1 2 TACAN Control See Sec. 3.1.4 180 220

147 X X X TACAN Control Word 100 200

150 002 Universal Coordinated Time See Table 6-12

00B UTC Hr:Min:S ±23:59:59 17 1.0sec 200 1200
031 Universal Coordinated Time 100 200 See Table 6-12
056 Universal Coordinated Time See Table 6-12
060 Universal Coordinated Time See Table 6-12

151 002 Localizer Bearing (True) Deg/180 ±180 11 0.1 167 333
027 MLS Azimuth Deviation
055 MLS AZ Deviation mV ± 2400 15 0.0732
056 Localizer Bearing (True) Deg/180 ±180 11 0.1 167 333
05A LB/KG Control Word See ARINC 429P2
060 Localizer Bearing (True) Deg/180 ±180 11 0.1 167 333

152 0 2 7 MLS Elevation Deviation

0 4 1 Open Loop Steering See ARINC 741
0 5 5 MLS GP Deviation mV ± 2400 15 0.0732

Above
153 0 0 2 Maximum Altitude Feet 65536 16 1 500 1000 100
S.L.
0 2 7 Flare
0 4 1 Closed Loop Steering See ARINC 741
0 5 5 MLS Selected Azimuth Deg 0-359 9 1
 ARINC SPECIFICATION 429, PART 1 - Page 60
ATTACHMENT 2
DATA STANDARDS
TABLE 2 - BNR DATA

Min Max Max

Eqpt Transit Transit Trans-
Label ID Parameter Units Range Sig Pos Resolution Interval Interval port Notes
(Hex) Name (Scale) Bits Sense (msec) (msec) Delay
2 2 (msec)
3

154 002 Runway Heading (True) N.M. 512 16 0.008 83.3 167
027 MLS Auxiliary Data
055 MLS Max Selectable GP Deg ± 51.1 9 1
056 Runway Heading (True) N.M. 512 16 0.008 83.3 167
060 Runway Heading (True N.M. 512 16 0.008 83.3 167

155 0 5 5 MLS Selected Glide Path Deg ± 51.1 9 0.01

162 0 1 2 ADF Bearing Deg/180 ±180 12 0.05 31.3 62.5

SDI-01=left/SDI-
0 2 5 ADF brg left/right Deg/180 ±180 12 0.05 125 250
10=right
0 2 9 Crew Oxygen Pressure PSI 4096 12 1 100 200
0 5 5 MLS Basic Data Word 5 N/A N/A N/A N/A
1 4 0 Density Altitude Feet 1131072 16 2 250 500

164 002 Minimum Descent Altitude (MDA) Feet 8192 16 0.125 500 1000
003 Target Height Feet 8192 16 0.125 500 1000
007 Radio Height Feet 8192 16 0.125 25 50
025 Radio Height Feet 8192 12 2.0 125 250
03B Radio Height VDC 32 11 0.015 150 250 Per ARINC 522A
055 MLS ABS GP Angle Deg ± 41 15 0.00125

165 0 0 B Vertical Velocity Feet/Min ± 32768 15 1.0 200 1200

0 5 5 MLS ABS Azimuth Angle Deg ± 82 16 0.00125

166 0 0 7 RALT Check Point Dev Feet 512 10 0.5 * *

0 0 B North/South Velocity Knots ± 4096 15 0.125 200

EPU Estimate Position Uncertainty

167 002 N.M. 0-128 16 0.00195
(ANP) Actual Navigation Perf.

RNP Reduced Navigation

171 002 N.M. 0-128 16 0.001953
Performance
0 5 6 Current RNP N.M. 0-128 16 0.00195
0 6 0 Current RNP N.M. 0-128 16 0.00195
X X X Manu. Specific Status Word See Attachment 6

173 010 Localizer Deviation DDM 0.4 12 0.0001 33.3 66.6

025 Localizer Deviation DDM 0.4 10 0.0004 125 250
029 Hydraulic Quantity % 128 7 1 100 200
03B Localizer Deviation Dots 4 11 0.002 150 250
055 Localizer Deviation DDM ± 0.4 12 0.0001
0BD Hydraulic Quantity % 128 7 1 500 1000
0D0 Hydraulic Oil Quantity US Pint 128 9 0.25 SDI 1= A/SDI 2= B

174 003 Delayed Flap Approach Speed (DFA) Knots 512 11 0.25 100 200
00B East/West Velocity Knots ± 4096 15 0.125 200 1200
010 Glideslope Deviation DDM 0.8 12 0.0002 33.3 66.6
029 Hydraulic Pressure PSI 4096 12 1 100 200
03B Glideslope Deviation Dots 4 11 0.0002 150 250
055 Glide Slope Deviation DDM ± 0.8 12 0.0002
0D0 Hydraulic Oil Pressure PSI 4096 12 1.0 SDI 1= A/SDI 2= B

175 0 0 3 Economical Speed Knots 1024 14 0.06 62.5 125

0 2 9 EGT (APU) Deg C 2048 11 1 100 200
0 3 3 Hydraulic Pump Case Drain Temp Deg C 256 12 0.06 100 200

176 003 Economical Mach Mach 4096 13 0.5 62.5 125

029 RPM (APU) % RPM 256 9 0.5 100 200
038 Left Static Pressure Uncorrected, mb mb 2048 18 0.008 20 200
05A Fuel Temperature - Set to Zero Deg. C 512 11 0.25 100 200
0AD Static Pressure Left, Uncorrected, mb mb 2048 18 0.008 20 200
 ARINC SPECIFICATION 429, PART 1 - Page 61
ATTACHMENT 2
DATA STANDARDS
TABLE 2 - BNR DATA

Min Max Max

Eqpt Transit Transit Trans-
Label ID Parameter Units Range Sig Pos Resolution Interval Interval port Notes
(Hex) Name (Scale) Bits Sense (msec) (msec) Delay
2 2 (msec)
3
Left Outer Tank Fuel Temp &
114 Deg ± 512 11 0.025
Advisory Warning

177 0 0 3 Economical Flight Level Feet 131072 17 1.0 31.3 62.5

0 2 9 Oil Quantity (APU) US Pint 128 9 0.25 100 200
Right Static Pressure, Uncorrected,
038 mb 2048 18 0.008 20 200
mb
0 5 5 Distance to Runway Threshold Nmiles 1024 16 0.007812
0 5 A Fuel Temp. Left Wing Tank Deg C 512 11 0.25 100 200
Static Pressure Right, Uncorrected,
0AD mb 2048 18 0.008 20 200
mb
Inner Tank 1 Fuel Temp & Advisory
114 Deg C ± 512 11 0.025
Warning

Inner Tank 2 Fuel Temp & Advisory

200 114 Deg C ± 512 11 0.025
Warning

201 0 5 A Fuel Temp. Right Wing Tank Deg C 512 11 0.25 100 200
Inner Tank 3 Fuel Temp & Advisory
114 Deg C ± 512 11 0.025
Warning
1 4 0 Mach Maximum Operation (Mmo) Mach 4096 12 0.001 62.5 125
1 4 2 Projected Future Latitude Deg ± 180 20 0.000172 150 400

202 0 0 2 Energy Management (clean) N.M. 512 15 0.016 100 200

0 0 9 DME Distance N.M. 512 16 0.008 83.3 167
0 5 A Fuel Temperature - Set to Zero Deg C 512 11 0.25 100 200
Inner Tank 4 Fuel Temp & Advisory
114 Deg C ± 512 11 0.025
Warning
1 4 0 Mach Rate M/minute 4096 12 0.001 62.5 125
1 4 2 Projected Future Latitude Fine Deg 0.000172 11 2.E-32 Cir 150 400

203 002 Energy Management Speed Brakes N.M. 512 15 0.016 100 200
006 Altitude (1013.25 mb) Feet 131072 17 1.0 31.3 62.5
018 Altitude Feet 131072 17 1.0 20 40
035 Own A/C Altitude Feet 131072 17 1.0 20 500
038 Altitude (1013.25 mb) Feet 131072 17 1.0 31.3 62.5
05A Fuel Tank #6 Temperature Deg C 512 11 0.25 100 200
10A Ambient Static Pressure PSIA 1.5 - 20.0 11 0.016 500 1000
10B Ambient Static Pressure PSIA 1.5 - 20.0 11 0.016 500 1000
Trim Tank Fuel Temp & Advisory
114 Deg C ± 512 11 0.025
Warning
1 4 0 Altitude Feet 131072 17 1 31.25 62.5

204 002 Utility Airspeed Knots 512 11 0.25 500 1000 50

006 Baro Corrected Altitude #1 Feet 131072 17 1.0 31.3 62.5
038 Baro Corrected Altitude #1 Feet 131072 17 1.0 31.3 62.5
056 Baro Altitude Knots 512 11 0.25 500 1000 50
05A Fuel Tank #7 Temperature Deg C 512 11 0.25 100 200
060 Baro Altitude Knots 512 11 0.25 500 1000 50
Right Outer Tank Fuel Temp &
114 Deg C ± 512 11 0.025
Advisory Warning
1 4 0 Baro Corrected Altitude Feet 131072 17 1 31.25 62.5

205 006 Mach Mach 4.096 16 0.0000625 62.5 125

01A Mach Mach 4.096 16 0.0000625 62.5 125
038 Mach Mach 4.096 16 0.0000625 62.5 125
05A Fuel Tank #8 Temperature Deg C 512 11 0.25 100 200
10A Mach Number Mach 1 11 0.002 100 500
10B Mach Number Mach 1 11 0.002 100 500
140 Mach Mach 4.096 16 0.00000625 62.5 125

206 0 0 6 Computed Airspeed Knots 1024 14 0.0625 62.5 125

0 1 8 Altitude (Variable Resolution) Feet Variable 15 Variable 31.3 62.5 See Attachment 6
0 3 8 Computed Airspeed Knots 1024 14 0.0625 62.5 125
 ARINC SPECIFICATION 429, PART 1 - Page 62
ATTACHMENT 2
DATA STANDARDS
TABLE 2 - BNR DATA

Min Max Max

Eqpt Transit Transit Trans-
Label ID Parameter Units Range Sig Pos Resolution Interval Interval port Notes
(Hex) Name (Scale) Bits Sense (msec) (msec) Delay
2 2 (msec)
3
0 C C Taxi Speed Knots 512 11 0.25 50 100
1 4 0 Computed Airspeed (CAS) Knots 1024 14 0.0625 62.5 125

207 006 Maximum Allowable Airspeed Knots 1024 12 0.25 62.5 125
00A Maximum Allowable Airspeed Knots 512 11 0.25 100 200
025 OP. Software Part Number See Attachment 6
038 Maximum Allowable Airspeed Knots 1024 12 0.25 62.5 125
Airspeed Maximum Operating
140 Knots 1024 12 .025 62.56 125
(VMO)

210 0 0 6 True Airspeed Knots 2048 15 0.0625 62.5 125

0 3 8 True Airspeed Knots 2048 15 0.0625 62.5 125
1 4 0 True Airspeed Knots 2048 15 0.0625 62.5 125

211 002 Total Air Temperature Deg C 512 11 0.25 250 500
003 Total Air Temperature Deg C 512 11 0.25 250 500
006 Total Air Temperature Deg C 512 11 0.25 250 500
01A Total Air Temperature Deg C 512 11 0.25 250 500
038 Total Air Temperature Deg C 512 11 0.25 250 500
0AD Total Air Temperature Indicated Deg C 512 12 0.125 250 500
10A Total Fan Inlet Temperature Deg C -80 - +90 10 0.125 500 1000
10B Total Fan Inlet Temperature Deg C -80 - +90 10 0.125 500 1000
140 Total Air Temperature (TAT) Deg C 512 12 0.125 250 500
142 Projected Future Longitude Deg ± 180 20 0.000172 250 500

212 004 Altitude Rate Ft/Min 32768 11 16 31.3 62.5

005 Altitude Rate Ft/Min 32768 11 16 31.3 62.5
006 Altitude Rate Ft/Min 32768 11 16 31.3 62.5
038 Altitude Rate Ft/Min 32768 11 16 31.3 62.5
03B Altitude Rate Ft/Min 32768 11 16 150 250
140 Altitude Rate Ft/Min 32768 11 16 31.25 62.5
142 Projected Future Longitude Fine Deg 0.000172 11 2E-32 Cir 150 400

213 002 Static Air Temperature Deg C 512 11 0.25 250 500
006 Static Air Temperature Deg C 512 11 0.25 250 500
038 Static Air Temperature Deg C 512 11 0.25 250 500
08D Fuel Used Lbs. 262144 18 1 75 125
140 Static Air Temperature (SAT) Deg C 512 11 0.25 250 500
142 Vertical Time Interval Minute 265 min 10 0.25 min 500 2000

214 X X X ICAO Aircraft Address (Part 1) See Attachment 6

215 006 Impacted Pressure mb 512 14 0.03125 62.5 125

01A Impact Pressure mb 512 14 0.03125 62.5 125
029 N1 Actual (EEC) % RPM 256 14 0.015 50 100
029 EPR Actual (EEC) 4 12 0.001 50 100
038 Impacted Pressure, Uncorrected, mb mb 512 14 0.03125 62.5 125
0AD Impacted Pressure, Uncorrected, mb mb 512 16 0.008 20 40
140 Impact Pressure Subsonic mb 512 14 0.03125 62.5 125

216 X X X ICAO Aircraft Address (Part 2)

217 002 Geometric Vertical Rate Ft/Min 20000 11 16

006 Static Pressure, Corrected (In.Hg.) in. Hg 64 16 0.001 62.5 125
029 N1 Limit (EEC) % RPM 256 14 0.015 100 200
029 EPR Limit (EEC) 4 12 0.001 100 200
Static Pressure, Average, Corrected
038 in. Hg 64 16 0.001 62.5 125
(In. Hg.)
1 4 0 Static Pressure Corrected (In. Hg.) in. Hg 64 16 0.001 62.5 125

220 0 0 6 Baro Corrected Altitude #2 Feet 131072 17 1.0 31.3 62.5

0 3 8 Baro Corrected Altitude #2 Feet 131072 17 1.0 31.3 62.5
1 4 0 Baro Corrected Altitude #2 Feet 131072 17 1 31.25 62.5
 ARINC SPECIFICATION 429, PART 1 - Page 63
ATTACHMENT 2
DATA STANDARDS
TABLE 2 - BNR DATA

Min Max Max

Eqpt Transit Transit Trans-
Label ID Parameter Units Range Sig Pos Resolution Interval Interval port Notes
(Hex) Name (Scale) Bits Sense (msec) (msec) Delay
2 2 (msec)
3
221 006 Indicated Angle of Attack (Avg) Deg/180 ±180 12 0.05 31.3 62.5
038 Indicated Angle of Attack (Average) Deg/180 ±180 12 0.05 31.3 62.5
0AD Indicated Angle of Attack Deg/180 ±180 14 0.01 31.3 200
12C Indicated Angle of Attack (Avg.) Deg/180 ±180 12 0.05 31.3 62.5
140 Angle of Attack Indicated Average Deg ±180 12 0.05 31.25 62.5

222 006 Indicated Angle of Attack (#1 Left) Deg/180 ±180 12 0.05 31.3 62.5
011 VOR Omnibearing Deg/180 ±180 12 0.004 50 100
112 TACAN Bearing Deg/180 ±180 12 0.05 180 220
115 Bearing Deg/180 ±180 11 0.1 50 50
12C Indicated Angle of Attack (#1 Left) Deg/180 ±180 12 0.05 31.3 62.5
140 Angle of Attack, Indicated #1 Left Deg ±180 12 0.05 31.5 62.5

223 0 0 6 Indicated Angle of Attack (#1 Right) Deg/180 ±180 12 0.05 31.3 62.5
1 2 C Indicated Angle of Attack (#1 Right) Deg/180 ±180 12 0.05 31.3 62.5
1 4 0 Angle of Attack, Indicated #1 Right Deg ±180 12 0.05 31.5 62.5

224 0 0 6 Indicated Angle of Attack (#2 Left) Deg/180 ±180 12 0.05 31.3 62.5
1 2 C Indicated Angle of Attack (#2 Left) Deg/180 ±180 12 0.05 31.3 62.5
1 4 0 Angle of Attack, Indicated #2 Left Deg ±180 12 0.05 31.5 62.5

225 0 0 2 Minimum Maneuvering Airspeed Knots 512 11 0.25 500 1000 50

0 0 6 Indicated Angle of Attack (#2 Right) Deg/180 ±180 12 0.05 31.3 62.5
Increas
0 2 B Compensated Altitude Rate Ft/Min 32768 11 16.0 31.3 62.5
-ing alt
056 Minimum Maneuvering Air Speed Knots 512 11 0.25 500 1000
060 Minimum Maneuvering Air Speed Knots 512 11 0.25 500 1000
12C Indicated Angle of Attack (#2 Right) Deg/180 ±180 12 0.05 31.3 62.5
140 Angle of Attack, Indicated #2 Right Deg ±180 12 0.05 31.5 62.5

227 0 3 D AVM Command See ARINC 429P2

0 7 E BITE Command Word See ARINC 604

231 0 A D Total Air Temperature Deg C 512 12 0.12 20 200

233 002 ACMS Information See Attachment 6

056 ACMS Information
060 ACMS Information
234 002 ACMS Information See Attachment 6
056 ACMS Information
060 ACMS Information

235 0 0 2 ACMS Information See Attachment 6

0 5 6 ACMS Information
0 6 0 ACMS Information

236 0 0 2 ACMS Information See Attachment 6

0 5 6 ACMS Information
0 6 0 ACMS Information

237 002 ACMS Information

00B Horizontal Uncertainty Level N.M. 16 17 0.000122 1200 See ARINC 743A
056 ACMS Information
060 ACMS Information

241 002 Min. Airspeed for Flap Extension Knots 512 11 0.25 500 1000 50
006 Corrected Angle of Attack Deg/180 ±180 12 0.05 31.3 62.5
038 Corrected Angle of Attack Deg/180 ±180 12 0.05 31.3 62.5
04D FQIS System Data 500 1024 See Attachment 6
056 Min. Airspeed for Flap Extension Knots 512 11 0.25 500 1000
060 Min. Airspeed for Flap Extension Knots 512 11 0.25 500 1000
140 Angle of Attack, Corrected Deg ±180 12 0.05 31.5 62.5
 ARINC SPECIFICATION 429, PART 1 - Page 64
ATTACHMENT 2
DATA STANDARDS
TABLE 2 - BNR DATA

Min Max Max

Eqpt Transit Transit Trans-
Label ID Parameter Units Range Sig Pos Resolution Interval Interval port Notes
(Hex) Name (Scale) Bits Sense (msec) (msec) Delay
2 2 (msec)
3
242 006 Total Pressure mb 2048 16 0.03125 62.5 125
01A Total Pressure mb 2048 16 0.03125 62.5 125
038 Total Pressure mb 2048 16 0.03125 62.5 125
03B Speed Deviation Dots 4 11 0.002 150 250
056 Modified Intent Data Block
0AD Total Pressure, Uncorrected, mb mb 2048 18 0.008 20 200
140 Total Pressure mb 2048 16 0.03125 62.5 125

243 X X X Simulator to Avcs Control Word 33 100 See ARINC Rpt 610

244 01C Fuel Flow (Engine Direct) Lbs/hr 32768 8 128.0 100 200
033 Fuel Flow (Wf) pph 32768 16 0.5 150 250
03B Mach Error Mach 0.064 11 0.00003 150 250
08D Fuel Flow Rate PPH 32768 16 0.5 75 125
10A Fuel Mass Flow MSEC 170 15 0.008 31.3 100
10B Fuel Mass Flow MSEC 170 15 0.008 31.3 100
140 Angle of Attack, Normalized Ratio 2 11 0.001 62.5 125

245 002 Minimum Airspeed Knots 256 12 0.0625 62.5 125

003 Minimum Airspeed Knots 256 12 0.0625 62.5 125
00A Minimum Airspeed Knots 512 13 0.0625 62.5 125
029 N3 (Engine) % RPM 256 14 0.015 50 100
038 Avg. Static Pres. mb uncorrected mb 2048 16 0.03125 62.5 125
03B EPR Error 4 12 0.001 150 250
Average Static Pressure mb
0AD mb 2048 16 0.03125 62.5 125
Uncorrected
056 Minimum Airspeed Knots 256 12 0.0625 62.5 125
060 Minimum Airspeed Knots 256 12 0.0625 62.5 125
140 Static Pressure, Uncorrected mb 2048 16 0.03125 62.5 125

246 002 Control Maximum Speed (VCMAX) Knots 512 11 0.25 50 100 50
006 Average Static Pressure mb 2048 16 0.03 62.5 125
01C N1 (Engine Direct) RPM 4096 12 1.0 100 200
029 N1 (Engine Direct) % RPM 256 14 0.015 50 100
038 Avg Static Pres mb Corrected mb 2048 16 0.03125 62.5 125
03B Angle of Attack Error Deg/180 ±180 14 0.01 150 250
247 002 Control Min. Speed (VCMIN) Knots 512 11 0.25 50 100 50
00B Horizontal Figure of Merit N.M. 16 18 6.1 E-5 200 1200
01F Total Fuel Lbs. 655360 14 40 500 1000
02C Total Fuel Lbs. 655360 14 40 500 1000
03B Speed Error Knots 256 12 0.06 150 250
04D Total Fuel Lbs. 655360 14 40 500 1000
056 Control Minimum Speed (Vcmin) Knots 512 11 0.25 50 100
05A Total Fuel Lbs. 655360 14 40 100 200
060 Control Minimum Speed (Vcmin) Knots 512 11 0.25 50 100
0EB Fuel to Remain Lbs. 1638400 14 100 100 125
114 Fuel on Board Lbs. 655320 13 40
140 Airspeed Minimum Vmc Knots 512 11 0.25 62.5 125

250 002 Continuous N1 Limit % RPM 256 14 0.015 50 200 200

02B Maximum Continuous EPR Limit - 4 12 0.001 100 200
02C Preselected Fuel Quantity Lbs. 655360 14 40 100 400
05A Preselected Fuel Quantity Lbs. 655360 14 40 100 200
038 Indicated Side Slip Angle Deg/180 ±180 12 0.05 31.3 62.5
0AD Indicated Side Slip Angle or AOS Deg/180 ±180 14 0.01 31.3 200
114 Preselected Fuel Quantity Lbs. 655320 13 40

251 001 Distance to Go N.M. 4096 15 0.125 100 200

002 Distance to Go N.M. 4096 15 0.125 100 200
006 Baro Corrected Altitude #3 Feet 131072 17 1.0 31.3 62.5
01A Flight Leg Counter 75 175 See Attachment 6
038 Baro Corrected Altitude #3 Feet 131072 17 1.0 31.3 62.5

252 0 0 1 Time to Go Min. 512 9 1.0 100 200

 ARINC SPECIFICATION 429, PART 1 - Page 65
ATTACHMENT 2
DATA STANDARDS
TABLE 2 - BNR DATA

Min Max Max

Eqpt Transit Transit Trans-
Label ID Parameter Units Range Sig Pos Resolution Interval Interval port Notes
(Hex) Name (Scale) Bits Sense (msec) (msec) Delay
2 2 (msec)
3
002 Time to Go Min. 512 9 1.0 100 200
006 Baro Corrected Altitude #4 Feet 131072 17 1.0 31.3 62.5
01A EPR Idle 4 12 0.001 100 200
02F EPR Idle Reference - 4 12 0.001 100 200
038 Baro Corrected Altitude #4 Feet 131072 17 1.0 31.3 62.5
03F EPR Idle Reference 4 12 0.001 100 200
0EB Time Until Jettison Complete Minutes 64 6 1 500 1000

253 0 0 2 Go-Around N1 Limit % RPM 256 14 0.015 50 200 200

0 1 E Go-Around EPR Limit 4 12 0.001 100 200
0 3 8 Corrected Side Slip Angle Deg/180 ±180 12 0.05 31.3 62.5

254 002 Cruise N1 Limit % RPM 256 14 0.015 50 200 200

01E Cruise EPR Limit 4 12 0.001 100 200
04D Actual Fuel Quan (test) Lbs 262144 15 8 500 1000
13A N1 Cruise % N1 Nom 256 14 0.015 100 200
140 Altitude Rate Ft/Min 131072 13 16 31.25 62.5

255 002 Climb N1 Limit % RPM 256 14 0.015 50 200 200

01E Climb EPR Limit 4 12 0.001 100 200
02F Maximum Climb EPR Rating N/A 4 12 0.001 100 200
03F Maximum Climb EPR Rating N/A 4 12 0.001 100 200
04D Fuel Quantity (gal) Gallons 32768 15 1.0 500 1000
08E Spoiler Position Deg/180 +180 11 0.1 50 100
13A N1 Climb % N1 Nom 256 14 0.015 100 200
140 Impact Pressure mb 4096 17 0.03125 62.5 125

256 002 Time For Climb Min. 512 9 1 100 200

00A V Stick Shaker Knots 512 11 0.25 100 200
02C Fuel Quantity (Tanks) #1 Lbs. 131072 15 4 500 1000
04D Fuel Discretes TBD TBD See ARINC 429P2
056 Time for Climb Min. 512 9 1 100 200
05A Fuel Quantity-Left Outer Cell Lbs. 131072 15 4 100 200 Zero for A-321
060 Time for Climb Min. 512 9 1 100 200
114 Left Outer Tank Fuel Quantity Lbs. 131072 15 4
140 Equivalent Airspeed Knots 1024 14 0.0625 62.5 125

257 002 Time For Descent Min. 512 9 1 100 200

02C Fuel Quantity (Tanks) #2 Lbs. 131072 15 4 500 1000
056 Time for Descent Min. 512 9 1 100 200
05A Fuel Quantity Left W/T Tank Lbs. 131072 15 4 100 200
060 Time for Descent Min. 512 9 1 100 200
114 Fuel Quantity (Tanks) #2 Lbs. 131072 15 4 500 1000
140 Total Pressure (High Range) mb 4096 17 0.03125 62.5 125

260 02C Fuel Quantity (Tanks) #3 Lbs. 131072 15 4 500 1000

05A Fuel Quantity Center Tank Lbs. 131072 15 4 100 200
033 T5 Deg C 1024 12 0.25 150 250 See Note [5]
10A LP Turbine Discharge Temp Deg C -55 - +850 11 0.50 100 500
10B LP Turbine Discharge Temperature Deg C -55 - +850 11 0.50 100 500
114 Collector Cell 1 and 2 Fuel Quantity Lbs. 131072 15 4

261 02C Fuel Quantity (Tanks) #4 Lbs. 131072 15 4 500 1000

033 P49 PSIA 128 14 0.008 150 250
05A Fuel Qty Right I/C or W/T Tank Lbs. 131072 15 4 100 200
10A LP Turbine Inlet Pressure PSIA 2-120 11 0.125 100 500
10B LP Turbine Inlet Pressure PSIA 2-120 11 0.125 100 500
114 Fuel on Board at Engine Start Lbs. 131072 15 4

262 002 Documentary Data 500 1000 See Attachment 6

00A Predicitive Airspeed Variation Knots 256 10 0.25 100 200
01C LP Compressor Exist Pres. (PT3) PSIA 64 13 0.008 100 200
02C Fuel Quantity (Tanks) #5 Lbs. 131072 15 4 500 1000
033 LP Compressor Exist Pressure PSIA 64 14 0.004 150 250
 ARINC SPECIFICATION 429, PART 1 - Page 66
ATTACHMENT 2
DATA STANDARDS
TABLE 2 - BNR DATA

Min Max Max

Eqpt Transit Transit Trans-
Label ID Parameter Units Range Sig Pos Resolution Interval Interval port Notes
(Hex) Name (Scale) Bits Sense (msec) (msec) Delay
2 2 (msec)
3
04D T/U Cap-L Tank 1-4 PF 655.35 16 0.01 TBD TBD
05A Fuel Quantity-Right Outer Cell Lbs. 131072 15 4 100 200
10A HP Compressor Inlet Total Pres. PSIA 2-50 11 0.032 100 500
10B HP Compressor Inlet Total Pres. PSIA 2-50 11 0.032 100 500
114 Center Tank Fuel Quantity Lbs. 131072 15 4

263 002 Min. Airspeed for Flap Retraction Knots 512 11 0.25 500 1000 50
00A Min. Airspeed for Flap Retraction Knots 512 11 0.25 100 200
01C LP Compressor Exit Temperature 256 12 0.06 100 200
02C Fuel Quantity (Tanks) #6 Lbs 131072 15 4 500 1000
033 LP Compressor Exit Temperature Deg C 256 12 0.063 150 250
04D T/U Cap-L Tank 5-8 PF 655.35 16 0.01 TBD TBD
056 Min. Airspeed for Flap Retraction Knots 512 11 0.25 500 1000
060 Min. Airspeed for Flap Retraction Knots 512 11 0.25 500 1000
Selected Compressor Inlet
10A Deg C -55 - +160 11 0.125 100 500
Temperature (Total)
Selected Compressor Inlet Temp
10B Deg C -55 - +160 11 0.125 100 500
(Total)
1 1 4 Collector Cell 3 and 4 Fuel Quantity Lbs. 131072 15 4

264 002 Time To Touchdown Min. 2048 11 1 100 200 145

00A Min. Airspeed for Slats Retraction Knots 512 11 0.25 100 200
01C HP Compressor Exit Pressure 512 14 0.03 100 200
02C Fuel Quantity (Tanks) #7 Lbs. 131072 15 4 500 1000
02F Burner Pressure PSIA 512 14 0.03 100 200
04D T/U Cap-L Tank 9-12 PF 655.35 16 0.01 TBD TBD
033 HP Compressor Exit Pressure PSIA 512 14 0.03 150 250
03F Burner Pressure PSIA 512 14 0.03 100 200
056 Time to Touchdown Min. 2048 11 1 100 200
060 Time to Touchdown Min. 2048 11 1 100 200
10A Selected Compressor Dischg Pres. PSIA 5-600 11 1.00 62.5 250
10B Selected Compressor Dischg Pres. PSIA 5-600 11 1.00 62.5 250
13A Burner Pressure PSIA 512 14 0.031 100 200

265 002 Min. Buffet Airspeed Knots 512 11 0.25 50 100 50

004 Integrated Vertical Acceleration Ft/Sec ±256 20 UP 0.000244 20
00A Maneuvering Airspeed Knots 512 11 0.25 100 200
01C HP Compressor Exit Temp (TT4.5) 1024 12 0.25 100 200
02C Fuel Quantity (Tanks) #8 Lbs. 131072 15 4 500 1000
033 HP Compressor Exit Temperature Deg C 1024 12 0.25 150 250
038 Integrated Vertical Acceleration Ft/Sec ±256 20 UP 0.000244 20
04D T/U Cap-L Tank 13-14 PF 655.35 16 0.01 TBD TBD
056 Min. Buffet Airspeed Knots 512 11 0.25 50 100
060 Min. Buffet Airspeed Knots 512 11 0.25 50 100
10A Selected Compressor Dischg Temp Deg C -55 - +650 11 0.50 100 500
10B Selected Compressor Dischg Temp Deg C -55 - +650 11 0.50 100 500
114 Inner Tank 3 Fuel Quantity Lbs. 131072 15 4

266 0 4 D T/U Cap-C Tank 1-4 PF 655.35 16 0.01 TBD TBD

1 1 4 Inner Tank 2 Fuel Quantity Lbs. 131072 15 4

267 002 Maximum Maneuver Airspeed Knots 512 11 0.25 500 1000 50
00A Predictive Max. Maneuver Speed Knots 512 11 0.25 100 200
02B Throttle Position Command Deg/180 ±180 12 0.05 50 100
04D T/U Cap-C Tank 5-8 PF 655.35 16 0.01 TBD TBD
033 Spare T/C Deg C 256 12 0.063 150 250
056 Max. Maneuver Airspeed Knots 512 11 0.25 500 1000
060 Max. Maneuver Airspeed Knots 512 11 0.25 500 1000
10A HP Compressor Inlet Temp. (total) Deg C -55 - +160 11 0.125 500 1000
10B HP Compressor Inlet Temperature Deg C -55 - +160 11 0.125 500 1000
114 Inner Tank 4 Fuel Quantity Lbs. 131072 15 4

270 04D T/U Cap-C Tank 9 PF 655.35 16 0.01 TBD TBD

115 Stored TACAN Control Word 25 50 See ARINC 429P2
 ARINC SPECIFICATION 429, PART 1 - Page 67
ATTACHMENT 2
DATA STANDARDS
TABLE 2 - BNR DATA

Min Max Max

Eqpt Transit Transit Trans-
Label ID Parameter Units Range Sig Pos Resolution Interval Interval port Notes
(Hex) Name (Scale) Bits Sense (msec) (msec) Delay
2 2 (msec)
3

271 04D T/U Cap-A Tank 1-4 PF 655.35 16 0.01 TBD TBD

272 04D T/U Cap Tank 5-8 PF 655.35 16 0.01 TBD TBD

273 04D T/U Cap-A Tank 9-11 PF 655.35 16 0.01 TBD TBD

274 04D T/U Cap-R Tank 1-4 PF 655.35 16 0.01 TBD TBD

275 04D T/U Cap-R Tank 5-8 PF 655.35 16 0.01 TBD TBD

Used only in
276 001 FCC to Simulator Control Word 50 150
simulator
Used only in
002 FMC to Simulator Control Word 33 100
simulator
Used only in
003 TCC to Simulator Control Word 50 150
simulator
04D T/U Cap-R Tank 9-12 PF 655.35 16 0.01 TBD TBD

277 04D T/U Cap-R Tank 13-14 PF 655.35 16 0.01 TBD TBD

300 10A ECU Internal Temperature Deg C -55 - +125 11 0.125 500 1000
10B ECU Internal Temperature Deg C -55 - +125 11 0.125 500 1000

301 10A Demanded Fuel Metering Valve Pos % 100 11 0.063 62.5 250
10B Demanded Fuel Metering Valve Pos % 100 11 0.063 62.5 250

302 10A Demanded Variable Stator Vane Pos % 100 11 0.063 100 500
10B Demanded Variable Stator Vane Pos % 100 11 0.063 100 500

303 10A Demanded Variable Bleed Valve Pos % 100 11 0.063 100 500
10B Demanded Variable Bleed Valve Pos % 100 11 0.063 100 500

304 10A Demanded HPT Clearance Valve Pos % 100 11 0.063 250 1000
10B Demanded HPT Clearance Valve Pos % 100 11 0.063 250 1000

305 10A Demanded LPT Clearance Valve Pos % 100 11 0.063 250 1000
10B Demanded LPT Clearance Valve Pos % 100 11 0.063 250 1000

0-180N/
310 002 Present Position - Latitude Deg/180 20 0.000172 100 200
0-180S
0-180N/
004 Present Position - Latitude Deg/180 20 0.000172 100 200
0-180S
029 Aileron Position Deg/180 ±180 11 0.088 50 100
0-180N/
038 Present Position - Latitude Deg/180 20 0.000172 100 200
0-180S
See Att. 6 for SDI
04D Comp Cap-Tank PF 327.67 15 0.01 TBD TBD
encoding
0-180N/
056 Present Position Latitude Deg/180 20 0.000172 100 200
0-180S
0-180N/
060 Present Position Latitude Deg/180 20 0.000172 100 200
0-180S
114 Right Outer Tank Fuel Quantity Lbs. 131068 15 4

0-180E/
311 002 Present Position - Longitude Deg/180 20 0.000172 100 200
0-180W
0-180E/
004 Present Position - Longitude Deg/180 20 0.000172 100 200
0-180W
029 Aileron Trim Deg/180 ±180 11 0.088 50 100
0-180E/
038 Present Position - Longitude Deg/180 20 0.000172 100 200
0-180W
 ARINC SPECIFICATION 429, PART 1 - Page 68
ATTACHMENT 2
DATA STANDARDS
TABLE 2 - BNR DATA

Min Max Max

Eqpt Transit Transit Trans-
Label ID Parameter Units Range Sig Pos Resolution Interval Interval port Notes
(Hex) Name (Scale) Bits Sense (msec) (msec) Delay
2 2 (msec)
3
03B Control Wheel Roll Force Lbs. 64 10 0.0625 150 250
0-180E/
056 Present Position Longitude Deg/180 20 0.000172 100 200
0-180W
0-180E/
060 Present Position Longitude Deg/180 20 0.000172 100 200
0-180W
114 Trim Tank Fuel Quantity Lbs. 131072 15 4

312 002 Ground Speed Knots 4096 15 0.125 25 50

004 Ground Speed Knots 4096 15 0.125 25 50
005 Ground Speed Knots 4096 15 0.125 25 50
029 Rudder Position Deg/180 ±180 11 0.088 50 100
038 Ground Speed Knots 4096 15 0.125 25 50
056 Ground Speed Knots 4096 15 0.125 25 50
05A Fuel Quantity ACT 1 Lbs. 131072 15 4 100 200
060 Ground Speed Knots 4096 15 0.125 25 50
Additional Center Tank (Act 1) Fuel
114 Lbs. 131072 15 4
Quantity

313 002 Track Angle - True Deg/180 ±180 12 0.05 25 50

004 Track Angle - True Deg/180 ±180 15 0.0055 25 50
025 Track Angle - True Deg/180 ±180 10 0.2 125 250
029 Rudder Trim Deg/180 ±180 11 0.088 50 100
038 Track Angle - True Deg/180 ±180 15 0.0055 25 50
056 Track Angle - True Deg/180 ±180 12 0.05 25 50
05A Fuel Quantity ACT 2 Lbs. 131072 15 4 100 200
060 Track Angle - True Deg/180 ±180 12 0.05 25 50
Additional Center Tank (Act 2) Fuel
114 Lbs. 131072 15 4
Quantity

TE
314 002 Stabilizer Pos Indication (B747-400) Deg/180 ±180 12 0.05 25 50 50
Down
004 True Heading Deg/180 ±180 15 0.0055 25 50
025 True Heading Deg/180 ±180 10 0.2 125 250
029 Elevator Position Deg/180 ±180 11 0.088 50 100
038 True Heading Deg/180 ±180 15 0.0055 25 50
03B Control Wheel Pitch Force Lbs. 64 10 0.0625 150 250
Rear Center tank (RCT) Fuel
114 Lbs. 131072 15 4
Quantity

TE
315 001 Stabilizer Position Deg/180 ±180 12 0.05 25 50
Down
002 Wind Speed Knots 256 8 1.0 50 100
004 Wind Speed Knots 256 8 1.0 50 100
005 Wind Speed Knots 256 8 1.0 50 100
TE
029 Stabilizer Position Deg/180 ±180 11 0.088 50 100
Down
038 Wind Speed Knots 256 8 1.0 50 100
056 Wind Speed Knots 256 8 1.0 50 100
060 Wind Speed Knots 256 8 1.0 50 100
TE
0A1 Stabilizer Position Deg/180 ±180 12 0.05 25 50
Down

CW
316 002 Wind Direction (True) Deg/180 +180 12 from 0.05 25 50 50
north
004 Wind Angle Deg/180 ±180 8 0.7 50 100
029 Oil Temperature (Engine) Deg C 2048 12 0.5 100 200
038 Wind Angle Deg/180 ±180 8 0.7 50 100
CW
056 Wind Direction (True) Deg/180 +180 12 from 0.05 25 50 50
north
 ARINC SPECIFICATION 429, PART 1 - Page 69
ATTACHMENT 2
DATA STANDARDS
TABLE 2 - BNR DATA

Min Max Max

Eqpt Transit Transit Trans-
Label ID Parameter Units Range Sig Pos Resolution Interval Interval port Notes
(Hex) Name (Scale) Bits Sense (msec) (msec) Delay
2 2 (msec)
3
CW
060 Wind Direction (True) Deg/180 +180 12 from 0.05 25 50 50
north
10A Engine Oil Temperature Deg C -55 - +170 11 1.00 250 1000
10B Engine Oil Temperature Deg C -55 - +170 11 1.00 250 1000
0D0 Engine Oil Temperature Deg C 2048 12 0.5 SDI 1=L SDI 2 =R

317 002 Track Angle - Magnetic Deg/180 ±180 12 0.05 25 50

004 Track Angle - Magnetic Deg/180 ±180 15 0.0055 25 50
005 Track Angle - Magnetic Deg/180 ±180 15 0.0055 25 50
025 Track Angle - Magnetic Deg/180 ±180 10 0.2 125 250
029 Oil Pressure (Engine) PSI 4096 12 1 50 100
038 Track Angle - Magnetic Deg/180 ±180 15 0.0055 25 50
056 Track Angle Magnetic Deg/180 ±180 12 0.05 25 50
060 Track Angle Magnetic Deg/180 ±180 12 0.05 25 50
0D0 Engine Oil Pressure PSI 4096 14 0.25 SDI 1 = L/SDI 2 = R

320 004 Magnetic Heading Deg/180 ±180 15 0.0055 25 50

005 Magnetic Heading Deg/180 ±180 15 0.0055 25 50
025 Magnetic Heading Deg/180 ±180 10 0.2 125 250
035 Own A/C Magnetic Heading Deg/180 ±180 15 0.0055 25 500 See ARINC 735
038 Magnetic Heading Deg/180 ±180 15 0.0055 25 50
See Att. 6 for SDI
04D Density-Tank Lb/Gal 8.191 13 0.001 TBD TBD
encoding

321 002 Drift Angle Deg/180 ±180 12 0.05 25 50

004 Drift Angle Deg/180 ±180 11 0.09 25 50
005 Drift Angle Deg/180 ±180 11 0.09 25 50
038 Drift Angle Deg/180 ±180 12 0.05 25 50
056 Drift Angle Deg/180 ±180 12 0.05 25 50
060 Drift Angle Deg/180 ±180 12 0.05 25 50
10A Exhaust Gas Temperature (Total) Deg C -55 - +1100 11 1.00 500 1000
10B Exhaust Gas Temperature (Total) Deg C -55 - +1100 11 1.00 500 1000

322 002 Flight Path Angle Deg/180 +180o 12 0.05 25 50

004 Flight Path Angle Deg/180 ±180 12 0.05 25 50
005 Flight Path Angle Deg/180 ±180 12 0.05 25 50
038 Flight Path Angle Deg/180 ±180 12 0.05 25 50
056 Flight Path Angle Deg/180 +180o 12 0.05 25 50
060 Flight Path Angle Deg/180 +180o 12 0.05 25 50
10A Total Compressor Discharge Temp Deg C -55 - +650 11 0.50 500 1000
10B Total Compressor Discharge Temp Deg C -55 - +650 11 0.50 500 1000

323 002 Geometric Altitude Feet 50000 17 1

004 Flight Path Acceleration g 4 12 0.001 10 20
005 Flight Path Acceleration g 4 12 0.001 10 20
038 Flight Path Acceleration g 4 12 0.001 10 20
056 Geometric Altitude Feet 50000 17 1
060 Geometric Altitude Feet 50000 17 1
10A Variable Stator Vane Position % -5 - +105 11 0.063 500 1000
10B Variable Stator Vane Position % -5 - +105 11 0.063 500 1000

324 004 Pitch Angle Deg/180 ±180 14 0.01 10 20

005 Pitch Angle Deg/180 ±180 14 0.01 10 20
025 Pitch Angle Deg/180 ±180 10 0.2 125 250
038 Pitch Angle Deg/180 ±180 14 0.01 10 20
See Att. 6 for SDI
04D Tank VSO Quantity Gal. 32768 15 1.0 TBD TBD
encoding
05A Effective Pitch Angle Deg./180 ±180 14 0.01
10A Selected Fuel Metering Valve Pos % -5 - +105 11 0.063 62.5 250
 ARINC SPECIFICATION 429, PART 1 - Page 70
ATTACHMENT 2
DATA STANDARDS
TABLE 2 - BNR DATA

Min Max Max

Eqpt Transit Transit Trans-
Label ID Parameter Units Range Sig Pos Resolution Interval Interval port Notes
(Hex) Name (Scale) Bits Sense (msec) (msec) Delay
2 2 (msec)
3
10B Selected Fuel Metering Valve Pos % -5 - +105 11 0.063 62.5 250
114 Effective Pitch Angle Deg ±180 13 0.02

325 004 Roll Angle Deg/180 ±180 14 0.01 10 20

005 Roll Angle Deg/180 ±180 14 0.01 10 20
01A Engine Control Trim Feedback
025 Roll Angle Deg/180 ±180 10 0.2 125 250
02F Stator Vane Feedback Inches 4 12 0.001 100 200
038 Roll Angle Deg/180 ±180 14 0.01 10 20
03F Stator Vane Feedback Inches 4 12 0.001 100 200
05A Effective Roll Angle Deg/180 ±180 14 0.01
10A Selected Variable Stator Vane Pos % -5 - +105 11 0.063 62.5 250
10B Selected Variable Stator Vane Pos % -5 - +105 11 0.063 62.5 250
114 Effective Roll Angle Deg ±180 13 0.02

326 004 Body Pitch Rate Deg/Sec 128 13 0.015 10 20

005 Body Pitch Rate Deg/Sec 128 13 0.015 10 20
038 Body Pitch Rate Deg/Sec 128 13 0.015 10 20
04D Uplift Quantity Lbs 1638400 14 100 TBD TBD
10A Compressor Discharge Static Press PSIA 5-600 11 1.00 500 1000
10B Compressor Discharge Static Press PSIA 5-600 11 1.00 500 1000

327 004 Body Roll Rate Deg/Sec 128 13 0.015 10 20

005 Body Roll Rate Deg/Sec 128 13 0.015 10 20
038 Body Roll Rate Deg/Sec 128 13 0.015 10 20
04D Uplift Density Lbs/Gal 8.181 13 0.001 TBD TBD
10A Fuel Metering Valve Position % -5 - +105 11 0.063 500 1000
10B Fuel Metering Valve Position % -5 - +105 11 0.063 500 1000

330 004 Body Yaw Rate Deg/Sec 128 13 0.015 10 20

005 Body Yaw Rate Deg/Sec 128 13 0.015 10 20
02F HC/TC Cooling Valve Pos. Feedback % 128 12 OPEN 0.03 100 200
038 Body Yaw Rate Deg/Sec 128 13 0.015 10 20
03F HC/TC Cooling Valve Pos. Feedback % 128 12 OPEN 0.03 100 200
Selected HPT Clearance Valve
10A % -5 - +105 11 0.063 250 1000
Position
10B Selected HPT Clearance Valve Pos % -5 - +105 11 0.063 250 1000

331 004 Body Longitudinal Acceleration g 4 12 0.001 10 20

005 Body Longitudinal Acceleration g 4 12 0.001 10 20
02F LTC Cooling Valve Pos. Feedback % 128 12 OPEN 0.03 100 200
038 Body Longitudinal Acceleration g 4 12 0.001 10 20
03F LTC Cooling Valve Pos. Feedback % 128 12 OPEN 0.03 100 200
10A Selected LPT Clearance Valve Pos % -5 - +105 11 0.063 250 1000
10B Selected LPT Clearance Valve % -5 - +105 11 0.063 250 1000

332 004 Body Lateral Acceleration g 4 12 0.001 10 20

005 Body Lateral Acceleration g 4 12 0.001 10 20
02F A/O Heat Xchr Valve Pos. Feedback % 128 12 OPEN 0.03 100 200
038 Body Lateral Acceleration g 4 12 0.001 10 20
03F A/O Heat Xchr Valve Pos. Feedback % 128 12 OPEN 0.03 100 200

333 004 Body Normal Acceleration g 4 12 0.001 10 20

005 Body Normal Acceleration g 4 12 0.001 10 20
02F Acceleration Fuel Flow Limit Lb/Hr 32768 12 8 100 200
038 Body Normal Acceleration g 4 12 0.001 10 20
03F Acceleration Fuel Flow Limit Lb/Hr 32768 12 8 100 200

334 004 Platform Heading Deg/180 ±180 11 0.09 20 40

005 Platform Heading Deg/180 ±180 11 0.09 20 40
 ARINC SPECIFICATION 429, PART 1 - Page 71
ATTACHMENT 2
DATA STANDARDS
TABLE 2 - BNR DATA

Min Max Max

Eqpt Transit Transit Trans-
Label ID Parameter Units Range Sig Pos Resolution Interval Interval port Notes
(Hex) Name (Scale) Bits Sense (msec) (msec) Delay
2 2 (msec)
3
02F Fuel Flow Command Lb/Hr 32768 12 8 100 200
038 Platform Heading Deg/180 ±180 11 0.09 20 40
03F Fuel Flow Command Lb/Hr 32768 12 8 100 200

335 002 Track Angle Rate Deg/Sec 32 11 0.015 10 20

004 Track Angle Rate Deg/Sec 32 11 0.015 10 20
005 Track Angle Rate Deg/Sec 32 11 0.015 10 20
02F 2.5 BLD Actuator Position % 128 12 0.031 100 200
038 Track Angle Rate Deg/Sec 32 11 0.015 10 20
03F 2.5 BLD Actuator Position % 128 12 0.031 100 200
056 Track Angle Rate Deg/Sec 32 11 0.015 10 20
060 Track Angle Rate Deg/Sec 32 11 0.015 10 20
10A Selected Variable Bleed Valve Pos % -5 - +105 11 0.063 100 500
10B Selected Variable Bleed Valve Pos % -5 - +105 11 0.063 100 500

336 002 Max Climb Angle Deg 32 15 Climb 0.001 100 200
004 Inertial Pitch Rate Deg/Sec 128 13 0.015 10 20
005 Inertial Pitch Rate Deg/Sec 128 13 0.015 10 20
01A Engine Torque % 256 12 0.063 100 200
02F N2 Corrected to Sta 2.5 % 128 12 0.031 100 200
038 Inertial Pitch Rate Deg/Sec 128 13 0.015 10 20
03F N2 Corrected to Sta 2.5 % 128 12 0.031 100 200
10A Variable Bleed Valve Position % -5 - +105 11 0.063 500 1000
10B Variable Bleed Valve Position % -5 - +105 11 0.063 500 1000

337 002 EPR - Required For Level Flight Ratio ±4 12 0.001 100 200 Engine Types: P&W
002 N1 - Required For Level Flight % RPM ±256 15 0.015 Engine Types: GE
004 Inertial Roll Rate Deg/Sec 128 13 0.015 10 20
005 Inertial Roll Rate Deg/Sec 128 13 0.015 10 20
01A Engine Rating % 0-256 12 0.063 100 200
038 Inertial Roll Rate Deg/Sec 128 13 0.015 10 20
10A HPT Clearance Valve Position % -5 - +105 11 0.063 500 1000
10B HPT Clearance Valve Position % -5 - +105 11 0.063 500 1000

340 003 EPR Actual 4 12 0.001 100 200

004 Inertial Yaw Rate Deg/Sec 128 13 0.015 10 20
004 Track Angle Grid Deg ± 180 15 0.0055 20 Hz 110 Hz
005 Inertial Yaw Rate Deg/Sec 128 13 0.015 10 20
01A EPR Actual 4 12 0.001 100 200
029 EPR Actual (Engine Direct) 4 12 0.001 50 100
02D EPR Actual 4 12 0.001 100 200
02F EPR Actual 4 12 0.001 25 50
033 EPR Actual 4 12 0.001 100 200
03F EPR Actual 4 12 0.001 25 50
13A N1 Take Off % N1Nom 256 14 0.015 25 50
140 Pressure Ratio (Pt/Ps) Ratio 16 14 0.001 62.5 125

341 002 Target N1 % RPM 256 14 0.015 100 200

003 N1 Command % RPM 256 14 0.015 100 200
003 EPR Command 4 12 0.001 100 200
004 Grid Heading Deg ± 180 15 0.0055 20 Hz 110 Hz
01A N1 Command % RPM 256 14 0.015 100 200
01A EPR Command 4 12 0.001 100 200
029 N1 Command (Engine) % RPM 256 14 0.015 50 100
029 EPR Command (Engine) 4 12 0.001 50 100
02F N1 Command % RPM 256 14 0.015 25 50
02F EPR Command 4 12 0.001 25 50
038 Grid Heading Deg ± 180 15 0.0055 20 Hz 110 Hz
03F EPR Command 4 12 0.001 100 200
04D I/O S/W REV 1&2 (1) 16 N/A TBD TBD
 ARINC SPECIFICATION 429, PART 1 - Page 72
ATTACHMENT 2
DATA STANDARDS
TABLE 2 - BNR DATA

Min Max Max

Eqpt Transit Transit Trans-
Label ID Parameter Units Range Sig Pos Resolution Interval Interval port Notes
(Hex) Name (Scale) Bits Sense (msec) (msec) Delay
2 2 (msec)
3
10A Command Fan Speed % 117.5 13 0.032 31.3 100
10B Command Fan Speed % 117.5 13 0.032 31.3 100
13A N1 Reference % N1Nom 256 14 0.015 25 50
140 Pressure Ratio (Ps/Pso) Ratio 4 12 0.001 62.5 125

342 002 N1 Bug Drive % RPM 256 14 0.015 100 200

003 N1 Limit % RPM 256 14 0.015 100 200
003 EPR Limit 4 12 0.001 100 200
01A N1 Maximum % RPM 256 14 0.015 100 200
01A EPR Maximum 4 12 0.001 100 200
029 N1 Limit (TCC) % RPM 256 14 0.015 100 200
029 EPR Limit (TOC) 4 12 0.001 100 200
02F Maximum Available EPR 4 12 0.001 100 200
03B EPR Limit 4 12 0.001 150 250
03B N1 Limit % RPM 256 14 0.015 150 250
03F Maximum Available EPR 4 12 0.001 100 200
See Att. 6 for SDI
04D S/W REV-Tank (1) 16 N/A TBD TBD
encoding
10A Max Allowed Fan Speed % 117.5 13 0.032 100 500
10B Max Allowed Fan Speed % 117.5 13 0.032 100 500
140 Air Density Ratio Ratio 4 12 0.001 250 500

343 003 N1 Derate % RPM 256 14 0.015 100 200

003 EPR Rate 4 12 0.001 100 200
01A N1 Demand % RPM 256 12 0.063 20 50
10A N1 Command vs. TLA % 117.5 13 0.032 31.3 100
10B N1 Command vs. TLA % 117.5 13 0.032 31.3 100

344 01A N2 % RPM 256 14 0.015 50 100

01C N2 % RPM 256 14 0.015 50 100
029 N2 % RPM 256 14 0.015 50 100
02F N2 % RPM 256 14 0.015 25 50
033 N2 % RPM 256 14 0.015 50 200
03F N2 % RPM 256 14 0.015 25 50
See ARINC 429,
0 4 D Fuel Discretes 50 100
Part 2
10A Selected Actual Core Speed % 128 12 0.063 31.3 100
10B Selected Actual Core Speed % 128 12 0.063 31.3 100
13A N2 Speed % RPM 256 14 0.015 25 50
0D0 N2 % RPM 256 13 0.03 SDI 1 = L/SDI 2 = R

345 01A Exhaust Gas Temperature Deg C 2048 12 0.5 100 200
01C Exhaust Gas Temperature Deg C 2048 12 0.5 100 200
029 Exhaust Gas Temperature Deg C 2048 12 0.5 50 100
02F Exhaust Gas Temperature Deg C 2048 12 0.5 25 50
033 Exhaust Gas Temperature Deg C 2048 12 0.5 100 200
03F Exhaust Gas Temperature Deg C 2048 12 0.5 25 50
04D Discretes Status 1&3 100 200 See ARINC 429P2
10A Selected Exhaust Gas Temp (Total) Deg C -55 - +1100 11 1.00 62.5 250
10B Selected Exhaust Gas Temp (Total) Deg C -55 - +1100 11 1.00 62.5 250
13A EGT Trimmed Deg C 2048 12 0.5 25 50
0D0 EGT Deg C 2048 12 0.5 SDI 1 = L/SDI 2 = R

346 003 N1 Actual % RPM 256 14 0.015 100 200

01A N1 Actual % RPM 256 14 0.015 100 200
02F N1 Actual % RPM 256 14 0.015 25 50
033 N1 Actual % RPM 256 14 0.015 50 200
03F N1 Actual % RPM 256 14 0.015 25 50
See Att. 6 for SDI
04D Cable Cap-Hi-Z PF 65535 15 2.0 100 200
encoding
 ARINC SPECIFICATION 429, PART 1 - Page 73
ATTACHMENT 2
DATA STANDARDS
TABLE 2 - BNR DATA

Min Max Max

Eqpt Transit Transit Trans-
Label ID Parameter Units Range Sig Pos Resolution Interval Interval port Notes
(Hex) Name (Scale) Bits Sense (msec) (msec) Delay
2 2 (msec)
3
10A Selected Actual Fan Speed % 128 12 0.063 31.3 100
10B Selected Actual Fan Speed % 128 12 0.063 31.3 100
13A N1 Speed Actual % N1Nom 256 14 0.015 25 50
0D0 N1 % RPM 256 13 0.03 SDI 1 = L/SDI 2 = R

347 029 Fuel Flow (Engine) Lbs/Hr 32768 12 8 50 100

10A LPT Clearance Valve Position % -5 - +105 11 0.063 500 1000
10B LPT Clearance Valve Position % -5 - +105 11 0.063 500 1000
13A Fuel Flow Lbs/Hr 32768 14 2 50 100
0D0 Fuel Flow Lbs/Hr 32768 12 8 SDI 1 = L/SDI 2 = R

353 0D0 Vibration Scalar 5.12 8 0.02 SDI 1 = L/SDI 2 = R

Bit 11-Chan. A
354 03D N1 Vibration Scalar 5.12 9 0.01
Bit 12-Chan. B
See ARINC 429P2
04D FQIS Tank ID 100 200
See Att. 6 for SDI

Bit 11-Chan. A
355 03D N2 Vibration Scalar 5.12 9 0.01
Bit 12-Chan. B

Bit 11-Chan. A
356 03D N2 Vibration Scalar 5.12 9 0.01
Bit 12-Chan. B

Bit 11-Chan. A
357 03D BB Vibration Scalar 5.12 9 0.01
Bit 12-Chan. B

360 002 Flight Information See Attachment 6

004 Potential Vertical Speed Ft/Min 32768 15 1.0 10 20
005 Potential Vertical Speed Ft/Min 32768 15 1.0 25 50
038 Potential Vertical Speed Ft/Min 32768 15 1.0 10 20
Bit 11-Chan. A
03D N1 Rotor Imbalance Angle Deg. ±180 9 1.0
Bit 12-Chan. B
056 Flight Information See Attachment 6
060 Flight Information See Attachment 6
10A Throttle Rate of Change Deg/Sec ±16 9/9 1.00 31.3 100 See Notes [6] & [7]
10B Throttle Rate of Change Deg/Sec ±16 9/9 1.00 31.3 100 See Notes [6] & [7]
142 RAIM Status Word N.M. 16 13 0.00195

361 004 Altitude (Inertial) Feet 131072 20 0.125 20 40

005 Altitude (Inertial) Feet 131072 18 0.5 20 40
038 Altitude (Inertial) Feet 131072 20 0.125 20 40
LPT Rotor Imbalance Angle (737 Bit 11-Chan. A
03D Deg. ±180 9 1.0
only) Bit 12-Chan. B
10A Derivative of Thrust vs. N1 DFN/%N1 2000 11 2.0 62.5 250 See Note [6]
10B Derivative of Thrust vs. N1 DFN/%N1 2000 11 2.0 62.5 250 See Note [6]

362 004 Along Track Horizontal Acceleration g 4 12 0.001 10 20

038 Along Track Horizontal Acceleration g 4 12 0.001 10 20
10A Derivative of N1 vs. TLA % N1/Deg 12 11 0.008 62.5 250 See Note [6]
10B Derivative of N1 vs. TLA % N1/Deg 12 11 0.008 62.5 250 See Note [6]
115 Range Rate Knots ±8192 13 1.0 50 50

363 004 Cross Track Acceleration g 4 12 0.001 10 20

038 Cross Track Acceleration g 4 12 0.001 10 20
10A Corrected Thrust LBF 64000 11 64.0 62.5 250 See Note [6]
10B Corrected Thrust LBF 64000 11 64.0 62.5 250 See Note [6]

364 004 Vertical Acceleration g 4 12 0.001 10 20

005 Vertical Acceleration g 4 12 0.001 10 20
 ARINC SPECIFICATION 429, PART 1 - Page 74
ATTACHMENT 2
DATA STANDARDS
TABLE 2 - BNR DATA

Min Max Max

Eqpt Transit Transit Trans-
Label ID Parameter Units Range Sig Pos Resolution Interval Interval port Notes
(Hex) Name (Scale) Bits Sense (msec) (msec) Delay
2 2 (msec)
3
13A N1 APR Rating % N1Nom 256 14 0.015 100 200
038 Vertical Acceleration g 4 12 0.001 10 20

365 004 Inertial Vertical Velocity (EFI) Ft/Min 32768 15 1.0 20 40

005 Inertial Vertical Velocity (EFI) Ft/Min 32768 15 1.0 20 40
13A N1 Max Reverse % N1Nom 256 14 0.015 100 200
038 Inertial Vertical Velocity (EFI) Ft/Min 32768 15 1.0 20 40

366 004 North-South Velocity Knots 4096 15 0.125 50 100

13A IGV Position Deg/180 ±180 12 0.05 100 200
038 North-South Velocity Knots 4096 15 0.125 50 100

367 004 East-West Velocity Knots 4096 15 0.125 100 200

13A IGV Request Deg/180 ±180 12 0.05 100 200
038 East-West Velocity Knots 4096 15 0.125 100 200

370 004 g 9 8 13 UP 0.001 100 200 110

005 g 9 8 13 UP 0.001 100 200 110
00B GNSS Height WGS-84 (HAE) Feet ± 131.072 20 0.125 1200
025 Decision Height Selected (EFI) Feet 8192 16 0.125 100 200
0C5 Decision Height Selected (EFI) Feet 16384 17 0.125 100 200

371 X X X Gen Aviation Equip. Identifier

372 005 Wind Direction-Magnetic Deg/180 ±180 9 0.35 50 100

10A Actual Fan Speed % 128 12 0.063 500 1000
10B Actual Fan Speed % 128 12 0.063 500 1000

373 005 North-South Velocity-Magnetic Knots 4096 15 0.125 100 200

10A Actual Core Speed % 128 12 0.063 500 1000
10B Actual Core Speed % 128 12 0.063 500 1000

374 005 East-West Velocity-Magnetic Knots 4096 15 0.125 100 200

10A Left Thrust Reverser Position % -5 - +105 11 0.063 500 1000
10B Left Thrust Reverser Position % -5 - +105 11 0.063 500 1000

375 004 Along Heading Acceleration Gs 4 18 1.53E-5 50 Hz 110 Hz

005 Along Heading Acceleration g 4 12 0.001 10 20
033 Spare DC1 VDC 16 12 0.004 150 250
038 Along Heading Acceleration Gs 4 18 1.53E-5 50 Hz 110 Hz
10A Right Thrust Reverser Position % -5 - +105 11 0.063 500 1000
10B Right Thrust Reverser Position % -5 - +105 11 0.063 500 1000
XXX GPS Differential Correction, Word A See ARINC 743

376 004 Cross Heading Acceleration Gs 4 18 1.53E-5 50 Hz 110 Hz

005 Cross Heading Acceleration g 4 12 0.001 10 20
033 Spare DC2 VDC 16 12 0.004 150 250
038 Cross Heading Acceleration Gs 4 18 1.53E-5 50 Hz 110 Hz
XXX GPS Differential Correction, Word B See ARINC 743
 ARINC SPECIFICATION 429, PART 1 - Page 75
ATTACHMENT 2
DATA STANDARDS
TABLE 2 - BNR DATA

[1] The number entered into the Range Column for each
parameter that is not angular in nature is the nearest
whole binary number greater than the parameter range
required. As explained in the Commentary following
Section 2.1.6 of this document, the weight of the most
significant bit of the twos complement fractional notation
binary word will be one half this value, and the actual
maximum value of the parameter capable of being
encoded will be the number in the range column less one
least significant bit value. The numbers entered in the
RANGE column for angular parameters are the actual
degree ranges required. The way in which these
parameters are encoded is also explained in the
Commentary following Section 2.1.6.

[2] Transmit intervals and the number of parameters to be

transmitted are prime factors in bus loading. The
interval for transmission of parameters should fall
between the minimum and maximum specified intervals
c-4 and nominally should be near the center of the range at
equal intervals between transmissions. When heavy bus
loading dictates a shift from the center of the range, the
shift should be toward the maximum transmit interval.

When words with like labels and with different SDI

codes are transmitted, each of those words is considered
a unique item of information. The guidance given in this
c-5 document for transmit intervals should be applied to
those words as if each word were identified by a
different label.

[3] Maximum transport delay is the worst case total delay

between an input function and the output response.

COMMENTARY

Since the nature of the data varies, the definition of

transport delay will differ depending on the
application. In the case of a sampling system, a
c-4 sample is complete when the 32-bit word
constituting the output data is complete. In the case
of a system involving filtering, transport delay is the
phase slope of the transfer function across the
frequency band of interest.

There can be situations in which it is necessary to define

which portions of an equipment are included in the
transport delay term. Such definitions should appear in
individual equipment Characteristics when needed.

[4] The values shown in parentheses are the preferred data

standards for stator vane angle. However, a considerable
portion of existing equipment use the other (non-
c-7 parenthesized) values. Users should verify the data
standards of the equipment they are or will be using.

[5] These labels can provide data in a degraded accuracy

mode. See Section 2.1.5.1 and 2.1.5.2.

[6] Optionally transmitted.

[7] Binary packed word consisting of:

c-12
Word 1 = Bits 11-19 (Range = 16)

Word 2 = Bits 20-28 (Range = 16)

ARINC SPECIFICATION 429, PART 1 - Page 76

ATTACHMENT 3

VOLTAGE LEVELS

A A
XMTR RCVR
B B
G G

+13
+11
+10
+9
+6.5 c-4
AC VOLTS

+2.5
V +0.5
AB
-0.5
-2.5

-6.5 c-4

-9
-10
-11
-13
HI NULL LO HI NULL LO
XMTR OUTPUT STATES RCVR INPUT STATES
 ARINC SPECIFICATION 429, PART 1 - Page 77

ATTACHMENT 4
INPUT/OUTPUT CIRCUIT STANDARDS

TRANSMITTING UNIT UTILIZATION DEVICE

OUTPUT ** **
+E /2 R s /2 CAPABILITY C R
o H H

R C
c-4 Eo I I

** C R
G
-E /2 R /2 ** G
o s TOTAL
SYSTEM **

OTHER DEVICES

OUTPUT (SYSTEM) UTILIZATION DEVICE

CAPABILITY STANDARDS

c-4 Total System *Resistance 400 to 8,000 ohms RI > 12,000 ohms

Total System *Capacitance 1,000 to 30,000 pF CI < 50 pF

System Capacitance Unbalance Not defined but unbalance due to RH or RG > 12,000 ohms
aircraft interwiring should be held
to a minimum CH and CG < 50 pF

The total differential input impedance of the receiver should be limited to the values specified in Section 2.2.4.2.

c-16 This drawing describes total system characteristics rather than individual component parameters.

NOTES:

* Includes aircraft interwiring

** Shields to be grounded in aircraft at both ends of all “breaks”.

ARINC SPECIFICATION 429, PART 1 - Page 78

ATTACHMENT 5
INTERNATIONAL STANDARDS ORGANIZATION CODE #5

The ISO Alphabet No. 5 seven-unit code set is reproduced in the table below with the BCD subset outlined in column 3:

STANDARD CODE

BIT 7 0 0 0 0 1 1 1 1
BIT 6 0 0 1 1 0 0 1 1
BIT 5 0 1 0 1 0 1 0 1
BIT BIT BIT BIT Column
4 3 2 1 0 1 2 3 4 5 6 7
Row

0 0 0 0 0 NUL DLE SP 0 @ P ! p

0 0 0 1 1 SOH DC1 ! 1 A Q a q

0 0 1 0 2 STX DC2 " 2 B R b r

0 0 1 1 3 ETX DC3 # 3 C S c s

0 1 0 0 4 EOT DC4 $ 4 D T d t

0 1 0 1 5 ENQ NAK % 5 E U e u

0 1 1 0 6 ACK SYN & 6 F V f v

0 1 1 1 7 BEL ETB ′ 7 G W g w

1 0 0 0 8 BS CAN ( 8 H X h x

1 0 0 1 9 HT EM ) 9 I Y i y

1 0 1 0 10 LF SUB * : J Z j z

1 0 1 1 11 VT ESC + ; K [ k {

1 1 0 0 12 FF FS ´ < L \ l 

1 1 0 1 13 CR GS - = M ] m }

1 1 1 0 14 SO RS • > N ∧ n ~

1 1 1 1 15 SI US / ? O  o DEL

NOTE: b8 is used as a parity bit.

 ARINC SPECIFICATION 429, PART 1 - Page 79

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLE

6.1. General Word Formats

TABLE 6-1
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P SSM DATA PAD DISCRETES SDI LABEL
[5] [4] MSB [3] [2] LSB [1]

Generalized BCD Word Format

TABLE 6-1-1
P SSM BCD CH #2 BCD CH #2 BCD CH #3 BCD CH #4 BCD CH #5 SDI 8 7 6 5 4 3 2 1
4 2 1 8 4 2 1 8 4 2 1 8 4 2 1 8 4 2 1
0 0 0 0 1 0 0 1 0 1 0 1 1 1 1 0 0 0 0 1 1 0 0 0 1 0 0 0 0 0 0 1
Example 2 5 7 8 6 DME DISTANCE (201)

BCD Word Format Example (No Discretes)

TABLE 6-2
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P SSM DATA PAD DISCRETES SDI LABEL
[5] [4] MSB [3] [2] LSB [1]

Generalized BNR Word Format

TABLE 6-2-1
31 30 29 11 8 7 6 5 4 3 2 1
P SSM PAD SDI LABEL
1/2 1/4 1/8 1/16 1/32 1/64 1/128 etc
0 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 1 1 1 1
Example: 512 Knots (i.e., 1/8 x 4096 where 4096 is entry in range column of Table 2, Att. 2) N-S VELOCITY (366)

BNR Word Format Example (No Discretes)

TABLE 6-3
P SSM “STX” UNIT WORD COUNT LABEL
(01) ADDRESS (357)
32 31 30 29 23 22 17 16 BNR EQUIV. 9 8 1

Alpha Numeric (ISO Alphabet No. 5) Message – Initial Word Format

P SSM “STX” SPARES WORD COUNT LABEL

(01) (Zeroes) (356)
32 31 30 29 23 22 17 16 BNR EQUIV. 9 8 1

Alpha Numeric (ISO Alphabet No. 5) Maintenance Data –Initial Word Format
c-4
P SSM “DATA CH #3” DATA CH #2 DATA CH #1 LABEL
(00) (356, 357)
32 31 30 29 P 23 22 L 16 15 A 9 8 1

Alpha Numeric (ISO Alphabet No. 5) Data – Intermediate Word Format

P SSM “DATA CH #3” DATA CH #2 DATA CH #1 LABEL

(10) (356, 357)
32 31 30 29 (BNR ZEROES) 23 22 A 16 15 H 9 8 1

Alpha Numeric (ISO Alphabet No. 5) Data – Final Word Format

(Taken together, the following example shows encoding of the word ALPHA into three successive data words).
ARINC SPECIFICATION 429, PART 1 - Page 80

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLES

TABLE 6-4
P SSM DISCRETES SDI LABEL
(00) (See Below)
32 31 30 29 MSB [2] LSB 11 10 9 8 1

LABEL USAGE SUBGROUP

155 – 161 Maintenance

270 – 276 Discretes
350 – 354 Maintenance c-4

Discrete Word Format

TABLE 6-5
P SSM ACKNOWLEDGEMENT WORD COUNT LABEL
(01) (FORMAT NOT DEFINED) (355)
32 31 30 29 17 16 BNR EQUIV. 9 8 1

Acknowledgement Word – Initial Word Format

TABLE 6-5-1
P SSM ACKNOWLEDGEMENT LABEL
(00) (FORMAT NOT DEFINED) (355)
32 31 30 29 9 8 1

Acknowledgement Word – Intermediate Word Format

TABLE 6-5-2
P SSM ACKNOWLEDGEMENT LABEL
(10) (FORMAT NOT DEFINED) (355)
32 31 30 29 9 8 1

Acknowledgement Word – Final Word Format

TABLE 6-6
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P SSM DATA PADS * SDI LABEL
[5] [4] [3] [1] (173/174)
* Bit No. 11 takes on the binary state “one” to annunciate that the ILS receiver is in the “tune inhibit” condition.

ILS Localizer/Glideslope Deviation Word

TABLE 6-7
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P SSM DATA FIELD ** * SDI LABEL
[5] [4] [1] (202) c-6
* Bit No. 11 is assigned to a memory on/off annunciation function (see Section 4.7 of ARINC 709)
** Bit No. 12 is set to “1” when data is for a foreground station in frequency scanning mode. 0 1 0 0 0 0 0 1

DME Distance Word

TABLE 6-8
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P SSM DATE
A FLIGHT PAD SDI LABEL
R Day Month
LEG [3] [1] (260)
I x10 x1 x10 x1
T 2 1 8 4 2 1 1 8 4 2 1 8 4 2 1
Y 0 0 1 0 0 0 1 1 0 1 0 0 0 0 1 0 1 0 0 0 0 0 0 0 0 0 0 1 1 0 1
Example 2 3 0 8 5 0 6 2

Date/Flight Leg Word

 ARINC SPECIFICATION 429, PART 1 - Page 81

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLE

TABLE 6-9
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P SSM FLIGHT NUMBER
A LABEL
R x1000 x100 x10 x1 PAD SDI
(261)
I 8 4 2 1 8 4 2 1 8 4 2 1 8 4 2 1
T 0 0 0 0 0 0 0 0 0 1 0 0 0 1 0 1 1 1 0 0 0 0 0 1 0 0 0 1 1 0 1
Y
Example 0 1 1 7 1 6 2

Flight Number Word

TABLE 6-10
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P SSM PAD SDI LABEL
MSB DATA LSB
[5] [4] [3] [6] [1] (222)

[6] Marker Beacon Output Discrete Bits

Bit State
Discrete Bit
Discrete Grounded Discrete Open
400 Hz 11 1 0
1300 Hz 12 1 0
3000 Hz 13 1 0

VOR Omnibearing

TABLE 6-11
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P SSM LEVER SDI LABEL
MSB DATA LSB PAD
[5] [4] POSITION [1] (127/137)

Bit
Lever
11 12 13 14 15
c-4 Position 1 (Cruise) 1 0 0 0 0
Position 2 0 1 0 0 0
Position 3 0 0 1 0 0
Position 4 0 0 0 1 0
Position 5 (Landing) 0 0 0 0 1

Slat/Flap Angle Word

TABLE 6-12
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P SSM HOURS MINUTES SECONDS LABEL
* SDI
[5] [4] 0-24 0-60 0-60 (150)
c-16 *Bit 11 of label 150 should be encoded with a “1” when the GNSS system clock is being used as the source of time.
Otherwise, bit 11 should be encoded as “0”.

UTC Binary Word

TABLE 6-13
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P SSM SDI LABEL
[5] [4] DATA PAD FTI [1] (164)
c-4 0 0 1 0 1 1 1 0
Note: When Bit 11 (Functional Test Inhibit) is a “1”, a functional test should not be performed. 4 6 1

Radio Height Word

ARINC SPECIFICATION 429, PART 1 - Page 82

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLES

TABLE 6-14
32 31 30 29 28 27 26 25 24 23 22 21 20 1 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P SSM DOCUMENTARY DATA PAD SDI LABEL
4 2 1 4 2 1 4 2 1 4 2 1 4 2 1 4 2 1 (262)
[5] [4] Code 1 Code 2 Code 3 Code 4 Code 5 Code 6 [1] 0 1 0 0 1 1 0 1

Documentary Data Word

[1] Source/Destination Identifier (SDI) Field

The purpose of the SDI field is explained in Section 2.1.4 of this document, as are also the limitations on its use.
When the SDI function is not required, this field may be occupied by binary zero or valid data pad bits.

[2] Discretes

As discussed in Section 2.3.1.2 of this document, unused bits in a word may be assigned to discrete functions, one
bit per variable. Bit #11 of the word should be the first to be so assigned, followed by bit #12 and so on, in
ascending numerical order, until the data field is reached. In the absence of discretes, unused bit positions should
be occupied by binary zero or valid data pad bits.

[3] Pad

All bit positions not used for data or discrete should be filled with binary zero or valid data pad bits. Section 2.1.2
of this document refers.

[4] Sign/Status Matrix (SSM)

Section 2.1.5 of this document describes the functions of the sign/status matrix and the ways in which the bits
constituting it are encoded.

[5] Parity Bit

This bit is encoded to render word parity odd. Section 2.3.4 of this document refers.
 ARINC SPECIFICATION 429, PART 1 - Page 83

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLE

TABLE 6-15
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P SSM PAD 3rd Digit 2nd Digit LSD PAD SDI LABEL (046)
1 0 0 0 0 0 0 1 1 0 0 1 0 0 1 0 0 1 0 0 0 0 0 0 0 1 1 0 0 1 0 0
Example 6 4 9 6 4 0

Engine Serial Number (3LDs)

TABLE 6-16
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
th th
P SSM PAD MSD 5 Digit 4 Digit PAD SDI LABEL (047)
0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 1 0 0 0 0 0 0 0 1 1 1 0 0 1 0 0
Example 0 3 2 7 4 0

Engine Serial Number (3 MSDs)

TABLE 6-17
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P SSM SPARE MSD LSD SDI LABEL (377)
1 1 1 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 1 1 0 1 0 0 1 1 1 1 1 1 1 1
c-11
1 0 D 7 7 3

Equipment Identifier Word

(Example provided for 10D code)
ARINC SPECIFICATION 429, PART 1 - Page 84

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLES

TABLE 6-18
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P SSM DATE SDI LABEL
A Day Month Year (260 031)
R x10 x1 x10 x1 x10 x1 Chronometer
I 2 1 8 4 2 1 1 8 4 2 1 8 4 2 1 8 4 2 1 Output Only
T 0 0 1 0 0 0 1 1 0 1 0 0 0 1 0 0 0 0 1 0 1 0 0 0 0 0 0 1 1 0 1
Y
Example 2 3 0 8 8 5 0 6 2

TABLE 6-19
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P SSM D PRIMARY COUNTER 0-4096 FLIGHT LEGS 4096-65535 PAD SDI LABEL
(00) LEGS (251 01A)
MSB LSB MSB LSB Electronic Supervisory Control

Flight Leg Counter

TABLE 6-20
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P SSM ALTITUDE SEE SDI LABEL
(00) MSB LSB BELOW (206 018)
Transponder

Bits
Range Bits Used App. Resolution
13 12 11
0 0 0 65536 15 4
0 0 1 65536 14 8
0 1 0 65536 13 16
0 1 1 51200 12 25
1 0 0 81920 14 10
1 0 1 51200 10 100

Altitude (Variable Reduction)

 ARINC SPECIFICATION 429, PART 1 - Page 85

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLE

TCAS INTRUDER RANGE WORD

TABLE 6-21
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P SSM INTRUDER RANGE INTRUDER INTRUDER SDI LABEL
[5] [3] [4] SENSE LVL[2] NUMBER [1] (130)
0 1 1 0 0 0 0 1 0 1 0 1 0 0 0 1 0 0 0 1 0 1 0 0 0 0 0 1 1 0 1 0
MSB LSB MSB LSB MSB LSB LSB MSB
5.25 NM 2 5 0 3 1

Note 1: Maximum number of intruders is 31.

Note 2: Intruder Sensitivity Level Status

Bits Meaning
18 17 16
0 0 0 Not Reported
0 0 1 SL = 1
0 1 0 SL = 2
0 1 1 SL = 3
1 0 0 SL = 4
1 0 1 SL = 5
1 1 0 SL = 6
1 1 1 SL = 7

Note 3: Maximum range is 127-15/16 nautical miles.

Note 4: Intruder range may be reported in the form of horizontal range when intruder is available.
Note 5: Sign Status Matrix (SSM) [BNR]

Bits Meaning
31 30
0 0 Failure Warning
0 1 No Computed Data
1 0 Functional Data
1 1 Normal Operation
ARINC SPECIFICATION 429, PART 1 - Page 86

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLES

TCAS INTRUDER ALTITUDE WORD

TABLE 6-22
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P SSM RELATIVE ALTITUDE I.V.S. FUTURE INTRUDER SDI LABEL
[5] [4] [3] [2] SPARE NUMBER [1] (131)
0 1 1 0 0 0 1 1 0 0 1 0 0 0 0 0 0 0 0 1 0 1 0 0 1 0 0 1 1 0 1 0
S MSB LSB MSB LSB LSB MSB
2500 FT LEVEL 5 1 3 1

Note 1: Maximum number of intruders is 31.

Note 2: Sense of Intruders VERTICAL RATE (Z SINT)

Bits Meaning
21 20
0 0 No Vertical Rate (Level Flight)
0 1 Climbing
1 0 Descending
1 1 No Data

Note 3: Binary, Two’s Complement Range = +/- 12700 Ft.

Note 4: The No Computed Data Report of the SSM field applies to relative altitude (Bits 29-22) only. See Note 5.

Note 5: Sign Status Matrix (SSM) [BNR]

Bits Meaning
31 30
0 0 Failure Warning
0 1 No Computed Data
1 0 Functional Data
1 1 Normal Operation
 ARINC SPECIFICATION 429, PART 1 - Page 87

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLE

TCAS INTRUDER BEARING WORD

TABLE 6-23

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P SSM BEARING DISPLAY INTRUDER SDI LABEL
MATRIX NUMBER
[5] [4] [3] [2] [1] (132)
1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 0 1 1 0 1 0
S MSB LSB MSB LSB MSB LSB LSB MSB
NO
0 THREAT 1 2 3 1

Note 1: Maximum number of intruders is 31.

Note 2: Display Matrix

Bits Meaning
18 17 16
0 0 0 No Threat
0 0 1 Traffic Advisory
0 1 0 Resolution Advisory
0 1 1 Proximate Traffic
1 0 0 Not Used
1 0 1 Not Used
1 1 0 Not Used
1 1 1 Not Used

Note 3: Binary, Fractional Binary;

Range = -180 to +180 Degrees

Note 4: The No Computed Data report in the SSM field applies to bearing information (Bits 29-19) only. See Note 5.

Note 5: Sign Status Matrix (SSM) [BNR]

Bits Meaning
31 30
0 0 Failure Warning
0 1 No Computed Data
1 0 Functional Data
1 1 Normal Operation
ARINC SPECIFICATION 429, PART 1 - Page 88

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLES

TRANSPONDER ALTITUDE/TCAS OWN AIRCRAFT ALTITUDE

TABLE 6-24

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P SSM S ALTITUDE ALT PAD LABEL
[2] [1] (203)

0 1 1 0 0 0 1 0 1 0 0 1 0 0 1 0 0 0 0 1 1 0 0 0 1 1 0 0 0 0 0 1
MSB LSB LSB MSB
21059 1 3 0 2

S = Sign Bit see Section 2.1.5.2 of this Document.

Note 1: Altitude Resolution

Bits Meaning
11
0 1 Ft
1 100 Ft

Note 2: Sign Status Matrix (SSM) [BNR]

Bits Meaning
31 30
0 0 Failure Warning
0 1 No Computed Data
1 0 Functional Data
1 1 Normal Operation
 ARINC SPECIFICATION 429, PART 1 - Page 89

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLE

2. Encoding Examples
Table 6-25 BCD DATA ENCODING EXAMPLES

Bit No. 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
SSM DATA FIELD [1] SDI LABEL
PARAMETER (Label) MSC LSC
4 2 1 8 4 2 1 8 4 2 1 8 4 2 1 8 4 2 1 1 2 4 1 2 4 1 2
Distance To Go (001) 1 0 0 0 1 0 0 1 1 1 0 1 0 1 0 0 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 0
+2750.4 NM
Time To Go (002) 0 0 0 0 0 1 0 1 0 0 0 1 0 1 0 0 1 1 P P P P 0 0 0 1 0 0 0 0 0 0
+145.3 Min.
Cross Track Distance (003) 1 0 0 0 1 0 0 0 1 0 0 1 0 1 0 1 1 0 P P P P 0 0 1 1 0 0 0 0 0 0
225.6 NM
Ground Speed (012) 1 0 0 0 0 0 0 1 1 0 0 1 0 1 0 0 0 0 P P P P 0 0 0 1 01 0 0 0 0
650 Knots
Track Angle (True) (013) 1 0 0 0 0 1 0 1 1 0 0 1 0 1 0 1 0 1 P P P P 0 0 1 1 0 1 0 0 0 0
165.5 Deg.
Selected Vertical Speed (020) 0 1 1 0 1 0 0 0 1 0 0 0 0 0 0 0 0 0 P P P P 0 0 0 0 0 0 1 0 0 0
-2200 Ft/Min
Selected EPR (021) 0 0 0 0 1 0 0 0 0 0 0 1 0 1 P P P P P P P P 0 0 1 0 0 0 1 0 0 0
2.05
Selected N1 (021) 1 0 0 0 1 0 0 1 1 1 0 1 0 1 0 0 0 0 P P P P 0 0 1 0 0 0 1 0 0 0
2750 RPM
Selected Mach (022) 0 0 0 0 0 0 1 0 0 0 0 1 0 1 0 0 0 0 P P P P 0 0 0 1 0 0 1 0 0 0
0.850 Mach
Selected Heading (023) 1 0 0 0 0 1 0 1 1 1 0 1 1 1 P P P P P P P P 0 0 1 1 0 0 1 0 0 0
177 Deg.
Selected Course (024) 1 0 0 0 1 0 0 1 0 1 0 1 0 0 P P P P P P P P 0 0 0 1 0 1 0 0 0
154 Deg.
Selected Altitude (025) 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 1 0 0 0
41000 Ft.
Selected Airspeed (026) 0 0 0 1 0 0 0 0 1 0 0 0 1 1 P P P P P P P P 0 0 0 1 1 0 1 0 0 0
423 Knots
Universal Time Constant (125) 1 0 0 0 0 1 0 1 0 1 0 1 0 0 0 1 0 1 0 1 0 1 0 0 1 0 1 0 1 0 1 0
1545.5 Hr.
Radio Height (165) 0 0 0 0 1 0 0 1 0 0 0 1 0 1 0 0 0 0 0 1 0 1 0 0 1 0 1 0 1 1 1 0
2450.5 Ft.
Decision Height Selected (170) 0 0 0 0 1 0 0 0 0 0 0 0 0 0 P P P P P P P P 0 0 0 0 0 1 1 1 1 0
200 Ft.
DME Distance (201) 0 0 0 0 1 0 0 1 0 1 0 1 1 1 1 0 0 0 0 1 1 0 0 0 1 0 0 0 0 0 0 1
257.86 NM
True Airspeed (230) 0 0 0 1 0 1 0 1 1 0 0 1 0 1 P P P P P P P P 0 0 0 0 0 1 1 0 0 1
565 Knots
Total Air Temp. (231) 0 1 1 0 0 0 0 0 1 0 0 1 0 1 P P P P P P P P 0 0 1 0 0 1 1 0 0 1
-025 Deg. C [2]
Altitude Rate (232) 1 1 1 0 0 1 0 1 0 1 0 0 1 0 0 1 0 1 0 0 0 0 0 0 0 1 0 1 1 0 0 1
-15250 Ft/Min
Static Air Temp. (233) 1 0 0 0 0 0 0 0 0 1 0 0 1 1 P P P P P P P P 0 0 1 1 0 1 1 0 0 1
+013 Deg. C [2]
Baroset (ins Hg) (235) 0 0 0 0 1 0 1 0 0 1 1 0 0 1 0 0 1 0 P P P P 0 0 1 0 1 1 1 0 0 1
29.92 ins Hg

NOTES:
[1] “P” denotes pad “zero” or valid data, see Section 2.1.2. Note possible use of pad bits for discrete functions per
Section 2.3.1.2.
[2] Because of the actual maximum value of the most significant character of these quantities exceeds 7, it cannot
be encoded in the most significant character position of the BCD word. For this reason, each quantity has
been given an “artificial” MSC of zero and its actual MSC encoded in the next most significant character
position of the word.
ARINC SPECIFICATION 429, PART 1 - Page 90

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLES

Table 6-25-1 BCD ENCODING OF LATITUDE AND LONGITUDE

Bit No. 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
DATA FIELD
SSM LABEL
PARAMETER (Label)
MSC LSC
1 8 4 2 1 8 4 2 1 8 4 2 1 8 4 2 1 8 4 2 1 1 2 4 1 2 4 1 2
Present Position (Lat.)
N 75 Deg 59.9' (010) 1 0 0 0 0 1 1 1 0 1 0 1 0 1 0 1 1 0 0 1 1 0 0 1 0 0 0 1 0 0 0 0
Present Position (Long) c-4
W 169 Deg 25.8' (011) 0 1 1 1 0 1 1 0 1 0 0 1 0 0 1 0 0 1 0 1 1 0 0 0 1 0 0 1 0 0 0 0

(See Commentary following Section 2.1.2 of this document for further information.)
 ARINC SPECIFICATION 429, PART 1 - Page 91

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLE

TABLE 6-26
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 Bit Nos.

MSB

LSB

THRESHOLD LOW

SYSTEM FAULT
WHEEL FAULT
DATA REF.
Wheel Nos.

DIFF. LOW
SPARES LABEL ARINC
747 DC-10
PARITY

OCT.

WHEEL
LABEL
SPARE
SPARE
BCD
BNR

512
256
128
64
32
16
8
4
2
1
1 1 1 0 0 0 1 0 1 1 0 0 1 0 115

2 2 1 0 0 1 1 0 1 1 0 0 1 0 115

13 3 1 0 0 0 1 1 1 1 0 0 1 0 117

14 4 1 0 0 1 1 1 1 1 0 0 1 0 117

3 5 1 0 1 0 1 0 1 1 0 0 1 0 115

4 6 1 0 1 1 1 0 1 1 0 0 1 0 115

15 7 1 0 1 0 1 1 1 1 0 0 1 0 117

16 8 1 0 1 1 1 1 1 1 0 0 1 0 117

5 9 1 0 0 0 0 0 1 1 0 0 1 0 114

9 10 1 0 0 0 0 1 1 1 0 0 1 0 116

6 1 0 0 1 0 0 1 1 0 0 1 0 114

7 1 0 1 0 0 0 1 1 0 0 1 0 114

8 1 0 1 1 0 0 1 1 0 0 1 0 114

10 1 0 0 1 0 1 1 1 0 0 1 0 116

11 1 0 1 0 0 1 1 1 0 0 1 0 116

12 1 0 1 1 0 1 1 1 0 0 1 0 116

BITS

10 9

747 DC-10
NOSE (064) NOSE (064)
NL NR NL NR

LO (061) 00 01 RO (063) LO (061) 00 RO (063)

1 2 13 14 1 2 3 4

00 01 00 01 00 01 00 01
3 4 15 16 5 6 7 8

10 11 LI (060) RI (062) 10 11 10 11 LI (060) RI (062) 1 0 11

5 6 9 10 9 10

00 01 00 01 00 00
7 8 11 12

10 11 10 11 01 01
ARINC SPECIFICATION 429, PART 1 - Page 92

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLES

TABLE 6-26-1
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 Bit Nos.

BRAKE FAULT
MSB

LSB

DIFF.TEMP.
REF.
Wheel Nos.

PREDICT

SYSTEM
SPARES LABEL ARINC
PARITY
DATA

WHEEL
LABEL
WARM
747 DC-10
BCD OCT.
BNR

HOT
512
256
128
64
32
16
8
4
2
1
1 1 1 0 0 0 1 0 1 1 0 0 0 0 115

2 2 1 0 0 1 1 0 1 1 0 0 1 0 115

13 3 1 0 0 0 1 1 1 1 0 0 1 0 117

14 4 1 0 0 1 1 1 1 1 0 0 1 0 117

3 5 1 0 1 0 1 0 1 1 0 0 1 0 115

4 6 1 0 1 1 1 0 1 1 0 0 1 0 115

15 7 1 0 1 0 1 1 1 1 0 0 1 0 117

16 8 1 0 1 1 1 1 1 1 0 0 1 0 117

5 9 1 0 0 0 0 0 1 1 0 0 1 0 114

9 10 1 0 0 0 0 1 1 1 0 0 1 0 116

6 1 0 0 1 0 0 1 1 0 0 1 0 114

7 1 0 1 0 0 0 1 1 0 0 1 0 114

8 1 0 1 1 0 0 1 1 0 0 1 0 114

10 1 0 0 1 0 1 1 1 0 0 1 0 116

11 1 0 1 0 0 1 1 1 0 0 1 0 116

12 1 0 1 1 0 1 1 1 0 0 1 0 116

BITS
10 9

747

LO (115) RO (117) LO (115) RO (117)

1 2 13 14 1 2 3 4

00 01 00 01 00 01 00 01
3 4 15 16 5 6 7 8

10 11 LI (114) RI (116) 10 11 10 11 LI (114) RI (116) 1 0 11

5 6 9 10 9 10

00 01 00 01 00 00
7 8 11 12

10 11 10 11 01 01
 ARINC SPECIFICATION 429, PART 1 - Page 93

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLE

Table 6-27 BNR DATA ENCODING EXAMPLES

Bit No. 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
LABEL
PARAMETER (Label) P SSM DATA FIELD [1] SDI
1 2 4 1 2 4 1 2
Selected Course (100) 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 P P P P P P 0 0 0 0 0 0 0 0 1 0
0 Deg. [3]
Selected Heading (101) 0 1 1 0 1 1 0 1 0 1 0 1 0 1 0 1 P P P P P P 0 0 1 0 0 0 0 0 1 0
150 Deg. [3]
Selected Altitude (102) 1 1 1 0 1 0 1 0 0 0 0 0 0 0 1 0 1 0 0 0 P P 0 0 0 1 0 0 0 0 1 0
41000 Ft.
Selected Airspeed (103) 0 1 1 0 1 1 0 1 0 0 1 1 1 0 0 P P P P P P P 0 0 1 1 0 0 0 0 1 0
423.0 Knots
Selected Vertical Speed (104) 1 1 1 1 1 1 0 1 1 1 0 1 1 0 P P P P P P P P 0 0 0 01 0 0 0 1 0
-2200 Ft/Min [2]
Selected Mach (106) 1 1 1 0 0 0 1 1 0 0 1 0 0 0 0 0 P P P P P P 0 0 0 1 1 0 0 0 1 0
800 m Mach
Desired Track (114) 0 1 1 1 1 0 0 0 0 1 1 1 0 0 1 0 P P P P P P 0 0 0 0 1 1 0 0 1 0
275 Deg. [3]
Cross Track Distance (116) 1 1 1 0 0 1 1 0 0 1 1 0 0 0 0 0 0 0 0 P P P 0 0 0 1 1 1 0 0 1 0
51.0 NM
Vertical Deviation (117) 0 1 1 0 0 1 0 0 1 0 1 1 0 0 0 P P P P P P P 0 0 1 1 1 1 0 0 1 0
600 Ft.
Flight Director Roll (140) 1 1 1 0 0 0 1 0 1 0 1 0 1 0 1 1 P P P P P P 0 0 0 0 0 0 0 1 1 0
+30 Deg.
Flight Director Pitch (141) 1 1 1 1 1 1 1 1 0 0 0 1 1 1 0 0 P P P P P P 0 0 1 0 0 0 0 1 1 0
-10 Deg. [2]
Fast/Slow (142) 0 1 1 0 0 1 1 1 1 0 0 0 0 0 0 0 P P P P P P 0 0 0 1 0 0 0 1 1 0
+15 Knots
UTC (150) 0 1 1 0 1 0 0 1 0 1 1 1 0 0 1 0 1 0 1 0 0 0 0 0 0 0 0 1 0 1 1 0
(18:57:20)
Radio Height (164) 0 1 1 0 0 1 0 0 1 1 0 0 1 0 0 1 0 0 0 0 P 0 0 0 0 0 1 0 1 1 1 0
2450 Ft.
Localizer Deviation (173) 1 1 1 0 0 0 0 0 1 1 0 1 1 0 0 0 P P P P P P 0 0 1 1 0 1 1 1 1 0
+0.021 DDM
Glide Slope Deviation (174) 1 1 1 1 1 1 0 1 1 0 0 0 0 0 0 0 P P P P P P 0 0 0 0 1 1 1 1 1 0
-0.125 DDM [2]
DME Distance (202) 0 1 1 0 1 0 0 0 0 0 0 0 1 1 1 0 1 1 1 0 P 0 0 0 0 1 0 0 0 0 0 1
257.86 NM
Altitude (29.92) (203) 0 1 1 0 0 1 0 1 0 1 1 1 1 1 1 0 0 1 0 0 0 P 0 0 1 1 0 0 0 0 0 1
45000 Ft.
Mach (205) 0 1 1 0 0 0 1 1 0 1 0 0 0 0 0 0 1 0 0 0 P P 0 0 1 0 1 0 0 0 0 1
0.8325 Mach
Computed Airspeed (206) 1 1 1 0 0 1 1 0 1 0 1 0 0 1 0 0 0 0 P P P P 0 0 0 1 1 0 0 0 0 1
425 Knots
True Airspeed (210) 0 1 1 0 0 1 0 0 0 1 1 0 1 0 1 0 0 0 0 P P P 0 0 0 0 0 1 0 0 0 1
565 Knots
Static Air Temp (213) 0 1 1 0 0 0 0 0 0 1 1 0 1 0 0 P P P P P P P 0 0 1 1 0 1 0 0 0 1
+13 Deg. C
Total Air Temp (211) 0 1 1 1 1 1 1 1 0 0 1 1 1 0 0 P P P P P P P 0 0 1 0 0 1 0 0 0 1
-25 Deg. C [2]
Altitude Rate (212) 0 1 1 1 1 0 0 0 1 0 0 0 1 1 1 P P P P P P P 0 0 0 10 1 0 0 0 1
-15250 Ft/Min [2]
Present Pos. Lat. (310) 1 1 1 0 0 1 1 1 0 0 1 1 1 1 1 0 1 0 1 0 1 0 0 0 0 0 0 1 0 0 1 1
N 81.5 Deg
Present Pos. Long. (311) 0 1 1 1 0 1 1 1 0 0 0 1 0 1 1 0 1 1 0 0 0 0 0 0 1 0 0 1 0 0 1 1
W 100.25
Ground Speed (312) 1 1 1 0 0 0 1 0 1 0 0 0 1 0 1 0 0 0 0 P P P 0 0 0 1 0 1 0 0 1 1
650 Knots
Flight Path Accel (323) 0 1 1 0 1 0 1 0 0 0 0 0 0 1 0 1 0 0 P P P P 0 0 1 1 0 0 1 0 1 1
+2.50 g

NOTES:

[1] “P” denotes pad “zero” or valid data, see Section 2.1.2. Note possible use of pad bits for discrete functions per
Section 2.3.1.2.

[2] Negative values are encoded as the two’s complements of positive values and the negative sign is annunciated
in the sign/status matrix.

[3] Angles in the range 0 to 180o are encoded as positive numbers. Angles in the range 180o to 360o are subtracted
from 360o and the resulting number encoded as a negative value per note 2. Arc minutes and seconds are
encoded as decimal degrees.
ARINC SPECIFICATION 429, PART 1 - Page 94

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLES

TABLE 6-28

AVM Command Word – Label 227 03D

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

P Command/Control Bits AVM Hex (Equipment) ID = 03D Hex PADS SDI Label (227)

0 0 0 0 0 0 1 1 1 1 0 1 1 1 1 0 1 0 0 1

Bits Meaning
10 9
0 0 Engine 4 (or All Call) {not used on 757}
0 1 Engine 1 (or Engine 1 and 2)
1 0 Engine 2
1 1 Engine 3 (or Engine 3 and 4)

Bits Parameter
31 30 29 28 27 26 25
0 0 0 0 0 0 0 Not Used
0 0 0 0 0 0 1 Unit Self Test
0 0 0 0 0 1 0 Use Accelerometer A**
0 0 0 0 0 1 1 Use Accelerometer B**
0 0 0 0 1 0 0 PAD
0 0 0 0 1 0 1 Erase Fault History
0 0 0 0 1 1 0 Erase Flight History*
0 0 0 0 1 1 1 Read Fault History
0 0 0 1 0 0 0 Read Flight History*
0 0 1 0 0 1 0 Reserved*

* 737 Only
** 757 Only
 ARINC SPECIFICATION 429, PART 1 - Page 95

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLE

ACMS INFORMATION

ORIGIN AND DESTINATION

TABLE 6-29
Label 061 002

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

ORIGIN ORIGIN ORIGIN OCTAL LABEL

P SSM
CHAR #3 CHAR #2 CHAR #1 061

Label 062 002

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

DESTINATION ISO #5 CHAR ORIGIN OCTAL LABEL

P SSM
CHAR #1 “SPACE” CHAR #4 062

Label 063 002

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

DESTINATION DESTINATION DESTINATION OCTAL LABEL

P SSM
CHAR #4 CHAR #3 CHAR #2 063

NOTE: All characters are expressed in ISO #5 format, as defined in ARINC Specification 429.
ARINC SPECIFICATION 429, PART 1 - Page 96

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLES

TABLE 6-30

TACAN Control - Label 145 002

RANGE 126
RESOLUTION 1.0
RATE 5Hz +/-10%

Bit No. Description

1 0
2 1 1
3 1
4 0 4
5 0
6 1
7 0 5
8 1
9-10 SDI
11-13 Pad Zero
14 VOR/TAC Select (TAC=1, VOR=0)
15 TACAN Select (TAC 1=1, TAC 2=0)
16 Pad Zero
17-20 BCD Units Chan Cont (LSB=17)
21-24 Hex Tens Chan Cont (LSB=24)
25 Pad Zero
26 X/Y Mode (X=1, Y=0)
27-28 Mode Cont (see Table A)
29 Pad Zero
30-31 SSM (see Table B)
32 Parity (Odd)

Table A – Mode Control Table B – SSM

Bits Description Bits Description

27 28 30 31
0 0 REC 0 0 Valid
0 1 A/A REC 0 1 Functional Test
1 0 T/R 1 0 No Computed Data
1 1 A/A T/R 1 1 Not Used
 ARINC SPECIFICATION 429, PART 1 - Page 97

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLE

ACMS INFORMATION FLIGHT NUMBER

TABLE 6-31
Label 233 EQ ID 002 MSB LSB MSB LSB
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
PAD PAD OCTAL LABEL
P SSM CHAR #2 CHAR #1 SDI
ZERO ZERO 233

Label 234 EQ ID 002

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
PAD PAD OCTAL LABEL
P SSM CHAR #4 CHAR #3 SDI
ZERO ZERO 234

Label 235 EQ ID 002

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
PAD PAD OCTAL LABEL
P SSM CHAR #6 CHAR #5 SDI
ZERO ZERO 235

Label 236 EQ ID 002

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
PAD PAD OCTAL LABEL
P SSM CHAR #8 CHAR #7 SDI
ZERO ZERO 236
Sign Matrix for BNR
Bit
Meaning
31 30
0 0 Failure Warning
c-16 0 1 No Computed data
1 0 Functional Test
1 1 Normal Operation
………………………………………………………………………………………………………………………………..
TABLE 6-32
Label 233 EQ ID 018 MSB LSB MSB LSB
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
PAD PAD OCTAL LABEL
P SSM CHAR #2 CHAR #1 SDI
ZERO ZERO 233
Label 234 EQ ID 018
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
PAD PAD OCTAL LABEL
P SSM CHAR #4 CHAR #3 SDI
ZERO ZERO 234
Label 235 EQ ID 018
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
PAD PAD OCTAL LABEL
P SSM CHAR #6 CHAR #5 SDI
ZERO ZERO 235
Label 236 EQ ID 018
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
PAD PAD OCTAL LABEL
P SSM CHAR #8 CHAR #7 SDI
ZERO ZERO 236
Sign Matrix for BCD
NOTE: The following information is provided in order to clarify the Bit
confusion that existed in the Industry in regards to definition of the Meaning
31 30
SSM for Label 233-236. It is expected that Flight ID will be 0 0 Valid
sourced from FMC EQ ID of 002. Alternative implementation may 0 1 No Computed data
include Mode “S” XPDR EQ ID 018. In this case the user 1 0 Functional Test
cautioned that the SSM will be BCD format. See ARINC 1 1 Failure Warning
Characteristic 718A, “Mark 4 Air Traffic Control Transponder
(ATCRB/MODE S)”, Attachment 3A for more detailed
information.
ARINC SPECIFICATION 429, PART 1 - Page 98

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLES

TABLE 6-33

Label 360-002

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

“STX” BINARY WORD COUNT

PAD OCTAL LABEL
P 0 1
ZERO 360
0 0 0 0 0 1 0 0 0 0 0 0 1 1 1
INITIAL WORD

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

FLIGHT NUMBER FLIGHT NUMBER FLIGHT NUMBER OCTAL LABEL

P 0 0
CHAR #3 CHAR #2 CHAR #1 360

INTERMEDIATE WORD (SECOND)

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

FLIGHT NUMBER FLIGHT NUMBER FLIGHT NUMBER OCTAL LABEL

P 0 0
CHAR #6 CHAR #5 CHAR #4 360

INTERMEDIATE WORD (THIRD)

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

ORIGIN FLIGHT NUMBER FLIGHT NUMBER OCTAL LABEL

P 0 0
CHAR #1 CHAR #8 CHAR #7 360

INTERMEDIATE WORD (FOURTH)

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

ORIGIN ORIGIN ORIGIN OCTAL LABEL

P 0 0
CHAR #4 CHAR #3 CHAR #2 360

INTERMEDIATE WORD (FIFTH)

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

DESTINATION DESTINATION DESTINATION OCTAL LABEL

P 0 0
CHAR #3 CHAR #2 CHAR #1 360

INTERMEDIATE WORD (SIXTH)

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

PAD PAD DESTINATION OCTAL LABEL

P 0 0
ZEROS ZEROS CHAR #4 360

INTERMEDIATE WORD (SEVENTH)

NOTE: All characters are expressed in ISO #5 format, as defined in Attachment 5.

 ARINC SPECIFICATION 429, PART 1 - Page 99

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLE

TABLE 6-34

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

SUBSYSTEM SAL SUBSYSTEM ID

P 0
MSB (LABEL 172)
ARINC SPECIFICATION 429, PART 1 - Page 100

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLES

TABLE 6-35
FQIS System Data - Label 241 04D

LABEL: 241
EQPT ID: 04D
PARAMETER NAME: FQIS System Data
UNITS: (See Below)
RANGE (SCALE): (See Below)
SIGNIFICANT DIGITS: (See Below)
RESOLUTION: (See Below)
MIN TRANS INTERVAL (msec): 500
MAX TRANS INTERVAL (msec): 1024
SOURCE DESTINATION IDENTIFIER: 01 – LEFT MAIN TANK
10 – RIGHT MAIN TANK
11 – CENTER TANK

Label 241 is transmitted approximately once per second. The data encoding depends on the sequence which it is
transmitted. Label 241 transmitting sequence, as defined below, starts with the left main tank data followed by the right
main tank and then the center tank. Once all the tank data has been transmitted (63 words of data), the sequence will
repeat with word number 1, left main tank, and so on. To determine the data that is transmitted at any specific time
requires knowing where in the following sequence the word is taken.

LABEL 241 WORD SEQUENCE

Sig.
Word Signal Units Range Dig. Res Data

1 LEFT MAIN TANK NO. 1 pF 319.922 12 .078125 BNR

2 LEFT MAIN TANK NO. 2 pF 319.922 12 .078125 BNR
3 LEFT MAIN TANK NO. 3 pF 319.922 12 .078125 BNR
4 LEFT MAIN TANK NO. 4 pF 319.922 12 .078125 BNR
5 LEFT MAIN TANK NO. 5 pF 319.922 12 .078125 BNR
6 LEFT MAIN TANK NO. 6 pF 319.922 12 .078125 BNR
7 LEFT MAIN TANK NO. 7 pF 319.922 12 .078125 BNR
8 LEFT MAIN TANK NO. 8 pF 319.922 12 .078125 BNR
9 LEFT MAIN TANK NO. 9 pF 319.922 12 .078125 BNR
10 LEFT MAIN TANK NO. 10 pF 319.922 12 .078125 BNR
11 LEFT MAIN TANK NO. 11 pF 319.922 12 .078125 BNR
12 LEFT MAIN TANK NO. 12 pF 319.922 12 .078125 BNR
13 LEFT MAIN TANK NO. 13 pF 319.922 12 .078125 BNR
14 LEFT MAIN TANK NO. 14 pF 319.922 12 .078125 BNR
15 LEFT MAIN BITE CAP. NO. 1 pF 319.922 12 .078125 BNR
16 LEFT MAIN COMPENSATOR pF 319.922 12 .078125 BNR
17 LOAD SELECT 10,000 Lb 0-90000 1 10000 BCD
18 LOAD SELECT 1,000 Lb 0-9000 1 1000 BCD
19 LOAD SELECT 100 Lb 0-900 1 100 BCD
20 NO DATA TRANSMITTED DURING THIS WORD
21 LEFT MAIN FUEL DENSITY Lb/Gal 8.000 12 .000977 BNR (1)
22 RIGHT MAIN TANK NO. 1 pF 319.922 12 .078125 BNR
23 RIGHT MAIN TANK NO. 2 pF 319.922 12 .078125 BNR
24 RIGHT MAIN TANK NO. 3 pF 319.922 12 .078125 BNR
25 RIGHT MAIN TANK NO. 4 pF 319.922 12 .078125 BNR
26 RIGHT MAIN TANK NO. 5 pF 319.922 12 .078125 BNR
27 RIGHT MAIN TANK NO. 6 pF 319.922 12 .078125 BNR
28 RIGHT MAIN TANK NO. 7 pF 319.922 12 .078125 BNR
29 RIGHT MAIN TANK NO. 8 pF 319.922 12 .078125 BNR
30 RIGHT MAIN TANK NO. 9 pF 319.922 12 .078125 BNR
31 RIGHT MAIN TANK NO. 10 pF 319.922 12 .078125 BNR
32 RIGHT MAIN TANK NO. 11 pF 319.922 12 .078125 BNR
33 RIGHT MAIN TANK NO. 12 pF 319.922 12 .078125 BNR
34 RIGHT MAIN TANK NO. 13 pF 319.922 12 .078125 BNR
35 RIGHT MAIN TANK NO. 14 pF 319.922 12 .078125 BNR
36 RIGHT MAIN COMPENSATOR pF 319.922 12 .078125 BNR
37 RIGHT MAIN BITE CAP. NO. 2 pF 319.922 12 .078125 BNR
38 LOAD SELECT 10,000 Lb 0-90000 1 10000 BCD
39 LOAD SELECT 1,000 Lb 0-9000 1 1000 BCD
40 LOAD SELECT 100 Lb 0-900 1 100 BCD
41 NO DATA TRANSMITTED DURING THIS WORD
42 RIGHT MAIN DENSITY Lb/Gal 8.000 12 .000977 BNR
43 CENTER TANK NO. 1 pF 319.922 12 .078125 BNR
44 CENTER TANK NO. 2 pF 319.922 12 .078125 BNR
45 CENTER TANK NO. 3 pF 319.922 12 .078125 BNR
46 CENTER TANK NO. 4 pF 319.922 12 .078125 BNR
 ARINC SPECIFICATION 429, PART 1 - Page 101

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLE

TABLE 6-35 (cont’d)

LABEL 241 WORD SEQUENCE (cont’d)

Sig.
Word Signal Units Range Dig. Res Data

47 CENTER TANK NO. 5 pF 319.922 12 .078125 BNR

48 CENTER TANK NO. 6 pF 319.922 12 .078125 BNR
49 CENTER TANK NO. 7 pF 319.922 12 .078125 BNR
50 CENTER TANK NO. 8 pF 319.922 12 .078125 BNR
51 CENTER TANK NO. 9 pF 319.922 12 .078125 BNR
52 CENTER COMPENSATOR pF 319.922 12 .078125 BNR
53 CENTER BITE CAP. NO. 3 pF 319.922 12 .078125 BNR
54 NO DATA TRANSMITTED DURING THIS WORD
55 NO DATA TRANSMITTED DURING THIS WORD
56 NO DATA TRANSMITTED DURING THIS WORD
57 NO DATA TRANSMITTED DURING THIS WORD
58 NO DATA TRANSMITTED DURING THIS WORD
59 LOAD SELECT 10,000 Lb 0-90000 1 10000 BCD
60 LOAD SELECT 1,000 Lb 0-9000 1 1000 BCD
61 LOAD SELECT 100 Lb 0-900 1 100 BCD
62 NO DATA TRANSMITTED DURING THIS WORD
63 CENTER TANK DENSITY Lb/Gal 8.000 12 .000977 BNR

NOTES:
(1) Add 4 Lb/Gal adjustment to density data, i.e., 0000 = 4.0 Lb/Gal, FFF = 8.0 Lb/Gal.

FQIS (EQ ID 04D) SDI Encoding for Labels 012, 013, 020, 022, 023, 030, 255, 310, 320, 324, 342, 346, 354

Bits Data
9 10
0 0 Aux
1 1 Center
1 0 Left
0 1 Right

FQIS (EQ ID 04D) SDI Encoding for Labels 156, 157, 160

Bits Data
9 10
0 0 #1
1 0 #2
0 1 #3
1 1 #4
ARINC SPECIFICATION 429, PART 1 - Page 102

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLES

TABLE 6-36

S/G HARDWARE PART NO. – Label 060 025

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

OCTAL LABEL
P SSM BCD CHARACTER *** RESERVED SDI
060

Bit Bit Status

Function
No. 1 0
10 SDI (Indicates Sequence ID)*
11 RESERVED (Own P/N)
Own P/N Other P/N
12 RESERVED (Position ID)**
13 RESERVED (Position ID)**

* Refer to Table 1 below

** Refer to Table 2 below
*** Unused Characters (Digits) are Pad Zero

Table 1 Table 2

Bits Sequence Bits Position

10 9 ID 13 12 ID
0 1 First Three Digits 0 0 Left
1 0 Next Four Digits 1 0 Center As Left
1 1 Last Three Digits 1 1 Center As Right
0 1 Right
 ARINC SPECIFICATION 429, PART 1 - Page 103

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLE

TABLE 6-37

S/G SOFTWARE PART NO. – Label 061 025

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

OCTAL LABEL
P SSM BCD CHARACTER *** RESERVED SDI
061

Bit Bit Status

Function
No. 1 0
10 SDI (Indicates Sequence ID)*
11 RESERVED (Own P/N)
Own P/N Other P/N
12 RESERVED (Position ID)**
13 RESERVED (Position ID)**

* Refer to Table 1 below

** Refer to Table 2 below
*** Unused Characters (Digits) are Pad Zero

Table 1 Table 2

Bits Sequence Bits Position

10 9 ID 13 12 ID
0 1 First Three Digits 0 0 Left
1 0 Next Four Digits 1 0 Center As Left
1 1 Last Three Digits 1 1 Center As Right
0 1 Right
ARINC SPECIFICATION 429, PART 1 - Page 104

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLES

TABLE 6-37

OP. SOFTWARE PART NO. – Label 207 025

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

OCTAL LABEL
P SSM BCD CHARACTER *** RESERVED SDI
207

Bit Status
Bit
Function
No 1 0
10 SDI (Indicates Sequence ID)*
11 RESERVED (Own P/N)
Own P/N Other P/N
12 RESERVED (Position ID)**
13 RESERVED (Position ID)**

* Refer to Table 1 below

** Refer to Table 2 below
*** Unused Characters (Digits) are Pad Zero

Table 1 Table 2

Bits Sequence Bits Position

10 9 ID 13 12 ID
0 1 First Three Digits 0 0 Left
1 0 Next Four Digits 1 0 Center As Left
1 1 Last Three Digits 1 1 Center As Right
0 1 Right
 ARINC SPECIFICATION 429, PART 1 - Page 105

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLE

TABLE 6-38
Tank Unit Data – Label 241 160
Word
Number SDI DESCRIPTION UNITS
1 1 Tank Unit #1 pF
2 1 Tank Unit #2 pF
3 1 Tank Unit #3 pF
4 1 Tank Unit #4 pF
5 1 Tank Unit #5 pF
6 1 Tank Unit #6 pF
7 1 Tank Unit #7 pF
8 1 Tank Unit #8 pF
9 1 Tank Unit #9 pF
10 1 Tank Unit #10 pF
11 1 Tank Unit #11 pF
12 1 Tank Unit #12 pF
13 1 Tank Unit #13 pF
14 1 Tank Unit #14 pF
15 1 BITE Capacitor pF
16 1 Compensator pF
17 1 Load Select Lbs.
18 1 Load Select Lbs.
19 1 Load Select Lbs.
20 1 Undefined -
21 1 Fuel Density Lbs/Gal
22 2 Tank Unit #1 pF
23 2 Tank Unit #2 pF
24 2 Tank Unit #3 pF
25 2 Tank Unit #4 pF
26 2 Tank Unit #5 pF
27 2 Tank Unit #6 pF
28 2 Tank Unit #7 pF
29 2 Tank Unit #8 pF
30 2 Tank Unit #9 pF
31 2 Tank Unit #10 pF
32 2 Tank Unit #11 pF
33 2 Tank Unit #12 pF
34 2 Tank Unit #13 pF
35 2 Tank Unit #14 pF
36 2 Compensator pF
37 2 BITE Capacitor #2 pF
38 2 Load Select Lbs
39 2 Load Select Lbs
40 2 Load Select Lbs
41 2 Undefined -
42 2 Fuel Density Lbs/Gal
43 3 Tank Unit #1 pF
44 3 Tank Unit #2 pF
45 3 Tank Unit #3 pF
46 3 Tank Unit #4 pF
47 3 Tank Unit #5 pF
48 3 Tank Unit #6 pF
49 3 Tank Unit #7 pF
50 3 Tank Unit #8 pF
51 3 Tank Unit #9 pF
52 3 Compensator pF
53 3 BITE Capacitor #3 pF
54 3 Undefined -
55 3 Undefined -
56 3 Undefined -
57 3 Undefined -
58 3 Undefined -
59 3 Load Select Lbs
60 3 Load select Lbs
61 3 Load Select Lbs
62 3 Undefined -
63 3 Fuel Density Lbs/Gal
ARINC SPECIFICATION 429, PART 1 - Page 106

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLES

TABLE 6-38-1
Tank Unit Data – Label 241 160 (cont’d)
RAW DATA TABLE
All Data Entries are 12-bit Center Justified Words
Table Organization: Words 1-20 raw data for left tank
Word 1 = Tank Unit #1
Word 2 = Tank Unit #2
Word 3 = Tank Unit #3
Word 4 = Tank Unit #4
Word 5 = Tank Unit #5
Word 6 = Tank Unit #6
Word 7 = Tank Unit #7
Word 8 = Tank Unit #8
Word 9 = Tank Unit #9
Word 10 = Tank Unit #10
Word 11 = Tank Unit #11
Word 12 = Tank Unit #12
Word 13 = (Spare)
Word 14 = (Spare)
Word 15 = BITE Capacitor #1
Word 16 = Compensator
Word 17 = Load Select 10,000 Digit
Word 18 = Load Select 1,000 Digit
Word 19 = Load Select 100 Digit
Word 20 = None
Word 21-40 raw data for right tank
Word 21 = Tank Unit #1
Word 22 = Tank Unit #2
Word 23 = Tank Unit #3
Word 24 = Tank Unit #4
Word 25 = Tank Unit #5
Word 26 = Tank Unit #6
Word 27 = Tank Unit #7
Word 28 = Tank Unit #8
Word 29 = Tank Unit #9
Word 30 = Tank Unit #10
Word 31 = Tank Unit #11
Word 32 = Tank Unit #12
Word 33 = (Spare)
Word 34 = (Spare)
Word 35 = Compensator
Word 36 = BITE Capacitor #2
Word 37 = Load Select 10,000 Digit
Word 38 = Load Select 1,000 Digit
Word 39 = Load Select 100 Digit
Word 40 = None
Words 41-60 raw data for Center Tank
Word 41 = Tank Unit #1
Word 42 = Tank Unit #2
Word 43 = Tank Unit #3
Word 44 = Tank Unit #4
Word 45 = Tank Unit #5
Word 46 = Tank Unit #6
Word 47 = Tank Unit #7
Word 48 = Tank Unit #8
Word 49 = Tank Unit #9
Word 50 = Compensator
Word 51 = BITE Capacitor #3
Word 52 = (Spare)
Word 53 = (Spare)
Word 54 = (Spare)
Word 55 = (Spare)
Word 56 = (Spare)
Word 57 = Load Select 10,000 Digit
Word 58 = Load Select 1,000 Digit
Word 59 = Load Select 100 Digit
Word 60 = None
 ARINC SPECIFICATION 429, PART 1 - Page 107

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLE

TABLE 6-39

ICAO Aircraft Address (Part 1)

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 876 543 21
P SSM A16--------------------------------------------------------------- A1 Octal Label
MSB 214
001 100 01

c-16
ICAO Aircraft Address (Part 2)

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 876 543 21
P SSM A24--------------------------A17 Octal Label
LSB 216
011 100 01

NOTE: Bits 9-12 (PAD bits) are set to binary 0.

 ARINC SPECIFICATION 429, PART 1 - Page 108

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLES
TABLE 6-40

RADIO SYSTEMS MANAGEMENT WORD FORMATS

ADF
SIGN/STATUS
PARITY (odd)

RESERVED
MATRIX

0.5 kHz

SPARE

(SDI)
ANT

BFO
Function 1000 kHz 100 kHz 10 kHz 1 kHz LABEL
(1) (0) (5) (7) ADF Frequency
(032)

Bit No. 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 876 564 21

Example 1 0 0 0 0 1 0 0 0 0 0 1 0 1 0 1 1 1 1 0 0 0 0 0 010 110 00

Notes [1] [2] [2] 2 3 0

[1] When bit no. 14 is “zero”, the radio should tune to the whole kilohertz frequency encoded in the word.
When bit no. 14 is “one”, the radio should tune 0.5kHz above this frequency.
[2]
Bit Zero One
11 BFO off BFO on
12 ADF Mode ANT Mode

TABLE 6-41

DME
SIGN/STATUS

0.00/0.05 MHz
PARITY (odd)

MLS FREQ.

ILS FREQ.
DISPLAY
MATRIX

IDENT

Function 10 MHz 1 MHz 0.1 MHz DME SDI LABEL

c-4 Mode DME Frequency
(035)

Bit No. 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 876 543 21

Example 1 0 0 0 0 1 0 1 0 1 0 1 1 0 1 0 1 0 0 0 0 0 0 0 101 110 00

Notes [1] [5] [2] [7] [3] [4] 5 3 0

[1] Directed Frequency #1, 115.65 MHz, VOR

[2] Bit 18 is used only for VOR & ILS frequencies and is limited to .00 or .05

[3] Bits 15 & 14 codes: VOR (0,0), ILS (0,1) or MLS (1,0). (1,1) is spare
.
[4] Refer to table in Section 4.1.2 of ARINC Characteristic 709 for mode codes
.
[5] Although not encoded in the tuning word all VOR & ILS frequencies have 1 as hundreds digit.
c-16 Although not encoded in the tuning word all MLS frequencies have 5 as the thousand digit and
0 as the hundred digit. Add 5031 MHz to the coded value to obtain the MLS frequency.

c-10 [6] (Original note deleted)

[7] Bit 16 when equal to “one” specifies that a displayable BCD output is to be provided for that station,
c-4 and when bit 17 is a “one”, an ident output is to be generated for that station.
 ARINC SPECIFICATION 429, PART 1 - Page 109

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLES

TABLE 6-42

RADIO SYSTEMS MANAGEMENT WORD FORMATS

HF COM
Word #1

USB/LSB MODE
SSM/AM MODE
WORD IDENT.
PARITY (Odd)

SIGN/STATUS

Function 10 MHz 1 MHz 0.1 MHz 0.01 MHz 0.001 MHz LABEL
MATRIX

(2) (3) (5) (7) (9) HF COM Frequency

(037)

Bit No. 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 876 543 2 1

Example 0 0 0 1 0 0 0 1 1 0 1 0 1 0 1 1 1 1 0 0 1 0 0 0 111 110 0 0

Notes [1] [2] 7 3 0

[1] Bit no. 11 should be set to “zero” for LSB operation and “one” for USB operation.
[2] Bit no. 10 should be set to “zero” for AM operation and “one” for SSB operation.

TABLE 6-42-1
HF COM c-4
Word #2

WORD IDENT.
SIGN/STATUS
PARITY (odd)

RESERVED
MATRIX

Function 0.1 kHz NOT USED LABEL

(5) HF COM Frequency
(037)

Bit No. 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 876 543 21

Example 0 0 0 0 1 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 111 110 00
[1] 7 3 0

[1] Bit No. 10 is reserved for CW mode select. The CW mode is selected when bit number 10 is a “one”.
When the second word is transmitted, it should immediately follow the first HF word.

ALTERNATE FORM
TABLE 6-43
HF COM
Word #1
WORD IDENT.
SIGN/STATUS
PARITY (odd)

MATRIX

Function 10MHz 1 MHz 0.1 MHz 0.01MHz 0.001MHz SDI LABEL

(2) (3) (5) (7) (9) HF COM Frequency
(205)

Bit No. 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 876 543 2 1

Example 0 0 0 1 0 0 0 1 1 0 1 0 1 0 1 1 1 1 0 0 1 0 0 1 101 000 01
5 0 2
 ARINC SPECIFICATION 429, PART 1 - Page 110

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLES

TABLE 6-43-1
HF COM
Word #2

WORD IDENT.
SIGN/STATUS
PARITY (odd)

MATRIX
Function 0.1 kHz NOT USED SDI LABEL
(5) HF COM Frequency
(205)

Bit No. 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 876 543 2 1

Example 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 101 000 0 1
5 0 2

RADIO SYSTEMS MANAGEMENT WORD FORMATS

TABLE 6-44
ILS
SIGN/STATUS
PARITY (odd)

c- 5
MATRIX

Function 10 MHz 1 MHz 0.1 MHz 0.01 MHz RES. LABEL

SPARE
(0) (9) (3) (0) (SDI) Frequency

CAT.
ILS
(033)

Bit No. 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 876 543 21

c- 3 Example 1 0 0 0 0 0 1 0 0 1 0 0 1 1 0 0 0 0 0 0 0 0 0 0 110 110 00
3 3 0

BIT POSITION 12 11
c- 5
CATEGORY NOT 0 0
ILS CAT I 0 1
ILS CAT II 1 0
ILS CAT III 1 1

TABLE 6-44-1
VOR/ILS
SIGN/STATUS
PARITY (odd)

Function 10 MHz 1 MHz 0.1 MHz 0.01 MHz RES. LABEL

MATRIX

(0) (9) (3) (0) (SDI) VOR/ILS Frequency

SPARE

(034)
CAT.
ILS

Bit No. 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 76 5 4 3 2 1
Example 1 0 0 0 0 0 1 0 0 1 0 0 1 1 0 0 0 0 0 0 0 0 0 0 001 1 1 0 00
[1] 4 3 0

c- 2 [1] Bit number 14 should be set to “zero” for VOR frequencies and “one” for ILS frequencies by the
tuning
information sources.
 ARINC SPECIFICATION 429, PART 1 - Page 111

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLES

TABLE 6-45

VHF/COM SIGN/STATUS
PARITY (odd)

MATRIX

Function 10 MHz 1 MHz 0.1 MHz 0.01 MHz 0.001 MHz RES LABEL
(2) (8) (5) (3) (0) (SDI) VHF COM Frequency
(030)

Bit No. 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 876 543 21

Example 1 0 0 0 1 0 1 0 0 0 0 1 0 1 0 0 1 1 0 0 0 0 0 0 000 110 00
0 3 0

TABLE 6-46

RADIO SYSTEMS MANAGEMENT WORD FORMATS

ATC

ALT. DATA SOURCE SEL.

CONTROL FUNCTION
TRANSPONDER Pilot Selected Mode A

ALT. REP. ON/OFF

Reply Code
SIGN/STATUS
PARITY (odd)

MATRIX

IDENT.
Function 0-7 0-7 0-7 0-7 CONTROL RES. LABEL
(3) (6) (2) (0) FUNCTION (SDI) Beacon
Transponder Code
A4 A2 A1 B4 B2 B1 C4 C2 C1 D4 D2 D1 (031)

Bit No. 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 876 543 21

Example 1 0 0 0 1 1 1 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 100 110 00

Notes [2] [1] [ 2] [1] 1 3 0

[1]

Bit Zero One

11 Altitude Report On Altitude Reporting Off
13 Ident. OFF Ident. ON
14 Use #1 Alt. Data Source Use #2 Alt. Data Source

[2]

Control Panel
Bit
Function
Function 17 16 15 12
DABS ON/
0 0 0 1
ASAS OFF
Reset Aural
0 0 1 0
Warning Signal
Remainder are Reserved for future use.
ARINC SPECIFICATION 429, PART 1 - Page 112

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLES
TABLE 6-47

TACAN Control – Label 146 112

RANGE 126
RESOLUTION 1.0
RATE 5Hz ±10%

Bit No. Description

1 0
2 1 1
3 1
4 0 4
5 0
6 1
7 1 6
8 0
9-10 SDI
11 Distance Memory (DIST MEM=1)
12 Bearing Memory (BRG MEM=1)
13 Pad Zero
14 VOR/TAC Select (TAC=1, VOR=0)
15 TACAN Select (TAC 1=1, TAC 2=0)
16 Pad Zero
17-20 BCD Units Chan Cont (LSB=17)
21-24 Hex Tens Chan Cont (LSB=24)
25 Pad Zero
26 X/Y Mode (X=1, Y=0)
27-28 Mode Cont (See Table A)
29 Pad Zero
30-31 SSM (See Table B)
32 Parity (Odd)

RADIO SYSTEMS MANAGEMENT WORD FORMATS

Table A – Mode Control Table B - SSM

Bits Description
Bits Description
27 28
30 31
0 0 REC
0 0 Valid
0 1 A/A REC
0 1 Functional Test
1 0 T/R
1 0 No Computed Data
1 1 A/A T/R
1 1 Not Used
 ARINC SPECIFICATION 429, PART 1 - Page 113

ATTACHMENT 6
GENERAL WORD FORMATS AND ENCODING EXAMPLES

TABLE 6-48

TACAN Control Word – Label 147 115

Bit No. Function 1 0 Note

1 0
1
2 1
3 1
4 0 4 Label Number (147)
5 0
6 1
7 1 7
8 1
9 SEL TACAN 1 TACAN 2
10 SEL ANTENNA 2 ANTENNA 1
11 LOBE ANTENNA LOBE
12 AUTO/MAN TUNE AUTOTUNE MANUAL TUNE
13 A/A AGC Disable ENABLE DISABLE
14 Pad X
15 -16 TACAN/MLS Select [1]
17 (LSB)
18 BCD Channel Code Units
19
20 (MSB)
21 (LSB)
22 HEX Channel Code Tens
23
24 (MSB)
25 TST TEST NO TEST
26 X/Y X Y
27-28 Mode Control [2]
29 INT NORMAL INVERSE
30-31 SSM [3]
32 Parity (odds)

[1] TACAN/MLS Select [2] Mode Control [3] SSM

Bits Description Bits Description Bits Description

15 16 27 28 30 31
0 0 TACAN 0 0 REC 0 0 Valid Data
1 0 MLS W 1 0 T/R 0 1 No Computed Data
0 1 Not Used 0 1 A/A REC 1 0 Functional Test
1 1 MLS Z 1 1 A/A T/R 1 1 Not Used
ARINC SPECIFICATION 429, PART 1 - Page 114

ATTACHMENT 7
DATA BIT ENCODING LOGIC

BI - POLAR RZ
BIT NUMBER

DATA
N

1
11

1
10

0
9

0
8

1
0
7
6

1
5

0
4

1
3

1
2

0
1

1
NULL
HI

LO
 ARINC SPECIFICATION 429, PART 1 - Page 115

ATTACHMENT 8
OUTPUT SIGNAL TIMING TOLERANCES

HI
TRANSMITTED VOLTAGE LINE A TO LINE B

NULL

LO

PARAMETER HIGH SPEED OPERATION LOW SPEED OPERATION

Bit Rate 100k bps + 1% 12 – 14.5kbps
Time Y 10 µsec + 2.5% Z* µsec + 2.5%
Time X 5 µsec + 5% Y/2 + 5%
Pulse Rise Time** 1.5 + 0.5 µsec 10 + 5 µsec
Pulse Fall Time** 1.5 + 0.5 µsec 10 + 5 µsec

* Z = 1 where R = bit rate selected from 12 – 14.5kbps range

** Pulse rise and fall times are measured between the 10% and 90% voltage amplitude points on the leading and
trailing edges of the pulse and include permitted time skew between the transmitter output voltages A-to-
ground and B-to-ground. These rise and fall times are for open circuit output measurements – Appendix 1
c-16 provides waveforms for typical test performance.
 THIS ATTACHMENT WAS REPRODUCED
ARINC SPECIFICATION 429, PART 1 - Page 116 WITH THE PERMISSION OF GAMA.
REVISIONS ARE NOT SHOWN, FOR ANY
COMMENTS OR QUESTIONS, PLEASE
CONTACT GAMA.

ATTACHMENT 9A
GENERAL AVIATION LABELS AND DATA STANDARDS

The following labels and data standards provided by GAMA (General Aviation Manufacturers Association) are typically used by general aviation. Labels
with a “G” or “P” suffix refer to GAMA standard, or GA industry PRIVATE bit structures, respectively. All others are ARINC standard words.

MIN MAX
EQPT. SIG XMIT XMIT MAX
LABEL ID PARAMETER DATA BITS / POSITIVE APPROX. INT INT UPDATE
(OCTAL) (HEX) NAME TYPE UNITS RANGE DIGITS SENSE RESOL (msec) (msec) INT NOTES
001 02 Distance to go BCD Always Pos
09 Distance to go BCD N.M. ±3999.9 5 Always Pos 0.1 100 200
002 02 Time to go BCD Always Pos
09 Time to go BCD Min. 0-399.9 4 Always Pos 0.1 100 200
012 02 Ground Speed BCD Always Pos
09 Ground Speed BCD Knots 0-2000 4 Always Pos 1.0 250 500
017 10 Selected Runway Heading BCD Degrees 0-359.9° 4 Always Pos 0.1° 167 333
024G 11 Selected Course 1 BCD Degrees 0-359° 3 Always Pos 1.0° 167 333 Bit 11 Non Std
027 11 Selected Course 2 BCD Degrees 0-359° 3 Always Pos 1.0° 167 333
030G 02 VHF COM Frequency BCD MHz 118-135.975 5 0.025 100 200 SSM Squelch
16 VHF COM Frequency BCD MHz 118-135.975 5 0.025 100 200 SSM XMIT
031G 02 Beacon Transponder Code BCD Discrete 100 200
18 Beacon Transponder Code BCD Discrete 100 200 SSM Reply
032 02 ADF Frequency BCD KHz 190-1750 5 0.5 100 200
12 ADF Frequency BCD KHz 190-1750 5 0.5 100 200
033 02 ILS Frequency BCD MHz 108-111.95 4 0.05 167 333
10 ILS Frequency BCD MHz 108-111.95 4 0.05 167 333
034G 02 VOR/ILS Frequency BCD MHz 108-117.95 4 0.05 167 333 See Att. 9B
10 VOR/ILS Frequency BCD MHz 108-117.95 4 0.05 167 333 See Att. 9B
11 VOR/ILS Frequency BCD MHz 108-117.95 4 0.05 167 333 See Att. 9B
035G 02 DME Frequency BCD MHz 108-135.95 4 0.05 100 200 See Att. 9B
09 DME Frequency BCD MHz 108-134.95 4 0.05 100 200 See Att. 9B
041 02 Set Position Latitude BCD Deg:Min 180N-180S 6 North 0.1 250 500
042 02 Set Position Longitude BCD Deg:Min 180E-180W 6 East 0.1 250 500
043 02 Set Magnetic Heading BCD Deg 0-359° 3 1 .0° 250 500
060P 02 Omega Data Select BNR Discrete 100 200 See Att. 9B
061P 02 Covariance Data BNR 100 200 See Att. 9B
074G 02 Data Record Header DSC Discrete See Note 1 See Att. 9B
075G 02 Active WPT From/To Data DSC Discrete See Note 1 See Att. 9B
100G 02 Selected Course 1 BNR Deg/180 ±180° 12 0.05° 167 333 Bit 11 Non Std
100 11 Selected Course 1 BNR Deg/180 ±180° 12 0.05° 167 333
101G 02 Selected Heading BNR Deg/180 ±180° 12 0.05° 31.3 62.5 Bit 11 Non Std
25 Selected Heading BNR Deg/180 ±180° 12 0.05° 31.3 62.5
102G 02 Selected Altitude BNR Feet 65536 16 Above S.L. 1 100 200 See Att. 9B
105 10 Selected Runway Heading BNR Deg/180 ±180° 11 0.1° 167 333
110 11 Selected Course 2 BNR Deg/180 ±180° 12 0.05° 167 333
113G 02 Message Checksum BNR See Note 2 See Att. 9B
114 02 Desired Track (True) BNR Deg/180 ±180° 12 0.05° 31.3 62.5
115 02 Waypoint Bearing (True) BNR Deg/180 ±180° 12 A/C To WPT 0.05° 31.3 62.5
116G 02 Cross Track Distance BNR Naut Mi 128 18 Fly Left 0.0005 31.3 62.5
117G 02 Vertical Deviation BNR Feet 16384 14 Fly Down 1.0 31.3 62.5 See Att. 9B
121 02 HORIZ.CMD.(To Autopilot) BNR Deg/180 ±180° 14 Fly Right 0.01° 50 100
122G 02 VERT.CMD. (To Autopilot) BNR Deg/180 ±180° 12 Fly Up 0.05° 50 100
123 02 Throttle Command BNR Deg/sec 2.56 18 Inc. Power 0.001° 50 100
125 02 Greenwich Mean Time BCD Hr/Min 0-23.59.9 5 0.1 100 200
147G 02 Magnetic Variation BNR Deg/180 ±180° 12 East 0.05° 500 1000 Bit 11 Non Std
150 02 Greenwich Mean Time BNR Hr:Min:Sec 23:59:59 5:6:6 1.0 sec 50 100 See Att. 6
157P 06 Normalized AOA BNR 1=Stall ±2 12 Upward 0.0005 125 125 125
162G 12 ADF Bearing BNR Deg/180 ±180° 12 0.05° 31.3 62.5 Bit 11 Non Std
163G 02 Wind on Nose BNR Knots 256 9 Head Wind 0.5 50 100 Bit 29 Non Std
173 10 Localizer Deviation BNR DDM 0.4 12 Fly Right 0.0001 33.3 66.6
174 10 Glideslope Deviation BNR DDM 0.8 12 Fly Down 0.0002 33.3 66.6
202 02 DME Distance BNR Naut Mi 512 16 Always Pos 0.005 83.3 167
09 DME Distance BNR Naut Mi 512 16 Always Pos 0.005 3.3 167
204 02 Baro Corrected Alt.#1 BNR Feet 131,072 17 Above S.L. 1.0 31.3 62.5
210 02 True Airspeed BNR Knots 2047.93 15 Always Pos 0.0625 62.5 125
213 02 Static Air Temperature BNR Deg C 512 11 Above Zero 0.25 250 500
222P 02 VOR Radial BNR Deg/180 ±180° 12 To Station 0.044° 50 100 See Att. 6
222 02 VOR Omnibearing BNR Deg/180 ±180° 12 From VOR 0.044° 50 100 More than
10 VOR Omnibearing BNR Deg/180 ±180° 12 From VOR 0.044° 31.3 62.5 one MKR
11 VOR Omnibearing BNR Deg/180 ±180° 12 From VOR 0.044° 31.3 62.5 beacon bit set is
MKR self test.

241P Normalized AOA BNR 1-Stall ±2 12 Upward 0.0005 125 125 125
251G 02 Distance To Go BNR Naut Mi 4096 15 Always Pos 0.125 100 200
252 02 Time-To-Go BNR Minutes 512 9 Always Pos 1.0 100 200
260G 02 Date BCD Discrete 6 1 Day 500 1000 See Att. 9B
261P 02 GPS Discrete Word 1 DSC Discrete 1000 1000 1000
275G 02 LRN Status Word DSC Discrete 200 400 See Att. 9B
277P 02 Cabin DSPY Cont DSC DSC Discrete 200 200
300G 02 STN MAG DEC, BNR Discrete See Note 2 See Att. 9B
Type & Class
 THIS ATTACHMENT WAS REPRODUCED
WITH THE PERMISSION OF GAMA. ARINC SPECIFICATION 429, PART 1 - Page 117
REVISIONS ARE NOT SHOWN, FOR ANY
COMMENTS OR QUESTIONS, PLEASE
CONTACT GAMA.

ATTACHMENT 9A
GENERAL AVIATION LABELS AND DATA STANDARDS

MIN MAX
EQPT. SIG XMIT XMIT MAX
LABEL ID PARAMETER DATA BITS / POSITIVE APPROX. INT INT UPDATE
(OCTAL) (HEX) NAME TYPE UNITS RANGE DIGITS SENSE RESOL (msec) (msec) INT NOTES
301G 02 Message Characters 7-9 BNR Discrete See Note 2
302G 02 Message Characters 10-12 BNR Discrete See Note 2
303G 02 BNR Discrete See Note 2
Message Length / Type / Number
304G 02 Message Characters 1-3 BNR Discrete See Note 2
305G 02 Message Characters 4-6 BNR Discrete See Note 2
306G 02 NAV/WPT/AP Latitude BNR Deg/280 180N-180S 20 North .000172° See Note 2
307G 02 NAV/WPT/AP Longitude BNR Deg/180 180E-180W 20 East .000172° See Note 2
310 02 Present Position Latitude BNR Deg/180 180N-180S 20 North .000172° 100 200
311 02 Present Position Longitude BNR Deg/180 180E-180W 20 East .000172° 100 200
312 02 Ground Speed BNR Knots 4096 15 Always Pos 0.125 25 50
313 02 Track Angle (True) BNR Deg/180 ±180° 12 0.05 25 50
314 02 True Heading BNR Deg/180 ±180° 15 0.0055° 25 50
315 02 Wind Speed BNR Knots 256 8 Always Pos 1.0 50 100
316 02 Wind Angle (True) BNR Deg/180 ±180° 8 0.7 50 100
320 02 Magnetic Heading BNR Deg/180 ±180° 15 0.0055° 25 50
321 02 Drift Angle BNR Deg/180 ±180° 12 0.05° 25 50
326G 02 Lateral Scale Factor BNR Naut Mi ±128 15 0.0039 NM 80 1200
327G 02 Vertical Scale Factor BNR Feet ±2048 15 0.0625 Ft 80 1200
351G 02 Distance To Destination BNR Naut Mi 32,768 18 Always Pos 0.125 500 1000
352G 02 Est Time to Destinaiton BNR Minutes 4096 12 Always Pos 1.0 500 1000 Via Flight
Plan
353P 02 Dest Local Time Offset BCD Hour/Min 23:59 5 Always Pos .01 Min 1000 1000 1000 Via Flight
Plan
371G 02 Specific Equipment Ident DSC 500 1000 See Att. 9B
09 Specific Equipment Ident DSC 500 1000
10 Specific Equipment Ident DSC 500 1000
11 Specific Equipment Ident DSC 500 1000
12 Specific Equipment Ident DSC 500 1000
16 Specific Equipment Ident DSC 500 1000
18 Specific Equipment Ident DSC 500 1000

NOTE 1: These labels are transmitted once at the beginning of each flight plan/graphics map data transfer. Refer to the GAMA FMS Output Bus
Standard for further information.

NOTE 2: These labels are used to make up the individual records that comprise a flight plan/graphics map data transfer. Not all labels are transmitted
with each record. Ten records are transmitted in one second. Refer to the “FMS Waypoint/Navaid/Airport Data Transfer Protocol”,
addendum 3.
 THIS ATTACHMENT WAS REPRODUCED
ARINC SPECIFICATION 429, PART 1 - Page 118 WITH THE PERMISSION OF GAMA.
REVISIONS ARE NOT SHOWN, FOR ANY
COMMENTS OR QUESTIONS, PLEASE
CONTACT GAMA.

ATTACHMENT 9B
GENERAL AVIATION WORD EXAMPLES

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
VOR/ILS Frequency
P SSM See Chapter 3 See Below SDI
Label 034G

Bit 11 Marker Sensitivity “1” denotes high, “0” denotes low

Bit 12 Last Tune Source “1” denotes control head. “0“ denotes other
Bit 13 VOR Digital Filtering “1” denotes no filter. “0” denotes filter
(Normally “1” but “0” for Honeywell (Olathe) manufactured equipment)

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
DME Frequency
P SSM See Chapter 3 See Below SDI
Label 035G

Bit 13 12 11 DME Mode

0 0 0 Standby
0 0 1 Directed Freq #1
0 1 0 Directed Freq #2
0 1 1 Directed Freq #3
1 0 0 Hold Freq #1
1 0 1 Hold Freq #2
1 1 0 Not used
1 1 1 Spare

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Omega Data Select
P SSM 0 Relane Binary Address
MSB Label 060P

*Specific user word

Bit 28 Full Restart Bit “1” denotes restart
Bit 27 Rho Rho Updating “1” inhibits update

Bit 26 25 Function
0 0 No Action
0 1 Relane
1 0 Do Not Release
1 1 Invalid Use

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Term Exponent (IEEE Flt. Pt.) Coveriance Data*
P SSM Mantissa (IEEE Flt. Pt.)
Indent - MSB Label 061P

*Specific user word

Bit 27 Sign “1” denotes negative

Bit 29 28 Functions
0 0 Term 1
0 1 Term 2
1 0 Term 3
1 1 Not Used

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Pad Pad Data Record Header
P SSM Number of Records
(Zeros) (Zeros) MSB Lable 074G

Bit 21 Prior Record Change “1” denotes changed record

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
From Waypoint To Waypoint From Waypoint To Waypoint See Active Waypoint From/To Data
P SSM 0
LS Byte LS Byte MS Byte MS Byte Below Label 075G

Bit 9 Auto/Leg/Man/Obs “1” denotes Auto/Leg, “0” denotes Man/Obs These are
Bit 10 Mag/True Reference “1” denotes True, “0” denotes Magnetic User
Bit 11 Radar Waypoint Displayed “1” inhibits display Specific
Bit 12 Lat/Long/ILS Mode “1” denotes ILS, “0“ denotes Lat/Long bits

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Selected Altitude
P SSM Same as Attachment 2 SDI
Label 102G

Bit 11 Altitude Select Knob “0” denotes “in motion” User-specific

Bit 12 Altitude Alert “1” denotes “on” bits
THIS ATTACHMENT WAS REPRODUCED
WITH THE PERMISSION OF GAMA. ARINC SPECIFICATION 429, PART 1 - Page 119
REVISIONS ARE NOT SHOWN, FOR ANY
COMMENTS OR QUESTIONS, PLEASE
CONTACT GAMA.

ATTACHMENT 9B
GENERAL AVIATION WORD EXAMPLES

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Message Check Sum
P SSM Check Sum
Label 113G

The message checksum is the two’s complement 21 but sum of all the other words transmitted in the group discarding the intermediate
carry and replacing bit 32 with odd parity.

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
+ See Vertical Deviation
P SSM Data SDI
- Below Label 117G

Bit 14 VNAV Arm Enable/Alert “1” denotes enable

User
Bit 13 VNAV Bendover “1” denotes “capture”, “0” denotes “track”
Specific
Bit 12 VNAV Bendover Direction “1” denotes “fly up”, “0” denotes flydown”
bits
Bit 11 Altitude with respect to 1000 ft. “1” denotes “greater”, “0” denotes less

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Day Month Year SDI Date
P SSM
10s 1s 10s 1s 10s 1s Label 260G

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Waypoint Number See Words in Message Length/Type/No.
P SSM Spare
(Binary) Below Message Label 303G

Bit 16 Date Record “1” denotes “off route”, “0” denotes “on route”

Bit 24 FMS Plan Mode “1” denotes “SELECT”, “0” denotes “not SELECT”
Bit 25 WPT at Plan Center “1” denotes “CENTER”, “0” denotes “not CENTER”
Bit 26 Flight Plan GAP Follows “1” denotes “GAP”, “0” denotes “no GAP”

Bit 15 14 13 WYPT/STATION TYPE

0 0 0 Waypoint
0 0 1 Nav Aid
0 1 0 Airport
0 1 1 NDB
1 0 0 Altitude Profile Point
1 0 1 No Symbol
1 1 0 VOR
1 1 1 Intersection
ARINC SPECIFICATION 429, PART 1 - Page 120 THIS ATTACHMENT WAS REPRODUCED
WITH THE PERMISSION OF GAMA.
REVISIONS ARE NOT SHOWN, FOR ANY
COMMENTS OR QUESTIONS, PLEASE
CONTACT GAMA.

ATTACHMENT 9B
GENERAL AVIATION WORD EXAMPLES

Bit No. Function Bit Status

1 0
1 x
2 x
3 x
Label
4 x
261G 02
5 x
LRN Status
6 x
7 x
8 x
9
SDI
10
11 Pad Zero
Spare
12
13
14
15
16 Reserved
17
18
19
20 Vert Dev (Final Appr) Angular Linear
21 Lat Dev Scaling in Transition Yes No
22 Lat Dev. (Final Appr) Angular Linear
23 Appr Integrity (Final Appr) Valid Invalid
24 GPS Integrity Fail Valid
GPS Annunciation
25 27(0) & 26(0) & 25(0) – Enroute
26 27(0) & 26(0) & 25(1) – Terminal
27 27(0) & 26(1) & 25(0) – Approach
(27(1) & 26(0) & 25(0) – Oceanic
28
Spare
29
SSM
31(0) & 30(0) – Normal Operations
30
31(0) & 30(1) – No Computed Data
31
31(1) & 30(0) – Functional Test
31(1) & 30(1) – Not used
32 Parity (odd)
 THIS ATTACHMENT WAS REPRODUCED ARINC SPECIFICATION 429, PART 1 - Page 121
WITH THE PERMISSION OF GAMA.
REVISIONS ARE NOT SHOWN, ANY
COMMENTS OR QUESTIONS, PLEASE
CONTACT GAMA.

ATTACHMENT 9B
GENERAL AVIATION WORD EXAMPLES

Bit No. Function Bit Status

1 0
1 x
2 x
3 x
Label
4 x
275G 02
5 x
LRN Status
6 x
7 x
8 x
9
SDI
10
11 Waypoint Alert On Off
12 Dead Reckon DR Not DR
13 Direct To Select Not Select
Mode
15(0) & 14(0) – Multiple Sensor Based
14 15(0) & 14(1) – VOR/DME Offset (RNAV) Approach
15 15(1) & 14(0) – VOR/TACAN (non-Offset)
Approach/Enroute
15(1) & 14(1) – ILS Approach
16 Vert & Lat Dev Scaling Approach Enroute
17 FMS Controlled Hdg Sub-mode FMS/FGS FGS Only
18 Remote FGS Army for Nav Capt Arm No Change
19 FMS Plan Mode Select Not Select
20 Display Final Appr Course Display No Change
21 Angular Scaling Active Not Active
22 Integrity Warn Warn Not Warn
23 To To Not To
24 From From Not From
25 Parallel XTK Offset Selected Not Selected
26 Airport Display Selected Select Not Selected
27 Message Alert On Off
28 True/Mag True Magnetic
29 HSI Valid (NAV Warn) Valid Warn
30
SSM
31
32 Parity (odd)
 THIS ATTACHMENT WAS REPRODUCED
ARINC SPECIFICATION 429, PART 1 - Page 122 WITH THE PERMISSION OF GAMA.
REVISIONS ARE NOT SHOWN, FOR ANY
COMMENTS OR QUESTIONS, PLEASE
CONTACT GAMA.

ATTACHMENT 9B
GENERAL AVIATION WORD EXAMPLES

Bit No. Function Bit Status

1 0
1 x
2 x
3 x
Label
4 x
277G 02
5 x
LRN Status
6 x
7 x
8 x
9
SDI (if required)
10
11 Play Briefing #1
12 Play Briefing #2
13 Play Briefing #3
14 Play Briefing #4
15 Play Briefing #5
16 Play Briefing #6
17 Cancel Briefing #1
18 Cancel Briefing #2
19 Cancel Briefing #3
20 Cancel Briefing #4
21 Cancel Briefing #5
22 Cancel Briefing #6
23 Annunciate Cabin Message (Note)
24
25
26 Spares Pad Zero
27
28
29 Alternate Format ALTERNATE STD
30 SSM
31 31(0) & 30(0) – Normal Operation
31(0) & 30(1) – No Computed Data
31(1) & 30(0) – Functional Test
31(1) & 30(1) – Failure Warning
32 Parity (Odd)

NOTE: The ALTERNATE FORMAT bit (#29) causes the briefing play (BITS 11 – 16) and briefing cancel (BITS 17
– 22) controls to be interpreted as the briefing number from 1 to 63 with the briefing #1 bit as the least
significant. If BIT 29 is set to 1, this decoding will be used. If the briefing number is non zero, the indicated
briefing will be played or canceled.
THIS ATTACHMENT WAS REPRODUCED ARINC SPECIFICATION 429, PART 1 - Page 123
WITH THE PERMISSION OF GAMA.
REVISIONS ARE NOT SHOWN, FOR ANY
COMMENTS OR QUESTIONS, PLEASE
CONTACT GAMA.

ATTACHMENT 9B
GENERAL AVIATION WORD EXAMPLES

Bit No. Function Bit Status

1 0
1 x
2 x
3 x
Label
4 x
300 02
5 x
Station Declination
6 x
7 x
8 x
9
10
11
Spares Pad Zero
12
13
14
15 DME Not Collated Same Location
16 Tuned and Received Being Received Not Received
17
18
19 Station Declination
20 Binary number with sign bit 24 East is positive. West is
21 2’s complement of the positive value. Range is 127 deg.
22 E/W. Resolution is 1 degree at bit 17.
23
24
25 VOR at location Yes No
26 DME at location Yes No
27 TACAN at location Yes No
28
Class Bit 29/28/0 low 0/1 high 1/0 terminal
29
30
SSM
31
32 Parity
ARINC SPECIFICATION 429, PART 1 - Page 124 THIS ATTACHMENT WAS REPRODUCED
WITH PERMISSION OF GAMA.
REVISIONS ARE NOT SHOWN, FOR ANY
COMMENTS OR QUESTIONS, PLEASE
CONTACT GAMA.

ATTACHMENT 9B
GENERAL AVIATION WORD EXAMPLES

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

GA Equipment
Company Private Company I. D. EQ Code EQ Code Ident
P Use (Binary) MSD (Hex) MSD (Hex) SDI LABEL 371

LABEL 371
Company I. D. Field
Binary Bit Assignments COMPANY

24 23 22 21 20 19

0 0 0 0 0 1 B&D INSTRUMENTS
0 0 0 0 1 0 BEECH AIRCRAFT
0 0 0 0 1 1 BENDIX AVIONICS
0 0 0 1 0 0 CANADIAN MARCONI
0 0 0 1 0 1 CESSNA AIRCRAFT
0 0 0 1 1 0 COLLINS AVIONICS
0 0 0 1 1 1 DELCO ELECTRONICS
0 0 1 0 0 0 FOSTER RNAV
0 0 1 0 0 1 GABLE CONTROLS
0 0 1 0 1 0 GLOBAL SYSTEMS
0 0 1 0 1 1 GULFSTREAM AEROSPACE
0 0 1 1 0 0 HONEYWELL
0 0 1 1 0 1 KING RADIO
0 0 1 1 1 0 LEARJET
0 0 1 1 1 1 LITTON AERO PRODUCTS
0 1 0 0 0 0 OFFSHORE NAVIGATION
0 1 0 0 0 1 RACAL AVIONICS
0 1 0 0 1 0 SPERRY
0 1 0 0 1 1 UNIVERSAL NAVIGATION SYS
0 1 0 1 0 0 3M AVIATION SAFETY SYSTEMS
0 1 0 1 0 1 ALLIEDSIGNAL GENERAL AVIATION AVIONICS
0 1 0 1 1 0 ALLIEDSIGNAL GLOBAL WULFSBERG
0 1 0 1 1 1 BF GOODRICH AVIONICS
0 1 1 0 0 0 GARMIN
0 1 1 0 0 1 ARNAV
0 1 1 0 1 0 COMPUTER INSTRUMENT CORPORATION
0 1 1 0 1 1 SPARE

1 1 1 1 1 1 SPARE
 ARINC SPECIFICATION 429, PART 1 - Page 125

THIS ATTACHMENT WAS REPRODUCED

WITH THE PERMISSION OF GAMA.
REVISIONS ARE NOT SHOWN, FOR ANY
COMMENTS OR QUESTIONS, PLEASE
CONTACT GAMA.

ATTACHMENT 9C
GENERAL AVIATION EQUIPMENT IDENTIFIERS

Equipment HEX
EQUIPMENT
ID

01 Flight Control Computer

02 Flight Management Computer
04 Inertial Reference System
05 Attitude and Heading Ref. System
06 Air Data System
09 Airborne DME
0B Global Positioning System
10 Airborne ILS Receiver
11 Airborne VOR Receiver
12 Airborne ADF System
16 Airborne VHF Comm Receiver
18 ATC Transponder
25 Electronic Flight Instruments
27 Microwave Landing System
36 Radio Management System
5A Loran
5B Omega
A9 Airborne DME Controller
B0 Airborne ILS Controller
B2 Airborne ADF Controller
B6 VHF Comm Controller
B8 ATC Transponder Controller
C7 Microwave Landing System Controller
FA Loran Controller
FB Omega Controller
 ARINC SPECIFICATION 429, PART 1 - Page 126

ATTACHMENT 10
MANUFACTURER SPECIFIC STATUS WORD

32 31 30 29 28 27 26 25 24 23 22 21 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Company Company I.D. Label
P
Private Use [A] (Binary) (171)

BIT 16 15 14 13 12 11 Company
0 0 0 0 0 1 B&D INSTRUMENTS
0 0 0 0 1 0 BEECH AIRCRAFT
0 0 0 0 1 1 BENDIX AVIONICS
0 0 0 1 0 0 CANADIAN MARCONI
0 0 0 1 0 1 CESSNA AIRCRAFT
0 0 0 1 1 0 COLLINS AVIONICS
0 0 0 1 1 1 DELCO ELECTRONICS
0 0 1 0 0 0 FOSTER RNAV
0 0 1 0 0 1 GABLES CONTROLS
0 0 1 0 1 0 GLOBAL SYSTEMS
0 0 1 0 1 1 GULFSTREAM AEROSPACE
0 0 1 1 0 0 HONEYWELL
0 0 1 1 0 1 KING RADIO
0 0 1 1 1 0 LEAR JET
0 0 1 1 1 1 LITTON AERO PRODUCTS
0 1 0 0 0 0 OFFSHORE NAVIGATION
0 1 0 0 0 1 RACAL AVIONICS
0 1 0 0 1 0 SPERRY
0 1 0 0 1 1 UNIVERSAL NAVIGATION SYSTEMS
0 1 0 1 0 0 3M AVIATION SAFETY SYSTEMS
0 1 0 1 0 1 ALLIED SIGNAL GENERAL AVIATION AVIONICS
0 1 0 1 1 0 ALLIED SIGNAL GLOBAL WULFSBAG
0 1 0 1 1 1 BF GOODRICH AVIONICS
0 1 1 0 0 0 GARMIN
0 1 1 0 0 1 ARNAV
0 1 1 0 1 0 COMPUTER INSTRUMENT CORPORATION
0 1 1 0 1 1 SPARE

1 1 1 1 1 1 SPARE

[A] This word is used for manufacturer-specific information exchange (e.g., sub-LRU-Level BITE status). The
Company I.D. fields should be used to differentiate each manufacturers’ unique use of the Company Private
Use field.
 ARINC SPECIFICATION 429, PART 1 - Page 127

ATTACHMENT 11
SYSTEM ADDRESS LABELS

SYSTEMS SYSTEM ADDRESS LABEL

(OCTAL)
777 CABIN INTERPHONE SYSTEM 152
c-16 CVR 157
747 DFHR AND A330/340 SSFDR 163
c-15 DFDAU (MANDATORY LOAD FUNCTION) 170
SDU #2 173
RFU 174
HGA/HPA TOP/PORT 175
HGA/HPA STARBOARD 176
LGA/HPA 177
GPS/GNSS SENSOR 201
FCMC Com A340-500/600 210
c-16 FCMC Mon A340-500/600 211
FCMC Int A340-500/600 212
MCDU 1 220
MCDU 2 221
MCDU 3 222
PRINTER 1 223
PRINTER 2 224
c-16 HUD 225
HIGH SPEED DL (ARINC 615) 226
MCDU 4 230
EIVMU 1 234
c-14 EIVMU 2 235
EIVMU 3 236
EIVMU 4 237
APM-MMR 241
MMR 242
ILS 244
MLS 245
c-16 AHRS 246
VDR #1 251
VDR #2 252
VDR #3 253
c-15 CABIN VIDEO SYSTEM (AIRSHOW) 266
LOW SPEED DL (ARINC 603) 300
FMC 1 300
FMC 2 301
DFDAU (AIDS) 302
c-14 CFDIU 303
ACARS MU/CMU (724B, 748) 304
WBS 305
TCAS 306
SDU #1 307
GPWS 310
GNLU 1 311
GNLU 2 312
c-16
GNLU 3 313
GNU 1 314
GNU 2 315
 ARINC SPECIFICATION 429, PART 1 - Page 128

ATTACHMENT 11
SYSTEM ADDRESS LABELS

SYSTEMS SYSTEM ADDRESS LABEL

(OCTAL)
GNU 3 316
AUTOTHROTTLE COMPUTER 321
FCC 1 322
FCC 2 323
FCC 3 324
APU 325
c-16 APU CONTROLLER 326
MODE CONTROL PANEL (MCP) 327
FMC 3 330
ATC TRANSPONDER 331
DADC 332
CABIN TELECOMMUNICATIONS UNIT (CTU) 334
c-15 HF DATA RADIO/DATA UNIT #1 340
HF DATA RADIO/DATA UNIT #2 344
ACESS 360
c-14 EFIS 361
PASSENGER SERVICES SYSTEM (PSS) 767300,400 362
c-16 CABIN SERVICE SYSTEM (CSS) 747-400 363
AUDIO ENTERTAINMENT SYSTEM (AES)BOEING 364
c-14 ENGINE INDICATION UNIT 365
c-16 MULTICAST 366
BRIDGE 367
CABIN TERMINAL 3 372
CABIN TERMINAL 4 373
c-14 CABIN TERMINAL 1 374
CABIN TERMINAL 2 375
OMEGA NAV. SYSTEMS 376
 ARINC SPECIFICATION 429, PART 1 - Page 129

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

A1-1.0 Introduction

Selection of the electrical characteristics of the Mark 33 DITS followed verification of the suitability of proposed values in
laboratory tests performed by the Boeing Commercial Airplane Co. Boeing presented two reports to AEEC’s Systems
Architecture and Interfaces Subcommittee on these activities, one at the meeting held in Arlington, Virginia, in March 1977
and the other at the meeting held in Los Angeles, California, in May 1977. The material in this Appendix is excerpted from
these reports.

A1-2.0 Electromagnetic Emission and Susceptibility Tests

Electromagnetic emission and susceptibility tests were conducted to determine if the proposed 100 kbps waveform was
suitable for use in a commercial airplane EMI environment. The EMI conditions used for the tests were derived from
RTCA Document DO-160, “Environmental Conditions and Test Procedures for Airborne Electronic/Electrical Equipment
and Instruments” dated February 28th, 1975.

A1-2.1 Cable and Test Configuration

The cable used for the tests was standard aircraft type twisted shielded wire of 22 AWG. The wire configuration consisted
of approximately 60 ft. of cable which was subjected to the EMI environment within a screened room. This cable was
connected in series with 300 ft. of cable not subjected to the EMI environment. The test was configured to simulate the
maximum length wire run with DO-160 conditions applied.

The 60 Ft. length of cable was connected to the transmitter for the emission tests and to the receiver for the susceptibility
tests.

A1-2.2 Transmitter Characteristics

The block schematic of the bipolar line driving transmitter built for the tests is shown in Figure a-(i). The waveform was
shaped at the pulse generator such that it exhibited the following characteristics:

Differential Output Voltage:

HI +10V
NULL 0V
LO -10V
Risetime = Falltime = l.0 µ sec
Bit Rate= 100 kilobits/second
HI time= NULL time= LO time

A1-2.3 Receiver Input Circuit Description

To perform the susceptibility tests, receivers were constructed utilizing various methods of common mode rejection and
various processing schemes.
Differential Amplifier Input. Figure a-(ii) shows schematics of the differential input stages used for the receivers. The
differential amplifier input stage required resistors to local ground at the input to provide a path for the input current for the
voltage followers. Voltage protection was used to prevent damage to the voltage followers in the event of high voltage,
common mode spikes. The voltage follower stages provided a controlled impedance for the differential amplifier stage.

Opto-Isolator Input The opto-isolator input stage utilized two H-P 5082-4371 isolators connected in opposite polarity to
detect the bipolar data. The HP 5082-4371 input has a forward conduction “knee” at approximately 1.4 volts. A second
simple LED (HP 5082-4650) was connected in series with each opto-isolator to provide a combined knee voltage of
approximately 3 volts. A series resistor RL of 1000 ohms was placed in series with the LED/opto-isolator network to limit
the receiver current to 7mA at 10 volts (differential) applied at the input. At 4.5V differential on the line, one opto-isolator
conducts 1.5 mA.
One circuit configuration which enables the opto-isolator to operate at 100 kilobits per second at these low input currents is
shown in figure a-(iii). A potential of +15 volts is applied to pin 8 to provide maximum gain in the first transistor. During
conduction, a charge on the second transistor is discharged via pin 7 and R2 to a potential of +0.5 volts set by R1 and R3.
Discharging to a +0.5 volt potential reduces the possibility of a loss of the first bit following a long null period. This
problem has been observed when discharging pin 7 to ground potential.
 ARINC SPECIFICATION 429, PART 1 - Page 130

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(i)
BIPOLAR TRANSMITTER BLOCK SCHEMATIC

SHAPED
BIPOLAR
+ RZ
PULSE
GENERATOR
_

SWITCHING
PSEUDO LINE
LOGIC TERMINATION
RANDOM DRIVER
BIT SEQUENCE
GENERATOR

DETAIL OF LINE DRIVER AND TERMINATION

LM0002
Ro L1
2

LM0002 Ro L1
2
 ARINC SPECIFICATION 429, PART 1 - Page 131

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(ii)
RZ BIPOLAR RECEIVER INPUT TYPES TESTED

DIFFERENTIAL
R AMPLIFIER
OVER
VOLTAGE
VOLTAGE FOLLOWERS

R PROTECTION

R > 12 K Ohms (Provides Path for V. F. Input Current)

Figure (a) Differential amplifier input schematic.

L R
1 L

LED
LED

L
2 OPTO

ISOLATORS

ONE’S
ZERO’S

RL = CURRENT LIMITING = 1000 OHMS

LED = LED IN SERIES WITH OPTO ISOLATOR TO PROVIDE ON NULL LEVEL
OPTO-ISOL = H-P 5082-4371

Figure (b) OPTO-ISOLATED INPUT SCHEMATIC

ARINC SPECIFICATION 429, PART 1 - Page 132

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

A1-2.4 Receiver Data Detection Technique

Two data detection schemes were used, (i) data sampling (sample and decision) and (ii) integrate and dump (Figure a-
(iv).

The data sampling system detects positive-going or negative-going edges which exceed ±3 volts differential voltage.
The edges cause a timing circuit to time for approximately 2 µsec. When the timing circuit has timed out, a sample of
the input is taken. If the sample is HI, a ONE is declared. If the sample is LO, a ZERO is declared. If the sample is
NULL, and error diagnostic can be output, since a NULL state is known to be invalid at the data sampling time. An
error diagnostic will be output if, for example, during a period of NULL on the line, a short-duration noise spike causes
the input to exceed the ±3V threshold, so initiating the edge detector timing circuit, but dissipates rapidly so that a
NULL is estimated at the data sampling time.

The integrate-and-dump processor circuit detects positive or negative-going edges which exceed the ±3V differential
threshold. The edge detection causes an integration circuit to integrate the input voltage for a period of 5 µsec. The
output of the integrator is sampled (timing is derived from the edge detector) at the end of the integration period. If it is
above zero voltage, a ONE is declared; if it is below zero voltage, a ZERO is declared.

A threshold level could be introduced about zero voltage to provide an indication of the total energy contained in the
pulse. If the integrator output fell within the threshold, an error diagnostic could be presented indicating the at the
detection of the bit was marginal.

A1-2.5 Test Data Message

The test waveform was a continuous pseudo-random bit pattern. This continuous pattern did not test the initial
synchronization or “false-alarm” aspects in a word-by-word transmission environment with NULL on the transmission
line between words.

A1-2.6 Emission of RF Energy Test Results

The following tests were performed under conditions of light (one receiver) and heavy (20 receivers) line loading.

A. Conducted RF Interference (RTCA DO-160 Paragraph 21.2)

The interference measured was within the limits specified in DO 160 Figure 21-2.

B. Radiated RF Interference (RTCA DO-160 Paragraph 21.3)

The interference measured was within the limits specified in DO-160 Figure 21-5.

It should be noted that the 20dB limit exceedance permitted in DO 160 was not taken. The transmitter output spectrum
can be further improved by the addition of filtering to attenuate output frequencies above those of interest in the digital
data.

A1-2.7 Susceptibility Test Results

The tests were performed to determine the susceptibility of the Mark 33 DITS to RF, AF and spike interference levels
specified in DO-160 under conditions of light (one receiver) and heavy (20 receivers) line loading.

The following receiver configurations were tested:

(i) Differential Amplifier input, time sample processing

(ii) Differential Amplifier input, integrate-and-dump processing
(iii) Opto-isolator input, time sample processing
(iv) Opto-isolator input, integrate-and-dump processing

The data transmitted consisted of a continuous pseudo-random bit sequence. Error checking was made on a bit-by-bit
basis.
A. Conducted RF Susceptibility (DO-160 Paragraph 20.20B Category Z)
No bit errors were detected with RF applied to any of the line loading and receiver configurations.
B. Magnetic Fields Induced Into Interconnecting Cables (DO-160 Paragraph 19.3)
Test performed at a level above those specified in DO-160 Figure 19-1. No bit errors were detected with the
field applied to the cable for any cable loading or receiver configuration.
 ARINC SPECIFICATION 429, PART 1 - Page 133

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(iii)
OPTO-ISOLATOR FRONT-END CIRCUIT SCHEMATIC

15 V 5V

R4
2
5.6k

3 6
O/ P

HP - 5082 - 4371
5V 7
R2
R1
500
10k

R3
1k
ARINC SPECIFICATION 429, PART 1 - Page 134

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(iv)
DATA DETECTION

(a) SAMPLE –AND- DECISION

BIT N BIT N + 1

HI
T+
NULL T -
LO

D D

E S E S
ZERO

( b ) INTEGRATE – AND - DUMP

HI T+
NULL T-
LO
S DMP S DMP

I I

E E

LEGEND:

E = EDGE DETECT (BIT TIMING)

D = DELAY

S = SAMPLE

I = INTEGRATION INTERVAL

DMP = DUMP INTEGRATOR CHARGE

 ARINC SPECIFICATION 429, PART 1 - Page 135

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

C. Electric Fields Induced Into Interconnecting Cables (DO-160 Paragraph 19.4)

The tests were perform with voltage levels above those specified in DO 160 Figure 19-1 Category Z. No bit
errors were detected with the field applied for any cable loading or receiver configuration.

D. Spikes Induced Into Interconnecting Cables (DO-160 Paragraph 19.5, Category Z)

The spikes were generated and applied to the cable as shown in DO-160, Figure 19-4. Bit errors were counted
during the application of 50 transients and also following the transient test. The following results were
observed:
Receiver Configuration Line Loading
Light Heavy

Diff. Amp., Sample Det 0 0

Diff. Amp., Int. & Dump Det 0 0
Opto-Isolator, Sample Det 8 15
Opto-Isolator, Int & Dump Det 0 1

All configurations performed with zero bit errors for approximately 107 bits following the transient test.

A1-3.0 Pulse Distortion Tests For Typical Aircraft wire Installations

Laboratory testing and computer simulation studies were conducted to investigate the pulse distortion introduced on
typical aircraft wire installations.

A1-3.1 Laboratory Tests

Receivers and a transmitter were constructed to operate using the DITS high speed (100 KBPS) waveform. Lengths of
twisted shielded cable were connected to form a representative wiring configuration for digital data. The wire length and
stub configuration were selected to represent postulated installations on a B747 airplane. The cable used for lab tests
was 20 and 22 AWG twisted shielded cable with wrapped KAPTON insulation, no. BMS B-51, Class 2 type III. The
pulse distortion at the receiver nodes of the wiring systems were recorded. The characteristics of the 20 AWG cable
were measured and used to develop the cable model used in the computer simulation.
A1-3.2 Computer Simulation

A computer program was developed to evaluate pulse distortion on lines with stubs. The DITS transmitter impedance
and voltage waveform was modeled. The cable model was developed from the measured cable characteristics. The
DITS receiver input impedance was modeled.

The computer simulation was run and results were plotted for various line length and stub configurations representing
postulated installations on a B747 airplane.

A1-3.3 Results

The results of the laboratory tests and computer simulation for the same cable configuration showed good agreement,
with a maximum difference of 0.4 volts on rising and falling edges. The computer simulation showed slightly higher
cable loss effect than the lab test. The lab test results were recorded using an oscilloscope camera; the computer results
were plotted. Only the plotted results are presented here.

Figure a-(v) shows the schematic for the first simulation. This configuration represents a transmitter, a receiver and a
single length of twisted shielded cable 200 feet long. The cable is modeled as Blocks 1 to 4, for later stub connection.

At the transmitter and receive ends of the cable, the shields are grounded via a 0.05 µH inductor (which models the
inductance of the ground lead). At other nodes, the shields and cable inners are carded through, representing a
continuous length of cable.

Figure a-(vi) Transmitter open circuit differential output voltage. This waveform was used for all the simulation runs.

Figure a-(vii) The transmitter output voltage and receiver input voltage for the configuration in Figure a-(v).
Figure a-(viii) shows the schematic for the second simulation. This configuration represents a transmitter at an engine
location, with receivers at the equipment bay and the flight deck. Four receiver loading configurations are shown with
maximum loading of twenty receivers. The waveforms for this simulation run are shown in Figures a-(ix) through a-
(xvi).
ARINC SPECIFICATION 429, PART 1 - Page 136

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

Figures a-(ix) and a-(x) Transmitter and receiver waveform for loading configuration 1.

Figures a-(xi) to a-(xvi) Waveforms for loading configurations 2, 3 and 4.

Figure a-(xvii) shows the schematic for the third simulation. This configuration represents a transmitter at the flight
deck with receivers at the equipment bay, the inner engine and the outer engine.

Figures a-(xviii) to a-(xxi) Waveforms for the third simulation.

Figure a-(xxii) shows the schematic for the fourth simulation. This configuration represents a transmitter at the
equipment bay with receivers at the equipment bay, the flight engineer’s panel, the first officer’s panel and the captain’s
panel.

Figures a-(xxiii) to a-(xxvi) Waveforms for the fourth simulation.

Figure a-(xxvii) shows the schematic for the fifth simulation. This is a long line simulation and is included to show the
operation of the system with lines longer than would realistically be used in a “B747-sized” airplane. This configuration
represents a transmitter with one receiver close (10 feet) and one receiver remote (500 feet).

Figures a-(xxviii) and a-(xxix) Waveforms for the “long line” configuration.

A1-3.4 Conclusions

From laboratory tests and simulations, it is concluded that no intolerable bit distortion is introduced into the “high speed
DITS” waveform due to cable lengths and stub configurations likely to be encountered on a “B747-size” transport
aircraft.
If installations are anticipated involving longer line lengths or cables with radically different electrical characteristics,
then further investigation may be required.
 ARINC SPECIFICATION 429, PART 1 - Page 137

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(v)

TRANSMITTER

BMS 13-51 20 AWG TSP 200 100 k

1 1 4 1 4 1 4 1 4 1 REC 1
TRANS (58m) (1m) (1m) (1m)
2 2 BUSLIN 5 2 BUSLIN 5 2 BUSLIN 5 2 BUSLIN 5 2 100k
3 1 6 3 2 6 3
3 6 3
4 6

1 SHIELD 2 1
SHIELD 2 1 SHIELD 2 1 SHIELD 2
1 2 3 4
* *

ALL
A L’s
.1
µh
.05µ
3 5 1
.01 40

4 6 TERM
2
.01 40
.1

B * SHIELD TIED TO INDUCTOR

ON TERM

TRANS
ARINC SPECIFICATION 429, PART 1 - Page 138

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

Amplitude Volts FIGURE a-(vi)

Time (microseconds)

TRANSMITTER LEAD A TO LEAD B VOLTAGE

 ARINC SPECIFICATION 429, PART 1 - Page 139

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(vii)

Amplitude Volts

Time (microseconds)

TRANSMITTER OUTPUT VOLTAGE

Amplitude Volts

Time (microseconds)

OPEN CIRCUIT VOLTAGE AT RECEIVER ONE

 ARINC SPECIFICATION 429, PART 1 - Page 140

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(viii)

# Load # Load
Configuration
Rec 1 Rec 2
1 1 1
2 1 10
3 10 1
4 10 10

RECEIVER
10 FEET TWO

TRANSMITTER RECEIVER
One
200 FEET 85 FEET

1 4 1
(3.05m)
2 BUSLIN 5 5 2
REC 2
3 6

1 SHIELD 5 2

* *
1 1 4 1 4 1 4 1 4 1
TRANS
(61m) (10m) (10m) (6m) REC 1
2 2 5 2 5 2 5 2 5 2
BUSLIN 1 Node BUSLIN 2 BUSLIN 3 BUSLIN 4
3 6 1 3 6 3 6 3 6

1 SHIELD 1 2 1 SHIELD 2 2 1 SHIELD 3 2 1 SHIELD 4 2

* * * *
1 2 3 4 5 6 7 8 9

16.5k
40pf
ALL
1
.1 L’s
3 5 1 .05 µ h 6k 50pf
.01 40
2

4 6 TERM
2
.01 40 * SHIELD TIED TO INDUCTOR 15k
45pf
.1 ON TERM BLOCK

TRANS REC 1
 ARINC SPECIFICATION 429, PART 1 - Page 141

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(ix)
Amplitude Volts

CONFIGURATION 1
Time (microseconds)

TRANSMITTER OUTPUT VOLTAGE

CONFIGURATION 1
Amplitude Volts

Time (microseconds)

VOLTAGE AT FIRST NODE

ARINC SPECIFICATION 429, PART 1 - Page 142

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(x)

CONFIGURATION 1
Amplitude Volts

Time (microseconds)

VOLTAGE AT RECEIVER ONE

CONFIGURATION 1
Amplitude Volts

Time (microseconds)

VOLTAGE AT RECEIVER TWO

 ARINC SPECIFICATION 429, PART 1 - Page 143

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(xi)

CONFIGURATION 2
Amplitude Volts

Time (microseconds)

TRANSMITTER OUTPUT VOLTAGE

CONFIGURATION 2
Amplitude Volts

Time (microseconds)

VOLTAGE AT FIRST NODE

ARINC SPECIFICATION 429, PART 1 - Page 144

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(xii)

CONFIGURATION 2
Amplitude Volts

Time (microseconds)

VOLTAGE AT RECEIVER ONE

CONFIGURATION 2
Amplitude Volts

Time (microseconds)

VOLTAGE AT RECEICER TWO

 ARINC SPECIFICATION 429, PART 1 - Page 145

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(xiii)

CONFIGURATION 3
Amplitude Volts

Time (microseconds)

TRANSMITTER OUTPUT VOLTAGE

CONFIGURATION 3
Amplitude Volts

Time (microseconds)

VOLTAGE AT FIRST NODE

ARINC SPECIFICATION 429, PART 1 - Page 146

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(xiv)

CONFIGURATION 3
Amplitude Volts

Time (microseconds)

VOLTAGE AT RECEIVER ONE

CONFIGURATION 3
Amplitude Volts

Time (microseconds)

VOLTAGE AT RECEIVER TWO

 ARINC SPECIFICATION 429, PART 1 - Page 147

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(xv)

CONFIGURATION 4
Amplitude Volts

Time (microseconds)

TRANSMITTER OUTPUT VOLTAGE

CONFIGURATION 4
Amplitude Volts

Time (microseconds)

VOLTAGE AT FIRST NODE

ARINC SPECIFICATION 429, PART 1 - Page 148

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(xvi)

CONFIGURATION 4
Amplitude Volts

Time (microseconds)

VOLTAGE AT RECEIVER ONE

CONFIGURATION 4
Amplitude Volts

Time (microseconds)

VOLTAGE AT RECEIVER TWO

 ARINC SPECIFICATION 429, PART 1 - Page 149

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(xvii)

REC REC
TWO THREE
10 FEET 50 FEET
TRANSMITTER

150 FEET 50 FEET 50 FEET 10 FEET

85 FEET

REC 3
1
REC 2

10 LOAD
LOADS

2
1
2
1

*
5
6
4
*

2
5
6
4

SHIELD 6
BUSLIN 6
SHIELD 5
BUSLIN 5

(15m)
(3.05m)

1
1

2
3

*
1
1

2
3

TRANS 1 1 4 1 4 1 4 1 4 1 REC 1
(26m) (46m) (15m) (3.05m)
2
1
2 2 5 2 5 2 5 5 2
BUSLIN 1 BUSLIN 2 NODE BUSLIN 3 NODE LOAD
3 6
NODE
3 6 2 3 6 3 3 BUSLIN 4 6
1

1 SHIELD SHIELD SHIELD SHIELD

2 11 2 1 2 1 2
1 2 3 4
* * * * * * * *
1 2 3 4 5 6 7 8 9

40pf 16.5k
ALL
1
.1 L’S
3 5 1 .05 µ h 6k 50pf
.01 40
2

4 6 TERM
2
.01 40 * SHIELD TIED TO INDUCTOR 45pf 15k
.1
ON TERM BLOCK

TRANS REC 1
ARINC SPECIFICATION 429, PART 1 - Page 150

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(xviii)
Amplitude Volts

Time (microseconds)

TRANSMITTER OUTPUT VOLTAGE

Amplitude Volts

Time (microseconds)
Time (microseconds)

VOLTAGE AT FIRST NODE

 ARINC SPECIFICATION 429, PART 1 - Page 151

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS
Amplitude Volts FIGURE a-(xix)

Time (microseconds)

VOLTAGE AT RECEIVER ONE

Amplitude volts

Time (microseconds)

VOLTAGE AT RECEIVER TWO

ARINC SPECIFICATION 429, PART 1 - Page 152

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(xx)
Amplitude Volts

Time (microseconds)

VOLTAGE AT SECOND NODE

Amplitude volts

Time (microseconds)

VOLTAGE AT RECEIVER THREE

 ARINC SPECIFICATION 429, PART 1 - Page 153

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(xxi)
Amplitude Volts

Time (microseconds)

VOLTAGE AT THREE NODE

 REC REC REC
TWO THREE FOUR

ARINC SPECIFICATION 429, PART 1 - Page 154

1 LOAD
REC 4
1 LOAD
5 FEET 20 FEET 20 FEET

REC 3
1 LOAD
REC 2

LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

TRANSMITTER
5 FEET 85 FEET 20 FEET

2
20FEET

1
2
1
2
1

*
5
4

2
*
4
5
6
*

2
6
5
4

SHIELD
BUSLIN
2

(6.1m)
BUSLIN

SHIELD

7
(6.1m)
SHIELD
BUSLIN

7
(1.5m)

6
5

1
1

2
3

*
1
1

2
3

*
1

1
2

*
3

TRANS 1 1 (1.5m) 4 1 (26m) 4 1 (6.1m) 4 1 (6.1m) 4 1 REC 1

2 2 5 2 5 2 5 2 5 2
1
BUSLIN BUSLIN BUSLIN BUSLIN
NODE NODE LOAD

FIGURE a-(xxii)
NODE
3 1 6 3 2 6 2 3 3 6 3 3 4

APPENDIX A
1 6

SHIELD SHIELD SHIELD SHIELD

1 2 1 2 1 2 1 2
1 2 3 4
* * * * * * * *
1 2 3 4 5 6 7 8 9

40pf 16.5k
ALL
1
.1 L’S
3 5 1 .05 µ h 6k 50pf
.01 40
2
4 6 TERM
2
.01 40
* SHIELD TIED TO INDUCTOR
15k
.1 ON TERM BLOCK 45pf

TRANS REC 1
 ARINC SPECIFICATION 429, PART 1 - Page 155

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS
Amplitude Volts FIGURE a-(xxiii)

Time (microseconds)

TRANSMITTER OUTPUT VOLTAGE

Amplitude Volts

Time (microseconds)

VOLTAGE AT FIRST NODE

ARINC SPECIFICATION 429, PART 1 - Page 156

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

Amplitude Volts FIGURE a-(xxiv)

Time (microseconds)

VOLTAGE AT RECEIVER ONE

Amplitude volts

Time (microseconds)

VOLTAGE AT RECEIVER TWO

 ARINC SPECIFICATION 429, PART 1 - Page 157

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(xxv)
Amplitude Volts

Time (microseconds)

VOLTAGE AT SECOND NODE

Amplitude volts

Time (microseconds)

VOLTAGE AT RECEIVER THREE

ARINC SPECIFICATION 429, PART 1 - Page 158

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a(xxvi)
Amplitude Volts

Time (microseconds)

VOLTAGE AT NODE THREE

Amplitude Volts

Time (microseconds)

VOLTAGE AT RECEIVER FOUR

 ARINC SPECIFICATION 429, PART 1 - Page 159

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(xxvii)

REC
5 FEET TWO

TRANSMITTER
REC
328 164 8
5 FEET ONE OR 100
FEET FEET FEET

REC 2
1 (1.5m) 4 1

2 BUSLIN 5 2
3 5 6 1 LOAD

SHIELD
1 2
5

* *
1 1 1 1 1 4 1
REC 1
4 4 4
TRANS (1.5m) (100m) (50m) (2m)
1 LOAD,
2 2 5 2 5 2 5 2 5 2 @ 100
BUSLIN 1 Node BUSLIN 2 Node BUSLIN 3 Node BUSLIN 4
3 6 1 3 6 2 3 6 3 3 6

1
SHIELD 2 SHIELD 2 1 SHIELD 2 1 SHIELD
1 2
1 2 3 4
* * * * * * * *
1 2 3 4 5 6 7 8 9

40pf 16.5k
ALL
1
.1 L’s
3 5 1 .05 µh 6k 50pf
.01 40
2

4 6 TERM
2
* SHIELD TIED TO INDUCTOR
.01 40
15k
.1 ON TERM BLOCK 45pf

Trans
ARINC SPECIFICATION 429, PART 1 - Page 160

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(xxviii)
Amplitude Volts

Time (microseconds)

TRANSMITTER OUTPUT VOLTAGE

Amplitude Volts

Time (microseconds)

VOLTAGE AT FIRST NODE

 ARINC SPECIFICATION 429, PART 1 - Page 161

APPENDIX A
LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

FIGURE a-(xxix)
Amplitude volts

Time (microseconds)

VOLTAGE AT RECEIVER ONE

Amplitude Volts

Time (microseconds)

VOLTAGE AT RECEIVER TWO

ARINC SPECIFICATION 429, PART 1 - Page 162
APPENDIX B
AN APPROACH TO A HYBRID BROADCAST-COMMAND/RESPONSE DATA BUS ARCHITECTURE

A2-1.0 Introduction
During the time that the broadcast approach to digital information transfer became established in the air transport industry,
the military aviation community adopted a command/response time division multiplex technique as its standard. In this
approach, all aircraft systems needing to exchange digital data are connected to a common bus and a dedicated “bus
controller” determines which of them may output data on to the bus at any given time. MIL STD 1553 was written to
describe this system.
The airlines considered adopting MIL STD 1553, or something like it, for use on post-1980 new civil aircraft types but found
the multiplex technique to be inappropriate for such applications. In civil avionics systems, data typically flows from a given
source to a single sink, or group of sinks which may be connected in a parallel, and these sinks are typically not themselves
data sources. Thus there is no need for the data transfer system to provide the capability for every unit of every avionics
system to both talk and listen to every other unit. The broadcast technique is adequate, and thus the airlines elected to stay
with it for their new DITS.

Another development in this same time frame has been the increased use by the military, particularly in transport aircraft, of
avionics equipment designed originally for the airlines. This trend may be expected to continue and so give rise to the need
to interface equipment providing Mark 33 DITS I/0 capability with a MIL STD 1553A data bus system. The material in this
Appendix prepared by the Information Engineering Division of the USAF Directorate of Avionics Engineering describes one
way of doing this, using a data exchange buffer to compensate for the electrical, logic and timing differences between the two
systems.

A2-2.0 Suggested Mark 33 DITS/MIL STD 1553A Interface

The following is a proposed method for interfacing an avionic system employing sensors designed for any combination of
ARINC Mark 33 DITS and MIL-STD-1553A. This method minimizes message related differences and compensates for
electrical, logic and timing differences in a Data Exchange Buffer (DEB).

In a hybrid system such as shown in Figure b-(i), a signal may originate in either a DITS type subsystem or a 1553A
subsystem and may be destined for either type of terminal. DITS data received by a DEB is momentarily stored and then
retransmitted, complete with label, to the 1553A bus controller. The bus controller determines the intended destinations from
the label and look-up table. For DITS destinations, the word is retransmitted, as received, to the appropriate DEB. For
1553A destinations, the data may be retransmitted as received or reformatted, as required by the destination subsystem.
Reformatting could involve removal of label and reversing of bit order (MSB vs LSB first). Figure b-(ii) shows the handling
of a word originating in the destined for DITS terminals.
Upon arrival at the appropriate destination DEB, the data is momentarily stored and then retransmitted in DITS format,
complete with label, to the destination subsystem. If all labels in the system are unique, all receivers in all subsystems
associated with a DEB may be connected in parallel. Only the data with the proper label will be recognized by each receiver.
If labels are not unique, the DEB must have separate transmitters to transmit the data with identical labels. The desired
transmitter could be specified in the 1553A subaddress field.
The retransmission of the data by the DEB allows inherently for different electrical and logical characteristics. The storage of
the data allows for simultaneous reception from multiple receivers (DITS and 1553A) and retransmission when the desired
bus is available. The much higher speed of 1553A would make retransmission delays small.
Figure b-(iii) illustrates the organization of a minimum system. It consists of multiple DITS receivers dumping received data
into a first-in first-out (FIFO) stack, available as single LSI chips. The received data is temporarily stored and then
retransmitted by the 1553A terminal. Data received via 1553A is dumped into another FIFO for retransmission by a DITS
transmitter. The hardware consists only of DITS receivers, the 1553A terminal, the DITS transmitter, and as many FIFO’s as
are required. Hand-shaking signals available on the FIFO’s eliminate almost all supporting SSI chips. This entire system
would probably fit on one full ATR card or less.
Figure b-(iv) illustrates possible organization for a more sophisticated DEB. It consists of an many DITS transmitters and
receivers as necessary, a single (internally redundant) 1553A remote terminal, a buffer memory, a controller
(microprocessor), and a program for the controller contained in ROM. Whenever a complete, valid word is available at a
receiver, the controller is notified. When the parallel data bus becomes available, the word is transferred to memory. When
the desired transmitter (DITS or 1553A) becomes available, the data word is routed from memory to the transmitter. The low
rate of DITS terminals (minimum 320 microsec/word) would result in a very low loading of the parallel bus and controller.
The speed of the 1553A terminal might necessitate a direct memory access arrangement. The controller, the program
memory, the buffer memory and a dual 1553A remote terminal would probably fit on one one-sided 3/4 ATR card. The
required ARINC transmitters and receivers would probably fit on another card.

This method represents one way of constructing a hybrid system. The retransmission of the label with the data greatly
reduces the intelligence required by the DEB but increases bus loading. A more intelligent DEB, perhaps located in the bus
controller, could achieve much higher efficiencies.
 ARINC SPECIFICATION 429, PART 1 - Page 163
APPENDIX B
AN APPROACH TO A HYBRID BROADCAST-COMMAND/RESPONSE DATA BUS ARCHITECTURE
FIGURE b-(i)
HYBRID BUS ARCHITECTURE
SUBSYSTEM
R
SUBSYSTEM

OLD
NEW

R
RT

T
R
RT

R
T

SUBSYSTEM
R

OLD
R
CONTROLLER

T
BUS

EXCHANGE
BUFFER
DATA
DUAL 1553A BUS

BUSES
DITS
SUBSYSTEM
NEW

RT

SUBSYSTEM
T

OLD
RT

R
T
 ARINC SPECIFICATION 429, PART 1 - Page 164
AN APPROACH TO A HYBRID BROADCAST-COMMAND/RESPONSE DATA BUS ARCHITECTURE
Received DITS word (32bits) LABEL

MESSAGE WORD FORMATTING

Data stored in buffer (2x16 bits) LABEL

FIGURE b-(ii)

APPENDIX B
Transmitted via 1553A S LABEL S

Data stored in buffer (2x16 bits) LABEL

Retransmitted via DITS (32 bits)

LABEL
 ARINC SPECIFICATION 429, PART 1 - Page 165
APPENDIX B
AN APPROACH TO A HYBRID BROADCAST-COMMAND/RESPONSE DATA BUS ARCHITECTURE
FIGURE b-(iii)
MINIMUM DATA EXCHANGE BUFFER
1553 A
BUS
TERMINAL
1553A
FIFO
RECEIVER
DITS

XMTR
DITS
RECEIVER
DITS

DITS BUS 3
DITS BUS 1

DITS BUS 2
ARINC SPECIFICATION 429, PART 1 - Page 166
APPENDIX B
AN APPROACH TO A HYBRID BROADCAST-COMMAND/RESPONSE DATA BUS ARCHITECTURE
FIGURE b-(iv)
PROGRAMMABLE DATA EXCHANGE BUFFER
TERMINAL
1553A
MEMORY
BUFFER

Internal Parrallel Data Bus

Address

XMTR
DITS
PROGRAM

CONTROLLER

RECEIVER
DITS
RECEIVER
DITS
 Collins Avionics Divisions
400 Collins Road, NE Rockwell Signal Degradation
Cedar Rapids, Iowa, 52406
(319) 395-1000 International • Modification Signal to Noise Ratio (MSN)
Cable COLINRAD Cedar Rapids • Static Accuracy

Spectral Characteristics
4 May 1979 • Update Interval
• Transmit Interval
• Pre-sampling Bandwidth Limit
A Control System View of
ARINC 429 Bus Specifications
By The following discussion of these characteristics should aid the reader in

DIGITAL SYSTEMS GUIDANCE (PART 1)

T. G. Sharpe and G. E. Forquer understanding their purpose and assessing their adequacy. It is recognized that
some changes may necessarily take place as the industry completes its digital
interfacing standardization task.
I. Introduction and Summary

APPENDIX C
The discussion below summarizes concepts that have grown out of an in-house
effort to determine what parameter characteristics Collins feels should be II. Stability Consideration
included in the data standards tables of ARINC Bus Specification 429 (DITS).
The DITS specification seems to be evolving as more than merely a digital bus
There is nothing uniquely digital in this area. Here our concern is with those
description since in many ways it is taking on the characteristics of a system
characteristics that are most often used in linear system stability analysis – namely
interface specification. This raises philosophical questions concerning those
gain and phase characteristics. We recognize at the outset that all sensor systems
characteristics, which should appear in the individual equipment specifications
are not 100% linear but this does not prevent us from defining a linear model of
versus those which should appear in “429”. The authors cannot resolve such

ARINC SPECIFICATION 429, PART 1 – Page 167

partitioning questions. Hopefully we can contribute, as outlined below, to an
understanding of what information is required by control systems designers to
achieve an acceptable system performance. The detailed discussion in this paper
evolves a set of terms (outlined below) which are usable in a specification. Which
of these terms appear in the individual equipment specifications and which appear
in “429” remains to be determined.
At the present time, it is suggested that control system designers interfacing with
digitally bused data should be concerned with three prime areas: stability
considerations, signal degradation, and spectral characteristics. Without these
elements of information, thorough analysis of system performance will not be
possible.
The following eight parameter characteristics should prove adequate for the
minimal control of interfacing considerations.
Stability
• Control Band
• Magnitude Limits
• Phase Limits
sufficient quality to support stability analyses. It is useful to consider here that
generally the sensor will be wideband relative to the band of frequencies of
interest to the control system. This is necessary from a stability point of view
since the converse (that is, signals narrowband relative to the control band) would
introduce excessive phase lag in the control band. Thus far we have implicitly
considered both bandpass and lowpass centered at zero frequency. For simplicity,
however, the discussion below will assume low pass sensor characteristics but the
ideas apply generally. Figure 1 illustrates an assumed sensor characteristic.
Gain and Phase Constraints
Note that prime concerns are that the gain remain essentially constant through the
control band and that the phase be bounded by a linear characteristic through the
control band. From a control law stability point of view, we are not concerned
with what happens at frequencies above the control band because these are
beyond the range where the data is being used by the control system. If we
consider open loop Bode plots broken at the sensor output, the control band as
used above should be wide enough to include the phase crossover as well as the
gain crossover. The phase and gain characteristics provide information about
phase and gain margin degradation. For most sensors the gain crossover in
 ARINC SPECIFICATION 429, PART 1 – Page 168
typical control laws is known approximately. Phase crossover is not as easily
determined. A reasonable first cut would be to define the control band as
approximately ten times the open loop crossover frequency with the expectation
that beyond this range control law gain is low enough to prevent gain margin
problems. However, some sensors may have trouble holding a tight gain (and
phase) spec over this wide a bandwidth. Possibly in these cases a loosening of the
spec between open loop crossover and ten times open loop crossover may be
required. With this kind of specification a simple transport delay in combination
with a gain change can be used for stability analysis or, for slightly more complex
cases, simple transfer functions can be used to approximately fit the spec. The
important point here is not to constrain the sensor designer to a first order or

DIGITAL SYSTEMS GUIDANCE (PART 1)

second order or any specific implementation, but to rather bound in a simple yet
usable sense the stability degradation the sensor can introduce. The important
stability characteristics are defined concisely below.

APPENDIX C
Control Band – That band of frequencies over which magnitude and phase
characteristics of the sensor are important to the control system stability.

• Magnitude Constraint – The bounds (envelope) on the permissible gain

variation in a linear frequency response sense that are permissible over the
control band.

• Phase Constraint – The bounds (envelope) on the permissible phase variation

in a linear frequency response sense that are permissible over the control
band.
 Potential Measurement Technique

These quantities could be measured by providing a sinusoidal input stimuli at

selected frequencies in the control band using a mid-range amplitude. At each
frequency the output component of interest (assuming some distortion) will be the
output component whose frequency corresponds to the input frequency. The SENSOR
phase and amplitude of this component of this component relative to the forcing
Signal Dependent
function will provide the magnitude and phase information. In the terminology of Process Noise
nonlinear system analysis, this procedure yields and empirically derived Noise
Sensor
Internally Sensor
describing function for the sensor over the control band. If amplitude dependent Input
Ouput
Generated Noise
nonlinearities are severe, more than one amplitude of forcing function may have f( )
+ +
to be used with the procedure repeated at each amplitude. Signal
+ + + Measurement
+ + + Error
+ -

DIGITAL SYSTEMS GUIDANCE (PART 1)

III. Signal Degradation
Installation
Noise
In this area we are concerned with what the sensor may have done to degrade the
signal. The thrust here is not stability but performance. Figure 2 presents a view
of sensor and signal characteristics that is useful in this context. In Figure 2 some

APPENDIX C
important sources of signal degradation are illustrated. The term “noise” is used
somewhat loosely in Figure 2 to denote degradation sources. Process noise and
installation noise are inherent in the signal impinging on the sensor – the former
being things such as gust noise and beam noise and the latter being effects such as

ARINC SPECIFICATION 429, PART 1 – Page 169

EMI, mounting errors, etc. Within the sensor itself there is internally generated
noise such as shot noise from resistors, EMI from digital buses, etc. that is
independent of the input signal. In a radio receiver this is the kind of noise that is
Figure 2. Sensor and Signal Characteristic
measured at the output when the input is shorted. Note that this “noise” can also
include bias and drift effects. If there is a digital sampling process in the sensor, and Measurement Noise
some aliasing of the input signal spectrum will occur. This aliased energy may
also be regarded as noise.

The other inherent sensor degradation is more difficult to deal with, however, for
it is signal dependent. A familiar analog example is input amplitude dependent
characteristics such as saturation effects that only become significant above
certain input amplitudes. Another is nonlinearities that produce harmonic
distortion under sine wave excitation as shown in the example below.
 ARINC SPECIFICATION 429, PART 1 – Page 170
Harmonic Distortion
To evaluate the spectral characteristics of measurement error will require tests
which force the system with noise type inputs. Exponentially correlated noise of
Consider square law distortion in an otherwise linear sensor. Let the sensor specified variance and correlation time (or bandwidth) should be sufficient in
output be most cases. If a sensor is known to be susceptible to a specific type of noise,
however, that noise should be included in the test. Often it will be useful to
y(t) = x(t) + kx(t)² separate out the low frequency or d-c components of measurement error since
these may be more tolerable in some applications than dynamic errors. A set of
tests that will measure these characteristics is described below.
Where x(t) is the sensor input and let x(t) = sinwt. Then

y(t) = sinwt + ksin²wt Modified Signal to Noise Ratio (MSN)

k k Force the sensor with random noise of specified rms value (σ) and correlation

DIGITAL SYSTEMS GUIDANCE (PART 1)

" time (τ). Determine the power spectral density (PSD) of the input signal to the
y(t) = sinwt ± 2 2
cos2wt
sensor. Determine the PSD of the measurement error. Plot the two PSD’s on a
common plot as shown in Figure 3. Define a modified signal to noise ratio
(which will be a function of frequency) as the square root of noise ratio at each
Note that d.c. and second harmonic components as well as the forcing frequency
frequency of signal PSD amplitude to measurement error PSD. Note in the
appear at the output. In digital systems a similar effect occurs when multiple rates
example shown in Figure 3 there is a bulge in the measurement error around zero

APPENDIX C
are introduced, such as signals being received at one rate from a digital bus and
frequency. This effect would indicate d-c bias and possibly low frequency bias
being used at a different rate by a software program. If the analog signals
drift from the sensor. This effect may or may not be important depending on
originally sampled and put on the bus were sinusoidal at one frequency then, in
whether the application permits washing out low frequency components, e.g. in a
general, frequency components less than and greater than the input frequency (as
complementary filter. In the range of frequencies where accurate sensor response
well as the input frequency) appear after the second sampler. The amplitude and
is required, it is suggested that appropriate values for the modified signal to noise
number of these spurious outputs is a function of the two sampling rates as well as
(MSN) will be 100 to 1000. Roughly, these numbers correspond to noise power
the input frequency. The net effect of all such internal sensor effects is
being 1% to .1% of signal power at each frequency or noise being 40 to 60 db
observable by subtracting sensor input from sensor output to yield measurement
down from signal. The relationship between MSD and ordinary signal to noise
error as shown in Figure 2.
can be understood by assuming both signal and noise PSD’s are flat over a band
of frequencies ∆w as shown in Figure 3. Let the value of the signal PSD in this
Measurement Error
band be So, then rms signal power in the band ∆w is given by So*w. Similarly,
rms error power is given by Po*w . Therefore conventional signal to noise over the
The involved nature of what can happen to the signal within the sensor as shown
band w is given by . RequiringSo that this signal to noise be 100 is equivalent to
in Figure 2 is the source of ambiguity in conventional “accuracy” specs. Since Po
requiring that noise power be 1% of signal power over this band. Carrying this
measurement noise can be dependent on input amplitude as well as spectral
back to the MSN implies that MSN (w) = = 100 Sover
o the band ∆w. The
characteristics, it is not possible to specify it with a single and simple metric. It Po
above also represents the motivation for considering square root of the ratio than
should also be apparent that measurement error must be addressed statistically
the ratio directly.
since a significant portion of the input, process noise, is only describable as a
random process.1 Technically the input signal is also in general a random
processes influenced by such things as the gust striking the aircraft. Gusts also Amplitude Dependent Nonlinearities
can only be described as random processes.
The approach described above tests for input frequency dependent degradations by
1
Recognizing that a complete description of a random process includes not only providing a realistic input spectrum. It should be realized that if there are
probability distributions but also spectral characteristics.
amplitude dependent degradations, the MSN analysis will yield different answers
depending on the rms value of the input noise. It is suggested that the MSN
measurement be done with worst case input noise, i.e., largest rms and bandwidth
that will be encountered. In some cases alternate MSN specs for different flight
regimes may be appropriate.
In many cases a more explicit presentation of the amplitude dependent non-
linearities may be desirable. A good example here is localizer receiver linearity,
specified as being linear within a given percentage up to .155 DDM, a larger
percentage from .155 to .310 DDM and not decreasing between .310 and .400
DDM. Such a specification is important in defining localizer capture laws, where
one can begin “using” the signal crudely before it is linear or precisely accurate. It
should be noted that this is a slightly different use of sensor data than for precise
state control, i.e. the control is carrying the system to a prescribed state rather
• Static Accuracy – A measure of the amplitude dependent
characteristics of sensor errors defined as the difference between
input and output signals after all transients have settled.
Potential Measurement Technique
Modified Signal to Noise (MSN) determination requires assuming a random
process model for the signal impinging on the sensor. Normally an exponentially
correlated signal with specified variance will be sufficient. Empirically
determined power spectral densities (using discrete Fourier Transform
techniques) will need to be measured for input signal as well as measurement
error. Static accuracy measurement was described above.
IV. Spectral Characteristics

DIGITAL SYSTEMS GUIDANCE (PART 1)

than maintaining it at a prescribed state in the presence of noise. Normally the In this area the digital nature of the system interface must be faced squarely. The
latter operation will require more accurate information from the sensor. The control system designer cannot alter the signal degradation introduced by
amplitude dependent degradations should be measured statically -- that is, one
should provide a test input at specified amplitude, allow transients to settle, and
measure the output value.

APPENDIX C
The important signal degradation terms are defined concisely below. Only the

ARINC SPECIFICATION 429, PART 1 - Page 171

last two are proposed as parameter characteristics--the first three being definitions
to clarify the last two. Signal Power Spectral
Density
( SPSD(w) )
• Measurement Error – The difference between the signal impinging
on the sensor and the output representation of that signal by the So
sensor expressed in consistent units. Measurement
A Error Power
M Spectral Density
• Signal PSD (SPSD) – The power spectral density of the signal P ( MEPSD(w) )
impinging on the sensor. L (rms = s ∆w )
0

I
• Measurement Error PSD (MEPSD) – The power spectral density of T
measurement error introduced by the sensor. U
D
E
• Modified Signal to Noise Ratio – A measure primarily of the
spectral characteristics of sensor errors defined as the square root of Po
 rms =
the ratio of SPSD and MEPSD at each frequency in the control 
p ∆w 
0

band. frequency
w w
SPSD (w)
i.e., MSN(w) = MEPSD (w) MSN (w) =
SPSD (w)
MEPSD (w)

MSN ∆ Modified Signal to Noise Ratio

Fig re 3 Modified Signal to Noise Ratio

the sensor whether it be due to nonlinearities, aliasing, noise, etc. He has great τ2w2+1
potential, however, for making matters worse if he is not alert to potential aliasing
Adequate roll off chracteristic of the digitally bused data reduces the aliasing
problems that he may introduce. To analyze aliasing precisely he would need a
problem of the second sampler if the second sampling is properly performed.
precise definition of the spectrum of each signal being received on the digital bus
However, not only this spectrum but also the frequency F1 enters into the aliasing
including the update interval for each signal. A more practical approach is to
in F2 (s), therefore, it is desirable also to carefully specify F1. This will be
place an upper bound on the received signal spectrum and then ensure
accomplished through the update interval. Assuming F2 is somewhat fixed by
downstream performance is adequate using this bound as the signal spectrum.
computer speed and loading considerations, aliasing can be minimized for a given
These ideas are made more precise below.
input spectrum by making F1 as high relative to F2 as possible.
Multirate Sampling
The important spectral characteristic terms are defined concisely below.
A simple model for signals received from a bus and used in a digital processor is

DIGITAL SYSTEMS GUIDANCE (PART 1)

• Update Interval – The cyclic time interval, as measured at the DITS bus
shown in Figure 4. We note that the spectrum of the signal on the bus, F1 (s), is an
interface, between transmissions of new freshly sensed and converted/derived
infinitely replicated version of the analog input spectrum with replicas spaced by
values of the parameter.
the input sampling frequency F1. We cannot, therefore, speak of the bandwidth
of F1 (s) strictly. What we mean here is that a bound is required on each copy in
F1 (s). Deriving the spectrum of the signal F2 (s) is beyond the scope of this Sampler Sampler

APPENDIX C
discussion but a technique has been developed that will yield this spectrum, F2 (s),
Analog F(S) F (S) Digital F 2 (S)
given the quantities F1, F2, and the shape of the repeated spectrum of F (s) in F1 Quantity
1
Register
(s). There is considerable spreading of signal energy in this process with f1 f2
considerable “aliasing” potential even if the quantity fc in Figure 4 is much less
than the Nyquist frequency ( f21 , f22 ) for both F1 and F2. The “aliasing” in Software
Bused

ARINC SPECIFICATION 429, PART 1 - Page 172

the spectrum F2 (s) occurs because the second sampler is not operating on a Fetch
Signal
properly band limited function (see Figure 4) due to the “infinite replica” nature F(S) A n a l o g
Input
of the spectrum F2 (s). Spectrum

Deterministic Versus Random Signals

S

The discussion above did not specify whether the original analog quantity was a
deterministic signal or a random process. For deterministic cases we deal with
the Fourier transforms of the signals involved. However, as pointed out in
Section III the signals of interest are really describable only in terms of random
processes. For this case the development must proceed in terms of power spectral -2f 1 -f 1 -f c fc f1 2f 1 S
density of the signals involved. Figure 5 then illustrates the bound on bused
signal PSD that is envisioned. Recall that white noise through a lowpass filter
yields a PSD that rolls off at 40 db/decade as shown below. Figure 4 Analysis of Multirate Sampling

White Noise Input PSD: U(S) = A - ∞ < w < + ∞

Filter Transfer Function: T (jw) = 1
Jτw+1
Output PSD: Y (S) = T(S)T*(S)U(S)
Y(w) = A
 ARINC SPECIFICATION 429, PART 1 - Page 173
• Transmit Interval – The cyclic time interval, as measured at the DITS bus
interface, between transmissions of the parameter. Transmit Interval ≤
Update Interval.

• Pre-sampling Bandwidth Limit – That bandwidth for a first order lag that will
upper bound the spectral characteristics of the signal of the signal on the bus.

Power

DIGITAL SYSTEMS GUIDANCE (PART 1)

Spectral
Density
40 db/decade

APPENDIX C
Frequency
Pre-Sampling
Bandwidth w
Limit

Note: Periodic Function -

Only Positive Half
of Zero Centered
Component Shown
(see Figure 4)

Figure 5 PSD Bound on Bused Signal

 ARINC SPECIFICATION 429, PART 1 - Page 174
Attachment to
BOEING COMMERCIAL AIRPLANE COMPANY P.O. Box 3707
SYST-B-8764-20-075
Seattle, Washington 98124
M/S 47-09
A Division of The Boeing Company
DESIGN PARAMETERS FOR DIGITAL AVIONIC SYSTEMS
Prepared by
May 11, 1979 Boeing Commercial Airplane Company
SYST-B8713-79-209 REVISION A

Mr. B. R. Climie, Chairman Summary

DIGITAL SYSTEMS GUIDANCE (PART 2)

Airlines Electronic Engineering Committee
This paper explains the necessity for defining presampling filter
Aeronautical Radio, Inc. characteristics, transport delays and minimum update rates for digital and
2551 Riva Road noise characteristics are discussed. A design procedure for selecting the
Annapolis, Maryland 21401 required filter characteristic and update rate is presented.

Dear Rick: Introduction

The enclosed paper is a revised version of “Design Parameters for Digital
Avionic Systems,” which was originally circulated with AEEC letter 79-
022/SAI-99. The revision addresses the topic of aliasing which could
occur when reducing the sampling rate of a digitally encoded signal. This
topic was discussed at the DITS working group meeting held on April 18
and 19.
Sincerely
AIR TRAFFIC CONTROL
AND ELECTRONIC SYSTEMS
APPENDIX D
The new generation of commercial aircraft will use digital technology to
implement many functions, which were traditionally performed with
analog hardware. These functions include inner and outer servo loops for
aircraft control and guidance, processing and filtering signals from
navigation and other sensors, and filtering of data prior to its display on
cockpit instruments. Digital technology will also replace the majority of
the formerly analog communication paths between systems, sensors,
instruments and actuators.
A basic property of these and other digital systems is that they only
process or transfer values of data from discrete points in time. The
contrast between the discrete time nature of a digital system and the
continuous time nature of an analog system is shown in Figure 1. Analog
systems are said to operate in the continuous time domain while digital
systems are said to operate in the discrete time domain.

In order for discrete time digital systems to be used to process or transfer

the inherently continuous time data from real world physical systems,
A. F. Norwood, Chief
samples of the continuous data must be taken at periodic intervals. These
samples from discrete points in time can then be used as the input to the
AFN: discrete time digital system. It is intuitively obvious that the interval
Enclosure between samples affects the accuracy with which the continuous time data
is represented by the discrete samples. It is also obvious that rapidly
varying signals should be sampled more often than slowly varying signals
in order to maintain an adequate representation of the continuous analog
data. Selection of a proper sampling rate for each signal is a design task
unique to digital systems. An understanding of the Sampling Theorem is
necessary in order to make the proper trade offs between sampling rate,
signal-to-noise ratio, signal delay, and system complexity.
B
BOOE
EIIN
NGG
The Sampling Theorem
The Sampling Theorem states that a signal which contains no frequency
components higher than fo Hertz can be exactly recovered from a set of its
samples if the samples are spaced no further apart than ½ fo seconds. This
is equivalent to requiring that the sampling frequency be greater than
twice the highest frequency component of the signal.
The reason for this requirement can be shown by examing the frequency
spectrum of the sampler output. Modeling the sampling operation as the
multiplication of the input signal by an impulse train as shown in Figure 2
allows the sampler output spectrum to be computed from a Fourier
Transform identity. The required identity states that time domain
multiplication is equivalent to frequency domain convolution. Therefore,
the output spectrum is found by convolving the input spectrum with the
spectrum of the impulse train. This relationship is shown in Figure 3.
The convolution operation has the effect of reproducing the spectrum of
the input signal about zero frequency and at all harmonics of the sampling
frequency. If the sampling frequency, 1/Ts, is greater than twice fo the
spectral components centered about the sampling frequency and its
harmonics will not overlap the spectral component centered about zero
frequency. Therefore, the spectral component centered about zero, which
is identical to the input spectrum, can be obtained by passing the sampled
output through a low pass filter with a bandwidth of fo Hz.
Application of the Sampling Theorem to Digital Avionics Systems
The discussion of the Sampling Theorem in the preceding section has
shown that a signal which contains no frequency components higher than
fo Hz. can be exactly represented by a series of samples spaced no further
apart than ½ fo seconds. However, signals, which represent physical
quantities, such as those processed by avionic systems never satisfy the
strict bandwidth limitation requirement stated above. Therefore exact
reproduction of the original signal from its samples is not possible. The
effect of the non-bandlimited nature of signals is to distort the replica
reconstructed from the samples. The shaded area shown in Figure 4
represents typical high frequency signal energy which distorts the low
frequency portion of the signal spectrum. The high frequency portion of
the signal takes on the identity of the lower frequencies, hence the name
“aliasing” for this phenomenon.
Aliasing becomes a greater problem when the signal is corrupted by noise,
which has a wider bandwidth than the signal. When this occurs both
signal energy and noise energy which is beyond one half of the sampling
frequency is aliased into the low frequency portion of the recovered
signal. This effect is shown in Figure 5. The signal-to-noise ratio is
degraded by both noise and signal components which are aliased into the
low frequency portion of the signal spectrum. The effect of aliasing can
be decreased by sampling the incoming signal at a higher rate and/or using
a presampling filter to reduce the bandwidth of the signal prior to
sampling. Neither of these approaches can ever completely eliminate the
effect of aliasing and they each result in some negative impact on the
overall system.
An increase in the sampling rate requires more computations to be done in
a given period of time. This requires more computational resources,
which increases the weight, complexity, and power requirements of the
computer subsystems. The use of a presampling filter to limit the
bandwidth prior to sampling distorts the signal. It also increases the delay
experienced by signals as they propagate through the system. The
increase in delay reduces phase margin if the signal is used in a closed
loop control system. Therefore, more stringent delay requirements must
be placed on other components in the loop if the system phase margin is
to remain constant.
DIGITAL SYSTEMS GUIDANCE (PART 2)
Design Tradeoffs for Digital Avionics Systems
The final choices of sample rate and presampling filter depend upon the
input signal and noise spectra, maximum allowable signal-to-noise ratio
degradation due to aliasing, maximum allowable transport delay, available
APPENDIX D
computational resources, and the bandwidth of the system which uses the
data. A practical way to make these choices is to analyze the system for
various sample rates and filters. This can best be done with the aid of a
computer program which computers the effect of each combination of
sample rate and filter characteristic on the output signal-to-noise ratio for
the defined input signal and noise spectra.
ARINC SPECIFICATION 429, PART 1 - Page 175
The initial computation is to determine the effect of the prefilter on the in-
band signal-to-noise ratio without regard to aliasing effects. A typical
plot of signal-to-noise ratio versus presampling filter bandwidth is shown
in the top curve of Figure 6. This curve forms a baseline against which
signal-to-noise ratio degradation caused by aliasing can be compared.
The signal-to-noise ratio is determined by computing the input signal
power and input noise power, which is passed by the selected prefilter.
This parameter will generally exhibit a peak value at a specific bandwidth.
The signal-to-noise ratio will decrease with increasing bandwidth as more
noise is admitted and decrease with decreasing bandwidth as signal energy
is eliminated.
The filter order is an important design parameter because higher order
filters roll off more rapidly near the cutoff frequency. Therefore higher
order filters admit less noise and signal from beyond the cutoff frequency
than low order filters. Because of this characteristic, high order filters
alias no more noise into the signal than slightly narrower bandwidth low
order filters. However, high order filters delay the signal more than low
order filters.
The ultimate objective of the design task discussed in this paper is to
achieve acceptable system performance with the minimum possible
 ARINC SPECIFICATION 429, PART 1 - Page 176
sampling rate. System performance is adversely affected by large due to aliasing. Signal and noise spectra of the signal to be sampled must
propagation delays and high in-band noise levels. be supplied as an input to the design procedure.

If the maximum allowable propagation delay is given, the minimum Reference: Herman J. Blinchikoff and Anatol I. Zverev, Filtering in the
usable filter bandwidth can be found standard plots of group delay versus Time and Frequency Domains, John Wiley and Sons, New
frequency for the type and order of filter considered. (See for example York.
Reference 1, page 112.) This minimum bandwidth is plotted on Figure 6
as a vertical line. The maximum achievable signal-to-noise ratio is
constrained by the requirement for a presampling filter wide enough to
limit delay to the given value. The intersection of the minimum
bandwidth line with the top curve of Figure 6 gives the maximum Analog
achievable signal-to-noise ratio i.e., the signal-to-noise ratio which would Analog System Analog
be achieved by an unsampled system. Input Output

DIGITAL SYSTEMS GUIDANCE (PART 2)

Sampling rate is chosen by comparing the maximum acceptable
degradation in signal-to-noise ratio to the actual aliasing degradation due Analog Analog
to sampling at the candidate rates. For the example shown in Figure 6, a Input Output
sampling rate of 50Hz would be chosen.
A system interface which meets prescribed limits on signal delay and
maximum noise due to aliasing can be designed using the procedures

APPENDIX D
outlined above. Some systems which use sampled data, such as closed time time
loop control systems, have a bandwidth which is much smaller than that
of the sampling filter. For this reason it is important to verify that the Figure 1(a) Typical Input and Output of Analog System
signal and noise power which is aliased into the frequency band of interest
is well below the inherent noise in that band.

This can be accomplished by constructing a signal and noise power

spectral density plot for the filter and sampling rate chosen. The power
spectral density plot is most easily obtained with the aid of a computer Digital
program. A typical plot of this type is shown in Figure 7. The example Digital Input System Digital Output
power spectral densities in Figure 7 show that the aliased signal and noise (discrete values) (discrete values)
is much lower than the inherent noise level in the frequency range of
interest. If this constraint is not met a different combination of filter and
sampling frequency must be chosen.

In some situations it may be desired to reduce the sampling rate of a Digital

digitally encoded signal. This may be done where wideband digital data Input
is used to drive an instrument or subsystem which responds only to
narrower bandwidth data. Simple deletion of unwanted samples to reduce
the sampling rate can cause aliasing problems similar to those encountered
when sampling an analog signal at an insufficient rate. The aliasing can
be elimination of the unwanted samples. Design of the digital filter is time time
subject to the same set of delay versus aliasing noise tradeoffs as the
design of an analog presampling filter. Figure 1(b) Typical Input and Output of Digital System

Conclusion

The procedures outlined in this paper can be used to choose the

presampling filter and sampling rate required for interfaces to a digital
signal processing or control system. The values are chosen to meet the
constraints of maximum allowable delay and maximum allowable noise
 X Low Pass
Bw = oHz r (t)
r (t) rs(t)

∑
n = −∞
δ (t − nTs )
−
2
T
−
1
−
1 0 1 1 2 f
s T s
2T s 2T s T s
T s

Figure 2 Mathmatical Model of Sampling Process

R (f) Figure 4 Sampler Output Spectrum When Input Signal Bandwidthis

not Limited to One-Half of the Sampling Frequency

DIGITAL SYSTEMS GUIDANCE (PART 2)

Input Noise Spectrum
0
-fo fo Input Signal Spectrum

Figure 3(b) Spectrum of f(t) Bandlimited to fo Hz

APPENDIX D
1 0 1
∞ −
ℑ{
∑
n = −∞
δ ( t − nTs )} 2T s 2T s

- - - - - - Figure 5(a) Input Signal and Noise Spectra

f

ARINC SPECIFICATION 429, PART 1 - Page 177

2 0 1 2
- - 1
Ts Ts Ts Ts
∞
Figure 3(b) Spectrum of Input Train, ∑
n=−∞
δ (t − nTs )

Rs(f) signal recovery

- - -
- - - 1 0 1
0
−
- 1 -fo fo 1 f
2T s 2T s
Ts Ts
Figure 5(b) Output Signal and Noise Spectra Showing Signal-to-Noise
- 1 + fo 1 -f Ratio Degradation Due to Aliasing of Signal and Noise
o
Ts Ts

Figure 3(c) Spectrum of Sampling Output

ARINC SPECIFICATION 429, PART 1 - Page 178
APPENDIX D
DIGITAL SYSTEMS GUIDANCE (PART 2)
 ARINC SPECIFICATION 429, PART 1 - Page 179

APPENDIX E
GUIDELINES FOR LABEL ASSIGNMENTS

The ARINC 429 data bus was developed to provide a standardized means of digital information transfer between the
“ARINC 700” series of avionics units. ARINC 429 has proven to be a very flexible standard and its usage has extended to
provide data transfer between Line Replaceable Units (LRU) which are not otherwise covered by ARINC Characteristics. It
is important that each new usage of ARINC 429 be coordinated and indexed by ARINC such that the information on usage
(label allocation, data format, etc.) is available industry-wide. The use of the same label for two different functions on a
particular LRU type built by different manufacturers can create serious problems.

To facilitate the coordination of ARINC 429 label usage between the industry and the ARINC staff, a set of guidelines is
provided.

1. New labels should be selected from the five character field as defined in Section 2.3 (three octal and three
hexadecimal).

2. The following labels have special significance and should not be used: label 000 (not used) and label 377
(equipment identification).

3. The following labels are presently “spare” and should only be used for new parameters which may have very
widespread usage throughout the airplane architecture.

005 040 050 054 107 163 227 371

c-16
006 046 051 055 113 167 240

007 047 052 057 124 226 243

4. Where possible, similar word usage should be “grouped”; for example, if Engine N 1 is to be provided from a new
unit (PMUX) it should utilize label 246 which is presently N 1 (engine direct).

5. Where possible, grouped usage should have identical data specification (units, range, significant digits/bits, positive
sense, resolution, min--max transmit interval). To facilitate this commonality it is permissible for a particular LRU
to output a lower resolution signal (fewer significant digits/bits) if the least significant remainder of the data field is
set to zeros.

6. Where word grouping is not possible, the labels should be selected from the following subgroups:

Binary coded decimal (BCD) sub-group 001 to 067, 125, 165, 170, 200, 201,230 to 237.

Binary (BNR) subgroup 070 to 124, 126 to 144, 150 to 154, 162 to 164, 166, 167, 171 to 177, 202 to 227, 240 to
257, 262 to 265, 267, 310 to 347, 360 to 376.

Mixed BCD and BNR subgroup 260, 261

Discretes subgroup 145 to 147, 270 to 276

Maintenance and discrete data subgroup 155, 156

Maintenance data subgroup 157 to 161, 350 to 354

Test word subgroup 266, 277

Application dependent subgroups 300 to 307

Acknowledgement subgroup 355

Maintenance ISO #5 subgroup 356

ISO #5 message subgroup 357

A schematic of these subgroups is attached.

ARINC SPECIFICATION 429, PART 1 - Page 180

APPENDIX E
GUIDELINES FOR LABEL ASSIGNMENTS

7. Allocation of bits within words, as defined in the appropriate sections.

BCD
BNR
Discretes
Maintenance data
Test
Application dependent
Acknowledgement
Maintenance ISO #5
ISO #5 message

8. The data should be fully defined by Equipment ID and the label and the Source Destination Indicator (SDI). It
should not be necessary to decode additional bits in the word to correctly interpret the data field.

9. The equipment ID should be allocated as the two least significant digits of the 7XX ARINC equipment
specification, if one exists. For equipment not otherwise covered by an ARINC Specification, an equipment ID
should be allocated with a non-numeric value of the hexadecimal character set as the least significant digit.

10. Equipment ID of 000 (HEX) should not be used.

11. The SDI code should indicate the aircraft installation number of the source equipment, in a multi-system installation,
as described in 2.1.4.

Least Significant Digit

Two /
Most /
Sig. /
Digits / 0 1 2 3 4 5 6 7
00 X
01
02
03 BCD
04
05
06
07
10 BNR
11
12 BCD
13
14 DISCRETE
15 MAINT DISC M DATA
16 MAINT DATA
17 BCD
20
21
22
23 BCD
24 BNR
25
26 MIX TEST
27 DISCRETE TEST
30 APPLICATION DEPENDENT
31
32
BNR
33
34
35 MAINT DATA ACK M ISO ISO5
36 BNR
37 EQ ID
 ARINC SPECIFICATION 429, PART 1 - Page 181
APPENDIX X
CHRONOLOGY & BIBLIOGRAPHY

X-l.0 Chronology
AEEC established the Systems Architecture and Interfaces (SAI) Subcommittee in 1975 to develop the air transport
industry’s approach to digital avionics systems architecture, to define digital system interface standards. With respect to this
last-named, the Subcommittee soon determined that the industry’s previous approaches to digital information transfer,
described in ARINC Specification 419, “Digital Data System Compendium”, needed rationalization and modernization to be
applicable in the future digital systems world. However, this work was not started immediately because of the need to
concentrate on the more basic tasks related to digital systems architecture.

About a year later, AEEC deemed it timely to start the spec-writing for a digital automatic flight control system based on the
system architecture concepts developed by the SAI Subcommittee. The Subcommittee AEEC established to do this began its
work in January 1977. Part of this activity was the definition of black box interface standards, and this brought into sharp
focus the need for the new digital information transfer system to be properly specified.
The SAI Subcommittee immediately began to devote time to the discussion of the issues involved to give direction to the
Digital Information Transfer System (DITS) working group it set up to develop a spec draft. This group met early in April
1977, and produced a draft which the full Subcommittee reviewed at its meeting in May. A second working group meeting
during the period of that Subcommittee meeting, followed by a third in mid-June, produced the second draft of the spec. This
draft was submitted to AEEC for adoption, which was achieved at the Summer 1977 General Session in July.

The spec adopted by AEEC contained details of numeric data (BNR and BCD) transfer only. The SAI Subcommittee
notified AEEC of its intent to broaden the scope of the document to cover alpha/numeric (ISO Alphabet No. 5) and graphic
data handling also. These subjects would be addressed in a Supplement to the spec which AEEC would be asked to approve
at a later date.

X-2.0 Bibliography

The following is a list of AEEC letters associated with the preparation of ARINC Specification 429. A list of AEEC letters
related the SAI Subcommittee's overall activities may be found in ARINC Report 299, “AEEC Letter Index”.

AEEC Letter No. Date Subject

76-130/SAI-20 Dec. 9, 1976 Report of the Systems Architecture and Interfaces Subcommittee Meeting
held November 16th, 17th and 18th, 1976 in Seattle, Washington

77-009/SAI-22 Jan. 27, 1977 Whither On-Board Digital Data Transmission Standards?

77-020/SAI-25 Feb. 11, 1977 More On Digital Data Transmission Standards

N77-035/SAI-26 Mar. 21, 1977 Boeing Report On Alternative Digital Information System Signalling
Standards

77-037/SAI-28 Mar. 25, 1977 Report of the Systems Architecture and Interfaces Subcommittee Meeting
Held March 7th, 8th and 9th, 1977 in Arlington, Virginia
77-047/SAI-33 Apr. 13, 1977 Circulation of Draft No. I of Project Paper 429, “Mark 33 Digital
Information Transfer System (DITS)”

77-056/SAI-37 Apr. 18, 1977 Report of the SAI Subcommittee BITS Working Group Meeting Held April
5-6, 1977, in Annapolis, Maryland
77-066/SAI-41 Jun. 8, 1977 Report of the Systems Architecture and Interfaces Subcommittee Meeting
Held May 9th, 10th and 11th, 1977 in Los Angeles, California
77-079/SAI-46 Jun. 23, 1977 Circulation of Draft No. 2 of Project paper 429, “Mark 33 Digital
Information Transfer System (DITS)”
ARINC SPECIFICATION 429, PART 1 - Page 182

APPENDIX X
CHRONOLOGY & BIBLIOGRAPHY

X-3.0 Meeting Attendees

The following people comprised the SAI Subcommittee’s Digital Information Transfer System Working Group.
Tom Ellison UNITED AIRLINES San Francisco, California
Wolfgang Bull DEUTSCHE LUFTHANSA Hamburg, Germany
Siegmar Gomille DEUTSCHE LUFTHANSA Hamburg, Germany
Jim Wahlen BENDIX AVIONICS Ft. Lauderdale, Florida
Tony Martin BOEING Seattle, Washington
Frank Rasmussen BOEING Seattle, Washington
Ed Schroeder BOEING Seattle, Washington
Arvind Dandekar COLLINS RADIO, ROCKWELL INT. Cedar Rapids, Iowa
Bill Harts COLLINS RADIO, ROCKWELL INT. Cedar Rapids, Iowa
David Lewis DELCO ELECTRONICS Milwaukee, Wisconsin
Ralph Bazil KING RADIO CORPORATION Olathe, Kansas
Hal Pierson MITRE CORPORATION McLean, Virginia
Bob Clark SPERRY FLIGHT SYSTEMS Phoenix, Arizona
Capt. Russ Glastetter USAF Dayton, Ohio
David Featherstone AERONAUTICAL RADIO, INC. Annapolis, Maryland

The following people attended one or more of the SAI Subcommittee meetings held November 16th-18th, 1976, March 7th-
9th, 1977 and May 9th-11th, 1977, during which the 429 DITS spec drafts and other proposals produced by the DITS
working group were reviewed, refined and finalized.
Airlines and ARINC Staff
T. A. Ellison, Chairman UNITED AIRLINES San Francisco, California
J. S. Davidson AIR CANADA Montreal, Canada
Gerard Collin AIR FRANCE Orly Aerogare, France
Jean Baptiste Rigaudias AIR FRANCE Orly Aerogare, France
Jean Le Luc AIR INTER Orly, France
Clarence L. Richmond AMERICAN AIRLINES Tulsa, Oklahoma
Robert M. Cook DELTA AIRLINES Atlanta, Georgia
Jose M. Recacha IBERIA SPANISH AIRLINES Barajas-Madrid, Spain
P. Lorie KLM AIRLINES Amsterdam, Netherlands
Ludwig Kilchert LUFTHANSA GERMAN AIRLINES Hamburg, Germany
Norton Codish PAN AM WORLD AIRLINES Jamaica, New York
Vic Persson SCANDINAVIAN AIRLINES Stockholm-Bromma, Sweden
Karl H. Riesen SWISSAIR Jamaica, New York
T. E. Jackson TWA Kansas City, Missouri
L. R. Berryhill UNITED AIRLINES Denver, Colorado
M. W. Brecht UNITED AIRLINES San Francisco, California
O. R. Evans UNITED AIRLINES San Francisco, California
C. H. Humphrey UNITED AIRLINES San Francisco, California
Robert K. Moyers U.S. AIR FORCE Washington, D.C.
Claude Gouillon UTA Puteaux, France
Wallace L. Urie WESTERN AIRLINES Los Angeles, California
W. T. Carnes AERONAUTICAL RADIO, INC. Annapolis, Maryland
B. R. Clime AERONAUTICAL RADIO, INC. Annapolis, Maryland
D. H. Featherstone AERONAUTICAL RADIO, INC. Annapolis, Maryland
C. C. Tinsley AERONAUTICAL RADIO, INC. Annapolis, Maryland

Manufacturers and Others

Bernard E. Bouet AEROSPATIALE Toulouse, France
Jean Tambareau AEROSPATIALE Toulouse, France
Russell Fine AIRESEARCH MFG. CO. Torrance, California
William M. Russell III AIR TRANSPORT ASSOCIATION Washington, D.C.
S. R. Sporn ARMA DIV./AMBAC Garden City, New York
Robert L. Daniel AVIATION CONSULTANT Studio City, California
Jean Francois Ferreri AVIONS MARCEL DASSAULT Saint Cloud, France
Jay J. Ahmann BENDIX AVIONICS DIV. Burbank, California
T. H. Hitt BENDIX AVIONICS DIV. Burbank, California
Brendan J. Spratt BENDIX AVIONICS DIV. Ft. Lauderdale, Florida
William C. Thompson BENDIX AVIONICS DIV. Ft. Lauderdale, Florida
 ARINC SPECIFICATION 429, PART 1 - Page 183

APPENDIX X
CHRONOLOGY & BIBLIOGRAPHY

James C. Whalen BENDIX AVIONICS DIV. Ft. Lauderdale, Florida

Howard E. Allen BENDIX CORP. FLIGHT SYSTEMS Tukwila, Washington
Donald L. Beckman BENDIX CORP. FLIGHT SYSTEMS Teterboro, New Jersey
Jerry Doniger BENDIX CORP. FLIGHT SYSTEMS Teterboro, New Jersey
Ken Kendall BENDIX CORP. FLIGHT SYSTEMS Teterboro, New Jersey
Albert T. Kirchhein BENDIX CORP. FLIGHT SYSTEMS Teterboro, New Jersey
Harry W. Bedell Jr. BENDIX LONG BEACH FAC. Lakewood, California
Dwayne Broderson BOEING COMMERCIAL AIRPLANE Seattle, Washington
James R. Fries BOEING COMMERCIAL AIRPLANE Seattle, Washington
R. F. Gorman BOEING COMMERCIAL AIRPLANE Seattle, Washington
Anthony J. Martin BOEING COMMERCIAL AIRPLANE Seattle, Washington
J. McHutchison BOEING COMMERCIAL AIRPLANE Seattle, Washington
Richard A. Peal BOEING COMMERCIAL AIRPLANE Seattle, Washington
Frank A. Rasmussen BOEING COMMERCIAL AIRPLANE Seattle, Washington
Irving R. Reese BOEING COMMERCIAL AIRPLANE Seattle, Washington
E. T. Schroeder BOEING COMMERCIAL AIRPLANE Seattle, Washington
V. J. Small BOEING COMMERCIAL AIRPLANE Seattle, Washington
Robert W. Sutton BOEING COMMERCIAL AIRPLANE Seattle, Washington
Ray Hillman BRITISH AEROSPACE Surrey, England
Richard A. Keall BRITISH AEROSPACE Hatfield, England
Donald J. Gussin CANADIAN MARCONI CO. Montreal, Canada
Arvind J. Dandekar COLLINS RADIO GROUP Cedar Rapids, Iowa
R. V. Donaldson COLLINS RADIO GROUP Cedar Rapids, Iowa
J. C. Hall COLLINS RADIO GROUP Cedar Rapids, Iowa
Bryand C. Hawkins COLLINS RADIO GROUP Cedar Rapids, Iowa
Eugene C. Machacer COLLINS RADIO GROUP Cedar Rapids, Iowa
Donald H. Wickenkamp COLLINS RADIO GROUP Cedar Rapids, Iowa
John F. Lent CROUZET Pasadena, California
Michel Pascal CROUZET Valence, France
Richard A. Johnson DELCO ELECTRONICS DIV. GMC Milwaukee, Wisconsin
L. David Lewis DELCO ELECTRONICS DIV. GMC Milwaukee, Wisconsin
John H. Sheldrick DELCO ELECTRONICS DIV. GMC Milwaukee, Wisconsin
Tom Sizlo DOUGLAS AIRCRAFT COMPANY Long Beach, California
John Carter E-A INDUSTRIAL CORP. Chamblee, California
David Burton ELDEC CORPORATION Lynnwood, California
Roy F. Keating ELDEC CORPORATION Lynnwood, California
Rene Plouhinec ELECTRONIQUE MARCEL DASSAULT Saint Cloud, France
John E. Reed FAA Washington, D.C.
Charles Sheets GARRETT CORP. Torrance, California
Robert E. Weir GARRETT AIREASEARCH Torrance, California
Richard Haley HAMILTON STANDARD Windsor Locks, Connecticut
S. C. Caliendi HAWKER SIDDELEY AVIATION Hatfield, Herts, England
Harry Graves HONEYWELL INC. Minneapolis, Minnesota
Ronald G. Raymond HONEYWELL INC. St. Louis Park, Minnesota
Claude P. Roquefeuill ISPENA Paris, France
Jack Hawkins ITT CANNON ELECTRIC Santa Ana, California
J. Langenback ITT CANNON ELECTRIC Santa Ana, California
Ray Swanson JAEGER Pasadena, California
Ken Berg KING RADIO CORP Olathe, Kansas
David A. Nelson KING RADIO CORP Olathe, Kansas
John C. Cotton LITTON AERO PRODUCTS Woodland Hills, California
L. J. Singleton LITTON AERO PRODUCTS Woodland Hills, California
P. H. Weinheimer LITTON AERO PRODUCTS Seattle, Washington
William R. Beckman LOCKHEED CALIFORNIA CO Burbank, California
Job Van Der Bliek LOCKHEED CALIFORNIA CO Burbank, California
Wm. J. Hillman LOCKHEED CALIFORNIA CO Burbank, California
Ed Selvig LOCKHEED CALIFORNIA CO Burbank, California
Barry J. Aldridge MARCONI ELLIOTT AVIONICS Rochester Kent, UK
Gordon Belcher MARCONI ELLIOTT AVIONICS Rochester Kent, UK
Derek Marshall MARCONI ELLIOTT AVIONICS Seattle, Washington
Karl-Heinz Terheiden MESSERSCHMITT-BLOKOW-BLOHM Hamburg, Germany
Harold L. Pierson MITRE CORPORATION McLean, Virginia
Richard W. Telsch MITRE CORPORATION McLean, Virginia
Gary C. Horan PRATT & WHITNEY AIRCRAFT East Hartford, Connecticut
G. A. Lucchi RCA Van Nuys, California
ARINC SPECIFICATION 429, PART 1 - Page 184

APPENDIX X
CHRONOLOGY & BIBLIOGRAPHY

Gerard A. Collin SAGEM Paris, France

Lloret SAGEM Paris, France
Jean-Yves Begeault SFENA Velizy-Villacoublay, France
Jefferson Z. Amacker SINGER KEARFOTT Little Falls, New Jersey
Joseph Koprowski SINGER KEARFOTT Little Falls, New Jersey
John Desmond SMITHS INDUSTRIES INC. Clearwater, Florida
Dave Richardson SMITHS INDUSTRIES INC. Clearwater, Florida
Brian Williams SMITHS INDUSTRIES INC. Cheltenham, Glos, UK
Mike C. Pietromonaco S. P. INC Bellevue, Washington
Donald Baker SPERRY FLIGHT SYSTEMS Phoenix, Arizona
Don Burkholder SPERRY FLIGHT SYSTEMS Phoenix, Arizona
Jack E. Emfinger SPERRY FLIGHT SYSTEMS Phoenix, Arizona
D. A. Few SPERRY FLIGHT SYSTEMS Phoenix, Arizona
Martin S. Klemes SPERRY FLIGHT SYSTEMS Phoenix, Arizona
R. J. Lofquist SPERRY FLIGHT SYSTEMS Phoenix, Arizona
Harry Miller SPERRY FLIGHT SYSTEMS Phoenix, Arizona
Ronald H. Neeves SPERRY FLIGHT SYSTEMS Phoenix, Arizona
Edmond Olive SPERRY FLIGHT SYSTEMS Phoenix, Arizona
R. E. Schaffer SPERRY FLIGHT SYSTEMS Phoenix, Arizona
Harry O. Smith SPERRY FLIGHT SYSTEMS Phoenix, Arizona
Al J. Venancio SPERRY FLIGHT SYSTEMS Phoenix, Arizona
Lou Borbely SUNSTRAND DATA CONTROL Redmond, Washington
Glenn H. Jones SUNSTRAND DATA CONTROL Redmond, Washington
Robert Schaeperkoetter SUNSTRAND DATA CONTROL Redmond, Washington
C. A. Bennet TELEDYNE CONTROLS El Segundo, California
H. E. Sutherland TELEDYNE CONTROLS El Segundo, California
D. A. Giroux THOMSON-CSF Les-Moulineaux, France
Charles Legrand THOMSON-CSF Les-Moulineaux, France
J. Ribiere THOMSON-CSF Malakoff, France
J. Lane Ware THOMSON-CSF New York, New York
William Donnell TRACOR APPLIED TECHNOLOGY Austin, Texas
R. R. Fay TRACOR APPLIED TECHNOLOGY Austin, Texas
Jean-Pierre Tomasi TRT Le Plessis-Robinson, France
Blaine C. Ferch USAF Wright Patterson AFB, Ohio
Erwin C. Gangi USAF Dayton, Ohio
Capt. R. A. Glastetter USAF Wright Patterson AFB, Ohio
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401- 7645 USA

SUPPLEMENT 1
TO

ARINC SPECIFICATION 429

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

Published: June 1, 1978

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: April 11, 1978

SUPPLEMENT 1 TO ARINC SPECIFICATION 429 - Page 2
A. PURPOSE OF THIS SUPPLEMENT
This Supplement adds to Specification 429 material
related to the transfer of graphic and ISO alphabet No. 5
encoded alpha/numeric data by the Mark 33 DITS. Also,
it clarifies the purpose of the SDI function, adds BCD and
BNR numeric data encoding examples to Attachment 6
and introduces two Appendices into the Specification.
B. ORGANIZATION OF THIS SUPPLEMENT
The first part of this document, printed on goldenrod
paper, contains descriptions of the changes introduced
into the Specification by this Supplement, and, where
appropriate, extracts from the original text for comparison
purposes. The second part consists of replacement white
pages for the Specification, modified to reflect these
changes. The modified and added material on each
replacement page is identified with “c-1” symbols in the
margins. Existing copies of Specification 429 may be
updated by simply inserting the replacement white pages
where necessary and destroying the pages they replace.
The goldenrod pages should be inserted inside the rear
cover of the Specification.
Copies of the Specification bearing the number 429-1
already contain this Supplement and thus do not require
revisions by the reader.
C. CHANGES TO SPECIFICATION 429
INTRODUCED BY THIS SUPPLEMENT
This section presents a complete tabulation of the changes
and additions to the Specification introduced by this
Supplement. Each change or addition is identified by the
section number and title currently employed in the
Specification, or by the section number and title that will
be employed when the Supplement is eventually
incorporated. In each case there is included a brief
description of the addition or change and, for other than
very minor revisions, any text originally contained in the
Specification is reproduced for reference.
1.3.2 ISO Alphabet No. 5 Data Transfer
Existing text supplemented – no other changes.
1.3.3 Graphic Data Transfer
New section added by this Supplement.
2.1.2 Information Element
COMMENTARY
revised to improved clarity of opening sentence, and
to modify the statement concerning the BCD-
encoding of latitude and longitude as a consequence
of the clarification of the use priorities for bit nos. 9
and 10 introduced into Section 2.1.4 by this
Supplement.
ORIGINAL TEXT FOLLOWS
To permit the use of common hardware elements for the
transmission of BNR and BCD numeric data, the format
for the Mark 33 DITS BCD word differs from that used
formerly for this type of data. Bit no. 32 is assigned to
parity, bit nos. 31 and 30 to the sign/status matrix, bit no.
29 is the most significant bit of the data field, and the
maximum decimal value of the most significant character
is 7. Previously, the BCD word contained no parity bit,
the sign/status matrix occupied bit nos. 32 and 31, bit no.
30 was the most significant data bit and the maximum
decimal value of the most significant character was 3.
This format made the word 8-bit byte oriented with
respect to the data. This characteristic is not retained in
the Mark 33 system.
Also, the Mark 33 BCD word will not accommodate
latitude and longitude to the formerly specified resolution
of 0.1 minute of arc. If BCD transmission of these
quantities in required, either the resolution must be
decreased or the word must be restructured.
Restructuring involves limiting the maximum decimal
value of the most significant character to 1, moving the
remaining BCD characters towards the MSB by two bit
positions and using bit nos. 9 and 10 for data instead of
reserving them for source/destination identification
encoding per Section 2.1.4 of this document. It is
probable, however, that future latitude and longitude
displays will not be the simple, dedicated read-out type
for which BCD data is intended. More likely is the use of
some form of multiple-message display, such as a CRT,
which will be backed by its own data processor and prefer
inputs of BNR data. If this proves to be the case, there
will be no problem!
2.1.3 Information Identifier
Text expanded to explain differing roles of label codes in
numeric (BCD/BNR) and alpha/numeric (ISO Alphabet
No. 5) data transfer. “Special Note” added.
ORIGINAL TEXT FOLLOWS
The first eight bits of each word are assigned to a label
function so that the data contained in the word may be
identified. Label code assignments are set forth in the
table of Attachment 1 to this document.
2.1.4 Source/Destination Identifier
Section modified to indicate that bit nos. 9 & 10 are not
available for the SDI function in DITS words employed
for graphic and ISO Alphabet No. 5 data transfer, or in
BNR/BCD words in which bit nos. 9 and 10 are needed
for valid data in order to achieve the desired resolution.
Code table revised and function application more fully
described. Consequential revisions to Commentary.
 SUPPLEMENT 1 TO ARINC SPECIFICATION 429 - Page 3
ORIGINAL TEXT FOLLOWS
Bit nos. 9 & 10 of the word should be reserved for a data
source/destination identification function. This function
may find application when specific words need to be
directed to a specific system of a multi-system installation
or when the source system of a multi-system installation
needs to be recognizable from the word content. When
the source/destination identifier function is used, bit nos.
9 & 10 should be encoded as follows. When it is not
used, binary zeros or valid data should be transmitted in
these positions
Bit No.
System
10 9
0 0 1 appears in a word identified by its label as an
0 1 2 instruction, e.g., a radio channel change command,
1 0 3 this code should be interpreted as a command to
1 1 4 perform a functional test.
.
COMMENTARY
In many applications of the Mark 33 DITS, data
source/destination identification will not be needed.
In these cases, bits 9 & 10 will be used as pad bits for
valid data. In certain other applications of the
system, for example, BCD latitude and longitude
encoding (if needed – see Commentary following
Section 2.1.2 of this document), the need to use bit
nos. 9 and 10 to obtain adequate data resolution will
preclude source/destination identification in this way.
Note that this document does not address the
practical question of how these bits will be set in
those multi-system installations in which the
source/destination identification function is desired.
One way would be to use program pins on individual
system black boxes which would be wired to set up
the appropriate code. The ARINC Characteristics
devoted to the individual systems will define the
method actually to be used.
2.1.5 Sign/Status Matrix
Section divided into two sub-sections, one to describe the
BCD numeric and ISO Alphabet #5 alpha/numeric data
sign status matrix, and the other to describe the BNR
numeric data sign/status matrix.
ORIGINAL TEXT FOLLOWS
The “sign” (plus, minus, north, south, etc.) of the
transmitted data and the status of the transmitter hardware
should be encoded in bit nos. 30 and 31 as shown in the
table below.
Bit No. Designation
31 30 BNR/BCD Data ISO # 5 Data
0 0 Plus, North, East
Right, To
0 1 No Computed Data TBD
1 0 Functional Test
1 1 Minus, South, West,
Left, From
Notes:
1. A source system should indicate failure by ceasing to
supply data to a bus.
2. Both bits should be “zero” in BNR and BCD words
when no sign is needed.
3. The “no computed data” code should be generated
when computed data is not available for reasons other
than equipment failure.
4. When is appears in a word identified by its label as a
system output, the “functional test” code should be
interpreted as advice that the data in the word results
from the execution of a functional test. When it
2.1.6 Data Standards
Typographical errors corrected in second paragraph of
Commentary.
2.2.1 Transmission System Interconnect
Existing material supplemented with information
concerning shield grounding.
2.2.3.2 Receiver Voltage Levels
DC levels between terminal A and ground and terminal B
and ground at which receivers should not be damaged
raised from +20VDC to +28VDC (min) and for –20VDC
to –28VDC (min) respectively to align numerical values
with aircraft DC power supply value.
2.3.1.3 ISO Alphabet No. 5 Data
New section added by this Supplement.
2.4.1 Bit Rate
Existing commentary supplemented with warning against
selection of 13.6 KBPS and 100 KBPS because of
possible interference with operation of OMEGA and
LORAN C system on the aircraft.
Attachment 2: Data Standards Tables 1 and 2
Column heading “MIN TRANSMIT INTERVAL msec”
changed to “MAX TRANSMIT INTERVAL msec” in
each case.
Attachment 2: Data Standards Table 3
Table 3 (Alpha/Numeric (ISO Alphabet No. 5) Data
Standards) deleted. Table 4 (Discrete Data) renumbered
Table 3.
Note: Table 3 was reserved for alpha/numeric (ISO
Alphabet No. 5) data standards prior to the preparation of
this Supplement. The need for it disappeared as a result
of the particular approach selected for handling this data
introduced into Specification 429 by this Supplement.
SUPPLEMENT 1 TO ARINC SPECIFICATION 429 - Page 4

Attachment 6: General Word Formats and Encoding

Examples

BNR word format example amended as consequence of

change to sign/status matrix (see Section 2.1.5) General
Word Formats for ISO Alphabet No. 5 data added.
Encoding examples added.

Appendix 1: Laboratory Verification of ARINC 429

DITS Electrical Characteristics

New material added by this Supplement.

Appendix 2: An Approach to a Hybrid Broadcast
Command/Response Data Bus Architecture.
New material added by this Supplement.
 NOTE: Due to the large number of changes
Created by this Supplement, it is NOT
available separately to update 429-1.

AERONAUTICAL RADIO, INC.

2551 Riva Road
Annapolis, Maryland 21401- 7645 USA

SUPPLEMENT 2

TO

ARINC SPECIFICATION 429

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

Published: March 1, 1979

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: December 6, 1978

SUPPLEMENT 2 TO ARINC SPECIFICATION 429 - Page 2

A. PURPOSE OF THIS SUPPLEMENT
This Supplement amends the material added to
Specification 429 on ISO Alphabet No. 5 data transfer,
and expands the multiple-word DITS message concept
first used in this application to cover Discrete,
Acknowledgement and Maintenance (ISO Alphabet No.
5 and discrete data formats) information transfer as well.
The Application Notes of Chapter 3 of the Specification
are amended to bring them into line with adopted
practice in the control of DME’s and ATC transponders,
and supplemented with material related to the multiple-
word message applications of the system just
mentioned. Also, additions and modifications have
been made to the label codes and data standards in
Attachments 1 and 2 of the Specification to bring them
into line with adopted practice.
B. ORGANIZATION OF THIS SUPPLEMENT
The first part of this document, printed on goldenrod
paper, contains descriptions of the changes introduced
into the Specification by this Supplement, and, where
appropriate, extracts from the original test for
comparison purposes. The second part consists of
replacement white pages for the Specification, modified
to reflect these changes. The modified and added
material on each replacement page is identified with “c-
2” symbols in the margins. Existing copies of
Specification 429 may be updated by simply inserting
the replacement white pages where necessary and
destroying the pages they replace. The goldenrod pages
should be inserted inside the rear cover of the
Specification.
Copies of the Specification bearing the number 429-2
already contain this Supplement and thus do not require
revisions by the reader.
C. CHANGES TO SPECIFICATION 429
INTRODUCED BY THIS SUPPLEMENT
used, the resolution possible for the information will
exceed that called for in this specification. The
Commentary following Section 2.1.6 of this document
refers.
2.1.3 INFORMATION IDENTIFIER
Text revised to describe label use for
AIM/Discrete/Maintenance data word type
identification.
ORIGINAL TEXT FOLLOWS:
2.1.3 Information Identifier
The first eight bits of each word are assigned to a label
function. Labels will a) identify the information
contained within numeric (BCD/BNR) data words (e.g.,
DME distance, static air temperature), and b) act as
receiving device addresses for alpha/numeric (ISO
Alphabet No. 5) data words (e.g., navigation system
CDU or map display). Label code assignments are set
forth in Attachment 1 to this document.
2.1.5.1 BCD NUMERIC AND AIM DATA WORDS
Title and text revised to include other AIM applications
in material originally prepared to describe sign/status
matrix use in ISO Alphabet No. 5 words, and to provide
definition of Self-Test.
ORIGINAL TEXT FOLLOWS:
2.1.5.1 BCD Numeric and ISO Alphabet No. 5 Data
Words
The sign (plus, minus, north, south, etc.) of BCD
numeric data, the word type of alpha/numeric (ISO
alphabet No. 5) data and the status of the transmitter
hardware should be encoded in bit nos. 30 and 31 of the
word as shown in the table below.

This section presents a complete tabulation of the

changes and additions to the Specification introduced by Bit No. Designation
this Supplement. Each change or addition is entitled by ISO #5
the section number and title currently employed in the 31 30 BNR/BCD Data Data
Specification, or by the section number and title that Plus, North, East
will be employed when the Supplement is eventually 0 0 Right, to Initial Word
incorporated. In each case there is included a brief No Computed
description of the addition or change and, for other than 0 1 No Computed Data
Data
very minor revisions, any text originally contained in Intermediate
the Specification is reproduced for reference. 1 0 Functional Test
Word
Minus, South, West
2.1.2 INFORMATION ELEMENT 1 1 Left, From Final Word

Text revised to describe word application groups. Notes:

ORIGINAL TEXT FOLLOWS:
2.1.2 Information Element
The basic information element is a digital word
containing 32 bits. Word formats for the different types
of data handled by the Mark 33 DITS (see Section 2.3.1
of this document) are depicted in Attachment 6. When
less than the full data field is needed to accommodate
the information conveyed in a word in the desired
manner, the unused bit positions should be filled with
binary zeros or valid data pad bits. If valid data bits are
1. A source system should annunciate any detected
failure that causes one or more of the words
normally output by that system to be unreliable
by ceasing to supply the affected word or
words to the data bus.
2. Both bits should be “zero” when no sign is
needed.
3. The “no computed data” code should be
generated when computed data is not
available for reasons other than equipment
failure.
 SUPPLEMENT 2 TO ARINC SPCIFICATION 429 - Page 3
4. When it appears in a word identified by its label as
a system output, the “functional test” code should
be interpreted as advice that the data in the word
results from the execution of a functional test.
When it appears in a word identified by its label as
an instruction, e.g., a radio channel change
command, this code should be interpreted as a
command to perform a functional test.
5. See Section 2.3.1.3 of this document for definitions
of the terms “Initial Word”, “Intermediate Word”
and “Final Word”.
2.1.5.2 BNR NUMERIC DATA WORDS
Text revised to provide definition of Self-Test.
ORIGINAL TEXT FOLLOWS:
2.1.5.2 BNR Numeric Data Words
The sign (plus, minus, north, south, etc.) of BNR
numeric data words and the status of the transmitter
hardware should be encoded in bit nos. 29, 30 and 31 of
the word as shown in the table below.
Bit No. Designation
31 30 29 BNR Data
Failure Warning/Plus, North, East
0 0 0 Right, To
Failure Warning/Minus, South, West,
0 0 1 Left, From
0 1 0 No Computed Data
Functional Test/Plus, North, East,
1 0 0 significant bit. Attachment 6 shows this against the
Right, To
Functional Test/Minus, South, West
1 0 1 Left, From
Normal Operation/Plus, North, East,
1 1 0 Right, To
Normal Operation/Minus, South
1 1 1 West, Left, From
0 1 1 Not Used (Growth)
Notes:
1. A source system should annunciate any detected
failure that causes one or more of the words
normally output by that system to be unreliable by
setting bit nos. 30 and 31 in the affected word(s) to
the “failure warning” code defined above. Words
containing this code should continue to be supplied
to the data bus during the failure condition.
2. Bit no. 29 should be “zero” when no sign is needed.
3. The “no computed data” code should be generated
when computed data is not available for reasons
other than equipment failure.
4. When it appears in a word identified by its label as
a system output, the “functional test” code should
be interpreted as advice that the data in the word
results from the execution of a functional test. A
self-test should produce indications of 1/8 of
positive full-scale values unless indicated otherwise
in an ARINC Equipment Characteristic.
5. If, during the execution of a functional test, a
source system detects a failure which causes one or
more of the words normally output by that system
to be unreliable, it should immediately change the
states of bit nos. 30 and 31 in the annunciation is
replaced with the “failure warning” annunciation
2.2.3.1 TRANSMITTER VOLTAGE LEVELS
Tolerances on “HI” and “LO” voltage states changed
from ± 0.5 volt to ± 1.0 volt to correct previously
undetected error.
2.3.1.2 DISCRETES
Minor changes to existing wording to improve clarity.
New paragraphs added to describe two types of
dedicated –to-discrete words and their applications.
ORIGINAL TEXT FOLLOWS:
2.3.1.2 Discretes
In addition to handling numeric data as specified above,
the Mark 33 DITS should also be capable of
accommodating discrete items of information, either in
the “spare” bits of data words or, when necessary, in
dedicated words. Any discrete information contained in
a word assigned a label in Attachment 1 is specified in
the definition for that word in Attachment 2.
The rule to be followed in the assignment of bits to
discrete functions is to start with the least significant bit
available in the word and to continue towards the most
background of the generalized word structure.
2.3.1.3 Maintenance Data (General Purpose)
This section inserted to describe use and application of
general purpose Maintenance words.
ORIGINAL TEXT FOLLOWS:
2.3.1.3 Alpha/Numeric (ISO Alphabet No. 5) Data
ISO Alphabet No. 5 alpha/numeric data will consist of
seven-bit characters encoded per the table of
Attachment 5 to this document. Three such characters
should occupy bit nos. 9 through 29 of a DITS 32-bit
word, as shown in the general word format diagram in
Attachment 6. As for numeric (BCD) data words, bit
nos. 1 through 8 should be the word label (receiving
device address-see Section 2.1.3), bit nos. 30 and 31 the
sign/status matrix and bit no. 32 the word parity bit.
The typical alpha/numeric message contains more than
three ISO Alphabet No. 5 characters, necessitating the
transmission of multi-DITS-word messages. The
following procedure should be used to permit receivers
to determine that such messages are received in their
entirety, with no words having been “lost along the
way”. Only when this determination has been made,
and the parity check for each word shows the data to be
error-free, should the message be displayed to the
aircrew or otherwise utilized.
SUPPLEMENT 2 TO ARINC SPECIFICATION 429 - Page 4

2.3.1.3 Alpha/Numeric (ISO Alphabet No. 5) Data (cont’d)

The first DITS word of the message should contain the

label in bit nos. 1 through 8, two numeric characters
encoded per ISO Alphabet No. 5 in bit nos. 9 through
15 and 16 through 22 and the ISO Alphabet No. 5
control character “STX”in bit nos. 23 through 29. The
two numeric characters should indicate the decimal
number of DITS words in the message (maximum
number is 99), with the most significant character
occupying bit nos. 16 through 22. This count, which
should include this initial word, will be one plus the
next whole number greater than one third of the number
of ISO Alphabet No. 5 characters to be transmitted. The
sign/status matrix should contain the “initial word” code
defined in Section 2.1.5 of this document.

The subsequent DITS words of the message should each

contain the label in bit nos. 1 through 8 and three ISO
Alphabet No. 5 characters. The sign/status matrix of all
these words except the last word should contain the
“intermediate word” code defined in Section 2.1.5.1 of
this document. The last word of the message should
contain the “final word” code in its sign/status matrix.
Any unused bit positions in the final word resulting
from the number of ISO characters in the message being
one or two less than a number wholly divisible by three
should be filled with binary “zeros”.

2.3.1.4 AIM Data

Section number, text and title revised to include other

AIM word applications in material originally prepared
to describe ISO Alphabet No. 5 data handling
(originally in Section 2.3.1.3). Detailed amendments in
this area also.

3.1.4.2 DME

The “Override” switching function has been replaced by

the “DME Mode Select” function.

3.1.4.7 ATC TRANSPONDER

“Mode A/B Select” and “Standby” deleted from list of

switching functions. Control word format re-structured
to release bits unneeded in numeric data part of word for
assignment to discrete switching functions.

Fig. 3-1 Radio Systems Management Word Formats

Bit nos. 11 and 12 in the DME data word have been

assigned to “DME Mode Select”.
The description of bit 14 in the VOR/ILS data word has
been revised to improve clarity.

ORIGINAL TEXT FOLLOWS:

[1] When bit no. 4 is “zero”, the ILS mode should

be “off. When bit no 14 is “one”, the ILS
mode should be “one”.
 SUPPLEMENT 2 TO ARINC SPCIFICATION 429 - Page 5

ORIGINAL ATC TRANSPONDER WORD FORMAT ILLUSTRATION FOLLOWS:

ATC
TRANSPONDER

A/B Mode Select

ALT. REP. OFF

SIGN/STATUS
PARITY (odd) LABEL

RESERVED
STANDBY
Beacon Transponder Code

MATRIX

IDENT

(SDI)
0.7

0.7

0.7

0.7
(3)

(6)

(2)

(0)
Bit No.
Example
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
0 0 0 0 1 1 0 1 1 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 1 1 0 1 1 0 0 0
[1]

[1]
Bit Zero One

11 Alt. Rep. ON Alt. Rep. OFF

12 Standby OFF Standby ON
13 Ident OFF Ident ON
14 Select Mode A Select Mode B

The revised format of the ATC transponder word is as shown

on page 10.

3.2 AIM Information Transfer

New section added by this Supplement.

Attachment 1: Label codes

Some parameter names have been changed and others have

been added to the list. Instead of showing the entire list, only
the original assignment of those that have been changed are
shown below.
SUPPLEMENT 2 TO ARINC SPECIFICATION 429 - Page 6

Label (Octal) Original Assignment Proposed Assignment

007 Align Status/Inertial Discretes No assignment

014 None assigned Magnetic Heading
015 None assigned Wind Speed
016 None assigned Wind Direction-True
017 None assigned Selected Runway Heading
024 Selected Course Selected Course #1
027 None assigned Selected Course #2
041 None assigned Set Latitude
042 None assigned Set Longitude
043 None assigned Set Magnetic Heading
044 None assigned True heading
045 None assigned Minimum Airspeed
100 Selected Course Selected Course #1
107 AFS Discretes No assignment
110 None assigned Selected Course #2
112 None assigned Selected EPR or N1
124 FMC Discretes Caution & Warning DFDR Discretes #1
130 None assigned Tt2
131 None assigned Pt2
132 None assigned Pt7
133 None assigned Thrust Lever Angle
145 None assigned AFS DFDR Discretes #1
146 None assigned AFS DFDR Discretes #2
147 None assigned AFS DFDR Discretes #3
166 None assigned RALT Check Point Dev.
203 Altitude (29.92) Altitude (1013.25mb)
204 Altitude (Baro) Baro Corrected Altitude #1
214 Air Data Computer Discretes No assignment
216 Baroset No assignment
220 None assigned Baro Corrected Altitude #2
221 None assigned Indicated Angle of Attack
223 Altitude (29.92) No assignment
224 Altitude Baro Caution/Warning DFDR Discretes #2
225 Mach No assignment
226 Computed Airspeed No assignment
227 Max Allowable Airspeed No assignment
234 Baroset (millibars) Baro Correction (mb #1)
235 Baroset (ins. of Hg) Baro Correction (mb #1)
236 None assigned Baro Correction (mb #2)
237 None assigned Baro Corrected (in of Hg #2)
241 None assigned Corrected Angle of Attack
242 None assigned Total Pressure
245 None assigned Minimum Airspeed
247 None assigned Total Fuel
270 None assigned Discrete Data #1
271 None assigned Discrete Data #2
272 None assigned Discrete Data #3
273 None assigned Discrete Data #4
274 None assigned Discrete Data #5
334 Free Heading Platform Heading
340 N1 or EPR Actual EPR Actual
346 None assigned N1 Actual
350 Engine Discretes Maintenance Data #1
351 Control Panel Discretes Maintenance Data #2
352 Control Panel Discretes Maintenance Data #3
353 Control Panel Discretes Maintenance Data #4
354 Instrument Discretes Maintenance Data #5
355 None assigned Acknowledgement
356 None assigned Maintenance ISO #5 Message
357 None assigned ISO #5 Message
360 None assigned Potential Vertical Speed
372 None assigned Wind Direction-Magnetic
373 None assigned N-S Velocity-Magnetic
374 None assigned E-W Velocity-Magnetic
375 None assigned Along Heading Acceleration
376 None assigned Cross Heading Acceleration
 SUPPLEMENT 2 TO ARINC SPCIFICATION 429 - Page 7

Attachment 2: Data Standards

A number of additions and changes have been made to the

tables. The octal labels and parameter names are shown for
each data item that has been changed. The original data is
shown only for the data that has been changed by this
supplement. Also a second “Note” has been added to Table 2.

Table 1 BCD DATA

Label Parameter Max Sig. Pad

(Octal) Name Transmit Range (Scale) Fig. Fig. Units Resol
Interval
170 Decision Hgt Sel.(EFI) 200 0 - 500 3 2 Feet 1.0
201 DME Distance 200* -1 - 399.99* 5 0 N.M. 0.01
230 True Airspeed 500* 130 - 599* 3 2 Knots 1.0
231 Total Air Temp. 500 +500 — 99* 2 3 oc 1.0
233 Static Air Temp. 500 -99 - +60* 2 3 oc 1.0
234 Baroset (mb)* 200* 0 - 3999* 4* 1* mb 1.0*
235 Baroset (ins. of Hg*) 200* 0 - 39.99* 4* 1* ins.Hg 0.01*

*This data has been changed.

Note: Labels 017, 027, 041, 042, 043, 044, 045, 236 and 237 previously had no values assigned. Values for labels 223, 224,
225, 226 and 227 have been changed.

Table 2 BNR DATA

Label Parameter Max Sig. Bits Approx.

Transmit (Not Inc. Units Range
(Octal) Name Resol.
Interval Sign)
100 Selected Course 62.5* 9 Deg/180 ± 180 o 0.35o
103 Selected Airspeed 62.5* 11* Deg/180 ± 180 o 0.25*
121 Horiz. Strg. Signal 100 9* Deg/180 +45o * 0.1 o *
122 Vert.Strg.Signal 100 9 Deg/180 +22.50 o * 0.05 o *
140 Flight Director-Roll 62.5* 9 Deg/180 ±45 o 0.1 o
141 Flight Director-Pitch 62.5* 9 Deg/180 ± 22.5 0.05 o
164 Radio Height 50 18* Feet 32768* 0.125
202 DME Distance 200* 16 N.M. 512 0.0008
203 Altitude (29.92) 62.5 17* Feet 131,071 1.0*
206 Computed Airspeed 125 12* Knots 1024 0.25*
207 Max.Allowable Airspeed 500* 12 Knots 1024 0.25
210 True Airspeed 500* 11 Knots 2048 1.0
215 Impact Pressure 125 12* ins/Hg* 32* 0.008*
313 Track Angle True 50* 12 Deg/180 ± 180 o 0.05 o
314 True Heading 50* 12 Deg/180 ± 180 o 0.05 o
317 Track Angle-Magnetic 50* 12 Deg/180 ± 180 o 0.05 o
320 Magnetic Heading 50* 12 Deg/180 ± 180 o 0.05 o
321 Drift Angle 50* 11 Deg/180 +90 o 0.05 o
322 Flight Path Angle 50* 10 Deg/180 ± 45 o 0.05 o
323 Flight Path Acceleration 20 12* g 4* 0.001*
324 Pitch Angle 50* 13 Deg/180 +90 o 0.01 o
325 Roll Angle 50* 14 Deg/180 ± 180 o 0.01 o
331 Body Long-accel. 6.25* 12 g 4 0.001
334 Free Heading 20* 12* Deg/180 ± 180 o 0.05 o
335 Track Angle Rate * * * * *
336 Inertial Pitch Rate 20 12* Deg/sec 128 0.03 o *
337 Inertial Roll Rate 20 12* Deg/sec 128 0.03 o *
340 N1 Actual * 200 12 RPM 4096 1
341 N1 Command 200 12* RPM* 4096* 1*
342 N1 Limit 200 12* RPM* 4096* 1*
343 N1 Derate 200 12* RPM* 4096* 1*
344 N2 100 14 RPM* 16384* 1*
SUPPLEMENT 2 TO ARINC SPECIFICATION 429 - Page 8

Table 2 BNR Data (cont’d)

Label Parameter Max Sig. Bits Approx.

(Octal) Name Transmit (Not Inc. Units Range Resol.
Interval Sign)
O
345 Exhaust Gas Temp. 200 11* C* 2048 1*
346 N1 Actual 200 12* RPM* 4096* 1*
347 Fuel Flow 200 11* Lbs/hr 32768 16*
362 Along Track Horiz. Accel. 50* 12 g 4 0.001
365 Integrated Vertical Accel. 50* 15* Knots 4096* 0.125*
366 N-S Velocity 200* 15 Knots 4096 0.125
367 E-W Velocity 200* 15 Knots 4096 0.125

Note: Labels 110, 112, 130, 131, 132, 133, 241, 245, 247, 346,
360, 372, 373, 374 and 376 previously had no values
assigned. Values for label 216 have been deleted.

*This data has been changed.

Attachment 6: General Word Formats and Encoding Examples

AIM word format examples have been added. Detailed

descriptions of these words have been included in the text of
Section 2.3.1.3.
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401- 7645 USA

SUPPLEMENT 3

TO

ARINC SPECIFICATION 429

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

Published: November 1, 1979

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: August 31, 1979

SUPPLEMENT 3 TO ARINC SPECIFICATION 429 - Page 2

A. PURPOSE OF THIS SUPPLEMENT ORIGINAL TEXT FOLLOWS:

This Supplement introduces material on the transfer of 2.1.6 Data Standards

file data and the related protocol. The file transfer
capability is being added primarily for the Flight The units, ranges, resolutions, refresh rates, number of
management Computer (FMC) program/data load and significant bits, pad bits etc. for the items of
update and FMC intersystem crosstalk. A number of information to be transferred by the Mark 33 DITS are
labels and corresponding data standards have been tabulated in Attachment 2 to this document.
added.
COMMENTARY
B. ORGANIZATION OF THIS SUPPLEMENT
Note that Section 2.3.1.1 of this document calls for
The first part of this document, printed on goldenrod numeric data to be encoded in BCD and binary, the
paper, contains descriptions of the changes introduced latter using two’s complement fractional notation.
into the Specification by this Supplement; and, where In this notation, the most significant bit of the data
appropriate, extracts from the original text for filed represents one half of the maximum value
comparison purposes. The second part consists of chosen for the parameter being defined.
replacement white pages for the Specification, modified Successive bits represents the increments of a
to reflect these changes. The modified and added binary fraction series. Negative number are
material on each replacement page is identified with “c- encoded as the complements of positive values and
3” symbols in the margins. Existing copies of the negative sign is annunciated in the sign/status
Specification 429 may be updated by simply inserting matrix.
the replacement white pages where necessary and
destroying the pages they replace. The goldenrod pages In establishing a given parameter’s binary data
should be inserted inside the rear cover of the standards for inclusion in Attachment 2, the units,
Specification. maximum value and resolution of the parameter
are first determined in that order. The least
Copies of the Specification bearing the number 429-3 significant bit of the word is then given a value
already contain this Supplement and thus do not require equal to the resolution increment, and the number
revisions by the reader. of significant bits is chosen such that the maximum
value of the fractional binary series just exceeds
C. CHANGES TO SPECIFICATION 429 the maximum value of the parameter, i.e., equals
INTRODUCED BY THIS SUPPLEMENT the next whole binary number greater than the
maximum parameter value less one least
This section presents a complete tabulation of the significant bit value. For example, if the Mark 33
changes and additions to the Specification introduced DITS is required to transfer altitude in units of feet
by this Supplement. Each change or addition is entitled over a range of zero to 100,000 feet with a
by the section number and title currently employed in resolution of one foot, the number of significant
the Specification or by the section number and title that bits is 17 and the maximum value of the fractional
will be employed when the Supplement is eventually binary series is 131,071 (i.e., 131,071 – 1). Note
incorporated. In each case there is included a brief that because accuracy is a quality of the
description of the addition or change and, for other than measurement process and not the data transfer
very minor revisions, any text originally contained in process, it plays no part in the selection of word
the Specification is reproduced for reference. characteristics. Obviously, the resolution provided
in the DITS word should equal or exceed the
2.1.5.1 BCD NUMERIC, DISCRETE AND AIM accuracy in order not to degrade it.
DATA WORDS
For the binary representation of angular data, the
Table amended to provide consistency between AIM Mark 33 DITS employs “degrees divided by 180o”
and file transfer data words. as the unit of data transfer and ± 1 (semicircle) as
the range for two’s complement fractional notation
ORIGINAL TEXT FOLLOWS: encoding ignoring, for the moment, the subtraction
of the least significant bit value. Thus the angular
Bit No. Designation range 0 through 359.XXX degrees is encoded as 0
31 30 BCD Numeric Data AIM Data through ± 179.XXX degrees, the value of the most
Plus, North East significant bit is none half semicircle and there are
0 0 Right, To Final Word no discontinuities in the code.
Intermed.
0 1 No Computed Data For convenience, all binary word ranges in
Word
1 0 Functional Test Control Word Attachment 2 are shown as whole binary numbers
Minus, South rather than such numbers less one least significant
1 1 West, Left, From Initial Word bit value. Also the resolutions shown are
approximate only. Accurate resolutions can be
2.1.6 DATA STANDARDS determined, if required, by reference to the range
values and numbers of significant bits for the
Text added to clarify data encoding. words of interest.
 SUPPLEMENT 3 TO ARINC SPECIFICATION 429 - Page 3

2.1.6 Data Standards (cont’d) 3.1.4.3 HF COMMUNICATIONS

COMMENTARY (cont’d) Text amended to describe switching functions and finer

frequency selection increments.
It should be noted that in all applications of the
two’s complement fractional notation, the ORIGINAL TEXT FOLLOWS:
maximum value of the word, once chosen, cannot
be changed by the use of more bits in the data field. 3.1.4.3 HF Communications
The number of bits in the word affects only the
resolution of the data, not its range. Frequency Range: 2.8MHz to 24MHz
Frequency Selection 1kHz
Binary coded decimal (BCD) data is encoded per Increments
the numeric subset of the ISO Alphabet No. 5 code Characters encoded 10MHz, 1MHz, 0.1MHz,
(see Attachment 5 to this document) using bit nos. in DITS word: 0.01MHz, 0.001MHz
1 through 4 of the seven-bit-per-character code. Switching Functions: USB/AM mode selection
Alpha/numeric data is encoded using all seven bits
per character of the ISO Alphabet #5 code and is
transmitted using the special word format Fig. 3-1 RADIO SYSTEMS MANAGEMENT WORD
described in Section 2.3.1.3 of this document. FORMATS

Error corrected in bits 24 and 25 of ILS word.

2.3.1.5 FILE DATA TRANSFER
HF COMM frequency word format changed and
Section added to provide description of file data second word added to enable the use of 100 Hz channel
transfer protocol. spacing.

ORIGINAL TEXT FOLLOWS:

HF COM

RESERVED (SDI)
USB/AM MODE
SIGN/STATUS
PARITY (Odd)

Function LABEL
HF COM Frequency
0.001MHz
MATRIX

0.01MHz
0.1MHz
10MHz

(9)
1MHz

(7)
(2)

(5)
(3)

Bit No. 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Example 0 0 0 0 1 0 0 0 1 1 0 1 0 1 0 1 1 1 1 0 0 1 0 0 1 1 1 1 1 0 0 0
Notes [1] [2]

[1] When bit no. 10 is “zero” the equipment should operate in the AM mode. When bit
no. 10 is “one” the equipment should operate in the SSB (USB) mode.
[2] Only bit no. 9 is available for the SDI function in this word.

ATTACHMENT 1: LABEL CODES

The following labels have been given new assignments:

053, 056, 060, 061, 062, 063, 065, 066, 067, 070, 071, 075, 076, 077, 120, 126, 134, 137, 143, 175, 176, 177, 200, 217,
226, 251, 252-256, 257, 260, 261, 277, 300-307, 361.
ATTACHMENT 2: DATA STANDARDS

Tables 1 and 2 have both additions and modifications made to the data standards. Notes 2 thru 5 deleted. The original
information provided in ARINC 429-2 is included in these tables. An asterisk beside a value designated that a change
has been recommended. The formats of table 1 and 2 have also been changed to provide the addition of data standard
descriptors.

Table 3.7 added for GPWS discretes.

 SUPPLEMENT 3 TO ARINC SPECIFICATION 429 - Page 4

ATTACHMENT 2: DATA STANDARDS (cont’d)

TABLE 1 BCD DATA

MAX.
LABEL PARAMETER TRANSMIT RANGE SIG. PAD
(OCTAL) NAME (SCALE FIG. FIG. UNITS RESOL
INTERVAL
msec

0 1 0 Present Position-Lat. 200* 90S-90N 5 0 Deg/Min* 0.1

0 1 1 Present Position-Long. 200* 180E-180W 6 0 Deg/Min* 0.1
0 1 2 Ground Speed 200* 0-2000 4 1 Knots 1.0
0 1 3 Track Angle (true) 200* 0-359.9 4 1 Deg 0.1
0 1 4 Magnetic Heading 200* 0-359 3 2 Deg 1.0
0 1 5 Wind Speed 200* 0-299 3 2 Knots 1.0
0 1 6 Wind Direction (true) 200* 0-359 3 2 Deg 1.0
0 4 1 Set Latitude 200* 90S-90N 5 0 Deg/Min 0.1
0 4 2 Set Longitude 200* 180E-180W 6 0 Deg/Min 0.1
0 4 3 Set Magnetic Heading 200* 0-359.9* 4* 1* Deg 0.1*
1 2 5 Greenwich Mean Time 200 0-23.59.9 5 0 Hr/Min* 0.1
# 2 3 0 True Airspeed 62.5* 100-599 3 0 Knots 1.0

TABLE 2 BNR DATA

MAX.
LABEL PARAMETER TRANSMIT SIG. BITS
(OCTAL) NAME (NOT INC. UNITS RANGE APPROX
INTERVAL
msec SIGN) See Note 1 RESOL
1 0 0 Selected Course #1 50 9* Deg/180 ±180o 0.35*
1 0 1 Selected Heading 62.5 9* Deg/180 ±180o 0.35*
1 0 5 Selected Runway Heading 62.5 9* Deg/180 ±180o 0.35*
1 1 0 Selected Course #2 50 9* Deg/180 ±180o 0.35*
1 1 6 Cross Track Distance 62.5 8* N.M. 128 0.5*
1 2 1 Horiz. Steering Signal 100 10* Deg/180 ±60 o 0.06*
1 2 2 Vertical Steering Signal 100 9* Deg/180 ±30 o 0.06*
1 2 3 Throttle Command * * * * *
o
1 3 0 Tt2* 200 11 C 128 0.06
1 3 1 Pt2* 200 13 PSIA 32 0.004
1 3 2 Pt7* 200 13 PSIA 32 0.004
1 4 0 Flight Director-Roll 100 9* Deg/180 ±45 o * 0.1*
1 4 1 Flight Director-Pitch 100 9* Deg/180 ±22.5 o 0.05
1 4 2 Fast/Slow 62.5 8* Knots 32 0.125*
1 4 3 Flight Director-Yaw* 100* 12* Deg/180* ±180 o 0.05*
1 6 4 Radio Height 50 17* Feet 16384* 0.125
2 0 3 Altitude (1013.25mb) 62.5 18* Feet 131,072 0.05*
2 1 0 True Airspeed 62.5* 11* Knots 2048 1.0*
o
2 1 1 Total Air Temp. 500 10* C 512 0.5*
o
2 1 3 Static Air Temp. 500 10* C 512 0.5*
2 2 1 Indicated Angle of Attack 62.5 11* Deg/90* ±90 o * 0.05
2 4 1 Corrected Angle of Attack 62.5 11* Deg/90* ±90 o * 0.05
2 4 7 Total Fuel 200* 15* Lb. 655,360 20*
3 1 0 Present Position-Lat. 200 18* Deg/180 0-90N-0-90S 0.00035*
3 1 1 Present Position-Long. 200 18* Deg/180 0-180E-0-180W 0.00070*
3 1 2 Ground speed 100* 15 Knots 4096 0.125
3 1 3 Track Angle True 40* 12 Deg/180 ±180 o 0.05
3 1 4 True Heading 40* 12 Deg/180 ±180 o 0.05
3 1 7 Track Angle-Mag 40* 12 Deg/180 ±180 o 0.05
3 2 0 Magnetic Heading 40* 12 Deg/180 ±180 o 0.05
3 2 1 Drift Angle 40* 11* Deg/180 ±90 o * 0.05
3 2 2 Flight Path Angle 40* 10* Deg/180 ±45 o * 0.05
3 2 4 Pitch Angle 20* 13* Deg/180 ±90 o * 0.01
3 2 5 Roll Angle 20* 14 Deg/180 ±180 o 0.01
3 6 0 Potential Vertical Speed 50 10* Ft/min* 16384* 16*

# The change to MTI was erroneously omitted from Draft 1 of Supplement 3, but was included prior to publication of
Supplement 3.
 SUPPLEMENT 3 TO ARINC SPECIFICATION 429 - Page 5

ATTACHMENT 2: DATA STANDARDS (cont’d)
NOTES
1. The number entered in the Range Column for each
parameter that is not angular in nature is the
nearest whole binary number greater than the
parameter range required. As explained in the
Commentary following Section 2.1.6 of this
document, the weight of the most significant bit of
the two’s complement fractional notation binary
word will be one half this value, and the actual
maximum value of the parameter capable of being
encoded will be the number in the range column
less one least significant bit value. The numbers
entered in the RANGE column for angular
parameters are the actual degree ranges required.
The way in which these parameters are encoded is
also explained in the Commentary following
Section 2.1.6.
4. A change in ARINC 710 not shown in Supplement
2 is a planned change for Supplement 3. The
resolution of Selected Runway Heading (BCD and
BNR) will be changed to .1 o.
5. A change being considered for Supplement 3 is to
change the range to –6g - +4g to facilitate direct
recording by the flight recorder.
ATTACHMENT 6: GENERAL WORD FORMATS &
ENCODING EXAMPLES
SSM codes in AIM words changed to reflect table
amendment of section 2.1.5.1.
Radio Height code example changed to reflect shift in
field.
Note 4 of Table 6.2 deleted to revert data coding to the
original two’s complement notation.

2. Bit nos. 9 and 10 of the word may be used to Word formats added for date/flight leg and flight
achieve a 20 bit capability for high resolution of number information.
the Lat./Long. Position (codes 310 and 311). The
resulting resolution is .000086o for latitude and Word format added for VOR Omnibearing.
.00017 o for longitude.
Codes 203, 204, 206 and 207 deleted in Table 6.1a.
3. A change in ARINC 707 not shown in Supplement
2 is a planned change for Supplement 3. A self-
test inhibit bit will be added and the range of the
data word will be halved to a value of 8192 ft.

ORIGINAL TEXT FOLLOWS:

ATTACHMENT 6

GENERAL WORD FORMATS AND ENCODING EXAMPLES

1. GENERAL WORD FORMATS

SUPPLEMENT 3 TO ARINC SPECIFICATION 429 - Page 6

ATTACHMENT 6: GENERAL WORD FORMATS & ENCODING EXAMPLES (cont’d)

 SUPPLEMENT 3 TO ARINC SPECIFICATION 429 - Page 7

ATTACHMENT 6: GENERAL WORD FORMATS & ENCODING EXAMPLES (cont’d)

DME DISTANCE WORD

Attachment 6 (cont’d)
GENERAL WORD FORMATS AND ENCODING EXAMPLES

NOTES

[1] Source/Destination Identifier (SDI) Field

The purpose of the SDI field is explained in

Section 2.1.4 of this document, as are also the
limitations on its use. When the SDI function is
not required, this field may be occupied by binary
zero or valid data pad bits.

[2] Discretes
As discussed in Section 2.3.1.2 of this document,
unused bits in a word may be assigned to discrete
functions, one bit per variable. Bit #11 of the
word should be the first to be so assigned;
followed by bit #12 and so on in ascending
numerical order until the data field is reached. In
the absence of discretes, unused bit positions
should be occupied by binary zero or valid data
pad bits.

[3] Pad

All bit positions not used for data or discretes

should be filled with binary zero or valid pad bits.
Section 2.1.2 of this document refers.

[4] Sign/Status Matrix (SSM)

Section 2.1.5 of this document describes the

functions of the sign/status matrix and the ways in
which the bits constituting it are encoded.

[5] Parity Bit

This bit is encoded to render word parity odd.
Section 2.3.4 of this document refers.
SUPPLEMENT 3 TO ARINC SPECIFICATION 429 - Page 8

TABLE 6-1a

BCD DATA ENCODING EXAMPLES

NOTES: [1] “P” denotes pad “zero” or valid data. Section 2.1.2 if this document refers. Note possible use
of pad bits for discrete functions per Section 2.3.1.2.

[2] Because the actual maximum value of the most significant character of each of these quantities
exceeds 7, it cannot be encoded in the most significant character position of the BCD word. For
this reason each quantity has been given and “artificial” MSC of zero and its actual MSC
encoded in the next most significant character position of the word.
 SUPPLEMENT 3 TO ARINC SPECIFICATION 429 - Page 9

TABLE 6-2

BNR DATA ENCODING EXAMPLES

NOTES: [1] “P” denotes pad “zero” or valid data. Section 2.1.2 of this document refers. Note possible use
of pad bits for discrete functions per Section 2.3.1.2.

[2] Negative values are encoded as the two’s complements of positive values and the negative sign
is annunciated in the sign/status matrix.

[3] Angles in the range 0 to 180o are encoded as positive numbers. Angles in the range 180 o to 360 o
are subtracted from 360 o and the resulting number encoded as a negative value per note 2. Arc
minutes and seconds are encoded as decimal degrees.

[4] Latitude values are encoded as positive angles in the range 0 to 90 o with the sign/status matrix
indicating North or South. Longitude values are encoded as positive angles in the range 0 to
180 o with the sign/status matrix indicating East or West. Arc minutes and seconds are encoded
as decimal degrees.
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401 – 7645 USA

SUPPLEMENT 4
TO

ARINC SPECIFICATION 429

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

Published: August 1, 1980

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: June 17, 1980

SUPPLEMENT 4 TO ARINC SPECIFICATION 429 - Page 2
A. PURPOSE OF THIS SUPPLEMENT
This Supplement introduces material on defining “No
Computed Data” and “Failure Warning”, priority
assignment of SSM codes, description of fault tolerance
and isolation, address capability of A/N messages,
command/response protocol, modification of data
standards, addition of new labels, change of some word
formats, addition of material on signal characteristics,
change of receiver impedance limits, expansion of the
current label, change of the receiver voltage thresholds and
modification of the HF and DME word formats.
B. ORGANIZATION OF THIS SUPPLEMENT
The first part of this document, printed on goldenrod paper,
contains description of the changes introduced into the
Specification by this Supplement, and, where appropriate,
extracts from the original text for comparison purposes.
The second part consists of replacement white pages for
the Specification, modified to reflect these changes. The
modified and added material on each replacement page is
identified with “c-4” symbols in the margins. Existing
copies of Specification 429 may be updated by simply
inserting the replacement white pages where necessary and
destroying the pages they replace. The goldenrod pages
should be inserted inside the rear cover of the
Specification.
Copies of the Specification bearing the number 429-4
already contain this Supplement and thus do not require
revisions by the reader.
C. CHANGES TO SPECIFICATION 429 INTRODUCED
BY THIS SUPPLEMENT
This section presents a complete tabulation of the changes
and additions to the Specification introduced by this
Supplement. Each change or addition is entitled by the
section number and title currently employed in the
Specification, or the section number and title that will be
employed when the Supplement is eventually incorporated.
In each case there is included a brief description of the
addition or change and, for other than very minor
revisions, any text originally contained in the Specification
is reproduced for reference.
2.1.3 INFORMATION IDENTIFIER
Text changed to describe use of five-character label.
Commentary text partially deleted.
ORIGINAL TEXT FOLLOWS:
2.1.3 Information Identifier
The first eight bits of each word are assigned to a label
function. Label will:
a. identify the information contained within BNR
and BCD numeric data words (e.g., DME distance,
static air temperature, etc.) and
b. identify the word application for Discrete,
Maintenance and AIM data.
Label code assignments are set forth in Attachment 1 to
this document.
Special Note:
In some ARINC 429 DITS applications, a bus will be
dedicated to delivering a single information element from a
source to one or more identical sink devices. In such
circumstances, the sink device designer might be tempted
to assume that decoding the word label is not necessary.
Experience has shown, however, that system developments
frequently occur that result in the need for additional
information elements to appear on the bus. If a sink device
designed for service prior to such a development cannot
decode the original word label, it cannot differentiate
between this word and the new data in the new situation.
The message for sink designers should therefore be quite
clear – provide label decoding from the outset, no matter
how strong the temptation to omit it might be.
COMMENTARY
Attachment 1 defines 256 discrete label codes. This
quantity is expected to meet label assignment needs
for the foreseeable future. Should additional labeling
capability be required in the longer term, it is
envisaged that, rather than extend the length of the
label field, a scheme will be devised in which existing
label assignments are duplicated. For example, the
system could readily accommodate the assignment of
the same label to two dissimilar parameters for which
the probability of transmission on the same bus is very
low.
Adherence to the label code assignments of
Attachment 1 is essential in inter-system
communications and in intra-system communications
where the system elements are defined as “unit
interchangeable” per ARINC Report No. 403. The
assignment of label codes for all such communications
must be coordinated with the air transport industry if
chaos is to be avoided. A manufacturer who finds that
Attachment 1 does not specify the label he needs for
such system application must not simply choose one
from those unassigned and “drive on”. He should
contact ARINC for assistance.
2.1.5.1 BCD NUMERIC, DISCRETE, AIM DATA AND
FILE TRANSFER WORDS
Text describing “no computed data” modified.
Commentary providing definitions added.
ORIGINAL TEXT FOLLOWS:
2.1.5.1 BCD Numeric, Discrete, AIM Data and File
Transfer Words
The sign (Plus, minus, North, South, etc.) of BCD numeric
data, the word type (first, intermediate, control, last) for
AIM data, and the status of the transmitter hardware should
be encoded in bit nos. 30 and 31 of the word as shown in
the table below. The sign/status matrices of Discrete
words should be encoded per the rules set forth for BCD
numeric data.
 SUPPLEMENT 4 TO ARINC SPECIFICATION 429 - Page 3

Bit No. Designation ORIGINAL TEXT FOLLOWS:

BCD Numeric
31 30 Word AIM File Transfer 2.1.5.2 BNR Numeric Data Words
Plus, North Intermediate Intermediate
0 0 East, Right Word, Plus, The sign (plus, minus, north, south, etc.) of BNR numeric
Word data words and the status of the transmitter hardware
To, Above North, etc.
No Computed should be encoded in bit nos. 29, 30 and 31 of the word as
0 1 Data Initial Word Initial Word shown in the table below.
Functional
1 0 Test Final Word Final Word Bit No. Designation
Minus, South Intermediate 31 30 29 BNR Data
1 1 West, Left, ControlWord Word, Minus Failure Warning/Plus, North, East
0 0 0
From, Below South, etc. Right, To
Failure Warning/Minus, South, West
0 0 1 Left, From
0 1 0 No Computed Data
Notes: Functional Test/Plus, North, East,
1 0 0
Right, To
1. A source system should annunciate any detected Functional Test/Minus, South, West
1 0 1
failure that causes one or more of the words normally Left, From
output by that system to be unreliable by ceasing to Normal Operation/Plus, North, East,
supply the affected word or words to the data bus. 1 1 0 Right, To
Normal Operation/Minus, South
2. Bit nos. 30 and 31 of BCD numeric data words should 1 1 1 West, Left, From
be “zero” when no sign is needed. 0 1 1 Not Used (Growth)
3. The “no computed data” code should be generated for Notes:
BCD numeric data words when computed data is not
available for reasons other than equipment failure. 1. A source system should annunciate any detected
failure that causes one or more of the words normally
4. When it appears in a BCD numeric data word output by that system to be unreliable by setting bit
identified by its (label) as a system output, the nos. 30 and 31 in the affected word(s) to the “failure
“functional test” code should be interpreted as advice warning” code defined above. Words containing this
that the data in the word results from the execution of code should continue to be supplied to the data bus
a functional test. When it appears in a BCD numeric during the failure condition.
data word identified by its label as an instruction, e.g.,
a radio channel change command, this code should be 2. Bit no. 29 should be “zero” when no sign is needed.
interpreted as a command to perform a functional test.
A self-test should produce indications of 1/8 of 3. The “no computed data” code should be generated
positive full-scale values unless indicated otherwise in when computed data is not available for reasons other
an ARINC Equipment Characteristic. than equipment failure.
5. See Section 2.3.1.3 of this document for definitions of 4. When it appears in a word identified by its label as a
the terms “Initial Word”, “Control Word”, system output, the “functional test” code should be
“Intermediate Word” and “Final Word.” interpreted as advice that the data in the word results
from the execution of a functional test. A self-test
should produce indications of 1/8 of positive full-scale
2.1.5.2 BNR NUMERIC DATA WORDS values unless indicated otherwise in an ARINC
Equipment Characteristic.
Table modified to permit sign coding for “no computed
data”. 5. If, during the execution of a functional test, a source
system detects a failure which causes one or more of
Definition of “failure warning” and “no computed data” the words normally output by that system to be
added. unreliable, it should immediately change the states of
bits nos. 30 and 31 in the annunciation to the “failure
warning” annunciation.
SUPPLEMENT 4 TO ARINC SPECIFICATION 429 - Page 4
2.1.5.3 STATUS PRIORITIES
New section inserted.
2.2.1 TRANSMISSION SYSTEM INTERCONNECT
Commentary expanded to provide description of possible
solutions to single-wire fault conditions.
ORIGINAL TEXT FOLLOWS:
2.2.1 Transmission System Interconnect
A data source should be connected to the data sink(s) by
means of a single twisted and shielded pair of wires. The
shields should be grounded at both ends and at all
production breaks in the cable. The interwiring diagram to
be found in each ARINC Equipment Characteristic shows
connector pins assigned to carry shields into black boxes
for grounding. Equipment manufacturers should ensure,
however, that their equipment will operate correctly if,
instead of being terminated on these pins, shields are
grounded in the aircraft close to the rack connector.
COMMENTARY
In practical wire line digital information transmission
systems, cable characteristics and electrical
mismatches can produce distortion of the digital data
pulses. Also, noise due to electrical interference
perturbs digital signals.
The performance of a digital receiver depends upon
the receiver input signal characteristics (data with
distortion and noise) and the receiver design.
Prior to the selection of the voltage and impedance
parameters set forth in this Section of this document,
the pulse distortion likely to be encountered in systems
built around them in existing size commercial aircraft
was evaluated and judged to be acceptable for a well-
designed receiver. No restriction is placed by this
specification, therefore, on the number or length of
sturbs for installations on aircraft no larger than those
existing, e.g., B 747. See Appendix 1 to this
document for a report of this investigation.
2.2.3.1 TRANSMITTER VOLTAGE LEVELS
Text changed to improve clarity.
ORIGINAL TEXT FOLLOWS:
2.2.3.1 Transmitter Voltage Levels
The differential output signal across the specified output
terminals (balanced to ground at the transmitter) should be
+ 10 ± 1.0 volts, 0 ± 0.5 volts and –10 ± 1.0 volts
respectively for the “HI”, “NULL” and “LO” states when
the transmitter is open circuit. The output impedance of
the transmitter should be as specified in Section 2.2.4.1 of
this document. This output impedance should be present
for the “HI”, “NULL” and “LO” transmitter output
conditions and also during transitions between these levels.
2.2.3.2 RECEIVER VOLTAGE LEVELS
Receiver voltage thresholds changed.
Fault voltage text deleted.
Commentary revised to include description of receiver
reaction to undefined voltages.
ORIGINAL TEXT FOLLOWS:
2.2.3.2 Receiver Voltage Levels
The differential voltage presented at the receiver input
terminals will be dependent upon line length, stub
configuration and the number of receivers connected. In
the absence of noise, the normal ranges of voltages
presented to the receiver terminals (A and B) would be:
“HI” +6V to 10V
“NULL” +0.5 to –0.5V
“LO” -6V to –10V
In practice, these nominal voltages will be perturbed by
noise and pulse distortion. Thus, receivers should
associate the following voltage ranges with the three states
indicated:
“HI” +5V to 13V
“NULL” +2.5V to –2.5V
“LO” -5V to –13V
Receivers should not be damaged by the application of up
to 20VAC (RMS) across terminals A and B by the
application of up to +28VDC (min) bias between terminal
A and ground and –28VDC (min) bias between terminal B
and ground. See Attachment 3 to this document for a
pictorial representation of transmitter and receiver voltage
levels.
COMMENTARY
Receiver input common mode voltages (terminal A to
ground and terminal B to ground) are not specified
because of the difficulties of defining ground with any
satisfactory degree of precision. Receiver
manufacturers are encouraged to work with the
differential input voltage (line A to line B) and not
line-to-ground voltages.
The opinion is held by some people that conditions on
transmission lines will be encountered which will
require receivers to operate with less than the above-
defined minimum difference of 2.5V between the
NULL and HI and NULL and LO states. Receiver
designers are encouraged to investigate the
possibilities and problems of working with a minimum
difference of 1 volt between these states and to report
their findings.
2.2.4.1 TRANSMITTER OUTPUT IMPEDANCE
Text added to improve clarity.
 SUPPLEMENT 4 TO ARINC SPECIFICATION 429 - Page 5
ORIGINAL TEXT FOLLOWS:
2.2.4.1 Transmitter Output Impedance
The transmitter output impedance should be 75 ± 5 ohms,
divided equally between line A and line B to provide an
impedance balanced output.
COMMENTARY
The output impedance of the transmitter is specified as
75 ± 5 ohms to provide an approximate match to the
characteristic impedance of the cable. The match can
only be approximate due to the wide range of
characteristic impedance which may be encountered
due to the variety of conductor wire gages and
insulation properties. Measurements on a few samples
of wire showed a spread of characteristic impedance
of 63 and 71 ohms. An extrapolation over the wire
gages 20 to 26 for wrapped and extruded insulation
indicate an expected characteristic impedance spread
of 80 to 60 ohms approx. Twisted shielded wire
specifications do not control the characteristic
impedance of the cable, thus future developments in
insulation techniques may result in cables having
characteristic impedances outside the range estimated.
2.2.4.2 RECEIVER INPUT IMPEDANCE
Value of RI changed.
ORIGINAL TEXT FOLLOWS:
2.2.4.2 Receiver Input Impedance
The receiver should exhibit the following characteristics,
measured at the receiver input terminals:
Differential Input Resistance RI = 6,000 ohms minimum
Differential Input Capacitance CI = 50pF maximum
Resistance to Ground RH and RG ≥ 12,000 ohms
Capacitance to Ground CH and CG ≤ 50pF.
No more than twenty receivers should be connected on to
one digital data bus and each receiver should incorporate
isolation provisions to ensure that the occurrence of any
reasonably probable failure does not cause loss of data to
the others.
See Attachment 4 to this document for a pictorial
representation of the input and output circuits standards.
COMMENTARY
The above characteristics apply to differential
amplifier receivers. Opto-isolator technology is
progressing and may soon find application in digital
data receivers. Opto-isolator receivers impose
slightly greater loads on data buses than differential
amplifier receivers and the way in which they are
characterized is different. It is probable, however, that
a future revision of this Specification will include
material specifically related to their use.
2.2.5 Fault Tolerance
New section inserted.
2.2.5.1 Receiver External Fault voltage Tolerance
New section inserted.
2.2.5.2 Transmitter External Fault Voltage Tolerance
New section inserted.
2.2.5.3 Transmitter External Fault Load Tolerance
New section inserted.
2.2.6 Fault Isolation
New section inserted.
2.2.6.1 Receiver Fault Isolation
New section inserted.
2.2.6.2 Transmitter Fault Isolation
New section inserted.
2.3.1.2 Discretes
Text modified to expand label examples.
Reference to AIDS limitations deleted.
ORIGINAL TEXT FOLLOWS:
2.3.1.2 Discretes
In addition to handling numeric data as specified above,
the Mark 33 DITS should also be capable of
accommodating discrete items of information either in the
unused (pad) bits of data words or, when necessary, in
dedicated words. Any discrete information contained in a
numeric data word assigned a label in Attachment 1 is
specified in the definition for that word in Attachment 2.
The rule to be followed in the assignments of bits to
discretes in numeric data words is to start with the least
significant bit of the word and to continue towards the
most significant bit available in the word. Attachment 6
shows that this against the background of the generalized
word structure.
There are two types of discrete words. These are general
purpose discrete words, and dedicated discrete words. Five
labels (octal 270-274) are assigned to the general purpose
words in Attachment 1. These words should be used in
ascending label order (starting with octal 270) when the
system receiving the data can identify its source by
reference to the port at which it arrives. The dedicated
words should be used when the
SUPPLEMENT 4 TO ARINC SPECIFICATION 429 - Page 6
2.3.1.2 Discretes (cont’d)
data is intended for the AIDS DFDAU which cannot
identify sources in this way.
COMMENTARY
The foregoing special provisions for the delivery of
discrete data to an AIDS were made to compensate for
the number of digital ports required when many ports
are used is extremely difficult to achieve, which
necessitated the development of the special AIDS
words. These words should be limited to AIDS
utilization. The few aircraft systems which deliver
discretes to an AIDS by means of the Mark 33 DITS
will be burdened very little by this. Similarly, the
impact of label use will be small.
2.3.1.4 AIM DATA
Text added to describe unit addressing.
ORIGINAL TEXT FOLLOWS:
2.3.1.4 AIMS Data
AIM data (Acknowledgement, ISO Alphabet No. 5 and
Maintenance information encoded in dedicated words)
should be handled in the manner described in this Section.
All three of these applications may involve the transfer of
more than 21 bits per “data package”. Source equipment
should format such long messages into groups of 32-bit
DITS words, each word containing the relevant application
label (see Attachment 1) in bit nos. 1 through 8, and a
sign/status matrix code in bit nos. 30 and 31.
Bit no. 32 should be encoded to render word parity odd.
The first word of each group should contain the sign/status
matrix code defined for “initial word” in Section 2.1.5.1 of
this document. It should also contain, in bit nos. 9 through
16, the binary representation of the number of words in the
group, except that when this word is the only word to be
transmitted, i.e., the total number of information bits to be
transmitted is 13 or less, bit nos. 9 through 16 should all be
binary “zeros”.
When the word application label is assigned in Attachment
1 for Acknowledgement Data, bit nos. 17 through 29 of
this initial word may be used for information transfer.
When the word application label is either of those assigned
in Attachment 1 for ISO Alphabet No. 5 data transfer or
Maintenance Data (ISO Alphabet Not. 5), bit nos. 17
through 22 should be binary “zeros” (spares) and bit nos.
23 through 29 should take on the pattern of the ISO
Alphabet No. 5 control character “STX”.
The second word of the ISO Alphabet No. 5 and
Maintenance Data (ISO Alphabet No. 5) application
groups is an optional control word containing the
sign/status matrix code for “control” information for the
display. When it is used, bit nos. 9 through 13 should
contain the binary representation of the line count, bit nos.
14 through 16 should encode the required color, bit nos. 17
and 18 the required intensity, bit nos. 19 and 20 the
required character size and bit no. 21 should indicate
whether or not the display is required to flash. See
Attachment 6 to this document for the encoding standards.
Bit nos. 22 through 29 of the word should be binary “zero”
(spares).
Intermediate words, containing the sign/status matrix code
for “intermediate word”, follow the initial word of the
group or the control word, when used. Intermediate words
are optional in the sense that they are only transmitted if
more words than the initial word and the final word (see
below) are needed to accommodate the quantity of
information to be transferred. When the word application
group label that is assigned in Attachment 1 for
Acknowledgement, Data bit nos. 9 through 29 of that word
are available for information transfer. When the word
application label is either of those assigned in Attachment
1 for ISO Alphabet No. 5 data transfer or Maintenance
Data (ISO Alphabet No. 5), bit nos. 9 through 29 of each
word should be divided into three seven-bit bytes (bit nos.
9 through 15, 16 through 22 and 23 through 29), each of
which contains one ISO Alphabet No. 5 character.
Each AIM application group transmission other than
single-word transmissions (see below) should be
terminated with a word containing the sign/status matrix
code for “final word” defined in Section 2.1.5.1 of this
document. The data field of this word should be structured
similarly to that of the intermediate word. Any unused bit
positions in ISO Alphabet No. 5) final transfer or
Maintenance Data (ISO Alphabet No. 5) final words
resulting from the number of ISO Alphabet No. 5
characters in the message being one or two less than a
number wholly divisible by three should be filled with
binary “zeros”.
2.3.1.5.1 COMMAND/RESPONSE PROTOCOL
Text modified to describe transmitter reaction to lack of
“Clear to send”.
ORIGINAL TEXT FOLLOWS:
2.3.1.5.1Command/Response Protocol
File data will consist of both ARINC 429 BNR numeric
words and ISO alphabet No. 5 characters. A file may
contain from 1 to 127 records. Each record may contain
from 1 to 126 data words.
A record will contain, at the minimum, one of the eight
versions of the “initial word” described in Section
2.3.1.5.2. Records in which this initial word contains the
“Data Follows” code will also contain from 1 to 126
“intermediate words” (data) and a “final word” (error
control). The file data transfer protocol is as follows. A
transmitter having the data to send to a receiver transmits,
on the bus connecting it to that receiver, the “Request to
Send” initial word. The receiver responds, on the separate
bus provided for return data flow, with the “Clear to Send”
reply. The transmitter then sends the “Data Follows”
initial word, the “intermediate words” and the “final
word”. The receiver processes the error control
information in the “final word” and, if no errors are
revealed, closes out the transaction by sending the “Data
Received OK” word to the transmitter.
If the receiver is not ready to accept data when the
transmitter sends its “Request to Send” word, it will so
 SUPPLEMENT 4 TO ARINC SPECIFICATION 429 - Page 7
indicate in its response (see Section 2.3.1.5.2). The
transmitter should then wait 200 milliseconds and
retransmit the “Request to Send”. The transmitter should
also repeat a “Request to Send” transmission 50
milliseconds after the initial transmission if no response is
obtained from the receiver. An alert should be raised in the
system containing the transmitter if 4 attempts to obtain a
“Clear to Send” response from a receiver are unsuccessful.
If the receiver detects a parity error during the
transmission, it may request an error-correcting
retransmission by sending a “Data Received Not OK”
word to the transmitter in which is identified the record in
which the error occurred. The transmitter will interrupt the
data flow and back up to the start of the record so
identified. It will then send a “Data Follows” initial word
identifying this record as the starting point of the
retransmission and recommence its output of data,
continuing through the “final word”. The receiver will
then close out the transaction as before.
An error detected by processing the error control
information in the “final word” will also result in the
receiver sending a “Data Received Not OK” word to the
transmitter. In the absence of identification of the record
in which the error occurred, this word should contain the
sequence number of the first record of the file. The
transmitter’s response will be to retransmit the whole file.
The receiver can signal loss of synchronization to the
transmitter at any time by sending the
“Synchronization Lost” initial word. On receiving this
word the transmitter should curtail the data flow and back
up to the beginning of the file. It should then re-establish
that the receiver can accept data by going through the
request-to-send/clear-to-send routine. Having done this it
should send the “Data Follows” initial word, followed by
the data and the “final word”.
The protocol also allows a transmitter to send file size
information to a receiver without any commitment to send,
or request to the receiver to accept, the file itself. The
“Header Information” initial word is used for this purpose.
Additionally, a “Poll” initial word is defined for use in
system in which continuous “handshaking” between two
terminals is desired. The response to a “Poll” word will be
either a “Request to Send” initial word when the polled
terminal does have data to transmit, or another “Poll” word
when it does not. An exchange of “Poll” words may be
interpreted as the message, “ I have nothing for you, do
you have anything for me?”
2.4.2 INFORMATION RATES
Commentary added to describe refresh rate.
ORIGINAL TEXT FOLLOWS:
2.4.2 Information Rates
The minimum update interval for each item of information
transferred by the Mark 33 DITS is specified in the tables
of Attachment 2.
Discretes contained within data words will be transferred at
the bit rate and repeated at the update rate of the primary
data. Words dedicated to discretes should be repeated
continuously at the rates defined in Attachment 2.
COMMENTARY
The time intervals between successive transmissions
of a given BCD word specified in table 1 of
Attachment 2 to this document are, in general, too
short for the signal to be of use in driving a display
device directly. If the signal was so used, the least
significant character of the display would change too
rapidly for human perception. Considerations other
than human factors demand the time intervals
specified. Thus, display designers should incorporate
into their devices means for selecting those words to
be used for updating the display from the greater
quantity delivered.
3.1.4.2 DME
Encoding and switch functions modified.
ORIGINAL TEXT FOLLOWS:
3.1.4.2 DME
Frequency Range: 108.00MHz to 135.95MHz
Frequency Selection: 50kHz
Increment:
Characters encoded10MHz, 1MHz, 0.1MHz,
In DITS word: 0.01MHz, (100MHz
Character is always
Decimal 1)
Switching Functions: Standby, DME Mode
Select ILS Mode
SUPPLEMENT 4 TO ARINC SPECIFICATION 429 - Page 8

FIGURE 3-1 Radio Systems Management Word Formats

HF and DME words modified.

ORIGINAL TEXT FOLLOWS:

DME

DME Mode Select

Function LABEL
SIGN/STATUS
PARITY (odd)

DME Frequency

RESERVED
ILS Mode
MATRIX

0.01MHz

(SDI)
0.1MHz

Standby
10MHz

1MHz

(0)
(1)

(5)
(1)
Bit No. 32 31 30 29 28 27 26 25 24 23 22 21 20 19 1 8 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
1 0 0 0 0 1 0 0 0 1 0 1 0 1 0 0 0 0 0 0 0 0 0 0 1 0 1 1 1 0 0 0
Example
Notes [1] [2] [3]

[1] Bit no. 14 should be set to “zero” for VOR frequencies and “one” for ILS frequencies by
the tuning information source.

[2] [3]
Bit Zero One

11 DME Mode select coding per

12 Section 4.1.6 of ARINC Char. 709
13 Standby off Standby on

HF COM
Word #1

USB/LSB Mode
SIGN/STATUS

Function LABEL

SSB/AM Mode
Word Identifier
PARITY (odd)

HF COM Frequency
0.001MHz
MATRIX

0.01MHz
0.1MHz
10MHz

(9)
1MHz

(7)
(2)

(5)
(3)

Bit No. 32 31 30 29 28 27 26 25 24 23 22 21 20 09 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Example 0 0 0 1 1 0 0 1 1 0 1 0 0 1 1 1 1 0 0 1 0 0 0 1 1 1 1 1 0 0 0
Notes [1] [2] [3]

[1] Bit no. 11 should be set to “zero” for LSB operation and “one” for USB operation.

[2] Bit no. 10 should be set to “zero” for AM operation and “one” for SSB operation.
[3] Bit no. 9 should be set to “zero” when the 100 Hz option is not used and “one” when it is.

HF COM
Word #2
SIGN/STATUS
PARITY (odd)

NOT USED LABEL

MATRIX

Function HF COM Frequency

.1Khz
(5)

Bit No.
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Example
0 0 0 0 1 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 0 0 0

Note: The HF COMM #2 word is used only when bit no. 9 of word #1 is “one”.
 SUPPLEMENT 4 TO ARINC SPECIFICATION 429 - Page 9

ATTACHMENT 1: LABEL CODES ATTACHMENT 2: DATA STANDARDS

Column “EQPT. ID (HEX)” has been added for five-
character label implementation.
Table containing “Equipment ID Codes” added.
The following labels have been given new assignments:
The columns for “bandwidth”, “noise level” and
“update interval” have been deleted. A column for
“minimum transmit interval” has been added. The
column for “transport delay” has been changed to
“maximum transport delay”. A column for “EQPT.ID
(HEX)” has been added.

004, 034, 056, 060-064, 070-106, 111, 114-122, 126, Data standards added for new labels.
127, 135, 136, 140-141, 144-162, 173-177, 202-212,
215, 217, 222-226, 242, 244-252, 256-265, 276, 310- Note [2]: A nominal interval description has been
322, 340-342, 344, 345, 347, 350, 370, 377. added.

Label 226 (FWC #2) deleted. Note [3]: A definition for “maximum transport delay”
has been added.
Labels 124 and 224 (C&W DFDR Discretes) deleted.
Note [4]: SDI assignments defined for labels 060-064.

The following tables list the parameters for which the

data standards have changed. An asterisk beside a
particular value designates that a new value is
suggested.

TABLE 1 BCD DATA

LABEL PARAMETER RANGE SIG. POSITIVE MAXIMUM

UNITS RESOL. TRANSMIT
(OCTAL) NAMES (SCALE) DIG. SENSE
INTERVAL

010 Present Position – Lat. Deg:Min 90S-90N* 5* 0.1 500

017 Selected Runway Heading Deg 0-359.9 4 0.1 200*
024 Selected Course #1 Deg 0-359 3 1.0 200*
027 Selected Course #2 Deg 0-359 3 200*
033 ILS Frequency 200*
034 VOR/ILS Frequency 200*
041 Set Latitude Deg:Min 90S-90N* 5* N 0.1 500
065 Gross Weight 100lb. 0-10000* 5 1.0 200
067 Lateral CG Mlb-in.* ± 100.00* 4* 0.1* 200
200 Drift Angle Deg ± 90* 3* 0.1 200
o
231 Total Air Temperature C -60-+90* 2* 1.0 500
232 Altitude Rate Ft/Min ± 20,000 4 Up 20.0* 62.5
o
233 Static Air Temperature C -99-+60* 2* 1.0 500

TABLE 2 BNR DATA

LABEL PARAMETER SIG. POSITIVE APPROX. MAXIMUM

UNITS RANGE TRNASMIT
(OCTAL) NAME BITS SENSE RESOL.
INTERVAL

077 Lateral CG MLB/in ± 128* 14* 0.001 200

100 Selected Course #1 Deg/180 ± 180o 12 0.05 o 50*
105 Selected Runway Heading Deg/180 ± 180o 11 0.05 o 62.5*
110 Selected course #2 Deg/180 ± 180o 12 0.05 o 50*
173 Localizer Deviation DDM ± 0.4 12 0.0001 62.5*
174 Glideslope Deviation DDM ± 0.8 12 0.0002 62.5*
222 VOR Omnibearing Deg/180 ± 180o 12 0.044 o 62.5*
256 Fuel Quantity #1 Lbs. 131,072 15 4 200*
257 Fuel Quantity #2 Lbs. 131,072 15 4 200*
310 Present Position – Lat. Deg/180 0-90N-0-90S* 20 .000086 o* 200
SUPPLEMENT 4 TO ARINC SPECIFICATION 429 - Page 10

ATTACHMENT 2: DATA STANDARDS (cont’d)

ORIGINAL TEX FOLLOWS:

[2] Transmit intervals and the number of

parameters to be transmitted are prime factors
in bus loading. It was suggested that a
Minimum Transmit Interval be specified
(perhaps a value of ½ the Transmit Interval) to
control bus loading. The ability of receivers to
reject unwanted words would also be effective
in improving bus efficiency.
Table 3.2 FCC DISCRETES – LABELS 270, 271

Existing tables replaced by new set of tables.

ORIGINAL TEXT FOLLOWS:

Table 3.2: FCC Discretes – Labels 270, 271

Discrete Word #1

Bit No. Function Bit Status

1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9* Capt. Flight Director On Off
10* F. O. Flight Director On Off
11 Turbulence Mode Requested Not Requested
12 Autopilot #1 Engaged Not Engaged
13 Autopilot #2 Engaged Not Engaged
14 RESERVED (A/P #3) Engaged Not engaged
15 Autothrottle #1 Armed Not Armed
16 RESERVED (A/T #2) Armed Not Armed
17 Airspeed Hold Mode Requested Not Requested
18 Airspeed Select Mode Requested Not Requested
19 Mach Select Mode Requested Not Requested
20 Mach Hold Mode Requested Not Requested
21
22 Bank Angle Limit See Below
23
24 Heading Select Mode Requested Not Requested
25 N1/EPR Select Mode Requested Not Requested
26 IAS on Throttle Requested Not Requested
27 Mach on Throttle Requested Not Requested
28 Spare
29 Spare
30 Sign/Status
31 Matrix
32 Parity (Odd)
 SUPPLEMENT 4 TO ARINC SPECIFICATION 429 - Page 11

ATTACHMENT 2: DATA STANDARDS (cont’d)

Bank Angle Limit Encoding

Bit nos. 21, 22 and 23 of Discrete Word #1 should be

encoded to indicate selected bank angle limit as follows:
*Bits 9 and 10, which are normally used for the SDI,
have purposely been used for Discrete information.

Bit No.
Limit
21 22 23
Not used 0 0 0
5o 0 0 1
10 o 0 1 0
15 o 0 1 1
20 o 1 0 0
25 o 1 0 1
30 o 1 1 0
Spare 1 1 1

Discrete Word #2

Bit Status
Bit No. Function
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9* Altitude Hold Mode Requested Not Requested
10* Altitude Select Mode Requested Not Requested
11 Vertical Speed Select Mode Requested Not Requested
12 Vertical Speed Hold Mode Requested Not Requested
13 Horizontal Navigation Requested Not Requested
14 Vertical Navigation Requested Not Requested
15 Land Command Requested Not Requested
16 LOC Approach Command Requested Not Requested
17 Back Course Approach Command Requested Not Requested
18 CWS #1 Requested Not Requested
19 CWS #2 Requested Not Requested
20 CWS #3 Requested Not Requested
21 Pitch Upper Mode Cancel Requested Not Requested
22 Roll Upper Mode Cancel Requested Not Requested
23 Heading Hold Requested Not Requested
24
25
26 Spare
27
28
29
30 Sign/Status
31 Matrix
32 Parity (odd)

* Bits 9 and 10, which are normally used for the SDI, have purposely been used for Discrete information.
SUPPLEMENT 4 TO ARINC SPECIFICATION 429 - Page 12

TABLE 3.7 GPWS DISCRETE LABEL 270 23

Visual message bit assignments inserted.

TABLE 3.8 TCC DISCRETES LABELS 272 03, 273
03, 274 03, 275 03

New tables inserted.

ATTACHMENT 3: VOLTAGE LEVELS

Hi and Lo thresholds changed from 5-13 volts to 6.5-13

volts.

ATTACHMENT 4: INPUT/OUTPUT CIRCUIT

STANDARDS

RI increased from 6,000 to 12,000 ohms.

Total system resistance range of 300-6000 ohms
changed to 400-8000 ohms.

ATTACHMENT 6: GENERAL WORD FORMATS

AND ENCODING EXAMPLES

Format for alphanumeric message initial word modified.

Slat/Flap angle word added.

GMT binary word added.

Label Fields changed in discrete word and maintenance

(discrete) word.
In table 6-1b note [1] deleted and bits 21 and 22 of
latitude word interchanged.

In Table 6-2 examples corrected for Present Position

(Latitude and Longitude).
Radio Height word added.

ORIGINAL TEXT FOLLOW:

P SSM “STX” SPARES WORD COUNT LABEL

32 31 (01) 30 29 23 22 (Zeros) 17 16 BNR EQUIV. 9 8 (356/357) 1

ALPHA NUMERIC (ISO ALPHABET NO. 5) DATA – INITIAL WORD FORMAT

P SSM SDI LABEL

DISCRETES
32 31 (00) 30 29 MSB 2 LSB 11 10 9 8 (270-274) 1

DISCRETE WORD FORMAT

P SSM MAINTENANCE DISCRETES SDI LABEL

DISCRETES
32 31 (00) 30 29 MSB LSB 11 10 9 8 (350-354) 1

MAINTENANCE (DISCRETE) WORD FORMAT

APPENDIX 3: DIGITAL SYSTEMS GUIDANCE

(PART 1)

Appendix added.
APPENDIX 4: DIGITAL SYSTEM GUIDANCE
(PART 2)
Appendix added.
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401 – 7645 USA

SUPPLEMENT 5

TO

ARINC SPECIFICATION 429

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

Published: April 4 1981

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: March 12, 1981

SUPPLEMENT 5 TO ARINC SPECIFICATION 429 – Page 2
A. PURPOSE OF THIS SUPPLEMENT
This Supplement introduces material on fault detection,
transmit intervals for words using multiple SDI codes,
modification of IRS/AHRS discrete formats, expansion
of error control definition, revision of ILS word,
addition of new labels and change of existing data
standards.
B. ORGANIZATION OF THIS SUPPLEMENT
The first part of this document, printed on goldenrod
paper, contains descriptions of the changes introduced
into the Specification by this Supplement, and, where
appropriate, extracts from the original text for
comparison purposes. The second part consists of
replacement white pages for the Specification, modified
to reflect these changes. The modified and added
material on each replacement page is identified with “c-
5” symbols in the margins. Existing copies of
Specification 429 may be updated by simply inserting
the replacement white pages where necessary and
destroying the pages they replace. The goldenrod pages
should be inserted inside the rear cover of the
Specification.
Copies of the Specification bearing the number 429-5
already contain this Supplement and thus do not require
revisions by the reader.
C. CHANGES TO SPECIFICATION 429
INTRODUCED BY THIS SUPPLEMENT
This section presents a complete tabulation of the
changes and additions to the Specification introduced
by this Supplement. Each change or addition is entitled
by the section number and title currently employed in
the Specification, or by the section number and title that
will be employed when the Supplement is eventually
incorporated. In each case there is included a brief
description of the addition or change and, for other than
very minor revisions, any text originally contained in
the Specification is reproduced for reference.
2.2.1 TRANSMISSION SYSTEM INTERCONNECT
Text revised for break connections.
Text added to Commentary describing increase of
voltage threshold.
ORIGINAL TEXT FOLLOWS:
2.2.1 Transmission System Interconnect
A data source should be connected to the data sink(s)
by means of a single twisted and shielded pair of wires.
The shields should be grounded at both ends and at all
production breaks in the cable to an aircraft ground
close to the rack connector.
COMMENTARY
In practical wire line digital information
transmission systems, cable characteristics and
electrical mismatches can produce distortion of the
digital data pulses. Also, noise due to electrical
interference perturbs digital signals. The
performance of a digital receiver depends upon the
receiver input signal characteristics (data with
distortion and noise) and the receiver design.
Prior to the selection of the voltage and impedance
parameters set forth in this Section of this
document, the pulse distortion likely to be
encountered in systems built around them in
existing size commercial aircraft was evaluated and
judged to be acceptable for a well-designed
receiver. No restriction is placed by this
specification, therefore, on the number or length of
stubs for installations on aircraft no larger than
those existing, e.g., B 747. See Appendix 1 to this
document for a report of this investigation.
Tests have shown that some receivers continue
decoding data properly when one side of the
transmission line is open or shorted to ground.
When this condition exists noise immunity
decreases and intermittent operation may occur.
Users desire protection against non-annunciated
system operation in this mode. This protection
may consist of additional circuitry to detect and
annunciate the fault.
2.2.3.2 RECEIVER VOLTAGE LEVELS
Normal voltage ranges changed due to impedance
changes.
ORIGINAL TEXT FOLLOWS:
2.2.3.2 Receiver Voltage Levels
The differential voltage presented at the receiver input
terminals will be dependent upon line length, stub
configuration and the number of receivers connected.
In the absence of noise, the normal ranges of voltages
presented to the receiver terminals (A and B) would be:
“HI” +6.5V to 10V
“NULL” +2.5V to –2.5V
“LO” -6.5V to –13V
In practice, these nominal voltages will be perturbed by
noise and pulse distortion. Thus, receivers should
associate the following voltage ranges with the three
states indicated:
“HI” +6.5V to 13V
“NULL” +2.5V to –2.5V
“LO” -6.5V to –13V
COMMENTARY
Receiver reaction is currently undefined in
Specification 429 for voltages that fall in the range
just above and below the “NULL” range.
Respective equipment Characteristics should be
referenced for desired receiver response in this
range. However, it is desirable that all DITS
receivers will discontinue operation when the
voltage levels fall into the undefined regions.
Manufacturers are urged, as new equipment is
developed, to “design in” the rejection capability.
The opinion is held by some people that conditions
on transmission lines will be encountered which
will require receivers to operate with less than the
 SUPPLEMENT 5 TO ARINC SPECIFICATION 429 – Page 3

above-defined minimum difference of 4.0V ORIGINAL TEXT FOLLOWS:

between the NULL and HI and NULL and LO
states. Receiver designers are encouraged to
investigate the possibilities and problems of
working with a minimum difference of 1 volt
between these states and to report their findings.
Receiver input common mode voltages (terminal A
to ground and terminal B to ground) are not
specified because of the difficulties of defining
ground with any satisfactory degree of precision.
Receiver manufacturers are encouraged to work
with the differential input voltage (line A to line B)
and not line-to-ground voltages.
2.3.1.5.4 FINAL WORDS
2.4.2 Information Rates
The minimum and maximum transmit intervals for each
item of information transferred by the Mark 33 DITS
are specified in the tables of Attachment 2.
COMMENTARY
There are no values given for refresh rates in this
Specification. However, it is desirable that data be
refreshed at least once per transmission. Those
data actually requiring long processing times or a
large number of samples are the only types not
expected to be refreshed with every transmission.

Text added to define checksum. Discretes contained within data words should be
transferred at the bit rate and repeated at the update rate
ORIGINAL TEXT FOLLOWS: of the primary data. Words dedicated to discretes
should be repeated continuously at the rates defined in
2.3.1.5.4 Final Words Attachment 2.

The final word of each record contains error control COMMENTARY

information. Bit nos. 1 through 8 contain the file label.
Bit nos. 9 through 29 contain an error control checksum
computed from the states of bit nos. 9 through 31 of
each intermediate word of the record. Bit nos. 30 and
31 of this word contain the code identifying it as a final
word. Bit no. 32 is encoded to render word parity odd.
2.3.4 ERROR DETECTION/CORRECTION
Obsolete text deleted.
ORIGIANL TEXT FOLLOWS:
2.3.4 Error Detection/Correction
The time intervals between successive
transmissions of a given BCD word specified in
table 1 of Attachment 2 to this document are, in
general, too short for the signal to be of use in
driving a display device directly. If the signal was
so used, the least significant character of the
display would change too rapidly for human
perception. Considerations other than human
factors demand the time intervals specified. Thus,
display designers should incorporate into their
devices means for selecting those words to be used
for updating the display from the greater quantity
delivered.

The last bit of each word should be encoded such that

word parity is rendered odd to allow error detection in
receivers. Note that the parity calculation encompasses
all 31 label and information bits of the word. The Mark
33 DITS contains no provisions for message
retransmission, the inclusion of redundant bits in words
or other means of error correction.

Fig. 3-1: RADIO SYSTEMS MANAGEMENT WORD

FORMATS

Bits 3 and 7 of transponder word changed to “0”.

(editorial)

Bit 11 and 12 assigned to ILS category designation.

Control Panel Function Matrix added to transponder

word.

ORIGINAL MATERIAL ON NEXT PAGE:

2.4.2 INFORMATION RATES

Text added to describe transmission of labels with

multiple SDI codes.
 SUPPLEMENT 5 TO ARINC SPECIFICATION 429 – Page 4

Fig. 3-1: RADIO SYSTEMS MANAGEMENT WORD FORMATS (cont’d)

ILS

SIGN/STATUS
PARITY (odd)

Function LABEL

RESERVED
ILS Frequency
MATRIX

0.01MHz
0.1MHz

(SDI)
SPARE

SPARE

SPARE

SPARE
10MHz

1MHz

(0)
(0)

(3)
(9)
Bit No. 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Example 1 0 0 0 0 0 1 0 0 1 0 0 1 1 0 0 0 0 0 0 0 0 0 0 1 1 0 1 10 0 0

ATTACHMENT 1: LABEL CODES

The following labels have been given new assignments:

073 02, 073 A2, 112 02, 130 1A, 131 2D, 132 1A, 133
1A, 151 02, 154 02, 164 02, 164 03, 174 03, 205 1A, 207
0A, 211 1A, 215 1A, 242 1A, 245 0A, 256 0A, 260 31,
262 0A, 263 0A, 264 0A, 265 0A, 270 1A, 270 1E, 270
30, 271 06, 271 1A, 271 1E, 272 1A, 274 0A, 275 2B,
300 1A, 301 1A, 303 1A, 304 1A, 305 1A, 306 1A, 307
1A, 325 1A, 340 1A, 340 2D, 341 1A, 342 1A, 344 1A,
345 1A, 346 1A, 350 1A, 351 1A, 352 1A, 353 1A, 354
1A.

Label 242** was deleted.

Label 316 04 changed form “Wind Angle” to “Wind

Direction (True)”.

ATTACHMENT 1: EQUIPMENT CODES

New assignments were made for 0A and 2D.

Note added to 1A.

 SUPPLEMENT 5 TO ARINC SPECIFICATION 429 – Page 5

ATTACHEMENT 2: DATA STANDARDS

Data standards were added for new labels.

The following table lists the parameters for which the

existing data standards have changed. An asterisk beside
a particular value designates that a new value is
suggested.

EQPT PARAMETER SIG. POS. MIN. MAX.

LABEL ID NAME UNITS RANGE DIG/ SENSE RESOL TR. TR.
(HEX) BITS INT. INT.
004 01 Runway Distance to Go Feet 0-79900 3 100.0 200* 400*
165 07 Radio Height Feet ± 0-7999.9 5 0.1 100* 200*
205 06 Mach mMach* 4096* 13* 0.5* 62.5 125
210 06 True Airspeed Knots 2048* 13* 0.25* 62.5 125
215 06 Impact Pressure mb 512* 9* 1.0* 62.5 125
242 06 Total Pressure mb 2045* 11* 1.0* 62.5 125
313 04 Track Angle True Deg/180 ± 180o 12* 0.05 o 25 50
314 04 True Heading Deg/180 ± 180 o 12* 0.05 o 25 50
317 04 Track Angle Magnetic Deg/180 ± 180 o 12* 0.05 o 25 50
317 05 Track Angle Magnetic Deg/180 ± 180 o 12* 0.05 o 25 50
320 04 Magnetic Heading Deg/180 ± 180 o 12* 0.05 o 25 50
320 05 Magnetic Heading Deg/180 ± 180 o 12* 0.05 o 25 50
323 04 Flight Path Acceleration g 2* 14* 0.0001* 10 20
323 05 Flight Path Acceleration g 2* 14* 0.0001* 10 20
324 04 Pitch Angle Deg/180 ± 180 o 14 0.01 o 25* 50*
324 05 Pitch Angle Deg/180 ± 180 o 14 0.01 o 25* 50*
325 04 Roll Angle Deg/180 ± 180 o 14 0.01 o 25* 50*
325 05 Roll Angle Deg/180 ± 180 o 14 0.01 o 25* 50*
360 04 Potential Vertical Speed Ft/min 16384* 10* 16* 25 50
360 05 Potential Vertical Speed Ft/min 16384* 10* 16* 25 50
361 04 Altitude (Inertial) Feet 131,072 18* 0.5* 32.25* 62.5*
361 05 Altitude (Inertial) Feet 131,072 18 0.5 31.25* 62.5*
365 04 Inertial Vert. Vel. (EFI) Ft/min 16384* 10* 16* 20 40
365 05 Inertial Vert. Vel. (EFI) Ft/min 16384* 10* 16* 20 40
375 05 Along Heading Accel. g 4 12 0.001 25* 50*
376 05 Cross Heading Accel. g 4 12 0.001 25* 50*

Note [2]: Guidance added for transmission intervals of

labels with multiple SDI codes.

ORIGINAL TEXT FOLLOWS:

[2] Transmit intervals and the number of parameters

to be transmitted are prime factors in bus
loading. The interval for transmission of
parameters should fall between the minimum
and maximum specified intervals and nominally
should be near the center of the range at equal
intervals between transmissions. When heavy
bus loading dictates a shift from the center of the
range, the shift should be toward the maximum
transmit interval.

TABLE 3.1: INTERVAL DISCRETES – LABEL 270

Discrete word formats revised.

SUPPLEMENT 5 TO ARINC SPECIFICATION 429 – Page 6

ORIGINAL TEXT FOLLOWS:

Table 3.1: Inertial Discretes – Label 270

Notes: [1] Attitude invalid is equivalent to IRS failure.

[2] Bit 14 “1” condition indicates that the
“Magnetic Heading” outputs are no longer
being computer and have the
characteristics of a “free DG” which is
subject to control by a “Set Heading” input
to the IRU. (See Section 3.2.4 for further
explanation).
 SUPPLEMENT 5 TO ARINC SPECIFICATION 429 – Page 7

TABLE 3.4: AIR DATA DISCRETES

Discrete word #1 format changed.

Discrete word #2 added.

ORIGINAL TEXT FOLLOWS:

Table 3.4: Air Data Discretes – Label 270

ATTACHMENT 6 – GENERAL WORD FORMATS AND ENCODING EXAMPLES

Examples revised to agree with adopted data standards changes. (editorial)

 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401 – 7645 USA

SUPPLEMENT 6
TO

ARINC SPECIFICATION 429

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

Published: January 22, 1982

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: December 9, 1981

SUPPLEMENT 6 TO ARINC SPECIFICATION 429 – Page 2
A. PURPOSE OF THIS SUPPLEMENT
This Supplement introduces the assignment of octal
labels and hexadecimal equipment identifiers, the
addition of guidance for label selection, a revision of
failure warning annunciation in discrete words, deletion
of the weight & balance words, editorial revisions to
the label tables and addition of EEC discrete word
formats.
B. ORGANIZATION OF THIS SUPPLEMENT
The first part of this document, printed on goldenrod
paper, contains descriptions of the changes introduced
into the Specification by this Supplement, and, where
appropriate, extracts from the original text for
comparison purposes. The second part consists of
replacement white pages for the Specification, modified
to reflect these changes. The modified and added
material on each replacement page is identified with “c-
6” symbols in the margins. Existing copies of
Specification 429 may be updated by simply inserting
the replacement white pages they replace. The
goldenrod pages should be inserted inside the rear
cover of the Specification.
Copies of the Specification bearing the number 429-6
already contain this Supplement and thus do not require
revisions by the reader.
C. CHANGES TO SPECIFICATION 429
INTRODUCED BY THIS SUPPLEMENT
This section presents a complete tabulation of the
changes and additions to the Specification introduced
by this Supplement. Each change or addition is entitled
by the section number and title currently employed in
the Specification, or by the section number and title that
will be employed when the Supplement is eventually
incorporated. In each case there is included a brief
description of the addition or change and, for other than
very minor revisions, any text originally contained in
the Specification is reproduced for reference.
2.1.5.1 BCD, NUMERIC, DISCRETE, AIM DATA
AND FILE TRANSFER WORDS
Commentary revised to reflect use of failure warning
flags in discrete words.
ORIGINAL TEXT FOLLOWS:
COMMENTARY
Definitions
Invalid Data – is defined as any data generated by a
source system whose fundamental characteristic is
the inability to convey reliable information for the
proper performance of a user system. There are
two categories of invalid data namely, “No
Computed Data” and “Failure Warning”.
No Computes Data – is a particular case of data
invalidity where the source system is unable to
compute reliable data for reasons other than system
failure. This inability to compute reliable data is
caused exclusively be a definite set of events or
conditions whose boundaries are uniquely defined
in the system characteristic. When such a
condition exists, the source system should
annunciate its outputs to be invalid by setting the
sign/status matrix of the affected words to the
“NCD” code, as defined in sections2.1.5.1 and
2.1.5.2. The system indicators may or may not be
flagged depending on system requirements.
Failure Warning – is a particular case of data
invalidity where the system monitors have detected
one or more failures. These failures are uniquely
characterized by boundaries defined in the system
characteristic. When such a condition exists, the
source system should annunciate its outputs to be
invalid by either ceasing to supply the affected
words to the data bus (the case of BCD data and
ILS-LRRA installations with provisions for the
interruption of AFS BNR data – see ARINC
characteristics 707 and 710) or by setting the
sign/status matrix of the affected words to the
“Failure Warning” code (BNR case), as defined in
sections 2.1.5.1 and 2.1.5.2. The system indicators
should always be flagged during a “Failure
Warning” condition.
2.1.5.2 BNR NUMERIC DATA WORDS
Commentary for failure warning revised.
ORIGINAL TEXT FOLLOWS:
COMMENTARY
Definitions
Invalid Data – is defined as any data generated by a
source system whose fundamental characteristic is
the inability to convey reliable information for the
proper performance of a user system. There are
two categories of invalid data, namely, “No
Computed Data” and “Failure Warning”.
No Computed Data – is a particular case of data
invalidity where the source system is unable to
compute reliable data for reasons other than system
failure. This inability to compute reliable data is
caused exclusively by a definite set of events or
conditions whose boundaries are uniquely defined
in the system characteristic. When such a
condition exists the source system should
annunciate its outputs to be invalid by setting the
sign/status matrix of the affected words to the
“NCD” code, as defined in sections 2.1.5.1 and
2.1.5.2. The system indicators may or may not be
flagged depending on system requirements.
Failure Warning – is a particular case of data
invalidity where the system monitors have detected
one or more failures. These failures are uniquely
characterized by boundaries defined in the system
characteristic. When such a condition exists, the
source system should annunciate its outputs to be
invalid by either ceasing to supply the affected
words to the data bus (the case of BCD data and
ILS-LRRA Installations with provisions for the
interruption of AFS BNR data – see ARINC
Characteristics 707 and 710) or by setting the
 SUPPLEMENT 6 TO ARINC SPECIFICATION 429 – Page 3

sign/status matrix of the affected words to the

“Failure Warning” code (BNR case), as defined in
sections 2.1.5.1 and 2.1.5.2. The system indicators
should always be flagged during a“Failure
Warning” conditions.

Fig. 3.1 RADIO SYSTEMS MANAGEMENT WORD

FORMATS

Assignments for bits 12, 15 and 17 removed from table

for note 1 of ATC transponder word (editorial).
ATTACHMENT 1: LABEL CODES

The following labels have been given new assignments:

021 02, 041 02, 042 02, 043 02, 066 02, 071 33, 072
2F, 072 33, 074 33, 075 02, 077 02, 114 2F, 115 2F,
130 2F, 131 2F, 132 33, 133 2F, 155 33, 156 33, 157
33, 160 33, 161 33, 241 2C, 244 33, 250 2B, 252 2F,
260 33, 261 33, 262 02, 262 33, 263 33, 264 2F, 264
33, 265 33, 267 0A, 267 33, 270 2F, 270 3A, 271 2F,
271 3A, 273 2F, 272 2F, 273 33, 274 2F, 274 33, 275
2F, 315 02, 340 2F, 341 2F, 342 2F, 344 2F, 344 33,
345 2F, 346 2F, 350 2F, 351 2E, 351 2F, 352 2E, 352
2F, 353 2F, 354 2F, 375 33, 376 33.
The following labels have been deleted:

060 32, 061 32, 062 32, 063 32, 064 32.

Editorial changes were made to provide for consistency

between Attachment 1 and Attachment 2.

“Predictive” deleted from 207 0A.

ATTACHMENT 1: EQUIPMENT CODES

New assignments were made for 0D, 2E, 2F, 3A, 3B,
33, and 34.

Nomenclature modified for 2C and 32.

ATTACHMENT 2: DATA STANDARDS

Data standards were added for new labels.

Editorial changes made.

Resolutions revised for 315 04, 315 05, 316 04, 321 04,
321 05, 322 04, 334 04, and 334 05 to match ARINC
704 and 705.

EEC discrete words added.

ATTACHMENT 6: GENERAL WORD FORMATS

AND CODING EXAMPLES

Format added for label 262 02.

Bit 12 corrected in DME distance word (editorial).

Example added for GMT binary word.

APPENDIX 5: LABEL SELECTION GUIDANCE

Appendix added.
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401 7645 USA

SUPPLEMENT 7
TO

ARINC SPECIFICATION 429

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

Published: January 3, 1983

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: November 4, 1982

SUPPLEMENT 7 TO ARINC SPECIFICATION 429 – Page 2

A. PURPOSE OF THIS SUPPLEMENT The terminology has been modified for the following
labels:
This Supplement introduces new label assignments, data
standards and equipment identification codes, and means 072 33, 074 33, 132 33, 244 33, 262 33, 263 33, 264 33,
for transmitting data with reduced accuracy. 265 33.

B. ORGANIZATION OF THIS SUPPLEMENT Station identifiers deleted on engine related parameters.

The first part of this document, printed on goldenrod
paper, contains descriptions of the changes introduced
into the Specification by this Supplement, and, where
appropriate, extracts from the original text for comparison
purposes. The second part consists of replacement white
pages for the Specification, modified to reflect these
changes. The modified and added material on each
replacement page is identified with “c-7” symbols in the
margins. Existing copies of Specification 429 may be
updated by simply inserting the replacement white pages
they replace. The goldenrod pages should be inserted
inside the rear cover of the Specification.
ATTACHMENT 1 – EQUIPMENT CODES
Code 2F changed from “EEC (Full Authority)” to “Full
Authority EEC-A”.
Code 30 assigned as “Airborne Separation Assurance
System”.
Description of Code OD changed to “AIDS Data
Management Unit (DMU)”
Code 3F assigned as “Full Authority EEC_B”.

Copies of the Specification bearing the number 429-7 ATTACHMENT 2 – DATA STANDARDS
already contain this Supplement and thus do not require
revisions by the reader. Data standards were added for new labels.

C. CHANGES TO SPECIFICATION 429
INTRODUCED BY THIS SUPPLEMENT
This section presents a complete tabulation of the changes
and additions to the Specification introduced by this
Supplement. Each change or addition is entitled by the
section number and title currently employed in the
Specification, or by the section number and title that will
be employed when the Supplement is eventually
incorporated. In each case there is included and, for other
than very minor revisions, any text originally contained in
the Specification is reproduced for reference.
Data standards added for the following existing labels:
270 3A, 271 3A, 270 2F-275 2F, 350 2F,-354 2F.
Note added to label 072 33.
Digits of label 014 changed from 3 to 4 (previously
adopted).
Range of label 014 changed from 359 to 359.9
(previously adopted). Significant bits of label 321
changed from 12 to 11 (typo).

2.1.5.1 BCD, NUMERIC, DISCRETE, AIM DATA Note [4] added.

AND FILE TRANSFER WORDS
Note [5] added.
Note [6] added.
Note flag [5] added to following labels:
2.1.5.2 BNR NUMERIC DATA WORDS
074 2C, 075 2C, 247 2C 250 2C, 256 2C, 257 2C, 260
Note [6] added. 2C, 262 2C.

ATTACHMENT 1 – LABEL CODES ATTACHMENT 6 – GENERAL WORD FORMATS

AND ENCODING EXAMPLES
The following labels have been given new assignments:
Formats for engine serial number words added.
046 33, 047 33, 114 3F, 115 3F, 127 33, 130 30, 130 3F,
131 30, 131 33, 132 30, 133 3F, 164 3B, 173 3B, 174 3B, Formats for ASAS words added.
175 33, 212 3B, 242 3B, 244 3B, 245 3B, 246 3B, 247
3B, 252 3F, 264 3F, 270 30, 270 33, 270 3B, 270 3F, 271
30, 271 33, 271 3B, 271 3F, 272 3B, 272 3F, 273 3B, 273
3F, 274 3B, 274 3F, 275 3B, 275 3F, 311 3B, 214 3B, 325
2F, 325 3F, 340 33, 340 3F, 341 3F, 342 3B, 342 3F, 344
3F, 345 3F, 346 33, 346 3F, 347 30, 350 3F, 351 3F, 352
3F, 353 3F, 354 3F, 377 30.
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401 – 7645 USA

SUPPLEMENT 8
TO

ARINC SPECIFICATION 429

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

Published: December 3, 1984

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: November 4, 1983

SUPPLEMENT 8 TO ARINC SPECIFICATION 429 – Page 2
A. PURPOSE OF THIS SUPPLEMENT
This Supplement introduces new label assignments,
revised data standards, expanded text describing SDI
codes and makes note of a change in the resolution of the
Magnetic Heading label incorporated in Supplement 7.
B. ORGANIZATION OF THIS SUPPLEMENT
The first part of this document, printed on goldenrod
paper, contains descriptions of the changes introduced
into the Specification by this Supplement, and, where
appropriate, extracts from the original text for comparison
purposes. The second part consists of replacement white
pages for the Specification, modified to reflect these
changes. The modified and added material on each
replacement page is identified with “c-8” symbols in the
margins. Existing copies of Specification 429 may be
updated by simply inserting the replacement white pages
they replace. The goldenrod pages should be inserted
inside the rear cover of the Specification.
Copies of the Specification bearing the number 429-8
already contain this Supplement and thus do not require
revisions by the reader.
C. CHANGES TO SPECIFICATION 429
INTRODUCED BY THIS SUPPLEMENT
This section presents a complete tabulation of the changes
and additions to the Specification introduced by this
Supplement. Each change or addition is entitled by the
section number and title currently employed in the
Specification, or by the section number and title that will
be employed when the Supplement is eventually
incorporated. In each case there is included a brief
description of the addition or change and, for other than
very minor revisions, any text originally contained in the
Specification is reproduced for reference.
2.1.4 SOURCE DESTINATION IDENTIFIER
Text added to clarify use of SDI on combined source/sink
equipment.
ORIGINAL TEXT FOLLOWS:
2.1.4 Source/Destination Identifier
Bit nos. 9 and 10 of numeric data words should be
reserved for a data source/destination identification
function. They are not available for this function in
alpha/numeric (ISO Alphabet No. 5) data words (See
Section 2.3.1.3 of this document) or when the resolution
needed for numeric (BNR/BCD) data necessitates their
use for valid data. The source/destination identifier
function may find application when specific words need
to be directed to a specific system of a multi-system
installation or when the source system of a multi-system
installation needs to be recognizable from the word
content. When it is used, a source equipment should
encode its aircraft installation number in bit nos. 9 and
10 as shown in the table below. A sink equipment should
recognize words containing its own installation number
code and words containing code “00”, the “all-call” code.
Bit No. Installation
10 9 No.
0 0 See Note Below
0 1 1
1 0 2
1 1 3
Note: In certain specialized application of the SDI
function the all-call capability may be forfeited so that
code “00” is available as an “installation no. 4” identifier.
When the SDI function is not used, binary zeros or valid
data should be transmitted in bit nos. 9 and 10.
COMMENTARY
This document does not address the practical
question of how the SDI bits will be set in those
multi-installation systems in which the
source/destination function is desired. One way
would be to use program pins on the individual
installation black boxes which would be wired to set
up the appropriate code. The ARINC Characteristics
devoted to the individual systems will define the
method actually to be used.
ATTACHMENT 1 – LABEL CODES
The following labels have been given new assignments:
012 25, 060 3C, 061 3C, 062 3C, 063 3C, 064 3C, 137
2F, 137 3F, 140 25, 141 25, 142 25, 151 27, 152 27, 153
27, 154 27, 155 27, 156 27, 157 27, 160 27, 161 27, 162
27, 163 27, 164 25, 164 27, 165 27, 170 C5, 173 25, 270
25, 271 C5, 272 C5, 273 C5, 274 25, 275 25, 313 25, 314
25, 317 25, 320 25, 324 25, 325 25, 330 2F, 330 3F, 331
2F, 332 2F, 332 3F, 333 3F, 334 2F, 334 3F, 350 25, 351
25, 352 25, 353 25, 370 C5.
ATTACHMENT 1 - EQUIPMENT CODES
Code 3C assigned to Tire Pressure System.
ATTACHMENT 2 – DATA STANDARDS
Table 1 had been modified in Supplement 7 to reflect the
resolution of label 014 as 0.1, rather than 1.0, which had
been incorrectly introduced in a previous Supplement.
This change is hereby noted.
Data standards added for new labels.
Data standards revised for labels 115 2F, 115 3F, 325 2F,
325 3F.
ATTACHMENT 6 – GENERAL WORD FORMATS
Tire pressure SDI bit coding added.
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401 – 7645 USA

SUPPLEMENT 9
TO

ARINC SPECIFICATION 429

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

Published: April 30, 1985

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: October 11, 1984

SUPPLEMENT 9 TO ARINC SPECIFICATION 429 - Page 2

A. PURPOSE OF THIS SUPPLEMENT

This Supplement introduces new label assignments and

equipment identification codes. This Supplement also
corrects a word format bit error introduced in a
previous Supplement.

B. ORGANIZATION OF THIS SUPPLEMENT

The first part of this document, printed on goldenrod

paper, contains descriptions of the changes introduced
into the Specification by this Supplement, and, where
appropriate, extracts from the original text for
comparison purposes. The second part consists of
replacement white pages for the Specification, modified
to reflect these changes. The modified and added
material on each replacement page is identified with “c-
9” symbols in the margins. Existing copies of
Specification 429 may be updated by simply inserting
the replacement white pages they replace. The
goldenrod pages should be inserted inside the rear
cover of the Specification.
Copies of the Specification bearing the number 429-9
already contain this Supplement and thus do not require
revisions by the reader.

C. CHANGES TO SPECIFICATION 429

INTRODUCED BY THIS SUPPLEMENT

This section presents a complete tabulation of the

changes and additions to the Specification introduced
by this Supplement. Each change or addition is entitled
by the section number and title currently employed in
the Specification, or by the section number and title that
will be employed when the Supplement is eventually
incorporated. In each case there is included a brief
description of the addition or change and, for other than
very minor revisions, any text originally contained in
the Specification is reproduced for reference.
ATTACHMENT 1 – LABEL CODES

The following labels have been given new assignments:

075 3E, 076 3E, 103 1B, 104 1B, 105 1B, 106 1B, 107
1B, 130 35, 131 35, 132 35, 203 18, 270 1B, 270 35,
270 3E, 270 4A, 271 18, 271 35, 272 18, 272 35, 273
18, 273 35, 274 18, 274 35, 275 18, 275 4A, 276 18,
300 3D, 336 1A, 337 1A, 347 18, 347 35, 350 18, 350
35, 350 3E, 370 04, and 370 05.

ATTACHMENT 1 – EQUIPMENT CODES

Codes 3D, 3E, 4A, 4B, 4C and 90-9F given new

assignments.

ATTACHMENT 2 – DATA STANDARDS

Data standards entered for new labels. Range for labels

012 and 170 changed to 7999.
ATTACHMENT 6 – GENERAL WORD FORMATS
AND ENCODING EXAMPLES
Label 150 and 323 examples corrected.
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401 – 7645 USA

SUPPLEMENT 10
TO

ARINC SPECIFICATION 429

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

Published: November 17, 1986

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: November 7, 1985

SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 2
A PURPOSE OF THIS SUPPLEMENT
This Supplement introduces new label assignments,
equipment identification codes and revised data standards.
B. ORGANIZATION OF THIS SUPPLEMENT
The first part of this document, printed on goldenrod
paper, contains descriptions of the changes introduced
into the Specification by this Supplement, and, where
appropriate, extracts from the original text for comparison
purposes. The second part consists of replacement white
pages for the Specification, modified to reflect these
changes. The modified and added material on each
replacement page is identified with “c-10” symbols in the
margins. Existing copies of Specification 429 may be
updated by simply inserting the replacement white pages
they replace. The goldenrod pages should be inserted
inside the rear cover of the Specification.
Copies of the Specification bearing the number 429-10
already contain this Supplement and thus do not require
revisions by the reader.
C. CHANGES TO SPECIFICATION 429
INTRODUCED BY THIS SUPPLEMENT
This section presents a complete tabulation of the changes
and additions to the Specification introduced by this
Supplement. Each change or addition is entitled by the
section number and title currently employed in the
Specification, or by the section number and title that will
be employed when the Supplement is eventually
incorporated. In each case there is included a brief
description of the addition or change and, for other than
very minor revisions, any text originally contained in the
Specification is reproduced for reference.
3.1.4 FREQUENCY RANGES AND SWITCHING
FUNCTIONS
Note 6 deleted on DME Frequency Word.
Attachment 1 – Label Codes
The following labels have been given new assignments:
072 02, 075 0B, 076 0B, 077 0B, 176 5A, 177 5A, 200
5A, 201 5A, 202 5A, 203 5A, 204 5A, 205 5A, 206 18,
213 8D, 227 7E, 241 4D, 242 09, 242 10, 242 11, 242 12,
244 8D, 247 4D, 251 1A, 255 2F, 255 3F, 256 4D, 270
0B, 272 3A, 272 5A, 273 5A, 274 5A, 275 5A, 276 2F,
276 3F, 335 2F, 336 2F, 336 3F, 356 XX, 371 00.
Labels for ARINC Characteristic 737 WBT and ARINC
Characteristic 738 ADIRS added.
Attachment 1 – Equipment Codes
The following codes have been given new assignments:
0B, 35, 36, 37, 38, 4D, 4E, 5A, 5B, 5C, 5D, 5E, 5F, 6A,
6B, 6C, 6D, 6E, 6F, 7A, 7B, 7C, 7D, 7E, 7F, 8A, 8B, 8C,
8D, AD, C3.
Attachment 2 – Data Standards
Data standards entered for new labels.
Data standards revised for the following labels:
060 36, 061 3C, 062 3C, 063 3C, 064 3C, 150
31, 176 03, 176 29, 270 3A, 270 2F, 270 3F, 271 2F, 271
3F, 272 2F, 272 3F, 273 2F, 273 3F, 274 2F, 274 3F, 275
2F, 275 3F, 350 2F, 350 3F, 351 2F, 351 3F, 352 2F, 352
3F, 353 2F, 353 3F, 354 2F, 354 3F.
Labels 060 37-064 3C significant bits changed from 9 to
10 and range changed from 512 to 1024.
Following note added to words (labels 270 3B-275 3B):
Typical discrete functions are shown in the above
tables. Slight variations of bit usage may arise
according to the specific application.
Label 203 35 changed to 203 18 (typographical error).
Transmit interval range added to label 150 31.
Labels 176 03 and 176 29 resolutions changed from 0.05
to 0.5 (typographical error).
Original bit assignments for remaining labels listed in
following pages.
Attachment 6 – General Word Formats and Encoding
Examples
Example added for label 251 1A, 077 0B and 206 18.
For TPIS word formats:
Wheel #519 label corrected to read “060”. SDI labels
clarified.
For BTMS word formats:
Wheel #10, #11, #12 labels corrected to read “116”. Bit
27 assigned to a value of “1024”. SDI labels clarified.
Special expanded format word example added for label
260 31.
Attachment 9A – General Aviation Labels and Data
Standards
New attachment added.
Attachment 9B – General Aviation Word Examples
New attachment added.
Attachment 9C – General Aviation Equipment Identifiers
New attachment added.
 SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 3

Table 3.11 Propulsion Discrete Interface Unit – Labels 270 3A and 271 3A

Label 270 3A

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI 1 0
Left Engine Right Engine
10 SDI 0 1
11 PDIU Status Flag Failed OK
12 T2 / P2 Probe Heat HEAT OFF HEAT ON
13 TLA Interlock Fault FAULT OK 1
14 Idle Select MINIMUM APPROACH
15 Air/Ground Switch GROUND AIR
16 Opposite Engine Status SHUT DOWN RUNNING
17 Spare X 2
18 Spare X
19 N2 Mode Trim Release (PROV) RELEASED FIXED 1
20 Spare X
21 Spare X
22 Spare X
23 Maintenance Test (Provisional) ON OFF 1
24 Ground Test Power ON OFF
25 Spare X
26 T/R Indication Power Failed (PROV) FAILED OK 1
27 T/R Not Stowed NOT STOWED STOWED 1
28 T/R Deployed Indication DEPLOYED NOT DEPLOYED 1
29 Engine Fire Warning ON OFF 1
30 SSM
31 SSM
32 Parity (Odd)

1 = RETURN TO SPARE

2 = CHANGE SPARE TO DEFINITION ON NEXT PAGE

SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 4

Table 3.12 EEC Status – Labels 270 2F, 270 3F, 271 2F, 271 3F, 272 2F, 272 3F, 273 2F, 273 3F, 274 2F, 274 3F, 275 2F,
275 3F

Label 270 2F

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI
10 SDI
11 PAD X
12 PAD X
13 PAD X
14 Spare X 2
15 Data Entry Plug Failed Normal 1
16 Auto Mode Selected Not Selected 3
17 Channel Manually Selected Selected Not Selected 3
18 N2 Droop Control Mode Engaged Not Engaged
19 Reverser System Failed Failed OK
20 Channel Controlling Status Controlling Not Controlling
21 Bleed Fall-Safe Open Fall-Safe Operational 3
22 TCA Valve Failed Closed Failed OK
23 Spare X 2
24 Overspeed Self-Test Failed Failed OK 3
25 Channel Incapable (Failed) Incapable Capable
26 Abnormal Start Abnormal OK (Provision) 3
27 SVA Fall-Safe Fall-Safe 3
28 Starter Cutout Command Cutout Not Cutout
29 Oil Overtemperature Overtemp OK 1
30 SSM
31 SSM
32 Parity (Odd)

1 = RETURN TO SPARE

2 = CHANGE SPARE TO DEFINITION ON NEXT PAGE

3 = CHANGE DEFINITION TO DEFINITION ON NEXT PAGE

 SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 5

Label 270 3F

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI
10 SDI
11 PAD X
12 PAD X
13 PAD X
14 Spare X 2
15 Data Entry Plug Failed Normal 1
16 Auto Mode Selected Not Selected 3
17 Channel Manually Selected Selected Not Selected 3
18 N2 Droop Control Mode Engaged Not Engaged
19 Reverser System Failed Failed OK
20 Channel Controlling Status Controlling Not Controlling
21 Bleed Fall-Safe Open Fall-Safe Operational 3
22 TCA Valve Failed Closed Failed OK
23 Spare X 2
24 Overspeed Self-Test Failed Failed OK 3
25 Channel Incapable (Failed) Incapable Capable
26 Abnormal Start Abnormal OK (Provision) 3
27 SVA Fall-Safe Fall-Safe 3
28 Starter Cutout Command Cutout Not Cutout
29 Oil Overtemperature Overtemp OK 1
30 SSM
31 SSM
32 Parity (Odd)
SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 6

Label 271 2F

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI
10 SDI
11 PAD X
12 PAD X
13 PAD X
14 Reverser Deploy Command ON OFF
15 Turbine Cooling Air Valve Solenoid ON OFF
16 Oil Cooler Bypass Valve Solenoid ON OFF 3
17 Cowl Vent Solenoid ON OFF 1
18 Breather Compartment Ejector Sol. ON OFF 1
19 Spare X 2
20 Spare X
21 Spare X
22 Spare X
23 Autostar Relay ON OFF (Provision) 1
24 TLA Interlock Actuator Command Block Fwd Block Rev
25 Spare Reverser Group Relay ON OFF (Provision) 1
26 Spare X 2
27 Spare X 2
28 Spare X 2
29 Spare X 2
30 SSM
31 SSM
32 Parity (Odd)
 SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 7

Label 271 3F

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI
10 SDI
11 PAD X
12 PAD X
13 PAD X
14 Reverser Deploy Command ON OFF
15 Turbine Cooling Air Valve Solenoid ON OFF
16 Oil Cooler Bypass Valve Solenoid ON OFF 3
17 Cowl Vent Solenoid ON OFF 1
18 Breather Compartment Ejector Sol. ON OFF 1
19 Spare X 2
20 Spare X
21 Spare X
22 Spare X
23 Autostar Relay ON OFF (Provision) 1
24 TLA Interlock Actuator Command Block Fwd Block Rev
25 Spare Reverser Group Relay ON OFF (Provision) 1
26 Spare X 2
27 Spare X 2
28 Spare X 2
29 Spare X 2
30 SSM
31 SSM
32 Parity (Odd)
SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 8

Label 272 2F

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI
10 SDI
11 PAD X
12 PAD X
13 PAD X
14 N1 Loop Engaged Not Engaged
15 N2 Loop Engaged Not Engaged
16 N2 Topping Loop Engaged Not Engaged
17 PB Topping Loop Engaged Not Engaged
18 PB Topping Loop Minimum Engaged Not Engaged
19 EPR Loop Engaged Not Engaged
20 Acceleration Schedule Loop Engaged Not Engaged
21 Deceleration Schedule Loop Engaged Not Engaged
22 T4.9 Topping Loop Engaged Not Engaged 1
23 Back Up Mode Engaged Not Engaged
24 Spare X 2
25 Spare X
26 Spare X
27 Spare X
28 Spare X
29 Spare X
30 SSM
31 SSM
32 Parity (Odd)
 SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 9

Label 272 3F

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI
10 SDI
11 PAD X
12 PAD X
13 PAD X
14 N1 Loop Engaged Not Engaged
15 N2 Loop Engaged Not Engaged
16 N2 Topping Loop Engaged Not Engaged
17 PB Topping Loop Engaged Not Engaged
18 PB Topping Loop Minimum Engaged Not Engaged
19 EPR Loop Engaged Not Engaged
20 Acceleration Schedule Loop Engaged Not Engaged
21 Deceleration Schedule Loop Engaged Not Engaged
22 T4.9 Topping Loop Engaged Not Engaged 1
23 Back Up Mode Engaged Not Engaged
24 Spare X 2
25 Spare X
26 Spare X
27 Spare X
28 Spare X
29 Spare X
30 SSM
31 SSM
32 Parity (Odd)
SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 10

Label 273 2F

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI
10 SDI
11 PAD X
12 PAD X
13 PAD X
14 P4.9 Interface Failed Failed OK 3
15 PB Interface Failed Failed OK 3
16 P2 (Pamb) Interface Failed* Failed OK 3
17 C3C Interface Failed Failed OK 3
18 T2 Interface Failed Failed OK 3
19 T4.9 Interface Failed Failed OK 3
20 Tfuel Interface Failed Failed OK 3
21 A/D Interface Failed Failed OK 3
22 RES/LVDT Interface Failed Failed OK 3
23 SVA Interface Failed Failed OK 3
24 N1 Interface Failed Failed OK 3
25 N2 Interface Failed Failed OK 3
26 P4.9 Sensor Prom Failed Failed OK 3
27 P2 (Pamb) Sensor Prom Failed* Failed OK 3
28 PB Sensor Prom Failed Failed OK 3
29 Background is not Executing Not Executing Executing 3
30 SSM
31 SSM
32 Parity (Odd)

* Primary channel uses P2, Secondary channel uses Pamb.

 SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 11

Label 273 3F

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI
10 SDI
11 PAD X
12 PAD X
13 PAD X
14 P4.9 Interface Failed Failed OK 3
15 PB Interface Failed Failed OK 3
16 P2 (Pamb) Interface Failed* Failed OK 3
17 C3C Interface Failed Failed OK 3
18 T2 Interface Failed Failed OK 3
19 T4.9 Interface Failed Failed OK 3
20 Tfuel Interface Failed Failed OK 3
21 A/D Interface Failed Failed OK 3
22 RES/LVDT Interface Failed Failed OK 3
23 SVA Interface Failed Failed OK 3
24 N1 Interface Failed Failed OK 3
25 N2 Interface Failed Failed OK 3
26 P4.9 Sensor Prom Failed Failed OK 3
27 P2 (Pamb) Sensor Prom Failed* Failed OK 3
28 PB Sensor Prom Failed Failed OK 3
29 Background is not Executing Not Executing Executing 3
30 SSM
31 SSM
32 Parity (Odd)

* Primary channel uses P2, Secondary channel uses Pamb.

SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 12

Label 274 2F

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI
10 SDI
11 PAD X
12 PAD X
13 PAD X
14 Parity Test Hardware Fault Error OK 3
15 ROM Checksum Failure Failed OK 3
16 Ram Test Failure Failed OK 3
17 Instruction Test Failure Failed OK 3
18 High Speed Cross Link Failure Failed OK 3
19 Foreground Software Execution Incorrectly Correctly
20 Watch Dog Timer Fault Error OK 3
21 Watch Dog/Parity Counter Latch Latched Not Latched 1
22 EAROM Failure Failed OK 3
23 ROM Parity Error Caused Reset Yes No
24 RAM Parity Error Caused Reset Yes No
25 Watchdog Timer Error Caused Reset Yes No
26 Status Buffer or Watchdog/Parity Failed OK 3
27 Loss of Clock Caused Reset Yes No
28 SDD Output #1 W/A Failed OK
29 SDD Output #2 W/A Failed OK
30 SSM
31 SSM
32 Parity (Odd)
 SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 13

Label 274 3F

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI
10 SDI
11 PAD X
12 PAD X
13 PAD X
14 Parity Test Hardware Fault Error OK 3
15 ROM Checksum Failure Failed OK 3
16 Ram Test Failure Failed OK 3
17 Instruction Test Failure Failed OK 3
18 High Speed Cross Link Failure Failed OK 3
19 Foreground Software Execution Incorrectly Correctly
20 Watch Dog Timer Fault Error OK 3
21 Watch Dog/Parity Counter Latch Latched Not Latched 1
22 EAROM Failure Failed OK 3
23 ROM Parity Error Caused Reset Yes No
24 RAM Parity Error Caused Reset Yes No
25 Watchdog Timer Error Caused Reset Yes No
26 Status Buffer or Watchdog/Parity Failed OK 3
27 Loss of Clock Caused Reset Yes No
28 SDD Output #1 W/A Failed OK
29 SDD Output #2 W/A Failed OK
30 SSM
31 SSM
32 Parity (Odd)
SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 14

Label 275 2F

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI
10 SDI
11 PAD X
12 PAD X
13 PAD X
14 Lamp (1,2 &/or 3) W/A Failed Failed OK 3
15 Other Channels Depower Discrete Disagree Agree
16 PB Sensor Failed Failed OK 3
17 PT4.9 Sensor Failed Failed OK 3
18 PT2 (Pamb)* Sensor Failed Failed OK 3
19 EEC Temperature Status High OK 3
20 2
21 2
22 2
23 2
24 2
25 Spare (all “o” states) 2
26 2
27 2
28 2
29
30 SSM
31 SSM
32 Parity (Odd)

[3] Primary channel uses PT2, Secondary channel uses Pamb.

 SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 15

Label 275 3F

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI
10 SDI
11 PAD X
12 PAD X
13 PAD X
14 Lamp (1,2 &/or 3) W/A Failed Failed OK 3
15 Other Channels Depower Discrete Disagree Agree
16 PB Sensor Failed Failed OK 3
17 PT4.9 Sensor Failed Failed OK 3
18 PT2 (Pamb)* Sensor Failed Failed OK 3
19 EEC Temperature Status High OK 3
20 2
21 2
22 2
23 2
24 2
25 Spare (all “o” states) 2
26 2
27 2
28 2
29
30 SSM
31 SSM
32 Parity (Odd)

CHANGE * Primary channel uses PT2: Secondary channel uses Pamb.

SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 16

Table 3.13 EEC Maintenance – Labels 350 2F, 350 3F, 351 2F, 351 3F, 352 2F, 352 3F, 353 2F, 353 3F, 354 2F, 354 3F

Label 350 2F

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI
10 SDI
11 PAD X
12 PAD X
13 PAD X
14 N1 Failed Failed OK 3
15 N2 Failed Failed OK 3
16 TT2 Failed Failed OK 3
17 TT4.9 Failed Failed OK 3
18 Tfuel Failed Failed OK 3
19 Toll Failed Failed OK 3
20 Wf Resolver Failed Failed OK 3
21 SVA LVDT Failed Failed OK 3
22 Bleed Prox Input Failed Failed OK 3
23 ACC #1 LVDT Failed Failed OK 3
24 ACC #2 LVDT Failed Failed OK 3
25 Reverser LVDT Failed Failed OK 3
26 AOC LVDT Failed Failed OK 3
27 Spare LVDT Failed Failed OK 3
28 TLA Resolver Failed Failed OK 3
29 Oil Overtemperature Overtemp OK 1
30 SSM
31 SSM
32 Parity (Odd)
 SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 17

Label 350 3F

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI
10 SDI
11 PAD X
12 PAD X
13 PAD X
14 N1 Failed Failed OK 3
15 N2 Failed Failed OK 3
16 TT2 Failed Failed OK 3
17 TT4.9 Failed Failed OK 3
18 Tfuel Failed Failed OK 3
19 Toll Failed Failed OK 3
20 Wf Resolver Failed Failed OK 3
21 SVA LVDT Failed Failed OK 3
22 Bleed Prox Input Failed Failed OK 3
23 ACC #1 LVDT Failed Failed OK 3
24 ACC #2 LVDT Failed Failed OK 3
25 Reverser LVDT Failed Failed OK 3
26 AOC LVDT Failed Failed OK 3
27 Spare LVDT Failed Failed OK 3
28 TLA Resolver Failed Failed OK 3
29 Oil Overtemperature Overtemp OK 1
30 SSM
31 SSM
32 Parity (Odd)
SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 18

Label 351 2F

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI
10 SDI
11 PAD X
12 PAD X
13 PAD X
14 Left ADC Inputs Failed Failed OK 3
15 Right ADC Inputs Failed Failed OK 3
16 Wf T/M W/A Failed Failed OK 3
17 SVA T/M W/A Failed Failed OK 3
18 BLD T/M W/A Failed Failed OK 3
19 ACC #1 T/M W/A Failed Failed OK 3
20 ACC #2 T/M W/A Failed Failed OK 3
21 AOC T/M W/A Failed Failed OK 3
22 Spare T/M W/A Failed Failed OK 1
23 Wf Track Check Failed Failed OK 3
24 SVA Track Check Failed Failed OK 3
25 Bld Track Check Failed Failed OK 3
26 ACC #1 Track Check Failed Failed OK 3
27 ACC #2 Track Check Failed Failed OK 3
28 AOC Track Check Failed Failed OK 3
29 Spare Track Check Failed Failed OK 1
30 SSM
31 SSM
32 Parity (Odd)
 SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 19

Label 351 3F

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI
10 SDI
11 PAD X
12 PAD X
13 PAD X
14 Left ADC Inputs Failed Failed OK 3
15 Right ADC Inputs Failed Failed OK 3
16 Wf T/M W/A Failed Failed OK 3
17 SVA T/M W/A Failed Failed OK 3
18 BLD T/M W/A Failed Failed OK 3
19 ACC #1 T/M W/A Failed Failed OK 3
20 ACC #2 T/M W/A Failed Failed OK 3
21 AOC T/M W/A Failed Failed OK 3
22 Spare T/M W/A Failed Failed OK 1
23 Wf Track Check Failed Failed OK 3
24 SVA Track Check Failed Failed OK 3
25 Bld Track Check Failed Failed OK 3
26 ACC #1 Track Check Failed Failed OK 3
27 ACC #2 Track Check Failed Failed OK 3
28 AOC Track Check Failed Failed OK 3
29 Spare Track Check Failed Failed OK 1
30 SSM
31 SSM
32 Parity (Odd)
SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 20

Label 352 2F

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI
10 SDI
11 PAD X
12 PAD X
13 PAD X
14 Spare X 1
15 Spare X 1
16 Spare X
17 Spare X 2
18 Spare X 2
19 Spare X 2
20 TCA Valve No. 1 Failed OK 3
21 TCA Valve No. 2 Failed OK 3
22 Channel Select Discrete Failed OK 3
23 PDIU SDD Input Failed Failed OK 3
24 N1 Sensor Failed* Failed OK (Provision) 3
25 Pb Pneumatic Line* Failed OK (Provision)
26 P4.9 Pneumatic Line* Failed OK (Provision)
27 TT4.9 Thermocouple Harness* Failed OK (Provision) 3
28 PDIU Status Failed OK 3
29 T/L Forward Interlock Failed OK 3
30 SSM
31 SSM
32 Parity (Odd)

*Primary channel only.

 SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 21

Label 352 3F

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI
10 SDI
11 PAD X
12 PAD X
13 PAD X
14 Spare X 2
15 Spare X 2
16 Spare X
17 Spare X 2
18 Spare X 2
19 Spare X 2
20 TCA Valve No. 1 Failed OK 3
21 TCA Valve No. 2 Failed OK 3
22 Channel Select Discrete Failed OK 3
23 PDIU SDD Input Failed Failed OK 3
24 N1 Sensor Failed* Failed OK (Provision) 3
25 Pb Pneumatic Line* Failed OK (Provision)
26 P4.9 Pneumatic Line* Failed OK (Provision)
27 TT4.9 Thermocouple Harness* Failed OK (Provision) 3
28 PDIU Status Failed OK 3
29 T/L Forward Interlock Failed OK 3
30 SSM
31 SSM
32 Parity (Odd)

* Primary channel only.

SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 22

Label 353 2F

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI
10 SDI
11 PAD X
12 PAD X
13 PAD X
14 N1 Crosscheck Failed Failed OK 3
15 N2 Crosscheck Failed Failed OK 3
16 PB Crosscheck Failed Failed OK 1
17 PT4.9 Crosscheck Failed Failed OK 1
18 TT2 Crosscheck Failed Failed OK 3
19 TT4.9 Crosscheck Failed Failed OK 3
20 Tfuel Crosscheck Failed Failed OK 3
21 Toil Crosscheck Failed Failed OK 3
22 Wf Resolver Crosscheck Failed Failed OK 3
23 SVA Resolver Crosscheck Failed Failed OK 3
24 Bld Prox Input Crosscheck Failed Failed OK 3
25 ACC #1 LVDT Crosscheck Failed Failed OK 3
26 ACC #2 LVDT Crosscheck Failed Failed OK 3
27 Reverser LVDT Crosscheck Failed Failed OK 3
28 AOC LVDT Crosscheck Failed Failed OK 3
29 TLA Resolver Crosscheck Failed Failed OK 3
30 SSM
31 SSM
32 Parity (Odd)
 SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 23

Label 353 3F

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI
10 SDI
11 PAD X
12 PAD X
13 PAD X
14 N1 Crosscheck Failed Failed OK 3
15 N2 Crosscheck Failed Failed OK 3
16 PB Crosscheck Failed Failed OK 1
17 PT4.9 Crosscheck Failed Failed OK 1
18 TT2 Crosscheck Failed Failed OK 3
19 TT4.9 Crosscheck Failed Failed OK 3
20 Tfuel Crosscheck Failed Failed OK 3
21 Toil Crosscheck Failed Failed OK 3
22 Wf Resolver Crosscheck Failed Failed OK 3
23 SVA Resolver Crosscheck Failed Failed OK 3
24 Bld Prox Input Crosscheck Failed Failed OK 3
25 ACC #1 LVDT Crosscheck Failed Failed OK 3
26 ACC #2 LVDT Crosscheck Failed Failed OK 3
27 Reverser LVDT Crosscheck Failed Failed OK 3
28 AOC LVDT Crosscheck Failed Failed OK 3
29 TLA Resolver Crosscheck Failed Failed OK 3
30 SSM
31 SSM
32 Parity (Odd)
SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 24

Label 354 2F

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI
10 SDI
11 PAD X
12 PAD X
13 PAD X
14 REV Command Solenoid W/A Failure Failure OK 3
15 TCA Solenoid W/A Failure Failure OK 3
16 Spare Solenoid W/A Failure Failure OK 1
17 Spare Solenoid W/A Failure Failure OK 1
18 Spare Relay W/A Failure Failure OK 1
19 Spare Solenoid W/A Failure Failure OK 3
20 BCE Solenoid W/A Failure Failure OK 1
21 Spare Solenoid W/A Failure Failure OK 1
22 Oil Bypass Solenoid W/A Failure Failure OK 3
23 Hot Start Relay W/A Failure Failure OK 1
24 TLA Lockout Relay W/A Failure Failure OK 3
25 Spare Relay W/A Failure Failure OK 1
26 Spare X 1
27 Essen. Sol. Current Sense Failure Failure OK 3
28 Critical & Noncritical Current Sense Failure Failure OK 3
29 Spare
30 SSM
31 SSM
32 Parity (Odd)
 SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 25

Label 354 3F

Bit Status
Bit No. Function Notes
1 0
1 X
2 X
3 X
4 Label X
5 X
6 X
7 X
8 X
9 SDI
10 SDI
11 PAD X
12 PAD X
13 PAD X
14 REV Command Solenoid W/A Failure Failure OK 3
15 TCA Solenoid W/A Failure Failure OK 3
16 Spare Solenoid W/A Failure Failure OK 1
17 Spare Solenoid W/A Failure Failure OK 1
18 Spare Relay W/A Failure Failure OK 1
19 Spare Solenoid W/A Failure Failure OK 3
20 BCE Solenoid W/A Failure Failure OK 1
21 Spare Solenoid W/A Failure Failure OK 1
22 Oil Bypass Solenoid W/A Failure Failure OK 3
23 Hot Start Relay W/A Failure Failure OK 1
24 TLA Lockout Relay W/A Failure Failure OK 3
25 Spare Relay W/A Failure Failure OK 1
26 Spare X 1
27 Essen. Sol. Current Sense Failure Failure OK 3
28 Critical & Noncritical Current Sense Failure Failure OK 3
29 Spare
30 SSM
31 SSM
32 Parity (Odd)
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401 – 7645 USA

SUPPLEMENT 11
TO

ARINC SPECIFICATION 429

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

Published: July 22, 1988

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: June 15, 1988

SUPPLEMENT 11 TO ARINC SPECIFICATION 429 – Page 2

A. PURPOSE OF THIS SUPPLEMENT
This Supplement introduces new label assignments and
equipment identification codes.
B. ORGANIZATION OF THIS SUPPLEMENT
The first part of this document, printed on goldenrod
paper, contains descriptions of the changes introduced
into the Specification by this Supplement, and, where
appropriate, extracts from the original text for comparison
purposes. The second part consists of replacement white
pages for the Specification, modified to reflect these
changes. The modified and added material on each
replacement page is identified with “c-11” symbols in the
margins. Existing copies of Specification 429 may be
updated by simply inserting the replacement white pages
they replace. The goldenrod pages should be inserted
inside the rear cover of the Specification.
Copies of the Specification bearing the number 429-11
already contain this Supplement and thus do not require
revisions by the reader.
C. CHANGES TO SPECIFICATION 429
INTRODUCED BY THIS SUPPLEMENT
This section presents a complete tabulation of the changes
and additions to the Specification introduced by this
Supplement. Each change or addition is entitled by the
section number and title currently employed in the
Specification or by the section number and title that will
be employed when the Supplement is eventually
incorporated. In each case there is included a brief
description of the addition or change and, for other than
very minor revisions, any text originally contained in the
Specification is reproduced or reference.
271 002, 274 0C5, 275 002, 276 001, 276 002, 276 003,
300 039, 300 040, 301 002, 301 039, 301 040, 302 002,
302 039, 302 040, 303 002, 304 039, 304 040, 305 039,
305 040, 306 039, 306 040, 307 039, 307 040, 314 002,
316 002, 322 002, 341 002, 342 002, 343 01A, 350 00B,
350 027, 350 040, 350 241, 350 341, 351 00B, 351 029,
354 002, 355 027, 360 002.
Label 076 008 changed from “Ellipsoidal Altitude” to
“GPS Height Above Referenced Ellipsoid”.
ATTACHMENT 1 – EQUIPMENT CODES
The following codes have been given new assignments:
039, 040, 041, 08E, 08F, 0AA, 0AB, 0AC, 0AE, 0AF,
0BA, 0BB, 0BC, 0BD, 0BE, 0BF, 0C2, 0CA, 0CB, 0CC,
0CD, 0CE, 0CF, 0DA, 0DB, 0DC, 0DD, 0DE, 0DF, 0EA,
0FF, 10A, 10B, 10C, 10C, 10D, 10E, 10F, 110, 12A, 12B,
136, 141, 241, 341.
ATTACHMENT 2 – DATA STANDARDS
Data Standards entered for new labels:
Label 076 008 changed from “Ellipsoidal Altitude” to
“GPS Height Above Referenced Ellipsoid”.
Data Standards revised for following labels:
076 00B, 077 00B, 270 00B
ATTACHMENT 6
Example revised for label 077 00B.
Example for label 260 removed.

2.1.5.1 BCD Numeric, Discrete, Aim Data, and File Example for label 260 031 expanded to include 260 002.
Transfer Words
Format for label 270 00B added.
SSM bit patterns separated from main figure.
Format for label 274 0C5 added.
FIGURE 3-1 RADION SYSTEMS MANAGEMENT
WORD FORMATS Format for label 350 027 added.

HF COM frequency control words added. Code for 747 NR corrected in diagram of TPIS word.
ATTACHMENT 1 – LABEL CODES Equipment ID word expanded to accommodate three-
character identifier.
070 002, 070 0CC, 071 002, 071 0CC, 072 002, 072 0CC,
073 0CC, 074 002, 100 0BB, 101 0BB, 103 0BB, 104 ATTACHMENT 9 – GENREAL AVIATION
0BB, 105 0BB, 106 0BB, 107 002, 114 0CC, 115 0BC, EQUIPMENT IDENTIFIERS
115 0CC, 116 0CC, 117 0CC, 126 002, 127 002,143 041,
143 241, 144 041, 144 341, 150 002, 152 041, 153 002, Code 08C added to list.
153 041, 162 0DE, 173 0BD, 200 002, 202 002,203 002,
204 002, 205 002, 205 0B9, 206 0CC, 207 002, 207 0B9, Codes for Loran and Omega changed from 08A/08B to
211 002, 213 002, 213 08D, 220 002, 220 017, 220 024, 05A/05B, respectively.
220 07E, 221 002, 221 017, 221 024, 221 07E, 222 002,
222 017, 222 024, 222 07E, 223 002, 223 017, 223 024,
223 07E, 224 002, 224 017, 224 024, 224 07E, 225 002,
226 0XX, 230 002, 230 017, 230 024, 230 07E, 241 002,
242 011, 243 0XX, 244 011, 244 08D, 245 002, 246 002,
246 006, 246 009, 247 002, 247 009, 247 0EB, 250 002,
250 12B, 252 0EB, 253 002, 254 002, 254 012, 255 002,
255 012, 255 08E, 256 002, 256 027, 257 002, 257 027,
263 002, 263 010, 264 002, 264 010, 265 002, 267 002,
 NOTE: Due to the large number of changes
Created by this Supplement, it is NOT
available separately to update 429-11.

AERONAUTICAL RADIO, INC.

2551 Riva Road
Annapolis, Maryland 21401 – 7645 USA

SUPPLEMENT 12
TO

ARINC SPECIFICATION 429

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

Published: July 1, 1990

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: October 25, 1989
SUPPLEMENT 12 TO ARINC SPECIFICATION 429 – Page 2
A. PURPOSE OF THIS SUPPLEMENT
The Supplement introduces the Williamsburg bit-oriented
file data transfer protocol which supports the transfer of
binary and character data. The previous AIM and
character-oriented file transfer protocol sections are
moved to Appendix 6. The Sign Status Matrix (SSM)
information is revised and reorganized. In addition, this
Supplement introduces new label assignments and
equipment identification codes.
B. ORGANIZATION OF THIS SUPPLEMENT
The first part of this document, printed on goldenrod
paper contains descriptions of the changes introduced into
the Specification by this Supplement, and, where
appropriate, extracts from the original text for comparison
purposes. The second part consists of replacement white
pages for the Specification, modified to reflect these
changes. The modified and added material on each
replacement page is identified with “c-12” symbols in the
margins. Existing copies of Specification 429 may be
updated by simply inserting the replacement white pages
they replace. The goldenrod pages should e inserted
inside the rear cover of the Specification.
Copies of the Specification bearing the number 429-12
already contain this Supplement and thus do not require
revisions by the reader.
C. CHANGES TO SPECIFICATION 429
INTRODUCED BY THIS SUPPLEMENT
This section presents a complete tabulation of the changes
and additions to the Specification introduced by this
Supplement. Each change or addition is entitled by the
section number and title currently employed in the
Specification, or by the section number and title that will
be employed when the Supplement is eventually
incorporated. In each case there is included a brief
description of the addition or change and, for other than
very minor revision, any text originally contained into the
Specification reproduced for reference.
2.1.3 Information Identifier
This section contains editorial corrections to comply with
changes introduced in Supplement 11.
2.1.5 Sign/Status Matrix
This section was revised and reorganized. The changes
include moving the AIM and file transfer SSM definitions
to Appendix 6, adding failure reporting to the discrete
word truth table (Section 2.1.5.3) and moving the
description of status priorities to Section 2.1.5.
2.3.1 Digital Language
The contents of Sections 2.3.1.4 through 2.3.1.5.7 were
moved to Appendix 6. The AIM Data and File Data
Transfer section headings were retained for reference
purposes. Section 2.3.1.5. File Data Transfer, provides
the reason for moving the original file transfer protocol
and introduces the Williamsburg protocol.
2.5 Bit-Oriented Communications Protocol
This new section was added to describe a bit-oriented data
transfer protocol. The new protocol was developed to
accommodate the interface of the ACARS Management
Unit (MU) and the Satellite Data Unit (SDU).
3.2 AIM Information Transfer
The information previously contained in this section is no
longer applicable to ARINC Specification 429. For
reference purposes, the section header is retained and the
original contents of this section are located in Appendix
6.
ATTACHMENT 1 – LABEL CODES
The following labels have been given new assignments:
002 115, 013 0B8, 016 0B8, 046 10A, 046 10B, 047 10A,
047 10B, 107 0BB, 110 0BB, 112 0BB, 114 0BB, 114
10A, 114 10B, 127 10A, 127 10B, 130 035, 130 10A130
10B, 131 035, 132 035, 133 10A, 133 10B, 134 10A, 134
10B, 137 10A, 137 10B, 155 10A, 155 10B, 156 10A,
156 10B, 157 10A, 157 10B, 160 10A, 160 10B, 161
10A, 161 10B, 201 115, 203 035, 203 10A, 203 10B, 205
10A, 205 10B, 211 10A, 211 10B, 220 116, 221 116, 222
115, 222 116,223 116, 224 116, 226 035, 230 116, 234
039, 234 040, 235 039, 235 040, 236 039, 236 040, 237
039, 237 040, 244 10A, 244 10B, 256 114, 257 114, 260
10A, 260 10B, 260 114, 261 10A, 261 10B, 261 114, 262
10A, 262 10B, 262 114, 263 10A, 263 10B, 263 114, 264
10A, 264 10B, 264 114, 265 004, 265 038, 265 10A, 265
10B, 265 114, 267 10A, 267 10B, 270 10A, 270 10B, 270
114, 270 115, 271 10A, 271 10B, 271 114, 272 002, 272
10A, 272 10B, 272 114, 273 10A, 273 10B, 273 114, 274
10A, 274 10B, 274 114, 275 10A, 275 10B, 275 114, 276
114, 277 018, 300 10A, 300 10B, 300 TBD, 301 10A, 301
10B, 302 10A, 302 10B, 303 10A, 303 10B, 304 10A,
304 10B, 305 10A, 305 10B, 306 10D, 310 114, 311 114,
312 114, 313 114, 316 10A, 316 10B, 320 035, 321 10A,
321 10B, 322 10A, 322 10B, 323 10A, 323 10B, 324
10A, 324 10B, 325 10A, 325 10B,326 10A, 326 10B, 327
10A, 327 10B, 330 10A, 330 10B, 331 10A, 331 10B,
335 10A, 335 10B, 336 002, 336 10A, 336 10B, 337 002,
337 002, 337 10A, 337 10B, 341 10A, 341 10B, 342 10A,
342 10B, 343 10A, 343 10B, 344 10A, 344 10B, 345
10A, 345 10B, 346 10A, 346 10B, 347 10A, 347 10B,
350 10A, 350 10B, 350 114, 350 115, 351 10A, 351 10B,
351 114, 352 10A, 352 10B, 352 114, 353 10A, 353 10B,
353 114, 354 10A, 354 10B, 357 035, 360 10A, 360 10B,
360 TBD, 361 10A, 361 10B, 362 10A, 362 10B, 362
115, 363 10A, 363 10B, 365 TBD, 372 10A, 372 10B,
373 10A, 373 10B, 374 10A, 374 10B, 374 TBD, 375
10A, 375 10B, 375 TBD.
Revised label 130 035 from “Traffic Advisory Range” to
“Intruder Range”.
Revised label 131 035 from “Traffic Advisory Altitude”
to “Intruder Altitude”.
Revised label 132 035 from “Traffic Advisory Bearing”
to “Intruder Bearing”.
 SUPPLEMENT 12 TO ARINC SPECIFICATION 429 – Page 3

Removed label 130 030 Traffic Advisory Range. ATTACHMENT 11 – BIT-ORIENTED DATA FILE
TRANSFER WORD FORMATS
Removed label 131 030 Traffic Advisory Altitude.
Add new Attachment.
Removed label 132 030 Traffic Advisory Bearing ATTACHMENT 11A – DESTINATION CODES
Estimate.
Add new Attachment.
Removed label 270 030 Transponder Discrete.
ATTACHMENT 11B – STATUS CODES
Removed label 347 030 Sector Control.
Add new Attachment.
Removed label 347 035 Antenna Control.
ATTACHMENT 11C – ALOHA/ALOHA RESPONSE
ATTACHMENT 1 – EQUIPMENT CODES PROTOCOL WORDS

The following codes have been given new assignments: Add new Attachment.

113, 114,115, 116, 117, 118, 119, 11A, 123, 124, 125, ATTACHMENT 12 – FILE TRANSFER EXAMPLE
126, 127, 128, 129, 15A, 15B, 15C, 15D, 15E, 16A, 16B,
16C, 16D, 16E, 17A, 17B, 17C, 18A, 18B, 18C, 18D, Add new Attachment.
18E, 18F.
ATTACHMENT 12A – FILED MAPPING EXAMPLE
ATTACHMENT 2 – DATA STANDARDS
Add new Attachment.
Tables 1, 2 updated to reflect changes to Attachment 1.
ATTACHMENT 13 – PROTOCOL DETERMINATION
Binary Data notes 6, 7 and 8 added. PROCEDURE DIAGRAMS

Discrete Data Standards entered for new labels: Add new Attachment.

272 002, 271 018, 272 018, 273 018, 275 018, 276 018, ATTACHEMENT 14 – SYSTEM ADDRESS LABELS
277 018, 274 018, 270 035, 271 035, 273 035, 274 035,
275 035, 013 0B8, 016 0B8, 161 10A, 161 10B, 350 114, Add new Attachment.
351 114, 352 114, 353 114, 270 115, 350 115.
ATTACHMENT 15 – LINK LAYER CRC DATA
ATTACHMENT 6 – GENERAL WORD FORMATS EXAMPLE
AND ENCODING EXAMPLES
Add new Attachment.
Add format for TCAS Intruder Range label 130.
APPENDIX 6 – FORMER MAINTENANCE, AIM AND
Add format for TCAS Intruder Altitude label 131. FILE TRANSFER TECHNIQUES
Add format for TCAS Intruder Bearing label 132. Add new Appendix.

Add format for Transponder Altitude/TCAS Own A/C APPENDIX 7 – MATHMATICAL EXAMPLE OF CRC
Altitude label 203. ENCODING/DECODING

Removed 730 ASAS Sector Control Word example. Add new Appendix.

Removed 730 TCAS Traffic Advisory Range Word

example.

Removed 730 TCAS Traffic Advisory Altitude Word

example.

Removed 730 TCAS Traffic Advisory Bearing Estimate

word example.

ATTACHMENT 9B – GENERAL AVIATION WORD

EXAMPLES

Add new Company Name Identifier.

ATTACHMENT 10 – VARIABLES OF BIT-

ORIENTED PROTOCOL

Add new Attachment.

 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401 – 7645 USA

SUPPLEMENT 13

TO

ARINC SPECIFICATION 429

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

Published: December 30, 1991

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: October 8, 1991

SUPPLEMENT 13 TO ARINC SPECIFICATION 429 – Page 2
A. PURPOSE OF THIS SUPPLEMENT
This Supplement introduces changes made to the
Williamsburg protocol as a result of its initial
implementation. This protocol supports the transfer of
binary and character data. In addition, this Supplement
introduces new label assignments and equipment
identification codes.
B. ORGANIZATION OF THIS SUPPLEMENT
The first part of this document, printed on goldenrod
paper contains descriptions of changes introduced into
this Specification by this Supplement. The second part
consists of replacement white pages for the Specification,
modified to reflect the changes. The modified and added
material on each page is identified by a c-13 in the
margins. Existing copies of ARINC Specification 429
may be updated by simply inserting the replacement
white pages where necessary and destroying the pages
they replace. The goldenrod pages are inserted inside the
rear cover of the Specification.
C. CHANGES TO ARINC SPECIFICATION 429
INTRODUCED BY THIS SUPPLEMENT
This section presents a complete tabulation of the changes
and additions to the Specification introduced by this
Supplement. Each change or addition is defined by the
section number and the title currently employed in the
Specification or by the section name and title that will be
employed when the Supplement is eventually
incorporated. In each case a brief description of the
change or addition is included.
AEEC STAFF NOTE: THESE CHANGES
APPLY TO ARINC 429, PART 3 ONLY.
2.3.1.5 File Data Transfer
An editorial change, correction to section numbering.
2.3.1.5.1 Bit-Oriented Protocol Determination
New Section added to describe ALO/ALR protocol
process to be used when a bilingual Link Layer protocol
system needs to determine necessary bit-oriented
interfaces.
2.5 Bit-Oriented communications Protocol
Included term “Williamsburg” parenthetically since this
terminology well-known in industry. Added commentary
to explain non-negotiation or parameters in this protocol.
D. Corrected Network Layer definition.
2.5.2 Link Data Unit (LDU) Size and Word Count
Added second paragraph to text, since it is a requirement,
and removed second paragraph from commentary.
2.5.4 Bit Rate and Word Timing
Corrected the commentary to change the more ambiguous
term “message” to LDU.
2.5.5.3 Destination Code
An editorial change was made.
2.5.6 Response to RTS
The last sentence in the second paragraph was reworded
and moved to a more appropriate section, 2.5.6.2.
2.5.6.1 Clear to Send (CTS)
In the second to last sentence, the word “valid” was added
to clarify the Not clear to send condition. The last
sentence was added to clarify the resetting of RTS
counters.
2.5.6.2 Not Clear to Send (NCTS)
The first paragraph was updated to include the
information deleted from Section 2.5.6 and to clarify the
validity requirements. The second paragraph was updated
to describe that and NCTS counter would be reset upon a
valid CTS response. The last sentence in the third
paragraph was deleted and it’s content expanded in the
following commentary of that section.
2.5.6.3 Destination Busy
The second paragraph of this section was updated to
indicate that a BUSY counter should be reset with a valid
CTS response to RTS.
2.5.7 No Response to RTS
The first paragraph of this section was updated to describe
proper response to RTS.
2.5.9 Unexpected RTS
This section was updated to include editorial changes and
a description of the correct responses to RTS. The last
sentence was deleted as redundant to Section in 2.5.13.1
and in conflict with other possible responses.
2.5.11 Data
The fourth paragraph of this section was updated to
describe the proper ending of an LDU transmission, and
to include the optional NAK response for receipt of an
incomplete octet.
2.5.11.3 Character Data Words
In the last paragraph, the “note” designator was removed
and the text clarified for the transfer of characters with a
parity bit.
2.5.13 Negative Acknowledgement (NAK)
This section was updated to clarify conditions for sending
the NAK word.
 SUPPLEMENT 13 TO ARINC SPECIFICATION 429 – Page 3

2.5.13.1 Missing SOT word ATTACHMENT 10 – VARIABLES OF BIT

Text was corrected to refer to “reception” instead of
“transmission” of a valid SOT word. Also, incorrect text
referring to the NAK response timing was deleted.
2.5.13.2 LDU Sequence Number Error
ORIENTED PROTOCOL
Tables 10-1 and 10-3 were updated to include events N5,
N6, and time T12. Options 07 and 012 in Table 10-4 were
changed to spares for consistency with corresponding text
updates.

The original text was omitted. Sections 2.5.13.1 –

2.5.13.7 were renumbered. ATTACHMENT 11C – ALOHA/ALOHA RESPONSE
PROTOCOL WORD DEFINITION
2.5.13.3 Parity Errors
Table 11C-3 was added to clarify protocol version
A commentary section was added to describe the number assignments, and is referenced by “note 1”.
procedures for receiving words with bad parity. “Note 2” was added to describe the GFI field of the
ALOHA word.
2.5.13.4 Word Count Errors
ATTACHMENT 12A – FIELD MAPPING EXAMPLE
This section was updated to clarify the NAK response
time for word count errors. Bk was changed to B24 in the data word map, “nibble” was
changed to “semi-octet”, and semi-octet arrow lengths
2.5.13.5 CRC Errors were shortened to correspond to the proper four and eight-
bit lengths.
This section was updated to clarify the NAK response
time for CRC errors. APPENDIX 7 – MATHEMATICAL EXAMPLE OF
CRC ENDODING/DECODING
2.5.13.6 Time Out Errors
Format (alignment) changes were made in the polynomial
This section was renumbered. divisions, “(X)” was corrected to “Q(x)”, and the
transmission order for the LDU Mapping of the 24-bit
2.5.13.7 Restart Initialization example was deleted to avoid possible misinterpretation.

This section was omitted due to potential conflicts with

the ALO/ALR procedures.

2.5.14 LDU Transfer Acknowledgement (ACK)

Text was revised to include LDU conditions for sink

acknowledgement transmission.

2.5.14.1 Duplicate LDU

This section was added to describe duplicate LDU

occurrences.

2.5.14.2 Auto-Synchronized Files

This section was added to describe the method of

handling auto-synchronized files.

2.5.15 SYN Word

New text was added to describe SYN response times for

non-consecutive LDU Sequence numbers. The last
paragraph was incorrect and deleted.

2.5.16 Response to ACK/NAK/SYN

New text was added to describe actions when NAK and

SYN are detected during a transmission.

2.5.19 ALO Response

A new section was added and updated to describe ALO

responses.
 Copyright 1993 by
AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401 – 7645 USA

SUPPLEMENT 14

TO

ARINC SPECIFICATION 429

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

Published: January 4, 1993

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: November 4, 1992

SUPPLEMENT 14 TO ARINC SPECIFICATION 429 – Page 2
A. PURPOSE OF THIS SUPPLEMENT
This Supplement introduces changes made to increase the
efficiency of data transfer across an ARINC 429 high
speed bit-oriented link. This protocol supports the
transfer of binary and character data.
B. ORGANIZATION OF THIS SUPPLEMENT
The first part of this document, printed on goldenrod
paper, contains descriptions of changes introduced into
this Specification by this Supplement. The second part
consists of replacement white pages for the Specification,
modified to reflect the changes. The modified and added
material on each page is identified by a c-14 in the
margins. Existing copies of ARINC 429 may be updated
by simply inserting the replacement white pages where
necessary and destroying the pages they replace. The
goldenrod pages are inserted inside the rear cover of the
Specification.
C. CHANGES TO ARINC SPECIFICATION 429
INTRODUCED BY THIS SUPPLEMENT
This section presents a complete tabulation of the changes
and additions to the Specification introduced by this
Supplement. Each change and addition is defined by the
section number and the title currently employed in the
Specification or by the section name and title that will be
employed when the Supplement is eventually
incorporated. In each case a brief description of the
change or addition is included.
AEEC STAFF NOTE: THESE CHANGES
APPLY TO ARINC 429, PART 3 ONLY.
2.3.1.5 File Data Transfer
An editorial change was needed to reference new section.
2.3.1.5.1 Bit-Oriented Protocol Determination
This section was expanded to include determination of
different version numbers of the bit-oriented protocol, and
was moved to Section 2.5.19.
2.5 Bit-Oriented Communication Protocol
An editorial change references a new section number.
2.5.4 Bit Rate and Word Timing
A maximum word gap of 64 bit-times, (averaged over the
LDU transmission) was added to eliminate excessive
delay in source transmission time.
Note: Sections 2.5.5 through 2.7 have been renumbered
and reordered for consistency.
2.5.5 Word type
The basic definition of “word type” was corrected to
include bits 31-29 in all bit-oriented words of an LDU.
2.5.6 Protocol Words
This section was added to specifically define the word
type for protocol words.
2.5.6.1 Protocol Identifier
This section was added to clarify the definition of bits 28-
25 for protocol words and to specify the relevant addition
for error conditions.
2.5.6.2 Destination Code
This section was updated, and a commentary added, to
clarify the role of the link layer protocol for upward
compatibility with changing network functionality. The
requirement for Destination code validation is not a link
layer function.
2.5.6.3 Word Count
This section was renumbered.
2.5.7 Request to Send (RTS)
This section was previously titled “Response to TS”, and
has been renumbered. The title was changed for
consistency, and an introductory paragraph added to
clarify the basic RTS function.
2.5.7.1 Clear to Send (CTS)
This section was renumbered.
2.5.7.2 Not Clear to Send (NCTS)
This section was renumbered.
2.5.7.3 Destination Busy
This section was renumbered, and an introductory
replacement paragraph inserted to clarify the “optional”
BUSY response, which may be used when a system
cannot accept a transmission by the source in a “timely
manner”. New commentary equates a “timely manner” to
the shorter retry sequence of the NCTS series.
2.5.7.4 No Response to RTS
This section was renumbered, and the ALOHA word was
included in the logic for error determination.
2.5.10 Start of Transmission (SOT)
Timer T13 was added as a requirement on the source to
begin transmission of an LDU within a specified interval
after receipt of the CTS word from the sink.
2.5.10.1 General Format Identifier (GFI)
This section was updated, and commentary added to
clarify the role of the GFI in pre-OSI as well as OSI
environments. Validation of the GFI code is required by
a high level entity (network layer) in both environments
to determine the format of the data words to follow. GFI
validation is not necessarily a link layer function.
 SUPPLEMENT 14 TO ARINC SPECIFICATION 429 – Page 3
2.5.11 Data
All references to Character Data word formats were
deleted.
2.5.11.3 Character Data Words
This section was deleted. The Character Data Word
format was removed from Supplement 14, as the format is
incompatible with those for Full and Partial Data word
formats. Currently, both binary and character data are
transmitted in octets defined by the other two data word
formats. The special character data format is not
required.
2.5.12.1 CRC Encoding
References to character data words were deleted. The
text for equation: M9x) = x16G(x) + R(x) was corrected
by moving the “bar” from G(x) to R(x).
2.5.13 Negative Acknowledgement (NAK)
NAK word interpretation was changed to remove
constraint on source for specific order of file sequencing
(i.e. Allows source to restart file with new FSN if
necessary).
2.5.14.1 Duplicate LDU
This first paragraph was rewritten to clarify.
2.5.14.3 Incomplete File Timer
This section was added to allow the sink to discard a
partial file of multiple LDUs when the T14 timeout
between LDU transmissions is exceeded. It ensures that a
source device cannot “lock-up” a sink.
2.5.15 SYN Word
The LDU sequence anomalies which generate a SYN
response by the sink were clarified.
2.5.16 Response to ACK/NAK/SYN
The T16 timer was introduced to replace T10 and T8. Also,
the action taken by the source upon receipt of a SYN
word was updated, which relaxes requirements to
maintain a specific File Sequence ordering by the source.
2.5.19 Protocol Initialization
2.5.19.1 Bit-Oriented Protocol Version,
2.5.19.2 ALOHA Response, and
2.5.19.3 Character-429 Determination
This section has been added to replace and expand on the
definition of the process to determine the link layer
protocol version supported by an interfacing system.
These sections replace three sections from Supplement
13.
2.3.1.5.1 Bit-Oriented Protocol Determination
2.5.19 ALO Response, and
2.5.20 Bit Protocol Verification
2.6 Windowed Bit-Oriented Protocol
This is a completely new section which contains the
system description of the new LLC2-like bit-oriented link
layer protocol for 429. It is based on Section 2.5, “Bit-
Oriented Communications Protocol”, with expanded text
as specified to allow for more efficient use of the 429
high (or low) speed data bus through “windowing”. The
definition includes provision for a Link Control Word
prior to each LDU.
ATTACHMENT 1 – EQUIPMENT CODES
New Equipment Code Identifiers were added.
ATTACHEMENT 6 – WORD FORMATS AND
ENCODING EXAMPLES
Example added for label 171.
ATTACHMENT 10 – VARIABLES OF BIT
ORIENTED PROTOCOL
Table 10-1 was updated to include a standard value for
N7, the maximum number of LDUs in a window (see
Section 2.6 “Windowed Bit-Oriented Protocol”).
Table 10-3 deleted Option 6 (O6) for NAK Send Time,
and deleted Option 9 (O9) for the Character Data Word,
both of which are no longer used.
Table 10-4 was revised to include columns for low speed
maximum and minimum values. These values were
established for timers and as response time design goals
for incoming transmissions. Timers T13 through T16 were
added.
Table 10-5 was added to include a definition of high
speed maximum and minimum values for timers and
response time design goals. The format is the same as the
revised Table 10-4. Timer T10 is not used in the high
speed protocol.
Table 10-6 was added to include notes to Tables 10-1
through 10-5.
ATTACHMENT 11 – BIT-ORIENTED DATA FILE
TRANSFER WORD FORMATS
Table 11-1A added “spares” for the deleted Character
Data Formats and corrected “Protocol Data Word” to read
“Protocol Word”.
Table 11-4 updated definitions for bits 9 through 24 of the
ALO and ALR words, and added the LCW (LDU Control
Word) format definition.
Table 11-4A was added as a partial replacement for
ATTACHMENT 11C and Table 11-4B was added to
define the new window definitions for the Windowed Bit-
Oriented protocol in Section 2.6.
Table 11-6A was revised, changing the former GFI bit
pattern (0001) for ISO 8208 to “unassigned”. The bit
pattern (0100) for ISO 8473 was changed to a more
SUPPLEMENT 14 TO ARINC SPECIFICATION 429 – Page 4

ATTACHMENT 11 – BIT-ORIENTED DATA FILE

TRANSFER WORD FORMATS (cont’d)
generic ISO 9577 definition. The bit pattern 1110
(hex”E”) is now defined as “ACARS VHF Format”.The
“NOTES” in ATTACHMENT 11 have been renumbered
to correspond to the new table definitions.

ATTACHMENT 11C – ALOHA/ALOHA RESPONSE

PROTOCOL WORD DEFINITION

This Attachment has been deleted. This information has

been moved to Tables 11-4, 11-4A, and 11-4B.

ATTACHMENT 13A – ALOHA VERSION

DETERMINATION SEQUENCE

This Attachment was added to support the ALOHA

version determination sequence called out in Section
2.5.19.1.1.
ATTACHMENT 14 – SYSTEM ADDERESS LABELS

New System Address Labels (SAL) were added.

ATTACHMENT 16 – SEQUENCE OF PROTOCOL

AND DATA WORDS IN WINDOW TRANSFER

This Attachment was added to illustrate the window

transfers for new Section 2.6.

ATTACHMENT 17 – FLOW DIAGRAM USED TO

DETERMINE CHARACTER-ORIENTED VS BIT-
ORIENTED PROTOCOL

This Attachment was added to illustrate the logic flow

that determines whether a character-oriented or bit-
oriented link layer protocol interface is to be used.
 Copyright 1995 by
AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401 – 7645 USA

SUPPLEMENT 15

TO

ARINC SPECIFICATION 429

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

Published: September 1, 1995

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: April 18, 1995

SUPPLEMENT 15 TO ARINC SPECIFICATION 429 - Page 2
A. PURPOSE OF THIS DOCUMENT
This Supplement introduces new label assignments,
equipment IDs, system address labels and updates to the
429W protocol.
B. ORGANIZATION OF THIS SUPPLEMENT
The first part of this document, printed on goldenrod paper
contains descriptions of changes introduced into this
Specification by this Supplement. The second part consists
of replacement white pages for the Specification, modified
to reflect the changes. The modified and added material on
each page is identified by a c-15 in the margins. Existing
copies of ARINC Specification 429 may be updated by
simply inserting the replacement white pages where
necessary and destroying the pages they replace. The
goldenrod pages are inserted inside the rear cover of the
Specification.
C. CHANGES TO ARINC SPECIFICATION 429
INTRODUCED BY THIS SUPPLEMENT
This section presents a complete tabulation of the changes
and additions to the Specification introduced by this
Supplement. Each change or addition is defined by the
section number and the title currently employed in the
Specification or by the section name and title that will be
employed when the Supplement is eventually incorporated.
In each case a brief description of the change or addition is
included.
2.0 Digital Information Transfer System Standards
Numerous changes were made to the protocol throughout
this Section.
2.1.5.3 Discrete Data Words
The technique for encoding SSM bits in discrete words
were revised.
ORIGINAL TEXT FOLLOWS:
2.1.5.3 Discrete Data Words
A source system should annunciate any detected failure that
could cause one or more of the words normally output by
that system to be unreliable. Three methods are defined.
The first method is to set bit numbers 30 and 31 in the
affected word(s) to the “Failure Warning” code defined in
the table below. This is the preferred method. Words
containing the “Failure Warning” code should continue to
be supplied to the data bus during the failure condition.
When using the second method, the equipment may stop
transmitting the affected word or words on the data bus.
The third method applies to data words which are defined
such that they contain failure information within the data
field. For these applications, refer to the associated ARINC
equipment characteristic to determine the proper SSM
reporting.
The “No Computed Data” code should be annunciated in
the affected Discrete Data word(s) when a source system is
unable to compute reliable data for reasons other than
system failure.
When the “Functional Test” code appears as a system
output, it should be interpreted as advice that the data in the
Discrete Data word contents are the result of the execution
of a functional test.
DISCRETE DATA WORDS
Meaning
Bit
30
0 0 Verified Data, Nomal Operation
0 1 No Computed Data
1 0 Functional Test
1 1 Failure Warning
2.2.2 Modulation
The following Commentary was added:
“Avionics manufacturers are warned that bus activity
monitoring should be implemented with caution. Crossed
wiring (interchanging A and B) at one end of the bus, which
will cause improper LRU/system operation, may not
necessarily be detected by a “simple” bus activity monitor.”
2.2.4.2 Receiver Input Impedance
The word “parallel” was changed to “combination”.
Figure 3.1 Radio Systems Management Word Formats
VHF Com Frequency Word - Bits 7,8,20,23 changed to “0”
and bits 15,16,21,28 changed to “1”.
ATTACHMENT 1 - LABEL CODES
This attachment was updated according to the tables on the
following pages.
Designation for label 155 027 changed from BCD to BNR.
ATTACHMENT 1 - LABEL CODES
The following new equipment codes were assigned:
03D, 053, 05A, 0D0, 0E0, 12C, 160, 19F, 13B
ATTACHMENT 2 - DATA STANDARDS
This attachment was updated according to the tables on the
following pages. Newly assigned discrete word formats are
included.
In word 270 115, bit 12 was changed from “pad” to “Tune”.
AUTOTUNE was assigned for “1” and NO AUTOTUNE
was assigned to “0”.
Word 155 027 moved from Table 1 to Table 2.
In Table 2 “SIG DIG” was changed to “SIG BIT”.
In Table 2 under label 077, “0--” was changed to “037”.
Duplicate 244 08D word removed.
 SUPPLEMENT 15 TO ARINC SPECIFICATION 429 - Page 3

ATTACHMENT 6 - GENERAL WORD FORMATS AND APPENDIX 8 - INTEROPERABILITY OF BIT-

ENCODING EXAMPLES ORIENTED LINK LAYER PROTOCOL
Table 2 - examples for Flight Director Pitch and Total Air Appendix added.
Temp corrected.
APPENDIX 9 - SDL DIAGRAMS OF THE
Examples for the following tables added. WILLIAMSBURG PROTOCOL
Manufacturer Specific Data Word Appendix added.
010101 assigned to Garmin
010110 assigned to ARNAV Systems
Bit 11 modified for label 150 to include reference to
precision source.
Word format for label 077 00B removed (from two places).
ATTACHMENT 9B - GENERAL AVIATION WORD
EXAMPLES
Manufacturer Specific Data Word
010101 assigned to Garmin
010110 assigned to ARNAV Systems

ATTACHMENT 10 - VARIABLES OF BIT-ORIENTED

PROTOCOL
Revised Notes 1 and 4.

Table 10-3 BIT-ORIENTED PROTOCOL OPTIONS -

Added Option 012

Table 10-5 VARIABLES OF HIGH SPEED BIT-

ORIENTED PROTOCOL - Revised Time T10 min and max
values.

ATTACHMENT 11 - BIT-ORIENTED DATA FILE

TRANSFER WORD FORMATS
Table 11-6A GENERAL FORMAT IDENTIFIER (GFI) -
Revised “Reserved ISO 9577” to “ISO 9577”

ATTACHMENT 11A - DESTINATION CODES

Added Cabin Packet Data Function. Corrected Ground
Station bit encoding.

ATTACHMENT 11B - STATUS CODES

Revised description of Code 86. Added entries for Code 8E
through 95.
ATTACHMENT 14 - SYSTEM ADDRESS LABELS

The following labels were added:

170 DFDAU (Mandatory Load Function)
266 Cabin Video System (Airshow)
334 Cabin Telecommunications Unit (CTU)
340 HF Data Radio/Data Unit #1
344 HF Data Radio/Data Unit #2
The following labels were revised:
175 HGA HPA
176 Spare
177 LGA HPA
 NEW AND REVISED BNR LABEL ASSIGNMENTS

SUPPLEMENT 15 TO ARINC SPECIFICATION 429 - Page 4

MIN MAX
LABEL EQ ID PARAMETER BINARY UNITS RANGE SIG RESOL REF NOTES
TI TI
New 061 002 ACMS Information 10 See Att. 6
New 062 002 ACMS Information 10 See Att. 6
New 063 002 ACMS Information 10 See At. 6
New 145 002 TACAN Control See Section 3.1.4 180 220 8 See Att. 6
Add 226 002 Min Op. Fuel Temp (non-conflicting) 34
New 233 002 ACMS Information 10 See Att. 6
New 234 002 ACMS Information 10 See Att. 6
New 235 002 ACMS Information 10 See Att. 6
New 236 002 ACMS Information 10 See Att. 6
Revise 265 002 Min Buffet Airspeed 11 31
Revise 360 002 Flight information See Att. 6
Revise 370 004 g 31
Revise 014 005 Magnetic Heading Deg 31
Revise 370 005 g 31
Revise 205 006 Mach 4096 31
Revise 205 01A Mach 4096 31
New 034 025 VOR/ILS Frequency 125 250 6
New 035 025 DME Frequency 125 250 6
New 060 025 S/G HARDWARE PART NO. 6 See Att. 6
New 061 025 S/G HARDWARE PART NO. 6 See Att. 6
New 101 025 Selected Heading Deg/180 + - 180 12 0.05 125 250 6
New 121 025 Pitch Limit Deg/180 + - 180 14 0.01 125 250 6
New 145 025 Discrete Status 2 EFIS 6
New 146 025 Discrete Status 3 EFIS 6
New 147 025 Discrete Status 4 EFIS 6
New 155 025 Discrete Status 5 EFIS 6
New 160 025 Discrete Status 6 EFIS 6
New 161 025 Discrete Status 7 EFIS 6
New 162 025 ADF brg left/right Deg/180 + - 180 12 0.05 125 250 6 SDI-01 = left / SDI-10 = right
New 207 025 OP, SOFTWARE PART NO. 6 See Att. 6
New 272 025 Discrete Data #3 6
New 273 025 Discrete Data #4 6
New 276 025 Discrete Status 8 EFIS 6
New 054 037 Zero Fuel Weight (kg) kg 655360 15 20 100 200 15
New 074 037 Zero Fuel Weight (lb) lb 1310720 15 40 100 200 15
Correction 076 037 Longitudinal C/G 163.84 14
New 077 037 Lateral C/G %MAC 131.072 17 0.01 100 200 14
New 107 037 Long, Zero Fuel C/G %MAC 163.84 14 0.01 100 200
DELETE 256 037 15
DELETE 257 037 15
DELETE 347 037 15
Revise 205 038 Mach 4096 31
Revise 342 038 EPR Limit 4 12 0.001 150 250 31
Revise 342 038 N1 Limit %RPM 256 14 0.015 150 250 31
 NEW AND REVISED BNR LABEL ASSIGNMENTS
MIN MAX
LABEL EQ ID PARAMETER BINARY UNITS RANGE SIG RESOL REF NOTES
TI TI
New 227 03D AVM Command 5 See Att. 2
New 270 03D Discrete Data #1 5 See Att. 2
New 350 03D Maintenance Data #1 5 See Att. 2
New 353 03D Maintenance Data #4 5 See Att. 2
New 354 03D N1 Vibration Scalar 5.12 9 0.01 5 Bit 11-Chan. A/Bit 12-Chan. B
New 355 03D N2 Vibration Scalar 5.12 9 0.01 5 Bit 11-Chan. A/Bit 12-Chan. B
New 356 03D N3 Vibration Scalar 5.12 9 0.01 5 Bit 11-Chan. A/Bit 12-Chan. B
New 357 03D BB Vibration Scalar 5.12 9 0.01 5 Bit 11-Chan. A/Bit 12-Chan. B
New 360 03D N1 Rotor Imbalance Angle Deg. +-180 9 1 5 Bit 11-Chan. A/Bit 12-Chan. B
New 361 03D LPT Rotor Imbalance Angle (737 only) Deg. +-180 9 1 5
New 025 04D Load SEL Control na 204700 11 100 5
New 156 04D L TANK FAULTS TBD TBD 5 See Att. 2
New 157 04D R TANK FAULTS TBD TBD 5 See Att. 2
New 160 04D C TANK FAULTS TBD TBD 5 See Att. 2
New 161 04D A TANK FAULTS TBD TBD 5 See Att. 2
New 241 04D FQIS SYSTEM DATA See Att. 6 500 1024 5 See Att. 6

SUPPLEMENT 15 TO ARINC SPECIFICATION 429 - Page 5

New 254 04D Actual Fuel Quan (teat) Lbs 262144 15 8 500 1000 9
New 255 04D Fuel Quantity (gal) Gallons 32768 15 1 500 1000 46
New 256 04D FUEL DISCRETES TBD TBD 5 See Att. 2
New 262 04D T/U CAP-L TANK 1-4 PF 655.35 16 0.01 TBD TBD 5
New 263 04D T/U CAP-L TANK 5-8 PF 655.35 16 0.01 TBD TBD 5
New 264 04D T/U CAP - L TANK 9-12 PF 655.35 16 0.01 TBD TBD 5
New 265 04D T/U CAP - L TANK 13-14 PF 655.35 16 0.01 TBD TBD 5
New 266 04D T/U CAP - C TANK 1-4 PF 655.35 16 0.01 TBD TBD 5
New 267 04D T/U CAP - C TANK 5-8 PF 655.35 16 0.01 TBD TBD 5
New 270 04D T/U CAP - C TANK 9 PF 655.35 16 0.01 TBD TBD 5
New 271 04D T/U CAP - A TANK 1-4 PF 655.35 16 0.01 TBD TBD 5
New 272 04D T/U CAP - A TANK 5-8 PF 655.35 16 0.01 TBD TBD 5
New 273 04D T/U CAP -A TANK 9-11 PF 655.35 16 0.01 TBD TBD 5
New 274 04D T/U CAP - R TANK 1-4 PF 655.35 16 0.01 TBD TBD 5
New 275 04D T/U CAP - R TANK 5-8 PF 655.35 16 0.01 TBD TBD 5
New 276 04D T/U CAP - R TANK 9-12 PF 655.35 16 0.01 TBD TBD 5
New 277 04D T/U CAP - R TANK 13-14 PF 655.35 16 0.01 TBD TBD 5
New 310 04D COMP CAP-TANK PF 327.67 15 0.01 TBD TBD 5 See Att. 6 for SDI encoding
New 320 04D DENSITY-TANK LB/GAL 8.191 13 0.001 TBD TBD 5 See Att. 6 for SDI encoding
New 324 04D TANK VSO QUANTITY GALS 32767 15 1 TBD TBD 5 See Att. 6 for SDI encoding
New 326 04D UPLIFT QUANTITY LBS 1638300 14 100 TBD TBD 5
New 327 04D UPLIFT DENSITY LB/GAL 8.181 13 0.001 TBD TBD 5
New 341 04D I/O S/W REV 1&2 (1) 16 N/A TBD TBD 5
New 342 04D S/W REV-TANK (1) 16 N/A TBD TBD 5 See Att. 6 for SDI encoding
New 344 04D FUEL DISCRETES 50 100 5 See Att. 2
New 345 04D DISCRETES STATUS 1&3 100 200 5 See Att. 2
New 346 04D CABLE CAP-HI-Z PF 65535 16 1 100 200 5 See Att. 6 for SDI encoding
 NEW AND REVISED BNR LABEL ASSIGNMENTS

SUPPLEMENT 15 TO ARINC SPECIFICATION 429 - Page 6

MIN MAX
LABEL EQ ID PARAMETER BINARY UNITS RANGE SIG RESOL REF NOTES
TI TI
New 350 04D MAINT. DATA FQIS 1-3 100 200 5 See Att. 2
New 351 04D MAINT. DATA FQIS 1&3 100 200 5 See Att. 2
New 352 04D MAINT. DATA FQIS 1-4 100 200 5 See Att. 2
New 353 04D MAINT. DATA FQIS 1-4 100 200 5 See Att. 2
New 354 04D FQIS TANK ID 100 200 5 See Att. 2, Att. 6 for SDI
New 355 04D MAINT. DATA FQIS 2-4 100 200 5 See Att. 2
New 357 04D MAINT. DATA FQIS 2-3 100 200 5 See Att. 2
New 151 05A LB/KG Control Word 17 See Att. 2
Revise 176 05A Fuel Temperature - Set to Zero Deg. C 512 11 0.25 100 200 19
Revise 177 05A Fuel Temp. Left Wing Tank Deg. C 512 11 0.25 100 200 19
Delete 200 05A 19
Revise 201 05A Fuel Temp. Right Wing Tank Deg. C 512 11 0.25 100 200 19
Revise 202 05A Fuel Temperature - Set to Zero Deg. C 512 11 0.25 100 200 19
New 247 05A Total Fuel lb 655360 14 40 100 200 19
New 250 05A Preselected Fuel Quantity lb 655360 14 40 100 200 19
New 256 05A Fuel Quantity - Left Outer Cell lb 131072 15 4 100 200 19 Zero for A-321
New 257 05A Fuel Quantity Left W/T Tank lb 131072 15 4 100 200 19
New 260 05A Fuel Quantity Center Tank lb 131072 15 4 100 200 19
New 261 05A Fuel Quantity Right I/C or W/T Tank lb 131072 15 4 100 200 19
New 262 05A Fuel Quantity - Right Outer Cell lb 131072 15 4 100 200 19 Zero for A-321
New 270 05A Discrete Data #1 100 200 19
New 271 05A Discrete Data #2 100 200 19
New 276 05A Discrete Data #7 100 200 19
New 300 05A Internal Para. For SPARTIAAL 19
New 301 05A Internal Para. For SPARTIAAL 19
New 302 05A Internal Para. For SPARTIAAL 19
New 303 05A Internal Para. For SPARTIAAL 19
New 304 05A Internal Para. For SPARTIAAL 19
New 305 05A Internal Para. For SPARTIAAL 19
New 306 05A Internal Para. For SPARTIAAL 19
New 307 05A Internal Para. For SPARTIAAL 19
New 310 05A Internal Para. For SPARTIAAL 19
New 311 05A Internal Para. For SPARTIAAL 19
New 312 05A Fuel Quantity ACT 1 lb 131072 15 4 100 200 19
New 313 05A Fuel Quantity ACT 2 lb 131072 15 4 100 200 19
New 314 05A Internal Para. For SPARTIAAL 19
New 315 05A Internal Para. For SPARTIAAL 19
New 316 05A Internal Para. For SPARTIAAL 19
New 317 05A Internal Para. For SPARTIAAL 19
New 324 05A Effective Pitch Angle Deg./180 +-180 14 0.01 19
New 325 05A Effective Roll Angle Deg./180 +-180 14 0.01 19
New 356 05A Maintenance Word 19
Revise 244 08D Fuel Flow Rate 32768 31
 NEW AND REVISED BNR LABEL ASSIGNMENTS
MIN MAX
LABEL EQ ID PARAMETER BINARY UNITS RANGE SIG RESOL REF NOTES
TI TI
New 155 0BB Maintenance Data #6 44
New 156 0BB Maintenance Data #7 44
New 157 0BB Maintenance Data #8 44
New 160 0BB Maintenance Data #9 3
New 276 0BB Discrete Data #5 3
New 354 0BB Maintenance Data #5 44
New 005 0D0 Engine Discrete 5 Bit 11-Chan. A/Bit 12-Chan. B
New 006 0D0 Engine Discrete 5
New 073 0D0 Engine Oil Quantity US Pint 128 9 0.25 5 SDI1 = L/SD12 = R
New 173 0d0 Hydraulic Oil Quantity US Pint 128 9 0.25 5 SDI1 = L/SD12 = B
New 174 0D0 Hydraulic Oil Pressure PSI 4096 12 1 5 SDI1 = A/SD12 = B
New 316 0D0 Engine Oil Temperature Deg. C 2048 12 0.5 5 SDI1 = L/SD12 = R
New 317 0D0 Engine Oil Pressure PSI 4096 14 0.25 5 SDI1 = L/SD12 = R
New 344 0D0 N2 %RPM 256 13 0.03 5 SDI1 = L/SD12 = R
New 345 0D0 EGT Deg. C 2048 12 0.5 5 SDI1 = L/SD12 = R
New 346 0D0 N1 %RPM 256 13 0.03 5 SDI1 = L/SD12 = R
New 347 0D0 Fuel Flow Lb/Hr 32768 12 8 5 SDI1 = L/SD12 = R

SUPPLEMENT 15 TO ARINC SPECIFICATION 429 -Page 7

New 353 0D0 Vibration Scalar 5.12 8 0.02 5 SDI1 = L/SD12 = R
Revise 360 10A Throttle Rate of Change 16 9/9 31
New 146 112 TACAN Control See Section 3.1.4 180 220 8
New 222 112 TACAN Control Deg/180 +-180 12 0.05 180 220 8
New 101 114 C/G Target % 164 8 0.01 100 200 40
Revise 270 115 Stored TACAN Control Word 25 50 42 See Att. 2
New 221 12C Indicated Angle of Attack (Ave.) Deg/180 +-180 12 0.05 31.3 62.5 45
New 222 12C Indicated Angle of Attack (#1 left) Deg/180 +-180 12 0.05 31.3 62.5 45
New 223 12C Indicated Angle of Attack (#1 right) Deg/180 +-180 12 0.05 31.3 62.5 45
New 224 12C Indicated Angle of Attack (#2 left) Deg/180 +-180 12 0.05 31.3 62.5 45
New 225 12C Indicated Angle of Attack (#2 right) Deg/180 +-180 12 0.05 31.3 62.5 45
New 114 13A Ambient Pressure PSIA 32 14 0.002 100 200 14
New 130 13A Inlet Temperature Deg. C 128 11 0.0625 100 200 14
New 131 13A Inlet Pressure PSIA 32 13 0.004 100 200 14
New 134 13A Throttle Lever Angle Deg/180 +-180 12 0.05 25 50 14
New 254 13A N1 Cruise %N1 Nom 256 14 0.015 100 200 14
New 255 13A N1 Climb %N1 Nom 256 14 0.015 100 200 14
New 264 13A Burner Pressure PSIA 512 14 0.031 100 200 14
New 340 13A N1 Take Off %N1 Nom 256 14 0.015 25 50 14
New 341 13A N1 Reference %N1 Nom 256 14 0.015 25 50 14
New 344 13A N2 Speed %RPM 256 14 0.015 25 50 14
New 345 13A EGT Trimmed Deg. C 2048 12 0.5 25 50 14
New 346 13A N1 Speed Actual %N1 Nom 256 14 0.015 25 50 14
New 347 13A Fuel Flow Lb/Hr 32768 14 2 50 100 14
New 364 13A N1 APR Rating %N1 Nom 256 14 0.015 100 200 14
New 365 13A N1 Max Reverse %N1 Nom 256 14 0.015 100 200 14
 SUPPLEMENT 15 TO ARINC SPECIFICATION 429 - Page 8
NEW AND REVISED BNR LABEL ASSIGNMENTS

MIN MAX
LABEL EQ ID PARAMETER BINARY UNITS RANGE SIG RESOL REF NOTES
TI TI
New 366 13A IGV Position Deg./180 +-180 12 0.05 100 200 14
New 367 13A IGV Request Deg./180 +-180 12 0.05 100 200 14
New 341 160 Tank Unit Data 13
New 147 xxx TACAN Control Word 100 200 42
Correction 171 xxx Manu. Specific Status Word 16 See Att. 6
New 214 xxx ICAO Aircraft Address (part 1) See Att. 6
New 316 xxx ICAO Aircraft Address (part 2) 43
New 375 xxx GPS Differential Correction Word A See ARINC 743A
New 376 xxx GPS Differential Correction Word B See ARINC 743A
Revised 021 002 Selected EPR EPR 0-3 4 0.001 100 200 31
New 027 002 TACAN Selected Course Degrees 0-359 3 1 167 333 7
Revised 020 020 Selected Vertical Speed Ft/Min 0-6000 4 1 100 200 31
Revised 021 020 Selected EPR EPR 0-3 4 0.001 100 200 31
New 047 020 VHF Com Frequency See Chap. 3 100 200 51
New 047 024 VHF Com Frequency See Chap. 3 100 200 51
Revised 155 027 MLS Selected GP Angle Degrees 100 200 51
Revised 065 037 Gross Weight 0-19999
New 163 037 Zero Fuel Weight (lb) Lbs 0-19999 5 1 100 200 15
New 243 037 Zero Fuel Weight (kg) KG 0-19999 5 1 100 200 15
New 52 037 Long. Zero Fuel CG %MAC 0-100.00 5 0.01 100 200 15
New 012 04D QTY-LD SEL (LB) Lbs 0-79999 19 100 5
New 013 04D QTY - FLT DECK (LB) Lbs 0-79999 19 100 5
New 017 04D TOTAL-FLT DECK (LB) Lbs 0-79999 19 100 5
New 020 04D TNK-LD SEL(LB) Lbs 0-79999 19 100 5
New 022 04D QTY-LD SEL (KG) KG 0-79999 19 100 5
New 023 04D QTY-FLT DECK (KG) KG 0-79999 19 100 5
New 027 04D TOTAL-FLT DECK (KG) KG 0-79999 19 100 5
New 030 04D TNK-LD SEL(KG) KG 0-79999 19 100 5
New 135 05A ACT 1 Fuel Quan. Display KG/LB 0-9999 16 100 100 200 19
New 136 05A ACT 2 Fuel Quan. Display KG/LB 0-9999 16 100 100 200 19
New 137 05A Center+ACT+ACT FQ Display KG/LB 0-9999 16 100 100 200 19
New 140 05A Actual Fuel Quan. Display KG/LB 0-9999 16 100 100 200 19
New 141 05A Preselected Fuel Quan. Display KG/LB 0-9999 16 100 100 200 19
New 142 05A Left Wing Fuel Quan. Display KG/LB 0-9999 16 100 100 200 19
New 143 05A Center Wing Fuel Quan. Display KG/LB 0-9999 16 100 100 200 19
New 144 05A Right Wing Fuel Quan. Display LG/LB 0-9999 16 100 100 200 19
New 272 05A Fuel Density KG/M3 0-9999 16 0.0001 100 200 19
New 273 05A Sensor Values Left Wing Tank pF 0-100 13 0.1 100 200 19
New 274 05A Sensor Values Center Wing Tank pF 0-100 13 0.1 100 200 19
New 275 05A Sensor Values Right Wing Tank pF 0-100 13 0.1 100 200 19
New 047 086 VHF Com Frequency See Chap. 3 100 200 51
Revised 021 0A1 Selected EPR EPR 0-3 4 0.001 100 200 31
New 201 112 TACAN Distance N.M. 0-399.99 5 0.01 190 210 8
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401 – 7645 USA

SUPPLEMENT 16
TO

ARINC SPECIFICATION 429

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

Published: September 27, 2001

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: November 14, 2000

SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1 - Page 2

A. PURPOSE OF THIS SUPPLEMENT 167 Air Traffic Service Unit (Airbus) 25

Integrated Standby Instrument System (A340/330,
168 20
This Supplement introduces new label assignments, A320/319/321)
equipment IDs, and System Address Labels (SAL) to 169 Data Link Control and Display Unit (A340/330) 20
ARINC Specification 429. 200 Versatile Integrated Avionics Unit (B717/MD-10) 7
201 Electronic Spoiler Control Unit (B717) 7
B. ORGANIZATION OF THIS SUPPLEMENT 202 Brake Control Unit (B717) 7
The material in Supplement 16 is integrated into 203 Pneumatic Overheat Detection Unit (B717) 7
ARINC Specification 429 to form an updated version of 204 Proximity Switch Electronics Unit (B717) 7
the standard. Changes introduced by Supplement 16 are 205 APU Electronic Control Unit (B717) 7
identified using change bars and are labeled by a 206 Aircraft Interface Unit (MD-10) 7
“c-16” symbol in the margin. 207 Fuel Quantity Gauging Unit (MD-10) 7

C. CHANGES TO ARINC SPECIFICATION 429

INTRODUCED BY THIS SUPPLEMENT
This section presents a complete tabulation of the
changes and additions to the Specification introduced
by this Supplement. Each change or addition is defined
by the section number and the title currently employed
in the Specification or by the section name and title that
will be employed when the Supplement is eventually
incorporated. In each case a brief description of the
change or addition is included.
ATTACHMENT 1-1 - LABEL CODES
Attachment 1-1 was updated to include new label
assignments, of these new assignments 35 labels were
revised and 3 label assignment deletions. A summary of
label codes added by Supplement 16 is reproduced as
Attachment 1-16 to this Supplement.
The deleted labels are:
Label
PARAMETER
Code
053 Track Angle Magnetic
217 Average Static Pressure
231 Total Air Temperature
ATTACHMENT 2 - DATA STANDARDS
Attachment 2 was updated to reflect new data
standards. The basis of the changes introduced in
Supplement 16 are reproduced as Attachment 1-16 to
this Supplement.
ATTACHMENT 4 - INPUT/OUTPUT CIRCUIT
STANDARDS
Text was added to identify the drawing as defining total
system characteristics.
ATTACHMENT 6 - GENERAL WORD FORMATS
AND ENCODING EXAMPLES
The text describing Label 150 bit 11 was revised to
reflect the contents of ARINC Characteristic 743A,
GNSS Sensor.
REF
ATT The text describing Label 214 and Label 216 was
revised to reflect the contents of ARINC Characteristic
36 758, Communications Management Unit.
36

ATTACHMENT 1-2 - EQUIPMENT CODES

ATTACHMENT 8 - OUTPUT SIGNAL TIMING
Attachment 1-2 was updated to include new equipment TOLERANCES
codes:
The text was modified to define pulse rise and fall
EQ REF times.
EQUIPMENT TYPE
ID ATT
055 Multi-Mode Receiver (MMR) (755) 33
056 GNSS Navigation Landing Unit (GNLU) (756) 3
057 Cockpit Voice Recorder (CVR) (757) 24
058 Communication Management Unit Mark 2 (758) 34
060 GNSS Navigation Unit (GNU) (760) 33
061 Satellite Terminal Unit (STU) (761) 11
Flap Control Unit (B747-400)/Flap Slat Electronics Unit
0BB 23
(B767-400)
108 Electronic Engine Control (EEC) Channel A (B737-700) 10
109 Electronic Engine Control (EEC) Channel B (B737-700) 10
122 Ground Auxiliary Power Unit (A320/319/321) 20
12D Logic Drive Control Computer (B747/B767) 1
12E Cargo Control Logic Unit (B767) 1
12F Cargo Electronics Interface Unit (B767) 1
13B Audio Entertainment System (AES) Controller (Boeing) 16
13F Camera Interface Unit (A340/B777) 25
130 Load Management Unit (LMU) Airbus 21
140 Supersonic Air Data Computer (Honeywell) 17
142 ADS-B Link Display Processor Unit (LPDU) 27
143 Vertical/Horizontal Gyro (Litton) 22
 SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1 - Page 3

ATTACHMENT 11 - SYSTEM ADDRESS LABELS

The following System Address Labels were added:

SAL
REF
OCTAL SYSTEM
ATT
LABEL
157 CVR 24
210 FCMC Com A340-500/600 44
211 FCMC Mon A340-500/600 44
212 FCMC Int A340-500/600 44
225 HUD 26
241 APM-MMR 5
242 MMR 5
244 ILS 5
245 MLS 5
246 AHRS 19
251 VDR #1
252 VDR #2
253 VDR #3
310 GPWS 2
311 GNLU 1 5
312 GNLU 2 5
313 GNLU 3 5
314 GNU 1 5
315 GNU 2 5
316 GNU 3 5
321 AUTOTHROTTLE COMPUTER 9
322 FCC 1 9
323 FCC 2 18
324 FCC 3 18
325 APU 13
326 APU CONTROLLER 28
327 Mode Control Panel (MCP) 45
330 FMC 3 8
331 ATC TRANSPONDER 12
332 DADC 12
Passenger Services System (PSS) 767-
362 15
300,400
363 Cabin Service System (CSS) 747-400 15
Audio Entertainment System (AES)
364 16
Boeing
366 Multicast 43
367 Bridge 43

APPENDIX E – GUIDELINES FOR LABEL

ASSIGNMENTS

Labels 171, 172, 214 and 216 were removed from spare
labels (item 3).
 SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1– Page 4
Eqpt.
Code No. Sig MIN MAX REF
Data ID Parameter Units Range Resolution
(Octal) Bits TX TX ATT
(Hex)
001 BCD 056 Distance To Go The Same Parameters as the FMS EQ ID 002
001 BCD 060 Distance To Go The Same Parameters as the FMS EQ ID 002
002 BCD 056 Time To Go The Same Parameters as the FMS EQ ID 002
002 BCD 060 Time To Go The Same Parameters as the FMS EQ ID 002
012 BCD 056 Ground Speed The Same Parameters as the FMS EQ ID 002
012 BCD 060 Ground Speed The Same Parameters as the FMS EQ ID 002
017 BCD 055 Selected Runway Heading Degrees 0-359.9 4 0.1
020 Discrete 06D Landing Gear Position Infor & System Status 90 100 37
021 Discrete 06D Landing Gear Position Infor & System Status 90 100 37

SUPPLEMENT 16 UPDATES TO LABEL CODES

022 Discrete 06D Landing Gear Position Infor & System Status 90 100 37
023 Discrete 06D Landing Gear Position Infor & System Status 90 100 37
024 Discrete 06D Landing Gear Position Infor & System Status 90 100 37
027 BCD 056 TACAN Selected Course The Same Parameters as the FMS EQ ID 002
027 BCD 060 TACAN Selected Course (Bcd) The Same Parameters as the FMS EQ ID 002
033 BCD 055 Landing System Mode/Frequency

ATTACHMENT 1-16
033 BCD 056 ILS Frequency The Same Parameters as the FMS EQ ID 002
033 BCD 060 ILS Frequency The Same Parameters as the FMS EQ ID 002
034 BCD 056 VOR/ILS Frequency The Same Parameters as the FMS EQ ID 002
034 BCD 060 VOR/ILS Frequency #1 The Same Parameters as the FMS EQ ID 002
035 BCD 055 Paired DME Frequency MHz 1008-135.9 4 0.05
035 BCD 056 DME Frequency The Same Parameters as the FMS EQ ID 002
035 BCD 060 DME Frequency #1 The Same Parameters as the FMS EQ ID 002
036 BCD 055 MLS Channel Selection 500-600 3 1
036 BCD 056 MLS Frequency Channel The Same Parameters as the FMS EQ ID 002
036 BCD 060 MLS Frequency/Channel The Same Parameters as the FMS EQ ID 002
041 BCD 056 Set Latitude The Same Parameters as the FMS EQ ID 002
041 BCD 060 Set Latitude The Same Parameters as the FMS EQ ID 002
042 BCD 056 Set Longitude The Same Parameters as the FMS EQ ID 002
042 BCD 060 Set Longitude The Same Parameters as the FMS EQ ID 002
043 BCD 056 Set Magnetic Heading The Same Parameters as the FMS EQ ID 002
043 BCD 060 Set Magnetic Heading The Same Parameters as the FMS EQ ID 002
052 BNR 004 Body Pitch Accel Deg/Sec2 ± 64 15 0.002 50 Hz 117 Hz
052 BNR 038 Body Pitch Accel Deg/Sec2 ± 64 15 0.002 50 Hz 117 Hz
053 BCD 004 Track Angle Magnetic Degree 1 3 1 250 500
053 BNR 004 Body Roll Accel Deg/Sec2 ± 64 15 0.002 50 Hz 117 Hz
053 BNR 038 Body Roll Accel Deg/Sec2 ± 64 15 0.002 50 Hz 117 Hz
054 BNR 004 Body Yaw Accel Deg/Sec2 ± 64 15 0.002 50 Hz 117 Hz
054 BNR 038 Body Yaw Accel Deg/Sec2 ± 64 15 0.002 50 Hz 117 Hz
056 BCD 056 ETA (Active Waypoint) The Same Parameters as the FMS EQ ID 002
056 BCD 060 ETA (Active Waypoint) The Same Parameters as the FMS EQ ID 002
061 BNR 00B Pseudo Range Meters ±268435456 20 256 200 1200
061 BNR 056 ACMS Information The Same Parameters as the FMS EQ ID 002
061 BNR 060 ACMS Information The Same Parameters as the FMS EQ ID 002
062 BNR 00B Pseudo Range Fine Meters 256 11 0.125 200 1200
062 BNR 056 ACMS Information The Same Parameters as the FMS EQ ID 002
062 BNR 060 ACMS Information The Same Parameters as the FMS EQ ID 002
 Eqpt.
Code No. Sig MIN MAX REF
Data ID Parameter Units Range Resolution
(Octal) Bits TX TX ATT
(Hex)
063 BNR 00B Range Rate M/S ±4096 20 0.0039 200 1200
063 BNR 056 ACMS Information The Same Parameters as the FMS EQ ID 002
063 BNR 060 ACMS Information The Same Parameters as the FMS EQ ID 002
064 BNR 00B Delta Range Meters ±4096 20 0.0039 200 1200
065 BNR 00B SV Position X Meters ±67108864 20 64 200 1200
066 BNR 00B SV Position X Fine Meters 64 14 0.0039 200 1200
070 BNR 00B SV Position Y Meters ±67108864 20 64 200 1200
070 BNR 056 Reference Airspeed (Vref) The Same Parameters as the FMS EQ ID 002
070 BNR 060 Reference Airspeed (Vref) The Same Parameters as the FMS EQ ID 002
071 BNR 00B SV Position Y Fine Meters 64 14 0.0039 200 1200
072 BNR 00B SV Position Z Meters ±67108864 20 64 200 1200

SUPPLEMENT 16 UPDATES TO LABEL CODES

073 BNR 00B SV Position Z Fine Meters 64 14 0.0039 200 1200
074 BNR 00B UTC Measure Time Seconds 10.0 20 9.536743µs 200 1200
074 BNR 056 Zero Fuel Weight The Same Parameters as the FMS EQ ID 002
074 BNR 060 Zero Fuel Weight The Same Parameters as the FMS EQ ID 002
074 BNR 114 Zero Fuel Weight Pounds 1310680 15 40 100 400 37
075 Discrete 008 Maximum Hazard Alert Level Output

ATTACHMENT 1-16
075 BNR 114 Aircraft Gross Weight Pounds 1310680 15 40 100 200 37
076 BNR 00B GNSS Altitude (Msl) Feet ±131072 20 0.125 200 1200
076 Discrete 008 Hazard Azimuth Output
076 BNR 114 Aircraft Longitudinal Center Of Gravity Percent 163.83% 14 0.01% 100 200 37
077 Discrete 008 Hazard Range Output

SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1- Page 5

077 BNR 056 Target Airspeed The Same Parameters as the FMS EQ ID 002
077 BNR 060 Target Airspeed The Same Parameters as the FMS EQ ID 002
077 BNR 114 Zero Fuel Center Of Gravity Percent 163.83% 14 0.01% 100 200 37
100 BNR 056 Selected Course #1 The Same Parameters as the FMS EQ ID 002
100 BNR 060 Selected Course #1 The Same Parameters as the FMS EQ ID 002
101 BNR 00B HDOP N/A 1024 15 0.031 200 1200
102 BNR 00B VDOP N/A 1024 15 0.031 200 1200
102 BNR 056 Selected Altitude The Same Parameters as the FMS EQ ID 002
102 BNR 060 Selected Altitude The Same Parameters as the FMS EQ ID 002
103 BNR 00B GNSS Track Angle Degrees ±108° 15 0.0055° 200 1200
103 BNR 056 Selected Airspeed The Same Parameters as the FMS EQ ID 002
103 BNR 060 Selected Airspeed The Same Parameters as the FMS EQ ID 002
104 BNR 056 Selected Vertical Speed The Same Parameters as the FMS EQ ID 002
104 BNR 060 Selected Vertical Speed The Same Parameters as the FMS EQ ID 002
105 BNR 055 Selected Runway Heading Degrees ± 180 11 0.1
105 BNR 056 Selected Runway Heading The Same Parameters as the FMS EQ ID 002
105 BNR 060 Selected Runway Heading The Same Parameters as the FMS EQ ID 002
106 BNR 060 Selected Mach The Same Parameters as the FMS EQ ID 002
106 BNR 056 Selected Mach The Same Parameters as the FMS EQ ID 002
107 BNR 056 Selected Cruise Altitude The Same Parameters as the FMS EQ ID 002
107 BNR 060 Selected Cruise Altitude The Same Parameters as the FMS EQ ID 002
110 BNR 00B GNSS Latitude Degrees ±108° 20 0.000172° 200 1200
111 BNR 00B GNSS Longitude Degrees ±108° 20 0.000172° 200 1200
112 BNR 00B GNSS Ground Speed Knots 4096 15 0.125 200 1200
114 BNR 056 Desired Track The Same Parameters as the FMS EQ ID 002
 SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1- Page 6
Eqpt.
Code No. Sig MIN MAX REF
Data ID Parameter Units Range Resolution
(Octal) Bits TX TX ATT
(Hex)
114 BNR 060 Desired Track The Same Parameters as the FMS EQ ID 002
115 BNR 056 Waypoint Bearing The Same Parameters as the FMS EQ ID 002
115 BNR 060 Waypoint Bearing The Same Parameters as the FMS EQ ID 002
116 BNR 00B Horizontal GLS Deviation Rectilinear Feet ± 24000 18 .00915 100 32
116 BNR 055 Horizontal GLS Deviation Rectilinear Feet ± 24000 18 00915 100 32
116 BNR 056 Cross Track Distance The Same Parameters as the FMS EQ ID 002
116 BNR 060 Cross Track Distance The Same Parameters as the FMS EQ ID 002
117 BNR 00B Vertical GLS Deviation Rectilinear Feet ± 1024 14 .0625 100 32
117 BNR 055 Vertical GLS Deviation Rectilinear Feet ± 1024 14 .0625 100 32

SUPPLEMENT 16 UPDATES TO LABEL CODES

117 BNR 056 Vertical Deviation The Same Parameters as the FMS EQ ID 002
117 BNR 060 Vertical Deviation The Same Parameters as the FMS EQ ID 002
120 BNR 00B GNSS Latitude Fine Degrees 0.000172° 11 8.38-E-8° 200 1200
120 BNR 056 Range to Altitude The Same Parameters as the FMS EQ ID 002
120 BNR 060 Range To Altitude The Same Parameters as the FMS EQ ID 002
121 BNR 00B GNSS Longitude Fine Degrees 0.000172° 11 8.38-E-8° 200 1200

ATTACHMENT 1-16
121 BNR 056 Horizontal Command Signal The Same Parameters as the FMS EQ ID 002
121 BNR 060 Horizontal Command Signal The Same Parameters as the FMS EQ ID 002
122 BNR 056 Vertical Command Signal The Same Parameters as the FMS EQ ID 002
122 BNR 060 Vertical Command Signal The Same Parameters as the FMS EQ ID 002
124 Discrete 00B Digital Time Mark - 200 1200
125 BCD 00B UTC Hr:Min 23:59.9 5 0.1 Min 200 1200
125 BCD 002 Universal Coordinate Time Hr-Min 0-23.59.9 4 0.1 100 200
125 BCD 056 Universal Coordinated Time (UTC) The Same Parameters as the FMS EQ ID 002
125 BCD 060 Universal Coordinated Time (UTC) The Same Parameters as the FMS EQ ID 002
126 BNR 056 Vertical Deviation (Wide) The Same Parameters as the FMS EQ ID 002
126 BNR 060 Vertical Deviation (Wide) The Same Parameters as the FMS EQ ID 002
130 BNR 00B Aut Horiz Integ Limit NM 16 17 1.2E-4 200 1200
133 BNR 00B Aut Vert Integ Limit Feet 32, 768 18 0.125 200 1200
136 BNR 00B Vertical Figure Of Merit Feet 32, 768 18 0.125 200 1200
137 BNR 140 Flap Angle Degrees 180 12 0.05 62.5 200 36
140 BNR 00B UTC Fine Seconds 1 20 0.953674µs 200 1200
140 Discrete 114 Pump Contactor States 37
141 BNR 00B UTC Fine Fractions Seconds 0.9536743µs 10 0.9313225ns 200 1200
141 Discrete 114 Pump Contactor and Pushbutton States 37
142 Discrete 114 Pump Push Button and LP Switch State 37
143 Discrete 114 Pump LP Switch State and FCMC Commands 37
144 Discrete 114 Valve Feedback 37
145 Discrete 114 Valve Feedback 37
146 Discrete 114 Valve Feedback 37
147 Discrete 114 Valve Feedback 37
150 BNR 00B UTC Hr:Min:S ±23:59:59 17 1.0 sec 200 1200
150 BNR 056 Universal Coordinated Time The Same Parameters as the FMS EQ ID 002
150 BNR 060 Universal Coordinated Time The Same Parameters as the FMS EQ ID 002
150 Discrete 114 FCMC Valve Commands 37
151 BNR 055 MLS AZ Deviation mV ± 2400 15 0.0732
151 BNR 056 Localizer Bearing (True) The Same Parameters as the FMS EQ ID 002
 Eqpt.
Code No. Sig MIN MAX REF
Data ID Parameter Units Range Resolution
(Octal) Bits TX TX ATT
(Hex)
151 BNR 060 Localizer Bearing (True) The Same Parameters as the FMS EQ ID 002
151 Discrete 114 FCMC Valve Commands 37
152 BNR 055 MLS GP Deviation mV ± 2400 15 0.0732
Overhead Panel Switch/ Pushbutton & Refuel
152 Discrete 114 37
Panel Battery Power Supply Switch States
153 BNR 055 MLS Selected Azimuth Degrees 0-359 9 1
153 Discrete 114 Level States 37
154 BNR 055 MLS Max Selectable GP Degrees ±51.1 9 1

SUPPLEMENT 16 UPDATES TO LABEL CODES

154 BNR 056 Runway Heading (True) The Same Parameters as the FMS EQ ID 002
154 BNR 060 Runway Heading (True) The Same Parameters as the FMS EQ ID 002
Level States and Low Warning and Transfer
154 Discrete 114 37
Indications
155 BNR 055 MLS Selected Glide Path Degrees ±51.1 9 0.01
155 Discrete 114 XFR Pump Faults & Wing Imbalance Warning 37

ATTACHMENT 1-16
156 BNR 055 MLS Basic Data Wd 1 N/A N/A N/A N/A
156 Discrete 114 Refuel Panel Switch States 37
157 SAL System Address Label For CVR 24
157 BNR 055 MLS Basic Data Wd 2 N/A N/A N/A N/A
157 BCD 114 Trim Tank Probe Capacitance pf 0-400 14 0.1 37

SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1- Page 7

160 BNR 055 MLS Basic Data Wd 3 N/A N/A N/A N/A
160 Discrete 114 Valve Feedback 37
161 BNR 055 MLS Basic Data Wd 4 N/A N/A N/A N/A
161 Discrete 114 Indicated Pump Status 37
162 BNR 055 MLS Basic Data Wd 5 N/A N/A N/A N/A
162 Discrete 114 Indicated Pump Status 37
162 BNR 140 Density Altitude Feet 131072 16 2 250 500 36
163 BNR 055 MLS Basic Data Wd 6 N/A N/A N/A N/A
163 Discrete 114 Indicated Pump Status 37
164 BNR 055 MLS ABS GP Angle Degrees ± 41 15 0.00125
164 Discrete 114 Indicated Pump Status 37
165 BNR 00B Vertical Velocity Feet/Min ±32768 15 1.0 200 1200
165 BNR 055 MLS ABS Azimuth Angle Degrees ± 82 16 0.00125
165 Discrete 114 Indicated Valve Status 37
166 BNR 00B North/South Velocity Knots ±4096 15 0.125 200
166 Discrete 114 Indicated Valve Status 37
EPU Estimate Position Uncertainty/ (ANP)
167 BNR 002 NM 0-128 16 0.00195
Actual Navigation Performance
167 Discrete 114 Indicated Valve Status 37
170 Discrete 114 Wing Imbalance And FQI Failure Warning 37
171 BNR 002 RNP Reduced Navigation Performance NM 0-128 16 0.001953
171 BNR 056 Current RNP The Same Parameters as the FMS EQ ID 002
171 BNR 060 Current RNP The Same Parameters as the FMS EQ ID 002
172 Subsystem Identifier
173 BNR 055 Localizer Deviation DDM ± 0.4 12 0.0001
174 BNR 00B East/West Velocity Knots ±4096 15 0.125 200 1200
174 BNR 055 Glide Slope Deviation DDM ± 0.8 12 0.0002
 SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1-Page 8
Eqpt.
Code No. Sig MIN MAX REF
Data ID Parameter Units Range Resolution
(Octal) Bits TX TX ATT
(Hex)
176 BNR 00B GLONASS Satellite Deselection W #1 17 31
176 BNR 0AD Static Pressure Left, Uncorrected, mb mb 2048 18 0.008 20 200 36
176 BNR 038 Left Static Pressure Uncorrected, mb mb 2048 18 0.008 20 200 36
176 BNR 114 Left Outer Tank Fuel Temp & Advisory Warn Degree C ±512 11 0.025 37
177 BNR 00B GLONASS Satellite Deselection W #2 17 31
177 BNR 0AD Static Pressure Right, Uncorrected, mb mb 2048 18 0.008 20 200 36
177 BNR 038 Right Static Pressure, Uncorrected, mb mb 2048 18 0.008 20 200 36

SUPPLEMENT 16 UPDATES TO LABEL CODES

177 BNR 055 Distance To Runway Threshold Nmiles 1024 16 0.007812
177 BNR 114 Inner Tank 1 Fuel Temp & Advisory Warning Degree C ±512 11 0.025 37
200 BCD 056 Drift Angle The Same Parameters as the FMS EQ ID 002
200 BCD 060 Drift Angle The Same Parameters as the FMS EQ ID 002
200 BNR 114 Inner Tank 2 Fuel Temp & Advisory Warning Degree C ±512 11 0.025 37
201 BNR 114 Inner Tank 3 Fuel Temp & Advisory Warning Degree C ±512 11 0.025 37

ATTACHMENT 1-16
201 BNR 140 Mach Maximum Operation (Mmo) Mach 4.096 12 0.001 62.5 125 36
201 BNR 142 Projected Future Latitude Degrees ± 180 20 0.000172 150 400 27
202 BNR 114 Inner Tank 4 Fuel Temp & Advisory Warning Degree C ±512 11 0.025 37
202 BNR 140 Mach Rate M/minute 4.096 12 0.001 62.5 125 36
202 BNR 142 Projected Future Latitude Fine Degrees .000172 11 2-E-32 Cir 150 400 27
203 BNR 114 Trim Tank Fuel Temp & Advisory Warning Degree C ±512 11 0.025 37
203 BNR 140 Altitude Feet 131072 17 1 31.25 62.5 36
204 BNR 056 Baro Altitude The Same Parameters as the FMS EQ ID 002
204 BNR 060 Baro Altitude The Same Parameters as the FMS EQ ID 002
204 BNR 114 Right Outer Tank Fuel Temp & Advisory Degree C ±512 11 0.025 37
Warning
204 BNR 140 Baro Corrected Altitude Feet 131072 17 1 31.25 62.5 36
205 BNR 140 Mach Mach 4.096 16 0.0000625 62.5 125 36
206 BNR 056 Computed Airspeed The Same Parameters as the FMS EQ ID 002
206 BNR 060 Computed Airspeed The Same Parameters as the FMS EQ ID 002
206 BNR 140 Computed Airspeed (CAS) Knots 1024 14 0.0625 62.5 125 36
207 BNR 140 Airspeed Maximum Operating (VMO) Knots 1024 12 .025 62.56 125 36
210 BNR 140 True Airspeed Knots 2048 15 0.0625 62.5 125 36
210 SAL FCMC Com A340-500/600 44
211 BNR 0AD Total Air Temperature Indicated Degree C 512 12 0.125 250 500 36
211 BNR 140 Total Air Temp (TAT) Degree C 512 11 0.25 250 500 36
211 BNR 142 Projected Future Longitude Degrees ± 180 20 0.000172 150 400 27
211 SAL FCMC M on A340-500/600 44
212 BNR 056 Alititude Rate The Same Parameters as the FMS EQ ID 002
212 BNR 060 Alititude Rate The Same Parameters as the FMS EQ ID 002
212 BNR 140 Altitude Rate Ft/Min 32768 11 16 31.25 62.5 36
212 BNR 142 Projected Future Longitude Fine Degrees .000172 11 2E -32 Cir 150 400 27
212 SAL FCMC Int A340-500/600 44
213 BNR 140 Static Air Temp (SAT) Degree C 512 11 0.25 250 500 36
213 BNR 142 Vertical Time Interval Minute 265 min 10 .25 mile 500 2000 27
215 BNR OAD Impacted Pressure, Uncorrected, mb mb 512 16 0.008 20 40 36
215 BNR O38 Impacted Pressure, Uncorrected, mb mb 512 14 0.03125 62.5 125 36
215 BNR 006 Impacted Pressure, Uncorrected, mb mb 512 14 0.03125 62.5 125 36
 Eqpt.
Code No. Sig MIN MAX REF
Data ID Parameter Units Range Resolution
(Octal) Bits TX TX ATT
(Hex)
215 BNR 140 Impact Pressure Subsonic mb 512 14 0.03125 62.5 125 36
217 BNR 0AD Average Static Pressure mb 2048 18 0.008 20 200 36
217 BNR 002 Geometric Vertical Rate Ft/Min 20000 11 16
217 BNR 006 Static Pressure, Corrected (In. Hg) Inches Hg 64 16 0.001 20 200 36
217 BNR 038 Static Pressure, Average, Corrected (In. Hg) Inches Hg 64 16 0.001 20 200 36
217 BNR 140 Static Pressure Corrected (In. Hg) Inches Hg 64 16 0.001 62.5 125 36
220 056 MCDU #1 Address Label The Same Parameters as the FMS EQ ID 002
220 060 MCDU #1 Address Label The Same Parameters as the FMS EQ ID 002
220 BNR 140 Baro Corrected Altitude #2 Feet 131072 17 1 31.25 62.5 36
221 056 MCDU #2 Address Label The Same Parameters as the FMS EQ ID 002

SUPPLEMENT 16 UPDATES TO LABEL CODES

221 060 MCDU #2 Address Label The Same Parameters as the FMS EQ ID 002
221 BNR 140 Angle Of Attack Indicated Average Degrees 180 12 0.05 31.25 62.5 36
222 056 MCDU #3 Address Label The Same Parameters as the FMS EQ ID 002
222 060 MCDU #3 Address Label The Same Parameters as the FMS EQ ID 002
222 BNR 140 Angle Of Attack, Indicated #1 Left Degrees 180 12 0.05 31.5 62.5 36
223 056 Printer #1 Address Label The Same Parameters as the FMS EQ ID 002

ATTACHMENT 1-16
223 060 Printer #1 Address Label The Same Parameters as the FMS EQ ID 002
223 BNR 140 Angle Of Attack, Indicated #1 Right Degrees 180 12 0.05 31.5 62.5 36
224 056 Printer #2 Address Label The Same Parameters as the FMS EQ ID 002
224 060 Printer #2 Address Label The Same Parameters as the FMS EQ ID 002

SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1- Page 9

224 BNR 140 Angle Of Attack, Indicated #2 Left Degrees 180 12 0.05 31.5 62.5 36
225 SAL System Address Label For HUD 26
225 BNR 056 Minimum Maneuvering Air Speed The Same Parameters as the FMS EQ ID 002
225 BNR 060 Minimum Maneuvering Air Speed The Same Parameters as the FMS EQ ID 002
225 BNR 140 Angle Of Attack, Indicated #2 Right Degrees 180 12 0.05 31.5 62.5 36
226 00B Data Loader Responses 200 1200
227 Discrete 019 CFDS Bite Command Summary For HFDR
227 Discrete 053 CFDS Bite Command Word For HFDU
230 BCD 114 Left Outer Probes Capacitance pf 0-400 14 0.1 37
231 BCD 0AD Total Air Temperature Degree C 512 12 20 200 36
231 BCD 114 Inner 2 Tank Probe Capacitance pf 0-400 14 0.1 37
232 File
002 Active Intent Data Block
Format
232 DISC 055 GLS Airport ID
232 Discrete 056 Active Intent Data Block
232 060 Active Intent Data Block The Same Parameters as the FMS EQ ID 002
232 BCD 114 Inner 4 Tank Probe Capacitance pf 0-400 14 0.1 37
233 BNR 056 ACMS Information The Same Parameters as the FMS EQ ID 002
233 BNR 060 ACMS Information The Same Parameters as the FMS EQ ID 002
233 BCD 114 Right Outer Probe Capacitance pf 0-400 14 0.1 37
234 BNR 056 ACMS Information The Same Parameters as the FMS EQ ID 002
234 BNR 060 ACMS Information The Same Parameters as the FMS EQ ID 002
235 BNR 056 ACMS Information The Same Parameters as the FMS EQ ID 002
235 BNR 060 ACMS Information The Same Parameters as the FMS EQ ID 002
236 BNR 056 ACMS Information The Same Parameters as the FMS EQ ID 002
236 BNR 060 ACMS Information The Same Parameters as the FMS EQ ID 002
 SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1- Page 10
Eqpt.
Code No. Sig MIN MAX REF
Data ID Parameter Units Range Resolution
(Octal) Bits TX TX ATT
(Hex)
237 BNR 00B Horizontal Uncertainty Level Nm 16 17 0.000122 1200 29
237 BNR 002 ACMS Information
237 BNR 056 ACMS Information The Same Parameters as the FMS EQ ID 002
237 BNR 060 ACMS Information The Same Parameters as the FMS EQ ID 002
241 SAL System Address Label For APM-MMR 5
241 BNR 056 Min. Airspeed for Flap Extension The Same Parameters as the FMS EQ ID 002
241 BNR 060 Min. Airspeed for Flap Extension The Same Parameters as the FMS EQ ID 002
241 BNR 140 Angle Of Attack, Corrected Degrees 180 12 0.05 31.5 62.5 36
242 SAL System Address Label for MMR 5
242 BNR 0AD Total Pressure, Uncorrected, mb 36
File
242 002 Modified Intent Data Block

SUPPLEMENT 16 UPDATES TO LABEL CODES

Format
242 BNR 056 Modified Intent Data Block The Same Parameters as the FMS EQ ID 002
242 060 Modified Intent Data Block The Same Parameters as the FMS EQ ID 002
242 BNR 140 Total Pressure mb 2048 16 0.03125 62.5 125 36
243 DISC 055 GLS Runway Selection
244 SAL System Address Label for ILS 5

ATTACHMENT 1-16
244 BNR 140 Angle Of Attack, Normalized Ratio 2 11 0.001 62.5 125 36
245 SAL System Address Label For MLS 5
245 BNR 0AD Average Static Pressure mb, Uncorrected mb 2048 18 0.008 20 200 36
245 BNR 038 Average Static Pressure mb, Uncorrected 36
245 BNR 056 Minimum Airspeed The Same Parameters as the FMS EQ ID 002
245 BNR 060 Minimum Airspeed The Same Parameters as the FMS EQ ID 002
245 BNR 140 Static Pressure, Uncorrected mb 2048 16 0.03125 62.5 125 36
246 SAL System Address Label for AHRS 19
246 BNR 038 Average Static Pressure mb, Corrected 36
246 BNR 056 General Max Speed (Vcmax) The Same Parameters as the FMS EQ ID 002
246 BNR 060 General Max Speed (Vcmax) The Same Parameters as the FMS EQ ID 002
246 BNR 140 Static Pressure, Corrected mb 2048 16 0.03125 62.5 125 36
247 BNR 00B Horizontal Figure Of Merit NM 16 18 6.1 E-5 200 1200
247 BNR 056 Control Minimum Speed (Vcmin) The Same Parameters as the FMS EQ ID 002
247 BNR 060 Control Minimum Speed (Vcmin) The Same Parameters as the FMS EQ ID 002
247 BNR 114 Fuel On Board Pounds 655320 13 40 37
247 BNR 140 Airspeed Minimum Vmc Knots 512 11 0.25 62.5 125 36
250 BNR 0AD Indicated Side Slip Angle or AOS Deg/180 ±180 14 0.01 31.3 200 36
250 BNR 114 Preselected Fuel Quantity Pounds 655320 13 40 37
251 SAL System Address Label VDR #1
252 SAL System Address Label VDR #2
253 SAL System Address Label VDR #3
254 Discrete 055 GBAS ID 200 41
254 BNR 140 Altitude Rate Ft/Min 131072 13 16 31.25 62.5 36
255 Discrete 055 GBAS Airport ID 200 42
255 BNR 140 Impact Pressure mb 4096 17 0.03125 62.5 125 36
256 BLOCK 055 MLS Station ID #1
256 BNR 056 Time For Climb The Same Parameters as the FMS EQ ID 002
256 BNR 060 Time For Climb The Same Parameters as the FMS EQ ID 002
 Eqpt.
Code No. Sig MIN MAX REF
Data ID Parameter Units Range Resolution
(Octal) Bits TX TX ATT
(Hex)
256 BNR 114 Left Outer Tank Fuel Quantity Pounds 131068 15 4 37
256 BNR 140 Equivalent Airspeed Knots 1024 14 0.0625 62.5 125 36
257 BLOCK 055 MLS Station ID #2
257 BNR 056 Time For Descent The Same Parameters as the FMS EQ ID 002
257 BNR 060 Time For Descent The Same Parameters as the FMS EQ ID 002
257 BNR 114 Inner Tank 1 Fuel Quantity Pounds 131068 15 4 37
257 BNR 140 Total Pressure (High Range) mb 4096 17 0.03125 62.5 125 36
260 BCD 00B Date dd:Mo:Yr dd:mm:yr 6 1 day 200 1200
260 BCD 056 Date/Flight Leg The Same Parameters as the FMS EQ ID 002
260 BCD 060 Date/Flight Leg The Same Parameters as the FMS EQ ID 002
260 BNR 114 Collector Cell 1 and 2 Fuel Quantity Pounds 131068 15 4 37

SUPPLEMENT 16 UPDATES TO LABEL CODES

261 BCD 056 Flight Number (BCD) The Same Parameters as the FMS EQ ID 002
261 BCD 060 Flight Number (BCD) The Same Parameters as the FMS EQ ID 002
261 BNR 114 Fuel On Board At Engine Start Pounds 131068 15 4 37
262 BNR 056 Documentary Data The Same Parameters as the FMS EQ ID 002
262 BNR 060 Documentary Data The Same Parameters as the FMS EQ ID 002
262 BNR 114 Center Tank Fuel Quantity Pounds 131068 15 4 37

ATTACHMENT 1-16
263 BLOCK 055 Ground Station/Approach
263 BNR 056 Min. Airspeed For Flap Retraction The Same Parameters as the FMS EQ ID 002

SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1- Page 11

263 BNR 060 Min. Airspeed For Flap Retraction The Same Parameters as the FMS EQ ID 002
263 BNR 114 Collector Cell 3 And 4 Fuel Quantity Pounds 131068 15 4 37
264 BLOCK 055 Ground Station/Approach
264 BNR 056 Time To Touchdown The Same Parameters as the FMS EQ ID 002
264 BNR 060 Time To Touchdown The Same Parameters as the FMS EQ ID 002
264 BNR 114 Spare 37
265 BNR 056 Min. Buffet Airspeed The Same Parameters as the FMS EQ ID 002
265 BNR 060 Min. Buffet Airspeed The Same Parameters as the FMS EQ ID 002
265 BNR 114 Inner Tank 3 Fuel Quantity Pounds 131068 15 4 37
266 BNR 114 Inner Tank 2 Fuel Quantity Pounds 131068 15 4 37
267 BNR 056 Max. Maneuver Airspeed The Same Parameters as the FMS EQ ID 002
267 BNR 060 Max. Maneuver Airspeed The Same Parameters as the FMS EQ ID 002
267 BNR 114 Inner Tank 4 Fuel Quantity Pounds 131068 15 4 37
MU Output Data Word, Communication Link
270 Discrete 024
Status
270 Discrete 039 MCDU Normal Discrete Word
270 Discrete 041 SDU To ACARS MU/CMU Status Word
270 Discrete 050 VDR Status Word
270 Discrete 053 HFDL Status Word
270 DISC 055 MLS Discrete
270 Discrete 056 Status Discretes
270 Discrete 058 Output Status Word #1
270 DISC 060 Intent Status
270 DISC 060 Status Discretes
270 DISC 060 Discrete Data #1
270 Discrete 114 Unusable, and Empty Warning 37
270 Discrete 140 Discrete Data # 1 250 500 36
 SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1- Page 12
Eqpt.
Code No. Sig MIN MAX REF
Data ID Parameter Units Range Resolution
(Octal) Bits TX TX ATT
(Hex)
270 Discrete 142 Aircraft Category (Disc Data 1) 5000 15000 27
271 Discrete 041 SDU To ACARS MU/CMU Join /Leave
Message
271 DISC 055 MMR Discrete
271 Discrete 056 Discrete Data #2
271 DISC 060 Discrete Data #2
271 Discrete 114 Fuel Transfer Indication 37
271 Discrete 140 Discrete Data # 2 250 500 36
271 Discrete 142 Altitude Filter Limits (Disc Data 2) 500 2000 27
272 Discrete 053 HFDL Slave (Disc Data 3) 35
272 Discrete 056 Discrete Data #3
272 DISC 060 Discrete Data #3

SUPPLEMENT 16 UPDATES TO LABEL CODES

272 Discrete 114 Fuel Transfer Indication 37
272 Discrete 140 Discrete Data # 3 250 500 36
273 DIS 00B GNSS Sensor Status N/A 200 1200
273 DISC 055 GNSS Status
273 Discrete 114 Memos And Status 37
274 Discrete 114 Fuel Transfer Indications 37

ATTACHMENT 1-16
275 Discrete 038 IR Discrete Word #2
275 Discrete 056 Discrete Data #6
275 DISC 060 Discrete Data #6
275 Discrete 114 Miscellaneous Warning 37
276 Discrete 024 MU Output Data Word, Pin Program Status
SDU To EICAS/ECAM/EDU For Dual
276 Discrete 041
SATCOM
276 Discrete 050 VDR Mode Command
276 Discrete 056 Discrete Data #7
276 Discrete 058 Output Status Word #2
276 DISC 060 Discrete Data #7
276 Discrete 114 Miscellaneous Discrete 37
277 Discrete 004 IRS Maintenance Discrete
277 Discrete 114 Fuel Transfer and CG Status 37
301 056 Application Dependent The Same Parameters as the FMS EQ ID 002
301 060 Application Dependent
302 056 Application Dependent The Same Parameters as the FMS EQ ID 002
302 060 Application Dependent
303 056 Application Dependent The Same Parameters as the FMS EQ ID 002
303 060 Application Dependent
310 SAL System Address Label for GPWS 2
310 BNR 056 Present Position Latitude The Same Parameters as the FMS EQ ID 002
310 BNR 060 Present Position Latitude The Same Parameters as the FMS EQ ID 002
310 BNR 114 Right Outer Tank Fuel Quantity Pounds 131068 15 4 37
311 SAL System Address Label for GNLU 1 5
311 BNR 056 Present Position Longitude The Same Parameters as the FMS EQ ID 002
311 BNR 060 Present Position Longitude The Same Parameters as the FMS EQ ID 002
311 BNR 114 Trim Tank Fuel Quantity Pounds 131068 15 4 37
 Eqpt.
Code No. Sig MIN MAX REF
Data ID Parameter Units Range Resolution
(Octal) Bits TX TX ATT
(Hex)
312 SAL System Address Label for GNLU 2 5
312 BNR 056 Ground Speed The Same Parameters as the FMS EQ ID 002
312 BNR 060 Ground Speed The Same Parameters as the FMS EQ ID 002
312 BNR 114 Additional Center Tank (Act 1) Fuel Quantity Pounds 131068 15 4 37
313 SAL System Address Label For GNLU 3 5
313 BNR 056 Track Angle True The Same Parameters as the FMS EQ ID 002
313 BNR 060 Track Angle True The Same Parameters as the FMS EQ ID 002
313 BNR 114 Additional Center Tank (Act 2) Fuel Quantity Pounds 131068 15 4 37
314 SAL System Address Label For GNU 1 5
314 BNR 114 Rear Center Tank (RCT) Fuel Quantity Pounds 131068 15 4 37

SUPPLEMENT 16 UPDATES TO LABEL CODES

315 SAL System Address Label For GNU 2 5
315 BNR 056 Wind Speed The Same Parameters as the FMS EQ ID 002
315 BNR 060 Wind Speed The Same Parameters as the FMS EQ ID 002
316 SAL System Address Label For GNU 3 5
316 BNR 056 Wind Direction (True) The Same Parameters as the FMS EQ ID 002
316 BNR 060 Wind Direction (True) The Same Parameters as the FMS EQ ID 002

ATTACHMENT 1-16
317 BNR 056 Track Angle Magnetic The Same Parameters as the FMS EQ ID 002
317 BNR 060 Track Angle Magnetic The Same Parameters as the FMS EQ ID 002
320 BNR 05A Fuel Quantity Act 3 4

SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1- Page 13

320 BNR 056 Magnetic Heading The Same Parameters as the FMS EQ ID 002
320 BNR 060 Magnetic Heading The Same Parameters as the FMS EQ ID 002
System Address Label for Autothrottle
321 SAL 9
Computer
321 BNR 056 Drift Angle The Same Parameters as the FMS EQ ID 002
321 BNR 060 Drift Angle The Same Parameters as the FMS EQ ID 002
322 SAL System Address Label for FCC 1 9
322 BNR 056 Flight Path Angle The Same Parameters as the FMS EQ ID 002
322 BNR 060 Flight Path Angle The Same Parameters as the FMS EQ ID 002
323 SAL System Address Label For FCC 2 18
323 BNR 002 Geometric Altitude Feet 50000 17 1
323 BNR 056 Geometric Altitude The Same Parameters as the FMS EQ ID 002
323 BNR 060 Geometric Altitude The Same Parameters as the FMS EQ ID 002
324 SAL System Address Label For FCC 3 18
324 BNR 056 Estimated Position Uncertanity The Same Parameters as the FMS EQ ID 002
324 BNR 060 Estimated Position Uncertanity The Same Parameters as the FMS EQ ID 002
324 BNR 114 Effective Pitch Angle Degrees ±180 13 0.02 37
325 SAL System Address Label For APU 13
325 BNR 114 Effective Roll Angle Degrees ±180 13 0.02 37
326 SAL System Address Label For APU Controller 28
327 SAL SAL Mode Control Pane (MCP) 45
330 SAL System Address Label For FMC 3 8
331 SAL System Address Label For ATC Transponder 12
332 SAL System Address Label For DADC 12
335 BNR 002 Track Angle Rate Deg/Sec 32 11 0.015 10 20
335 BNR 056 Track Angle Rate The Same Parameters as the FMS EQ ID 002
335 BNR 060 Track Angle Rate The Same Parameters as the FMS EQ ID 002
 SUPPLEMENT 15 TO ARINC SPECIFICATION 429 PART 1- Page 14
Eqpt.
Code No. Sig MIN MAX REF
Data ID Parameter Units Range Resolution
(Octal) Bits TX TX ATT
(Hex)
340 BNR 004 Inertial Yaw Rate Deg/Sec 128 13 0.015 10 20 14
340 BNR 004 Track Angle Grid Degree ± 180 15 0.0055 20 Hz 110 Hz
340 BNR 005 Inertial Yaw Rate Deg/Sec 128 13 0.015 10 20 14
340 BNR 140 Pressure Ratio (Pt/Ps) Ratio 16 14 0.001 62.5 125 36
341 BNR 004 Grid Heading Degree ± 180 15 0.0055 20 Hz 110 Hz
341 BNR 038 Grid Heading Degree ± 180 15 0.0055 20 Hz 110 Hz
341 BNR 140 Pressure Ratio (Ps/Pso) Ratio 4 12 0.001 62.5 125 36
342 BNR 140 Air Density Ratio Ratio 4 12 0.001 250 500 36
350 Discrete 004 IRS Maintenance Discrete
350 Discrete 018 Maintenance Data #1 38

SUPPLEMENT 16 UPDATES TO LABEL CODES

350 Discrete 019 CFDS Bite Fault Summary Word For HFDR
350 Discrete 024 MU Output Data Word Failure Status
350 Discrete 038 IRS Maintenance Word #1
350 Discrete 050 VDR Fault Summary Word
350 Discrete 053 CFDS Bite Fault Summary Word For HFDU
350 DISC 055 ILS Maintenance Word

ATTACHMENT 1-16
350 Discrete 058 Maintenance Word #1
350 BCD 114 Fuel Density kg/l 0-.999 4 0.01 37
350 Discrete 140 Maintenance Data # 1 250 500 36
351 Discrete 024 MU Output Data Word, Failure Status
351 Discrete 038 IRS Maintenance Word #2
351 DISC 055 MMR Maintenance Word
351 Discrete 058 Maintenance Word #2
351 BCD 114 Inner Tank 1 Probe Capacitance pf 0-400 14 0.1 37
351 Discrete 140 Maintenance Data # 2 250 500 36
352 DISC 055 MLS Bite Status
352 Discrete 058 Maintenance Word 34
352 BCD 114 Center, ACT & RCT Probe Capacitance pf 0-400 14 0.1 37
352 Discrete 140 Maintenance Data # 3 Flight Count 524287 250 500 36
353 Discrete 038 IRS Maintenance Word #3
353 BCD 114 Inner Tank 3 Probe Capacitance pf 0-400 14 0.1 37
354 056 Maintenance Data #5 The Same Parameters as the FMS EQ ID 002
354 060 Maintenance Data #5
355 DIS 00B GNSS Fault Summary - 21 200 1200
355 Discrete 038 IRS Maintenance Word #4
357 ISO-5 056 ISO Alphabet #5 Message The Same Parameters as the FMS EQ ID 002
357 ISO-5 060 ISO Alphabet #5 Message The Same Parameters as the FMS EQ ID 002
360 BNR 056 Flight Information The Same Parameters as the FMS EQ ID 002
360 BNR 060 Flight Information The Same Parameters as the FMS EQ ID 002
360 BNR 142 RAIM Status Word NM 16 13 0.00195 39
362 SAL System Address Label For PSS 15
363 SAL System Address Label For CSS 15
364 SAL System Address Label For AES 16
366 SAL System Address Label For Multicast 43
367 SAL System Address Label For Bridge 43
370 BNR 00B GNSS Height WGS-84 (Hae) Feet ±131,072 20 0.125 1200 30
 Eqpt.
Code No. Sig MIN MAX REF
Data ID Parameter Units Range Resolution
(Octal) Bits TX TX ATT
(Hex)
370 BNR 00B GNSS Height Feet ±131,072 20 0.125 200 1200
375 BNR 004 Along Hdg Accel Gs 4 18 1.53E-5 50 Hz 110Hz
375 BNR 038 Along Hdg Accel Gs 4 18 1.53E-5 50 Hz 110Hz
376 BNR 004 Cross Hdg Accel Gs 4 18 1.53E-5 50 Hz 110Hz
376 BNR 038 Cross Hdg Accel Gs 4 18 1.53E-5 50 Hz 110Hz

SUPPLEMENT 16 UPDATES TO LABEL CODES

ATTACHMENT 1-16

SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1- Page 15

 MARK 33 DIGITAL INFORMATION
TRANSFER SYSTEM (DITS)

PART 2
DISCRETE WORD DATA STANDARDS

ARINC SPECIFICATION 429P2-15

PUBLISHED: March 6, 1996

AN DOCUMENT
0
Prepared by
AIRLINES ELECTRONIC ENGINEERING COMMITTEE
Published by
AERONAUTICAL RADIO, INC.
2551 RIVA ROAD, ANNAPOLIS, MARYLAND 21401
This document is based on material submitted by various
participants during the drafting process. Neither AEEC nor ARINC
has made any determination whether these materials could be
subject to valid claims of patent, copyright or other proprietary
rights by third parties, and no representation or warranty, express or
implied, is made in this regard. Any use of or reliance on this
document shall constitute an acceptance thereof "as is" and be
subject to this disclaimer.
 ARINC SPECIFICATION 429
TABLE OF CONTENTS

ITEM SUBJECT PAGE

1.0 INTRODUCTION 1
1.1 Purpose of ARINC Specification 429 1
1.2 Organization of ARINC Specification 429 1

2.0 DATA STANDARDS 2-138

iii
 ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 1

1.0 INTRODUCTION

1.1 Purpose of ARINC Specification 429

ARINC Specification 429 defines the air transport industry’s standards for the transfer of digital data between avionics
systems elements. Adherence to these standards is desired for all inter-systems communications in which the system
line replaceable units are defined as “unit interchangeable” in the relevant ARINC characteristics. Their use for intra-
system communications in systems in which the line replaceable units are defined in the ARINC characteristics as
“system interchangeable” is not essential, although it is desired.

1.2 Organization of ARINC Specification 429

ARINC Specification 429 was originally published in a single volume through version 14 (429-14). The size of the
document and the need for improved organization dictated the division of the document into three parts. Those three
parts include:

Part 1, “Functional Description, Electrical Interface, Label Assignments and Word Formats

Part 2 , “Discrete Word Data Formats

¢-15
Part 3, “File Data Transfer Techniques”

Part 1 provides the basic description of the functions and the supporting physical and electrical interfaces for the data
transfer system. Data word formats, standard label and address assignments, and application examples are defined.
Part 2 lists discrete word bit assignments in label order. Part 3 describes protocols and message definitions for data
transferred in large blocks and/or file format. For convenience of the user, the section and attachment numbering has
been retained for the material moved from the original Specification to Part 3.

Updates to each part of future releases of ARINC 429 will be independent of the other parts to accommodate timely
revisions as industry needs dictate. The “dash numbers” for each new Part will not be synchronized with the other
Parts as time passes. Users of ARINC Specification 429 should ensure that the latest version of each Part is used when
designing or procuring equipment.
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 2

2.0 DATA STANDARDS

Label 005 0D0 - Engine Discretes (737)

Bit No. Function 1 0

1 X
2 X
3 X
4 Label 005 0D0 X
5 X
6 X
7 X
8 X
9-10 SDI
11 PAD X
12 PAD X
13 Failure to clear serial data interrupt Fail Pass
14 ARINC received fail Fail Pass
15 PROM checksum fail Fail Pass
16 User RAM fail Fail Pass
17 NV RAM address fail Fail Pass
18 NV RAM bit fail Fail Pass
19 RTC fail Fail Pass
20 Microprocessor fail Fail Pass
21 Battery low Fail Pass
22 NV RAM corrupt Fail Pass
23 Not used
24 Not used
25 Not used
26 Interrogate activated Activated Non-Activated
27 Erase activated Activated Non-Activated
28 BIT activated Activated Non-Activated
29
30 SSM
31
32 Parity (Odd)

*Bits Installation
Number

10 9

0 0 (4)
0 1 1
1 0 2
1 1 3
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 3

DATA STANDARDS

Label 006 0D0 - Engine Options (737)

Bit No. Function 1 0

1 X
2 X
3 X
4 Label 006 0D0 X
5 X
6 X
7 X
8 X
9-10 SDI
11 X
12 X
13 X
14 X
15 X
16 X
17 X
18 PADS X
19 X
20 X
21 X
22 X
23 X
24 X
29
30 SSM
31
32 Parity (Odd)

*Bits Installation Bits Data

Number
28 27 26 25
10 9
1 1 0 0 Engine - Option - 1
0 0 (4) 1 0 1 0 Engine - Option - 2
0 1 1 0 1 1 0 Engine - Option - 3
1 0 2 0 1 1 0 Engine - Option - 3
1 1 3 0 0 0 0 Engine - Option - 4
ADDED: July 1, 1990
ARINC SPECIFICATION 429 PART 2 - Page 4
DATA STANDARDS

Label 013 0B8 - Control Word for TCAS/Mode S Transponder

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 013 0B8 X
5 X
6 X
7 X
8 X
9 SDI (MSB) 1
10 SDI (LSB)
11 Flight Level Absolute Relative
12 Altitude Select 2
13 Altitude Select
14 Spare
15 Spare
16 Spare
17 Spare
18 User
19 Defined 3
20 TCAS Display
21 Mode
22 0.5
23 1.0
24 Selected 2.0
25 TCAS 4.0
26 Range 8.0
27 (NM) 16.0
28 32.0
29 64.0
30 SSM
31 SSM
32 Parity (Odd)

Note 1: SDI Note 2: Altitude Select

BITS MEANING BITS MEANING

10 9 13 12

0 0 Both (TA/RA Bus #1 and #2) 0 0 Normal -A to +A

0 1 Left (TA/RA Bus #1) 0 1 Above -A to +B
1 0 Right (TA/RA Bus #2) 1 0 Below -B to +A
1 1 Unrestricted 1 1 Not Used

NOTE 3: The use of these user-defined bits is optional. They are generated at the control panel, passed through
the transponder without change and sent to the TCAS computer unit. If there is no control function
possible from these bits, they are set to zero.
ADDED: July 1, 1990
ARINC SPECIFICATION 429 PART 2 - Page 5

DATA STANDARDS

Label 016 0B8 - Control Word for TCAS/Mode S Transponder

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 016 0B8 X
5 X
6 X
7 X
8 X
9 SDI
10
11 Altitude Reporting OFF ON
12 SPI Ident ON Ident OFF
13 Display
14 Control 1 5
15 Sensitivity
16 Level 2
17 Control
18 D1
19 D2
20 D4 3
21 C1
22 C2 4096
23 C4 Ident
24 B1 Code
25 B2
26 B4
27 A1
28 A2
29 A4
30 SSM
31 SSM
32 Parity (Odd)

Note 1: Display Control Note 2: Manuel Sensitivity Level Control

BITS MEANING BITS MEANING

14 13 17 16 15

0 0 Primary and Traffic Advisory 0 0 0 SL=0 (AUTOMATIC)

0 1 Primary display functions only (no TCAS data) 0 0 1 SL=1 (STBY)
1 0 TCAS Traffic Advisory Only 0 1 0 SL=2 (TA ONLY)
1 1 No control function possible 0 1 1 SL=3
1 0 0 SL=4
1 0 1 SL=5
1 1 0 SL=6
1 1 1 SL=7

NOTE 3: See Attachment 5A of ARINC Characteristic 735 for Mode A reply codes.
NOTE 4: The transfer time should not exceed 200 milliseconds.
COMMENTARY
The delay from the time a command is activated at the control panel to the time of the equipment
response should be minimized.
NOTE 5: Primary display functions are those functions for which a display may have need designed when that
display is also being used in a shared manner as a Traffic Advisory Display.
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 6
DATA STANDARDS

Label 145 025 - Discrete Status 2 EFIS

Bit No. Function Bit Status

1 0

1 X
2 X
3 X
4 Label 145 025 X
5 X
6 X
7 X
8 X
9-10 SDI
11 DI-29P GROUND OPEN
12 DI-30P GROUND OPEN
13 DI-31P GROUND OPEN
14 DI-32P GROUND OPEN
15 DI-33P GROUND OPEN
16 DI-34P GROUND OPEN
17 DI-35P GROUND OPEN
18 DI-36P GROUND OPEN
19 DI-37P GROUND OPEN
20 DI-38P GROUND OPEN
21 DI-39P GROUND OPEN
22 DI-40P GROUND OPEN
23 DI-41P GROUND OPEN
24 DI-43P GROUND OPEN
25 DI-44P GROUND OPEN
26 DI-45P GROUND OPEN
27 PAD X
28 PAD X
29 PAD X
30-31 SSM
32 Parity (Odd)
 REVISED: August 1, 1980
ARINC SPECIFICATION 429 PART 2 - Page 7

DATA STANDARDS

Label 145 0A1 - FCC Control Panel Status Discrete (Triplex)

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 145 0A1 X
5 X
6 X
7 X
8 X
9-10 Unassigned
11 A/P CWS R Engaged Requested Not Requested
12 A/P CWS L Engaged Requested Not Requested
13 A/P CWS C Engaged Requested Not Requested
14 A/P CMD R Engaged Requested Not Requested
15 A/P CMD L Engaged Requested Not Requested
16 A/P CMD C Engaged Requested Not Requested
17 Land 2 (Green) Requested Not Requested
18 Land 3 (Green) Requested Not Requested
19 LOC Mode Oper. Requested Not Requested
20 Appr. Mode Req. Requested Not Requested
21 G/S Mode Oper. Requested Not Requested
22 Flare Oper. Requested Not Requested
23 Rollout Mode Oper. Requested Not Requested
24 G/A Mode Oper. Requested Not Requested
25
26
27 Not Used
28
29
30-31 SSM
32 Parity (Odd)
ADDED: MARCH 6, 1996
ARINC SPECIFICATION ARINC 429 PART 2 - Page 8

DATA STANDARDS

Label 146 025 - Discrete Status 3 EFIS

Bit No. Function Bit Status

1 0

1 X
2 X
3 X
4 Label 146 025 X
5 X
6 X
7 X
8 X
9-10 SDI
11 DI-46P GROUND OPEN
12 DI-47P GROUND OPEN
13 DI-48P GROUND OPEN
14 DI-49P GROUND OPEN
15 DI-50P GROUND OPEN
16 DI-51P GROUND OPEN
17 DI-52P GROUND OPEN
18 DI-53P GROUND OPEN
19 DI-54P GROUND OPEN
20 DI-55P GROUND OPEN
21 DI-56P GROUND OPEN
22 DI-58P GROUND OPEN
23 DI-59P GROUND OPEN
24 DI-60P GROUND OPEN
25 DI-61P GROUND OPEN
26 DI-62P GROUND OPEN
27 PAD X
28 PAD X
29 PAD X
30-31 SSM
32 Parity (Odd)
 REVISED: August 1, 1980
ARINC SPECIFICATION 429 PART 2 - Page 9

DATA STANDARDS

Label 146 0A1 - FCC Control Panel Status Discrete (Dual-Dual)

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 146 0A1 X
5 X
6 X
7 X
8 X
9-10 Unassigned
11 A/P CWS Requested Not Requested
12 A/P CMD Requested Not Requested
13 Capt. F/D Eng. Requested Not Requested
14 Land Trk Requested Not Requested
15 ATS Warn. Requested Not Requested
16 ILS Cat. 2 Available Requested Not Requested
17 Cat. 2 Autoland Avail. Requested Not Requested
18 Cat. 3 Autoland Avail. Requested Not Requested
19 LOC Excess Beam Dev. Requested Not Requested
20 F/O F/D Eng. Requested Not Requested
21 Glide Excess Beam Dev. Requested Not Requested
22 Auto G/A Not Available Requested Not Requested
23 Engine Out Compensation Not Avail. Requested Not Requested
24 Unassigned
25 Align FW Requested Not Requested
26 Land 3 FW Requested Not Requested
27 Warning Inhibit Requested Not Requested
28 Unassigned
29 A/P CMD Warning Requested Not Requested
30-31 SSM
32 Parity (Odd)
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 10

DATA STANDARDS

Label 147 025 - Discrete Status 4 EFIS

Bit No. Function Bit Status

1 0

1 X
2 X
3 X
4 Label 147 025 X
5 X
6 X
7 X
8 X
9-10 SDI
11 DI-63P GROUND OPEN
12 DI-64P GROUND OPEN
13 DI-65P GROUND OPEN
14 DI-66P GROUND OPEN
15 DI-67P GROUND OPEN
16 DI-68P GROUND OPEN
17 DI-69P GROUND OPEN
18 DI-93P GROUND OPEN
19 DI-94P GROUND OPEN
20 DI-95P GROUND OPEN
21 DI-98P GROUND OPEN
22 DI-99P GROUND OPEN
23 DI-100P GROUND OPEN
24 DI-101P GROUND OPEN
25 DI-106P GROUND OPEN
26 DI-107P GROUND OPEN
27 PAD X
28 PAD X
29 PAD X
30-31 SSM
32 Parity (Odd)
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 11

DATA STANDARDS

Label 151 05A - LB/KG Control Word

Bit No. Function Bit Status

1 0

1 X
2 X
3 X
4 Label 151 05A X
5 X
6 X
7 X
8 X
9-27 PAD Bits X
28 LBS/KGS
29 PAD X
30-31 SSM
32 P
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 12

DATA STANDARDS

Label 155 025 - Discrete Status 5 EFIS

Bit No. Function Bit Status

1 0

1 X
2 X
3 X
4 Label 155 025 X
5 X
6 X
7 X
8 X
9-10 SDI
11 DI-108P GROUND OPEN
12 DI-110P GROUND OPEN
13 DI-111P GROUND OPEN
14 DI-112P GROUND OPEN
15 DI-115P GROUND OPEN
16 DI-116P GROUND OPEN
17 DI-117P GROUND OPEN
18 DI-118P GROUND OPEN
19 DI-119P GROUND OPEN
20 DI-120P GROUND OPEN
21 DI-121P GROUND OPEN
22 DI-122P GROUND OPEN
23 DI-123P GROUND OPEN
24 DI-125P GROUND OPEN
25 DI-126P GROUND OPEN
26 DI-127P GROUND OPEN
27 PAD X
28 PAD X
29 PAD X
30-31 SSM
32 Parity (Odd)
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 17

DATA STANDARDS

Label 160 025 - Discrete Status 6 EFIS

Bit No. Function Bit Status

1 0

1 X
2 X
3 X
4 Label 160 025 X
5 X
6 X
7 X
8 X
9-10 SDI
11 DI-128P GROUND OPEN
12 DI-129P GROUND OPEN
13 DI-130P GROUND OPEN
14 DI-139P GROUND OPEN
15 DI-140P GROUND OPEN
16 DI-142P GROUND OPEN
17 DI-143P GROUND OPEN
18 DI-144P GROUND OPEN
19 RESERVED
20 RESERVED
21 RESERVED
22 RESERVED
23 RESERVED
24 RESERVED
25 RESERVED
26 RESERVED
27 PAD X
28 PAD X
29 PAD X
30-31 SSM
32 Parity (Odd)
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 19

DATA STANDARDS

Label 161 025 - Discrete Status 7 EFIS

Bit No. Function Bit Status

1 0

1 X
2 X
3 X
4 Label 161 025 X
5 X
6 X
7 X
8 X
9-10 SDI
11 RESERVED
12 RESERVED
13 RESERVED
14 RESERVED
15 RESERVED
16 RESERVED
17 RESERVED
18 RESERVED
19 RESERVED
20 RESERVED
21 RESERVED
22 RESERVED
23 RESERVED
24 RESERVED
25 RESERVED
26 RESERVED
27 PAD X
28 PAD X
29 PAD X
30-31 SSM
32 Parity (Odd)
ADDED: July 1, 1990
ARINC SPECIFICATION 429 PART 2 - Page 22

DATA STANDARDS

Label 161 10A - Full Authority Engine Control Maintenance Discretes

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 161 10A X
5 X
6 X
7 X
8 X
9 SDI
10
11
12
13
14
15 Pad
16
17
18
19
20
21
22
23
24
25 Screen 1
26 ID
27
28
29
30 SSM
31 SSM
32 Parity (Odd)

Note 1: Screen ID Codes

Value (HEX) MEANING

13 Ignition Test
14 Ignitor Test in Progress
21 FADEC Test
22 FADEC Test in Progress
ADDED: July 1, 1996
ARINC SPECIFICATION 429 PART 2 - Page 23

DATA STANDARDS

Label 161 10B - Full Authority Engine Control Maintenance Discretes

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 161 10B X
5 X
6 X
7 X
8 X
9 SDI
10
11
12
13
14
15 Pad
16
17
18
19
20
21
22
23
24
25 Screen 1
26 ID
27
28
29
30 SSM
31 SSM
32 Parity (Odd)

Note 1: Screen ID Codes

Value (HEX) MEANING

13 Ignition Test
14 Ignitor Test in Progress
21 FADEC Test
22 FADEC Test in Progress
ADDED: August 1, 1980
ARINC SPECIFICATION 429 Part 2 - Page 25

DATA STANDARDS

Label 270 001 - FCC General Discrete Word

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 270 001 X
5 X
6 X
7 X
8 X
9-10 SDI
11 Glide Capt. ID Requested Not Requested
12 LOC Capt. Cond. Requested Not Requested
13 LOC Trk Com. Requested Not Requested
14 LOC Trk Mon. Requested Not Requested
15 700 Ft. Com. Requested Not Requested
16 700 Ft. Mon. Requested Not Requested
17 Flare Cond. Com. Requested Not Requested
18 Flare Cond. Mon. Requested Not Requested
19 CWS L.D. Pitch Requested Not Requested
20 CWS L.D. Roll Requested Not Requested
21 Appr. II Own Requested Not Requested
22 Land II Own Requested Not Requested
23 Land III Own Requested Not Requested
24 FCC FW Requested Not Requested
25 AHRS I Validity Requested Not Requested
26 N1 Command Requested Not Requested
27 ARM TCC Command Requested Not Requested
28 SPD/Mach Command Requested Not Requested
29 TBD
30-31 SSM
32 Parity (Odd)
 REVISED: April 24, 1981
ARINC SPECIFICATION 429 PART 2 - Page 26

DATA STANDARDS

Label 270 004 - IRS Discrete

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 270 004 X
5 X
6 Bit 11 or 12 or X
7 13 is always set X
8 to logic (1) X
9-10 SDI
11 Align Mode/Not Ready Yes No
12 Reversionary Attitude Mode Yes No
13 Normal Mode Yes No
14 Set Heading Yes No
15 Attitude Invalid Yes No
16 DC Fail (Low) Yes No
17 ON DC Yes No
18 ADC Fault Yes No
19 IRU Fault See Note Yes No
20 DC Fail - ON DC 2 Yes No
21 Align Fault Yes No
22 No IRS Initialization Yes No
23 EXCESSIVE MOTION ERROR Yes No
24 ADC/IRU Fault Yes No
25 No VOR/DME #1 Input Yes No
26
27 Align Status
28
29 No VOR/DME #2 Input Yes No
30-31 SSM
32 Parity (Odd)
ADDED: April 24, 1981
ARINC SPECIFICATION 429 PART 2 - Page 27

DATA STANDARDS

IRS/AHRS BIT EXPLANATIONS

Bit No. Function

11 Align Mode/NR The IRU operating software mode is ALIGN or the initialization of any mode.

12 Reversionary Att. Mode The IRU operating software is ATT.

13 NAV Mode The IRU operating software mode is NAV.

14 Set Heading Magnetic heading outputs are no longer being calculated but have the
characteristics of a "free DG" and a set heading has been input to the IRU.

15 Attitude Invalid The IRU has detected a failure of attitude, heading, angular body rates, or
linear body accelerations (same as FAULT discrete).

16 DC Fail The IRU DC power input is less than 18 VDC.

17 On DC The IRU is operating on the DC power input.

18 ADC Fault ADC in-flight fault, but power-on BITE found no faults with the IRU ADC input
channel.

19 IRU Fault The BITE has detected a fault not annunciated in BITS 18, 21, 22, 23, or 24.

20 DC Fail - On DC The DC power input was not available when required by the IRU. This
condition shall be reset only by power-on initialization.

21 Align Fault Failed the IRU operating software ALIGN criterion but neither power-on nor
continuous BITE show any faults.

22 No IRS Initialization No input or an incorrect input has been received from the IRMP or FMC’s.

23 Excessive Motion Error Non-zero ground speed during the ALIGN mode.

24 ADC/IRU Fault ADC in-flight fault, but no power-on BITE information available prior to
flight.

25 No VOR/DME #1 Input

26 Align status is represented by a series of descending digits, each indicating

27 Align Status a successive state of alignment. Three bits provide a seven state alignment
28 status as follows:

LSB MSB
26 27 28

1 1 1 Alignment Commenced
0 1 1 -
- - - -
- - - -
- - - -
- - - -
1 0 0 Highest Alignment Status
0 0 0 Unassigned

29 No VOR/DME #2 Input
ADDED: April 24, 1981
ARINC SPECIFICATION 429 PART 2 - Page 28

DATA STANDARDS

Label 270 005 - AHRS Discrete

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 270 005 X
5 X
6 X
7 X
8 X
9-10 SDI
11 Align Mode/Not Ready Yes No
12 Reversionary Attitude Mode Yes No
13 Normal Mode Yes No
14 Magnetic Heading/DG Mode Yes No
15 Attitude Invalid Yes No
16 Low Battery (Not used in AHRS) Yes No
17 On Battery Yes No
18 TAS Invalid Yes No
19 AHRU Fault Yes No
20
21
22 IRS Use
23
24
25 No VOR/DME #1 Input Yes No
26
27 IRS Use
28
29 No VOR/DME #2 Input Yes No
30-31 SSM
32 Parity (Odd)

NOTES: 1) Attitude invalid is equivalent to AHRS failure.

2) Bit 13 "1" condition indicates that AHRS is in the "Normal" mode as described in Section 1.2.1 of ARINC
Characteristic 705. A "0" condition indicates that the AHRS is in the reversionary "Basic mode".

3) Bit 14 "1" condition indicates that AHRS is in the "Magnetic Heading" mode. A "0" condition indicates
the AHRS is in the reversionary "DG" mode. See Section 1.2.2 of ARINC Characteristic 705 for
description of modes of heading operation.
 REVISED: April 24, 1981
ARINC SPECIFICATION 429 PART 2 - Page 29

DATA STANDARDS

Label 270 006 - ADS Discrete

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 270 006 X
5 X
6 X
7 X
8 X
9-10 SDI
11 Icing Detector On Off
12 Pitot Probe Heat On Off
13 ADS Computer Status Fail Good
14 Pitot/Static Probe Heat On Off
15 Static Source Heat On Off
16 TAT Probe Heat On Off
17 Left Side Angle of Attack Sensor On Off
Heat
18 Right Side Angle of Attack Sensor On Off
Heat
19 VMO/MMO Overspeed Warning Warn Not Warn
20
21
22
23 Spare
24
25
26
27 Angle of Attack Alternate Yes No
Correction
28 Baro-Correction Port "A" Yes No
29 Zero Mach SSEC Yes No
30-31 SSM
32 Parity (Odd)
ARINC SPECIFICATION 429 PART 2 - Page 30

DATA STANDARDS

Label 270 00B - GPS DATA

Bit No. Function 1 0

1 X
2 X
3 X
4 Label 270 00B X
5 X
6 X
7 X
8 X
9-10 SDI
11 Spare
12 Spare
13 Vertical Maneuver Alert (flash) On Off
14 Vertical Maneuver Alert (on) Flash Off
15 Turn Point Alert (flash) On Off
16 Turn Point Alert (on) Flash Off
17 No Waypoint Entered True False
18 No Course Entered True False
19 2D/3D NAV 3D 2D
20 GPS NAV VALID True False
21 EN ROUTE True False
22 Terminal True False
23 GPS HIGH ACCURACY True false
24 APPROACH (Angular) True False
25 GPS SELF TEST (BIT) True False
26 Figure of Merit (LSB)
27 Figure of Merit (LSB)
28 Figure of Merit (LSB)
29 Figure of Merit (MSB)
30 SSM
31
32 Parity (Odd)

NOTE: Typical discrete functions are shown in the above table. Slight variations of bit usage may arise according
to the specific application.

Bits 15 16 Status

0 0 Enroute
1 0 Terminal
0 1 Approach
1 1 N/A
ADDED: January 22, 1982
ARINC SPECIFICATION 429 PART 2 - Page 31

DATA STANDARDS

Label 270 01A - EEC Discrete

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 270 01A X
5 X
6 X
7 X
8 X
9-10 SDI
11 X
12 Pad X
13 X
14 X
15 EPR Loop Selected Yes No
16 N2 Loop Selected Yes No
17 EGT Loop Selected Yes No
18 Integrator On Min Stop Yes No
19 Integrator On Max Stop Yes No
20 EEC On/Off Discrete Off No
21 Initialization Yes No
22 Low Speed Latch Yes No
23 EAROM Failed Good
24 EEC Probe T2 Selected Yes No
25 Fault Light On Off
26 See Main Panel Yes No
27 TCC System Failed Good
28 TCA System Failed Good
29 Thrust Bump Inhibit Yes No
30-31 SSM
32 Parity (Odd)
 REVISED: August 1, 1980
ARINC SPECIFICATION 429 PART 2 - Page 32

DATA STANDARDS

Label 270 023 - GPWS Discrete

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 270 023 X
5 X
6 X
7 X
8 X
9-10 SDI
11 Sink Rate
12 Pull Up
13 Terrain
14 Don’t Sink
15 Too Low Gear *
16 Too Low Flap
17 Too Low Terrain
18 Glide Slope
19 Minimum Minimum
20 Terrain Pull Up
21
22
23
24
25 Spare (All "O" States)
26
27
28
29
30-31 SSM
32 Parity (Odd)

* Only one visual message should be displayed at a time (only one data bit should be set to the logic "1" state
at a time).
 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 33

DATA STANDARDS

Label 270 02F - EEC Status

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 270 02F X
5 X
6 X
7 X
8 X
9-10 SDI X
11 PAD X
12 PAD X
13 PAD X
14 PDIU Status Invalid OK
15 Spare X
16 Channel Select Mode Secondary Auto
17 Primary Chan. Manually Selected** Selected Not Selected
18 N2 Droop Control Mode Engaged Not Engaged
19 Reverser System Status Inoperative OK
20 Channel Controlling Status Controlling Not Controlling
21 2.5 Bleed System Failed Failed Operational
22 TCA Valve(s) Failed Closed Failed OK
23 Case Cooling Valve Stuck Failed OK
24 14th Stage Bleed System Failed Failed Operational
25 Channel Incapable (Failed) Incapable Capable
26 Oil Cooling System Status Faulted Ok
27 SVA System Failed Failed Operational
28 Starter Cutout Command Cutout Not Cutout
29 Spare X
30-31 SSM X
32 Parity X

** Secondary Channel Only.

NOTE: Typical discrete functions are shown in the above table. Slight variations of bit usage may arise
according to the specific application.
ADDED: April 24, 1981
ARINC SPECIFICATION 429 PART 2 - Page 34

DATA STANDARDS

Label 270 030 - Transponder Discrete

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 270 030 X
5 X
6 X
7 X
8 X
9-10 SDI
11
12
13-14 SPARE
15-16
17
18 Left (See Note 1 Below)
19
20 Right (See Note 2 Below)
21
22
23 Up (See Note 3 Below)
24
25
26
27-28 Down (See Note 4 Below)
29
30 SSM
31
32 Parity (Odd)

Note 1: Left Component Note 2: Right Component

00 - No Left Adivisory 00 - No Right Advisory

01 - Turn Left 01 - Turn Right
10 - Don’t Turn Left 10 - Don’t Turn Right
11 - Not Used 11 - Not Used

Note 3: Up Component Note 4: Down Component

0000 - No Up Advisory 0000 - No Down Advisory

0001 - Climb 0001 - Decend
0010 - Climb Faster than 500 FPM 0010 - Decend Faster than 500 FPM
0011 - Climb Faster than 1000 FPM 0011 - Decend Faster than 1000 FPM
0100 - Climb Faster than 2000 FPM 0100 - Decend Faster than 2000 FPM
0101 - Don’t Decend 0101 - Don’t Climb
0110 - Don’t Decend Faster than 500 FPM 0110 - Don’t Climb Faster than 500 FPM
0111 - Don’t Decend Faster than 1000 FPM 0111 - Don’t Climb Faster than 1000 FPM
1000 - Don’t Decend Faster than 2000 FPM 1000 - Don’t Climb Faster than 2000 FPM
1001 - 1111 Not Used 1001 - 1111 Not Used
ADDED: January 3, 1983
ARINC SPECIFICATION 429 PART 2 - Page 35

DATA STANDARDS

Label 270 033

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 270 033 X
5 X
6 X
7 X
8 X
9-10 SDI
11 Turbine Case Cooling Valve Open Closed
12 Upper Turbine Cooling Valve Open Closed
13 Lower Turbine Cooling Valve Open Closed
14 Fuel Heater Valve Open Closed
15
16
17
18
19
20
21 Spare (all "0" states)
22
23
24
25
26
27
28
29
30-31 SSM
32 Parity (Odd)
ADDED: July 1, 1990
ARINC SPECIFICATION 429 PART 2 - Page 36

DATA STANDARDS

Label 270 035 - TCAS Vertical RA Data Discrete

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 270 035 X
5 X
6 X
7 X
8 X
9 SDI BIT 0
10 SDI BIT 1
11 100 ft/min
12 200 ft/min
13 Advisory 200 ft/min
14 Altitude 200 ft/min
15 Rate 1600 ft/min
16 3200 ft/min
17 Sign
18 Combined Control
19 Combined Control 1
20 Combined Control
21 Vertical Control
22 Vertical Control 2
23 Vertical Control
24 Up Advisory
25 Up Advisory 3
26 Up Advisory
27 Down Advisory
28 Down Advisory 4
29 Down Advisory
30 SSM
31 SSM 5
32 Parity (Odd)

Note 1: Combined Control

BITS MEANING

20 19 18

0 0 0 No Advisory
0 0 1 Clear of Conflict
0 1 0 Drop Track
0 1 1 Altitude Lost
1 0 0 Climb Corrective See Note 1A
1 0 1 Descend Corrective See Note 1A
1 1 0 Preventative
1 1 1 Not Used

NOTE 1A: CAS logic defined by RTCA DO-185 Change 6 does not discriminate between Climb Corrective and
Descend Corrective. The omission is expected to be corrected in Change 7. Meanwhile, the receiving A R
Display must assume a Climb Corrective when either a Climb Corrective or Descend Corrective is issued until the
MOPS is revised.
ADDED: July 1, 1990
ARINC SPECIFICATION 429 PART 2 - Page 37

DATA STANDARDS

Label 270 035 (cont’d) - TCAS Vertical RA Data Discrete

Note 2: Vertical Control

BITS MEANING

23 22 21

0 0 0 Advisory is not one of

the following types
0 0 1 Crossing
0 1 0 Reversal
0 1 1 Increase
1 0 0 Maintain
1 0 1 Not Used
1 1 0 Not Used
1 1 1 Not Used

Note 3: Up Advisory

BITS MEANING

26 25 24

0 0 0 No Up Advisory
0 0 1 Climb
0 1 0 Don’t Descend
0 1 1 Don’t Descend > 500
1 0 0 Don’t Descend > 1000
1 0 1 Don’t Descend > 2000
1 1 0 Not Used
1 1 1 Not Used

Note 4: Down Advisory

BITS MEANING

29 28 27

0 0 0 No Down Advisory
0 0 1 Descend
0 1 0 Don’t Climb >
0 1 1 Don’t Climb > 500
1 0 0 Don’t Climb > 1000
1 0 1 Don’t Climb > 2000
1 1 0 Not Used
1 1 1 Not Used

NOTE 5: The presence of a No Computed Data report in the SSM field indicates that the no RA exists or that
information in bits 18 through 29 is unreliable. Therefore, no RA should be issued by the Display.
 REVISED: NOVEMBER 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 38

DATA STANDARDS

Label 270 03A - Propulsion Discrete Interface Unit

Bit Status
Bit No. Function
1 0

1 X
2 X
3 x
4 Label 270 03A X
5 X
6 X
7 X
8 X
9-10 SDI
1 0
Left Engine Right Engine
0 1
10 SDI
11 PDUI Self Test Failed OK
12 P2/T2 Probe Heat Heat Off Heat On
13 Spare X
14 Idle Select Minimum Approach
15 Air/Ground Switch Ground Air
16 Opposite Engine Status Shut Down Running
17 EEC to PDUI SDD Faulted OK
18 Spare X
19 Spare X
20 Spare X
21 Spare X
22 Spare X
23 Spare X
24 Ground Test Power On Off
25 Spare X
26 Spare X
27 Spare X
28 Spare X
29 Spare X
30-31 SSM
32 Parity (Odd)

NOTE: Typical discrete functions are shown in the above table. Slight variations of bit usage may arise
according to the specific application.
ADDED: January 3, 1983
ARINC SPECIFICATION 429 PART 2 - Page 39

DATA STANDARDS

Label 270 03B

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 270 03B X
5 X
6 X
7 X
8 X
9-10 SDI
11 INS Selected Not Selected
12 VOR/LOC Selected Not Selected
13 ILS/Land Selected Not Selected
14 Land Selected Not Selected
15 Altitude Hold Selected Not Selected
16 Altitude Select Selected Not Selected
17 Mach Selected Not Selected
18 IAS Selected Not Selected
19 Vertical Speed Selected Not Selected
20 TURB Selected Not Selected
21 PMS Selected Not Selected
22 Captain’s F/D On and Select Selected Not Selected
23 F/O F/D On and Select Selected Not Selected
24 Course Transfer No. 1 Selected Not Selected
25 Course Transfer No. 2 Selected Not Selected
26 A/P Engage Manual Selected Not Selected
27 A/P Engage Command Selected Not Selected
28 Spare (all "0" states)
29 Word Validity Invalid Valid
30-31 SSM
32 Parity (Odd)
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 40

DATA STANDARDS

Label 270 03D - Status Word

Bit No. Function 1 0

1 X
2 X
3 X
4 Label 270 03D X
5 X
6 X
7 X
8 X
9-10 SDI
11-28 Data
30-31 Status Matrix
32 Parity (Odd)

Bit Parameter

**11 AVM System Fault

*11 PAD
12 AVM System Fault
*13 AVM Engine 1 Alert
**13 Broadband Alert - Engine 1
*14 AVM Engine 2 Alert
**14 Broadband Alert - Engine 2
**15 AVM Engine 1 Double Channel Fault
*15 PAD
**16 AVM Engine 2 Double Channel Fault
*16 PAD
*17 PAD
**17 AVM Engine 1 Alert
*18 PAD
**18 AVM Engine 2 Alert
**19 Engine 1 High Broadband Alert
*19 PAD
**20 Engine 2 High Broadband Alert
*20 PAD
21 NVRAM Failure
22 Fault History Erase
23 PAD
***23 Flight History Erase
24 PAD
25 PAD
26 PAD
27 PAD
28 PAD
29 PAD

* 757 Pratt and Whitney and 737 CFM-56

** 757 Rolls Royce Only
*** 737 CFM-56 Only
 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 41

DATA STANDARDS

Label 270 03F - EEC Status

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 270 03F X
5 X
6 X
7 X
8 X
9-10 SDI X
11 PAD X
12 PAD X
13 PAD X
14 PDIU Status Invalid OK
15 Spare X
16 Channel Select Mode Secondary Auto
17 Primary Chan. Manually Selected** Selected Not Selected
18 N2 Droop Control Mode Engaged Not Engaged
19 Reverser System Status Inoperative OK
20 Channel Controlling Status Controlling Not Controlling
21 2.5 Bleed System Failed Failed Operational
22 TCA Valve(s) Failed Closed Failed OK
23 Case Cooling Valve Stuck Failed OK
24 14th State Bleed System Failed Failed Operational
25 Channel Incapable (Failed) Incapable Capable
26 Oil Cooling System Status Faulted Ok
27 SVA System Failed Failed Operational
28 Starter Cutout Command Cutout Not Cutout
29 Spare X
30-31 SSM X
32 Parity X

** Secondary Channel Only.

NOTE: Typical discrete functions are shown in the above table. Slight variations of bit usage may arise
according to the specific application.
 REVISED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 42

DATA STANDARDS

Label 270 115 - Stored TACAN Control Word

Bit No. Function 1 0

1 X
2 X
3 X
4 Label 270 115 X
5 X
6 X
7 X
8 X
9 SEL TACAN 1 TACAN 2
10 MEM IN BEARING MEMORY NO BEARING MEMORY
11 MEM IN RANGE MEMORY NO RANGE MEMORY
12 TUNE AUTOTUNE NO AUTOTUNE
13-14 Pad
15-16 MLS Select 1
17 (LSB)
18 BCD Channel Code Units
19
20 (MSB)
21 (LSB)
22 HEX Channel Code Tens
23
24 (MSB)
25 TST TEST NO TEST
26 X/Y X Y
27-28 Mode Control 2
29 INT NORMAL INVERSE
30 AGC ENABLE DISABLE
31 STAT NO COMPUTED DATA VALID DATA
32 Parity (Odd)

Table 1 - TACAN/MLS Select Table 2 - Mode Control

Bits Meaning Bits Meaning

15 16 27 28

0 0 TACAN 0 0 REC
1 0 MLS W Mode 1 0 T/R
0 1 Not Used 0 1 A/A REC
1 1 MLS Z Mode 1 1 A/A T/R
ADDED: April 24, 1981
ARINC SPECIFICATION 429 PART 2 - Page 43

DATA STANDARDS

Label 271 005 - AHRS Discrete

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 271 005 X
5 X
6 X
7 X
8 X
9-10 SDI
11 MSU Fail Yes No
12 RMCU Fail Yes No
13
14
15
16
17
18
19
20 Spare
21
22
23
24
25
26
27
28
29 No VOR/DME #2 Input
30-31 SSM
32 Parity (Odd)
ADDED: April 24, 1981
ARINC SPECIFICATION 429 PART 2 - Page 44

DATA STANDARDS

Label 271 006 - ADS Discrete

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 271 006 X
5 X
6 X
7 X
8 X
9-10 SDI
11 Zero Angle of Attack SSEC Yes No
12 Angle of Attack Sensor Status Fail Good
13
14
15
16
17
18
19
20 Spare
21
22
23
24
25
26
27
28
29
30-31 SSM
32 Parity (Odd)
ADDED: July 1, 1990
ARINC SPECIFICATION 429 PART 2 - Page 45

DATA STANDARDS

Label 271 018 - TCAS Coordination Discrete (MTB,CVC,VRC,CHC,HRC,HSB,VSB)

Transponder To TCAS - Bus 1 Word 1

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 271 018 X
5 X
6 X
7 X
8 X
RF MSG BIT
9 MTB 42
10 CVC 43
11 CVC 44
12 VRC 45
13 VRC 46
14 CHC 47
15 CHC 48
16 CHC 49
17 HRC 50
18 HRC 51
19 HRC 52
20 HSB 56
21 HSB 57
22 HSB 58
23 HSB 59
24 HSB 60
25 VSB 61
26 VSB 62
27 VSB 63
28 VSB 64
29 Pad
30 SSM
31 SSM
32 Parity (Odd)

NOTE: ARINC 429 data word fields for which there are corresponding RF fields are transmitted with the MSB first
in order to maintain consistancy between RF and ARINC 429 data. Normal ARINC 429 protocol calls for the
transmission of the LSB of the field first.
ADDED: January 22, 1982
ARINC SPECIFICATION 429 PART 2 - Page 46

DATA STANDARDS

Label 271 01A - EEC Discrete

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 271 01A X
5 X
6 X
7 X
8 X
9-10 SDI
11 Model X
12 Pad X
13 0 1 2 3 X
14 X
15 Engine Model Code 1 0 1 0
16 Engine Model Code 1 1 0 0
17 X
18 Spare X
19 X
20 X
21 A/C Pack On Off
22 A/C Pack Flow Mode Hi Lo
23 Air Driven Pump Boeing On Off
24 Wing Anti-Icing 767 On Off
25 Cowl Anti-Icing Only On Off
26 Isolation Valve Open Closed
27 Approach Idle Sel. Not Sel.
28 Tt2 Probe Heat On Off
29 Spare X
30-31 SSM
32 Parity (Odd)
 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 47

DATA STANDARDS

Label 271 02F

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 271 02F X
5 X
6 X
7 X
8 X
9-10 SDI X
11 PAD X
12 PAD X
13 PAD X
14 Reverser Deploy Command On Off
15 Turbine Cooling Air Valve Solenoid On Off
16 Fuel-Oil Heat Ex. Bypass Valve Sol. On Off
17 Spare
18 Spare
19 14th Stage Bleed Command Closed Open
20 Spare X
21 Spare X
22 Spare X
23 Spare X
24 T/L Interlock Actuator Command Block Fwd Block Rev
25 Reserved (Spare Relay Command) X
26 X
27 0000 = PW2037 X
28 Engine Type Code other codes
29 Invalid X
30-31 SSM X
32 Parity (Odd) X

NOTE: Typical discrete functions are shown in the above table. Slight variations of bit usage may arise
according to the specific application.
ADDED: January 3, 1983
ARINC SPECIFICATION 429 PART 2 - Page 48

DATA STANDARDS

Label 271 033

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 271 033 X
5 X
6 X
7 X
8 X
9-10 SDI
11 High Pressure Compressor Exit Pressure Failed Good
12 Fan Inlet Total Pressure Failed Good
13 Low Pressure Compressor Exit Pressure Failed Good
14 Exhaust Gas Total Pressure Failed Good
15 Thermocouples Failed Good
16 CPU Self-Test Failed Good
17 A/D Converter Self-Test Failed Good
18 ARINC 429 Self-Test Failed Good
19 Stator Vane Angle Failed Good
20 Low Press. Comp. Bleed Valve Pos. Failed Good
21 Fuel Flow Failed Good
22 Power Supplies Failed Good
23 Tachometers Failed Good
24 Resistive Temperature Probes Failed Good
25
26
27 Spare (all "0" states)
28
29
30-31 SSM
32 Parity (Odd)
ADDED: July 1, 1990
ARINC SPECIFICATION 429 PART 2 - Page 49

DATA STANDARDS

Label 271 035 (RESERVED) - TCAS Horizontal RA Data Discrete

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 271 035 X
5 X
6 X
7 X
8 X
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32 Parity (Odd)
 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 50

DATA STANDARDS

Label 271 03A

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 271 03A X
5 X
6 X
7 X
8 X
9-10 SDI
11 ECS Pack-L ON OFF
12 ECS Pack-R ON OFF
13 ECS Pack Demand-L HI LO
14 ECS Pack Demand-R HI LO
15 PNEU Shutoff Valve-L CLOSED OPEN
16 PNEU Shutoff Valve-R CLOSED OPEN
17 Isolation Valve OPEN CLOSED
18 Spare X
19 Wing Anti-Ice-L ON OFF
20 Wing Anti-Ice-R ON OFF
21 Cowl Anti-Ice-L ON OFF
22 Cowl Anti-Ice-R ON OFF
23
24
25
26 Spare (all "0" states)
27
28
29
30-31 SSM
32 Parity (Odd)

NOTE: Typical discrete functions are shown in the above table. Slight variations of bit usage may arise
according to the specific application.
ADDED: January 3, 1983
ARINC SPECIFICATION 429 PART 2 - Page 51

DATA STANDARDS

Label 271 03B

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 271 03B X X
5 X
6 X
7 X
8 X
9-10 SDI
11 Flare Arm Armed Not Armed
12 Flare Engage Engaged Not Engaged
13 Glide Slope Capture Engaged Not Engaged
14 Go-Around Engage Engaged Not Engaged
15 Dual Engage Engaged Not Engaged
16 Triple Arm Armed Not Armed
17 Triple Engage Engaged Not Engaged
18 Rollout Engage Engaged Not Engaged
19 Nav Arm Armed Not Armed
20 Nav Capture Engaged Not Engaged
21 Pitch Wheel Enable Enabled Not Enabled
22 Turn Knob in Detent In Detent Not in Detent
23 Heading Hold A or C, and B Hold Not Hold
24 28 VDC Reference Referenced Not Referenced
25 Spare (Pad Bit) X
26 Spare (Pad Bit) X
27 Spare (Pad Bit) X
28 Yaw Damper Engage Engaged Not Engaged
29 Word Validity Invalid Valid
30-31 SSM
32 Parity (Odd)
 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 52

DATA STANDARDS

Label 271 03F

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 271 03F X
5 X
6 X
7 X
8 X
9-10 SDI X
11 PAD X
12 PAD X
13 PAD X
14 Reverser Deploy Command On Off
15 Turbine Cooling Air Valve Solenoid On Off
16 Fuel-Oil Heat Ex. Bypass Valve Sol. On Off
17 Spare
18 Spare
19 14th Stage Bleed Command Closed Open
20 Spare X
21 Spare X
22 Spare X
23 Spare X
24 T/L Interlock Actuator Command Block Fwd Block Rev
25 Reserved (Spare Relay Command) X
26 X
27 0000 = PW2037 X
28 Engine Type Code other codes
29 Invalid X
30-31 SSM X
32 Parity (Odd) X

NOTE: Typical discrete functions are shown in the above table. Slight variations of bit usage may arise
according to the specific application.
ADDED: August 1, 1980
ARINC SPECIFICATION 429 PART 2 - Page 53

DATA STANDARDS

Label 272 001 - FCC Automatic Throttle Modes Discrete Word

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 272 001 X
5 X
6 X
7 X
8 X
9 PERF Requested Not Requested
10 CLP Requested Not Requested
11 SPD Requested Not Requested
12 APR Requested Not Requested
13 LIM Requested Not Requested
14 FLP Requested Not Requested
15 SLT Requested Not Requested
16 N1 Requested Not Requested
17 EPR Requested Not Requested
18 TO Requested Not Requested
19 FLX Requested Not Requested
20 MCT Requested Not Requested
21 CLB Requested Not Requested
22 CR Requested Not Requested
23 VNAV Requested Not Requested
24 IAS Requested Not Requested
25 MACH Requested Not Requested
26 ALT Requested Not Requested
27 TRK Requested Not Requested
28 RTD Requested Not Requested
29 MIN Requested Not Requested
30-31 SSM
32 Parity
ADDED: August 1, 1980
ARINC SPECIFICATION 429 PART 2 - Page 54

DATA STANDARDS

AUTOMATIC THROTTLE MODES EXPLANATIONS

Bit No. Function

1-8 Label 272 01

9 PERF The performance submode of the VNV basic mode is in effect. Used with bit 23.
10 CLP The automatic throttles are clamped.
11 SPD The automatic throttles are engaged in the speed select control mode.
12 APR The automatic throttles are engaged in the speed select mode and throttle
control is limited by flap or slat maximum speeds, or by engine limits
(N1 or EPR), or by throttle low limit position.
13 LIM Automatic throttle control is currently limited by flap or slat maximum
speeds, or by engine limits (N1 or EPR), or by throttle low limit position.
14 FLP Used with bit 13 to designate flap limit control currently in effect.
15 SLT Used with bit 13 to designate slat limit control currently in effect.
16 N1 The automatic throttles are engaged in the N1 basic mode and controlling to
a selected N1 limit defined by bits 18 thru 22. Also used with bit 13 and
with bit 23 as the second word.
17 EPR The automatic throttles are engaged in the EPR basic mode and controlling to
a selected EPR limit defined by bits 18 thru 22. Also used with bit 13 and
with bit 23 as the second word.
18 TO The N1 or EPR take off thrust limit is currently in effect. Used with Bit 16
or 17. Also used with bit 28 for noise abatement annunication.
19 FLX The N1 or EPR maximum continuous thrust limit is currently in effect. Used
with bit 16 or 17.
20 MCT The N1 or EPR maximum continuous thrust limit is currently in effect. Used
with bit 16 or 17.
21 CLB The N1 or EPR climb thrust limit is currently in effect. Used with bit 16
or 17.
22 CR The N1 or EPR cruise thrust limit is currently in effect. Used with bit 16
or 17.
23 VNV The automatic throttles are ingaged in the vertical navigation mode and
controlling in accordance with a submode designated by bits 24 thru 27 and
bits 9, 16 and 17.
24 IAS The IAS submode of the VNV basic mode is currently in effect. Used with
bit 23.
25 MACH The Mach submode of the VNV basic mode is currently in effect. Used with
bit 23.
26 ALT The altitude hold submode the VNV basic mode is currently in effect. Used
with bit 23.
27 TRK The climb (descent) path track submode of the VNV basic mode is currently in
effect. Used with bit 23.
28 RTD The automatic throttles are engaged in the retard control mode. Also used
with bit 18 for noise or abatement annunciation.
29 MIN The automatic throttles are engaged in the speed control mode and throttle
control is limited to the minimum alpha cruise speed.
 REVISED: July 1, 1990
ARINC SPECIFICATION 429 PART 2 - Page 55

DATA STANDARDS

Label 272 002 - FMC Discretes

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 272 002 X
5 X
6 X
7 X
8 X
9 SDI BIT 0
10 SDI BIT 1
11 Enable
12 100
13 Climb 200
14 Rate 400
15 Performance 800
16 Limit 1600
17 3200
18
19
20
21
22 Pad
23
24
25
26
27
28 1500 FPM Climb Limit Cannot Climb Can Climb
29 2500 FPM Climb Limit Cannot Climb Can Climb
30-31 SSM
32 Parity (Odd)
 REVISED: August 1, 1980
ARINC SPECIFICATION 429 PART 2 - Page 56

DATA STANDARDS

Label 272 003 - TCC Discrete

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 272 003 X
5 X
6 X
7 X
8 X
9-10 SDI
11 Automatic Throttle Failure/Warning Flag Normal
12 APR* Engaged Not Engaged
13
14
15
16
17
18
19
20 Spare
21
22
23
24
25
26
27
28
29
30-31 SSM
32 Parity (Odd)

* The automatic throttles are engaged in the speed select mode and throttle control is to the minimum alpha
approach speed.
ADDED: July 1, 1990
ARINC SPECIFICATION 429 PART 2 - Page 57

DATA STANDARDS

Label 272 018 - TCAS Coordination Discrete (MID Part 1)

Transponder To TCAS - Bus 1 Word 2

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 272 018 X
5 X
6 X
7 X
8 X
9 TCAS Broadcast Bit 1
MID (Part 1) RF MSG BIT
10 MID BIT A 1 (MSB) 65
11 MID BIT A 2 66
12 MID BIT A 3 67
13 MID BIT A 4 68
14 MID BIT A 5 69
15 MID BIT A 6 70
16 MID BIT A 7 71
17 MID BIT A 8 72
18 MID BIT A 9 73
19 MID BIT A 10 74
20 MID BIT A 11 75
21 MID BIT A 12 76
22 MID BIT A 13 77
23 MID BIT A 14 78
24 MID BIT A 15 79
25 MID BIT A 16 80
26 Pad
27 Pad
28 Pad
29 Pad
30 SSM
31 SSM
32 Parity (odd)

Note 1: TCAS Broadcast Bit

BIT MEANING

0 Coordination Message
1 Received TCAS Broadcast

NOTE: ARINC 429 data word fields for which there are corresponding RF fields are transmitted with the MSB first
in order to maintain consistency between RF and ARINC 429 data. Normal ARINC 429 protocol calls for the
transmission of the LSB of the field first
ADDED: January 22, 1982
ARINC SPECIFICATION 429 PART 2 - Page 58

DATA STANDARDS

Label 272 01A - EEC Discrete

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 272 01A X
5 X
6 X
7 X
8 X
9-10 SDI
11 X
12 Pad X
13 X
14 X
15 TCC Stg 2 Sol On Off
16 TCC Stg 1 Sol On Off
17 TCC Stg 3 Sol On Off
18 TCC Stg 1 Valve Open Closed
19 Spare X
20 TCA-A-Air Valve Open Closed
21 TCA-B-Air Valve Open Closed
22 X
23 X
24 X
25 Spare X
26 X
27 X
28 X
29 X
30-31 SSM
32 Parity (Odd)
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 59

DATA STANDARDS

Label 272 025 - Discrete Data No. 1

Bit No. Function Bit Status

1 0

1 X
2 X
3 X
4 Label 272 025 X
5 X
6 X
7 X
8 X
9-10 SDI
11
12
13 DISPLAY MODE SELECTED
14 (see mode select table)
15
16
17 CP SUM CHECK NOT OK OK
18 NAV MODE SELECTED SELECTED NOT SEL
19 ADF/VOR VECTORS VECTORS NO VECT
20 DF-NAV AIDS SELECTED NOT SEL
21 DF-WAYPOINT SELECTED NOT SEL
22 DF-ROUTE DATA SELECTED NOT SEL
23 DF-AIRPORTS SELECTED NOT SEL
24 MAP ORIENT TRACK UP HDG UP
25 VOR/ILS ORIENT TRACK UP HDG UP
26 RA ALERT RESET RESET NOT RESET
27 NAV ORIENT TRACK UP HDG UP
28 FULL COMPASS ROSE FULL ROSE EXP ROSE
29 PAD X
30-31 SSM
32 Parity (Odd)

Bits Selected

1 1 1 1 1 1 Function
1 2 3 4 5 6

1 0 0 0 0 0 MAP MODE SELECTED

0 1 0 0 0 0 VOR MODE SELECTED

0 0 1 0 0 0 ILS MODE SELECTED

0 0 0 1 0 0 PLAN MODE SELECTED

0 0 0 0 1 0 VOR FULL SELECTED

0 0 0 0 0 1 ILS FULL SELECTED

0 0 0 0 0 0 NO SELECTION

(All other bit patterns

shall be considered
invalid)
 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 60

DATA STANDARDS

Label 272 02F

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 272 02F X
5 X
6 X
7 X
8 X
9-10 SDI X
11 Pad X
12 Pad X
13 Pad X
14 N1 Loop Engaged Not Engaged
15 N2 Loop Engaged Not Engaged
16 N2 Topping Loop Engaged Not Engaged
17 PB Topping Loop Engaged Not Engaged
18 PB Topping Loop Minimum Engaged Not Engaged
19 EPR Loop Engaged Not Engaged
20 Accel Schedule Loop Engaged Not Engaged
21 Decel Schedule Loop Engaged Not Engaged
22 Spare X
23 Back Up Mode Engaged Not Engaged
24 2.5 BLD 2-Position Mode Engaged Not Engaged
25 Spare X
26 Spare X
27 Spare X
28 Spare X
29 Spare X
30-31 SSM X
32 Parity (Odd)

NOTE: Typical discrete functions are shown in the above table. Slight variations of bit usage may arise
according to the specific application.
 REVISED: July 22, 1988
ARINC SPECIFICATION 429 PART 2 - Page 61

DATA STANDARDS

Label 272 03A

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 272 03A X
5 X
6 X
7 X
8 X
9-10 SDI
11 RAM In-Flight Monitor Failed OK
12 ROM In-Flight Monitor Failed OK
13 WDT In-Flight Monitor Failed OK
14 Discrete Output 1 IFM Failed OK
15 Discrete Output 1 IFM Failed OK
16 Serial Data Input - Pri Failed OK
17 Serial Data Input - Sec Failed OK
18 Spare X
19 Discrete Input IFM Failed OK
20 Power Up RAM Failed OK
21 BIT:RAM Failed OK
22 BIT:ROM Failed OK
23 BIT:Discrete Output 1 Failed OK
24 BIT:Discrete Output 2(Prov) Failed OK
25 BIT:Discrete Input Failed OK
26 BIT: Serial Data Failed OK
27 BIT:Watchdog Timer Failed OK
28 Spare
29 Spare X
30-31 SSM X
32 Parity (Odd)

NOTE: Typical discrete functions are shown in the above table. Slight variations
of bit usage may arise according to the specific application.
ADDED: January 3, 1983
ARINC SPECIFICATION 429 PART 2 - Page 62

DATA STANDARDS

Label 272 03B

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 272 03B X
5 X
6 X
7 X
8 X
9-10 SDI
11 Trim Wheel Enable Enabled Not Enabled
12 Altitude Select Capture Engaged Not Engaged
13 Flare Arm Armed Not Armed
14 Flare Engage Engaged Not Engaged
15 Glide Slope Arm Armed Not Armed
16 Glide Slope Engage Engaged Not Engaged
17 Go-Around Engage Engaged Not Engaged
18 Heading Select Selected Not Selected
19 Nav Engage Engaged Not Engaged
20 Localizer Capture Engaged Not Engaged
21
22
23
24 Spare (all "0" states)
25
26
27
28
29 Word Validity Invalid Valid
30-31 SSM
32 Parity (Odd)
 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 63

DATA STANDARDS

Label 272 03F

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 272 03F X
5 X
6 X
7 X
8 X
9-10 SDI X
11 Pad X
12 Pad X
13 Pad X
14 N1 Loop Engaged Not Engaged
15 N2 Loop Engaged Not Engaged
16 N2 Topping Loop Engaged Not Engaged
17 PB Topping Loop Engaged Not Engaged
18 PB Topping Loop Minimum Engaged Not Engaged
19 EPR Loop Engaged Not Engaged
20 Accel Schedule Loop Engaged Not Engaged
21 Decel Schedule Loop Engaged Not Engaged
22 Spare X
23 Back Up Mode Engaged Not Engaged
24 2.5 BLD 2-Position Mode Engaged Not Engaged
25 Spare X
26 Spare X
27 Spare X
28 Spare X
29 Spare X
30-31 SSM X
32 Parity (Odd)

NOTE: Typical discrete functions are shown in the above table. Slight variations of bit usage may arise
according to the specific application.
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 64

DATA STANDARDS

Label 272 05A - (A-320) FQS - Fuel Density

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 272 05A (Fuel Density) X
5 X
6 X
7 X
8 X
9 SDI
10
11
12 0.1 pf
13-14
15-16
17 1 pf
18
19
20 10 pf
21
22
23 100 pf
24
25 probe number
26 (units)
27
28 probe number
29 (units)
30-31 SSM
32 Parity

NOTE: Typical discrete functions are shown in the above table. Slight variations of bit usage may arise according
to the specific application.
ADDED: August 1, 1980
ARINC SPECIFICATION 429 PART 2 - Page 65

DATA STANDARDS

Label 273 001 - FCC Arm Modes Discrete Word

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 273 001 X
5 X
6 X
7 X
8 X
9 Unassigned
10 Unassigned
11 Test Requested Not Requested
12 ALT Armed Not Armed
13 FMC Armed Not Armed
14 LNAV Armed Not Armed
15 VNAV Armed Not Armed
16 LOC Engaged Not Engaged
17 Back Course Engaged Not Engaged
18 Appr. 2 Engaged Not Engaged
19 Land 2 Engaged Not Engaged
20 Land 1 Armed Not Armed
21 Land 3 Armed Not Armed
22 Glideslope Armed Not Armed
23 VOR Armed Not Armed
24 Climb Armed Not Armed
25 Descent Armed Not Armed
26
27 Unassigned
28
29
30-31 SSM
32 Parity (Odd)
ADDED: August 1, 1980
ARINC SPECIFICATION 429 PART 2 - Page 66

DATA STANDARDS

ARM MODES EXPLANATIONS

Bit No. Function

1-8 Label 273 001

9
10
11 TEST A test of interfacing systems has been requested.
12 ALT The latitude preselect mode has been armed.
13 FMC The lateral and vertical navigation modes of the flight management system
have been armed.
14 LNAV The lateral navigation submode of the FMS is armed.
15 VNAV The vertical navigation submode of the FMS is armed.
16 LOC The localizer mode has been armed.
17 BACK COURSE The localizer back course mode has been armed.
18 APPR The approach mode has been armed.
19 LAND 2 The autoland mode is armed on FCC No. 2.
20 LAND 1 The autoland mode is armed on FCC No. 1.
21 LAND 3 The autoland mode is armed on FCC No. 3.
22 GLIDE SLOPE The glideslope mode has been armed.
23 VOR The VOR mode has been armed.
24 CLIMB The climb submode of the VNV basic mode is armed.
25 DESCENT The Descent submode of the VNV basic mode is armed.
26-29 TBD
ADDED: August 1, 1980
ARINC SPECIFICATION 429 PART 2 - Page 67

DATA STANDARDS

Label 273 003 - TCC Discrete

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 273 003 X
5 X
6 X
7 X
8 X
9-10 SDI
11 No bleed air Requested Not Requested
12 One air conditioning pack Requested Not Requested
13 Two air conditioning packs Requested Not Requested
14 Three air conditioning packs Requested Not Requested
15 Half wing anti-icing Requested Not Requested
16 Total wing anti-icing Requested Not Requested
17 Engine cowling anti-icing Requested Not Requested
18 Engine operting condition (Engine Out) Requested Not Requested
19 Speed brake Position - retract Requested Not Requested
20 Speed brake Position - 1/3 Requested Not Requested
21 Speed brake Position - 2/3 Requested Not Requested
22 Speed brake Position - full Requested Not Requested
23 Landing gear position Requested Not Requested
24 Slat position - retract Requested Not Requested
25 Slat position - take off Requested Not Requested
26 Slat position - land Requested Not Requested
27 Electronic Engine Control On-Off No. 1 On Off
28 Electronic Engine Control On-Off No. 2 On Off
29 Electronic Engine Control On-Off No. 3 On Off
30-31 SSM
32 Parity (Odd)
ADDED: July 1, 1990
ARINC SPECIFICATION 429 PART 2 - Page 68

DATA STANDARDS

Label 273 018 - TCAS Mode S Ground Uplink (SLC, IIS) Word

Transponder To TCAS - Bus 1 Word 3

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 273 018 X
5 X
6 X
7 X
8 X
9
10
11
12
13
14
15 Pad
16
17
18
19
20
21
RF MSG BIT
22 (MSB) 41
23 SLC 1 2 3 42
24 43
25 (LSB) 44
26 17
27 IIS 18
28 2 19
29 20
30 SSM
31 SSM
32 Parity (odd)

Note 1: Sensitivity Level Command (SLC) NOTE 2: This data is received from the ground station in data
words UF 20 & UF 21.
BITS MEANING
NOTE 3: ARINC 429 data word fields for which there are
22 23 24 25 corresponding RF fields are transmitted with the MSB
first in order to maintain consistency between RF and
0 0 0 0 SLC 0 ARINC 429 data. The normal ARINC 429 protocol calls for
0 0 0 1 SLC 1 the transmission of the LSB of the field first.
0 0 1 0 SLC 2
0 0 1 1 SLC 3
0 1 0 0 SLC 4
0 1 0 1 SLC 5
0 1 1 0 SLC 6
0 1 1 1 SLC 7
1 0 0 0
to Not Assigned

1 1 1 0
1 1 1 1 Cancel previous level
command
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 69

DATA STANDARDS

Label 273 025 - Discrete Data No. 2

Bit No. Function Bit Status

1 0

1 X
2 X
3 X
4 Label 273 025 X
5 X
6 X
7 X
8 X
9-10 SDI
11
12
13
14
15 PITCH REF
16
17
18
19
20 FLIGHT PATH DATA ON OFF
21 PAD X
22 FPA DISABLE OFF ON
23 WEATHER RADAR DATA SELECT SEL NOT SEL
24 RANGE SELECTED
25
26
27 (see range table)
28
29
30-31 SSM
32 Parity (Odd)

Bits Range

2 2 2 2 2 2 Selected
4 5 6 7 8 9

1 0 0 0 0 0 5 MILES (not used)

0 1 0 0 0 0 10 MILES

0 0 1 0 0 0 20 MILES

0 0 0 1 0 0 40 MILES

0 0 0 0 1 0 80 MILES

0 0 0 0 0 1 160 MILES

0 0 0 0 0 0 320 MILES

(All other bit patterns

are considered invalid)
 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 70

DATA STANDARDS

Label 273 02F

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 273 02F X
5 X
6 X
7 X
8 X
9-10 SDI X
11 X
12 Pad X
13 X
14 P4.9 Interface Failed OK
15 PB Interface Failed OK
16 P2 (Pamb) Interface* Failed OK
17 CJC Interface Failed OK
18 T2 Interface Failed OK
19 T4.9 Interface Failed OK
20 Tfuel/Toil Interface Failed OK
21 A/D Interface Failed OK
22 RES/LVDT Interface Failed OK
23 SVA Interface Failed OK
24 N1 Interface Failed OK
25 N2 Interface Failed OK
26 P4.9 Sensor PROM Failed OK
27 P2 (Pamb) Sensor PROM* Failed OK
28 PB Sensor PROM Failed OK
29 Background Execution Not Executing Executing
30-31 SSM X
32 Parity (Odd)
* Primary channel uses P2; Secondary channel uses Pamb

NOTE: Typical discrete functions are shown in the above table. Slight variations of bit usage may arise
according to the specific application.
ADDED: July 1, 1990
ARINC SPECIFICATION 429 PART 2 - Page 71

DATA STANDARDS

Label 273 035 - TCAS Output Discrete (ARA, RAC)

TCAS To Transponder And Displays - Bus 2 Word 1

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 273 035 X
5 X
6 X
7 X
8 X
9
10 Pad
11
RF MSG BIT
12 41
13 42
14 43
15 44
16 45
17 ARA 1 46
18 47
19 48
20 49
21 50
22 51
23 52
24 53
25 54
26 55
27 RAC 1 56
28 57
29 58
30 SSM
31 SSM
32 Parity (Odd)

NOTE 1: Sent by own transponder in DF 16, 20 and 21.

ADDED: January 3, 1983
ARINC SPECIFICATION 429 PART 2 - Page 72

DATA STANDARDS

Label 273 03B

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 273 03B X
5 X
6 X
7 X
8 X
9-10 SDI
11 A/P Red Warning Lights Warn Normal
12 A/P Servo System Pitch/Roll Failed Normal
13 A/P Servo System Yaw Failed Normal
14 A/P Camout Pitch Camout Normal
15 A/P Camout Roll Camout Normal
16 A/P Camout Yaw Camout Normal
17 A/P Confidence Test Failed Passed
18 Spare (Pad Bit) X
19 Spare (Pad Bit) X
20 A/T Red Warning Lights Warn Normal
21 A/T Speed Flag Flag Normal
22
23
24 Spare (all "0" states)
25
26
27
28
29 Word Validity Invalid Valid
30-31 SSM
32 Parity (Odd)
 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 73

DATA STANDARDS

Label 273 03F

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 273 03F X
5 X
6 X
7 X
8 X
9-10 SDI X
11 X
12 Pad X
13 X
14 P4.9 Interface Failed OK
15 PB Interface Failed OK
16 P2 (Pamb) Interface* Failed OK
17 CJC Interface Failed OK
18 T2 Interface Failed OK
19 T4.9 Interface Failed OK
20 Tfuel/Toil Interface Failed OK
21 A/D Interface Failed OK
22 RES/LVDT Interface Failed OK
23 SVA Interface Failed OK
24 N1 Interface Failed OK
25 N2 Interface Failed OK
26 P4.9 Sensor PROM Failed OK
27 P2 (Pamb) Sensor PROM* Failed OK
28 PB Sensor PROM Failed OK
29 Background Execution Not Executing Executing
30-31 SSM X
32 Parity (Odd)
* Primary channel uses P2; Secondary channel uses Pamb

NOTE: Typical discrete functions are shown in the above table. Slight variations of bit usage may arise
according to the specific application.
 REVISED: July 22, 1988
ARINC SPECIFICATION 429 PART 2 - Page 74

DATA STANDARDS

Label 273 05A - (A-320) FQS - Right Wing

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 273 05A (Right Wing) X
5 X
6 X
7 X
8 X
9 SDI
10
11
12 0.1 pf
13-14
15-16
17 1 pf
18
19
20 10 pf
21
22
23 100 pf
24
25 probe number
26 (units)
27
28 probe number
29 (units)
30-31 SSM
32 Parity

NOTE: Typical discrete functions are shown in the above table. Slight variations of bit usage may arise according
to the specific application.
ADDED: August 1, 1980
ARINC SPECIFICATION 429 PART 2 - Page 75

DATA STANDARDS

Label 274 001 - FCC Pitch Modes Discrete Word

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 274 001 X
5 X
6 X
7 X
8 X
9 Descent Requested Not Requested
10 Climb Requested Not Requested
11 IAS Requested Not Requested
12 VNAV Requested Not Requested
13 ALT Requested Not Requested
14 V/S Requested Not Requested
15 Flare Requested Not Requested
16 Pitch G/A Requested Not Requested
17 Pitch T/O Requested Not Requested
18 Mach Requested Not Requested
19 Glideslope Requested Not Requested
20 Flap Speed Requested Not Requested
21 Min Speed Requested Not Requested
22 Track Requested Not Requested
23 Pitch Limit Requested Not Requested
24 Turb. Requested Not Requested
25 CWS Requested Not Requested
26 Hold Requested Not Requested
27 Performance Requested Not Requested
28 Pitch Requested Not Requested
29 Capture Requested Not Requested
30-31 SSM
32 Parity
ADDED: August 1, 1980
ARINC SPECIFICATION 429 PART 2 - Page 76

DATA STANDARDS

PITCH MODES EXPLANATIONS

Bit No. Function

11 IAS The "Airspeed" reference mode is selected.

12 VNAV The pitch axis "Vertical Navigation" mode is selected.
13 ALT The "Altitude" reference mode is selected.
14 V/S The "Vertical Speed" reference mode is selected.
15 FLARE The "Flare" phase of the autoland mode is engaged.
16 PITCH G/A The Pitch Axis "Go Around" mode is engaged.
17 PITCH T/O The Pitch Axis is engaged in the "Take Off" mode.
18 MACH The "Mach" reference speed mode is selected.
19 GLIDE SLOPE The "Glideslope" guidance mode is selected.
20 FLAP SPEED The aircraft is being controlled to a speed which is limited by the flap
setting.
21 MIN SPEED The aircraft is being controlled to the minimum speed for its configuration.
22 TRACK The "Track" phase of the selected mode is engaged.
23 PITCH LIMIT The aircraft pitch attitude is veing controlled to the maximum value.
24 TURB The pitch axis "Turbulence" penetration mode is engaged.
25 CWS The pitch axis is engaged in the "CWS" mode.
26 HOLD The aircraft is holding a preselected value of altitude, attitude or speed.
27 PERFORMANCE The "Performance" submode of the Flight Management Vertical Navigation mode
is engaged.
28 PITCH The Pitch Attitude Mode is selected.
29 CAPTURE The "Capture" phase of the selected mode is engaged.
ADDED: August 1, 1980
ARINC SPECIFICATION 429 PART 2 - Page 77

DATA STANDARDS

Label 274 003 - TCC Discrete

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 274 003 X
5 X
6 X
7 X
8 X
9 DFA Mode Armed Armed Not Armed
10 DFA Mode Engaged Engaged Not Engaged
11 ATS OFF OFF Passive
12 ATS Armed Armed Passive
13 ATS Mode Engaged Engaged Passive
14 Left Clutch Off Off Passive
15 Right Clutch Off Off Passive
16 Both Clutches Off Off Passive
17 VNV The automatic throttles are engaged in the vertical Engaged Not Engaged
navigation mode and controlling in accordance with a
submode designated by bits 23 thru 26 and 29.
18 ATS N1/EPR Mode Engaged Engaged Not Engaged
19 EPR Engaged Not Engaged
20 ATS Mach Mode Engaged Engaged Not Engaged
21 ATS Speed Mode Engaged Engaged Not Engaged
22 ATS Retard Activated Engaged Not Engaged
23 IAS The IAS submode of VNV basic mode currently in effect. In Effect Not In Effect
Used with bit 17.
24 MACH The Mach submode of VNV basic mode currently in In Effect Not In Effect
effect. Used with bit 17.
25 ALT The altitude hold submode of VNV basic mode is In Effect Not In Effect
currently in effect. Used with bit 17.
26 TRK The climb (descent) path-track submode of the VNV In Effect Not In Effect
basic mode is currently in effect. Used with bit 17.
27 ATS Alpha Mode Activated Activated Not Activated
28 ATS Throttle Pusher Activated (Alpha Floor Protection) Activated Not Activated
29 PERF The Performance submode of the VNV basic mode is in In Effect Not In Effect
effect. Used with bit 17.
30-31 SSM
32 Parity
ADDED: July 1, 1990
ARINC SPECIFICATION 429 PART 2 - Page 78

DATA STANDARDS

Label 274 018 - TCAS Coordination Discrete (MID Part 2)

Transponder To TCAS - Bus 1 Word 8

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 274 018 X
5 X
6 X X
7 X
8
MID (Part 2) RF MSG BIT
9 MID BIT A17 81
10 MID BIT A18 82
11 MID BIT A19 83
12 MID BIT A20 84
13 MID BIT A21 85
14 MID BIT A22 86
15 MID BIT A23 87
16 MID BIT A24 (LSB) 88
17 Pad
18 Pad
19 Pad
20 Pad
21 Pad
22 Pad
23 Pad
24 Pad
25 Pad
26 Pad
27 Pad
28 Pad
29 Pad
30 SSM
31 SSM
32 Parity (odd)

NOTE: ARINC 429 data word fields for which there are corresponding RF fields are transmitted with the MSB first
in order to maintain consistency between RF and ARINC 429 data. Normal ARINC 429 protocol calls for the
transmission of the LSB of the field first.
 REVISED: November 11, 1986
ARINC SPECIFICATION 429 PART 2 - Page 79

DATA STANDARDS

Label 274 02F

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 274 02F X
5 X
6 X
7 X
8 X
9 SDI X
10 SDI X
11 X
12 PAD X
13 X
14 Parity Test Hardware Error OK
15 ROM Checksum Failed OK
16 RAM Test Failed OK
17 Instruction Test Failed OK
18 High Speed Cross Link Text Failed OK
19 Foreground Software Execution Incorrect Correct
20 Watchdog Timer Error OK
21 Spare X
22 EAROM Failed OK
23 ROM Parity Error Caused Reset Yes No
24 RAM Parity Error Caused Reset Yes No
25 Watchdog Timer Error Caused Reset Yes No
26 Status Buffer Failed OK
27 Loss of Clock Caused Reset Yes No
28 SDD Output #1 W/A Failed OK
29 SDD Output #2 W/A Failed OK
30 SSM X
31 SSM X
32 Parity (Odd)

NOTE: Typical discrete functions are shown in the above table. Slight variations of bit usage may arise according to
the specific application.
ADDED: July 1, 1990
ARINC SPECIFICATION 429 PART 2 - Page 80

DATA STANDARDS

Label 274 035 - TCAS Output Discrete (SL, R1)

TCAS To Transponder And Displays - Bus 2 Word 2

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 274 035 X
5 X
6 X
7 X
8 X
9
10
11
12
13
14
15 Pad
16
17
18
19
20
21
22
RF MSG BIT
23 SL (MSB) 9
24 SL 1 2 10
25 SL 11
26 R1 (MSB) 14
27 R1 1 2 15
28 R1 16
29 R1 17
30 SSM
31 SSM
32 Parity (odd)

NOTE 1: Sent by own transponder in data word DF, 0, 16.

NOTE 2: ARINC 429 data word fields for which there are corresponding RF fields are transmitted with the MSB
first in order to maintain consistency between RF and ARINC 429 data. Normal ARINC 429 protocol scla
for the transmission of the LSB of the field first.
ADDED: January 22, 1982
ARINC SPECIFICATION 429 PART 2 - Page 81

DATA STANDARDS

Label 274 03B

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 274 03B X
5 X
6 X
7 X
8 X
9-10 SDI
11 Magnetic Heading Flag Flag Normal
12 Localizer Flag Flag Normal
13 Glide Slope Flag Flag Normal
14 Low Range Radio Altimeter Flag Normal
15 ILS Limit Warn Warn Not Selected
16 ILS Frequency Select Selected Normal
17 INS Altitude Secondary Flags Flag Normal
18 INS True Heading Flags Flag Normal
19 INS HSI Nav Warn Warn Normal
20 CADC True Airspeed Flags Flag Normal
21 CADC Computer Airspeed Flags Flag Normal
22 CADC Corrected Altitude Flags Flag Normal
23 CADC Uncorrected Altitude Flag Flag Normal
24 CADC Mach Flag Flag Normal
25 Altitude Rate Module Flag Flag Normal
26 Spare (Pad Bit) X
27 Spare (Pad Bit) X
28 Spare (Pad Bit) X
29 Word Validity Invalid Valid
30-31 SSM
32 Parity (Odd)
 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 82

DATA STANDARDS

Label 274 03F

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 274 03F X
5 X
6 X
7 X
8 X
9 SDI X
10 SDI X
11 X
12 PAD X
13 X
14 Parity Test Hardware Error OK
15 ROM Checksum Failed OK
16 RAM Test Failed OK
17 Instruction Test Failed OK
18 High Speed Cross Link Text Failed OK
19 Foreground Software Execution Incorrect Correct
20 Watchdog timer Error OK
21 Spare X
22 EAHOM Failed OK
23 ROM Parity Error Caused Reset Yes No
24 RAM Parity Error caused Reset Yes No
25 Watchdog Timer Error Caused Reset Yes No
26 Status Buffer Failed OK
27 Loss of Clock Caused Reset Yes No
28 SDD Output #1 W/A Failed OK
29 SDD Output #2 W/A Failed OK
30 SSM X
31 SSM X
32 Parity (Odd)

NOTE: Typical discrete functions are shown in the above table. Slight variations of bit usage may arise according to
the specific application.
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 83

DATA STANDARDS

Label 274 05A - (A-320) FQS - Center

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 274 05A (Center) X
5 X
6 X
7 X
8 X
9 SDI
10
11
12 0.1 pf
13-14
15-16
17 1 pf
18
19
20 10 pf
21
22
23 100 pf
24
25 probe number
26 (units)
27
28 probe number
29 (units)
30-31 SSM
32 Parity

NOTE: Typical discrete functions are shown in the above table. Slight variations of bit usage may arise according
to the specific application.
ADDED: July 22, 1988
ARINC SPECIFICATION 429 PART 2 - Page 84

DATA STANDARDS

Label 274 0C5 - EFIS CP

ENCODING
Bit No. Function
1 0

1-8 Label 274 0C5

9-10 SDI
11 Spare
12 Spare
13 Spare
14 Spare
15 Spare
16 Spare
17 BARO SEL IN SEL NOT SEL
18 BARO SEL HPA SEL NOT SEL
19 BARO SEL MTRS SEL NOT SEL
20 FPV SEL NOT SEL
21 METRIC ALT SEL NOT SEL
22 WXR DATA SEL NOT SEL
23-29 MAP RANGE SEL NOT SEL
23-29 MAP RANGE SEL NOT SEL
23-29 MAP RANGE SEL NOT SEL
23-29 MAP RANGE SEL NOT SEL
23-29 MAP RANGE SEL NOT SEL
23-29 MAP RANGE SEL NOT SEL
23-29 MAP RANGE SEL NOT SEL
30-31 SSM
30-31 SSM
32 Parity (Odd)

MAP RANGE MATRIX

BIT POSITIONS 29 28 27 26 25 24 23 RANGE

0 0 0 0 0 1 0 5 MILES
0 0 0 0 1 0 0 10
0 0 0 1 0 0 0 20
0 0 1 0 0 0 0 40
0 1 0 0 0 0 0 80
1 0 0 0 0 0 0 160
0 0 0 0 0 0 0 320
0 0 0 0 0 0 1 640

SSM MATRIX

BIT POSITIONS 31 30

0 0 VALID DATA (WXR)

0 1 INVALID DATA (WXR)
ADDED: August 1, 1980
ARINC SPECIFICATION 429 PART 2 - Page 85

DATA STANDARDS

Label 275 001 - FCC Roll Modes Discrete Word

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 275 001 X
5 X
6 X
7 X
8 X
9 Unassigned
10 Unassigned
11 LNAV Requested Not Requested
12 HDG HOLD Requested Not Requested
13 HDG SEL Requested Not Requested
14 B/COURSE VOR Requested Not Requested
15 LOC Requested Not Requested
16 ROLLOUT Requested Not Requested
17 ROLL T.O. Requested Not Requested
18 ROLL G/A Requested Not Requested
19 Unassigned
20 WINGS LEVEL Requested Not Requested
21 CAPTURE Requested Not Requested
22 VOR Requested Not Requested
23 TRACK Requested Not Requested
24
25 Unassigned
26
27
28 ALIGN Requested Not Requested
29 CWS Requested Not Requested
30-31 SSM
32 Parity
ADDED: August 1, 1980
ARINC SPECIFICATION 429 PART 2 - Page 86

DATA STANDARDS

ROLL MODES EXPLANATIONS

Bit No. Function

11 LNAV The "Lateral Navigation" mode is selected.

12 HDG HOLD The "Heading Hold" mode is engaged.
13 HDG SEL The "Heading Select" mode is engaged.
14 B/COURSE VOR The "Backcourse" or "VOR" mode is selected.
15 LOC The "Localizer" guidance mode is selected.
16 ROLL OUT The "Roll Out" phase of the autoland mode is engaged.
17 ROLL T.O. The Roll Axis "Take Off" mode is engaged.
18 ROLL G/A The Roll Axis "Go Around" mode is engaged.
20 WINGS LEVEL The Roll Axis "Turbulence" penetration mode is engaged.
21 CAPTURE The "Capture" phase of the selected mode is engaged.
22 VOR The "VOR" mode is selected.
23 TRACK The "Track" phase of the selected mode is engaged.
28 ALIGN The "Align" phase of the autoland mode is engaged.
29 CWS The Roll Axis "CWS" mode is engaged.
 REVISED: August 1, 1980
ARINC SPECIFICATION 429 PART 2 - Page 87

DATA STANDARDS

Label 275 003 - TCC Discrete

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 275 003 X
5 X
6 X
7 X
8 X
9-10 SDI
11 Engine Type 1 High Low
12 Engine Type 2 High Low
13 Engine Type 3 Encoded to define one of 32 types High Low
14 Engine Type 4 High Low
15 Engine Type 5 High Low
16 LIM Automatic throttle control is currently limited by In Effect Not In Effect
flap or slat maximum speeds, or by engine limits (N1
or EPR), or by throttle low limit protection.
17 TO Mode Engaged Engaged Not Engaged
18 FLX TO Mode Engaged Engaged Not Engaged
19 Climb Mode Engaged Engaged Not Engaged
20 Cruise Mode Engaged Engaged Not Engaged
21 Maximum Continuous Thrust Mode Engaged Engaged Not Engaged
22 GA Mode Engaged Engaged Not Engaged
23 FLP Used with bit 16 to designate flap limit control. In Effect Not In Effect
currently in effect.
24 N1/EPR Limit Failure/Warning
25 SLT Used with bit 16 to designate slat limit. In Effect Not In Effect
26 N1 The automatic throttles are engaged in the N1 basic Engaged Not Engaged
mode and control to a selected N1 limit defined by
bits 17 thru 22. Also used with bit 16.
27 Test Test Normal
28 Spare
29 EPR The automatic throttles are engaged in the EPR basic Engaged Not Engaged
mode and control to a selected N1 limit defined by
bits 17 thru 22. Also used with bit 16.
30-31 SSM
32 Parity
ADDED: July 1, 1990
ARINC SPECIFICATION 429 PART 2 - Page 88

DATA STANDARDS

Label 275 018 - TCAS Control Discrete (MODE S Address Part 1)

Transponder To TCAS - Bus 1 Word 5

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 275 018 X
5 X
6 X
7 X
8 X
9
10
11 Pad
12
13
Mode S Address
(Part 1)
14 BIT A1 (MSB)
15 BIT A2
16 BIT A3
17 BIT A4
18 BIT A5
19 BIT A6 1
20 BIT A7
21 BIT A8
22 BIT A9 2
23 BIT A10
24 BIT A11
25 BIT A12
26 BIT A13
27 BIT A14
28 BIT A15
29 BIT A16 (LSB)
30-31 SSM
32 Parity (odd)

NOTE 1: Sent by own TCAS in data word UF-16.

NOTE 2: ARINC 429 data word fields for which there are corresponding RF fields are transmitted with the MSB
first in order to maintain consistency between RF and ARINC 429 data. Normal ARINC 429 protocol scla
for the transmission of the LSB of the field first.
 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 89

DATA STANDARDS

Label 275 02F

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 275 02F X
5 X
6 X
7 X
8 X
9-10 SDI X
11 X
12 PAD X
13 X
14 Lamp 1,2 &/or 3 W/A Failed OK
15 Other Channel’s Depower Discretes Disagree Agree
16 PB Sensor Failed OK
17 P4.9 Sensor Failed OK
18 P2 P(amb)** Sensor Failed OK
19 PBSensor Crosscheck* Failed OK
20 P4.9 Sensor Crosscheck* Failed OK
21 Serial Data Receiver Failed OK
22 Serial Data Transmitter Failed OK
23 Activity Monitor Failed OK
24 Other Channel’s Depower Logic Failed OK
25 Pressure Sensors Correlation Disagree Agree
26 PB Heater Failed OK
27 Automatic Channel Transfer* Failed OK
28 Pamb Sensor Drift* Failed OK
29 Spare X
30-31 SSM X
32 Parity (Odd)

* Primary channel only.

** Primary channel uses P2: Secondary channel uses Pamb

NOTE: Typical discrete functions are shown in the above table. Slight variations
of bit usage may arise according to the specific application.
ADDED: July 1, 1990
ARINC SPECIFICATION 429 PART 2 - Page 90

DATA STANDARDS

Label 275 035 - Acknowledgement (ACK/NAK) Discrete

TCAS To Transponder - Bus 2 Word 3

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 275 035 X
5 X
6 X
7 X
8 X
9
10
11
12
13
14
15
16
17 Pad
18
19
20
21
22
23
24
25
26
27
28
29 ACK/NAK ACK NAK
30 SSM
31 SSM
32 Parity (Odd)
 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 91

DATA STANDARDS

Label 275 03B

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 275 03B X
5 X
6 X
7 X
8 X
9-10 SDI
11 A/T Engage Engage Not Engaged
12 A/T Alternate Rating I Engage Not Engaged
13 A/T Alternate Rating II Engage Not Engaged
14 A/T Alpha Engage Not Engaged
15 A/T Flag Limit Engage Not Engaged
16 A/T Retard Engage Not Engaged
17 A/T Mach Engage Not Engaged
18 A/T Speed Engage Not Engaged
19 A/T EPR Engage Not Engaged
20 A/T Throttle Hold Engage Not Engaged
21 A/T Go Around Engage Not Engaged
22
23
24
25 Spare (all "0" states)
26
27
28
29 Word Validity Invalid Valid
30-31 SSM
32 Parity (Odd)
 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 92

DATA STANDARDS

Label 275 03F

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 275 03F X
5 X
6 X
7 X
8 X
9-10 SDI X
11 X
12 PAD X
13 X
14 Lamp 1,2 &/or 3 W/A Failed OK
15 Other Channel’s Depower Discretes Disagree Agree
16 PB Sensor Failed OK
17 P4.9 Sensor Failed OK
18 P2 P(amb)** Sensor Failed OK
19 PBSensor Crosscheck* Failed OK
20 P4.9 Sensor Crosscheck* Failed OK
21 Serial Data Receiver Failed OK
22 Serial Data Transmitter Failed OK
23 Activity Monitor Failed OK
24 Other Channel’s Depower Logic Failed OK
25 Pressure Sensors Correlation Disagree Agree
26 PB Heater Failed OK
27 Automatic Channel Transfer* Failed OK
28 Pamb Sensor Drift* Failed OK
29 Spare X
30-31 SSM X
32 Parity (Odd)

* Primary channel only.

** Primary channel uses P2: Secondary channel uses Pamb

NOTE: Typical discrete functions are shown in the above table. Slight variations
of bit usage may arise according to the specific application.
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 93

DATA STANDARDS

Label 275 05A - (A-320) FQS - Left Wing

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 275 05A (Left Wing) X
5 X
6 X
7 X
8 X
9 SDI
10
11
12 0.1 pf
13-14
15-16
17 1 pf
18
19
20 10 pf
21
22
23 100 pf
24
25 probe number
26 (units)
27
28 probe number
29 (units)
30-31 SSM
32 Parity

NOTE: Typical discrete functions are shown in the above table. Slight variations of bit usage may arise according
to the specific application.
ADDED: July 1, 1990
ARINC SPECIFICATION 429 PART 2 - Page 94

DATA STANDARDS

Label 276 018 - TCAS Control Discrete (Mode S Address Part 2, Max A/S)

Transponder To TCAS - Bus 1 Word 6

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 276 018 X
5 X
6 X
7
8 X
9 Aural Advisory Cancel and Cancel Normal
Visual Annunciator
10 R1 Echo 1
11 Pad
12 Pad
Mode S Address
(Part 2) RF MSG BIT
(MSB) 81
13 BIT A17 82
14 BIT A18 83
15 BIT A19 2 84
16 BIT A20 85
17 BIT A21 3 86
18 BIT A22 87
19 BIT A23 88
20 BIT A24 (LSB) 14
21 (MSB) 15
22 Maximum 16
23 Airspeed 3 17
24 (LSB)
25 Pad
26 Pad
27 Pad
28 Pad
29 Pad
30 SSM
31 SSM
32 Parity (odd)

NOTE 1: See Attachment 12 of ARINC Characteristic 735 for logic encoding of the R1 field.
NOTE 2: Sent by own transponder in DF-0, 16.
NOTE 3: ARINC 429 data word fields for which there are corresponding RF fields are transmitted with the MSB
first in order to maintain consistency between RF and ARINC 429 data. Normal ARINC 429 protocol scla
for the transmission of the LSB of the field first.
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 95
DATA STANDARDS

Label 276 025 - Discrete Status 8 EFIS

Bit No. Function Bit Status

1 0

1 X
2 X
3 X
4 Label 276 025 X
5 X
6 X
7 X
8 X
9-10 SDI
11 RESERVED
12 RESERVED
13 RESERVED
14 RESERVED
15 RESERVED
16 RESERVED
17 RESERVED
18 RESERVED
19 RESERVED
20 RESERVED
21 RESERVED
22 RESERVED
23 RESERVED
24 RESERVED
25 RESERVED
26 RESERVED
27 PAD X
28 PAD X
29 PAD X
30-31 SSM
32 Parity (Odd)
 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 96

DATA STANDARDS

Label 276 02F

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 276 02F X
5 X
6 X
7 X
8
9-10 SDI X
11 X
12 PAD X
13 X
14 EEC Channel Failed OK
15 EEC Unit Failed OK
16 Resolver/ LVDT Excitation Failed OK
17 Spare X
18 Spare X
19 FCU Functions Failed OK
20 HCC Functions Failed OK
21 LCC Functions Failed OK
22 2.5 Bleed Functions W/A Failed OK
23 Spare X
24 Spare X
25 Spare X
26 Spare X
27 Spare X
28 EEC Temperature Status High OK
29 Overspeed Test** Failed OK
30-31 SSM X
32 Parity (Odd)

** Second channel only.

NOTE: Typical discrete functions are shown in the above table. Slight variations
of bit usage may arise according to the specific application.
 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 97

DATA STANDARDS

Label 276 03F

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 276 03F X
5 X
6 X
7 X
8
9-10 SDI X
11 X
12 PAD X
13 X
14 EEC Channel Failed OK
15 EEC Unit Failed OK
16 Resolver/ LVDT Excitation Failed OK
17 Spare X
18 Spare X
19 FCU Functions Failed OK
20 HCC Functions Failed OK
21 LCC Functions Failed OK
22 2.5 Bleed Functions W/A Failed OK
23 Spare X
24 Spare X
25 Spare X
26 Spare X
27 Spare X
28 EEC Temperature Status High OK
29 Overspeed Test** Failed OK
30-31 SSM X
32 Parity (Odd)

** Second channel only.

NOTE: Typical discrete functions are shown in the above table. Slight variations
of bit usage may arise according to the specific application.
ADDED: July 1, 1990
ARINC SPECIFICATION 429 PART 2 - Page 98

ATTACHMENT 2 (cont’d)
DATA STANDARDS

Label 277 018 - Acknowledgement (ACK/NAK) Discrete

Transponder To TCAS - Bus 1 Word 7

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 277 018 X
5 X
6 X
7 X
8 X
9
10
11
12
13
14
15
16
17
18 Pad
19
20
21
22
23
24
25
26
27
28
29 ACK/NAK ACK NAK
30 SSM
31 SSM
32 Parity (Odd)
ADDED: January 22, 1982
ARINC SPECIFICATION 429 PART 2 - Page 101

DATA STANDARDS

Label 350 01A - EEC Discrete

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 350 01A X
5 X
6 X
7 X
8 X
9-10 SDI
11 Pad X
12 Pad X
13 Pad X
14 Pad X
15 Connector J2 Not Inst. Inst.
16 Connector J5 Not Inst. Inst.
17 T2 Probe Failed Good
18 EGT Assy. Failed Good
19 TLA Resol. Failed Good
20 RPX Failed Good
21 A Chan SDD In Failed Good
22 B Chan SDD In Failed Good
23 Coil Failed Good
24 Stg I Valve Malfunction Good
25 P2 Leak Leak Good
26 System Trim Required Good
27 TCA-A Valve Malfunction Good
28 TCA-B Valve Malfunction X
29 Spare
30-31 SSM
32 Parity (Odd)
ADDED: July 22, 1988
ARINC SPECIFICATION 429 PART 2 - Page 102

DATA STANDARDS

Label 350 027 - MLS Fault Summary

Bit Status
Bit No. Function
1 0

1-8 Label (Octal) 350 027

9-10 SDI
11 LRU Failure Failure OK
12 #1 Antenna Failure Failure OK
13 #2 Antenna Failure Failure OK
14 #3 Antenna Failure Failure OK
15 Source Selection Port A Port B
16 Input Data Inactive OK
17 CFDIU Input Bus Inactive OK
18 Battery Low Warning Low OK
19 Resv. MIL-STD-1553B Input Bus Inactive OK
20 Resv. DME Input Bus Inactive OK
21 Resv. DME Tuning Interface Failure OK
22 Resv. Synchro Reference Invalid Failure OK
23
24
25
26
27
28 Bite Test Inhibit Inhibit Enable
29 Commmand Word Acknowledge ACK NAK
30 SSM
31 SSM
32 Parity (Odd)

NOTE: Transmission interval min. 50 ms, max. 250 ms.

 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 103

DATA STANDARDS

Label 350 02F

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 350 02F X
5 X
6 X
7 X
8 X
9-10 SDI X
11 X
12 PAD X
13 X
14 N1 Signal Failed OK
15 N2 Signal Failed OK
16 T2 Signal Failed OK
17 T4.9 Signal Failed OK
18 Tfuel Signal Failed OK
19 Toil Signal Failed OK
20 Wf Feedback Signal Failed OK
21 SVA Feedback Signal Failed OK
22 2.5 BLD Feedback Signal Failed OK
23 HCC Feedback Signal Failed OK
24 LCC Feedback Signal Failed OK
25 Reverser Position Signal Failed OK
26 AOX Feedback Signal Failed OK
27 Reserved (Spare Feedback Signal) X
28 Thrust Lever Position Signal Failed OK
29 Spare X
30-31 SSM X
32 Parity (Odd)

NOTE: Typical discrete functions are shown in the above table. Slight variations
of bit usage may arise according to the specific application.
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 104
DATA STANDARDS

Label 350 03D - Maintenance Data #1

Bit No. Function 1 0

1 X
2 X
3 X
4 Label 350 03D X
5 X
6 X
7 X
8 X
9-10 SDI
11-28 Data
30-31 Status Matrix
32 Parity (Odd)

Bits Data

10 9

0 0 Engine 4 (or All Call) {Not used on 757}

0 1 Engine 1 (or Engine 1 and 2)
1 0 Engine 2
1 1 Engine 3 (or Engine 3 and 4)

Bit Data

11 Signal Conditioner Status

12 N1 Tachometer Signal Loss
13 N2 Tachometer Signal Loss
*14 PAD
**14 N3 Tachometer Signal Loss
15 Ch A Accelerometer High Noise
***15 PAD
16 Ch B Accelerometer High Noise
***16 PAD
17 Channel A <> Channel B
***17 PAD
*18 PAD
**18 High Broadband Levels
*19 PAD
**19 Ch A Accelerometer Low Signal
*20 PAD
**20 Ch B Accelerometer Low Signal
21 PAD
22 PAD
23 PAD
24 PAD
25 PAD
26 PAD
27 PAD
28 Unit Not Available
29 Command Word Acknowledge

* 757 Pratt and Whitney and 737 CFM Only (Reserved)

** 757 Rolls Royce Only
*** 757 Only
 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2- Page 105

DATA STANDARDS

Label 350 03F

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 350 03F X
5 X
6 X
7 X
8 X
9-10 SDI X
11 X
12 PAD X
13 X
14 N1 Signal Failed OK
15 N2 Signal Failed OK
16 T2 Signal Failed OK
17 T4.9 Signal Failed OK
18 Tfuel Signal Failed OK
19 Toil Signal Failed OK
20 Wf Feedback Signal Failed OK
21 SVA Feedback Signal Failed OK
22 2.5 BLD Feedback Signal Failed OK
23 HCC Feedback Signal Failed OK
24 LCC Feedback Signal Failed OK
25 Reverser Position Signal Failed OK
26 AOX Feedback Signal Failed OK
27 Reserved (Spare Feedback Signal) X
28 Thrust Lever Position Signal Failed OK
29 Spare X
30-31 SSM X
32 Parity (Odd)

NOTE: Typical discrete functions are shown in the above table. Slight variations
of bit usage may arise according to the specific application.
ADDED: July 1, 1990
ARINC SPECIFICATION 429 PART 2 - Page 107

DATA STANDARDS

Label 350 114 - Fuel Unit Management System Discrete (A-330/A-340)

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 350 114 X
5 X
6 X
7 X
8 X
9 SDI
10
11
12
13 Fuel Density (0.0001’s)
14
15
16
17 Fuel Density (0.001’s)
18
19
20
21 Fuel Density (0.01’s)
22
23
24
25 Fuel Density (0.1’s)
26
27
28 Tank Ident
29
30 SSM
31 SSM
32 Parity (Odd)
ADDED: July 1, 1990
ARINC SPECIFICATION 429 PART 2 - Page 108

DATA STANDARDS

Label 350 115 - TACAN Discrete

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 350 115 X
5 X
6 X
7 X
8 X
9 LSB
10
11
12 AGC
13 (X 1/256 FULL SCALE)
14
15
16 MSB
17 CPU Failed OK
18 RAM Failed OK
19 ROM Failed OK
20 2 PORT RAM Failed OK
21 2 PORT DATA Failed OK
22 NOVRAM Failed OK
23 SYNTHESIZER Failed OK
24 RECEIVER Failed OK
25 POWER SUPPLY Failed OK
26 XMIT POWER Failed OK
27 AUDIO Failed OK
28 POWER UP Failed OK
29 SUPPRESSION Present Not Present
30 D/A Failed OK
31 TACAN FAIL Failed OK
32 Parity (Odd)

NOTE: Bite 21 thru 28 indicate self test status information.

ADDED: January 22, 1982
ARINC SPECIFICATION 429 PART 2 - Page 109

DATA STANDARDS

Label 351 01A - EEC Discrete

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 351 01A X
5 X
6 X
7 X
8 X
9-10 SDI
11 Pad X
12 Pad X
13 Pad X
14 Pad X
15 ARINC Transmitter Fail Good
16 RPX Drift Fail Good
17 RPX Test Fail Good
18 TLA Correl Test Fail Good
19 Resolver Test Fail Good
20 Resolver Drift Fail Good
21 Angle Range Check Fail Good
22 Sine Range Check Fail Good
23 Cosine Range Check Fail Good
24 Spare X
25 LLDC Test #1 Fail Good
26 LLDC Drift #1 Fail Good
27 P2 Range Check (Boeing Only) Fail Good
28 P7 Range Check Fail Good
29 EPR Range Check Fail Good
30-31 SSM
32 Parity (Odd)
 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 110

DATA STANDARDS

Label 351 02F

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 351 02F X
5 X
6 X
7 X
8 X
9-10 SDI X
11 X
12 PAD X
13 X
14 Local ADC Inputs (Pri-Left, Failed OK
Sec-Right)
15 Crosstalk ADC Inputs* Failed OK
16 Wf T/M W/A Failed OK
17 SVA T/M W/A Failed OK
18 2.5 BLD T/M W/A Failed OK
19 HCC T/M W/A Failed OK
20 LCC T/M W/A Failed OK
21 AOX T/M W/A Failed OK
22 Spare X
23 Wf Track Check Failed OK
24 SVA Track Check Failed OK
25 2.5 BLD Track Check Failed OK
26 HCC Track Check Failed OK
27 LCC Track Check Failed OK
28 AOX Track Check Failed OK
29 Reserved (Spare Track Check) X
30-31 SSM X
32 Parity (Odd)

* Primary channel only.

NOTE: Typical discrete functions are shown in the above table. Slight variations
of bit usage may arise according to the specific application.
 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 111

DATA STANDARDS

Label 351 03F

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 351 03F X
5 X
6 X
7 X
8 X
9-10 SDI X
11 X
12 PAD X
13 X
14 Local ADC Inputs (Pri-Left, Failed OK
Sec-Right)
15 Crosstalk ADC Inputs* Failed OK
16 Wf T/M W/A Failed OK
17 SVA T/M W/A Failed OK
18 2.5 BLD T/M W/A Failed OK
19 HCC T/M W/A Failed OK
20 LCC T/M W/A Failed OK
21 AOX T/M W/A Failed OK
22 Spare X
23 Wf Track Check Failed OK
24 SVA Track Check Failed OK
25 2.5 BLD Track Check Failed OK
26 HCC Track Check Failed OK
27 LCC Track Check Failed OK
28 AOX Track Check Failed OK
29 Reserved (Spare Track Check) X
30-31 SSM X
32 Parity (Odd)

* Primary channel only.

NOTE: Typical discrete functions are shown in the above table. Slight variations
of bit usage may arise according to the specific application.
ADDED: July 1, 1990
ARINC SPECIFICATION 429 PART 2 - Page 113

DATA STANDARDS

Label 351 114 - Fuel Unit Management System Discrete (A-330/A-340)

Bit Status
Bit No. Function
1 0

1 X
2 X
3 Label 351 114 (Left Wing) X
4 X
5 X
6 X
7 X
8 X
9 SDI
10
11
12
13 Probe Capacitance (0.1’s)
14
15
16
17 Probe Capacitance (1’s)
18
19
20
21 Probe Capacitance (10’s)
22
23 Probe Capacitance (100’s)
24
25
26 Probe Number (1’s)
27
28
29 Probe Number (10’s)
30 SSM
31 SSM
32 Parity (Odd)
ADDED: January 22, 1982
ARINC SPECIFICATION 429 PART 2 - Page 114

DATA STANDARDS

Label 352 01A - EEC Discrete

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 352 01A X
5 X
6 X
7 X
8 X
9-10 SDI
11 Pad X
12 Pad X
13 Pad X
14 Pad X
15 EGT Loop Sel/Fail Fail Good
16 N2 Fail Good
17 P7 Test Fail Good
18 N2/P2 Test Fail Good
19 T/M, D/A or Driver Fail Good
20 T/M "Undetermined" Fail Good
21 Pres Temp Inputs Fail Good
22 Latch Solenoid W/A Fail Good
23 Health Indicator W/A Fail Good
24 ROM Sum Test Fail Good
25 RAM Test Fail Good
26 Watchdog Timer Fail Good
27 Instruction Test Fail Good
28 Watchdog Resets Fail Good
29 Converter Reset Fail Good
30-31 SSM
32 Parity (Odd)
 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 115

DATA STANDARDS

Label 352 02F

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 352 02F X
5 X
6 X
7 X
8 X
9-10 SDI X
11 X
12 PAD X
13 X
14 DC Power Group 1 Failed OK
15 DC Power Group 2 Failed OK
16 Spare X
17 EEC to PDIU SDD Failed OK
18 PDIU Self Test Failed OK
19 HCC T/M W/A Failed OK
20 Local TCA Valve (Pri-Left, Failed OK
Sec-Right)
21 Crosstalk TCA Valve Check* Failed OK
22 Spare X
23 SDD Input from PDIU Failed OK
24 N1 Sensor (Pri and Sec)* Failed OK
25 PB Pneumatic Line* Failed OK
26 P4.9 Pneumatic Line* Failed OK
27 P2 Probe / Line* Failed OK
28 Fire Warn. Discrete Disagreement* Disagree OK
29 Data Entry Plug Failed OK
30-31 SSM X
32 Parity (Odd)

* Primary channel only.

NOTE: Typical discrete functions are shown in the above table. Slight variations
of bit usage may arise according to the specific application.
 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 116

DATA STANDARDS

Label 352 03F

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 352 03F X
5 X
6 X
7 X
8 X
9-10 SDI X
11 X
12 PAD X
13 X
14 DC Power Group 1 Failed OK
15 DC Power Group 2 Failed OK
16 Spare X
17 EEC to PDIU SDD Failed OK
18 PDIU Self Test Failed OK
19 HCC T/M W/A Failed OK
20 Local TCA Valve (Pri-Left, Failed OK
Sec-Right)
21 Crosstalk TCA Valve Check* Failed OK
22 Spare X
23 SDD Input from PDIU Failed OK
24 N1 Sensor (Pri and Sec)* Failed OK
25 PB Pneumatic Line* Failed OK
26 P4.9 Pneumatic Line* Failed OK
27 P2 Probe / Line* Failed OK
28 Fire Warn. Discrete Disagreement* Disagree OK
29 Data Entry Plug Failed OK
30-31 SSM X
32 Parity (Odd)

* Primary channel only.

NOTE: Typical discrete functions are shown in the above table. Slight variations
of bit usage may arise according to the specific application.
ADDED: July 1, 1990
ARINC SPECIFICATION 429 PART 2 - Page 118

DATA STANDARDS

Label 352 114 - Fuel Unit Management System Discrete (A-330/A-340)

Bit Status
Bit No. Function
1 0

1 X
2 X
3 Label 352 114 (Center/Trim) X
4 X
5 X
6 X
7 X
8 X
9 SDI
10
11
12
13 Probe Capacitance (0.1’s)
14
15
16
17 Probe Capacitance (1’s)
18
19
20
21 Probe Capacitance (10’s)
22
23 Probe Capacitance (100’s)
24
25
26 Probe Number (1’s)
27
28
29 Probe Number (10’s)
30 SSM
31 SSM
32 Parity (Odd)
ADDED: January 22, 1982
ARINC SPECIFICATION 429 PART 2 - Page 119

DATA STANDARDS

Label 353 01A - EEC Discrete

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 353 01A X
5 X
6 X
7 X
8 X
9-10 SDI
11 Pad X
12 Pad X
13 Pad X
14 Pad X
15 Spare X
16 EGT Loop Disabled Yes No
17 Synth Altitude Yes No
18 Synth Mach Number Yes No
19 SDD ’A’ W/A Failure Good
20 ADD ’B’ W/A Failure Good
21 Probe Heat (Boeing 767 Only) Disagreement Normal
22 Pressure Accuracy Degraded Normal
23 T/M Coil Yes No
24 TCC Schedule (Airbus Default Normal
25 Acft Pt Used 310,000 Yes No
26 P2 Range Check Only) Failed Good
27 TCA System Failed Good
28 TCC System Failed Good
29 System Trim Required Okay
30-31 SSM
32 Parity (Odd)
 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 120

DATA STANDARDS

Label 353 02F

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 353 02F X
5 X
6 X
7 X
8 X
9-10 SDI X
11 X
12 PAD X
13 X
14 N1 Crosscheck* Failed OK
15 N2 Crosscheck* Failed OK
16 Spare X
17 Spare X
18 T2 Crosscheck* Failed OK
19 T2 Probe/ADC T2 Disagreement Disagree OK
20 Tfuel Crosscheck* Failed OK
21 Toil Crosscheck* Failed OK
22 Wf Feedback Crosscheck* Failed OK
23 SVA Feedback Crosscheck Failed OK
24 2.5 BLD Feedback Crosscheck* Failed OK
25 HCC Feedback Crosscheck* Failed OK
26 LCC Feedback Crosscheck* Failed OK
27 Reverser Position Crosscheck* Failed OK
28 AOX Feedback Crosscheck Failed OK
29 Thrust Lever Position Crosscheck* Failed OK
30-31 SSM X
32 Parity (Odd)

* Primary channel only.

NOTE: Typical discrete functions are shown in the above table. Slight variations
of bit usage may arise according to the specific application.
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 121
DATA STANDARDS

Label 353 03D - Maintenance Data #4 Highest Vibration

Bit No. Function 1 0

1 X
2 X
3 X
4 Label 353 03D X
5 X
6 X
7 X
8 X
9-10 SDI
11-12 Accelerometer Source
13 X
14 X
15 PADS X
16 X
17 X
18-19 Data ID
20-28 Data
29-31 SSM
32 Parity (Odd)

Bits Data Bits Data

10 9 12 11

0 0 Engine 4 0 0 No Channel in commmand

0 1 Engine 1 0 1 Channel A
1 0 Engine 2 1 0 Channel B
1 1 Engine 3

* Data ID

Bits Data

19 18

0 0 N1 Vibration (Label 354)

0 1 N2 Vibration (Label 355)
1 0 N3 Vibration (Label 356)
1 1 BB Vibration (Label 357)

* 737 Data ID

Bits Data

19 18

0 0 CN1 Vibration (Label 354)

0 1 CN2 Vibration (Label 355)
1 0 TN1 Vibration (Label 356)
1 1 TN2 Vibration (Label 357)
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 122

DATA STANDARDS

Label 353 03D - Maintenance Data #4 Highest Vibration (cont’d)

* 757 Data ID

Bits Data

19 18

0 0 BB Vibration (Label 357)

0 1 N1 Vibration (Label 354)
1 0 N1 Vibration (Label 355)
1 1 N3 Vibration (Label 356)**

** Used on 757 Rolls Royce Engines only

Data

Bit 28 27 26 25 24 23 22 21 20
MSB <----------------------> LSB

Bit Encoding for Vibration Labels

Bits = 9
Resolution = 0.01
Range = 0 to 5.12
Units = Scalar Units

SSM

Bits Data

31 30 29

1 0 0 Self Test
1 1 0 Normal Operation
 REVISED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 123

DATA STANDARDS

Label 353 03F

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 353 03F X
5 X
6 X
7 X
8 X
9-10 SDI X
11 X
12 PAD X
13 X
14 N1 Crosscheck* Failed OK
15 N2 Crosscheck* Failed OK
16 Spare X
17 Spare X
18 T2 Crosscheck* Failed OK
19 T2 Probe/ADC T2 Disagreement Disagree OK
20 Tfuel Crosscheck* Failed OK
21 Toil Crosscheck* Failed OK
22 Wf Feedback Crosscheck* Failed OK
23 SVA Feedback Crosscheck Failed OK
24 2.5 BLD Feedback Crosscheck* Failed OK
25 HCC Feedback Crosscheck* Failed OK
26 LCC Feedback Crosscheck* Failed OK
27 Reverser Position Crosscheck* Failed OK
28 AOX Feedback Crosscheck Failed OK
29 Thrust Lever Position Crosscheck* Failed OK
30-31 SSM X
32 Parity (Odd)

* Primary channel only.

NOTE: Typical discrete functions are shown in the above table. Slight variations
of bit usage may arise according to the specific application.
ADDED: July 1, 1990
ARINC SPECIFICATION 429 PART 2 - Page 125

DATA STANDARDS

Label 353 114 - Fuel Unit Management System Discrete (A-330/A-340)

Bit Status
Bit No. Function
1 0

1 X
2 X
3 Label 353 114 (Right Wing) X
4 X
5 X
6 X
7 X
8 X
9 SDI
10
11
12
13 Probe Capacitance (0.1’s)
14
15
16
17 Probe Capacitance (1’s)
18
19
20
21 Probe Capacitance (10’s)
22
23 Probe Capacitance (100’s)
24
25
26 Probe Number (1’s)
27
28
29 Probe Number (10’s)
30 SSM
31 SSM
32 Parity (Odd)
ADDED: January 22, 1982
ARINC SPECIFICATION 429 PART 2 - Page 126

DATA STANDARDS

Label 354 01A - EEC Discrete

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 354 01A X
5 X
6 X
7 X
8 X
9-10 SDI
11 Pad X
12 Pad X
13 Pad X
14 Pad X
15 TPT2 Temp Diode Fail Good
16 TPT7 Temp Diode Fail Good
17 Fail Good
18 T/M W/A’A Range Check Fail Good
19 T/M W/A’B Range Check Fail Good
20 Spare X
21 Spare X
22 LLDC Test #2 Fail Good
23 LLDC Drift #2 Fail Good
24 TCC Stage I W/A Fail Good
25 TCC Stage II W/A Fail Good
26 TCC Stage III W/A Fail X
27 Spare X
28 Spare X
29 Spare
30-31 SSM
32 Parity (Odd)
ADDED: November 17, 1986
ARINC SPECIFICATION 429 PART 2- Page 127

DATA STANDARDS

Label 354 02F

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 354 02F X
5 X
6 X
7 X
8 X
9-10 SDI X
11 X
12 PAD X
13 X
14 REV Command Solenoid W/A Failed OK
15 TCA Solenoid W/A Failed OK
16 Reserved (Spare Solenoid W/A) X
17 Reserved (Spare Solenoid W/A) X
18 Reserved (Spare Relay W/A) X
19 14th Stage Bleed T/M W/A Failed OK
20 Spare X
21 Reserved (Spare Solenoid W/A) X
22 Oil Bypass Solenoid W/A Failed OK
23 Reserved (Spare Relay W/A) X
24 T/L Interlock Relay W/A Failed OK
25 Reserved (Spare Relay W/A) X
26 Spare X
27 Group 1 Overcurrent Sense Tripped OK
28 Group 2 Overcurrent Sense Tripped OK
29 Spare X
30-31 SSM X
32 Parity (Odd)

NOTE: Typical discrete functions are shown in the above table. Slight variations
of bit usage may arise according to the specific application.
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 128
DATA STANDARDS

Label 354 03D - Maintenance Data #5 N1 Vibration

Bit No. Function 1 0

1 X
2 X
3 X
4 Label 354 03D X
5 X
6 X
7 X
8 X
9-10 SDI
11-12 Accelerometer Source
13 X
14 X
15 X
16 PADS X
17 X
18 X
19 X
20-28 Data
29 X
30 SSM (Normal Operation) X
31 X
32 Parity (Odd)

Bits Data Bits Data

10 9 12 11

0 0 Engine 4 0 0 No Channel in commmand

0 1 Engine 1 0 1 Channel A
1 0 Engine 2 1 0 Channel B
1 1 Engine 3

Bit 28 27 26 25 24 23 22 21 20
MSB <----------------------> LSB

Bit Encoding for Vibration Labels

Bits = 9
Resolution = 0.01
Range = 0 to 5.12
Units = Scalar Units
ADDED: November 17, 1986
ARINC SPECIFICATION 429 PART 2 - Page 129

DATA STANDARDS

Label 354 03F

Bit Status
Bit No. Function
1 0

1 X
2 X
3 X
4 Label 354 03F X
5 X
6 X
7 X
8 X
9-10 SDI X
11 X
12 PAD X
13 X
14 REV Command Solenoid W/A Failed OK
15 TCA Solenoid W/A Failed OK
16 Reserved (Spare Solenoid W/A) X
17 Reserved (Spare Solenoid W/A) X
18 Reserved (Spare Relay W/A) X
19 14th Stage Bleed T/M W/A Failed OK
20 Spare X
21 Reserved (Spare Solenoid W/A) X
22 Oil Bypass Solenoid W/A Failed OK
23 Reserved (Spare Relay W/A) X
24 T/L Interlock Relay W/A Failed OK
25 Reserved (Spare Relay W/A) X
26 Spare X
27 Group 1 Overcurrent Sense Tripped OK
28 Group 2 Overcurrent Sense Tripped OK
29 Spare X
30-31 SSM X
32 Parity (Odd)

NOTE: Typical discrete functions are shown in the above table. Slight variations
of bit usage may arise according to the specific application.
ADDED: July 22, 1988
ARINC SPECIFICATION 429 PART 2- Page 131

DATA STANDARDS

Label 355 027 - Fault Supplement Word for MLS

Bit Status
Bit No. Function
1 0

1
2
3
4
5 Label 355 027
6
7
8
9 SDI
10
11
12
13
14
15
16
17
18
19
20
21
22
23 BITS 11 thru 29
24 reserved for Company
25 private use.
26
27
28
29
30 SSM
31
32 Parity (Odd)

NOTE: Transmission interval min. 50 ms, max. 250 ms.

ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 132
DATA STANDARDS

Label 355 03D - Maintenance Data #6 N2 Vibration

Bit No. Function 1 0

1 X
2 X
3 X
4 Label 355 03D X
5 X
6 X
7 X
8 X
9-10 SDI
11-12 Accelerometer Source
13 X
14 X
15 X
16 PADS X
17 X
18 X
19 X
20-28 Data
29 X
30 SSM (Normal Operation) X
31 X
32 Parity (Odd)

Bits Data Bits Data

10 9 12 11

0 0 Engine 4 0 0 No Channel in commmand

0 1 Engine 1 0 1 Channel A
1 0 Engine 2 1 0 Channel B
1 1 Engine 3

Bit 28 27 26 25 24 23 22 21 20
MSB <----------------------> LSB

Bit Encoding for Vibration Labels

Bits = 9
Resolution = 0.01
Range = 0 to 5.12
Units = Scalar Units
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 134

DATA STANDARDS

Label 356 03D - N3 Vibration

Bit No. Function 1 0

1 X
2 X
3 X
4 Label 356 03D X
5 X
6 X
7 X
8 X
9-10 SDI
11-12 Accelerometer Source
13 X
14 X
15 X
16 PADS X
17 X
18 X
19 X
20-28 Data
29 X
30 SSM (Normal Operation) X
31 X
32 Parity (Odd)

Bits Data Bits Data

10 9 12 11

0 0 Engine 4 0 0 No Channel in commmand

0 1 Engine 1 0 1 Channel A
1 0 Engine 2 1 0 Channel B
1 1 Engine 3

Bit 28 27 26 25 24 23 22 21 20
MSB <----------------------> LSB

Bit Encoding for Vibration Labels

Bits = 9
Resolution = 0.01
Range = 0 to 5.12
Units = Scalar Units
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 135

DATA STANDARDS

Label 357 03D - BB Vibration

Bit No. Function 1 0

1 X
2 X
3 X
4 Label 357 03D X
5 X
6 X
7 X
8 X
9-10 SDI
11-12 Accelerometer Source
13 X
14 X
15 X
16 PADS X
17 X
18 X
19 X
20-28 Data
29 X
30 SSM (Normal Operation) X
31 X
32 Parity (Odd)

Bits Data Bits Data

10 9 12 11

0 0 Engine 4 0 0 No Channel in commmand

0 1 Engine 1 0 1 Channel A
1 0 Engine 2 1 0 Channel B
1 1 Engine 3

Bit 28 27 26 25 24 23 22 21 20
MSB <----------------------> LSB

Bit Encoding for Vibration Labels

Bits = 9
Resolution = 0.01
Range = 0 to 5.12
Units = Scalar Units
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 137

DATA STANDARDS

Label 360 03D - N1 Rotor Imbalance Angle

Bit No. Function 1 0

1 X
2 X
3 X
4 Label 360 03D X
5 X
6 X
7 X
8 X
9-10 SDI
11-12 Accelerometer Source
13 X
14 X
15 X
16 PADS X
17 X
18 X
19 X
20-28 Data
29-31 SSM
32 Parity (Odd)

Bits Data Bits Data

10 9 12 11

0 0 Engine 4 0 0 No Channel in commmand

0 1 Engine 1 0 1 Channel A
1 0 Engine 2 1 0 Channel B
1 1 Engine 3

Bit 28 27 26 25 24 23 22 21 20
MSB <----------------------> LSB

Bit Encoding for Imbalance Angles

Bits = 9
Resolution = 1.0
Range = 0 to 360
Units = Degrees

Bits Data

31 30 29

1 0 0 Functional Test
0 1 0 No Computed Data
1 1 0 Normal Operation
0 0 0 Failure Warning
ADDED: MARCH 6, 1996
ARINC SPECIFICATION 429 PART 2 - Page 138

DATA STANDARDS

Label 361 03D* - LPT Rotor Imbalance Angle

Bit No. Function 1 0

1 X
2 X
3 X
4 Label 361 03D X
5 X
6 X
7 X
8 X
9-10 SDI
11-12 Accelerometer Source
13 X
14 X
15 X
16 PADS X
17 X
18 X
19 X
20-28 Data
29-31 SSM
32 Parity (Odd)

Bits Data Bits Data

10 9 12 11

0 0 Engine 4 0 0 No Channel in commmand

0 1 Engine 1 0 1 Channel A
1 0 Engine 2 1 0 Channel B
1 1 Engine 3

Bit 28 27 26 25 24 23 22 21 20
MSB <----------------------> LSB

Bit Encoding for Imbalance Angles

Bits = 9
Resolution = 1.0
Range = 0 to 360
Units = Degrees

Bits Data

31 30 29

1 0 0 Functional Test
0 1 0 No Computed Data
1 1 0 Normal Operation
0 0 0 Failure Warning

* 737 Only
 MARK 33 DIGITAL INFORMATION TRANSFER
SYSTEM (DITS), PART 3
FILE DATA TRANSFER TECHNIQUES

ARINC SPECIFICATION 429P3-18

PUBLISHED: OCTOBER 12, 2001

AN A DOCUMENT
Prepared by
AIRLINES ELECTRONIC ENGINEERING COMMITTEE
Published by
AERONAUTICAL RADIO, INC.
2551 RIVA ROAD, ANNAPOLIS, MARYLAND 21401
This document is based on material submitted by various
participants during the drafting process. Neither AEEC nor ARINC
has made any determination whether these materials could be
subject to valid claims of patent, copyright or other proprietary
rights by third parties, and no representation or warranty, express or
implied, is made in this regard. Any use of or reliance on this
document shall constitute an acceptance thereof “as is” and be
subject to this disclaimer.
 ©
Copyright 2001 by
AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401-7465 USA

©
ARINC SPECIFICATION 429P3-18
MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

PART 3

FILE DATA TRANSFER TECHNIQUES

Published: October 12, 2001

Prepared by the Airlines Electronic Engineering Committee

Specification 429P3 Adopted by the Airlines Electronic Engineering Committee: July 21, 1977
Specification 429P3 Adopted by the Industry: September 15, 1977

Summary of Document Supplements

Supplement Adoption Date Published
Specification 429P3-1 April 11, 1978 June 1, 1978
Specification 429P3-2 December 6, 1978 March 1, 1979
Specification 429P3-3 August 31, 1979 November 1, 1979
Specification 429P3-4 June 17, 1980 August 1, 1980
Specification 429P3-5 March 12, 1981 April 24, 1981
Specification 429P3-6 December 9, 1981 January 22, 1982
Specification 429P3-7 November 4, 1983 January 3, 1984
Specification 429P3-8 November 4, 1984 December 3, 1984
Specification 429P3-9 October 11, 1984 April 30, 1985
Specification 429P3-10 November 7, 1985 November 17, 1986
Specification 429P3-11 June 15, 1988 July 22, 1988
Specification 429P3-12 October 25, 1989 July 1, 1990
Specification 429P3-13 October 8, 1991 December 30, 1991
Specification 429P3-14 November 4, 1992 January 4, 1993
Specification 429P3-15 April 18, 1995 September 1, 1995
Specification 429P3-16 June 24, 1997 June 30, 1997
Specification 429P3-17 March 31, 1999 May 17, 1999
Specification 429P3-18 July 18, 2001 October 12, 2001
A description of the changes introduced by each supplement is included on Goldenrod paper at the end of this document.
 FOREWORD
Activities of AERONAUTICAL RADIO, INC. (ARINC)
and the
Purpose of ARINC Reports and Specifications

Aeronautical Radio, Inc. is a corporation in which the United States scheduled airlines are the
principal stockholders. Other stockholders include a variety of other air transport companies, aircraft
manufacturers and non-U.S. airlines.

Activities of ARINC include the operation of an extensive system of domestic and overseas
aeronautical land radio stations, the fulfillment of systems requirements to accomplish ground and
airborne compatibility, the allocation and assignment of frequencies to meet those needs, the
coordination incident to standard airborne compatibility, the allocation and assignment of frequencies
to meet those needs, the coordination incident to standard airborne communications and electronics
systems and the exchange of technical information. ARINC sponsors the Airlines Electronic
Engineering Committee (AEEC), composed of airline technical personnel. The AEEC formulates
standards for electronic equipment and systems for the airlines. The establishment of Equipment
Characteristics is a principal function of this Committee.

It is desirable to reference certain general ARINC Specifications or Report which are

applicable to more than one type of equipment. These general Specifications and Reports may be
considered as supplementary to the Equipment Characteristics in which they are referenced. They are
intended to set forth the desires of the airlines pertaining to components and general design,
construction and test criteria, in order to insure satisfactory operation and the necessary
interchangeability in airline service. The release of a Specification or Equipment Characteristics
should not be construed to obligate ARINC or any airline insofar as the purchase of any components or
equipment is concerned.

An ARINC Report ( Specification or Characteristic) has a twofold purpose, which is:

(1) To indicate to the prospective manufacturers of airline electronic equipment the

considered opinion of the airline technical people, coordinated on an industry basis,
concerning requisites of new equipment, and

(2) To channel new equipment designs in a direction which can result in the maximum
possible standardization of those physical and electrical characteristics which influence
interchangeability of equipment without seriously hampering engineering initiative.

ii
 ARINC SPECIFICATION 429 PART 3
TABLE OF CONTENTS
ITEM SUBJECT PAGE

1.0 INTRODUCTION 1
1.1 Purpose of this Document 1
1.2 Organization of ARINC Specification 429 1
1.3 Development of Data Transfer 1
1.3.1 File Data Transfer Techniques - Basic Philosophy 1
1.3.2 Data Transfer 1
1.3.3 Broadcast Data 1
1.3.4 File Data Transfer 1
1.3.5 Transmission Order 2
1.3.5.1 Data Bit Encoding Logic 2
1.3.6 Bit-Oriented Protocol Determination 2
1.4 Relationship to Other Standards 2
2.0 BIT ORIENTED FILE TRANSFER PROTOCOL 3
2.1 - 2.4 Not used to maintain consistency with previous versions of 3
ARINC Specification 429
2.5 Bit-Oriented Communications Protocol 3
2.5.1 Link Data Units (LDU) 4
2.5.2 Link Data Unit (LDU) Size and Word Count 4
2.5.3 System Address Labels (SALs) 4
2.5.4 Bit Rate and Word Timing 4
2.5.5 Word Type 5
2.5.6 Protocol Words 5
2.5.6.1 Protocol Identifier 5
2.5.6.2 Destination Code 5
2.5.6.3 Word Count 5
2.5.7 Request To Send (RTS) 5
2.5.7.1 Clear To Send (CTS) 5
2.5.7.2 Not Clear To Send (NCTS) 5
2.5.7.3 Destination Busy (BUSY) 6
2.5.7.4 No Response to RTS 6
2.5.8 Conflicting RTS Transmissions 6
2.5.8.1 Half Duplex Mode 6
2.5.8.2 Full Duplex Mode 7
2.5.9 Unexpected RTS 7
2.5.10 Start Of Transmission (SOT) 7
2.5.10.1 General Format Identifier (GFI) 7
2.5.10.2 File Sequence Number 7
2.5.10.3 LDU Sequence Number 7
2.5.11 Data 7
2.5.11.1 Full Data Word(s) 7
2.5.11.2 Partial Data Word(s) 8
2.5.12 End of Transmission (EOT) 8
2.5.12.1 CRC Encoding 8
2.5.12.2 CRC Decoding 8
2.5.13 Negative Acknowledgment (NAK) 9
2.5.13.1 Missing SOT Word 9
2.5.13.2 Missing EOT Word 9
2.5.13.3 Parity Errors 9
2.5.13.4 Word Count Errors 9
2.5.13.5 CRC Errors 9
2.5.13.6 Time Out Errors 9
2.5.14 LDU Transfer Acknowledgment (ACK) 9
2.5.14.1 Duplicate LDU 9
2.5.14.2 Auto-Synchronized Files 9
2.5.14.3 Incomplete File timer 10
2.5.15 SYN Word 10
2.5.16 Response to ACK/NAK/SYN 10
2.5.17 Solo Word (Single Word Transfers) 10
2.5.17.1 Test Word and Loop Word 11
2.5.17.2 Optional Solo Word Definitions 11
2.5.18 Optional End-To-End Message Verification 11
2.5.19 Protocol Initialization 11
2.5.19.1 Bit-Oriented Protocol Version 11
2.5.19.1.1 ALOHA 11

iii
 ARINC SPECIFICATION 429 PART 3
TABLE OF CONTENTS

ITEM SUBJECT PAGE

2.5.19.1.2 ALOHA Response 12
2.5.19.2 Williamsburg/File Transfer Determination 12
2.6 Windowed Bit-Oriented Communications Protocol 13

3.0 BIT ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL 14

3.1 Bit Oriented Media Access Control (MAC) Protocol 14
3.1.1 Introduction 14
3.1.2 Relationship Between the Version 1 and Version 3 Protocols 14
3.1.3 Protocol Architecture 15
3.1.4 Buffering 15
3.2 Media Access Control (MAC) Sublayer 15
3.2.1 MAC Sublayer Service Specification 15
3.2.2 MA DATA request 16
3.2.2.1 Function 16
3.2.2.2 Semantics 16
3.2.2.2.1 destination MA address 16
3.2.2.2.2 destination SAL address 16
3.2.2.2.3 m sdu 16
3.2.2.2.4 service class 16
3.2.2.3 When Generated 17
3.2.2.4 Effect of Receipt 17
3.2.3 MA DATA.indication 17
3.2.3.1 Function 17
3.2.3.2 Semantics 17
3.2.3.2.1 destination MA address 17
3.2.3.2.2 destination SAL address 17
3.2.3.2.3 source MA address 17
3.2.3.2.4 source SAL address 17
3.2.3.2.5 m sdu 17
3.2.3.2.6 reception status 17
3.2.3.2.7 service class 17
3.2.3.3 When Generated 18
3.2.3.4 Effect of Receipt 18
3.2.4 MAC Control functions 18
3.2.4.1 MA CONTROL.request 18
3.2.4.2 MA CONTROL.indication 19
3.3 MAC Frame Structures 19
3.3.1 Information Frame Format 19
3.3.1.1 Address fields 19
3.3.1.2 Length/Type Field 19
3.3.1.2.1 Length 19
3.3.1.2.2 Type 20
3.3.1.3 Data Field 20
3.3.1.4 Frame Check Sequence (FCS) Field 20
3.3.1.5 Validation of Information Frame 20
3.3.1.5.1 Invalid Address 20
3.3.1.5.2 Invalid Length/Type 20
3.3.1.5.3 Invalid FCS 20
3.3.2 Command Frame Format 20
3.3.2.1 GFI Field 20
3.3.2.2 Command Type Field 21
3.3.2.3 Data Field 21
3.3.2.4 Frame Check Sequence (FCS) Field 21
3.3.2.5 Validation of Command Frame 21
3.3.2.5.1 Invalid FCS 21
3.4 MAC Transmit/Receive Functions 21
3.4.1 Frame Data Unit (FDU) 21
3.4.2 Frame Data Unit (FDU) Size and Word Count 21
3.4.3 System Address Labels (SALs) 21
3.4.4 Bit Rate and Word Timing 22
3.4.5 Word Type 22
3.4.6 Start of Frame (SOF) 22
3.4.6.1 Information/Command (I/C) Frame Field 22
3.4.6.2 Information SOF word 22

iv
 ARINC SPECIFICATION 429 PART 3
TABLE OF CONTENTS
ITEM SUBJECT PAGE

3.4.6.2.1 Word Count 22

3.4.6.2.2 Reserved Bits 22
3.4.6.3 Command SOF word 22
3.4.6.3.1 Word Count 22
3.4.6.3.2 Reserved Bits 22
3.4.6.3.3 General Format Identifier Field (GFI) 22
3.4.6.3.4 Command Type Field (CT) 22
3.4.7 Data 23
3.4.7.1 Full Data Word(s) 23
3.4.7.2 Partial Data Word(s) 23
3.4.7.3 SOLO Words 23
3.4.8 End of Frame (EOF) 23
3.4.9 Frame Check Sequence 23
3.4.9.1 32-Bit CRC Encoding 24
3.4.9.2 32-Bit CRC Decoding 24
3.4.10 Incomplete FDU Timer 24
3.4.11 ALOHA 24
3.4.12 Validation of FDUs 25
3.4.12.1 Missing SOF Word 25
3.4.12.2 Missing EOF Word(s) 25
3.4.12.3 Parity Errors 25
3.4.12.4 Word Count Errors 25
3.4.12.5 CRC Errors 25
3.4.13 Inter-FDU Gap Time 26
ATTACHMENTS

1-9 Numbers not used in Part 3 of Specification 429 27

10 Variables of Bit-Oriented Protocol 28
11 Bit-Oriented Data File Transfer Word Formats 35
11A Destination Codes 41
11B Status Codes 43
11C ALOHA/ALOHA Response Protocol Word Definition 44
12 Version 1 File Transfer Example 45
12A Field Mapping Example 46
13 Protocol Determination Procedure Diagrams 47
13A ALOHA Version Determination Sequence 49
14 System Address Labels 50
15 Deleted by Supplement 16 51
16 Deleted by Supplement 16 52
17 Flow Diagram Used to Determine Character-Oriented vs Bit-Oriented Protocol 53
18 MAC Sublayer Support Diagrams 54
19 Command Frame Data Unit (FDU) Structure and Examples 56
20 Information Frame Data Unit (FDU) Structure and Example 58

APPENDICES
A-E Letters not used in Part 3 of Specification 429 60
F Former AIM and File Data Transfer Techniques 61
G Mathematical Example of CRC Encoding/Decoding 67
H Interoperability of Bit-Oriented Link Layer Protocol 71
I SDL Diagrams of the Version 1 Williamsburg Protocol 72
J Protocol Structure 90
K Glossary & Acronyms 93

v

1.0 INTRODUCTION
1.1 Purpose of this Document
This document defines the air transport industry’s standards
for the transfer of aperiodic digital data between avionics
systems elements. Adherence to these standards is desired
for all inter-systems communications in which the system
line replaceable units are defined as “unit interchangeable”
in the relevant ARINC equipment Characteristics. Their use
for intra-system communications in systems in which the
line replaceable units are defined in the ARINC equipment
Characteristics as “system interchangeable” is not essential,
although it may be convenient.
1.2 Organization of ARINC Specification 429
The original release of ARINC Specification 429 was
published in its entirety as one document in 1977. Through
the years as the Specification grew in content, the physical
size grew proportionately. As a result, the effort involved
with locating specific data became increasingly difficult.
The solution, concurrent with the publication of Supplement
c-15 15, was to divide Specification 429 into three parts. Part 1
addresses the physical parameters (wiring, voltage levels,
coding, etc.) and label assignments. Part 2 provides the
formats of words with discrete bit encoding. Part 3 defines
file data transfer protocols.
Parts 1, 2, and 3 are being published separately beginning
with the updates provided by Supplement 15. In the future,
updates to the individual Parts of ARINC Specification 429
will be accomplished by independent Supplements starting
with Supplement 16. Each Part will be updated via
Supplement as the need dictates. Therefore the “dash
numbers,” i.e. -16, -17, etc. may not necessarily be
concurrent for all three parts of Specification 429.
The descriptive material for the changes introduced by the
Supplement 1-14 are provided in Part 1. Part 3 contains
Supplements 12 and above. The new bit-oriented protocol
was introduced by Supplement 12. The description of
changes introduced by Supplements 15 and later for each
Part are contained within the respective Parts of the
document.
1.3 Development of File Data Transfer
ARINC Specification 429, “Mark 33 Digital Information
Transfer System (DITS)” was adopted by AEEC in July
1977. Specification 429 defined a broadcast data bus.
General provisions were made for file data transfer. In
October 1989, AEEC updated a file data transfer procedure
with a more comprehensive process that will support the
transfer of both bit and character-oriented data.
COMMENTARY
c-16 The ACARS character protocol is defined in ARINC
Specification 619.
COMMENTARY
c-15 The desire for exchanging binary data via ACARS was
instrumental in initiating the development of a
ARINC SPECIFICATION 429 PART 3 - Page 1
more sophisticated file transfer protocol. The
fundamental concept was developed at a joint Satellite
and ACARS Protocol Working Group meeting held in c-15
February 1988 in Williamsburg, Virginia. The new
protocol became known popularly as the
“Williamsburg Protocol.”
1.3.1 File Data Transfer Techniques
- Basic Philosophy
This “File Data Transfer Techniques” specification
describes a system in which an LRU may generate binary
extended length messages “on demand.” Data is sent in the
form of Link Data Units (LDU) organized in 8-bit octets.
System Address Labels (SAL) are used to identify the
recipient. Two data bus speeds are supported.
1.3.2 Data Transfer
The same principles of the physical layer implementation
described in Part 1 to ARINC Specification 429, c-16
“Functional Description and Word Formats,” apply to File
Data Transfer. Any avionics system element having
information to transmit does so from a designated output
port over a single twisted and shielded pair of wires to all
other system elements having need of that information.
Unlike the simple broadcast protocol that can deliver data to
multiple recipients in a single transmission, the File
Transfer technique can be used only for point-to-point
message delivery.
1.3.3 Broadcast Data
The same simple “broadcast” transmission technique c-15
defined in ARINC Specification 429 Parts 1 and 2 may be
supported concurrently with the use of aperiodic File Data
Transfer.
1.3.4 File Data Transfer
When Specification 429 was adopted in 1977, provisions
were made for a character-oriented file data transfer
protocol. This definition was used as guidance for the
character-oriented file transfer protocol descriptions
incorporated into many ARINC equipment characteristics.
In 1989, a new protocol was developed that expanded the c-16
capability of file data protocol to support the transfer of bit-
oriented information. The original description of file data
transfer was declared obsolete; a copy, as a historical
record, is retained in Appendix F. The ACARS character
oriented file transfer protocol which was derived from the
material in Appendix F is documented in ARINC
Specification 619.
The protocol defined in this document is preferred for new
applications. The purpose of this bit-oriented
communications protocol is to provide for the transparent c-13
transfer of data files using the physical layer data bus
defined by Specification 429, Part 1.
COMMENTARY
The data transparent protocol described in Section 2.5 was c-15
developed in order to facilitate the communications of the
ACARS Management Unit (MU) and the Satellite Data
Unit (SDU). Its viability as a universal protocol was
 ARINC SPECIFICATION 429 PART 3 - Page 2
1.0 INTRODUCTION

1.3.4 File Data Transfer (cont’d) information to ensure that the desired section will be
located.
COMMENTARY (cont’d)
Documents referenced in this document include: c-17
recognized by the Systems Architecture and
c-15 Interfaces(SAI) Subcommittee which recommended its IEEE Standard 802.3, 1998 Edition, “Carrier Sense
inclusion herein as the standard means of file data Multiple Access with Collision Detection (CSMA/CD)
transfer. Access Method and Physical Layer Specifications”
The process for determining the protocol (character-
oriented as defined in ARINC Specification 619, or bit-
oriented) to be used in the interaction between two units,
where this information is not pre-determined is described in
Section 2.5.19.

1.3.5 Transmission Order

c-17 The most significant octet of the file and least significant bit
(LSB) of each octet should be transmitted first. The label is
transmitted ahead of the data in each case. It may be noted
that the Label field is encoded in reverse order, i.e., the least
significant bit of the word is the most significant bit of the
label. This “reversed label” characteristic is a legacy from
past systems in which the octal coding of the label field was,
apparently, of no significance.
1.3.5.1 Data Bit Encoding Logic

A “HI” state after the beginning of the bit interval returning

to a “NULL” state before the end of the same bit interval
signifies a logic “one.”

A “LO” state after the beginning of the bit interval returning

to a “NULL” state before the end of the same bit interval
signifies a logic “zero.” This is represented graphically in
ARINC Specification 429, Part 1 Attachment 7.
1.3.6 Bit-Oriented Protocol Determination
An LRU will require logic to determine which protocol
c-16 (character or bit-oriented) and which version to use when
prior knowledge is not available. See Section 2.5.19.1 for
bit protocol version determination.

1.4 Relationship to Other Standards

This document defines an onboard data link protocol to be
used for file data transfer between cooperating Line
Replaceable Units (LRU). As an onboard data bus, this
standard is often included in AEEC equipment standards
(ARINC 700 series) by reference.
Conversely, this Specification also references other
c-17 documents. For example, Version 3 of the file transfer
protocol, defined in Chapter 3 herein, utilizes many of the
principles of the IEEE communications standard 802.3.
Appropriately, there are numerous references to that
standard. IEEE 802.3, 1998 was current when the
definition of Version 3 was completed. Since the IEEE
standard may evolve over time, a generic (non-time dated)
reference (i.e., IEEE 802.3) is used wherever possible to
enable the reference within this document to remain
current, to the maximum extent possible, without future
Supplements. Exceptions to this practice include
references to specific clauses or paragraphs of IEEE
802.3, 1998. These references are not intended to limit the
growth or evolution of these provisions, but rather to
ensure that the reader is equipped with sufficient

2.0 BIT-ORIENTED FILE TRANSFER PROTOCOL
2.1 This Section number is not used in Part 3 to maintain
consistency with previous versions of ARINC Specification
429.
2.2 This Section number is not used in Part 3 to maintain
consistency with previous versions of ARINC Specification
429.
2.3 This Section number is not used in Part 3 to maintain
consistency with previous versions of ARINC Specification
429.
2.4 This Section number is not used in Part 3 to maintain
consistency with previous versions of ARINC Specification
429.
2.5 Bit-Oriented Communications Protocol
This section describes Version 1 of the bit-oriented
(Williamsburg) protocol and message exchange procedures
for file data transfer between units desiring to exchange bit-
oriented data assembled in data files. This protocol should
be used in lieu of the character-oriented file data transfer
defined in ARINC Specification 619. All other bus activity
c-13 remains unchanged. The bit-oriented protocol is designed to
accommodate data transfer between sending and receiving
units in a form compatible with the Open Systems
Interconnect (OSI) model developed by the International
Standards Organization (ISO). This document directs itself
to an implementation of the Link layer, however, an
overview of the first four layers (Physical, Link, Network
and Transport) is provided.
Communications will permit the intermixing of bit-oriented
file transfer data words (which contain System Address
Labels (SALs)) with conventional data words (which
contain label codes). If the sink should receive a
conventional data word during the process of accepting a
bit-oriented file transfer message, the sink should accept the
conventional data word and resume processing of the
incoming file transfer message.
The process for determining the protocol (character-
oriented or bit-oriented) to be used in the interaction
between two units, where this information is not pre-
determined is described in Section 2.5.19. The definition of
c-12 the protocol words used to determine the type of protocol is
contained in Table 11-4 of Attachment 11.
A table illustrating the bit-oriented file transfer word
formats is shown in Attachment 11.
The description provided in the following subsections
contains references to options which may be exercised and
timing values which may be selected for each individual
system for which this protocol is chosen. The options are
designated with an “O” and a sequence number, e.g., O5.
The timing values are designated with a “T” and a sequence
number, e.g., T2. See Attachment 10 for tables containing
standard options, events, applications and timers.
ARINC SPECIFICATION 429 PART 3 - Page 3
COMMENTARY
There is no protocol to support negotiation of the
parameters, and options such as those defined in c-12
Attachment 10.
The data file and associated protocol control information
are encoded into 32-bit words and transmitted over the
physical interface as described in Part 1 of Specification
429. At the Link layer, data is transferred using a data
transparent bit-oriented data file transfer protocol designed
to permit the units involved to send and receive information c-16
in multiple word frames. It is structured to allow the
transmission of any binary data organized into a data file
composed of octets. Examples of file transfer and field
mapping are given in Attachments 12 and 12A respectively.
The bit-oriented protocol will support either full or half
duplex operation (O1).
A. Physical Medium
The physical interface should be as described in Part 1 of
Specification 429.
B. Physical Layer
The Physical layer provides the functions necessary to
activate, maintain and release the physical link which will c-12
carry the bit stream of the communication. The electrical
interface, voltage, timing, etc. described in Part 1 of
Specification 429 should be used by the interfacing units.
Data words will contain 32 bits; bits 1-8 will contain the
System Address Label (SAL) and bit 32 will be the parity
(odd) bit.
C. Link Layer
The Link layer is responsible for transferring information
from one logical network entity to another and for
enunciating any errors encountered during transmission.
The Link layer provides a highly reliable virtual channel
and some flow control mechanisms.
D. Network Layer
It is the responsibility of the Network layer to ensure that
data packets are properly routed between any two terminals. c-13
The Network layer performs a number of functions. The
Network layer expects the Link layer to supply data from
correctly received frames.
COMMENTARY
The Network layer provides for the decoding of
information up to the packet level in order to determine
which node (unit) the message should be transferred to.
To obtain interoperability, this process, though simple
in this application, must be reproduced using the same c-14
set of rules throughout all the communications
networks (and their subnetworks) on-board the aircraft
and on the ground.
The bit-oriented data link protocol was designed to operate
in a bit-oriented Network layer environment. Specifically,
the Data Link Subcommittee expects that ISO 8208 will be c-13
selected as the Subnetwork layer protocol for air/ground
 ARINC SPECIFICATION 429 PART 3 - Page 4
2.0 BIT-ORIENTED FILE TRANSFER PROTOCOL
2.5 Bit-Oriented Communications Protocol (cont’d)
subnetworks. There are, however, some applications where
c-13 the bit-oriented file transfer protocol will be used under
other Network layer protocols.
E. Transport Layer
The Transport layer controls the transportation of data
between a source end-system to a destination end-system. It
provides “network independent” data delivery between
c-12 these processing end-systems. It is the highest order of
function involved in moving data between systems. It
relieves higher layers from any concern with the pure
transportation of information between them.
2.5.1 Link Data Units (LDU)
A Link Data Unit (LDU) contains binary encoded octets.
The octets may be set to any possible binary value. The
LDU may represent raw data, character data, bit-oriented
messages, character-oriented messages, or any string of bits
desired. The only restriction is that the bits be organized
into full 8-bit octets. The interpretation of those bits is not a
part of this Link layer protocol. The LDUs are assembled to
make up a data file.
c-16 LDUs consist of a set of contiguous ARINC 429 32-bit data
words, each containing the System Address Label (see
Section 2.5.3) of the sink. The initial data word of each
LDU is a Start of Transmission (SOT) as described in
Section 2.5.10. The data described above is contained
within the data words which follow (See Section 2.5.11).
The LDU is concluded with an End of Transmission (EOT)
data word (see Section 2.5.12). No data file should exceed
255 LDUs.
Within the context of this document, LDUs correspond to
frames and files correspond to packets, as defined in
Section 2.5.
2.5.2 Link Data Unit (LDU) Size and Word Count
The Link Data Unit (LDU) may vary in size from 3 to 255
c-12 ARINC 429 words including the SOT and EOT words.
When a LDU is organized for transmission, the total
number of ARINC 429 words to be sent (word count) is
calculated. The word count is the sum of the SOT word, the
data words in the LDU and the EOT word.
In order to obtain maximum system efficiency, the data
should be encoded into the minimum number of LDUs.
COMMENTARY
The word count field is 8 bits in length. Thus the
maximum number of ARINC 429 words which can be
counted in this field is 255. The word count field
c-13 appears in the RTS and CTS data words. The number
of LDUs needed to transfer a specific data file will
depend upon the method used to encode the data
words.
2.5.3 System Address Labels (SALs)
LDUs are sent point-to-point, even though other systems
may be connected and listening to the output of a
transmitting system. In order to identify the intended
recipient of a transmission, the Label field (bits 1-8) is used
to carry a System Address Label (SAL). Each on-board
system is assigned a SAL as shown in ARINC Specification
429, Part 1, Attachment 14. When a system sends an LDU
to another system, the sending system (the “source”) c-13
addresses each ARINC 429 word to the receiving system
(the “sink”) by setting the Label field to the SAL of the
sink. When a system receives any data containing its SAL
that is not sent through the established conventions of this
protocol, the data received should be ignored.
COMMENTARY
In the data transparent protocol, data files are identified
by content rather than by ARINC 429 label. Thus, the c-16
label field loses the function of parameter identification
available in broadcast communications.
2.5.4 Bit Rate and Word Timing
Data transfer may operate at either high speed or low speed
(O2) as defined in Part 1 of Specification 429. The source
should introduce a gap between the end of each ARINC 429
word transmitted and the beginning of the next. The gap
should be 4 bit times (minimum). The sink should be
capable of receiving the LDU with the minimum word gap
of 4 bit times between words. The source should not exceed
a maximum average of 64 bit times between data words of
an LDU.
COMMENTARY
The maximum average word gap is intended to compel c-14
the source to transmit successive data words of an LDU
without excessive delay. This provision prevents a
source that is transmitting a short message from using
the full available LDU transfer time (T9). The primary
value of this provision is realized when assessing a
maximum LDU transfer time for short fixed-length
LDUs, such as for Automatic Dependence Surveillance
(ADS).
If a Williamsburg source device were to synchronously
transmit long length or full LDUs over a single ARINC
429 data bus to several sink devices, the source may
not be able to transmit the data words for a given LDU
at a rate fast enough to satisfy this requirement because
of other bus activity. In aircraft operation, given the
asynchronous burst mode nature of Williamsburg LDU
transmissions, it is extremely unlikely that a
Williamsburg source would synchronously begin
sending a long length or full LDU to more than two
Williamsburg sink devices. Although, a laboratory c-16
condition could be designed to test a Williamsburg
transmitter which would likely result in the
transmitter’s failure to meet the maximum word gap
requirement, this test should be disregarded. A failure
to meet this requirement will either result in a
successful (but slower) LDU transfer, or an LDU
retransmission due to an LDU transfer timeout.

2.0 BIT-ORIENTED FILE TRANSFER PROTOCOL
2.5.5 Word Type
The Word Type Field occupies bit 31-29 in all bit-oriented
LDU words. See Table 11-1A of Attachment 11 for a
description of the Word Type field. The Word Type field is
used to identify the function of each ARINC 429 data word
used by the bit-oriented communication protocol.
2.5.6 Protocol Words
The protocol words are identified with a Word Type field of
“100” and are used to control the file transfer process.
2.5.6.1 Protocol Identifier
c-14 The protocol identifier field occupies bits 28-25 of the
protocol word and identifies the type of protocol word
being transmitted. Table 11-4 of Attachment 11 contains the
different protocol words and their formats.
Protocol words with an invalid protocol identifier field
should be ignored.
2.5.6.2 Destination Code
c-16 Some protocol words contain a Destination Code. The
c-18 Destination Code field (bits 24-17) typically indicates the
final destination of the LDU (O10). If the LDU is intended
for the use of the system receiving the message, the
c-16 destination code may be set to null (hex 00). However, if
the LDU is a message intended to be passed on to another
on-board system, the Destination Code should indicate the
system to which the message is to be passed. Some
interfaces (e.g., between an ARINC 758 CMU and a multi-
c-18 bearer-system ARINC 761 SDU) use the “Destination”
code to select a specific bearer system to be used for a
downlink message, and to indicate the specific bearer
system used for an uplink message. The Destination Codes
c-16 are assigned according to the applications involved as
shown in Attachment 11A.
In an OSI environment, the Link layer protocol is not
responsible for validating the destination code. It is the
c-14 responsibility of the higher level entities to detect invalid
destination codes and to initiate error logging and recovery.
COMMENTARY
Within the pre-OSI environment, the Destination Code
provides Network layer information. In the OSI
environment, this field may contain the same
information for routing purposes between OSI and non-
OSI systems.
2.5.6.3 Word Count
Some protocol words contain a Word Count field. The
Word Count field (bits 16-9) reflects the number of ARINC
429 words to be transmitted in the subsequent LDU. The
maximum word count value is 255 ARINC 429 words and
the minimum word count value is 3 ARINC 429 words. A
LDU with the minimum word count value of 3 ARINC 429
words would contain a SOT word, one data word and an
EOT word. A LDU with the maximum word count value of
255 ARINC 429 words would contain a SOT word, 253
data words and an EOT word.
ARINC SPECIFICATION 429 PART 3 - Page 5
2.5.7 Request To Send (RTS)
When an on-board system needs to send a LDU to another
on-board system, it will issue a Request To Send (RTS) to
that system. The RTS word contains a Destination Code
and a Word Count field.
When a system receives a RTS, it should send a response to
the source within T1 milliseconds. The response can be: (1)
Clear to Send, (2) Not Clear to Send or (3) Busy.
To be considered valid CTS, NCTS or BUSY data words
must have odd parity and contain the same destination code
as the corresponding RTS. A valid CTS must also contain
the same word count as the RTS.
2.5.7.1 Clear To Send (CTS)
When a system receives a valid RTS and is ready to accept
the LDU transfer, it should send a CTS word to the source
within T1 milliseconds. The CTS contains a Destination
Code (bits 24-17) and a Word Count field (bits 16-9). The
Destination Code in the CTS should contain the same
Destination Code as the RTS word (See Section 2.5.6.2).
The Word Count field should contain the same Word Count
value as the RTS word. If the source receives a CTS
containing a different Destination Code or Word Count
field value or a Word count field value equal to zero, it
should treat it as a valid Not Clear To Send. All of the RTS
counters (N1, N2, N3) will be reset after a valid CTS is
received.
c-14
2.5.7.2 Not Clear To Send (NCTS)
When a system either receives a valid RTS and is NOT
ready to accept the LDU transfer or receives an RTS with
an invalid destination or invalid word count, it should send
a Not Clear To Send (NCTS) to the source within T1
milliseconds. See Table 11-4 of Attachment 11 for the
format of the NCTS word. The NCTS word should contain
the same Destination Code as the RTS word and status code
(bits 16-9) as shown in Attachment 11B indicating the
reason for the busy response. If the NCTS received does not
contain the same Destination Code, then the source should
declare the NCTS to be invalid and ignore it. The status
codes are for engineering purposes only and should be
ignored by the system receiving the NCTS word.
Upon receipt of the NCTS word, the source should wait for
T2 milliseconds before repeating the RTS. The RTS may be
repeated T2 milliseconds after each NCTS until N1 requests
nominally have gone without receiving a valid CTS. The
actual number of attempts (N1) a system should make and
the action to be taken when the limit is exceeded depend on
the application (A1). The NCTS counter (N1) should be
reset upon valid (CTS) response to the RTS.
After sending a NCTS, the sink may optionally choose (O3)
to send a CTS with the requested Destination Code and
Word Count automatically as soon as it is ready to
 ARINC SPECIFICATION 429 PART 3 - Page 6
2.0 BIT-ORIENTED FILE TRANSFER PROTOCOL
2.5.7.2 Not Clear To Send (NCTS) (cont’d)
accept the file transfer, without waiting for another RTS.
The source may optionally choose (O4) to accept such a
CTS. Alternatively, the source may ignore the CTS with the
requested Destination Code and Word Count and repeat its
RTS.
COMMENTARY
If the word count and/or destination fields in the
received RTS word are not valid by virtue of illegal or
unsupported values, the sink should respond with the
NCTS word using an optional status code identifying
the condition. Some original implementations simply
ignored an invalid RTS word. However, the preference
is to respond with a NCTS.
2.5.7.3 Destination Busy (BUSY)
When a system receives a valid RTS and is not able to
accept an LDU within a timely manner, the receiving
c-14 system may optionally send a BUSY response to the source
within T3 milliseconds. See Table 11-4 of Attachment 11
for the format of the BUSY data word. The BUSY word
should contain the same Destination Code as the RTS word
and a status code (bits 16-9) as shown in Attachment 11B
indicating the reason for the busy response. If the BUSY
received does not contain the same Destination Code, then
the source should declare the BUSY to be invalid and
ignore it. The status codes are for engineering purposes only
and should be ignored by the system receiving the BUSY
word.
COMMENTARY
A timely manner refers to the interval defined by the
NCTS retry sequence.
Upon receipt of the BUSY word, the source should wait for
T4 seconds before repeating the RTS. The RTS may be
repeated every T4 seconds for as many times as the
application requires up to a maximum of N2 . Each new
attempt could possibly consist of several RTS
transmissions. Note that the busy condition could last for
hours, depending on the nature of the application and the
buffering capacity of the sink. The action taken following
T4 - N2 time out depends upon the application (A2). The
application requirements may supersede the value of N2
defined in Attachment 10. The Busy counter (N2) should be
reset upon valid (CTS) response to the RTS.
After sending a BUSY, the sink may optionally choose (O3)
to send a CTS with the requested Destination Code and
Word Count automatically as soon as it is ready to accept
the file transfer, without waiting for another RTS. The
source may optionally choose (O4) to accept such a CTS.
Alternatively, the source may ignore the CTS with the
requested Destination Code and Word Count and repeat the
RTS.
When expedited file transfers are desired between 2 BOP
c-16 devices, the sink device should support Option 3 (Send
Auto CTS) and the source device should support Option 4
(Accept Auto CTS).
COMMENTARY
If Option 3 (Send Auto CTS) and Option 4 (Accept
Auto CTS) cannot be supported between two devices
where expedited file transfers are necessary, an
alternative approach is to reduce the BUSY Retry
Timer (T4) and increase the BUSY counter (N2) c-16
accordingly to make the T4N2 timeout period identical
to the existing T4N2 value. The recommended value for
low speed is T4=1.5 seconds and N2=200.
2.5.7.4 No Response to RTS
If the source receives no response to the RTS within T5
milliseconds, the request should be repeated. In the absence
of any valid response (such as CTS, NCTS, or BUSY), or
the absence of an unexpected RTS, the RTS should be
repeated every T5 milliseconds until at least N3 requests
have gone unanswered. Any response other than a valid
CTS, NCTS, BUSY, Aloha, or an unexpected RTS should
be ignored. The No response counter (N3) should be reset c-14
upon valid response to the RTS. All the RTS counters (N1,
N2, N3) will be reset after a valid CTS is received.
The actual number of attempts a source should make (N3)
before giving up, or taking some different course of action,
when the limit is exceeded depends on the application (A3).
The action to be taken is described in Table 10-2 of
Attachment 10 or in the applicable equipment characteristic.
2.5.8 Conflicting RTS Transmissions
2.5.8.1 Half Duplex Mode
When operating in half duplex mode, it is possible that two
systems might decide to send RTS messages to each other
at nearly the same time, causing each system to appear to
receive the other’s RTS in response to its own RTS. If this
occurs, each system should set a random timer to a time in
the range of zero to T6 milliseconds in increments of no
more than T7 milliseconds. If a system receives another c-12
RTS before this timer expires, that system will defer its own
need to transmit and will respond to the other system’s RTS
as defined in the preceding paragraphs. If no RTS is
received within the random time, the system should re-
transmit the RTS. If a conflicting RTS occurs again, the
same procedure will take effect for as many times as it takes
for one system to prevail over the other.
If this protocol is used in an environment that has well
defined priorities (O5), one system may be assigned priority
over another to resolve RTS conflicts without the random
retransmission procedure described above.
COMMENTARY
Typically, a well-defined priority in avionics gives an
RTS for uplinks priority over an RTS for downlinks. c-16

2.0 BIT-ORIENTED FILE TRANSFER PROTOCOL
2.5.8.2 Full Duplex Mode
When operating in a full duplex mode, both systems must
be capable of operating as a source and sink at the same
time. If both systems initiate an RTS, both should receive a
CTS and both should respond normally to the CTS. Neither
system should abort.
A conflicting RTS applies only to a receiving system that
has transmitted a CTS (in response to a RTS) and receives
another RTS. This RTS is treated simply as a retransmission
and the sink should retransmit a CTS.
2.5.9 Unexpected RTS
It is possible, that after sending a CTS word to a requesting
source, that the source does not receive the CTS and re-
transmits the RTS to the sink. Alternatively, a source may
experience a reset which causes a new RTS to be sent in the
middle of an LDU transfer. If, for any reason, the first word
c-13 received by a sink after having sent a CTS word is an RTS,
then the sink should transmit another CTS word. If a sink
receives another RTS after having sent a CTS, even in the
middle of receiving an LDU, the sink should discard any
partial LDU already received and respond as defined in
Section 2.5.7.1.
2.5.10 Start Of Transmission (SOT)
When a system receives a valid CTS with a Destination
Code and Word Count matching the Destination Code and
Word Count of the previous RTS, the system should
respond by sending the Start of Transmission (SOT) word
within T13 milliseconds, immediately followed by the data
words which constitute the LDU. See Table 11-6 of
Attachment 11 for a description of the SOT word format.
The SOT word contains the File Sequence Number in its
File Sequence Number field (bits 24-17). It also contains a
General Format Identifier (GFI) and a LDU Sequence
Number.
c-14
2.5.10.1 General Format Identifier (GFI)
The General Format Identifier (GFI) occupies bits 28-25 in
the SOT word. See Table 11-6A of Attachment 11 for a
description of the GFI field. The GFI is transparent to the
Link layer protocol. It is designated by a higher level entity
in the source device, to indicate to a higher level entity in
the sink, the format of the data words that follow. It is the
responsibility of the higher level entities to detect invalid
GFI designations and to initiate error logging and recovery.
COMMENTARY
Within the pre-OSI environment the GFI provides
c-14 Network layer function information. In the OSI
environment this field may contain the same
information for bridging purposes between the OSI and
non-OSI world.
A code of 1111 is used to indicate that an extended GFI of
c-12 8 bits will be found in the first data octet (Nibbles 1 and 2)
of the first data word in the file.
ARINC SPECIFICATION 429 PART 3 - Page 7
2.5.10.2 File Sequence Number
The File Sequence Number (bits 24-17) of the SOT word
contains an 8-bit number assigned to the file. It is initialized
to the hex value 00 and increments by 1 for each new file
that is sent over the ARINC 429 link. After reaching hex
FF, the File Sequence Number should start over at hex 01,
skipping zero. A file consisting of multiple LDUs will have
the same File Sequence Number in each of the SOT words
of each LDU.
2.5.10.3 LDU Sequence Number
The LDU Sequence Number (bits 16-9) of the SOT word
contains an 8-bit number assigned to the LDU. It is
initialized to the hex value 00 and increments by 1 for each
new LDU of the same file that is sent over the ARINC 429
link. The LDU Sequence Number should be reset to 00 at
the beginning of each new file.
2.5.11 Data
Data words immediately follow the SOT word. The octets
of the data file are encoded and transmitted in 32-bit data
words. There are two basic types of data words: full binary
and partial binary. Binary data words may contain one, two,
three, four and five semi-octets. A semi-octet (or nibble) is
half of an octet, or four bits in length. c-12
Binary data words of five semi-octets are called Full Data
words. Binary data words of fewer than five semi-octets are
called Partial Binary Data words.
A data file may be sent using any combination of full and
partial data words. There are no restrictions regarding the
particular type of data within a file. The formats of Data
words are illustrated in Attachment 11.
Each binary data file, prior to transmission, should conclude
(end) with a complete octet. Any incomplete final octet
should be completed with zeros before transmission. Each
LDU transmitted, should also end in a complete octet. If, at
the end of the transmission, the receiver determines that an
odd number of semi-octets has been received, that is, the
LDU ends with an incomplete octet, the receiver should
send a NAK or assume the upper 4 bits of the partial octet
to be zeros, and proceed normally.
2.5.11.1 Full Data Word(s)
A Full Data Word has 20 bits available for data. This space
is allocated in five semi-octets. The octets of the data file
are divided into two semi-octets and placed sequentially
into the data words. The least significant bit of the least
significant semi-octet is sent first. c-13
If, in the process of placing the octets into the data words,
an octet is split between two different words, the least
significant semi-octet goes in the last (n5) semi-octet of the
current data field and the most significant semi-octet
follows in the first (n1) semi-octet of the data field of the
next word. See Attachment 11 for data word formats.
 ARINC SPECIFICATION 429 PART 3 - Page 8
2.0 BIT-ORIENTED FILE TRANSFER PROTOCOL
2.5.11.1 Full Data Word(s) (cont’d)
If the end of the LDU does not completely fill the last Full
Data Word, a Partial Data Word (see Section 2.5.11.2)
should be used to complete the LDU transmission.
c-13 In order to obtain maximum system efficiency, Partial Data
Words should be used only when they are required to
complete the data for an LDU transmission. An LDU
should not be encoded as a string of Partial Data Words
where 8 or 16 bits of data are encoded for each ARINC 429
word used.
2.5.11.2 Partial Data Word(s)
A Partial Data Word contains from one to four semi-octets.
The number of semi-octets in a partial data word is
indicated in bits 28-25 of the word. Only full four-bit semi-
c-16 octets can be sent; one, two or three bits are invalid. Partial
Data Word semi-octets are sent in the same order as the
semi-octets in a full data word. The unused semi-octets in
the partial data word should be set to binary zeros.
2.5.12 End of Transmission (EOT)
Each LDU transfer is terminated by an End of Transmission
(EOT) word. See Table 11-7 of Attachment 11 for the
definition of this word. Table 11-7A of Attachment 11
contains the definition for bit 25 of the EOT word. This bit
c-14 is used to indicate if the LDU is the final LDU of the file
transfer. If the file transfer consists of a single LDU, bit 25
should be set to 1 to indicate that this is the final LDU. If N
LDUs are to be sent, then bit 25 of LDU 1 through LDU N-
1 should be set to 0 and bit 25 of LDU N should be set to 1.
The EOT word contains a Cyclic Redundancy Check or
CRC (bits 24-9).
COMMENTARY
The ARINC 429 data link is a twisted shielded pair of
wires which has been demonstrated to exhibit high
integrity and unlikely to introduce errors into the data
passing through it. Simple parametric data is usually
transmitted at a refresh rate high enough to permit
c-12 recognition and suppression of erroneous data. Since
the transfer of data using a file transfer protocol
contains no provision for automatic refresh, some
applications may require high data integrity to be
confirmed by an error checking mechanism. For this
reason, each LDU contains a CRC check. The use of
the CRC in this case does not imply any inherent lack
of integrity of the ARINC 429 link.
2.5.12.1 CRC Encoding
The CRC field is a 16 bit sequence with the most significant
bit (MSB) transmitted first. Determination and encoding of
the CRC is as follows:
c-12 The k bits of data in the LDU are represented as the
coefficients of the polynomial, G(x); where k is the number
of data bits in the LDU existing between, but not including,
the SOT and EOT words. For example, if the data stream is
101001, k=6 and G(X)=x5+ x3 + 1.
The CRC calculation is performed over the data octets only
of the LDU with any semi-octets zero filled.
There exists a generator polynomial which is of the form,
P(x) = x16 + x12 + x5 + 1
The CRC is then determined as the one’s complement of the
remainder, R(x), obtained from the modulo 2 division of:
x16G(x) + xk(x15+x14+x13+...+x2+x+1) = Q(x) + R(x)
P(x) P(x)
Note: The addition of xk(x15+x14+x13...+x2+x+1) to x16G(x)
(which is equivalent to inverting the first 16 bits of G(x) and
appending a bit string of 16 zeroes to the lower order end of
G(x)), corresponds to initializing the initial remainder to a
value of all “ones.” The complementing of R(x), by the
transmitter, at the completion of the division ensures that
the received, error-free message will result in a unique, non-
zero remainder at the receiver.
At the transmitter, the CRC is added to the x16G(x) product,
resulting in the message, M(x), of length n where:
n = k+16,
c-12
and M(x) = x16G(x) + R(x)
= x16G(x) + CRC
2.5.12.2 CRC Decoding
Decoding of the CRC at the receiver is as follows:
At the receiver, the incoming M(x) is multiplied by x16,
added to the product,
n
x (x15+x14+x13+...+x2+x+1)
and divided by P(x) as follows:
x16M(x)+xn(x15+x14+x13+...+x+1) = Qr(x) + Rr(x)
P(x) P(x)
If the transmission of the serial incoming bits plus CRC
(i.e., M(x)) is error free, then the remainder, Rr(x) will be
0001110100001111 (coefficients of x15 through x0,
respectively). A mathematical example of CRC encoding
and decoding can be found in Appendix G.
COMMENTARY
The notation used to describe the CRC is based on the
property of cyclic codes that a code vector such as
1000000100001 can be represented by a polynomial
G(x) = x12 + x5 + 1. The elements of an n element code
word are thus the coefficients of a polynomial of order
n - 1. In this application, these coefficients can have
the value 0 or 1 and all polynomial operations are
performed module 2. The polynomial representing the
data content (message) of an LDU is generated using
the LDU bit which is encoded in bit 9

2.0 BIT-ORIENTED FILE TRANSFER PROTOCOL
of the first data word as the coefficient of the highest
c-12 order term. A mathematical example of CRC encoding
and decoding can be found in Appendix G.
2.5.13 Negative Acknowledgment(NAK)
If the sink detects any of the errors described in the
following subsections, it sends a NAK to the source upon
detecting the error or within T8 milliseconds of receiving the
EOT word, whichever occurs first. See Table 11-4 of
Attachment 11 for a description of the NAK word format.
The NAK word should contain the same File Sequence
Number (bits 24-17) as the SOT word and a status code
c-14 (bits 16-9) as shown in Attachment 11B indicating the
reason for the NAK. The File Sequence Number and status
code are intended to be used for engineering purposes only
and should be ignored by the system receiving the NAK.
The sink should test for errors to determine if a NAK
should be sent. It is not necessary for the sink to be aware of
the type of error that occurred, as long as any of the errors
c-13 listed in the following subsections will elicit a NAK
response.
2.5.13.1 Missing SOT Word
Following reception of a valid CTS word, the source should
transmit the SOT word as the first word of the LDU as
specified in Section 2.5.10, Start of Transmission (SOT). If
c-12 the SOT word is not received as the first word of the LDU,
the sink should send the NAK response. See also Section
2.5.9.
2.5.13.2 Missing EOT Word
Following the transmission of the final data word of each
LDU, the source should transmit the EOT word as the final
word of the LDU as specified in Section 2.5.12, End of
Transmission (EOT). If the EOT word is not received as the
c-13 final word of the LDU within T9 seconds of the CTS, then
the sink should send the NAK response to the source within
T8 milliseconds after the T9 has expired.
2.5.13.3 Parity Errors
Bit 32 of each ARINC 429 word should be set to odd parity
for the entire word. Upon receipt of a word, the receiving
unit should verify that each word was received with odd
c-12 parity. If any word is received with even parity, the
receiving unit should take no action and ignore the word.
COMMENTARY
When the sink receives a word with bad parity, it
cannot be sure of the intended label. The word may not
even be a part of the LDU, so by ignoring the offending
word there may still be a chance of a successful file
c-12 transfer. If the offending word was intended to be a
part of the LDU, then when the EOT word is received,
the actual word count will not match the expected
count. The sink will either NAK the source when the
EOT word is received, or when it times out waiting for
the full expected number of words.
ARINC SPECIFICATION 429 PART 3 - Page 9
2.5.13.4 Word Count Errors
Upon receipt of the EOT word, the sink should verify that
the actual number of words received is the number of words
expected, per the RTS and CTS words. If the word counts c-14
do not match, the sink should send a NAK response to the
source.
2.5.13.5 CRC Errors
Upon receipt of the EOT word, the sink should verify the
CRC on the received LDU. If the 16-bit CRC is invalid, the c-13
sink should send the NAK response.
2.5.13.6 Time Out Errors
The sink will not time the gaps between the words received,
However, if the sink does not receive the complete LDU
transfer within T9 seconds of having sent the CTS, it should
send a NAK to the source and discard any partial LDU
received.
2.5.14 LDU Transfer Acknowledgment(ACK)
If all words of the LDU transfer are received within T9
seconds of the CTS, each with odd parity, and the word c-12
count and CRC verify, and the LDU is either the next LDU,
a duplicate LDU or the first LDU of a new file, then the
sink should send an acknowledgment(ACK) to the source
within T8 milliseconds of receiving the EOT word. See
Table 11-4 of Attachment 11 for a description of the ACK
word format. The ACK word should contain the File
Sequence Number (bits 24-17) and LDU sequence number
(bits 16-9) to indicate a successful LDU transfer.
2.5.14.1 Duplicate LDU
An LDU is determined to be a duplicate if its File Sequence
Number and LDU Sequence Number are not both zero, and
it’s SOT words are identical to those of the previously
received LDU. When a duplicate LDU is detected, the sink
should discard the LDU just received and acknowledge per
Section 2.5.14. c-16
COMMENTARY
Some implementations look at both SOT and EOT to
determine duplicate LDUs.
COMMENTARY
A File Sequence Number of zero along with an LDU
Sequence Number of zero should be interpreted as an
indication of a reset in the source and the LDU should
not be compared to the previous one.
2.5.14.2 Auto-Synchronized Files
c-12
When the File Sequence Number is different from the
previous LDU transfer and the LDU Sequence Number is
zero, then the sink discards any previously received partial
file, and accepts the LDU just received.
 ARINC SPECIFICATION 429 PART 3 - Page 10
2.0 BIT-ORIENTED FILE TRANSFER PROTOCOL
2.5.14.2 Auto-Synchronized Files (cont’d)
COMMENTARY
c-12
Some implementations do not support auto-
synchronized files.
2.5.14.3 Incomplete File Timer
The Incomplete File (T14) timer is used to insure that a
source device may not “lock-up” a sink with an incomplete
file.
For multiple-LDU files, the maximum time allowed from
transmission of the ACK or NAK for a previous LDU to the
reception of the next RTS should be T14 minutes. The sink
will start the T14 timer when it sends a NAK or when it
sends an ACK for each LDU of a file except the last LDU.
The T14 timer is stopped each time another valid RTS is
c-14 received. The T14 timer should also be stopped if the sink
discards the partial file for other reasons defined in this
specification. When T14 minutes is exceeded, the sink
should send the SYN word within T8 milliseconds and
discard any partial file already received.
For Half Duplex environments (i.e., Option O1 of Table 10-
3) this timer only applies when the device is operating as a
sink.
2.5.15 SYN Word
The SYN word is used by the sink to inform the source that
it (the sink) has become confused concerning the
construction of the file. A typical example is an
inappropriate or unexpected File/LDU Sequence Number in
the SOT word. See Table 11-4 of Attachment 11 for a
c-13 description of the SYN word format. Upon receipt of the
SOT word, the sink should verify the LDU Sequence
Number (bits 16-9).
COMMENTARY
If an SOT word of an LDU has the same File Sequence
Number and LDU Sequence Numbers as the previous
LDU, some implementations will interpret this as an
unexpected File/LDU Sequence Number instead of a
duplicate LDU.
If the LDU is not a duplicate and its LDU Sequence
c-16 Number is not the next in sequence (i.e., is not the next
LDU), and is not the first LDU of a new file, then the sink
should send the SYN response to the source within T8
milliseconds of receipt of the SOT word, or within T8
milliseconds of receipt of the EOT word when necessary to
determine a duplicate LDU, and discard any partial file
already received.
COMMENTARY
Some implementations look at both SOT and EOT
to determine duplicate LDUs.
The SYN word may be sent without timing constraint when
c-13 the received data words cannot be normally processed.
There is no acknowledgmentdefined for the source when a
SYN word is received. The action taken is specified in c-13
Section 2.5.16.
2.5.16 Response to ACK/NAK/SYN
The source should expect a response to the transmission c-14
within T16 of sending the EOT .
COMMENTARY
Timer T10 may apply instead of T16, for those devices
compliant with version “0000” or “0001” of this
protocol (Table 11-4A of Attachment 11). T10 is started c-13
after the CTS is received whereas time T16 is started
after the EOT word is transmitted.
If an ACK is received and the File Sequence Number and
LDU Sequence Number match the contents of the SOT
word, the source should consider the transfer successful. If
an ACK is received and the File Sequence Number and/or
the LDU Sequence Number do not match the SOT word, or
if a NAK is received or if no response is detected, the
source should repeat the entire LDU transmission process,
starting with the sending of the RTS word. If the source c-14
detects a SYN during the transmission process, it should
retransmit the entire file, if able, beginning with the first
LDU. The File Sequence Number contained within the
SYN word is provided for testing purposes and is not
evaluated by the source. If the source is not able to
retransmit or rebuild the entire file, that file is discarded and
the source proceeds normally with the first LDU of the next
file, when it is ready for transmission.
COMMENTARY
If end-to-end accountability is required, then either
upper layer OSI protocols or the application process
should provide this capability.
Each new attempt to re-transmit the LDU should start with
the necessary RTS transmissions in order to obtain a CTS
again. After receiving N4 consecutive NAK words, or after
receiving N5 consecutive SYN words, the file transfer
between the two systems should be considered failed.
2.5.17 Solo Word (Single Word Transfers)
If the data to be sent consists of 1 or 2 octets only, (e.g., a
button code from a CDU keyboard) then it is not necessary c-12
to obtain a CTS. In this case the data may be sent “in the
blind” using the Solo Word format (O8). The Solo Word
contains a 16-bit data field in bits 24-9 and a 4-bit identifier
in bits 28-25 to identify the nature of the data. For example,
the I.D. may indicate that the data is a key code from a
CDU or a status word. Codes 0000 and 0001 are reserved
for the TEST and LOOP words as defined in Section
2.5.17.1. All other codes are available for application use.
Solo Words are not acknowledged at the link level.
However, they may invoke a Solo Word or data file transfer
response as required by the application. Solo Words cannot
be interleaved with data file words during a data file
transfer. If error detection beyond parity is required, some
bits of the data field can be defined as check bits, to be
verified by the application.

2.0 BIT-ORIENTED FILE TRANSFER PROTOCOL
2.5.17.1 Test Word and Loop Word
The integrity of the ARINC 429 link between two units may
be tested. The test is initiated by the source sending the
Loop Test Pattern Word (TEST).
The TEST word contains a 16-bit binary pattern (bits 24-9)
chosen by the originator. The system receiving the TEST
Word should respond by sending a Loop Test Response
(LOOP) word containing the same 16-bit pattern (bits 24-9)
within T11 milliseconds.
COMMENTARY
The preferred reaction to a loop test failure has not
been defined.
2.5.17.2 Optional Solo Word Definitions
c-12 Each equipment utilizing this bit-oriented protocol may
define solo words as needed. See Table 11-5 of Attachment
11 for the format definition. These solo word definitions
should be unambiguous.
COMMENTARY
The same SOLO word ID coding may be
usedrepeatedly in different units as long as its meaning
remains unambiguous.
2.5.18 Optional End-To-End Message Verification
In some applications, an end-to-end integrity check is
desirable in order to validate the correct transfer of a data
file from the message source to its final destination. For
further information, the reader should refer to the applicable
ARINC Equipment Characteristic, e.g., ARINC
Characteristic 702, “Flight Management Computer
System.”
2.5.19 Protocol Initialization
The ALO word should be sent by any system which
supports the bit-oriented Link layer protocol just after the
system powers-up, or performs a re-initialization for any
reason.
c-14
A system which supports the bit-oriented Link layer
protocol should first determine if the interfacing device also
supports the bit-oriented protocol using the ALO/ALR
process described in Section 2.5.19.1. If the system is
bilingual and there is no response to the ALO/ALR process,
it may also determine if the interfacing device supports the
character-oriented protocol as described in Section 2.5.19.2.
A bilingual system should repeat the processes described in
c-16 Sections 2.5.19.1 and if applicable 2.5.19.2, until a common
protocol version is selected by both systems. Examples of
protocol initialization are given in Attachment 13.
COMMENTARY
c-14 In addition to a “power-reset” or a system “re-
initialization,” a device that supports the bit-oriented
ARINC SPECIFICATION 429 PART 3 - Page 11
protocol may at any time determine the ARINC 429 c-14
link status using the ALO/ALR process described in
Section 2.5.19.1 and Section 2.5.19.2.
2.5.19.1 Bit-Oriented Protocol Version
The ALO/ALR process is intended to be used when a
system needs to determine whether or not an interface
supports the bit-oriented protocol. To maintain c-16
interoperability, all systems which support the Link layer
Bit-Oriented Protocol must be able to respond to the
initialization of this process. Attachment 11, Table 11-4,
shows the ALO and ALR word formats.
When a system with a bit-oriented Link layer protocol has
the need to make this determination, it should construct the
ALO word and transmit this word to the device in question.
The system should then wait for a maximum period of time
defined by T12. If the device in question has not responded
within time T12, the initiating system should initiate another
ALO word and again delay up to T12. The initiating system
should attempt a maximum of N6 ALO word operations
before declaring the device in question as “Not bit-oriented”
or “Not able to respond.”
2.5.19.1.1 ALOHA
The first ALOHA word transmitted in a sequence should c-14
contain the highest Version Number supported by the
source device. If the ALOHA Response contains a version
that does not match the ALO version, the source device
should take one of the following actions:
a. If the source device is able to adapt to the differences in
protocol version, file transfers may proceed using the
protocol version identified in the ALR word.
b. If the source device is not able to adapt to the
differences in protocol version, the source should again
initiate the ALOHA word with the version field set to
the highest version supported by the source that is lower
than the version indicated in the previous ALR (see
examples identified in Attachment 13A).
The ALO/ALR protocol determination process should
continue until a common protocol version is found. If none
of the protocol versions match, the source should notify the
higher level entity of the communications failure and
continue the protocol determination process.
When the system only supports bit oriented protocols it
should repeat the process described in this section. When
the system also supports character oriented protocols then
the process defined in 2.5.19.2 should be followed. The c-16
protocol determination process will continue until a
common protocol is found. See Attachment 17.
The ALOHA word should contain a Subsystem SAL field
as shown in Attachment 11, Table 11-4. This field should
contain the SAL of the device sending the ALOHA word,
with bit 17 as the most significant bit and bit 24 as the least
significant bit of the Subsystem SAL.
 ARINC SPECIFICATION 429 PART 3 - Page 12
2.0 BIT-ORIENTED FILE TRANSFER PROTOCOL
2.5.19.1.2 ALOHA Response
A device that supports the bit-oriented Link layer protocol
should always be able to respond to the receipt of the ALO
word. Whenever a device receives the ALO word, it should
leave its present task and respond within T15 with an ALR
word.
The ALR response should reflect the device’s protocol
version level by way of the Version Number contained
within the ALR word. If the Version Number of the ALO
does not match the sink device’s protocol Version Number,
the sink device should select the next lowest version
supported (equal to or lower than the version indicated by
c-14 the previous ALO word) and indicate this new version in
the ALR word.
After the device has responded to the ALO word (with the
ALR), the device should take the following action:
If the device was in the sink mode (had already begun
receiving any LDU of a file), it should discard any partial
file it had received. Since the ALO represents a system “re-
initialization” (per Section 2.3), the source may reset the
File and LDU sequence numbers.
If the device was in the source mode (had already begun
transmitting any LDU or file), it should resend the entire file
beginning with the first LDU of the file.
If Option O12 is selected for a particular bit-oriented
protocol interface, the device receiving an ALOHA word
c-16 should use the Subsystem SAL from the ALOHA word as
the SAL of the ALOHA Response (ALR) word and for all
subsequent bit-oriented protocol transmissions for that
interface.
COMMENTARY
A bit-oriented Link layer protocol device receiving an
ALOHA word should take caution if utilizing the
Subsystem SAL field of the ALOHA word to
determine how to send the ALR reply. Previous
supplements of the bit-oriented Link layer protocol
defined the Subsystem SAL field as [TBD] bits, and as
such, some devices in service may have encoded non-
zero bits in this field. A receiving system should
therefore implement a reasonableness check to validate
c-16 that the data bits received in this field represent a SAL
associated with a known bit-oriented Link layer
protocol device. If a device receives an ALOHA word
containing a System SAL of all zeros or an unknown
SAL, and the ALOHA word is received on a data bus
that has a specific bit-oriented Link layer protocol
subsystem associated with it, it is recommended that
the ALR word be attempted using the SAL for that
specific subsystem, to ensure interoperability.
2.5.19.2 Williamsburg/File Transfer Determination
In some situations there may be a transition period from a
device using the character-oriented file transfer protocol
c-14 defined in ARINC Specification 619 to the same device
using the Williamsburg bit-oriented protocol introduced in
Supplement 12. In this situation, it is desirable to have an
“automatic” determination sequence which allows the
devices to adjust from the character-oriented to bit-oriented
protocol. Because of the environment in which these
devices are to operate, it is necessary to have a cyclic
process to establish the protocol to communicate with. An
attempt to establish contact using the bit-oriented ALO-
ALR words should be made to the point where the link is
considered to be failed or to be established.
If the link has been established, then normal bit-oriented
communications can be pursued. If the link is considered
failed, then an attempt to obtain a response to the character-
oriented RTS-CTS words should be made. The typical
repeat sequence for the character-oriented protocol is 3 tries
(See Attachment 13). If a character-oriented CTS, NCTS
(CTS 0), or BUSY (CTS Q) response is obtained, then the
link is considered established and normal character-oriented
communications can be pursued. If the character-oriented
protocol fails, then the cycle should be re-started using the
bit-oriented ALO sequence. There may be a period of c-14
inactivity between cyclic attempts of not more than 15
seconds. Attachment 17 contains an example diagram of
these determination sequences.
If a protocol has been established and the link fails because
of a loss of activity (if defined on that bus), or because of a
failure to deliver a message due to a no response, then the
protocol determination sequence should be started again. A
graphical representation of this is presented in Attachment
17.
COMMENTARY
This determination sequence is only necessary when
there is a possibility of having to support both the older
character-oriented protocol and the newer bit-oriented
protocol on the same ARINC 429 data bus.
COMMENTARY
During the protocol determination process, a bilingual
device should recognize protocol words using both the
bit-oriented (Williamsburg) and the character-oriented
formats. It is recommended that at least the ALOHA
word and the character-oriented RTS and NAK words
be recognized by the device capable of the automatic
protocol determination. This would minimize
synchronization problems between the two
communicating devices and allow the Link layer method
to be established in a timely manner.
COMMENTARY
c-16
When an LRU performs the character protocol
determination (RTS) it is initiating the sequence of
events for a file transfer, but it does not complete the file
transfer. Some LRUs will wait forever for the file
transfer to be completed unless the source sends a NAK
word to terminate the file transfer. Therefore, it is
recommended that protocol determination logic which
includes character protocol should transmit a character
oriented NAK word when a character oriented CTS
word is received in response to a character oriented RTS
word.
 ARINC SPECIFICATION 429 PART 3 - Page 13
2.0 BIT-ORIENTED FILE TRANSFER PROTOCOL

2.6 Windowed Bit-Oriented Communications Protocol

This section has been deleted.
c-16
Version 2 of the bit-oriented (Williamsburg) Protocol,
previously in this section, has been superseded by Version 3
of the bit-oriented (Williamsburg) Protocol defined in
Section 3.0 of this document.
 ARINC SPECIFICATION 429 PART 3 - Page 14
3.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL
3.1 Bit-Oriented Media Access Control (MAC) Protocol
3.1.1 Introduction
This section describes Version 3 of the bit-oriented
(Williamsburg) protocol. It is an IEEE 802 compliant MAC
protocol for frame oriented data transfer using the Data Link
layer.
Within the ISO/OSI Reference Model, the Data Link layer is
responsible for the logical connection between at least two
entities of the same Local Area Network (LAN). It interfaces
to the Network layer, which is responsible for the connection
between at least two networks, and the Physical layer, which is
responsible for the physical connection between adjacent
nodes, i.e. repeaters, bridges or computers. The Data Link
layer is further divided into two sublayers.
The Media Access Control (MAC) sublayer, which is a
Physical, layer dependent entity. The purpose of the MAC is
to provide a standard interface to the entities above it. The
MAC isolates the sublayer above it from the details of the
Physical layer. The ARINC 429 MAC is defined herein.
The Logical Link Control (LLC) sublayer is assumed by
c-17 IEEE/ISO as the second sublayer, which is a physically
independent control sublayer.
For further description of the OSI protocol layers please refer
to Section 2.5 of this document.
COMMENTARY
Generally, multiple MAC Service Clients (users)
interface with the MAC entity (MAC Service Provider).
In the IEEE/ISO set of standards the LLC is the most
prominent one. Additionally, the bridging function may
act as a MAC Service Client as well as a MAC Control
function. In the non-OSI world there are a variety of
different protocols that may or may not directly interface
with the MAC. Here, the most prominent one is Internet
Protocol (IP). LLC Service Providers are required for
some classes of IEEE 802.3 Local and Metropolitan Area
Networks, specifically where the MAC frame contains
insufficient information for protocol selection, or when
required by higher layer protocols (specifically OSI based
protocols such as ATN). This document follows the
guidance of IEEE 802.3 where the Length/Type field is
used to select between LLC as a MAC Client, and where
the Network Layer is selected as the MAC Client. The
selection of MAC Client (LLC or non-LLC frame format)
is mutually exclusive.
In order to make ARINC 429 compatible with standard
data buses adopted by the Institute of Electrical and
Electronics Engineers (IEEE) and the International
Organization for Standardization (ISO) it is paramount to
support their common functionality and interfaces which
are constituted by the MAC.
In order to facilitate bridging between this version of the
protocol and other IEEE data buses the following
subsections are closely modeled after IEEE 802.3
(Ethernet).
Throughout Section 3 of this document the following
terms are being used:
MAC Sublayer: This term refers to the abstract
definition of a layered communication stack in which
the MAC Sublayer is part of the Data Link layer.
MAC Entity: Implementation of the functionality
described for the MAC Sublayer
MAC Service Provider: This term can be used
interchangeably with MAC entity and is supposed to
provide context to the Client/Server nature of the layers
of the communication stack.
MAC Service Client: Any entity (implementation) that
uses the services of the MAC entity (implementation)
MAC Frame: Logical representation of the information
structures exchanged between peer MAC entities. A
detailed description of the structures are given in
Section 3.3
Frame Data Unit (FDU): An ARINC 429 envelope that
contains a MAC frame as well as specific control
information. A detailed description of the structures is c-17
given in Section 3.4.
3.1.2 Relationship Between Version 1 And Version 3
Protocols
The bit-oriented MAC protocol (Version 3) is derived
from the full-handshake (Version 1) bit-oriented
protocol (BOP) defined in Section 2.5 of this
specification. Version 3 is presented to MAC Service
Clients that do not require or desire the more exhaustive
Data Link layer transfer validation provided by the
Version 1 protocol.
The Version 3 protocol assumes a sufficiently robust
ARINC 429 physical layer. All valid frames received by
the sink are passed up to the MAC Service Client. The
demands for buffering are much greater for Version 3
than for Version 1. In Version 1 the transmitter is
responsible for buffering, in Version 3 the receiver is
responsible.
The Version 1 ARINC 429 LDU full and partial data
words have been retained. New SOF and EOF words
have been defined for Version 3 (see Sections 3.4.6 and
3.4.8) which replace the Version 1 SOT and EOT words.
The bit-oriented MAC protocol does not use the RTS,
CTS, NCTS, BUSY, SYN, ACK and NAK words. Only
single Frame Data Unit (FDU) transmissions are
supported. Duplicate FDU detection is not performed by
the MAC. Any segmentation and reassembly, if
necessary, should take place above the ARINC 429 MAC
sublayer. The terms Frame Data Unit (FDU) and MAC
frame are defined in Sections 3.3.1, 3.3.2, and 3.4.1.
The Version 3 bit-oriented MAC protocol specifies full
duplex operation (O1) to allow simultaneous data
transfers in both directions. The Version 1 bit-oriented
(Williamsburg) protocol typically operates in half-duplex
mode only.

3.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL
3.1.3 Protocol Architecture
The MAC protocol described herein can support MAC
service clients that are part of the Data Link layer such as
LLC and can support MAC service clients in higher layer
entities such as the Network Layer. A protocol architecture
diagram is used to illustrate this relationship (See Figure 18-
1 of Attachment 18).
3.1.4 Buffering
The MAC sublayer should provide sufficient buffering to
account for expected processing/queuing delays. Some
provisions for flow control are provided through the MAC
sublayer (see Section 3.2.4). Flow control is primarily the
responsibility of the MAC service client or a higher level
entity.
COMMENTARY
Each layer should have sufficient buffering for expected
processing/queuing delays. In order to accurately estimate
c-17 the amount of buffering needed, each layer will need to
specify the maximum allowed delays. However, if the
buffering capacity is exceeded, new FDUs are discarded.
There is a non-zero time delay between the time when a
FDU arrives at the ARINC 429 MAC sublayer and the
time when the MAC Service Client processes that same
frame. Any flow control, introduced between two
systems, is provided by entities above the MAC service
entity sending messages to each other. For this reason, the
entity responsible for flow control should attempt to
anticipate the need to activate flow control in order to
accommodate the delays.
The entity responsible for flow control should attempt to
have adequate buffering capacity to handle all FDU
transfers received from the time it exerts flow control to
the time when the source flow control entity stops
transmitting. This will only be possible if the maximum
allowed delay in each of the various components is
specified. These delays include any processing or
queuing delays introduced by communications with the
MAC Service Client.
Failure to coordinate the requirements (i.e. delays) will
make it difficult to consistently provide adequate
buffering capacity and may lead to data loss and possible
communication failures.
If buffering of incoming frames is done at the MAC sublayer,
then the reception status parameter of the MAC primitive,
MA_DATA.indication (see Section 3.2.3) should be used to
inform the MAC Service Client of a buffering problem for the
received frame.
COMMENTARY
ISO standards documents do not explicitly specify at
which (sub) layer buffering is accomplished.
ARINC SPECIFICATION 429 PART 3 - Page 15
3.2 Media Access Control (MAC) Sublayer
This section describes the various aspects of the MAC
sublayer functionality. The MAC Sublayer Service
Specification (Section 3.2.1) details the procedures in
an abstract way (via service primitives) that provide the
communication service to the MAC Service Client. The
subsequent section, MAC Frame Structures (Section
3.3), defines the MAC frames that will be presented to
and expected from the peer MAC entity. The next
section, MAC Transmit/Receive Functions (Section
3.4), is related more to the interface with the particular
ARINC 429 transmission and reception process itself
and specifies how the FDUs are structured as a
sequence of ARINC 429 words.
There are two types of applications that have driven the
development of this version of the protocol. One is the
need for a bridgeable protocol that can transfer data
between an ARINC 429 bus and a non-ARINC 429
based data bus. This type of application would need fast
file transfer traffic that is focused upon aircraft-wide
topology and would utilize an independent exchange of
MAC frame-based information.
The other need is to transfer local, ARINC 429 only,
fast file transfer traffic that is focused upon exchanges c-17
between two closely cooperating systems. In order to
allow for the optimized transmission of the two types of
information, two specialized MAC frame structures
have been defined, the Information frame and the
Command frame. The Information frame is intended to
be bridgeable to IEEE 802.3 (Ethernet). The Command
frame is not bridgeable. Option 13 (O13) in Table 10-3B
of Attachment 10 allows for the apriori selection of
frame type, based on the applicable equipment interface
specification.
From a transmitter’s point of view, i.e., the originating
MAC Service Client, one parameter within the
MA_DATA.request primitive selects which type of
MAC frame to create (see Section 3.2.2.2.4).
From the receivers point of view, i.e., the receiving
MAC Service Client, the type of frame (Information or
Command) received is indicated through a parameter in
the MA_DATA.indication primitive, based on the
contents of the SOF word (see Sections 3.2.3.2.7 and
3.4.6).
The Version 3 Information frame format facilitates
bridging between this version of the ARINC 429
protocol and IEEE data buses. The following
subsections are closely modeled after IEEE 802.3
(Ethernet).
The Version 3 Command frame format facilitates the
exchange of command/response pairs, which are peer-
to-peer only and hence do not require the additional
addressing capability provided by the Information
frame.
3.2.1 MAC Sublayer Service Specification
This section describes the services that the Media
Access Control Sublayer provides to the next higher
layer, i.e., to the MAC Service Client. The services
 ARINC SPECIFICATION 429 PART 3 - Page 16
3.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL
3.2.1 MAC Sublayer Service Specification (cont’d)
are described in an abstract way and do not imply any
particular implementation or any exposed interface. There is
not necessarily a one-to-one correspondence between the
primitives described herein and the implementation.
Four primitives are used to describe this interface. They are:
MA_DATA.request
MA_DATA.indication
MA_CONTROL.request (optional)
MA_CONTROL.indication (optional)
The MAC sublayer is depicted in Attachment 18 Figure
18-2.
These primitives describe the required local information
needed to identify the purpose of the incoming or outgoing
data transfers. Their services are described in the following
subsections. These services are local to each device and do
not imply any particular implementation at the service
interface.
This section provides all the information needed in order to
initiate transfer or process reception of user data or control
information.
c-17
3.2.2 MA_DATA.request
The MA_DATA.request primitive is used to describe how
to transmit data that is carried by a MAC frame. The service
is looked at from the transmitting MAC Service Client point
of view.
The requesting MAC Service Client needs to provide
sufficient information to the MAC sublayer to enable the
MAC sublayer to format a FDU for transmission to a peer
MAC Service Client. This information should include the
destination, the data and the transmission service
(Information or Command).
3.2.2.1 Function
The MA_DATA.request primitive defines the transfer of
data from a local MAC Service Client entity to a single peer
MAC Service Client entity (or entities in the case of group
addresses).
The ARINC 429 MAC protocol provides two classes of
service, the Command frame (local non-bridgeable frame)
and the Information frame (bridgeable frame).
3.2.2.2 Semantics
The following parameters are provided with this primitive:
MA_DATA.request
(destination_MA_address,
destination_SAL_address
m_sdu,
service_class)
3.2.2.2.1 destination_MA_address
The destination_MA_address parameter should provide
either an individual or a group MAC address when an
Information frame is to be sent. If an invalid address is
being handed over, the primitive should not initiate a
FDU transmission. Instead, the MA_DATA.request
should be dropped and the layer management should be
informed.
The destination_MA_address is not used with a
Command frame, but is required for an Information
frame.
The format and contents of the
destination_MA_address for an Information frame is
defined in ARINC Specification 664.
COMMENTARY
At the time this text was written, ARINC
Specification 664 was in draft state i.e., Project Paper
664.
3.2.2.2.2 destination_ SAL _address
The destination_SAL_address is required for both
Command and Information frames. The
destination_SAL_ address field contains the SAL to be
used for transmitting the FDU.
c-17
The destination_SAL_address field for an Information
frame can contain either a unique SAL, a multicast SAL
or a bridge SAL.
The destination_SAL_address field for a Command
frame should contain a unique SAL.
The format and content of the SAL is defined in
ARINC Specification 429, Part 1.
3.2.2.2.3 m_sdu
The m_sdu parameter indicates the MAC service data
unit (data content) to be transmitted by the MAC
sublayer entity.
If the m_sdu is empty, i.e. the length is zero, the
MA_DATA.request primitive should not cause the
initiation of a FDU transmission. Instead, the
MA_DATA.request should be dropped and the layer
management should be informed. The MAC Service
Client should not create a MA_DATA.request with an
empty m_sdu field.
3.2.2.2.4 service_ class
The service class parameter indicates a quality of
service requested by the MAC Service Client. The
parameter indicates whether an Information or
Command frame should be constructed. For a
Command frame, the GFI field and Command Type
field values are also indicated via this parameter (see
Sections 3.3.2.1 and 3.3.2.2)
COMMENTARY
Currently, two services have been defined, which
are “Transmission of Information Frame” and
“Transmission of Command Frame”. The
determination of how to initiate one or the other is
 ARINC SPECIFICATION 429 PART 3 - Page 17
3.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL

done locally and is a matter of implementation. source_MA_address

However, care should be taken in selecting the
mechanism to forward that information. More services source_SAL_address
might be defined at a later stage, which in turn might m_sdu,
create a conflict with the implementation.
reception_status,
There is an implication on the destination address field service_class)
that originates from the determination of which type of
frame to use. The Command frame uses only the unique 3.2.3.2.1 destination_MA_address
System Address Label (SAL) that has been defined for
Version 1 of this protocol. The Information frame, The destination_MA_address is obtained from the
however, needs two addresses in parallel: the IEEE Information frame and will contain either an individual
compliant 48-bit destination and source addresses as well or a group MAC entity address. The
as a SAL. destination_MA_address parameter is empty when the
MA_DATA.Indication is generated in response to
receiving a Command frame
3.2.2.3 When Generated
3.2.3.2.2 destination_SAL_address
The MAC Service Client generates the MA_DATA.request
primitive. It is a request by a MAC Service Client to the The destination_SAL_address data is obtained from the
local MAC sublayer to transfer a MAC Service Data Unit received FDU for either an Information or Command
(m_sdu) to a peer MAC Service Client entity (or entities). frame.
The primitive is generated either as the result of a request
from a higher layer entity, or internally from the MAC
Service Client itself. 3.2.3.2.3 source_MA_ address
The source_MA_address parameter contains the data c-17
c-17 3.2.2.4 Effect of Receipt from the source_MA_address field of an incoming FDU
that contains an Information frame. For MAC
Upon receipt of the MA_DATA.request primitive, the MAC addressing information refer to ARINC Specification
sublayer first creates the MAC frame by appending any 664.
MAC-specific fields (See Section 3.3.1 and 3.3.2).
COMMENTARY
Secondly, the MAC service entity packs the resulting MAC
frame into an ARINC 429 “container” consisting of a series At the time this text was written, ARINC
of contiguous ARINC 429 32-bit words (See Section 3.4.1) Specification 664 was in draft state i.e., Project
to create a FDU. It transmits the properly formatted FDU to Paper 664.
the peer MAC sublayer entity (or entities) by means of the
Physical layer services for subsequent transfer to the The source_MA_address parameter is empty when the
associated MAC Service Clients. MA_DATA.indication is generated in response to
receiving a Command frame.

3.2.3 MA_DATA.indication 3.2.3.2.4 source_SAL_ address

The MA_DATA.indication primitive is used to describe, at The source_SAL_address is generated by the MAC
the destination MAC Service Client, the mechanics to be based on the physical port on which the Information or
used in order to receive data that is carried by a FDU. The Command frame was received.
service is looked at from the receiving MAC Service Client
point of view. This primitive is generated by the MAC entity 3.2.3.2.5 m_sdu
upon reception of a valid FDU, and recreation of the MAC
frame. The m_sdu parameter indicates the MAC service data
unit as received by the local MAC sublayer entity.
3.2.3.1 Function
3.2.3.2.6 reception_status
The MA_DATA.indication primitive defines the transfer of
data from a remote MAC Service Client entity to a local The reception_status parameter is used to pass status
peer MAC Service Client entity. information to the MAC Service Client. The content of
this parameter is implementation specific.
3.2.3.2 Semantics
3.2.3.2.7 service_class
The following parameters are provided with the
MA_DATA.indication primitive: The service_class parameter is used to indicate whether
an incoming frame is an Information or Command
MA_DATA.indication frame. If it is a Command frame, the GFI and command
(destination_MA_address, type (CT) information is also passed to the MAC
Service Client.
destination_SAL_address,
 ARINC SPECIFICATION 429 PART 3 - Page 18
3.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL
3.2.3.3 When Generated
The MA_DATA.indication primitive is passed from the
MAC sublayer to the MAC Service Client to indicate the
arrival of a FDU at the local MAC sublayer entity. The
MAC Sublayer first validates the FDU (see Section 3.4.12)
and then removes the ARINC 429 “container” (i.e., the
ARINC 429 32 bit word protocol headers/footers) and
combines the resulting data and parameters into a
MA_DATA.indication primitive. The primitive is reported
only if the frame is valid (see Sections 3.3.1.5 and 3.3.2.5).
3.2.3.4 Effect of Receipt
The effect of receipt by the MAC Service Client is not
defined in this document. Refer to the appropriate ARINC
specification for MAC Service Client definitions.
Since buffering capacity is limited, in the event the MAC
Service Client can not consume a frame, any subsequent
frames may be discarded.
3.2.4 MAC Control functions
The MAC control function is derived from IEEE 802.3
Clause 31. Support of MAC control provides for real-time
c-17 control and manipulation of MAC sublayer operations, and
is provided as an Option (O14) for the Version 3 protocol.
Sections 3.2.4.1 and 3.2.4.2 describe this method of
providing flow control for the Version 3 bit-oriented
protocol using either the Information frame format for
Ethernet bridgeable interfaces, or the Command frame
format for non-bridgeable interfaces. Frames destined for
the MAC control sublayer (MAC Control frames) are
distinguished from frames destined for MAC Service Clients
by a unique identifier.
For Information frames, the MAC Control Sublayer receives
m_sdu frames and examines the ‘Type’ field for this unique
identifier to determine if it is equal to control value (Pause
opcode) of 8808 hex. If it is equal to 8808 hex, the MAC
Control sublayer processes the Information frame.
Otherwise the Information frame is passed to the MAC
Service Client without modification.
For Command frames, the MAC Control Sublayer examines
the Command Type parameter. If it is set to ‘MAC Control’
(and the first two octets of the m_sdu contain the Pause
opcode, 8808 hex), the MAC Control sublayer processes the
Command frame. Otherwise the Command frame is passed
to the MAC Service Client without modification.
In the Version 1 protocol, flow control was provided through
the use of BUSY and NCTS word responses to an RTS word.
These ARINC 429 specific protocol words are not used in
Version 3.
For Version 3, the Ethernet compatible PAUSE function is
defined at the MAC Control sublayer. This control sublayer
is part of the MAC, physically located just above the MAC
sublayer, but below the MAC Service Client. Figure 18-2 of
Attachment 18 depicts the usage of interlayer interfaces by
the MAC Control sublayer. LRUs that support the option
(O14) to implement the MAC control sublayer should
support the optional MAC service primitives,
MA_CONTROL.request and MA_CONTROL. indication,
as illustrated. The PAUSE operation is used to inhibit
transmission of data frames from a directly connected
full-duplex peer system only, and is therefore not
bridgeable.
3.2.4.1 MA_CONTROL.request
The MA_CONTROL.request primitive is generated by
the local MAC Control client to send to its peer, via the
MAC sublayer, to request inhibiting of MAC frame
transmissions from another system for a specified
period of time. The MA_CONTROL.request primitive
specifies:
a1. the destination_MA_address (for an Information
frame) or
a2. Command Type set to MAC Control (for a
Command frame)
b. the PAUSE opcode (8808 hex)
c. a Request_operand indicating the length of time
for which it wishes to inhibit data frame
transmission and
d. the Destination SAL.
The size of a MAC Control frame is 32-bits: a 16-bit c-17
(PAUSE opcode), and a 16-bit request operand.
An example of the format of the MAC Control frame
using both the Information and Command frame Data
Unit (FDU) formats is illustrated in Attachments 19 and
20.
The Pause quanta (units of pause time) inhibits
transmission of data frames for a specific period of
time. The pause time quanta for Williamsburg Version
3 over high speed ARINC 429 is 5 milliseconds.
The PAUSE flow control function is defined as optional
(O14) for Version 3, since it is not anticipated that all
Version 3 interface implementations, such as that of the
CMU/VDR, will require flow control at the MAC
sublayer. (i.e., VDR Mode A uses the MSK modulation
scheme so air/ground throughput is somewhat limited and
the need for flow control is not anticipated. For VDL
Mode 2, the ARINC 429 MAC Service Client is
AVLC/8208, which provides flow control from the CMU
to the DSP ground station.)
COMMENTARY
IEEE 802.3, 1998 Annex 31B.2 states: “The pause-
time is measured in units of pause quanta, equal to
512 bit times for the particular implementation. The
range of possible pause time is 0 to 65535 pause
quanta.” The bit time for 10 megabit Ethernet is 0.1
us, therefore a pause quanta is 51.2 us for this media.
The bit time for 100 kilobit high speed ARINC 429 is 10
us, therefore the pause quanta for high speed ARINC 429
is 5.12 ms, or approximately 5 ms. The pause time range
for ARINC 429 is then from 5 ms to 327 seconds. It is
recommended that the pause range be appropriate for the
application being supported to prevent adverse effects.

3.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL
COMMENTARY
In typical operation the PAUSE function can be used in
an X-OFF, X-ON operation by setting the pause_time to
a large value, then when convenient, sending another
PAUSE command with the pause_time = 0 to restart
transmission. Sending another MAC Control frame
before the Pause value in the previous MAC Control
frame times out should cause the sink to replace the
current Pause value with the new Pause value, if non-
zero, and restart the timer. A Pause value of 0 terminates
the Pause and restores normal operation.
3.2.4.2 MA_CONTROL.indication
The MA_CONTROL.indication primitive indicates the
status of the local PAUSE operation (i.e., paused, or not
paused) to the MAC Service Client.
When the MAC Control sublayer receives a MAC Control
frame indicating a Pause condition, it should:
a. Notify the local MAC sublayer to stop sending
frames to the peer MAC sublayer. The MAC sublayer
should complete a frame transmission in progress.
c-17 b. Notify the local MAC Service Client of the Pause
condition.
c. Start timer of duration indicated in the MAC Control
frame.
d. Refuse frames from the local MAC Service Client
until the timer expires.
When the pause timer expires the MAC Service Client
should be notified. Likewise, when another control frame
with the pause_time set equal to 0 is received then the MAC
Service Client should be notified and normal operation
resumed.
COMMENTARY
The design of ARINC 429 ICs frequently contain
transmit FIFOs in order to reduce the burden on the
microprocessor and therefore do not facilitate the
termination of data transmission in mid frame. An
implementation that does terminate transmission mid
frame will cause Timer T17 in the receiver to time out.
3.3 MAC Frame Structures
This section defines in detail the MAC frame structures for
ARINC 429 using MAC procedures. It defines the relative
positions of the various components of the MAC frame. It
describes the general method for representing station
addresses as well as ARINC 429 specific System Address
Labels (see Section 3.4.3). Refer to ARINC Specification
664 for the MAC address specification for Information
frames.
COMMENTARY
At the time this text was written, ARINC Specification
664 was in draft state i.e., Project Paper 664.
ARINC SPECIFICATION 429 PART 3 - Page 19
3.3.1 Information Frame Format
The MAC Information frame comprises 5 fields: the
destination address field, the source address field, the
length/type field, the data field and the frame check
sequence field. Of these 5 fields all except the data field
are of fixed length. Due to the transmission scheme
used no preamble or delimiter fields are required as
with other technologies. The frame check sequence
field has been put into the EOF (see Section 3.4.8)
words. Attachment 20 shows the format of the
Information frame (and the FDU structure).
3.3.1.1 Address fields
Each MAC Information frame contains two address
fields: the destination and the source address field, they
are constructed the same way. The destination field
specifies the MAC entity (or entities) for which the
FDU is intended. The source address field identifies the
MAC entity from which the FDU is initiated. Each
address field contains 48 bits (i.e., six octets). For the
construction of the MAC address fields see ARINC
Specification 664.
COMMENTARY c-17
At the time this text was written, ARINC
Specification 664 was in draft state i.e., Project Paper
664.
3.3.1.2 Length/Type Field
The Length/Type Field is defined in IEEE 802.3 Clause
3.2.6. This 2-octet field takes one of two meanings,
depending on its numeric value.
a. If the value of this field is less than or equal to
1500 decimal, then the Length/Type field
indicates the number of MAC client data octets
contained in the subsequent data field of the
frame (Length interpretation). In this case the
MAC Client is defined to be the LLC service
entity, and the LLC header should immediately
follow the IEEE 802.3 header.
b. If the value of this field is equal to or greater
than 1536 decimal, than the Length/Type field
indicates the nature of the MAC Client protocol
(Client interpretation).
c. Any other value of this field is considered
undefined (i.e., values between 1500 and 1536)
3.3.1.2.1 Length
If the Length/Type field is a Length value, the use of
IEEE 802.3 LLC is assumed. The values and uses of the
LLC field are beyond the scope of this specification.
Length indicates the total number of octets in the data
field of the frame. It does not include the address fields,
the length/type field, or the FCS field.
Valid values for length are between 1 and 1500.
 ARINC SPECIFICATION 429 PART 3 - Page 20
3.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL
3.3.1.2.1 Length (cont’d)
COMMENTARY (cont’d)
The maximum size permitted by IEEE 802.3 is 1500
bytes for the payload of an Ethernet frame (i.e., the
m_sdu size of an Ethernet frame).
3.3.1.2.2 Type
Protocols other than LLC may be used and this is supported
by using the Length/Type field as an indicator of protocol
type. When the Length/Type field is used in this manner
then it should contain the protocol type consistent with the
protocol encapsulated by the Ethernet frame. Valid values
for the type field are defined in ARINC Specification 664.
COMMENTARY
At the time this text was written, ARINC Specification
664 was in draft state i.e., Project Paper 664.
3.3.1.3 Data Field
The data field can contain up to 2536 (2550-14) octets.
However, the number of data field octets should be limited
to 1500 in order to allow bridging to Ethernet-based
c-17 networks.
Full data transparency is provided in the sense that any
arbitrary sequence of octet values may appear in the data
field.
3.3.1.4 Frame Check Sequence (FCS) Field
A cyclic redundancy check (CRC) sequence is used by the
transmit and receive algorithms to generate and check a 32-
bit (4-octet) CRC value. This value is computed as a
function of the contents of the source address field,
destination address field, Length/Type field and data field.
The encoding is performed by the generating polynomial as
defined in Section 3.4.9. The FCS is calculated by the
transmitting MAC Service Entity and appended to the MAC
frame. The FCS is recalculated and verified by the receiving
MAC Service Entity following reconstruction of the entire
frame and prior to providing the MA_DATA.indication to
the MAC Service Client.
If Option O15 is not selected, the 32 bit CRC will not be
generated or evaluated across the interface. If not used for
containing the CRC, the FCS field should be set to binary
zero to indicate to the receiving MAC service entity that the
FCS was not calculated by the transmitting MAC service
entity.
COMMENTARY
Not implementing (generating and validating) a Frame
Check Sequence in the Information frame may have
negative consequences on system integrity. The
integrator is cautioned to be aware of applications that
utilize the interface in which Option 15 has not been
selected.
3.3.1.5 Validation of Information Frame
The receiving MAC sublayer should determine the validity
of the incoming Information frame before passing the MAC
frame to its local Service Client. The following subsections
list the conditions for which the Information frame is
said to be invalid. The contents of invalid MAC frames
should not be passed to the local MAC Service Client,
however reception of an invalid frame, and the reason
for declaring it invalid, should be indicated to the MAC
Service Client.
3.3.1.5.1 Invalid Address
Address checking should be performed according to
ARINC Specification 664.
3.3.1.5.2 Invalid Length/Type
If the value in the Length/Type field is not a valid value
as defined in section 3.3.1.2.1 and is not a known Type
value then the MAC frame is considered invalid.
If the Length/Type field contains a length value and the
number of octets does not match the length then the
MAC frame is considered invalid.
3.3.1.5.3 Invalid FCS
The receiving MAC sublayer should verify the 32-bit
FCS of the received MAC frame. If the 32-bit FCS is
invalid, the MAC frame is also invalid
c-17
The value of binary zero in the FCS field is a unique
and valid FCS if CRC generation (O15) is not selected.
This indicates that the source MAC Service Entity does
not calculate the CRC for this field. The receiving
system should check that CRC non-generation (O15) has
been selected for this port.
3.3.2 Command Frame Format
For a MAC Command frame the following four fields
are needed:
a. the GFI field ,
b. the Command Type field,
c. the Data field and
d. the Frame Check Sequence field.
Of these four fields all except the data field are fixed
length. In order to retain as much compatibility with
ARINC 429 Williamsburg processing as possible, the
frame check field has been put into the EOF word (See
Section 3.4.8). Attachment 19 shows the format of the
Command frame (and FDU) structure.
The Command frame does not contain separate address
fields like the Information frame. It relies on the
ARINC 429 SAL for addressing. For the definition of
the SAL see Section 3.4.3.
3.3.2.1 GFI Field
In order to retain as much compatibility with ARINC
429 Williamsburg Version 1 as possible, the GFI field
has been retained in the SOF word. See Section 2.5 for
the definition of GFI. If the GFI field is not used, this
field is set to binary zeroes.

3.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL
3.3.2.2 Command Type Field
The Command Type field was created to provide
mechanism for the receiver to differentiate between
Command frame that contains a command message,
control message, or a data message (such as a VDL Mode
frame transmitted across a CMU/VDR interface).
3.3.2.3 Data Field
The Data field contains up to 2552 octets. Full data
transparency is provided in the sense that any arbitrary
sequence of octet values may appear in the data field.
3.3.2.4 Frame Check Sequence (FCS) Field
A Cyclic Redundancy Check (CRC) sequence is used by the
transmit and receive algorithms to generate and check a 16-
bit (2-octet) CRC value. This value is computed as a
function of the contents of the data field. The encoding is
performed by the generating polynomial as defined in
Section 3.4.9.
3.3.2.5 Validation of Command Frame
The receiving MAC sublayer should determine the validity
c-17 of the incoming Command frame before passing the MAC
frame to its local Service Client. The following subsection
lists the condition for which the Command frame is said to
be invalid. The contents of invalid MAC frames should not
be passed to the MAC Service Client.
3.3.2.5.1 Invalid FCS
The receiving MAC sublayer should verify the 16-bit FCS
of the received MAC frame. If the 16-bit FCS is invalid, the
MAC frame is also invalid.
3.4 MAC Transmit/Receive Functions
This section defines the functions to transmit and receive the
contents of FDUs on the physical medium. It is also known as
the interface to the Physical layer.
3.4.1 Frame Data Unit (FDU)
A Frame Data Unit (FDU) envelops a MAC frame and
consists of a set of contiguous ARINC 429 32-bit words, each
containing the System Address Label (see Section 3.4.3) of
the sink. A FDU can be either an Information frame or a
Command frame. The initial data word of each FDU is a Start
of Frame (SOF) data word (see Section 3.4.6). The MAC
frame (See Section 3.3) is contained within the data words that
follow. The FDU is concluded with one or two consecutive
End of Frame (EOF) words (see Section 3.4.8). A FDU
always consists of no more than one frame.
A Frame Data Unit (FDU) contains binary encoded octets.
The octets may be set to any possible binary value. The FDU
contains any string of bits desired. The only restriction is that
the bits be organized into full 8 bit octets. The interpretation
of those bits is not a part of this specification.
3.4.2 Frame Data Unit (FDU) Size and Word Count
The FDU word count is the sum of the SOF word, the data
words containing the MAC frame, and the EOF word(s). The
Frame Data Unit (FDU) may vary in size from a minimum of
ARINC SPECIFICATION 429 PART 3 - Page 21
three, to a maximum of 1023 ARINC 429 words
(including the SOF and EOF words). When a FDU is
a organized for transmission, the total number of ARINC
a 429 words to be sent (word count) is calculated.
a
2
3.4.3 System Address Labels (SALs) c-17
Each on-board system attached to an ARINC 429 bus that
requires aperiodic message capability is assigned a
System Address Label (SAL). The listing of SAL
assignments can be found in Attachment 11 to ARINC c-18
Specification 429, Part 1. FDUs are sent point-to-point,
even though other systems may be connected and
listening to the output of a transmitting system. In order
to identify the intended recipient of a transmission, the
Label field (bits 1-8) is used to carry a System Address
Label (SAL).
When a system sends a FDU to another system, the
sending system (source) addresses each ARINC 429
word to the receiving system (sink) by setting the Label
field to the SAL assigned to the sink.
Apart from existing system specific unique SALs, two
universally applicable SALs have been defined: the
Multicast SAL (MSAL) and the Bridge SAL (BSAL).
These SAL´s are designated for Information frames
only and should not be used for Command frames.
For situations where a system will need to communicate
with another system, which has no SAL assigned, i.e., is c-17
not attached to an ARINC 429 bus, a Bridge SAL will be
used.
COMMENTARY
The Bridge SAL assumes that no compatibility
conflict will arise with other systems. The bridge will
accept all FDUs and afterwards selects how to
handle them based upon a predefined or, in some
cases, learned bridging table.
For situations, where multiple systems will need to be
addressed at the same time, a Multicast SAL will be used
This SAL can only be used for the transmission of
Information frames. In this case, a system needs to
examine the MAC destination address contained in the
FDU.
COMMENTARY
Similar to the Bridge SAL, the Multicast SAL
assures that no compatibility conflict will arise with
other systems. Generally, it addresses all attached
systems, local or remote (beyond the bridge). It is the
responsibility of each individual system to determine
whether or not to accept the FDU being received.
When a system receives any data containing its SAL that
is not sent through the established conventions of this
protocol, the data received should be ignored.
 ARINC SPECIFICATION 429 PART 3 - Page 22
3.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL
3.4.4 Bit Rate and Word Timing
Data transfer should operate at the low or high-speed rate as
c-18 defined in Part 1 of ARINC Specification 429 depending on
the value of Option 2 (see Table 10-3b). The source should
introduce a gap between the end of each ARINC 429 word
transmitted and the beginning of the next. The gap should be
c-17 at least 4 bit times (minimum). The sink should be capable of
receiving the FDU with the minimum word gap of 4 bit times
between words. The source should not exceed a maximum
average of 40 bit times between data words of a FDU.
3.4.5 Word Type
The Word Type field occupies bit 31-29 in all bit-oriented
FDU words. See Table 11-1A of Attachment 11 for a
description of the Word Type field. The Word Type field is
used to identify the function of each ARINC 429 data word
used by the bit-oriented communication protocol. There are
two new word types for the Version 3 protocol, word types
010 and 011.
3.4.6 Start of Frame (SOF)
When a system wants to transmit either an Information
Frame Data Unit or a Command Frame Data Unit, the
system should start by sending the Start of Frame (SOF)
data word, immediately followed by the data words, which
contain the contents of the MAC frame. The format of the
SOF word differs between Information and Command
c-17 FDUs. See Attachment 11, Tables 11-8 and 11-10 for a
description of these two words.
In order to distinguish between Information and Command
frames, the SOF word contains an Information/Command
Frame field.
3.4.6.1 Information/Command (I/C) Frame Field
The Version 3 protocol provides for two different MAC
frame types in order to adapt to the requirements of different
applications: an (Ethernet) bridgeable Information frame
and a non-bridgeable Command frame. For a description of
the Frame Data Units (FDUs) which contain these two types
of MAC frames, see Attachments 19 and 20.
To identify the different frame types, bits 20-19 of the SOF
word (for both Information and Command FDU) carry the
following discriminator:
Bit 20 Bit 19 Definition
0 0 Information frame
0 1 Command frame
1 0 Reserved
1 1 Reserved
3.4.6.2 Information SOF word
The SOF word for the Information Frame Data Unit
contains a 10-bit word count, a 2-bit Information/Command
(I/C) frame field (as described in Section 3.4.6.1) and an 8-
bit Reserved field.
3.4.6.2.1 Word Count
The Word Count field (bits 18-9) of the Information SOF
word reflects the number of ARINC 429 words to be
transmitted in the Frame Data Unit. For the Information
frame, the maximum word count value is 1023 ARINC
429 words. The minimum word count value is 10
ARINC 429 words. An Information FDU with the
minimum word count would contain one SOF word,
seven data words, and two EOF words. An Information
FDU with the maximum word count value would
contain one SOF word, 1020 data words and two EOF
words.
3.4.6.2.2 Reserved Bits
Bits 28-21 of the SOF word for the Information FDU
are reserved (not used). These bits should be set to
binary zeroes.
3.4.6.3 Command SOF word
The SOF word for the Command frame Data Unit
contains a 10-bit word count, a 2-bit
Information/Command (I/C) frame field (described in
Section 3.4.6.1), a 2-bit Reserved field, a 2-bit
Command Type Field and a 4-bit General Format
Identifier (GFI) field.
3.4.6.3.1 Word Count c-17
The Word Count field (bits 18-9) of the Command SOF
word reflects the number of ARINC 429 words to be
transmitted in the Frame Data Unit. For the Command
frame, the maximum word count value is 1023 ARINC
429 words. The minimum word count value is 3 ARINC
429 words. A Command FDU with the minimum word
count would contain one SOF word, one data word and
one EOF word. A Command FDU with the maximum
word count value would contain one SOF word, 1021
data words and one EOF word.
3.4.6.3.2 Reserved Bits
Bits 22-21 of the SOF word for the Command FDU are
reserved (not used). These bits should be set to binary
zeroes.
3.4.6.3.3 General Format Identifier Field (GFI)
For the Command Frame Data Unit (FDU), a General
Format Identifier (GFI) occupies bits 28-25 of the SOF
word. It’s function is similar to the General Format
Identifier described in Section 2.5.10.1 of the Version 1
bit-oriented protocol. This field is maintained in the
Command FDU for backward compatibility to the
point-to-point (non-bridgeable) link layer protocol used
in Version 1. The GFI field is used in Version 3 as an
indicator to the MAC Service Client of the format of
data words to follow.
3.4.6.3.4 Command Type Field (CT)
For the Command Frame Data Unit (FDU), a Command
Type (CT) field occupies bits 24-23 of the SOF word.
The purpose of the CT field is to facilitate the
differentiation of FDUs by functional context.
The following values have been assigned:

3.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL
Bit 24 Bit 23 Meaning
0 0 Command
0 1 Data
1 0 MAC Control
1 1 reserved
COMMENTARY
The contextual differentiation contained in the CT field
may be used to implement a flow control mechanism by
which FDUs of one context type are blocked while
FDUs of other types are not. Such a mechanism might
be used in a buffer-limited implementation to control
the flow of FDUs containing application data while
allowing command or control FDUs to pass freely. The
protocols and procedures to implement this mechanism
are not part of this specification.
3.4.7 Data
The definition of the data words which contain the MAC
frame’s contents are identical for both Version 3
(Information or Command) frame types, and are identical
with the data words used in Version 1 of the bit-oriented
protocol. However, the first six data words of an
Information MAC frame data unit contains additional MAC
c-17 addressing and length/type information.
Data words immediately follow the SOF word. The octets of
the FDU are encoded and transmitted in 32-bit data words.
There are two basic types of data words: full binary and
partial binary. Binary data words may contain one, two, three,
four and five semi-octets. A semi-octet (or nibble) is half of an
octet, or four bits in length.
Binary data words of five semi-octets are called Full Data
words. Binary data words of fewer than five semi-octets are
called Partial Binary Data words.
Each FDU, prior to transmission, should conclude (end) with
a complete octet.
3.4.7.1 Full Data Word(s)
A Full Data Word has 20 bits available for data. This space is
allocated in five semi-octets. The octets of the data file are
divided into two semi-octets and placed sequentially into the
data words. The least significant bit of the least significant
semi-octet is sent first.
If, in the process of placing the octets into the data words, an
octet is split between two different words, the least significant
semi-octet goes in the last (n5) semi-octet of the current data
field. The most significant semi-octet follows in the first (n1)
semi-octet of the data field of the next word. See Tables 11-2
and 11-3 of Attachment 11 for data word formats.
If the end of the FDU does not completely fill the last Full
Data Word, a Partial Data Word (see Section 3.4.7.2) should
be used to complete the FDU transmission.
In order to obtain maximum system efficiency, Partial Data
Words should be used only when they are required to
complete the data for a FDU transmission. A FDU should not
be encoded as a string of Partial Data Words where 8 or 16
bits of data are encoded for each ARINC 429 word used.
ARINC SPECIFICATION 429 PART 3 - Page 23
3.4.7.2 Partial Data Word(s)
A Partial Data Word contains from one to four semi-
octets. The number of semi-octets in a partial data word is
indicated in bits 28-25 of the word. Only full four-bit
semi-octets can be sent; one, two or three bits are invalid.
Partial Data Word semi-octets are sent in the same order
as the semi-octets in a full data word. The unused semi-
octets in the partial data word should be set to binary
zeros.
3.4.7.3 SOLO Words
SOLO words, as defined in the Williamsburg Version 1
protocol in Section 2.5.17, may be used in the Version 3
protocol. However, they should be used only across non-
bridgeable interfaces (i.e. in conjunction with Command
frames).
3.4.8 End of Frame (EOF)
Each FDU transfer is terminated by one or two End of
Frame (EOF) word(s), depending upon the nature of the
FDU. The format and number of EOF word(s) differ
between Information and Command frames.
For an Information frame the EOF words contain a frame
check sequence which consists of a 32-bit Cyclic c-17
Redundancy Check (CRC).
For a Command frame the EOF word is identical to a
Version 1 EOT word and contains a frame check
sequence which consists of a 16-bit Cyclic Redundancy
Check (CRC).
The final FDU bit is always set for consistency with
Version 1.
See Attachment 11, Tables 11-9 and 11-11 for the
definition of these words.
COMMENTARY
The ARINC 429 Physical layer is a twisted shielded
pair of wires which has been demonstrated to exhibit
high integrity and unlikely to introduce errors into
the data passing through it. Simple parametric data is
usually transmitted at a refresh rate high enough to
permit recognition and suppression of erroneous
data. Since the transfer of data using a file transfer
protocol contains no provision for automatic refresh,
some applications may require high data integrity to
be confirmed by an error checking mechanism. For
this reason, each FDU contains a CRC check. The
use of the CRC in this case does not imply any
inherent lack of integrity of the ARINC 429 link.
3.4.9 Frame Check Sequence
For a Command frame, the Frame Check Sequence field
of the EOF word contains a 16-bit CRC as defined in
Sections 2.5.12.1 and 2.5.12.2 of the Version 1 bit-
oriented protocol. For an Information frame, the Frame
Check Sequence field of the EOF words contains a 32-
bit CRC, as defined in this section. Both CRC
polynomials are referenced in ISO 3309, and the
procedure for calculation of the 32-bit CRC is identical
 ARINC SPECIFICATION 429 PART 3 - Page 24
3.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL
3.4.9 Frame Check Sequence (cont’d)
to that of the 16-bit CRC. The only implementation
differences are found in the length and format of the two
generator polynomials and length of the CRCs.
The most significant bit (MSB) of the 32-bit CRC sequence
for Information frames is transmitted first.
3.4.9.1 32-Bit CRC Encoding
Determination and encoding of the CRC is as follows:
The k bits of information data in the frame are represented
as the coefficients of a polynomial, G(x); where k is the
number of data bits in the frame existing between, but not
including, the SOF and EOF words. For example, if the data
stream is 1010001,
k = 7 and G(X) = x6 + x4 + 1
The CRC calculation is performed over the data octets only
of the frame with any semi-octets zero filled.
The generator polynomial for the 32-bit CRC is of the form,
c-17
P(x) = x32 + x26 + x23 + x22 + x16 + x12 +x11 + x10 + x8
+ x7 + x5 + x4 + x2 + x + 1
The CRC is then determined as the one’s complement of the
remainder, R(x), obtained from the modulo 2 division of:
x32G(x) + xk (x31 + x30 + x29 + x28 +….+ x3 + x2 + x + 1)
P(x)
= Q(x) + R(x)
P(x)
Note: The addition of xk (x31 + x30 + x29 + x28 + ... + x3 + x2 +
x + 1) to x32G(x) (which is equivalent to inverting the first
32 bits of G(x) and appending a bit string of 32 zeroes to the
lower order end of G(x)), corresponds to initializing the
initial remainder to a value of all “ones”. The
complementing of R(x), by the transmitter, at the completion
of the division ensures that the received, error-free message
will result in a unique, non-zero remainder at the receiver.
32
At the transmitter, the CRC is added to the x G(x) product,
resulting in the message, M(x), of length n where:
n = k + 32, and
M(x) = x32 G(x) + R(x)
= x32 G(x) + CRC
3.4.9.2 32-Bit CRC Decoding
Decoding of the CRC at the receiver is as follows:
At the receiver, the incoming M(x) is multiplied by x32,
added to the product, xn (x31 + x30 + x29 + x28 + ... + x3 + x2 +
x + 1) and divided by P(x) as follows:
x32M(x) + xn (x31 + x30 + x29 + x28 + .... + x3 + x2 + x + 1)
P(x)
= Qr(x) + Rr(x)
P(x)
If the transmission of the serial incoming bits plus CRC
(i.e. M(x)) is error free, then the remainder, Rr(x) will
be:
1100 0111 0000 0100 1101 1101 0111 1011
(coefficients of x31 through x0 , respectively).
COMMENTARY
The notation used to describe the CRC is based on
the property of cyclic codes that any code vector,
such as 1000000100001, can be represented by a
polynomial G(x) = x12 + x5 + 1. The elements of an n
element code word are thus the coefficients of a
polynomial of order n - 1. In this application, these
coefficients can have the value 0 or 1 and all
polynomial operations are performed modulo 2. The
polynomial representing the information content of a
frame is generated starting with the Frame bit which c-17
is encoded in bit 9 of the first ARINC 429 data word
(following the SOF word) as the coefficient of the
first (highest order) term.
3.4.10 Incomplete FDU Timer
The Incomplete FDU (T17) timer is used to insure that a
source device does not “lock-up” a sink with an
incomplete frame.
The sink will start the T17 timer when it receives a
respective SOF word.
In case of an Information frame the T17 timer is stopped
when both valid EOF words are received.
In case of a Command frame the T17 timer is stopped
when a single valid EOF word is received.
The T17 timer should also be stopped if the sink discards
the partial frame for other reasons defined in this
specification. When T17 is exceeded, the sink should
discard any partial frame already received and ignore any
data until a proper SOF word is received.
3.4.11 ALOHA
The first ALOHA word transmitted in a sequence
should contain the highest Version Number supported
by the source device. If the ALOHA Response contains
a version that does not match the ALO version, the
source device should take one of the following actions:
a. If the source device is able to adapt to the
differences in protocol version, file transfers may
proceed using the protocol version identified in the
ALR word.

3.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL
b. If the source device is not able to adapt to the
differences in protocol version, the source should again
initiate the ALOHA word with the version field set to
the highest version supported by the source that is lower
than the version indicated in the previous ALR (see
examples identified in Attachment 13A).
The ALO/ALR protocol determination process should
continue until a common protocol version is found. If either
a protocol version is found or none of the protocol versions
match, the source should notify the local MAC Service
Client with a MA_DATA.indication with its
reception_status set to notify a reset condition. The
parameter in the primitive only has local significance and
provides the MAC Service Client with status information.
When the system only supports bit-oriented protocols, it
should repeat the process described in this section.
When the system also supports character oriented protocols,
then the process defined in Section 2.5.19.2 should be
followed. The protocol determination process will continue
until a common protocol is found. See Attachment 17.
The ALOHA word should contain a Subsystem SAL field as
shown in Attachment 11, Table 11-4. This field should
contain the SAL of the device sending the ALOHA word,
c-17 with bit 17 as the most significant bit and bit 24 as the least
significant bit of the Subsystem SAL.
A device that supports the bit-oriented Link layer protocol
should always be able to respond to the receipt of the ALO
word.
Whenever a device receives the ALO word, it should leave
its present task and respond within T15 with an ALR word.
The ALR response should reflect the device’s protocol
version level by the way of the Version Number contained
within the ALR word. If the Version Number of the ALO
does not match the sink device’s protocol Version Number,
the sink device should select the next lowest version
supported (equal to or lower than the version indicated by
the previous ALO word) and indicate this new version in the
ALR word.
If the device was in the sink mode (had already begun
receiving a FDU), it should discard any partial FDU it had
received.
If the device was in the source mode (had already begun
transmitting a FDU), it should resend the FDU beginning
with the first word of the FDU.
Because Option O12 is selected, the device receiving an
ALOHA word should use the Subsystem SAL from the
ALOHA word as the SAL of the ALOHA Response (ALR)
word and for all subsequent bit-oriented protocol
transmissions for that interface.
3.4.12 Validation of FDUs
The receiving MAC sublayer should determine the validity
of the incoming Start of Frame (SOF) word, the MAC
frame, and the End of Frame (EOF) words before passing
the MAC frame to its local Service Client. The SOF, MAC
frame, and EOF are collectively referred to as a Frame Data
Unit (FDU). The following subsections list conditions for
ARINC SPECIFICATION 429 PART 3 - Page 25
which the FDU is said to be invalid in addition to the
conditions already identified in sections 3.3.1.5 and
3.3.2.4 for invalid frames. The contents of invalid MAC
frames should not be passed to the local MAC Service
Client.
3.4.12.1 Missing SOF Word
The Information SOF word should be formatted as
depicted in Attachment 11, Table 11-10 and should be
the first word of the transmitted information FDU. The
Command SOF word should be formatted as depicted in
Attachment 11, Table 11-8 and should be the first word
of the transmitted command FDU. If the SOF word is
not received as the first word, the MAC frame is
invalid.
3.4.12.2 Missing EOF Word(s)
Two EOF words should follow the transmission of the
final data words of an Information MAC frame. They
should be formatted as depicted in Attachment 11,
Table 11-11. If either or both are missing, or are not
formatted as depicted in Attachment 11, Table 11-11,
then the MAC frame is invalid.
One EOF word should follow the transmission of the
final data words of a Command MAC frame. It should
be formatted as depicted in Attachment 11, Table 11-9. c-17
If it is missing, or is not formatted as depicted in
Attachment 11, Table 11-9, then the MAC frame is
invalid.
3.4.12.3 Parity Errors
Bit 32 of each ARINC 429 word should be set to odd
parity for the entire word. Upon receipt of a word, the
receiving unit should verify that each word was
received with odd parity. If any word is received with
even parity, the receiving unit should take no action and
ignore the word.
COMMENTARY
When the receiving MAC sublayer receives a word
with bad parity, it cannot be sure of the intended
label. The word may not even be a part of the FDU,
so by ignoring the offending word, there may still be
a chance of a successful FDU transfer. If the
offending word was intended to be a part of the
FDU, then when the EOF word(s) are received, the
actual word count will not match the expected word
count (and the CRC will probably be invalid). If the
word count is incorrect (or if the CRC is invalid),
then the MAC frame is also invalid, as per Sections
3.4.12.5 and 3.4.12.4 (or Sections 3.3.1.5.3 and
3.3.2.5.1 for invalid CRC).
3.4.12.4 Word Count Errors
Upon receipt of the final EOF word of the FDU, the
receiving MAC sublayer should verify that the actual
number of words received is the number of words
expected, as per bits 18-9 of the SOF word. If the word
counts do not match, the MAC frame is invalid.
 ARINC SPECIFICATION 429 PART 3 - Page 26
3.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL

3.4.12.5 CRC Errors

Upon receipt of the final EOF word of the FDU, the
receiving MAC sublayer should verify the CRC of the
received MAC frame. If the CRC is invalid, the MAC frame
is also invalid and should be discarded.
The FDU should contain an integral number of octets in
c-17 order to pass the FCS.

3.4.13 Inter-FDU Gap Time

An inter-Frame Data Unit gap time, T18, of 10 ms minimum
should be implemented between any two successive MAC
frame transmissions in order to allow the receiving MAC
sublayer sufficient CRC verification time between frames.
Timer T18 is closely related to the generation of the CRC
field for the Information frame. If a CRC is not to be
generated (O15 = No), this timer is not necessary and
implementation is optional.
 ARINC SPECIFICATION 429 PART 3 - Page 27

ATTACHMENTS 1 - 9

Attachments 1 through 9 are included in ARINC Specification 429 Part 1 and therefore are not used in ARINC Specification
429, Part 3. These attachment numbers are not used to maintain consistency with previous versions of ARINC Specification c-16
429.
 ARINC SPECIFICATION 429 PART 3 - Page 28
ATTACHMENT 10
VARIABLES OF BIT-ORIENTED PROTOCOL

Table 10-1 BIT-ORIENTED PROTOCOL EVENTS

EVENT DESCRIPTION OF EVENT STANDARD
VALUE [1]
N1 MAX NUMBER OF RTS REPEATS FOLLOWING NCTS 5
N2 MAX NUMBER OF RTS REPEATS FOLLOWING BUSY 20
N3 MAX NUMBER OF RTS REPEATS FOLLOWING NO RESPONSE 5
c-16
N4 NUMBER OF NAK WORDS RECEIVED BEFORE DECLARING 3
FAILURE OF COMMUNICATION
N5 NUMBER OF SYN WORDS RECEIVED BEFORE DECLARING 3
FAILURE OF COMMUNICATION
N6 MAX NUMBER OF ALO REPEATS FOLLOWING NO RESPONSE 3

Table 10-2 BIT-ORIENTED PROTOCOL APPLICATION SELECTION

APPLICATION CONDITION STANDARD ACTIONS
A1 WHEN T2 N1 EXCEEDED REPORT TO HIGHER LEVEL ENTITY
A2 WHEN T4 N2 EXCEEDED REPORT TO HIGHER LEVEL ENTITY
A3 WHEN T5 N3 EXCEEDED REPORT TO HIGHER LEVEL ENTITY

Table 10-3a BIT-ORIENTED PROTOCOL OPTIONS FOR VERSION 1

OPTION DESCRIPTION STANDARD INTERFACE [1]
O1 Half or Full Duplex Operation Half Duplex
O2 High or Low Speed Bus Low
O3 Automatic CTS when ready No [5]
O4 Accept Auto CTS No [5]
O5 Sys Priority to resolve RTS Conflict Yes
c-16
O6 Reserved --
O7 Reserved --
O8 Use of SOLO Word Yes
O9 Reserved --
O10 Dest Code in RTS/CTS/NCTS/BUSY used Yes
O11 Bit-Protocol verification Yes
O12 Use Subsystem SAL from ALO word No
 ARINC SPECIFICATION 429 PART 3 - Page 29
ATTACHMENT 10
VARIABLES OF BIT-ORIENTED PROTOCOL

Table 10-3b - BIT-ORIENTED PROTOCOL OPTIONS FOR VERSION 3

Option Description Standard Interface [1] Notes
O1 Half or Full Duplex Operation Full Duplex
O2 High or Low Speed Bus High
O3 Automatic CTS when ready N/A
O4 Accept Auto CTS N/A
O5 Sys Priority to resolve RTS Conflict N/A
O6 Spare --
O7 Spare --
O8 Use of SOLO Word Yes 6
O9 Spare --
O10 Destination Code in RTS/CTS/NCTS/BUSY N/A
used
O11 Bit-Protocol verification Yes
O12 Use Subsystem SAL from ALO word Yes
O13 Use of Information or Command frames 7
O14 Use of Pause Function 7 c-17
O15 Generation (Yes) or Non-generation (No) of 32 Yes 8
bit CRC for Information frame

NOTES:

[1] The STANDARD VALUE (or STANDARD INTERFACE) should be used as the default value if a specific value is
not designated in the applicable equipment specification. For example, the standard interface for option 2 (429 bus
speed) defaults to low speed for version 1 systems, unless high speed is specified in equipment specifications.
Values shown as N/A indicate that option cannot be used.

[2] For those timers that are not associated with a repeat sequence, it is intended that a working system has minimized
actual response times. For example: A system should reply with CTS as soon as possible after reception of RTS. It is
not intended that a system take the maximum time T1 to reply to the RTS on a routine basis.

[3] T6 and T7 are used when Option 5 (O5) is not selected.

[4] Implementation of timer T10 is optional. If T10 is not used, T16 should be used.
[5] 03 and 04 should be Yes for expedited file transfer. See Section 2.5.7.3.
[6] The SOLO Word is not bridgeable to Ethernet and should only be used in conjunction with Command frame (non-
bridgeable) interfaces.
[7] Options 13 and 14 are dependent on the applicable equipment interface specification. For a point to point only
interface, such as the CMU/VDR VDL Mode 2 Interface, Option 13 is set to ‘Command Frame’. For equipment
interfaces that may need to be bridgeable to Ethernet, Option 13 is set to ‘Information frame.’ If the Pause Function
option is selected as ‘Yes’, then the Pause function will be formatted into a Command FDU if Option 13 is set to
‘Command Frame’, or into an Information FDU if Option 13 is set to ‘Information Frame’.
[8] Selection of Option 15 is dependent on the applicable equipment interface specification.
 ARINC SPECIFICATION 429 PART 3 - Page 30
ATTACHMENT 10
VARIABLES OF BIT-ORIENTED PROTOCOL

Table 10-4 VARIABLES OF LOW SPEED BIT-ORIENTED PROTOCOL - VERSION 1

TIMER OR
DESIGN GOAL
MIN MAX FOR SOURCE OR
TIME DESCRIPTION VALUE VALUE SINK NOTES REFERENCE
T1 CTS/NCTS Send Time 0 ms 100 ms Goal for Sink 2 2.5.7
T2 RTS Repeat Time 500 ms 700 ms Timer for Source 2.5.7.2
After Receipt of NCTS
T3 Busy Send Time 0 ms 100 ms Goal for Sink 2 2.5.7.3
T4 RTS Repeat Time 15 sec 18 sec Timer for Source 2.5.7.3
After Receipt of Busy
T5 RTS Repeat Time 500 ms 700 ms Timer for Source 2.5.7.4
If No Response
T6 Time of Random Timer to 50 ms 500 ms Goal for Source 3 2.5.8.1
Resolve RTS Conflicts
T7 Increment of Time T6 10 ms 100 ms Goal for Source 3 2.5.8.1
T8 ACK/NAK/SYN Send 0 ms 200 ms Goal for Sink 2 2.5.13
Time
T9 LDU Timeout 2.5 sec 2.7 sec Timer for Sink 2.5.13.2
c-16 Following CTS
2.5.13.6
T10 ACK/NAK Timeout 2.7 sec 3.0 sec Timer for Source 4 2.5.16
T11 Loop Back Send Time 0 ms 100 ms Goal for Sink 2 2.5.17.1
T12 ALO Repeat Time 200 ms 250 ms Timer for Source 2.5.19.1
if No Response to ALO
T13 SOT Send Time 0 ms 200 ms Goal for Source 2 2.5.10
After Receipt of CTS

T14 Incomplete File Timeout 2 min 2.2 min Timer for Sink 2.5.14.3
T15 ALR Send Time 0ms 180 ms Goal for Sink 2 2.5.19.1.2
T16 ACK/NAK Timeout 220 ms 330 ms Timer for Source 2.5.16
After EOT
 ARINC SPECIFICATION 429 PART 3 - Page 31
ATTACHMENT 10
VARIABLES OF BIT-ORIENTED PROTOCOL

Table 10-5 VARIABLES OF HIGH SPEED BIT-ORIENTED PROTOCOL - VERSION 1

TIMER OR
DESIGN GOAL
MIN MAX FOR SOURCE
TIME DESCRIPTION VALUE VALUE OR SINK NOTES REFERENCE
T1 CTS/NCTS Send Time 0 ms 100 ms Goal for Sink 2 2.5.7
T2 RTS Repeat Time 100 ms 140 ms Timer for Source 2.5.7.2
After Receipt of NCTS
T3 Busy Send Time 0 ms 100 ms Goal for Sink 2 2.5.7.3
T4 RTS Repeat Time 1.0 sec 1.2 sec Timer for Source 2.5.7.3
After Receipt of Busy
T5 RTS Repeat Time 150 ms 200 ms Timer for Source 2.5.7.4
If No Response
T6 Time of Random Timer to 50 ms 500 ms Goal for Source 3 2.5.8.1
Resolve RTS Conflicts
T7 Increment of Time T6 10 ms 100 ms Goal for Source 3 2.5.8.1
T8 ACK/NAK/SYN Send 0 ms 200 ms Goal for Sink 2 2.5.13
Time
T9 LDU Timeout 400 ms 440 ms Timer for Sink 2.5.13.2
Following CTS
2.5.13.6
T10 ACK/NAK Timeout 600 ms 660 ms Timer for Source 4 2.5.16 c-16
After CTS
T11 Loop Back Send Time 0 ms 100 ms Goal for Sink 2 2.5.17.1
T12 ALO Repeat Time 200 ms 250 ms Timer for Source 2.5.19.1
if No Response to ALO
T13 SOT Send Time 0 ms 100 ms Goal for Source 2 2.5.10
After Receipt of CTS

T14 Incomplete File Timeout 10 sec 11 sec Timer for Sink 2.5.14.3
T15 ALR Send Time 0 ms 180 ms Goal for Sink 2 2.5.19.1.2
T16 ACK/NAK Timeout 220 ms 330 ms Timer for Source 2.5.16
After EOT
 ARINC SPECIFICATION 429 PART 3 - Page 32
ATTACHMENT 10
VARIABLES OF BIT-ORIENTED PROTOCOL

Table 10-6 - VARIABLES OF HIGH SPEED CONNECTIONLESS BIT-ORIENTED PROTOCOL - VERSION 3

TIME DESCRIPTION MIN VALUE MAX VALUE TIMER OR NOTES REFERENCE
DESIGN GOAL
FOR SOURCE
OR SINK
T1
T2
T3
T4
T5
T6
T7
c-17 T8
T9
T10
T11
T12 ALO Repeat Time if No 200 ms 250 ms Timer for Source
Response to ALO
T13
T14
T15 ALR Send Time 0 ms 180 ms Goal for Sink
T16
T17 Incomplete FDU 750 ms 1 sec Timer for Sink
Timeout
T18 Inter-FDU Gap Time 10 ms N/A Timer for Source 1

NOTE:

[1] The minimum value is specified to give the sink time to finish processing an FDU before the next FDU arrives.
The designer is encouraged to use the min value of 10 ms in order to make optimal use of the ARINC 429 data
bus bandwidth. A maximum value cannot be specified because of the aperiodic nature of the data sent by most
applications that use the ARINC 429W file transfer protocol. If the LRU does not have another FDU to transmit
then this gap will be very large (seconds, minutes, hours!).
 ARINC SPECIFICATION 429 PART 3 - Page 33
ATTACHMENT 10
VARIABLES OF BIT-ORIENTED PROTOCOL

Table 10-7 VARIABLES OF LOW SPEED CONNECTIONLESS BIT-ORIENTED

PROTOCOL - VERSION 3 c-16

TIME DESCRIPTION MIN VALUE MAX VALUE TIMER OR NOTES REFERENCE

DESIGN GOAL
FOR SOURCE
OR SINK
T1
T2
T3
T4
T5
T6
T7
T8
T9 c-18

T10
T11
T12 ALO Repeat Time if No 200 ms 250 ms Timer for Source
Response to ALO
T13
T14
T15 ALR Send Time 0 ms 180 ms Goal for Sink
T16
T17 Incomplete FDU 7.5 seconds 1 sec Timer for Sink
Timeout
T18 Inter-FDU Gap Time 10 ms N/A Timer for Source 1

NOTE:

[1] The minimum value is specified to give the sink time to finish processing an FDU before the next FDU arrives.
The designer is encouraged to use the min value of 10 ms in order to make optimal use of the ARINC 429 data
bus bandwidth. A maximum value cannot be specified because of the aperiodic nature of the data sent by most
applications that use the ARINC 429W file transfer protocol. If the LRU does not have another FDU to transmit
then this gap will be very large (seconds, minutes, hours!).
 ARINC SPECIFICATION 429 PART 3 - Page 34
ATTACHMENT 10
VARIABLES OF BIT-ORIENTED PROTOCOL

NOTES:

1 The STANDARD VALUE (or STANDARD INTERFACE) should be used as the default value if a specific value is
not designated in the applicable equipment specification. For example, the standard interface for option 2 (429 bus
c-16 speed) defaults to low speed for version 1 systems, unless high speed is specified in equipment specifications.
Values shown as N/A indicate that option cannot be used.

2 For those timers that are not associated with a repeat sequence, it is intended that a working system has minimized
actual response times. For example: A system should reply with CTS as soon as possible after reception of RTS. It
is not intended that a system take the maximum time T1 to reply to the RTS on a routine basis.

3 T6 and T7 are used when Option 5 (O5) is not selected.

4 Implementation of timer T10 is optional. If T10 is not used, T16 should be used.

c-16 5 O3 and O4 should be Yes for expedited file transfer. See Section 2.5.7.3.
 ARINC SPECIFICATION 429 PART 3 - Page 35
ATTACHMENT 11
BIT-ORIENTED DATA FILE TRANSFER WORD FORMATS

NOTE: All reserved fields should be set to binary 0

Table 11-1 GENERAL WORD FORMAT

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
GFI, Control c-16
[1] P Word Type Data or Word DATA SAL
Type
Extensions

Table 11-1A WORD TYPE

31 30 29 WORD TYPE
0 0 0 Full Binary Data Word
0 0 1 Partial Binary Data Word
0 1 0 Start of Frame – Version 3 c-16
0 1 1 End of Frame – Version 3
1 0 0 Protocol Word
1 0 1 Solo Word
1 1 0 Start Of Transmission – Version 1
1 1 1 End Of Transmission – Version 1

Table 11-2 FULL DATA WORD

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

[2] P 0 0 0 n5 n4 n3 n2 n1 SAL

Table 11-3 PARTIAL DATA WORD

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
[2] P 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 n1 SAL
P 0 0 1 1 0 0 1 0 0 0 0 0 0 0 0 n2 n1 SAL
[3] P 0 0 1 1 0 1 0 0 0 0 0 n3 n2 n1 SAL
P 0 0 1 1 0 1 1 n4 n3 n2 n1 SAL

Table 11-4 PROTOCOL WORD

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
RTS P 1 0 0 0 0 0 1 Destination Code [4] Word Count [5] SAL
CTS P 1 0 0 0 0 1 0 Destination Code . Word Count . SAL
NCTS P 1 0 0 0 0 1 1 Destination Code . Status Code [6] SAL
BUSY P 1 0 0 0 1 0 0 Destination Code . Status Code . SAL
NAK P 1 0 0 0 1 0 1 File Sequence Number Status Code . SAL
ACK P 1 0 0 0 1 1 0 File Sequence Number LDU Sequence Number SAL
AL0 P 1 0 0 0 1 1 1 Subsystem SAL [7] 0 0 0 0 Version No. SAL
[10]
ALR P 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Version No. SAL c-16
[10]
SYN P 1 0 0 1 0 0 1 File Sequence Number Status Code [6] SAL
ARINC SPECIFICATION 429 PART 3 - Page 36
ATTACHMENT 11
BIT-ORIENTED DATA FILE TRANSFER WORD FORMATS

Table 11-4A ALO-ALR VERSION NUMBER (See Appendix H)

12 11 10 9 APPLICABILITY NOTES
0 0 0 0 Changes to Sec. 2.5 by Supplement 12 of ARINC 429, Part 3 8
0 0 0 1 Changes to Sec. 2.5 through Supplement 16 of ARINC 429, Part 3 8
0 0 1 0 Obsolete, formerly defined in Sec. 2.6 of ARINC 429, Part 3
c-16 0 0 1 1 Section 3.0 of ARINC 429, Part 3
0 1 0 0 Reserved
. Reserved
. Reserved
1 1 1 0 Reserved
1 1 1 1 Reserved

Table 11-4B ALO-ALR WINDOW SIZE

c-16
This table deleted by Supplement 16.

Table 11-5 SOLO WORD

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
TEST P 1 0 1 0 0 0 0 16-Bit Test Pattern SAL
LOOP P 1 0 1 0 0 0 1 16-Bit Loop Back SAL
SOLO P 1 0 1 I. D. 16-Bit Data Field SAL

Table 11-6 START OF TRANSMISSION

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
c-16 SOT P 1 1 0 GFI File Sequence Number LDU Sequence Number SAL
 ARINC SPECIFICATION 429 PART 3 - Page 37

ATTACHMENT 11
BIT-ORIENTED DATA FILE TRANSFER WORD FORMATS

Table 11-6A GENERAL FORMAT IDENTIFIER (GFI)

Bit
28 27 26 25 Description Notes
0 0 0 0 Reserved 1
0 0 0 1 Reserved
0 0 1 0 Command-Control Data
0 0 1 1 General Purpose Bit-Oriented Protocol (GPBOP)
0 1 0 0 ISO 9577
0 1 0 1 Reserved
0 1 1 0 Reserved c-17
0 1 1 1 Reserved
1 0 0 0 Reserved
1 0 0 1 Reserved
1 0 1 0 Reserved
1 0 1 1 Reserved
1 1 0 0 Reserved
1 1 0 1 Reserved
1 1 1 0 ACARS VHF Format
1 1 1 1 Extended GFI

NOTE:

[1] For consistency with Version 1, the GFI value (0000) is discouraged. The value 0000 should only be used for
local communications between 2 LRUs that will never need to use a different file format on that ARINC 429
bus. The data format for the GFI ‘0000’ is unique to that particular interface and is not defined herein.

Table 11-7 END OF TRANSMISSION

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 c-14
EOT 1 1 1 0 0 0 X LSB Cyclic Redundancy Check (CRC) 9 MSB SAL

NOTE: Bit 25 of the EOT is the final LDU bit.

Table 11-7A FINAL LDU BIT

25 DESCRIPTION
0 Not Final LDU
1 Final LDU
 ARINC SPECIFICATION 429 PART 3 - Page 38

ATTACHMENT 11
BIT-ORIENTED DATA FILE TRANSFER WORD FORMATS

Table 11-8 COMMAND FRAME SOF

Version 3 Command Frame SOF

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P 0 1 0 GFI CT Reserved I/C ARINC 429 Word Count U SAL

Where:
P – 32 Bit Parity
GFI – General Format Identifier (GFI) Field
CT – Command Type Field
00 Command Path
01 Data Path
10 MAC Control
11 Reserved
I/C – Information/Command Frame Identifier Field; 00-Information; 01-Command, 10, 11-Reserve
Word Count Field – 10 bits for a Command Frame, Max Command Frame size = 2552 bytes
c-17 U SAL – Unique (standard ARINC 429) System Address Label (SAL) (same as Version 1)

Table 11-9 COMMAND FRAME EOF

Version 3 Command Frame EOF

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P 0 1 1 0 0 0 1 LSB FCS (16 Bit CRC) MSB U SAL

Where:
P – 32 Bit Parity
Bit 25 (Command Frame Final Bit) for EOF word always set to 1
FCS – Frame Check Sequence, 16-bit CRC for Command Frame

Table 11-10 INFORMATION FRAME SOF

Version 3 Command Frame SOF

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P 0 1 0 Reserved I/C ARINC 429 Word Count M/B/U SAL

Where:
P – 32 Bit Parity
I/C – Information/Command Frame Identifier Field; 00-Information; 01-Command; 10, 11- Reserved
Word Count Field – 10 bits for an Information Frame – Max Information Frame Size = 2550 bytes, Limit for
Bridgeability = 1500 bytes
M/B/U SAL – Multicast/Bridge/Unique (standard ARINC 429) System Address Label (SAL)
 ARINC SPECIFICATION 429 PART 3 - Page 39

ATTACHMENT 11
BIT-ORIENTED DATA FILE TRANSFER WORD FORMATS
Table 11-11 INFORMATION FRAME EOF
Version 3 Command Frame EOF

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P 0 1 1 0 0 0 0 FCS (32-Bit CRC) MSB M/B/U SAL c-17
P 0 1 1 0 0 0 1 LSB FCS (32-Bit CRC) M/B/U SAL

Where:
P – 32 Bit Parity
FCS – Frame Check Sequence, 32-bit CRC for Information Frame
Bit 25 for first half of Information Frame EOF word = 0
Bit 25 for second half of Information Frame EOF word = 1
ARINC SPECIFICATION 429 PART 3 - Page 40

ATTACHMENT 11
BIT-ORIENTED DATA FILE TRANSFER WORD FORMATS

NOTES

[1] All words are transmitted using odd parity (denoted by P in bit 32).

[2] The MSB/LSB determination of the “Data” field for Full and Partial Data words is as follows:

The ordering of octets (or ASCII characters) is from right to left, i.e.:

A) The first (most significant) octet is in bits 16-9 of the first Data word.

B) The second octet is in bits 24-17 of the first Data word ,etc.

The ordering of bits within each octet (or ASCII characters) is:

A) The LSB of the first octet is in bit 9 of the first Data word.

B) The MSB of the first octet is in bit 16 of the first Data word.

C) The LSB of the second octet is in bit 17 of the first Data word, etc.

EXAMPLE: The encoding of “PHX” (using 7-bit ASCII characters with all pad bits set to 0) using one
Full Data Word and one Partial Data Word is:

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

“X” “H” “P”

(Lower ½)
Word P 0 0 0 1 0 0 0 0 1 0 0 1 0 0 0 0 1 0 1 0 0 0 0 SAL

“X”
(Upper ½)
Data Word 2 P 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 SAL

[3] Bits 24 through 31 of Partial Data Words are coded to avoid conflict with old RTS words, defined in Appendix F,
which contains the ISO Alphabet control character "DC2" in bits 29 through 23.

[4] Destination Codes are contained in Attachment 11A.

[5] Word Count values of 0000 0000 through 0000 0010 are not used; i.e. values of Word Count may be 3 through 255
(03 through FFh).
c-16
[6] Status Codes are contained in Attachment 11B.

[7] This is the System Address Label of the system which is sending out the ALO.

[8] Versions 0 and 1 are equivalent for the ALOHA (ALO) and ALOHA RESPONSE (ALR) Protocol Words.

[9] The MSB/LSB determination for all Link Layer CRC Computation is:

Bit 9 of the first Data word is the MSB (coefficient of the highest order term) of the polynomial representing the
c-14 “message”. The LSB (coefficient of the lowest order term) of the polynomial representing the “message” is the most
significant bit of the last octet or character (which contains valid non-zero data) which will be found in the final data
word preceding the EOT Word.

c-14 [10] Bits 12 through 9 define the version number of the ARINC 429 bit-oriented protocol, as referenced in Table 11-4A.
 ARINC SPECIFICATION 429 PART 3 - Page 41
ATTACHMENT 11A
DESTINATION CODES

BIT CODE [1]

CHARARACTER
DESTINATION 22222111 NOTES
CODE 43210987
CABIN TERMINAL (1-4) 1-4
USER TERMINAL (5-8) 5-8
FMC, LEFT SIDE A 01000001
FMC, RIGHT SIDE B 01000010
CONTROL DISPLAY UNIT C 01000011 c-15
DFDAU D 01000100
CABIN PACKET DATA FUNCTION E 01000101 c-15
CFDIU F 01000110
GROUND STATION G 01000111
HF LINK H 01001000
EICAS/ECAM/EFIS I 01001001
AUTOMATIC DEPENDENT SURVEILLANCE J 01001010 c-15
UNIT (ADSU)
KEYBOARD/DISPLAY K 01001011
Unassigned L 01001100 c-18
ACARS MANAGEMENT UNIT (MU) M 01001101
FMC, CENTER N 01001110
OPTIONAL AUXILIARY TERMINAL O 01001111 c-16
PRINTER P 01010000
SATELLITE DATA UNIT, LEFT SIDE (SDU 1) Q 01010001 2
c-15
SATELLITE DATA UNIT, RIGHT SIDE (SDU 2) R 01010010 2
SATELLITE LINK S 01010011
HFDR Left T 01010100 6 c-18
HFDR Right U 01010101
VHF LINK (VDR) V 01010110
TAWS W 01010111
CVR X 01011000
Unassigned Y 01011001
c-18
Unassigned Z 01011010
INMARSAT SATELLITE LINK CONTROL CODE VT 00001011 3, 4
ICO SATELLITE LINK CONTROL CODE CR 00001101 3, 4
GLOBALSTAR SATELLITE LINK CONTROL CODE SO 00001110 3, 4
 ARINC SPECIFICATION 429 PART 3 – Page 42

ATTACHMENT 11 A
DESTINATION CODES

NOTES:
c-18 [1] The Destination Code may be a 7-bit ISO Alphabet No. 5 code with no parity, or, alternatively, a binary value.
Bit 24 should contain a zero.
[2] Origin/Destination Codes Q and R are used when the SDU transmits/receives onboard messages as an ACARS
end system.

[3] These are non-printable control codes (reference ARINC 429 Part 1 Attachment 5).
[4] These codes are used for the specific satellite links indicated; character code "S" is used for any available non-
specific satellite link.
c-18
[5] Origin/Destination Codes T and U are used when the HFDR transmits/receives onboard messages as an ACARS
End System. The code H is distinguished from codes T and U in that the H is used to designate the HFDR as
the downlink medium for a message while the T and U are used to indicate that the message is to be consumed
by the DFDR.
[6] Transponder (XPDR) was removed from the DESTINATION column.
 ARINC SPECIFICATION 429 PART 3 - Page 43

ATTACHMENT 11B
STATUS CODES

CODE (HEX) DESCRIPTION NAK NCTS BUSY SYN

00 No Information X X X X
01 User Defined X X X X
02 User Defined X X X X
. . X X X X
. . X X X X
. . X X X X
7E User Defined X X X X
7F User Defined X X X X
80 Missing SOT Word X
81 LDU Sequence Number Error X X
82 Invalid GFI X
83 Missing EOT Word X
84 Invalid Destination Code X X
85 CRC Error X
c-15
86 LDU Time-Out Error X
87 Restart Initialization X X
88 Word Count Error X X
89 Word Count Error/Input Overrun X
8A Word Count Error/Parity Error X
8B Sink Flow Control X X
8C Buffer Full X X
8D Device Off-Line X
8E File Time-Out Error X
8F Window with Multiple FSNs X
90 Missing LDU Control Word X
91 Remaining LDUs/Received LDUs Error X c-15
92 Window Size Exceeds Sink’s Receive X
Capability
93 Invalid LDU Count in Window X
94 Invalid EOT in Window X
95 New File with Previous Incomplete X
96 Reserved
. .
. .
FE Reserved
FF Reserved
 ARINC SPECIFICATION 429 PART 3 - Page 44

ATTACHMENT 11C
ALOHA/ALOHA RESPONSE PROTOCOL WORD DEFINITION

Table 11C-1 VERSION 1 ALOHA INITIAL (ALO) PROTOCOL WORD EXAMPLE

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P Protocol ALO Subsystem SAL of originator Reserved [2] Version SAL
[3] Number [1]
1 0 0 0 1 1 1 0 0 0 0 0 0 0 1

[1] See Table 11-4A for version number.

c-16 [2] Reserved fields should be set to binary 0.

[3] This field should contain the SAL of the device sending the ALOHA word, with bit 17 as the most
significant bit and bit 24 as the least significant bit of the subsystem SAL.
Table 11C-2 VERSION 1 ALOHA RESPONSE (ALR) PROTOCOL WORD EXAMPLE

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P Protocol ALR Reserved [2] Ver. Number [1] SAL
1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1

[1] See Table 11-4A for version number.

[2] Reserved fields should be set to binary 0.

NOTE: Table 11-C3 has been moved to Attachment 11, Table 11-4C.
 ARINC SPECIFICATION 429 PART 3 – Page 45

ATTACHMENT 12
VERSION 1 FILE TRANSFER EXAMPLE

SOURCE SINK

AIRLINE
SOURCE

RTS WORD

ORIGINAL
CTS WORD
DATA

FILE SOT WORD 1

DATA WORD 2

DATA WORD 3

o FIRST LDU
o
o

DATA WORD 254

EOT WORD 255

ACK WORD

RTS WORD

CTS WORD

SOT WORD 1

DATA WORD 2
AIRCRAFT
DATA WORD 3 DESTINATION

LAST LDU DATA WORD 4

DATA WORD 5 RECEIVED

DATA WORD 6 DATA

EOT WORD 7 FILE

ACK WORD
 ARINC SPECIFICATION 429 PART 3 – Page 46

ATTACHMENT 12A
FIELD MAPPING EXAMPLE

B B B B B B B B B B B B B B B B B B B B B B B B
24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
CRC DATA
LSB MSB LSB MSB

c-13
Semi octet

FIRST WORD Octet

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
n5 n4
P 0 0 0 B B B B B n3 B B n2 B B n1 B SAL
20 17 16 13 12 9 8 5 4 1

SECOND WORD
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
n1
P 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 B B SAL
c-14 24 21

EOT WORD

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

P 1 1 1 0 0 0 * LSB CRC MSB SAL

* Final LDU Bit

This example takes 24 bits of data and puts it into two data words. For the CRC computation, the MSB is the bit
position that represents the coefficient of the highest order term of the polynomial.
 ARINC SPECIFICATION 429 PART 3 - Page 47

ATTACHMENT 13
PROTOCOL DETERMINATION PROCEDURE DIAGRAMS

Diagram 13-1 PROTOCOL DETERMINATION PROCEDURE DIAGRAM (TWO BILINGUAL UNITS)

Assume that both Unit A and Unit B are capable of communicating using both ARINC 429 character-oriented file transfer format
or bit-oriented file transfer format. Assume Unit A will initiate the exchange to determine the protocol to be used.

UNIT A UNIT B

ALO

ALR

BIT-ORIENTED COMMUNICATIONS ESTABLISHED

Diagram 13-2 PROTOCOL DETERMINATION PROCEDURE DIAGRAM (ONE BILINGUAL

UNIT AND ONE CHARACTER-ONLY UNIT)

Assume that Unit A is capable of communicating using both ARINC 429 character-oriented file transfer format or bit-oriented file
transfer format. Assume that Unit B is only capable of communicating using the ARINC 429 character-oriented file transfer
format. Assume Unit A will initiate the exchange to determine the protocol to be used.

UNIT A UNIT B

ALO

ALO

ALO

CHARACTER-ORIENTED RTS

CHARACTER-ORIENTED CTS

CHARACTER-ORIENTED COMMUNICATIONS ESTABLISHED

Assume Unit B will initiate the exchange to determine the protocol to be used.

UNIT A UNIT B

CHARACTER-ORIENTED RTS

CHARACTER-ORIENTED CTS

CHARACTER-ORIENTED COMMUNICATIONS ESTABLISHED

ARINC SPECIFICATION 429 PART 3 - Page 48
ATTACHMENT 13 (cont'd)
PROTOCOL DETERMINATION PROCEDURE DIAGRAMS

Diagram 13-3 PROTOCOL DETERMINATION PROCEDURE DIAGRAM

(TWO CHARACTER-ONLY UNITS)

Assume that Unit A is only capable of communicating using the bit-oriented file transfer format. Assume that Unit B is capable
of communicating only using the ARINC 429 character-oriented file transfer format. Assume Unit A will initiate the exchange to
determine the protocol to be used. The resulting "No Response" conclusion accurately identifies the inability of the two units to
communicate.

UNIT A UNIT B

ALO

ALO

ALO

NO RESPONSE COMMUNICATIONS NOT POSSIBLE

Assume Unit B will initiate the exchange. The resulting “No Response” conclusion accurately identifies the inability of the
two units to communicate.

UNIT A UNIT B

CHARACTER-ORIENTED RTS

CHARACTER-ORIENTED RTS

CHARACTER-ORIENTED RTS

COMMUNICATIONS NOT POSSIBLE NO RESPONSE

 ARINC SPECIFICATION 429 PART 3 – Page 49

ATTACHMENT 13A
ALOHA VERSION DETERMINATION SEQUENCE

Example #1
SOURCE Device : "A" SINK Device : "B"
Versions of protocol Versions of protocol
supported by this supported by this
device (1, 2 & 5) device (1, 3 & 6)

ALO: Version = 5
ALR: Version = 3

ALO: Version = 2

ALR Version = 1
Time Time

Example #2
SOURCE Device : "A" SINK Device : "B"
Versions of protocol Versions of protocol
supported by this supported by this
device (1, 2 & 5) device (1, 2, 3 & 6)

ALO: Version = 5
ALR: Version = 3

ALO: Version = 2

ALR Version = 1
Time Time

Example #3
SOURCE Device : "A" SINK Device : "B"
Versions of protocol Versions of protocol
supported by this supported by this
device (1, 2 & 5) device (1)

ALO: Version = 5
ALR: Version = 1

Time Time
 ARINC SPECIFICATION 429 PART 3 - Page 50

ATTACHMENT 14
SYSTEM ADDRESS LABELS

c-16 The listing of System Address Label (SAL) assignments is contained in Attachment 11 to ARINC Specification 429, Part 1.
 ARINC SPECIFICATION 429 PART 3 - Page 51

ATTACHMENT 15

NOTE: This attachment has been deleted by Supplement 16.

This Attachment number is not used in this Specification to maintain consistency with previous versions of ARINC c-16
Specification 429 prior to its separation into 3 parts by Supplement 15 and to avoid confusion among the parts.
 ARINC SPECIFICATION 429 PART 3 - Page 52

ATTACHMENT 16

NOTE: This attachment has been deleted by Supplement 16.

c-16 This Attachment number is not used in this Specification to maintain consistency with previous versions of ARINC
Specification 429 prior to its separation into 3 parts by Supplement 15 and to avoid confusion among the parts.
 ARINC SPECIFICATION 429 PART 3 - Page 53

ATTACHMENT 17
FLOW DIAGRAM USED TO DETERMINE CHARACTER-ORIENTED VS BIT-ORIENTED PROTOCOL

begin

attempt normal
bit-oriented link bit-oriented
protocol established communications

failed normal no
comm response

attempt normal
char-oriented link
established char-oriented
protocol communications
failed normal no
comm response

wait 0-15 seconds

 ARINC SPECIFICATION 429 PART 3 - Page 54

ATTACHMENT 18
MAC SUBLAYER SUPPORT DIAGRAMS

(3) Higher Layer LLC Service MAC Service MAC Service LLC Service
Entity Client Client Client Client

(2) Data Link Layer

LLC Sublayer MAC Service MAC Service

Client Client
(802.2 LLC) (802.2 LLC)

c-17
802.3-LENGTH 802.3-TYPE

Media Access
Control (MAC) MAC Control MAC Control
Sublayer
MAC Service Entity MAC Service Entity

Physical Signaling Physical Signaling

(1) Physical Signaling (429) (429)
Layer

NOTE: The MAC Control Sublayer is normally a pass through except for MAC Control PDUs that are processed by the
MAC Control sublayer entity and are not passed to higher layers. The operation of the MAC Control Sublayer
is defined in IEEE 802.3 Clause 31. MAC Control Functions are defined Section 3.2.4 of this Specification.

Figure 18-1 - MAC Sublayer and its Service Clients

 ARINC SPECIFICATION 429 PART 3 - Page 55

ATTACHMENT 18
MAC SUBLAYER SUPPORT DIAGRAMS

MAC Service
Client MA_CONTROL.Indication
MA_DATA.Indication
MA_CONTROL.Request
MA_DATA.Request

429 MAC Control Sublayer

Transmit Frame c-17

MAC Receive Frame
Sublayer
(destination address, length/type, data, (destination and source addresses, length/type,
service class) data, reception status, service class)

429 Medium Access Control

Transmit
Receive

Physical
Layer 429 Physical

Figure 18-2 - MAC Control Sublayer Support Of Interlayer Service Interfaces

 ARINC SPECIFICATION 429 PART 3 - Page 56

ATTACHMENT 19
COMMAND FRAME DATA UNIT (FDU) STRUCTURE AND EXAMPLES

Table 19-1 V3 Command Frame SOF

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P 0 1 0 GFI CT Rsvd I/C ARINC 429 Word Count U SAL

Where:
P – 32 bit Parity
GPI – General Format Identifier (GFI) Field
CT – Command Type Field
00 Command Path
01 Data Path
10 MAC Control
11 Reserved
I/C – Information/Command Frame Identifier Field; 00 – Information; 01 – Command, 10, 11 – Reserved
Word Count Field – 10 bits for a Command Frame, Max Command Frame size = 2552 bytes
U SAL – Unique (standard ARINC 429) System Address Label (SAL) (same as Version 1)

c-17 Table 19-2 V3 Command Frame (Full and Partial) Data Words

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P 0 0 0 DATA U SAL
P 0 0 0 DATA U SAL
P 0 0 0 DATA U SAL
P 0 0 0 DATA U SAL

Table 19-3 V3 Command Frame EOF

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
0 1 1 0 0 0 1 LSB FCS (16-Bit CRC) MSB U SAL

Where:
Bit 25 (Command Frame Final Bit) for EOF word always set to 1
FCS – Frame Check Sequence, 16-bit CRC for Command Frame
 ARINC SPECIFICATION 429 PART 3 - Page 57

ATTACHMENT 19
COMMAND FRAME DATA UNIT (FDU) STRUCTURE AND EXAMPLES

Table 19-4 Example of Command Frame Data Unit (FDU) Containing a MAC Control Frame Requesting a
5 Pause Quanta (25 millisecond) Delay

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

V3 Command Frame SOF:

P 0 1 0 X X X X 1 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 U SAL

V3 Command Frame (Full and Partial) Data Words: c-17

P 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 0 0 0 1 0 0 0 U SAL
P 0 0 1 1 0 1 0 0 0 0 0 0 0 0 0 0 1 0 1 0 0 0 0 U SAL

V3 Command Frame EOF:

P 0 1 1 0 0 0 1 LSB FCS (16-Bit CRC) MSB U SAL

Where:
GFI Field = X’s as placeholder for actual values used over interface (See Table 11-6A of Attachment 11)
Pause Opcode – 16 bit field = 8808 hex
Request Operand – 16 bit field = Pause Time = 5 Pause Quanta = 0005 hex
 ARINC SPECIFICATION 429 PART 3 - Page 58

ATTACHMENT 20
INFORMATION FRAME DATA UNIT (FDU) STRUCTURE AND EXAMPLE

Table 20-1 Version 3 Information Frame SOF

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P 0 1 0 Reserved I/C ARINC 429 Word Count M/B/U SAL

Where:
P – 32 bit Parity
I/C – Information/Command Frame Identifier Field; 00-Information; 01-Command; 10, 11-Reserved
Word Count Field – 10 bits for an Information Frame – Max Information Frame Size = 2550 bytes,
Limit for Bridging = 1500 bytes
M/B/U SAL – Multicast/Bridge/Unique (standard ARINC 429) System Address Label (SAL)

Table 20-2 Version 3 Information Frame (Full and Partial) Data Words

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P 0 0 0 Destination LSB M/B/U SAL
P 0 0 0 Destination M/B/U SAL
P 0 0 0 Source LSB MSB Destination M/B/U SAL
P 0 0 0 Source M/B/U SAL
P 0 0 0 Length/Type LSB MSB Source M/B/U SAL
P 0 0 0 Data MSB Length/Type M/B/U SAL
P 0 0 0 Data M/B/U SAL
c-17 P 0 0 0 Data M/B/U SAL
P 0 0 0 Data M/B/U SAL

Where:
P – 32 bit Parity
Destination – 48 Bit MAC Destination Address
Source – 48 Bit MAC Source Address
Length/Type – 16 bit field

Table 20-3 Version 3 Information Frame EOF

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
P 0 1 1 0 0 0 0 FCS (32-Bit CRC) MSB M/B/U SAL
P 0 1 1 0 0 0 1 LSB FCS (32-Bit CRC) M/B/U SAL

Where:
FCS – Frame Check Sequence, 32-bit CRC for Information Frame
Bit 25 for first half of Information Frame EOF word = 0
Bit 25 for second half of Information Frame EOF word = 1
 ARINC SPECIFICATION 429 PART 3 - Page 59

ATTACHMENT 20
INFORMATION FRAME DATA UNIT (FDU) STRUCTURE AND EXAMPLE

Table 20-4: Example of Information Frame Data Unit (FDU) Containing a MAC Control Frame Requesting
a 5 Pause Quanta (25 millisecond) Delay

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

V3 Information Frame SOF:

P 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 U SAL

V3 Information Frame (Full and Partial) Data Words:

c-17
P 0 0 0 X X X X X X X X X X X X X X X X X X X X U SAL
P 0 0 0 X X X X X X X X X X X X X X X X X X X X U SAL
P 0 0 0 Y Y Y Y Y Y Y Y Y Y Y Y X X X X X X X X U SAL
P 0 0 0 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y U SAL
P 0 0 0 1 0 0 0 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y U SAL
P 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 0 0 0 U SAL
P 0 0 1 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 U SAL

V3 Information Frame EOF:

P 0 1 1 0 0 0 0 FCS (32-Bit CRC) MSB U SAL

P 0 1 1 0 0 0 1 LSB FCS (32-Bit CRC) U SAL

Where:
Destination – 48 Bit MAC Destination Address = X’s as placeholders (see ARINC Specification 664)
Source – 48 Bit MAC Source Address = Y’s as placeholders (see ARINC Specification 664)
Length/Type – 16 bit field = Pause Opcode = 8808 hex
Request Operand – 16 bit field = Pause Time = 5 Pause Quanta = 0005 hex
 ARINC SPECIFICATION 429 PART 3 - Page 60

APPENDICES A - E

Appendices A through E are included in ARINC Specification 429, Part 1, ARINC Specification 429 and therefore not used
c-16 in this Part to avoid potential confusion due to duplication. In addition, this approach is used to maintain consistency with
previous versions of ARINC Specification 429 when it was published as a whole (through Supplement 14).
 ARINC SPECIFICATION 429 PART 3 - Page 61

APPENDIX F
FORMER AIM AND FILE DATA TRANSFER TECHNIQUES

AEEC Staff Note: See Supplements 4, 5, 6, 7. And 11 of ARINC Specification 429 Part 1 for changes prior to division of c-18
ARINC Specification 429 into separate parts.

The information contained in Sections F-2.1.5.2, F-2.1.5.3, F-2.3.1.4 and F-3.2 of this Appendix is no longer applicable to
ARINC Specification 429. The contents of Section F-2.3.1.5 provides guidance for character-oriented file transfer protocols
reflected in ARINC equipment characteristics. The information is contained herein for reference purposes.

COMMENTARY

Bit-oriented file transfer is the preferred protocol (See Section 2.5 of Part 3 of ARINC Specification 429) for use in new
applications. The guidance for character-oriented protocol was removed from the body of the specification to avoid the
continuation of its use, but retained herein for those who need to understand the basis for character-oriented protocol
already implemented.

F-2.1.5 Sign/Status Matrix

F-2.1.5.2 AIM Data

The order function (first, intermediate, last or control) of AIM or maintenance data should be encoded in bit numbers 30 and
31 of the word as shown in the table below. See Section F-2.3.1.4 of this document for definitions of the terms “Initial
Word”, “Control Word”, “Intermediate Word” and “Final Word.”

AIM DATA SIGN/STATUS MATRIX

BIT
31 30 MEANING
0 0 Intermediate Word
0 1 Initial Word
1 0 Final Word
1 1 Control Word

F-2.1.5.3 Character-Oriented File Transfer

The order and function (first, intermediate, last and control) of text and the sign (Plus/Minus, North/South, etc.) of numeric
data transferred by file transfer should be encoded in bits 30 and 31 of each word as shown in the table below.

CHARACTER-ORIENTED FILE TRANSFER STATUS MATRIX

BIT TEXT DATA
31 30
0 0 Intermediate Word Plus, North, etc.
0 1 Initial Word Not Defined
1 0 Final Word Not Defined
1 1 Intermediate Word Minus, South etc.

Alternatively, the SSM field may be used to describe position in a series of data words (initial, intermediate, final) or word
content (control word). Sections F-2.3.1.5.2 through F-2.3.1.5.4 contain the definitions of the terms initial, intermediate and
final words.

F-2.3.1 Digital Language

F-2.3.1.4 AIM Data

AIM data (Acknowledgement, ISO Alphabet No. 5 and Maintenance information encoded in dedicated words) should be
handled in the manner described in this section.

All three of these applications may involve the transfer of more than 21 bits per “data package”. Source equipment should
format such long messages into groups of 32-bit DITS words, each word containing the relevant application label (see
ARINC Specification 429, Part 1, Attachment 1) in bits 1 through 8, and a sign/status matrix code in bits 30 and 31.
ARINC SPECIFICATION 429 PART 3 - Page 62

APPENDIX F
FORMER AIM AND FILE DATA TRANSFER TECHNIQUES

Bit 32 should be encoded to render word parity odd. The first word of each group should contain the sign/status matrix code
defined for “initial word” in F-2.1.5.1. It should also contain, in bits 9 through 16, the binary representation of the number of
words in the group, except that when this word is the only word to be transmitted, the total number of information bits to be
transmitted is 13 or less) bits 9 through 16 should all be binary “zeros”. See ARINC Specification 429, Part 1, Attachment 6
for word format.

When the word application label is assigned in ARINC Specification 429, Part 1, Attachment 1 for Acknowledgement Data,
bits 17 through 29 of this initial word may be used for information transfer. When the word application label is either of
those assigned in ARINC Specification 429, Part 1, Attachment 1 Maintenance Data (ISO Alphabet No. 5), bits 17 through
22 should be binary 'zeros” (spares). When the label is for ISO Alphabet No. 5 Messages, bits 17 through 22 are used for
unit addressing. Bit usage is given in the table below.

BIT FUNCTION
22 21 20 19 18 17
0 0 0 0 0 0 All Call, All Groups
0 0 X X X X Group 0, Units 1-15
0 1 0 0 0 0 Group 1, All Call
0 1 X X X X Group 1, Units 1-15
1 0 0 0 0 0 Group 2, All Call
1 0 X X X X Group 2, Units 1-15
1 1 0 0 0 0 Group 3, All Call
1 1 X X X X Group 3, Units 1-15

Example:

1 0 1 0 1 0 Group 2, Unit 10

For ISO Alphabet No. 5 Messages and Maintenance Data bits 23 through 29 should take on the pattern of the IOS Alphabet
No. 5 control character “STX”.

The second word of the ISO Alphabet No. 5 and Maintenance Data (ISO Alphabet No. 5) application groups is an optional
control word containing sign/status matrix code for “control” information for display. When it is used, bits 9 through 13
should contain the binary representation of the line count, bits 14 through 16 should encode the required color, bits 17 and 18
the required intensity, bits 19 and 20 the required character size and bit 21 should indicate whether or not the display is
required to flash. See ARINC Specification 429, Part 1, Attachment 6 for the encoding standards. Bits 22 through 29 of the
word should be binary “zeros” (spares).

Intermediate words, containing the sign/matrix code for “intermediate word”, follow the initial word of the group or the
control word, when used. Intermediate words are optional in the sense that they are only transmitted if more words than the
initial word and the final word (see below) are needed to accommodate the quantity of information to be transferred. When
the word application group label that is assigned in ARINC Specification 429, Part 1, Attachment 1 for Acknowledgement is
used. Data bits 9 through 29 of that word are available for information transfer. When the word application label is either of
those assigned in ARINC Specification 429, Part 1, Attachment 1 for ISO Alphabet No. 5 data transfer or Maintenance Data
(ISO Alphabet No. 5), bits 9 through 29 of each word should be divided into three seven-bit bytes (bits 9 through 15, 16
through 22 and 23 through 29), each of which contains one ISO Alphabet No. 5 character.

Each AIM application group transmission other than single-word transmission (see below) should be terminated with a word
containing the sign/status matrix code for “final word” defined in F-2.1.5.1. The data field of this word should be structured
similarly to that of the intermediate word. Any unused bit positions in ISO Alphabet No. 5 data transfer or Maintenance
Data (ISO Alphabet No. 5) final words resulting from the number of ISO Alphabet No. 5 characters in the message being
one or two less than a number wholly divisible by three should be filled with binary “zeros.”
 ARINC SPECIFICATION 429 PART 3 - Page 63

APPENDIX F
FORMER AIM AND FILE DATA TRANSFER TECHNIQUES

F-2.3.1.5 File Data Transfer

F-2.3.1.5.1 Command/Response Protocol

File data will consist of both ARINC 429 BNR numeric words and ISO Alphabet No. 5 characters. A file may contain from
1 to 127 records. Each record may contain from 1 to 126 data words.

A record should contain, at the minimum, one of the eight versions of the “initial word” described in F-2.3.1.5.2. Records in
which this initial word contains the “Data Follows” code should also contain from 1 to 126 “intermediate words” (data) and a
“final word” (error control). The file data transfer protocol is as follows. A transmitter having the data to send to a receiver
transmits, on the bus connecting it to that receiver, the “Request to Send” initial word. The receiver responds, on the
separate bus provided for return data flow, with the “Clear to Send” reply. The transmitter then sends the “Data Follows:
initial word, the “intermediate words” and the “final word”. The receiver processes the error control information in the ‘final
word” and, if no errors are revealed, closes out the transaction by sending the “Data Received OK” word to the transmitter.

If the receiver is not ready to accept data when the transmitter sends its “Request to Send” word, it should so indicate its
response (See F-2.3.1.5.2). The transmitter should then wait 200 milliseconds and retransmit the “Request to Send”. The
transmitter should also repeat a “Request to Send” transmission 50 milliseconds after the initial transmission if no response is
obtained from the receiver. If 2 additional attempts also spaced at 50 milliseconds produce no response from the receiver,
the transmitter should send the data. This feature is incorporated to enable file transfer (under a degraded mode of operation)
in the event of a failure in the receiver-to-transmitter bus.

If the receiver detects a parity error during the transmission, it may request an error-correcting retransmission by sending a
“Data Received Not OK” word to the transmitter in which is identified the record in which the error occurred. The
transmitter should interrupt the data flow and back up to the start of the record so identified. It should then send a “Data
Follows” initial word identifying this record as the starting point of the retransmission and recommence its output of data,
continuing through the “final word”. The receiver should then close out the transaction as before.

An error detected by processing the error control information in the “final word” should also result in the receiver sending a
“Data Received Not OK” word to the transmitter. In the absence of identification of the record in which the error occurred,
this word should contain the sequence number of the first record of the file. The transmitter's response should be to
retransmit the whole file.

The receiver can signal loss of synchronization to the transmitter at any time bysending the “Synchronization Lost” initial
word. On receiving this word, the transmitter should curtail the data flow and back up to the beginning of the file. It should
then re-establish that the receiver can accept data by going through the request-to-send routine. Having done this it should
send the “Data Follows” initial word, followed by the data and the “final word”.

The protocol also allows a transmitter to send the file size information to a receiver without any commitment to send, or
request to the receiver to accept, the file itself. The “Header Information” initial word is used for this purpose. Additionally,
a “Poll” initial word is defined for use in the system which continuous “hand-shaking” between two terminals is desired.
The response to a “Poll” word will be either a “Request” to Send” initial word when the polled terminal does have data to
transmit, or another “Poll” word when it does not. An exchange of “Poll” words may be interpreted as the message, “I have
nothing for you, do you have anything for me?”

F-2.3.1.5.2 Initial Word Types

The eight initial types are as follows:

Request to Send
Clear to Send
Data Follows
Data Received OK
Data Received Not OK
Synchronization Lose
Header Information
Poll

Bits 1 through 8 of all of those words except the “Poll” word contain the label code identifying the file to be transferred using
the protocol. Bits 1 through 8 of the “Poll” word contains binary zeros. Bits 9 through 29 are divided into three seven-bit
fields, the contents of which vary with word type as shown in Table A below. Bits 30 and 31 contain the code identifying
them as initial words while bit 32 is encoded to render word parity odd.
ARINC SPECIFICATION 429 PART 3 - Page 64

APPENDIX F
FORMER AIM AND FILE DATA TRANSFER TECHNIQUES

NOTES

1. The amount of data the receiver can accept upon receipt of a “Request to Send” signal is determined by the rate at which
data delivery can take place and the amount of time the receiver has available before it must turn its attention to some
other function. The receiver will set the count code in bits 9-15 of the “Clear to Send” word to indicate the number of
maximum length records it can accept when it determines that the “Request to Send signal originates in a high speed
data source. It will set this code to indicate the number of 32-bit words it can accept when it determines that the
“Request to Send” originates in a low speed data source, e.g., the ACARS ground-to-air link. The receiver will
annunciate the contents of this field (record count or word count) by setting Bit 22 as indicated. It will determine the
high or low speed nature of the source by port identification of the source of the “Request to Send” signal, the “Request
to Send” word label, the SDI code or some combination of these information items.

2. The record sequence number is the number of that record in a multiple-record file being transmitted.

F-2.3.1.5.3 Intermediate Words

Intermediate words contain the data being transmitted by means of the protocol. Bits 1 through 8 contain the file label. Bits
9 through 29 can accommodate three ISO Alphabet No. 5 characters or one ARINC 429 BNR numeric word without its
label. Note that this alpha/numeric data interleaving capability without labels necessitates a prior agreement between
transmitter and receiver on data format. Bits 30 and 31 contain the word code or the sign information (only) encoded in the
sign/status matrix of BNR numeric data words. Bit 32 is encoded to render the word parity odd.

F-2.3.1.5.4 Final Words

The final word of each record contains error control information. Bits 1 through 8 contain the file label. Bits 9 through 29
contain an error control checksum computed from the states of bits 9 through 29 of all intermediate words of the record. The
error control checksum should be generated by the arithmetic addition of the binary values of bits 9 through 29 of all
intermediate words and discarding the overflow. Bits 30 and 31 of this word contain the code identifying it as a final word.
Bit 32 is encoded to render the word parity odd.

F-2.3.1.5.5 Word Type Encoding

Bits 30 and 31 of each word used in data file transfer should be encoded to indicate word type as follows:

BIT
31 30 WORD TYPE
0 0 Intermediate Word requiring no sign data or
having Plus, North, East, Above Right, or To
sign

0 1 Initial Word (all types)

1 0 Final Word

1 1 Intermediate Word having Minus, South,

West, Below, Left, or From sign

F-2.3.1.5.6 File Data Formats

As noted in F-2.3.1.5.3, the transmission of file data words without labels necessitates the use of pre-arranged data formats.
The need to standardize such formats was examined by the working group. The conclusion was reached that a standard
format was desirable for flight management computer flight plan updating and for computer cross-talk, but was not necessary
for updating the computer's data base. Manufacturers are invited to submit proposals for a standard flight plan update file
and cross-talk bus formats.

F-2.3.1.5.7 File Data Labels

Labels define the application of the file data to be transferred. Such application include FMC program load/update, flight
plan load/update, the FMC inter-system cross-talk, etc. There may be a need to assign more than one label to some of those
applications if priority override capability is desired.
 ARINC SPECIFICATION 429 PART 3 - Page 65

APPENDIX F
FORMER AIM AND FILE DATA TRANSFER TECHNIQUES

F-3.2 AIM Information Transfer

F-2.3.1.4 describes the techniques to be used for the transfer of Acknowledgement, ISO Alphabet No. 5 and Maintenance
(ISO Alphabet No. 5) data by means of the Mark 33 DITS. The motivation for the adoption of this technique was label
conservation. Without it, a separate label would have to be assigned to each AIM word application for each source of such
data. In it, labels are assigned by word application only, and (where necessary) utilization device input port recognition
utilized to identify sources. A special exception to this rule is made for the Airborne Integrated Data System (AIDS), as
described in F-2.3.1.4. The technique also accommodates the use of multiple-word DITS messages, as described in Section
F-2.3.1.4.

F-3.2.1 Acknowledgement Data

Source equipments responding to requests for acknowledgement of incoming data delivered via a DITS input port should do
so in the manner described in F-2.3.1.4. No applications for this system capability have yet been identified and thus no data
standards for acknowledgement messages have been established.

F-3.2.2 ISO Alphabet No. 5 Data

Source equipment transmitting ISO Alphabet No. 5 information by means of the Mark 33 DITS should do so in the manner
described in F-2.3.1.4. This application, and the use of ISO data for maintenance-related information transfer, will be the
most likely to make use of the multiple-word message transmission capability of the system. Receiving equipment should
make use of the binary word count and the sign/status matrix codes of the words to ensure that such messages are received in
their entirety, with no words having been “lost along the way.” Only when this determination has been made, and the parity
check for each word shows the data to be error-free, should the message be displayed to the crew or otherwise utilized.

F-3.2.3 Maintenance Data

Source equipment putting out data intended for a maintenance assist system on the aircraft should do so in the manner
described in F-2.3.1.4. The Maintenance assist system should use input port recognition to identify data sources. The
Maintenance word as described by AIM data handling techniques is limited to IOS Alphabet No. 5 messages.
ARINC SPECIFICATION 429 PART 3 - Page 66

APPENDIX F
FORMER AIM AND FILE DATA TRANSFER TECHNIQUES

TABLE A - INITIAL WORD TYPES

INITIAL FIELD
WORD TYPE (Bits) FIELD CONTENTS
Request to Send 9-15 BNR count number of records to be sent (Max. 127)
(Tx-to-Rx) 16-22 Binary zeros
23-29 ISO Alphabet No. 5 Control Character
“DC2”
Clear to Send 9-15 Binary zeros when receiver is not ready to accept data. BNR count of the
(Rx-to-Tx) number of maximum length of records OR the number of 32-bit words the
See Note 1 receiver can accept when it is ready
16-21 Binary zeros
22 Binary zero when receiver is not ready to receive data and when BNR
counts in 9-15 is record count. Binary one when count in bits 9-15
is 32-bit word count.
ISO Alphabet Control Characters
23-29 “DC3”
Data Follows 9-15 BNR count of number of words in record (Max. 126)
(Tx-to-Rx) 16-22 Record Sequence No. (BNR)
See Note 2 23-29 ISO Alphabet No. 5 Control Character
“STX”
Data Received 9-15 BNR count of number of words in record (Max. 126)
OK 16-22 Record Sequence No. (BNR)
(Rx-to-Tx) ISO Alphabet No. 5 Control Character
“ACK”
Data Received 9-15 BNR count number of words in record
Not OK 16-22 Record sequence no. (BNR) in which error occurred
(Rx-to-Tx) 23-29 ISO Alphabet No. 5 Control Character
“NAK”
Synchronization 9-15 Binary Zeros
Lost 16-22 Binary Zeros
(Rx-to-Tx) 23-29 ISO Alphabet No. 5 Control Character
“SYN”
Header 9-15 BNR count of number of records in file to be transferred
Information 16-22 Binary Zeros
(Tx-to-Rx) 23-29 ISO Alphabet No. 5 Control Character
“SOH”
Poll 9-15 Binary Zeros
(B-directional) 16-22 Binary Zeros
23-29 ISO Alphabet No. 5 Control Character
“ENQ”
 ARINC SPECIFICATION 429 PART 3 - Page 67

APPENDIX G
MATHEMATICAL EXAMPLE OF CRC ENCODING/DECODING

NOTE: The following example describes the polynomial division procedure for CRC encoding and decoding. Arithmetic
operations are modulo 2. Actual software/hardware implementations are expected to vary significantly from this example,
since these polynomial divisions are more efficiently simulated by logical operations.

For CRC computations, the MSB is the bit which represents the coefficient of the highest order term of the polynomial. It
is not related to the MSB or LSB of each individual octet. Slashes (/) are used to separate octets for readability only, and
do not denote division in this example.

The following (arbitrary) 24-bit message is to be transmitted with a CRC encoded:

10100111 / 10000111 / 10101100

(MSB) (LSB)

The mathematical procedure is as follows:

For this message, k = 24, and
23 21 18 17 16 15 10 9 8 7 5 3 2
G(x) = x +x +x +x +x +x +x +x +x +x +x +x +x.
16 16 23 21 18 17 7 5 3 2
x G(x) = x (x + x + x + x + ... + x + x + x + x ).
39 37 34 33 23 21 19 18
= x + x + x + x + ... + x + x + x + x .

and
k 15 14 13 12 11 3 2
x (x + x + x + x + x + ... + x + x + x + 1)
39 38 37 36 27 26 25 24
= x + x + x + x + ... + x + x + x + x .

At The Transmitter: Using coefficients of the above polynomials, the dividend is calculated as follows:
16
x G(x) = 1010 0111 1000 0111 1010 1100 0000 0000 0000 0000

and
k 15 14 2
x (x + x +...+ x + x + 1) = 1111 1111 1111 1111 0000 0000 0000 0000 0000 0000

1010 0111 1000 0111 1010 1100 0000 0000 0000 0000
+ 1111 1111 1111 1111 0000 0000 0000 0000 0000 0000
= 0101 1000 0111 1000 1010 1100 0000 0000 0000 0000

Then the Dividend is: 0101 1000 0111 1000 1010 1100 0000 0000 0000 0000
16 12 5
and the Divisor, P(x) = x + x + x + 1, is: 1 0001 0000 0010 0001
ARINC SPECIFICATION 429 PART 3 - Page 68

APPENDIX G
MATHEMATICAL EXAMPLE OF CRC ENCODING/DECODING

P(x) = 1 0001 0000 0010 0001 is the divisor of the dividend below.

(Q(x), the quotient generated by the division process, is not used).

Q(x) = 101 1101 1010 1001 1101 1001

0101 1000 0111 1000 1010 1100 0000 0000 0000 0000
100 0100 0000 1000 01
1 1100 0111 0000 1110
1 0001 0000 0010 0001
1101 0111 0010 1111 1
1000 1000 0001 0000 1
101 1111 0011 1111 01
Using (synthetic) 100 0100 0000 1000 01
Polynomial 1 1011 0011 0111 0000
Division: 1 0001 0000 0010 0001
1010 0011 0101 0101 0
1000 1000 0001 0000 1
10 1011 0100 0001 100
10 0010 0000 0100 001
1001 0100 0101 1010 0
1000 1000 0001 0000 1
1 1100 0100 1010 1
Note: Since all operations are Modulo 2,
addition and subtraction are both
equivalent to XOR operations (no carries!)

1000 1000 0001 0000 1

1 0001 0010 1101 1000
1 0001 0000 0010 0001

R(x) = 0000 0010 1111 1001

CRC = R(x) = 1111 1101 0000 0110

16
M(x) = x G(x) + CRC

= 1010 0111 1000 0111 1010 1100 0000 0000 0000 0000
+ 1111 1101 0000 0110
= 1010 0111 1000 0111 1010 1100 1111 1101 0000 0110

or

M(x) = 1010 0111 1000 0111 1010 1100 1111 1101 0000 0110

MSB (message) LSB MSB (CRC) LSB

M(x) is the transmitted message with CRC.

 ARINC SPECIFICATION 429 PART 3 - Page 69

APPENDIX G
MATHEMATICAL EXAMPLE OF CRC ENCODING/DECODING

At The Receiver:

The dividend to be operated on by P(x) is determined (mathematically) as follows:

16 40 15 14 13 12 2
x M(x) + x (x + x + x + x + ... + x + x + 1)

= 1010 0111 1000 0111 1010 1100 1111 1101 0000 0110 0000 0000 0000 0000
+ 1111 1111 1111 1111 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
= 0101 1000 0111 1000 1010 1100 1111 1101 0000 0110 0000 0000 0000 0000

The above string is the dividend used by the receiver.

(The divisor, 10001000000100001, is the same as that used by the transmitter.)

(The quotient, Q(x), generated by the division process, is not used.)

Q(x) = 101 1101 1010 1001 1101 1001 . . . .

0101 1000 0111 1000 1010 1100 1111 1101 0000 0110 0000 0000 0000 0000
100 0100 0000 1000 01
1 1100 0111 0000 1110
1 0001 0000 0010 0001
1101 0111 0010 1111 1
1000 1000 0001 0000 1
101 1111 0011 1111 01
100 0100 0000 1000 01
1 1011 0011 0111 0000

1001 0110 1110 1101 0

1000 1000 0001 0000 1
1 1110 1111 1101 1110
1 0001 0000 0010 0001
1111 1111 1111 1111

Note: At this point, if the division is

carried through to termination, the
final remainder is: Rr(x) = 0001 1101 0000 1111
ARINC SPECIFICATION 429 PART 3 - Page 70

APPENDIX G
MATHEMATICAL EXAMPLE OF CRC ENCODING/DECODING

LDU Mapping for 24-bit Example

Because of the transmission order of ARINC 429 32-bit words, the first bit of the first Data Word transmitted after the SAL is the
MSB of the message (for CRC computations). Therefore, the actual transmission order of the bit string, M(x), is the reverse of
the previous example, when mapped into 32-bit words.

The following represents the mapping of the preceding 24-bit message and CRC into an LDU for transmission:

MSB (message) LSB MSB (CRC) LSB

M(x) = 1010 0111 1000 0111 1010 1100 1111 1101 0000 0110

SOT Word P 110 GFI File No. LDU No. SAL

Full Data Word P 000 0101 1110 0001 1110 0101 SAL
LDU
Partial Data Word P 001 1000 0000 0000 0000 0011 SAL

EOT Word P 111 0001 0110 0000 1011 1111 SAL

Legend:

The CRC is calculated over these bits.

These are the CRC bits

 ARINC SPECIFICATION 429 PART 3 - Page 71
APPENDIX H
INTEROPERABILITY OF BIT-ORIENTED LINK LAYER PROTOCOL

H.1 Version Number Designators

The version number of a system is transmitted to the peer system in the ALO and ALR words.
• Version 1 systems are defined to be (Williamsburg) bit-oriented communication protocol systems, as defined in
Section 2.0 this Specification.
• Version 2 systems are obsolete and have been deleted from ARINC Specification 429 - Part 3.
• Version 3 systems are defined to provide a standard MAC-based sublayer of the bit-oriented communications-
protocol, and are defined in Section 3.0 of ARINC 429 - Part 3. c-16

H.2 Interoperability - Same Version Number

Beginning with Supplement 13 of 429, any version 1 system should interoperate with any other version 1 system (i.e.,
the version number should be independent of supplement number implementation.) For example, a version 1 429-13
system should interoperate with a version 1 429-14 system.
Similarly, any version 3 system should interoperate with any other version 3 system (independent of supplement
number).
In general, higher supplement numbers of the same version number clarify requirements.

H.3 Interoperability - Different Version Numbers

c-17
Version 1 and Version 3 can coexist on the same physical bus.
H.4 Bit-Oriented Link Layer GFIs for Standard Network Service

When a system implements a standard (e.g. ISO) network service, which resides directly above the 429 Version 1
(Williamsburg), then the ISO GFI bit-coding of "4h" (for ISO 9577) as specified in ARINC 429-14 should be used. c-16
ISO GFI bit-codings originally specified in ARINC 429-13 were "1h" for ISO 8208 and "4h" for ISO 8473. These GFI
bit-codings are not compatible with the new GFI "4h" designator and should not be used as standard network service
identifiers.
 ARINC CHARACTERISTIC 429 PART 3 - Page 72

APPENDIX I
SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL

/*
* ARINC Specification 429, Part 3
MSC - File_Transfer _Example *
* Note that some of the names in
* the message sequence diagram in
c-15 * Attachment 11 do not match names
* in This Appendix
*
*/

Airline_Source Source Sink Aircraft_ Destination

Original_Data_File

RTS
CTS

SOT

DATA [2]
DATA [3]

DATA [4]
.
.
.
.
.
DATA [254]
EOT
ACK
RTS

CTS
SOT

DATA [2]
DATA [3]

DATA [4]

DATA [6]
EOT

ACK
Received_Data_File
 ARINC CHARACTERISTIC 429 PART 3 - Page 73

APPENDIX I
SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL

System Williamsburg
Diagram (1)
/*
* ARINC 429 Williamsburg (Section 2.5)
*
* Author, W. Turner, K. Dihle
ARINC 429 Williamsburg Working Group c-15
*
* This is the SDT description of the 429 protocol
* as developed by the 429W Working Group through
* August 1994
*
*
*/
[DL_UNITDATA.ind]
/*
* Notes:
*
* It was not clear what the Williamsburg Convergence DLPI_if
* Function actually did, other than change the names
* of the primitives. Unless more definitions occur
* in this area, the WCF will be removed in later
[DL_UNITDATA.req]
* versions.
*
* LDU signal is not sent. Instead SOT, Data, EOT are used.
*
* Things to add to this defintion:
* SOLO Words
* File Seq No/LDU Seq No.
* n4count m_if
* n5count LRU_Lyr_2
* Determine task of Segment and Reassemble. [DL_ERROR.ind]

Signal

DL_UNITDATA

/* This document is based on material submitted by various participants (p429_both),

during the drafting process. Neither AEEC nor ARINC has made any (p429_to_sink),
determination whether these materials could be subject to claims (p429_to_source),
of patent or other proprietary rights by third parties, and no SOT, EOT, Data
representation or warranty, expressed or implied is made in this
regard. Any use or reliance on this doucment shall constitute
an acceptance hereof "as is" and be subject to this disclaimer. */ Physical_429_if

/* This is a working paper prepared for AEEC. It does not constitute

air transport industry or ARINC approved policy, nor is it endorsed (p429_both),
by the U.S. Federal Government, any of its agencies or others who (p429_to_sink),
may have participated in its preparation. */ (p429_to_source),
SOT, EOT, Data
ARINC CHARACTERISTIC 429 PART 3 - Page 74

APPENDIX I
SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL

The following definitions are used:

Signal

DL_UNITDATA.req,
DL_UNITDATA.ind,
DL_ERROR.ind,

/* Wilmsbrg*/
/* -----*/

ACK, /*2.5.1.4 */
ALO, /*2.5.19.1.1 */
ALR, /*2.5.19.1.2 */
BUSY, /*2.5.7.3 */
CTS, /*2.5.7.1 */
Data, /*2.5.11 */
EOT, /*2.5.12 */
NAK, /*2.5.13 */
NCTS, /*2.5.7.2 */
RTS, /*2.5.7 */
SOT, /*2.5.10 */
SYN, /*2.5.15 */

/*LOOP, 2.5.17.1 */
/*SOLO, 2.5.17.2 */
/*TEST, 2.5.17.2 */
/*LCW */

Signalist p429_both =
ALO<ALR/* LOOP,SOLO,TEST */;

Signalist p429_to_sink =
RTS;

Signalist p429_to_source =
ACK,BUSY,CTS,NAK,NCTS,SYN;
 ARINC CHARACTERISTIC 429 PART 3 - Page 75

APPENDIX I
SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL

Block LRU_Lyr_2 [DL_UNITDATA.ind] 1 (1)

Connect Physical_429_if and source_if, sink_if;

Connect DLPI_if and d_if;
Connect m_if and m_if:
d_if

Signal
FILE,
LDU.req, [DL_UNITDATA.req]
LDU.ind;
(1,1)

WCF

[FILE] [FILE]

williamsburg_ifa williamsburg_ifb

(1,1) (1,1)
m_if
Segment Reassemble
[DL_ERROR.ind.]

[LDU.ind]
send_if receive_if
[LDU.req]

(1,1)

Source_and_Sink

ACK, RTS,
BUSY, (p429_both)
CTS, SOT, EOT,
NAK, Data
NCTS,
SYN Note: the sink_if is a receive
(p429_both) bus, and typically for a single
Williamsburg function there may be
source_if sink_if
multiple sink_ifs.

ACK,
BUSY,
CTS,
RTS, NAK,
(p429_both) NCTS,
SOT, EOT, SYN
Data (p429_both)
ARINC CHARACTERISTIC 429 PART 3 - Page 76

APPENDIX I
SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL

Process Reassemble 1(1)

idle

LDU.ind

'reassemble
LDUs into
a File'

FILE

-
 ARINC CHARACTERISTIC 429 PART 3 - Page 77

APPENDIX I
SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL

Process Segment 1(1)

idle

FILE

'segment the
File into
LDUs'

LDU.req

-
 ARINC CHARACTERISTIC 429 PART 3 - Page 78

APPENDIX I
SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL

Process Source_and_Sink 1 (12)

/*
* Bit-Oriented Protocol Events
* Part 3, Table 10-1 (1,1); This is the power-on
*/
c-15 Synonym N1 integer = 5; /*Number of RTS repeats from NCTS */
transition
Synonym N2 integer = 20; /*Number of RTS repeats after BUSY */
Synonym N3 integer = 5; /*Number of RTS repeats after no resp */
Synonym N4 integer = 3; /*Number of NAKs rcvd before NO COMM */
Synonym N5 integer = 3; /*Number of SYN before NO COMM */ System Inactive
Synonym N6 integer = 3; /*Number of ALO after no response*/
State 0
/*
* Selected Options
* Table 10-3
*
* Option 1 Half Duplex
* Option 2 Low Speed Bus Rate
* Option 3 Automatic CTS when Ready = No ALO 2.5.19
* Option 4 Accept Auto CTS = No via source_if 2.3
* Option 5 System Priority to resolve RTS Conflict = No
* Option 8 Use Solo Word = Yes
* Option 10 Dest Code in RTS/CTS/NCTS/BUSY used = Yes
* Option 11 Bit-Oriented Protocol Vertification = Yes
*/

/*
* Variables for Low Speed Bit-Oriented Protocol 2.5.19
c-15 Part 3, Table 10-4
set (now+ t12,
T12)
2.3
*/

/* Timer for Source */

Synonym t2 duration = 500; /* RTS repeat time after receipt of NCTS */

Synonym t4 duration = 15000; /* RTS repeat time after receipt of BUSY */ n1count := 0 reset state
Synonym t5 duration = 500; /* RTS repeat time if no response*/ n2count := 0 variables
Synonym t12 duration = 200; /* ALO repeat time if no response to ALO*/ n3count := 0 2.5.19
Synonym t16 duration = 220; /* ACK/NAK Timeout after EOT*/

/* Timer for Sink */

c-15
Synonym t9 duration = 2500; /* LDU timeout following CTS */ n4count := 0
Synonym t14 duration = 120000; /* Incomplete File Timeout */ n5count := 0 2.5.19
/* n6count := 0
* Variables for High Speed Bit-Oriented Protocol
* Part 3, Table 10-5
*/

/* Timer for Source */

Synonym t2 duration = 100; /* RTS repeat time after receipt of NCTS */ ALO_idle
Synonym t4 duration = 1000; /* RTS repeat time after receipt of BUSY */
Synonym t5 duration = 150; /* RTS repeat time if no response*/
Synonym t12 duration = 200; /* ALO repeat time if no response to ALO*/
Synonym t16 duration = 220; /* ACK/NAK Timeout after EOT*/

/* Timer for Sink */

c-15 Dc:
/* Synonym t9 duration = 400 /* LDU timeout following CTS */ n1count, /* This Source_and_Sink state
/* Synonym t14 duration = 10000' /* Incomplete File Timeout */ n2count, machine is replicated for each
n3count SAL pair. This state
n4count, machine asumes that SAL
n5count assignments have occurred; i.e.
n6count integer; - the state machine
only makes use of the pre-
Timer determined SAL pair.*/
T2,T4,T5,T9,T12,T14,T16;
 ARINC CHARACTERISTIC 429 PART 3 - Page 79

APPENDIX I
SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL

2(12)
Process Source_and_Sink
Synonym version_match boolean = true;
Synonym can_adapt boolean = true;
(1,1); Synonym try_different_version boolean = true;
ALO_Idle

go_
ALO 2.5.19 ALR
aloha

ALR 2.5.19.1 2.5.19

via source_if reset(T12)
2.5.19.1.1

reset(T12) recount := 0 2.5.19.1

2.5.19

Link_ 2.5.19.1.1
_Idle version_ true
_match
false
Link_
2.5.19.1.1
_Idle

ALO_Idle

can_adapt
false true

T12 2.5.19.1
try_ 'adapt'
_different_
_version true
n6count :=
n6count + 1 2.5.19.1
false Link_
2.5.19.1.1
_Idle

else
n6count 'not bit ALO
oriented' via source_if
<N6

ALO set(now + t12,

2.5.19.1 2.5.19.1
via source_if T12)

-
set(now + t12, 2.5.1
T12) 2.5.19.1 ALO_
Idle
'not bit Not successful. This should lead
oriented' to the character-oriented
ALO_Idle protocol determination process,
if applicable, or a cyclical
2.5.19.1 attempt to establish bit-
oriented protocol. See Attachment 17.
- 2.5.19, 2.5.19.2
ARINC CHARACTERISTIC 429 PART 3 - Page 80

APPENDIX I
SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL

3(12)
Process Source_and_ Sink

Synonym valid_and_ready boolean = true;

(1,1); Synonym are_we_busy boolean = false; Invalid and N/A
Synonym messages_queued boolean = false; transitions not shown

Link_
_Idle

LDU.req RTS go_rts ALO T14

SYN
set(now + t5, 2.5.7.4 via sink_if
reset(T14) 2.5.14.3 go_aloha
T5)

'discard any
partial file
are_we_ received'
RTS via
2.5.7 _ busy true
source_if

BUSY 2.5.7.3 Link_

via sink_if 2.5.7 _Idle
Wait_ false
_CTS Unless Option 3
- is implemented
2.5.7.3 2.5.14.3
valid_and
_ ready

true false
2.5.19.1.2
CTS 2.5.7.1 NCTS 2.5.7.2
via sink_if 2.5.7 via sink_if 2.5.7

set(now + t9, Link_ Unless Option 3

T9) 2.5.13.2 _Idle is implemented
2.5.7.2

Wait_
_SOT
 ARINC CHARACTERISTIC 429 PART 3 - Page 81

APPENDIX I
SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL

Process Source_and_ Sink 4(12)

Synonym valid_CTS boolean = true;
Synonym random_number duration = 1;
(1,1); Dc:
t6 duration;
Timer
T6;

Wait_
_CTS

2.5.7.1
LDU.req RTS CTS 2.5.10 ALO 2.5.7.4
2.5.8.1

reset(T5)
go_
n3count=0 _CTS
2.5.7.4
So message just
LDU.req
de-queued
to self
is not lost
reset(T5)
2.5.7.4 valid_CTS
false
go_
2.5.19.1.2
true _aloha
go_
_NCTS
reset(T14) 2.5.14.3 reset(T5)

t6 :=
n1count := 0, 2.5.7.4
random_ 2.5.8.1 n2count := 0,
number 2.5.7.1
n3count := 0
2.5.7.1, 2.5.7.2
set(now + t6, 2.5.7.3, 2.5.7.4
T6) 2.5.8.1 SOT
via source_if

2.5.10
Wait_RTS_
Data
_Conflict
via source_if

EOT
If Option 5 2.5.12
via source_if
is used, one
system will
have priority
2.5.8.1 NOTE: set(now + t16,
Usually uplinks T16) 2.5.16
are accorded
priority
Wait_
_ACK
 ARINC CHARACTERISTIC 429 PART 3 - Page 82

APPENDIX I
SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL

5(12)
Process Source_and_ Sink

(1,1);

Wait_
_CTS

NCTS go_
BBUUSSYY 2.5.7.3 T5 2.5.7.4
_NCTS

reset(T5) 2.5.7.4 reset(T5)

reset(T5) 2.5.7.4

n3count :=0 2.5.7.4 n3count :=0 2.5.7.4

n1count := n2count :=
n2count + 1 n3count :=
n1count + 1
n3count + 1

n1count else else

n2count
n3count
else
<N1 <N2 <N3

set(now + t2, DL_ERROR.ind set(now + t4, DL_ERROR.ind set(now + t5, DL_ERROR.ind

T2) T4)
T5)

NCTS_ Busy_ n1count :=0 NCTS_ Busy_ RTS via

_Delay _Delay n2count :=0
source_if n3count :=0

Link_ Link_ Wait_ Link_

_Idle _Idle _CTS _Idle

2.5.7.2 2.5.7.3 2.5.7.4

 ARINC CHARACTERISTIC 429 PART 3 - Page 83

APPENDIX I
SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL

6(12)
Process Source_and_ Sink

(1,1);

Wait_RTS_
_Conflict

RTS 2.5.8.1 BAULSOY 2.5.19.1.2 T6 2.5.8.1

'requeue
go_ set(now + t5,
unitdata 2.5.19.1.2 2.5.7.4
_aloha T5)
request'

2.5.14.3 RTS
reset(T14) via source_if 2.5.8.1

CTS
2.5.8.1 Wait_ RTS_
via sink_if Wait_ CTS
_Conflict

set(now + t9, 2.5.13.2

T9) 2.5.13.6

LDU.req

Wait_
SOT
 ARINC CHARACTERISTIC 429 PART 3 - Page 84

APPENDIX I
SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL

7(12)
Process Source_and_ Sink

(1,1);

NCTS_BUSY_
_Delay

This transition valid

LDU.req RTS ALO CTS only if Option 4 is
set.

Otherwise CTS is
go_ ignored.
go_
LDU.req _aloha _CTS
2.5.7.2, 2.5.7.3
to self

2.5.19.1.2
go_
_RTS

2.5.7

NCTS_BUSY_
_Delay

T4 2.5.7.3 T2 2.5.7.2

set(now + t5, set(now + t5,

T5) 2.5.7.4 T5) 2.5.7.4

RTS RTS 2.5.7.2

via source_if 2.5.7.3 via source_if

Wait_ Wait_
_CTS _CTS
 ARINC CHARACTERISTIC 429 PART 3 - Page 85

APPENDIX I
SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL

8(12)
Process Source_and_ Sink
Synonym FSN_LSN_match boolean = true;
(1,1);

Wait_
_ACK

2.5.16

LDU.req RTS ALO ACK

LDU.req 'requeue file set(now +t5,

to self 2.5.19.1.2' reset(T16) T5) 2.5.7.4

go_ go_ RTS 2.5.16

_rts _aloha FSN_LSN_ via source_if
_match false
Wait_
true _CTS
Link_
_Idle

Wait_
_ACK

SYN 2.5.16 T16 NAK 2.5.16

2.5.16

n5count := 2.5.16 set(now + 2.5.7.4 reset(T16)

n5count +1 t5, T5)

RTS n4count :=
n4count :=0 2.5.16 2.5.16 2.5.16
via source_if n4count +1

Wait_ n5count :=0 2.5.16

2.5.16
_CTS

n5count else
n4count else
<N5 DL_
set(now + ERROR.ind
2.5.7.4 <N4 DL_
t5, T5) 2.5.16
set(now + ERROR.ind
t5, T5)
RTS of 1st LDU Link_
via source_if 2.5.16 _Idle
RTS Link_
via source_if _Idle
Wait_
_CTS
Wait_ 2.5.7.4
2.5.16 _CTS
2.5.16
ARINC CHARACTERISTIC 429 PART 3 - Page 86

APPENDIX I
SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL

9(12)
Process Source_and_ Sink
Synonym LSN_FSN_confusion boolean = true;
(1,1);

Wait_
_SOT

LDU.req RTS ALO SOT

2.5.15
go_ go_
LDU_FSN_
_rts _aloha
_confusion true

2.5.9 2.5.19.1.2 false

Wait_ 'discard 2.5.15

_EOT partial File'

2.5.10.2
2.5.10.3 reset(T14) 2.5.14.3

SYN 2.5.15
via sink_if unexpected FSN

Link_
_Idle

Wait_
_SOT

EOT 2.5.13.1 Data 2.5.13.2 T9 2.5.13.2

NAK
2.5.13.2
via sink_if

Link_
_Idle
 ARINC CHARACTERISTIC 429 PART 3 - Page 87

APPENDIX I
SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL

10(12)
Process Source_and_ Sink
Synonym valid_EOT boolean = true;
(1,1);

Wait_
_EOT

LDU.req RTS ALO T9 2.5.13.2 SYN

'discard NAK 2.5.13.2 'discard

'discard via sink_if
partial LDU' partial File' 2.5.3.16 partial File'

set (now+ t14, 2.5.13.2 reset (T14)

go_ reset(T14) T14)
_RTS

'discard any
2.5.13.6 Link_
2.5.9 partial LDU'
go_ _Idle
_aloha
Link_ 2.5.14.3
_Idle
2.5.14.3

2.5.19.1.2
ARINC CHARACTERISTIC 429 PART 3 - Page 88

APPENDIX I
SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL

11(12)
Process Source_and_ Sink

(1,1);
Wait_ is also the
_EOT wait for data state

NAK 2.5.13.4
Data 2.5.13.3 EOT 2.5.14.3
via sink_if 2.5.13.5

'discard any
correct_ partial LDU' 2.5.14.3
odd_parity false
_word_
false
_count
2.5.6.3
true
true final_ LDU
'store data 'ignore false
word' 2.5.13.3' set(now+ t14,
LDU_ T14)
_CRC_ true
_count false
- - reset(T14)
true
discuss; not
2.5.14 described Link_
next_or_ false _Idle
true _duplicate

2.5.14.3

2.5.14 first_of_ false

ACK
2.5.14.1 _new file
via sink_if
2.5.14.2
'discard any
partial file' 2.5.15
discuss; not true
final_LDU
described false 'discard any
partial file' reset(T14) 2.5.14.3
true

reset(T14) set(now + t14, SYN

reset(T14) 2.5.14
T14) via sink_if

Link_
_Idle
2.5.14.2
duplicate
true
Send LDU signal 'discard LDU
to upper layers 2.5.14.1' 2.5.14.3
false

Synonym odd_parity boolean = true;

Synonym correct_word_count boolean = true;
LDU.ind
Synonym LDU_CRC_correct boolean = true;
Synonym next_or_duplicate boolean = true;
Synonym duplicate boolean =true;
L i n-k _ Link_ Synonym first_of new_file = true;
_Idle _Idle Synonym final_LDU boolean = true;
 ARINC CHARACTERISTIC 429 PART 3 - Page 89

APPENDIX I
SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL

Process WCF 1(1)

idle

DL_
UNITDATA. FILE
req

FILE_
DL_
via
UNITDATA.
williamsburg
req
_ifa

- -
 c-17

ARINC SPECIFICATION 429 PART 3 - Page 90

Mgt Entity
CMU/VDR ATN 1 Data Loader
Protocol Layers VDL Mode 2 Interface

Transport Layer TCP/UDP Mgt MIB

CLTP/TP4
Figure J1-1 ARINC 429 Williamsburg Version 3 Protocol Layer Diagram

CLNP IP

Mgt MIB
Network
Layer
Subnetwork (ITU.T
Sublayer X.25/
ISO 8208)

PROTOCOL STRUCTURE
APPENDIX J
LLC
Mgt MIB

ARINC 429 ARINC 429

Command Information
LLC Length
Frames Frames Type
Sublayer
Data Link
Layer
ARINC 429 Williamsburg Version 3 MAC Protocol (Part 3)
MAC
Sublayer MAC Control MAC Control

ARINC 429 Command Frame ARINC 429 Information Frame Mgt MIB

Physical
Layer ARINC 429 Physical Layer (Part 1)
 ARINC SPECIFICATION 429 PART 3 - Page 91

APPENDIX J
PROTOCOL STRUCTURE

Physical Layer - The physical layer is a high speed ARINC 429 data bus.

Link Layer – It is responsible for the exchange of data between points (nodes) connected to one network. One network
can be constructed either by a bus (A429, A629) or by a set of buses and point-to-point links that can be interconnected
by bridges (A646).

MAC Sublayer – The scope of this document is the “lower” part of the Link Layer. The ARINC 429 (Williamsburg)
Version 3 protocol specifies the functionality of the MAC Service Provider that provides two types of MAC Frames, a
bridgeable Information frame based upon the frame structure specified in IEEE 802.3 (Ethernet) and a non-bridgeable
Command frame for point-to-point transfers of data of any kind, e.g. link management information.

LLC Sublayer – One potential MAC Service Client is the Logical Link Control Sublayer, which may be used to provide
a logical interface between LLC entities. All IEEE 802 specifications share the notion of this “upper” portion of the Link
Layer, which enables it to provide a common set of services. It may be used to provide a logical interface between peer
entities. Three classes of service have been defined which can be connectionless-unacknowledged, connectionless-
acknowledged or connection-oriented.

Network Layer – Other potential MAC Service Clients are either Internet (summarized by TCP/IP), specific (e.g. VDL
Mode 2) or further standardized or non-standardized protocols. The Network layer provides a home for specifications of
protocols that support the communication across network boundaries. In the example shown, these are, e.g., IP or CLNP.

Subnetwork Sublayer – In the scope of this document this sublayer is defined as an X.25 subset (profile). It may be
required to provide services to the Network Layer, and interfaces with the LLC Sublayer. In the ISO network definition,
these are the Subnetwork Access Protocols (SNAP) and provide services to the Subnetwork Independent Convergence
Protocol (SNICP) and the Subnetwork Dependent Convergence Protocol (SNDCP). These services include flow control, c-17
error recovery and segmentation/reassembly.

It should be noted, however, that there is another (totally separate) SNAP definition by IEEE that resides on top of LLC
Class 1 (connectionless-unacknowledged service) and acts as a Link layer client multiplexer similar to the 802.3 TYPE
interpretation.

Transport Layer – This layer provides services for the exchange of information between communication applications,
such as the Trivial File Transfer Protocol (TFTP) in the Internet suite of protocols which in this example is used by the
Data Loader application or Simple Network Management Protocol (SNMP) for network management.

Typical Applications
This section focuses on the scope of this document, the various characteristics of the ARINC 429 Version 3
specification.

A429 Information Frame – As specified in section 3.3.1 this frame provides for a bridgeable frame format that is used by
various applications. In this example, Data Loader (via TCP/IP stack) or ATN 1 (via OSI stack) could take advantage of
this format.

A429 Command Frame – As specified in section 3.3.2 this frame provides for a non-bridgeable point-to-point frame
format that may be used by the CMU/VDR VDL Mode 2 Interface.

ÍEEE 802.3 – IEEE used to assume that LLC resides above any of the 802.n (with n bigger than 2) specifications. IEEE
802.3 has always been in “competition” with the Ethernet specification, developed by Xerox, Digital and Intel. However,
Xerox has shifted authority about the Ethernet specification to IEEE, which incorporated it into the current (1998)
edition of the 802.3 specification. The main difference between the two specifications was the interpretation of a field
that is now called “LENGTH/TYPE”.

802.3-LENGTH – The “LENGTH” interpretation assumes that LLC is the MAC Service Client. If the value in this field
is less than or equal to 1500 decimal, a “LENGTH” interpretation is specified.
 ARINC SPECIFICATION 429 PART 3 - Page 92

APPENDIX J
PROTOCOL STRUCTURE

802.3-TYPE – The “TYPE” interpretation assumes that a different protocol is the MAC Service Client. If the value in
this field is bigger than or equal to 1536 decimal, the value specifies the respective protocol. Assignments are
documented in an Internet Request for Comment (RFC).

MAC Control – This functionality has been introduced recently and currently provides for a PAUSE function only. It
enables temporary suppression of any data transmission when sent to the peer MAC entity (reverse MAC Control
commands can still be returned, though). Both types of frames, Information and Command, support this function in
c-17
different ways.

Network Management – Each layer of the communication stack is required to maintain a Management Information Base
(MIB) which consists of parameters and behavioral characteristics of that layer and may be retrieved by the Network
Management entity. The contents of the respective MIB are specified in the related protocol layer specification whereas
the MIB structure as well as the Network Management Protocol and functionality is specified in a separate specification.
 ARINC SPECIFICATION 429 PART 3 - Page 93
APPENDIX K
GLOSSARY & ACRONYMS

ACK Acknowledge
ADS Automatic Dependent Surveillance
AIDS Airborne Integrated Data System
ALR ALOHA Response
BOP Bit-Oriented Protocol
BSAL Bridge System Address Label
CRC Cyclic Redundancy Check
CT Command Type
CTS Clear to Send
DITS Mark 33 Digital Information Transfer System
EOF End of Field
EOT End of Transmission
FDU Frame Data Unit
GFI General Format Identifier
I/C Information/Command
IEEE Institute of Electrical and Electronics Engineers
IP Internet Protocol
ISO International Standard Organization
LAN Local Area Network
LDU Link Data Units
LLC Logical Link Control
LOOP Loop Test Response
LRU Line Replaceable Units
LSB Least Significant Bit
MAC Media Access Control
MSAL Multicast System Address Label
MSB Most Significant Bit
MU Management Unit
NCTS Not Clear to Send
OSI Open Systems Interconnect
RTS Request to Send
SAI Systems Architecture and Interfaces Subcommittee
SAL System Address Labels
SOF Start of Field
SOT Start of Transmission
TEST Loop Test Pattern Word
VDL VHF Data Link
 NOTE: Due to the large number of changes
Created by this Supplement, it is NOT
available separately to update 429-11.

AERONAUTICAL RADIO, INC.

2551 Riva Road
Annapolis, Maryland 21401 – 7645 USA

SUPPLEMENT 12

TO

ARINC SPECIFICATION 429

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

Published: July 1, 1990

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: October 25, 1989

SUPPLEMENT 12 TO ARINC SPECIFICATION 429 PART 3 – Page 2

A. PURPOSE OF THIS SUPPLEMENT 2.5 Bit-Oriented Communications Protocol

This Supplement introduces the Williamsburg bit-oriented This new section was added to describe a bit-oriented data
file data transfer protocol which supports the transfer of transfer protocol. The new protocol was developed to
binary and character data. The previous AIM and accommodate the interface of the ACARS Management
character-oriented file data transfer protocol sections are Unit (MU) and the Satellite Data Unit (SDU).
moved to Appendix 6. The Sign Status Matrix (SSM)
information is revised and reorganized. In addition, this 3.2 AIM Information Transfer
Supplement introduces new label assignments and
equipment identification codes. The information previously contained in this section is no
longer applicable to ARINC Specification 429. For
reference purposes, the section header is retained and the
B. ORGANIZATION OF THIS SUPPLEMENT original contents of this section are located in Appendix
6.
The first part of this document, printed on goldenrod
paper contains descriptions of changes introduced into
this Specification by this Supplement and where ATTACHMENT 1 – LABEL CODES
appropriate extracts from the original text for comparison
purposes. The second part consists of replacement white The following labels have been given new assignments:
pages for the Specification, modified to reflect these
changes. The modified and added material on each 002 115 013 0B8 016 0B8 046 10A 046 10B 047 10A
replacement page is identified with “c-12” symbols in the 047 10B 107 0BB 110 0BB 112 0BB 114 0BB 114 10A
margins. Existing copies of ARINC Specification 429 114 10B 127 10A 127 10B 130 035 130 10A 130 10B
may be updated by simply inserting the replacement 131 035 132 035 133 10A 133 10B 134 10A 134 10B
white pages they replace. The goldenrod pages are 137 10A 137 10B 155 10A 155 10B 156 10A 156 10B
inserted inside the rear cover of the Specification. 157 10A 157 10B 160 10A 160 10B 161 10A 161 10B
201 115 203 035 203 10A 203 10B 205 10A 205 10B
Copies of the Specification bearing the number 429-12 211 10A 211 10B 220 116 221 116 222 115 222 116
already contain this Supplement and thus do not require 223 116 224 116 226 035 230 116 234 039 234 040
revision by the reader. 235 039 235 040 236 039 236 040 237 039 237 040
244 10A 244 10B 256 114 257 114 260 10A 260 10B
260 114 261 10A 261 10B 261 114 262 10A 262 10B
C. CHANGES TO ARINC SPECIFICATION 429 262 114 263 10A 263 10B 263 114 264 10A 264 10B
INTRODUCED BY THIS SUPPLEMENT 264 114 265 004 265 038 265 10A 265 10B 265 114
267 10A 267 10B 270 10A 270 10B 270 114 270 115
This section presents a complete tabulation of the changes 271 10A 271 10B 271 114 272 002 272 10A 272 10B
and additions to the Specification introduced by this 272 114 273 10A 273 10B 273 114 274 10A 274 10B
Supplement. Each change or addition is entitled by the 274 114 275 10A 275 10B 275 114 276 114 277 018
section number and the title currently employed in the 300 10A 300 10B 300 TBD 301 10A 301 10B 302 10A
Specification or by the section name and title that will be 302 10B 303 10A 303 10B 304 10A 304 10B 305 10A
employed when the Supplement is eventually 305 10B 306 10D 310 114 311 114 312 114 313 114
incorporated. In each case there is included a brief 316 10A 316 10B 320 035 321 10A 321 10B 322 10A
description of the addition or change and, for other than 322 10B 323 10A 323 10B 324 10A 324 10B 325 10A
very minor revision, any text originally contained in the 325 10B 326 10A 326 10B 327 10A 327 10B 330 10A
Specification is reproduced for reference. 330 10B 331 10A 331 10B 335 10A 335 10B 336 002
336 10A 336 10B 337 002 337 002 337 10A 337 10B
2.1.3 Information Identifier 341 10A 341 10B 342 10A 342 10B 343 10A 343 10B
344 10A 344 10B 345 10A 345 10B 346 10A 346 10B
This section contains editorial corrections to comply with 347 10A 347 10B 350 10A 350 10B 350 114 350 115
changes introduced in Supplement 11. 351 10A 351 10B 351 114 352 10A 352 10B 352 114
353 10A 353 10B 353 114 354 10A 354 10B 357 035
360 10A 360 10B 360 TBD 361 10A 361 10B 362 10B
2.1.5 Sign/Status Matrix 362 10B 362 115 363 10A 363 10B 365 TBD 372 10A
372 10B 373 10A 373 10B 374 10A 374 10B 374 TBD
This section was revised and reorganized. The changes 375 10A 375 10B 375 TBD
include moving the AIM and file transfer SSM definitions
to Appendix 6, adding failure reporting to the discrete
word truth table (Section 2.1.5.3) and moving the Revised label 130 035 from “Traffic Advisory Range” to
description of status priorities to Section 2.1.5. “Intruder Range”.
Revised label 131 035 from “Traffic Advisory Altitude”
2.3.1 Digital Language to “Intruder Altitude”.
The contents of Sections 2.3.1.4 through 2.3.1.5.7 were Revised label 132 035 from “Traffic Advisory Bearing”
moved to Appendix 6. The AIM Data and File Data to “Intruder Bearing”.
transfer section headings were retained for reference
purposes. Section 2.3.1.5, File Data Transfer, provides the Removed label 130 030 Traffic Advisory Range.
reason for moving the original file transfer protocol and
introduces the Williamsburg protocol. Removed label 131 030 Traffic Advisory Altitude.
 SUPPLEMENT 12 TO ARINC SPECIFICATION 429 PART 3 – Page 3

Removed label 132 030 Traffic Advisory Bearing ATTACHMENT 11A - DESTINATION CODES
Estimate.
Add new Attachment.
Removed label 270 030 Transponder Discrete.
ATTACHMENT 11B - STATUS CODES
Removed label 347 030 Sector Control.
Add new Attachment.
Removed 347 035 Antenna Control.
ATTACHMENT 11C - ALOHA/ALOHA RESPONSE
ATTACHMENT 1 – EQUIPMENT CODES PROTOCOL WORDS

The following codes have been given new assignments: Add new Attachment.

113, 114, 115, 116, 117, 118, 119, 11A, 123, 124, 125, ATTACHMENT 12 - FILE TRANSFER EXAMPLE
126, 127, 128, 129, 15A, 15B, 15C, 15D, 15E, 16A, 16B,
16C, 16D, 16E, 17A, 17B, 17C, 18A, 18B, 18C, 18D, Add new Attachment.
18E, 18F.
ATTACHMENT 12A - FIELD MAPPING EXAMPLE
ATTACHMENT 2 – DATA STANDARDS
Add new Attachment.
Tables 1, 2 updated to reflect changes to Attachment 1.
ATTACHMENT 13 - PROTOCOL DETERMINATION
Binary Data notes 6, 7 and 8 added. PROCEDURE DIAGRAMS

Add new Attachment.

Discrete Data Standards entered for new labels:
ATTACHMENT 14 – SYSTEM ADDRESS LABELS
272 002 271 018 272 018 273 018 275 018 276 018
277 018 274 018 270 035 271 035 273 035 274 035 Add new Attachment.
275 035 013 0B8 016 0B8 161 10A 161 10B 350 114
351 114 352 114 353 114 270 115 350 115 ATTACHMENT 15 - LINK LAYER CRD DATA
EXAMPLE

ATTACHMENT 6 – GENERAL WORD FORMATS Add new Attachment.

AND ENCODING EXAMPLES
APPENDIX 6 - FORMER MAINTENANCE, AIM AND
Add format for TCAS Intruder Range label 130. FILE TRANSFER TECHNIQUES

Add format for TCAS Intruder Altitude label 131. Add new Appendix.

Add format for TCAS Intruder Bearing label 132. APPENDIX 7 – MATHEMATICAL EXAMPLE OF
CRC ENCODING/DECODING
Add format for Transponder Altitude/TCAS Own A/C
Altitude label 203. Add new Appendix.
Removed 730 ASAS Sector Control Word example.

Removed 730 TCAS Traffic Advisory Range Word

example.

Removed 730 TCAS Traffic Advisory Bearing Estimate

Word example.

ATTACHMENT 9B – GENERAL AVIATION WORD

EXAMPLES

Add new Company Name Identifier.

ATTACHMENT 10 – VARIABLES OF BIT-

ORIENTED PROTOCOL

Add new Attachment.

ATTTACHMENT 11 – BIT-ORIENTED DATA FILE

TRANSFER WORD FORMATS

Add new Attachment.

 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401 – 7645 USA

SUPPLEMENT 13

TO

ARINC SPECIFICATION 429

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

Published: December 30, 1991

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: October 8, 1991

SUPPLEMENT 13 TO ARINC SPECIFICATION 429 – Page 2
A. PURPOSE OF THIS SUPPLEMENT
This Supplement introduces changes made to the
Williamsburg protocol as a result of its initial
implementation. This protocol supports the transfer of
binary and character data. In addition, this Supplement
introduces new label assignments and equipment
identification codes.
B. ORGANIZATION OF THIS SUPPLEMENT
The first part of this document, printed on goldenrod
paper contains descriptions of changes introduced into
this Specification by this Supplement. The second part
consists of replacement white pages for the Specification,
modified to reflect the changes. The modified and added
material on each page is identified by a c-13 in the
margins. Existing copies of ARINC Specification 429
may be updated by simply inserting the replacement
white pages where necessary and destroying the pages
they replace. The goldenrod pages are inserted inside the
rear cover of the Specification.
C. CHANGES TO ARINC SPECIFICATION 429
INTRODUCED BY THIS SUPPLEMENT
This section presents a complete tabulation of the changes
and additions to the Specification introduced by this
Supplement. Each change or addition is defined by the
section number and the title currently employed in the
Specification or by the section name and title that will be
employed when the Supplement is eventually
incorporated. In each case a brief description of the
change or addition is included.
AEEC STAFF NOTE: THESE CHANGES
APPLY TO ARINC 429, PART 3 ONLY.
2.3.1.5 File Data Transfer
An editorial change, correction to section numbering.
2.3.1.5.1 Bit-Oriented Protocol Determination
New Section added to describe ALO/ALR protocol
process to be used when a bilingual Link Layer protocol
system needs to determine necessary bit-oriented
interfaces.
2.5 Bit-Oriented communications Protocol
Included term “Williamsburg” parenthetically since this
terminology well-known in industry. Added commentary
to explain non-negotiation or parameters in this protocol.
D. Corrected Network Layer definition.
2.5.2 Link Data Unit (LDU) Size and Word Count
Added second paragraph to text, since it is a requirement,
and removed second paragraph from commentary.
2.5.4 Bit Rate and Word Timing
Corrected the commentary to change the more ambiguous
term “message” to LDU.
2.5.5.3 Destination Code
An editorial change was made.
2.5.6 Response to RTS
The last sentence in the second paragraph was reworded
and moved to a more appropriate section, 2.5.6.2.
2.5.6.1 Clear to Send (CTS)
In the second to last sentence, the word “valid” was added
to clarify the Not clear to send condition. The last
sentence was added to clarify the resetting of RTS
counters.
2.5.6.2 Not Clear to Send (NCTS)
The first paragraph was updated to include the
information deleted from Section 2.5.6 and to clarify the
validity requirements. The second paragraph was updated
to describe that and NCTS counter would be reset upon a
valid CTS response. The last sentence in the third
paragraph was deleted and it’s content expanded in the
following commentary of that section.
2.5.6.3 Destination Busy
The second paragraph of this section was updated to
indicate that a BUSY counter should be reset with a valid
CTS response to RTS.
2.5.7 No Response to RTS
The first paragraph of this section was updated to describe
proper response to RTS.
2.5.9 Unexpected RTS
This section was updated to include editorial changes and
a description of the correct responses to RTS. The last
sentence was deleted as redundant to Section in 2.5.13.1
and in conflict with other possible responses.
2.5.11 Data
The fourth paragraph of this section was updated to
describe the proper ending of an LDU transmission, and
to include the optional NAK response for receipt of an
incomplete octet.
2.5.11.3 Character Data Words
In the last paragraph, the “note” designator was removed
and the text clarified for the transfer of characters with a
parity bit.
2.5.13 Negative Acknowledgement (NAK)
This section was updated to clarify conditions for sending
the NAK word.
 SUPPLEMENT 13 TO ARINC SPECIFICATION 429 – Page 3

2.5.13.1 Missing SOT word ATTACHMENT 10 – VARIABLES OF BIT

Text was corrected to refer to “reception” instead of
“transmission” of a valid SOT word. Also, incorrect text
referring to the NAK response timing was deleted.
2.5.13.2 LDU Sequence Number Error
ORIENTED PROTOCOL
Tables 10-1 and 10-3 were updated to include events N5,
N6, and time T12. Options 07 and 012 in Table 10-4 were
changed to spares for consistency with corresponding text
updates.

The original text was omitted. Sections 2.5.13.1 –

2.5.13.7 were renumbered. ATTACHMENT 11C – ALOHA/ALOHA RESPONSE
PROTOCOL WORD DEFINITION
2.5.13.3 Parity Errors
Table 11C-3 was added to clarify protocol version
A commentary section was added to describe the number assignments, and is referenced by “note 1”.
procedures for receiving words with bad parity. “Note 2” was added to describe the GFI field of the
ALOHA word.
2.5.13.4 Word Count Errors
ATTACHMENT 12A – FIELD MAPPING EXAMPLE
This section was updated to clarify the NAK response
time for word count errors. Bk was changed to B24 in the data word map, “nibble” was
changed to “semi-octet”, and semi-octet arrow lengths
2.5.13.5 CRC Errors were shortened to correspond to the proper four and eight-
bit lengths.
This section was updated to clarify the NAK response
time for CRC errors. APPENDIX 7 – MATHEMATICAL EXAMPLE OF
CRC ENDODING/DECODING
2.5.13.6 Time Out Errors
Format (alignment) changes were made in the polynomial
This section was renumbered. divisions, “(X)” was corrected to “Q(x)”, and the
transmission order for the LDU Mapping of the 24-bit
2.5.13.7 Restart Initialization example was deleted to avoid possible misinterpretation.

This section was omitted due to potential conflicts with

the ALO/ALR procedures.

2.5.14 LDU Transfer Acknowledgement (ACK)

Text was revised to include LDU conditions for sink

acknowledgement transmission.

2.5.14.1 Duplicate LDU

This section was added to describe duplicate LDU

occurrences.

2.5.14.2 Auto-Synchronized Files

This section was added to describe the method of

handling auto-synchronized files.

2.5.15 SYN Word

New text was added to describe SYN response times for

non-consecutive LDU Sequence numbers. The last
paragraph was incorrect and deleted.

2.5.16 Response to ACK/NAK/SYN

New text was added to describe actions when NAK and

SYN are detected during a transmission.

2.5.19 ALO Response

A new section was added and updated to describe ALO

responses.
 Copyright 1993 by
AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401 – 7645 USA

SUPPLEMENT 14

TO

ARINC SPECIFICATION 429

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

Published: January 4, 1993

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: November 4, 1992

SUPPLEMENT 14 TO ARINC SPECIFICATION 429 – Page 2
A. PURPOSE OF THIS SUPPLEMENT
This Supplement introduces changes made to increase the
efficiency of data transfer across an ARINC 429 high
speed bit-oriented link. This protocol supports the
transfer of binary and character data.
B. ORGANIZATION OF THIS SUPPLEMENT
The first part of this document, printed on goldenrod
paper, contains descriptions of changes introduced into
this Specification by this Supplement. The second part
consists of replacement white pages for the Specification,
modified to reflect the changes. The modified and added
material on each page is identified by a c-14 in the
margins. Existing copies of ARINC 429 may be updated
by simply inserting the replacement white pages where
necessary and destroying the pages they replace. The
goldenrod pages are inserted inside the rear cover of the
Specification.
C. CHANGES TO ARINC SPECIFICATION 429
INTRODUCED BY THIS SUPPLEMENT
This section presents a complete tabulation of the changes
and additions to the Specification introduced by this
Supplement. Each change and addition is defined by the
section number and the title currently employed in the
Specification or by the section name and title that will be
employed when the Supplement is eventually
incorporated. In each case a brief description of the
change or addition is included.
AEEC STAFF NOTE: THESE CHANGES
APPLY TO ARINC 429, PART 3 ONLY.
2.3.1.5 File Data Transfer
An editorial change was needed to reference new section.
2.3.1.5.1 Bit-Oriented Protocol Determination
This section was expanded to include determination of
different version numbers of the bit-oriented protocol, and
was moved to Section 2.5.19.
2.5 Bit-Oriented Communication Protocol
An editorial change references a new section number.
2.5.4 Bit Rate and Word Timing
A maximum word gap of 64 bit-times, (averaged over the
LDU transmission) was added to eliminate excessive
delay in source transmission time.
Note: Sections 2.5.5 through 2.7 have been renumbered
and reordered for consistency.
2.5.5 Word type
The basic definition of “word type” was corrected to
include bits 31-29 in all bit-oriented words of an LDU.
2.5.6 Protocol Words
This section was added to specifically define the word
type for protocol words.
2.5.6.1 Protocol Identifier
This section was added to clarify the definition of bits 28-
25 for protocol words and to specify the relevant addition
for error conditions.
2.5.6.2 Destination Code
This section was updated, and a commentary added, to
clarify the role of the link layer protocol for upward
compatibility with changing network functionality. The
requirement for Destination code validation is not a link
layer function.
2.5.6.3 Word Count
This section was renumbered.
2.5.7 Request to Send (RTS)
This section was previously titled “Response to TS”, and
has been renumbered. The title was changed for
consistency, and an introductory paragraph added to
clarify the basic RTS function.
2.5.7.1 Clear to Send (CTS)
This section was renumbered.
2.5.7.2 Not Clear to Send (NCTS)
This section was renumbered.
2.5.7.3 Destination Busy
This section was renumbered, and an introductory
replacement paragraph inserted to clarify the “optional”
BUSY response, which may be used when a system
cannot accept a transmission by the source in a “timely
manner”. New commentary equates a “timely manner” to
the shorter retry sequence of the NCTS series.
2.5.7.4 No Response to RTS
This section was renumbered, and the ALOHA word was
included in the logic for error determination.
2.5.10 Start of Transmission (SOT)
Timer T13 was added as a requirement on the source to
begin transmission of an LDU within a specified interval
after receipt of the CTS word from the sink.
2.5.10.1 General Format Identifier (GFI)
This section was updated, and commentary added to
clarify the role of the GFI in pre-OSI as well as OSI
environments. Validation of the GFI code is required by
a high level entity (network layer) in both environments
to determine the format of the data words to follow. GFI
validation is not necessarily a link layer function.
 SUPPLEMENT 14 TO ARINC SPECIFICATION 429 – Page 3
2.5.11 Data
All references to Character Data word formats were
deleted.
2.5.11.3 Character Data Words
This section was deleted. The Character Data Word
format was removed from Supplement 14, as the format is
incompatible with those for Full and Partial Data word
formats. Currently, both binary and character data are
transmitted in octets defined by the other two data word
formats. The special character data format is not
required.
2.5.12.1 CRC Encoding
References to character data words were deleted. The
text for equation: M9x) = x16G(x) + R(x) was corrected
by moving the “bar” from G(x) to R(x).
2.5.13 Negative Acknowledgement (NAK)
NAK word interpretation was changed to remove
constraint on source for specific order of file sequencing
(i.e. Allows source to restart file with new FSN if
necessary).
2.5.14.1 Duplicate LDU
This first paragraph was rewritten to clarify.
2.5.14.3 Incomplete File Timer
This section was added to allow the sink to discard a
partial file of multiple LDUs when the T14 timeout
between LDU transmissions is exceeded. It ensures that a
source device cannot “lock-up” a sink.
2.5.15 SYN Word
The LDU sequence anomalies which generate a SYN
response by the sink were clarified.
2.5.16 Response to ACK/NAK/SYN
The T16 timer was introduced to replace T10 and T8. Also,
the action taken by the source upon receipt of a SYN
word was updated, which relaxes requirements to
maintain a specific File Sequence ordering by the source.
2.5.19 Protocol Initialization
2.5.19.1 Bit-Oriented Protocol Version,
2.5.19.2 ALOHA Response, and
2.5.19.3 Character-429 Determination
This section has been added to replace and expand on the
definition of the process to determine the link layer
protocol version supported by an interfacing system.
These sections replace three sections from Supplement
13.
2.3.1.5.1 Bit-Oriented Protocol Determination
2.5.19 ALO Response, and
2.5.20 Bit Protocol Verification
2.6 Windowed Bit-Oriented Protocol
This is a completely new section which contains the
system description of the new LLC2-like bit-oriented link
layer protocol for 429. It is based on Section 2.5, “Bit-
Oriented Communications Protocol”, with expanded text
as specified to allow for more efficient use of the 429
high (or low) speed data bus through “windowing”. The
definition includes provision for a Link Control Word
prior to each LDU.
ATTACHMENT 1 – EQUIPMENT CODES
New Equipment Code Identifiers were added.
ATTACHEMENT 6 – WORD FORMATS AND
ENCODING EXAMPLES
Example added for label 171.
ATTACHMENT 10 – VARIABLES OF BIT
ORIENTED PROTOCOL
Table 10-1 was updated to include a standard value for
N7, the maximum number of LDUs in a window (see
Section 2.6 “Windowed Bit-Oriented Protocol”).
Table 10-3 deleted Option 6 (O6) for NAK Send Time,
and deleted Option 9 (O9) for the Character Data Word,
both of which are no longer used.
Table 10-4 was revised to include columns for low speed
maximum and minimum values. These values were
established for timers and as response time design goals
for incoming transmissions. Timers T13 through T16 were
added.
Table 10-5 was added to include a definition of high
speed maximum and minimum values for timers and
response time design goals. The format is the same as the
revised Table 10-4. Timer T10 is not used in the high
speed protocol.
Table 10-6 was added to include notes to Tables 10-1
through 10-5.
ATTACHMENT 11 – BIT-ORIENTED DATA FILE
TRANSFER WORD FORMATS
Table 11-1A added “spares” for the deleted Character
Data Formats and corrected “Protocol Data Word” to read
“Protocol Word”.
Table 11-4 updated definitions for bits 9 through 24 of the
ALO and ALR words, and added the LCW (LDU Control
Word) format definition.
Table 11-4A was added as a partial replacement for
ATTACHMENT 11C and Table 11-4B was added to
define the new window definitions for the Windowed Bit-
Oriented protocol in Section 2.6.
Table 11-6A was revised, changing the former GFI bit
pattern (0001) for ISO 8208 to “unassigned”. The bit
pattern (0100) for ISO 8473 was changed to a more
SUPPLEMENT 14 TO ARINC SPECIFICATION 429 – Page 4

ATTACHMENT 11 – BIT-ORIENTED DATA FILE

TRANSFER WORD FORMATS (cont’d)
generic ISO 9577 definition. The bit pattern 1110
(hex”E”) is now defined as “ACARS VHF Format”.The
“NOTES” in ATTACHMENT 11 have been renumbered
to correspond to the new table definitions.

ATTACHMENT 11C – ALOHA/ALOHA RESPONSE

PROTOCOL WORD DEFINITION

This Attachment has been deleted. This information has

been moved to Tables 11-4, 11-4A, and 11-4B.

ATTACHMENT 13A – ALOHA VERSION

DETERMINATION SEQUENCE

This Attachment was added to support the ALOHA

version determination sequence called out in Section
2.5.19.1.1.
ATTACHMENT 14 – SYSTEM ADDERESS LABELS

New System Address Labels (SAL) were added.

ATTACHMENT 16 – SEQUENCE OF PROTOCOL

AND DATA WORDS IN WINDOW TRANSFER

This Attachment was added to illustrate the window

transfers for new Section 2.6.

ATTACHMENT 17 – FLOW DIAGRAM USED TO

DETERMINE CHARACTER-ORIENTED VS BIT-
ORIENTED PROTOCOL

This Attachment was added to illustrate the logic flow

that determines whether a character-oriented or bit-
oriented link layer protocol interface is to be used.
 Copyright 1995 by
AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401 – 7645 USA

SUPPLEMENT 15

TO

ARINC SPECIFICATION 429

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

PART 3

FILE DATA TRANSFER TECHNIQUES

Published: August 31, 1995

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: April 18, 1995

SUPPLEMENT 15 TO ARINC SPECIFICATION 429 PART 3 – Page 2

A. PURPOSE OF THIS SUPPLEMENT ATTACHMENT 10 - VARIABLES OF BIT-ORIENTED

PROTOCOL
This portion of Supplement 15 provides corrections and
additions to the file transfer provisions of ARINC Revised Notes 1 and 4.
Specification 429. The reader should note that the
organization of ARINC 429 has been described in Section Table 10-3 BIT-ORIENTED PROTOCOL OPTIONS -
B below. Added Option 012.

Appendix C was added to assist designers in establishing Table 10-5 VARIABLES OF HIGH SPEED BIT-
connectivity between LRUs designed to different versions ORIENTED PROTOCOL - Revised Time T10 min and
of Specification 429. Appendix D comprises the max values.
Specification and Description Language (SDL) diagrams
that reflect the intent of the textual material. The SDL ATTACHMENT 11 - BIT-ORIENTED DATA FILE
diagrams have not been fully proofed, and remain TRANSFER WORD FORMATS
advisory in nature. Therefore, the text material has
precedence over the SDL diagrams. When the SDL Table 11-6A GENERAL FORMAT IDENTIFIER (GFI) -
diagrams have been validated, they will be moved to an Revised “Reserved ISO 9577” to “ISO 9577”
Attachment.
ATTACHMENT 11A - DESTINATION CODES
B. ORGANIZATION OF THIS SUPPLEMENT
Added Cabin Packet Data Function. Corrected Ground
The portion of this document, printed on goldenrod paper, Station bit encoding.
contains descriptions of changes introduced into this
Specification by this Supplement. In the text, printed on ATTACHMENT 11B - STATUS CODES
white paper, the modified and added material on each
page is identified by a c-15 in the margins. In view of the Revised description of Code 86. Added entries for Code
document reorganization, existing copies of ARINC 429 8E through 95.
cannot be updated.
ATTACHMENT 14 - SYSTEM ADDRESS LABELS
This Supplement is the first in which ARINC
Specification 429 is divided into three parts. This part, The following labels were added:
Part 3, contains the definition of the protocols used for 170 DFDAU (Mandatory Load Function)
file data transfer. Typically, file data transfer is non- 266 Cabin Video System (Airshow)
periodic in nature. 334 Cabin Telecommunications Unit (CTU)
340 HF Data Radio/Data Unit #1
The fundamental physical layer descriptions of the wire, 344 HF Data Radio/Data Unit #2
voltage levels and coding of data are contained in Part 1.
Part 1 also contains the listing of data word labels The following labels were revised:
assigned for the transmission of broadcast periodic data. 175 HGA HPA
176 Spare
Part 2 contains a tabulation of the ever-increasing list of 177 LGA HPA
Discrete data words used to provide status information.
APPENDIX 8 - INTEROPERABILITY OF BIT-
ORIENTED LINK LAYER PROTOCOL
C. CHANGES TO ARINC SPECIFICATION 429
INTRODUCED BY THIS SUPPLEMENT Appendix added.

This section presents a complete tabulation of the changes APPENDIX 9 - SDL DIAGRAMS OF THE
and additions to the Specification introduced by this WILLIAMSBURG PROTOCOL
Supplement. Each change and addition is defined by the Appendix added.
section number and the title currently employed in the
Specification or by the section name and title that will be
employed when the Supplement is eventually
incorporated. In each case, a brief description of the
change or addition is included. A tabulation of sections is
included with this supplement to enable the reader to
correlate the previous section assignments with the new
Part 3 Supplement 15 section number assignments.

The following changes affect only ARINC Specification

429-15, Part 3, File Data Transfer Techniques. Refer to
Parts 1 and 2 for changes impacting the broadcast
provisions of ARINC Specification 429.
 SUPPLEMENT 15 TO ARINC SPECIFICATION 429 PART 3 – Page 3

ARINC Specification 429 is now available in three separate parts: Part 1 “Functional Description and Word Formats”,
Part 2 “Digital Information Transfer System Standards” and Part 3 “File Data Transfer Techniques.” The changes are
described in Supplements printed on goldenrod colored paper. The following pages provided a record of the section
numbering of the text now included in Part 3.

Old Number New Number

(Supp 14) (Supp 15) Section Title

1.1 1.1 Purpose of this Document

1.2 1.2 Relationship to ARINC Specification 419 changed to 429
1.3 1.3 “Mark 33 Digital Information Transfer System”_ - Basic Philosophy
changed to: “File Data Transfer Techniques”
1.3.1 1.3.1 Number Data Transfer changed to: Data Transfer
1.3.2 1.3.2 ISO Alphabet No. 4 Data Transfer changed to: Broadcast Data
1.3.3 1.3.3 Graphic Data Transfer
2.3.1.5 2.1 File Data Transfer
2.3.1.5.1 2.3 Bit-Oriented Protocol Determination
2.3.2 2.2 Transmission Order
2.5 Chapter 3.0 Bit-Oriented Communications Protocol changed to:
Bit Oriented File Transfer Protocol
2.5 3.1 Bit-Oriented File Transfer Protocol
2.5.1 3.2 Link Data Units (LDU)
2.5.2 3.3 Link Data Unit (LDU) Size and Word Count
2.5.3 3.4 System Address Labels (SAL)
2.5.4 3.5 Bit Rate and Word Timing
2.5.5 3.6 Word Type
2.5.6 3.7 Protocol Words
2.5.6.1 3.7.1 Protocol Identifier
2.5.6.2 3.7.2 Destination Code
2.5.6.3 3.7.3 Word Count
2.5.7 3.8 Request To Send (RTS)
2.5.7.1 3.8.1 Clear To Send (CTS)
2.5.7.2 3.8.2 Not Clear To Send (NCTS)
2.5.7.3 3.8.3 Destination Busy (BUSY)
2.5.7.4 3.8.4 No Response to RTS
2.5.8 3.9 Conflicting RTS Transmissions
2.5.8.1 3.9.1 Half Duplex Mode
2.5.8.2 3.9.2 Full Duplex Mode
2.5.9 3.10 Unexpected RTS
2.5.10 3.11 Start of Transmission (SOT)
SUPPLEMENT 15 TO ARINC SPECIFICATION 429 PART 3 – Page 4

Old Number New Number

(Supp 14) (Supp 15) Section Title

2.5.10.1 3.11.1 General Format Identifier (GFI)

2.5.10.2 3.11.2 File Sequence Number
2.5.10.3 3.11.2 LDU Sequence Number
2.5.11 3.12 Data
2.5.11.1 3.12.1 Full Data Word(s)
2.5.11.2 3.12.2 Partial Data Word(s)
2.5.12 3.13 End of Transmission (EOT)
2.5.12.1 3.13.1 CRC Encoding
2.5.12.2 3.13.2 CRC Decoding
2.5.13 3.14 Negative Acknowledgement (NAK)
2.5.13.1 3.14.1 Missing SOT Word
2.5.13.2 3.14.2 Missing EOT Word
2.5.13.3 3.14.3 Parity Errors
2.5.13.4 3.14.4 Word Count Errors
2.5.13.5 3.14.5 CRC Errors
2.5.13.6 3.14.6 Time Out Errors
2.5.14 3.15 LDU Transfer Acknowledgement (ACK)
2.5.14.1 3.15.1 Duplicate LDU
2.5.14.2 3.15.2 Auto-Synchronized Files
2.5.14.3 3.15.3 Incomplete File Time
2.5.15 3.16 SYN Word
2.5.16 3.17 Response to ACK/NAK/SN
2.5.17 3.18 Solo Word
2.5.17.1 3.18.1 Test Word and Loop Word
2.5.17.2 3.18.2 Optional Solo Word Definitions
2.5.18 3.19 Optional End-to-End Message Verification
2.5.19 3.20 Protocol Initialization
2.5.19.1 3.20.1 Bit-Oriented Protocol Version
2.5.19.1.1 3.20.1.1 ALOHA
2.5.19.1.2 3.20.1.2 ALOHA Response
2.5.19.2 3.20.2 Williamsburg/File Transfer Determination
2.6 Chapter 4.0 Window Bit-Oriented Protocol change to:
Window Bit-Oriented File Transfer Protocol
2.6 4.1 Windowed Bit-Oriented Protocol change to:
Windowed Bit-Oriented Communications Protocol
2.6.1 4.2 Window Size
2.6.2 4.3 Window Definition
 SUPPLEMENT 15 TO ARINC SPECIFICATION 429 PART 3 – Page 5

Old Number New Number

(Supp 14) (Supp 15) Section Title

2.6.3 4.4 Protocol Word Deltas

2.6.3.1 4.4.1 Request To Send (RTS)
2.6.3.1.1 4.4.1.1 Unexpected Request To Send (RTS)
2.6.3.2 4.4.2 Clear To Send (CTS)
2.6.3.3 4.4.3 Not Clear To Send (NCTS)
2.6.3.4 4.4.4 BUSY
2.6.3.5 4.4.5 LDU Control Word (LCW)
2.6.3.6 4.4.6 Start Of Transmission (SOT)
2.6.3.7 4.4.7 Negative Acknowledgement (NAK)
2.6.3.7.1 4.4.7.1 Missing LDU Control Word
2.6.3.7.2 4.4.7.2 Missing SOT Word
2.6.3.7.3 4.4.7.3 Missing EOT Word
2.6.3.7.4 4.4.7.4 Parity Errors
2.6.3.7.5 4.4.7.5 Word Count Errors
2.6.3.7.6 4.4.7.6 CRC Errors
2.6.3.7.7 4.4.7.7 LDU Timeout Errors
2.6.3.8 4.4.8 Window Transfer Acknowledgement (ACK)
2.6.3.8.1 4.4.8.1 Determination of End of Window
2.6.3.8.2 4.4.8.2 Incomplete File Timer
2.6.4 4.5 Bit Rate and Word Timing
2.6.5 4.6 Response to ACK/NAK/SYN
2.6.6 4.7 Protocol Initialization Deltas
2.6.6.1 4.7.1 ALOHA
2.6.6.2 4.7.2 ALOHA Response
ATT 10 ATT 1 Variables of Bit-Oriented Protocol
Table 10-1 Table 1-1 Bit-Oriented Protocol Events
Table 10-2 Table 1-2 Bit-Oriented Protocol Application Selection
Table 10-3 Table 1-3 Bit-Oriented Protocol Options
Table 10-4 Table 1-4 Variables of Low Speed Bit-Oriented Protocol
Table 10-5 Table 1-5 Variables of High Speed Bit-Oriented Protocol
ATT 11 ATT 2 Bit-Oriented Data File Transfer Word Formats
Table 11-1 Table 2-1 General Word Format
Table 11-1A Table 2-1A Word Type
Table 11-2 Table 2-2 Full Data Word
Table 11-2 Table 2-3 Partial Data Word
Table 11-4 Table 2-4 Protocol Word
Table11-4A Table 2-4A ALO-ALR Version Number
Table 11-4B Table 2-4B ALO-ALR Window Size
Table 11-5 Table 2-5 Solo Word
Table 11-6 Table 2-6 Start of Transmission
Table 11-6A Table 2-6A General Format Identifier (GFI)
Table 11-7 Table 2-7 End of Transmission
Table 11-7A Table 2-7A Final LDU Bit
ATT 11A ATT 3 Destination Codes
SUPPLEMENT 15 TO ARINC SPECIFICATION 429 – Page 6

Old Number New Number

(Supp 14) (Supp 15) Section Title

ATT 11B ATT 4 Status Codes

ATT 11C ATT 5 ALOHA/ALOHA Response Protocol Word Definition
Table 11C-1 Table 5-1 ALOHA Initial (ALO) Protocol Word
Table 11C-2 Table 5-2 ALOHA Response (ALR) Protocol Word
Table 11C-3 Table 5-3 Version Number for ALO/ALR Protocol Words
ATT 12 ATT 6 File Transfer Example
ATT 12A ATT 7 Field Mapping Exchange
ATT 13 ATT 8 Protocol Determination procedure Diagrams
Diagram 13-1 Diagram 8-1 Protocol Determination Procedure Diagram (Two Bilingual Units)
Diagram 13-2 Diagram 8-2 Protocol Determination Procedure Diagram (One Bilingual Unit and One
Diagram 13-3 Diagram 8-3 Character-Only Unit)
ATT 13A ATT 9 ALOHA Version Determination Sequence
ATT 15 ATT 10 Link Layer CRC Data Example
ATT 16 ATT 11 Sequence of Protocol and Data Words in Window Transfer
ATT 17 ATT 12 Flow Diagram Used to Determine Character-Oriented vs Bit-Oriented Protocol
APPENDIX 6 APPENDIX A Former AIM and File Data Transfer Techniques
A6-2.1.5 A2.1.5 Sign/Status Matrix
A6-2.1.5.2 A2.1.5.2 AIM Data
A6-2.1.5.3 A2.1.5.3 Character-Oriented File Transfer
A6-2.3.1 A2.3.1 Digital Language
A6-2.3.1.4 A2.3.1.4 AIM Data
A6-2.3.1.5 A2.3.1.5 File Data Transfer
A6-2.3.1.5.1 A2.3.1.5.1 Command/Response Protocol
A6-2.3.1.5.2 A2.3.1.5.2 Initial Word Types
A6-2.3.1.5.3 A2.3.1.5.3 Intermediate Words
A6-2.3.1.5.4 A2.3.1.5.4 Final Words
A6-2.3.1.5.5 A2.3.1.5.5 Word Type Encoding
A6-2.3.1.5.6 A2.3.1.5.6 File Data Formats
A6-2.3.1.5.7 A2.3.1.5.7 File Data Labels
A6-3.2 A-3.2 AIM Information Transfer
A6-3.2.1 A3.2.1 Acknowledgement Data
A6-3.2.2 A3.2.2 ISO Alphabet No. 5 Data
A6-3.2.3 A3.2.3 Maintenance Data
APPENDIX 7 APPENDIX B Mathematical Example of CRC Encoding/Decoding
APPENDIX 8 APPENDIX C Interoperability of Bit-oriented Link Layer Protocol
APPENDIX 9 APPENDIX D SDL Diagrams of Williamsburg Protocol
 Copyright 1997 by
AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401 - 7645 USA

SUPPLEMENT 16

TO

ARINC SPECIFICATION 429

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

PART 3

FILE DATA TRANSFER TECHNIQUES

Published: June 30, 1997

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: June 24, 1997

SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 3 – Page 2
A. PURPOSE OF THIS SUPPLEMENT
This Supplement reorganizes Part 3 to be consistent with
previous published versions of ARINC Specification 429.
It also restores several paragraphs missing from
Supplement 15.
The technical changes include clarification of the Version
1 (Williamsburg) protocol, deletion of the Version 2
protocol, and creation of the Version 3 protocol. The
definition of the Version 3 protocol will be completed in a
future Supplement.
B. ORGANIZATION OF THIS SUPPLEMENT
The first part of this document, printed on goldrod
colored paper, contains descriptions of the changes
introduced into this Specification by this Supplement. The
second part, printed on white paper, contains the changes
made to the specification. The modified and added
material on each page is identified by a c-16 in the
margins. In view of the document reorganization, ARINC
Specification 429, Part 3, is reprinted in its entirety as
ARINC Specification 429-16, Part 3.
C. CHANGES TO ARINC SPECIFICATION 429,
INTRODUCED BY THIS SUPPLEMENT
This section presents a complete tabulation of the changes
and additions to the Specification introduced by this
Supplement. Each change and addition is defined by the
Section number and the title that will be employed when
the Supplement is eventually incorporated. In each case,
a brief description of the change or addition is included.
1.0 Introduction
This section contains a reorganization of the material
previously in Section 1.0 and 2.0 of ARINC Specification
419P3-15 with the following exceptions.
The section on Graphic Data Transfer (formerly 1.3.4) is
deleted, Sections 1.3, 1.3.1, 1.3.2, and 1.3.4 include minor
changes clarifying the background for file data transfer,
and Section 1.3.6 on Bit-Oriented Protocol Determination
(formerly 1.3.7) was revised to refer to Section 2.5.19.
2.0 Bit-Oriented File Transfer Protocol
Section number 2.1 – 2.4 have been inserted as
placeholders to re-establish section numbering
consistency with ARINC Specification 429-14 and its
predecessors.
Section 2.5 and subsections contain the material previously
published in Section 3.0 of ARINC Specification 429P3-
15, as modified below.
2.5 Bit-Oriented Communications Protocol
References to Attachments 12 and 12A updated.
2.5.1 Link Data Units (LDU)
The definition of LDU is clarified.
2.5.3 System Address labels (SALs)
Commentary on use of SALs clarified.
2.5.4 Bit Rate and Word Timing
Commentary on use of word gap criteria clarified.
2.5.6.2 Destination Code
Introduction to section added, and use of Destination Code
clarified.
2.5.6.3 Word Count
Introduction to section added.
2.5.7.3 Destination Busy (BUSY)
The use of Option 3 (Send Auto CTS) and Option 4
(Accept Auto CTS) is clarified.
2.5.81 Half Duplex Mode
This section restores text missing from the published
version of Part 3, Supplement 15.
2.5.11.2 Partial Data Word
Location of the length of a partial data word is clarified.
2.5.14.1 Duplicate LDU
The definition of a duplicate LDU is clarified.
2.5.15 SYN Word
The definition of a duplicate LDU is clarified.
2.5.19 Protocol Initialization
The protocol version determination is clarified.
2.5.19.1 Bit-Oriented Protocol Version
The protocol version determination is clarified.
2.5.19.1.1 ALOHA
The protocol version determination is clarified.
2.5.19.1.2 ALOHA Response
This section restores text missing from the published
version of Part 3, Supplement 15.
2.5.19.2 Williamsburg/File Transfer Determination
This section restores text missing from the published
version of Part 3, Supplement 15, and commentary is added
on use of a NAK in the protocol determination logic.
2.6 Windowed Bit-Oriented Communications Protocol
Section 2.6 and subsections have been deleted. Section 2.6
contained the definition of Version 2 of the Williamsburg
protocol. Version 2 of the Williamsburg protocol has been
superseded by Version 3. Section 2.6 and subsections
contained the material previously published in Section 4.0
of ARINC Specification 429P3-15.
 SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 3- Page 3

ATTACHMENT 16 - SEQUENCE OF PROTOCOL

3.0 Bit-Oriented Media Access Control (MAC) AND DATA WORDS IN WINDOWN TRANSFER

An introduction to the Bit-Oriented Media Access Control
(Williamsburg Version 3) protocol is added.
ATTACHMENTS 1-17
Attachment numbers 1-9 have been inserted as
placeholders to re-establish section numbering consistency
with ARINC Specification 429-14 and its predecessors.
This section is deleted as part of the Version 2 protocol.
APPENDICES A-K
Appendix numbers A-E have been inserted as
placeholders to re-establish section numbering
consistency with ARINC Specification 429-14 and its
predecessor.

Attachments 10-17 contain material published in
Attachments 1-12 of ARINC Specification 429P3-15, as
modified below.
ATTACHMENT 10 - VAIABLES OF BIT-ORIENTED
PROTOCOL
Appendices F-J contain the material published in
Appendices A-D of ARINC 429P3-15.
Appendix H was revised to reflect the deletion of the
Version 2 protocol and creation of the Version 3 protocol.

Table 10-3 is replaced with Table 10-3A, containing

options for Version 1. Tables 10-3B, 10-6 and 10-7 are
added as placeholders for Version 3 Williamsburg.
Variables for the Version 2 protocol in Tables 10-1 and 10-
3A are deleted.

ATTACHMENT 11 - BIT-ORITENTED DATA FILE

TRANSFER WORD FORMATS

The general word format in Table 11-1 is clarified.

The LCW protocol word format in Table 11-4 is

modified.

Table 11-4 is modified to add the Service Class Identifier

to the LCW format.

Table 11-4B is deleted as part of the Version 2 protocol.

Table 11-4A is modified to add the version number for

Version 3, and delete references to Version 2.

ATTACHMENT 11A - DESTINATION CODES

The destination Code N for FMC, Center, is added.

ATTACHMENT 11C - ALOHA/ALOHA RESPONSE

PROTOCOL WORD DEFINTION

The ALOHA and ALOHA Response protocol word

definitions are revised to be consistent with other changes
made to the protocol, and the titles of the tables modified
to indicate they are examples.

ATTACHMENT 12 - VERSION 1 FILE TRANSFER

EXAMPLE

The title is changed to indicate Version 1.

ATTACHMENT 12A - FIELD MAPPING EXAMPLE

Attachment 12A is replaced with an updated example

ATTACHMENT 15 - LINK LAYER CRC DATA

EXAMPALE

This section is deleted as part of the Version 2 protocol.

 Copyright© 1999 by
AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401-7465 USA

SUPPLEMENT 17
TO
ARINC SPECIFICATION 429©
MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)
PART 3
FILE DATA TRANSFER TECHNIQUES

Published: May 31, 1999

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: March 31, 1999
SUPPLEMENT 17 TO ARINC SPECIFICATION 429 PART 3 – Page 2

A. PURPOSE OF THIS SUPPLEMENT ATTACHMENT 11 - BIT ORIENTED DATA FILE

This Supplement introduces the definition of a new bit-
oriented file data transfer protocol. The protocol is designed
to be consistent with the IEEE-802 Media Access Control
(MAC) protocol definition. Version 3 fills the role intended
for Version 2 of the Williamsburg protocol by providing a
high throughput avionics file data transfer interface. Version
2 was deleted by Supplement 16. Version 3 is intended to
be capable of being bridged to other common data bus
protocols, most significantly, Ethernet.
B. ORGANIZATION OF THIS SUPPLEMENT
Changes introduced by Supplement 17 were deemed
sufficiently significant to issue an entirely new publication
of Specification 429 Part 3. There is no standalone
Supplement.
TRANSFER WORD FORMATS
Table 11-1A was updated to add Version 3 SOF and EOF
words.
Table 11-8 was added defining the command frame SOF.
Table 11-9 was added defining the command frame EOF.
Table 11-10 was added defining the information frame
SOF.
Table 11-11 was added defining the information frame
EOF.
ATTACHMENT 18 – MAC SUBLAYER SUPPORT
DIAGRAMS

This part, printed on goldenrod-colored paper, contains a New Attachment added.

list of descriptions of changes introduced into this
Specification by this Supplement 17.
In the body of the document, the changes (.i.e., the modified
and added material) introduced by Supplement 17 are
identified by c-17 change bars in the margins.
C. CHANGES TO ARINC SPECIFICATION 429, PART
3 INTRODUCED BY THIS SUPPLEMENT
This section presents a complete tabulation of the changes
and additions to the Specification introduced by this
Supplement. In the text below, the Section number and title
of each affected Section, Attachment or Appendix is listed,
followed by a brief description of the change or addition.
1.3.5 Transmission Order
Transmission order of bits was clarified.
ATTACHMENT 19 – COMMAND FRAME DATA
UNIT (FDU) STRUCTURE AND EXAMPLES
New Attachment added.
ATTACHMENT 20 – INFORMATION FRAME DATA
UNIT (FDU) STRUCTURE AND EXAMPLES
New Attachment added.
APPENDIX 8 - INTEROPERABILITY OF BIT-
ORIENTED LINK LAYER PROTOCOL
Appendix 8 is updated to discuss interoperability between
Version 1 and Version 3.
APPENDIX 10 - ARINC 429 WILLIAMSBURG
PROTOCOL LAYER DIAGRAM

1.4 Relationship to Other Standards
A new section was added. It discusses the relationship of
this document to other AEEC documents and to other
industry documents.
A new Appendix was added providing a general
overview of the protocol structure over different
communication stacks.

3.0 Bit-Oriented Media Access Control Protocol

The definition of the bit-oriented Media Access Control
(Williamsburg Version 3) protocol was added, replacing
introductory text inserted by Supplement 16 as a
placeholder.
ATTACHMENT 10 - VARIABLES OF BIT-ORIENTED
PROTOCOL

Table 10-3B, containing options for Version 3, was added.

Table 10-6, containing timer values for the ARINC 429

high-speed Version 3 bus, was added.
Table 10-7, containing a placeholder for low speed bus
timers associated with Version 3 protocol was deleted
because the low speed implementation is not recommended.
 Copyright© 1999 by
AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401-7465 USA

SUPPLEMENT 18
TO
ARINC SPECIFICATION 429©
MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)
PART 3
FILE DATA TRANSFER TECHNIQUES

Published: October 12, 2001

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: July 18, 2001
SUPPLEMENT 18 TO ARINC SPECIFICATION 429 PART 3 - Page 2

A. PURPOSE OF THIS SUPPLEMENT

This Supplement introduces the assignment of 3 new
satellite links, HFDR Right, TAWS, and CVR into the
Destination Code table.

A Table was added to define the Variables of Low Speed

Connectionless Bit-Oriented Protocol.

Typographical errors were corrected in the text.

B. ORGANIZATION OF THIS SUPPLEMENT
The first part of this document printed on golden-rod paper
contains descriptions of changes introduced into this
Specification by this Supplement.

The changes introduced by Supplement 18 have been

identified using change bars and are labeled in the margin
by a “c-18” indicator.
C. CHANGES TO ARINC SPECIFICATION 429, PART
3 INTRODUCED BY THIS SUPPLEMENT

This section presents a complete tabulation of the changes

and additions to the Specification to be introduced by this
Supplement. Each change or addition is identified by the
section number and the title that will be employed for that
section when the Supplement is eventually incorporated. In
each case a brief description of the change or addition is
included.

3.4.3 System Address Labels (SAL)

Corrected the reference to the table of SAL assignments

(from Attachment 14 to Attachment 11) in ARINC
Specification 429 Part 1.

3.4.4 Bit Rate and Word Timing

Provision was added to specify that the Williamsburg
version 3 protocol may be operated at low speed.

ATTACHMENT 10 – VARIABLES TO BIT-ORIENTED

PROTOCOL

Added new Table 10-7 to support low speed operation of

Williamsburg protocol at low speed. Later modified the
value of the variables.

ATTACHMENT 11A – DESTINATION CODES

The assignment of ‘T” for the transponder was deleted. Six
new entries, HFDR Right, TAWS, CVR Inmarsat, ICO, and
Globalstar satellite link identifiers were added as destination
codes. The format and content of the table was aligned with
the corresponding Table 3-1 of Attachment 3 to ARINC
Specification 619 to improve consistency.
APPENDIX A – J
These appendices were formerly identified as Appendix 1 –
10. During the regeneration of Specification Description
Language (SDL) diagrams in Appendix I, references to
Section 1.3.7 were revised to Section 2.5.19.
APPENDIX K

New Appendix added.