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 Specification 429 Adopted by the Airlines Electronic Engineering Committee: Adopted by the Industry: Summary of Document Supplements Supplement Specification 429-1 Specification 429-2 Specification 429-3 Specification 429-4 Specification 429-5 Specification 429-6 Specification 429-7 Specification 429-8 Specification 429-9 Specification 429-10 Specification 429-11 Specification 429-12 Specification 429-13 Specification 429-14 Specification 429-15 Specification 429-16 Adoption Date April 11, 1978 December 6, 1978 August 31, 1979 June 17, 1980 March 12, 1981 December 9, 1981 November 4, 1982 November 4, 1983 October 11, 1984 November 7, 1985 June 15, 1988 October 25, 1989 October 8, 1991 November 4, 1992 April 18, 1995 November 14, 2000 Published June 1, 1978 March 1, 1979 November 1, 1979 August 1, 1980 April 4, 1981 January 22, 1982 January 3, 1983 December 3, 1984 April 30, 1985 November 17, 1986 July 22, 1988 July 1, 1990 December 30, 1991 January 4, 1993 September 1, 1995 September 27, 2001 July 21, 1977 September 15, 1977

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

(2)

ii

ARINC SPECIFICATION 429 TABLE OF CONTENTS ITEM 1.0 1.1 1.2 1.3 1.4 1.4.1 1.4.2 1.4.3 2.0 2.1 2.1.1 2.1.2 2.1.3 2.1.4 2.1.5 2.1.5.1 2.1.5.2 2.1.5.3 2.1.6 2.2 2.2.1 2.2.2 2.2.3 2.2.3.1 2.2.3.2 2.2.4 2.2.4.1 2.2.4.2 2.2.5 2.2.5.1 2.2.5.2 2.2.5.3 2.2.6 2.2.6.1 2.2.6.2 2.3 2.3.1 2.3.1.1 2.3.1.2 2.3.1.3 2.3.1.4 2.3.1.5 2.3.1.5.1 2.3.2 2.3.3 2.3.4 2.4 2.4.1 2.4.1.1 2.4.1.2 2.4.2 2.4.3 2.4.4 2.4.5 3.0 3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.1.4.1 3.1.4.2 SUBJECT INTRODUCTION Purpose of this Document Organization of ARINC Specification 429 Relationship to ARINC Specification 419 “Mark 33 Digital Information Transfer System” Basic Philosophy Numeric Data Transfer ISO Alphabet No. 5 Data Transfer Graphic Data Transfer DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS Message Related Elements Direction of Information Flow Information Element Information Identifier Source/Destination Identifier Sign/Status Matrix BCD Numeric BNR Numeric Data Words Discrete Data Words Data Standards Electrically Related Elements Transmission System Interconnect Modulation Voltage Levels Transmitter Voltage Levels Receiver Voltage Levels Impedance Levels Transmitter Output Impedance Receiver Input Impedance Fault Tolerance Receiver External Fault Voltage Tolerance Transmitter External Fault Voltage Transmitter External Fault Load Tolerance Fault Isolation Receiver Fault Isolation Transmitter Fault Isolation Logic Related Elements Digital Language Numeric Data Discretes Maintenance Data (General Purpose) AIM Data File Data Transfer Bit-Oriented Protocol Determination Transmission Order Data Bit Encoding Logic Error Detection/Correction Timing Related Elements Bit Rate High Speed Operation Low Speed Operation Information Rates Clocking Method Word Synchronization Timing Tolerances MARK 33 DITS APPLICATIONS NOTES Radio Systems Management Word Format and Digital Language Update Rate Sign/Status Matrix Frequency Ranges and Switching Functions ADF DME iii PAGE 1 1 1 1 1 1 1 1 2 2 2 2 2 3 3 4 4 5 5 6 6 6 6 6 7 7 7 7 7 7 8 8 8 8 8 8 8 8 8 8 8 8 9 9 9 9 9 9 9 9 10 10 10 10 11 11 11 11 11 11 11 11

ARINC SPECIFICATION 429 TABLE OF CONTENTS ITEM 3.1.4.3 3.1.4.4 3.1.4.5 3.1.4.6 3.1.4.7 3.2 ATTACHMENTS 1-1 1-2 2 3 4 5 6 7 8 9A 9B 9C 10 11 APPENDICES A B C D E X SUBJECT HF Communications ILS VOR/ILS VHF Communications ATC Transponder AIM Information Transfer PAGE 11 11 11 11 11 12

Label Codes Equipment Codes Data Standards Voltage Levels Input/Output Circuit Standards International Standards Organization Code #5 General Word Formats and Encoding Examples Data Bit Encoding Logic Output Signal Timing Tolerances General Aviation Labels and Data Standards General Aviation Word Examples General Aviation Equipment Identifiers Manufacturer Specific Status Word System Address Labels

13 44 48 76 77 78 79 114 115 116 118 125 126 127

Laboratory Verification of ARINC 429 DITS Electrical Characteristics An Approach to a Hybrid Broadcast-Command/Response Data Bus Architecture Digital Systems Guidance (Part 1) Digital Systems Guidance (Part 2) Guidelines for Label Assignments Chronology & Bibliography

129 162 167 174 179 181

iv

ARINC SPECIFICATION 429, PART 1 - Page 1 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. 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 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 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. c-4 The eight bits will: a. identify the information contained within BNR and BCD numeric data words (e.g., DME distance, static air temperature, etc.) and identify the word application for Discrete, Maintenance and AIM data.

c-2

b.

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.

c-1

c-1

ARINC SPECIFICATION 429, PART 1 - Page 3 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, 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. 10 0 0 1 1 9 0 1 0 1 Installation No. See Note Below 1 2 3 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 excluded) should be coded for “Functional Test”. Pass through data words are those words received by the unit and retransmitted without alteration. When the SSM code is used to transmit status and more 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. 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 multiinstallation 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

c-8

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 4 2.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS 2.1.5 Sign/Status Matrix (cont’d) Failure Warning No Computed Data Functional Test Normal Operation Priority 1 Priority 2 Priority 3 Priority 4 BCD NUMERIC SIGN/STATUS MATRIX Bit No. 31 30 0 0 1 0 0 1 1 1

Meaning Plus, North, East, Right, To, Above No Computed Data Functional Test Minus, South, West, Left, From, Below

Each data word type has its own unique utilization of the SSM field. These various formats are described in the 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. 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. c-12 The sign (plus/minus, north/south, etc.) of BCD Numeric 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. COMMENTARY A typical instruction input to a radio, for example, would be a channel change command word. When this command word is received with the “Functional Test” coding in the SSM field, the radio should exercise its functional test. When the “Functional Test” code appears as a system 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 produce indications of 1/8 of positive full-scale values unless indicated otherwise in the associated ARINC Equipment Characteristic.

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. 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. When it appears 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 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. BNR STATUX MATRIX Bit No. 31 30 0 0 1 0 0 1 1 1 Meaning Failure Warning No Computed Data Functional Test Normal Operation c-12

The sign (plus, minus, north, south, etc.) of BNR Numeric Data words should be encoded in the Sign Matrix field (Bit No. 29) as shown in the table below. Bit No. 29 should be “zero” when no sign is needed.

ARINC SPECIFICATION 429, PART 1 - Page 5 2.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS SIGN MATRIX Bit No. 29 0 1 Meaning Plus, North, East, Right, To, Above Minus, South, West, Left, From, Below 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.

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. 11 0 1 Meaning Nominal Accuracy Degraded Accuracy

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, o Mark the 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 as follows. Consider encoding o o o the angular range 0 to 360 in 1 increments. Per the general encoding rules above, the positive semicircle o o 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 matrix will indicate the positive sign. The negative o o 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

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. 31 30 0 0 1 0 0 1 1 1 Meaning Verified Data, Normal Operation No Computed Data Functional Test Failure Warning

c-3

PART 1 . the resolutions shown are approximate only. 2. on the number or length of stubs for installations on aircraft no larger than those existing.5 volts. See Appendix 1 to this document for a report of this investigation.1. 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. Thus. No restriction is placed by this specification.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) Line A to Line B Line A to Ground Line B to Ground +10 +1.g.3 of this document. Users desire protection against non-annunciated system operation in this mode. which is the maximum signal level under this one-wire fault condition. For convenience. “NULL” and “LO” states. B 747. cannot be changed by the use of more bits in the data field. 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. 2. This is tri-level state modulation consisting of “HI”.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. all binary word ranges in Attachment 2 are shown as whole binary numbers rather than such numbers less one least significant bit value.2.5 0 +0. by reference to the range values and numbers of significant bits for the words of interest.5 LO (V) -10 +1. e. 2. Throughout the negative semicircle. Also. COMMENTARY In practical wire line digital information transmission systems.6 Data Standards (cont’d) COMMENTARY (cont’d) c-3 the result of subtracting each value from 360. once chosen. Also.2.. Accurate resolutions can be determined.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS 2. The shields should be grounded at both ends to an aircraft ground close to the rack connector and at all production breaks in the cable.25 -5 +0. The number of bits in the word affects only the resolution of the data.2. 1 through 4 of the seven-bit-per-character code. therefore.25 +5 +0.5 . It should be noted that in all applications of the twos complement fractional notation.3. Manufacturers building DITS receivers are urged to incorporate this feature in their circuitry whether it is to be used in ARINC 7XX-series equipment or Non-ARINC devices. the sign/status matrix contains the negative sign. This protection may consist of additional circuitry to detect and annunciate the fault.0 c-4 c-5 c-5 c-5 +5 +0.ARINC SPECIFICATION 429.3. 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”.5 0 +0.0 NULL (V) 0 +0.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. Tests have shown that some receivers continue decoding data properly when one side of the transmission line is open or shorted to ground. or to increase the receiver threshold to above 5. noise due to electrical interference perturbs digital signals. When this condition exists noise immunity decreases and intermittent operation may occur. the maximum value of the word. 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. 2. cable characteristics and electrical mismatches can produce distortion of the digital data pulses. if required. o the code for 181 is the twos complement of the code o for 179 .2 Modulation RZ bipolar modulation should be used.Page 6 2. not its range.5 c-4 -5 +0. 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 welldesigned receiver.1. which o includes 180 .3 Voltage Levels 2.

that a future revision of this Specification will include material specifically related to their use. however. to “design in” the rejection capability.2.2 Receiver Input Impedance The receiver should exhibit the following characteristics. or The output impedance of the transmitter is specified as 75 ± 5 ohms to provide an approximate match to the characteristic impedance of the cable. it is desirable that all DITS receivers will discontinue operation when the voltage levels fall into the undefined regions. as new equipment is developed. c-4 c-4 c-4 c-4 c-4 . measured at the receiver input terminals: Differential Input Resistance RI = 12. Twisted shielded wire specifications do not control the characteristic impedance of the cable. 2. 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. Opto-isolator technology is progressing and may soon find application in digital data receivers. PART 1 .5V to -0. 2. The total receiver input resistance including the effects of RI.Page 7 2.5 Fault Tolerance 2. superimposed upon a normally operating bus. or c.4. divided equally between line A and line B to provide an impedance balanced output.2. Respective equipment characteristics should be referenced for desired receiver response in this range.2.000 ohms minimum (400 ohms minimum for twenty receiver loads). stub configuration and the number of receivers connected. the normal ranges of voltages presented to the receiver terminals (A and B) would be: c-5 “HI” +7. characteristic impedances which may be encountered due to the variety of conductor wire gauges and insulation properties.3.5V “LO” -7. This output impedance should be present for the “HI”.1 Transmitter Output Impedance The transmitter output impedance should be 75 ±5 ohms. receivers should associate the following voltage ranges with the three states indicated: c-4 “HI” +6.5. Thus. COMMENTARY The above characteristics apply to differential amplifier receivers. “NULL” and “LO” transmitter output conditions and also during transitions between these levels. However. 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. It is probable. RH and RG in parallel should be 8.2 Receiver Voltage Levels The differential voltage presented at the receiver input terminals will be dependent upon line length.4. In the absence of noise. Manufacturers are urged.2.25V to -11V In practice.5V to 13V “NULL” +2.4 Impedance Levels 2.0V between the NULL and HI and NULL and LO states.2. Receiver manufacturers are encouraged to work with the differential input voltage (line A to line B) and not lineto-ground voltages. The match can only be approximate due to the wide range of b. these nominal voltages will be perturbed by noise and pulse distortion. 2.ARINC SPECIFICATION 429. 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. thus future developments in insulation techniques may result in cables having characteristic impedances outside the range estimated.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS 2.1 Receiver External Fault Voltage Tolerance Receivers should withstand without sustaining damage the following steady-state voltages being applied to their terminals.25V to +11V “NULL” +0. Opto-isolator receivers impose slightly greater loads on data buses than differential amplifier receivers and the way in which they are characterized is different. 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.2. ±29 Vdc applied between terminal B and ground. Operation within specification limits is not required under these conditions. Measurements on a few samples of wire showed a spread of characteristic impedance of 63 to 71 ohms. COMMENTARY a.000 ohms minimum Differential Input Capacitance CI = 50pF maximum Resistance to Ground RH and RG ≥ 12.5V “LO” -6. 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. ±29 Vdc applied between terminal A and ground.5V to -13V COMMENTARY Receiver reaction is currently undefined herein for voltages that fall in the range just above and below the “Null” range.000 ohms Capacitance to Ground CH and CG ≤ 50pF.5V to -2. 30 Vac RMS applied across terminals A and B.

When more than one word is transmitted the lowest octal value label should be used first and the other labels used sequentially until the message has been completed.2 Discretes In addition to handling numeric data as specified above. 5 (see Attachment 5 to this document). (i) BNR expressed in twos complement fractional notation and (ii) BCD per the numerical subset of ISO Alphabet No.3.6. BCD or BNR numeric data but should never contain ISO Alphabet No.2. or b. b and c above. 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. The general purpose maintenance words should be formatted according to the layouts of the corresponding BCD/BNR/discrete data words shown in Attachment 2. from terminal A to ground. Word formats are illustrated in Attachment 6 to this document. without There are two types of discrete words. This definition was used as guidance for the character-oriented file transfer protocol descriptions incorporated into many ARINC equipment characteristics. 2. The protocol defined in Part 3 is preferred for new applications. c. which recommended its inclusion herein as the standard means of file data transfer. or greater than ±29 Vdc between B and ground.5. simultaneously. Attachment 6 shows its against the background of the generalized word structure.2.2. from terminal B to ground. when necessary.2. The original contents of this section are located in Part 3 of this Specification.6. These are general purpose discrete words.3. 2. or d. The lowest octal value label assigned to the maintenance words should be used when only one maintenance word is transmitted. across terminals A and B. c-4 b.3 and Attachment 1). 2. 2.1.1.3 Maintenance Data (General Purpose) c-2 Transmitter External Fault Load Tolerance assigned a label in Attachment 1 is specified in the definition for that word in Attachment 6. 2. PART 1 . 2. Any discrete information contained in a numeric data word c-14 c-13 c-2 . the section header is retained and the original contents of this section are located in Part 3 of this Specification.1. 2. c-4 The general purpose maintenance words are assigned labels in sequential order as are the labels for the general purpose discrete words. the Mark 33 DITS should also be capable of accommodating discrete items of information either in the unused (pad) bits of data words or.3. The process for determining the protocol (characteroriented or bit-oriented) to be used in the interaction c-2 c-12 2. or greater than ±29 Vdc between A and ground.1 Numeric Data The Mark 33 DITS should accommodate numeric data encoded in two digital languages.3. and dedicated discrete words.Page 8 2. The general purpose maintenance words may contain discrete.5. Its viability as a universal protocol was recognized by the Systems Architecture and Interfaces (SAI) Subcommittee. 5 messages.1. These words should be used in ascending label order (starting with 270 XXX) when the system receiving the data can identify its source by reference to the port at which it arrives. 2.3. For reference purposes.4 AIM Data The information previously contained in this section is no longer applicable to ARINC Specification 429. 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). in dedicated words.5 File Data Transfer This section previously described a character-oriented file data transfer protocol.1 Receiver Fault Isolation c-4 Each receiver should incorporate isolation provisions to 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). The purpose of this bit-oriented communications protocol is to provide for the transparent transfer of data files using the ARINC 429 data bus. An information item encoded in both languages will be assigned a unique address for each (see Section 2. or c.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS c-2 2.1 Digital Language 2.1.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.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.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.6 Fault Isolation 2. Seven labels (270 XXX-276 XXX) are assigned to the general purpose words in Attachment 1.2.3 c-4 Transmitters should indefinitely withstand sustaining damage a short circuit applied: a. a voltage greater than 30 Vac RMS between terminal A and B.ARINC SPECIFICATION 429.3.1.

c-5 . NOTE: High bit rate and low bit rate messages will not be intermixed on the same bus.1 High Speed Operation The bit rate for high speed operation of the system should be 100 kilobits per second ±1%. c-13 2.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”. As this process eliminates any obviously wild data points. 32 of each word. 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”. All systems which support the Link Layer bitoriented protocol must be able to respond to the initiation of this process.5. This “reversed label” characteristic is a legacy from past systems in which the octal coding of the label field was. As pointed out in the Commentary following Section 2. of no significance. 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. If the device in question has not responded within T12. may be checked for parity by reference to the binary state of Bit No. the initiating system should initiate another ALO word and again delay up to T12.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS between two units.3. not because a need for it existed for error detection.0 to 14.4.2 Transmission Order The Least Significant Bit (LSB) and Least Significant Character (LSC) of each word should be transmitted first. When a system with a bit-oriented Link Layer protocol has the need to make this determination. The selected rate should be maintained within 1%.4 Error Detection/Correction c-5 The last bit of each word should be encoded such that word parity is rendered odd to allow error detection in receivers.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. the data may be submitted to reasonableness checks. where this information is not predetermined is described in Section 2. Bit symmetry and jitter should be within the tolerances specified in Attachment 8. 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. 2.4. COMMENTARY Although the bit rates specified above should be held within the stated tolerances over the long term. 2. Also. the need for further error detection is questionable.3. individual bit lengths may fall outside the limits expected from these tolerances. The error detection capability specified above may be used as desired in receiving terminals. 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”. Note that the parity calculation encompasses all 31 label and information bits of the word. it should construct the ALO word and transmit this word to the device in question.Page 9 2.2 Low Speed Operation The bit rate for low speed operation of the system should be within the range 12.1. Also.2 of this document.1 Bit Rate 2. 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. This is represented graphically in Attachment 7 to this document. the parity bit was added to the BCD word for reasons related to BCD/BNR transmitter hardware commonality. BCD data intended for human consumption in the cockpit is normally smoothed before transmission to ensure tolerable levels of display jitter.1. Attachment 11C shows the ALO and ALR word formats. PART 1 .5 kilobits per second.1. for example. 2. BCD may be submitted to reasonableness checks.ARINC SPECIFICATION 429.3.19. 2. apparently. or performs a re-initialization for any reason. It is for this reason that no means for error correction are specified in this document. The system should then wait for a maximum period of time defined by T12.4. notwithstanding the RFI performance of the ARINC 429 DITS reported in Appendix 1 to this document.6 kilobits per second for low speed operations and precisely 100 kilobits per second for high speed operations to ensure that the system is not responsible for interference to LORAN C systems with which the aircraft might be equipped.3.5.1. system designers are advised to avoid selection of 13. 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. BNR data.

COMMENTARY RF interference radiated by the Mark 33 DITS using the waveform characteristics specified in this section has been shown not to exceed that permitted by Figure 21-5 of RTCA Document DO-160.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS 2.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. c-5 . Thus. in general.4. Considerations other than human factors demand the time intervals specified.4. too short for the signal to be of use in driving a display device directly.4. Also. PART 1 .5 Timing Tolerances The waveform timing tolerances should be as shown in Attachment 8 to this document. would change too rapidly for human perception. Each and every unique item of information should be transmitted once during an interval bounded in length by the minimum and maximum values specified in Attachment 2. 2. If the signal was so used the least significant character of the display.Page 10 2.2 Information Rates c-4 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. The beginning of the first transmitted bit following this gap signifies the beginning of the new word.4. “Environmental Conditions and Test Procedures for Airborne Electronic/Electrical Equipment and Instruments”. COMMENTARY There are no values given for refresh rates in this Specification.3 Clocking Method Clocking is inherent in the data transmission. Words with like labels but with different SDI codes should be treated as unique items of information.ARINC SPECIFICATION 429. 2. However. a word having the same label and four different SDI codes should appear on the bus four times (once for each SDI code) during that time interval. 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. 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. Stated another way. COMMENTARY The time intervals between successive transmissions of a given BCD word specified in table 1 of Attachment 2 to this document are. it is desirable that data be refreshed at least once per 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. Words dedicated to discretes should be repeated continuously at the rates defined in Attachment 2. Appendix 1 to this document refers. Discretes contained within data words should be transferred at the bit rate and repeated at the update rate of the primary data. conducted RF interference is within the limits specified in Figure 21-2 of DO-160.

4. Altitude Reporting On/Off.5 VOR/ILS Frequency Range: 108. Bit Nos. 10MHz character is limited to 7) VOR/ILS/MLS Frequency.00MHz to 111. 3. 3. Reply Code Ranges: Code increments: No. 0. Pulse Select. 3.05MHz (VOR/ILS only) (100MHz character is 1 for VOR/ILS.01MHz.5kHz 1000kHz.000 MHz to 135. together with the discretes required for function switching for that radio.1 Word Format and Digital Language The standard DITS 32-bit BCD word should be used. 1MHz.1.4. of which Bit Nos.01MHz.001MHz.1MHz. 1kHz 0.4. Reply code selection. 0. is required and it is this that the Mark 33 DITS accommodates).2 DME Frequency Range: (VOR/ILS) Frequency Selection Increment: (VOR/ILS) Characters encoded in DITS word: 108.1. the normal states of the sign/status matrix bits will be binary “zeros”.1.6 VHF Communications Frequency Range: 118. 0.ARINC SPECIFICATION 429. (see Section 2. They should interpret the former as an instruction to perform a functional test or functional test sequence. X-pulse Select (reserved).7 ATC Transponder Note: The ATC Transponder operates on two frequencies (one receive and one transmit) which do not require selection. However. however.4 ILS Frequency Range: 108.4. 3. 10kHz.2 Update Rate Switching Functions: None 3.1. 11 through 29 constitute the data.01MHz.4 Frequency Ranges and Switching Functions 3.0 MARK 33 DITS APPLICATIONS NOTES 3.5kHz on/off. 32 is the word parity bit.01MHz. PART 1 . The following paragraphs set forth the rules which should be followed in the application of the DITS to ensure interchangeability of radios and control sources. ADF/ANT mode selection 3. 30 and 31 form the sign/status matrix and Bit No. Bit Nos. The data field should contain the frequency to which the radio defined by the label field is to tune encoded in BCD characters.1MHz. 0.1. 0.1. 1 through 8 constitute the label.4.Page 11 3. 1MHz. 100kHz.8MHz to 24MHz Frequency Selection Increment: 1kHz or . 9 and 10 are reserved for a source/destination identifier code. BFO on/off. 0.1kHz Characters encoded in DITS words: 10MHz. 3. (100MHz character is always decimal 1) Switching Functions: None 3.1 Radio Systems Management One special application of the Mark 33 DITS is to radio systems frequency selection and function switching.1 ADF Frequency Range: Frequency Selection Increment: Characters encoded in DITS word: Switching Functions: 190kHz to 1750kHz 0. the radios should recognize the codes for “functional test” and “no computed data”. 3. 1MHz.4.5 of this document). IRS/FMC Input Select (reserved). (100MHz character is always decimal 1) Switching Functions: ILS Mode 3.4.00 MHz to 117.3 Sign/Status Matrix Since sign is not a characteristic of radio systems management information.3 HF Communications Frequency Range: 2. Altitude Source Select. They should regard the latter as an instruction to remain tuned to the frequency contained in the last valid word received until either another valid word is decoded or their primary power is removed. 0.1MHz.1kHz.975MHz Frequency Selection Increment: 25kHz Characters encoded in DITS words: 10MHz. 0.1MHz 0.1. 1MHz.00MHz to 135.1. 0-7 in four independent groups 1 decimal digit per group ALL Ident.1. VFR/IFR Select (reserved). of characters encoded in DITS words: Switching Functions: Switching Functions: Display Control . (100MHz character is always decimal 1) The nominal update rate for all radio systems management words should be five times per second.1kHz Switching Functions: USB/LSB mode selection SB/AM mode selection Note: Two words may be transmitted for HF frequency selection to facilitate frequency resolution of 0.1MHz. 1Mhz. 0.95MHz Frequency Selection Increment: 50kHz Characters encoded in DITS words: 10MHz.95MHz Frequency Selection Increment: 50kHz Characters encoded in DITS words: 10MHz.95MHz 50kHz 10Mhz. bit nos. 0. Attachment 6 shows how the word should be structured for each radio system requiring the DITS management service.1. Directed Frequency Numbers.1. 0.1. DME modes.

For reference purposes. . PART 1 .2 AIM Information Transfer The information previously contained in this section is no longer applicable to ARINC Specification 429. the section header is retained and the original contents of this section are located in Part 3.Page 12 3.ARINC SPECIFICATION 429.0 MARK 33 DITS APPLICATIONS NOTES 3.

Latitude Present Position . PART 1 .Page 13 Code No. 6 1 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 X 0 5 6 0 5 6 1 0 0 D D 0 0 3 0 0 3 0 0 0 2 3 4 5 6 0 0 3 4 B 0 0 3 0 0 0 3 0 3 B 1 4 5 A B 2 4 6 A 0 0 2 2 6 A A 2 4 6 A X 2 6 0 2 6 0 5 2 1 0 0 2 4 8 2 4 8 2 4 5 5 8 D 6 0 2 4 8 D 8 4 5 8 2 4 5 8 4 8 8 0 D 5 0 0 0 D D 1 2 2 0 0 D 1 1 0 D D 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 5 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6 0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 7 0 0 0 0 1 1 1 1 1 0 0 1 1 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 8 0 1 1 1 0 0 0 0 1 0 1 0 1 0 0 0 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1 1 0 0 0 1 1 1 1 0 0 0 1 1 1 1 1 0 0 0 0 1 1 1 1 1 1 1 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 1 3 4 5 6 7 0 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X 6-25 6-25 6-25 6-25-1 6-25-1 0 1 1 6-25 0 1 2 6-25 0 1 3 0 1 4 0 1 5 0 1 6 0 1 7 6-25 0 2 0 6-25 6-25 0 2 1 6-25 0 2 2 . (Octal) Eqpt.Longitude Present Position .True Wind Direction .True Total-FLT Deck (LB) Selected Runway Heading Selected Runway Heading Selected Runway Heading Selected Vertical Speed TNK-LD SEL (LB) Landing Gear Position Infor & System Status Selected Vertical Speed Selected EPR Selected N1 Selected EPR Selected N1 Landing Gear Position Infor & System Status Selected EPR Selected N1 Selected Mach QTY-LD SEL (KG) Landing Gear Position Infor & System Status Selected Mach Notes & Cross Ref.Latitude Present Position .True Track Angle .Latitude Present Position . to Tables in Att.Longitude Present Position .True TCAS Mode/Sens Selected Runway .ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429.Longitude Ground Speed Ground Speed Ground Speed Ground Speed Ground Speed QTY-LD SEL (LB) Ground Speed Ground Speed Track Angle .True Track Angle .True QTY-FLT Deck (LB) Control Panel Set Magnetic Heading Magnetic Heading Magnetic Heading Wind Speed Wind Speed Wind Speed Wind Speed Wind Direction . ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL Not Used Distance to Go Distance to Go Distance to Go Time to Go Time to Go Time to Go Time to Station Cross Track Distance Runway Distance to Go Engine Discrete Engine Discrete Spare Present Position .

PART 1 . (Octal) Eqpt. 6 6-25 1 0 0 0 2 0 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 4 6 A 1 2 6 A B 2 4 A 0 2 A 0 1 2 4 5 6 A B 2 2 4 B 2 B 1 2 B 0 1 2 5 5 6 B 0 0 1 2 2 5 6 B 0 0 0 2 2 5 5 6 A 0 2 5 5 6 C 0 B 0 D D 1 1 0 D 1 1 0 D 1 3 0 1 2 1 0 D 6 0 1 1 0 4 D 6 0 8 2 0 2 2 0 0 5 6 0 0 2 6 1 0 5 6 0 0 2 6 9 0 5 5 6 0 9 2 0 5 6 0 7 2 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 6 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 7 1 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 8 1 1 1 1 0 0 0 0 0 1 1 1 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 1 1 0 0 0 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 1 1 0 6-25 0 2 4 6-25 0 2 5 6-25 0 2 6 0 2 7 6-45 0 3 0 0 3 1 6-45 6-46 6-40 6-40 6-40 6-44 0 3 2 0 3 3 Note 2 0 3 4 6-41 6-41 0 3 5 0 3 6 0 0 3 4 7 0 6-42-1 .ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429.Page 14 Code No. ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL Selected Heading QTY-LD SEL (KG) Landing Gear Position Infor & System Status Selected Heading Selected Course #1 Selected Course #1 Landing Gear Position Infor & System Status Selected Course #1 Selected Course #1 Selected Altitude Load SEL Control Selected Altitude Selected Airspeed Selected Airspeed Selected Airspeed TACAN Selected Course Selected Course # 2 Selected Course # 2 Total-FLT Deck (KG) TACAN Selected Course TACAN Selected Course Selected Course # 2 Selected Course # 2 VHF COM Frequency VHF COM Frequency TNK-LD SEL (KG) VHF COM Frequency Beacon Transponder Code Beacon Transponder Code ADF Frequency ADF Frequency ADF Frequency ILS Frequency ILS Frequency ILS Frequency Landing System Mode/Frequency ILS Frequency ILS Frequency ILS Frequency VOR/ILS Frequency Baro Correction (mb) #3 VOR/ILS Frequency VOR/ILS Frequency VOR/ILS Frequency VOR/ILS Frequency VOR/ILS Frequency #1 VOR/ILS Frequency DME Frequency Baro Correction (ins of Hg) #3 DME Frequency DME Frequency DME Frequency Paired DME Frequency DME Frequency DME Frequency #1 DME Frequency MLS Frequency MLS Frequency MLS Channel Selection MLS Frequency Channel MLS Frequency Channel MLS Frequency HF COM Frequency HF COM Frequency Spare X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref. to Tables in Att.

(MSDs) VHF COM Frequency Engine Serial No.Magnetic Body Roll Acceleration Body Yaw Acceleration Zero Fuel Weight (KG) Body Yaw Acceleration Spare Estimated Time of Arrival Wind Direction . PART 1 . (MSDs) Spare Spare Body Pitch Acceleration Longitude Zero Fuel CG Body Pitch Acceleration Body Roll Acceleration Track Angle .Page 15 Code No.ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429. (MSDs) Engine Serial No. (Octal) Eqpt. to Tables in Att. 6 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 5 6 A 0 0 2 5 6 A 0 0 2 5 6 A 0 3 0 3 0 0 2 2 3 B 0 0 2 4 0 6 0 4 2 4 0 6 0 4 2 4 0 6 0 4 4 8 3 3 A B 0 4 3 6 A B 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 7 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 1 1 1 1 1 1 1 1 1 0 0 1 1 1 1 1 1 0 0 0 0 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 8 1 1 1 1 1 1 0 0 0 0 0 0 1 1 1 1 1 1 0 0 1 0 0 0 1 1 1 1 1 1 0 1 0 0 0 1 1 1 0 0 0 1 0 0 0 0 0 1 0 0 0 1 1 1 1 1 1 1 0 4 1 0 4 2 0 4 3 0 0 0 4 4 4 4 5 6 6-15 6-15 6-15 0 4 7 6-16 6-16 6-16 0 0 0 5 5 5 0 1 2 0 5 3 0 0 5 5 4 5 0 3 3 0 0 3 0 3 3 0 0 3 5 6 2 3 3 0 0 2 3 3 5 6 4 7 8 4 5 8 4 7 8 2 5 7 6 0 5 7 C 2 B 5 7 C 6 0 X X X X X X X X X X X X X X X X X X X X X X X X 6-29 6-37 6-36 0 5 6 0 0 5 6 7 0 0 6 1 . (LSDs) VHF COM Frequency VHF COM Frequency Engine Serial No. (LSDs) Engine Serial No. ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL Set Latitude Set Latitude Set Latitude Set Latitude Set Latitude Set Latitude Set Longitude Set Longitude Set Longitude Set Longitude Set Longitude Set Longitude Set Magnetic Heading Set Magnetic Heading Set Magnetic Heading Set Magnetic Heading Set Magnetic Heading Set Magnetic Heading True Heading True Heading Minimum Airspeed Engine Serial No. (LSDs) Engine Serial No.Magnetic Gross Weight (KG) ETA (Active Waypoint) ETA (Active Waypoint) Spare S/G Hardware Part No Tire Loading (Left Body Main) Tire Pressure (Left Inner) ACMS Information Pseudo Range S/G Hardware Part No Tire Loading (Right Body Main) Tire Pressure (Left Outer) ACMS Information ACMS Information X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref.

0) Zero Fuel Weight (lb) Zero Fuel Weight Zero Fuel Weight Zero Fuel Weight X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref.) Engine Oil Quantity Zero Fuel Weight UTC Measure Time Zero Fuel Weight LP Compressor Bleed Position (3. PART 1 . ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL ACMS Information Pseudo Range Fine Tire Loading (Left Wing Main) Tire Pressure (Right Inner) ACMS Information ACMS Information ACMS Information Range Rate Tire Loading (Right Wing Main) Tire Pressure (Right Outer) ACMS Information ACMS Information Delta Range Tire Loading (Nose) Tire Pressure (Nose) Gross Weight SV Position X Gross Weight Longitudinal Center of Gravity SV Position X Fine Longitudinal Center of Gravity Lateral Center of Gravity Reference Airspeed (Vref) SV Position Y AC Frequency (Engine) Hard landing Magnitude #1 Reference Airspeed (Vref) Reference Airspeed (Vref) Brakes . to Tables in Att.Metered Hydraulic Pressure L (Normal) Take-Off Climb Airspeed (V2) SV Position Y Fine AC Frequency (Alt.Metered Hydraulic Pressure L (Alt) VR (Rotation Speed) SV Position Z Stator Vane Angle AC Voltage (Engine) Stator Vane Angle Stator Vane Angle Brakes . (Octal) Eqpt. Sources) VBV Hard Landing Magnitude #2 Brakes .ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429.Metered Hydraulic Pressure R (Normal) V1 (Critical Engine Failure Speed) SV Position Z Fine Oil Quantity Oil Quantity V2 (Critical Engine Failure Speed) Brakes .Metered Hydraulic Pressure R (Alt. 6 6-29 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 3 3 5 6 0 0 3 3 5 6 0 3 3 0 0 3 0 0 3 3 0 0 2 3 5 6 C 0 0 2 3 3 C 0 0 1 2 2 3 C 0 0 1 2 A C D 0 0 2 3 3 5 6 1 2 B 7 C 6 0 2 B 7 C 6 0 B 7 C 3 B 7 2 B 7 7 2 B 9 7 6 0 C 2 B 9 3 7 C 2 B C 9 F 3 C 2 B C 9 2 C 0 2 B C 3 7 6 0 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 6 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 7 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 8 0 0 0 0 0 0 1 1 1 1 1 1 0 0 0 1 1 1 0 0 0 1 0 0 0 0 0 0 0 1 1 1 1 1 1 0 0 0 0 0 0 0 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 6 2 6-29 0 6 3 0 6 4 0 6 5 0 0 6 6 6 7 0 7 0 0 7 1 0 7 2 0 7 3 0 7 4 .Page 16 Code No.

to Tables in Att.ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429. ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL Gross Weight Gross Weight Maximum Hazard Alert Level Output Geodetic Altitude AC Voltage (Alt.PDU Selected Heading HDOP Selected Heading Selected Heading DC Current (TRU) Selected Heading Inboard Flaps . (Octal) Eqpt. PART 1 . Sources) Gross Weight Gross Weight Gross Weight Aircraft Gross Weight Hazard Azimuth Output GNSS Altitude (MSL) AC Voltage (Bus Bar) Longitudinal Center of Gravity Longitudinal Center of Gravity Aircraft Longitudinal Center of Gravity Target Airspeed Hazard Azimuth Output GPS Hor/Vert Deviation AC Load (Engine) Lateral Center of Gravity Target Airspeed Target Airspeed Zero Fuel Center of Gravity Selected Course #1 Selected Course #1 Selected Course #1 Selected Course #1 AC Load (Alt.Page 17 Code No. Source) Gross Weight (Kilogram) Selected Course #1 Selected Course #1 Selected Course #1 Selected Course #1 Outbound Flaps . 6 1 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 2 3 3 1 0 0 2 3 3 1 0 0 0 2 3 5 6 1 0 0 1 2 2 3 5 6 A B B 0 0 2 2 2 A B 1 0 0 2 2 5 6 A 0 0 0 0 1 2 2 5 6 A B 2 3 8 B 9 C 7 E 4 8 B 9 7 E 4 2 8 B 9 7 6 0 4 1 2 1 0 9 7 6 0 1 1 B 2 B 0 5 9 1 B 4 2 B 0 9 6 0 1 1 2 3 B B 0 9 6 0 1 B 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 7 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 8 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 0 7 5 0 7 6 0 7 7 6-27 1 0 0 6-27 1 0 1 6-27 1 0 2 6-27 1 0 3 .PDU C/G Target Selected Altitude VDOP Selected Altitude DC Current (Battery) Selected Altitude Selected Altitude Selected Altitude Selected Airspeed Selected Airspeed Selected Airspeed GNSS Track Angle Left/PDU Flap Selected Airspeed DC Voltage (TRU) Selected Airspeed Selected Airspeed Selected Airspeed Left Outboard Flap Position X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref.

Left Spare Desired Track Brake Temperature (Left Inner L/G) Ambient Pressure Pamb Sensor Desired Track Desired Track Flap Lever Position .Median Value Selected Course #2 Selected Course #2 GNSS Latitude Selected Course #2 Selected Course #2 Selected Course #2 Selected Course #2 Selected Course #2 Flap Lever Position . (Octal) Eqpt. to Tables in Att.Page 18 Code No. 6 6-27 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 1 2 2 2 5 6 A B 0 1 1 2 2 5 5 6 A B B 0 1 2 2 5 6 A B 0 1 3 5 6 B 0 0 0 1 1 2 A B B 0 0 1 0 0 A A B 0 2 2 3 5 6 B C 0 0 3 1 2 B 0 9 B 6 0 1 B 2 0 B 0 9 5 6 0 1 0 B 2 B 0 9 6 0 1 B 2 B 7 6 0 B 1 2 B 0 1 0 1 1 B 1 B D 2 B 1 1 B 2 9 F F 6 0 B C A B A 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 6 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 8 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 1 0 4 1 0 5 6-27 1 0 6 1 0 7 1 1 0 1 1 1 1 1 2 1 1 3 1 1 4 X X X X X X X X X X X 6-27 . ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL Selected Vertical Speed Selected Vertical Speed Right/PDU Flap Selected Vertical Speed DC Voltage (Battery) Selected Vertical Speed Selected Vertical Speed Selected Vertical Speed Selected Vertical Speed Right Outboard Flap Position Selected Runway Heading Selected Runway Heading Left/PDU Slat Selected Runway Heading Oil Temperature Input (IDG/CSD) Selected Runway Heading Selected Runway Heading Selected Runway Heading Selected Runway Heading Selected Runway Heading Left Inboard Flap Position Selected Mach Right/PDU Slat Selected Mach Oil Temperature Input (IDG/CSD) Selected Mach Selected Mach Selected Mach Right Inboard Flap Position Selected Cruise Altitude Flap/Slat Lever Longitude Zero Fuel C/G Selected Cruise Altitude Selected Cruise Altitude Flap Lever Position . PART 1 .Center Test Word A GNSS Longitude Test Word A Runway Length GNSS Ground Speed Selected EPR Selected N1 Flap Lever Position .Right Wheel Torque Output Selected Ambient Static Pressure Selected Ambient Static Pressure Ambient Pressure X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref.ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429.

Page 19 Code No. (Octal) Eqpt. to Tables in Att. ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL Waypoint Bearing Brake Temperature (Left Outer L/G) Fuel Temperature Fuel Temperature Waypoint Bearing Waypoint Bearing Fuel Temperature Wheel Torque Output Cross Track Distance Horizontal GLS Deviation Rectilinear Brake Temperature (Right Inner L/G) Horizontal GLS Deviation Rectilinear Cross Track Distance Cross Track Distance Wheel Torque Output Vertical Deviation Vertical GLS Deviation Rectilinear Brake Temperature (Right Inner L/G) Vertical GLS Deviation Rectilinear Vertical Deviation Vertical Deviation Wheel Torque Output Range to Altitude GNSS Latitude Fine Pack Bypass Turbine Position Range to Altitude Range to Altitude Horizontal Command Signal GNSS Longitude Fine Pitch Limit Pack Outlet Temperature Horizontal Command Signal Horizontal Command Signal Vertical Command Signal Pack Turbine Inlet Temperature Vertical Command Signal Vertical Command Signal Throttle Command Digital Time Mark Universal Time Coordinated (UTC) Universal Time Coordinated (UTC) Universal Time Coordinated (UTC) Universal Time Coordinated (UTC) Universal Time Coordinated (UTC) Vertical Deviation (wide) FWC Word Pack Flow Vertical Deviation (Wide) Vertical Deviation (Wide) Selected Landing Altitude Slat Angle P14 Fan Discharge Static Pressure Fan Discharge Static Pressure Aut Horiz Integ Limit Fan Inlet Total Temperature Fan Inlet Total Temperature Fan Inlet Total Temperature Intruder Range Fan Inlet Total Temperature Selected Total Air Temperature Selected Total Air Temperature Inlet Temperature X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref. 6 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 1 1 1 0 2 2 3 5 6 B C 0 0 2 5 5 6 C 0 0 2 5 5 6 C 0 0 2 5 6 0 0 2 2 5 6 0 2 5 6 0 0 0 0 3 5 6 0 2 2 5 6 0 1 3 0 0 0 1 1 2 3 3 0 0 3 2 9 F F 6 0 C C 2 B 9 5 6 0 C 2 B 9 5 6 0 C 2 B 9 6 0 2 B 5 9 6 0 2 9 6 0 2 B 2 B 1 6 0 2 6 9 6 0 2 B 3 A B B A C F 5 F A B A 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 5 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 6 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 7 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 8 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 1 1 1 1 1 1 1 0 0 0 0 0 1 1 1 1 1 1 0 0 0 0 1 0 1 1 1 1 1 0 0 0 0 0 1 1 1 1 1 0 0 0 0 0 0 0 0 0 1 1 5 6-26 6-27 1 1 6 6-26 6-27 1 1 7 6-26 1 2 0 1 2 1 1 2 2 1 1 2 2 3 4 6-25 6-25 1 2 5 1 2 6 6-11 1 2 7 1 3 0 6-21 .ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429. PART 1 .

PART 1 . ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL Fan Inlet Total Pressure Fan Inlet Total Pressure Fan Inlet Total Pressure Fan Inlet Total Pressure Fan Inlet Total Pressure Intruder Altitude Inlet Pressure Exhaust Gas Total Pressure Exhaust Gas Total Pressure Exhaust Gas Total Pressure Intruder Bearing Aut Horiz Integ Limit Thrust Lever Angle Thrust Lever Angle Thrust Lever Angle Selected Throttle Lever Angle Selected Throttle Lever Angle Power Lever Angle Throttle Lever Angle Throttle Lever Angle Throttle Lever Angle Engine Vibration #1 Engine Fan Vibration ACT 1 Fuel Quantity Display Vertical Figure of Merit Engine Vibration #2 Engine Turbine Vibration ACT 2 Fuel Quantity Display Flap Angle Flap Angle Thrust Reverser Position Feedback Thrust Reverser Position Feedback Center+ACT1+ACT2 FQ Display Selected Thrust Reverser Position Selected Thrust Reverser Position Flap Angle Flight Director .Fast/Slow Flight Director .Roll Precooler Output Temperature Actual Fuel Quantity Display Pump Contactor States Flight Director .Pitch Precooler Input Temperature Preselected Fuel Quantity Display Pump Contactor and Pushbutton States Flight Director . to Tables in Att.ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429.Pitch UTC Fine Fractions Flight Director .Yaw HPA Command Word Center Wing Fuel Quantity Display Pump LP Switch State and FCMC Commands HPA Response Word Altitude Error ACU/BSU Contorl Word Right Wing Fuel Quantity Display Valve Feedback ACU/BSU Contorl Word X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref. (Octal) Eqpt.Fast/Slow Flight Director . 6 1 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 1 1 0 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 1 0 0 0 1 2 0 0 0 1 3 1 1 2 2 3 3 3 1 1 3 3 0 1 2 3 0 0 1 0 0 3 1 2 5 0 1 2 5 1 2 2 3 5 0 0 4 0 0 2 2 5 1 0 0 2 2 5 1 0 0 2 5 1 0 4 5 1 4 2 4 5 1 4 A C D F 3 5 A A C 3 5 B A F F A B C A B A C 9 A B C 9 A B A F F A A B 0 1 B 5 9 A 4 1 B 5 9 A 4 2 3 5 A 4 1 1 A 4 1 B 1 A 4 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 7 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 8 1 1 1 1 1 1 1 0 0 0 0 1 1 1 1 1 1 0 0 0 0 1 1 1 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 1 1 1 1 1 1 0 0 0 0 0 1 1 1 1 1 0 0 0 0 0 1 3 1 6-22 1 3 2 6-23 1 3 3 1 3 4 1 3 5 1 3 6 6-11 6-11 1 3 7 6-11 6-27 1 4 0 6-27 1 4 1 6-27 1 4 2 1 4 3 1 4 4 .Page 20 Code No.Fast/Slow Left Wing Fuel Quantity Display Pump Push Button and LP Switch State Flight Director .Roll UTC Fine Flight Director .

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

ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429. to Tables in Att. PART 1 . (Octal) Eqpt.Page 22 Code No.System Address Label Minimum Descent Altitude (MDA) Target Height Radio Height Radio Height MLS Dataword 7 Radio Height MLS ABS GP Angle Indicated Pump Status X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref. 6 1 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 0 0 1 1 1 0 0 0 0 0 0 0 1 1 1 0 0 0 0 0 0 1 1 1 0 0 0 0 0 0 1 1 0 0 0 1 0 0 0 0 0 0 0 1 1 2 2 3 4 5 B 0 0 1 1 2 3 4 5 B 0 0 1 1 2 2 3 4 5 B 0 0 1 1 2 2 3 4 5 0 0 1 1 2 2 2 5 D 1 4 2 3 5 1 0 0 0 2 2 3 5 1 C 7 9 3 D 5 B A B 4 C 7 3 D 5 B A B 4 C 5 7 3 D 5 B A B 4 C 5 7 3 D 5 A B 4 2 5 7 9 5 E 4 0 7 7 5 4 2 3 7 5 7 B 5 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 5 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 7 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 8 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1 1 0 0 0 0 0 0 0 0 1 5 6 See Attachment 11 1 5 7 1 6 0 1 6 1 1 6 2 1 6 3 See Attachment 11 1 6 4 6-13/6-27 6-13/6-27 . ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL Maintnance Data #7 MLS Dataword 1 Discrete #12 Maintenance Data #7 L Tank Faults MLS Basic Data Wd 1 Maintenance Data #7 Maintenance Data #7 Maintenance Data #7 Refuel Panel Switch States System Address Label for CVR Maintenance Data #8 MLS Dataword 2 Maintenance Data #8 R Tank Faults MLS Basic Data Wd 2 Maintenance Data #8 Maintenance Data #8 Maintenance Data #8 Trim Tank Probe Capacitance Maintenance Data #9 Discrete Status 6 EFIS MLS Dataword 3 Maintenance Data #9 C Tank Faults MLS Basic Data Wd 3 Maintenance Data #9 Maintenance Data #9 Maintenance Data #9 Valve Feedback Maintenance Data #10 Discrete Status 7 EFIS MLS Dataword 4 Maintenance Data #10 A Tank Faults MLS Basic Data Wd 4 Maintenance Data #10 Maintenance Data #10 Indicated Pump Status ADF Bearing ADF Bearing Left/Right MLS Dataword 5 Crew Oxygen Pressure MLS Basic Data Wd 5 Stick Shaker Margin Proportional Signal Indicated Pump Status Density Altitude MLS Dataword 6 Zero Fuel Weight (lb) MLS Basic Data Wd 6 Indicated Pump Status 747 DFDR & A330/340 SSFDR .

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

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

Hg) Static Pressure Corrected (In. Hg) Baro Corrected Altitude #2 Baro Corrected Altitude #2 Baro Corrected Altitude #2 MCDU #1 . mb Impact Pressure N1 Actual (EEC) EPR Actual (EEC) Impacted Pressure. ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL True Airspeed Cargo Compartment Temperature True Airspeed True Airspeed FCMC Com A340-500/600 Total Air Temperature Total Air Temperature Total Air Temperature Total Air Temperature Cargo Duct Temperature Total Air Temperature Total Air Temperature Indicated Total Fan Inlet Temperature Total Fan Inlet Temperature Total Air Temp (TAT) Projected Future Longitude FCMC Mon A340-500/600 Altitude Rate Altitude Rate Altitude Rate Cargo Temp.System Address label (Recipient) Indicated Angle of Attack (Average) Indicated Angle of Attack (Average) Indicated Angle of Attack (Average) Indicated Angle of Attack (Average) Angle of Attach Indicated Average MCDU #2 . Hg) N1 Limit (EEC) EPR Actual (EEC) Static Pressure.Page 25 Code No. 6 6-27 6-27 1 0 2 0 1 0 0 0 0 0 1 0 0 0 0 0 0 0 1 1 1 1 0 0 0 0 0 0 0 0 1 1 0 0 0 0 1 1 X 0 0 0 0 0 0 1 X 0 0 0 0 0 1 0 0 1 0 0 0 1 1 0 2 3 4 0 0 0 1 2 3 A 0 0 4 4 0 0 0 2 3 3 5 6 4 4 0 0 3 8 4 4 X 0 1 2 2 3 A 4 X 0 0 2 2 3 4 0 3 4 0 3 A 2 4 6 9 8 0 2 3 6 A 9 8 D A B 0 2 4 5 6 9 8 B 6 0 0 2 2 6 8 D 0 2 X 6 A 9 9 8 D 0 X 2 6 9 9 8 0 6 8 0 6 8 D C 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 5 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 8 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 0 1 1 1 1 1 1 1 0 1 1 1 1 1 1 0 0 0 0 1 1 1 1 1 1 6-27 2 1 1 6-27 2 1 2 6-27 6-27 6-27 2 1 3 2 1 4 6-39/Note 1 2 1 5 2 1 6 Note 1 2 1 7 2 2 0 See Attachment 11 2 2 1 See Attachment 11 . to Tables in Att. mb Impact Pressure Subsonic ICAO Aircraft Address (Part 2) Geometric Vertical Rate Static Pressure. (Octal) Eqpt. Corrected (In. Reg. Uncorrected. mb Impacted Pressure.ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429. Corrected (In. Valve Position Altitude Rate Altitude Rate Altitude Rate Altitude Rate Altitude Rate Projected Future Longitude Fine FCMC Int A340-500/600 Static Air Temperature Static Air Temperature Static Air Temperature Fuel Used Static Air Temp (SAT) Veritical Time Interval ICAO Aircraft Address (Part 1) Impacted Pressure. Average. PART 1 . Uncorrected.System Address label (Recipient) X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref. Uncorrected.

System Address Label Indicated Angle of Attack (#2 Left) Indicated Angle of Attack (#2 Left) Angle of Attack. Indicated (#2 Left) Printer #2 . to Tables in Att. Indicated (#1 Right) Printer #1 . Indicated (#2 Right) System Address Label for HUD Min. ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL Indicated Angle of Attack (#1 Left) VOR Omnibearing TACAN Bearing Bearing Indicated Angle of Attack (#1 Left) Angle of Attack.System Address Label Indicated Angle of Attack (#1 Right) Indicated Angle of Attack (#1 Right) Angle of Attack. Maneuvering Airspeed Indicated Angle of Attack (#2 Right) Compensated Altitude Rate Minimum Maneuvering Airspeed Minimum Maneuvering Airspeed Indicated Angle of Attack (#2 Right) Angle of Attack. (Octal) Eqpt. Hg) #1 Baro Correction (ins.Page 26 Code No.System Address Label Total Air Temperature Total Air Temperature Inner 2 Tank Probe Capacitance Altitude Rate Altitude Rate Altitude Rate GLS Airport ID Inner 4 Tank Probe Capacitance ACMS Information Static Air Temperature Static Air Temperature ACMS Information ACMS Information Right Outer Probe Capacitance ACMS Information Baro Correction (mb) #1 Baro Correction (mb) #1 ACMS Information ACMS Information System Address Label for EIVMU 1 ACMS Information Baro Correction (ins.System Address Label Min. Op. 6 1 0 0 0 0 0 1 1 1 1 0 1 1 0 1 1 0 0 0 0 0 1 1 0 0 0 0 0 0 0 1 0 0 1 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 1 1 1 2 4 0 2 4 0 2 4 0 0 2 5 6 2 4 0 1 3 5 7 0 3 1 0 3 1 0 0 0 5 1 0 0 3 5 6 1 0 0 3 5 6 0 0 3 5 6 6 1 2 5 C 0 6 C 0 6 C 0 2 6 B 6 0 C 0 2 9 D 3 E 6 8 4 6 8 4 4 5 6 5 4 2 6 8 6 0 4 2 6 8 6 0 2 6 8 6 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 6 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 7 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 8 0 0 0 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 1 1 1 1 0 0 1 1 1 1 0 0 0 0 1 1 1 0 0 0 0 0 1 1 1 1 1 1 0 0 0 0 0 0 1 1 1 1 1 1 6-10 2 2 2 See Attachment 11 2 2 3 See Attachment 11 2 2 4 See Attachment 11 2 2 5 See Attachment 11 See Attachment 11 6-28 2 2 6 2 2 7 2 3 0 6-25 6-25 See Attachment 11 6-25 2 3 1 6-25 2 3 2 2 3 3 6-31 6-25 6-25 6-31 2 3 4 2 3 5 See Attachment 11 6-31 6-25 6-25 See Attachment 11 . Fuel Temp (non-conflicting) Data Loader System Addess Label (High Speed) CFDS Bite Command Summary for HFDR AVM Command CFDS Bite Command Summary for HFDR BITE Command Word True Airspeed True Airspeed Left Outer Probes Capacitance MCDU #4 . Hg) #1 ACMS Information ACMS Information System Address Label for EIVMU 2 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref. PART 1 . Indicated (#1 Left) MCDU #3 .ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429.

Hg) #2 ACMS Information ACMS Information System Address Label for EIVMU 4 Spare Min. Corrected Tank Unit Data System Address Label for APM-MMR Total Pressure Ground Station ID (Word #1) Ground Station ID (Word #1) Ground Station ID (Word #1) Ground Station ID (Word #1) Total Pressure Total Pressure Speed Deviation Total Pressure. mb Total Pressure System Address Label for MMR Zero Fuel Weight (kg) GLS Runway Selection Simulator to Avionics Control Word Ground Station ID (Word #2) Ground Station ID (Word #2) VOR Ground Station Ident Word #2 Ground Station ID (Word #2) Fuel Flow (Engine Direct) Fuel Flow (Wf) Mach Error Fuel Flow Rate Fuel Mass Flow Fuel Mass Flow Angle of Attack. Airspeed for Flap Extension Corrected Angle of Attack Reserved (Special Use) Corrected Angle of Attack FQIS System Data Min. ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL ACMS Information Baro Correction (mb) #2 Baro Correction (mb) #2 ACMS Information ACMS Information System Address Label for EIVMU 3 ACMS Information Baro Correction (ins. 6 6-31 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 1 0 0 0 0 1 0 0 X 0 0 0 0 0 0 0 0 1 1 1 0 0 3 5 6 0 0 0 3 5 6 2 6 8 6 0 2 6 B 8 6 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 4 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 7 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 8 0 0 0 0 0 0 1 1 1 1 1 1 1 0 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 2 3 6 See Attachment 11 2 3 7 See Attachment 11 2 4 0 2 4 1 0 0 2 3 4 5 6 4 6 0 0 1 1 1 1 3 3 A 4 3 5 X 0 1 1 1 1 3 3 8 0 0 4 2 6 C 8 D 6 0 0 0 6 9 0 1 2 A 8 B D 0 7 5 X 9 0 1 2 C 3 B D A B 0 6-35 6-38 See Attachment 11 2 4 2 See Attachment 11 2 4 3 Note 1 2 4 4 See Attachment 11 . to Tables in Att. Uncorrected. (Octal) Eqpt. Normalized System Address Label for ILS X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref.ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429.Page 27 Code No. Hg) #2 Horizontal Uncertainty Level Baro Correction (ins. Airspeed for Flap Extension Min. Airspeed for Flap Extension Angle of Attack. PART 1 .

Uncorrected EPR Error Minimum Airspeed Minimum Airspeed Average Static Pressure mb. (Octal) Eqpt.Page 28 Code No. Uncorrected Static Pressure. Uncorrected System Address Label for MLS General Maximum Speed (VCMAX) Average Static Pressure DME Ground Station Ident Word #1 N1 (Engine Direct) N1 (Engine Direct) Average Static Pressure mb. ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL Minimum Airspeed Minimum Airspeed Minimum Airspeed N3 (Engine) Average Static Pressure mb.ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429. Corrected Angle of Attack Error System address Label for AHRS Control Minimum Speed (VCMIN) DME Ground Station Ident Word #1 Horizontal Figure of Merit Total Fuel Total Fuel Speed Error Total Fuel Control Minimum Speed (VCMIN) Total Fuel Control Minimum Speed (VCMIN) Fuel to Remain Fuel on Board Airspeed Minimum Vmc Continuous N1 Limit Maximum Continuous EPR Limit Preselected Fuel Quantity Indicated Side Slip Angle Preselected Fuel Quantity Indicated Side Slip Angle or AOS Preselected Fuel Quantity Temperature Rate of Change Distance to Go Distance to Go Baro Corrected Altitude #3 Flight Leg Counter Baro Corrected Altitude #3 System Address Label VDR #1 Time to Go Time to Go Baro Corrected Altitude #4 EPR Idle EPR Idle Reference Baro Corrected Altitude #4 EPR Idle Reference Time Until Jettison Complete System Address Label VDR #2 Go-Around N1 Limit Go-Around EPR Limit Corrected Side Slip Angle System Address Label VDR #3 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref. 6 1 0 0 0 0 0 0 0 0 0 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 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 3 3 5 6 A 4 0 0 0 1 2 3 3 0 0 0 1 2 3 4 5 5 6 E 1 4 0 2 2 3 5 A 1 2 0 0 0 1 3 0 0 0 1 2 3 3 E 0 1 3 2 3 A 9 8 B 6 0 D 0 2 6 9 C 9 8 B 2 9 B F C B D 6 A 0 B 4 0 2 B C 8 A D 4 B 1 2 6 A 8 1 2 6 A F 8 F B 2 E 8 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 6 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 7 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 8 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 1 1 1 1 2 4 5 See Attachment 11 2 4 6 See Attachment 11 2 4 7 2 5 0 2 5 1 6-19 See Attachment 11 2 5 2 See Attachment 11 2 5 3 See Attachment 11 . PART 1 . to Tables in Att.

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

Right Outer Cell Documentary Data HP Compressor Inlet Total Pressure HP Compressor Inlet Total Pressure Center Tank Fuel Quantity Minimum Airspeed for Flap Retraction Minimum Airspeed for Flap Retraction ILS Ground Station Ident Word #1 LP Compressor Exit Temperature Fuel Quantity (Tanks) #6 LP Compressor Exit Temperature T/U CAP-L Tank 5-8 Ground Station/Approach Minimum Airspeed For Flap Retraction Minimum Airspeed For Flap Retraction Selected Compressor Inlet Temperature (Total) Selected Compressor Inlet Temperature (Total) Collector Cell 3 and 4 Fuel Quantity Time to Touchdown Minimum Airspeed for Slats Retraction ILS Ground Station Ident Word #2 HP Compressor Exit Pressure Fuel Quantity (Tanks) #7 Burner Pressure HP Compressor Exit Pressure Burner Pressure T/U CAP-L Tank 9-12 Ground Station/Approach Time to Touchdown Time to Touchdown Selected Compressor Discharge Temperature Selected Compressor Discharge Temperature Fuel Quantity (Tanks) #7 Burner Pressure Minimum Buffet Airspeed Integrated Vertical Acceleration Maneuvering Airspeed HP Compressor Exit Temperature (TT4.System Address Label X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref.5) Fuel Quantity (Tanks) #8 HP Compressor Exit Temperature Integrated Vertical Acceleration T/U CAP-L Tank 13-14 Minimum Buffet Airspeed Minimum Buffet Airspeed Selected Compressor Discharge Temperature Selected Compressor Discharge Temperature Inner Tank 3 Fuel Quantity Test Word B Test Word B T/U CAP-C Tank 1-4 Inner Tank 2 Fuel Quantity Cabin Video System . (Octal) Eqpt. PART 1 . ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL Documentary Data Predictive Airspeed Variation LP Compressor Exist Pressure (PT3) Fuel Quantity (Tanks) #5 LP Compressor Exist Pressure T/U CAP-L Tank 1-4 Documentary Data Fuel Quantity .Page 30 Code No.ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429. to Tables in Att. 6 6-14 1 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 1 0 0 1 2 3 4 5 5 6 0 0 1 0 0 1 1 2 3 4 5 5 6 0 0 1 0 0 1 1 2 2 3 3 4 5 5 6 0 0 1 3 0 0 0 1 2 3 3 4 5 6 0 0 1 0 1 4 1 2 A C C 3 D 6 A 0 A B 4 2 A 0 C C 3 D 5 6 0 A B 4 2 A 0 C C F 3 F D 5 6 0 A B 4 A 2 4 A C C 3 8 D 6 0 A B 4 1 D D 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 7 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 8 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 2 6 2 2 6 3 2 6 4 2 6 5 2 6 6 See Attachment 11 .

ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429.Page 31 Code No. ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL Maximum Maneuver Airspeed Predictive Maximum Maneuver Speed Throttle Position Command Spare T/C T/U CAP-C Tank 5-8 Maximum Maneuver Airspeed Maximum Maneuver Airspeed HP Compressor Inlet Temperature (Total) HP Compressor Inlet Temperature (Total) Inner Tank 4 Fuel Quantity Discrete Data #1 Discrete Data #1 Discrete Data #1 Discrete Data #1 Discrete Data #1 Discrete Data #1 Discrete Data #1 Discrete Data #1 Discrete Data #1 Discrete Data #1 MU Output Data Word. Communication Link Status Discrete Data #1 Discrete Data #1 Discrete Data #1 Discrete Data #1 Discrete Data #1 Discrete Data #1 Discrete Data #1 Discrete Data #1 Discrete Data #1 Discrete Data #1 MCDU Normal Discrete Word Discrete Data #1 Discrete Data #1 Discrete Data #1 Discrete Data #1 Discrete Data #1 SDU To ACARS MU/CMU Status Word Discrete Data #1 T/U CAP-C Tank 9 VDR Status Word HFDL Status Word MLS Discrete Status Discretes Output Status Word #1 Discrete Data #1 Intent Status Status Discretes Discrete Data #1 Discrete Data #1 Discrete Data #1 Discrete Data #1 Discrete Data #1 Discrete Data #1 Discrete Data #1 Unusable. (Octal) Eqpt. 6 1 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 0 0 2 3 4 5 6 0 0 1 0 0 0 0 0 0 1 1 1 1 2 2 2 2 2 3 3 3 3 3 3 3 3 3 3 3 3 4 4 4 5 5 5 5 5 5 6 6 6 A A A C 0 0 1 1 4 4 2 A B 3 D 6 0 A B 4 1 2 4 5 6 B A B C E 4 5 7 9 F 0 1 3 5 7 8 9 A B D E F 1 A D 0 3 5 6 8 A 0 0 0 2 8 D 5 A B 4 5 0 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 5 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 6 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 7 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 6 7 2 7 0 . PART 1 . and Empty Warning Stored TACAN Control Word Discrete Data #1 Aircraft Category (Disc Data 1) X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref. to Tables in Att.

(Octal) Eqpt.Page 32 Code No. 6 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 1 1 1 1 2 2 3 3 3 3 3 3 3 3 4 4 5 5 5 6 A A A C 0 0 1 4 4 0 0 0 1 1 1 2 2 2 3 3 3 3 3 4 5 5 5 6 A C 0 0 1 4 2 6 8 A C E 9 F 0 1 3 5 8 A B F 1 D 5 6 A 0 2 8 D 5 A B 4 0 2 1 2 3 8 A C 5 9 F 5 8 A B F D 3 6 A 0 D 5 A B 4 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 5 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 8 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 7 1 2 7 2 . PART 1 . to Tables in Att. ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL Discrete Data #2 Discrete Data #2 Discrete Data #2 Discrete Data #2 Discrete Data #2 Discrete Data #2 Discrete Data #2 Discrete Data #2 Discrete Data #2 Discrete Data #2 Discrete Data #2 Discrete Data #2 Discrete Data #2 Discrete Data #2 Discrete Data #2 Discrete Data #2 SDU To ACARS MU/CMU Join/Leave Message T/U CAP-A Tank 1-4 MMR Discrete Discrete Data #2 Fuel Density Discrete Data #2 Discrete Data #2 Discrete Data #2 Discrete Data #2 Discrete Data #2 Discrete Data #2 Discrete Data #2 Fuel Transfer Indication Discrete Data #2 Altitude Filter Limits (Disc Data 2) Discrete Data #3 Discrete Data #3 Discrete Data #3 Discrete Data #3 Discrete Data #3 Discrete Data #3 Discrete Data #3 Discrete Data #3 Discrete Data #3 Discrete Data #3 Discrete Data #3 Discrete Data #3 Discrete Data #3 Discrete Data #3 T/U CAP-A Tank 5-8 HFDL Slave (Disc Data 2) Discrete Data #3 Fuel Density Discrete Data #3 Discrete Data #3 Discrete Data #3 Discrete Data #3 Discrete Data #3 Fuel Transfer Indication Discrete Data #3 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref.ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429.

Page 33 Code No. 6 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 1 1 2 2 2 3 3 3 3 4 5 5 C 0 0 1 0 0 0 1 1 2 2 2 3 3 3 3 4 5 C 0 0 1 0 0 0 1 1 2 2 2 2 3 3 3 3 4 4 5 5 6 0 0 1 1 3 B 8 C 5 9 F 3 5 B F D 5 A 5 A B 4 1 3 A 8 C 5 9 F 3 5 B F D A 5 A B 4 1 2 3 8 C 5 9 B F 5 8 B F A D A 6 0 A B 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 5 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 7 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 7 3 2 7 4 2 7 5 . PART 1 . to Tables in Att. ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL Discrete Data #4 Discrete Data #4 GNSS Sensor Status Discrete Data #4 Discrete Data #4 Discrete Data #4 Discrete Data #4 Discrete Data #4 Discrete Data #4 Discrete Data #4 Discrete Data #4 Discrete Data #4 T/U CAP-A Tank 9-11 GNSS Status Sensor Valves Left Wing Tank Discrete Data #4 Discrete Data #4 Discrete Data #4 Memos and Status Discrete Data #5 Discrete Data #5 Discrete Data #5 Discrete Data #5 Discrete Data #5 Discrete Data #5 Discrete Data #5 Discrete Data #5 Discrete Data #5 Discrete Data #5 Discrete Data #5 Discrete Data #5 T/U CAP-R Tank 1-4 Sensor Valves Right Wing Tank Discrete Data #5 Discrete Data #5 Discrete Data #5 Fuel Transfer Indications Discrete Data #6 Discrete Data #6 Discrete Data #6 Discrete Data #6 Discrete Data #6 Discrete Data #6 Discrete Data #6 Discrete Data #6 Discrete Data #6 Discrete Data #6 IR Discrete Word #2 Discrete Data #6 Discrete Data #6 T/U CAP-R Tank 5-8 Discrete Data #6 Discrete Data #6 Discrete Data #6 Discrete Data #6 Discrete Data #6 Discrete Data #6 Miscellaneous Warning X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref. (Octal) Eqpt.ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429.

Simulator Use Only General Test Word IRS Maintenance Discrete Discrete Data #8 IR Test T/U CAP-R Tank 13-14 Fuel Transfer and CG Status Application Dependent Application Dependent Application Dependent Internal Parameter for SPATIAAL ECU Internal Temperature ECU Internal Temperature Data Loader Address Label (Low Speed) System Address Label for FMC 1 Application Dependent Application Dependent Application Dependent Application Dependent Internal Parameter for SPATIAAL Application Dependent Demanded Fuel Metering Valve Position Demanded Fuel Metering Valve Position System Address Label for FMC 2 Application Dependent Application Dependent Application Dependent Application Dependent Internal Parameter for SPATIAAL Application Dependent Demanded Variable Stator Vane Position Demanded Variable Stator Vane Position System Address Label for AIDS (DFDAU) Application Dependent Application Dependent Application Dependent Application Dependent Internal Parameter for SPATIAAL Application Dependent Demanded Variable Bleed Valve Position Demanded Variable Bleed Valve Position System Address Label for CFDIU Application Dependent Application Dependent Internal Parameter for SPATIAAL Demanded HPT Clearance Valve Position Demanded HPT Clearance Valve Position System Address Label for ACARS X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref. to Tables in Att.Page 34 Code No. PART 1 .Simulator Use Only TCC to Simulator Control Word .ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429. (Octal) Eqpt. ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL Discrete Data #7 Discrete Data #7 Discrete Data #7 Discrete Status 8 EFIS Discrete Data #7 Discrete Data #7 Discrete Data #7 T/U CAP-R Tank 9-12 Discrete Data #7 Output Status Word #2 Discrete Data #7 Discrete Data #7 Discrete Data #7 Discrete Data #7 FCC to Simulator Control Word .Simulator Use Only FMC to Simulator Control Word . 6 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 X 0 0 0 0 1 0 0 0 0 1 1 T 0 0 0 0 0 0 1 1 0 0 0 0 0 0 1 1 0 0 0 0 0 0 1 1 0 0 0 1 1 0 1 1 2 2 2 3 4 5 5 5 6 B 1 0 0 0 X 0 1 3 4 1 0 1 3 5 0 0 B 0 0 1 5 5 6 0 0 0 0 1 5 5 6 0 0 0 0 1 5 5 6 0 0 0 1 5 0 0 2 8 C 5 9 F F D 6 8 A 0 B 4 1 2 3 X 4 8 8 D 4 1 A D A A B D 1 2 A 6 A 0 A B 1 2 A 6 A 0 A B 1 2 A 6 A 0 A B 1 A A A B 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 7 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 2 7 6 Note 1 2 7 7 3 0 0 See Attachment 11 3 0 1 See Attachment 11 3 0 2 See Attachment 11 3 0 3 See attachment 11 3 0 4 See Attachment 11 .

True Track Angle .Latitude Aileron Position Present Position .Longitude Present Position . to Tables in Att.TANK Present Position Latitude Internal Parameter for SPATIAAL Present Postion Latitude Right Outer Tank Fuel Quantity System Address Label for GPWS Present Position .True Fuel Quantity ACT 2 Track Angle . PART 1 .True Rudder Trim Track Angle .True Track Angle . (Octal) Eqpt.True Track Angle .Latitude COMP CAP . ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL Application Dependent Application Dependent Internal Parameter for SPATIAAL Demanded LPT Clearance Valve Position Demanded LPT Clearance Valve Position System Address Label for Weight/Balance System Application Dependent Application Dependent Internal Parameter for SPATIAAL System Address Label for TCAS Application Dependent Application Dependent Internal Parameter for SPATIAAL System Address Label for Satellite Data Unit (SDI) Present Position .True Additional Center Tank (Act 2) Fuel Quantity System Address Label for GNLU 3 Stabilizer Position Indication (B747-400) True Heading True Heading Elevator Position True Heading Control Wheel Pitch Force Internal Parameter for SPATIAAL Rear Center Tank (RCT) Fuel Quantity System Address Label for GNU 1 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref.Longitude Control Wheel Roll Force Present Postion Longitude Internal Parameter for SPATIAAL Present Position Longitude Right Outer Tank Fuel Quantity System Address Label for GNLU 1 Ground Speed Ground Speed Ground Speed Rudder Position Ground Speed Ground Speed Fuel Quantity ACT 1 Ground Speed Additional Center Tank (Act 1) Fuel Quantity System Address Label for GNLU 2 Track Angle .Latitude Present Position .ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429.Longitude Aileron Trim Present Position .Page 35 Code No. 6 1 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 1 5 0 0 0 1 5 0 1 5 0 0 2 3 4 5 5 6 1 0 0 2 3 3 5 5 6 1 0 0 0 2 3 5 5 6 1 0 0 2 2 3 5 5 6 1 0 0 2 2 3 3 5 1 1 A A A B 1 A A 1 A A 2 4 9 8 D 6 A 0 4 2 4 9 8 B 6 A 0 4 2 4 5 9 8 6 A 0 4 2 4 5 9 8 6 A 0 4 2 4 5 9 8 B A 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 6 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 7 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 8 1 1 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 3 0 5 See Attachment 11 3 0 6 See Attachment 11 3 0 7 See Attachment 11 6-27 3 1 0 See Attachment 11 6-27 3 1 1 See Attachment 11 6-27 3 1 2 See Attachment 11 3 1 3 See Attachment 11 3 1 4 See Attachment 11 .

Magnetic Track Angle .Magnetic Track Angle .Tank Fuel Quantity Act 3 Magnetic Heading Magnetic Heading Drift Angle Drift Angle Drift Angle Engine Fuel Temperature Drift Angle Drift Angle Drift Angle Exhaust gas Temperature (Total) Exhaust gas Temperature (Total) System Address label for Autothrottle Computer Flight Path Angle Flight Path Angle Flight Path Angle Engine Nacelle Temperature Flight Path Angle Flight Path Angle Flight Path Angle Total Compressor Discharge Temperature Total Compressor Discharge Temperature System Address Label for FCC 1 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref.Magnetic Internal Parameter for SPATIAAL Track Angle .Magnetic Oil Pressure (Engine) Magnetic Heading Magnetic Heading Magnetic Heading Engine Fuel Pressure Own Aircraft Magnetic Heading Magnetic Heading Density .Magnetic Track Angle . ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL Stabilizer Position Wind Speed Wind Speed Wind Speed Stabilizer Position Wind Speed Wind Speed Internal Parameter for SPATIAAL Wind Speed Stabilizer Position System Address Label for GNU 2 Wind Direction (True) Wind Angle Oil Temperature (Engine) Wind Angle Wind Direction (True) Internal Parameter for SPATIAAL Wind Direction (True) Engine Oil Temperature Engine Oil Temperature Engine Oil Temperature System Address Label for GNU 3 Track Angle . 6 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 1 1 0 0 0 0 2 3 5 5 6 A 0 0 2 3 5 5 6 D 0 0 0 0 0 2 2 3 5 5 6 D 0 0 2 2 3 3 4 5 5 6 0 0 0 2 3 5 6 0 0 0 0 0 2 3 5 6 0 0 1 2 4 5 9 8 6 A 0 1 2 4 9 8 6 A 0 0 A B 2 4 5 5 9 8 6 A 0 0 4 5 5 9 5 8 D A 6 0 2 4 5 9 8 6 0 A B 2 4 5 9 8 6 0 A B 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 5 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 7 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 8 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 3 1 5 See Attachment 11 3 1 6 See Attachment 11 3 1 7 3 2 0 3 2 1 See Attachment 11 3 2 2 See Attachment 11 . to Tables in Att.Magnetic Track Angle .ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429. (Octal) Eqpt. PART 1 .Magnetic Oil Pressure (Engine) Track Angle .Page 36 Code No.

ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429. 6 1 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 1 1 1 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 0 1 1 0 0 0 0 1 1 0 0 0 0 0 1 1 0 0 0 0 0 1 1 0 0 0 3 5 6 0 0 0 0 2 3 4 5 0 0 1 0 0 1 2 2 3 3 5 0 0 1 0 0 3 4 5 0 0 0 0 3 4 0 0 0 0 2 3 3 0 0 0 0 2 3 3 0 0 2 4 5 8 6 0 A B 4 5 5 8 D A A B 4 4 5 A 5 F 8 F A A B 4 4 5 8 D A A B 4 5 8 D A B 4 5 F 8 F A B 4 5 F 8 F A B 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 6 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 7 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 6-27 3 2 3 See Attachment 11 3 2 4 See Attachment 11 3 2 5 See Attachment 11 3 2 6 See Attachment 11 3 2 7 3 3 0 See Attachment 11 3 3 1 See Attachment 11 . (Octal) Eqpt. to Tables in Att. ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL Geometric Altitude Flight Path Acceleration Flight Path Acceleration Flight Path Acceleration Geometric Altitude Geometric Altitude Variable Stator Vane Position Variable Stator Vane Position System Address Label for FCC 2 Pitch Angle Pitch Angle Pitch Angle Pitch Angle Tank VSO Quantity Effective Pitch Angle Selected Fuel Metering Valve Position Selected Fuel Metering Valve Position Effective Pitch Angle System Address Label for FCC 3 Roll Angle Roll Angle Engine Control Trim Feedback Roll Angle Stator Vane Feedback Roll Angle Stator Vane Feedback Effective Roll Angle Selected Fuel Metering Vane Position Selected Fuel Metering Vane Position Effective Roll Angle System Address Label for APU Body Pitch Rate Body Pitch Rate Body Pitch Rate Uplift Quantity Maintenance Word Compressor Discharge Static Pressure Compressor Discharge Static Pressure System Address Label for APU Controller Body Roll Rate Body Roll Rate Body Roll Rate Uplift Density Fuel Metering Valve Position Fuel Metering Valve Position SAL Mode Control Panel (MCP) Body Yaw Rate Body Yaw Rate HC/TC Cooling Valve Position Feedback Body Yaw Rate HC/TC Cooling Valve Position Feedback Selected HPT Clearance Valve Postion Selected HPT Clearance Valve Postion System Address Label for FMC 3 Body Longitudinal Acceleration Body Longitudinal Acceleration LTC Cooling Valve Position Feedback Body Longitudinal Acceleration LTC Cooling Valve Position Feedback Selected LPT Clearance Valve Position Selected LPT Clearance Valve Position System Address Label for ATC Transponder X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref. PART 1 .Page 37 Code No.

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

System Address Label NDB Effectivity Exhaust Gas Temperature Exhaust Gas Temperature Exhaust Gas Temperature Exhaust Gas Temperature Exhaust Gas Temperature Exhaust Gas Temperature Discretes Status 1&3 EGT Selected Exhaust Gas Temperature (Total) Selected Exhaust Gas Temperature (Total) EGT Trimmed X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref. TLA N2 N2 N2 N2 N2 N2 Fuel Discretes N2 Selected Actual Core Speed Selected Actual Core Speed N2 Speed HF DATA Radio/Data #2 . PART 1 . to Tables in Att.ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429. ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL Target N1 N1 Command EPR Command Grid Heading N1 Command EPR Command N1 Command (Engine) EPR Command (Engine) N1 Command EPR Command Grid Heading EPR Command I/O S/W REV 1&2 Command Fan Speed Command Fan Speed N1 Reference Pressure Ratio (Ps/Pso) N1 Bug Drive N1 Limit EPR Limit N1 Maximum EPR Maximum N1 Limit (TCC) EPR Limit (TOC) Maximum Available EPR N1 Limit EPR Limit Maximum Available EPR S/W Rev-Tank Maximum Allowed Fan Speed Maximum Allowed Fan Speed Air Density Ratio N1 Derate EPR Rate N1 Demand N1 Command vs. 6 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 1 1 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 1 1 2 2 2 2 3 3 4 0 0 3 4 0 0 0 1 1 2 2 2 3 3 3 4 0 0 4 0 0 1 0 0 1 1 2 2 3 3 4 D 0 0 3 0 1 1 2 2 3 3 4 D 0 0 3 2 3 3 4 A A 9 9 F F 8 F D A B A 0 2 3 3 A A 9 9 F B B F D A B 0 3 3 A A B A C 9 F 3 F D 0 A B A 2 A C 9 F 3 F D 0 A B A 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 3 4 1 3 4 2 3 4 3 3 4 4 See Attachment 11 3 4 5 . TLA N1 Command vs.Page 39 Code No. (Octal) Eqpt.

ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL N1 Actual N1 Actual N1 Actual N1 Actual N1 Actual Cable Cap-Hi-Z N1 Selected Actual Fan Speed Selected Actual Fan Speed N1 Speed Actual Antenna Control Fuel Flow (Engine) Sector Control Antenna Control Fuel Flow LPT Clearance Valve Position LPT Clearance Valve Position Fuel Flow Maintenance Data #1 IRS Maintenance Discrete Maintenance Data #1 GPS Test Word (manufacturer specific) Maintenance Data #1 CFDS Bite Fault Summary Word for HFDR Maintenance Data #1 Maintenance Data #1 Maintenance Data #1 MU Output Data Word Failure Status Maintenance Data #1 Maintenance Data #1 Maintenance Data #1 Maintenance Data #1 Maintenance Data #1 Maintenance Data #1 IRS Maintenance Word #1 Maintenance Data #1 Maintenance Data #1 Maintenance Data #1 Maintenance Data #1 Maintenance Data FQIS 1-3 VDR Fault Summary Word CFDS Bite Fault Summary Word for HFDR ILS Maintenance Word Maintenance Word #1 Maintenance Data #1 Maintenance Data #1 Fuel Density Maintenance Data #1 Maintenance Data #1 Maintenance Data #1 Maintenance Data #1 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref. 6 1 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 0 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 2 3 0 1 2 3 3 4 D 0 0 3 1 2 3 3 D 0 0 3 0 0 0 0 1 1 1 1 2 2 2 2 2 2 3 3 3 3 3 3 4 4 5 5 5 5 0 0 1 1 4 4 4 3 A F 3 F D 0 A B A 8 9 0 5 0 A B A 3 4 6 B 8 9 A C 3 4 5 7 9 F 2 5 8 D E F 0 D 0 3 5 8 A B 4 5 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 6 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 7 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 4 6 3 4 7 3 5 0 .Page 40 Code No. PART 1 .ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429. (Octal) Eqpt. to Tables in Att.

(Octal) Eqpt. ACT & RCT Probe Capacitance Maintenance Data #3 Flight Count Maintenance Data #4 Maintenance Data #4 Maintenance Data #4 Maintenance Data #4 IRS Maintenance Word #3 Maintenance Data #4 Maintenance Data #4 Maintenance Data FQIS 1-4 Vibration Maintenance Data #4 Maintenance Data #4 Inner Tank 1 Probe Capacitance Maintenance Data #5 Maintenance Data #5 Maintenance Data #5 Maintenance Data #5 N1 Vibration Maintenance Data #5 FQIS Tank ID Maintenance Data #5 Maintenance Data #5 Maintenance Data #5 Maintenance Data #5 Maintenance Data #5 GNSS Fault Summary MLS Maintenance Data IRS Maintenance Word #4 N2 Vibration Maintenance Data FQIS 2-4 Acknowledgement N3 Vibration Maintenance ISO #5 Message BITE Status Word X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref. ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL Maintenance Data #2 SRU Test Word (manufacturer specific) Maintenance Data #2 Maintenance Data #2 MU Output Data Word Failure Status Maintenance Data #2 Maintenance Data #2 Maintenance Data #2 Maintenance Data #2 Maintenance Data #2 IRS Maintenance Word #2 Maintenance Data #2 Maintenance Data FQIS 1&3 MMR Maintenance Word Maintenance Word #2 Maintenance Data #2 Maintenance Data #2 Inner Tank 1 Probe Capacitance Maintenance Data #2 Maintenance Data #3 Maintenance Data #2 Maintenance Data #2 Maintenance Data #2 Maintenance Data #2 Maintenance Data #2 Maintenance Data FQIS 1-4 MLS Bite Status Maintenance Word Maintenance Data #2 Maintenance Data #2 Center. 6 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 X 0 X Y 0 0 1 1 2 2 2 2 2 3 3 3 4 5 5 0 0 1 4 1 1 2 2 2 3 4 5 5 0 0 1 4 1 1 2 2 3 3 3 4 D 0 0 1 0 1 1 2 3 3 4 5 6 B 0 0 0 2 3 3 4 X 3 X Y 6 B A C 4 5 9 E F 1 8 F D 5 8 A B 4 0 A C 5 E F F D 5 8 A B 4 0 A C 5 F 8 D F D 0 A B 4 2 A C F D F D 6 0 B A B B 7 8 D D X D X Y 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 8 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 0 0 0 3 5 1 3 5 2 3 5 3 3 5 4 3 5 5 X X X X X X X X X X X X 6-3/Note 1 Note 1 6-5/Note 1 3 5 6 .ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429. to Tables in Att. PART 1 .Page 41 Code No.

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

to Tables in Att. (Octal) Eqpt.Magnetic Actual Fan Speed Actual Fan Speed Cabin Terminal #3 .System Address Label East-West Velocity .System Address Label Cross Heading Acceleration Cross Heading Acceleration Spare DC2 Cross Heading Acceleration GPS Differential Correction Word B Equipment Identification Equipment Identification X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Notes & Cross Ref.System Address Label North-South Velocity .Magnetic Left Thrust Reverser Position Left Thrust Reverser Position Cabin Terminal #1 .Page 43 Code No. ID (Hex) Transmission Order Bit Position Data Parameter BNR BCD DISC SAL g g GNSS Height WGS-84 (HAE) Decision Height Selected (EFI) Decision Height Selected (EFI) General Aviation Equipment Identifier Wind Direction . . PART 1 .Magnetic Actual Core Speed Actual Core Speed Cabin Terminal #4 .ATTACHMENT 1-1 LABEL CODES ARINC SPECIFICATION 429.System Address Label Along Heading Acceleration Along Heading Acceleration Spare DC1 Along Heading Acceleration Right Thrust Reverser Position Right Thrust Reverser Position GPS Differential Correction Word A Cabin Terminal #2 . [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. 6 1 0 3 0 7 0 0 0 0 0 0 0 0 0 1 1 0 1 1 0 1 1 0 0 0 0 1 1 X 0 0 0 0 X 0 X 0 0 0 2 C 0 0 0 0 0 0 0 0 0 0 0 0 3 3 0 0 X 0 0 3 3 X 3 X 4 5 B 5 5 0 5 A B 5 A B 5 A B 4 5 3 8 A B X 4 5 3 8 X 0 X 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 5 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 6 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 7 0 0 0 0 0 0 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 8 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 1 1 3 7 1 See Attachment 9B 3 7 2 See Attachment 11 3 7 3 See Attachment 11 3 7 4 See Attachment 11 3 7 5 See Attachment 11 3 7 6 3 7 7 6-17/Note 1 Notes [1] XXX or YYY is applicable to all Equipment IDs.

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

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

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

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

2 Max Transport Delay (msec) 3 Units Notes 0 0 2 Distance to Go 0 5 6 Distance to Go 0 6 0 Distance to Go 002 056 060 115 Time to Go Time to Go Time to Go Time to Station N.1 0.9 0-359.1 0.M.9 0-79900 180N-180S 180N-180S 180N-180S 180E-180W 180E-180W 180E-180W 0-7000 0-7000 0-79999 0-7000 0-7000 0-7000 0-7000 0-7000 0-359.M. Deck (LB) Track Angle .1.9 ±3999.0 1.0 1.9 0-799 0-799 0-799 0-799 0-359 0-359 0-359.9 0-359.1 1.Longitude 0 0 4 Present Position .1 0. Deg Deg Deg Deg Knots Knots Knots Knots Deg Deg Deg Lbs.1 0.M. PART 1 .0 1.Transit Transit Bits Sense lution Interval Interval (msec) 2 (msec) 2 5 5 5 4 4 4 4 4 3 6 6 6 6 6 6 4 4 5 4 4 4 4 4 4 4 5 4 4 4 4 3 3 3 3 3 3 4 5 4 4 4 4 5 4 4 4 4 4 3 N N N E E E 0.Latitude 0 3 8 Present Position .9 0-399.0 0.1 0.9 0-359. Min Min Min Min N.0 1.True 0 3 8 Wind Direction .1 0.Longitude 002 004 04D 005 025 038 056 060 002 004 04D 038 Ground Speed Ground Speed Qty-LD SEL (LB) Ground Speed Ground Speed Ground Speed Ground Speed Ground Speed Track Angle .0 1.9 0-79999 0-359.9 0-359. Knots Knots Knots Knots Knots Deg Deg Lbs.0 1.9 ±3999.1 0.0 0.9 0-359.1 0.1 1.1 0.Longitude 0 3 8 Present Position .1 1.1 1.0 0.1 0.9 0-399.True Qty-Flt.True Track Angle .9 ±6000 0-79999 ±6000 0-3 0-3000 0-3 0-3000 0-3 002 003 004 010 0 0 2 Cross Track Distance 0 0 1 Runway Distance to Go 0 0 2 Present Position .1 1.001 1 0.1 0.9 0-399.Latitude 0 0 4 Present Position .0 1.9 0-399.2 See Section 2.1 0.1 0.1 0.M.0 1.0 1.Latitude 0 0 2 Present Position .Page 48 ATTACHMENT 2 DATA STANDARDS TABLE 1 .9 0-79999 0-359.1 0.1 0.0 1.0 1.001 1 0.0 1.True 011 012 013 014 0 0 4 Magnetic Heading 0 0 5 Magnetic Heading 0 3 8 Magnetic Heading 002 004 005 038 Wind Speed Wind Speed Wind Speed Wind Speed 015 016 0 0 4 Wind Direction .1 100. Deck (LB) Selected Runway Heading Selected Runway Heading Selected Runway Heading 017 167 167 100 100 100 100 100 100 100 333 333 200 200 200 200 200 200 200 020 0 2 0 Selected Vertical Speed 0 4 D Tnk-LD SEL (LB) 0 A 1 Selected Vertical Speed 002 002 020 020 0A1 Selected EPR Selected N1 Selected EPR Selected N1 Selected EPR Up 021 .ARINC SPECIFICATION 429. Ft/Min EPR RPM EPR RPM EPR ±3999. Deg Deg Deg Ft/Min Lbs. Feet Deg:Min Deg:Min Deg:Min Deg:Min Deg:Min Deg:Min Knots Knots Lbs.0 0.BCD DATA Eqpt Label ID (Hex) 001 Parameter Name Range (Scale) Min Max Sig Pos Reso.1 0.0 0. N. N.9 0-399.True 010 04D 055 0A0 0B0 Selected Runway Heading Total-Flt.1.9 0-359.0 1.0 0.0 1.1 0.001 100 100 100 100 100 100 50 100 100 250 250 250 250 250 250 250 250 250 125 250 250 250 250 250 250 250 250 250 250 250 250 250 250 250 167 200 200 200 200 200 200 50 200 200 500 500 500 500 500 500 500 500 500 250 500 500 500 500 500 500 500 500 500 500 500 500 500 500 500 333 See Section 2.

0 1.5 167 167 167 167 167 100 62.0 1.1 035 ins Hg 5 0.BCD DATA Eqpt Label ID (Hex) 0 A 1 Selected N1 022 0 2 0 Selected Mach 0 4 D Qty-LD SEL (KG) 0 A 1 Selected Mach 0 2 0 Selected Heading 0 4 D Qty-Flt Deck (KG) 0 A 1 Selected Heading 011 020 0A1 0B1 Selected Course #1 Selected Course #1 Selected Course #1 Selected Course #1 Parameter Name Range (Scale) Min Max Sig Pos Reso.0 1.0 0.0 1.001 1.Transit Transit Bits Sense lution Interval Interval (msec) 2 (msec) 2 4 4 5 4 3 5 3 3 3 3 3 5 5 3 3 3 3 3 3 5 3 3 3 3 1 0.0 1.0 100 100 100 100 100 167 167 167 167 100 100 100 100 100 167 167 167 167 167 167 167 100 100 5 1.0 1.0 1.0 100 100 100 100 100 100 167 167 167 167 167 167 167 62.0 1.0 1.0 1.0 1.ARINC SPECIFICATION 429.Page 49 ATTACHMENT 2 DATA STANDARDS TABLE 1 .0 1. PART 1 .0 1.001 .001 1.0 1.0 1.0 1.0 1.0 1.0 1.5 100 100 200 200 200 200 200 200 333 333 333 333 333 333 333 125 333 333 333 333 333 200 125 200 200 200 200 200 200 200 333 333 333 333 200 200 200 200 200 333 333 333 333 333 333 333 200 200 Max Transport Delay (msec) 3 Units Notes RPM Mach Kg Mach Deg Kg Deg Deg Deg Deg Deg Feet Feet Knots Knots Knots Deg Deg Deg Kg Deg Deg Deg Deg 0-3000 0-4 0-79999 0-4 0-359 0-79999 0-359 0-359 0-359 0-359 0-359 0-50000 0-50000 30-450 30-450 30-450 0-359 0-359 0-359 0-79999 0-359 0-359 0-359 0-359 See Chapter 3 See Chapter 3 0-79999 See Chapter 3 See Chapter 3 See Chapter 3 See Chapter 3 See Chapter 3 See Chapter 3 See Chapter 3 See Chapter 3 See Chapter 3 See Chapter 3 See Chapter 3 See Chapter 3 See Chapter 3 745-1050 See Chapter 3 See Chapter 3 See Chapter 3 See Chapter 3 See Chapter 3 See Chapter 3 22-31 See Chapter 3 See Chapter 3 023 024 025 0 2 0 Selected Altitude 0 A 1 Selected Altitude 0 0 3 Selected Airspeed 0 2 0 Selected Airspeed 0 A 1 Selected Airspeed 002 011 020 04D 056 060 0A1 0B1 020 024 04D 0B6 TACAN Selected Course Selected Course #2 Selected Course #2 Total-Flt Deck (KG) TACAN Selected Course TACAN Selected Course (BCD) Selected Course #2 Selected Course #2 VHF COM Frequency VHF COM Frequency TNK-LD SEL (KG) VHF COM Frequency 026 027 030 Kg 031 0 2 0 Beacon Transponder Code 0 B 8 Beacon Transponder Code 0 1 2 ADF Frequency 0 2 0 ADF Frequency 0 B 2 ADF Frequency 002 010 020 056 060 0B0 002 006 011 020 056 060 0B0 002 006 009 020 ILS Frequency ILS Frequency ILS Frequency ILS Frequency ILS Frequency ILS Frequency VOR/ILS Frequency Baro Correction (mb) #3 VOR/ILS Frequency VOR/ILS Frequency VOR/ILS Frequency VOR/ILS Frequency #1 VOR/ILS Frequency DME Frequency Baro Correction (ins of Hg) #3 DME Frequency DME Frequency 032 033 034 mb 5 0.

3 % MAC Deg Hr:Min Deg 100 kg Hr:Min Hr:Min 052 053 056 0 3 7 Long. 6 See Att.1 1.Magnetic Gross Weight (Kilograms) ETA (Active Waypoint) ETA (Active Waypoint) .59.05 100 100 100 100 100 3 1 100 100 100 100 100 6 6 6 6 6 6 6 6 6 6 6 6 3 3 3 3 3 3 4 4 4 N N N N N N E E E E E E 0.1 100 250 250 250 100 250 250 200 200 200 200 200 500 500 500 500 500 500 500 500 500 500 500 500 500 500 500 500 500 500 500 500 125 1000 1000 1000 200 200 1000 1000 1000 200 200 500 500 500 200 500 500 See Att.0 0. (LSDs) 020 024 033 10A 10B 0B6 VHF Com Frequency VHF Com Frequency Engine Serial No. Zero Fuel CG 0 0 5 Track Angle-Magnetic 002 005 037 056 060 Estimated Time of Arrival Wind Direction .00 0-359 0-23.0 1.1 0.0 1.59.9 042 043 044 0 0 4 True Heading 0 3 8 True Heading 0 0 3 Minimum Airspeed 0 3 3 Engine Serial No. 6 200 200 200 200 200 Max Transport Delay (msec) 3 Units Notes Paired DME Frequency DME Frequency DME Frequency DME Frequency MLS Frequency MLS Frequency MLS Channel Selection MLS Frequency Channel MLS Frequency Channel MLS Frequency MHz 108-135.1 0.9 0-359 0-19999 0-23.Page 50 ATTACHMENT 2 DATA STANDARDS TABLE 1 .59.1 0.0 1.Transit Transit Bits Sense lution Interval Interval (msec) 2 (msec) 2 4 0. 6 See Att. (LSDs) 1 0 A Engine Serial No.1 0.1 0.0 0. (LSDs) 1 0 B Engine Serial No.1 0.0 1. 3 See Chap.9 0-259. 3 100 100 500 500 500 100 0-100. PART 1 . 6 See Chap. 6 See Att.1 1.0 1.1 0.1 0.BCD DATA Eqpt Label ID (Hex) 055 056 060 0A9 036 002 020 055 056 060 0C7 Parameter Name Range (Scale) Min Max Sig Pos Reso.1 250 250 250 250 250 250 250 250 250 250 250 250 250 250 250 250 250 250 250 250 62.9 See Chapter 3 See Chapter 3 See Chapter 3 See Chapter 3 See Chapter 3 500-600 See Chapter 3 See Chapter 3 See Chapter 3 See Chapter 3 See Chapter 3 037 0 2 0 HF COM Frequency 0 B 9 HF COM Frequency 002 004 020 056 060 0A4 002 004 020 056 060 0A4 002 004 020 056 060 0A4 Set Latitude Set Latitude Set Latitude Set Latitude Set Latitude Set Latitude Set Longitude Set Longitude Set Longitude Set Longitude Set Longitude Set Longitude Set Magnetic Heading Set Magnetic Heading Set Magnetic Heading Set Magnetic Heading Set Magnetic Heading Set Magnetic Heading Deg/Min Deg/Min Deg/Min Deg/Min Deg/Min Deg/Min Deg/Min Deg/Min Deg/Min Deg/Min Deg/Min Deg/Min Deg Deg Deg Deg Deg Deg Deg Deg Knots 041 180N/180S 180N/180S 180N/180S 180N/180S 180N/180S 180N/180S 180E/180W 180E/180W 180E/180W 180E/180W 180E/180W 180E/180W 0-359 0-359 0-359 0-359 0-359 0-359 0-359.1 0.1 0.9 0-359. (MSDs) VHF Com Frequency 045 046 047 See Att. (MSDs) Engine Serial No.0 0.01 1. 6 See Att.1 0.9 5 3 5 3 5 5 5 0.5 500 500 500 See Chap.ARINC SPECIFICATION 429.0 1. (MSDs) Engine Serial No.1 0.1 0.9 0-23.1 0.

01 0.9 0-12000 0-19999 0-100.59.99 0-399.99 0-399.1 0.1 0. Display 0 5 A Preselect Fuel Quan.9 0-299.1 0.1 0.0 0.1 1.01 0.1 0.1 0.01 0.BCD DATA Eqpt Label ID (Hex) 060 061 062 063 064 065 Parameter Name Range (Scale) Min Max Sig Pos Reso.01 0.0 0.01 100 100 100 100 100 100 200 200 200 200 200 200 100 25 100 100 100 100 100 100 83.1 0.3 190 50 200 200 200 200 200 200 200 200 167 210 50 200 201 0 0 9 DME Distance 1 1 2 TACAN Distance 1 1 5 DME Distance .00 0-100.0 1. Feet Feet Feet Deg Deg Deg Deg N.1 0.9 ±7000 ±7000 ±180 ±180 ±180 ±180 -1-399.1 0.9 0-299. N. N. 0-9999 0-9999 0-9999 0-9999 0-9999 0-359. Display 0 5 A Right Wing Fuel Quan. PART 1 .9 0-400 0-19999 ±7999.00 0-23.0 0.9 0-23.M.1 1.Transit Transit Bits Sense lution Interval Interval (msec) 2 (msec) 2 4 4 4 4 4 5 5 5 5 5 4 5 5 4 4 4 4 4 0.M. Display 0 2 7 MLS Selected GP Angle 1 1 4 Trim Tank Probe Capacitance 0 3 7 Zero Fuel Weight (lb) 0 0 7 Radio Height 0 2 5 Decision Height Selected (EFI) 0 C 5 Decision Height Selected (EFI) 002 004 056 060 Drift Angle Drift Angle Drift Angle Drift Angle Kg/Lb Kg/Lb Kg/Lb Kg/Lb Kg/Lb Deg pf Lbs.M.9 23:59.59.0 1. Display 0 5 A ACT 2 Fuel Quan.01 0.9 0-23.9 0-299.Page 51 ATTACHMENT 2 DATA STANDARDS TABLE 1 . Display 0 5 A Center+Act1+Act2 FQ Display Kg/Lb Kg/Lb Kg/Lb 140 141 142 143 144 155 157 163 165 170 0 5 A Actual Fuel Quan.1 100 100 100 100 100 100 100 100 100 100 500 100 100 100 200 100 100 100 100 100 100 200 200 200 200 200 200 200 1000 200 200 200 1200 200 200 200 200 200 200 Max Transport Delay (msec) 3 Units Notes 0 3 7 Tire Loading (Left Body Main) 0 3 7 Tire Loading (Right Body Main) 0 3 7 Tire Loading (Left Wing Main) 0 3 7 Tire Loading (Right Wing Main) 0 3 7 Tire Loading (Nose) 0 0 3 Gross Weight 0 3 7 Gross Weight 0 0 2 Longitudinal Center of Gravity 0 3 7 Longitudinal Center of Gravity 0 3 7 Lateral Center of Gravity 0 0 2 Universal Coordinate Time 0 0 B UTC % % % % % 100 lb.1 0.1 Min 0.1 0.ARINC SPECIFICATION 429. 100 lb.59.59. Display 0 5 A Left Wing Fuel Quan.00 0-100.1 0.9 0-23.1 1. % MAC % MAC % MAC Hr-Min Hr:Min 0-299.9 0-299.9 0-9999 0-9999 0-9999 066 067 125 0 3 1 Universal Coordinate Time Hr:Min 0 5 6 Universal Coordinate Time Hr-Min 0 6 0 Universal Coordinated Time (UTC) Hr-Min 135 136 137 0 5 A ACT 1 Fuel Quan.99 4 4 4 4 4 4 14 5 5 4 4 4 4 4 4 5 5 5 100 100 100 100 100 0. Display 0 5 A Center Wing Fuel Quan.

0 10.0 0.5 62.1 0.5 100 500 125 125 125 125 125 125 125 125 200 1000 200 1000 1000 1000 1000 1000 1000 1000 200 235 236 237 243 260 dd:mm:yr 15 4 100 500 500 500 261 0-9999 0-9999 0-9999 0-9999 0-9999 0-100 0-100 0-100 4 4 4 4 16 13 13 13 1.1 500 500 500 500 100 200 100 100 272 273 274 275 345 350 351 352 353 0 5 A Fuel Density 0 5 A Sensor Values Left Wing Tank 0 5 A Sensor Values Center Wing Tank 0 5 A Sensor Values Right Wing Tank 0 0 2 NDB Effectivity 1 1 4 Fuel Density 1 1 4 Inner Tank 1 Probe Capacitance 1 1 4 Center. 1 1 4 Inner Tank 3 Probe Capacitance 200 200 1000 See Attachment 6 kg/l pf pf pf 0-.0 1.1 0.5 62.1 0. ACT &RCT Probe Capac.3 31.5 62.01 0.5 62.0 250 250 250 250 500 500 500 500 230 231 232 31.001 0.0 1.001 0.5 62.1 10.5 62. pF pF pF 100-599 100-599 -060-+099 -060-+099 0-400 ±20000 ±20000 ±20000 0-400 -099-+060 -099-+060 0-400 745-1050 745-1050 22-31 22-31 745-1050 745-1050 22-31 22-31 0-19999 3 3 3 3 14 4 4 4 14 3 3 14 5 5 5 5 5 5 5 5 5 Up Up Up 1.5 233 0 0 6 Static Air Temperature 0 3 8 Static Air Temperature 1 1 4 Right Outer Probe Capacitance 0 0 6 Baro Correction (mb) #1 0 3 8 Baro Correction (mb) #1 0 0 6 Baro Correction (ins of Hg) #1 0 3 8 Baro Correction (ins of Hg) #1 0 0 6 Baro Correction (mb) #2 0 3 8 Baro Correction (mb) #2 0 0 6 Baro Correction (ins of Hg) #2 0 3 8 Baro Correction (ins of Hg) #2 0 3 7 Zero Fuel Weight (kg) 002 00B 031 056 060 0A2 002 0A2 056 060 Date/Flight Leg Date Date (No Flight Leg) Date/Flight Leg Date/Flight Leg Date/Flight Leg Flight Number Flight Number Flight Number Flight Number 250 250 500 500 234 62.1 0.BCD DATA Max Transport Delay (msec) 3 Eqpt Label ID (Hex) 205 Parameter Name Units Range (Scale) Sig Pos Bits Sens e Resolution Max Min Transit Transit Interval Interval (msec) 2 (msec) 2 Notes See Figure 3-1 See Figure 3-1 0 0 2 HF COM Freq (New Format) 0 B 9 HF COM Freq (New Format) 0 0 6 True Airspeed 0 3 8 True Airspeed 0 0 6 Total Air Temperature 0 3 8 Total Air Temperature 1 1 4 Inner 2 Tank Probe Capacitance 004 005 006 114 Altitude Rate Altitude Rate Altitude Rate Inner 4 Tank Probe Capacitance Knots Knots Deg C Deg C pf Ft/Min Ft/Min Ft/Min pf Deg C Deg C pf mb mb ins Hg ins Hg mb mb ins Hg ins Hg Kg N/A dd:mo:yr N/A N/A N/A N/A N/A N/A N/A N/A Kg/cu.0 1.0 1.1 0.0001 100 0.1 0.3 31.999 0-400 0-400 0-400 4 14 14 14 0.0 1. PART 1 .0 0.0 10.1 1.1 0.001 1.0 1.3 62.ARINC SPECIFICATION 429.1 0.001 0.5 62.m.5 62.5 62.Page 52 ATTACHMENT 2 DATA STANDARDS TABLE 1 .0 0.0 1.0 0.1 .

ARINC SPECIFICATION 429.BCD DATA Eqpt Label ID (Hex) 377 Parameter Name Range (Scale) Sig Pos Bits Sens e Resolution Min Max Transit Transit Interval Interval (msec) 2 (msec) 2 1000 1000 Max Transport Delay (msec) 3 Units Notes 0 3 0 Equipment Identification X X X Equipment Identification See Attachment 6 See Attachment 6 .Page 53 ATTACHMENT 2 DATA STANDARDS TABLE 1 . PART 1 .

125 1.BNR DATA Eqpt Label ID (Hex) Min Transit Interval (msec) 2 Max Transit Interval (msec) 2 Max Transport Delay (msec) 3 Parameter Name Units Range (Scale) Sig Pos Resolution Bits Sense Notes 005 025 034 035 052 0 D 0 Engine Discrete 0 4 D Load SEL Control 0 2 5 VOR/ILS Frequency 0 2 5 DME Frequency 0 0 4 Body Pitch Acceleration 0 3 8 Body Pitch Acceleration 0 0 4 Body Roll Acceleration 0 3 8 Body Roll Acceleration 0 0 4 Body Yaw Acceleration 0 3 7 Zero Fuel Weight (Kg) 0 3 8 Body Yaw Acceleration 0 2 5 S/G Software Part Number 0 3 C Tire Pressure (Left Outer) 002 00B 025 03C 056 060 002 00B 03C 056 060 002 00B 03C 056 060 ACMS Information Pseudo Range S/G Hardware Part Number Tire Pressure (Left Inner) ACMS Information ACMS Information ACMS Information Pseudo Rang Fine Tire Pressure (Right Inner) ACMS Information ACMS Information ACMS Information Range Rate Tire Pressure (Right Outer) ACMS Information ACMS Information Deg/Sec2 Deg/Sec2 Deg/Sec2 Deg/Sec2 Deg/Sec2 Kg Deg/Sec2 ± 64 ± 64 ± 64 ± 64 ± 64 655360 ± 64 15 15 15 15 15 15 15 0.25 0.25 0.0039 1.ARINC SPECIFICATION 429.L (alt. A/ Bit 12-Chan.0 64 0. B 053 054 060 PSIA 1024 ± 268435456 1024 10 1.Metered Hyd.002 0.0039 1.0039 0.0 50 250 See Attachment 6 See Attachment 6 See Attachment 6 061 Meters PSIA 20 10 256 1. Knots Knots PSIG Knots Meters Hz Deg Lbs.25 0.002 NA 204700 11 100 125 125 50 Hz 50 Hz 50 Hz 50 Hz 50 Hz 100 50 Hz 250 250 117 Hz 117 Hz 117 Hz 117 Hz 117 Hz 200 117 Hz Bit 11-Chan. PART 1 . PSIG ± 4096 1024 ±67108864 64 512 ±67108864 512 512 512 4096 512 64 512 64 4096 20 10 20 14 11 20 11 12 11 11 12 11 14 11 12 12 12 0.Pres.25 64 . L 0CC (Normal) 002 00B 029 033 037 0CC Take-Off Climb Airspeed (V2) SV Position Y Fine AC Frequency (Engine) VBV Hard Landing Magnitude #2 Brakes-Metered Hyd.) 002 00B 029 037 056 060 Meters PSIA Meters Meters Knots Meters Hz Lbs.0 200 50 1200 250 063 M/S PSIA ± 4096 1024 20 10 0.002 0.002 0. Pres.0 200 50 1200 250 See Attachment 6 See Attachment 6 See Attachment 6 See Attachment 6 See Attachment 6 See Attachment 6 See Attachment 6 See Attachment 6 See Attachment 6 See Attachment 6 062 Meters PSIA 256 1024 11 10 0.0 200 50 1200 250 See Attachment 6 See Attachment 6 See Attachment 6 064 0 0 B Delta Range 0 3 C Tire Pressure (Nose) 0 0 B SV Position X 0 0 B SV Position X Fine Reference Airspeed (Vref) SV Position X AC Frequency (Engine) Hard Landing Magnitude #1 Reference Airspeed (Vref) Reference Airspeed (Vref) Brakes .002 20 0.002 0.0039 0.25 0.Page 54 ATTACHMENT 2 DATA STANDARDS TABLE 2 .016 1 200 50 200 200 500 200 100 100 500 500 50 500 200 100 150 100 50 1200 250 1200 1200 1000 1200 200 200 1000 1000 100 1000 1200 200 250 200 100 50 1000 See Attachment 6 065 066 070 1000 1000 #1 & 2 coded in SDI 071 #1 & 2 coded in SDI .25 1 0.

Lbs.01 0.25 1 0.25 0. Sources) Gross Weight Gross Weight Gross Weight Aircraft Gross Weight Knots Meters Deg/180 Volts Deg/180 Deg PSIG Knots Meters cc US Pint Knots PSIG US Pint Lbs.072 512 512 163.01% 0.84% ±180 ±180 ±180 ±180 128 ±180 ±180 655360 ±180 ±180 ±180 11 20 11 10 11 12 12 11 14 8 9 11 12 9 15 20 15 10 15 15 15 15 15 15 17 10 15 15 15 15 17 20 10 14 14 14 17 11 8 8 17 11 11 14 12 12 12 12 8 12 12 15 12 12 12 0.01% 0.8 1.Pres.0 0. Lbs. Lbs.Ellipsoid GNSS Altitude (Msl) AC Voltage (Bus Bar) Longitudinal Center of Gravity Longitudinal Center of Gravity Aircraft Longitudinal Center of 114 Gravity Lateral Center of Gravity Target Airspeed GPS Hor/Vert Deviation AC Load (Engine) Lateral Center of Gravity Target Airspeed Target Airspeed Zero Fuel Center of Gravity Selected Course #1 Selected Course #1 Selected Course #1 Sleected Course #1 AC Load (Alt. Lbs.001 0.Page 55 ATTACHMENT 2 DATA STANDARDS TABLE 2 .1 0.05 0.0 0.25 64 0.Pres.016 1 0.05 20 0.25 0.05 0. Feet Feet Volts % MAC % Percent MLb-in Knots % F.536743µs 40 0.004 40 40 40 40 40 40 1. Lbs.25 0.05 0.25 40 9.25 0.25 0.05 0.25 40 40 40 40 1. Lbs.S. Seconds Lbs.84 164 163. Inches Lbs.PDU 077 0-002 00B 029 037 056 060 114 001 002 011 020 029 056 060 037 0A1 0B1 0BB Revised by Supp 11 100 .25 0.) Engine Oil Quantity Zero Fuel Weight UTC Measure Time Zero Fuel Weight LP Compressor Bleed Pos.05 0.0039 128 0. PART 1 .0 0.ARINC SPECIFICATION 429. Source) Selected Course #1 Selected Course #1 Gross Weight (Kilogram) Selected Course #1 Selected Course #1 Outboard Flaps .0 1310720 4 1310720 1310720 1310720 1310720 1310720 1310720 131072 256 1310720 1310720 1310720 1310720 131072 ±131072 256 163.R (normal) V1 (critical engine failure speed) SV Position Z Fine Oil Quantity Oil Quantity V2 (critical engine failure speed) Brakes-Metered Hyd.25 0.01 0.05 1.BNR DATA Eqpt Label ID (Hex) Min Transit Interval (msec) 2 500 200 100 100 100 150 50 100 200 100 100 100 50 Max Transit Interval (msec) 2 1000 1200 200 200 200 250 100 200 1200 200 200 200 100 Max Transport Delay (msec) 3 Parameter Name Units Range (Scale) Sig Pos Resolution Bits Sense Notes 072 002 00B 01C 029 02F 033 0CC 002 00B 01C 029 0A2 0CC 0D0 002 00B 02C 033 037 056 060 114 002 003 00B 029 02C 037 03E 114 00B 00B 029 037 03E Rotation Speed (VR) SV Position Z Stator Vane Angle AC Voltage (Engine) Stator Vane Angle Stator Vane Angle Brakes-Metered Hyd. Lbs. (3.01 0.05 0.05 1000 Revised by Supp 11 See Note [4] #1 &2 coded in SDI 073 #1 & 2 coded in SDI SDI 1=L/SDI 2=R 1000 074 500 200 100 100 100 500 500 100 100 100 500 100 100 100 100 100 25 200 100 100 100 100 100 100 25 100 100 100 100 100 167 167 167 167 100 167 167 100 167 167 20 1000 1200 400 200 200 1000 1000 400 200 200 1000 200 200 200 200 400 50 1200 200 200 200 200 200 200 50 200 200 200 200 200 333 333 333 333 200 333 333 200 333 333 100 See Note [5] 1000 1000 075 076 GPS Height Above Ref.125 0. Lbs. % % MAC Knots Knots Percent Deg/180 Deg/180 Deg/180 Deg/180 % Deg/180 Deg/180 Kilograms Deg/180 Deg/180 Deg/180 512 ±67108864 ±180 256 ±180 64 4096 512 64 32768 128 512 4096 128 1310720 10. Feet Volts Lbs.0) Zero Fuel Weight (lb) Zero Fuel Weight Zero Fuel Weight Zero Fuel Weight Gross Weight Gross Weight Geodetic Altitude AC Voltage (Alt.1 0.84% 128 512 128 256 131.R (alt.0 0.

ARINC SPECIFICATION 429.5 1200 62.3 31.05 0.3 20 100 100 100 Max Transit Interval (msec) 2 62.031 1. Input (IDG/CSD) Selected Runway Heading Selected Runway Heading Selected Runway Heading Selected Runway Heading Selected Runway Heading Left Inboard Flap Position Selected Mach Right/PDU Slat Selected Mach Oil Temp.000687 Notes Deg/180 N/A Deg/180 Deg/180 Amperes Deg/180 Deg/180 % Feet N/A Feet Amperes Feet Feet Feet Knots Knots Knots Deg Deg/180 Knots Volts Knots Knots Knots Deg/180 Ft/Min Ft/Min Deg/180 Ft/Min Volts Ft/Min Ft/Min Ft/Min Ft/Min Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 Deg C Deg Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 Mach Deg/180 Mach Deg C Mach Mach Mach Deg/180 Feet Deg/180 Deg/180 102 103 104 105 106 107 0 0 2 Selected Cruise Altitude 0 1 B Flap/Slat Lever 0 B B Flap Lever Position-median value .1 0.05 0.25 1 16 16 16 0.25 0. Input (IDG/CSD) Selected Mach Selected Mach Selected Mach Right Inboard Flap Position Units Range (Scale) ±180 1024 ±180 ±180 256 ±180 ±180 164 65536 1024 65536 256 65536 65536 65536 512 512 512 ±108 ±180 512 128 512 512 512 ±180 16384 16384 ±180 16384 128 16384 16384 16384 16384 ±180 ±180 ±180 ±180 ±180 2048 ±180 ±180 ±180 ±180 ±180 ±180 4096 ±180 4096 2048 4096 4096 4096 ±180 65536 ±180 ±180 Sig Pos Resolution Bits Sense 12 15 12 12 8 12 12 8 16 15 16 8 16 16 16 11 11 11 15 18 11 9 11 11 11 12 10 10 18 10 9 14 10 10 10 12 11 11 18 11 12 11 11 11 11 11 12 12 18 12 12 12 12 12 12 16 18 18 UP UP UP UP UP UP UP UP 0.01 1.0 0.3 100 100 100 31.05 0.3 200 31.25 0.25 0.05 1.5 100 200 200 1200 200 200 200 200 200 200 200 200 1200 200 200 200 200 200 200 100 200 200 200 200 200 200 200 200 200 100 333 333 200 333 200 333 333 333 333 100 200 200 200 200 200 200 62.0 1.5 0.0 0.3 125 100 31.000687 0.1 0.5 250 200 62.05 0.1 0.5 1 1 1 0.25 0.25 0.3 20 100 100 200 100 100 100 100 100 100 100 100 200 100 100 100 100 100 100 20 100 100 100 100 100 100 100 100 100 20 167 167 100 167 100 167 167 167 167 20 31.031 0.25 0.000687 0.0 0.000687 16 0.0055 0.05 1 0.BNR DATA Eqpt Label ID (Hex) 101 002 00B 020 025 029 0A1 0BB 114 002 00B 020 029 056 060 0A1 001 002 003 00B 01B 020 029 056 060 0A1 0BB 001 002 01B 020 029 02B 056 060 0A1 0BB 002 010 01B 020 029 055 056 060 0A1 0B0 0BB 002 01B 020 029 056 060 0A1 0BB Min Transit Interval (msec) 2 31.5 100 200 200 200 Max Transport Delay (msec) 3 Parameter Name Selected Heading HDOP Selected Heading Selected Heading DC Current (TRU) Selected Heading Inboard Flaps .1 0.000687 0.0 1.05 0.1 0.000687 0.PDU C/G Target Selected Altitude VDOP Selected Altitude DC Current (Battery) Selected Altitude Selected Altitude Selected Altitude Selected Airspeed Selected Airspeed Selected Airspeed GNSS Track Angle Left/PDU Flap Selected Airspeed DC Voltage (TRU) Selected Airspeed Selected Airspeed Selected Airspeed Left Outboard Flap Position Selected Vertical Speed Selected Vertical Speed Right/PDU Flap Selected Vertical Speed DC Voltage (Battery) Selected Vertical Speed Selected Vertical Speed Selected Vertical Speed Selected Vertical Speed Right Outboard Flap Position Selected Runway Heading Selected Runway Heading Left/PDU Slat Selected Runway Heading Oil Temp.1 0. PART 1 .0 1.Page 56 ATTACHMENT 2 DATA STANDARDS TABLE 2 .25 0.05 1 0.05 16 16 0.5 0.3 31.0 1.25 0.1 0.1 0.

5-20.000172 10 0.5 62./Ft.5 100 50 1200 50 No.000172 512 11 14 11 14 11 11 12 15 11 15 1.3 50 62.3 50 25 200 25 62.3 31.ARINC SPECIFICATION 429.001 1 0. N. 1 to 4 in SDI 116 002 00B 029 055 056 060 0CC Cross Track Distance Horizontal GLS Deviation Rectilinear Brake Temp.05 1 0.000687 4 0.00915 1 .0 4 0.84 65536 65536 ±180 ±180 ±180 ±180 ±180 ±180 ±180 ±180 180 ±180 20480 4096 4 4096 ±180 ±180 2048 32 32 ±180 ±180 ±180 16384 1.3 100 100 100 31. (Left Inner L/G) Ambient Pressure Pamb Sensor Desired Track Desired Track Flap Lever Position .5 100 200 100 62.016 0.M.0625 1 .016 31. 5 to 8 in SDI 115 No.016 0.05 1 4 Notes 0 3 7 Long.M.M.25 0.00915 0. N.25 0.05 0.5 200 200 200 62.05 0.M.000687 0.000172 0. PART 1 .5-20.3 100 31.3 500 50 Max Transit Interval (msec) 2 200 200 200 333 333 1200 333 333 333 333 333 160 1200 500 1200 200 200 160 200 200 200 200 200 200 160 100 500 500 200 62. 9 to 12 in SDI 117 002 00B 029 055 056 060 0CC Vertical Deviation Vertical GLS Deviation Rectilinear Brake Temp.0 32 ±180 2048 512 512 ±180 ±180 256 16384 Sig Pos Resolution Bits Sense 14 16 16 12 12 20 12 12 12 12 12 18 20 11 15 12 12 18 12 11 14 14 12 12 18 12 11 11 14 12 11 11 11 12 12 8 12 0.Left Desired Track Brake Temp. 13 to 16 in SDI 120 0 0 2 Range to Altitude 0 0 B GNSS Latitude Fine 0 5 6 Range to Altitude .Right Wheel Torque Output Selected Ambient Static Pressure Selected Ambient Static Pressure Ambient Pressure Waypoint Bearing Brake Temp.05 1 0. Lb.5 100 200 100 62.5 1000 100 Max Transport Delay (msec) 3 Parameter Name Units Range (Scale) 163.01 1 1 0.3 31. (Right Outer L/G) Vertical GLS Deviation Rectilinear Vertical Deviation Vertical Deviation Wheel Torque Output Feet Feet Deg C Feet Feet Feet Lb.5 100 No.004 4 31.5 62.002 0. Deg N.05 0.38-E-8 o 0. 128 24000 2048 24000 128 128 16384 15 18 11 18 15 15 12 0.05 0.Page 57 ATTACHMENT 2 DATA STANDARDS TABLE 2 . UP UP 111 112 0 0 B GNSS Longitude 002 00B 0A1 0A1 0BB 002 029 02F 03F 056 060 0BB 0CC 10A 10B 13A 002 029 02F 03F 056 060 0BC 0CC Runway Length GNSS Ground Speed Selected EPR Selected N1 Flap Lever Position .05 0.002 0. Zero Fuel Ctr of Gravity 0 5 6 Selected Cruise Altitude 0 6 0 Selected Cruise Altitude 110 001 002 00B 010 011 020 0A1 0B1 0BB Selected Course #2 Selected Course #2 GNSS Latitude Selected Course #2 Selected Course #2 Selected Course #2 Selected Course #2 Selected Course #2 Flap Lever Position .000687 0.016 8.05 0.05 0. (Left Outer L/G) Fuel Temperature Fuel Temperature Waypoint Bearing Waypoint Bearing Fuel Temperature Wheel Torque Output 114 No.05 0. PSIA PSIA PSIA Deg/180 Deg C Deg C Deg C Deg/180 Deg/180 Deg C Lb.004 0.0625 1.5 62.BNR DATA Eqpt Label ID (Hex) Min Transit Interval (msec) 2 100 100 100 167 167 200 167 167 167 167 167 80 200 250 200 100 100 80 100 100 100 100 100 100 80 50 100 100 100 31.002 0.Center % MAC Feet Feet Deg/180 Deg/180 Deg Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 Deg Feet Knots RPM Deg/180 Deg/180 Deg C PSIA PSIA Deg/180 Deg/180 Deg/180 Lb.05 0.0 1.004 .05 0./Ft./Ft.0 . Feet Deg C Feet N.3 31.0 1./Ft.M. (Right Inner L/G) Horizontal GLS Deviation Rectilinear Cross Track Deviation Cross Track Deviation Wheel Torque Output N.3 100 31.125 0. 2048 1024 2048 1024 2048 2048 16384 512 0.

004 0.004 0.M.3 31.05 0.38-E-8 o 0.05 0.3 100 500 500 25 1200 250 50 50 100 100 200 1000 1000 50 See Att.016 0. 6 and ARINC 735 See Att. 6 and ARINC 735 See Att.004 0.0625 0.06 0.002 0.+90 -80 .05 0.004 0.002 100 100 100 100 200 200 200 250 500 Feet Deg/180 Deg/180 Deg/180 Deg Deg Deg/180 Deg Deg Deg/180 32.0 16 128 128 128 Sig Pos Resolution Bits Sense 15 14 11 14 14 14 12 12 12 18 15 15 15 16 12 14 11 11 17 11 11 11 above sel alt above sel alt above sel alt UP 0.06 Notes 0 6 0 Range to Altitude 121 002 00B 025 056 060 Horizontal Command Signal GNSS Longitude Fine Pitch Limit Horizontal Command Signal Horizontal Command Signal N.01 0. Deg/180 Degrees Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 Deg/Sec Feet Feet Feet Feet Deg/180 PSIA PSIA PSIA N.0 1.05 200 100 25 25 31.004 0.088 0.05 0.5 .5 62.2E-4 0.088 0.016 0.3 31.01 8.05 0.3 31. Deg C Deg C Deg C 122 0 0 2 Vertical Command Signal 0 5 6 Vertical Command Signal 0 6 0 Vertical Command Signal 0 0 2 Throttle Command 0 0 2 Vertical Deviation (wide) 0 5 6 Vertical Deviation 0 6 0 Vertical Deviation 123 126 127 002 01B 033 10A 10B 00B 01A 01C 02F Selected Landing Altitude Slat Angle P14 Fan Discharge Static Pressure Fan Discharge Static Pressure Aut Horiz Integ Limit Fan Inlet Total Temperature Fan Inlet Total Temperature Fan Inlet Total Temperature 130 0 3 5 Intruder Range 03F 10A 10B 13A 131 01A 01C 02D 02F 033 Fan Inlet Total Temperature Selected Total Air Temperature Selected Total Air Temperature Inlet Temperature Fan Inlet Total Pressure Fan Inlet Total Pressure Fan Inlet Total Pressure Fan Inlet Total Pressure Fan Inlet Total Pressure 0 3 5 Intruder Altitude 132 13A 01A 01C 033 Inlet Pressure Exhaust Gas Total Pressure Exhaust Gas Total Pressure Exhaust Gas Total Pressure 0 3 5 Intruder Bearing 133 00B 01A 02F 03F 10A 10B 01C 10A 10B 13A Aut Vert Integ Limit Thrust Lever Angle Thrust Lever Angle Thrust Lever Angle Selected Throttle Lever Angle Selected Throttle Lever Angle Power Lever Angle Throttle Lever Angle Throttle Lever Angle Throttle Lever Angle 134 .30.004 0.3 100 100 100 100 100 200 100 100 100 Max Transit Interval (msec) 2 50 100 1200 250 100 100 100 100 100 100 62.ARINC SPECIFICATION 429.004 0.01 0. PART 1 .Page 58 ATTACHMENT 2 DATA STANDARDS TABLE 2 .0 1. 6 and ARINC 735 Max Transport Delay (msec) 3 Parameter Name Units Range (Scale) 512 ±180 0.06 0.0 1.BNR DATA Eqpt Label ID (Hex) Min Transit Interval (msec) 2 25 50 200 125 50 50 500 500 500 50 31.+90 128 32 32 32 32 32 11 10 10 11 13 13 13 13 13 0.5 200 200 200 500 500 1200 200 200 200 500 Deg C Deg C Deg C Deg C PSIA PSIA PSIA PSIA PSIA 128 -80 .05 0.01 0.5 .30.000172 ±180 ±180 ±180 ±180 ±180 ±180 256 32768 32768 32768 65536 ±180 32 1.088 0.0 1 0.125 0.06 0.05 0.088 0.016 1.768 ±180 ±180 ±180 90 90 ±180 ±128 ±128 ±180 18 12 12 12 11 11 12 11 11 12 0.5 62.05 0.004 100 100 100 100 100 100 100 100 100 200 500 500 200 200 200 200 200 200 500 PSIA PSIA PSIA PSIA 32 32 32 32 13 13 13 14 0.125 0.001 1.M.125 0.

1 0.063 0.4 180 180 100 ±23:59:59 220 220 200 See Attachment 6 See Table 6-12 17 1.05 0.02 0.1.3 31.1 0.125 0.+105 180 ±180 1 ±180 ±180 0.Roll 0 0 1 Flight Director .03 0.953674µs 0.Roll 0 0 B UTC Fine 0 2 5 Flight Director .05 0.02 0.768 8 ±180 ±180 128 128 -5 .Fast/Slow 0 0 1 Flight Director .+105 -5 .1 167 333 167 167 333 See ARINC 429P2 333 152 0 2 7 MLS Elevation Deviation 0 4 1 Open Loop Steering 0 5 5 MLS GP Deviation 0 0 2 Maximum Altitude 0 2 7 Flare 0 4 1 Closed Loop Steering 0 5 5 MLS Selected Azimuth mV Feet ± 2400 65536 See ARINC 741 15 16 Above S.BNR DATA Eqpt Label ID (Hex) 135 Min Transit Interval (msec) 2 100 100 200 100 100 100 100 100 62.9536743µs ±180 32 32 32 ±180 Sig Pos Resolution Bits Sense 12 7 18 12 12 12 12 12 11 11 12 12 20 10 12 10 10 12 12 8 12 0.Pitch 0 0 B UTC Fine Fractions 0 2 5 Flight Director .Fast/Slow 0 2 5 Flight Director .1.5 50 200 125 50 200 125 31.05 0.002 1 0.0sec 200 100 1200 200 See Table 6-12 See Table 6-12 See Table 6-12 Hr:Min:S 151 Deg/180 mV Deg/180 Deg/180 ±180 ± 2400 ±180 ±180 11 15 11 11 0.05 0.0732 0.Yaw 0 4 1 HPA Command Word 2 4 1 HPA Response Word 141 142 143 144 0 2 B Altitude Error 0 4 1 ACU/BSU Control Word 3 4 1 ACU/BSU Response Word Feet 8192 14 1. 3. 0.Fast/Slow 0 0 3 Flight Director .05 0.0 25 50 See ARINC 741 See ARINC 741 145 146 147 150 0 0 2 TACAN Control 1 1 2 TACAN Control X X X TACAN Control Word 002 00B 031 056 060 002 027 055 056 05A 060 Universal Coordinated Time UTC Universal Coordinated Time Universal Coordinated Time Universal Coordinated Time Localizer Bearing (True) MLS Azimuth Deviation MLS AZ Deviation Localizer Bearing (True) LB/KG Control Word Localizer Bearing (True) See Sec.L.125 0.953674µs 0. 3.002 0.ARINC SPECIFICATION 429.0732 1 500 1000 100 See ARINC 741 153 Deg 0-359 9 1 .4 See Sec.008 0.008 0.Page 59 ATTACHMENT 2 DATA STANDARDS TABLE 2 .5 62.5 62.3 125 50 Max Transit Interval (msec) 2 200 200 1200 200 200 200 200 200 250 250 200 100 1200 250 100 1200 250 62.063 0. PART 1 .05 Notes 0 1 C Engine Vibration #1 0 2 9 Engine Fan Vibration 0 0 B Vertical Figure of Merit 0 1 C Engine Vibration #2 01B 02A 02F 03F 10A 10B 140 Flap Angle Flap Angle Thrust Reverser Position Feedback Thrust Reverser Position Feedback Selected Thrust Reverser Position Selected Thrust Reverser Position Flap Angle in/sec % FS Feet in/sec Deg/180 Deg/180 % % % % Deg Deg/180 Seconds Deg/180 Deg/180 Seconds Deg/180 Knots Knots Knots Deg/180 136 137 140 0 0 1 Flight Director .03 0.Pitch 0 0 2 Flight Director .5 62.5 250 100 See ARINC 741 See ARINC 741 Above Cmd Alt See Attachment 6 See Attachment 6 Max Transport Delay (msec) 3 Parameter Name Units Range (Scale) 8 128 32.

N.5 250 200 500 1000 1000 50 250 250 SDI-01=left/SDI10=right 164 002 003 007 025 03B 055 Minimum Descent Altitude (MDA) Target Height Radio Height Radio Height Radio Height MLS ABS GP Angle Per ARINC 522A 165 0 0 B Vertical Velocity 0 5 5 MLS ABS Azimuth Angle 0 0 7 RALT Check Point Dev 0 0 B North/South Velocity 002 EPU Estimate Position Uncertainty (ANP) Actual Navigation Perf.M.M.M.ARINC SPECIFICATION 429. Specific Status Word 002 010 025 029 03B 055 0BD 0D0 003 00B 010 029 03B 055 0D0 Localizer Deviation Localizer Deviation Hydraulic Quantity Localizer Deviation Localizer Deviation Hydraulic Quantity Hydraulic Oil Quantity Delayed Flap Approach Speed (DFA) East/West Velocity Glideslope Deviation Hydraulic Pressure Glideslope Deviation Glide Slope Deviation Hydraulic Oil Pressure N.001953 0.25 0. Deg Deg/180 Deg/180 PSI N/A Feet Feet Feet Feet Feet VDC Deg Feet/Min Deg Feet Knots N. PART 1 .5 0.3 125 100 150 500 66.4 128 4 ± 0.3 83.05 1 N/A 2 0. mb Mach % RPM mb Deg.1 ±180 ±180 4096 N/A 1131072 8192 8192 8192 8192 32 ± 41 ± 32768 ± 82 512 ± 4096 0-128 16 9 16 16 9 12 12 12 N/A 16 16 16 16 12 11 15 15 16 10 15 16 0.0 0.125 0. 0-128 0-128 0-128 16 16 16 0.5 0.25 0.0002 0.0001 1 0.008 1 0.3 125 100 250 500 500 25 125 150 62.06 1 0.125 0.0 0. 200 1200 166 * 200 * 167 171 RNP Reduced Navigation Performance 0 5 6 Current RNP 0 6 0 Current RNP X X X Manu.00125 1.06 33. mb Fuel Temperature .01 0.25 0. Deg N. Uncorrected. N.00195 83.M.002 0.5 100 100 125 200 200 176 003 029 038 05A 0AD Economical Mach RPM (APU) Left Static Pressure Uncorrected.Page 60 ATTACHMENT 2 DATA STANDARDS TABLE 2 .5 100 20 100 20 125 200 200 200 200 .6 200 250 SDI 1= A/SDI 2= B 175 0 0 3 Economical Speed 0 2 9 EGT (APU) 0 3 3 Hydraulic Pump Case Drain Temp 62.008 62.125 0.008 0.M.Set to Zero Static Pressure Left.6 250 200 250 1000 SDI 1= A/SDI 2= B 174 100 200 33.00125 0. C mb 4096 256 2048 512 2048 13 9 18 11 18 0.05 0.4 128 128 512 ± 4096 0.M.015 0.0002 1 0.0002 1.0004 1 0. 512 ± 51.0 0.8 4096 4 ± 0. N.M.5 0.3 Max Transit Interval (msec) 2 167 Max Transport Delay (msec) 3 Parameter Name Units Range (Scale) Sig Pos Resolution Bits Sense Notes 154 002 027 055 056 060 Runway Heading (True) MLS Auxiliary Data MLS Max Selectable GP Runway Heading (True) Runway Heading (True N.BNR DATA Eqpt Label ID (Hex) Min Transit Interval (msec) 2 83.3 100 150 200 1200 66.008 0.3 167 167 155 162 0 5 5 MLS Selected Glide Path 0 1 2 ADF Bearing 0 2 5 ADF brg left/right 0 2 9 Crew Oxygen Pressure 0 5 5 MLS Basic Data Word 5 1 4 0 Density Altitude 31.125 0.8 4096 1024 2048 256 12 10 7 11 12 7 9 11 15 12 12 11 12 12 14 11 12 0.008 0.4 0.00195 See Attachment 6 173 DDM DDM % Dots DDM % US Pint Knots Knots DDM PSI Dots DDM PSI Knots Deg C Deg C 0.00195 0.125 2.0001 0.1 512 512 ± 51.

001 0.5 125 31.Set to Zero Deg C Inner Tank 4 Fuel Temp & Advisory 114 Deg C Warning 1 4 0 Mach Rate M/minute 1 4 2 Projected Future Latitude Fine Deg 002 006 018 035 038 05A 10A 10B Energy Management Speed Brakes Altitude (1013.5 200 1000 1000 62.000172 512 131072 131072 131072 131072 512 1.025 1 0.25 0. 0 0 9 DME Distance N.001 2.25 62.096 512 1 1 4.3 500 100 500 62. Feet Feet Feet Feet Deg C PSIA PSIA Deg C Feet Knots Feet Feet Knots Deg C Knots Deg C Feet Mach Mach Mach Deg C Mach Mach Mach Knots Feet Knots 202 203 204 002 006 038 056 05A 060 50 50 205 006 01A 038 05A 10A 10B 140 206 0 0 6 Computed Airspeed 0 1 8 Altitude (Variable Resolution) 0 3 8 Computed Airspeed See Attachment 6 .M.025 1 0.002 0.25 0.5 62.25 1.0 0.3 100 20 100 20 62.3 31.ARINC SPECIFICATION 429.096 4.3 20 20 31.25 0.3 100 125 400 200 167 200 100 200 0 5 A Fuel Temp.007812 0.0 1.002 0.Page 61 ATTACHMENT 2 DATA STANDARDS TABLE 2 .0 0. Left Wing Tank Static Pressure Right.025 31.M.008 0.008 0.E-32 Cir 0.5 100 100 100 62.25 0.25 0.016 1. 0 5 A Fuel Temperature .25 0.025 1.3 100 500 500 125 400 200 62.3 62.5 1000 62.20.0625 31.25 mb) Fuel Tank #6 Temperature Ambient Static Pressure Ambient Static Pressure Trim Tank Fuel Temp & Advisory 114 Warning 1 4 0 Altitude Utility Airspeed Baro Corrected Altitude #1 Baro Corrected Altitude #1 Baro Altitude Fuel Tank #7 Temperature Baro Altitude Right Outer Tank Fuel Temp & 114 Advisory Warning 1 4 0 Baro Corrected Altitude Mach Mach Mach Fuel Tank #8 Temperature Mach Number Mach Number Mach N.00000625 0.0 1.0625 Variable 0.25 500 31.5 .5 150 100 31.000172 0.5 200 200 200 200 0 0 3 Economical Flight Level 0 2 9 Oil Quantity (APU) Right Static Pressure.0 0.5 62.5 62.5 125 125 125 200 500 500 125 125 62.0000625 0.25 0.025 0.5 150 100 83.M. Right Wing Tank Deg C Inner Tank 3 Fuel Temp & Advisory 114 Deg C Warning 1 4 0 Mach Maximum Operation (Mmo) Mach 1 4 2 Projected Future Latitude Deg 0 0 2 Energy Management (clean) N.25 0.008 0. 038 mb 0 5 5 Distance to Runway Threshold 0 5 A Fuel Temp.016 0.25 0.5 62.5 31. 0AD mb Inner Tank 1 Fuel Temp & Advisory 114 Warning 114 200 201 Inner Tank 2 Fuel Temp & Advisory Deg C Warning 11 11 11 12 20 15 16 11 11 12 11 15 17 17 17 17 11 11 11 11 17 11 17 17 11 11 11 11 17 16 16 16 11 11 11 16 14 15 14 0.20.0000625 0.25 mb) Altitude Own A/C Altitude Altitude (1013.5 1000 200 1000 50 62.0 1.016 0. Uncorrected.BNR DATA Eqpt Label ID (Hex) 114 177 Min Transit Interval (msec) 2 Max Transit Interval (msec) 2 Max Transport Delay (msec) 3 Parameter Name Left Outer Tank Fuel Temp & Advisory Warning Units Range (Scale) Sig Pos Resolution Bits Sense Notes Deg Feet US Pint mb Nmiles Deg C mb Deg C ± 512 131072 128 2048 1024 512 2048 ± 512 ± 512 512 ± 512 4096 ± 180 512 512 512 ± 512 4096 0.0 1.096 1024 Variable 1024 11 17 9 18 16 11 18 11 0.0 ± 512 131072 512 131072 131072 512 512 512 ± 512 131072 4.025 0.5 40 500 62. Uncorrected.096 4. PART 1 .016 0.5 .0000625 0.0 1.5 62.025 0.

008 0.5 62.001 0.125 0.001 0.5 62.3 31.5 62.025 0. Corrected (In.25 150 250 250 250 75 250 500 Max Transit Interval (msec) 2 100 125 125 200 See Attachment 6 Knots Knots Knots Knots Knots Deg C Deg C Deg C Deg C Deg C Deg C Deg C Deg C Deg C Deg Ft/Min Ft/Min Ft/Min Ft/Min Ft/Min Ft/Min Deg Deg C Deg C Deg C Lbs.) 1 4 0 Static Pressure Corrected (In.001 0.Hg.001 0.5 220 . Hg Feet Feet Feet 20000 64 256 4 64 64 131072 131072 131072 11 16 14 12 16 16 17 17 17 16 0.3 31.25 0.25 125 200 200 125 125 62.) 0 0 6 Baro Corrected Altitude #2 0 3 8 Baro Corrected Altitude #2 1 4 0 Baro Corrected Altitude #2 Ft/Min in.ARINC SPECIFICATION 429.001 1.5 100 62.3 150 31.3 31.3 31. mb Impacted Pressure.+90 512 ± 180 32768 32768 32768 32768 32768 32768 0.0625 0.25 1 0. mb Impact Pressure Subsonic 216 217 X X X ICAO Aircraft Address (Part 2) 002 006 029 029 Geometric Vertical Rate Static Pressure.5 100 100 62.125 0. Hg in. Uncorrected.5 62.015 0.25 .Page 62 ATTACHMENT 2 DATA STANDARDS TABLE 2 .5 31.5 62.5 62. Average.03125 0.5 400 500 500 500 125 500 2000 See Attachment 6 mb mb % RPM mb mb mb 512 512 256 4 512 512 512 14 14 14 12 14 16 14 0.5 62.5 62.015 0.125 0. Corrected 038 (In. Deg C Minute 1024 1024 2048 2048 2048 512 512 512 512 512 512 -80 .+90 -80 . Hg. Uncorrected.3 31.25 0.5 20 62.25 0.0625 0.56 62.03125 0.25 0. Hg.25 min 125 125 125 125 125 500 500 500 500 500 500 1000 1000 500 500 62.0625 0.25 0.0 1 62.5 125 125 100 100 125 40 125 Max Transport Delay (msec) 3 Parameter Name Units Range (Scale) 512 1024 1024 512 Sig Pos Resolution Bits Sense 11 14 12 11 0.5 50 50 62.5 62.25 0.03125 62.125 0.) N1 Limit (EEC) EPR Limit (EEC) Static Pressure.5 250 250 250 250 250 250 500 500 250 250 31.5 62.25 Notes 0 C C Taxi Speed 1 4 0 Computed Airspeed (CAS) 207 006 00A 025 038 Maximum Allowable Airspeed Maximum Allowable Airspeed OP.0 1.000172 16 16 16 16 16 16 2E-32 Cir 0.BNR DATA Eqpt Label ID (Hex) Min Transit Interval (msec) 2 50 62.03125 0.5 62.25 0.0625 0.25 0.5 250 62.25 0.000172 512 512 512 262144 512 265 min 12 12 15 15 15 11 11 11 11 11 12 10 10 12 20 11 11 11 11 11 11 11 11 11 11 18 11 10 0. Software Part Number Maximum Allowable Airspeed Airspeed Maximum Operating 140 (VMO) 0 0 6 True Airspeed 0 3 8 True Airspeed 1 4 0 True Airspeed 002 003 006 01A 038 0AD 10A 10B 140 142 004 005 006 038 03B 140 142 002 006 038 08D 140 142 Total Air Temperature Total Air Temperature Total Air Temperature Total Air Temperature Total Air Temperature Total Air Temperature Indicated Total Fan Inlet Temperature Total Fan Inlet Temperature Total Air Temperature (TAT) Projected Future Longitude Altitude Rate Altitude Rate Altitude Rate Altitude Rate Altitude Rate Altitude Rate Projected Future Longitude Fine Static Air Temperature Static Air Temperature Static Air Temperature Fuel Used Static Air Temperature (SAT) Vertical Time Interval Knots Knots Knots Knots 210 211 212 213 214 215 X X X ICAO Aircraft Address (Part 1) 006 01A 029 029 038 0AD 140 Impacted Pressure Impact Pressure N1 Actual (EEC) EPR Actual (EEC) Impacted Pressure.25 0. PART 1 . Hg % RPM in.

5 50 See Attachment 6 .5 62.3 31.5 62.5 1024 1000 1000 62.5 62.5 62.05 0.3 31.05 0.05 0.BNR DATA Eqpt Label ID (Hex) 221 006 038 0AD 12C 140 006 011 112 115 12C 140 Min Transit Interval (msec) 2 31.3 31.5 1000 1000 62.25 0.25 31.5 31.12 20 200 See Attachment 6 50 Max Transport Delay (msec) 3 Parameter Name Indicated Angle of Attack (Avg) Indicated Angle of Attack (Average) Indicated Angle of Attack Indicated Angle of Attack (Avg.5 See ARINC 429P2 See ARINC 604 Deg C 512 12 0.05 0.5 62.05 500 31.0 0.05 0.05 0.01 0.000122 1200 See ARINC 743A 241 Knots Deg/180 Deg/180 Knots Knots Deg 512 ±180 ±180 512 512 ±180 11 12 12 11 11 12 0.05 16.5 1000 62. Airspeed for Flap Extension Corrected Angle of Attack Corrected Angle of Attack FQIS System Data Min.5 Max Transit Interval (msec) 2 62.05 0.M.004 0.3 50 180 50 31.3 31.05 0. Indicated #1 Left Units Range (Scale) ±180 ±180 ±180 ±180 ±180 ±180 ±180 ±180 ±180 ±180 ±180 ±180 ±180 ±180 ±180 ±180 ±180 512 ±180 32768 512 512 ±180 ±180 Sig Pos Resolution Bits Sense 12 12 14 12 12 12 12 12 11 12 12 12 12 12 12 12 12 11 12 11 11 11 12 12 Increas -ing alt 0. 16 17 0. Indicated #1 Right Deg 0 0 6 Indicated Angle of Attack (#2 Left) 1 2 C Indicated Angle of Attack (#2 Left) 1 4 0 Angle of Attack.3 500 500 31.3 31.3 31.05 0.3 31.05 0. Airspeed for Flap Extension Angle of Attack.05 0. Airspeed for Flap Extension Min.5 31.25 0.3 31.ARINC SPECIFICATION 429.) Angle of Attack Indicated Average Indicated Angle of Attack (#1 Left) VOR Omnibearing TACAN Bearing Bearing Indicated Angle of Attack (#1 Left) Angle of Attack.Page 63 ATTACHMENT 2 DATA STANDARDS TABLE 2 .25 0.5 62. Indicated #2 Left Deg/180 Deg/180 Deg 224 225 0 0 2 Minimum Maneuvering Airspeed Knots 0 0 6 Indicated Angle of Attack (#2 Right) Deg/180 0 2 B Compensated Altitude Rate 056 060 12C 140 Minimum Maneuvering Air Speed Minimum Maneuvering Air Speed Indicated Angle of Attack (#2 Right) Angle of Attack. Indicated #2 Right Ft/Min Knots Knots Deg/180 Deg 227 0 3 D AVM Command 0 7 E BITE Command Word 0 A D Total Air Temperature 002 056 060 002 056 060 ACMS Information ACMS Information ACMS Information ACMS Information ACMS Information ACMS Information 231 233 234 See Attachment 6 235 0 0 2 ACMS Information 0 5 6 ACMS Information 0 6 0 ACMS Information 0 0 2 ACMS Information 0 5 6 ACMS Information 0 6 0 ACMS Information 002 00B 056 060 002 006 038 04D 056 060 140 ACMS Information Horizontal Uncertainty Level ACMS Information ACMS Information Min.05 0.3 31. PART 1 .5 100 220 50 62.05 Notes Deg/180 Deg/180 Deg/180 Deg/180 Deg Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 Deg 222 223 0 0 6 Indicated Angle of Attack (#1 Right) Deg/180 1 2 C Indicated Angle of Attack (#1 Right) Deg/180 1 4 0 Angle of Attack.5 62.5 200 62.5 62.5 62. Corrected See Attachment 6 236 See Attachment 6 237 N.3 500 500 500 31.1 0.05 0.25 0.25 0.5 500 31.25 0.05 0.05 0.3 31.05 0.5 1000 62.5 62.5 62.3 31.5 62.5 62.3 31.05 0.

001 40 40 0. Uncorrected.5 150 50 200 500 500 150 500 50 100 50 100 62.5 50 62.03125 Notes mb mb mb Dots mb mb 243 244 X X X Simulator to Avcs Control Word 01C 033 03B 08D 10A 10B 140 002 003 00A 029 038 03B 0AD 056 060 140 Fuel Flow (Engine Direct) Fuel Flow (Wf) Mach Error Fuel Flow Rate Fuel Mass Flow Fuel Mass Flow Angle of Attack. 32768 32768 0.03125 0.3 100 200 200 62.25 40 0.01 40 0.5 0. Lbs.5 0.01 0.ARINC SPECIFICATION 429.5 62. Knots Lbs. Normalized Minimum Airspeed Minimum Airspeed Minimum Airspeed N3 (Engine) Avg.03125 0.0625 0.5 62.03125 0. Speed (VCMIN) Horizontal Figure of Merit Total Fuel Total Fuel Speed Error Total Fuel Control Minimum Speed (Vcmin) Total Fuel Control Minimum Speed (Vcmin) Fuel to Remain Fuel on Board Airspeed Minimum Vmc Continuous N1 Limit Maximum Continuous EPR Limit Preselected Fuel Quantity Preselected Fuel Quantity Indicated Side Slip Angle Indicated Side Slip Angle or AOS Preselected Fuel Quantity Distance to Go Distance to Go Baro Corrected Altitude #3 Flight Leg Counter Baro Corrected Altitude #3 245 246 247 002 006 01C 029 038 03B 002 00B 01F 02C 03B 04D 056 05A 060 0EB 114 140 002 02B 02C 05A 038 0AD 114 001 002 006 01A 038 50 250 251 100 100 31.0 1.001 0.5 150 20 62.5 62.Page 64 ATTACHMENT 2 DATA STANDARDS TABLE 2 .008 0. Lbs.0 100 150 150 75 31.125 0.008 0.5 62.0625 0.064 32768 170 170 2 256 256 512 256 2048 4 2048 256 256 2048 512 2048 4096 256 2048 ±180 512 16 655360 655360 256 655360 512 655360 512 1638400 655320 512 256 4 655360 655360 ±180 ±180 655320 4096 4096 131072 131072 512 8 16 11 16 15 15 11 12 12 13 14 16 12 16 12 12 16 11 16 12 14 16 14 11 18 14 14 12 14 11 14 11 14 13 11 14 12 14 14 12 14 13 15 15 17 17 9 128.0625 0.5 175 62.25 100 40 0.3 Max Transit Interval (msec) 2 125 125 125 250 200 125 100 200 250 250 125 100 100 125 125 125 125 100 125 250 125 125 125 125 100 125 200 100 125 250 100 1200 1000 1000 250 1000 100 200 100 125 125 200 200 400 200 62.03125 0.1 E-5 40 40 0.03125 0. mb Total Pressure Units Range (Scale) 2048 2048 2048 4 2048 2048 Sig Pos Resolution Bits Sense 16 16 16 11 18 16 0.03 1.M. Static Pres.5 200 200 50 See ARINC Rpt 610 Max Transport Delay (msec) 3 Parameter Name Total Pressure Total Pressure Total Pressure Speed Deviation Modified Intent Data Block Total Pressure.5 150 62.0 0.25 0.002 0. Knots Lbs. Feet Feet Min.M.015 0.5 200 See Attachment 6 252 0 0 1 Time to Go .5 50 100 100 100 31. Knots Lbs.BNR DATA Eqpt Label ID (Hex) 242 006 01A 038 03B 056 0AD 140 Min Transit Interval (msec) 2 62.0625 0.0 1.00003 0.03125 0.125 1.3 75 31.001 0. Deg/180 Deg/180 Lbs.5 62.M.008 0.05 0.5 33 Lbs/hr pph Mach PPH MSEC MSEC Ratio Knots Knots Knots % RPM mb mb Knots Knots mb Knots mb RPM % RPM mb Deg/180 Knots N.015 0. PART 1 .5 62.5 62. Lbs. Uncorrected Control Maximum Speed (VCMAX) Average Static Pressure N1 (Engine Direct) N1 (Engine Direct) Avg Static Pres mb Corrected Angle of Attack Error Control Min.015 0.3 62.03125 0.3 31.0625 0. mb uncorrected EPR Error Average Static Pressure mb Uncorrected Minimum Airspeed Minimum Airspeed Static Pressure. N. Lbs.5 62.25 6.25 0.3 31. N.5 100 50 62.0 0.5 50 62.06 40 0. Knots % RPM Lbs.

PSIA 256 64 131072 64 10 13 15 14 0.+850 -55 . Lbs. Min. Knots Lbs.1 0.0 0.5 100 100 500 TBD 100 100 100 62.015 0.03125 4 4 0. Lbs.BNR DATA Eqpt Label ID (Hex) 002 006 01A 02F 038 03F 0EB 253 Min Transit Interval (msec) 2 100 31. Lbs. Knots Min.004 500 100 100 500 150 1000 200 200 1000 250 See Attachment 6 . 0 0 2 Go-Around N1 Limit 0 1 E Go-Around EPR Limit 0 3 8 Corrected Side Slip Angle 002 01E 04D 13A 140 002 01E 02F 03F 04D 08E 13A 140 002 00A 02C 04D 056 05A 060 114 140 002 02C 056 05A 060 114 140 02C 05A 033 10A 10B 114 02C 033 05A 10A 10B 114 002 00A 01C 02C 033 Cruise N1 Limit Cruise EPR Limit Actual Fuel Quan (test) N1 Cruise Altitude Rate Climb N1 Limit Climb EPR Limit Maximum Climb EPR Rating Maximum Climb EPR Rating Fuel Quantity (gal) Spoiler Position N1 Climb Impact Pressure Time For Climb V Stick Shaker Fuel Quantity (Tanks) #1 Fuel Discretes Time for Climb Fuel Quantity-Left Outer Cell Time for Climb Left Outer Tank Fuel Quantity Equivalent Airspeed Time For Descent Fuel Quantity (Tanks) #2 Time for Descent Fuel Quantity Left W/T Tank Time for Descent Fuel Quantity (Tanks) #2 Total Pressure (High Range) Fuel Quantity (Tanks) #3 Fuel Quantity Center Tank T5 LP Turbine Discharge Temp LP Turbine Discharge Temperature Collector Cell 1 and 2 Fuel Quantity Fuel Quantity (Tanks) #4 P49 Fuel Qty Right I/C or W/T Tank LP Turbine Inlet Pressure LP Turbine Inlet Pressure Fuel on Board at Engine Start Documentary Data Predicitive Airspeed Variation LP Compressor Exist Pres.05 0.001 1. PART 1 . Min. (PT3) Fuel Quantity (Tanks) #5 LP Compressor Exist Pressure 254 200 255 200 256 See ARINC 429P2 Zero for A-321 257 260 See Note [5] 261 500 150 100 100 100 1000 250 200 500 500 262 Knots PSIA Lbs.03125 1 0.0625 1 4 1 4 1 4 0. Deg C Deg C Deg C Lbs.25 0.3 100 100 31. Lbs.125 0.25 4 1 4 1 4 0. Lbs. Lbs.5 200 200 200 200 1000 100 200 125 200 200 1000 TBD 200 200 200 125 200 1000 200 200 200 1000 125 1000 200 250 500 500 200 Max Transport Delay (msec) 3 Parameter Name Time to Go Baro Corrected Altitude #4 EPR Idle EPR Idle Reference Baro Corrected Altitude #4 EPR Idle Reference Time Until Jettison Complete Units Range (Scale) 512 131072 4 4 131072 4 64 256 4 ±180 256 4 262144 256 131072 256 4 4 4 32768 +180 256 4096 512 512 131072 512 131072 512 131072 1024 512 131072 512 131072 512 131072 4096 131072 131072 1024 -55 .5 200 1000 200 200 62.3 50 100 500 100 31. Min.25 50 100 100 100 500 50 100 62.5 500 100 150 100 100 Max Transit Interval (msec) 2 200 62.25 0.+850 131072 131072 128 131072 2-120 2-120 131072 Sig Pos Resolution Bits Sense 9 17 12 12 17 12 6 14 12 12 14 12 15 14 13 14 12 12 12 15 11 14 17 9 11 15 9 15 9 15 14 9 15 9 15 9 15 17 15 15 12 11 11 15 15 14 15 11 11 15 1.5 200 200 62.50 4 4 0.001 8 0.0 1.001 0. Feet Feet Minutes % RPM Deg/180 % RPM Lbs % N1 Nom Ft/Min % RPM N/A N/A Gallons Deg/180 % N1 Nom mb Min.0 0.008 4 0. PSIA Lbs. Min.015 0.Page 65 ATTACHMENT 2 DATA STANDARDS TABLE 2 .015 0.015 16 0.5 100 500 100 100 100 500 62.015 0.001 1 0.001 1.008 4 0.001 0.50 0. Lbs.0 0.5 200 200 1000 200 62.ARINC SPECIFICATION 429.3 100 500 50 100 31.001 0. PSIA PSIA Lbs.001 0. mb Lbs.125 4 Notes Min.

Knots Knots Deg/180 PF Deg C Knots Knots Deg C Deg C Lbs. Maneuver Airspeed HP Compressor Inlet Temp.25 4 0.03 1 1 1.01 0.+160 -55 .032 4 0.03 4 0.03 0.25 0.01 0.01 4 0. Burner Pressure Min.25 0.25 0.01 0.35 131072 512 512 ±180 655. Min. Selected Compressor Dischg Pres.01 4 0. Maneuver Airspeed Max. PSIA PF PSIA PSIA Min. Buffet Airspeed Selected Compressor Dischg Temp Selected Compressor Dischg Temp Inner Tank 3 Fuel Quantity 500 100 100 500 150 TBD 500 500 100 100 1000 200 200 1000 250 TBD 1000 1000 500 500 50 264 002 00A 01C 02C 02F 04D 033 03F 056 060 10A 10B 13A 002 004 00A 01C 02C 033 038 04D 056 060 10A 10B 114 100 100 100 500 100 TBD 150 100 100 100 62.50 0.35 131072 2-50 2-50 131072 512 512 256 131072 256 655.25 0.5 62. Airspeed for Flap Retraction Min.50 4 0.25 0. Knots Knots Lbs Deg C PF Knots Knots Deg C Deg C Lbs.35 512 512 2048 2048 5-600 5-600 512 512 ±256 512 1024 131072 1024 ±256 655. Maneuver Speed Throttle Position Command T/U Cap-C Tank 5-8 Spare T/C Max.+160 -55 . PART 1 .25 0. Airspeed for Flap Retraction Selected Compressor Inlet 10A Temperature (Total) Selected Compressor Inlet Temp 10B (Total) 1 1 4 Collector Cell 3 and 4 Fuel Quantity Time To Touchdown Min.25 0.063 0.Page 66 ATTACHMENT 2 DATA STANDARDS TABLE 2 .25 0. PF Lbs.5 100 50 100 100 500 150 TBD 50 50 100 100 200 200 200 1000 200 TBD 250 200 200 200 250 250 200 100 20 200 200 1000 250 20 TBD 100 100 500 500 145 265 50 UP UP 266 0 4 D T/U Cap-C Tank 1-4 1 1 4 Inner Tank 2 Fuel Quantity 002 00A 02B 04D 033 056 060 10A 10B 114 Maximum Maneuver Airspeed Predictive Max. Buffet Airspeed Integrated Vertical Acceleration Maneuvering Airspeed HP Compressor Exit Temp (TT4.000244 0.25 0.+650 131072 655.BNR DATA Eqpt Label ID (Hex) 04D 05A 10A 10B 114 263 002 00A 01C 02C 033 04D 056 060 Min Transit Interval (msec) 2 TBD 100 100 100 Max Transit Interval (msec) 2 TBD 200 500 500 Max Transport Delay (msec) 3 Parameter Name T/U Cap-L Tank 1-4 Fuel Quantity-Right Outer Cell HP Compressor Inlet Total Pres.000244 0.25 0.35 256 512 512 -55 .125 4 0.125 4 1 0.06 4 0.35 Sig Pos Resolution Bits Sense 16 15 11 11 15 11 11 12 15 12 16 11 11 11 11 15 11 11 14 15 14 16 14 14 11 11 11 11 14 11 20 11 12 15 12 20 16 11 11 11 11 15 16 15 11 11 12 16 12 11 11 11 11 15 16 0.125 0.35 512 512 -55 .00 0.+160 131072 2048 512 512 131072 512 655. Airspeed for Slats Retraction HP Compressor Exit Pressure Fuel Quantity (Tanks) #7 Burner Pressure T/U Cap-L Tank 9-12 HP Compressor Exit Pressure Burner Pressure Time to Touchdown Time to Touchdown Selected Compressor Dischg Pres.+160 131072 655.01 Notes PF Lbs.125 0.ARINC SPECIFICATION 429.25 0. Min.25 0.05 0.00 1.25 0. PF Min.+650 -55 . Airspeed for Flap Retraction LP Compressor Exit Temperature Fuel Quantity (Tanks) #6 LP Compressor Exit Temperature T/U Cap-L Tank 5-8 Min. Airspeed for Flap Retraction Min.5) Fuel Quantity (Tanks) #8 HP Compressor Exit Temperature Integrated Vertical Acceleration T/U Cap-L Tank 13-14 Min.01 0. Buffet Airspeed Min.03 0. PSIA PSIA Lbs. Center Tank Fuel Quantity Units Range (Scale) 655. PSIA PSIA PSIA Knots Ft/Sec Knots Lbs.063 0. HP Compressor Inlet Total Pres. Knots Lbs.25 0.032 0. (total) HP Compressor Inlet Temperature Inner Tank 4 Fuel Quantity T/U Cap-C Tank 9 Stored TACAN Control Word TBD TBD 267 500 100 50 TBD 150 500 500 500 500 1000 200 100 TBD 250 1000 1000 1000 1000 50 270 04D 115 TBD 25 TBD 50 See ARINC 429P2 .35 512 512 -55 . Deg C Ft/Sec PF Knots Knots Deg C Deg C Lbs.031 0.

Longitude Aileron Trim Present Position .000172 4 0.01 0.35 655. Deg/180 Deg/180 Deg/180 Deg/180 304 305 310 .01 0.000172 0.01 0.063 0.Page 67 ATTACHMENT 2 DATA STANDARDS TABLE 2 .125 0.063 0.+125 100 100 100 100 100 100 100 100 100 100 0-180N/ 0-180S 0-180N/ 0-180S ±180 0-180N/ 0-180S 327.000172 0.063 0.063 0.125 0.000172 0.088 0.000172 0.000172 0.01 0.01 0.063 0.Longitude Present Position .Longitude Deg/180 Deg/180 Deg/180 Deg/180 PF Deg/180 Deg/180 Lbs.35 655.5 62.01 0.000172 0.088 0.Latitude Comp Cap-Tank Present Position Latitude Present Position Latitude Right Outer Tank Fuel Quantity Present Position . 6 for SDI encoding Used only in simulator Used only in simulator Used only in simulator Max Transport Delay (msec) 3 Parameter Name Units Range (Scale) Sig Pos Resolution Bits Sense Notes 271 04D T/U Cap-A Tank 1-4 T/U Cap Tank 5-8 T/U Cap-A Tank 9-11 T/U Cap-R Tank 1-4 T/U Cap-R Tank 5-8 FCC to Simulator Control Word FMC to Simulator Control Word TCC to Simulator Control Word T/U Cap-R Tank 9-12 T/U Cap-R Tank 13-14 ECU Internal Temperature ECU Internal Temperature Demanded Fuel Metering Valve Pos Demanded Fuel Metering Valve Pos PF PF PF PF PF 655.063 0.063 0.35 655.35 16 16 16 16 16 0.063 0.063 0.35 -55 .01 272 04D 273 04D 274 275 276 04D 04D 001 002 003 04D 277 04D 300 10A 10B 301 10A 10B 302 10A 10B 303 10A 10B 10A 10B 10A 10B 002 004 029 038 04D 056 060 114 311 002 004 029 038 Demanded Variable Stator Vane Pos % Demanded Variable Stator Vane Pos % Demanded Variable Bleed Valve Pos % Demanded Variable Bleed Valve Pos % Demanded HPT Clearance Valve Pos % Demanded HPT Clearance Valve Pos % Demanded LPT Clearance Valve Pos % Demanded LPT Clearance Valve Pos % Present Position .000172 100 100 50 100 200 200 100 200 TBD TBD 500 500 62.ARINC SPECIFICATION 429.+125 -55 .35 655.063 0.BNR DATA Eqpt Label ID (Hex) Min Transit Interval (msec) 2 TBD TBD TBD TBD TBD 50 33 50 PF PF Deg C Deg C % % 655.01 0. PART 1 .Latitude Present Position .35 655.67 0-180N/ 0-180S 0-180N/ 0-180S 131068 0-180E/ 0-180W 0-180E/ 0-180W ±180 0-180E/ 0-180W 16 16 11 11 11 11 11 11 11 11 11 11 11 11 20 20 11 20 15 20 20 15 20 20 11 20 0.5 100 100 100 100 250 250 250 250 100 100 50 100 TBD 100 100 Max Transit Interval (msec) 2 TBD TBD TBD TBD TBD 150 100 150 TBD TBD 1000 1000 250 250 500 500 500 500 1000 1000 1000 1000 200 200 100 200 TBD 200 200 See Att.Latitude Aileron Position Present Position .

True Additional Center Tank (Act 2) Fuel Quantity Units Range (Scale) 64 0-180E/ 0-180W 0-180E/ 0-180W 131072 4096 4096 4096 ±180 4096 4096 131072 4096 131072 ±180 ±180 ±180 ±180 ±180 ±180 131072 ±180 131072 Sig Pos Resolution Bits Sense 10 20 20 15 15 15 15 11 15 15 15 15 15 12 15 10 11 15 12 15 12 15 TE Down 0.0625 0.0 TE Down CW from north 0.ARINC SPECIFICATION 429.7 25 50 100 50 25 50 100 200 100 50 50 CW from north 0.5 0.BNR DATA Eqpt Label ID (Hex) 03B 056 060 114 312 002 004 005 029 038 056 05A 060 114 313 002 004 025 029 038 056 05A 060 114 Min Transit Interval (msec) 2 150 100 100 Max Transit Interval (msec) 2 250 200 200 Max Transport Delay (msec) 3 Parameter Name Control Wheel Roll Force Present Position Longitude Present Position Longitude Trim Tank Fuel Quantity Ground Speed Ground Speed Ground Speed Rudder Position Ground Speed Ground Speed Fuel Quantity ACT 1 Ground Speed Additional Center Tank (Act 1) Fuel Quantity Track Angle .0625 4 25 25 125 50 25 150 50 50 250 100 50 250 50 315 001 002 004 005 029 038 056 060 0A1 Deg/180 Knots Knots Knots Deg/180 Knots Knots Knots Deg/180 ±180 256 256 256 ±180 256 256 256 ±180 12 8 8 8 11 8 8 8 12 TE Down 0.True Track Angle .05 50 .0055 0. Knots Knots Knots Deg/180 Knots Knots Lbs.0 1.True Rudder Trim Track Angle .125 0.7 0. ±180 ±180 ±180 ±180 ±180 64 131072 12 15 10 11 15 10 15 0.000172 4 0.0055 0.2 0.05 0.0 1.125 4 0.088 0.True Track Angle .05 0.05 316 002 004 029 038 056 Wind Direction (True) Wind Angle Oil Temperature (Engine) Wind Angle Wind Direction (True) Deg/180 Deg/180 Deg C Deg/180 Deg/180 +180 ±180 2048 ±180 +180 12 8 12 8 12 0.125 4 0. 25 25 25 50 25 25 100 25 50 50 50 100 50 50 200 50 25 25 125 50 25 25 100 25 50 50 250 100 50 50 200 50 314 002 004 025 029 038 03B 114 Stabilizer Pos Indication (B747-400) Deg/180 True Heading True Heading Elevator Position True Heading Control Wheel Pitch Force Rear Center tank (RCT) Fuel Quantity Stabilizer Position Wind Speed Wind Speed Wind Speed Stabilizer Position Wind Speed Wind Speed Wind Speed Stabilizer Position Deg/180 Deg/180 Deg/180 Deg/180 Lbs.05 0. Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 Lbs.0 1.05 4 Notes Lbs.0 1.088 1.0055 0. Deg/180 Lbs.True Fuel Quantity ACT 2 Track Angle .125 0.True Track Angle .05 4 0. Knots Lbs.2 0.125 0.Page 68 ATTACHMENT 2 DATA STANDARDS TABLE 2 .0 25 50 50 50 50 50 50 50 25 50 100 100 100 100 100 100 100 50 TE Down 0.088 0. Deg/180 Deg/180 Lbs.05 1.000172 0.0055 0. Lbs.125 0. PART 1 .088 0.

ARINC SPECIFICATION 429.+170 -55 .5 0.01 0.2 1 0.+105 -5 .01 0. Deg.50 0.191 ±180 ±180 ±180 ±180 ±180 ±180 -55 .05 0.Magnetic Track Angle .05 0.001 0.00 1.Page 69 ATTACHMENT 2 DATA STANDARDS TABLE 2 ./180 % +180 -55 .00 0.00 0.0055 0. PART 1 .0055 0.0055 0.05 0.05 0.Magnetic Track Angle .063 0.2 0.50 1 0.5 1000 1000 20 20 250 20 TBD 250 See Att. 6 for SDI encoding 322 323 10 10 10 20 20 20 500 500 10 10 125 10 TBD 62.+105 12 11 11 12 12 15 15 10 12 15 12 12 14 15 15 10 15 15 13 12 11 11 12 12 12 11 11 12 12 12 12 12 12 11 11 17 12 12 12 17 17 11 11 14 14 10 14 15 14 11 0.001 0.0 0.05 0.0055 0.05 0.+1100 +180o ±180 ±180 ±180 +180o +180o -55 .01 0.Magnetic Track Angle .Magnetic Track Angle Magnetic Track Angle Magnetic Engine Oil Pressure Magnetic Heading Magnetic Heading Magnetic Heading Own A/C Magnetic Heading Magnetic Heading Density-Tank Drift Angle Drift Angle Drift Angle Drift Angle Drift Angle Drift Angle Exhaust Gas Temperature (Total) Exhaust Gas Temperature (Total) Flight Path Angle Flight Path Angle Flight Path Angle Flight Path Angle Flight Path Angle Flight Path Angle Total Compressor Discharge Temp Total Compressor Discharge Temp Geometric Altitude Flight Path Acceleration Flight Path Acceleration Flight Path Acceleration Geometric Altitude Geometric Altitude Variable Stator Vane Position Variable Stator Vane Position Pitch Angle Pitch Angle Pitch Angle Pitch Angle Tank VSO Quantity Effective Pitch Angle Selected Fuel Metering Valve Pos Deg/180 Deg C Deg C Deg C Deg/180 Deg/180 Deg/180 Deg/180 PSI Deg/180 Deg/180 Deg/180 PSI Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 Lb/Gal Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 Deg C Deg C Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 Deg C Deg C Feet g g g Feet Feet % % Deg/180 Deg/180 Deg/180 Deg/180 Gal.00 1.BNR DATA Eqpt Label ID (Hex) Min Transit Interval (msec) 2 25 250 250 Max Transit Interval (msec) 2 50 1000 1000 SDI 1=L SDI 2 =R 25 25 25 125 50 25 25 25 50 50 50 250 100 50 50 50 SDI 1 = L/SDI 2 = R 25 25 125 25 25 TBD 25 25 25 25 25 25 500 500 25 25 25 25 25 25 500 500 50 50 250 500 50 TBD 50 50 50 50 50 50 1000 1000 50 50 50 50 50 50 1000 1000 Max Transport Delay (msec) 3 50 Parameter Name Units Range (Scale) Sig Pos Resolution Bits Sense CW from north Notes 060 10A 10B 0D0 317 002 004 005 025 029 038 056 060 0D0 004 005 025 035 038 04D 321 002 004 005 038 056 060 10A 10B 002 004 005 038 056 060 10A 10B 002 004 005 038 056 060 10A 10B 004 005 025 038 04D 05A 10A Wind Direction (True) Engine Oil Temperature Engine Oil Temperature Engine Oil Temperature Track Angle .05 0.2 0.0055 0.05 1.001 1 1 0.Magnetic Oil Pressure (Engine) Track Angle .05 0.05 1.09 0.+105 ±180 ±180 ±180 ±180 32768 ±180 -5 .063 0.+170 2048 ±180 ±180 ±180 ±180 4096 ±180 ±180 ±180 4096 ±180 ±180 ±180 ±180 ±180 8.+650 50000 4 4 4 50000 50000 -5 .0055 0.05 0.+1100 -55 .001 0.05 0. 6 for SDI encoding 324 .01 1.0055 0.+650 -55 .063 320 See ARINC 735 See Att.09 0.05 0.25 0.05 0.

001 0.001 0.02 0.ARINC SPECIFICATION 429.015 0.00 1.001 0. Feedback Body Lateral Acceleration A/O Heat Xchr Valve Pos.01 0.+105 4 4 128 4 128 -5 .063 0.+105 -5 .+105 ±180 ±180 ±180 ±180 4 ±180 4 ±180 -5 .09 Notes Deg/180 Deg/180 Deg/180 Inches Deg/180 Inches Deg/180 % % Deg Deg/Sec Deg/Sec Deg/Sec Lbs PSIA PSIA Deg/Sec Deg/Sec Deg/Sec Lbs/Gal % % Deg/Sec Deg/Sec % Deg/Sec % % % g g % g % % % g g % g % g g Lb/Hr g Lb/Hr Deg/180 Deg/180 10 10 125 100 10 100 62.+105 -5 .BNR DATA Eqpt Label ID (Hex) 10B 114 325 004 005 01A 025 02F 038 03F 05A 10A 10B 114 004 005 038 04D 10A 10B 004 005 038 04D 10A 10B 004 005 02F 038 03F 10A 10B 331 004 005 02F 038 03F 10A 10B 004 005 02F 038 03F 004 005 02F 038 03F 004 005 Min Transit Interval (msec) 2 62.001 0. Feedback Body Longitudinal Acceleration LTC Cooling Valve Pos.063 0.001 0.015 0.063 0.063 0.001 0.2 0.+105 4 4 128 4 128 4 4 32768 4 32768 ±180 ±180 Sig Pos Resolution Bits Sense 11 13 14 14 10 12 14 12 14 11 11 13 13 13 13 14 11 11 13 13 13 13 11 11 13 13 12 OPEN 13 12 OPEN 11 11 12 12 12 OPEN 12 12 OPEN 11 11 12 12 12 OPEN 12 12 OPEN 12 12 12 12 12 11 11 0.02 0.03 0.181 -5 .5 Max Transit Interval (msec) 2 250 Max Transport Delay (msec) 3 Parameter Name Selected Fuel Metering Valve Pos Effective Pitch Angle Roll Angle Roll Angle Engine Control Trim Feedback Roll Angle Stator Vane Feedback Roll Angle Stator Vane Feedback Effective Roll Angle Selected Variable Stator Vane Pos Selected Variable Stator Vane Pos Effective Roll Angle Body Pitch Rate Body Pitch Rate Body Pitch Rate Uplift Quantity Compressor Discharge Static Press Compressor Discharge Static Press Body Roll Rate Body Roll Rate Body Roll Rate Uplift Density Fuel Metering Valve Position Fuel Metering Valve Position Body Yaw Rate Body Yaw Rate HC/TC Cooling Valve Pos.015 0.001 8 0.015 0.063 0.015 0.015 0.063 0.001 0.+105 128 128 128 128 128 -5 .015 100 1.00 0.001 8 0.03 0.09 0.03 0. Feedback Body Normal Acceleration Body Normal Acceleration Acceleration Fuel Flow Limit Body Normal Acceleration Acceleration Fuel Flow Limit Platform Heading Platform Heading % Deg Units Range (Scale) -5 . Feedback Selected HPT Clearance Valve Position Selected HPT Clearance Valve Pos Body Longitudinal Acceleration Body Longitudinal Acceleration LTC Cooling Valve Pos.001 0.03 0.01 0.5 20 20 250 200 20 200 250 250 326 10 10 10 TBD 500 500 10 10 10 TBD 500 500 10 10 100 10 100 250 250 10 10 100 10 100 250 250 10 10 100 10 100 10 10 100 10 100 20 20 20 20 20 TBD 1000 1000 20 20 20 TBD 1000 1000 20 20 200 20 200 1000 1000 20 20 200 20 200 1000 1000 20 20 200 20 200 20 20 200 20 200 40 40 327 330 332 333 334 .5 62.+105 -5 .063 0.063 0.015 0.01 0.001 0.001 0.+105 -5 . Feedback Selected LPT Clearance Valve Pos Selected LPT Clearance Valve Body Lateral Acceleration Body Lateral Acceleration A/O Heat Xchr Valve Pos.Page 70 ATTACHMENT 2 DATA STANDARDS TABLE 2 .03 0.015 0. Feedback Body Yaw Rate HC/TC Cooling Valve Pos.+105 ±180 128 128 128 1638400 5-600 5-600 128 128 128 8.01 0.03 0.063 0. PART 1 .

015 0.001 0.015 0.001 0.015 0.001 0.001 0. PART 1 .001 0.063 0.5 BLD Actuator Position Track Angle Rate Track Angle Rate Selected Variable Bleed Valve Pos Selected Variable Bleed Valve Pos Max Climb Angle Inertial Pitch Rate Inertial Pitch Rate Engine Torque N2 Corrected to Sta 2.001 0.015 0.001 N/A Notes Lb/Hr Deg/180 Lb/Hr Deg/Sec Deg/Sec Deg/Sec % Deg/Sec % Deg/Sec Deg/Sec % % Deg Deg/Sec Deg/Sec % % Deg/Sec % % % Ratio % RPM Deg/Sec Deg/Sec % Deg/Sec % % 336 337 340 Deg/Sec Deg Deg/Sec % N1Nom Ratio % RPM % RPM Deg % RPM % RPM % RPM Deg 341 .015 0.5 BLD Actuator Position Track Angle Rate 2.001 0.+105 32 128 128 256 128 128 128 -5 .015 0.5 100 100 100 20 Hz 100 100 50 50 25 25 20 Hz 100 TBD Max Transit Interval (msec) 2 200 40 200 20 20 20 200 20 200 20 20 500 500 200 20 20 200 200 20 200 1000 1000 200 20 20 200 20 1000 1000 200 20 110 Hz 20 200 100 200 50 200 50 50 125 200 200 200 110 Hz 200 200 100 100 50 50 110 Hz 200 TBD Engine Types: P&W Engine Types: GE Max Transport Delay (msec) 3 Parameter Name Fuel Flow Command Platform Heading Fuel Flow Command Track Angle Rate Track Angle Rate Track Angle Rate 2.001 0.031 0.001 0.5 Inertial Pitch Rate N2 Corrected to Sta 2.+105 -5 .015 0.015 0.Required For Level Flight Inertial Roll Rate Inertial Roll Rate Engine Rating Inertial Roll Rate HPT Clearance Valve Position HPT Clearance Valve Position EPR Actual Inertial Yaw Rate Track Angle Grid Inertial Yaw Rate EPR Actual EPR Actual (Engine Direct) EPR Actual EPR Actual EPR Actual EPR Actual N1 Take Off Pressure Ratio (Pt/Ps) Target N1 N1 Command EPR Command Grid Heading N1 Command EPR Command N1 Command (Engine) EPR Command (Engine) N1 Command EPR Command Grid Heading EPR Command I/O S/W REV 1&2 Units Range (Scale) 32768 ±180 32768 32 32 32 128 32 128 32 32 -5 .BNR DATA Eqpt Label ID (Hex) 02F 038 03F 335 002 004 005 02F 038 03F 056 060 10A 10B 002 004 005 01A 02F 038 03F 10A 10B 002 002 004 005 01A 038 10A 10B 003 004 004 005 01A 029 02D 02F 033 03F 13A 140 002 003 003 004 01A 01A 029 029 02F 02F 038 03F 04D Min Transit Interval (msec) 2 100 20 100 10 10 10 100 10 100 10 10 100 100 100 10 10 100 100 10 100 500 500 100 10 10 100 10 500 500 100 10 20 Hz 10 100 50 100 25 100 25 25 62.015 0.063 0.015 0.5 Variable Bleed Valve Position Variable Bleed Valve Position EPR .001 0.031 0.001 0.031 0.015 0.031 0.+105 -5 .09 8 0.001 0.001 0.063 0.+105 4 128 ± 180 128 4 4 4 4 4 4 256 16 256 256 4 ± 180 256 4 256 4 256 4 ± 180 4 (1) Sig Pos Resolution Bits Sense 12 11 12 11 11 11 12 11 12 11 11 11 11 15 13 13 12 12 13 12 11 11 12 15 13 13 12 13 11 11 12 13 15 13 12 12 12 12 12 12 14 14 14 14 12 15 14 12 14 12 14 12 15 12 16 Climb 8 0.015 0.0055 0.ARINC SPECIFICATION 429.015 0.015 0.063 0.001 0.015 0.Page 71 ATTACHMENT 2 DATA STANDARDS TABLE 2 .015 0.063 0.015 0.0055 0.0055 0.063 0.015 0.015 0.+105 -5 .015 0.063 0.063 0.Required For Level Flight N1 .+105 ±4 ±256 128 128 0-256 128 -5 .015 0.

5 31.5 25 200 200 100 50 200 50 200 250 250 50 See ARINC 429.015 0.015 0.032 0.015 0.015 0.032 0.015 2.015 0.001 N/A 0.015 0.3 31.Page 72 ATTACHMENT 2 DATA STANDARDS TABLE 2 .5 256 4 256 256 4 256 4 256 4 4 4 256 4 (1) Sig Pos Resolution Bits Sense 13 13 14 12 14 14 12 14 12 14 12 12 12 14 12 16 13 13 12 14 12 12 13 13 14 14 14 14 14 14 0.001 0.032 0.5 0.015 0.015 Notes % % % N1Nom Ratio % RPM % RPM % RPM % RPM % RPM % % Ratio % RPM % RPM % % % RPM % RPM % RPM % RPM % RPM % RPM 117.5 117.063 0.015 0.001 0.5 4 256 4 256 117.001 0.3 25 Max Transit Interval (msec) 2 100 100 50 125 200 200 200 200 200 200 200 200 250 250 200 TBD 500 500 500 200 200 50 100 100 100 100 100 50 200 50 100 100 100 50 SDI 1 = L/SDI 2 = R 100 100 50 25 100 25 100 62.ARINC SPECIFICATION 429.001 0.5 117.3 25 62.5 117. TLA N2 N2 N2 N2 N2 N2 Units Range (Scale) 117.5 0.032 0. TLA N1 Command vs.063 0.015 0.001 0.5 0.015 0.001 0.+1100 2048 2048 12 12 14 13 12 12 12 12 12 12 11 11 12 12 0.03 0.001 0.5 100 100 100 100 100 100 100 100 150 150 100 TBD 100 100 250 100 100 20 31.032 0.015 0.015 0.5 1.032 0.3 31.5 0. Part 2 See Att.3 31.001 0.00 0.+1100 -55 .5 0.3 50 50 50 25 50 25 50 % % % RPM % RPM Deg C Deg C Deg C Deg C Deg C Deg C Deg C Deg C Deg C Deg C 128 128 256 256 2048 2048 2048 2048 2048 2048 -55 .063 0.5 256 256 256 256 256 256 344 0 4 D Fuel Discretes 10A 10B 13A 0D0 345 01A 01C 029 02F 033 03F 04D 10A 10B 13A 0D0 Selected Actual Core Speed Selected Actual Core Speed N2 Speed N2 Exhaust Gas Temperature Exhaust Gas Temperature Exhaust Gas Temperature Exhaust Gas Temperature Exhaust Gas Temperature Exhaust Gas Temperature Discretes Status 1&3 Selected Exhaust Gas Temp (Total) Selected Exhaust Gas Temp (Total) EGT Trimmed EGT See ARINC 429P2 SDI 1 = L/SDI 2 = R 346 003 01A 02F 033 03F 04D N1 Actual N1 Actual N1 Actual N1 Actual N1 Actual Cable Cap-Hi-Z % RPM % RPM % RPM % RPM % RPM PF 256 256 256 256 256 65535 14 14 14 14 14 15 0.5 0.015 0.015 0.5 62.015 0.015 0.015 0. PART 1 .BNR DATA Eqpt Label ID (Hex) 10A 10B 13A 140 342 002 003 003 01A 01A 029 029 02F 03B 03B 03F 04D 10A 10B 140 343 003 003 01A 10A 10B 01A 01C 029 02F 033 03F Min Transit Interval (msec) 2 31.00 1. 6 for SDI encoding Max Transport Delay (msec) 3 Parameter Name Command Fan Speed Command Fan Speed N1 Reference Pressure Ratio (Ps/Pso) N1 Bug Drive N1 Limit EPR Limit N1 Maximum EPR Maximum N1 Limit (TCC) EPR Limit (TOC) Maximum Available EPR EPR Limit N1 Limit Maximum Available EPR S/W REV-Tank Max Allowed Fan Speed Max Allowed Fan Speed Air Density Ratio N1 Derate EPR Rate N1 Demand N1 Command vs.0 100 100 25 50 25 100 200 200 50 200 50 200 See Att. 6 for SDI encoding .

ARINC SPECIFICATION 429. N1 Along Track Horizontal Acceleration Along Track Horizontal Acceleration Derivative of N1 vs. B See Note [6] See Note [6] 62.Page 73 ATTACHMENT 2 DATA STANDARDS TABLE 2 .12 9 0.5 62.5 0. 6 for SDI Bit 11-Chan.0 64.03 8 0.3 31.12 Sig Pos Resolution Bits Sense 12 12 14 13 12 11 11 14 12 8 9 0.0 0.0 0.02 0.M.12 9 0.5 250 250 20 20 250 250 50 20 20 250 250 362 004 038 10A 10B 115 004 038 10A 10B See Note [6] See Note [6] 363 See Note [6] See Note [6] 364 004 005 Vertical Acceleration Vertical Acceleration g g 4 4 12 12 0. A Bit 12-Chan.0 2.01 356 03D N2 Vibration Scalar 5. B See ARINC 429P2 See Att.125 1.063 0.0 1.001 10 10 20 20 .0 31.00 0. A Bit 12-Chan.+105 -5 .+105 32768 32768 5.063 0.063 0. DFN/%N1 DFN/%N1 g g % N1/Deg % N1/Deg Knots g g LBF LBF ±16 ±16 16 131072 131072 131072 ±180 2000 2000 4 4 12 12 ±8192 4 4 64000 64000 9/9 9/9 13 20 18 20 9 11 11 12 12 11 11 13 12 12 11 11 1. TLA Range Rate Cross Track Acceleration Cross Track Acceleration Corrected Thrust Corrected Thrust Scalar 5.3 100 100 361 004 005 038 03D 10A 10B 20 20 20 40 40 40 Bit 11-Chan. A Bit 12-Chan.3 31.063 2 8 0.00195 0.0 1.01 Notes % % % N1Nom % RPM Lbs/Hr % % Lbs/Hr Lbs/Hr Scalar Scalar 100 200 355 03D N2 Vibration Scalar 5.0 10 25 10 20 50 20 Bit 11-Chan. N1 Derivative of Thrust vs.01 Deg/Sec Deg/Sec N.12 5. A Bit 12-Chan. A Bit 12-Chan. A Bit 12-Chan. PART 1 .5 62.12 9 0.001 0. Feet Feet Feet Deg.008 1.01 357 360 03D 002 004 005 038 03D 056 060 10A 10B 142 BB Vibration Flight Information Potential Vertical Speed Potential Vertical Speed Potential Vertical Speed N1 Rotor Imbalance Angle Flight Information Flight Information Throttle Rate of Change Throttle Rate of Change RAIM Status Word Altitude (Inertial) Altitude (Inertial) Altitude (Inertial) LPT Rotor Imbalance Angle (737 only) Derivative of Thrust vs. TLA Derivative of N1 vs.0 1.5 10 10 62. 32768 32768 32768 ±180 15 15 15 9 1.0 2.001 0.001 64. B Bit 11-Chan.001 0.015 0. B See Attachment 6 See Attachment 6 See Notes [6] & [7] See Notes [6] & [7] Max Transport Delay (msec) 3 Parameter Name Selected Actual Fan Speed Selected Actual Fan Speed N1 Speed Actual N1 Fuel Flow (Engine) LPT Clearance Valve Position LPT Clearance Valve Position Fuel Flow Fuel Flow Vibration N1 Vibration FQIS Tank ID Units Range (Scale) 128 128 256 256 32768 -5 .5 62.5 50 10 10 62.125 0. B See Attachment 6 Ft/Min Ft/Min Ft/Min Deg. B Bit 11-Chan.BNR DATA Eqpt Label ID (Hex) 10A 10B 13A 0D0 347 029 10A 10B 13A 0D0 353 0D0 354 03D 04D Min Transit Interval (msec) 2 31.00 1.008 0.001 0.3 25 Max Transit Interval (msec) 2 100 100 50 SDI 1 = L/SDI 2 = R 50 500 500 50 100 1000 1000 100 SDI 1 = L/SDI 2 = R SDI 1 = L/SDI 2 = R Bit 11-Chan.

ARINC SPECIFICATION 429. PART 1 .05 0.53E-5 50 Hz 10 150 50 Hz 110 Hz 20 250 110 Hz See ARINC 743 373 374 375 376 .+105 4 4 16 4 -5 .004 1.+105 -5 .063 1.063 0.063 0.125 0.+105 -5 . Word B Deg/180 % % Knots % % Knots % % Gs g VDC Gs % % ±180 128 128 4096 128 128 4096 -5 .063 0.125 Notes % N1Nom g Ft/Min Ft/Min % N1Nom Ft/Min Knots Deg/180 Knots Knots Deg/180 Knots 9 9 Feet Feet Feet 366 367 370 371 372 X X X Gen Aviation Equip.53E-5 0.125 0.125 0.125 0.001 1.+105 9 12 12 15 12 12 15 11 11 18 12 12 18 11 11 0.063 50 500 500 100 500 500 100 500 500 50 Hz 10 150 50 Hz 500 500 100 1000 1000 200 1000 1000 200 1000 1000 110 Hz 20 250 110 Hz 1000 1000 See ARINC 743 Gs g VDC Gs 4 4 16 4 18 12 12 18 1.001 0.BNR DATA Eqpt Label ID (Hex) 13A 038 365 004 005 13A 038 004 13A 038 004 13A 038 004 005 00B 025 0C5 Min Transit Interval (msec) 2 100 10 20 20 100 20 50 100 50 100 100 100 100 100 100 100 Max Transit Interval (msec) 2 200 20 40 40 200 40 100 200 100 200 200 200 200 200 1200 200 200 110 110 Max Transport Delay (msec) 3 Parameter Name N1 APR Rating Vertical Acceleration Inertial Vertical Velocity (EFI) Inertial Vertical Velocity (EFI) N1 Max Reverse Inertial Vertical Velocity (EFI) North-South Velocity IGV Position North-South Velocity East-West Velocity IGV Request East-West Velocity g g GNSS Height WGS-84 (HAE) Decision Height Selected (EFI) Decision Height Selected (EFI) Units Range (Scale) 256 4 32768 32768 256 32768 4096 ±180 4096 4096 ±180 4096 8 8 ± 131.001 0.072 8192 16384 Sig Pos Resolution Bits Sense 14 12 15 15 14 15 15 12 15 15 12 15 13 13 20 16 17 UP UP 0.05 0.125 0.35 0. Word A Cross Heading Acceleration Cross Heading Acceleration Spare DC2 Cross Heading Acceleration GPS Differential Correction. Identifier 005 10A 10B 005 10A 10B 005 10A 10B 004 005 033 038 10A 10B XXX 004 005 033 038 XXX Wind Direction-Magnetic Actual Fan Speed Actual Fan Speed North-South Velocity-Magnetic Actual Core Speed Actual Core Speed East-West Velocity-Magnetic Left Thrust Reverser Position Left Thrust Reverser Position Along Heading Acceleration Along Heading Acceleration Spare DC1 Along Heading Acceleration Right Thrust Reverser Position Right Thrust Reverser Position GPS Differential Correction.015 0.125 0.063 0.063 0.53E-5 0.001 0.015 1.063 0.0 0.001 0.Page 74 ATTACHMENT 2 DATA STANDARDS TABLE 2 .125 0.125 0.004 1.0 1.53E-5 0.0 0.

each of those words is considered a unique item of information.6. When heavy bus loading dictates a shift from the center of the range. the weight of the most significant bit of the twos complement fractional notation binary word will be one half this value. the definition of transport delay will differ depending on the application. The guidance given in this document for transmit intervals should be applied to those words as if each word were identified by a different label. 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.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. Transmit intervals and the number of parameters to be transmitted are prime factors in bus loading.6 of this document. The way in which these parameters are encoded is also explained in the Commentary following Section 2. However.Page 75 ATTACHMENT 2 DATA STANDARDS TABLE 2 . In the case of a system involving filtering.ARINC SPECIFICATION 429.1.1 and 2. When words with like labels and with different SDI codes are transmitted. These labels can provide data in a degraded accuracy mode. PART 1 . 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. a sample is complete when the 32-bit word constituting the output data is complete. a considerable portion of existing equipment use the other (nonparenthesized) values. There can be situations in which it is necessary to define which portions of an equipment are included in the transport delay term.1.5. COMMENTARY Since the nature of the data varies. transport delay is the phase slope of the transfer function across the frequency band of interest. the shift should be toward the maximum transmit interval.1. [4] c-7 [5] [6] [7] c-12 The values shown in parentheses are the preferred data standards for stator vane angle. The numbers entered in the RANGE column for angular parameters are the actual degree ranges required. Optionally transmitted. See Section 2. Users should verify the data standards of the equipment they are or will be using.2. Such definitions should appear in individual equipment Characteristics when needed. In the case of a sampling system.5. Binary packed word consisting of: Word 1 = Bits 11-19 (Range = 16) Word 2 = Bits 20-28 (Range = 16) [2] c-4 c-5 c-4 . [3] Maximum transport delay is the worst case total delay between an input function and the output response.1. As explained in the Commentary following Section 2.

5 AC VOLTS +2.ARINC SPECIFICATION 429.5 -10 -9 -11 -13 HI NULL LO HI NULL RCVR INPUT STATES LO XMTR OUTPUT STATES c-4 c-4 .5 -0.5 -2.5 V AB +0.Page 76 ATTACHMENT 3 VOLTAGE LEVELS A B G XMTR RCVR A B G +13 +10 +11 +9 +6.5 -6. PART 1 .

NOTES: * Includes aircraft interwiring ** Shields to be grounded in aircraft at both ends of all “breaks”.2.000 ohms 1.000 to 30. c-16 This drawing describes total system characteristics rather than individual component parameters. PART 1 .000 pF Not defined but unbalance due to aircraft interwiring should be held to a minimum UTILIZATION DEVICE STANDARDS RI > 12.ARINC SPECIFICATION 429. .2.Page 77 ATTACHMENT 4 INPUT/OUTPUT CIRCUIT STANDARDS TRANSMITTING UNIT +E /2 o R s /2 Eo -E /2 o R /2 s OUTPUT CAPABILITY UTILIZATION DEVICE ** ** C H R I C R H c-4 I R ** TOTAL SYSTEM ** ** OTHER DEVICES C G G OUTPUT (SYSTEM) CAPABILITY c-4 Total System *Resistance Total System *Capacitance System Capacitance Unbalance 400 to 8.000 ohms CH and CG < 50 pF The total differential input impedance of the receiver should be limited to the values specified in Section 2.4.000 ohms CI < 50 pF RH or RG > 12.

5 seven-unit code set is reproduced in the table below with the BCD subset outlined in column 3: STANDARD CODE BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 Column 0 0 0 0 Row 0 0 1 1 0 1 0 2 0 1 1 3 1 0 0 4 1 0 1 5 1 1 0 6 1 1 1 7 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 NUL SOH STX ETX EOT ENQ ACK BEL BS HT LF VT FF CR SO SI DLE DC1 DC2 DC3 DC4 NAK SYN ETB CAN EM SUB ESC FS GS RS US SP ! " # $ % & ′ ( ) * + ´ • / 0 1 2 3 4 5 6 7 8 9 : . PART 1 .ARINC SPECIFICATION 429.Page 78 ATTACHMENT 5 INTERNATIONAL STANDARDS ORGANIZATION CODE #5 The ISO Alphabet No. . < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ∧  ! a b c d e f g h i j k l m n o p q r s t u v w x y z {  } ~ DEL NOTE: b8 is used as a parity bit.

1. . 357) 1 Alpha Numeric (ISO Alphabet No.e. 1/8 x 4096 where 4096 is entry in range column of Table 2.ARINC SPECIFICATION 429. 5) Message – Initial Word Format P 32 31 SSM (01) 30 29 “STX” 23 22 SPARES (Zeroes) 17 16 WORD COUNT BNR EQUIV. 9 8 LABEL (356) 1 Alpha Numeric (ISO Alphabet No. PART 1 . 2) 0 1 0 Example: 1 0 1 1 1 N-S VELOCITY (366) 1 BNR Word Format Example (No Discretes) TABLE 6-3 P 32 31 SSM (01) 30 29 “STX” 23 22 UNIT ADDRESS 17 16 WORD COUNT BNR EQUIV.Page 79 ATTACHMENT 6 GENERAL WORD FORMATS AND ENCODING EXAMPLE 6. 357) 1 Alpha Numeric (ISO Alphabet No. 5) Data – Final Word Format (Taken together. 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 P SSM DATA PAD DISCRETES SDI [5] [4] MSB [3] [2] LSB [1] 8 7 6 5 4 3 LABEL 2 1 Generalized BCD Word Format TABLE 6-1-1 P SSM 0 0 0 Example BCD CH #2 BCD CH #2 4 2 1 8 4 2 1 0 1 0 0 1 0 1 2 5 8 0 BCD CH #3 4 2 1 1 1 1 7 8 1 BCD CH #4 4 2 1 0 0 0 8 8 0 BCD CH #5 4 2 1 1 1 0 6 SDI 0 0 8 1 7 6 5 4 3 2 1 1 0 0 0 0 0 0 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 P SSM DATA PAD DISCRETES SDI [5] [4] MSB [3] [2] LSB [1] 8 7 6 5 4 3 LABEL 2 1 Generalized BNR Word Format TABLE 6-2-1 P 31 30 SSM 29 PAD 11 SDI 0 0 1 8 7 6 5 4 3 LABEL 2 1 1/2 1/4 1/8 1/16 1/32 1/64 1/128 etc 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 512 Knots (i. 5) Data – Intermediate Word Format P 32 31 SSM (10) 30 29 “DATA CH #3” (BNR ZEROES) 23 22 DATA CH #2 A 16 15 DATA CH #1 H 9 8 LABEL (356.. the following example shows encoding of the word ALPHA into three successive data words). 5) Maintenance Data –Initial Word Format c-4 P 32 31 SSM (00) 30 29 “DATA CH #3” P 23 22 DATA CH #2 L 16 15 DATA CH #1 A 9 8 LABEL (356. 9 8 LABEL (357) 1 Alpha Numeric (ISO Alphabet No. Att.

11 takes on the binary state “one” to annunciate that the ILS receiver is in the “tune inhibit” condition.7 of ARINC 709) ** Bit No. PART 1 .ARINC SPECIFICATION 429.Page 80 ATTACHMENT 6 GENERAL WORD FORMATS AND ENCODING EXAMPLES TABLE 6-4 P 32 31 SSM (00) 30 29 MSB DISCRETES [2] SDI LSB 11 10 9 8 LABEL (See Below) 1 LABEL 155 – 161 270 – 276 350 – 354 USAGE SUBGROUP Maintenance Discretes Maintenance Discrete Word Format c-4 TABLE 6-5 P 32 31 SSM (01) ACKNOWLEDGEMENT (FORMAT NOT DEFINED) 30 29 WORD COUNT 17 16 BNR EQUIV. 8 7 6 5 4 3 LABEL (202) 0 0 0 2 1 c-6 0 1 0 1 0 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 P SSM DATE A FLIGHT PAD SDI Day Month R LEG [3] [1] I x10 x10 x1 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 Example 2 3 0 8 5 8 7 6 5 4 3 2 1 LABEL (260) 0 0 0 0 0 1 6 1 0 2 1 Date/Flight Leg Word . 12 is set to “1” when data is for a foreground station in frequency scanning mode. 9 8 LABEL (355) 1 Acknowledgement Word – Initial Word Format TABLE 6-5-1 P 32 31 SSM (00) 30 29 ACKNOWLEDGEMENT (FORMAT NOT DEFINED) 9 8 LABEL (355) 1 Acknowledgement Word – Intermediate Word Format TABLE 6-5-2 P 32 31 SSM (10) 30 29 ACKNOWLEDGEMENT (FORMAT NOT DEFINED) 9 8 LABEL (355) 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 P SSM DATA PADS * SDI [5] [4] [3] [1] * Bit No. 7 6 5 4 3 LABEL (173/174) 2 1 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 P SSM DATA FIELD ** * SDI [5] [4] [1] * Bit No. 11 is assigned to a memory on/off annunciation function (see Section 4.

a functional test should not be performed.ARINC SPECIFICATION 429. bit 11 should be encoded as “0”.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 P SSM FLIGHT NUMBER A x1000 x100 x10 x1 PAD SDI R 8 4 2 1 8 4 2 1 8 4 2 1 8 4 2 1 I T 0 0 0 0 0 0 0 0 0 1 0 0 0 1 0 1 1 1 0 0 0 0 0 Y Example 0 1 1 7 8 7 6 5 4 3 2 1 LABEL (261) 1 0 1 0 0 1 6 1 0 2 1 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 P [5] SSM [4] MSB DATA LSB PAD [3] [6] 9 8 7 6 5 4 3 2 1 SDI [1] LABEL (222) [6] Marker Beacon Output Discrete Bits Discrete 400 Hz 1300 Hz 3000 Hz Bit 11 12 13 Bit State Discrete Grounded Discrete Open 1 0 1 0 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 P SSM LEVER SDI MSB DATA LSB PAD [5] [4] POSITION [1] 8 7 6 5 4 3 LABEL (127/137) 2 1 Lever c-4 Position 1 (Cruise) Position 2 Position 3 Position 4 Position 5 (Landing) 11 1 0 0 0 0 12 0 1 0 0 0 Bit 13 0 0 1 0 0 14 0 0 0 1 0 15 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 P SSM HOURS MINUTES SECONDS * SDI [5] [4] 0-24 0-60 0-60 *Bit 11 of label 150 should be encoded with a “1” when the GNSS system clock is being used as the source of time. 6 5 4 3 LABEL (150) 2 1 c-16 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 P SSM SDI [5] [4] DATA PAD FTI [1] 8 7 5 4 3 LABEL (164) 1 0 1 1 6 6 2 1 c-4 Note: When Bit 11 (Functional Test Inhibit) is a “1”. 0 0 4 1 1 0 Radio Height Word . PART 1 . Otherwise.

5 of this document describes the functions of the sign/status matrix and the ways in which the bits constituting it are encoded.1.3.3. [5] Parity Bit This bit is encoded to render word parity odd.ARINC SPECIFICATION 429.1. Section 2.1. unused bits in a word may be assigned to discrete functions. . unused bit positions should be occupied by binary zero or valid data pad bits. Bit #11 of the word should be the first to be so assigned.2 of this document refers. one bit per variable. PART 1 . followed by bit #12 and so on.2 of this document. When the SDI function is not required.4 of this document refers.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 P SSM DOCUMENTARY DATA PAD SDI 4 2 1 4 2 1 4 2 1 4 2 1 4 2 1 4 2 1 [5] [4] [1] Code 1 Code 2 Code 3 Code 4 Code 5 Code 6 8 7 5 4 3 LABEL (262) 0 0 1 1 6 2 1 0 1 0 1 Documentary Data Word [1] Source/Destination Identifier (SDI) Field The purpose of the SDI field is explained in Section 2. Section 2. as are also the limitations on its use. [3] Pad All bit positions not used for data or discrete should be filled with binary zero or valid data pad bits.1. until the data field is reached. in ascending numerical order. In the absence of discretes. this field may be occupied by binary zero or valid data pad bits. [4] Sign/Status Matrix (SSM) Section 2.4 of this document. [2] Discretes As discussed in Section 2.

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 P 1 SSM 0 0 0 PAD 0 0 0 3rd Digit 1 6 1 0 0 2nd Digit 1 4 0 0 1 LSD 0 9 0 1 0 PAD 0 0 0 0 9 0 8 0 7 1 6 6 1 5 0 4 0 4 3 1 2 0 0 1 0 SDI LABEL (046) Example 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 P 0 SSM 0 0 0 PAD 0 0 0 MSD 0 0 0 0 0 5 Digit 0 3 1 1 0 th 9 0 8 1 7 1 7 6 1 5 0 4 0 4 3 1 2 0 0 1 0 4 Digit 0 2 1 0 0 th PAD 0 0 0 SDI 0 LABEL (047) Example 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 P SSM 1 1 0 0 0 SPARE 0 0 0 0 0 MSD 0 1 0 1 0 0 0 0 0 1 LSD 1 D 0 1 1 0 9 0 8 1 7 1 7 6 1 5 1 4 1 7 3 1 2 1 3 1 1 SDI LABEL (377) c-11 Equipment Identifier Word (Example provided for 10D code) .ARINC SPECIFICATION 429.

ARINC SPECIFICATION 429. Resolution 4 8 16 25 10 100 Altitude (Variable Reduction) . 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 P A R I T Y Example 2 3 0 8 8 5 0 6 2 0 0 x10 2 1 1 0 8 0 4 0 SSM Day x1 2 1 1 1 x10 1 0 8 1 4 0 DATE Month x1 2 0 1 0 8 1 x10 4 0 2 0 1 0 8 0 4 1 Year x1 2 0 1 1 0 0 0 0 0 9 8 7 6 5 4 3 2 1 SDI LABEL (260 031) Chronometer Output Only 0 1 1 0 1 TABLE 6-19 32 31 30 29 28 P SSM (00) MSB LSB MSB D 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 PRIMARY COUNTER 0-4096 FLIGHT LEGS 4096-65535 LEGS LSB PAD SDI 8 7 6 5 4 3 2 1 LABEL (251 01A) 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 P SSM (00) MSB ALTITUDE SEE LSB BELOW SDI 8 7 6 5 4 3 2 1 LABEL (206 018) Transponder Bits 13 0 0 0 0 1 1 12 0 0 1 1 0 0 11 0 1 0 1 0 1 Range 65536 65536 65536 51200 81920 51200 Bits Used 15 14 13 12 14 10 App.

Note 2: Intruder Sensitivity Level Status 18 0 0 0 0 1 1 1 1 Bits 17 16 0 0 0 1 1 0 1 1 0 0 0 1 1 0 1 1 Meaning Not Reported SL = 1 SL = 2 SL = 3 SL = 4 SL = 5 SL = 6 SL = 7 Note 3: Maximum range is 127-15/16 nautical miles.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 P 0 SSM [5] 1 1 0 MSB 5. Note 5: Sign Status Matrix (SSM) [BNR] Bits 31 0 0 1 1 30 0 1 0 1 Meaning Failure Warning No Computed Data Functional Data Normal Operation .25 NM 0 0 0 1 0 1 0 1 INTRUDER RANGE [3] [4] 0 0 LSB 0 MSB 2 18 17 16 15 14 13 12 11 10 9 INTRUDER NUMBER [1] 0 MSB 5 0 1 0 1 LSB 0 0 0 LSB 0 3 1 0 0 1 SDI 8 7 6 5 4 LABEL (130) 1 0 1 0 MSB 3 2 1 INTRUDER SENSE LVL[2] 1 0 LSB Note 1: Maximum number of intruders is 31.ARINC SPECIFICATION 429. PART 1 . Note 4: Intruder range may be reported in the form of horizontal range when intruder is available.

V.S. Note 5: Sign Status Matrix (SSM) [BNR] Bits 31 0 0 1 1 30 0 1 0 1 Meaning Failure Warning No Computed Data Functional Data Normal Operation .ARINC SPECIFICATION 429.12700 Ft. See Note 5. 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 P 0 SSM [5] [4] 1 1 0 0 0 1 1 0 0 S MSB 2500 FT RELATIVE ALTITUDE [3] 1 0 LSB LEVEL 21 20 [2] 0 0 19 18 17 16 15 14 13 12 11 10 FUTURE SPARE 0 0 0 0 MSB 5 INTRUDER NUMBER 0 1 [1] 0 1 LSB 0 0 1 LSB 1 3 0 0 1 SDI 9 8 7 6 5 4 (131) 1 0 1 1 0 MSB 3 2 1 I. Note 4: The No Computed Data Report of the SSM field applies to relative altitude (Bits 29-22) only. LABEL Note 1: Maximum number of intruders is 31. Two’s Complement Range = +/. Note 2: Sense of Intruders VERTICAL RATE (Z SINT) Bits 21 0 0 1 1 20 0 1 0 1 Meaning No Vertical Rate (Level Flight) Climbing Descending No Data Note 3: Binary.

See Note 5. Note 5: Sign Status Matrix (SSM) [BNR] Bits 31 0 0 1 1 30 0 1 0 1 Meaning Failure Warning No Computed Data Functional Data Normal Operation . Range = -180 to +180 Degrees Note 4: The No Computed Data report in the SSM field applies to bearing information (Bits 29-19) only.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 BEARING DISPLAY INTRUDER P SSM SDI MATRIX NUMBER [3] [2] [1] [5] [4] 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 LSB 0 0 S MSB LSB MSB LSB MSB NO THREAT 8 7 6 5 4 3 2 1 LABEL (132) 0 LSB 2 3 1 0 1 1 0 1 1 0 MSB Note 1: Maximum number of intruders is 31. Note 2: Display Matrix 18 0 0 0 0 1 1 1 1 Bits 17 16 0 0 0 1 1 0 1 1 0 0 0 1 1 0 1 1 Meaning No Threat Traffic Advisory Resolution Advisory Proximate Traffic Not Used Not Used Not Used Not Used Note 3: Binary.ARINC SPECIFICATION 429. Fractional Binary. PART 1 .

2 of this Document. Note 1: Altitude Resolution Bits 11 0 1 Meaning 1 Ft 100 Ft Note 2: Sign Status Matrix (SSM) [BNR] 31 0 0 1 1 Bits 30 0 1 0 1 Meaning Failure Warning No Computed Data Functional Data Normal Operation .1. PART 1 .ARINC SPECIFICATION 429.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 P SSM S ALTITUDE ALT PAD [2] [1] 0 1 1 0 0 0 MSB 1 0 1 0 0 1 0 21059 0 1 0 0 0 0 1 1 LSB 0 1 0 0 8 7 6 5 4 3 LABEL (203) 0 0 0 0 2 1 1 1 LSB 3 0 0 1 MSB 2 S = Sign Bit see Section 2.5.

Page 89 ATTACHMENT 6 GENERAL WORD FORMATS AND ENCODING EXAMPLE 2.2.5 Hr. C [2] Baroset (ins Hg) 29.5 Deg.1.1.4 NM Time To Go +145. DME Distance 257. Selected Course 154 Deg.86 NM True Airspeed 565 Knots Total Air Temp.5 Ft.05 Selected N1 2750 RPM Selected Mach 0.6 NM Ground Speed 650 Knots Track Angle (True) 165. . Because of the actual maximum value of the most significant character of these quantities exceeds 7. Cross Track Distance 225.ARINC SPECIFICATION 429. Decision Height Selected 200 Ft.92 ins Hg (001) 1 (002) 0 (003) 1 (012) 1 (013) 1 (020) 0 (021) 0 (021) 1 (022) 0 (023) 1 (024) 1 (025) 0 (026) 0 (125) 1 (165) 0 (170) 0 (201) 0 (230) 0 (231) 0 (232) 1 (233) 1 (235) 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 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 MSC 4 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 1 0 0 0 0 2 1 0 1 0 0 1 1 1 0 0 1 0 0 0 1 1 1 0 0 0 0 1 1 0 1 0 0 1 0 0 0 0 1 0 0 0 1 0 0 0 1 0 1 0 0 8 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 4 1 1 0 1 1 0 0 1 0 1 1 0 0 1 1 0 1 1 0 1 0 0 2 1 0 1 1 1 1 0 1 0 1 0 0 1 0 0 0 0 1 1 0 0 0 1 1 0 0 0 0 0 0 1 0 1 1 1 0 1 0 0 1 0 0 1 1 1 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 4 1 1 1 1 1 0 1 1 1 1 1 0 0 1 1 0 1 1 1 0 0 0 2 0 0 0 0 0 0 0 0 0 1 0 0 1 0 0 0 1 0 0 1 1 0 1 1 1 1 1 1 0 1 1 1 1 0 0 1 0 1 0 1 1 1 0 1 1 8 0 0 0 0 0 0 P 0 0 P P 0 P 0 0 P 1 P P 0 P 0 4 0 0 1 0 1 0 P 0 0 P P 0 P 1 0 P 0 P P 1 P 0 2 0 1 1 0 0 0 P 0 0 P P 0 P 0 0 P 0 P P 0 P 1 1 0 1 0 0 1 0 P 0 0 P P 0 P 1 0 P 0 P P 1 P 0 8 0 P P P P P P P P P P 0 P 0 0 P 0 P P 0 P P 4 1 P P P P P P P P P P 0 P 1 1 P 1 P P 0 P P 2 0 P P P P P P P P P P 0 P 0 0 P 1 P P 0 P P DATA FIELD [1] LSC 1 0 1 2 4 1 2 4 1 2 0 0 1 0 0 0 0 0 0 0 SDI LABEL P 0 0 0 1 0 0 0 0 0 0 P 0 0 1 1 0 0 0 0 0 0 P 0 0 0 1 01 0 0 0 0 P 0 0 1 1 0 1 0 0 0 0 P 0 0 0 0 0 0 1 0 0 0 P 0 0 1 0 0 0 1 0 0 0 P 0 0 1 0 0 0 1 0 0 0 P 0 0 0 1 0 0 1 0 0 0 P 0 0 1 1 0 0 1 0 0 0 P 0 0 0 0 1 0 1 0 0 0 0 0 1 0 1 0 1 0 0 0 P 0 0 0 1 1 0 1 0 0 0 1 1 0 0 1 0 1 0 1 0 1 0 0 0 1 0 1 0 1 1 1 0 P 0 0 0 0 0 1 1 1 1 0 0 0 0 1 0 0 0 0 0 0 1 P 0 0 0 0 0 1 1 0 0 1 P 0 0 1 0 0 1 1 0 0 1 0 0 0 0 1 0 1 1 0 0 1 P 0 0 1 1 0 1 1 0 0 1 P 0 0 1 0 1 1 1 0 0 1 NOTES: [1] [2] “P” denotes pad “zero” or valid data. PART 1 . C [2] Altitude Rate -15250 Ft/Min Static Air Temp. Radio Height 2450. For this reason. Note possible use of pad bits for discrete functions per Section 2. it cannot be encoded in the most significant character position of the BCD word. -025 Deg. +013 Deg. Encoding Examples Table 6-25 BCD DATA ENCODING EXAMPLES Bit No.3 Min.3. Selected Vertical Speed -2200 Ft/Min Selected EPR 2.850 Mach Selected Heading 177 Deg. Selected Airspeed 423 Knots Universal Time Constant 1545.2. PARAMETER (Label) Distance To Go +2750. see Section 2. Selected Altitude 41000 Ft. 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.

) .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 c-4 (See Commentary following Section 2.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) W 169 Deg 25. PART 1 .Page 90 ATTACHMENT 6 GENERAL WORD FORMATS AND ENCODING EXAMPLES Table 6-25-1 BCD ENCODING OF LATITUDE AND LONGITUDE Bit No. PARAMETER (Label) 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 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.2 of this document for further information.) N 75 Deg 59.ARINC SPECIFICATION 429.1.

PART 1 . DC-10 SPARES DATA LABEL REF. 512 MSB 256 128 64 32 16 8 4 2 1 LSB SPARE SPARE DIFF.ARINC SPECIFICATION 429. ARINC OCT.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. 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 0 0 1 0 1 1 0 0 1 0 0 1 1 0 1 1 0 0 1 0 0 0 1 1 1 1 0 0 1 0 0 1 1 1 1 1 0 0 1 0 1 0 1 0 1 1 0 0 1 0 1 1 1 0 1 1 0 0 1 0 1 0 1 1 1 1 0 0 1 0 1 1 1 1 1 1 0 0 1 0 0 0 0 0 1 1 0 0 1 0 0 0 0 1 1 1 0 0 1 0 0 1 0 0 1 1 0 0 1 0 1 0 0 0 1 1 0 0 1 0 1 1 0 0 1 1 0 0 1 0 0 1 0 1 1 1 0 0 1 0 1 0 0 1 1 1 0 0 1 0 1 1 0 1 1 1 0 0 1 0 115 115 117 117 115 115 117 117 114 116 114 114 114 116 116 116 BITS 10 9 747 NOSE (064) NL LO (061) 1 00 3 10 11 01 4 LI (060) 5 00 7 10 11 01 8 10 6 00 11 11 RI (062) 9 01 12 10 10 2 00 15 11 00 01 NR RO (063) 13 01 16 10 14 00 5 11 LO (061) 1 01 6 2 DC-10 NOSE (064) NL 00 NR RO (063) 3 00 7 LI (060) RI (062) 1 0 9 00 00 10 11 01 8 4 01 01 . LOW THRESHOLD LOW WHEEL FAULT SYSTEM FAULT WHEEL LABEL 1 2 13 14 3 4 15 16 5 9 6 7 8 10 11 12 1 2 3 4 5 6 7 8 9 10 PARITY BNR BCD Wheel 747 Nos.

ARINC SPECIFICATION 429. WARM HOT BRAKE FAULT SYSTEM WHEEL LABEL Bit Nos. PARITY BNR BCD Wheel 747 Nos. DC-10 SPARES DATA LABEL REF.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 512 MSB 256 128 64 32 16 8 4 2 1 LSB PREDICT DIFF.TEMP. PART 1 . ARINC OCT. 1 2 13 14 3 4 15 16 5 9 6 7 8 10 11 12 1 2 3 4 5 6 7 8 9 10 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 0 0 1 0 1 1 0 0 0 0 0 1 1 0 1 1 0 0 1 0 0 0 1 1 1 1 0 0 1 0 0 1 1 1 1 1 0 0 1 0 1 0 1 0 1 1 0 0 1 0 1 1 1 0 1 1 0 0 1 0 1 0 1 1 1 1 0 0 1 0 1 1 1 1 1 1 0 0 1 0 0 0 0 0 1 1 0 0 1 0 0 0 0 1 1 1 0 0 1 0 0 1 0 0 1 1 0 0 1 0 1 0 0 0 1 1 0 0 1 0 1 1 0 0 1 1 0 0 1 0 0 1 0 1 1 1 0 0 1 0 1 0 0 1 1 1 0 0 1 0 1 1 0 1 1 1 0 0 1 0 115 115 117 117 115 115 117 117 114 116 114 114 114 116 116 116 BITS 10 9 747 LO (115) 1 00 3 10 11 01 4 LI (114) 5 00 7 10 11 01 8 10 6 00 11 11 RI (116) 9 01 12 01 01 10 00 10 2 00 15 11 RO (117) 13 01 16 10 14 00 5 11 LO (115) 1 01 6 LI (114) RI (116) 1 0 9 00 10 2 00 7 11 RO (117) 3 01 8 4 .

Flight Director Pitch -10 Deg.86 NM Altitude (29. Arc minutes and seconds are encoded as decimal degrees. N 81. [2] Fast/Slow +15 Knots UTC (18:57:20) Radio Height 2450 Ft. . Angles in the range 180o to 360o are subtracted from 360o and the resulting number encoded as a negative value per note 2.ARINC SPECIFICATION 429. [3] Cross Track Distance 51.5 Deg Present Pos. C Total Air Temp -25 Deg. Angles in the range 0 to 180o are encoded as positive numbers.0 NM Vertical Deviation 600 Ft. Selected Airspeed 423.125 DDM [2] DME Distance 257.2.1.0 Knots Selected Vertical Speed -2200 Ft/Min [2] Selected Mach 800 m Mach Desired Track 275 Deg.50 g 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 P SSM DATA FIELD [1] SDI 1 2 4 1 2 4 1 2 (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 (101) 0 (102) 1 (103) 0 (104) 1 (106) 1 (114) 0 (116) 1 (117) 0 (140) 1 (141) 1 (142) 0 (150) 0 (164) 0 (173) 1 (174) 1 (202) 0 (203) 0 (205) 0 (206) 1 (210) 0 (213) 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 1 0 1 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 1 1 0 1 0 0 1 1 1 1 0 1 0 0 0 1 0 1 0 0 1 1 0 0 0 0 0 1 1 0 0 0 1 1 0 1 1 0 0 1 1 0 1 1 0 1 0 1 0 1 0 1 1 0 1 0 1 1 0 0 0 1 0 0 1 0 1 0 1 1 1 0 0 0 0 0 0 1 1 0 0 1 0 1 1 1 1 1 0 1 1 1 0 0 0 0 1 1 1 0 0 1 0 1 1 0 0 0 1 0 1 1 0 0 0 0 0 1 0 0 0 1 1 0 1 0 1 1 1 0 0 0 1 0 0 0 1 0 0 1 0 1 0 0 1 0 1 1 0 0 0 0 1 1 1 0 0 1 1 0 1 1 0 0 0 0 0 0 0 0 1 0 1 1 1 1 1 0 0 1 0 0 0 0 1 0 1 1 1 1 0 1 0 0 0 1 0 1 1 0 1 0 1 0 1 0 1 0 1 0 0 1 0 0 0 0 1 0 1 1 0 0 0 0 1 1 0 0 0 0 1 1 0 0 1 1 0 1 1 0 0 1 1 1 1 1 0 1 0 1 0 0 0 0 0 0 0 0 1 0 0 0 0 0 1 1 0 1 0 0 0 1 1 1 0 1 0 1 0 P 0 1 0 0 1 0 0 1 0 0 0 1 1 0 0 1 0 0 1 1 1 1 0 1 0 P P 0 0 0 P 1 0 0 0 1 0 0 0 0 0 0 0 P P P 0 0 0 1 P 1 P P P P 0 P P P P 1 0 P P 1 0 1 0 0 P P P 1 1 0 0 P P 0 P P P P 0 P P P P 0 0 P P 1 1 0 0 0 P P P 0 1 0 0 0 P P P P 0 P P P P 1 0 P P 1 0 0 P 0 P P P 1 0 0 P P 0 P P P P P P P P P 0 0 P P 0 0 0 P P P P P 0 0 P P P P P P P P P P P P P 0 P P P P 0 P P P P P P 1 0 P P P 0 0 1 0 0 0 0 0 1 0 P 0 0 0 1 0 0 0 0 1 0 P 0 0 1 1 0 0 0 0 1 0 P 0 0 0 01 0 0 0 1 0 P 0 0 0 1 1 0 0 0 1 0 P 0 0 0 0 1 1 0 0 1 0 P 0 0 0 1 1 1 0 0 1 0 P 0 0 1 1 1 1 0 0 1 0 P 0 0 0 0 0 0 0 1 1 0 P 0 0 1 0 0 0 0 1 1 0 P 0 0 0 1 0 0 0 1 1 0 0 0 0 0 0 0 0 1 0 1 1 0 0 0 0 0 1 0 1 1 1 0 P 0 0 1 1 0 1 1 1 1 0 P 0 0 0 0 1 1 1 1 1 0 0 0 0 0 1 0 0 0 0 0 1 P 0 0 1 1 0 0 0 0 0 1 P 0 0 1 0 1 0 0 0 0 1 P 0 0 0 1 1 0 0 0 0 1 P 0 0 0 0 0 1 0 0 0 1 P 0 0 1 1 0 1 0 0 0 1 P 0 0 1 0 0 1 0 0 0 1 P 0 0 0 10 1 0 0 0 1 0 0 0 0 0 0 0 1 0 0 1 1 0 0 1 0 0 1 0 0 1 1 (211) 0 (212) 0 (310) 1 (311) 0 (312) 1 (323) 0 P 0 0 0 1 0 1 0 0 1 1 P 0 0 1 1 0 0 1 0 1 1 NOTES: [1] [2] [3] “P” denotes pad “zero” or valid data. C [2] Altitude Rate -15250 Ft/Min [2] Present Pos. [3] Selected Heading 150 Deg.2. Flight Director Roll +30 Deg.Page 93 ATTACHMENT 6 GENERAL WORD FORMATS AND ENCODING EXAMPLE Table 6-27 BNR DATA ENCODING EXAMPLES Bit No.25 Ground Speed 650 Knots Flight Path Accel +2. Long. PART 1 . Localizer Deviation +0. W 100. Note possible use of pad bits for discrete functions per Section 2.92) 45000 Ft. [3] Selected Altitude 41000 Ft.3.1. Lat. Negative values are encoded as the two’s complements of positive values and the negative sign is annunciated in the sign/status matrix. PARAMETER (Label) Selected Course 0 Deg.021 DDM Glide Slope Deviation -0.8325 Mach Computed Airspeed 425 Knots True Airspeed 565 Knots Static Air Temp +13 Deg. Mach 0. see Section 2.

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 P Command/Control Bits 0 0 AVM Hex (Equipment) ID = 03D Hex 0 0 0 0 1 1 1 1 0 1 PADS 9 8 7 6 5 4 3 2 1 SDI 1 1 1 Label (227) 0 1 0 0 1 Bits 10 0 0 1 1 9 0 1 0 1 Meaning Engine 4 (or All Call) {not used on 757} Engine 1 (or Engine 1 and 2) Engine 2 Engine 3 (or Engine 3 and 4) Bits 31 0 0 0 0 0 0 0 0 0 0 30 0 0 0 0 0 0 0 0 0 0 29 0 0 0 0 0 0 0 0 0 1 28 0 0 0 0 0 0 0 0 1 0 27 0 0 0 0 1 1 1 1 0 0 26 0 0 1 1 0 0 1 1 0 1 25 0 1 0 1 0 1 0 1 0 0 Not Used Parameter Unit Self Test Use Accelerometer A** Use Accelerometer B** PAD Erase Fault History Erase Flight History* Read Fault History Read Flight History* 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 P SSM ORIGIN CHAR #3 ORIGIN CHAR #2 ORIGIN CHAR #1 9 8 7 6 5 4 3 2 1 OCTAL LABEL 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 P SSM DESTINATION CHAR #1 ISO #5 CHAR “SPACE” ORIGIN CHAR #4 9 8 7 6 5 4 3 2 1 OCTAL LABEL 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 P SSM DESTINATION CHAR #4 DESTINATION CHAR #3 DESTINATION CHAR #2 9 8 7 6 5 4 3 2 1 OCTAL LABEL 063 NOTE: All characters are expressed in ISO #5 format. PART 1 .ARINC SPECIFICATION 429. as defined in ARINC Specification 429. .

VOR=0) TACAN Select (TAC 1=1.ARINC SPECIFICATION 429.Page 96 ATTACHMENT 6 GENERAL WORD FORMATS AND ENCODING EXAMPLES TABLE 6-30 TACAN Control . Y=0) Mode Cont (see Table A) Pad Zero SSM (see Table B) Parity (Odd) Table A – Mode Control Bits 27 28 0 0 0 1 1 0 1 1 Description REC A/A REC T/R A/A T/R Table B – SSM Bits 31 0 1 0 1 Description Valid Functional Test No Computed Data Not Used 30 0 0 1 1 . TAC 2=0) Pad Zero BCD Units Chan Cont (LSB=17) Hex Tens Chan Cont (LSB=24) Pad Zero X/Y Mode (X=1.0 RATE 5Hz +/-10% Bit No. 1 2 3 4 5 6 7 8 9-10 11-13 14 15 16 17-20 21-24 25 26 27-28 29 30-31 32 Description 0 1 1 1 0 4 0 1 0 5 1 SDI Pad Zero VOR/TAC Select (TAC=1.Label 145 002 RANGE 126 RESOLUTION 1. PART 1 .

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
P SSM PAD ZERO CHAR #2

LSB
18 PAD ZERO

MSB
17 16 15 14 13 12 CHAR #1

LSB
11 10 9 SDI 8 7 6 5 4 3 2 1 OCTAL LABEL 233

32 31 30 29 28 27 26 25 24 23 22 21 20 19

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

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

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

Sign Matrix for BNR
Bit 31 0 30 0 1 0 1 Meaning Failure Warning No Computed data Functional Test Normal Operation

c-16

0 1 1

……………………………………………………………………………………………………………………………….. 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 P SSM PAD ZERO CHAR #2 18 PAD ZERO 18 PAD ZERO 18 PAD ZERO 18 PAD ZERO 17 16 15 14 13 12 11 10 9 SDI 8 7 6 5 4 3 2 1 CHAR #1 OCTAL LABEL 233 8 7 6 5 4 3 2 1

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

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

Label 236 EQ ID 018
32 31 30 29 28 27 26 25 24 23 22 21 20 19 P SSM PAD ZERO CHAR #8 17 16 15 14 13 12 11 10 9 SDI CHAR #7 OCTAL LABEL 236

Sign Matrix for BCD NOTE: The following information is provided in order to clarify the confusion that existed in the Industry in regards to definition of the SSM for Label 233-236. It is expected that Flight ID will be sourced from FMC EQ ID of 002. Alternative implementation may include Mode “S” XPDR EQ ID 018. In this case the user cautioned that the SSM will be BCD format. See ARINC Characteristic 718A, “Mark 4 Air Traffic Control Transponder (ATCRB/MODE S)”, Attachment 3A for more detailed information.
Bit 31 0 0 1 1 30 0 1 0 1 Meaning Valid No Computed data Functional Test Failure Warning

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 “STX” P 0 1 0 0 0 0 0 1 0 PAD ZERO BINARY WORD COUNT 0 0 0 0 0 1 1 1 9 8 7 6 5 4 3 2 1

OCTAL LABEL 360

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 P 0 0 FLIGHT NUMBER CHAR #3 FLIGHT NUMBER CHAR #2 FLIGHT NUMBER CHAR #1 9 8 7 6 5 4 3 2 1

OCTAL LABEL 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 P 0 0 FLIGHT NUMBER CHAR #6 FLIGHT NUMBER CHAR #5 FLIGHT NUMBER CHAR #4 9 8 7 6 5 4 3 2 1

OCTAL LABEL 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 P 0 0 ORIGIN CHAR #1 FLIGHT NUMBER CHAR #8 FLIGHT NUMBER CHAR #7 9 8 7 6 5 4 3 2 1

OCTAL LABEL 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 P 0 0 ORIGIN CHAR #4 ORIGIN CHAR #3 ORIGIN CHAR #2 9 8 7 6 5 4 3 2 1

OCTAL LABEL 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 P 0 0 DESTINATION CHAR #3 DESTINATION CHAR #2 DESTINATION CHAR #1 9 8 7 6 5 4 3 2 1

OCTAL LABEL 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 P 0 0 PAD ZEROS PAD ZEROS DESTINATION CHAR #4 9 8 7 6 5 4 3 2 1

OCTAL LABEL 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 SUBSYSTEM SAL MSB 8 7 6 5 4 3 2 1

P

0

SUBSYSTEM ID (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: EQPT ID: PARAMETER NAME: UNITS: RANGE (SCALE): SIGNIFICANT DIGITS: RESOLUTION: MIN TRANS INTERVAL (msec): MAX TRANS INTERVAL (msec): SOURCE DESTINATION IDENTIFIER: 241 04D FQIS System Data (See Below) (See Below) (See Below) (See Below) 500 1024 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
Word 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 Signal LEFT MAIN TANK NO. 1 LEFT MAIN TANK NO. 2 LEFT MAIN TANK NO. 3 LEFT MAIN TANK NO. 4 LEFT MAIN TANK NO. 5 LEFT MAIN TANK NO. 6 LEFT MAIN TANK NO. 7 LEFT MAIN TANK NO. 8 LEFT MAIN TANK NO. 9 LEFT MAIN TANK NO. 10 LEFT MAIN TANK NO. 11 LEFT MAIN TANK NO. 12 LEFT MAIN TANK NO. 13 LEFT MAIN TANK NO. 14 LEFT MAIN BITE CAP. NO. 1 LEFT MAIN COMPENSATOR LOAD SELECT 10,000 LOAD SELECT 1,000 LOAD SELECT 100 NO DATA TRANSMITTED DURING THIS WORD LEFT MAIN FUEL DENSITY RIGHT MAIN TANK NO. 1 RIGHT MAIN TANK NO. 2 RIGHT MAIN TANK NO. 3 RIGHT MAIN TANK NO. 4 RIGHT MAIN TANK NO. 5 RIGHT MAIN TANK NO. 6 RIGHT MAIN TANK NO. 7 RIGHT MAIN TANK NO. 8 RIGHT MAIN TANK NO. 9 RIGHT MAIN TANK NO. 10 RIGHT MAIN TANK NO. 11 RIGHT MAIN TANK NO. 12 RIGHT MAIN TANK NO. 13 RIGHT MAIN TANK NO. 14 RIGHT MAIN COMPENSATOR RIGHT MAIN BITE CAP. NO. 2 LOAD SELECT 10,000 LOAD SELECT 1,000 LOAD SELECT 100 NO DATA TRANSMITTED DURING THIS WORD RIGHT MAIN DENSITY CENTER TANK NO. 1 CENTER TANK NO. 2 CENTER TANK NO. 3 CENTER TANK NO. 4 Units pF pF pF pF pF pF pF pF pF pF pF pF pF pF pF pF Lb Lb Lb Lb/Gal pF pF pF pF pF pF pF pF pF pF pF pF pF pF pF pF Lb Lb Lb Lb/Gal pF pF pF pF Range 319.922 319.922 319.922 319.922 319.922 319.922 319.922 319.922 319.922 319.922 319.922 319.922 319.922 319.922 319.922 319.922 0-90000 0-9000 0-900 8.000 319.922 319.922 319.922 319.922 319.922 319.922 319.922 319.922 319.922 319.922 319.922 319.922 319.922 319.922 319.922 319.922 0-90000 0-9000 0-900 8.000 319.922 319.922 319.922 319.922 Sig. Dig. 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 1 1 1 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 1 1 1 12 12 12 12 12 Res .078125 .078125 .078125 .078125 .078125 .078125 .078125 .078125 .078125 .078125 .078125 .078125 .078125 .078125 .078125 .078125 10000 1000 100 .000977 .078125 .078125 .078125 .078125 .078125 .078125 .078125 .078125 .078125 .078125 .078125 .078125 .078125 .078125 .078125 .078125 10000 1000 100 .000977 .078125 .078125 .078125 .078125 Data BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BCD BCD BCD BNR (1) BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BCD BCD BCD BNR BNR BNR BNR 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)
Word 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 Signal CENTER TANK NO. 5 CENTER TANK NO. 6 CENTER TANK NO. 7 CENTER TANK NO. 8 CENTER TANK NO. 9 CENTER COMPENSATOR CENTER BITE CAP. NO. 3 NO DATA TRANSMITTED DURING THIS WORD NO DATA TRANSMITTED DURING THIS WORD NO DATA TRANSMITTED DURING THIS WORD NO DATA TRANSMITTED DURING THIS WORD NO DATA TRANSMITTED DURING THIS WORD LOAD SELECT 10,000 LOAD SELECT 1,000 LOAD SELECT 100 NO DATA TRANSMITTED DURING THIS WORD CENTER TANK DENSITY Units pF pF pF pF pF pF pF Range 319.922 319.922 319.922 319.922 319.922 319.922 319.922 Sig. Dig. 12 12 12 12 12 12 12 Res Data .078125 .078125 .078125 .078125 .078125 .078125 .078125 BNR BNR BNR BNR BNR BNR BNR

Lb Lb Lb Lb/Gal

0-90000 0-9000 0-900 8.000

1 1 1 12

10000 1000 100 .000977

BCD BCD BCD 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 9 0 1 1 0 10 0 1 0 1 Aux Center Left Right Data

FQIS (EQ ID 04D) SDI Encoding for Labels 156, 157, 160
Bits 9 0 1 0 1 10 0 0 1 1 #1 #2 #3 #4 Data

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

P

SSM

BCD CHARACTER ***

RESERVED

SDI

OCTAL LABEL 060

Bit No. 10 11 12 13

Function SDI (Indicates Sequence ID)* RESERVED (Own P/N) RESERVED (Position ID)** RESERVED (Position ID)**

1

Bit Status 0 Other P/N

Own P/N

* ** ***

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

Table 1 Bits 10 0 1 1 9 1 0 1 Sequence ID First Three Digits Next Four Digits Last Three Digits

Table 2 Bits 12 0 0 1 1 Position ID Left Center As Left Center As Right Right

13 0 1 1 0

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

P

SSM

BCD CHARACTER ***

RESERVED

SDI

OCTAL LABEL 061

Bit No. 10 11 12 13

Function SDI (Indicates Sequence ID)* RESERVED (Own P/N) RESERVED (Position ID)** RESERVED (Position ID)**

Bit Status 1 Own P/N 0 Other P/N

* ** ***

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

Table 1 Bits 10 0 1 1 9 1 0 1 Sequence ID First Three Digits Next Four Digits Last Three Digits

Table 2 13 0 1 1 0 Bits 12 0 0 1 1 Position ID Left Center As Left Center As Right 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

P

SSM

BCD CHARACTER ***

RESERVED

SDI

OCTAL LABEL 207

Bit No 10 11 12 13

Bit Status Function SDI (Indicates Sequence ID)* RESERVED (Own P/N) RESERVED (Position ID)** RESERVED (Position ID)** 1 0

Own P/N

Other P/N

* ** ***

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

Table 1 Bits 10 0 1 1 9 1 0 1 Sequence ID First Three Digits Next Four Digits Last Three Digits

Table 2 13 0 1 1 0 Bits 12 0 0 1 1 Position ID Left Center As Left Center As Right 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 SDI DESCRIPTION Number 1 1 Tank Unit #1 2 1 Tank Unit #2 3 1 Tank Unit #3 4 1 Tank Unit #4 5 1 Tank Unit #5 6 1 Tank Unit #6 7 1 Tank Unit #7 8 1 Tank Unit #8 9 1 Tank Unit #9 10 1 Tank Unit #10 11 1 Tank Unit #11 12 1 Tank Unit #12 13 1 Tank Unit #13 14 1 Tank Unit #14 15 1 BITE Capacitor 16 1 Compensator 17 1 Load Select 18 1 Load Select 19 1 Load Select 20 1 Undefined 21 1 Fuel Density 22 2 Tank Unit #1 23 2 Tank Unit #2 24 2 Tank Unit #3 25 2 Tank Unit #4 26 2 Tank Unit #5 27 2 Tank Unit #6 28 2 Tank Unit #7 29 2 Tank Unit #8 30 2 Tank Unit #9 31 2 Tank Unit #10 32 2 Tank Unit #11 33 2 Tank Unit #12 34 2 Tank Unit #13 35 2 Tank Unit #14 36 2 Compensator 37 2 BITE Capacitor #2 38 2 Load Select 39 2 Load Select 40 2 Load Select 41 2 Undefined 42 2 Fuel Density 43 3 Tank Unit #1 44 3 Tank Unit #2 45 3 Tank Unit #3 46 3 Tank Unit #4 47 3 Tank Unit #5 48 3 Tank Unit #6 49 3 Tank Unit #7 50 3 Tank Unit #8 51 3 Tank Unit #9 52 3 Compensator 53 3 BITE Capacitor #3 54 3 Undefined 55 3 Undefined 56 3 Undefined 57 3 Undefined 58 3 Undefined 59 3 Load Select 60 3 Load select 61 3 Load Select 62 3 Undefined 63 3 Fuel Density

UNITS pF pF pF pF pF pF pF pF pF pF pF pF pF pF pF pF Lbs. Lbs. Lbs. Lbs/Gal pF pF pF pF pF pF pF pF pF pF pF pF pF pF pF pF Lbs Lbs Lbs Lbs/Gal pF pF pF pF pF pF pF pF pF pF pF Lbs Lbs Lbs 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 P SSM A16--------------------------------------------------------------- A1 MSB 876 543 21 Octal Label 214 001 100 01 c-16 876 543 21 Octal Label 216 011 100 01

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 P SSM A24--------------------------A17 LSB 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 MATRIX PARITY (odd) RESERVED (SDI) 0.5 kHz SPARE ANT

Function

1000 kHz (1)

100 kHz (0)

10 kHz (5)

1 kHz (7)

BFO

LABEL ADF Frequency (032) 876 010 2 564 110 3 21 00 0

Bit No. Example Notes

32 1

31 30 0 0

29 28 27 0 0 1

26 25 24 23 0 0 0 0

22 21 20 19 0 1 0 1

18 17 16 15 0 1 1 1

14 1 [1]

13 0

12 0 [2]

11 0 [2]

10 9 0 0

[1] [2]

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. Bit 11 12 Zero BFO off ADF Mode One BFO on ANT Mode

TABLE 6-41
DME SIGN/STATUS MATRIX 0.00/0.05 MHz PARITY (odd) MLS FREQ. ILS FREQ. IDENT DISPLAY

c-4

Function

10 MHz

1 MHz

0.1 MHz

DME Mode

SDI

LABEL DME Frequency (035) 876 101 5 543 110 3 21 00 0

Bit No. Example Notes [1] [5]

32 1

31 30 0 0

29 28 27 0 0 1

26 25 24 23 0 1 0 1

22 21 20 19 0 1 1 0

18 1 [2]

17 16 0 1 [7]

15 0 [3]

14 0

13 12 11 0 0 0 [4]

10 9 0 0

[1] [2] [3] . [4] . [5] c-16 c-10 c-4 [6] [7]

Directed Frequency #1, 115.65 MHz, VOR Bit 18 is used only for VOR & ILS frequencies and is limited to .00 or .05 Bits 15 & 14 codes: VOR (0,0), ILS (0,1) or MLS (1,0). (1,1) is spare Refer to table in Section 4.1.2 of ARINC Characteristic 709 for mode codes Although not encoded in the tuning word all VOR & ILS frequencies have 1 as hundreds digit. 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. (Original note deleted) Bit 16 when equal to “one” specifies that a displayable BCD output is to be provided for that station, 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 Function 10 MHz (2) 1 MHz (3) 0.1 MHz (5) 0.01 MHz (7) 0.001 MHz (9) USB/LSB MODE SSM/AM MODE WORD IDENT. 11 10 9 0 0 0 [1] [2] PARITY (Odd) SIGN/STATUS MATRIX LABEL HF COM Frequency (037)

Bit No. Example Notes

32 0

31 30 0 0

29 28 1 0

27 26 25 24 0 0 1 1

23 22 21 20 0 1 0 1

19 18 17 16 0 1 1 1

15 14 13 12 1 0 0 1

876 111 7

543 110 3

2 1 0 0 0

[1] [2]

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

TABLE 6-42-1
RESERVED WORD IDENT. SIGN/STATUS MATRIX PARITY (odd) HF COM Word #2 Function

c-4
0.1 kHz (5) NOT USED LABEL HF COM Frequency (037)

Bit No. Example

32 0

31 30 0 0

29 28 27 26 0 1 0 1

25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

10 9 0 1 [1]

876 111 7

543 110 3

21 00 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
WORD IDENT. SIGN/STATUS MATRIX PARITY (odd) HF COM Word #1 Function

10MHz (2)

1 MHz (3)

0.1 MHz (5)

0.01MHz (7)

0.001MHz (9)

SDI

LABEL HF COM Frequency (205)

Bit No. Example

32 0

31 30 0 0

29 28 1 0

27 26 25 24 0 0 1 1

23 22 21 20 0 1 0 1

19 18 17 16 0 1 1 1

15 14 13 12 1 0 0 1

11 0

10 9 0 1

876 101 5

543 000 0

2 1 01 2

ARINC SPECIFICATION 429, PART 1 - Page 110 ATTACHMENT 6 GENERAL WORD FORMATS AND ENCODING EXAMPLES TABLE 6-43-1
WORD IDENT. SIGN/STATUS MATRIX PARITY (odd) HF COM Word #2 Function

0.1 kHz (5)

NOT USED

SDI

LABEL HF COM Frequency (205)

Bit No. Example

32 0

31 30 0 0

29 28 27 26 0 1 0 0

25 24 23 22 21 20 19 18 17 16 15 14 13 12 0 0 0 0 0 0 0 0 0 0 0 0 0 0

11 1

10 9 0 0

876 101 5

543 000 0

2 1 0 1 2

RADIO SYSTEMS MANAGEMENT WORD FORMATS TABLE 6-44 c- 5
SIGN/STATUS MATRIX ILS PARITY (odd)

SPARE

Function

c- 3

Bit No. Example

32 1

31 30 0 0

29 28 27 0 0 0

26 25 24 23 1 0 0 1

22 21 20 19 0 0 1 1

18 17 16 15 0 0 0 0

14 13 0 0

12 11 0 0

ILS CAT.

10 MHz (0)

1 MHz (9)

0.1 MHz (3)

0.01 MHz (0)

RES. (SDI)

LABEL Frequency (033) 876 110 3 543 110 3 21 00 0

10 9 0 0

BIT POSITION c- 5
CATEGORY NOT ILS CAT I ILS CAT II ILS CAT III

12
0 0 1 1

11
0 1 0 1

TABLE 6-44-1
VOR/ILS SIGN/STATUS MATRIX PARITY (odd) 10 MHz (0)

Function

SPARE

1 MHz (9)

0.1 MHz (3)

0.01 MHz (0)

RES. (SDI) ILS CAT.

LABEL VOR/ILS Frequency (034) 8 76 001 4 5 4 3 1 1 0 3 2 1 00 0

Bit No. Example

32 1

31 30 0 0

29 28 27 0 0 0

26 25 24 23 1 0 0 1

22 21 20 19 0 0 1 1

18 17 16 15 0 0 0 0

14 0 [1]

13 12 11 0 0 0

10 9 0 0

c- 2 tuning

[1]

Bit number 14 should be set to “zero” for VOR frequencies and “one” for ILS frequencies by the information sources.

ARINC SPECIFICATION 429, PART 1 - Page 111 ATTACHMENT 6 GENERAL WORD FORMATS AND ENCODING EXAMPLES

TABLE 6-45
VHF/COM SIGN/STATUS MATRIX PARITY (odd)

Function

10 MHz (2)

1 MHz (8)

0.1 MHz (5)

0.01 MHz (3)

0.001 MHz (0)

RES (SDI)

LABEL VHF COM Frequency (030)

Bit No. Example

32 1

31 30 0 0

29 28 27 0 1 0

26 25 24 23 1 0 0 0

22 21 20 19 0 1 0 1

18 17 16 15 0 0 1 1

14 13 12 11 0 0 0 0

10 9 0 0

876 000 0

543 110 3

21 00 0

TABLE 6-46
RADIO SYSTEMS MANAGEMENT WORD FORMATS ALT. DATA SOURCE SEL. IDENT. ATC TRANSPONDER SIGN/STATUS MATRIX PARITY (odd)

Pilot Selected Mode A Reply Code 0-7 (3) A4 A2 A1 0-7 (6) B4 B2 B1 0-7 (2) C4 C2 C1 0-7 (0) D4 D2 D1 CONTROL FUNCTION

Function

CONTROL FUNCTION ALT. REP. ON/OFF

RES. (SDI)

LABEL Beacon Transponder Code (031)

Bit No. Example Notes

32 1

31 30 0 0

29 28 27 0 1 1

26 25 24 1 1 0

23 22 21 0 1 0

20 19 18 0 0 0

17 16 15 0 0 0 [2]

14 13 12 11 0 0 0 0 [1] [ 2] [1]

10 9 0 0

876 100 1

543 110 3

21 00 0

[1] Bit 11 13 14 Zero Altitude Report On Ident. OFF Use #1 Alt. Data Source One Altitude Reporting Off Ident. ON Use #2 Alt. Data Source

[2] Control Panel Bit Function Function 17 16 15 DABS ON/ 0 0 0 ASAS OFF Reset Aural 0 0 1 Warning Signal Remainder are Reserved for future use.

12 1 0

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. 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17-20 21-24 25 26 27-28 29 30-31 32 0 1 1 0 0 1 1 0

Description

1 4

6 SDI Distance Memory (DIST MEM=1) Bearing Memory (BRG MEM=1) Pad Zero VOR/TAC Select (TAC=1, VOR=0) TACAN Select (TAC 1=1, TAC 2=0) Pad Zero BCD Units Chan Cont (LSB=17) Hex Tens Chan Cont (LSB=24) Pad Zero X/Y Mode (X=1, Y=0) Mode Cont (See Table A) Pad Zero SSM (See Table B) Parity (Odd)

RADIO SYSTEMS MANAGEMENT WORD FORMATS

Table A – Mode Control Bits 27 28 0 0 0 1 1 0 1 1 Description REC A/A REC T/R A/A T/R

Table B - SSM Bits 30 31 0 0 0 1 1 0 1 1 Description Valid Functional Test No Computed Data 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.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 -16 17 18 19 20 21 22 23 24 25 26 27-28 29 30-31 32 0 1 1 0 0 1 1 1

Function 1
4 Label Number (147)

1

0

Note

7 SEL SEL LOBE AUTO/MAN TUNE A/A AGC Disable Pad TACAN/MLS Select (LSB) BCD Channel Code Units (MSB) (LSB) HEX Channel Code Tens (MSB) TST X/Y Mode Control INT SSM Parity (odds) TEST X NORMAL TACAN 1 ANTENNA 2 ANTENNA LOBE AUTOTUNE ENABLE TACAN 2 ANTENNA 1 MANUAL TUNE DISABLE X [1]

NO TEST Y [2] INVERSE [3]

[1] TACAN/MLS Select Bits 15 16 0 0 1 0 0 1 1 1 Description TACAN MLS W Not Used MLS Z

[2] Mode Control Bits 27 28 0 0 1 0 0 1 1 1 Description REC T/R A/A REC A/A T/R

[3] SSM Bits 30 31 0 0 0 1 1 0 1 1 Description Valid Data No Computed Data Functional Test Not Used

Page 114 ATTACHMENT 7 DATA BIT ENCODING LOGIC BIT NUMBER BI .ARINC SPECIFICATION 429. PART 1 .POLAR RZ N 11 10 8 9 6 7 5 4 3 2 1 HI NULL LO 1 0 1 1 0 1 0 1 0 0 1 1 DATA .

.5% 5 µsec + 5% 1.ARINC SPECIFICATION 429.5kbps Z* µsec + 2.5 + 0.5% Y/2 + 5% 10 + 5 µsec 10 + 5 µsec Z = 1 where R = bit rate selected from 12 – 14.5 µsec LOW SPEED OPERATION 12 – 14.5 µsec 1.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-toground and B-to-ground. PART 1 .Page 115 ATTACHMENT 8 OUTPUT SIGNAL TIMING TOLERANCES HI TRANSMITTED VOLTAGE LINE A TO LINE B NULL X Y LO PARAMETER Bit Rate Time Y Time X Pulse Rise Time** Pulse Fall Time** * ** c-16 HIGH SPEED OPERATION 100k bps + 1% 10 µsec + 2. These rise and fall times are for open circuit output measurements – Appendix 1 provides waveforms for typical test performance.5 + 0.

93 512 ±180° ±180° ±180° ±180° 12 12 12 12 16 11 12 12 12 18 14 14 12 18 5 12 5:6:6 12 12 9 12 12 16 16 17 15 11 12 12 12 12 Above S.95 180N-180S 180E-180W 0-359° 5 5 4 4 4 4 4 4 4 6 6 3 North East 0. REVISIONS ARE NOT SHOWN. 9B See Att.05° 1 0.95 108-111. 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. 0.05° 0.044° A/C To WPT Fly Left Fly Down Fly Right Fly Up Inc.044° 0.8 512 512 131.0625 0.3 50 33.0° NOTES Bit 11 Non Std 200 200 200 200 SSM Squelch SSM XMIT SSM Reply 190-1750 190-1750 108-111.0001 0.5 250 50 50 31.3 100 167 167 See Note 2 31.3 31.ARINC SPECIFICATION 429. or GA industry PRIVATE bit structures.0° ±180° ±180° ±180° ±180° 65536 ±180° ±180° ±180° ±180° 128 16384 ±180° ±180° 2. 9B Bit 11 Non Std Bit 11 Non Std See Att.1° 0. Knots Degrees Degrees Degrees MHz MHz Discrete Discrete KHz KHz MHz MHz MHz MHz MHz MHz MHz Deg:Min Deg:Min Deg Discrete Discrete Discrete Deg/180 Deg/180 Deg/180 Deg/180 Feet Deg/180 Deg/180 Deg/180 Deg/180 Naut Mi Feet Deg/180 Deg/180 Deg/sec Hr/Min Deg/180 Hr:Min:Sec 1=Stall Deg/180 Knots DDM DDM Naut Mi Naut Mi Feet Knots Deg C Deg/180 Deg/180 Deg/180 Deg/180 RANGE ±3999. 9B See Att. Min.59.5 100 66.3 31.3 31.05° 0.5 100 100 100 200 1000 100 125 62.95 108-117.5 62.3 31. 9B See Att.95 108-117.05° 0.3 83. 9B See Att.L.044° 0.0005 0.05° 0.05 0.95 108-134. 9B See Att. PART 1 .5 62. 9B See Att.0 0.0 0. PLEASE CONTACT GAMA. Labels with a “G” or “P” suffix refer to GAMA standard.05 0. Type & Class BNR BNR BNR BCD DSC DSC DSC BNR 1-Stall Naut Mi Minutes Discrete Discrete Discrete Discrete Discrete ±2 4096 512 12 15 9 6 Upward Always Pos Always Pos 0.025 0.005 0.05° 0.0 sec 0.Page 116 THIS ATTACHMENT WAS REPRODUCED WITH THE PERMISSION OF GAMA.5 See Att.95 108-117.025 MAX XMIT INT (msec) 200 200 500 333 333 333 100 100 100 100 200 200 333 333 333 333 333 200 200 500 500 500 200 200 MAX UPDATE INT LABEL (OCTAL) 001 002 012 017 024G 027 030G 031G 032 033 034G 035G 041 042 043 060P 061P 074G 075G 100G 100 101G 102G 105 110 113G 114 115 116G 117G 121 122G 123 125 147G 150 157P 162G 163G 173 174 202 204 210 213 222P 222 PARAMETER NAME Distance to go Distance to go Time to go Time to go Ground Speed Ground Speed Selected Runway Heading Selected Course 1 Selected Course 2 VHF COM Frequency VHF COM Frequency Beacon Transponder Code Beacon Transponder Code ADF Frequency ADF Frequency ILS Frequency ILS Frequency VOR/ILS Frequency VOR/ILS Frequency VOR/ILS Frequency DME Frequency DME Frequency Set Position Latitude Set Position Longitude Set Magnetic Heading Omega Data Select Covariance Data Data Record Header Active WPT From/To Data Selected Course 1 Selected Course 1 Selected Heading Selected Heading Selected Altitude Selected Runway Heading Selected Course 2 Message Checksum Desired Track (True) Waypoint Bearing (True) Cross Track Distance Vertical Deviation HORIZ. RESOL 0.4 0.6 66.95 108-135. EQPT. 6 125 Bit 11 Non Std Bit 29 Non Std See Att.005 1. 125 241P 251G 252 260G 261P 275G 277P 300G 02 02 02 02 02 02 02 Normalized AOA Distance To Go Time-To-Go Date GPS Discrete Word 1 LRN Status Word Cabin DSPY Cont DSC STN MAG DEC.9 0-399. All others are ARINC standard words.#1 True Airspeed Static Air Temperature VOR Radial VOR Omnibearing VOR Omnibearing VOR Omnibearing DATA TYPE BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BNR BNR DSC DSC BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BCD BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR UNITS N.072 2047.001° 0.25 0. ID (HEX) 02 09 02 09 02 09 10 11 11 02 16 02 18 02 12 02 10 02 10 11 02 09 02 02 02 02 02 02 02 02 11 02 25 02 10 11 02 02 02 02 02 02 02 02 02 02 02 06 12 02 10 10 02 09 02 02 02 02 02 10 11 SIG BITS / DIGITS 5 4 4 4 3 3 5 5 MIN XMIT INT (msec) 100 100 250 167 167 167 0.1 0.05° 0. (To Autopilot) Throttle Command Greenwich Mean Time Magnetic Variation Greenwich Mean Time Normalized AOA ADF Bearing Wind on Nose Localizer Deviation Glideslope Deviation DME Distance DME Distance Baro Corrected Alt.5 62.0 1 Day 125 100 100 500 1000 200 200 See Note 2 125 200 200 1000 1000 400 200 See Att.1 1 .5 62.3 31.5 0.1 0. 9B See Att.975 118-135. FOR ANY COMMENTS OR QUESTIONS.3 50 50 50 100 500 50 125 31.125 1.56 0-23.3 See Att.9 0-2000 0-359. 9B See Att.3 31. 9B See Att.05 0.CMD.0002 0.CMD.(To Autopilot) VERT. 9B . Always Pos Above Zero To Station From VOR From VOR From VOR 100 100 167 167 167 167 167 100 100 250 250 250 100 100 See Note 1 See Note 1 167 167 31. 9B See Att.5 200 333 333 62.01° 0.05 0.05 0.0° 1.05 0.0005 0.5 0.05 0.M.6 167 167 62.5 0.3 3.05° 0.5 125 500 100 100 62. 9B 1000 See Att.0005 1.L.05° 1. 9B 333 333 62.05° 0.3 33. 6 More than one MKR beacon bit set is MKR self test.975 POSITIVE SENSE Always Pos Always Pos Always Pos Always Pos Always Pos Always Pos Always Pos Always Pos Always Pos APPROX. Power East Upward Head Wind Fly Right Fly Down Always Pos Always Pos Above S.044° 0.1 0. respectively.0 0.5 62.1° 1.9° 0-359° 0-359° 118-135.1 1.3 62. 9B Bit 11 Non Std See Att.9 ±180° 23:59:59 ±2 ±180° 256 0.

FOR ANY COMMENTS OR QUESTIONS. REVISIONS ARE NOT SHOWN. ARINC SPECIFICATION 429.0625 Ft 0. NOTE 2: .125 1.7 0. ID (HEX) 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 09 10 11 12 16 18 PARAMETER NAME Message Characters 7-9 Message Characters 10-12 Message Length / Type / Number Message Characters 1-3 Message Characters 4-6 NAV/WPT/AP Latitude NAV/WPT/AP Longitude Present Position Latitude Present Position Longitude Ground Speed Track Angle (True) True Heading Wind Speed Wind Angle (True) Magnetic Heading Drift Angle Lateral Scale Factor Vertical Scale Factor Distance To Destination Est Time to Destinaiton Dest Local Time Offset Specific Equipment Ident Specific Equipment Ident Specific Equipment Ident Specific Equipment Ident Specific Equipment Ident Specific Equipment Ident Specific Equipment Ident DATA TYPE BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BCD DSC DSC DSC DSC DSC DSC DSC UNITS Discrete Discrete Discrete Discrete Discrete Deg/280 Deg/180 Deg/180 Deg/180 Knots Deg/180 Deg/180 Knots Deg/180 Deg/180 Deg/180 Naut Mi Feet Naut Mi Minutes Hour/Min RANGE SIG BITS / DIGITS POSITIVE SENSE APPROX.0039 NM 0.768 4096 23:59 20 20 20 20 15 12 15 8 8 15 12 15 15 18 12 5 North East North East Always Pos Always Pos Always Pos Always Pos Always Pos . Ten records are transmitted in one second. addendum 3.05° 0.000172° . 9B NOTE 1: These labels are transmitted once at the beginning of each flight plan/graphics map data transfer.THIS ATTACHMENT WAS REPRODUCED WITH THE PERMISSION OF GAMA. Not all labels are transmitted with each record.05 0.0 0.125 0. PLEASE CONTACT GAMA.0055° 0.0055° 1.000172° . RESOL MIN XMIT INT (msec) See Note 2 See Note 2 See Note 2 See Note 2 See Note 2 See Note 2 See Note 2 100 100 25 25 25 50 50 25 25 80 80 500 500 1000 500 500 500 500 500 500 500 MAX XMIT INT (msec) MAX UPDATE INT NOTES 180N-180S 180E-180W 180N-180S 180E-180W 4096 ±180° ±180° 256 ±180° ±180° ±180° ±128 ±2048 32. These labels are used to make up the individual records that comprise a flight plan/graphics map data transfer. PART 1 .01 Min 200 200 50 50 50 100 100 50 50 1200 1200 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 Via Flight Plan Via Flight Plan See Att. Refer to the GAMA FMS Output Bus Standard for further information.000172° .Page 117 ATTACHMENT 9A GENERAL AVIATION LABELS AND DATA STANDARDS LABEL (OCTAL) 301G 302G 303G 304G 305G 306G 307G 310 311 312 313 314 315 316 320 321 326G 327G 351G 352G 353P 371G EQPT. Refer to the “FMS Waypoint/Navaid/Airport Data Transfer Protocol”.0 .000172° 0.

REVISIONS ARE NOT SHOWN. “0” denotes low “1” denotes control head. Pt. PLEASE CONTACT GAMA. “0” denotes Magnetic “1” inhibits display “1” denotes ILS.ARINC SPECIFICATION 429. FOR ANY COMMENTS OR QUESTIONS.Page 118 THIS ATTACHMENT WAS REPRODUCED WITH THE PERMISSION OF GAMA. “0” denotes filter (Normally “1” but “0” for Honeywell (Olathe) manufactured equipment) 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 SDI 8 7 6 5 4 3 DME Frequency Label 035G 2 1 32 P 31 30 29 28 27 26 25 24 SSM Bit 13 0 0 0 0 1 1 1 1 12 0 0 1 1 0 0 1 1 11 0 1 0 1 0 1 0 1 See Chapter 3 DME Mode Standby Directed Freq #1 Directed Freq #2 Directed Freq #3 Hold Freq #1 Hold Freq #2 Not used Spare See Below 32 P 31 30 29 0 28 27 26 25 24 MSB 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 SSM Relane Binary Address 6 5 4 3 Omega Data Select Label 060P 2 1 *Specific user word Bit 28 Bit 27 Bit 26 0 0 1 1 30 29 28 Term Indent Full Restart Bit Rho Rho Updating 25 0 1 0 1 27 Function No Action Relane Do Not Release Invalid Use 26 25 “1” denotes restart “1” inhibits update 32 P 31 SSM 24 23 22 21 20 Exponent (IEEE Flt. ATTACHMENT 9B GENERAL AVIATION WORD EXAMPLES 32 P 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 SDI 9 8 7 6 5 4 3 VOR/ILS Frequency Label 034G 2 1 SSM See Chapter 3 See Below Bit 11 Bit 12 Bit 13 Marker Sensitivity Last Tune Source VOR Digital Filtering “1” denotes high. Pt. “0“ denotes Lat/Long 21 20 19 18 17 16 15 14 13 12 11 10 9 SDI These are User Specific bits 8 7 6 5 4 3 Selected Altitude Label 102G 2 1 SSM Same as Attachment 2 Bit 11 Bit 12 Altitude Select Knob Altitude Alert “0” denotes “in motion” “1” denotes “on” User-specific bits .) 5 4 3 Coveriance Data* Label 061P 2 1 *Specific user word Bit 27 Sign Bit 29 0 0 1 1 30 29 28 28 0 1 0 1 27 Functions Term 1 Term 2 Term 3 Not Used 26 25 Pad (Zeros) 24 23 22 “1” denotes negative 32 P 31 21 20 19 SSM 18 17 Pad (Zeros) 16 15 MSB 14 13 12 11 10 9 8 7 Number of Records 6 5 4 3 Data Record Header Lable 074G 2 1 Bit 21 32 P 31 30 29 0 28 Prior Record Change 27 26 25 From Waypoint LS Byte 24 23 22 21 To Waypoint LS Byte “1” denotes changed record 20 19 18 17 From Waypoint MS Byte 16 15 14 13 To Waypoint MS Byte 12 11 10 See Below 9 8 7 6 5 4 3 2 Active Waypoint From/To Data Label 075G 1 SSM Bit 9 Bit 10 Bit 11 Bit 12 32 P 31 30 29 28 Auto/Leg/Man/Obs Mag/True Reference Radar Waypoint Displayed Lat/Long/ILS Mode 27 26 25 24 23 22 “1” denotes Auto/Leg. PART 1 .) MSB 19 18 17 16 15 14 13 12 11 10 9 8 7 6 Mantissa (IEEE Flt. “0” denotes Man/Obs “1” denotes True. “0“ denotes other “1” denotes no filter.

“0” denotes “no GAP” . PLEASE CONTACT GAMA. 32 P 31 30 29 + 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 See Below 11 10 9 SDI 8 7 6 5 4 3 Vertical Deviation Label 117G 2 1 SSM Data Bit 14 Bit 13 Bit 12 Bit 11 VNAV Arm Enable/Alert VNAV Bendover VNAV Bendover Direction Altitude with respect to 1000 ft. “0” denotes “not SELECT” “1” denotes “CENTER”. ARINC SPECIFICATION 429. “0” denotes “on route” “1” denotes “SELECT”. “1” denotes enable “1” denotes “capture”. “0” denotes flydown” “1” denotes “greater”. PART 1 . “0” denotes less User Specific bits 32 P 31 30 29 10s 29 28 Day 27 26 1s 25 24 23 10s 22 21 1s 20 19 18 17 10s 17 16 15 Year 14 13 1s 12 11 10 SSM Month 9 SDI 8 7 6 5 4 3 2 1 Date Label 260G 8 7 6 5 4 3 2 Message Length/Type/No.THIS ATTACHMENT WAS REPRODUCED WITH THE PERMISSION OF GAMA. Label 303G 1 32 P 31 30 28 Spare 27 26 25 24 23 22 SSM 21 20 19 18 Waypoint Number (Binary) 16 15 14 13 See Below 12 11 10 Words in Message 9 Bit 16 Bit 24 Bit 25 Bit 26 Bit 15 0 0 0 0 1 1 1 1 Date Record FMS Plan Mode WPT at Plan Center Flight Plan GAP Follows 14 0 0 1 1 0 0 1 1 13 0 1 0 1 0 1 0 1 WYPT/STATION TYPE Waypoint Nav Aid Airport NDB Altitude Profile Point No Symbol VOR Intersection “1” denotes “off route”. “0” denotes “track” “1” denotes “fly up”.Page 119 ATTACHMENT 9B GENERAL AVIATION WORD EXAMPLES 32 P 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 Message Check Sum Label 113G 2 1 SSM Check Sum 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. REVISIONS ARE NOT SHOWN. “0” denotes “not CENTER” “1” denotes “GAP”. FOR ANY COMMENTS OR QUESTIONS.

REVISIONS ARE NOT SHOWN. (Final Appr) Appr Integrity (Final Appr) GPS Integrity GPS Annunciation 27(0) & 26(0) & 25(0) – Enroute 27(0) & 26(0) & 25(1) – Terminal 27(0) & 26(1) & 25(0) – Approach (27(1) & 26(0) & 25(0) – Oceanic Spare SSM 31(0) & 30(0) – Normal Operations 31(0) & 30(1) – No Computed Data 31(1) & 30(0) – Functional Test 31(1) & 30(1) – Not used Parity (odd) Angular Yes Angular Valid Fail Linear No Linear Invalid Valid .ARINC SPECIFICATION 429. FOR ANY COMMENTS OR QUESTIONS. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 x Label 261G 02 LRN Status x x x x x x SDI Spare Pad Zero Bit Status 0 x Reserved Vert Dev (Final Appr) Lat Dev Scaling in Transition Lat Dev. PLEASE CONTACT GAMA. ATTACHMENT 9B GENERAL AVIATION WORD EXAMPLES Bit No. PART 1 .Page 120 THIS ATTACHMENT WAS REPRODUCED WITH THE PERMISSION OF GAMA.

ANY COMMENTS OR QUESTIONS. ARINC SPECIFICATION 429. 1 2 3 4 5 6 7 8 9 10 11 12 13 Function 1 x Label 275G 02 LRN Status x x x x x x SDI Waypoint Alert Dead Reckon Direct To Mode 15(0) & 14(0) – Multiple Sensor Based 15(0) & 14(1) – VOR/DME Offset (RNAV) Approach 15(1) & 14(0) – VOR/TACAN (non-Offset) Approach/Enroute 15(1) & 14(1) – ILS Approach Vert & Lat Dev Scaling FMS Controlled Hdg Sub-mode Remote FGS Army for Nav Capt FMS Plan Mode Display Final Appr Course Angular Scaling Integrity Warn To From Parallel XTK Offset Airport Display Selected Message Alert True/Mag HSI Valid (NAV Warn) SSM Parity (odd) On DR Select Off Not DR Not Select Bit Status 0 x 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Approach FMS/FGS Arm Select Display Active Warn To From Selected Select On True Valid Enroute FGS Only No Change Not Select No Change Not Active Not Warn Not To Not From Not Selected Not Selected Off Magnetic Warn .THIS ATTACHMENT WAS REPRODUCED WITH THE PERMISSION OF GAMA. PLEASE CONTACT GAMA.Page 121 ATTACHMENT 9B GENERAL AVIATION WORD EXAMPLES Bit No. PART 1 . REVISIONS ARE NOT SHOWN.

Page 122 THIS ATTACHMENT WAS REPRODUCED WITH THE PERMISSION OF GAMA. FOR ANY COMMENTS OR QUESTIONS. PLEASE CONTACT GAMA. . 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Function 1 x Label 277G 02 LRN Status x x x x x x Bit Status 0 x SDI (if required) Play Briefing #1 Play Briefing #2 Play Briefing #3 Play Briefing #4 Play Briefing #5 Play Briefing #6 Cancel Briefing #1 Cancel Briefing #2 Cancel Briefing #3 Cancel Briefing #4 Cancel Briefing #5 Cancel Briefing #6 Annunciate Cabin Message (Note) Spares Pad Zero 32 Alternate Format SSM 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 Parity (Odd) ALTERNATE STD 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 the briefing number is non zero. REVISIONS ARE NOT SHOWN. PART 1 . If BIT 29 is set to 1. ATTACHMENT 9B GENERAL AVIATION WORD EXAMPLES Bit No. this decoding will be used.ARINC SPECIFICATION 429. the indicated briefing will be played or canceled.

Range is 127 deg.THIS ATTACHMENT WAS REPRODUCED WITH THE PERMISSION OF GAMA. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 x x Label 300 02 Station Declination Bit Status 0 x x x x x x Spares Pad Zero DME Tuned and Received Not Collated Being Received Same Location Not Received Station Declination Binary number with sign bit 24 East is positive. ARINC SPECIFICATION 429.Page 123 ATTACHMENT 9B GENERAL AVIATION WORD EXAMPLES Bit No. West is 2’s complement of the positive value. E/W. VOR at location DME at location TACAN at location Class Bit 29/28/0 low 0/1 high 1/0 terminal SSM Parity Yes Yes Yes No No No . REVISIONS ARE NOT SHOWN. PLEASE CONTACT GAMA. PART 1 . FOR ANY COMMENTS OR QUESTIONS. Resolution is 1 degree at bit 17.

D.ARINC SPECIFICATION 429. FOR ANY COMMENTS OR QUESTIONS. PLEASE CONTACT GAMA. ATTACHMENT 9B GENERAL AVIATION WORD EXAMPLES 32 31 30 29 28 27 26 25 Company Private Use 24 23 22 21 20 19 Company I. PART 1 . Field Binary Bit Assignments 24 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 23 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 22 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1 21 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 20 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 19 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 COMPANY B&D INSTRUMENTS BEECH AIRCRAFT BENDIX AVIONICS CANADIAN MARCONI CESSNA AIRCRAFT COLLINS AVIONICS DELCO ELECTRONICS FOSTER RNAV GABLE CONTROLS GLOBAL SYSTEMS GULFSTREAM AEROSPACE HONEYWELL KING RADIO LEARJET LITTON AERO PRODUCTS OFFSHORE NAVIGATION RACAL AVIONICS SPERRY UNIVERSAL NAVIGATION SYS 3M AVIATION SAFETY SYSTEMS ALLIEDSIGNAL GENERAL AVIATION AVIONICS ALLIEDSIGNAL GLOBAL WULFSBERG BF GOODRICH AVIONICS GARMIN ARNAV COMPUTER INSTRUMENT CORPORATION SPARE 1 1 1 1 1 1 SPARE . D.Page 124 THIS ATTACHMENT WAS REPRODUCED WITH PERMISSION OF GAMA. (Binary) 18 17 16 15 EQ Code MSD (Hex) 14 13 12 11 EQ Code MSD (Hex) 10 9 8 7 6 5 4 3 2 1 GA Equipment Ident LABEL 371 P SDI LABEL 371 Company I. REVISIONS ARE NOT SHOWN.

ATTACHMENT 9C GENERAL AVIATION EQUIPMENT IDENTIFIERS Equipment HEX ID 01 02 04 05 06 09 0B 10 11 12 16 18 25 27 36 5A 5B A9 B0 B2 B6 B8 C7 FA FB EQUIPMENT Flight Control Computer Flight Management Computer Inertial Reference System Attitude and Heading Ref.ARINC SPECIFICATION 429. PLEASE CONTACT GAMA. REVISIONS ARE NOT SHOWN.Page 125 THIS ATTACHMENT WAS REPRODUCED WITH THE PERMISSION OF GAMA. System Air Data System Airborne DME Global Positioning System Airborne ILS Receiver Airborne VOR Receiver Airborne ADF System Airborne VHF Comm Receiver ATC Transponder Electronic Flight Instruments Microwave Landing System Radio Management System Loran Omega Airborne DME Controller Airborne ILS Controller Airborne ADF Controller VHF Comm Controller ATC Transponder Controller Microwave Landing System Controller Loran Controller Omega Controller . PART 1 . FOR ANY COMMENTS OR QUESTIONS.

Page 126 ATTACHMENT 10 MANUFACTURER SPECIFIC STATUS WORD 32 P 31 30 29 28 27 26 25 24 23 22 21 19 18 17 Company Private Use [A] 16 15 14 13 12 11 Company I.g. . PART 1 .ARINC SPECIFICATION 429.D.. The Company I. sub-LRU-Level BITE status).D. fields should be used to differentiate each manufacturers’ unique use of the Company Private Use field. (Binary) 10 9 8 7 6 5 4 3 2 1 Label (171) BIT 16 15 14 13 12 11 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 Company B&D INSTRUMENTS BEECH AIRCRAFT BENDIX AVIONICS CANADIAN MARCONI CESSNA AIRCRAFT COLLINS AVIONICS DELCO ELECTRONICS FOSTER RNAV GABLES CONTROLS GLOBAL SYSTEMS GULFSTREAM AEROSPACE HONEYWELL KING RADIO LEAR JET LITTON AERO PRODUCTS OFFSHORE NAVIGATION RACAL AVIONICS SPERRY UNIVERSAL NAVIGATION SYSTEMS 3M AVIATION SAFETY SYSTEMS ALLIED SIGNAL GENERAL AVIATION AVIONICS ALLIED SIGNAL GLOBAL WULFSBAG BF GOODRICH AVIONICS GARMIN ARNAV COMPUTER INSTRUMENT CORPORATION SPARE 1 1 1 1 1 1 SPARE [A] This word is used for manufacturer-specific information exchange (e.

Page 127 ATTACHMENT 11 SYSTEM ADDRESS LABELS SYSTEMS 777 CABIN INTERPHONE SYSTEM CVR 747 DFHR AND A330/340 SSFDR DFDAU (MANDATORY LOAD FUNCTION) SDU #2 RFU HGA/HPA TOP/PORT HGA/HPA STARBOARD LGA/HPA GPS/GNSS SENSOR FCMC Com A340-500/600 FCMC Mon A340-500/600 FCMC Int A340-500/600 MCDU 1 MCDU 2 MCDU 3 PRINTER 1 PRINTER 2 HUD HIGH SPEED DL (ARINC 615) MCDU 4 EIVMU 1 EIVMU 2 EIVMU 3 EIVMU 4 APM-MMR MMR ILS MLS AHRS VDR #1 VDR #2 VDR #3 CABIN VIDEO SYSTEM (AIRSHOW) LOW SPEED DL (ARINC 603) FMC 1 FMC 2 DFDAU (AIDS) CFDIU ACARS MU/CMU (724B.ARINC SPECIFICATION 429. PART 1 . 748) WBS TCAS SDU #1 GPWS GNLU 1 GNLU 2 GNLU 3 GNU 1 GNU 2 SYSTEM ADDRESS LABEL (OCTAL) 152 157 163 170 173 174 175 176 177 201 210 211 212 220 221 222 223 224 225 226 230 234 235 236 237 241 242 244 245 246 251 252 253 266 300 300 301 302 303 304 305 306 307 310 311 312 313 314 315 c-16 c-15 c-16 c-16 c-14 c-16 c-15 c-14 c-16 .

400 CABIN SERVICE SYSTEM (CSS) 747-400 AUDIO ENTERTAINMENT SYSTEM (AES)BOEING ENGINE INDICATION UNIT MULTICAST BRIDGE CABIN TERMINAL 3 CABIN TERMINAL 4 CABIN TERMINAL 1 CABIN TERMINAL 2 OMEGA NAV.Page 128 ATTACHMENT 11 SYSTEM ADDRESS LABELS SYSTEMS GNU 3 AUTOTHROTTLE COMPUTER FCC 1 FCC 2 FCC 3 APU APU CONTROLLER MODE CONTROL PANEL (MCP) FMC 3 ATC TRANSPONDER DADC CABIN TELECOMMUNICATIONS UNIT (CTU) HF DATA RADIO/DATA UNIT #1 HF DATA RADIO/DATA UNIT #2 ACESS EFIS PASSENGER SERVICES SYSTEM (PSS) 767300.ARINC SPECIFICATION 429. SYSTEMS SYSTEM ADDRESS LABEL (OCTAL) 316 321 322 323 324 325 326 327 330 331 332 334 340 344 360 361 362 363 364 365 366 367 372 373 374 375 376 c-16 c-15 c-14 c-16 c-14 c-16 c-14 . PART 1 .

This cable was connected in series with 300 ft. one opto-isolator conducts 1. in March 1977 and the other at the meeting held in Los Angeles.3 Receiver Input Circuit Description To perform the susceptibility tests.1 Cable and Test Configuration The cable used for the tests was standard aircraft type twisted shielded wire of 22 AWG. The HP 5082-4371 input has a forward conduction “knee” at approximately 1.ARINC SPECIFICATION 429.0 µ sec Bit Rate= 100 kilobits/second HI time= NULL time= LO time A1-2. Discharging to a +0. Figure a-(ii) shows schematics of the differential input stages used for the receivers. 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). 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.2 Transmitter Characteristics The block schematic of the bipolar line driving transmitter built for the tests is shown in Figure a-(i). The voltage follower stages provided a controlled impedance for the differential amplifier stage. During conduction. The test was configured to simulate the maximum length wire run with DO-160 conditions applied. common mode spikes. a charge on the second transistor is discharged via pin 7 and R2 to a potential of +0. . A1-2. PART 1 . The material in this Appendix is excerpted from these reports. A potential of +15 volts is applied to pin 8 to provide maximum gain in the first transistor. California. Voltage protection was used to prevent damage to the voltage followers in the event of high voltage. Opto-Isolator Input The opto-isolator input stage utilized two H-P 5082-4371 isolators connected in opposite polarity to detect the bipolar data. of cable which was subjected to the EMI environment within a screened room. of cable not subjected to the EMI environment. Differential Amplifier Input.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.Page 129 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS A1-1. in May 1977. A1-2.5 mA. length of cable was connected to the transmitter for the emission tests and to the receiver for the susceptibility tests.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. 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.5V differential on the line. 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. The EMI conditions used for the tests were derived from RTCA Document DO-160. 1975. At 4.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. receivers were constructed utilizing various methods of common mode rejection and various processing schemes.4 volts. one at the meeting held in Arlington. A1-2. The wire configuration consisted of approximately 60 ft. “Environmental Conditions and Test Procedures for Airborne Electronic/Electrical Equipment and Instruments” dated February 28th. The 60 Ft. Virginia. Boeing presented two reports to AEEC’s Systems Architecture and Interfaces Subcommittee on these activities. 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.5 volts set by R1 and R3.

Page 130 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS FIGURE a-(i) BIPOLAR TRANSMITTER BLOCK SCHEMATIC + PULSE GENERATOR SHAPED BIPOLAR RZ _ PSEUDO RANDOM BIT SEQUENCE GENERATOR SWITCHING LOGIC LINE DRIVER TERMINATION DETAIL OF LINE DRIVER AND TERMINATION LM0002 Ro 2 L1 LM0002 Ro 2 L1 . PART 1 .ARINC SPECIFICATION 429.

Page 131 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS FIGURE a-(ii) RZ BIPOLAR RECEIVER INPUT TYPES TESTED R OVER VOLTAGE VOLTAGE FOLLOWERS DIFFERENTIAL AMPLIFIER R PROTECTION R > 12 K Ohms (Provides Path for V.ARINC SPECIFICATION 429. F. Input Current) Figure (a) Differential amplifier input schematic. L 1 R L LED LED L 2 OPTO ISOLATORS ONE’S ZERO’S RL LED OPTO-ISOL = CURRENT LIMITING = 1000 OHMS = LED IN SERIES WITH OPTO ISOLATOR TO PROVIDE ON NULL LEVEL = H-P 5082-4371 Figure (b) OPTO-ISOLATED INPUT SCHEMATIC . PART 1 .

A threshold level could be introduced about zero voltage to provide an indication of the total energy contained in the pulse. but dissipates rapidly so that a NULL is estimated at the data sampling time.6 Emission of RF Energy Test Results The following tests were performed under conditions of light (one receiver) and heavy (20 receivers) line loading. The output of the integrator is sampled (timing is derived from the edge detector) at the end of the integration period. 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.7 Susceptibility Test Results The tests were performed to determine the susceptibility of the Mark 33 DITS to RF. Conducted RF Interference (RTCA DO-160 Paragraph 21.ARINC SPECIFICATION 429. (i) data sampling (sample and decision) and (ii) integrate and dump (Figure a(iv). a sample of the input is taken. since a NULL state is known to be invalid at the data sampling time. during a period of NULL on the line. B. Magnetic Fields Induced Into Interconnecting Cables (DO-160 Paragraph 19. If the integrator output fell within the threshold. A1-2. a ONE is declared. a ZERO is declared.Page 132 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS A1-2. a ONE is declared. No bit errors were detected with the field applied to the cable for any cable loading or receiver configuration. A.3) Test performed at a level above those specified in DO-160 Figure 19-1. . The integrate-and-dump processor circuit detects positive or negative-going edges which exceed the ±3V differential threshold. Radiated RF Interference (RTCA DO-160 Paragraph 21. If it is above zero voltage. A1-2. The edge detection causes an integration circuit to integrate the input voltage for a period of 5 µsec. integrate-and-dump processing Opto-isolator input. for example. The following receiver configurations were tested: (i) (ii) (iii) (iv) Differential Amplifier input. A.3) The interference measured was within the limits specified in DO-160 Figure 21-5. a ZERO is declared. an error diagnostic could be presented indicating the at the detection of the bit was marginal. A1-2. If the sample is HI. If the sample is LO. B. so initiating the edge detector timing circuit. Error checking was made on a bit-by-bit basis.4 Receiver Data Detection Technique Two data detection schemes were used.2) The interference measured was within the limits specified in DO 160 Figure 21-2.20B Category Z) No bit errors were detected with RF applied to any of the line loading and receiver configurations. if it is below zero voltage. time sample processing Opto-isolator input. integrate-and-dump processing The data transmitted consisted of a continuous pseudo-random bit sequence. time sample processing Differential Amplifier input. When the timing circuit has timed out. An error diagnostic will be output if. AF and spike interference levels specified in DO-160 under conditions of light (one receiver) and heavy (20 receivers) line loading. a short-duration noise spike causes the input to exceed the ±3V threshold. Conducted RF Susceptibility (DO-160 Paragraph 20. The edges cause a timing circuit to time for approximately 2 µsec. The data sampling system detects positive-going or negative-going edges which exceed ±3 volts differential voltage. If the sample is NULL. 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.5 Test Data Message The test waveform was a continuous pseudo-random bit pattern. PART 1 . and error diagnostic can be output. It should be noted that the 20dB limit exceedance permitted in DO 160 was not taken.

6k O/ P R3 1k . PART 1 .ARINC SPECIFICATION 429.5082 .4371 5V R1 10k 7 R2 500 5V R4 5.Page 133 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS FIGURE a-(iii) OPTO-ISOLATOR FRONT-END CIRCUIT SCHEMATIC 15 V 8 2 3 6 5 HP .

PART 1 .Page 134 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS FIGURE a-(iv) DATA DETECTION (a) SAMPLE –AND.ARINC SPECIFICATION 429.DUMP HI T+ NULL TLO I E E S DMP S I DMP LEGEND: E D S I DMP = EDGE DETECT (BIT TIMING) = DELAY = SAMPLE = INTEGRATION INTERVAL = DUMP INTEGRATOR CHARGE .DECISION BIT N HI T+ NULL T LO BIT N + 1 D E S E D S ZERO ( b ) INTEGRATE – AND .

with a maximum difference of 0. The waveforms for this simulation run are shown in Figures a-(ix) through a(xvi). Sample Det Diff.2 Computer Simulation A computer program was developed to evaluate pulse distortion on lines with stubs. The wire length and stub configuration were selected to represent postulated installations on a B747 airplane.. BMS B-51. the shields and cable inners are carded through.4) The tests were perform with voltage levels above those specified in DO 160 Figure 19-1 Category Z. Figure a-(vii) The transmitter output voltage and receiver input voltage for the configuration in Figure a-(v).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. with receivers at the equipment bay and the flight deck. The characteristics of the 20 AWG cable were measured and used to develop the cable model used in the computer simulation. the computer results were plotted. The computer simulation was run and results were plotted for various line length and stub configurations representing postulated installations on a B747 airplane. The cable used for lab tests was 20 and 22 AWG twisted shielded cable with wrapped KAPTON insulation. for later stub connection. a receiver and a single length of twisted shielded cable 200 feet long. Only the plotted results are presented here. This configuration represents a transmitter.ARINC SPECIFICATION 429. Int & Dump Det Line Light 0 0 8 0 Loading Heavy 0 0 15 1 D. The following results were observed: Receiver Configuration Diff. A1-3.4 volts on rising and falling edges. Figure a-(viii) shows the schematic for the second simulation. Int. Amp. A1-3. All configurations performed with zero bit errors for approximately 107 bits following the transient test. The DITS receiver input impedance was modeled. A1-3. The computer simulation showed slightly higher cable loss effect than the lab test. no. Spikes Induced Into Interconnecting Cables (DO-160 Paragraph 19. Lengths of twisted shielded cable were connected to form a representative wiring configuration for digital data.3 Results The results of the laboratory tests and computer simulation for the same cable configuration showed good agreement. Figure a-(vi) Transmitter open circuit differential output voltage.05 µH inductor (which models the inductance of the ground lead). At other nodes. The cable model was developed from the measured cable characteristics. Electric Fields Induced Into Interconnecting Cables (DO-160 Paragraph 19. the shields are grounded via a 0. Four receiver loading configurations are shown with maximum loading of twenty receivers. The DITS transmitter impedance and voltage waveform was modeled.1 Laboratory Tests Receivers and a transmitter were constructed to operate using the DITS high speed (100 KBPS) waveform. Figure a-(v) shows the schematic for the first simulation. A1-3.5. Class 2 type III. Sample Det Opto-Isolator. The cable is modeled as Blocks 1 to 4. PART 1 . The lab test results were recorded using an oscilloscope camera. Bit errors were counted during the application of 50 transients and also following the transient test.. Category Z) The spikes were generated and applied to the cable as shown in DO-160. The pulse distortion at the receiver nodes of the wiring systems were recorded. Amp.Page 135 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS C. & Dump Det Opto-Isolator. This configuration represents a transmitter at an engine location. . representing a continuous length of cable. At the transmitter and receive ends of the cable. Figure 19-4. No bit errors were detected with the field applied for any cable loading or receiver configuration. This waveform was used for all the simulation runs.

Figure a-(xxii) shows the schematic for the fourth simulation.ARINC SPECIFICATION 429. This configuration represents a transmitter with one receiver close (10 feet) and one receiver remote (500 feet). the inner engine and the outer engine. Figure a-(xvii) shows the schematic for the third simulation. . the flight engineer’s panel. This configuration represents a transmitter at the flight deck with receivers at the equipment bay.4 Conclusions From laboratory tests and simulations. the first officer’s panel and the captain’s panel. Figures a-(xviii) to a-(xxi) Waveforms for the third simulation. Figures a-(xxviii) and a-(xxix) Waveforms for the “long line” configuration. Figures a-(xi) to a-(xvi) Waveforms for loading configurations 2. Figures a-(xxiii) to a-(xxvi) Waveforms for the fourth simulation.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. This configuration represents a transmitter at the equipment bay with receivers at the equipment bay. 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. If installations are anticipated involving longer line lengths or cables with radically different electrical characteristics. A1-3. 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. Figure a-(xxvii) shows the schematic for the fifth simulation. 3 and 4. PART 1 . then further investigation may be required.

01 4 .01 .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 TRANS 1 1 (58m) BUSLIN 1 SHIELD 1 4 5 6 1 2 2 3 2 3 (1m) BUSLIN 2 SHIELD 2 4 5 6 1 2 3 (1m) BUSLIN 3 SHIELD 3 4 5 6 1 2 3 (1m) BUSLIN 4 SHIELD 4 4 5 6 1 REC 1 100k 2 1 2 1 2 1 2 1 2 * * A . PART 1 .1 3 .1 6 40 5 40 2 1 ALL L’s .ARINC SPECIFICATION 429.05µh µ TERM B TRANS * SHIELD TIED TO INDUCTOR ON TERM .

PART 1 .ARINC SPECIFICATION 429.Page 138 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS FIGURE a-(vi) Amplitude Volts Time (microseconds) TRANSMITTER LEAD A TO LEAD B VOLTAGE .

ARINC SPECIFICATION 429.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 . PART 1 .

01 .1 40 5 40 2 4 2 1 16.ARINC SPECIFICATION 429.Page 140 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS FIGURE a-(viii) # Load Rec 1 1 1 10 10 # Load Rec 2 1 10 1 10 Configuration 1 2 3 4 10 FEET RECEIVER TWO TRANSMITTER 200 FEET 85 FEET RECEIVER One 1 2 3 (3.01 6 . PART 1 .5k ALL L’s .05m) BUSLIN 5 4 5 6 1 2 REC 2 1 SHIELD 5 2 * TRANS 1 1 4 1 * 4 1 4 1 4 1 (61m) 2 2 3 5 2 Node 1 (10m) 5 2 6 (10m) 5 2 3 (6m) 5 2 6 REC 1 6 BUSLIN 1 BUSLIN 2 3 6 3 BUSLIN 3 BUSLIN 4 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 * 40pf .05 µ h TERM * SHIELD TIED TO INDUCTOR ON TERM BLOCK 1 6k 50pf 45pf 15k TRANS REC 1 .1 3 .

Page 141 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS FIGURE a-(ix) Amplitude Volts Time (microseconds) TRANSMITTER OUTPUT VOLTAGE Time (microseconds) VOLTAGE AT FIRST NODE CONFIGURATION 1 Amplitude Volts CONFIGURATION 1 . PART 1 .ARINC SPECIFICATION 429.

PART 1 .Page 142 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS FIGURE a-(x) Time (microseconds) VOLTAGE AT RECEIVER ONE Time (microseconds) VOLTAGE AT RECEIVER TWO CONFIGURATION 1 Amplitude Volts CONFIGURATION 1 Amplitude Volts .ARINC SPECIFICATION 429.

PART 1 .Page 143 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS FIGURE a-(xi) Time (microseconds) TRANSMITTER OUTPUT VOLTAGE Time (microseconds) VOLTAGE AT FIRST NODE CONFIGURATION 2 Amplitude Volts CONFIGURATION 2 Amplitude Volts .ARINC SPECIFICATION 429.

Page 144 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS FIGURE a-(xii) Time (microseconds) VOLTAGE AT RECEIVER ONE Time (microseconds) VOLTAGE AT RECEICER TWO CONFIGURATION 2 Amplitude Volts CONFIGURATION 2 Amplitude Volts .ARINC SPECIFICATION 429. PART 1 .

ARINC SPECIFICATION 429. PART 1 .Page 145 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS FIGURE a-(xiii) Time (microseconds) TRANSMITTER OUTPUT VOLTAGE Time (microseconds) VOLTAGE AT FIRST NODE CONFIGURATION 3 Amplitude Volts CONFIGURATION 3 Amplitude Volts .

Page 146 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS FIGURE a-(xiv) Time (microseconds) VOLTAGE AT RECEIVER ONE Time (microseconds) VOLTAGE AT RECEIVER TWO CONFIGURATION 3 Amplitude Volts CONFIGURATION 3 Amplitude Volts .ARINC SPECIFICATION 429. PART 1 .

Page 147 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS FIGURE a-(xv) Time (microseconds) TRANSMITTER OUTPUT VOLTAGE Time (microseconds) VOLTAGE AT FIRST NODE CONFIGURATION 4 Amplitude Volts CONFIGURATION 4 Amplitude Volts .ARINC SPECIFICATION 429. PART 1 .

PART 1 .ARINC SPECIFICATION 429.Page 148 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS FIGURE a-(xvi) Time (microseconds) VOLTAGE AT RECEIVER ONE Time (microseconds) VOLTAGE AT RECEIVER TWO CONFIGURATION 4 Amplitude Volts CONFIGURATION 4 Amplitude Volts .

5k 50pf 2 * SHIELD TIED TO INDUCTOR ON TERM BLOCK 45pf 15k TRANS REC 1 .01 4 .ARINC SPECIFICATION 429.01 .Page 149 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS FIGURE a-(xvii) 10 FEET TRANSMITTER REC TWO 50 FEET REC THREE 85 FEET 150 FEET 50 FEET 50 FEET 10 FEET REC 3 1 REC 2 10 LOADS 1 LOAD 1 2 2 5 * 4 6 5 4 6 2 SHIELD 5 BUSLIN 5 1 2 3 1 SHIELD 6 BUSLIN 6 (3.1 3 .05m) (15m) 2 2 3 * * 1 1 * TRANS 1 1 4 1 4 1 4 1 4 1 (26m) 2 2 3 REC 1 1 LOAD (46m) 5 6 NODE 1 (15m) 5 2 NODE 2 (3.05m) 5 2 NODE 3 BUSLIN 1 2 3 5 2 BUSLIN 2 6 3 BUSLIN 3 6 3 BUSLIN 4 6 1 SHIELD 1 2 11 SHIELD 2 2 1 SHIELD 3 2 1 SHIELD 4 2 * * * 1 2 * 3 4 * 5 6 7 8 9 * * * .05 µ h TERM 40pf 1 6k 2 16. PART 1 .1 6 40 5 40 1 ALL L’S .

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 . PART 1 .ARINC SPECIFICATION 429.

ARINC SPECIFICATION 429.Page 151 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS FIGURE a-(xix) Amplitude Volts Time (microseconds) VOLTAGE AT RECEIVER ONE Amplitude volts Time (microseconds) VOLTAGE AT RECEIVER TWO . 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 .

ARINC SPECIFICATION 429.Page 153 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS FIGURE a-(xxi) Amplitude Volts Time (microseconds) VOLTAGE AT THREE NODE . PART 1 .

1m) BUSLIN 6 SHIELD 5 (1.01 .05 µ h 40pf 1 6k 2 16.5m) BUSLIN 1 SHIELD 1 4 5 6 1 2 NODE 3 1 (26m) BUSLIN 2 SHIELD 2 4 5 6 1 2 NODE 2 3 (6.5m) BUSLIN 5 SHIELD 6 (6.1 3 .1 6 40 5 40 2 1 ALL L’S . PART 1 .Page 154 REC 3 1 LOAD REC 4 1 LOAD REC 2 1 LOAD 5 FEET 20 FEET 20 FEET APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS 2 TRANSMITTER 5 FEET 1 2 1 2 1 85 FEET 20 FEET 20FEET 4 5 6 * 5 6 4 4 5 6 2 * (6.5k 50pf TERM * SHIELD TIED TO INDUCTOR ON TERM BLOCK 45pf 15k TRANS REC 1 .1m) BUSLIN 7 1 2 3 1 SHIELD 7 2 2 1 2 3 1 2 3 1 * * 1 * * TRANS 1 2 1 2 3 (1.01 4 .1m) BUSLIN 4 SHIELD 4 4 5 6 1 2 REC 1 1 LOAD FIGURE a-(xxii) 1 2 1 2 1 2 1 2 * * * 1 2 * 3 4 * 5 6 7 8 9 * * * .REC TWO REC THREE REC FOUR ARINC SPECIFICATION 429.1m) BUSLIN 3 SHIELD 3 4 5 6 1 2 NODE 3 3 (6.

ARINC SPECIFICATION 429. PART 1 .Page 155 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS FIGURE a-(xxiii) Amplitude Volts Time (microseconds) TRANSMITTER OUTPUT VOLTAGE Amplitude Volts Time (microseconds) VOLTAGE AT FIRST NODE .

PART 1 .Page 156 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS FIGURE a-(xxiv) Amplitude Volts Time (microseconds) VOLTAGE AT RECEIVER ONE Amplitude volts Time (microseconds) VOLTAGE AT RECEIVER TWO .ARINC SPECIFICATION 429.

PART 1 .ARINC SPECIFICATION 429.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 .

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 . PART 1 .ARINC SPECIFICATION 429.

@ 100 (1.1 3 . PART 1 .ARINC SPECIFICATION 429.1 6 40 5 40 2 1 ALL L’s .5m) BUSLIN 5 SHIELD 5 4 5 6 1 2 REC 2 1 LOAD 1 2 * TRANS 1 2 1 4 1 * 4 1 4 1 4 1 2 6 REC 1 1 LOAD.5m) 2 5 2 Node 1 3 (100m) 5 2 Node 3 2 6 (50m) 5 2 Node 3 3 6 (2m) 5 BUSLIN 1 3 BUSLIN 2 BUSLIN 3 BUSLIN 4 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 * * * .01 4 .5k 50pf 45pf 15k Trans .05 µh TERM * SHIELD TIED TO INDUCTOR ON TERM BLOCK 40pf 1 6k 2 16.Page 159 APPENDIX A LABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS FIGURE a-(xxvii) REC TWO 5 FEET TRANSMITTER 5 FEET 328 FEET 164 FEET 8 FEET REC ONE OR 100 1 2 3 (1.01 .

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 . PART 1 .ARINC SPECIFICATION 429.

Data received via 1553A is dumped into another FIFO for retransmission by a DITS transmitter. available as single LSI chips. The material in this Appendix prepared by the Information Engineering Division of the USAF Directorate of Avionics Engineering describes one way of doing this. logic and timing differences in a Data Exchange Buffer (DEB). of avionics equipment designed originally for the airlines. and these sinks are typically not themselves data sources. the data may be retransmitted as received or reformatted. A more intelligent DEB. the controller is notified. PART 1 . or group of sinks which may be connected in a parallel. Upon arrival at the appropriate destination DEB. When the desired transmitter (DITS or 1553A) becomes available. the DEB must have separate transmitters to transmit the data with identical labels. the 1553A terminal. could achieve much higher efficiencies. The bus controller determines the intended destinations from the label and look-up table. a controller (microprocessor). The low rate of DITS terminals (minimum 320 microsec/word) would result in a very low loading of the parallel bus and controller. to the destination subsystem. the word is retransmitted.0 Introduction During the time that the broadcast approach to digital information transfer became established in the air transport industry. data typically flows from a given source to a single sink. as required by the destination subsystem. The retransmission of the label with the data greatly reduces the intelligence required by the DEB but increases bus loading. For DITS destinations. 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 retransmission of the data by the DEB allows inherently for different electrical and logical characteristics. logic and timing differences between the two systems. as received. valid word is available at a receiver.ARINC SPECIFICATION 429. a buffer memory. and as many FIFO’s as are required. . The received data is temporarily stored and then retransmitted by the 1553A terminal. the buffer memory and a dual 1553A remote terminal would probably fit on one one-sided 3/4 ATR card. The desired transmitter could be specified in the 1553A subaddress field.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. In this approach. It consists of multiple DITS receivers dumping received data into a first-in first-out (FIFO) stack. using a data exchange buffer to compensate for the electrical. the data word is routed from memory to the transmitter. the word is transferred to memory. Reformatting could involve removal of label and reversing of bit order (MSB vs LSB first). This method minimizes message related differences and compensates for electrical. The speed of the 1553A terminal might necessitate a direct memory access arrangement. 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 hardware consists only of DITS receivers. Another development in this same time frame has been the increased use by the military. In a hybrid system such as shown in Figure b-(i). It consists of an many DITS transmitters and receivers as necessary. to the appropriate DEB. Whenever a complete. Figure b-(iv) illustrates possible organization for a more sophisticated DEB. DITS data received by a DEB is momentarily stored and then retransmitted. a signal may originate in either a DITS type subsystem or a 1553A subsystem and may be destined for either type of terminal. This method represents one way of constructing a hybrid system. For 1553A destinations. Figure b-(iii) illustrates the organization of a minimum system. The much higher speed of 1553A would make retransmission delays small. The broadcast technique is adequate. If all labels in the system are unique. The airlines considered adopting MIL STD 1553. When the parallel data bus becomes available. a single (internally redundant) 1553A remote terminal. the military aviation community adopted a command/response time division multiplex technique as its standard. the DITS transmitter. and thus the airlines elected to stay with it for their new DITS. to the 1553A bus controller. The required ARINC transmitters and receivers would probably fit on another card. perhaps located in the bus controller. This entire system would probably fit on one full ATR card or less. for use on post-1980 new civil aircraft types but found the multiplex technique to be inappropriate for such applications. The storage of the data allows for simultaneous reception from multiple receivers (DITS and 1553A) and retransmission when the desired bus is available. complete with label. complete with label. If labels are not unique. and a program for the controller contained in ROM. Hand-shaking signals available on the FIFO’s eliminate almost all supporting SSI chips. The controller. all receivers in all subsystems associated with a DEB may be connected in parallel. Figure b-(ii) shows the handling of a word originating in the destined for DITS terminals. Only the data with the proper label will be recognized by each receiver.Page 162 APPENDIX B AN APPROACH TO A HYBRID BROADCAST-COMMAND/RESPONSE DATA BUS ARCHITECTURE A2-1. MIL STD 1553 was written to describe this system. the data is momentarily stored and then retransmitted in DITS format. In civil avionics systems. particularly in transport aircraft. 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. the program memory. A2-2. or something like it.

PART 1 .ARINC SPECIFICATION 429.Page 163 APPENDIX B AN APPROACH TO A HYBRID BROADCAST-COMMAND/RESPONSE DATA BUS ARCHITECTURE FIGURE b-(i) HYBRID BUS ARCHITECTURE NEW SUBSYSTEM RT T R R BUS CONTROLLER DUAL 1553A BUS DATA EXCHANGE BUFFER NEW SUBSYSTEM RT DITS BUSES OLD SUBSYSTEM RT R T R T OLD SUBSYSTEM T R R OLD SUBSYSTEM RT T R R .

Page 164 APPENDIX B AN APPROACH TO A HYBRID BROADCAST-COMMAND/RESPONSE DATA BUS ARCHITECTURE Received DITS word (32bits) LABEL FIGURE b-(ii) MESSAGE WORD FORMATTING Data stored in buffer (2x16 bits) LABEL Transmitted via 1553A S LABEL S Data stored in buffer (2x16 bits) LABEL Retransmitted via DITS (32 bits) LABEL .ARINC SPECIFICATION 429. PART 1 .

ARINC SPECIFICATION 429.Page 165 APPENDIX B AN APPROACH TO A HYBRID BROADCAST-COMMAND/RESPONSE DATA BUS ARCHITECTURE FIGURE b-(iii) MINIMUM DATA EXCHANGE BUFFER DITS RECEIVER FIFO 1553A TERMINAL 1553 A BUS DITS RECEIVER DITS BUS 1 DITS BUS 2 DITS BUS 3 DITS XMTR . PART 1 .

Page 166 APPENDIX B AN APPROACH TO A HYBRID BROADCAST-COMMAND/RESPONSE DATA BUS ARCHITECTURE FIGURE b-(iv) PROGRAMMABLE DATA EXCHANGE BUFFER BUFFER MEMORY 1553A TERMINAL CONTROLLER DITS RECEIVER DITS RECEIVER Internal Parrallel Data Bus DITS XMTR PROGRAM Address . PART 1 .ARINC SPECIFICATION 429.

Without these elements of information. This raises philosophical questions concerning those characteristics. Sharpe and G. 52406 (319) 395-1000 Cable COLINRAD Cedar Rapids Rockwell International Signal Degradation • Modification Signal to Noise Ratio (MSN) • Static Accuracy Spectral Characteristics • Update Interval • Transmit Interval • Pre-sampling Bandwidth Limit The following discussion of these characteristics should aid the reader in understanding their purpose and assessing their adequacy. Figure 1 illustrates an assumed sensor characteristic. signal degradation. This is necessary from a stability point of view since the converse (that is. Which of these terms appear in the individual equipment specifications and which appear in “429” remains to be determined. The DITS specification seems to be evolving as more than merely a digital bus description since in many ways it is taking on the characteristics of a system interface specification. Iowa. We recognize at the outset that all sensor systems are not 100% linear but this does not prevent us from defining a linear model of sufficient quality to support stability analyses. PART 1 – Page 167 Control Band Magnitude Limits Phase Limits . The phase and gain characteristics provide information about phase and gain margin degradation. it is suggested that control system designers interfacing with digitally bused data should be concerned with three prime areas: stability considerations. Thus far we have implicitly considered both bandpass and lowpass centered at zero frequency. The following eight parameter characteristics should prove adequate for the minimal control of interfacing considerations. 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. The authors cannot resolve such partitioning questions. as outlined below.Collins Avionics Divisions 400 Collins Road. 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. the discussion below will assume low pass sensor characteristics but the ideas apply generally. G. signals narrowband relative to the control band) would introduce excessive phase lag in the control band. however. the control band as used above should be wide enough to include the phase crossover as well as the gain crossover. 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. E. For most sensors the gain crossover in ARINC SPECIFICATION 429. From a control law stability point of view. It is recognized that some changes may necessarily take place as the industry completes its digital interfacing standardization task. and spectral characteristics. which should appear in the individual equipment specifications versus those which should appear in “429”. thorough analysis of system performance will not be possible. Hopefully we can contribute. The detailed discussion in this paper evolves a set of terms (outlined below) which are usable in a specification. For simplicity. to an understanding of what information is required by control systems designers to achieve an acceptable system performance. If we consider open loop Bode plots broken at the sensor output. Introduction and Summary The discussion below summarizes concepts that have grown out of an in-house effort to determine what parameter characteristics Collins feels should be included in the data standards tables of ARINC Bus Specification 429 (DITS). APPENDIX C DIGITAL SYSTEMS GUIDANCE (PART 1) 4 May 1979 A Control System View of ARINC 429 Bus Specifications By T. Here our concern is with those characteristics that are most often used in linear system stability analysis – namely gain and phase characteristics. At the present time. Forquer I. Stability • • • II. NE Cedar Rapids. Stability Consideration There is nothing uniquely digital in this area.

The important stability characteristics are defined concisely below. some sensors may have trouble holding a tight gain (and phase) spec over this wide a bandwidth. 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. With this kind of specification a simple transport delay in combination with a gain change can be used for stability analysis or. The important point here is not to constrain the sensor designer to a first order or second order or any specific implementation. for slightly more complex cases. • . but to rather bound in a simple yet usable sense the stability degradation the sensor can introduce. Phase crossover is not as easily determined.ARINC SPECIFICATION 429. • • APPENDIX C DIGITAL SYSTEMS GUIDANCE (PART 1) Control Band – That band of frequencies over which magnitude and phase characteristics of the sensor are important to the control system stability. However. Magnitude Constraint – The bounds (envelope) on the permissible gain variation in a linear frequency response sense that are permissible over the control band. simple transfer functions can be used to approximately fit the spec. PART 1 – Page 168 typical control laws is known approximately. Phase Constraint – The bounds (envelope) on the permissible phase variation in a linear frequency response sense that are permissible over the control band. Possibly in these cases a loosening of the spec between open loop crossover and ten times open loop crossover may be required.

The other inherent sensor degradation is more difficult to deal with. Signal Degradation SENSOR Process Noise Signal Dependent Noise Sensor Input Internally Generated Noise Sensor Ouput Measurement Error Signal + + f( ) + + + + + + + - APPENDIX C DIGITAL SYSTEMS GUIDANCE (PART 1) In this area we are concerned with what the sensor may have done to degrade the signal. III. In Figure 2 some important sources of signal degradation are illustrated. Installation Noise ARINC SPECIFICATION 429. 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 EMI. Another is nonlinearities that produce harmonic distortion under sine wave excitation as shown in the example below. This aliased energy may also be regarded as noise. The phase and amplitude of this component of this component relative to the forcing function will provide the magnitude and phase information. If amplitude dependent nonlinearities are severe. The thrust here is not stability but performance. PART 1 – Page 169 Figure 2. Within the sensor itself there is internally generated noise such as shot noise from resistors. this procedure yields and empirically derived describing function for the sensor over the control band. Sensor and Signal Characteristic and Measurement Noise . mounting errors. some aliasing of the input signal spectrum will occur. If there is a digital sampling process in the sensor. In the terminology of nonlinear system analysis. A familiar analog example is input amplitude dependent characteristics such as saturation effects that only become significant above certain input amplitudes. for it is signal dependent. The term “noise” is used somewhat loosely in Figure 2 to denote degradation sources. At each frequency the output component of interest (assuming some distortion) will be the output component whose frequency corresponds to the input frequency. however.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. Note that this “noise” can also include bias and drift effects. In a radio receiver this is the kind of noise that is measured at the output when the input is shorted. more than one amplitude of forcing function may have to be used with the procedure repeated at each amplitude. Figure 2 presents a view of sensor and signal characteristics that is useful in this context. that is independent of the input signal. EMI from digital buses. etc. etc.

Amplitude Dependent Nonlinearities APPENDIX C DIGITAL SYSTEMS GUIDANCE (PART 1) y(t) = sinwt ± 2 " k cos2wt 2 Note that d. This effect may or may not be important depending on whether the application permits washing out low frequency components. If a sensor is known to be susceptible to a specific type of noise. Let the sensor output be y(t) = x(t) + kx(t)² Where x(t) is the sensor input and let x(t) = sinwt. Therefore conventional signal to noise over the So band w is given by . If the analog signals originally sampled and put on the bus were sinusoidal at one frequency then. and second harmonic components as well as the forcing frequency appear at the output. Consider square law distortion in an otherwise linear sensor. is only describable as a random process. Exponentially correlated noise of specified variance and correlation time (or bandwidth) should be sufficient in most cases. however. it is suggested that appropriate values for the modified signal to noise (MSN) will be 100 to 1000. Since measurement noise can be dependent on input amplitude as well as spectral characteristics. Roughly. The Po above also represents the motivation for considering square root of the ratio than the ratio directly. 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. A set of tests that will measure these characteristics is described below. e. that noise should be included in the test. Determine the PSD of the measurement error. rms error power is given by Po*w . then rms signal power in the band ∆w is given by So*w. Gusts also can only be described as random processes. The amplitude and number of these spurious outputs is a function of the two sampling rates as well as the input frequency. in a complementary filter. Measurement Error The involved nature of what can happen to the signal within the sensor as shown in Figure 2 is the source of ambiguity in conventional “accuracy” specs. frequency components less than and greater than the input frequency (as well as the input frequency) appear after the second sampler. It should also be apparent that measurement error must be addressed statistically since a significant portion of the input. 1 The approach described above tests for input frequency dependent degradations by Recognizing that a complete description of a random process includes not only probability distributions but also spectral characteristics.g. Define a modified signal to noise ratio (which will be a function of frequency) as the square root of noise ratio at each frequency of signal PSD amplitude to measurement error PSD.1% of signal power at each frequency or noise being 40 to 60 db down from signal. The net effect of all such internal sensor effects is observable by subtracting sensor input from sensor output to yield measurement error as shown in Figure 2. Plot the two PSD’s on a common plot as shown in Figure 3. Often it will be useful to separate out the low frequency or d-c components of measurement error since these may be more tolerable in some applications than dynamic errors. The relationship between MSD and ordinary signal to noise can be understood by assuming both signal and noise PSD’s are flat over a band of frequencies ∆w as shown in Figure 3. Determine the power spectral density (PSD) of the input signal to the sensor. Requiring that this signal to noise be 100 is equivalent to Po requiring that noise power be 1% of signal power over this band. Then y(t) = sinwt + ksin²wt k Modified Signal to Noise Ratio (MSN) Force the sensor with random noise of specified rms value (σ) and correlation time (τ). In the range of frequencies where accurate sensor response is required.c. Carrying this o back to the MSN implies that MSN (w) = = 100 Sover the band ∆w.ARINC SPECIFICATION 429. such as signals being received at one rate from a digital bus and being used at a different rate by a software program. it is not possible to specify it with a single and simple metric. these numbers correspond to noise power being 1% to . Let the value of the signal PSD in this band be So. Note in the example shown in Figure 3 there is a bulge in the measurement error around zero frequency.1 Technically the input signal is also in general a random processes influenced by such things as the gust striking the aircraft. It should be realized that if there are . In digital systems a similar effect occurs when multiple rates are introduced. Similarly. in general. providing a realistic input spectrum. process noise. This effect would indicate d-c bias and possibly low frequency bias drift from the sensor.

the control is carrying the system to a prescribed state rather than maintaining it at a prescribed state in the presence of noise. It is suggested that the MSN measurement be done with worst case input noise. Empirically determined power spectral densities (using discrete Fourier Transform techniques) will need to be measured for input signal as well as measurement error. Spectral Characteristics APPENDIX C DIGITAL SYSTEMS GUIDANCE (PART 1) In this area the digital nature of the system interface must be faced squarely.amplitude dependent degradations. Normally an exponentially correlated signal with specified variance will be sufficient. MSN(w) = MSN (w) = MSN ∆ Modified Signal to Noise Ratio Fig re 3 Modified Signal to Noise Ratio . The amplitude dependent degradations should be measured statically -. a larger percentage from .155 DDM. • Measurement Error – The difference between the signal impinging on the sensor and the output representation of that signal by the sensor expressed in consistent units. the MSN analysis will yield different answers depending on the rms value of the input noise. Only the last two are proposed as parameter characteristics--the first three being definitions to clarify the last two. A good example here is localizer receiver linearity. SPSD (w) MEPSD (w) Modified Signal to Noise (MSN) determination requires assuming a random process model for the signal impinging on the sensor.that is. Such a specification is important in defining localizer capture laws. Measurement Error PSD (MEPSD) – The power spectral density of measurement error introduced by the sensor. and measure the output value.155 to . Normally the latter operation will require more accurate information from the sensor.Page 171 Signal Power Spectral Density ( SPSD(w) ) So • • • A M P L I T U D E Po (rms = s ∆w ) 0 Measurement Error Power Spectral Density ( MEPSD(w) )  rms =    p ∆w   0 frequency w w SPSD (w) MEPSD (w) i. The important signal degradation terms are defined concisely below.e. one should provide a test input at specified amplitude. • 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.310 DDM and not decreasing between .310 and . PART 1 . Static accuracy measurement was described above.. Modified Signal to Noise Ratio – A measure primarily of the spectral characteristics of sensor errors defined as the square root of the ratio of SPSD and MEPSD at each frequency in the control band. where one can begin “using” the signal crudely before it is linear or precisely accurate.. largest rms and bandwidth that will be encountered.e. i. In some cases alternate MSN specs for different flight regimes may be appropriate. specified as being linear within a given percentage up to . Signal PSD (SPSD) – The power spectral density of the signal impinging on the sensor. allow transients to settle. i.400 DDM. Potential Measurement Technique In many cases a more explicit presentation of the amplitude dependent nonlinearities may be desirable. It should be noted that this is a slightly different use of sensor data than for precise state control.e. The control system designer cannot alter the signal degradation introduced by ARINC SPECIFICATION 429. IV.

Recall that white noise through a lowpass filter yields a PSD that rolls off at 40 db/decade as shown below. The “aliasing” in the spectrum F2 (s) occurs because the second sampler is not operating on a properly band limited function (see Figure 4) due to the “infinite replica” nature of the spectrum F2 (s). To analyze aliasing precisely he would need a precise definition of the spectrum of each signal being received on the digital bus including the update interval for each signal. is an infinitely replicated version of the analog input spectrum with replicas spaced by the input sampling frequency F1. Figure 5 then illustrates the bound on bused signal PSD that is envisioned. These ideas are made more precise below. noise. We cannot. Deriving the spectrum of the signal F2 (s) is beyond the scope of this discussion but a technique has been developed that will yield this spectrum. Assuming F2 is somewhat fixed by computer speed and loading considerations. and the shape of the repeated spectrum of F (s) in F1 (s). not only this spectrum but also the frequency F1 enters into the aliasing in F2 (s).Page 172 F(S) A n a l o g Input Spectrum S The discussion above did not specify whether the original analog quantity was a deterministic signal or a random process. therefore. Deterministic Versus Random Signals τ2w2+1 Adequate roll off chracteristic of the digitally bused data reduces the aliasing problem of the second sampler if the second sampling is properly performed. We note that the spectrum of the signal on the bus. as measured at the DITS bus interface. F1 (s). aliasing can be minimized for a given input spectrum by making F1 as high relative to F2 as possible. for making matters worse if he is not alert to potential aliasing problems that he may introduce. F2. therefore. f22 ) for both F1 and F2. However. However. it is desirable also to carefully specify F1. APPENDIX C DIGITAL SYSTEMS GUIDANCE (PART 1) • Update Interval – The cyclic time interval. The important spectral characteristic terms are defined concisely below. given the quantities F1. PART 1 . For deterministic cases we deal with the Fourier transforms of the signals involved. between transmissions of new freshly sensed and converted/derived values of the parameter. F2 (s). Multirate Sampling A simple model for signals received from a bus and used in a digital processor is shown in Figure 4. speak of the bandwidth of F1 (s) strictly. etc. He has great potential. What we mean here is that a bound is required on each copy in F1 (s).the sensor whether it be due to nonlinearities. This will be accomplished through the update interval. aliasing. Sampler Sampler Analog Quantity F(S) f1 F (S) 1 Digital Register F 2 (S) f2 Software Fetch Bused Signal ARINC SPECIFICATION 429.∞ < w < + ∞ Filter Transfer Function: T (jw) = 1 Jτw+1 Output PSD: Y (S) = T(S)T*(S)U(S) Y(w) = A -2f 1 -f 1 -f c fc f1 2f 1 S Figure 4 Analysis of Multirate Sampling . For this case the development must proceed in terms of power spectral density of the signals involved. A more practical approach is to place an upper bound on the received signal spectrum and then ensure downstream performance is adequate using this bound as the signal spectrum. There is considerable spreading of signal energy in this process with considerable “aliasing” potential even if the quantity fc in Figure 4 is much less than the Nyquist frequency ( f21 . however. White Noise Input PSD: U(S) = A . as pointed out in Section III the signals of interest are really describable only in terms of random processes.

Page 173 • Transmit Interval – The cyclic time interval. PART 1 . 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. Transmit Interval ≤ Update Interval. as measured at the DITS bus interface. • Power Spectral Density 40 db/decade APPENDIX C DIGITAL SYSTEMS GUIDANCE (PART 1) Frequency Pre-Sampling Bandwidth Limit w Note: Periodic Function Only Positive Half of Zero Centered Component Shown (see Figure 4) Figure 5 PSD Bound on Bused Signal .ARINC SPECIFICATION 429. between transmissions of the parameter.

It is intuitively obvious that the interval between samples affects the accuracy with which the continuous time data is represented by the discrete samples. Washington 98124 M/S 47-09 A Division of The Boeing Company Attachment to SYST-B-8764-20-075 May 11. The revision addresses the topic of aliasing which could occur when reducing the sampling rate of a digitally encoded signal. F. signal-to-noise ratio.Page 174 BOEING COMMERCIAL AIRPLANE COMPANY P. Analog systems are said to operate in the continuous time domain while digital systems are said to operate in the discrete time domain. Norwood. B. and system complexity. transport delays and minimum update rates for digital and noise characteristics are discussed. In order for discrete time digital systems to be used to process or transfer the inherently continuous time data from real world physical systems. instruments and actuators. These samples from discrete points in time can then be used as the input to the discrete time digital system. 2551 Riva Road Annapolis. Chief AFN: Enclosure BOEING BOEING . Maryland 21401 Dear Rick: The enclosed paper is a revised version of “Design Parameters for Digital Avionic Systems. processing and filtering signals from navigation and other sensors. Chairman Airlines Electronic Engineering Committee Aeronautical Radio. and filtering of data prior to its display on cockpit instruments. These functions include inner and outer servo loops for aircraft control and guidance. 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. sensors.O. A. samples of the continuous data must be taken at periodic intervals. Sincerely AIR TRAFFIC CONTROL AND ELECTRONIC SYSTEMS Summary APPENDIX D DIGITAL SYSTEMS GUIDANCE (PART 2) This paper explains the necessity for defining presampling filter characteristics. PART 1 . This topic was discussed at the DITS working group meeting held on April 18 and 19. R. signal delay. An understanding of the Sampling Theorem is necessary in order to make the proper trade offs between sampling rate.” which was originally circulated with AEEC letter 79022/SAI-99. Introduction The new generation of commercial aircraft will use digital technology to implement many functions.ARINC SPECIFICATION 429. 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. A design procedure for selecting the required filter characteristic and update rate is presented. Box 3707 Seattle. which were traditionally performed with analog hardware. 1979 SYST-B8713-79-209 DESIGN PARAMETERS FOR DIGITAL AVIONIC SYSTEMS Prepared by Boeing Commercial Airplane Company REVISION A Mr. Digital technology will also replace the majority of the formerly analog communication paths between systems. Inc. Climie.

The filter order is an important design parameter because higher order filters roll off more rapidly near the cutoff frequency. complexity. It also increases the delay experienced by signals as they propagate through the system. high order filters delay the signal more than low order filters. 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. This curve forms a baseline against which signal-to-noise ratio degradation caused by aliasing can be compared. and the bandwidth of the system which uses the data. 1/Ts. The ultimate objective of the design task discussed in this paper is to achieve acceptable system performance with the minimum possible APPENDIX D DIGITAL SYSTEMS GUIDANCE (PART 2) ARINC SPECIFICATION 429. Therefore. This relationship is shown in Figure 3. Therefore. which represent physical quantities. available computational resources. Design Tradeoffs for Digital Avionics Systems The final choices of sample rate and presampling filter depend upon the input signal and noise spectra. Therefore exact reproduction of the original signal from its samples is not possible. 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 increase in delay reduces phase margin if the signal is used in a closed loop control system. maximum allowable signal-to-noise ratio degradation due to aliasing. the output spectrum is found by convolving the input spectrum with the spectrum of the impulse train. 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. The shaded area shown in Figure 4 represents typical high frequency signal energy which distorts the low frequency portion of the signal spectrum. which increases the weight. This requires more computational resources. which has a wider bandwidth than the signal. The use of a presampling filter to limit the bandwidth prior to sampling distorts the signal. 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. An increase in the sampling rate requires more computations to be done in a given period of time. Therefore. The required identity states that time domain multiplication is equivalent to frequency domain convolution. The high frequency portion of the signal takes on the identity of the lower frequencies. 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. Because of this characteristic. high order filters alias no more noise into the signal than slightly narrower bandwidth low order filters. However. which is passed by the selected prefilter. The reason for this requirement can be shown by examing the frequency spectrum of the sampler output. Aliasing becomes a greater problem when the signal is corrupted by noise. and power requirements of the computer subsystems. more stringent delay requirements must be placed on other components in the loop if the system phase margin is to remain constant. 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. hence the name “aliasing” for this phenomenon. signals. A typical plot of signal-to-noise ratio versus presampling filter bandwidth is shown in the top curve of Figure 6. such as those processed by avionic systems never satisfy the strict bandwidth limitation requirement stated above. The initial computation is to determine the effect of the prefilter on the inband signal-to-noise ratio without regard to aliasing effects. 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. the spectral component centered about zero. PART 1 .Page 175 . Therefore higher order filters admit less noise and signal from beyond the cutoff frequency than low order filters. maximum allowable transport delay. 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. 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. This parameter will generally exhibit a peak value at a specific bandwidth. Neither of these approaches can ever completely eliminate the effect of aliasing and they each result in some negative impact on the overall system. can be exactly represented by a series of samples spaced no further apart than ½ fo seconds.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. A practical way to make these choices is to analyze the system for various sample rates and filters. The signal-to-noise ratio is determined by computing the input signal power and input noise power. This is equivalent to requiring that the sampling frequency be greater than twice the highest frequency component of the signal. If the sampling frequency. However. 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. The effect of the non-bandlimited nature of signals is to distort the replica reconstructed from the samples. This effect is shown in Figure 5.

) This minimum bandwidth is plotted on Figure 6 as a vertical line. Signal and noise spectra of the signal to be sampled must be supplied as an input to the design procedure.. Some systems which use sampled data. A typical plot of this type is shown in Figure 7. Filtering in the Time and Frequency Domains. 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. System performance is adversely affected by large propagation delays and high in-band noise levels. such as closed loop control systems. a sampling rate of 50Hz would be chosen. PART 1 . the signal-to-noise ratio which would be achieved by an unsampled system. In some situations it may be desired to reduce the sampling rate of a digitally encoded signal. Sampling rate is chosen by comparing the maximum acceptable degradation in signal-to-noise ratio to the actual aliasing degradation due to sampling at the candidate rates. If the maximum allowable propagation delay is given.Page 176 sampling rate. The aliasing can be elimination of the unwanted samples. The values are chosen to meet the constraints of maximum allowable delay and maximum allowable noise due to aliasing. For the example shown in Figure 6. have a bandwidth which is much smaller than that of the sampling filter. 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. For this reason it is important to verify that the signal and noise power which is aliased into the frequency band of interest is well below the inherent noise in that band. New York. John Wiley and Sons. Zverev. page 112. Reference: Herman J. The intersection of the minimum bandwidth line with the top curve of Figure 6 gives the maximum achievable signal-to-noise ratio i. Design of the digital filter is subject to the same set of delay versus aliasing noise tradeoffs as the design of an analog presampling filter. The example power spectral densities in Figure 7 show that the aliased signal and noise is much lower than the inherent noise level in the frequency range of interest. the minimum usable filter bandwidth can be found standard plots of group delay versus frequency for the type and order of filter considered. The power spectral density plot is most easily obtained with the aid of a computer program. If this constraint is not met a different combination of filter and sampling frequency must be chosen. (See for example Reference 1. Analog Input Analog Input Analog System Analog Output APPENDIX D DIGITAL SYSTEMS GUIDANCE (PART 2) Analog Output time Figure 1(a) Typical Input and Output of Analog System time Digital Input (discrete values) Digital System Digital Output (discrete values) Digital Input time Figure 1(b) Typical Input and Output of Digital System time . A system interface which meets prescribed limits on signal delay and maximum noise due to aliasing can be designed using the procedures outlined above. This can be accomplished by constructing a signal and noise power spectral density plot for the filter and sampling rate chosen. 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. This may be done where wideband digital data is used to drive an instrument or subsystem which responds only to narrower bandwidth data.ARINC SPECIFICATION 429. Blinchikoff and Anatol I.e.

. PART 1 .- . n=−∞ ∑ ∞ Ts δ (t − nTs ) Rs(f) signal recovery ....- Figure 5(a) Input Signal and Noise Spectra f ARINC SPECIFICATION 429.1 -fo + fo 0 fo 1 -f o 1 f − 1 0 1 Ts .- .1 0 1 2 Ts Ts Figure 3(b) Spectrum of Input Train.1 Ts Ts Ts 2T s 2T s Figure 5(b) Output Signal and Noise Spectra Showing Signal-to-Noise Ratio Degradation Due to Aliasing of Signal and Noise Figure 3(c) Spectrum of Sampling Output ..r (t) X rs(t) δ (t − nTs ) Low Pass Bw = oHz r (t) n = −∞ Figure 2 Mathmatical Model of Sampling Process ∑ ∞ − 2 T − s 1 T − s 1 2T s 0 1 2T s 1 2 s f s T T R (f) Figure 4 Sampler Output Spectrum When Input Signal Bandwidthis not Limited to One-Half of the Sampling Frequency APPENDIX D DIGITAL SYSTEMS GUIDANCE (PART 2) Input Noise Spectrum -fo 0 fo 1 2T s 1 2T s Input Signal Spectrum Figure 3(b) Spectrum of f(t) Bandlimited to fo Hz ℑ{ n = −∞ ∑ ∞ − δ ( t − nTs )} 0 .Page 177 - 2 Ts .

PART 1 .ARINC SPECIFICATION 429.Page 178 APPENDIX D DIGITAL SYSTEMS GUIDANCE (PART 2) .

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. 3. the labels should be selected from the following subgroups: Binary coded decimal (BCD) sub-group 001 to 067. Where word grouping is not possible. for example. 167. 126 to 144. 267.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. 171 to 177. 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). 046 047 051 052 055 057 113 124 167 226 240 243 040 050 054 107 163 227 371 Where possible. The following labels are presently “spare” and should only be used for new parameters which may have very widespread usage throughout the airplane architecture. 350 to 354 Test word subgroup 266. The use of the same label for two different functions on a particular LRU type built by different manufacturers can create serious problems. 262 to 265. 270 to 276 Maintenance and discrete data subgroup 155. 240 to 257. min--max transmit interval). 1. It is important that each new usage of ARINC 429 be coordinated and indexed by ARINC such that the information on usage (label allocation. range. New labels should be selected from the five character field as defined in Section 2. The following labels have special significance and should not be used: label 000 (not used) and label 377 (equipment identification). 5. 360 to 376. Mixed BCD and BNR subgroup 260. PART 1 . To facilitate the coordination of ARINC 429 label usage between the industry and the ARINC staff. grouped usage should have identical data specification (units.ARINC SPECIFICATION 429. 166. 310 to 347. positive sense. resolution.) is available industry-wide. 201. . 170. etc. Where possible. 005 c-16 006 007 4. data format. 202 to 227.3 (three octal and three hexadecimal). 162 to 164. 165. 125. a set of guidelines is provided. 156 Maintenance data subgroup 157 to 161. Binary (BNR) subgroup 070 to 124.230 to 237. 2. similar word usage should be “grouped”. 200. 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. 150 to 154. significant digits/bits. 261 Discretes subgroup 145 to 147.

Digits 00 01 02 03 04 05 06 07 10 11 12 13 14 15 16 17 20 21 22 23 24 25 26 27 30 31 32 33 34 35 36 37 / / / / 0 X 1 2 3 4 5 6 7 10. Least Significant Digit Two Most Sig. if one exists.1. as described in 2. BCD BNR Discretes Maintenance data Test Application dependent Acknowledgement Maintenance ISO #5 ISO #5 message 8. PART 1 . BCD BNR BCD MAINT MAINT BCD DATA DISCRETE DISC M DATA BCD BNR MIX DISCRETE APPLICATION DEPENDENT BNR MAINT DATA BNR EQ ID ACK M ISO ISO5 TEST TEST . The equipment ID should be allocated as the two least significant digits of the 7XX ARINC equipment specification. The SDI code should indicate the aircraft installation number of the source equipment. Allocation of bits within words. For equipment not otherwise covered by an ARINC Specification. 9. 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. Equipment ID of 000 (HEX) should not be used. as defined in the appropriate sections. an equipment ID should be allocated with a non-numeric value of the hexadecimal character set as the least significant digit. 11. in a multi-system installation.ARINC SPECIFICATION 429.4.Page 180 APPENDIX E GUIDELINES FOR LABEL ASSIGNMENTS 7.

13. 1977 in Arlington.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. 2 of Project paper 429. Washington Whither On-Board Digital Data Transmission Standards? More On Digital Data Transmission Standards Boeing Report On Alternative Digital Information System Signalling Standards Report of the Systems Architecture and Interfaces Subcommittee Meeting Held March 7th. 5) and graphic data handling also. X-2. 76-130/SAI-20 77-009/SAI-22 77-020/SAI-25 N77-035/SAI-26 77-037/SAI-28 77-047/SAI-33 77-056/SAI-37 77-066/SAI-41 77-079/SAI-46 Date Dec. in Annapolis. produced the second draft of the spec. These subjects would be addressed in a Supplement to the spec which AEEC would be asked to approve at a later date. With respect to this last-named.0 Bibliography The following is a list of AEEC letters associated with the preparation of ARINC Specification 429.ARINC SPECIFICATION 429. The spec adopted by AEEC contained details of numeric data (BNR and BCD) transfer only. 1977 in Los Angeles. 10th and 11th. A second working group meeting during the period of that Subcommittee meeting. described in ARINC Specification 419. followed by a third in mid-June. Part of this activity was the definition of black box interface standards. The SAI Subcommittee notified AEEC of its intent to broaden the scope of the document to cover alpha/numeric (ISO Alphabet No. 23. “Digital Data System Compendium”. 1977 Jun. 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. California Circulation of Draft No. 27. 1977 Mar. I of Project Paper 429. Maryland Report of the Systems Architecture and Interfaces Subcommittee Meeting Held May 9th. 18. 1977 Feb. A list of AEEC letters related the SAI Subcommittee's overall activities may be found in ARINC Report 299. The Subcommittee AEEC established to do this began its work in January 1977. 8. This group met early in April 1977. the Subcommittee soon determined that the industry’s previous approaches to digital information transfer. needed rationalization and modernization to be applicable in the future digital systems world. 9. which was achieved at the Summer 1977 General Session in July. However. 21. Virginia Circulation of Draft No. to define digital system interface standards. “AEEC Letter Index”. AEEC Letter No. 1977 Jun. 1976 Jan. 1977. 25. 1977 Apr. PART 1 . this work was not started immediately because of the need to concentrate on the more basic tasks related to digital systems architecture. 8th and 9th. 1977 Subject Report of the Systems Architecture and Interfaces Subcommittee Meeting held November 16th. 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. “Mark 33 Digital Information Transfer System (DITS)” . 1976 in Seattle. and this brought into sharp focus the need for the new digital information transfer system to be properly specified. and produced a draft which the full Subcommittee reviewed at its meeting in May.Page 181 APPENDIX X CHRONOLOGY & BIBLIOGRAPHY X-l. 17th and 18th. This draft was submitted to AEEC for adoption. “Mark 33 Digital Information Transfer System (DITS)” Report of the SAI Subcommittee BITS Working Group Meeting Held April 5-6. 11. 1977 Mar. About a year later. 1977 Apr.

AIR TRANSPORT ASSOCIATION ARMA DIV. Ohio Annapolis. New York Studio City. Maryland . Maryland The following people attended one or more of the SAI Subcommittee meetings held November 16th-18th. INC. Humphrey Robert K. Tom Ellison Wolfgang Bull Siegmar Gomille Jim Wahlen Tony Martin Frank Rasmussen Ed Schroeder Arvind Dandekar Bill Harts David Lewis Ralph Bazil Hal Pierson Bob Clark Capt. DELCO ELECTRONICS KING RADIO CORPORATION MITRE CORPORATION SPERRY FLIGHT SYSTEMS USAF AERONAUTICAL RADIO. D. Manufacturers and Others Bernard E. Thompson AEROSPATIALE AEROSPATIALE AIRESEARCH MFG. Washington Seattle. ROCKWELL INT. PART 1 . INC. France Toulouse. INC. R. March 7th9th. Russell III S. France Orly Aerogare. California Saint Cloud. Davidson Gerard Collin Jean Baptiste Rigaudias Jean Le Luc Clarence L.Page 182 APPENDIX X CHRONOLOGY & BIBLIOGRAPHY X-3. Germany Jamaica. Missouri Denver. New York Kansas City. Wisconsin Olathe. S.0 Meeting Attendees The following people comprised the SAI Subcommittee’s Digital Information Transfer System Working Group. Hitt Brendan J. Featherstone C. Urie W. Maryland Annapolis. Netherlands Hamburg. Florida Seattle. ROCKWELL INT. R. Richmond Robert M. Iowa Cedar Rapids. Maryland Annapolis. New York Stockholm-Bromma. Sporn Robert L. San Francisco. COLLINS RADIO. T. California Montreal. Puteaux. Lorie Ludwig Kilchert Norton Codish Vic Persson Karl H. H. Canada Orly Aerogare. AIR FORCE UTA WESTERN AIRLINES AERONAUTICAL RADIO. H. Brecht O. Carnes B. Arizona Dayton. California Annapolis. Georgia Barajas-Madrid. H. D. Colorado San Francisco. 1976. Toulouse. Ellison. Germany Hamburg. during which the 429 DITS spec drafts and other proposals produced by the DITS working group were reviewed. Lauderdale. Spain Amsterdam. France Orly. Jackson L. Bouet Jean Tambareau Russell Fine William M. Evans C. BENDIX AVIONICS DIV. BENDIX AVIONICS DIV. Germany Ft. France Tulsa. Washington Seattle. Cook Jose M. Florida Ft.ARINC SPECIFICATION 429. Iowa Milwaukee. Florida San Francisco./AMBAC AVIATION CONSULTANT AVIONS MARCEL DASSAULT BENDIX AVIONICS DIV. refined and finalized.C. France Torrance. California Ft. Ahmann T.S. Chairman J. Sweden Jamaica. Tinsley UNITED AIRLINES AIR CANADA AIR FRANCE AIR FRANCE AIR INTER AMERICAN AIRLINES DELTA AIRLINES IBERIA SPANISH AIRLINES KLM AIRLINES LUFTHANSA GERMAN AIRLINES PAN AM WORLD AIRLINES SCANDINAVIAN AIRLINES SWISSAIR TWA UNITED AIRLINES UNITED AIRLINES UNITED AIRLINES UNITED AIRLINES U. France Los Angeles. W. R. R. 1977 and May 9th-11th. CO. Spratt William C. California San Francisco. Daniel Jean Francois Ferreri Jay J. E. Maryland Annapolis. Oklahoma Atlanta. Russ Glastetter David Featherstone UNITED AIRLINES DEUTSCHE LUFTHANSA DEUTSCHE LUFTHANSA BENDIX AVIONICS BOEING BOEING BOEING COLLINS RADIO.C. AERONAUTICAL RADIO. California Washington. Garden City. California Burbank. France Burbank. Moyers Claude Gouillon Wallace L. California San Francisco. Clime D. 1977. Kansas McLean. Recacha P. C. INC. California Hamburg. Lauderdale. Riesen T. Lauderdale. BENDIX AVIONICS DIV. AERONAUTICAL RADIO. AERONAUTICAL RADIO. Washington Cedar Rapids. A. Airlines and ARINC Staff T. Berryhill M. INC. Virginia Phoenix. California Washington.

Gussin Arvind J. David Lewis John H. California LITTON AERO PRODUCTS Woodland Hills. Washington BOEING COMMERCIAL AIRPLANE Seattle. California HAMILTON STANDARD Windsor Locks. Reese E. Hall Bryand C. Wisconsin DELCO ELECTRONICS DIV. C. Roquefeuill Jack Hawkins J. California LOCKHEED CALIFORNIA CO Burbank. California LOCKHEED CALIFORNIA CO Burbank. Connecticut HAWKER SIDDELEY AVIATION Hatfield. D. Lent Michel Pascal Richard A. Washington BOEING COMMERCIAL AIRPLANE Seattle. Minnesota HONEYWELL INC. California . California BOEING COMMERCIAL AIRPLANE Seattle. Singleton P. Washington BOEING COMMERCIAL AIRPLANE Seattle. California LOCKHEED CALIFORNIA CO Burbank. California E-A INDUSTRIAL CORP. Canada COLLINS RADIO GROUP Cedar Rapids. C. V. Lakewood.C. Washington BENDIX CORP. Virginia PRATT & WHITNEY AIRCRAFT East Hartford. California LITTON AERO PRODUCTS Seattle. Sheldrick Tom Sizlo John Carter David Burton Roy F. T. Weinheimer William R. Hillman Ed Selvig Barry J. Iowa COLLINS RADIO GROUP Cedar Rapids. GMC Milwaukee. Minnesota ISPENA Paris. Iowa CROUZET Pasadena. Weir Richard Haley S. Washington BOEING COMMERCIAL AIRPLANE Seattle. California ELDEC CORPORATION Lynnwood. Chamblee. FLIGHT SYSTEMS Teterboro. Caliendi Harry Graves Ronald G. UK MARCONI ELLIOTT AVIONICS Seattle. Washington BOEING COMMERCIAL AIRPLANE Seattle. Wickenkamp John F. Florida BENDIX CORP. Schroeder V. J. California KING RADIO CORP Olathe. New Jersey BENDIX CORP. England HONEYWELL INC. Montreal. Lucchi BENDIX AVIONICS DIV. GMC Milwaukee. California ELDEC CORPORATION Lynnwood. California ELECTRONIQUE MARCEL DASSAULT Saint Cloud. France ITT CANNON ELECTRIC Santa Ana. Dwayne Broderson James R. Hawkins Eugene C. Keating Rene Plouhinec John E. Washington BOEING COMMERCIAL AIRPLANE Seattle. Horan G. Lauderdale. Nelson John C. California GARRETT AIREASEARCH Torrance. FLIGHT SYSTEMS Tukwila.ARINC SPECIFICATION 429. France FAA Washington. Washington BOEING COMMERCIAL AIRPLANE Seattle. Martin J. UK MARCONI ELLIOTT AVIONICS Rochester Kent. H. Minneapolis. Whalen Howard E. Donaldson J. Torrance. California ITT CANNON ELECTRIC Santa Ana. J. Langenback Ray Swanson Ken Berg David A. St. New Jersey BENDIX CORP. Pierson Richard W. England CANADIAN MARCONI CO. New Jersey BENDIX LONG BEACH FAC. California CROUZET Valence. England BRITISH AEROSPACE Hatfield. Rasmussen Irving R. Keall Donald J. Ft. A. Iowa COLLINS RADIO GROUP Cedar Rapids. California JAEGER Pasadena. Beckman Jerry Doniger Ken Kendall Albert T. GARRETT CORP. Washington BOEING COMMERCIAL AIRPLANE Seattle. California MARCONI ELLIOTT AVIONICS Rochester Kent. J. Washington MESSERSCHMITT-BLOKOW-BLOHM Hamburg. F. Raymond Claude P. McHutchison Richard A. Sutton Ray Hillman Richard A. Bedell Jr.Page 183 APPENDIX X CHRONOLOGY & BIBLIOGRAPHY James C. Wisconsin DELCO ELECTRONICS DIV. FLIGHT SYSTEMS Teterboro. Allen Donald L. PART 1 . Wisconsin DOUGLAS AIRCRAFT COMPANY Long Beach. Washington LOCKHEED CALIFORNIA CO Burbank. Johnson L. Washington BRITISH AEROSPACE Surrey. Washington BOEING COMMERCIAL AIRPLANE Seattle. France DELCO ELECTRONICS DIV. Cotton L. Beckman Job Van Der Bliek Wm. Gorman Anthony J. Aldridge Gordon Belcher Derek Marshall Karl-Heinz Terheiden Harold L. FLIGHT SYSTEMS Teterboro. Kansas KING RADIO CORP Olathe. Peal Frank A. Kirchhein Harry W. Germany MITRE CORPORATION McLean. Fries R. Washington BOEING COMMERCIAL AIRPLANE Seattle. Louis Park. Iowa COLLINS RADIO GROUP Cedar Rapids. New Jersey BENDIX CORP. Machacer Donald H. Telsch Gary C. Reed Charles Sheets Robert E. Herts. Virginia MITRE CORPORATION McLean. Small Robert W. Dandekar R. GMC Milwaukee. FLIGHT SYSTEMS Teterboro. Kansas LITTON AERO PRODUCTS Woodland Hills. Iowa COLLINS RADIO GROUP Cedar Rapids. Connecticut RCA Van Nuys. Iowa COLLINS RADIO GROUP Cedar Rapids.

ARINC SPECIFICATION 429, PART 1 - Page 184 APPENDIX X CHRONOLOGY & BIBLIOGRAPHY

Gerard A. Collin Lloret Jean-Yves Begeault Jefferson Z. Amacker Joseph Koprowski John Desmond Dave Richardson Brian Williams Mike C. Pietromonaco Donald Baker Don Burkholder Jack E. Emfinger D. A. Few Martin S. Klemes R. J. Lofquist Harry Miller Ronald H. Neeves Edmond Olive R. E. Schaffer Harry O. Smith Al J. Venancio Lou Borbely Glenn H. Jones Robert Schaeperkoetter C. A. Bennet H. E. Sutherland D. A. Giroux Charles Legrand J. Ribiere J. Lane Ware William Donnell R. R. Fay Jean-Pierre Tomasi Blaine C. Ferch Erwin C. Gangi Capt. R. A. Glastetter

SAGEM SAGEM SFENA SINGER KEARFOTT SINGER KEARFOTT SMITHS INDUSTRIES INC. SMITHS INDUSTRIES INC. SMITHS INDUSTRIES INC. S. P. INC SPERRY FLIGHT SYSTEMS SPERRY FLIGHT SYSTEMS SPERRY FLIGHT SYSTEMS SPERRY FLIGHT SYSTEMS SPERRY FLIGHT SYSTEMS SPERRY FLIGHT SYSTEMS SPERRY FLIGHT SYSTEMS SPERRY FLIGHT SYSTEMS SPERRY FLIGHT SYSTEMS SPERRY FLIGHT SYSTEMS SPERRY FLIGHT SYSTEMS SPERRY FLIGHT SYSTEMS SUNSTRAND DATA CONTROL SUNSTRAND DATA CONTROL SUNSTRAND DATA CONTROL TELEDYNE CONTROLS El TELEDYNE CONTROLS El THOMSON-CSF THOMSON-CSF THOMSON-CSF THOMSON-CSF TRACOR APPLIED TECHNOLOGY TRACOR APPLIED TECHNOLOGY TRT USAF USAF USAF

Paris, France Paris, France Velizy-Villacoublay, France Little Falls, New Jersey Little Falls, New Jersey Clearwater, Florida Clearwater, Florida Cheltenham, Glos, UK Bellevue, Washington Phoenix, Arizona Phoenix, Arizona Phoenix, Arizona Phoenix, Arizona Phoenix, Arizona Phoenix, Arizona Phoenix, Arizona Phoenix, Arizona Phoenix, Arizona Phoenix, Arizona Phoenix, Arizona Phoenix, Arizona Redmond, Washington Redmond, Washington Redmond, Washington Segundo, California Segundo, California Les-Moulineaux, France Les-Moulineaux, France Malakoff, France New York, New York Austin, Texas Austin, Texas Le Plessis-Robinson, France Wright Patterson AFB, Ohio Dayton, Ohio 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 INTRODUCED BY THIS SUPPLEMENT 429 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.

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

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. 10 0 0 1 1 . 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. 31 0 0 1 1 30 0 1 0 1 Designation BNR/BCD Data Plus, North, East Right, To No Computed Data Functional Test Minus, South, West, Left, From ISO # 5 Data 9 0 1 0 1 System 1 2 3 4 Notes: 1. A source system should indicate failure by ceasing to supply data to a bus. 2. 3. Both bits should be “zero” in BNR and BCD words when no sign is needed. The “no computed data” code should be generated when computed data is not available for reasons other than equipment failure. 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 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.

4.

2.1.6 Data Standards Typographical errors corrected in second paragraph of Commentary. 2.2.1 Transmission System Interconnect Existing material supplemented 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. with information

TBD

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 multipleword 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 “c2” 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 INTRODUCED BY THIS SUPPLEMENT 429 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 AIM/Discrete/Maintenance data word 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. Bit No. 31 0 0 1 1 30 0 1 0 1 Designation ISO #5 BNR/BCD Data Data Plus, North, East Initial Word Right, to No Computed No Computed Data Data Intermediate Functional Test Word Minus, South, West Final Word Left, From for type

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.2 INFORMATION ELEMENT Text revised to describe word application groups. 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

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 ceasing to supply the affected word or words to the data bus. 2. 3. Both bits should be “zero” when no sign is needed. 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. See Section 2.3.1.3 of this document for definitions of the terms “Initial Word”, “Intermediate Word” and “Final Word”. 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 significant bit. Attachment 6 shows this against the 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.

5.

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. 31 0 0 0 1 1 1 1 0 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. Bit no. 29 should be “zero” when no sign is needed. The “no computed data” code should be generated when computed data is not available for reasons other than equipment failure. 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. Bit No. 30 29 0 0 1 0 0 1 1 1 0 1 0 0 1 0 1 1 Designation BNR Data Failure Warning/Plus, North, East Right, To Failure Warning/Minus, South, West, Left, From No Computed Data Functional Test/Plus, North, East, Right, To Functional Test/Minus, South, West Left, From Normal Operation/Plus, North, East, Right, To Normal Operation/Minus, South West, Left, From Not Used (Growth)

2. 3.

4.

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 MATRIX PARITY (odd) RESERVED (SDI) 10 9 0 0 LABEL Beacon Transponder Code

Bit No. Example

32 0

31 30 0 0

29 28 27 0 1 1

26 25 24 23 0 1 1 0

22 21 20 19 0 0 1 1

18 17 16 15 0 0 0 0

14 0

13 0

12 0

STANDBY

IDENT

0.7 (3)

0.7 (6)

0.7 (2)

0.7 (0)

11 0

8 7 6 5 4 3 2 1 1 1 0 1 1 0 0 0

[1] [1] Bit 11 12 13 14 Zero Alt. Rep. ON Standby OFF Ident OFF Select Mode A One Alt. Rep. OFF Standby ON Ident ON 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) 007 014 015 016 017 024 027 041 042 043 044 045 100 107 110 112 124 130 131 132 133 145 146 147 166 203 204 214 216 220 221 223 224 225 226 227 234 235 236 237 241 242 245 247 270 271 272 273 274 334 340 346 350 351 352 353 354 355 356 357 360 372 373 374 375 376

Original Assignment Align Status/Inertial Discretes None assigned None assigned None assigned None assigned Selected Course None assigned None assigned None assigned None assigned None assigned None assigned Selected Course AFS Discretes None assigned None assigned FMC Discretes None assigned None assigned None assigned None assigned None assigned None assigned None assigned None assigned Altitude (29.92) Altitude (Baro) Air Data Computer Discretes Baroset None assigned None assigned Altitude (29.92) Altitude Baro Mach Computed Airspeed Max Allowable Airspeed Baroset (millibars) Baroset (ins. of Hg) None assigned None assigned None assigned None assigned None assigned None assigned None assigned None assigned None assigned None assigned None assigned Free Heading N1 or EPR Actual None assigned Engine Discretes Control Panel Discretes Control Panel Discretes Control Panel Discretes Instrument Discretes None assigned None assigned None assigned None assigned None assigned None assigned None assigned None assigned None assigned

Proposed Assignment No assignment Magnetic Heading Wind Speed Wind Direction-True Selected Runway Heading Selected Course #1 Selected Course #2 Set Latitude Set Longitude Set Magnetic Heading True heading Minimum Airspeed Selected Course #1 No assignment Selected Course #2 Selected EPR or N1 Caution & Warning DFDR Discretes #1 Tt2 Pt2 Pt7 Thrust Lever Angle AFS DFDR Discretes #1 AFS DFDR Discretes #2 AFS DFDR Discretes #3 RALT Check Point Dev. Altitude (1013.25mb) Baro Corrected Altitude #1 No assignment No assignment Baro Corrected Altitude #2 Indicated Angle of Attack No assignment Caution/Warning DFDR Discretes #2 No assignment No assignment No assignment Baro Correction (mb #1) Baro Correction (mb #1) Baro Correction (mb #2) Baro Corrected (in of Hg #2) Corrected Angle of Attack Total Pressure Minimum Airspeed Total Fuel Discrete Data #1 Discrete Data #2 Discrete Data #3 Discrete Data #4 Discrete Data #5 Platform Heading EPR Actual N1 Actual Maintenance Data #1 Maintenance Data #2 Maintenance Data #3 Maintenance Data #4 Maintenance Data #5 Acknowledgement Maintenance ISO #5 Message ISO #5 Message Potential Vertical Speed Wind Direction-Magnetic N-S Velocity-Magnetic E-W Velocity-Magnetic Along Heading Acceleration Cross Heading Acceleration

05 o * 0.01* *This data has been changed.05 o 0. 3 5 3 2 2 4* 4* Pad Fig.99* Sig.Strg. 041.5* 50 200* 62.92) Computed Airspeed Max.03 o * 0.39.05 o 0.M.05 o 0.0008 1.(EFI) DME Distance True Airspeed Total Air Temp.0 1.25 1.0 0.05 o 0. of Hg*) Max Transmit Interval 200 200* 500* 500 500 200* 200* Range (Scale) 0 .05 o 0. Static Air Temp.Signal Flight Director-Roll Flight Director-Pitch Radio Height DME Distance Altitude (29.5* 100 100 62. Note: Labels 017.01 1. Table 2 BNR DATA Label (Octal) 100 103 121 122 140 141 164 202 203 206 207 210 215 313 314 317 320 321 322 323 324 325 331 334 335 336 337 340 341 342 343 344 Parameter Name Selected Course Selected Airspeed Horiz.99* 130 . 042.25* 20* * 20 20 200 200 200 200 100 Sig. Bits (Not Inc.001* 0.+60* 0 . 236 and 237 previously had no values assigned.071 1024 1024 2048 32* ± 180 o ± 180 o ± 180 o ± 180 o +90 o ± 45 o 4* +90 o ± 180 o 4 ± 180 o * 128 128 4096 4096* 4096* 4096* 16384* Approx.599* +500 — 99* -99 . Table 1 BCD DATA Label (Octal) 170 201 230 231 233 234 235 Parameter Name Decision Hgt Sel.0 1. Strg.3999* 0 . The octal labels and parameter names are shown for each data item that has been changed. 027. 0. Signal Vert.5 32768* 512 131.01 o 0.500 -1 . 045.SUPPLEMENT 2 TO ARINC SPCIFICATION 429 .0 0.5* 62.1 o * 0. 043. Feet Knots Knots Knots ins/Hg* Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 g Deg/180 Deg/180 g Deg/180 * Deg/sec Deg/sec RPM RPM* RPM* RPM* RPM* Range ± 180 o ± 180 o +45o * +22.399.Page 7 Attachment 2: Data Standards A number of additions and changes have been made to the tables.50 o * ±45 o ± 22. Sign) 9 11* 9* 9 9 9 18* 16 17* 12* 12 11 12* 12 12 12 12 11 10 12* 13 14 12 12* * 12* 12* 12 12* 12* 12* 14 Units Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 Feet N. 2 0 2 3 3 1* 1* Units Feet N. Knots oc oc mb ins.05 o 0.35o 0. 224.05 o 0. Values for labels 223. Fig.05 o * 0. Resol.25* 0. 226 and 227 have been changed. Free Heading Track Angle Rate Inertial Pitch Rate Inertial Roll Rate N1 Actual * N1 Command N1 Limit N1 Derate N2 Max Transmit Interval 62.1 o 0.5* 62. Also a second “Note” has been added to Table 2. Baroset (mb)* Baroset (ins.0* 0.03 o * 1 1* 1* 1* 1* .Hg Resol 1. 044.0* 0.001 0.25* 0.125 0.5 125 500* 500* 125 50* 50* 50* 50* 50* 50* 20 50* 50* 6.0 1.Allowable Airspeed True Airspeed Impact Pressure Track Angle True True Heading Track Angle-Magnetic Magnetic Heading Drift Angle Flight Path Angle Flight Path Acceleration Pitch Angle Roll Angle Body Long-accel.008* 0.01 o 0. 225.M. The original data is shown only for the data that has been changed by this supplement.

133. Accel.SUPPLEMENT 2 TO ARINC SPECIFICATION 429 .3.Page 8 Table 2 BNR Data (cont’d) Label (Octal) 345 346 347 362 365 366 367 Parameter Name Exhaust Gas Temp. 130. Attachment 6: General Word Formats and Encoding Examples AIM word format examples have been added. 131.125* 0.125 0. 372. N-S Velocity E-W Velocity Max Transmit Interval 200 200 200 50* 50* 200* 200* Sig. 373. 1* 1* 16* 0. Resol. Bits (Not Inc. 245. 132. Detailed descriptions of these words have been included in the text of Section 2. 346. . 241.001 0. Sign) 11* 12* 11* 12 15* 15 15 Units C* RPM* Lbs/hr g Knots Knots Knots O Range 2048 4096* 32768 4 4096* 4096 4096 Approx.1. N1 Actual Fuel Flow Along Track Horiz. 360. Integrated Vertical Accel. 112. 374 and 376 previously had no values assigned. Values for label 216 have been deleted. *This data has been changed.3. 247.125 Note: Labels 110.

AERONAUTICAL RADIO. 1979 Prepared by the Airlines Electronic Engineering Committee Adopted by the Airlines Electronic Engineering Committee: August 31. 1979 . INC. Maryland 21401. 2551 Riva Road Annapolis.7645 USA SUPPLEMENT 3 TO ARINC SPECIFICATION 429 MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS) Published: November 1.

Negative number are encoded as the complements of positive values and the negative sign is annunciated in the sign/status matrix. equals the next whole binary number greater than the maximum parameter value less one least significant bit value. South Initial Word West. For the binary representation of angular data. CHANGES TO SPECIFICATION 429 INTRODUCED BY THIS SUPPLEMENT Note that Section 2. it plays no part in the selection of word characteristics.1. . the subtraction of the least significant bit value. the latter using two’s complement fractional notation.XXX degrees. and. if required. PURPOSE OF THIS SUPPLEMENT This Supplement introduces material on the transfer of file data and the related protocol. maximum value and resolution of the parameter are first determined in that order. by reference to the range values and numbers of significant bits for the words of interest. for other than very minor revisions. the number of significant bits is 17 and the maximum value of the fractional binary series is 131. the most significant bit of the data filed represents one half of the maximum value chosen for the parameter being defined. the Mark 33 DITS employs “degrees divided by 180o” as the unit of data transfer and ± 1 (semicircle) as the range for two’s complement fractional notation encoding ignoring.SUPPLEMENT 3 TO ARINC SPECIFICATION 429 . For example. Existing copies of Specification 429 may be updated by simply inserting the replacement white pages where necessary and destroying the pages they replace. A number of labels and corresponding data standards have been added. i. B. C.. the resolution provided in the DITS word should equal or exceed the accuracy in order not to degrade it. The goldenrod pages should be inserted inside the rear cover of the Specification. number of significant bits. extracts from the original text for comparison purposes. refresh rates. pad bits etc. COMMENTARY This section presents a complete tabulation of the changes and additions to the Specification introduced by this Supplement.1 BCD NUMERIC.3. Note that because accuracy is a quality of the measurement process and not the data transfer process.e. Copies of the Specification bearing the number 429-3 already contain this Supplement and thus do not require revisions by the reader..1 of this document calls for numeric data to be encoded in BCD and binary. for the moment.XXX degrees is encoded as 0 through ± 179. For convenience. The second part consists of replacement white pages for the Specification. ORGANIZATION OF THIS SUPPLEMENT The first part of this document. Accurate resolutions can be determined. the units. modified to reflect these changes. Thus the angular range 0 through 359. In this notation.1.071 – 1).1. The modified and added material on each replacement page is identified with “c3” symbols in the margins.000 feet with a resolution of one foot. all binary word ranges in Attachment 2 are shown as whole binary numbers rather than such numbers less one least significant bit value. 31 30 0 0 1 1 0 1 0 1 Designation BCD Numeric Data AIM Data Plus. Obviously.6 Data Standards The units. where appropriate. Left. ranges. In each case there is included a brief description of the addition or change and.6 DATA STANDARDS Text added to clarify data encoding. 2. any text originally contained in the Specification is reproduced for reference. if the Mark 33 DITS is required to transfer altitude in units of feet over a range of zero to 100. the value of the most significant bit is none half semicircle and there are no discontinuities in the code. ORIGINAL TEXT FOLLOWS: Bit No. for the items of information to be transferred by the Mark 33 DITS are tabulated in Attachment 2 to this document. Also the resolutions shown are approximate only. printed on goldenrod paper.1. 131. From 2. 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. North East Final Word Right. The least significant bit of the word is then given a value equal to the resolution increment.e. Successive bits represents the increments of a binary fraction series. 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 establishing a given parameter’s binary data standards for inclusion in Attachment 2. resolutions.Page 2 A. ORIGINAL TEXT FOLLOWS: 2. contains descriptions of the changes introduced into the Specification by this Supplement. The file transfer capability is being added primarily for the Flight management Computer (FMC) program/data load and update and FMC intersystem crosstalk. DISCRETE AND AIM DATA WORDS Table amended to provide consistency between AIM and file transfer data words.071 (i. To Intermed.5. No Computed Data Word Functional Test Control Word Minus.

1MHz (5) 10MHz (2) 1MHz (3) 8 7 6 5 4 3 2 1 1 1 1 1 1 0 0 0 When bit no.6 Data Standards (cont’d) COMMENTARY (cont’d) It should be noted that in all applications of the two’s complement fractional notation. 066.SUPPLEMENT 3 TO ARINC SPECIFICATION 429 . 300-307.1. 260. . 077. ORIGINAL TEXT FOLLOWS: 3.1MHz. 176. 3-1 RADIO SYSTEMS MANAGEMENT WORD FORMATS Error corrected in bits 24 and 25 of ILS word.5 FILE DATA TRANSFER Section added to provide description of file data transfer protocol. 175. ATTACHMENT 1: LABEL CODES The following labels have been given new assignments: 053. The number of bits in the word affects only the resolution of the data. cannot be changed by the use of more bits in the data field.7 added for GPWS discretes. 061. 10 is “one” the equipment should operate in the SSB (USB) mode. not its range. 1 through 4 of the seven-bit-per-character code. An asterisk beside a value designated that a change has been recommended. 070.3. HF COMM frequency word format changed and second word added to enable the use of 100 Hz channel spacing. 0.1. Notes 2 thru 5 deleted.3. 0. The original information provided in ARINC 429-2 is included in these tables.01MHz (7) LABEL HF COM Frequency 0. 126. Only bit no. 251. 217. 277. 062.3 HF Communications Frequency Range: Frequency Selection Increments Characters encoded in DITS word: Switching Functions: 2. 075. ATTACHMENT 2: DATA STANDARDS Tables 1 and 2 have both additions and modifications made to the data standards. 261. 5 code (see Attachment 5 to this document) using bit nos. Table 3. 200. 226. RESERVED (SDI) 9 0 [2] Bit No. ORIGINAL TEXT FOLLOWS: HF COM Function USB/AM MODE SIGN/STATUS MATRIX PARITY (Odd) 3. 137.001MHz (9) 0. 067. once chosen.1.4. 361. 2. 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. 056.3 HF COMMUNICATIONS Text amended to describe switching functions and finer frequency selection increments.1. Binary coded decimal (BCD) data is encoded per the numeric subset of the ISO Alphabet No. 143. 0. 10 is “zero” the equipment should operate in the AM mode. 177. 060. 063. the maximum value of the word.01MHz. 134. 076. 257.4.1.8MHz to 24MHz 1kHz 10MHz. When bit no. 1MHz. 252-256.001MHz USB/AM mode selection Fig.3 of this document. The formats of table 1 and 2 have also been changed to provide the addition of data standard descriptors. 071. 9 is available for the SDI function in this word. Example Notes 32 0 31 30 0 0 29 28 27 0 1 0 [1] [2] 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 0 0 1 1 0 1 0 1 0 1 1 1 1 0 0 1 0 [1] 0. 120.Page 3 2. 065.

05* 0.06* 0. TRANSMIT INTERVAL msec 200* 200* 200* 200* 200* 200* 200* 200* 200* 200* 200 62. FIG.1* 0.5* 0.35* 0.01 16* The change to MTI was erroneously omitted from Draft 1 of Supplement 3. .0 1.125* 0.05 0.SUPPLEMENT 3 TO ARINC SPECIFICATION 429 . SIGN) 9* 9* 9* 9* 8* 10* 9* * 11 13 13 9* 9* 8* 12* 17* 18* 11* 10* 10* 11* 11* 15* 18* 18* 15 12 12 12 12 11* 10* 13* 14 10* UNITS Deg/180 Deg/180 Deg/180 Deg/180 N. Steering Signal Vertical Steering Signal Throttle Command Tt2* Pt2* Pt7* Flight Director-Roll Flight Director-Pitch Fast/Slow Flight Director-Yaw* Radio Height Altitude (1013.125 0.06 0.1 0.5* RANGE (SCALE SIG. Static Air Temp. TRANSMIT INTERVAL msec 50 62. Deg/180 Deg/180 Knots Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 Ft/min* RANGE See Note 1 ±180o ±180o ±180o ±180o 128 ±60 o ±30 o * 128 32 32 ±45 o * ±22.0 TABLE 2 BNR DATA LABEL (OCTAL) 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3 3 3 3 3 # 0 0 0 1 1 2 2 2 3 3 3 4 4 4 4 6 0 1 1 1 2 4 4 1 1 1 1 1 1 2 2 2 2 2 6 0 1 5 0 6 1 2 3 0 1 2 0 1 2 3 4 3 0 1 3 1 1 7 0 1 2 3 4 7 0 1 2 4 5 0 PARAMETER NAME Selected Course #1 Selected Heading Selected Runway Heading Selected Course #2 Cross Track Distance Horiz.35* 0. UNITS RESOL # Present Position-Lat.1 1.00035* 0.05 0.06* * 0.05 0. Present Position-Long.05* 1. but was included prior to publication of Supplement 3.004 0.Page 4 ATTACHMENT 2: DATA STANDARDS (cont’d) TABLE 1 BCD DATA LABEL (OCTAL) 0 0 0 0 0 0 0 0 0 0 1 2 1 1 1 1 1 1 1 4 4 4 2 3 0 1 2 3 4 5 6 1 2 3 5 0 PARAMETER NAME MAX.59.5* 500 500 62. Deg/180 Deg/180 * o C PSIA PSIA Deg/180 Deg/180 Knots Deg/180* Feet Feet Knots o C o C Deg/90* Deg/90* Lb.1 1. Indicated Angle of Attack Corrected Angle of Attack Total Fuel Present Position-Lat.05 0.5 62.35* 0.125 0. BITS (NOT INC.5 o 32 ±180 o 16384* 131.5 62.0 0. Ground Speed Track Angle (true) Magnetic Heading Wind Speed Wind Direction (true) Set Latitude Set Longitude Set Magnetic Heading Greenwich Mean Time True Airspeed 90S-90N 180E-180W 0-2000 0-359.0 0. Present Position-Long.5 100 100 * 200 200 200 100 100 62.01 0.072 2048 512 512 ±90 o * ±90 o * 655. PAD FIG.360 0-90N-0-90S 0-180E-0-180W 4096 ±180 o ±180 o ±180 o ±180 o ±90 o * ±45 o * ±90 o * ±180 o 16384* APPROX RESOL 0.5 200* 200 200 100* 40* 40* 40* 40* 40* 40* 20* 20* 50 SIG.05 0.M.9 100-599 5 6 4 4 3 3 3 5 6 4* 5 3 0 0 1 1 2 2 2 0 0 1* 0 0 Deg/Min* Deg/Min* Knots Deg Deg Knots Deg Deg/Min Deg/Min Deg Hr/Min* Knots 0.5* 0.05 0.0 1.5 62.1 1.004 0.35* 0. Ground speed Track Angle True True Heading Track Angle-Mag Magnetic Heading Drift Angle Flight Path Angle Pitch Angle Roll Angle Potential Vertical Speed MAX.5 50 62.05 0.1 0.05 20* 0.00070* 0.25mb) True Airspeed Total Air Temp.9 0-359 0-299 0-359 90S-90N 180E-180W 0-359.9* 0-23.0* 0.05 0.5* 0.1 0.1* 0.5 100* 50 62.

A change in ARINC 710 not shown in Supplement 2 is a planned change for Supplement 3. A change in ARINC 707 not shown in Supplement 2 is a planned change for Supplement 3. The way in which these parameters are encoded is also explained in the Commentary following Section 2. A selftest inhibit bit will be added and the range of the data word will be halved to a value of 8192 ft.000086o for latitude and .1.1. ORIGINAL TEXT FOLLOWS: ATTACHMENT 6 GENERAL WORD FORMATS AND ENCODING EXAMPLES 1. The numbers entered in the RANGE column for angular parameters are the actual degree ranges required. ATTACHMENT 6: GENERAL WORD FORMATS & ENCODING EXAMPLES SSM codes in AIM words changed to reflect table amendment of section 2.00017 o for longitude. Radio Height code example changed to reflect shift in field.+4g to facilitate direct recording by the flight recorder. 2.1a. The resolution of Selected Runway Heading (BCD and BNR) will be changed to . Bit nos.1 o./Long. A change being considered for Supplement 3 is to change the range to –6g . 206 and 207 deleted in Table 6.2 deleted to revert data coding to the original two’s complement notation.1. 204. Codes 203. 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. Position (codes 310 and 311). Note 4 of Table 6. The resulting resolution is . GENERAL WORD FORMATS .6 of this document. Word format added for VOR Omnibearing. 9 and 10 of the word may be used to achieve a 20 bit capability for high resolution of the Lat. 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. 5. As explained in the Commentary following Section 2.Page 5 ATTACHMENT 2: DATA STANDARDS (cont’d) NOTES 1.SUPPLEMENT 3 TO ARINC SPECIFICATION 429 . Word formats added for date/flight leg and flight number information.6.1. the weight of the most significant bit of the two’s complement fractional notation binary word will be one half this value. 4. 3.5.

Page 6 ATTACHMENT 6: GENERAL WORD FORMATS & ENCODING EXAMPLES (cont’d) .SUPPLEMENT 3 TO ARINC SPECIFICATION 429 .

1. In the absence of discretes.5 of this document describes the functions of the sign/status matrix and the ways in which the bits constituting it are encoded. one bit per variable.1.3. as are also the limitations on its use. [5] Parity Bit This bit is encoded to render word parity odd. followed by bit #12 and so on in ascending numerical order until the data field is reached.SUPPLEMENT 3 TO ARINC SPECIFICATION 429 .2 of this document refers. [4] Sign/Status Matrix (SSM) Section 2. unused bits in a word may be assigned to discrete functions.4 of this document.1. this field may be occupied by binary zero or valid data pad bits. When the SDI function is not required.4 of this document refers. . Section 2. [3] Pad All bit positions not used for data or discretes should be filled with binary zero or valid pad bits. Section 2. unused bit positions should be occupied by binary zero or valid data pad bits.3. [2] Discretes As discussed in Section 2.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.2 of this document. Bit #11 of the word should be the first to be so assigned.

Page 8 TABLE 6-1a BCD DATA ENCODING EXAMPLES NOTES: [1] [2] “P” denotes pad “zero” or valid data.1. Because the actual maximum value of the most significant character of each of these quantities exceeds 7.3. it cannot be encoded in the most significant character position of the BCD word.SUPPLEMENT 3 TO ARINC SPECIFICATION 429 .1. Note possible use of pad bits for discrete functions per Section 2. . Section 2.2 if this document refers. 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.2.

Page 9 TABLE 6-2 BNR DATA ENCODING EXAMPLES NOTES: [1] [2] [3] “P” denotes pad “zero” or valid data.1. [4] . Arc minutes and seconds are encoded as decimal degrees.2. Longitude values are encoded as positive angles in the range 0 to 180 o with the sign/status matrix indicating East or West. Angles in the range 0 to 180o are encoded as positive numbers.3. 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. Latitude values are encoded as positive angles in the range 0 to 90 o with the sign/status matrix indicating North or South. Section 2.1. Negative values are encoded as the two’s complements of positive values and the negative sign is annunciated in the sign/status matrix.2 of this document refers. Note possible use of pad bits for discrete functions per Section 2.SUPPLEMENT 3 TO ARINC SPECIFICATION 429 . Arc minutes and seconds are encoded as decimal degrees.

Maryland 21401 – 7645 USA SUPPLEMENT 4 TO ARINC SPECIFICATION 429 MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS) Published: August 1. INC. 1980 Prepared by the Airlines Electronic Engineering Committee Adopted by the Airlines Electronic Engineering Committee: June 17.AERONAUTICAL RADIO. 2551 Riva Road Annapolis. 1980 .

etc. AIM DATA AND FILE TRANSFER WORDS Text describing “no computed data” modified. modification of data standards. He should contact ARINC for assistance.1.1. printed on goldenrod paper.SUPPLEMENT 4 TO ARINC SPECIFICATION 429 . priority assignment of SSM codes. minus.1 BCD NUMERIC. Commentary text partially deleted. The modified and added material on each replacement page is identified with “c-4” symbols in the margins. 30 and 31 of the word as shown in the table below. If a sink device designed for service prior to such a development cannot decode the original word label. last) for AIM data. 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”. PURPOSE OF THIS SUPPLEMENT This Supplement introduces material on defining “No Computed Data” and “Failure Warning”. modified to reflect these changes.Page 2 A. ORGANIZATION OF THIS SUPPLEMENT The first part of this document. however. Maintenance and AIM data. Copies of the Specification bearing the number 429-4 already contain this Supplement and thus do not require revisions by the reader. The goldenrod pages should be inserted inside the rear cover of the Specification. B. change of receiver impedance limits. Commentary providing definitions added. 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. extracts from the original text for comparison purposes. Experience has shown. a bus will be dedicated to delivering a single information element from a source to one or more identical sink devices. North. etc. for other than very minor revisions. addition of material on signal characteristics. Discrete. where appropriate. 2. 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. DISCRETE. identify the word application for Discrete. For example. command/response protocol. that system developments frequently occur that result in the need for additional information elements to appear on the bus. ORIGINAL TEXT FOLLOWS: 2. change of some word formats.g. change of the receiver voltage thresholds and modification of the HF and DME word formats. In such circumstances. COMMENTARY Attachment 1 defines 256 discrete label codes. Label will: a. static air temperature. AIM Data and File Transfer Words The sign (Plus. control. any text originally contained in the Specification is reproduced for reference. description of fault tolerance and isolation.) of BCD numeric data. The second part consists of replacement white pages for the Specification.5. In each case there is included a brief description of the addition or change and. The assignment of label codes for all such communications must be coordinated with the air transport industry if chaos is to be avoided. the sink device designer might be tempted to assume that decoding the word label is not necessary. . expansion of the current label. Label code assignments are set forth in Attachment 1 to this document. This quantity is expected to meet label assignment needs for the foreseeable future. Special Note: In some ARINC 429 DITS applications. South.3 Information Identifier The first eight bits of each word are assigned to a label function. intermediate.5. no matter how strong the temptation to omit it might be. DME distance. 403. Existing copies of Specification 429 may be updated by simply inserting the replacement white pages where necessary and destroying the pages they replace. or the section number and title that will be employed when the Supplement is eventually incorporated. a scheme will be devised in which existing label assignments are duplicated. and the status of the transmitter hardware should be encoded in bit nos. 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. contains description of the changes introduced into the Specification by this Supplement. The message for sink designers should therefore be quite clear – provide label decoding from the outset.1. 2. the word type (first. addition of new labels.) and b.1 BCD Numeric. it cannot differentiate between this word and the new data in the new situation.1. C..3 INFORMATION IDENTIFIER Text changed to describe use of five-character label. rather than extend the length of the label field. The sign/status matrices of Discrete words should be encoded per the rules set forth for BCD numeric data. it is envisaged that. Should additional labeling capability be required in the longer term. and. identify the information contained within BNR and BCD numeric data words (e. ORIGINAL TEXT FOLLOWS: 2. address capability of A/N messages. Each change or addition is entitled by the section number and title currently employed in the Specification.

5. North. it should immediately change the states of bits nos. Bit No. 5. Initial Word Final Word Intermediate Word. 3.2 BNR NUMERIC DATA WORDS Table modified to permit sign coding for “no computed data”. To Functional Test/Minus. West Left.. minus. From Normal Operation/Plus. etc. 3. . West Left. Above No Computed Data Functional Test Minus. 29 should be “zero” when no sign is needed. a source system detects a failure which causes one or more of the words normally output by that system to be unreliable. Definition of “failure warning” and “no computed data” added.1. 30 and 31 of the word as shown in the table below. East. 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. Right To.3.1. The “no computed data” code should be generated for BCD numeric data words when computed data is not available for reasons other than equipment failure. South. North.SUPPLEMENT 4 TO ARINC SPECIFICATION 429 . From Not Used (Growth) 2.g.5. 5. this code should be interpreted as a command to perform a functional test. 30 29 0 0 1 0 0 1 1 1 0 1 0 0 1 0 1 1 Designation BNR Data Failure Warning/Plus. North East. 30 and 31 in the annunciation to the “failure warning” annunciation.” 1 1 1 1 0 Notes: 1. Bit no.Page 3 Bit No. 30 and 31 of BCD numeric data words should be “zero” when no sign is needed. When it appears in a BCD numeric data word identified by its (label) as a system output. 4. “Control Word”. 31 0 0 1 1 30 0 1 0 1 BCD Numeric Word Plus. To Normal Operation/Minus. during the execution of a functional test. 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. A self-test should produce indications of 1/8 of positive full-scale values unless indicated otherwise in an ARINC Equipment Characteristic. Words containing this code should continue to be supplied to the data bus during the failure condition. 29. the “functional test” code should be interpreted as advice that the data in the word results from the execution of a functional test. Left. From. The “no computed data” code should be generated when computed data is not available for reasons other than equipment failure. North. the “functional test” code should be interpreted as advice that the data in the word results from the execution of a functional test. Left. 2. Bit nos. South West. e. When it appears in a BCD numeric data word identified by its label as an instruction. a radio channel change command. North. If. South.3 of this document for definitions of the terms “Initial Word”.1.) of BNR numeric data words and the status of the transmitter hardware should be encoded in bit nos. 2. etc. Below Designation AIM Intermediate Word Initial Word Final Word ControlWord File Transfer Intermediate Word. 31 0 0 0 Notes: 1. Right. ORIGINAL TEXT FOLLOWS: 2. 30 and 31 in the affected word(s) to the “failure warning” code defined above. When it appears in a word identified by its label as a system output. 4. “Intermediate Word” and “Final Word. To Failure Warning/Minus. East Right.2 BNR Numeric Data Words The sign (plus. north. East. A self-test should produce indications of 1/8 of positive full-scale values unless indicated otherwise in an ARINC Equipment Characteristic. See Section 2. Minus South. etc. South West. Right. Plus. south. From No Computed Data Functional Test/Plus.

Page 4 2. e. In practice.4. shields are grounded in the aircraft close to the rack connector. Thus.2. The output impedance of the transmitter should be as specified in Section 2.2.1 TRANSMITTER VOLTAGE LEVELS Text changed to improve clarity. Equipment manufacturers should ensure. 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. 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 abovedefined minimum difference of 2.1 Transmitter Voltage Levels The differential output signal across the specified output terminals (balanced to ground at the transmitter) should be + 10 ± 1.2.3.5 to –0. that their equipment will operate correctly if.5 volts and –10 ± 1.3. In the absence of noise. . The interwiring diagram to be found in each ARINC Equipment Characteristic shows connector pins assigned to carry shields into black boxes for grounding. The performance of a digital receiver depends upon the receiver input signal characteristics (data with distortion and noise) and the receiver design.4. on the number or length of sturbs for installations on aircraft no larger than those existing.g. The shields should be grounded at both ends and at all production breaks in the cable.5. however. stub configuration and the number of receivers connected. these nominal voltages will be perturbed by noise and pulse distortion.1 of this document. Also.5V to –2.3.1 TRANSMITTER OUTPUT IMPEDANCE Text added to improve clarity. ORIGINAL TEXT FOLLOWS: 2. ORIGINAL TEXT FOLLOWS: 2. No restriction is placed by this specification. See Appendix 1 to this document for a report of this investigation. 2.2. Commentary revised to include description of receiver reaction to undefined voltages. instead of being terminated on these pins. 2. Receiver manufacturers are encouraged to work with the differential input voltage (line A to line B) and not line-to-ground voltages. ORIGINAL TEXT FOLLOWS: 2.2. Fault voltage text deleted.1. 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.1 TRANSMISSION SYSTEM INTERCONNECT Commentary expanded to provide description of possible solutions to single-wire fault conditions. receivers should associate the following voltage ranges with the three states indicated: “HI” “NULL” “LO” +5V to 13V +2.5V -6V to –10V 2. “NULL” and “LO” states when the transmitter is open circuit. COMMENTARY In practical wire line digital information transmission systems. Prior to the selection of the voltage and impedance parameters set forth in this Section of this document.2 RECEIVER VOLTAGE LEVELS Receiver voltage thresholds changed.SUPPLEMENT 4 TO ARINC SPECIFICATION 429 ..0 volts.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.2.3 STATUS PRIORITIES New section inserted. 0 ± 0. the normal ranges of voltages presented to the receiver terminals (A and B) would be: “HI” “NULL” “LO” +6V to 10V +0. This output impedance should be present for the “HI”.5V -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. 2. therefore.0 volts respectively for the “HI”.3. 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 welldesigned receiver.2. noise due to electrical interference perturbs digital signals. See Attachment 3 to this document for a pictorial representation of transmitter and receiver voltage levels. “NULL” and “LO” transmitter output conditions and also during transitions between these levels.2 Receiver Voltage Levels The differential voltage presented at the receiver input terminals will be dependent upon line length.5V between the NULL and HI and NULL and LO states. cable characteristics and electrical mismatches can produce distortion of the digital data pulses. B 747.2.

the Mark 33 DITS should also be capable of accommodating discrete items of information either in the unused (pad) bits of data words or. 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.3. It is probable. 2. Five labels (octal 270-274) are assigned to the general purpose words in Attachment 1.5 Fault Tolerance New section inserted. New section inserted.2. 2. COMMENTARY 2.000 ohms minimum Differential Input Capacitance CI = 50pF maximum Resistance to Ground RH and RG ≥ 12. These are general purpose discrete words. 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.2. There are two types of discrete words.2. 2.4.5. in dedicated words.5. Opto-isolator technology is progressing and may soon find application in digital data receivers.1.2. 2. 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.2 Discretes Text modified to expand label examples. COMMENTARY The above characteristics apply to differential amplifier receivers.Page 5 ORIGINAL TEXT FOLLOWS: 2. . measured at the receiver input terminals: Differential Input Resistance RI = 6. The dedicated words should be used when the New section inserted.6. 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. 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.3. Measurements on a few samples of wire showed a spread of characteristic impedance of 63 and 71 ohms.4. divided equally between line A and line B to provide an impedance balanced output.1.2. thus future developments in insulation techniques may result in cables having characteristic impedances outside the range estimated.000 ohms Capacitance to Ground CH and CG ≤ 50pF.2. See Attachment 4 to this document for a pictorial representation of the input and output circuits standards.2 Receiver Input Impedance The receiver should exhibit the following characteristics. 2. 2.1 Receiver Fault Isolation New section inserted. Opto-isolator receivers impose slightly greater loads on data buses than differential amplifier receivers and the way in which they are characterized is different. ORIGINAL TEXT FOLLOWS: 2.SUPPLEMENT 4 TO ARINC SPECIFICATION 429 .2. 2.6 Fault Isolation New section inserted.6. Attachment 6 shows that this against the background of the generalized word structure.2.2. Value of RI changed. ORIGINAL TEXT FOLLOWS: 2.5. and dedicated discrete words.1 Receiver External Fault voltage Tolerance 2. when necessary. that a future revision of this Specification will include material specifically related to their use.2 Transmitter Fault Isolation New section inserted.2 RECEIVER INPUT IMPEDANCE Reference to AIDS limitations deleted.3 Transmitter External Fault Load Tolerance The output impedance of the transmitter is specified as 75 ± 5 ohms to provide an approximate match to the characteristic impedance of the cable.4.2 Transmitter External Fault Voltage Tolerance New section inserted. Twisted shielded wire specifications do not control the characteristic impedance of the cable.2.1 Transmitter Output Impedance The transmitter output impedance should be 75 ± 5 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.2 Discretes In addition to handling numeric data as specified above. however.

A file may contain from 1 to 127 records. 1 through 8. the impact of label use will be small. 9 through 16 should all be binary “zeros”.1. Bit nos. 9 through 29 of that word are available for information transfer.5. Data bit nos. 17 through 29 of this initial word may be used for information transfer.1Command/Response Protocol File data will consist of both ARINC 429 BNR numeric words and ISO alphabet No. 19 and 20 the required character size and bit no. on the bus connecting it to that receiver. Intermediate words.Page 6 2. When the word application label is either of those assigned in Attachment 1 for ISO Alphabet No.3. with the “Clear to Send” reply.1 COMMAND/RESPONSE PROTOCOL Text modified to describe transmitter reaction to lack of “Clear to send”.5. These words should be limited to AIDS utilization.1. 30 and 31. 9 through 13 should contain the binary representation of the line count. 5) final words resulting from the number of ISO Alphabet No. 17 through 22 should be binary “zeros” (spares) and bit nos. bit nos. 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). Each record may contain from 1 to 126 data words. ISO Alphabet No. The few aircraft systems which deliver discretes to an AIDS by means of the Mark 33 DITS will be burdened very little by this.1 of this document.1. bit nos.2. When the word application label is assigned in Attachment 1 for Acknowledgement Data. The transmitter then sends the “Data Follows” initial word. one of the eight versions of the “initial word” described in Section 2. 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. 2. the “Request to Send” initial word. on the separate bus provided for return data flow.1.3. i. 5 control character “STX”.3.1. bit nos. All three of these applications may involve the transfer of more than 21 bits per “data package”.1. See Attachment 6 to this document for the encoding standards. when used. 5 data transfer or Maintenance Data (ISO Alphabet Not. 23 through 29 should take on the pattern of the ISO Alphabet No. in bit nos. 5 characters. When the word application label is either of those assigned in Attachment 1 for ISO Alphabet No. 9 through 29 of each word should be divided into three seven-bit bytes (bit nos. if no errors are revealed.. which necessitated the development of the special AIDS words.3. 5 characters in the message being one or two less than a number wholly divisible by three should be filled with binary “zeros”. 5). each word containing the relevant application label (see Attachment 1) in bit nos. 5 data transfer or Maintenance Data (ISO Alphabet No. bit nos. bit nos.3.4 AIM DATA Text added to describe unit addressing. 5 character. and a sign/status matrix code in bit nos. it will so . If the receiver is not ready to accept data when the transmitter sends its “Request to Send” word. Any unused bit positions in ISO Alphabet No. 2. 32 should be encoded to render word parity odd. follow the initial word of the group or the control word.SUPPLEMENT 4 TO ARINC SPECIFICATION 429 . When it is used. A record will contain.3. 17 and 18 the required intensity. 5 and Maintenance Data (ISO Alphabet No. When the word application group label that is assigned in Attachment 1 for Acknowledgement. 5) final transfer or Maintenance Data (ISO Alphabet No.5. The file data transfer protocol is as follows. closes out the transaction by sending the “Data Received OK” word to the transmitter. Bit no. The receiver processes the error control information in the “final word” and. except that when this word is the only word to be transmitted. 5) application groups is an optional control word containing the sign/status matrix code for “control” information for the display. It should also contain. ORIGINAL TEXT FOLLOWS: 2. The first word of each group should contain the sign/status matrix code defined for “initial word” in Section 2. the binary representation of the number of words in the group. The second word of the ISO Alphabet No. each of which contains one ISO Alphabet No. bit nos. 14 through 16 should encode the required color. A transmitter having the data to send to a receiver transmits. 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.5. 21 should indicate whether or not the display is required to flash. ORIGINAL TEXT FOLLOWS: 2.1. bit nos. Similarly. 5). 9 through 16.1.5. the total number of information bits to be transmitted is 13 or less. 5 and Maintenance information encoded in dedicated words) should be handled in the manner described in this Section. bit nos. The receiver responds. the “intermediate words” and the “final word”. 9 through 15.4 AIMS Data AIM data (Acknowledgement. The data field of this word should be structured similarly to that of the intermediate word. at the minimum.1 of this document.e. 22 through 29 of the word should be binary “zero” (spares). 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.2 Discretes (cont’d) data is intended for the AIDS DFDAU which cannot identify sources in this way. 16 through 22 and 23 through 29). containing the sign/status matrix code for “intermediate word”. Source equipment should format such long messages into groups of 32-bit DITS words.

display designers should incorporate into their devices means for selecting those words to be used for updating the display from the greater quantity delivered.95MHz Frequency Selection: 50kHz Increment: Characters encoded10MHz. On receiving this word the transmitter should curtail the data flow and back up to the beginning of the file. In the absence of identification of the record in which the error occurred. Having done this it should send the “Data Follows” initial word. Additionally.4.2). It should then re-establish that the receiver can accept data by going through the request-to-send/clear-to-send routine. 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. a “Poll” initial word is defined for use in system in which continuous “handshaking” between two terminals is desired.5.1.4. In DITS word: 0.1.2 INFORMATION RATES Commentary added to describe refresh rate.Page 7 indicate in its response (see Section 2. The “Header Information” initial word is used for this purpose. this word should contain the sequence number of the first record of the file. An exchange of “Poll” words may be interpreted as the message.SUPPLEMENT 4 TO ARINC SPECIFICATION 429 . (100MHz Character is always Decimal 1) Switching Functions: Standby. Discretes contained within data words will be transferred at the bit rate and repeated at the update rate of the primary data. 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. or request to the receiver to accept. 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 the receiver detects a parity error during the transmission. in general. 3. Thus. COMMENTARY The time intervals between successive transmissions of a given BCD word specified in table 1 of Attachment 2 to this document are. The transmitter will interrupt the data flow and back up to the start of the record so identified.2 DME Encoding and switch functions modified.2 DME Frequency Range: 108. 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.1. If the signal was so used. do you have anything for me?” 2. The receiver will then close out the transaction as before.1MHz.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. Considerations other than human factors demand the time intervals specified. or another “Poll” word when it does not. Words dedicated to discretes should be repeated continuously at the rates defined in Attachment 2. The protocol also allows a transmitter to send file size information to a receiver without any commitment to send. ORIGINAL TEXT FOLLOWS: 2.4.01MHz. the least significant character of the display would change too rapidly for human perception. 1MHz. continuing through the “final word”.3.4.00MHz to 135. The transmitter should then wait 200 milliseconds and retransmit the “Request to Send”. followed by the data and the “final word”. “ I have nothing for you. ORIGINAL TEXT FOLLOWS: 3. the file itself. 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. too short for the signal to be of use in driving a display device directly. DME Mode Select ILS Mode . 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. The response to a “Poll” word will be either a “Request to Send” initial word when the polled terminal does have data to transmit. 0.

10 should be set to “zero” for AM operation and “one” for SSB operation.01MHz (0) 0.1MHz (5) Standby 10MHz (1) 1MHz (1) 8 7 6 5 4 3 2 1 1 0 1 1 1 0 0 0 [1] [2] [3] Bit no. [2] Bit no. HF COM Word #2 PARITY (odd) SIGN/STATUS MATRIX NOT USED .01MHz (7) 0.6 of ARINC Char.1MHz (5) 10MHz (2) 1MHz (3) 11 0 [1] 10 9 0 0 [2] [3] 8 7 6 5 4 3 2 1 1 1 1 1 1 0 0 0 [1] Bit no. 9 should be set to “zero” when the 100 Hz option is not used and “one” when it is. 11 should be set to “zero” for LSB operation and “one” for USB operation. . 9 of word #1 is “one”. Example Notes 32 0 31 30 0 0 29 28 1 1 27 26 25 24 0 0 1 1 23 22 21 20 0 1 0 09 18 17 16 0 1 1 1 15 14 13 12 1 0 0 1 0.001MHz (9) 0. [3] Bit no.SUPPLEMENT 4 TO ARINC SPECIFICATION 429 .Page 8 FIGURE 3-1 Radio Systems Management Word Formats HF and DME words modified.1Khz (5) Function LABEL HF COM Frequency Bit No. ORIGINAL TEXT FOLLOWS: DME DME Mode Select SIGN/STATUS MATRIX PARITY (odd) Function Bit No. 709 Standby off Standby on HF COM Word #1 SSB/AM Mode Word Identifier PARITY (odd) Function SIGN/STATUS MATRIX LABEL HF COM Frequency Bit No. Example Note: 32 0 31 30 0 0 29 28 27 26 0 1 0 1 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 10 9 0 0 8 7 6 5 4 3 2 1 1 1 1 1 1 0 0 0 The HF COMM #2 word is used only when bit no.1. 14 should be set to “zero” for VOR frequencies and “one” for ILS frequencies by the tuning information source. Bit 11 12 13 Zero One DME Mode select coding per Section 4. Example Notes 32 1 31 30 0 0 29 28 27 0 0 1 26 25 24 23 0 0 0 1 22 21 20 19 0 1 0 1 1 8 17 16 15 0 0 0 0 14 0 [1] 13 0 [2] 12 11 0 0 [3] 10 9 0 0 RESERVED (SDI) USB/LSB Mode LABEL DME Frequency ILS Mode 0.

05 o 0. Table containing “Equipment ID Codes” added. The column for “transport delay” has been changed to “maximum transport delay”. Deg/180 RANGE ± 128* ± 180o ± 180o ± 180o ± 0.5* 62.8 ± 180o 131. A column for “EQPT.0* 1. 340-342. Label 226 (FWC #2) deleted. Data standards added for new labels.1* 0. 144-162. 135.Page 9 ATTACHMENT 1: LABEL CODES Column “EQPT. The following labels have been given new assignments: 004. 310322.044 o 4 4 . 244-252. “noise level” and “update interval” have been deleted.0 TABLE 2 BNR DATA LABEL (OCTAL) 077 100 105 110 173 174 222 256 257 310 PARAMETER NAME Lateral CG Selected Course #1 Selected Runway Heading Selected course #2 Localizer Deviation Glideslope Deviation VOR Omnibearing Fuel Quantity #1 Fuel Quantity #2 Present Position – Lat. Note [2]: A nominal interval description has been added. 242. 140-141.5* 200* 200* 200 . 344.05 o 0. An asterisk beside a particular value designates that a new value is suggested.0 MAXIMUM TRANSMIT INTERVAL 500 200* 200* 200* 200* 200* 500 200 200 200 500 62. 217. 114-122. DIG. 256-265. 070-106. BITS 14* 12 11 12 12 12 12 15 15 20 POSITIVE SENSE APPROX.0002 0.0001 0. 202-212.* Deg o C Ft/Min o C RANGE (SCALE) 90S-90N* 0-359. 347. The following tables list the parameters for which the data standards have changed. 126. 127. 222-226. 215.0 0. 173-177. A column for “minimum transmit interval” has been added. 0. 060-064. Selected Runway Heading Selected Course #1 Selected Course #2 ILS Frequency VOR/ILS Frequency Set Latitude Gross Weight Lateral CG Drift Angle Total Air Temperature Altitude Rate Static Air Temperature UNITS Deg:Min Deg Deg Deg Deg:Min 100lb. Mlb-in. UNITS MLB/in Deg/180 Deg/180 Deg/180 DDM DDM Deg/180 Lbs.05 o 0. 370.1 1. Labels 124 and 224 (C&W DFDR Discretes) deleted.000 -99-+60* SIG. TABLE 1 BCD DATA LABEL (OCTAL) 010 017 024 027 033 034 041 065 067 200 231 232 233 PARAMETER NAMES Present Position – Lat. 056. 276. 111.1 1.5* 62.5* 50* 62. ID (HEX)” has been added for fivecharacter label implementation.000086 o* MAXIMUM TRNASMIT INTERVAL 200 50* 62.4 ± 0.0 20.ID (HEX)” has been added. RESOL. Note [4]: SDI assignments defined for labels 060-064.5 500 Up 0. ATTACHMENT 2: DATA STANDARDS The columns for “bandwidth”.072 131.00* ± 90* -60-+90* ± 20. 034. 5* 4 3 3 5* 5 4* 3* 2* 4 2* N POSITIVE SENSE RESOL.1 0.001 0. Note [3]: A definition for “maximum transport delay” has been added. Lbs. 0. 136. 350.SUPPLEMENT 4 TO ARINC SPECIFICATION 429 . 377.1 1.9 0-359 0-359 90S-90N* 0-10000* ± 100.072 0-90N-0-90S* SIG. 345.

271 Existing tables replaced by new set of tables. Flight Director F. 271 Discrete Word #1 Bit No. Table 3. The ability of receivers to reject unwanted words would also be effective in improving bus efficiency.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. O. It was suggested that a Minimum Transmit Interval be specified (perhaps a value of ½ the Transmit Interval) to control bus loading. ORIGINAL TEXT FOLLOWS: Table 3.2 FCC DISCRETES – LABELS 270.2: FCC Discretes – Labels 270. Flight Director Turbulence Mode Autopilot #1 Autopilot #2 RESERVED (A/P #3) Autothrottle #1 RESERVED (A/T #2) Airspeed Hold Mode Airspeed Select Mode Mach Select Mode Mach Hold Mode Bank Angle Limit Heading Select Mode N1/EPR Select Mode IAS on Throttle Mach on Throttle Spare Spare Sign/Status Matrix Parity (Odd) On On Requested Engaged Engaged Engaged Armed Armed Requested Requested Requested Requested .SUPPLEMENT 4 TO ARINC SPECIFICATION 429 . 1 2 3 4 5 6 7 8 9* 10* 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X Label X X X X X X Off Off Not Requested Not Engaged Not Engaged Not engaged Not Armed Not Armed Not Requested Not Requested Not Requested Not Requested See Below Requested Requested Requested Requested Not Requested Not Requested Not Requested Not Requested Bit Status 0 X Capt.

.SUPPLEMENT 4 TO ARINC SPECIFICATION 429 . which are normally used for the SDI. 21. Limit Not used 5o 10 o 15 o 20 o 25 o 30 o Spare Discrete Word #2 Bit No. 1 2 3 4 5 6 7 8 9* 10* 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function Bit Status 1 X X X X X X Altitude Hold Mode Altitude Select Mode Vertical Speed Select Mode Vertical Speed Hold Mode Horizontal Navigation Vertical Navigation Land Command LOC Approach Command Back Course Approach Command CWS #1 CWS #2 CWS #3 Pitch Upper Mode Cancel Roll Upper Mode Cancel Heading Hold X Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Not Requested Not Requested Not Requested Not Requested Not Requested Not Requested Not Requested Not Requested Not Requested Not Requested Not Requested Not Requested Not Requested Not Requested Not Requested 0 X Label 21 0 0 0 0 1 1 1 1 Bit No. have purposely been used for Discrete information.Page 11 ATTACHMENT 2: DATA STANDARDS (cont’d) Bank Angle Limit Encoding Bit nos. 22 0 0 1 1 0 0 1 1 23 0 1 0 1 0 1 0 1 Spare Sign/Status Matrix Parity (odd) * Bits 9 and 10. 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.

Slat/Flap angle word added. ORIGINAL TEXT FOLLOW: P 32 SSM 31 (01) 30 “STX” 29 23 SPARES 22 (Zeros) 17 WORD COUNT 16 BNR EQUIV.000 ohms. 273 03. SYSTEM GUIDANCE SDI 10 9 8 LABEL (350-354) 1 DISCRETES LSB 11 SDI 10 9 8 LABEL (270-274) 1 .8 TCC DISCRETES LABELS 272 03. ATTACHMENT STANDARDS 4: INPUT/OUTPUT CIRCUIT RI increased from 6. ATTACHMENT 6: GENERAL WORD FORMATS AND ENCODING EXAMPLES Format for alphanumeric message initial word modified.5-13 volts. 9 8 LABEL (356/357) 1 ALPHA NUMERIC (ISO ALPHABET NO.Page 12 TABLE 3. Total system resistance range of 300-6000 ohms changed to 400-8000 ohms.000 to 12. GMT binary word added. 274 03. In Table 6-2 examples corrected for Present Position (Latitude and Longitude). APPENDIX 4: DIGITAL (PART 2) Appendix added.SUPPLEMENT 4 TO ARINC SPECIFICATION 429 . TABLE 3. Radio Height word added.7 GPWS DISCRETE LABEL 270 23 Visual message bit assignments inserted. 5) DATA – INITIAL WORD FORMAT P 32 SSM 31 (00) 30 29 MSB 2 DISCRETE WORD FORMAT P 32 SSM 31 (00) 30 MAINTENANCE DISCRETES 29 MSB DISCRETES LSB 11 MAINTENANCE (DISCRETE) WORD FORMAT APPENDIX 3: DIGITAL SYSTEMS GUIDANCE (PART 1) Appendix added. ATTACHMENT 3: VOLTAGE LEVELS Hi and Lo thresholds changed from 5-13 volts to 6. In table 6-1b note [1] deleted and bits 21 and 22 of latitude word interchanged. Label Fields changed in discrete word and maintenance (discrete) word. 275 03 New tables inserted.

2551 Riva Road Annapolis. 1981 . 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. INC.AERONAUTICAL RADIO.

5V to –2. receivers should associate the following voltage ranges with the three states indicated: “HI” +6. where appropriate.5V to 13V “NULL” +2. on the number or length of stubs for installations on aircraft no larger than those existing. 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 2. ORIGINAL TEXT FOLLOWS: COMMENTARY 2.3. as new equipment is developed. The second part consists of replacement white pages for the Specification. The modified and added material on each replacement page is identified with “c5” symbols in the margins. ORGANIZATION OF THIS SUPPLEMENT The first part of this document. When this condition exists noise immunity decreases and intermittent operation may occur. extracts from the original text for comparison purposes. See Appendix 1 to this document for a report of this investigation. Prior to the selection of the voltage and impedance parameters set forth in this Section of this document. stub configuration and the number of receivers connected. C. therefore. contains descriptions of the changes introduced into the Specification by this Supplement.5V to 10V “NULL” +2. Users desire protection against non-annunciated system operation in this mode. This protection may consist of additional circuitry to detect and annunciate the fault.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. B. In the absence of noise. The goldenrod pages should be inserted inside the rear cover of the Specification. for other than very minor revisions.2.5V to –13V In practice. B 747.5V “LO” -6.5V to –13V . modified to reflect these changes. 2. Existing copies of Specification 429 may be updated by simply inserting the replacement white pages where necessary and destroying the pages they replace. Thus.5V “LO” -6.2 Receiver Voltage Levels The differential voltage presented at the receiver input terminals will be dependent upon line length. and.g.2. No restriction is placed by this specification.2 RECEIVER VOLTAGE LEVELS Normal voltage ranges changed due to impedance changes. 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. PURPOSE OF THIS SUPPLEMENT This Supplement introduces material on fault detection.1 TRANSMISSION SYSTEM INTERCONNECT Text revised for break connections. cable characteristics and electrical mismatches can produce distortion of the digital data pulses. it is desirable that all DITS receivers will discontinue operation when the voltage levels fall into the undefined regions. any text originally contained in the Specification is reproduced for reference. CHANGES TO SPECIFICATION 429 INTRODUCED BY THIS SUPPLEMENT performance of a digital receiver depends upon the receiver input signal characteristics (data with distortion and noise) and the receiver design.SUPPLEMENT 5 TO ARINC SPECIFICATION 429 – Page 2 A. noise due to electrical interference perturbs digital signals.2. The Receiver reaction is currently undefined in Specification 429 for voltages that fall in the range just above and below the “NULL” range.5V to –2.2. Respective equipment Characteristics should be referenced for desired receiver response in this range. Manufacturers are urged. transmit intervals for words using multiple SDI codes. 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. these nominal voltages will be perturbed by noise and pulse distortion. modification of IRS/AHRS discrete formats. revision of ILS word. In each case there is included a brief description of the addition or change and. or by the section number and title that will be employed when the Supplement is eventually incorporated. Copies of the Specification bearing the number 429-5 already contain this Supplement and thus do not require revisions by the reader. the normal ranges of voltages presented to the receiver terminals (A and B) would be: “HI” +6. addition of new labels and change of existing data standards. printed on goldenrod paper. e. 2.3. Each change or addition is entitled by the section number and title currently employed in the Specification. However. Tests have shown that some receivers continue decoding data properly when one side of the transmission line is open or shorted to ground.. to “design in” the rejection capability. ORIGINAL TEXT FOLLOWS: This section presents a complete tabulation of the changes and additions to the Specification introduced by this Supplement. Also. COMMENTARY In practical wire line digital information transmission systems. Text added to Commentary describing increase of voltage threshold. expansion of error control definition.

COMMENTARY The time intervals between successive transmissions of a given BCD word specified in table 1 of Attachment 2 to this document are. (editorial) Bit 11 and 12 assigned to ILS category designation. 3-1: RADIO SYSTEMS MANAGEMENT WORD FORMATS Bits 3 and 7 of transponder word changed to “0”.4 ERROR DETECTION/CORRECTION Obsolete text deleted.2 INFORMATION RATES Text added to describe transmission of labels with multiple SDI codes.4 Error Detection/Correction The last bit of each word should be encoded such that word parity is rendered odd to allow error detection in receivers.5. it is desirable that data be refreshed at least once per transmission. . Receiver manufacturers are encouraged to work with the differential input voltage (line A to line B) and not line-to-ground voltages. 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. 9 through 29 contain an error control checksum computed from the states of bit nos. Discretes contained within data words should be transferred at the bit rate and repeated at the update rate of the primary data. The Mark 33 DITS contains no provisions for message retransmission.0V between the NULL and HI and NULL and LO states. Bit nos. too short for the signal to be of use in driving a display device directly. 2.SUPPLEMENT 5 TO ARINC SPECIFICATION 429 – Page 3 above-defined minimum difference of 4. 30 and 31 of this word contain the code identifying it as a final word. COMMENTARY There are no values given for refresh rates in this Specification.4 FINAL WORDS Text added to define checksum. 2. Bit nos.1. 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.4. If the signal was so used.3.3. the least significant character of the display would change too rapidly for human perception. 1 through 8 contain the file label. Fig. Bit nos. the inclusion of redundant bits in words or other means of error correction.1. ORIGIANL TEXT FOLLOWS: 2. in general.4 Final Words The final word of each record contains error control information. Bit no. 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 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. ORIGINAL TEXT FOLLOWS: 2. Note that the parity calculation encompasses all 31 label and information bits of the word. ORIGINAL TEXT FOLLOWS: 2. 9 through 31 of each intermediate word of the record. Control Panel Function Matrix added to transponder word. However. ORIGINAL MATERIAL ON NEXT PAGE: 2. Considerations other than human factors demand the time intervals specified. Words dedicated to discretes should be repeated continuously at the rates defined in Attachment 2. 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.4.3. 32 is encoded to render word parity odd.5.3.

174 03. 242 1A. 303 1A. 207 0A. Note added to 1A. 073 A2. 211 1A. 271 1A. . 306 1A. 264 0A. 262 0A. 346 1A. 305 1A. 340 2D. 272 1A. 215 1A. 112 02. Label 242** was deleted. 304 1A. 205 1A.01MHz (0) 0. 342 1A. Label 316 04 changed form “Wind Angle” to “Wind Direction (True)”.1MHz (3) LABEL ILS Frequency SPARE SPARE SPARE SPARE 10MHz (0) 1MHz (9) 8 7 6 5 4 3 2 1 1 1 0 1 10 0 0 ATTACHMENT 1: LABEL CODES The following labels have been given new assignments: 073 02. 352 1A. 265 0A. 350 1A. 271 1E. 270 1E. Example 32 1 31 30 0 0 29 28 27 0 0 0 26 25 24 23 1 0 0 1 22 21 20 19 0 0 1 1 18 17 16 15 0 0 0 0 14 0 13 0 12 0 11 0 10 9 0 0 RESERVED (SDI) Function 0. 345 1A. 270 1A. 325 1A. 351 1A. 301 1A. 274 0A. 260 31. 270 30. 340 1A. 130 1A. 245 0A. 256 0A. 133 1A. 164 03. 263 0A. ATTACHMENT 1: EQUIPMENT CODES New assignments were made for 0A and 2D. 151 02. 271 06. 353 1A.SUPPLEMENT 5 TO ARINC SPECIFICATION 429 – Page 4 Fig. 154 02. 164 02. 131 2D. 3-1: RADIO SYSTEMS MANAGEMENT WORD FORMATS (cont’d) ILS SIGN/STATUS MATRIX PARITY (odd) Bit No. 275 2B. 307 1A. 341 1A. 354 1A. 132 1A. 344 1A. 300 1A.

TR.01 o 0. 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.05 o 0. 400* 200* 125 125 125 125 50 50 50 50 50 50 20 20 50* 50* 50* 50* 50 50 62. Vel. TR. (EFI) Along Heading Accel. The following table lists the parameters for which the existing data standards have changed.5 62.01 o 16* 16* 0.SUPPLEMENT 5 TO ARINC SPECIFICATION 429 – Page 5 ATTACHEMENT 2: DATA STANDARDS Data standards were added for new labels.5* 62.5 62.0* 0.1: INTERVAL DISCRETES – LABEL 270 Discrete word formats revised.072 131.5 16* 16* 0.0* 1.05 o 0.5* 0. Vel. EQPT ID (HEX) 01 07 06 06 06 06 04 04 04 05 04 05 04 05 04 05 04 05 04 05 04 05 04 05 05 05 SIG.25* 20 20 25* 25* MAX.5 62.001 Note [2]: Guidance added for transmission intervals of labels with multiple SDI codes.25* 31. 200* 100* 62.0001* 0.9 4096* 2048* 512* 2045* ± 180o ± 180 o ± 180 o ± 180 o ± 180 o ± 180 o 2* 2* ± 180 o ± 180 o ± 180 o ± 180 o 16384* 16384* 131. DIG/ BITS 3 5 13* 13* 9* 11* 12* 12* 12* 12* 12* 12* 14* 14* 14 14 14 14 10* 10* 18* 18 10* 10* 12 12 MIN.072 16384* 16384* 4 4 POS. (EFI) Inertial Vert.5* 0. An asterisk beside a particular value designates that a new value is suggested. When heavy bus loading dictates a shift from the center of the range. Cross Heading Accel. the shift should be toward the maximum transmit interval. INT.001 0.05 o 0. INT. UNITS Feet Feet mMach* Knots mb mb Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 g g Deg/180 Deg/180 Deg/180 Deg/180 Ft/min Ft/min Feet Feet Ft/min Ft/min g g RANGE 0-79900 ± 0-7999.1 0. SENSE RESOL 100.05 o 0.05 o 0.0001* 0.5* 40 40 50* 50* LABEL 004 165 205 210 215 242 313 314 317 317 320 320 323 323 324 324 325 325 360 360 361 361 365 365 375 376 PARAMETER NAME Runway Distance to Go Radio Height Mach True Airspeed Impact Pressure Total Pressure Track Angle True True Heading Track Angle Magnetic Track Angle Magnetic Magnetic Heading Magnetic Heading Flight Path Acceleration Flight Path Acceleration Pitch Angle Pitch Angle Roll Angle Roll Angle Potential Vertical Speed Potential Vertical Speed Altitude (Inertial) Altitude (Inertial) Inertial Vert. TABLE 3.5 25 25 25 25 25 25 10 10 25* 25* 25* 25* 25 25 32.25* 1.0 0. .01 o 0. ORIGINAL TEXT FOLLOWS: [2] Transmit intervals and the number of parameters to be transmitted are prime factors in bus loading.01 o 0.05 o 0.

4 for further explanation). 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.2.1: Inertial Discretes – Label 270 Notes: [1] [2] Attitude invalid is equivalent to IRS failure. .SUPPLEMENT 5 TO ARINC SPECIFICATION 429 – Page 6 ORIGINAL TEXT FOLLOWS: Table 3. (See Section 3.

ORIGINAL TEXT FOLLOWS: Table 3. (editorial) .4: Air Data Discretes – Label 270 ATTACHMENT 6 – GENERAL WORD FORMATS AND ENCODING EXAMPLES Examples revised to agree with adopted data standards changes.SUPPLEMENT 5 TO ARINC SPECIFICATION 429 – Page 7 TABLE 3.4: AIR DATA DISCRETES Discrete word #1 format changed. Discrete word #2 added.

1981 . 2551 Riva Road Annapolis. 1982 Prepared by the Airlines Electronic Engineering Committee Adopted by the Airlines Electronic Engineering Committee: December 9. Maryland 21401 – 7645 USA SUPPLEMENT 6 TO ARINC SPECIFICATION 429 MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS) Published: January 22.AERONAUTICAL RADIO. INC.

The system indicators may or may not be flagged depending on system requirements. The second part consists of replacement white pages for the Specification.5. When such a condition exists. 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. 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.SUPPLEMENT 6 TO ARINC SPECIFICATION 429 – Page 2 A. contains descriptions of the changes introduced into the Specification by this Supplement. deletion of the weight & balance words. 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.5. or by the section number and title that will be employed when the Supplement is eventually incorporated. extracts from the original text for comparison purposes. as defined in sections 2. as defined in sections 2. PURPOSE OF THIS SUPPLEMENT This Supplement introduces the assignment of octal labels and hexadecimal equipment identifiers. This inability to compute reliable data is caused exclusively be a definite set of events or 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.5. Each change or addition is entitled by the section number and title currently employed in the Specification.1. and. When such a condition exists. “No Computed Data” and “Failure Warning”.2. C.1 BCD.5. AIM DATA AND FILE TRANSFER WORDS Commentary revised to reflect use of failure warning flags in discrete words. These failures are uniquely characterized by boundaries defined in the system characteristic. 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 . 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. where appropriate.5. 2.2 BNR NUMERIC DATA WORDS Commentary for failure warning revised. any text originally contained in the Specification is reproduced for reference. Copies of the Specification bearing the number 429-6 already contain this Supplement and thus do not require revisions by the reader. B. 2. the addition of guidance for label selection. Existing copies of Specification 429 may be updated by simply inserting the replacement white pages they replace. Failure Warning – is a particular case of data invalidity where the system monitors have detected one or more failures. The goldenrod pages should be inserted inside the rear cover of the Specification. as defined in sections2.1. There are two categories of invalid data. 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).1.1 and 2.5. These failures are uniquely characterized by boundaries defined in the system characteristic.1 and 2. Failure Warning – is a particular case of data invalidity where the system monitors have detected one or more failures. namely. printed on goldenrod paper.2.5.1.1 and 2. for other than very minor revisions. CHANGES TO SPECIFICATION 429 INTRODUCED BY THIS SUPPLEMENT conditions whose boundaries are uniquely defined in the system characteristic. There are two categories of invalid data namely. editorial revisions to the label tables and addition of EEC discrete word formats. The system indicators may or may not be flagged depending on system requirements.1. modified to reflect these changes. 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. ORGANIZATION OF THIS SUPPLEMENT The first part of this document.1. In each case there is included a brief description of the addition or change and. When such a condition exists. DISCRETE. the source system should annunciate its outputs to be invalid by setting the sign/status matrix of the affected words to the “NCD” code.1.2.1. The system indicators should always be flagged during a “Failure Warning” condition. a revision of failure warning annunciation in discrete words. The modified and added material on each replacement page is identified with “c6” symbols in the margins. NUMERIC. “No Computed Data” and “Failure Warning”. ORIGINAL TEXT FOLLOWS: COMMENTARY This section presents a complete tabulation of the changes and additions to the Specification introduced by this Supplement.5.

321 04. 322 04. 271 2F. 376 33. EEC discrete words added. 262 33. 375 33.5. 244 33. 133 2F. 344 2F. and 334 05 to match ARINC 704 and 705. ATTACHMENT 6: GENERAL WORD FORMATS AND CODING EXAMPLES Format added for label 262 02. The system indicators should always be flagged during a“Failure Warning” conditions. 157 33. and 34. 15 and 17 removed from table for note 1 of ATC transponder word (editorial). 274 2F. 342 2F. 071 33. 262 02. Editorial changes made. 271 3A. 241 2C. 263 33. 352 2F.5. 156 33. 270 2F. 315 05.1. 353 2F. Fig. 345 2F. 072 33. 252 2F. 160 33. 274 33. as defined in sections 2. ATTACHMENT 1: EQUIPMENT CODES New assignments were made for 0D. 3. 340 2F. Bit 12 corrected in DME distance word (editorial). 33. ATTACHMENT 2: DATA STANDARDS Data standards were added for new labels. “Predictive” deleted from 207 0A.1. 077 02. 334 04. 062 32. .1 RADIO SYSTEMS MANAGEMENT WORD FORMATS Assignments for bits 12. 130 2F. 155 33. Editorial changes were made to provide for consistency between Attachment 1 and Attachment 2. ATTACHMENT 1: LABEL CODES The following labels have been given new assignments: 021 02. 273 2F. The following labels have been deleted: 060 32. 354 2F. 132 33. 064 32.SUPPLEMENT 6 TO ARINC SPECIFICATION 429 – Page 3 sign/status matrix of the affected words to the “Failure Warning” code (BNR case). 041 02. APPENDIX 5: LABEL SELECTION GUIDANCE Appendix added. 264 2F. Nomenclature modified for 2C and 32. 261 33. Example added for GMT binary word. 260 33. 264 33. 043 02. 275 2F. 270 3A. 074 33.1 and 2. Resolutions revised for 315 04. 316 04. 341 2F. 321 05. 315 02. 115 2F. 114 2F. 072 2F. 351 2F.2. 346 2F. 352 2E. 344 33. 267 0A. 2E. 272 2F. 351 2E. 063 32. 250 2B. 3A. 267 33. 066 02. 042 02. 265 33. 075 02. 273 33. 2F. 3B. 061 32. 131 2F. 350 2F. 161 33.

1983 Prepared by the Airlines Electronic Engineering Committee Adopted by the Airlines Electronic Engineering Committee: November 4. 1982 . Maryland 21401 7645 USA SUPPLEMENT 7 TO ARINC SPECIFICATION 429 MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS) Published: January 3. INC.AERONAUTICAL RADIO. 2551 Riva Road Annapolis.

Existing copies of Specification 429 may be updated by simply inserting the replacement white pages they replace. Code 30 assigned as “Airborne Separation Assurance System”. 342 3F. 273 3B. 173 3B. 311 3B. 270 3B. 342 3B. Significant bits of label 321 changed from 12 to 11 (typo). 046 33. 256 2C. 131 30. and means for transmitting data with reduced accuracy. 130 3F. 132 30. 074 33. 275 3B. 247 2C 250 2C.5. Formats for ASAS words added.1 BCD. 130 30. 244 33. 325 3F. 271 3B. 270 33. 131 33. Station identifiers deleted on engine related parameters.SUPPLEMENT 7 TO ARINC SPECIFICATION 429 – Page 2 A. 264 33. ORGANIZATION OF THIS SUPPLEMENT The first part of this document. 265 33.1. 262 33. Note [6] added. and. In each case there is included and. or by the section number and title that will be employed when the Supplement is eventually incorporated. 351 3F. 352 3F. modified to reflect these changes. ATTACHMENT 6 – GENERAL WORD FORMATS AND ENCODING EXAMPLES . 273 3F. 340 33. NUMERIC. 272 3B. 270 2F-275 2F. 271 3F. 347 30. 271 33. 132 33. 346 33. Range of label 014 changed from 359 to 359. Note [5] added. 252 3F. 164 3B. 245 3B. The second part consists of replacement white pages for the Specification. 127 33. 350 2F. 114 3F. 353 3F. contains descriptions of the changes introduced into the Specification by this Supplement. 340 3F. The goldenrod pages should be inserted inside the rear cover of the Specification. Data standards added for the following existing labels: 270 3A. DISCRETE. B. 346 3F. 074 2C. 271 3A. AIM DATA AND FILE TRANSFER WORDS Note added to label 072 33. 242 3B. Note flag [5] added to following labels: 2. 212 3B. printed on goldenrod paper. C.9 (previously adopted). This section presents a complete tabulation of the changes and additions to the Specification introduced by this Supplement. 2. 047 33. PURPOSE OF THIS SUPPLEMENT This Supplement introduces new label assignments. Digits of label 014 changed from 3 to 4 (previously adopted). data standards and equipment identification codes. 214 3B. 247 3B. 272 3F. 270 3F. 175 33. CHANGES TO SPECIFICATION 429 INTRODUCED BY THIS SUPPLEMENT The terminology has been modified for the following labels: 072 33. The modified and added material on each replacement page is identified with “c-7” symbols in the margins. 345 3F. 344 3F. 263 33. 075 2C. 262 2C. any text originally contained in the Specification is reproduced for reference. 271 30.2 BNR NUMERIC DATA WORDS Note [6] added. Copies of the Specification bearing the number 429-7 already contain this Supplement and thus do not require revisions by the reader. Note [4] added. 341 3F. 325 2F. 274 3F. 246 3B. 377 30. 274 3B. 115 3F. 275 3F. 244 3B. ATTACHMENT 2 – DATA STANDARDS Data standards were added for new labels. 174 3B. 260 2C.-354 2F. for other than very minor revisions. Description of Code OD changed to “AIDS Data Management Unit (DMU)” Code 3F assigned as “Full Authority EEC_B”. ATTACHMENT 1 – LABEL CODES The following labels have been given new assignments: Formats for engine serial number words added. Each change or addition is entitled by the section number and title currently employed in the Specification. extracts from the original text for comparison purposes. ATTACHMENT 1 – EQUIPMENT CODES Code 2F changed from “EEC (Full Authority)” to “Full Authority EEC-A”. 257 2C. 270 30. where appropriate. 354 3F. 264 3F. 133 3F.1. 350 3F.5.

2551 Riva Road Annapolis. 1983 . 1984 Prepared by the Airlines Electronic Engineering Committee Adopted by the Airlines Electronic Engineering Committee: November 4.AERONAUTICAL RADIO. INC. Maryland 21401 – 7645 USA SUPPLEMENT 8 TO ARINC SPECIFICATION 429 MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS) Published: December 3.

the “all-call” code. ATTACHMENT 1 – LABEL CODES The following labels have been given new assignments: 012 25.3.4 Source/Destination Identifier Bit nos. revised data standards. Data standards revised for labels 115 2F. 274 25. 164 27. ATTACHMENT 6 – GENERAL WORD FORMATS Tire pressure SDI bit coding added. 9 0 1 0 1 Installation No. 313 25. which had been incorrectly introduced in a previous Supplement. 352 25. ORGANIZATION OF THIS SUPPLEMENT The first part of this document. ORIGINAL TEXT FOLLOWS: 2. PURPOSE OF THIS SUPPLEMENT This Supplement introduces new label assignments. Existing copies of Specification 429 may be updated by simply inserting the replacement white pages they replace. 325 2F. 154 27. CHANGES TO SPECIFICATION 429 INTRODUCED BY THIS SUPPLEMENT 10 0 0 1 1 Bit No.4 SOURCE DESTINATION IDENTIFIER Text added to clarify use of SDI on combined source/sink equipment. any text originally contained in the Specification is reproduced for reference. 275 25. This change is hereby noted. 062 3C. 334 3F. . extracts from the original text for comparison purposes. 140 25. Copies of the Specification bearing the number 429-8 already contain this Supplement and thus do not require revisions by the reader. 351 25.1. 162 27. A sink equipment should recognize words containing its own installation number code and words containing code “00”. 317 25. 141 25. One way would be to use program pins on the individual installation black boxes which would be wired to set up the appropriate code. When the SDI function is not used. 064 3C. ATTACHMENT 1 . 324 25. 353 25. The ARINC Characteristics devoted to the individual systems will define the method actually to be used. 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. The modified and added material on each replacement page is identified with “c-8” symbols in the margins. 270 25.0. 325 25. Data standards added for new labels. 332 2F.SUPPLEMENT 8 TO ARINC SPECIFICATION 429 – Page 2 A. 9 and 10 of numeric data words should be reserved for a data source/destination identification function. 173 25. 331 2F. C. 4” identifier. 334 2F. 320 25. 333 3F. Each change or addition is entitled by the section number and title currently employed in the Specification. 153 27. 370 C5. The goldenrod pages should be inserted inside the rear cover of the Specification. 137 3F. 170 C5. 2. printed on goldenrod paper. modified to reflect these changes. The second part consists of replacement white pages for the Specification. See Note Below 1 2 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. 157 27. a source equipment should encode its aircraft installation number in bit nos. and. 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. 156 27. or by the section number and title that will be employed when the Supplement is eventually incorporated. 164 25. expanded text describing SDI codes and makes note of a change in the resolution of the Magnetic Heading label incorporated in Supplement 7. 271 C5. 273 C5. 272 C5. 330 2F. 325 3F. 163 27. 061 3C.1. rather than 1.1. When it is used. 350 25. 137 2F.EQUIPMENT CODES This section presents a complete tabulation of the changes and additions to the Specification introduced by this Supplement. They are not available for this function in alpha/numeric (ISO Alphabet No. 9 and 10. binary zeros or valid data should be transmitted in bit nos. 142 25. ATTACHMENT 2 – DATA STANDARDS Table 1 had been modified in Supplement 7 to reflect the resolution of label 014 as 0. 314 25. 151 27. Code 3C assigned to Tire Pressure System. 9 and 10 as shown in the table below. 5) data words (See Section 2. 060 3C. 330 3F. In each case there is included a brief description of the addition or change and.1. 115 3F. where appropriate. 152 27. 160 27. contains descriptions of the changes introduced into the Specification by this Supplement. 063 3C. 155 27. B.3 of this document) or when the resolution needed for numeric (BNR/BCD) data necessitates their use for valid data. for other than very minor revisions. 332 3F. 165 27. 161 27.

Maryland 21401 – 7645 USA SUPPLEMENT 9 TO ARINC SPECIFICATION 429 MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS) Published: April 30. 1984 .AERONAUTICAL RADIO. INC. 1985 Prepared by the Airlines Electronic Engineering Committee Adopted by the Airlines Electronic Engineering Committee: October 11. 2551 Riva Road Annapolis.

This Supplement also corrects a word format bit error introduced in a previous Supplement. 272 18. 274 18. or by the section number and title that will be employed when the Supplement is eventually incorporated. modified to reflect these changes.SUPPLEMENT 9 TO ARINC SPECIFICATION 429 . for other than very minor revisions. 350 18. 347 18. 132 35. where appropriate.Page 2 A. . 104 1B. 130 35. C. In each case there is included a brief description of the addition or change and. The second part consists of replacement white pages for the Specification. 350 35. PURPOSE OF THIS SUPPLEMENT This Supplement introduces new label assignments and equipment identification codes. ATTACHMENT 1 – EQUIPMENT CODES Codes 3D. Copies of the Specification bearing the number 429-9 already contain this Supplement and thus do not require revisions by the reader. 275 18. any text originally contained in the Specification is reproduced for reference. 107 1B. ORGANIZATION OF THIS SUPPLEMENT The first part of this document. 271 35. 103 1B. ATTACHMENT 6 – GENERAL WORD FORMATS AND ENCODING EXAMPLES Label 150 and 323 examples corrected. 271 18. contains descriptions of the changes introduced into the Specification by this Supplement. The modified and added material on each replacement page is identified with “c9” symbols in the margins. 076 3E. 300 3D. 276 18. 274 35. and. 131 35. ATTACHMENT 2 – DATA STANDARDS Data standards entered for new labels. 273 35. 270 35. 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. 270 3E. 272 35. 347 35. ATTACHMENT 1 – LABEL CODES The following labels have been given new assignments: 075 3E. 3E. B. Each change or addition is entitled by the section number and title currently employed in the Specification. Range for labels 012 and 170 changed to 7999. 270 4A. extracts from the original text for comparison purposes. 275 4A. 4A. 203 18. 4C and 90-9F given new assignments. Existing copies of Specification 429 may be updated by simply inserting the replacement white pages they replace. and 370 05. 350 3E. 105 1B. The goldenrod pages should be inserted inside the rear cover of the Specification. 270 1B. 336 1A. 106 1B. 4B. printed on goldenrod paper. 337 1A. 370 04. 273 18.

1985 . 2551 Riva Road Annapolis. INC. 1986 Prepared by the Airlines Electronic Engineering Committee Adopted by the Airlines Electronic Engineering Committee: November 7.AERONAUTICAL RADIO. Maryland 21401 – 7645 USA SUPPLEMENT 10 TO ARINC SPECIFICATION 429 MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS) Published: November 17.

202 5A. 356 XX. 273 3F. Data standards revised for the following labels: 060 36. 273 5A. 176 29. 36.4 FREQUENCY RANGES AND SWITCHING FUNCTIONS Note 6 deleted on DME Frequency Word.1. 062 3C. 5D. modified to reflect these changes. Special expanded format word example added for label 260 31. 077 0B. Labels 176 03 and 176 29 resolutions changed from 0. 242 10. 273 2F. Bit 27 assigned to a value of “1024”. 076 0B. Existing copies of Specification 429 may be updated by simply inserting the replacement white pages they replace. 241 4D. 336 3F. 061 3C. for other than very minor revisions. 8C. Copies of the Specification bearing the number 429-10 already contain this Supplement and thus do not require revisions by the reader. 176 03. ORGANIZATION OF THIS SUPPLEMENT The first part of this document. 276 3F. Attachment 9A – General Aviation Labels and Data Standards New attachment added. 247 4D. 271 3F. 38. 7F. 201 5A. 270 3F. 251 1A. 176 5A. The second part consists of replacement white pages for the Specification. 353 2F. 37.05 to 0. 203 5A. 077 0B and 206 18. The modified and added material on each replacement page is identified with “c-10” symbols in the margins. In each case there is included a brief description of the addition or change and. contains descriptions of the changes introduced into the Specification by this Supplement. 270 2F. equipment identification codes and revised data standards. This section presents a complete tabulation of the changes and additions to the Specification introduced by this Supplement. or by the section number and title that will be employed when the Supplement is eventually incorporated. 064 3C. 213 8D. Attachment 1 – Label Codes The following labels have been given new assignments: 072 02. 255 3F. printed on goldenrod paper. 352 2F. SDI labels clarified. 350 2F. 353 3F. any text originally contained in the Specification is reproduced for reference. 276 2F. 274 5A. Attachment 6 – General Word Formats and Encoding Examples Example added for label 251 1A. C. 272 3F. Slight variations of bit usage may arise according to the specific application. 335 2F. Attachment 1 – Equipment Codes Attachment 9C – General Aviation Equipment Identifiers The following codes have been given new assignments: New attachment added. 5E. #12 labels corrected to read “116”. 075 0B. B. 351 2F.SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 2 A PURPOSE OF THIS SUPPLEMENT This Supplement introduces new label assignments. 275 5A. 5F. 7C. . SDI labels clarified. 6E. extracts from the original text for comparison purposes. 242 11. 200 5A. Following note added to words (labels 270 3B-275 3B): Typical discrete functions are shown in the above tables. 6A. and. 063 3C. 35. 272 5A. 272 2F. 336 2F. 242 12. 206 18. Labels for ARINC Characteristic 737 WBT and ARINC Characteristic 738 ADIRS added. AD. 6C. 150 31. 204 5A. 351 3F. 275 2F.5 (typographical error). 244 8D. 354 3F. For BTMS word formats: Wheel #10. 256 4D. 350 3F. 274 2F. 352 3F. 272 3A. Each change or addition is entitled by the section number and title currently employed in the Specification. 7B. 177 5A. 275 3F. 8D. 3. 0B. 371 00. 6B. 255 2F. 4E. Original bit assignments for remaining labels listed in following pages. 5C. 205 5A. 7D. 8B. 354 2F. 5A. 271 2F. Attachment 9B – General Aviation Word Examples New attachment added. 5B. 6D. 8A. Labels 060 37-064 3C significant bits changed from 9 to 10 and range changed from 512 to 1024. The goldenrod pages should be inserted inside the rear cover of the Specification. For TPIS word formats: Wheel #519 label corrected to read “060”. 227 7E. Label 203 35 changed to 203 18 (typographical error). 242 09. #11. 4D. CHANGES TO SPECIFICATION 429 INTRODUCED BY THIS SUPPLEMENT Attachment 2 – Data Standards Data standards entered for new labels. 270 3A. 7A. 7E. 274 3F. 270 0B. C3. Transmit interval range added to label 150 31. where appropriate. 6F.

11 Propulsion Discrete Interface Unit – Labels 270 3A and 271 3A Label 270 3A Bit Status Bit No.SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 3 Table 3. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X Label X X X X X X SDI 1 Left Engine 0 Failed HEAT OFF FAULT MINIMUM GROUND SHUT DOWN RELEASED OK HEAT ON OK APPROACH AIR RUNNING X X FIXED X X X OFF OFF X OK STOWED NOT DEPLOYED OFF Right Engine SDI 0 1 PDIU Status Flag T2 / P2 Probe Heat TLA Interlock Fault Idle Select Air/Ground Switch Opposite Engine Status Spare Spare N2 Mode Trim Release (PROV) Spare Spare Spare Maintenance Test (Provisional) Ground Test Power Spare T/R Indication Power Failed (PROV) T/R Not Stowed T/R Deployed Indication Engine Fire Warning SSM SSM Parity (Odd) 1 = RETURN TO SPARE 2 = CHANGE SPARE TO DEFINITION ON NEXT PAGE 0 X Notes 1 2 1 ON ON FAILED NOT STOWED DEPLOYED ON 1 1 1 1 1 .

270 3F. 274 3F. 274 2F. 272 3F. 272 2F. 271 3F. 275 3F Label 270 2F Bit Status Bit No. 271 2F.12 EEC Status – Labels 270 2F. 275 2F. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X X X X X X X SDI SDI PAD PAD PAD Spare Data Entry Plug Auto Mode Channel Manually Selected N2 Droop Control Mode Reverser System Failed Channel Controlling Status Bleed Fall-Safe Open TCA Valve Failed Closed Spare Overspeed Self-Test Failed Channel Incapable (Failed) Abnormal Start SVA Fall-Safe Starter Cutout Command Oil Overtemperature SSM SSM Parity (Odd) 1 = RETURN TO SPARE 2 = CHANGE SPARE TO DEFINITION ON NEXT PAGE 3 = CHANGE DEFINITION TO DEFINITION ON NEXT PAGE X X X X Normal Not Selected Not Selected Not Engaged OK Not Controlling Operational OK X OK Capable OK (Provision) Not Cutout OK 0 X Label Notes Failed Selected Selected Engaged Failed Controlling Fall-Safe Failed Failed Incapable Abnormal Fall-Safe Cutout Overtemp 2 1 3 3 3 2 3 3 3 1 .SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 4 Table 3. 273 2F. 273 3F.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X X X X X X X SDI SDI PAD PAD PAD Spare Data Entry Plug Auto Mode Channel Manually Selected N2 Droop Control Mode Reverser System Failed Channel Controlling Status Bleed Fall-Safe Open TCA Valve Failed Closed Spare Overspeed Self-Test Failed Channel Incapable (Failed) Abnormal Start SVA Fall-Safe Starter Cutout Command Oil Overtemperature SSM SSM Parity (Odd) X X X X Normal Not Selected Not Selected Not Engaged OK Not Controlling Operational OK X OK Capable OK (Provision) Not Cutout OK 0 X Label Notes Failed Selected Selected Engaged Failed Controlling Fall-Safe Failed Failed Incapable Abnormal Fall-Safe Cutout Overtemp 2 1 3 3 3 2 3 3 3 1 .SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 5 Label 270 3F Bit Status Bit No.

SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 6 Label 271 2F Bit Status Bit No. Spare Spare Spare Spare Autostar Relay TLA Interlock Actuator Command Spare Reverser Group Relay Spare Spare Spare Spare SSM SSM Parity (Odd) X X X OFF OFF OFF OFF OFF X X X X OFF (Provision) Block Rev OFF (Provision) X X X X 0 X Label Notes ON ON ON ON ON 3 1 1 2 ON Block Fwd ON 1 1 2 2 2 2 . 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X X X X X X X SDI SDI PAD PAD PAD Reverser Deploy Command Turbine Cooling Air Valve Solenoid Oil Cooler Bypass Valve Solenoid Cowl Vent Solenoid Breather Compartment Ejector Sol.

SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 7 Label 271 3F Bit Status Bit No. Spare Spare Spare Spare Autostar Relay TLA Interlock Actuator Command Spare Reverser Group Relay Spare Spare Spare Spare SSM SSM Parity (Odd) X X X OFF OFF OFF OFF OFF X X X X OFF (Provision) Block Rev OFF (Provision) X X X X 0 X Label Notes ON ON ON ON ON 3 1 1 2 ON Block Fwd ON 1 1 2 2 2 2 . 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X X X X X X X SDI SDI PAD PAD PAD Reverser Deploy Command Turbine Cooling Air Valve Solenoid Oil Cooler Bypass Valve Solenoid Cowl Vent Solenoid Breather Compartment Ejector Sol.

9 Topping Loop Back Up Mode Spare Spare Spare Spare Spare Spare SSM SSM Parity (Odd) X X X Not Engaged Not Engaged Not Engaged Not Engaged Not Engaged Not Engaged Not Engaged Not Engaged Not Engaged Not Engaged X X X X X X 0 X Label Notes Engaged Engaged Engaged Engaged Engaged Engaged Engaged Engaged Engaged Engaged 1 2 . 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X X X X X X X SDI SDI PAD PAD PAD N1 Loop N2 Loop N2 Topping Loop PB Topping Loop PB Topping Loop Minimum EPR Loop Acceleration Schedule Loop Deceleration Schedule Loop T4.SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 8 Label 272 2F Bit Status Bit No.

9 Topping Loop Back Up Mode Spare Spare Spare Spare Spare Spare SSM SSM Parity (Odd) X X X Not Engaged Not Engaged Not Engaged Not Engaged Not Engaged Not Engaged Not Engaged Not Engaged Not Engaged Not Engaged X X X X X X 0 X Label Notes Engaged Engaged Engaged Engaged Engaged Engaged Engaged Engaged Engaged Engaged 1 2 .SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 9 Label 272 3F Bit Status Bit No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X X X X X X X SDI SDI PAD PAD PAD N1 Loop N2 Loop N2 Topping Loop PB Topping Loop PB Topping Loop Minimum EPR Loop Acceleration Schedule Loop Deceleration Schedule Loop T4.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X X X X X X X SDI SDI PAD PAD PAD P4.9 Sensor Prom Failed P2 (Pamb) Sensor Prom Failed* PB Sensor Prom Failed Background is not Executing SSM SSM Parity (Odd) X X X OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK Executing 0 X Label Notes Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Not Executing 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 * Primary channel uses P2.SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 10 Label 273 2F Bit Status Bit No. .9 Interface Failed PB Interface Failed P2 (Pamb) Interface Failed* C3C Interface Failed T2 Interface Failed T4. Secondary channel uses Pamb.9 Interface Failed Tfuel Interface Failed A/D Interface Failed RES/LVDT Interface Failed SVA Interface Failed N1 Interface Failed N2 Interface Failed P4.

.9 Sensor Prom Failed P2 (Pamb) Sensor Prom Failed* PB Sensor Prom Failed Background is not Executing SSM SSM Parity (Odd) X X X OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK Executing 0 X Label Notes Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Not Executing 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 * Primary channel uses P2. Secondary channel uses Pamb. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X X X X X X X SDI SDI PAD PAD PAD P4.9 Interface Failed PB Interface Failed P2 (Pamb) Interface Failed* C3C Interface Failed T2 Interface Failed T4.9 Interface Failed Tfuel Interface Failed A/D Interface Failed RES/LVDT Interface Failed SVA Interface Failed N1 Interface Failed N2 Interface Failed P4.SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 11 Label 273 3F Bit Status Bit No.

SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 12 Label 274 2F Bit Status Bit No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X X X X X X X SDI SDI PAD PAD PAD Parity Test Hardware Fault ROM Checksum Failure Ram Test Failure Instruction Test Failure High Speed Cross Link Failure Foreground Software Execution Watch Dog Timer Fault Watch Dog/Parity Counter Latch EAROM Failure ROM Parity Error Caused Reset RAM Parity Error Caused Reset Watchdog Timer Error Caused Reset Status Buffer or Watchdog/Parity Loss of Clock Caused Reset SDD Output #1 W/A SDD Output #2 W/A SSM SSM Parity (Odd) X X X OK OK OK OK OK Correctly OK Not Latched OK No No No OK No OK OK 0 X Label Notes Error Failed Failed Failed Failed Incorrectly Error Latched Failed Yes Yes Yes Failed Yes Failed Failed 3 3 3 3 3 3 1 3 3 .

SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 13 Label 274 3F Bit Status Bit No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X X X X X X X SDI SDI PAD PAD PAD Parity Test Hardware Fault ROM Checksum Failure Ram Test Failure Instruction Test Failure High Speed Cross Link Failure Foreground Software Execution Watch Dog Timer Fault Watch Dog/Parity Counter Latch EAROM Failure ROM Parity Error Caused Reset RAM Parity Error Caused Reset Watchdog Timer Error Caused Reset Status Buffer or Watchdog/Parity Loss of Clock Caused Reset SDD Output #1 W/A SDD Output #2 W/A SSM SSM Parity (Odd) X X X OK OK OK OK OK Correctly OK Not Latched OK No No No OK No OK OK 0 X Label Notes Error Failed Failed Failed Failed Incorrectly Error Latched Failed Yes Yes Yes Failed Yes Failed Failed 3 3 3 3 3 3 1 3 3 .

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X X X X X X X SDI SDI PAD PAD PAD Lamp (1. Secondary channel uses Pamb. .9 Sensor Failed PT2 (Pamb)* Sensor Failed EEC Temperature Status X X X OK Agree OK OK OK OK 0 X Label Notes Failed Disagree Failed Failed Failed High 3 3 3 3 3 2 2 2 2 2 2 2 2 2 Spare (all “o” states) SSM SSM Parity (Odd) [3] Primary channel uses PT2.2 &/or 3) W/A Failed Other Channels Depower Discrete PB Sensor Failed PT4.SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 14 Label 275 2F Bit Status Bit No.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X X X X X X X SDI SDI PAD PAD PAD Lamp (1.SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 15 Label 275 3F Bit Status Bit No. .2 &/or 3) W/A Failed Other Channels Depower Discrete PB Sensor Failed PT4.9 Sensor Failed PT2 (Pamb)* Sensor Failed EEC Temperature Status X X X OK Agree OK OK OK OK 0 X Label Notes Failed Disagree Failed Failed Failed High 3 3 3 3 3 2 2 2 2 2 2 2 2 2 Spare (all “o” states) SSM SSM Parity (Odd) CHANGE * Primary channel uses PT2: Secondary channel uses Pamb.

354 2F. 354 3F Label 350 2F Bit Status Bit No.9 Failed Tfuel Failed Toll Failed Wf Resolver Failed SVA LVDT Failed Bleed Prox Input Failed ACC #1 LVDT Failed ACC #2 LVDT Failed Reverser LVDT Failed AOC LVDT Failed Spare LVDT Failed TLA Resolver Failed Oil Overtemperature SSM SSM Parity (Odd) X X X OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK 0 Notes Label X Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Overtemp 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 1 . 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X X X X X X X SDI SDI PAD PAD PAD N1 Failed N2 Failed TT2 Failed TT4. 350 3F. 352 3F. 353 3F.13 EEC Maintenance – Labels 350 2F. 351 2F. 353 2F.SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 16 Table 3. 351 3F. 352 2F.

SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 17 Label 350 3F Bit Status Bit No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X X X X X X X SDI SDI PAD PAD PAD N1 Failed N2 Failed TT2 Failed TT4.9 Failed Tfuel Failed Toll Failed Wf Resolver Failed SVA LVDT Failed Bleed Prox Input Failed ACC #1 LVDT Failed ACC #2 LVDT Failed Reverser LVDT Failed AOC LVDT Failed Spare LVDT Failed TLA Resolver Failed Oil Overtemperature SSM SSM Parity (Odd) X X X OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK 0 Notes Label X Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Overtemp 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 1 .

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X X X X X X X SDI SDI PAD PAD PAD Left ADC Inputs Failed Right ADC Inputs Failed Wf T/M W/A Failed SVA T/M W/A Failed BLD T/M W/A Failed ACC #1 T/M W/A Failed ACC #2 T/M W/A Failed AOC T/M W/A Failed Spare T/M W/A Failed Wf Track Check Failed SVA Track Check Failed Bld Track Check Failed ACC #1 Track Check Failed ACC #2 Track Check Failed AOC Track Check Failed Spare Track Check Failed SSM SSM Parity (Odd) X X X OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK 0 Notes Label X Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed 3 3 3 3 3 3 3 3 1 3 3 3 3 3 3 1 .SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 18 Label 351 2F Bit Status Bit No.

SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 19 Label 351 3F Bit Status Bit No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X X X X X X X SDI SDI PAD PAD PAD Left ADC Inputs Failed Right ADC Inputs Failed Wf T/M W/A Failed SVA T/M W/A Failed BLD T/M W/A Failed ACC #1 T/M W/A Failed ACC #2 T/M W/A Failed AOC T/M W/A Failed Spare T/M W/A Failed Wf Track Check Failed SVA Track Check Failed Bld Track Check Failed ACC #1 Track Check Failed ACC #2 Track Check Failed AOC Track Check Failed Spare Track Check Failed SSM SSM Parity (Odd) X X X OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK 0 Notes Label X Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed 3 3 3 3 3 3 3 3 1 3 3 3 3 3 3 1 .

2 Channel Select Discrete PDIU SDD Input Failed N1 Sensor Failed* Pb Pneumatic Line* P4.9 Thermocouple Harness* PDIU Status T/L Forward Interlock SSM SSM Parity (Odd) *Primary channel only.SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 20 Label 352 2F Bit Status Bit No. 1 TCA Valve No. X X X X X X X X X OK OK OK OK OK (Provision) OK (Provision) OK (Provision) OK (Provision) OK OK 0 Notes Label X 1 1 2 2 2 3 3 3 3 3 3 3 3 Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed .9 Pneumatic Line* TT4. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X X X X X X X SDI SDI PAD PAD PAD Spare Spare Spare Spare Spare Spare TCA Valve No.

SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 21 Label 352 3F Bit Status Bit No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X X X X X X X SDI SDI PAD PAD PAD Spare Spare Spare Spare Spare Spare TCA Valve No.9 Pneumatic Line* TT4.9 Thermocouple Harness* PDIU Status T/L Forward Interlock SSM SSM Parity (Odd) * Primary channel only. 1 TCA Valve No. X X X X X X X X X OK OK OK OK OK (Provision) OK (Provision) OK (Provision) OK (Provision) OK OK 0 Notes Label X 2 2 2 2 2 3 3 3 3 3 3 3 3 Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed . 2 Channel Select Discrete PDIU SDD Input Failed N1 Sensor Failed* Pb Pneumatic Line* P4.

9 Crosscheck Failed TT2 Crosscheck Failed TT4.SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 22 Label 353 2F Bit Status Bit No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X X X X X X X SDI SDI PAD PAD PAD N1 Crosscheck Failed N2 Crosscheck Failed PB Crosscheck Failed PT4.9 Crosscheck Failed Tfuel Crosscheck Failed Toil Crosscheck Failed Wf Resolver Crosscheck Failed SVA Resolver Crosscheck Failed Bld Prox Input Crosscheck Failed ACC #1 LVDT Crosscheck Failed ACC #2 LVDT Crosscheck Failed Reverser LVDT Crosscheck Failed AOC LVDT Crosscheck Failed TLA Resolver Crosscheck Failed SSM SSM Parity (Odd) X X X OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK 0 Notes Label X Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed 3 3 1 1 3 3 3 3 3 3 3 3 3 3 3 3 .

9 Crosscheck Failed Tfuel Crosscheck Failed Toil Crosscheck Failed Wf Resolver Crosscheck Failed SVA Resolver Crosscheck Failed Bld Prox Input Crosscheck Failed ACC #1 LVDT Crosscheck Failed ACC #2 LVDT Crosscheck Failed Reverser LVDT Crosscheck Failed AOC LVDT Crosscheck Failed TLA Resolver Crosscheck Failed SSM SSM Parity (Odd) X X X OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK 0 Notes Label X Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed 3 3 1 1 3 3 3 3 3 3 3 3 3 3 3 3 . 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X X X X X X X SDI SDI PAD PAD PAD N1 Crosscheck Failed N2 Crosscheck Failed PB Crosscheck Failed PT4.SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 23 Label 353 3F Bit Status Bit No.9 Crosscheck Failed TT2 Crosscheck Failed TT4.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X X X X X X X SDI SDI PAD PAD PAD REV Command Solenoid W/A Failure TCA Solenoid W/A Failure Spare Solenoid W/A Failure Spare Solenoid W/A Failure Spare Relay W/A Failure Spare Solenoid W/A Failure BCE Solenoid W/A Failure Spare Solenoid W/A Failure Oil Bypass Solenoid W/A Failure Hot Start Relay W/A Failure TLA Lockout Relay W/A Failure Spare Relay W/A Failure Spare Essen. Sol.SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 24 Label 354 2F Bit Status Bit No. Current Sense Failure Critical & Noncritical Current Sense Failure Spare SSM SSM Parity (Odd) X X X OK OK OK OK OK OK OK OK OK OK OK OK X OK OK 0 Notes Label X Failure Failure Failure Failure Failure Failure Failure Failure Failure Failure Failure Failure Failure Failure 3 3 1 1 1 3 1 1 3 1 3 1 1 3 3 .

Current Sense Failure Critical & Noncritical Current Sense Failure Spare SSM SSM Parity (Odd) X X X OK OK OK OK OK OK OK OK OK OK OK OK X OK OK 0 Notes Label X Failure Failure Failure Failure Failure Failure Failure Failure Failure Failure Failure Failure Failure Failure 3 3 1 1 1 3 1 1 3 1 3 1 1 3 3 . Sol. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X X X X X X X SDI SDI PAD PAD PAD REV Command Solenoid W/A Failure TCA Solenoid W/A Failure Spare Solenoid W/A Failure Spare Solenoid W/A Failure Spare Relay W/A Failure Spare Solenoid W/A Failure BCE Solenoid W/A Failure Spare Solenoid W/A Failure Oil Bypass Solenoid W/A Failure Hot Start Relay W/A Failure TLA Lockout Relay W/A Failure Spare Relay W/A Failure Spare Essen.SUPPLEMENT 10 TO ARINC SPECIFICATION 429 – Page 25 Label 354 3F Bit Status Bit No.

INC. Maryland 21401 – 7645 USA SUPPLEMENT 11 TO ARINC SPECIFICATION 429 MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS) Published: July 22. 2551 Riva Road Annapolis. 1988 Prepared by the Airlines Electronic Engineering Committee Adopted by the Airlines Electronic Engineering Committee: June 15. 1988 .AERONAUTICAL RADIO.

0CD. ATTACHMENT 2 – DATA STANDARDS Data Standards entered for new labels: Label 076 008 changed from “Ellipsoidal Altitude” to “GPS Height Above Referenced Ellipsoid”. 070 0CC. 0BF. 301 040. 0CE. 10C. 0BB. 0AC. PURPOSE OF THIS SUPPLEMENT This Supplement introduces new label assignments and equipment identification codes. 307 040. Aim Data. 072 0CC. 242 011. contains descriptions of the changes introduced into the Specification by this Supplement. 350 00B. 126 002. extracts from the original text for comparison purposes. 256 002. 225 002. ATTACHMENT 9 – GENREAL EQUIPMENT IDENTIFIERS Code 08C added to list. 12B. 350 027. 2. printed on goldenrod paper. 223 002. 110. 257 002. where appropriate. 264 002. 253 002. 246 009. 264 010. Example for label 260 removed. 0DE. 0DC. 247 0EB. 10B. 08F. 0DF. 276 002. 08E. 136. 224 017. The second part consists of replacement white pages for the Specification. 141. ATTACHMENT 1 – EQUIPMENT CODES The following codes have been given new assignments: 039. any text originally contained in the Specification is reproduced or reference. 246 002. 10E. 220 07E. 341. 305 040. 255 08E. 100 0BB. 322 002. The modified and added material on each replacement page is identified with “c-11” symbols in the margins. 205 0B9. 303 002. Discrete. 213 08D. 246 006. 0CC. 200 002. 314 002. 224 002. Format for label 350 027 added. 302 002. 221 024. 103 0BB.5. 221 002. for other than very minor revisions. 316 002. 300 040. ATTACHMENT 1 – LABEL CODES 070 002. 205 002. 077 00B. 306 040. 12A. 276 001. 127 002. 173 0BD. The goldenrod pages should be inserted inside the rear cover of the Specification. 222 002. 073 0CC. Code for 747 NR corrected in diagram of TPIS word. 360 002. 152 041. 206 0CC. Codes for Loran and Omega changed from 08A/08B to 05A/05B. 143 241. 0AA. 351 029. 254 012. 230 024. 222 07E. 153 041. CHANGES TO SPECIFICATION 429 INTRODUCED BY THIS SUPPLEMENT 271 002. 250 002. C. 115 0BC. 10A. 144 341. 072 002. 211 002. 220 024. 114 0CC. 307 039. 202 002. 106 0BB. 071 0CC. 0BC. 245 002. 351 00B. 10D. 350 040. and. 354 002. 255 002. 223 024. 0FF. 263 002. 10C. Label 076 008 changed from “Ellipsoidal Altitude” to “GPS Height Above Referenced Ellipsoid”. and File Transfer Words SSM bit patterns separated from main figure. 276 003. 247 009. 105 0BB.1 BCD Numeric. 306 039. 252 0EB. 0CA. 0DD. 230 017. FIGURE 3-1 RADION SYSTEMS MANAGEMENT WORD FORMATS HF COM frequency control words added. 301 002. 220 002. Data Standards revised for following labels: 076 00B. 041. In each case there is included a brief description of the addition or change and. Copies of the Specification bearing the number 429-11 already contain this Supplement and thus do not require revisions by the reader. 244 011. 0AB. 342 002. 244 08D. 341 002. 241. 350 341. 230 07E. 101 0BB. This section presents a complete tabulation of the changes and additions to the Specification introduced by this Supplement. Example for label 260 031 expanded to include 260 002. 256 027. 0AE. 204 002. 223 07E. 0CB. 107 002. 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. 275 002. 104 0BB. 274 0C5. 0BD.143 041. 221 07E. Existing copies of Specification 429 may be updated by simply inserting the replacement white pages they replace. modified to reflect these changes. Format for label 274 0C5 added. 263 010. 071 002. 222 017. 355 027. 304 040. 207 0B9. 162 0DE. 254 002. 0EA. 221 017. 302 040. 213 002. ORGANIZATION OF THIS SUPPLEMENT The first part of this document. 343 01A. 10F. 0C2.SUPPLEMENT 11 TO ARINC SPECIFICATION 429 – Page 2 A. respectively. 0DB. 0DA. 117 0CC. B. 350 241. 074 002. Equipment ID word expanded to accommodate threecharacter identifier. 257 027. 0BE. 241 002. Format for label 270 00B added. 230 002. 255 012. 115 0CC. 0CF. 270 00B ATTACHMENT 6 Example revised for label 077 00B. 300 039. 302 039. 222 024. 224 07E. 0BA.203 002. 226 0XX. AVIATION . 265 002. 144 041. 207 002. 304 039. 250 12B. 0AF. 153 002. 243 0XX. 040. 223 017. 247 002.1. 224 024. 116 0CC. 150 002. 220 017. 301 039. 267 002. 305 039.

1989 . Maryland 21401 – 7645 USA SUPPLEMENT 12 TO ARINC SPECIFICATION 429 MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS) Published: July 1. INC.NOTE: Due to the large number of changes Created by this Supplement. AERONAUTICAL RADIO. it is NOT available separately to update 429-11. 1990 Prepared by the Airlines Electronic Engineering Committee Adopted by the Airlines Electronic Engineering Committee: October 25. 2551 Riva Road Annapolis.

267 10A. 274 10A. 351 10B. 272 114. 127 10B. 311 114. 372 10A. 310 114. 360 10A. 337 10A. 257 114. 335 10B. 270 10B. 343 10B. 363 10B. 375 10A. 221 116. 203 035. 372 10B. 260 10B. Revised label 131 035 from “Traffic Advisory Altitude” to “Intruder Altitude”. 110 0BB. The changes include moving the AIM and file transfer SSM definitions to Appendix 6. 330 10B. 265 004. 331 10B. 260 114. .4 through 2. 276 114. 237 039. 350 10B. 323 10A. 350 114. 324 10B. 114 10B. 275 10A. 130 10A130 10B. 236 040.3. 337 002. 327 10A. 271 10A.1. 300 TBD. 346 10A.3. 365 TBD. 263 114. 363 10A. 271 114. 354 10B. 205 10B. 273 10B. 375 10B. 156 10A. 300 10A. Section 2. 244 10A. 264 10B. 330 10A. 131 035.223 116.1. 016 0B8. or by the section number and title that will be employed when the Supplement is eventually incorporated. 046 10B. 352 114.3. 261 10A. ORGANIZATION OF THIS SUPPLEMENT The first part of this document.5. 341 10A. 267 10B. This section presents a complete tabulation of the changes and additions to the Specification introduced by this Supplement. In each case there is included a brief description of the addition or change and. 156 10B. 203 10B. 261 10B. 262 10A. 211 10B. provides the reason for moving the original file transfer protocol and introduces the Williamsburg protocol. 316 10A. 261 114. 326 10B. 357 035. 013 0B8. 270 115. 130 035. 274 10B. 322 10B. 305 10B. 316 10B. 325 10A. 322 10A. 351 114. 373 10B. 226 035. 302 10A. 342 10A. 345 10B. 265 10A. 237 040. 272 10A. printed on goldenrod paper contains descriptions of the changes introduced into the Specification by this Supplement. 211 10A. 347 10B. 354 10A. 362 115. 235 039. 273 114.3. 137 10A. extracts from the original text for comparison purposes. 132 035. any text originally contained into the Specification reproduced for reference. where appropriate. 046 10A.5. this Supplement introduces new label assignments and equipment identification codes. 265 038. 3. 353 10B.5. Copies of the Specification bearing the number 429-12 already contain this Supplement and thus do not require revisions by the reader. The goldenrod pages should e inserted inside the rear cover of the Specification. 350 115. Revised label 132 035 from “Traffic Advisory Bearing” to “Intruder Bearing”. 047 10B. 304 10B. 2. 224 116. The new protocol was developed to accommodate the interface of the ACARS Management Unit (MU) and the Satellite Data Unit (SDU). 353 114.1. 320 035. 265 10B.5 Bit-Oriented Communications Protocol This new section was added to describe a bit-oriented data transfer protocol. 134 10B. 344 10B. 157 10B. 343 10A. 303 10B. C. 270 114. 114 10A. for other than very minor revision. 234 039. 344 10A. 327 10B.SUPPLEMENT 12 TO ARINC SPECIFICATION 429 – Page 2 A. 325 10B. 353 10A. 312 114. ATTACHMENT 1 – LABEL CODES The following labels have been given new assignments: 002 115. modified to reflect these changes. 112 0BB. 360 TBD. 262 10B. 323 10B.1. 346 10B. 336 002. The modified and added material on each replacement page is identified with “c-12” symbols in the margins. 306 10D. 256 114. 352 10A.5. 341 10B.2 AIM Information Transfer The information previously contained in this section is no longer applicable to ARINC Specification 429. 374 10B. 230 116. 324 10A. 244 10B. 205 10A. 274 114. and. 235 040. File Data Transfer. 336 10A. 275 114. 277 018.326 10A. 201 115. 313 114. 2. 336 10B. 203 10A. 347 10A. adding failure reporting to the discrete word truth table (Section 2. Existing copies of Specification 429 may be updated by simply inserting the replacement white pages they replace. Revised label 130 035 from “Traffic Advisory Range” to “Intruder Range”. 342 10B. 133 10B. The AIM Data and File Data Transfer section headings were retained for reference purposes.3) and moving the description of status priorities to Section 2. 161 10A. 302 10B. 362 10B. 264 10A. Each change or addition is entitled by the section number and title currently employed in the Specification. The second part consists of replacement white pages for the Specification.7 were moved to Appendix 6. 360 10B. 220 116. 337 10B. 137 10B. 114 0BB.5 Sign/Status Matrix This section was revised and reorganized. 133 10A. B. 234 040. 236 039. 321 10A. the section header is retained and the original contents of this section are located in Appendix 6. 047 10A. 155 10A. 300 10B. 361 10B. 107 0BB. 271 10B. 222 116. 373 10A. 305 10A. 337 002. 160 10B. 262 114. 362 10A. 352 10B. 272 002.1. 155 10B. 335 10A. 263 10B. 350 10A. 134 10A. 263 10A. 265 114. 260 10A. The Sign Status Matrix (SSM) information is revised and reorganized. 304 10A. 331 10A. In addition. 264 114. 345 10A. 270 10A. 127 10A.3 Information Identifier This section contains editorial corrections to comply with changes introduced in Supplement 11. 303 10A. The previous AIM and character-oriented file transfer protocol sections are moved to Appendix 6. 351 10A. 160 10A. 275 10B. 375 TBD. 301 10A. 374 10A. 2. 361 10A. 161 10B. CHANGES TO SPECIFICATION INTRODUCED BY THIS SUPPLEMENT 429 2. 374 TBD.1 Digital Language The contents of Sections 2. For reference purposes. 272 10B. 321 10B. 157 10A. PURPOSE OF THIS SUPPLEMENT The Supplement introduces the Williamsburg bit-oriented file data transfer protocol which supports the transfer of binary and character data. 301 10B.1.1. 273 10A. 222 115.

277 018. 276 018. 272 018. VARIABLES OF BITAPPENDIX 6 – FORMER MAINTENANCE. ATTACHMENT 2 – DATA STANDARDS Add new Attachment. 16E. Discrete Data Standards entered for new labels: 272 002. 2 updated to reflect changes to Attachment 1. 350 114. ATTACHMENT 13 – PROTOCOL DETERMINATION PROCEDURE DIAGRAMS Add new Attachment. 350 115. 114. Binary Data notes 6.SUPPLEMENT 12 TO ARINC SPECIFICATION 429 – Page 3 Removed label 130 030 Traffic Advisory Range. 16C. 17A. 118. 15B. ATTACHMENT 11B – STATUS CODES Removed label 347 030 Sector Control. 273 018. 18E. 127. Tables 1. 128. 15A. 16A. 125. 013 0B8. 271 035. 119. 11A. ATTACHMENT 12A – FILED MAPPING EXAMPLE . 18B. Removed label 132 030 Traffic Advisory Bearing Estimate. Add format for TCAS Intruder Altitude label 131. 270 035. ATTACHMENT 11C – ALOHA/ALOHA RESPONSE PROTOCOL WORDS Add new Attachment. 17C. 271 018. Removed 730 ASAS Sector Control Word example. 18D. 117. 274 035. 129. ATTACHMENT 1 – EQUIPMENT CODES The following codes have been given new assignments: 113. 7 and 8 added. Removed 730 TCAS Traffic Advisory Altitude Word example. 270 115. 116. 275 035. Removed label 270 030 Transponder Discrete. Removed label 131 030 Traffic Advisory Altitude. Removed 730 TCAS Traffic Advisory Range Word example. 18A. 16B.115. AIM AND FILE TRANSFER TECHNIQUES Add new Appendix. APPENDIX 7 – MATHMATICAL EXAMPLE OF CRC ENCODING/DECODING Add new Appendix. ATTACHMENT 11A – DESTINATION CODES Add new Attachment. Removed 730 TCAS Traffic Advisory Bearing Estimate word example. 17B. 18F. ATTACHMENT 9B – GENERAL AVIATION WORD EXAMPLES Add new Company Name Identifier. ATTACHMENT 6 – GENERAL WORD FORMATS AND ENCODING EXAMPLES Add format for TCAS Intruder Range label 130. Add format for TCAS Intruder Bearing label 132. 15E. 353 114. ATTACHMENT 11 – BIT-ORIENTED DATA FILE TRANSFER WORD FORMATS Add new Attachment. 18C. ATTACHMENT 12 – FILE TRANSFER EXAMPLE Add new Attachment. 126. 274 018. 16D. 15C. 161 10A. Add new Attachment. ATTACHMENT 10 – ORIENTED PROTOCOL Add new Attachment. ATTACHMENT 15 – LINK LAYER CRC DATA EXAMPLE Add new Attachment. 124. 273 035. 352 114. Add format for Transponder Altitude/TCAS Own A/C Altitude label 203. Removed label 347 035 Antenna Control. 016 0B8. ATTACHEMENT 14 – SYSTEM ADDRESS LABELS Add new Attachment. 123. 161 10B. 351 114. 15D. 275 018.

INC. Maryland 21401 – 7645 USA SUPPLEMENT 13 TO ARINC SPECIFICATION 429 MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS) Published: December 30.AERONAUTICAL RADIO. 1991 Prepared by the Airlines Electronic Engineering Committee Adopted by the Airlines Electronic Engineering Committee: October 8. 2551 Riva Road Annapolis. 1991 .

This protocol supports the transfer of binary and character data. B. 2.5.5. 2. the word “valid” was added to clarify the Not clear to send condition.7 No Response to RTS The first paragraph of this section was updated to describe proper response to RTS. AEEC STAFF NOTE: THESE CHANGES APPLY TO ARINC 429.9 Unexpected RTS This section was updated to include editorial changes and a description of the correct responses to RTS.5. In addition. 2.4 Bit Rate and Word Timing Corrected the commentary to change the more ambiguous term “message” to LDU. 2. The second paragraph was updated to describe that and NCTS counter would be reset upon a valid CTS response.2. 2.1 and in conflict with other possible responses.5.6 and to clarify the validity requirements. the “note” designator was removed and the text clarified for the transfer of characters with a parity bit.5.SUPPLEMENT 13 TO ARINC SPECIFICATION 429 – Page 2 A.5 File Data Transfer An editorial change. The last sentence was added to clarify the resetting of RTS counters.6.2 Not Clear to Send (NCTS) The first paragraph was updated to include the information deleted from Section 2.1. and removed second paragraph from commentary.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. 2.11 Data The fourth paragraph of this section was updated to describe the proper ending of an LDU transmission.5.5 Bit-Oriented communications Protocol Included term “Williamsburg” parenthetically since this terminology well-known in industry.6. 2. correction to section numbering.6 Response to RTS The last sentence in the second paragraph was reworded and moved to a more appropriate section. C.3 Destination Code An editorial change was made. printed on goldenrod paper contains descriptions of changes introduced into this Specification by this Supplement.5. PURPOSE OF THIS SUPPLEMENT This Supplement introduces changes made to the Williamsburg protocol as a result of its initial implementation. since it is a requirement. . 2.5. In each case a brief description of the change or addition is included.5.2 Link Data Unit (LDU) Size and Word Count Added second paragraph to text.5. 2. and to include the optional NAK response for receipt of an incomplete octet. The last sentence in the third paragraph was deleted and it’s content expanded in the following commentary of that section. The second part consists of replacement white pages for the Specification.3. 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.1. The last sentence was deleted as redundant to Section in 2. Existing copies of ARINC Specification 429 may be updated by simply inserting the replacement white pages where necessary and destroying the pages they replace. 2. Corrected Network Layer definition. PART 3 ONLY.5. ORGANIZATION OF THIS SUPPLEMENT 2.11.6.13. D. The goldenrod pages are inserted inside the rear cover of the Specification. Added commentary to explain non-negotiation or parameters in this protocol.5. 2. this Supplement introduces new label assignments and equipment identification codes. 2. 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. 2.6.5.3 Character Data Words In the last paragraph.13 Negative Acknowledgement (NAK) This section was updated to clarify conditions for sending the NAK word.5.1 Clear to Send (CTS) The first part of this document.3. The modified and added material on each page is identified by a c-13 in the margins.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.5. modified to reflect the changes.5. 2. In the second to last sentence.

2.1 – ATTACHMENT 11C – ALOHA/ALOHA RESPONSE PROTOCOL WORD DEFINITION ATTACHMENT 10 – ORIENTED PROTOCOL VARIABLES OF BIT Tables 10-1 and 10-3 were updated to include events N5. 2.5.5. and the transmission order for the LDU Mapping of the 24-bit example was deleted to avoid possible misinterpretation.5.1 Duplicate LDU This section was added to describe duplicate LDU occurrences.15 SYN Word New text was added to describe SYN response times for non-consecutive LDU Sequence numbers.6 Time Out Errors This section was renumbered.13. 2.13.13. Bk was changed to B24 in the data word map. 2. Also.2 LDU Sequence Number Error The original text was omitted. “Note 2” was added to describe the GFI field of the ALOHA word. and is referenced by “note 1”.5 CRC Errors This section was updated to clarify the NAK response time for CRC errors. N6. incorrect text referring to the NAK response timing was deleted.19 ALO Response A new section was added and updated to describe ALO responses. 2.13.5. 2.5. 2. and semi-octet arrow lengths were shortened to correspond to the proper four and eightbit lengths. .5.13.13. 2.14. 2. “(X)” was corrected to “Q(x)”.5. Options 07 and 012 in Table 10-4 were changed to spares for consistency with corresponding text updates. 2.16 Response to ACK/NAK/SYN New text was added to describe actions when NAK and SYN are detected during a transmission.3 Parity Errors A commentary section was added to describe the procedures for receiving words with bad parity. “nibble” was changed to “semi-octet”. 2. and time T12.5. The last paragraph was incorrect and deleted.13.5.13.SUPPLEMENT 13 TO ARINC SPECIFICATION 429 – Page 3 2.5.2 Auto-Synchronized Files This section was added to describe the method of handling auto-synchronized files.5.4 Word Count Errors ATTACHMENT 12A – FIELD MAPPING EXAMPLE This section was updated to clarify the NAK response time for word count errors. Sections 2.7 were renumbered.13.1 Missing SOT word Text was corrected to refer to “reception” instead of “transmission” of a valid SOT word.5. 2.5. APPENDIX 7 – MATHEMATICAL EXAMPLE OF CRC ENDODING/DECODING Table 11C-3 was added to clarify protocol version number assignments. Format (alignment) changes were made in the polynomial divisions.5.5. 2.14 LDU Transfer Acknowledgement (ACK) Text was revised to include LDU conditions for sink acknowledgement transmission.14.7 Restart Initialization This section was omitted due to potential conflicts with the ALO/ALR procedures.

Maryland 21401 – 7645 USA SUPPLEMENT 14 TO ARINC SPECIFICATION 429 MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS) Published: January 4.Copyright 1993 by AERONAUTICAL RADIO. 2551 Riva Road Annapolis. INC. 1993 Prepared by the Airlines Electronic Engineering Committee Adopted by the Airlines Electronic Engineering Committee: November 4. 1992 .

2. 2.5.5.3 Word Count This section was renumbered.5.7 have been renumbered and reordered for consistency. to clarify the role of the link layer protocol for upward compatibility with changing network functionality. The title was changed for consistency.5.5. 2. 2. In each case a brief description of the change or addition is included. 2.4 Bit Rate and Word Timing A maximum word gap of 64 bit-times.3. printed on goldenrod paper. AEEC STAFF NOTE: THESE CHANGES APPLY TO ARINC 429. This protocol supports the transfer of binary and character data. Note: Sections 2. 2. 2. 2.6. B. contains descriptions of changes introduced into this Specification by this Supplement.3 Destination Busy This section was renumbered. 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.5.6.5.5.5.SUPPLEMENT 14 TO ARINC SPECIFICATION 429 – Page 2 A. 2. and an introductory replacement paragraph inserted to clarify the “optional” BUSY response.1. C.3. The goldenrod pages are inserted inside the rear cover of the Specification.7 Request to Send (RTS) This section was previously titled “Response to TS”. 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.7.6 Protocol Words This section was added to specifically define the word type for protocol words.2 Destination Code This section was updated.7. 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.10.5. and was moved to Section 2.5.7.5 Bit-Oriented Communication Protocol An editorial change references a new section number. 2. The requirement for Destination code validation is not a link layer function.1 Protocol Identifier This section was added to clarify the definition of bits 2825 for protocol words and to specify the relevant addition for error conditions. and an introductory paragraph added to clarify the basic RTS function. The modified and added material on each page is identified by a c-14 in the margins.19. modified to reflect the changes. 2.4 No Response to RTS This section was renumbered.5 File Data Transfer An editorial change was needed to reference new section. 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.10 Start of Transmission (SOT) 2. and has been renumbered.6.5. and commentary added to clarify the role of the GFI in pre-OSI as well as OSI environments.7.5.5 through 2.2 Not Clear to Send (NCTS) This section was renumbered. 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.5. GFI validation is not necessarily a link layer function. which may be used when a system cannot accept a transmission by the source in a “timely manner”. PART 3 ONLY. (averaged over the LDU transmission) was added to eliminate excessive delay in source transmission time.5. . Existing copies of ARINC 429 may be updated by simply inserting the replacement white pages where necessary and destroying the pages they replace. 2. New commentary equates a “timely manner” to the shorter retry sequence of the NCTS series.1 Clear to Send (CTS) This section was renumbered.1. 2.1 General Format Identifier (GFI) This section was updated.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. and a commentary added. 2. 2. and the ALOHA word was included in the logic for error determination.1 Bit-Oriented Protocol Determination This section was expanded to include determination of different version numbers of the bit-oriented protocol. ORGANIZATION OF THIS SUPPLEMENT The first part of this document. The second part consists of replacement white pages for the Specification.

5.11 Data All references to Character Data word formats were deleted. “BitOriented Communications Protocol”.1 Duplicate LDU This first paragraph was rewritten to clarify. The bit pattern (0100) for ISO 8473 was changed to a more Table 11-1A added “spares” for the deleted Character Data Formats and corrected “Protocol Data Word” to read “Protocol Word”. The Character Data Word format was removed from Supplement 14. and 2.5. 2.5.SUPPLEMENT 14 TO ARINC SPECIFICATION 429 – Page 3 2.19 ALO Response.5.19 Protocol Initialization 2. ATTACHMENT 1 – EQUIPMENT CODES New Equipment Code Identifiers were added. The text for equation: M9x) = x16G(x) + R(x) was corrected by moving the “bar” from G(x) to R(x). 2.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.1. 2. the action taken by the source upon receipt of a SYN word was updated.5. 2.5. Allows source to restart file with new FSN if necessary). ATTACHEMENT 6 – WORD ENCODING EXAMPLES Example added for label 171. ATTACHMENT 10 – ORIENTED PROTOCOL VARIABLES OF BIT 2. 2. The special character data format is not required.20 Bit Protocol Verification 2.5.5. changing the former GFI bit pattern (0001) for ISO 8208 to “unassigned”. both of which are no longer used.5. The format is the same as the revised Table 10-4. Also.11.3 Character Data Words This section was deleted. the maximum number of LDUs in a window (see Section 2. It ensures that a source device cannot “lock-up” a sink.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.5.2 ALOHA Response. Table 11-6A was revised. and added the LCW (LDU Control Word) format definition.16 Response to ACK/NAK/SYN The T16 timer was introduced to replace T10 and T8.14.12. The definition includes provision for a Link Control Word prior to each LDU. both binary and character data are transmitted in octets defined by the other two data word formats.5. It is based on Section 2. These values were established for timers and as response time design goals for incoming transmissions. 2.e. FORMATS AND Table 10-1 was updated to include a standard value for N7.5.19. Table 10-3 deleted Option 6 (O6) for NAK Send Time. 2.13 Negative Acknowledgement (NAK) NAK word interpretation was changed to remove constraint on source for specific order of file sequencing (i.6.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. . with expanded text as specified to allow for more efficient use of the 429 high (or low) speed data bus through “windowing”.5. and Table 11-4 updated definitions for bits 9 through 24 of the ALO and ALR words. 2.5.1 CRC Encoding References to character data words were deleted. These sections replace three sections from Supplement 13.5. Currently. Table 10-5 was added to include a definition of high speed maximum and minimum values for timers and response time design goals. ATTACHMENT 11 – BIT-ORIENTED DATA FILE TRANSFER WORD FORMATS Table 10-4 was revised to include columns for low speed maximum and minimum values.19. Table 10-6 was added to include notes to Tables 10-1 through 10-5.1 Bit-Oriented Protocol Version. 2. Timers T13 through T16 were added. 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 BitOriented protocol in Section 2. and deleted Option 9 (O9) for the Character Data Word. Timer T10 is not used in the high speed protocol.3. 2. which relaxes requirements to maintain a specific File Sequence ordering by the source. as the format is incompatible with those for Full and Partial Data word formats.15 SYN Word The LDU sequence anomalies which generate a SYN response by the sink were clarified.14.6 “Windowed Bit-Oriented Protocol”).5.19.1 Bit-Oriented Protocol Determination 2.

This information has been moved to Tables 11-4. ATTACHMENT 16 – SEQUENCE OF PROTOCOL AND DATA WORDS IN WINDOW TRANSFER This Attachment was added to illustrate the window transfers for new Section 2. and 11-4B. ATTACHMENT 11C – ALOHA/ALOHA RESPONSE PROTOCOL WORD DEFINITION This Attachment has been deleted.The “NOTES” in ATTACHMENT 11 have been renumbered to correspond to the new table definitions. .5.1.19.6. The bit pattern 1110 (hex”E”) is now defined as “ACARS VHF Format”. ATTACHMENT 14 – SYSTEM ADDERESS LABELS New System Address Labels (SAL) were added. 11-4A. ATTACHMENT 17 – FLOW DIAGRAM USED TO DETERMINE CHARACTER-ORIENTED VS BITORIENTED PROTOCOL This Attachment was added to illustrate the logic flow that determines whether a character-oriented or bitoriented link layer protocol interface is to be used.SUPPLEMENT 14 TO ARINC SPECIFICATION 429 – Page 4 ATTACHMENT 11 – BIT-ORIENTED DATA FILE TRANSFER WORD FORMATS (cont’d) generic ISO 9577 definition.1. ATTACHMENT 13A – ALOHA DETERMINATION SEQUENCE VERSION This Attachment was added to support the ALOHA version determination sequence called out in Section 2.

2551 Riva Road Annapolis. INC. 1995 Prepared by the Airlines Electronic Engineering Committee Adopted by the Airlines Electronic Engineering Committee: April 18.Copyright 1995 by AERONAUTICAL RADIO. Maryland 21401 – 7645 USA SUPPLEMENT 15 TO ARINC SPECIFICATION 429 MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS) Published: September 1. 1995 .

which will cause improper LRU/system operation.16.2.2. 0E0. For these applications.2 Modulation The following Commentary was added: “Avionics manufacturers are warned that bus activity monitoring should be implemented with caution. modified to reflect the changes. DISCRETE DATA WORDS Meaning Bit 0 0 1 1 30 0 1 0 1 Verified Data.SUPPLEMENT 15 TO ARINC SPECIFICATION 429 .4. 13B ATTACHMENT 2 .LABEL CODES This attachment was updated according to the tables on the following pages.Page 2 A.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.1. may not necessarily be detected by a “simple” bus activity monitor.1. In each case a brief description of the change or addition is included. AUTOTUNE was assigned for “1” and NO AUTOTUNE was assigned to “0”.23 changed to “0” and bits 15. 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. 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. Designation for label 155 027 changed from BCD to BNR.1 Radio Systems Management Word Formats VHF Com Frequency Word . Figure 3. 2. Word 155 027 moved from Table 1 to Table 2. 160. The second part consists of replacement white pages for the Specification.8. C. Three methods are defined.5. B. 12C. 19F. In Table 2 under label 077. PURPOSE OF THIS DOCUMENT This Supplement introduces new label assignments. 05A. This is the preferred method. “0--” was changed to “037”. system address labels and updates to the 429W protocol. 053.DATA STANDARDS This attachment was updated according to the tables on the following pages. ORGANIZATION OF THIS SUPPLEMENT The first part of this document. bit 12 was changed from “pad” to “Tune”.Bits 7.20. .28 changed to “1”. ATTACHMENT 1 . 0D0. Nomal Operation No Computed Data Functional Test Failure Warning 2. Existing copies of ARINC Specification 429 may be updated by simply inserting the replacement white pages where necessary and destroying the pages they replace. 2. ATTACHMENT 1 . refer to the associated ARINC equipment characteristic to determine the proper SSM reporting.5.3 Discrete Data Words The technique for encoding SSM bits in discrete words were revised. In Table 2 “SIG DIG” was changed to “SIG BIT”. Duplicate 244 08D word removed. When using the second method. 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. Newly assigned discrete word formats are included. printed on goldenrod paper contains descriptions of changes introduced into this Specification by this Supplement. In word 270 115.” 2. When the “Functional Test” code appears as a system output. 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. 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. ORIGINAL TEXT FOLLOWS: 2.21. 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. The modified and added material on each page is identified by a c-15 in the margins. equipment IDs.0 Digital Information Transfer System Standards Numerous changes were made to the protocol throughout this Section. Crossed wiring (interchanging A and B) at one end of the bus.LABEL CODES The following new equipment codes were assigned: 03D. The goldenrod pages are inserted inside the rear cover of the Specification. Words containing the “Failure Warning” code should continue to be supplied to the data bus during the failure condition.2 Receiver Input Impedance The word “parallel” was changed to “combination”.

BIT-ORIENTED DATA FILE TRANSFER WORD FORMATS Table 11-6A GENERAL FORMAT IDENTIFIER (GFI) Revised “Reserved ISO 9577” to “ISO 9577” ATTACHMENT 11A . Word format for label 077 00B removed (from two places). Manufacturer Specific Data Word 010101 assigned to Garmin 010110 assigned to ARNAV Systems Bit 11 modified for label 150 to include reference to precision source.Page 3 ATTACHMENT 6 .Revised Time T10 min and max values.DESTINATION CODES Added Cabin Packet Data Function.examples for Flight Director Pitch and Total Air Temp corrected.STATUS CODES Revised description of Code 86. Table 10-3 BIT-ORIENTED PROTOCOL OPTIONS Added Option 012 Table 10-5 VARIABLES OF HIGH SPEED BITORIENTED PROTOCOL .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 . ATTACHMENT 9B . ATTACHMENT 14 .SUPPLEMENT 15 TO ARINC SPECIFICATION 429 .VARIABLES OF BIT-ORIENTED PROTOCOL Revised Notes 1 and 4. Examples for the following tables added. Added entries for Code 8E through 95. Station bit encoding. Corrected Ground APPENDIX 8 .INTEROPERABILITY OF BITORIENTED LINK LAYER PROTOCOL Appendix added. ATTACHMENT 11B .SDL DIAGRAMS OF THE WILLIAMSBURG PROTOCOL Appendix added.GENERAL WORD FORMATS AND ENCODING EXAMPLES Table 2 . APPENDIX 9 . ATTACHMENT 11 .GENERAL AVIATION WORD EXAMPLES Manufacturer Specific Data Word 010101 assigned to Garmin 010110 assigned to ARNAV Systems ATTACHMENT 10 .

SOFTWARE PART NO.01 0.180 12 0.84 131.180 12 14 0.05 0.015 150 150 250 250 .1. Discrete Data #3 Discrete Data #4 Discrete Status 8 EFIS Zero Fuel Weight (kg) Zero Fuel Weight (lb) Longitudinal C/G Lateral C/G Long. 6 See Att.4 180 220 11 Deg 4096 4096 125 125 250 250 See Att. 6 See Att. 6 See Att. 6 See Att. Zero Fuel C/G BINARY UNITS RANGE SIG RESOL MIN TI MAX TI REF 10 10 10 8 34 10 10 10 10 31 31 31 31 31 31 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 15 15 14 14 15 15 15 31 31 31 See Att. 6 See Att. 6 See Att. S/G HARDWARE PART NO. Selected Heading Pitch Limit Discrete Status 2 EFIS Discrete Status 3 EFIS Discrete Status 4 EFIS Discrete Status 5 EFIS Discrete Status 6 EFIS Discrete Status 7 EFIS ADF brg left/right OP. 6 kg lb %MAC %MAC 655360 1310720 163.05 125 250 SDI-01 = left / SDI-10 = right See Att.84 15 15 17 14 20 40 0.072 163. Fuel Temp (non-conflicting) ACMS Information ACMS Information ACMS Information ACMS Information Min Buffet Airspeed Flight information g Magnetic Heading g Mach Mach VOR/ILS Frequency DME Frequency S/G HARDWARE PART NO.01 125 125 250 250 Deg/180 + .01 100 100 100 100 200 200 200 200 Mach EPR Limit N1 Limit %RPM 4096 4 256 12 14 0. 6 Deg/180 Deg/180 + . 6 NOTES See Section 3. 6 See At. 6 See Att.Page 4 PARAMETER ACMS Information ACMS Information ACMS Information TACAN Control Min Op. 6 See Att.001 0.180 + .NEW AND REVISED BNR LABEL ASSIGNMENTS LABEL EQ ID New New New New Add New New New New Revise Revise Revise Revise Revise Revise Revise New New New New New New New New New New New New New New New New New New New Correction New New DELETE DELETE DELETE Revise Revise Revise 061 062 063 145 226 233 234 235 236 265 360 370 014 370 205 205 034 035 060 061 101 121 145 146 147 155 160 161 162 207 272 273 276 054 074 076 077 107 256 257 347 205 342 342 002 002 002 002 002 002 002 002 002 002 002 004 005 005 006 01A 025 025 025 025 025 025 025 025 025 025 025 025 025 025 025 025 025 037 037 037 037 037 037 037 037 038 038 038 SUPPLEMENT 15 TO ARINC SPECIFICATION 429 .

01 0. 2 See Att.35 327. B Bit 11-Chan.01 0.Page 5 15 15 16 16 16 16 16 16 16 16 16 16 16 16 16 16 15 13 15 14 13 16 16 8 1 0.01 0.L TANK 13-14 T/U CAP .L TANK 9-12 T/U CAP .01 0. 2 See Att.12 5.181 (1) (1) See Att. 2 See Att.35 655.01 0.01 0. 6 for SDI encoding See Att.01 0.35 655.35 655. 6 SUPPLEMENT 15 TO ARINC SPECIFICATION 429 .01 1 1 100 TBD TBD TBD TBD 500 500 500 TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD 50 100 100 TBD TBD TBD TBD 1024 1000 1000 TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD 100 200 200 Lbs Gallons PF PF PF PF PF PF PF PF PF PF PF PF PF PF PF LB/GAL GALS LBS LB/GAL See Att.R TANK 9-12 T/U CAP .01 0.35 655. 6 for SDI encoding PF 65535 16 1 See Att.12 +-180 +-180 204700 9 9 9 9 9 9 11 0.01 0.35 655.35 655.12 5.67 8. B Bit 11-Chan.35 655.01 0.A TANK 1-4 T/U CAP . A/Bit 12-Chan. B Bit 11-Chan. B Scalar Scalar Scalar Scalar Deg. A/Bit 12-Chan.35 655.001 N/A N/A See Att.C TANK 1-4 T/U CAP .01 0.01 0.C TANK 5-8 T/U CAP . Deg.01 0.C TANK 9 T/U CAP .NEW AND REVISED BNR LABEL ASSIGNMENTS LABEL EQ ID New New New New New New New New New New New New New New New New New New New New New New New New New New New New New New New New New New New New New New New New New New New 227 270 350 353 354 355 356 357 360 361 025 156 157 160 161 241 254 255 256 262 263 264 265 266 267 270 271 272 273 274 275 276 277 310 320 324 326 327 341 342 344 345 346 03D 03D 03D 03D 03D 03D 03D 03D 03D 03D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D 04D PARAMETER AVM Command Discrete Data #1 Maintenance Data #1 Maintenance Data #4 N1 Vibration N2 Vibration N3 Vibration BB Vibration N1 Rotor Imbalance Angle LPT Rotor Imbalance Angle (737 only) Load SEL Control L TANK FAULTS R TANK FAULTS C TANK FAULTS A TANK FAULTS FQIS SYSTEM DATA Actual Fuel Quan (teat) Fuel Quantity (gal) FUEL DISCRETES T/U CAP-L TANK 1-4 T/U CAP-L TANK 5-8 T/U CAP . A/Bit 12-Chan.35 655.01 0. 2 See Att. 2 See Att. 2 See Att. B Bit 11-Chan.12 5. 6 for SDI encoding See Att.A TANK 5-8 T/U CAP -A TANK 9-11 T/U CAP . 2 See Att. 2 See Att.01 0. 2 Bit 11-Chan. na 5.35 655. 6 for SDI encoding .001 1 100 0.35 655.R TANK 1-4 T/U CAP .R TANK 5-8 T/U CAP . 2 See Att.R TANK 13-14 COMP CAP-TANK DENSITY-TANK TANK VSO QUANTITY UPLIFT QUANTITY UPLIFT DENSITY I/O S/W REV 1&2 S/W REV-TANK FUEL DISCRETES DISCRETES STATUS 1&3 CABLE CAP-HI-Z BINARY UNITS RANGE SIG RESOL MIN TI MAX TI REF 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 9 46 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 NOTES See Att.01 0.35 655. A/Bit 12-Chan. 6 for SDI encoding See Att.191 32767 1638300 8.01 0.35 655. 6 262144 32768 655.01 0. 2 See Att. A/Bit 12-Chan.

C Deg. Att. DATA FQIS 2-3 LB/KG Control Word Fuel Temperature . For SPARTIAAL Internal Para. DATA FQIS 1-3 MAINT.Set to Zero Fuel Temp. For SPARTIAAL Internal Para. DATA FQIS 1&3 MAINT. For SPARTIAAL Internal Para. 2 See Att.25 40 40 4 4 4 4 4 100 100 100 100 100 100 100 100 100 100 100 100 100 100 Zero for A-321 Zero for A-321 lb lb 131072 131072 15 15 4 4 100 100 200 200 Deg. For SPARTIAAL Internal Para.25 0.01 0. 2 See Att. For SPARTIAAL Internal Para.25 0. For SPARTIAAL Internal Para. 2 See Att. For SPARTIAAL Internal Para. Right Wing Tank Fuel Temperature . For SPARTIAAL Internal Para. Left Wing Tank Fuel Temp. For SPARTIAAL Internal Para./180 +-180 +-180 32768 14 14 0.NEW AND REVISED BNR LABEL ASSIGNMENTS LABEL New New New New New New New New Revise Revise Delete Revise Revise New New New New New New New New New New New New New New New New New New New New New New New New New New New New New Revise 350 351 352 353 354 355 357 151 176 177 200 201 202 247 250 256 257 260 261 262 270 271 276 300 301 302 303 304 305 306 307 310 311 312 313 314 315 316 317 324 325 356 244 SUPPLEMENT 15 TO ARINC SPECIFICATION 429 .25 0. 2 See Att. For SPARTIAAL Effective Pitch Angle Effective Roll Angle Maintenance Word Fuel Flow Rate BINARY UNITS RANGE SIG RESOL MIN TI 100 100 100 100 100 100 100 MAX TI 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 REF 5 5 5 5 5 5 5 17 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 31 NOTES See Att. 2 See Att. DATA FQIS 1-4 MAINT.01 .Page 6 EQ ID 04D 04D 04D 04D 04D 04D 04D 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 08D PARAMETER MAINT. For SPARTIAAL Internal Para. C Deg. 2 See Att.Right Outer Cell Discrete Data #1 Discrete Data #2 Discrete Data #7 Internal Para. DATA FQIS 1-4 FQIS TANK ID MAINT. 2 Deg. C lb lb lb lb lb lb lb 512 512 512 512 655360 655360 131072 131072 131072 131072 131072 11 11 11 11 14 14 15 15 15 15 15 0.Set to Zero Total Fuel Preselected Fuel Quantity Fuel Quantity .Left Outer Cell Fuel Quantity Left W/T Tank Fuel Quantity Center Tank Fuel Quantity Right I/C or W/T Tank Fuel Quantity . 6 for SDI See Att. For SPARTIAAL Fuel Quantity ACT 1 Fuel Quantity ACT 2 Internal Para. For SPARTIAAL Internal Para. For SPARTIAAL Internal Para. DATA FQIS 2-4 MAINT. C Deg./180 Deg. 2.

NEW AND REVISED BNR LABEL ASSIGNMENTS LABEL EQ ID New New New New New New New New New New New New New New New New New New Revise New New New Revise New New New New New New New New New New New New New New New New New New New New 155 156 157 160 276 354 005 006 073 173 174 316 317 344 345 346 347 353 360 146 222 101 270 221 222 223 224 225 114 130 131 134 254 255 264 340 341 344 345 346 347 364 365 0BB 0BB 0BB 0BB 0BB 0BB 0D0 0D0 0D0 0d0 0D0 0D0 0D0 0D0 0D0 0D0 0D0 0D0 10A 112 112 114 115 12C 12C 12C 12C 12C 13A 13A 13A 13A 13A 13A 13A 13A 13A 13A 13A 13A 13A 13A 13A PARAMETER Maintenance Data #6 Maintenance Data #7 Maintenance Data #8 Maintenance Data #9 Discrete Data #5 Maintenance Data #5 Engine Discrete Engine Discrete Engine Oil Quantity Hydraulic Oil Quantity Hydraulic Oil Pressure Engine Oil Temperature Engine Oil Pressure N2 EGT N1 Fuel Flow Vibration Throttle Rate of Change TACAN Control TACAN Control C/G Target Stored TACAN Control Word Indicated Angle of Attack (Ave.01 0.25 0.03 0.02 180 180 100 25 31.05 0.5 62.5 0.5 62.015 0.015 2 0.5 200 200 200 50 200 200 200 50 50 50 50 50 100 200 200 SUPPLEMENT 15 TO ARINC SPECIFICATION 429 -Page 7 0.05 0. C %RPM Lb/Hr Scalar See Section 3.0625 0. A/Bit 12-Chan.002 0.015 0.015 0.004 0.05 0. C PSI %RPM Deg.5 0.05 0.5 62.3 31. B SDI1 = L/SD12 = R SDI1 = L/SD12 = B SDI1 = A/SD12 = B SDI1 = L/SD12 = R SDI1 = L/SD12 = R SDI1 = L/SD12 = R SDI1 = L/SD12 = R SDI1 = L/SD12 = R SDI1 = L/SD12 = R SDI1 = L/SD12 = R US Pint US Pint PSI Deg.05 0.3 31.1.015 0.25 0.) Indicated Angle of Attack (#1 left) Indicated Angle of Attack (#1 right) Indicated Angle of Attack (#2 left) Indicated Angle of Attack (#2 right) Ambient Pressure Inlet Temperature Inlet Pressure Throttle Lever Angle N1 Cruise N1 Climb Burner Pressure N1 Take Off N1 Reference N2 Speed EGT Trimmed N1 Speed Actual Fuel Flow N1 APR Rating N1 Max Reverse BINARY UNITS RANGE SIG RESOL MIN TI MAX TI REF 44 44 44 3 3 44 5 5 5 5 5 5 5 5 5 5 5 5 31 8 8 40 42 45 45 45 45 45 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 NOTES Bit 11-Chan.015 0.05 0.4 Deg/180 % Deg/180 Deg/180 Deg/180 Deg/180 Deg/180 PSIA Deg.3 31.5 62.03 8 0.12 16 +-180 164 +-180 +-180 +-180 +-180 +-180 32 128 32 +-180 256 256 512 256 256 256 2048 256 32768 256 256 9 9 12 12 14 13 12 13 12 8 9/9 12 8 12 12 12 12 12 14 11 13 12 14 14 14 14 14 14 12 14 14 14 14 0.015 0. 2 .25 1 0.3 100 100 100 25 100 100 100 25 25 25 25 25 50 100 100 220 220 200 50 62. C %N1 Nom Lb/Hr %N1 Nom %N1 Nom 128 128 4096 2048 4096 256 2048 256 32768 5.5 0.3 31. C PSIA Deg/180 %N1 Nom %N1 Nom PSIA %N1 Nom %N1 Nom %RPM Deg.031 0.05 0.015 See Att.

Display Left Wing Fuel Quan.1 0. 0-3 0-359 0-6000 0-3 4 3 4 4 0.05 0. 6 See Att.00 0-79999 0-79999 0-79999 0-79999 0-79999 0-79999 0-79999 0-79999 0-9999 0-9999 0-9999 0-9999 0-9999 0-9999 0-9999 0-9999 0-9999 0-100 0-100 0-100 0-3 0-399. 3 Degrees Lbs KG %MAC Lbs Lbs Lbs Lbs KG KG KG KG KG/LB KG/LB KG/LB KG/LB KG/LB KG/LB KG/LB LG/LB KG/M3 pF pF pF See Chap./180 Deg. Display Preselected Fuel Quan. Zero Fuel CG QTY-LD SEL (LB) QTY . Display Center Wing Fuel Quan.SUPPLEMENT 15 TO ARINC SPECIFICATION 429 . Display Fuel Density Sensor Values Left Wing Tank Sensor Values Center Wing Tank Sensor Values Right Wing Tank VHF Com Frequency Selected EPR 112 TACAN Distance EPR Degrees Ft/Min EPR See Chap.001 0.M. 3 See Chap. Display ACT 2 Fuel Quan. Display Right Wing Fuel Quan./180 RANGE +-180 +-180 SIG 12 12 RESOL 0.001 100 167 100 100 100 100 100 100 100 100 200 333 200 200 200 200 200 200 200 200 14 14 13 42 16 See Att.05 MIN TI 100 100 100 MAX TI 200 200 200 REF NOTES IGV Position IGV Request Tank Unit Data TACAN Control Word Manu.1 0. 6 43 See ARINC 743A See ARINC 743A 31 7 31 31 51 51 51 15 15 15 5 5 5 5 5 5 5 5 19 19 19 19 19 19 19 19 19 19 19 19 51 31 8 0-19999 0-19999 0-19999 0-100.Page 8 NEW AND REVISED BNR LABEL ASSIGNMENTS LABEL EQ ID New New New New Correction New New New New Revised New Revised Revised New New Revised Revised New New New New New New New New New New New New New New New New New New New New New New New New Revised New 366 367 341 147 171 214 316 375 376 021 027 020 021 047 047 155 065 163 243 52 012 013 017 020 022 023 027 030 135 136 137 140 141 142 143 144 272 273 274 275 047 021 201 13A 13A 160 xxx xxx xxx xxx xxx xxx 002 002 020 020 020 024 027 037 037 037 037 04D 04D 04D 04D 04D 04D 04D 04D 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 05A 086 0A1 PARAMETER BINARY UNITS Deg.FLT DECK (LB) TOTAL-FLT DECK (LB) TNK-LD SEL(LB) QTY-LD SEL (KG) QTY-FLT DECK (KG) TOTAL-FLT DECK (KG) TNK-LD SEL(KG) ACT 1 Fuel Quan.1 0. 3 EPR N. Display Center+ACT+ACT FQ Display Actual Fuel Quan.001 1 1 0.01 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 0.99 5 5 5 19 19 19 19 19 19 19 19 16 16 16 16 16 16 16 16 16 13 13 13 4 5 1 1 0. Specific Status Word ICAO Aircraft Address (part 1) ICAO Aircraft Address (part 2) GPS Differential Correction Word A GPS Differential Correction Word B Selected EPR TACAN Selected Course Selected Vertical Speed Selected EPR VHF Com Frequency VHF Com Frequency MLS Selected GP Angle Gross Weight Zero Fuel Weight (lb) Zero Fuel Weight (kg) Long.01 100 100 100 100 100 100 100 100 100 100 100 100 100 100 190 200 200 200 200 200 200 200 200 200 200 200 200 200 200 210 .0001 0.

AERONAUTICAL RADIO. INC. 2551 Riva Road Annapolis. 2001 Prepared by the Airlines Electronic Engineering Committee Adopted by the Airlines Electronic Engineering Committee: November 14. 2000 . Maryland 21401 – 7645 USA SUPPLEMENT 16 TO ARINC SPECIFICATION 429 MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS) Published: September 27.

DATA STANDARDS Attachment 2 was updated to reflect new data standards. . Communications Management Unit. In each case a brief description of the change or addition is included.OUTPUT SIGNAL TIMING TOLERANCES The text was modified to define pulse rise and fall times. The text describing Label 214 and Label 216 was revised to reflect the contents of ARINC Characteristic 758. A summary of label codes added by Supplement 16 is reproduced as Attachment 1-16 to 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. PURPOSE OF THIS SUPPLEMENT This Supplement introduces new label assignments. ATTACHMENT 1-2 . The deleted labels are: Label PARAMETER Code 053 Track Angle Magnetic 217 Average Static Pressure 231 Total Air Temperature REF ATT 36 36 167 Air Traffic Service Unit (Airbus) Integrated Standby Instrument System (A340/330.GENERAL WORD FORMATS AND ENCODING EXAMPLES The text describing Label 150 bit 11 was revised to reflect the contents of ARINC Characteristic 743A. ATTACHMENT 4 .INPUT/OUTPUT CIRCUIT STANDARDS Text was added to identify the drawing as defining total system characteristics.Page 2 A. ORGANIZATION OF THIS SUPPLEMENT The material in Supplement 16 is integrated into ARINC Specification 429 to form an updated version of the standard.LABEL CODES Attachment 1-1 was updated to include new label assignments. 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. of these new assignments 35 labels were revised and 3 label assignment deletions.SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1 . and System Address Labels (SAL) to ARINC Specification 429. GNSS Sensor. ATTACHMENT 1-1 . Changes introduced by Supplement 16 are identified using change bars and are labeled by a “c-16” symbol in the margin. C. B. The basis of the changes introduced in Supplement 16 are reproduced as Attachment 1-16 to this Supplement. equipment IDs. 168 A320/319/321) 169 Data Link Control and Display Unit (A340/330) 200 Versatile Integrated Avionics Unit (B717/MD-10) 201 Electronic Spoiler Control Unit (B717) 202 Brake Control Unit (B717) 203 Pneumatic Overheat Detection Unit (B717) 204 Proximity Switch Electronics Unit (B717) 205 APU Electronic Control Unit (B717) 206 Aircraft Interface Unit (MD-10) 207 Fuel Quantity Gauging Unit (MD-10) 25 20 20 7 7 7 7 7 7 7 7 ATTACHMENT 2 .EQUIPMENT CODES Attachment 1-2 was updated to include new equipment codes: EQ ID 055 056 057 058 060 061 0BB 108 109 122 12D 12E 12F 13B 13F 130 140 142 143 EQUIPMENT TYPE Multi-Mode Receiver (MMR) (755) GNSS Navigation Landing Unit (GNLU) (756) Cockpit Voice Recorder (CVR) (757) Communication Management Unit Mark 2 (758) GNSS Navigation Unit (GNU) (760) Satellite Terminal Unit (STU) (761) Flap Control Unit (B747-400)/Flap Slat Electronics Unit (B767-400) Electronic Engine Control (EEC) Channel A (B737-700) Electronic Engine Control (EEC) Channel B (B737-700) Ground Auxiliary Power Unit (A320/319/321) Logic Drive Control Computer (B747/B767) Cargo Control Logic Unit (B767) Cargo Electronics Interface Unit (B767) Audio Entertainment System (AES) Controller (Boeing) Camera Interface Unit (A340/B777) Load Management Unit (LMU) Airbus Supersonic Air Data Computer (Honeywell) ADS-B Link Display Processor Unit (LPDU) Vertical/Horizontal Gyro (Litton) REF ATT 33 3 24 34 33 11 23 10 10 20 1 1 1 16 25 21 17 27 22 ATTACHMENT 8 . ATTACHMENT 6 .

SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1 . 172.400 Cabin Service System (CSS) 747-400 Audio Entertainment System (AES) Boeing Multicast Bridge REF ATT 24 44 44 44 26 5 5 5 5 19 2 5 5 5 5 5 5 9 9 18 18 13 28 45 8 12 12 15 15 16 43 43 APPENDIX E – ASSIGNMENTS GUIDELINES FOR LABEL Labels 171.SYSTEM ADDRESS LABELS The following System Address Labels were added: SAL OCTAL LABEL 157 210 211 212 225 241 242 244 245 246 251 252 253 310 311 312 313 314 315 316 321 322 323 324 325 326 327 330 331 332 362 363 364 366 367 SYSTEM CVR FCMC Com A340-500/600 FCMC Mon A340-500/600 FCMC Int A340-500/600 HUD APM-MMR MMR ILS MLS AHRS VDR #1 VDR #2 VDR #3 GPWS GNLU 1 GNLU 2 GNLU 3 GNU 1 GNU 2 GNU 3 AUTOTHROTTLE COMPUTER FCC 1 FCC 2 FCC 3 APU APU CONTROLLER Mode Control Panel (MCP) FMC 3 ATC TRANSPONDER DADC Passenger Services System (PSS) 767300. . 214 and 216 were removed from spare labels (item 3).Page 3 ATTACHMENT 11 .

125 200 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 100 100 100 100 100 37 37 37 37 37 ATTACHMENT 1-16 SUPPLEMENT 16 UPDATES TO LABEL CODES MHz Deg/Sec2 Deg/Sec2 Degree Deg/Sec2 Deg/Sec2 Deg/Sec2 Deg/Sec2 117 Hz 117 Hz 500 117 Hz 117 Hz 117 Hz 117 Hz Meters 1200 Meters 1200 .1 90 90 90 90 90 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 1008-135.002 50 Hz ± 64 15 0.002 50 Hz The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 ±268435456 20 256 200 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 256 11 0.002 50 Hz ± 64 15 0.9 4 0.SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1– Page 4 Code No.05 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 500-600 3 1 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 ± 64 15 0.9 4 0. ID (Hex) 056 060 056 060 056 060 055 06D 06D 06D 06D 06D 056 060 055 056 060 056 060 055 056 060 055 056 060 056 060 056 060 056 060 004 038 004 004 038 004 038 056 060 00B 056 060 00B 056 060 Parameter Distance To Go Distance To Go Time To Go Time To Go Ground Speed Ground Speed Selected Runway Heading Landing Gear Position Infor & System Status Landing Gear Position Infor & System Status Landing Gear Position Infor & System Status Landing Gear Position Infor & System Status Landing Gear Position Infor & System Status TACAN Selected Course TACAN Selected Course (Bcd) Landing System Mode/Frequency ILS Frequency ILS Frequency VOR/ILS Frequency VOR/ILS Frequency #1 Paired DME Frequency DME Frequency DME Frequency #1 MLS Channel Selection MLS Frequency Channel MLS Frequency/Channel Set Latitude Set Latitude Set Longitude Set Longitude Set Magnetic Heading Set Magnetic Heading Body Pitch Accel Body Pitch Accel Track Angle Magnetic Body Roll Accel Body Roll Accel Body Yaw Accel Body Yaw Accel ETA (Active Waypoint) ETA (Active Waypoint) Pseudo Range ACMS Information ACMS Information Pseudo Range Fine ACMS Information ACMS Information Units Range Sig Bits Resolution MIN TX MAX TX REF ATT 001 001 002 002 012 012 017 020 021 022 023 024 027 027 033 033 033 034 034 035 035 035 036 036 036 041 041 042 042 043 043 052 052 053 053 053 054 054 056 056 061 061 061 062 062 062 Degrees The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 0-359.002 50 Hz ± 64 15 0.002 50 Hz ± 64 15 0.002 50 Hz 1 3 1 250 ± 64 15 0. (Octal) Data BCD BCD BCD BCD BCD BCD BCD Discrete Discrete Discrete Discrete Discrete BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BCD BNR BNR BCD BNR BNR BNR BNR BCD BCD BNR BNR BNR BNR BNR BNR Eqpt.

83% 14 0.83% 15 20 14 40 0.031 200 1024 15 0.Page 5 Percent N/A N/A Degrees Degrees Degrees Degrees Knots The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 163.0 20 9.000172° 200 ±108° 20 0. ID (Hex) 00B 056 060 00B 00B 00B 00B 056 060 00B 00B 00B 00B 056 060 114 008 114 00B 008 114 008 056 060 114 056 060 00B 00B 056 060 00B 056 060 056 060 055 056 060 060 056 056 060 00B 00B 00B 056 Parameter Range Rate ACMS Information ACMS Information Delta Range SV Position X SV Position X Fine SV Position Y Reference Airspeed (Vref) Reference Airspeed (Vref) SV Position Y Fine SV Position Z SV Position Z Fine UTC Measure Time Zero Fuel Weight Zero Fuel Weight Zero Fuel Weight Maximum Hazard Alert Level Output Aircraft Gross Weight GNSS Altitude (Msl) Hazard Azimuth Output Aircraft Longitudinal Center Of Gravity Hazard Range Output Target Airspeed Target Airspeed Zero Fuel Center Of Gravity Selected Course #1 Selected Course #1 HDOP VDOP Selected Altitude Selected Altitude GNSS Track Angle Selected Airspeed Selected Airspeed Selected Vertical Speed Selected Vertical Speed Selected Runway Heading Selected Runway Heading Selected Runway Heading Selected Mach Selected Mach Selected Cruise Altitude Selected Cruise Altitude GNSS Latitude GNSS Longitude GNSS Ground Speed Desired Track Units M/S Range Sig Bits Resolution MIN TX MAX TX 1200 REF ATT Meters Meters Meters Meters Meters Meters Meters Seconds Pounds Pounds Feet Percent ±4096 20 0.0039 200 ±67108864 20 64 200 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 64 14 0.0039 200 ±67108864 20 64 200 64 14 0.0055° 200 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 ± 180 11 0.0039 200 10.125 200 The Same Parameters as the FMS EQ ID 002 200 37 1200 1200 1200 1200 1200 1200 .536743µs 200 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 1310680 15 40 100 1310680 ±131072 163.125 0.031 200 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 ±108° 15 0. (Octal) 063 063 063 064 065 066 070 070 070 071 072 073 074 074 074 074 075 075 076 076 076 077 077 077 077 100 100 101 102 102 102 103 103 103 104 104 105 105 105 106 106 107 107 110 111 112 114 Data BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR Discrete BNR BNR Discrete BNR Discrete BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR Eqpt.0039 200 ±67108864 20 64 200 64 14 0.Code No.0039 200 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 ±4096 20 0.01% 100 200 100 1200 1200 1200 1200 1200 1200 1200 1200 ATTACHMENT 1-16 SUPPLEMENT 16 UPDATES TO LABEL CODES 400 200 1200 200 37 37 37 SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1.1 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 ±108° 20 0.01% 100 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 1024 15 0.000172° 200 4096 15 0.

Page 6 Code No.5 1 20 0.9536743µs 100 100 32 32 100 100 32 32 ATTACHMENT 1-16 SUPPLEMENT 16 UPDATES TO LABEL CODES 1200 1200 1200 1200 200 1200 1200 1200 200 1200 1200 36 37 10 0.125 200 32.2E-4 200 32. ID (Hex) 060 056 060 00B 055 056 060 00B 055 056 060 00B 056 060 00B 056 060 056 060 00B 00B 002 056 060 056 060 00B 00B 00B 140 00B 114 00B 114 114 114 114 114 114 114 00B 056 060 114 055 056 Parameter Desired Track Waypoint Bearing Waypoint Bearing Horizontal GLS Deviation Rectilinear Horizontal GLS Deviation Rectilinear Cross Track Distance Cross Track Distance Vertical GLS Deviation Rectilinear Vertical GLS Deviation Rectilinear Vertical Deviation Vertical Deviation GNSS Latitude Fine Range to Altitude Range To Altitude GNSS Longitude Fine Horizontal Command Signal Horizontal Command Signal Vertical Command Signal Vertical Command Signal Digital Time Mark UTC Universal Coordinate Time Universal Coordinated Time (UTC) Universal Coordinated Time (UTC) Vertical Deviation (Wide) Vertical Deviation (Wide) Aut Horiz Integ Limit Aut Vert Integ Limit Vertical Figure Of Merit Flap Angle UTC Fine Pump Contactor States UTC Fine Fractions Pump Contactor and Pushbutton States Pump Push Button and LP Switch State Pump LP Switch State and FCMC Commands Valve Feedback Valve Feedback Valve Feedback Valve Feedback UTC Universal Coordinated Time Universal Coordinated Time FCMC Valve Commands MLS AZ Deviation Localizer Bearing (True) Units Range Sig Bits Resolution MIN TX MAX TX REF ATT Feet Feet Feet Feet Degrees Degrees Hr:Min Hr-Min NM Feet Feet Degrees Seconds Seconds The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 ± 24000 18 .9 4 0. 768 18 0.0625 ± 1024 14 .1 100 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 16 17 1.38-E-8° 200 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 200 23:59.05 62.000172° 11 8. 768 18 0.1 Min 200 0-23.0 sec 200 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 ± 2400 15 0.9 5 0.953674µs 200 0.SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1.38-E-8° 200 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 0.9313225ns 200 37 37 37 37 37 37 37 Hr:Min:S ±23:59:59 17 1. (Octal) 114 115 115 116 116 116 116 117 117 117 117 120 120 120 121 121 121 122 122 124 125 125 125 125 126 126 130 133 136 137 140 140 141 141 142 143 144 145 146 147 150 150 150 150 151 151 Data BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR Discrete BCD BCD BCD BCD BNR BNR BNR BNR BNR BNR BNR Discrete BNR Discrete Discrete Discrete Discrete Discrete Discrete Discrete BNR BNR BNR Discrete BNR BNR Eqpt.0732 The Same Parameters as the FMS EQ ID 002 1200 37 mV .000172° 11 8.125 200 180 12 0.59.0625 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 0.00915 ± 24000 18 00915 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 ± 1024 14 .

1 N/A N/A 37 N/A 2 N/A 0.0001 0.00195 37 37 NM 0-128 16 0. (Octal) 151 151 152 152 153 153 154 154 154 154 155 155 156 156 157 157 157 160 160 161 161 162 162 162 163 163 164 164 165 165 165 166 166 167 167 170 171 171 171 172 173 174 174 Data BNR Discrete BNR Discrete BNR Discrete BNR BNR BNR Discrete BNR Discrete BNR Discrete SAL BNR BCD BNR Discrete BNR Discrete BNR Discrete BNR BNR Discrete BNR Discrete BNR BNR Discrete BNR Discrete BNR Discrete Discrete BNR BNR BNR BNR BNR BNR Eqpt.Page 7 DDM Knots DDM 200 1200 .1 N/A 9 N/A 0.00125 37 1.0732 37 Degrees Degrees 0-359 9 1 37 ±51.0002 200 1200 37 200 37 250 500 37 36 37 37 37 ATTACHMENT 1-16 SUPPLEMENT 16 UPDATES TO LABEL CODES SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1.00125 0.125 0.01 37 N/A 37 24 N/A pf N/A N/A N/A Feet N/A Degrees Feet/Min Degrees Knots NM N/A 0-400 N/A N/A N/A 131072 N/A ± 41 ±32768 ± 82 ±4096 0-128 N/A 14 N/A N/A N/A 16 N/A 15 15 16 15 16 N/A 0.001953 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 ± 0.0 0.1 9 1 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 37 Degrees N/A ±51. ID (Hex) 060 114 055 114 055 114 055 056 060 114 055 114 055 114 055 114 055 114 055 114 055 114 140 055 114 055 114 00B 055 114 00B 114 002 114 114 002 056 060 055 00B 055 Parameter Localizer Bearing (True) FCMC Valve Commands MLS GP Deviation Overhead Panel Switch/ Pushbutton & Refuel Panel Battery Power Supply Switch States MLS Selected Azimuth Level States MLS Max Selectable GP Runway Heading (True) Runway Heading (True) Level States and Low Warning and Transfer Indications MLS Selected Glide Path XFR Pump Faults & Wing Imbalance Warning MLS Basic Data Wd 1 Refuel Panel Switch States System Address Label For CVR MLS Basic Data Wd 2 Trim Tank Probe Capacitance MLS Basic Data Wd 3 Valve Feedback MLS Basic Data Wd 4 Indicated Pump Status MLS Basic Data Wd 5 Indicated Pump Status Density Altitude MLS Basic Data Wd 6 Indicated Pump Status MLS ABS GP Angle Indicated Pump Status Vertical Velocity MLS ABS Azimuth Angle Indicated Valve Status North/South Velocity Indicated Valve Status EPU Estimate Position Uncertainty/ (ANP) Actual Navigation Performance Indicated Valve Status Wing Imbalance And FQI Failure Warning RNP Reduced Navigation Performance Current RNP Current RNP Subsystem Identifier Localizer Deviation East/West Velocity Glide Slope Deviation Units Range Sig Bits Resolution MIN TX MAX TX REF ATT The Same Parameters as the FMS EQ ID 002 37 mV ± 2400 15 0.8 12 15 12 0.125 0.4 ±4096 ± 0.Code No.

025 ±512 11 0.03125 250 500 20 62.007812 ±512 11 0. Uncorrected.000172 150 ±512 11 0.025 131072 17 1 31.5 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 1024 14 0.000172 11 2-E-32 Cir 150 ±512 11 0.025 4.096 16 0.5 .5 1024 12 .025 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 ±512 11 0.5 512 512 ± 180 12 11 20 0.025 17 2048 18 0. Uncorrected.008 20 2048 18 0. mb Left Static Pressure Uncorrected.25 4.001 62.008 20 18 0. mb Impacted Pressure.025 62.03125 0.001 62.25 0. mb Right Static Pressure.0000625 62.000172 11 2E -32 Cir 150 512 265 min 512 512 512 11 10 16 14 14 0.000172 250 250 150 200 200 200 200 ATTACHMENT 1-16 SUPPLEMENT 16 UPDATES TO LABEL CODES 37 125 400 125 400 62.56 2048 15 0.25 .5 ± 180 20 0.5 125 36 36 Knots Knots Knots Degree C Degree C Degrees 125 125 125 500 500 400 36 36 36 44 36 36 27 44 Ft/Min Degrees Degree C Minute mb mb mb The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 32768 11 16 31.0625 62. Uncorrected.125 0.025 131072 17 1 31.25 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 ±512 11 0. (Octal) 176 176 176 176 177 177 177 177 177 200 200 200 201 201 201 202 202 202 203 203 204 204 204 204 205 206 206 206 207 210 210 211 211 211 211 212 212 212 212 212 213 213 215 215 215 Data BNR BNR BNR BNR BNR BNR BNR BNR BNR BCD BCD BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR SAL BNR BNR BNR SAL BNR BNR BNR BNR SAL BNR BNR BNR BNR BNR Eqpt. Uncorrected.025 4. Uncorrected.25 .008 20 11 0.008 20 1024 16 0. ID (Hex) 00B 0AD 038 114 00B 0AD 038 055 114 056 060 114 114 140 142 114 140 142 114 140 056 060 114 140 140 056 060 140 140 140 0AD 140 142 056 060 140 142 140 142 OAD O38 006 Parameter GLONASS Satellite Deselection W #1 Static Pressure Left. mb Units Range Sig Bits Resolution MIN TX MAX TX REF ATT 31 36 36 37 31 36 36 mb mb Degree C mb mb Nmiles Degree C 2048 2048 ±512 Degree C Degree C Mach Degrees Degree C M/minute Degrees Degree C Feet Degree C Feet Mach 17 18 0. mb Left Outer Tank Fuel Temp & Advisory Warn GLONASS Satellite Deselection W #2 Static Pressure Right. mb Impacted Pressure. Uncorrected.25 mile 0.5 400 500 2000 40 125 125 36 27 44 36 27 36 36 36 . mb Distance To Runway Threshold Inner Tank 1 Fuel Temp & Advisory Warning Drift Angle Drift Angle Inner Tank 2 Fuel Temp & Advisory Warning Inner Tank 3 Fuel Temp & Advisory Warning Mach Maximum Operation (Mmo) Projected Future Latitude Inner Tank 4 Fuel Temp & Advisory Warning Mach Rate Projected Future Latitude Fine Trim Tank Fuel Temp & Advisory Warning Altitude Baro Altitude Baro Altitude Right Outer Tank Fuel Temp & Advisory Warning Baro Corrected Altitude Mach Computed Airspeed Computed Airspeed Computed Airspeed (CAS) Airspeed Maximum Operating (VMO) True Airspeed FCMC Com A340-500/600 Total Air Temperature Indicated Total Air Temp (TAT) Projected Future Longitude FCMC M on A340-500/600 Alititude Rate Alititude Rate Altitude Rate Projected Future Longitude Fine FCMC Int A340-500/600 Static Air Temp (SAT) Vertical Time Interval Impacted Pressure.5 37 37 36 27 37 36 27 37 36 37 62.SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1-Page 8 Code No.096 12 0.096 12 0.5 62.0625 62.008 0.5 62.

5 36 62.05 31.25 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 180 12 0.5 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 180 12 0. Hg) Static Pressure.5 36 SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1. Hg) Static Pressure Corrected (In. (Octal) 215 217 217 217 217 217 220 220 220 221 221 221 222 222 222 223 223 223 224 224 224 225 225 225 225 226 227 227 230 231 231 232 232 232 232 232 233 233 233 234 234 235 235 236 236 Data BNR BNR BNR BNR BNR BNR Eqpt.1 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 0-400 14 0. Corrected (In. Indicated #1 Right Printer #2 Address Label Printer #2 Address Label Angle Of Attack.5 1200 36 pf Degree C pf 0-400 512 0-400 14 12 14 0. ID (Hex) 140 0AD 002 006 038 140 056 060 140 056 060 140 056 060 140 056 060 140 056 060 140 056 060 140 00B 019 053 114 0AD 114 002 055 056 060 114 056 060 114 056 060 056 060 056 060 Parameter Impact Pressure Subsonic Average Static Pressure Geometric Vertical Rate Static Pressure.5 200 62.5 36 62.001 20 16 0.1 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 37 37 .001 20 64 16 0.5 36 ATTACHMENT 1-16 SUPPLEMENT 16 UPDATES TO LABEL CODES 62.Page 9 62. Indicated #2 Left System Address Label For HUD Minimum Maneuvering Air Speed Minimum Maneuvering Air Speed Angle Of Attack.05 31.008 20 11 16 16 0.001 62. Indicated #1 Left Printer #1 Address Label Printer #1 Address Label Angle Of Attack.5 18 0. Average. Corrected (In.05 31.5 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 131072 17 1 31.1 200 37 36 37 pf 0-400 pf The Same Parameters as the FMS EQ ID 002 14 0.Code No. Hg) MCDU #1 Address Label MCDU #1 Address Label Baro Corrected Altitude #2 MCDU #2 Address Label MCDU #2 Address Label Angle Of Attack Indicated Average MCDU #3 Address Label MCDU #3 Address Label Angle Of Attack.5 36 26 Degrees 180 62.05 31.1 20 0.5 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 180 12 0.05 31. Indicated #2 Right Data Loader Responses CFDS Bite Command Summary For HFDR CFDS Bite Command Word For HFDU Left Outer Probes Capacitance Total Air Temperature Inner 2 Tank Probe Capacitance Active Intent Data Block GLS Airport ID Active Intent Data Block Active Intent Data Block Inner 4 Tank Probe Capacitance ACMS Information ACMS Information Right Outer Probe Capacitance ACMS Information ACMS Information ACMS Information ACMS Information ACMS Information ACMS Information Units mb mb Ft/Min Inches Hg Inches Hg Inches Hg Range 512 2048 20000 64 64 Sig Bits Resolution MIN TX MAX TX 125 200 200 200 125 REF ATT 36 36 36 36 36 BNR Feet BNR Degrees BNR Degrees BNR Degrees BNR SAL BNR BNR BNR Discrete Discrete BCD BCD BCD File Format DISC Discrete BCD BNR BNR BCD BNR BNR BNR BNR BNR BNR Degrees 14 0.25 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 180 12 0.03125 62.5 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 12 0.

5 ±180 14 0.3 655320 13 40 125 1200 36 125 200 37 36 36 37 055 140 055 140 055 056 060 Ft/Min mb 131072 4096 13 17 16 0.5 20 125 200 mb The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 2048 16 0. Uncorrected.5 125 36 5 36 5 36 36 Ratio mb 2 2048 11 18 0.5 125 36 19 36 mb NM Pounds Knots Deg/180 Pounds The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 2048 16 0. Uncorrected Minimum Airspeed Minimum Airspeed Static Pressure.5 Degrees 62. Corrected Horizontal Figure Of Merit Control Minimum Speed (Vcmin) Control Minimum Speed (Vcmin) Fuel On Board Airspeed Minimum Vmc Indicated Side Slip Angle or AOS Preselected Fuel Quantity System Address Label VDR #1 System Address Label VDR #2 System Address Label VDR #3 GBAS ID Altitude Rate GBAS Airport ID Impact Pressure MLS Station ID #1 Time For Climb Time For Climb Units Nm Range 16 Sig Bits 17 Resolution 0.03125 62.5 16 18 6.008 62. mb Modified Intent Data Block Modified Intent Data Block Modified Intent Data Block Total Pressure GLS Runway Selection System Address Label for ILS Angle Of Attack.01 31. Corrected General Max Speed (Vcmax) General Max Speed (Vcmax) Static Pressure.25 62. Normalized System Address Label For MLS Average Static Pressure mb.000122 MIN TX MAX TX 1200 REF ATT 29 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 5 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 180 12 0.001 0. ID (Hex) 00B 002 056 060 056 060 140 0AD 002 056 060 140 055 140 0AD 038 056 060 140 038 056 060 140 00B 056 060 114 140 0AD 114 Parameter Horizontal Uncertainty Level ACMS Information ACMS Information ACMS Information System Address Label For APM-MMR Min. (Octal) 237 237 237 237 241 241 241 241 242 242 242 242 242 242 243 244 244 245 245 245 245 245 245 246 246 246 246 246 247 247 247 247 247 250 250 251 252 253 254 254 255 255 256 256 256 Data BNR BNR BNR BNR SAL BNR BNR BNR SAL BNR File Format BNR BNR DISC SAL BNR SAL BNR BNR BNR BNR BNR SAL BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR SAL SAL SAL Discrete BNR Discrete BNR BLOCK BNR BNR Eqpt.25 62. Uncorrected System Address Label for AHRS Average Static Pressure mb.03125 62.5 200 125 41 36 42 36 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 .SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1.03125 31. Airspeed for Flap Extension Angle Of Attack. Corrected System Address Label for MMR Total Pressure.5 36 5 36 ATTACHMENT 1-16 SUPPLEMENT 16 UPDATES TO LABEL CODES mb The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 2048 16 0.1 E-5 200 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 655320 13 40 512 11 0. Airspeed for Flap Extension Min.05 31.03125 62. Uncorrected Average Static Pressure mb.5 200 62.Page 10 Code No.

Maneuver Airspeed Max.Page 11 Pounds 37 37 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 131068 15 4 131068 15 4 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 131068 15 4 Pounds Pounds 37 37 Pounds 37 250 500 37 36 . and Empty Warning Discrete Data # 1 Units Pounds Knots Range 131068 1024 Sig Bits 15 14 Resolution 4 0. Communication Link Status MCDU Normal Discrete Word SDU To ACARS MU/CMU Status Word VDR Status Word HFDL Status Word MLS Discrete Status Discretes Output Status Word #1 Intent Status Status Discretes Discrete Data #1 Unusable. Airspeed For Flap Retraction Min. ID (Hex) 114 140 055 056 060 114 140 00B 056 060 114 056 060 114 056 060 114 055 056 060 114 055 056 060 114 056 060 114 114 056 060 114 024 039 041 050 053 055 056 058 060 060 060 114 140 Parameter Left Outer Tank Fuel Quantity Equivalent Airspeed MLS Station ID #2 Time For Descent Time For Descent Inner Tank 1 Fuel Quantity Total Pressure (High Range) Date Date/Flight Leg Date/Flight Leg Collector Cell 1 and 2 Fuel Quantity Flight Number (BCD) Flight Number (BCD) Fuel On Board At Engine Start Documentary Data Documentary Data Center Tank Fuel Quantity Ground Station/Approach Min. Maneuver Airspeed Inner Tank 4 Fuel Quantity MU Output Data Word. (Octal) 256 256 257 257 257 257 257 260 260 260 260 261 261 261 262 262 262 263 263 263 263 264 264 264 264 265 265 265 266 267 267 267 270 270 270 270 270 270 270 270 270 270 270 270 270 Data BNR BNR BLOCK BNR BNR BNR BNR BCD BCD BCD BNR BCD BCD BNR BNR BNR BNR BLOCK BNR BNR BNR BLOCK BNR BNR BNR BNR BNR BNR BNR BNR BNR BNR Discrete Discrete Discrete Discrete Discrete DISC Discrete Discrete DISC DISC DISC Discrete Discrete Eqpt.03125 62.Code No. Buffet Airspeed Inner Tank 3 Fuel Quantity Inner Tank 2 Fuel Quantity Max. Airspeed For Flap Retraction Collector Cell 3 And 4 Fuel Quantity Ground Station/Approach Time To Touchdown Time To Touchdown Spare Min.5 125 Pounds mb dd:Mo:Yr Pounds Pounds Pounds The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 131068 15 4 4096 17 0. Buffet Airspeed Min.5 dd:mm:yr 6 1 day 200 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 131068 15 4 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 131068 15 4 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 131068 15 4 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 131068 15 4 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 125 1200 37 36 37 ATTACHMENT 1-16 SUPPLEMENT 16 UPDATES TO LABEL CODES 37 37 SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1.0625 MIN TX MAX TX REF ATT 37 36 62.

Pin Program Status SDU To EICAS/ECAM/EDU For Dual SATCOM VDR Mode Command Discrete Data #7 Output Status Word #2 Discrete Data #7 Miscellaneous Discrete IRS Maintenance Discrete Fuel Transfer and CG Status Application Dependent Application Dependent Application Dependent Application Dependent Application Dependent Application Dependent System Address Label for GPWS Present Position Latitude Present Position Latitude Right Outer Tank Fuel Quantity System Address Label for GNLU 1 Present Position Longitude Present Position Longitude Trim Tank Fuel Quantity Units Range Sig Bits Resolution 5000 MIN TX MAX TX 15000 REF ATT 27 250 500 500 2000 37 36 27 35 ATTACHMENT 1-16 SUPPLEMENT 16 UPDATES TO LABEL CODES N/A 250 200 500 1200 37 36 37 37 37 37 37 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 2 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 131068 15 4 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 131068 15 4 SAL BNR BNR BNR SAL BNR BNR BNR Pounds 37 5 Pounds 37 .SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1. ID (Hex) 142 041 055 056 060 114 140 142 053 056 060 114 140 00B 055 114 114 038 056 060 114 024 041 050 056 058 060 114 004 114 056 060 056 060 056 060 056 060 114 056 060 114 Parameter Aircraft Category (Disc Data 1) SDU To ACARS MU/CMU Join /Leave Message MMR Discrete Discrete Data #2 Discrete Data #2 Fuel Transfer Indication Discrete Data # 2 Altitude Filter Limits (Disc Data 2) HFDL Slave (Disc Data 3) Discrete Data #3 Discrete Data #3 Fuel Transfer Indication Discrete Data # 3 GNSS Sensor Status GNSS Status Memos And Status Fuel Transfer Indications IR Discrete Word #2 Discrete Data #6 Discrete Data #6 Miscellaneous Warning MU Output Data Word.Page 12 Code No. (Octal) 270 271 271 271 271 271 271 271 272 272 272 272 272 273 273 273 274 275 275 275 275 276 276 276 276 276 276 276 277 277 301 301 302 302 303 303 310 310 310 310 311 311 311 311 Data Discrete Discrete DISC Discrete DISC Discrete Discrete Discrete Discrete Discrete DISC Discrete Discrete DIS DISC Discrete Discrete Discrete Discrete DISC Discrete Discrete Discrete Discrete Discrete Discrete DISC Discrete Discrete Discrete Eqpt.

ID (Hex) 056 060 114 056 060 114 114 056 060 056 060 056 060 05A 056 060 Parameter System Address Label for GNLU 2 Ground Speed Ground Speed Additional Center Tank (Act 1) Fuel Quantity System Address Label For GNLU 3 Track Angle True Track Angle True Additional Center Tank (Act 2) Fuel Quantity System Address Label For GNU 1 Rear Center Tank (RCT) Fuel Quantity System Address Label For GNU 2 Wind Speed Wind Speed System Address Label For GNU 3 Wind Direction (True) Wind Direction (True) Track Angle Magnetic Track Angle Magnetic Fuel Quantity Act 3 Magnetic Heading Magnetic Heading System Address Label for Autothrottle Computer Drift Angle Drift Angle System Address Label for FCC 1 Flight Path Angle Flight Path Angle System Address Label For FCC 2 Geometric Altitude Geometric Altitude Geometric Altitude System Address Label For FCC 3 Estimated Position Uncertanity Estimated Position Uncertanity Effective Pitch Angle System Address Label For APU Effective Roll Angle System Address Label For APU Controller SAL Mode Control Pane (MCP) System Address Label For FMC 3 System Address Label For ATC Transponder System Address Label For DADC Track Angle Rate Track Angle Rate Track Angle Rate Units Range Sig Bits Resolution MIN TX MAX TX REF ATT 5 Pounds The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 131068 15 4 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 131068 15 4 131068 15 4 37 5 Pounds Pounds 37 5 37 5 ATTACHMENT 1-16 SUPPLEMENT 16 UPDATES TO LABEL CODES The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 5 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 4 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 9 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 9 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 18 Feet 50000 17 1 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 18 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 ±180 13 0.02 ±180 13 0.Code No.015 10 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 .Page 13 056 060 056 060 002 056 060 056 060 114 114 Degrees Degrees 37 13 37 28 45 8 12 12 20 002 056 060 Deg/Sec 32 11 0.02 SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1. (Octal) 312 312 312 312 313 313 313 313 314 314 315 315 315 316 316 316 317 317 320 320 320 321 321 321 322 322 322 323 323 323 323 324 324 324 324 325 325 326 327 330 331 332 335 335 335 Data SAL BNR BNR BNR SAL BNR BNR BNR SAL BNR SAL BNR BNR SAL BNR BNR BNR BNR BNR BNR BNR SAL BNR BNR SAL BNR BNR SAL BNR BNR BNR SAL BNR BNR BNR SAL BNR SAL SAL SAL SAL SAL BNR BNR BNR Eqpt.

Failure Status IRS Maintenance Word #2 MMR Maintenance Word Maintenance Word #2 Inner Tank 1 Probe Capacitance Maintenance Data # 2 MLS Bite Status Maintenance Word Center.001 10 20 Hz 10 62.5 20 Hz 20 Hz 62.001 0.00195 00B Feet ±131.999 4 0.072 20 0.SUPPLEMENT 15 TO ARINC SPECIFICATION 429 PART 1.1 250 500 pf 0-400 14 0.015 0.0055 0.Page 14 Code No.5 250 MIN TX MAX TX 20 110 Hz 20 125 110 Hz 110 Hz 125 500 REF ATT 14 14 36 36 36 38 ATTACHMENT 1-16 SUPPLEMENT 16 UPDATES TO LABEL CODES kg/l 0-.0055 0.1 The Same Parameters as the FMS EQ ID 002 21 200 1200 DIS Discrete ISO-5 ISO-5 BNR BNR BNR SAL SAL SAL SAL SAL BNR - NM The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 The Same Parameters as the FMS EQ ID 002 16 13 0. ACT & RCT Probe Capacitance Maintenance Data # 3 Flight Count IRS Maintenance Word #3 Inner Tank 3 Probe Capacitance Maintenance Data #5 Maintenance Data #5 GNSS Fault Summary IRS Maintenance Word #4 ISO Alphabet #5 Message ISO Alphabet #5 Message Flight Information Flight Information RAIM Status Word System Address Label For PSS System Address Label For CSS System Address Label For AES System Address Label For Multicast System Address Label For Bridge GNSS Height WGS-84 (Hae) Units Deg/Sec Degree Deg/Sec Ratio Degree Degree Ratio Ratio Range 128 ± 180 128 16 ± 180 ± 180 4 4 Sig Bits 13 15 13 14 15 15 12 12 Resolution 0.0055 0.125 1200 39 15 15 16 43 43 30 .1 250 500 37 36 34 37 36 37 pf 0-400 524287 14 0. ID (Hex) 004 004 005 140 004 038 140 140 004 018 019 024 038 050 053 055 058 114 140 024 038 055 058 114 140 055 058 114 140 038 114 056 060 00B 038 056 060 056 060 142 Parameter Inertial Yaw Rate Track Angle Grid Inertial Yaw Rate Pressure Ratio (Pt/Ps) Grid Heading Grid Heading Pressure Ratio (Ps/Pso) Air Density Ratio IRS Maintenance Discrete Maintenance Data #1 CFDS Bite Fault Summary Word For HFDR MU Output Data Word Failure Status IRS Maintenance Word #1 VDR Fault Summary Word CFDS Bite Fault Summary Word For HFDU ILS Maintenance Word Maintenance Word #1 Fuel Density Maintenance Data # 1 MU Output Data Word.015 0.001 0.01 250 500 37 36 pf 0-400 14 0. (Octal) 340 340 340 340 341 341 341 342 350 350 350 350 350 350 350 350 350 350 350 351 351 351 351 351 351 352 352 352 352 353 353 354 354 355 355 357 357 360 360 360 362 363 364 366 367 370 Data BNR BNR BNR BNR BNR BNR BNR BNR Discrete Discrete Discrete Discrete Discrete Discrete Discrete DISC Discrete BCD Discrete Discrete Discrete DISC Discrete BCD Discrete DISC Discrete BCD Discrete Discrete BCD Eqpt.

Page 15 .53E-5 200 50 Hz 50 Hz 50 Hz 50 Hz MIN TX MAX TX 1200 110Hz 110Hz 110Hz 110Hz REF ATT ATTACHMENT 1-16 SUPPLEMENT 16 UPDATES TO LABEL CODES SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1. (Octal) 370 375 375 376 376 Data BNR BNR BNR BNR BNR Eqpt.072 4 4 4 4 Sig Bits 20 18 18 18 18 Resolution 0.53E-5 1.53E-5 1.Code No.125 1.53E-5 1. ID (Hex) 00B 004 038 004 038 GNSS Height Along Hdg Accel Along Hdg Accel Cross Hdg Accel Cross Hdg Accel Parameter Units Feet Gs Gs Gs Gs Range ±131.

1996 AN 0 DOCUMENT Prepared by AIRLINES ELECTRONIC ENGINEERING COMMITTEE Published by AERONAUTICAL RADIO.MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS) PART 2 DISCRETE WORD DATA STANDARDS ARINC SPECIFICATION 429P2-15 PUBLISHED: March 6. MARYLAND 21401 . ANNAPOLIS. 2551 RIVA ROAD. INC.

Any use of or reliance on this document shall constitute an acceptance thereof "as is" and be subject to this disclaimer. express or implied. . copyright or other proprietary rights by third parties. is made in this regard.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. and no representation or warranty.

0 SUBJECT INTRODUCTION Purpose of ARINC Specification 429 Organization of ARINC Specification 429 DATA STANDARDS PAGE 1 1 1 2-138 iii .0 1.2 2.1 1.ARINC SPECIFICATION 429 TABLE OF CONTENTS ITEM 1.

Part 2 lists discrete word bit assignments in label order. For convenience of the user. Their use for intrasystem communications in systems in which the line replaceable units are defined in the ARINC characteristics as “system interchangeable” is not essential. The size of the document and the need for improved organization dictated the division of the document into three parts. “Functional Description.Page 1 1. 1. although it is desired.ADDED: MARCH 6.2 Organization of ARINC Specification 429 ARINC Specification 429 was originally published in a single volume through version 14 (429-14). the section and attachment numbering has been retained for the material moved from the original Specification to Part 3. “Discrete Word Data Formats ¢-15 Part 3. Electrical Interface.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. Data word formats. Those three parts include: Part 1. Label Assignments and Word Formats Part 2 .0 INTRODUCTION 1. standard label and address assignments. Part 3 describes protocols and message definitions for data transferred in large blocks and/or file format. 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. 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. and application examples are defined. . The “dash numbers” for each new Part will not be synchronized with the other Parts as time passes. “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. 1996 ARINC SPECIFICATION 429 PART 2 . Users of ARINC Specification 429 should ensure that the latest version of each Part is used when designing or procuring equipment.

Page 2 2.0 DATA STANDARDS Label 005 0D0 . 1996 ARINC SPECIFICATION 429 PART 2 . 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 0 X X X X X Label 005 0D0 X X X SDI PAD PAD Failure to clear serial data interrupt ARINC received fail PROM checksum fail User RAM fail NV RAM address fail NV RAM bit fail RTC fail Microprocessor fail Battery low NV RAM corrupt Not used Not used Not used Interrogate activated Erase activated BIT activated SSM Parity (Odd) X X Pass Pass Pass Pass Pass Pass Pass Pass Pass Pass Fail Fail Fail Fail Fail Fail Fail Fail Fail Fail Activated Activated Activated Non-Activated Non-Activated Non-Activated *Bits Installation Number 10 0 0 1 1 9 0 1 0 1 (4) 1 2 3 .ADDED: MARCH 6.Engine Discretes (737) Bit No.

1996 ARINC SPECIFICATION 429 PART 2 .Page 3 DATA STANDARDS Label 006 0D0 . 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 29 30 31 32 Function 1 0 X X X X X Label 006 0D0 X X X SDI X X X X X X X X X X X X X X PADS SSM Parity (Odd) *Bits Installation Number 28 Bits 27 1 0 1 1 0 26 0 1 1 1 0 25 0 0 0 0 0 Data 10 0 0 1 1 9 0 1 0 1 (4) 1 2 3 1 1 0 0 0 Engine Engine Engine Engine Engine Option Option Option Option Option 1 2 3 3 4 .Engine Options (737) Bit No.ADDED: MARCH 6.

Page 4 DATA STANDARDS Label 013 0B8 . 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.0 2.0 32.0 64.ADDED: July 1. . 1990 ARINC SPECIFICATION 429 PART 2 .0 16.5 1. They are generated at the control panel.0 4. Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 0 X X X X X X X X SDI (MSB) SDI (LSB) Flight Level Altitude Select Altitude Select Spare Spare Spare Spare User Defined TCAS Display Mode 1 Absolute 2 Relative Label 013 0B8 3 Selected TCAS Range (NM) 0.0 8.0 SSM SSM Parity (Odd) Note 1: BITS 10 0 0 1 1 9 0 1 0 1 SDI MEANING Note 2: BITS 13 12 0 1 0 1 Altitude Select MEANING Both (TA/RA Bus #1 and #2) Left (TA/RA Bus #1) Right (TA/RA Bus #2) Unrestricted 0 0 1 1 Normal -A to +A Above -A to +B Below -B to +A Not Used NOTE 3: The use of these user-defined bits is optional.Control Word for TCAS/Mode S Transponder Bit Status Bit No.

Control Word for TCAS/Mode S Transponder Bit Status Bit No. . Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 0 X X X X X X X X SDI Altitude Reporting SPI Display Control Sensitivity Level Control D1 D2 D4 C1 C2 C4 B1 B2 B4 A1 A2 A4 SSM SSM Parity (Odd) OFF Ident ON 1 2 5 ON Ident OFF Label 016 0B8 3 4096 Ident Code Note 1: BITS 14 0 0 1 1 13 0 1 0 1 Display Control MEANING Note 2: BITS 17 16 0 0 1 1 0 0 1 1 Manuel Sensitivity Level Control MEANING 15 0 1 0 1 0 1 0 1 SL=0 (AUTOMATIC) SL=1 (STBY) SL=2 (TA ONLY) SL=3 SL=4 SL=5 SL=6 SL=7 Primary and Traffic Advisory Primary display functions only (no TCAS data) TCAS Traffic Advisory Only No control function possible 0 0 0 0 1 1 1 1 NOTE 3: NOTE 4: See Attachment 5A of ARINC Characteristic 735 for Mode A reply codes. COMMENTARY The delay from the time a command is activated at the control panel to the time of the equipment response should be minimized. 1990 ARINC SPECIFICATION 429 PART 2 .Page 5 DATA STANDARDS Label 016 0B8 .ADDED: July 1. 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. The transfer time should not exceed 200 milliseconds.

Discrete Status 2 EFIS Bit No. 1996 ARINC SPECIFICATION 429 PART 2 .ADDED: MARCH 6. Function Bit Status 1 0 X X X 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 Label 145 025 X X X X X SDI DI-29P DI-30P DI-31P DI-32P DI-33P DI-34P DI-35P DI-36P DI-37P DI-38P DI-39P DI-40P DI-41P DI-43P DI-44P DI-45P PAD PAD PAD SSM Parity (Odd) GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN X X X .Page 6 DATA STANDARDS Label 145 025 .

G/A Mode Oper. Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Not Not Not Not Not Not Not Not Not Not Not Not Not Not Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested X X Not Used SSM Parity (Odd) . Rollout Mode Oper. G/S Mode Oper.Page 7 DATA STANDARDS Label 145 0A1 . Appr. Flare Oper. 1980 ARINC SPECIFICATION 429 PART 2 . Mode Req.REVISED: August 1.FCC Control Panel Status Discrete (Triplex) Bit Status Bit No. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 0 X X X Label 145 0A1 X X X Unassigned A/P CWS R Engaged A/P CWS L Engaged A/P CWS C Engaged A/P CMD R Engaged A/P CMD L Engaged A/P CMD C Engaged Land 2 (Green) Land 3 (Green) LOC Mode Oper.

Function Bit Status 1 0 X X X 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 Label 146 025 X X X X X SDI DI-46P DI-47P DI-48P DI-49P DI-50P DI-51P DI-52P DI-53P DI-54P DI-55P DI-56P DI-58P DI-59P DI-60P DI-61P DI-62P PAD PAD PAD SSM Parity (Odd) GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN X X X .Page 8 DATA STANDARDS Label 146 025 .Discrete Status 3 EFIS Bit No. 1996 ARINC SPECIFICATION ARINC 429 PART 2 .ADDED: MARCH 6.

1980 ARINC SPECIFICATION 429 PART 2 . Unassigned Align FW Land 3 FW Warning Inhibit Unassigned A/P CMD Warning SSM Parity (Odd) Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Not Not Not Not Not Not Not Not Not Not Not Not Not Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested X X Not Requested Not Requested Not Requested Not Requested . LOC Excess Beam Dev. Cat.Page 9 DATA STANDARDS Label 146 0A1 . 3 Autoland Avail. Auto G/A Not Available Engine Out Compensation Not Avail. F/D Eng.FCC Control Panel Status Discrete (Dual-Dual) Bit Status Bit No. 2 Autoland Avail. 2 Available Cat. F/O F/D Eng.REVISED: August 1. Land Trk ATS Warn. Glide Excess Beam Dev. ILS Cat. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 0 X X X Label 146 0A1 X X X Unassigned A/P CWS A/P CMD Capt.

Page 10 DATA STANDARDS Label 147 025 . 1996 ARINC SPECIFICATION 429 PART 2 .ADDED: MARCH 6.Discrete Status 4 EFIS Bit No. Function Bit Status 1 0 X X X 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 Label 147 025 X X X SDI DI-63P DI-64P DI-65P DI-66P DI-67P DI-68P DI-69P DI-93P DI-94P DI-95P DI-98P DI-99P DI-100P DI-101P DI-106P DI-107P PAD PAD PAD SSM Parity (Odd) GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN X X X X X .

ADDED: MARCH 6. Function Bit Status 1 0 X X X 1 2 3 4 5 6 7 8 9-27 28 29 30-31 32 Label 151 05A X X X X X PAD Bits LBS/KGS PAD SSM P X X . 1996 ARINC SPECIFICATION 429 PART 2 .LB/KG Control Word Bit No.Page 11 DATA STANDARDS Label 151 05A .

1996 ARINC SPECIFICATION 429 PART 2 .Page 12 DATA STANDARDS Label 155 025 .Discrete Status 5 EFIS Bit No.ADDED: MARCH 6. Function Bit Status 1 0 X X X 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 Label 155 025 X X X X X SDI DI-108P DI-110P DI-111P DI-112P DI-115P DI-116P DI-117P DI-118P DI-119P DI-120P DI-121P DI-122P DI-123P DI-125P DI-126P DI-127P PAD PAD PAD SSM Parity (Odd) GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN X X X .

.

.

.

.

ADDED: MARCH 6.Discrete Status 6 EFIS Bit No.Page 17 DATA STANDARDS Label 160 025 . 1996 ARINC SPECIFICATION 429 PART 2 . Function Bit Status 1 0 X X X X X X X X 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 Label 160 025 SDI DI-128P DI-129P DI-130P DI-139P DI-140P DI-142P DI-143P DI-144P RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED PAD PAD PAD SSM Parity (Odd) GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND OPEN OPEN OPEN OPEN OPEN OPEN OPEN OPEN X X X .

.

Discrete Status 7 EFIS Bit No.Page 19 DATA STANDARDS Label 161 025 . Function Bit Status 1 0 X X X X X X X X 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 Label 161 025 SDI RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED PAD PAD PAD SSM Parity (Odd) X X X .ADDED: MARCH 6. 1996 ARINC SPECIFICATION 429 PART 2 .

.

.

1990 ARINC SPECIFICATION 429 PART 2 .ADDED: July 1.Full Authority Engine Control Maintenance Discretes Bit Status Bit No.Page 22 DATA STANDARDS Label 161 10A . Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 0 X X X X X X X X SDI Label 161 10A Pad Screen ID 1 SSM SSM Parity (Odd) Note 1: Screen ID Codes MEANING Ignition Test Ignitor Test in Progress FADEC Test FADEC Test in Progress Value (HEX) 13 14 21 22 .

1996 ARINC SPECIFICATION 429 PART 2 . Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 0 X X X X X X X X SDI Label 161 10B Pad Screen ID 1 SSM SSM Parity (Odd) Note 1: Screen ID Codes MEANING Ignition Test Ignitor Test in Progress FADEC Test FADEC Test in Progress Value (HEX) 13 14 21 22 .Page 23 DATA STANDARDS Label 161 10B .ADDED: July 1.Full Authority Engine Control Maintenance Discretes Bit Status Bit No.

.

Pitch CWS L.FCC General Discrete Word Bit Status Bit No.D. Flare Cond. 700 Ft. Cond.ADDED: August 1. Mon.D. 1980 ARINC SPECIFICATION 429 Part 2 . Flare Cond. Mon.Page 25 DATA STANDARDS Label 270 001 . LOC Trk Mon. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 270 001 X X X X X X SDI Glide Capt. Roll Appr. Com. LOC Trk Com. ID LOC Capt. CWS L. II Own Land II Own Land III Own FCC FW AHRS I Validity N1 Command ARM TCC Command SPD/Mach Command TBD SSM Parity (Odd) Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested 0 . Com. 700 Ft.

1981 ARINC SPECIFICATION 429 PART 2 .Page 26 DATA STANDARDS Label 270 004 .ON DC 2 Align Fault No IRS Initialization EXCESSIVE MOTION ERROR ADC/IRU Fault No VOR/DME #1 Input Align Status No VOR/DME #2 Input SSM Parity (Odd) Yes No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No No No No No No No No No No No No No No No X X X X X X 0 .REVISED: April 24.IRS Discrete Bit Status Bit No. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 270 004 Bit 11 or 12 or 13 is always set to logic (1) SDI Align Mode/Not Ready Reversionary Attitude Mode Normal Mode Set Heading Attitude Invalid DC Fail (Low) ON DC ADC Fault IRU Fault See Note DC Fail .

The DC power input was not available when required by the IRU. Three bits provide a seven state alignment status as follows: Align Status LSB 26 1 0 1 0 27 1 1 0 0 MSB 28 1 1 0 0 Alignment Commenced Highest Alignment Status Unassigned 29 No VOR/DME #2 Input . heading. but power-on BITE found no faults with the IRU ADC input channel. 22 23 24 No IRS Initialization Excessive Motion Error ADC/IRU Fault 25 26 27 28 No VOR/DME #1 Input Align status is represented by a series of descending digits. 21. Mode NAV Mode Set Heading Function The IRU operating software mode is ALIGN or the initialization of any mode.On DC 21 Align Fault Failed the IRU operating software ALIGN criterion but neither power-on nor continuous BITE show any faults. Non-zero ground speed during the ALIGN mode. The IRU is operating on the DC power input. but no power-on BITE information available prior to flight. The BITE has detected a fault not annunciated in BITS 18. or 24. 22. The IRU has detected a failure of attitude.ADDED: April 24. The IRU operating software is ATT. each indicating a successive state of alignment. ADC in-flight fault. ADC in-flight fault. or linear body accelerations (same as FAULT discrete). The IRU DC power input is less than 18 VDC. condition shall be reset only by power-on initialization. 23. 1981 ARINC SPECIFICATION 429 PART 2 . This 15 Attitude Invalid 16 17 18 DC Fail On DC ADC Fault 19 20 IRU Fault DC Fail . angular body rates. No input or an incorrect input has been received from the IRMP or FMC’s. The IRU operating software mode is NAV.Page 27 DATA STANDARDS IRS/AHRS BIT EXPLANATIONS Bit No. 11 12 13 14 Align Mode/NR Reversionary Att. 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.

2 of ARINC Characteristic 705 for description of modes of heading operation.2. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 270 005 X X X X X X SDI Align Mode/Not Ready Reversionary Attitude Mode Normal Mode Magnetic Heading/DG Mode Attitude Invalid Low Battery (Not used in AHRS) On Battery TAS Invalid AHRU Fault Yes Yes Yes Yes Yes Yes Yes Yes Yes No No No No No No No No No 0 IRS Use No VOR/DME #1 Input IRS Use No VOR/DME #2 Input SSM Parity (Odd) Yes No Yes No NOTES: 1) 2) Attitude invalid is equivalent to AHRS failure. Bit 13 "1" condition indicates that AHRS is in the "Normal" mode as described in Section 1. Bit 14 "1" condition indicates that AHRS is in the "Magnetic Heading" mode. 3) . 1981 ARINC SPECIFICATION 429 PART 2 .Page 28 DATA STANDARDS Label 270 005 .1 of ARINC Characteristic 705.2. A "0" condition indicates the AHRS is in the reversionary "DG" mode. See Section 1. A "0" condition indicates that the AHRS is in the reversionary "Basic mode".AHRS Discrete Bit Status Bit No.ADDED: April 24.

REVISED: April 24.Page 29 DATA STANDARDS Label 270 006 . 1981 ARINC SPECIFICATION 429 PART 2 .ADS Discrete Bit Status Bit No. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 270 006 X X X X X X SDI Icing Detector Pitot Probe Heat ADS Computer Status Pitot/Static Probe Heat Static Source Heat TAT Probe Heat Left Side Angle of Attack Sensor Heat Right Side Angle of Attack Sensor Heat VMO/MMO Overspeed Warning On On Fail On On On On On Warn Off Off Good Off Off Off Off Off Not Warn 0 Spare Angle of Attack Alternate Correction Baro-Correction Port "A" Zero Mach SSEC SSM Parity (Odd) Yes Yes Yes No No No .

GPS DATA Bit No.ARINC SPECIFICATION 429 PART 2 . 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Function 1 X 0 X Label 270 00B X X X X X X SDI Spare Spare Vertical Maneuver Alert (flash) Vertical Maneuver Alert (on) Turn Point Alert (flash) Turn Point Alert (on) No Waypoint Entered No Course Entered 2D/3D NAV GPS NAV VALID EN ROUTE Terminal GPS HIGH ACCURACY APPROACH (Angular) GPS SELF TEST (BIT) Figure of Merit (LSB) Figure of Merit (LSB) Figure of Merit (LSB) Figure of Merit (MSB) SSM Parity (Odd) On Flash On Flash True True 3D True True True True True True Off Off Off Off False False 2D False False False false False False NOTE: Typical discrete functions are shown in the above table.Page 30 DATA STANDARDS Label 270 00B . Slight variations of bit usage may arise according to the specific application. Bits 15 0 1 0 1 16 0 0 1 1 Status Enroute Terminal Approach N/A .

EEC Discrete Bit Status Bit No.Page 31 DATA STANDARDS Label 270 01A .ADDED: January 22. 1982 ARINC SPECIFICATION 429 PART 2 . Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 270 01A X X X X X X SDI Pad X X X X Yes Yes Yes Yes Yes Off Yes Yes Failed Yes On Yes Failed Failed Yes No No No No No No No No Good No Off No Good Good No 0 EPR Loop Selected N2 Loop Selected EGT Loop Selected Integrator On Min Stop Integrator On Max Stop EEC On/Off Discrete Initialization Low Speed Latch EAROM EEC Probe T2 Selected Fault Light See Main Panel TCC System TCA System Thrust Bump Inhibit SSM Parity (Odd) .

REVISED: August 1.Page 32 DATA STANDARDS Label 270 023 . .GPWS Discrete Bit Status Bit No. 1980 ARINC SPECIFICATION 429 PART 2 . Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 270 023 X X X X X X SDI Sink Rate Pull Up Terrain Don’t Sink Too Low Gear Too Low Flap Too Low Terrain Glide Slope Minimum Minimum Terrain Pull Up 0 * Spare (All "O" States) SSM 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. Manually Selected** N2 Droop Control Mode Reverser System Status Channel Controlling Status 2. according to the specific application. NOTE: Typical discrete functions are shown in the above table.EEC Status Bit Status Bit No. Slight variations of bit usage may arise . 1986 ARINC SPECIFICATION 429 PART 2 . Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 ** X X Label 270 02F X X X X X X X X X X Invalid Secondary Selected Engaged Inoperative Controlling Failed Failed Failed Failed Incapable Faulted Failed Cutout OK X Auto Not Selected Not Engaged OK Not Controlling Operational OK OK Operational Capable Ok Operational Not Cutout X X X 0 SDI PAD PAD PAD PDIU Status Spare Channel Select Mode Primary Chan.Page 33 DATA STANDARDS Label 270 02F .5 Bleed System Failed TCA Valve(s) Failed Closed Case Cooling Valve Stuck 14th Stage Bleed System Failed Channel Incapable (Failed) Oil Cooling System Status SVA System Failed Starter Cutout Command Spare SSM Parity Secondary Channel Only.

ADDED: April 24. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13-14 15-16 17 18 19 20 21 22 23 24 25 26 27-28 29 30 31 32 X X Label 270 030 X X X X X X SDI 0 SPARE Left (See Note 1 Below) Right (See Note 2 Below) Up (See Note 3 Below) Down (See Note 4 Below) SSM Parity (Odd) Note 1: 00 01 10 11 - Left Component Note 2: 00 01 10 11 - Right Component No Left Adivisory Turn Left Don’t Turn Left Not Used No Right Advisory Turn Right Don’t Turn Right Not Used Note 3: 0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 - Up Component No Up Advisory Climb Climb Faster than 500 FPM Climb Faster than 1000 FPM Climb Faster than 2000 FPM Don’t Decend Don’t Decend Faster than 500 FPM Don’t Decend Faster than 1000 FPM Don’t Decend Faster than 2000 FPM 1111 Not Used Note 4: 0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 - Down Component No Down Advisory Decend Decend Faster than Decend Faster than Decend Faster than Don’t Climb Don’t Climb Faster Don’t Climb Faster Don’t Climb Faster 1111 Not Used 500 FPM 1000 FPM 2000 FPM than 500 FPM than 1000 FPM than 2000 FPM .Transponder Discrete Bit Status Bit No.Page 34 DATA STANDARDS Label 270 030 . 1981 ARINC SPECIFICATION 429 PART 2 .

Page 35 DATA STANDARDS Label 270 033 Bit Status Bit No.ADDED: January 3. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 270 033 X X X X X X SDI Turbine Case Cooling Valve Upper Turbine Cooling Valve Lower Turbine Cooling Valve Fuel Heater Valve Open Open Open Open Closed Closed Closed Closed 0 Spare (all "0" states) SSM Parity (Odd) . 1983 ARINC SPECIFICATION 429 PART 2 .

Meanwhile.ADDED: July 1. The omission is expected to be corrected in Change 7.TCAS Vertical RA Data Discrete Bit Status Bit No.Page 36 DATA STANDARDS Label 270 035 . 1990 ARINC SPECIFICATION 429 PART 2 . 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. . Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 X X Label 270 035 X X X X X X SDI BIT 0 SDI BIT 1 100 ft/min 200 ft/min Advisory 200 ft/min Altitude 200 ft/min Rate 1600 ft/min 3200 ft/min Sign Combined Control Combined Control 1 Combined Control Vertical Control Vertical Control 2 Vertical Control Up Advisory Up Advisory 3 Up Advisory Down Advisory Down Advisory 4 Down Advisory SSM SSM 5 Parity (Odd) 0 Note 1: BITS 20 19 18 0 0 0 0 1 1 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 Combined Control MEANING No Advisory Clear of Conflict Drop Track Altitude Lost Climb Corrective Descend Corrective Preventative Not Used See Note 1A See Note 1A NOTE 1A: CAS logic defined by RTCA DO-185 Change 6 does not discriminate between Climb Corrective and Descend Corrective.

no RA should be issued by the Display. .Page 37 DATA STANDARDS Label 270 035 (cont’d) . 1990 ARINC SPECIFICATION 429 PART 2 .ADDED: July 1.TCAS Vertical RA Data Discrete Note 2: BITS 23 22 21 0 0 0 0 1 1 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 Advisory is not one of the following types Crossing Reversal Increase Maintain Not Used Not Used Not Used Vertical Control MEANING Note 3: BITS 26 25 24 0 0 0 0 1 1 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 Up Advisory MEANING No Up Advisory Climb Don’t Descend Don’t Descend > Don’t Descend > Don’t Descend > Not Used Not Used 500 1000 2000 Note 4: BITS 29 28 27 0 0 0 0 1 1 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 Down Advisory MEANING No Down Advisory Descend Don’t Climb > Don’t Climb > 500 Don’t Climb > 1000 Don’t Climb > 2000 Not Used 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.

Propulsion Discrete Interface Unit Bit Status Bit No.Page 38 DATA STANDARDS Label 270 03A . Slight variations of bit usage may arise .REVISED: NOVEMBER 17. Function 1 1 2 3 4 5 6 7 8 9-10 X X Label 270 03A x X X X X X SDI 1 Left Engine 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 0 Right Engine 1 Failed Heat Off Minimum Ground Shut Down Faulted OK Heat On X Approach Air Running OK X X X X X X Off X X X X X 0 0 SDI PDUI Self Test P2/T2 Probe Heat Spare Idle Select Air/Ground Switch Opposite Engine Status EEC to PDUI SDD Spare Spare Spare Spare Spare Spare Ground Test Power Spare Spare Spare Spare Spare SSM Parity (Odd) On NOTE: Typical discrete functions are shown in the above table. according to the specific application. 1986 ARINC SPECIFICATION 429 PART 2 .

ADDED: January 3. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 270 03B X X X X X X SDI INS VOR/LOC ILS/Land Land Altitude Hold Altitude Select Mach IAS Vertical Speed TURB PMS Captain’s F/D On and Select F/O F/D On and Select Course Transfer No. 1983 ARINC SPECIFICATION 429 PART 2 . 1 Course Transfer No.Page 39 DATA STANDARDS Label 270 03B Bit Status Bit No. 2 A/P Engage Manual A/P Engage Command Spare (all "0" states) Word Validity SSM Parity (Odd) Selected Selected Selected Selected Selected Selected Selected Selected Selected Selected Selected Selected Selected Selected Selected Selected Selected Invalid Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not Selected Selected Selected Selected Selected Selected Selected Selected Selected Selected Selected Selected Selected Selected Selected Selected Selected 0 Valid .

Status Word Bit No.Engine 2 AVM Engine 1 Double Channel Fault PAD AVM Engine 2 Double Channel Fault PAD PAD AVM Engine 1 Alert PAD AVM Engine 2 Alert Engine 1 High Broadband Alert PAD Engine 2 High Broadband Alert PAD NVRAM Failure Fault History Erase PAD Flight History Erase PAD PAD PAD PAD PAD PAD * 757 Pratt and Whitney and 737 CFM-56 ** 757 Rolls Royce Only *** 737 CFM-56 Only . 1 2 3 4 5 6 7 8 9-10 11-28 30-31 32 Function 1 X 0 X Label 270 03D X X X X X X SDI Data Status Matrix Parity (Odd) Bit **11 *11 12 *13 **13 *14 **14 **15 *15 **16 *16 *17 **17 *18 **18 **19 *19 **20 *20 21 22 23 ***23 24 25 26 27 28 29 Parameter AVM System Fault PAD AVM System Fault AVM Engine 1 Alert Broadband Alert . 1996 ARINC SPECIFICATION 429 PART 2 .Page 40 DATA STANDARDS Label 270 03D .Engine 1 AVM Engine 2 Alert Broadband Alert .ADDED: MARCH 6.

REVISED: November 17.Page 41 DATA STANDARDS Label 270 03F . Slight variations of bit usage may arise . 1986 ARINC SPECIFICATION 429 PART 2 . Manually Selected** N2 Droop Control Mode Reverser System Status Channel Controlling Status 2. according to the specific application. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 ** X X Label 270 03F X X X X X X X X X X Invalid Secondary Selected Engaged Inoperative Controlling Failed Failed Failed Failed Incapable Faulted Failed Cutout OK X Auto Not Selected Not Engaged OK Not Controlling Operational OK OK Operational Capable Ok Operational Not Cutout X X X 0 SDI PAD PAD PAD PDIU Status Spare Channel Select Mode Primary Chan.5 Bleed System Failed TCA Valve(s) Failed Closed Case Cooling Valve Stuck 14th State Bleed System Failed Channel Incapable (Failed) Oil Cooling System Status SVA System Failed Starter Cutout Command Spare SSM Parity Secondary Channel Only.EEC Status Bit Status Bit No. NOTE: Typical discrete functions are shown in the above table.

TACAN/MLS Select Bits 15 0 1 0 1 16 0 0 1 1 TACAN MLS W Mode Not Used MLS Z Mode Meaning Table 2 .REVISED: MARCH 6. 1996 ARINC SPECIFICATION 429 PART 2 .Page 42 DATA STANDARDS Label 270 115 . 1 2 3 4 5 6 7 8 9 10 11 12 13-14 15-16 17 18 19 20 21 22 23 24 25 26 27-28 29 30 31 32 Function 1 X 0 X Label 270 115 X X X X X X SEL MEM MEM TUNE Pad MLS Select TACAN 1 IN BEARING MEMORY IN RANGE MEMORY AUTOTUNE 1 (LSB) BCD Channel Code Units (MSB) (LSB) HEX Channel Code Tens (MSB) TST X/Y Mode Control INT AGC STAT Parity (Odd) TEST X 2 NORMAL ENABLE NO COMPUTED DATA INVERSE DISABLE VALID DATA NO TEST Y TACAN 2 NO BEARING MEMORY NO RANGE MEMORY NO AUTOTUNE Table 1 .Stored TACAN Control Word Bit No.Mode Control Bits 27 0 1 0 1 28 0 0 1 1 REC T/R A/A REC A/A T/R Meaning .

Page 43 DATA STANDARDS Label 271 005 . 1981 ARINC SPECIFICATION 429 PART 2 . Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 271 005 X X X X X X SDI MSU Fail RMCU Fail Yes Yes No No 0 Spare No VOR/DME #2 Input SSM Parity (Odd) .ADDED: April 24.AHRS Discrete Bit Status Bit No.

Page 44 DATA STANDARDS Label 271 006 .ADS Discrete Bit Status Bit No.ADDED: April 24. 1981 ARINC SPECIFICATION 429 PART 2 . Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 271 006 X X X X X X SDI Zero Angle of Attack SSEC Angle of Attack Sensor Status Yes Fail No Good 0 Spare SSM Parity (Odd) .

HRC.Bus 1 Word 1 Bit Status Bit No.VSB) Transponder To TCAS . .Page 45 DATA STANDARDS Label 271 018 .VRC.HSB.CVC. 1990 ARINC SPECIFICATION 429 PART 2 .CHC.ADDED: July 1.TCAS Coordination Discrete (MTB. Normal ARINC 429 protocol calls for the transmission of the LSB of the field first. Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 X X Label 271 018 X X X X X X RF MSG BIT 42 43 44 45 46 47 48 49 50 51 52 56 57 58 59 60 61 62 63 64 0 MTB CVC CVC VRC VRC CHC CHC CHC HRC HRC HRC HSB HSB HSB HSB HSB VSB VSB VSB VSB Pad SSM SSM 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.

Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 271 01A X X X X X X SDI Model Pad 0 1 2 3 Engine Model Code Engine Model Code Spare 1 0 1 0 1 1 0 0 X X X X On Hi On On On Open Sel. Off X X X X X 0 A/C Pack A/C Pack Flow Mode Air Driven Pump Wing Anti-Icing Cowl Anti-Icing Isolation Valve Approach Idle Tt2 Probe Heat Spare SSM Parity (Odd) Boeing 767 Only .ADDED: January 22.Page 46 DATA STANDARDS Label 271 01A . On Off Lo Off Off Off Closed Not Sel. 1982 ARINC SPECIFICATION 429 PART 2 .EEC Discrete Bit Status Bit No.

according to the specific application. 1986 ARINC SPECIFICATION 429 PART 2 . Slight variations of bit usage may arise . Bypass Valve Sol.Page 47 DATA STANDARDS Label 271 02F Bit Status Bit No. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 271 02F X X X X X X SDI PAD PAD PAD Reverser Deploy Command Turbine Cooling Air Valve Solenoid Fuel-Oil Heat Ex.REVISED: November 17. Spare Spare 14th Stage Bleed Command Spare Spare Spare Spare T/L Interlock Actuator Command Reserved (Spare Relay Command) 0000 = PW2037 other codes Invalid X X X X On On On Off Off Off 0 Closed Open X X X X Block Rev X X X X X X Block Fwd Engine Type Code SSM Parity (Odd) NOTE: Typical discrete functions are shown in the above table.

Bleed Valve Pos. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 271 033 X X X X X X SDI High Pressure Compressor Exit Pressure Fan Inlet Total Pressure Low Pressure Compressor Exit Pressure Exhaust Gas Total Pressure Thermocouples CPU Self-Test A/D Converter Self-Test ARINC 429 Self-Test Stator Vane Angle Low Press.Page 48 DATA STANDARDS Label 271 033 Bit Status Bit No. Comp. 1983 ARINC SPECIFICATION 429 PART 2 . Fuel Flow Power Supplies Tachometers Resistive Temperature Probes Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Good Good Good Good Good Good Good Good Good Good Good Good Good Good 0 Spare (all "0" states) SSM Parity (Odd) .ADDED: January 3.

Page 49 DATA STANDARDS Label 271 035 (RESERVED) . 1990 ARINC SPECIFICATION 429 PART 2 .TCAS Horizontal RA Data Discrete Bit Status Bit No.ADDED: July 1. Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 X X Label 271 035 X X X X X X 0 Parity (Odd) .

Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 271 03A X X X X X X SDI ECS Pack-L ECS Pack-R ECS Pack Demand-L ECS Pack Demand-R PNEU Shutoff Valve-L PNEU Shutoff Valve-R Isolation Valve Spare Wing Anti-Ice-L Wing Anti-Ice-R Cowl Anti-Ice-L Cowl Anti-Ice-R ON ON HI HI CLOSED CLOSED OPEN ON ON ON ON OFF OFF LO LO OPEN OPEN CLOSED X OFF OFF OFF OFF 0 Spare (all "0" states) SSM Parity (Odd) NOTE: Typical discrete functions are shown in the above table. 1986 ARINC SPECIFICATION 429 PART 2 . according to the specific application.REVISED: November 17.Page 50 DATA STANDARDS Label 271 03A Bit Status Bit No. Slight variations of bit usage may arise .

Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 271 03B X X X X X X X SDI Flare Arm Flare Engage Glide Slope Capture Go-Around Engage Dual Engage Triple Arm Triple Engage Rollout Engage Nav Arm Nav Capture Pitch Wheel Enable Turn Knob in Detent Heading Hold A or C. 1983 ARINC SPECIFICATION 429 PART 2 .ADDED: January 3.Page 51 DATA STANDARDS Label 271 03B Bit Status Bit No. and B 28 VDC Reference Spare (Pad Bit) Spare (Pad Bit) Spare (Pad Bit) Yaw Damper Engage Word Validity SSM Parity (Odd) Armed Engaged Engaged Engaged Engaged Armed Engaged Engaged Armed Engaged Enabled In Detent Hold Referenced Not Not Not Not Not Not Not Not Not Not Not Not Not Not Armed Engaged Engaged Engaged Engaged Armed Engaged Engaged Armed Engaged Enabled in Detent Hold Referenced X X X Not Engaged Valid 0 Engaged Invalid .

according to the specific application. 1986 ARINC SPECIFICATION 429 PART 2 . Spare Spare 14th Stage Bleed Command Spare Spare Spare Spare T/L Interlock Actuator Command Reserved (Spare Relay Command) 0000 = PW2037 other codes Invalid X X X X On On On Off Off Off 0 Closed Open X X X X Block Rev X X X X X X Block Fwd Engine Type Code SSM Parity (Odd) NOTE: Typical discrete functions are shown in the above table. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 271 03F X X X X X X SDI PAD PAD PAD Reverser Deploy Command Turbine Cooling Air Valve Solenoid Fuel-Oil Heat Ex.REVISED: November 17. Slight variations of bit usage may arise .Page 52 DATA STANDARDS Label 271 03F Bit Status Bit No. Bypass Valve Sol.

1980 ARINC SPECIFICATION 429 PART 2 . Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 272 001 X X X X X PERF CLP SPD APR LIM FLP SLT N1 EPR TO FLX MCT CLB CR VNAV IAS MACH ALT TRK RTD MIN SSM Parity Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not X Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested 0 .Page 53 DATA STANDARDS Label 272 001 .ADDED: August 1.FCC Automatic Throttle Modes Discrete Word Bit Status Bit No.

The N1 or EPR cruise thrust limit is currently in effect.ADDED: August 1. The automatic throttles are clamped. The N1 or EPR take off thrust limit is currently in effect. The N1 or EPR maximum continuous thrust limit is currently in effect. or by throttle low limit position. The automatic throttles are engaged in the N1 basic mode and controlling to a selected N1 limit defined by bits 18 thru 22. The automatic throttles are engaged in the retard control mode. The automatic throttles are engaged in the EPR basic mode and controlling to a selected EPR limit defined by bits 18 thru 22. Used with bit 16 or 17. Used with bit 23. PERF CLP SPD APR 13 14 15 16 LIM FLP SLT N1 17 EPR 18 19 20 21 22 23 TO FLX MCT CLB CR VNV 24 25 26 27 28 29 IAS MACH ALT TRK RTD MIN . The N1 or EPR maximum continuous thrust limit is currently in effect. Used with bit 23. Automatic throttle control is currently limited by flap or slat maximum speeds. The automatic throttles are engaged in the speed select control mode. Used with bit 16 or 17. 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. Also used with bit 13 and with bit 23 as the second word. 16 and 17. Used with Bit 16 or 17. The altitude hold submode the VNV basic mode is currently in effect. Used with bit 23. Used with bit 16 or 17. The automatic throttles are engaged in the speed select mode and throttle control is limited by flap or slat maximum speeds. The IAS submode of the VNV basic mode is currently in effect. Also used with bit 13 and with bit 23 as the second word. Used with bit 13 to designate slat limit control currently in effect. Also used with bit 28 for noise abatement annunication. Used with bit 13 to designate flap limit control currently in effect. or by engine limits (N1 or EPR). Used with bit 16 or 17. or by throttle low limit position. The Mach submode of the VNV basic mode is currently in effect. Used with bit 23. 1980 ARINC SPECIFICATION 429 PART 2 . The automatic throttles are engaged in the speed control mode and throttle control is limited to the minimum alpha cruise speed. 1-8 9 10 11 12 Function Label 272 01 The performance submode of the VNV basic mode is in effect. or by engine limits (N1 or EPR). The N1 or EPR climb thrust limit is currently in effect.Page 54 DATA STANDARDS AUTOMATIC THROTTLE MODES EXPLANATIONS Bit No. Used with bit 23. Also used with bit 18 for noise or abatement annunciation. The climb (descent) path track submode of the VNV basic mode is currently in effect.

Page 55 DATA STANDARDS Label 272 002 .REVISED: July 1. Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 272 002 X X X X X X SDI BIT 0 SDI BIT 1 Enable Climb Rate Performance Limit 100 200 400 800 1600 3200 0 Pad 1500 FPM Climb Limit 2500 FPM Climb Limit SSM Parity (Odd) Cannot Climb Cannot Climb Can Climb Can Climb . 1990 ARINC SPECIFICATION 429 PART 2 .FMC Discretes Bit Status Bit No.

.REVISED: August 1.Page 56 DATA STANDARDS Label 272 003 . Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 272 003 X X X X X X SDI Automatic Throttle Failure/Warning APR* Flag Engaged Normal Not Engaged 0 Spare SSM Parity (Odd) * The automatic throttles are engaged in the speed select mode and throttle control is to the minimum alpha approach speed. 1980 ARINC SPECIFICATION 429 PART 2 .TCC Discrete Bit Status Bit No.

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 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 X X Label 272 018 X X X X X X TCAS Broadcast Bit 1 MID (Part 1) MID BIT A 1 (MSB) MID BIT A 2 MID BIT A 3 MID BIT A 4 MID BIT A 5 MID BIT A 6 MID BIT A 7 MID BIT A 8 MID BIT A 9 MID BIT A 10 MID BIT A 11 MID BIT A 12 MID BIT A 13 MID BIT A 14 MID BIT A 15 MID BIT A 16 Pad Pad Pad Pad SSM SSM Parity (odd) RF MSG BIT 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 0

Note 1: BIT 9 0 1

TCAS Broadcast Bit MEANING

Coordination Message 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 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 272 01A X X X X X X SDI Pad X X X X Sol Sol Sol Valve Valve Valve On On On Open Open Open Off Off Off Closed X Closed Closed X X X X X X X X 0

TCC Stg 2 TCC Stg 1 TCC Stg 3 TCC Stg 1 Spare TCA-A-Air TCA-B-Air

Spare

SSM 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 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32

X X Label 272 025 X X X X X X SDI

DISPLAY MODE SELECTED (see mode select table)

CP SUM CHECK NAV MODE SELECTED ADF/VOR VECTORS DF-NAV AIDS DF-WAYPOINT DF-ROUTE DATA DF-AIRPORTS MAP ORIENT VOR/ILS ORIENT RA ALERT RESET NAV ORIENT FULL COMPASS ROSE PAD SSM Parity (Odd)

NOT OK SELECTED VECTORS SELECTED SELECTED SELECTED SELECTED TRACK UP TRACK UP RESET TRACK UP FULL ROSE

OK NOT SEL NO VECT NOT SEL NOT SEL NOT SEL NOT SEL HDG UP HDG UP NOT RESET HDG UP EXP ROSE X

Bits 1 1 1 0 0 0 0 0 0 1 2 0 1 0 0 0 0 0 1 3 0 0 1 0 0 0 0 1 4 0 0 0 1 0 0 0 1 5 0 0 0 0 1 0 0 1 6 0 0 0 0 0 1 0

Selected Function

MAP MODE SELECTED VOR MODE SELECTED ILS MODE SELECTED PLAN MODE SELECTED VOR FULL SELECTED ILS FULL SELECTED 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 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 272 02F X X X X X SDI Pad Pad Pad N1 Loop N2 Loop N2 Topping Loop PB Topping Loop PB Topping Loop Minimum EPR Loop Accel Schedule Loop Decel Schedule Loop Spare Back Up Mode 2.5 BLD 2-Position Mode Spare Spare Spare Spare Spare SSM Parity (Odd) X X X X X Engaged Engaged Engaged Engaged Engaged Engaged Engaged Engaged X Engaged Engaged X X X X X X 0

Engaged Engaged Engaged Engaged Engaged Engaged Engaged Engaged Engaged Engaged

Not Not Not Not Not Not Not Not Not Not

NOTE:

Typical discrete functions are shown in the above table. according to the specific application.

Slight variations of bit usage may arise

REVISED: July 22, 1988 ARINC SPECIFICATION 429 PART 2 - Page 61 DATA STANDARDS Label 272 03A

Bit Status Bit No. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 272 03A X X X X X X SDI RAM In-Flight Monitor ROM In-Flight Monitor WDT In-Flight Monitor Discrete Output 1 IFM Discrete Output 1 IFM Serial Data Input - Pri Serial Data Input - Sec Spare Discrete Input IFM Power Up RAM BIT:RAM BIT:ROM BIT:Discrete Output 1 BIT:Discrete Output 2(Prov) BIT:Discrete Input BIT: Serial Data BIT:Watchdog Timer Spare Spare SSM Parity (Odd) Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed OK OK OK OK OK OK OK X OK OK OK OK OK OK OK OK OK X X 0

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 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 272 03B X X X X X X SDI Trim Wheel Enable Altitude Select Capture Flare Arm Flare Engage Glide Slope Arm Glide Slope Engage Go-Around Engage Heading Select Nav Engage Localizer Capture Enabled Engaged Armed Engaged Armed Engaged Engaged Selected Engaged Engaged Not Not Not Not Not Not Not Not Not Not Enabled Engaged Armed Engaged Armed Engaged Engaged Selected Engaged Engaged 0

Spare (all "0" states)

Word Validity SSM Parity (Odd)

Invalid

Valid

REVISED: November 17, 1986 ARINC SPECIFICATION 429 PART 2 - Page 63 DATA STANDARDS Label 272 03F

Bit Status Bit No. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 272 03F X X X X X SDI Pad Pad Pad N1 Loop N2 Loop N2 Topping Loop PB Topping Loop PB Topping Loop Minimum EPR Loop Accel Schedule Loop Decel Schedule Loop Spare Back Up Mode 2.5 BLD 2-Position Mode Spare Spare Spare Spare Spare SSM Parity (Odd) X X X X X Engaged Engaged Engaged Engaged Engaged Engaged Engaged Engaged X Engaged Engaged X X X X X X 0

Engaged Engaged Engaged Engaged Engaged Engaged Engaged Engaged Engaged Engaged

Not Not Not Not Not Not Not Not Not Not

NOTE:

Typical discrete functions are shown in the above table. according to the specific application.

Slight variations of bit usage may arise

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 1 2 3 4 5 6 7 8 9 10 11 12 13-14 15-16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X 272 05A (Fuel Density) X X X X X X SDI 0

0.1 pf

1 pf

10 pf

100 pf probe number (units) probe number (units) SSM 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 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 273 001 X X X X X X Unassigned Unassigned Test ALT FMC LNAV VNAV LOC Back Course Appr. 2 Land 2 Land 1 Land 3 Glideslope VOR Climb Descent Unassigned 0

Requested Armed Armed Armed Armed Engaged Engaged Engaged Engaged Armed Armed Armed Armed Armed Armed

Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not

Requested Armed Armed Armed Armed Engaged Engaged Engaged Engaged Armed Armed Armed Armed Armed Armed

SSM Parity (Odd)

ADDED: August 1, 1980 ARINC SPECIFICATION 429 PART 2 - Page 66 DATA STANDARDS ARM MODES EXPLANATIONS

Bit No. 1-8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26-29 Label 273 001

Function

TEST ALT FMC LNAV VNAV LOC BACK COURSE APPR LAND 2 LAND 1 LAND 3 GLIDE SLOPE VOR CLIMB DESCENT TBD

A test of interfacing systems has been requested. The latitude preselect mode has been armed. The lateral and vertical navigation modes of the flight management system have been armed. The lateral navigation submode of the FMS is armed. The vertical navigation submode of the FMS is armed. The localizer mode has been armed. The localizer back course mode has been armed. The approach mode has been armed. The autoland mode is armed on FCC No. 2. The autoland mode is armed on FCC No. 1. The autoland mode is armed on FCC No. 3. The glideslope mode has been armed. The VOR mode has been armed. The climb submode of the VNV basic mode is armed. The Descent submode of the VNV basic mode is armed.

ADDED: August 1, 1980 ARINC SPECIFICATION 429 PART 2 - Page 67 DATA STANDARDS Label 273 003 - TCC Discrete

Bit Status Bit No. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 273 003 X X X X X X SDI No bleed air One air conditioning pack Two air conditioning packs Three air conditioning packs Half wing anti-icing Total wing anti-icing Engine cowling anti-icing Engine operting condition (Engine Out) Speed brake Position - retract Speed brake Position - 1/3 Speed brake Position - 2/3 Speed brake Position - full Landing gear position Slat position - retract Slat position - take off Slat position - land Electronic Engine Control On-Off No. 1 Electronic Engine Control On-Off No. 2 Electronic Engine Control On-Off No. 3 SSM Parity (Odd) Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested On On On Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not Off Off Off Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested 0

Bus 1 Word 3 Bit Status Bit No. 22 23 24 25 0 0 0 0 0 0 0 0 1 0 0 0 0 1 1 1 1 0 to 1 1 1 1 1 1 0 1 0 0 1 1 0 0 1 1 0 0 1 0 1 0 1 0 1 0 SLC SLC SLC SLC SLC SLC SLC SLC 0 1 2 3 4 5 6 7 Not Assigned Cancel previous level command . 1990 ARINC SPECIFICATION 429 PART 2 .Page 68 DATA STANDARDS Label 273 018 . IIS) Word Transponder To TCAS .ADDED: July 1.TCAS Mode S Ground Uplink (SLC. The normal ARINC 429 protocol calls for the transmission of the LSB of the field first. Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 X X Label 273 018 X X X X X X 0 Pad SLC (MSB) 1 2 (LSB) 3 IIS 2 SSM SSM Parity (odd) RF MSG BIT 41 42 43 44 17 18 19 20 Note 1: BITS Sensitivity Level Command (SLC) MEANING NOTE 2: This data is received from the ground station in data words UF 20 & UF 21. 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.

2 Bit No.Discrete Data No. 1996 ARINC SPECIFICATION 429 PART 2 .Page 69 DATA STANDARDS Label 273 025 . Function Bit Status 1 0 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 273 025 X X X X X X SDI PITCH REF FLIGHT PATH DATA PAD FPA DISABLE WEATHER RADAR DATA SELECT RANGE SELECTED ON OFF SEL OFF X ON NOT SEL (see range table) SSM Parity (Odd) Bits 2 4 1 0 0 0 0 0 0 2 5 0 1 0 0 0 0 0 2 6 0 0 1 0 0 0 0 2 7 0 0 0 1 0 0 0 2 8 0 0 0 0 1 0 0 2 9 0 0 0 0 0 1 0 Range Selected 5 MILES (not used) 10 MILES 20 MILES 40 MILES 80 MILES 160 MILES 320 MILES (All other bit patterns are considered invalid) .ADDED: MARCH 6.

9 Interface Failed Tfuel/Toil Interface Failed A/D Interface Failed RES/LVDT Interface Failed SVA Interface Failed N1 Interface Failed N2 Interface Failed P4. Secondary channel uses Pamb X X X X OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK Executing X 0 NOTE: Typical discrete functions are shown in the above table.9 Sensor PROM Failed P2 (Pamb) Sensor PROM* Failed PB Sensor PROM Failed Background Execution Not Executing SSM Parity (Odd) Primary channel uses P2. Slight variations of bit usage may arise . according to the specific application. 1986 ARINC SPECIFICATION 429 PART 2 .9 Interface Failed PB Interface Failed P2 (Pamb) Interface* Failed CJC Interface Failed T2 Interface Failed T4.Page 70 DATA STANDARDS Label 273 02F Bit Status Bit No.REVISED: November 17. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 * X X Label 273 02F X X X X X X SDI Pad P4.

RAC) TCAS To Transponder And Displays . .ADDED: July 1.Page 71 DATA STANDARDS Label 273 035 TCAS Output Discrete (ARA. Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 X X Label 273 035 X X X X X X Pad RF MSG BIT 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 0 ARA 1 RAC 1 SSM SSM Parity (Odd) NOTE 1: Sent by own transponder in DF 16.Bus 2 Word 1 Bit Status Bit No. 1990 ARINC SPECIFICATION 429 PART 2 . 20 and 21.

1983 ARINC SPECIFICATION 429 PART 2 .Page 72 DATA STANDARDS Label 273 03B Bit Status Bit No. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 273 03B X X X X X X SDI A/P Red Warning Lights A/P Servo System Pitch/Roll A/P Servo System Yaw A/P Camout Pitch A/P Camout Roll A/P Camout Yaw A/P Confidence Test Spare (Pad Bit) Spare (Pad Bit) A/T Red Warning Lights A/T Speed Flag Warn Failed Failed Camout Camout Camout Failed Normal Normal Normal Normal Normal Normal Passed X X Normal Normal 0 Warn Flag Spare (all "0" states) Word Validity SSM Parity (Odd) Invalid Valid .ADDED: January 3.

9 Interface Failed Tfuel/Toil Interface Failed A/D Interface Failed RES/LVDT Interface Failed SVA Interface Failed N1 Interface Failed N2 Interface Failed P4. according to the specific application.REVISED: November 17. Secondary channel uses Pamb X X X X OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK Executing X 0 NOTE: Typical discrete functions are shown in the above table.9 Interface Failed PB Interface Failed P2 (Pamb) Interface* Failed CJC Interface Failed T2 Interface Failed T4.9 Sensor PROM Failed P2 (Pamb) Sensor PROM* Failed PB Sensor PROM Failed Background Execution Not Executing SSM Parity (Odd) Primary channel uses P2.Page 73 DATA STANDARDS Label 273 03F Bit Status Bit No. 1986 ARINC SPECIFICATION 429 PART 2 . Slight variations of bit usage may arise . Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 * X X Label 273 03F X X X X X X SDI Pad P4.

.Page 74 DATA STANDARDS Label 273 05A .1 pf 1 pf 10 pf 100 pf probe number (units) probe number (units) SSM Parity NOTE: Typical discrete functions are shown in the above table. 1988 ARINC SPECIFICATION 429 PART 2 .(A-320) FQS .REVISED: July 22.Right Wing Bit Status Bit No. Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13-14 15-16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X 273 05A (Right Wing) X X X X X X SDI 0 0. Slight variations of bit usage may arise according to the specific application.

Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 274 001 X X X X X X Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested 0 Descent Climb IAS VNAV ALT V/S Flare Pitch G/A Pitch T/O Mach Glideslope Flap Speed Min Speed Track Pitch Limit Turb. CWS Hold Performance Pitch Capture SSM Parity Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not Not .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.

The "Altitude" reference mode is selected. 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 IAS VNAV ALT V/S FLARE PITCH G/A PITCH T/O MACH GLIDE SLOPE FLAP SPEED MIN SPEED TRACK PITCH LIMIT TURB CWS HOLD PERFORMANCE PITCH CAPTURE Function The "Airspeed" reference mode is selected. The aircraft pitch attitude is veing controlled to the maximum value. 1980 ARINC SPECIFICATION 429 PART 2 . The "Flare" phase of the autoland mode is engaged. The Pitch Axis "Go Around" mode is engaged. The aircraft is holding a preselected value of altitude. The Pitch Attitude Mode is selected. The "Glideslope" guidance mode is selected. The "Mach" reference speed mode is selected. The "Track" phase of the selected mode is engaged. attitude or speed. The "Capture" phase of the selected mode is engaged. The pitch axis "Vertical Navigation" mode is selected. The pitch axis "Turbulence" penetration mode is engaged. The aircraft is being controlled to a speed which is limited by the flap setting. The aircraft is being controlled to the minimum speed for its configuration. The pitch axis is engaged in the "CWS" mode. The Pitch Axis is engaged in the "Take Off" mode. The "Performance" submode of the Flight Management Vertical Navigation mode is engaged. .Page 76 DATA STANDARDS PITCH MODES EXPLANATIONS Bit No.ADDED: August 1. The "Vertical Speed" reference mode is selected.

SSM Parity Armed Engaged OFF Armed Engaged Off Off Off Engaged Engaged Engaged Engaged Engaged Engaged In Effect In Effect In Effect In Effect Activated Activated In Effect Not Not Not Not Not Not Engaged Engaged Engaged Engaged Engaged In Effect Not In Effect Not In Effect Not In Effect Not Activated Not Activated Not In Effect . Used with bit 17. The altitude hold submode of VNV basic mode is currently in effect.ADDED: August 1.Page 77 DATA STANDARDS Label 274 003 . 1980 ARINC SPECIFICATION 429 PART 2 . Used with bit 17. Used with bit 17. The Mach submode of VNV basic mode currently in effect. Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 X X Label 274 003 X X X X X X Not Armed Not Engaged Passive Passive Passive Passive Passive Passive Not Engaged 0 VNV 18 19 20 21 22 23 24 25 26 27 28 29 IAS MACH ALT TRK ATS ATS PERF 30-31 32 DFA Mode Armed DFA Mode Engaged ATS OFF ATS Armed ATS Mode Engaged Left Clutch Off Right Clutch Off Both Clutches Off The automatic throttles are engaged in the vertical navigation mode and controlling in accordance with a submode designated by bits 23 thru 26 and 29. The climb (descent) path-track submode of the VNV basic mode is currently in effect. ATS N1/EPR Mode Engaged EPR ATS Mach Mode Engaged ATS Speed Mode Engaged ATS Retard Activated The IAS submode of VNV basic mode currently in effect. Used with bit 17.TCC Discrete Bit Status Bit No. Used with bit 17. Alpha Mode Activated Throttle Pusher Activated (Alpha Floor Protection) The Performance submode of the VNV basic mode is in effect.

ADDED: July 1. .TCAS Coordination Discrete (MID Part 2) Transponder To TCAS . Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 X X Label 274 018 X X X X 0 X X MID (Part 2) MID BIT A17 MID BIT A18 MID BIT A19 MID BIT A20 MID BIT A21 MID BIT A22 MID BIT A23 MID BIT A24 Pad Pad Pad Pad Pad Pad Pad Pad Pad Pad Pad Pad Pad SSM SSM Parity (odd) (LSB) RF MSG BIT 81 82 83 84 85 86 87 88 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.Bus 1 Word 8 Bit Status Bit No. 1990 ARINC SPECIFICATION 429 PART 2 . Normal ARINC 429 protocol calls for the transmission of the LSB of the field first.Page 78 DATA STANDARDS Label 274 018 .

REVISED: November 11. Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 X X Label 274 02F X X X X X X X X X X X Error Failed Failed Failed Failed Incorrect Error Failed Yes Yes Yes Failed Yes Failed Failed OK OK OK OK OK Correct OK X OK No No No OK No OK OK X X 0 SDI SDI PAD Parity Test Hardware ROM Checksum RAM Test Instruction Test High Speed Cross Link Text Foreground Software Execution Watchdog Timer Spare EAROM ROM Parity Error Caused Reset RAM Parity Error Caused Reset Watchdog Timer Error Caused Reset Status Buffer Loss of Clock Caused Reset SDD Output #1 W/A SDD Output #2 W/A SSM SSM Parity (Odd) NOTE: Typical discrete functions are shown in the above table. . Slight variations of bit usage may arise according to the specific application. 1986 ARINC SPECIFICATION 429 PART 2 .Page 79 DATA STANDARDS Label 274 02F Bit Status Bit No.

Bus 2 Word 2 Bit Status Bit No. Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 X X Label 274 035 X X X X X X 0 Pad SL SL SL R1 R1 R1 R1 SSM SSM Parity (odd) (MSB) 1 2 (MSB) 2 1 RF MSG BIT 9 10 11 14 15 16 17 NOTE 1: NOTE 2: Sent by own transponder in data word DF. 0. 16. R1) TCAS To Transponder And Displays . 1990 ARINC SPECIFICATION 429 PART 2 . Normal ARINC 429 protocol s c l a for the transmission of the LSB of the field first. .TCAS Output Discrete (SL.Page 80 DATA STANDARDS Label 274 035 . 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.ADDED: July 1.

Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 274 03B X X X SDI Magnetic Heading Flag Localizer Flag Glide Slope Flag Low Range Radio Altimeter ILS Limit Warn ILS Frequency Select INS Altitude Secondary Flags INS True Heading Flags INS HSI Nav Warn CADC True Airspeed Flags CADC Computer Airspeed Flags CADC Corrected Altitude Flags CADC Uncorrected Altitude Flag CADC Mach Flag Altitude Rate Module Flag Spare (Pad Bit) Spare (Pad Bit) Spare (Pad Bit) Word Validity SSM Parity (Odd) Flag Flag Flag Flag Warn Selected Flag Flag Warn Flag Flag Flag Flag Flag Flag Normal Normal Normal Normal Not Selected Normal Normal Normal Normal Normal Normal Normal Normal Normal Normal X X X Valid X X X 0 Invalid .Page 81 DATA STANDARDS Label 274 03B Bit Status Bit No. 1982 ARINC SPECIFICATION 429 PART 2 .ADDED: January 22.

REVISED: November 17. Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 X X Label 274 03F X X X X X X X X X X X Error Failed Failed Failed Failed Incorrect Error Failed Yes Yes Yes Failed Yes Failed Failed OK OK OK OK OK Correct OK X OK No No No OK No OK OK X X 0 SDI SDI PAD Parity Test Hardware ROM Checksum RAM Test Instruction Test High Speed Cross Link Text Foreground Software Execution Watchdog timer Spare EAHOM ROM Parity Error Caused Reset RAM Parity Error caused Reset Watchdog Timer Error Caused Reset Status Buffer Loss of Clock Caused Reset SDD Output #1 W/A SDD Output #2 W/A SSM SSM Parity (Odd) NOTE: Typical discrete functions are shown in the above table. 1986 ARINC SPECIFICATION 429 PART 2 .Page 82 DATA STANDARDS Label 274 03F Bit Status Bit No. Slight variations of bit usage may arise according to the specific application. .

.Center Bit Status Bit No.Page 83 DATA STANDARDS Label 274 05A . Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13-14 15-16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X 274 05A (Center) X X X X X X SDI 0 0.(A-320) FQS . 1996 ARINC SPECIFICATION 429 PART 2 .1 pf 1 pf 10 pf 100 pf probe number (units) probe number (units) SSM Parity NOTE: Typical discrete functions are shown in the above table.ADDED: MARCH 6. Slight variations of bit usage may arise according to the specific application.

Page 84 DATA STANDARDS Label 274 0C5 . Function 1 1-8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23-29 23-29 23-29 23-29 23-29 23-29 23-29 30-31 30-31 32 Label 274 0C5 SDI Spare Spare Spare Spare Spare Spare BARO SEL IN BARO SEL HPA BARO SEL MTRS FPV METRIC ALT WXR DATA MAP RANGE MAP RANGE MAP RANGE MAP RANGE MAP RANGE MAP RANGE MAP RANGE SSM SSM Parity (Odd) 0 SEL SEL SEL SEL SEL SEL SEL SEL SEL SEL SEL SEL SEL NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT SEL SEL SEL SEL SEL SEL SEL SEL SEL SEL SEL SEL SEL MAP RANGE MATRIX BIT POSITIONS 29 0 0 0 0 0 1 0 0 28 0 0 0 0 1 0 0 0 27 0 0 0 1 0 0 0 0 26 0 0 1 0 0 0 0 0 25 0 1 0 0 0 0 0 0 24 1 0 0 0 0 0 0 0 23 0 0 0 0 0 0 0 1 RANGE 5 MILES 10 20 40 80 160 320 640 SSM MATRIX BIT POSITIONS 31 0 0 30 0 1 VALID DATA (WXR) INVALID DATA (WXR) .EFIS CP ENCODING Bit No. 1988 ARINC SPECIFICATION 429 PART 2 .ADDED: July 22.

1980 ARINC SPECIFICATION 429 PART 2 .FCC Roll Modes Discrete Word Bit Status Bit No. Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 275 001 X X X X X X Unassigned Unassigned LNAV HDG HOLD HDG SEL B/COURSE VOR LOC ROLLOUT ROLL T. ROLL G/A Unassigned WINGS LEVEL CAPTURE VOR TRACK Unassigned 0 Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Not Not Not Not Not Not Not Not Not Not Not Not Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested Requested ALIGN CWS SSM Parity Requested Requested Not Requested Not Requested .Page 85 DATA STANDARDS Label 275 001 .ADDED: August 1.O.

"Heading Hold" mode is engaged. 11 12 13 14 15 16 17 18 20 21 22 23 28 29 LNAV HDG HOLD HDG SEL B/COURSE VOR LOC ROLL OUT ROLL T. Roll Axis "Turbulence" penetration mode is engaged.Page 86 DATA STANDARDS ROLL MODES EXPLANATIONS Bit No.ADDED: August 1. "Align" phase of the autoland mode is engaged. 1980 ARINC SPECIFICATION 429 PART 2 . . "Track" phase of the selected mode is engaged. "Heading Select" mode is engaged. "Capture" phase of the selected mode is engaged. Roll Axis "Take Off" mode is engaged. Roll Axis "CWS" mode is engaged. ROLL G/A WINGS LEVEL CAPTURE VOR TRACK ALIGN CWS The The The The The The The The The The The The The The Function "Lateral Navigation" mode is selected. Roll Axis "Go Around" mode is engaged. "Localizer" guidance mode is selected.O. "Roll Out" phase of the autoland mode is engaged. "Backcourse" or "VOR" mode is selected. "VOR" mode is selected.

SSM Parity High High High High High In Effect Low Low Low Low Low Not In Effect 0 17 18 19 20 21 22 23 24 25 26 FLP Engaged Engaged Engaged Engaged Engaged Engaged In Effect Not Not Not Not Not Not Not Engaged Engaged Engaged Engaged Engaged Engaged In Effect SLT N1 In Effect Engaged Not In Effect Not Engaged 27 28 29 Test Engaged Normal Not Engaged EPR 30-31 32 . Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 LIM X X Label 275 003 X X X X X X SDI Engine Type 1 Engine Type 2 Engine Type 3 Encoded to define one of 32 types Engine Type 4 Engine Type 5 Automatic throttle control is currently limited by flap or slat maximum speeds. TO Mode Engaged FLX TO Mode Engaged Climb Mode Engaged Cruise Mode Engaged Maximum Continuous Thrust Mode Engaged GA Mode Engaged Used with bit 16 to designate flap limit control. or by throttle low limit protection. N1/EPR Limit Failure/Warning Used with bit 16 to designate slat limit. Also used with bit 16.Page 87 DATA STANDARDS Label 275 003 . 1980 ARINC SPECIFICATION 429 PART 2 . Test Spare The automatic throttles are engaged in the EPR basic mode and control to a selected N1 limit defined by bits 17 thru 22.TCC Discrete Bit Status Bit No. Also used with bit 16. or by engine limits (N1 or EPR). The automatic throttles are engaged in the N1 basic mode and control to a selected N1 limit defined by bits 17 thru 22. currently in effect.REVISED: August 1.

Bus 1 Word 5 Bit Status Bit No.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 . Normal ARINC 429 protocol s c l a for the transmission of the LSB of the field first. Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 X X Label 275 018 X X X X X X 0 Pad 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 BIT A1 BIT A2 BIT A3 BIT A4 BIT A5 BIT A6 BIT A7 BIT A8 BIT A9 BIT A10 BIT A11 BIT A12 BIT A13 BIT A14 BIT A15 BIT A16 SSM Parity (odd) Mode S Address (Part 1) (MSB) 1 2 (LSB) NOTE 1: NOTE 2: Sent by own TCAS in data word UF-16. . 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.

Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 * ** X X Label 275 02F X X X X X X SDI PAD Lamp 1. Primary channel uses P2: Secondary channel uses Pamb OK Agree OK OK OK OK OK OK OK OK OK Agree OK OK OK X X X X X X 0 NOTE: Typical discrete functions are shown in the above table.Page 89 DATA STANDARDS Label 275 02F Bit Status Bit No.9 Sensor Failed P2 P(amb)** Sensor Failed PBSensor Crosscheck* Failed P4.9 Sensor Crosscheck* Failed Serial Data Receiver Failed Serial Data Transmitter Failed Activity Monitor Failed Other Channel’s Depower Logic Failed Pressure Sensors Correlation Disagree PB Heater Failed Automatic Channel Transfer* Failed Pamb Sensor Drift* Failed Spare SSM Parity (Odd) Primary channel only.REVISED: November 17.2 &/or 3 W/A Failed Other Channel’s Depower Discretes Disagree PB Sensor Failed P4. . 1986 ARINC SPECIFICATION 429 PART 2 . Slight variations of bit usage may arise according to the specific application.

Acknowledgement (ACK/NAK) Discrete TCAS To Transponder . 1990 ARINC SPECIFICATION 429 PART 2 . Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 X X Label 275 035 X X X X X X 0 Pad ACK/NAK SSM SSM Parity (Odd) ACK NAK .Bus 2 Word 3 Bit Status Bit No.ADDED: July 1.Page 90 DATA STANDARDS Label 275 035 .

Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 275 03B X X X X X X SDI A/T A/T A/T A/T A/T A/T A/T A/T A/T A/T A/T Engage Alternate Rating I Alternate Rating II Alpha Flag Limit Retard Mach Speed EPR Throttle Hold Go Around Engage Engage Engage Engage Engage Engage Engage Engage Engage Engage Engage Not Not Not Not Not Not Not Not Not Not Not Engaged Engaged Engaged Engaged Engaged Engaged Engaged Engaged Engaged Engaged Engaged 0 Spare (all "0" states) Word Validity SSM Parity (Odd) Invalid Valid .Page 91 DATA STANDARDS Label 275 03B Bit Status Bit No. 1986 ARINC SPECIFICATION 429 PART 2 .REVISED: November 17.

Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 * ** X X Label 275 03F X X X X X X SDI PAD Lamp 1.Page 92 DATA STANDARDS Label 275 03F Bit Status Bit No.9 Sensor Crosscheck* Failed Serial Data Receiver Failed Serial Data Transmitter Failed Activity Monitor Failed Other Channel’s Depower Logic Failed Pressure Sensors Correlation Disagree PB Heater Failed Automatic Channel Transfer* Failed Pamb Sensor Drift* Failed Spare SSM Parity (Odd) Primary channel only. 1986 ARINC SPECIFICATION 429 PART 2 .2 &/or 3 W/A Failed Other Channel’s Depower Discretes Disagree PB Sensor Failed P4.REVISED: November 17. Slight variations of bit usage may arise according to the specific application. Primary channel uses P2: Secondary channel uses Pamb OK Agree OK OK OK OK OK OK OK OK OK Agree OK OK OK X X X X X X 0 NOTE: Typical discrete functions are shown in the above table. .9 Sensor Failed P2 P(amb)** Sensor Failed PBSensor Crosscheck* Failed P4.

ADDED: MARCH 6.Page 93 DATA STANDARDS Label 275 05A .Left Wing Bit Status Bit No. 1996 ARINC SPECIFICATION 429 PART 2 . .(A-320) FQS . Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13-14 15-16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X 275 05A (Left Wing) X X X X X X SDI 0 0. Slight variations of bit usage may arise according to the specific application.1 pf 1 pf 10 pf 100 pf probe number (units) probe number (units) SSM Parity NOTE: Typical discrete functions are shown in the above table.

TCAS Control Discrete (Mode S Address Part 2. 1990 ARINC SPECIFICATION 429 PART 2 . Normal ARINC 429 protocol s c l a for the transmission of the LSB of the field first. . Function 1 1 2 3 4 5 6 7 8 9 10 11 12 X X Label 276 018 X X X X X Aural Advisory Cancel and Visual Annunciator R1 Echo 1 Pad Pad Mode S Address (Part 2) (MSB) BIT A17 BIT A18 BIT A19 2 BIT A20 BIT A21 3 BIT A22 BIT A23 BIT A24 (LSB) (MSB) Maximum Airspeed 3 (LSB) Pad Pad Pad Pad Pad SSM SSM Parity (odd) Cancel Normal 0 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 RF MSG BIT 81 82 83 84 85 86 87 88 14 15 16 17 NOTE 1: NOTE 2: NOTE 3: See Attachment 12 of ARINC Characteristic 735 for logic encoding of the R1 field.ADDED: July 1.Page 94 DATA STANDARDS Label 276 018 .Bus 1 Word 6 Bit Status Bit No. 16. Max A/S) Transponder To TCAS . 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. Sent by own transponder in DF-0.

Page 95 DATA STANDARDS Label 276 025 . 1996 ARINC SPECIFICATION 429 PART 2 . Function Bit Status 1 0 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X Label 276 025 X X X X X X SDI RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED PAD PAD PAD SSM Parity (Odd) X X X .Discrete Status 8 EFIS Bit No.ADDED: MARCH 6.

5 Bleed Functions W/A Spare Spare Spare Spare Spare EEC Temperature Status Overspeed Test** SSM Parity (Odd) Second channel only. . Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 ** X X Label 276 02F X X X X X X X X X Failed Failed Failed OK OK OK X X Failed Failed Failed Failed OK OK OK OK X X X X X High Failed OK OK X 0 SDI PAD EEC Channel EEC Unit Resolver/ LVDT Excitation Spare Spare FCU Functions HCC Functions LCC Functions 2. NOTE: Typical discrete functions are shown in the above table.REVISED: November 17. 1986 ARINC SPECIFICATION 429 PART 2 .Page 96 DATA STANDARDS Label 276 02F Bit Status Bit No. Slight variations of bit usage may arise according to the specific application.

. NOTE: Typical discrete functions are shown in the above table.REVISED: November 17. 1986 ARINC SPECIFICATION 429 PART 2 .5 Bleed Functions W/A Spare Spare Spare Spare Spare EEC Temperature Status Overspeed Test** SSM Parity (Odd) Second channel only. Slight variations of bit usage may arise according to the specific application. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 ** X X Label 276 03F X X X X X X X X X Failed Failed Failed OK OK OK X X Failed Failed Failed Failed OK OK OK OK X X X X X High Failed OK OK X 0 SDI PAD EEC Channel EEC Unit Resolver/ LVDT Excitation Spare Spare FCU Functions HCC Functions LCC Functions 2.Page 97 DATA STANDARDS Label 276 03F Bit Status Bit No.

Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 X X Label 277 018 X X X X X X 0 Pad ACK/NAK SSM SSM Parity (Odd) ACK NAK . 1990 ARINC SPECIFICATION 429 PART 2 .Bus 1 Word 7 Bit Status Bit No.Page 98 ATTACHMENT 2 (cont’d) DATA STANDARDS Label 277 018 .ADDED: July 1.Acknowledgement (ACK/NAK) Discrete Transponder To TCAS .

.

.

Inst. Failed Resol. Good Good Good Good Good Good Good Good Good Good Good X X 0 .ADDED: January 22. Failed Failed Failed Failed Failed Malfunction Leak Required Malfunction Malfunction Inst. Probe Failed Assy. Not Inst.EEC Discrete Bit Status Bit No. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X X Label 350 01A X X X X SDI Pad Pad Pad Pad Connector J2 Connector J5 T2 EGT TLA RPX A Chan SDD In B Chan SDD In Coil Stg I Valve P2 Leak System Trim TCA-A Valve TCA-B Valve Spare SSM Parity (Odd) X X X X Not Inst.Page 101 DATA STANDARDS Label 350 01A . 1982 ARINC SPECIFICATION 429 PART 2 .

MLS Fault Summary Bit Status Bit No.ADDED: July 22. 1988 ARINC SPECIFICATION 429 PART 2 . .Page 102 DATA STANDARDS Label 350 027 . MIL-STD-1553B Input Bus Resv. max. Function 1 1-8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Label (Octal) 350 027 SDI LRU Failure #1 Antenna Failure #2 Antenna Failure #3 Antenna Failure Source Selection Input Data CFDIU Input Bus Battery Low Warning Resv. 250 ms. Synchro Reference Invalid 0 Failure Failure Failure Failure Port A Inactive Inactive Low Inactive Inactive Failure Failure OK OK OK OK Port B OK OK OK OK OK OK OK Bite Test Inhibit Commmand Word Acknowledge SSM SSM Parity (Odd) Inhibit ACK Enable NAK NOTE: Transmission interval min. 50 ms. DME Input Bus Resv. DME Tuning Interface Resv.

REVISED: November 17.5 BLD Feedback Signal HCC Feedback Signal LCC Feedback Signal Reverser Position Signal AOX Feedback Signal Reserved (Spare Feedback Signal) Thrust Lever Position Signal Spare SSM Parity (Odd) NOTE: Typical discrete functions are shown in the above table.9 Signal Tfuel Signal Toil Signal Wf Feedback Signal SVA Feedback Signal 2. . 1986 ARINC SPECIFICATION 429 PART 2 .Page 103 DATA STANDARDS Label 350 02F Bit Status Bit No. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X X Label 350 02F X X X X X X X X Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed OK OK OK OK OK OK OK OK OK OK OK OK OK X OK X X X 0 SDI PAD N1 Signal N2 Signal T2 Signal T4. Slight variations of bit usage may arise according to the specific application.

1 2 3 4 5 6 7 8 9-10 11-28 30-31 32 Function 1 X X X 0 Label 350 03D X X X X X SDI Data Status Matrix Parity (Odd) Bits 10 0 0 1 1 9 0 1 0 1 Engine Engine Engine Engine Data 4 (or All Call) {Not used on 757} 1 (or Engine 1 and 2) 2 3 (or Engine 3 and 4) Bit 11 12 13 *14 **14 15 ***15 16 ***16 17 ***17 *18 **18 *19 **19 *20 **20 21 22 23 24 25 26 27 28 29 Data Signal Conditioner Status N1 Tachometer Signal Loss N2 Tachometer Signal Loss PAD N3 Tachometer Signal Loss Ch A Accelerometer High Noise PAD Ch B Accelerometer High Noise PAD Channel A <> Channel B PAD PAD High Broadband Levels PAD Ch A Accelerometer Low Signal PAD Ch B Accelerometer Low Signal PAD PAD PAD PAD PAD PAD PAD Unit Not Available Command Word Acknowledge * 757 Pratt and Whitney and 737 CFM Only (Reserved) ** 757 Rolls Royce Only *** 757 Only .Page 104 DATA STANDARDS Label 350 03D . 1996 ARINC SPECIFICATION 429 PART 2 .ADDED: MARCH 6.Maintenance Data #1 Bit No.

1986 ARINC SPECIFICATION 429 PART 2. Slight variations of bit usage may arise according to the specific application.REVISED: November 17.5 BLD Feedback Signal HCC Feedback Signal LCC Feedback Signal Reverser Position Signal AOX Feedback Signal Reserved (Spare Feedback Signal) Thrust Lever Position Signal Spare SSM Parity (Odd) NOTE: Typical discrete functions are shown in the above table.Page 105 DATA STANDARDS Label 350 03F Bit Status Bit No.9 Signal Tfuel Signal Toil Signal Wf Feedback Signal SVA Feedback Signal 2. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X X Label 350 03F X X X X X X X X Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed OK OK OK OK OK OK OK OK OK OK OK OK OK X OK X X X 0 SDI PAD N1 Signal N2 Signal T2 Signal T4. .

.

Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 X X X Label 350 114 X X X X SDI X 0 Fuel Density (0. 1990 ARINC SPECIFICATION 429 PART 2 .1’s) Tank Ident SSM SSM Parity (Odd) .Page 107 DATA STANDARDS Label 350 114 .001’s) Fuel Density (0.01’s) Fuel Density (0.Fuel Unit Management System Discrete (A-330/A-340) Bit Status Bit No.ADDED: July 1.0001’s) Fuel Density (0.

ADDED: July 1.TACAN Discrete Bit Status Bit No. .Page 108 DATA STANDARDS Label 350 115 . Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 X X X Label 350 115 X X X X LSB X 0 AGC (X 1/256 FULL SCALE) MSB CPU RAM ROM 2 PORT RAM 2 PORT DATA NOVRAM SYNTHESIZER RECEIVER POWER SUPPLY XMIT POWER AUDIO POWER UP SUPPRESSION D/A TACAN FAIL Parity (Odd) Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Present Failed Failed OK OK OK OK OK OK OK OK OK OK OK OK Not Present OK OK NOTE: Bite 21 thru 28 indicate self test status information. 1990 ARINC SPECIFICATION 429 PART 2 .

ADDED: January 22. 1982 ARINC SPECIFICATION 429 PART 2 .EEC Discrete Bit Status Bit No.Page 109 DATA STANDARDS Label 351 01A . Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X X Label 351 01A X X X X SDI Pad Pad Pad Pad ARINC Transmitter RPX Drift RPX Test TLA Correl Test Resolver Test Resolver Drift Angle Range Check Sine Range Check Cosine Range Check Spare LLDC Test #1 LLDC Drift #1 P2 Range Check (Boeing Only) P7 Range Check EPR Range Check SSM Parity (Odd) X X X X Fail Fail Fail Fail Fail Fail Fail Fail Fail Fail Fail Fail Fail Fail Good Good Good Good Good Good Good Good Good X Good Good Good Good Good X 0 .

5 BLD Track Check HCC Track Check LCC Track Check AOX Track Check Reserved (Spare Track Check) SSM Parity (Odd) Primary channel only.Page 110 DATA STANDARDS Label 351 02F Bit Status Bit No. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 * X X X Label 351 02F X X X X SDI PAD Local ADC Inputs (Pri-Left. Slight variations of bit usage may arise according to the specific application.REVISED: November 17. Sec-Right) Crosstalk ADC Inputs* Wf T/M W/A SVA T/M W/A 2. . 1986 ARINC SPECIFICATION 429 PART 2 . Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed OK OK OK OK OK OK OK OK X OK OK OK OK OK OK X X X X X X X 0 NOTE: Typical discrete functions are shown in the above table.5 BLD T/M W/A HCC T/M W/A LCC T/M W/A AOX T/M W/A Spare Wf Track Check SVA Track Check 2.

Sec-Right) Crosstalk ADC Inputs* Wf T/M W/A SVA T/M W/A 2. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 * X X X Label 351 03F X X X X SDI PAD Local ADC Inputs (Pri-Left. Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed OK OK OK OK OK OK OK OK X OK OK OK OK OK OK X X X X X X X 0 NOTE: Typical discrete functions are shown in the above table.5 BLD Track Check HCC Track Check LCC Track Check AOX Track Check Reserved (Spare Track Check) SSM Parity (Odd) Primary channel only. . 1986 ARINC SPECIFICATION 429 PART 2 . Slight variations of bit usage may arise according to the specific application.REVISED: November 17.Page 111 DATA STANDARDS Label 351 03F Bit Status Bit No.5 BLD T/M W/A HCC T/M W/A LCC T/M W/A AOX T/M W/A Spare Wf Track Check SVA Track Check 2.

.

Fuel Unit Management System Discrete (A-330/A-340) Bit Status Bit No. 1990 ARINC SPECIFICATION 429 PART 2 . Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 X X X X X X X X SDI 0 Label 351 114 (Left Wing) Probe Capacitance (0.1’s) Probe Capacitance (1’s) Probe Capacitance (10’s) Probe Capacitance (100’s) Probe Number (1’s) Probe Number (10’s) SSM SSM Parity (Odd) .Page 113 DATA STANDARDS Label 351 114 .ADDED: July 1.

1982 ARINC SPECIFICATION 429 PART 2 . Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X X Label 352 01A X X X X SDI Pad Pad Pad Pad EGT Loop Sel/Fail N2 P7 Test N2/P2 Test T/M.Page 114 DATA STANDARDS Label 352 01A .ADDED: January 22. D/A or Driver T/M "Undetermined" Pres Temp Inputs Latch Solenoid W/A Health Indicator W/A ROM Sum Test RAM Test Watchdog Timer Instruction Test Watchdog Resets Converter Reset SSM Parity (Odd) X X X X Fail Fail Fail Fail Fail Fail Fail Fail Fail Fail Fail Fail Fail Fail Fail Good Good Good Good Good Good Good Good Good Good Good Good Good Good Good X 0 .EEC Discrete Bit Status Bit No.

Slight variations of bit usage may arise according to the specific application. Discrete Disagreement* Data Entry Plug SSM Parity (Odd) Primary channel only. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 * X X X Label 352 02F X X X SDI PAD DC Power Group 1 DC Power Group 2 Spare EEC to PDIU SDD PDIU Self Test HCC T/M W/A Local TCA Valve (Pri-Left. Sec-Right) Crosstalk TCA Valve Check* Spare SDD Input from PDIU N1 Sensor (Pri and Sec)* PB Pneumatic Line* P4.9 Pneumatic Line* P2 Probe / Line* Fire Warn. 1986 ARINC SPECIFICATION 429 PART 2 .Page 115 DATA STANDARDS Label 352 02F Bit Status Bit No.REVISED: November 17. . Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Disagree Failed OK OK X OK OK OK OK OK X OK OK OK OK OK OK OK X X X X X X X 0 NOTE: Typical discrete functions are shown in the above table.

REVISED: November 17. Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Disagree Failed OK OK X OK OK OK OK OK X OK OK OK OK OK OK OK X X X X X X X 0 NOTE: Typical discrete functions are shown in the above table. 1986 ARINC SPECIFICATION 429 PART 2 .9 Pneumatic Line* P2 Probe / Line* Fire Warn. . Discrete Disagreement* Data Entry Plug SSM Parity (Odd) Primary channel only. Sec-Right) Crosstalk TCA Valve Check* Spare SDD Input from PDIU N1 Sensor (Pri and Sec)* PB Pneumatic Line* P4.Page 116 DATA STANDARDS Label 352 03F Bit Status Bit No. Slight variations of bit usage may arise according to the specific application. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 * X X X Label 352 03F X X X SDI PAD DC Power Group 1 DC Power Group 2 Spare EEC to PDIU SDD PDIU Self Test HCC T/M W/A Local TCA Valve (Pri-Left.

.

Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 X X X X X X X X SDI 0 Label 352 114 (Center/Trim) Probe Capacitance (0.Fuel Unit Management System Discrete (A-330/A-340) Bit Status Bit No.1’s) Probe Capacitance (1’s) Probe Capacitance (10’s) Probe Capacitance (100’s) Probe Number (1’s) Probe Number (10’s) SSM SSM Parity (Odd) .ADDED: July 1. 1990 ARINC SPECIFICATION 429 PART 2 .Page 118 DATA STANDARDS Label 352 114 .

Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X X Label 353 01A X X X X SDI Pad Pad Pad Pad Spare EGT Loop Disabled Synth Altitude Synth Mach Number SDD ’A’ W/A ADD ’B’ W/A Probe Heat (Boeing 767 Only) Pressure Accuracy T/M Coil TCC Schedule (Airbus Acft Pt Used 310.ADDED: January 22.Page 119 DATA STANDARDS Label 353 01A .EEC Discrete Bit Status Bit No. 1982 ARINC SPECIFICATION 429 PART 2 .000 P2 Range Check Only) TCA System TCC System System Trim SSM Parity (Odd) X X X X X Yes Yes Yes Failure Failure Disagreement Degraded Yes Default Yes Failed Failed Failed Required No No No Good Good Normal Normal No Normal No Good Good Good Okay X 0 .

5 BLD Feedback Crosscheck* Failed HCC Feedback Crosscheck* Failed LCC Feedback Crosscheck* Failed Reverser Position Crosscheck* Failed AOX Feedback Crosscheck Failed Thrust Lever Position Crosscheck* Failed SSM Parity (Odd) Primary channel only. Slight variations of bit usage may arise according to the specific application. 1986 ARINC SPECIFICATION 429 PART 2 .REVISED: November 17.Page 120 DATA STANDARDS Label 353 02F Bit Status Bit No. OK OK X X OK OK OK OK OK OK OK OK OK OK OK OK X X X X X X 0 NOTE: Typical discrete functions are shown in the above table. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 * X X X Label 353 02F X X X X SDI PAD N1 Crosscheck* Failed N2 Crosscheck* Failed Spare Spare T2 Crosscheck* Failed T2 Probe/ADC T2 Disagreement Disagree Tfuel Crosscheck* Failed Toil Crosscheck* Failed Wf Feedback Crosscheck* Failed SVA Feedback Crosscheck Failed 2. .

Maintenance Data #4 Highest Vibration Bit No. 1996 ARINC SPECIFICATION 429 PART 2 .Page 121 DATA STANDARDS Label 353 03D . 1 2 3 4 5 6 7 8 9-10 11-12 13 14 15 16 17 18-19 20-28 29-31 32 Function 1 X X X Label 353 03D X X X X SDI Accelerometer Source X X X X X X 0 PADS Data ID Data SSM Parity (Odd) Bits 10 0 0 1 1 9 0 1 0 1 Data Bits 12 11 0 1 0 Data Engine Engine Engine Engine 4 1 2 3 0 0 1 No Channel in commmand Channel A Channel B * Data ID Bits 19 0 0 1 1 18 0 1 0 1 N1 N2 N3 BB Vibration Vibration Vibration Vibration (Label (Label (Label (Label 354) 355) 356) 357) Data * 737 Data ID Bits 19 0 0 1 1 18 0 1 0 1 CN1 CN2 TN1 TN2 Vibration Vibration Vibration Vibration (Label (Label (Label (Label 354) 355) 356) 357) Data .ADDED: MARCH 6.

Page 122 DATA STANDARDS Label 353 03D .ADDED: MARCH 6.01 Range = 0 to 5. 1996 ARINC SPECIFICATION 429 PART 2 .Maintenance Data #4 Highest Vibration (cont’d) * 757 Data ID Bits 19 0 0 1 1 18 0 1 0 1 BB N1 N1 N3 Vibration Vibration Vibration Vibration (Label (Label (Label (Label 357) 354) 355) 356)** Data ** 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.12 Units = Scalar Units SSM Bits 31 1 1 30 0 1 29 0 0 Self Test Normal Operation Data .

Page 123 DATA STANDARDS Label 353 03F Bit Status Bit No. .5 BLD Feedback Crosscheck* Failed HCC Feedback Crosscheck* Failed LCC Feedback Crosscheck* Failed Reverser Position Crosscheck* Failed AOX Feedback Crosscheck Failed Thrust Lever Position Crosscheck* Failed SSM Parity (Odd) Primary channel only.REVISED: November 17. OK OK X X OK OK OK OK OK OK OK OK OK OK OK OK X X X X X X 0 NOTE: Typical discrete functions are shown in the above table. 1986 ARINC SPECIFICATION 429 PART 2 . Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 * X X X Label 353 03F X X X X SDI PAD N1 Crosscheck* Failed N2 Crosscheck* Failed Spare Spare T2 Crosscheck* Failed T2 Probe/ADC T2 Disagreement Disagree Tfuel Crosscheck* Failed Toil Crosscheck* Failed Wf Feedback Crosscheck* Failed SVA Feedback Crosscheck Failed 2. Slight variations of bit usage may arise according to the specific application.

.

1990 ARINC SPECIFICATION 429 PART 2 .Page 125 DATA STANDARDS Label 353 114 .ADDED: July 1.1’s) Probe Capacitance (1’s) Probe Capacitance (10’s) Probe Capacitance (100’s) Probe Number (1’s) Probe Number (10’s) SSM SSM Parity (Odd) .Fuel Unit Management System Discrete (A-330/A-340) Bit Status Bit No. Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 X X X X X X X X SDI 0 Label 353 114 (Right Wing) Probe Capacitance (0.

Page 126 DATA STANDARDS Label 354 01A .EEC Discrete Bit Status Bit No. 1982 ARINC SPECIFICATION 429 PART 2 .ADDED: January 22. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X X Label 354 01A X X X X SDI Pad Pad Pad Pad TPT2 Temp Diode TPT7 Temp Diode T/M W/A’A Range Check T/M W/A’B Range Check Spare Spare LLDC Test #2 LLDC Drift #2 TCC Stage I W/A TCC Stage II W/A TCC Stage III W/A Spare Spare Spare SSM Parity (Odd) X X X X Fail Fail Fail Fail Fail Good Good Good Good Good X X Fail Fail Fail Fail Fail Good Good Good Good X X X X 0 .

Page 127 DATA STANDARDS Label 354 02F Bit Status Bit No. . Slight variations of bit usage may arise according to the specific application.ADDED: November 17. Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X X Label 354 02F X X X X X X X X Failed Failed OK OK X X X Failed OK X X Failed Failed OK X OK X X Tripped Tripped OK OK X X X 0 SDI PAD REV Command Solenoid W/A TCA Solenoid W/A Reserved (Spare Solenoid W/A) Reserved (Spare Solenoid W/A) Reserved (Spare Relay W/A) 14th Stage Bleed T/M W/A Spare Reserved (Spare Solenoid W/A) Oil Bypass Solenoid W/A Reserved (Spare Relay W/A) T/L Interlock Relay W/A Reserved (Spare Relay W/A) Spare Group 1 Overcurrent Sense Group 2 Overcurrent Sense Spare SSM Parity (Odd) NOTE: Typical discrete functions are shown in the above table. 1986 ARINC SPECIFICATION 429 PART 2.

12 Units = Scalar Units .ADDED: MARCH 6.Maintenance Data #5 N1 Vibration Bit No. 1996 ARINC SPECIFICATION 429 PART 2 . 1 2 3 4 5 6 7 8 9-10 11-12 13 14 15 16 17 18 19 20-28 29 30 31 32 Function 1 X X X 0 Label 354 03D X X X X X SDI Accelerometer Source X X X X X X X X SSM (Normal Operation) Parity (Odd) X X PADS Data Bits 10 0 0 1 1 9 0 1 0 1 Data Bits 12 11 0 1 0 Data Engine Engine Engine Engine 4 1 2 3 0 0 1 No Channel in commmand Channel A Channel B 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.Page 128 DATA STANDARDS Label 354 03D .

Function 1 1 2 3 4 5 6 7 8 9-10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30-31 32 X X X Label 354 03F X X X X X X X X Failed Failed OK OK X X X Failed OK X X Failed Failed OK X OK X X Tripped Tripped OK OK X X X 0 SDI PAD REV Command Solenoid W/A TCA Solenoid W/A Reserved (Spare Solenoid W/A) Reserved (Spare Solenoid W/A) Reserved (Spare Relay W/A) 14th Stage Bleed T/M W/A Spare Reserved (Spare Solenoid W/A) Oil Bypass Solenoid W/A Reserved (Spare Relay W/A) T/L Interlock Relay W/A Reserved (Spare Relay W/A) Spare Group 1 Overcurrent Sense Group 2 Overcurrent Sense Spare SSM Parity (Odd) NOTE: Typical discrete functions are shown in the above table. 1986 ARINC SPECIFICATION 429 PART 2 . .Page 129 DATA STANDARDS Label 354 03F Bit Status Bit No.ADDED: November 17. Slight variations of bit usage may arise according to the specific application.

.

Fault Supplement Word for MLS Bit Status Bit No.Page 131 DATA STANDARDS Label 355 027 . . 1988 ARINC SPECIFICATION 429 PART 2. 250 ms.ADDED: July 22. SSM Parity (Odd) NOTE: Transmission interval min. Function 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 0 Label 355 027 SDI BITS 11 thru 29 reserved for Company private use. max. 50 ms.

12 Units = Scalar Units .Page 132 DATA STANDARDS Label 355 03D .Maintenance Data #6 N2 Vibration Bit No.ADDED: MARCH 6. 1996 ARINC SPECIFICATION 429 PART 2 .01 Range = 0 to 5. 1 2 3 4 5 6 7 8 9-10 11-12 13 14 15 16 17 18 19 20-28 29 30 31 32 Function 1 X X X 0 Label 355 03D X X X X X SDI Accelerometer Source X X X X X X X X SSM (Normal Operation) Parity (Odd) X X PADS Data Bits 10 0 0 1 1 9 0 1 0 1 Data Bits 12 11 0 1 0 Data Engine Engine Engine Engine 4 1 2 3 0 0 1 No Channel in commmand Channel A Channel B Bit 28 27 26 25 24 23 22 21 20 MSB <----------------------> LSB Bit Encoding for Vibration Labels Bits = 9 Resolution = 0.

.

12 Units = Scalar Units .N3 Vibration Bit No.Page 134 DATA STANDARDS Label 356 03D .ADDED: MARCH 6. 1 2 3 4 5 6 7 8 9-10 11-12 13 14 15 16 17 18 19 20-28 29 30 31 32 Function 1 X X X Label 356 03D X X X X SDI Accelerometer Source X X X X X X X X SSM (Normal Operation) Parity (Odd) X X X 0 PADS Data Bits 10 0 0 1 1 9 0 1 0 1 Data Bits 12 11 0 1 0 Data Engine Engine Engine Engine 4 1 2 3 0 0 1 No Channel in commmand Channel A Channel B 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. 1996 ARINC SPECIFICATION 429 PART 2 .

Page 135 DATA STANDARDS Label 357 03D . 1996 ARINC SPECIFICATION 429 PART 2 . 1 2 3 4 5 6 7 8 9-10 11-12 13 14 15 16 17 18 19 20-28 29 30 31 32 Function 1 X X X 0 Label 357 03D X X X X SDI Accelerometer Source X PADS X X X X X X X X Data SSM (Normal Operation) Parity (Odd) X X Bits 10 0 0 1 1 9 0 1 0 1 Data Bits 12 11 0 1 0 Data Engine Engine Engine Engine 4 1 2 3 0 0 1 No Channel in commmand Channel A Channel B Bit 28 27 26 25 24 23 22 21 20 MSB <----------------------> LSB Bit Encoding for Vibration Labels Bits = 9 Resolution = 0.BB Vibration Bit No.ADDED: MARCH 6.01 Range = 0 to 5.12 Units = Scalar Units .

.

Page 137 DATA STANDARDS Label 360 03D . 1996 ARINC SPECIFICATION 429 PART 2 .0 Range = 0 to 360 Units = Degrees Bits 31 1 0 1 0 30 0 1 1 0 29 0 0 0 0 Data Functional Test No Computed Data Normal Operation Failure Warning .N1 Rotor Imbalance Angle Bit No. 1 2 3 4 5 6 7 8 9-10 11-12 13 14 15 16 17 18 19 20-28 29-31 32 Function 1 X X X X 0 Label 360 03D X X X X SDI Accelerometer Source X X X X X X X PADS Data SSM Parity (Odd) Bits 10 0 0 1 1 9 0 1 0 1 Data Bits 12 11 0 1 0 Data Engine Engine Engine Engine 4 1 2 3 0 0 1 No Channel in commmand Channel A Channel B Bit 28 27 26 25 24 23 22 21 20 MSB <----------------------> LSB Bit Encoding for Imbalance Angles Bits = 9 Resolution = 1.ADDED: MARCH 6.

0 Range = 0 to 360 Units = Degrees Bits 31 1 0 1 0 30 0 1 1 0 29 0 0 0 0 Data Functional Test No Computed Data Normal Operation Failure Warning * 737 Only . 1 2 3 4 5 6 7 8 9-10 11-12 13 14 15 16 17 18 19 20-28 29-31 32 Function 1 X X X X 0 Label 361 03D X X X X SDI Accelerometer Source X X X X X X X PADS Data SSM Parity (Odd) Bits 10 0 0 1 1 9 0 1 0 1 Data Bits 12 11 0 1 0 Data Engine Engine Engine Engine 4 1 2 3 0 0 1 No Channel in commmand Channel A Channel B Bit 28 27 26 25 24 23 22 21 20 MSB <----------------------> LSB Bit Encoding for Imbalance Angles Bits = 9 Resolution = 1.ADDED: MARCH 6.Page 138 DATA STANDARDS Label 361 03D* . 1996 ARINC SPECIFICATION 429 PART 2 .LPT Rotor Imbalance Angle Bit No.

2001 AN A DOCUMENT Prepared by AIRLINES ELECTRONIC ENGINEERING COMMITTEE Published by AERONAUTICAL RADIO. ANNAPOLIS. INC. 2551 RIVA ROAD.MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS). MARYLAND 21401 . PART 3 FILE DATA TRANSFER TECHNIQUES ARINC SPECIFICATION 429P3-18 PUBLISHED: OCTOBER 12.

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. is made in this regard. and no representation or warranty.This document is based on material submitted by various participants during the drafting process. Any use of or reliance on this document shall constitute an acceptance thereof “as is” and be subject to this disclaimer. express or implied.

1979 November 1. 2001 © Prepared by the Airlines Electronic Engineering Committee Specification 429P3 Specification 429P3 Adopted by the Airlines Electronic Engineering Committee: Adopted by the Industry: Summary of Document Supplements Supplement Specification 429P3-1 Specification 429P3-2 Specification 429P3-3 Specification 429P3-4 Specification 429P3-5 Specification 429P3-6 Specification 429P3-7 Specification 429P3-8 Specification 429P3-9 Specification 429P3-10 Specification 429P3-11 Specification 429P3-12 Specification 429P3-13 Specification 429P3-14 Specification 429P3-15 Specification 429P3-16 Specification 429P3-17 Specification 429P3-18 Adoption Date April 11. 1988 October 25. 1990 December 30. 1984 October 11. 1989 October 8.Copyright 2001 by AERONAUTICAL RADIO. 1988 July 1. Maryland 21401-7465 USA © ARINC SPECIFICATION 429P3-18 MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS) PART 3 FILE DATA TRANSFER TECHNIQUES Published: October 12. 1986 July 22. 1978 August 31. 2551 Riva Road Annapolis. 1981 November 4. 1995 June 24. 2001 Published June 1. 1977 September 15. 1985 November 17. 1993 September 1. 1984 April 30. 1995 June 30. 1999 October 12. INC. 1982 January 3. 1980 April 24. 1991 January 4. . 2001 July 21. 1980 March 12. 1991 November 4. 1984 December 3. 1979 August 1. 1984 November 7. 1981 January 22. 1979 June 17. 1977 A description of the changes introduced by each supplement is included on Goldenrod paper at the end of this document. 1978 December 6. 1997 May 17. 1985 June 15. 1992 April 18. 1981 December 9. 1997 March 31. 1983 November 4. 1999 July 18. 1978 March 1.

coordinated on an industry basis. These general Specifications and Reports may be considered as supplementary to the Equipment Characteristics in which they are referenced. (ARINC) and the Purpose of ARINC Reports and Specifications Aeronautical Radio. the allocation and assignment of frequencies to meet those needs. the fulfillment of systems requirements to accomplish ground and airborne compatibility. (2) ii . airlines. ARINC sponsors the Airlines Electronic Engineering Committee (AEEC). concerning requisites of new equipment. is a corporation in which the United States scheduled airlines are the principal stockholders. the coordination incident to standard airborne communications and electronics systems and the exchange of technical information. construction and test criteria. It is desirable to reference certain general ARINC Specifications or Report which are applicable to more than one type of equipment. 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.S.FOREWORD Activities of AERONAUTICAL RADIO. Inc. composed of airline technical personnel. INC. They are intended to set forth the desires of the airlines pertaining to components and general design. Activities of ARINC include the operation of an extensive system of domestic and overseas aeronautical land radio stations. and 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. the coordination incident to standard airborne compatibility. The establishment of Equipment Characteristics is a principal function of this Committee. which is: (1) To indicate to the prospective manufacturers of airline electronic equipment the considered opinion of the airline technical people. An ARINC Report ( Specification or Characteristic) has a twofold purpose. The AEEC formulates standards for electronic equipment and systems for the airlines. Other stockholders include a variety of other air transport companies. in order to insure satisfactory operation and the necessary interchangeability in airline service. the allocation and assignment of frequencies to meet those needs. aircraft manufacturers and non-U.

18 2.5.1 2.1 2.14.6 1.0 2.5.1 .5.5.5.5.5.2 1.5.5.17.16 2.6 2.1.5.3.7.8 2.13.10.3.5.14.2 1.4 1.5 2.5.5 1.19 2.7.6 2.2 2.13.5.1 2.5.15 2.14.2 2.14 2.3.3.1 2.5.19.3 1.8.3 2.5.1 2.10.2 2.13.3 2.5.5.2 2.2 2.5.19.11 2.2 2.5.8.5.5 2.1 1.Basic Philosophy Data Transfer Broadcast Data File Data Transfer Transmission Order Data Bit Encoding Logic Bit-Oriented Protocol Determination Relationship to Other Standards BIT ORIENTED FILE TRANSFER PROTOCOL Not used to maintain consistency with previous versions of ARINC Specification 429 Bit-Oriented Communications Protocol Link Data Units (LDU) Link Data Unit (LDU) Size and Word Count System Address Labels (SALs) Bit Rate and Word Timing Word Type Protocol Words Protocol Identifier Destination Code Word Count Request To Send (RTS) Clear To Send (CTS) Not Clear To Send (NCTS) Destination Busy (BUSY) No Response to RTS Conflicting RTS Transmissions Half Duplex Mode Full Duplex Mode Unexpected RTS Start Of Transmission (SOT) General Format Identifier (GFI) File Sequence Number LDU Sequence Number Data Full Data Word(s) Partial Data Word(s) End of Transmission (EOT) CRC Encoding CRC Decoding Negative Acknowledgment (NAK) Missing SOT Word Missing EOT Word Parity Errors Word Count Errors CRC Errors Time Out Errors LDU Transfer Acknowledgment (ACK) Duplicate LDU Auto-Synchronized Files Incomplete File timer SYN Word Response to ACK/NAK/SYN Solo Word (Single Word Transfers) Test Word and Loop Word Optional Solo Word Definitions Optional End-To-End Message Verification Protocol Initialization Bit-Oriented Protocol Version ALOHA iii PAGE 1 1 1 1 1 1 1 1 2 2 2 2 3 3 3 4 4 4 4 5 5 5 5 5 5 5 5 6 6 6 6 7 7 7 7 7 7 7 7 8 8 8 8 9 9 9 9 9 9 9 9 9 9 10 10 10 10 11 11 11 11 11 11 .1 1.3 2.9 2.5.7.5.5.5.5.12.3 2.5.11.4 2.5.5.5.1 2.4 2.13.5.1 2.7.5.6.13.7 2.17.12 2.5.2.2 2.5.5.4 2.5.ARINC SPECIFICATION 429 PART 3 TABLE OF CONTENTS ITEM 1.12.5.6.1 2.3.4 2.3.2 2.0 1.2 2.13 2.3 2.10.10 2.3.5.5.5 2.5.1 2.3 2.5.1 1.5.5.5.11.4 2.2 2.5.17 2.3 1.5.5.1 SUBJECT INTRODUCTION Purpose of this Document Organization of ARINC Specification 429 Development of Data Transfer File Data Transfer Techniques .13.6.1 2.5.5.1 2.

3.2.5 3.6.1 3.3 3.3.2 2.3.2.2.1.1 3.2.4.3.2.3.3.1 3.2.4.2.2 3.4 3.2.1 3.1 3.2.2.2.2 3.2.2 3.2.19.1 3.3.0 3.1 3.3 3.6 3.3 3.3.2.2.3.4 3.3 3.indication Function Semantics destination MA address destination SAL address source MA address source SAL address m sdu reception status service class When Generated Effect of Receipt MAC Control functions MA CONTROL.2 3.2 3.2 3.2 3.2.2.2.1 3.2.1.request MA CONTROL.2.5.2 3.1.2.2.4.2.4 3.4 3.2.2.1.3.2.1 3.3 3.1.1 3.3.1.2.1 3.2.2.5.3.3.2.2.6.3.2 3.1.2.1 3.5.2.1 3.3.3.2.1 3.3.4.1.4.6 3.6 3.4 3.4 3.4 3.2.2.5 3.3 3.2.3.3.1.4 3.5.2.1.1.19.2.2.2 3.3 3.2.1.3.7 3.5 3.2 3.2.4.3.3.3.2 3.4 3.3 3.2 3.2.3 3.5.2.1.2 3.1 3.1.2.ARINC SPECIFICATION 429 PART 3 TABLE OF CONTENTS ITEM 2.5.3 3.3.3.4.4.3.2.2.2 2.4.3.3 3.2.2.1 3.3.4 3.2.2 SUBJECT ALOHA Response Williamsburg/File Transfer Determination Windowed Bit-Oriented Communications Protocol BIT ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL Bit Oriented Media Access Control (MAC) Protocol Introduction Relationship Between the Version 1 and Version 3 Protocols Protocol Architecture Buffering Media Access Control (MAC) Sublayer MAC Sublayer Service Specification MA DATA request Function Semantics destination MA address destination SAL address m sdu service class When Generated Effect of Receipt MA DATA.1.2.2.indication MAC Frame Structures Information Frame Format Address fields Length/Type Field Length Type Data Field Frame Check Sequence (FCS) Field Validation of Information Frame Invalid Address Invalid Length/Type Invalid FCS Command Frame Format GFI Field Command Type Field Data Field Frame Check Sequence (FCS) Field Validation of Command Frame Invalid FCS MAC Transmit/Receive Functions Frame Data Unit (FDU) Frame Data Unit (FDU) Size and Word Count System Address Labels (SALs) Bit Rate and Word Timing Word Type Start of Frame (SOF) Information/Command (I/C) Frame Field Information SOF word iv PAGE 12 12 13 14 14 14 14 15 15 15 15 16 16 16 16 16 16 16 17 17 17 17 17 17 17 17 17 17 17 17 18 18 18 18 19 19 19 19 19 19 20 20 20 20 20 20 20 20 20 21 21 21 21 21 21 21 21 21 22 22 22 22 22 .5 3.4.3.

9.4 3.3 3.7.2 3.4.12.4.6.3.6.4.2 3.9 3.2 3.ARINC SPECIFICATION 429 PART 3 TABLE OF CONTENTS ITEM 3.13 ATTACHMENTS 1-9 10 11 11A 11B 11C 12 12A 13 13A 14 15 16 17 18 19 20 APPENDICES A-E F G H I J K Letters not used in Part 3 of Specification 429 Former AIM and File Data Transfer Techniques Mathematical Example of CRC Encoding/Decoding Interoperability of Bit-Oriented Link Layer Protocol SDL Diagrams of the Version 1 Williamsburg Protocol Protocol Structure Glossary & Acronyms 60 61 67 71 72 90 93 Numbers not used in Part 3 of Specification 429 Variables of Bit-Oriented Protocol Bit-Oriented Data File Transfer Word Formats Destination Codes Status Codes ALOHA/ALOHA Response Protocol Word Definition Version 1 File Transfer Example Field Mapping Example Protocol Determination Procedure Diagrams ALOHA Version Determination Sequence System Address Labels Deleted by Supplement 16 Deleted by Supplement 16 Flow Diagram Used to Determine Character-Oriented vs Bit-Oriented Protocol MAC Sublayer Support Diagrams Command Frame Data Unit (FDU) Structure and Examples Information Frame Data Unit (FDU) Structure and Example 27 28 35 41 43 44 45 46 47 49 50 51 52 53 54 56 58 SUBJECT Word Count Reserved Bits Command SOF word Word Count Reserved Bits General Format Identifier Field (GFI) Command Type Field (CT) Data Full Data Word(s) Partial Data Word(s) SOLO Words End of Frame (EOF) Frame Check Sequence 32-Bit CRC Encoding 32-Bit CRC Decoding Incomplete FDU Timer ALOHA Validation of FDUs Missing SOF Word Missing EOF Word(s) Parity Errors Word Count Errors CRC Errors Inter-FDU Gap Time PAGE 22 22 22 22 22 22 22 23 23 23 23 23 23 24 24 24 24 25 25 25 25 25 25 26 v .4.4.11 3.4.7.4.12.2.4.1 3.3 3.2 3.2.3 3.4.4.9.4.3.7 3.4.4.6.12 3.3.12.12.6.4.4.7.4.5 3.3 3.4.6.12.6.4.4 3.1 3.8 3.6.4.2 3.10 3.4.4.1 3.4.3.4.1 3.1 3.4.

Part 3 contains Supplements 12 and above.Basic Philosophy This “File Data Transfer Techniques” specification describes a system in which an LRU may generate binary extended length messages “on demand.ARINC SPECIFICATION 429 PART 3 . a copy. Each Part will be updated via Supplement as the need dictates. Part 1.0 INTRODUCTION 1. “Mark 33 Digital Information Transfer System (DITS)” was adopted by AEEC in July 1977. 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.” i. The solution. Therefore the “dash numbers. Through the years as the Specification grew in content. 1.e. Parts 1. In the future. Part 3 defines file data transfer protocols.” Data is sent in the form of Link Data Units (LDU) organized in 8-bit octets. 1. the File Transfer technique can be used only for point-to-point message delivery. Two data bus speeds are supported. although it may be convenient. updates to the individual Parts of ARINC Specification 429 will be accomplished by independent Supplements starting with Supplement 16.3. The new protocol became known popularly as the “Williamsburg Protocol.3.5 was developed in order to facilitate the communications of the ACARS Management Unit (MU) and the Satellite Data Unit (SDU). -17. and 3 are being published separately beginning with the updates provided by Supplement 15.) and label assignments. 2. The original description of file data transfer was declared obsolete.3. the physical size grew proportionately. a new protocol was developed that expanded the c-16 capability of file data protocol to support the transfer of bitoriented information. Specification 429 defined a broadcast data bus. The fundamental concept was developed at a joint Satellite and ACARS Protocol Working Group meeting held in c-15 February 1988 in Williamsburg. COMMENTARY The data transparent protocol described in Section 2. 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. Unlike the simple broadcast protocol that can deliver data to multiple recipients in a single transmission.3 Development of File Data Transfer ARINC Specification 429.” 1.2 Data Transfer The same principles of the physical layer implementation described in Part 1 to ARINC Specification 429. was to divide Specification 429 into three parts. 1. In October 1989. may not necessarily be concurrent for all three parts of Specification 429. voltage levels.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. As a result. System Address Labels (SAL) are used to identify the recipient. The protocol defined in this document is preferred for new applications. c-16 “Functional Description and Word Formats. 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. 1. Virginia. -16. is retained in Appendix F.” apply to File Data Transfer. Part 2 provides the formats of words with discrete bit encoding. the effort involved with locating specific data became increasingly difficult.1 File Data Transfer Techniques . COMMENTARY c-15 The desire for exchanging binary data via ACARS was instrumental in initiating the development of a more sophisticated file transfer protocol.3. concurrent with the publication of Supplement c-15 15. etc.2 Organization of ARINC Specification 429 The original release of ARINC Specification 429 was published in its entirety as one document in 1977. etc. General provisions were made for file data transfer. AEEC updated a file data transfer procedure with a more comprehensive process that will support the transfer of both bit and character-oriented data. coding.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. The description of changes introduced by Supplements 15 and later for each Part are contained within the respective Parts of the document. Its viability as a universal protocol was c-15 . COMMENTARY c-16 The ACARS character protocol is defined in ARINC Specification 619. The descriptive material for the changes introduced by the Supplement 1-14 are provided in Part 1. In 1989. provisions were made for a character-oriented file data transfer protocol. 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.Page 1 1. 1. Part 1 addresses the physical parameters (wiring. The ACARS character oriented file transfer protocol which was derived from the material in Appendix F is documented in ARINC Specification 619. The new bit-oriented protocol was introduced by Supplement 12. as a historical record. This definition was used as guidance for the character-oriented file transfer protocol descriptions incorporated into many ARINC equipment characteristics.4 File Data Transfer When Specification 429 was adopted in 1977.

1998 was current when the definition of Version 3 was completed. Conversely.ARINC SPECIFICATION 429 PART 3 . to the maximum extent possible.3.3.5.3) is used wherever possible to enable the reference within this document to remain current.” 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.1 for bit protocol version determination.5. the least significant bit of the word is the most significant bit of the label. 1. The label is transmitted ahead of the data in each case. As an onboard data bus.3.Page 2 1. Version 3 of the file transfer protocol.3. this standard is often included in AEEC equipment standards (ARINC 700 series) by reference.3. c-17 . The process for determining the protocol (characteroriented as defined in ARINC Specification 619. 1. defined in Chapter 3 herein. “Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications” information to ensure that the desired section will be located. This “reversed label” characteristic is a legacy from past systems in which the octal coding of the label field was.3. IEEE 802. or bitoriented) to be used in the interaction between two units. Part 1 Attachment 7.3. i. a generic (non-time dated) reference (i. 1998.3. Appropriately. this Specification also references other c-17 documents. 1. of no significance.” This is represented graphically in ARINC Specification 429.e.19. 1998 Edition.. 1.0 INTRODUCTION 1.5 Transmission Order c-17 The most significant octet of the file and least significant bit (LSB) of each octet should be transmitted first. It may be noted that the Label field is encoded in reverse order. Since the IEEE standard may evolve over time.5. See Section 2. without future Supplements. utilizes many of the principles of the IEEE communications standard 802.4 File Data Transfer (cont’d) COMMENTARY (cont’d) Documents referenced in this document include: c-15 recognized by the Systems Architecture and Interfaces(SAI) Subcommittee which recommended its inclusion herein as the standard means of file data transfer.19. apparently. IEEE 802. where this information is not pre-determined is described in Section 2.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. Exceptions to this practice include references to specific clauses or paragraphs of IEEE 802.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. there are numerous references to that standard.e. but rather to ensure that the reader is equipped with sufficient IEEE Standard 802. These references are not intended to limit the growth or evolution of these provisions.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).. For example.

though simple in this application.0 BIT-ORIENTED FILE TRANSFER PROTOCOL 2. e. the sink should accept the conventional data word and resume processing of the incoming file transfer message. 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. events. T2. To obtain interoperability. etc. B. 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). applications and timers. timing. and options such as those defined in c-12 Attachment 10.Page 3 2. 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). c-13 The Network layer performs a number of functions.1 This Section number is not used in Part 3 to maintain consistency with previous versions of ARINC Specification 429. Link. O5.4 This Section number is not used in Part 3 to maintain consistency with previous versions of ARINC Specification 429. Examples of file transfer and field mapping are given in Attachments 12 and 12A respectively. If the sink should receive a conventional data word during the process of accepting a bit-oriented file transfer message. All other bus activity c-13 remains unchanged. The definition of c-12 the protocol words used to determine the type of protocol is contained in Table 11-4 of Attachment 11. The Link layer provides a highly reliable virtual channel and some flow control mechanisms. 2. See Attachment 10 for tables containing standard options. This document directs itself to an implementation of the Link layer.3 This Section number is not used in Part 3 to maintain consistency with previous versions of ARINC Specification 429.ARINC SPECIFICATION 429 PART 3 . 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 bitoriented data assembled in data files. voltage. The bit-oriented data link protocol was designed to operate in a bit-oriented Network layer environment. 2.g. Physical Medium The Physical layer provides the functions necessary to activate. This protocol should be used in lieu of the character-oriented file data transfer defined in ARINC Specification 619. 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. this process.19.g. It is structured to allow the transmission of any binary data organized into a data file composed of octets. 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. Network and Transport) is provided. 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. At the Link layer. Data words will contain 32 bits. Network Layer It is the responsibility of the Network layer to ensure that data packets are properly routed between any two terminals. The physical interface should be as described in Part 1 of Specification 429. The Network layer expects the Link layer to supply data from correctly received frames. the Data Link Subcommittee expects that ISO 8208 will be c-13 selected as the Subnetwork layer protocol for air/ground . Specifically.2 This Section number is not used in Part 3 to maintain consistency with previous versions of ARINC Specification 429. The bit-oriented protocol will support either full or half duplex operation (O1). The process for determining the protocol (characteroriented or bit-oriented) to be used in the interaction between two units. The timing values are designated with a “T” and a sequence number. maintain and release the physical link which will c-12 carry the bit stream of the communication. Physical Layer COMMENTARY There is no protocol to support negotiation of the parameters. however. bits 1-8 will contain the System Address Label (SAL) and bit 32 will be the parity (odd) bit.5. 2. where this information is not predetermined is described in Section 2. 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.. described in Part 1 of Specification 429 should be used by the interfacing units. D. The electrical interface. C. e. A table illustrating the bit-oriented file transfer word formats is shown in Attachment 11. The options are designated with an “O” and a sequence number. 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. A. an overview of the first four layers (Physical..

as defined in Section 2. the data received should be ignored. 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. E. 2. It provides “network independent” data delivery between c-12 these processing end-systems. the Label field (bits 1-8) is used to carry a System Address Label (SAL). the data should be encoded into the minimum number of LDUs. The LDU may represent raw data. The LDUs are assembled to make up a data file. 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. Thus.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. Within the context of this document. The data described above is contained within the data words which follow (See Section 2.3) of the sink. 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. however. In the data transparent protocol.1 Link Data Units (LDU) A Link Data Unit (LDU) contains binary encoded octets. some applications where c-13 the bit-oriented file transfer protocol will be used under other Network layer protocols. character-oriented messages. this test should be disregarded. The interpretation of those bits is not a part of this Link layer protocol. In order to obtain maximum system efficiency.5. The LDU is concluded with an End of Transmission (EOT) data word (see Section 2. When a LDU is organized for transmission. The gap should be 4 bit times (minimum). the c-16 label field loses the function of parameter identification available in broadcast communications. the data words in the LDU and the EOT word. There are.10. Each on-board system is assigned a SAL as shown in ARINC Specification 429.Page 4 2. character data. COMMENTARY 2. 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. No data file should exceed 255 LDUs. The sink should be capable of receiving the LDU with the minimum word gap of 4 bit times between words. The only restriction is that the bits be organized into full 8-bit octets. c-16 LDUs consist of a set of contiguous ARINC 429 32-bit data words. even though other systems may be connected and listening to the output of a transmitting system. It relieves higher layers from any concern with the pure transportation of information between them. such as for Automatic Dependence Surveillance (ADS). or any string of bits desired.0 BIT-ORIENTED FILE TRANSFER PROTOCOL 2. bit-oriented messages.5.5.5. The octets may be set to any possible binary value. the total number of ARINC 429 words to be sent (word count) is calculated. Transport Layer 2. Part 1. or an LDU retransmission due to an LDU transfer timeout. The number of LDUs needed to transfer a specific data file will depend upon the method used to encode the data words.5. A failure to meet this requirement will either result in a successful (but slower) LDU transfer. In order to identify the intended recipient of a transmission. COMMENTARY The word count field is 8 bits in length.5. The primary value of this provision is realized when assessing a maximum LDU transfer time for short fixed-length LDUs. 2. When a system sends an LDU to another system. 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. 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.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. each containing the System Address Label (see Section 2. It is the highest order of function involved in moving data between systems. LDUs correspond to frames and files correspond to packets. Attachment 14. The Transport layer controls the transportation of data between a source end-system to a destination end-system. The source should introduce a gap between the end of each ARINC 429 word transmitted and the beginning of the next.3 System Address Labels (SALs) LDUs are sent point-to-point. Thus the maximum number of ARINC 429 words which can be counted in this field is 255.5. The word count is the sum of the SOT word. c-13 . This provision prevents a source that is transmitting a short message from using the full available LDU transfer time (T9).ARINC SPECIFICATION 429 PART 3 . When a system receives any data containing its SAL that is not sent through the established conventions of this protocol.5. The initial data word of each LDU is a Start of Transmission (SOT) as described in Section 2. The word count field appears in the RTS and CTS data words.12). given the asynchronous burst mode nature of Williamsburg LDU transmissions. Although. In aircraft operation.5 Bit-Oriented Communications Protocol (cont’d) subnetworks.5. data files are identified by content rather than by ARINC 429 label.11).

The Word Count field should contain the same Word Count value as the RTS word. The status codes are for engineering purposes only and should be ignored by the system receiving the NCTS word.5.7.0 BIT-ORIENTED FILE TRANSFER PROTOCOL 2.5.6. this field may contain the same information for routing purposes between OSI and nonOSI systems. Table 11-4 of Attachment 11 contains the different protocol words and their formats. It is the c-14 responsibility of the higher level entities to detect invalid destination codes and to initiate error logging and recovery.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 CTS word to the source within T1 milliseconds. Protocol words with an invalid protocol identifier field should be ignored.ARINC SPECIFICATION 429 PART 3 . it will issue a Request To Send (RTS) to that system. one data word and an EOT word.3 Word Count Some protocol words contain a Word Count field. The Destination Codes c-16 are assigned according to the applications involved as shown in Attachment 11A. A LDU with the minimum word count value of 3 ARINC 429 words would contain a SOT word. A valid CTS must also contain the same word count as the RTS. The RTS may be repeated T2 milliseconds after each NCTS until N1 requests nominally have gone without receiving a valid CTS. The Word Type field is used to identify the function of each ARINC 429 data word used by the bit-oriented communication protocol.5. However.1 Clear To Send (CTS) When a system receives a valid RTS and is ready to accept the LDU transfer. 2. 2.5. the source should wait for T2 milliseconds before repeating the RTS. the c-16 destination code may be set to null (hex 00). The NCTS counter (N1) should be reset upon valid (CTS) response to the RTS. 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 . the Destination Code should indicate the system to which the message is to be passed. The response can be: (1) Clear to Send. it should send a Not Clear To Send (NCTS) to the source within T1 milliseconds. The maximum word count value is 255 ARINC 429 words and the minimum word count value is 3 ARINC 429 words.2 Destination Code c-16 c-18 Some protocol words contain a Destination Code.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. The Destination Code field (bits 24-17) typically indicates the final destination of the LDU (O10). All of the RTS counters (N1. then the source should declare the NCTS to be invalid and ignore it.6. See Table 11-1A of Attachment 11 for a description of the Word Type field. 2. See Table 11-4 of Attachment 11 for the format of the NCTS word.7. 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. 253 data words and an EOT word. The Word Count field (bits 16-9) reflects the number of ARINC 429 words to be transmitted in the subsequent LDU. the Destination Code provides Network layer information. In an OSI environment.6. between an ARINC 758 CMU and a multic-18 bearer-system ARINC 761 SDU) use the “Destination” code to select a specific bearer system to be used for a downlink message. Some interfaces (e. 2.5.5. N3) will be reset after a valid CTS is received. A LDU with the maximum word count value of 255 ARINC 429 words would contain a SOT word. and to indicate the specific bearer system used for an uplink message.5. the Link layer protocol is not responsible for validating the destination code. If the LDU is intended for the use of the system receiving the message. c-14 2. To be considered valid CTS. 2.2).5. 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).6.5 Word Type The Word Type Field occupies bit 31-29 in all bit-oriented LDU words. When a system receives a RTS. if the LDU is a message intended to be passed on to another on-board system. The Destination Code in the CTS should contain the same Destination Code as the RTS word (See Section 2. NCTS or BUSY data words must have odd parity and contain the same destination code as the corresponding RTS. After sending a NCTS. COMMENTARY Within the pre-OSI environment. 2.Page 5 2. 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.7 Request To Send (RTS) When an on-board system needs to send a LDU to another on-board system. Upon receipt of the NCTS word. it should send a response to the source within T1 milliseconds..g. it should treat it as a valid Not Clear To Send.5. (2) Not Clear to Send or (3) Busy.6 Protocol Words The protocol words are identified with a Word Type field of “100” and are used to control the file transfer process. In the OSI environment. N2. The CTS contains a Destination Code (bits 24-17) and a Word Count field (bits 16-9). The RTS word contains a Destination Code and a Word Count field. If the NCTS received does not contain the same Destination Code.

2 Not Clear To Send (NCTS) (cont’d) accept the file transfer. When operating in half duplex mode. If this occurs. N3) will be reset after a valid CTS is received.7. 2. All the RTS counters (N1.ARINC SPECIFICATION 429 PART 3 .7. Alternatively. If a conflicting RTS occurs again. In the absence of any valid response (such as CTS. the sink should respond with the NCTS word using an optional status code identifying the condition. 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. 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. 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 the BUSY received does not contain the same Destination Code. NCTS. See Table 11-4 of Attachment 11 for the format of the BUSY data word. If this protocol is used in an environment that has well defined priorities (O5). N2. COMMENTARY 2. When expedited file transfers are desired between 2 BOP c-16 devices. If no RTS is received within the random time. the RTS should be repeated every T5 milliseconds until at least N3 requests have gone unanswered. or an unexpected RTS should be ignored.7.5. The source may optionally choose (O4) to accept such a CTS. or BUSY). Note that the busy condition could last for hours. causing each system to appear to receive the other’s RTS in response to its own RTS. depending on the nature of the application and the buffering capacity of the sink.3 Destination Busy (BUSY) When a system receives a valid RTS and is not able to accept an LDU within a timely manner. a well-defined priority in avionics gives an c-16 RTS for uplinks priority over an RTS for downlinks.5. BUSY. the same procedure will take effect for as many times as it takes for one system to prevail over the other. The recommended value for low speed is T4=1. The action to be taken is described in Table 10-2 of Attachment 10 or in the applicable equipment characteristic. without waiting for another RTS. when the limit is exceeded depends on the application (A3). However. 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.Page 6 2. Any response other than a valid CTS.0 BIT-ORIENTED FILE TRANSFER PROTOCOL 2. or taking some different course of action. one system may be assigned priority over another to resolve RTS conflicts without the random retransmission procedure described above. Alternatively. COMMENTARY Typically. the source may ignore the CTS with the requested Destination Code and Word Count and repeat the RTS. The No response counter (N3) should be reset c-14 upon valid response to the RTS. the preference is to respond with a NCTS.8 Conflicting RTS Transmissions A timely manner refers to the interval defined by the NCTS retry sequence. 2. without waiting for another RTS. The source may optionally choose (O4) to accept such a CTS.5 seconds and N2=200. the system should retransmit the RTS. it is possible that two systems might decide to send RTS messages to each other at nearly the same time. The actual number of attempts a source should make (N3) before giving up. the receiving c-14 system may optionally send a BUSY response to the source within T3 milliseconds. 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. the sink device should support Option 3 (Send Auto CTS) and the source device should support Option 4 (Accept Auto CTS). The RTS may be repeated every T4 seconds for as many times as the application requires up to a maximum of N2 . or the absence of an unexpected RTS. The status codes are for engineering purposes only and should be ignored by the system receiving the BUSY word. the source may ignore the CTS with the requested Destination Code and Word Count and repeat its RTS. The action taken following T4 . the source should wait for T4 seconds before repeating the RTS.5. 2. Aloha. After sending a BUSY. the request should be repeated. Some original implementations simply ignored an invalid RTS word. then the source should declare the BUSY to be invalid and ignore it.N2 time out depends upon the application (A2). Each new attempt could possibly consist of several RTS transmissions. 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.4 No Response to RTS If the source receives no response to the RTS within T5 milliseconds.5. 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.1 Half Duplex Mode Upon receipt of the BUSY word. .8. If a system receives another c-12 RTS before this timer expires. COMMENTARY If the word count and/or destination fields in the received RTS word are not valid by virtue of illegal or unsupported values. NCTS.5.

2. COMMENTARY c-14 Within the pre-OSI environment the GFI provides Network layer function information.11.2 Full Duplex Mode When operating in a full duplex mode. 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. in the process of placing the octets into the data words. Each LDU transmitted. should also end in a complete octet. the receiver should send a NAK or assume the upper 4 bits of the partial octet to be zeros.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. both should receive a CTS and both should respond normally to the CTS. to indicate to a higher level entity in the sink. 2. that the source does not receive the CTS and retransmits the RTS to the sink. This space is allocated in five semi-octets. In the OSI environment this field may contain the same information for bridging purposes between the OSI and non-OSI world. immediately followed by the data words which constitute the LDU. It is initialized to the hex value 00 and increments by 1 for each new file that is sent over the ARINC 429 link. at the end of the transmission. 2. A semi-octet (or nibble) is c-12 half of an octet. even in the middle of receiving an LDU. four and five semi-octets.Page 7 2.5. that after sending a CTS word to a requesting source. the LDU ends with an incomplete octet. a source may experience a reset which causes a new RTS to be sent in the middle of an LDU transfer. an octet is split between two different words. 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. The octets of the data file are divided into two semi-octets and placed sequentially into the data words. .10. A conflicting RTS applies only to a receiving system that has transmitted a CTS (in response to a RTS) and receives another RTS.5. Binary data words of fewer than five semi-octets are called Partial Binary Data words. See Table 11-6 of Attachment 11 for a description of the SOT word format.5. The least significant bit of the least c-13 significant semi-octet is sent first. 2. the File Sequence Number should start over at hex 01. both systems must be capable of operating as a source and sink at the same time. then the sink should transmit another CTS word. the receiver determines that an odd number of semi-octets has been received. Neither system should abort. Binary data words of five semi-octets are called Full Data words.10. If. the sink should discard any partial LDU already received and respond as defined in Section 2. skipping zero. After reaching hex FF. prior to transmission. c-14 2.5.5.5. or four bits in length. See Attachment 11 for data word formats.10. for any reason. The LDU Sequence Number should be reset to 00 at the beginning of each new file. If a sink receives another RTS after having sent a CTS.5. A data file may be sent using any combination of full and partial data words.9 Unexpected RTS It is possible.1 Full Data Word(s) A Full Data Word has 20 bits available for data.0 BIT-ORIENTED FILE TRANSFER PROTOCOL 2. It also contains a General Format Identifier (GFI) and a LDU Sequence Number. It is designated by a higher level entity in the source device. Binary data words may contain one. There are no restrictions regarding the particular type of data within a file. Alternatively. The formats of Data words are illustrated in Attachment 11. 2. There are two basic types of data words: full binary and partial binary. two.11 Data Data words immediately follow the SOT word. If. and proceed normally. 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. A file consisting of multiple LDUs will have the same File Sequence Number in each of the SOT words of each LDU. It is the responsibility of the higher level entities to detect invalid GFI designations and to initiate error logging and recovery.ARINC SPECIFICATION 429 PART 3 .1.1 General Format Identifier (GFI) The General Format Identifier (GFI) occupies bits 28-25 in the SOT word. Any incomplete final octet should be completed with zeros before transmission.3 LDU Sequence Number The LDU Sequence Number (bits 16-9) of the SOT word contains an 8-bit number assigned to the LDU.5. The GFI is transparent to the Link layer protocol. Each binary data file.8. that is. See Table 11-6A of Attachment 11 for a description of the GFI field. If. the system should respond by sending the Start of Transmission (SOT) word within T13 milliseconds. If both systems initiate an RTS.7.5. the first word c-13 received by a sink after having sent a CTS word is an RTS. the format of the data words that follow. The SOT word contains the File Sequence Number in its File Sequence Number field (bits 24-17). should conclude (end) with a complete octet. 2.2 File Sequence Number The File Sequence Number (bits 24-17) of the SOT word contains an 8-bit number assigned to the file. This RTS is treated simply as a retransmission and the sink should retransmit a CTS. three. The octets of the data file are encoded and transmitted in 32-bit data words.

1 Full Data Word(s) (cont’d) If the end of the LDU does not completely fill the last Full Data Word. obtained from the modulo 2 division of: x16G(x) + xk(x15+x14+x13+.2 Partial Data Word(s) A Partial Data Word contains from one to four semi-octets. There exists a generator polynomial which is of the form... by the transmitter. Table 11-7A of Attachment 11 contains the definition for bit 25 of the EOT word. See Table 11-7 of Attachment 11 for the definition of this word... if the data stream is 101001.. 2. The use of the CRC in this case does not imply any inherent lack of integrity of the ARINC 429 link. some applications may require high data integrity to be confirmed by an error checking mechanism. a Partial Data Word (see Section 2.1 CRC Encoding The CRC field is a 16 bit sequence with the most significant bit (MSB) transmitted first.5. these coefficients can have the value 0 or 1 and all polynomial operations are performed module 2. resulting in the message. The unused semi-octets in the partial data word should be set to binary zeros. then the remainder. c-13 In order to obtain maximum system efficiency.0 BIT-ORIENTED FILE TRANSFER PROTOCOL 2. of length n where: n = k+16. 2. 2. If the file transfer consists of a single LDU. then bit 25 of LDU 1 through LDU N1 should be set to 0 and bit 25 of LDU N should be set to 1.Page 8 2. 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. M(x)) is error free. Only full four-bit semic-16 octets can be sent. If N LDUs are to be sent. R(x). 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.5. each LDU contains a CRC check.5.5.” The complementing of R(x).ARINC SPECIFICATION 429 PART 3 .5. For example. but not including. At the transmitter.+x2+x+1) and divided by P(x) as follows: x16M(x)+xn(x15+x14+x13+. In this application...11. The elements of an n element code word are thus the coefficients of a polynomial of order n .12. the incoming M(x) is multiplied by x16. M(x). The polynomial representing the data content (message) of an LDU is generated using the LDU bit which is encoded in bit 9 The CRC calculation is performed over the data octets only of the LDU with any semi-octets zero filled. This bit c-14 is used to indicate if the LDU is the final LDU of the file transfer. and M(x) = x16G(x) + R(x) = x16G(x) + CRC 2. the SOT and EOT words. at the completion of the division ensures that the received.12 End of Transmission (EOT) Each LDU transfer is terminated by an End of Transmission (EOT) word. 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.+x+1) = Qr(x) + Rr(x) P(x) P(x) If the transmission of the serial incoming bits plus CRC (i. G(x).e. two or three bits are invalid.5. the CRC is added to the x16G(x) product.2 CRC Decoding Decoding of the CRC at the receiver is as follows: At the receiver. 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.11. nonzero remainder at the receiver. P(x) = x16 + x12 + x5 + 1 The CRC is then determined as the one’s complement of the remainder.+x2+x+1) = Q(x) + R(x) P(x) P(x) Note: The addition of xk(x15+x14+x13. respectively). one.1. The EOT word contains a Cyclic Redundancy Check or CRC (bits 24-9). Partial Data Words should be used only when they are required to complete the data for an LDU transmission. where k is the number of data bits in the LDU existing between. The number of semi-octets in a partial data word is indicated in bits 28-25 of the word. Since the transfer of data using a file transfer protocol contains no provision for automatic refresh. Partial Data Word semi-octets are sent in the same order as the semi-octets in a full data word. COMMENTARY c-12 c-12 . error-free message will result in a unique. For this reason.. corresponds to initializing the initial remainder to a value of all “ones. added to the product. Simple parametric data is usually transmitted at a refresh rate high enough to permit recognition and suppression of erroneous data. k=6 and G(X)=x5+ x3 + 1..11. bit 25 should be set to 1 to indicate that this is the final LDU.2) should be used to complete the LDU transmission. A mathematical example of CRC encoding and decoding can be found in Appendix G. n x (x15+x14+x13+.12.+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)). Rr(x) will be 0001110100001111 (coefficients of x15 through x0.

2. COMMENTARY 2. c-12 If all words of the LDU transfer are received within T9 seconds of the CTS.0 BIT-ORIENTED FILE TRANSFER PROTOCOL c-12 of the first data word as the coefficient of the highest order term. A mathematical example of CRC encoding and decoding can be found in Appendix G. See Table 11-4 of Attachment 11 for a description of the ACK word format. and the LDU is either the next LDU.2 Missing EOT Word Following the transmission of the final data word of each LDU.14.Page 9 2.5. whichever occurs first.13 Negative Acknowledgment(NAK) If the sink detects any of the errors described in the following subsections.5. 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. End of Transmission (EOT).5.3 Parity Errors Bit 32 of each ARINC 429 word should be set to odd parity for the entire word.1 Missing SOT Word Following reception of a valid CTS word.5. it cannot be sure of the intended label. the sink should verify that the actual number of words received is the number of words expected.4 Word Count Errors Upon receipt of the EOT word. 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.14 LDU Transfer Acknowledgment(ACK) c-12 .12. if the sink does not receive the complete LDU transfer within T9 seconds of having sent the CTS. If the EOT word is not received as the c-13 final word of the LDU within T9 seconds of the CTS. the source should transmit the SOT word as the first word of the LDU as specified in Section 2. 2. so by ignoring the offending word there may still be a chance of a successful file transfer.10.13.13. c-16 COMMENTARY Some implementations look at both SOT and EOT to determine duplicate LDUs. and it’s SOT words are identical to those of the previously received LDU. a duplicate LDU or the first LDU of a new file.5.5. If the word counts c-14 do not match. per the RTS and CTS words. It is not necessary for the sink to be aware of the type of error that occurred. 2. Upon receipt of a word.9. and accepts the LDU just received. 2.13. it sends a NAK to the source upon detecting the error or within T8 milliseconds of receiving the EOT word. See Table 11-4 of Attachment 11 for a description of the NAK word format. the c-13 sink should send the NAK response. The word may not even be a part of the LDU.5. However.5. When a duplicate LDU is detected.5. the sink should send a NAK response to the source. then the sink discards any previously received partial file. the sink should send the NAK response.5 CRC Errors Upon receipt of the EOT word. 2.5. The sink will either NAK the source when the EOT word is received. Start of Transmission (SOT).14.ARINC SPECIFICATION 429 PART 3 . then the sink should send an acknowledgment(ACK) to the source within T8 milliseconds of receiving the EOT word.5.5. the receiving unit should take no action and ignore the word.13. each with odd parity. The sink should test for errors to determine if a NAK should be sent. 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. the receiving unit should verify that each word was received with odd c-12 parity.6 Time Out Errors The sink will not time the gaps between the words received. COMMENTARY When the sink receives a word with bad parity. as long as any of the errors c-13 listed in the following subsections will elicit a NAK response.13. the sink should verify the CRC on the received LDU. then the sink should send the NAK response to the source within T8 milliseconds after the T9 has expired.5. 2. If c-12 the SOT word is not received as the first word of the LDU. or when it times out waiting for the full expected number of words.14. If any word is received with even parity. If the offending word was intended to be a part of the LDU. See also Section 2.5. the source should transmit the EOT word as the final word of the LDU as specified in Section 2.1 Duplicate LDU An LDU is determined to be a duplicate if its File Sequence Number and LDU Sequence Number are not both zero.2 Auto-Synchronized Files When the File Sequence Number is different from the previous LDU transfer and the LDU Sequence Number is zero. 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.13. 2. If the 16-bit CRC is invalid. it should send a NAK to the source and discard any partial LDU received. and the word c-12 count and CRC verify. the actual word count will not match the expected count. the sink should discard the LDU just received and acknowledge per Section 2. 2. then when the EOT word is received. 2.

2. 2.D. For multiple-LDU files.0 BIT-ORIENTED FILE TRANSFER PROTOCOL 2. The T14 timer is stopped each time another valid RTS is c-14 received. some bits of the data field can be defined as check bits. Codes 0000 and 0001 are reserved for the TEST and LOOP words as defined in Section 2. If the source c-14 detects a SYN during the transmission process.. or within T8 milliseconds of receipt of the EOT word when necessary to determine a duplicate LDU. beginning with the first LDU. some implementations will interpret this as an unexpected File/LDU Sequence Number instead of a duplicate LDU. In this case the data may be sent “in the blind” using the Solo Word format (O8). starting with the sending of the RTS word. Solo Words cannot be interleaved with data file words during a data file transfer. the file transfer between the two systems should be considered failed. See Table 11-4 of Attachment 11 for a c-13 description of the SYN word format.16 Response to ACK/NAK/SYN The source should expect a response to the transmission c-14 within T16 of sending the EOT . (e.e. for those devices compliant with version “0000” or “0001” of this protocol (Table 11-4A of Attachment 11). or after receiving N5 consecutive SYN words.Page 10 2. if able. Option O1 of Table 103) this timer only applies when the device is operating as a sink.5.17 Solo Word (Single Word Transfers) If the data to be sent consists of 1 or 2 octets only. the source should consider the transfer successful. The T timer should also be stopped if the sink 14 discards the partial file for other reasons defined in this specification. when it is ready for transmission. that file is discarded and the source proceeds normally with the first LDU of the next file. or if a NAK is received or if no response is detected. 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.ARINC SPECIFICATION 429 PART 3 .5. A typical example is an inappropriate or unexpected File/LDU Sequence Number in the SOT word. then either upper layer OSI protocols or the application process should provide this capability. and discard any partial file already received.2 Auto-Synchronized Files (cont’d) COMMENTARY c-12 Some implementations synchronized files. it should retransmit the entire file. The action taken is specified in c-13 Section 2. If error detection beyond parity is required. COMMENTARY Timer T10 may apply instead of T16.5. COMMENTARY If an SOT word of an LDU has the same File Sequence Number and LDU Sequence Numbers as the previous LDU. a button code from a CDU keyboard) then it is not necessary c-12 to obtain a CTS. Upon receipt of the SOT word.14. SYN word is received. the sink should send the SYN word within T8 milliseconds and discard any partial file already received. and is not the first LDU of a new file. . If the source is not able to retransmit or rebuild the entire file. 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.17.16. to be verified by the application.5. the I. For example. If an ACK is received and the File Sequence Number and LDU Sequence Number match the contents of the SOT word. then the sink should send the SYN response to the source within T8 milliseconds of receipt of the SOT word.. COMMENTARY If end-to-end accountability is required.e. the source should repeat the entire LDU transmission process.. may indicate that the data is a key code from a CDU or a status word. There is no acknowledgmentdefined for the source when a do not support auto2. For Half Duplex environments (i.5. the sink should verify the LDU Sequence Number (bits 16-9).5. The File Sequence Number contained within the SYN word is provided for testing purposes and is not evaluated by the source. T10 is started c-13 after the CTS is received whereas time T16 is started after the EOT word is transmitted. 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. COMMENTARY Some implementations look at both SOT and EOT to determine duplicate LDUs. 2.1.5.14. When T14 minutes is exceeded. is not the next LDU). All other codes are available for application use. If the LDU is not a duplicate and its LDU Sequence c-16 Number is not the next in sequence (i.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.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. 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. they may invoke a Solo Word or data file transfer response as required by the application. Solo Words are not acknowledged at the link level.g. However. If an ACK is received and the File Sequence Number and/or the LDU Sequence Number do not match the SOT word. The SYN word may be sent without timing constraint when c-13 the received data words cannot be normally processed.

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.5. with bit 17 as the most significant bit and bit 24 as the least significant bit of the Subsystem SAL.5. the source should notify the higher level entity of the communications failure and continue the protocol determination process. If the device in question has not responded within time T12.1 ALOHA The first ALOHA word transmitted in a sequence should c-14 contain the highest Version Number supported by the source device.1.2.2.19. COMMENTARY c-14 In addition to a “power-reset” or a system “reinitialization.2 should be followed. To maintain c-16 interoperability.5. 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. it should construct the ALO word and transmit this word to the device in question.5.19. 2. shows the ALO and ALR word formats. The ALOHA word should contain a Subsystem SAL field as shown in Attachment 11.17. 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. ARINC Characteristic 702. protocol may at any time determine the ARINC 429 c-14 link status using the ALO/ALR process described in Section 2.1. If the source device is not able to adapt to the differences in protocol version.5. c-12 Each equipment utilizing this bit-oriented protocol may define solo words as needed. When the system also supports character oriented protocols then the process defined in 2. See Attachment 17. or performs a re-initialization for any reason. Examples of protocol initialization are given in Attachment 13.19.5. The ALO/ALR protocol determination process should continue until a common protocol version is found.5. A bilingual system should repeat the processes described in c-16 Sections 2. When the system only supports bit oriented protocols it should repeat the process described in this section. For further information. When a system with a bit-oriented Link layer protocol has the need to make this determination.5. b. This field should contain the SAL of the device sending the ALOHA word.. 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). Attachment 11.Page 11 2. COMMENTARY The same SOLO word ID coding may be usedrepeatedly in different units as long as its meaning remains unambiguous. The TEST word contains a 16-bit binary pattern (bits 24-9) chosen by the originator.5. The test is initiated by the source sending the Loop Test Pattern Word (TEST).19. “Flight Management Computer System. 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. all systems which support the Link layer Bit-Oriented Protocol must be able to respond to the initialization of this process. e.18 Optional End-To-End Message Verification In some applications.17.2 Optional Solo Word Definitions The system should then wait for a maximum period of time defined by T12. file transfers may proceed using the protocol version identified in the ALR word.19. the source device should take one of the following actions: a. See Table 11-5 of Attachment 11 for the format definition.” 2.” a device that supports the bit-oriented . Table 11-4. If the ALOHA Response contains a version that does not match the ALO version. 2. These solo word definitions should be unambiguous. COMMENTARY The preferred reaction to a loop test failure has not been defined. If the system is bilingual and there is no response to the ALO/ALR process.1 and Section 2.5.5.0 BIT-ORIENTED FILE TRANSFER PROTOCOL 2.19.1 Test Word and Loop Word The integrity of the ARINC 429 link between two units may be tested. 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. Table 11-4.” 2.19. If none of the protocol versions match. The c-16 protocol determination process will continue until a common protocol is found. 2.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. until a common protocol version is selected by both systems.g. it may also determine if the interfacing device supports the character-oriented protocol as described in Section 2.5.5.19. If the source device is able to adapt to the differences in protocol version. the reader should refer to the applicable ARINC Equipment Characteristic.ARINC SPECIFICATION 429 PART 3 . the initiating system should initiate another ALO word and again delay up to T12.1 and if applicable 2.19.

the device should take the following action: If the device was in the sink mode (had already begun receiving any LDU of a file). but it does not complete the file transfer. Previous supplements of the bit-oriented Link layer protocol defined the Subsystem SAL field as [TBD] bits.19.Page 12 2. Some LRUs will wait forever for the file transfer to be completed unless the source sends a NAK word to terminate the file transfer.ARINC SPECIFICATION 429 PART 3 . then an attempt to obtain a response to the characteroriented RTS-CTS words should be made. 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. Therefore.5. it should discard any partial file it had received. This would minimize synchronization problems between the two communicating devices and allow the Link layer method to be established in a timely manner. If the link has been established.5. some devices in service may have encoded nonzero bits in this field. 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. and as such. the source may reset the File and LDU sequence numbers. Since the ALO represents a system “reinitialization” (per Section 2. it is necessary to have a cyclic process to establish the protocol to communicate with. and the ALOHA word is received on a data bus that has a specific bit-oriented Link layer protocol subsystem associated with it. The ALR response should reflect the device’s protocol version level by way of the Version Number contained within the ALR word.3). then the cycle should be re-started using the bit-oriented ALO sequence. If Option O12 is selected for a particular bit-oriented protocol interface. it is desirable to have an COMMENTARY During the protocol determination process. In this situation. it should resend the entire file beginning with the first LDU of the file. 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. If the character-oriented protocol fails.19. An attempt to establish contact using the bit-oriented ALOALR words should be made to the point where the link is considered to be failed or to be established. it should leave its present task and respond within T15 with an ALR word. a bilingual device should recognize protocol words using both the bit-oriented (Williamsburg) and the character-oriented formats. A receiving system should therefore implement a reasonableness check to validate that the data bits received in this field represent a SAL associated with a known bit-oriented Link layer protocol device.1. or because of a failure to deliver a message due to a no response. If the device was in the source mode (had already begun transmitting any LDU or file). NCTS (CTS 0). 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. Because of the environment in which these devices are to operate. 2.0 BIT-ORIENTED FILE TRANSFER PROTOCOL 2. it is recommended that the ALR word be attempted using the SAL for that specific subsystem. A graphical representation of this is presented in Attachment 17. then the protocol determination sequence should be started again. then normal bit-oriented communications can be pursued. Attachment 17 contains an example diagram of these determination sequences.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. 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. Whenever a device receives the ALO word. COMMENTARY c-16 When an LRU performs the character protocol determination (RTS) it is initiating the sequence of events for a file transfer. “automatic” determination sequence which allows the devices to adjust from the character-oriented to bit-oriented protocol. If the link is considered failed.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. If a device receives an ALOHA word containing a System SAL of all zeros or an unknown SAL. or BUSY (CTS Q) response is obtained. then the link is considered established and normal character-oriented communications can be pursued. After the device has responded to the ALO word (with the ALR). 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. c-16 . If a character-oriented CTS. If a protocol has been established and the link fails because of a loss of activity (if defined on that bus). The typical repeat sequence for the character-oriented protocol is 3 tries (See Attachment 13). There may be a period of c-14 inactivity between cyclic attempts of not more than 15 seconds. to ensure interoperability. If the Version Number of the ALO does not match the sink device’s protocol Version Number.

c-16 Version 2 of the bit-oriented (Williamsburg) Protocol. .0 BIT-ORIENTED FILE TRANSFER PROTOCOL 2.0 of this document.ARINC SPECIFICATION 429 PART 3 .6 Windowed Bit-Oriented Communications Protocol This section has been deleted.Page 13 2. previously in this section. has been superseded by Version 3 of the bit-oriented (Williamsburg) Protocol defined in Section 3.

The selection of MAC Client (LLC or non-LLC frame format) is mutually exclusive. repeaters.4. bridges or computers. the Data Link layer is responsible for the logical connection between at least two entities of the same Local Area Network (LAN). The MAC isolates the sublayer above it from the details of the Physical layer. In Version 1 the transmitter is responsible for buffering.8) which replace the Version 1 SOT and EOT words. 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 Data Link layer is further divided into two sublayers. 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. NCTS.4. Any segmentation and reassembly. This document follows the guidance of IEEE 802. multiple MAC Service Clients (users) interface with the MAC entity (MAC Service Provider). 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.1 Introduction This section describes Version 3 of the bit-oriented (Williamsburg) protocol. The Version 3 bit-oriented MAC protocol specifies full duplex operation (O1) to allow simultaneous data transfers in both directions. and where the Network Layer is selected as the MAC Client.3 Local and Metropolitan Area Networks.3. COMMENTARY Generally. 3.1 Bit-Oriented Media Access Control (MAC) Protocol 3. 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. New SOF and EOF words have been defined for Version 3 (see Sections 3.3 Frame Data Unit (FDU): An ARINC 429 envelope that contains a MAC frame as well as specific control information. For further description of the OSI protocol layers please refer to Section 2.Page 14 3. LLC Service Providers are required for some classes of IEEE 802.5 of this specification.1. The bit-oriented MAC protocol does not use the RTS.6 and 3. Additionally.3 (Ethernet). if necessary. the bridging function may act as a MAC Service Client as well as a MAC Control function.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL 3. which is responsible for the connection between at least two networks. specifically where the MAC frame contains insufficient information for protocol selection. and 3. or when required by higher layer protocols (specifically OSI based protocols such as ATN). In the IEEE/ISO set of standards the LLC is the most prominent one. The Version 1 ARINC 429 LDU full and partial data words have been retained. In the non-OSI world there are a variety of different protocols that may or may not directly interface with the MAC. A detailed description of the structures are given in Section 3. which is a physically independent control sublayer. BUSY. i. . All valid frames received by the sink are passed up to the MAC Service Client. The Version 1 bit-oriented (Williamsburg) protocol typically operates in half-duplex mode only.ARINC SPECIFICATION 429 PART 3 . SYN. 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. The purpose of the MAC is to provide a standard interface to the entities above it.e. Only single Frame Data Unit (FDU) transmissions are supported. CTS.1. which is responsible for the physical connection between adjacent nodes. 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.4. It interfaces to the Network layer.5 of this document. in Version 3 the receiver is responsible. The ARINC 429 MAC is defined herein. should take place above the ARINC 429 MAC sublayer. The terms Frame Data Unit (FDU) and MAC frame are defined in Sections 3.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.1. The demands for buffering are much greater for Version 3 than for Version 1. The Version 3 protocol assumes a sufficiently robust ARINC 429 physical layer.1. layer dependent entity. Within the ISO/OSI Reference Model.2. and the Physical layer. which is a Physical. Duplicate FDU detection is not performed by the MAC. A detailed description of the structures is c-17 given in Section 3. the most prominent one is Internet Protocol (IP). Here. The Media Access Control (MAC) sublayer. ACK and NAK words. The Logical Link Control (LLC) sublayer is assumed by c-17 IEEE/ISO as the second sublayer. It is an IEEE 802 compliant MAC protocol for frame oriented data transfer using the Data Link layer.4. Throughout Section 3 of this document the following terms are being used: 3.3 where the Length/Type field is used to select between LLC as a MAC Client.3.

3 (Ethernet).. In order to accurately estimate the amount of buffering needed.2. MAC Transmit/Receive Functions (Section 3. Any flow control. Flow control is primarily the responsibility of the MAC service client or a higher level entity. the entity responsible for flow control should attempt to anticipate the need to activate flow control in order to accommodate the delays. the Information frame and the Command frame. The Version 3 Command frame format facilitates the exchange of command/response pairs.indication primitive.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL 3. This section describes the services that the Media Access Control Sublayer provides to the next higher layer. MA_DATA.4 Buffering The MAC sublayer should provide sufficient buffering to account for expected processing/queuing delays. new FDUs are discarded.3). based on the applicable equipment interface specification. The Information frame is intended to be bridgeable to IEEE 802.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.2.2.1.2. the type of frame (Information or Command) received is indicated through a parameter in the MA_DATA.7 and 3.e.2. c-17 . The next section.ARINC SPECIFICATION 429 PART 3 .3) should be used to inform the MAC Service Client of a buffering problem for the received frame. The MAC Sublayer Service Specification (Section 3.2. A protocol architecture diagram is used to illustrate this relationship (See Figure 181 of Attachment 18). then the reception status parameter of the MAC primitive.e.e. From a transmitter’s point of view. MAC Frame Structures (Section 3.2. The subsequent section. if the buffering capacity is exceeded. i.. two specialized MAC frame structures have been defined. 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. COMMENTARY Each layer should have sufficient buffering for expected processing/queuing delays.Page 15 3. This will only be possible if the maximum allowed delay in each of the various components is specified. the receiving MAC Service Client. the originating MAC Service Client. i. These delays include any processing or queuing delays introduced by communications with the MAC Service Client. 3.3 (Ethernet). is provided by entities above the MAC service entity sending messages to each other.request primitive selects which type of MAC frame to create (see Section 3. based on the contents of the SOF word (see Sections 3.4).indication (see Section 3. The other need is to transfer local.4.. delays) will make it difficult to consistently provide adequate buffering capacity and may lead to data loss and possible communication failures. From the receivers point of view. each layer will need to specify the maximum allowed delays. In order to allow for the optimized transmission of the two types of information. fast file transfer traffic that is focused upon exchanges c-17 between two closely cooperating systems. 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. There are two types of applications that have driven the development of this version of the protocol.1. The following subsections are closely modeled after IEEE 802.2 Media Access Control (MAC) Sublayer This section describes the various aspects of the MAC sublayer functionality. defines the MAC frames that will be presented to and expected from the peer MAC entity. However. to the MAC Service Client.4).4). The Command frame is not bridgeable.e.1) details the procedures in an abstract way (via service primitives) that provide the communication service to the MAC Service Client. which are peerto-peer only and hence do not require the additional addressing capability provided by the Information frame. i.2. 3. Failure to coordinate the requirements (i.6). 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. introduced between two systems. one parameter within the MA_DATA. ARINC 429 only. 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. The services 3.3. 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. For this reason. Some provisions for flow control are provided through the MAC sublayer (see Section 3.2. Option 13 (O13) in Table 10-3B of Attachment 10 allows for the apriori selection of frame type. If buffering of incoming frames is done at the MAC sublayer.1 MAC Sublayer Service Specification COMMENTARY ISO standards documents do not explicitly specify at which (sub) layer buffering is accomplished. The Version 3 Information frame format facilitates bridging between this version of the ARINC 429 protocol and IEEE data buses.

If the m_sdu is empty.3. There is not necessarily a one-to-one correspondence between the primitives described herein and the implementation.ARINC SPECIFICATION 429 PART 3 . For a Command frame. but is required for an Information frame.2. COMMENTARY At the time this text was written.e.2. the MA_DATA.2. destination_SAL_address m_sdu.2.2.1 and 3. the length is zero. The destination_SAL_address field for a Command frame should contain a unique SAL.2. the primitive should not initiate a FDU transmission. 3.1 destination_MA_address The destination_MA_address parameter should provide either an individual or a group MAC address when an The service class parameter indicates a quality of service requested by the MAC Service Client.2) COMMENTARY Currently.2 MA_DATA.2.request (optional) MA_CONTROL.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).e. The determination of how to initiate one or the other is Information frame is to be sent.2.Page 16 3. ARINC Specification 664 was in draft state i.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.2. the data and the transmission service (Information or Command). The destination_SAL_ address field contains the SAL to be used for transmitting the FDU. 3.indication MA_CONTROL.indication (optional) The MAC sublayer is depicted in Attachment 18 Figure 18-2.request (destination_MA_address.2. The parameter indicates whether an Information or Command frame should be constructed. These services are local to each device and do not imply any particular implementation at the service interface.request primitive is used to describe how to transmit data that is carried by a MAC frame. 3. These primitives describe the required local information needed to identify the purpose of the incoming or outgoing data transfers. the Command frame (local non-bridgeable frame) and the Information frame (bridgeable frame). They are: MA_DATA.2 Semantics The following parameters are provided with this primitive: MA_DATA. Four primitives are used to describe this interface. 3.2.request should be dropped and the layer management should be informed. Part 1. The destination_SAL_address field for an Information frame can contain either a unique SAL.2.1 Function The MA_DATA.3 m_sdu The m_sdu parameter indicates the MAC service data unit (data content) to be transmitted by the MAC sublayer entity.2.2.request The MA_DATA. which are “Transmission of Information Frame” and “Transmission of Command Frame”. Instead. i.2. the GFI field and Command Type field values are also indicated via this parameter (see Sections 3.2. The format and contents of the destination_MA_address for an Information frame is defined in ARINC Specification 664. Project Paper 664.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL 3. c-17 3. 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.2.3.request primitive should not cause the initiation of a FDU transmission. a multicast SAL or a bridge SAL. 3. Their services are described in the following subsections. If an invalid address is being handed over. The format and content of the SAL is defined in ARINC Specification 429.2. service_class) 3.1 MAC Sublayer Service Specification (cont’d) are described in an abstract way and do not imply any particular implementation or any exposed interface.4 service_ class c-17 . Instead. the MA_DATA. The ARINC 429 MAC protocol provides two classes of service.2. The service is looked at from the transmitting MAC Service Client point of view. The destination_MA_address is not used with a Command frame.request MA_DATA. This section provides all the information needed in order to initiate transfer or process reception of user data or control information. two services have been defined. the MA_DATA.2.2 destination_ SAL _address The destination_SAL_address is required for both Command and Information frames. This information should include the destination.

2.7 service_class The service_class parameter is used to indicate whether an incoming frame is an Information or Command frame. The service is looked at from the receiving MAC Service Client point of view.1 and 3. service_class) 3. 3. 3. which in turn might create a conflict with the implementation.2.3. The source_MA_address parameter is empty when the MA_DATA. source_MA_address source_SAL_address m_sdu. reception_status. the MAC service entity packs the resulting MAC frame into an ARINC 429 “container” consisting of a series of contiguous ARINC 429 32-bit words (See Section 3.request primitive.request primitive.2.e. 3. However. the GFI and command type (CT) information is also passed to the MAC Service Client. The primitive is generated either as the result of a request from a higher layer entity.2.2.3.2. 3. For MAC addressing information refer to ARINC Specification 664.3.3. or internally from the MAC Service Client itself. 3.4 Effect of Receipt Upon receipt of the MA_DATA.3.4.indication primitive defines the transfer of data from a remote MAC Service Client entity to a local peer MAC Service Client entity.1 destination_MA_address The destination_MA_address is obtained from the Information frame and will contain either an individual or a group MAC entity address. needs two addresses in parallel: the IEEE compliant 48-bit destination and source addresses as well as a SAL.ARINC SPECIFICATION 429 PART 3 . There is an implication on the destination address field that originates from the determination of which type of frame to use.2 destination_SAL_address The destination_SAL_address data is obtained from the received FDU for either an Information or Command frame.Page 17 3. at the destination MAC Service Client.3. c-17 3.2. however. It is a request by a MAC Service Client to the local MAC sublayer to transfer a MAC Service Data Unit (m_sdu) to a peer MAC Service Client entity (or entities).3 When Generated The MAC Service Client generates the MA_DATA.indication is generated in response to receiving a Command frame. The Information frame. .2.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL done locally and is a matter of implementation.2.2 Semantics The following parameters are MA_DATA.2.2.indication (destination_MA_address.1) to create a FDU.2.3.4 source_SAL_ address The source_SAL_address is generated by the MAC based on the physical port on which the Information or Command frame was received. This primitive is generated by the MAC entity upon reception of a valid FDU.2.. The destination_MA_address parameter is empty when the MA_DATA.2. and recreation of the MAC frame. The Command frame uses only the unique System Address Label (SAL) that has been defined for Version 1 of this protocol. If it is a Command frame.2.3 MA_DATA.5 m_sdu The m_sdu parameter indicates the MAC service data unit as received by the local MAC sublayer entity. the MAC sublayer first creates the MAC frame by appending any MAC-specific fields (See Section 3. provided with the 3. the mechanics to be used in order to receive data that is carried by a FDU. 3.2.3 source_MA_ address The source_MA_address parameter contains the data c-17 from the source_MA_address field of an incoming FDU that contains an Information frame.2.indication primitive: MA_DATA.indication primitive is used to describe. 3.3. More services might be defined at a later stage.2.3. The content of this parameter is implementation specific.Indication is generated in response to receiving a Command frame 3. Project Paper 664.2. destination_SAL_address.2.1 Function The MA_DATA. Secondly.3. COMMENTARY At the time this text was written.6 reception_status The reception_status parameter is used to pass status information to the MAC Service Client. 3. It transmits the properly formatted FDU to the peer MAC sublayer entity (or entities) by means of the Physical layer services for subsequent transfer to the associated MAC Service Clients.2. care should be taken in selecting the mechanism to forward that information. ARINC Specification 664 was in draft state i.indication The MA_DATA.2).3.

The PAUSE flow control function is defined as optional (O14) for Version 3.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL 3. flow control was provided through the use of BUSY and NCTS word responses to an RTS word. the MAC Control Sublayer examines the Command Type parameter. and is provided as an Option (O14) for the Version 3 protocol.4 Effect of Receipt The effect of receipt by the MAC Service Client is not defined in this document. .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.e.4. the MAC Control sublayer processes the Command frame.3 Clause 31. c. indication.2. Otherwise the Command frame is passed to the MAC Service Client without modification.indication primitive. Figure 18-2 of Attachment 18 depicts the usage of interlayer interfaces by the MAC Control sublayer. If it is set to ‘MAC Control’ (and the first two octets of the m_sdu contain the Pause opcode. the Ethernet compatible PAUSE function is defined at the MAC Control sublayer.2.5 and 3. such as that of the CMU/VDR. The range of possible pause time is 0 to 65535 pause quanta. Sections 3. equal to 512 bit times for the particular implementation. The primitive is reported only if the frame is valid (see Sections 3.12) and then removes the ARINC 429 “container” (i.1 and 3.. The bit time for 100 kilobit high speed ARINC 429 is 10 us. the ARINC 429 32 bit word protocol headers/footers) and combines the resulting data and parameters into a MA_DATA. therefore a pause quanta is 51. The Pause quanta (units of pause time) inhibits transmission of data frames for a specific period of time. Support of MAC control provides for real-time c-17 control and manipulation of MAC sublayer operations.4. 8808 hex). LRUs that support the option (O14) to implement the MAC control sublayer should support the optional MAC service primitives. or the Command frame format for non-bridgeable interfaces. This control sublayer is part of the MAC. Since buffering capacity is limited. 3. and is therefore not bridgeable.2. and a 16-bit request operand. The pause time range for ARINC 429 is then from 5 ms to 327 seconds. (i. the destination_MA_address (for an Information frame) or a2.1.4.e. or approximately 5 ms.1 us.) COMMENTARY IEEE 802. transmission of data frames from a directly connected full-duplex peer system only.request primitive specifies: a1.3.3. The pause time quanta for Williamsburg Version 3 over high speed ARINC 429 is 5 milliseconds.2 states: “The pausetime is measured in units of pause quanta. VDR Mode A uses the MSK modulation scheme so air/ground throughput is somewhat limited and the need for flow control is not anticipated. the ARINC 429 MAC Service Client is AVLC/8208. The PAUSE operation is used to inhibit The size of a MAC Control frame is 32-bits: a 16-bit c-17 (PAUSE opcode).4 MAC Control functions d. Command Type set to MAC Control (for a Command frame) b..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.request primitive is generated by the local MAC Control client to send to its peer. 3. which provides flow control from the CMU to the DSP ground station. to request inhibiting of MAC frame transmissions from another system for a specified period of time.ARINC SPECIFICATION 429 PART 3 . MA_CONTROL. 3. since it is not anticipated that all Version 3 interface implementations.Page 18 3. Frames destined for the MAC control sublayer (MAC Control frames) are distinguished from frames destined for MAC Service Clients by a unique identifier. the PAUSE opcode (8808 hex) a Request_operand indicating the length of time for which it wishes to inhibit data frame transmission and the Destination SAL.5). For Information frames. If it is equal to 8808 hex. but below the MAC Service Client.12 ms.2 us for this media. For Version 3.3. The MAC control function is derived from IEEE 802. will require flow control at the MAC sublayer. These ARINC 429 specific protocol words are not used in Version 3. 1998 Annex 31B. in the event the MAC Service Client can not consume a frame. therefore the pause quanta for high speed ARINC 429 is 5. In the Version 1 protocol. Refer to the appropriate ARINC specification for MAC Service Client definitions. via the MAC sublayer.3. The MAC Sublayer first validates the FDU (see Section 3.1 MA_CONTROL.3.3 When Generated The MA_DATA.2. 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.2. the MAC Control sublayer processes the Information frame. 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.” The bit time for 10 megabit Ethernet is 0. For Command frames. any subsequent frames may be discarded. It is recommended that the pause range be appropriate for the application being supported to prevent adverse effects.request and MA_CONTROL. physically located just above the MAC sublayer. Otherwise the Information frame is passed to the MAC Service Client without modification. For VDL Mode 2. The MA_CONTROL.2. as illustrated.request The MA_CONTROL.4.2.

2 MA_CONTROL.e. 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. If the value of this field is less than or equal to 1500 decimal. sending another PAUSE command with the pause_time = 0 to restart transmission.ARINC SPECIFICATION 429 PART 3 . If the value of this field is equal to or greater than 1536 decimal. Attachment 20 shows the format of the Information frame (and the FDU structure). a.1. ARINC Specification 664 was in draft state i. Notify the local MAC sublayer to stop sending frames to the peer MAC sublayer. it should: a. the length/type field. ARINC Specification 664 was in draft state i.e.. The values and uses of the LLC field are beyond the scope of this specification. or not paused) to the MAC Service Client.. Likewise.3. c-17 b. Refuse frames from the local MAC Service Client until the timer expires. The frame check sequence field has been put into the EOF (see Section 3.4.indication 3.6.e. COMMENTARY At the time this text was written. When the MAC Control sublayer receives a MAC Control frame indicating a Pause condition..3. than the Length/Type field indicates the nature of the MAC Client protocol (Client interpretation). b.3 LLC is assumed.3. Project Paper 664. the source address field.3 Clause 3.3 header. X-ON operation by setting the pause_time to a large value.e.1. then the Length/Type field indicates the number of MAC client data octets contained in the subsequent data field of the frame (Length interpretation).2.3). and restart the timer. This 2-octet field takes one of two meanings. It does not include the address fields. the use of IEEE 802.1 Length If the Length/Type field is a Length value. The source address field identifies the MAC entity from which the FDU is initiated.3 MAC Frame Structures This section defines in detail the MAC frame structures for ARINC 429 using MAC procedures. Each MAC Information frame contains two address fields: the destination and the source address field. Project Paper 664.3. COMMENTARY At the time this text was written.e. 3. Of these 5 fields all except the data field are of fixed length. c. if nonzero.2.8) words.. Length indicates the total number of octets in the data field of the frame.4. The MAC sublayer should complete a frame transmission in progress. Each address field contains 48 bits (i. Notify the local MAC Service Client of the Pause condition. d.1 Information Frame Format The MAC Information frame comprises 5 fields: the destination address field. paused. the length/type field.4. c. A Pause value of 0 terminates the Pause and restores normal operation. Valid values for length are between 1 and 1500. When the pause timer expires the MAC Service Client should be notified. The destination field specifies the MAC entity (or entities) for which the FDU is intended.2. It describes the general method for representing station addresses as well as ARINC 429 specific System Address Labels (see Section 3. the data field and the frame check sequence field. values between 1500 and 1536) c-17 3. Any other value of this field is considered undefined (i.. An implementation that does terminate transmission mid frame will cause Timer T17 in the receiver to time out. .1. 3.Page 19 3.2 Length/Type Field The Length/Type Field is defined in IEEE 802. six octets). then when convenient.1 Address fields The MA_CONTROL. depending on its numeric value. 3. Due to the transmission scheme used no preamble or delimiter fields are required as with other technologies. they are constructed the same way. Refer to ARINC Specification 664 for the MAC address specification for Information frames. and the LLC header should immediately follow the IEEE 802. or the FCS field. 3.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL COMMENTARY In typical operation the PAUSE function can be used in an X-OFF. 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. In this case the MAC Client is defined to be the LLC service entity.indication primitive indicates the status of the local PAUSE operation (i. For the construction of the MAC address fields see ARINC Specification 664. Start timer of duration indicated in the MAC Control frame. 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. It defines the relative positions of the various components of the MAC frame.

Project Paper 664. c-17 .2 Command Frame Format For a MAC Command frame the following four fields are needed: a. 3.2.4.8).indication to the MAC Service Client.4. See Section 2. Valid values for the type field are defined in ARINC Specification 664.1 GFI Field In order to retain as much compatibility with ARINC 429 Williamsburg Version 1 as possible.. Length/Type field and data field. The integrator is cautioned to be aware of applications that utilize the interface in which Option 15 has not been selected. and the reason for declaring it invalid. Attachment 19 shows the format of the Command frame (and FDU) structure.3. the frame check field has been put into the EOF word (See Section 3.Page 20 3.3. For the definition of the SAL see Section 3. Full data transparency is provided in the sense that any arbitrary sequence of octet values may appear in the data field. 3.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL 3.2. 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. If not used for containing the CRC. The FCS is calculated by the transmitting MAC Service Entity and appended to the MAC frame.1. the GFI field has been retained in the SOF word.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 32bit (4-octet) CRC value. If the GFI field is not used. this field is set to binary zeroes. 3. This indicates that the source MAC Service Entity does not calculate the CRC for this field.3.e. 3. the Command Type field. the GFI field .3. COMMENTARY At the time this text was written.5. ARINC Specification 664 was in draft state i.3.2 Invalid Length/Type If the value in the Length/Type field is not a valid value as defined in section 3.3 is 1500 bytes for the payload of an Ethernet frame (i.1. In order to retain as much compatibility with ARINC 429 Williamsburg processing as possible. Of these four fields all except the data field are fixed length. c. the Data field and d.1.ARINC SPECIFICATION 429 PART 3 . If Option O15 is not selected. 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.. the m_sdu size of an Ethernet frame).3 Data Field The data field can contain up to 2536 (2550-14) octets. It relies on the ARINC 429 SAL for addressing.3.e.1.5.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.1 and is not a known Type value then the MAC frame is considered invalid.4.5 for the definition of GFI. COMMENTARY Not implementing (generating and validating) a Frame Check Sequence in the Information frame may have negative consequences on system integrity. the number of data field octets should be limited to 1500 in order to allow bridging to Ethernet-based c-17 networks. If the 32-bit FCS is invalid.1. 3. b. The contents of invalid MAC frames should not be passed to the local MAC Service Client. This value is computed as a function of the contents of the source address field.5.3.3.1. however reception of an invalid frame.3. 3. 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.1.3. the Frame Check Sequence field.3. 3. The following subsections The Command frame does not contain separate address fields like the Information frame. should be indicated to the MAC Service Client. 3. the 32 bit CRC will not be generated or evaluated across the interface. list the conditions for which the Information frame is said to be invalid.1.9.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.2. destination address field.3 Invalid FCS The receiving MAC sublayer should verify the 32-bit FCS of the received MAC frame. The receiving system should check that CRC non-generation (O15) has been selected for this port.1 Length (cont’d) COMMENTARY (cont’d) The maximum size permitted by IEEE 802. However. the MAC frame is also invalid The value of binary zero in the FCS field is a unique and valid FCS if CRC generation (O15) is not selected.1.2. 3. The encoding is performed by the generating polynomial as defined in Section 3. 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.1 Invalid Address Address checking should be performed according to ARINC Specification 664.

the data words containing the MAC frame. 3.e. For situations where a system will need to communicate with another system. The interpretation of those bits is not a part of this specification. The MAC frame (See Section 3. The listing of SAL assignments can be found in Attachment 11 to ARINC Specification 429. the total number of ARINC 429 words to be sent (word count) is calculated. In order to identify the intended recipient of a transmission. 3. COMMENTARY Similar to the Bridge SAL.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. For situations. or a data message (such as a VDL Mode frame transmitted across a CMU/VDR interface). learned bridging table. The initial data word of each FDU is a Start of Frame (SOF) data word (see Section 3. c-17 c-18 c-17 . in some cases.3.2.3) is contained within the data words that follow.3. The bridge will accept all FDUs and afterwards selects how to handle them based upon a predefined or. 3. The encoding is performed by the generating polynomial as defined in Section 3.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. 3.4. When a system sends a FDU to another system. Apart from existing system specific unique SALs. the MAC frame is also invalid. The octets may be set to any possible binary value.3 Data Field The Data field contains up to 2552 octets. Generally. a Multicast SAL will be used This SAL can only be used for the transmission of Information frames. two universally applicable SALs have been defined: the Multicast SAL (MSAL) and the Bridge SAL (BSAL).4.2 Frame Data Unit (FDU) Size and Word Count The FDU word count is the sum of the SOF word.8).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. The only restriction is that the bits be organized into full 8 bit octets. the Multicast SAL assures that no compatibility conflict will arise with other systems.3.4. control message. 3. a system needs to examine the MAC destination address contained in the FDU. It is the responsibility of each individual system to determine whether or not to accept the FDU being received. is not attached to an ARINC 429 bus. 3. the Label field (bits 1-8) is used to carry a System Address Label (SAL).4. When a FDU is organized for transmission.6).2. the data received should be ignored. and the EOF word(s). 3.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL 3. If the 16-bit FCS is invalid. each containing the System Address Label (see Section 3. A FDU can be either an Information frame or a Command frame. A Frame Data Unit (FDU) contains binary encoded octets.4 MAC Transmit/Receive Functions This section defines the functions to transmit and receive the contents of FDUs on the physical medium. COMMENTARY The Bridge SAL assumes that no compatibility conflict will arise with other systems. i.3) of the sink.3 System Address Labels (SALs) Each on-board system attached to an ARINC 429 bus that requires aperiodic message capability is assigned a System Address Label (SAL). local or remote (beyond the bridge). In this case. The Frame Data Unit (FDU) may vary in size from a minimum of When a system receives any data containing its SAL that is not sent through the established conventions of this protocol. 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. The FDU is concluded with one or two consecutive End of Frame (EOF) words (see Section 3. It is also known as the interface to the Physical layer. it addresses all attached systems.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 16bit (2-octet) CRC value. even though other systems may be connected and listening to the output of a transmitting system. where multiple systems will need to be addressed at the same time.4. Full data transparency is provided in the sense that any arbitrary sequence of octet values may appear in the data field. a Bridge SAL will be used.2. a a a 2 three.2. FDUs are sent point-to-point. Part 1.1 Invalid FCS The receiving MAC sublayer should verify the 16-bit FCS of the received MAC frame. These SAL´s are designated for Information frames only and should not be used for Command frames.3. 3..ARINC SPECIFICATION 429 PART 3 .4.4. The FDU contains any string of bits desired.Page 21 3.5. to a maximum of 1023 ARINC 429 words (including the SOF and EOF words). The following subsection lists the condition for which the Command frame is said to be invalid. A FDU always consists of no more than one frame. This value is computed as a function of the contents of the data field.9.3.2. which has no SAL assigned. The contents of invalid MAC frames should not be passed to the MAC Service Client.

For a description of the Frame Data Units (FDUs) which contain these two types of MAC frames.6. The GFI field is used in Version 3 as an indicator to the MAC Service Client of the format of data words to follow.4.6.2 Reserved Bits Bits 28-21 of the SOF word for the Information FDU are reserved (not used). 3. See Attachment 11. and two EOF words.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.4.2 Information SOF word The SOF word for the Information Frame Data Unit contains a 10-bit word count. The Word Type field is used to identify the function of each ARINC 429 data word used by the bit-oriented communication protocol. For the Command frame.ARINC SPECIFICATION 429 PART 3 .0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL 3. bits 20-19 of the SOF word (for both Information and Command FDU) carry the following discriminator: Bit 20 0 0 1 1 Bit 19 0 1 0 1 Definition Information frame Command frame Reserved Reserved frame.6 Start of Frame (SOF) When a system wants to transmit either an Information Frame Data Unit or a Command Frame Data Unit.4.4.4.3. immediately followed by the data words.4. seven data words. a 2-bit Reserved field.2.6. 3. The source should not exceed a maximum average of 40 bit times between data words of a FDU. The sink should be capable of receiving the FDU with the minimum word gap of 4 bit times between words.5.4. An Information FDU with the minimum word count would contain one SOF word. The minimum word count value is 3 ARINC 429 words. 3. An Information FDU with the maximum word count value would contain one SOF word. In order to distinguish between Information and Command frames.6.4 Command Type Field (CT) For the Command Frame Data Unit (FDU). It’s function is similar to the General Format Identifier described in Section 2.3 Command SOF word The SOF word for the Command frame Data Unit contains a 10-bit word count.1) and an 8bit Reserved field.4.Page 22 3.6. a Command Type (CT) field occupies bits 24-23 of the SOF word. the system should start by sending the Start of Frame (SOF) data word.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. 3. The source should introduce a gap between the end of each ARINC 429 word transmitted and the beginning of the next. 3.6.3. The minimum word count value is 10 ARINC 429 words. a 2-bit Information/Command (I/C) frame field (described in Section 3. the maximum word count value is 1023 ARINC 429 words. To identify the different frame types.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.3.5 Word Type The Word Type field occupies bit 31-29 in all bit-oriented FDU words. 3. The format of the SOF word differs between Information and Command FDUs. 3. 3. Tables 11-8 and 11-10 for a description of these two words. a 2-bit Information/Command (I/C) frame field (as described in Section 3. a General Format Identifier (GFI) occupies bits 28-25 of the SOF word.4. 3. A Command FDU with the minimum word count would contain one SOF word.4.4. For the Information . 1020 data words and two EOF words. 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.1).1 of the Version 1 bit-oriented protocol. A Command FDU with the maximum word count value would contain one SOF word.6.4.6. These bits should be set to binary zeroes.4 Bit Rate and Word Timing c-18 Data transfer should operate at the low or high-speed rate as defined in Part 1 of ARINC Specification 429 depending on the value of Option 2 (see Table 10-3b).3. word types 010 and 011.4. a 2-bit Command Type Field and a 4-bit General Format Identifier (GFI) field. There are two new word types for the Version 3 protocol.6. The purpose of the CT field is to facilitate the differentiation of FDUs by functional context.2. which contain the contents of the MAC frame. The gap should be at least 4 bit times (minimum). See Table 11-1A of Attachment 11 for a description of the Word Type field.6. see Attachments 19 and 20.1 Word Count 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. the maximum word count value is 1023 ARINC 429 words. The following values have been assigned: c-17 c-17 c-17 3.10. 3.4.3 General Format Identifier Field (GFI) For the Command Frame Data Unit (FDU). 1021 data words and one EOF word. one data word and one EOF word. the SOF word contains an Information/Command Frame field.

The octets of the FDU are encoded and transmitted in 32-bit data words. the least significant semi-octet goes in the last (n5) semi-octet of the current data field. depending upon the nature of the FDU. 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. three.4.9 Frame Check Sequence For a Command frame.Page 23 3. The format and number of EOF word(s) differ between Information and Command frames. in the process of placing the octets into the data words. and the procedure for calculation of the 32-bit CRC is identical 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. However.5.17. Each FDU. 3. two. prior to transmission. Tables 11-9 and 11-11 for the definition of these words. The octets of the data file are divided into two semi-octets and placed sequentially into the data words. See Attachment 11. each FDU contains a CRC check.12. may be used in the Version 3 protocol. or four bits in length. two or three bits are invalid. as defined in this section. The number of semi-octets in a partial data word is indicated in bits 28-25 of the word. For an Information frame.4.e.7.2 Partial Data Word(s) Bit 24 0 0 1 1 Bit 23 0 1 0 1 Meaning Command Data MAC Control reserved A Partial Data Word contains from one to four semioctets.1 and 2. some applications may require high data integrity to be confirmed by an error checking mechanism. The protocols and procedures to implement this mechanism are not part of this specification. Partial Data Words should be used only when they are required to complete the data for a FDU transmission. 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). If the end of the FDU does not completely fill the last Full Data Word. one. Binary data words of five semi-octets are called Full Data words.4.1 Full Data Word(s) A Full Data Word has 20 bits available for data.ARINC SPECIFICATION 429 PART 3 .4. . A semi-octet (or nibble) is half of an octet. 3. the Frame Check Sequence field of the EOF word contains a 16-bit CRC as defined in Sections 2. The most significant semi-octet follows in the first (n1) semi-octet of the data field of the next word.4. as defined in the Williamsburg Version 1 protocol in Section 2. See Tables 11-2 and 11-3 of Attachment 11 for data word formats.5. For an Information frame the EOF words contain a frame check sequence which consists of a 32-bit Cyclic c-17 Redundancy Check (CRC). four and five semi-octets.3 SOLO Words SOLO words. The use of the CRC in this case does not imply any inherent lack of integrity of the ARINC 429 link.2 of the Version 1 bitoriented protocol.7. a Partial Data Word (see Section 3. and are identical with the data words used in Version 1 of the bit-oriented protocol. the Frame Check Sequence field of the EOF words contains a 32bit CRC. Only full four-bit semi-octets can be sent. However. Binary data words may contain one. Both CRC polynomials are referenced in ISO 3309. Since the transfer of data using a file transfer protocol contains no provision for automatic refresh.12.7.4. If. in conjunction with Command frames). 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.7. 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. Data words immediately follow the SOF word. 3. should conclude (end) with a complete octet. There are two basic types of data words: full binary and partial binary. The least significant bit of the least significant semi-octet is sent first. This space is allocated in five semi-octets. For this reason. the first six data words of an Information MAC frame data unit contains additional MAC c-17 addressing and length/type information.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL 3. In order to obtain maximum system efficiency. 3. The final FDU bit is always set for consistency with Version 1.5. Partial Data Word semi-octets are sent in the same order as the semi-octets in a full data word.2) should be used to complete the FDU transmission. The unused semioctets in the partial data word should be set to binary zeros.8 End of Frame (EOF) Each FDU transfer is terminated by one or two End of Frame (EOF) word(s).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. 3. an octet is split between two different words. Simple parametric data is usually transmitted at a refresh rate high enough to permit recognition and suppression of erroneous data. Binary data words of fewer than five semi-octets are called Partial Binary Data words. they should be used only across nonbridgeable interfaces (i.4.

If the ALOHA Response contains a version that does not match the ALO version. error-free message will result in a unique. added to the product.Page 24 3. The sink will start the T17 timer when it receives a respective SOF word. The only implementation differences are found in the length and format of the two generator polynomials and length of the CRCs. Note: The addition of xk (x31 + x30 + x29 + x28 + . The most significant bit (MSB) of the 32-bit CRC sequence for Information frames is transmitted first.ARINC SPECIFICATION 429 PART 3 .2 32-Bit CRC Decoding 32 Decoding of the CRC at the receiver is as follows: At the receiver. corresponds to initializing the initial remainder to a value of all “ones”. In case of a Command frame the T17 timer is stopped when a single valid EOF word is received. the CRC is added to the x G(x) product. The generator polynomial for the 32-bit CRC is of the form.. the sink should discard any partial frame already received and ignore any data until a proper SOF word is received.4. 3. For example.9.4. R(x). if the data stream is 1010001.4. M(x)) is error free. the SOF and EOF words. + x3 + x2 + x + 1) P(x) = Qr(x) + Rr(x) P(x) The Incomplete FDU (T17) timer is used to insure that a source device does not “lock-up” a sink with an incomplete frame. M(x). Rr(x) will be: x32M(x) + xn (x31 + x30 + x29 + x28 + .. 3.4.+ x3 + x2 + x + 1) P(x) = Q(x) + R(x) P(x) 1100 0111 0000 0100 1101 1101 0111 1011 (coefficients of x31 through x0 . COMMENTARY The notation used to describe the CRC is based on the property of cyclic codes that any code vector. If the source device is able to adapt to the differences in protocol version. then the remainder. the incoming M(x) is multiplied by x32. obtained from the modulo 2 division of: x32G(x) + xk (x31 + x30 + x29 + x28 +….4. resulting in the message. these coefficients can have the value 0 or 1 and all polynomial operations are performed modulo 2.. The complementing of R(x).1. by the transmitter. At the transmitter.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. can be represented by a polynomial G(x) = x12 + x5 + 1. of length n where: n M(x) = k + 32. xn (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)). When T17 is exceeded...11 ALOHA The first ALOHA word transmitted in a sequence should contain the highest Version Number supported by the source device. file transfers may proceed using the protocol version identified in the ALR word. such as 1000000100001.9 Frame Check Sequence (cont’d) to that of the 16-bit CRC. respectively). + x3 + x2 + x + 1) and divided by P(x) as follows: .. at the completion of the division ensures that the received. In this application. 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.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL 3. 3. In case of an Information frame the T17 timer is stopped when both valid EOF words are received. where k is the number of data bits in the frame existing between.. The T17 timer should also be stopped if the sink discards the partial frame for other reasons defined in this specification. and = x32 G(x) + R(x) = x32 G(x) + CRC 3. 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.9. non-zero remainder at the receiver. 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.10 Incomplete FDU Timer If the transmission of the serial incoming bits plus CRC (i. but not including. The elements of an n element code word are thus the coefficients of a polynomial of order n . G(x).e. the source device should take one of the following actions: a.

4.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL b. the receiving unit should take no action and ignore the word. the actual word count will not match the expected word count (and the CRC will probably be invalid). The SOF. it should discard any partial FDU it had received. Two EOF words should follow the transmission of the final data words of an Information MAC frame. the receiving MAC sublayer should verify that the actual number of words received is the number of words expected.1. If either a protocol version is found or none of the protocol versions match. then the MAC frame is invalid. If either or both are missing.indication with its reception_status set to notify a reset condition. as per bits 18-9 of the SOF word. which the FDU is said to be invalid in addition to the conditions already identified in sections 3. One EOF word should follow the transmission of the final data words of a Command MAC frame.4. or is not formatted as depicted in Attachment 11. If the word counts do not match.Page 25 3.5.3 Parity Errors Bit 32 of each ARINC 429 word should be set to odd parity for the entire word. the MAC frame is invalid.12.1 Missing SOF Word The Information SOF word should be formatted as depicted in Attachment 11.3. Table 11-9.3. it should leave its present task and respond within T15 with an ALR word. See Attachment 17.12. 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.12. Table 11-9. 3. Table 11-4. 3. Upon receipt of a word. it cannot be sure of the intended label. If the word count is incorrect (or if the CRC is invalid). The word may not even be a part of the FDU.12. the MAC frame is invalid.4 Word Count Errors The receiving MAC sublayer should determine the validity of the incoming Start of Frame (SOF) word. The contents of invalid MAC frames should not be passed to the local MAC Service Client. c-17 with bit 17 as the most significant bit and bit 24 as the least significant bit of the Subsystem SAL. When the system only supports bit-oriented protocols. Table 11-11.4 for invalid frames. 3. It should be formatted as depicted in Attachment 11. the source should notify the local MAC Service Client with a MA_DATA. The parameter in the primitive only has local significance and provides the MAC Service Client with status information.4. then the MAC frame is invalid. If the device was in the source mode (had already begun transmitting a FDU).5 and 3.12.ARINC SPECIFICATION 429 PART 3 . COMMENTARY When the receiving MAC sublayer receives a word with bad parity. A device that supports the bit-oriented Link layer protocol should always be able to respond to the receipt of the ALO word. The ALR response should reflect the device’s protocol version level by the way of the Version Number contained within the ALR word. then the MAC frame is also invalid. it should resend the FDU beginning with the first word of the FDU. If any word is received with even parity. the receiving unit should verify that each word was received with odd parity. then when the EOF word(s) are received.5.4. The ALO/ALR protocol determination process should continue until a common protocol version is found. Because Option O12 is selected. Table 11-8 and should be the first word of the transmitted command FDU.4. as per Sections 3. The protocol determination process will continue until a common protocol is found.19. If the device was in the sink mode (had already begun receiving a FDU). If the Version Number of the ALO does not match the sink device’s protocol Version Number. Table 11-10 and should be the first word of the transmitted information FDU. and EOF are collectively referred to as a Frame Data Unit (FDU). If the offending word was intended to be a part of the FDU. The following subsections list conditions for Upon receipt of the final EOF word of the FDU. it should repeat the process described in this section. Whenever a device receives the ALO word.1. If it is missing. 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). there may still be a chance of a successful FDU transfer.5. and the End of Frame (EOF) words before passing the MAC frame to its local Service Client. the MAC frame. The Command SOF word should be formatted as depicted in Attachment 11.12. MAC frame. then the process defined in Section 2. If the source device is not able to adapt to the differences in protocol version. or are not formatted as depicted in Attachment 11. 3.3 and 3.4.5 and 3.2 should be followed.2. Table 11-11. If the SOF word is not received as the first word.1 for invalid CRC). so by ignoring the offending word.3.12 Validation of FDUs 3.2.4 (or Sections 3.2 Missing EOF Word(s) When the system also supports character oriented protocols. This field should contain the SAL of the device sending the ALOHA word.3. The ALOHA word should contain a Subsystem SAL field as shown in Attachment 11. They should be formatted as depicted in Attachment 11. 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. c-17 .4.

13 Inter-FDU Gap Time An inter-Frame Data Unit gap time. the MAC frame is also invalid and should be discarded. If a CRC is not to be generated (O15 = No).0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL 3. this timer is not necessary and implementation is optional. Timer T18 is closely related to the generation of the CRC field for the Information frame. . the receiving MAC sublayer should verify the CRC of the received MAC frame.5 CRC Errors Upon receipt of the final EOF word of the FDU. c-17 The FDU should contain an integral number of octets in order to pass the FCS. If the CRC is invalid.4.12. 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. T18.ARINC SPECIFICATION 429 PART 3 .Page 26 3.4. 3.

These attachment numbers are not used to maintain consistency with previous versions of ARINC Specification c-16 429.9 Attachments 1 through 9 are included in ARINC Specification 429 Part 1 and therefore are not used in ARINC Specification 429.ARINC SPECIFICATION 429 PART 3 . . Part 3.Page 27 ATTACHMENTS 1 .

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 N1 N2 N3 c-16 N4 N5 N6 MAX NUMBER OF RTS REPEATS FOLLOWING NCTS MAX NUMBER OF RTS REPEATS FOLLOWING BUSY MAX NUMBER OF RTS REPEATS FOLLOWING NO RESPONSE NUMBER OF NAK WORDS RECEIVED BEFORE DECLARING FAILURE OF COMMUNICATION NUMBER OF SYN WORDS RECEIVED BEFORE DECLARING FAILURE OF COMMUNICATION MAX NUMBER OF ALO REPEATS FOLLOWING NO RESPONSE STANDARD VALUE [1] 5 20 5 3 3 3 Table 10-2 BIT-ORIENTED PROTOCOL APPLICATION SELECTION APPLICATION CONDITION A1 A2 A3 WHEN T2 N1 EXCEEDED WHEN T4 N2 EXCEEDED WHEN T5 N3 EXCEEDED STANDARD ACTIONS REPORT TO HIGHER LEVEL ENTITY REPORT TO HIGHER LEVEL ENTITY REPORT TO HIGHER LEVEL ENTITY c-16 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 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 .

the standard interface for option 2 (429 bus speed) defaults to low speed for version 1 systems. [5] 03 and 04 should be Yes for expedited file transfer. See Section 2. or into an Information FDU if Option 13 is set to ‘Information Frame’. such as the CMU/VDR VDL Mode 2 Interface.3.5. For example.Page 29 ATTACHMENT 10 VARIABLES OF BIT-ORIENTED PROTOCOL Table 10-3b . If T10 is not used. unless high speed is specified in equipment specifications. it is intended that a working system has minimized actual response times. Notes 6 7 7 8 c-17 . For example: A system should reply with CTS as soon as possible after reception of RTS. Option 13 is set to ‘Command Frame’. [6] The SOLO Word is not bridgeable to Ethernet and should only be used in conjunction with Command frame (nonbridgeable) interfaces. For a point to point only interface. T16 should be used. [4] Implementation of timer T10 is optional.’ If the Pause Function option is selected as ‘Yes’. Values shown as N/A indicate that option cannot be used. Option 13 is set to ‘Information frame.BIT-ORIENTED PROTOCOL OPTIONS FOR VERSION 3 Option Description Standard Interface [1] 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 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 O14 Use of Pause Function O15 Generation (Yes) or Non-generation (No) of 32 Yes 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. It is not intended that a system take the maximum time T1 to reply to the RTS on a routine basis.7. [2] For those timers that are not associated with a repeat sequence.ARINC SPECIFICATION 429 PART 3 . [8] Selection of Option 15 is dependent on the applicable equipment interface specification. then the Pause function will be formatted into a Command FDU if Option 13 is set to ‘Command Frame’. [3] T6 and T7 are used when Option 5 (O5) is not selected. For equipment interfaces that may need to be bridgeable to Ethernet. [7] Options 13 and 14 are dependent on the applicable equipment interface specification.

7 sec Goal for Sink Timer for Source Goal for Sink Timer for Source Timer for Source Goal for Source Goal for Source Goal for Sink Timer for Sink 3 3 2 2 2 REFERENCE 2.19.5.5.19.16 2.5.5.8.5.14.8.Page 30 ATTACHMENT 10 VARIABLES OF BIT-ORIENTED PROTOCOL Table 10-4 VARIABLES OF LOW SPEED BIT-ORIENTED PROTOCOL .10 T14 T15 T16 2 min 0ms 220 ms 2.1 2.5.0 sec 100 ms 250 ms 200 ms Timer for Source Goal for Sink Timer for Source Goal for Source 4 2 2.6 2.1 2.1 2.5.1 2 2.13 2.3 2.2 min 180 ms 330 ms Timer for Sink Goal for Sink Timer for Source 2 2.3 2.2 2.ARINC SPECIFICATION 429 PART 3 .5.17.7 sec 0 ms 200 ms 0 ms 3.7 2.7.3 2.5.7.5.5.13.2 2.7.5.5.4 2.7.5.16 .13.5.1.5 sec 100 ms 700 ms 100 ms 18 sec 700 ms 500 ms 100 ms 200 ms 2.5.VERSION 1 TIMER OR DESIGN GOAL FOR SOURCE OR MIN MAX SINK NOTES TIME DESCRIPTION VALUE VALUE T1 T2 T3 T4 T5 T6 T7 T8 T9 c-16 T10 T11 T12 T13 CTS/NCTS Send Time RTS Repeat Time After Receipt of NCTS Busy Send Time RTS Repeat Time After Receipt of Busy RTS Repeat Time If No Response Time of Random Timer to Resolve RTS Conflicts Increment of Time T6 ACK/NAK/SYN Send Time LDU Timeout Following CTS ACK/NAK Timeout Loop Back Send Time ALO Repeat Time if No Response to ALO SOT Send Time After Receipt of CTS Incomplete File Timeout ALR Send Time ACK/NAK Timeout After EOT 0 ms 500 ms 0 ms 15 sec 500 ms 50 ms 10 ms 0 ms 2.2 2.5.

7 2.10 T14 T15 T16 10 sec 0 ms 220 ms 11 sec 180 ms 330 ms Timer for Sink Goal for Sink Timer for Source 2 2.5.ARINC SPECIFICATION 429 PART 3 .5.5.2 2.19.4 2.5.2 2.5.2 sec 200 ms 500 ms 100 ms 200 ms 440 ms Goal for Sink Timer for Source Goal for Sink Timer for Source Timer for Source Goal for Source Goal for Source Goal for Sink Timer for Sink 3 3 2 2 2 REFERENCE 2.8.5.13 2.5.5.7.5.1 2.5.1 2.6 T10 T11 T12 T13 600 ms 0 ms 200 ms 0 ms 660 ms 100 ms 250 ms 100 ms Timer for Source Goal for Sink Timer for Source Goal for Source 4 2 2.14.5.VERSION 1 TIMER OR DESIGN GOAL FOR SOURCE MIN MAX OR SINK NOTES TIME DESCRIPTION VALUE VALUE T1 T2 T3 T4 T5 T6 T7 T8 T9 CTS/NCTS Send Time RTS Repeat Time After Receipt of NCTS Busy Send Time RTS Repeat Time After Receipt of Busy RTS Repeat Time If No Response Time of Random Timer to Resolve RTS Conflicts Increment of Time T6 ACK/NAK/SYN Send Time LDU Timeout Following CTS ACK/NAK Timeout After CTS Loop Back Send Time ALO Repeat Time if No Response to ALO SOT Send Time After Receipt of CTS Incomplete File Timeout ALR Send Time ACK/NAK Timeout After EOT 0 ms 100 ms 0 ms 1.5.13.5.1 2.3 2.0 sec 150 ms 50 ms 10 ms 0 ms 400 ms 100 ms 140 ms 100 ms 1.1.19.1 c-16 2 2.16 2.7.16 .5.5.7.13.3 2.17.8.5.7.5.2 2.3 2.Page 31 ATTACHMENT 10 VARIABLES OF BIT-ORIENTED PROTOCOL Table 10-5 VARIABLES OF HIGH SPEED BIT-ORIENTED PROTOCOL .

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. Incomplete FDU Timeout Inter-FDU Gap Time 750 ms 10 ms 1 sec N/A Timer for Sink Timer for Source 1 ALR Send Time 0 ms 180 ms Goal for Sink ALO Repeat Time if No Response to ALO 200 ms 250 ms Timer for Source . hours!). minutes. 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.ARINC SPECIFICATION 429 PART 3 .VARIABLES OF HIGH SPEED CONNECTIONLESS BIT-ORIENTED PROTOCOL . If the LRU does not have another FDU to transmit then this gap will be very large (seconds.Page 32 ATTACHMENT 10 VARIABLES OF BIT-ORIENTED PROTOCOL Table 10-6 .VERSION 3 NOTES REFERENCE TIME DESCRIPTION MIN VALUE MAX VALUE TIMER OR DESIGN GOAL FOR SOURCE OR SINK T1 T2 T3 T4 T5 T6 T7 c-17 T8 T9 T10 T11 T12 T13 T14 T15 T16 T17 T18 NOTE: [1] The minimum value is specified to give the sink time to finish processing an FDU before the next FDU arrives.

ARINC SPECIFICATION 429 PART 3 .5 seconds 10 ms 1 sec N/A Timer for Sink Timer for Source 1 ALR Send Time 0 ms 180 ms Goal for Sink ALO Repeat Time if No Response to ALO 200 ms 250 ms Timer for Source c-18 .VERSION 3 c-16 TIME DESCRIPTION MIN VALUE MAX VALUE TIMER OR DESIGN GOAL FOR SOURCE OR SINK NOTES REFERENCE T1 T2 T3 T4 T5 T6 T7 T8 T9 T10 T11 T12 T13 T14 T15 T16 T17 T18 NOTE: [1] The minimum value is specified to give the sink time to finish processing an FDU before the next FDU arrives. hours!). 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. minutes. Incomplete FDU Timeout Inter-FDU Gap Time 7. If the LRU does not have another FDU to transmit then this gap will be very large (seconds. 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.Page 33 ATTACHMENT 10 VARIABLES OF BIT-ORIENTED PROTOCOL Table 10-7 VARIABLES OF LOW SPEED CONNECTIONLESS BIT-ORIENTED PROTOCOL .

Implementation of timer T10 is optional. Values shown as N/A indicate that option cannot be used. It is not intended that a system take the maximum time T1 to reply to the RTS on a routine basis. For example. O3 and O4 should be Yes for expedited file transfer.Page 34 ATTACHMENT 10 VARIABLES OF BIT-ORIENTED PROTOCOL NOTES: 1 c-16 2 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 those timers that are not associated with a repeat sequence. 3 4 c-16 5 .ARINC SPECIFICATION 429 PART 3 . See Section 2. If T10 is not used. T6 and T7 are used when Option 5 (O5) is not selected. unless high speed is specified in equipment specifications.3.5. T16 should be used. the standard interface for option 2 (429 bus speed) defaults to low speed for version 1 systems. 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.7.

[10] 1 0 0 1 File Sequence Number Status Code [6] 8 7 6 5 4 SAL SAL SAL SAL SAL SAL SAL SAL SAL 3 2 1 P 1 0 P 1 0 c-16 . 1 0 0 Destination Code . Control P Word Type Data or Word DATA SAL Type Extensions c-16 Table 11-1A WORD TYPE 31 0 0 0 0 1 1 1 1 30 0 0 1 1 0 0 1 1 29 0 1 0 1 0 1 0 1 WORD TYPE Full Binary Data Word Partial Binary Data Word Start of Frame – Version 3 End of Frame – Version 3 Protocol Word Solo Word Start Of Transmission – Version 1 End Of Transmission – Version 1 c-16 Table 11-2 FULL DATA WORD BIT [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 P 0 0 0 n5 n4 n3 n2 n1 4 3 2 1 SAL Table 11-3 PARTIAL DATA WORD BIT [2] [3] 32 P P P P 31 0 0 0 0 30 29 28 0 1 1 0 1 1 0 1 1 0 1 1 27 0 0 0 0 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 n1 0 1 0 0 0 0 0 0 0 0 n2 n1 1 0 0 0 0 0 n3 n2 n1 1 1 n4 n3 n2 n1 8 7 6 5 4 SAL SAL SAL SAL 3 2 1 Table 11-4 PROTOCOL WORD BIT RTS CTS NCTS BUSY NAK ACK AL0 ALR SYN 32 P P P P P P P 31 1 1 1 1 1 1 1 30 29 28 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 0 0 1 Destination Code [4] Word Count [5] 0 1 0 Destination Code . Status Code [6] .ARINC SPECIFICATION 429 PART 3 . 1 0 1 File Sequence Number Status Code 1 1 0 File Sequence Number LDU Sequence Number 1 1 1 Subsystem SAL [7] 0 0 0 0 Version No.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 [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 GFI. Status Code . Word Count . [10] 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Version No. 0 1 1 Destination Code .

D.0 of ARINC 429.6 of ARINC 429. Part 3 Section 3. Part 3 Obsolete. Part 3 Changes to Sec. 2. 2.5 by Supplement 12 of ARINC 429. 16-Bit Data Field 7 6 5 4 SAL SAL SAL 3 2 1 Table 11-6 START OF TRANSMISSION BIT SOT 32 31 P 1 30 1 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 0 GFI File Sequence Number LDU Sequence Number 7 6 5 4 SAL 3 2 1 c-16 . 1 1 1 1 0 1 10 0 0 1 1 0 9 0 1 0 1 0 APPLICABILITY Changes to Sec.ARINC SPECIFICATION 429 PART 3 .5 through Supplement 16 of ARINC 429. formerly defined in Sec. Part 3 Reserved Reserved Reserved Reserved Reserved NOTES 8 8 c-16 Table 11-4B ALO-ALR WINDOW SIZE c-16 This table deleted by Supplement 16.Page 36 ATTACHMENT 11 BIT-ORIENTED DATA FILE TRANSFER WORD FORMATS Table 11-4A ALO-ALR VERSION NUMBER (See Appendix H) 12 0 0 0 0 0 1 1 11 0 0 0 0 1 . . Table 11-5 SOLO WORD BIT TEST LOOP SOLO 32 P P P 31 1 1 1 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 0 1 0 0 0 0 16-Bit Test Pattern 0 1 0 0 0 1 16-Bit Loop Back 0 1 I. 2.

the GFI value (0000) is discouraged. The data format for the GFI ‘0000’ is unique to that particular interface and is not defined herein. 27 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 26 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 25 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 Description Reserved Reserved Command-Control Data General Purpose Bit-Oriented Protocol (GPBOP) ISO 9577 Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved ACARS VHF Format Extended GFI Notes 1 c-17 Table 11-7 END OF TRANSMISSION BIT EOT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 1 1 1 0 0 0 X LSB Cyclic Redundancy Check (CRC) 9 11 10 9 MSB 8 7 6 5 4 3 2 1 SAL c-14 NOTE: Bit 25 of the EOT is the final LDU bit.Page 37 ATTACHMENT 11 BIT-ORIENTED DATA FILE TRANSFER WORD FORMATS Table 11-6A GENERAL FORMAT IDENTIFIER (GFI) Bit 28 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 NOTE: [1] For consistency with Version 1.ARINC SPECIFICATION 429 PART 3 . 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. Table 11-7A FINAL LDU BIT 25 0 1 DESCRIPTION Not Final LDU Final LDU .

11. 01-Command. 10. Limit for Bridgeability = 1500 bytes M/B/U SAL – Multicast/Bridge/Unique (standard ARINC 429) System Address Label (SAL) . 00-Information. 00-Information.Reserved Word Count Field – 10 bits for an Information Frame – Max Information Frame Size = 2550 bytes.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 c-17 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. 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 P 0 1 0 Reserved I/C ARINC 429 Word Count 7 6 5 4 3 2 1 M/B/U SAL Where: P – 32 Bit Parity I/C – Information/Command Frame Identifier Field. Max Command Frame size = 2552 bytes 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 P 0 1 1 0 0 0 1 LSB FCS (16 Bit CRC) MSB 6 5 4 3 2 1 U SAL Where: P – 32 Bit Parity Bit 25 (Command Frame Final Bit) for EOF word always set to 1 FCS – Frame Check Sequence. 10. 11-Reserve Word Count Field – 10 bits for a Command Frame.ARINC SPECIFICATION 429 PART 3 . 01-Command.

Page 39 ATTACHMENT 11 BIT-ORIENTED DATA FILE TRANSFER WORD FORMATS Table 11-11 INFORMATION FRAME EOF Version 3 Command Frame EOF BIT 32 P P 31 0 0 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 1 1 0 0 0 0 FCS (32-Bit CRC) MSB M/B/U SAL 1 1 0 0 0 1 LSB FCS (32-Bit CRC) M/B/U SAL c-17 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 .

Versions 0 and 1 are equivalent for the ALOHA (ALO) and ALOHA RESPONSE (ALR) Protocol Words. values of Word Count may be 3 through 255 (03 through FFh). 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. Status Codes are contained in Attachment 11B. This is the System Address Label of the system which is sending out the ALO.: A) The first (most significant) octet is in bits 16-9 of the first Data word.ARINC SPECIFICATION 429 PART 3 . C) The LSB of the second octet is in bit 17 of the first Data word. i.etc.e. i. as referenced in Table 11-4A. which contains the ISO Alphabet control character "DC2" in bits 29 through 23. defined in Appendix F. Word Count values of 0000 0000 through 0000 0010 are not used. B) The MSB of the first octet is in bit 16 of the first Data word. 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. Destination Codes are contained in Attachment 11A.e. 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” (Lower ½) 0 1 0 0 0 “H” 0 1 0 0 1 0 0 0 0 1 “P” 0 1 0 0 0 0 SAL Word P 0 0 Data Word 2 P 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 “X” (Upper ½) 0 0 0 1 0 1 SAL [3] [4] [5] c-16 [6] [7] [8] [9] c-14 Bits 24 through 31 of Partial Data Words are coded to avoid conflict with old RTS words. . 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 “message”. etc. B) The second octet is in bits 24-17 of the first Data word . 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.Page 40 ATTACHMENT 11 BIT-ORIENTED DATA FILE TRANSFER WORD FORMATS NOTES [1] [2] All words are transmitted using odd parity (denoted by P in bit 32). c-14 [10] Bits 12 through 9 define the version number of the ARINC 429 bit-oriented protocol.

CENTER OPTIONAL AUXILIARY TERMINAL PRINTER SATELLITE DATA UNIT.Page 41 ATTACHMENT 11A DESTINATION CODES DESTINATION CABIN TERMINAL (1-4) USER TERMINAL (5-8) FMC. 4 3.ARINC SPECIFICATION 429 PART 3 . 4 3. LEFT SIDE FMC. RIGHT SIDE CONTROL DISPLAY UNIT DFDAU CABIN PACKET DATA FUNCTION CFDIU GROUND STATION HF LINK EICAS/ECAM/EFIS AUTOMATIC DEPENDENT SURVEILLANCE UNIT (ADSU) KEYBOARD/DISPLAY Unassigned ACARS MANAGEMENT UNIT (MU) FMC. RIGHT SIDE (SDU 2) SATELLITE LINK HFDR Left HFDR Right VHF LINK (VDR) TAWS CVR Unassigned Unassigned INMARSAT SATELLITE LINK ICO SATELLITE LINK GLOBALSTAR SATELLITE LINK CHARARACTER CODE 1-4 5-8 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z CONTROL CODE VT CONTROL CODE CR CONTROL CODE SO BIT CODE [1] 22222111 43210987 NOTES 01000001 01000010 01000011 01000100 01000101 01000110 01000111 01001000 01001001 01001010 01001011 01001100 01001101 01001110 01001111 01010000 01010001 01010010 01010011 01010100 01010101 01010110 01010111 01011000 01011001 01011010 00001011 00001101 00001110 c-15 c-15 c-15 c-18 c-16 2 2 6 c-15 c-18 c-18 3. LEFT SIDE (SDU 1) SATELLITE DATA UNIT. 4 .

Transponder (XPDR) was removed from the DESTINATION column.ARINC SPECIFICATION 429 PART 3 – Page 42 ATTACHMENT 11 A DESTINATION CODES NOTES: c-18 [1] [2] [3] [4] c-18 [5] Origin/Destination Codes T and U are used when the HFDR transmits/receives onboard messages as an ACARS End System. The Destination Code may be a 7-bit ISO Alphabet No. [6] . a binary value. 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. character code "S" is used for any available nonspecific satellite link. 5 code with no parity. Bit 24 should contain a zero. These codes are used for the specific satellite links indicated. These are non-printable control codes (reference ARINC 429 Part 1 Attachment 5). Origin/Destination Codes Q and R are used when the SDU transmits/receives onboard messages as an ACARS end system. or. alternatively.

. . .ARINC SPECIFICATION 429 PART 3 . . FE FF DESCRIPTION No Information User Defined User Defined . 7E 7F 80 81 82 83 84 85 86 87 88 89 8A 8B 8C 8D 8E 8F 90 91 92 93 94 95 96 . . User Defined User Defined Missing SOT Word LDU Sequence Number Error Invalid GFI Missing EOT Word Invalid Destination Code CRC Error LDU Time-Out Error Restart Initialization Word Count Error Word Count Error/Input Overrun Word Count Error/Parity Error Sink Flow Control Buffer Full Device Off-Line File Time-Out Error Window with Multiple FSNs Missing LDU Control Word Remaining LDUs/Received LDUs Error Window Size Exceeds Sink’s Receive Capability Invalid LDU Count in Window Invalid EOT in Window New File with Previous Incomplete Reserved . Reserved Reserved NAK X X X X X X X X X X X X X X X X X X X NCTS X X X X X X X X BUSY X X X X X X X X SYN X X X X X X X X X X c-15 X X X X X X X X X X X X X X X c-15 .Page 43 ATTACHMENT 11B STATUS CODES CODE (HEX) 00 01 02 . .

with bit 17 as the most significant bit and bit 24 as the least significant bit of the subsystem SAL. . Number [1] 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 6 5 4 3 SAL 2 1 [1] See Table 11-4A for version number. NOTE: Table 11-C3 has been moved to Attachment 11. [2] Reserved fields should be set to binary 0.ARINC SPECIFICATION 429 PART 3 . 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 P Protocol ALR Reserved [2] Ver.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 P Protocol ALO Subsystem SAL of originator Reserved [2] Version [3] Number [1] 1 0 0 0 1 1 1 0 0 0 0 0 0 0 1 8 7 6 5 4 3 SAL 2 1 [1] See Table 11-4A for version number. Table 11-4C. [3] This field should contain the SAL of the device sending the ALOHA word. c-16 [2] Reserved fields should be set to binary 0.

ARINC SPECIFICATION 429 PART 3 – Page 45 ATTACHMENT 12 VERSION 1 FILE TRANSFER EXAMPLE SOURCE AIRLINE SOURCE RTS WORD ORIGINAL DATA FILE CTS WORD SOT WORD DATA WORD DATA WORD o o o DATA WORD EOT WORD ACK WORD 254 255 1 2 3 FIRST LDU SINK RTS WORD CTS WORD SOT WORD DATA WORD DATA WORD LAST LDU DATA WORD DATA WORD DATA WORD EOT WORD 1 2 3 4 5 6 7 RECEIVED DATA FILE AIRCRAFT DESTINATION ACK WORD .

For the CRC computation.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 8 7 6 5 4 3 2 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 n5 P 0 0 0 B 20 B B 17 16 n4 B B 13 12 n3 B B 9 8 n2 B 5 B 4 n1 B 1 SAL 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 n1 8 7 6 5 4 3 2 1 c-14 P 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 B 24 B 21 SAL 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 P 1 1 1 0 0 0 * LSB CRC MSB 8 7 6 5 4 3 2 1 SAL * Final LDU Bit This example takes 24 bits of data and puts it into two data words. . the MSB is the bit position that represents the coefficient of the highest order term of the polynomial.

Assume Unit A will initiate the exchange to determine the protocol to be used. Assume that Unit B is only capable of communicating using the ARINC 429 character-oriented file transfer format. UNIT A ALO ALR UNIT B 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 Unit A will initiate the exchange to determine the protocol to be used. UNIT A CHARACTER-ORIENTED RTS CHARACTER-ORIENTED CTS UNIT B CHARACTER-ORIENTED COMMUNICATIONS ESTABLISHED . UNIT A ALO ALO ALO CHARACTER-ORIENTED RTS CHARACTER-ORIENTED CTS UNIT B CHARACTER-ORIENTED COMMUNICATIONS ESTABLISHED Assume Unit B will initiate the exchange to determine the protocol to be used.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.

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. UNIT A CHARACTER-ORIENTED RTS CHARACTER-ORIENTED RTS CHARACTER-ORIENTED RTS UNIT B COMMUNICATIONS NOT POSSIBLE NO RESPONSE . Assume that Unit B is capable of communicating only using the ARINC 429 character-oriented file transfer format. The resulting “No Response” conclusion accurately identifies the inability of the two units to communicate. 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 ALO ALO ALO UNIT B NO RESPONSE COMMUNICATIONS NOT POSSIBLE Assume Unit B will initiate the exchange.ARINC SPECIFICATION 429 PART 3 .

2 & 5) ALO: Version = 5 Example #3 SINK Device : "B" Versions of protocol supported by this device (1) ALR: Version = 1 Time Time . 2. 2 & 5) Example #2 SINK Device : "B" Versions of protocol supported by this device (1. 2 & 5) SINK Device : "B" Versions of protocol supported by this device (1. 3 & 6) ALO: Version = 5 ALR: Version = 3 ALO: Version = 2 Time ALR Version = 1 Time SOURCE Device : "A" Versions of protocol supported by this device (1. 3 & 6) ALO: Version = 5 ALR: Version = 3 ALO: Version = 2 Time ALR Version = 1 Time SOURCE Device : "A" Versions of protocol supported by this device (1.ARINC SPECIFICATION 429 PART 3 – Page 49 ATTACHMENT 13A ALOHA VERSION DETERMINATION SEQUENCE Example #1 SOURCE Device : "A" Versions of protocol supported by this device (1.

Part 1.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. .ARINC SPECIFICATION 429 PART 3 .

ARINC SPECIFICATION 429 PART 3 .Page 51 ATTACHMENT 15 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.

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.Page 52 ATTACHMENT 16 NOTE: This attachment has been deleted by Supplement 16. .ARINC SPECIFICATION 429 PART 3 .

ARINC SPECIFICATION 429 PART 3 .Page 53 ATTACHMENT 17 FLOW DIAGRAM USED TO DETERMINE CHARACTER-ORIENTED VS BIT-ORIENTED PROTOCOL begin attempt bit-oriented protocol failed link established normal bit-oriented communications normal comm no response attempt char-oriented protocol failed link established normal char-oriented communications normal comm no response wait 0-15 seconds .

2.Page 54 ATTACHMENT 18 MAC SUBLAYER SUPPORT DIAGRAMS (3) Higher Layer Entity LLC Service Client MAC Service Client MAC Service Client LLC Service Client (2) Data Link Layer LLC Sublayer MAC Service Client (802. The operation of the MAC Control Sublayer is defined in IEEE 802.2 LLC) 802. MAC Control Functions are defined Section 3.4 of this Specification.MAC Sublayer and its Service Clients .3-TYPE c-17 802.3-LENGTH Media Access Control (MAC) Sublayer MAC Control MAC Service Entity MAC Control MAC Service Entity (1) Physical Signaling Layer Physical Signaling (429) Physical Signaling (429) 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.ARINC SPECIFICATION 429 PART 3 . Figure 18-1 .3 Clause 31.2 LLC) MAC Service Client (802.

service class) Receive Frame (destination and source addresses.Indication MA_CONTROL.Indication MA_DATA.Page 55 ATTACHMENT 18 MAC SUBLAYER SUPPORT DIAGRAMS MAC Service Client MA_DATA. length/type.Request 429 MAC Control Sublayer MAC Sublayer Transmit Frame (destination address. data. service class) c-17 429 Medium Access Control Transmit Receive Physical Layer 429 Physical Figure 18-2 .ARINC SPECIFICATION 429 PART 3 . reception status. data.MAC Control Sublayer Support Of Interlayer Service Interfaces .Request MA_CONTROL. length/type.

ARINC SPECIFICATION 429 PART 3 . 00 – Information. 01 – Command. 16-bit CRC for Command Frame . 10.Page 56 ATTACHMENT 19 COMMAND FRAME DATA UNIT (FDU) STRUCTURE AND EXAMPLES Table 19-1 BIT V3 Command Frame SOF 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. 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 BIT 32 P P P P 31 0 0 0 0 V3 Command Frame (Full and Partial) Data Words 30 0 0 0 0 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 DATA U SAL 0 DATA U SAL 0 DATA U SAL 0 DATA U SAL Table 19-3 BIT V3 Command Frame EOF 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.

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: P P 0 0 0 0 0 1 0 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 1 0 0 0 1 1 0 0 0 0 0 0 0 U SAL U SAL c-17 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 .

ARINC SPECIFICATION 429 PART 3 . 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 .Page 58 ATTACHMENT 20 INFORMATION FRAME DATA UNIT (FDU) STRUCTURE AND EXAMPLE Table 20-1 BIT Version 3 Information Frame SOF 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. 10. 00-Information. 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 BIT 32 P P P P P P P P P 31 0 0 0 0 0 0 0 0 0 Version 3 Information Frame (Full and Partial) Data Words 30 0 0 0 0 0 0 0 0 0 29 28 27 26 25 24 23 22 21 0 0 0 Source 0 0 Length/Type LSB MSB 0 Data 0 0 0 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 Destination LSB M/B/U SAL Destination M/B/U SAL LSB MSB Destination M/B/U SAL Source M/B/U SAL Source M/B/U SAL MSB Length/Type M/B/U SAL Data M/B/U SAL Data M/B/U SAL Data M/B/U SAL c-17 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. 01-Command.

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 4 3 2 1 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 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: P P P P P P P 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 X X X X X X X X X X X X X X X X Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y 1 0 0 0 Y Y Y Y 0 0 0 0 0 0 0 0 1 0 0 1 0 0 0 0 X X Y Y Y 0 0 X X Y Y Y 0 0 X X Y Y Y 0 0 X X Y Y Y 0 0 X X X Y Y 1 0 X X X Y Y 0 0 X X X Y Y 0 0 X X X Y Y 0 0 X X X Y Y 1 0 X X X Y Y 0 1 X X X Y Y 0 0 X X X Y Y 0 1 U SAL U SAL U SAL U SAL U SAL U SAL U SAL c-17 V3 Information Frame EOF: P P 0 0 1 1 1 1 0 0 0 0 0 0 0 1 LSB FCS (32-Bit CRC) FCS (32-Bit CRC) MSB U SAL 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 .

E Appendices A through E are included in ARINC Specification 429.ARINC SPECIFICATION 429 PART 3 . ARINC Specification 429 and therefore not used c-16 in this Part to avoid potential confusion due to duplication. this approach is used to maintain consistency with previous versions of ARINC Specification 429 when it was published as a whole (through Supplement 14). . In addition.Page 60 APPENDICES A . Part 1.

See Section F-2. etc. intermediate and final words.5 Sign/Status Matrix F-2. And 11 of ARINC Specification 429 Part 1 for changes prior to division of ARINC Specification 429 into separate parts.1.1.1.2 AIM Data The order function (first. F-2. The contents of Section F-2.1. Sections F-2.5. 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.5.5 provides guidance for character-oriented file transfer protocols reflected in ARINC equipment characteristics. CHARACTER-ORIENTED FILE TRANSFER STATUS MATRIX BIT TEXT DATA 31 30 0 0 Intermediate Word Plus.1. The information is contained herein for reference purposes.1 Digital Language F-2. ISO Alphabet No. All three of these applications may involve the transfer of more than 21 bits per “data package”. but retained herein for those who need to understand the basis for character-oriented protocol already implemented.4 contain the definitions of the terms initial.3.” 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. 5 and Maintenance information encoded in dedicated words) should be handled in the manner described in this section. intermediate.5. Alternatively. North.5. F-2.3.2. “Control Word”.5.3.4 and F-3. final) or word content (control word).3. etc.3.2 of this Appendix is no longer applicable to ARINC Specification 429. last and control) of text and the sign (Plus/Minus.1. Attachment 1) in bits 1 through 8. South etc.5. COMMENTARY Bit-oriented file transfer is the preferred protocol (See Section 2. The guidance for character-oriented protocol was removed from the body of the specification to avoid the continuation of its use. F-2. “Intermediate Word” and “Final Word. North/South.3 Character-Oriented File Transfer The order and function (first.1.1. intermediate.4 of this document for definitions of the terms “Initial Word”.) of numeric data transferred by file transfer should be encoded in bits 30 and 31 of each word as shown in the table below.Page 61 APPENDIX F FORMER AIM AND FILE DATA TRANSFER TECHNIQUES AEEC Staff Note: See Supplements 4. 7. 0 1 Initial Word Not Defined 1 0 Final Word Not Defined 1 1 Intermediate Word Minus.ARINC SPECIFICATION 429 PART 3 . 5. intermediate. F-2.1. c-18 The information contained in Sections F-2. each word containing the relevant application label (see ARINC Specification 429. and a sign/status matrix code in bits 30 and 31. Source equipment should format such long messages into groups of 32-bit DITS words. Part 1.3.3. .5 of Part 3 of ARINC Specification 429) for use in new applications.1.4 AIM Data AIM data (Acknowledgement. 6. the SSM field may be used to describe position in a series of data words (initial.1.3.2 through F-2.

When the word application label is assigned in ARINC Specification 429. 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. Attachment 1 Maintenance Data (ISO Alphabet No. bits 19 and 20 the required character size and bit 21 should indicate whether or not the display is required to flash. 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. BIT 22 0 0 0 0 1 1 1 1 Example: 1 0 1 0 1 0 Group 2. It should also contain. 5). when used. bits 17 and 18 the required intensity. See ARINC Specification 429. Intermediate words.1. The data field of this word should be structured similarly to that of the intermediate word. 5 and Maintenance Data (ISO Alphabet No. Bit usage is given in the table below. the total number of information bits to be transmitted is 13 or less) bits 9 through 16 should all be binary “zeros”. 16 through 22 and 23 through 29). the binary representation of the number of words in the group.” . bits 17 through 29 of this initial word may be used for information transfer.ARINC SPECIFICATION 429 PART 3 . Attachment 1 for ISO Alphabet No. Units 1-15 Group 3. Attachment 1 for Acknowledgement Data. When the word application label is either of those assigned in ARINC Specification 429. Part 1. 5) final words resulting from the number of ISO Alphabet No. Part 1. Data bits 9 through 29 of that word are available for information transfer. in bits 9 through 16. Units 1-15 Group 1. When it is used. When the word application group label that is assigned in ARINC Specification 429. When the word application label is either of those assigned in ARINC Specification 429. each of which contains one ISO Alphabet No. See ARINC Specification 429. The second word of the ISO Alphabet No. The first word of each group should contain the sign/status matrix code defined for “initial word” in F-2. bits 9 through 29 of each word should be divided into three seven-bit bytes (bits 9 through 15. Attachment 6 for the encoding standards.1. Any unused bit positions in ISO Alphabet No. follow the initial word of the group or the control word. 5). bits 17 through 22 are used for unit addressing. 5 data transfer or Maintenance Data (ISO Alphabet No.1. containing the sign/matrix code for “intermediate word”. Part 1. Bits 22 through 29 of the word should be binary “zeros” (spares). 5 character. Part 1. All Groups Group 0. bits 14 through 16 should encode the required color. except that when this word is the only word to be transmitted. 5 Messages and Maintenance Data bits 23 through 29 should take on the pattern of the IOS Alphabet No. Attachment 6 for word format. All Call Group 1. Attachment 1 for Acknowledgement is used.Page 62 APPENDIX F FORMER AIM AND FILE DATA TRANSFER TECHNIQUES Bit 32 should be encoded to render word parity odd.1. 5 control character “STX”. Units 1-15 FUNCTION For ISO Alphabet No. When the label is for ISO Alphabet No.5. 5 characters in the message being one or two less than a number wholly divisible by three should be filled with binary “zeros. All Call Group 2. All Call Group 3. 5) application groups is an optional control word containing sign/status matrix code for “control” information for display. bits 17 through 22 should be binary 'zeros” (spares). Units 1-15 Group 2. Part 1. bits 9 through 13 should contain the binary representation of the line count. Unit 10 0 0 1 1 0 0 1 1 21 0 X 0 X 0 X 0 X 20 19 0 X 0 X 0 X 0 X 18 0 X 0 X 0 X 0 X 17 0 X 0 X 0 X 0 X All Call.5. 5 Messages. 5 data transfer or Maintenance Data (ISO Alphabet No. Part 1.

The response to a “Poll” word will be either a “Request” to Send” initial word when the polled terminal does have data to transmit. continuing through the “final word”. The transmitter's response should be to retransmit the whole file. The transmitter should then wait 200 milliseconds and retransmit the “Request to Send”. with the “Clear to Send” reply. The receiver responds. The transmitter should also repeat a “Request to Send” transmission 50 milliseconds after the initial transmission if no response is obtained from the receiver.5. one of the eight versions of the “initial word” described in F-2.3. 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). at the minimum.3. followed by the data and the “final word”.1. If the receiver detects a parity error during the transmission. Bits 9 through 29 are divided into three seven-bit fields. Each record may contain from 1 to 126 data words. The receiver can signal loss of synchronization to the transmitter at any time bysending the “Synchronization Lost” initial word. The transmitter then sends the “Data Follows: initial word. The file data transfer protocol is as follows. The receiver processes the error control information in the ‘final word” and. The receiver should then close out the transaction as before. or another “Poll” word when it does not.1. the transmitter should curtail the data flow and back up to the beginning of the file.1. Having done this it should send the “Data Follows” initial word. the “intermediate words” and the “final word”.ARINC SPECIFICATION 429 PART 3 . . A record should contain. If the receiver is not ready to accept data when the transmitter sends its “Request to Send” word.5 File Data Transfer F-2.3. 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.1. Additionally. An exchange of “Poll” words may be interpreted as the message. If 2 additional attempts also spaced at 50 milliseconds produce no response from the receiver. if no errors are revealed.3. Bits 30 and 31 contain the code identifying them as initial words while bit 32 is encoded to render word parity odd.5.3. In the absence of identification of the record in which the error occurred. The “Header Information” initial word is used for this purpose. the file itself. 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. this word should contain the sequence number of the first record of the file. The transmitter should interrupt the data flow and back up to the start of the record so identified.5. it should so indicate its response (See F-2. on the separate bus provided for return data flow. “I have nothing for you.5. a “Poll” initial word is defined for use in the system which continuous “hand-shaking” between two terminals is desired. A transmitter having the data to send to a receiver transmits. on the bus connecting it to that receiver. closes out the transaction by sending the “Data Received OK” word to the transmitter.1.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. A file may contain from 1 to 127 records. Bits 1 through 8 of the “Poll” word contains binary zeros. do you have anything for me?” F-2. the contents of which vary with word type as shown in Table A below.2. or request to the receiver to accept.1 Command/Response Protocol File data will consist of both ARINC 429 BNR numeric words and ISO Alphabet No. the transmitter should send the data. The protocol also allows a transmitter to send the file size information to a receiver without any commitment to send.Page 63 APPENDIX F FORMER AIM AND FILE DATA TRANSFER TECHNIQUES F-2.2). 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. 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. It should then re-establish that the receiver can accept data by going through the request-to-send routine. On receiving this word. 5 characters. the “Request to Send” initial word.

5. F-2. 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.5.3.7 File Data Labels Labels define the application of the file data to be transferred.3. the FMC inter-system cross-talk. etc. Bits 1 through 8 contain the file label.ARINC SPECIFICATION 429 PART 3 . F-2.3.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. Below.g. 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. Manufacturers are invited to submit proposals for a standard flight plan update file and cross-talk bus formats. Bit 32 is encoded to render the word parity odd. Bits 9 through 29 can accommodate three ISO Alphabet No.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 0 30 0 WORD TYPE Intermediate Word requiring no sign data or having Plus. Bits 1 through 8 contain the file label. Bit 32 is encoded to render the word parity odd.1.1. e.Page 64 APPENDIX F FORMER AIM AND FILE DATA TRANSFER TECHNIQUES NOTES 1. . F-2.3 Intermediate Words Intermediate words contain the data being transmitted by means of the protocol.5. Above Right.6 File Data Formats As noted in F-2. It will determine the high or low speed nature of the source by port identification of the source of the “Request to Send” signal.5.5. the “Request to Send” word label.3. North..1. 5 characters or one ARINC 429 BNR numeric word without its label. East. the ACARS ground-to-air link. or From sign 0 1 1 1 0 1 F-2. There may be a need to assign more than one label to some of those applications if priority override capability is desired.1. 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. The need to standardize such formats was examined by the working group. The record sequence number is the number of that record in a multiple-record file being transmitted.4 Final Words The final word of each record contains error control information. West. The conclusion was reached that a standard format was desirable for flight management computer flight plan updating and for computer cross-talk.3. Left.3. but was not necessary for updating the computer's data base. the SDI code or some combination of these information items. Bits 30 and 31 of this word contain the code identifying it as a final word. 2.3. Bits 30 and 31 contain the word code or the sign information (only) encoded in the sign/status matrix of BNR numeric data words. 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. South. or To sign Initial Word (all types) Final Word Intermediate Word having Minus. the transmission of file data words without labels necessitates the use of pre-arranged data formats. The receiver will annunciate the contents of this field (record count or word count) by setting Bit 22 as indicated.5. F-2. Such application include FMC program load/update. Note that this alpha/numeric data interleaving capability without labels necessitates a prior agreement between transmitter and receiver on data format.1. flight plan load/update.

1.4.4.3.3.2. 5 messages. should the message be displayed to the crew or otherwise utilized. F-3. a separate label would have to be assigned to each AIM word application for each source of such data. . Without it.3. The Maintenance word as described by AIM data handling techniques is limited to IOS Alphabet No.1. with no words having been “lost along the way. In it. labels are assigned by word application only.3. will be the most likely to make use of the multiple-word message transmission capability of the system.4 describes the techniques to be used for the transfer of Acknowledgement. 5 and Maintenance (ISO Alphabet No.1. and the use of ISO data for maintenance-related information transfer.2.2 ISO Alphabet No. F-3. 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. No applications for this system capability have yet been identified and thus no data standards for acknowledgement messages have been established. The technique also accommodates the use of multiple-word DITS messages. The motivation for the adoption of this technique was label conservation.3.4. A special exception to this rule is made for the Airborne Integrated Data System (AIDS).4.1.Page 65 APPENDIX F FORMER AIM AND FILE DATA TRANSFER TECHNIQUES F-3.2. The Maintenance assist system should use input port recognition to identify data sources.1.1. F-3. 5 Data Source equipment transmitting ISO Alphabet No. as described in Section F-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 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.” Only when this determination has been made. ISO Alphabet No. and the parity check for each word shows the data to be error-free.3. 5) data by means of the Mark 33 DITS. and (where necessary) utilization device input port recognition utilized to identify sources. This application. 5 information by means of the Mark 33 DITS should do so in the manner described in F-2.4.ARINC SPECIFICATION 429 PART 3 .2 AIM Information Transfer F-2. as described in F-2.

5 Control Character “SOH” Binary Zeros Binary Zeros ISO Alphabet No. BNR count of the number of maximum length of records OR the number of 32-bit words the receiver can accept when it is ready Binary zeros Binary zero when receiver is not ready to receive data and when BNR counts in 9-15 is record count. ISO Alphabet Control Characters “DC3” BNR count of number of words in record (Max.ARINC SPECIFICATION 429 PART 3 . 126) Record Sequence No. 127) Binary zeros ISO Alphabet No. 5 Control Character “DC2” Binary zeros when receiver is not ready to accept data. (BNR) ISO Alphabet No. Binary one when count in bits 9-15 is 32-bit word count.Page 66 APPENDIX F FORMER AIM AND FILE DATA TRANSFER TECHNIQUES TABLE A . 5 Control Character “ENQ” . 5 Control Character “STX” BNR count of number of words in record (Max. 5 Control Character “SYN” BNR count of number of records in file to be transferred Binary Zeros ISO Alphabet No.INITIAL WORD TYPES INITIAL FIELD WORD TYPE (Bits) Request to Send 9-15 (Tx-to-Rx) 16-22 23-29 Clear to Send (Rx-to-Tx) See Note 1 9-15 16-21 22 Data Follows (Tx-to-Rx) See Note 2 Data Received OK (Rx-to-Tx) Data Received Not OK (Rx-to-Tx) Synchronization Lost (Rx-to-Tx) Header Information (Tx-to-Rx) Poll (B-directional) 23-29 9-15 16-22 23-29 9-15 16-22 9-15 16-22 23-29 9-15 16-22 23-29 9-15 16-22 23-29 9-15 16-22 23-29 FIELD CONTENTS BNR count number of records to be sent (Max. (BNR) in which error occurred ISO Alphabet No. (BNR) ISO Alphabet No. 5 Control Character “NAK” Binary Zeros Binary Zeros ISO Alphabet No. 126) Record Sequence No. 5 Control Character “ACK” BNR count number of words in record Record sequence no.

+ x + x + x + x .. x + x + x + x + . and do not denote division in this example. since these polynomial divisions are more efficiently simulated by logical operations.. is: 1 0001 .. Actual software/hardware implementations are expected to vary significantly from this example. the dividend is calculated as follows: x G(x) 16 = 1010 0111 1000 0111 1010 1100 0000 0000 0000 0000 and x (x + x +.. + x + x + x + x . the MSB is the bit which represents the coefficient of the highest order term of the polynomial.Page 67 APPENDIX G MATHEMATICAL EXAMPLE OF CRC ENCODING/DECODING NOTE: The following example describes the polynomial division procedure for CRC encoding and decoding... + x + x + x + 1) = x + x + x + x + . It is not related to the MSB or LSB of each individual octet.+ x + x + 1) k 15 14 2 = 1111 1111 0111 1111 1000 1111 1000 1111 0111 1111 0111 1111 1000 0000 1010 0000 1010 0000 1100 0000 1100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 + = 1010 1111 0101 Then the Dividend is: 16 12 5 0101 1000 0111 1000 0000 1010 0010 1100 0001 0000 0000 0000 0000 and the Divisor.. x (x + x + x + x + .. k = 24. Arithmetic operations are modulo 2. 39 37 34 33 23 21 19 18 16 23 21 18 17 7 5 3 2 23 21 18 17 16 15 10 9 8 7 5 3 2 x (x + x + x + x + x + . The following (arbitrary) 24-bit message is to be transmitted with a CRC encoded: 10100111 / 10000111 / 10101100 (MSB) The mathematical procedure is as follows: For this message. and G(x) x G(x) 16 (LSB) = = = and x +x +x +x +x +x +x +x +x +x +x +x +x.. P(x) = x + x + x + 1. + x + x + x + x ). For CRC computations. 39 38 37 36 27 26 25 24 k 15 14 13 12 11 3 2 At The Transmitter: Using coefficients of the above polynomials..ARINC SPECIFICATION 429 PART 3 . Slashes (/) are used to separate octets for readability only.

(Q(x).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. the quotient generated by the division process. addition and subtraction are both equivalent to XOR operations (no carries!) 1000 1 1 R(x) = CRC 16 1000 0001 0001 0000 1111 0001 0010 0000 0010 1101 0000 1101 0010 1111 0000 1 1000 0001 1001 0110 = R(x) = M(x) = = + = or x G(x) + CRC 1010 1010 0111 0111 1000 1000 0111 0111 1010 1010 1100 1100 0000 1111 1111 0000 1101 1101 0000 0000 0000 0000 0110 0110 M(x) = 1010 MSB 0111 1000 0111 1010 1100 LSB 1111 MSB 1101 0000 0110 LSB (message) (CRC) M(x) is the transmitted message with CRC. 101 1010 01 1110 0001 1111 0000 1111 1000 0111 0010 0101 0001 0100 0000 0100 1000 1100 Q(x) 0101 100 1 1 1000 0100 1100 0001 1101 1000 101 100 1 1 0111 0000 0111 0000 0111 1000 1111 0100 1011 0001 1010 1000 10 10 = 1000 1000 0000 0010 0010 0001 0011 0000 0011 0000 0011 1000 1011 0010 1001 1000 1 1101 1100 1010 0000 1001 0000 1101 0000 1001 0000 Using (synthetic) Polynomial Division: 1 1 01 01 0000 0001 0101 0000 0001 0100 0101 0001 0100 0 1 100 001 1010 0000 1010 0 1 1 Note: Since all operations are Modulo 2. is not used).

. generated by the division process. 0000 . is the same as that used by the transmitter. 0000 .) (The quotient. 0000 .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: x M(x) + x (x + x + x + x + .. + x + x + 1) = + = 1010 1111 0101 0111 1111 1000 1000 1111 0111 0111 1111 1000 1010 0000 1010 1100 0000 1100 1111 0000 1111 1101 0000 1101 0000 0000 0000 0110 0000 0110 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 16 40 15 14 13 12 2 The above string is the dividend used by the receiver. the final remainder is: Rr(x) = 0001 1101 0000 1111 .) Q(x) 0101 100 1 1 1000 0100 1100 0001 1101 1000 101 100 1 0111 0000 0111 0000 0111 1000 1111 0100 1011 = 1000 1000 0000 0010 0010 0001 0011 0000 0011 101 1010 01 1110 0001 1111 0000 1111 1000 0111 1101 1100 1010 1111 1001 1101 1101 0000 1001 0110 .ARINC SPECIFICATION 429 PART 3 . (The divisor. 10001000000100001. Q(x). 0000 1 1 01 01 0000 1001 1000 1 1 0110 1000 1110 0001 1111 1110 0001 1111 0000 1111 1101 0000 1101 0010 1111 0 1 1110 0001 1111 Note: At this point. is not used. if the division is carried through to termination.

the first bit of the first Data Word transmitted after the SAL is the MSB of the message (for CRC computations).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 following represents the mapping of the preceding 24-bit message and CRC into an LDU for transmission: MSB M(x) = 1010 0111 (message) 1000 0111 P 110 P 000 P 001 P 111 1010 GFI 0101 1000 0001 LSB 1100 MSB 1111 (CRC) 1101 0000 LSB 0110 SAL SAL LDU Partial Data Word EOT Word Legend: The CRC is calculated over these bits. 1110 0001 LDU No. when mapped into 32-bit words. M(x). the actual transmission order of the bit string.ARINC SPECIFICATION 429 PART 3 . These are the CRC bits 0000 0110 0000 0000 0000 1011 0011 1111 SAL SAL SOT Word Full Data Word File No. Therefore. 1110 0101 . is the reverse of the previous example.

Version 3 systems are defined to provide a standard MAC-based sublayer of the bit-oriented communicationsc-16 protocol. • • • Version 1 systems are defined to be (Williamsburg) bit-oriented communication protocol systems. c-17 . These GFI bit-codings are not compatible with the new GFI "4h" designator and should not be used as standard network service identifiers. H. any version 3 system should interoperate with any other version 3 system (independent of supplement number).ARINC SPECIFICATION 429 PART 3 .0 this Specification. and are defined in Section 3. H.4 Bit-Oriented Link Layer GFIs for Standard Network Service When a system implements a standard (e.1 Version Number Designators The version number of a system is transmitted to the peer system in the ALO and ALR words.Page 71 APPENDIX H INTEROPERABILITY OF BIT-ORIENTED LINK LAYER PROTOCOL H. which resides directly above the 429 Version 1 (Williamsburg).Same Version Number Beginning with Supplement 13 of 429. In general. ISO) network service.3 Interoperability .0 of ARINC 429 . the version number should be independent of supplement number implementation. a version 1 429-13 system should interoperate with a version 1 429-14 system. any version 1 system should interoperate with any other version 1 system (i. c-16 ISO GFI bit-codings originally specified in ARINC 429-13 were "1h" for ISO 8208 and "4h" for ISO 8473.. Similarly. higher supplement numbers of the same version number clarify requirements.g. H.) For example. as defined in Section 2. then the ISO GFI bit-coding of "4h" (for ISO 9577) as specified in ARINC 429-14 should be used.2 Interoperability .Part 3. Version 2 systems are obsolete and have been deleted from ARINC Specification 429 .Part 3.e.Different Version Numbers Version 1 and Version 3 can coexist on the same physical bus.

Part 3 * * Note that some of the names in * the message sequence diagram in * 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] . .Page 72 APPENDIX I SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL MSC .File_Transfer _Example c-15 /* * ARINC Specification 429. . 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 . .

W. DLPI_if [DL_UNITDATA. EOT. */ (p429_both). the WCF will be removed in later versions.req] LRU_Lyr_2 m_if [DL_ERROR. Unless more definitions occur in this area.Page 73 APPENDIX I SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL System Williamsburg /* * ARINC 429 Williamsburg (Section 2. SOT.ARINC CHARACTERISTIC 429 PART 3 . */ (p429_both). any of its agencies or others who may have participated in its preparation.ind] /* * * * * * * * * * * * * * * * * Notes: It was not clear what the Williamsburg Convergence Function actually did. and no representation or warranty. (p429_to_sink). EOT are used. EOT. LDU signal is not sent. Dihle ARINC 429 Williamsburg Working Group * * This is the SDT description of the 429 protocol * as developed by the 429W Working Group through * August 1994 * * */ Diagram (1) c-15 [DL_UNITDATA. Data Physical_429_if /* This is a working paper prepared for AEEC.5) * * Author. Any use or reliance on this doucment shall constitute an acceptance hereof "as is" and be subject to this disclaimer. K. Neither AEEC nor ARINC has made any determination whether these materials could be subject to claims of patent or other proprietary rights by third parties. expressed or implied is made in this regard. n4count n5count Determine task of Segment and Reassemble. other than change the names of the primitives. (p429_to_source). (p429_to_source).ind] Signal DL_UNITDATA /* This document is based on material submitted by various participants during the drafting process. Things to add to this defintion: SOLO Words File Seq No/LDU Seq No. Instead SOT.S. nor is it endorsed by the U. It does not constitute air transport industry or ARINC approved policy. SOT. Data. Federal Government. Data . (p429_to_sink). Turner.

5. RTS.ind.19.5. Signalist p429_to_source = ACK.1.7. CTS. NAK. /*LOOP.11 /*2.7.Page 74 APPENDIX I SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL The following definitions are used: Signal DL_UNITDATA.5.5. Signalist p429_to_sink = RTS.2 2.SOLO. ALR.2 /*2.17.TEST */. DL_ERROR.10 /*2.19.SYN. /*LCW /*2. SOT.5.req. DL_UNITDATA. . SYN. Data.7 /*2.13 /*2.5.5.17.ARINC CHARACTERISTIC 429 PART 3 .5.1.1 /*2. EOT.5.4 /*2.15 2. NCTS.5. ALO. /*TEST.3 /*2.BUSY. /*SOLO.CTS.ind.5. /* Wilmsbrg*/ /* -----*/ ACK.NAK.5.NCTS.2 */ */ */ */ */ */ */ */ */ */ */ */ */ */ */ */ Signalist p429_both = ALO<ALR/* LOOP.7. BUSY.2 /*2.5.1 2.5.17.12 /*2.1.5.1 /*2.

ARINC CHARACTERISTIC 429 PART 3 .Page 75 APPENDIX I SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL 1 (1) Block LRU_Lyr_2 [DL_UNITDATA.req.1) WCF [FILE] williamsburg_ifa [FILE] williamsburg_ifb (1. Data .ind.req] receive_if (1. LDU. NCTS.] [LDU. sink_if. SYN (p429_both) source_if sink_if RTS. NAK. EOT. (p429_both) SOT. NCTS. (p429_both) SOT.1) Segment (1.1) Reassemble m_if [DL_ERROR. SYN (p429_both) RTS.ind. NAK. BUSY. LDU. EOT. CTS. Connect DLPI_if and d_if.ind] Connect Physical_429_if and source_if. and typically for a single Williamsburg function there may be multiple sink_ifs. Connect m_if and m_if: d_if Signal FILE.req] (1. CTS.1) Source_and_Sink ACK.ind] send_if [LDU. [DL_UNITDATA. Data Note: the sink_if is a receive bus. ACK. BUSY.

ARINC CHARACTERISTIC 429 PART 3 .ind 'reassemble LDUs into a File' FILE - .Page 76 APPENDIX I SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL Process Reassemble 1(1) idle LDU.

ARINC CHARACTERISTIC 429 PART 3 .req - .Page 77 APPENDIX I SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL Process Segment 1(1) idle FILE 'segment the File into LDUs' LDU.

/*Number of SYN before NO COMM */ Synonym N6 integer = 3. .5. /* LDU timeout following CTS */ Synonym t14 duration = 120000. /*Number of ALO after no response*/ /* * Selected Options * Table 10-3 * * Option 1 Half Duplex * Option 2 Low Speed Bus Rate * Option 3 Automatic CTS when Ready = No * Option 4 Accept Auto CTS = No * 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 Part 3.T9. /* RTS repeat time if no response*/ t12 duration = 200.1). i.5. /* ALO repeat time if no response to ALO*/ t16 duration = 220. n5count n6count integer.19 c-15 /* Timer for Sink */ Synonym t9 duration = 2500.T14. n2count. Table 10-5 */ /* Timer for Source */ Synonym Synonym Synonym Synonym Synonym t2 duration = 100. /* RTS repeat time after receipt of BUSY */ t5 duration = 500. /* ACK/NAK Timeout after EOT*/ n4count := 0 n5count := 0 n6count := 0 2. /*Number of NAKs rcvd before NO COMM */ Synonym N5 integer = 3.T12.Page 78 APPENDIX I SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL Process Source_and_Sink /* * Bit-Oriented Protocol Events * Part 3.T4.the state machine only makes use of the predetermined SAL pair. Timer T2.19 ALO_idle c-15 /* Timer for Sink */ /* Synonym t9 duration = 400 /* LDU timeout following CTS */ /* Synonym t14 duration = 10000' /* Incomplete File Timeout */ Dc: n1count. /*Number of RTS repeats after no resp */ Synonym N4 integer = 3. /* RTS repeat time after receipt of NCTS */ t4 duration = 15000. /*Number of RTS repeats after BUSY */ Synonym N3 integer = 5. /* Incomplete File Timeout */ /* * Variables for High Speed Bit-Oriented Protocol * Part 3.e. This state machine asumes that SAL assignments have occurred. n3count n4count.T5. T12) 2.ARINC CHARACTERISTIC 429 PART 3 . Table 10-1 */ Synonym N1 integer = 5. /*Number of RTS repeats from NCTS */ Synonym N2 integer = 20.19 2.5.19 2. /* RTS repeat time after receipt of BUSY */ t5 duration = 150.*/ .5.3 c-15 set (now+ t12. /* ACK/NAK Timeout after EOT*/ 1 (12) (1. c-15 This is the power-on transition System Inactive State 0 ALO via source_if 2. Table 10-4 */ /* Timer for Source */ Synonym Synonym Synonym Synonym Synonym t2 duration = 500. /* RTS repeat time after receipt of NCTS */ t4 duration = 1000. /* ALO repeat time if no response to ALO*/ t16 duration = 220.T16. /* RTS repeat time if no response*/ t12 duration = 200. /* This Source_and_Sink state machine is replicated for each SAL pair.3 n1count := 0 n2count := 0 n3count := 0 reset state variables 2.

Synonym can_adapt boolean = true.5. ALO_Idle ALO 2.19.5.19.2 ALO_Idle 2.Page 79 APPENDIX I SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL 2(12) Synonym version_match boolean = true.5.1 2.1).5.19 reset(T12) 2.19.5.1 ALO_Idle false T12 2.1. Process Source_and_Sink (1.5.19.5.19.19.5.1 Link_ _Idle can_adapt true n6count <N6 ALO via source_if else 'not bit oriented' ALO via source_if 2. This should lead to the character-oriented protocol determination process.5.1.19.1 reset(T12) 2.1 - .5.1 Link_ _Idle false version_ _match true Link_ _Idle 2.5.19 recount := 0 2. T12) set(now + t12.19.1.5.19.19 go_ aloha ALR ALR via source_if 2.19.1 'not bit oriented' ALO_ Idle Not successful.1.1 2.19.19.5.5.19. T12) 2. if applicable. 2.5. or a cyclical attempt to establish bitoriented protocol.1 2.5.1 2.1 false 'adapt' true 2. See Attachment 17.ARINC CHARACTERISTIC 429 PART 3 .5.19.1 try_ _different_ _version n6count := n6count + 1 2.5. Synonym try_different_version boolean = true.1 - set(now + t12. 2.

7.1.5.2 Wait_ _SOT .5.7.7.7.5. Synonym messages_queued boolean = false.3 set(now + t9.5.req RTS go_rts ALO T14 set(now + t5.2 2.3 2.7 Link_ _Idle Wait_ _CTS false valid_and _ ready true CTS via sink_if 2.Page 80 APPENDIX I SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL 3(12) Synonym valid_and_ready boolean = true.5.7 false 2.5.7 are_we_ _ busy 'discard any partial file received' true BUSY via sink_if 2.5.14.5.1 2. Process Source_and_ Sink (1. Invalid and N/A transitions not shown Link_ _Idle LDU.3 go_aloha SYN via sink_if RTS via source_if 2. T9) 2.14.3 2. Synonym are_we_busy boolean = false.ARINC CHARACTERISTIC 429 PART 3 .5.19.5.5.2 Link_ _Idle Unless Option 3 is implemented 2.5.2 NCTS via sink_if 2. T5) 2.5.13.5.7 Unless Option 3 is implemented 2.1).7.7.4 reset(T14) 2.

5. Wait_ _CTS LDU.4 2.8.5.1 NOTE: Usually uplinks are accorded priority EOT via source_if 2. 2. 2.7. Synonym random_number duration = 1.5.1. n3count := 0 2.req RTS 2.ARINC CHARACTERISTIC 429 PART 3 .5.7.5.7.1 SOT via source_if 2.5. Dc: t6 duration.5.7.10 Data via source_if Wait_RTS_ _Conflict If Option 5 is used.19.1 2.5.3 reset(T5) So message just de-queued is not lost n3count=0 2. n2count := 0.14.5.1).5.7.5.5.Page 81 APPENDIX I SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL Process Source_and_ Sink (1.4 reset(T5) go_ _CTS LDU.4 2.7.7.7.5. one system will have priority 2.7.1 2.3.12 set(now + t16.req to self reset(T5) 2.5. Timer T6. T16) 2.1.10 ALO 2. 4(12) Synonym valid_CTS boolean = true.8.4 valid_CTS true reset(T14) t6 := random_ number set(now + t6.8.5.2 2.4 false go_ _NCTS go_ _aloha 2.16 Wait_ _ACK .2 2.5.1 n1count := 0.5. T6) 2.5.7.1 CTS 2.8.5.5.

4 .ARINC CHARACTERISTIC 429 PART 3 .4 n3count :=0 2.5. Wait_ _CTS NCTS go_ _NCTS BUSY BUSY 2.4 n3count :=0 2.ind NCTS_ Busy_ _Delay n1count :=0 NCTS_ Busy_ _Delay n2count :=0 RTS via source_if n3count :=0 Link_ _Idle Link_ _Idle Wait_ _CTS Link_ _Idle 2.Page 82 APPENDIX I SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL 5(12) Process Source_and_ Sink (1.5.5.ind set(now + t5.2 2.7.7.4 reset(T5) reset(T5) 2. T5) DL_ERROR.7.1).7.7.5.5.5.5.3 T5 2.3 2. T4) DL_ERROR.5. T2) DL_ERROR.ind set(now + t4.7.7.4 reset(T5) 2.5.7.7.4 n1count := n1count + 1 n2count := n2count + 1 n3count := n3count + 1 else n3count else <N3 n1count <N1 else n2count <N2 set(now + t2.

1 BUSY ALO 2.6 LDU.5.5.2 set(now + t5.5.5.1 Wait_ RTS_ _Conflict Wait_ CTS set(now + t9.5.5.5.8.1 CTS via sink_if 2.8.13.1 'requeue unitdata request' go_ _aloha 2. Wait_RTS_ _Conflict RTS 2.2 2.1).4 reset(T14) 2.5.1. T5) 2.19.13.2 T6 2.5.1.8.ARINC CHARACTERISTIC 429 PART 3 .5.7.req Wait_ SOT .Page 83 APPENDIX I SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL 6(12) Process Source_and_ Sink (1.14.19.8. T9) 2.3 RTS via source_if 2.

4 RTS via source_if 2.5.1. 2.Page 84 APPENDIX I SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL 7(12) Process Source_and_ Sink (1.2.1).7.5.5.5.req RTS ALO CTS This transition valid only if Option 4 is set.ARINC CHARACTERISTIC 429 PART 3 .7 NCTS_BUSY_ _Delay T4 2.5.5.5.7. Otherwise CTS is ignored.2 Wait_ _CTS Wait_ _CTS .7. T5) 2.7.7.7.4 set(now + t5. NCTS_BUSY_ _Delay LDU.7.3 RTS via source_if 2.3 LDU.2 set(now + t5. 2.req to self go_ _aloha go_ _CTS go_ _RTS 2.5.5.3 T2 2.19.2 2.7. T5) 2.5.

8(12) Wait_ _ACK 2.4 NAK reset(T16) 2.1).4 2.Page 85 APPENDIX I SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL Process Source_and_ Sink Synonym FSN_LSN_match boolean = true.5. T5) RTS via source_if Wait_ _CTS else DL_ ERROR.16 n4count := n4count +1 n5count :=0 2. T5) RTS via source_if Wait_ _CTS else DL_ ERROR.5.5.16 Wait_ _ACK SYN n5count := n5count +1 n4count :=0 2.4 go_ _rts FSN_LSN_ _match true Link_ _Idle 2.5.7.5.4 of 1st LDU 2.5.16 Link_ _Idle Link_ _Idle 2.5.5.16 n5count <N5 set(now + t5.7.16 T16 set(now + t5.5.5.5.5.7.16 2.19.req RTS LDU.16 2.16 .5.5.5.ind 2.16 2.16 2.1.ind n4count <N4 set(now + t5.16 2.2' go_ _aloha ACK set(now +t5.5.req to self ALO 'requeue file 2.16 LDU.5.16 2.5. (1.16 2. T5) RTS via source_if false Wait_ _CTS reset(T16) 2.5.7.ARINC CHARACTERISTIC 429 PART 3 .16 2. T5) RTS via source_if Wait_ _CTS 2.5.

9 go_ _aloha 2.1).5.15 unexpected FSN Link_ _Idle Wait_ _SOT EOT 2.19.5.5.Page 86 APPENDIX I SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL Process Source_and_ Sink Synonym LSN_FSN_confusion boolean = true.5.13.3 SYN via sink_if 2.14.5.13.2 Link_ _Idle .2 NAK via sink_if 2.5.15 true reset(T14) 2.2 T9 2.5.15 LDU_FSN_ _confusion false Wait_ _EOT 2. 9(12) Wait_ _SOT LDU. (1.5.2 2.5.3 'discard partial File' 2.5.13.req RTS ALO SOT go_ _rts 2.13.ARINC CHARACTERISTIC 429 PART 3 .1 Data 2.2 2.5.1.5.10.10.

2 2.13.19.5.2 'discard partial File' go_ _RTS reset(T14) reset (T14) 2. T14) 2.16 2.14.1.5.2 2.5.5.3. (1.13.req RTS ALO T9 NAK via sink_if set (now+ t14.5. Process Source_and_ Sink Wait_ _EOT LDU.13.9 'discard any partial LDU' go_ _aloha 2.13.5.Page 87 APPENDIX I SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL 10(12) Synonym valid_EOT boolean = true.5.3 Link_ _Idle 2.14.5.2 SYN 'discard partial LDU' 'discard partial File' 2.3 .5.6 Link_ _Idle 2.1).ARINC CHARACTERISTIC 429 PART 3 .

14.3 2.3' final_ LDU false set(now+ t14.3 NAK via sink_if 'discard any partial LDU' 2. Synonym duplicate boolean =true. not described Link_ _Idle 'discard any partial file' discuss.14 true 2.5.5.1). .ind L i n-k _ _Idle Link_ _Idle Synonym odd_parity boolean = true. Synonym final_LDU boolean = true.5.14.14.13.5.3 EOT 2. not described true final_LDU true reset(T14) set(now + t14. Wait_ _EOT is also the wait for data state 11(12) Data 2.5. Synonym LDU_CRC_correct boolean = true.5.14 duplicate Send LDU signal to upper layers 2.14.3 2.5.14 2.13. Synonym first_of new_file = true.5. Synonym correct_word_count boolean = true.14.1' 2.5.5.3 'ignore 2. T14) reset(T14) SYN via sink_if Link_ _Idle false 'discard any partial file' reset(T14) 2. Synonym next_or_duplicate boolean = true.5.13.5.5. T14) true false reset(T14) - - true 2.ARINC CHARACTERISTIC 429 PART 3 .1 2.2 first_of_ _new file false next_or_ _duplicate false discuss.5.Page 88 APPENDIX I SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL Process Source_and_ Sink (1.3 false LDU.6.5 odd_parity true 'store data word' false correct_ _word_ _count true LDU_ _CRC_ _count false 2.2 true 'discard LDU 2.3 ACK via sink_if 2.14.14.4 2.5.15 2.5.14.5.13.5.14.

Page 89 APPENDIX I SDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL 1(1) Process WCF idle DL_ UNITDATA. req FILE FILE_ via williamsburg _ifa DL_ UNITDATA. req - - .ARINC CHARACTERISTIC 429 PART 3 .

c-17 CMU/VDR VDL Mode 2 Interface ATN 1 Data Loader Mgt Entity ARINC SPECIFICATION 429 PART 3 .T X.Page 90 Protocol Layers Transport Layer CLTP/TP4 TCP/UDP Mgt MIB Figure J1-1 ARINC 429 Williamsburg Version 3 Protocol Layer Diagram CLNP Network Layer Subnetwork Sublayer (ITU.25/ ISO 8208) IP Mgt MIB APPENDIX J PROTOCOL STRUCTURE LLC ARINC 429 Information Frames Mgt MIB LLC Sublayer Data Link Layer MAC Sublayer ARINC 429 Command Frames Length Type ARINC 429 Williamsburg Version 3 MAC Protocol (Part 3) MAC Control ARINC 429 Command Frame MAC Control ARINC 429 Information Frame Mgt MIB Physical Layer ARINC 429 Physical Layer (Part 1) .

In the ISO network definition. the various characteristics of the ARINC 429 Version 3 specification.25 subset (profile).3. It may be used to provide a logical interface between peer entities. However. which enables it to provide a common set of services.. It may be required to provide services to the Network Layer. Network Layer – Other potential MAC Service Clients are either Internet (summarized by TCP/IP). these are the Subnetwork Access Protocols (SNAP) and provide services to the Subnetwork Independent Convergence Protocol (SNICP) and the Subnetwork Dependent Convergence Protocol (SNDCP). .n (with n bigger than 2) specifications. 802. e. link management information.1 this frame provides for a bridgeable frame format that is used by various applications. and interfaces with the LLC Sublayer.3 – IEEE used to assume that LLC resides above any of the 802. In this example. LLC Sublayer – One potential MAC Service Client is the Logical Link Control Sublayer.3 specification. however. The ARINC 429 (Williamsburg) Version 3 protocol specifies the functionality of the MAC Service Provider that provides two types of MAC Frames. Link Layer – It is responsible for the exchange of data between points (nodes) connected to one network.3-LENGTH – The “LENGTH” interpretation assumes that LLC is the MAC Service Client. It should be noted.3 TYPE interpretation. Xerox has shifted authority about the Ethernet specification to IEEE. a bridgeable Information frame based upon the frame structure specified in IEEE 802. c-17 error recovery and segmentation/reassembly. connectionlessacknowledged or connection-oriented. One network can be constructed either by a bus (A429. All IEEE 802 specifications share the notion of this “upper” portion of the Link Layer.3 (Ethernet) and a non-bridgeable Command frame for point-to-point transfers of data of any kind. The Network layer provides a home for specifications of protocols that support the communication across network boundaries.The physical layer is a high speed ARINC 429 data bus.ARINC SPECIFICATION 429 PART 3 . developed by Xerox. A429 Information Frame – As specified in section 3. Digital and Intel. Subnetwork Sublayer – In the scope of this document this sublayer is defined as an X. Transport Layer – This layer provides services for the exchange of information between communication applications. MAC Sublayer – The scope of this document is the “lower” part of the Link Layer. A429 Command Frame – As specified in section 3. In the example shown. The main difference between the two specifications was the interpretation of a field that is now called “LENGTH/TYPE”. these are. a “LENGTH” interpretation is specified.3 has always been in “competition” with the Ethernet specification. If the value in this field is less than or equal to 1500 decimal. Typical Applications This section focuses on the scope of this document. ÍEEE 802. IP or CLNP. 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. which may be used to provide a logical interface between LLC entities.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. A629) or by a set of buses and point-to-point links that can be interconnected by bridges (A646). Data Loader (via TCP/IP stack) or ATN 1 (via OSI stack) could take advantage of this format. Three classes of service have been defined which can be connectionless-unacknowledged. VDL Mode 2) or further standardized or non-standardized protocols.g.g.g. 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. specific (e. which incorporated it into the current (1998) edition of the 802. e. These services include flow control.3. IEEE 802.Page 91 APPENDIX J PROTOCOL STRUCTURE Physical Layer .

though). 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.3-TYPE – The “TYPE” interpretation assumes that a different protocol is the MAC Service Client. MAC Control – This functionality has been introduced recently and currently provides for a PAUSE function only. Information and Command. Assignments are documented in an Internet Request for Comment (RFC). 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. Both types of frames.ARINC SPECIFICATION 429 PART 3 .Page 92 APPENDIX J PROTOCOL STRUCTURE 802. It enables temporary suppression of any data transmission when sent to the peer MAC entity (reverse MAC Control commands can still be returned. . If the value in this field is bigger than or equal to 1536 decimal. support this function in c-17 different ways. the value specifies the respective protocol.

Page 93 APPENDIX K GLOSSARY & ACRONYMS ACK ADS AIDS ALR BOP BSAL CRC CT CTS DITS EOF EOT FDU GFI I/C IEEE IP ISO LAN LDU LLC LOOP LRU LSB MAC MSAL MSB MU NCTS OSI RTS SAI SAL SOF SOT TEST VDL Acknowledge Automatic Dependent Surveillance Airborne Integrated Data System ALOHA Response Bit-Oriented Protocol Bridge System Address Label Cyclic Redundancy Check Command Type Clear to Send Mark 33 Digital Information Transfer System End of Field End of Transmission Frame Data Unit General Format Identifier Information/Command Institute of Electrical and Electronics Engineers Internet Protocol International Standard Organization Local Area Network Link Data Units Logical Link Control Loop Test Response Line Replaceable Units Least Significant Bit Media Access Control Multicast System Address Label Most Significant Bit Management Unit Not Clear to Send Open Systems Interconnect Request to Send Systems Architecture and Interfaces Subcommittee System Address Labels Start of Field Start of Transmission Loop Test Pattern Word VHF Data Link .ARINC SPECIFICATION 429 PART 3 .

AERONAUTICAL RADIO.NOTE: Due to the large number of changes Created by this Supplement. 2551 Riva Road Annapolis. 1990 Prepared by the Airlines Electronic Engineering Committee Adopted by the Airlines Electronic Engineering Committee: October 25. 1989 . Maryland 21401 – 7645 USA SUPPLEMENT 12 TO ARINC SPECIFICATION 429 MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS) Published: July 1. INC. it is NOT available separately to update 429-11.

The contents of Sections 2. File Data Transfer.1. ATTACHMENT 1 – LABEL CODES The following labels have been given new assignments: 002 047 114 131 137 157 201 211 223 235 244 260 262 264 267 271 272 274 300 302 305 316 322 325 330 336 341 344 347 351 353 360 362 372 375 115 10B 10B 035 10A 10A 115 10A 116 039 10A 114 114 114 10A 10A 114 114 10A 10B 10B 10A 10B 10B 10B 10A 10A 10A 10A 10A 10A 10A 10B 10B 10A 013 107 127 132 137 157 203 211 224 235 244 261 263 265 267 271 273 275 300 303 306 316 323 326 331 336 341 344 347 351 353 360 362 373 375 0B8 0BB 10A 035 10B 10B 035 10B 116 040 10B 10A 10A 004 10B 10B 10A 10A 10B 10A 10D 10B 10A 10A 10A 10B 10B 10B 10B 10B 10B 10B 115 10A 10B 016 110 127 133 155 160 203 220 226 236 256 261 263 265 270 271 273 275 300 303 310 320 323 326 331 337 342 345 350 351 353 360 363 373 375 0B8 0BB 10B 10A 10A 10A 10A 116 035 039 114 10B 10B 038 10A 114 10B 10B TBD 10B 114 035 10B 10B 10B 002 10A 10A 10A 114 114 TBD 10A 10B TBD 046 112 130 133 155 160 203 221 230 236 257 261 263 265 270 272 273 275 301 304 311 321 324 327 335 337 342 345 350 352 354 361 363 374 10A 0BB 035 10B 10B 10B 10B 116 116 040 114 114 114 10A 10B 002 114 114 10A 10A 114 10A 10A 10A 10A 002 10B 10B 10B 10A 10A 10A 10B 10A 046 114 130 134 156 161 205 222 234 237 260 262 264 265 270 272 274 276 301 304 312 321 324 327 335 337 343 346 350 352 354 361 365 374 10B 0BB 10A 10A 10A 10A 10A 115 039 039 10A 10A 10A 10B 114 10A 10A 114 10B 10B 114 10B 10B 10B 10B 10A 10A 10A 114 10B 10B 10B TBD 10B 047 114 130 134 156 161 205 222 234 237 260 262 264 265 270 272 274 277 302 305 313 322 325 330 336 337 343 346 350 352 357 362 372 374 10A 10A 10B 10B 10B 10B 10B 116 040 040 10B 10B 10B 114 115 10B 10B 018 10A 10A 114 10A 10A 10A 002 10B 10B 10B 115 114 035 10B 10A TBD This section was revised and reorganized. The modified and added material on each replacement page is identified with “c-12” symbols in the margins.3 Information Identifier This section contains editorial corrections to comply with changes introduced in Supplement 11. the section header is retained and the original contents of this section are located in Appendix 6.4 through 2. In addition. Removed label 130 030 Traffic Advisory Range.1. printed on goldenrod paper contains descriptions of changes introduced into this Specification by this Supplement and where appropriate extracts from the original text for comparison purposes. Removed label 131 030 Traffic Advisory Altitude. The new protocol was developed to accommodate the interface of the ACARS Management Unit (MU) and the Satellite Data Unit (SDU).1. Each change or addition is entitled 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. any text originally contained in the Specification is reproduced for reference.1. For reference purposes.5. Copies of the Specification bearing the number 429-12 already contain this Supplement and thus do not require revision by the reader. C. . Existing copies of ARINC Specification 429 may be updated by simply inserting the replacement white pages they replace. 2. for other than very minor revision.5. The previous AIM and character-oriented file data transfer protocol sections are moved to Appendix 6.5.1.3.3) and moving the description of status priorities to Section 2.3.5 Bit-Oriented Communications Protocol This new section was added to describe a bit-oriented data transfer protocol. Revised label 131 035 from “Traffic Advisory Altitude” to “Intruder Altitude”. The Sign Status Matrix (SSM) information is revised and reorganized.1 Digital Language Revised label 130 035 from “Traffic Advisory Range” to “Intruder Range”.5 Sign/Status Matrix 2.SUPPLEMENT 12 TO ARINC SPECIFICATION 429 PART 3 – Page 2 A. 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. The changes include moving the AIM and file transfer SSM definitions to Appendix 6.5.3.7 were moved to Appendix 6. Revised label 132 035 from “Traffic Advisory Bearing” to “Intruder Bearing”.3.1.1. B. The AIM Data and File Data transfer section headings were retained for reference purposes. PURPOSE OF THIS SUPPLEMENT This Supplement introduces the Williamsburg bit-oriented file data transfer protocol which supports the transfer of binary and character data. provides the reason for moving the original file transfer protocol and introduces the Williamsburg protocol. adding failure reporting to the discrete word truth table (Section 2. 2. Section 2. The second part consists of replacement white pages for the Specification. 2. this Supplement introduces new label assignments and equipment identification codes. In each case there is included a brief description of the addition or change and. ORGANIZATION OF THIS SUPPLEMENT The first part of this document.2 AIM Information Transfer The information previously contained in this section is no longer applicable to ARINC Specification 429. 3. modified to reflect these changes. The goldenrod pages are inserted inside the rear cover of the Specification.

17A. ATTACHMENT 9B – GENERAL AVIATION WORD EXAMPLES Add new Company Name Identifier. Add new Attachment. ATTTACHMENT 11 – BIT-ORIENTED DATA FILE TRANSFER WORD FORMATS Add new Attachment. 16A. 18B. 16D. 18A.FILE TRANSFER EXAMPLE Add new Attachment. 127. 123. ATTACHMENT 15 . 125. 2 updated to reflect changes to Attachment 1. ATTACHMENT 11C . 117. 18F. 124.LINK LAYER CRD DATA EXAMPLE Add new Attachment. Add format for Transponder Altitude/TCAS Own A/C Altitude label 203. 129. ATTACHMENT 12A . 17C. VARIABLES OF BIT- . ATTACHMENT 1 – EQUIPMENT CODES The following codes have been given new assignments: 113.FIELD MAPPING EXAMPLE ATTACHMENT 13 . 15B. 11A.FORMER MAINTENANCE. 18C. 16C. 17B. 15E. 15C. APPENDIX 6 . ATTACHMENT 12 . 18E. ATTACHMENT 10 – ORIENTED PROTOCOL Add new Attachment. Add new Attachment. ATTACHMENT 2 – DATA STANDARDS Add new Attachment. Add format for TCAS Intruder Bearing label 132.DESTINATION CODES Add new Attachment. APPENDIX 7 – MATHEMATICAL EXAMPLE OF CRC ENCODING/DECODING Add new Appendix. Removed 730 ASAS Sector Control Word example. Add format for TCAS Intruder Altitude label 131. Removed 347 035 Antenna Control. Binary Data notes 6. ATTACHMENT 11B . 16E. 114. 118.SUPPLEMENT 12 TO ARINC SPECIFICATION 429 PART 3 – Page 3 Removed label 132 030 Traffic Advisory Bearing Estimate. Removed 730 TCAS Traffic Advisory Range Word example. 15D. 7 and 8 added. 128. 15A. Removed label 270 030 Transponder Discrete.STATUS CODES Removed label 347 030 Sector Control. 119. Tables 1. AIM AND FILE TRANSFER TECHNIQUES Add new Appendix. 126. 115. 18D. Removed 730 TCAS Traffic Advisory Bearing Estimate Word example. 16B.ALOHA/ALOHA RESPONSE PROTOCOL WORDS Add new Attachment.PROTOCOL DETERMINATION PROCEDURE DIAGRAMS Add new Attachment. ATTACHMENT 6 – GENERAL WORD FORMATS AND ENCODING EXAMPLES Add format for TCAS Intruder Range label 130. 116. Discrete Data Standards entered for new labels: ATTACHMENT 14 – SYSTEM ADDRESS LABELS 272 277 275 351 002 018 035 114 271 274 013 352 018 018 0B8 114 272 270 016 353 018 035 0B8 114 273 271 161 270 018 035 10A 115 275 273 161 350 018 035 10B 115 276 018 274 035 350 114 ATTACHMENT 11A .

Maryland 21401 – 7645 USA SUPPLEMENT 13 TO ARINC SPECIFICATION 429 MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS) Published: December 30. 2551 Riva Road Annapolis. 1991 Prepared by the Airlines Electronic Engineering Committee Adopted by the Airlines Electronic Engineering Committee: October 8. 1991 . INC.AERONAUTICAL RADIO.

2. this Supplement introduces new label assignments and equipment identification codes. printed on goldenrod paper contains descriptions of changes introduced into this Specification by this Supplement. 2.11 Data The fourth paragraph of this section was updated to describe the proper ending of an LDU transmission.5.5. 2.1 and in conflict with other possible responses. 2. 2.1. 2.11. 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. 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. PART 3 ONLY. correction to section numbering.5.3. C.5. The second paragraph was updated to describe that and NCTS counter would be reset upon a valid CTS response. 2.1 Clear to Send (CTS) The first part of this document.6.5. ORGANIZATION OF THIS SUPPLEMENT 2.1. PURPOSE OF THIS SUPPLEMENT This Supplement introduces changes made to the Williamsburg protocol as a result of its initial implementation.5.5.13.5.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.5.4 Bit Rate and Word Timing Corrected the commentary to change the more ambiguous term “message” to LDU.2.5 File Data Transfer An editorial change. The last sentence was added to clarify the resetting of RTS counters.7 No Response to RTS The first paragraph of this section was updated to describe proper response to RTS.5.6.6.6 Response to RTS The last sentence in the second paragraph was reworded and moved to a more appropriate section. since it is a requirement.5. The modified and added material on each page is identified by a c-13 in the margins. Corrected Network Layer definition.5.2 Not Clear to Send (NCTS) The first paragraph was updated to include the information deleted from Section 2.3 Destination Code An editorial change was made. D. and to include the optional NAK response for receipt of an incomplete octet. 2. The second part consists of replacement white pages for the Specification.5 Bit-Oriented communications Protocol Included term “Williamsburg” parenthetically since this terminology well-known in industry.6 and to clarify the validity requirements. the “note” designator was removed and the text clarified for the transfer of characters with a parity bit. 2. In addition.5. modified to reflect the changes. 2. The last sentence was deleted as redundant to Section in 2.SUPPLEMENT 13 TO ARINC SPECIFICATION 429 – Page 2 A.6. 2. B.5. 2. 2.3. the word “valid” was added to clarify the Not clear to send condition. .9 Unexpected RTS This section was updated to include editorial changes and a description of the correct responses to RTS. In each case a brief description of the change or addition is included.5. The goldenrod pages are inserted inside the rear cover of the Specification.5. and removed second paragraph from commentary.2 Link Data Unit (LDU) Size and Word Count Added second paragraph to text. 2. Added commentary to explain non-negotiation or parameters in this protocol. This protocol supports the transfer of binary and character data.3 Character Data Words In the last paragraph.5. 2.13 Negative Acknowledgement (NAK) This section was updated to clarify conditions for sending the NAK word. In the second to last sentence.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. AEEC STAFF NOTE: THESE CHANGES APPLY TO ARINC 429. The last sentence in the third paragraph was deleted and it’s content expanded in the following commentary of that section. Existing copies of ARINC Specification 429 may be updated by simply inserting the replacement white pages where necessary and destroying the pages they replace.

5. 2. 2.7 were renumbered.14 LDU Transfer Acknowledgement (ACK) Text was revised to include LDU conditions for sink acknowledgement transmission.5. 2. “(X)” was corrected to “Q(x)”.13. 2.14. N6.5. 2.5.13.7 Restart Initialization This section was omitted due to potential conflicts with the ALO/ALR procedures.4 Word Count Errors ATTACHMENT 12A – FIELD MAPPING EXAMPLE This section was updated to clarify the NAK response time for word count errors.SUPPLEMENT 13 TO ARINC SPECIFICATION 429 – Page 3 2.19 ALO Response A new section was added and updated to describe ALO responses.5.5.16 Response to ACK/NAK/SYN New text was added to describe actions when NAK and SYN are detected during a transmission.5 CRC Errors This section was updated to clarify the NAK response time for CRC errors. and semi-octet arrow lengths were shortened to correspond to the proper four and eightbit lengths. incorrect text referring to the NAK response timing was deleted. .5. Also.13.13.13.3 Parity Errors A commentary section was added to describe the procedures for receiving words with bad parity.1 – ATTACHMENT 11C – ALOHA/ALOHA RESPONSE PROTOCOL WORD DEFINITION ATTACHMENT 10 – ORIENTED PROTOCOL VARIABLES OF BIT Tables 10-1 and 10-3 were updated to include events N5.14.15 SYN Word New text was added to describe SYN response times for non-consecutive LDU Sequence numbers. 2. and time T12.5.5. and the transmission order for the LDU Mapping of the 24-bit example was deleted to avoid possible misinterpretation.13.2 Auto-Synchronized Files This section was added to describe the method of handling auto-synchronized files. The last paragraph was incorrect and deleted.5. Options 07 and 012 in Table 10-4 were changed to spares for consistency with corresponding text updates.13.1 Duplicate LDU This section was added to describe duplicate LDU occurrences. Bk was changed to B24 in the data word map.13.5.2 LDU Sequence Number Error The original text was omitted. APPENDIX 7 – MATHEMATICAL EXAMPLE OF CRC ENDODING/DECODING Table 11C-3 was added to clarify protocol version number assignments. Sections 2.13.5. Format (alignment) changes were made in the polynomial divisions. 2. 2. “Note 2” was added to describe the GFI field of the ALOHA word.1 Missing SOT word Text was corrected to refer to “reception” instead of “transmission” of a valid SOT word. 2. 2.6 Time Out Errors This section was renumbered. and is referenced by “note 1”.5.5. 2. 2.5. 2. “nibble” was changed to “semi-octet”.

2551 Riva Road Annapolis. 1993 Prepared by the Airlines Electronic Engineering Committee Adopted by the Airlines Electronic Engineering Committee: November 4. INC. Maryland 21401 – 7645 USA SUPPLEMENT 14 TO ARINC SPECIFICATION 429 MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS) Published: January 4.Copyright 1993 by AERONAUTICAL RADIO. 1992 .

2. B. and an introductory paragraph added to clarify the basic RTS function.5.4 Bit Rate and Word Timing A maximum word gap of 64 bit-times.7.5 Bit-Oriented Communication Protocol An editorial change references a new section number. 2. printed on goldenrod paper.5. 2.7.7 Request to Send (RTS) This section was previously titled “Response to TS”. C.5.3 Word Count This section was renumbered.5 through 2. New commentary equates a “timely manner” to the shorter retry sequence of the NCTS series.5. 2.6.5.19. 2.5.6 Protocol Words This section was added to specifically define the word type for protocol words. The second part consists of replacement white pages for the Specification. 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.10 Start of Transmission (SOT) 2.5 File Data Transfer An editorial change was needed to reference new section.1 Clear to Send (CTS) This section was renumbered. 2. Existing copies of ARINC 429 may be updated by simply inserting the replacement white pages where necessary and destroying the pages they replace.7.5. and a commentary added.6.1 General Format Identifier (GFI) This section was updated. In each case a brief description of the change or addition is included. The requirement for Destination code validation is not a link layer function. The modified and added material on each page is identified by a c-14 in the margins. contains descriptions of changes introduced into this Specification by this Supplement.5. AEEC STAFF NOTE: THESE CHANGES APPLY TO ARINC 429. This protocol supports the transfer of binary and character data.1.6.5. 2. 2. The title was changed for consistency.3. 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.4 No Response to RTS This section was renumbered.5. The goldenrod pages are inserted inside the rear cover of the Specification. 2. 2.2 Not Clear to Send (NCTS) This section was renumbered.5. .3.1 Protocol Identifier This section was added to clarify the definition of bits 2825 for protocol words and to specify the relevant addition for error conditions. PART 3 ONLY.1.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. to clarify the role of the link layer protocol for upward compatibility with changing network functionality. modified to reflect the changes. 2. 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. which may be used when a system cannot accept a transmission by the source in a “timely manner”. 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.7 have been renumbered and reordered for consistency.5. ORGANIZATION OF THIS SUPPLEMENT The first part of this document.10. and was moved to Section 2. 2.2 Destination Code This section was updated.1 Bit-Oriented Protocol Determination This section was expanded to include determination of different version numbers of the bit-oriented protocol.3 Destination Busy This section was renumbered. 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. and an introductory replacement paragraph inserted to clarify the “optional” BUSY response. (averaged over the LDU transmission) was added to eliminate excessive delay in source transmission time. GFI validation is not necessarily a link layer function. and has been renumbered.5. and the ALOHA word was included in the logic for error determination.5.5.7. 2.SUPPLEMENT 14 TO ARINC SPECIFICATION 429 – Page 2 A. 2. Note: Sections 2. and commentary added to clarify the role of the GFI in pre-OSI as well as OSI environments. 2.

Table 10-3 deleted Option 6 (O6) for NAK Send Time.e. ATTACHMENT 1 – EQUIPMENT CODES New Equipment Code Identifiers were added. The bit pattern (0100) for ISO 8473 was changed to a more Table 11-1A added “spares” for the deleted Character Data Formats and corrected “Protocol Data Word” to read “Protocol Word”. and 2.SUPPLEMENT 14 TO ARINC SPECIFICATION 429 – Page 3 2.6 “Windowed Bit-Oriented Protocol”).3.19. 2.16 Response to ACK/NAK/SYN The T16 timer was introduced to replace T10 and T8.1 Bit-Oriented Protocol Determination 2.20 Bit Protocol Verification 2.5. The definition includes provision for a Link Control Word prior to each LDU.5.5.13 Negative Acknowledgement (NAK) NAK word interpretation was changed to remove constraint on source for specific order of file sequencing (i. 2.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. .11 Data All references to Character Data word formats were deleted.5. Table 10-6 was added to include notes to Tables 10-1 through 10-5.6. 2. and Table 11-4 updated definitions for bits 9 through 24 of the ALO and ALR words.3 Character Data Words This section was deleted. These values were established for timers and as response time design goals for incoming transmissions. 2. ATTACHEMENT 6 – WORD ENCODING EXAMPLES Example added for label 171. It ensures that a source device cannot “lock-up” a sink.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. Table 10-5 was added to include a definition of high speed maximum and minimum values for timers and response time design goals. 2.2 ALOHA Response. as the format is incompatible with those for Full and Partial Data word formats. 2. changing the former GFI bit pattern (0001) for ISO 8208 to “unassigned”.5.5.5. Also.19. The format is the same as the revised Table 10-4.5. It is based on Section 2.5.19. ATTACHMENT 10 – ORIENTED PROTOCOL VARIABLES OF BIT 2.15 SYN Word The LDU sequence anomalies which generate a SYN response by the sink were clarified.1 Duplicate LDU This first paragraph was rewritten to clarify.5. These sections replace three sections from Supplement 13. which relaxes requirements to maintain a specific File Sequence ordering by the source.19 ALO Response. The Character Data Word format was removed from Supplement 14.5. both binary and character data are transmitted in octets defined by the other two data word formats.14. The text for equation: M9x) = x16G(x) + R(x) was corrected by moving the “bar” from G(x) to R(x).19 Protocol Initialization 2.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. both of which are no longer used. and added the LCW (LDU Control Word) format definition. Currently.12. ATTACHMENT 11 – BIT-ORIENTED DATA FILE TRANSFER WORD FORMATS Table 10-4 was revised to include columns for low speed maximum and minimum values. Allows source to restart file with new FSN if necessary). Timers T13 through T16 were added. 2. 2.5.1.5. the maximum number of LDUs in a window (see Section 2.1 Bit-Oriented Protocol Version. The special character data format is not required. Table 11-6A was revised.5. 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 BitOriented protocol in Section 2.1 CRC Encoding References to character data words were deleted.11. Timer T10 is not used in the high speed protocol. 2. “BitOriented Communications Protocol”.14. FORMATS AND Table 10-1 was updated to include a standard value for N7. with expanded text as specified to allow for more efficient use of the 429 high (or low) speed data bus through “windowing”. and deleted Option 9 (O9) for the Character Data Word.5.5. 2. the action taken by the source upon receipt of a SYN word was updated.

. The bit pattern 1110 (hex”E”) is now defined as “ACARS VHF Format”.19. ATTACHMENT 17 – FLOW DIAGRAM USED TO DETERMINE CHARACTER-ORIENTED VS BITORIENTED PROTOCOL This Attachment was added to illustrate the logic flow that determines whether a character-oriented or bitoriented link layer protocol interface is to be used.1.1. 11-4A. ATTACHMENT 13A – ALOHA DETERMINATION SEQUENCE VERSION This Attachment was added to support the ALOHA version determination sequence called out in Section 2. This information has been moved to Tables 11-4.5. 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.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.SUPPLEMENT 14 TO ARINC SPECIFICATION 429 – Page 4 ATTACHMENT 11 – BIT-ORIENTED DATA FILE TRANSFER WORD FORMATS (cont’d) generic ISO 9577 definition.6. and 11-4B.

Copyright 1995 by AERONAUTICAL RADIO. 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. 2551 Riva Road Annapolis. INC. 1995 Prepared by the Airlines Electronic Engineering Committee Adopted by the Airlines Electronic Engineering Committee: April 18. 1995 .

Table 10-5 VARIABLES OF HIGH SPEED BITORIENTED PROTOCOL . Part 1 also contains the listing of data word labels assigned for the transmission of broadcast periodic data. printed on goldenrod paper. Therefore. File Data Transfer Techniques. In the text. The fundamental physical layer descriptions of the wire. ATTACHMENT 11 . printed on white paper. PURPOSE OF THIS SUPPLEMENT This portion of Supplement 15 provides corrections and additions to the file transfer provisions of ARINC Specification 429. The SDL diagrams have not been fully proofed. voltage levels and coding of data are contained in Part 1. ATTACHMENT 11B .VARIABLES OF BIT-ORIENTED PROTOCOL Revised Notes 1 and 4. 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.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 APPENDIX 8 . Added entries for Code 8E through 95. Appendix C was added to assist designers in establishing connectivity between LRUs designed to different versions of Specification 429. a brief description of the change or addition is included. file data transfer is nonperiodic in nature. the modified and added material on each page is identified by a c-15 in the margins. existing copies of ARINC 429 cannot be updated. ATTACHMENT 14 .DESTINATION CODES Added Cabin Packet Data Function. This part. they will be moved to an Attachment. In each case. The following changes affect only ARINC Specification 429-15. APPENDIX 9 . ATTACHMENT 10 .STATUS CODES Revised description of Code 86.Revised Time T10 min and max values. Part 3. Typically. When the SDL diagrams have been validated. Appendix D comprises the Specification and Description Language (SDL) diagrams that reflect the intent of the textual material. Part 2 contains a tabulation of the ever-increasing list of Discrete data words used to provide status information. The reader should note that the organization of ARINC 429 has been described in Section B below. Refer to Parts 1 and 2 for changes impacting the broadcast provisions of ARINC Specification 429. 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. the text material has precedence over the SDL diagrams.BIT-ORIENTED DATA FILE TRANSFER WORD FORMATS Table 11-6A GENERAL FORMAT IDENTIFIER (GFI) Revised “Reserved ISO 9577” to “ISO 9577” ATTACHMENT 11A . contains the definition of the protocols used for file data transfer. . Part 3. In view of the document reorganization. and remain advisory in nature. Table 10-3 BIT-ORIENTED PROTOCOL OPTIONS Added Option 012.SUPPLEMENT 15 TO ARINC SPECIFICATION 429 PART 3 – Page 2 A. 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. ORGANIZATION OF THIS SUPPLEMENT The portion of this document.SDL DIAGRAMS OF THE WILLIAMSBURG PROTOCOL Appendix added.INTEROPERABILITY OF BITORIENTED LINK LAYER PROTOCOL Appendix added. Corrected Ground Station bit encoding. B. contains descriptions of changes introduced into this Specification by this Supplement. This Supplement is the first in which ARINC Specification 429 is divided into three parts.

3. Part 2 “Digital Information Transfer System Standards” and Part 3 “File Data Transfer Techniques.8.1 1.6.8.3 1.3 2.5 2.7.8.2 1.1 2.2 2.” The changes are described in Supplements printed on goldenrod colored paper.2 3.5.3 2.5.5.5 2.1 3.8.5.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”.7.9 3.10 New Number (Supp 15) 1.2 1. 4 Data Transfer changed to: Broadcast Data Graphic Data Transfer File Data Transfer Bit-Oriented Protocol Determination Transmission Order Bit-Oriented Communications Protocol changed to: Bit Oriented File Transfer Protocol Bit-Oriented File Transfer Protocol Link Data Units (LDU) Link Data Unit (LDU) Size and Word Count System Address Labels (SAL) Bit Rate and Word Timing Word Type Protocol Words Protocol Identifier Destination Code Word Count Request To Send (RTS) Clear To Send (CTS) Not Clear To Send (NCTS) Destination Busy (BUSY) No Response to RTS Conflicting RTS Transmissions Half Duplex Mode Full Duplex Mode Unexpected RTS Start of Transmission (SOT) .5.3.3 3.8 2.5.3 3.11 Section Title Purpose of this Document Relationship to ARINC Specification 419 changed to 429 “Mark 33 Digital Information Transfer System”_ .5.1 3.9.7 3.2 2.5 2.3 3.10 3.5.1 2.Basic Philosophy changed to: “File Data Transfer Techniques” Number Data Transfer changed to: Data Transfer ISO Alphabet No.5.3 2.3.3.2 2.1 1.2 1.3.2 3.0 3.2 2. Old Number (Supp 14) 1.6 3.1 3.3 2.1 1.7.7.1 1.5.7.2 3.2 3.5.3.4 2.2 1.4 2.5.1.3 2.6.3.1 2.5.2 2.5 3.7 2.8.2 Chapter 3.3 2.5 2.1 2.6.3.9 2.6 2.1.7.8 3.5.5.5.7.3.3 1.5.8. The following pages provided a record of the section numbering of the text now included in Part 3.4 3.4 3.5.5.1 2.1 3.5.9.1 2.

19.3 2.2 3.5.2 2.4 3.16 3.1 2.10.11.2 3.11.10.1 2.5.12.6 3.15 2.1 3.1 3.13.14.5.5.5.18 2.1 2.17 3.17.5.12 2.5.1 4.5.5.18.2 2.20.5.13.2 2.2 3.5.5.13.6 2.5.1 2.6 2.4 2.1 3.3 3.5.5.SUPPLEMENT 15 TO ARINC SPECIFICATION 429 PART 3 – Page 4 Old Number (Supp 14) 2.1 3.18 3.1 3.3 2.17 2.2 New Number (Supp 15) 3.14 3.5.16 2.14.14.5.20 3.14.5.1 2.1 3.6.5.5 3.15.17.14 2.2 3.5.13 3.15 3.5.5.11.2 3.5.14.2 4.3 2.11 2.12.15.5.6 2.2 3.2 3.20.5.1.5.2 2.2 2.3 3.11.5.20.15.13 2.0 4.1.13.1 3.5.12.12 3.1 2.19 3.3 Section Title General Format Identifier (GFI) File Sequence Number LDU Sequence Number Data Full Data Word(s) Partial Data Word(s) End of Transmission (EOT) CRC Encoding CRC Decoding Negative Acknowledgement (NAK) Missing SOT Word Missing EOT Word Parity Errors Word Count Errors CRC Errors Time Out Errors LDU Transfer Acknowledgement (ACK) Duplicate LDU Auto-Synchronized Files Incomplete File Time SYN Word Response to ACK/NAK/SN Solo Word Test Word and Loop Word Optional Solo Word Definitions Optional End-to-End Message Verification Protocol Initialization Bit-Oriented Protocol Version ALOHA ALOHA Response Williamsburg/File Transfer Determination Window Bit-Oriented Protocol change to: Window Bit-Oriented File Transfer Protocol Windowed Bit-Oriented Protocol change to: Windowed Bit-Oriented Communications Protocol Window Size Window Definition .5.14.19.1.13.5.19.1 2.2 2.1 2.2 Chapter 4.10.14.5 2.1 3.19 2.13.5.11.2 2.14.2 3.6.14.12.19.13.18.1.13.2 2.20.1 2.

3.4.7.6.3 2.7 4.7.3.5 2.6 4.4 2.3.4.6.6 2.1 4.3.4.1 2.6 2.4.4.3.6.3 4.4.1.4 4.6.7.SUPPLEMENT 15 TO ARINC SPECIFICATION 429 PART 3 – Page 5 Old Number (Supp 14) 2.3.5 4.4.1 2.6.1.6.6 4.7 2.2 ATT 1 Table 1-1 Table 1-2 Table 1-3 Table 1-4 Table 1-5 ATT 2 Table 2-1 Table 2-1A Table 2-2 Table 2-3 Table 2-4 Table 2-4A Table 2-4B Table 2-5 Table 2-6 Table 2-6A Table 2-7 Table 2-7A ATT 3 Section Title Protocol Word Deltas Request To Send (RTS) Unexpected Request To Send (RTS) Clear To Send (CTS) Not Clear To Send (NCTS) BUSY LDU Control Word (LCW) Start Of Transmission (SOT) Negative Acknowledgement (NAK) Missing LDU Control Word Missing SOT Word Missing EOT Word Parity Errors Word Count Errors CRC Errors LDU Timeout Errors Window Transfer Acknowledgement (ACK) Determination of End of Window Incomplete File Timer Bit Rate and Word Timing Response to ACK/NAK/SYN Protocol Initialization Deltas ALOHA ALOHA Response Variables of Bit-Oriented Protocol Bit-Oriented Protocol Events Bit-Oriented Protocol Application Selection Bit-Oriented Protocol Options Variables of Low Speed Bit-Oriented Protocol Variables of High Speed Bit-Oriented Protocol Bit-Oriented Data File Transfer Word Formats General Word Format Word Type Full Data Word Partial Data Word Protocol Word ALO-ALR Version Number ALO-ALR Window Size Solo Word Start of Transmission General Format Identifier (GFI) End of Transmission Final LDU Bit Destination Codes .4.4.6.6.4.3.8.3.7.3.7.8.2 2.4.6.6.8.7.3.6.3.6.4.6.1 4.6.6 4.7 2.6 2.7.6.3 2.6.2 2.3.7.7.3.2 4.2 2.6.1 2.6.7 4.6.3.4.1 4.1 4.7 4.4 4.4 4.4.1 2.6.7.8 2.5 2.4.7.6.7.2 ATT 10 Table 10-1 Table 10-2 Table 10-3 Table 10-4 Table 10-5 ATT 11 Table 11-1 Table 11-1A Table 11-2 Table 11-2 Table 11-4 Table11-4A Table 11-4B Table 11-5 Table 11-6 Table 11-6A Table 11-7 Table 11-7A ATT 11A New Number (Supp 15) 4.7.4 2.2 4.5 4.1 2.3.7.8 4.8.6.4.3 4.4.6.4 2.4.3.6.7.7.3 2.3.5 2.1 4.2 4.6.6.3.5 4.

3 A2.5 A6-2.5 A2.4 A6-2.3.1 A6-3.2.5.1.3.1.3.1.1.2 A2.2 A6-3.1.1.5.6 A6-2.4 A2.3.1.5.1 A6-2.5.3.2 A3.5.3.4 A6-2.5.3.3 A6-2.1.2.5 A6-2.1.5 A2.3 A2.3.5.5.5.3.1.3.2.3.3 APPENDIX B APPENDIX C APPENDIX D Section Title Status Codes ALOHA/ALOHA Response Protocol Word Definition ALOHA Initial (ALO) Protocol Word ALOHA Response (ALR) Protocol Word Version Number for ALO/ALR Protocol Words File Transfer Example Field Mapping Exchange Protocol Determination procedure Diagrams Protocol Determination Procedure Diagram (Two Bilingual Units) Protocol Determination Procedure Diagram (One Bilingual Unit and One Character-Only Unit) ALOHA Version Determination Sequence Link Layer CRC Data Example Sequence of Protocol and Data Words in Window Transfer Flow Diagram Used to Determine Character-Oriented vs Bit-Oriented Protocol Former AIM and File Data Transfer Techniques Sign/Status Matrix AIM Data Character-Oriented File Transfer Digital Language AIM Data File Data Transfer Command/Response Protocol Initial Word Types Intermediate Words Final Words Word Type Encoding File Data Formats File Data Labels AIM Information Transfer Acknowledgement Data ISO Alphabet No.7 A6-3.3.3.3.1.2 A2.2.2 A3.1.3.1.3.2.3.1.5.1.5 A2.7 A-3.5.3 A6-2.1.1.3.5.1.5.3.5.1. 5 Data Maintenance Data Mathematical Example of CRC Encoding/Decoding Interoperability of Bit-oriented Link Layer Protocol SDL Diagrams of Williamsburg Protocol .1 A6-2.1.5.4 A2.5 A6-2.5.6 A2.SUPPLEMENT 15 TO ARINC SPECIFICATION 429 – Page 6 Old Number (Supp 14) ATT 11B ATT 11C Table 11C-1 Table 11C-2 Table 11C-3 ATT 12 ATT 12A ATT 13 Diagram 13-1 Diagram 13-2 Diagram 13-3 ATT 13A ATT 15 ATT 16 ATT 17 APPENDIX 6 A6-2.1 A3.1.1 A2.2 A6-3.3.5.2 A6-2.5.2 A6-2.1.2.1.3 APPENDIX 7 APPENDIX 8 APPENDIX 9 New Number (Supp 15) ATT 4 ATT 5 Table 5-1 Table 5-2 Table 5-3 ATT 6 ATT 7 ATT 8 Diagram 8-1 Diagram 8-2 Diagram 8-3 ATT 9 ATT 10 ATT 11 ATT 12 APPENDIX A A2.1 A2.1.

Copyright 1997 by AERONAUTICAL RADIO. Maryland 21401 . 2551 Riva Road Annapolis. INC.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 .

6 and subsections contained the material previously published in Section 4. Part 3.1.3.5. and creation of the Version 3 protocol. 1. and Section 1.1 Link Data Units (LDU) The definition of LDU is clarified. The definition of the Version 3 protocol will be completed in a future Supplement.5. INTRODUCED BY THIS SUPPLEMENT This section presents a complete tabulation of the changes and additions to the Specification introduced by this Supplement.4 include minor changes clarifying the background for file data transfer.4 Bit Rate and Word Timing Commentary on use of word gap criteria clarified.1 – 2. 2. Section 2. 2. 2.15 SYN Word The definition of a duplicate LDU is clarified. 2.6 on Bit-Oriented Protocol Determination (formerly 1. The second part.81 Half Duplex Mode This section restores text missing from the published version of Part 3. Section 2. 2.SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 3 – Page 2 A.2 ALOHA Response This section restores text missing from the published version of Part 3. 1. In view of the document reorganization. Part 3. .5. Commentary on use of SALs clarified. 2.0 Bit-Oriented File Transfer Protocol Section number 2.2.5.3.2 Destination Code Introduction to section added. 2. Supplement 15. Supplement 15. printed on goldrod colored paper.0 Introduction This section contains a reorganization of the material previously in Section 1. CHANGES TO ARINC SPECIFICATION 429.5.5.3.5.5. Section 2.5.2 Partial Data Word Location of the length of a partial data word is clarified.3 Destination Busy (BUSY) The use of Option 3 (Send Auto CTS) and Option 4 (Accept Auto CTS) is clarified.6 and subsections have been deleted. C.1 Duplicate LDU The definition of a duplicate LDU is clarified.5. 2. 1. deletion of the Version 2 protocol.5. is reprinted in its entirety as ARINC Specification 429-16.11.7.6 contained the definition of Version 2 of the Williamsburg protocol.5 and subsections contain the material previously published in Section 3.6. and commentary is added on use of a NAK in the protocol determination logic.19. The technical changes include clarification of the Version 1 (Williamsburg) protocol. as modified below. In each case.3.5.5. Supplement 15.3. printed on white paper. contains the changes made to the specification. Each change and addition is defined by the Section number and the title that will be employed when the Supplement is eventually incorporated. and use of Destination Code clarified.1. a brief description of the change or addition is included.0 of ARINC Specification 429P3-15.14. Windowed Bit-Oriented Communications Protocol 2.7) was revised to refer to Section 2. ARINC Specification 429.5.19.3 Word Count Introduction to section added. The modified and added material on each page is identified by a c-16 in the margins. 2.2 Williamsburg/File Transfer Determination This section restores text missing from the published version of Part 3. Sections 1.5. It also restores several paragraphs missing from Supplement 15. contains descriptions of the changes introduced into this Specification by this Supplement. and 1.3 System Address labels (SALs) Section 2.19 Protocol Initialization The protocol version determination is clarified. ORGANIZATION OF THIS SUPPLEMENT The first part of this document. 2.1 ALOHA The protocol version determination is clarified. PURPOSE OF THIS SUPPLEMENT This Supplement reorganizes Part 3 to be consistent with previous published versions of ARINC Specification 429. 2. 2.4) is deleted.4 have been inserted as placeholders to re-establish section numbering consistency with ARINC Specification 429-14 and its predecessors.19. Version 2 of the Williamsburg protocol has been superseded by Version 3. 2.19.0 and 2.3. 2.0 of ARINC Specification 429P315. B.0 of ARINC Specification 419P3-15 with the following exceptions.6 2.1.19.5. 2.6.5 Bit-Oriented Communications Protocol References to Attachments 12 and 12A updated.1 Bit-Oriented Protocol Version The protocol version determination is clarified. The section on Graphic Data Transfer (formerly 1. 2.3.

ATTACHMENT 11 . Appendices F-J contain the material published in Appendices A-D of ARINC 429P3-15. Table 11-4B is deleted as part of the Version 2 protocol.SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 3.LINK LAYER CRC DATA EXAMPALE This section is deleted as part of the Version 2 protocol. ATTACHMENT 11A . and delete references to Version 2.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. Variables for the Version 2 protocol in Tables 10-1 and 103A are deleted. as modified below.0 Bit-Oriented Media Access Control (MAC) An introduction to the Bit-Oriented Media Access Control (Williamsburg Version 3) protocol is added.VERSION 1 FILE TRANSFER EXAMPLE The title is changed to indicate Version 1. Table 11-4 is modified to add the Service Class Identifier to the LCW format. containing options for Version 1. Center. The LCW protocol word format in Table 11-4 is modified. ATTACHMENT 10 .FIELD MAPPING EXAMPLE Attachment 12A is replaced with an updated example ATTACHMENT 15 . and the titles of the tables modified to indicate they are examples. Appendix numbers A-E have been inserted as placeholders to re-establish section numbering consistency with ARINC Specification 429-14 and its predecessor. ATTACHMENT 11C . ATTACHMENT 16 . Tables 10-3B. Attachments 10-17 contain material published in Attachments 1-12 of ARINC Specification 429P3-15. Appendix H was revised to reflect the deletion of the Version 2 protocol and creation of the Version 3 protocol.Page 3 3.DESTINATION CODES The destination Code N for FMC.BIT-ORITENTED DATA FILE TRANSFER WORD FORMATS The general word format in Table 11-1 is clarified. Table 11-4A is modified to add the version number for Version 3. 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. is added. ATTACHMENT 12A . APPENDICES A-K . ATTACHMENT 12 .VAIABLES OF BIT-ORIENTED PROTOCOL Table 10-3 is replaced with Table 10-3A.SEQUENCE OF PROTOCOL AND DATA WORDS IN WINDOWN TRANSFER This section is deleted as part of the Version 2 protocol. 10-6 and 10-7 are added as placeholders for Version 3 Williamsburg.

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. INC.Copyright© 1999 by AERONAUTICAL RADIO. 1999 . 2551 Riva Road Annapolis.

.SUPPLEMENT 17 TO ARINC SPECIFICATION 429 PART 3 – Page 2 A. containing options for Version 3. .BIT ORIENTED DATA FILE TRANSFER WORD FORMATS Table 11-1A was updated to add Version 3 SOF and EOF words. Table 10-6. most significantly. PURPOSE OF THIS SUPPLEMENT This Supplement introduces the definition of a new bitoriented file data transfer protocol. Table 11-9 was added defining the command frame EOF.VARIABLES OF BIT-ORIENTED PROTOCOL Table 10-3B. Version 3 is intended to be capable of being bridged to other common data bus protocols. In the body of the document. replacing introductory text inserted by Supplement 16 as a placeholder. followed by a brief description of the change or addition. CHANGES TO ARINC SPECIFICATION 429. Version 2 was deleted by Supplement 16.4 Relationship to Other Standards A new section was added. APPENDIX 10 . ATTACHMENT 10 . was added. printed on goldenrod-colored paper.ARINC 429 WILLIAMSBURG PROTOCOL LAYER DIAGRAM A new Appendix was added providing a general overview of the protocol structure over different communication stacks. This part. ATTACHMENT 18 – MAC SUBLAYER SUPPORT DIAGRAMS New Attachment added. containing a placeholder for low speed bus timers associated with Version 3 protocol was deleted because the low speed implementation is not recommended.0 Bit-Oriented Media Access Control Protocol The definition of the bit-oriented Media Access Control (Williamsburg Version 3) protocol was added. Table 11-8 was added defining the command frame SOF.5 Transmission Order Transmission order of bits was clarified.INTEROPERABILITY OF BITORIENTED LINK LAYER PROTOCOL Appendix 8 is updated to discuss interoperability between Version 1 and Version 3. containing timer values for the ARINC 429 high-speed Version 3 bus. was added. C.3. APPENDIX 8 . 3. ATTACHMENT 20 – INFORMATION FRAME DATA UNIT (FDU) STRUCTURE AND EXAMPLES New Attachment added. Table 11-10 was added defining the information frame SOF. the modified and added material) introduced by Supplement 17 are identified by c-17 change bars in the margins. the Section number and title of each affected Section. ATTACHMENT 19 – COMMAND FRAME DATA UNIT (FDU) STRUCTURE AND EXAMPLES New Attachment added.e. Table 11-11 was added defining the information frame EOF. Ethernet. Version 3 fills the role intended for Version 2 of the Williamsburg protocol by providing a high throughput avionics file data transfer interface. The protocol is designed to be consistent with the IEEE-802 Media Access Control (MAC) protocol definition. It discusses the relationship of this document to other AEEC documents and to other industry documents. ORGANIZATION OF THIS SUPPLEMENT Changes introduced by Supplement 17 were deemed sufficiently significant to issue an entirely new publication of Specification 429 Part 3. B. ATTACHMENT 11 . 1. PART 3 INTRODUCED BY THIS SUPPLEMENT This section presents a complete tabulation of the changes and additions to the Specification introduced by this Supplement. 1. the changes (. contains a list of descriptions of changes introduced into this Specification by this Supplement 17. Table 10-7.i. Attachment or Appendix is listed. In the text below. There is no standalone Supplement.

INC. 2001 Prepared by the Airlines Electronic Engineering Committee Adopted by the Airlines Electronic Engineering Committee: July 18. 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. 2551 Riva Road Annapolis.Copyright© 1999 by AERONAUTICAL RADIO. 2001 .

3. CVR Inmarsat.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. 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. Six new entries. B.7 were revised to Section 2. A Table was added to define the Variables of Low Speed Connectionless Bit-Oriented Protocol. TAWS. During the regeneration of Specification Description Language (SDL) diagrams in Appendix I.4.19. C. TAWS.5. PURPOSE OF THIS SUPPLEMENT This Supplement introduces the assignment of 3 new satellite links. HFDR Right. . ATTACHMENT 11A – DESTINATION CODES The assignment of ‘T” for the transponder was deleted. ICO.4 Bit Rate and Word Timing Provision was added to specify that the Williamsburg version 3 protocol may be operated at low speed. Later modified the value of the variables. 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. HFDR Right. In each case a brief description of the change or addition is included.Page 2 A. 3.SUPPLEMENT 18 TO ARINC SPECIFICATION 429 PART 3 . APPENDIX A – J These appendices were formerly identified as Appendix 1 – 10. ATTACHMENT 10 – VARIABLES TO BIT-ORIENTED PROTOCOL Added new Table 10-7 to support low speed operation of Williamsburg protocol at low speed. and Globalstar satellite link identifiers were added as destination codes. references to Section 1. 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. Typographical errors were corrected in the text.4. and CVR into the Destination Code table. APPENDIX K New Appendix added. 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. 3. The changes introduced by Supplement 18 have been identified using change bars and are labeled in the margin by a “c-18” indicator.