arinc 429-16

MARK 33 DIGITAL INFORMATIONTRANSFER SYSTEM (DITS)

PART 1FUNCTIONAL DESCRIPTION, ELECTRICALINTERFACE, LABEL ASSIGNMENTS AND

WORD FORMATS

ARINC SPECIFICATION 429PART1-16

PUBLISHED: SEPTEMBER 27, 2001

AN DOCUMENT

Prepared byAIRLINES ELECTRONIC ENGINEERING COMMITTEEPublished byAERONAUTICAL RADIO, INC.2551 RIVA ROAD, ANNAPOLIS, MARYLAND 21401

This document is based on material submitted by variousparticipants during the drafting process. Neither AEEC nor ARINChas made any determination whether these materials could besubject to valid claims of patent, copyright or other proprietaryrights by third parties, and no representation or warranty, express orimplied, is made in this regard. Any use of or reliance on thisdocument shall constitute an acceptance thereof “as is” and besubject to this disclaimer.

Copyright 2001 byAERONAUTICAL RADIO, INC.

2551 Riva RoadAnnapolis, Maryland 21401-7465 USA

ARINC SPECIFICATION 429PART1-16©

MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS)

PART 1

FUNCTIONAL DESCRIPTION, ELECTRICAL INTERFACE,

LABEL ASSIGNMENTS AND WORD FORMATS

Published: September 27, 2001

Prepared by the Airlines Electronic Engineering Committee

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

Summary of Document Supplements

Supplement Adoption Date Published

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

A description of the changes introduced by each supplement is included on goldenrod paper at the end of this document.

FOREWORD

Activities of AERONAUTICAL RADIO, INC. (ARINC)

and the

Purpose of ARINC Reports and Specifications

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

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

It is desirable to reference certain general ARINC Specifications or Report which areapplicable to more than one type of equipment. These general Specifications and Reports may beconsidered as supplementary to the Equipment Characteristics in which they are referenced. They areintended 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 necessaryinterchangeability in airline service. The release of a Specification or Equipment Characteristicsshould not be construed to obligate ARINC or any airline insofar as the purchase of any components orequipment 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 theconsidered opinion of the airline technical people, coordinated on an industry basis,concerning requisites of new equipment, and

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

ii

ARINC SPECIFICATION 429TABLE OF CONTENTS

ITEM SUBJECT PAGE

1.0 INTRODUCTION 11.1 Purpose of this Document 11.2 Organization of ARINC Specification 429 11.3 Relationship to ARINC Specification 419 11.4 “Mark 33 Digital Information Transfer System” Basic Philosophy 11.4.1 Numeric Data Transfer 11.4.2 ISO Alphabet No. 5 Data Transfer 11.4.3 Graphic Data Transfer 1

2.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS 22.1 Message Related Elements 22.1.1 Direction of Information Flow 22.1.2 Information Element 22.1.3 Information Identifier 22.1.4 Source/Destination Identifier 32.1.5 Sign/Status Matrix 32.1.5.1 BCD Numeric 42.1.5.2 BNR Numeric Data Words 42.1.5.3 Discrete Data Words 52.1.6 Data Standards 52.2 Electrically Related Elements 62.2.1 Transmission System Interconnect 62.2.2 Modulation 62.2.3 Voltage Levels 62.2.3.1 Transmitter Voltage Levels 62.2.3.2 Receiver Voltage Levels 72.2.4 Impedance Levels 72.2.4.1 Transmitter Output Impedance 72.2.4.2 Receiver Input Impedance 72.2.5 Fault Tolerance 72.2.5.1 Receiver External Fault Voltage Tolerance 72.2.5.2 Transmitter External Fault Voltage 82.2.5.3 Transmitter External Fault Load Tolerance 82.2.6 Fault Isolation 82.2.6.1 Receiver Fault Isolation 82.2.6.2 Transmitter Fault Isolation 82.3 Logic Related Elements 82.3.1 Digital Language 82.3.1.1 Numeric Data 82.3.1.2 Discretes 82.3.1.3 Maintenance Data (General Purpose) 82.3.1.4 AIM Data 82.3.1.5 File Data Transfer 82.3.1.5.1 Bit-Oriented Protocol Determination 92.3.2 Transmission Order 92.3.3 Data Bit Encoding Logic 92.3.4 Error Detection/Correction 92.4 Timing Related Elements 92.4.1 Bit Rate 92.4.1.1 High Speed Operation 92.4.1.2 Low Speed Operation 92.4.2 Information Rates 102.4.3 Clocking Method 102.4.4 Word Synchronization 102.4.5 Timing Tolerances 10

3.0 MARK 33 DITS APPLICATIONS NOTES 113.1 Radio Systems Management 113.1.1 Word Format and Digital Language 113.1.2 Update Rate 113.1.3 Sign/Status Matrix 113.1.4 Frequency Ranges and Switching Functions 113.1.4.1 ADF 113.1.4.2 DME 11

iii


ITEM SUBJECT PAGE

3.1.4.3 HF Communications 113.1.4.4 ILS 113.1.4.5 VOR/ILS 113.1.4.6 VHF Communications 113.1.4.7 ATC Transponder 113.2 AIM Information Transfer 12

ATTACHMENTS1-1 Label Codes 131-2 Equipment Codes 442 Data Standards 483 Voltage Levels 764 Input/Output Circuit Standards 775 International Standards Organization Code #5 786 General Word Formats and Encoding Examples 797 Data Bit Encoding Logic 1148 Output Signal Timing Tolerances 1159A General Aviation Labels and Data Standards 1169B General Aviation Word Examples 1189C General Aviation Equipment Identifiers 12510 Manufacturer Specific Status Word 12611 System Address Labels 127

APPENDICESA Laboratory Verification of ARINC 429 DITS Electrical Characteristics 129B An Approach to a Hybrid Broadcast-Command/Response Data Bus Architecture 162C Digital Systems Guidance (Part 1) 167D Digital Systems Guidance (Part 2) 174E Guidelines for Label Assignments 179X Chronology & Bibliography 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 standardsfor the transfer of digital data between avionics systemselements. Adherence to these standards is desired for allinter-systems communications in which the system linereplaceable units are defined as unit interchangeable in therelevant ARINC characteristics. Their use for intra-systemcommunications in systems in which the line replaceableunits are defined in the ARINC characteristics as systeminterchangeable is not essential, although it may beconvenient.

1.2 Organization of ARINC Specification 429

ARINC Specification 429 was originally published in asingle volume through version 14 (429-14). The size of thedocument and the need for improved organization dictatedthe division of the document into three parts. Those threeparts include:

Part 1 Functional Description, Electrical Interface, LabelAssignments and Word Formats

Part 2 Discrete Word Data Formats

Part 3 File Data Transfer Techniques

Part 1 provides the basic description of the functions andthe supporting physical and electrical interfaces for the datatransfer system. Data word formats, standard label andaddress assignments, and application examples are defined.Part 2 lists discrete word bit assignments in label order. Part3 describes protocols and message definitions for datatransferred in large blocks and/or file format. Forconvenience of the user, the section and attachmentnumbering has been retained for the material moved fromthe original Specification to Part 3.

Updates to each part of future releases of ARINC 429 willbe independent of the other parts to accommodate timelyrevisions as industry needs dictate. The dash numbers foreach Part will NOT be synchronized with the other Parts astime passes. Users of ARINC Specification 429 shouldensure that the latest version of each Part is used whendesigning or procuring equipment.

1.3 Relationship to ARINC Specification 419

ARINC Specification 419, “Digital Data SystemCompendium”, is a catalog of the elements of the severaldigital data transmission systems that have foundapplication during the “emergent” period of digital avionicstechnology. The maturing of this technology, now evidentin the scope of its planned use on aircraft of the 1980s andbeyond, has shown the need for a generally applicabledigital information transfer system having capabilities notprovided by any combination of the elements presentlydefined in Specification 419. In defining such a system, thisdocument draws on the experience gained in the preparationof Specification 419 but is otherwise separate and distinctfrom it. Addition of the element specifications of thesystem defined herein to the Specification 419 catalog is notanticipated.

1.4 “Mark 33 Digital Information Transfer System” - Basic Philosophy

This “Mark 33 Digital Information Transfer System(DITS)” specification describes a system in which anavionics system element having information to transmitdoes so from a designated output port over a single twistedand shielded pair of wires to all other system elementshaving need of that information. Bi-directional data flow ona given twisted and shielded pair of wires is not permitted.

1.4.1 Numeric Data Transfer

The Mark 33 DITS numeric data transmissioncharacteristics have been developed from those ofsuccessful predecessor air transport industry digitalinformation transfer systems. Data for transmission,encoded in either twos complement fractional binarynotation or binary coded decimal notation, is supplied fromsource systems at rates sufficiently high to ensure smallincremental value changes between updates. Transmissionis made “open loop”, i.e., sinks are not required to informsources that information has been received. A parity bit istransmitted as part of each data word to permit simple errorchecks to be performed by the sinks. These, together withdata reasonableness checks which may also be performedby the sinks, may be used to prevent the display or otherutilization of a erroneous or suspect word. The inherentlyhigh integrity of the twisted and shielded wire transmissionmedium ensures that such drop-outs are few. The low ratesof change of the data ensure that when one does occur, it isof no consequence.

1.4.2 ISO Alphabet No. 5 Data Transfer

In addition to the transfer of BNR and BCD numeric data asjust described, the Mark 33 DITS handles alpha andnumeric data encoded per ISO Alphabet No. 5. The same“broadcast” transmission philosophy is used, although the“housekeeping” aspects of system operation differ in orderto accommodate particular needs associated with this typeof data. These differences will be addressed individually inthis document as they arise.

1.4.3 Graphic Data Transfer

A third type of data which may eventually be handled by theMark 33 DITS is graphic data, i.e., the lines, circles,randomly positioned alpha/numeric text and other symbolsused on CRT map and similar displays. The techniqueemployed for this purpose can be basically similar to thatused for ISO Alphabet No. 5 alpha/numeric data transfer.However, because a need for graphic data handlingcapability has not yet emerged, the air transport industry hasdecided not to be specific concerning this technique for themoment. When the need for graphic data handling isestablished, appropriate specification material will bedeveloped.

c-15

c-1

c-1


2.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS

2.1 Message Related Elements

This section describes the digital data transfer systemelements considered to be principally related to the messageitself or the manner in which it is handled.

2.1.1 Direction of Information Flow

The information output of an avionics system elementshould be transmitted from a designated port (or ports) towhich the receiving ports of other system elements in needof that information are connected. In no case doesinformation flow into a port designated for transmission.

COMMENTARY

A separate data bus (twisted and shielded pair of wiresper Section 2.2.1) for each direction is used when datais required to flow both ways between two avionicssystems elements.

2.1.2 Information Element

The basic information element is a digital word containing32 bits. There are five application groups for such words,BNR data, BCD data, Discrete data, Maintenance data(general) and Acknowledgement, ISO Alphabet No. 5 andMaintenance (ISO Alphabet No. 5) data (AIM). Wordformats for these different applications are depicted inAttachment 6 while the relevant data handling rules are setforth in Section 2.3.1. When less than the full data field isneeded to accommodate the information conveyed in aword in the desired manner, the unused bit positions shouldbe filled with binary zeros or, in the case of BNR/BCDnumeric data, valid data bits. If valid data bits are used, theresolution possible for the information may exceed thatcalled for in this Specification. The Commentary followingSection 2.1.6 of this document refers.

COMMENTARY

To permit the use of identical error-checking hardwareelements in the handling of BNR and BCD numericdata words, the format for the Mark 33 DITS BCDword differs from that used formerly for this type ofdata. Bit No. 32 is assigned to parity, Bit Nos. 31 and30 to the sign/status matrix, Bit No. 29 is the mostsignificant bit of the data field, and the maximumdecimal value of the most significant character is 7.Previously, the BCD word contained no parity bit, thesign/status matrix occupied Bit Nos. 32 and 31, BitNo. 30 was the most significant data bit and themaximum decimal value of the most significantcharacter was 3. This format made the word 8-bit byteoriented with respect to the data. This characteristic isnot retained in the Mark 33 system.

Also, latitude and longitude can only be encoded in theMark 33 DITS word with the formerly specifiedresolution of 0.1 minute of arc if Bit Nos. 9 and 10 areused for data rather than the SDI function described inSection 2.1.4 of this document, and the word isstructured differently from the standard shown inAttachment 6. Restructuring the word involveslimiting the maximum value of the most significantcharacter to 1 and moving the remaining BCDcharacters towards the MSB by two bit positions. It is

possible, however, that future latitude and longitudedisplays will not be the simple, dedicated read-out typefor which BCD data is intended. More likely is the useof some form of multiple-message display, such as aCRT, which will be backed by its own data processorand prefer inputs of BNR data. If this proves to be thecase, these special provisions for BCD-encoding willnot be required.

2.1.3 Information Identifier

The type of information contained in a word is identified bya six-character label. The first three characters are octalcharacters coded in binary in the first eight bits of the word.The eight bits will:

a. identify the information contained within BNR andBCD numeric data words (e.g., DME distance, staticair temperature, etc.) and

b. identify the word application for Discrete, Maintenanceand AIM data.

The last three characters of the six-character label arehexadecimal characters used to provide for identification ofARINC 429 bus sources. Each triplet of hexadecimalcharacters identifies a “black box” with one or more DITSports. Each three character code (and black box) may haveup to 255 eight bit labels assigned to it. The code is usedadministratively to retain distinction between unlikeparameters having like labels assignments.

COMMENTARY

Some users have expressed a desire to have means foridentifying label sets and buses associated with aparticular equipment ID code. Octal label 377 hasbeen assigned for this purpose. (The code appears inthe 3 LSDs of the BCD Word format). Thetransmission of the equipment identifier word on a buswill permit receivers attached to the bus to recognizethe source of the DITS information. Since thetransmission of the equipment identifier word isoptional, receivers should not depend on that word forcorrect operation.

Label code assignments are set forth in Attachment 1 tothis document.

Special Note:

In some ARINC 429 DITS applications, a bus will bededicated to delivering a single information element from asource to one or more identical sink devices. In suchcircumstances, the sink device designer might be tempted toassume that decoding the word label is not necessary. Experience has shown, however, that system developmentsfrequently occur that result in the need for additionalinformation elements to appear on the bus. If a sink devicedesigned for service prior to such a development cannotdecode the original word label, it cannot differentiatebetween this word and the new data in the new situation. The message for sink designers should therefore be quiteclear - provide label decoding from the outset, no matterhow strong the temptation to omit it might be.

c-2

c-1

c-1

c-1

c-2

c-4

c-2

c-12

c-4

c-2

c-1



COMMENTARY

Adherence to the label code assignments ofAttachment 1 is essential in inter-systemcommunications and in intra-system communicationswhere the system elements are defined as “unitinterchangeable” per ARINC Report 403. Theassignment of label codes for all such communicationsmust be coordinated with the air transport industry ifchaos is to be avoided. A manufacturer who finds thatAttachment 1 does not specify the label he needs forsuch system application must not simply choose onefrom those unassigned and “drive on”. He shouldcontact AEEC Staff for assistance.

2.1.4 Source/Destination Identifier

Bit Nos. 9 and 10 of numeric data words should be reservedfor a data source/destination identification function. Theyare not available for this function in alpha/numeric (ISOAlphabet No. 5) data words (see Section 2.3.1.3 of thisdocument) or when the resolution needed for numeric(BNR/BCD) data necessitates their use of valid data. Thesource/destination identifier function may find applicationwhen specific words need to be directed to a specific systemof a multi-system installation or when the source system ofa multi-system installation needs to be recognizable fromthe word content. When it is used, a source equipmentshould encode its aircraft installation number in Bit Nos. 9and 10 as shown in the table below. A sink equipmentshould recognize words containing its own installationnumber 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 bitsby equipment functioning only as a source or only as asink is described above. Both the source and sink textsabove are applicable to equipment functioning as botha source and a sink. Such equipment should recognizethe SDI bits on the inputs and should also encode theSDI bits, as applicable, on the outputs. DME, VOR,ILS and other sensors, are examples of source and sinkequipment generally considered to be only sourceequipment. These are actually sinks for their owncontrol panels. Many other types of equipment are alsomisconstrued as source only or sink only. A simplerule of thumb is: if a unit has a 429 input port and a429 output port, it is a source and sink! With theincrease of equipment consolidation, e.g., centralizedcontrol panels, the correct use of the SDI bits cannot beoverstressed.

Bit No.

10 9Installation No.

0011

0101

See Note Below123

Note: In certain specialized applications of the SDIfunction the all-call capability may be forfeited so thatcode “00” is available as an “installation no. 4” identifier.

When the SDI function is not used, binary zeros or validdata should be transmitted in Bit Nos. 9 and 10.

COMMENTARY

This document does not address the practical questionof how the SDI bits will be set in those multi-installation systems in which the source/destinationfunction is desired. One way would be to use programpins on the individual installation black boxes whichwould be wired to set up the appropriate code. TheARINC Characteristics devoted to the individualsystems will define the method actually to be used.

2.1.5 Sign/Status Matrix

This section describes the coding of the Sign/Status Matrix(SSM) field. In all cases the SSM field uses Bits 30 and 31.For BNR data words, the SSM field also includes Bit 29.

The SSM field may be used to report hardware equipmentcondition (fault/normal), operational mode (functional test),or validity of data word content (verified/no computeddata).

The following definitions apply in this Specification:

Invalid Data - is defined as any data generated by a sourcesystem whose fundamental characteristic is the inability toconvey reliable information for the proper performance of auser system. There are two categories of invalid data,namely, “No Computed Data” and “Failure Warning”.

No Computed Data - is a particular case of data invaliditywhere the source system is unable to compute reliable datafor reasons other than system failure. This inability tocompute reliable data is caused exclusively by a definite setof events or conditions whose boundaries are uniquelydefined in the system characteristic.

Failure Warning - is a particular case of data invaliditywhere the system monitors have detected one or morefailures. These failures are uniquely characterized byboundaries 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 sourcesystem should annunciate its outputs to be invalid by settingthe sign/status matrix of the affected words to the “NoComputed Data” code, as defined in the subsections whichfollow. The system indicators may or may not be flagged,depending on system requirements.

While the unit is in the functional test mode, all output datawords generated within the unit (i.e., pass through words areexcluded) should be coded for “Functional Test”. Passthrough data words are those words received by the unit andretransmitted without alteration.

When the SSM code is used to transmit status and morethan one reportable condition exists, the condition with thehighest priority should be encoded in Bit Nos. 30 and 31.The order of condition priorities to be used is shown in thetable below.

c-1

c-8

c-1

c-12



2.1.5 Sign/Status Matrix (cont’d)

Failure WarningNo Computed DataFunctional TestNormal Operation

Priority 1Priority 2Priority 3Priority 4

Each data word type has its own unique utilization of theSSM field. These various formats are described in thefollowing subsections.

2.1.5.1 BCD Numeric

When a failure is detected within a system which wouldcause one or more of the words normally output by thatsystem to be unreliable, the system should stop transmittingthe affected word or words on the data bus.

Some avionic systems are capable of detecting a faultcondition which results in less than normal accuracy. Inthese systems, when a fault of this nature (for instance,partial sensor loss) which results in degraded accuracy isdetected, each unreliable BCD digit should be encoded“1111” when transmitted on the data bus. For equipmentshaving 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 ofthe inaccurate digit. Parameters for which such a degradedmode of operation is possible are identified in the Notecolumn of the tables in Attachment 2.

The sign (plus/minus, north/south, etc.) of BCD NumericData should be encoded in bit numbers 30 and 31 of theword as shown in the table below. Bit Nos. 30 and 31 ofBCD Numeric Data words should be “zero” where no signis needed.

The “No Computed Data” code should be annunciated inthe affected BCD Numeric Data word(s) when a sourcesystem is unable to compute reliable data for reasons otherthan system failure.

When the “Functional Test” code appears in Bits 30 and 31of an instruction input data word, it should be interpreted asa command to perform a functional test.

COMMENTARY

A typical instruction input to a radio, for example,would be a channel change command word. When thiscommand word is received with the “Functional Test”coding in the SSM field, the radio should exercise itsfunctional test.

When the “Functional Test” code appears as a systemoutput, it should be interpreted as advice that the data in theBCD Numeric Data word contents are the result of theexecution of a functional test. A functional test shouldproduce indications of 1/8 of positive full-scale valuesunless indicated otherwise in the associated ARINCEquipment Characteristic.

BCD NUMERIC SIGN/STATUS MATRIX

Bit No.31 30

Meaning

0011

0101

Plus, North, East, Right, To, AboveNo Computed DataFunctional TestMinus, South, West, Left, From, Below

2.1.5.2 BNR Numeric Data Words

The status of the transmitter hardware should be encoded inthe Status Matrix field (Bit Nos. 30 and 31) of BNRNumeric Data words as shown in the table below.

A source system should annunciate any detected failure thatcauses one or more of the words normally output by thatsystem to be unreliable by setting Bit Nos. 30 and 31 in theaffected word(s) to the “Failure Warning” code defined inthe table below. Words containing this code shouldcontinue to be supplied to the data bus during the failurecondition.

The “No Computed Data” code should be annunciated inthe affected BNR Numeric Data word(s) when a sourcesystem is unable to compute reliable data for reasons otherthan system failure.

When it appears as a system output, the “Functional Test”code should be interpreted as advice that the data in theword results from the execution of a functional test. Afunctional test should produce indications of 1/8 of positivefull-scale values unless indicated otherwise in an ARINCequipment characteristic.

If, during the execution of a functional test, a source systemdetects a failure which causes one or more of the wordsnormally output by that system to be unreliable, it shouldimmediately change the states of Bit Nos. 30 and 31 in theaffected words such that the “Functional Test” annunciationis replaced with “Failure Warning” annunciation.

BNR STATUX MATRIX

Bit No.31 30

Meaning

0011

0101

Failure WarningNo Computed DataFunctional TestNormal Operation

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

c-12 c-12



SIGN MATRIX

Bit No.29

Meaning

01

Plus, North, East, Right, To, AboveMinus, South, West, Left, From, Below

Some avionic systems are capable of detecting a faultcondition which results in less than normal accuracy. Inthese systems, when a fault of this nature (for instance,partial sensor loss) which results in degraded accuracy isdetected, the equipment should continue to report “Normal”for the sign status matrix while indicating the degradedperformance by coding bit 11 as follows:

ACCURACY STATUS

Bit No.11

Meaning

01

Nominal AccuracyDegraded Accuracy

This implies that degraded accuracy can be coded only inBNR words not exceeding 17 bits of data. Parameters forwhich such a degraded mode of operation is possible areidentified 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 thatcould cause one or more of the words normally output bythat system to be unreliable. Three methods are defined.The first method is to set Bit Nos. 30 and 31 in the affectedword(s) to the “Failure Warning” code defined in the tablebelow. Words containing the “Failure Warning” codeshould continue to be supplied to the data bus during thefailure condition. When using the second method, theequipment may stop transmitting the affected word or wordson the data bus. Designers should use this method when thedisplay or use of the discrete data by a system isundesirable. The third method applies to data words whichare defined such that they contain failure information withinthe data field. For these applications, refer to the associatedARINC equipment characteristic to determine proper SSMreporting. Designers should preclude mixing operationaland BITE data in the same word.

The “No Computed Data” code should be annunciated inthe affected Discrete Data word(s) when a source system isunable to compute reliable data for reasons other thansystem failure.

When the “Functional Test” code appears as a systemoutput, it should be interpreted as advice that the data in theDiscrete Data word contents are the result of the executionof a functional test.

DISCRETE DATA WORDS

Bit No.31 30

Meaning

0011

0101

Verified Data, Normal OperationNo Computed DataFunctional TestFailure Warning

2.1.6 Data Standards

The units, ranges, resolutions, refresh rates, number ofsignificant bits, pad bits, etc. for the items of information tobe transferred by the Mark 33 DITS are tabulated inAttachment 2 to this document.

COMMENTARY

Note that Section 2.3.1.1 of this document calls fornumeric data to be encoded in BCD and binary, thelatter using twos complement fractional notation. Inthis notation, the most significant bit of the data fieldrepresents one half of the maximum value chosen forthe parameter being defined. Successive bits representthe increments of a binary fraction series. Negativenumbers are encoded as the twos complements ofpositive value and the negative sign is annunciated inthe sign/status matrix.

In establishing a given parameter’s binary datastandards for inclusion in Attachment 2, the unitsmaximum value and resolution are first determined inthat order. The least significant bit of the word is thengiven a value equal to the resolution increment, and thenumber of significant bits is chosen such that themaximum value of the fractional binary series justexceeds the maximum value of the parameter, i.e.,equals the next whole binary number greater than themaximum parameter value less one least significant bitvalue. For example, if the Mark 33 DITS is required totransfer altitude in units of feet over a range of zero to100,000 feet with a resolution of one foot, the numberof significant bits is 17 and the maximum value of thefractional binary series is 131,071 (i.e., 131,072 - 1).

Note that because accuracy is a quality of themeasurement process and not the data transfer process,it plays no part in the selection of word characteristics.Obviously, the resolution provided in the DITS wordshould equal or exceed the accuracy in order not todegrade it.

For the binary representation of angular data, the Mark33 DITS employs “degrees divided by 180o” as theunit of data transfer and ±1 (semicircle) as the rangefor twos complement fractional notation encoding(ignoring, for the moment, the subtraction of the leastsignificant bit value). Thus the angular range 0through 359.XXX degrees is encoded as 0 through±179.XXX degrees, the value of the most significantbit is one half semicircle and there are nodiscontinuities in the code.

This may be illustrated as follows. Consider encodingthe angular range 0o to 360o in 1o increments. Per thegeneral encoding rules above, the positive semicirclewill cover the range 0o to 179o (one least significant bitless than full range). All the bits of the code will be“zeros” for 0o and “ones” for 179o, and the sign/statusmatrix will indicate the positive sign. The negativesemicircle will cover the range 180o to 359o. All thebits will be “zeros” for 180o. The codes for anglesbetween 181o to 359o will be determined by taking thetwos complements of the fractional binary series for

c-12

c-15

c-12

c-15

c-12

c-1

c-3



2.1.6 Data Standards (cont’d)

COMMENTARY (cont’d)

the result of subtracting each value from 360. Thus,the code for 181o is the twos complement of the codefor 179o. Throughout the negative semicircle, whichincludes 180o, the sign/status matrix contains thenegative sign.

For convenience, all binary word ranges inAttachment 2 are shown as whole binary numbersrather than such numbers less one least significantbit value. Also, the resolutions shown areapproximate only. Accurate resolutions can bedetermined, if required, by reference to the rangevalues and numbers of significant bits for the words ofinterest.

It should be noted that in all applications of the twoscomplement fractional notation, the maximum value ofthe word, once chosen, cannot be changed by the use ofmore bits in the data field. The number of bits in theword affects only the resolution of the data, not itsrange.

Binary Coded Decimal (BCD) data is encoded per thenumeric subset of the ISO Alphabet #5 code (seeAttachment 5 to this document) using Bit Nos. 1through 4 of the seven-bit-per-character code.Alpha/numeric data is encoded using all seven bits percharacter of the ISO Alphabet #5 code and istransmitted using the special word format described inSection 2.3.1.3 of this document.

2.2 Electrically Related Elements

This section describes the digital transfer system elementsconsidered to be principally related to the electrical aspectsof the signal circuit.

2.2.1 Transmission System Interconnect

A data source should be connected to the data sink(s) bymeans of a single twisted and shielded pair of wires. Theshields should be grounded at both ends to an aircraftground close to the rack connector and at all productionbreaks in the cable.

COMMENTARY

In practical wire line digital information transmissionsystems, cable characteristics and electrical mismatchescan produce distortion of the digital data pulses. Also,noise due to electrical interference perturbs digitalsignals.

The performance of a digital receiver depends upon thereceiver input signal characteristics (data withdistortion and noise) and the receiver design.

Prior to the selection of the voltage and impedanceparameters set forth in this section of this document, thepulse distortion likely to be encountered in systemsbuilt around them in existing size commercial aircraftwas evaluated and judged to be acceptable for a well-designed receiver. No restriction is placed by thisspecification, therefore, on the number or length ofstubs for installations on aircraft no larger than thoseexisting, e.g., B 747. See Appendix 1 to this documentfor a report of this investigation.

Tests have shown that some receivers continuedecoding data properly when one side of thetransmission line is open or shorted to ground. Whenthis condition exists noise immunity decreases andintermittent operation may occur. Users desireprotection against non-annunciated system operation inthis mode. This protection may consist of additionalcircuitry to detect and annunciate the fault, or toincrease the receiver threshold to above 5.5 volts,which is the maximum signal level under this one-wirefault condition.

Most ARINC Characteristics now contain textspecifying that DITS receivers should discontinueoperation when the voltage thresholds fall into theundefined regions between “Null” and “Hi” or “Null”and “Lo”. Manufacturers building DITS receivers areurged to incorporate this feature in their circuitrywhether it is to be used in ARINC 7XX-seriesequipment or Non-ARINC devices.

2.2.2 Modulation

RZ bipolar modulation should be used. This is tri-levelstate modulation consisting of “HI”, “NULL” and “LO”states.

2.2.3 Voltage Levels

2.2.3.1 Transmitter Voltage Levels

The differential output signal across the specified outputterminals (balanced to ground at the transmitter) should beas given in the following table when the transmitter is opencircuit:

HI (V) NULL (V) LO (V)Line A

toLine B

Line Ato

Ground

Line Bto

Ground

+10 +1.0

+5 +0.5

-5 +0.5

0 +0.5

0 +0.25

0 +0.25

-10 +1.0

-5 +0.5

+5 +0.5

c-3

c-5

c-5

c-4

c-4

c-5



2.2.3.2 Receiver Voltage Levels

The differential voltage presented at the receiver inputterminals will be dependent upon line length, stubconfiguration and the number of receivers connected. In theabsence of noise, the normal ranges of voltages presented tothe receiver terminals (A and B) would be:

“HI” +7.25V to +11V“NULL” +0.5V to -0.5V“LO” -7.25V to -11V

In practice, these nominal voltages will be perturbed bynoise and pulse distortion. Thus, receivers should associatethe following voltage ranges with the three states indicated:

“HI” +6.5V to 13V“NULL” +2.5V to -2.5V“LO” -6.5V to -13V

COMMENTARY

Receiver reaction is currently undefined herein forvoltages that fall in the range just above and below the“Null” range. Respective equipment characteristicsshould be referenced for desired receiver response inthis range. However, it is desirable that all DITSreceivers will discontinue operation when the voltagelevels fall into the undefined regions. Manufacturersare urged, as new equipment is developed, to “designin” the rejection capability.

The opinion is held by some people that conditions ontransmission lines will be encountered which willrequire receivers to operate with less than the abovedefined minimum difference of 4.0V between theNULL and HI and NULL and LO states. Receiverdesigners are encouraged to investigate thepossibilities and problems of working with a minimumdifference of 1 volt between these states and to reporttheir findings.

Receiver input common mode voltages (terminal A toground and terminal B to ground) are not specifiedbecause of the difficulties of defining ground with anysatisfactory degree of precision. Receivermanufacturers are encouraged to work with thedifferential input voltage (line A to line B) and not line-to-ground voltages.

2.2.4 Impedance Levels

2.2.4.1 Transmitter Output Impedance

The transmitter output impedance should be 75 ±5 ohms,divided equally between line A and line B to provide animpedance balanced output. This output impedance shouldbe present for the “HI”, “NULL” and “LO” transmitteroutput conditions and also during transitions between theselevels.

COMMENTARY

The output impedance of the transmitter is specified as75 ± 5 ohms to provide an approximate match to thecharacteristic impedance of the cable. The match canonly be approximate due to the wide range of

characteristic impedances which may be encountereddue to the variety of conductor wire gauges andinsulation properties. Measurements on a few samplesof wire showed a spread of characteristic impedance of63 to 71 ohms. An extrapolation over the wire gauges20 to 26 for wrapped and extruded insulation indicatean expected characteristic impedance spread of 60 to80 ohms approx. Twisted shielded wire specificationsdo not control the characteristic impedance of thecable, thus future developments in insulationtechniques may result in cables having characteristicimpedances outside the range estimated.

2.2.4.2 Receiver Input Impedance

The receiver should exhibit the following characteristics,measured at the receiver input terminals:

Differential Input Resistance RI = 12,000 ohms minimumDifferential Input Capacitance CI = 50pF maximumResistance to Ground RH and RG ≥ 12,000 ohmsCapacitance to Ground CH and CG ≤ 50pF.

The total receiver input resistance including the effects ofRI, RH and RG in parallel should be 8,000 ohms minimum(400 ohms minimum for twenty receiver loads).

No more than twenty receivers should be connected on toone digital data bus and each receiver should incorporateisolation provisions to ensure that the occurrence of anyreasonably probable failure does not cause loss of data tothe others.

See Attachment 4 to this document for a pictorialrepresentation of the input and output circuit standards.

COMMENTARY

The above characteristics apply to differentialamplifier receivers. Opto-isolator technology isprogressing and may soon find application in digitaldata receivers. Opto-isolator receivers impose slightlygreater loads on data buses than differential amplifierreceivers and the way in which they are characterized isdifferent. It is probable, however, that a future revisionof this Specification will include material specificallyrelated to their use.

2.2.5 Fault Tolerance

2.2.5.1 Receiver External Fault Voltage Tolerance

Receivers should withstand without sustaining damage thefollowing steady-state voltages being applied to theirterminals, superimposed upon a normally operating bus.Operation within specification limits is not required underthese conditions.

a. 30 Vac RMS applied across terminals A and B, or

b. ±29 Vdc applied between terminal A and ground, or

c. ±29 Vdc applied between terminal B and ground.

c-5

c-4

c-4

c-4

c-4

c-4

c-4



2.2.5.2 Transmitter External Fault Voltage

Transmitter failures caused by external fault voltages shouldnot cause other transmitters or other circuitry in the unit tofunction outside of their specification limits or to fail.

2.2.5.3 Transmitter External Fault Load Tolerance

Transmitters should indefinitely withstand withoutsustaining damage a short circuit applied:

a. across terminals A and B, or

b. from terminal A to ground, or

c. from terminal B to ground, or

d. b and c above, simultaneously.

2.2.6 Fault Isolation

2.2.6.1 Receiver Fault Isolation

Each receiver should incorporate isolation provisions toensure that the occurrence of any reasonably probableinternal LRU or bus receiver failure does not cause anyinput bus to operate outside of its specification limits (bothundervoltage or overvoltage).

2.2.6.2 Transmitter Fault Isolation

Each transmitter should incorporate isolation provisions toensure that it does not under any reasonably probable LRUfault condition provide an output voltage in excess of:

a. a voltage greater than 30 Vac RMS between terminal Aand B, or

b. greater than ±29 Vdc between A and ground, or

c. greater than ±29 Vdc between B and ground.

2.3 Logic Related Elements

This section describes the digital transfer system elementsconsidered to be principally related to the logic aspects ofthe signal circuit.

2.3.1 Digital Language

2.3.1.1 Numeric Data

The Mark 33 DITS should accommodate numeric dataencoded in two digital languages, (i) BNR expressed intwos complement fractional notation and (ii) BCD per thenumerical subset of ISO Alphabet No. 5 (see Attachment 5to this document). An information item encoded in bothlanguages will be assigned a unique address for each (seeSection 2.1.3 and Attachment 1). Word formats areillustrated in Attachment 6 to this document.

2.3.1.2 Discretes

In addition to handling numeric data as specified above, theMark 33 DITS should also be capable of accommodatingdiscrete items of information either in the unused (pad) bitsof data words or, when necessary, in dedicated words. Anydiscrete information contained in a numeric data word

assigned a label in Attachment 1 is specified in thedefinition for that word in Attachment 6.

The rule to be followed in the assignment soft bits todiscrete in numeric data words is to start with the leastsignificant bit of the word and to continue towards the mostsignificant bit available in the word. Attachment 6 showsits against the background of the generalized word structure.

There are two types of discrete words. These are generalpurpose discrete words, and dedicated discrete words.Seven labels (270 XXX-276 XXX) are assigned to thegeneral purpose words in Attachment 1. These wordsshould be used in ascending label order (starting with 270XXX) when the system receiving the data can identify itssource by reference to the port at which it arrives.

2.3.1.3 Maintenance Data (General Purpose)

The general purpose maintenance words are assigned labelsin sequential order as are the labels for the general purposediscrete words. The lowest octal value label assigned to themaintenance words should be used when only onemaintenance word is transmitted. When more than oneword is transmitted the lowest octal value label should beused first and the other labels used sequentially until themessage has been completed. The general purposemaintenance words may contain discrete, BCD or BNRnumeric data but should never contain ISO Alphabet No. 5messages. The general purpose maintenance words shouldbe formatted according to the layouts of the correspondingBCD/BNR/discrete data words shown in Attachment 2.

2.3.1.4 AIM Data

The information previously contained in this section is nolonger applicable to ARINC Specification 429. Forreference purposes, the section header is retained and theoriginal contents of this section are located in Part 3 of thisSpecification.

2.3.1.5 File Data Transfer

This section previously described a character-oriented filedata transfer protocol. This definition was used as guidancefor the character-oriented file transfer protocol descriptionsincorporated into many ARINC equipment characteristics. The original contents of this section are located in Part 3 ofthis Specification.

The protocol defined in Part 3 is preferred for newapplications. The purpose of this bit-oriented com-munications protocol is to provide for the transparenttransfer of data files using the ARINC 429 data bus.

COMMENTARY

The data transparent protocol described in Part 3 wasdeveloped in order to facilitate the communications ofthe ACARS Management Unit (MU) and the SatelliteData Unit (SDU). Its viability as a universal protocolwas recognized by the Systems Architecture andInterfaces (SAI) Subcommittee, which recommendedits inclusion herein as the standard means of file datatransfer.

The process for determining the protocol (character-oriented or bit-oriented) to be used in the interaction

c-4

c-4

c-4

c-2

c-2

c-4

c-12

c-13

c-14

c-2

c-2



between two units, where this information is not pre-determined is described in Section 2.5.19.

2.3.1.5.1 Bit-Oriented Protocol Determination

The ALO word should be sent by any system whichsupports the bit-oriented Link Layer protocol just after thesystem powers-up, or performs a re-initialization for anyreason. The ALO/ALR protocol process may also be usedwhen a bit-oriented Link Layer protocol system needs todetermine if any of its interfaces support the bit-orientedprotocol. All systems which support the Link Layer bit-oriented protocol must be able to respond to the initiation ofthis process. Attachment 11C shows the ALO and ALRword formats.

When a system with a bit-oriented Link Layer protocol hasthe need to make this determination, it should construct theALO word and transmit this word to the device in question. The system should then wait for a maximum period of timedefined by T12. If the device in question has not respondedwithin T12, the initiating system should initiate another ALOword and again delay up to T12. An initiating system willattempt a maximum of N6 ALO word operations beforedeclaring the device in question as “Not bit-oriented” or“Not able to respond”.

2.3.2 Transmission Order

The Least Significant Bit (LSB) and Least SignificantCharacter (LSC) of each word should be transmitted first. Itmay be noted that the least significant bit of the word is themost significant bit of the label and that the label istransmitted ahead of the data in each case. This “reversedlabel” characteristic is a legacy from past systems in whichthe octal coding of the label field was, apparently, of nosignificance.

2.3.3 Data Bit Encoding Logic

A “HI” state after the beginning of the bit interval returningto a “NULL” state before the end of the same bit intervalsignifies a logic “one”.

A “LO” state after the beginning of the bit interval returningto a “NULL” state before the end of the same bit intervalsignifies a logic “zero”. This is represented graphically inAttachment 7 to this document.

2.3.4 Error Detection/Correction

The last bit of each word should be encoded such that wordparity is rendered odd to allow error detection in receivers. Note that the parity calculation encompasses all 31 labeland information bits of the word.

COMMENTARY

Air transport industry experience with digitalinformation transfer systems pre-dating the Mark 33DITS has shown that the twisted shielded pair of wirescan be regarded as a high integrity link unlikely tointroduce bit errors into the data passing through it. Itis for this reason that no means for error correction arespecified in this document. The error detectioncapability specified above may be used as desired in

receiving terminals. BNR data, for example, may bechecked for parity by reference to the binary state ofBit No. 32 of each word. Also, the data may besubmitted to reasonableness checks. BCD may besubmitted to reasonableness checks. BCD dataintended for human consumption in the cockpit isnormally smoothed before transmission to ensuretolerable levels of display jitter. As this processeliminates any obviously wild data points, the need forfurther error detection is questionable. As pointed outin the Commentary following Section 2.1.2 of thisdocument, the parity bit was added to the BCD wordfor reasons related to BCD/BNR transmitter hardwarecommonality, not because a need for it existed for errordetection.

2.4 Timing Related Elements

This section describes the digital data transfer systemelements considered to be principally related to the timingaspects of the signal circuit.

2.4.1 Bit Rate

2.4.1.1 High Speed Operation

The bit rate for high speed operation of the system shouldbe 100 kilobits per second ±1%.

2.4.1.2 Low Speed Operation

The bit rate for low speed operation of the system should bewithin the range 12.0 to 14.5 kilobits per second. Theselected rate should be maintained within 1%.

NOTE:

High bit rate and low bit rate messages will not beintermixed on the same bus.

COMMENTARY

Although the bit rates specified above should be heldwithin the stated tolerances over the long term,individual bit lengths may fall outside the limitsexpected from these tolerances. Bit symmetry and jittershould be within the tolerances specified in Attachment8.

Also, notwithstanding the RFI performance of theARINC 429 DITS reported in Appendix 1 to thisdocument, system designers are advised to avoidselection of 13.6 kilobits per second for low speedoperations and precisely 100 kilobits per second forhigh speed operations to ensure that the system is notresponsible for interference to LORAN C systems withwhich the aircraft might be equipped.

c-5

c-5

c-13



2.4.2 Information Rates

The minimum and maximum transmit intervals for eachitem of information transferred by the Mark 33 DITS arespecified in the tables of Attachment 2. Words with likelabels but with different SDI codes should be treated asunique items of information. Each and every unique itemof information should be transmitted once during aninterval bounded in length by the minimum and maximumvalues specified in Attachment 2. Stated another way, aword having the same label and four different SDI codesshould appear on the bus four times (once for each SDIcode) during that time interval.

COMMENTARY

There are no values given for refresh rates in thisSpecification. However, it is desirable that data berefreshed at least once per transmission. Those dataactually requiring long processing times or a largenumber of samples are the only types not expected tobe refreshed with every transmission.

Discretes contained within data words should be transferredat the bit rate and repeated at the update rate of the primarydata. Words dedicated to discretes should be repeatedcontinuously at the rates defined in Attachment 2.

COMMENTARY

The time intervals between successive transmissions ofa given BCD word specified in table 1 of Attachment 2to this document are, in general, too short for the signalto be of use in driving a display device directly. If thesignal was so used the least significant character of thedisplay, would change too rapidly for humanperception. Considerations other than human factorsdemand the time intervals specified. Thus, displaydesigners should incorporate into their devices meansfor selecting those words to be used for updating thedisplay from the greater quantity delivered.

2.4.3 Clocking Method

Clocking is inherent in the data transmission. Theidentification of the bit interval is related to the initiation ofeither a “HI” or “LO” state from a previous “NULL” statein a bipolar RZ code.

2.4.4 Word Synchronization

The digital word should be synchronized by reference to agap of four bit times (minimum) between the periods ofword transmissions. The beginning of the first transmittedbit following this gap signifies the beginning of the newword.

2.4.5 Timing Tolerances

The waveform timing tolerances should be as shown inAttachment 8 to this document.

COMMENTARY

RF interference radiated by the Mark 33 DITS usingthe waveform characteristics specified in this sectionhas been shown not to exceed that permitted by Figure21-5 of RTCA Document DO-160, “EnvironmentalConditions and Test Procedures for AirborneElectronic/Electrical Equipment and Instruments”.Also, conducted RF interference is within the limitsspecified in Figure 21-2 of DO-160. Appendix 1 tothis document refers.

c-4

c-5


3.0 MARK 33 DITS APPLICATIONS NOTES

3.1 Radio Systems Management

One special application of the Mark 33 DITS is to radiosystems frequency selection and function switching. Thefollowing paragraphs set forth the rules which should befollowed in the application of the DITS to ensureinterchangeability of radios and control sources.

3.1.1 Word Format and Digital Language

The standard DITS 32-bit BCD word should be used, of whichBit Nos. 1 through 8 constitute the label, Bit Nos. 9 and 10 arereserved for a source/destination identifier code, bit nos. 11through 29 constitute the data, Bit Nos. 30 and 31 form thesign/status matrix and Bit No. 32 is the word parity bit. Thedata field should contain the frequency to which the radiodefined by the label field is to tune encoded in BCD characters,together with the discretes required for function switching forthat radio. Attachment 6 shows how the word should bestructured for each radio system requiring the DITSmanagement service.

3.1.2 Update Rate

The nominal update rate for all radio systems managementwords should be five times per second.


Since sign is not a characteristic of radio systems managementinformation, the normal states of the sign/status matrix bits willbe binary “zeros”. However, the radios should recognize thecodes for “functional test” and “no computed data”, (seeSection 2.1.5 of this document). They should interpret theformer as an instruction to perform a functional test orfunctional test sequence. They should regard the latter as aninstruction to remain tuned to the frequency contained in thelast valid word received until either another valid word isdecoded or their primary power is removed.

3.1.4 Frequency Ranges and Switching Functions

3.1.4.1 ADF

Frequency Range: 190kHz to 1750kHzFrequency Selection Increment: 0.5kHzCharacters encoded in DITS word: 1000kHz, 100kHz, 10kHz, 1kHzSwitching Functions: 0.5kHz on/off, BFO on/off,

ADF/ANT mode selection

3.1.4.2 DME

Frequency Range: 108.00MHz to 135.95MHz(VOR/ILS)

Frequency Selection Increment: 50kHz(VOR/ILS)

Characters encoded in DITS word: 10Mhz, 1Mhz, 0.1MHz0.05MHz (VOR/ILS only)(100MHz character is 1for VOR/ILS, 10MHz characteris limited to 7)

Switching Functions: VOR/ILS/MLSFrequency, DME modes,Directed Frequency Numbers,

Display Control

3.1.4.3 HF Communications

Frequency Range: 2.8MHz to 24MHzFrequency Selection Increment: 1kHz or .1kHzCharacters encoded in DITS words: 10MHz, 1MHz, 0.1MHz,

0.01MHz, 0.001MHz, 0.1kHz

Switching Functions: USB/LSB mode selectionSB/AM mode selection

Note: Two words may be transmitted for HF frequencyselection to facilitate frequency resolution of 0.1kHz.

3.1.4.4 ILS

Frequency Range: 108.00MHz to 111.95MHzFrequency Selection Increment: 50kHz Characters encoded in DITS words: 10MHz, 1MHz, 0.1MHz,

0.01MHz, (100MHz character isalways decimal 1)

Switching Functions: None

3.1.4.5 VOR/ILS

Frequency Range: 108.00 MHz to 117.95MHzFrequency Selection Increment: 50kHzCharacters encoded in DITS words: 10MHz, 1MHz, 0.1MHz, 0.01MHz,

(100MHz character is alwaysdecimal 1)

Switching Functions: ILS Mode

3.1.4.6 VHF Communications

Frequency Range: 118.000 MHz to 135.975MHzFrequency Selection Increment: 25kHzCharacters encoded in DITS words: 10MHz, 1MHz, 0.1MHz, 0.01MHz,

(100MHz character is alwaysdecimal 1)

Switching Functions: None

3.1.4.7 ATC Transponder

Note: The ATC Transponder operates on two frequencies(one receive and one transmit) which do not requireselection. Reply code selection, however, isrequired and it is this that the Mark 33 DITSaccommodates).

Reply Code Ranges: 0-7 in four independent groupsCode increments: 1 decimal digit per groupNo. of characters encoded in DITS words: ALL

Switching Functions: Ident. Pulse Select, AltitudeReporting On/Off, Altitude SourceSelect, X-pulse Select (reserved),VFR/IFR Select (reserved),IRS/FMC Input Select (reserved).


3.0 MARK 33 DITS APPLICATIONS NOTES

3.2 AIM Information Transfer

The information previously contained in this section is nolonger applicable to ARINC Specification 429. For referencepurposes, the section header is retained and the originalcontents of this section are located in Part 3.

ATTACHMENT 1-1LABEL CODES


1 2 3 4 5 6 7 8 BNR BCD DISC SAL

0 X X 0 0 0 0 0 0 0 0 Not Used

0 0 2 0 0 0 0 0 0 0 1 Distance to Go X 6-250 5 6 0 0 0 0 0 0 0 1 Distance to Go X0 6 0 0 0 0 0 0 0 0 1 Distance to Go X0 0 2 0 0 0 0 0 0 1 0 Time to Go X 6-250 5 6 0 0 0 0 0 0 1 0 Time to Go X0 6 0 0 0 0 0 0 0 1 0 Time to Go X1 1 5 0 0 0 0 0 0 1 0 Time to Station X0 0 2 0 0 0 0 0 0 1 1 Cross Track Distance X 6-250 0 1 0 0 0 0 0 1 0 0 Runway Distance to Go X0 D 0 0 0 0 0 0 1 0 1 Engine Discrete X0 D 0 0 0 0 0 0 1 1 0 Engine Discrete X0 0 0 0 0 0 1 1 1 Spare0 0 2 0 0 0 0 1 0 0 0 Present Position - Latitude X 6-25-10 0 4 0 0 0 0 1 0 0 0 Present Position - Latitude X0 3 8 0 0 0 0 1 0 0 0 Present Position - Latitude X0 0 2 0 0 0 0 1 0 0 1 Present Position - Longitude X 6-25-10 0 4 0 0 0 0 1 0 0 1 Present Position - Longitude X0 3 8 0 0 0 0 1 0 0 1 Present Position - Longitude X0 0 2 0 0 0 0 1 0 1 0 Ground Speed X 6-250 0 4 0 0 0 0 1 0 1 0 Ground Speed X0 0 5 0 0 0 0 1 0 1 0 Ground Speed X0 2 5 0 0 0 0 1 0 1 0 Ground Speed X0 3 8 0 0 0 0 1 0 1 0 Ground Speed X0 4 D 0 0 0 0 1 0 1 0 QTY-LD SEL (LB) X0 5 6 0 0 0 0 1 0 1 0 Ground Speed X0 6 0 0 0 0 0 1 0 1 0 Ground Speed X0 0 2 0 0 0 0 1 0 1 1 Track Angle - True X 6-250 0 4 0 0 0 0 1 0 1 1 Track Angle - True X0 3 8 0 0 0 0 1 0 1 1 Track Angle - True X0 4 D 0 0 0 0 1 0 1 1 QTY-FLT Deck (LB) X0 B 8 0 0 0 0 1 0 1 1 Control Panel Set X0 0 4 0 0 0 0 1 1 0 0 Magnetic Heading X0 0 5 0 0 0 0 1 1 0 0 Magnetic Heading X0 3 8 0 0 0 0 1 1 0 0 Magnetic Heading X0 0 2 0 0 0 0 1 1 0 1 Wind Speed X0 0 4 0 0 0 0 1 1 0 1 Wind Speed X0 0 5 0 0 0 0 1 1 0 1 Wind Speed X0 3 8 0 0 0 0 1 1 0 1 Wind Speed X0 0 4 0 0 0 0 1 1 1 0 Wind Direction - True X0 3 8 0 0 0 0 1 1 1 0 Wind Direction - True X0 B 8 0 0 0 0 1 1 1 0 TCAS Mode/Sens X0 1 0 0 0 0 0 1 1 1 1 Selected Runway - True X0 4 D 0 0 0 0 1 1 1 1 Total-FLT Deck (LB) X0 5 5 0 0 0 0 1 1 1 1 Selected Runway Heading X0 A 0 0 0 0 0 1 1 1 1 Selected Runway Heading X0 B 0 0 0 0 0 1 1 1 1 Selected Runway Heading X0 2 0 0 0 0 1 0 0 0 0 Selected Vertical Speed X 6-250 4 D 0 0 0 1 0 0 0 0 TNK-LD SEL (LB) X0 6 D 0 0 0 1 0 0 0 0 Landing Gear Position Infor & System Status X0 A 1 0 0 0 1 0 0 0 0 Selected Vertical Speed X0 0 2 0 0 0 1 0 0 0 1 Selected EPR X 6-250 0 2 0 0 0 1 0 0 0 1 Selected N1 X 6-250 2 0 0 0 0 1 0 0 0 1 Selected EPR X0 2 0 0 0 0 1 0 0 0 1 Selected N1 X0 6 D 0 0 0 1 0 0 0 1 Landing Gear Position Infor & System Status X0 A 1 0 0 0 1 0 0 0 1 Selected EPR X0 A 1 0 0 0 1 0 0 0 1 Selected N1 X0 2 0 0 0 0 1 0 0 1 0 Selected Mach X 6-250 4 D 0 0 0 1 0 0 1 0 QTY-LD SEL (KG) X0 6 D 0 0 0 1 0 0 1 0 Landing Gear Position Infor & System Status X0 A 1 0 0 0 1 0 0 1 0 Selected Mach X

0 0 7

0 1 2

0 0 30 0 40 0 50 0 6

0 1 5

0 1 6

0 1 7

0 2 0

0 1 0

0 1 1

0 1 3

0 1 4

Code No. (Octal)

Eqpt. ID (Hex)

0 0 2

0 0 1

0 0 0

Data Notes & Cross Ref. to Tables in

Att. 6Parameter

Transmission Order Bit Position

0 2 1

0 2 2




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 2 0 0 0 0 1 0 0 1 1 Selected Heading X 6-250 4 D 0 0 0 1 0 0 1 1 QTY-LD SEL (KG) X0 6 D 0 0 0 1 0 0 1 1 Landing Gear Position Infor & System Status X0 A 1 0 0 0 1 0 0 1 1 Selected Heading X0 1 1 0 0 0 1 0 1 0 0 Selected Course #1 X 6-250 2 0 0 0 0 1 0 1 0 0 Selected Course #1 X0 6 D 0 0 0 1 0 1 0 0 Landing Gear Position Infor & System Status X0 A 1 0 0 0 1 0 1 0 0 Selected Course #1 X0 B 1 0 0 0 1 0 1 0 0 Selected Course #1 X0 2 0 0 0 0 1 0 1 0 1 Selected Altitude X 6-250 4 D 0 0 0 1 0 1 0 1 Load SEL Control X0 A 1 0 0 0 1 0 1 0 1 Selected Altitude X0 0 3 0 0 0 1 0 1 1 0 Selected Airspeed X 6-250 2 0 0 0 0 1 0 1 1 0 Selected Airspeed X0 A 1 0 0 0 1 0 1 1 0 Selected Airspeed X0 0 2 0 0 0 1 0 1 1 1 TACAN Selected Course X0 1 1 0 0 0 1 0 1 1 1 Selected Course # 2 X0 2 0 0 0 0 1 0 1 1 1 Selected Course # 2 X0 4 D 0 0 0 1 0 1 1 1 Total-FLT Deck (KG) X0 5 6 0 0 0 1 0 1 1 1 TACAN Selected Course X0 6 0 0 0 0 1 0 1 1 1 TACAN Selected Course X0 A 1 0 0 0 1 0 1 1 1 Selected Course # 2 X0 B 1 0 0 0 1 0 1 1 1 Selected Course # 2 X0 2 0 0 0 0 1 1 0 0 0 VHF COM Frequency X 6-450 2 4 0 0 0 1 1 0 0 0 VHF COM Frequency X0 4 D 0 0 0 1 1 0 0 0 TNK-LD SEL (KG) X0 B 6 0 0 0 1 1 0 0 0 VHF COM Frequency X 6-450 2 0 0 0 0 1 1 0 0 1 Beacon Transponder Code X 6-460 B 8 0 0 0 1 1 0 0 1 Beacon Transponder Code X0 1 2 0 0 0 1 1 0 1 0 ADF Frequency X 6-400 2 0 0 0 0 1 1 0 1 0 ADF Frequency X 6-400 B 2 0 0 0 1 1 0 1 0 ADF Frequency X 6-400 0 2 0 0 0 1 1 0 1 1 ILS Frequency X 6-440 1 0 0 0 0 1 1 0 1 1 ILS Frequency X0 2 0 0 0 0 1 1 0 1 1 ILS Frequency X0 5 5 0 0 0 1 1 0 1 1 Landing System Mode/Frequency X Note 20 5 6 0 0 0 1 1 0 1 1 ILS Frequency X0 6 0 0 0 0 1 1 0 1 1 ILS Frequency X0 B 0 0 0 0 1 1 0 1 1 ILS Frequency X0 0 2 0 0 0 1 1 1 0 0 VOR/ILS Frequency X0 0 6 0 0 0 1 1 1 0 0 Baro Correction (mb) #3 X0 1 1 0 0 0 1 1 1 0 0 VOR/ILS Frequency X0 2 0 0 0 0 1 1 1 0 0 VOR/ILS Frequency X0 2 5 0 0 0 1 1 1 0 0 VOR/ILS Frequency X0 5 6 0 0 0 1 1 1 0 0 VOR/ILS Frequency X0 6 0 0 0 0 1 1 1 0 0 VOR/ILS Frequency #1 X0 B 0 0 0 0 1 1 1 0 0 VOR/ILS Frequency X0 0 2 0 0 0 1 1 1 0 1 DME Frequency X 6-410 0 6 0 0 0 1 1 1 0 1 Baro Correction (ins of Hg) #3 X0 0 9 0 0 0 1 1 1 0 1 DME Frequency X 6-410 2 0 0 0 0 1 1 1 0 1 DME Frequency X0 2 5 0 0 0 1 1 1 0 1 DME Frequency X0 5 5 0 0 0 1 1 1 0 1 Paired DME Frequency X0 5 6 0 0 0 1 1 1 0 1 DME Frequency X0 6 0 0 0 0 1 1 1 0 1 DME Frequency #1 X0 A 9 0 0 0 1 1 1 0 1 DME Frequency X0 0 2 0 0 0 1 1 1 1 0 MLS Frequency X0 2 0 0 0 0 1 1 1 1 0 MLS Frequency X0 5 5 0 0 0 1 1 1 1 0 MLS Channel Selection X0 5 6 0 0 0 1 1 1 1 0 MLS Frequency Channel X0 6 0 0 0 0 1 1 1 1 0 MLS Frequency Channel X0 C 7 0 0 0 1 1 1 1 0 MLS Frequency X0 0 2 0 0 0 1 1 1 1 1 HF COM Frequency X 6-42-10 B 9 0 0 0 1 1 1 1 1 HF COM Frequency X0 0 0 1 0 0 0 0 0 Spare0 4 0

0 3 5

0 3 6

0 3 7

0 2 7

0 3 0

0 3 1

0 3 2

0 3 3

0 3 4

0 2 5

0 2 6

0 2 4

0 2 3




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 0 2 0 0 1 0 0 0 0 1 Set Latitude X0 0 4 0 0 1 0 0 0 0 1 Set Latitude X0 2 0 0 0 1 0 0 0 0 1 Set Latitude X0 5 6 0 0 1 0 0 0 0 1 Set Latitude X0 6 0 0 0 1 0 0 0 0 1 Set Latitude X0 A 4 0 0 1 0 0 0 0 1 Set Latitude X0 0 2 0 0 1 0 0 0 1 0 Set Longitude X0 0 4 0 0 1 0 0 0 1 0 Set Longitude X0 2 0 0 0 1 0 0 0 1 0 Set Longitude X0 5 6 0 0 1 0 0 0 1 0 Set Longitude X0 6 0 0 0 1 0 0 0 1 0 Set Longitude X0 A 4 0 0 1 0 0 0 1 0 Set Longitude X0 0 2 0 0 1 0 0 0 1 1 Set Magnetic Heading X0 0 4 0 0 1 0 0 0 1 1 Set Magnetic Heading X0 2 0 0 0 1 0 0 0 1 1 Set Magnetic Heading X0 5 6 0 0 1 0 0 0 1 1 Set Magnetic Heading X0 6 0 0 0 1 0 0 0 1 1 Set Magnetic Heading X0 A 4 0 0 1 0 0 0 1 1 Set Magnetic Heading X0 0 4 0 0 1 0 0 1 0 0 True Heading X0 3 8 0 0 1 0 0 1 0 0 True Heading X0 0 3 0 0 1 0 0 1 0 1 Minimum Airspeed X0 3 3 0 0 1 0 0 1 1 0 Engine Serial No. (LSDs) X 6-151 0 A 0 0 1 0 0 1 1 0 Engine Serial No. (LSDs) X 6-151 0 B 0 0 1 0 0 1 1 0 Engine Serial No. (LSDs) X 6-150 2 0 0 0 1 0 0 1 1 1 VHF COM Frequency X0 2 4 0 0 1 0 0 1 1 1 VHF COM Frequency X0 3 3 0 0 1 0 0 1 1 1 Engine Serial No. (MSDs) X 6-160 B 6 0 0 1 0 0 1 1 1 VHF COM Frequency X1 0 A 0 0 1 0 0 1 1 1 Engine Serial No. (MSDs) X 6-161 0 B 0 0 1 0 0 1 1 1 Engine Serial No. (MSDs) X 6-160 0 0 1 0 1 0 0 0 Spare0 0 0 1 0 1 0 0 1 Spare

0 0 4 0 0 1 0 1 0 1 0 Body Pitch Acceleration X

0 3 7 0 0 1 0 1 0 1 0 Longitude Zero Fuel CG X0 3 8 0 0 1 0 1 0 1 0 Body Pitch Acceleration X

0 0 4 0 0 1 0 1 0 1 1 Body Roll Acceleration X

0 0 5 0 0 1 0 1 0 1 1 Track Angle - Magnetic X0 3 8 0 0 1 0 1 0 1 1 Body Roll Acceleration X

0 0 4 0 0 1 0 1 1 0 0 Body Yaw Acceleration X

0 3 7 0 0 1 0 1 1 0 0 Zero Fuel Weight (KG) X0 3 8 0 0 1 0 1 1 0 0 Body Yaw Acceleration X0 0 0 1 0 1 1 0 1 Spare0 0 2 0 0 1 0 1 1 1 0 Estimated Time of Arrival X0 0 5 0 0 1 0 1 1 1 0 Wind Direction - Magnetic X0 3 7 0 0 1 0 1 1 1 0 Gross Weight (KG) X0 5 6 0 0 1 0 1 1 1 0 ETA (Active Waypoint) X0 6 0 0 0 1 0 1 1 1 0 ETA (Active Waypoint) X0 0 0 1 0 1 1 1 1 Spare0 2 5 0 0 1 1 0 0 0 0 S/G Hardware Part No X 6-360 3 7 0 0 1 1 0 0 0 0 Tire Loading (Left Body Main) X0 3 C 0 0 1 1 0 0 0 0 Tire Pressure (Left Inner) X0 0 2 0 0 1 1 0 0 0 1 ACMS Information X 6-290 0 B 0 0 1 1 0 0 0 1 Pseudo Range X0 2 5 0 0 1 1 0 0 0 1 S/G Hardware Part No X 6-370 3 7 0 0 1 1 0 0 0 1 Tire Loading (Right Body Main) X0 3 C 0 0 1 1 0 0 0 1 Tire Pressure (Left Outer) X0 5 6 0 0 1 1 0 0 0 1 ACMS Information X0 6 0 0 0 1 1 0 0 0 1 ACMS Information X

0 6 0

0 5 00 5 1

0 6 1

0 5 5

0 5 7

0 5 3

0 5 2

0 5 4

0 5 6

0 4 4

0 4 5

0 4 6

0 4 7

0 4 1

0 4 2

0 4 3




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 0 2 0 0 1 1 0 0 1 0 ACMS Information X 6-290 0 B 0 0 1 1 0 0 1 0 Pseudo Range Fine X0 3 7 0 0 1 1 0 0 1 0 Tire Loading (Left Wing Main) X0 3 C 0 0 1 1 0 0 1 0 Tire Pressure (Right Inner) X0 5 6 0 0 1 1 0 0 1 0 ACMS Information X0 6 0 0 0 1 1 0 0 1 0 ACMS Information X0 0 2 0 0 1 1 0 0 1 1 ACMS Information X 6-290 0 B 0 0 1 1 0 0 1 1 Range Rate X0 3 7 0 0 1 1 0 0 1 1 Tire Loading (Right Wing Main) X0 3 C 0 0 1 1 0 0 1 1 Tire Pressure (Right Outer) X0 5 6 0 0 1 1 0 0 1 1 ACMS Information X0 6 0 0 0 1 1 0 0 1 1 ACMS Information X

0 0 B 0 0 1 1 0 1 0 0 Delta Range X

0 3 7 0 0 1 1 0 1 0 0 Tire Loading (Nose) X0 3 C 0 0 1 1 0 1 0 0 Tire Pressure (Nose) X0 0 3 0 0 1 1 0 1 0 1 Gross Weight X0 0 B 0 0 1 1 0 1 0 1 SV Position X X0 3 7 0 0 1 1 0 1 0 1 Gross Weight X0 0 2 0 0 1 1 0 1 1 0 Longitudinal Center of Gravity X0 0 B 0 0 1 1 0 1 1 0 SV Position X Fine X0 3 7 0 0 1 1 0 1 1 0 Longitudinal Center of Gravity X0 3 7 0 0 1 1 0 1 1 1 Lateral Center of Gravity X0 0 2 0 0 1 1 1 0 0 0 Reference Airspeed (Vref) X0 0 B 0 0 1 1 1 0 0 0 SV Position Y X0 2 9 0 0 1 1 1 0 0 0 AC Frequency (Engine) X0 3 7 0 0 1 1 1 0 0 0 Hard landing Magnitude #1 X0 5 6 0 0 1 1 1 0 0 0 Reference Airspeed (Vref) X0 6 0 0 0 1 1 1 0 0 0 Reference Airspeed (Vref) X0 C C 0 0 1 1 1 0 0 0 Brakes - Metered Hydraulic Pressure L (Normal) X0 0 2 0 0 1 1 1 0 0 1 Take-Off Climb Airspeed (V2) X0 0 B 0 0 1 1 1 0 0 1 SV Position Y Fine X0 2 9 0 0 1 1 1 0 0 1 AC Frequency (Alt. Sources) X0 3 3 0 0 1 1 1 0 0 1 VBV X0 3 7 0 0 1 1 1 0 0 1 Hard Landing Magnitude #2 X0 C C 0 0 1 1 1 0 0 1 Brakes - Metered Hydraulic Pressure L (Alt) X0 0 2 0 0 1 1 1 0 1 0 VR (Rotation Speed) X0 0 B 0 0 1 1 1 0 1 0 SV Position Z X0 1 C 0 0 1 1 1 0 1 0 Stator Vane Angle X0 2 9 0 0 1 1 1 0 1 0 AC Voltage (Engine) X0 2 F 0 0 1 1 1 0 1 0 Stator Vane Angle X0 3 3 0 0 1 1 1 0 1 0 Stator Vane Angle X0 C C 0 0 1 1 1 0 1 0 Brakes - Metered Hydraulic Pressure R (Normal) X0 0 2 0 0 1 1 1 0 1 1 V1 (Critical Engine Failure Speed) X0 0 B 0 0 1 1 1 0 1 1 SV Position Z Fine X0 1 C 0 0 1 1 1 0 1 1 Oil Quantity X0 2 9 0 0 1 1 1 0 1 1 Oil Quantity X0 A 2 0 0 1 1 1 0 1 1 V2 (Critical Engine Failure Speed) X0 C C 0 0 1 1 1 0 1 1 Brakes - Metered Hydraulic Pressure R (Alt.) X0 D 0 0 0 1 1 1 0 1 1 Engine Oil Quantity X0 0 2 0 0 1 1 1 1 0 0 Zero Fuel Weight X0 0 B 0 0 1 1 1 1 0 0 UTC Measure Time X0 2 C 0 0 1 1 1 1 0 0 Zero Fuel Weight X0 3 3 0 0 1 1 1 1 0 0 LP Compressor Bleed Position (3.0) X0 3 7 0 0 1 1 1 1 0 0 Zero Fuel Weight (lb) X0 5 6 0 0 1 1 1 1 0 0 Zero Fuel Weight X0 6 0 0 0 1 1 1 1 0 0 Zero Fuel Weight X1 1 4 0 0 1 1 1 1 0 0 Zero Fuel Weight X

0 6 6

0 7 4

0 7 3

0 6 4

0 6 3

0 6 5

0 6 7

0 7 0

0 7 1

0 7 2

0 6 2




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 0 2 0 0 1 1 1 1 0 1 Gross Weight X0 0 3 0 0 1 1 1 1 0 1 Gross Weight X0 0 8 0 0 1 1 1 1 0 1 Maximum Hazard Alert Level Output X0 0 B 0 0 1 1 1 1 0 1 Geodetic Altitude X0 2 9 0 0 1 1 1 1 0 1 AC Voltage (Alt. Sources) X0 2 C 0 0 1 1 1 1 0 1 Gross Weight X0 3 7 0 0 1 1 1 1 0 1 Gross Weight X0 3 E 0 0 1 1 1 1 0 1 Gross Weight X1 1 4 0 0 1 1 1 1 0 1 Aircraft Gross Weight X

0 0 8 0 0 1 1 1 1 1 0 Hazard Azimuth Output X

0 0 B 0 0 1 1 1 1 1 0 GNSS Altitude (MSL) X0 2 9 0 0 1 1 1 1 1 0 AC Voltage (Bus Bar) X0 3 7 0 0 1 1 1 1 1 0 Longitudinal Center of Gravity X0 3 E 0 0 1 1 1 1 1 0 Longitudinal Center of Gravity X1 1 4 0 0 1 1 1 1 1 0 Aircraft Longitudinal Center of Gravity X0 0 2 0 0 1 1 1 1 1 1 Target Airspeed X0 0 8 0 0 1 1 1 1 1 1 Hazard Azimuth Output X0 0 B 0 0 1 1 1 1 1 1 GPS Hor/Vert Deviation X0 2 9 0 0 1 1 1 1 1 1 AC Load (Engine) X0 3 7 0 0 1 1 1 1 1 1 Lateral Center of Gravity X0 5 6 0 0 1 1 1 1 1 1 Target Airspeed X0 6 0 0 0 1 1 1 1 1 1 Target Airspeed X1 1 4 0 0 1 1 1 1 1 1 Zero Fuel Center of Gravity X0 0 1 0 1 0 0 0 0 0 0 Selected Course #1 X 6-270 0 2 0 1 0 0 0 0 0 0 Selected Course #1 X0 1 1 0 1 0 0 0 0 0 0 Selected Course #1 X0 2 0 0 1 0 0 0 0 0 0 Selected Course #1 X0 2 9 0 1 0 0 0 0 0 0 AC Load (Alt. Source) X0 3 7 0 1 0 0 0 0 0 0 Gross Weight (Kilogram) X0 5 6 0 1 0 0 0 0 0 0 Selected Course #1 X0 6 0 0 1 0 0 0 0 0 0 Selected Course #1 X0 A 1 0 1 0 0 0 0 0 0 Selected Course #1 X0 B 1 0 1 0 0 0 0 0 0 Selected Course #1 X0 B B 0 1 0 0 0 0 0 0 Outbound Flaps - PDU X0 0 2 0 1 0 0 0 0 0 1 Selected Heading X 6-270 0 B 0 1 0 0 0 0 0 1 HDOP X0 2 0 0 1 0 0 0 0 0 1 Selected Heading X0 2 5 0 1 0 0 0 0 0 1 Selected Heading X0 2 9 0 1 0 0 0 0 0 1 DC Current (TRU) X0 A 1 0 1 0 0 0 0 0 1 Selected Heading X0 B B 0 1 0 0 0 0 0 1 Inboard Flaps - PDU X1 1 4 0 1 0 0 0 0 0 1 C/G Target X0 0 2 0 1 0 0 0 0 1 0 Selected Altitude X 6-270 0 B 0 1 0 0 0 0 1 0 VDOP X0 2 0 0 1 0 0 0 0 1 0 Selected Altitude X0 2 9 0 1 0 0 0 0 1 0 DC Current (Battery) X0 5 6 0 1 0 0 0 0 1 0 Selected Altitude X0 6 0 0 1 0 0 0 0 1 0 Selected Altitude X0 A 1 0 1 0 0 0 0 1 0 Selected Altitude X0 0 1 0 1 0 0 0 0 1 1 Selected Airspeed X 6-270 0 2 0 1 0 0 0 0 1 1 Selected Airspeed X0 0 3 0 1 0 0 0 0 1 1 Selected Airspeed X0 0 B 0 1 0 0 0 0 1 1 GNSS Track Angle X0 1 B 0 1 0 0 0 0 1 1 Left/PDU Flap X0 2 0 0 1 0 0 0 0 1 1 Selected Airspeed X0 2 9 0 1 0 0 0 0 1 1 DC Voltage (TRU) X0 5 6 0 1 0 0 0 0 1 1 Selected Airspeed X0 6 0 0 1 0 0 0 0 1 1 Selected Airspeed X0 A 1 0 1 0 0 0 0 1 1 Selected Airspeed X0 B B 0 1 0 0 0 0 1 1 Left Outboard Flap Position X

1 0 2

1 0 3

1 0 0

1 0 1

0 7 6

0 7 7

0 7 5




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


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

1 0 4

1 0 5

1 0 6

1 0 7

1 1 0

1 1 1

1 1 2

1 1 3

1 1 4




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 0 2 0 1 0 0 1 1 0 1 Waypoint Bearing X0 2 9 0 1 0 0 1 1 0 1 Brake Temperature (Left Outer L/G) X0 2 F 0 1 0 0 1 1 0 1 Fuel Temperature X0 3 F 0 1 0 0 1 1 0 1 Fuel Temperature X0 5 6 0 1 0 0 1 1 0 1 Waypoint Bearing X0 6 0 0 1 0 0 1 1 0 1 Waypoint Bearing X0 B C 0 1 0 0 1 1 0 1 Fuel Temperature X0 C C 0 1 0 0 1 1 0 1 Wheel Torque Output X 6-260 0 2 0 1 0 0 1 1 1 0 Cross Track Distance X 6-270 0 B 0 1 0 0 1 1 1 0 Horizontal GLS Deviation Rectilinear X0 2 9 0 1 0 0 1 1 1 0 Brake Temperature (Right Inner L/G) X0 5 5 0 1 0 0 1 1 1 0 Horizontal GLS Deviation Rectilinear X0 5 6 0 1 0 0 1 1 1 0 Cross Track Distance X0 6 0 0 1 0 0 1 1 1 0 Cross Track Distance X0 C C 0 1 0 0 1 1 1 0 Wheel Torque Output X 6-260 0 2 0 1 0 0 1 1 1 1 Vertical Deviation X 6-270 0 B 0 1 0 0 1 1 1 1 Vertical GLS Deviation Rectilinear X0 2 9 0 1 0 0 1 1 1 1 Brake Temperature (Right Inner L/G) X0 5 5 0 1 0 0 1 1 1 1 Vertical GLS Deviation Rectilinear X0 5 6 0 1 0 0 1 1 1 1 Vertical Deviation X0 6 0 0 1 0 0 1 1 1 1 Vertical Deviation X0 C C 0 1 0 0 1 1 1 1 Wheel Torque Output X 6-260 0 2 0 1 0 1 0 0 0 0 Range to Altitude X0 0 B 0 1 0 1 0 0 0 0 GNSS Latitude Fine X0 2 9 0 1 0 1 0 0 0 0 Pack Bypass Turbine Position X0 5 6 0 1 0 1 0 0 0 0 Range to Altitude X0 6 0 0 1 0 1 0 0 0 0 Range to Altitude X0 0 2 0 1 0 1 0 0 0 1 Horizontal Command Signal X0 0 B 0 1 0 1 0 0 0 1 GNSS Longitude Fine X0 2 5 0 1 0 1 0 0 0 1 Pitch Limit X0 2 9 0 1 0 1 0 0 0 1 Pack Outlet Temperature X0 5 6 0 1 0 1 0 0 0 1 Horizontal Command Signal X0 6 0 0 1 0 1 0 0 0 1 Horizontal Command Signal X0 0 2 0 1 0 1 0 0 1 0 Vertical Command Signal X0 2 9 0 1 0 1 0 0 1 0 Pack Turbine Inlet Temperature X0 5 6 0 1 0 1 0 0 1 0 Vertical Command Signal X0 6 0 0 1 0 1 0 0 1 0 Vertical Command Signal X0 0 2 0 1 0 1 0 0 1 1 Throttle Command X0 0 B 0 1 0 1 0 1 0 0 Digital Time Mark X0 0 2 0 1 0 1 0 1 0 1 Universal Time Coordinated (UTC) X 6-250 0 B 0 1 0 1 0 1 0 1 Universal Time Coordinated (UTC) X

0 3 1 0 1 0 1 0 1 0 1 Universal Time Coordinated (UTC) X 6-25

0 5 6 0 1 0 1 0 1 0 1 Universal Time Coordinated (UTC) X0 6 0 0 1 0 1 0 1 0 1 Universal Time Coordinated (UTC) X0 0 2 0 1 0 1 0 1 1 0 Vertical Deviation (wide) X0 2 6 0 1 0 1 0 1 1 0 FWC Word X0 2 9 0 1 0 1 0 1 1 0 Pack Flow X0 5 6 0 1 0 1 0 1 1 0 Vertical Deviation (Wide) X0 6 0 0 1 0 1 0 1 1 0 Vertical Deviation (Wide) X0 0 2 0 1 0 1 0 1 1 1 Selected Landing Altitude X0 1 B 0 1 0 1 0 1 1 1 Slat Angle X 6-110 3 3 0 1 0 1 0 1 1 1 P14 X1 0 A 0 1 0 1 0 1 1 1 Fan Discharge Static Pressure X1 0 B 0 1 0 1 0 1 1 1 Fan Discharge Static Pressure X0 0 B 0 1 0 1 1 0 0 0 Aut Horiz Integ Limit X0 1 A 0 1 0 1 1 0 0 0 Fan Inlet Total Temperature X

0 1 C 0 1 0 1 1 0 0 0 Fan Inlet Total Temperature X

0 2 F 0 1 0 1 1 0 0 0 Fan Inlet Total Temperature X0 3 5 0 1 0 1 1 0 0 0 Intruder Range X 6-210 3 F 0 1 0 1 1 0 0 0 Fan Inlet Total Temperature X1 0 A 0 1 0 1 1 0 0 0 Selected Total Air Temperature X1 0 B 0 1 0 1 1 0 0 0 Selected Total Air Temperature X1 3 A 0 1 0 1 1 0 0 0 Inlet Temperature X

1 1 5

1 1 6

1 1 7

1 2 0

1 2 3

1 2 1

1 2 2

1 2 4

1 3 0

1 2 7

1 2 5

1 2 6




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 1 A 0 1 0 1 1 0 0 1 Fan Inlet Total Pressure X0 1 C 0 1 0 1 1 0 0 1 Fan Inlet Total Pressure X0 2 D 0 1 0 1 1 0 0 1 Fan Inlet Total Pressure X0 2 F 0 1 0 1 1 0 0 1 Fan Inlet Total Pressure X0 3 3 0 1 0 1 1 0 0 1 Fan Inlet Total Pressure X0 3 5 0 1 0 1 1 0 0 1 Intruder Altitude X 6-221 3 A 0 1 0 1 1 0 0 1 Inlet Pressure X0 1 A 0 1 0 1 1 0 1 0 Exhaust Gas Total Pressure X0 1 C 0 1 0 1 1 0 1 0 Exhaust Gas Total Pressure X0 3 3 0 1 0 1 1 0 1 0 Exhaust Gas Total Pressure X0 3 5 0 1 0 1 1 0 1 0 Intruder Bearing X 6-230 0 B 0 1 0 1 1 0 1 1 Aut Horiz Integ Limit X0 1 A 0 1 0 1 1 0 1 1 Thrust Lever Angle X

0 2 F 0 1 0 1 1 0 1 1 Thrust Lever Angle X

0 3 F 0 1 0 1 1 0 1 1 Thrust Lever Angle X1 0 A 0 1 0 1 1 0 1 1 Selected Throttle Lever Angle X1 0 B 0 1 0 1 1 0 1 1 Selected Throttle Lever Angle X0 1 C 0 1 0 1 1 1 0 0 Power Lever Angle X1 0 A 0 1 0 1 1 1 0 0 Throttle Lever Angle X1 0 B 0 1 0 1 1 1 0 0 Throttle Lever Angle X1 3 A 0 1 0 1 1 1 0 0 Throttle Lever Angle X0 1 C 0 1 0 1 1 1 0 1 Engine Vibration #1 X0 2 9 0 1 0 1 1 1 0 1 Engine Fan Vibration X0 5 A 0 1 0 1 1 1 0 1 ACT 1 Fuel Quantity Display X0 0 B 0 1 0 1 1 1 1 0 Vertical Figure of Merit X0 1 C 0 1 0 1 1 1 1 0 Engine Vibration #2 X

0 2 9 0 1 0 1 1 1 1 0 Engine Turbine Vibration X

0 5 A 0 1 0 1 1 1 1 0 ACT 2 Fuel Quantity Display X0 1 B 0 1 0 1 1 1 1 1 Flap Angle X 6-110 2 A 0 1 0 1 1 1 1 1 Flap Angle X 6-110 2 F 0 1 0 1 1 1 1 1 Thrust Reverser Position Feedback X0 3 F 0 1 0 1 1 1 1 1 Thrust Reverser Position Feedback X0 5 A 0 1 0 1 1 1 1 1 Center+ACT1+ACT2 FQ Display X1 0 A 0 1 0 1 1 1 1 1 Selected Thrust Reverser Position X1 0 B 0 1 0 1 1 1 1 1 Selected Thrust Reverser Position X1 4 0 0 1 0 1 1 1 1 1 Flap Angle X 6-110 0 1 0 1 1 0 0 0 0 0 Flight Director - Roll X 6-270 0 B 0 1 1 0 0 0 0 0 UTC Fine X0 2 5 0 1 1 0 0 0 0 0 Flight Director - Roll X0 2 9 0 1 1 0 0 0 0 0 Precooler Output Temperature X0 5 A 0 1 1 0 0 0 0 0 Actual Fuel Quantity Display X1 1 4 0 1 1 0 0 0 0 0 Pump Contactor States X0 0 1 0 1 1 0 0 0 0 1 Flight Director - Pitch X 6-270 0 B 0 1 1 0 0 0 0 1 UTC Fine Fractions X0 2 5 0 1 1 0 0 0 0 1 Flight Director - Pitch X0 2 9 0 1 1 0 0 0 0 1 Precooler Input Temperature X0 5 A 0 1 1 0 0 0 0 1 Preselected Fuel Quantity Display X1 1 4 0 1 1 0 0 0 0 1 Pump Contactor and Pushbutton States X0 0 2 0 1 1 0 0 0 1 0 Flight Director - Fast/Slow X 6-270 0 3 0 1 1 0 0 0 1 0 Flight Director - Fast/Slow X0 2 5 0 1 1 0 0 0 1 0 Flight Director - Fast/Slow X0 5 A 0 1 1 0 0 0 1 0 Left Wing Fuel Quantity Display X1 1 4 0 1 1 0 0 0 1 0 Pump Push Button and LP Switch State X0 0 1 0 1 1 0 0 0 1 1 Flight Director - Yaw X0 4 1 0 1 1 0 0 0 1 1 HPA Command Word X0 5 A 0 1 1 0 0 0 1 1 Center Wing Fuel Quantity Display X1 1 4 0 1 1 0 0 0 1 1 Pump LP Switch State and FCMC Commands X2 4 1 0 1 1 0 0 0 1 1 HPA Response Word X0 2 B 0 1 1 0 0 1 0 0 Altitude Error X0 4 1 0 1 1 0 0 1 0 0 ACU/BSU Contorl Word X0 5 A 0 1 1 0 0 1 0 0 Right Wing Fuel Quantity Display X1 1 4 0 1 1 0 0 1 0 0 Valve Feedback X3 4 1 0 1 1 0 0 1 0 0 ACU/BSU Contorl Word X

1 3 2

1 3 4

1 3 3

1 3 1

1 4 1

1 3 5

1 4 2

1 4 0

1 3 7

1 3 6

1 4 3

1 4 4




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 0 2 0 1 1 0 0 1 0 1 TACAN Control X 6-300 2 5 0 1 1 0 0 1 0 1 Discrete Status 2 EFIS X0 2 9 0 1 1 0 0 1 0 1 Discrete Status 2 EFIS X0 A 1 0 1 1 0 0 1 0 1 AFS DFDR Discretes #1 X1 1 4 0 1 1 0 0 1 0 1 Valve Feedback X0 2 5 0 1 1 0 0 1 1 0 Discrete Status 3 EFIS X0 2 9 0 1 1 0 0 1 1 0 Discrete Data #9 X0 A 1 0 1 1 0 0 1 1 0 AFS DFDR Discretes #2 X1 1 2 0 1 1 0 0 1 1 0 TACAN Control X 6-471 1 4 0 1 1 0 0 1 1 0 Valve Feedback X0 2 5 0 1 1 0 0 1 1 1 Discrete Status 4 EFIS X0 2 9 0 1 1 0 0 1 1 1 Discrete Data #10 X0 A 1 0 1 1 0 0 1 1 1 AFS DFDR Discretes #3 X1 1 4 0 1 1 0 0 1 1 1 Valve Feedback XX X X 0 1 1 0 0 1 1 1 TACAN Control Word X 6-48/Note 10 0 2 0 1 1 0 1 0 0 0 Universal Time Constant (UTC) X 6-12/6-270 0 B 0 1 1 0 1 0 0 0 Universal Time Constant (UTC) X0 2 9 0 1 1 0 1 0 0 0 Cabin Altitude Rate X0 3 1 0 1 1 0 1 0 0 0 Universal Time Constant (UTC) X 6-12/6-270 5 6 0 1 1 0 1 0 0 0 Universal Coordinated Time X0 6 0 0 1 1 0 1 0 0 0 Universal Coordinated Time X1 1 4 0 1 1 0 1 0 0 0 FCMC Valve Commands X0 0 2 0 1 1 0 1 0 0 1 Localizer Bearing (True) X0 2 7 0 1 1 0 1 0 0 1 MLS Azimuth Deviation X0 2 9 0 1 1 0 1 0 0 1 Cabin Altitude X0 5 5 0 1 1 0 1 0 0 1 MLS Azimuth Deviation X0 5 6 0 1 1 0 1 0 0 1 Localizer Bearing (True) X0 5 A 0 1 1 0 1 0 0 1 LB/KG Control Word X0 6 0 0 1 1 0 1 0 0 1 Localizer Bearing (True) X1 1 4 0 1 1 0 1 0 0 1 FCMC Valve Commands X0 2 7 0 1 1 0 1 0 1 0 MLS Elevation Deviation X0 2 9 0 1 1 0 1 0 1 0 Cabin Pressure X0 4 1 0 1 1 0 1 0 1 0 Open Loop Steering X0 5 5 0 1 1 0 1 0 1 0 MLS GP Deviation X

1 1 4 0 1 1 0 1 0 1 0Overhead Panel Switch/Pushbutton & Refuel Panel Battery Power Supply Switch States

X

0 1 1 0 1 0 1 0 777 Cabin Interphone System - System Address Label X See Attachment 110 0 2 0 1 1 0 1 0 1 1 Maximum Altitude X0 2 7 0 1 1 0 1 0 1 1 Flare X0 2 9 0 1 1 0 1 0 1 1 Pressurization Valve Position (Gr. #1) X0 4 1 0 1 1 0 1 0 1 1 Closed Loop Steering X0 5 5 0 1 1 0 1 0 1 1 MLS Selected Azimuth X1 1 4 0 1 1 0 1 0 1 1 Level States X0 0 2 0 1 1 0 1 1 0 0 Runway Heading (True) X0 2 7 0 1 1 0 1 1 0 0 MLS Auxilliary Data X0 2 9 0 1 1 0 1 1 0 0 Pressurization Valve Position (Gr. #2) X0 5 5 0 1 1 0 1 1 0 0 MLS Max Selectable GP X0 5 6 0 1 1 0 1 1 0 0 Runway Heading (True) X0 6 0 0 1 1 0 1 1 0 0 Runway Heading (True) X1 1 4 0 1 1 0 1 1 0 0 Level States and Low Warning and Transfer Indications X0 1 C 0 1 1 0 1 1 0 1 Maintenance Data #6 X0 2 5 0 1 1 0 1 1 0 1 Discrete Status 5 EFIS X0 2 7 0 1 1 0 1 1 0 1 MLS Selected GP Angle X0 2 9 0 1 1 0 1 1 0 1 Discrete #1 X0 3 3 0 1 1 0 1 1 0 1 Maintenance Data #6 X0 5 5 0 1 1 0 1 1 0 1 MLS Selected Glide Path X0 B B 0 1 1 0 1 1 0 1 Maintenance Data #6 X1 0 A 0 1 1 0 1 1 0 1 Maintenance Data #6 X1 0 B 0 1 1 0 1 1 0 1 Maintenance Data #6 X1 1 4 0 1 1 0 1 1 0 1 XFR Pump Faults & Wing Imbalance Warning X

1 4 6

1 4 5

1 5 1

1 4 7

1 5 0

1 5 5

1 5 2

1 5 4

1 5 3




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 1 C 0 1 1 0 1 1 1 0 Maintnance Data #7 X0 2 7 0 1 1 0 1 1 1 0 MLS Dataword 1 X0 2 9 0 1 1 0 1 1 1 0 Discrete #12 X0 3 3 0 1 1 0 1 1 1 0 Maintenance Data #7 X0 4 D 0 1 1 0 1 1 1 0 L Tank Faults X0 5 5 0 1 1 0 1 1 1 0 MLS Basic Data Wd 1 X0 B B 0 1 1 0 1 1 1 0 Maintenance Data #7 X1 0 A 0 1 1 0 1 1 1 0 Maintenance Data #7 X1 0 B 0 1 1 0 1 1 1 0 Maintenance Data #7 X1 1 4 0 1 1 0 1 1 1 0 Refuel Panel Switch States X

0 1 1 0 1 1 1 1 System Address Label for CVR X See Attachment 110 1 C 0 1 1 0 1 1 1 1 Maintenance Data #8 X0 2 7 0 1 1 0 1 1 1 1 MLS Dataword 2 X0 3 3 0 1 1 0 1 1 1 1 Maintenance Data #8 X0 4 D 0 1 1 0 1 1 1 1 R Tank Faults X0 5 5 0 1 1 0 1 1 1 1 MLS Basic Data Wd 2 X0 B B 0 1 1 0 1 1 1 1 Maintenance Data #8 X1 0 A 0 1 1 0 1 1 1 1 Maintenance Data #8 X1 0 B 0 1 1 0 1 1 1 1 Maintenance Data #8 X1 1 4 0 1 1 0 1 1 1 1 Trim Tank Probe Capacitance X0 1 C 0 1 1 1 0 0 0 0 Maintenance Data #9 X0 2 5 0 1 1 1 0 0 0 0 Discrete Status 6 EFIS X0 2 7 0 1 1 1 0 0 0 0 MLS Dataword 3 X0 3 3 0 1 1 1 0 0 0 0 Maintenance Data #9 X0 4 D 0 1 1 1 0 0 0 0 C Tank Faults X0 5 5 0 1 1 1 0 0 0 0 MLS Basic Data Wd 3 X0 B B 0 1 1 1 0 0 0 0 Maintenance Data #9 X1 0 A 0 1 1 1 0 0 0 0 Maintenance Data #9 X1 0 B 0 1 1 1 0 0 0 0 Maintenance Data #9 X1 1 4 0 1 1 1 0 0 0 0 Valve Feedback X0 1 C 0 1 1 1 0 0 0 1 Maintenance Data #10 X0 2 5 0 1 1 1 0 0 0 1 Discrete Status 7 EFIS X0 2 7 0 1 1 1 0 0 0 1 MLS Dataword 4 X0 3 3 0 1 1 1 0 0 0 1 Maintenance Data #10 X0 4 D 0 1 1 1 0 0 0 1 A Tank Faults X0 5 5 0 1 1 1 0 0 0 1 MLS Basic Data Wd 4 X1 0 A 0 1 1 1 0 0 0 1 Maintenance Data #10 X1 0 B 0 1 1 1 0 0 0 1 Maintenance Data #10 X1 1 4 0 1 1 1 0 0 0 1 Indicated Pump Status X0 1 2 0 1 1 1 0 0 1 0 ADF Bearing X0 2 5 0 1 1 1 0 0 1 0 ADF Bearing Left/Right X0 2 7 0 1 1 1 0 0 1 0 MLS Dataword 5 X0 2 9 0 1 1 1 0 0 1 0 Crew Oxygen Pressure X0 5 5 0 1 1 1 0 0 1 0 MLS Basic Data Wd 5 X0 D E 0 1 1 1 0 0 1 0 Stick Shaker Margin Proportional Signal X1 1 4 0 1 1 1 0 0 1 0 Indicated Pump Status X1 4 0 0 1 1 1 0 0 1 0 Density Altitude X0 2 7 0 1 1 1 0 0 1 1 MLS Dataword 6 X0 3 7 0 1 1 1 0 0 1 1 Zero Fuel Weight (lb) X0 5 5 0 1 1 1 0 0 1 1 MLS Basic Data Wd 6 X1 1 4 0 1 1 1 0 0 1 1 Indicated Pump Status X

0 1 1 1 0 0 1 1 747 DFDR & A330/340 SSFDR - System Address Label X See Attachment 110 0 2 0 1 1 1 0 1 0 0 Minimum Descent Altitude (MDA) X0 0 3 0 1 1 1 0 1 0 0 Target Height X0 0 7 0 1 1 1 0 1 0 0 Radio Height X 6-13/6-270 2 5 0 1 1 1 0 1 0 0 Radio Height X 6-13/6-270 2 7 0 1 1 1 0 1 0 0 MLS Dataword 7 X0 3 B 0 1 1 1 0 1 0 0 Radio Height X0 5 5 0 1 1 1 0 1 0 0 MLS ABS GP Angle X1 1 4 0 1 1 1 0 1 0 0 Indicated Pump Status X

1 5 6

1 6 1

1 5 7

1 6 3

1 6 2

1 6 0

1 6 4




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 0 7 0 1 1 1 0 1 0 1 Radio Height X 6-250 0 B 0 1 1 1 0 1 0 1 Vertical Velocity X0 2 7 0 1 1 1 0 1 0 1 MLS Dataword 8 X0 5 5 0 1 1 1 0 1 0 1 MLS ABS Azimuth Angle X1 1 4 0 1 1 1 0 1 0 1 Indicated Valve Status X0 0 7 0 1 1 1 0 1 1 0 RALT Check Point Dev. X0 0 B 0 1 1 1 0 1 1 0 North/South Velocity X1 1 4 0 1 1 1 0 1 1 0 Indicated Valve Status X0 0 2 0 1 1 1 0 1 1 1 EPU Estimate Position Uncertainty/ (ANP) Actual Navi. Perf. X1 1 4 0 1 1 1 0 1 1 1 Indicated Valve Status X0 2 5 0 1 1 1 1 0 0 0 Decision Height Selected (EFI) X 6-250 C 5 0 1 1 1 1 0 0 0 Decision Height Selected (EFI) X 6-251 1 4 0 1 1 1 1 0 0 0 Wing Imbalance and FQI Failure Warning X

0 1 1 1 1 0 0 0 DFDAU - System Address Label X See Attachment 110 0 2 0 1 1 1 1 0 0 1 RNP Required Navigation Performance X0 5 6 0 1 1 1 1 0 0 1 Current RNP X0 6 0 0 1 1 1 1 0 0 1 Current RNP XX X X 0 1 1 1 1 0 0 1 Manufacturer Specific Status Word X See Attachment 10X X X 0 1 1 1 1 0 1 0 Subsystem Identifier 6-34/Note 10 1 0 0 1 1 1 1 0 1 1 Localizer Deviation X 6-6/6-270 2 5 0 1 1 1 1 0 1 1 Localizer Deviation X 6-6/6-270 2 9 0 1 1 1 1 0 1 1 Hydraulic Quantity X0 3 B 0 1 1 1 1 0 1 1 Localizer Deviation X0 5 5 0 1 1 1 1 0 1 1 Localizer Deviation X0 B D 0 1 1 1 1 0 1 1 Hydraulic Quantity X0 D 0 0 1 1 1 1 0 1 1 Hydraulic Oil X

0 1 1 1 1 0 1 1 SDU #2 - System Address Label X See Attachment 110 0 3 0 1 1 1 1 1 0 0 Delayed Flap Approach Speed (DFA) X0 0 B 0 1 1 1 1 1 0 0 East/West Velocity X0 1 0 0 1 1 1 1 1 0 0 Glideslope Deviation X 6-6/6-270 2 9 0 1 1 1 1 1 0 0 Hydraulic Pressure X0 3 B 0 1 1 1 1 1 0 0 Glideslope Deviation X 6-6/6-270 5 5 0 1 1 1 1 1 0 0 Glideslope Deviation X0 D 0 0 1 1 1 1 1 0 0 Hydraulic Oil Pressure X

0 1 1 1 1 1 0 0 RFU - System Address Label X See Attachment 110 0 3 0 1 1 1 1 1 0 1 Economical Speed X0 2 9 0 1 1 1 1 1 0 1 EGT (APU) X0 3 3 0 1 1 1 1 1 0 1 Hydraulic Pump Case Drain Temperature X

0 1 1 1 1 1 0 1 HGA/HPA Top/Port - System Address Label X See Attachment 110 0 3 0 1 1 1 1 1 1 0 Economical Mach X0 2 9 0 1 1 1 1 1 1 0 RPM (APU) X0 3 8 0 1 1 1 1 1 1 0 Left Static Pressure Uncorrected, mb X0 5 A 0 1 1 1 1 1 1 0 Fuel Temperature - Set to Zero X0 A D 0 1 1 1 1 1 1 0 Static Pressure Left, Uncorrected, mb X1 1 4 0 1 1 1 1 1 1 0 Left Outer Tank Fuel Temp & Advisory Warning X

0 1 1 1 1 1 1 0 HGA/HPA Starboard - System Address Label X See Attachment 110 0 3 0 1 1 1 1 1 1 1 Economical Flight Level X0 2 9 0 1 1 1 1 1 1 1 Oil Quantity (APU) X0 3 8 0 1 1 1 1 1 1 1 Right Static Pressure Uncorrected, mb X0 5 5 0 1 1 1 1 1 1 1 Distance To Runway Threshold X0 5 A 0 1 1 1 1 1 1 1 Fuel Temperature Left Wing Tank X0 A D 0 1 1 1 1 1 1 1 Static Pressure Right, Uncorrected, mb X1 1 4 0 1 1 1 1 1 1 1 Inner Tank 1 Fuel Temp & Advisory Warning X

0 1 1 1 1 1 1 1 LGA/HPA - System Address Label X See Attachment 110 0 2 1 0 0 0 0 0 0 0 Drift Angle X0 0 4 1 0 0 0 0 0 0 0 Drift Angle X0 5 6 1 0 0 0 0 0 0 0 Drift Angle X0 6 0 1 0 0 0 0 0 0 0 Drift Angle X1 1 4 1 0 0 0 0 0 0 0 Inner Tank 2 Fuel Temp & Advisory Warning X

1 6 5

1 6 6

1 6 7

1 7 0

1 7 2

1 7 3

1 7 1

1 7 4

1 7 5

1 7 6

1 7 7

2 0 0




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 0 9 1 0 0 0 0 0 0 1 DME Distance X 6-1-10 5 A 1 0 0 0 0 0 0 1 Fuel Temperature Right Wing Tank X1 1 2 1 0 0 0 0 0 0 1 TACAN Distance X1 1 4 1 0 0 0 0 0 0 1 Inner Tank 3 Fuel Temp & Advisory Warning X1 1 5 1 0 0 0 0 0 0 1 DME X 6-251 4 0 1 0 0 0 0 0 0 1 Mach Maximum Operation (Mmo) X1 4 2 1 0 0 0 0 0 0 1 Projected Future Latitude X

1 0 0 0 0 0 0 1 GPS/GNSS Sensor - System Address Label X See Attachment 110 0 2 1 0 0 0 0 0 1 0 Energy Management (clean) X0 0 9 1 0 0 0 0 0 1 0 DME Distance X 6-7/6-270 2 9 1 0 0 0 0 0 1 0 Cabin Compartment Temperature (Group #1) X0 5 A 1 0 0 0 0 0 1 0 Fuel Temperature - Set to Zero X1 1 4 1 0 0 0 0 0 1 0 Inner Tank 4 Fuel Temp & Advisory Warning X1 4 0 1 0 0 0 0 0 1 0 Mach Rate X1 4 2 1 0 0 0 0 0 1 0 Projected Future Latitude Fine X0 0 2 1 0 0 0 0 0 1 1 Energy Management Speed Brakes X0 0 6 1 0 0 0 0 0 1 1 Altitude (1013.25mB) X0 1 8 1 0 0 0 0 0 1 1 Altitude X 6-24/6-270 2 9 1 0 0 0 0 0 1 1 Cabin Compartment Temperature (Group #2) X0 3 5 1 0 0 0 0 0 1 1 Own A/C Altitude X0 3 8 1 0 0 0 0 0 1 1 Altitude (1013.25mB) X0 5 A 1 0 0 0 0 0 1 1 Fuel Tank #6 Temperature X1 0 A 1 0 0 0 0 0 1 1 Ambient Static Pressure X1 0 B 1 0 0 0 0 0 1 1 Ambient Static Pressure X1 1 4 1 0 0 0 0 0 1 1 Trim Tank Fuel Temp & Advisory Warning X1 4 0 1 0 0 0 0 0 1 1 Altitude X0 0 2 1 0 0 0 0 1 0 0 Utitlity Airspeed X0 0 6 1 0 0 0 0 1 0 0 Baro Corrected Altitude #1 X0 2 9 1 0 0 0 0 1 0 0 Cabin Duct Temperature (Group #1) X0 3 8 1 0 0 0 0 1 0 0 Baro Corrected Altitude #1 X0 5 6 1 0 0 0 0 1 0 0 Baro Altitude X0 5 A 1 0 0 0 0 1 0 0 Fuel Tank #7 Temperature X0 6 0 1 0 0 0 0 1 0 0 Baro Altitude X1 1 4 1 0 0 0 0 1 0 0 Right Outer Tank Fuel Temp & Advisory Warning X1 4 0 1 0 0 0 0 1 0 0 Baro Corrected Altitude X0 0 2 1 0 0 0 0 1 0 1 HF COM Frequency (New Format) X 6-430 0 6 1 0 0 0 0 1 0 1 Mach X 6-270 1 A 1 0 0 0 0 1 0 1 Mach X 6-270 2 9 1 0 0 0 0 1 0 1 Cabin Duct Temperature (Group #2) X0 3 8 1 0 0 0 0 1 0 1 Mach X0 5 A 1 0 0 0 0 1 0 1 Fuel Tank #8 Temperature X0 B 9 1 0 0 0 0 1 0 1 HF COM Frequency (New Format) X1 0 A 1 0 0 0 0 1 0 1 Mach Number X1 0 B 1 0 0 0 0 1 0 1 Mach Number X1 4 0 1 0 0 0 0 1 0 1 Mach X0 0 6 1 0 0 0 0 1 1 0 Computed Airspeed X 6-270 1 8 1 0 0 0 0 1 1 0 Altitude (Variable Resolution) X 6-200 2 9 1 0 0 0 0 1 1 0 Cabin Temp. Reg. Valve Position (Group #1) X0 3 8 1 0 0 0 0 1 1 0 Computed Airspeed X 6-270 5 6 1 0 0 0 0 1 1 0 Computed Airspeed X0 6 0 1 0 0 0 0 1 1 0 Computed Airspeed X0 C C 1 0 0 0 0 1 1 0 Taxi Speed X1 4 0 1 0 0 0 0 1 1 0 Computed Airspeed (CAS) X0 0 2 1 0 0 0 0 1 1 1 HF Control Word X See Attachment 110 0 6 1 0 0 0 0 1 1 1 Max. Allowable Airspeed X0 0 A 1 0 0 0 0 1 1 1 Max. Allowable Airspeed X0 2 5 1 0 0 0 0 1 1 1 OP. Software Part Number X 6-370 2 9 1 0 0 0 0 1 1 1 Cabin Temp. Reg. Valve Position (Group #2) X0 3 8 1 0 0 0 0 1 1 1 Max. Allowable Airspeed X0 B 9 1 0 0 0 0 1 1 1 HF Control Word X See Attachment 111 4 0 1 0 0 0 0 1 1 1 Airspeed Maximum Operating (VMO) X

2 0 1

2 0 2

2 0 3

2 0 4

2 0 5

2 0 6

2 0 7




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 0 6 1 0 0 0 1 0 0 0 True Airspeed X 6-270 2 9 1 0 0 0 1 0 0 0 Cargo Compartment Temperature X0 3 8 1 0 0 0 1 0 0 0 True Airspeed X 6-271 4 0 1 0 0 0 1 0 0 0 True Airspeed X

1 0 0 0 1 0 0 0 FCMC Com A340-500/600 X0 0 2 1 0 0 0 1 0 0 1 Total Air Temperature X 6-270 0 3 1 0 0 0 1 0 0 1 Total Air Temperature X0 0 6 1 0 0 0 1 0 0 1 Total Air Temperature X0 1 A 1 0 0 0 1 0 0 1 Total Air Temperature X0 2 9 1 0 0 0 1 0 0 1 Cargo Duct Temperature X0 3 8 1 0 0 0 1 0 0 1 Total Air Temperature X0 A D 1 0 0 0 1 0 0 1 Total Air Temperature Indicated X1 0 A 1 0 0 0 1 0 0 1 Total Fan Inlet Temperature X1 0 B 1 0 0 0 1 0 0 1 Total Fan Inlet Temperature X1 4 0 1 0 0 0 1 0 0 1 Total Air Temp (TAT) X1 4 2 1 0 0 0 1 0 0 1 Projected Future Longitude X

1 0 0 0 1 0 0 1 FCMC Mon A340-500/600 X0 0 4 1 0 0 0 1 0 1 0 Altitude Rate X 6-270 0 5 1 0 0 0 1 0 1 0 Altitude Rate X0 0 6 1 0 0 0 1 0 1 0 Altitude Rate X0 2 9 1 0 0 0 1 0 1 0 Cargo Temp. Reg. Valve Position X0 3 8 1 0 0 0 1 0 1 0 Altitude Rate X0 3 B 1 0 0 0 1 0 1 0 Altitude Rate X0 5 6 1 0 0 0 1 0 1 0 Altitude Rate X0 6 0 1 0 0 0 1 0 1 0 Altitude Rate X1 4 0 1 0 0 0 1 0 1 0 Altitude Rate X1 4 2 1 0 0 0 1 0 1 0 Projected Future Longitude Fine X

1 0 0 0 1 0 1 0 FCMC Int A340-500/600 X0 0 2 1 0 0 0 1 0 1 1 Static Air Temperature X 6-270 0 6 1 0 0 0 1 0 1 1 Static Air Temperature X 6-270 3 8 1 0 0 0 1 0 1 1 Static Air Temperature X0 8 D 1 0 0 0 1 0 1 1 Fuel Used X 6-271 4 0 1 0 0 0 1 0 1 1 Static Air Temp (SAT) X1 4 2 1 0 0 0 1 0 1 1 Veritical Time Interval XX X X 1 0 0 0 1 1 0 0 ICAO Aircraft Address (Part 1) X 6-39/Note 10 0 6 1 0 0 0 1 1 0 1 Impacted Pressure, Uncorrected, mb X0 1 A 1 0 0 0 1 1 0 1 Impact Pressure X0 2 9 1 0 0 0 1 1 0 1 N1 Actual (EEC) X0 2 9 1 0 0 0 1 1 0 1 EPR Actual (EEC) X0 3 8 1 0 0 0 1 1 0 1 Impacted Pressure, Uncorrected, mb X0 A D 1 0 0 0 1 1 0 1 Impacted Pressure, Uncorrected, mb X1 4 0 1 0 0 0 1 1 1 1 Impact Pressure Subsonic XX X X 1 0 0 0 1 1 1 0 ICAO Aircraft Address (Part 2) X Note 10 0 2 1 0 0 0 1 1 1 1 Geometric Vertical Rate X0 0 6 1 0 0 0 1 1 1 1 Static Pressure, Corrected (In. Hg) X0 2 9 1 0 0 0 1 1 1 1 N1 Limit (EEC) X0 2 9 1 0 0 0 1 1 1 1 EPR Actual (EEC) X0 3 8 1 0 0 0 1 1 1 1 Static Pressure, Average, Corrected (In. Hg) X1 4 0 1 0 0 0 1 1 1 1 Static Pressure Corrected (In. Hg) X0 0 6 1 0 0 1 0 0 0 0 Baro Corrected Altitude #2 X0 3 8 1 0 0 1 0 0 0 0 Baro Corrected Altitude #2 X1 4 0 1 0 0 1 0 0 0 0 Baro Corrected Altitude #2 X

1 0 0 1 0 0 0 0 MCDU #1 - System Address label (Recipient) X See Attachment 110 0 6 1 0 0 1 0 0 0 1 Indicated Angle of Attack (Average) X0 3 8 1 0 0 1 0 0 0 1 Indicated Angle of Attack (Average) X0 A D 1 0 0 1 0 0 0 1 Indicated Angle of Attack (Average) X1 2 C 1 0 0 1 0 0 0 1 Indicated Angle of Attack (Average) 1 4 0 1 0 0 1 0 0 0 1 Angle of Attach Indicated Average X

1 0 0 1 0 0 0 1 MCDU #2 - System Address label (Recipient) X See Attachment 11

2 1 0

2 1 1

2 1 2

2 1 3

2 1 4

2 1 6

2 1 5

2 1 7

2 2 0

2 2 1




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 0 6 1 0 0 1 0 0 1 0 Indicated Angle of Attack (#1 Left) X0 1 1 1 0 0 1 0 0 1 0 VOR Omnibearing X 6-101 1 2 1 0 0 1 0 0 1 0 TACAN Bearing X1 1 5 1 0 0 1 0 0 1 0 Bearing X1 2 C 1 0 0 1 0 0 1 0 Indicated Angle of Attack (#1 Left) X1 4 0 1 0 0 1 0 0 1 0 Angle of Attack, Indicated (#1 Left) X

1 0 0 1 0 0 1 0 MCDU #3 - System Address Label X See Attachment 110 0 6 1 0 0 1 0 0 1 1 Indicated Angle of Attack (#1 Right) X1 2 C 1 0 0 1 0 0 1 1 Indicated Angle of Attack (#1 Right) X1 4 0 1 0 0 1 0 0 1 1 Angle of Attack, Indicated (#1 Right) X

1 0 0 1 0 0 1 1 Printer #1 - System Address Label X See Attachment 110 0 6 1 0 0 1 0 1 0 0 Indicated Angle of Attack (#2 Left) X1 2 C 1 0 0 1 0 1 0 0 Indicated Angle of Attack (#2 Left) X1 4 0 1 0 0 1 0 1 0 0 Angle of Attack, Indicated (#2 Left) X

1 0 0 1 0 1 0 0 Printer #2 - System Address Label X See Attachment 110 0 2 1 0 0 1 0 1 0 1 Min. Maneuvering Airspeed X0 0 6 1 0 0 1 0 1 0 1 Indicated Angle of Attack (#2 Right) X0 2 B 1 0 0 1 0 1 0 1 Compensated Altitude Rate X0 5 6 1 0 0 1 0 1 0 1 Minimum Maneuvering Airspeed X0 6 0 1 0 0 1 0 1 0 1 Minimum Maneuvering Airspeed X1 2 C 1 0 0 1 0 1 0 1 Indicated Angle of Attack (#2 Right) X1 4 0 1 0 0 1 0 1 0 1 Angle of Attack, Indicated (#2 Right) X

1 0 0 1 0 1 0 1 System Address Label for HUD X See Attachment 110 0 2 1 0 0 1 0 1 1 0 Min. Op. Fuel Temp (non-conflicting) X

1 0 0 1 0 1 1 0 Data Loader System Addess Label (High Speed) X See Attachment 110 1 9 1 0 0 1 0 1 1 1 CFDS Bite Command Summary for HFDR X0 3 D 1 0 0 1 0 1 1 1 AVM Command X 6-280 5 3 1 0 0 1 0 1 1 1 CFDS Bite Command Summary for HFDR X0 7 E 1 0 0 1 0 1 1 1 BITE Command Word X0 0 6 1 0 0 1 1 0 0 0 True Airspeed X 6-250 3 8 1 0 0 1 1 0 0 0 True Airspeed X 6-251 1 4 1 0 0 1 1 0 0 0 Left Outer Probes Capacitance X

1 0 0 1 1 0 0 0 MCDU #4 - System Address Label X See Attachment 110 0 6 1 0 0 1 1 0 0 1 Total Air Temperature X 6-250 3 8 1 0 0 1 1 0 0 1 Total Air Temperature X1 1 4 1 0 0 1 1 0 0 1 Inner 2 Tank Probe Capacitance X0 0 4 1 0 0 1 1 0 1 0 Altitude Rate X 6-250 0 5 1 0 0 1 1 0 1 0 Altitude Rate X0 0 6 1 0 0 1 1 0 1 0 Altitude Rate X0 5 5 1 0 0 1 1 0 1 0 GLS Airport ID X1 1 4 1 0 0 1 1 0 1 0 Inner 4 Tank Probe Capacitance X0 0 2 1 0 0 1 1 0 1 1 ACMS Information X 6-310 0 6 1 0 0 1 1 0 1 1 Static Air Temperature X 6-250 3 8 1 0 0 1 1 0 1 1 Static Air Temperature X 6-250 5 6 1 0 0 1 1 0 1 1 ACMS Information X0 6 0 1 0 0 1 1 0 1 1 ACMS Information X1 1 4 1 0 0 1 1 0 1 1 Right Outer Probe Capacitance X0 0 2 1 0 0 1 1 1 0 0 ACMS Information X 6-310 0 6 1 0 0 1 1 1 0 0 Baro Correction (mb) #1 X0 3 8 1 0 0 1 1 1 0 0 Baro Correction (mb) #1 X0 5 6 1 0 0 1 1 1 0 0 ACMS Information X0 6 0 1 0 0 1 1 1 0 0 ACMS Information X

1 0 0 1 1 1 0 0 System Address Label for EIVMU 1 X See Attachment 110 0 2 1 0 0 1 1 1 0 1 ACMS Information X 6-310 0 6 1 0 0 1 1 1 0 1 Baro Correction (ins. Hg) #1 X 6-250 3 8 1 0 0 1 1 1 0 1 Baro Correction (ins. Hg) #1 X 6-250 5 6 1 0 0 1 1 1 0 1 ACMS Information X0 6 0 1 0 0 1 1 1 0 1 ACMS Information X

1 0 0 1 1 1 0 1 System Address Label for EIVMU 2 X See Attachment 11

2 2 4

2 2 3

2 3 3

2 2 6

2 3 2

2 2 5

2 2 7

2 3 1

2 3 0

2 3 4

2 3 5

2 2 2




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 0 2 1 0 0 1 1 1 1 0 ACMS Information X 6-310 0 6 1 0 0 1 1 1 1 0 Baro Correction (mb) #2 X0 3 8 1 0 0 1 1 1 1 0 Baro Correction (mb) #2 X0 5 6 1 0 0 1 1 1 1 0 ACMS Information X0 6 0 1 0 0 1 1 1 1 0 ACMS Information X

1 0 0 1 1 1 1 0 System Address Label for EIVMU 3 X See Attachment 110 0 2 1 0 0 1 1 1 1 1 ACMS Information X0 0 6 1 0 0 1 1 1 1 1 Baro Correction (ins. Hg) #2 X0 0 B 1 0 0 1 1 1 1 1 Horizontal Uncertainty Level X0 3 8 1 0 0 1 1 1 1 1 Baro Correction (ins. Hg) #2 X0 5 6 1 0 0 1 1 1 1 1 ACMS Information X0 6 0 1 0 0 1 1 1 1 1 ACMS Information X

1 0 0 1 1 1 1 1 System Address Label for EIVMU 4 X See Attachment 110 1 0 1 0 0 0 0 0 Spare0 0 2 1 0 1 0 0 0 0 1 Min. Airspeed for Flap Extension X0 0 6 1 0 1 0 0 0 0 1 Corrected Angle of Attack X0 2 C 1 0 1 0 0 0 0 1 Reserved (Special Use) X0 3 8 1 0 1 0 0 0 0 1 Corrected Angle of Attack X0 4 D 1 0 1 0 0 0 0 1 FQIS System Data X 6-350 5 6 1 0 1 0 0 0 0 1 Min. Airspeed for Flap Extension X0 6 0 1 0 1 0 0 0 0 1 Min. Airspeed for Flap Extension X1 4 0 1 0 1 0 0 0 0 1 Angle of Attack, Corrected X1 6 0 1 0 1 0 0 0 0 1 Tank Unit Data X 6-38

1 0 1 0 0 0 0 1 System Address Label for APM-MMR X See Attachment 110 0 6 1 0 1 0 0 0 1 0 Total Pressure X0 0 9 1 0 1 0 0 0 1 0 Ground Station ID (Word #1) X0 1 0 1 0 1 0 0 0 1 0 Ground Station ID (Word #1) X0 1 1 1 0 1 0 0 0 1 0 Ground Station ID (Word #1) X1 1 2 1 0 1 0 0 0 1 0 Ground Station ID (Word #1) X0 1 A 1 0 1 0 0 0 1 0 Total Pressure X0 3 8 1 0 1 0 0 0 1 0 Total Pressure X0 3 B 1 0 1 0 0 0 1 0 Speed Deviation X0 A D 1 0 1 0 0 0 1 0 Total Pressure, Uncorrected, mb X1 4 0 1 0 1 0 0 0 1 0 Total Pressure X

1 0 1 0 0 0 1 0 System Address Label for MMR X See Attachment 110 3 7 1 0 1 0 0 0 1 1 Zero Fuel Weight (kg) X0 5 5 1 0 1 0 0 0 1 1 GLS Runway Selection XX X X 1 0 1 0 0 0 1 1 Simulator to Avionics Control Word X Note 10 0 9 1 0 1 0 0 1 0 0 Ground Station ID (Word #2) X0 1 0 1 0 1 0 0 1 0 0 Ground Station ID (Word #2) X0 1 1 1 0 1 0 0 1 0 0 VOR Ground Station Ident Word #2 X0 1 2 1 0 1 0 0 1 0 0 Ground Station ID (Word #2) X0 1 C 1 0 1 0 0 1 0 0 Fuel Flow (Engine Direct) X0 3 3 1 0 1 0 0 1 0 0 Fuel Flow (Wf) X0 3 B 1 0 1 0 0 1 0 0 Mach Error X0 8 D 1 0 1 0 0 1 0 0 Fuel Flow Rate X1 0 A 1 0 1 0 0 1 0 0 Fuel Mass Flow X1 0 B 1 0 1 0 0 1 0 0 Fuel Mass Flow X1 4 0 1 0 1 0 0 1 0 0 Angle of Attack, Normalized X

1 0 1 0 0 1 0 0 System Address Label for ILS X See Attachment 11

2 4 2

2 4 4

2 3 6

2 4 0

2 4 3

2 4 1

2 3 7




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 0 2 1 0 1 0 0 1 0 1 Minimum Airspeed X0 0 3 1 0 1 0 0 1 0 1 Minimum Airspeed X0 0 A 1 0 1 0 0 1 0 1 Minimum Airspeed X0 2 9 1 0 1 0 0 1 0 1 N3 (Engine) X0 3 8 1 0 1 0 0 1 0 1 Average Static Pressure mb, Uncorrected X0 3 B 1 0 1 0 0 1 0 1 EPR Error X0 5 6 1 0 1 0 0 1 0 1 Minimum Airspeed X0 6 0 1 0 1 0 0 1 0 1 Minimum Airspeed X0 A D 1 0 1 0 0 1 0 1 Average Static Pressure mb, Uncorrected X1 4 0 1 0 1 0 0 1 0 1 Static Pressure, Uncorrected X

1 0 1 0 0 1 0 1 System Address Label for MLS X See Attachment 110 0 2 1 0 1 0 0 1 1 0 General Maximum Speed (VCMAX) X0 0 6 1 0 1 0 0 1 1 0 Average Static Pressure X0 0 9 1 0 1 0 0 1 1 0 DME Ground Station Ident Word #1 X0 1 C 1 0 1 0 0 1 1 0 N1 (Engine Direct) X0 2 9 1 0 1 0 0 1 1 0 N1 (Engine Direct) X0 3 8 1 0 1 0 0 1 1 0 Average Static Pressure mb, Corrected X0 3 B 1 0 1 0 0 1 1 0 Angle of Attack Error X

1 0 1 0 0 1 1 0 System address Label for AHRS X See Attachment 110 0 2 1 0 1 0 0 1 1 1 Control Minimum Speed (VCMIN) X0 0 9 1 0 1 0 0 1 1 1 DME Ground Station Ident Word #1 X0 0 B 1 0 1 0 0 1 1 1 Horizontal Figure of Merit X0 1 F 1 0 1 0 0 1 1 1 Total Fuel X0 2 C 1 0 1 0 0 1 1 1 Total Fuel X0 3 B 1 0 1 0 0 1 1 1 Speed Error X0 4 D 1 0 1 0 0 1 1 1 Total Fuel X0 5 6 1 0 1 0 0 1 1 1 Control Minimum Speed (VCMIN) X0 5 A 1 0 1 0 0 1 1 1 Total Fuel X0 6 0 1 0 1 0 0 1 1 1 Control Minimum Speed (VCMIN) X0 E B 1 0 1 0 0 1 1 1 Fuel to Remain X1 1 4 1 0 1 0 0 1 1 1 Fuel on Board X1 4 0 1 0 1 0 0 1 1 1 Airspeed Minimum Vmc X0 0 2 1 0 1 0 1 0 0 0 Continuous N1 Limit X0 2 B 1 0 1 0 1 0 0 0 Maximum Continuous EPR Limit X0 2 C 1 0 1 0 1 0 0 0 Preselected Fuel Quantity X0 3 8 1 0 1 0 1 0 0 0 Indicated Side Slip Angle X0 5 A 1 0 1 0 1 0 0 0 Preselected Fuel Quantity X0 A D 1 0 1 0 1 0 0 0 Indicated Side Slip Angle or AOS X1 1 4 1 0 1 0 1 0 0 0 Preselected Fuel Quantity X1 2 B 1 0 1 0 1 0 0 0 Temperature Rate of Change X0 0 1 1 0 1 0 1 0 0 1 Distance to Go X0 0 2 1 0 1 0 1 0 0 1 Distance to Go X0 0 6 1 0 1 0 1 0 0 1 Baro Corrected Altitude #3 X0 1 A 1 0 1 0 1 0 0 1 Flight Leg Counter X 6-190 3 8 1 0 1 0 1 0 0 1 Baro Corrected Altitude #3 X

1 0 1 0 1 0 0 1 System Address Label VDR #1 X See Attachment 110 0 1 1 0 1 0 1 0 1 0 Time to Go X0 0 2 1 0 1 0 1 0 1 0 Time to Go X0 0 6 1 0 1 0 1 0 1 0 Baro Corrected Altitude #4 X0 1 A 1 0 1 0 1 0 1 0 EPR Idle X0 2 F 1 0 1 0 1 0 1 0 EPR Idle Reference X0 3 8 1 0 1 0 1 0 1 0 Baro Corrected Altitude #4 X0 3 F 1 0 1 0 1 0 1 0 EPR Idle Reference X0 E B 1 0 1 0 1 0 1 0 Time Until Jettison Complete X

1 0 1 0 1 0 1 0 System Address Label VDR #2 X See Attachment 110 0 2 1 0 1 0 1 0 1 1 Go-Around N1 Limit X0 1 E 1 0 1 0 1 0 1 1 Go-Around EPR Limit X0 3 8 1 0 1 0 1 0 1 1 Corrected Side Slip Angle X

1 0 1 0 1 0 1 1 System Address Label VDR #3 X See Attachment 11

2 4 5

2 4 6

2 4 7

2 5 1

2 5 0

2 5 2

2 5 3




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


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

2 5 4

2 5 5

2 6 0

2 6 1

2 5 6

2 5 7




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 0 2 1 0 1 1 0 0 1 0 Documentary Data X 6-140 0 A 1 0 1 1 0 0 1 0 Predictive Airspeed Variation X0 1 C 1 0 1 1 0 0 1 0 LP Compressor Exist Pressure (PT3) X0 2 C 1 0 1 1 0 0 1 0 Fuel Quantity (Tanks) #5 X0 3 3 1 0 1 1 0 0 1 0 LP Compressor Exist Pressure X0 4 D 1 0 1 1 0 0 1 0 T/U CAP-L Tank 1-4 X0 5 6 1 0 1 1 0 0 1 0 Documentary Data X0 5 A 1 0 1 1 0 0 1 0 Fuel Quantity - Right Outer Cell X0 6 0 1 0 1 1 0 0 1 0 Documentary Data X1 0 A 1 0 1 1 0 0 1 0 HP Compressor Inlet Total Pressure X1 0 B 1 0 1 1 0 0 1 0 HP Compressor Inlet Total Pressure X1 1 4 1 0 1 1 0 0 1 0 Center Tank Fuel Quantity X0 0 2 1 0 1 1 0 0 1 1 Minimum Airspeed for Flap Retraction X0 0 A 1 0 1 1 0 0 1 1 Minimum Airspeed for Flap Retraction X0 1 0 1 0 1 1 0 0 1 1 ILS Ground Station Ident Word #1 X0 1 C 1 0 1 1 0 0 1 1 LP Compressor Exit Temperature X0 2 C 1 0 1 1 0 0 1 1 Fuel Quantity (Tanks) #6 X0 3 3 1 0 1 1 0 0 1 1 LP Compressor Exit Temperature X0 4 D 1 0 1 1 0 0 1 1 T/U CAP-L Tank 5-8 X0 5 5 1 0 1 1 0 0 1 1 Ground Station/Approach X0 5 6 1 0 1 1 0 0 1 1 Minimum Airspeed For Flap Retraction X0 6 0 1 0 1 1 0 0 1 1 Minimum Airspeed For Flap Retraction X1 0 A 1 0 1 1 0 0 1 1 Selected Compressor Inlet Temperature (Total) X1 0 B 1 0 1 1 0 0 1 1 Selected Compressor Inlet Temperature (Total) X1 1 4 1 0 1 1 0 0 1 1 Collector Cell 3 and 4 Fuel Quantity X0 0 2 1 0 1 1 0 1 0 0 Time to Touchdown X0 0 A 1 0 1 1 0 1 0 0 Minimum Airspeed for Slats Retraction X0 1 0 1 0 1 1 0 1 0 0 ILS Ground Station Ident Word #2 X0 1 C 1 0 1 1 0 1 0 0 HP Compressor Exit Pressure X0 2 C 1 0 1 1 0 1 0 0 Fuel Quantity (Tanks) #7 X0 2 F 1 0 1 1 0 1 0 0 Burner Pressure X0 3 3 1 0 1 1 0 1 0 0 HP Compressor Exit Pressure X0 3 F 1 0 1 1 0 1 0 0 Burner Pressure X0 4 D 1 0 1 1 0 1 0 0 T/U CAP-L Tank 9-12 X0 5 5 1 0 1 1 0 1 0 0 Ground Station/Approach X0 5 6 1 0 1 1 0 1 0 0 Time to Touchdown X0 6 0 1 0 1 1 0 1 0 0 Time to Touchdown X1 0 A 1 0 1 1 0 1 0 0 Selected Compressor Discharge Temperature X1 0 B 1 0 1 1 0 1 0 0 Selected Compressor Discharge Temperature X1 1 4 1 0 1 1 0 1 0 0 Fuel Quantity (Tanks) #7 X1 3 A 1 0 1 1 0 1 0 0 Burner Pressure X0 0 2 1 0 1 1 0 1 0 1 Minimum Buffet Airspeed X0 0 4 1 0 1 1 0 1 0 1 Integrated Vertical Acceleration X0 0 A 1 0 1 1 0 1 0 1 Maneuvering Airspeed X0 1 C 1 0 1 1 0 1 0 1 HP Compressor Exit Temperature (TT4.5) X0 2 C 1 0 1 1 0 1 0 1 Fuel Quantity (Tanks) #8 X0 3 3 1 0 1 1 0 1 0 1 HP Compressor Exit Temperature X0 3 8 1 0 1 1 0 1 0 1 Integrated Vertical Acceleration X0 4 D 1 0 1 1 0 1 0 1 T/U CAP-L Tank 13-14 X0 5 6 1 0 1 1 0 1 0 1 Minimum Buffet Airspeed X0 6 0 1 0 1 1 0 1 0 1 Minimum Buffet Airspeed X1 0 A 1 0 1 1 0 1 0 1 Selected Compressor Discharge Temperature X1 0 B 1 0 1 1 0 1 0 1 Selected Compressor Discharge Temperature X1 1 4 1 0 1 1 0 1 0 1 Inner Tank 3 Fuel Quantity X0 0 1 1 0 1 1 0 1 1 0 Test Word B X0 1 D 1 0 1 1 0 1 1 0 Test Word B X0 4 D 1 0 1 1 0 1 1 0 T/U CAP-C Tank 1-4 X1 1 4 1 0 1 1 0 1 1 0 Inner Tank 2 Fuel Quantity X

1 0 1 1 0 1 1 0 Cabin Video System - System Address Label X See Attachment 11

2 6 2

2 6 3

2 6 4

2 6 5

2 6 6




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


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

2 6 7

2 7 0




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 0 2 1 0 1 1 1 0 0 1 Discrete Data #2 X0 0 6 1 0 1 1 1 0 0 1 Discrete Data #2 X0 1 8 1 0 1 1 1 0 0 1 Discrete Data #2 X0 1 A 1 0 1 1 1 0 0 1 Discrete Data #2 X0 1 C 1 0 1 1 1 0 0 1 Discrete Data #2 X0 1 E 1 0 1 1 1 0 0 1 Discrete Data #2 X0 2 9 1 0 1 1 1 0 0 1 Discrete Data #2 X0 2 F 1 0 1 1 1 0 0 1 Discrete Data #2 X0 3 0 1 0 1 1 1 0 0 1 Discrete Data #2 X0 3 1 1 0 1 1 1 0 0 1 Discrete Data #2 X0 3 3 1 0 1 1 1 0 0 1 Discrete Data #2 X0 3 5 1 0 1 1 1 0 0 1 Discrete Data #2 X0 3 8 1 0 1 1 1 0 0 1 Discrete Data #2 X0 3 A 1 0 1 1 1 0 0 1 Discrete Data #2 X0 3 B 1 0 1 1 1 0 0 1 Discrete Data #2 X0 3 F 1 0 1 1 1 0 0 1 Discrete Data #2 X0 4 1 1 0 1 1 1 0 0 1 SDU To ACARS MU/CMU Join/Leave Message X0 4 D 1 0 1 1 1 0 0 1 T/U CAP-A Tank 1-4 X0 5 5 1 0 1 1 1 0 0 1 MMR Discrete X0 5 6 1 0 1 1 1 0 0 1 Discrete Data #2 X0 5 A 1 0 1 1 1 0 0 1 Fuel Density X0 6 0 1 0 1 1 1 0 0 1 Discrete Data #2 X0 A 2 1 0 1 1 1 0 0 1 Discrete Data #2 X0 A 8 1 0 1 1 1 0 0 1 Discrete Data #2 X0 A D 1 0 1 1 1 0 0 1 Discrete Data #2 X0 C 5 1 0 1 1 1 0 0 1 Discrete Data #2 X1 0 A 1 0 1 1 1 0 0 1 Discrete Data #2 X1 0 B 1 0 1 1 1 0 0 1 Discrete Data #2 X1 1 4 1 0 1 1 1 0 0 1 Fuel Transfer Indication X1 4 0 1 0 1 1 1 0 0 1 Discrete Data #2 X1 4 2 1 0 1 1 1 0 0 1 Altitude Filter Limits (Disc Data 2) X0 0 1 1 0 1 1 1 0 1 0 Discrete Data #3 X0 0 2 1 0 1 1 1 0 1 0 Discrete Data #3 X0 0 3 1 0 1 1 1 0 1 0 Discrete Data #3 X0 1 8 1 0 1 1 1 0 1 0 Discrete Data #3 X0 1 A 1 0 1 1 1 0 1 0 Discrete Data #30 1 C 1 0 1 1 1 0 1 0 Discrete Data #3 X0 2 5 1 0 1 1 1 0 1 0 Discrete Data #3 X0 2 9 1 0 1 1 1 0 1 0 Discrete Data #3 X0 2 F 1 0 1 1 1 0 1 0 Discrete Data #3 X0 3 5 1 0 1 1 1 0 1 0 Discrete Data #3 X0 3 8 1 0 1 1 1 0 1 0 Discrete Data #3 X0 3 A 1 0 1 1 1 0 1 0 Discrete Data #3 X0 3 B 1 0 1 1 1 0 1 0 Discrete Data #3 X0 3 F 1 0 1 1 1 0 1 0 Discrete Data #3 X0 4 D 1 0 1 1 1 0 1 0 T/U CAP-A Tank 5-8 X0 5 3 1 0 1 1 1 0 1 0 HFDL Slave (Disc Data 2) X0 5 6 1 0 1 1 1 0 1 0 Discrete Data #3 X0 5 A 1 0 1 1 1 0 1 0 Fuel Density X0 6 0 1 0 1 1 1 0 1 0 Discrete Data #3 X0 A D 1 0 1 1 1 0 1 0 Discrete Data #3 X0 C 5 1 0 1 1 1 0 1 0 Discrete Data #3 X1 0 A 1 0 1 1 1 0 1 0 Discrete Data #3 X1 0 B 1 0 1 1 1 0 1 0 Discrete Data #3 X1 1 4 1 0 1 1 1 0 1 0 Fuel Transfer Indication X1 4 0 1 0 1 1 1 0 1 0 Discrete Data #3 X

2 7 1

2 7 2




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 0 1 1 0 1 1 1 0 1 1 Discrete Data #4 X0 0 3 1 0 1 1 1 0 1 1 Discrete Data #4 X0 0 B 1 0 1 1 1 0 1 1 GNSS Sensor Status X0 1 8 1 0 1 1 1 0 1 1 Discrete Data #4 X0 1 C 1 0 1 1 1 0 1 1 Discrete Data #4 X0 2 5 1 0 1 1 1 0 1 1 Discrete Data #4 X0 2 9 1 0 1 1 1 0 1 1 Discrete Data #4 X0 2 F 1 0 1 1 1 0 1 1 Discrete Data #4 X0 3 3 1 0 1 1 1 0 1 1 Discrete Data #4 X0 3 5 1 0 1 1 1 0 1 1 Discrete Data #4 X0 3 B 1 0 1 1 1 0 1 1 Discrete Data #4 X0 3 F 1 0 1 1 1 0 1 1 Discrete Data #4 X0 4 D 1 0 1 1 1 0 1 1 T/U CAP-A Tank 9-11 X0 5 5 1 0 1 1 1 0 1 1 GNSS Status X0 5 A 1 0 1 1 1 0 1 1 Sensor Valves Left Wing Tank X0 C 5 1 0 1 1 1 0 1 1 Discrete Data #4 X1 0 A 1 0 1 1 1 0 1 1 Discrete Data #4 X1 0 B 1 0 1 1 1 0 1 1 Discrete Data #4 X1 1 4 1 0 1 1 1 0 1 1 Memos and Status X0 0 1 1 0 1 1 1 1 0 0 Discrete Data #5 X0 0 3 1 0 1 1 1 1 0 0 Discrete Data #5 X0 0 A 1 0 1 1 1 1 0 0 Discrete Data #5 X0 1 8 1 0 1 1 1 1 0 0 Discrete Data #5 X0 1 C 1 0 1 1 1 1 0 0 Discrete Data #5 X0 2 5 1 0 1 1 1 1 0 0 Discrete Data #5 X0 2 9 1 0 1 1 1 1 0 0 Discrete Data #5 X0 2 F 1 0 1 1 1 1 0 0 Discrete Data #5 X0 3 3 1 0 1 1 1 1 0 0 Discrete Data #5 X0 3 5 1 0 1 1 1 1 0 0 Discrete Data #5 X0 3 B 1 0 1 1 1 1 0 0 Discrete Data #5 X0 3 F 1 0 1 1 1 1 0 0 Discrete Data #5 X0 4 D 1 0 1 1 1 1 0 0 T/U CAP-R Tank 1-4 X0 5 A 1 0 1 1 1 1 0 0 Sensor Valves Right Wing Tank X0 C 5 1 0 1 1 1 1 0 0 Discrete Data #5 X1 0 A 1 0 1 1 1 1 0 0 Discrete Data #5 X1 0 B 1 0 1 1 1 1 0 0 Discrete Data #5 X1 1 4 1 0 1 1 1 1 0 0 Fuel Transfer Indications X0 0 1 1 0 1 1 1 1 0 1 Discrete Data #6 X0 0 2 1 0 1 1 1 1 0 1 Discrete Data #6 X0 0 3 1 0 1 1 1 1 0 1 Discrete Data #6 X0 1 8 1 0 1 1 1 1 0 1 Discrete Data #6 X0 1 C 1 0 1 1 1 1 0 1 Discrete Data #6 X0 2 5 1 0 1 1 1 1 0 1 Discrete Data #6 X0 2 9 1 0 1 1 1 1 0 1 Discrete Data #6 X0 2 B 1 0 1 1 1 1 0 1 Discrete Data #6 X0 2 F 1 0 1 1 1 1 0 1 Discrete Data #6 X0 3 5 1 0 1 1 1 1 0 1 Discrete Data #6 X0 3 8 1 0 1 1 1 1 0 1 IR Discrete Word #2 X0 3 B 1 0 1 1 1 1 0 1 Discrete Data #6 X0 3 F 1 0 1 1 1 1 0 1 Discrete Data #6 X0 4 A 1 0 1 1 1 1 0 1 T/U CAP-R Tank 5-8 X0 4 D 1 0 1 1 1 1 0 1 Discrete Data #6 X0 5 A 1 0 1 1 1 1 0 1 Discrete Data #6 X0 5 6 1 0 1 1 1 1 0 1 Discrete Data #6 X0 6 0 1 0 1 1 1 1 0 1 Discrete Data #6 X1 0 A 1 0 1 1 1 1 0 1 Discrete Data #6 X1 0 B 1 0 1 1 1 1 0 1 Discrete Data #6 X1 1 4 1 0 1 1 1 1 0 1 Miscellaneous Warning X

2 7 3

2 7 4

2 7 5




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 0 2 1 0 1 1 1 1 1 0 Discrete Data #7 X0 1 8 1 0 1 1 1 1 1 0 Discrete Data #7 X0 1 C 1 0 1 1 1 1 1 0 Discrete Data #7 X0 2 5 1 0 1 1 1 1 1 0 Discrete Status 8 EFIS X0 2 9 1 0 1 1 1 1 1 0 Discrete Data #7 X0 2 F 1 0 1 1 1 1 1 0 Discrete Data #7 X0 3 F 1 0 1 1 1 1 1 0 Discrete Data #7 X0 4 D 1 0 1 1 1 1 1 0 T/U CAP-R Tank 9-12 X0 5 6 1 0 1 1 1 1 1 0 Discrete Data #7 X0 5 8 1 0 1 1 1 1 1 0 Output Status Word #2 X0 5 A 1 0 1 1 1 1 1 0 Discrete Data #7 X0 6 0 1 0 1 1 1 1 1 0 Discrete Data #7 X0 B B 1 0 1 1 1 1 1 0 Discrete Data #7 X1 1 4 1 0 1 1 1 1 1 0 Discrete Data #7 X0 0 1 1 0 1 1 1 1 1 0 FCC to Simulator Control Word - Simulator Use Only X0 0 2 1 0 1 1 1 1 1 0 FMC to Simulator Control Word - Simulator Use Only X0 0 3 1 0 1 1 1 1 1 0 TCC to Simulator Control Word - Simulator Use Only XX X X 1 0 1 1 1 1 1 1 General Test Word X Note 10 0 4 1 0 1 1 1 1 1 1 IRS Maintenance Discrete X0 1 8 1 0 1 1 1 1 1 1 Discrete Data #8 X0 3 8 1 0 1 1 1 1 1 1 IR Test X0 4 D 1 0 1 1 1 1 1 1 T/U CAP-R Tank 13-14 X1 1 4 1 0 1 1 1 1 1 1 Fuel Transfer and CG Status X0 0 1 1 1 0 0 0 0 0 0 Application Dependent X0 1 A 1 1 0 0 0 0 0 0 Application Dependent X0 3 D 1 1 0 0 0 0 0 0 Application Dependent X0 5 A 1 1 0 0 0 0 0 0 Internal Parameter for SPATIAAL X1 0 A 1 1 0 0 0 0 0 0 ECU Internal Temperature X1 0 B 1 1 0 0 0 0 0 0 ECU Internal Temperature XT B D 1 1 0 0 0 0 0 0 Data Loader Address Label (Low Speed) X

1 1 0 0 0 0 0 0 System Address Label for FMC 1 X See Attachment 110 0 1 1 1 0 0 0 0 0 1 Application Dependent X0 0 2 1 1 0 0 0 0 0 1 Application Dependent X0 1 A 1 1 0 0 0 0 0 1 Application Dependent X0 5 6 1 1 0 0 0 0 0 1 Application Dependent X0 5 A 1 1 0 0 0 0 0 1 Internal Parameter for SPATIAAL X0 6 0 1 1 0 0 0 0 0 1 Application Dependent X1 0 A 1 1 0 0 0 0 0 1 Demanded Fuel Metering Valve Position X1 0 B 1 1 0 0 0 0 0 1 Demanded Fuel Metering Valve Position X

1 1 0 0 0 0 0 1 System Address Label for FMC 2 X See Attachment 110 0 1 1 1 0 0 0 0 1 0 Application Dependent X0 0 2 1 1 0 0 0 0 1 0 Application Dependent X0 1 A 1 1 0 0 0 0 1 0 Application Dependent X0 5 6 1 1 0 0 0 0 1 0 Application Dependent X0 5 A 1 1 0 0 0 0 1 0 Internal Parameter for SPATIAAL X0 6 0 1 1 0 0 0 0 1 0 Application Dependent X1 0 A 1 1 0 0 0 0 1 0 Demanded Variable Stator Vane Position X1 0 B 1 1 0 0 0 0 1 0 Demanded Variable Stator Vane Position X

1 1 0 0 0 0 1 0 System Address Label for AIDS (DFDAU) X See Attachment 110 0 1 1 1 0 0 0 0 1 1 Application Dependent X0 0 2 1 1 0 0 0 0 1 1 Application Dependent X0 1 A 1 1 0 0 0 0 1 1 Application Dependent X0 5 6 1 1 0 0 0 0 1 1 Application Dependent X0 5 A 1 1 0 0 0 0 1 1 Internal Parameter for SPATIAAL X0 6 0 1 1 0 0 0 0 1 1 Application Dependent X1 0 A 1 1 0 0 0 0 1 1 Demanded Variable Bleed Valve Position X1 0 B 1 1 0 0 0 0 1 1 Demanded Variable Bleed Valve Position X

1 1 0 0 0 0 1 1 System Address Label for CFDIU X See attachment 110 0 1 1 1 0 0 0 1 0 0 Application Dependent X0 1 A 1 1 0 0 0 1 0 0 Application Dependent X0 5 A 1 1 0 0 0 1 0 0 Internal Parameter for SPATIAAL X1 0 A 1 1 0 0 0 1 0 0 Demanded HPT Clearance Valve Position X1 0 B 1 1 0 0 0 1 0 0 Demanded HPT Clearance Valve Position X

1 1 0 0 0 1 0 0 System Address Label for ACARS X See Attachment 11

3 0 3

3 0 4

2 7 7

3 0 0

3 0 1

3 0 2

2 7 6




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 0 1 1 1 0 0 0 1 0 1 Application Dependent X0 1 A 1 1 0 0 0 1 0 1 Application Dependent X0 5 A 1 1 0 0 0 1 0 1 Internal Parameter for SPATIAAL X1 0 A 1 1 0 0 0 1 0 1 Demanded LPT Clearance Valve Position X1 0 B 1 1 0 0 0 1 0 1 Demanded LPT Clearance Valve Position X

1 1 0 0 0 1 0 1 System Address Label for Weight/Balance System X See Attachment 110 0 1 1 1 0 0 0 1 1 0 Application Dependent X0 1 A 1 1 0 0 0 1 1 0 Application Dependent X0 5 A 1 1 0 0 0 1 1 0 Internal Parameter for SPATIAAL X

1 1 0 0 0 1 1 0 System Address Label for TCAS X See Attachment 110 0 1 1 1 0 0 0 1 1 1 Application Dependent X0 1 A 1 1 0 0 0 1 1 1 Application Dependent X0 5 A 1 1 0 0 0 1 1 1 Internal Parameter for SPATIAAL X

1 1 0 0 0 1 1 1 System Address Label for Satellite Data Unit (SDI) X See Attachment 110 0 2 1 1 0 0 1 0 0 0 Present Position - Latitude X 6-270 0 4 1 1 0 0 1 0 0 0 Present Position - Latitude X0 2 9 1 1 0 0 1 0 0 0 Aileron Position X0 3 8 1 1 0 0 1 0 0 0 Present Position - Latitude X0 4 D 1 1 0 0 1 0 0 0 COMP CAP - TANK X0 5 6 1 1 0 0 1 0 0 0 Present Position Latitude X0 5 A 1 1 0 0 1 0 0 0 Internal Parameter for SPATIAAL X0 6 0 1 1 0 0 1 0 0 0 Present Postion Latitude X1 1 4 1 1 0 0 1 0 0 0 Right Outer Tank Fuel Quantity X

1 1 0 0 1 0 0 0 System Address Label for GPWS X See Attachment 110 0 2 1 1 0 0 1 0 0 1 Present Position - Longitude X 6-270 0 4 1 1 0 0 1 0 0 1 Present Position - Longitude X0 2 9 1 1 0 0 1 0 0 1 Aileron Trim X0 3 8 1 1 0 0 1 0 0 1 Present Position - Longitude X0 3 B 1 1 0 0 1 0 0 1 Control Wheel Roll Force X0 5 6 1 1 0 0 1 0 0 1 Present Postion Longitude X0 5 A 1 1 0 0 1 0 0 1 Internal Parameter for SPATIAAL X0 6 0 1 1 0 0 1 0 0 1 Present Position Longitude X1 1 4 1 1 0 0 1 0 0 1 Right Outer Tank Fuel Quantity X

1 1 0 0 1 0 0 1 System Address Label for GNLU 1 X See Attachment 110 0 2 1 1 0 0 1 0 1 0 Ground Speed X 6-270 0 4 1 1 0 0 1 0 1 0 Ground Speed X0 0 5 1 1 0 0 1 0 1 0 Ground Speed X0 2 9 1 1 0 0 1 0 1 0 Rudder Position X0 3 8 1 1 0 0 1 0 1 0 Ground Speed X0 5 6 1 1 0 0 1 0 1 0 Ground Speed X0 5 A 1 1 0 0 1 0 1 0 Fuel Quantity ACT 1 X0 6 0 1 1 0 0 1 0 1 0 Ground Speed X1 1 4 1 1 0 0 1 0 1 0 Additional Center Tank (Act 1) Fuel Quantity X

1 1 0 0 1 0 1 0 System Address Label for GNLU 2 X See Attachment 110 0 2 1 1 0 0 1 0 1 1 Track Angle - True X0 0 4 1 1 0 0 1 0 1 1 Track Angle - True X0 2 5 1 1 0 0 1 0 1 1 Track Angle - True X0 2 9 1 1 0 0 1 0 1 1 Rudder Trim X0 3 8 1 1 0 0 1 0 1 1 Track Angle - True X0 5 6 1 1 0 0 1 0 1 1 Track Angle - True X0 5 A 1 1 0 0 1 0 1 1 Fuel Quantity ACT 2 X0 6 0 1 1 0 0 1 0 1 1 Track Angle - True X1 1 4 1 1 0 0 1 0 1 1 Additional Center Tank (Act 2) Fuel Quantity X

1 1 0 0 1 0 1 1 System Address Label for GNLU 3 X See Attachment 110 0 2 1 1 0 0 1 1 0 0 Stabilizer Position Indication (B747-400) X0 0 4 1 1 0 0 1 1 0 0 True Heading X0 2 5 1 1 0 0 1 1 0 0 True Heading X0 2 9 1 1 0 0 1 1 0 0 Elevator Position X0 3 8 1 1 0 0 1 1 0 0 True Heading X0 3 B 1 1 0 0 1 1 0 0 Control Wheel Pitch Force X0 5 A 1 1 0 0 1 1 0 0 Internal Parameter for SPATIAAL X1 1 4 1 1 0 0 1 1 0 0 Rear Center Tank (RCT) Fuel Quantity X

1 1 0 0 1 1 0 0 System Address Label for GNU 1 X See Attachment 11

3 1 3

3 1 4

3 0 7

3 1 1

3 1 0

3 1 2

3 0 5

3 0 6




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 0 1 1 1 0 0 1 1 0 1 Stabilizer Position X0 0 2 1 1 0 0 1 1 0 1 Wind Speed X0 0 4 1 1 0 0 1 1 0 1 Wind Speed X0 0 5 1 1 0 0 1 1 0 1 Wind Speed X0 2 9 1 1 0 0 1 1 0 1 Stabilizer Position X0 3 8 1 1 0 0 1 1 0 1 Wind Speed X0 5 6 1 1 0 0 1 1 0 1 Wind Speed X0 5 A 1 1 0 0 1 1 0 1 Internal Parameter for SPATIAAL X0 6 0 1 1 0 0 1 1 0 1 Wind Speed X0 A 1 1 1 0 0 1 1 0 1 Stabilizer Position X

1 1 0 0 1 1 0 1 System Address Label for GNU 2 X See Attachment 110 0 2 1 1 0 0 1 1 1 0 Wind Direction (True) X0 0 4 1 1 0 0 1 1 1 0 Wind Angle X0 2 9 1 1 0 0 1 1 1 0 Oil Temperature (Engine) X0 3 8 1 1 0 0 1 1 1 0 Wind Angle X0 5 6 1 1 0 0 1 1 1 0 Wind Direction (True) X0 5 A 1 1 0 0 1 1 1 0 Internal Parameter for SPATIAAL X0 6 0 1 1 0 0 1 1 1 0 Wind Direction (True) X0 D 0 1 1 0 0 1 1 1 0 Engine Oil Temperature X1 0 A 1 1 0 0 1 1 1 0 Engine Oil Temperature X1 0 B 1 1 0 0 1 1 1 0 Engine Oil Temperature X

1 1 0 0 1 1 1 0 System Address Label for GNU 3 X See Attachment 110 0 2 1 1 0 0 1 1 1 1 Track Angle - Magnetic X0 0 4 1 1 0 0 1 1 1 1 Track Angle - Magnetic X0 0 5 1 1 0 0 1 1 1 1 Track Angle - Magnetic X0 2 5 1 1 0 0 1 1 1 1 Track Angle - Magnetic X0 2 9 1 1 0 0 1 1 1 1 Oil Pressure (Engine) X0 3 8 1 1 0 0 1 1 1 1 Track Angle - Magnetic X0 5 6 1 1 0 0 1 1 1 1 Track Angle - Magnetic X0 5 A 1 1 0 0 1 1 1 1 Internal Parameter for SPATIAAL X0 6 0 1 1 0 0 1 1 1 1 Track Angle - Magnetic X0 D 0 1 1 0 0 1 1 1 1 Oil Pressure (Engine) X0 0 4 1 1 0 1 0 0 0 0 Magnetic Heading X0 0 5 1 1 0 1 0 0 0 0 Magnetic Heading X0 2 5 1 1 0 1 0 0 0 0 Magnetic Heading X0 2 9 1 1 0 1 0 0 0 0 Engine Fuel Pressure X0 3 5 1 1 0 1 0 0 0 0 Own Aircraft Magnetic Heading X0 3 8 1 1 0 1 0 0 0 0 Magnetic Heading X0 4 D 1 1 0 1 0 0 0 0 Density - Tank X0 5 A 1 1 0 1 0 0 0 0 Fuel Quantity Act 3 X0 5 6 1 1 0 1 0 0 0 0 Magnetic Heading X0 6 0 1 1 0 1 0 0 0 0 Magnetic Heading X0 0 2 1 1 0 1 0 0 0 1 Drift Angle X0 0 4 1 1 0 1 0 0 0 1 Drift Angle X0 0 5 1 1 0 1 0 0 0 1 Drift Angle X0 2 9 1 1 0 1 0 0 0 1 Engine Fuel Temperature X0 3 8 1 1 0 1 0 0 0 1 Drift Angle X0 5 6 1 1 0 1 0 0 0 1 Drift Angle X0 6 0 1 1 0 1 0 0 0 1 Drift Angle X1 0 A 1 1 0 1 0 0 0 1 Exhaust gas Temperature (Total) X1 0 B 1 1 0 1 0 0 0 1 Exhaust gas Temperature (Total) X

1 1 0 1 0 0 0 1 System Address label for Autothrottle Computer X See Attachment 110 0 2 1 1 0 1 0 0 1 0 Flight Path Angle X0 0 4 1 1 0 1 0 0 1 0 Flight Path Angle X0 0 5 1 1 0 1 0 0 1 0 Flight Path Angle X0 2 9 1 1 0 1 0 0 1 0 Engine Nacelle Temperature X0 3 8 1 1 0 1 0 0 1 0 Flight Path Angle X0 5 6 1 1 0 1 0 0 1 0 Flight Path Angle X0 6 0 1 1 0 1 0 0 1 0 Flight Path Angle X1 0 A 1 1 0 1 0 0 1 0 Total Compressor Discharge Temperature X1 0 B 1 1 0 1 0 0 1 0 Total Compressor Discharge Temperature X

1 1 0 1 0 0 1 0 System Address Label for FCC 1 X See Attachment 11

3 1 7

3 2 0

3 2 2

3 2 1

3 1 5

3 1 6




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 0 2 1 1 0 1 0 0 1 1 Geometric Altitude X0 0 4 1 1 0 1 0 0 1 1 Flight Path Acceleration X 6-270 0 5 1 1 0 1 0 0 1 1 Flight Path Acceleration X0 3 8 1 1 0 1 0 0 1 1 Flight Path Acceleration X0 5 6 1 1 0 1 0 0 1 1 Geometric Altitude X0 6 0 1 1 0 1 0 0 1 1 Geometric Altitude X1 0 A 1 1 0 1 0 0 1 1 Variable Stator Vane Position X1 0 B 1 1 0 1 0 0 1 1 Variable Stator Vane Position X

1 1 0 1 0 0 1 1 System Address Label for FCC 2 X See Attachment 110 0 4 1 1 0 1 0 1 0 0 Pitch Angle X0 0 5 1 1 0 1 0 1 0 0 Pitch Angle X0 2 5 1 1 0 1 0 1 0 0 Pitch Angle X0 3 8 1 1 0 1 0 1 0 0 Pitch Angle X0 4 D 1 1 0 1 0 1 0 0 Tank VSO Quantity X0 5 A 1 1 0 1 0 1 0 0 Effective Pitch Angle X1 0 A 1 1 0 1 0 1 0 0 Selected Fuel Metering Valve Position X1 0 B 1 1 0 1 0 1 0 0 Selected Fuel Metering Valve Position X1 1 4 1 1 0 1 0 1 0 0 Effective Pitch Angle X

1 1 0 1 0 1 0 0 System Address Label for FCC 3 X See Attachment 110 0 4 1 1 0 1 0 1 0 1 Roll Angle X0 0 5 1 1 0 1 0 1 0 1 Roll Angle X0 1 A 1 1 0 1 0 1 0 1 Engine Control Trim Feedback X0 2 5 1 1 0 1 0 1 0 1 Roll Angle X0 2 F 1 1 0 1 0 1 0 1 Stator Vane Feedback X0 3 8 1 1 0 1 0 1 0 1 Roll Angle X0 3 F 1 1 0 1 0 1 0 1 Stator Vane Feedback X0 5 A 1 1 0 1 0 1 0 1 Effective Roll Angle X1 0 A 1 1 0 1 0 1 0 1 Selected Fuel Metering Vane Position X1 0 B 1 1 0 1 0 1 0 1 Selected Fuel Metering Vane Position X1 1 4 1 1 0 1 0 1 0 1 Effective Roll Angle X

1 1 0 1 0 1 0 1 System Address Label for APU X See Attachment 110 0 4 1 1 0 1 0 1 1 0 Body Pitch Rate X0 0 5 1 1 0 1 0 1 1 0 Body Pitch Rate X0 3 8 1 1 0 1 0 1 1 0 Body Pitch Rate X0 4 D 1 1 0 1 0 1 1 0 Uplift Quantity X0 5 A 1 1 0 1 0 1 1 0 Maintenance Word X1 0 A 1 1 0 1 0 1 1 0 Compressor Discharge Static Pressure X1 0 B 1 1 0 1 0 1 1 0 Compressor Discharge Static Pressure X

1 1 0 1 0 1 1 0 System Address Label for APU Controller X See Attachment 110 0 4 1 1 0 1 0 1 1 1 Body Roll Rate X0 0 5 1 1 0 1 0 1 1 1 Body Roll Rate X0 3 8 1 1 0 1 0 1 1 1 Body Roll Rate X0 4 D 1 1 0 1 0 1 1 1 Uplift Density X1 0 A 1 1 0 1 0 1 1 1 Fuel Metering Valve Position X1 0 B 1 1 0 1 0 1 1 1 Fuel Metering Valve Position X

1 1 0 1 0 1 1 1 SAL Mode Control Panel (MCP) X0 0 4 1 1 0 1 1 0 0 0 Body Yaw Rate X0 0 5 1 1 0 1 1 0 0 0 Body Yaw Rate X0 2 F 1 1 0 1 1 0 0 0 HC/TC Cooling Valve Position Feedback X0 3 8 1 1 0 1 1 0 0 0 Body Yaw Rate X0 3 F 1 1 0 1 1 0 0 0 HC/TC Cooling Valve Position Feedback X1 0 A 1 1 0 1 1 0 0 0 Selected HPT Clearance Valve Postion X1 0 B 1 1 0 1 1 0 0 0 Selected HPT Clearance Valve Postion X

1 1 0 1 1 0 0 0 System Address Label for FMC 3 X See Attachment 110 0 4 1 1 0 1 1 0 0 1 Body Longitudinal Acceleration X0 0 5 1 1 0 1 1 0 0 1 Body Longitudinal Acceleration X0 2 F 1 1 0 1 1 0 0 1 LTC Cooling Valve Position Feedback X0 3 8 1 1 0 1 1 0 0 1 Body Longitudinal Acceleration X0 3 F 1 1 0 1 1 0 0 1 LTC Cooling Valve Position Feedback X1 0 A 1 1 0 1 1 0 0 1 Selected LPT Clearance Valve Position X1 0 B 1 1 0 1 1 0 0 1 Selected LPT Clearance Valve Position X

1 1 0 1 1 0 0 1 System Address Label for ATC Transponder X See Attachment 11

3 2 7

3 3 0

3 3 1

3 2 3

3 2 5

3 2 6

3 2 4




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 0 4 1 1 0 1 1 0 1 0 Body Lateral Acceleration X0 0 5 1 1 0 1 1 0 1 0 Body Lateral Acceleration X0 2 F 1 1 0 1 1 0 1 0 A/O Heat Exchanger Valve Postion Feedback X0 3 8 1 1 0 1 1 0 1 0 Body Lateral Acceleration X0 3 F 1 1 0 1 1 0 1 0 A/O Heat Exchanger Valve Postion Feedback X

1 1 0 1 1 0 1 0 System Address Label for DADC X See Attachment 110 0 4 1 1 0 1 1 0 1 1 Body Normal Acceleration X0 0 5 1 1 0 1 1 0 1 1 Body Normal Acceleration X0 2 F 1 1 0 1 1 0 1 1 Acceleration Fuel Flow Limit X0 3 8 1 1 0 1 1 0 1 1 Body Normal Acceleration X0 3 F 1 1 0 1 1 0 1 1 Acceleration Fuel Flow Limit X0 0 4 1 1 0 1 1 1 0 0 Platform Heading X0 0 5 1 1 0 1 1 1 0 0 Platform Heading X0 2 F 1 1 0 1 1 1 0 0 Fuel Flow Command X0 3 8 1 1 0 1 1 1 0 0 Platform Heading X0 3 F 1 1 0 1 1 1 0 0 Fuel Flow Command X

1 1 0 1 1 1 0 0 CTU - System Address Label X See Attachment 110 0 2 1 1 0 1 1 1 0 1 Track Angle Rate X0 0 4 1 1 0 1 1 1 0 1 Track Angle Rate X0 0 5 1 1 0 1 1 1 0 1 Track Angle Rate X0 2 F 1 1 0 1 1 1 0 1 2.5 Bld Actuator Postion X0 3 8 1 1 0 1 1 1 0 1 Track Angle Rate X0 3 F 1 1 0 1 1 1 0 1 2.5 Bld Actuator Postion X0 5 6 1 1 0 1 1 1 0 1 Track Angle Rate X0 6 0 1 1 0 1 1 1 0 1 Track Angle Rate X1 0 A 1 1 0 1 1 1 0 1 Selected Variable Bleed Valve Position X1 0 B 1 1 0 1 1 1 0 1 Selected Variable Bleed Valve Position X0 0 2 1 1 0 1 1 1 1 0 Maximum Climb Angle X0 0 4 1 1 0 1 1 1 1 0 Inertial Pitch Rate X0 0 5 1 1 0 1 1 1 1 0 Inertial Pitch Rate X0 1 A 1 1 0 1 1 1 1 0 Engine Torque X0 2 F 1 1 0 1 1 1 1 0 N2 Corrected to Sta. 2.5 X0 3 8 1 1 0 1 1 1 1 0 Inertial Pitch Rate X0 3 F 1 1 0 1 1 1 1 0 N2 Corrected to Sta. 2.5 X1 0 A 1 1 0 1 1 1 1 0 Variable Bleed Value Position X1 0 B 1 1 0 1 1 1 1 0 Variable Bleed Value Position X0 0 2 1 1 0 1 1 1 1 1 EPR - Required for Level Flight X0 0 2 1 1 0 1 1 1 1 1 N1 - Required for Level Flight X0 0 4 1 1 0 1 1 1 1 1 Inertial Roll Rate X0 0 5 1 1 0 1 1 1 1 1 Inertial Roll Rate X0 1 A 1 1 0 1 1 1 1 1 Engine Rating X0 3 8 1 1 0 1 1 1 1 1 Inertial Roll Rate X1 0 A 1 1 0 1 1 1 1 1 HPT Clearance Valve Position X1 0 B 1 1 0 1 1 1 1 1 HPT Clearance Valve Position X0 0 3 1 1 1 0 0 0 0 0 EPR Actual X0 0 4 1 1 1 0 0 0 0 0 Inertial Yaw Rate X0 0 4 1 1 1 0 0 0 0 0 Track Angle Rate X0 0 5 1 1 1 0 0 0 0 0 Inertial Yaw Rate X0 1 A 1 1 1 0 0 0 0 0 EPR Actual X0 2 9 1 1 1 0 0 0 0 0 EPR Actual (Engine Direct) X0 2 D 1 1 1 0 0 0 0 0 EPR Actual X0 2 F 1 1 1 0 0 0 0 0 EPR Actual X0 3 3 1 1 1 0 0 0 0 0 EPR Actual X0 3 F 1 1 1 0 0 0 0 0 EPR Actual X1 3 A 1 1 1 0 0 0 0 0 N1 Take Off X1 4 0 1 1 1 0 0 0 0 0 Pressure Ratio (Pt/Ps) X

1 1 1 0 0 0 0 0 HF DATA Radio/Data #1 - System Address Label X See Attachment 11

3 3 7

3 4 0

3 3 3

3 3 4

3 3 6

3 3 5

3 3 2




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 0 2 1 1 1 0 0 0 0 1 Target N1 X0 0 3 1 1 1 0 0 0 0 1 N1 Command X0 0 3 1 1 1 0 0 0 0 1 EPR Command X0 0 4 1 1 1 0 0 0 0 1 Grid Heading X0 1 A 1 1 1 0 0 0 0 1 N1 Command X0 1 A 1 1 1 0 0 0 0 1 EPR Command X0 2 9 1 1 1 0 0 0 0 1 N1 Command (Engine) X0 2 9 1 1 1 0 0 0 0 1 EPR Command (Engine) X0 2 F 1 1 1 0 0 0 0 1 N1 Command X0 2 F 1 1 1 0 0 0 0 1 EPR Command X0 3 8 1 1 1 0 0 0 0 1 Grid Heading X0 3 F 1 1 1 0 0 0 0 1 EPR Command X0 4 D 1 1 1 0 0 0 0 1 I/O S/W REV 1&2 X1 0 A 1 1 1 0 0 0 0 1 Command Fan Speed X1 0 B 1 1 1 0 0 0 0 1 Command Fan Speed X1 3 A 1 1 1 0 0 0 0 1 N1 Reference X1 4 0 1 1 1 0 0 0 0 1 Pressure Ratio (Ps/Pso) X0 0 2 1 1 1 0 0 0 1 0 N1 Bug Drive X0 0 3 1 1 1 0 0 0 1 0 N1 Limit X0 0 3 1 1 1 0 0 0 1 0 EPR Limit X0 1 A 1 1 1 0 0 0 1 0 N1 Maximum X0 1 A 1 1 1 0 0 0 1 0 EPR Maximum X0 2 9 1 1 1 0 0 0 1 0 N1 Limit (TCC) X0 2 9 1 1 1 0 0 0 1 0 EPR Limit (TOC) X0 2 F 1 1 1 0 0 0 1 0 Maximum Available EPR X0 3 B 1 1 1 0 0 0 1 0 N1 Limit X0 3 B 1 1 1 0 0 0 1 0 EPR Limit X0 3 F 1 1 1 0 0 0 1 0 Maximum Available EPR X0 4 D 1 1 1 0 0 0 1 0 S/W Rev-Tank X1 0 A 1 1 1 0 0 0 1 0 Maximum Allowed Fan Speed X1 0 B 1 1 1 0 0 0 1 0 Maximum Allowed Fan Speed X1 4 0 1 1 1 0 0 0 1 0 Air Density Ratio X0 0 3 1 1 1 0 0 0 1 1 N1 Derate X0 0 3 1 1 1 0 0 0 1 1 EPR Rate X0 1 A 1 1 1 0 0 0 1 1 N1 Demand X1 0 A 1 1 1 0 0 0 1 1 N1 Command vs. TLA X1 0 B 1 1 1 0 0 0 1 1 N1 Command vs. TLA X0 1 A 1 1 1 0 0 1 0 0 N2 X0 1 C 1 1 1 0 0 1 0 0 N2 X0 2 9 1 1 1 0 0 1 0 0 N2 X0 2 F 1 1 1 0 0 1 0 0 N2 X0 3 3 1 1 1 0 0 1 0 0 N2 X0 3 F 1 1 1 0 0 1 0 0 N2 X0 4 D 1 1 1 0 0 1 0 0 Fuel Discretes X0 D 0 1 1 1 0 0 1 0 0 N2 X1 0 A 1 1 1 0 0 1 0 0 Selected Actual Core Speed X1 0 B 1 1 1 0 0 1 0 0 Selected Actual Core Speed X1 3 A 1 1 1 0 0 1 0 0 N2 Speed X

1 1 1 0 0 1 0 0 HF DATA Radio/Data #2 - System Address Label X See Attachment 110 0 2 1 1 1 0 0 1 0 1 NDB Effectivity X0 1 A 1 1 1 0 0 1 0 1 Exhaust Gas Temperature X0 1 C 1 1 1 0 0 1 0 1 Exhaust Gas Temperature X0 2 9 1 1 1 0 0 1 0 1 Exhaust Gas Temperature X0 2 F 1 1 1 0 0 1 0 1 Exhaust Gas Temperature X0 3 3 1 1 1 0 0 1 0 1 Exhaust Gas Temperature X0 3 F 1 1 1 0 0 1 0 1 Exhaust Gas Temperature X0 4 D 1 1 1 0 0 1 0 1 Discretes Status 1&3 X0 D 0 1 1 1 0 0 1 0 1 EGT X1 0 A 1 1 1 0 0 1 0 1 Selected Exhaust Gas Temperature (Total) X1 0 B 1 1 1 0 0 1 0 1 Selected Exhaust Gas Temperature (Total) X1 3 A 1 1 1 0 0 1 0 1 EGT Trimmed X

3 4 3

3 4 4

3 4 5

3 4 1

3 4 2




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


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

3 4 7

3 5 0

3 4 6




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


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

3 5 3

3 5 4

3 5 6

3 5 5

3 5 1

3 5 2




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 0 2 1 1 1 0 1 1 1 1 ISO Alphabet #5 Message X 6-30 1 7 1 1 1 0 1 1 1 1 ISO Alphabet #5 Message X0 2 4 1 1 1 0 1 1 1 1 ISO Alphabet #5 Message X0 3 5 1 1 1 0 1 1 1 1 TCAS Intruder Data File X0 3 7 1 1 1 0 1 1 1 1 ISO Alphabet #5 Message X0 3 D 1 1 1 0 1 1 1 1 BB Vibration X0 4 D 1 1 1 0 1 1 1 1 Maintenance Data FQIS 2-3 X0 5 6 1 1 1 0 1 1 1 1 ISO Alphabet #5 Message0 6 0 1 1 1 0 1 1 1 1 ISO Alphabet #5 Message0 0 2 1 1 1 1 0 0 0 0 Flight Information X 6-330 0 4 1 1 1 1 0 0 0 0 Potential Vertical Speed X0 0 5 1 1 1 1 0 0 0 0 Potential Vertical Speed X0 3 8 1 1 1 1 0 0 0 0 Potential Vertical Speed X0 3 D 1 1 1 1 0 0 0 0 N1 Rotor Imbalance Angle X0 5 6 1 1 1 1 0 0 0 0 Flight Information X0 6 0 1 1 1 1 0 0 0 0 Flight Information X1 0 A 1 1 1 1 0 0 0 0 Throttle Rate of Change X1 0 B 1 1 1 1 0 0 0 0 Throttle Rate of Change X1 4 2 1 1 1 1 0 0 0 0 RAIM Status Word X

1 1 1 1 0 0 0 0 ACESS System Address Label X See Attachment 110 0 4 1 1 1 1 0 0 0 1 Altitude (Inertial) X0 0 5 1 1 1 1 0 0 0 1 Altitude (Inertial) X0 3 8 1 1 1 1 0 0 0 1 Altitude (Inertial) X0 3 D 1 1 1 1 0 0 0 1 LPT Rotor Imbalance Angle (737 only) X1 0 A 1 1 1 1 0 0 0 1 Derivative of Thrust vs. N1 X1 0 B 1 1 1 1 0 0 0 1 Derivative of Thrust vs. N1 X

1 1 1 1 0 0 0 1 EFIS System Address Label X See Attachment 110 0 4 1 1 1 1 0 0 1 0 Along Track Horizontal Acceleration X0 3 8 1 1 1 1 0 0 1 0 Along Track Horizontal Acceleration X1 0 A 1 1 1 1 0 0 1 0 Derivative of Thrust vs. TLA X1 0 B 1 1 1 1 0 0 1 0 Derivative of Thrust vs. TLA X1 1 5 1 1 1 1 0 0 1 0 Range Rate X

1 1 1 1 0 0 1 0 System Address Label for PSS X See Attachment 110 0 4 1 1 1 1 0 0 1 1 Cross Track Acceleration X0 3 8 1 1 1 1 0 0 1 1 Cross Track Acceleration X1 0 A 1 1 1 1 0 0 1 1 Corrected Thrust X1 0 B 1 1 1 1 0 0 1 1 Corrected Thrust X

1 1 1 1 0 0 1 1 System Address Label for CSS X See Attachment 110 0 4 1 1 1 1 0 1 0 0 Vertical Acceleration X0 0 5 1 1 1 1 0 1 0 0 Vertical Acceleration X0 3 8 1 1 1 1 0 1 0 0 Vertical Acceleration X1 3 A 1 1 1 1 0 1 0 0 N1 APR Rating X

1 1 1 1 0 1 0 0 System Address Label for AES X See Attachment 110 0 4 1 1 1 1 0 1 0 1 Inertial Vertical Velocity (EFI) X0 0 5 1 1 1 1 0 1 0 1 Inertial Vertical Velocity (EFI) X0 3 8 1 1 1 1 0 1 0 1 Inertial Vertical Velocity (EFI) X1 3 A 1 1 1 1 0 1 0 1 N1 Max Reverse X

1 1 1 1 0 1 0 1 Engine Indication Unit - System Address Label X See Attachment 110 0 4 1 1 1 1 0 1 1 0 North-South Velocity X 6-2-10 3 8 1 1 1 1 0 1 1 0 North-South Velocity X1 3 A 1 1 1 1 0 1 1 0 IGV Position X

1 1 1 1 0 1 1 0 System Address Label for Multicast X See Attachment 110 0 4 1 1 1 1 0 1 1 1 East-West Velocity X0 3 8 1 1 1 1 0 1 1 1 East-West Velocity X1 3 A 1 1 1 1 0 1 1 1 EGV Request X

1 1 1 1 0 1 1 1 System Address Label for Bridge X See Attachment 11

3 6 7

3 6 3

3 6 4

3 6 6

3 6 5

3 5 7

3 6 2

3 6 1

3 6 0




Code No. (Octal)

Eqpt. ID (Hex)

0 0 0


Att. 6Parameter


0 0 4 1 1 1 1 1 0 0 0 g X0 0 5 1 1 1 1 1 0 0 0 g X0 0 B 1 1 1 1 1 0 0 0 GNSS Height WGS-84 (HAE) X0 2 5 1 1 1 1 1 0 0 0 Decision Height Selected (EFI) X0 C 5 1 1 1 1 1 0 0 0 Decision Height Selected (EFI) X0 0 0 1 1 1 1 1 0 0 1 General Aviation Equipment Identifier X See Attachment 9B0 0 5 1 1 1 1 1 0 1 0 Wind Direction - Magnetic X1 0 A 1 1 1 1 1 0 1 0 Actual Fan Speed X1 0 B 1 1 1 1 1 0 1 0 Actual Fan Speed X

1 1 1 1 1 0 1 0 Cabin Terminal #3 - System Address Label X See Attachment 110 0 5 1 1 1 1 1 1 0 0 North-South Velocity - Magnetic X1 0 A 1 1 1 1 1 1 0 0 Actual Core Speed X1 0 B 1 1 1 1 1 1 0 0 Actual Core Speed X

1 1 1 1 1 1 0 0 Cabin Terminal #4 - System Address Label X See Attachment 110 0 5 1 1 1 1 1 1 0 0 East-West Velocity - Magnetic X1 0 A 1 1 1 1 1 1 0 0 Left Thrust Reverser Position X1 0 B 1 1 1 1 1 1 0 0 Left Thrust Reverser Position X

1 1 1 1 1 1 0 0 Cabin Terminal #1 - System Address Label X See Attachment 110 0 4 1 1 1 1 1 1 0 1 Along Heading Acceleration X0 0 5 1 1 1 1 1 1 0 1 Along Heading Acceleration X0 3 3 1 1 1 1 1 1 0 1 Spare DC1 X0 3 8 1 1 1 1 1 1 0 1 Along Heading Acceleration X1 0 A 1 1 1 1 1 1 0 1 Right Thrust Reverser Position X1 0 B 1 1 1 1 1 1 0 1 Right Thrust Reverser Position XX X X 1 1 1 1 1 1 0 1 GPS Differential Correction Word A X

1 1 1 1 1 1 0 1 Cabin Terminal #2 - System Address Label X See Attachment 110 0 4 1 1 1 1 1 1 1 0 Cross Heading Acceleration X0 0 5 1 1 1 1 1 1 1 0 Cross Heading Acceleration X0 3 3 1 1 1 1 1 1 1 0 Spare DC2 X0 3 8 1 1 1 1 1 1 1 0 Cross Heading Acceleration XX X X 1 1 1 1 1 1 1 0 GPS Differential Correction Word B X0 3 0 1 1 1 1 1 1 1 1 Equipment Identification X XX X X 1 1 1 1 1 1 1 1 Equipment Identification X X 6-17/Note 1

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

Notes[1] XXX or YYY is applicable to all Equipment IDs.

3 7 1

3 7 0

3 7 7

3 7 2

3 7 3

3 7 4

3 7 5

3 7 6


ATTACHMENT 1-2EQUIPMENT CODES

c-5

EquipID

(Hex)

EquipmentType

EquipID

(Hex)

EquipmentType

000 Not Used 03A Propulsion Discrete Interface Unit c-11001 Flight Control Computer (701) 03B Autopilot Buffer Unit c-6002 Flight Management Computer (702) 03C Tire Pressure Monitoring System c-8003 Thrust Control Computer (703) 03D Airborne Vibration Monitor (737/757/767) c-9004 Inertial Reference System (704) 03E Center of Gravity Control Computer005 Attitude and Heading Ref. System (705) 03F Full Authority EEC-B

c-7

006 Air Data System (706) 040 Cockpit Printer (740) c-11007 Radio Altimeter (707) 041 Satellite Data Unit008 Airborne Weather Radar (708) 042009 Airborne DME (709) 043

c-5 00A FAC (A310) 044c-10 00B Global Positioning System (743) 045

00C 046 CTUc-7 00D AIDS Data Management Unit 047 Digital Flight Data Recorder

c-14

00E 04800F 049010 Airborne ILS Receiver (710) 04A Landing Gear Position Interface Unit011 Airborne VOR Receiver (711) 04B Main Electrical System Controller012 Airborne ADF System (712) 04C Emergency Electrical System Controller

c-9

013 04D Fuel Qty. Indicating System (757/767)014 04E Fuel Qty. Indicating System (747)

c-10

015 04F016 Airborne VHF COM receiver (716) 050 VDR (750)

c-14

017 DEFDARS-AIDS (717) 051018 ATC Transponder (718) 052019 Airborne HF/SSB System (719) 053 HF Data Unit

c-5 01A Electronic Supervisory Control [1] 05401B Digital Slat/Flap Computer (A310) 055 Multi-Mode Receiver (MMR) (755)01C Engine Parameter Digitizer (Engine) 056 GNSS Navigation Landing Unit (GNLU)(756)01D A/P & F/D Mode Control Panel (757/767) 057 Cockpit Voice Recorder (CVR) (757)01E Performance Data Computer (Boeing 737) 058 Communication Management Unit Mark 2 (758)

c-16

01F Fuel Quantity Totalizer 059020 DFS System (720) 05A Fuel Quan. Indicating System (A-320/A-321)021 05B Cargo Smoke Detection Unit (A-320)022 05C Cabin Pressure Unit (A-320)023 Ground Prox. Warning System (723) 05D Zone Controller (A-320)024 ACARS (724) 05E Cargo Heat (A-320)025 Electronic Flt. Instruments (725) 05F CIDS (A-320)

c-10

026 Flight Warning Computer (726) 060 GNSS Navigation Unit (GNU) (760)027 Microwave Landing System (727) 061 Satellite Terminal Unit (STU) (761)

c-16

028 062029 ADDCS (729) and EICAS 06302A Thrust Management Computer 06402B Perf. Nav. Computer System (Boeing 737) 065

c-6 02C Digital Fuel Gauging System (A310) 066c-5 02D EPR Indicator (Boeing 757) 067c-6 02E Land Rollout CU/Landing C & LU 068

02F Full Authority EEC-A 069c-7

030 Airborne Separation Assurance System 06A AMU (A-320)031 Chronometer (731) 06B Battery Charge Limiter (A-320)

c-10

032 Pass. Entertainment Tape Reproducer (732) 06C Flt. Cont. Data Concentrator (A-320)033 Propulsion Multiplexer (PMUX)(733) 06D Landing Gear Prox. Control (A-320)c-6034 Fault Isolation & Detection System (734) 06E Brake Steering Unit (A-320)035 TCAS (735) 06F Bleed Air (A-320)036 Radio Management System (736) 070037 Weight and Balance System (737) 071038 ADIRS (738) 072

c-10

039 MCDU (739) 073

[1] “Electronic Engine Control” and “Power Management Control” are two other names for equipment identified by “1A”.



EquipID

(Hex)

EquipmentType

EquipID

(Hex)

EquipmentType

074 0B0 Airborne ILS Controller (710)075 0B1 Airborne VOR Controller (711)076 0B2 Airborne ADF Controller (712)077 0B3079 0B407A APU Engine Control Unit (A-320) 0B507B Engine Interface Unit (A-320) 0B6 VHF COM Controller (716)07C FADEC Channel A (A-320) 0B707D FADEC Channel B (A-320) 0B8 ATC Transponder Controller (716)07E Centralized Fault Data Interface Unit 0B9 HF/SSB System Controller (719)

c-10

07F Fire Detection Unit (A-320) 0BA Power Supply Module (B-747-400) c-11080 0BB Flap Control Unit (B-747-400) c-16081 Flap Slat Electronics Unit (B767-400)082 0BC Fuel System Interface Card (B-747-400)083 0BD Hydraulic Quantity Monitor Unit (B-747-400)084 0BE Hydraulic Interface Module (B-747-400)085 0BF Window Heat Control Unit (B-747-400)

c-11

086 0C0087 0C1088 0C2 PVS Control Unit c-11089 0C3 GPWS Controller (723) c-1008A Window Heat Computer (A-320) 0C408B Probes Heat Computer (a-320) 0C5 EFI Controller (725)08C Avionics Cooling Computer (A-320) 0C6

c-10

08D Fuel Flow Indicator (B-747) 0C7 MLS Controller08E Surface Position Digitizer (B-747-400) 0C8

c-14c-11

08F Vacuum System Controller 0C9090 0CA Brake Temperature Monitor Unit (B-747-400)091 0CB Autostart (B-747-400)093 0CC Brake System Control Unit (B-747-400)094 0CD Pack Temperature Controller (B-747-400)095 0CE EICAS/EFIC Interface Unit (B-747-400)096 0CF Para Visual Display Computer (B-747-400)097 0D0 Engine Instrument System (737)

c-11

098 0D1099 0D209A 0D3 Thermal Monitoring Unit (General)09B 0D409C 0D5 TCAS Control Panel

c-14

09D 0D609E 0D7

c-10

09F 0D80A0 0D90A1 FCC Controller (701) 0DA Prox. Switch Electronics Unit (B-747-400)0A2 FMC Controller (702) 0DB APU Controller (B-747-400)0A3 Thrust Rating Controller (703) 0DC Zone Temperature Controller (B-747-400)0A4 IRS Controller (704) 0DD Cabin Pressure Controller (B-747-400)0A5 0DE Windshear Computer (Sperry)0A6 0DF Equipment Cooling Card (B-747-400)

c-11

0A7 0E0 Crew Rest Temp. Controller (747-400)0A8 Airborne WXR Controller (708) 0E10A9 Airborne DME Controller (709) 0E20AA Generator Control Unit (A-320) 0E30AB Air Supply Control & Test Unit (B-747-400) 0E4c-110AC Bus Control Unit (B-747-400) 0E5

c-10 0AD ADIRS Air Data Module 0E60AE Yaw Damper Module (B-747-400) 0E7

c-110AF Stabilizer Trim Module (B-747-400) 0E8



EquipID

(Hex)

EquipmentType

EquipID

(Hex)

EquipmentType

0E9 123 Ground Power Control Unit (A-330/A-340)0EA Misc. Environment Control (B-747) 124 Fuel Management Computer (A-330/A-340)0EB Fuel Jettison Control Card (B-747) 125 Center of Gravity Fuel Control Comp.(A-330/A-340)0EC Advance Cabin Entertainment Serv. Sys. 126 Circuit breakers Monitoring Unit (A-330/A-340)0ED Fuel System Controller (MD-11) 127 Electrical Contractor Management Unit (A-330/A-340)0EE Hydraulic System Controller (MD-11) 128 Hydraulic Electrical Generator Control Unit (A-330/A-340)

c-11

0EF Environmental System Controller (MD-11) 129 Hydraulic System Monitoring Unit (A-330/A-340)

c-12

0F0 12A Cargo Bay Conditioning Card (B-747)0F1 12B Predictive Windshear System Sensor

c-11

0F2 12C Angle of Attack Sensor c-140F3 12D Logic Drive Control Computer (B747/B767)0F4 12E Cargo Control Logic Unit (B767)0F5 12F Cargo Electronics Interface Unit (B767)0F6 130 Load Management Unit (LMU) Airbus

c-16

0F7 1310F8 1320F9 1330FA Misc. System controller (MD-11) 1340FB Anti-Skid System (MD-11) 1350FC Cabin Pressure Control Sys. (MD-11) 136 Audio Management System c-110FD Air Condition Control System (MD-11) 1370FE Pneumatic Control System (MD-11) 138

c-11

0FF Manifold Failure Detection System (MD-11) 139100 13A Full Authority Engine Control (P&W) c-14101 13B Audio Entertainment System (AES) Controller (Boeing) c-16102 13C Boarding Music Machine (B-777)103 13D Passenger In Flight Info Unit (Airshow)104 13E Video Interface Unit (B-777)

c-14

105 13F Camera Interface Unit (A340/B777)106 140 Supersonic Air Data Computer

c-16

107 141 Satellite RF Unit c-11108 Electronic Engine Control (EEC) Channel A (B737-700) 142 ADS-B Link Display Processor Unit (LPDU)

c-16109 Elect Eng Control (EEC) Channel B (B737-700) 143 Vertical/Horizontal Gyro

c-16

10A Full Authority Engine Control A (GE) 14410B Full Authority Engine Control B (GE) 14510C APU Controller 14610D Data Loader 14710E Fire Detection Unit (MD-11) 148

c-11

10F Auto Brake Unit (MD-11) 149101 Multiplexer PES (A-320) 14A111 14B

c-14 112 TACAN Adapter Unit (TAU) 14C113 Stall Warning Card (B-747-400) 14D114 Fuel Unit Management System (A330/A340) 14E115 TACAN 14F116 Eng Interface Vibration Monitoring Unit (A-330/A-340) 150 AIMS Gen. Pur. Bus #1 (B-777)117 Engine Control Unit Channel A (A-330/A-340) 151 AIMS Gen. Pur. Bus #2 (B-777)118 Engine Control Unit Channel B (A-330/A-340) 152 AIMS Digital Comm. Mgmt. (B-777)119 Centralized Maintenance Computer (A-330/A-340) 153 AIMS Gen. Pur. Bus #3 (B-777)

c-12

11A Multi-Disk Drive Unit (A-330/A-340) 154 Central Maintenance Computer (B-777)11B 155 AIMS EFIS Control Panel (B-777)11C 156 AIMS Display Unit (B-777)11D 157 AIMS Cursor Control Device (B-777)

c-14

11E 158 AIMS General Purpose Bus #4 c-1611F 159120 15A Flight Data Interface Unit (A-330/A-340)121 15B Flight Control Unit (A-330/A-340)

c-16 122 Ground Auxiliary Power Unit (A320/319/321) 15C Flight Control Primary Computer (A-330/A-340)c-12



EquipID

(Hex)

EquipmentType

EquipID

(Hex)

EquipmentType

15D Flight Control Secondary Computer (A-330/A-340) 19F Cade Environment Systemc-12

15E Flight Mgmt Guidance Env Comp (A-330/A-340) 200 Versatile Integrated Avionics Unit (B717/MD-10)15F 201 Electronic Spoiler Control Unit (B717)160 Special Fuel Quan. Sys. (Boeing) 202 Brake Control Unit (B717)161 203 Pneumatic Overheat Detection Unit (B717)162 204 Proximity Switch Electronics Unit (B717)163 205 APU Electronic Control Unit (B717)164 206 Aircraft Interface Unit (MD-10)165 207 Fuel Quantity Gauging Unit (MD-10)

c-16

166167 Air Traffic Service Unit (Airbus)168 Integ Standby Instr System (A340/330,A320/319/321)c-16169 Data Link Control and Display Unit (A340/330)16A Display Unit (A-330/A-340)16B Display Management Computer (A-330/A-340) 241 High Power Amplifier c-1116C Head-Up Display Computer (A-330/A-340)16D ECAM Control Panel (A-330/A-340)

c-12

16E Clock (A-330/A-340)16F Cabin Interphone System (B-777)

c-14170 Radio Tuning Panel (B-777)171172 341 Satellite ACU c-1117317417517617717817917A Cabin Ventilation Controller (A-330/A-340)17B Smoke Detection Control Unit (A-330/A-340)c-1217C Proximity Sensor Control Unit (A-330/A-340)17D17E17F18018118218318418518618718818918A Audio Control Panel (A-330/A-340)18B Cockpit Voice recorder (A-330/A-340)18C Passenger Entertainment Sys Main MUX (A330/A340)18D Passenger Entertainment Sys Audio Repro.(A330/A340)18E Pre-recorded Announcement Music Repro (A-330/A340)

c-11

18F Video Control Unit (A-330/A-340)


ATTACHMENT 2DATA STANDARDS

TABLE 1 - BCD DATA

LabelEqptID

(Hex)

ParameterName Units Range

(Scale)SigBits

PosSense

Reso-lution

MinTransitInterval(msec) 2

MaxTransitInterval(msec) 2

MaxTrans-

portDelay

(msec) 3

Notes

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

0 0 2 0 0 2 Time to Go Min 0-399.9 4 0.1 100 2000 5 6 Time to Go Min 0-399.9 4 0.1 100 2000 6 0 Time to Go Min 0-399.9 4 0.1 100 2001 1 5 Time to Station Min 0-399.9 4 0.1 50 50

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

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

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

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

0 1 2 0 0 2 Ground Speed Knots 0-7000 4 1.0 250 5000 0 4 Ground Speed Knots 0-7000 4 1.0 250 5000 4 D Qty-LD SEL (LB) Lbs. 0-79999 5 1.00 0 5 Ground Speed Knots 0-7000 4 1.0 250 5000 2 5 Ground Speed Knots 0-7000 4 1.0 125 2500 3 8 Ground Speed Knots 0-7000 4 1.0 250 5000 5 6 Ground Speed Knots 0-7000 4 1.0 250 5000 6 0 Ground Speed Knots 0-7000 4 1.0 250 500

0 1 3 0 0 2 Track Angle - True Deg 0-359.9 4 0.1 250 5000 0 4 Track Angle - True Deg 0-359.9 4 0.1 250 5000 4 D Qty-Flt. Deck (LB) Lbs. 0-79999 5 1.00 3 8 Track Angle - True Deg 0-359.9 4 0.1 250 500

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

0 1 5 0 0 2 Wind Speed Knots 0-799 3 1.0 250 5000 0 4 Wind Speed Knots 0-799 3 1.0 250 5000 0 5 Wind Speed Knots 0-799 3 1.0 250 5000 3 8 Wind Speed Knots 0-799 3 1.0 250 500

0 1 6 0 0 4 Wind Direction - True Deg 0-359 3 1.0 250 5000 3 8 Wind Direction - True Deg 0-359 3 1.0 250 500

0 1 7 0 1 0 Selected Runway Heading Deg 0-359.9 4 0.1 167 3330 4 D Total-Flt. Deck (LB) Lbs. 0-79999 5 1.00 5 5 Selected Runway Heading Deg 0-359.9 4 0.10 A 0 Selected Runway Heading Deg 0-359.9 4 0.1 167 3330 B 0 Selected Runway Heading Deg 0-359.9 4 0.1 167 333

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

0 2 1 0 0 2 Selected EPR EPR 0-3 4 0.001 100 2000 0 2 Selected N1 RPM 0-3000 4 1 100 2000 2 0 Selected EPR EPR 0-3 4 0.001 100 2000 2 0 Selected N1 RPM 0-3000 4 1 100 2000 A 1 Selected EPR EPR 0-3 3 0.001 100 200



TABLE 1 - BCD DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense

Reso-lution



MaxTrans-

portDelay

(msec) 3

Notes

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

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

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

0 2 4 0 1 1 Selected Course #1 Deg 0-359 3 1.0 167 3330 2 0 Selected Course #1 Deg 0-359 3 1.0 167 3330 A 1 Selected Course #1 Deg 0-359 3 1.0 167 3330 B 1 Selected Course #1 Deg 0-359 3 1.0 167 333

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

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

0 2 7 0 0 2 TACAN Selected Course Deg 0-359 3 1.0 167 3330 1 1 Selected Course #2 Deg 0-359 3 1.0 167 3330 2 0 Selected Course #2 Deg 0-359 3 1.0 167 3330 4 D Total-Flt Deck (KG) Kg 0-79999 5 1.00 5 6 TACAN Selected Course Deg 0-359 3 1.0 167 3330 6 0 TACAN Selected Course (BCD) Deg 0-359 3 1.0 167 3330 A 1 Selected Course #2 Deg 0-359 3 1.0 167 3330 B 1 Selected Course #2 Deg 0-359 3 1.0 167 333

0 3 0 0 2 0 VHF COM Frequency See Chapter 3 100 2000 2 4 VHF COM Frequency See Chapter 3 100 2000 4 D TNK-LD SEL (KG) Kg 0-79999 5 1.00 B 6 VHF COM Frequency See Chapter 3 100 200

0 3 1 0 2 0 Beacon Transponder Code See Chapter 3 100 2000 B 8 Beacon Transponder Code See Chapter 3 100 200

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

0 3 3 0 0 2 ILS Frequency See Chapter 3 167 3330 1 0 ILS Frequency See Chapter 3 167 3330 2 0 ILS Frequency See Chapter 3 167 3330 5 6 ILS Frequency See Chapter 3 167 3330 6 0 ILS Frequency See Chapter 3 167 3330 B 0 ILS Frequency See Chapter 3 167 333

0 3 4 0 0 2 VOR/ILS Frequency See Chapter 3 167 3330 0 6 Baro Correction (mb) #3 mb 745-1050 5 0.1 62.5 1250 1 1 VOR/ILS Frequency See Chapter 3 167 3330 2 0 VOR/ILS Frequency See Chapter 3 167 3330 5 6 VOR/ILS Frequency See Chapter 3 167 3330 6 0 VOR/ILS Frequency #1 See Chapter 3 167 3330 B 0 VOR/ILS Frequency See Chapter 3 167 333

0 3 5 0 0 2 DME Frequency See Chapter 3 100 2000 0 6 Baro Correction (ins of Hg) #3 ins Hg 22-31 5 0.001 62.5 1250 0 9 DME Frequency See Chapter 3 100 2000 2 0 DME Frequency See Chapter 3 100 200



TABLE 1 - BCD DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense

Reso-lution



MaxTrans-

portDelay

(msec) 3

Notes

0 5 5 Paired DME Frequency MHz 108-135.9 4 0.050 5 6 DME Frequency See Chapter 3 100 2000 6 0 DME Frequency See Chapter 3 100 2000 A 9 DME Frequency See Chapter 3 100 200

0 3 6 0 0 2 MLS Frequency See Chapter 3 100 2000 2 0 MLS Frequency See Chapter 3 100 2000 5 5 MLS Channel Selection 500-600 3 10 5 6 MLS Frequency Channel See Chapter 3 100 2000 6 0 MLS Frequency Channel See Chapter 3 100 2000 C 7 MLS Frequency See Chapter 3 100 200

0 3 7 0 2 0 HF COM Frequency See Chapter 3 100 2000 B 9 HF COM Frequency See Chapter 3 100 200

0 4 1 0 0 2 Set Latitude Deg/Min 180N/180S 6 N 0.1 250 5000 0 4 Set Latitude Deg/Min 180N/180S 6 N 0.1 250 5000 2 0 Set Latitude Deg/Min 180N/180S 6 N 0.1 250 5000 5 6 Set Latitude Deg/Min 180N/180S 6 N 0.1 250 5000 6 0 Set Latitude Deg/Min 180N/180S 6 N 0.1 250 5000 A 4 Set Latitude Deg/Min 180N/180S 6 N 0.1 250 500

0 4 2 0 0 2 Set Longitude Deg/Min 180E/180W 6 E 0.1 250 5000 0 4 Set Longitude Deg/Min 180E/180W 6 E 0.1 250 5000 2 0 Set Longitude Deg/Min 180E/180W 6 E 0.1 250 5000 5 6 Set Longitude Deg/Min 180E/180W 6 E 0.1 250 5000 6 0 Set Longitude Deg/Min 180E/180W 6 E 0.1 250 5000 A 4 Set Longitude Deg/Min 180E/180W 6 E 0.1 250 500

0 4 3 0 0 2 Set Magnetic Heading Deg 0-359 3 1.0 250 5000 0 4 Set Magnetic Heading Deg 0-359 3 1.0 250 5000 2 0 Set Magnetic Heading Deg 0-359 3 1.0 250 5000 5 6 Set Magnetic Heading Deg 0-359 3 1.0 250 5000 6 0 Set Magnetic Heading Deg 0-359 3 1.0 250 5000 A 4 Set Magnetic Heading Deg 0-359 3 1.0 250 500

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

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

0 4 6 0 3 3 Engine Serial No. (LSDs) 500 1000 See Att. 61 0 A Engine Serial No. (LSDs) 500 1000 See Att. 61 0 B Engine Serial No. (LSDs) 500 1000 See Att. 6

0 4 7 0 2 0 VHF Com Frequency See Chap. 3 100 2000 2 4 VHF Com Frequency See Chap. 3 100 2000 3 3 Engine Serial No. (MSDs) 500 1000 See Att. 61 0 A Engine Serial No. (MSDs) 500 1000 See Att. 61 0 B Engine Serial No. (MSDs) 500 1000 See Att. 60 B 6 VHF Com Frequency See Chap. 3 100 200

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

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

0 5 6 0 0 2 Estimated Time of Arrival Hr:Min 0-23.59.9 5 0.1 250 5000 0 5 Wind Direction - Magnetic Deg 0-359 3 1.0 250 5000 3 7 Gross Weight (Kilograms) 100 kg 0-19999 5 1.0 100 2000 5 6 ETA (Active Waypoint) Hr:Min 0-23.59.9 5 0.1 250 5000 6 0 ETA (Active Waypoint) Hr:Min 0-23.59.9 5 0.1 250 500



TABLE 1 - BCD DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense

Reso-lution



MaxTrans-

portDelay

(msec) 3

Notes

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

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

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

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

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

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

0 6 6 0 0 2 Longitudinal Center of Gravity % MAC 0-100.00 5 0.01 500 10000 3 7 Longitudinal Center of Gravity % MAC 0-100.00 5 0.01 100 200

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

1 2 5 0 0 2 Universal Coordinate Time Hr-Min 0-23.59.9 4 0.1 100 2000 0 B UTC Hr:Min 23:59.9 5 0.1

Min200 1200

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

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

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

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

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

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

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

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

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

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

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

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

1 6 5 0 0 7 Radio Height Feet ±7999.9 5 0.1 25 200

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

2 0 0 0 0 2 Drift Angle Deg ±180 4 0.1 100 2000 0 4 Drift Angle Deg ±180 4 0.1 100 2000 5 6 Drift Angle Deg ±180 4 0.1 100 2000 6 0 Drift Angle Deg ±180 4 0.1 100 200

2 0 1 0 0 9 DME Distance N.M. -1-399.99 5 0.01 83.3 1671 1 2 TACAN Distance N.M. 0-399.99 5 0.01 190 2101 1 5 DME Distance N.M. 0-399.99 5 0.01 50 50



TABLE 1 - BCD DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSens

e

Reso-lution



MaxTrans-

portDelay

(msec) 3

Notes

2 0 5 0 0 2 HF COM Freq (New Format) See Figure 3-10 B 9 HF COM Freq (New Format) See Figure 3-1

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

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

2 3 2 0 0 4 Altitude Rate Ft/Min ±20000 4 Up 10.0 31.3 62.50 0 5 Altitude Rate Ft/Min ±20000 4 Up 10.0 31.3 62.50 0 6 Altitude Rate Ft/Min ±20000 4 Up 10.0 31.3 62.51 1 4 Inner 4 Tank Probe Capacitance pf 0-400 14 0.1

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

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

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

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

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

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

2 6 0 0 0 2 Date/Flight Leg N/A 500 10000 0 B Date dd:mo:yr dd:mm:yr 15 40 3 1 Date (No Flight Leg) N/A 100 2000 5 6 Date/Flight Leg N/A 500 10000 6 0 Date/Flight Leg N/A 500 10000 A 2 Date/Flight Leg N/A 500 1000

2 6 1 0 0 2 Flight Number N/A 0-9999 4 1.0 500 10000 A 2 Flight Number N/A 0-9999 4 1.0 500 10000 5 6 Flight Number N/A 0-9999 4 1.0 500 10000 6 0 Flight Number N/A 0-9999 4 1.0 500 1000

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

2 7 3 0 5 A Sensor Values Left Wing Tank pF 0-100 13 100 200

2 7 4 0 5 A Sensor Values Center Wing Tank pF 0-100 13 0.1 100 200

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

3 4 5 0 0 2 NDB Effectivity 1000 See Attachment 6

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

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

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

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



TABLE 1 - BCD DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSens

e

Reso-lution



MaxTrans-

portDelay

(msec) 3

Notes

3 7 7 0 3 0 Equipment Identification 1000 See Attachment 6X X X Equipment Identification 1000 See Attachment 6



TABLE 2 - BNR DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense Resolution

MinTransitInterval(msec)

2

MaxTransitInterval(msec)

2

MaxTrans-

portDelay(msec)

3

Notes

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

0 2 5 0 4 D Load SEL Control NA 204700 11 100

0 3 4 0 2 5 VOR/ILS Frequency 125 250

0 3 5 0 2 5 DME Frequency 125 250

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

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

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

0 6 0 0 2 5 S/G Software Part Number See Attachment 60 3 C Tire Pressure (Left Outer) PSIA 1024 10 1.0 50 250 See Attachment 6

0 6 1 0 0 2 ACMS Information See Attachment 60 0 B Pseudo Range Meters ± 268435456 20 256 200 12000 2 5 S/G Hardware Part Number See Attachment 60 3 C Tire Pressure (Left Inner) PSIA 1024 10 1.0 50 250 See Attachment 60 5 6 ACMS Information See Attachment 60 6 0 ACMS Information See Attachment 6

0 6 2 0 0 2 ACMS Information See Attachment 60 0 B Pseudo Rang Fine Meters 256 11 0.125 200 1200 See Attachment 60 3 C Tire Pressure (Right Inner) PSIA 1024 10 1.0 50 250 See Attachment 60 5 6 ACMS Information See Attachment 60 6 0 ACMS Information See Attachment 6

0 6 3 0 0 2 ACMS Information See Attachment 60 0 B Range Rate M/S ± 4096 20 0.0039 200 12000 3 C Tire Pressure (Right Outer) PSIA 1024 10 1.0 50 250 See Attachment 60 5 6 ACMS Information See Attachment 60 6 0 ACMS Information See Attachment 6

0 6 4 0 0 B Delta Range Meters ± 4096 20 0.0039 200 12000 3 C Tire Pressure (Nose) PSIA 1024 10 1.0 50 250 See Attachment 6

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

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

0 7 0 0 0 2 Reference Airspeed (Vref) Knots 512 11 0.25 500 1000 10000 0 B SV Position X Meters ±67108864 20 64 200 12000 2 9 AC Frequency (Engine) Hz 512 11 .25 100 2000 3 7 Hard Landing Magnitude #1 Lbs. 12 - 100 2000 5 6 Reference Airspeed (Vref) Knots 512 11 0.25 500 1000 10000 6 0 Reference Airspeed (Vref) Knots 512 11 0.25 500 1000 1000

0 C C Brakes - Metered Hyd. Pres. L(Normal)

PSIG 4096 12 1 50 100 #1 & 2 coded in SDI

0 7 1 0 0 2 Take-Off Climb Airspeed (V2) Knots 512 11 0.25 500 1000 500 0 B SV Position Y Fine Meters 64 14 0.0039 200 12000 2 9 AC Frequency (Engine) Hz 512 11 0.25 100 2000 3 3 VBV Deg 64 12 0.016 150 2500 3 7 Hard Landing Magnitude #2 Lbs. 12 - 100 2000 C C Brakes-Metered Hyd.Pres.L (alt.) PSIG 4096 12 1 50 100 #1 & 2 coded in SDI



TABLE 2 - BNR DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense Resolution


2


2

MaxTrans-

portDelay(msec)

3

Notes

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

0 7 3 0 0 2 V1 (critical engine failure speed) Knots 512 11 0.25 100 2000 0 B SV Position Z Fine Meters 64 14 0.0039 200 12000 1 C Oil Quantity cc 32768 8 128 100 2000 2 9 Oil Quantity US Pint 128 9 0.25 100 2000 A 2 V2 (critical engine failure speed) Knots 512 11 0.25 100 2000 C C Brakes-Metered Hyd.Pres.R (alt.) PSIG 4096 12 1 50 100 #1 & 2 coded in SDI0 D 0 Engine Oil Quantity US Pint 128 9 0.25 SDI 1=L/SDI 2=R

0 7 4 0 0 2 Zero Fuel Weight Lbs. 1310720 15 40 500 1000 10000 0 B UTC Measure Time Seconds 10.0 20 9.536743µs 200 12000 2 C Zero Fuel Weight Lbs. 1310720 15 40 100 4000 3 3 LP Compressor Bleed Pos. (3.0) Inches 4 10 0.004 100 200 See Note [5]0 3 7 Zero Fuel Weight (lb) Lbs. 1310720 15 40 100 2000 5 6 Zero Fuel Weight Lbs. 1310720 15 40 500 1000 10000 6 0 Zero Fuel Weight Lbs. 1310720 15 40 500 1000 10001 1 4 Zero Fuel Weight Lbs. 1310720 15 40 100 400

0 7 5 0 0 2 Gross Weight Lbs. 1310720 15 40 100 2000 0 3 Gross Weight Lbs. 1310720 15 40 100 2000 0 B Geodetic Altitude Feet 131072 17 1.0 500 10000 2 9 AC Voltage (Alt. Sources) Volts 256 10 0.25 100 2000 2 C Gross Weight Lbs. 1310720 15 40 100 2000 3 7 Gross Weight Lbs. 1310720 15 40 100 2000 3 E Gross Weight Lbs. 1310720 15 40 100 2001 1 4 Aircraft Gross Weight Lbs. 1310720 15 40 100 400

0 7 6 0 0 B GPS Height Above Ref.Ellipsoid Feet 131072 17 1.0 25 500 0 B GNSS Altitude (Msl) Feet ±131072 20 0.125 200 12000 2 9 AC Voltage (Bus Bar) Volts 256 10 0.25 100 2000 3 7 Longitudinal Center of Gravity % MAC 163.84 14 0.01 100 2000 3 E Longitudinal Center of Gravity % 164 14 0.01 100 200

1 1 4 Aircraft Longitudinal Center ofGravity

Percent 163.84% 14 0.01% 100 200

0 7 7 0 - - Lateral Center of Gravity MLb-in 128 17 0.001 100 2000 0 2 Target Airspeed Knots 512 11 0.25 100 2000 0 B GPS Hor/Vert Deviation % F.S. 128 8 0.8 25 50 Revised by Supp 110 2 9 AC Load (Engine) % 256 8 1.0 100 2000 3 7 Lateral Center of Gravity % MAC 131.072 17 0.01 100 2000 5 6 Target Airspeed Knots 512 11 0.25 100 2000 6 0 Target Airspeed Knots 512 11 0.25 100 2001 1 4 Zero Fuel Center of Gravity Percent 163.84% 14 0.01% 100 200

1 0 0 0 0 1 Selected Course #1 Deg/180 ±180 12 0.05 167 3330 0 2 Selected Course #1 Deg/180 ±180 12 0.05 167 3330 1 1 Selected Course #1 Deg/180 ±180 12 0.05 167 3330 2 0 Sleected Course #1 Deg/180 ±180 12 0.05 167 3330 2 9 AC Load (Alt. Source) % 128 8 1.0 100 2000 5 6 Selected Course #1 Deg/180 ±180 12 0.05 167 3330 6 0 Selected Course #1 Deg/180 ±180 12 0.05 167 3330 3 7 Gross Weight (Kilogram) Kilograms 655360 15 20 100 2000 A 1 Selected Course #1 Deg/180 ±180 12 0.05 167 3330 B 1 Selected Course #1 Deg/180 ±180 12 0.05 167 3330 B B Outboard Flaps - PDU Deg/180 ±180 12 0.05 20 100



TABLE 2 - BNR DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense Resolution


2


2

MaxTrans-

portDelay(msec)

3

Notes

1 0 1 0 0 2 Selected Heading Deg/180 ±180 12 0.05 31.3 62.50 0 B HDOP N/A 1024 15 0.031 200 12000 2 0 Selected Heading Deg/180 ±180 12 0.05 31.3 62.50 2 5 Selected Heading Deg/180 ±180 12 0.05 125 2500 2 9 DC Current (TRU) Amperes 256 8 1.0 100 2000 A 1 Selected Heading Deg/180 ±180 12 0.05 31.3 62.50 B B Inboard Flaps - PDU Deg/180 ±180 12 0.05 20 1001 1 4 C/G Target % 164 8 0.01 100 200

1 0 2 0 0 2 Selected Altitude Feet 65536 16 1.0 100 2000 0 B VDOP N/A 1024 15 0.031 200 12000 2 0 Selected Altitude Feet 65536 16 1.0 100 2000 2 9 DC Current (Battery) Amperes 256 8 1.0 100 2000 5 6 Selected Altitude Feet 65536 16 1.0 100 2000 6 0 Selected Altitude Feet 65536 16 1.0 100 2000 A 1 Selected Altitude Feet 65536 16 1.0 100 200

1 0 3 0 0 1 Selected Airspeed Knots 512 11 0.25 100 2000 0 2 Selected Airspeed Knots 512 11 0.25 100 2000 0 3 Selected Airspeed Knots 512 11 0.25 100 2000 0 B GNSS Track Angle Deg ±108 15 0.0055 200 12000 1 B Left/PDU Flap Deg/180 ±180 18 0.000687 100 2000 2 0 Selected Airspeed Knots 512 11 0.25 100 2000 2 9 DC Voltage (TRU) Volts 128 9 0.25 100 2000 5 6 Selected Airspeed Knots 512 11 0.25 100 2000 6 0 Selected Airspeed Knots 512 11 0.25 100 2000 A 1 Selected Airspeed Knots 512 11 0.25 100 2000 B B Left Outboard Flap Position Deg/180 ±180 12 0.05 20 100

1 0 4 0 0 1 Selected Vertical Speed Ft/Min 16384 10 UP 16 100 2000 0 2 Selected Vertical Speed Ft/Min 16384 10 UP 16 100 2000 1 B Right/PDU Flap Deg/180 ±180 18 0.000687 100 2000 2 0 Selected Vertical Speed Ft/Min 16384 10 UP 16 100 2000 2 9 DC Voltage (Battery) Volts 128 9 0.25 100 2000 2 B Selected Vertical Speed Ft/Min 16384 14 UP 1 100 2000 5 6 Selected Vertical Speed Ft/Min 16384 10 UP 16 100 2000 6 0 Selected Vertical Speed Ft/Min 16384 10 UP 16 100 2000 A 1 Selected Vertical Speed Ft/Min 16384 10 UP 16 100 2000 B B Right Outboard Flap Position Deg/180 ±180 12 0.05 20 100

1 0 5 0 0 2 Selected Runway Heading Deg/180 ±180 11 0.1 167 3330 1 0 Selected Runway Heading Deg/180 ±180 11 0.1 167 3330 1 B Left/PDU Slat Deg/180 ±180 18 0.000687 100 2000 2 0 Selected Runway Heading Deg/180 ±180 11 0.1 167 3330 2 9 Oil Temp. Input (IDG/CSD) Deg C 2048 12 0.5 100 2000 5 5 Selected Runway Heading Deg ±180 11 0.10 5 6 Selected Runway Heading Deg/180 ±180 11 0.1 167 3330 6 0 Selected Runway Heading Deg/180 ±180 11 0.1 167 3330 A 1 Selected Runway Heading Deg/180 ±180 11 0.1 167 3330 B 0 Selected Runway Heading Deg/180 ±180 11 0.1 167 3330 B B Left Inboard Flap Position Deg/180 ±180 12 0.05 20 100

1 0 6 0 0 2 Selected Mach Mach 4096 12 1 31.3 2000 1 B Right/PDU Slat Deg/180 ±180 18 0.000687 100 2000 2 0 Selected Mach Mach 4096 12 0.5 100 2000 2 9 Oil Temp. Input (IDG/CSD) Deg C 2048 12 0.5 100 2000 5 6 Selected Mach Mach 4096 12 1 31.3 2000 6 0 Selected Mach Mach 4096 12 1 31.3 2000 A 1 Selected Mach Mach 4096 12 1 31.3 62.50 B B Right Inboard Flap Position Deg/180 ±180 12 0.05 20 100

1 0 7 0 0 2 Selected Cruise Altitude Feet 65536 16 UP 1 100 2000 1 B Flap/Slat Lever Deg/180 ±180 18 0.000687 100 2000 B B Flap Lever Position-median value Deg/180 ±180 18 0.000687 100 200



TABLE 2 - BNR DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense Resolution


2


2

MaxTrans-

portDelay(msec)

3

Notes

0 3 7 Long. Zero Fuel Ctr of Gravity % MAC 163.84 14 0.01 100 2000 5 6 Selected Cruise Altitude Feet 65536 16 UP 1 100 2000 6 0 Selected Cruise Altitude Feet 65536 16 UP 1 100 200

1 1 0 0 0 1 Selected Course #2 Deg/180 ±180 12 0.05 167 3330 0 2 Selected Course #2 Deg/180 ±180 12 0.05 167 3330 0 B GNSS Latitude Deg ±180 20 0.000172 200 12000 1 0 Selected Course #2 Deg/180 ±180 12 0.05 167 3330 1 1 Selected Course #2 Deg/180 ±180 12 0.05 167 3330 2 0 Selected Course #2 Deg/180 ±180 12 0.05 167 3330 A 1 Selected Course #2 Deg/180 ±180 12 0.05 167 3330 B 1 Selected Course #2 Deg/180 ±180 12 0.05 167 3330 B B Flap Lever Position - Center Deg/180 180 18 0.000687 80 160

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

1 1 2 0 0 2 Runway Length Feet 20480 11 10 250 5000 0 B GNSS Ground Speed Knots 4096 15 0.125 200 12000 A 1 Selected EPR 4 12 0.001 100 2000 A 1 Selected N1 RPM 4096 12 1 100 2000 B B Flap Lever Position - Left Deg/180 ±180 18 0.000687 80 160

1 1 4 0 0 2 Desired Track Deg/180 ±180 12 0.05 100 2000 2 9 Brake Temp. (Left Inner L/G) Deg C 2048 11 1 100 2000 2 F Ambient Pressure PSIA 32 14 0.002 100 2000 3 F Pamb Sensor PSIA 32 14 0.002 100 2000 5 6 Desired Track Deg/180 ±180 12 0.05 100 2000 6 0 Desired Track Deg/180 ±180 12 0.05 100 2000 B B Flap Lever Position - Right Deg/180 ±180 18 0.000687 80 1600 C C Wheel Torque Output Lb./Ft. 16384 12 4 50 100 No. 5 to 8 in SDI1 0 A Selected Ambient Static Pressure PSIA 1.5-20.0 11 0.016 100 5001 0 B Selected Ambient Static Pressure PSIA 1.5-20.0 11 0.016 100 5001 3 A Ambient Pressure PSIA 32 14 0.002 100 200

1 1 5 0 0 2 Waypoint Bearing Deg/180 ±180 12 0.05 31.3 62.50 2 9 Brake Temp. (Left Outer L/G) Deg C 2048 11 1 100 2000 2 F Fuel Temperature Deg C 512 11 0.25 100 2000 3 F Fuel Temperature Deg C 512 11 0.25 100 2000 5 6 Waypoint Bearing Deg/180 ±180 12 0.05 31.3 62.50 6 0 Waypoint Bearing Deg/180 ±180 12 0.05 31.3 62.50 B C Fuel Temperature Deg C 256 8 1 500 10000 C C Wheel Torque Output Lb./Ft. 16384 12 4 50 100 No. 1 to 4 in SDI

1 1 6 0 0 2 Cross Track Distance N.M. 128 15 0.004 31.3 62.50 0 B Horizontal GLS Deviation Rectilinear Feet 24000 18 .00915 1000 2 9 Brake Temp. (Right Inner L/G) Deg C 2048 11 1 100 2000 5 5 Horizontal GLS Deviation Rectilinear Feet 24000 18 .00915 1000 5 6 Cross Track Deviation N.M. 128 15 0.004 31.3 62.50 6 0 Cross Track Deviation N.M. 128 15 0.004 31.3 62.50 C C Wheel Torque Output Lb./Ft. 16384 12 4 50 100 No. 9 to 12 in SDI

1 1 7 0 0 2 Vertical Deviation Feet 2048 11 1.0 31.3 62.50 0 B Vertical GLS Deviation Rectilinear Feet 1024 14 .0625 1000 2 9 Brake Temp. (Right Outer L/G) Deg C 2048 11 1 100 2000 5 5 Vertical GLS Deviation Rectilinear Feet 1024 14 .0625 1000 5 6 Vertical Deviation Feet 2048 11 1.0 31.3 62.50 6 0 Vertical Deviation Feet 2048 11 1.0 31.3 62.50 C C Wheel Torque Output Lb./Ft. 16384 12 4 50 100 No. 13 to 16 in SDI

1 2 0 0 0 2 Range to Altitude N.M. 512 15 0.016 25 500 0 B GNSS Latitude Fine Deg 0.000172 11 8.38-E-8 o 200 12000 5 6 Range to Altitude N.M. 512 15 0.016 25 50



TABLE 2 - BNR DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense Resolution


2


2

MaxTrans-

portDelay(msec)

3

Notes

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

1 2 1 0 0 2 Horizontal Command Signal Deg/180 ±180 14 0.01 50 1000 0 B GNSS Longitude Fine Degrees 0.000172 11 8.38-E-8 o 200 12000 2 5 Pitch Limit Deg/180 ±180 14 0.01 125 2500 5 6 Horizontal Command Signal Deg/180 ±180 14 0.01 50 1000 6 0 Horizontal Command Signal Deg/180 ±180 14 0.01 50 100

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

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

1 2 6 0 0 2 Vertical Deviation (wide) Feet 32768 15 abovesel alt

1.0 31.3 62.5

0 5 6 Vertical Deviation Feet 32768 15 abovesel alt

1.0 31.3 62.5

0 6 0 Vertical Deviation Feet 32768 15 abovesel alt

1.0 31.3 62.5

1 2 7 0 0 2 Selected Landing Altitude Feet 65536 16 UP 1 100 2000 1 B Slat Angle Deg/180 ±180 12 0.05 100 2000 3 3 P14 PSIA 32 14 0.002 100 2001 0 A Fan Discharge Static Pressure PSIA 1.5 - 30.0 11 0.016 100 5001 0 B Fan Discharge Static Pressure PSIA 1.5 - 30.0 11 0.016 100 500

1 3 0 0 0 B Aut Horiz Integ Limit N.M. 16 17 1.2E-4 200 12000 1 A Fan Inlet Total Temperature Deg C 128 11 0.06 100 2000 1 C Fan Inlet Total Temperature Deg C 128 11 0.06 100 2000 2 F Fan Inlet Total Temperature Deg C 128 11 0.06 100 200

0 3 5 Intruder Range 500 See Att. 6 andARINC 735

0 3 F Fan Inlet Total Temperature Deg C 128 11 0.06 100 2001 0 A Selected Total Air Temperature Deg C -80 - +90 10 0.125 100 5001 0 B Selected Total Air Temperature Deg C -80 - +90 10 0.125 100 5001 3 A Inlet Temperature Deg C 128 11 0.0625 100 200

1 3 1 0 1 A Fan Inlet Total Pressure PSIA 32 13 0.004 100 2000 1 C Fan Inlet Total Pressure PSIA 32 13 0.004 100 2000 2 D Fan Inlet Total Pressure PSIA 32 13 0.004 100 2000 2 F Fan Inlet Total Pressure PSIA 32 13 0.004 100 2000 3 3 Fan Inlet Total Pressure PSIA 32 13 0.004 100 200

0 3 5 Intruder Altitude 500 See Att. 6 andARINC 735

1 3 A Inlet Pressure PSIA 32 13 0.004 100 2001 3 2 0 1 A Exhaust Gas Total Pressure PSIA 32 13 0.004 100 200

0 1 C Exhaust Gas Total Pressure PSIA 32 13 0.004 100 2000 3 3 Exhaust Gas Total Pressure PSIA 32 14 0.002 100 250

0 3 5 Intruder Bearing 500 See Att. 6 andARINC 735

1 3 3 0 0 B Aut Vert Integ Limit Feet 32,768 18 0.125 200 12000 1 A Thrust Lever Angle Deg/180 ±180 12 0.05 100 2500 2 F Thrust Lever Angle Deg/180 ±180 12 0.05 25 500 3 F Thrust Lever Angle Deg/180 ±180 12 0.05 25 501 0 A Selected Throttle Lever Angle Deg 90 11 0.088 31.3 1001 0 B Selected Throttle Lever Angle Deg 90 11 0.088 31.3 100

1 3 4 0 1 C Power Lever Angle Deg/180 ±180 12 0.05 100 2001 0 A Throttle Lever Angle Deg ±128 11 0.088 500 10001 0 B Throttle Lever Angle Deg ±128 11 0.088 500 10001 3 A Throttle Lever Angle Deg/180 ±180 12 0.05 25 50



TABLE 2 - BNR DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense Resolution


2


2

MaxTrans-

portDelay(msec)

3

Notes

1 3 5 0 1 C Engine Vibration #1 in/sec 8 12 0.002 100 2000 2 9 Engine Fan Vibration % FS 128 7 1 100 200

1 3 6 0 0 B Vertical Figure of Merit Feet 32,768 18 0.125 200 12000 1 C Engine Vibration #2 in/sec 8 12 0.002 100 200

1 3 7 0 1 B Flap Angle Deg/180 ±180 12 0.05 100 200 See Attachment 60 2 A Flap Angle Deg/180 ±180 12 0.05 100 200 See Attachment 60 2 F Thrust Reverser Position Feedback % 128 12 0.03 100 2000 3 F Thrust Reverser Position Feedback % 128 12 0.03 100 2001 0 A Selected Thrust Reverser Position % -5 - +105 11 0.063 62.5 2501 0 B Selected Thrust Reverser Position % -5 - +105 11 0.063 62.5 2501 4 0 Flap Angle Deg 180 12 0.05 62.5 200

1 4 0 0 0 1 Flight Director - Roll Deg/180 ±180 12 0.05 50 1000 0 B UTC Fine Seconds 1 20 0.953674µs 200 12000 2 5 Flight Director - Roll Deg/180 ±180 10 0.02 125 250

1 4 1 0 0 1 Flight Director - Pitch Deg/180 ±180 12 0.05 50 1000 0 B UTC Fine Fractions Seconds 0.9536743µs 10 0.953674µs 200 12000 2 5 Flight Director - Pitch Deg/180 ±180 10 0.02 125 250

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

1 4 3 0 0 1 Flight Director - Yaw Deg/180 ±180 12 0.05 50 1000 4 1 HPA Command Word See ARINC 7412 4 1 HPA Response Word See ARINC 741

1 4 4 0 2 B Altitude Error Feet 8192 14AboveCmdAlt

1.0 25 50

0 4 1 ACU/BSU Control Word See ARINC 7413 4 1 ACU/BSU Response Word See ARINC 741

1 4 5 0 0 2 TACAN Control See Sec. 3.1.4 180 220 See Attachment 6

1 4 6 1 1 2 TACAN Control See Sec. 3.1.4 180 220

1 4 7 X X X TACAN Control Word 100 200

1 5 0 0 0 2 Universal Coordinated Time See Table 6-120 0 B UTC Hr:Min:S ±23:59:59 17 1.0sec 200 12000 3 1 Universal Coordinated Time 100 200 See Table 6-120 5 6 Universal Coordinated Time See Table 6-120 6 0 Universal Coordinated Time See Table 6-12

1 5 1 0 0 2 Localizer Bearing (True) Deg/180 ±180 11 0.1 167 3330 2 7 MLS Azimuth Deviation0 5 5 MLS AZ Deviation mV ± 2400 15 0.07320 5 6 Localizer Bearing (True) Deg/180 ±180 11 0.1 167 3330 5 A LB/KG Control Word See ARINC 429P20 6 0 Localizer Bearing (True) Deg/180 ±180 11 0.1 167 333

1 5 2 0 2 7 MLS Elevation Deviation0 4 1 Open Loop Steering See ARINC 7410 5 5 MLS GP Deviation mV ± 2400 15 0.0732

1 5 3 0 0 2 Maximum Altitude Feet 65536 16 AboveS.L.

1 500 1000 100

0 2 7 Flare0 4 1 Closed Loop Steering See ARINC 7410 5 5 MLS Selected Azimuth Deg 0-359 9 1



TABLE 2 - BNR DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense Resolution


2


2

MaxTrans-

portDelay(msec)

3

Notes

1 5 4 0 0 2 Runway Heading (True) N.M. 512 16 0.008 83.3 1670 2 7 MLS Auxiliary Data0 5 5 MLS Max Selectable GP Deg ± 51.1 9 10 5 6 Runway Heading (True) N.M. 512 16 0.008 83.3 1670 6 0 Runway Heading (True N.M. 512 16 0.008 83.3 167

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

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

0 2 5 ADF brg left/right Deg/180 ±180 12 0.05 125 250 SDI-01=left/SDI-10=right

0 2 9 Crew Oxygen Pressure PSI 4096 12 1 100 2000 5 5 MLS Basic Data Word 5 N/A N/A N/A N/A1 4 0 Density Altitude Feet 1131072 16 2 250 500

1 6 4 0 0 2 Minimum Descent Altitude (MDA) Feet 8192 16 0.125 500 10000 0 3 Target Height Feet 8192 16 0.125 500 10000 0 7 Radio Height Feet 8192 16 0.125 25 500 2 5 Radio Height Feet 8192 12 2.0 125 2500 3 B Radio Height VDC 32 11 0.015 150 250 Per ARINC 522A0 5 5 MLS ABS GP Angle Deg ± 41 15 0.00125

1 6 5 0 0 B Vertical Velocity Feet/Min ± 32768 15 1.0 200 12000 5 5 MLS ABS Azimuth Angle Deg ± 82 16 0.00125

1 6 6 0 0 7 RALT Check Point Dev Feet 512 10 0.5 * *0 0 B North/South Velocity Knots ± 4096 15 0.125 200

1 6 7 0 0 2 EPU Estimate Position Uncertainty(ANP) Actual Navigation Perf.

N.M. 0-128 16 0.00195

1 7 1 0 0 2 RNP Reduced NavigationPerformance

N.M. 0-128 16 0.001953

0 5 6 Current RNP N.M. 0-128 16 0.001950 6 0 Current RNP N.M. 0-128 16 0.00195

X X X Manu. Specific Status Word See Attachment 6

1 7 3 0 1 0 Localizer Deviation DDM 0.4 12 0.0001 33.3 66.60 2 5 Localizer Deviation DDM 0.4 10 0.0004 125 2500 2 9 Hydraulic Quantity % 128 7 1 100 2000 3 B Localizer Deviation Dots 4 11 0.002 150 2500 5 5 Localizer Deviation DDM ± 0.4 12 0.00010 B D Hydraulic Quantity % 128 7 1 500 10000 D 0 Hydraulic Oil Quantity US Pint 128 9 0.25 SDI 1= A/SDI 2= B

1 7 4 0 0 3 Delayed Flap Approach Speed (DFA) Knots 512 11 0.25 100 2000 0 B East/West Velocity Knots ± 4096 15 0.125 200 12000 1 0 Glideslope Deviation DDM 0.8 12 0.0002 33.3 66.60 2 9 Hydraulic Pressure PSI 4096 12 1 100 2000 3 B Glideslope Deviation Dots 4 11 0.0002 150 2500 5 5 Glide Slope Deviation DDM ± 0.8 12 0.00020 D 0 Hydraulic Oil Pressure PSI 4096 12 1.0 SDI 1= A/SDI 2= B

1 7 5 0 0 3 Economical Speed Knots 1024 14 0.06 62.5 1250 2 9 EGT (APU) Deg C 2048 11 1 100 2000 3 3 Hydraulic Pump Case Drain Temp Deg C 256 12 0.06 100 200

1 7 6 0 0 3 Economical Mach Mach 4096 13 0.5 62.5 1250 2 9 RPM (APU) % RPM 256 9 0.5 100 2000 3 8 Left Static Pressure Uncorrected, mb mb 2048 18 0.008 20 2000 5 A Fuel Temperature - Set to Zero Deg. C 512 11 0.25 100 2000 A D Static Pressure Left, Uncorrected, mb mb 2048 18 0.008 20 200



TABLE 2 - BNR DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense Resolution


2


2

MaxTrans-

portDelay(msec)

3

Notes

1 1 4 Left Outer Tank Fuel Temp &Advisory Warning

Deg ± 512 11 0.025

1 7 7 0 0 3 Economical Flight Level Feet 131072 17 1.0 31.3 62.50 2 9 Oil Quantity (APU) US Pint 128 9 0.25 100 200

0 3 8 Right Static Pressure, Uncorrected,mb

mb 2048 18 0.008 20 200

0 5 5 Distance to Runway Threshold Nmiles 1024 16 0.0078120 5 A Fuel Temp. Left Wing Tank Deg C 512 11 0.25 100 200

0 A D Static Pressure Right, Uncorrected,mb

mb 2048 18 0.008 20 200

1 1 4 Inner Tank 1 Fuel Temp & AdvisoryWarning

Deg C ± 512 11 0.025

2 0 0 1 1 4 Inner Tank 2 Fuel Temp & AdvisoryWarning

Deg C ± 512 11 0.025

2 0 1 0 5 A Fuel Temp. Right Wing Tank Deg C 512 11 0.25 100 200


Deg C ± 512 11 0.025

1 4 0 Mach Maximum Operation (Mmo) Mach 4096 12 0.001 62.5 1251 4 2 Projected Future Latitude Deg ± 180 20 0.000172 150 400

2 0 2 0 0 2 Energy Management (clean) N.M. 512 15 0.016 100 2000 0 9 DME Distance N.M. 512 16 0.008 83.3 1670 5 A Fuel Temperature - Set to Zero Deg C 512 11 0.25 100 200


Deg C ± 512 11 0.025

1 4 0 Mach Rate M/minute 4096 12 0.001 62.5 1251 4 2 Projected Future Latitude Fine Deg 0.000172 11 2.E-32 Cir 150 400

2 0 3 0 0 2 Energy Management Speed Brakes N.M. 512 15 0.016 100 2000 0 6 Altitude (1013.25 mb) Feet 131072 17 1.0 31.3 62.50 1 8 Altitude Feet 131072 17 1.0 20 400 3 5 Own A/C Altitude Feet 131072 17 1.0 20 5000 3 8 Altitude (1013.25 mb) Feet 131072 17 1.0 31.3 62.50 5 A Fuel Tank #6 Temperature Deg C 512 11 0.25 100 2001 0 A Ambient Static Pressure PSIA 1.5 - 20.0 11 0.016 500 10001 0 B Ambient Static Pressure PSIA 1.5 - 20.0 11 0.016 500 1000

1 1 4 Trim Tank Fuel Temp & AdvisoryWarning

Deg C ± 512 11 0.025

1 4 0 Altitude Feet 131072 17 1 31.25 62.5

2 0 4 0 0 2 Utility Airspeed Knots 512 11 0.25 500 1000 500 0 6 Baro Corrected Altitude #1 Feet 131072 17 1.0 31.3 62.50 3 8 Baro Corrected Altitude #1 Feet 131072 17 1.0 31.3 62.50 5 6 Baro Altitude Knots 512 11 0.25 500 1000 500 5 A Fuel Tank #7 Temperature Deg C 512 11 0.25 100 2000 6 0 Baro Altitude Knots 512 11 0.25 500 1000 50

1 1 4 Right Outer Tank Fuel Temp &Advisory Warning

Deg C ± 512 11 0.025

1 4 0 Baro Corrected Altitude Feet 131072 17 1 31.25 62.5

2 0 5 0 0 6 Mach Mach 4.096 16 0.0000625 62.5 1250 1 A Mach Mach 4.096 16 0.0000625 62.5 1250 3 8 Mach Mach 4.096 16 0.0000625 62.5 1250 5 A Fuel Tank #8 Temperature Deg C 512 11 0.25 100 2001 0 A Mach Number Mach 1 11 0.002 100 5001 0 B Mach Number Mach 1 11 0.002 100 5001 4 0 Mach Mach 4.096 16 0.00000625 62.5 125

2 0 6 0 0 6 Computed Airspeed Knots 1024 14 0.0625 62.5 1250 1 8 Altitude (Variable Resolution) Feet Variable 15 Variable 31.3 62.5 See Attachment 60 3 8 Computed Airspeed Knots 1024 14 0.0625 62.5 125



TABLE 2 - BNR DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense Resolution


2


2

MaxTrans-

portDelay(msec)

3

Notes

0 C C Taxi Speed Knots 512 11 0.25 50 1001 4 0 Computed Airspeed (CAS) Knots 1024 14 0.0625 62.5 125

2 0 7 0 0 6 Maximum Allowable Airspeed Knots 1024 12 0.25 62.5 1250 0 A Maximum Allowable Airspeed Knots 512 11 0.25 100 2000 2 5 OP. Software Part Number See Attachment 60 3 8 Maximum Allowable Airspeed Knots 1024 12 0.25 62.5 125

1 4 0 Airspeed Maximum Operating(VMO)

Knots 1024 12 .025 62.56 125

2 1 0 0 0 6 True Airspeed Knots 2048 15 0.0625 62.5 1250 3 8 True Airspeed Knots 2048 15 0.0625 62.5 1251 4 0 True Airspeed Knots 2048 15 0.0625 62.5 125

2 1 1 0 0 2 Total Air Temperature Deg C 512 11 0.25 250 5000 0 3 Total Air Temperature Deg C 512 11 0.25 250 5000 0 6 Total Air Temperature Deg C 512 11 0.25 250 5000 1 A Total Air Temperature Deg C 512 11 0.25 250 5000 3 8 Total Air Temperature Deg C 512 11 0.25 250 5000 A D Total Air Temperature Indicated Deg C 512 12 0.125 250 5001 0 A Total Fan Inlet Temperature Deg C -80 - +90 10 0.125 500 10001 0 B Total Fan Inlet Temperature Deg C -80 - +90 10 0.125 500 10001 4 0 Total Air Temperature (TAT) Deg C 512 12 0.125 250 5001 4 2 Projected Future Longitude Deg ± 180 20 0.000172 250 500

2 1 2 0 0 4 Altitude Rate Ft/Min 32768 11 16 31.3 62.50 0 5 Altitude Rate Ft/Min 32768 11 16 31.3 62.50 0 6 Altitude Rate Ft/Min 32768 11 16 31.3 62.50 3 8 Altitude Rate Ft/Min 32768 11 16 31.3 62.50 3 B Altitude Rate Ft/Min 32768 11 16 150 2501 4 0 Altitude Rate Ft/Min 32768 11 16 31.25 62.51 4 2 Projected Future Longitude Fine Deg 0.000172 11 2E-32 Cir 150 400

2 1 3 0 0 2 Static Air Temperature Deg C 512 11 0.25 250 5000 0 6 Static Air Temperature Deg C 512 11 0.25 250 5000 3 8 Static Air Temperature Deg C 512 11 0.25 250 5000 8 D Fuel Used Lbs. 262144 18 1 75 1251 4 0 Static Air Temperature (SAT) Deg C 512 11 0.25 250 5001 4 2 Vertical Time Interval Minute 265 min 10 0.25 min 500 2000

2 1 4 X X X ICAO Aircraft Address (Part 1) See Attachment 6

2 1 5 0 0 6 Impacted Pressure mb 512 14 0.03125 62.5 1250 1 A Impact Pressure mb 512 14 0.03125 62.5 1250 2 9 N1 Actual (EEC) % RPM 256 14 0.015 50 1000 2 9 EPR Actual (EEC) 4 12 0.001 50 1000 3 8 Impacted Pressure, Uncorrected, mb mb 512 14 0.03125 62.5 1250 A D Impacted Pressure, Uncorrected, mb mb 512 16 0.008 20 401 4 0 Impact Pressure Subsonic mb 512 14 0.03125 62.5 125

2 1 6 X X X ICAO Aircraft Address (Part 2)

2 1 7 0 0 2 Geometric Vertical Rate Ft/Min 20000 11 160 0 6 Static Pressure, Corrected (In.Hg.) in. Hg 64 16 0.001 62.5 1250 2 9 N1 Limit (EEC) % RPM 256 14 0.015 100 2000 2 9 EPR Limit (EEC) 4 12 0.001 100 200

0 3 8 Static Pressure, Average, Corrected(In. Hg.)

in. Hg 64 16 0.001 62.5 125

1 4 0 Static Pressure Corrected (In. Hg.) in. Hg 64 16 0.001 62.5 125

2 2 0 0 0 6 Baro Corrected Altitude #2 Feet 131072 17 1.0 31.3 62.50 3 8 Baro Corrected Altitude #2 Feet 131072 17 1.0 31.3 62.51 4 0 Baro Corrected Altitude #2 Feet 131072 17 1 31.25 62.5



TABLE 2 - BNR DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense Resolution


2


2

MaxTrans-

portDelay(msec)

3

Notes

2 2 1 0 0 6 Indicated Angle of Attack (Avg) Deg/180 ±180 12 0.05 31.3 62.50 3 8 Indicated Angle of Attack (Average) Deg/180 ±180 12 0.05 31.3 62.50 A D Indicated Angle of Attack Deg/180 ±180 14 0.01 31.3 2001 2 C Indicated Angle of Attack (Avg.) Deg/180 ±180 12 0.05 31.3 62.51 4 0 Angle of Attack Indicated Average Deg ±180 12 0.05 31.25 62.5

2 2 2 0 0 6 Indicated Angle of Attack (#1 Left) Deg/180 ±180 12 0.05 31.3 62.50 1 1 VOR Omnibearing Deg/180 ±180 12 0.004 50 1001 1 2 TACAN Bearing Deg/180 ±180 12 0.05 180 2201 1 5 Bearing Deg/180 ±180 11 0.1 50 501 2 C Indicated Angle of Attack (#1 Left) Deg/180 ±180 12 0.05 31.3 62.51 4 0 Angle of Attack, Indicated #1 Left Deg ±180 12 0.05 31.5 62.5

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

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

2 2 5 0 0 2 Minimum Maneuvering Airspeed Knots 512 11 0.25 500 1000 500 0 6 Indicated Angle of Attack (#2 Right) Deg/180 ±180 12 0.05 31.3 62.5

0 2 B Compensated Altitude Rate Ft/Min 32768 11 Increas-ing alt

16.0 31.3 62.5

0 5 6 Minimum Maneuvering Air Speed Knots 512 11 0.25 500 10000 6 0 Minimum Maneuvering Air Speed Knots 512 11 0.25 500 10001 2 C Indicated Angle of Attack (#2 Right) Deg/180 ±180 12 0.05 31.3 62.51 4 0 Angle of Attack, Indicated #2 Right Deg ±180 12 0.05 31.5 62.5

2 2 7 0 3 D AVM Command See ARINC 429P20 7 E BITE Command Word See ARINC 604

2 3 1 0 A D Total Air Temperature Deg C 512 12 0.12 20 200

2 3 3 0 0 2 ACMS Information See Attachment 60 5 6 ACMS Information0 6 0 ACMS Information




2 3 7 0 0 2 ACMS Information0 0 B Horizontal Uncertainty Level N.M. 16 17 0.000122 1200 See ARINC 743A0 5 6 ACMS Information0 6 0 ACMS Information

2 4 1 0 0 2 Min. Airspeed for Flap Extension Knots 512 11 0.25 500 1000 500 0 6 Corrected Angle of Attack Deg/180 ±180 12 0.05 31.3 62.50 3 8 Corrected Angle of Attack Deg/180 ±180 12 0.05 31.3 62.50 4 D FQIS System Data 500 1024 See Attachment 60 5 6 Min. Airspeed for Flap Extension Knots 512 11 0.25 500 10000 6 0 Min. Airspeed for Flap Extension Knots 512 11 0.25 500 10001 4 0 Angle of Attack, Corrected Deg ±180 12 0.05 31.5 62.5



TABLE 2 - BNR DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense Resolution


2


2

MaxTrans-

portDelay(msec)

3

Notes

2 4 2 0 0 6 Total Pressure mb 2048 16 0.03125 62.5 1250 1 A Total Pressure mb 2048 16 0.03125 62.5 1250 3 8 Total Pressure mb 2048 16 0.03125 62.5 1250 3 B Speed Deviation Dots 4 11 0.002 150 2500 5 6 Modified Intent Data Block0 A D Total Pressure, Uncorrected, mb mb 2048 18 0.008 20 2001 4 0 Total Pressure mb 2048 16 0.03125 62.5 125

2 4 3 X X X Simulator to Avcs Control Word 33 100 See ARINC Rpt 610

2 4 4 0 1 C Fuel Flow (Engine Direct) Lbs/hr 32768 8 128.0 100 2000 3 3 Fuel Flow (Wf) pph 32768 16 0.5 150 2500 3 B Mach Error Mach 0.064 11 0.00003 150 2500 8 D Fuel Flow Rate PPH 32768 16 0.5 75 1251 0 A Fuel Mass Flow MSEC 170 15 0.008 31.3 1001 0 B Fuel Mass Flow MSEC 170 15 0.008 31.3 1001 4 0 Angle of Attack, Normalized Ratio 2 11 0.001 62.5 125

2 4 5 0 0 2 Minimum Airspeed Knots 256 12 0.0625 62.5 1250 0 3 Minimum Airspeed Knots 256 12 0.0625 62.5 1250 0 A Minimum Airspeed Knots 512 13 0.0625 62.5 1250 2 9 N3 (Engine) % RPM 256 14 0.015 50 1000 3 8 Avg. Static Pres. mb uncorrected mb 2048 16 0.03125 62.5 1250 3 B EPR Error 4 12 0.001 150 250

0 A D Average Static Pressure mbUncorrected

mb 2048 16 0.03125 62.5 125

0 5 6 Minimum Airspeed Knots 256 12 0.0625 62.5 1250 6 0 Minimum Airspeed Knots 256 12 0.0625 62.5 1251 4 0 Static Pressure, Uncorrected mb 2048 16 0.03125 62.5 125

2 4 6 0 0 2 Control Maximum Speed (VCMAX) Knots 512 11 0.25 50 100 500 0 6 Average Static Pressure mb 2048 16 0.03 62.5 1250 1 C N1 (Engine Direct) RPM 4096 12 1.0 100 2000 2 9 N1 (Engine Direct) % RPM 256 14 0.015 50 1000 3 8 Avg Static Pres mb Corrected mb 2048 16 0.03125 62.5 1250 3 B Angle of Attack Error Deg/180 ±180 14 0.01 150 250

2 4 7 0 0 2 Control Min. Speed (VCMIN) Knots 512 11 0.25 50 100 500 0 B Horizontal Figure of Merit N.M. 16 18 6.1 E-5 200 12000 1 F Total Fuel Lbs. 655360 14 40 500 10000 2 C Total Fuel Lbs. 655360 14 40 500 10000 3 B Speed Error Knots 256 12 0.06 150 2500 4 D Total Fuel Lbs. 655360 14 40 500 10000 5 6 Control Minimum Speed (Vcmin) Knots 512 11 0.25 50 1000 5 A Total Fuel Lbs. 655360 14 40 100 2000 6 0 Control Minimum Speed (Vcmin) Knots 512 11 0.25 50 1000 E B Fuel to Remain Lbs. 1638400 14 100 100 1251 1 4 Fuel on Board Lbs. 655320 13 401 4 0 Airspeed Minimum Vmc Knots 512 11 0.25 62.5 125

2 5 0 0 0 2 Continuous N1 Limit % RPM 256 14 0.015 50 200 2000 2 B Maximum Continuous EPR Limit - 4 12 0.001 100 2000 2 C Preselected Fuel Quantity Lbs. 655360 14 40 100 4000 5 A Preselected Fuel Quantity Lbs. 655360 14 40 100 2000 3 8 Indicated Side Slip Angle Deg/180 ±180 12 0.05 31.3 62.50 A D Indicated Side Slip Angle or AOS Deg/180 ±180 14 0.01 31.3 2001 1 4 Preselected Fuel Quantity Lbs. 655320 13 40

2 5 1 0 0 1 Distance to Go N.M. 4096 15 0.125 100 2000 0 2 Distance to Go N.M. 4096 15 0.125 100 2000 0 6 Baro Corrected Altitude #3 Feet 131072 17 1.0 31.3 62.50 1 A Flight Leg Counter 75 175 See Attachment 60 3 8 Baro Corrected Altitude #3 Feet 131072 17 1.0 31.3 62.5

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



TABLE 2 - BNR DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense Resolution


2


2

MaxTrans-

portDelay(msec)

3

Notes

0 0 2 Time to Go Min. 512 9 1.0 100 2000 0 6 Baro Corrected Altitude #4 Feet 131072 17 1.0 31.3 62.50 1 A EPR Idle 4 12 0.001 100 2000 2 F EPR Idle Reference - 4 12 0.001 100 2000 3 8 Baro Corrected Altitude #4 Feet 131072 17 1.0 31.3 62.50 3 F EPR Idle Reference 4 12 0.001 100 2000 E B Time Until Jettison Complete Minutes 64 6 1 500 1000

2 5 3 0 0 2 Go-Around N1 Limit % RPM 256 14 0.015 50 200 2000 1 E Go-Around EPR Limit 4 12 0.001 100 2000 3 8 Corrected Side Slip Angle Deg/180 ±180 12 0.05 31.3 62.5

2 5 4 0 0 2 Cruise N1 Limit % RPM 256 14 0.015 50 200 2000 1 E Cruise EPR Limit 4 12 0.001 100 2000 4 D Actual Fuel Quan (test) Lbs 262144 15 8 500 10001 3 A N1 Cruise % N1 Nom 256 14 0.015 100 2001 4 0 Altitude Rate Ft/Min 131072 13 16 31.25 62.5

2 5 5 0 0 2 Climb N1 Limit % RPM 256 14 0.015 50 200 2000 1 E Climb EPR Limit 4 12 0.001 100 2000 2 F Maximum Climb EPR Rating N/A 4 12 0.001 100 2000 3 F Maximum Climb EPR Rating N/A 4 12 0.001 100 2000 4 D Fuel Quantity (gal) Gallons 32768 15 1.0 500 10000 8 E Spoiler Position Deg/180 +180 11 0.1 50 1001 3 A N1 Climb % N1 Nom 256 14 0.015 100 2001 4 0 Impact Pressure mb 4096 17 0.03125 62.5 125

2 5 6 0 0 2 Time For Climb Min. 512 9 1 100 2000 0 A V Stick Shaker Knots 512 11 0.25 100 2000 2 C Fuel Quantity (Tanks) #1 Lbs. 131072 15 4 500 10000 4 D Fuel Discretes TBD TBD See ARINC 429P20 5 6 Time for Climb Min. 512 9 1 100 2000 5 A Fuel Quantity-Left Outer Cell Lbs. 131072 15 4 100 200 Zero for A-3210 6 0 Time for Climb Min. 512 9 1 100 2001 1 4 Left Outer Tank Fuel Quantity Lbs. 131072 15 41 4 0 Equivalent Airspeed Knots 1024 14 0.0625 62.5 125

2 5 7 0 0 2 Time For Descent Min. 512 9 1 100 2000 2 C Fuel Quantity (Tanks) #2 Lbs. 131072 15 4 500 10000 5 6 Time for Descent Min. 512 9 1 100 2000 5 A Fuel Quantity Left W/T Tank Lbs. 131072 15 4 100 2000 6 0 Time for Descent Min. 512 9 1 100 2001 1 4 Fuel Quantity (Tanks) #2 Lbs. 131072 15 4 500 10001 4 0 Total Pressure (High Range) mb 4096 17 0.03125 62.5 125

2 6 0 0 2 C Fuel Quantity (Tanks) #3 Lbs. 131072 15 4 500 10000 5 A Fuel Quantity Center Tank Lbs. 131072 15 4 100 2000 3 3 T5 Deg C 1024 12 0.25 150 250 See Note [5]1 0 A LP Turbine Discharge Temp Deg C -55 - +850 11 0.50 100 5001 0 B LP Turbine Discharge Temperature Deg C -55 - +850 11 0.50 100 5001 1 4 Collector Cell 1 and 2 Fuel Quantity Lbs. 131072 15 4

2 6 1 0 2 C Fuel Quantity (Tanks) #4 Lbs. 131072 15 4 500 10000 3 3 P49 PSIA 128 14 0.008 150 2500 5 A Fuel Qty Right I/C or W/T Tank Lbs. 131072 15 4 100 2001 0 A LP Turbine Inlet Pressure PSIA 2-120 11 0.125 100 5001 0 B LP Turbine Inlet Pressure PSIA 2-120 11 0.125 100 5001 1 4 Fuel on Board at Engine Start Lbs. 131072 15 4

2 6 2 0 0 2 Documentary Data 500 1000 See Attachment 60 0 A Predicitive Airspeed Variation Knots 256 10 0.25 100 2000 1 C LP Compressor Exist Pres. (PT3) PSIA 64 13 0.008 100 2000 2 C Fuel Quantity (Tanks) #5 Lbs. 131072 15 4 500 10000 3 3 LP Compressor Exist Pressure PSIA 64 14 0.004 150 250



TABLE 2 - BNR DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense Resolution


2


2

MaxTrans-

portDelay(msec)

3

Notes

0 4 D T/U Cap-L Tank 1-4 PF 655.35 16 0.01 TBD TBD0 5 A Fuel Quantity-Right Outer Cell Lbs. 131072 15 4 100 2001 0 A HP Compressor Inlet Total Pres. PSIA 2-50 11 0.032 100 5001 0 B HP Compressor Inlet Total Pres. PSIA 2-50 11 0.032 100 5001 1 4 Center Tank Fuel Quantity Lbs. 131072 15 4

2 6 3 0 0 2 Min. Airspeed for Flap Retraction Knots 512 11 0.25 500 1000 500 0 A Min. Airspeed for Flap Retraction Knots 512 11 0.25 100 2000 1 C LP Compressor Exit Temperature 256 12 0.06 100 2000 2 C Fuel Quantity (Tanks) #6 Lbs 131072 15 4 500 10000 3 3 LP Compressor Exit Temperature Deg C 256 12 0.063 150 2500 4 D T/U Cap-L Tank 5-8 PF 655.35 16 0.01 TBD TBD0 5 6 Min. Airspeed for Flap Retraction Knots 512 11 0.25 500 10000 6 0 Min. Airspeed for Flap Retraction Knots 512 11 0.25 500 1000

1 0 A Selected Compressor InletTemperature (Total)

Deg C -55 - +160 11 0.125 100 500

1 0 B Selected Compressor Inlet Temp(Total)

Deg C -55 - +160 11 0.125 100 500

1 1 4 Collector Cell 3 and 4 Fuel Quantity Lbs. 131072 15 4

2 6 4 0 0 2 Time To Touchdown Min. 2048 11 1 100 200 1450 0 A Min. Airspeed for Slats Retraction Knots 512 11 0.25 100 2000 1 C HP Compressor Exit Pressure 512 14 0.03 100 2000 2 C Fuel Quantity (Tanks) #7 Lbs. 131072 15 4 500 10000 2 F Burner Pressure PSIA 512 14 0.03 100 2000 4 D T/U Cap-L Tank 9-12 PF 655.35 16 0.01 TBD TBD0 3 3 HP Compressor Exit Pressure PSIA 512 14 0.03 150 2500 3 F Burner Pressure PSIA 512 14 0.03 100 2000 5 6 Time to Touchdown Min. 2048 11 1 100 2000 6 0 Time to Touchdown Min. 2048 11 1 100 2001 0 A Selected Compressor Dischg Pres. PSIA 5-600 11 1.00 62.5 2501 0 B Selected Compressor Dischg Pres. PSIA 5-600 11 1.00 62.5 2501 3 A Burner Pressure PSIA 512 14 0.031 100 200

2 6 5 0 0 2 Min. Buffet Airspeed Knots 512 11 0.25 50 100 500 0 4 Integrated Vertical Acceleration Ft/Sec ±256 20 UP 0.000244 200 0 A Maneuvering Airspeed Knots 512 11 0.25 100 2000 1 C HP Compressor Exit Temp (TT4.5) 1024 12 0.25 100 2000 2 C Fuel Quantity (Tanks) #8 Lbs. 131072 15 4 500 10000 3 3 HP Compressor Exit Temperature Deg C 1024 12 0.25 150 2500 3 8 Integrated Vertical Acceleration Ft/Sec ±256 20 UP 0.000244 200 4 D T/U Cap-L Tank 13-14 PF 655.35 16 0.01 TBD TBD0 5 6 Min. Buffet Airspeed Knots 512 11 0.25 50 1000 6 0 Min. Buffet Airspeed Knots 512 11 0.25 50 1001 0 A Selected Compressor Dischg Temp Deg C -55 - +650 11 0.50 100 5001 0 B Selected Compressor Dischg Temp Deg C -55 - +650 11 0.50 100 5001 1 4 Inner Tank 3 Fuel Quantity Lbs. 131072 15 4

2 6 6 0 4 D T/U Cap-C Tank 1-4 PF 655.35 16 0.01 TBD TBD1 1 4 Inner Tank 2 Fuel Quantity Lbs. 131072 15 4

2 6 7 0 0 2 Maximum Maneuver Airspeed Knots 512 11 0.25 500 1000 500 0 A Predictive Max. Maneuver Speed Knots 512 11 0.25 100 2000 2 B Throttle Position Command Deg/180 ±180 12 0.05 50 1000 4 D T/U Cap-C Tank 5-8 PF 655.35 16 0.01 TBD TBD0 3 3 Spare T/C Deg C 256 12 0.063 150 2500 5 6 Max. Maneuver Airspeed Knots 512 11 0.25 500 10000 6 0 Max. Maneuver Airspeed Knots 512 11 0.25 500 10001 0 A HP Compressor Inlet Temp. (total) Deg C -55 - +160 11 0.125 500 10001 0 B HP Compressor Inlet Temperature Deg C -55 - +160 11 0.125 500 10001 1 4 Inner Tank 4 Fuel Quantity Lbs. 131072 15 4

2 7 0 0 4 D T/U Cap-C Tank 9 PF 655.35 16 0.01 TBD TBD1 1 5 Stored TACAN Control Word 25 50 See ARINC 429P2



TABLE 2 - BNR DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense Resolution


2


2

MaxTrans-

portDelay(msec)

3

Notes

2 7 1 0 4 D T/U Cap-A Tank 1-4 PF 655.35 16 0.01 TBD TBD

2 7 2 0 4 D T/U Cap Tank 5-8 PF 655.35 16 0.01 TBD TBD

2 7 3 0 4 D T/U Cap-A Tank 9-11 PF 655.35 16 0.01 TBD TBD

2 7 4 0 4 D T/U Cap-R Tank 1-4 PF 655.35 16 0.01 TBD TBD


2 7 6 0 0 1 FCC to Simulator Control Word 50 150Used only insimulator

0 0 2 FMC to Simulator Control Word 33 100Used only insimulator

0 0 3 TCC to Simulator Control Word 50 150Used only insimulator

0 4 D T/U Cap-R Tank 9-12 PF 655.35 16 0.01 TBD TBD


3 0 0 1 0 A ECU Internal Temperature Deg C -55 - +125 11 0.125 500 10001 0 B ECU Internal Temperature Deg C -55 - +125 11 0.125 500 1000

3 0 1 1 0 A Demanded Fuel Metering Valve Pos % 100 11 0.063 62.5 2501 0 B Demanded Fuel Metering Valve Pos % 100 11 0.063 62.5 250

3 0 2 1 0 A Demanded Variable Stator Vane Pos % 100 11 0.063 100 5001 0 B Demanded Variable Stator Vane Pos % 100 11 0.063 100 500

3 0 3 1 0 A Demanded Variable Bleed Valve Pos % 100 11 0.063 100 5001 0 B Demanded Variable Bleed Valve Pos % 100 11 0.063 100 500

3 0 4 1 0 A Demanded HPT Clearance Valve Pos % 100 11 0.063 250 10001 0 B Demanded HPT Clearance Valve Pos % 100 11 0.063 250 1000

3 0 5 1 0 A Demanded LPT Clearance Valve Pos % 100 11 0.063 250 10001 0 B Demanded LPT Clearance Valve Pos % 100 11 0.063 250 1000

3 1 0 0 0 2 Present Position - Latitude Deg/1800-180N/0-180S

20 0.000172 100 200

0 0 4 Present Position - Latitude Deg/1800-180N/0-180S

20 0.000172 100 200

0 2 9 Aileron Position Deg/180 ±180 11 0.088 50 100

0 3 8 Present Position - Latitude Deg/1800-180N/0-180S

20 0.000172 100 200

0 4 D Comp Cap-Tank PF 327.67 15 0.01 TBD TBDSee Att. 6 for SDIencoding

0 5 6 Present Position Latitude Deg/1800-180N/0-180S

20 0.000172 100 200

0 6 0 Present Position Latitude Deg/1800-180N/0-180S

20 0.000172 100 200

1 1 4 Right Outer Tank Fuel Quantity Lbs. 131068 15 4

3 1 1 0 0 2 Present Position - Longitude Deg/1800-180E/0-180W

20 0.000172 100 200

0 0 4 Present Position - Longitude Deg/1800-180E/0-180W

20 0.000172 100 200

0 2 9 Aileron Trim Deg/180 ±180 11 0.088 50 100

0 3 8 Present Position - Longitude Deg/1800-180E/0-180W

20 0.000172 100 200



TABLE 2 - BNR DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense Resolution


2


2

MaxTrans-

portDelay(msec)

3

Notes

0 3 B Control Wheel Roll Force Lbs. 64 10 0.0625 150 250

0 5 6 Present Position Longitude Deg/1800-180E/0-180W

20 0.000172 100 200

0 6 0 Present Position Longitude Deg/1800-180E/0-180W

20 0.000172 100 200

1 1 4 Trim Tank Fuel Quantity Lbs. 131072 15 4

3 1 2 0 0 2 Ground Speed Knots 4096 15 0.125 25 500 0 4 Ground Speed Knots 4096 15 0.125 25 500 0 5 Ground Speed Knots 4096 15 0.125 25 500 2 9 Rudder Position Deg/180 ±180 11 0.088 50 1000 3 8 Ground Speed Knots 4096 15 0.125 25 500 5 6 Ground Speed Knots 4096 15 0.125 25 500 5 A Fuel Quantity ACT 1 Lbs. 131072 15 4 100 2000 6 0 Ground Speed Knots 4096 15 0.125 25 50

1 1 4Additional Center Tank (Act 1) FuelQuantity

Lbs. 131072 15 4

3 1 3 0 0 2 Track Angle - True Deg/180 ±180 12 0.05 25 500 0 4 Track Angle - True Deg/180 ±180 15 0.0055 25 500 2 5 Track Angle - True Deg/180 ±180 10 0.2 125 2500 2 9 Rudder Trim Deg/180 ±180 11 0.088 50 1000 3 8 Track Angle - True Deg/180 ±180 15 0.0055 25 500 5 6 Track Angle - True Deg/180 ±180 12 0.05 25 500 5 A Fuel Quantity ACT 2 Lbs. 131072 15 4 100 2000 6 0 Track Angle - True Deg/180 ±180 12 0.05 25 50

1 1 4Additional Center Tank (Act 2) FuelQuantity

Lbs. 131072 15 4

3 1 4 0 0 2 Stabilizer Pos Indication (B747-400) Deg/180 ±180 12TE

Down0.05 25 50 50

0 0 4 True Heading Deg/180 ±180 15 0.0055 25 500 2 5 True Heading Deg/180 ±180 10 0.2 125 2500 2 9 Elevator Position Deg/180 ±180 11 0.088 50 1000 3 8 True Heading Deg/180 ±180 15 0.0055 25 500 3 B Control Wheel Pitch Force Lbs. 64 10 0.0625 150 250

1 1 4Rear Center tank (RCT) FuelQuantity

Lbs. 131072 15 4

3 1 5 0 0 1 Stabilizer Position Deg/180 ±180 12TE

Down0.05 25 50

0 0 2 Wind Speed Knots 256 8 1.0 50 1000 0 4 Wind Speed Knots 256 8 1.0 50 1000 0 5 Wind Speed Knots 256 8 1.0 50 100

0 2 9 Stabilizer Position Deg/180 ±180 11TE

Down0.088 50 100

0 3 8 Wind Speed Knots 256 8 1.0 50 1000 5 6 Wind Speed Knots 256 8 1.0 50 1000 6 0 Wind Speed Knots 256 8 1.0 50 100

0 A 1 Stabilizer Position Deg/180 ±180 12TE

Down0.05 25 50

3 1 6 0 0 2 Wind Direction (True) Deg/180 +180 12CWfromnorth

0.05 25 50 50

0 0 4 Wind Angle Deg/180 ±180 8 0.7 50 1000 2 9 Oil Temperature (Engine) Deg C 2048 12 0.5 100 2000 3 8 Wind Angle Deg/180 ±180 8 0.7 50 100

0 5 6 Wind Direction (True) Deg/180 +180 12CWfromnorth

0.05 25 50 50



TABLE 2 - BNR DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense Resolution


2


2

MaxTrans-

portDelay(msec)

3

Notes

0 6 0 Wind Direction (True) Deg/180 +180 12CWfromnorth

0.05 25 50 50

1 0 A Engine Oil Temperature Deg C -55 - +170 11 1.00 250 10001 0 B Engine Oil Temperature Deg C -55 - +170 11 1.00 250 10000 D 0 Engine Oil Temperature Deg C 2048 12 0.5 SDI 1=L SDI 2 =R

3 1 7 0 0 2 Track Angle - Magnetic Deg/180 ±180 12 0.05 25 500 0 4 Track Angle - Magnetic Deg/180 ±180 15 0.0055 25 500 0 5 Track Angle - Magnetic Deg/180 ±180 15 0.0055 25 500 2 5 Track Angle - Magnetic Deg/180 ±180 10 0.2 125 2500 2 9 Oil Pressure (Engine) PSI 4096 12 1 50 1000 3 8 Track Angle - Magnetic Deg/180 ±180 15 0.0055 25 500 5 6 Track Angle Magnetic Deg/180 ±180 12 0.05 25 500 6 0 Track Angle Magnetic Deg/180 ±180 12 0.05 25 500 D 0 Engine Oil Pressure PSI 4096 14 0.25 SDI 1 = L/SDI 2 = R

3 2 0 0 0 4 Magnetic Heading Deg/180 ±180 15 0.0055 25 500 0 5 Magnetic Heading Deg/180 ±180 15 0.0055 25 500 2 5 Magnetic Heading Deg/180 ±180 10 0.2 125 2500 3 5 Own A/C Magnetic Heading Deg/180 ±180 15 0.0055 25 500 See ARINC 7350 3 8 Magnetic Heading Deg/180 ±180 15 0.0055 25 50

0 4 D Density-Tank Lb/Gal 8.191 13 0.001 TBD TBDSee Att. 6 for SDIencoding

3 2 1 0 0 2 Drift Angle Deg/180 ±180 12 0.05 25 500 0 4 Drift Angle Deg/180 ±180 11 0.09 25 500 0 5 Drift Angle Deg/180 ±180 11 0.09 25 500 3 8 Drift Angle Deg/180 ±180 12 0.05 25 500 5 6 Drift Angle Deg/180 ±180 12 0.05 25 500 6 0 Drift Angle Deg/180 ±180 12 0.05 25 501 0 A Exhaust Gas Temperature (Total) Deg C -55 - +1100 11 1.00 500 10001 0 B Exhaust Gas Temperature (Total) Deg C -55 - +1100 11 1.00 500 1000

3 2 2 0 0 2 Flight Path Angle Deg/180 +180o 12 0.05 25 500 0 4 Flight Path Angle Deg/180 ±180 12 0.05 25 500 0 5 Flight Path Angle Deg/180 ±180 12 0.05 25 500 3 8 Flight Path Angle Deg/180 ±180 12 0.05 25 500 5 6 Flight Path Angle Deg/180 +180o 12 0.05 25 500 6 0 Flight Path Angle Deg/180 +180o 12 0.05 25 501 0 A Total Compressor Discharge Temp Deg C -55 - +650 11 0.50 500 10001 0 B Total Compressor Discharge Temp Deg C -55 - +650 11 0.50 500 1000

3 2 3 0 0 2 Geometric Altitude Feet 50000 17 10 0 4 Flight Path Acceleration g 4 12 0.001 10 200 0 5 Flight Path Acceleration g 4 12 0.001 10 200 3 8 Flight Path Acceleration g 4 12 0.001 10 200 5 6 Geometric Altitude Feet 50000 17 10 6 0 Geometric Altitude Feet 50000 17 11 0 A Variable Stator Vane Position % -5 - +105 11 0.063 500 10001 0 B Variable Stator Vane Position % -5 - +105 11 0.063 500 1000

3 2 4 0 0 4 Pitch Angle Deg/180 ±180 14 0.01 10 200 0 5 Pitch Angle Deg/180 ±180 14 0.01 10 200 2 5 Pitch Angle Deg/180 ±180 10 0.2 125 2500 3 8 Pitch Angle Deg/180 ±180 14 0.01 10 20

0 4 D Tank VSO Quantity Gal. 32768 15 1.0 TBD TBDSee Att. 6 for SDIencoding

0 5 A Effective Pitch Angle Deg./180 ±180 14 0.011 0 A Selected Fuel Metering Valve Pos % -5 - +105 11 0.063 62.5 250



TABLE 2 - BNR DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense Resolution


2


2

MaxTrans-

portDelay(msec)

3

Notes

1 0 B Selected Fuel Metering Valve Pos % -5 - +105 11 0.063 62.5 2501 1 4 Effective Pitch Angle Deg ±180 13 0.02

3 2 5 0 0 4 Roll Angle Deg/180 ±180 14 0.01 10 200 0 5 Roll Angle Deg/180 ±180 14 0.01 10 200 1 A Engine Control Trim Feedback0 2 5 Roll Angle Deg/180 ±180 10 0.2 125 2500 2 F Stator Vane Feedback Inches 4 12 0.001 100 2000 3 8 Roll Angle Deg/180 ±180 14 0.01 10 200 3 F Stator Vane Feedback Inches 4 12 0.001 100 2000 5 A Effective Roll Angle Deg/180 ±180 14 0.011 0 A Selected Variable Stator Vane Pos % -5 - +105 11 0.063 62.5 2501 0 B Selected Variable Stator Vane Pos % -5 - +105 11 0.063 62.5 2501 1 4 Effective Roll Angle Deg ±180 13 0.02

3 2 6 0 0 4 Body Pitch Rate Deg/Sec 128 13 0.015 10 200 0 5 Body Pitch Rate Deg/Sec 128 13 0.015 10 200 3 8 Body Pitch Rate Deg/Sec 128 13 0.015 10 200 4 D Uplift Quantity Lbs 1638400 14 100 TBD TBD1 0 A Compressor Discharge Static Press PSIA 5-600 11 1.00 500 10001 0 B Compressor Discharge Static Press PSIA 5-600 11 1.00 500 1000

3 2 7 0 0 4 Body Roll Rate Deg/Sec 128 13 0.015 10 200 0 5 Body Roll Rate Deg/Sec 128 13 0.015 10 200 3 8 Body Roll Rate Deg/Sec 128 13 0.015 10 200 4 D Uplift Density Lbs/Gal 8.181 13 0.001 TBD TBD1 0 A Fuel Metering Valve Position % -5 - +105 11 0.063 500 10001 0 B Fuel Metering Valve Position % -5 - +105 11 0.063 500 1000

3 3 0 0 0 4 Body Yaw Rate Deg/Sec 128 13 0.015 10 200 0 5 Body Yaw Rate Deg/Sec 128 13 0.015 10 200 2 F HC/TC Cooling Valve Pos. Feedback % 128 12 OPEN 0.03 100 2000 3 8 Body Yaw Rate Deg/Sec 128 13 0.015 10 200 3 F HC/TC Cooling Valve Pos. Feedback % 128 12 OPEN 0.03 100 200

1 0 ASelected HPT Clearance ValvePosition

% -5 - +105 11 0.063 250 1000

1 0 B Selected HPT Clearance Valve Pos % -5 - +105 11 0.063 250 1000

3 3 1 0 0 4 Body Longitudinal Acceleration g 4 12 0.001 10 200 0 5 Body Longitudinal Acceleration g 4 12 0.001 10 200 2 F LTC Cooling Valve Pos. Feedback % 128 12 OPEN 0.03 100 2000 3 8 Body Longitudinal Acceleration g 4 12 0.001 10 200 3 F LTC Cooling Valve Pos. Feedback % 128 12 OPEN 0.03 100 2001 0 A Selected LPT Clearance Valve Pos % -5 - +105 11 0.063 250 10001 0 B Selected LPT Clearance Valve % -5 - +105 11 0.063 250 1000

3 3 2 0 0 4 Body Lateral Acceleration g 4 12 0.001 10 200 0 5 Body Lateral Acceleration g 4 12 0.001 10 200 2 F A/O Heat Xchr Valve Pos. Feedback % 128 12 OPEN 0.03 100 2000 3 8 Body Lateral Acceleration g 4 12 0.001 10 200 3 F A/O Heat Xchr Valve Pos. Feedback % 128 12 OPEN 0.03 100 200

3 3 3 0 0 4 Body Normal Acceleration g 4 12 0.001 10 200 0 5 Body Normal Acceleration g 4 12 0.001 10 200 2 F Acceleration Fuel Flow Limit Lb/Hr 32768 12 8 100 2000 3 8 Body Normal Acceleration g 4 12 0.001 10 200 3 F Acceleration Fuel Flow Limit Lb/Hr 32768 12 8 100 200

3 3 4 0 0 4 Platform Heading Deg/180 ±180 11 0.09 20 400 0 5 Platform Heading Deg/180 ±180 11 0.09 20 40



TABLE 2 - BNR DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense Resolution


2


2

MaxTrans-

portDelay(msec)

3

Notes

0 2 F Fuel Flow Command Lb/Hr 32768 12 8 100 2000 3 8 Platform Heading Deg/180 ±180 11 0.09 20 400 3 F Fuel Flow Command Lb/Hr 32768 12 8 100 200

3 3 5 0 0 2 Track Angle Rate Deg/Sec 32 11 0.015 10 200 0 4 Track Angle Rate Deg/Sec 32 11 0.015 10 200 0 5 Track Angle Rate Deg/Sec 32 11 0.015 10 200 2 F 2.5 BLD Actuator Position % 128 12 0.031 100 2000 3 8 Track Angle Rate Deg/Sec 32 11 0.015 10 200 3 F 2.5 BLD Actuator Position % 128 12 0.031 100 2000 5 6 Track Angle Rate Deg/Sec 32 11 0.015 10 200 6 0 Track Angle Rate Deg/Sec 32 11 0.015 10 201 0 A Selected Variable Bleed Valve Pos % -5 - +105 11 0.063 100 5001 0 B Selected Variable Bleed Valve Pos % -5 - +105 11 0.063 100 500

3 3 6 0 0 2 Max Climb Angle Deg 32 15 Climb 0.001 100 2000 0 4 Inertial Pitch Rate Deg/Sec 128 13 0.015 10 200 0 5 Inertial Pitch Rate Deg/Sec 128 13 0.015 10 200 1 A Engine Torque % 256 12 0.063 100 2000 2 F N2 Corrected to Sta 2.5 % 128 12 0.031 100 2000 3 8 Inertial Pitch Rate Deg/Sec 128 13 0.015 10 200 3 F N2 Corrected to Sta 2.5 % 128 12 0.031 100 2001 0 A Variable Bleed Valve Position % -5 - +105 11 0.063 500 10001 0 B Variable Bleed Valve Position % -5 - +105 11 0.063 500 1000

3 3 7 0 0 2 EPR - Required For Level Flight Ratio ±4 12 0.001 100 200 Engine Types: P&W0 0 2 N1 - Required For Level Flight % RPM ±256 15 0.015 Engine Types: GE0 0 4 Inertial Roll Rate Deg/Sec 128 13 0.015 10 200 0 5 Inertial Roll Rate Deg/Sec 128 13 0.015 10 200 1 A Engine Rating % 0-256 12 0.063 100 2000 3 8 Inertial Roll Rate Deg/Sec 128 13 0.015 10 201 0 A HPT Clearance Valve Position % -5 - +105 11 0.063 500 10001 0 B HPT Clearance Valve Position % -5 - +105 11 0.063 500 1000

3 4 0 0 0 3 EPR Actual 4 12 0.001 100 2000 0 4 Inertial Yaw Rate Deg/Sec 128 13 0.015 10 200 0 4 Track Angle Grid Deg ± 180 15 0.0055 20 Hz 110 Hz0 0 5 Inertial Yaw Rate Deg/Sec 128 13 0.015 10 200 1 A EPR Actual 4 12 0.001 100 2000 2 9 EPR Actual (Engine Direct) 4 12 0.001 50 1000 2 D EPR Actual 4 12 0.001 100 2000 2 F EPR Actual 4 12 0.001 25 500 3 3 EPR Actual 4 12 0.001 100 2000 3 F EPR Actual 4 12 0.001 25 501 3 A N1 Take Off % N1Nom 256 14 0.015 25 501 4 0 Pressure Ratio (Pt/Ps) Ratio 16 14 0.001 62.5 125

3 4 1 0 0 2 Target N1 % RPM 256 14 0.015 100 2000 0 3 N1 Command % RPM 256 14 0.015 100 2000 0 3 EPR Command 4 12 0.001 100 2000 0 4 Grid Heading Deg ± 180 15 0.0055 20 Hz 110 Hz0 1 A N1 Command % RPM 256 14 0.015 100 2000 1 A EPR Command 4 12 0.001 100 2000 2 9 N1 Command (Engine) % RPM 256 14 0.015 50 1000 2 9 EPR Command (Engine) 4 12 0.001 50 1000 2 F N1 Command % RPM 256 14 0.015 25 500 2 F EPR Command 4 12 0.001 25 500 3 8 Grid Heading Deg ± 180 15 0.0055 20 Hz 110 Hz0 3 F EPR Command 4 12 0.001 100 2000 4 D I/O S/W REV 1&2 (1) 16 N/A TBD TBD



TABLE 2 - BNR DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense Resolution


2


2

MaxTrans-

portDelay(msec)

3

Notes

1 0 A Command Fan Speed % 117.5 13 0.032 31.3 1001 0 B Command Fan Speed % 117.5 13 0.032 31.3 1001 3 A N1 Reference % N1Nom 256 14 0.015 25 501 4 0 Pressure Ratio (Ps/Pso) Ratio 4 12 0.001 62.5 125

3 4 2 0 0 2 N1 Bug Drive % RPM 256 14 0.015 100 2000 0 3 N1 Limit % RPM 256 14 0.015 100 2000 0 3 EPR Limit 4 12 0.001 100 2000 1 A N1 Maximum % RPM 256 14 0.015 100 2000 1 A EPR Maximum 4 12 0.001 100 2000 2 9 N1 Limit (TCC) % RPM 256 14 0.015 100 2000 2 9 EPR Limit (TOC) 4 12 0.001 100 2000 2 F Maximum Available EPR 4 12 0.001 100 2000 3 B EPR Limit 4 12 0.001 150 2500 3 B N1 Limit % RPM 256 14 0.015 150 2500 3 F Maximum Available EPR 4 12 0.001 100 200

0 4 D S/W REV-Tank (1) 16 N/A TBD TBDSee Att. 6 for SDIencoding

1 0 A Max Allowed Fan Speed % 117.5 13 0.032 100 5001 0 B Max Allowed Fan Speed % 117.5 13 0.032 100 5001 4 0 Air Density Ratio Ratio 4 12 0.001 250 500

3 4 3 0 0 3 N1 Derate % RPM 256 14 0.015 100 2000 0 3 EPR Rate 4 12 0.001 100 2000 1 A N1 Demand % RPM 256 12 0.063 20 501 0 A N1 Command vs. TLA % 117.5 13 0.032 31.3 1001 0 B N1 Command vs. TLA % 117.5 13 0.032 31.3 100

3 4 4 0 1 A N2 % RPM 256 14 0.015 50 1000 1 C N2 % RPM 256 14 0.015 50 1000 2 9 N2 % RPM 256 14 0.015 50 1000 2 F N2 % RPM 256 14 0.015 25 500 3 3 N2 % RPM 256 14 0.015 50 2000 3 F N2 % RPM 256 14 0.015 25 50

0 4 D Fuel Discretes 50 100See ARINC 429,Part 2

1 0 A Selected Actual Core Speed % 128 12 0.063 31.3 1001 0 B Selected Actual Core Speed % 128 12 0.063 31.3 1001 3 A N2 Speed % RPM 256 14 0.015 25 500 D 0 N2 % RPM 256 13 0.03 SDI 1 = L/SDI 2 = R

3 4 5 0 1 A Exhaust Gas Temperature Deg C 2048 12 0.5 100 2000 1 C Exhaust Gas Temperature Deg C 2048 12 0.5 100 2000 2 9 Exhaust Gas Temperature Deg C 2048 12 0.5 50 1000 2 F Exhaust Gas Temperature Deg C 2048 12 0.5 25 500 3 3 Exhaust Gas Temperature Deg C 2048 12 0.5 100 2000 3 F Exhaust Gas Temperature Deg C 2048 12 0.5 25 500 4 D Discretes Status 1&3 100 200 See ARINC 429P21 0 A Selected Exhaust Gas Temp (Total) Deg C -55 - +1100 11 1.00 62.5 2501 0 B Selected Exhaust Gas Temp (Total) Deg C -55 - +1100 11 1.00 62.5 2501 3 A EGT Trimmed Deg C 2048 12 0.5 25 500 D 0 EGT Deg C 2048 12 0.5 SDI 1 = L/SDI 2 = R

3 4 6 0 0 3 N1 Actual % RPM 256 14 0.015 100 2000 1 A N1 Actual % RPM 256 14 0.015 100 2000 2 F N1 Actual % RPM 256 14 0.015 25 500 3 3 N1 Actual % RPM 256 14 0.015 50 2000 3 F N1 Actual % RPM 256 14 0.015 25 50

0 4 D Cable Cap-Hi-Z PF 65535 15 2.0 100 200See Att. 6 for SDIencoding



TABLE 2 - BNR DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense Resolution


2


2

MaxTrans-

portDelay(msec)

3

Notes

1 0 A Selected Actual Fan Speed % 128 12 0.063 31.3 1001 0 B Selected Actual Fan Speed % 128 12 0.063 31.3 1001 3 A N1 Speed Actual % N1Nom 256 14 0.015 25 500 D 0 N1 % RPM 256 13 0.03 SDI 1 = L/SDI 2 = R

3 4 7 0 2 9 Fuel Flow (Engine) Lbs/Hr 32768 12 8 50 1001 0 A LPT Clearance Valve Position % -5 - +105 11 0.063 500 10001 0 B LPT Clearance Valve Position % -5 - +105 11 0.063 500 10001 3 A Fuel Flow Lbs/Hr 32768 14 2 50 1000 D 0 Fuel Flow Lbs/Hr 32768 12 8 SDI 1 = L/SDI 2 = R

3 5 3 0 D 0 Vibration Scalar 5.12 8 0.02 SDI 1 = L/SDI 2 = R

3 5 4 0 3 D N1 Vibration Scalar 5.12 9 0.01Bit 11-Chan. ABit 12-Chan. B

0 4 D FQIS Tank ID 100 200See ARINC 429P2See Att. 6 for SDI



3 5 7 0 3 D BB Vibration Scalar 5.12 9 0.01Bit 11-Chan. ABit 12-Chan. B

3 6 0 0 0 2 Flight Information See Attachment 60 0 4 Potential Vertical Speed Ft/Min 32768 15 1.0 10 200 0 5 Potential Vertical Speed Ft/Min 32768 15 1.0 25 500 3 8 Potential Vertical Speed Ft/Min 32768 15 1.0 10 20

0 3 D N1 Rotor Imbalance Angle Deg. ±180 9 1.0Bit 11-Chan. ABit 12-Chan. B

0 5 6 Flight Information See Attachment 60 6 0 Flight Information See Attachment 61 0 A Throttle Rate of Change Deg/Sec ±16 9/9 1.00 31.3 100 See Notes [6] & [7]1 0 B Throttle Rate of Change Deg/Sec ±16 9/9 1.00 31.3 100 See Notes [6] & [7]1 4 2 RAIM Status Word N.M. 16 13 0.00195

3 6 1 0 0 4 Altitude (Inertial) Feet 131072 20 0.125 20 400 0 5 Altitude (Inertial) Feet 131072 18 0.5 20 400 3 8 Altitude (Inertial) Feet 131072 20 0.125 20 40

0 3 DLPT Rotor Imbalance Angle (737only)

Deg. ±180 9 1.0Bit 11-Chan. ABit 12-Chan. B

1 0 A Derivative of Thrust vs. N1 DFN/%N1 2000 11 2.0 62.5 250 See Note [6]1 0 B Derivative of Thrust vs. N1 DFN/%N1 2000 11 2.0 62.5 250 See Note [6]

3 6 2 0 0 4 Along Track Horizontal Acceleration g 4 12 0.001 10 200 3 8 Along Track Horizontal Acceleration g 4 12 0.001 10 201 0 A Derivative of N1 vs. TLA % N1/Deg 12 11 0.008 62.5 250 See Note [6]1 0 B Derivative of N1 vs. TLA % N1/Deg 12 11 0.008 62.5 250 See Note [6]1 1 5 Range Rate Knots ±8192 13 1.0 50 50

3 6 3 0 0 4 Cross Track Acceleration g 4 12 0.001 10 200 3 8 Cross Track Acceleration g 4 12 0.001 10 201 0 A Corrected Thrust LBF 64000 11 64.0 62.5 250 See Note [6]1 0 B Corrected Thrust LBF 64000 11 64.0 62.5 250 See Note [6]

3 6 4 0 0 4 Vertical Acceleration g 4 12 0.001 10 200 0 5 Vertical Acceleration g 4 12 0.001 10 20



TABLE 2 - BNR DATA

LabelEqptID

(Hex)


(Scale)SigBits

PosSense Resolution


2


2

MaxTrans-

portDelay(msec)

3

Notes

1 3 A N1 APR Rating % N1Nom 256 14 0.015 100 2000 3 8 Vertical Acceleration g 4 12 0.001 10 20

3 6 5 0 0 4 Inertial Vertical Velocity (EFI) Ft/Min 32768 15 1.0 20 400 0 5 Inertial Vertical Velocity (EFI) Ft/Min 32768 15 1.0 20 401 3 A N1 Max Reverse % N1Nom 256 14 0.015 100 2000 3 8 Inertial Vertical Velocity (EFI) Ft/Min 32768 15 1.0 20 40

3 6 6 0 0 4 North-South Velocity Knots 4096 15 0.125 50 1001 3 A IGV Position Deg/180 ±180 12 0.05 100 2000 3 8 North-South Velocity Knots 4096 15 0.125 50 100

3 6 7 0 0 4 East-West Velocity Knots 4096 15 0.125 100 2001 3 A IGV Request Deg/180 ±180 12 0.05 100 2000 3 8 East-West Velocity Knots 4096 15 0.125 100 200

3 7 0 0 0 4 g 9 8 13 UP 0.001 100 200 1100 0 5 g 9 8 13 UP 0.001 100 200 1100 0 B GNSS Height WGS-84 (HAE) Feet ± 131.072 20 0.125 12000 2 5 Decision Height Selected (EFI) Feet 8192 16 0.125 100 2000 C 5 Decision Height Selected (EFI) Feet 16384 17 0.125 100 200

3 7 1 X X X Gen Aviation Equip. Identifier

3 7 2 0 0 5 Wind Direction-Magnetic Deg/180 ±180 9 0.35 50 1001 0 A Actual Fan Speed % 128 12 0.063 500 10001 0 B Actual Fan Speed % 128 12 0.063 500 1000

3 7 3 0 0 5 North-South Velocity-Magnetic Knots 4096 15 0.125 100 2001 0 A Actual Core Speed % 128 12 0.063 500 10001 0 B Actual Core Speed % 128 12 0.063 500 1000

3 7 4 0 0 5 East-West Velocity-Magnetic Knots 4096 15 0.125 100 2001 0 A Left Thrust Reverser Position % -5 - +105 11 0.063 500 10001 0 B Left Thrust Reverser Position % -5 - +105 11 0.063 500 1000

3 7 5 0 0 4 Along Heading Acceleration Gs 4 18 1.53E-5 50 Hz 110 Hz0 0 5 Along Heading Acceleration g 4 12 0.001 10 200 3 3 Spare DC1 VDC 16 12 0.004 150 2500 3 8 Along Heading Acceleration Gs 4 18 1.53E-5 50 Hz 110 Hz1 0 A Right Thrust Reverser Position % -5 - +105 11 0.063 500 10001 0 B Right Thrust Reverser Position % -5 - +105 11 0.063 500 1000X X X GPS Differential Correction, Word A See ARINC 743

3 7 6 0 0 4 Cross Heading Acceleration Gs 4 18 1.53E-5 50 Hz 110 Hz0 0 5 Cross Heading Acceleration g 4 12 0.001 10 200 3 3 Spare DC2 VDC 16 12 0.004 150 2500 3 8 Cross Heading Acceleration Gs 4 18 1.53E-5 50 Hz 110 HzX X X GPS Differential Correction, Word B See ARINC 743



TABLE 2 - BNR DATA

[1] The number entered into the Range Column for eachparameter that is not angular in nature is the nearestwhole binary number greater than the parameter rangerequired. As explained in the Commentary followingSection 2.1.6 of this document, the weight of the mostsignificant bit of the twos complement fractional notationbinary word will be one half this value, and the actualmaximum value of the parameter capable of beingencoded will be the number in the range column less oneleast significant bit value. The numbers entered in theRANGE column for angular parameters are the actualdegree ranges required. The way in which theseparameters are encoded is also explained in theCommentary following Section 2.1.6.

[2] Transmit intervals and the number of parameters to betransmitted are prime factors in bus loading. Theinterval for transmission of parameters should fallbetween the minimum and maximum specified intervalsand nominally should be near the center of the range atequal intervals between transmissions. When heavy busloading dictates a shift from the center of the range, theshift should be toward the maximum transmit interval.

When words with like labels and with different SDIcodes are transmitted, each of those words is considereda unique item of information. The guidance given in thisdocument for transmit intervals should be applied tothose words as if each word were identified by adifferent label.

[3] Maximum transport delay is the worst case total delaybetween an input function and the output response.

COMMENTARY

Since the nature of the data varies, the definition oftransport delay will differ depending on theapplication. In the case of a sampling system, asample is complete when the 32-bit wordconstituting the output data is complete. In the caseof a system involving filtering, transport delay is thephase slope of the transfer function across thefrequency band of interest.

There can be situations in which it is necessary to definewhich portions of an equipment are included in thetransport delay term. Such definitions should appear inindividual equipment Characteristics when needed.

[4] The values shown in parentheses are the preferred datastandards for stator vane angle. However, a considerableportion of existing equipment use the other (non-parenthesized) values. Users should verify the datastandards of the equipment they are or will be using.

[5] These labels can provide data in a degraded accuracymode. See Section 2.1.5.1 and 2.1.5.2.

[6] Optionally transmitted.

[7] Binary packed word consisting of:

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

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

c-4

c-5

c-7

c-12

c-4


ATTACHMENT 3

VOLTAGE LEVELS

A

B

G

R C V RA

B

G

X M T R

AC

VO

LT

S

X M T R O U T P U T S T A T E S R C V R I N P U T S T A T E S

H I N U L L L O H I N U L L L O

A BV

+ 1 0

-10

+ 1 1

+ 9

+ 1 3

+ 6 . 5

+ 2 . 5

-2 .5

-6 .5

-13

-9

-11

+ 0 . 5-0 .5

c-4

c-4


ATTACHMENT 4INPUT/OUTPUT CIRCUIT STANDARDS

OUTPUT (SYSTEM)CAPABILITY

Total System *Resistance

Total System *Capacitance

System Capacitance Unbalance

400 to 8,000 ohms

1,000 to 30,000 pF

Not defined but unbalance due toaircraft interwiring should be heldto a minimum

UTILIZATION DEVICESTANDARDS

RI > 12,000 ohms

CI < 50 pF

RH or RG > 12,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.2.4.2.

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

NOTES:

* Includes aircraft interwiring

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

c-16

c-4

c-4

O T H E R D E V I C E S

T O T A LS Y S T E M

O U T P U TC A P A B I L I T Y

T R A N S M I T T I N G U N I T U T I L I Z A T I O N D E V I C E

+E /2

-E /2

o

o

R /2

R /2

s

s

E o

CH

CG

RI

RH

RG

CI

* * * *

* *

* ** *


ATTACHMENT 5INTERNATIONAL STANDARDS ORGANIZATION CODE #5

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

STANDARD CODE

BIT 7 BIT 6 BIT 5

00

0

00

1

01

0

01

1

10

0

10

1

11

0

11

1

BIT4

BIT3

BIT2

BIT1

Column

Row

0 1 2 3 4 5 6 7

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

NOTE: b8 is used as a parity bit.


ATTACHMENT 6GENERAL WORD FORMATS AND ENCODING EXAMPLE

6.1. General Word Formats

TABLE 6-132 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 1P

[5]SSM[4]

DATA PAD DISCRETES MSB [3] [2] LSB

SDI[1]

LABEL

Generalized BCD Word Format

TABLE 6-1-1P SSM BCD CH #2 BCD CH #2 BCD CH #3 BCD CH #4 BCD CH #5 SDI 8 7 6 5 4 3 2 1

0 0 040

21

10

80

41

20

11

80

41

21

11

81

40

20

10

80

41

21

10 0 0 1 0 0 0 0 0 0 1

Example 2 5 7 8 6 DME DISTANCE (201)

BCD Word Format Example (No Discretes)

TABLE 6-232 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 1P

[5]SSM[4]

DATA PAD DISCRETES MSB [3] [2] LSB

SDI[1]

LABEL

Generalized BNR Word Format

TABLE 6-2-18 7 6 5 4 3 2 1

P31 30

SSM29

1/2 1/4 1/8 1/16 1/32 1/64 1/128 etc

11PAD SDI LABEL

0 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 1 1 1 1Example: 512 Knots (i.e., 1/8 x 4096 where 4096 is entry in range column of Table 2, Att. 2) N-S VELOCITY (366)

BNR Word Format Example (No Discretes)

TABLE 6-3P SSM

(01)“STX” UNIT

ADDRESSWORD COUNT LABEL

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

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

P SSM(01)

“STX” SPARES(Zeroes)

WORD COUNT LABEL(356)

32 31 30 29 23 22 17 16 BNR EQUIV. 9 8 1

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

P SSM(00)

“DATA CH #3” DATA CH #2 DATA CH #1 LABEL(356, 357)

32 31 30 29 P 23 22 L 16 15 A 9 8 1

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

P SSM(10)

“DATA CH #3” DATA CH #2 DATA CH #1 LABEL(356, 357)

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

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

(Taken together, the following example shows encoding of the word ALPHA into three successive data words).

c-4


ATTACHMENT 6GENERAL WORD FORMATS AND ENCODING EXAMPLES

TABLE 6-4DISCRETESP SSM

(00)SDI LABEL

(See Below)32 31 30 29 MSB [2] LSB 11 10 9 8 1

LABEL USAGE SUBGROUP

155 – 161 Maintenance270 – 276 Discretes350 – 354 Maintenance

Discrete Word Format

TABLE 6-5 ACKNOWLEDGEMENT WORD COUNTP SSM

(01) (FORMAT NOT DEFINED)LABEL

(355)32 31 30 29 17 16 BNR EQUIV. 9 8 1

Acknowledgement Word – Initial Word Format

TABLE 6-5-1ACKNOWLEDGEMENTP SSM


(355)32 31 30 29 9 8 1

Acknowledgement Word – Intermediate Word Format

TABLE 6-5-2ACKNOWLEDGEMENTP SSM


(355)32 31 30 29 9 8 1

Acknowledgement Word – Final Word Format

TABLE 6-632 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 1P

[5]SSM[4]

DATA PADS * [3]

SDI[1]

LABEL(173/174)

* Bit No. 11 takes on the binary state “one” to annunciate that the ILS receiver is in the “tune inhibit” condition.

ILS Localizer/Glideslope Deviation Word

TABLE 6-732 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 1P

[5]SSM[4]

DATA FIELD ** * SDI[1]

LABEL(202)

* Bit No. 11 is assigned to a memory on/off annunciation function (see Section 4.7 of ARINC 709)** Bit No. 12 is set to “1” when data is for a foreground station in frequency scanning mode. 0 1 0 0 0 0 0 1

DME Distance Word

TABLE 6-832 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

DATE

Day Month

SSM

x10 x1 x10 x1

FLIGHTLEG

PAD[3]

SDI[1]

LABEL(260)

2 1 8 4 2 1 1 8 4 2 1 8 4 2 1

PARITY 0 0 1 0 0 0 1 1 0 1 0 0 0 0 1 0 1 0 0 0 0 0 0 0 0 0 0 1 1 0 1Example 2 3 0 8 5 0 6 2

Date/Flight Leg Word

c-4

c-6



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

FLIGHT NUMBER

x1000 x100 x10 x1

SSM

8 4 2 1 8 4 2 1 8 4 2 1 8 4 2 1

PAD SDILABEL

(261)

PARITY

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

Example 0 1 1 7 1 6 2

Flight Number Word

TABLE 6-1032 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[5]

SSM[4]

MSB DATA LSBPAD[3] [6]

SDI[1]

LABEL(222)

[6] Marker Beacon Output Discrete Bits

Bit StateDiscrete Bit Discrete Grounded Discrete Open400 Hz1300 Hz3000 Hz

111213

111

000

VOR Omnibearing

TABLE 6-1132 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 1P

[5]SSM[4]

MSB DATA LSB PADLEVER

POSITIONSDI[1]

LABEL(127/137)

BitLever 11 12 13 14 15Position 1 (Cruise)Position 2Position 3Position 4Position 5 (Landing)

10000

01000

00100

00010

00001

Slat/Flap Angle Word

TABLE 6-1232 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 1P

[5]SSM[4]

HOURS0-24

MINUTES0-60

SECONDS0-60

* SDILABEL

(150)*Bit 11 of label 150 should be encoded with a “1” when the GNSS system clock is being used as the source of time.Otherwise, bit 11 should be encoded as “0”.

UTC Binary Word

TABLE 6-1332 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(164)

P[5]

SSM[4] DATA PAD FTI

SDI[1]

0 0 1 0 1 1 1 0 Note: When Bit 11 (Functional Test Inhibit) is a “1”, a functional test should not be performed. 4 6 1

Radio Height Word

c-4

c-16

c-4



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

DOCUMENTARY DATA4 2 1 4 2 1 4 2 1 4 2 1 4 2 1 4 2 1

LABEL(262)

P

[5]

SSM

[4] Code 1 Code 2 Code 3 Code 4 Code 5 Code 6

PAD SDI

[1] 0 1 0 0 1 1 0 1

Documentary Data Word

[1] Source/Destination Identifier (SDI) Field

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

[2] Discretes

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

[3] Pad

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

[4] Sign/Status Matrix (SSM)

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

[5] Parity Bit

This bit is encoded to render word parity odd. Section 2.3.4 of this document refers.



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

P SSM PAD 3rd Digit 2nd Digit LSD PAD SDI LABEL (046)

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

Example 6 4 9 6 4 0

Engine Serial Number (3LDs)

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

P SSM PAD MSD 5th Digit 4th Digit PAD SDI LABEL (047)

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

Example 0 3 2 7 4 0

Engine Serial Number (3 MSDs)

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

P SSM SPARE MSD LSD SDI LABEL (377)

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

1 0 D 7 7 3

Equipment Identifier Word(Example provided for 10D code)

c-11



TABLE 6-1832 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 DATE

Day Month Year

x10 x1 x10 x1 x10 x1

2 1 8 4 2 1 1 8 4 2 1 8 4 2 1 8 4 2 1

SDI LABEL

(260 031)

Chronometer

Output Only

P

A

R

I

T

Y0 0 1 0 0 0 1 1 0 1 0 0 0 1 0 0 0 0 1 0 1 0 0 0 0 0 0 1 1 0 1

Example 2 3 0 8 8 5 0 6 2

TABLE 6-1932 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

4096-65535

LEGS

P SSM

(00)

D PRIMARY COUNTER 0-4096 FLIGHT LEGS

MSB LSB MSB LSB

PAD SDI LABEL

(251 01A)

Electronic Supervisory Control

Flight Leg Counter

TABLE 6-2032 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

(00)

ALTITUDE

MSB LSB

SEE

BELOW

SDI LABEL

(206 018)

Transponder

Bits13 12 11

Range Bits Used App. Resolution

000011

001100

010101

655366553665536512008192051200

151413121410

48

162510

100

Altitude (Variable Reduction)



TCAS INTRUDER RANGE WORD

TABLE 6-2132 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

[5]

INTRUDER RANGE

[3] [4]

INTRUDER

SENSE LVL[2]

INTRUDER

NUMBER [1]

SDI LABEL

(130)

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

MSB LSB MSB LSB MSB LSB LSB MSB

5.25 NM 2 5 0 3 1

Note 1: Maximum number of intruders is 31.

Note 2: Intruder Sensitivity Level Status

Bits Meaning18 17 1600001111

00110011

01010101

Not ReportedSL = 1SL = 2SL = 3SL = 4SL = 5SL = 6SL = 7

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

Note 4: Intruder range may be reported in the form of horizontal range when intruder is available.

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

Bits Meaning31 300011

0101

Failure WarningNo Computed DataFunctional DataNormal Operation



TCAS INTRUDER ALTITUDE WORD

TABLE 6-2232 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

[5] [4]

RELATIVE ALTITUDE

[3]

I.V.S.

[2]

FUTURE

SPARE

INTRUDER

NUMBER [1]

SDI LABEL

(131)

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

S MSB LSB MSB LSB LSB MSB

2500 FT LEVEL 5 1 3 1


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


0101

No Vertical Rate (Level Flight)ClimbingDescendingNo Data

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

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



0101




TCAS INTRUDER BEARING WORDTABLE 6-23

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

P SSM

[5] [4]

BEARING

[3]

DISPLAYMATRIX

[2]

INTRUDERNUMBER

[1]

SDI LABEL

(132)

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

S MSB LSB MSB LSB MSB LSB LSB MSB

0 NOTHREAT 1 2 3 1


Note 2: Display Matrix

Bits Meaning18 17 1600001111

00110011

01010101

No ThreatTraffic AdvisoryResolution AdvisoryProximate TrafficNot UsedNot UsedNot UsedNot Used

Note 3: Binary, Fractional Binary;Range = -180 to +180 Degrees

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



0101




TRANSPONDER ALTITUDE/TCAS OWN AIRCRAFT ALTITUDETABLE 6-24

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

[2]S ALTITUDE ALT

[1]PAD LABEL

(203)

0 1 1 0 0 0 1 0 1 0 0 1 0 0 1 0 0 0 0 1 1 0 0 0 1 1 0 0 0 0 0 1 MSB LSB LSB MSB

21059 1 3 0 2

S = Sign Bit see Section 2.1.5.2 of this Document.

Note 1: Altitude Resolution

Bits Meaning1101

1 Ft100 Ft



0101




2. Encoding Examples

Table 6-25 BCD DATA ENCODING EXAMPLES

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

DATA FIELD [1]

MSC LSC

LABEL

PARAMETER (Label)

SSM

4 2 1 8 4 2 1 8 4 2 1 8 4 2 1 8 4 2 1

SDI

1 2 4 1 2 4 1 2Distance To Go (001) +2750.4 NM

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

Time To Go (002) +145.3 Min.

0 0 0 0 0 1 0 1 0 0 0 1 0 1 0 0 1 1 P P P P 0 0 0 1 0 0 0 0 0 0

Cross Track Distance (003) 225.6 NM

1 0 0 0 1 0 0 0 1 0 0 1 0 1 0 1 1 0 P P P P 0 0 1 1 0 0 0 0 0 0

Ground Speed (012) 650 Knots

1 0 0 0 0 0 0 1 1 0 0 1 0 1 0 0 0 0 P P P P 0 0 0 1 0 1 0 0 0 0

Track Angle (True) (013) 165.5 Deg.

1 0 0 0 0 1 0 1 1 0 0 1 0 1 0 1 0 1 P P P P 0 0 1 1 0 1 0 0 0 0

Selected Vertical Speed (020) -2200 Ft/Min

0 1 1 0 1 0 0 0 1 0 0 0 0 0 0 0 0 0 P P P P 0 0 0 0 0 0 1 0 0 0

Selected EPR (021) 2.05

0 0 0 0 1 0 0 0 0 0 0 1 0 1 P P P P P P P P 0 0 1 0 0 0 1 0 0 0

Selected N1 (021) 2750 RPM

1 0 0 0 1 0 0 1 1 1 0 1 0 1 0 0 0 0 P P P P 0 0 1 0 0 0 1 0 0 0

Selected Mach (022) 0.850 Mach

0 0 0 0 0 0 1 0 0 0 0 1 0 1 0 0 0 0 P P P P 0 0 0 1 0 0 1 0 0 0

Selected Heading (023) 177 Deg.

1 0 0 0 0 1 0 1 1 1 0 1 1 1 P P P P P P P P 0 0 1 1 0 0 1 0 0 0

Selected Course (024) 154 Deg.

1 0 0 0 1 0 0 1 0 1 0 1 0 0 P P P P P P P P 0 0 0 1 0 1 0 0 0

Selected Altitude (025) 41000 Ft.

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

Selected Airspeed (026) 423 Knots

0 0 0 1 0 0 0 0 1 0 0 0 1 1 P P P P P P P P 0 0 0 1 1 0 1 0 0 0

Universal Time Constant (125) 1545.5 Hr.

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

Radio Height (165) 2450.5 Ft.

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

Decision Height Selected (170) 200 Ft.

0 0 0 0 1 0 0 0 0 0 0 0 0 0 P P P P P P P P 0 0 0 0 0 1 1 1 1 0

DME Distance (201) 257.86 NM

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

True Airspeed (230) 565 Knots

0 0 0 1 0 1 0 1 1 0 0 1 0 1 P P P P P P P P 0 0 0 0 0 1 1 0 0 1

Total Air Temp. (231) -025 Deg. C [2]

0 1 1 0 0 0 0 0 1 0 0 1 0 1 P P P P P P P P 0 0 1 0 0 1 1 0 0 1

Altitude Rate (232) -15250 Ft/Min

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

Static Air Temp. (233) +013 Deg. C [2]

1 0 0 0 0 0 0 0 0 1 0 0 1 1 P P P P P P P P 0 0 1 1 0 1 1 0 0 1

Baroset (ins Hg) (235) 29.92 ins Hg

0 0 0 0 1 0 1 0 0 1 1 0 0 1 0 0 1 0 P P P P 0 0 1 0 1 1 1 0 0 1

NOTES:

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

[2] Because of the actual maximum value of the most significant character of these quantities exceeds 7, it cannotbe encoded in the most significant character position of the BCD word. For this reason, each quantity hasbeen given an “artificial” MSC of zero and its actual MSC encoded in the next most significant characterposition of the word.



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

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

MSC LSCLABEL

PARAMETER (Label)SSM

1 8 4 2 1 8 4 2 1 8 4 2 1 8 4 2 1 8 4 2 1 1 2 4 1 2 4 1 2 Present Position (Lat.) N 75 Deg 59.9' (010) 1 0 0 0 0 1 1 1 0 1 0 1 0 1 0 1 1 0 0 1 1 0 0 1 0 0 0 1 0 0 0 0 Present Position (Long) W 169 Deg 25.8' (011) 0 1 1 1 0 1 1 0 1 0 0 1 0 0 1 0 0 1 0 1 1 0 0 0 1 0 0 1 0 0 0 0

(See Commentary following Section 2.1.2 of this document for further information.)

c-4



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

MSB

LSB

DATAWheel747

Nos.DC-10

PAR

ITY

BN

RB

CD

SPARES

512

256

128

64 32 16 8 4 2 1 SPA

RE

SPA

RE

DIF

F. L

OW

TH

RE

SHO

LD

LO

W

WH

EE

L F

AU

LT

SYST

EM

FA

UL

T

WH

EE

LL

AB

EL

LABELREF.

ARINCOCT.

1 1 1 0 0 0 1 0 1 1 0 0 1 0 115

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

B I T S

10 9

N L N R

0 0 0 1

N L N R

0 0LO (061) RO (063) LO (061) RO (063)

LI (060) RI (062) LI (060) RI (062)

1 2

0 0 0 1

3 4

1 0 1 1

5 6

87

0 0 0 1

1 0 1 1

9 1 0

1 21 1

0 0 0 1

1 0 1 1

1 3 1 4

1 61 5

0 0

1 0

0 1

1 1

1 2

5 6

0 0 0 1

1 0 1 1

3 4

7 8

9 1 0

0 0 0 0

0 1 0 1

0 0 0 1

1 0 1 1

7 4 7N O S E ( 0 6 4 )

D C - 1 0N O S E ( 0 6 4 )



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

MSB

LSB

DATAWheel

747Nos.

DC-10

PAR

ITY

BN

RB

CD

SPARES

512

256

128

64 32 16 8 4 2 1 PRE

DIC

T

DIF

F.T

EM

P.

WA

RM

HO

T

BR

AK

E F

AU

LT

SYST

EM

WH

EE

LL

AB

EL LABEL

REF.ARINCOCT.

1 1 1 0 0 0 1 0 1 1 0 0 0 0 115

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

B I T S

10 9

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

LI (114) RI (116) LI (114) RI (116)

1 2

0 0 0 1

3 4

1 0 1 1

5 6

87

0 0 0 1

1 0 1 1

9 1 0

1 21 1

0 0 0 1

1 0 1 1

1 3 1 4

1 61 5

0 0

1 0

0 1

1 1

1 2

5 6

0 0 0 1

1 0 1 1

3 4

7 8

9 1 0

0 0 0 0

0 1 0 1

0 0 0 1

1 0 1 1

7 4 7



Table 6-27 BNR DATA ENCODING EXAMPLES

Bit No. 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1LABELPARAMETER (Label) P SSM DATA FIELD [1] SDI

1 2 4 1 2 4 1 2Selected Course (100) 0 Deg. [3]

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

Selected Heading (101)150 Deg. [3]

0 1 1 0 1 1 0 1 0 1 0 1 0 1 0 1 P P P P P P 0 0 1 0 0 0 0 0 1 0

Selected Altitude (102) 41000 Ft.

1 1 1 0 1 0 1 0 0 0 0 0 0 0 1 0 1 0 0 0 P P 0 0 0 1 0 0 0 0 1 0

Selected Airspeed (103) 423.0 Knots

0 1 1 0 1 1 0 1 0 0 1 1 1 0 0 P P P P P P P 0 0 1 1 0 0 0 0 1 0

Selected Vertical Speed (104) -2200 Ft/Min [2]

1 1 1 1 1 1 0 1 1 1 0 1 1 0 P P P P P P P P 0 0 0 0 1 0 0 0 1 0

Selected Mach (106) 800 m Mach

1 1 1 0 0 0 1 1 0 0 1 0 0 0 0 0 P P P P P P 0 0 0 1 1 0 0 0 1 0

Desired Track (114) 275 Deg. [3]

0 1 1 1 1 0 0 0 0 1 1 1 0 0 1 0 P P P P P P 0 0 0 0 1 1 0 0 1 0

Cross Track Distance (116) 51.0 NM

1 1 1 0 0 1 1 0 0 1 1 0 0 0 0 0 0 0 0 P P P 0 0 0 1 1 1 0 0 1 0

Vertical Deviation (117) 600 Ft.

0 1 1 0 0 1 0 0 1 0 1 1 0 0 0 P P P P P P P 0 0 1 1 1 1 0 0 1 0

Flight Director Roll (140) +30 Deg.

1 1 1 0 0 0 1 0 1 0 1 0 1 0 1 1 P P P P P P 0 0 0 0 0 0 0 1 1 0

Flight Director Pitch (141) -10 Deg. [2]

1 1 1 1 1 1 1 1 0 0 0 1 1 1 0 0 P P P P P P 0 0 1 0 0 0 0 1 1 0

Fast/Slow (142) +15 Knots

0 1 1 0 0 1 1 1 1 0 0 0 0 0 0 0 P P P P P P 0 0 0 1 0 0 0 1 1 0

UTC (150) (18:57:20)

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

Radio Height (164) 2450 Ft.

0 1 1 0 0 1 0 0 1 1 0 0 1 0 0 1 0 0 0 0 P 0 0 0 0 0 1 0 1 1 1 0

Localizer Deviation (173) +0.021 DDM

1 1 1 0 0 0 0 0 1 1 0 1 1 0 0 0 P P P P P P 0 0 1 1 0 1 1 1 1 0

Glide Slope Deviation (174) -0.125 DDM [2]

1 1 1 1 1 1 0 1 1 0 0 0 0 0 0 0 P P P P P P 0 0 0 0 1 1 1 1 1 0

DME Distance (202) 257.86 NM

0 1 1 0 1 0 0 0 0 0 0 0 1 1 1 0 1 1 1 0 P 0 0 0 0 1 0 0 0 0 0 1

Altitude (29.92) (203) 45000 Ft.

0 1 1 0 0 1 0 1 0 1 1 1 1 1 1 0 0 1 0 0 0 P 0 0 1 1 0 0 0 0 0 1

Mach (205) 0.8325 Mach

0 1 1 0 0 0 1 1 0 1 0 0 0 0 0 0 1 0 0 0 P P 0 0 1 0 1 0 0 0 0 1

Computed Airspeed (206) 425 Knots

1 1 1 0 0 1 1 0 1 0 1 0 0 1 0 0 0 0 P P P P 0 0 0 1 1 0 0 0 0 1

True Airspeed (210) 565 Knots

0 1 1 0 0 1 0 0 0 1 1 0 1 0 1 0 0 0 0 P P P 0 0 0 0 0 1 0 0 0 1

Static Air Temp (213) +13 Deg. C

0 1 1 0 0 0 0 0 0 1 1 0 1 0 0 P P P P P P P 0 0 1 1 0 1 0 0 0 1

Total Air Temp (211) -25 Deg. C [2]

0 1 1 1 1 1 1 1 0 0 1 1 1 0 0 P P P P P P P 0 0 1 0 0 1 0 0 0 1

Altitude Rate (212) -15250 Ft/Min [2]

0 1 1 1 1 0 0 0 1 0 0 0 1 1 1 P P P P P P P 0 0 0 1 0 1 0 0 0 1

Present Pos. Lat. (310) N 81.5 Deg

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

Present Pos. Long. (311) W 100.25

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

Ground Speed (312) 650 Knots

1 1 1 0 0 0 1 0 1 0 0 0 1 0 1 0 0 0 0 P P P 0 0 0 1 0 1 0 0 1 1

Flight Path Accel (323) +2.50 g

0 1 1 0 1 0 1 0 0 0 0 0 0 1 0 1 0 0 P P P P 0 0 1 1 0 0 1 0 1 1

NOTES:

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

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

[3] Angles in the range 0 to 180o are encoded as positive numbers. Angles in the range 180o to 360o are subtractedfrom 360o and the resulting number encoded as a negative value per note 2. Arc minutes and seconds areencoded as decimal degrees.



TABLE 6-28

AVM Command Word – Label 227 03D

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

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

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

Bits Meaning

10 9

0 0 Engine 4 (or All Call) {not used on 757}

0 1 Engine 1 (or Engine 1 and 2)

1 0 Engine 2

1 1 Engine 3 (or Engine 3 and 4)

Bits Parameter

31 30 29 28 27 26 25

0 0 0 0 0 0 0 Not Used

0 0 0 0 0 0 1 Unit Self Test

0 0 0 0 0 1 0 Use Accelerometer A**

0 0 0 0 0 1 1 Use Accelerometer B**

0 0 0 0 1 0 0 PAD

0 0 0 0 1 0 1 Erase Fault History

0 0 0 0 1 1 0 Erase Flight History*

0 0 0 0 1 1 1 Read Fault History

0 0 0 1 0 0 0 Read Flight History*

0 0 1 0 0 1 0 Reserved*

* 737 Only** 757 Only



ACMS INFORMATION

ORIGIN AND DESTINATIONTABLE 6-29Label 061 002

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

P SSMORIGIN

CHAR #3

ORIGIN

CHAR #2

ORIGIN

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

P SSMDESTINATION

CHAR #1

ISO #5 CHAR

“SPACE”

ORIGIN

CHAR #4

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 9 8 7 6 5 4 3 2 1

P SSMDESTINATION

CHAR #4

DESTINATION

CHAR #3

DESTINATION

CHAR #2

OCTAL LABEL

063

NOTE: All characters are expressed in ISO #5 format, as defined in ARINC Specification 429.



TABLE 6-30

TACAN Control - Label 145 002

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

Bit No. Description1 02 1 13 14 0 45 06 17 0 58 1

9-10 SDI11-13 Pad Zero

14 VOR/TAC Select (TAC=1, VOR=0)15 TACAN Select (TAC 1=1, TAC 2=0)16 Pad Zero

17-20 BCD Units Chan Cont (LSB=17)21-24 Hex Tens Chan Cont (LSB=24)

25 Pad Zero26 X/Y Mode (X=1, Y=0)

27-28 Mode Cont (see Table A)29 Pad Zero

30-31 SSM (see Table B)32 Parity (Odd)

Table A – Mode Control Table B – SSM

Bits Description27 280 0 REC0 1 A/A REC1 0 T/R1 1 A/A T/R

Bits Description30 310 0 Valid0 1 Functional Test1 0 No Computed Data1 1 Not Used



ACMS INFORMATION FLIGHT NUMBERTABLE 6-31

Label 233 EQ ID 002 MSB LSB MSB LSB32 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 SSMPAD

ZEROCHAR #2

PAD

ZEROCHAR #1 SDI

OCTAL LABEL

233

Label 234 EQ ID 00232 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 SSMPAD

ZEROCHAR #4

PAD

ZEROCHAR #3 SDI

OCTAL LABEL

234

Label 235 EQ ID 00232 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 SSMPAD

ZEROCHAR #6

PAD

ZEROCHAR #5 SDI

OCTAL LABEL

235

Label 236 EQ ID 00232 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 SSMPAD

ZEROCHAR #8

PAD

ZEROCHAR #7 SDI

OCTAL LABEL

236

Sign Matrix for BNRBit

31 30Meaning

0 0 Failure Warning

0 1 No Computed data

1 0 Functional Test

1 1 Normal Operation

………………………………………………………………………………………………………………………………..TABLE 6-32

Label 233 EQ ID 018 MSB LSB MSB LSB32 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 SSMPAD

ZEROCHAR #2

PAD

ZEROCHAR #1 SDI

OCTAL LABEL

233

Label 234 EQ ID 01832 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 SSMPAD

ZEROCHAR #4

PAD

ZEROCHAR #3 SDI

OCTAL LABEL

234

Label 235 EQ ID 01832 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 SSMPAD

ZEROCHAR #6

PAD

ZEROCHAR #5 SDI

OCTAL LABEL

235

Label 236 EQ ID 01832 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 SSMPAD

ZEROCHAR #8

PAD

ZEROCHAR #7 SDI

OCTAL LABEL

236

Sign Matrix for BCDNOTE: The following information is provided in order to clarify the

confusion that existed in the Industry in regards to definition of theSSM for Label 233-236. It is expected that Flight ID will besourced from FMC EQ ID of 002. Alternative implementation mayinclude Mode “S” XPDR EQ ID 018. In this case the usercautioned that the SSM will be BCD format. See ARINCCharacteristic 718A, “Mark 4 Air Traffic Control Transponder(ATCRB/MODE S)”, Attachment 3A for more detailedinformation.

Bit31 30

Meaning

0 0 Valid0 1 No Computed data1 0 Functional Test1 1 Failure Warning

c-16



TABLE 6-33

Label 360-002

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

“STX” BINARY WORD COUNTP 0 1

0 0 0 0 0 1 0

PADZERO

0 0 0 0 0 1 1 1

OCTAL LABEL360

INITIAL WORD

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

P 0 0FLIGHT NUMBER

CHAR #3FLIGHT NUMBER


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

P 0 0FLIGHT NUMBER



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

P 0 0ORIGIN



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

P 0 0ORIGIN

CHAR #4ORIGIN

CHAR #3ORIGIN

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

P 0 0DESTINATION

CHAR #3DESTINATION

CHAR #2DESTINATION

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

P 0 0PAD

ZEROSPAD

ZEROSDESTINATION

CHAR #4OCTAL LABEL

360

INTERMEDIATE WORD (SEVENTH)

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



TABLE 6-34

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

P 0 SUBSYSTEM SAL

MSB

SUBSYSTEM ID

(LABEL 172)



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

LABEL: 241EQPT ID: 04DPARAMETER NAME: FQIS System DataUNITS: (See Below)RANGE (SCALE): (See Below)SIGNIFICANT DIGITS: (See Below)RESOLUTION: (See Below)MIN TRANS INTERVAL (msec): 500MAX TRANS INTERVAL (msec): 1024SOURCE DESTINATION IDENTIFIER: 01 – LEFT MAIN TANK

10 – RIGHT MAIN TANK11 – CENTER TANK

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

LABEL 241 WORD SEQUENCE

Sig.Word Signal Units Range Dig. Res Data

1 LEFT MAIN TANK NO. 1 pF 319.922 12 .078125 BNR2 LEFT MAIN TANK NO. 2 pF 319.922 12 .078125 BNR3 LEFT MAIN TANK NO. 3 pF 319.922 12 .078125 BNR4 LEFT MAIN TANK NO. 4 pF 319.922 12 .078125 BNR5 LEFT MAIN TANK NO. 5 pF 319.922 12 .078125 BNR6 LEFT MAIN TANK NO. 6 pF 319.922 12 .078125 BNR7 LEFT MAIN TANK NO. 7 pF 319.922 12 .078125 BNR8 LEFT MAIN TANK NO. 8 pF 319.922 12 .078125 BNR9 LEFT MAIN TANK NO. 9 pF 319.922 12 .078125 BNR10 LEFT MAIN TANK NO. 10 pF 319.922 12 .078125 BNR11 LEFT MAIN TANK NO. 11 pF 319.922 12 .078125 BNR12 LEFT MAIN TANK NO. 12 pF 319.922 12 .078125 BNR13 LEFT MAIN TANK NO. 13 pF 319.922 12 .078125 BNR14 LEFT MAIN TANK NO. 14 pF 319.922 12 .078125 BNR15 LEFT MAIN BITE CAP. NO. 1 pF 319.922 12 .078125 BNR16 LEFT MAIN COMPENSATOR pF 319.922 12 .078125 BNR17 LOAD SELECT 10,000 Lb 0-90000 1 10000 BCD18 LOAD SELECT 1,000 Lb 0-9000 1 1000 BCD19 LOAD SELECT 100 Lb 0-900 1 100 BCD20 NO DATA TRANSMITTED DURING THIS WORD21 LEFT MAIN FUEL DENSITY Lb/Gal 8.000 12 .000977 BNR (1)22 RIGHT MAIN TANK NO. 1 pF 319.922 12 .078125 BNR23 RIGHT MAIN TANK NO. 2 pF 319.922 12 .078125 BNR24 RIGHT MAIN TANK NO. 3 pF 319.922 12 .078125 BNR25 RIGHT MAIN TANK NO. 4 pF 319.922 12 .078125 BNR26 RIGHT MAIN TANK NO. 5 pF 319.922 12 .078125 BNR27 RIGHT MAIN TANK NO. 6 pF 319.922 12 .078125 BNR28 RIGHT MAIN TANK NO. 7 pF 319.922 12 .078125 BNR29 RIGHT MAIN TANK NO. 8 pF 319.922 12 .078125 BNR30 RIGHT MAIN TANK NO. 9 pF 319.922 12 .078125 BNR31 RIGHT MAIN TANK NO. 10 pF 319.922 12 .078125 BNR32 RIGHT MAIN TANK NO. 11 pF 319.922 12 .078125 BNR33 RIGHT MAIN TANK NO. 12 pF 319.922 12 .078125 BNR34 RIGHT MAIN TANK NO. 13 pF 319.922 12 .078125 BNR35 RIGHT MAIN TANK NO. 14 pF 319.922 12 .078125 BNR36 RIGHT MAIN COMPENSATOR pF 319.922 12 .078125 BNR37 RIGHT MAIN BITE CAP. NO. 2 pF 319.922 12 .078125 BNR38 LOAD SELECT 10,000 Lb 0-90000 1 10000 BCD39 LOAD SELECT 1,000 Lb 0-9000 1 1000 BCD40 LOAD SELECT 100 Lb 0-900 1 100 BCD41 NO DATA TRANSMITTED DURING THIS WORD42 RIGHT MAIN DENSITY Lb/Gal 8.000 12 .000977 BNR43 CENTER TANK NO. 1 pF 319.922 12 .078125 BNR44 CENTER TANK NO. 2 pF 319.922 12 .078125 BNR45 CENTER TANK NO. 3 pF 319.922 12 .078125 BNR46 CENTER TANK NO. 4 pF 319.922 12 .078125 BNR



TABLE 6-35 (cont’d)

LABEL 241 WORD SEQUENCE (cont’d)

Sig.Word Signal Units Range Dig. Res Data

47 CENTER TANK NO. 5 pF 319.922 12 .078125 BNR48 CENTER TANK NO. 6 pF 319.922 12 .078125 BNR49 CENTER TANK NO. 7 pF 319.922 12 .078125 BNR50 CENTER TANK NO. 8 pF 319.922 12 .078125 BNR51 CENTER TANK NO. 9 pF 319.922 12 .078125 BNR52 CENTER COMPENSATOR pF 319.922 12 .078125 BNR53 CENTER BITE CAP. NO. 3 pF 319.922 12 .078125 BNR54 NO DATA TRANSMITTED DURING THIS WORD55 NO DATA TRANSMITTED DURING THIS WORD56 NO DATA TRANSMITTED DURING THIS WORD57 NO DATA TRANSMITTED DURING THIS WORD58 NO DATA TRANSMITTED DURING THIS WORD59 LOAD SELECT 10,000 Lb 0-90000 1 10000 BCD60 LOAD SELECT 1,000 Lb 0-9000 1 1000 BCD61 LOAD SELECT 100 Lb 0-900 1 100 BCD62 NO DATA TRANSMITTED DURING THIS WORD63 CENTER TANK DENSITY Lb/Gal 8.000 12 .000977 BNR

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

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

Bits Data

9 10

0 0 Aux

1 1 Center

1 0 Left

0 1 Right

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

Bits Data

9 10

0 0 #1

1 0 #2

0 1 #3

1 1 #4



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

060

Bit StatusBitNo.

Function1 0

10 SDI (Indicates Sequence ID)*11 RESERVED (Own P/N)12 RESERVED (Position ID)**13 RESERVED (Position ID)**

Own P/N Other P/N

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

Table 1 Table 2

Bits10 9

SequenceID

0 11 01 1

First Three DigitsNext Four DigitsLast Three Digits

Bits13 12

PositionID

0 0 1 0 1 1 0 1

LeftCenter As LeftCenter As RightRight



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


061

Bit StatusBitNo.

Function1 0


Own P/N Other P/N


Table 1 Table 2

Bits10 9

SequenceID

0 11 01 1


Bits13 12

PositionID

0 01 01 10 1




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


207

Bit StatusBitNo

Function1 0


Own P/N Other P/N


Table 1 Table 2

Bits10 9

SequenceID

0 11 01 1


Bits13 12

PositionID

0 01 01 10 1




TABLE 6-38Tank Unit Data – Label 241 160

WordNumber SDI DESCRIPTION UNITS

1 1 Tank Unit #1 pF2 1 Tank Unit #2 pF3 1 Tank Unit #3 pF4 1 Tank Unit #4 pF5 1 Tank Unit #5 pF6 1 Tank Unit #6 pF7 1 Tank Unit #7 pF8 1 Tank Unit #8 pF9 1 Tank Unit #9 pF

10 1 Tank Unit #10 pF11 1 Tank Unit #11 pF12 1 Tank Unit #12 pF13 1 Tank Unit #13 pF14 1 Tank Unit #14 pF15 1 BITE Capacitor pF16 1 Compensator pF17 1 Load Select Lbs.18 1 Load Select Lbs.19 1 Load Select Lbs.20 1 Undefined -21 1 Fuel Density Lbs/Gal22 2 Tank Unit #1 pF23 2 Tank Unit #2 pF24 2 Tank Unit #3 pF25 2 Tank Unit #4 pF26 2 Tank Unit #5 pF27 2 Tank Unit #6 pF28 2 Tank Unit #7 pF29 2 Tank Unit #8 pF30 2 Tank Unit #9 pF31 2 Tank Unit #10 pF32 2 Tank Unit #11 pF33 2 Tank Unit #12 pF34 2 Tank Unit #13 pF35 2 Tank Unit #14 pF36 2 Compensator pF37 2 BITE Capacitor #2 pF38 2 Load Select Lbs39 2 Load Select Lbs40 2 Load Select Lbs41 2 Undefined -42 2 Fuel Density Lbs/Gal43 3 Tank Unit #1 pF44 3 Tank Unit #2 pF45 3 Tank Unit #3 pF46 3 Tank Unit #4 pF47 3 Tank Unit #5 pF48 3 Tank Unit #6 pF49 3 Tank Unit #7 pF50 3 Tank Unit #8 pF51 3 Tank Unit #9 pF52 3 Compensator pF53 3 BITE Capacitor #3 pF54 3 Undefined -55 3 Undefined -56 3 Undefined -57 3 Undefined -58 3 Undefined -59 3 Load Select Lbs60 3 Load select Lbs61 3 Load Select Lbs62 3 Undefined -63 3 Fuel Density Lbs/Gal



TABLE 6-38-1Tank Unit Data – Label 241 160 (cont’d)RAW DATA TABLEAll Data Entries are 12-bit Center Justified WordsTable Organization: Words 1-20 raw data for left tank

Word 1 = Tank Unit #1Word 2 = Tank Unit #2Word 3 = Tank Unit #3Word 4 = Tank Unit #4Word 5 = Tank Unit #5Word 6 = Tank Unit #6Word 7 = Tank Unit #7Word 8 = Tank Unit #8Word 9 = Tank Unit #9Word 10 = Tank Unit #10Word 11 = Tank Unit #11Word 12 = Tank Unit #12Word 13 = (Spare)Word 14 = (Spare)Word 15 = BITE Capacitor #1Word 16 = CompensatorWord 17 = Load Select 10,000 DigitWord 18 = Load Select 1,000 DigitWord 19 = Load Select 100 DigitWord 20 = NoneWord 21-40 raw data for right tankWord 21 = Tank Unit #1Word 22 = Tank Unit #2Word 23 = Tank Unit #3Word 24 = Tank Unit #4Word 25 = Tank Unit #5Word 26 = Tank Unit #6Word 27 = Tank Unit #7Word 28 = Tank Unit #8Word 29 = Tank Unit #9Word 30 = Tank Unit #10Word 31 = Tank Unit #11Word 32 = Tank Unit #12Word 33 = (Spare)Word 34 = (Spare)Word 35 = CompensatorWord 36 = BITE Capacitor #2Word 37 = Load Select 10,000 DigitWord 38 = Load Select 1,000 DigitWord 39 = Load Select 100 DigitWord 40 = NoneWords 41-60 raw data for Center TankWord 41 = Tank Unit #1Word 42 = Tank Unit #2Word 43 = Tank Unit #3Word 44 = Tank Unit #4Word 45 = Tank Unit #5Word 46 = Tank Unit #6Word 47 = Tank Unit #7Word 48 = Tank Unit #8Word 49 = Tank Unit #9Word 50 = CompensatorWord 51 = BITE Capacitor #3Word 52 = (Spare)Word 53 = (Spare)Word 54 = (Spare)Word 55 = (Spare)Word 56 = (Spare)Word 57 = Load Select 10,000 DigitWord 58 = Load Select 1,000 DigitWord 59 = Load Select 100 DigitWord 60 = None



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 8 7 6 5 4 3 2 1P SSM A16--------------------------------------------------------------- A1 Octal Label

MSB 214001 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 8 7 6 5 4 3 2 1P SSM A24--------------------------A17 Octal Label

LSB 216011 100 01

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

c-16



TABLE 6-40

RADIO SYSTEMS MANAGEMENT WORD FORMATS

ADF

Function

PAR

ITY

(od

d)

SIG

N/S

TA

TU

SM

AT

RIX

1000 kHz(1)

100 kHz(0)

10 kHz(5)

1 kHz(7) 0.

5 kH

z

SPA

RE

AN

T

BFO

RE

SER

VE

D(S

DI)

LABELADF Frequency

(032)

8 7 60 1 0

5 6 41 1 0

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

2 3 0

[1] When bit no. 14 is “zero”, the radio should tune to the whole kilohertz frequency encoded in the word.When bit no. 14 is “one”, the radio should tune 0.5kHz above this frequency.

[2]

TABLE 6-41

DME

Function

PAR

ITY

(od

d)

SIG

N/S

TA

TU

SM

AT

RIX

10 MHz 1 MHz 0.1 MHz

0.00

/0.0

5 M

Hz

IDE

NT

DIS

PL

AY

ML

S FR

EQ

.

ILS

FRE

Q.

DMEMode

SDI LABELDME Frequency

(035)

8 7 61 0 1

5 4 31 1 0

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

5 3 0

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

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

[3] Bits 15 & 14 codes: VOR (0,0), ILS (0,1) or MLS (1,0). (1,1) is spare.[4] Refer to table in Section 4.1.2 of ARINC Characteristic 709 for mode codes.[5] Although not encoded in the tuning word all VOR & ILS frequencies have 1 as hundreds digit.

Although not encoded in the tuning word all MLS frequencies have 5 as the thousand digit and0 as the hundred digit. Add 5031 MHz to the coded value to obtain the MLS frequency.

[6] (Original note deleted)

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

c-4

Bit Zero One11 BFO off BFO on12 ADF Mode ANT Mode

c-4

c-16

c-10



TABLE 6-42


HF COMWord #1

Function

PAR

ITY

(O

dd)

SIG

N/S

TA

TU

SM

AT

RIX

10 MHz(2)

1 MHz(3)

0.1 MHz(5)

0.01 MHz(7)

0.001 MHz(9)

USB

/LSB

MO

DE

SSM

/AM

MO

DE

WO

RD

ID

EN

T.

LABELHF COM Frequency

(037)

8 7 61 1 1

5 4 31 1 0

2 10 0

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

11 10 9 0 0 0

[1] [2] 7 3 0

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

TABLE 6-42-1HF COMWord #2

Function

PAR

ITY

(od

d)

SIG

N/S

TA

TU

SM

AT

RIX 0.1 kHz

(5)NOT USED

RE

SER

VE

DW

OR

D I

DE

NT

.


(037)

8 7 61 1 1

5 4 31 1 0

2 10 0

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] 7 3 0

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

ALTERNATE FORMTABLE 6-43

HF COMWord #1

Function

PAR

ITY

(od

d)

SIG

N/S

TA

TU

SM

AT

RIX 10MHz

(2)1 MHz

(3)0.1 MHz

(5)0.01MHz

(7)0.001MHz

(9)

WO

RD

ID

EN

T.

SDI LABELHF COM Frequency

(205)

8 7 61 0 1

5 4 30 0 0

2 10 1

Bit No.Example

32 0

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

5 0 2

c-4



TABLE 6-43-1HF COMWord #2

FunctionPA

RIT

Y (

odd)

SIG

N/S

TA

TU

SM

AT

RIX 0.1 kHz

(5)NOT USED

WO

RD

ID

EN

T.

SDI LABELHF COM Frequency

(205)

8 7 61 0 1

5 4 30 0 0

2 10 1

Bit No.Example

32 0

31 30 0 0

29 28 27 260 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

5 0 2


TABLE 6-44ILS

Function

PAR

ITY

(od

d)

SIG

N/S

TA

TU

SM

AT

RIX 10 MHz

(0) 1 MHz (9)

0.1 MHz (3)

0.01 MHz (0)

SPA

RE

ILS

CA

T.

RES. (SDI)

LABEL Frequency (033)

8 7 61 1 0

5 4 31 1 0

2 10 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 13 0 0

12 11 0 0

10 9 0 0

3 3 0

BIT POSITION 12 11

CATEGORY NOTILS CAT IILS CAT IIILS CAT III

0011

0101

TABLE 6-44-1VOR/ILS

Function

PA

RIT

Y (

odd)

SIG

N/S

TA

TU

S M

AT

RIX

10 MHz (0)

1 MHz (9)

0.1 MHz (3)

0.01 MHz (0)

SPA

RE

IL

S C

AT

.

RES.(SDI)

LABEL VOR/ILS Frequency

(034)

8 7 60 0 1

5 4 31 1 0

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

4 3 0

[1] Bit number 14 should be set to “zero” for VOR frequencies and “one” for ILS frequencies by thetuning

information sources.

c- 2

c- 5

c- 5

c- 3



TABLE 6-45

VHF/COM

Function

PAR

ITY

(od

d)

SIG

N/S

TA

TU

SM

AT

RIX 10 MHz

(2)1 MHz

(8)0.1 MHz

(5)0.01 MHz

(3)0.001 MHz

(0) RES(SDI)

LABELVHF COM Frequency

(030)

8 7 60 0 0

5 4 31 1 0

2 10 0

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

0 3 0

TABLE 6-46


ATCTRANSPONDER

Function

PAR

ITY

(od

d)

SIG

N/S

TA

TU

SM

AT

RIX

Pilot Selected Mode A Reply Code

0-7 0-7 0-7 0-7 (3) (6) (2) (0)

A4 A2 A1 B4 B2 B1 C4 C2 C1 D4 D2 D1

CONTROLFUNCTION

AL

T. D

AT

A S

OU

RC

E S

EL

.ID

EN

T.

CO

NT

RO

L F

UN

CT

ION

AL

T. R

EP.

ON

/OFF

RES.(SDI)

LABELBeacon

Transponder Code(031)

8 7 61 0 0

5 4 31 1 0

2 10 0

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

1 3 0

[1]

Bit Zero One111314

Altitude Report OnIdent. OFFUse #1 Alt. Data Source

Altitude Reporting OffIdent. ONUse #2 Alt. Data Source

[2]

Control PanelFunction

Bit

Function 17 16 15 12DABS ON/ASAS OFF

0 0 0 1

Reset AuralWarning Signal

0 0 1 0

Remainder are Reserved for future use.



TABLE 6-47

TACAN Control – Label 146 112

RANGE 126RESOLUTION 1.0RATE 5Hz ±10%

Bit No. Description

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

01 110 4011 60 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)


Table A – Mode Control Table B - SSM

Bits Description27 280 00 11 01 1

RECA/A RECT/RA/A T/R


ValidFunctional TestNo Computed DataNot Used



TABLE 6-48

TACAN Control Word – Label 147 115

Bit No. Function 1 0 Note

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

1

4 Label Number (147)

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)

TACAN 1ANTENNA 2ANTENNA LOBEAUTOTUNEENABLE

TESTX

NORMAL

TACAN 2ANTENNA 1

MANUAL TUNEDISABLEX

NO TESTY

INVERSE

[1]

[2]

[3]

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


TACANMLS WNot UsedMLS Z


RECT/RA/A RECA/A T/R


Valid DataNo Computed DataFunctional TestNot Used

12

34

56

78

910

11N

H

IN

UL

L

LO

BIT

NU

MB

ER

BI

- PO

LA

R

RZ

DA

TA

10

11

01

01

00

11

ATTACHMENT 7DATA BIT ENCODING LOGIC



ATTACHMENT 8OUTPUT SIGNAL TIMING TOLERANCES

PARAMETER HIGH SPEED OPERATION LOW SPEED OPERATIONBit RateTime YTime X

Pulse Rise Time**Pulse Fall Time**

100k bps + 1%10 µsec + 2.5%

5 µsec + 5%1.5 + 0.5 µsec1.5 + 0.5 µsec

12 – 14.5kbpsZ* µsec + 2.5%

Y/2 + 5%10 + 5 µsec10 + 5 µsec

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

** Pulse rise and fall times are measured between the 10% and 90% voltage amplitude points on the leading andtrailing edges of the pulse and include permitted time skew between the transmitter output voltages A-to-ground and B-to-ground. These rise and fall times are for open circuit output measurements – Appendix 1provides waveforms for typical test performance.c-16

HI

NULL

LO

TR

AN

SMIT

TE

D V

OL

TA

GE

LIN

E A

TO

LIN

E B

X

Y


ATTACHMENT 9AGENERAL AVIATION LABELS AND DATA STANDARDS

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

LABEL(OCTAL)

EQPT.ID

(HEX)PARAMETER

NAMEDATATYPE UNITS RANGE

SIGBITS /

DIGITSPOSITIVE

SENSEAPPROX.RESOL

MINXMITINT

(msec)

MAXXMITINT

(msec)

MAXUPDATE

INT NOTES0 0 1 0 2

0 9Distance to goDistance to go

BCDBCD N.M. ±3999.9 5

Always PosAlways Pos 0.1 100 200

0 0 2 0 20 9

Time to goTime to go

BCDBCD Min. 0-399.9 4


0 1 2 0 20 9

Ground SpeedGround Speed

BCDBCD Knots 0-2000 4


0 1 7 1 0 Selected Runway Heading BCD Degrees 0-359.9° 4 Always Pos 0.1° 167 3330 2 4 G 1 1 Selected Course 1 BCD Degrees 0-359° 3 Always Pos 1.0° 167 333 Bit 11 Non Std0 2 7 1 1 Selected Course 2 BCD Degrees 0-359° 3 Always Pos 1.0° 167 3330 3 0 G 0 2

1 6VHF COM FrequencyVHF COM Frequency

BCDBCD

MHzMHz

118-135.975118-135.975

55

0.0250.025

100100

200200

SSM SquelchSSM XMIT

0 3 1 G 0 21 8

Beacon Transponder CodeBeacon Transponder Code

BCDBCD

DiscreteDiscrete

100100

200200 SSM Reply

0 3 2 0 21 2

ADF FrequencyADF Frequency

BCDBCD

KHzKHz

190-1750190-1750

55

0.50.5

100100

200200

0 3 3 0 21 0

ILS FrequencyILS Frequency

BCDBCD

MHzMHz

108-111.95108-111.95

44

0.050.05

167167

333333

0 3 4 G 0 21 01 1

VOR/ILS FrequencyVOR/ILS FrequencyVOR/ILS Frequency

BCDBCDBCD

MHzMHzMHz

108-117.95108-117.95108-117.95

444

0.050.050.05

167167167

333333333

See Att. 9BSee Att. 9BSee Att. 9B

0 3 5 G 0 20 9

DME FrequencyDME Frequency

BCDBCD

MHzMHz

108-135.95108-134.95

44

0.050.05

100100

200200

See Att. 9BSee Att. 9B

0 4 1 0 2 Set Position Latitude BCD Deg:Min 180N-180S 6 North 0.1 250 5000 4 2 0 2 Set Position Longitude BCD Deg:Min 180E-180W 6 East 0.1 250 5000 4 3 0 2 Set Magnetic Heading BCD Deg 0-359° 3 1 .0° 250 5000 6 0 P 0 2 Omega Data Select BNR Discrete 100 200 See Att. 9B0 6 1 P 0 2 Covariance Data BNR 100 200 See Att. 9B0 7 4 G 0 2 Data Record Header DSC Discrete See Note 1 See Att. 9B0 7 5 G 0 2 Active WPT From/To Data DSC Discrete See Note 1 See Att. 9B1 0 0 G 0 2 Selected Course 1 BNR Deg/180 ±180° 12 0.05° 167 333 Bit 11 Non Std1 0 0 1 1 Selected Course 1 BNR Deg/180 ±180° 12 0.05° 167 3331 0 1 G 0 2

2 5Selected HeadingSelected Heading

BNRBNR

Deg/180Deg/180

±180°±180°

1212

0.05°0.05°

31.331.3

62.562.5

Bit 11 Non Std

1 0 2 G 0 2 Selected Altitude BNR Feet 65536 16 Above S.L. 1 100 200 See Att. 9B1 0 5 1 0 Selected Runway Heading BNR Deg/180 ±180° 11 0.1° 167 3331 1 0 1 1 Selected Course 2 BNR Deg/180 ±180° 12 0.05° 167 3331 1 3 G 0 2 Message Checksum BNR See Note 2 See Att. 9B1 1 4 0 2 Desired Track (True) BNR Deg/180 ±180° 12 0.05° 31.3 62.51 1 5 0 2 Waypoint Bearing (True) BNR Deg/180 ±180° 12 A/C To WPT 0.05° 31.3 62.51 1 6 G 0 2 Cross Track Distance BNR Naut Mi 128 18 Fly Left 0.0005 31.3 62.51 1 7 G 0 2 Vertical Deviation BNR Feet 16384 14 Fly Down 1.0 31.3 62.5 See Att. 9B1 2 1 0 2 HORIZ.CMD.(To Autopilot) BNR Deg/180 ±180° 14 Fly Right 0.01° 50 1001 2 2 G 0 2 VERT.CMD. (To Autopilot) BNR Deg/180 ±180° 12 Fly Up 0.05° 50 1001 2 3 0 2 Throttle Command BNR Deg/sec 2.56 18 Inc. Power 0.001° 50 1001 2 5 0 2 Greenwich Mean Time BCD Hr/Min 0-23.59.9 5 0.1 100 2001 4 7 G 0 2 Magnetic Variation BNR Deg/180 ±180° 12 East 0.05° 500 1000 Bit 11 Non Std1 5 0 0 2 Greenwich Mean Time BNR Hr:Min:Sec 23:59:59 5:6:6 1.0 sec 50 100 See Att. 61 5 7 P 0 6 Normalized AOA BNR 1=Stall ±2 12 Upward 0.0005 125 125 1251 6 2 G 1 2 ADF Bearing BNR Deg/180 ±180° 12 0.05° 31.3 62.5 Bit 11 Non Std1 6 3 G 0 2 Wind on Nose BNR Knots 256 9 Head Wind 0.5 50 100 Bit 29 Non Std1 7 3 1 0 Localizer Deviation BNR DDM 0.4 12 Fly Right 0.0001 33.3 66.61 7 4 1 0 Glideslope Deviation BNR DDM 0.8 12 Fly Down 0.0002 33.3 66.62 0 2 0 2

0 9DME DistanceDME Distance

BNRBNR

Naut MiNaut Mi

512512

1616

Always PosAlways Pos

0.0050.005

83.33.3

167167

2 0 4 0 2 Baro Corrected Alt.#1 BNR Feet 131,072 17 Above S.L. 1.0 31.3 62.52 1 0 0 2 True Airspeed BNR Knots 2047.93 15 Always Pos 0.0625 62.5 1252 1 3 0 2 Static Air Temperature BNR Deg C 512 11 Above Zero 0.25 250 5002 2 2 P 0 2 VOR Radial BNR Deg/180 ±180° 12 To Station 0.044° 50 100 See Att. 6

2 2 2 0 21 01 1

VOR OmnibearingVOR OmnibearingVOR Omnibearing

BNRBNRBNR

Deg/180Deg/180Deg/180

±180°±180°±180°

121212

From VORFrom VORFrom VOR

0.044°0.044°0.044°

5031.331.3

10062.562.5

More thanone MKRbeacon bit set isMKR self test.

2 4 1 P Normalized AOA BNR 1-Stall ±2 12 Upward 0.0005 125 125 1252 5 1 G 0 2 Distance To Go BNR Naut Mi 4096 15 Always Pos 0.125 100 2002 5 2 0 2 Time-To-Go BNR Minutes 512 9 Always Pos 1.0 100 2002 6 0 G 0 2 Date BCD Discrete 6 1 Day 500 1000 See Att. 9B2 6 1 P 0 2 GPS Discrete Word 1 DSC Discrete 1000 1000 10002 7 5 G 0 2 LRN Status Word DSC Discrete 200 400 See Att. 9B2 7 7 P 0 2 Cabin DSPY Cont DSC DSC Discrete 200 2003 0 0 G 0 2 STN MAG DEC,

Type & ClassBNR Discrete See Note 2 See Att. 9B

THIS ATTACHMENT WAS REPRODUCEDWITH THE PERMISSION OF GAMA.REVISIONS ARE NOT SHOWN, FOR ANYCOMMENTS OR QUESTIONS, PLEASECONTACT GAMA.


ATTACHMENT 9AGENERAL AVIATION LABELS AND DATA STANDARDS

LABEL(OCTAL)

EQPT.ID

(HEX)PARAMETER

NAMEDATATYPE UNITS RANGE

SIGBITS /

DIGITSPOSITIVE

SENSEAPPROX.RESOL

MINXMITINT

(msec)

MAXXMITINT

(msec)

MAXUPDATE

INT NOTES3 0 1 G 0 2 Message Characters 7-9 BNR Discrete See Note 23 0 2 G 0 2 Message Characters 10-12 BNR Discrete See Note 23 0 3 G 0 2

Message Length / Type / NumberBNR Discrete See Note 2

3 0 4 G 0 2 Message Characters 1-3 BNR Discrete See Note 23 0 5 G 0 2 Message Characters 4-6 BNR Discrete See Note 23 0 6 G 0 2 NAV/WPT/AP Latitude BNR Deg/280 180N-180S 20 North .000172° See Note 23 0 7 G 0 2 NAV/WPT/AP Longitude BNR Deg/180 180E-180W 20 East .000172° See Note 23 1 0 0 2 Present Position Latitude BNR Deg/180 180N-180S 20 North .000172° 100 2003 1 1 0 2 Present Position Longitude BNR Deg/180 180E-180W 20 East .000172° 100 2003 1 2 0 2 Ground Speed BNR Knots 4096 15 Always Pos 0.125 25 503 1 3 0 2 Track Angle (True) BNR Deg/180 ±180° 12 0.05 25 503 1 4 0 2 True Heading BNR Deg/180 ±180° 15 0.0055° 25 503 1 5 0 2 Wind Speed BNR Knots 256 8 Always Pos 1.0 50 1003 1 6 0 2 Wind Angle (True) BNR Deg/180 ±180° 8 0.7 50 1003 2 0 0 2 Magnetic Heading BNR Deg/180 ±180° 15 0.0055° 25 503 2 1 0 2 Drift Angle BNR Deg/180 ±180° 12 0.05° 25 503 2 6 G 0 2 Lateral Scale Factor BNR Naut Mi ±128 15 0.0039 NM 80 12003 2 7 G 0 2 Vertical Scale Factor BNR Feet ±2048 15 0.0625 Ft 80 12003 5 1 G 0 2 Distance To Destination BNR Naut Mi 32,768 18 Always Pos 0.125 500 10003 5 2 G 0 2 Est Time to Destinaiton BNR Minutes 4096 12 Always Pos 1.0 500 1000 Via Flight

Plan3 5 3 P 0 2 Dest Local Time Offset BCD Hour/Min 23:59 5 Always Pos .01 Min 1000 1000 1000 Via Flight

Plan3 7 1 G 0 2

0 91 01 11 21 61 8

Specific Equipment IdentSpecific Equipment IdentSpecific Equipment IdentSpecific Equipment IdentSpecific Equipment IdentSpecific Equipment IdentSpecific Equipment Ident

DSCDSCDSCDSCDSCDSCDSC

500500500500500500500

1000100010001000100010001000

See Att. 9B

NOTE 1: These labels are transmitted once at the beginning of each flight plan/graphics map data transfer. Refer to the GAMA FMS Output BusStandard for further information.

NOTE 2: These labels are used to make up the individual records that comprise a flight plan/graphics map data transfer. Not all labels are transmittedwith each record. Ten records are transmitted in one second. Refer to the “FMS Waypoint/Navaid/Airport Data Transfer Protocol”,addendum 3.



ATTACHMENT 9BGENERAL AVIATION WORD EXAMPLES

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

P SSM See Chapter 3 See Below SDIVOR/ILS Frequency

Label 034G

Bit 11Bit 12Bit 13

Marker SensitivityLast Tune Source

VOR Digital Filtering

“1” denotes high, “0” denotes low“1” denotes control head. “0“ denotes other“1” denotes no filter. “0” denotes filter(Normally “1” but “0” for Honeywell (Olathe) manufactured equipment)

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

P SSM See Chapter 3 See Below SDIDME Frequency

Label 035G

Bit 13 12 11 DME Mode

00001111

00110011

01010101

StandbyDirected Freq #1Directed Freq #2Directed Freq #3Hold Freq #1Hold Freq #2Not usedSpare

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

Binary AddressOmega Data Select

Label 060P

*Specific user wordBit 28Bit 27

Full Restart BitRho Rho Updating

“1” denotes restart“1” inhibits update

Bit 26 25 Function0011

0101

No ActionRelaneDo Not ReleaseInvalid Use

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

P SSMTermIndent -

Exponent (IEEE Flt. Pt.)MSB

Mantissa (IEEE Flt. Pt.)Coveriance Data*

Label 061P

*Specific user wordBit 27 Sign “1” denotes negative

Bit 29 28 Functions0011

0101

Term 1Term 2Term 3Not Used

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

P SSMPad

(Zeros)Pad

(Zeros) MSBNumber of Records

Data Record HeaderLable 074G

Bit 21 Prior Record Change “1” denotes changed record

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

P SSM 0From Waypoint

LS ByteTo Waypoint

LS ByteFrom Waypoint

MS ByteTo Waypoint

MS ByteSee

BelowActive Waypoint From/To Data

Label 075G

Bit 9Bit 10Bit 11Bit 12

Auto/Leg/Man/ObsMag/True ReferenceRadar Waypoint DisplayedLat/Long/ILS Mode

“1” denotes Auto/Leg, “0” denotes Man/Obs“1” denotes True, “0” denotes Magnetic“1” inhibits display“1” denotes ILS, “0“ denotes Lat/Long

These areUser

Specificbits

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 Same as Attachment 2 SDISelected Altitude

Label 102G

Bit 11Bit 12

Altitude Select KnobAltitude Alert

“0” denotes “in motion”“1” denotes “on”

User-specificbits




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 Check SumMessage Check Sum

Label 113G

The message checksum is the two’s complement 21 but sum of all the other words transmitted in the group discarding the intermediatecarry and replacing bit 32 with odd parity.

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

P SSM+-

DataSee

BelowSDI

Vertical DeviationLabel 117G

Bit 14Bit 13Bit 12Bit 11

VNAV Arm Enable/AlertVNAV BendoverVNAV Bendover DirectionAltitude with respect to 1000 ft.

“1” denotes enable“1” denotes “capture”, “0” denotes “track”“1” denotes “fly up”, “0” denotes flydown”“1” denotes “greater”, “0” denotes less

UserSpecific

bits

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

Day Month Year SDIP SSM

10s 1s 10s 1s 10s 1s

DateLabel 260G

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

P SSM SpareWaypoint Number

(Binary)See

BelowWords inMessage

Message Length/Type/No.Label 303G

Bit 16 Date Record “1” denotes “off route”, “0” denotes “on route”

Bit 24 FMS Plan Mode “1” denotes “SELECT”, “0” denotes “not SELECT”

Bit 25 WPT at Plan Center “1” denotes “CENTER”, “0” denotes “not CENTER”

Bit 26 Flight Plan GAP Follows “1” denotes “GAP”, “0” denotes “no GAP”

Bit 15 14 13 WYPT/STATION TYPE00001111

00110011

01010101

WaypointNav AidAirportNDBAltitude Profile PointNo SymbolVORIntersection




Bit No. Function Bit Status1 0

12345678

Label261G 02LRN Status

x

xx

x

x

xxx

910

SDI

1112

SparePad Zero

13141516171819

Reserved

20 Vert Dev (Final Appr) Angular Linear21 Lat Dev Scaling in Transition Yes No22 Lat Dev. (Final Appr) Angular Linear23 Appr Integrity (Final Appr) Valid Invalid24 GPS Integrity Fail Valid

252627

GPS Annunciation27(0) & 26(0) & 25(0) – Enroute27(0) & 26(0) & 25(1) – Terminal27(0) & 26(1) & 25(0) – Approach(27(1) & 26(0) & 25(0) – Oceanic

2829

Spare

3031

SSM31(0) & 30(0) – Normal Operations31(0) & 30(1) – No Computed Data31(1) & 30(0) – Functional Test31(1) & 30(1) – Not used

32 Parity (odd)





12345678


x

xxxx

x

x

x

910

SDI

11 Waypoint Alert On Off12 Dead Reckon DR Not DR13 Direct To Select Not Select

1415

Mode15(0) & 14(0) – Multiple Sensor Based15(0) & 14(1) – VOR/DME Offset (RNAV) Approach15(1) & 14(0) – VOR/TACAN (non-Offset)

Approach/Enroute15(1) & 14(1) – ILS Approach

16 Vert & Lat Dev Scaling Approach Enroute17 FMS Controlled Hdg Sub-mode FMS/FGS FGS Only18 Remote FGS Army for Nav Capt Arm No Change19 FMS Plan Mode Select Not Select20 Display Final Appr Course Display No Change21 Angular Scaling Active Not Active22 Integrity Warn Warn Not Warn23 To To Not To24 From From Not From25 Parallel XTK Offset Selected Not Selected26 Airport Display Selected Select Not Selected27 Message Alert On Off28 True/Mag True Magnetic29 HSI Valid (NAV Warn) Valid Warn3031

SSM

32 Parity (odd)

THIS ATTACHMENT WAS REPRODUCEDWITH THE PERMISSION OF GAMA.REVISIONS ARE NOT SHOWN, ANYCOMMENTS OR QUESTIONS, PLEASECONTACT GAMA.




12345678


x

xxxxxx

x

910

SDI (if required)

11 Play Briefing #112 Play Briefing #213 Play Briefing #314 Play Briefing #415 Play Briefing #516 Play Briefing #617 Cancel Briefing #118 Cancel Briefing #219 Cancel Briefing #320 Cancel Briefing #421 Cancel Briefing #522 Cancel Briefing #623 Annunciate Cabin Message (Note)2425262728

Spares Pad Zero

29 Alternate Format ALTERNATE STD3031

SSM31(0) & 30(0) – Normal Operation31(0) & 30(1) – No Computed Data31(1) & 30(0) – Functional Test31(1) & 30(1) – Failure Warning

32 Parity (Odd)

NOTE: The ALTERNATE FORMAT bit (#29) causes the briefing play (BITS 11 – 16) and briefing cancel (BITS 17– 22) controls to be interpreted as the briefing number from 1 to 63 with the briefing #1 bit as the leastsignificant. If BIT 29 is set to 1, this decoding will be used. If the briefing number is non zero, the indicatedbriefing will be played or canceled.





12345678

Label300 02Station Declination

xx

xxxxxx

91011121314

Spares Pad Zero

1516

DMETuned and Received

Not CollatedBeing Received

Same LocationNot Received

1718192021222324

Station DeclinationBinary number with sign bit 24 East is positive. West is2’s complement of the positive value. Range is 127 deg.E/W. Resolution is 1 degree at bit 17.

252627

VOR at locationDME at locationTACAN at location

YesYesYes

NoNoNo

2829

Class Bit 29/28/0 low 0/1 high 1/0 terminal

3031

SSM

32 Parity




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

PCompany Private

UseCompany I. D.

(Binary)EQ Code

MSD (Hex)EQ Code

MSD (Hex) SDI

GA EquipmentIdent

LABEL 371

LABEL 371Company I. D. Field

Binary Bit Assignments COMPANY

24 23 22 21 20 19

0 0 0 0 0 1 B&D INSTRUMENTS0 0 0 0 1 0 BEECH AIRCRAFT0 0 0 0 1 1 BENDIX AVIONICS0 0 0 1 0 0 CANADIAN MARCONI0 0 0 1 0 1 CESSNA AIRCRAFT0 0 0 1 1 0 COLLINS AVIONICS0 0 0 1 1 1 DELCO ELECTRONICS0 0 1 0 0 0 FOSTER RNAV0 0 1 0 0 1 GABLE CONTROLS0 0 1 0 1 0 GLOBAL SYSTEMS0 0 1 0 1 1 GULFSTREAM AEROSPACE0 0 1 1 0 0 HONEYWELL0 0 1 1 0 1 KING RADIO0 0 1 1 1 0 LEARJET0 0 1 1 1 1 LITTON AERO PRODUCTS0 1 0 0 0 0 OFFSHORE NAVIGATION0 1 0 0 0 1 RACAL AVIONICS0 1 0 0 1 0 SPERRY0 1 0 0 1 1 UNIVERSAL NAVIGATION SYS0 1 0 1 0 0 3M AVIATION SAFETY SYSTEMS0 1 0 1 0 1 ALLIEDSIGNAL GENERAL AVIATION AVIONICS0 1 0 1 1 0 ALLIEDSIGNAL GLOBAL WULFSBERG0 1 0 1 1 1 BF GOODRICH AVIONICS0 1 1 0 0 0 GARMIN0 1 1 0 0 1 ARNAV0 1 1 0 1 0 COMPUTER INSTRUMENT CORPORATION0 1 1 0 1 1 SPARE

1 1 1 1 1 1 SPARE

THIS ATTACHMENT WAS REPRODUCEDWITH PERMISSION OF GAMA.REVISIONS ARE NOT SHOWN, FOR ANYCOMMENTS OR QUESTIONS, PLEASECONTACT GAMA.


ATTACHMENT 9CGENERAL AVIATION EQUIPMENT IDENTIFIERS

Equipment HEXID

EQUIPMENT

01 Flight Control Computer

02 Flight Management Computer

04 Inertial Reference System

05 Attitude and Heading Ref. System

06 Air Data System

09 Airborne DME

0B Global Positioning System

10 Airborne ILS Receiver

11 Airborne VOR Receiver

12 Airborne ADF System

16 Airborne VHF Comm Receiver

18 ATC Transponder

25 Electronic Flight Instruments

27 Microwave Landing System

36 Radio Management System

5A Loran

5B Omega

A9 Airborne DME Controller

B0 Airborne ILS Controller

B2 Airborne ADF Controller

B6 VHF Comm Controller

B8 ATC Transponder Controller

C7 Microwave Landing System Controller

FA Loran Controller

FB Omega Controller



ATTACHMENT 10MANUFACTURER SPECIFIC STATUS WORD

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

PCompany

Private Use [A]Company I.D.

(Binary)Label(171)

BIT 16 15 14 13 12 11 Company 0 0 0 0 0 1 0 0 0 0 1 0 0 0 0 0 1 1 0 0 0 1 0 0 0 0 0 1 0 1 0 0 0 1 1 0 0 0 0 1 1 1 0 0 1 0 0 0 0 0 1 0 0 1 0 0 1 0 1 0 0 0 1 0 1 1 0 0 1 1 0 0 0 0 1 1 0 1 0 0 1 1 1 0 0 0 1 1 1 1 0 1 0 0 0 0 0 1 0 0 0 1 0 1 0 0 1 0 0 1 0 0 1 1 0 1 0 1 0 0 0 1 0 1 0 1 0 1 0 1 1 0 0 1 0 1 1 1 0 1 1 0 0 0 0 1 1 0 0 1 0 1 1 0 1 0 0 1 1 0 1 1

1 1 1 1 1 1

B&D INSTRUMENTSBEECH AIRCRAFTBENDIX AVIONICSCANADIAN MARCONICESSNA AIRCRAFTCOLLINS AVIONICSDELCO ELECTRONICSFOSTER RNAVGABLES CONTROLSGLOBAL SYSTEMSGULFSTREAM AEROSPACEHONEYWELLKING RADIOLEAR JETLITTON AERO PRODUCTSOFFSHORE NAVIGATIONRACAL AVIONICSSPERRYUNIVERSAL NAVIGATION SYSTEMS3M AVIATION SAFETY SYSTEMSALLIED SIGNAL GENERAL AVIATION AVIONICSALLIED SIGNAL GLOBAL WULFSBAGBF GOODRICH AVIONICSGARMINARNAVCOMPUTER INSTRUMENT CORPORATIONSPARE

SPARE

[A] This word is used for manufacturer-specific information exchange (e.g., sub-LRU-Level BITE status). TheCompany I.D. fields should be used to differentiate each manufacturers’ unique use of the Company PrivateUse field.


ATTACHMENT 11SYSTEM ADDRESS LABELS

c-14

c-16

c-15

SYSTEMS SYSTEM ADDRESS LABEL(OCTAL)

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

c-16

c-14

c-16

c-16

c-16

c-15



SYSTEMS SYSTEM ADDRESS LABEL(OCTAL)

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

c-14

c-16

c-14

c-16

c-14

c-15

c-16


APPENDIX ALABORATORY VERIFICATION OF ARINC 429 DITS ELECTRICAL CHARACTERISTICS

A1-1.0 Introduction

Selection of the electrical characteristics of the Mark 33 DITS followed verification of the suitability of proposed values inlaboratory tests performed by the Boeing Commercial Airplane Co. Boeing presented two reports to AEEC’s SystemsArchitecture and Interfaces Subcommittee on these activities, one at the meeting held in Arlington, Virginia, in March 1977and the other at the meeting held in Los Angeles, California, in May 1977. The material in this Appendix is excerpted fromthese reports.

A1-2.0 Electromagnetic Emission and Susceptibility Tests

Electromagnetic emission and susceptibility tests were conducted to determine if the proposed 100 kbps waveform wassuitable for use in a commercial airplane EMI environment. The EMI conditions used for the tests were derived fromRTCA Document DO-160, “Environmental Conditions and Test Procedures for Airborne Electronic/Electrical Equipmentand Instruments” dated February 28th, 1975.

A1-2.1 Cable and Test Configuration

The cable used for the tests was standard aircraft type twisted shielded wire of 22 AWG. The wire configuration consistedof approximately 60 ft. of cable which was subjected to the EMI environment within a screened room. This cable wasconnected in series with 300 ft. of cable not subjected to the EMI environment. The test was configured to simulate themaximum length wire run with DO-160 conditions applied.

The 60 Ft. length of cable was connected to the transmitter for the emission tests and to the receiver for the susceptibilitytests.

A1-2.2 Transmitter Characteristics

The block schematic of the bipolar line driving transmitter built for the tests is shown in Figure a-(i). The waveform wasshaped at the pulse generator such that it exhibited the following characteristics:

Differential Output Voltage:HI +10VNULL 0VLO -10VRisetime = Falltime = l.0 µ secBit Rate= 100 kilobits/secondHI time= NULL time= LO time

A1-2.3 Receiver Input Circuit Description

To perform the susceptibility tests, receivers were constructed utilizing various methods of common mode rejection andvarious processing schemes.

Differential Amplifier Input. Figure a-(ii) shows schematics of the differential input stages used for the receivers. Thedifferential amplifier input stage required resistors to local ground at the input to provide a path for the input current for thevoltage followers. Voltage protection was used to prevent damage to the voltage followers in the event of high voltage,common mode spikes. The voltage follower stages provided a controlled impedance for the differential amplifier stage.

Opto-Isolator Input The opto-isolator input stage utilized two H-P 5082-4371 isolators connected in opposite polarity todetect the bipolar data. The HP 5082-4371 input has a forward conduction “knee” at approximately 1.4 volts. A secondsimple LED (HP 5082-4650) was connected in series with each opto-isolator to provide a combined knee voltage ofapproximately 3 volts. A series resistor RL of 1000 ohms was placed in series with the LED/opto-isolator network to limitthe receiver current to 7mA at 10 volts (differential) applied at the input. At 4.5V differential on the line, one opto-isolatorconducts 1.5 mA.

One circuit configuration which enables the opto-isolator to operate at 100 kilobits per second at these low input currents isshown in figure a-(iii). A potential of +15 volts is applied to pin 8 to provide maximum gain in the first transistor. Duringconduction, a charge on the second transistor is discharged via pin 7 and R2 to a potential of +0.5 volts set by R1 and R3.Discharging to a +0.5 volt potential reduces the possibility of a loss of the first bit following a long null period. Thisproblem has been observed when discharging pin 7 to ground potential.



FIGURE a-(i)BIPOLAR TRANSMITTER BLOCK SCHEMATIC

DETAIL OF LINE DRIVER AND TERMINATION

LM0002

LM0002

2R o

L 1

L 1

P U L S EG E N E R A T O R

+

_

P S E U D OR A N D O MB I T S E Q U E N C EG E N E R A T O R

S W I T C H I N GL O G I C

S H A P E DB I P O L A R

R Z

L I N ED R I V E R

T E R M I N A T I O N

2R o



FIGURE a-(ii)RZ BIPOLAR RECEIVER INPUT TYPES TESTED

R > 12 K Ohms (Provides Path for V. F. Input Current)

Figure (a) Differential amplifier input schematic.

RL = CURRENT LIMITING = 1000 OHMSLED = LED IN SERIES WITH OPTO ISOLATOR TO PROVIDE ON NULL LEVEL

OPTO-ISOL = H-P 5082-4371

Figure (b) OPTO-ISOLATED INPUT SCHEMATIC

L 1

O P T O

I S O L A T O R S

L 2

R L

L E DL E D

OVER

VOLTAGE

PROTECTION

D I F F E R E N T I A LA M P L I F I E R

V O L T A G EF O L L O W E R S

R

R

ZERO’SONE’S



A1-2.4 Receiver Data Detection Technique

Two data detection schemes were used, (i) data sampling (sample and decision) and (ii) integrate and dump (Figure a-(iv).

The data sampling system detects positive-going or negative-going edges which exceed ±3 volts differential voltage.The edges cause a timing circuit to time for approximately 2 µsec. When the timing circuit has timed out, a sample ofthe input is taken. If the sample is HI, a ONE is declared. If the sample is LO, a ZERO is declared. If the sample isNULL, and error diagnostic can be output, since a NULL state is known to be invalid at the data sampling time. Anerror diagnostic will be output if, for example, during a period of NULL on the line, a short-duration noise spike causesthe input to exceed the ±3V threshold, so initiating the edge detector timing circuit, but dissipates rapidly so that aNULL is estimated at the data sampling time.

The integrate-and-dump processor circuit detects positive or negative-going edges which exceed the ±3V differentialthreshold. The edge detection causes an integration circuit to integrate the input voltage for a period of 5 µsec. Theoutput of the integrator is sampled (timing is derived from the edge detector) at the end of the integration period. If it isabove zero voltage, a ONE is declared; if it is below zero voltage, a ZERO is declared.

A threshold level could be introduced about zero voltage to provide an indication of the total energy contained in thepulse. If the integrator output fell within the threshold, an error diagnostic could be presented indicating the at thedetection of the bit was marginal.

A1-2.5 Test Data Message

The test waveform was a continuous pseudo-random bit pattern. This continuous pattern did not test the initialsynchronization or “false-alarm” aspects in a word-by-word transmission environment with NULL on the transmissionline between words.

A1-2.6 Emission of RF Energy Test Results

The following tests were performed under conditions of light (one receiver) and heavy (20 receivers) line loading.

A. Conducted RF Interference (RTCA DO-160 Paragraph 21.2)The interference measured was within the limits specified in DO 160 Figure 21-2.

B. Radiated RF Interference (RTCA DO-160 Paragraph 21.3)The interference measured was within the limits specified in DO-160 Figure 21-5.

It should be noted that the 20dB limit exceedance permitted in DO 160 was not taken. The transmitter output spectrumcan be further improved by the addition of filtering to attenuate output frequencies above those of interest in the digitaldata.

A1-2.7 Susceptibility Test Results

The tests were performed to determine the susceptibility of the Mark 33 DITS to RF, AF and spike interference levelsspecified in DO-160 under conditions of light (one receiver) and heavy (20 receivers) line loading.

The following receiver configurations were tested:

(i) Differential Amplifier input, time sample processing(ii) Differential Amplifier input, integrate-and-dump processing(iii) Opto-isolator input, time sample processing(iv) Opto-isolator input, integrate-and-dump processing

The data transmitted consisted of a continuous pseudo-random bit sequence. Error checking was made on a bit-by-bitbasis.

A. Conducted RF Susceptibility (DO-160 Paragraph 20.20B Category Z)No bit errors were detected with RF applied to any of the line loading and receiver configurations.

B. Magnetic Fields Induced Into Interconnecting Cables (DO-160 Paragraph 19.3)Test performed at a level above those specified in DO-160 Figure 19-1. No bit errors were detected with thefield applied to the cable for any cable loading or receiver configuration.



FIGURE a-(iii)OPTO-ISOLATOR FRONT-END CIRCUIT SCHEMATIC

5 V15 V

R 45.6k

8

6

5

O/P

HP - 5082 - 43715 V

R110k

R2500

R31k

7

2

3



FIGURE a-(iv)DATA DETECTION

(a) SAMPLE –AND- DECISION

( b ) INTEGRATE – AND - DUMP

LEGEND:

E = EDGE DETECT (BIT TIMING)

D = DELAY

S = SAMPLE

I = INTEGRATION INTERVAL

DMP = DUMP INTEGRATOR CHARGE

HINULL

LO

BIT N BIT N + 1

T +T -

S

D

E

ZERO

D

E S

HINULL

LOS

I

E

DMP S

I

E

DMP

T+T-



C. Electric Fields Induced Into Interconnecting Cables (DO-160 Paragraph 19.4)The tests were perform with voltage levels above those specified in DO 160 Figure 19-1 Category Z. No biterrors were detected with the field applied for any cable loading or receiver configuration.

D. Spikes Induced Into Interconnecting Cables (DO-160 Paragraph 19.5, Category Z)The spikes were generated and applied to the cable as shown in DO-160, Figure 19-4. Bit errors were countedduring the application of 50 transients and also following the transient test. The following results wereobserved:

Receiver Configuration Line LoadingLight Heavy

Diff. Amp., Sample Det 0 0Diff. Amp., Int. & Dump Det 0 0Opto-Isolator, Sample Det 8 15Opto-Isolator, Int & Dump Det 0 1

All configurations performed with zero bit errors for approximately 107 bits following the transient test.

A1-3.0 Pulse Distortion Tests For Typical Aircraft wire Installations

Laboratory testing and computer simulation studies were conducted to investigate the pulse distortion introduced ontypical aircraft wire installations.

A1-3.1 Laboratory Tests

Receivers and a transmitter were constructed to operate using the DITS high speed (100 KBPS) waveform. Lengths oftwisted shielded cable were connected to form a representative wiring configuration for digital data. The wire length andstub configuration were selected to represent postulated installations on a B747 airplane. The cable used for lab testswas 20 and 22 AWG twisted shielded cable with wrapped KAPTON insulation, no. BMS B-51, Class 2 type III. Thepulse distortion at the receiver nodes of the wiring systems were recorded. The characteristics of the 20 AWG cablewere measured and used to develop the cable model used in the computer simulation.

A1-3.2 Computer Simulation

A computer program was developed to evaluate pulse distortion on lines with stubs. The DITS transmitter impedanceand voltage waveform was modeled. The cable model was developed from the measured cable characteristics. TheDITS receiver input impedance was modeled.

The computer simulation was run and results were plotted for various line length and stub configurations representingpostulated installations on a B747 airplane.

A1-3.3 Results

The results of the laboratory tests and computer simulation for the same cable configuration showed good agreement,with a maximum difference of 0.4 volts on rising and falling edges. The computer simulation showed slightly highercable loss effect than the lab test. The lab test results were recorded using an oscilloscope camera; the computer resultswere plotted. Only the plotted results are presented here.

Figure a-(v) shows the schematic for the first simulation. This configuration represents a transmitter, a receiver and asingle length of twisted shielded cable 200 feet long. The cable is modeled as Blocks 1 to 4, for later stub connection.

At the transmitter and receive ends of the cable, the shields are grounded via a 0.05 µH inductor (which models theinductance of the ground lead). At other nodes, the shields and cable inners are carded through, representing acontinuous length of cable.

Figure a-(vi) Transmitter open circuit differential output voltage. This waveform was used for all the simulation runs.

Figure a-(vii) The transmitter output voltage and receiver input voltage for the configuration in Figure a-(v).

Figure a-(viii) shows the schematic for the second simulation. This configuration represents a transmitter at an enginelocation, with receivers at the equipment bay and the flight deck. Four receiver loading configurations are shown withmaximum loading of twenty receivers. The waveforms for this simulation run are shown in Figures a-(ix) through a-(xvi).



Figures a-(ix) and a-(x) Transmitter and receiver waveform for loading configuration 1.

Figures a-(xi) to a-(xvi) Waveforms for loading configurations 2, 3 and 4.

Figure a-(xvii) shows the schematic for the third simulation. This configuration represents a transmitter at the flightdeck with receivers at the equipment bay, the inner engine and the outer engine.

Figures a-(xviii) to a-(xxi) Waveforms for the third simulation.

Figure a-(xxii) shows the schematic for the fourth simulation. This configuration represents a transmitter at theequipment bay with receivers at the equipment bay, the flight engineer’s panel, the first officer’s panel and the captain’spanel.

Figures a-(xxiii) to a-(xxvi) Waveforms for the fourth simulation.

Figure a-(xxvii) shows the schematic for the fifth simulation. This is a long line simulation and is included to show theoperation of the system with lines longer than would realistically be used in a “B747-sized” airplane. This configurationrepresents a transmitter with one receiver close (10 feet) and one receiver remote (500 feet).

Figures a-(xxviii) and a-(xxix) Waveforms for the “long line” configuration.

A1-3.4 Conclusions

From laboratory tests and simulations, it is concluded that no intolerable bit distortion is introduced into the “high speedDITS” waveform due to cable lengths and stub configurations likely to be encountered on a “B747-size” transportaircraft.

If installations are anticipated involving longer line lengths or cables with radically different electrical characteristics,then further investigation may be required.



FIGURE a-(v)

TRANS (58m)

BUSLIN1

(1m)BUSLIN

2

SHIELD1

SHIELD2

(1m)

BUSLIN3

(1m)BUSLIN

4

SHIELD3

SHIELD4

REC 1

100k

TERM

* SHIELD TIED TO INDUCTORON TERM

A

B

1

2

3

4

5

6

.01

.01 40

40

.1

.1

1 1 1 111

2

2

2 2 22

22

2

1 111 2

3 333

4 44 4

5 55 5

66 6 6

TRANSMITTER

BMS 13-51 20 AWG TSP 200 100 k

* *

TRANS

ALLL’s

.05µµµµh



FIGURE a-(vi)

TRANSMITTER LEAD A TO LEAD B VOLTAGE

Am

plit

ude

Vol

ts

Time (microseconds)



FIGURE a-(vii)

TRANSMITTER OUTPUT VOLTAGE

OPEN CIRCUIT VOLTAGE AT RECEIVER ONE

Am

plit

ude

Vol

ts

Time (microseconds)

Am

plit

ude

Vol

ts

Time (microseconds)



FIGURE a-(viii)

TRANS

Configuration# LoadRec 1

# LoadRec 2

1 1 12 1 103 10 14 10 10

ALLL’s.05

REC 1

RECEIVERTWO

TRANSMITTER

85 FEET200 FEET

10 FEET

RECEIVEROne

REC 2

(3.05m)BUSLIN 5

SHIELD 5

1

1

1

2

2

2

3

4

5

6

TRANS(61m)

BUSLIN 1

(10m)

BUSLIN 2

SHIELD 1 SHIELD 2

(10m)

BUSLIN 3

(6m)

BUSLIN 4

SHIELD 3 SHIELD 4

REC 1

TERM

* SHIELD TIED TO INDUCTORON TERM BLOCK

1

2

3

4

5

6

.01

.01 40

40

.1

.1

1 1 1 111

2

2

2 2 22

22

2

1 111 2

3 333

4 44 4

5 55 5

66 6 6

1 2 3 4 5 76 8 9

50pf6k

40pf16.5k

45pf 15k

1

2

** **

**

Node1

hµ



FIGURE a-(ix)


VOLTAGE AT FIRST NODE

CO

NF

IGU

RA

TIO

N 1

CO

NF

IGU

RA

TIO

N 1

Am

plit

ude

Vol

ts

Time (microseconds)

Am

plit

ude

Vol

ts

Time (microseconds)



FIGURE a-(x)

VOLTAGE AT RECEIVER ONE

VOLTAGE AT RECEIVER TWO

CO

NF

IGU

RA

TIO

N 1

CO

NF

IGU

RA

TIO

N 1

Am

plit

ude

Vol

tsA

mpl

itud

e V

olts

Time (microseconds)

Time (microseconds)



FIGURE a-(xi)



CO

NF

IGU

RA

TIO

N 2

CO

NF

IGU

RA

TIO

N 2

Am

plit

ude

Vol

ts

Time (microseconds)

Am

plit

ude

Vol

ts

Time (microseconds)



FIGURE a-(xii)


VOLTAGE AT RECEICER TWO

Am

plit

ude

Vol

ts

Time (microseconds)

Am

plit

ude

Vol

ts

Time (microseconds)

CO

NF

IGU

RA

TIO

N 2

CO

NF

IGU

RA

TIO

N 2



FIGURE a-(xiii)



CO

NF

IGU

RA

TIO

N 3

CO

NF

IGU

RA

TIO

N 3

Am

plit

ude

Vol

tsA

mpl

itud

e V

olts

Time (microseconds)

Time (microseconds)



FIGURE a-(xiv)



CO

NF

IGU

RA

TIO

N 3

CO

NF

IGU

RA

TIO

N 3

Time (microseconds)

Am

plit

ude

Vol

tsA

mpl

itud

e V

olts

Time (microseconds)



FIGURE a-(xv)



CO

NF

IGU

RA

TIO

N 4

CO

NF

IGU

RA

TIO

N 4

Am

plit

ude

Vol

ts

Time (microseconds)

Am

plit

ude

Vol

ts

Time (microseconds)



FIGURE a-(xvi)



CO

NF

IGU

RA

TIO

N 4

CO

NF

IGU

RA

TIO

N 4

Am

plit

ude

Vol

ts

Time (microseconds)

Am

plit

ude

Vol

ts

Time (microseconds)



FIGURE a-(xvii)

ALLL’S.05

TR

AN

SMIT

TE

R

8 5 F E E T 1 5 0 F E E T

1 0 F E E T

R E CT W O

5 0 F E E T

5 0 F E E T

R E CT H R E E

5 0 F E E T

T R A N S (26m)

BUSLIN 1

S H I E L D1

(15m)

BUSLIN 3

(3.05m)

BUSLIN 4

S H I E L D3

S H I E L D4

R E C 1

T E R M

* S H I E L D T I E D T O I N D U C T O RO N T E R M B L O C K

1

2

3

4

5

6

.01

.01 4 0

4 0

.1

.1

1 1 11

2 22

22

2

1 11 2

3 33

44 4

5 55

6 6 6

h

1 2 3 4 5 76 8 9

5 0 p f6 k

4 0 p f 1 6 . 5 k

4 5 p f 1 5 k

1

2

1L O A D

N O D E1

N O D E2

N O D E3

(46m)

BUSLIN 2

S H I E L D2

1

2

2

1

3 6

1

2

4

5

(15m

)

BU

SLIN

6

SHIE

LD

6

1

2

2 136

1 2

4 5

RE

C 3 1

L O A D

(3.0

5m)

BU

SLIN

5

SHIE

LD

5

1

2

2 136

1 2

4 5

RE

C 2 1 0

L O A D S

T R A N S R E C 1

**

**

µ

* * * * * * **

1

1 0 F E E T



FIGURE a-(xviii)



Time (microseconds)

Am

plit

ude

Vol

ts

Time (microseconds)

Time (microseconds)

Am

plit

ude

Vol

ts



FIGURE a-(xix)



Time (microseconds)

Am

plit

ude

volt

s

Time (microseconds)

Am

plit

ude

Vol

ts



FIGURE a-(xx)

VOLTAGE AT SECOND NODE

VOLTAGE AT RECEIVER THREE

Time (microseconds)

Am

plit

ude

Vol

tsA

mpl

itud

e vo

lts

Time (microseconds)



FIGURE a-(xxi)

VOLTAGE AT THREE NODE

Am

plit

ude

Vol

ts

Time (microseconds)

AR

INC

SPE

CIF

ICA

TIO

N 429, P

AR

T 1 - P

age 154AP

PE

ND

IX A

LA

BO

RA

TO

RY

VE

RIF

ICA

TIO

N O

F A

RIN

C 429 D

ITS E

LE

CT

RIC

AL

CH

AR

AC

TE

RIST

ICS

FIG

UR

E a-(xxii)

ALLL’S.05

TRANS (1.5m)

BUSLIN1

SHIELD1

(6.1m)

BUSLIN3

(6.1m)

BUSLIN4

SHIELD3

SHIELD4

REC 1

TERM* SHIELD TIED TO INDUCTOR

ON TERM BLOCK

1

2

3

4

5

6

.01

.01 40

40

.1

.1

1 1 11

2 22

22

2

1 11 2

3 33

44 4

5 55

6 6 6

h

1 2 3 4 5 76 8 9

50pf6k

40pf 16.5k

45pf 15k

1

2

1LOADNODE

1

NODE2

NODE3

(26m)

BUSLIN2

SHIELD2

1

2

2

1

3 6

1

2

4

5

(1.5

m)

BU

SLIN

5

SHIE

LD

5

1

2

2 136

1 2

4 5

RE

C 2

1 L

OA

D

TRANS REC 1

(6.1

m)

BU

SLIN

6

SHIE

LD

6

1

2

2

1

36

1 2

4 5

RE

C 3

1 L

OA

D

(6.1

m)

BU

SLIN

7

SHIE

LD

7

1

2

2 136

1 2

4 5

RE

C 4

1 L

OA

D

TRANSMITTER5 FEET 85 FEET

5 FEET

RECTWO

20 FEET

20 FEET

RECTHREE

20 FEET

20FEET

RECFOUR

µ

* * * * * * * *

*

**

*

**



FIGURE a-(xxiii)



Am

plit

ude

Vol

ts

Time (microseconds)

Time (microseconds)

Am

plit

ude

Vol

ts



FIGURE a-(xxiv)



Time (microseconds)

Am

plit

ude

Vol

ts

Time (microseconds)

Am

plit

ude

volt

s



FIGURE a-(xxv)

VOLTAGE AT SECOND NODE

VOLTAGE AT RECEIVER THREE

Am

plit

ude

Vol

ts

Time (microseconds)

Am

plit

ude

volt

s

Time (microseconds)



FIGURE a(xxvi)

VOLTAGE AT NODE THREE

VOLTAGE AT RECEIVER FOUR

Time (microseconds)

Am

plit

ude

Vol

ts

Time (microseconds)

Am

plit

ude

Vol

ts



FIGURE a-(xxvii)

ALLL’s.05

REC 2(1.5m)

BUSLIN5

SHIELD5

1

1

1

2

2

23

4

56

TRANS (1.5m)

BUSLIN 1

(100m)

BUSLIN 2

SHIELD2

(50m)

BUSLIN 3

(2m)

BUSLIN 4

SHIELD3

SHIELD4

REC 1

TERM* SHIELD TIED TO INDUCTOR

ON TERM BLOCK

1 1 1 111

2

2

2 2 22

2

2

1 11 2

3 333

4 44 4

5 55 5

66 6 6

h

1 2 3 4 5 76 8 9

50pf6k

40pf 16.5k

45pf 15k

1

2

1 LOAD,@ 100

1 LOAD

SHIELD1

21

µ

Node1

Node2

Node3

*

* *

** * * * * *

RECTWO

TRANSMITTER

328 FEET

5 FEET

5 FEET

RECONE164

FEET8

FEET OR 100

1

2

3

4

5

6

.01

.01 40

40

.1

.1

Trans



FIGURE a-(xxviii)



Time (microseconds)

Am

plit

ude

Vol

tsA

mpl

itud

e V

olts

Time (microseconds)



FIGURE a-(xxix)



Time (microseconds)

Am

plit

ude

volt

sA

mpl

itud

e V

olts

Time (microseconds)


APPENDIX BAN APPROACH TO A HYBRID BROADCAST-COMMAND/RESPONSE DATA BUS ARCHITECTURE

A2-1.0 Introduction

During the time that the broadcast approach to digital information transfer became established in the air transport industry,the military aviation community adopted a command/response time division multiplex technique as its standard. In thisapproach, all aircraft systems needing to exchange digital data are connected to a common bus and a dedicated “buscontroller” determines which of them may output data on to the bus at any given time. MIL STD 1553 was written todescribe this system.

The airlines considered adopting MIL STD 1553, or something like it, for use on post-1980 new civil aircraft types but foundthe multiplex technique to be inappropriate for such applications. In civil avionics systems, data typically flows from a givensource to a single sink, or group of sinks which may be connected in a parallel, and these sinks are typically not themselvesdata sources. Thus there is no need for the data transfer system to provide the capability for every unit of every avionicssystem to both talk and listen to every other unit. The broadcast technique is adequate, and thus the airlines elected to staywith it for their new DITS.

Another development in this same time frame has been the increased use by the military, particularly in transport aircraft, ofavionics equipment designed originally for the airlines. This trend may be expected to continue and so give rise to the needto interface equipment providing Mark 33 DITS I/0 capability with a MIL STD 1553A data bus system. The material in thisAppendix prepared by the Information Engineering Division of the USAF Directorate of Avionics Engineering describes oneway of doing this, using a data exchange buffer to compensate for the electrical, logic and timing differences between the twosystems.

A2-2.0 Suggested Mark 33 DITS/MIL STD 1553A Interface

The following is a proposed method for interfacing an avionic system employing sensors designed for any combination ofARINC Mark 33 DITS and MIL-STD-1553A. This method minimizes message related differences and compensates forelectrical, logic and timing differences in a Data Exchange Buffer (DEB).

In a hybrid system such as shown in Figure b-(i), a signal may originate in either a DITS type subsystem or a 1553Asubsystem and may be destined for either type of terminal. DITS data received by a DEB is momentarily stored and thenretransmitted, complete with label, to the 1553A bus controller. The bus controller determines the intended destinations fromthe label and look-up table. For DITS destinations, the word is retransmitted, as received, to the appropriate DEB. For1553A destinations, the data may be retransmitted as received or reformatted, as required by the destination subsystem.Reformatting could involve removal of label and reversing of bit order (MSB vs LSB first). Figure b-(ii) shows the handlingof a word originating in the destined for DITS terminals.

Upon arrival at the appropriate destination DEB, the data is momentarily stored and then retransmitted in DITS format,complete with label, to the destination subsystem. If all labels in the system are unique, all receivers in all subsystemsassociated with a DEB may be connected in parallel. Only the data with the proper label will be recognized by each receiver.If labels are not unique, the DEB must have separate transmitters to transmit the data with identical labels. The desiredtransmitter could be specified in the 1553A subaddress field.

The retransmission of the data by the DEB allows inherently for different electrical and logical characteristics. The storage ofthe data allows for simultaneous reception from multiple receivers (DITS and 1553A) and retransmission when the desiredbus is available. The much higher speed of 1553A would make retransmission delays small.

Figure b-(iii) illustrates the organization of a minimum system. It consists of multiple DITS receivers dumping received datainto a first-in first-out (FIFO) stack, available as single LSI chips. The received data is temporarily stored and thenretransmitted by the 1553A terminal. Data received via 1553A is dumped into another FIFO for retransmission by a DITStransmitter. The hardware consists only of DITS receivers, the 1553A terminal, the DITS transmitter, and as many FIFO’s asare required. Hand-shaking signals available on the FIFO’s eliminate almost all supporting SSI chips. This entire systemwould probably fit on one full ATR card or less.

Figure b-(iv) illustrates possible organization for a more sophisticated DEB. It consists of an many DITS transmitters andreceivers as necessary, a single (internally redundant) 1553A remote terminal, a buffer memory, a controller(microprocessor), and a program for the controller contained in ROM. Whenever a complete, valid word is available at areceiver, the controller is notified. When the parallel data bus becomes available, the word is transferred to memory. Whenthe desired transmitter (DITS or 1553A) becomes available, the data word is routed from memory to the transmitter. The lowrate of DITS terminals (minimum 320 microsec/word) would result in a very low loading of the parallel bus and controller.The speed of the 1553A terminal might necessitate a direct memory access arrangement. The controller, the programmemory, the buffer memory and a dual 1553A remote terminal would probably fit on one one-sided 3/4 ATR card. Therequired ARINC transmitters and receivers would probably fit on another card.

This method represents one way of constructing a hybrid system. The retransmission of the label with the data greatlyreduces the intelligence required by the DEB but increases bus loading. A more intelligent DEB, perhaps located in the buscontroller, could achieve much higher efficiencies.

AR

INC

SPE

CIF

ICA

TIO

N 429, P

AR

T 1 - P

age 163

AP

PE

ND

IX B

AN

AP

PR

OA

CH

TO

A H

YB

RID

BR

OA

DC

AST

-CO

MM

AN

D/R

ESP

ON

SE D

AT

A B

US A

RC

HIT

EC

TU

RE

NEWSUBSYSTEM

RT

BUSCONTROLLER

DUAL 1553A BUS

DATAEXCHANGE

BUFFER

RT

T R R

OLDSUBSYSTEM

OLDSUBSYSTEM

T R R T R R

OLDSUBSYSTEM

TR

DITSBUSES

NEWSUBSYSTEM

RT

RT

T R

FIG

UR

E b-(i)

HY

BR

ID B

US A

RC

HIT

EC

TU

RE

AR

INC

SPE

CIF

ICA

TIO

N 429, P

AR

T 1 - P

age 164AP

PE

ND

IX B

AN

AP

PR

OA

CH

TO

A H

YB

RID

BR

OA

DC

AST

-CO

MM

AN

D/R

ESP

ON

SE D

AT

A B

US A

RC

HIT

EC

TU

RE

FIG

UR

E b-(ii)

ME

SSAG

E W

OR

D F

OR

MA

TT

ING

LABEL

LABEL

S SLABEL

LABEL

LABEL

Received DITS word (32bits)

Data stored in buffer (2x16 bits)

Data stored in buffer (2x16 bits)

Transmitted via 1553A

Retransmitted via DITS (32 bits)

AR

INC

SPE

CIF

ICA

TIO

N 429, P

AR

T 1 - P

age 165

AP

PE

ND

IX B

AN

AP

PR

OA

CH

TO

A H

YB

RID

BR

OA

DC

AST

-CO

MM

AN

D/R

ESP

ON

SE D

AT

A B

US A

RC

HIT

EC

TU

RE

FIG

UR

E b-(iii)

MIN

IMU

M D

AT

A E

XC

HA

NG

E B

UF

FE

R

DITS BUS 1

DITS BUS 2

DITS BUS 3DITS

XMTR

DITSRECEIVER

DITSRECEIVER

FIFO1553A

TERMINAL

1553 ABUS

AR

INC

SPE

CIF

ICA

TIO

N 429, P

AR

T 1 - P

age 166AP

PE

ND

IX B

AN

AP

PR

OA

CH

TO

A H

YB

RID

BR

OA

DC

AST

-CO

MM

AN

D/R

ESP

ON

SE D

AT

A B

US A

RC

HIT

EC

TU

RE

FIG

UR

E b-(iv)

PR

OG

RA

MM

AB

LE

DA

TA

EX

CH

AN

GE

BU

FF

ER

DITSXMTR

BUFFERMEMORY

Internal Parrallel Data Bus

DITSRECEIVER

DITSRECEIVER

1553ATERMINAL

AddressCONTROLLER

PROGRAM

RockwellInternational

4 May 1979

A Control System View ofARINC 429 Bus Specifications

ByT. G. Sharpe and G. E. Forquer

I. Introduction and Summary

The discussion below summarizes concepts that have grown out of an in-houseeffort to determine what parameter characteristics Collins feels should beincluded in the data standards tables of ARINC Bus Specification 429 (DITS).The DITS specification seems to be evolving as more than merely a digital busdescription since in many ways it is taking on the characteristics of a systeminterface specification. This raises philosophical questions concerning thosecharacteristics, which should appear in the individual equipment specificationsversus those which should appear in “429”. The authors cannot resolve suchpartitioning questions. Hopefully we can contribute, as outlined below, to anunderstanding of what information is required by control systems designers toachieve an acceptable system performance. The detailed discussion in this paperevolves a set of terms (outlined below) which are usable in a specification. Whichof these terms appear in the individual equipment specifications and which appearin “429” remains to be determined.

At the present time, it is suggested that control system designers interfacing withdigitally bused data should be concerned with three prime areas: stabilityconsiderations, signal degradation, and spectral characteristics. Without theseelements of information, thorough analysis of system performance will not bepossible.

The following eight parameter characteristics should prove adequate for theminimal control of interfacing considerations.

Stability• Control Band• Magnitude Limits• Phase Limits

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 inunderstanding their purpose and assessing their adequacy. It is recognized thatsome changes may necessarily take place as the industry completes its digitalinterfacing standardization task.

II. Stability Consideration

There is nothing uniquely digital in this area. Here our concern is with thosecharacteristics that are most often used in linear system stability analysis – namelygain and phase characteristics. We recognize at the outset that all sensor systemsare not 100% linear but this does not prevent us from defining a linear model ofsufficient quality to support stability analyses. It is useful to consider here thatgenerally the sensor will be wideband relative to the band of frequencies ofinterest to the control system. This is necessary from a stability point of viewsince the converse (that is, signals narrowband relative to the control band) wouldintroduce excessive phase lag in the control band. Thus far we have implicitlyconsidered both bandpass and lowpass centered at zero frequency. For simplicity,however, the discussion below will assume low pass sensor characteristics but theideas apply generally. Figure 1 illustrates an assumed sensor characteristic.

Gain and Phase Constraints

Note that prime concerns are that the gain remain essentially constant through thecontrol band and that the phase be bounded by a linear characteristic through thecontrol band. From a control law stability point of view, we are not concernedwith what happens at frequencies above the control band because these arebeyond the range where the data is being used by the control system. If weconsider open loop Bode plots broken at the sensor output, the control band asused above should be wide enough to include the phase crossover as well as thegain crossover. The phase and gain characteristics provide information aboutphase and gain margin degradation. For most sensors the gain crossover in

AR

INC

SPE

CIF

ICA

TIO

N429,P

AR

T1

–P

age167

AP

PE

ND

IX C

DIG

ITA

L SY

STE

MS G

UID

AN

CE

(PA

RT

1)Collins Avionics Divisions

400 Collins Road, NECedar Rapids, Iowa, 52406

(319) 395-1000Cable COLINRAD Cedar Rapids

typical control laws is known approximately. Phase crossover is not as easilydetermined. A reasonable first cut would be to define the control band asapproximately ten times the open loop crossover frequency with the expectationthat beyond this range control law gain is low enough to prevent gain marginproblems. However, some sensors may have trouble holding a tight gain (andphase) spec over this wide a bandwidth. Possibly in these cases a loosening of thespec between open loop crossover and ten times open loop crossover may berequired. With this kind of specification a simple transport delay in combinationwith a gain change can be used for stability analysis or, for slightly more complexcases, simple transfer functions can be used to approximately fit the spec. Theimportant point here is not to constrain the sensor designer to a first order orsecond order or any specific implementation, but to rather bound in a simple yetusable sense the stability degradation the sensor can introduce. The importantstability characteristics are defined concisely below.

• Control Band – That band of frequencies over which magnitude and phasecharacteristics of the sensor are important to the control system stability.

• Magnitude Constraint – The bounds (envelope) on the permissible gainvariation in a linear frequency response sense that are permissible over thecontrol band.

• Phase Constraint – The bounds (envelope) on the permissible phase variationin a linear frequency response sense that are permissible over the controlband.

AR

INC

SPE

CIF

ICA

TIO

N 429, P

AR

T 1 – P

age 168

AP

PE

ND

IX C

DIG

ITA

L SY

STE

MS G

UID

AN

CE

(PA

RT

1)

f( )

S E N S O R

Signa l DependentNoise

Internal lyGenerated Noise

Instal lat ionNoise

S ignal

ProcessNoise

SensorInput Sensor

O u p u t

M e a s u r e m e n tError

-

++

+

++

+

++

+

Potential Measurement Technique

These quantities could be measured by providing a sinusoidal input stimuli atselected frequencies in the control band using a mid-range amplitude. At eachfrequency the output component of interest (assuming some distortion) will be theoutput component whose frequency corresponds to the input frequency. Thephase and amplitude of this component of this component relative to the forcingfunction will provide the magnitude and phase information. In the terminology ofnonlinear system analysis, this procedure yields and empirically deriveddescribing function for the sensor over the control band. If amplitude dependentnonlinearities are severe, more than one amplitude of forcing function may haveto be used with the procedure repeated at each amplitude.

III. Signal Degradation

In this area we are concerned with what the sensor may have done to degrade thesignal. The thrust here is not stability but performance. Figure 2 presents a viewof sensor and signal characteristics that is useful in this context. In Figure 2 someimportant sources of signal degradation are illustrated. The term “noise” is usedsomewhat loosely in Figure 2 to denote degradation sources. Process noise andinstallation noise are inherent in the signal impinging on the sensor – the formerbeing things such as gust noise and beam noise and the latter being effects such asEMI, mounting errors, etc. Within the sensor itself there is internally generatednoise such as shot noise from resistors, EMI from digital buses, etc. that isindependent of the input signal. In a radio receiver this is the kind of noise that ismeasured at the output when the input is shorted. Note that this “noise” can alsoinclude bias and drift effects. If there is a digital sampling process in the sensor,some aliasing of the input signal spectrum will occur. This aliased energy mayalso be regarded as noise.

The other inherent sensor degradation is more difficult to deal with, however, forit is signal dependent. A familiar analog example is input amplitude dependentcharacteristics such as saturation effects that only become significant abovecertain input amplitudes. Another is nonlinearities that produce harmonicdistortion under sine wave excitation as shown in the example below.

Figure 2. Sensor and Signal Characteristic

and Measurement Noise

AR

INC

SPE

CIF

ICA

TIO

N 429, P

AR

T 1 – P

age 169

AP

PE

ND

IX C

DIG

ITA

L SY

STE

MS G

UID

AN

CE

(PA

RT

1)

22

kk"

So

Po

So

Po

Harmonic Distortion

Consider square law distortion in an otherwise linear sensor. Let the sensoroutput be

y(t) = x(t) + kx(t)²

Where x(t) is the sensor input and let x(t) = sinwt. Then

y(t) = sinwt + ksin²wt

y(t) = sinwt ± cos2wt

Note that d.c. and second harmonic components as well as the forcing frequencyappear at the output. In digital systems a similar effect occurs when multiple ratesare introduced, such as signals being received at one rate from a digital bus andbeing used at a different rate by a software program. If the analog signalsoriginally sampled and put on the bus were sinusoidal at one frequency then, ingeneral, frequency components less than and greater than the input frequency (aswell as the input frequency) appear after the second sampler. The amplitude andnumber of these spurious outputs is a function of the two sampling rates as well asthe input frequency. The net effect of all such internal sensor effects isobservable by subtracting sensor input from sensor output to yield measurementerror as shown in Figure 2.

Measurement Error

The involved nature of what can happen to the signal within the sensor as shownin Figure 2 is the source of ambiguity in conventional “accuracy” specs. Sincemeasurement noise can be dependent on input amplitude as well as spectralcharacteristics, it is not possible to specify it with a single and simple metric. Itshould also be apparent that measurement error must be addressed statisticallysince a significant portion of the input, process noise, is only describable as arandom process.1 Technically the input signal is also in general a randomprocesses influenced by such things as the gust striking the aircraft. Gusts alsocan only be described as random processes.

1 Recognizing that a complete description of a random process includes not onlyprobability distributions but also spectral characteristics.

To evaluate the spectral characteristics of measurement error will require testswhich force the system with noise type inputs. Exponentially correlated noise ofspecified variance and correlation time (or bandwidth) should be sufficient inmost cases. If a sensor is known to be susceptible to a specific type of noise,however, that noise should be included in the test. Often it will be useful toseparate out the low frequency or d-c components of measurement error sincethese may be more tolerable in some applications than dynamic errors. A set oftests that will measure these characteristics is described below.

Modified Signal to Noise Ratio (MSN)

Force the sensor with random noise of specified rms value (σ) and correlationtime (τ). Determine the power spectral density (PSD) of the input signal to thesensor. Determine the PSD of the measurement error. Plot the two PSD’s on acommon plot as shown in Figure 3. Define a modified signal to noise ratio(which will be a function of frequency) as the square root of noise ratio at eachfrequency of signal PSD amplitude to measurement error PSD. Note in theexample shown in Figure 3 there is a bulge in the measurement error around zerofrequency. This effect would indicate d-c bias and possibly low frequency biasdrift from the sensor. This effect may or may not be important depending onwhether the application permits washing out low frequency components, e.g. in acomplementary filter. In the range of frequencies where accurate sensor responseis required, it is suggested that appropriate values for the modified signal to noise(MSN) will be 100 to 1000. Roughly, these numbers correspond to noise power

being 1% to .1% of signal power at each frequency or noise being 40 to 60 dbdown from signal. The relationship between MSD and ordinary signal to noisecan be understood by assuming both signal and noise PSD’s are flat over a bandof frequencies ∆w as shown in Figure 3. Let the value of the signal PSD in thisband be So, then rms signal power in the band ∆w is given by So*w. Similarly,rms error power is given by Po*w . Therefore conventional signal to noise over theband w is given by . Requiring that this signal to noise be 100 is equivalent torequiring that noise power be 1% of signal power over this band. Carrying thisback to the MSN implies that MSN (w) = = 100 over the band ∆w. Theabove also represents the motivation for considering square root of the ratio thanthe ratio directly.

Amplitude Dependent Nonlinearities

The approach described above tests for input frequency dependent degradations byproviding a realistic input spectrum. It should be realized that if there are

AR

INC

SPE

CIF

ICA

TIO

N 429, P

AR

T 1 – P

age 170

AP

PE

ND

IX C

DIG

ITA

L SY

STE

MS G

UID

AN

CE

(PA

RT

1)

amplitude dependent degradations, the MSN analysis will yield different answersdepending on the rms value of the input noise. It is suggested that the MSNmeasurement be done with worst case input noise, i.e., largest rms and bandwidththat will be encountered. In some cases alternate MSN specs for different flightregimes may be appropriate.

In many cases a more explicit presentation of the amplitude dependent non-linearities may be desirable. A good example here is localizer receiver linearity,specified as being linear within a given percentage up to .155 DDM, a largerpercentage from .155 to .310 DDM and not decreasing between .310 and .400DDM. Such a specification is important in defining localizer capture laws, whereone can begin “using” the signal crudely before it is linear or precisely accurate. Itshould be noted that this is a slightly different use of sensor data than for precisestate control, i.e. the control is carrying the system to a prescribed state ratherthan maintaining it at a prescribed state in the presence of noise. Normally thelatter operation will require more accurate information from the sensor. Theamplitude dependent degradations should be measured statically -- that is, oneshould provide a test input at specified amplitude, allow transients to settle, andmeasure the output value.

The important signal degradation terms are defined concisely below. Only thelast two are proposed as parameter characteristics--the first three being definitionsto clarify the last two.

• Measurement Error – The difference between the signal impingingon the sensor and the output representation of that signal by thesensor expressed in consistent units.

• Signal PSD (SPSD) – The power spectral density of the signalimpinging on the sensor.

• Measurement Error PSD (MEPSD) – The power spectral density ofmeasurement error introduced by the sensor.

• Modified Signal to Noise Ratio – A measure primarily of thespectral characteristics of sensor errors defined as the square root ofthe ratio of SPSD and MEPSD at each frequency in the controlband.

i.e., MSN(w) =

• Static Accuracy – A measure of the amplitude dependentcharacteristics of sensor errors defined as the difference betweeninput and output signals after all transients have settled.

Potential Measurement Technique

Modified Signal to Noise (MSN) determination requires assuming a randomprocess model for the signal impinging on the sensor. Normally an exponentiallycorrelated signal with specified variance will be sufficient. Empiricallydetermined power spectral densities (using discrete Fourier Transformtechniques) will need to be measured for input signal as well as measurementerror. Static accuracy measurement was described above.

IV. Spectral Characteristics

In this area the digital nature of the system interface must be faced squarely. Thecontrol system designer cannot alter the signal degradation introduced by

AR

INC

SPE

CIF

ICA

TIO

N 429, P

AR

T 1 - P

age 171

S ignal Power Spectra lDens i ty

( SPSD(w) )

M e a s u r e m e n tError Power

Spectral Densi ty( M E P S D ( w ) )

f requency

ww

∆= wrms p0

( )wrms s ∆=0

M S N ( w ) =

MSN Modif ied Signal to Noise Ratio∆

Fig re 3 Modif ied Signal to Noise Ratio

SPSD (w)MEPSD (w)

AMPLITUDE

S o

P o

SPSD (w)MEPSD (w)

AP

PE

ND

IX C

DIG

ITA

L SY

STE

MS G

UID

AN

CE

(PA

RT

1)

the sensor whether it be due to nonlinearities, aliasing, noise, etc. He has greatpotential, however, for making matters worse if he is not alert to potential aliasingproblems that he may introduce. To analyze aliasing precisely he would need aprecise definition of the spectrum of each signal being received on the digital busincluding the update interval for each signal. A more practical approach is toplace an upper bound on the received signal spectrum and then ensuredownstream performance is adequate using this bound as the signal spectrum.These ideas are made more precise below.

Multirate Sampling

A simple model for signals received from a bus and used in a digital processor isshown in Figure 4. We note that the spectrum of the signal on the bus, F1 (s), is aninfinitely replicated version of the analog input spectrum with replicas spaced bythe input sampling frequency F1. We cannot, therefore, speak of the bandwidthof F1 (s) strictly. What we mean here is that a bound is required on each copy inF1 (s). Deriving the spectrum of the signal F2 (s) is beyond the scope of thisdiscussion but a technique has been developed that will yield this spectrum, F2 (s),given the quantities F1, F2, and the shape of the repeated spectrum of F (s) in F1

(s). There is considerable spreading of signal energy in this process withconsiderable “aliasing” potential even if the quantity fc in Figure 4 is much lessthan the Nyquist frequency for both F1 and F2. The “aliasing” inthe spectrum F2 (s) occurs because the second sampler is not operating on aproperly band limited function (see Figure 4) due to the “infinite replica” natureof the spectrum F2 (s).

Deterministic Versus Random Signals

The discussion above did not specify whether the original analog quantity was adeterministic signal or a random process. For deterministic cases we deal withthe Fourier transforms of the signals involved. However, as pointed out inSection III the signals of interest are really describable only in terms of randomprocesses. For this case the development must proceed in terms of power spectraldensity of the signals involved. Figure 5 then illustrates the bound on busedsignal PSD that is envisioned. Recall that white noise through a lowpass filteryields a PSD that rolls off at 40 db/decade as shown below.

White Noise Input PSD: U(S) = A - ∞ < w < + ∞

Filter Transfer Function: T (jw) = 1

Jτw+1

Output PSD: Y (S) = T(S)T*(S)U(S)

Y(w) = A

τ2w2+1

Adequate roll off chracteristic of the digitally bused data reduces the aliasingproblem of the second sampler if the second sampling is properly performed.However, not only this spectrum but also the frequency F1 enters into the aliasingin F2 (s), therefore, it is desirable also to carefully specify F1. This will beaccomplished through the update interval. Assuming F2 is somewhat fixed bycomputer speed and loading considerations, aliasing can be minimized for a giveninput spectrum by making F1 as high relative to F2 as possible.

The important spectral characteristic terms are defined concisely below.

• Update Interval – The cyclic time interval, as measured at the DITS businterface, between transmissions of new freshly sensed and converted/derivedvalues of the parameter.

)2

f 2,2f 1(

Digita lRegis ter

S a m p l e r S a m p l e r

f1 f 2

F(S) FA n a l o gQ u a n t i t y

B u s e dSignal

Sof twareFetch

F(S) A n a l o gInputSpec trum

S

-2f1 -f 1 -fc 2 f 1 Sfc

F igure 4 Analys is of Mult irate Sampl ing

2(S)F

1(S)

f 1

AR

INC

SPE

CIF

ICA

TIO

N 429, P

AR

T 1 - P

age 172

AP

PE

ND

IX C

DIG

ITA

L SY

STE

MS G

UID

AN

CE

(PA

RT

1)

• Transmit Interval – The cyclic time interval, as measured at the DITS businterface, between transmissions of the parameter. Transmit Interval ≤Update Interval.

• Pre-sampling Bandwidth Limit – That bandwidth for a first order lag that willupper bound the spectral characteristics of the signal of the signal on the bus.

Figure 5 PSD Bound on Bused S igna l

Note: Per iodic Funct ion - Only Posit ive Half of Zero Centered Component Shown (see Figure 4)

Frequency

w

40 db/decade

P o w e r SpectralDensi ty

Pre-Sampl ingBandwidth

Limit

AP

PE

ND

IX C

DIG

ITA

L SY

STE

MS G

UID

AN

CE

(PA

RT

1)

AR

INC

SPE

CIF

ICA

TIO

N 429, P

AR

T 1 - P

age 173

BOEING COMMERCIAL AIRPLANE COMPANY P.O. Box 3707 Seattle, Washington 98124 M/S 47-09 A Division of The Boeing Company

May 11, 1979SYST-B8713-79-209

Mr. B. R. Climie, ChairmanAirlines Electronic Engineering CommitteeAeronautical Radio, Inc.2551 Riva RoadAnnapolis, Maryland 21401

Dear Rick:

The enclosed paper is a revised version of “Design Parameters for DigitalAvionic Systems,” which was originally circulated with AEEC letter 79-022/SAI-99. The revision addresses the topic of aliasing which couldoccur when reducing the sampling rate of a digitally encoded signal. Thistopic was discussed at the DITS working group meeting held on April 18and 19.

Sincerely

AIR TRAFFIC CONTROLAND ELECTRONIC SYSTEMS

A. F. Norwood, Chief

AFN:Enclosure

Attachment toSYST-B-8764-20-075

DESIGN PARAMETERS FOR DIGITAL AVIONIC SYSTEMSPrepared by

Boeing Commercial Airplane CompanyREVISION A

Summary

This paper explains the necessity for defining presampling filtercharacteristics, transport delays and minimum update rates for digital andnoise characteristics are discussed. A design procedure for selecting therequired filter characteristic and update rate is presented.

Introduction

The new generation of commercial aircraft will use digital technology toimplement many functions, which were traditionally performed withanalog hardware. These functions include inner and outer servo loops foraircraft control and guidance, processing and filtering signals fromnavigation and other sensors, and filtering of data prior to its display oncockpit instruments. Digital technology will also replace the majority ofthe formerly analog communication paths between systems, sensors,instruments and actuators.

A basic property of these and other digital systems is that they onlyprocess or transfer values of data from discrete points in time. Thecontrast between the discrete time nature of a digital system and thecontinuous time nature of an analog system is shown in Figure 1. Analogsystems are said to operate in the continuous time domain while digitalsystems are said to operate in the discrete time domain.

In order for discrete time digital systems to be used to process or transferthe inherently continuous time data from real world physical systems,samples of the continuous data must be taken at periodic intervals. Thesesamples from discrete points in time can then be used as the input to thediscrete time digital system. It is intuitively obvious that the intervalbetween samples affects the accuracy with which the continuous time datais represented by the discrete samples. It is also obvious that rapidlyvarying signals should be sampled more often than slowly varying signalsin order to maintain an adequate representation of the continuous analogdata. Selection of a proper sampling rate for each signal is a design taskunique to digital systems. An understanding of the Sampling Theorem isnecessary in order to make the proper trade offs between sampling rate,signal-to-noise ratio, signal delay, and system complexity.

AP

PE

ND

IX D

DIG

ITA

L SY

STE

MS G

UID

AN

CE

(PA

RT

2)

AR

INC

SPE

CIF

ICA

TIO

N 429, P

AR

T 1 - P

age 174

BBBBBBBBBBBBOOOOOOOOOOOOEEEEEEEEEEEEIIIIIIIIIIIINNNNNNNNNNNNGGGGGGGGGGGG

The Sampling Theorem

The Sampling Theorem states that a signal which contains no frequencycomponents higher than fo Hertz can be exactly recovered from a set of itssamples if the samples are spaced no further apart than ½ fo seconds. Thisis equivalent to requiring that the sampling frequency be greater thantwice the highest frequency component of the signal.

The reason for this requirement can be shown by examing the frequencyspectrum of the sampler output. Modeling the sampling operation as themultiplication of the input signal by an impulse train as shown in Figure 2allows the sampler output spectrum to be computed from a FourierTransform identity. The required identity states that time domainmultiplication is equivalent to frequency domain convolution. Therefore,the output spectrum is found by convolving the input spectrum with thespectrum of the impulse train. This relationship is shown in Figure 3.The convolution operation has the effect of reproducing the spectrum ofthe input signal about zero frequency and at all harmonics of the samplingfrequency. If the sampling frequency, 1/Ts, is greater than twice fo thespectral components centered about the sampling frequency and itsharmonics will not overlap the spectral component centered about zerofrequency. Therefore, the spectral component centered about zero, whichis identical to the input spectrum, can be obtained by passing the sampledoutput through a low pass filter with a bandwidth of fo Hz.

Application of the Sampling Theorem to Digital Avionics Systems

The discussion of the Sampling Theorem in the preceding section hasshown that a signal which contains no frequency components higher thanfo Hz. can be exactly represented by a series of samples spaced no furtherapart than ½ fo seconds. However, signals, which represent physicalquantities, such as those processed by avionic systems never satisfy thestrict bandwidth limitation requirement stated above. Therefore exactreproduction of the original signal from its samples is not possible. Theeffect of the non-bandlimited nature of signals is to distort the replicareconstructed from the samples. The shaded area shown in Figure 4represents typical high frequency signal energy which distorts the lowfrequency portion of the signal spectrum. The high frequency portion ofthe signal takes on the identity of the lower frequencies, hence the name“aliasing” for this phenomenon.

Aliasing becomes a greater problem when the signal is corrupted by noise,which has a wider bandwidth than the signal. When this occurs bothsignal energy and noise energy which is beyond one half of the samplingfrequency is aliased into the low frequency portion of the recoveredsignal. This effect is shown in Figure 5. The signal-to-noise ratio isdegraded by both noise and signal components which are aliased into thelow frequency portion of the signal spectrum. The effect of aliasing canbe decreased by sampling the incoming signal at a higher rate and/or usinga presampling filter to reduce the bandwidth of the signal prior tosampling. Neither of these approaches can ever completely eliminate the

effect of aliasing and they each result in some negative impact on theoverall system.

An increase in the sampling rate requires more computations to be done ina given period of time. This requires more computational resources,which increases the weight, complexity, and power requirements of thecomputer subsystems. The use of a presampling filter to limit thebandwidth prior to sampling distorts the signal. It also increases the delayexperienced by signals as they propagate through the system. Theincrease in delay reduces phase margin if the signal is used in a closedloop control system. Therefore, more stringent delay requirements mustbe placed on other components in the loop if the system phase margin isto remain constant.

Design Tradeoffs for Digital Avionics Systems

The final choices of sample rate and presampling filter depend upon theinput signal and noise spectra, maximum allowable signal-to-noise ratiodegradation due to aliasing, maximum allowable transport delay, availablecomputational resources, and the bandwidth of the system which uses thedata. A practical way to make these choices is to analyze the system forvarious sample rates and filters. This can best be done with the aid of acomputer program which computers the effect of each combination ofsample rate and filter characteristic on the output signal-to-noise ratio forthe defined input signal and noise spectra.

The initial computation is to determine the effect of the prefilter on the in-band signal-to-noise ratio without regard to aliasing effects. A typicalplot of signal-to-noise ratio versus presampling filter bandwidth is shownin the top curve of Figure 6. This curve forms a baseline against whichsignal-to-noise ratio degradation caused by aliasing can be compared.The signal-to-noise ratio is determined by computing the input signalpower and input noise power, which is passed by the selected prefilter.This parameter will generally exhibit a peak value at a specific bandwidth.The signal-to-noise ratio will decrease with increasing bandwidth as morenoise is admitted and decrease with decreasing bandwidth as signal energyis eliminated.

The filter order is an important design parameter because higher orderfilters roll off more rapidly near the cutoff frequency. Therefore higherorder filters admit less noise and signal from beyond the cutoff frequencythan low order filters. Because of this characteristic, high order filtersalias no more noise into the signal than slightly narrower bandwidth loworder filters. However, high order filters delay the signal more than loworder filters.

The ultimate objective of the design task discussed in this paper is toachieve acceptable system performance with the minimum possible

AR

INC

SPE

CIF

ICA

TIO

N429,P

AR

T1

-P

age175

AP

PE

ND

IX D

DIG

ITA

L SY

STE

MS G

UID

AN

CE

(PA

RT

2)

sampling rate. System performance is adversely affected by largepropagation delays and high in-band noise levels.

If the maximum allowable propagation delay is given, the minimumusable filter bandwidth can be found standard plots of group delay versusfrequency for the type and order of filter considered. (See for exampleReference 1, page 112.) This minimum bandwidth is plotted on Figure 6as a vertical line. The maximum achievable signal-to-noise ratio isconstrained by the requirement for a presampling filter wide enough tolimit delay to the given value. The intersection of the minimumbandwidth line with the top curve of Figure 6 gives the maximumachievable signal-to-noise ratio i.e., the signal-to-noise ratio which wouldbe achieved by an unsampled system.

Sampling rate is chosen by comparing the maximum acceptabledegradation in signal-to-noise ratio to the actual aliasing degradation dueto sampling at the candidate rates. For the example shown in Figure 6, asampling rate of 50Hz would be chosen.

A system interface which meets prescribed limits on signal delay andmaximum noise due to aliasing can be designed using the proceduresoutlined above. Some systems which use sampled data, such as closedloop control systems, have a bandwidth which is much smaller than thatof the sampling filter. For this reason it is important to verify that thesignal and noise power which is aliased into the frequency band of interestis well below the inherent noise in that band.

This can be accomplished by constructing a signal and noise powerspectral density plot for the filter and sampling rate chosen. The powerspectral density plot is most easily obtained with the aid of a computerprogram. A typical plot of this type is shown in Figure 7. The examplepower spectral densities in Figure 7 show that the aliased signal and noiseis much lower than the inherent noise level in the frequency range ofinterest. If this constraint is not met a different combination of filter andsampling frequency must be chosen.

In some situations it may be desired to reduce the sampling rate of adigitally encoded signal. This may be done where wideband digital datais used to drive an instrument or subsystem which responds only tonarrower bandwidth data. Simple deletion of unwanted samples to reducethe sampling rate can cause aliasing problems similar to those encounteredwhen sampling an analog signal at an insufficient rate. The aliasing canbe elimination of the unwanted samples. Design of the digital filter issubject to the same set of delay versus aliasing noise tradeoffs as thedesign of an analog presampling filter.

Conclusion

The procedures outlined in this paper can be used to choose thepresampling filter and sampling rate required for interfaces to a digitalsignal processing or control system. The values are chosen to meet theconstraints of maximum allowable delay and maximum allowable noise

due to aliasing. Signal and noise spectra of the signal to be sampled mustbe supplied as an input to the design procedure.

Reference: Herman J. Blinchikoff and Anatol I. Zverev, Filtering in theTime and Frequency Domains, John Wiley and Sons, NewYork.

A n a l o gS y s t e mA n a l o g

InputA n a l o gO u t p u t

A n a l o gInput

A n a l o gO u t p u t

t ime t ime

Figure 1(a) Typica l Input and Output o f Analog System

Digita lS y s t e mDigita l Input

(discrete values)Dig i ta l Output

(discrete values)

t ime t ime

Figure 1(b) Typical Input and Output of Dig i ta l System

Digita lInput

AR

INC

SPE

CIF

ICA

TIO

N 429, P

AR

T 1 - P

age 176

AP

PE

ND

IX D

DIG

ITA

L SY

STE

MS G

UID

AN

CE

(PA

RT

2)

Figure 4 Sampler Output Spectrum When Input Signal Bandwidthisnot Limited to One-Half of the Sampling Frequency

Figure 5(a) Input Signal and Noise Spectra

Figure 5(b) Output Signal and Noise Spectra Showing Signal-to-NoiseRatio Degradation Due to Aliasing of Signal and Noise

∑∞

−∞=

−

n

nTst )(δ

0

0

0

fT s

2−T s

1−

T s2

1−T s2

1

T s

1T s

2

T s2

1

T s2

1−

T s2

1−

AR

INC

SPE

CIF

ICA

TIO

N 429, P

AR

T 1 - P

age 177

AP

PE

ND

IX D

DIG

ITA

L SY

STE

MS G

UID

AN

CE

(PA

RT

2)

T s2

1

∑∞

−∞=

−

n

nTst )(δ

X Low PassBw =oHzrs(t)

Figure 2 Mathmatical Model of Sampling Process

r (t)r (t)

0

R (f)

-fo fo

Figure 3(b) Spectrum of f(t) Bandlimited to fo Hz

})({ ∑∞

−∞=

−ℑ

n

nTstδ

- - - - - -

0- 1

Ts

1Ts

f2Ts

-2Ts

Figure 3(b) Spectrum of Input Train,

0- - -

Rs(f) signal recovery

+ -

-fo

- - -

ffo

fo fo

1Ts

- 1Ts

1Ts

- 1Ts

Figure 3(c) Spectrum of Sampling Output

Input Noise Spectrum

Input Signal Spectrum

AR

INC

SPE

CIF

ICA

TIO

N 429, P

AR

T 1 - P

age 178

AP

PE

ND

IX D

DIG

ITA

L SY

STE

MS G

UID

AN

CE

(PA

RT

2)


APPENDIX EGUIDELINES 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 toprovide data transfer between Line Replaceable Units (LRU) which are not otherwise covered by ARINC Characteristics. Itis important that each new usage of ARINC 429 be coordinated and indexed by ARINC such that the information on usage(label allocation, data format, etc.) is available industry-wide. The use of the same label for two different functions on aparticular LRU type built by different manufacturers can create serious problems.

To facilitate the coordination of ARINC 429 label usage between the industry and the ARINC staff, a set of guidelines isprovided.

1. New labels should be selected from the five character field as defined in Section 2.3 (three octal and threehexadecimal).

2. The following labels have special significance and should not be used: label 000 (not used) and label 377(equipment identification).

3. The following labels are presently “spare” and should only be used for new parameters which may have verywidespread usage throughout the airplane architecture.

005 040 050 054 107 163 227 371

006 046 051 055 113 167 240

007 047 052 057 124 226 243

4. Where possible, similar word usage should be “grouped”; for example, if Engine N 1 is to be provided from a newunit (PMUX) it should utilize label 246 which is presently N 1 (engine direct).

5. Where possible, grouped usage should have identical data specification (units, range, significant digits/bits, positivesense, resolution, min--max transmit interval). To facilitate this commonality it is permissible for a particular LRUto output a lower resolution signal (fewer significant digits/bits) if the least significant remainder of the data field isset to zeros.

6. Where word grouping is not possible, the labels should be selected from the following subgroups:

Binary coded decimal (BCD) sub-group 001 to 067, 125, 165, 170, 200, 201,230 to 237.

Binary (BNR) subgroup 070 to 124, 126 to 144, 150 to 154, 162 to 164, 166, 167, 171 to 177, 202 to 227, 240 to257, 262 to 265, 267, 310 to 347, 360 to 376.

Mixed BCD and BNR subgroup 260, 261

Discretes subgroup 145 to 147, 270 to 276

Maintenance and discrete data subgroup 155, 156

Maintenance data subgroup 157 to 161, 350 to 354

Test word subgroup 266, 277

Application dependent subgroups 300 to 307

Acknowledgement subgroup 355

Maintenance ISO #5 subgroup 356

ISO #5 message subgroup 357

A schematic of these subgroups is attached.

c-16


APPENDIX EGUIDELINES FOR LABEL ASSIGNMENTS

7. Allocation of bits within words, as defined in the appropriate sections.

BCDBNRDiscretesMaintenance dataTestApplication dependentAcknowledgementMaintenance ISO #5ISO #5 message

8. The data should be fully defined by Equipment ID and the label and the Source Destination Indicator (SDI). Itshould not be necessary to decode additional bits in the word to correctly interpret the data field.

9. The equipment ID should be allocated as the two least significant digits of the 7XX ARINC equipmentspecification, if one exists. For equipment not otherwise covered by an ARINC Specification, an equipment IDshould be allocated with a non-numeric value of the hexadecimal character set as the least significant digit.

10. Equipment ID of 000 (HEX) should not be used.

11. The SDI code should indicate the aircraft installation number of the source equipment, in a multi-system installation,as described in 2.1.4.

Least Significant Digit

TwoMostSig.

Digits

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

00 X010203040506

BCD

071011

BNR

12 BCD1314 DISCRETE15 MAINT DISC M DATA16 MAINT DATA17 BCD20212223 BCD24 BNR2526 MIX TEST27 DISCRETE TEST30 APPLICATION DEPENDENT31323334

BNR

35 MAINT DATA ACK M ISO ISO536 BNR37 EQ ID


APPENDIX XCHRONOLOGY & BIBLIOGRAPHY

X-l.0 Chronology

AEEC established the Systems Architecture and Interfaces (SAI) Subcommittee in 1975 to develop the air transportindustry’s approach to digital avionics systems architecture, to define digital system interface standards. With respect to thislast-named, the Subcommittee soon determined that the industry’s previous approaches to digital information transfer,described in ARINC Specification 419, “Digital Data System Compendium”, needed rationalization and modernization to beapplicable in the future digital systems world. However, this work was not started immediately because of the need toconcentrate on the more basic tasks related to digital systems architecture.

About a year later, AEEC deemed it timely to start the spec-writing for a digital automatic flight control system based on thesystem architecture concepts developed by the SAI Subcommittee. The Subcommittee AEEC established to do this began itswork in January 1977. Part of this activity was the definition of black box interface standards, and this brought into sharpfocus the need for the new digital information transfer system to be properly specified.

The SAI Subcommittee immediately began to devote time to the discussion of the issues involved to give direction to theDigital Information Transfer System (DITS) working group it set up to develop a spec draft. This group met early in April1977, and produced a draft which the full Subcommittee reviewed at its meeting in May. A second working group meetingduring the period of that Subcommittee meeting, followed by a third in mid-June, produced the second draft of the spec. Thisdraft was submitted to AEEC for adoption, which was achieved at the Summer 1977 General Session in July.

The spec adopted by AEEC contained details of numeric data (BNR and BCD) transfer only. The SAI Subcommitteenotified AEEC of its intent to broaden the scope of the document to cover alpha/numeric (ISO Alphabet No. 5) and graphicdata handling also. These subjects would be addressed in a Supplement to the spec which AEEC would be asked to approveat a later date.

X-2.0 Bibliography

The following is a list of AEEC letters associated with the preparation of ARINC Specification 429. A list of AEEC lettersrelated the SAI Subcommittee's overall activities may be found in ARINC Report 299, “AEEC Letter Index”.

AEEC Letter No. Date Subject

76-130/SAI-20 Dec. 9, 1976 Report of the Systems Architecture and Interfaces Subcommittee Meetingheld November 16th, 17th and 18th, 1976 in Seattle, Washington

77-009/SAI-22 Jan. 27, 1977 Whither On-Board Digital Data Transmission Standards?

77-020/SAI-25 Feb. 11, 1977 More On Digital Data Transmission Standards

N77-035/SAI-26 Mar. 21, 1977 Boeing Report On Alternative Digital Information System SignallingStandards

77-037/SAI-28 Mar. 25, 1977 Report of the Systems Architecture and Interfaces Subcommittee MeetingHeld March 7th, 8th and 9th, 1977 in Arlington, Virginia

77-047/SAI-33 Apr. 13, 1977 Circulation of Draft No. I of Project Paper 429, “Mark 33 DigitalInformation Transfer System (DITS)”

77-056/SAI-37 Apr. 18, 1977 Report of the SAI Subcommittee BITS Working Group Meeting Held April5-6, 1977, in Annapolis, Maryland

77-066/SAI-41 Jun. 8, 1977 Report of the Systems Architecture and Interfaces Subcommittee MeetingHeld May 9th, 10th and 11th, 1977 in Los Angeles, California

77-079/SAI-46 Jun. 23, 1977 Circulation of Draft No. 2 of Project paper 429, “Mark 33 DigitalInformation Transfer System (DITS)”



X-3.0 Meeting Attendees

The following people comprised the SAI Subcommittee’s Digital Information Transfer System Working Group.

Tom Ellison UNITED AIRLINES San Francisco, CaliforniaWolfgang Bull DEUTSCHE LUFTHANSA Hamburg, GermanySiegmar Gomille DEUTSCHE LUFTHANSA Hamburg, GermanyJim Wahlen BENDIX AVIONICS Ft. Lauderdale, FloridaTony Martin BOEING Seattle, WashingtonFrank Rasmussen BOEING Seattle, WashingtonEd Schroeder BOEING Seattle, WashingtonArvind Dandekar COLLINS RADIO, ROCKWELL INT. Cedar Rapids, IowaBill Harts COLLINS RADIO, ROCKWELL INT. Cedar Rapids, IowaDavid Lewis DELCO ELECTRONICS Milwaukee, WisconsinRalph Bazil KING RADIO CORPORATION Olathe, KansasHal Pierson MITRE CORPORATION McLean, VirginiaBob Clark SPERRY FLIGHT SYSTEMS Phoenix, ArizonaCapt. Russ Glastetter USAF Dayton, OhioDavid Featherstone AERONAUTICAL RADIO, INC. Annapolis, Maryland

The following people attended one or more of the SAI Subcommittee meetings held November 16th-18th, 1976, March 7th-9th, 1977 and May 9th-11th, 1977, during which the 429 DITS spec drafts and other proposals produced by the DITSworking group were reviewed, refined and finalized.

Airlines and ARINC Staff

T. A. Ellison, Chairman UNITED AIRLINES San Francisco, CaliforniaJ. S. Davidson AIR CANADA Montreal, CanadaGerard Collin AIR FRANCE Orly Aerogare, FranceJean Baptiste Rigaudias AIR FRANCE Orly Aerogare, FranceJean Le Luc AIR INTER Orly, FranceClarence L. Richmond AMERICAN AIRLINES Tulsa, OklahomaRobert M. Cook DELTA AIRLINES Atlanta, GeorgiaJose M. Recacha IBERIA SPANISH AIRLINES Barajas-Madrid, SpainP. Lorie KLM AIRLINES Amsterdam, NetherlandsLudwig Kilchert LUFTHANSA GERMAN AIRLINES Hamburg, GermanyNorton Codish PAN AM WORLD AIRLINES Jamaica, New YorkVic Persson SCANDINAVIAN AIRLINES Stockholm-Bromma, SwedenKarl H. Riesen SWISSAIR Jamaica, New YorkT. E. Jackson TWA Kansas City, MissouriL. R. Berryhill UNITED AIRLINES Denver, ColoradoM. W. Brecht UNITED AIRLINES San Francisco, CaliforniaO. R. Evans UNITED AIRLINES San Francisco, CaliforniaC. H. Humphrey UNITED AIRLINES San Francisco, CaliforniaRobert K. Moyers U.S. AIR FORCE Washington, D.C.Claude Gouillon UTA Puteaux, FranceWallace L. Urie WESTERN AIRLINES Los Angeles, CaliforniaW. T. Carnes AERONAUTICAL RADIO, INC. Annapolis, MarylandB. R. Clime AERONAUTICAL RADIO, INC. Annapolis, MarylandD. H. Featherstone AERONAUTICAL RADIO, INC. Annapolis, MarylandC. C. Tinsley AERONAUTICAL RADIO, INC. Annapolis, Maryland

Manufacturers and Others

Bernard E. Bouet AEROSPATIALE Toulouse, FranceJean Tambareau AEROSPATIALE Toulouse, FranceRussell Fine AIRESEARCH MFG. CO. Torrance, CaliforniaWilliam M. Russell III AIR TRANSPORT ASSOCIATION Washington, D.C.S. R. Sporn ARMA DIV./AMBAC Garden City, New YorkRobert L. Daniel AVIATION CONSULTANT Studio City, CaliforniaJean Francois Ferreri AVIONS MARCEL DASSAULT Saint Cloud, FranceJay J. Ahmann BENDIX AVIONICS DIV. Burbank, CaliforniaT. H. Hitt BENDIX AVIONICS DIV. Burbank, CaliforniaBrendan J. Spratt BENDIX AVIONICS DIV. Ft. Lauderdale, FloridaWilliam C. Thompson BENDIX AVIONICS DIV. Ft. Lauderdale, Florida



James C. Whalen BENDIX AVIONICS DIV. Ft. Lauderdale, FloridaHoward E. Allen BENDIX CORP. FLIGHT SYSTEMS Tukwila, WashingtonDonald L. Beckman BENDIX CORP. FLIGHT SYSTEMS Teterboro, New JerseyJerry Doniger BENDIX CORP. FLIGHT SYSTEMS Teterboro, New JerseyKen Kendall BENDIX CORP. FLIGHT SYSTEMS Teterboro, New JerseyAlbert T. Kirchhein BENDIX CORP. FLIGHT SYSTEMS Teterboro, New JerseyHarry W. Bedell Jr. BENDIX LONG BEACH FAC. Lakewood, CaliforniaDwayne Broderson BOEING COMMERCIAL AIRPLANE Seattle, WashingtonJames R. Fries BOEING COMMERCIAL AIRPLANE Seattle, WashingtonR. F. Gorman BOEING COMMERCIAL AIRPLANE Seattle, WashingtonAnthony J. Martin BOEING COMMERCIAL AIRPLANE Seattle, WashingtonJ. McHutchison BOEING COMMERCIAL AIRPLANE Seattle, WashingtonRichard A. Peal BOEING COMMERCIAL AIRPLANE Seattle, WashingtonFrank A. Rasmussen BOEING COMMERCIAL AIRPLANE Seattle, WashingtonIrving R. Reese BOEING COMMERCIAL AIRPLANE Seattle, WashingtonE. T. Schroeder BOEING COMMERCIAL AIRPLANE Seattle, WashingtonV. J. Small BOEING COMMERCIAL AIRPLANE Seattle, WashingtonRobert W. Sutton BOEING COMMERCIAL AIRPLANE Seattle, WashingtonRay Hillman BRITISH AEROSPACE Surrey, EnglandRichard A. Keall BRITISH AEROSPACE Hatfield, EnglandDonald J. Gussin CANADIAN MARCONI CO. Montreal, CanadaArvind J. Dandekar COLLINS RADIO GROUP Cedar Rapids, IowaR. V. Donaldson COLLINS RADIO GROUP Cedar Rapids, IowaJ. C. Hall COLLINS RADIO GROUP Cedar Rapids, IowaBryand C. Hawkins COLLINS RADIO GROUP Cedar Rapids, IowaEugene C. Machacer COLLINS RADIO GROUP Cedar Rapids, IowaDonald H. Wickenkamp COLLINS RADIO GROUP Cedar Rapids, IowaJohn F. Lent CROUZET Pasadena, CaliforniaMichel Pascal CROUZET Valence, FranceRichard A. Johnson DELCO ELECTRONICS DIV. GMC Milwaukee, WisconsinL. David Lewis DELCO ELECTRONICS DIV. GMC Milwaukee, WisconsinJohn H. Sheldrick DELCO ELECTRONICS DIV. GMC Milwaukee, WisconsinTom Sizlo DOUGLAS AIRCRAFT COMPANY Long Beach, CaliforniaJohn Carter E-A INDUSTRIAL CORP. Chamblee, CaliforniaDavid Burton ELDEC CORPORATION Lynnwood, CaliforniaRoy F. Keating ELDEC CORPORATION Lynnwood, CaliforniaRene Plouhinec ELECTRONIQUE MARCEL DASSAULT Saint Cloud, FranceJohn E. Reed FAA Washington, D.C.Charles Sheets GARRETT CORP. Torrance, CaliforniaRobert E. Weir GARRETT AIREASEARCH Torrance, CaliforniaRichard Haley HAMILTON STANDARD Windsor Locks, ConnecticutS. C. Caliendi HAWKER SIDDELEY AVIATION Hatfield, Herts, EnglandHarry Graves HONEYWELL INC. Minneapolis, MinnesotaRonald G. Raymond HONEYWELL INC. St. Louis Park, MinnesotaClaude P. Roquefeuill ISPENA Paris, FranceJack Hawkins ITT CANNON ELECTRIC Santa Ana, CaliforniaJ. Langenback ITT CANNON ELECTRIC Santa Ana, CaliforniaRay Swanson JAEGER Pasadena, CaliforniaKen Berg KING RADIO CORP Olathe, KansasDavid A. Nelson KING RADIO CORP Olathe, KansasJohn C. Cotton LITTON AERO PRODUCTS Woodland Hills, CaliforniaL. J. Singleton LITTON AERO PRODUCTS Woodland Hills, CaliforniaP. H. Weinheimer LITTON AERO PRODUCTS Seattle, WashingtonWilliam R. Beckman LOCKHEED CALIFORNIA CO Burbank, CaliforniaJob Van Der Bliek LOCKHEED CALIFORNIA CO Burbank, CaliforniaWm. J. Hillman LOCKHEED CALIFORNIA CO Burbank, CaliforniaEd Selvig LOCKHEED CALIFORNIA CO Burbank, CaliforniaBarry J. Aldridge MARCONI ELLIOTT AVIONICS Rochester Kent, UKGordon Belcher MARCONI ELLIOTT AVIONICS Rochester Kent, UKDerek Marshall MARCONI ELLIOTT AVIONICS Seattle, WashingtonKarl-Heinz Terheiden MESSERSCHMITT-BLOKOW-BLOHM Hamburg, GermanyHarold L. Pierson MITRE CORPORATION McLean, VirginiaRichard W. Telsch MITRE CORPORATION McLean, VirginiaGary C. Horan PRATT & WHITNEY AIRCRAFT East Hartford, ConnecticutG. A. Lucchi RCA Van Nuys, California



Gerard A. Collin SAGEM Paris, FranceLloret SAGEM Paris, FranceJean-Yves Begeault SFENA Velizy-Villacoublay, FranceJefferson Z. Amacker SINGER KEARFOTT Little Falls, New JerseyJoseph Koprowski SINGER KEARFOTT Little Falls, New JerseyJohn Desmond SMITHS INDUSTRIES INC. Clearwater, FloridaDave Richardson SMITHS INDUSTRIES INC. Clearwater, FloridaBrian Williams SMITHS INDUSTRIES INC. Cheltenham, Glos, UKMike C. Pietromonaco S. P. INC Bellevue, WashingtonDonald Baker SPERRY FLIGHT SYSTEMS Phoenix, ArizonaDon Burkholder SPERRY FLIGHT SYSTEMS Phoenix, ArizonaJack E. Emfinger SPERRY FLIGHT SYSTEMS Phoenix, ArizonaD. A. Few SPERRY FLIGHT SYSTEMS Phoenix, ArizonaMartin S. Klemes SPERRY FLIGHT SYSTEMS Phoenix, ArizonaR. J. Lofquist SPERRY FLIGHT SYSTEMS Phoenix, ArizonaHarry Miller SPERRY FLIGHT SYSTEMS Phoenix, ArizonaRonald H. Neeves SPERRY FLIGHT SYSTEMS Phoenix, ArizonaEdmond Olive SPERRY FLIGHT SYSTEMS Phoenix, ArizonaR. E. Schaffer SPERRY FLIGHT SYSTEMS Phoenix, ArizonaHarry O. Smith SPERRY FLIGHT SYSTEMS Phoenix, ArizonaAl J. Venancio SPERRY FLIGHT SYSTEMS Phoenix, ArizonaLou Borbely SUNSTRAND DATA CONTROL Redmond, WashingtonGlenn H. Jones SUNSTRAND DATA CONTROL Redmond, WashingtonRobert Schaeperkoetter SUNSTRAND DATA CONTROL Redmond, WashingtonC. A. Bennet TELEDYNE CONTROLS El Segundo, CaliforniaH. E. Sutherland TELEDYNE CONTROLS El Segundo, CaliforniaD. A. Giroux THOMSON-CSF Les-Moulineaux, FranceCharles Legrand THOMSON-CSF Les-Moulineaux, FranceJ. Ribiere THOMSON-CSF Malakoff, FranceJ. Lane Ware THOMSON-CSF New York, New YorkWilliam Donnell TRACOR APPLIED TECHNOLOGY Austin, TexasR. R. Fay TRACOR APPLIED TECHNOLOGY Austin, TexasJean-Pierre Tomasi TRT Le Plessis-Robinson, FranceBlaine C. Ferch USAF Wright Patterson AFB, OhioErwin C. Gangi USAF Dayton, OhioCapt. R. A. Glastetter USAF Wright Patterson AFB, Ohio

AERONAUTICAL RADIO, INC.2551 Riva Road

Annapolis, Maryland 21401- 7645 USA

SUPPLEMENT 1

TO

ARINC SPECIFICATION 429


Published: June 1, 1978


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 materialrelated to the transfer of graphic and ISO alphabet No. 5encoded alpha/numeric data by the Mark 33 DITS. Also,it clarifies the purpose of the SDI function, adds BCD andBNR numeric data encoding examples to Attachment 6and introduces two Appendices into the Specification.

B. ORGANIZATION OF THIS SUPPLEMENT

The first part of this document, printed on goldenrodpaper, contains descriptions of the changes introducedinto the Specification by this Supplement, and, whereappropriate, extracts from the original text for comparisonpurposes. The second part consists of replacement whitepages for the Specification, modified to reflect thesechanges. The modified and added material on eachreplacement page is identified with “c-1” symbols in themargins. Existing copies of Specification 429 may beupdated by simply inserting the replacement white pageswhere necessary and destroying the pages they replace.The goldenrod pages should be inserted inside the rearcover of the Specification.

Copies of the Specification bearing the number 429-1already contain this Supplement and thus do not requirerevisions by the reader.

C. CHANGES TO SPECIFICATION 429INTRODUCED BY THIS SUPPLEMENT

This section presents a complete tabulation of the changesand additions to the Specification introduced by thisSupplement. Each change or addition is identified by thesection number and title currently employed in theSpecification, or by the section number and title that willbe employed when the Supplement is eventuallyincorporated. In each case there is included a briefdescription of the addition or change and, for other thanvery minor revisions, any text originally contained in theSpecification 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.


COMMENTARY

revised to improved clarity of opening sentence, andto modify the statement concerning the BCD-encoding of latitude and longitude as a consequenceof the clarification of the use priorities for bit nos. 9and 10 introduced into Section 2.1.4 by thisSupplement.

ORIGINAL TEXT FOLLOWS

To permit the use of common hardware elements for thetransmission of BNR and BCD numeric data, the formatfor the Mark 33 DITS BCD word differs from that usedformerly for this type of data. Bit no. 32 is assigned toparity, bit nos. 31 and 30 to the sign/status matrix, bit no.29 is the most significant bit of the data field, and themaximum decimal value of the most significant characteris 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 maximumdecimal value of the most significant character was 3.This format made the word 8-bit byte oriented withrespect to the data. This characteristic is not retained inthe Mark 33 system.

Also, the Mark 33 BCD word will not accommodatelatitude and longitude to the formerly specified resolutionof 0.1 minute of arc. If BCD transmission of thesequantities in required, either the resolution must bedecreased or the word must be restructured.Restructuring involves limiting the maximum decimalvalue of the most significant character to 1, moving theremaining BCD characters towards the MSB by two bitpositions and using bit nos. 9 and 10 for data instead ofreserving them for source/destination identificationencoding per Section 2.1.4 of this document. It isprobable, however, that future latitude and longitudedisplays will not be the simple, dedicated read-out typefor which BCD data is intended. More likely is the use ofsome form of multiple-message display, such as a CRT,which will be backed by its own data processor and preferinputs of BNR data. If this proves to be the case, therewill be no problem!


Text expanded to explain differing roles of label codes innumeric (BCD/BNR) and alpha/numeric (ISO AlphabetNo. 5) data transfer. “Special Note” added.


The first eight bits of each word are assigned to a labelfunction so that the data contained in the word may beidentified. Label code assignments are set forth in thetable of Attachment 1 to this document.


Section modified to indicate that bit nos. 9 & 10 are notavailable for the SDI function in DITS words employedfor graphic and ISO Alphabet No. 5 data transfer, or inBNR/BCD words in which bit nos. 9 and 10 are neededfor valid data in order to achieve the desired resolution.Code table revised and function application more fullydescribed. Consequential revisions to Commentary.



Bit nos. 9 & 10 of the word should be reserved for a datasource/destination identification function. This functionmay find application when specific words need to bedirected to a specific system of a multi-system installationor when the source system of a multi-system installationneeds to be recognizable from the word content. Whenthe source/destination identifier function is used, bit nos.9 & 10 should be encoded as follows. When it is notused, binary zeros or valid data should be transmitted inthese positions

Bit No.10 9 System

0 0 10 1 21 0 31 1 4

.COMMENTARY

In many applications of the Mark 33 DITS, datasource/destination identification will not be needed.In these cases, bits 9 & 10 will be used as pad bits forvalid data. In certain other applications of thesystem, for example, BCD latitude and longitudeencoding (if needed – see Commentary followingSection 2.1.2 of this document), the need to use bitnos. 9 and 10 to obtain adequate data resolution willpreclude source/destination identification in this way.

Note that this document does not address thepractical question of how these bits will be set inthose multi-system installations in which thesource/destination identification function is desired.One way would be to use program pins on individualsystem black boxes which would be wired to set upthe appropriate code. The ARINC Characteristicsdevoted to the individual systems will define themethod actually to be used.


Section divided into two sub-sections, one to describe theBCD numeric and ISO Alphabet #5 alpha/numeric datasign status matrix, and the other to describe the BNRnumeric data sign/status matrix.


The “sign” (plus, minus, north, south, etc.) of thetransmitted data and the status of the transmitter hardwareshould be encoded in bit nos. 30 and 31 as shown in thetable below.

DesignationBit No.

31 30 BNR/BCD Data ISO # 5 Data

0 0 Plus, North, EastRight, To

0 1 No Computed Data TBD1 0 Functional Test1 1 Minus, South, West,

Left, From

Notes:1. A source system should indicate failure by ceasing to

supply data to a bus.

2. Both bits should be “zero” in BNR and BCD wordswhen no sign is needed.

3. The “no computed data” code should be generatedwhen computed data is not available for reasons otherthan equipment failure.

4. When is appears in a word identified by its label as asystem output, the “functional test” code should beinterpreted as advice that the data in the word resultsfrom the execution of a functional test. When itappears in a word identified by its label as aninstruction, e.g., a radio channel change command,this code should be interpreted as a command toperform a functional test.


Typographical errors corrected in second paragraph ofCommentary.


Existing material supplemented with informationconcerning shield grounding.


DC levels between terminal A and ground and terminal Band ground at which receivers should not be damagedraised from +20VDC to +28VDC (min) and for –20VDCto –28VDC (min) respectively to align numerical valueswith aircraft DC power supply value.

2.3.1.3 ISO Alphabet No. 5 Data


2.4.1 Bit Rate

Existing commentary supplemented with warning againstselection of 13.6 KBPS and 100 KBPS because ofpossible interference with operation of OMEGA andLORAN 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” ineach case.

Attachment 2: Data Standards Table 3

Table 3 (Alpha/Numeric (ISO Alphabet No. 5) DataStandards) deleted. Table 4 (Discrete Data) renumberedTable 3.

Note: Table 3 was reserved for alpha/numeric (ISOAlphabet No. 5) data standards prior to the preparation ofthis Supplement. The need for it disappeared as a resultof the particular approach selected for handling this dataintroduced into Specification 429 by this Supplement.


Attachment 6: General Word Formats and EncodingExamples

BNR word format example amended as consequence ofchange to sign/status matrix (see Section 2.1.5) GeneralWord Formats for ISO Alphabet No. 5 data added.Encoding examples added.

Appendix 1: Laboratory Verification of ARINC 429DITS Electrical Characteristics

New material added by this Supplement.

Appendix 2: An Approach to a Hybrid BroadcastCommand/Response Data Bus Architecture.

New material added by this Supplement.

NOTE: Due to the large number of changesCreated by this Supplement, it is NOTavailable separately to update 429-1.



SUPPLEMENT 2

TO



Published: March 1, 1979


Adopted by the Airlines Electronic Engineering Committee: December 6, 1978



This Supplement amends the material added toSpecification 429 on ISO Alphabet No. 5 data transfer,and expands the multiple-word DITS message conceptfirst 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 Specificationare amended to bring them into line with adoptedpractice in the control of DME’s and ATC transponders,and supplemented with material related to the multiple-word message applications of the system justmentioned. Also, additions and modifications havebeen made to the label codes and data standards inAttachments 1 and 2 of the Specification to bring theminto line with adopted practice.


The first part of this document, printed on goldenrodpaper, contains descriptions of the changes introducedinto the Specification by this Supplement, and, whereappropriate, extracts from the original test forcomparison purposes. The second part consists ofreplacement white pages for the Specification, modifiedto reflect these changes. The modified and addedmaterial on each replacement page is identified with “c-2” symbols in the margins. Existing copies ofSpecification 429 may be updated by simply insertingthe replacement white pages where necessary anddestroying the pages they replace. The goldenrod pagesshould be inserted inside the rear cover of theSpecification.



This section presents a complete tabulation of thechanges and additions to the Specification introduced bythis Supplement. Each change or addition is entitled bythe section number and title currently employed in theSpecification, or by the section number and title thatwill be employed when the Supplement is eventuallyincorporated. In each case there is included a briefdescription of the addition or change and, for other thanvery minor revisions, any text originally contained inthe Specification is reproduced for reference.

2.1.2 INFORMATION ELEMENT

Text revised to describe word application groups.

ORIGINAL TEXT FOLLOWS:


The basic information element is a digital wordcontaining 32 bits. Word formats for the different typesof data handled by the Mark 33 DITS (see Section 2.3.1of this document) are depicted in Attachment 6. Whenless than the full data field is needed to accommodatethe information conveyed in a word in the desiredmanner, the unused bit positions should be filled withbinary zeros or valid data pad bits. If valid data bits are

used, the resolution possible for the information willexceed that called for in this specification. TheCommentary following Section 2.1.6 of this documentrefers.

2.1.3 INFORMATION IDENTIFIER

Text revised to describe label use forAIM/Discrete/Maintenance data word typeidentification.



The first eight bits of each word are assigned to a labelfunction. Labels will a) identify the informationcontained within numeric (BCD/BNR) data words (e.g.,DME distance, static air temperature), and b) act asreceiving device addresses for alpha/numeric (ISOAlphabet No. 5) data words (e.g., navigation systemCDU or map display). Label code assignments are setforth in Attachment 1 to this document.

2.1.5.1 BCD NUMERIC AND AIM DATA WORDS

Title and text revised to include other AIM applicationsin material originally prepared to describe sign/statusmatrix use in ISO Alphabet No. 5 words, and to providedefinition of Self-Test.


2.1.5.1 BCD Numeric and ISO Alphabet No. 5 DataWords

The sign (plus, minus, north, south, etc.) of BCDnumeric data, the word type of alpha/numeric (ISOalphabet No. 5) data and the status of the transmitterhardware should be encoded in bit nos. 30 and 31 of theword as shown in the table below.

Bit No. Designation

31 30 BNR/BCD Data ISO #5Data

0 0 Plus, North, EastRight, to Initial Word

0 1 No Computed Data No ComputedData

1 0 Functional Test IntermediateWord

1 1 Minus, South, WestLeft, From Final Word

Notes:1. A source system should annunciate any detected

failure that causes one or more of the wordsnormally output by that system to be unreliableby ceasing to supply the affected word orwords to the data bus.

2. Both bits should be “zero” when no sign isneeded.

3. The “no computed data” code should begenerated when computed data is notavailable for reasons other than equipmentfailure.

SUPPLEMENT 2 TO ARINC SPCIFICATION 429 - Page 3

4. When it appears in a word identified by its label asa system output, the “functional test” code shouldbe interpreted as advice that the data in the wordresults from the execution of a functional test.When it appears in a word identified by its label asan instruction, e.g., a radio channel changecommand, this code should be interpreted as acommand to perform a functional test.

5. See Section 2.3.1.3 of this document for definitionsof the terms “Initial Word”, “Intermediate Word”and “Final Word”.

2.1.5.2 BNR NUMERIC DATA WORDS

Text revised to provide definition of Self-Test.



The sign (plus, minus, north, south, etc.) of BNRnumeric data words and the status of the transmitterhardware should be encoded in bit nos. 29, 30 and 31 ofthe word as shown in the table below.

Bit No.31 30 29

DesignationBNR Data

0 0 0 Failure Warning/Plus, North, EastRight, To

0 0 1 Failure Warning/Minus, South, West,Left, From

0 1 0 No Computed Data

1 0 0 Functional Test/Plus, North, East,Right, To

1 0 1 Functional Test/Minus, South, WestLeft, From

1 1 0 Normal Operation/Plus, North, East,Right, To

1 1 1 Normal Operation/Minus, SouthWest, Left, From

0 1 1 Not Used (Growth)

Notes:

1. A source system should annunciate any detectedfailure that causes one or more of the wordsnormally output by that system to be unreliable bysetting bit nos. 30 and 31 in the affected word(s) tothe “failure warning” code defined above. Wordscontaining this code should continue to be suppliedto the data bus during the failure condition.

2. Bit no. 29 should be “zero” when no sign is needed.

3. The “no computed data” code should be generatedwhen computed data is not available for reasonsother than equipment failure.

4. When it appears in a word identified by its label asa system output, the “functional test” code shouldbe interpreted as advice that the data in the wordresults from the execution of a functional test. Aself-test should produce indications of 1/8 ofpositive full-scale values unless indicated otherwisein an ARINC Equipment Characteristic.

5. If, during the execution of a functional test, asource system detects a failure which causes one ormore of the words normally output by that systemto be unreliable, it should immediately change thestates of bit nos. 30 and 31 in the annunciation isreplaced with the “failure warning” annunciation

2.2.3.1 TRANSMITTER VOLTAGE LEVELS

Tolerances on “HI” and “LO” voltage states changedfrom ± 0.5 volt to ± 1.0 volt to correct previouslyundetected error.

2.3.1.2 DISCRETES

Minor changes to existing wording to improve clarity.New paragraphs added to describe two types ofdedicated –to-discrete words and their applications.


2.3.1.2 Discretes

In addition to handling numeric data as specified above,the Mark 33 DITS should also be capable ofaccommodating discrete items of information, either inthe “spare” bits of data words or, when necessary, indedicated words. Any discrete information contained ina word assigned a label in Attachment 1 is specified inthe definition for that word in Attachment 2.

The rule to be followed in the assignment of bits todiscrete functions is to start with the least significant bitavailable in the word and to continue towards the mostsignificant bit. Attachment 6 shows this against thebackground of the generalized word structure.

2.3.1.3 Maintenance Data (General Purpose)

This section inserted to describe use and application ofgeneral purpose Maintenance words.


2.3.1.3 Alpha/Numeric (ISO Alphabet No. 5) Data

ISO Alphabet No. 5 alpha/numeric data will consist ofseven-bit characters encoded per the table ofAttachment 5 to this document. Three such charactersshould occupy bit nos. 9 through 29 of a DITS 32-bitword, as shown in the general word format diagram inAttachment 6. As for numeric (BCD) data words, bitnos. 1 through 8 should be the word label (receivingdevice address-see Section 2.1.3), bit nos. 30 and 31 thesign/status matrix and bit no. 32 the word parity bit.

The typical alpha/numeric message contains more thanthree ISO Alphabet No. 5 characters, necessitating thetransmission of multi-DITS-word messages. Thefollowing procedure should be used to permit receiversto determine that such messages are received in theirentirety, with no words having been “lost along theway”. Only when this determination has been made,and the parity check for each word shows the data to beerror-free, should the message be displayed to theaircrew or otherwise utilized.


2.3.1.3 Alpha/Numeric (ISO Alphabet No. 5) Data (cont’d)

The first DITS word of the message should contain thelabel in bit nos. 1 through 8, two numeric charactersencoded per ISO Alphabet No. 5 in bit nos. 9 through15 and 16 through 22 and the ISO Alphabet No. 5control character “STX”in bit nos. 23 through 29. Thetwo numeric characters should indicate the decimalnumber of DITS words in the message (maximumnumber is 99), with the most significant characteroccupying bit nos. 16 through 22. This count, whichshould include this initial word, will be one plus thenext whole number greater than one third of the numberof ISO Alphabet No. 5 characters to be transmitted. Thesign/status matrix should contain the “initial word” codedefined in Section 2.1.5 of this document.

The subsequent DITS words of the message should eachcontain the label in bit nos. 1 through 8 and three ISOAlphabet No. 5 characters. The sign/status matrix of allthese words except the last word should contain the“intermediate word” code defined in Section 2.1.5.1 ofthis document. The last word of the message shouldcontain the “final word” code in its sign/status matrix.Any unused bit positions in the final word resultingfrom the number of ISO characters in the message beingone or two less than a number wholly divisible by threeshould be filled with binary “zeros”.

2.3.1.4 AIM Data

Section number, text and title revised to include otherAIM word applications in material originally preparedto describe ISO Alphabet No. 5 data handling(originally in Section 2.3.1.3). Detailed amendments inthis area also.

3.1.4.2 DME

The “Override” switching function has been replaced bythe “DME Mode Select” function.

3.1.4.7 ATC TRANSPONDER

“Mode A/B Select” and “Standby” deleted from list ofswitching functions. Control word format re-structuredto release bits unneeded in numeric data part of word forassignment to discrete switching functions.

Fig. 3-1 Radio Systems Management Word Formats

Bit nos. 11 and 12 in the DME data word have beenassigned to “DME Mode Select”.

The description of bit 14 in the VOR/ILS data word hasbeen revised to improve clarity.


[1] When bit no. 4 is “zero”, the ILS mode shouldbe “off. When bit no 14 is “one”, the ILSmode should be “one”.


ORIGINAL ATC TRANSPONDER WORD FORMAT ILLUSTRATION FOLLOWS:

PAR

ITY

(od

d)

SIG

N/S

TA

TU

SM

AT

RIX

0.7

(3)

0.7

(6)

0.7

(2)

0.7

(0)

A/B

Mod

e Se

lect

IDE

NT

STA

ND

BY

AL

T. R

EP.

OFF

RE

SER

VE

D(S

DI)

LABELBeacon Transponder Code

ATCTRANSPONDER

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

11 0

10 9 0 0

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

[1]

[1]Bit Zero One

11121314

Alt. Rep. ONStandby OFFIdent OFFSelect Mode A

Alt. Rep. OFFStandby ONIdent ONSelect Mode B

The revised format of the ATC transponder word is as shownon page 10.



Attachment 1: Label codes

Some parameter names have been changed and others havebeen added to the list. Instead of showing the entire list, onlythe original assignment of those that have been changed areshown below.


Label (Octal) Original Assignment Proposed Assignment

007 Align Status/Inertial Discretes No assignment014 None assigned Magnetic Heading015 None assigned Wind Speed016 None assigned Wind Direction-True017 None assigned Selected Runway Heading024 Selected Course Selected Course #1027 None assigned Selected Course #2041 None assigned Set Latitude042 None assigned Set Longitude043 None assigned Set Magnetic Heading044 None assigned True heading045 None assigned Minimum Airspeed100 Selected Course Selected Course #1107 AFS Discretes No assignment110 None assigned Selected Course #2112 None assigned Selected EPR or N1124 FMC Discretes Caution & Warning DFDR Discretes #1130 None assigned Tt2131 None assigned Pt2132 None assigned Pt7133 None assigned Thrust Lever Angle145 None assigned AFS DFDR Discretes #1146 None assigned AFS DFDR Discretes #2147 None assigned AFS DFDR Discretes #3166 None assigned RALT Check Point Dev.203 Altitude (29.92) Altitude (1013.25mb)204 Altitude (Baro) Baro Corrected Altitude #1214 Air Data Computer Discretes No assignment216 Baroset No assignment220 None assigned Baro Corrected Altitude #2221 None assigned Indicated Angle of Attack223 Altitude (29.92) No assignment224 Altitude Baro Caution/Warning DFDR Discretes #2225 Mach No assignment226 Computed Airspeed No assignment227 Max Allowable Airspeed No assignment234 Baroset (millibars) Baro Correction (mb #1)235 Baroset (ins. of Hg) Baro Correction (mb #1)236 None assigned Baro Correction (mb #2)237 None assigned Baro Corrected (in of Hg #2)241 None assigned Corrected Angle of Attack242 None assigned Total Pressure245 None assigned Minimum Airspeed247 None assigned Total Fuel270 None assigned Discrete Data #1271 None assigned Discrete Data #2272 None assigned Discrete Data #3273 None assigned Discrete Data #4274 None assigned Discrete Data #5334 Free Heading Platform Heading340 N1 or EPR Actual EPR Actual346 None assigned N1 Actual350 Engine Discretes Maintenance Data #1351 Control Panel Discretes Maintenance Data #2352 Control Panel Discretes Maintenance Data #3353 Control Panel Discretes Maintenance Data #4354 Instrument Discretes Maintenance Data #5355 None assigned Acknowledgement356 None assigned Maintenance ISO #5 Message357 None assigned ISO #5 Message360 None assigned Potential Vertical Speed372 None assigned Wind Direction-Magnetic373 None assigned N-S Velocity-Magnetic374 None assigned E-W Velocity-Magnetic375 None assigned Along Heading Acceleration376 None assigned Cross Heading Acceleration


Attachment 2: Data Standards

A number of additions and changes have been made to thetables. The octal labels and parameter names are shown foreach data item that has been changed. The original data isshown only for the data that has been changed by thissupplement. Also a second “Note” has been added to Table 2.

Table 1 BCD DATA

Label(Octal)

ParameterName

MaxTransmitInterval

Range (Scale) Sig.Fig.

PadFig. Units Resol

170 Decision Hgt Sel.(EFI) 200 0 - 500 3 2 Feet 1.0201 DME Distance 200* -1 - 399.99* 5 0 N.M. 0.01230 True Airspeed 500* 130 - 599* 3 2 Knots 1.0231 Total Air Temp. 500 +500 — 99* 2 3 oc 1.0233 Static Air Temp. 500 -99 - +60* 2 3 oc 1.0234 Baroset (mb)* 200* 0 - 3999* 4* 1* mb 1.0*235 Baroset (ins. of Hg*) 200* 0 - 39.99* 4* 1* ins.Hg 0.01*

*This data has been changed.

Note: Labels 017, 027, 041, 042, 043, 044, 045, 236 and 237 previously had no values assigned. Values for labels 223, 224,225, 226 and 227 have been changed.

Table 2 BNR DATA

Label(Octal)

ParameterName

MaxTransmitInterval

Sig. Bits(Not Inc.Sign)

Units Range Approx.Resol.

100 Selected Course 62.5* 9 Deg/180 ± 180 o 0.35o

103 Selected Airspeed 62.5* 11* Deg/180 ± 180 o 0.25*121 Horiz. Strg. Signal 100 9* Deg/180 +45o * 0.1 o *122 Vert.Strg.Signal 100 9 Deg/180 +22.50 o * 0.05 o *140 Flight Director-Roll 62.5* 9 Deg/180 ±45 o 0.1 o

141 Flight Director-Pitch 62.5* 9 Deg/180 ± 22.5 0.05 o

164 Radio Height 50 18* Feet 32768* 0.125202 DME Distance 200* 16 N.M. 512 0.0008203 Altitude (29.92) 62.5 17* Feet 131,071 1.0*206 Computed Airspeed 125 12* Knots 1024 0.25*207 Max.Allowable Airspeed 500* 12 Knots 1024 0.25210 True Airspeed 500* 11 Knots 2048 1.0215 Impact Pressure 125 12* ins/Hg* 32* 0.008*313 Track Angle True 50* 12 Deg/180 ± 180 o 0.05 o

314 True Heading 50* 12 Deg/180 ± 180 o 0.05 o

317 Track Angle-Magnetic 50* 12 Deg/180 ± 180 o 0.05 o

320 Magnetic Heading 50* 12 Deg/180 ± 180 o 0.05 o

321 Drift Angle 50* 11 Deg/180 +90 o 0.05 o

322 Flight Path Angle 50* 10 Deg/180 ± 45 o 0.05 o

323 Flight Path Acceleration 20 12* g 4* 0.001*324 Pitch Angle 50* 13 Deg/180 +90 o 0.01 o

325 Roll Angle 50* 14 Deg/180 ± 180 o 0.01 o

331 Body Long-accel. 6.25* 12 g 4 0.001334 Free Heading 20* 12* Deg/180 ± 180 o 0.05 o

335 Track Angle Rate * * * * *336 Inertial Pitch Rate 20 12* Deg/sec 128 0.03 o *337 Inertial Roll Rate 20 12* Deg/sec 128 0.03 o *340 N1 Actual * 200 12 RPM 4096 1341 N1 Command 200 12* RPM* 4096* 1*342 N1 Limit 200 12* RPM* 4096* 1*343 N1 Derate 200 12* RPM* 4096* 1*344 N2 100 14 RPM* 16384* 1*


Table 2 BNR Data (cont’d)

Label(Octal)

ParameterName

MaxTransmitInterval

Sig. Bits(Not Inc.Sign)

Units Range Approx.Resol.

345 Exhaust Gas Temp. 200 11* OC * 2048 1*346 N1 Actual 200 12* RPM* 4096* 1*347 Fuel Flow 200 11* Lbs/hr 32768 16*362 Along Track Horiz. Accel. 50* 12 g 4 0.001365 Integrated Vertical Accel. 50* 15* Knots 4096* 0.125*366 N-S Velocity 200* 15 Knots 4096 0.125367 E-W Velocity 200* 15 Knots 4096 0.125

Note: Labels 110, 112, 130, 131, 132, 133, 241, 245, 247, 346,360, 372, 373, 374 and 376 previously had no valuesassigned. Values for label 216 have been deleted.

*This data has been changed.

Attachment 6: General Word Formats and Encoding Examples

AIM word format examples have been added. Detaileddescriptions of these words have been included in the text ofSection 2.3.1.3.



SUPPLEMENT 3

TO



Published: November 1, 1979


Adopted by the Airlines Electronic Engineering Committee: August 31, 1979



This Supplement introduces material on the transfer offile data and the related protocol. The file transfercapability is being added primarily for the Flightmanagement Computer (FMC) program/data load andupdate and FMC intersystem crosstalk. A number oflabels and corresponding data standards have beenadded.


The first part of this document, printed on goldenrodpaper, contains descriptions of the changes introducedinto the Specification by this Supplement; and, whereappropriate, extracts from the original text forcomparison purposes. The second part consists ofreplacement white pages for the Specification, modifiedto reflect these changes. The modified and addedmaterial on each replacement page is identified with “c-3” symbols in the margins. Existing copies ofSpecification 429 may be updated by simply insertingthe replacement white pages where necessary anddestroying the pages they replace. The goldenrod pagesshould be inserted inside the rear cover of theSpecification.



This section presents a complete tabulation of thechanges and additions to the Specification introducedby this Supplement. Each change or addition is entitledby the section number and title currently employed inthe Specification or by the section number and title thatwill be employed when the Supplement is eventuallyincorporated. In each case there is included a briefdescription of the addition or change and, for other thanvery minor revisions, any text originally contained inthe Specification is reproduced for reference.

2.1.5.1 BCD NUMERIC, DISCRETE AND AIMDATA WORDS

Table amended to provide consistency between AIMand file transfer data words.


Bit No. Designation31 30 BCD Numeric Data AIM Data

0 0 Plus, North EastRight, To Final Word

0 1 No Computed Data Intermed.Word

1 0 Functional Test Control Word

1 1 Minus, SouthWest, Left, From Initial Word

2.1.6 DATA STANDARDS

Text added to clarify data encoding.



The units, ranges, resolutions, refresh rates, number ofsignificant bits, pad bits etc. for the items ofinformation to be transferred by the Mark 33 DITS aretabulated in Attachment 2 to this document.

COMMENTARY

Note that Section 2.3.1.1 of this document calls fornumeric data to be encoded in BCD and binary, thelatter using two’s complement fractional notation.In this notation, the most significant bit of the datafiled represents one half of the maximum valuechosen for the parameter being defined.Successive bits represents the increments of abinary fraction series. Negative number areencoded as the complements of positive values andthe negative sign is annunciated in the sign/statusmatrix.

In establishing a given parameter’s binary datastandards for inclusion in Attachment 2, the units,maximum value and resolution of the parameterare first determined in that order. The leastsignificant bit of the word is then given a valueequal to the resolution increment, and the numberof significant bits is chosen such that the maximumvalue of the fractional binary series just exceedsthe maximum value of the parameter, i.e., equalsthe next whole binary number greater than themaximum parameter value less one leastsignificant bit value. For example, if the Mark 33DITS is required to transfer altitude in units of feetover a range of zero to 100,000 feet with aresolution of one foot, the number of significantbits is 17 and the maximum value of the fractionalbinary series is 131,071 (i.e., 131,071 – 1). Notethat because accuracy is a quality of themeasurement process and not the data transferprocess, it plays no part in the selection of wordcharacteristics. Obviously, the resolution providedin the DITS word should equal or exceed theaccuracy in order not to degrade it.

For the binary representation of angular data, theMark 33 DITS employs “degrees divided by 180o”as the unit of data transfer and ± 1 (semicircle) asthe range for two’s complement fractional notationencoding ignoring, for the moment, the subtractionof the least significant bit value. Thus the angularrange 0 through 359.XXX degrees is encoded as 0through ± 179.XXX degrees, the value of the mostsignificant bit is none half semicircle and there areno discontinuities in the code.

For convenience, all binary word ranges inAttachment 2 are shown as whole binary numbersrather than such numbers less one least significantbit value. Also the resolutions shown areapproximate only. Accurate resolutions can bedetermined, if required, by reference to the rangevalues and numbers of significant bits for thewords of interest.


2.1.6 Data Standards (cont’d)


It should be noted that in all applications of thetwo’s complement fractional notation, themaximum value of the word, once chosen, cannotbe changed by the use of more bits in the data field.The number of bits in the word affects only theresolution of the data, not its range.

Binary coded decimal (BCD) data is encoded perthe numeric subset of the ISO Alphabet No. 5 code(see Attachment 5 to this document) using bit nos.1 through 4 of the seven-bit-per-character code.Alpha/numeric data is encoded using all seven bitsper character of the ISO Alphabet #5 code and istransmitted using the special word formatdescribed in Section 2.3.1.3 of this document.

2.3.1.5 FILE DATA TRANSFER

Section added to provide description of file datatransfer protocol.

3.1.4.3 HF COMMUNICATIONS

Text amended to describe switching functions and finerfrequency selection increments.


3.1.4.3 HF Communications

Frequency Range: 2.8MHz to 24MHzFrequency Selection 1kHz

IncrementsCharacters encoded 10MHz, 1MHz, 0.1MHz,

in DITS word: 0.01MHz, 0.001MHzSwitching Functions: USB/AM mode selection

Fig. 3-1 RADIO SYSTEMS MANAGEMENT WORDFORMATS

Error corrected in bits 24 and 25 of ILS word.

HF COMM frequency word format changed andsecond word added to enable the use of 100 Hz channelspacing.


HF COM

Function

PAR

ITY

(O

dd)

SIG

N/S

TA

TU

SM

AT

RIX

10M

Hz

(

2)

1MH

z

(3)

0.1M

Hz

(

5)

0.01

MH

z

(7)

0.00

1MH

z

(9

)

USB

/AM

MO

DE

RE

SER

VE

D (

SDI)


Bit No.ExampleNotes

32 0

31 30 0 0

29 28 27 0 1 0

26 25 24 23 0 0 1 1

22 21 20 19 0 1 0 1

18 17 16 15 0 1 1 1

14 13 12 11 1 0 0 1

10 0[1]

90[2]

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

[1] When bit no. 10 is “zero” the equipment should operate in the AM mode. When bitno. 10 is “one” the equipment should operate in the SSB (USB) mode.

[2] Only bit no. 9 is available for the SDI function in this word.

ATTACHMENT 1: LABEL CODES

The following labels have been given new assignments:

053, 056, 060, 061, 062, 063, 065, 066, 067, 070, 071, 075, 076, 077, 120, 126, 134, 137, 143, 175, 176, 177, 200, 217,226, 251, 252-256, 257, 260, 261, 277, 300-307, 361.

ATTACHMENT 2: DATA STANDARDS

Tables 1 and 2 have both additions and modifications made to the data standards. Notes 2 thru 5 deleted. The originalinformation provided in ARINC 429-2 is included in these tables. An asterisk beside a value designated that a changehas been recommended. The formats of table 1 and 2 have also been changed to provide the addition of data standarddescriptors.

Table 3.7 added for GPWS discretes.


ATTACHMENT 2: DATA STANDARDS (cont’d)

TABLE 1 BCD DATA

LABEL(OCTAL)

PARAMETERNAME

MAX.TRANSMITINTERVALmsec

RANGE(SCALE

SIG.FIG.

PADFIG. UNITS RESOL

0 1 0 Present Position-Lat. 200* 90S-90N 5 0 Deg/Min* 0.10 1 1 Present Position-Long. 200* 180E-180W 6 0 Deg/Min* 0.10 1 2 Ground Speed 200* 0-2000 4 1 Knots 1.00 1 3 Track Angle (true) 200* 0-359.9 4 1 Deg 0.10 1 4 Magnetic Heading 200* 0-359 3 2 Deg 1.00 1 5 Wind Speed 200* 0-299 3 2 Knots 1.00 1 6 Wind Direction (true) 200* 0-359 3 2 Deg 1.00 4 1 Set Latitude 200* 90S-90N 5 0 Deg/Min 0.10 4 2 Set Longitude 200* 180E-180W 6 0 Deg/Min 0.10 4 3 Set Magnetic Heading 200* 0-359.9* 4* 1* Deg 0.1*1 2 5 Greenwich Mean Time 200 0-23.59.9 5 0 Hr/Min* 0.12 3 0 True Airspeed 62.5* 100-599 3 0 Knots 1.0

TABLE 2 BNR DATA

LABEL(OCTAL)

PARAMETERNAME

MAX.TRANSMITINTERVAL

msec

SIG. BITS(NOT INC.

SIGN)UNITS RANGE

See Note 1APPROXRESOL

1 0 0 Selected Course #1 50 9* Deg/180 ±180o 0.35*1 0 1 Selected Heading 62.5 9* Deg/180 ±180o 0.35*1 0 5 Selected Runway Heading 62.5 9* Deg/180 ±180o 0.35*1 1 0 Selected Course #2 50 9* Deg/180 ±180o 0.35*1 1 6 Cross Track Distance 62.5 8* N.M. 128 0.5*1 2 1 Horiz. Steering Signal 100 10* Deg/180 ±60 o 0.06*1 2 2 Vertical Steering Signal 100 9* Deg/180 ±30 o 0.06*1 2 3 Throttle Command * * * * *1 3 0 Tt2* 200 11 oC 128 0.061 3 1 Pt2* 200 13 PSIA 32 0.0041 3 2 Pt7* 200 13 PSIA 32 0.0041 4 0 Flight Director-Roll 100 9* Deg/180 ±45 o * 0.1*1 4 1 Flight Director-Pitch 100 9* Deg/180 ±22.5 o 0.051 4 2 Fast/Slow 62.5 8* Knots 32 0.125*1 4 3 Flight Director-Yaw* 100* 12* Deg/180* ±180 o 0.05*1 6 4 Radio Height 50 17* Feet 16384* 0.1252 0 3 Altitude (1013.25mb) 62.5 18* Feet 131,072 0.05*2 1 0 True Airspeed 62.5* 11* Knots 2048 1.0*2 1 1 Total Air Temp. 500 10* oC 512 0.5*2 1 3 Static Air Temp. 500 10* oC 512 0.5*2 2 1 Indicated Angle of Attack 62.5 11* Deg/90* ±90 o * 0.052 4 1 Corrected Angle of Attack 62.5 11* Deg/90* ±90 o * 0.052 4 7 Total Fuel 200* 15* Lb. 655,360 20*3 1 0 Present Position-Lat. 200 18* Deg/180 0-90N-0-90S 0.00035*3 1 1 Present Position-Long. 200 18* Deg/180 0-180E-0-180W 0.00070*3 1 2 Ground speed 100* 15 Knots 4096 0.1253 1 3 Track Angle True 40* 12 Deg/180 ±180 o 0.053 1 4 True Heading 40* 12 Deg/180 ±180 o 0.053 1 7 Track Angle-Mag 40* 12 Deg/180 ±180 o 0.053 2 0 Magnetic Heading 40* 12 Deg/180 ±180 o 0.053 2 1 Drift Angle 40* 11* Deg/180 ±90 o * 0.053 2 2 Flight Path Angle 40* 10* Deg/180 ±45 o * 0.053 2 4 Pitch Angle 20* 13* Deg/180 ±90 o * 0.013 2 5 Roll Angle 20* 14 Deg/180 ±180 o 0.013 6 0 Potential Vertical Speed 50 10* Ft/min* 16384* 16*

# The change to MTI was erroneously omitted from Draft 1 of Supplement 3, but was included prior to publication ofSupplement 3.

#



NOTES

1. The number entered in the Range Column for eachparameter that is not angular in nature is thenearest whole binary number greater than theparameter range required. As explained in theCommentary following Section 2.1.6 of thisdocument, the weight of the most significant bit ofthe two’s complement fractional notation binaryword will be one half this value, and the actualmaximum value of the parameter capable of beingencoded will be the number in the range columnless one least significant bit value. The numbersentered in the RANGE column for angularparameters are the actual degree ranges required.The way in which these parameters are encoded isalso explained in the Commentary followingSection 2.1.6.

2. Bit nos. 9 and 10 of the word may be used toachieve a 20 bit capability for high resolution ofthe Lat./Long. Position (codes 310 and 311). Theresulting resolution is .000086o for latitude and.00017 o for longitude.

3. A change in ARINC 707 not shown in Supplement2 is a planned change for Supplement 3. A self-test inhibit bit will be added and the range of thedata word will be halved to a value of 8192 ft.

4. A change in ARINC 710 not shown in Supplement2 is a planned change for Supplement 3. Theresolution of Selected Runway Heading (BCD andBNR) will be changed to .1 o.

5. A change being considered for Supplement 3 is tochange the range to –6g - +4g to facilitate directrecording by the flight recorder.

ATTACHMENT 6: GENERAL WORD FORMATS &ENCODING EXAMPLES

SSM codes in AIM words changed to reflect tableamendment of section 2.1.5.1.

Radio Height code example changed to reflect shift infield.

Note 4 of Table 6.2 deleted to revert data coding to theoriginal two’s complement notation.

Word formats added for date/flight leg and flightnumber information.

Word format added for VOR Omnibearing.

Codes 203, 204, 206 and 207 deleted in Table 6.1a.


ATTACHMENT 6

GENERAL WORD FORMATS AND ENCODING EXAMPLES

1. GENERAL WORD FORMATS


ATTACHMENT 6: GENERAL WORD FORMATS & ENCODING EXAMPLES (cont’d)


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 inSection 2.1.4 of this document, as are also thelimitations on its use. When the SDI function isnot required, this field may be occupied by binaryzero or valid data pad bits.

[2] Discretes

As discussed in Section 2.3.1.2 of this document,unused bits in a word may be assigned to discretefunctions, one bit per variable. Bit #11 of theword should be the first to be so assigned;followed by bit #12 and so on in ascendingnumerical order until the data field is reached. Inthe absence of discretes, unused bit positionsshould be occupied by binary zero or valid datapad bits.

[3] Pad

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

[4] Sign/Status Matrix (SSM)

Section 2.1.5 of this document describes thefunctions of the sign/status matrix and the ways inwhich the bits constituting it are encoded.

[5] Parity Bit

This bit is encoded to render word parity odd.Section 2.3.4 of this document refers.


TABLE 6-1a

BCD DATA ENCODING EXAMPLES

NOTES: [1] “P” denotes pad “zero” or valid data. Section 2.1.2 if this document refers. Note possible useof pad bits for discrete functions per Section 2.3.1.2.

[2] Because the actual maximum value of the most significant character of each of these quantitiesexceeds 7, it cannot be encoded in the most significant character position of the BCD word. Forthis reason each quantity has been given and “artificial” MSC of zero and its actual MSCencoded in the next most significant character position of the word.


TABLE 6-2

BNR DATA ENCODING EXAMPLES

NOTES: [1] “P” denotes pad “zero” or valid data. Section 2.1.2 of this document refers. Note possible useof pad bits for discrete functions per Section 2.3.1.2.

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

[3] Angles in the range 0 to 180o are encoded as positive numbers. Angles in the range 180 o to 360 o

are subtracted from 360 o and the resulting number encoded as a negative value per note 2. Arcminutes and seconds are encoded as decimal degrees.

[4] Latitude values are encoded as positive angles in the range 0 to 90 o with the sign/status matrixindicating North or South. Longitude values are encoded as positive angles in the range 0 to180 o with the sign/status matrix indicating East or West. Arc minutes and seconds are encodedas decimal degrees.


Annapolis, Maryland 21401 – 7645 USA

SUPPLEMENT 4

TO



Published: August 1, 1980


Adopted by the Airlines Electronic Engineering Committee: June 17, 1980



This Supplement introduces material on defining “NoComputed Data” and “Failure Warning”, priorityassignment of SSM codes, description of fault toleranceand isolation, address capability of A/N messages,command/response protocol, modification of datastandards, addition of new labels, change of some wordformats, addition of material on signal characteristics,change of receiver impedance limits, expansion of thecurrent label, change of the receiver voltage thresholds andmodification of the HF and DME word formats.


The first part of this document, printed on goldenrod paper,contains description of the changes introduced into theSpecification by this Supplement, and, where appropriate,extracts from the original text for comparison purposes.The second part consists of replacement white pages forthe Specification, modified to reflect these changes. Themodified and added material on each replacement page isidentified with “c-4” symbols in the margins. Existingcopies of Specification 429 may be updated by simplyinserting the replacement white pages where necessary anddestroying the pages they replace. The goldenrod pagesshould be inserted inside the rear cover of theSpecification.


C. CHANGES TO SPECIFICATION 429 INTRODUCEDBY THIS SUPPLEMENT

This section presents a complete tabulation of the changesand additions to the Specification introduced by thisSupplement. Each change or addition is entitled by thesection number and title currently employed in theSpecification, or the section number and title that will beemployed when the Supplement is eventually incorporated.In each case there is included a brief description of theaddition or change and, for other than very minorrevisions, any text originally contained in the Specificationis reproduced for reference.

2.1.3 INFORMATION IDENTIFIER

Text changed to describe use of five-character label.

Commentary text partially deleted.



The first eight bits of each word are assigned to a labelfunction. Label will:

a. identify the information contained within BNRand BCD numeric data words (e.g., DME distance,

static air temperature, etc.) and

b. identify the word application for Discrete, Maintenance and AIM data.

Label code assignments are set forth in Attachment 1 tothis document.

Special Note:

In some ARINC 429 DITS applications, a bus will bededicated to delivering a single information element from asource to one or more identical sink devices. In suchcircumstances, the sink device designer might be temptedto assume that decoding the word label is not necessary.Experience has shown, however, that system developmentsfrequently occur that result in the need for additionalinformation elements to appear on the bus. If a sink devicedesigned for service prior to such a development cannotdecode the original word label, it cannot differentiatebetween this word and the new data in the new situation.The message for sink designers should therefore be quiteclear – provide label decoding from the outset, no matterhow strong the temptation to omit it might be.

COMMENTARY

Attachment 1 defines 256 discrete label codes. Thisquantity is expected to meet label assignment needsfor the foreseeable future. Should additional labelingcapability be required in the longer term, it isenvisaged that, rather than extend the length of thelabel field, a scheme will be devised in which existinglabel assignments are duplicated. For example, thesystem could readily accommodate the assignment ofthe same label to two dissimilar parameters for whichthe probability of transmission on the same bus is verylow.

Adherence to the label code assignments ofAttachment 1 is essential in inter-systemcommunications and in intra-system communicationswhere the system elements are defined as “unitinterchangeable” per ARINC Report No. 403. Theassignment of label codes for all such communicationsmust be coordinated with the air transport industry ifchaos is to be avoided. A manufacturer who finds thatAttachment 1 does not specify the label he needs forsuch system application must not simply choose onefrom those unassigned and “drive on”. He shouldcontact ARINC for assistance.

2.1.5.1 BCD NUMERIC, DISCRETE, AIM DATA ANDFILE TRANSFER WORDS

Text describing “no computed data” modified.

Commentary providing definitions added.


2.1.5.1 BCD Numeric, Discrete, AIM Data and FileTransfer Words

The sign (Plus, minus, North, South, etc.) of BCD numericdata, the word type (first, intermediate, control, last) forAIM data, and the status of the transmitter hardware shouldbe encoded in bit nos. 30 and 31 of the word as shown inthe table below. The sign/status matrices of Discretewords should be encoded per the rules set forth for BCDnumeric data.


Bit No. Designation

31 30 BCD NumericWord AIM File Transfer

0 0Plus, NorthEast, RightTo, Above

IntermediateWord

IntermediateWord, Plus,North, etc.

0 1 No ComputedData Initial Word Initial Word

1 0 FunctionalTest Final Word Final Word

1 1Minus, SouthWest, Left,From, Below

ControlWordIntermediateWord, MinusSouth, etc.

Notes:

1. A source system should annunciate any detectedfailure that causes one or more of the words normallyoutput by that system to be unreliable by ceasing tosupply the affected word or words to the data bus.

2. Bit nos. 30 and 31 of BCD numeric data words shouldbe “zero” when no sign is needed.

3. The “no computed data” code should be generated forBCD numeric data words when computed data is notavailable for reasons other than equipment failure.

4. When it appears in a BCD numeric data wordidentified by its (label) as a system output, the“functional test” code should be interpreted as advicethat the data in the word results from the execution ofa functional test. When it appears in a BCD numericdata word identified by its label as an instruction, e.g.,a radio channel change command, this code should beinterpreted as a command to perform a functional test.A self-test should produce indications of 1/8 ofpositive full-scale values unless indicated otherwise inan ARINC Equipment Characteristic.

5. See Section 2.3.1.3 of this document for definitions ofthe terms “Initial Word”, “Control Word”,“Intermediate Word” and “Final Word.”


Table modified to permit sign coding for “no computeddata”.

Definition of “failure warning” and “no computed data”added.



The sign (plus, minus, north, south, etc.) of BNR numericdata words and the status of the transmitter hardwareshould be encoded in bit nos. 29, 30 and 31 of the word asshown in the table below.

Bit No.31 30 29

DesignationBNR Data

0 0 0 Failure Warning/Plus, North, EastRight, To

0 0 1 Failure Warning/Minus, South, WestLeft, From

0 1 0 No Computed Data

1 0 0 Functional Test/Plus, North, East,Right, To

1 0 1 Functional Test/Minus, South, WestLeft, From

1 1 0 Normal Operation/Plus, North, East,Right, To

1 1 1 Normal Operation/Minus, SouthWest, Left, From

0 1 1 Not Used (Growth)

Notes:

1. A source system should annunciate any detectedfailure that causes one or more of the words normallyoutput by that system to be unreliable by setting bitnos. 30 and 31 in the affected word(s) to the “failurewarning” code defined above. Words containing thiscode should continue to be supplied to the data busduring the failure condition.

2. Bit no. 29 should be “zero” when no sign is needed.

3. The “no computed data” code should be generatedwhen computed data is not available for reasons otherthan equipment failure.

4. When it appears in a word identified by its label as asystem output, the “functional test” code should beinterpreted as advice that the data in the word resultsfrom the execution of a functional test. A self-testshould produce indications of 1/8 of positive full-scalevalues unless indicated otherwise in an ARINCEquipment Characteristic.

5. If, during the execution of a functional test, a sourcesystem detects a failure which causes one or more ofthe words normally output by that system to beunreliable, it should immediately change the states ofbits nos. 30 and 31 in the annunciation to the “failurewarning” annunciation.


2.1.5.3 STATUS PRIORITIES

New section inserted.

2.2.1 TRANSMISSION SYSTEM INTERCONNECT

Commentary expanded to provide description of possiblesolutions to single-wire fault conditions.



A data source should be connected to the data sink(s) bymeans of a single twisted and shielded pair of wires. Theshields should be grounded at both ends and at allproduction breaks in the cable. The interwiring diagram tobe found in each ARINC Equipment Characteristic showsconnector pins assigned to carry shields into black boxesfor grounding. Equipment manufacturers should ensure,however, that their equipment will operate correctly if,instead of being terminated on these pins, shields aregrounded in the aircraft close to the rack connector.

COMMENTARY

In practical wire line digital information transmissionsystems, cable characteristics and electricalmismatches can produce distortion of the digital datapulses. Also, noise due to electrical interferenceperturbs digital signals.

The performance of a digital receiver depends uponthe receiver input signal characteristics (data withdistortion and noise) and the receiver design.

Prior to the selection of the voltage and impedanceparameters set forth in this Section of this document,the pulse distortion likely to be encountered in systemsbuilt around them in existing size commercial aircraftwas evaluated and judged to be acceptable for a well-designed receiver. No restriction is placed by thisspecification, therefore, on the number or length ofsturbs for installations on aircraft no larger than thoseexisting, e.g., B 747. See Appendix 1 to thisdocument for a report of this investigation.

2.2.3.1 TRANSMITTER VOLTAGE LEVELS

Text changed to improve clarity.


2.2.3.1 Transmitter Voltage Levels

The differential output signal across the specified outputterminals (balanced to ground at the transmitter) should be+ 10 ± 1.0 volts, 0 ± 0.5 volts and –10 ± 1.0 voltsrespectively for the “HI”, “NULL” and “LO” states whenthe transmitter is open circuit. The output impedance ofthe transmitter should be as specified in Section 2.2.4.1 ofthis document. This output impedance should be presentfor the “HI”, “NULL” and “LO” transmitter outputconditions and also during transitions between these levels.

2.2.3.2 RECEIVER VOLTAGE LEVELS

Receiver voltage thresholds changed.

Fault voltage text deleted.

Commentary revised to include description of receiverreaction to undefined voltages.



The differential voltage presented at the receiver inputterminals will be dependent upon line length, stubconfiguration and the number of receivers connected. Inthe absence of noise, the normal ranges of voltagespresented to the receiver terminals (A and B) would be:

“HI” +6V to 10V“NULL” +0.5 to –0.5V“LO” -6V to –10V

In practice, these nominal voltages will be perturbed bynoise and pulse distortion. Thus, receivers shouldassociate the following voltage ranges with the three statesindicated:

“HI” +5V to 13V“NULL” +2.5V to –2.5V“LO” -5V to –13V

Receivers should not be damaged by the application of upto 20VAC (RMS) across terminals A and B by theapplication of up to +28VDC (min) bias between terminalA and ground and –28VDC (min) bias between terminal Band ground. See Attachment 3 to this document for apictorial representation of transmitter and receiver voltagelevels.

COMMENTARY

Receiver input common mode voltages (terminal A toground and terminal B to ground) are not specifiedbecause of the difficulties of defining ground with anysatisfactory degree of precision. Receivermanufacturers are encouraged to work with thedifferential input voltage (line A to line B) and notline-to-ground voltages.

The opinion is held by some people that conditions ontransmission lines will be encountered which willrequire receivers to operate with less than the above-defined minimum difference of 2.5V between theNULL and HI and NULL and LO states. Receiverdesigners are encouraged to investigate thepossibilities and problems of working with a minimumdifference of 1 volt between these states and to reporttheir findings.

2.2.4.1 TRANSMITTER OUTPUT IMPEDANCE

Text added to improve clarity.



2.2.4.1 Transmitter Output Impedance

The transmitter output impedance should be 75 ± 5 ohms,divided equally between line A and line B to provide animpedance balanced output.

COMMENTARY

The output impedance of the transmitter is specified as75 ± 5 ohms to provide an approximate match to thecharacteristic impedance of the cable. The match canonly be approximate due to the wide range ofcharacteristic impedance which may be encountereddue to the variety of conductor wire gages andinsulation properties. Measurements on a few samplesof wire showed a spread of characteristic impedanceof 63 and 71 ohms. An extrapolation over the wiregages 20 to 26 for wrapped and extruded insulationindicate an expected characteristic impedance spreadof 80 to 60 ohms approx. Twisted shielded wirespecifications do not control the characteristicimpedance of the cable, thus future developments ininsulation techniques may result in cables havingcharacteristic impedances outside the range estimated.

2.2.4.2 RECEIVER INPUT IMPEDANCE

Value of RI changed.



The receiver should exhibit the following characteristics,measured at the receiver input terminals:

Differential Input Resistance RI = 6,000 ohms minimum

Differential Input Capacitance CI = 50pF maximumResistance to Ground RH and RG ≥ 12,000 ohmsCapacitance to Ground CH and CG ≤ 50pF.

No more than twenty receivers should be connected on toone digital data bus and each receiver should incorporateisolation provisions to ensure that the occurrence of anyreasonably probable failure does not cause loss of data tothe others.

See Attachment 4 to this document for a pictorialrepresentation of the input and output circuits standards.

COMMENTARY

The above characteristics apply to differentialamplifier receivers. Opto-isolator technology isprogressing and may soon find application in digitaldata receivers. Opto-isolator receivers imposeslightly greater loads on data buses than differentialamplifier receivers and the way in which they arecharacterized is different. It is probable, however, thata future revision of this Specification will includematerial specifically related to their use.

2.2.5 Fault Tolerance


2.2.5.1 Receiver External Fault voltage Tolerance


2.2.5.2 Transmitter External Fault Voltage Tolerance


2.2.5.3 Transmitter External Fault Load Tolerance


2.2.6 Fault Isolation


2.2.6.1 Receiver Fault Isolation


2.2.6.2 Transmitter Fault Isolation


2.3.1.2 Discretes

Text modified to expand label examples.

Reference to AIDS limitations deleted.


2.3.1.2 Discretes

In addition to handling numeric data as specified above,the Mark 33 DITS should also be capable ofaccommodating discrete items of information either in theunused (pad) bits of data words or, when necessary, indedicated words. Any discrete information contained in anumeric data word assigned a label in Attachment 1 isspecified in the definition for that word in Attachment 2.

The rule to be followed in the assignments of bits todiscretes in numeric data words is to start with the leastsignificant bit of the word and to continue towards themost significant bit available in the word. Attachment 6shows that this against the background of the generalizedword structure.

There are two types of discrete words. These are generalpurpose discrete words, and dedicated discrete words. Fivelabels (octal 270-274) are assigned to the general purposewords in Attachment 1. These words should be used inascending label order (starting with octal 270) when thesystem receiving the data can identify its source byreference to the port at which it arrives. The dedicatedwords should be used when the


2.3.1.2 Discretes (cont’d)

data is intended for the AIDS DFDAU which cannotidentify sources in this way.

COMMENTARY

The foregoing special provisions for the delivery ofdiscrete data to an AIDS were made to compensate forthe number of digital ports required when many portsare used is extremely difficult to achieve, whichnecessitated the development of the special AIDSwords. These words should be limited to AIDSutilization. The few aircraft systems which deliverdiscretes to an AIDS by means of the Mark 33 DITSwill be burdened very little by this. Similarly, theimpact of label use will be small.

2.3.1.4 AIM DATA

Text added to describe unit addressing.


2.3.1.4 AIMS Data

AIM data (Acknowledgement, ISO Alphabet No. 5 andMaintenance information encoded in dedicated words)should be handled in the manner described in this Section.

All three of these applications may involve the transfer ofmore than 21 bits per “data package”. Source equipmentshould format such long messages into groups of 32-bitDITS words, each word containing the relevant applicationlabel (see Attachment 1) in bit nos. 1 through 8, and asign/status matrix code in bit nos. 30 and 31.

Bit no. 32 should be encoded to render word parity odd.The first word of each group should contain the sign/statusmatrix code defined for “initial word” in Section 2.1.5.1 ofthis document. It should also contain, in bit nos. 9 through16, the binary representation of the number of words in thegroup, except that when this word is the only word to betransmitted, i.e., the total number of information bits to betransmitted is 13 or less, bit nos. 9 through 16 should all bebinary “zeros”.

When the word application label is assigned in Attachment1 for Acknowledgement Data, bit nos. 17 through 29 ofthis initial word may be used for information transfer.When the word application label is either of those assignedin Attachment 1 for ISO Alphabet No. 5 data transfer orMaintenance Data (ISO Alphabet Not. 5), bit nos. 17through 22 should be binary “zeros” (spares) and bit nos.23 through 29 should take on the pattern of the ISOAlphabet No. 5 control character “STX”.

The second word of the ISO Alphabet No. 5 andMaintenance Data (ISO Alphabet No. 5) applicationgroups is an optional control word containing thesign/status matrix code for “control” information for thedisplay. When it is used, bit nos. 9 through 13 shouldcontain the binary representation of the line count, bit nos.14 through 16 should encode the required color, bit nos. 17and 18 the required intensity, bit nos. 19 and 20 therequired character size and bit no. 21 should indicatewhether or not the display is required to flash. SeeAttachment 6 to this document for the encoding standards.

Bit nos. 22 through 29 of the word should be binary “zero”(spares).

Intermediate words, containing the sign/status matrix codefor “intermediate word”, follow the initial word of thegroup or the control word, when used. Intermediate wordsare optional in the sense that they are only transmitted ifmore words than the initial word and the final word (seebelow) are needed to accommodate the quantity ofinformation to be transferred. When the word applicationgroup label that is assigned in Attachment 1 forAcknowledgement, Data bit nos. 9 through 29 of that wordare available for information transfer. When the wordapplication label is either of those assigned in Attachment1 for ISO Alphabet No. 5 data transfer or MaintenanceData (ISO Alphabet No. 5), bit nos. 9 through 29 of eachword should be divided into three seven-bit bytes (bit nos.9 through 15, 16 through 22 and 23 through 29), each ofwhich contains one ISO Alphabet No. 5 character.

Each AIM application group transmission other thansingle-word transmissions (see below) should beterminated with a word containing the sign/status matrixcode for “final word” defined in Section 2.1.5.1 of thisdocument. The data field of this word should be structuredsimilarly to that of the intermediate word. Any unused bitpositions in ISO Alphabet No. 5) final transfer orMaintenance Data (ISO Alphabet No. 5) final wordsresulting from the number of ISO Alphabet No. 5characters in the message being one or two less than anumber wholly divisible by three should be filled withbinary “zeros”.

2.3.1.5.1 COMMAND/RESPONSE PROTOCOL

Text modified to describe transmitter reaction to lack of“Clear to send”.


2.3.1.5.1Command/Response Protocol

File data will consist of both ARINC 429 BNR numericwords and ISO alphabet No. 5 characters. A file maycontain from 1 to 127 records. Each record may containfrom 1 to 126 data words.

A record will contain, at the minimum, one of the eightversions of the “initial word” described in Section2.3.1.5.2. Records in which this initial word contains the“Data Follows” code will also contain from 1 to 126“intermediate words” (data) and a “final word” (errorcontrol). The file data transfer protocol is as follows. Atransmitter having the data to send to a receiver transmits,on the bus connecting it to that receiver, the “Request toSend” initial word. The receiver responds, on the separatebus provided for return data flow, with the “Clear to Send”reply. The transmitter then sends the “Data Follows”initial word, the “intermediate words” and the “finalword”. The receiver processes the error controlinformation in the “final word” and, if no errors arerevealed, closes out the transaction by sending the “DataReceived OK” word to the transmitter.

If the receiver is not ready to accept data when thetransmitter sends its “Request to Send” word, it will so


indicate in its response (see Section 2.3.1.5.2). Thetransmitter should then wait 200 milliseconds andretransmit the “Request to Send”. The transmitter shouldalso repeat a “Request to Send” transmission 50milliseconds after the initial transmission if no response isobtained from the receiver. An alert should be raised in thesystem containing the transmitter if 4 attempts to obtain a“Clear to Send” response from a receiver are unsuccessful.

If the receiver detects a parity error during thetransmission, it may request an error-correctingretransmission by sending a “Data Received Not OK”word to the transmitter in which is identified the record inwhich the error occurred. The transmitter will interrupt thedata flow and back up to the start of the record soidentified. It will then send a “Data Follows” initial wordidentifying this record as the starting point of theretransmission and recommence its output of data,continuing through the “final word”. The receiver willthen close out the transaction as before.

An error detected by processing the error controlinformation in the “final word” will also result in thereceiver sending a “Data Received Not OK” word to thetransmitter. In the absence of identification of the recordin which the error occurred, this word should contain thesequence number of the first record of the file. Thetransmitter’s response will be to retransmit the whole file.

The receiver can signal loss of synchronization to thetransmitter at any time by sending the“Synchronization Lost” initial word. On receiving thisword the transmitter should curtail the data flow and backup to the beginning of the file. It should then re-establishthat the receiver can accept data by going through therequest-to-send/clear-to-send routine. Having done this itshould send the “Data Follows” initial word, followed bythe data and the “final word”.

The protocol also allows a transmitter to send file sizeinformation to a receiver without any commitment to send,or request to the receiver to accept, the file itself. The“Header Information” initial word is used for this purpose.Additionally, a “Poll” initial word is defined for use insystem in which continuous “handshaking” between twoterminals is desired. The response to a “Poll” word will beeither a “Request to Send” initial word when the polledterminal does have data to transmit, or another “Poll” wordwhen it does not. An exchange of “Poll” words may beinterpreted as the message, “ I have nothing for you, doyou have anything for me?”

2.4.2 INFORMATION RATES

Commentary added to describe refresh rate.



The minimum update interval for each item of informationtransferred by the Mark 33 DITS is specified in the tablesof Attachment 2.

Discretes contained within data words will be transferred atthe bit rate and repeated at the update rate of the primarydata. Words dedicated to discretes should be repeatedcontinuously at the rates defined in Attachment 2.

COMMENTARY

The time intervals between successive transmissionsof a given BCD word specified in table 1 ofAttachment 2 to this document are, in general, tooshort for the signal to be of use in driving a displaydevice directly. If the signal was so used, the leastsignificant character of the display would change toorapidly for human perception. Considerations otherthan human factors demand the time intervalsspecified. Thus, display designers should incorporateinto their devices means for selecting those words tobe used for updating the display from the greaterquantity delivered.

3.1.4.2 DME

Encoding and switch functions modified.


3.1.4.2 DME

Frequency Range: 108.00MHz to 135.95MHzFrequency Selection: 50kHz

Increment:Characters encoded10MHz, 1MHz, 0.1MHz,

In DITS word: 0.01MHz, (100MHzCharacter is always

Decimal 1)Switching Functions:Standby, DME Mode

Select ILS Mode


FIGURE 3-1 Radio Systems Management Word Formats

HF and DME words modified.

ORIGINAL TEXT FOLLOWS:PA

RIT

Y (

odd)

SIG

N/S

TA

TU

SM

AT

RIX

10M

Hz

(

1)

1MH

z

(1)

0.1M

Hz

(

5)

0.01

MH

z

(0)

ILS

Mod

e

Stan

dby

DM

E M

ode

Sele

ct

RE

SER

VE

D

(SD

I)

LABELDME Frequency

DME

Function

Bit No.

ExampleNotes

32 1

31 30 0 0

29 28 27 26 25 24 23 22 21 20 19 1 8 17 16 15 0 0 1 0 0 0 1 0 1 0 1 0 0 0 0

14 0

[1]

13 0

[2]

12 11 0 0

[3]

10 9 0 0

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

[1] Bit no. 14 should be set to “zero” for VOR frequencies and “one” for ILS frequencies bythe tuning information source.

[2] [3]Bit Zero One

1112

DME Mode select coding perSection 4.1.6 of ARINC Char. 709

13 Standby off Standby on

PAR

ITY

(od

d)

SIG

N/S

TA

TU

SM

AT

RIX

10M

Hz

(

2)

1MH

z

(3)

0.1M

Hz

(

5)

0.01

MH

z

(7)

0.00

1MH

z

(9

)

USB

/LSB

Mod

e

SSB

/AM

Mod

eW

ord

Iden

tifi

er LABELHF COM Frequency

HF COMWord #1

Function

Bit No.ExampleNotes

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

11 0[1]

10 9 0 0[2] [3]

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

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

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

[3] Bit no. 9 should be set to “zero” when the 100 Hz option is not used and “one” when it is.

PAR

ITY

(od

d)

SIG

N/S

TA

TU

SM

AT

RIX

.1K

hz

(5)

NOT USED LABELHF COM Frequency

HF COMWord #2

Function

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 0

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

Note: The HF COMM #2 word is used only when bit no. 9 of word #1 is “one”.



Column “EQPT. ID (HEX)” has been added for five-character label implementation.

Table containing “Equipment ID Codes” added.


004, 034, 056, 060-064, 070-106, 111, 114-122, 126,127, 135, 136, 140-141, 144-162, 173-177, 202-212,215, 217, 222-226, 242, 244-252, 256-265, 276, 310-322, 340-342, 344, 345, 347, 350, 370, 377.

Label 226 (FWC #2) deleted.

Labels 124 and 224 (C&W DFDR Discretes) deleted.


The columns for “bandwidth”, “noise level” and“update interval” have been deleted. A column for“minimum transmit interval” has been added. Thecolumn for “transport delay” has been changed to“maximum transport delay”. A column for “EQPT.ID(HEX)” has been added.

Data standards added for new labels.

Note [2]: A nominal interval description has beenadded.

Note [3]: A definition for “maximum transport delay”has been added.

Note [4]: SDI assignments defined for labels 060-064.

The following tables list the parameters for which thedata standards have changed. An asterisk beside aparticular value designates that a new value issuggested.

TABLE 1 BCD DATA

LABEL(OCTAL)

PARAMETERNAMES UNITS RANGE

(SCALE)SIG.DIG.

POSITIVESENSE RESOL.

MAXIMUMTRANSMITINTERVAL

010 Present Position – Lat. Deg:Min 90S-90N* 5* 0.1 500017 Selected Runway Heading Deg 0-359.9 4 0.1 200*024 Selected Course #1 Deg 0-359 3 1.0 200*027 Selected Course #2 Deg 0-359 3 200*033 ILS Frequency 200*034 VOR/ILS Frequency 200*041 Set Latitude Deg:Min 90S-90N* 5* N 0.1 500065 Gross Weight 100lb. 0-10000* 5 1.0 200067 Lateral CG Mlb-in.* ± 100.00* 4* 0.1* 200200 Drift Angle Deg ± 90* 3* 0.1 200231 Total Air Temperature oC -60-+90* 2* 1.0 500232 Altitude Rate Ft/Min ± 20,000 4 Up 20.0* 62.5233 Static Air Temperature oC -99-+60* 2* 1.0 500

TABLE 2 BNR DATA

LABEL(OCTAL)

PARAMETERNAME UNITS RANGE SIG.

BITSPOSITIVE

SENSEAPPROX.RESOL.

MAXIMUMTRNASMITINTERVAL

077 Lateral CG MLB/in ± 128* 14* 0.001 200100 Selected Course #1 Deg/180 ± 180o 12 0.05 o 50*105 Selected Runway Heading Deg/180 ± 180o 11 0.05 o 62.5*110 Selected course #2 Deg/180 ± 180o 12 0.05 o 50*173 Localizer Deviation DDM ± 0.4 12 0.0001 62.5*174 Glideslope Deviation DDM ± 0.8 12 0.0002 62.5*222 VOR Omnibearing Deg/180 ± 180o 12 0.044 o 62.5*256 Fuel Quantity #1 Lbs. 131,072 15 4 200*257 Fuel Quantity #2 Lbs. 131,072 15 4 200*310 Present Position – Lat. Deg/180 0-90N-0-90S* 20 .000086 o* 200



ORIGINAL TEX FOLLOWS:

[2] Transmit intervals and the number ofparameters to be transmitted are prime factorsin bus loading. It was suggested that aMinimum Transmit Interval be specified(perhaps a value of ½ the Transmit Interval) tocontrol bus loading. The ability of receivers toreject unwanted words would also be effectivein improving bus efficiency.

Table 3.2 FCC DISCRETES – LABELS 270, 271

Existing tables replaced by new set of tables.


Table 3.2: FCC Discretes – Labels 270, 271

Discrete Word #1

Bit StatusBit No. Function

1 01 X2 X3 X4 Label X5 X6 X7 X8 X9* Capt. Flight Director On Off

10* F. O. Flight Director On Off11 Turbulence Mode Requested Not Requested12 Autopilot #1 Engaged Not Engaged13 Autopilot #2 Engaged Not Engaged14 RESERVED (A/P #3) Engaged Not engaged15 Autothrottle #1 Armed Not Armed16 RESERVED (A/T #2) Armed Not Armed17 Airspeed Hold Mode Requested Not Requested18 Airspeed Select Mode Requested Not Requested19 Mach Select Mode Requested Not Requested20 Mach Hold Mode Requested Not Requested2122 Bank Angle Limit See Below2324 Heading Select Mode Requested Not Requested25 N1/EPR Select Mode Requested Not Requested26 IAS on Throttle Requested Not Requested27 Mach on Throttle Requested Not Requested28 Spare29 Spare30 Sign/Status31 Matrix32 Parity (Odd)



Bank Angle Limit Encoding

Bit nos. 21, 22 and 23 of Discrete Word #1 should beencoded to indicate selected bank angle limit as follows:

*Bits 9 and 10, which are normally used for the SDI,have purposely been used for Discrete information.

Bit No.Limit 21 22 23Not used 0 0 0 5o 0 0 1 10 o 0 1 0 15 o 0 1 1 20 o 1 0 0 25 o 1 0 1 30 o 1 1 0Spare 1 1 1

Discrete Word #2


1 01 X2 X3 X4 Label X5 X6 X7 X8 X9* Altitude Hold Mode Requested Not Requested

10* Altitude Select Mode Requested Not Requested11 Vertical Speed Select Mode Requested Not Requested12 Vertical Speed Hold Mode Requested Not Requested13 Horizontal Navigation Requested Not Requested14 Vertical Navigation Requested Not Requested15 Land Command Requested Not Requested16 LOC Approach Command Requested Not Requested17 Back Course Approach Command Requested Not Requested18 CWS #1 Requested Not Requested19 CWS #2 Requested Not Requested20 CWS #3 Requested Not Requested21 Pitch Upper Mode Cancel Requested Not Requested22 Roll Upper Mode Cancel Requested Not Requested23 Heading Hold Requested Not Requested242526 Spare27282930 Sign/Status31 Matrix32 Parity (odd)

* Bits 9 and 10, which are normally used for the SDI, have purposely been used for Discrete information.


TABLE 3.7 GPWS DISCRETE LABEL 270 23

Visual message bit assignments inserted.

TABLE 3.8 TCC DISCRETES LABELS 272 03, 27303, 274 03, 275 03

New tables inserted.

ATTACHMENT 3: VOLTAGE LEVELS

Hi and Lo thresholds changed from 5-13 volts to 6.5-13volts.

ATTACHMENT 4: INPUT/OUTPUT CIRCUITSTANDARDS

RI increased from 6,000 to 12,000 ohms.

Total system resistance range of 300-6000 ohmschanged to 400-8000 ohms.

ATTACHMENT 6: GENERAL WORD FORMATSAND ENCODING EXAMPLES

Format for alphanumeric message initial word modified.

Slat/Flap angle word added.

GMT binary word added.

Label Fields changed in discrete word and maintenance(discrete) word.

In table 6-1b note [1] deleted and bits 21 and 22 oflatitude word interchanged.

In Table 6-2 examples corrected for Present Position(Latitude and Longitude).

Radio Height word added.

ORIGINAL TEXT FOLLOW:

P32

SSM31 (01) 30

“STX”29 23

SPARES22 (Zeros) 17

WORD COUNT16 BNR EQUIV. 9

LABEL8 (356/357) 1

ALPHA NUMERIC (ISO ALPHABET NO. 5) DATA – INITIAL WORD FORMAT

P

32

SSM

31 (00) 30DISCRETES

29 MSB 2 LSB 11

SDI

10 9

LABEL

8 (270-274) 1

DISCRETE WORD FORMAT

P

32

SSM

31 (00) 30

MAINTENANCE DISCRETESDISCRETES

29 MSB LSB 11

SDI

10 9

LABEL

8 (350-354) 1

MAINTENANCE (DISCRETE) WORD FORMAT

APPENDIX 3: DIGITAL SYSTEMS GUIDANCE(PART 1)

Appendix added.

APPENDIX 4: DIGITAL SYSTEM GUIDANCE(PART 2)

Appendix added.



SUPPLEMENT 5

TO



Published: April 4 1981


Adopted by the Airlines Electronic Engineering Committee: March 12, 1981

SUPPLEMENT 5 TO ARINC SPECIFICATION 429 – Page 2


This Supplement introduces material on fault detection,transmit intervals for words using multiple SDI codes,modification of IRS/AHRS discrete formats, expansionof error control definition, revision of ILS word,addition of new labels and change of existing datastandards.


The first part of this document, printed on goldenrodpaper, contains descriptions of the changes introducedinto the Specification by this Supplement, and, whereappropriate, extracts from the original text forcomparison purposes. The second part consists ofreplacement white pages for the Specification, modifiedto reflect these changes. The modified and addedmaterial on each replacement page is identified with “c-5” symbols in the margins. Existing copies ofSpecification 429 may be updated by simply insertingthe replacement white pages where necessary anddestroying the pages they replace. The goldenrod pagesshould be inserted inside the rear cover of theSpecification.



This section presents a complete tabulation of thechanges and additions to the Specification introducedby this Supplement. Each change or addition is entitledby the section number and title currently employed inthe Specification, or by the section number and title thatwill be employed when the Supplement is eventuallyincorporated. In each case there is included a briefdescription of the addition or change and, for other thanvery minor revisions, any text originally contained inthe Specification is reproduced for reference.

2.2.1 TRANSMISSION SYSTEM INTERCONNECT

Text revised for break connections.

Text added to Commentary describing increase ofvoltage threshold.



A data source should be connected to the data sink(s)by means of a single twisted and shielded pair of wires.The shields should be grounded at both ends and at allproduction breaks in the cable to an aircraft groundclose to the rack connector.

COMMENTARY

In practical wire line digital informationtransmission systems, cable characteristics andelectrical mismatches can produce distortion of thedigital data pulses. Also, noise due to electricalinterference perturbs digital signals. The

performance of a digital receiver depends upon thereceiver input signal characteristics (data withdistortion and noise) and the receiver design.

Prior to the selection of the voltage and impedanceparameters set forth in this Section of thisdocument, the pulse distortion likely to beencountered in systems built around them inexisting size commercial aircraft was evaluated andjudged to be acceptable for a well-designedreceiver. No restriction is placed by thisspecification, therefore, on the number or length ofstubs for installations on aircraft no larger thanthose existing, e.g., B 747. See Appendix 1 to thisdocument for a report of this investigation.

Tests have shown that some receivers continuedecoding data properly when one side of thetransmission line is open or shorted to ground.When this condition exists noise immunitydecreases and intermittent operation may occur.Users desire protection against non-annunciatedsystem operation in this mode. This protectionmay consist of additional circuitry to detect andannunciate the fault.

2.2.3.2 RECEIVER VOLTAGE LEVELS

Normal voltage ranges changed due to impedancechanges.



The differential voltage presented at the receiver inputterminals will be dependent upon line length, stubconfiguration and the number of receivers connected.In the absence of noise, the normal ranges of voltagespresented to the receiver terminals (A and B) would be:

“HI” +6.5V to 10V“NULL” +2.5V to –2.5V“LO” -6.5V to –13V

In practice, these nominal voltages will be perturbed bynoise and pulse distortion. Thus, receivers shouldassociate the following voltage ranges with the threestates indicated:

“HI” +6.5V to 13V“NULL” +2.5V to –2.5V“LO” -6.5V to –13V

COMMENTARY

Receiver reaction is currently undefined inSpecification 429 for voltages that fall in the rangejust above and below the “NULL” range.Respective equipment Characteristics should bereferenced for desired receiver response in thisrange. However, it is desirable that all DITSreceivers will discontinue operation when thevoltage levels fall into the undefined regions.Manufacturers are urged, as new equipment isdeveloped, to “design in” the rejection capability.

The opinion is held by some people that conditionson transmission lines will be encountered whichwill require receivers to operate with less than the


above-defined minimum difference of 4.0Vbetween the NULL and HI and NULL and LOstates. Receiver designers are encouraged toinvestigate the possibilities and problems ofworking with a minimum difference of 1 voltbetween these states and to report their findings.

Receiver input common mode voltages (terminal Ato ground and terminal B to ground) are notspecified because of the difficulties of definingground with any satisfactory degree of precision.Receiver manufacturers are encouraged to workwith the differential input voltage (line A to line B)and not line-to-ground voltages.

2.3.1.5.4 FINAL WORDS

Text added to define checksum.


2.3.1.5.4 Final Words

The final word of each record contains error controlinformation. Bit nos. 1 through 8 contain the file label.Bit nos. 9 through 29 contain an error control checksumcomputed from the states of bit nos. 9 through 31 ofeach intermediate word of the record. Bit nos. 30 and31 of this word contain the code identifying it as a finalword. Bit no. 32 is encoded to render word parity odd.

2.3.4 ERROR DETECTION/CORRECTION

Obsolete text deleted.

ORIGIANL TEXT FOLLOWS:

2.3.4 Error Detection/Correction

The last bit of each word should be encoded such thatword parity is rendered odd to allow error detection inreceivers. Note that the parity calculation encompassesall 31 label and information bits of the word. The Mark33 DITS contains no provisions for messageretransmission, the inclusion of redundant bits in wordsor other means of error correction.

Fig. 3-1: RADIO SYSTEMS MANAGEMENT WORDFORMATS

Bits 3 and 7 of transponder word changed to “0”.(editorial)

Bit 11 and 12 assigned to ILS category designation.

Control Panel Function Matrix added to transponderword.

ORIGINAL MATERIAL ON NEXT PAGE:

2.4.2 INFORMATION RATES

Text added to describe transmission of labels withmultiple SDI codes.



The minimum and maximum transmit intervals for eachitem of information transferred by the Mark 33 DITSare specified in the tables of Attachment 2.

COMMENTARY

There are no values given for refresh rates in thisSpecification. However, it is desirable that data berefreshed at least once per transmission. Thosedata actually requiring long processing times or alarge number of samples are the only types notexpected to be refreshed with every transmission.

Discretes contained within data words should betransferred at the bit rate and repeated at the update rateof the primary data. Words dedicated to discretesshould be repeated continuously at the rates defined inAttachment 2.

COMMENTARY

The time intervals between successivetransmissions of a given BCD word specified intable 1 of Attachment 2 to this document are, ingeneral, too short for the signal to be of use indriving a display device directly. If the signal wasso used, the least significant character of thedisplay would change too rapidly for humanperception. Considerations other than humanfactors demand the time intervals specified. Thus,display designers should incorporate into theirdevices means for selecting those words to be usedfor updating the display from the greater quantitydelivered.


Fig. 3-1: RADIO SYSTEMS MANAGEMENT WORD FORMATS (cont’d)

PAR

ITY

(od

d)

SIG

N/S

TA

TU

SM

AT

RIX

10M

Hz

(

0)

1MH

z

(9)

0.1M

Hz

(

3)

0.01

MH

z

(0)

SPA

RE

SPA

RE

SPA

RE

SPA

RE

RE

SER

VE

D

(SD

I)

LABELILS Frequency

ILS

Function

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

13 0

12 0

11 0

10 9 0 0

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



073 02, 073 A2, 112 02, 130 1A, 131 2D, 132 1A, 1331A, 151 02, 154 02, 164 02, 164 03, 174 03, 205 1A, 2070A, 211 1A, 215 1A, 242 1A, 245 0A, 256 0A, 260 31,262 0A, 263 0A, 264 0A, 265 0A, 270 1A, 270 1E, 27030, 271 06, 271 1A, 271 1E, 272 1A, 274 0A, 275 2B,300 1A, 301 1A, 303 1A, 304 1A, 305 1A, 306 1A, 3071A, 325 1A, 340 1A, 340 2D, 341 1A, 342 1A, 344 1A,345 1A, 346 1A, 350 1A, 351 1A, 352 1A, 353 1A, 3541A.

Label 242** was deleted.

Label 316 04 changed form “Wind Angle” to “WindDirection (True)”.

ATTACHMENT 1: EQUIPMENT CODES

New assignments were made for 0A and 2D.

Note added to 1A.


ATTACHEMENT 2: DATA STANDARDS

Data standards were added for new labels.

The following table lists the parameters for which theexisting data standards have changed. An asterisk besidea particular value designates that a new value issuggested.

LABELEQPTID(HEX)

PARAMETERNAME UNITS RANGE

SIG.DIG/BITS

POS.SENSE RESOL

MIN.TR.INT.

MAX.TR.INT.

004 01 Runway Distance to Go Feet 0-79900 3 100.0 200* 400*165 07 Radio Height Feet ± 0-7999.9 5 0.1 100* 200*205 06 Mach mMach* 4096* 13* 0.5* 62.5 125210 06 True Airspeed Knots 2048* 13* 0.25* 62.5 125215 06 Impact Pressure mb 512* 9* 1.0* 62.5 125242 06 Total Pressure mb 2045* 11* 1.0* 62.5 125313 04 Track Angle True Deg/180 ± 180o 12* 0.05 o 25 50314 04 True Heading Deg/180 ± 180 o 12* 0.05 o 25 50317 04 Track Angle Magnetic Deg/180 ± 180 o 12* 0.05 o 25 50317 05 Track Angle Magnetic Deg/180 ± 180 o 12* 0.05 o 25 50320 04 Magnetic Heading Deg/180 ± 180 o 12* 0.05 o 25 50320 05 Magnetic Heading Deg/180 ± 180 o 12* 0.05 o 25 50323 04 Flight Path Acceleration g 2* 14* 0.0001* 10 20323 05 Flight Path Acceleration g 2* 14* 0.0001* 10 20324 04 Pitch Angle Deg/180 ± 180 o 14 0.01 o 25* 50*324 05 Pitch Angle Deg/180 ± 180 o 14 0.01 o 25* 50*325 04 Roll Angle Deg/180 ± 180 o 14 0.01 o 25* 50*325 05 Roll Angle Deg/180 ± 180 o 14 0.01 o 25* 50*360 04 Potential Vertical Speed Ft/min 16384* 10* 16* 25 50360 05 Potential Vertical Speed Ft/min 16384* 10* 16* 25 50361 04 Altitude (Inertial) Feet 131,072 18* 0.5* 32.25* 62.5*361 05 Altitude (Inertial) Feet 131,072 18 0.5 31.25* 62.5*365 04 Inertial Vert. Vel. (EFI) Ft/min 16384* 10* 16* 20 40365 05 Inertial Vert. Vel. (EFI) Ft/min 16384* 10* 16* 20 40375 05 Along Heading Accel. g 4 12 0.001 25* 50*376 05 Cross Heading Accel. g 4 12 0.001 25* 50*

Note [2]: Guidance added for transmission intervals oflabels with multiple SDI codes.


[2] Transmit intervals and the number of parametersto be transmitted are prime factors in busloading. The interval for transmission ofparameters should fall between the minimumand maximum specified intervals and nominallyshould be near the center of the range at equalintervals between transmissions. When heavybus loading dictates a shift from the center of therange, the shift should be toward the maximumtransmit interval.

TABLE 3.1: INTERVAL DISCRETES – LABEL 270

Discrete word formats revised.



Table 3.1: Inertial Discretes – Label 270

Notes: [1] Attitude invalid is equivalent to IRS failure.[2] Bit 14 “1” condition indicates that the

“Magnetic Heading” outputs are no longerbeing computer and have thecharacteristics of a “free DG” which issubject to control by a “Set Heading” inputto the IRU. (See Section 3.2.4 for furtherexplanation).


TABLE 3.4: AIR DATA DISCRETES

Discrete word #1 format changed.

Discrete word #2 added.


Table 3.4: Air Data Discretes – Label 270

ATTACHMENT 6 – GENERAL WORD FORMATS AND ENCODING EXAMPLES

Examples revised to agree with adopted data standards changes. (editorial)



SUPPLEMENT 6

TO



Published: January 22, 1982


Adopted by the Airlines Electronic Engineering Committee: December 9, 1981



This Supplement introduces the assignment of octallabels and hexadecimal equipment identifiers, theaddition of guidance for label selection, a revision offailure warning annunciation in discrete words, deletionof the weight & balance words, editorial revisions tothe label tables and addition of EEC discrete wordformats.


The first part of this document, printed on goldenrodpaper, contains descriptions of the changes introducedinto the Specification by this Supplement, and, whereappropriate, extracts from the original text forcomparison purposes. The second part consists ofreplacement white pages for the Specification, modifiedto reflect these changes. The modified and addedmaterial on each replacement page is identified with “c-6” symbols in the margins. Existing copies ofSpecification 429 may be updated by simply insertingthe replacement white pages they replace. Thegoldenrod pages should be inserted inside the rearcover of the Specification.




2.1.5.1 BCD, NUMERIC, DISCRETE, AIM DATAAND FILE TRANSFER WORDS

Commentary revised to reflect use of failure warningflags in discrete words.


COMMENTARY

Definitions

Invalid Data – is defined as any data generated by asource system whose fundamental characteristic isthe inability to convey reliable information for theproper performance of a user system. There aretwo categories of invalid data namely, “NoComputed Data” and “Failure Warning”.

No Computes Data – is a particular case of datainvalidity where the source system is unable tocompute reliable data for reasons other than systemfailure. This inability to compute reliable data iscaused exclusively be a definite set of events or

conditions whose boundaries are uniquely definedin the system characteristic. When such acondition exists, the source system shouldannunciate its outputs to be invalid by setting thesign/status matrix of the affected words to the“NCD” code, as defined in sections2.1.5.1 and2.1.5.2. The system indicators may or may not beflagged depending on system requirements.

Failure Warning – is a particular case of datainvalidity where the system monitors have detectedone or more failures. These failures are uniquelycharacterized by boundaries defined in the systemcharacteristic. When such a condition exists, thesource system should annunciate its outputs to beinvalid by either ceasing to supply the affectedwords to the data bus (the case of BCD data andILS-LRRA installations with provisions for theinterruption of AFS BNR data – see ARINCcharacteristics 707 and 710) or by setting thesign/status matrix of the affected words to the“Failure Warning” code (BNR case), as defined insections 2.1.5.1 and 2.1.5.2. The system indicatorsshould always be flagged during a “FailureWarning” condition.


Commentary for failure warning revised.


COMMENTARY

Definitions

Invalid Data – is defined as any data generated by asource system whose fundamental characteristic isthe inability to convey reliable information for theproper performance of a user system. There aretwo categories of invalid data, namely, “NoComputed Data” and “Failure Warning”.

No Computed Data – is a particular case of datainvalidity where the source system is unable tocompute reliable data for reasons other than systemfailure. This inability to compute reliable data iscaused exclusively by a definite set of events orconditions whose boundaries are uniquely definedin the system characteristic. When such acondition exists the source system shouldannunciate its outputs to be invalid by setting thesign/status matrix of the affected words to the“NCD” code, as defined in sections 2.1.5.1 and2.1.5.2. The system indicators may or may not beflagged depending on system requirements.

Failure Warning – is a particular case of datainvalidity where the system monitors have detectedone or more failures. These failures are uniquelycharacterized by boundaries defined in the systemcharacteristic. When such a condition exists, thesource system should annunciate its outputs to beinvalid by either ceasing to supply the affectedwords to the data bus (the case of BCD data andILS-LRRA Installations with provisions for theinterruption of AFS BNR data – see ARINCCharacteristics 707 and 710) or by setting the


sign/status matrix of the affected words to the“Failure Warning” code (BNR case), as defined insections 2.1.5.1 and 2.1.5.2. The system indicatorsshould always be flagged during a“FailureWarning” conditions.

Fig. 3.1 RADIO SYSTEMS MANAGEMENT WORDFORMATS

Assignments for bits 12, 15 and 17 removed from tablefor note 1 of ATC transponder word (editorial).



021 02, 041 02, 042 02, 043 02, 066 02, 071 33, 0722F, 072 33, 074 33, 075 02, 077 02, 114 2F, 115 2F,130 2F, 131 2F, 132 33, 133 2F, 155 33, 156 33, 15733, 160 33, 161 33, 241 2C, 244 33, 250 2B, 252 2F,260 33, 261 33, 262 02, 262 33, 263 33, 264 2F, 26433, 265 33, 267 0A, 267 33, 270 2F, 270 3A, 271 2F,271 3A, 273 2F, 272 2F, 273 33, 274 2F, 274 33, 2752F, 315 02, 340 2F, 341 2F, 342 2F, 344 2F, 344 33,345 2F, 346 2F, 350 2F, 351 2E, 351 2F, 352 2E, 3522F, 353 2F, 354 2F, 375 33, 376 33.

The following labels have been deleted:

060 32, 061 32, 062 32, 063 32, 064 32.

Editorial changes were made to provide for consistencybetween Attachment 1 and Attachment 2.

“Predictive” deleted from 207 0A.

ATTACHMENT 1: EQUIPMENT CODES

New assignments were made for 0D, 2E, 2F, 3A, 3B,33, and 34.

Nomenclature modified for 2C and 32.



Editorial changes made.

Resolutions revised for 315 04, 315 05, 316 04, 321 04,321 05, 322 04, 334 04, and 334 05 to match ARINC704 and 705.

EEC discrete words added.

ATTACHMENT 6: GENERAL WORD FORMATSAND CODING EXAMPLES

Format added for label 262 02.

Bit 12 corrected in DME distance word (editorial).

Example added for GMT binary word.

APPENDIX 5: LABEL SELECTION GUIDANCE

Appendix added.


Annapolis, Maryland 21401 7645 USA

SUPPLEMENT 7

TO





Adopted by the Airlines Electronic Engineering Committee: November 4, 1982



This Supplement introduces new label assignments, datastandards and equipment identification codes, and meansfor transmitting data with reduced accuracy.


The first part of this document, printed on goldenrodpaper, contains descriptions of the changes introducedinto the Specification by this Supplement, and, whereappropriate, extracts from the original text for comparisonpurposes. The second part consists of replacement whitepages for the Specification, modified to reflect thesechanges. The modified and added material on eachreplacement page is identified with “c-7” symbols in themargins. Existing copies of Specification 429 may beupdated by simply inserting the replacement white pagesthey replace. The goldenrod pages should be insertedinside the rear cover of the Specification.



This section presents a complete tabulation of the changesand additions to the Specification introduced by thisSupplement. Each change or addition is entitled by thesection number and title currently employed in theSpecification, or by the section number and title that willbe employed when the Supplement is eventuallyincorporated. In each case there is included and, for otherthan very minor revisions, any text originally contained inthe Specification is reproduced for reference.

2.1.5.1 BCD, NUMERIC, DISCRETE, AIM DATAAND FILE TRANSFER WORDS

Note [6] added.


Note [6] added.

ATTACHMENT 1 – LABEL CODES


046 33, 047 33, 114 3F, 115 3F, 127 33, 130 30, 130 3F,131 30, 131 33, 132 30, 133 3F, 164 3B, 173 3B, 174 3B,175 33, 212 3B, 242 3B, 244 3B, 245 3B, 246 3B, 2473B, 252 3F, 264 3F, 270 30, 270 33, 270 3B, 270 3F, 27130, 271 33, 271 3B, 271 3F, 272 3B, 272 3F, 273 3B, 2733F, 274 3B, 274 3F, 275 3B, 275 3F, 311 3B, 214 3B, 3252F, 325 3F, 340 33, 340 3F, 341 3F, 342 3B, 342 3F, 3443F, 345 3F, 346 33, 346 3F, 347 30, 350 3F, 351 3F, 3523F, 353 3F, 354 3F, 377 30.

The terminology has been modified for the followinglabels:

072 33, 074 33, 132 33, 244 33, 262 33, 263 33, 264 33,265 33.

Station identifiers deleted on engine related parameters.

ATTACHMENT 1 – EQUIPMENT CODES

Code 2F changed from “EEC (Full Authority)” to “FullAuthority EEC-A”.

Code 30 assigned as “Airborne Separation AssuranceSystem”.

Description of Code OD changed to “AIDS DataManagement Unit (DMU)”

Code 3F assigned as “Full Authority EEC_B”.

ATTACHMENT 2 – DATA STANDARDS


Data standards added for the following existing labels:

270 3A, 271 3A, 270 2F-275 2F, 350 2F,-354 2F.

Note added to label 072 33.

Digits of label 014 changed from 3 to 4 (previouslyadopted).

Range of label 014 changed from 359 to 359.9(previously adopted). Significant bits of label 321changed from 12 to 11 (typo).

Note [4] added.

Note [5] added.

Note flag [5] added to following labels:

074 2C, 075 2C, 247 2C 250 2C, 256 2C, 257 2C, 2602C, 262 2C.

ATTACHMENT 6 – GENERAL WORD FORMATSAND ENCODING EXAMPLES

Formats for engine serial number words added.

Formats for ASAS words added.



SUPPLEMENT 8

TO



Published: December 3, 1984





This Supplement introduces new label assignments,revised data standards, expanded text describing SDIcodes and makes note of a change in the resolution of theMagnetic Heading label incorporated in Supplement 7.





This section presents a complete tabulation of the changesand additions to the Specification introduced by thisSupplement. Each change or addition is entitled by thesection number and title currently employed in theSpecification, or by the section number and title that willbe employed when the Supplement is eventuallyincorporated. In each case there is included a briefdescription of the addition or change and, for other thanvery minor revisions, any text originally contained in theSpecification is reproduced for reference.

2.1.4 SOURCE DESTINATION IDENTIFIER

Text added to clarify use of SDI on combined source/sinkequipment.



Bit nos. 9 and 10 of numeric data words should bereserved for a data source/destination identificationfunction. They are not available for this function inalpha/numeric (ISO Alphabet No. 5) data words (SeeSection 2.3.1.3 of this document) or when the resolutionneeded for numeric (BNR/BCD) data necessitates theiruse for valid data. The source/destination identifierfunction may find application when specific words needto be directed to a specific system of a multi-systeminstallation or when the source system of a multi-systeminstallation needs to be recognizable from the wordcontent. When it is used, a source equipment shouldencode its aircraft installation number in bit nos. 9 and10 as shown in the table below. A sink equipment shouldrecognize words containing its own installation numbercode and words containing code “00”, the “all-call” code.

Bit No.10 9

InstallationNo.

0 0 See Note Below0 1 11 0 21 1 3

Note: In certain specialized application of the SDIfunction the all-call capability may be forfeited so thatcode “00” is available as an “installation no. 4” identifier.

When the SDI function is not used, binary zeros or validdata should be transmitted in bit nos. 9 and 10.

COMMENTARY

This document does not address the practicalquestion of how the SDI bits will be set in thosemulti-installation systems in which thesource/destination function is desired. One waywould be to use program pins on the individualinstallation black boxes which would be wired to setup the appropriate code. The ARINC Characteristicsdevoted to the individual systems will define themethod actually to be used.



012 25, 060 3C, 061 3C, 062 3C, 063 3C, 064 3C, 1372F, 137 3F, 140 25, 141 25, 142 25, 151 27, 152 27, 15327, 154 27, 155 27, 156 27, 157 27, 160 27, 161 27, 16227, 163 27, 164 25, 164 27, 165 27, 170 C5, 173 25, 27025, 271 C5, 272 C5, 273 C5, 274 25, 275 25, 313 25, 31425, 317 25, 320 25, 324 25, 325 25, 330 2F, 330 3F, 3312F, 332 2F, 332 3F, 333 3F, 334 2F, 334 3F, 350 25, 35125, 352 25, 353 25, 370 C5.

ATTACHMENT 1 - EQUIPMENT CODES

Code 3C assigned to Tire Pressure System.


Table 1 had been modified in Supplement 7 to reflect theresolution of label 014 as 0.1, rather than 1.0, which hadbeen incorrectly introduced in a previous Supplement.This change is hereby noted.

Data standards added for new labels.

Data standards revised for labels 115 2F, 115 3F, 325 2F,325 3F.

ATTACHMENT 6 – GENERAL WORD FORMATS

Tire pressure SDI bit coding added.



SUPPLEMENT 9

TO



Published: April 30, 1985


Adopted by the Airlines Electronic Engineering Committee: October 11, 1984



This Supplement introduces new label assignments andequipment identification codes. This Supplement alsocorrects a word format bit error introduced in aprevious Supplement.


The first part of this document, printed on goldenrodpaper, contains descriptions of the changes introducedinto the Specification by this Supplement, and, whereappropriate, extracts from the original text forcomparison purposes. The second part consists ofreplacement white pages for the Specification, modifiedto reflect these changes. The modified and addedmaterial on each replacement page is identified with “c-9” symbols in the margins. Existing copies ofSpecification 429 may be updated by simply insertingthe replacement white pages they replace. Thegoldenrod pages should be inserted inside the rearcover of the Specification.






075 3E, 076 3E, 103 1B, 104 1B, 105 1B, 106 1B, 1071B, 130 35, 131 35, 132 35, 203 18, 270 1B, 270 35,270 3E, 270 4A, 271 18, 271 35, 272 18, 272 35, 27318, 273 35, 274 18, 274 35, 275 18, 275 4A, 276 18,300 3D, 336 1A, 337 1A, 347 18, 347 35, 350 18, 35035, 350 3E, 370 04, and 370 05.


Codes 3D, 3E, 4A, 4B, 4C and 90-9F given newassignments.


Data standards entered for new labels. Range for labels012 and 170 changed to 7999.


Label 150 and 323 examples corrected.



SUPPLEMENT 10

TO



Published: November 17, 1986




A PURPOSE OF THIS SUPPLEMENT

This Supplement introduces new label assignments,equipment identification codes and revised data standards.





This section presents a complete tabulation of the changesand additions to the Specification introduced by thisSupplement. Each change or addition is entitled by thesection number and title currently employed in theSpecification, or by the section number and title that willbe employed when the Supplement is eventuallyincorporated. In each case there is included a briefdescription of the addition or change and, for other thanvery minor revisions, any text originally contained in theSpecification is reproduced for reference.

3.1.4 FREQUENCY RANGES AND SWITCHINGFUNCTIONS

Note 6 deleted on DME Frequency Word.

Attachment 1 – Label Codes


072 02, 075 0B, 076 0B, 077 0B, 176 5A, 177 5A, 2005A, 201 5A, 202 5A, 203 5A, 204 5A, 205 5A, 206 18,213 8D, 227 7E, 241 4D, 242 09, 242 10, 242 11, 242 12,244 8D, 247 4D, 251 1A, 255 2F, 255 3F, 256 4D, 2700B, 272 3A, 272 5A, 273 5A, 274 5A, 275 5A, 276 2F,276 3F, 335 2F, 336 2F, 336 3F, 356 XX, 371 00.

Labels for ARINC Characteristic 737 WBT and ARINCCharacteristic 738 ADIRS added.

Attachment 1 – Equipment Codes

The following codes have been given new assignments:

0B, 35, 36, 37, 38, 4D, 4E, 5A, 5B, 5C, 5D, 5E, 5F, 6A,6B, 6C, 6D, 6E, 6F, 7A, 7B, 7C, 7D, 7E, 7F, 8A, 8B, 8C,8D, AD, C3.

Attachment 2 – Data Standards

Data standards entered for new labels.

Data standards revised for the following labels:

060 36, 061 3C, 062 3C, 063 3C, 064 3C, 15031, 176 03, 176 29, 270 3A, 270 2F, 270 3F, 271 2F, 2713F, 272 2F, 272 3F, 273 2F, 273 3F, 274 2F, 274 3F, 2752F, 275 3F, 350 2F, 350 3F, 351 2F, 351 3F, 352 2F, 3523F, 353 2F, 353 3F, 354 2F, 354 3F.

Labels 060 37-064 3C significant bits changed from 9 to10 and range changed from 512 to 1024.

Following note added to words (labels 270 3B-275 3B):

Typical discrete functions are shown in the abovetables. Slight variations of bit usage may ariseaccording to the specific application.

Label 203 35 changed to 203 18 (typographical error).

Transmit interval range added to label 150 31.

Labels 176 03 and 176 29 resolutions changed from 0.05to 0.5 (typographical error).

Original bit assignments for remaining labels listed infollowing pages.

Attachment 6 – General Word Formats and EncodingExamples

Example added for label 251 1A, 077 0B and 206 18.

For TPIS word formats:

Wheel #519 label corrected to read “060”. SDI labelsclarified.

For BTMS word formats:

Wheel #10, #11, #12 labels corrected to read “116”. Bit27 assigned to a value of “1024”. SDI labels clarified.

Special expanded format word example added for label260 31.

Attachment 9A – General Aviation Labels and DataStandards

New attachment added.

Attachment 9B – General Aviation Word Examples


Attachment 9C – General Aviation Equipment Identifiers



Table 3.11 Propulsion Discrete Interface Unit – Labels 270 3A and 271 3A

Label 270 3A


1 0Notes

1 X2 X3 X4 Label X5 X6 X7 X8 X9

10

SDI 1 0 Left Engine Right Engine SDI 0 1

11 PDIU Status Flag Failed OK12 T2 / P2 Probe Heat HEAT OFF HEAT ON13 TLA Interlock Fault FAULT OK 114 Idle Select MINIMUM APPROACH15 Air/Ground Switch GROUND AIR16 Opposite Engine Status SHUT DOWN RUNNING17 Spare X 218 Spare X19 N2 Mode Trim Release (PROV) RELEASED FIXED 120 Spare X21 Spare X22 Spare X23 Maintenance Test (Provisional) ON OFF 124 Ground Test Power ON OFF25 Spare X26 T/R Indication Power Failed (PROV) FAILED OK 127 T/R Not Stowed NOT STOWED STOWED 128 T/R Deployed Indication DEPLOYED NOT DEPLOYED 129 Engine Fire Warning ON OFF 130 SSM31 SSM32 Parity (Odd)

1 = RETURN TO SPARE

2 = CHANGE SPARE TO DEFINITION ON NEXT PAGE


Table 3.12 EEC Status – Labels 270 2F, 270 3F, 271 2F, 271 3F, 272 2F, 272 3F, 273 2F, 273 3F, 274 2F, 274 3F, 275 2F,275 3F

Label 270 2F

Bit Status

Bit No. Function 1 0 Notes

1 X2 X3 X4 Label X5 X6 X7 X8 X9 SDI

10 SDI11 PAD X12 PAD X13 PAD X14 Spare X 215 Data Entry Plug Failed Normal 116 Auto Mode Selected Not Selected 317 Channel Manually Selected Selected Not Selected 318 N2 Droop Control Mode Engaged Not Engaged19 Reverser System Failed Failed OK20 Channel Controlling Status Controlling Not Controlling21 Bleed Fall-Safe Open Fall-Safe Operational 322 TCA Valve Failed Closed Failed OK23 Spare X 224 Overspeed Self-Test Failed Failed OK 325 Channel Incapable (Failed) Incapable Capable26 Abnormal Start Abnormal OK (Provision) 327 SVA Fall-Safe Fall-Safe 328 Starter Cutout Command Cutout Not Cutout29 Oil Overtemperature Overtemp OK 130 SSM31 SSM32 Parity (Odd)

1 = RETURN TO SPARE

2 = CHANGE SPARE TO DEFINITION ON NEXT PAGE

3 = CHANGE DEFINITION TO DEFINITION ON NEXT PAGE


Label 270 3F

Bit Status



10 SDI11 PAD X12 PAD X13 PAD X14 Spare X 215 Data Entry Plug Failed Normal 116 Auto Mode Selected Not Selected 317 Channel Manually Selected Selected Not Selected 318 N2 Droop Control Mode Engaged Not Engaged19 Reverser System Failed Failed OK20 Channel Controlling Status Controlling Not Controlling21 Bleed Fall-Safe Open Fall-Safe Operational 322 TCA Valve Failed Closed Failed OK23 Spare X 224 Overspeed Self-Test Failed Failed OK 325 Channel Incapable (Failed) Incapable Capable26 Abnormal Start Abnormal OK (Provision) 327 SVA Fall-Safe Fall-Safe 328 Starter Cutout Command Cutout Not Cutout29 Oil Overtemperature Overtemp OK 130 SSM31 SSM32 Parity (Odd)


Label 271 2F

Bit Status



10 SDI11 PAD X12 PAD X13 PAD X14 Reverser Deploy Command ON OFF15 Turbine Cooling Air Valve Solenoid ON OFF16 Oil Cooler Bypass Valve Solenoid ON OFF 317 Cowl Vent Solenoid ON OFF 118 Breather Compartment Ejector Sol. ON OFF 119 Spare X 220 Spare X21 Spare X22 Spare X23 Autostar Relay ON OFF (Provision) 124 TLA Interlock Actuator Command Block Fwd Block Rev25 Spare Reverser Group Relay ON OFF (Provision) 126 Spare X 227 Spare X 228 Spare X 229 Spare X 230 SSM31 SSM32 Parity (Odd)


Label 271 3F

Bit Status



10 SDI11 PAD X12 PAD X13 PAD X14 Reverser Deploy Command ON OFF15 Turbine Cooling Air Valve Solenoid ON OFF16 Oil Cooler Bypass Valve Solenoid ON OFF 317 Cowl Vent Solenoid ON OFF 118 Breather Compartment Ejector Sol. ON OFF 119 Spare X 220 Spare X21 Spare X22 Spare X23 Autostar Relay ON OFF (Provision) 124 TLA Interlock Actuator Command Block Fwd Block Rev25 Spare Reverser Group Relay ON OFF (Provision) 126 Spare X 227 Spare X 228 Spare X 229 Spare X 230 SSM31 SSM32 Parity (Odd)


Label 272 2F

Bit Status



10 SDI11 PAD X12 PAD X13 PAD X14 N1 Loop Engaged Not Engaged15 N2 Loop Engaged Not Engaged16 N2 Topping Loop Engaged Not Engaged17 PB Topping Loop Engaged Not Engaged18 PB Topping Loop Minimum Engaged Not Engaged19 EPR Loop Engaged Not Engaged20 Acceleration Schedule Loop Engaged Not Engaged21 Deceleration Schedule Loop Engaged Not Engaged22 T4.9 Topping Loop Engaged Not Engaged 123 Back Up Mode Engaged Not Engaged24 Spare X 225 Spare X26 Spare X27 Spare X28 Spare X29 Spare X30 SSM31 SSM32 Parity (Odd)


Label 272 3F

Bit Status



10 SDI11 PAD X12 PAD X13 PAD X14 N1 Loop Engaged Not Engaged15 N2 Loop Engaged Not Engaged16 N2 Topping Loop Engaged Not Engaged17 PB Topping Loop Engaged Not Engaged18 PB Topping Loop Minimum Engaged Not Engaged19 EPR Loop Engaged Not Engaged20 Acceleration Schedule Loop Engaged Not Engaged21 Deceleration Schedule Loop Engaged Not Engaged22 T4.9 Topping Loop Engaged Not Engaged 123 Back Up Mode Engaged Not Engaged24 Spare X 225 Spare X26 Spare X27 Spare X28 Spare X29 Spare X30 SSM31 SSM32 Parity (Odd)


Label 273 2F

Bit Status



10 SDI11 PAD X12 PAD X13 PAD X14 P4.9 Interface Failed Failed OK 315 PB Interface Failed Failed OK 316 P2 (Pamb) Interface Failed* Failed OK 317 C3C Interface Failed Failed OK 318 T2 Interface Failed Failed OK 319 T4.9 Interface Failed Failed OK 320 Tfuel Interface Failed Failed OK 321 A/D Interface Failed Failed OK 322 RES/LVDT Interface Failed Failed OK 323 SVA Interface Failed Failed OK 324 N1 Interface Failed Failed OK 325 N2 Interface Failed Failed OK 326 P4.9 Sensor Prom Failed Failed OK 327 P2 (Pamb) Sensor Prom Failed* Failed OK 328 PB Sensor Prom Failed Failed OK 329 Background is not Executing Not Executing Executing 330 SSM31 SSM32 Parity (Odd)

* Primary channel uses P2, Secondary channel uses Pamb.


Label 273 3F

Bit Status



10 SDI11 PAD X12 PAD X13 PAD X14 P4.9 Interface Failed Failed OK 315 PB Interface Failed Failed OK 316 P2 (Pamb) Interface Failed* Failed OK 317 C3C Interface Failed Failed OK 318 T2 Interface Failed Failed OK 319 T4.9 Interface Failed Failed OK 320 Tfuel Interface Failed Failed OK 321 A/D Interface Failed Failed OK 322 RES/LVDT Interface Failed Failed OK 323 SVA Interface Failed Failed OK 324 N1 Interface Failed Failed OK 325 N2 Interface Failed Failed OK 326 P4.9 Sensor Prom Failed Failed OK 327 P2 (Pamb) Sensor Prom Failed* Failed OK 328 PB Sensor Prom Failed Failed OK 329 Background is not Executing Not Executing Executing 330 SSM31 SSM32 Parity (Odd)

* Primary channel uses P2, Secondary channel uses Pamb.


Label 274 2F

Bit Status



10 SDI11 PAD X12 PAD X13 PAD X14 Parity Test Hardware Fault Error OK 315 ROM Checksum Failure Failed OK 316 Ram Test Failure Failed OK 317 Instruction Test Failure Failed OK 318 High Speed Cross Link Failure Failed OK 319 Foreground Software Execution Incorrectly Correctly20 Watch Dog Timer Fault Error OK 321 Watch Dog/Parity Counter Latch Latched Not Latched 122 EAROM Failure Failed OK 323 ROM Parity Error Caused Reset Yes No24 RAM Parity Error Caused Reset Yes No25 Watchdog Timer Error Caused Reset Yes No26 Status Buffer or Watchdog/Parity Failed OK 327 Loss of Clock Caused Reset Yes No28 SDD Output #1 W/A Failed OK29 SDD Output #2 W/A Failed OK30 SSM31 SSM32 Parity (Odd)


Label 274 3F

Bit Status



10 SDI11 PAD X12 PAD X13 PAD X14 Parity Test Hardware Fault Error OK 315 ROM Checksum Failure Failed OK 316 Ram Test Failure Failed OK 317 Instruction Test Failure Failed OK 318 High Speed Cross Link Failure Failed OK 319 Foreground Software Execution Incorrectly Correctly20 Watch Dog Timer Fault Error OK 321 Watch Dog/Parity Counter Latch Latched Not Latched 122 EAROM Failure Failed OK 323 ROM Parity Error Caused Reset Yes No24 RAM Parity Error Caused Reset Yes No25 Watchdog Timer Error Caused Reset Yes No26 Status Buffer or Watchdog/Parity Failed OK 327 Loss of Clock Caused Reset Yes No28 SDD Output #1 W/A Failed OK29 SDD Output #2 W/A Failed OK30 SSM31 SSM32 Parity (Odd)


Label 275 2F

Bit Status



10 SDI11 PAD X12 PAD X13 PAD X14 Lamp (1,2 &/or 3) W/A Failed Failed OK 315 Other Channels Depower Discrete Disagree Agree16 PB Sensor Failed Failed OK 317 PT4.9 Sensor Failed Failed OK 318 PT2 (Pamb)* Sensor Failed Failed OK 319 EEC Temperature Status High OK 320 221 222 223 224 225 Spare (all “o” states) 226 227 228 22930 SSM31 SSM32 Parity (Odd)

[3] Primary channel uses PT2, Secondary channel uses Pamb.


Label 275 3F

Bit Status



10 SDI11 PAD X12 PAD X13 PAD X14 Lamp (1,2 &/or 3) W/A Failed Failed OK 315 Other Channels Depower Discrete Disagree Agree16 PB Sensor Failed Failed OK 317 PT4.9 Sensor Failed Failed OK 318 PT2 (Pamb)* Sensor Failed Failed OK 319 EEC Temperature Status High OK 320 221 222 223 224 225 Spare (all “o” states) 226 227 228 22930 SSM31 SSM32 Parity (Odd)

CHANGE * Primary channel uses PT2: Secondary channel uses Pamb.


Table 3.13 EEC Maintenance – Labels 350 2F, 350 3F, 351 2F, 351 3F, 352 2F, 352 3F, 353 2F, 353 3F, 354 2F, 354 3F

Label 350 2F

Bit Status



10 SDI11 PAD X12 PAD X13 PAD X14 N1 Failed Failed OK 315 N2 Failed Failed OK 316 TT2 Failed Failed OK 317 TT4.9 Failed Failed OK 318 Tfuel Failed Failed OK 319 Toll Failed Failed OK 320 Wf Resolver Failed Failed OK 321 SVA LVDT Failed Failed OK 322 Bleed Prox Input Failed Failed OK 323 ACC #1 LVDT Failed Failed OK 324 ACC #2 LVDT Failed Failed OK 325 Reverser LVDT Failed Failed OK 326 AOC LVDT Failed Failed OK 327 Spare LVDT Failed Failed OK 328 TLA Resolver Failed Failed OK 329 Oil Overtemperature Overtemp OK 130 SSM31 SSM32 Parity (Odd)


Label 350 3F

Bit Status



10 SDI11 PAD X12 PAD X13 PAD X14 N1 Failed Failed OK 315 N2 Failed Failed OK 316 TT2 Failed Failed OK 317 TT4.9 Failed Failed OK 318 Tfuel Failed Failed OK 319 Toll Failed Failed OK 320 Wf Resolver Failed Failed OK 321 SVA LVDT Failed Failed OK 322 Bleed Prox Input Failed Failed OK 323 ACC #1 LVDT Failed Failed OK 324 ACC #2 LVDT Failed Failed OK 325 Reverser LVDT Failed Failed OK 326 AOC LVDT Failed Failed OK 327 Spare LVDT Failed Failed OK 328 TLA Resolver Failed Failed OK 329 Oil Overtemperature Overtemp OK 130 SSM31 SSM32 Parity (Odd)


Label 351 2F

Bit Status



10 SDI11 PAD X12 PAD X13 PAD X14 Left ADC Inputs Failed Failed OK 315 Right ADC Inputs Failed Failed OK 316 Wf T/M W/A Failed Failed OK 317 SVA T/M W/A Failed Failed OK 318 BLD T/M W/A Failed Failed OK 319 ACC #1 T/M W/A Failed Failed OK 320 ACC #2 T/M W/A Failed Failed OK 321 AOC T/M W/A Failed Failed OK 322 Spare T/M W/A Failed Failed OK 123 Wf Track Check Failed Failed OK 324 SVA Track Check Failed Failed OK 325 Bld Track Check Failed Failed OK 326 ACC #1 Track Check Failed Failed OK 327 ACC #2 Track Check Failed Failed OK 328 AOC Track Check Failed Failed OK 329 Spare Track Check Failed Failed OK 130 SSM31 SSM32 Parity (Odd)


Label 351 3F

Bit Status



10 SDI11 PAD X12 PAD X13 PAD X14 Left ADC Inputs Failed Failed OK 315 Right ADC Inputs Failed Failed OK 316 Wf T/M W/A Failed Failed OK 317 SVA T/M W/A Failed Failed OK 318 BLD T/M W/A Failed Failed OK 319 ACC #1 T/M W/A Failed Failed OK 320 ACC #2 T/M W/A Failed Failed OK 321 AOC T/M W/A Failed Failed OK 322 Spare T/M W/A Failed Failed OK 123 Wf Track Check Failed Failed OK 324 SVA Track Check Failed Failed OK 325 Bld Track Check Failed Failed OK 326 ACC #1 Track Check Failed Failed OK 327 ACC #2 Track Check Failed Failed OK 328 AOC Track Check Failed Failed OK 329 Spare Track Check Failed Failed OK 130 SSM31 SSM32 Parity (Odd)


Label 352 2F

Bit Status



10 SDI11 PAD X12 PAD X13 PAD X14 Spare X 115 Spare X 116 Spare X17 Spare X 218 Spare X 219 Spare X 220 TCA Valve No. 1 Failed OK 321 TCA Valve No. 2 Failed OK 322 Channel Select Discrete Failed OK 323 PDIU SDD Input Failed Failed OK 324 N1 Sensor Failed* Failed OK (Provision) 325 Pb Pneumatic Line* Failed OK (Provision)26 P4.9 Pneumatic Line* Failed OK (Provision)27 TT4.9 Thermocouple Harness* Failed OK (Provision) 328 PDIU Status Failed OK 329 T/L Forward Interlock Failed OK 330 SSM31 SSM32 Parity (Odd)

*Primary channel only.


Label 352 3F

Bit Status



10 SDI11 PAD X12 PAD X13 PAD X14 Spare X 215 Spare X 216 Spare X17 Spare X 218 Spare X 219 Spare X 220 TCA Valve No. 1 Failed OK 321 TCA Valve No. 2 Failed OK 322 Channel Select Discrete Failed OK 323 PDIU SDD Input Failed Failed OK 324 N1 Sensor Failed* Failed OK (Provision) 325 Pb Pneumatic Line* Failed OK (Provision)26 P4.9 Pneumatic Line* Failed OK (Provision)27 TT4.9 Thermocouple Harness* Failed OK (Provision) 328 PDIU Status Failed OK 329 T/L Forward Interlock Failed OK 330 SSM31 SSM32 Parity (Odd)

* Primary channel only.


Label 353 2F

Bit Status



10 SDI11 PAD X12 PAD X13 PAD X14 N1 Crosscheck Failed Failed OK 315 N2 Crosscheck Failed Failed OK 316 PB Crosscheck Failed Failed OK 117 PT4.9 Crosscheck Failed Failed OK 118 TT2 Crosscheck Failed Failed OK 319 TT4.9 Crosscheck Failed Failed OK 320 Tfuel Crosscheck Failed Failed OK 321 Toil Crosscheck Failed Failed OK 322 Wf Resolver Crosscheck Failed Failed OK 323 SVA Resolver Crosscheck Failed Failed OK 324 Bld Prox Input Crosscheck Failed Failed OK 325 ACC #1 LVDT Crosscheck Failed Failed OK 326 ACC #2 LVDT Crosscheck Failed Failed OK 327 Reverser LVDT Crosscheck Failed Failed OK 328 AOC LVDT Crosscheck Failed Failed OK 329 TLA Resolver Crosscheck Failed Failed OK 330 SSM31 SSM32 Parity (Odd)


Label 353 3F

Bit Status



10 SDI11 PAD X12 PAD X13 PAD X14 N1 Crosscheck Failed Failed OK 315 N2 Crosscheck Failed Failed OK 316 PB Crosscheck Failed Failed OK 117 PT4.9 Crosscheck Failed Failed OK 118 TT2 Crosscheck Failed Failed OK 319 TT4.9 Crosscheck Failed Failed OK 320 Tfuel Crosscheck Failed Failed OK 321 Toil Crosscheck Failed Failed OK 322 Wf Resolver Crosscheck Failed Failed OK 323 SVA Resolver Crosscheck Failed Failed OK 324 Bld Prox Input Crosscheck Failed Failed OK 325 ACC #1 LVDT Crosscheck Failed Failed OK 326 ACC #2 LVDT Crosscheck Failed Failed OK 327 Reverser LVDT Crosscheck Failed Failed OK 328 AOC LVDT Crosscheck Failed Failed OK 329 TLA Resolver Crosscheck Failed Failed OK 330 SSM31 SSM32 Parity (Odd)


Label 354 2F

Bit Status



10 SDI11 PAD X12 PAD X13 PAD X14 REV Command Solenoid W/A Failure Failure OK 315 TCA Solenoid W/A Failure Failure OK 316 Spare Solenoid W/A Failure Failure OK 117 Spare Solenoid W/A Failure Failure OK 118 Spare Relay W/A Failure Failure OK 119 Spare Solenoid W/A Failure Failure OK 320 BCE Solenoid W/A Failure Failure OK 121 Spare Solenoid W/A Failure Failure OK 122 Oil Bypass Solenoid W/A Failure Failure OK 323 Hot Start Relay W/A Failure Failure OK 124 TLA Lockout Relay W/A Failure Failure OK 325 Spare Relay W/A Failure Failure OK 126 Spare X 127 Essen. Sol. Current Sense Failure Failure OK 328 Critical & Noncritical Current Sense Failure Failure OK 329 Spare30 SSM31 SSM32 Parity (Odd)


Label 354 3F

Bit Status



10 SDI11 PAD X12 PAD X13 PAD X14 REV Command Solenoid W/A Failure Failure OK 315 TCA Solenoid W/A Failure Failure OK 316 Spare Solenoid W/A Failure Failure OK 117 Spare Solenoid W/A Failure Failure OK 118 Spare Relay W/A Failure Failure OK 119 Spare Solenoid W/A Failure Failure OK 320 BCE Solenoid W/A Failure Failure OK 121 Spare Solenoid W/A Failure Failure OK 122 Oil Bypass Solenoid W/A Failure Failure OK 323 Hot Start Relay W/A Failure Failure OK 124 TLA Lockout Relay W/A Failure Failure OK 325 Spare Relay W/A Failure Failure OK 126 Spare X 127 Essen. Sol. Current Sense Failure Failure OK 328 Critical & Noncritical Current Sense Failure Failure OK 329 Spare30 SSM31 SSM32 Parity (Odd)



SUPPLEMENT 11

TO



Published: July 22, 1988





This Supplement introduces new label assignments andequipment identification codes.





This section presents a complete tabulation of the changesand additions to the Specification introduced by thisSupplement. Each change or addition is entitled by thesection number and title currently employed in theSpecification or by the section number and title that willbe employed when the Supplement is eventuallyincorporated. In each case there is included a briefdescription of the addition or change and, for other thanvery minor revisions, any text originally contained in theSpecification is reproduced or reference.

2.1.5.1 BCD Numeric, Discrete, Aim Data, and FileTransfer Words

SSM bit patterns separated from main figure.

FIGURE 3-1 RADION SYSTEMS MANAGEMENTWORD FORMATS

HF COM frequency control words added.


070 002, 070 0CC, 071 002, 071 0CC, 072 002, 072 0CC,073 0CC, 074 002, 100 0BB, 101 0BB, 103 0BB, 1040BB, 105 0BB, 106 0BB, 107 002, 114 0CC, 115 0BC,115 0CC, 116 0CC, 117 0CC, 126 002, 127 002,143 041,143 241, 144 041, 144 341, 150 002, 152 041, 153 002,153 041, 162 0DE, 173 0BD, 200 002, 202 002,203 002,204 002, 205 002, 205 0B9, 206 0CC, 207 002, 207 0B9,211 002, 213 002, 213 08D, 220 002, 220 017, 220 024,220 07E, 221 002, 221 017, 221 024, 221 07E, 222 002,222 017, 222 024, 222 07E, 223 002, 223 017, 223 024,223 07E, 224 002, 224 017, 224 024, 224 07E, 225 002,226 0XX, 230 002, 230 017, 230 024, 230 07E, 241 002,242 011, 243 0XX, 244 011, 244 08D, 245 002, 246 002,246 006, 246 009, 247 002, 247 009, 247 0EB, 250 002,250 12B, 252 0EB, 253 002, 254 002, 254 012, 255 002,255 012, 255 08E, 256 002, 256 027, 257 002, 257 027,263 002, 263 010, 264 002, 264 010, 265 002, 267 002,

271 002, 274 0C5, 275 002, 276 001, 276 002, 276 003,300 039, 300 040, 301 002, 301 039, 301 040, 302 002,302 039, 302 040, 303 002, 304 039, 304 040, 305 039,305 040, 306 039, 306 040, 307 039, 307 040, 314 002,316 002, 322 002, 341 002, 342 002, 343 01A, 350 00B,350 027, 350 040, 350 241, 350 341, 351 00B, 351 029,354 002, 355 027, 360 002.

Label 076 008 changed from “Ellipsoidal Altitude” to“GPS Height Above Referenced Ellipsoid”.



039, 040, 041, 08E, 08F, 0AA, 0AB, 0AC, 0AE, 0AF,0BA, 0BB, 0BC, 0BD, 0BE, 0BF, 0C2, 0CA, 0CB, 0CC,0CD, 0CE, 0CF, 0DA, 0DB, 0DC, 0DD, 0DE, 0DF, 0EA,0FF, 10A, 10B, 10C, 10C, 10D, 10E, 10F, 110, 12A, 12B,136, 141, 241, 341.


Data Standards entered for new labels:

Label 076 008 changed from “Ellipsoidal Altitude” to“GPS Height Above Referenced Ellipsoid”.

Data Standards revised for following labels:

076 00B, 077 00B, 270 00B

ATTACHMENT 6

Example revised for label 077 00B.

Example for label 260 removed.

Example for label 260 031 expanded to include 260 002.

Format for label 270 00B added.

Format for label 274 0C5 added.

Format for label 350 027 added.

Code for 747 NR corrected in diagram of TPIS word.

Equipment ID word expanded to accommodate three-character identifier.

ATTACHMENT 9 – GENREAL AVIATIONEQUIPMENT IDENTIFIERS

Code 08C added to list.

Codes for Loran and Omega changed from 08A/08B to05A/05B, respectively.




SUPPLEMENT 12

TO




Prepared by the Airlines Electronic Engineering CommitteeAdopted by the Airlines Electronic Engineering Committee: October 25, 1989



The Supplement introduces the Williamsburg bit-orientedfile data transfer protocol which supports the transfer ofbinary and character data. The previous AIM andcharacter-oriented file transfer protocol sections aremoved to Appendix 6. The Sign Status Matrix (SSM)information is revised and reorganized. In addition, thisSupplement introduces new label assignments andequipment identification codes.


The first part of this document, printed on goldenrodpaper contains descriptions of the changes introduced intothe Specification by this Supplement, and, whereappropriate, extracts from the original text for comparisonpurposes. The second part consists of replacement whitepages for the Specification, modified to reflect thesechanges. The modified and added material on eachreplacement page is identified with “c-12” symbols in themargins. Existing copies of Specification 429 may beupdated by simply inserting the replacement white pagesthey replace. The goldenrod pages should e insertedinside the rear cover of the Specification.



This section presents a complete tabulation of the changesand additions to the Specification introduced by thisSupplement. Each change or addition is entitled by thesection number and title currently employed in theSpecification, or by the section number and title that willbe employed when the Supplement is eventuallyincorporated. In each case there is included a briefdescription of the addition or change and, for other thanvery minor revision, any text originally contained into theSpecification reproduced for reference.


This section contains editorial corrections to comply withchanges introduced in Supplement 11.


This section was revised and reorganized. The changesinclude moving the AIM and file transfer SSM definitionsto Appendix 6, adding failure reporting to the discreteword truth table (Section 2.1.5.3) and moving thedescription of status priorities to Section 2.1.5.


The contents of Sections 2.3.1.4 through 2.3.1.5.7 weremoved to Appendix 6. The AIM Data and File DataTransfer section headings were retained for referencepurposes. Section 2.3.1.5. File Data Transfer, providesthe reason for moving the original file transfer protocoland introduces the Williamsburg protocol.

2.5 Bit-Oriented Communications Protocol

This new section was added to describe a bit-oriented datatransfer protocol. The new protocol was developed toaccommodate the interface of the ACARS ManagementUnit (MU) and the Satellite Data Unit (SDU).


The information previously contained in this section is nolonger applicable to ARINC Specification 429. Forreference purposes, the section header is retained and theoriginal contents of this section are located in Appendix6.



002 115, 013 0B8, 016 0B8, 046 10A, 046 10B, 047 10A,047 10B, 107 0BB, 110 0BB, 112 0BB, 114 0BB, 11410A, 114 10B, 127 10A, 127 10B, 130 035, 130 10A13010B, 131 035, 132 035, 133 10A, 133 10B, 134 10A, 13410B, 137 10A, 137 10B, 155 10A, 155 10B, 156 10A,156 10B, 157 10A, 157 10B, 160 10A, 160 10B, 16110A, 161 10B, 201 115, 203 035, 203 10A, 203 10B, 20510A, 205 10B, 211 10A, 211 10B, 220 116, 221 116, 222115, 222 116,223 116, 224 116, 226 035, 230 116, 234039, 234 040, 235 039, 235 040, 236 039, 236 040, 237039, 237 040, 244 10A, 244 10B, 256 114, 257 114, 26010A, 260 10B, 260 114, 261 10A, 261 10B, 261 114, 26210A, 262 10B, 262 114, 263 10A, 263 10B, 263 114, 26410A, 264 10B, 264 114, 265 004, 265 038, 265 10A, 26510B, 265 114, 267 10A, 267 10B, 270 10A, 270 10B, 270114, 270 115, 271 10A, 271 10B, 271 114, 272 002, 27210A, 272 10B, 272 114, 273 10A, 273 10B, 273 114, 27410A, 274 10B, 274 114, 275 10A, 275 10B, 275 114, 276114, 277 018, 300 10A, 300 10B, 300 TBD, 301 10A, 30110B, 302 10A, 302 10B, 303 10A, 303 10B, 304 10A,304 10B, 305 10A, 305 10B, 306 10D, 310 114, 311 114,312 114, 313 114, 316 10A, 316 10B, 320 035, 321 10A,321 10B, 322 10A, 322 10B, 323 10A, 323 10B, 32410A, 324 10B, 325 10A, 325 10B,326 10A, 326 10B, 32710A, 327 10B, 330 10A, 330 10B, 331 10A, 331 10B,335 10A, 335 10B, 336 002, 336 10A, 336 10B, 337 002,337 002, 337 10A, 337 10B, 341 10A, 341 10B, 342 10A,342 10B, 343 10A, 343 10B, 344 10A, 344 10B, 34510A, 345 10B, 346 10A, 346 10B, 347 10A, 347 10B,350 10A, 350 10B, 350 114, 350 115, 351 10A, 351 10B,351 114, 352 10A, 352 10B, 352 114, 353 10A, 353 10B,353 114, 354 10A, 354 10B, 357 035, 360 10A, 360 10B,360 TBD, 361 10A, 361 10B, 362 10A, 362 10B, 362115, 363 10A, 363 10B, 365 TBD, 372 10A, 372 10B,373 10A, 373 10B, 374 10A, 374 10B, 374 TBD, 37510A, 375 10B, 375 TBD.

Revised label 130 035 from “Traffic Advisory Range” to“Intruder Range”.

Revised label 131 035 from “Traffic Advisory Altitude”to “Intruder Altitude”.

Revised label 132 035 from “Traffic Advisory Bearing”to “Intruder Bearing”.


Removed label 130 030 Traffic Advisory Range.

Removed label 131 030 Traffic Advisory Altitude.

Removed label 132 030 Traffic Advisory BearingEstimate.

Removed label 270 030 Transponder Discrete.

Removed label 347 030 Sector Control.

Removed label 347 035 Antenna Control.



113, 114,115, 116, 117, 118, 119, 11A, 123, 124, 125,126, 127, 128, 129, 15A, 15B, 15C, 15D, 15E, 16A, 16B,16C, 16D, 16E, 17A, 17B, 17C, 18A, 18B, 18C, 18D,18E, 18F.


Tables 1, 2 updated to reflect changes to Attachment 1.

Binary Data notes 6, 7 and 8 added.

Discrete Data Standards entered for new labels:

272 002, 271 018, 272 018, 273 018, 275 018, 276 018,277 018, 274 018, 270 035, 271 035, 273 035, 274 035,275 035, 013 0B8, 016 0B8, 161 10A, 161 10B, 350 114,351 114, 352 114, 353 114, 270 115, 350 115.


Add format for TCAS Intruder Range label 130.

Add format for TCAS Intruder Altitude label 131.

Add format for TCAS Intruder Bearing label 132.

Add format for Transponder Altitude/TCAS Own A/CAltitude label 203.

Removed 730 ASAS Sector Control Word example.

Removed 730 TCAS Traffic Advisory Range Wordexample.

Removed 730 TCAS Traffic Advisory Altitude Wordexample.

Removed 730 TCAS Traffic Advisory Bearing Estimateword example.

ATTACHMENT 9B – GENERAL AVIATION WORDEXAMPLES

Add new Company Name Identifier.

ATTACHMENT 10 – VARIABLES OF BIT-ORIENTED PROTOCOL

Add new Attachment.

ATTACHMENT 11 – BIT-ORIENTED DATA FILETRANSFER WORD FORMATS

Add new Attachment.ATTACHMENT 11A – DESTINATION CODES

Add new Attachment.

ATTACHMENT 11B – STATUS CODES

Add new Attachment.

ATTACHMENT 11C – ALOHA/ALOHA RESPONSEPROTOCOL WORDS

Add new Attachment.

ATTACHMENT 12 – FILE TRANSFER EXAMPLE

Add new Attachment.

ATTACHMENT 12A – FILED MAPPING EXAMPLE

Add new Attachment.

ATTACHMENT 13 – PROTOCOL DETERMINATIONPROCEDURE DIAGRAMS

Add new Attachment.

ATTACHEMENT 14 – SYSTEM ADDRESS LABELS

Add new Attachment.

ATTACHMENT 15 – LINK LAYER CRC DATAEXAMPLE

Add new Attachment.

APPENDIX 6 – FORMER MAINTENANCE, AIM ANDFILE TRANSFER TECHNIQUES

Add new Appendix.

APPENDIX 7 – MATHMATICAL EXAMPLE OF CRCENCODING/DECODING

Add new Appendix.



SUPPLEMENT 13

TO








This Supplement introduces changes made to theWilliamsburg protocol as a result of its initialimplementation. This protocol supports the transfer ofbinary and character data. In addition, this Supplementintroduces new label assignments and equipmentidentification codes.


The first part of this document, printed on goldenrodpaper contains descriptions of changes introduced intothis Specification by this Supplement. The second partconsists of replacement white pages for the Specification,modified to reflect the changes. The modified and addedmaterial on each page is identified by a c-13 in themargins. Existing copies of ARINC Specification 429may be updated by simply inserting the replacementwhite pages where necessary and destroying the pagesthey replace. The goldenrod pages are inserted inside therear cover of the Specification.

C. CHANGES TO ARINC SPECIFICATION 429INTRODUCED BY THIS SUPPLEMENT

This section presents a complete tabulation of the changesand additions to the Specification introduced by thisSupplement. Each change or addition is defined by thesection number and the title currently employed in theSpecification or by the section name and title that will beemployed when the Supplement is eventuallyincorporated. In each case a brief description of thechange or addition is included.


An editorial change, correction to section numbering.


New Section added to describe ALO/ALR protocolprocess to be used when a bilingual Link Layer protocolsystem needs to determine necessary bit-orientedinterfaces.

2.5 Bit-Oriented communications Protocol

Included term “Williamsburg” parenthetically since thisterminology well-known in industry. Added commentaryto explain non-negotiation or parameters in this protocol.

D. Corrected Network Layer definition.

2.5.2 Link Data Unit (LDU) Size and Word Count

Added second paragraph to text, since it is a requirement,and removed second paragraph from commentary.

2.5.4 Bit Rate and Word Timing

Corrected the commentary to change the more ambiguousterm “message” to LDU.

2.5.5.3 Destination Code

An editorial change was made.

2.5.6 Response to RTS

The last sentence in the second paragraph was rewordedand moved to a more appropriate section, 2.5.6.2.

2.5.6.1 Clear to Send (CTS)

In the second to last sentence, the word “valid” was addedto clarify the Not clear to send condition. The lastsentence was added to clarify the resetting of RTScounters.

2.5.6.2 Not Clear to Send (NCTS)

The first paragraph was updated to include theinformation deleted from Section 2.5.6 and to clarify thevalidity requirements. The second paragraph was updatedto describe that and NCTS counter would be reset upon avalid CTS response. The last sentence in the thirdparagraph was deleted and it’s content expanded in thefollowing commentary of that section.

2.5.6.3 Destination Busy

The second paragraph of this section was updated toindicate that a BUSY counter should be reset with a validCTS response to RTS.

2.5.7 No Response to RTS

The first paragraph of this section was updated to describeproper response to RTS.

2.5.9 Unexpected RTS

This section was updated to include editorial changes anda description of the correct responses to RTS. The lastsentence was deleted as redundant to Section in 2.5.13.1and in conflict with other possible responses.

2.5.11 Data

The fourth paragraph of this section was updated todescribe the proper ending of an LDU transmission, andto include the optional NAK response for receipt of anincomplete octet.

2.5.11.3 Character Data Words

In the last paragraph, the “note” designator was removedand the text clarified for the transfer of characters with aparity bit.

2.5.13 Negative Acknowledgement (NAK)

This section was updated to clarify conditions for sendingthe NAK word.

AEEC STAFF NOTE: THESE CHANGESAPPLY TO ARINC 429, PART 3 ONLY.


2.5.13.1 Missing SOT word

Text was corrected to refer to “reception” instead of“transmission” of a valid SOT word. Also, incorrect textreferring to the NAK response timing was deleted.

2.5.13.2 LDU Sequence Number Error

The original text was omitted. Sections 2.5.13.1 –2.5.13.7 were renumbered.

2.5.13.3 Parity Errors

A commentary section was added to describe theprocedures for receiving words with bad parity.

2.5.13.4 Word Count Errors

This section was updated to clarify the NAK responsetime for word count errors.

2.5.13.5 CRC Errors

This section was updated to clarify the NAK responsetime for CRC errors.

2.5.13.6 Time Out Errors

This section was renumbered.

2.5.13.7 Restart Initialization

This section was omitted due to potential conflicts withthe ALO/ALR procedures.

2.5.14 LDU Transfer Acknowledgement (ACK)

Text was revised to include LDU conditions for sinkacknowledgement transmission.

2.5.14.1 Duplicate LDU

This section was added to describe duplicate LDUoccurrences.

2.5.14.2 Auto-Synchronized Files

This section was added to describe the method ofhandling auto-synchronized files.

2.5.15 SYN Word

New text was added to describe SYN response times fornon-consecutive LDU Sequence numbers. The lastparagraph was incorrect and deleted.

2.5.16 Response to ACK/NAK/SYN

New text was added to describe actions when NAK andSYN are detected during a transmission.

2.5.19 ALO Response

A new section was added and updated to describe ALOresponses.

ATTACHMENT 10 – VARIABLES OF BITORIENTED PROTOCOL

Tables 10-1 and 10-3 were updated to include events N5,N6, and time T12. Options 07 and 012 in Table 10-4 werechanged to spares for consistency with corresponding textupdates.

ATTACHMENT 11C – ALOHA/ALOHA RESPONSEPROTOCOL WORD DEFINITION

Table 11C-3 was added to clarify protocol versionnumber assignments, and is referenced by “note 1”.“Note 2” was added to describe the GFI field of theALOHA word.

ATTACHMENT 12A – FIELD MAPPING EXAMPLE

Bk was changed to B24 in the data word map, “nibble” waschanged to “semi-octet”, and semi-octet arrow lengthswere shortened to correspond to the proper four and eight-bit lengths.

APPENDIX 7 – MATHEMATICAL EXAMPLE OFCRC ENDODING/DECODING

Format (alignment) changes were made in the polynomialdivisions, “(X)” was corrected to “Q(x)”, and thetransmission order for the LDU Mapping of the 24-bitexample was deleted to avoid possible misinterpretation.


2551 Riva RoadAnnapolis, Maryland 21401 – 7645 USA

SUPPLEMENT 14

TO








This Supplement introduces changes made to increase theefficiency of data transfer across an ARINC 429 highspeed bit-oriented link. This protocol supports thetransfer of binary and character data.


The first part of this document, printed on goldenrodpaper, contains descriptions of changes introduced intothis Specification by this Supplement. The second partconsists of replacement white pages for the Specification,modified to reflect the changes. The modified and addedmaterial on each page is identified by a c-14 in themargins. Existing copies of ARINC 429 may be updatedby simply inserting the replacement white pages wherenecessary and destroying the pages they replace. Thegoldenrod pages are inserted inside the rear cover of theSpecification.


This section presents a complete tabulation of the changesand additions to the Specification introduced by thisSupplement. Each change and addition is defined by thesection number and the title currently employed in theSpecification or by the section name and title that will beemployed when the Supplement is eventuallyincorporated. In each case a brief description of thechange or addition is included.


An editorial change was needed to reference new section.


This section was expanded to include determination ofdifferent version numbers of the bit-oriented protocol, andwas moved to Section 2.5.19.

2.5 Bit-Oriented Communication Protocol

An editorial change references a new section number.


A maximum word gap of 64 bit-times, (averaged over theLDU transmission) was added to eliminate excessivedelay in source transmission time.

Note: Sections 2.5.5 through 2.7 have been renumberedand reordered for consistency.

2.5.5 Word type

The basic definition of “word type” was corrected toinclude bits 31-29 in all bit-oriented words of an LDU.

2.5.6 Protocol Words

This section was added to specifically define the wordtype for protocol words.

2.5.6.1 Protocol Identifier

This section was added to clarify the definition of bits 28-25 for protocol words and to specify the relevant additionfor error conditions.


This section was updated, and a commentary added, toclarify the role of the link layer protocol for upwardcompatibility with changing network functionality. Therequirement for Destination code validation is not a linklayer function.

2.5.6.3 Word Count


2.5.7 Request to Send (RTS)

This section was previously titled “Response to TS”, andhas been renumbered. The title was changed forconsistency, and an introductory paragraph added toclarify the basic RTS function.






This section was renumbered, and an introductoryreplacement paragraph inserted to clarify the “optional”BUSY response, which may be used when a systemcannot accept a transmission by the source in a “timelymanner”. New commentary equates a “timely manner” tothe shorter retry sequence of the NCTS series.

2.5.7.4 No Response to RTS

This section was renumbered, and the ALOHA word wasincluded in the logic for error determination.

2.5.10 Start of Transmission (SOT)

Timer T13 was added as a requirement on the source tobegin transmission of an LDU within a specified intervalafter receipt of the CTS word from the sink.

2.5.10.1 General Format Identifier (GFI)

This section was updated, and commentary added toclarify the role of the GFI in pre-OSI as well as OSIenvironments. Validation of the GFI code is required bya high level entity (network layer) in both environmentsto determine the format of the data words to follow. GFIvalidation is not necessarily a link layer function.



2.5.11 Data

All references to Character Data word formats weredeleted.


This section was deleted. The Character Data Wordformat was removed from Supplement 14, as the format isincompatible with those for Full and Partial Data wordformats. Currently, both binary and character data aretransmitted in octets defined by the other two data wordformats. The special character data format is notrequired.

2.5.12.1 CRC Encoding

References to character data words were deleted. Thetext for equation: M9x) = x16G(x) + R(x) was correctedby moving the “bar” from G(x) to R(x).


NAK word interpretation was changed to removeconstraint on source for specific order of file sequencing(i.e. Allows source to restart file with new FSN ifnecessary).


This first paragraph was rewritten to clarify.

2.5.14.3 Incomplete File Timer

This section was added to allow the sink to discard apartial file of multiple LDUs when the T14 timeoutbetween LDU transmissions is exceeded. It ensures that asource device cannot “lock-up” a sink.

2.5.15 SYN Word

The LDU sequence anomalies which generate a SYNresponse by the sink were clarified.


The T16 timer was introduced to replace T10 and T8. Also,the action taken by the source upon receipt of a SYNword was updated, which relaxes requirements tomaintain a specific File Sequence ordering by the source.

2.5.19 Protocol Initialization

2.5.19.1 Bit-Oriented Protocol Version,

2.5.19.2 ALOHA Response, and

2.5.19.3 Character-429 Determination

This section has been added to replace and expand on thedefinition of the process to determine the link layerprotocol version supported by an interfacing system.These sections replace three sections from Supplement13.


2.5.19 ALO Response, and

2.5.20 Bit Protocol Verification

2.6 Windowed Bit-Oriented Protocol

This is a completely new section which contains thesystem description of the new LLC2-like bit-oriented linklayer protocol for 429. It is based on Section 2.5, “Bit-Oriented Communications Protocol”, with expanded textas specified to allow for more efficient use of the 429high (or low) speed data bus through “windowing”. Thedefinition includes provision for a Link Control Wordprior to each LDU.


New Equipment Code Identifiers were added.

ATTACHEMENT 6 – WORD FORMATS ANDENCODING EXAMPLES

Example added for label 171.


Table 10-1 was updated to include a standard value forN7, the maximum number of LDUs in a window (seeSection 2.6 “Windowed Bit-Oriented Protocol”).

Table 10-3 deleted Option 6 (O6) for NAK Send Time,and deleted Option 9 (O9) for the Character Data Word,both of which are no longer used.

Table 10-4 was revised to include columns for low speedmaximum and minimum values. These values wereestablished for timers and as response time design goalsfor incoming transmissions. Timers T13 through T16 wereadded.

Table 10-5 was added to include a definition of highspeed maximum and minimum values for timers andresponse time design goals. The format is the same as therevised Table 10-4. Timer T10 is not used in the highspeed protocol.

Table 10-6 was added to include notes to Tables 10-1through 10-5.


Table 11-1A added “spares” for the deleted CharacterData Formats and corrected “Protocol Data Word” to read“Protocol Word”.

Table 11-4 updated definitions for bits 9 through 24 of theALO and ALR words, and added the LCW (LDU ControlWord) format definition.

Table 11-4A was added as a partial replacement forATTACHMENT 11C and Table 11-4B was added todefine the new window definitions for the Windowed Bit-Oriented protocol in Section 2.6.

Table 11-6A was revised, changing the former GFI bitpattern (0001) for ISO 8208 to “unassigned”. The bitpattern (0100) for ISO 8473 was changed to a more


ATTACHMENT 11 – BIT-ORIENTED DATA FILETRANSFER WORD FORMATS (cont’d)

generic ISO 9577 definition. The bit pattern 1110(hex”E”) is now defined as “ACARS VHF Format”.The“NOTES” in ATTACHMENT 11 have been renumberedto correspond to the new table definitions.


This Attachment has been deleted. This information hasbeen moved to Tables 11-4, 11-4A, and 11-4B.

ATTACHMENT 13A – ALOHA VERSIONDETERMINATION SEQUENCE

This Attachment was added to support the ALOHAversion determination sequence called out in Section2.5.19.1.1.

ATTACHMENT 14 – SYSTEM ADDERESS LABELS

New System Address Labels (SAL) were added.

ATTACHMENT 16 – SEQUENCE OF PROTOCOLAND DATA WORDS IN WINDOW TRANSFER

This Attachment was added to illustrate the windowtransfers for new Section 2.6.

ATTACHMENT 17 – FLOW DIAGRAM USED TODETERMINE CHARACTER-ORIENTED VS BIT-ORIENTED PROTOCOL

This Attachment was added to illustrate the logic flowthat determines whether a character-oriented or bit-oriented link layer protocol interface is to be used.



SUPPLEMENT 15

TO







A. PURPOSE OF THIS DOCUMENT

This Supplement introduces new label assignments,equipment IDs, system address labels and updates to the429W protocol.


The first part of this document, printed on goldenrod papercontains descriptions of changes introduced into thisSpecification by this Supplement. The second part consistsof replacement white pages for the Specification, modifiedto reflect the changes. The modified and added material oneach page is identified by a c-15 in the margins. Existingcopies of ARINC Specification 429 may be updated bysimply inserting the replacement white pages wherenecessary and destroying the pages they replace. Thegoldenrod pages are inserted inside the rear cover of theSpecification.

C. CHANGES TO ARINC SPECIFICATION 429 INTRODUCED BY THIS SUPPLEMENT

This section presents a complete tabulation of the changesand additions to the Specification introduced by thisSupplement. Each change or addition is defined by thesection number and the title currently employed in theSpecification or by the section name and title that will beemployed when the Supplement is eventually incorporated. In each case a brief description of the change or addition isincluded.

2.0 Digital Information Transfer System Standards

Numerous changes were made to the protocol throughoutthis Section.


The technique for encoding SSM bits in discrete wordswere revised.



A source system should annunciate any detected failure thatcould cause one or more of the words normally output bythat system to be unreliable. Three methods are defined. The first method is to set bit numbers 30 and 31 in theaffected word(s) to the “Failure Warning” code defined inthe table below. This is the preferred method. Wordscontaining the “Failure Warning” code should continue tobe supplied to the data bus during the failure condition. When using the second method, the equipment may stoptransmitting the affected word or words on the data bus. The third method applies to data words which are definedsuch that they contain failure information within the datafield. For these applications, refer to the associated ARINCequipment characteristic to determine the proper SSMreporting.The “No Computed Data” code should be annunciated inthe affected Discrete Data word(s) when a source system isunable to compute reliable data for reasons other thansystem failure.

When the “Functional Test” code appears as a systemoutput, it should be interpreted as advice that the data in theDiscrete Data word contents are the result of the executionof a functional test.

DISCRETE DATA WORDS

2.2.2 Modulation

The following Commentary was added:

“Avionics manufacturers are warned that bus activitymonitoring should be implemented with caution. Crossedwiring (interchanging A and B) at one end of the bus, whichwill cause improper LRU/system operation, may notnecessarily be detected by a “simple” bus activity monitor.”


The word “parallel” was changed to “combination”.

Figure 3.1 Radio Systems Management Word Formats

VHF Com Frequency Word - Bits 7,8,20,23 changed to “0”and bits 15,16,21,28 changed to “1”.

ATTACHMENT 1 - LABEL CODES

This attachment was updated according to the tables on thefollowing pages.

Designation for label 155 027 changed from BCD to BNR.

ATTACHMENT 1 - LABEL CODES

The following new equipment codes were assigned:03D, 053, 05A, 0D0, 0E0, 12C, 160, 19F, 13B

ATTACHMENT 2 - DATA STANDARDS

This attachment was updated according to the tables on thefollowing pages. Newly assigned discrete word formats areincluded.

In word 270 115, bit 12 was changed from “pad” to “Tune”. AUTOTUNE was assigned for “1” and NO AUTOTUNEwas assigned to “0”.

Word 155 027 moved from Table 1 to Table 2.

In Table 2 “SIG DIG” was changed to “SIG BIT”.In Table 2 under label 077, “0--” was changed to “037”.

Duplicate 244 08D word removed.

BitMeaning

300 0 Verified Data, Nomal Operation0 1 No Computed Data1 0 Functional Test1 1 Failure Warning


ATTACHMENT 6 - GENERAL WORD FORMATS ANDENCODING EXAMPLES

Table 2 - examples for Flight Director Pitch and Total AirTemp corrected.

Examples for the following tables added.

Manufacturer Specific Data Word010101 assigned to Garmin010110 assigned to ARNAV Systems

Bit 11 modified for label 150 to include reference toprecision source.

Word format for label 077 00B removed (from two places).

ATTACHMENT 9B - GENERAL AVIATION WORDEXAMPLES

Manufacturer Specific Data Word010101 assigned to Garmin010110 assigned to ARNAV Systems

ATTACHMENT 10 - VARIABLES OF BIT-ORIENTEDPROTOCOL

Revised Notes 1 and 4.

Table 10-3 BIT-ORIENTED PROTOCOL OPTIONS -Added Option 012

Table 10-5 VARIABLES OF HIGH SPEED BIT-ORIENTED PROTOCOL - Revised Time T10 min and maxvalues.

ATTACHMENT 11 - BIT-ORIENTED DATA FILETRANSFER WORD FORMATS

Table 11-6A GENERAL FORMAT IDENTIFIER (GFI) -Revised “Reserved ISO 9577” to “ISO 9577”

ATTACHMENT 11A - DESTINATION CODES

Added Cabin Packet Data Function. Corrected GroundStation bit encoding.

ATTACHMENT 11B - STATUS CODES

Revised description of Code 86. Added entries for Code 8Ethrough 95.

ATTACHMENT 14 - SYSTEM ADDRESS LABELS

The following labels were added:170 DFDAU (Mandatory Load Function)266 Cabin Video System (Airshow)334 Cabin Telecommunications Unit (CTU)340 HF Data Radio/Data Unit #1344 HF Data Radio/Data Unit #2

The following labels were revised:175 HGA HPA176 Spare177 LGA HPA

APPENDIX 8 - INTEROPERABILITY OF BIT-ORIENTED LINK LAYER PROTOCOL

Appendix added.

APPENDIX 9 - SDL DIAGRAMS OF THEWILLIAMSBURG PROTOCOL

Appendix added.

NEW AND REVISED BNR LABEL ASSIGNMENTS

LABEL EQ ID PARAMETER BINARY UNITS RANGE SIG RESOLMIN

TIMAX

TIREF NOTES

New 061 002 ACMS Information 10 See Att. 6New 062 002 ACMS Information 10 See Att. 6New 063 002 ACMS Information 10 See At. 6New 145 002 TACAN Control See Section 3.1.4 180 220 8 See Att. 6Add 226 002 Min Op. Fuel Temp (non-conflicting) 34New 233 002 ACMS Information 10 See Att. 6New 234 002 ACMS Information 10 See Att. 6New 235 002 ACMS Information 10 See Att. 6New 236 002 ACMS Information 10 See Att. 6Revise 265 002 Min Buffet Airspeed 11 31Revise 360 002 Flight information See Att. 6Revise 370 004 g 31Revise 014 005 Magnetic Heading Deg 31Revise 370 005 g 31Revise 205 006 Mach 4096 31Revise 205 01A Mach 4096 31New 034 025 VOR/ILS Frequency 125 250 6New 035 025 DME Frequency 125 250 6New 060 025 S/G HARDWARE PART NO. 6 See Att. 6New 061 025 S/G HARDWARE PART NO. 6 See Att. 6New 101 025 Selected Heading Deg/180 + - 180 12 0.05 125 250 6New 121 025 Pitch Limit Deg/180 + - 180 14 0.01 125 250 6New 145 025 Discrete Status 2 EFIS 6New 146 025 Discrete Status 3 EFIS 6New 147 025 Discrete Status 4 EFIS 6New 155 025 Discrete Status 5 EFIS 6New 160 025 Discrete Status 6 EFIS 6New 161 025 Discrete Status 7 EFIS 6New 162 025 ADF brg left/right Deg/180 + - 180 12 0.05 125 250 6 SDI-01 = left / SDI-10 = rightNew 207 025 OP, SOFTWARE PART NO. 6 See Att. 6New 272 025 Discrete Data #3 6New 273 025 Discrete Data #4 6New 276 025 Discrete Status 8 EFIS 6New 054 037 Zero Fuel Weight (kg) kg 655360 15 20 100 200 15New 074 037 Zero Fuel Weight (lb) lb 1310720 15 40 100 200 15Correction 076 037 Longitudinal C/G 163.84 14New 077 037 Lateral C/G %MAC 131.072 17 0.01 100 200 14New 107 037 Long, Zero Fuel C/G %MAC 163.84 14 0.01 100 200DELETE 256 037 15DELETE 257 037 15DELETE 347 037 15Revise 205 038 Mach 4096 31Revise 342 038 EPR Limit 4 12 0.001 150 250 31Revise 342 038 N1 Limit %RPM 256 14 0.015 150 250 31

SUP

PL

EM

EN

T 15 T

O A

RIN

C SP

EC

IFIC

AT

ION

429 - Page 4



TIMAX

TIREF NOTES

New 227 03D AVM Command 5 See Att. 2New 270 03D Discrete Data #1 5 See Att. 2New 350 03D Maintenance Data #1 5 See Att. 2New 353 03D Maintenance Data #4 5 See Att. 2New 354 03D N1 Vibration Scalar 5.12 9 0.01 5 Bit 11-Chan. A/Bit 12-Chan. BNew 355 03D N2 Vibration Scalar 5.12 9 0.01 5 Bit 11-Chan. A/Bit 12-Chan. BNew 356 03D N3 Vibration Scalar 5.12 9 0.01 5 Bit 11-Chan. A/Bit 12-Chan. BNew 357 03D BB Vibration Scalar 5.12 9 0.01 5 Bit 11-Chan. A/Bit 12-Chan. BNew 360 03D N1 Rotor Imbalance Angle Deg. +-180 9 1 5 Bit 11-Chan. A/Bit 12-Chan. BNew 361 03D LPT Rotor Imbalance Angle (737 only) Deg. +-180 9 1 5New 025 04D Load SEL Control na 204700 11 100 5New 156 04D L TANK FAULTS TBD TBD 5 See Att. 2New 157 04D R TANK FAULTS TBD TBD 5 See Att. 2New 160 04D C TANK FAULTS TBD TBD 5 See Att. 2New 161 04D A TANK FAULTS TBD TBD 5 See Att. 2New 241 04D FQIS SYSTEM DATA See Att. 6 500 1024 5 See Att. 6New 254 04D Actual Fuel Quan (teat) Lbs 262144 15 8 500 1000 9New 255 04D Fuel Quantity (gal) Gallons 32768 15 1 500 1000 46New 256 04D FUEL DISCRETES TBD TBD 5 See Att. 2New 262 04D T/U CAP-L TANK 1-4 PF 655.35 16 0.01 TBD TBD 5New 263 04D T/U CAP-L TANK 5-8 PF 655.35 16 0.01 TBD TBD 5New 264 04D T/U CAP - L TANK 9-12 PF 655.35 16 0.01 TBD TBD 5New 265 04D T/U CAP - L TANK 13-14 PF 655.35 16 0.01 TBD TBD 5New 266 04D T/U CAP - C TANK 1-4 PF 655.35 16 0.01 TBD TBD 5New 267 04D T/U CAP - C TANK 5-8 PF 655.35 16 0.01 TBD TBD 5New 270 04D T/U CAP - C TANK 9 PF 655.35 16 0.01 TBD TBD 5New 271 04D T/U CAP - A TANK 1-4 PF 655.35 16 0.01 TBD TBD 5New 272 04D T/U CAP - A TANK 5-8 PF 655.35 16 0.01 TBD TBD 5New 273 04D T/U CAP -A TANK 9-11 PF 655.35 16 0.01 TBD TBD 5New 274 04D T/U CAP - R TANK 1-4 PF 655.35 16 0.01 TBD TBD 5New 275 04D T/U CAP - R TANK 5-8 PF 655.35 16 0.01 TBD TBD 5New 276 04D T/U CAP - R TANK 9-12 PF 655.35 16 0.01 TBD TBD 5New 277 04D T/U CAP - R TANK 13-14 PF 655.35 16 0.01 TBD TBD 5New 310 04D COMP CAP-TANK PF 327.67 15 0.01 TBD TBD 5 See Att. 6 for SDI encodingNew 320 04D DENSITY-TANK LB/GAL 8.191 13 0.001 TBD TBD 5 See Att. 6 for SDI encodingNew 324 04D TANK VSO QUANTITY GALS 32767 15 1 TBD TBD 5 See Att. 6 for SDI encodingNew 326 04D UPLIFT QUANTITY LBS 1638300 14 100 TBD TBD 5New 327 04D UPLIFT DENSITY LB/GAL 8.181 13 0.001 TBD TBD 5New 341 04D I/O S/W REV 1&2 (1) 16 N/A TBD TBD 5New 342 04D S/W REV-TANK (1) 16 N/A TBD TBD 5 See Att. 6 for SDI encodingNew 344 04D FUEL DISCRETES 50 100 5 See Att. 2New 345 04D DISCRETES STATUS 1&3 100 200 5 See Att. 2New 346 04D CABLE CAP-HI-Z PF 65535 16 1 100 200 5 See Att. 6 for SDI encoding

SUP

PL

EM

EN

T 15 T

O A

RIN

C SP

EC

IFIC

AT

ION

429 - Page 5



TIMAX

TIREF NOTES

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

SUP

PL

EM

EN

T 15 T

O A

RIN

C SP

EC

IFIC

AT

ION

429 - Page 6



TIMAX

TIREF NOTES

New 155 0BB Maintenance Data #6 44New 156 0BB Maintenance Data #7 44New 157 0BB Maintenance Data #8 44New 160 0BB Maintenance Data #9 3New 276 0BB Discrete Data #5 3New 354 0BB Maintenance Data #5 44New 005 0D0 Engine Discrete 5 Bit 11-Chan. A/Bit 12-Chan. BNew 006 0D0 Engine Discrete 5New 073 0D0 Engine Oil Quantity US Pint 128 9 0.25 5 SDI1 = L/SD12 = RNew 173 0d0 Hydraulic Oil Quantity US Pint 128 9 0.25 5 SDI1 = L/SD12 = BNew 174 0D0 Hydraulic Oil Pressure PSI 4096 12 1 5 SDI1 = A/SD12 = BNew 316 0D0 Engine Oil Temperature Deg. C 2048 12 0.5 5 SDI1 = L/SD12 = RNew 317 0D0 Engine Oil Pressure PSI 4096 14 0.25 5 SDI1 = L/SD12 = RNew 344 0D0 N2 %RPM 256 13 0.03 5 SDI1 = L/SD12 = RNew 345 0D0 EGT Deg. C 2048 12 0.5 5 SDI1 = L/SD12 = RNew 346 0D0 N1 %RPM 256 13 0.03 5 SDI1 = L/SD12 = RNew 347 0D0 Fuel Flow Lb/Hr 32768 12 8 5 SDI1 = L/SD12 = RNew 353 0D0 Vibration Scalar 5.12 8 0.02 5 SDI1 = L/SD12 = RRevise 360 10A Throttle Rate of Change 16 9/9 31New 146 112 TACAN Control See Section 3.1.4 180 220 8New 222 112 TACAN Control Deg/180 +-180 12 0.05 180 220 8New 101 114 C/G Target % 164 8 0.01 100 200 40Revise 270 115 Stored TACAN Control Word 25 50 42 See Att. 2New 221 12C Indicated Angle of Attack (Ave.) Deg/180 +-180 12 0.05 31.3 62.5 45New 222 12C Indicated Angle of Attack (#1 left) Deg/180 +-180 12 0.05 31.3 62.5 45New 223 12C Indicated Angle of Attack (#1 right) Deg/180 +-180 12 0.05 31.3 62.5 45New 224 12C Indicated Angle of Attack (#2 left) Deg/180 +-180 12 0.05 31.3 62.5 45New 225 12C Indicated Angle of Attack (#2 right) Deg/180 +-180 12 0.05 31.3 62.5 45New 114 13A Ambient Pressure PSIA 32 14 0.002 100 200 14New 130 13A Inlet Temperature Deg. C 128 11 0.0625 100 200 14New 131 13A Inlet Pressure PSIA 32 13 0.004 100 200 14New 134 13A Throttle Lever Angle Deg/180 +-180 12 0.05 25 50 14New 254 13A N1 Cruise %N1 Nom 256 14 0.015 100 200 14New 255 13A N1 Climb %N1 Nom 256 14 0.015 100 200 14New 264 13A Burner Pressure PSIA 512 14 0.031 100 200 14New 340 13A N1 Take Off %N1 Nom 256 14 0.015 25 50 14New 341 13A N1 Reference %N1 Nom 256 14 0.015 25 50 14New 344 13A N2 Speed %RPM 256 14 0.015 25 50 14New 345 13A EGT Trimmed Deg. C 2048 12 0.5 25 50 14New 346 13A N1 Speed Actual %N1 Nom 256 14 0.015 25 50 14New 347 13A Fuel Flow Lb/Hr 32768 14 2 50 100 14New 364 13A N1 APR Rating %N1 Nom 256 14 0.015 100 200 14New 365 13A N1 Max Reverse %N1 Nom 256 14 0.015 100 200 14

SUP

PL

EM

EN

T 15 T

O A

RIN

C SP

EC

IFIC

AT

ION

429 -Page 7



TIMAX

TIREF NOTES

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

SUP

PL

EM

EN

T 15 T

O A

RIN

C SP

EC

IFIC

AT

ION

429 - Page 8



SUPPLEMENT 16

TO






SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 1 - Page 2


This Supplement introduces new label assignments,equipment IDs, and System Address Labels (SAL) toARINC Specification 429.


The material in Supplement 16 is integrated intoARINC Specification 429 to form an updated version ofthe standard. Changes introduced by Supplement 16 areidentified using change bars and are labeled by a “c-16” symbol in the margin.


This section presents a complete tabulation of thechanges and additions to the Specification introducedby this Supplement. Each change or addition is definedby the section number and the title currently employedin the Specification or by the section name and title thatwill be employed when the Supplement is eventuallyincorporated. In each case a brief description of thechange or addition is included.

ATTACHMENT 1-1 - LABEL CODES

Attachment 1-1 was updated to include new labelassignments, of these new assignments 35 labels wererevised and 3 label assignment deletions. A summary oflabel codes added by Supplement 16 is reproduced asAttachment 1-16 to this Supplement.

The deleted labels are:

LabelCode

PARAMETERREFATT

053 Track Angle Magnetic217 Average Static Pressure 36231 Total Air Temperature 36

ATTACHMENT 1-2 - EQUIPMENT CODES

Attachment 1-2 was updated to include new equipmentcodes:

EQID

EQUIPMENT TYPE REFATT

055 Multi-Mode Receiver (MMR) (755) 33056 GNSS Navigation Landing Unit (GNLU) (756) 3057 Cockpit Voice Recorder (CVR) (757) 24058 Communication Management Unit Mark 2 (758) 34060 GNSS Navigation Unit (GNU) (760) 33061 Satellite Terminal Unit (STU) (761) 11

0BBFlap Control Unit (B747-400)/Flap Slat Electronics Unit(B767-400)

23

108 Electronic Engine Control (EEC) Channel A (B737-700) 10109 Electronic Engine Control (EEC) Channel B (B737-700) 10122 Ground Auxiliary Power Unit (A320/319/321) 2012D Logic Drive Control Computer (B747/B767) 112E Cargo Control Logic Unit (B767) 112F Cargo Electronics Interface Unit (B767) 113B Audio Entertainment System (AES) Controller (Boeing) 1613F Camera Interface Unit (A340/B777) 25130 Load Management Unit (LMU) Airbus 21140 Supersonic Air Data Computer (Honeywell) 17142 ADS-B Link Display Processor Unit (LPDU) 27143 Vertical/Horizontal Gyro (Litton) 22

167 Air Traffic Service Unit (Airbus) 25

168Integrated Standby Instrument System (A340/330,A320/319/321)

20

169 Data Link Control and Display Unit (A340/330) 20200 Versatile Integrated Avionics Unit (B717/MD-10) 7201 Electronic Spoiler Control Unit (B717) 7202 Brake Control Unit (B717) 7203 Pneumatic Overheat Detection Unit (B717) 7204 Proximity Switch Electronics Unit (B717) 7205 APU Electronic Control Unit (B717) 7206 Aircraft Interface Unit (MD-10) 7207 Fuel Quantity Gauging Unit (MD-10) 7

ATTACHMENT 2 - DATA STANDARDS

Attachment 2 was updated to reflect new datastandards. The basis of the changes introduced inSupplement 16 are reproduced as Attachment 1-16 tothis Supplement.

ATTACHMENT 4 - INPUT/OUTPUT CIRCUITSTANDARDS

Text was added to identify the drawing as defining totalsystem characteristics.

ATTACHMENT 6 - GENERAL WORD FORMATSAND ENCODING EXAMPLES

The text describing Label 150 bit 11 was revised toreflect the contents of ARINC Characteristic 743A,GNSS Sensor.

The text describing Label 214 and Label 216 wasrevised to reflect the contents of ARINC Characteristic758, Communications Management Unit.

ATTACHMENT 8 - OUTPUT SIGNAL TIMINGTOLERANCES

The text was modified to define pulse rise and falltimes.



The following System Address Labels were added:

SALOCTALLABEL

SYSTEM REFATT

157 CVR 24210 FCMC Com A340-500/600 44211 FCMC Mon A340-500/600 44212 FCMC Int A340-500/600 44225 HUD 26241 APM-MMR 5242 MMR 5244 ILS 5245 MLS 5246 AHRS 19251 VDR #1252 VDR #2253 VDR #3310 GPWS 2311 GNLU 1 5312 GNLU 2 5313 GNLU 3 5314 GNU 1 5315 GNU 2 5316 GNU 3 5321 AUTOTHROTTLE COMPUTER 9322 FCC 1 9323 FCC 2 18324 FCC 3 18325 APU 13326 APU CONTROLLER 28327 Mode Control Panel (MCP) 45330 FMC 3 8331 ATC TRANSPONDER 12332 DADC 12

362Passenger Services System (PSS) 767-300,400

15

363 Cabin Service System (CSS) 747-400 15

364Audio Entertainment System (AES)Boeing

16

366 Multicast 43367 Bridge 43

APPENDIX E – GUIDELINES FOR LABELASSIGNMENTS

Labels 171, 172, 214 and 216 were removed from sparelabels (item 3).

Code No.

(Octal)Data

Eqpt.ID

(Hex)Parameter Units Range

SigBits

ResolutionMINTX

MAXTX

REFATT

001 BCD 056 Distance To Go The Same Parameters as the FMS EQ ID 002001 BCD 060 Distance To Go The Same Parameters as the FMS EQ ID 002002 BCD 056 Time To Go The Same Parameters as the FMS EQ ID 002002 BCD 060 Time To Go The Same Parameters as the FMS EQ ID 002012 BCD 056 Ground Speed The Same Parameters as the FMS EQ ID 002012 BCD 060 Ground Speed The Same Parameters as the FMS EQ ID 002017 BCD 055 Selected Runway Heading Degrees 0-359.9 4 0.1020 Discrete 06D Landing Gear Position Infor & System Status 90 100 37021 Discrete 06D Landing Gear Position Infor & System Status 90 100 37022 Discrete 06D Landing Gear Position Infor & System Status 90 100 37023 Discrete 06D Landing Gear Position Infor & System Status 90 100 37024 Discrete 06D Landing Gear Position Infor & System Status 90 100 37027 BCD 056 TACAN Selected Course The Same Parameters as the FMS EQ ID 002027 BCD 060 TACAN Selected Course (Bcd) The Same Parameters as the FMS EQ ID 002033 BCD 055 Landing System Mode/Frequency033 BCD 056 ILS Frequency The Same Parameters as the FMS EQ ID 002033 BCD 060 ILS Frequency The Same Parameters as the FMS EQ ID 002034 BCD 056 VOR/ILS Frequency The Same Parameters as the FMS EQ ID 002034 BCD 060 VOR/ILS Frequency #1 The Same Parameters as the FMS EQ ID 002035 BCD 055 Paired DME Frequency MHz 1008-135.9 4 0.05035 BCD 056 DME Frequency The Same Parameters as the FMS EQ ID 002035 BCD 060 DME Frequency #1 The Same Parameters as the FMS EQ ID 002036 BCD 055 MLS Channel Selection 500-600 3 1036 BCD 056 MLS Frequency Channel The Same Parameters as the FMS EQ ID 002036 BCD 060 MLS Frequency/Channel The Same Parameters as the FMS EQ ID 002041 BCD 056 Set Latitude The Same Parameters as the FMS EQ ID 002041 BCD 060 Set Latitude The Same Parameters as the FMS EQ ID 002042 BCD 056 Set Longitude The Same Parameters as the FMS EQ ID 002042 BCD 060 Set Longitude The Same Parameters as the FMS EQ ID 002043 BCD 056 Set Magnetic Heading The Same Parameters as the FMS EQ ID 002043 BCD 060 Set Magnetic Heading The Same Parameters as the FMS EQ ID 002052 BNR 004 Body Pitch Accel Deg/Sec2 ± 64 15 0.002 50 Hz 117 Hz052 BNR 038 Body Pitch Accel Deg/Sec2 ± 64 15 0.002 50 Hz 117 Hz053 BCD 004 Track Angle Magnetic Degree 1 3 1 250 500053 BNR 004 Body Roll Accel Deg/Sec2 ± 64 15 0.002 50 Hz 117 Hz053 BNR 038 Body Roll Accel Deg/Sec2 ± 64 15 0.002 50 Hz 117 Hz054 BNR 004 Body Yaw Accel Deg/Sec2 ± 64 15 0.002 50 Hz 117 Hz054 BNR 038 Body Yaw Accel Deg/Sec2 ± 64 15 0.002 50 Hz 117 Hz056 BCD 056 ETA (Active Waypoint) The Same Parameters as the FMS EQ ID 002056 BCD 060 ETA (Active Waypoint) The Same Parameters as the FMS EQ ID 002061 BNR 00B Pseudo Range Meters ±268435456 20 256 200 1200061 BNR 056 ACMS Information The Same Parameters as the FMS EQ ID 002061 BNR 060 ACMS Information The Same Parameters as the FMS EQ ID 002062 BNR 00B Pseudo Range Fine Meters 256 11 0.125 200 1200062 BNR 056 ACMS Information The Same Parameters as the FMS EQ ID 002062 BNR 060 ACMS Information The Same Parameters as the FMS EQ ID 002

SUP

PL

EM

EN

T 16 T

O A

RIN

C SP

EC

IFIC

AT

ION

429 PA

RT

1– Page 4

AT

TA

CH

ME

NT

1-16SU

PP

LE

ME

NT

16 UP

DA

TE

S TO

LA

BE

L C

OD

ES

Code No.(Octal)

DataEqpt.

ID(Hex)

Parameter Units RangeSigBits

ResolutionMINTX

MAXTX

REFATT

063 BNR 00B Range Rate M/S ±4096 20 0.0039 200 1200063 BNR 056 ACMS Information The Same Parameters as the FMS EQ ID 002063 BNR 060 ACMS Information The Same Parameters as the FMS EQ ID 002064 BNR 00B Delta Range Meters ±4096 20 0.0039 200 1200065 BNR 00B SV Position X Meters ±67108864 20 64 200 1200066 BNR 00B SV Position X Fine Meters 64 14 0.0039 200 1200070 BNR 00B SV Position Y Meters ±67108864 20 64 200 1200070 BNR 056 Reference Airspeed (Vref) The Same Parameters as the FMS EQ ID 002070 BNR 060 Reference Airspeed (Vref) The Same Parameters as the FMS EQ ID 002071 BNR 00B SV Position Y Fine Meters 64 14 0.0039 200 1200072 BNR 00B SV Position Z Meters ±67108864 20 64 200 1200073 BNR 00B SV Position Z Fine Meters 64 14 0.0039 200 1200074 BNR 00B UTC Measure Time Seconds 10.0 20 9.536743µs 200 1200074 BNR 056 Zero Fuel Weight The Same Parameters as the FMS EQ ID 002074 BNR 060 Zero Fuel Weight The Same Parameters as the FMS EQ ID 002074 BNR 114 Zero Fuel Weight Pounds 1310680 15 40 100 400 37075 Discrete 008 Maximum Hazard Alert Level Output075 BNR 114 Aircraft Gross Weight Pounds 1310680 15 40 100 200 37076 BNR 00B GNSS Altitude (Msl) Feet ±131072 20 0.125 200 1200076 Discrete 008 Hazard Azimuth Output076 BNR 114 Aircraft Longitudinal Center Of Gravity Percent 163.83% 14 0.01% 100 200 37077 Discrete 008 Hazard Range Output077 BNR 056 Target Airspeed The Same Parameters as the FMS EQ ID 002077 BNR 060 Target Airspeed The Same Parameters as the FMS EQ ID 002077 BNR 114 Zero Fuel Center Of Gravity Percent 163.83% 14 0.01% 100 200 37100 BNR 056 Selected Course #1 The Same Parameters as the FMS EQ ID 002100 BNR 060 Selected Course #1 The Same Parameters as the FMS EQ ID 002101 BNR 00B HDOP N/A 1024 15 0.031 200 1200102 BNR 00B VDOP N/A 1024 15 0.031 200 1200102 BNR 056 Selected Altitude The Same Parameters as the FMS EQ ID 002102 BNR 060 Selected Altitude The Same Parameters as the FMS EQ ID 002103 BNR 00B GNSS Track Angle Degrees ±108° 15 0.0055° 200 1200103 BNR 056 Selected Airspeed The Same Parameters as the FMS EQ ID 002103 BNR 060 Selected Airspeed The Same Parameters as the FMS EQ ID 002104 BNR 056 Selected Vertical Speed The Same Parameters as the FMS EQ ID 002104 BNR 060 Selected Vertical Speed The Same Parameters as the FMS EQ ID 002105 BNR 055 Selected Runway Heading Degrees ± 180 11 0.1105 BNR 056 Selected Runway Heading The Same Parameters as the FMS EQ ID 002105 BNR 060 Selected Runway Heading The Same Parameters as the FMS EQ ID 002106 BNR 060 Selected Mach The Same Parameters as the FMS EQ ID 002106 BNR 056 Selected Mach The Same Parameters as the FMS EQ ID 002107 BNR 056 Selected Cruise Altitude The Same Parameters as the FMS EQ ID 002107 BNR 060 Selected Cruise Altitude The Same Parameters as the FMS EQ ID 002110 BNR 00B GNSS Latitude Degrees ±108° 20 0.000172° 200 1200111 BNR 00B GNSS Longitude Degrees ±108° 20 0.000172° 200 1200112 BNR 00B GNSS Ground Speed Knots 4096 15 0.125 200 1200114 BNR 056 Desired Track The Same Parameters as the FMS EQ ID 002

SUP

PL

EM

EN

T 16 T

O A

RIN

C SP

EC

IFIC

AT

ION

429 PA

RT

1- Page 5

AT

TA

CH

ME

NT

1-16SU

PP

LE

ME

NT

16 UP

DA

TE

S TO

LA

BE

L C

OD

ES

Code No.(Octal)

DataEqpt.

ID(Hex)


ResolutionMINTX

MAXTX

REFATT

114 BNR 060 Desired Track The Same Parameters as the FMS EQ ID 002115 BNR 056 Waypoint Bearing The Same Parameters as the FMS EQ ID 002115 BNR 060 Waypoint Bearing The Same Parameters as the FMS EQ ID 002116 BNR 00B Horizontal GLS Deviation Rectilinear Feet ± 24000 18 .00915 100 32116 BNR 055 Horizontal GLS Deviation Rectilinear Feet ± 24000 18 00915 100 32116 BNR 056 Cross Track Distance The Same Parameters as the FMS EQ ID 002116 BNR 060 Cross Track Distance The Same Parameters as the FMS EQ ID 002117 BNR 00B Vertical GLS Deviation Rectilinear Feet ± 1024 14 .0625 100 32117 BNR 055 Vertical GLS Deviation Rectilinear Feet ± 1024 14 .0625 100 32117 BNR 056 Vertical Deviation The Same Parameters as the FMS EQ ID 002117 BNR 060 Vertical Deviation The Same Parameters as the FMS EQ ID 002120 BNR 00B GNSS Latitude Fine Degrees 0.000172° 11 8.38-E-8° 200 1200120 BNR 056 Range to Altitude The Same Parameters as the FMS EQ ID 002120 BNR 060 Range To Altitude The Same Parameters as the FMS EQ ID 002121 BNR 00B GNSS Longitude Fine Degrees 0.000172° 11 8.38-E-8° 200 1200121 BNR 056 Horizontal Command Signal The Same Parameters as the FMS EQ ID 002121 BNR 060 Horizontal Command Signal The Same Parameters as the FMS EQ ID 002122 BNR 056 Vertical Command Signal The Same Parameters as the FMS EQ ID 002122 BNR 060 Vertical Command Signal The Same Parameters as the FMS EQ ID 002124 Discrete 00B Digital Time Mark - 200 1200125 BCD 00B UTC Hr:Min 23:59.9 5 0.1 Min 200 1200125 BCD 002 Universal Coordinate Time Hr-Min 0-23.59.9 4 0.1 100 200125 BCD 056 Universal Coordinated Time (UTC) The Same Parameters as the FMS EQ ID 002125 BCD 060 Universal Coordinated Time (UTC) The Same Parameters as the FMS EQ ID 002126 BNR 056 Vertical Deviation (Wide) The Same Parameters as the FMS EQ ID 002126 BNR 060 Vertical Deviation (Wide) The Same Parameters as the FMS EQ ID 002130 BNR 00B Aut Horiz Integ Limit NM 16 17 1.2E-4 200 1200133 BNR 00B Aut Vert Integ Limit Feet 32, 768 18 0.125 200 1200136 BNR 00B Vertical Figure Of Merit Feet 32, 768 18 0.125 200 1200137 BNR 140 Flap Angle Degrees 180 12 0.05 62.5 200 36140 BNR 00B UTC Fine Seconds 1 20 0.953674µs 200 1200140 Discrete 114 Pump Contactor States 37141 BNR 00B UTC Fine Fractions Seconds 0.9536743µs 10 0.9313225ns 200 1200141 Discrete 114 Pump Contactor and Pushbutton States 37142 Discrete 114 Pump Push Button and LP Switch State 37143 Discrete 114 Pump LP Switch State and FCMC Commands 37144 Discrete 114 Valve Feedback 37145 Discrete 114 Valve Feedback 37146 Discrete 114 Valve Feedback 37147 Discrete 114 Valve Feedback 37150 BNR 00B UTC Hr:Min:S ±23:59:59 17 1.0 sec 200 1200150 BNR 056 Universal Coordinated Time The Same Parameters as the FMS EQ ID 002150 BNR 060 Universal Coordinated Time The Same Parameters as the FMS EQ ID 002150 Discrete 114 FCMC Valve Commands 37151 BNR 055 MLS AZ Deviation mV ± 2400 15 0.0732151 BNR 056 Localizer Bearing (True) The Same Parameters as the FMS EQ ID 002

SUP

PL

EM

EN

T 16 T

O A

RIN

C SP

EC

IFIC

AT

ION

429 PA

RT

1- Page 6

AT

TA

CH

ME

NT

1-16SU

PP

LE

ME

NT

16 UP

DA

TE

S TO

LA

BE

L C

OD

ES

Code No.(Octal)

DataEqpt.

ID(Hex)


ResolutionMINTX

MAXTX

REFATT

151 BNR 060 Localizer Bearing (True) The Same Parameters as the FMS EQ ID 002151 Discrete 114 FCMC Valve Commands 37152 BNR 055 MLS GP Deviation mV ± 2400 15 0.0732

152 Discrete 114Overhead Panel Switch/ Pushbutton & RefuelPanel Battery Power Supply Switch States

37

153 BNR 055 MLS Selected Azimuth Degrees 0-359 9 1153 Discrete 114 Level States 37154 BNR 055 MLS Max Selectable GP Degrees ±51.1 9 1154 BNR 056 Runway Heading (True) The Same Parameters as the FMS EQ ID 002154 BNR 060 Runway Heading (True) The Same Parameters as the FMS EQ ID 002

154 Discrete 114Level States and Low Warning and TransferIndications

37

155 BNR 055 MLS Selected Glide Path Degrees ±51.1 9 0.01155 Discrete 114 XFR Pump Faults & Wing Imbalance Warning 37156 BNR 055 MLS Basic Data Wd 1 N/A N/A N/A N/A156 Discrete 114 Refuel Panel Switch States 37157 SAL System Address Label For CVR 24157 BNR 055 MLS Basic Data Wd 2 N/A N/A N/A N/A157 BCD 114 Trim Tank Probe Capacitance pf 0-400 14 0.1 37160 BNR 055 MLS Basic Data Wd 3 N/A N/A N/A N/A160 Discrete 114 Valve Feedback 37161 BNR 055 MLS Basic Data Wd 4 N/A N/A N/A N/A161 Discrete 114 Indicated Pump Status 37162 BNR 055 MLS Basic Data Wd 5 N/A N/A N/A N/A162 Discrete 114 Indicated Pump Status 37162 BNR 140 Density Altitude Feet 131072 16 2 250 500 36163 BNR 055 MLS Basic Data Wd 6 N/A N/A N/A N/A163 Discrete 114 Indicated Pump Status 37164 BNR 055 MLS ABS GP Angle Degrees ± 41 15 0.00125164 Discrete 114 Indicated Pump Status 37165 BNR 00B Vertical Velocity Feet/Min ±32768 15 1.0 200 1200165 BNR 055 MLS ABS Azimuth Angle Degrees ± 82 16 0.00125165 Discrete 114 Indicated Valve Status 37166 BNR 00B North/South Velocity Knots ±4096 15 0.125 200166 Discrete 114 Indicated Valve Status 37

167 BNR 002EPU Estimate Position Uncertainty/ (ANP)Actual Navigation Performance

NM 0-128 16 0.00195

167 Discrete 114 Indicated Valve Status 37170 Discrete 114 Wing Imbalance And FQI Failure Warning 37171 BNR 002 RNP Reduced Navigation Performance NM 0-128 16 0.001953171 BNR 056 Current RNP The Same Parameters as the FMS EQ ID 002171 BNR 060 Current RNP The Same Parameters as the FMS EQ ID 002172 Subsystem Identifier173 BNR 055 Localizer Deviation DDM ± 0.4 12 0.0001174 BNR 00B East/West Velocity Knots ±4096 15 0.125 200 1200174 BNR 055 Glide Slope Deviation DDM ± 0.8 12 0.0002

SUP

PL

EM

EN

T 16 T

O A

RIN

C SP

EC

IFIC

AT

ION

429 PA

RT

1- Page 7

AT

TA

CH

ME

NT

1-16SU

PP

LE

ME

NT

16 UP

DA

TE

S TO

LA

BE

L C

OD

ES

Code No.(Octal)

DataEqpt.

ID(Hex)


ResolutionMINTX

MAXTX

REFATT

176 BNR 00B GLONASS Satellite Deselection W #1 17 31176 BNR 0AD Static Pressure Left, Uncorrected, mb mb 2048 18 0.008 20 200 36176 BNR 038 Left Static Pressure Uncorrected, mb mb 2048 18 0.008 20 200 36176 BNR 114 Left Outer Tank Fuel Temp & Advisory Warn Degree C ±512 11 0.025 37177 BNR 00B GLONASS Satellite Deselection W #2 17 31177 BNR 0AD Static Pressure Right, Uncorrected, mb mb 2048 18 0.008 20 200 36177 BNR 038 Right Static Pressure, Uncorrected, mb mb 2048 18 0.008 20 200 36177 BNR 055 Distance To Runway Threshold Nmiles 1024 16 0.007812177 BNR 114 Inner Tank 1 Fuel Temp & Advisory Warning Degree C ±512 11 0.025 37200 BCD 056 Drift Angle The Same Parameters as the FMS EQ ID 002200 BCD 060 Drift Angle The Same Parameters as the FMS EQ ID 002200 BNR 114 Inner Tank 2 Fuel Temp & Advisory Warning Degree C ±512 11 0.025 37201 BNR 114 Inner Tank 3 Fuel Temp & Advisory Warning Degree C ±512 11 0.025 37201 BNR 140 Mach Maximum Operation (Mmo) Mach 4.096 12 0.001 62.5 125 36201 BNR 142 Projected Future Latitude Degrees ± 180 20 0.000172 150 400 27202 BNR 114 Inner Tank 4 Fuel Temp & Advisory Warning Degree C ±512 11 0.025 37202 BNR 140 Mach Rate M/minute 4.096 12 0.001 62.5 125 36202 BNR 142 Projected Future Latitude Fine Degrees .000172 11 2-E-32 Cir 150 400 27203 BNR 114 Trim Tank Fuel Temp & Advisory Warning Degree C ±512 11 0.025 37203 BNR 140 Altitude Feet 131072 17 1 31.25 62.5 36204 BNR 056 Baro Altitude The Same Parameters as the FMS EQ ID 002204 BNR 060 Baro Altitude The Same Parameters as the FMS EQ ID 002204 BNR 114 Right Outer Tank Fuel Temp & Advisory

WarningDegree C ±512 11 0.025 37

204 BNR 140 Baro Corrected Altitude Feet 131072 17 1 31.25 62.5 36205 BNR 140 Mach Mach 4.096 16 0.0000625 62.5 125 36206 BNR 056 Computed Airspeed The Same Parameters as the FMS EQ ID 002206 BNR 060 Computed Airspeed The Same Parameters as the FMS EQ ID 002206 BNR 140 Computed Airspeed (CAS) Knots 1024 14 0.0625 62.5 125 36207 BNR 140 Airspeed Maximum Operating (VMO) Knots 1024 12 .025 62.56 125 36210 BNR 140 True Airspeed Knots 2048 15 0.0625 62.5 125 36210 SAL FCMC Com A340-500/600 44211 BNR 0AD Total Air Temperature Indicated Degree C 512 12 0.125 250 500 36211 BNR 140 Total Air Temp (TAT) Degree C 512 11 0.25 250 500 36211 BNR 142 Projected Future Longitude Degrees ± 180 20 0.000172 150 400 27211 SAL FCMC M on A340-500/600 44212 BNR 056 Alititude Rate The Same Parameters as the FMS EQ ID 002212 BNR 060 Alititude Rate The Same Parameters as the FMS EQ ID 002212 BNR 140 Altitude Rate Ft/Min 32768 11 16 31.25 62.5 36212 BNR 142 Projected Future Longitude Fine Degrees .000172 11 2E -32 Cir 150 400 27212 SAL FCMC Int A340-500/600 44213 BNR 140 Static Air Temp (SAT) Degree C 512 11 0.25 250 500 36213 BNR 142 Vertical Time Interval Minute 265 min 10 .25 mile 500 2000 27215 BNR OAD Impacted Pressure, Uncorrected, mb mb 512 16 0.008 20 40 36215 BNR O38 Impacted Pressure, Uncorrected, mb mb 512 14 0.03125 62.5 125 36215 BNR 006 Impacted Pressure, Uncorrected, mb mb 512 14 0.03125 62.5 125 36

SUP

PL

EM

EN

T 16 T

O A

RIN

C SP

EC

IFIC

AT

ION

429 PA

RT

1-Page 8

AT

TA

CH

ME

NT

1-16SU

PP

LE

ME

NT

16 UP

DA

TE

S TO

LA

BE

L C

OD

ES

Code No.(Octal)

DataEqpt.

ID(Hex)


ResolutionMINTX

MAXTX

REFATT

215 BNR 140 Impact Pressure Subsonic mb 512 14 0.03125 62.5 125 36217 BNR 0AD Average Static Pressure mb 2048 18 0.008 20 200 36217 BNR 002 Geometric Vertical Rate Ft/Min 20000 11 16217 BNR 006 Static Pressure, Corrected (In. Hg) Inches Hg 64 16 0.001 20 200 36217 BNR 038 Static Pressure, Average, Corrected (In. Hg) Inches Hg 64 16 0.001 20 200 36217 BNR 140 Static Pressure Corrected (In. Hg) Inches Hg 64 16 0.001 62.5 125 36220 056 MCDU #1 Address Label The Same Parameters as the FMS EQ ID 002220 060 MCDU #1 Address Label The Same Parameters as the FMS EQ ID 002220 BNR 140 Baro Corrected Altitude #2 Feet 131072 17 1 31.25 62.5 36221 056 MCDU #2 Address Label The Same Parameters as the FMS EQ ID 002221 060 MCDU #2 Address Label The Same Parameters as the FMS EQ ID 002221 BNR 140 Angle Of Attack Indicated Average Degrees 180 12 0.05 31.25 62.5 36222 056 MCDU #3 Address Label The Same Parameters as the FMS EQ ID 002222 060 MCDU #3 Address Label The Same Parameters as the FMS EQ ID 002222 BNR 140 Angle Of Attack, Indicated #1 Left Degrees 180 12 0.05 31.5 62.5 36223 056 Printer #1 Address Label The Same Parameters as the FMS EQ ID 002223 060 Printer #1 Address Label The Same Parameters as the FMS EQ ID 002223 BNR 140 Angle Of Attack, Indicated #1 Right Degrees 180 12 0.05 31.5 62.5 36224 056 Printer #2 Address Label The Same Parameters as the FMS EQ ID 002224 060 Printer #2 Address Label The Same Parameters as the FMS EQ ID 002224 BNR 140 Angle Of Attack, Indicated #2 Left Degrees 180 12 0.05 31.5 62.5 36225 SAL System Address Label For HUD 26225 BNR 056 Minimum Maneuvering Air Speed The Same Parameters as the FMS EQ ID 002225 BNR 060 Minimum Maneuvering Air Speed The Same Parameters as the FMS EQ ID 002225 BNR 140 Angle Of Attack, Indicated #2 Right Degrees 180 12 0.05 31.5 62.5 36226 00B Data Loader Responses 200 1200227 Discrete 019 CFDS Bite Command Summary For HFDR227 Discrete 053 CFDS Bite Command Word For HFDU230 BCD 114 Left Outer Probes Capacitance pf 0-400 14 0.1 37231 BCD 0AD Total Air Temperature Degree C 512 12 20 200 36231 BCD 114 Inner 2 Tank Probe Capacitance pf 0-400 14 0.1 37232 File

Format002 Active Intent Data Block

232 DISC 055 GLS Airport ID232 Discrete 056 Active Intent Data Block232 060 Active Intent Data Block The Same Parameters as the FMS EQ ID 002232 BCD 114 Inner 4 Tank Probe Capacitance pf 0-400 14 0.1 37233 BNR 056 ACMS Information The Same Parameters as the FMS EQ ID 002233 BNR 060 ACMS Information The Same Parameters as the FMS EQ ID 002233 BCD 114 Right Outer Probe Capacitance pf 0-400 14 0.1 37234 BNR 056 ACMS Information The Same Parameters as the FMS EQ ID 002234 BNR 060 ACMS Information The Same Parameters as the FMS EQ ID 002235 BNR 056 ACMS Information The Same Parameters as the FMS EQ ID 002235 BNR 060 ACMS Information The Same Parameters as the FMS EQ ID 002236 BNR 056 ACMS Information The Same Parameters as the FMS EQ ID 002236 BNR 060 ACMS Information The Same Parameters as the FMS EQ ID 002

SUP

PL

EM

EN

T 16 T

O A

RIN

C SP

EC

IFIC

AT

ION

429 PA

RT

1- Page 9

AT

TA

CH

ME

NT

1-16SU

PP

LE

ME

NT

16 UP

DA

TE

S TO

LA

BE

L C

OD

ES

Code No.(Octal)

DataEqpt.

ID(Hex)


ResolutionMINTX

MAXTX

REFATT

237 BNR 00B Horizontal Uncertainty Level Nm 16 17 0.000122 1200 29237 BNR 002 ACMS Information237 BNR 056 ACMS Information The Same Parameters as the FMS EQ ID 002237 BNR 060 ACMS Information The Same Parameters as the FMS EQ ID 002241 SAL System Address Label For APM-MMR 5241 BNR 056 Min. Airspeed for Flap Extension The Same Parameters as the FMS EQ ID 002241 BNR 060 Min. Airspeed for Flap Extension The Same Parameters as the FMS EQ ID 002241 BNR 140 Angle Of Attack, Corrected Degrees 180 12 0.05 31.5 62.5 36242 SAL System Address Label for MMR 5242 BNR 0AD Total Pressure, Uncorrected, mb 36

242File

Format002 Modified Intent Data Block

242 BNR 056 Modified Intent Data Block The Same Parameters as the FMS EQ ID 002242 060 Modified Intent Data Block The Same Parameters as the FMS EQ ID 002242 BNR 140 Total Pressure mb 2048 16 0.03125 62.5 125 36243 DISC 055 GLS Runway Selection244 SAL System Address Label for ILS 5244 BNR 140 Angle Of Attack, Normalized Ratio 2 11 0.001 62.5 125 36245 SAL System Address Label For MLS 5245 BNR 0AD Average Static Pressure mb, Uncorrected mb 2048 18 0.008 20 200 36245 BNR 038 Average Static Pressure mb, Uncorrected 36245 BNR 056 Minimum Airspeed The Same Parameters as the FMS EQ ID 002245 BNR 060 Minimum Airspeed The Same Parameters as the FMS EQ ID 002245 BNR 140 Static Pressure, Uncorrected mb 2048 16 0.03125 62.5 125 36246 SAL System Address Label for AHRS 19246 BNR 038 Average Static Pressure mb, Corrected 36246 BNR 056 General Max Speed (Vcmax) The Same Parameters as the FMS EQ ID 002246 BNR 060 General Max Speed (Vcmax) The Same Parameters as the FMS EQ ID 002246 BNR 140 Static Pressure, Corrected mb 2048 16 0.03125 62.5 125 36247 BNR 00B Horizontal Figure Of Merit NM 16 18 6.1 E-5 200 1200247 BNR 056 Control Minimum Speed (Vcmin) The Same Parameters as the FMS EQ ID 002247 BNR 060 Control Minimum Speed (Vcmin) The Same Parameters as the FMS EQ ID 002247 BNR 114 Fuel On Board Pounds 655320 13 40 37247 BNR 140 Airspeed Minimum Vmc Knots 512 11 0.25 62.5 125 36250 BNR 0AD Indicated Side Slip Angle or AOS Deg/180 ±180 14 0.01 31.3 200 36250 BNR 114 Preselected Fuel Quantity Pounds 655320 13 40 37251 SAL System Address Label VDR #1252 SAL System Address Label VDR #2253 SAL System Address Label VDR #3254 Discrete 055 GBAS ID 200 41254 BNR 140 Altitude Rate Ft/Min 131072 13 16 31.25 62.5 36255 Discrete 055 GBAS Airport ID 200 42255 BNR 140 Impact Pressure mb 4096 17 0.03125 62.5 125 36256 BLOCK 055 MLS Station ID #1256 BNR 056 Time For Climb The Same Parameters as the FMS EQ ID 002256 BNR 060 Time For Climb The Same Parameters as the FMS EQ ID 002

SUP

PL

EM

EN

T 16 T

O A

RIN

C SP

EC

IFIC

AT

ION

429 PA

RT

1- Page 10

AT

TA

CH

ME

NT

1-16SU

PP

LE

ME

NT

16 UP

DA

TE

S TO

LA

BE

L C

OD

ES

Code No.(Octal)

DataEqpt.

ID(Hex)


ResolutionMINTX

MAXTX

REFATT

256 BNR 114 Left Outer Tank Fuel Quantity Pounds 131068 15 4 37256 BNR 140 Equivalent Airspeed Knots 1024 14 0.0625 62.5 125 36257 BLOCK 055 MLS Station ID #2257 BNR 056 Time For Descent The Same Parameters as the FMS EQ ID 002257 BNR 060 Time For Descent The Same Parameters as the FMS EQ ID 002257 BNR 114 Inner Tank 1 Fuel Quantity Pounds 131068 15 4 37257 BNR 140 Total Pressure (High Range) mb 4096 17 0.03125 62.5 125 36260 BCD 00B Date dd:Mo:Yr dd:mm:yr 6 1 day 200 1200260 BCD 056 Date/Flight Leg The Same Parameters as the FMS EQ ID 002260 BCD 060 Date/Flight Leg The Same Parameters as the FMS EQ ID 002260 BNR 114 Collector Cell 1 and 2 Fuel Quantity Pounds 131068 15 4 37261 BCD 056 Flight Number (BCD) The Same Parameters as the FMS EQ ID 002261 BCD 060 Flight Number (BCD) The Same Parameters as the FMS EQ ID 002261 BNR 114 Fuel On Board At Engine Start Pounds 131068 15 4 37262 BNR 056 Documentary Data The Same Parameters as the FMS EQ ID 002262 BNR 060 Documentary Data The Same Parameters as the FMS EQ ID 002262 BNR 114 Center Tank Fuel Quantity Pounds 131068 15 4 37263 BLOCK 055 Ground Station/Approach263 BNR 056 Min. Airspeed For Flap Retraction The Same Parameters as the FMS EQ ID 002263 BNR 060 Min. Airspeed For Flap Retraction The Same Parameters as the FMS EQ ID 002263 BNR 114 Collector Cell 3 And 4 Fuel Quantity Pounds 131068 15 4 37264 BLOCK 055 Ground Station/Approach264 BNR 056 Time To Touchdown The Same Parameters as the FMS EQ ID 002264 BNR 060 Time To Touchdown The Same Parameters as the FMS EQ ID 002264 BNR 114 Spare 37265 BNR 056 Min. Buffet Airspeed The Same Parameters as the FMS EQ ID 002265 BNR 060 Min. Buffet Airspeed The Same Parameters as the FMS EQ ID 002265 BNR 114 Inner Tank 3 Fuel Quantity Pounds 131068 15 4 37266 BNR 114 Inner Tank 2 Fuel Quantity Pounds 131068 15 4 37267 BNR 056 Max. Maneuver Airspeed The Same Parameters as the FMS EQ ID 002267 BNR 060 Max. Maneuver Airspeed The Same Parameters as the FMS EQ ID 002267 BNR 114 Inner Tank 4 Fuel Quantity Pounds 131068 15 4 37

270 Discrete 024MU Output Data Word, Communication LinkStatus

270 Discrete 039 MCDU Normal Discrete Word270 Discrete 041 SDU To ACARS MU/CMU Status Word270 Discrete 050 VDR Status Word270 Discrete 053 HFDL Status Word270 DISC 055 MLS Discrete270 Discrete 056 Status Discretes270 Discrete 058 Output Status Word #1270 DISC 060 Intent Status270 DISC 060 Status Discretes270 DISC 060 Discrete Data #1270 Discrete 114 Unusable, and Empty Warning 37270 Discrete 140 Discrete Data # 1 250 500 36

SUP

PL

EM

EN

T 16 T

O A

RIN

C SP

EC

IFIC

AT

ION

429 PA

RT

1- Page 11

AT

TA

CH

ME

NT

1-16SU

PP

LE

ME

NT

16 UP

DA

TE

S TO

LA

BE

L C

OD

ES

Code No.(Octal)

DataEqpt.

ID(Hex)


ResolutionMINTX

MAXTX

REFATT

270 Discrete 142 Aircraft Category (Disc Data 1) 5000 15000 27

271 Discrete 041 SDU To ACARS MU/CMU Join /LeaveMessage

271 DISC 055 MMR Discrete271 Discrete 056 Discrete Data #2271 DISC 060 Discrete Data #2271 Discrete 114 Fuel Transfer Indication 37271 Discrete 140 Discrete Data # 2 250 500 36271 Discrete 142 Altitude Filter Limits (Disc Data 2) 500 2000 27272 Discrete 053 HFDL Slave (Disc Data 3) 35272 Discrete 056 Discrete Data #3272 DISC 060 Discrete Data #3272 Discrete 114 Fuel Transfer Indication 37272 Discrete 140 Discrete Data # 3 250 500 36273 DIS 00B GNSS Sensor Status N/A 200 1200273 DISC 055 GNSS Status273 Discrete 114 Memos And Status 37274 Discrete 114 Fuel Transfer Indications 37275 Discrete 038 IR Discrete Word #2275 Discrete 056 Discrete Data #6275 DISC 060 Discrete Data #6275 Discrete 114 Miscellaneous Warning 37276 Discrete 024 MU Output Data Word, Pin Program Status

276 Discrete 041SDU To EICAS/ECAM/EDU For DualSATCOM

276 Discrete 050 VDR Mode Command276 Discrete 056 Discrete Data #7276 Discrete 058 Output Status Word #2276 DISC 060 Discrete Data #7276 Discrete 114 Miscellaneous Discrete 37277 Discrete 004 IRS Maintenance Discrete277 Discrete 114 Fuel Transfer and CG Status 37301 056 Application Dependent The Same Parameters as the FMS EQ ID 002301 060 Application Dependent302 056 Application Dependent The Same Parameters as the FMS EQ ID 002302 060 Application Dependent303 056 Application Dependent The Same Parameters as the FMS EQ ID 002303 060 Application Dependent310 SAL System Address Label for GPWS 2310 BNR 056 Present Position Latitude The Same Parameters as the FMS EQ ID 002310 BNR 060 Present Position Latitude The Same Parameters as the FMS EQ ID 002310 BNR 114 Right Outer Tank Fuel Quantity Pounds 131068 15 4 37311 SAL System Address Label for GNLU 1 5311 BNR 056 Present Position Longitude The Same Parameters as the FMS EQ ID 002311 BNR 060 Present Position Longitude The Same Parameters as the FMS EQ ID 002311 BNR 114 Trim Tank Fuel Quantity Pounds 131068 15 4 37

SUP

PL

EM

EN

T 16 T

O A

RIN

C SP

EC

IFIC

AT

ION

429 PA

RT

1- Page 12

AT

TA

CH

ME

NT

1-16SU

PP

LE

ME

NT

16 UP

DA

TE

S TO

LA

BE

L C

OD

ES

Code No.(Octal)

DataEqpt.

ID(Hex)


ResolutionMINTX

MAXTX

REFATT

312 SAL System Address Label for GNLU 2 5312 BNR 056 Ground Speed The Same Parameters as the FMS EQ ID 002312 BNR 060 Ground Speed The Same Parameters as the FMS EQ ID 002312 BNR 114 Additional Center Tank (Act 1) Fuel Quantity Pounds 131068 15 4 37313 SAL System Address Label For GNLU 3 5313 BNR 056 Track Angle True The Same Parameters as the FMS EQ ID 002313 BNR 060 Track Angle True The Same Parameters as the FMS EQ ID 002313 BNR 114 Additional Center Tank (Act 2) Fuel Quantity Pounds 131068 15 4 37314 SAL System Address Label For GNU 1 5314 BNR 114 Rear Center Tank (RCT) Fuel Quantity Pounds 131068 15 4 37315 SAL System Address Label For GNU 2 5315 BNR 056 Wind Speed The Same Parameters as the FMS EQ ID 002315 BNR 060 Wind Speed The Same Parameters as the FMS EQ ID 002316 SAL System Address Label For GNU 3 5316 BNR 056 Wind Direction (True) The Same Parameters as the FMS EQ ID 002316 BNR 060 Wind Direction (True) The Same Parameters as the FMS EQ ID 002317 BNR 056 Track Angle Magnetic The Same Parameters as the FMS EQ ID 002317 BNR 060 Track Angle Magnetic The Same Parameters as the FMS EQ ID 002320 BNR 05A Fuel Quantity Act 3 4320 BNR 056 Magnetic Heading The Same Parameters as the FMS EQ ID 002320 BNR 060 Magnetic Heading The Same Parameters as the FMS EQ ID 002

321 SALSystem Address Label for AutothrottleComputer

9

321 BNR 056 Drift Angle The Same Parameters as the FMS EQ ID 002321 BNR 060 Drift Angle The Same Parameters as the FMS EQ ID 002322 SAL System Address Label for FCC 1 9322 BNR 056 Flight Path Angle The Same Parameters as the FMS EQ ID 002322 BNR 060 Flight Path Angle The Same Parameters as the FMS EQ ID 002323 SAL System Address Label For FCC 2 18323 BNR 002 Geometric Altitude Feet 50000 17 1323 BNR 056 Geometric Altitude The Same Parameters as the FMS EQ ID 002323 BNR 060 Geometric Altitude The Same Parameters as the FMS EQ ID 002324 SAL System Address Label For FCC 3 18324 BNR 056 Estimated Position Uncertanity The Same Parameters as the FMS EQ ID 002324 BNR 060 Estimated Position Uncertanity The Same Parameters as the FMS EQ ID 002324 BNR 114 Effective Pitch Angle Degrees ±180 13 0.02 37325 SAL System Address Label For APU 13325 BNR 114 Effective Roll Angle Degrees ±180 13 0.02 37326 SAL System Address Label For APU Controller 28327 SAL SAL Mode Control Pane (MCP) 45330 SAL System Address Label For FMC 3 8331 SAL System Address Label For ATC Transponder 12332 SAL System Address Label For DADC 12335 BNR 002 Track Angle Rate Deg/Sec 32 11 0.015 10 20335 BNR 056 Track Angle Rate The Same Parameters as the FMS EQ ID 002335 BNR 060 Track Angle Rate The Same Parameters as the FMS EQ ID 002

SUP

PL

EM

EN

T 16 T

O A

RIN

C SP

EC

IFIC

AT

ION

429 PA

RT

1- Page 13

AT

TA

CH

ME

NT

1-16SU

PP

LE

ME

NT

16 UP

DA

TE

S TO

LA

BE

L C

OD

ES

Code No.(Octal)

DataEqpt.

ID(Hex)


ResolutionMINTX

MAXTX

REFATT

340 BNR 004 Inertial Yaw Rate Deg/Sec 128 13 0.015 10 20 14340 BNR 004 Track Angle Grid Degree ± 180 15 0.0055 20 Hz 110 Hz340 BNR 005 Inertial Yaw Rate Deg/Sec 128 13 0.015 10 20 14340 BNR 140 Pressure Ratio (Pt/Ps) Ratio 16 14 0.001 62.5 125 36341 BNR 004 Grid Heading Degree ± 180 15 0.0055 20 Hz 110 Hz341 BNR 038 Grid Heading Degree ± 180 15 0.0055 20 Hz 110 Hz341 BNR 140 Pressure Ratio (Ps/Pso) Ratio 4 12 0.001 62.5 125 36342 BNR 140 Air Density Ratio Ratio 4 12 0.001 250 500 36350 Discrete 004 IRS Maintenance Discrete350 Discrete 018 Maintenance Data #1 38350 Discrete 019 CFDS Bite Fault Summary Word For HFDR350 Discrete 024 MU Output Data Word Failure Status350 Discrete 038 IRS Maintenance Word #1350 Discrete 050 VDR Fault Summary Word350 Discrete 053 CFDS Bite Fault Summary Word For HFDU350 DISC 055 ILS Maintenance Word350 Discrete 058 Maintenance Word #1350 BCD 114 Fuel Density kg/l 0-.999 4 0.01 37350 Discrete 140 Maintenance Data # 1 250 500 36351 Discrete 024 MU Output Data Word, Failure Status351 Discrete 038 IRS Maintenance Word #2351 DISC 055 MMR Maintenance Word351 Discrete 058 Maintenance Word #2351 BCD 114 Inner Tank 1 Probe Capacitance pf 0-400 14 0.1 37351 Discrete 140 Maintenance Data # 2 250 500 36352 DISC 055 MLS Bite Status352 Discrete 058 Maintenance Word 34352 BCD 114 Center, ACT & RCT Probe Capacitance pf 0-400 14 0.1 37352 Discrete 140 Maintenance Data # 3 Flight Count 524287 250 500 36353 Discrete 038 IRS Maintenance Word #3353 BCD 114 Inner Tank 3 Probe Capacitance pf 0-400 14 0.1 37354 056 Maintenance Data #5 The Same Parameters as the FMS EQ ID 002354 060 Maintenance Data #5355 DIS 00B GNSS Fault Summary - 21 200 1200355 Discrete 038 IRS Maintenance Word #4357 ISO-5 056 ISO Alphabet #5 Message The Same Parameters as the FMS EQ ID 002357 ISO-5 060 ISO Alphabet #5 Message The Same Parameters as the FMS EQ ID 002360 BNR 056 Flight Information The Same Parameters as the FMS EQ ID 002360 BNR 060 Flight Information The Same Parameters as the FMS EQ ID 002360 BNR 142 RAIM Status Word NM 16 13 0.00195 39362 SAL System Address Label For PSS 15363 SAL System Address Label For CSS 15364 SAL System Address Label For AES 16366 SAL System Address Label For Multicast 43367 SAL System Address Label For Bridge 43370 BNR 00B GNSS Height WGS-84 (Hae) Feet ±131,072 20 0.125 1200 30

SUP

PL

EM

EN

T 15 T

O A

RIN

C SP

EC

IFIC

AT

ION

429 PA

RT

1- Page 14

AT

TA

CH

ME

NT

1-16SU

PP

LE

ME

NT

16 UP

DA

TE

S TO

LA

BE

L C

OD

ES

Code No.(Octal)

DataEqpt.

ID(Hex)


ResolutionMINTX

MAXTX

REFATT

370 BNR 00B GNSS Height Feet ±131,072 20 0.125 200 1200375 BNR 004 Along Hdg Accel Gs 4 18 1.53E-5 50 Hz 110Hz375 BNR 038 Along Hdg Accel Gs 4 18 1.53E-5 50 Hz 110Hz376 BNR 004 Cross Hdg Accel Gs 4 18 1.53E-5 50 Hz 110Hz376 BNR 038 Cross Hdg Accel Gs 4 18 1.53E-5 50 Hz 110Hz

SUP

PL

EM

EN

T 16 T

O A

RIN

C SP

EC

IFIC

AT

ION

429 PA

RT

1- Page 15

AT

TA

CH

ME

NT

1-16SU

PP

LE

ME

NT

16 UP

DA

TE

S TO

LA

BE

L C

OD

ES

MARK 33 DIGITAL INFORMATIONTRANSFER SYSTEM (DITS)

PART 2DISCRETE WORD DATA STANDARDS

ARINC SPECIFICATION 429P2-15

PUBLISHED: March 6, 1996

AN 0

DOCUMENT

Prepared byAIRLINES ELECTRONIC ENGINEERING COMMITTEEPublished byAERONAUTICAL RADIO, INC.2551 RIVA ROAD, ANNAPOLIS, MARYLAND 21401

This document is based on material submitted by variousparticipants during the drafting process. Neither AEEC nor ARINChas made any determination whether these materials could besubject to valid claims of patent, copyright or other proprietaryrights by third parties, and no representation or warranty, express orimplied, is made in this regard. Any use of or reliance on thisdocument shall constitute an acceptance thereof "as is" and besubject to this disclaimer.


ITEM SUBJECT PAGE

1.0 INTRODUCTION 11.1 Purpose of ARINC Specification 429 11.2 Organization of ARINC Specification 429 1

2.0 DATA STANDARDS 2-138

iii

ADDED: MARCH 6, 1996ARINC SPECIFICATION 429 PART 2 - Page 1

1.0 INTRODUCTION

1.1 Purpose of ARINC Specification 429

ARINC Specification 429 defines the air transport industry’s standards for the transfer of digital data between avionicssystems elements. Adherence to these standards is desired for all inter-systems communications in which the systemline replaceable units are defined as “unit interchangeable” in the relevant ARINC characteristics. Their use for intra-system communications in systems in which the line replaceable units are defined in the ARINC characteristics as“system interchangeable” is not essential, although it is desired.


ARINC Specification 429 was originally published in a single volume through version 14 (429-14). The size of thedocument and the need for improved organization dictated the division of the document into three parts. Those threeparts include:

Part 1, “Functional Description, Electrical Interface, Label Assignments and Word Formats

Part 2 , “Discrete Word Data Formats¢-15

Part 3, “File Data Transfer Techniques”

Part 1 provides the basic description of the functions and the supporting physical and electrical interfaces for the datatransfer 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 datatransferred in large blocks and/or file format. For convenience of the user, the section and attachment numbering hasbeen 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 timelyrevisions as industry needs dictate. The “dash numbers” for each new Part will not be synchronized with the otherParts as time passes. Users of ARINC Specification 429 should ensure that the latest version of each Part is used whendesigning or procuring equipment.

ADDED: MARCH 6, 1996ARINC SPECIFICATION 429 PAR T 2 - Page 2

2.0 DATA STANDARDS

Label 005 0D0 - Engine Discretes (737)

Bit No. Function 1 0

1 X2 X3 X4 Label 005 0D0 X5 X6 X7 X8 X9-10 SDI11 PAD X12 PAD X13 Failure to clear serial data interrupt Fail Pass14 ARINC received fail Fail Pass15 PROM checksum fail Fail Pass16 User RAM fail Fail Pass17 NV RAM address fail Fail Pass18 NV RAM bit fail Fail Pass19 RTC fail Fail Pass20 Microprocessor fail Fail Pass21 Battery low Fail Pass22 NV RAM corrupt Fail Pass23 Not used24 Not used25 Not used26 Interrogate activated Activated Non-Activated27 Erase activated Activated Non-Activated28 BIT activated Activated Non-Activated2930 SSM3132 Parity (Odd)

*Bits InstallationNumber

10 9

0 0 (4)0 1 11 0 21 1 3


DATA STANDARDS

Label 006 0D0 - Engine Options (737)


1 X2 X3 X4 Label 006 0D0 X5 X6 X7 X8 X9-10 SDI11 X12 X13 X14 X15 X16 X17 X18 PADS X19 X20 X21 X22 X23 X24 X2930 SSM3132 Parity (Odd)

*Bits Installation Bits DataNumber

28 27 26 2510 9

1 1 0 0 Engine - Option - 10 0 (4) 1 0 1 0 Engine - Option - 20 1 1 0 1 1 0 Engine - Option - 31 0 2 0 1 1 0 Engine - Option - 31 1 3 0 0 0 0 Engine - Option - 4

ADDED: July 1, 1990ARINC SPECIFICATION 429 PAR T 2 - Page 4

DATA STANDARDS

Label 013 0B8 - Control Word for TCAS/Mode S Transponder


1 0

1 X2 X3 X4 Label 013 0B8 X5 X6 X7 X8 X9 SDI (MSB) 110 SDI (LSB)11 Flight Level Absolute Relative12 Altitude Select 213 Altitude Select14 Spare15 Spare16 Spare17 Spare18 User19 Defined 320 TCAS Display21 Mode22 0.523 1.024 Selected 2.025 TCAS 4.026 Range 8.027 (NM) 16.028 32.029 64.030 SSM31 SSM32 Parity (Odd)

Note 1: SDI Note 2: Altitude Select

BITS MEANING BITS MEANING

10 9 13 12

0 0 Both (TA/RA Bus #1 and #2) 0 0 Normal -A to +A0 1 Left (TA/RA Bus #1) 0 1 Above -A to +B1 0 Right (TA/RA Bus #2) 1 0 Below -B to +A1 1 Unrestricted 1 1 Not Used

NOTE 3: The use of these user-defined bits is optional. They are generated at the control panel, passed throughthe transponder without change and sent to the TCAS computer unit. If there is no control functionpossible from these bits, they are set to zero.


DATA STANDARDS

Label 016 0B8 - Control Word for TCAS/Mode S Transponder


1 0

1 X2 X3 X4 Label 016 0B8 X5 X6 X7 X8 X9 SDI1011 Altitude Reporting OFF ON12 SPI Ident ON Ident OFF13 Display14 Control 1 515 Sensitivity16 Level 217 Control18 D119 D220 D4 321 C122 C2 409623 C4 Ident24 B1 Code25 B226 B427 A128 A229 A430 SSM31 SSM32 Parity (Odd)

Note 1: Display Control Note 2: Manuel Sensitivity Level Control

BITS MEANING BITS MEANING

14 13 17 16 15

0 0 Primary and Traffic Advisory 0 0 0 SL=0 (AUTOMATIC)0 1 Primary display functions only (no TCAS data) 0 0 1 SL=1 (STBY)1 0 TCAS Traffic Advisory Only 0 1 0 SL=2 (TA ONLY)1 1 No control function possible 0 1 1 SL=3

1 0 0 SL=41 0 1 SL=51 1 0 SL=61 1 1 SL=7

NOTE 3: See Attachment 5A of ARINC Characteristic 735 for Mode A reply codes.

NOTE 4: The transfer time should not exceed 200 milliseconds.

COMMENTARY

The delay from the time a command is activated at the control panel to the time of the equipmentresponse should be minimized.

NOTE 5: Primary display functions are those functions for which a display may have need designed when thatdisplay is also being used in a shared manner as a Traffic Advisory Display.


DATA STANDARDS

Label 145 025 - Discrete Status 2 EFIS

Bit No. Function Bit Status

1 0

1 X2 X3 X4 Label 145 025 X5 X6 X7 X8 X9-10 SDI11 DI-29P GROUND OPEN12 DI-30P GROUND OPEN13 DI-31P GROUND OPEN14 DI-32P GROUND OPEN15 DI-33P GROUND OPEN16 DI-34P GROUND OPEN17 DI-35P GROUND OPEN18 DI-36P GROUND OPEN19 DI-37P GROUND OPEN20 DI-38P GROUND OPEN21 DI-39P GROUND OPEN22 DI-40P GROUND OPEN23 DI-41P GROUND OPEN24 DI-43P GROUND OPEN25 DI-44P GROUND OPEN26 DI-45P GROUND OPEN27 PAD X28 PAD X29 PAD X30-31 SSM32 Parity (Odd)

REVISED: August 1, 1980ARINC SPECIFICATION 429 PAR T 2 - Page 7

DATA STANDARDS

Label 145 0A1 - FCC Control Panel Status Discrete (Triplex)


1 0

1 X2 X3 X4 Label 145 0A1 X5 X6 X7 X8 X9-10 Unassigned11 A/P CWS R Engaged Requested Not Requested12 A/P CWS L Engaged Requested Not Requested13 A/P CWS C Engaged Requested Not Requested14 A/P CMD R Engaged Requested Not Requested15 A/P CMD L Engaged Requested Not Requested16 A/P CMD C Engaged Requested Not Requested17 Land 2 (Green) Requested Not Requested18 Land 3 (Green) Requested Not Requested19 LOC Mode Oper. Requested Not Requested20 Appr. Mode Req. Requested Not Requested21 G/S Mode Oper. Requested Not Requested22 Flare Oper. Requested Not Requested23 Rollout Mode Oper. Requested Not Requested24 G/A Mode Oper. Requested Not Requested252627 Not Used282930-31 SSM32 Parity (Odd)

ADDED: MARCH 6, 1996ARINC SPECIFICATION ARINC 429 PAR T 2 - Page 8

DATA STANDARDS



1 0



DATA STANDARDS

Label 146 0A1 - FCC Control Panel Status Discrete (Dual-Dual)


1 0

1 X2 X3 X4 Label 146 0A1 X5 X6 X7 X8 X9-10 Unassigned11 A/P CWS Requested Not Requested12 A/P CMD Requested Not Requested13 Capt. F/D Eng. Requested Not Requested14 Land Trk Requested Not Requested15 ATS Warn. Requested Not Requested16 ILS Cat. 2 Available Requested Not Requested17 Cat. 2 Autoland Avail. Requested Not Requested18 Cat. 3 Autoland Avail. Requested Not Requested19 LOC Excess Beam Dev. Requested Not Requested20 F/O F/D Eng. Requested Not Requested21 Glide Excess Beam Dev. Requested Not Requested22 Auto G/A Not Available Requested Not Requested23 Engine Out Compensation Not Avail. Requested Not Requested24 Unassigned25 Align FW Requested Not Requested26 Land 3 FW Requested Not Requested27 Warning Inhibit Requested Not Requested28 Unassigned29 A/P CMD Warning Requested Not Requested30-31 SSM32 Parity (Odd)


DATA STANDARDS



1 0



DATA STANDARDS

Label 151 05A - LB/KG Control Word


1 0

1 X2 X3 X4 Label 151 05A X5 X6 X7 X8 X9-27 PAD Bits X28 LBS/KGS29 PAD X30-31 SSM32 P


DATA STANDARDS



1 0



DATA STANDARDS



1 0

1 X2 X3 X4 Label 160 025 X5 X6 X7 X8 X9-10 SDI11 DI-128P GROUND OPEN12 DI-129P GROUND OPEN13 DI-130P GROUND OPEN14 DI-139P GROUND OPEN15 DI-140P GROUND OPEN16 DI-142P GROUND OPEN17 DI-143P GROUND OPEN18 DI-144P GROUND OPEN19 RESERVED20 RESERVED21 RESERVED22 RESERVED23 RESERVED24 RESERVED25 RESERVED26 RESERVED27 PAD X28 PAD X29 PAD X30-31 SSM32 Parity (Odd)


DATA STANDARDS



1 0

1 X2 X3 X4 Label 161 025 X5 X6 X7 X8 X9-10 SDI11 RESERVED12 RESERVED13 RESERVED14 RESERVED15 RESERVED16 RESERVED17 RESERVED18 RESERVED19 RESERVED20 RESERVED21 RESERVED22 RESERVED23 RESERVED24 RESERVED25 RESERVED26 RESERVED27 PAD X28 PAD X29 PAD X30-31 SSM32 Parity (Odd)


DATA STANDARDS

Label 161 10A - Full Authority Engine Control Maintenance Discretes


1 0

1 X2 X3 X4 Label 161 10A X5 X6 X7 X8 X9 SDI101112131415 Pad16171819202122232425 Screen 126 ID27282930 SSM31 SSM32 Parity (Odd)

Note 1: Screen ID Codes

Value (HEX) MEANING

13 Ignition Test14 Ignitor Test in Progress21 FADEC Test22 FADEC Test in Progress


DATA STANDARDS

Label 161 10B - Full Authority Engine Control Maintenance Discretes


1 0

1 X2 X3 X4 Label 161 10B X5 X6 X7 X8 X9 SDI101112131415 Pad16171819202122232425 Screen 126 ID27282930 SSM31 SSM32 Parity (Odd)

Note 1: Screen ID Codes

Value (HEX) MEANING

13 Ignition Test14 Ignitor Test in Progress21 FADEC Test22 FADEC Test in Progress

ADDED: August 1, 1980ARINC SPECIFICATION 429 Par t 2 - Page 25

DATA STANDARDS

Label 270 001 - FCC General Discrete Word


1 0

1 X2 X3 X4 Label 270 001 X5 X6 X7 X8 X9-10 SDI11 Glide Capt. ID Requested Not Requested12 LOC Capt. Cond. Requested Not Requested13 LOC Trk Com. Requested Not Requested14 LOC Trk Mon. Requested Not Requested15 700 Ft. Com. Requested Not Requested16 700 Ft. Mon. Requested Not Requested17 Flare Cond. Com. Requested Not Requested18 Flare Cond. Mon. Requested Not Requested19 CWS L.D. Pitch Requested Not Requested20 CWS L.D. Roll Requested Not Requested21 Appr. II Own Requested Not Requested22 Land II Own Requested Not Requested23 Land III Own Requested Not Requested24 FCC FW Requested Not Requested25 AHRS I Validity Requested Not Requested26 N1 Command Requested Not Requested27 ARM TCC Command Requested Not Requested28 SPD/Mach Command Requested Not Requested29 TBD30-31 SSM32 Parity (Odd)

REVISED: April 24, 1981ARINC SPECIFICATION 429 PAR T 2 - Page 26

DATA STANDARDS

Label 270 004 - IRS Discrete


1 0

1 X2 X3 X4 Label 270 004 X5 X6 Bit 11 or 12 or X7 13 is always set X8 to logic (1) X9-10 SDI11 Align Mode/Not Ready Yes No12 Reversionary Attitude Mode Yes No13 Normal Mode Yes No14 Set Heading Yes No15 Attitude Invalid Yes No16 DC Fail (Low) Yes No17 ON DC Yes No18 ADC Fault Yes No19 IRU Fault See Note Yes No20 DC Fail - ON DC 2 Yes No21 Align Fault Yes No22 No IRS Initialization Yes No23 EXCESSIVE MOTION ERROR Yes No24 ADC/IRU Fault Yes No25 No VOR/DME #1 Input Yes No2627 Align Status2829 No VOR/DME #2 Input Yes No30-31 SSM32 Parity (Odd)

ADDED: April 24, 1981ARINC SPECIFICATION 429 PAR T 2 - Page 27

DATA STANDARDS

IRS/AHRS BIT EXPLANATIONS

Bit No. Function

11 Align Mode/NR The IRU operating software mode is ALIGN or the initialization of any mode.

12 Reversionary Att. Mode The IRU operating software is ATT.

13 NAV Mode The IRU operating software mode is NAV.

14 Set Heading Magnetic heading outputs are no longer being calculated but have thecharacteristics of a "free DG" and a set heading has been input to the IRU.

15 Attitude Invalid The IRU has detected a failure of attitude, heading, angular body rates, orlinear body accelerations (same as FAULT discrete).

16 DC Fail The IRU DC power input is less than 18 VDC.

17 On DC The IRU is operating on the DC power input.

18 ADC Fault ADC in-flight fault, but power-on BITE found no faults with the IRU ADC inputchannel.

19 IRU Fault The BITE has detected a fault not annunciated in BITS 18, 21, 22, 23, or 24.

20 DC Fail - On DC The DC power input was not available when required by the IRU. Thiscondition shall be reset only by power-on initialization.

21 Align Fault Failed the IRU operating software ALIGN criterion but neither power-on norcontinuous BITE show any faults.

22 No IRS Initialization No input or an incorrect input has been received from the IRMP or FMC’s.

23 Excessive Motion Error Non-zero ground speed during the ALIGN mode.

24 ADC/IRU Fault ADC in-flight fault, but no power-on BITE information available prior toflight.

25 No VOR/DME #1 Input

26 Align status is represented by a series of descending digits, each indicating27 Align Status a successive state of alignment. Three bits provide a seven state alignment28 status as follows:

LSB MSB26 27 28

1 1 1 Alignment Commenced0 1 1 -- - - -- - - -- - - -- - - -1 0 0 Highest Alignment Status0 0 0 Unassigned

29 No VOR/DME #2 Input


DATA STANDARDS

Label 270 005 - AHRS Discrete


1 0

1 X2 X3 X4 Label 270 005 X5 X6 X7 X8 X9-10 SDI11 Align Mode/Not Ready Yes No12 Reversionary Attitude Mode Yes No13 Normal Mode Yes No14 Magnetic Heading/DG Mode Yes No15 Attitude Invalid Yes No16 Low Battery (Not used in AHRS) Yes No17 On Battery Yes No18 TAS Invalid Yes No19 AHRU Fault Yes No202122 IRS Use232425 No VOR/DME #1 Input Yes No2627 IRS Use2829 No VOR/DME #2 Input Yes No30-31 SSM32 Parity (Odd)

NOTES: 1) Attitude invalid is equivalent to AHRS failure.

2) Bit 13 "1" condition indicates that AHRS is in the "Normal" mode as described in Section 1.2.1 of ARINCCharacteristic 705. A "0" condition indicates that the AHRS is in the reversionary "Basic mode".

3) Bit 14 "1" condition indicates that AHRS is in the "Magnetic Heading" mode. A "0" condition indicatesthe AHRS is in the reversionary "DG" mode. See Section 1.2.2 of ARINC Characteristic 705 fordescription of modes of heading operation.

REVISED: April 24, 1981ARINC SPECIFICATION 429 PAR T 2 - Page 29

DATA STANDARDS

Label 270 006 - ADS Discrete


1 0

1 X2 X3 X4 Label 270 006 X5 X6 X7 X8 X9-10 SDI11 Icing Detector On Off12 Pitot Probe Heat On Off13 ADS Computer Status Fail Good14 Pitot/Static Probe Heat On Off15 Static Source Heat On Off16 TAT Probe Heat On Off17 Left Side Angle of Attack Sensor On Off

Heat18 Right Side Angle of Attack Sensor On Off

Heat19 VMO/MMO Overspeed Warning Warn Not Warn20212223 Spare24252627 Angle of Attack Alternate Yes No

Correction28 Baro-Correction Port "A" Yes No29 Zero Mach SSEC Yes No30-31 SSM32 Parity (Odd)

ARINC SPECIFICATION 429 PAR T 2 - Page 30

DATA STANDARDS

Label 270 00B - GPS DATA


1 X2 X3 X4 Label 270 00B X5 X6 X7 X8 X9-10 SDI11 Spare12 Spare13 Vertical Maneuver Alert (flash) On Off14 Vertical Maneuver Alert (on) Flash Off15 Turn Point Alert (flash) On Off16 Turn Point Alert (on) Flash Off17 No Waypoint Entered True False18 No Course Entered True False19 2D/3D NAV 3D 2D20 GPS NAV VALID True False21 EN ROUTE True False22 Terminal True False23 GPS HIGH ACCURACY True false24 APPROACH (Angular) True False25 GPS SELF TEST (BIT) True False26 Figure of Merit (LSB)27 Figure of Merit (LSB)28 Figure of Merit (LSB)29 Figure of Merit (MSB)30 SSM3132 Parity (Odd)

NOTE: Typical discrete functions are shown in the above table. Slight variations of bit usage may arise accordingto the specific application.

Bits 15 16 Status

0 0 Enroute1 0 Terminal0 1 Approach1 1 N/A

ADDED: January 22, 1982ARINC SPECIFICATION 429 PAR T 2 - Page 31

DATA STANDARDS

Label 270 01A - EEC Discrete


1 0

1 X2 X3 X4 Label 270 01A X5 X6 X7 X8 X9-10 SDI11 X12 Pad X13 X14 X15 EPR Loop Selected Yes No16 N2 Loop Selected Yes No17 EGT Loop Selected Yes No18 Integrator On Min Stop Yes No19 Integrator On Max Stop Yes No20 EEC On/Off Discrete Off No21 Initialization Yes No22 Low Speed Latch Yes No23 EAROM Failed Good24 EEC Probe T2 Selected Yes No25 Fault Light On Off26 See Main Panel Yes No27 TCC System Failed Good28 TCA System Failed Good29 Thrust Bump Inhibit Yes No30-31 SSM32 Parity (Odd)


DATA STANDARDS

Label 270 023 - GPWS Discrete


1 0

1 X2 X3 X4 Label 270 023 X5 X6 X7 X8 X9-10 SDI11 Sink Rate12 Pull Up13 Terrain14 Don’t Sink15 Too Low Gear *16 Too Low Flap17 Too Low Terrain18 Glide Slope19 Minimum Minimum20 Terrain Pull Up2122232425 Spare (All "O" States)2627282930-31 SSM32 Parity (Odd)

* Only one visual message should be displayed at a time (only one data bit should be set to the logic "1" stateat a time).

REVISED: November 17, 1986ARINC SPECIFICATION 429 PAR T 2 - Page 33

DATA STANDARDS

Label 270 02F - EEC Status


1 0

1 X2 X3 X4 Label 270 02F X5 X6 X7 X8 X9-10 SDI X11 PAD X12 PAD X13 PAD X14 PDIU Status Invalid OK15 Spare X16 Channel Select Mode Secondary Auto17 Primary Chan. Manually Selected** Selected Not Selected18 N2 Droop Control Mode Engaged Not Engaged19 Reverser System Status Inoperative OK20 Channel Controlling Status Controlling Not Controlling21 2.5 Bleed System Failed Failed Operational22 TCA Valve(s) Failed Closed Failed OK23 Case Cooling Valve Stuck Failed OK24 14th Stage Bleed System Failed Failed Operational25 Channel Incapable (Failed) Incapable Capable26 Oil Cooling System Status Faulted Ok27 SVA System Failed Failed Operational28 Starter Cutout Command Cutout Not Cutout29 Spare X30-31 SSM X32 Parity X

** Secondary Channel Only.

NOTE: Typical discrete functions are shown in the above table. Slight variations of bit usage may ariseaccording to the specific application.


DATA STANDARDS

Label 270 030 - Transponder Discrete


1 0

1 X2 X3 X4 Label 270 030 X5 X6 X7 X8 X9-10 SDI111213-14 SPARE15-161718 Left (See Note 1 Below)1920 Right (See Note 2 Below)212223 Up (See Note 3 Below)24252627-28 Down (See Note 4 Below)2930 SSM3132 Parity (Odd)

Note 1: Left Component Note 2: Right Component

00 - No Left Adivisory 00 - No Right Advisory01 - Turn Left 01 - Turn Right10 - Don’t Turn Left 10 - Don’t Turn Right11 - Not Used 11 - Not Used

Note 3: Up Component Note 4: Down Component

0000 - No Up Advisory 0000 - No Down Advisory0001 - Climb 0001 - Decend0010 - Climb Faster than 500 FPM 0010 - Decend Faster than 500 FPM0011 - Climb Faster than 1000 FPM 0011 - Decend Faster than 1000 FPM0100 - Climb Faster than 2000 FPM 0100 - Decend Faster than 2000 FPM0101 - Don’t Decend 0101 - Don’t Climb0110 - Don’t Decend Faster than 500 FPM 0110 - Don’t Climb Faster than 500 FPM0111 - Don’t Decend Faster than 1000 FPM 0111 - Don’t Climb Faster than 1000 FPM1000 - Don’t Decend Faster than 2000 FPM 1000 - Don’t Climb Faster than 2000 FPM1001 - 1111 Not Used 1001 - 1111 Not Used


DATA STANDARDS

Label 270 033


1 0

1 X2 X3 X4 Label 270 033 X5 X6 X7 X8 X9-10 SDI11 Turbine Case Cooling Valve Open Closed12 Upper Turbine Cooling Valve Open Closed13 Lower Turbine Cooling Valve Open Closed14 Fuel Heater Valve Open Closed15161718192021 Spare (all "0" states)222324252627282930-31 SSM32 Parity (Odd)


DATA STANDARDS

Label 270 035 - TCAS Vertical RA Data Discrete


1 0

1 X2 X3 X4 Label 270 035 X5 X6 X7 X8 X9 SDI BIT 010 SDI BIT 111 100 ft/min12 200 ft/min13 Advisory 200 ft/min14 Altitude 200 ft/min15 Rate 1600 ft/min16 3200 ft/min17 Sign18 Combined Control19 Combined Control 120 Combined Control21 Vertical Control22 Vertical Control 223 Vertical Control24 Up Advisory25 Up Advisory 326 Up Advisory27 Down Advisory28 Down Advisory 429 Down Advisory30 SSM31 SSM 532 Parity (Odd)

Note 1: Combined Control

BITS MEANING

20 19 18

0 0 0 No Advisory0 0 1 Clear of Conflict0 1 0 Drop Track0 1 1 Altitude Lost1 0 0 Climb Corrective See Note 1A1 0 1 Descend Corrective See Note 1A1 1 0 Preventative1 1 1 Not Used

NOTE 1A: CAS logic defined by RTCA DO-185 Change 6 does not discriminate between Climb Corrective andDescend Corrective. The omission is expected to be corrected in Change 7. Meanwhile, the receiving RA

Display must assume a Climb Corrective when either a Climb Corrective or Descend Corrective isissued until theMOPS is revised.


DATA STANDARDS

Label 270 035 (cont’d) - TCAS Vertical RA Data Discrete

Note 2: Vertical Control

BITS MEANING

23 22 21

0 0 0 Advisory is not one ofthe following types

0 0 1 Crossing0 1 0 Reversal0 1 1 Increase1 0 0 Maintain1 0 1 Not Used1 1 0 Not Used1 1 1 Not Used

Note 3: Up Advisory

BITS MEANING

26 25 24

0 0 0 No Up Advisory0 0 1 Climb0 1 0 Don’t Descend0 1 1 Don’t Descend > 5001 0 0 Don’t Descend > 10001 0 1 Don’t Descend > 20001 1 0 Not Used1 1 1 Not Used

Note 4: Down Advisory

BITS MEANING

29 28 27

0 0 0 No Down Advisory0 0 1 Descend0 1 0 Don’t Climb >0 1 1 Don’t Climb > 5001 0 0 Don’t Climb > 10001 0 1 Don’t Climb > 20001 1 0 Not Used1 1 1 Not Used

NOTE 5: The presence of a No Computed Data report in the SSM field indicates that the no RA exists or thatinformation in bits 18 through 29 is unreliable. Therefore, no RA should be issued by the Display.

REVISED: NOVEMBER 17, 1986ARINC SPECIFICATION 429 PAR T 2 - Page 38

DATA STANDARDS

Label 270 03A - Propulsion Discrete Interface Unit


1 0

1 X2 X3 x4 Label 270 03A X5 X6 X7 X8 X9-10 SDI

1 0Left Engine Right Engine

0 110 SDI11 PDUI Self Test Failed OK12 P2/T 2 Probe Heat Heat Off Heat On13 Spare X14 Idle Select Minimum Approach15 Air/Ground Switch Ground Air16 Opposite Engine Status Shut Down Running17 EEC to PDUI SDD Faulted OK18 Spare X19 Spare X20 Spare X21 Spare X22 Spare X23 Spare X24 Ground Test Power On Off25 Spare X26 Spare X27 Spare X28 Spare X29 Spare X30-31 SSM32 Parity (Odd)



DATA STANDARDS

Label 270 03B


1 0

1 X2 X3 X4 Label 270 03B X5 X6 X7 X8 X9-10 SDI11 INS Selected Not Selected12 VOR/LOC Selected Not Selected13 ILS/Land Selected Not Selected14 Land Selected Not Selected15 Altitude Hold Selected Not Selected16 Altitude Select Selected Not Selected17 Mach Selected Not Selected18 IAS Selected Not Selected19 Vertical Speed Selected Not Selected20 TURB Selected Not Selected21 PMS Selected Not Selected22 Captain’s F/D On and Select Selected Not Selected23 F/O F/D On and Select Selected Not Selected24 Course Transfer No. 1 Selected Not Selected25 Course Transfer No. 2 Selected Not Selected26 A/P Engage Manual Selected Not Selected27 A/P Engage Command Selected Not Selected28 Spare (all "0" states)29 Word Validity Invalid Valid30-31 SSM32 Parity (Odd)


DATA STANDARDS

Label 270 03D - Status Word


1 X2 X3 X4 Label 270 03D X5 X6 X7 X8 X9-10 SDI11-28 Data30-31 Status Matrix32 Parity (Odd)

Bit Parameter

**11 AVM System Fault*11 PAD

12 AVM System Fault*13 AVM Engine 1 Alert

**13 Broadband Alert - Engine 1*14 AVM Engine 2 Alert

**14 Broadband Alert - Engine 2**15 AVM Engine 1 Double Channel Fault

*15 PAD**16 AVM Engine 2 Double Channel Fault

*16 PAD*17 PAD

**17 AVM Engine 1 Alert*18 PAD

**18 AVM Engine 2 Alert**19 Engine 1 High Broadband Alert

*19 PAD**20 Engine 2 High Broadband Alert

*20 PAD21 NVRAM Failure22 Fault History Erase23 PAD

***23 Flight History Erase24 PAD25 PAD26 PAD27 PAD28 PAD29 PAD

* 757 Pratt and Whitney and 737 CFM-56** 757 Rolls Royce Only*** 737 CFM-56 Only


DATA STANDARDS

Label 270 03F - EEC Status


1 0

1 X2 X3 X4 Label 270 03F X5 X6 X7 X8 X9-10 SDI X11 PAD X12 PAD X13 PAD X14 PDIU Status Invalid OK15 Spare X16 Channel Select Mode Secondary Auto17 Primary Chan. Manually Selected** Selected Not Selected18 N2 Droop Control Mode Engaged Not Engaged19 Reverser System Status Inoperative OK20 Channel Controlling Status Controlling Not Controlling21 2.5 Bleed System Failed Failed Operational22 TCA Valve(s) Failed Closed Failed OK23 Case Cooling Valve Stuck Failed OK24 14th State Bleed System Failed Failed Operational25 Channel Incapable (Failed) Incapable Capable26 Oil Cooling System Status Faulted Ok27 SVA System Failed Failed Operational28 Starter Cutout Command Cutout Not Cutout29 Spare X30-31 SSM X32 Parity X

** Secondary Channel Only.


REVISED: MARCH 6, 1996ARINC SPECIFICATION 429 PAR T 2 - Page 42

DATA STANDARDS

Label 270 115 - Stored TACAN Control Word


1 X2 X3 X4 Label 270 115 X5 X6 X7 X8 X9 SEL TACAN 1 TACAN 210 MEM IN BEARING MEMORY NO BEARING MEMORY11 MEM IN RANGE MEMORY NO RANGE MEMORY12 TUNE AUTOTUNE NO AUTOTUNE13-14 Pad15-16 MLS Select 117 (LSB)18 BCD Channel Code Units1920 (MSB)21 (LSB)22 HEX Channel Code Tens2324 (MSB)25 TST TEST NO TEST26 X/Y X Y27-28 Mode Control 229 INT NORMAL INVERSE30 AGC ENABLE DISABLE31 STAT NO COMPUTED DATA VALID DATA32 Parity (Odd)

Table 1 - TACAN/MLS Select Table 2 - Mode Control

Bits Meaning Bits Meaning

15 16 27 28

0 0 TACAN 0 0 REC1 0 MLS W Mode 1 0 T/R0 1 Not Used 0 1 A/A REC1 1 MLS Z Mode 1 1 A/A T/R


DATA STANDARDS

Label 271 005 - AHRS Discrete


1 0

1 X2 X3 X4 Label 271 005 X5 X6 X7 X8 X9-10 SDI11 MSU Fail Yes No12 RMCU Fail Yes No1314151617181920 Spare212223242526272829 No VOR/DME #2 Input30-31 SSM32 Parity (Odd)


DATA STANDARDS

Label 271 006 - ADS Discrete


1 0

1 X2 X3 X4 Label 271 006 X5 X6 X7 X8 X9-10 SDI11 Zero Angle of Attack SSEC Yes No12 Angle of Attack Sensor Status Fail Good1314151617181920 Spare21222324252627282930-31 SSM32 Parity (Odd)


DATA STANDARDS

Label 271 018 - TCAS Coordination Discrete (MTB,CVC,VRC,CHC,HRC,HSB,VSB)

Transponder To TCAS - Bus 1 Word 1


1 0

1 X2 X3 X4 Label 271 018 X5 X6 X7 X8 X

RF MSG BIT9 MTB 4210 CVC 4311 CVC 4412 VRC 4513 VRC 4614 CHC 4715 CHC 4816 CHC 4917 HRC 5018 HRC 5119 HRC 5220 HSB 5621 HSB 5722 HSB 5823 HSB 5924 HSB 6025 VSB 6126 VSB 6227 VSB 6328 VSB 6429 Pad30 SSM31 SSM32 Parity (Odd)

NOTE: ARINC 429 data word fields for which there are corresponding RF fields are transmitted with the MSB firstin order to maintain consistancy between RF and ARINC 429 data. Normal ARINC 429 protocol calls for thetransmission of the LSB of the field first.


DATA STANDARDS



1 0

1 X2 X3 X4 Label 271 01A X5 X6 X7 X8 X9-10 SDI11 Model X12 Pad X13 0 1 2 3 X14 X15 Engine Model Code 1 0 1 016 Engine Model Code 1 1 0 017 X18 Spare X19 X20 X21 A/C Pack On Off22 A/C Pack Flow Mode Hi Lo23 Air Driven Pump Boeing On Off24 Wing Anti-Icing 767 On Off25 Cowl Anti-Icing Only On Off26 Isolation Valve Open Closed27 Approach Idle Sel. Not Sel.28 Tt2 Probe Heat On Off29 Spare X30-31 SSM32 Parity (Odd)


DATA STANDARDS

Label 271 02F


1 0

1 X2 X3 X4 Label 271 02F X5 X6 X7 X8 X9-10 SDI X11 PAD X12 PAD X13 PAD X14 Reverser Deploy Command On Off15 Turbine Cooling Air Valve Solenoid On Off16 Fuel-Oil Heat Ex. Bypass Valve Sol. On Off17 Spare18 Spare19 14th Stage Bleed Command Closed Open20 Spare X21 Spare X22 Spare X23 Spare X24 T/L Interlock Actuator Command Block Fwd Block Rev25 Reserved (Spare Relay Command) X26 X27 0000 = PW2037 X28 Engine Type Code other codes29 Invalid X30-31 SSM X32 Parity (Odd) X



DATA STANDARDS

Label 271 033


1 0

1 X2 X3 X4 Label 271 033 X5 X6 X7 X8 X9-10 SDI11 High Pressure Compressor Exit Pressure Failed Good12 Fan Inlet Total Pressure Failed Good13 Low Pressure Compressor Exit Pressure Failed Good14 Exhaust Gas Total Pressure Failed Good15 Thermocouples Failed Good16 CPU Self-Test Failed Good17 A/D Converter Self-Test Failed Good18 ARINC 429 Self-Test Failed Good19 Stator Vane Angle Failed Good20 Low Press. Comp. Bleed Valve Pos. Failed Good21 Fuel Flow Failed Good22 Power Supplies Failed Good23 Tachometers Failed Good24 Resistive Temperature Probes Failed Good252627 Spare (all "0" states)282930-31 SSM32 Parity (Odd)


DATA STANDARDS

Label 271 035 (RESERVED) - TCAS Horizontal RA Data Discrete


1 0

1 X2 X3 X4 Label 271 035 X5 X6 X7 X8 X91011121314151617181920212223242526272829303132 Parity (Odd)


DATA STANDARDS

Label 271 03A


1 0

1 X2 X3 X4 Label 271 03A X5 X6 X7 X8 X9-10 SDI11 ECS Pack-L ON OFF12 ECS Pack-R ON OFF13 ECS Pack Demand-L HI LO14 ECS Pack Demand-R HI LO15 PNEU Shutoff Valve-L CLOSED OPEN16 PNEU Shutoff Valve-R CLOSED OPEN17 Isolation Valve OPEN CLOSED18 Spare X19 Wing Anti-Ice-L ON OFF20 Wing Anti-Ice-R ON OFF21 Cowl Anti-Ice-L ON OFF22 Cowl Anti-Ice-R ON OFF23242526 Spare (all "0" states)27282930-31 SSM32 Parity (Odd)



DATA STANDARDS

Label 271 03B


1 0

1 X2 X3 X4 Label 271 03B X X5 X6 X7 X8 X9-10 SDI11 Flare Arm Armed Not Armed12 Flare Engage Engaged Not Engaged13 Glide Slope Capture Engaged Not Engaged14 Go-Around Engage Engaged Not Engaged15 Dual Engage Engaged Not Engaged16 Triple Arm Armed Not Armed17 Triple Engage Engaged Not Engaged18 Rollout Engage Engaged Not Engaged19 Nav Arm Armed Not Armed20 Nav Capture Engaged Not Engaged21 Pitch Wheel Enable Enabled Not Enabled22 Turn Knob in Detent In Detent Not in Detent23 Heading Hold A or C, and B Hold Not Hold24 28 VDC Reference Referenced Not Referenced25 Spare (Pad Bit) X26 Spare (Pad Bit) X27 Spare (Pad Bit) X28 Yaw Damper Engage Engaged Not Engaged29 Word Validity Invalid Valid30-31 SSM32 Parity (Odd)


DATA STANDARDS

Label 271 03F


1 0

1 X2 X3 X4 Label 271 03F X5 X6 X7 X8 X9-10 SDI X11 PAD X12 PAD X13 PAD X14 Reverser Deploy Command On Off15 Turbine Cooling Air Valve Solenoid On Off16 Fuel-Oil Heat Ex. Bypass Valve Sol. On Off17 Spare18 Spare19 14th Stage Bleed Command Closed Open20 Spare X21 Spare X22 Spare X23 Spare X24 T/L Interlock Actuator Command Block Fwd Block Rev25 Reserved (Spare Relay Command) X26 X27 0000 = PW2037 X28 Engine Type Code other codes29 Invalid X30-31 SSM X32 Parity (Odd) X


ADDED: August 1, 1980ARINC SPECIFICATION 429 PAR T 2 - Page 53

DATA STANDARDS

Label 272 001 - FCC Automatic Throttle Modes Discrete Word


1 0

1 X2 X3 X4 Label 272 001 X5 X6 X7 X8 X9 PERF Requested Not Requested10 CLP Requested Not Requested11 SPD Requested Not Requested12 APR Requested Not Requested13 LIM Requested Not Requested14 FLP Requested Not Requested15 SLT Requested Not Requested16 N1 Requested Not Requested17 EPR Requested Not Requested18 TO Requested Not Requested19 FLX Requested Not Requested20 MCT Requested Not Requested21 CLB Requested Not Requested22 CR Requested Not Requested23 VNAV Requested Not Requested24 IAS Requested Not Requested25 MACH Requested Not Requested26 ALT Requested Not Requested27 TRK Requested Not Requested28 RTD Requested Not Requested29 MIN Requested Not Requested30-31 SSM32 Parity


DATA STANDARDS

AUTOMATIC THROTTLE MODES EXPLANATIONS

Bit No. Function

1-8 Label 272 019 PERF The performance submode of the VNV basic mode is in effect. Used with bit 23.10 CLP The automatic throttles are clamped.11 SPD The automatic throttles are engaged in the speed select control mode.12 APR The automatic throttles are engaged in the speed select mode and throttle

control is limited by flap or slat maximum speeds, or by engine limits(N1 or EPR), or by throttle low limit position.

13 LIM Automatic throttle control is currently limited by flap or slat maximumspeeds, or by engine limits (N1 or EPR), or by throttle low limit position.

14 FLP Used with bit 13 to designate flap limit control currently in effect.15 SLT Used with bit 13 to designate slat limit control currently in effect.16 N1 The automatic throttles are engaged in the N1 basic mode and controlling to

a selected N1 limit defined by bits 18 thru 22. Also used with bit 13 andwith bit 23 as the second word.

17 EPR The automatic throttles are engaged in the EPR basic mode and controlling toa selected EPR limit defined by bits 18 thru 22. Also used with bit 13 andwith bit 23 as the second word.

18 TO The N1 or EPR take off thrust limit is currently in effect. Used with Bit 16or 17. Also used with bit 28 for noise abatement annunication.

19 FLX The N1 or EPR maximum continuous thrust limit is currently in effect. Usedwith bit 16 or 17.

20 MCT The N1 or EPR maximum continuous thrust limit is currently in effect. Usedwith bit 16 or 17.

21 CLB The N1 or EPR climb thrust limit is currently in effect. Used with bit 16or 17.

22 CR The N1 or EPR cruise thrust limit is currently in effect. Used with bit 16or 17.

23 VNV The automatic throttles are ingaged in the vertical navigation mode andcontrolling in accordance with a submode designated by bits 24 thru 27 andbits 9, 16 and 17.

24 IAS The IAS submode of the VNV basic mode is currently in effect. Used withbit 23.

25 MACH The Mach submode of the VNV basic mode is currently in effect. Used withbit 23.

26 ALT The altitude hold submode the VNV basic mode is currently in effect. Usedwith bit 23.

27 TRK The climb (descent) path track submode of the VNV basic mode is currently ineffect. Used with bit 23.

28 RTD The automatic throttles are engaged in the retard control mode. Also usedwith bit 18 for noise or abatement annunciation.

29 MIN The automatic throttles are engaged in the speed control mode and throttlecontrol is limited to the minimum alpha cruise speed.

REVISED: July 1, 1990ARINC SPECIFICATION 429 PAR T 2 - Page 55

DATA STANDARDS

Label 272 002 - FMC Discretes


1 0

1 X2 X3 X4 Label 272 002 X5 X6 X7 X8 X9 SDI BIT 010 SDI BIT 111 Enable12 10013 Climb 20014 Rate 40015 Performance 80016 Limit 160017 32001819202122 Pad232425262728 1500 FPM Climb Limit Cannot Climb Can Climb29 2500 FPM Climb Limit Cannot Climb Can Climb30-31 SSM32 Parity (Odd)


DATA STANDARDS

Label 272 003 - TCC Discrete


1 0

1 X2 X3 X4 Label 272 003 X5 X6 X7 X8 X9-10 SDI11 Automatic Throttle Failure/Warning Flag Normal12 APR* Engaged Not Engaged1314151617181920 Spare21222324252627282930-31 SSM32 Parity (Odd)

* The automatic throttles are engaged in the speed select mode and throttle control is to the minimum alphaapproach speed.


DATA STANDARDS

Label 272 018 - TCAS Coordination Discrete (MID Part 1)



1 0

1 X2 X3 X4 Label 272 018 X5 X6 X7 X8 X9 TCAS Broadcast Bit 1

MID (Part 1) RF MSG BIT10 MID BIT A 1 (MSB) 6511 MID BIT A 2 6612 MID BIT A 3 6713 MID BIT A 4 6814 MID BIT A 5 6915 MID BIT A 6 7016 MID BIT A 7 7117 MID BIT A 8 7218 MID BIT A 9 7319 MID BIT A 10 7420 MID BIT A 11 7521 MID BIT A 12 7622 MID BIT A 13 7723 MID BIT A 14 7824 MID BIT A 15 7925 MID BIT A 16 8026 Pad27 Pad28 Pad29 Pad30 SSM31 SSM32 Parity (odd)

Note 1: TCAS Broadcast Bit

BIT MEANING

9

0 Coordination Message1 Received TCAS Broadcast

NOTE: ARINC 429 data word fields for which there are corresponding RF fields are transmitted with the MSB firstin order to maintain consistency between RF and ARINC 429 data. Normal ARINC 429 protocol calls for thetransmission of the LSB of the field first


DATA STANDARDS



1 0

1 X2 X3 X4 Label 272 01A X5 X6 X7 X8 X9-10 SDI11 X12 Pad X13 X14 X15 TCC Stg 2 Sol On Off16 TCC Stg 1 Sol On Off17 TCC Stg 3 Sol On Off18 TCC Stg 1 Valve Open Closed19 Spare X20 TCA-A-Air Valve Open Closed21 TCA-B-Air Valve Open Closed22 X23 X24 X25 Spare X26 X27 X28 X29 X30-31 SSM32 Parity (Odd)


DATA STANDARDS

Label 272 025 - Discrete Data No. 1


1 0

1 X2 X3 X4 Label 272 025 X5 X6 X7 X8 X9-10 SDI111213 DISPLAY MODE SELECTED14 (see mode select table)151617 CP SUM CHECK NOT OK OK18 NAV MODE SELECTED SELECTED NOT SEL19 ADF/VOR VECTORS VECTORS NO VECT20 DF-NAV AIDS SELECTED NOT SEL21 DF-WAYPOINT SELECTED NOT SEL22 DF-ROUTE DATA SELECTED NOT SEL23 DF-AIRPORTS SELECTED NOT SEL24 MAP ORIENT TRACK UP HDG UP25 VOR/ILS ORIENT TRACK UP HDG UP26 RA ALERT RESET RESET NOT RESET27 NAV ORIENT TRACK UP HDG UP28 FULL COMPASS ROSE FULL ROSE EXP ROSE29 PAD X30-31 SSM32 Parity (Odd)

Bits Selected

1 1 1 1 1 1 Function1 2 3 4 5 6

1 0 0 0 0 0 MAP MODE SELECTED

0 1 0 0 0 0 VOR MODE SELECTED

0 0 1 0 0 0 ILS MODE SELECTED

0 0 0 1 0 0 PLAN MODE SELECTED

0 0 0 0 1 0 VOR FULL SELECTED

0 0 0 0 0 1 ILS FULL SELECTED

0 0 0 0 0 0 NO SELECTION

(All other bit patternsshall be consideredinvalid)


DATA STANDARDS

Label 272 02F


1 0

1 X2 X3 X4 Label 272 02F X5 X6 X7 X8 X9-10 SDI X11 Pad X12 Pad X13 Pad X14 N1 Loop Engaged Not Engaged15 N2 Loop Engaged Not Engaged16 N2 Topping Loop Engaged Not Engaged17 PB Topping Loop Engaged Not Engaged18 PB Topping Loop Minimum Engaged Not Engaged19 EPR Loop Engaged Not Engaged20 Accel Schedule Loop Engaged Not Engaged21 Decel Schedule Loop Engaged Not Engaged22 Spare X23 Back Up Mode Engaged Not Engaged24 2.5 BLD 2-Position Mode Engaged Not Engaged25 Spare X26 Spare X27 Spare X28 Spare X29 Spare X30-31 SSM X32 Parity (Odd)



DATA STANDARDS

Label 272 03A


1 0

1 X2 X3 X4 Label 272 03A X5 X6 X7 X8 X9-10 SDI11 RAM In-Flight Monitor Failed OK12 ROM In-Flight Monitor Failed OK13 WDT In-Flight Monitor Failed OK14 Discrete Output 1 IFM Failed OK15 Discrete Output 1 IFM Failed OK16 Serial Data Input - Pri Failed OK17 Serial Data Input - Sec Failed OK18 Spare X19 Discrete Input IFM Failed OK20 Power Up RAM Failed OK21 BIT:RAM Failed OK22 BIT:ROM Failed OK23 BIT:Discrete Output 1 Failed OK24 BIT:Discrete Output 2(Prov) Failed OK25 BIT:Discrete Input Failed OK26 BIT: Serial Data Failed OK27 BIT:Watchdog Timer Failed OK28 Spare29 Spare X30-31 SSM X32 Parity (Odd)

NOTE: Typical discrete functions are shown in the above table. Slight variationsof bit usage may arise according to the specific application.


DATA STANDARDS

Label 272 03B


1 0

1 X2 X3 X4 Label 272 03B X5 X6 X7 X8 X9-10 SDI11 Trim Wheel Enable Enabled Not Enabled12 Altitude Select Capture Engaged Not Engaged13 Flare Arm Armed Not Armed14 Flare Engage Engaged Not Engaged15 Glide Slope Arm Armed Not Armed16 Glide Slope Engage Engaged Not Engaged17 Go-Around Engage Engaged Not Engaged18 Heading Select Selected Not Selected19 Nav Engage Engaged Not Engaged20 Localizer Capture Engaged Not Engaged21222324 Spare (all "0" states)2526272829 Word Validity Invalid Valid30-31 SSM32 Parity (Odd)


DATA STANDARDS

Label 272 03F


1 0

1 X2 X3 X4 Label 272 03F X5 X6 X7 X8 X9-10 SDI X11 Pad X12 Pad X13 Pad X14 N1 Loop Engaged Not Engaged15 N2 Loop Engaged Not Engaged16 N2 Topping Loop Engaged Not Engaged17 PB Topping Loop Engaged Not Engaged18 PB Topping Loop Minimum Engaged Not Engaged19 EPR Loop Engaged Not Engaged20 Accel Schedule Loop Engaged Not Engaged21 Decel Schedule Loop Engaged Not Engaged22 Spare X23 Back Up Mode Engaged Not Engaged24 2.5 BLD 2-Position Mode Engaged Not Engaged25 Spare X26 Spare X27 Spare X28 Spare X29 Spare X30-31 SSM X32 Parity (Odd)



DATA STANDARDS

Label 272 05A - (A-320) FQS - Fuel Density


1 0

1 X2 X3 X4 272 05A (Fuel Density) X5 X6 X7 X8 X9 SDI101112 0.1 pf13-1415-1617 1 pf181920 10 pf212223 100 pf2425 probe number26 (units)2728 probe number29 (units)30-31 SSM32 Parity



DATA STANDARDS

Label 273 001 - FCC Arm Modes Discrete Word


1 0

1 X2 X3 X4 Label 273 001 X5 X6 X7 X8 X9 Unassigned10 Unassigned11 Test Requested Not Requested12 ALT Armed Not Armed13 FMC Armed Not Armed14 LNAV Armed Not Armed15 VNAV Armed Not Armed16 LOC Engaged Not Engaged17 Back Course Engaged Not Engaged18 Appr. 2 Engaged Not Engaged19 Land 2 Engaged Not Engaged20 Land 1 Armed Not Armed21 Land 3 Armed Not Armed22 Glideslope Armed Not Armed23 VOR Armed Not Armed24 Climb Armed Not Armed25 Descent Armed Not Armed2627 Unassigned282930-31 SSM32 Parity (Odd)


DATA STANDARDS

ARM MODES EXPLANATIONS

Bit No. Function

1-8 Label 273 00191011 TEST A test of interfacing systems has been requested.12 ALT The latitude preselect mode has been armed.13 FMC The lateral and vertical navigation modes of the flight management system

have been armed.14 LNAV The lateral navigation submode of the FMS is armed.15 VNAV The vertical navigation submode of the FMS is armed.16 LOC The localizer mode has been armed.17 BACK COURSE The localizer back course mode has been armed.18 APPR The approach mode has been armed.19 LAND 2 The autoland mode is armed on FCC No. 2.20 LAND 1 The autoland mode is armed on FCC No. 1.21 LAND 3 The autoland mode is armed on FCC No. 3.22 GLIDE SLOPE The glideslope mode has been armed.23 VOR The VOR mode has been armed.24 CLIMB The climb submode of the VNV basic mode is armed.25 DESCENT The Descent submode of the VNV basic mode is armed.26-29 TBD


DATA STANDARDS



1 0

1 X2 X3 X4 Label 273 003 X5 X6 X7 X8 X9-10 SDI11 No bleed air Requested Not Requested12 One air conditioning pack Requested Not Requested13 Two air conditioning packs Requested Not Requested14 Three air conditioning packs Requested Not Requested15 Half wing anti-icing Requested Not Requested16 Total wing anti-icing Requested Not Requested17 Engine cowling anti-icing Requested Not Requested18 Engine operting condition (Engine Out) Requested Not Requested19 Speed brake Position - retract Requested Not Requested20 Speed brake Position - 1/3 Requested Not Requested21 Speed brake Position - 2/3 Requested Not Requested22 Speed brake Position - full Requested Not Requested23 Landing gear position Requested Not Requested24 Slat position - retract Requested Not Requested25 Slat position - take off Requested Not Requested26 Slat position - land Requested Not Requested27 Electronic Engine Control On-Off No. 1 On Off28 Electronic Engine Control On-Off No. 2 On Off29 Electronic Engine Control On-Off No. 3 On Off30-31 SSM32 Parity (Odd)


DATA STANDARDS

Label 273 018 - TCAS Mode S Ground Uplink (SLC, IIS) Word



1 0

1 X2 X3 X4 Label 273 018 X5 X6 X7 X8 X9101112131415 Pad161718192021

RF MSG BIT22 (MSB) 4123 SLC 1 2 3 4224 4325 (LSB) 4426 1727 IIS 1828 2 1929 2030 SSM31 SSM32 Parity (odd)

Note 1: Sensitivity Level Command (SLC) NOTE 2: This data is received from the ground station in datawords UF 20 & UF 21.

BITS MEANINGNOTE 3: ARINC 429 data word fields for which there are

22 23 24 25 corresponding RF fields are transmitted with the MSBfirst in order to maintain consistency between RF and

0 0 0 0 SLC 0 ARINC 429 data. The normal ARINC 429 protocol calls for0 0 0 1 SLC 1 the transmission of the LSB of the field first.0 0 1 0 SLC 20 0 1 1 SLC 30 1 0 0 SLC 40 1 0 1 SLC 50 1 1 0 SLC 60 1 1 1 SLC 71 0 0 0

to Not Assigned

1 1 1 01 1 1 1 Cancel previous level

command


DATA STANDARDS

Label 273 025 - Discrete Data No. 2


1 0

1 X2 X3 X4 Label 273 025 X5 X6 X7 X8 X9-10 SDI1112131415 PITCH REF1617181920 FLIGHT PATH DATA ON OFF21 PAD X22 FPA DISABLE OFF ON23 WEATHER RADAR DATA SELECT SEL NOT SEL24 RANGE SELECTED252627 (see range table)282930-31 SSM32 Parity (Odd)

Bits Range

2 2 2 2 2 2 Selected4 5 6 7 8 9

1 0 0 0 0 0 5 MILES (not used)

0 1 0 0 0 0 10 MILES

0 0 1 0 0 0 20 MILES

0 0 0 1 0 0 40 MILES

0 0 0 0 1 0 80 MILES

0 0 0 0 0 1 160 MILES

0 0 0 0 0 0 320 MILES

(All other bit patternsare considered invalid)


DATA STANDARDS

Label 273 02F


1 0

1 X2 X3 X4 Label 273 02F X5 X6 X7 X8 X9-10 SDI X11 X12 Pad X13 X14 P4.9 Interface Failed OK15 PB Interface Failed OK16 P2 (P amb) Interface* Failed OK17 CJC Interface Failed OK18 T2 Interface Failed OK19 T4.9 Interface Failed OK20 Tfuel /T oil Interface Failed OK21 A/D Interface Failed OK22 RES/LVDT Interface Failed OK23 SVA Interface Failed OK24 N1 Interface Failed OK25 N2 Interface Failed OK26 P4.9 Sensor PROM Failed OK27 P2 (P amb) Sensor PROM* Failed OK28 PB Sensor PROM Failed OK29 Background Execution Not Executing Executing30-31 SSM X32 Parity (Odd)* Primary channel uses P 2; Secondary channel uses P amb



DATA STANDARDS

Label 273 035 - TCAS Output Discrete (ARA, RAC)

TCAS To Transponder And Displays - Bus 2 Word 1


1 0


RF MSG BIT12 4113 4214 4315 4416 4517 ARA 1 4618 4719 4820 4921 5022 5123 5224 5325 5426 5527 RAC 1 5628 5729 5830 SSM31 SSM32 Parity (Odd)

NOTE 1: Sent by own transponder in DF 16, 20 and 21.


DATA STANDARDS

Label 273 03B


1 0

1 X2 X3 X4 Label 273 03B X5 X6 X7 X8 X9-10 SDI11 A/P Red Warning Lights Warn Normal12 A/P Servo System Pitch/Roll Failed Normal13 A/P Servo System Yaw Failed Normal14 A/P Camout Pitch Camout Normal15 A/P Camout Roll Camout Normal16 A/P Camout Yaw Camout Normal17 A/P Confidence Test Failed Passed18 Spare (Pad Bit) X19 Spare (Pad Bit) X20 A/T Red Warning Lights Warn Normal21 A/T Speed Flag Flag Normal222324 Spare (all "0" states)2526272829 Word Validity Invalid Valid30-31 SSM32 Parity (Odd)


DATA STANDARDS

Label 273 03F


1 0

1 X2 X3 X4 Label 273 03F X5 X6 X7 X8 X9-10 SDI X11 X12 Pad X13 X14 P4.9 Interface Failed OK15 PB Interface Failed OK16 P2 (P amb) Interface* Failed OK17 CJC Interface Failed OK18 T2 Interface Failed OK19 T4.9 Interface Failed OK20 Tfuel /T oil Interface Failed OK21 A/D Interface Failed OK22 RES/LVDT Interface Failed OK23 SVA Interface Failed OK24 N1 Interface Failed OK25 N2 Interface Failed OK26 P4.9 Sensor PROM Failed OK27 P2 (P amb) Sensor PROM* Failed OK28 PB Sensor PROM Failed OK29 Background Execution Not Executing Executing30-31 SSM X32 Parity (Odd)* Primary channel uses P 2; Secondary channel uses P amb



DATA STANDARDS

Label 273 05A - (A-320) FQS - Right Wing


1 0

1 X2 X3 X4 273 05A (Right Wing) X5 X6 X7 X8 X9 SDI101112 0.1 pf13-1415-1617 1 pf181920 10 pf212223 100 pf2425 probe number26 (units)2728 probe number29 (units)30-31 SSM32 Parity



DATA STANDARDS

Label 274 001 - FCC Pitch Modes Discrete Word


1 0

1 X2 X3 X4 Label 274 001 X5 X6 X7 X8 X9 Descent Requested Not Requested10 Climb Requested Not Requested11 IAS Requested Not Requested12 VNAV Requested Not Requested13 ALT Requested Not Requested14 V/S Requested Not Requested15 Flare Requested Not Requested16 Pitch G/A Requested Not Requested17 Pitch T/O Requested Not Requested18 Mach Requested Not Requested19 Glideslope Requested Not Requested20 Flap Speed Requested Not Requested21 Min Speed Requested Not Requested22 Track Requested Not Requested23 Pitch Limit Requested Not Requested24 Turb. Requested Not Requested25 CWS Requested Not Requested26 Hold Requested Not Requested27 Performance Requested Not Requested28 Pitch Requested Not Requested29 Capture Requested Not Requested30-31 SSM32 Parity


DATA STANDARDS

PITCH MODES EXPLANATIONS

Bit No. Function

11 IAS The "Airspeed" reference mode is selected.12 VNAV The pitch axis "Vertical Navigation" mode is selected.13 ALT The "Altitude" reference mode is selected.14 V/S The "Vertical Speed" reference mode is selected.15 FLARE The "Flare" phase of the autoland mode is engaged.16 PITCH G/A The Pitch Axis "Go Around" mode is engaged.17 PITCH T/O The Pitch Axis is engaged in the "Take Off" mode.18 MACH The "Mach" reference speed mode is selected.19 GLIDE SLOPE The "Glideslope" guidance mode is selected.20 FLAP SPEED The aircraft is being controlled to a speed which is limited by the flap

setting.21 MIN SPEED The aircraft is being controlled to the minimum speed for its configuration.22 TRACK The "Track" phase of the selected mode is engaged.23 PITCH LIMIT The aircraft pitch attitude is veing controlled to the maximum value.24 TURB The pitch axis "Turbulence" penetration mode is engaged.25 CWS The pitch axis is engaged in the "CWS" mode.26 HOLD The aircraft is holding a preselected value of altitude, attitude or speed.27 PERFORMANCE The "Performance" submode of the Flight Management Vertical Navigation mode

is engaged.28 PITCH The Pitch Attitude Mode is selected.29 CAPTURE The "Capture" phase of the selected mode is engaged.


DATA STANDARDS



1 0

1 X2 X3 X4 Label 274 003 X5 X6 X7 X8 X9 DFA Mode Armed Armed Not Armed10 DFA Mode Engaged Engaged Not Engaged11 ATS OFF OFF Passive12 ATS Armed Armed Passive13 ATS Mode Engaged Engaged Passive14 Left Clutch Off Off Passive15 Right Clutch Off Off Passive16 Both Clutches Off Off Passive17 VNV The automatic throttles are engaged in the vertical Engaged Not Engaged

navigation mode and controlling in accordance with asubmode designated by bits 23 thru 26 and 29.

18 ATS N1/EPR Mode Engaged Engaged Not Engaged19 EPR Engaged Not Engaged20 ATS Mach Mode Engaged Engaged Not Engaged21 ATS Speed Mode Engaged Engaged Not Engaged22 ATS Retard Activated Engaged Not Engaged23 IAS The IAS submode of VNV basic mode currently in effect. In Effect Not In Effect

Used with bit 17.24 MACH The Mach submode of VNV basic mode currently in In Effect Not In Effect

effect. Used with bit 17.25 ALT The altitude hold submode of VNV basic mode is In Effect Not In Effect

currently in effect. Used with bit 17.26 TRK The climb (descent) path-track submode of the VNV In Effect Not In Effect

basic mode is currently in effect. Used with bit 17.27 ATS Alpha Mode Activated Activated Not Activated28 ATS Throttle Pusher Activated (Alpha Floor Protection) Activated Not Activated29 PERF The Performance submode of the VNV basic mode is in In Effect Not In Effect

effect. Used with bit 17.30-31 SSM32 Parity


DATA STANDARDS

Label 274 018 - TCAS Coordination Discrete (MID Part 2)



1 0

1 X2 X3 X4 Label 274 018 X5 X6 X X7 X8

MID (Part 2) RF MSG BIT9 MID BIT A17 8110 MID BIT A18 8211 MID BIT A19 8312 MID BIT A20 8413 MID BIT A21 8514 MID BIT A22 8615 MID BIT A23 8716 MID BIT A24 (LSB) 8817 Pad18 Pad19 Pad20 Pad21 Pad22 Pad23 Pad24 Pad25 Pad26 Pad27 Pad28 Pad29 Pad30 SSM31 SSM32 Parity (odd)

NOTE: ARINC 429 data word fields for which there are corresponding RF fields are transmitted with the MSB firstin order to maintain consistency between RF and ARINC 429 data. Normal ARINC 429 protocol calls for thetransmission of the LSB of the field first.


DATA STANDARDS

Label 274 02F


1 0

1 X2 X3 X4 Label 274 02F X5 X6 X7 X8 X9 SDI X10 SDI X11 X12 PAD X13 X14 Parity Test Hardware Error OK15 ROM Checksum Failed OK16 RAM Test Failed OK17 Instruction Test Failed OK18 High Speed Cross Link Text Failed OK19 Foreground Software Execution Incorrect Correct20 Watchdog Timer Error OK21 Spare X22 EAROM Failed OK23 ROM Parity Error Caused Reset Yes No24 RAM Parity Error Caused Reset Yes No25 Watchdog Timer Error Caused Reset Yes No26 Status Buffer Failed OK27 Loss of Clock Caused Reset Yes No28 SDD Output #1 W/A Failed OK29 SDD Output #2 W/A Failed OK30 SSM X31 SSM X32 Parity (Odd)

NOTE: Typical discrete functions are shown in the above table. Slight variations of bit usage may arise according tothe specific application.


DATA STANDARDS

Label 274 035 - TCAS Output Discrete (SL, R1)

TCAS To Transponder And Displays - Bus 2 Word 2


1 0


RF MSG BIT23 SL (MSB) 924 SL 1 2 1025 SL 1126 R1 (MSB) 1427 R1 1 2 1528 R1 1629 R1 1730 SSM31 SSM32 Parity (odd)

NOTE 1: Sent by own transponder in data word DF, 0, 16.

NOTE 2: ARINC 429 data word fields for which there are corresponding RF fields are transmitted with the MSBfirst 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.


DATA STANDARDS

Label 274 03B


1 0

1 X2 X3 X4 Label 274 03B X5 X6 X7 X8 X9-10 SDI11 Magnetic Heading Flag Flag Normal12 Localizer Flag Flag Normal13 Glide Slope Flag Flag Normal14 Low Range Radio Altimeter Flag Normal15 ILS Limit Warn Warn Not Selected16 ILS Frequency Select Selected Normal17 INS Altitude Secondary Flags Flag Normal18 INS True Heading Flags Flag Normal19 INS HSI Nav Warn Warn Normal20 CADC True Airspeed Flags Flag Normal21 CADC Computer Airspeed Flags Flag Normal22 CADC Corrected Altitude Flags Flag Normal23 CADC Uncorrected Altitude Flag Flag Normal24 CADC Mach Flag Flag Normal25 Altitude Rate Module Flag Flag Normal26 Spare (Pad Bit) X27 Spare (Pad Bit) X28 Spare (Pad Bit) X29 Word Validity Invalid Valid30-31 SSM32 Parity (Odd)


DATA STANDARDS

Label 274 03F


1 0

1 X2 X3 X4 Label 274 03F X5 X6 X7 X8 X9 SDI X10 SDI X11 X12 PAD X13 X14 Parity Test Hardware Error OK15 ROM Checksum Failed OK16 RAM Test Failed OK17 Instruction Test Failed OK18 High Speed Cross Link Text Failed OK19 Foreground Software Execution Incorrect Correct20 Watchdog timer Error OK21 Spare X22 EAHOM Failed OK23 ROM Parity Error Caused Reset Yes No24 RAM Parity Error caused Reset Yes No25 Watchdog Timer Error Caused Reset Yes No26 Status Buffer Failed OK27 Loss of Clock Caused Reset Yes No28 SDD Output #1 W/A Failed OK29 SDD Output #2 W/A Failed OK30 SSM X31 SSM X32 Parity (Odd)

NOTE: Typical discrete functions are shown in the above table. Slight variations of bit usage may arise according tothe specific application.


DATA STANDARDS

Label 274 05A - (A-320) FQS - Center


1 0

1 X2 X3 X4 274 05A (Center) X5 X6 X7 X8 X9 SDI101112 0.1 pf13-1415-1617 1 pf181920 10 pf212223 100 pf2425 probe number26 (units)2728 probe number29 (units)30-31 SSM32 Parity



DATA STANDARDS

Label 274 0C5 - EFIS CP

ENCODINGBit No. Function

1 0

1-8 Label 274 0C59-10 SDI11 Spare12 Spare13 Spare14 Spare15 Spare16 Spare17 BARO SEL IN SEL NOT SEL18 BARO SEL HPA SEL NOT SEL19 BARO SEL MTRS SEL NOT SEL20 FPV SEL NOT SEL21 METRIC ALT SEL NOT SEL22 WXR DATA SEL NOT SEL23-29 MAP RANGE SEL NOT SEL23-29 MAP RANGE SEL NOT SEL23-29 MAP RANGE SEL NOT SEL23-29 MAP RANGE SEL NOT SEL23-29 MAP RANGE SEL NOT SEL23-29 MAP RANGE SEL NOT SEL23-29 MAP RANGE SEL NOT SEL30-31 SSM30-31 SSM32 Parity (Odd)

MAP RANGE MATRIX

BIT POSITIONS 29 28 27 26 25 24 23 RANGE

0 0 0 0 0 1 0 5 MILES0 0 0 0 1 0 0 100 0 0 1 0 0 0 200 0 1 0 0 0 0 400 1 0 0 0 0 0 801 0 0 0 0 0 0 1600 0 0 0 0 0 0 3200 0 0 0 0 0 1 640

SSM MATRIX

BIT POSITIONS 31 30

0 0 VALID DATA (WXR)0 1 INVALID DATA (WXR)


DATA STANDARDS

Label 275 001 - FCC Roll Modes Discrete Word


1 0

1 X2 X3 X4 Label 275 001 X5 X6 X7 X8 X9 Unassigned10 Unassigned11 LNAV Requested Not Requested12 HDG HOLD Requested Not Requested13 HDG SEL Requested Not Requested14 B/COURSE VOR Requested Not Requested15 LOC Requested Not Requested16 ROLLOUT Requested Not Requested17 ROLL T.O. Requested Not Requested18 ROLL G/A Requested Not Requested19 Unassigned20 WINGS LEVEL Requested Not Requested21 CAPTURE Requested Not Requested22 VOR Requested Not Requested23 TRACK Requested Not Requested2425 Unassigned262728 ALIGN Requested Not Requested29 CWS Requested Not Requested30-31 SSM32 Parity


DATA STANDARDS

ROLL MODES EXPLANATIONS

Bit No. Function

11 LNAV The "Lateral Navigation" mode is selected.12 HDG HOLD The "Heading Hold" mode is engaged.13 HDG SEL The "Heading Select" mode is engaged.14 B/COURSE VOR The "Backcourse" or "VOR" mode is selected.15 LOC The "Localizer" guidance mode is selected.16 ROLL OUT The "Roll Out" phase of the autoland mode is engaged.17 ROLL T.O. The Roll Axis "Take Off" mode is engaged.18 ROLL G/A The Roll Axis "Go Around" mode is engaged.20 WINGS LEVEL The Roll Axis "Turbulence" penetration mode is engaged.21 CAPTURE The "Capture" phase of the selected mode is engaged.22 VOR The "VOR" mode is selected.23 TRACK The "Track" phase of the selected mode is engaged.28 ALIGN The "Align" phase of the autoland mode is engaged.29 CWS The Roll Axis "CWS" mode is engaged.


DATA STANDARDS



1 0

1 X2 X3 X4 Label 275 003 X5 X6 X7 X8 X9-10 SDI11 Engine Type 1 High Low12 Engine Type 2 High Low13 Engine Type 3 Encoded to define one of 32 types High Low14 Engine Type 4 High Low15 Engine Type 5 High Low16 LIM Automatic throttle control is currently limited by In Effect Not In Effect

flap or slat maximum speeds, or by engine limits (N1or EPR), or by throttle low limit protection.

17 TO Mode Engaged Engaged Not Engaged18 FLX TO Mode Engaged Engaged Not Engaged19 Climb Mode Engaged Engaged Not Engaged20 Cruise Mode Engaged Engaged Not Engaged21 Maximum Continuous Thrust Mode Engaged Engaged Not Engaged22 GA Mode Engaged Engaged Not Engaged23 FLP Used with bit 16 to designate flap limit control. In Effect Not In Effect

currently in effect.24 N1/EPR Limit Failure/Warning25 SLT Used with bit 16 to designate slat limit. In Effect Not In Effect26 N1 The automatic throttles are engaged in the N1 basic Engaged Not Engaged

mode and control to a selected N1 limit defined bybits 17 thru 22. Also used with bit 16.

27 Test Test Normal28 Spare29 EPR The automatic throttles are engaged in the EPR basic Engaged Not Engaged

mode and control to a selected N1 limit defined bybits 17 thru 22. Also used with bit 16.

30-31 SSM32 Parity


DATA STANDARDS

Label 275 018 - TCAS Control Discrete (MODE S Address Part 1)



1 0


Mode S Address(Part 1)

14 BIT A1 (MSB)15 BIT A216 BIT A317 BIT A418 BIT A519 BIT A6 120 BIT A721 BIT A822 BIT A9 223 BIT A1024 BIT A1125 BIT A1226 BIT A1327 BIT A1428 BIT A1529 BIT A16 (LSB)30-31 SSM32 Parity (odd)

NOTE 1: Sent by own TCAS in data word UF-16.




DATA STANDARDS

Label 275 02F


1 0

1 X2 X3 X4 Label 275 02F X5 X6 X7 X8 X9-10 SDI X11 X12 PAD X13 X14 Lamp 1,2 &/or 3 W/A Failed OK15 Other Channel’s Depower Discretes Disagree Agree16 PB Sensor Failed OK17 P4.9 Sensor Failed OK18 P2 P( amb)** Sensor Failed OK19 PBSensor Crosscheck* Failed OK20 P4.9 Sensor Crosscheck* Failed OK21 Serial Data Receiver Failed OK22 Serial Data Transmitter Failed OK23 Activity Monitor Failed OK24 Other Channel’s Depower Logic Failed OK25 Pressure Sensors Correlation Disagree Agree26 PB Heater Failed OK27 Automatic Channel Transfer* Failed OK28 Pamb Sensor Drift* Failed OK29 Spare X30-31 SSM X32 Parity (Odd)

* Primary channel only.** Primary channel uses P 2: Secondary channel uses P amb



DATA STANDARDS

Label 275 035 - Acknowledgement (ACK/NAK) Discrete

TCAS To Transponder - Bus 2 Word 3


1 0

1 X2 X3 X4 Label 275 035 X5 X6 X7 X8 X91011121314151617 Pad181920212223242526272829 ACK/NAK ACK NAK30 SSM31 SSM32 Parity (Odd)


DATA STANDARDS

Label 275 03B


1 0

1 X2 X3 X4 Label 275 03B X5 X6 X7 X8 X9-10 SDI11 A/T Engage Engage Not Engaged12 A/T Alternate Rating I Engage Not Engaged13 A/T Alternate Rating II Engage Not Engaged14 A/T Alpha Engage Not Engaged15 A/T Flag Limit Engage Not Engaged16 A/T Retard Engage Not Engaged17 A/T Mach Engage Not Engaged18 A/T Speed Engage Not Engaged19 A/T EPR Engage Not Engaged20 A/T Throttle Hold Engage Not Engaged21 A/T Go Around Engage Not Engaged22232425 Spare (all "0" states)26272829 Word Validity Invalid Valid30-31 SSM32 Parity (Odd)


DATA STANDARDS

Label 275 03F


1 0

1 X2 X3 X4 Label 275 03F X5 X6 X7 X8 X9-10 SDI X11 X12 PAD X13 X14 Lamp 1,2 &/or 3 W/A Failed OK15 Other Channel’s Depower Discretes Disagree Agree16 PB Sensor Failed OK17 P4.9 Sensor Failed OK18 P2 P( amb)** Sensor Failed OK19 PBSensor Crosscheck* Failed OK20 P4.9 Sensor Crosscheck* Failed OK21 Serial Data Receiver Failed OK22 Serial Data Transmitter Failed OK23 Activity Monitor Failed OK24 Other Channel’s Depower Logic Failed OK25 Pressure Sensors Correlation Disagree Agree26 PB Heater Failed OK27 Automatic Channel Transfer* Failed OK28 Pamb Sensor Drift* Failed OK29 Spare X30-31 SSM X32 Parity (Odd)

* Primary channel only.** Primary channel uses P 2: Secondary channel uses P amb



DATA STANDARDS

Label 275 05A - (A-320) FQS - Left Wing


1 0

1 X2 X3 X4 275 05A (Left Wing) X5 X6 X7 X8 X9 SDI101112 0.1 pf13-1415-1617 1 pf181920 10 pf212223 100 pf2425 probe number26 (units)2728 probe number29 (units)30-31 SSM32 Parity



DATA STANDARDS

Label 276 018 - TCAS Control Discrete (Mode S Address Part 2, Max A/S)



1 0

1 X2 X3 X4 Label 276 018 X5 X6 X78 X9 Aural Advisory Cancel and Cancel Normal

Visual Annunciator10 R1 Echo 111 Pad12 Pad

Mode S Address(Part 2) RF MSG BIT

(MSB) 8113 BIT A17 8214 BIT A18 8315 BIT A19 2 8416 BIT A20 8517 BIT A21 3 8618 BIT A22 8719 BIT A23 8820 BIT A24 (LSB) 1421 (MSB) 1522 Maximum 1623 Airspeed 3 1724 (LSB)25 Pad26 Pad27 Pad28 Pad29 Pad30 SSM31 SSM32 Parity (odd)

NOTE 1: See Attachment 12 of ARINC Characteristic 735 for logic encoding of the R1 field.

NOTE 2: Sent by own transponder in DF-0, 16.




DATA STANDARDS



1 0

1 X2 X3 X4 Label 276 025 X5 X6 X7 X8 X9-10 SDI11 RESERVED12 RESERVED13 RESERVED14 RESERVED15 RESERVED16 RESERVED17 RESERVED18 RESERVED19 RESERVED20 RESERVED21 RESERVED22 RESERVED23 RESERVED24 RESERVED25 RESERVED26 RESERVED27 PAD X28 PAD X29 PAD X30-31 SSM32 Parity (Odd)


DATA STANDARDS

Label 276 02F


1 0

1 X2 X3 X4 Label 276 02F X5 X6 X7 X89-10 SDI X11 X12 PAD X13 X14 EEC Channel Failed OK15 EEC Unit Failed OK16 Resolver/ LVDT Excitation Failed OK17 Spare X18 Spare X19 FCU Functions Failed OK20 HCC Functions Failed OK21 LCC Functions Failed OK22 2.5 Bleed Functions W/A Failed OK23 Spare X24 Spare X25 Spare X26 Spare X27 Spare X28 EEC Temperature Status High OK29 Overspeed Test** Failed OK30-31 SSM X32 Parity (Odd)

** Second channel only.



DATA STANDARDS

Label 276 03F


1 0

1 X2 X3 X4 Label 276 03F X5 X6 X7 X89-10 SDI X11 X12 PAD X13 X14 EEC Channel Failed OK15 EEC Unit Failed OK16 Resolver/ LVDT Excitation Failed OK17 Spare X18 Spare X19 FCU Functions Failed OK20 HCC Functions Failed OK21 LCC Functions Failed OK22 2.5 Bleed Functions W/A Failed OK23 Spare X24 Spare X25 Spare X26 Spare X27 Spare X28 EEC Temperature Status High OK29 Overspeed Test** Failed OK30-31 SSM X32 Parity (Odd)

** Second channel only.



ATTACHMENT 2 (cont’d)DATA STANDARDS

Label 277 018 - Acknowledgement (ACK/NAK) Discrete



1 0

1 X2 X3 X4 Label 277 018 X5 X6 X7 X8 X9101112131415161718 Pad1920212223242526272829 ACK/NAK ACK NAK30 SSM31 SSM32 Parity (Odd)


DATA STANDARDS



1 0

1 X2 X3 X4 Label 350 01A X5 X6 X7 X8 X9-10 SDI11 Pad X12 Pad X13 Pad X14 Pad X15 Connector J2 Not Inst. Inst.16 Connector J5 Not Inst. Inst.17 T2 Probe Failed Good18 EGT Assy. Failed Good19 TLA Resol. Failed Good20 RPX Failed Good21 A Chan SDD In Failed Good22 B Chan SDD In Failed Good23 Coil Failed Good24 Stg I Valve Malfunction Good25 P2 Leak Leak Good26 System Trim Required Good27 TCA-A Valve Malfunction Good28 TCA-B Valve Malfunction X29 Spare30-31 SSM32 Parity (Odd)


DATA STANDARDS

Label 350 027 - MLS Fault Summary


1 0

1-8 Label (Octal) 350 0279-10 SDI11 LRU Failure Failure OK12 #1 Antenna Failure Failure OK13 #2 Antenna Failure Failure OK14 #3 Antenna Failure Failure OK15 Source Selection Port A Port B16 Input Data Inactive OK17 CFDIU Input Bus Inactive OK18 Battery Low Warning Low OK19 Resv. MIL-STD-1553B Input Bus Inactive OK20 Resv. DME Input Bus Inactive OK21 Resv. DME Tuning Interface Failure OK22 Resv. Synchro Reference Invalid Failure OK232425262728 Bite Test Inhibit Inhibit Enable29 Commmand Word Acknowledge ACK NAK30 SSM31 SSM32 Parity (Odd)

NOTE: Transmission interval min. 50 ms, max. 250 ms.


DATA STANDARDS

Label 350 02F


1 0

1 X2 X3 X4 Label 350 02F X5 X6 X7 X8 X9-10 SDI X11 X12 PAD X13 X14 N1 Signal Failed OK15 N2 Signal Failed OK16 T2 Signal Failed OK17 T4.9 Signal Failed OK18 Tfuel Signal Failed OK19 Toil Signal Failed OK20 Wf Feedback Signal Failed OK21 SVA Feedback Signal Failed OK22 2.5 BLD Feedback Signal Failed OK23 HCC Feedback Signal Failed OK24 LCC Feedback Signal Failed OK25 Reverser Position Signal Failed OK26 AOX Feedback Signal Failed OK27 Reserved (Spare Feedback Signal) X28 Thrust Lever Position Signal Failed OK29 Spare X30-31 SSM X32 Parity (Odd)



DATA STANDARDS

Label 350 03D - Maintenance Data #1


1 X2 X3 X4 Label 350 03D X5 X6 X7 X8 X9-10 SDI11-28 Data30-31 Status Matrix32 Parity (Odd)

Bits Data

10 9

0 0 Engine 4 (or All Call) {Not used on 757}0 1 Engine 1 (or Engine 1 and 2)1 0 Engine 21 1 Engine 3 (or Engine 3 and 4)

Bit Data

11 Signal Conditioner Status12 N1 Tachometer Signal Loss13 N2 Tachometer Signal Loss

*14 PAD**14 N3 Tachometer Signal Loss

15 Ch A Accelerometer High Noise***15 PAD

16 Ch B Accelerometer High Noise***16 PAD

17 Channel A <> Channel B***17 PAD

*18 PAD**18 High Broadband Levels

*19 PAD**19 Ch A Accelerometer Low Signal

*20 PAD**20 Ch B Accelerometer Low Signal

21 PAD22 PAD23 PAD24 PAD25 PAD26 PAD27 PAD28 Unit Not Available29 Command Word Acknowledge

* 757 Pratt and Whitney and 737 CFM Only (Reserved)** 757 Rolls Royce Only*** 757 Only

REVISED: November 17, 1986ARINC SPECIFICATION 429 PART 2- Page 105

DATA STANDARDS

Label 350 03F


1 0

1 X2 X3 X4 Label 350 03F X5 X6 X7 X8 X9-10 SDI X11 X12 PAD X13 X14 N1 Signal Failed OK15 N2 Signal Failed OK16 T2 Signal Failed OK17 T4.9 Signal Failed OK18 Tfuel Signal Failed OK19 Toil Signal Failed OK20 Wf Feedback Signal Failed OK21 SVA Feedback Signal Failed OK22 2.5 BLD Feedback Signal Failed OK23 HCC Feedback Signal Failed OK24 LCC Feedback Signal Failed OK25 Reverser Position Signal Failed OK26 AOX Feedback Signal Failed OK27 Reserved (Spare Feedback Signal) X28 Thrust Lever Position Signal Failed OK29 Spare X30-31 SSM X32 Parity (Odd)



DATA STANDARDS

Label 350 114 - Fuel Unit Management System Discrete (A-330/A-340)


1 0

1 X2 X3 X4 Label 350 114 X5 X6 X7 X8 X9 SDI10111213 Fuel Density (0.0001’s)14151617 Fuel Density (0.001’s)18192021 Fuel Density (0.01’s)22232425 Fuel Density (0.1’s)262728 Tank Ident2930 SSM31 SSM32 Parity (Odd)


DATA STANDARDS

Label 350 115 - TACAN Discrete


1 0

1 X2 X3 X4 Label 350 115 X5 X6 X7 X8 X9 LSB101112 AGC13 (X 1/256 FULL SCALE)141516 MSB17 CPU Failed OK18 RAM Failed OK19 ROM Failed OK20 2 PORT RAM Failed OK21 2 PORT DATA Failed OK22 NOVRAM Failed OK23 SYNTHESIZER Failed OK24 RECEIVER Failed OK25 POWER SUPPLY Failed OK26 XMIT POWER Failed OK27 AUDIO Failed OK28 POWER UP Failed OK29 SUPPRESSION Present Not Present30 D/A Failed OK31 TACAN FAIL Failed OK32 Parity (Odd)

NOTE: Bite 21 thru 28 indicate self test status information.


DATA STANDARDS



1 0

1 X2 X3 X4 Label 351 01A X5 X6 X7 X8 X9-10 SDI11 Pad X12 Pad X13 Pad X14 Pad X15 ARINC Transmitter Fail Good16 RPX Drift Fail Good17 RPX Test Fail Good18 TLA Correl Test Fail Good19 Resolver Test Fail Good20 Resolver Drift Fail Good21 Angle Range Check Fail Good22 Sine Range Check Fail Good23 Cosine Range Check Fail Good24 Spare X25 LLDC Test #1 Fail Good26 LLDC Drift #1 Fail Good27 P2 Range Check (Boeing Only) Fail Good28 P7 Range Check Fail Good29 EPR Range Check Fail Good30-31 SSM32 Parity (Odd)


DATA STANDARDS

Label 351 02F


1 0

1 X2 X3 X4 Label 351 02F X5 X6 X7 X8 X9-10 SDI X11 X12 PAD X13 X14 Local ADC Inputs (Pri-Left, Failed OK

Sec-Right)15 Crosstalk ADC Inputs* Failed OK16 Wf T/M W/A Failed OK17 SVA T/M W/A Failed OK18 2.5 BLD T/M W/A Failed OK19 HCC T/M W/A Failed OK20 LCC T/M W/A Failed OK21 AOX T/M W/A Failed OK22 Spare X23 Wf Track Check Failed OK24 SVA Track Check Failed OK25 2.5 BLD Track Check Failed OK26 HCC Track Check Failed OK27 LCC Track Check Failed OK28 AOX Track Check Failed OK29 Reserved (Spare Track Check) X30-31 SSM X32 Parity (Odd)




DATA STANDARDS

Label 351 03F


1 0

1 X2 X3 X4 Label 351 03F X5 X6 X7 X8 X9-10 SDI X11 X12 PAD X13 X14 Local ADC Inputs (Pri-Left, Failed OK

Sec-Right)15 Crosstalk ADC Inputs* Failed OK16 Wf T/M W/A Failed OK17 SVA T/M W/A Failed OK18 2.5 BLD T/M W/A Failed OK19 HCC T/M W/A Failed OK20 LCC T/M W/A Failed OK21 AOX T/M W/A Failed OK22 Spare X23 Wf Track Check Failed OK24 SVA Track Check Failed OK25 2.5 BLD Track Check Failed OK26 HCC Track Check Failed OK27 LCC Track Check Failed OK28 AOX Track Check Failed OK29 Reserved (Spare Track Check) X30-31 SSM X32 Parity (Odd)




DATA STANDARDS



1 0

1 X2 X3 Label 351 114 (Left Wing) X4 X5 X6 X7 X8 X9 SDI10111213 Probe Capacitance (0.1’s)14151617 Probe Capacitance (1’s)18192021 Probe Capacitance (10’s)2223 Probe Capacitance (100’s)242526 Probe Number (1’s)272829 Probe Number (10’s)30 SSM31 SSM32 Parity (Odd)


DATA STANDARDS



1 0

1 X2 X3 X4 Label 352 01A X5 X6 X7 X8 X9-10 SDI11 Pad X12 Pad X13 Pad X14 Pad X15 EGT Loop Sel/Fail Fail Good16 N2 Fail Good17 P7 Test Fail Good18 N2/P2 Test Fail Good19 T/M, D/A or Driver Fail Good20 T/M "Undetermined" Fail Good21 Pres Temp Inputs Fail Good22 Latch Solenoid W/A Fail Good23 Health Indicator W/A Fail Good24 ROM Sum Test Fail Good25 RAM Test Fail Good26 Watchdog Timer Fail Good27 Instruction Test Fail Good28 Watchdog Resets Fail Good29 Converter Reset Fail Good30-31 SSM32 Parity (Odd)


DATA STANDARDS

Label 352 02F


1 0

1 X2 X3 X4 Label 352 02F X5 X6 X7 X8 X9-10 SDI X11 X12 PAD X13 X14 DC Power Group 1 Failed OK15 DC Power Group 2 Failed OK16 Spare X17 EEC to PDIU SDD Failed OK18 PDIU Self Test Failed OK19 HCC T/M W/A Failed OK20 Local TCA Valve (Pri-Left, Failed OK

Sec-Right)21 Crosstalk TCA Valve Check* Failed OK22 Spare X23 SDD Input from PDIU Failed OK24 N1 Sensor (Pri and Sec)* Failed OK25 PB Pneumatic Line* Failed OK26 P4.9 Pneumatic Line* Failed OK27 P2 Probe / Line* Failed OK28 Fire Warn. Discrete Disagreement* Disagree OK29 Data Entry Plug Failed OK30-31 SSM X32 Parity (Odd)




DATA STANDARDS

Label 352 03F


1 0

1 X2 X3 X4 Label 352 03F X5 X6 X7 X8 X9-10 SDI X11 X12 PAD X13 X14 DC Power Group 1 Failed OK15 DC Power Group 2 Failed OK16 Spare X17 EEC to PDIU SDD Failed OK18 PDIU Self Test Failed OK19 HCC T/M W/A Failed OK20 Local TCA Valve (Pri-Left, Failed OK

Sec-Right)21 Crosstalk TCA Valve Check* Failed OK22 Spare X23 SDD Input from PDIU Failed OK24 N1 Sensor (Pri and Sec)* Failed OK25 PB Pneumatic Line* Failed OK26 P4.9 Pneumatic Line* Failed OK27 P2 Probe / Line* Failed OK28 Fire Warn. Discrete Disagreement* Disagree OK29 Data Entry Plug Failed OK30-31 SSM X32 Parity (Odd)




DATA STANDARDS



1 0

1 X2 X3 Label 352 114 (Center/Trim) X4 X5 X6 X7 X8 X9 SDI10111213 Probe Capacitance (0.1’s)14151617 Probe Capacitance (1’s)18192021 Probe Capacitance (10’s)2223 Probe Capacitance (100’s)242526 Probe Number (1’s)272829 Probe Number (10’s)30 SSM31 SSM32 Parity (Odd)


DATA STANDARDS



1 0

1 X2 X3 X4 Label 353 01A X5 X6 X7 X8 X9-10 SDI11 Pad X12 Pad X13 Pad X14 Pad X15 Spare X16 EGT Loop Disabled Yes No17 Synth Altitude Yes No18 Synth Mach Number Yes No19 SDD ’A’ W/A Failure Good20 ADD ’B’ W/A Failure Good21 Probe Heat (Boeing 767 Only) Disagreement Normal22 Pressure Accuracy Degraded Normal23 T/M Coil Yes No24 TCC Schedule (Airbus Default Normal25 Acft Pt Used 310,000 Yes No26 P2 Range Check Only) Failed Good27 TCA System Failed Good28 TCC System Failed Good29 System Trim Required Okay30-31 SSM32 Parity (Odd)


DATA STANDARDS

Label 353 02F


1 0

1 X2 X3 X4 Label 353 02F X5 X6 X7 X8 X9-10 SDI X11 X12 PAD X13 X14 N1 Crosscheck* Failed OK15 N2 Crosscheck* Failed OK16 Spare X17 Spare X18 T2 Crosscheck* Failed OK19 T2 Probe/ADC T 2 Disagreement Disagree OK20 Tfuel Crosscheck* Failed OK21 Toil Crosscheck* Failed OK22 Wf Feedback Crosscheck* Failed OK23 SVA Feedback Crosscheck Failed OK24 2.5 BLD Feedback Crosscheck* Failed OK25 HCC Feedback Crosscheck* Failed OK26 LCC Feedback Crosscheck* Failed OK27 Reverser Position Crosscheck* Failed OK28 AOX Feedback Crosscheck Failed OK29 Thrust Lever Position Crosscheck* Failed OK30-31 SSM X32 Parity (Odd)




DATA STANDARDS

Label 353 03D - Maintenance Data #4 Highest Vibration


1 X2 X3 X4 Label 353 03D X5 X6 X7 X8 X9-10 SDI11-12 Accelerometer Source13 X14 X15 PADS X16 X17 X18-19 Data ID20-28 Data29-31 SSM32 Parity (Odd)

Bits Data Bits Data

10 9 12 11

0 0 Engine 4 0 0 No Channel in commmand0 1 Engine 1 0 1 Channel A1 0 Engine 2 1 0 Channel B1 1 Engine 3

* Data ID

Bits Data

19 18

0 0 N1 Vibration (Label 354)0 1 N2 Vibration (Label 355)1 0 N3 Vibration (Label 356)1 1 BB Vibration (Label 357)

* 737 Data ID

Bits Data

19 18

0 0 CN1 Vibration (Label 354)0 1 CN2 Vibration (Label 355)1 0 TN1 Vibration (Label 356)1 1 TN2 Vibration (Label 357)


DATA STANDARDS

Label 353 03D - Maintenance Data #4 Highest Vibration (cont’d)

* 757 Data ID

Bits Data

19 18

0 0 BB Vibration (Label 357)0 1 N1 Vibration (Label 354)1 0 N1 Vibration (Label 355)1 1 N3 Vibration (Label 356)**

** Used on 757 Rolls Royce Engines only

Data

Bit 28 27 26 25 24 23 22 21 20MSB <----------------------> LSB

Bit Encoding for Vibration LabelsBits = 9Resolution = 0.01Range = 0 to 5.12Units = Scalar Units

SSM

Bits Data

31 30 29

1 0 0 Self Test1 1 0 Normal Operation


DATA STANDARDS

Label 353 03F


1 0

1 X2 X3 X4 Label 353 03F X5 X6 X7 X8 X9-10 SDI X11 X12 PAD X13 X14 N1 Crosscheck* Failed OK15 N2 Crosscheck* Failed OK16 Spare X17 Spare X18 T2 Crosscheck* Failed OK19 T2 Probe/ADC T 2 Disagreement Disagree OK20 Tfuel Crosscheck* Failed OK21 Toil Crosscheck* Failed OK22 Wf Feedback Crosscheck* Failed OK23 SVA Feedback Crosscheck Failed OK24 2.5 BLD Feedback Crosscheck* Failed OK25 HCC Feedback Crosscheck* Failed OK26 LCC Feedback Crosscheck* Failed OK27 Reverser Position Crosscheck* Failed OK28 AOX Feedback Crosscheck Failed OK29 Thrust Lever Position Crosscheck* Failed OK30-31 SSM X32 Parity (Odd)




DATA STANDARDS



1 0

1 X2 X3 Label 353 114 (Right Wing) X4 X5 X6 X7 X8 X9 SDI10111213 Probe Capacitance (0.1’s)14151617 Probe Capacitance (1’s)18192021 Probe Capacitance (10’s)2223 Probe Capacitance (100’s)242526 Probe Number (1’s)272829 Probe Number (10’s)30 SSM31 SSM32 Parity (Odd)


DATA STANDARDS



1 0

1 X2 X3 X4 Label 354 01A X5 X6 X7 X8 X9-10 SDI11 Pad X12 Pad X13 Pad X14 Pad X15 TPT2 Temp Diode Fail Good16 TPT7 Temp Diode Fail Good17 Fail Good18 T/M W/A’A Range Check Fail Good19 T/M W/A’B Range Check Fail Good20 Spare X21 Spare X22 LLDC Test #2 Fail Good23 LLDC Drift #2 Fail Good24 TCC Stage I W/A Fail Good25 TCC Stage II W/A Fail Good26 TCC Stage III W/A Fail X27 Spare X28 Spare X29 Spare30-31 SSM32 Parity (Odd)

ADDED: November 17, 1986ARINC SPECIFICATION 429 PART 2- Page 127

DATA STANDARDS

Label 354 02F


1 0

1 X2 X3 X4 Label 354 02F X5 X6 X7 X8 X9-10 SDI X11 X12 PAD X13 X14 REV Command Solenoid W/A Failed OK15 TCA Solenoid W/A Failed OK16 Reserved (Spare Solenoid W/A) X17 Reserved (Spare Solenoid W/A) X18 Reserved (Spare Relay W/A) X19 14th Stage Bleed T/M W/A Failed OK20 Spare X21 Reserved (Spare Solenoid W/A) X22 Oil Bypass Solenoid W/A Failed OK23 Reserved (Spare Relay W/A) X24 T/L Interlock Relay W/A Failed OK25 Reserved (Spare Relay W/A) X26 Spare X27 Group 1 Overcurrent Sense Tripped OK28 Group 2 Overcurrent Sense Tripped OK29 Spare X30-31 SSM X32 Parity (Odd)



DATA STANDARDS

Label 354 03D - Maintenance Data #5 N1 Vibration


1 X2 X3 X4 Label 354 03D X5 X6 X7 X8 X9-10 SDI11-12 Accelerometer Source13 X14 X15 X16 PADS X17 X18 X19 X20-28 Data29 X30 SSM (Normal Operation) X31 X32 Parity (Odd)

Bits Data Bits Data

10 9 12 11


Bit 28 27 26 25 24 23 22 21 20MSB <----------------------> LSB


ADDED: November 17, 1986ARINC SPECIFICATION 429 PAR T 2 - Page 129

DATA STANDARDS

Label 354 03F


1 0

1 X2 X3 X4 Label 354 03F X5 X6 X7 X8 X9-10 SDI X11 X12 PAD X13 X14 REV Command Solenoid W/A Failed OK15 TCA Solenoid W/A Failed OK16 Reserved (Spare Solenoid W/A) X17 Reserved (Spare Solenoid W/A) X18 Reserved (Spare Relay W/A) X19 14th Stage Bleed T/M W/A Failed OK20 Spare X21 Reserved (Spare Solenoid W/A) X22 Oil Bypass Solenoid W/A Failed OK23 Reserved (Spare Relay W/A) X24 T/L Interlock Relay W/A Failed OK25 Reserved (Spare Relay W/A) X26 Spare X27 Group 1 Overcurrent Sense Tripped OK28 Group 2 Overcurrent Sense Tripped OK29 Spare X30-31 SSM X32 Parity (Odd)


ADDED: July 22, 1988ARINC SPECIFICATION 429 PART 2- Page 131

DATA STANDARDS

Label 355 027 - Fault Supplement Word for MLS


1 0

12345 Label 355 0276789 SDI1011121314151617181920212223 BITS 11 thru 2924 reserved for Company25 private use.2627282930 SSM3132 Parity (Odd)

NOTE: Transmission interval min. 50 ms, max. 250 ms.


DATA STANDARDS

Label 355 03D - Maintenance Data #6 N2 Vibration



Bits Data Bits Data

10 9 12 11


Bit 28 27 26 25 24 23 22 21 20MSB <----------------------> LSB



DATA STANDARDS

Label 356 03D - N3 Vibration



Bits Data Bits Data

10 9 12 11


Bit 28 27 26 25 24 23 22 21 20MSB <----------------------> LSB



DATA STANDARDS

Label 357 03D - BB Vibration



Bits Data Bits Data

10 9 12 11


Bit 28 27 26 25 24 23 22 21 20MSB <----------------------> LSB



DATA STANDARDS

Label 360 03D - N1 Rotor Imbalance Angle


1 X2 X3 X4 Label 360 03D X5 X6 X7 X8 X9-10 SDI11-12 Accelerometer Source13 X14 X15 X16 PADS X17 X18 X19 X20-28 Data29-31 SSM32 Parity (Odd)

Bits Data Bits Data

10 9 12 11


Bit 28 27 26 25 24 23 22 21 20MSB <----------------------> LSB

Bit Encoding for Imbalance AnglesBits = 9Resolution = 1.0Range = 0 to 360Units = Degrees

Bits Data

31 30 29

1 0 0 Functional Test0 1 0 No Computed Data1 1 0 Normal Operation0 0 0 Failure Warning


DATA STANDARDS

Label 361 03D* - LPT Rotor Imbalance Angle


1 X2 X3 X4 Label 361 03D X5 X6 X7 X8 X9-10 SDI11-12 Accelerometer Source13 X14 X15 X16 PADS X17 X18 X19 X20-28 Data29-31 SSM32 Parity (Odd)

Bits Data Bits Data

10 9 12 11


Bit 28 27 26 25 24 23 22 21 20MSB <----------------------> LSB

Bit Encoding for Imbalance AnglesBits = 9Resolution = 1.0Range = 0 to 360Units = Degrees

Bits Data

31 30 29

1 0 0 Functional Test0 1 0 No Computed Data1 1 0 Normal Operation0 0 0 Failure Warning

* 737 Only

MARK 33 DIGITAL INFORMATION TRANSFERSYSTEM (DITS), PART 3

FILE DATA TRANSFER TECHNIQUES

ARINC SPECIFICATION 429P3-18

PUBLISHED: OCTOBER 12, 2001

AN AAAA DOCUMENTPrepared byAIRLINES ELECTRONIC ENGINEERING COMMITTEEPublished byAERONAUTICAL RADIO, INC.2551 RIVA ROAD, ANNAPOLIS, MARYLAND 21401

This document is based on material submitted by variousparticipants during the drafting process. Neither AEEC nor ARINChas made any determination whether these materials could besubject to valid claims of patent, copyright or other proprietaryrights by third parties, and no representation or warranty, express orimplied, is made in this regard. Any use of or reliance on thisdocument shall constitute an acceptance thereof “as is” and besubject to this disclaimer.

Copyright© 2001 byAERONAUTICAL RADIO, INC.


ARINC SPECIFICATION 429P3-18©


PART 3


Published: October 12, 2001


Specification 429P3 Adopted by the Airlines Electronic Engineering Committee: July 21, 1977Specification 429P3 Adopted by the Industry: September 15, 1977

Summary of Document Supplements

Supplement Adoption Date Published

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

A description of the changes introduced by each supplement is included on Goldenrod paper at the end of this document.

FOREWORD

Activities of AERONAUTICAL RADIO, INC. (ARINC)

and the

Purpose of ARINC Reports and Specifications

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

Activities of ARINC include the operation of an extensive system of domestic and overseasaeronautical land radio stations, the fulfillment of systems requirements to accomplish ground andairborne compatibility, the allocation and assignment of frequencies to meet those needs, thecoordination incident to standard airborne compatibility, the allocation and assignment of frequenciesto meet those needs, the coordination incident to standard airborne communications and electronicssystems and the exchange of technical information. ARINC sponsors the Airlines ElectronicEngineering Committee (AEEC), composed of airline technical personnel. The AEEC formulatesstandards for electronic equipment and systems for the airlines. The establishment of EquipmentCharacteristics is a principal function of this Committee.

It is desirable to reference certain general ARINC Specifications or Report which areapplicable to more than one type of equipment. These general Specifications and Reports may beconsidered as supplementary to the Equipment Characteristics in which they are referenced. They areintended 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 necessaryinterchangeability in airline service. The release of a Specification or Equipment Characteristicsshould not be construed to obligate ARINC or any airline insofar as the purchase of any components orequipment 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 theconsidered opinion of the airline technical people, coordinated on an industry basis,concerning requisites of new equipment, and

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

ii

ARINC SPECIFICATION 429 PART 3TABLE OF CONTENTS

iii

ITEM SUBJECT PAGE

1.0 INTRODUCTION 11.1 Purpose of this Document 11.2 Organization of ARINC Specification 429 11.3 Development of Data Transfer 11.3.1 File Data Transfer Techniques - Basic Philosophy 11.3.2 Data Transfer 11.3.3 Broadcast Data 11.3.4 File Data Transfer 11.3.5 Transmission Order 21.3.5.1 Data Bit Encoding Logic 21.3.6 Bit-Oriented Protocol Determination 21.4 Relationship to Other Standards 2

2.0 BIT ORIENTED FILE TRANSFER PROTOCOL 32.1 - 2.4 Not used to maintain consistency with previous versions of 3

ARINC Specification 4292.5 Bit-Oriented Communications Protocol 32.5.1 Link Data Units (LDU) 42.5.2 Link Data Unit (LDU) Size and Word Count 42.5.3 System Address Labels (SALs) 42.5.4 Bit Rate and Word Timing 42.5.5 Word Type 52.5.6 Protocol Words 52.5.6.1 Protocol Identifier 52.5.6.2 Destination Code 52.5.6.3 Word Count 52.5.7 Request To Send (RTS) 52.5.7.1 Clear To Send (CTS) 52.5.7.2 Not Clear To Send (NCTS) 52.5.7.3 Destination Busy (BUSY) 62.5.7.4 No Response to RTS 62.5.8 Conflicting RTS Transmissions 62.5.8.1 Half Duplex Mode 62.5.8.2 Full Duplex Mode 72.5.9 Unexpected RTS 72.5.10 Start Of Transmission (SOT) 72.5.10.1 General Format Identifier (GFI) 72.5.10.2 File Sequence Number 72.5.10.3 LDU Sequence Number 72.5.11 Data 72.5.11.1 Full Data Word(s) 72.5.11.2 Partial Data Word(s) 82.5.12 End of Transmission (EOT) 82.5.12.1 CRC Encoding 82.5.12.2 CRC Decoding 82.5.13 Negative Acknowledgment (NAK) 92.5.13.1 Missing SOT Word 92.5.13.2 Missing EOT Word 92.5.13.3 Parity Errors 92.5.13.4 Word Count Errors 92.5.13.5 CRC Errors 92.5.13.6 Time Out Errors 92.5.14 LDU Transfer Acknowledgment (ACK) 92.5.14.1 Duplicate LDU 92.5.14.2 Auto-Synchronized Files 92.5.14.3 Incomplete File timer 102.5.15 SYN Word 102.5.16 Response to ACK/NAK/SYN 102.5.17 Solo Word (Single Word Transfers) 102.5.17.1 Test Word and Loop Word 112.5.17.2 Optional Solo Word Definitions 112.5.18 Optional End-To-End Message Verification 112.5.19 Protocol Initialization 112.5.19.1 Bit-Oriented Protocol Version 112.5.19.1.1 ALOHA 11


iv

ITEM SUBJECT PAGE

2.5.19.1.2 ALOHA Response 122.5.19.2 Williamsburg/File Transfer Determination 122.6 Windowed Bit-Oriented Communications Protocol 13

3.0 BIT ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL 143.1 Bit Oriented Media Access Control (MAC) Protocol 143.1.1 Introduction 143.1.2 Relationship Between the Version 1 and Version 3 Protocols 143.1.3 Protocol Architecture 153.1.4 Buffering 153.2 Media Access Control (MAC) Sublayer 153.2.1 MAC Sublayer Service Specification 153.2.2 MA DATA request 163.2.2.1 Function 163.2.2.2 Semantics 163.2.2.2.1 destination MA address 163.2.2.2.2 destination SAL address 163.2.2.2.3 m sdu 163.2.2.2.4 service class 163.2.2.3 When Generated 173.2.2.4 Effect of Receipt 173.2.3 MA DATA.indication 173.2.3.1 Function 173.2.3.2 Semantics 173.2.3.2.1 destination MA address 173.2.3.2.2 destination SAL address 173.2.3.2.3 source MA address 173.2.3.2.4 source SAL address 173.2.3.2.5 m sdu 173.2.3.2.6 reception status 173.2.3.2.7 service class 173.2.3.3 When Generated 183.2.3.4 Effect of Receipt 183.2.4 MAC Control functions 183.2.4.1 MA CONTROL.request 183.2.4.2 MA CONTROL.indication 193.3 MAC Frame Structures 193.3.1 Information Frame Format 193.3.1.1 Address fields 193.3.1.2 Length/Type Field 193.3.1.2.1 Length 193.3.1.2.2 Type 203.3.1.3 Data Field 203.3.1.4 Frame Check Sequence (FCS) Field 203.3.1.5 Validation of Information Frame 203.3.1.5.1 Invalid Address 203.3.1.5.2 Invalid Length/Type 203.3.1.5.3 Invalid FCS 203.3.2 Command Frame Format 203.3.2.1 GFI Field 203.3.2.2 Command Type Field 213.3.2.3 Data Field 213.3.2.4 Frame Check Sequence (FCS) Field 213.3.2.5 Validation of Command Frame 213.3.2.5.1 Invalid FCS 213.4 MAC Transmit/Receive Functions 213.4.1 Frame Data Unit (FDU) 213.4.2 Frame Data Unit (FDU) Size and Word Count 213.4.3 System Address Labels (SALs) 213.4.4 Bit Rate and Word Timing 223.4.5 Word Type 223.4.6 Start of Frame (SOF) 223.4.6.1 Information/Command (I/C) Frame Field 223.4.6.2 Information SOF word 22


v

ITEM SUBJECT PAGE

3.4.6.2.1 Word Count 223.4.6.2.2 Reserved Bits 223.4.6.3 Command SOF word 223.4.6.3.1 Word Count 223.4.6.3.2 Reserved Bits 223.4.6.3.3 General Format Identifier Field (GFI) 223.4.6.3.4 Command Type Field (CT) 223.4.7 Data 233.4.7.1 Full Data Word(s) 233.4.7.2 Partial Data Word(s) 233.4.7.3 SOLO Words 233.4.8 End of Frame (EOF) 233.4.9 Frame Check Sequence 233.4.9.1 32-Bit CRC Encoding 243.4.9.2 32-Bit CRC Decoding 243.4.10 Incomplete FDU Timer 243.4.11 ALOHA 243.4.12 Validation of FDUs 253.4.12.1 Missing SOF Word 253.4.12.2 Missing EOF Word(s) 253.4.12.3 Parity Errors 253.4.12.4 Word Count Errors 253.4.12.5 CRC Errors 253.4.13 Inter-FDU Gap Time 26

ATTACHMENTS

1 - 9 Numbers not used in Part 3 of Specification 429 2710 Variables of Bit-Oriented Protocol 2811 Bit-Oriented Data File Transfer Word Formats 3511A Destination Codes 4111B Status Codes 4311C ALOHA/ALOHA Response Protocol Word Definition 4412 Version 1 File Transfer Example 4512A Field Mapping Example 4613 Protocol Determination Procedure Diagrams 4713A ALOHA Version Determination Sequence 4914 System Address Labels 5015 Deleted by Supplement 16 5116 Deleted by Supplement 16 5217 Flow Diagram Used to Determine Character-Oriented vs Bit-Oriented Protocol 5318 MAC Sublayer Support Diagrams 5419 Command Frame Data Unit (FDU) Structure and Examples 5620 Information Frame Data Unit (FDU) Structure and Example 58

APPENDICES

A-E Letters not used in Part 3 of Specification 429 60F Former AIM and File Data Transfer Techniques 61G Mathematical Example of CRC Encoding/Decoding 67H Interoperability of Bit-Oriented Link Layer Protocol 71I SDL Diagrams of the Version 1 Williamsburg Protocol 72J Protocol Structure 90K Glossary & Acronyms 93

ARINC SPECIFICATION 429 PART 3 - Page 1

1.0 INTRODUCTION

c-15

c-16

c-15

c-15

c-13

c-16

1.1 Purpose of this Document

This document defines the air transport industry’s standardsfor the transfer of aperiodic digital data between avionicssystems elements. Adherence to these standards is desiredfor all inter-systems communications in which the systemline replaceable units are defined as “unit interchangeable”in the relevant ARINC equipment Characteristics. Their usefor intra-system communications in systems in which theline replaceable units are defined in the ARINC equipmentCharacteristics as “system interchangeable” is not essential,although it may be convenient.


The original release of ARINC Specification 429 waspublished in its entirety as one document in 1977. Throughthe years as the Specification grew in content, the physicalsize grew proportionately. As a result, the effort involvedwith locating specific data became increasingly difficult.The solution, concurrent with the publication of Supplement15, was to divide Specification 429 into three parts. Part 1addresses the physical parameters (wiring, voltage levels,coding, etc.) and label assignments. Part 2 provides theformats of words with discrete bit encoding. Part 3 definesfile data transfer protocols.

Parts 1, 2, and 3 are being published separately beginningwith the updates provided by Supplement 15. In the future,updates to the individual Parts of ARINC Specification 429will be accomplished by independent Supplements startingwith Supplement 16. Each Part will be updated viaSupplement as the need dictates. Therefore the “dashnumbers,” i.e. -16, -17, etc. may not necessarily beconcurrent for all three parts of Specification 429.

The descriptive material for the changes introduced by theSupplement 1-14 are provided in Part 1. Part 3 containsSupplements 12 and above. The new bit-oriented protocolwas introduced by Supplement 12. The description ofchanges introduced by Supplements 15 and later for eachPart are contained within the respective Parts of thedocument.

1.3 Development of File Data Transfer

ARINC Specification 429, “Mark 33 Digital InformationTransfer System (DITS)” was adopted by AEEC in July1977. Specification 429 defined a broadcast data bus.General provisions were made for file data transfer. InOctober 1989, AEEC updated a file data transfer procedurewith a more comprehensive process that will support thetransfer of both bit and character-oriented data.

COMMENTARY

The ACARS character protocol is defined in ARINCSpecification 619.

COMMENTARY

The desire for exchanging binary data via ACARS wasinstrumental in initiating the development of a

more sophisticated file transfer protocol. Thefundamental concept was developed at a joint Satelliteand ACARS Protocol Working Group meeting held inFebruary 1988 in Williamsburg, Virginia. The newprotocol became known popularly as the“Williamsburg Protocol.”

1.3.1 File Data Transfer Techniques- Basic Philosophy

This “File Data Transfer Techniques” specificationdescribes a system in which an LRU may generate binaryextended length messages “on demand.” Data is sent in theform of Link Data Units (LDU) organized in 8-bit octets.System Address Labels (SAL) are used to identify therecipient. Two data bus speeds are supported.

1.3.2 Data Transfer

The same principles of the physical layer implementationdescribed in Part 1 to ARINC Specification 429,“Functional Description and Word Formats,” apply to FileData Transfer. Any avionics system element havinginformation to transmit does so from a designated outputport over a single twisted and shielded pair of wires to allother system elements having need of that information.Unlike the simple broadcast protocol that can deliver data tomultiple recipients in a single transmission, the FileTransfer technique can be used only for point-to-pointmessage delivery.

1.3.3 Broadcast Data

The same simple “broadcast” transmission techniquedefined in ARINC Specification 429 Parts 1 and 2 may besupported concurrently with the use of aperiodic File DataTransfer.

1.3.4 File Data Transfer

When Specification 429 was adopted in 1977, provisionswere made for a character-oriented file data transferprotocol. This definition was used as guidance for thecharacter-oriented file transfer protocol descriptionsincorporated into many ARINC equipment characteristics.In 1989, a new protocol was developed that expanded thecapability of file data protocol to support the transfer of bit-oriented information. The original description of file datatransfer was declared obsolete; a copy, as a historicalrecord, is retained in Appendix F. The ACARS characteroriented file transfer protocol which was derived from thematerial in Appendix F is documented in ARINCSpecification 619.

The protocol defined in this document is preferred for newapplications. The purpose of this bit-orientedcommunications protocol is to provide for the transparenttransfer of data files using the physical layer data busdefined by Specification 429, Part 1.

COMMENTARY

The data transparent protocol described in Section 2.5 wasdeveloped in order to facilitate the communications of theACARS Management Unit (MU) and the Satellite DataUnit (SDU). Its viability as a universal protocol was

c-15

c-16

c-15


1.0 INTRODUCTION

c-17

1.3.4 File Data Transfer (cont’d)


recognized by the Systems Architecture andInterfaces(SAI) Subcommittee which recommended itsinclusion herein as the standard means of file datatransfer.

The process for determining the protocol (character-oriented as defined in ARINC Specification 619, or bit-oriented) to be used in the interaction between two units,where this information is not pre-determined is described inSection 2.5.19.


The most significant octet of the file and least significant bit(LSB) of each octet should be transmitted first. The label istransmitted ahead of the data in each case. It may be notedthat the Label field is encoded in reverse order, i.e., the leastsignificant bit of the word is the most significant bit of thelabel. This “reversed label” characteristic is a legacy frompast systems in which the octal coding of the label field was,apparently, of no significance.

1.3.5.1 Data Bit Encoding Logic

A “HI” state after the beginning of the bit interval returningto a “NULL” state before the end of the same bit intervalsignifies a logic “one.”

A “LO” state after the beginning of the bit interval returningto a “NULL” state before the end of the same bit intervalsignifies a logic “zero.” This is represented graphically inARINC Specification 429, Part 1 Attachment 7.

1.3.6 Bit-Oriented Protocol Determination

An LRU will require logic to determine which protocol(character or bit-oriented) and which version to use whenprior knowledge is not available. See Section 2.5.19.1 forbit protocol version determination.

1.4 Relationship to Other Standards

This document defines an onboard data link protocol to beused for file data transfer between cooperating LineReplaceable Units (LRU). As an onboard data bus, thisstandard is often included in AEEC equipment standards(ARINC 700 series) by reference.

Conversely, this Specification also references otherdocuments. For example, Version 3 of the file transferprotocol, defined in Chapter 3 herein, utilizes many of theprinciples of the IEEE communications standard 802.3.Appropriately, there are numerous references to thatstandard. IEEE 802.3, 1998 was current when thedefinition of Version 3 was completed. Since the IEEEstandard may evolve over time, a generic (non-time dated)reference (i.e., IEEE 802.3) is used wherever possible toenable the reference within this document to remaincurrent, to the maximum extent possible, without futureSupplements. Exceptions to this practice includereferences to specific clauses or paragraphs of IEEE802.3, 1998. These references are not intended to limit thegrowth or evolution of these provisions, but rather toensure that the reader is equipped with sufficient

information to ensure that the desired section will belocated.

Documents referenced in this document include:

IEEE Standard 802.3, 1998 Edition, “Carrier SenseMultiple Access with Collision Detection (CSMA/CD)Access Method and Physical Layer Specifications”

c-15

c-16

c-17

c-17


2.0 BIT-ORIENTED FILE TRANSFER PROTOCOL

2.1 This Section number is not used in Part 3 to maintainconsistency with previous versions of ARINC Specification429.





This section describes Version 1 of the bit-oriented(Williamsburg) protocol and message exchange proceduresfor file data transfer between units desiring to exchange bit-oriented data assembled in data files. This protocol shouldbe used in lieu of the character-oriented file data transferdefined in ARINC Specification 619. All other bus activityremains unchanged. The bit-oriented protocol is designed toaccommodate data transfer between sending and receivingunits in a form compatible with the Open SystemsInterconnect (OSI) model developed by the InternationalStandards Organization (ISO). This document directs itselfto an implementation of the Link layer, however, anoverview of the first four layers (Physical, Link, Networkand Transport) is provided.

Communications will permit the intermixing of bit-orientedfile transfer data words (which contain System AddressLabels (SALs)) with conventional data words (whichcontain label codes). If the sink should receive aconventional data word during the process of accepting abit-oriented file transfer message, the sink should accept theconventional data word and resume processing of theincoming file transfer message.

The process for determining the protocol (character-oriented or bit-oriented) to be used in the interactionbetween two units, where this information is not pre-determined is described in Section 2.5.19. The definition ofthe protocol words used to determine the type of protocol iscontained in Table 11-4 of Attachment 11.

A table illustrating the bit-oriented file transfer wordformats is shown in Attachment 11.

The description provided in the following subsectionscontains references to options which may be exercised andtiming values which may be selected for each individualsystem for which this protocol is chosen. The options aredesignated with an “O” and a sequence number, e.g., O5.The timing values are designated with a “T” and a sequencenumber, e.g., T2. See Attachment 10 for tables containingstandard options, events, applications and timers.

COMMENTARY

There is no protocol to support negotiation of theparameters, and options such as those defined inAttachment 10.

The data file and associated protocol control informationare encoded into 32-bit words and transmitted over thephysical interface as described in Part 1 of Specification429. At the Link layer, data is transferred using a datatransparent bit-oriented data file transfer protocol designedto permit the units involved to send and receive informationin multiple word frames. It is structured to allow thetransmission of any binary data organized into a data filecomposed of octets. Examples of file transfer and fieldmapping are given in Attachments 12 and 12A respectively.The bit-oriented protocol will support either full or halfduplex operation (O1).

A. Physical Medium

The physical interface should be as described in Part 1 ofSpecification 429.

B. Physical Layer

The Physical layer provides the functions necessary toactivate, maintain and release the physical link which willcarry the bit stream of the communication. The electricalinterface, voltage, timing, etc. described in Part 1 ofSpecification 429 should be used by the interfacing units.Data words will contain 32 bits; bits 1-8 will contain theSystem Address Label (SAL) and bit 32 will be the parity(odd) bit.

C. Link Layer

The Link layer is responsible for transferring informationfrom one logical network entity to another and forenunciating any errors encountered during transmission.The Link layer provides a highly reliable virtual channeland some flow control mechanisms.

D. Network Layer

It is the responsibility of the Network layer to ensure thatdata packets are properly routed between any two terminals.The Network layer performs a number of functions. TheNetwork layer expects the Link layer to supply data fromcorrectly received frames.

COMMENTARY

The Network layer provides for the decoding ofinformation up to the packet level in order to determinewhich node (unit) the message should be transferred to.To obtain interoperability, this process, though simplein this application, must be reproduced using the sameset of rules throughout all the communicationsnetworks (and their subnetworks) on-board the aircraftand on the ground.

The bit-oriented data link protocol was designed to operatein a bit-oriented Network layer environment. Specifically,the Data Link Subcommittee expects that ISO 8208 will beselected as the Subnetwork layer protocol for air/ground

c-13

c-12

c-12

c-16

c-12

c-13

c-14

c-13



2.5 Bit-Oriented Communications Protocol (cont’d)

subnetworks. There are, however, some applications wherethe bit-oriented file transfer protocol will be used underother Network layer protocols.

E. Transport Layer

The Transport layer controls the transportation of databetween a source end-system to a destination end-system. Itprovides “network independent” data delivery betweenthese processing end-systems. It is the highest order offunction involved in moving data between systems. Itrelieves higher layers from any concern with the puretransportation of information between them.

2.5.1 Link Data Units (LDU)

A Link Data Unit (LDU) contains binary encoded octets.The octets may be set to any possible binary value. TheLDU may represent raw data, character data, bit-orientedmessages, character-oriented messages, or any string of bitsdesired. The only restriction is that the bits be organizedinto full 8-bit octets. The interpretation of those bits is not apart of this Link layer protocol. The LDUs are assembled tomake up a data file.

LDUs consist of a set of contiguous ARINC 429 32-bit datawords, each containing the System Address Label (seeSection 2.5.3) of the sink. The initial data word of eachLDU is a Start of Transmission (SOT) as described inSection 2.5.10. The data described above is containedwithin the data words which follow (See Section 2.5.11).The LDU is concluded with an End of Transmission (EOT)data word (see Section 2.5.12). No data file should exceed255 LDUs.

Within the context of this document, LDUs correspond toframes and files correspond to packets, as defined inSection 2.5.


The Link Data Unit (LDU) may vary in size from 3 to 255ARINC 429 words including the SOT and EOT words.When a LDU is organized for transmission, the totalnumber of ARINC 429 words to be sent (word count) iscalculated. The word count is the sum of the SOT word, thedata words in the LDU and the EOT word.

In order to obtain maximum system efficiency, the datashould be encoded into the minimum number of LDUs.

COMMENTARY

The word count field is 8 bits in length. Thus themaximum number of ARINC 429 words which can becounted in this field is 255. The word count fieldappears in the RTS and CTS data words. The numberof LDUs needed to transfer a specific data file willdepend upon the method used to encode the datawords.

2.5.3 System Address Labels (SALs)

LDUs are sent point-to-point, even though other systemsmay be connected and listening to the output of atransmitting system. In order to identify the intendedrecipient of a transmission, the Label field (bits 1-8) is usedto carry a System Address Label (SAL). Each on-boardsystem is assigned a SAL as shown in ARINC Specification429, Part 1, Attachment 14. When a system sends an LDUto another system, the sending system (the “source”)addresses each ARINC 429 word to the receiving system(the “sink”) by setting the Label field to the SAL of thesink. When a system receives any data containing its SALthat is not sent through the established conventions of thisprotocol, the data received should be ignored.

COMMENTARY

In the data transparent protocol, data files are identifiedby content rather than by ARINC 429 label. Thus, thelabel field loses the function of parameter identificationavailable in broadcast communications.


Data transfer may operate at either high speed or low speed(O2) as defined in Part 1 of Specification 429. The sourceshould introduce a gap between the end of each ARINC 429word transmitted and the beginning of the next. The gapshould be 4 bit times (minimum). The sink should becapable of receiving the LDU with the minimum word gapof 4 bit times between words. The source should not exceeda maximum average of 64 bit times between data words ofan LDU.

COMMENTARY

The maximum average word gap is intended to compelthe source to transmit successive data words of an LDUwithout excessive delay. This provision prevents asource that is transmitting a short message from usingthe full available LDU transfer time (T9). The primaryvalue of this provision is realized when assessing amaximum LDU transfer time for short fixed-lengthLDUs, such as for Automatic Dependence Surveillance(ADS).

If a Williamsburg source device were to synchronouslytransmit long length or full LDUs over a single ARINC429 data bus to several sink devices, the source maynot be able to transmit the data words for a given LDUat a rate fast enough to satisfy this requirement becauseof other bus activity. In aircraft operation, given theasynchronous burst mode nature of Williamsburg LDUtransmissions, it is extremely unlikely that aWilliamsburg source would synchronously beginsending a long length or full LDU to more than twoWilliamsburg sink devices. Although, a laboratorycondition could be designed to test a Williamsburgtransmitter which would likely result in thetransmitter’s failure to meet the maximum word gaprequirement, this test should be disregarded. A failureto meet this requirement will either result in asuccessful (but slower) LDU transfer, or an LDUretransmission due to an LDU transfer timeout.

c-13

c-12

c-16

c-12

c-13

c-13

c-16

c-14

c-16



2.5.5 Word Type

The Word Type Field occupies bit 31-29 in all bit-orientedLDU words. See Table 11-1A of Attachment 11 for adescription of the Word Type field. The Word Type field isused to identify the function of each ARINC 429 data wordused by the bit-oriented communication protocol.


The protocol words are identified with a Word Type field of“100” and are used to control the file transfer process.


The protocol identifier field occupies bits 28-25 of theprotocol word and identifies the type of protocol wordbeing transmitted. Table 11-4 of Attachment 11 contains thedifferent protocol words and their formats.

Protocol words with an invalid protocol identifier fieldshould be ignored.


Some protocol words contain a Destination Code. TheDestination Code field (bits 24-17) typically indicates thefinal destination of the LDU (O10). If the LDU is intendedfor the use of the system receiving the message, thedestination code may be set to null (hex 00). However, ifthe LDU is a message intended to be passed on to anotheron-board system, the Destination Code should indicate thesystem to which the message is to be passed. Someinterfaces (e.g., between an ARINC 758 CMU and a multi-bearer-system ARINC 761 SDU) use the “Destination”code to select a specific bearer system to be used for adownlink message, and to indicate the specific bearersystem used for an uplink message. The Destination Codesare assigned according to the applications involved asshown in Attachment 11A.

In an OSI environment, the Link layer protocol is notresponsible for validating the destination code. It is theresponsibility of the higher level entities to detect invaliddestination codes and to initiate error logging and recovery.

COMMENTARY

Within the pre-OSI environment, the Destination Codeprovides Network layer information. In the OSIenvironment, this field may contain the sameinformation for routing purposes between OSI and non-OSI systems.

2.5.6.3 Word Count

Some protocol words contain a Word Count field. TheWord Count field (bits 16-9) reflects the number of ARINC429 words to be transmitted in the subsequent LDU. Themaximum word count value is 255 ARINC 429 words andthe minimum word count value is 3 ARINC 429 words. ALDU with the minimum word count value of 3 ARINC 429words would contain a SOT word, one data word and anEOT word. A LDU with the maximum word count value of255 ARINC 429 words would contain a SOT word, 253data words and an EOT word.

2.5.7 Request To Send (RTS)

When an on-board system needs to send a LDU to anotheron-board system, it will issue a Request To Send (RTS) tothat system. The RTS word contains a Destination Codeand a Word Count field.

When a system receives a RTS, it should send a response tothe source within T1 milliseconds. The response can be: (1)Clear to Send, (2) Not Clear to Send or (3) Busy.

To be considered valid CTS, NCTS or BUSY data wordsmust have odd parity and contain the same destination codeas the corresponding RTS. A valid CTS must also containthe same word count as the RTS.

2.5.7.1 Clear To Send (CTS)

When a system receives a valid RTS and is ready to acceptthe LDU transfer, it should send a CTS word to the sourcewithin T1 milliseconds. The CTS contains a DestinationCode (bits 24-17) and a Word Count field (bits 16-9). TheDestination Code in the CTS should contain the sameDestination Code as the RTS word (See Section 2.5.6.2).The Word Count field should contain the same Word Countvalue as the RTS word. If the source receives a CTScontaining a different Destination Code or Word Countfield value or a Word count field value equal to zero, itshould treat it as a valid Not Clear To Send. All of the RTScounters (N1, N2, N3) will be reset after a valid CTS isreceived.

2.5.7.2 Not Clear To Send (NCTS)

When a system either receives a valid RTS and is NOTready to accept the LDU transfer or receives an RTS withan invalid destination or invalid word count, it should senda Not Clear To Send (NCTS) to the source within T1milliseconds. See Table 11-4 of Attachment 11 for theformat of the NCTS word. The NCTS word should containthe same Destination Code as the RTS word and status code(bits 16-9) as shown in Attachment 11B indicating thereason for the busy response. If the NCTS received does notcontain the same Destination Code, then the source shoulddeclare the NCTS to be invalid and ignore it. The statuscodes are for engineering purposes only and should beignored by the system receiving the NCTS word.

Upon receipt of the NCTS word, the source should wait forT2 milliseconds before repeating the RTS. The RTS may berepeated T2 milliseconds after each NCTS until N1 requestsnominally have gone without receiving a valid CTS. Theactual number of attempts (N1) a system should make andthe action to be taken when the limit is exceeded depend onthe application (A1). The NCTS counter (N1) should bereset upon valid (CTS) response to the RTS.

After sending a NCTS, the sink may optionally choose (O3)to send a CTS with the requested Destination Code andWord Count automatically as soon as it is ready to

c-14

c-16

c-14

c-14c-18

c-16

c-18c-16



2.5.7.2 Not Clear To Send (NCTS) (cont’d)

accept the file transfer, without waiting for another RTS.The source may optionally choose (O4) to accept such aCTS. Alternatively, the source may ignore the CTS with therequested Destination Code and Word Count and repeat itsRTS.

COMMENTARY

If the word count and/or destination fields in thereceived RTS word are not valid by virtue of illegal orunsupported values, the sink should respond with theNCTS word using an optional status code identifyingthe condition. Some original implementations simplyignored an invalid RTS word. However, the preferenceis to respond with a NCTS.

2.5.7.3 Destination Busy (BUSY)

When a system receives a valid RTS and is not able toaccept an LDU within a timely manner, the receivingsystem may optionally send a BUSY response to the sourcewithin T3 milliseconds. See Table 11-4 of Attachment 11for the format of the BUSY data word. The BUSY wordshould contain the same Destination Code as the RTS wordand a status code (bits 16-9) as shown in Attachment 11Bindicating the reason for the busy response. If the BUSYreceived does not contain the same Destination Code, thenthe source should declare the BUSY to be invalid andignore it. The status codes are for engineering purposes onlyand should be ignored by the system receiving the BUSYword.

COMMENTARY

A timely manner refers to the interval defined by theNCTS retry sequence.

Upon receipt of the BUSY word, the source should wait forT4 seconds before repeating the RTS. The RTS may berepeated every T4 seconds for as many times as theapplication requires up to a maximum of N2 . Each newattempt could possibly consist of several RTStransmissions. Note that the busy condition could last forhours, depending on the nature of the application and thebuffering capacity of the sink. The action taken followingT4 - N2 time out depends upon the application (A2). Theapplication requirements may supersede the value of N2defined in Attachment 10. The Busy counter (N2) should bereset upon valid (CTS) response to the RTS.

After sending a BUSY, the sink may optionally choose (O3)to send a CTS with the requested Destination Code andWord Count automatically as soon as it is ready to acceptthe file transfer, without waiting for another RTS. Thesource may optionally choose (O4) to accept such a CTS.

Alternatively, the source may ignore the CTS with therequested Destination Code and Word Count and repeat theRTS.

When expedited file transfers are desired between 2 BOPdevices, the sink device should support Option 3 (SendAuto CTS) and the source device should support Option 4(Accept Auto CTS).

COMMENTARY

If Option 3 (Send Auto CTS) and Option 4 (AcceptAuto CTS) cannot be supported between two deviceswhere expedited file transfers are necessary, analternative approach is to reduce the BUSY RetryTimer (T4) and increase the BUSY counter (N2)accordingly to make the T4N2 timeout period identicalto the existing T4N2 value. The recommended value forlow speed is T4=1.5 seconds and N2=200.


If the source receives no response to the RTS within T5milliseconds, the request should be repeated. In the absenceof any valid response (such as CTS, NCTS, or BUSY), orthe absence of an unexpected RTS, the RTS should berepeated every T5 milliseconds until at least N3 requestshave gone unanswered. Any response other than a validCTS, NCTS, BUSY, Aloha, or an unexpected RTS shouldbe ignored. The No response counter (N3) should be resetupon valid response to the RTS. All the RTS counters (N1,N2, N3) will be reset after a valid CTS is received.

The actual number of attempts a source should make (N3)before giving up, or taking some different course of action,when the limit is exceeded depends on the application (A3).The action to be taken is described in Table 10-2 ofAttachment 10 or in the applicable equipment characteristic.

2.5.8 Conflicting RTS Transmissions

2.5.8.1 Half Duplex Mode

When operating in half duplex mode, it is possible that twosystems might decide to send RTS messages to each otherat nearly the same time, causing each system to appear toreceive the other’s RTS in response to its own RTS. If thisoccurs, each system should set a random timer to a time inthe range of zero to T6 milliseconds in increments of nomore than T7 milliseconds. If a system receives anotherRTS before this timer expires, that system will defer its ownneed to transmit and will respond to the other system’s RTSas defined in the preceding paragraphs. If no RTS isreceived within the random time, the system should re-transmit the RTS. If a conflicting RTS occurs again, thesame procedure will take effect for as many times as it takesfor one system to prevail over the other.

If this protocol is used in an environment that has welldefined priorities (O5), one system may be assigned priorityover another to resolve RTS conflicts without the randomretransmission procedure described above.

COMMENTARY

Typically, a well-defined priority in avionics gives anRTS for uplinks priority over an RTS for downlinks.

c-14

c-16

c-16

c-14

c-12

c-16



2.5.8.2 Full Duplex Mode

When operating in a full duplex mode, both systems mustbe capable of operating as a source and sink at the sametime. If both systems initiate an RTS, both should receive aCTS and both should respond normally to the CTS. Neithersystem should abort.

A conflicting RTS applies only to a receiving system thathas transmitted a CTS (in response to a RTS) and receivesanother RTS. This RTS is treated simply as a retransmissionand the sink should retransmit a CTS.


It is possible, that after sending a CTS word to a requestingsource, that the source does not receive the CTS and re-transmits the RTS to the sink. Alternatively, a source mayexperience a reset which causes a new RTS to be sent in themiddle of an LDU transfer. If, for any reason, the first wordreceived by a sink after having sent a CTS word is an RTS,then the sink should transmit another CTS word. If a sinkreceives another RTS after having sent a CTS, even in themiddle of receiving an LDU, the sink should discard anypartial LDU already received and respond as defined inSection 2.5.7.1.

2.5.10 Start Of Transmission (SOT)

When a system receives a valid CTS with a DestinationCode and Word Count matching the Destination Code andWord Count of the previous RTS, the system shouldrespond by sending the Start of Transmission (SOT) wordwithin T13 milliseconds, immediately followed by the datawords which constitute the LDU. See Table 11-6 ofAttachment 11 for a description of the SOT word format.The SOT word contains the File Sequence Number in itsFile Sequence Number field (bits 24-17). It also contains aGeneral Format Identifier (GFI) and a LDU SequenceNumber.


The General Format Identifier (GFI) occupies bits 28-25 inthe SOT word. See Table 11-6A of Attachment 11 for adescription of the GFI field. The GFI is transparent to theLink layer protocol. It is designated by a higher level entityin the source device, to indicate to a higher level entity inthe sink, the format of the data words that follow. It is theresponsibility of the higher level entities to detect invalidGFI designations and to initiate error logging and recovery.

COMMENTARY

Within the pre-OSI environment the GFI providesNetwork layer function information. In the OSIenvironment this field may contain the sameinformation for bridging purposes between the OSI andnon-OSI world.

A code of 1111 is used to indicate that an extended GFI of8 bits will be found in the first data octet (Nibbles 1 and 2)of the first data word in the file.

2.5.10.2 File Sequence Number

The File Sequence Number (bits 24-17) of the SOT wordcontains an 8-bit number assigned to the file. It is initializedto the hex value 00 and increments by 1 for each new filethat is sent over the ARINC 429 link. After reaching hexFF, the File Sequence Number should start over at hex 01,skipping zero. A file consisting of multiple LDUs will havethe same File Sequence Number in each of the SOT wordsof each LDU.

2.5.10.3 LDU Sequence Number

The LDU Sequence Number (bits 16-9) of the SOT wordcontains an 8-bit number assigned to the LDU. It isinitialized to the hex value 00 and increments by 1 for eachnew LDU of the same file that is sent over the ARINC 429link. The LDU Sequence Number should be reset to 00 atthe beginning of each new file.

2.5.11 Data

Data words immediately follow the SOT word. The octetsof the data file are encoded and transmitted in 32-bit datawords. There are two basic types of data words: full binaryand partial binary. Binary data words may contain one, two,three, four and five semi-octets. A semi-octet (or nibble) ishalf of an octet, or four bits in length.

Binary data words of five semi-octets are called Full Datawords. Binary data words of fewer than five semi-octets arecalled Partial Binary Data words.

A data file may be sent using any combination of full andpartial data words. There are no restrictions regarding theparticular type of data within a file. The formats of Datawords are illustrated in Attachment 11.

Each binary data file, prior to transmission, should conclude(end) with a complete octet. Any incomplete final octetshould be completed with zeros before transmission. EachLDU transmitted, should also end in a complete octet. If, atthe end of the transmission, the receiver determines that anodd number of semi-octets has been received, that is, theLDU ends with an incomplete octet, the receiver shouldsend a NAK or assume the upper 4 bits of the partial octetto be zeros, and proceed normally.

2.5.11.1 Full Data Word(s)

A Full Data Word has 20 bits available for data. This spaceis allocated in five semi-octets. The octets of the data fileare divided into two semi-octets and placed sequentiallyinto the data words. The least significant bit of the leastsignificant semi-octet is sent first.

If, in the process of placing the octets into the data words,an octet is split between two different words, the leastsignificant semi-octet goes in the last (n5) semi-octet of thecurrent data field and the most significant semi-octetfollows in the first (n1) semi-octet of the data field of thenext word. See Attachment 11 for data word formats.

c-13

c-14

c-14

c-12

c-13

c-12



2.5.11.1 Full Data Word(s) (cont’d)

If the end of the LDU does not completely fill the last FullData Word, a Partial Data Word (see Section 2.5.11.2)should be used to complete the LDU transmission.

In order to obtain maximum system efficiency, Partial DataWords should be used only when they are required tocomplete the data for an LDU transmission. An LDUshould not be encoded as a string of Partial Data Wordswhere 8 or 16 bits of data are encoded for each ARINC 429word used.

2.5.11.2 Partial Data Word(s)

A Partial Data Word contains from one to four semi-octets.The number of semi-octets in a partial data word isindicated in bits 28-25 of the word. Only full four-bit semi-octets can be sent; one, two or three bits are invalid. PartialData Word semi-octets are sent in the same order as thesemi-octets in a full data word. The unused semi-octets inthe partial data word should be set to binary zeros.

2.5.12 End of Transmission (EOT)

Each LDU transfer is terminated by an End of Transmission(EOT) word. See Table 11-7 of Attachment 11 for thedefinition of this word. Table 11-7A of Attachment 11contains the definition for bit 25 of the EOT word. This bitis used to indicate if the LDU is the final LDU of the filetransfer. If the file transfer consists of a single LDU, bit 25should be set to 1 to indicate that this is the final LDU. If NLDUs are to be sent, then bit 25 of LDU 1 through LDU N-1 should be set to 0 and bit 25 of LDU N should be set to 1.The EOT word contains a Cyclic Redundancy Check orCRC (bits 24-9).

COMMENTARY

The ARINC 429 data link is a twisted shielded pair ofwires which has been demonstrated to exhibit highintegrity and unlikely to introduce errors into the datapassing through it. Simple parametric data is usuallytransmitted at a refresh rate high enough to permitrecognition and suppression of erroneous data. Sincethe transfer of data using a file transfer protocolcontains no provision for automatic refresh, someapplications may require high data integrity to beconfirmed by an error checking mechanism. For thisreason, each LDU contains a CRC check. The use ofthe CRC in this case does not imply any inherent lackof integrity of the ARINC 429 link.


The CRC field is a 16 bit sequence with the most significantbit (MSB) transmitted first. Determination and encoding ofthe CRC is as follows:

The k bits of data in the LDU are represented as thecoefficients of the polynomial, G(x); where k is the numberof data bits in the LDU existing between, but not including,the SOT and EOT words. For example, if the data stream is101001, k=6 and G(X)=x5+ x3 + 1.

The CRC calculation is performed over the data octets onlyof the LDU with any semi-octets zero filled.

There exists a generator polynomial which is of the form,

P(x) = x16 + x12 + x5 + 1

The CRC is then determined as the one’s complement of theremainder, R(x), obtained from the modulo 2 division of:

x16G(x) + xk(x15+x14+x13+...+x2+x+1) = Q(x) + R(x) P(x) P(x)

Note: The addition of xk(x15+x14+x13...+x2+x+1) to x16G(x)(which is equivalent to inverting the first 16 bits of G(x) andappending a bit string of 16 zeroes to the lower order end ofG(x)), corresponds to initializing the initial remainder to avalue of all “ones.” The complementing of R(x), by thetransmitter, at the completion of the division ensures thatthe received, error-free message will result in a unique, non-zero remainder at the receiver.

At the transmitter, the CRC is added to the x16G(x) product,resulting in the message, M(x), of length n where:

n = k+16,

and M(x) = x16G(x) + R(x)

= x16G(x) + CRC

2.5.12.2 CRC Decoding

Decoding of the CRC at the receiver is as follows:

At the receiver, the incoming M(x) is multiplied by x16,added to the product,

xn(x15+x14+x13+...+x2+x+1)

and divided by P(x) as follows:

x16M(x)+xn(x15+x14+x13+...+x+1) = Qr(x) + Rr(x) P(x) P(x)

If the transmission of the serial incoming bits plus CRC(i.e., M(x)) is error free, then the remainder, Rr(x) will be0001110100001111 (coefficients of x15 through x0,respectively). A mathematical example of CRC encodingand decoding can be found in Appendix G.

COMMENTARY

The notation used to describe the CRC is based on theproperty of cyclic codes that a code vector such as1000000100001 can be represented by a polynomialG(x) = x12 + x5 + 1. The elements of an n element codeword are thus the coefficients of a polynomial of ordern - 1. In this application, these coefficients can havethe value 0 or 1 and all polynomial operations areperformed module 2. The polynomial representing thedata content (message) of an LDU is generated usingthe LDU bit which is encoded in bit 9

c-13

c-16

c-14

c-12

c-12

c-12



of the first data word as the coefficient of the highestorder term. A mathematical example of CRC encodingand decoding can be found in Appendix G.

2.5.13 Negative Acknowledgment(NAK)

If the sink detects any of the errors described in thefollowing subsections, it sends a NAK to the source upondetecting the error or within T8 milliseconds of receiving theEOT word, whichever occurs first. See Table 11-4 ofAttachment 11 for a description of the NAK word format.The NAK word should contain the same File SequenceNumber (bits 24-17) as the SOT word and a status code(bits 16-9) as shown in Attachment 11B indicating thereason for the NAK. The File Sequence Number and statuscode are intended to be used for engineering purposes onlyand should be ignored by the system receiving the NAK.

The sink should test for errors to determine if a NAKshould be sent. It is not necessary for the sink to be aware ofthe type of error that occurred, as long as any of the errorslisted in the following subsections will elicit a NAKresponse.

2.5.13.1 Missing SOT Word

Following reception of a valid CTS word, the source shouldtransmit the SOT word as the first word of the LDU asspecified in Section 2.5.10, Start of Transmission (SOT). Ifthe SOT word is not received as the first word of the LDU,the sink should send the NAK response. See also Section2.5.9.

2.5.13.2 Missing EOT Word

Following the transmission of the final data word of eachLDU, the source should transmit the EOT word as the finalword of the LDU as specified in Section 2.5.12, End ofTransmission (EOT). If the EOT word is not received as thefinal word of the LDU within T9 seconds of the CTS, thenthe sink should send the NAK response to the source withinT8 milliseconds after the T9 has expired.


Bit 32 of each ARINC 429 word should be set to odd parityfor the entire word. Upon receipt of a word, the receivingunit should verify that each word was received with oddparity. If any word is received with even parity, thereceiving unit should take no action and ignore the word.

COMMENTARY

When the sink receives a word with bad parity, itcannot be sure of the intended label. The word may noteven be a part of the LDU, so by ignoring the offendingword there may still be a chance of a successful filetransfer. If the offending word was intended to be apart of the LDU, then when the EOT word is received,the actual word count will not match the expectedcount. The sink will either NAK the source when theEOT word is received, or when it times out waiting forthe full expected number of words.


Upon receipt of the EOT word, the sink should verify thatthe actual number of words received is the number of wordsexpected, per the RTS and CTS words. If the word countsdo not match, the sink should send a NAK response to thesource.

2.5.13.5 CRC Errors

Upon receipt of the EOT word, the sink should verify theCRC on the received LDU. If the 16-bit CRC is invalid, thesink should send the NAK response.


The sink will not time the gaps between the words received,However, if the sink does not receive the complete LDUtransfer within T9 seconds of having sent the CTS, it shouldsend a NAK to the source and discard any partial LDUreceived.

2.5.14 LDU Transfer Acknowledgment(ACK)

If all words of the LDU transfer are received within T9seconds of the CTS, each with odd parity, and the wordcount and CRC verify, and the LDU is either the next LDU,a duplicate LDU or the first LDU of a new file, then thesink should send an acknowledgment(ACK) to the sourcewithin T8 milliseconds of receiving the EOT word. SeeTable 11-4 of Attachment 11 for a description of the ACKword format. The ACK word should contain the FileSequence Number (bits 24-17) and LDU sequence number(bits 16-9) to indicate a successful LDU transfer.


An LDU is determined to be a duplicate if its File SequenceNumber and LDU Sequence Number are not both zero, andit’s SOT words are identical to those of the previouslyreceived LDU. When a duplicate LDU is detected, the sinkshould discard the LDU just received and acknowledge perSection 2.5.14.

COMMENTARY

Some implementations look at both SOT and EOT todetermine duplicate LDUs.

COMMENTARY

A File Sequence Number of zero along with an LDUSequence Number of zero should be interpreted as anindication of a reset in the source and the LDU shouldnot be compared to the previous one.


When the File Sequence Number is different from theprevious LDU transfer and the LDU Sequence Number iszero, then the sink discards any previously received partialfile, and accepts the LDU just received.

c-14

c-12

c-13

c-12

c-13

c-12

c-12

c-14

c-13

c-12

c-16

c-12



2.5.14.2 Auto-Synchronized Files (cont’d)

COMMENTARY

Some implementations do not support auto-synchronized files.


The Incomplete File (T14) timer is used to insure that asource device may not “lock-up” a sink with an incompletefile.

For multiple-LDU files, the maximum time allowed fromtransmission of the ACK or NAK for a previous LDU to thereception of the next RTS should be T14 minutes. The sinkwill start the T14 timer when it sends a NAK or when itsends an ACK for each LDU of a file except the last LDU.The T14 timer is stopped each time another valid RTS isreceived. The T14 timer should also be stopped if the sinkdiscards the partial file for other reasons defined in thisspecification. When T14 minutes is exceeded, the sinkshould send the SYN word within T8 milliseconds anddiscard any partial file already received.

For Half Duplex environments (i.e., Option O1 of Table 10-3) this timer only applies when the device is operating as asink.

2.5.15 SYN Word

The SYN word is used by the sink to inform the source thatit (the sink) has become confused concerning theconstruction of the file. A typical example is aninappropriate or unexpected File/LDU Sequence Number inthe SOT word. See Table 11-4 of Attachment 11 for adescription of the SYN word format. Upon receipt of theSOT word, the sink should verify the LDU SequenceNumber (bits 16-9).

COMMENTARY

If an SOT word of an LDU has the same File SequenceNumber and LDU Sequence Numbers as the previousLDU, some implementations will interpret this as anunexpected File/LDU Sequence Number instead of aduplicate LDU.

If the LDU is not a duplicate and its LDU SequenceNumber is not the next in sequence (i.e., is not the nextLDU), and is not the first LDU of a new file, then the sinkshould send the SYN response to the source within T8milliseconds of receipt of the SOT word, or within T8milliseconds of receipt of the EOT word when necessary todetermine a duplicate LDU, and discard any partial filealready received.

COMMENTARY

Some implementations look at both SOT and EOTto determine duplicate LDUs.

The SYN word may be sent without timing constraint whenthe received data words cannot be normally processed.There is no acknowledgmentdefined for the source when a

SYN word is received. The action taken is specified inSection 2.5.16.


The source should expect a response to the transmissionwithin T16 of sending the EOT .

COMMENTARY

Timer T10 may apply instead of T16, for those devicescompliant with version “0000” or “0001” of thisprotocol (Table 11-4A of Attachment 11). T10 is startedafter the CTS is received whereas time T16 is startedafter the EOT word is transmitted.

If an ACK is received and the File Sequence Number andLDU Sequence Number match the contents of the SOTword, the source should consider the transfer successful. Ifan ACK is received and the File Sequence Number and/orthe LDU Sequence Number do not match the SOT word, orif a NAK is received or if no response is detected, thesource should repeat the entire LDU transmission process,starting with the sending of the RTS word. If the sourcedetects a SYN during the transmission process, it shouldretransmit the entire file, if able, beginning with the firstLDU. The File Sequence Number contained within theSYN word is provided for testing purposes and is notevaluated by the source. If the source is not able toretransmit or rebuild the entire file, that file is discarded andthe source proceeds normally with the first LDU of the nextfile, when it is ready for transmission.

COMMENTARY

If end-to-end accountability is required, then eitherupper layer OSI protocols or the application processshould provide this capability.

Each new attempt to re-transmit the LDU should start withthe necessary RTS transmissions in order to obtain a CTSagain. After receiving N4 consecutive NAK words, or afterreceiving N5 consecutive SYN words, the file transferbetween the two systems should be considered failed.

2.5.17 Solo Word (Single Word Transfers)

If the data to be sent consists of 1 or 2 octets only, (e.g., abutton code from a CDU keyboard) then it is not necessaryto obtain a CTS. In this case the data may be sent “in theblind” using the Solo Word format (O8). The Solo Wordcontains a 16-bit data field in bits 24-9 and a 4-bit identifierin bits 28-25 to identify the nature of the data. For example,the I.D. may indicate that the data is a key code from aCDU or a status word. Codes 0000 and 0001 are reservedfor the TEST and LOOP words as defined in Section2.5.17.1. All other codes are available for application use.Solo Words are not acknowledged at the link level.However, they may invoke a Solo Word or data file transferresponse as required by the application. Solo Words cannotbe interleaved with data file words during a data filetransfer. If error detection beyond parity is required, somebits of the data field can be defined as check bits, to beverified by the application.

c-14

c-13

c-16

c-13

c-14

c-13

c-14

c-12

c-13

c-12



2.5.17.1 Test Word and Loop Word

The integrity of the ARINC 429 link between two units maybe tested. The test is initiated by the source sending theLoop Test Pattern Word (TEST).

The TEST word contains a 16-bit binary pattern (bits 24-9)chosen by the originator. The system receiving the TESTWord should respond by sending a Loop Test Response(LOOP) word containing the same 16-bit pattern (bits 24-9)within T11 milliseconds.

COMMENTARY

The preferred reaction to a loop test failure has notbeen defined.

2.5.17.2 Optional Solo Word Definitions

Each equipment utilizing this bit-oriented protocol maydefine solo words as needed. See Table 11-5 of Attachment11 for the format definition. These solo word definitionsshould be unambiguous.

COMMENTARY

The same SOLO word ID coding may beusedrepeatedly in different units as long as its meaningremains unambiguous.

2.5.18 Optional End-To-End Message Verification

In some applications, an end-to-end integrity check isdesirable in order to validate the correct transfer of a datafile from the message source to its final destination. Forfurther information, the reader should refer to the applicableARINC Equipment Characteristic, e.g., ARINCCharacteristic 702, “Flight Management ComputerSystem.”


The ALO word should be sent by any system whichsupports the bit-oriented Link layer protocol just after thesystem powers-up, or performs a re-initialization for anyreason.

A system which supports the bit-oriented Link layerprotocol should first determine if the interfacing device alsosupports the bit-oriented protocol using the ALO/ALRprocess described in Section 2.5.19.1. If the system isbilingual and there is no response to the ALO/ALR process,it may also determine if the interfacing device supports thecharacter-oriented protocol as described in Section 2.5.19.2.

A bilingual system should repeat the processes described inSections 2.5.19.1 and if applicable 2.5.19.2, until a commonprotocol version is selected by both systems. Examples ofprotocol initialization are given in Attachment 13.

COMMENTARY

In addition to a “power-reset” or a system “re-initialization,” a device that supports the bit-oriented

protocol may at any time determine the ARINC 429link status using the ALO/ALR process described inSection 2.5.19.1 and Section 2.5.19.2.

2.5.19.1 Bit-Oriented Protocol Version

The ALO/ALR process is intended to be used when asystem needs to determine whether or not an interfacesupports the bit-oriented protocol. To maintaininteroperability, all systems which support the Link layerBit-Oriented Protocol must be able to respond to theinitialization of this process. Attachment 11, Table 11-4,shows the ALO and ALR word formats.

When a system with a bit-oriented Link layer protocol hasthe need to make this determination, it should construct theALO word and transmit this word to the device in question.

The system should then wait for a maximum period of timedefined by T12. If the device in question has not respondedwithin time T12, the initiating system should initiate anotherALO word and again delay up to T12. The initiating systemshould attempt a maximum of N6 ALO word operationsbefore declaring the device in question as “Not bit-oriented”or “Not able to respond.”

2.5.19.1.1 ALOHA

The first ALOHA word transmitted in a sequence shouldcontain the highest Version Number supported by thesource device. If the ALOHA Response contains a versionthat does not match the ALO version, the source deviceshould take one of the following actions:

a. If the source device is able to adapt to the differences inprotocol version, file transfers may proceed using theprotocol version identified in the ALR word.

b. If the source device is not able to adapt to thedifferences in protocol version, the source should againinitiate the ALOHA word with the version field set tothe highest version supported by the source that is lowerthan the version indicated in the previous ALR (seeexamples identified in Attachment 13A).

The ALO/ALR protocol determination process shouldcontinue until a common protocol version is found. If noneof the protocol versions match, the source should notify thehigher level entity of the communications failure andcontinue the protocol determination process.

When the system only supports bit oriented protocols itshould repeat the process described in this section. Whenthe system also supports character oriented protocols thenthe process defined in 2.5.19.2 should be followed. Theprotocol determination process will continue until acommon protocol is found. See Attachment 17.

The ALOHA word should contain a Subsystem SAL fieldas shown in Attachment 11, Table 11-4. This field shouldcontain the SAL of the device sending the ALOHA word,with bit 17 as the most significant bit and bit 24 as the leastsignificant bit of the Subsystem SAL.

c-12

c-14

c-16

c-14

c-14

c-16

c-14

c-16



2.5.19.1.2 ALOHA Response

A device that supports the bit-oriented Link layer protocolshould always be able to respond to the receipt of the ALOword. Whenever a device receives the ALO word, it shouldleave its present task and respond within T15 with an ALRword.

The ALR response should reflect the device’s protocolversion level by way of the Version Number containedwithin the ALR word. If the Version Number of the ALOdoes not match the sink device’s protocol Version Number,the sink device should select the next lowest versionsupported (equal to or lower than the version indicated bythe previous ALO word) and indicate this new version inthe ALR word.

After the device has responded to the ALO word (with theALR), the device should take the following action:

If the device was in the sink mode (had already begunreceiving any LDU of a file), it should discard any partialfile it had received. Since the ALO represents a system “re-initialization” (per Section 2.3), the source may reset theFile and LDU sequence numbers.

If the device was in the source mode (had already beguntransmitting any LDU or file), it should resend the entire filebeginning with the first LDU of the file.

If Option O12 is selected for a particular bit-orientedprotocol interface, the device receiving an ALOHA wordshould use the Subsystem SAL from the ALOHA word asthe SAL of the ALOHA Response (ALR) word and for allsubsequent bit-oriented protocol transmissions for thatinterface.

COMMENTARY

A bit-oriented Link layer protocol device receiving anALOHA word should take caution if utilizing theSubsystem SAL field of the ALOHA word todetermine how to send the ALR reply. Previoussupplements of the bit-oriented Link layer protocoldefined the Subsystem SAL field as [TBD] bits, and assuch, some devices in service may have encoded non-zero bits in this field. A receiving system shouldtherefore implement a reasonableness check to validatethat the data bits received in this field represent a SALassociated with a known bit-oriented Link layerprotocol device. If a device receives an ALOHA wordcontaining a System SAL of all zeros or an unknownSAL, and the ALOHA word is received on a data busthat has a specific bit-oriented Link layer protocolsubsystem associated with it, it is recommended thatthe ALR word be attempted using the SAL for thatspecific subsystem, to ensure interoperability.

2.5.19.2 Williamsburg/File Transfer Determination

In some situations there may be a transition period from adevice using the character-oriented file transfer protocoldefined in ARINC Specification 619 to the same deviceusing the Williamsburg bit-oriented protocol introduced inSupplement 12. In this situation, it is desirable to have an

“automatic” determination sequence which allows thedevices to adjust from the character-oriented to bit-orientedprotocol. Because of the environment in which thesedevices are to operate, it is necessary to have a cyclicprocess to establish the protocol to communicate with. Anattempt to establish contact using the bit-oriented ALO-ALR words should be made to the point where the link isconsidered to be failed or to be established.

If the link has been established, then normal bit-orientedcommunications can be pursued. If the link is consideredfailed, then an attempt to obtain a response to the character-oriented RTS-CTS words should be made. The typicalrepeat sequence for the character-oriented protocol is 3 tries(See Attachment 13). If a character-oriented CTS, NCTS(CTS 0), or BUSY (CTS Q) response is obtained, then thelink is considered established and normal character-orientedcommunications can be pursued. If the character-orientedprotocol fails, then the cycle should be re-started using thebit-oriented ALO sequence. There may be a period ofinactivity between cyclic attempts of not more than 15seconds. Attachment 17 contains an example diagram ofthese determination sequences.

If a protocol has been established and the link fails becauseof a loss of activity (if defined on that bus), or because of afailure to deliver a message due to a no response, then theprotocol determination sequence should be started again. Agraphical representation of this is presented in Attachment17.

COMMENTARY

This determination sequence is only necessary whenthere is a possibility of having to support both the oldercharacter-oriented protocol and the newer bit-orientedprotocol on the same ARINC 429 data bus.

COMMENTARY

During the protocol determination process, a bilingualdevice should recognize protocol words using both thebit-oriented (Williamsburg) and the character-orientedformats. It is recommended that at least the ALOHAword and the character-oriented RTS and NAK wordsbe recognized by the device capable of the automaticprotocol determination. This would minimizesynchronization problems between the twocommunicating devices and allow the Link layer methodto be established in a timely manner.

COMMENTARY

When an LRU performs the character protocoldetermination (RTS) it is initiating the sequence ofevents for a file transfer, but it does not complete the filetransfer. Some LRUs will wait forever for the filetransfer to be completed unless the source sends a NAKword to terminate the file transfer. Therefore, it isrecommended that protocol determination logic whichincludes character protocol should transmit a characteroriented NAK word when a character oriented CTSword is received in response to a character oriented RTSword.

c-14

c-16

c-16

c-14

c-14

c-16



2.6 Windowed Bit-Oriented Communications Protocol

This section has been deleted.

Version 2 of the bit-oriented (Williamsburg) Protocol,previously in this section, has been superseded by Version 3of the bit-oriented (Williamsburg) Protocol defined inSection 3.0 of this document.

c-16


3.0 BIT-ORIENTED MEDIA ACCESS CONTROL (MAC) PROTOCOL

3.1 Bit-Oriented Media Access Control (MAC) Protocol

3.1.1 Introduction

This section describes Version 3 of the bit-oriented(Williamsburg) protocol. It is an IEEE 802 compliant MACprotocol for frame oriented data transfer using the Data Linklayer.

Within the ISO/OSI Reference Model, the Data Link layer isresponsible for the logical connection between at least twoentities of the same Local Area Network (LAN). It interfacesto the Network layer, which is responsible for the connectionbetween at least two networks, and the Physical layer, which isresponsible for the physical connection between adjacentnodes, i.e. repeaters, bridges or computers. The Data Linklayer is further divided into two sublayers.

The Media Access Control (MAC) sublayer, which is aPhysical, layer dependent entity. The purpose of the MAC isto provide a standard interface to the entities above it. TheMAC isolates the sublayer above it from the details of thePhysical layer. The ARINC 429 MAC is defined herein.

The Logical Link Control (LLC) sublayer is assumed byIEEE/ISO as the second sublayer, which is a physicallyindependent control sublayer.

For further description of the OSI protocol layers please referto Section 2.5 of this document.

COMMENTARY

Generally, multiple MAC Service Clients (users)interface with the MAC entity (MAC Service Provider).In the IEEE/ISO set of standards the LLC is the mostprominent one. Additionally, the bridging function mayact as a MAC Service Client as well as a MAC Controlfunction. In the non-OSI world there are a variety ofdifferent protocols that may or may not directly interfacewith the MAC. Here, the most prominent one is InternetProtocol (IP). LLC Service Providers are required forsome classes of IEEE 802.3 Local and Metropolitan AreaNetworks, specifically where the MAC frame containsinsufficient information for protocol selection, or whenrequired by higher layer protocols (specifically OSI basedprotocols such as ATN). This document follows theguidance of IEEE 802.3 where the Length/Type field isused to select between LLC as a MAC Client, and wherethe Network Layer is selected as the MAC Client. Theselection of MAC Client (LLC or non-LLC frame format)is mutually exclusive.

In order to make ARINC 429 compatible with standarddata buses adopted by the Institute of Electrical andElectronics Engineers (IEEE) and the InternationalOrganization for Standardization (ISO) it is paramount tosupport their common functionality and interfaces whichare constituted by the MAC.

In order to facilitate bridging between this version of theprotocol and other IEEE data buses the followingsubsections are closely modeled after IEEE 802.3(Ethernet).

Throughout Section 3 of this document the followingterms are being used:

MAC Sublayer: This term refers to the abstractdefinition of a layered communication stack in whichthe MAC Sublayer is part of the Data Link layer.

MAC Entity: Implementation of the functionalitydescribed for the MAC Sublayer

MAC Service Provider: This term can be usedinterchangeably with MAC entity and is supposed toprovide context to the Client/Server nature of the layersof the communication stack.

MAC Service Client: Any entity (implementation) thatuses the services of the MAC entity (implementation)

MAC Frame: Logical representation of the informationstructures exchanged between peer MAC entities. Adetailed description of the structures are given inSection 3.3

Frame Data Unit (FDU): An ARINC 429 envelope thatcontains a MAC frame as well as specific controlinformation. A detailed description of the structures isgiven in Section 3.4.

3.1.2 Relationship Between Version 1 And Version 3Protocols

The bit-oriented MAC protocol (Version 3) is derivedfrom the full-handshake (Version 1) bit-orientedprotocol (BOP) defined in Section 2.5 of thisspecification. Version 3 is presented to MAC ServiceClients that do not require or desire the more exhaustiveData Link layer transfer validation provided by theVersion 1 protocol.

The Version 3 protocol assumes a sufficiently robustARINC 429 physical layer. All valid frames received bythe sink are passed up to the MAC Service Client. Thedemands for buffering are much greater for Version 3than for Version 1. In Version 1 the transmitter isresponsible for buffering, in Version 3 the receiver isresponsible.

The Version 1 ARINC 429 LDU full and partial datawords have been retained. New SOF and EOF wordshave been defined for Version 3 (see Sections 3.4.6 and3.4.8) which replace the Version 1 SOT and EOT words.The bit-oriented MAC protocol does not use the RTS,CTS, NCTS, BUSY, SYN, ACK and NAK words. Onlysingle Frame Data Unit (FDU) transmissions aresupported. Duplicate FDU detection is not performed bythe MAC. Any segmentation and reassembly, ifnecessary, should take place above the ARINC 429 MACsublayer. The terms Frame Data Unit (FDU) and MACframe are defined in Sections 3.3.1, 3.3.2, and 3.4.1.

The Version 3 bit-oriented MAC protocol specifies fullduplex operation (O1) to allow simultaneous datatransfers in both directions. The Version 1 bit-oriented(Williamsburg) protocol typically operates in half-duplexmode only.

c-17 c-17



3.1.3 Protocol Architecture

The MAC protocol described herein can support MACservice clients that are part of the Data Link layer such asLLC and can support MAC service clients in higher layerentities such as the Network Layer. A protocol architecturediagram is used to illustrate this relationship (See Figure 18-1 of Attachment 18).

3.1.4 Buffering

The MAC sublayer should provide sufficient buffering toaccount for expected processing/queuing delays. Someprovisions for flow control are provided through the MACsublayer (see Section 3.2.4). Flow control is primarily theresponsibility of the MAC service client or a higher levelentity.

COMMENTARY

Each layer should have sufficient buffering for expectedprocessing/queuing delays. In order to accurately estimatethe amount of buffering needed, each layer will need tospecify the maximum allowed delays. However, if thebuffering capacity is exceeded, new FDUs are discarded.

There is a non-zero time delay between the time when aFDU arrives at the ARINC 429 MAC sublayer and thetime when the MAC Service Client processes that sameframe. Any flow control, introduced between twosystems, is provided by entities above the MAC serviceentity sending messages to each other. For this reason, theentity responsible for flow control should attempt toanticipate the need to activate flow control in order toaccommodate the delays.

The entity responsible for flow control should attempt tohave adequate buffering capacity to handle all FDUtransfers received from the time it exerts flow control tothe time when the source flow control entity stopstransmitting. This will only be possible if the maximumallowed delay in each of the various components isspecified. These delays include any processing orqueuing delays introduced by communications with theMAC Service Client.

Failure to coordinate the requirements (i.e. delays) willmake it difficult to consistently provide adequatebuffering capacity and may lead to data loss and possiblecommunication failures.

If buffering of incoming frames is done at the MAC sublayer,then the reception status parameter of the MAC primitive,MA_DATA.indication (see Section 3.2.3) should be used toinform the MAC Service Client of a buffering problem for thereceived frame.

COMMENTARY

ISO standards documents do not explicitly specify atwhich (sub) layer buffering is accomplished.

3.2 Media Access Control (MAC) Sublayer

This section describes the various aspects of the MACsublayer functionality. The MAC Sublayer ServiceSpecification (Section 3.2.1) details the procedures inan abstract way (via service primitives) that provide thecommunication service to the MAC Service Client. Thesubsequent section, MAC Frame Structures (Section3.3), defines the MAC frames that will be presented toand expected from the peer MAC entity. The nextsection, MAC Transmit/Receive Functions (Section3.4), is related more to the interface with the particularARINC 429 transmission and reception process itselfand specifies how the FDUs are structured as asequence of ARINC 429 words.

There are two types of applications that have driven thedevelopment of this version of the protocol. One is theneed for a bridgeable protocol that can transfer databetween an ARINC 429 bus and a non-ARINC 429based data bus. This type of application would need fastfile transfer traffic that is focused upon aircraft-widetopology and would utilize an independent exchange ofMAC frame-based information.

The other need is to transfer local, ARINC 429 only,fast file transfer traffic that is focused upon exchangesbetween two closely cooperating systems. In order toallow for the optimized transmission of the two types ofinformation, two specialized MAC frame structureshave been defined, the Information frame and theCommand frame. The Information frame is intended tobe bridgeable to IEEE 802.3 (Ethernet). The Commandframe is not bridgeable. Option 13 (O13) in Table 10-3Bof Attachment 10 allows for the apriori selection offrame type, based on the applicable equipment interfacespecification.

From a transmitter’s point of view, i.e., the originatingMAC Service Client, one parameter within theMA_DATA.request primitive selects which type ofMAC frame to create (see Section 3.2.2.2.4).

From the receivers point of view, i.e., the receivingMAC Service Client, the type of frame (Information orCommand) received is indicated through a parameter inthe MA_DATA.indication primitive, based on thecontents of the SOF word (see Sections 3.2.3.2.7 and3.4.6).

The Version 3 Information frame format facilitatesbridging between this version of the ARINC 429protocol and IEEE data buses. The followingsubsections are closely modeled after IEEE 802.3(Ethernet).

The Version 3 Command frame format facilitates theexchange of command/response pairs, which are peer-to-peer only and hence do not require the additionaladdressing capability provided by the Informationframe.

3.2.1 MAC Sublayer Service Specification

This section describes the services that the MediaAccess Control Sublayer provides to the next higherlayer, i.e., to the MAC Service Client. The services

c-17 c-17



3.2.1 MAC Sublayer Service Specification (cont’d)

are described in an abstract way and do not imply anyparticular implementation or any exposed interface. There isnot necessarily a one-to-one correspondence between theprimitives described herein and the implementation.

Four primitives are used to describe this interface. They are:

MA_DATA.requestMA_DATA.indicationMA_CONTROL.request (optional)MA_CONTROL.indication (optional)

The MAC sublayer is depicted in Attachment 18 Figure18-2.

These primitives describe the required local informationneeded to identify the purpose of the incoming or outgoingdata transfers. Their services are described in the followingsubsections. These services are local to each device and donot imply any particular implementation at the serviceinterface.

This section provides all the information needed in order toinitiate transfer or process reception of user data or controlinformation.

3.2.2 MA_DATA.request

The MA_DATA.request primitive is used to describe howto transmit data that is carried by a MAC frame. The serviceis looked at from the transmitting MAC Service Client pointof view.

The requesting MAC Service Client needs to providesufficient information to the MAC sublayer to enable theMAC sublayer to format a FDU for transmission to a peerMAC Service Client. This information should include thedestination, the data and the transmission service(Information or Command).

3.2.2.1 Function

The MA_DATA.request primitive defines the transfer ofdata from a local MAC Service Client entity to a single peerMAC Service Client entity (or entities in the case of groupaddresses).

The ARINC 429 MAC protocol provides two classes ofservice, the Command frame (local non-bridgeable frame)and the Information frame (bridgeable frame).

3.2.2.2 Semantics

The following parameters are provided with this primitive:

MA_DATA.request(destination_MA_address,destination_SAL_addressm_sdu,service_class)

3.2.2.2.1 destination_MA_address

The destination_MA_address parameter should provideeither an individual or a group MAC address when an

Information frame is to be sent. If an invalid address isbeing handed over, the primitive should not initiate aFDU transmission. Instead, the MA_DATA.requestshould be dropped and the layer management should beinformed.

The destination_MA_address is not used with aCommand frame, but is required for an Informationframe.

The format and contents of thedestination_MA_address for an Information frame isdefined in ARINC Specification 664.

COMMENTARY

At the time this text was written, ARINCSpecification 664 was in draft state i.e., Project Paper664.

3.2.2.2.2 destination_ SAL _address

The destination_SAL_address is required for bothCommand and Information frames. Thedestination_SAL_ address field contains the SAL to beused for transmitting the FDU.

The destination_SAL_address field for an Informationframe can contain either a unique SAL, a multicast SALor a bridge SAL.

The destination_SAL_address field for a Commandframe should contain a unique SAL.

The format and content of the SAL is defined inARINC Specification 429, Part 1.

3.2.2.2.3 m_sdu

The m_sdu parameter indicates the MAC service dataunit (data content) to be transmitted by the MACsublayer entity.

If the m_sdu is empty, i.e. the length is zero, theMA_DATA.request primitive should not cause theinitiation of a FDU transmission. Instead, theMA_DATA.request should be dropped and the layermanagement should be informed. The MAC ServiceClient should not create a MA_DATA.request with anempty m_sdu field.

3.2.2.2.4 service_ class

The service class parameter indicates a quality ofservice requested by the MAC Service Client. Theparameter indicates whether an Information orCommand frame should be constructed. For aCommand frame, the GFI field and Command Typefield values are also indicated via this parameter (seeSections 3.3.2.1 and 3.3.2.2)

COMMENTARY

Currently, two services have been defined, whichare “Transmission of Information Frame” and“Transmission of Command Frame”. Thedetermination of how to initiate one or the other is

c-17 c-17



done locally and is a matter of implementation.However, care should be taken in selecting themechanism to forward that information. More servicesmight be defined at a later stage, which in turn mightcreate a conflict with the implementation.

There is an implication on the destination address fieldthat originates from the determination of which type offrame to use. The Command frame uses only the uniqueSystem Address Label (SAL) that has been defined forVersion 1 of this protocol. The Information frame,however, needs two addresses in parallel: the IEEEcompliant 48-bit destination and source addresses as wellas a SAL.

3.2.2.3 When Generated

The MAC Service Client generates the MA_DATA.requestprimitive. It is a request by a MAC Service Client to thelocal MAC sublayer to transfer a MAC Service Data Unit(m_sdu) to a peer MAC Service Client entity (or entities).The primitive is generated either as the result of a requestfrom a higher layer entity, or internally from the MACService Client itself.

3.2.2.4 Effect of Receipt

Upon receipt of the MA_DATA.request primitive, the MACsublayer first creates the MAC frame by appending anyMAC-specific fields (See Section 3.3.1 and 3.3.2).

Secondly, the MAC service entity packs the resulting MACframe into an ARINC 429 “container” consisting of a seriesof contiguous ARINC 429 32-bit words (See Section 3.4.1)to create a FDU. It transmits the properly formatted FDU tothe peer MAC sublayer entity (or entities) by means of thePhysical layer services for subsequent transfer to theassociated MAC Service Clients.

3.2.3 MA_DATA.indication

The MA_DATA.indication primitive is used to describe, atthe destination MAC Service Client, the mechanics to beused in order to receive data that is carried by a FDU. Theservice is looked at from the receiving MAC Service Clientpoint of view. This primitive is generated by the MAC entityupon reception of a valid FDU, and recreation of the MACframe.

3.2.3.1 Function

The MA_DATA.indication primitive defines the transfer ofdata from a remote MAC Service Client entity to a localpeer MAC Service Client entity.

3.2.3.2 Semantics

The following parameters are provided with theMA_DATA.indication primitive:

MA_DATA.indication

(destination_MA_address,

destination_SAL_address,

source_MA_address

source_SAL_address

m_sdu,

reception_status,

service_class)

3.2.3.2.1 destination_MA_address

The destination_MA_address is obtained from theInformation frame and will contain either an individualor a group MAC entity address. Thedestination_MA_address parameter is empty when theMA_DATA.Indication is generated in response toreceiving a Command frame

3.2.3.2.2 destination_SAL_address

The destination_SAL_address data is obtained from thereceived FDU for either an Information or Commandframe.

3.2.3.2.3 source_MA_ address

The source_MA_address parameter contains the datafrom the source_MA_address field of an incoming FDUthat contains an Information frame. For MACaddressing information refer to ARINC Specification664.

COMMENTARY

At the time this text was written, ARINCSpecification 664 was in draft state i.e., ProjectPaper 664.

The source_MA_address parameter is empty when theMA_DATA.indication is generated in response toreceiving a Command frame.

3.2.3.2.4 source_SAL_ address

The source_SAL_address is generated by the MACbased on the physical port on which the Information orCommand frame was received.

3.2.3.2.5 m_sdu

The m_sdu parameter indicates the MAC service dataunit as received by the local MAC sublayer entity.

3.2.3.2.6 reception_status

The reception_status parameter is used to pass statusinformation to the MAC Service Client. The content ofthis parameter is implementation specific.

3.2.3.2.7 service_class

The service_class parameter is used to indicate whetheran incoming frame is an Information or Commandframe. If it is a Command frame, the GFI and commandtype (CT) information is also passed to the MACService Client.

c-17c-17



3.2.3.3 When Generated

The MA_DATA.indication primitive is passed from theMAC sublayer to the MAC Service Client to indicate thearrival of a FDU at the local MAC sublayer entity. TheMAC Sublayer first validates the FDU (see Section 3.4.12)and then removes the ARINC 429 “container” (i.e., theARINC 429 32 bit word protocol headers/footers) andcombines the resulting data and parameters into aMA_DATA.indication primitive. The primitive is reportedonly if the frame is valid (see Sections 3.3.1.5 and 3.3.2.5).

3.2.3.4 Effect of Receipt

The effect of receipt by the MAC Service Client is notdefined in this document. Refer to the appropriate ARINCspecification for MAC Service Client definitions.

Since buffering capacity is limited, in the event the MACService Client can not consume a frame, any subsequentframes may be discarded.

3.2.4 MAC Control functions

The MAC control function is derived from IEEE 802.3Clause 31. Support of MAC control provides for real-timecontrol and manipulation of MAC sublayer operations, andis provided as an Option (O14) for the Version 3 protocol.Sections 3.2.4.1 and 3.2.4.2 describe this method ofproviding flow control for the Version 3 bit-orientedprotocol using either the Information frame format forEthernet bridgeable interfaces, or the Command frameformat for non-bridgeable interfaces. Frames destined forthe MAC control sublayer (MAC Control frames) aredistinguished from frames destined for MAC Service Clientsby a unique identifier.

For Information frames, the MAC Control Sublayer receivesm_sdu frames and examines the ‘Type’ field for this uniqueidentifier to determine if it is equal to control value (Pauseopcode) of 8808 hex. If it is equal to 8808 hex, the MACControl sublayer processes the Information frame.Otherwise the Information frame is passed to the MACService Client without modification.

For Command frames, the MAC Control Sublayer examinesthe Command Type parameter. If it is set to ‘MAC Control’(and the first two octets of the m_sdu contain the Pauseopcode, 8808 hex), the MAC Control sublayer processes theCommand frame. Otherwise the Command frame is passedto the MAC Service Client without modification.

In the Version 1 protocol, flow control was provided throughthe use of BUSY and NCTS word responses to an RTS word.These ARINC 429 specific protocol words are not used inVersion 3.

For Version 3, the Ethernet compatible PAUSE function isdefined at the MAC Control sublayer. This control sublayeris part of the MAC, physically located just above the MACsublayer, but below the MAC Service Client. Figure 18-2 ofAttachment 18 depicts the usage of interlayer interfaces bythe MAC Control sublayer. LRUs that support the option(O14) to implement the MAC control sublayer shouldsupport the optional MAC service primitives,MA_CONTROL.request and MA_CONTROL. indication,as illustrated. The PAUSE operation is used to inhibit

transmission of data frames from a directly connectedfull-duplex peer system only, and is therefore notbridgeable.

3.2.4.1 MA_CONTROL.request

The MA_CONTROL.request primitive is generated bythe local MAC Control client to send to its peer, via theMAC sublayer, to request inhibiting of MAC frametransmissions from another system for a specifiedperiod of time. The MA_CONTROL.request primitivespecifies:

a1. the destination_MA_address (for an Informationframe) or

a2. Command Type set to MAC Control (for aCommand frame)

b. the PAUSE opcode (8808 hex)

c. a Request_operand indicating the length of timefor which it wishes to inhibit data frametransmission and

d. the Destination SAL.

The size of a MAC Control frame is 32-bits: a 16-bit(PAUSE opcode), and a 16-bit request operand.

An example of the format of the MAC Control frameusing both the Information and Command frame DataUnit (FDU) formats is illustrated in Attachments 19 and20.

The Pause quanta (units of pause time) inhibitstransmission of data frames for a specific period oftime. The pause time quanta for Williamsburg Version3 over high speed ARINC 429 is 5 milliseconds.

The PAUSE flow control function is defined as optional(O14) for Version 3, since it is not anticipated that allVersion 3 interface implementations, such as that of theCMU/VDR, will require flow control at the MACsublayer. (i.e., VDR Mode A uses the MSK modulationscheme so air/ground throughput is somewhat limited andthe need for flow control is not anticipated. For VDLMode 2, the ARINC 429 MAC Service Client isAVLC/8208, which provides flow control from the CMUto the DSP ground station.)

COMMENTARY

IEEE 802.3, 1998 Annex 31B.2 states: “The pause-time is measured in units of pause quanta, equal to512 bit times for the particular implementation. Therange of possible pause time is 0 to 65535 pausequanta.” The bit time for 10 megabit Ethernet is 0.1us, therefore a pause quanta is 51.2 us for this media.

The bit time for 100 kilobit high speed ARINC 429 is 10us, therefore the pause quanta for high speed ARINC 429is 5.12 ms, or approximately 5 ms. The pause time rangefor ARINC 429 is then from 5 ms to 327 seconds. It isrecommended that the pause range be appropriate for theapplication being supported to prevent adverse effects.

c-17 c-17



COMMENTARY

In typical operation the PAUSE function can be used inan X-OFF, X-ON operation by setting the pause_time toa large value, then when convenient, sending anotherPAUSE command with the pause_time = 0 to restarttransmission. Sending another MAC Control framebefore the Pause value in the previous MAC Controlframe times out should cause the sink to replace thecurrent Pause value with the new Pause value, if non-zero, and restart the timer. A Pause value of 0 terminatesthe Pause and restores normal operation.

3.2.4.2 MA_CONTROL.indication

The MA_CONTROL.indication primitive indicates thestatus of the local PAUSE operation (i.e., paused, or notpaused) to the MAC Service Client.

When the MAC Control sublayer receives a MAC Controlframe indicating a Pause condition, it should:

a. Notify the local MAC sublayer to stop sendingframes to the peer MAC sublayer. The MAC sublayershould complete a frame transmission in progress.

b. Notify the local MAC Service Client of the Pausecondition.

c. Start timer of duration indicated in the MAC Controlframe.

d. Refuse frames from the local MAC Service Clientuntil the timer expires.

When the pause timer expires the MAC Service Clientshould be notified. Likewise, when another control framewith the pause_time set equal to 0 is received then the MACService Client should be notified and normal operationresumed.

COMMENTARY

The design of ARINC 429 ICs frequently containtransmit FIFOs in order to reduce the burden on themicroprocessor and therefore do not facilitate thetermination of data transmission in mid frame. Animplementation that does terminate transmission midframe will cause Timer T17 in the receiver to time out.

3.3 MAC Frame Structures

This section defines in detail the MAC frame structures forARINC 429 using MAC procedures. It defines the relativepositions of the various components of the MAC frame. Itdescribes the general method for representing stationaddresses as well as ARINC 429 specific System AddressLabels (see Section 3.4.3). Refer to ARINC Specification664 for the MAC address specification for Informationframes.

COMMENTARY

At the time this text was written, ARINC Specification664 was in draft state i.e., Project Paper 664.

3.3.1 Information Frame Format

The MAC Information frame comprises 5 fields: thedestination address field, the source address field, thelength/type field, the data field and the frame checksequence field. Of these 5 fields all except the data fieldare of fixed length. Due to the transmission schemeused no preamble or delimiter fields are required aswith other technologies. The frame check sequencefield has been put into the EOF (see Section 3.4.8)words. Attachment 20 shows the format of theInformation frame (and the FDU structure).

3.3.1.1 Address fields

Each MAC Information frame contains two addressfields: the destination and the source address field, theyare constructed the same way. The destination fieldspecifies the MAC entity (or entities) for which theFDU is intended. The source address field identifies theMAC entity from which the FDU is initiated. Eachaddress field contains 48 bits (i.e., six octets). For theconstruction of the MAC address fields see ARINCSpecification 664.

COMMENTARY

At the time this text was written, ARINCSpecification 664 was in draft state i.e., Project Paper664.

3.3.1.2 Length/Type Field

The Length/Type Field is defined in IEEE 802.3 Clause3.2.6. This 2-octet field takes one of two meanings,depending on its numeric value.

a. If the value of this field is less than or equal to1500 decimal, then the Length/Type fieldindicates the number of MAC client data octetscontained in the subsequent data field of theframe (Length interpretation). In this case theMAC Client is defined to be the LLC serviceentity, and the LLC header should immediatelyfollow the IEEE 802.3 header.

b. If the value of this field is equal to or greaterthan 1536 decimal, than the Length/Type fieldindicates the nature of the MAC Client protocol(Client interpretation).

c. Any other value of this field is consideredundefined (i.e., values between 1500 and 1536)

3.3.1.2.1 Length

If the Length/Type field is a Length value, the use ofIEEE 802.3 LLC is assumed. The values and uses of theLLC field are beyond the scope of this specification.

Length indicates the total number of octets in the datafield of the frame. It does not include the address fields,the length/type field, or the FCS field.

Valid values for length are between 1 and 1500.

c-17 c-17



3.3.1.2.1 Length (cont’d)


The maximum size permitted by IEEE 802.3 is 1500bytes for the payload of an Ethernet frame (i.e., them_sdu size of an Ethernet frame).

3.3.1.2.2 Type

Protocols other than LLC may be used and this is supportedby using the Length/Type field as an indicator of protocoltype. When the Length/Type field is used in this mannerthen it should contain the protocol type consistent with theprotocol encapsulated by the Ethernet frame. Valid valuesfor the type field are defined in ARINC Specification 664.

COMMENTARY

At the time this text was written, ARINC Specification664 was in draft state i.e., Project Paper 664.

3.3.1.3 Data Field

The data field can contain up to 2536 (2550-14) octets.However, the number of data field octets should be limitedto 1500 in order to allow bridging to Ethernet-basednetworks.

Full data transparency is provided in the sense that anyarbitrary sequence of octet values may appear in the datafield.

3.3.1.4 Frame Check Sequence (FCS) Field

A cyclic redundancy check (CRC) sequence is used by thetransmit and receive algorithms to generate and check a 32-bit (4-octet) CRC value. This value is computed as afunction of the contents of the source address field,destination address field, Length/Type field and data field.The encoding is performed by the generating polynomial asdefined in Section 3.4.9. The FCS is calculated by thetransmitting MAC Service Entity and appended to the MACframe. The FCS is recalculated and verified by the receivingMAC Service Entity following reconstruction of the entireframe and prior to providing the MA_DATA.indication tothe MAC Service Client.

If Option O15 is not selected, the 32 bit CRC will not begenerated or evaluated across the interface. If not used forcontaining the CRC, the FCS field should be set to binaryzero to indicate to the receiving MAC service entity that theFCS was not calculated by the transmitting MAC serviceentity.

COMMENTARY

Not implementing (generating and validating) a FrameCheck Sequence in the Information frame may havenegative consequences on system integrity. Theintegrator is cautioned to be aware of applications thatutilize the interface in which Option 15 has not beenselected.

3.3.1.5 Validation of Information Frame

The receiving MAC sublayer should determine the validityof the incoming Information frame before passing the MACframe to its local Service Client. The following subsections

list the conditions for which the Information frame issaid to be invalid. The contents of invalid MAC framesshould not be passed to the local MAC Service Client,however reception of an invalid frame, and the reasonfor declaring it invalid, should be indicated to the MACService Client.

3.3.1.5.1 Invalid Address

Address checking should be performed according toARINC Specification 664.

3.3.1.5.2 Invalid Length/Type

If the value in the Length/Type field is not a valid valueas defined in section 3.3.1.2.1 and is not a known Typevalue then the MAC frame is considered invalid.

If the Length/Type field contains a length value and thenumber of octets does not match the length then theMAC frame is considered invalid.

3.3.1.5.3 Invalid FCS

The receiving MAC sublayer should verify the 32-bitFCS of the received MAC frame. If the 32-bit FCS isinvalid, the MAC frame is also invalid

The value of binary zero in the FCS field is a uniqueand valid FCS if CRC generation (O15) is not selected.This indicates that the source MAC Service Entity doesnot calculate the CRC for this field. The receivingsystem should check that CRC non-generation (O15) hasbeen selected for this port.

3.3.2 Command Frame Format

For a MAC Command frame the following four fieldsare needed:

a. the GFI field ,

b. the Command Type field,

c. the Data field and

d. the Frame Check Sequence field.

Of these four fields all except the data field are fixedlength. In order to retain as much compatibility withARINC 429 Williamsburg processing as possible, theframe check field has been put into the EOF word (SeeSection 3.4.8). Attachment 19 shows the format of theCommand frame (and FDU) structure.

The Command frame does not contain separate addressfields like the Information frame. It relies on theARINC 429 SAL for addressing. For the definition ofthe SAL see Section 3.4.3.

3.3.2.1 GFI Field

In order to retain as much compatibility with ARINC429 Williamsburg Version 1 as possible, the GFI fieldhas been retained in the SOF word. See Section 2.5 forthe definition of GFI. If the GFI field is not used, thisfield is set to binary zeroes.

c-17 c-17



3.3.2.2 Command Type Field

The Command Type field was created to provide amechanism for the receiver to differentiate between aCommand frame that contains a command message, acontrol message, or a data message (such as a VDL Mode 2frame transmitted across a CMU/VDR interface).

3.3.2.3 Data Field

The Data field contains up to 2552 octets. Full datatransparency is provided in the sense that any arbitrarysequence of octet values may appear in the data field.

3.3.2.4 Frame Check Sequence (FCS) Field

A Cyclic Redundancy Check (CRC) sequence is used by thetransmit and receive algorithms to generate and check a 16-bit (2-octet) CRC value. This value is computed as afunction of the contents of the data field. The encoding isperformed by the generating polynomial as defined inSection 3.4.9.

3.3.2.5 Validation of Command Frame

The receiving MAC sublayer should determine the validityof the incoming Command frame before passing the MACframe to its local Service Client. The following subsectionlists the condition for which the Command frame is said tobe invalid. The contents of invalid MAC frames should notbe passed to the MAC Service Client.

3.3.2.5.1 Invalid FCS

The receiving MAC sublayer should verify the 16-bit FCSof the received MAC frame. If the 16-bit FCS is invalid, theMAC frame is also invalid.

3.4 MAC Transmit/Receive Functions

This section defines the functions to transmit and receive thecontents of FDUs on the physical medium. It is also known asthe interface to the Physical layer.

3.4.1 Frame Data Unit (FDU)

A Frame Data Unit (FDU) envelops a MAC frame andconsists of a set of contiguous ARINC 429 32-bit words, eachcontaining the System Address Label (see Section 3.4.3) ofthe sink. A FDU can be either an Information frame or aCommand frame. The initial data word of each FDU is a Startof Frame (SOF) data word (see Section 3.4.6). The MACframe (See Section 3.3) is contained within the data words thatfollow. The FDU is concluded with one or two consecutiveEnd of Frame (EOF) words (see Section 3.4.8). A FDUalways consists of no more than one frame.

A Frame Data Unit (FDU) contains binary encoded octets.The octets may be set to any possible binary value. The FDUcontains any string of bits desired. The only restriction is thatthe bits be organized into full 8 bit octets. The interpretationof those bits is not a part of this specification.

3.4.2 Frame Data Unit (FDU) Size and Word Count

The FDU word count is the sum of the SOF word, the datawords containing the MAC frame, and the EOF word(s). TheFrame Data Unit (FDU) may vary in size from a minimum of

three, to a maximum of 1023 ARINC 429 words(including the SOF and EOF words). When a FDU isorganized for transmission, the total number of ARINC429 words to be sent (word count) is calculated.

3.4.3 System Address Labels (SALs)

Each on-board system attached to an ARINC 429 bus thatrequires aperiodic message capability is assigned aSystem Address Label (SAL). The listing of SALassignments can be found in Attachment 11 to ARINCSpecification 429, Part 1. FDUs are sent point-to-point,even though other systems may be connected andlistening to the output of a transmitting system. In orderto identify the intended recipient of a transmission, theLabel field (bits 1-8) is used to carry a System AddressLabel (SAL).

When a system sends a FDU to another system, thesending system (source) addresses each ARINC 429word to the receiving system (sink) by setting the Labelfield to the SAL assigned to the sink.

Apart from existing system specific unique SALs, twouniversally applicable SALs have been defined: theMulticast SAL (MSAL) and the Bridge SAL (BSAL).These SAL´s are designated for Information framesonly and should not be used for Command frames.

For situations where a system will need to communicatewith another system, which has no SAL assigned, i.e., isnot attached to an ARINC 429 bus, a Bridge SAL will beused.

COMMENTARY

The Bridge SAL assumes that no compatibilityconflict will arise with other systems. The bridge willaccept all FDUs and afterwards selects how tohandle them based upon a predefined or, in somecases, learned bridging table.

For situations, where multiple systems will need to beaddressed at the same time, a Multicast SAL will be usedThis SAL can only be used for the transmission ofInformation frames. In this case, a system needs toexamine the MAC destination address contained in theFDU.

COMMENTARY

Similar to the Bridge SAL, the Multicast SALassures that no compatibility conflict will arise withother systems. Generally, it addresses all attachedsystems, local or remote (beyond the bridge). It is theresponsibility of each individual system to determinewhether or not to accept the FDU being received.

When a system receives any data containing its SAL thatis not sent through the established conventions of thisprotocol, the data received should be ignored.

c-17

c-18

c-17

c-17




Data transfer should operate at the low or high-speed rate asdefined in Part 1 of ARINC Specification 429 depending onthe value of Option 2 (see Table 10-3b). The source shouldintroduce a gap between the end of each ARINC 429 wordtransmitted and the beginning of the next. The gap should beat least 4 bit times (minimum). The sink should be capable ofreceiving the FDU with the minimum word gap of 4 bit timesbetween words. The source should not exceed a maximumaverage of 40 bit times between data words of a FDU.

3.4.5 Word Type

The Word Type field occupies bit 31-29 in all bit-orientedFDU words. See Table 11-1A of Attachment 11 for adescription of the Word Type field. The Word Type field isused to identify the function of each ARINC 429 data wordused by the bit-oriented communication protocol. There aretwo new word types for the Version 3 protocol, word types010 and 011.

3.4.6 Start of Frame (SOF)

When a system wants to transmit either an InformationFrame Data Unit or a Command Frame Data Unit, thesystem should start by sending the Start of Frame (SOF)data word, immediately followed by the data words, whichcontain the contents of the MAC frame. The format of theSOF word differs between Information and CommandFDUs. See Attachment 11, Tables 11-8 and 11-10 for adescription of these two words.

In order to distinguish between Information and Commandframes, the SOF word contains an Information/CommandFrame field.

3.4.6.1 Information/Command (I/C) Frame Field

The Version 3 protocol provides for two different MACframe types in order to adapt to the requirements of differentapplications: an (Ethernet) bridgeable Information frameand a non-bridgeable Command frame. For a description ofthe Frame Data Units (FDUs) which contain these two typesof MAC frames, see Attachments 19 and 20.

To identify the different frame types, bits 20-19 of the SOFword (for both Information and Command FDU) carry thefollowing discriminator:

Bit 20 Bit 19 Definition0 0 Information frame0 1 Command frame1 0 Reserved1 1 Reserved

3.4.6.2 Information SOF word

The SOF word for the Information Frame Data Unitcontains a 10-bit word count, a 2-bit Information/Command(I/C) frame field (as described in Section 3.4.6.1) and an 8-bit Reserved field.

3.4.6.2.1 Word Count

The Word Count field (bits 18-9) of the Information SOFword reflects the number of ARINC 429 words to betransmitted in the Frame Data Unit. For the Information

frame, the maximum word count value is 1023 ARINC429 words. The minimum word count value is 10ARINC 429 words. An Information FDU with theminimum word count would contain one SOF word,seven data words, and two EOF words. An InformationFDU with the maximum word count value wouldcontain one SOF word, 1020 data words and two EOFwords.

3.4.6.2.2 Reserved Bits

Bits 28-21 of the SOF word for the Information FDUare reserved (not used). These bits should be set tobinary zeroes.

3.4.6.3 Command SOF word

The SOF word for the Command frame Data Unitcontains a 10-bit word count, a 2-bitInformation/Command (I/C) frame field (described inSection 3.4.6.1), a 2-bit Reserved field, a 2-bitCommand Type Field and a 4-bit General FormatIdentifier (GFI) field.

3.4.6.3.1 Word Count

The Word Count field (bits 18-9) of the Command SOFword reflects the number of ARINC 429 words to betransmitted in the Frame Data Unit. For the Commandframe, the maximum word count value is 1023 ARINC429 words. The minimum word count value is 3 ARINC429 words. A Command FDU with the minimum wordcount would contain one SOF word, one data word andone EOF word. A Command FDU with the maximumword count value would contain one SOF word, 1021data words and one EOF word.

3.4.6.3.2 Reserved Bits

Bits 22-21 of the SOF word for the Command FDU arereserved (not used). These bits should be set to binaryzeroes.

3.4.6.3.3 General Format Identifier Field (GFI)

For the Command Frame Data Unit (FDU), a GeneralFormat Identifier (GFI) occupies bits 28-25 of the SOFword. It’s function is similar to the General FormatIdentifier described in Section 2.5.10.1 of the Version 1bit-oriented protocol. This field is maintained in theCommand FDU for backward compatibility to thepoint-to-point (non-bridgeable) link layer protocol usedin Version 1. The GFI field is used in Version 3 as anindicator to the MAC Service Client of the format ofdata words to follow.

3.4.6.3.4 Command Type Field (CT)

For the Command Frame Data Unit (FDU), a CommandType (CT) field occupies bits 24-23 of the SOF word.The purpose of the CT field is to facilitate thedifferentiation of FDUs by functional context.

The following values have been assigned:

c-17

c-18

c-17

c-17



Bit 24 Bit 23 Meaning0 0 Command0 1 Data1 0 MAC Control1 1 reserved

COMMENTARY

The contextual differentiation contained in the CT fieldmay be used to implement a flow control mechanism bywhich FDUs of one context type are blocked whileFDUs of other types are not. Such a mechanism mightbe used in a buffer-limited implementation to controlthe flow of FDUs containing application data whileallowing command or control FDUs to pass freely. Theprotocols and procedures to implement this mechanismare not part of this specification.

3.4.7 Data

The definition of the data words which contain the MACframe’s contents are identical for both Version 3(Information or Command) frame types, and are identicalwith the data words used in Version 1 of the bit-orientedprotocol. However, the first six data words of anInformation MAC frame data unit contains additional MACaddressing and length/type information.

Data words immediately follow the SOF word. The octets ofthe FDU are encoded and transmitted in 32-bit data words.There are two basic types of data words: full binary andpartial binary. Binary data words may contain one, two, three,four and five semi-octets. A semi-octet (or nibble) is half of anoctet, or four bits in length.

Binary data words of five semi-octets are called Full Datawords. Binary data words of fewer than five semi-octets arecalled Partial Binary Data words.

Each FDU, prior to transmission, should conclude (end) witha complete octet.

3.4.7.1 Full Data Word(s)

A Full Data Word has 20 bits available for data. This space isallocated in five semi-octets. The octets of the data file aredivided into two semi-octets and placed sequentially into thedata words. The least significant bit of the least significantsemi-octet is sent first.

If, in the process of placing the octets into the data words, anoctet is split between two different words, the least significantsemi-octet goes in the last (n5) semi-octet of the current datafield. The most significant semi-octet follows in the first (n1)semi-octet of the data field of the next word. See Tables 11-2and 11-3 of Attachment 11 for data word formats.

If the end of the FDU does not completely fill the last FullData Word, a Partial Data Word (see Section 3.4.7.2) shouldbe used to complete the FDU transmission.

In order to obtain maximum system efficiency, Partial DataWords should be used only when they are required tocomplete the data for a FDU transmission. A FDU should notbe encoded as a string of Partial Data Words where 8 or 16bits of data are encoded for each ARINC 429 word used.

3.4.7.2 Partial Data Word(s)

A Partial Data Word contains from one to four semi-octets. The number of semi-octets in a partial data word isindicated in bits 28-25 of the word. Only full four-bitsemi-octets can be sent; one, two or three bits are invalid.Partial Data Word semi-octets are sent in the same orderas the semi-octets in a full data word. The unused semi-octets in the partial data word should be set to binaryzeros.

3.4.7.3 SOLO Words

SOLO words, as defined in the Williamsburg Version 1protocol in Section 2.5.17, may be used in the Version 3protocol. However, they should be used only across non-bridgeable interfaces (i.e. in conjunction with Commandframes).

3.4.8 End of Frame (EOF)

Each FDU transfer is terminated by one or two End ofFrame (EOF) word(s), depending upon the nature of theFDU. The format and number of EOF word(s) differbetween Information and Command frames.

For an Information frame the EOF words contain a framecheck sequence which consists of a 32-bit CyclicRedundancy Check (CRC).

For a Command frame the EOF word is identical to aVersion 1 EOT word and contains a frame checksequence which consists of a 16-bit Cyclic RedundancyCheck (CRC).

The final FDU bit is always set for consistency withVersion 1.

See Attachment 11, Tables 11-9 and 11-11 for thedefinition of these words.

COMMENTARY

The ARINC 429 Physical layer is a twisted shieldedpair of wires which has been demonstrated to exhibithigh integrity and unlikely to introduce errors intothe data passing through it. Simple parametric data isusually transmitted at a refresh rate high enough topermit recognition and suppression of erroneousdata. Since the transfer of data using a file transferprotocol contains no provision for automatic refresh,some applications may require high data integrity tobe confirmed by an error checking mechanism. Forthis reason, each FDU contains a CRC check. Theuse of the CRC in this case does not imply anyinherent lack of integrity of the ARINC 429 link.

3.4.9 Frame Check Sequence

For a Command frame, the Frame Check Sequence fieldof the EOF word contains a 16-bit CRC as defined inSections 2.5.12.1 and 2.5.12.2 of the Version 1 bit-oriented protocol. For an Information frame, the FrameCheck Sequence field of the EOF words contains a 32-bit CRC, as defined in this section. Both CRCpolynomials are referenced in ISO 3309, and theprocedure for calculation of the 32-bit CRC is identical

c-17 c-17



3.4.9 Frame Check Sequence (cont’d)

to that of the 16-bit CRC. The only implementationdifferences are found in the length and format of the twogenerator polynomials and length of the CRCs.

The most significant bit (MSB) of the 32-bit CRC sequencefor Information frames is transmitted first.

3.4.9.1 32-Bit CRC Encoding

Determination and encoding of the CRC is as follows:

The k bits of information data in the frame are representedas the coefficients of a polynomial, G(x); where k is thenumber of data bits in the frame existing between, but notincluding, the SOF and EOF words. For example, if the datastream is 1010001,

k = 7 and G(X) = x6 + x4 + 1

The CRC calculation is performed over the data octets onlyof the frame with any semi-octets zero filled.

The generator polynomial for the 32-bit CRC is of the form,

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 theremainder, R(x), obtained from the modulo 2 division of:

x32G(x) + xk (x31 + x30 + x29 + x28 +….+ x3 + x2 + x + 1)P(x)

R(x)= Q(x) +P(x)

Note: The addition of xk (x31 + x30 + x29 + x28 + ... + x3 + x2 +x + 1) to x32G(x) (which is equivalent to inverting the first32 bits of G(x) and appending a bit string of 32 zeroes to thelower order end of G(x)), corresponds to initializing theinitial remainder to a value of all “ones”. Thecomplementing of R(x), by the transmitter, at the completionof the division ensures that the received, error-free messagewill result in a unique, non-zero remainder at the receiver.

At the transmitter, the CRC is added to the x32G(x) product,resulting in the message, M(x), of length n where:

n = k + 32, and

M(x) = x32 G(x) + R(x)

= x32 G(x) + CRC

3.4.9.2 32-Bit CRC Decoding

Decoding of the CRC at the receiver is as follows:

At the receiver, the incoming M(x) is multiplied by x32,added to the product, xn (x31 + x30 + x29 + x28 + ... + x3 + x2 +x + 1) and divided by P(x) as follows:

x32M(x) + xn (x31 + x30 + x29 + x28 + .... + x3 + x2 + x + 1)P(x)

Rr(x)= Qr(x) +P(x)

If the transmission of the serial incoming bits plus CRC(i.e. M(x)) is error free, then the remainder, Rr(x) willbe:

1100 0111 0000 0100 1101 1101 0111 1011(coefficients of x31 through x0 , respectively).

COMMENTARY

The notation used to describe the CRC is based onthe property of cyclic codes that any code vector,such as 1000000100001, can be represented by apolynomial G(x) = x12 + x5 + 1. The elements of an nelement code word are thus the coefficients of apolynomial of order n - 1. In this application, thesecoefficients can have the value 0 or 1 and allpolynomial operations are performed modulo 2. Thepolynomial representing the information content of aframe is generated starting with the Frame bit whichis encoded in bit 9 of the first ARINC 429 data word(following the SOF word) as the coefficient of thefirst (highest order) term.

3.4.10 Incomplete FDU Timer

The Incomplete FDU (T17) timer is used to insure that asource device does not “lock-up” a sink with anincomplete frame.

The sink will start the T17 timer when it receives arespective SOF word.

In case of an Information frame the T17 timer is stoppedwhen both valid EOF words are received.

In case of a Command frame the T17 timer is stoppedwhen a single valid EOF word is received.

The T17 timer should also be stopped if the sink discardsthe partial frame for other reasons defined in thisspecification. When T17 is exceeded, the sink shoulddiscard any partial frame already received and ignore anydata until a proper SOF word is received.

3.4.11 ALOHA

The first ALOHA word transmitted in a sequenceshould contain the highest Version Number supportedby the source device. If the ALOHA Response containsa version that does not match the ALO version, thesource device should take one of the following actions:

a. If the source device is able to adapt to thedifferences in protocol version, file transfers mayproceed using the protocol version identified in theALR word.

c-17 c-17



b. If the source device is not able to adapt to thedifferences in protocol version, the source should againinitiate the ALOHA word with the version field set tothe highest version supported by the source that is lowerthan the version indicated in the previous ALR (seeexamples identified in Attachment 13A).

The ALO/ALR protocol determination process shouldcontinue until a common protocol version is found. If eithera protocol version is found or none of the protocol versionsmatch, the source should notify the local MAC ServiceClient with a MA_DATA.indication with itsreception_status set to notify a reset condition. Theparameter in the primitive only has local significance andprovides the MAC Service Client with status information.

When the system only supports bit-oriented protocols, itshould repeat the process described in this section.

When the system also supports character oriented protocols,then the process defined in Section 2.5.19.2 should befollowed. The protocol determination process will continueuntil a common protocol is found. See Attachment 17.

The ALOHA word should contain a Subsystem SAL field asshown in Attachment 11, Table 11-4. This field shouldcontain the SAL of the device sending the ALOHA word,with bit 17 as the most significant bit and bit 24 as the leastsignificant bit of the Subsystem SAL.

A device that supports the bit-oriented Link layer protocolshould always be able to respond to the receipt of the ALOword.

Whenever a device receives the ALO word, it should leaveits present task and respond within T15 with an ALR word.

The ALR response should reflect the device’s protocolversion level by the way of the Version Number containedwithin the ALR word. If the Version Number of the ALOdoes not match the sink device’s protocol Version Number,the sink device should select the next lowest versionsupported (equal to or lower than the version indicated bythe previous ALO word) and indicate this new version in theALR word.

If the device was in the sink mode (had already begunreceiving a FDU), it should discard any partial FDU it hadreceived.

If the device was in the source mode (had already beguntransmitting a FDU), it should resend the FDU beginningwith the first word of the FDU.

Because Option O12 is selected, the device receiving anALOHA word should use the Subsystem SAL from theALOHA word as the SAL of the ALOHA Response (ALR)word and for all subsequent bit-oriented protocoltransmissions for that interface.

3.4.12 Validation of FDUs

The receiving MAC sublayer should determine the validityof the incoming Start of Frame (SOF) word, the MACframe, and the End of Frame (EOF) words before passingthe MAC frame to its local Service Client. The SOF, MACframe, and EOF are collectively referred to as a Frame DataUnit (FDU). The following subsections list conditions for

which the FDU is said to be invalid in addition to theconditions already identified in sections 3.3.1.5 and3.3.2.4 for invalid frames. The contents of invalid MACframes should not be passed to the local MAC ServiceClient.

3.4.12.1 Missing SOF Word

The Information SOF word should be formatted asdepicted in Attachment 11, Table 11-10 and should bethe first word of the transmitted information FDU. TheCommand SOF word should be formatted as depicted inAttachment 11, Table 11-8 and should be the first wordof the transmitted command FDU. If the SOF word isnot received as the first word, the MAC frame isinvalid.

3.4.12.2 Missing EOF Word(s)

Two EOF words should follow the transmission of thefinal data words of an Information MAC frame. Theyshould be formatted as depicted in Attachment 11,Table 11-11. If either or both are missing, or are notformatted as depicted in Attachment 11, Table 11-11,then the MAC frame is invalid.

One EOF word should follow the transmission of thefinal data words of a Command MAC frame. It shouldbe formatted as depicted in Attachment 11, Table 11-9.If it is missing, or is not formatted as depicted inAttachment 11, Table 11-9, then the MAC frame isinvalid.


Bit 32 of each ARINC 429 word should be set to oddparity for the entire word. Upon receipt of a word, thereceiving unit should verify that each word wasreceived with odd parity. If any word is received witheven parity, the receiving unit should take no action andignore the word.

COMMENTARY

When the receiving MAC sublayer receives a wordwith bad parity, it cannot be sure of the intendedlabel. The word may not even be a part of the FDU,so by ignoring the offending word, there may still bea chance of a successful FDU transfer. If theoffending word was intended to be a part of theFDU, then when the EOF word(s) are received, theactual word count will not match the expected wordcount (and the CRC will probably be invalid). If theword count is incorrect (or if the CRC is invalid),then the MAC frame is also invalid, as per Sections3.4.12.5 and 3.4.12.4 (or Sections 3.3.1.5.3 and3.3.2.5.1 for invalid CRC).


Upon receipt of the final EOF word of the FDU, thereceiving MAC sublayer should verify that the actualnumber of words received is the number of wordsexpected, as per bits 18-9 of the SOF word. If the wordcounts do not match, the MAC frame is invalid.

c-17

c-17



3.4.12.5 CRC Errors

Upon receipt of the final EOF word of the FDU, thereceiving MAC sublayer should verify the CRC of thereceived MAC frame. If the CRC is invalid, the MAC frameis also invalid and should be discarded.

The FDU should contain an integral number of octets inorder to pass the FCS.

3.4.13 Inter-FDU Gap Time

An inter-Frame Data Unit gap time, T18, of 10 ms minimumshould be implemented between any two successive MACframe transmissions in order to allow the receiving MACsublayer sufficient CRC verification time between frames.

Timer T18 is closely related to the generation of the CRCfield for the Information frame. If a CRC is not to begenerated (O15 = No), this timer is not necessary andimplementation is optional.

c-17


ATTACHMENTS 1 - 9

Attachments 1 through 9 are included in ARINC Specification 429 Part 1 and therefore are not used in ARINC Specification429, Part 3. These attachment numbers are not used to maintain consistency with previous versions of ARINC Specification429.

c-16


ATTACHMENT 10VARIABLES OF BIT-ORIENTED PROTOCOL

Table 10-1 BIT-ORIENTED PROTOCOL EVENTSEVENT DESCRIPTION OF EVENT STANDARD

VALUE [1]

N1 MAX NUMBER OF RTS REPEATS FOLLOWING NCTS 5

N2 MAX NUMBER OF RTS REPEATS FOLLOWING BUSY 20

N3 MAX NUMBER OF RTS REPEATS FOLLOWING NO RESPONSE 5

N4 NUMBER OF NAK WORDS RECEIVED BEFORE DECLARINGFAILURE OF COMMUNICATION

3

N5 NUMBER OF SYN WORDS RECEIVED BEFORE DECLARINGFAILURE OF COMMUNICATION

3

N6 MAX NUMBER OF ALO REPEATS FOLLOWING NO RESPONSE 3

Table 10-2 BIT-ORIENTED PROTOCOL APPLICATION SELECTIONAPPLICATION CONDITION STANDARD ACTIONS

A1 WHEN T2 N1 EXCEEDED REPORT TO HIGHER LEVEL ENTITYA2 WHEN T4 N2 EXCEEDED REPORT TO HIGHER LEVEL ENTITYA3 WHEN T5 N3 EXCEEDED REPORT TO HIGHER LEVEL ENTITY

Table 10-3a BIT-ORIENTED PROTOCOL OPTIONS FOR VERSION 1OPTION DESCRIPTION STANDARD INTERFACE [1]

O1 Half or Full Duplex Operation Half DuplexO2 High or Low Speed Bus LowO3 Automatic CTS when ready No [5]O4 Accept Auto CTS No [5]O5 Sys Priority to resolve RTS Conflict YesO6 Reserved --O7 Reserved --O8 Use of SOLO Word YesO9 Reserved --O10 Dest Code in RTS/CTS/NCTS/BUSY used YesO11 Bit-Protocol verification YesO12 Use Subsystem SAL from ALO word No

c-16

c-16



Table 10-3b - BIT-ORIENTED PROTOCOL OPTIONS FOR VERSION 3Option Description Standard Interface [1] Notes

O1 Half or Full Duplex Operation Full DuplexO2 High or Low Speed Bus High

O3 Automatic CTS when ready N/AO4 Accept Auto CTS N/AO5 Sys Priority to resolve RTS Conflict N/AO6 Spare --O7 Spare --O8 Use of SOLO Word Yes 6O9 Spare --O10 Destination Code in RTS/CTS/NCTS/BUSY

usedN/A

O11 Bit-Protocol verification YesO12 Use Subsystem SAL from ALO word YesO13 Use of Information or Command frames 7O14 Use of Pause Function 7O15 Generation (Yes) or Non-generation (No) of 32

bit CRC for Information frameYes 8

NOTES:

[1] The STANDARD VALUE (or STANDARD INTERFACE) should be used as the default value if a specific value isnot designated in the applicable equipment specification. For example, the standard interface for option 2 (429 busspeed) defaults to low speed for version 1 systems, unless high speed is specified in equipment specifications.Values shown as N/A indicate that option cannot be used.

[2] For those timers that are not associated with a repeat sequence, it is intended that a working system has minimizedactual response times. For example: A system should reply with CTS as soon as possible after reception of RTS. It isnot intended that a system take the maximum time T1 to reply to the RTS on a routine basis.

[3] T6 and T7 are used when Option 5 (O5) is not selected.

[4] Implementation of timer T10 is optional. If T10 is not used, T16 should be used.

[5] 03 and 04 should be Yes for expedited file transfer. See Section 2.5.7.3.

[6] The SOLO Word is not bridgeable to Ethernet and should only be used in conjunction with Command frame (non-bridgeable) interfaces.

[7] Options 13 and 14 are dependent on the applicable equipment interface specification. For a point to point onlyinterface, such as the CMU/VDR VDL Mode 2 Interface, Option 13 is set to ‘Command Frame’. For equipmentinterfaces that may need to be bridgeable to Ethernet, Option 13 is set to ‘Information frame.’ If the Pause Functionoption is selected as ‘Yes’, then the Pause function will be formatted into a Command FDU if Option 13 is set to‘Command Frame’, or into an Information FDU if Option 13 is set to ‘Information Frame’.

[8] Selection of Option 15 is dependent on the applicable equipment interface specification.

c-17



Table 10-4 VARIABLES OF LOW SPEED BIT-ORIENTED PROTOCOL - VERSION 1

TIME DESCRIPTIONMINVALUE

MAXVALUE

TIMER ORDESIGN GOALFOR SOURCE ORSINK NOTES REFERENCE

T1 CTS/NCTS Send Time 0 ms 100 ms Goal for Sink 2 2.5.7

T2 RTS Repeat TimeAfter Receipt of NCTS

500 ms 700 ms Timer for Source 2.5.7.2

T3 Busy Send Time 0 ms 100 ms Goal for Sink 2 2.5.7.3

T4 RTS Repeat TimeAfter Receipt of Busy

15 sec 18 sec Timer for Source 2.5.7.3

T5 RTS Repeat TimeIf No Response


T6 Time of Random Timer toResolve RTS Conflicts

50 ms 500 ms Goal for Source 3 2.5.8.1

T7 Increment of Time T6 10 ms 100 ms Goal for Source 3 2.5.8.1

T8 ACK/NAK/SYN SendTime

0 ms 200 ms Goal for Sink 2 2.5.13

T9 LDU TimeoutFollowing CTS

2.5 sec 2.7 sec Timer for Sink 2.5.13.2

2.5.13.6

T10 ACK/NAK Timeout 2.7 sec 3.0 sec Timer for Source 4 2.5.16

T11 Loop Back Send Time 0 ms 100 ms Goal for Sink 2 2.5.17.1

T12 ALO Repeat Timeif No Response to ALO


T13 SOT Send TimeAfter Receipt of CTS

0 ms 200 ms Goal for Source 2 2.5.10

T14 Incomplete File Timeout 2 min 2.2 min Timer for Sink 2.5.14.3

T15 ALR Send Time 0ms 180 ms Goal for Sink 2 2.5.19.1.2

T16 ACK/NAK TimeoutAfter EOT

220 ms 330 ms Timer for Source 2.5.16

c-16



Table 10-5 VARIABLES OF HIGH SPEED BIT-ORIENTED PROTOCOL - VERSION 1

TIME DESCRIPTIONMIN

VALUEMAX

VALUE

TIMER OR DESIGN GOALFOR SOURCEOR SINK NOTES REFERENCE

T1 CTS/NCTS Send Time 0 ms 100 ms Goal for Sink 2 2.5.7

T2 RTS Repeat TimeAfter Receipt of NCTS


T3 Busy Send Time 0 ms 100 ms Goal for Sink 2 2.5.7.3

T4 RTS Repeat TimeAfter Receipt of Busy

1.0 sec 1.2 sec Timer for Source 2.5.7.3

T5 RTS Repeat TimeIf No Response


T6 Time of Random Timer toResolve RTS Conflicts

50 ms 500 ms Goal for Source 3 2.5.8.1

T7 Increment of Time T6 10 ms 100 ms Goal for Source 3 2.5.8.1

T8 ACK/NAK/SYN SendTime

0 ms 200 ms Goal for Sink 2 2.5.13

T9 LDU TimeoutFollowing CTS

400 ms 440 ms Timer for Sink 2.5.13.2

2.5.13.6

T10 ACK/NAK TimeoutAfter CTS

600 ms 660 ms Timer for Source 4 2.5.16

T11 Loop Back Send Time 0 ms 100 ms Goal for Sink 2 2.5.17.1

T12 ALO Repeat Timeif No Response to ALO


T13 SOT Send TimeAfter Receipt of CTS

0 ms 100 ms Goal for Source 2 2.5.10

T14 Incomplete File Timeout 10 sec 11 sec Timer for Sink 2.5.14.3

T15 ALR Send Time 0 ms 180 ms Goal for Sink 2 2.5.19.1.2

T16 ACK/NAK TimeoutAfter EOT

220 ms 330 ms Timer for Source 2.5.16

c-16



Table 10-6 - VARIABLES OF HIGH SPEED CONNECTIONLESS BIT-ORIENTED PROTOCOL - VERSION 3

TIME DESCRIPTION MIN VALUE MAX VALUE TIMER ORDESIGN GOALFOR SOURCE

OR SINK

NOTES REFERENCE

T1

T2

T3

T4

T5

T6

T7

T8

T9

T10

T11

T12 ALO Repeat Time if NoResponse to ALO

200 ms 250 ms Timer for Source

T13

T14

T15 ALR Send Time 0 ms 180 ms Goal for Sink

T16

T17 Incomplete FDUTimeout

750 ms 1 sec Timer for Sink

T18 Inter-FDU Gap Time 10 ms N/A Timer for Source 1

NOTE:

[1] The minimum value is specified to give the sink time to finish processing an FDU before the next FDU arrives.The designer is encouraged to use the min value of 10 ms in order to make optimal use of the ARINC 429 databus bandwidth. A maximum value cannot be specified because of the aperiodic nature of the data sent by mostapplications that use the ARINC 429W file transfer protocol. If the LRU does not have another FDU to transmitthen this gap will be very large (seconds, minutes, hours!).

c-17



Table 10-7 VARIABLES OF LOW SPEED CONNECTIONLESS BIT-ORIENTEDPROTOCOL - VERSION 3

TIME DESCRIPTION MIN VALUE MAX VALUE TIMER ORDESIGN GOALFOR SOURCE

OR SINK

NOTES REFERENCE

T1

T2

T3

T4

T5

T6

T7

T8

T9

T10

T11

T12 ALO Repeat Time if NoResponse to ALO

200 ms 250 ms Timer for Source

T13

T14

T15 ALR Send Time 0 ms 180 ms Goal for Sink

T16

T17 Incomplete FDUTimeout

7.5 seconds 1 sec Timer for Sink

T18 Inter-FDU Gap Time 10 ms N/A Timer for Source 1

NOTE:

[1] The minimum value is specified to give the sink time to finish processing an FDU before the next FDU arrives.The designer is encouraged to use the min value of 10 ms in order to make optimal use of the ARINC 429 databus bandwidth. A maximum value cannot be specified because of the aperiodic nature of the data sent by mostapplications that use the ARINC 429W file transfer protocol. If the LRU does not have another FDU to transmitthen this gap will be very large (seconds, minutes, hours!).

c-16

c-18



NOTES:

1 The STANDARD VALUE (or STANDARD INTERFACE) should be used as the default value if a specific value isnot designated in the applicable equipment specification. For example, the standard interface for option 2 (429 busspeed) defaults to low speed for version 1 systems, unless high speed is specified in equipment specifications.Values shown as N/A indicate that option cannot be used.

2 For those timers that are not associated with a repeat sequence, it is intended that a working system has minimizedactual response times. For example: A system should reply with CTS as soon as possible after reception of RTS. Itis not intended that a system take the maximum time T1 to reply to the RTS on a routine basis.

3 T6 and T7 are used when Option 5 (O5) is not selected.

4 Implementation of timer T10 is optional. If T10 is not used, T16 should be used.

5 O3 and O4 should be Yes for expedited file transfer. See Section 2.5.7.3.

c-16

c-16


ATTACHMENT 11BIT-ORIENTED DATA FILE TRANSFER WORD FORMATS

NOTE: All reserved fields should be set to binary 0

Table 11-1 GENERAL WORD FORMAT

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

[1] P Word TypeGFI, ControlData or WordTypeExtensions

DATA SAL

Table 11-1A WORD TYPE

31 30 29 WORD TYPE0 0 0 Full Binary Data Word0 0 1 Partial Binary Data Word0 1 0 Start of Frame – Version 30 1 1 End of Frame – Version 31 0 0 Protocol Word1 0 1 Solo Word1 1 0 Start Of Transmission – Version 11 1 1 End Of Transmission – Version 1

Table 11-2 FULL DATA WORD

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

[2] P 0 0 0 n5 n4 n3 n2 n1 SAL

Table 11-3 PARTIAL DATA WORD

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

[2]

[3]

PPPP 0 0 1 1 0 1 1 n4 n3 n2 n1

SALSALSALSAL

Table 11-4 PROTOCOL WORD

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1RTS P 1 0 0 0 0 0 1 Destination Code [4] Word Count [5] SALCTS P 1 0 0 0 0 1 0 Destination Code . Word Count . SAL

NCTS P 1 0 0 0 0 1 1 Destination Code . Status Code [6] SALBUSY P 1 0 0 0 1 0 0 Destination Code . Status Code . SALNAK P 1 0 0 0 1 0 1 File Sequence Number Status Code . SALACK P 1 0 0 0 1 1 0 File Sequence Number LDU Sequence Number SALAL0 P 1 0 0 0 1 1 1 Subsystem SAL [7] 0 0 0 0 Version No.

[10]SAL

ALR P 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Version No.[10]

SAL

SYN P 1 0 0 1 0 0 1 File Sequence Number Status Code [6] SAL

c-16

c-16

c-16

c-16



Table 11-4A ALO-ALR VERSION NUMBER (See Appendix H)

12 11 10 9 APPLICABILITY NOTES0 0 0 0 Changes to Sec. 2.5 by Supplement 12 of ARINC 429, Part 3 80 0 0 1 Changes to Sec. 2.5 through Supplement 16 of ARINC 429, Part 3 80 0 1 0 Obsolete, formerly defined in Sec. 2.6 of ARINC 429, Part 30 0 1 1 Section 3.0 of ARINC 429, Part 30 1 0 0 Reserved

. Reserved

. Reserved1 1 1 0 Reserved1 1 1 1 Reserved

Table 11-4B ALO-ALR WINDOW SIZE

This table deleted by Supplement 16.

Table 11-5 SOLO WORD

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

TESTLOOPSOLO

PPP 1 0 1 I. D. 16-Bit Data Field

SALSALSAL

Table 11-6 START OF TRANSMISSION

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1SOT P 1 1 0 GFI File Sequence Number LDU Sequence Number SAL

c-16

c-16

c-16



Table 11-6A GENERAL FORMAT IDENTIFIER (GFI)

Bit

28 27 26 25 Description Notes0 0 0 0 Reserved 10 0 0 1 Reserved0 0 1 0 Command-Control Data0 0 1 1 General Purpose Bit-Oriented Protocol (GPBOP)0 1 0 0 ISO 95770 1 0 1 Reserved0 1 1 0 Reserved0 1 1 1 Reserved1 0 0 0 Reserved1 0 0 1 Reserved1 0 1 0 Reserved1 0 1 1 Reserved1 1 0 0 Reserved1 1 0 1 Reserved1 1 1 0 ACARS VHF Format1 1 1 1 Extended GFI

NOTE:

[1] For consistency with Version 1, the GFI value (0000) is discouraged. The value 0000 should only be used forlocal communications between 2 LRUs that will never need to use a different file format on that ARINC 429bus. The data format for the GFI ‘0000’ is unique to that particular interface and is not defined herein.

Table 11-7 END OF TRANSMISSION

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1EOT 1 1 1 0 0 0 X LSB Cyclic Redundancy Check (CRC) 9 MSB SAL

NOTE: Bit 25 of the EOT is the final LDU bit.

Table 11-7A FINAL LDU BIT

25 DESCRIPTION0 Not Final LDU1 Final LDU

c-17

c-14



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 1P 0 1 0 GFI CT Reserved I/C ARINC 429 Word Count U SAL

Where:P – 32 Bit ParityGFI – General Format Identifier (GFI) FieldCT – Command Type Field00 Command Path01 Data Path10 MAC Control11 ReservedI/C – Information/Command Frame Identifier Field; 00-Information; 01-Command, 10, 11-ReserveWord Count Field – 10 bits for a Command Frame, Max Command Frame size = 2552 bytesU SAL – Unique (standard ARINC 429) System Address Label (SAL) (same as Version 1)

Table 11-9 COMMAND FRAME EOF

Version 3 Command Frame EOF

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1P 0 1 1 0 0 0 1 LSB FCS (16 Bit CRC) MSB U SAL

Where:P – 32 Bit ParityBit 25 (Command Frame Final Bit) for EOF word always set to 1FCS – Frame Check Sequence, 16-bit CRC for Command Frame

Table 11-10 INFORMATION FRAME SOF

Version 3 Command Frame SOF

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1P 0 1 0 Reserved I/C ARINC 429 Word Count M/B/U SAL

Where:P – 32 Bit ParityI/C – Information/Command Frame Identifier Field; 00-Information; 01-Command; 10, 11- ReservedWord Count Field – 10 bits for an Information Frame – Max Information Frame Size = 2550 bytes, Limit forBridgeability = 1500 bytesM/B/U SAL – Multicast/Bridge/Unique (standard ARINC 429) System Address Label (SAL)

c-17



Table 11-11 INFORMATION FRAME EOF

Version 3 Command Frame EOF

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1P 0 1 1 0 0 0 0 FCS (32-Bit CRC) MSB M/B/U SALP 0 1 1 0 0 0 1 LSB FCS (32-Bit CRC) M/B/U SAL

Where:P – 32 Bit ParityFCS – Frame Check Sequence, 32-bit CRC for Information FrameBit 25 for first half of Information Frame EOF word = 0Bit 25 for second half of Information Frame EOF word = 1

c-17



NOTES

[1] All words are transmitted using odd parity (denoted by P in bit 32).

[2] The MSB/LSB determination of the “Data” field for Full and Partial Data words is as follows:

The ordering of octets (or ASCII characters) is from right to left, i.e.:

A) The first (most significant) octet is in bits 16-9 of the first Data word.

B) The second octet is in bits 24-17 of the first Data word ,etc.

The ordering of bits within each octet (or ASCII characters) is:

A) The LSB of the first octet is in bit 9 of the first Data word.

B) The MSB of the first octet is in bit 16 of the first Data word.

C) The LSB of the second octet is in bit 17 of the first Data word, etc.

EXAMPLE: The encoding of “PHX” (using 7-bit ASCII characters with all pad bits set to 0) using oneFull Data Word and one Partial Data Word is:

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

“X” “H” “P”(Lower ½)

Word P 0 0 0 1 0 0 0 0 1 0 0 1 0 0 0 0 1 0 1 0 0 0 0 SAL

“X”(Upper ½)

Data Word 2 P 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 SAL

[3] Bits 24 through 31 of Partial Data Words are coded to avoid conflict with old RTS words, defined in Appendix F, which contains the ISO Alphabet control character "DC2" in bits 29 through 23.

[4] Destination Codes are contained in Attachment 11A.

[5] Word Count values of 0000 0000 through 0000 0010 are not used; i.e. values of Word Count may be 3 through 255(03 through FFh).

[6] Status Codes are contained in Attachment 11B.

[7] This is the System Address Label of the system which is sending out the ALO.

[8] Versions 0 and 1 are equivalent for the ALOHA (ALO) and ALOHA RESPONSE (ALR) Protocol Words.

[9] The MSB/LSB determination for all Link Layer CRC Computation is:

Bit 9 of the first Data word is the MSB (coefficient of the highest order term) of the polynomial representing the“message”. The LSB (coefficient of the lowest order term) of the polynomial representing the “message” is the mostsignificant bit of the last octet or character (which contains valid non-zero data) which will be found in the final dataword preceding the EOT Word.

[10] Bits 12 through 9 define the version number of the ARINC 429 bit-oriented protocol, as referenced in Table 11-4A.

c-16

c-14c-14

c-14


ATTACHMENT 11ADESTINATION CODES

BIT CODE [1]2 2 2 2 2 1 1 1DESTINATION

CHARARACTERCODE 4 3 2 1 0 9 8 7

NOTES

CABIN TERMINAL (1-4) 1-4

USER TERMINAL (5-8) 5-8

FMC, LEFT SIDE A 0 1 0 0 0 0 0 1

FMC, RIGHT SIDE B 0 1 0 0 0 0 1 0

CONTROL DISPLAY UNIT C 0 1 0 0 0 0 1 1

DFDAU D 0 1 0 0 0 1 0 0

CABIN PACKET DATA FUNCTION E 0 1 0 0 0 1 0 1

CFDIU F 0 1 0 0 0 1 1 0

GROUND STATION G 0 1 0 0 0 1 1 1

HF LINK H 0 1 0 0 1 0 0 0

EICAS/ECAM/EFIS I 0 1 0 0 1 0 0 1

AUTOMATIC DEPENDENT SURVEILLANCEUNIT (ADSU)

J 0 1 0 0 1 0 1 0

KEYBOARD/DISPLAY K 0 1 0 0 1 0 1 1

Unassigned L 0 1 0 0 1 1 0 0

ACARS MANAGEMENT UNIT (MU) M 0 1 0 0 1 1 0 1

FMC, CENTER N 0 1 0 0 1 1 1 0

OPTIONAL AUXILIARY TERMINAL O 0 1 0 0 1 1 1 1

PRINTER P 0 1 0 1 0 0 0 0

SATELLITE DATA UNIT, LEFT SIDE (SDU 1) Q 0 1 0 1 0 0 0 1 2

SATELLITE DATA UNIT, RIGHT SIDE (SDU 2) R 0 1 0 1 0 0 1 0 2

SATELLITE LINK S 0 1 0 1 0 0 1 1

HFDR Left T 0 1 0 1 0 1 0 0 6

HFDR Right U 0 1 0 1 0 1 0 1

VHF LINK (VDR) V 0 1 0 1 0 1 1 0

TAWS W 0 1 0 1 0 1 1 1

CVR X 0 1 0 1 1 0 0 0

Unassigned Y 0 1 0 1 1 0 0 1

Unassigned Z 0 1 0 1 1 0 1 0

INMARSAT SATELLITE LINK CONTROL CODE VT 0 0 0 0 1 0 1 1 3, 4

ICO SATELLITE LINK CONTROL CODE CR 0 0 0 0 1 1 0 1 3, 4

GLOBALSTAR SATELLITE LINK CONTROL CODE SO 0 0 0 0 1 1 1 0 3, 4

c-18

c-18

c-18

c-15

c-16

c-15

c-15

c-15

ARINC SPECIFICATION 429 PART 3 – Page 42

ATTACHMENT 11 ADESTINATION CODES

NOTES:

[1] The Destination Code may be a 7-bit ISO Alphabet No. 5 code with no parity, or, alternatively, a binary value.Bit 24 should contain a zero.

[2] Origin/Destination Codes Q and R are used when the SDU transmits/receives onboard messages as an ACARSend system.

[3] These are non-printable control codes (reference ARINC 429 Part 1 Attachment 5).

[4] These codes are used for the specific satellite links indicated; character code "S" is used for any available non-specific satellite link.

[5] Origin/Destination Codes T and U are used when the HFDR transmits/receives onboard messages as an ACARSEnd System. The code H is distinguished from codes T and U in that the H is used to designate the HFDR asthe downlink medium for a message while the T and U are used to indicate that the message is to be consumedby the DFDR.

[6] Transponder (XPDR) was removed from the DESTINATION column.

c-18

c-18


ATTACHMENT 11BSTATUS CODES

CODE (HEX) DESCRIPTION NAK NCTS BUSY SYN

00 No Information X X X X01 User Defined X X X X02 User Defined X X X X. . X X X X. . X X X X. . X X X X

7E User Defined X X X X7F User Defined X X X X80 Missing SOT Word X81 LDU Sequence Number Error X X82 Invalid GFI X83 Missing EOT Word X84 Invalid Destination Code X X85 CRC Error X86 LDU Time-Out Error X87 Restart Initialization X X88 Word Count Error X X89 Word Count Error/Input Overrun X8A Word Count Error/Parity Error X8B Sink Flow Control X X8C Buffer Full X X8D Device Off-Line X8E File Time-Out Error X8F Window with Multiple FSNs X90 Missing LDU Control Word X91 Remaining LDUs/Received LDUs Error X92 Window Size Exceeds Sink’s Receive

CapabilityX

93 Invalid LDU Count in Window X94 Invalid EOT in Window X95 New File with Previous Incomplete X96 Reserved. .. .

FE ReservedFF Reserved

c-15

c-15


ATTACHMENT 11CALOHA/ALOHA RESPONSE PROTOCOL WORD DEFINITION

Table 11C-1 VERSION 1 ALOHA INITIAL (ALO) PROTOCOL WORD EXAMPLE

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

P Protocol ALO Subsystem SAL of originator

[3]

Reserved [2] Version

Number [1]

SAL

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

[1] See Table 11-4A for version number.

[2] Reserved fields should be set to binary 0.

[3] This field should contain the SAL of the device sending the ALOHA word, with bit 17 as the mostsignificant bit and bit 24 as the least significant bit of the subsystem SAL.

Table 11C-2 VERSION 1 ALOHA RESPONSE (ALR) PROTOCOL WORD EXAMPLE

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

P Protocol ALR Reserved [2] Ver. Number [1] SAL

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

[1] See Table 11-4A for version number.

[2] Reserved fields should be set to binary 0.

NOTE: Table 11-C3 has been moved to Attachment 11, Table 11-4C.

c-16


ATTACHMENT 12VERSION 1 FILE TRANSFER EXAMPLE

SOURCE SINK

AIRLINESOURCE

RTS WORD

ORIGINAL

DATACTS WORD

FILE SOT WORD 1

DATA WORD 2

DATA WORD 3

o FIRST LDUoo

DATA WORD 254

EOT WORD 255

ACK WORD

RTS WORD

CTS WORD

SOT WORD 1

DATA WORD 2AIRCRAFT

DATA WORD 3 DESTINATION

LAST LDU DATA WORD 4

DATA WORD 5 RECEIVED

DATA WORD 6 DATA

EOT WORD 7 FILE

ACK WORD


ATTACHMENT 12AFIELD 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 MSBLSB MSB

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

n5 n4

P 0 0 0 B B B B B n3 B B n2 B B n1 B SAL

20 17 16 13 12 9 8 5 4 1

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

n1

P 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 B B SAL

24 21

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

P 1 1 1 0 0 0 * LSB CRC MSB SAL

* Final LDU Bit

This example takes 24 bits of data and puts it into two data words. For the CRC computation, the MSB is the bitposition that represents the coefficient of the highest order term of the polynomial.

SECOND WORD

EOT WORD

c-13c-13

c-14

Semi octet

OctetFIRST WORD


ATTACHMENT 13PROTOCOL 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 formator bit-oriented file transfer format. Assume Unit A will initiate the exchange to determine the protocol to be used.

UNIT A UNIT B

ALO

ALR

BIT-ORIENTED COMMUNICATIONS ESTABLISHED

Diagram 13-2 PROTOCOL DETERMINATION PROCEDURE DIAGRAM (ONE BILINGUALUNIT 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 filetransfer format. Assume that Unit B is only capable of communicating using the ARINC 429 character-oriented file transferformat. Assume Unit A will initiate the exchange to determine the protocol to be used.

UNIT A UNIT B

ALO

ALO

ALO

CHARACTER-ORIENTED RTS

CHARACTER-ORIENTED CTS

CHARACTER-ORIENTED COMMUNICATIONS ESTABLISHED

Assume Unit B will initiate the exchange to determine the protocol to be used.

UNIT A UNIT B


CHARACTER-ORIENTED CTS

CHARACTER-ORIENTED COMMUNICATIONS ESTABLISHED


ATTACHMENT 13 (cont'd)PROTOCOL DETERMINATION PROCEDURE DIAGRAMS

Diagram 13-3 PROTOCOL DETERMINATION PROCEDURE DIAGRAM(TWO CHARACTER-ONLY UNITS)

Assume that Unit A is only capable of communicating using the bit-oriented file transfer format. Assume that Unit B is capableof communicating only using the ARINC 429 character-oriented file transfer format. Assume Unit A will initiate the exchange todetermine the protocol to be used. The resulting "No Response" conclusion accurately identifies the inability of the two units tocommunicate.

UNIT A UNIT B

ALO

ALO

ALO

NO RESPONSE COMMUNICATIONS NOT POSSIBLE

Assume Unit B will initiate the exchange. The resulting “No Response” conclusion accurately identifies the inability of thetwo units to communicate.

UNIT A UNIT B




COMMUNICATIONS NOT POSSIBLE NO RESPONSE


ATTACHMENT 13AALOHA VERSION DETERMINATION SEQUENCE

Example #3SOURCE Dev ice : "A"Vers ions of pro tocol

suppor ted by th isdevice (1 , 2 & 5)

ALO: Vers ion = 5

SINK Device : "B"Vers ions of pro tocol

suppor ted by th isdevice (1)

ALR: Vers ion = 1

T i m e T i m e

Example #2SOURCE Dev ice : "A"

Vers ions of pro tocolsuppor ted by th isdevice (1 , 2 & 5)

ALO: Vers ion = 5

ALO: Vers ion = 2


suppor ted by th isdevice (1 , 2 , 3 & 6)

ALR: Vers ion = 3

ALR Vers ion = 1T i m e T i m e

Example #1

T i m eT i m e

SOURCE Dev ice : "A"Vers ions of pro tocol


ALO: Vers ion = 5

ALO: Vers ion = 2



ALR: Vers ion = 3

ALR Vers ion = 1



The listing of System Address Label (SAL) assignments is contained in Attachment 11 to ARINC Specification 429, Part 1.c-16


ATTACHMENT 15

NOTE: This attachment has been deleted by Supplement 16.

This Attachment number is not used in this Specification to maintain consistency with previous versions of ARINCSpecification 429 prior to its separation into 3 parts by Supplement 15 and to avoid confusion among the parts.

c-16


ATTACHMENT 16

NOTE: This attachment has been deleted by Supplement 16.

This Attachment number is not used in this Specification to maintain consistency with previous versions of ARINCSpecification 429 prior to its separation into 3 parts by Supplement 15 and to avoid confusion among the parts.

c-16


ATTACHMENT 17FLOW DIAGRAM USED TO DETERMINE CHARACTER-ORIENTED VS BIT-ORIENTED PROTOCOL

begin

at temptbit-orientedprotocol

fai led

at temptchar-or iented

protocol

fai led

wait 0-15 seconds

n o r m a lbit -orientedcommunica t ions

n o r m a lc o m m

n oresponse

n o r m a lchar-or ientedcommunica t ions

n o r m a lc o m m

n oresponse

l inkestabl ished

linkestabl ished


ATTACHMENT 18MAC SUBLAYER SUPPORT DIAGRAMS

NOTE: The MAC Control Sublayer is normally a pass through except for MAC Control PDUs that are processed by theMAC Control sublayer entity and are not passed to higher layers. The operation of the MAC Control Sublayeris defined in IEEE 802.3 Clause 31. MAC Control Functions are defined Section 3.2.4 of this Specification.

Figure 18-1 - MAC Sublayer and its Service Clients

LLC Sublayer

MAC ServiceClient

MAC Control

MAC Service Entity

MAC Control

MAC Service Entity

Physical Signaling(429)

Physical Signaling(429)

(3) Higher LayerEntity

(2) Data Link Layer

Media AccessControl (MAC)Sublayer

(1) Physical SignalingLayer

MAC ServiceClient

(802.2 LLC)

MAC ServiceClient

(802.2 LLC)

LLC ServiceClient

MAC ServiceClient

LLC ServiceClient

802.3-TYPE802.3-LENGTHc-17


ATTACHMENT 18MAC SUBLAYER SUPPORT DIAGRAMS

Figure 18-2 - MAC Control Sublayer Support Of Interlayer Service Interfaces

429 Medium Access Control

429 MAC Control Sublayer

429 Physical

Transmit

Receive

MA_CONTROL.Indication

MA_CONTROL.RequestMA_DATA.Indication

MA_DATA.Request

Receive Frame

(destination and source addresses, length/type,data, reception status, service class)

Transmit Frame

(destination address, length/type, data,service class)

MACSublayer

MAC ServiceClient

PhysicalLayer

c-17


ATTACHMENT 19COMMAND FRAME DATA UNIT (FDU) STRUCTURE AND EXAMPLES

Table 19-1 V3 Command Frame SOF

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1P 0 1 0 GFI CT Rsvd I/C ARINC 429 Word Count U SAL

Where:P – 32 bit ParityGPI – General Format Identifier (GFI) FieldCT – Command Type Field00 Command Path01 Data Path10 MAC Control11 ReservedI/C – Information/Command Frame Identifier Field; 00 – Information; 01 – Command, 10, 11 – ReservedWord Count Field – 10 bits for a Command Frame, Max Command Frame size = 2552 bytesU SAL – Unique (standard ARINC 429) System Address Label (SAL) (same as Version 1)

Table 19-2 V3 Command Frame (Full and Partial) Data Words

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

Table 19-3 V3 Command Frame EOF

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 10 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 1FCS – Frame Check Sequence, 16-bit CRC for Command Frame

c-17


ATTACHMENT 19COMMAND FRAME DATA UNIT (FDU) STRUCTURE AND EXAMPLES

Table 19-4 Example of Command Frame Data Unit (FDU) Containing a MAC Control Frame Requesting a5 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 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 0 0 0 1 0 0 0 U SALP 0 0 1 1 0 1 0 0 0 0 0 0 0 0 0 0 1 0 1 0 0 0 0 U SAL

V3 Command Frame EOF:

P 0 1 1 0 0 0 1 LSB FCS (16-Bit CRC) MSB U SAL

Where:GFI Field = X’s as placeholder for actual values used over interface (See Table 11-6A of Attachment 11)Pause Opcode – 16 bit field = 8808 hexRequest Operand – 16 bit field = Pause Time = 5 Pause Quanta = 0005 hex

c-17


ATTACHMENT 20INFORMATION FRAME DATA UNIT (FDU) STRUCTURE AND EXAMPLE

Table 20-1 Version 3 Information Frame SOF

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1P 0 1 0 Reserved I/C ARINC 429 Word Count M/B/U SAL

Where:P – 32 bit ParityI/C – Information/Command Frame Identifier Field; 00-Information; 01-Command; 10, 11-ReservedWord Count Field – 10 bits for an Information Frame – Max Information Frame Size = 2550 bytes,Limit for Bridging = 1500 bytesM/B/U SAL – Multicast/Bridge/Unique (standard ARINC 429) System Address Label (SAL)

Table 20-2 Version 3 Information Frame (Full and Partial) Data Words

BIT 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1P 0 0 0 Destination LSB M/B/U SALP 0 0 0 Destination M/B/U SALP 0 0 0 Source LSB MSB Destination M/B/U SALP 0 0 0 Source M/B/U SALP 0 0 0 Length/Type LSB MSB Source M/B/U SALP 0 0 0 Data MSB Length/Type M/B/U SALP 0 0 0 Data M/B/U SALP 0 0 0 Data M/B/U SALP 0 0 0 Data M/B/U SAL

Where:P – 32 bit ParityDestination – 48 Bit MAC Destination AddressSource – 48 Bit MAC Source AddressLength/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 1P 0 1 1 0 0 0 0 FCS (32-Bit CRC) MSB M/B/U SALP 0 1 1 0 0 0 1 LSB FCS (32-Bit CRC) M/B/U SAL

Where:FCS – Frame Check Sequence, 32-bit CRC for Information FrameBit 25 for first half of Information Frame EOF word = 0Bit 25 for second half of Information Frame EOF word = 1

c-17


ATTACHMENT 20INFORMATION FRAME DATA UNIT (FDU) STRUCTURE AND EXAMPLE

Table 20-4: Example of Information Frame Data Unit (FDU) Containing a MAC Control Frame Requestinga 5 Pause Quanta (25 millisecond) Delay

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

V3 Information Frame SOF:

P 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 U SAL

V3 Information Frame (Full and Partial) Data Words:

P 0 0 0 X X X X X X X X X X X X X X X X X X X X U SALP 0 0 0 X X X X X X X X X X X X X X X X X X X X U SALP 0 0 0 Y Y Y Y Y Y Y Y Y Y Y Y X X X X X X X X U SALP 0 0 0 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y U SALP 0 0 0 1 0 0 0 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y U SALP 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 0 0 0 U SALP 0 0 1 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 U SAL

V3 Information Frame EOF:

P 0 1 1 0 0 0 0 FCS (32-Bit CRC) MSB U SALP 0 1 1 0 0 0 1 LSB FCS (32-Bit CRC) U SAL

Where:Destination – 48 Bit MAC Destination Address = X’s as placeholders (see ARINC Specification 664)Source – 48 Bit MAC Source Address = Y’s as placeholders (see ARINC Specification 664)Length/Type – 16 bit field = Pause Opcode = 8808 hexRequest Operand – 16 bit field = Pause Time = 5 Pause Quanta = 0005 hex

c-17


APPENDICES A - E

Appendices A through E are included in ARINC Specification 429, Part 1, ARINC Specification 429 and therefore not usedin this Part to avoid potential confusion due to duplication. In addition, this approach is used to maintain consistency withprevious versions of ARINC Specification 429 when it was published as a whole (through Supplement 14).

c-16


APPENDIX FFORMER AIM AND FILE DATA TRANSFER TECHNIQUES

AEEC Staff Note: See Supplements 4, 5, 6, 7. And 11 of ARINC Specification 429 Part 1 for changes prior to division ofARINC Specification 429 into separate parts.

The information contained in Sections F-2.1.5.2, F-2.1.5.3, F-2.3.1.4 and F-3.2 of this Appendix is no longer applicable toARINC Specification 429. The contents of Section F-2.3.1.5 provides guidance for character-oriented file transfer protocolsreflected in ARINC equipment characteristics. The information is contained herein for reference purposes.

COMMENTARY

Bit-oriented file transfer is the preferred protocol (See Section 2.5 of Part 3 of ARINC Specification 429) for use in newapplications. The guidance for character-oriented protocol was removed from the body of the specification to avoid thecontinuation of its use, but retained herein for those who need to understand the basis for character-oriented protocolalready implemented.

F-2.1.5 Sign/Status Matrix

F-2.1.5.2 AIM Data

The order function (first, intermediate, last or control) of AIM or maintenance data should be encoded in bit numbers 30 and31 of the word as shown in the table below. See Section F-2.3.1.4 of this document for definitions of the terms “InitialWord”, “Control Word”, “Intermediate Word” and “Final Word.”

AIM DATA SIGN/STATUS MATRIXBIT

31 30 MEANING0 0 Intermediate Word0 1 Initial Word1 0 Final Word1 1 Control Word

F-2.1.5.3 Character-Oriented File Transfer

The order and function (first, intermediate, last and control) of text and the sign (Plus/Minus, North/South, etc.) of numericdata transferred by file transfer should be encoded in bits 30 and 31 of each word as shown in the table below.

CHARACTER-ORIENTED FILE TRANSFER STATUS MATRIXBIT

31 30TEXT DATA

0 0 Intermediate Word Plus, North, etc.0 1 Initial Word Not Defined1 0 Final Word Not Defined1 1 Intermediate Word Minus, South etc.

Alternatively, the SSM field may be used to describe position in a series of data words (initial, intermediate, final) or wordcontent (control word). Sections F-2.3.1.5.2 through F-2.3.1.5.4 contain the definitions of the terms initial, intermediate andfinal words.

F-2.3.1 Digital Language

F-2.3.1.4 AIM Data

AIM data (Acknowledgement, ISO Alphabet No. 5 and Maintenance information encoded in dedicated words) should behandled in the manner described in this section.

All three of these applications may involve the transfer of more than 21 bits per “data package”. Source equipment shouldformat such long messages into groups of 32-bit DITS words, each word containing the relevant application label (seeARINC Specification 429, Part 1, Attachment 1) in bits 1 through 8, and a sign/status matrix code in bits 30 and 31.

c-18



Bit 32 should be encoded to render word parity odd. The first word of each group should contain the sign/status matrix codedefined for “initial word” in F-2.1.5.1. It should also contain, in bits 9 through 16, the binary representation of the number ofwords in the group, except that when this word is the only word to be transmitted, the total number of information bits to betransmitted is 13 or less) bits 9 through 16 should all be binary “zeros”. See ARINC Specification 429, Part 1, Attachment 6for word format.

When the word application label is assigned in ARINC Specification 429, Part 1, Attachment 1 for Acknowledgement Data,bits 17 through 29 of this initial word may be used for information transfer. When the word application label is either ofthose assigned in ARINC Specification 429, Part 1, Attachment 1 Maintenance Data (ISO Alphabet No. 5), bits 17 through22 should be binary 'zeros” (spares). When the label is for ISO Alphabet No. 5 Messages, bits 17 through 22 are used forunit addressing. Bit usage is given in the table below.

BIT

22 21 20 19 18 17

FUNCTION

0 0 0 0 0 0 All Call, All Groups

0 0 X X X X Group 0, Units 1-15

0 1 0 0 0 0 Group 1, All Call






Example:

1 0 1 0 1 0 Group 2, Unit 10

For ISO Alphabet No. 5 Messages and Maintenance Data bits 23 through 29 should take on the pattern of the IOS AlphabetNo. 5 control character “STX”.

The second word of the ISO Alphabet No. 5 and Maintenance Data (ISO Alphabet No. 5) application groups is an optionalcontrol word containing sign/status matrix code for “control” information for display. When it is used, bits 9 through 13should contain the binary representation of the line count, bits 14 through 16 should encode the required color, bits 17 and 18the required intensity, bits 19 and 20 the required character size and bit 21 should indicate whether or not the display isrequired to flash. See ARINC Specification 429, Part 1, Attachment 6 for the encoding standards. Bits 22 through 29 of theword should be binary “zeros” (spares).

Intermediate words, containing the sign/matrix code for “intermediate word”, follow the initial word of the group or thecontrol word, when used. Intermediate words are optional in the sense that they are only transmitted if more words than theinitial word and the final word (see below) are needed to accommodate the quantity of information to be transferred. Whenthe word application group label that is assigned in ARINC Specification 429, Part 1, Attachment 1 for Acknowledgement isused. Data bits 9 through 29 of that word are available for information transfer. When the word application label is either ofthose assigned in ARINC Specification 429, Part 1, Attachment 1 for ISO Alphabet No. 5 data transfer or Maintenance Data(ISO Alphabet No. 5), bits 9 through 29 of each word should be divided into three seven-bit bytes (bits 9 through 15, 16through 22 and 23 through 29), each of which contains one ISO Alphabet No. 5 character.

Each AIM application group transmission other than single-word transmission (see below) should be terminated with a wordcontaining the sign/status matrix code for “final word” defined in F-2.1.5.1. The data field of this word should be structuredsimilarly to that of the intermediate word. Any unused bit positions in ISO Alphabet No. 5 data transfer or MaintenanceData (ISO Alphabet No. 5) final words resulting from the number of ISO Alphabet No. 5 characters in the message beingone or two less than a number wholly divisible by three should be filled with binary “zeros.”



F-2.3.1.5 File Data Transfer

F-2.3.1.5.1 Command/Response Protocol

File data will consist of both ARINC 429 BNR numeric words and ISO Alphabet No. 5 characters. A file may contain from1 to 127 records. Each record may contain from 1 to 126 data words.

A record should contain, at the minimum, one of the eight versions of the “initial word” described in F-2.3.1.5.2. Records inwhich this initial word contains the “Data Follows” code should also contain from 1 to 126 “intermediate words” (data) and a“final word” (error control). The file data transfer protocol is as follows. A transmitter having the data to send to a receivertransmits, on the bus connecting it to that receiver, the “Request to Send” initial word. The receiver responds, on theseparate bus provided for return data flow, with the “Clear to Send” reply. The transmitter then sends the “Data Follows:initial word, the “intermediate words” and the “final word”. The receiver processes the error control information in the ‘finalword” and, if no errors are revealed, closes out the transaction by sending the “Data Received OK” word to the transmitter.

If the receiver is not ready to accept data when the transmitter sends its “Request to Send” word, it should so indicate itsresponse (See F-2.3.1.5.2). The transmitter should then wait 200 milliseconds and retransmit the “Request to Send”. Thetransmitter should also repeat a “Request to Send” transmission 50 milliseconds after the initial transmission if no response isobtained from the receiver. If 2 additional attempts also spaced at 50 milliseconds produce no response from the receiver,the transmitter should send the data. This feature is incorporated to enable file transfer (under a degraded mode of operation)in the event of a failure in the receiver-to-transmitter bus.

If the receiver detects a parity error during the transmission, it may request an error-correcting retransmission by sending a“Data Received Not OK” word to the transmitter in which is identified the record in which the error occurred. Thetransmitter should interrupt the data flow and back up to the start of the record so identified. It should then send a “DataFollows” initial word identifying this record as the starting point of the retransmission and recommence its output of data,continuing through the “final word”. The receiver should then close out the transaction as before.

An error detected by processing the error control information in the “final word” should also result in the receiver sending a“Data Received Not OK” word to the transmitter. In the absence of identification of the record in which the error occurred,this word should contain the sequence number of the first record of the file. The transmitter's response should be toretransmit the whole file.

The receiver can signal loss of synchronization to the transmitter at any time bysending the “Synchronization Lost” initialword. On receiving this word, the transmitter should curtail the data flow and back up to the beginning of the file. It shouldthen re-establish that the receiver can accept data by going through the request-to-send routine. Having done this it shouldsend the “Data Follows” initial word, followed by the data and the “final word”.

The protocol also allows a transmitter to send the file size information to a receiver without any commitment to send, orrequest to the receiver to accept, the file itself. The “Header Information” initial word is used for this purpose. Additionally,a “Poll” initial word is defined for use in the system which continuous “hand-shaking” between two terminals is desired. The response to a “Poll” word will be either a “Request” to Send” initial word when the polled terminal does have data totransmit, or another “Poll” word when it does not. An exchange of “Poll” words may be interpreted as the message, “I havenothing for you, do you have anything for me?”

F-2.3.1.5.2 Initial Word Types

The eight initial types are as follows:

Request to SendClear to SendData FollowsData Received OKData Received Not OKSynchronization LoseHeader InformationPoll

Bits 1 through 8 of all of those words except the “Poll” word contain the label code identifying the file to be transferred usingthe protocol. Bits 1 through 8 of the “Poll” word contains binary zeros. Bits 9 through 29 are divided into three seven-bitfields, the contents of which vary with word type as shown in Table A below. Bits 30 and 31 contain the code identifyingthem as initial words while bit 32 is encoded to render word parity odd.



NOTES

1. The amount of data the receiver can accept upon receipt of a “Request to Send” signal is determined by the rate at whichdata delivery can take place and the amount of time the receiver has available before it must turn its attention to someother function. The receiver will set the count code in bits 9-15 of the “Clear to Send” word to indicate the number ofmaximum length records it can accept when it determines that the “Request to Send signal originates in a high speeddata source. It will set this code to indicate the number of 32-bit words it can accept when it determines that the“Request to Send” originates in a low speed data source, e.g., the ACARS ground-to-air link. The receiver willannunciate the contents of this field (record count or word count) by setting Bit 22 as indicated. It will determine thehigh or low speed nature of the source by port identification of the source of the “Request to Send” signal, the “Requestto Send” word label, the SDI code or some combination of these information items.

2. The record sequence number is the number of that record in a multiple-record file being transmitted.

F-2.3.1.5.3 Intermediate Words

Intermediate words contain the data being transmitted by means of the protocol. Bits 1 through 8 contain the file label. Bits9 through 29 can accommodate three ISO Alphabet No. 5 characters or one ARINC 429 BNR numeric word without itslabel. Note that this alpha/numeric data interleaving capability without labels necessitates a prior agreement betweentransmitter and receiver on data format. Bits 30 and 31 contain the word code or the sign information (only) encoded in thesign/status matrix of BNR numeric data words. Bit 32 is encoded to render the word parity odd.

F-2.3.1.5.4 Final Words

The final word of each record contains error control information. Bits 1 through 8 contain the file label. Bits 9 through 29contain an error control checksum computed from the states of bits 9 through 29 of all intermediate words of the record. Theerror control checksum should be generated by the arithmetic addition of the binary values of bits 9 through 29 of allintermediate words and discarding the overflow. Bits 30 and 31 of this word contain the code identifying it as a final word. Bit 32 is encoded to render the word parity odd.

F-2.3.1.5.5 Word Type Encoding

Bits 30 and 31 of each word used in data file transfer should be encoded to indicate word type as follows:

BIT31 30 WORD TYPE0

0

1

1

0

1

0

1

Intermediate Word requiring no sign data orhaving Plus, North, East, Above Right, or Tosign

Initial Word (all types)

Final Word

Intermediate Word having Minus, South,West, Below, Left, or From sign

F-2.3.1.5.6 File Data Formats

As noted in F-2.3.1.5.3, the transmission of file data words without labels necessitates the use of pre-arranged data formats. The need to standardize such formats was examined by the working group. The conclusion was reached that a standardformat was desirable for flight management computer flight plan updating and for computer cross-talk, but was not necessaryfor updating the computer's data base. Manufacturers are invited to submit proposals for a standard flight plan update fileand cross-talk bus formats.

F-2.3.1.5.7 File Data Labels Labels define the application of the file data to be transferred. Such application include FMC program load/update, flightplan load/update, the FMC inter-system cross-talk, etc. There may be a need to assign more than one label to some of thoseapplications if priority override capability is desired.



F-3.2 AIM Information Transfer

F-2.3.1.4 describes the techniques to be used for the transfer of Acknowledgement, ISO Alphabet No. 5 and Maintenance(ISO Alphabet No. 5) data by means of the Mark 33 DITS. The motivation for the adoption of this technique was labelconservation. Without it, a separate label would have to be assigned to each AIM word application for each source of suchdata. In it, labels are assigned by word application only, and (where necessary) utilization device input port recognitionutilized to identify sources. A special exception to this rule is made for the Airborne Integrated Data System (AIDS), asdescribed in F-2.3.1.4. The technique also accommodates the use of multiple-word DITS messages, as described in SectionF-2.3.1.4.

F-3.2.1 Acknowledgement Data

Source equipments responding to requests for acknowledgement of incoming data delivered via a DITS input port should doso in the manner described in F-2.3.1.4. No applications for this system capability have yet been identified and thus no datastandards for acknowledgement messages have been established.

F-3.2.2 ISO Alphabet No. 5 Data

Source equipment transmitting ISO Alphabet No. 5 information by means of the Mark 33 DITS should do so in the mannerdescribed in F-2.3.1.4. This application, and the use of ISO data for maintenance-related information transfer, will be themost likely to make use of the multiple-word message transmission capability of the system. Receiving equipment shouldmake use of the binary word count and the sign/status matrix codes of the words to ensure that such messages are received intheir entirety, with no words having been “lost along the way.” Only when this determination has been made, and the paritycheck for each word shows the data to be error-free, should the message be displayed to the crew or otherwise utilized.

F-3.2.3 Maintenance Data

Source equipment putting out data intended for a maintenance assist system on the aircraft should do so in the mannerdescribed in F-2.3.1.4. The Maintenance assist system should use input port recognition to identify data sources. TheMaintenance word as described by AIM data handling techniques is limited to IOS Alphabet No. 5 messages.



TABLE A - INITIAL WORD TYPESINITIAL

WORD TYPEFIELD(Bits) FIELD CONTENTS

Request to Send (Tx-to-Rx)

9-1516-2223-29

BNR count number of records to be sent (Max. 127)Binary zerosISO Alphabet No. 5 Control Character“DC2”

Clear to Send (Rx-to-Tx) See Note 1

9-15

16-2122

23-29

Binary zeros when receiver is not ready to accept data. BNR count of thenumber of maximum length of records OR the number of 32-bit words thereceiver can accept when it is readyBinary zerosBinary zero when receiver is not ready to receive data and when BNR counts in 9-15 is record count. Binary one when count in bits 9-15is 32-bit word count.ISO Alphabet Control Characters“DC3”

Data Follows (Tx-to-Rx) See Note 2

9-1516-2223-29

BNR count of number of words in record (Max. 126)Record Sequence No. (BNR)ISO Alphabet No. 5 Control Character“STX”

Data Received OK (Rx-to-Tx)

9-1516-22

BNR count of number of words in record (Max. 126)Record Sequence No. (BNR)ISO Alphabet No. 5 Control Character“ACK”

Data Received Not OK (Rx-to-Tx)

9-1516-2223-29

BNR count number of words in recordRecord sequence no. (BNR) in which error occurredISO Alphabet No. 5 Control Character“NAK”

Synchronization Lost (Rx-to-Tx)

9-1516-2223-29

Binary ZerosBinary ZerosISO Alphabet No. 5 Control Character“SYN”

Header Information (Tx-to-Rx)

9-1516-2223-29

BNR count of number of records in file to be transferredBinary ZerosISO Alphabet No. 5 Control Character“SOH”

Poll (B-directional)

9-1516-2223-29

Binary ZerosBinary ZerosISO Alphabet No. 5 Control Character“ENQ”


APPENDIX GMATHEMATICAL EXAMPLE OF CRC ENCODING/DECODING

NOTE: The following example describes the polynomial division procedure for CRC encoding and decoding. Arithmeticoperations are modulo 2. Actual software/hardware implementations are expected to vary significantly from this example,since these polynomial divisions are more efficiently simulated by logical operations.

For CRC computations, the MSB is the bit which represents the coefficient of the highest order term of the polynomial. Itis not related to the MSB or LSB of each individual octet. Slashes (/) are used to separate octets for readability only, anddo not denote division in this example.

The following (arbitrary) 24-bit message is to be transmitted with a CRC encoded:

10100111 / 10000111 / 10101100

(MSB) (LSB)

The mathematical procedure is as follows: For this message, k = 24, and

G(x) = x23 + x21 + x18 + x17 + x16 + x15 + x10 + x9 + x8 + x7 + x5 + x3 + x2.

x16G(x) = x16(x23 + x21 + x18 + x17 + ... + x7 + x5 + x3 + x2).

= x39 + x37 + x34 + x33 + ... + x23 + x21 + x19 + x18.

and

xk(x15 + x14 + x13 + x12 + x11 + ... + x3 + x2 + x + 1)

= x39 + x38 + x37 + x36 + ... + x27 + x26 + x25 + x24.

At The Transmitter: Using coefficients of the above polynomials, the dividend is calculated as follows:

x16G(x) = 1010 0111 1000 0111 1010 1100 0000 0000 0000 0000

and

xk(x15 + x14 +...+ x2 + x + 1) = 1111 1111 1111 1111 0000 0000 0000 0000 0000 0000

1010 0111 1000 0111 1010 1100 0000 0000 0000 0000+ 1111 1111 1111 1111 0000 0000 0000 0000 0000 0000= 0101 1000 0111 1000 1010 1100 0000 0000 0000 0000

Then the Dividend is: 0101 1000 0111 1000 1010 1100 0000 0000 0000 0000

and the Divisor, P(x) = x16 + x12 + x5 + 1, is: 1 0001 0000 0010 0001



P(x) = 1 0001 0000 0010 0001 is the divisor of the dividend below.

(Q(x), the quotient generated by the division process, is not used).

Q(x) = 101 1101 1010 1001 1101 1001

0101 1000 0111 1000 1010 1100 0000 0000 0000 0000100 0100 0000 1000 01

1 1100 0111 0000 11101 0001 0000 0010 0001

1101 0111 0010 1111 11000 1000 0001 0000 1101 1111 0011 1111 01

Using (synthetic) 100 0100 0000 1000 01 Polynomial 1 1011 0011 0111 0000Division: 1 0001 0000 0010 0001

1010 0011 0101 0101 01000 1000 0001 0000 1

10 1011 0100 0001 10010 0010 0000 0100 001

1001 0100 0101 1010 01000 1000 0001 0000 1

1 1100 0100 1010 1Note: Since all operations are Modulo 2,addition and subtraction are bothequivalent to XOR operations (no carries!)

1000 1000 0001 0000 11 0001 0010 1101 10001 0001 0000 0010 0001

R(x) = 0000 0010 1111 1001

CRC = R(x) = 1111 1101 0000 0110

M(x) = x16G(x) + CRC

= 1010 0111 1000 0111 1010 1100 0000 0000 0000 0000+ 1111 1101 0000 0110= 1010 0111 1000 0111 1010 1100 1111 1101 0000 0110

or

M(x) = 1010 0111 1000 0111 1010 1100 1111 1101 0000 0110

MSB (message) LSB MSB (CRC) LSB

M(x) is the transmitted message with CRC.



At The Receiver:

The dividend to be operated on by P(x) is determined (mathematically) as follows:

x16M(x) + x40(x15 + x14 + x13 + x12 + ... + x2 + x + 1)

= 1010 0111 1000 0111 1010 1100 1111 1101 0000 0110 0000 0000 0000 0000+ 1111 1111 1111 1111 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000= 0101 1000 0111 1000 1010 1100 1111 1101 0000 0110 0000 0000 0000 0000

The above string is the dividend used by the receiver.

(The divisor, 10001000000100001, is the same as that used by the transmitter.)

(The quotient, Q(x), generated by the division process, is not used.)

Q(x) = 101 1101 1010 1001 1101 1001 . . . .

0101 1000 0111 1000 1010 1100 1111 1101 0000 0110 0000 0000 0000 0000100 0100 0000 1000 01

1 1100 0111 0000 11101 0001 0000 0010 0001

1101 0111 0010 1111 11000 1000 0001 0000 1101 1111 0011 1111 01100 0100 0000 1000 01

1 1011 0011 0111 0000

1001 0110 1110 1101 01000 1000 0001 0000 1

1 1110 1111 1101 11101 0001 0000 0010 0001

1111 1111 1111 1111

Note: At this point, if the division iscarried through to termination, thefinal remainder is: Rr(x) = 0001 1101 0000 1111



LDU Mapping for 24-bit Example

Because of the transmission order of ARINC 429 32-bit words, the first bit of the first Data Word transmitted after the SAL is theMSB of the message (for CRC computations). Therefore, the actual transmission order of the bit string, M(x), is the reverse ofthe previous example, when mapped into 32-bit words.

The following represents the mapping of the preceding 24-bit message and CRC into an LDU for transmission:

MSB (message) LSB MSB (CRC) LSB

M(x) = 1010 0111 1000 0111 1010 1100 1111 1101 0000 0110

SOT Word P 110 GFI File No. LDU No. SAL

Full Data Word P 000 0101 1110 0001 1110 0101 SAL

Partial Data Word P 001 1000 0000 0000 0000 0011 SAL

EOT Word P 111 0001 0110 0000 1011 1111 SAL

Legend:

The CRC is calculated over these bits.

These are the CRC bits

LDU


APPENDIX HINTEROPERABILITY OF BIT-ORIENTED LINK LAYER PROTOCOL

H.1 Version Number Designators

The version number of a system is transmitted to the peer system in the ALO and ALR words.

• Version 1 systems are defined to be (Williamsburg) bit-oriented communication protocol systems, as defined inSection 2.0 this Specification.

• Version 2 systems are obsolete and have been deleted from ARINC Specification 429 - Part 3.

• Version 3 systems are defined to provide a standard MAC-based sublayer of the bit-oriented communications-protocol, and are defined in Section 3.0 of ARINC 429 - Part 3.

H.2 Interoperability - Same Version Number

Beginning with Supplement 13 of 429, any version 1 system should interoperate with any other version 1 system (i.e.,the version number should be independent of supplement number implementation.) For example, a version 1 429-13system should interoperate with a version 1 429-14 system.

Similarly, any version 3 system should interoperate with any other version 3 system (independent of supplementnumber).

In general, higher supplement numbers of the same version number clarify requirements.

H.3 Interoperability - Different Version Numbers

Version 1 and Version 3 can coexist on the same physical bus.

H.4 Bit-Oriented Link Layer GFIs for Standard Network Service

When a system implements a standard (e.g. ISO) network service, which resides directly above the 429 Version 1(Williamsburg), then the ISO GFI bit-coding of "4h" (for ISO 9577) as specified in ARINC 429-14 should be used.

ISO GFI bit-codings originally specified in ARINC 429-13 were "1h" for ISO 8208 and "4h" for ISO 8473. These GFIbit-codings are not compatible with the new GFI "4h" designator and should not be used as standard network serviceidentifiers.

c-16

c-16

c-17

ARINC CHARACTERISTIC 429 PART 3 - Page 72

APPENDIX ISDL DIAGRAMS OF THE VERSION 1 WILLIAMSBURG PROTOCOL

Air l ine_Source Source Aircraf t_ Dest inat ionS ink

Orig ina l_Data_Fi le

R T S

C T S

S O T

D A T A [ 2 ]

D A T A [ 3 ]

D A T A [ 4 ]

D A T A [ 2 5 4 ]

E O T

A C K

R T S

C T S

S O T

D A T A [ 2 ]

D A T A [ 3 ]

D A T A [ 4 ]

D A T A [ 6 ]

E O T

A C K

Received_Data_Fi le

/* * ARINC Speci f ica t ion 429, Par t 3 * * Note that some of the names in * the message sequence diagram in * At tachment 11 do not match names * in This Appendix * */

M S C - F i l e _ T r a n s f e r _ E x a m p l e

.

.

.

.

.

c-15



Sys tem Wi l l i amsburgDiagram (1)

/* * ARINC 429 Wil l iamsburg (Sect ion 2 .5) * * Author , W. Turner , K. Dihle ARINC 429 Wil l iamsburg Working Group * * This is the SDT descript ion of the 429 protocol * as developed by the 429W Working Group through * August 1994 * * */

/* * Notes: * * I t was not c lear what the Wil l iamsburg Convergence * Funct ion actual ly did, other than change the names * of the primit ives. Unless more defini t ions occur * in this area, the WCF wil l be removed in later * versions. * * LDU signal is not sent . Instead SOT, Data , EOT are used. * * Things to add to this defintion: * SOLO Words * Fi le Seq No/LDU Seq No. * n4count * n5count * Determine task of Segment and Reassemble .

L R U _ L y r _ 2

[ D L _ U N I T D A T A . i n d ]

[ D L _ U N I T D A T A . r e q ]

m_i f

[ D L _ E R R O R . i n d ]

(p429_both) ,(p429_to_s ink) ,(p429_to_source) ,SOT, EOT, Da ta

(p429_both) ,(p429_to_s ink) ,(p429_to_source) ,SOT, EOT, Da ta

Phys ica l_429_i f

Signal

D L _ U N I T D A T A

/* Th i s document i s based on mate r i a l submi t t ed by va r ious pa r t i c ipan t sd u r i n g t h e d r a f t i n g p r o c e s s . N e i t h e r A E E C n o r A R I N C h a s m a d e a n yde te rmina t ion whe the r these mate r i a l s cou ld be sub jec t to c l a imsof pa tent or o ther propr ie ta ry r ights by th i rd par t ies , and norepresen ta t ion o r war ran ty , expressed o r impl ied i s made in th i sregard . Any use o r re l i ance on th i s doucment sha l l cons t i tu tean accep tance hereof "as i s " and be sub jec t to th i s d i sc la imer . * /

/* Th is i s a work ing paper p repared fo r AEEC. I t does no t cons t i tu tea i r t r anspor t indus t ry o r ARINC approved po l icy , nor i s i t endorsedby the U .S . Federa l Government , any o f i t s agenc ies o r o the r s whomay have par t ic ipa ted in i t s p repara t ion . * /

D L P I _ i f

c-15



The following definitions are used:

Signal

DL_UNITDATA.req,DL_UNITDATA.ind,DL_ERROR.ind,

/* Wilmsbrg*//* -----*/

ACK, /*2.5.1.4 */ALO, /*2.5.19.1.1 */ALR, /*2.5.19.1.2 */BUSY, /*2.5.7.3 */CTS, /*2.5.7.1 */Data, /*2.5.11 */EOT, /*2.5.12 */NAK, /*2.5.13 */NCTS, /*2.5.7.2 */RTS, /*2.5.7 */SOT, /*2.5.10 */SYN, /*2.5.15 */

/*LOOP, 2.5.17.1 *//*SOLO, 2.5.17.2 *//*TEST, 2.5.17.2 *//*LCW */

Signalist p429_both = ALO<ALR/* LOOP,SOLO,TEST */;

Signalist p429_to_sink =RTS;

Signalist p429_to_source =ACK,BUSY,CTS,NAK,NCTS,SYN;



W C F

Note: the s ink_if is a receivebus, and typical ly for a s ingleWil l iamsburg func t ion there may bemult ip le s ink_ifs .

B l o c k L R U _ L y r _ 2 [ D L _ U N I T D A T A . i n d ] 1 (1)

Connect Phys ica l_429_i f and source_i f , s ink_i f ;Connec t DLPI_ i f and d_ i f ;Connec t m_i f and m_i f :

S igna l F ILE, LDU. req , LDU. ind ;

(1 ,1)

[ F I L E ] [ F I L E ]

wi l l i amsburg_i fa wi l l i amsburg_i fb

(1 ,1) (1 ,1)

Segmen t Reas semble

Sou rce_and_S ink

send_i f receive_if[LDU. ind]

[LDU. req ]

m _ i f

[ D L _ E R R O R . i n d . ]

(1 ,1)

A C K ,B U S Y ,C T S ,N A K ,N C T S ,S Y N(p429_bo th )

source_i f s ink_i f

R T S ,(p429_bo th )S O T , E O T ,D a t a

R T S ,(p429_bo th )S O T , E O T ,D a t a

A C K ,B U S Y ,C T S ,N A K ,N C T S ,S Y N(p429_bo th )

d_i f

[ D L _ U N I T D A T A . r e q ]



Process Reassemble 1(1 )

idle

L D U . i n d

' reassembleL D U s i n t o

a File '

F I L E

-



Proces s Segmen t 1 (1 )

idle

L D U . r e q

' segment theFi le in to

L D U s '

F I L E

-



c-15

c-15

c-15

/* * Bit-Oriented Protocol Events * Part 3, Table 10-1 */Synonym N1 in teger = 5 ; /*Number of RTS repeats f rom NCTS */Synonym N2 in teger = 20; /*Number of RTS repeats af ter BUSY */Synonym N3 integer = 5; /*Number of RTS repeats af ter no resp */Synonym N4 in teger = 3 ; /*Number of NAKs rcvd before NO COMM */Synonym N5 in teger = 3 ; /*Number of SYN before NO COMM */Synonym N6 integer = 3 ; /*Number of ALO af ter no response*//* * Selected Options * Table 10-3 * * Option 1 Half Duplex * Opt ion 2 Low Speed Bus Rate * Opt ion 3 Automat ic CTS when Ready = No * Opt ion 4 Accept Auto CTS = No * Option 5 System Prior i ty to resolve RTS Confl ic t = No * Opt ion 8 Use Solo Word = Yes * Opt ion 10 Des t Code in RTS/CTS/NCTS/BUSY used = Yes * Option 11 Bit-Oriented Protocol Vert i f icat ion = Yes */

/* * Variables for Low Speed Bit-Oriented Protocol Part 3, Table 10-4*/

/* Timer for Source */

Synonym t2 durat ion = 500; /* RTS repeat t ime af ter receipt of NCTS */Synonym t4 durat ion = 15000; /* RTS repeat t ime af ter receipt of BUSY */Synonym t5 durat ion = 500; /* RTS repeat t ime i f no response*/Synonym t12 durat ion = 200; /* ALO repeat t ime i f no response to ALO*/Synonym t16 dura t ion = 220; /* ACK/NAK Timeout a f te r EOT*/

/* Timer for Sink */

Synonym t9 durat ion = 2500; /* LDU t imeout fol lowing CTS */Synonym t14 durat ion = 120000; /* Incomplete Fi le Timeout *//* * Variables for High Speed Bit-Oriented Protocol * Part 3, Table 10-5*/

/* Timer for Source */

Synonym t2 durat ion = 100; /* RTS repeat t ime af ter receipt of NCTS */Synonym t4 durat ion = 1000; /* RTS repeat t ime af ter receipt of BUSY */Synonym t5 durat ion = 150; /* RTS repeat t ime i f no response*/Synonym t12 durat ion = 200; /* ALO repeat t ime i f no response to ALO*/Synonym t16 dura t ion = 220; /* ACK/NAK Timeout a f te r EOT*/

/* Timer for Sink */

/* Synonym t9 durat ion = 400 /* LDU t imeout fol lowing CTS *//* Synonym t14 durat ion = 10000' /* Incomplete Fi le Timeout */

P rocess Source_and_Sink 1 (12)

(1,1) ; This i s the power-ontransi t ion

System Inact iveState 0

2 .5 .192 .3

reset s tatevar iables2 .5 .19

2 .5 .19

A L Ovia source_if

se t (now+ t12 ,T 1 2 )

n1count := 0n2count := 0n3count := 0

n4count := 0n5count := 0n6count := 0

A L O _ i d l e

Dc :n1count ,n2count ,n3coun tn4count ,n5coun tn6count in teger ;

T i m e rT2 ,T4 ,T5 ,T9 ,T12 ,T14 ,T16 ;

/* This Source_and_Sink s ta temachine i s repl ica ted for eachSAL pair . This s ta temach ine a sumes tha t SALass ignments have occurred; i .e .- the s ta te machineonly makes use of the pre-de te rmined SAL pa i r .* /

2 .5 .192 .3

c-15



A L O

A L O _ I d l e

g o _a loha

A L Rvia source_i f rese t (T12)

recount := 0

ve r s ion__ m a t c h

(1,1) ;

P r o c e s s S o u r c e _ a n d _ S i n k 2(12 )

2 .5 .192 .5 .19 .12 .5 .19 .1 .1

2 .5 .19 2 .5 .19 .1

2 .5 .19 .1 .1

2 .5 .19 .1 .1

false

t rue

t ruefalse

L i n k __Id le

A L O _ I d l e

L i n k __Id le

2 .5 .19 .1

2 .5 .19 .1

2 .5 .19 .1false

t rue

else

< N 6

2 .5 .19 .1

2 .5 .12 .5 .19 .1

2 .5 .19 .1

Not success fu l . This should leadto the charac ter -or ientedpro toco l de te rmina t ion process ,i f appl icable , or a cycl icala t tempt to es tabl ish bi t -o r ien ted pro toco l . See At tachment 17 .2 .5 .19 , 2 .5 .19 .2

2 .5 .19

2 .5 .19 .1 .1

Synonym ve r s ion_match boo lean = t rue ;Synonym can_adap t boo lean = t rue ;Synonym t ry_di f fe ren t_vers ion boolean = t rue ;

A L R

rese t (T12)

L i n k __Id le

can_adap t

'adapt 'T 1 2

try__di f fe rent_

_ver s ionn6coun t :=

n6coun t + 1

n 6 c o u n t

A L Ovia source_i f

se t (now + t12 ,T 1 2 )

A L O _ I d l e

'not bi tor iented '

L i n k __Id le

A L Ovia source_i f

se t (now + t12 ,T 1 2 )

-

A L O _Idle

'not bi tor iented '

-



L D U . r e q

(1,1) ;Synonym va l id_and_ready boo lean = t rue ;Synonym a re_we_busy boo lean = fa l se ;Synonym messages_queued boo lean = f a l se ;

P roces s Sou rce_and_ S ink3 (12 )

Inva l id and N/Atrans i t ions no t shown

L i n k __Id le

L i n k __Id le

R T S go_r t s A L O

g o _ a l o h a

T 1 4

S Y Nvia s ink_if

'd iscard anypart ial f i lereceived '

2 .5 .14 .3

2 .5 .19 .1 .22 .5 .7 .22 .5 .7

Unles s Op t ion 3i s implemented2 .5 .7 .2

L i n k __Id le

N C T Svia s ink_if

falset rue

C T Svia s ink_if

2 .5 .13 .2

2 .5 .7 .12 .5 .7

se t (now + t9 ,T 9 )

W a i t __ S O T

va l id_and_ ready

-

B U S Yvia s ink_if

a r e _ w e __ busy

false

t rue

W a i t __ C T S

R T S v i asource_ i f

2 .5 .7

2 .5 .7 .4se t (now + t5 ,T 5 ) 2 .5 .14 .3rese t (T14)

2 .5 .7 .32 .5 .7

Unles s Op t ion 3i s implemented2 .5 .7 .3



(1,1);

Synonym va l id_CTS boo lean = t rue ;Synonym random_number du ra t ion = 1 ;D c :t6 durat ion;T i m e rT6 ;

Process Source_and_ S ink

W a i t __ C T S

R T S C T S

reset (T5)

2 .5 .7 .4

2 .5 .7 .1

2 .5 .7 .4

2 .5 .8 .1L D U . r e q2 .5 .7 .12 .5 .10 2 .5 .7 .4

2 .5 .7 .4

2 .5 .14 .3

2 .5 .8 .1

2 .5 .8 .1

n 3 c o u n t = 0

reset (T5)

rese t (T14)

t6 :=r a n d o m _n u m b e r

se t (now + t6 ,T 6 )

W a i t _ R T S __Conf l ic t

If Opt ion 5is used, onesys tem wi l lhave pr ior i ty2 . 5 . 8 . 1 N O T E :Usual ly up l inksare accordedpriori ty

v a l i d _ C T S

A L O

L D U . r e qto self

So message jus tde -queuedis not lost

go__a loha

go__ C T S

go__ N C T S

false

true

reset (T5)

2 .5 .12

n1count := 0 ,n2count := 0 ,n3count := 0

2 .5 .7 .1 , 2 .5 .7 .22 .5 .7 .3 , 2 .5 .7 .4

S O Tvia source_if

D a t avia source_if

E O Tvia source_if

2 .5 .10

2 .5 .16se t (now + t16 ,

T 1 6 )

W a i t __ A C K

4(12)

2 .5 .19 .1 .2



(1 ,1) ;


W a i t __ C T S

N C T S B U S Y

2.5 .7 .4

2 .5 .7 .4

rese t (T5)

n3coun t :=0

L i n k __Id le

g o __ N C T S

2.5 .7 .2

n1coun t :=n1coun t + 1

n 1 c o u n t

< N 2

se t (now + t2 , T2)

D L _ E R R O R . i n d

N C T S _ B u s y __ D e l a y

n1coun t :=0

rese t (T5)


n3coun t :=0

n 2 c o u n t

se t (now + t4 ,T 4 )

N C T S _ B u s y __ D e l a y

< N 1

2.5 .7 .3

B U S Y

rese t (T5)

2 .5 .7 .3

2 .5 .7 .4

2 .5 .7 .4


else

n2coun t :=0

L i n k __Id le

T 5 2 .5 .7 .4


n 3 c o u n t

< N 3else

2 .5 .7 .4

se t (now + t5 ,T 5 )


n3coun t :=0

L i n k __Id le

W a i t __ C T S

else

R T S v i asource_ i f



(1,1);

Process Source_and_ S ink6(12)

W a i t _ R T S __Confl ic t

R T S B U S Y

2.5 .14.3rese t (T14)

Wai t_S O T

'requeueuni tdatarequest '

A L O 2.5.19.1 .2

2.5 .19.1 .2

T 6 2.5 .8 .12.5 .8 .1

go__a loha

set (now + t5 ,T5 )

2.5 .7 .4

2.5 .8 .1C T Svia s ink_if

se t (now + t9 ,T9 )

2 .5 .13 .22.5 .13 .6

W a i t _ R T S __Confl ic t

L D U . r e q

R T Svia source_if

W a i t _ C T S

2.5.8 .1



(1 ,1) ;


N C T S _ B U S Y __ D e l a y

A L O C T SThis t rans i t ion val idonly i f Opt ion 4 i sset .

O the rwise CTS i signored .

2 .5 .7 .2 , 2 .5 .7 .3

L D U . r e q R T S

L D U . r e qto self

2 .5 .19 .1 .2g o _

_ R T S

g o __ C T S

g o __a loha

2 .5 .7

N C T S _ B U S Y __ D e l a y

T 2 2.5 .7 .2T 4

2 .5 .7 .4

2 .5 .7 .2R T Svia source_i f

se t (now + t5 ,T 5 )

W a i t __ C T S

W a i t __ C T S

R T Svia source_i f

se t (now + t5 ,T 5 )

2 .5 .7 .3

2 .5 .7 .4

2 .5 .7 .3



(1 ,1) ;

P roces s Sou rce_and_ S ink

W a i t __ A C K

A L O

2.5 .16

' requeue f i le2 .5 .19 .1 .2 '

F S N _ L S N __ m a t c h

A C K

2.5 .16g o __rts

2 .5 .16

W a i t __ C T S

8(12 )

S y n o n y m F S N _ L S N _ m a t c h b o o l e a n = t r u e ;

L D U . r e qto self rese t (T16)

g o __a loha

2 .5 .7 .4

L i n k __Id le

W a i t __ A C K

L D U . r e q R T S

se t (now +t5 ,T 5 )

R T Svia source_i f

W a i t __ C T S

2 .5 .16 2 .5 .7 .4

T 1 6S Y N N A K 2.5 .162 .5 .16

se t (now +t5 , T5)

2 .5 .16

rese t (T16)n5coun t :=n 5 c o u n t + 1

n4coun t :=0 2 .5 .16R T S

via source_i fn4coun t :=n 4 c o u n t + 1 2 .5 .16

n5coun t :=0 2 .5 .162 .5 .16

n 4 c o u n t

se t (now +t5 , T5)

2 .5 .7 .4

R T Svia source_i f

W a i t __ C T S

D L _E R R O R . i n d

2 .5 .16

n 5 c o u n t

D L _E R R O R . i n d

L i n k __Id le

else

< N 5

se t (now +t5 , T5)

2 .5 .7 .4

o f 1 s t LDU2.5 .16

W a i t __ C T S

2 .5 .16

R T Svia source_i f

e lse

< N 4

L i n k __Id le

2 .5 .16

t rue

false



(1,1);

Process Source_and_ S ink

W a i t __ S O T

A L O

2.5 .15L D U _ F S N __confus ion

S O T

go__rts

9(12)

Synonym LSN_FSN_confus ion boo lean = t rue ;

go__a loha

W a i t __ E O T

L D U . r e q R T S

W a i t __ S O T

DataE O T T 9 2.5 .13 .22.5 .13 .1 2.5 .13 .2

2.5 .14 .3

2 .5 .15unexpec ted FSN

2.5 .19.1 .22.5 .9

2 .5 .10 .22.5 .10 .3

false

true

'discardpartial File '

2 .5 .15

rese t (T14)

S Y Nvia s ink_if

L i n k __Idle

N A Kvia s ink_if

L i n k __Idle

2 .5 .13 .2



(1 ,1) ;

P roces s Sou rce_and_ S ink

W a i t __ E O T

A L O 2.5 .13 .2T 9

g o __ R T S

1 0 ( 1 2 )

Synonym va l id_EOT boo lean = t rue ;

g o __a loha

L D U . r e q R T S

2.5 .13 .6

2 .5 .14 .3

2 .5 .9

2 .5 .19 .1 .2

L i n k __Id le

S Y N

'discardpar t ia l LDU'

'd iscardpart ial Fi le '

rese t (T14)

2 .5 .13 .22 .5 .3 .16

N A Kvia s ink_if

'd iscardpart ial Fi le '

se t (now+ t14 ,T 1 4 )

'd iscard anypar t ia l LDU'

2 .5 .13 .2 rese t (T14)

L i n k __Id le

2 .5 .14 .3



(1 ,1) ;

P roces s Sou rce_and_ S ink1 1 ( 1 2 )

t rue

W a i t __ E O T

E O T2.5 .13 .3

'd iscard anypar t ia l LDU'

is a lso thewai t for data s ta te

D a t a 2 .5 .14 .3N A K

via s ink_if2 .5 .13 .42 .5 .13 .5

odd_par i tycor rec t__ w o r d __ c o u n t

false

L D U __ C R C __ c o u n t

f i na l_ LDU

rese t (T14)

2 .5 .14 .3

t rue

false

L i n k __Id le

discuss ; notdesc r ibed

-

' s tore dataword '

2 .5 .14 .3

-

nex t_o r__dupl ica te

t rue' ignore2 .5 .13 .3 '

t rue

t rue

false

false

falsef i rs t_of__new f i le

2 .5 .142 .5 .14 .12 .5 .14 .2

A C Kvia s ink_if

d iscuss ; notdesc r ibed f i n a l _ L D U

true

false

se t (now + t14 ,T 1 4 )

rese t (T14)

'd iscard anypartial f i le '

r ese t (T14)

dupl ica tet rue

false

' d i sca rd LDU2.5 .14 .1 '

S e n d L D U s i g n a lto upper layers

-

L D U . i n d

se t (now+ t14 ,T 1 4 )

L i n k __Id le

L i n k __Id le

'd iscard anypartial f i le '

r ese t (T14)

2 .5 .14 .3

2 .5 .14 .2

2 .5 .14

2 .5 .14 .3

2 .5 .15

S Y Nvia s ink_if

L i n k __Id le

Synonym odd_par i ty boo lean = t rue ;Synonym cor rec t_word_coun t boo lean = t rue ;S y n o n y m L D U _ C R C _ c o r r e c t b o o l e a n = t r u e ;Synonym nex t_or_dup l i ca te boo lean = t rue ;Synonym dup l i ca te boo lean = t rue ;Synonym f i r s t_of new_f i le = t rue ;Synonym f ina l_LDU boo lean = t rue ;

false

2 .5 .14

2 .5 .6 .3

t rue



-

P r o c e s s W C F 1(1)

idle

F I L E

D L _U N I T D A T A .

req

D L _U N I T D A T A .

req

F I L E _via

wi l l i amsburg_ifa

-

AR

INC

SPE

CIF

ICA

TIO

N 429 P

AR

T 3 - P

age 90

AP

PE

ND

IX J

PR

OT

OC

OL

STR

UC

TU

RE

Figure J1-1 AR

INC

429 William

sburg Version 3 P

rotocol Layer D

iagram

Data LinkLayer

PhysicalLayer

Protocol Layers

ARINC 429 Command Frame

I PCLNP

LLC

CLTP/TP4

ARINC 429 Physical Layer (Part 1)

Mgt MIB

Mgt MIB

Mgt MIB

Mgt MIB

Transport Layer

NetworkLayer

ATN 1

ARINC 429 Williamsburg Version 3 MAC Protocol (Part 3)

ARINC 429 Information Frame

(ITU.TX.25/

ISO 8208)

CMU/VDRVDL Mode 2 Interface

MAC Control

Mgt Entity

SubnetworkSublayer

LLCSublayer

MACSublayer

TCP/UDP

Data Loader

TypeLength

MAC Control

ARINC 429Information

Frames

ARINC 429Command

Frames

c-17


APPENDIX JPROTOCOL STRUCTURE

Physical Layer - The physical layer is a high speed ARINC 429 data bus.

Link Layer – It is responsible for the exchange of data between points (nodes) connected to one network. One networkcan be constructed either by a bus (A429, A629) or by a set of buses and point-to-point links that can be interconnectedby bridges (A646).

MAC Sublayer – The scope of this document is the “lower” part of the Link Layer. The ARINC 429 (Williamsburg)Version 3 protocol specifies the functionality of the MAC Service Provider that provides two types of MAC Frames, abridgeable Information frame based upon the frame structure specified in IEEE 802.3 (Ethernet) and a non-bridgeableCommand frame for point-to-point transfers of data of any kind, e.g. link management information.

LLC Sublayer – One potential MAC Service Client is the Logical Link Control Sublayer, which may be used to providea logical interface between LLC entities. All IEEE 802 specifications share the notion of this “upper” portion of the LinkLayer, which enables it to provide a common set of services. It may be used to provide a logical interface between peerentities. Three classes of service have been defined which can be connectionless-unacknowledged, connectionless-acknowledged or connection-oriented.

Network Layer – Other potential MAC Service Clients are either Internet (summarized by TCP/IP), specific (e.g. VDLMode 2) or further standardized or non-standardized protocols. The Network layer provides a home for specifications ofprotocols that support the communication across network boundaries. In the example shown, these are, e.g., IP or CLNP.

Subnetwork Sublayer – In the scope of this document this sublayer is defined as an X.25 subset (profile). It may berequired to provide services to the Network Layer, and interfaces with the LLC Sublayer. In the ISO network definition,these are the Subnetwork Access Protocols (SNAP) and provide services to the Subnetwork Independent ConvergenceProtocol (SNICP) and the Subnetwork Dependent Convergence Protocol (SNDCP). These services include flow control,error recovery and segmentation/reassembly.

It should be noted, however, that there is another (totally separate) SNAP definition by IEEE that resides on top of LLCClass 1 (connectionless-unacknowledged service) and acts as a Link layer client multiplexer similar to the 802.3 TYPEinterpretation.

Transport Layer – This layer provides services for the exchange of information between communication applications,such as the Trivial File Transfer Protocol (TFTP) in the Internet suite of protocols which in this example is used by theData Loader application or Simple Network Management Protocol (SNMP) for network management.

Typical ApplicationsThis section focuses on the scope of this document, the various characteristics of the ARINC 429 Version 3specification.

A429 Information Frame – As specified in section 3.3.1 this frame provides for a bridgeable frame format that is used byvarious applications. In this example, Data Loader (via TCP/IP stack) or ATN 1 (via OSI stack) could take advantage ofthis format.

A429 Command Frame – As specified in section 3.3.2 this frame provides for a non-bridgeable point-to-point frameformat that may be used by the CMU/VDR VDL Mode 2 Interface.

ÍEEE 802.3 – IEEE used to assume that LLC resides above any of the 802.n (with n bigger than 2) specifications. IEEE802.3 has always been in “competition” with the Ethernet specification, developed by Xerox, Digital and Intel. However,Xerox has shifted authority about the Ethernet specification to IEEE, which incorporated it into the current (1998)edition of the 802.3 specification. The main difference between the two specifications was the interpretation of a fieldthat is now called “LENGTH/TYPE”.

802.3-LENGTH – The “LENGTH” interpretation assumes that LLC is the MAC Service Client. If the value in this fieldis less than or equal to 1500 decimal, a “LENGTH” interpretation is specified.

c-17


APPENDIX JPROTOCOL STRUCTURE

802.3-TYPE – The “TYPE” interpretation assumes that a different protocol is the MAC Service Client. If the value inthis field is bigger than or equal to 1536 decimal, the value specifies the respective protocol. Assignments aredocumented in an Internet Request for Comment (RFC).

MAC Control – This functionality has been introduced recently and currently provides for a PAUSE function only. Itenables temporary suppression of any data transmission when sent to the peer MAC entity (reverse MAC Controlcommands can still be returned, though). Both types of frames, Information and Command, support this function indifferent ways.

Network Management – Each layer of the communication stack is required to maintain a Management Information Base(MIB) which consists of parameters and behavioral characteristics of that layer and may be retrieved by the NetworkManagement entity. The contents of the respective MIB are specified in the related protocol layer specification whereasthe MIB structure as well as the Network Management Protocol and functionality is specified in a separate specification.

c-17


APPENDIX KGLOSSARY & ACRONYMS

ACK AcknowledgeADS Automatic Dependent SurveillanceAIDS Airborne Integrated Data SystemALR ALOHA ResponseBOP Bit-Oriented ProtocolBSAL Bridge System Address LabelCRC Cyclic Redundancy CheckCT Command TypeCTS Clear to SendDITS Mark 33 Digital Information Transfer SystemEOF End of FieldEOT End of TransmissionFDU Frame Data UnitGFI General Format IdentifierI/C Information/CommandIEEE Institute of Electrical and Electronics EngineersIP Internet ProtocolISO International Standard OrganizationLAN Local Area NetworkLDU Link Data UnitsLLC Logical Link ControlLOOP Loop Test ResponseLRU Line Replaceable UnitsLSB Least Significant BitMAC Media Access ControlMSAL Multicast System Address LabelMSB Most Significant BitMU Management UnitNCTS Not Clear to SendOSI Open Systems InterconnectRTS Request to SendSAI Systems Architecture and Interfaces SubcommitteeSAL System Address LabelsSOF Start of FieldSOT Start of TransmissionTEST Loop Test Pattern WordVDL VHF Data Link



SUPPLEMENT 12

TO







SUPPLEMENT 12 TO ARINC SPECIFICATION 429 PART 3 – Page 2


This Supplement introduces the Williamsburg bit-orientedfile data transfer protocol which supports the transfer ofbinary and character data. The previous AIM andcharacter-oriented file data transfer protocol sections aremoved to Appendix 6. The Sign Status Matrix (SSM)information is revised and reorganized. In addition, thisSupplement introduces new label assignments andequipment identification codes.


The first part of this document, printed on goldenrodpaper contains descriptions of changes introduced intothis Specification by this Supplement and whereappropriate extracts from the original text for comparisonpurposes. The second part consists of replacement whitepages for the Specification, modified to reflect thesechanges. The modified and added material on eachreplacement page is identified with “c-12” symbols in themargins. Existing copies of ARINC Specification 429may be updated by simply inserting the replacementwhite pages they replace. The goldenrod pages areinserted inside the rear cover of the Specification.

Copies of the Specification bearing the number 429-12already contain this Supplement and thus do not requirerevision by the reader.


This section presents a complete tabulation of the changesand additions to the Specification introduced by thisSupplement. Each change or addition is entitled by thesection number and the title currently employed in theSpecification or by the section name and title that will beemployed when the Supplement is eventuallyincorporated. In each case there is included a briefdescription of the addition or change and, for other thanvery minor revision, any text originally contained in theSpecification is reproduced for reference.


This section contains editorial corrections to comply withchanges introduced in Supplement 11.


This section was revised and reorganized. The changesinclude moving the AIM and file transfer SSM definitionsto Appendix 6, adding failure reporting to the discreteword truth table (Section 2.1.5.3) and moving thedescription of status priorities to Section 2.1.5.


The contents of Sections 2.3.1.4 through 2.3.1.5.7 weremoved to Appendix 6. The AIM Data and File Datatransfer section headings were retained for referencepurposes. Section 2.3.1.5, File Data Transfer, provides thereason for moving the original file transfer protocol andintroduces the Williamsburg protocol.


This new section was added to describe a bit-oriented datatransfer protocol. The new protocol was developed toaccommodate the interface of the ACARS ManagementUnit (MU) and the Satellite Data Unit (SDU).


The information previously contained in this section is nolonger applicable to ARINC Specification 429. Forreference purposes, the section header is retained and theoriginal contents of this section are located in Appendix6.



002 115 013 0B8 016 0B8 046 10A 046 10B 047 10A

047 10B 107 0BB 110 0BB 112 0BB 114 0BB 114 10A

114 10B 127 10A 127 10B 130 035 130 10A 130 10B

131 035 132 035 133 10A 133 10B 134 10A 134 10B

137 10A 137 10B 155 10A 155 10B 156 10A 156 10B

157 10A 157 10B 160 10A 160 10B 161 10A 161 10B

201 115 203 035 203 10A 203 10B 205 10A 205 10B

211 10A 211 10B 220 116 221 116 222 115 222 116

223 116 224 116 226 035 230 116 234 039 234 040

235 039 235 040 236 039 236 040 237 039 237 040

244 10A 244 10B 256 114 257 114 260 10A 260 10B

260 114 261 10A 261 10B 261 114 262 10A 262 10B

262 114 263 10A 263 10B 263 114 264 10A 264 10B

264 114 265 004 265 038 265 10A 265 10B 265 114

267 10A 267 10B 270 10A 270 10B 270 114 270 115

271 10A 271 10B 271 114 272 002 272 10A 272 10B

272 114 273 10A 273 10B 273 114 274 10A 274 10B

274 114 275 10A 275 10B 275 114 276 114 277 018

300 10A 300 10B 300 TBD 301 10A 301 10B 302 10A

302 10B 303 10A 303 10B 304 10A 304 10B 305 10A

305 10B 306 10D 310 114 311 114 312 114 313 114

316 10A 316 10B 320 035 321 10A 321 10B 322 10A

322 10B 323 10A 323 10B 324 10A 324 10B 325 10A

325 10B 326 10A 326 10B 327 10A 327 10B 330 10A

330 10B 331 10A 331 10B 335 10A 335 10B 336 002

336 10A 336 10B 337 002 337 002 337 10A 337 10B

341 10A 341 10B 342 10A 342 10B 343 10A 343 10B

344 10A 344 10B 345 10A 345 10B 346 10A 346 10B

347 10A 347 10B 350 10A 350 10B 350 114 350 115

351 10A 351 10B 351 114 352 10A 352 10B 352 114

353 10A 353 10B 353 114 354 10A 354 10B 357 035

360 10A 360 10B 360 TBD 361 10A 361 10B 362 10B

362 10B 362 115 363 10A 363 10B 365 TBD 372 10A

372 10B 373 10A 373 10B 374 10A 374 10B 374 TBD

375 10A 375 10B 375 TBD

Revised label 130 035 from “Traffic Advisory Range” to“Intruder Range”.

Revised label 131 035 from “Traffic Advisory Altitude”to “Intruder Altitude”.

Revised label 132 035 from “Traffic Advisory Bearing”to “Intruder Bearing”.

Removed label 130 030 Traffic Advisory Range.

Removed label 131 030 Traffic Advisory Altitude.


Removed label 132 030 Traffic Advisory BearingEstimate.

Removed label 270 030 Transponder Discrete.

Removed label 347 030 Sector Control.

Removed 347 035 Antenna Control.



113, 114, 115, 116, 117, 118, 119, 11A, 123, 124, 125,126, 127, 128, 129, 15A, 15B, 15C, 15D, 15E, 16A, 16B,16C, 16D, 16E, 17A, 17B, 17C, 18A, 18B, 18C, 18D,18E, 18F.


Tables 1, 2 updated to reflect changes to Attachment 1.

Binary Data notes 6, 7 and 8 added.

Discrete Data Standards entered for new labels:

272 002 271 018 272 018 273 018 275 018 276 018

277 018 274 018 270 035 271 035 273 035 274 035

275 035 013 0B8 016 0B8 161 10A 161 10B 350 114

351 114 352 114 353 114 270 115 350 115


Add format for TCAS Intruder Range label 130.

Add format for TCAS Intruder Altitude label 131.

Add format for TCAS Intruder Bearing label 132.

Add format for Transponder Altitude/TCAS Own A/CAltitude label 203.

Removed 730 ASAS Sector Control Word example.

Removed 730 TCAS Traffic Advisory Range Wordexample.

Removed 730 TCAS Traffic Advisory Bearing EstimateWord example.

ATTACHMENT 9B – GENERAL AVIATION WORDEXAMPLES

Add new Company Name Identifier.

ATTACHMENT 10 – VARIABLES OF BIT-ORIENTED PROTOCOL

Add new Attachment.

ATTTACHMENT 11 – BIT-ORIENTED DATA FILETRANSFER WORD FORMATS

Add new Attachment.


Add new Attachment.


Add new Attachment.

ATTACHMENT 11C - ALOHA/ALOHA RESPONSEPROTOCOL WORDS

Add new Attachment.

ATTACHMENT 12 - FILE TRANSFER EXAMPLE

Add new Attachment.

ATTACHMENT 12A - FIELD MAPPING EXAMPLE

Add new Attachment.

ATTACHMENT 13 - PROTOCOL DETERMINATIONPROCEDURE DIAGRAMS

Add new Attachment.

ATTACHMENT 14 – SYSTEM ADDRESS LABELS

Add new Attachment.

ATTACHMENT 15 - LINK LAYER CRD DATAEXAMPLE

Add new Attachment.

APPENDIX 6 - FORMER MAINTENANCE, AIM ANDFILE TRANSFER TECHNIQUES

Add new Appendix.

APPENDIX 7 – MATHEMATICAL EXAMPLE OFCRC ENCODING/DECODING

Add new Appendix.



SUPPLEMENT 13

TO








This Supplement introduces changes made to theWilliamsburg protocol as a result of its initialimplementation. This protocol supports the transfer ofbinary and character data. In addition, this Supplementintroduces new label assignments and equipmentidentification codes.


The first part of this document, printed on goldenrodpaper contains descriptions of changes introduced intothis Specification by this Supplement. The second partconsists of replacement white pages for the Specification,modified to reflect the changes. The modified and addedmaterial on each page is identified by a c-13 in themargins. Existing copies of ARINC Specification 429may be updated by simply inserting the replacementwhite pages where necessary and destroying the pagesthey replace. The goldenrod pages are inserted inside therear cover of the Specification.


This section presents a complete tabulation of the changesand additions to the Specification introduced by thisSupplement. Each change or addition is defined by thesection number and the title currently employed in theSpecification or by the section name and title that will beemployed when the Supplement is eventuallyincorporated. In each case a brief description of thechange or addition is included.


An editorial change, correction to section numbering.


New Section added to describe ALO/ALR protocolprocess to be used when a bilingual Link Layer protocolsystem needs to determine necessary bit-orientedinterfaces.

2.5 Bit-Oriented communications Protocol

Included term “Williamsburg” parenthetically since thisterminology well-known in industry. Added commentaryto explain non-negotiation or parameters in this protocol.

D. Corrected Network Layer definition.


Added second paragraph to text, since it is a requirement,and removed second paragraph from commentary.


Corrected the commentary to change the more ambiguousterm “message” to LDU.


An editorial change was made.

2.5.6 Response to RTS

The last sentence in the second paragraph was rewordedand moved to a more appropriate section, 2.5.6.2.


In the second to last sentence, the word “valid” was addedto clarify the Not clear to send condition. The lastsentence was added to clarify the resetting of RTScounters.


The first paragraph was updated to include theinformation deleted from Section 2.5.6 and to clarify thevalidity requirements. The second paragraph was updatedto describe that and NCTS counter would be reset upon avalid CTS response. The last sentence in the thirdparagraph was deleted and it’s content expanded in thefollowing commentary of that section.


The second paragraph of this section was updated toindicate that a BUSY counter should be reset with a validCTS response to RTS.

2.5.7 No Response to RTS

The first paragraph of this section was updated to describeproper response to RTS.


This section was updated to include editorial changes anda description of the correct responses to RTS. The lastsentence was deleted as redundant to Section in 2.5.13.1and in conflict with other possible responses.

2.5.11 Data

The fourth paragraph of this section was updated todescribe the proper ending of an LDU transmission, andto include the optional NAK response for receipt of anincomplete octet.


In the last paragraph, the “note” designator was removedand the text clarified for the transfer of characters with aparity bit.


This section was updated to clarify conditions for sendingthe NAK word.



2.5.13.1 Missing SOT word

Text was corrected to refer to “reception” instead of“transmission” of a valid SOT word. Also, incorrect textreferring to the NAK response timing was deleted.

2.5.13.2 LDU Sequence Number Error

The original text was omitted. Sections 2.5.13.1 –2.5.13.7 were renumbered.


A commentary section was added to describe theprocedures for receiving words with bad parity.


This section was updated to clarify the NAK responsetime for word count errors.

2.5.13.5 CRC Errors

This section was updated to clarify the NAK responsetime for CRC errors.



2.5.13.7 Restart Initialization

This section was omitted due to potential conflicts withthe ALO/ALR procedures.

2.5.14 LDU Transfer Acknowledgement (ACK)

Text was revised to include LDU conditions for sinkacknowledgement transmission.


This section was added to describe duplicate LDUoccurrences.


This section was added to describe the method ofhandling auto-synchronized files.

2.5.15 SYN Word

New text was added to describe SYN response times fornon-consecutive LDU Sequence numbers. The lastparagraph was incorrect and deleted.


New text was added to describe actions when NAK andSYN are detected during a transmission.

2.5.19 ALO Response

A new section was added and updated to describe ALOresponses.


Tables 10-1 and 10-3 were updated to include events N5,N6, and time T12. Options 07 and 012 in Table 10-4 werechanged to spares for consistency with corresponding textupdates.


Table 11C-3 was added to clarify protocol versionnumber assignments, and is referenced by “note 1”.“Note 2” was added to describe the GFI field of theALOHA word.

ATTACHMENT 12A – FIELD MAPPING EXAMPLE

Bk was changed to B24 in the data word map, “nibble” waschanged to “semi-octet”, and semi-octet arrow lengthswere shortened to correspond to the proper four and eight-bit lengths.

APPENDIX 7 – MATHEMATICAL EXAMPLE OFCRC ENDODING/DECODING

Format (alignment) changes were made in the polynomialdivisions, “(X)” was corrected to “Q(x)”, and thetransmission order for the LDU Mapping of the 24-bitexample was deleted to avoid possible misinterpretation.



SUPPLEMENT 14

TO








This Supplement introduces changes made to increase theefficiency of data transfer across an ARINC 429 highspeed bit-oriented link. This protocol supports thetransfer of binary and character data.


The first part of this document, printed on goldenrodpaper, contains descriptions of changes introduced intothis Specification by this Supplement. The second partconsists of replacement white pages for the Specification,modified to reflect the changes. The modified and addedmaterial on each page is identified by a c-14 in themargins. Existing copies of ARINC 429 may be updatedby simply inserting the replacement white pages wherenecessary and destroying the pages they replace. Thegoldenrod pages are inserted inside the rear cover of theSpecification.


This section presents a complete tabulation of the changesand additions to the Specification introduced by thisSupplement. Each change and addition is defined by thesection number and the title currently employed in theSpecification or by the section name and title that will beemployed when the Supplement is eventuallyincorporated. In each case a brief description of thechange or addition is included.


An editorial change was needed to reference new section.


This section was expanded to include determination ofdifferent version numbers of the bit-oriented protocol, andwas moved to Section 2.5.19.

2.5 Bit-Oriented Communication Protocol

An editorial change references a new section number.


A maximum word gap of 64 bit-times, (averaged over theLDU transmission) was added to eliminate excessivedelay in source transmission time.

Note: Sections 2.5.5 through 2.7 have been renumberedand reordered for consistency.

2.5.5 Word type

The basic definition of “word type” was corrected toinclude bits 31-29 in all bit-oriented words of an LDU.


This section was added to specifically define the wordtype for protocol words.


This section was added to clarify the definition of bits 28-25 for protocol words and to specify the relevant additionfor error conditions.


This section was updated, and a commentary added, toclarify the role of the link layer protocol for upwardcompatibility with changing network functionality. Therequirement for Destination code validation is not a linklayer function.

2.5.6.3 Word Count


2.5.7 Request to Send (RTS)

This section was previously titled “Response to TS”, andhas been renumbered. The title was changed forconsistency, and an introductory paragraph added toclarify the basic RTS function.






This section was renumbered, and an introductoryreplacement paragraph inserted to clarify the “optional”BUSY response, which may be used when a systemcannot accept a transmission by the source in a “timelymanner”. New commentary equates a “timely manner” tothe shorter retry sequence of the NCTS series.


This section was renumbered, and the ALOHA word wasincluded in the logic for error determination.

2.5.10 Start of Transmission (SOT)

Timer T13 was added as a requirement on the source tobegin transmission of an LDU within a specified intervalafter receipt of the CTS word from the sink.


This section was updated, and commentary added toclarify the role of the GFI in pre-OSI as well as OSIenvironments. Validation of the GFI code is required bya high level entity (network layer) in both environmentsto determine the format of the data words to follow. GFIvalidation is not necessarily a link layer function.



2.5.11 Data

All references to Character Data word formats weredeleted.


This section was deleted. The Character Data Wordformat was removed from Supplement 14, as the format isincompatible with those for Full and Partial Data wordformats. Currently, both binary and character data aretransmitted in octets defined by the other two data wordformats. The special character data format is notrequired.


References to character data words were deleted. Thetext for equation: M9x) = x16G(x) + R(x) was correctedby moving the “bar” from G(x) to R(x).


NAK word interpretation was changed to removeconstraint on source for specific order of file sequencing(i.e. Allows source to restart file with new FSN ifnecessary).


This first paragraph was rewritten to clarify.


This section was added to allow the sink to discard apartial file of multiple LDUs when the T14 timeoutbetween LDU transmissions is exceeded. It ensures that asource device cannot “lock-up” a sink.

2.5.15 SYN Word

The LDU sequence anomalies which generate a SYNresponse by the sink were clarified.


The T16 timer was introduced to replace T10 and T8. Also,the action taken by the source upon receipt of a SYNword was updated, which relaxes requirements tomaintain a specific File Sequence ordering by the source.


2.5.19.1 Bit-Oriented Protocol Version,

2.5.19.2 ALOHA Response, and

2.5.19.3 Character-429 Determination

This section has been added to replace and expand on thedefinition of the process to determine the link layerprotocol version supported by an interfacing system.These sections replace three sections from Supplement13.


2.5.19 ALO Response, and

2.5.20 Bit Protocol Verification

2.6 Windowed Bit-Oriented Protocol

This is a completely new section which contains thesystem description of the new LLC2-like bit-oriented linklayer protocol for 429. It is based on Section 2.5, “Bit-Oriented Communications Protocol”, with expanded textas specified to allow for more efficient use of the 429high (or low) speed data bus through “windowing”. Thedefinition includes provision for a Link Control Wordprior to each LDU.


New Equipment Code Identifiers were added.

ATTACHEMENT 6 – WORD FORMATS ANDENCODING EXAMPLES

Example added for label 171.


Table 10-1 was updated to include a standard value forN7, the maximum number of LDUs in a window (seeSection 2.6 “Windowed Bit-Oriented Protocol”).

Table 10-3 deleted Option 6 (O6) for NAK Send Time,and deleted Option 9 (O9) for the Character Data Word,both of which are no longer used.

Table 10-4 was revised to include columns for low speedmaximum and minimum values. These values wereestablished for timers and as response time design goalsfor incoming transmissions. Timers T13 through T16 wereadded.

Table 10-5 was added to include a definition of highspeed maximum and minimum values for timers andresponse time design goals. The format is the same as therevised Table 10-4. Timer T10 is not used in the highspeed protocol.

Table 10-6 was added to include notes to Tables 10-1through 10-5.


Table 11-1A added “spares” for the deleted CharacterData Formats and corrected “Protocol Data Word” to read“Protocol Word”.

Table 11-4 updated definitions for bits 9 through 24 of theALO and ALR words, and added the LCW (LDU ControlWord) format definition.

Table 11-4A was added as a partial replacement forATTACHMENT 11C and Table 11-4B was added todefine the new window definitions for the Windowed Bit-Oriented protocol in Section 2.6.

Table 11-6A was revised, changing the former GFI bitpattern (0001) for ISO 8208 to “unassigned”. The bitpattern (0100) for ISO 8473 was changed to a more


ATTACHMENT 11 – BIT-ORIENTED DATA FILETRANSFER WORD FORMATS (cont’d)

generic ISO 9577 definition. The bit pattern 1110(hex”E”) is now defined as “ACARS VHF Format”.The“NOTES” in ATTACHMENT 11 have been renumberedto correspond to the new table definitions.


This Attachment has been deleted. This information hasbeen moved to Tables 11-4, 11-4A, and 11-4B.

ATTACHMENT 13A – ALOHA VERSIONDETERMINATION SEQUENCE

This Attachment was added to support the ALOHAversion determination sequence called out in Section2.5.19.1.1.

ATTACHMENT 14 – SYSTEM ADDERESS LABELS

New System Address Labels (SAL) were added.

ATTACHMENT 16 – SEQUENCE OF PROTOCOLAND DATA WORDS IN WINDOW TRANSFER

This Attachment was added to illustrate the windowtransfers for new Section 2.6.

ATTACHMENT 17 – FLOW DIAGRAM USED TODETERMINE CHARACTER-ORIENTED VS BIT-ORIENTED PROTOCOL

This Attachment was added to illustrate the logic flowthat determines whether a character-oriented or bit-oriented link layer protocol interface is to be used.



SUPPLEMENT 15

TO



PART 3


Published: August 31, 1995





This portion of Supplement 15 provides corrections andadditions to the file transfer provisions of ARINCSpecification 429. The reader should note that theorganization of ARINC 429 has been described in SectionB below.

Appendix C was added to assist designers in establishingconnectivity between LRUs designed to different versionsof Specification 429. Appendix D comprises theSpecification and Description Language (SDL) diagramsthat reflect the intent of the textual material. The SDLdiagrams have not been fully proofed, and remainadvisory in nature. Therefore, the text material hasprecedence over the SDL diagrams. When the SDLdiagrams have been validated, they will be moved to anAttachment.


The portion of this document, printed on goldenrod paper,contains descriptions of changes introduced into thisSpecification by this Supplement. In the text, printed onwhite paper, the modified and added material on eachpage is identified by a c-15 in the margins. In view of thedocument reorganization, existing copies of ARINC 429cannot be updated.

This Supplement is the first in which ARINCSpecification 429 is divided into three parts. This part,Part 3, contains the definition of the protocols used forfile data transfer. Typically, file data transfer is non-periodic in nature.

The fundamental physical layer descriptions of the wire,voltage levels and coding of data are contained in Part 1.Part 1 also contains the listing of data word labelsassigned for the transmission of broadcast periodic data.

Part 2 contains a tabulation of the ever-increasing list ofDiscrete data words used to provide status information.


This section presents a complete tabulation of the changesand additions to the Specification introduced by thisSupplement. Each change and addition is defined by thesection number and the title currently employed in theSpecification or by the section name and title that will beemployed when the Supplement is eventuallyincorporated. In each case, a brief description of thechange or addition is included. A tabulation of sections isincluded with this supplement to enable the reader tocorrelate the previous section assignments with the newPart 3 Supplement 15 section number assignments.

The following changes affect only ARINC Specification429-15, Part 3, File Data Transfer Techniques. Refer toParts 1 and 2 for changes impacting the broadcastprovisions of ARINC Specification 429.


Revised Notes 1 and 4.

Table 10-3 BIT-ORIENTED PROTOCOL OPTIONS -Added Option 012.

Table 10-5 VARIABLES OF HIGH SPEED BIT-ORIENTED PROTOCOL - Revised Time T10 min andmax values.

ATTACHMENT 11 - BIT-ORIENTED DATA FILETRANSFER WORD FORMATS

Table 11-6A GENERAL FORMAT IDENTIFIER (GFI) -Revised “Reserved ISO 9577” to “ISO 9577”


Added Cabin Packet Data Function. Corrected GroundStation bit encoding.


Revised description of Code 86. Added entries for Code8E through 95.


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 #1344 HF Data Radio/Data Unit #2

The following labels were revised:175 HGA HPA176 Spare177 LGA HPA


Appendix added.

APPENDIX 9 - SDL DIAGRAMS OF THEWILLIAMSBURG PROTOCOL

Appendix added.


ARINC Specification 429 is now available in three separate parts: Part 1 “Functional Description and Word Formats”,Part 2 “Digital Information Transfer System Standards” and Part 3 “File Data Transfer Techniques.” The changes aredescribed in Supplements printed on goldenrod colored paper. The following pages provided a record of the sectionnumbering of the text now included in Part 3.

Old Number(Supp 14)

New Number(Supp 15) Section Title

1.1 1.1 Purpose of this Document1.2 1.2 Relationship to ARINC Specification 419 changed to 429

1.3 1.3 “Mark 33 Digital Information Transfer System”_ - Basic Philosophychanged to: “File Data Transfer Techniques”

1.3.1 1.3.1 Number Data Transfer changed to: Data Transfer1.3.2 1.3.2 ISO Alphabet No. 4 Data Transfer changed to: Broadcast Data1.3.3 1.3.3 Graphic Data Transfer2.3.1.5 2.1 File Data Transfer2.3.1.5.1 2.3 Bit-Oriented Protocol Determination2.3.2 2.2 Transmission Order

2.5 Chapter 3.0 Bit-Oriented Communications Protocol changed to:Bit Oriented File Transfer Protocol

2.5 3.1 Bit-Oriented File Transfer Protocol2.5.1 3.2 Link Data Units (LDU)2.5.2 3.3 Link Data Unit (LDU) Size and Word Count2.5.3 3.4 System Address Labels (SAL)2.5.4 3.5 Bit Rate and Word Timing2.5.5 3.6 Word Type2.5.6 3.7 Protocol Words2.5.6.1 3.7.1 Protocol Identifier2.5.6.2 3.7.2 Destination Code2.5.6.3 3.7.3 Word Count2.5.7 3.8 Request To Send (RTS)2.5.7.1 3.8.1 Clear To Send (CTS)2.5.7.2 3.8.2 Not Clear To Send (NCTS)2.5.7.3 3.8.3 Destination Busy (BUSY)2.5.7.4 3.8.4 No Response to RTS2.5.8 3.9 Conflicting RTS Transmissions2.5.8.1 3.9.1 Half Duplex Mode2.5.8.2 3.9.2 Full Duplex Mode2.5.9 3.10 Unexpected RTS2.5.10 3.11 Start of Transmission (SOT)


Old Number(Supp 14)


2.5.10.1 3.11.1 General Format Identifier (GFI)2.5.10.2 3.11.2 File Sequence Number2.5.10.3 3.11.2 LDU Sequence Number2.5.11 3.12 Data2.5.11.1 3.12.1 Full Data Word(s)2.5.11.2 3.12.2 Partial Data Word(s)2.5.12 3.13 End of Transmission (EOT)2.5.12.1 3.13.1 CRC Encoding2.5.12.2 3.13.2 CRC Decoding2.5.13 3.14 Negative Acknowledgement (NAK)2.5.13.1 3.14.1 Missing SOT Word2.5.13.2 3.14.2 Missing EOT Word2.5.13.3 3.14.3 Parity Errors2.5.13.4 3.14.4 Word Count Errors2.5.13.5 3.14.5 CRC Errors2.5.13.6 3.14.6 Time Out Errors2.5.14 3.15 LDU Transfer Acknowledgement (ACK)2.5.14.1 3.15.1 Duplicate LDU2.5.14.2 3.15.2 Auto-Synchronized Files2.5.14.3 3.15.3 Incomplete File Time2.5.15 3.16 SYN Word2.5.16 3.17 Response to ACK/NAK/SN2.5.17 3.18 Solo Word2.5.17.1 3.18.1 Test Word and Loop Word2.5.17.2 3.18.2 Optional Solo Word Definitions2.5.18 3.19 Optional End-to-End Message Verification2.5.19 3.20 Protocol Initialization2.5.19.1 3.20.1 Bit-Oriented Protocol Version2.5.19.1.1 3.20.1.1 ALOHA2.5.19.1.2 3.20.1.2 ALOHA Response2.5.19.2 3.20.2 Williamsburg/File Transfer Determination

2.6 Chapter 4.0 Window Bit-Oriented Protocol change to:Window Bit-Oriented File Transfer Protocol

2.6 4.1 Windowed Bit-Oriented Protocol change to:Windowed Bit-Oriented Communications Protocol

2.6.1 4.2 Window Size2.6.2 4.3 Window Definition


Old Number(Supp 14)


2.6.3 4.4 Protocol Word Deltas2.6.3.1 4.4.1 Request To Send (RTS)2.6.3.1.1 4.4.1.1 Unexpected Request To Send (RTS)2.6.3.2 4.4.2 Clear To Send (CTS)2.6.3.3 4.4.3 Not Clear To Send (NCTS)2.6.3.4 4.4.4 BUSY2.6.3.5 4.4.5 LDU Control Word (LCW)2.6.3.6 4.4.6 Start Of Transmission (SOT)2.6.3.7 4.4.7 Negative Acknowledgement (NAK)2.6.3.7.1 4.4.7.1 Missing LDU Control Word2.6.3.7.2 4.4.7.2 Missing SOT Word2.6.3.7.3 4.4.7.3 Missing EOT Word2.6.3.7.4 4.4.7.4 Parity Errors2.6.3.7.5 4.4.7.5 Word Count Errors2.6.3.7.6 4.4.7.6 CRC Errors2.6.3.7.7 4.4.7.7 LDU Timeout Errors2.6.3.8 4.4.8 Window Transfer Acknowledgement (ACK)2.6.3.8.1 4.4.8.1 Determination of End of Window2.6.3.8.2 4.4.8.2 Incomplete File Timer2.6.4 4.5 Bit Rate and Word Timing2.6.5 4.6 Response to ACK/NAK/SYN2.6.6 4.7 Protocol Initialization Deltas2.6.6.1 4.7.1 ALOHA2.6.6.2 4.7.2 ALOHA ResponseATT 10Table 10-1Table 10-2Table 10-3Table 10-4Table 10-5

ATT 1Table 1-1Table 1-2Table 1-3Table 1-4Table 1-5

Variables of Bit-Oriented ProtocolBit-Oriented Protocol EventsBit-Oriented Protocol Application SelectionBit-Oriented Protocol OptionsVariables of Low Speed Bit-Oriented ProtocolVariables of High Speed Bit-Oriented Protocol

ATT 11Table 11-1Table 11-1ATable 11-2Table 11-2Table 11-4Table11-4ATable 11-4BTable 11-5Table 11-6Table 11-6ATable 11-7Table 11-7A

ATT 2Table 2-1Table 2-1ATable 2-2Table 2-3Table 2-4Table 2-4ATable 2-4BTable 2-5Table 2-6Table 2-6ATable 2-7Table 2-7A

Bit-Oriented Data File Transfer Word FormatsGeneral Word Format Word TypeFull Data WordPartial Data WordProtocol Word ALO-ALR Version Number ALO-ALR Window SizeSolo WordStart of Transmission General Format Identifier (GFI)End of Transmission Final LDU Bit

ATT 11A ATT 3 Destination Codes


Old Number(Supp 14)


ATT 11B ATT 4 Status CodesATT 11C Table 11C-1 Table 11C-2 Table 11C-3

ATT 5 Table 5-1 Table 5-2 Table 5-3

ALOHA/ALOHA Response Protocol Word Definition ALOHA Initial (ALO) Protocol Word ALOHA Response (ALR) Protocol Word Version Number for ALO/ALR Protocol Words

ATT 12 ATT 6 File Transfer ExampleATT 12A ATT 7 Field Mapping ExchangeATT 13 Diagram 13-1 Diagram 13-2 Diagram 13-3

ATT 8 Diagram 8-1 Diagram 8-2 Diagram 8-3

Protocol Determination procedure Diagrams Protocol Determination Procedure Diagram (Two Bilingual Units) Protocol Determination Procedure Diagram (One Bilingual Unit and OneCharacter-Only Unit)

ATT 13A ATT 9 ALOHA Version Determination SequenceATT 15 ATT 10 Link Layer CRC Data ExampleATT 16 ATT 11 Sequence of Protocol and Data Words in Window TransferATT 17 ATT 12 Flow Diagram Used to Determine Character-Oriented vs Bit-Oriented ProtocolAPPENDIX 6A6-2.1.5A6-2.1.5.2A6-2.1.5.3A6-2.3.1A6-2.3.1.4A6-2.3.1.5A6-2.3.1.5.1A6-2.3.1.5.2A6-2.3.1.5.3A6-2.3.1.5.4A6-2.3.1.5.5A6-2.3.1.5.6A6-2.3.1.5.7A6-3.2A6-3.2.1A6-3.2.2A6-3.2.3

APPENDIX AA2.1.5A2.1.5.2A2.1.5.3A2.3.1A2.3.1.4A2.3.1.5A2.3.1.5.1A2.3.1.5.2A2.3.1.5.3A2.3.1.5.4A2.3.1.5.5A2.3.1.5.6A2.3.1.5.7A-3.2A3.2.1A3.2.2A3.2.3

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. 5 Data Maintenance Data

APPENDIX 7 APPENDIX B Mathematical Example of CRC Encoding/DecodingAPPENDIX 8 APPENDIX C Interoperability of Bit-oriented Link Layer ProtocolAPPENDIX 9 APPENDIX D SDL Diagrams of Williamsburg Protocol


2551 Riva RoadAnnapolis, Maryland 21401 - 7645 USA

SUPPLEMENT 16

TO



PART 3


Published: June 30, 1997





This Supplement reorganizes Part 3 to be consistent withprevious published versions of ARINC Specification 429.It also restores several paragraphs missing fromSupplement 15.

The technical changes include clarification of the Version1 (Williamsburg) protocol, deletion of the Version 2protocol, and creation of the Version 3 protocol. Thedefinition of the Version 3 protocol will be completed in afuture Supplement.


The first part of this document, printed on goldrodcolored paper, contains descriptions of the changesintroduced into this Specification by this Supplement. Thesecond part, printed on white paper, contains the changesmade to the specification. The modified and addedmaterial on each page is identified by a c-16 in themargins. In view of the document reorganization, ARINCSpecification 429, Part 3, is reprinted in its entirety asARINC Specification 429-16, Part 3.

C. CHANGES TO ARINC SPECIFICATION 429,INTRODUCED BY THIS SUPPLEMENT

This section presents a complete tabulation of the changesand additions to the Specification introduced by thisSupplement. Each change and addition is defined by theSection number and the title that will be employed whenthe Supplement is eventually incorporated. In each case,a brief description of the change or addition is included.

1.0 Introduction

This section contains a reorganization of the materialpreviously in Section 1.0 and 2.0 of ARINC Specification419P3-15 with the following exceptions.

The section on Graphic Data Transfer (formerly 1.3.4) isdeleted, Sections 1.3, 1.3.1, 1.3.2, and 1.3.4 include minorchanges clarifying the background for file data transfer,and Section 1.3.6 on Bit-Oriented Protocol Determination(formerly 1.3.7) was revised to refer to Section 2.5.19.

2.0 Bit-Oriented File Transfer Protocol

Section number 2.1 – 2.4 have been inserted asplaceholders to re-establish section numberingconsistency with ARINC Specification 429-14 and itspredecessors.

Section 2.5 and subsections contain the material previouslypublished in Section 3.0 of ARINC Specification 429P3-15, as modified below.


References to Attachments 12 and 12A updated.

2.5.1 Link Data Units (LDU)

The definition of LDU is clarified.

2.5.3 System Address labels (SALs)

Commentary on use of SALs clarified.


Commentary on use of word gap criteria clarified.


Introduction to section added, and use of Destination Codeclarified.

2.5.6.3 Word Count

Introduction to section added.

2.5.7.3 Destination Busy (BUSY)

The use of Option 3 (Send Auto CTS) and Option 4(Accept Auto CTS) is clarified.

2.5.81 Half Duplex Mode

This section restores text missing from the publishedversion of Part 3, Supplement 15.

2.5.11.2 Partial Data Word

Location of the length of a partial data word is clarified.


The definition of a duplicate LDU is clarified.

2.5.15 SYN Word

The definition of a duplicate LDU is clarified.


The protocol version determination is clarified.

2.5.19.1 Bit-Oriented Protocol Version


2.5.19.1.1 ALOHA


2.5.19.1.2 ALOHA Response

This section restores text missing from the publishedversion of Part 3, Supplement 15.

2.5.19.2 Williamsburg/File Transfer Determination

This section restores text missing from the publishedversion of Part 3, Supplement 15, and commentary is addedon use of a NAK in the protocol determination logic.

2.6 Windowed Bit-Oriented Communications Protocol

Section 2.6 and subsections have been deleted. Section 2.6contained the definition of Version 2 of the Williamsburgprotocol. Version 2 of the Williamsburg protocol has beensuperseded by Version 3. Section 2.6 and subsectionscontained the material previously published in Section 4.0of ARINC Specification 429P3-15.

SUPPLEMENT 16 TO ARINC SPECIFICATION 429 PART 3- Page 3

3.0 Bit-Oriented Media Access Control (MAC)

An introduction to the Bit-Oriented Media Access Control(Williamsburg Version 3) protocol is added.

ATTACHMENTS 1-17

Attachment numbers 1-9 have been inserted asplaceholders to re-establish section numbering consistencywith ARINC Specification 429-14 and its predecessors.

Attachments 10-17 contain material published inAttachments 1-12 of ARINC Specification 429P3-15, asmodified below.

ATTACHMENT 10 - VAIABLES OF BIT-ORIENTEDPROTOCOL

Table 10-3 is replaced with Table 10-3A, containingoptions for Version 1. Tables 10-3B, 10-6 and 10-7 areadded as placeholders for Version 3 Williamsburg.Variables for the Version 2 protocol in Tables 10-1 and 10-3A are deleted.

ATTACHMENT 11 - BIT-ORITENTED DATA FILETRANSFER WORD FORMATS

The general word format in Table 11-1 is clarified.

The LCW protocol word format in Table 11-4 ismodified.

Table 11-4 is modified to add the Service Class Identifierto the LCW format.

Table 11-4B is deleted as part of the Version 2 protocol.

Table 11-4A is modified to add the version number forVersion 3, and delete references to Version 2.


The destination Code N for FMC, Center, is added.

ATTACHMENT 11C - ALOHA/ALOHA RESPONSEPROTOCOL WORD DEFINTION

The ALOHA and ALOHA Response protocol worddefinitions are revised to be consistent with other changesmade to the protocol, and the titles of the tables modifiedto indicate they are examples.

ATTACHMENT 12 - VERSION 1 FILE TRANSFEREXAMPLE

The title is changed to indicate Version 1.

ATTACHMENT 12A - FIELD MAPPING EXAMPLE

Attachment 12A is replaced with an updated example

ATTACHMENT 15 - LINK LAYER CRC DATAEXAMPALE

This section is deleted as part of the Version 2 protocol.

ATTACHMENT 16 - SEQUENCE OF PROTOCOLAND DATA WORDS IN WINDOWN TRANSFER

This section is deleted as part of the Version 2 protocol.

APPENDICES A-K

Appendix numbers A-E have been inserted asplaceholders to re-establish section numberingconsistency with ARINC Specification 429-14 and itspredecessor.

Appendices F-J contain the material published inAppendices A-D of ARINC 429P3-15.

Appendix H was revised to reflect the deletion of theVersion 2 protocol and creation of the Version 3 protocol.



SUPPLEMENT 17

TO

ARINC SPECIFICATION 429©


PART 3


Published: May 31, 1999


Adopted by the Airlines Electronic Engineering Committee: March 31, 1999



This Supplement introduces the definition of a new bit-oriented file data transfer protocol. The protocol is designedto be consistent with the IEEE-802 Media Access Control(MAC) protocol definition. Version 3 fills the role intendedfor Version 2 of the Williamsburg protocol by providing ahigh throughput avionics file data transfer interface. Version2 was deleted by Supplement 16. Version 3 is intended tobe capable of being bridged to other common data busprotocols, most significantly, Ethernet.


Changes introduced by Supplement 17 were deemedsufficiently significant to issue an entirely new publicationof Specification 429 Part 3. There is no standaloneSupplement.

This part, printed on goldenrod-colored paper, contains alist of descriptions of changes introduced into thisSpecification by this Supplement 17.

In the body of the document, the changes (.i.e., the modifiedand added material) introduced by Supplement 17 areidentified by c-17 change bars in the margins.

C. CHANGES TO ARINC SPECIFICATION 429, PART3 INTRODUCED BY THIS SUPPLEMENT

This section presents a complete tabulation of the changesand additions to the Specification introduced by thisSupplement. In the text below, the Section number and titleof each affected Section, Attachment or Appendix is listed,followed by a brief description of the change or addition.


Transmission order of bits was clarified.

1.4 Relationship to Other Standards

A new section was added. It discusses the relationship ofthis document to other AEEC documents and to otherindustry documents.

3.0 Bit-Oriented Media Access Control Protocol

The definition of the bit-oriented Media Access Control(Williamsburg Version 3) protocol was added, replacingintroductory text inserted by Supplement 16 as aplaceholder.


Table 10-3B, containing options for Version 3, was added.

Table 10-6, containing timer values for the ARINC 429high-speed Version 3 bus, was added.

Table 10-7, containing a placeholder for low speed bustimers associated with Version 3 protocol was deletedbecause the low speed implementation is not recommended.

ATTACHMENT 11 - BIT ORIENTED DATA FILETRANSFER WORD FORMATS

Table 11-1A was updated to add Version 3 SOF and EOFwords.

Table 11-8 was added defining the command frame SOF.

Table 11-9 was added defining the command frame EOF.

Table 11-10 was added defining the information frameSOF.

Table 11-11 was added defining the information frameEOF.

ATTACHMENT 18 – MAC SUBLAYER SUPPORTDIAGRAMS

New Attachment added.

ATTACHMENT 19 – COMMAND FRAME DATAUNIT (FDU) STRUCTURE AND EXAMPLES


ATTACHMENT 20 – INFORMATION FRAME DATAUNIT (FDU) STRUCTURE AND EXAMPLES



Appendix 8 is updated to discuss interoperability betweenVersion 1 and Version 3.

APPENDIX 10 - ARINC 429 WILLIAMSBURGPROTOCOL LAYER DIAGRAM

A new Appendix was added providing a generaloverview of the protocol structure over differentcommunication stacks.



SUPPLEMENT 18

TO

ARINC SPECIFICATION 429©


PART 3


Published: October 12, 2001


Adopted by the Airlines Electronic Engineering Committee: July 18, 2001



This Supplement introduces the assignment of 3 newsatellite links, HFDR Right, TAWS, and CVR into theDestination Code table.

A Table was added to define the Variables of Low SpeedConnectionless Bit-Oriented Protocol.

Typographical errors were corrected in the text.


The first part of this document printed on golden-rod papercontains descriptions of changes introduced into thisSpecification by this Supplement.

The changes introduced by Supplement 18 have beenidentified using change bars and are labeled in the marginby a “c-18” indicator.

C. CHANGES TO ARINC SPECIFICATION 429, PART3 INTRODUCED BY THIS SUPPLEMENT

This section presents a complete tabulation of the changesand additions to the Specification to be introduced by thisSupplement. Each change or addition is identified by thesection number and the title that will be employed for thatsection when the Supplement is eventually incorporated. Ineach case a brief description of the change or addition isincluded.

3.4.3 System Address Labels (SAL)

Corrected the reference to the table of SAL assignments(from Attachment 14 to Attachment 11) in ARINCSpecification 429 Part 1.


Provision was added to specify that the Williamsburgversion 3 protocol may be operated at low speed.

ATTACHMENT 10 – VARIABLES TO BIT-ORIENTEDPROTOCOL

Added new Table 10-7 to support low speed operation ofWilliamsburg protocol at low speed. Later modified thevalue of the variables.

ATTACHMENT 11A – DESTINATION CODES

The assignment of ‘T” for the transponder was deleted. Sixnew entries, HFDR Right, TAWS, CVR Inmarsat, ICO, andGlobalstar satellite link identifiers were added as destinationcodes. The format and content of the table was aligned withthe corresponding Table 3-1 of Attachment 3 to ARINCSpecification 619 to improve consistency.

APPENDIX A – J

These appendices were formerly identified as Appendix 1 –10. During the regeneration of Specification DescriptionLanguage (SDL) diagrams in Appendix I, references toSection 1.3.7 were revised to Section 2.5.19.

APPENDIX K

New Appendix added.