ARINIG MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS) PART 1 FUNCTIONAL DESCRIPTION, ELECTRICAL INTERFACE, LABEL ASSIGNMENTS AND WORD FORMATS ARINC SPECIFICATION 429 PART 1-17 PUBLISHED: May 17, 2004 av ARINC vocument‘This document is based on material submitted by vasious participants during the drafting process. Neither AFEC nor ARINC. hhas made any determination whether these materials could be ‘subject 1o valid claims of patent, copyright or other proprietary sats by third parties. and no representation or warranty, express or implied, is made in this regard. Any use of or reliance on this document shall constitute an acceptance thereof “as is” and be subject to this disclaimer,ARINC Standard — Errata Report 41. Document Title ARINC Specification 429 Part 1-17: Mevk 33 — Digital Dyformation Transfer System (DITS) Published: May 17, 2004 2. Reference Page Number: 70___ Section Number: Att2. Table 2 Date of Submission: _1SMAROT 3. Error ARINC 429 Part 1, Table 2, BNR Data, (Label 335 reproduced in part): ARINC Specification 429 (May 17,2004) Min | Max | Max apt Transmit | Transmit | Trans. Label | 1D Praneter Units es ia aa Resolution | Interval | Interval | Port Delay | Notes aex| > (onsee) | (msee) | (mse) 2 2 3 oa | Track Angle Rate | DepSee | 32 | 11 bois 10 20 (04 _| Teck Angle Rate | Deg’Ses | _32_| 11 ois 10 20 00s | Teele Angle Rate | Deg'See | 32 | 11 ois 10 20 oF ays [038 | Track Angie Rate | DeyiSec [32 [13 018 10 20 03F 056 _| Track Angie Rate | Degisee | 32 [11 01s 10 20 (050 _| Track Angle Rate | DepiSes | 32 | 11 pois 10 20 108 108 4. Recommended Correction ARINC 429 Part 1, Table 2, BNR Data (Label 335 reproduced in part), Changes are shaded in yellow ARINC Specification 429 Part 1-17 REVISED. Min ‘Max Max Eat |p, R sig | Po \Transmit | Transmit | 79° aba] ad | Peame | aig | Ran | S| 78 Jpation | itera! | eral | | Nie EX (ses) | mes) | rcs 2 |? | oof Ange Rae | Dees a oom | a} ot Task nl at [Deg ee h oois | 10 | 9 05 [Task Angle Bat | Dees u oois | 0 | 29 OF sos [088 Tas Ange Ra | Deve 7 ois | OF oss_| Takagi | Degee a come] 9 060 [Tak Angle Rate | DepSes n oois| 0 | 29 wun rT ARIS Eo orm 12420085. Reason for Correction Table 2 from ARINC Specification 429 Part 1 provides baseline definition of Label 335, Track Angle Rate data. “Notes” column is expanded to show the system aeronyas for each of the souroesideutified by the "Equipment ID” Positive sense is specified as CW (clockwise) to conform to ARINC 705, AHRS, and ARINC 718A, Transponder 6. Submitter (Optional) Robert H. (Bob) Saffell (Rockwell Collins) and Paul Prisaznuk (AEEC staff) ‘Comments should be directed to daniel martinec @arine.com. nendations will be evaluated by the staff, Any mmittee for incorporation into a subsequent Note: Items 2-5 may be repeated for additional errata. All recom substantive changes will requite submission to the velevant su Supplement. [To be completed by IA Staff] Errata Report Identifier: 07-0S1/ERR.00S Engineer Assigned: Dan Martinec. Review Statu: ARINC Enea Foon 1242008Specification 429 Specification 129 © 2004 by AERONAUTICAL RADIO, INC. 2851 Riva Road Annapolis, Maryland 21401-7465 USA. ARINC SPECIFICATION 429 PART 1-17 ‘MARK 33 DIGITAL INFORMATION TRANSFER SYSTEM (DITS) PART 1 FUNCTIONAL DESCRIPTION, ELECTRICAL INTERFACE, LABEL ASSIGNMENTS AND WORD FORMATS Published: May 17, 2004 Prepared by the Airlines Electronic Engineering Committee Adopted by the Airlines Electronic Engineering Committee July 21, 1977 ‘Adopted by the Industry: September 15, 1977 Summary of Document Supplements ‘Supplement Adoption Date Published Specification 429-1 April 11, 1978 June 1, 1978 Specification 129-2 ‘December 6, 1978 ‘March 1, 1979 Specification 429-3 ‘August 31, 1979 November 1, 1979 Specification 129-4 June 17, 1980) August I, 1980, Specification 429-5 March 12, 1981 April 4, 1981 Specification 129-8 ‘December 9, 1981 January 22, 1982 Specification 429-7 November 4, 1982 January 3, 1983) Specification 439-8 November 4, 1983 December 3, 1984 Specification 129-9) October 11, 1984 ‘Apnil 30, 1985 Specification 429-10 November 7, 1985 November 17, 1986 Specification 429-11 June 15, 1988 July 22, 1988 Specification 429-12 October 25, 1989 July T, 1990 Specification 429-13 October 8, 1991 Deceriber 30, 1991 Specification 429-14 November 4, 1992 January 4, 1993 Specification 129-15 “Apmil 15, 1995 September 1, 1995 Specification 429-16 November 14, 2000 September 27, 2001 Specification 129-17 May 8,204 May 17, 2004) A deseription of the changes introduced by each supplement is included on goldenrod paper atthe end of this documentFOREWORD Aeronautical Radio, Inc.. the AEEC. and ARINC Standards Aeronautical Radio, Inc. (ARINC) was incorporated in 1929 by four fledgling airlines in the United States as a privately-owned company dedicated to serving the communications needs of the air transport industry. Today, the major U.S. aitlines remain the Company's principal shareholders. Other shareholders include a number of non-U.S. airlines and other aircraft operators. ARINC sponsors aviation industry committees and participates in related industry activities that benefit aviation at large by providing techmical leadership and guidance and frequency management. These activities directly support airline goals: promote safety. efficiency. regularity. and cost-effectiveness in aireraft operations. The Airlines Electronic Engineering Committee (AEEC) is an international body of airline technical professionals that leads the development of technical standards for airborne electronic equipment including avionics and in-flight entertainment equipment-used in commercial, military, and business aviation. The ABEC establishes consensus-based, voluntary form. fit, fnction. and interface standards that are published by ARINC and are known as ARINC Standards, The use of ARINC Standards results in substantial benefits to airlines by allowing avionics interchangeability and commonality and reducing avionics cost by promoting competition. There are three classes of ARINC Standards a) ARINC Characteristics ~ Define the form, fit, function, and interfaces of avionics and other airline electronic equipment. ARINC Characteristics indicate to prospective manufacturers of airline electronic equipment the considered and coordinated opinion of the airline technical ‘community conceming the requisites of new equipment including standardized physical and electrical characteristics to foster interchangeability and competition. b) ARINC Specifications — Are principally used to define either the physical packaging or ‘mounting of avionics equipment. data communication standards, ot a high-level computer language. ©) ARINC Reports — Provide guidelines or general information found by the airlines to be good. practices, often related to avionics maintenance and support, The release of an ARINC Standard docs not obligate any airline o ARINC to purchase equipment so described, nor does it establish or indicate recognition or the existence of an operational requirement for such equipment, nor does it constitute endorsement of any manufacturer’s product designed or built to meet the ARINC Standard. In order to facilitate the continuous product improvement of this ARINC Standard, two items are included in the back of this volume: a) An Errata Report solicits any corrections to the text or diagrams in this ARINC Standard. b) An ARINC IA Project Initiation’ Modification (APIM) form solicits any recommendations for addition of substantive material to this volume which would be the subject of a new Supplement.nN. ‘TABLE OF CONTENTS SUBJECT PAGE peTRODUCTE Purpose of this Document Organization of ARINC Specification 429 Relitiouship to ARINC Specizeation 419 “Mark 33 Digital Information Transfer System” Basic Philosophy ‘Numesis Data Transfer ISO Alphabet No. 5 Data Transfer Graphit Data Transier DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS Message Related Elements Direction of Information Flow Information Element Information Identifier Souree/Destination Identifier Sign/Status Matis 'BCD Numeric BNR Numeric Data Words Discrete Data Words Data Standards Electrically Related Elements ‘Transmission System Interconnect ‘Modulation Voltage Levels “Transmitter Voltage Levels Receiver Voltage Levels Impedance Levels Transmitter Output Impedance Reeciver Input Impedance Fault Tolerance Receiver Extemal Fault Voltage Tolerance ‘Transmitter Extemal Fault Voltage ‘Transmitter Extemal Fault Load Tolerance Fault olation Receiver Fault Isolation ‘Transmitter Fault Isolation Logic Related Elements Digital Language ‘Numeric Data Discretes Maintenance Data (General Purpose) AIM Data File Data Transfer 1 Bit-Oriented Protocol Determination ‘Transmission Order Data Bit Encoding Logic Exzor Detection Correction Timing Related Elements ‘Bit Rate High Speed Operation Low Speed Operation Information Rates Clocking Method 10 Word Synchronization 10 Timing Tolerances 10 6 6 62 MARK 33 DITS APPLICATIONS NOTES u Radio Systems Management i Word Format and Digital Language im Update Rate iL Sign Status Matrix ul Frequency Ranges and Switching Functions i ‘ADF rn DME. inN. ‘TABLE OF CONTENTS SUBJECT HE Communications ILs VORILS VHF Communications ATC Transponder ‘AIM Information Transfer Label Codes, Equipment Codes Data Standards Voltage Levels Input Output Cizcuit Standards International Standards Organization Code #5 General Word Formats and Encoding Examples Data Bit Encoding Logic Output Signal Timing Tolerances General Aviation Labels and Data Standards General Aviation Word Examples General Aviation Equipment Identifiers Manufacturer Specific Status Word System Address Labels Laboratory Verification of ARINC 429 DITS Electical Characteristics dn Approdsh oa Hybrid Broades Command Response Data Bos Arcitectre Digital Systems Guidance (Part 1) Digital Syetemss Guidance (Part2) Guidelines for Label Assignments Chronology & Bibliography ARINC Standard ~ Errata Report ARINC IA Project Initiation’ Modification (APIM) PAGE ul i i L i 2 13 3 g 15 76 nT 78 uy 118 us 121 12s 129 130 132 165 170 77 182 1stels ARINC SPECIFICATION 429, PART 1 - Page 1 LOINTRODUCTION 1.1 Purpose of this Dosument This document defines the air transport industry's standards for the uansfer of digital data between avionics systems elements. Adherence to these standards is desized for all inter-systems communications in which the system line replaceable units are defined as unit interchangeable in the relevant ARINC characteristics. Their use for intra-system Communications in systems in which the line replaceable ‘mits are defined in the ARINC characteristics as system interchangeable is not essential, although it may be convenient. 1.2 Organization of ARINC Specification 429 ARINC Specification 429 was originally published in a single volume through version 14 (429-14). ‘The size of the document and the need for improved organization dictated the division of the document into three parts, Those three parts include; Part 1 Functional Description, Electrical Interface, Label Assignments and Word Formats Part2 Discrete Word Data Formats Part 3. File Data Transfer Techniques, Part 1 provides the basic description of the functions and the supporting physical and electrical interfaces forthe data transfer system. Data word formats, standard label and address assignments, and application examples are defined. Part 2 lists diserete word bit assignments in label order, Part 3 describes protocols and message definitions for” data transferred in Jarge blocks andor file format. | For convenience of the user, the section and attachment numbering has been retained for the material moved from the original Specification to Part 3 Updates to each part of future releases of ARINC 429 will bbe independent of the other parts to accommodate timely revisions as industry needs dictate. The dash numbers for exch Part will NOT be synchronized with the other Paris as time passes. “Users of ARINC Specification 429 should ensure that the latest version of each Part is used when designing or procuring equipment. 13 Relationship to ARINC Specification 419 ARINC Specification 419, “Digital Data Systema Compendium”, is a catalog of the elements of the several digital deta ‘transmission systems that have found application during the “emergent” period of digital avionics technology. The maturing of this technology, now evident in the scope of its planned use on aircraft of the 1980s and beyond, has shown the need for a generally applicable digital information transfer system having capabilities not provided by any combination of the elements presently defined in Specification 419. In defining such a system, this document draws on the experience gained inthe preparstion ff Specification 419 buts otherwise separate and distinet from it, Addition of the element specifications of the system defined herein to the Specification 419 catalog is not anticipated, MMe Palen This “Mark 33 Digital Information Transfer System (DITS)” specification describes a system in which an elma en len ving infomation to, ana jozs so from a designated ouput port over a sinale tw tnd shictded pai of vires to all othr sytem ements hhaving need of that information, Bi-directional data flow on a given twisted and shiclded pair of wires is not permitted, 1.4.1 Numetie Data Transfer ‘The Mark 33 DITS numeric data transmission characteristics have been developed from those of successful predecessor air transport industry digital information transfer systems. Data for transmission, encoded in either twos complement dractional binary notation or binary coded decimal notation, is supplied from source systems at rates sufficiently high to ensure small incremental value changes been updates. Transmission is made “open loop”, ie, sinks are not required to inform sources that information has been received. A parity bit is tuansmitted as part of each data word to permit simple error cheeks to be performed by the sinks. ‘These, together with data reasonableness checks which may also be performed by the sinks, may be used to prevent the display or other utilization of 2 erroneous of suspect word, The inherently high intearty of the twisted and shielded wire transmission medium ensures that such drop-outs are few, The low rates of shang of th dra ensue that when one does eect tis cof no consequence, 1.4.2 ISO Alphabet No. § Data Transfer In addition to the transfer of BNR and BCD numeric data as just deseribed, the Mark 33 DITS handles alpha and! numeric data encoded per ISO Alphabet No, 5. The same “broadcast” transmission philosophy is used, although the “housekeeping” aspects of system operation differ in order to accommodate particular needs associated with this type of data. These differences will be addressed individually in| this document as they arise, 1.43 Graphic Data Transfer A third type of data which may eventually be handled bythe Mark 33° DITS i graphic data, ie, the lines, circles randomly positioned alphafnumeri text and otber symbols teed on CRT aap and sinilar displays. ‘The techrique ‘ployed for this purpose ean be basicaly similar to that {sel for ISO Alphabet No.3 alphanumeric data transfer Hovere, because anne ft gop da ening capability has not yet emerged, the ar transport industry has detided not to be specific conceming this technique forthe moment. When the need for araphic data handling is| CStublished, appropriate specification ‘material wil be developed. el elARINC SPECIFICATION 429, PART 1 - Page 2 2.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS 2.1 Message Related Elements Tie secon decibes the dial ata wane stm lements considered to be principally related to the message itself or the manner in which itis handled. 2.1.1 Direstion of Information Flow The information output of an avionics system clement should be transmitted from a designated port (or ports) to which the receiving ports of other system clements in need of that information are connected. In no case does information flow into a port designated for transmission, COMMENTARY. ‘A separate data bus (twisted and shielded pair of wires per Section 2.2.1) for each direction is used when data is required to dow both ways between to avionics systems elements, 2.1.2 Information Element The basi information clement is digital word containing 32 bia There are five aplication groups for such words BNR data, BCD data, Discrete data, Maintnsnce data (General) and Acknowledgement, SO Alphabet Number 3 atx Maintenance (ISO Alphabet Number 5) data (AIND, ‘Word formats for thse diferent applications are depicted in Atachment 6 while te relevant Gat handling rule are fet forth n Section 2.1. When Less than the fll data fed iS needed to aroommodate the information coaveyed ina ‘word inthe desred manner, the unwed bit postions should i led wih binary 20s or, in the ease of BNVBCD, rmaerio data, valid deta bit. valid data bits are used, the fesohtion possible for the information may exceed that called for in this Spesfiaton. The Commentary following Section 2.1.6 ofthis document refs COMMENTARY. ‘To permit the use of identical eror-checking hardware elements in the handling of BNR and BCD numeric data words, the format for the Mark 33 DITS BCD. ‘word differs fiom that used formerly for this type of data. Bit Number 32 is assigned to parity, Bit Numbers 31 and 30 to the sign/tatus matrix, Bit ‘Number 29 is the most significant bit ofthe data field, and the maximum decimal value of the most significant character is 7. Previously, the BCD word. contained no party bit, the sign/status matrix occupied Bit Numbers 32 and 31, Bit Number 30 was the most significant data bit and the maxignum decimal value of the most significant character was 3, This format made the word 8-bit byte oriented with respect to the data. This characteristic is not retained in the Mark 33, system, Also, latitude and longitude can only be encoded in the Mak 33 DITS word with the formerly specified resolution of 0.1 minute of are if Bit Numbers 9 and 10 are used for daia rather than the SDI function deseribed in Section 2.1.4 of this document, and the word is structured differently from the standard shown in Attachment 6. Restructuring the word involves limiting the maximum value of the most significant character to 1 and moving the remaining BCD characters towards the MSB by two bit positions. Itis possible, however, that future latitude and lonaitude displays will not be the simple, dedicated read-out type for which BCD data is intended, More likely isthe use of some form of multiple-message display, such as a CRT, which will be backed by ite own data processor and prefer inputs of BNR data. _If this proves to be the case, these special provisions for BCD-encoding will not be required. 2.1.3 Information Identifier ‘The type of information contained in a word is identified by a six-character label. The fist three characters are octal characters coded in binary in the first eight bits of the word. The eight bits will a. identify the information contained within BNR and BCD numeric data words (e.g., DME distance, static air temperature, ete.) and identify the word application for Discrete, Maintenance and AIM data, ‘The last three characters of the six-character label are hexadecimal characters used to provide for identification of ARINC 429 bur sources, Each triplet of hexadecimal characters identifies a “black box” with one or more DITS ports, Each three character code (and black box) may have up to 255 cight bit labels assigned to it, The code is used administratively to retain distinction between unlike parameters having like labels assignments. COMMENTARY. Some users have 2d a desire to have means for ‘Renting label sets and buses aseociated wath particular equipment ID code, Octal label 377 has ‘been assigned for this purpose. (The code appears in the 3 LSDs of the BCD Word format), The transmission of the equipment identifier word on a bus will permit receivers attached to the bus to recognize the source of the DITS information, Since the twansmission of the equipment identifier word is optional, receivers should not depend on that word for correct operation Label code assignments are set forth in Attachment 1-1 10 this document, Special Note: In some ARINC 429 DITS applications, a bus will be dedicated to delivering 2 single information element from a source to one or more identical sink devices. In such circumstances, the sink device designer might be tempted to assume that decoding the word label is not necessary. Experience has shown, however, that system developments frequently occur that result in the need for additional information elements to appear on the bus. If sink device designed for service prior to such a development cannot decode the original word label, it cannot Installation Number See Nove Below 1 Note: In certain specialized applications of the SDI function the all-call capability may be forfeited so that code “00” is available as an “installation Number 4” ‘detifier, When the SDI function is not used, binary zeros or valid data should be transmitted in Bit Numbers 9 and 10. COMMENTAR' This document does not adress the practical question, of how the SDI bits will be set’ in those multi- installation systems in which the sourceidestination, fmetion is desired. One way would be to use program, pins on the individual installation black boxes which ‘would be wired to set up the appropriate code. The ARINC Characteristics devoted to the individual systems will define the method actually to be used, 2.1.8 Sign/Status Matris ‘This section describes the coding of the Sign’Status Matrix (SSM) field. In all cases the SSM field uses Bits 30 and 31 For BNR data words, the SSM field also includes Bit 29. ‘The SSM field may be used to report hardware equipment condition (faulvnormal, operational mode (Zmetional test), cor validity of data word content (verified/no computed data). ‘The following definitions apply in thie Specification: Invalid Data - is defined as any data generated by a source system whose fundamental characteristic isthe snabulity 10 convey reliable information for the proper performance of a user system. There are two categories of invalid data, ‘namely, “No Computed Data” and “Failure Waming.” No Computed Data - is a particular case of data invalidity \where the souree system is unable to compute reliable data for reasons other than system failure. This inability to compute reliable data is caused exclusively by a definite set of events or conditions whose boundaries are uniquely ‘defined inthe system characteristic Failure Waming - is 2 particular case of data invalidity where the system monitors have detected one or more failures. These failures ate uniquely characterized by houndaries defined in the system characteristic. ‘The system indicators should always be flagged during a ‘allure Waming” condition, When a “No Computed Data” condition exists, the source system should snnuneiate ite ouputs to he invalid by setting ‘he signistatus matrix of the affected words to the “No Computed Data” code, 25 defined in the subsections which | follow. The system indicators may or may not be flagged, depending on system requirements. While the unit is inthe fanctional test mode, all output data words generated within the unit (Le., pass through words are excluded) should be coded for “Functional Test.” Pass through data words are those words received by the unit and setransmitted without alteration, When the SSM code is used to transmit status and more than one reportable condition exists, the condition with the highest priomty should be encoded in Bit Numubers 30 and ‘The order of condition priorities to be used is shown in| ihe table below. el ezARINC SPECIFICATION 429, PART 1 - Page 4 2.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS 2.1.5 Siga/Status Matris (cont'd) Failure Waming | Pronity 1 No Computed Data | Priority 2 Functional Test | Priority 3 Normal Operation | Priority 4 Each data word type has its own unique utilization of the SSM field. These various formats ate described in the following subsections. 2.1.5.1 BCD Numeric When a failure is detected within a system which would cause one or more of the words normally output by that tem to be unreliable, the system should stop transmitting the affected word or words on the data bus. Some avionie systems are capable of detecting a fault condition which results in les than normal accuracy. In these systems, when a faut of this nature (for instance partial sensor loss) which results in degraded accuracy Getected, each unreliable BCD i STITT” when transmited on the data bus For equipments having a display, the “1111” code should, when Teceived, Sah equa bbe dil be dplaved & pace of the inaccurate digit Parameters for which such a eraded mode of operation is possible are identified in the Note Column of the tables in Attachment 2 ‘The sign (plus‘minus, north/south, etc.) of BCD Numeric Data should be encoded in bit mumbers 30 and 31 of the ‘word as shown in the table below. Bit Numbers 30 and 31 of BCD Numeric Data words should be “zero” where no sign is needed. ‘The “No Computed Data” code should be anmunciated in the affected BCD Numeric Data word(s) when a source system is unable to compute reliable data for reasons other than system failure When the “Functional Test” code appears in Bits 30 and 31 of an instruction input data word, it should be interpreted as command to perform a functional test. COMMENTARY. A typical instruction input to a radio, for example, ‘would be a channel change command word. When t command word is received with the “Functional Test coding in the SSM field, the radio should exercise its functional tes. When the “Functional Test” code appears as a system output, it should be interpreted as adviee thatthe data inthe BCD Numeric Data word contents are the result of the execution of a functional test, A functional test should produce indications of 1/8 of positive fullscale values lunless indicated otherwise in the associated ARINC Equipment Characteristic, BCD NUMERIC SIGN/STATUS MATRIX Ba Number Ba Numba Meaning 0) 0 _| Plus, North, East, Right, To, Above 0 | 1 | NoCompured Data 1 | 0 | Functional Test 1_| 1 | Minus, South, West, Left, From, Below 2.15.2 BNR Numeric Data Words ‘The status of the transmitter hardware should be encoded in the Status Matrix field (Bit Numbers 30 and 31) of BNR Numeric Data words as shown in the table below. A source system should annunciate any detected failure that causes one or more of the words normally output by that system to be unreliable by setting Bit Numbers 30 and 31 in the affected word(s) to the “Failure Waming” code defined in the table below, Words containing this code should continue to be supplied to the data bus during the failure condition ‘The “No Computed Data” code should be annunciated in the affected BNR Numeric Data word(s) when a source system is unable to compute reliable data for reasons other than system failure When it appears as a system output, the “Functional Test” code should be interpreted as advice that the data in the ‘word results from the execution of a finetional test, A funetional tet should produce indications of 1S of positive full-scale values unless indicated otherwise in an ARINC equipment charaeterisic, If, during the execution of a functional test, a source system tects a failure which causes one or more of the words normally output by that system to be unreliable, it should immediately change the states of Bit Numbers 30 and 31 in the affected words such that the “Functional Test” anmunciation is replaced with “Failure Warning” ‘annuneiation, BNR STATUS MATRIX Bit Number aL oe Meaning 0) 0 | Faihue Waring 0 | 1 | NoComputed Data 1 | 0 | Functional Test 11 _| Normal Operation ‘The sign (plus, minus, north, south, ete.) of BNR Numeric ‘Data words should be encoded in the Sign Matrix field Bit Number 29) as shown in the table below. Bit Number 29 should be “zero” when no sign is needed,ez els el2 ols el? ARINC SPECIFICATION 429, PART 1 - Page S 2.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS SIGN MATRIX Base Me 0 ‘Plus, North, East, Riaht, To, Above 1 ‘Minus, South, West, Let, From, Below Some avionie systems are capable of detecting a fault condition which results in less than normal accuracy. In these systems, when fault of this nature (for instanc partial sensor loss) which results in degraded accuracy is detected, the equipment should continue fo report “Normal” for the sign status matrix while indicating the degraded performance by coding bit 11 as follows: ACCURACY STATUS BENnbe eaning 0 ‘Nominal Accuracy 1 ‘Degraded Accurae ‘This implies that degraded ageurney ean be coded only in BNR words not exceeding 17 bits of data. Parameters for which such a degraded mode of operation is possible are identified in the notes column of the tables in Attachment 2 2.1.5.3 Discrete Data Words A source system should annunciate any detected failure that could cause one or more of the words normally output by that system to be unreliable. ‘Three methods are defined. ‘The firet method is to set Bit Numbers 30 and 31 in the affected word(s) to the “Failure Warning” code defined in the table below. Words containing the “Failure Warning code should continue to be supplied to the data bus during the fiulure condition. When using the second method, the ‘equipment may stop transmitting the affected word or words fon the data bus, Designers should use this method when the display or use of the discrete data by a system is undesirable. The third method applies to data words which are defined auch that they contain fahure information Within the data field. For these applications, refer to the associated ARINC equipment characteristic to determine proper SSM. reporting. Designers should preclude mixing operational and BITE data inthe same word, ‘The “No Computed Data” code should be anmunciated in the affected Discrete Data word(s) when a source system is lunable to compute reliable data for reasons other than system failure, When the “Functional Test” code appears as a systema ‘output, it should be interpreted as advice thatthe data inthe Diserete Data word contents are the result of the execution of a functional test DISCRETE DATA WORDS Bat Number Ba Nomber Meaning 0 | 0 | Verified Data, Normal Operation 0 | 1 | NoComputed Data 1 | 0 | Functional Test 1_| 1 _| Fsiture Waning 2.1.6 Data Standards The units, ranges, resolutions, reffesh rates, mumber of significant bits, pad bits, etc. for the items of information to be transfemred by the Mack 33 DITS are tabulated in Attachment 2 to this document. COMMENTARY Note that Section 23.1.1 of this document calls for numeric data to be encoded in BCD and binary, the latter using twos complement fractional notation. In this notation, the most significant bit of the data field represents one half of the maximum value chosen for the parameter being defined. Successive bits represent the increments of a binary fraction series, Negative numbers are encoded as the twos complements of positive value and the negative sign is annumciated in the sign/status matri, Tn establishing a given parameter's binary data Standards for toclusfoa in ‘Atachment 2 the units Maximum valve and resokton are it deermined in that onder. The least significant bit of the word is then sven a value equal othe resofution increment nd the fianber of significant bis ig chosen such that the taxinum valve of the factional inary series just cxesads the maximum value of the parameter, Le. qual the neat whole binary auiber greater than the tinimum parameter value Tess one least sianiicant bit Valu, For example ifthe Mark 35 DITS fs required (> transfer altode in units of fet over a range of zero to 10,000 feet with a reohition of one foots the number of sianificant bits 17 andthe maximum value ofthe factional bina series i 131,071 Gre, 131,072 1). Note that because accuracy is a quality of the sree roses an oth data ser proses i plays no past in the selection of word characteristics bridal be resolotion provided ia the DITS word Shonen or ese he sccasy oer nt 10 elt For the binary representation of angular data, the Mark: 33 DITS employs “degrees divided by 180°" as the unit of data tansfer and +1 (semicicle) as the range for twos complement fractional notation encoding Genoring, for the moment, the subtraction of the least significant bit value). Thus the anguler range 0 through 359.XXX degrees is encoded as 0 through +4179.XXX degrees, the value of the most significant bit is one half semicircle and there are no dliscontinuities in the code. This may be illustrated as follows. Consider encoding the angular range 0” to 360° in 1° increments. Per the ‘general encoding rules above, the positive semicircle ‘ill cover the range 0° to 179° (one least significant bit less than full range). Al the bits of the code will be “Zeros” for O° and “ones” for 179°, and the sign/status atric will indicate the positive sign. The negative semicircle will cover the range 180° to 359°. All the bits will be “zeros” for 180°, The codes for angles between 181° to 359° will be determined by taking the ‘twos complements ofthe fiactional binary series forARINC SPECIFICATION 429, PART 1 - Page 6 2.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS 2.1.6 Data Standards (cont'd) COMMENTARY (cont'd) the result of subtracting cach value from 360, Thus, the code for 181" is the twos complement of the code for 179°. Throughout the negative semicircle, which includes’ 180°, the sign'status matrix contains the negative sign For convenience, all binary word ranges in ‘Attachment 2 are shown a5 whole binary numbers father than auch numbers les one least ignficant bit value, Also, the resolutions shown are fpprosimate only” ‘Accurate resohitions can “be determined, if required, by reference to the 1 Salven and mimbers of significant bits for the words of interest It should be noted that in all applications of the twos complement fractional notation, the maximum value of the word, once chosen, cannot be changed by the use of ‘more bits in the data field. The number of bits in the word affects only the resolution of the data, not its Binary Coded Decimal (BCD) data is encoded per the ‘numeric subset of the ISO Alphabet #5 code (Gee ‘Attachment $ to this document) using Bit Numbers 1 through 4 of the sevenbitper-character code. ‘Alpha laumeric data is encoded using all seven bits per character of the ISO Alphabet #5 code and. is ‘wansmitted using the special word format described in Section 2.3.1.3 ofthis document, 2.2 Electrically Related Blements ‘This section describes the digital transfer system elements considered to be principally related to the electrical aspects of the signal cireut. 2.2.1 Transmission System Interconnect A data source should be connected to the data sink(s) by ‘means of a single twisted and shielded pair of wires. The shields should be grounded at both ends to an aircraft around close to the rack connector and at all production ‘breaks inthe cable. COMMENTARY In practical wire line digital information transmission, systems, cable characteristics and electrical mismatches can produce distortion of the digital data pulses, Also, noise due to electrical interference perurbs digital signals. ‘The performance of a digital receiver depends upon the receiver input signal characteristics (data with distortion and noise) and the receiver design, Prior to the selection of the voltage and impedance Parameter st rth nti section ofthis docu the pele tisowtign Ley to be encounterel in tens wilt around them in existing size commercial aircraft ‘wes evaluated and judged to be acceptable for a well- designed receiver. No restiction is placed by this specification, therefore, on the number or Iength of stubs for installations on aircraft no larger than those existing, ¢g..B 747. See Appendix A to this document for a report of this investigation. Tests have shown that some receivers continue decoding data properly when one side of the transmission line is open or shorted to ground. When. this condition exists noise immunity dacreases and intermittent operation may occur. Users desire protection against non-annunciated system operation in this mode. This protection may consist of additional circuitry to detect and annunciate the fault, of 10 increase the recsiver threshold to above 5.5 volts, ‘which is the maximum signal level under this one-wire fault condition. Most_ ARINC Characteristics now contain text specifying that DITS teceivers should discontinue operation when the voltage thresholds fall into the undefined regions between “Null” and “Hi” or “Null” and “Lo,” Manufacturers building DITS receivers are urged to incorporate this feature in their citeuitry wiiether i is to be used in ARINC 7XXseries equipment or Non-ARINC devices, Modulation RZ bipolar modulation should be used. This is tri-level State modulation consisting of “HI,” “NULL” and “LO” states. 2.23 Voltage Levels 2.2.3.1 Transmitter Voltage Levels ‘The differential output signal across the specified output terminals (balanced to ground at the transmitter) should be as given in the following table when the tansinitter is open circuit: HIG) | NULLG@) | Low Line A to +10 #10 Line B 0 405 -10 +10 $408 +5 205 ot os edot ARINC SPECIFICATION 429, PART 1 - Page 7 2.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS 2 Ressiver Voltage Levels The differential voltage presented at the receiver input terminals will be dependent upon line length, stub configuration and the number of receivers connected, In the absence of noise, the normal ranges of voltages presented to the receiver terminals (A and B) would be: In practice, these nominal voltages will be perturbed by noise and pulse distortion, Thus, receivers should associate the following Voltage ranges with the three states indicated cH 46sVt0 BV “NULL” 423V10-25V “LO” -6.5V 10-150 COMMENTARY. Receiver reaction is currently undefined herein for ‘voltages that fallin the range just above and below the ‘Null” range, Respective equipment characteristics should be feferenced for desired receiver response in this range. However, it is desirable that all DITS receivers will discontinue operation when the voltage levels fall into the undetined regions. Manufacturers are urged, as new equipment is developed, to “desian in” the rejection capability The opinion is held by some peopl that conditions on transmission lines wil’ be ‘encountered ‘which will equite receivers to operate with less than the above defined ‘minimum difference of 4OV between the NULL and Hl and NULL and LO states. Receiver designers are encouraged to investigate the possibilities and problems of working with a minimum {iference of 1 volt berwcen these states and to report their findings. ‘Receiver input common mode voltages (terminal A to ground and terminal B to ground) are not, specified because of the difficulties of defining ground with any satisiactory degree of precision. Receiver ‘manufacturers are encouraged to work with the differential input voltage (Line A to line B) and not line- To-ground voltages 2.24 Impedance Levels 2.24.1 Transmitter Output Impedance The transmitter output impedance should be 75 45 ohms, divided equally between line A and line B to provide an Jimpedance balanced output. This output impedance should bbe. present for the “HI.” “NULL” and "LO" transmitter ‘output conditions and also during transitions between these levels. COMMENTARY. The output impedance of the transmitter is specified as, ' obims to provide an approximate match to the characteristic impedance of the cable. The match can only be approximate due to the wide range of characteristic impedances which may be encountered due to the variety of conductor wire gauges and insulation properties. Measurements on a few samples, of wire showed a spread of characteristic impedance of 63 to 71 ohms. An extrapolation over the wire gauges, 20 to 26 for wrapped and extruded insulation indicate an expected characteristic impedance spread of 60 to 50 ohims approx. Twisted shielded wire specifications do not control the characteristic impedance of the cable, thus future developments in insulation techniques may result in cables having characteristic, impedances outside the range estimated. 22.42 Receiver Input Impedance ‘The receiver should exhibit the following characteristics, measured atthe receiver input terminals: Difierential Input Resistance Ry ‘Differential Input Capacitance C,= SOpF maximum. Resistance to Ground Ry and Re> 12,000 ohms Capacitance to Ground Cz and Co <5 ‘The total receiver input resistance including the effects of R,, Re 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 to fone digital data bus and each receiver should incorporate ‘solation provisions to ensure that the occurrence of any reasonably probable failure does not cause loss of data to the others. See Attachment 4 to this document for a pictorial representation of the input and ouput cireuit standards, COMMENTARY. ‘The above characteristics apply to differential amplifier receivers. Opto-isolator_technolozy is, progressing and may soon find application in digital data receivers. Opto-isolator receivers impose slightly greater loads on data buses than differential amplifier receivers and the way in which they are characterized is. different. It s probable, however, that a future revision of this Specification will include material specifically related to their use 2.2.8 Fault Tolerance 2.2.5.1 Receiver Extemal Fault Voltage Tolerance Receivers should withstand without sustaining damage the following steady-state voltages being applied to their terminals, superimposed upon a normally operating bus. Operation within specification limits is not required under these conditions. 8, 30 Vac RMS applied across terminals A and B, or , 229 Vde applied between terminal A and ground, or ¢. 429 Vde applied between terminal B and ground, ot et otARINC SPECIFICATION 429, PART 1 - Page 8 2.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS 2.2.5.2 Transmitter External Fault Voltage ‘Transmitter failures caused by external fault voltages should aot cause other transmitters Gr other circuitry in the unit to function outside of their specification limits or to fai 2253 TransmitterEstemal Fault Load Tolerance ed ot Transmitters should indefinitely withstand without sustaining damage a short circuit applied: 4. across terminals A and B, or ». fiom terminal A to ground, or «. from terminal B to ground, or d. band c above, simultaneously 2.2.6 Fault Isolation 2.2.6.1 Receiver Fault Isolat Each receiver should incorporate isolation provisions to ensue that the occurence of any reasonably probable intemal LRU or bus receiver failure does not cause any input bus to operate outside ofits specification limits (both undervoltage or overvoltage). 2.2.6.2 Transmitter Fault Isolation Each transmitter should incorporate isolation provisions to censure that it does not under any reasonably probable LRU fault condition provide an output voltage in excess of 4. avoltage greater than 30 Vac RMS between terminal A and B, or ,areater than =29 Vde between A and ground, or . ateater than =29 Vee between B and ground, Logic Related Elements ‘This section describes the digital transfer system elements considered to be principally related to the logic aspeets of the signal circuit 2.3.1 Digital Language 23.1.1 Numeric Data ‘The Mark 33 DITS should accommodate numeric data encoded in two digital languages, (i) BNR expressed in ‘vos complement Sractional notation and (3) BCD per the rnumerical subset of ISO Alphabet Number 5 (see Attachment 5 to this document). An information iter encoded in both languages will be assigned a unique address for each (see Section 2.1.3 and Attachment 1-1) Word formats are illustrated in Attachment 6 to this document 23.1.2 Discretes In addition to handling numeric data as specified above, the Mark 33 DITS should also be capable of accommodating | discrete items of information either in the unused (pad) bits ff data words or, when necessary, in dedicated words. Any discrete information contained in a numeric data word assigned a label in Attachment 1-1 is specified in the definition for that word in Attachment 6 The rule to be followed in the assignment soft bits to discrete in mumeric data words is 10 start with the least significant bit of the word and to continue towards the most significant bit available in the word, Atachment 6 shows its against the background ofthe generalized word structure There are two types of discrete words. These are gencral purpose discrete words, and dedicated discrete ‘words. Seven labels (270 XXX-276 XXX) are assigned to the general purpose words in Attachment 1-1. These words should be used in ascending label order (starting with 270 XXX) when the system receiving the data can identify its source by reference to the port at which it arrives, “Maintenance Data (General Purpose) ‘The general purpose maintenance words are assigned labels in sequential order as are the labels forthe general purpose discrete words, The lowest octal value label assigned to the maintenance words should be used when only one maintenance word is wansmitted. When more than one ‘word is transmitted the lowest octal value label should be used first and the other labels used sequentially until the message has been completed. The general purpose maintenance words may contain discrete, BCD or BNR sumeric data but should never contain ISO Alphabet ‘Number 5 messages. The general purpose maintenance words should be formatted according to the layouts of the corresponding BCD/BNRidiserete data words shown in ‘Attachment 2 23.13 23.14 AIMData ‘The information previously contained in this section is no longer applicable to ARINC Specification 429. For reference pusposes, the section header is retained and the original contents of this section ate located in Patt 3 of this Specification. 23.1.5 File Data Transfer ‘This section previously described a character-oriented file data transfer protocol. This definition was used as guidance for the character-oriented file transfer protocol descriptions incorporated into many ARINC equipment characteristics. ‘The original contents of this section are located in Part 3 of this Specification. ‘The protocol defined in Part 3 is prefered for new: application ‘The purpose of this bit-oriented communications protocol is to provide for the transparent twansfer of data files using the ARINC 429 data bus. COMMENTARY “The data transparent protocol described in Part 3 was, developed in order to facilitate the communications of the ACARS Management Unit (MU) and the Satellite Data Unit (SDU)..Its viability as @ universal protocol was recognized by the Systems Architecture and Interfaces (SAI) Subcommittee, which recommenced i igtsion heen a the standard means of fe daa ‘ransfer: ot en elselt els os ARINC SPECIFICATION 429, PART 1 - Page 9 2.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS The process, for determining the protocol (charactet~ oriented or bit-oriented) to be used in the interaction between to units, where this information is not pre- determined is described in Patt 3 of ARINC 428. 23.15.1 Bi ented Protocol Determination The ALO word should be sent by any system which supports the bitoriented Link Layer protocol just after the system powers-up, or performs a revinitialization for any reason. The ALO/ALR protocol process may also be used when a bitoriented Link Layer protocol system needs to determine if any of its interfaces support the bit-oriented protocol. All systems which support the Link Layer bit- Oriented protocol must be able to respond tothe initiation of| this process, Attachment 11C of Part 3 to ARINC 429, show's the ALO and ALR word formas. ‘When a system with a bitoriented Link Layer protocol has the need to make this determination, it should construct the ALO word and transmit this word to the device in question. “The system should then wait for a maximum period of time defined by Ty, Ifthe device in question has not responded within Tz, the initiating system should initiate another ALO ‘word and again delay up to Ty, An initiating system will attempt a maximum of Nz ALO werd operations before declaring the device in question as “Not bit-oriented” or “Not able to respond.” 2.3.2 Transmission Order The Least Significant Bit (LSB) and Least Significant Character (LSC) of each word should be transmitted first. It may be noted thatthe least significant bit of the word is the ‘most significant bit of the label and that the label is transmitted ahead of the data in each case. This “reversed label” characteristic is a legacy from past systems in which the oval coding of the label field was, apparently, of no 2.33 Data Bit Encoding Logic ACHI? state after the beginning of the bit interval returning to 2 “NULL” state before the end of the same bit interval signifies a logie “one.” A“LO” state affer the beginning of th bit interval returning to 2 “NULL” state before the end of the same bit interval signifies @ logic “zero.” ‘This is represented eraphically in Attachment 7 to this document. 2.3.4 EmorDetection/Correction ‘The last bit of each word should be encoded such that word parity is rendered odd to allow error detection in receivers, Note that the parity calculation encompasses all 31 label and information bts ofthe word. COMMENTARY. Air tansport industry experience with digital information transfer systems predating the Mark 33 DITS has shown that the twisted shielded pair of wires can be regarded as a high snteanity link unlikely to introduce bit errors into the data passing through it. Tt is for this reason that no means for error correction are specified in this document. The error detection capability specified above may be used as desired in receiving terminals, BNR data, for example, may be checked for parity by reference to the binary state of Bit Number 32 of each word. Also, the data may be submitted to reasonableness checks, BCD may be mates fo scmnnblten chess BCD. dhe intended for human consumption in the cockpit is normally smoothed before transmission, to ensure tolerable levels of display jier. As this process eliminates any obviously wild data points, the need for further error detection is questionable. As pointed out in the Commentary following Section 2.1.2 of this document, the pariy bit was added to the BCD word for reasons related fo BCD/BNR transmitter hardware commonality, not because a need for it existed for error detection. 24 Timing Related Elements ‘This section describes the digital data transfer system clements considered to be principally related to the timing aspects ofthe signal circuit 24.1 BitRate 24.1.1 High Speed Operation “The bit rate for high speed operation of the system should bbe 100 kilobits per second =14%. 24.1.2 Low Speed Operation “The bit sate for low speed operation of the system should be within the range 12.0 to 145 kilobits per second. The selected rate should be maintained within 1%. NOTE: High bit rate and low bit rate messages will not be intermixed on the same bus. COMMENTARY Although the bit rates specified above should be held within “the stated tolerances over the long term, individual bit lengths may fall outside the limits expected from these tolerances. Bit symmetry and jitter should be within the tolerances specified in Attachment 8 ‘Also, notwithstanding the RET performance of the ARINC 429 DITS reported in Appendix 1 to this document, system designers are advised to avoid selection of 15.6 kilobits per second for low speed operations and precisely 100 kilobits per second for high speed operations to ensure that the system is not responsible for interference to LORAN C systems with which the aireraft might be equipped. 2.42 Information Rates ‘The minimum and maximum transmit intervals for each stem of information transferred by the Mark 33 DITS are specified in the tables of Attachment 2. Words with like labels but with different SDI codes should be treated as ‘unique items of information. Each and every unique item of information should be transmitted once during an interval bounded in length by the minimum and maxinaum os Je osos ARINC SPECIFICATION 429, PART 1 - Page 10 2.0 DIGITAL INFORMATION TRANSFER SYSTEM STANDARDS 24.2 Information Rates (comt'd) values specified in Attachment 2. Stated another way. a word having the same label and four different SDI codes should appear on the bus four times (once for each SDI code) during that time interval. COMMENTARY There are no values given for reffesh sates in this Specification, However, it is desirable that data be refreshed at least once per transmission. Those data actually requiring long processing times or a large ‘number of samples are the only types not expected to be refreshed with every transmission. Discretes contained within data words should be transferred atthe bit rate and repeated atthe update rate ofthe primary data, Words dedicated 10 discretes should be repeated continuously atthe rates defined in Attachment 2. COMMENTARY ‘The time intervals between successive transmissions of a given BCD word specified in table 1 of Attachment 2 to this document are, in general, too short forthe signal to be of use in driving a display device ditectly. If the signal was so used the least significant character of the display, would change too rapidly for human perception, Considerations other than uman factors demand the time intervals specified. Thus, display designers should incorporate into their devices means for selecting those words to be used for updating the dlsplay from the greater quantity delivered. 243 Clocking Method Clocking is inherent in the data transmission, The identification of the bit interval is related to the initiation of either a “HI” of “LO” state fiom a previous “NULL state ina bipolar RZ code, 24.4 Word Synchronization ‘The digital word should be synchronized by reference to a ‘zap of four bit times (minimum) between the periods of ‘Word tansmissions. The beginning of the fist wansmitted Sit following this gop signifies the begining of the new 245 Timing Tolerances ‘The wavelorm timing tolerances should be as shown in Attachment § to this document, COMMENTARY. RF interference radiated by the Mark 33 DITS using the waveform characteristics specified in this section hhas been shown not to exceed that permitted by Figure 21-S of RICA Document DO-160, “Environmental Conditions and Test Procedures for Aitbome Electronic‘Electrical Equipment and Instruments.” Also, conducted RF interference is within the limits specified in Figure 21-2 of DO-160. Appendix 1 to this document refersARINC SPECIFICATION 429, PART 1 - Page 11 3.0 MARK 33 DITS APPLICATIONS NOTES 3.1 Raslio Systems Management One special application of the Mark 33 DITS is to radio systems fequency selection and function switching The following paragraphs set forth the rules which should be followed in the application of the DITS to ensure interchangeabilty of radios and control sourees. 3.1.1 Word Format and Digital Language ‘The standard DITS 32-bit BCD word should be used, of which Bit Numbers 1 through § constitute the label, Bit Numbers 9 and 10 are reserved for a sourceidestination identifier code, bit ‘Numbers 11 through 29 constitute the data, Bit Numbers 30 and 31 form the sign/status matrix and Bit Number 32 is the ‘word parity bit. The data field should contain the frequency to which the radio defined by the label field isto tune encoded in BCD. characters, together with the discretes required for function switching for that radio. Attachment 6 shows how the ‘word should be structured for each radio system requiring the DITS management service 3.1.2 Update Rate ‘The nominal update rate for all radio systems management ‘words should be five times per second 43.1.3 Sign/Status Matrix Since sign is not a characteristic of radio systems management information, the normal states of the sign/status matrix bits will be binary “Zeros.” However, the radios should recognize the codes for “functional test” ‘and “no computed data,” (see Seotion 2.1.5 of this document). They should interpret the former as an instruction to perform a functional test or functional test sequence. They should regard the later as an instruction to remain tuned to the ffequency contained in the lust valid word received until either another valid word is, decoded or ther primary power is removed. 3.14 Frequency Ranges and Switching Funetions 3.141 ADE Frequency Range 190k te 1750 Fregoany Selection Increment! 0 Ske Characters encode in DITS werd: 10D0KES, 100K, 10K Sovtehing Functions 5k onol BFO ent ADP ANT mode sleeion 3.14.2 DME Frequency Range (VORILS) 108 00M» 135 95MEe Frequency Seletion Increment! SEE (worms) (Character encoded inDITS word: 10M, tMhe, 01M DosMe (VOR LS ont) (00M characteris fe VORILS, JME characer limited io 7) VORTSMES Frequeey, DME modes, Digested Frequency Number, Display Coawol| Switching Functions: Note: The ATC Trang 3.143 HE Communications Frequency Range 200 Ne Frequency Seeenon Increment: tkHzor He Characters encoded in DITS words: 10M, IME 0 IME Swathing Faction: USBLSB moée sseenon SBIAM made secon Note: Two words may be transmitted for HF frequency selection to facilitate frequency resolution of 0.1KEZ. 3.144 Ls Frequency Range 108 ooo 111 SsNee Frequency Seeenon Increment Characters encoded in DITS words: 10MB, 1M 0 1M 001M, LOOM characters slays dein 1) Switching Function: None 3.14.5 VORALS Frequency Range: 108.00 Nieto 117 95MHe Frequency Seleeson remax SOME Characes encoded in DITS words: 10M, IME 0 IMs, 001M, (oN crate says decal 1) Switching Function: ISMode 3.14.6 VE Communications 117 975M 137 000M ; 2542 33182 Jer 10MHz, 1M, 01MM, 001ME, (CLOONErcharcter aay deci) Swtcing Finstions Nene 3.1.47 ATC Transponder ler operates on two frequencies (one receive and one transmit) whieh do not require selection Reply code. selection, however, is required and it is this that the Mark 33 DITS accommodates). Reply Code Ranges: 0-Tin oer independent mous Coe increment 1 decimal pe roop Numterofchancien ended ALL in DIES wor ent Pate Select, Alki Reporting On Of, Altre Source Select, Xp Select (reseed) VFR ER Sec (oer, JS FMC apo let eserves). Switching Fanctions