throbber
" é
`
`7’.
`
`L Ah. N\cf%¢'I:IAI=fA‘Cj7EiRiI#siTj:C»is;
`
`,-
`
`;
`
`_
`" ‘L/.
`*2‘
`~.
`.,_
`4
`I
`7
`____;';
`.
`‘

`\ /I;
`A / pususngnz» *_EcEMB_ER~30, 1994
`_
`‘I
`J ,
`, V.7_\
`I
`-—.
`—V
`N5
`'
`
`3
`
`;__/
`
`,
`
`'-
`
`'
`
`,.
`
`, Au"Al2,I/_l,§lG'r'_£:oou_g_:ENT
`,.Pi:pared1:y,
`,
`'
`V
`-‘,
`V I
`/T" AIRLINES EIJECTRGINIC ENGINEERING c\gJMl',r1|'I'l'EE
`Pub/llshgd Igy r
`_
`=3 ,
`'
`-2
`u

`'AERQNAUTICAL R_Ap1o. Lac. »
`@551 RIVA ROAD. AJSINAFPUS. MRRYMND 2140.1,
`
`'
`
`11
`
`BOEING
`Ex. 1040, p. 1
`
`

`
`submitted by various
`is based on material
`This document
`participants during the drafting; process. Neither AEEC nor
`ARINC has made any determination whether these materials could
`be subject to claims of patent or other proprietary rights by third
`parties, 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 hereof ‘as is“ and be subject
`to this
`
`disclaimer.
`
`BOHNG
`BOEING
`Ex. 1040, p. 2
`Ex.1040,p.2
`
`

`
`Copyright” 1992. by
`AERONAUTICAL RADIO, INC.
`2551 Riva Road
`Annapolis, Maryland 21401
`
`ARINC CI-IARACTERISTIC 753”
`
`HF DATA LINK SYSTEM
`
`Published: December 30, 1994
`
`-Prepared by the Airlines Electronic Engineering Committee
`
`Chamcteristic 753
`
`Adopted by the Airlines Electronic Engineering Committee: October 20, 1994
`
`Adopted by the Industry: December 9, 1994
`
`BOEING
`BOEING
`Ex. 1040, p. 3
`EX. 1040, p. 3
`
`

`
`EQEEEKHD
`
`Activities of AERONAUTICAL RADIO, INC. (ARINC)
`
`and the
`
`Purpose of ARINC Characteristics
`
`Aeronautical Radio, Inc. is a corporation in which the United States scheduled airlines
`are the principal stockholders. Other stockholders include a variety of other air transport
`companies, aircraft manufacturers and non-U.S. airlines.
`
`Activities of ARINC include the operation of an extensive system of domestic and
`overseas aeronautical land radio stations, the fulfillment of systems requirements to accomplish
`ground and airborne compatibility, the allocation and assignment of frequencies to meet those
`needs, the coordination incident to standard airborne communications and electronics systems
`and the exchange of technical information. ARINC sponsors the Airlines Electronic Engineering
`Committee (AEEC), composed of airline techni.cal personnel. The AEEC formulates standards
`for electronic equipment and systems for the airlines.
`The establishment of Equipment
`Characteristics is a principal function of this Committee.
`
`An ARINC Equipment Characteristic is finalized after investigation and coordination with
`the airlines who have a requirement or anticipate a requirement, with other aircraft operators,
`with the Military services having similar requirements, and with the equipment manufacturers.
`It is released as an ARINC Equipment Characteristic only when the interested airline companies
`are in general agreement. Such a release does not commit any airline or ARINC to purchase
`equipment so described nor does it establish or indicate recognition of 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 Characteristic. An ARINC Characteristic
`has a twofold purpose, which is:
`
`(1)
`
`(2)
`
`To indicate to the prospective manufacturers of airline electronic equipment the
`considered opinion of the airline technical people, coordinated on an industry
`basis, concerning requisites of new equipment, and
`
`in the
`To channel new equipment designs in a direction which can result
`maximum possible standardization of those physical and electrical characteristics
`which influence interchangeability of equipment without seriously hampering
`engineering initiative.
`
`BOHNG
`BOEING
`Ex. 1040, p. 4
`Ex.1040,p.4
`
`

`
`ARJNC CHARACTERISTIC 753
`TABLE OF CONTENTS
`
`E
`
`SUBJECT
`
`
`
`_9AuMHommpppmmHoUI.hLi)[~.)i—ntor-—I
`
`
`
`2.
`
`2 2
`
`.
`2.
`2.
`2.
`2.
`2.
`2.
`
`INTRODUCTION
`Purpose of this Document
`Relationship to Other Documents
`System Overview
`Airborne HFDL System Configuration
`Ground System Configuration
`Terms
`
`Interchangeability
`Regulatory Approvals
`
`INTERCHANGEABILITY STANDARDS
`Introduction
`
`Form Factor, Connector, and Index Pin Coding
`Standard Interwiring
`Power Circuitry
`Primary Power Input
`Power Control Circuitry
`Common Ground
`Internal Circuit Protection
`Abnormal Power
`
`System Functions and Signal Characteristics
`Environmental Conditions
`Cooling
`Grounding and Bonding
`Standardized Signalling
`ARINC 429 DITS Data Bus
`Standard "Open"
`Standard "Ground"
`
`Standard "Applied Voltage" Output
`Standard Discrete Input
`Standard Discrete Output
`Standard Program Pin Input
`
`SYSTEM DESIGN
`Introduction
`
`System Design
`AOC and ATS
`Other Services
`
`HFDL Avionics Components
`HF Data Radio
`HF Data Unit
`HF Data Link Control Functions
`Optional Additional Components
`Central Maintenance System
`Analog Data Operation
`Interlocks on Dual HFDR Systems
`HFDR and HFDU Modes of Operation
`HFDR Mode Select
`HFDU/I-IF Transceiver Combination Mode Select
`ARINC 719 HP Transceiver Controlled by
`Discretes
`
`ARINC 719 HF Transceiver Controlled by
`ARINC 429 Words
`ARINC 559A HF Transceiver
`
`HF DATA RADIO DESIGN
`Introduction
`Transceiver
`
`Tuning
`Frequency Switching Time
`Transmitter - Receiver Interaction
`Transmit to Receive Turnaround Time
`
`tQt~Jk~JhArdr—i—i--IL-
`
`
`
`i—3§i)i|i|—3}--\|—|I-II-H-31-||d|d|—'|—'CVOC\D\O\DOOOOO0OOOOO0--I‘--J‘--J‘--I‘--I‘-~l'--IIO\G\UI§hUIU|UIUI'J\-I5-I8-b-B-P-H-D-3-I>~b)U)LrJLD
`
`BOEING
`BOEING
`Ex. 1040, p. 5
`EX. 1040, p. 5
`
`'--30\U'I-hLr)l\H—-
`
`
`
`L):--Italks)!--I{Jr-I
`IQEQD-‘t—‘IONlxlldldLL0bL
`
`22
`
`.
`2.
`2.
`2.
`2.
`2.
`2.
`2.
`2.
`2.
`2.
`2.
`
`
`
`3.
`3.
`3.
`3.
`
`3 3 3
`
`.
`3.
`
`3 3
`
`.
`3.
`3.
`
`3 3 3 3
`
`.
`3.
`
`sssssss99.......PwNN-o99ooommssswwwwvwwwoPPPPPPPW““°“PPP*
`
`

`
`Ii
`
`3*’ M
`
`
`
`eseeesees+++s+++++s++++++++++++++9sassesessseesssesesssssseses@9999asasaaesewwwwmsesss9ssseesees+999ssewwwwwwwwwwwwwwwwwwwwv
`
`4999bG%%¥s¥b“F%%rr-LflI~Jr-L0t~Jb---FhLa-‘lt-.Ib--U1-Fhla3I~JI-~\
`
`
`
`
`flHHH*““*WPP““ew~—w~999ewn99wwamewwww~—
`
`
`
`-fl-{.oJl--3*-'I‘~JI-t.~7ItdI---.'lO\UI~h-l.oJt\J=--
`
`ARINC CHARACTERISTIC 753
`
`TABLE OF CONTENTS
`
`SUBTECT
`
`Receive to Transmit Turnaround Time
`Transmitter
`
`Power Output
`SSE Suppressed Cartier
`SSB Full Carrier (AME)
`Tune Power
`VSWR Tolerance
`
`Transmit Duty Cycle
`Frequency Stability
`Phase Stability
`Audio Input
`Input Level
`Audio Processing and Modulation limiting
`Frequency Response
`Transmit Audio Distortion
`Transmitter Keying
`Occupied Spectrum
`Interrnodulation Distortion
`Harmonics
`Non-Harmonics
`
`Tone Tuning Signal
`Receiver
`Sensitivity
`Selectivity
`SSB Suppressed Carrier
`Amplitude Modulated Equivalent (AME)
`Group Delay
`Frequency Stability
`Spurious Responses
`Audio Output
`Source Impedance
`Gain
`
`Frequency Response
`Distortion
`I-Ium Level
`Phase Shift
`Phase Stability
`Automatic Gain Control
`Voice Mode
`Data Mode
`
`Settling Time
`RF Sensitivity Control andlor Squelch Control
`SSB Mode Linearity
`SELCAL Output
`Frequency Response
`Distortion
`Phase Shift
`
`Differential Phase Delay
`I-{FDR — System Interface
`HF Voicel'Data Mode Switching
`HFDR Voice Transceiver Tuning
`ARINC 719 Style I-IF Transceiver Tuning
`ARINC 559A Style: HF Transceiver 'l\1ning
`I-IF Voice Transceiver Keying
`I-IF Antenna Coupler Tuning Initiation
`ACARS MUICMU Interface Functions
`Voi-::efData Mode Switching Functions
`Other Interfaces
`Aircraft Position Data
`Universal Coordinated Time (UTC) Data
`ICAO Address Data
`Maintenance Data
`
`iv
`
`PAGE
`
`11
`12
`
`12
`
`n----u-ap—-y--:-Ib-a—nv—-:-r—n>-In-r--I-IIb—>—II-I-AI-I--Inb—Irur—-r-—an—-:-»un—In—nr—una>-b-ar-huu—Ip—ar-n-ahdhavuwat--to--r-I--I-o-an--I--u—n—->-up--II-n--I
`
`BOEING
`BOEING
`Ex. 1040, p. 6
`EX. 1040, p. 6
`
`

`
`
`
`
`
`tQ|—-bJ|—IU)kQI--A
`
`ARINC CI-IARACTERISTIC 753
`TABLE OF CONTENTS
`
`SUBJECT
`
`Maintenance System Identification
`Data Loader
`Status Indication Discretes
`HFDL DATA LINK LOST Indication Discrete
`HFDR FAULT Indication Discrete
`Built-In Tests
`
`Air;’Ground Discrete Input
`Transmit Inhibit Discrete Input
`Key Event Output
`SDI Input Pin Definition
`HF Test Enable Discrete Definition
`Chopper Control
`Strap Even Parity
`ICAO Strap Even Parity
`
`I-IF DATA UNIT DESIGN
`Introduction
`
`I-IF Voice/Data Mode Enable Switching
`Air/Ground Data Transmission Functions
`HF Transceiver Audio Interface
`Transmit Audio Waveform
`HF Transceiver Keying
`Air/Ground Data Receive Functions
`HF Transceiver Audio Interface
`Receive Audio Waveform
`HF Transceiver Tuning
`ARINC 719 HF Transceiver Tuning
`ARINC 559A I-IF Transceiver Tuning
`HF Antenna Coupler Tuning Initiation
`Air/Ground Data Transfer Protocol
`ACARS MUICMU Interface Functions
`Other Interfaces
`Aircraft Position Data
`
`Universal Coordinated Time (UTC) Data
`ICAO Address Data
`Maintenance Data
`
`Maintenance System Identification
`Data Loader
`
`AirfGround Discrete Input
`MU/CMU Interface Speed Select
`Transmit Inhibit Discrete Input
`SDI Inputs
`Strap Even Parity
`Status Indications
`HF DATA LINK LOST Indication Discrete
`HFDU FAULT Indication Discrete
`Built-In Tests
`
`DATALINK CONTROL FUNCTIONS
`Introduction
`HFDCF Functions
`HF Voice/Data Select
`Programmable Functions
`I-IF Datalink ON/OFF Switch
`I-IF Datalink DATA LINK LOST Indication
`I-IFDUII-IFDR FAULT Indication
`HF Datalink Status Display
`HFDU Mode Select
`
`HF Frequency Port Select
`RF Sensitivity or Squelch Control
`
`BOEING
`BOEING
`Ex. 1040, p. 7
`EX. 1040, p. 7
`
`IE
`
`D—|
`
`4 4 4
`
`.
`4.
`4.
`
`....:"*:'*:'-‘-:‘-“-.‘*.4‘.~°*:F*:“
`
`:5'5'5‘.‘°)°.“°.‘°§°§°}°§°§°§°§°‘°°°“‘°‘E"$“°‘:‘°*:"*"‘P’P’!'°‘*”""‘°F"P‘?‘.°“F".°‘.°‘.°‘?‘P‘?‘.°‘.°‘9‘"naaaoozswnnmee
`
`
`
`5.
`5.
`5.
`5.
`5.
`
`5 5 5
`
`.
`5.
`5.
`5.
`5.
`5.
`5.
`5.
`5.
`5.
`5.
`5.
`5.
`5.
`5.
`5.
`5.
`5.
`5.
`5.
`5.
`5.
`5.
`5.
`5.
`
`
`
`D—|\DOO'--.iD'\Ul.-P-F~UJbJI—\0;.
`
`I\J)--4
`
`6.0
`6.1
`6.2
`6.2.1
`6.2.2
`6.2.3
`6.2.4
`6.2.5
`6.2.6
`6.2.7
`6.2.8
`6.2.9
`
`

`
`ARINC CHARACTERISTIC 753
`
`TABLE OE CONTENTS
`
`IE
`
`El
`
`PAGE
`
`iiLLL L
`
`i.n1t:'mi~.nI—-i..oioi—-
`
`hhwmm
`b-db-|l—lI-fil-II-I
`
`qqqqqqqqqqqqqqqq
`
`HfiflqfiflflfiflqflomnwppnypuwemacmnbhhnnahbhAnnhhhhbhbbbhhhbLn:zi.mo.—-PPPPPPPPPPPPPP?
`
`
`v'...ai.»aL»>L>i.»i.s:i~JiaixJi~J'''°''
`
`
`ATTACHMENTS
`
`ANTENNA SYSTEMS
`Introduction
`Antenna
`
`HF Antenna Coupler
`Matching
`Frequency Coverage
`Power Handling Capability
`Tune Mode
`
`Interwiring
`Multiwire Serial Interface (MSI)
`Physical Layer
`Physical Medium
`Serial vs Parallel Interface Selection
`Detection Scheme
`Parallel Interface (ARINC 719) Definition
`Multiwire Serial Interface (ARINC 753
`or MSI) Definition
`Link Layer Protocol
`Link Protocol Sequencing
`Link Protocol Message Description
`Link Protocol Timings
`Control Protocol
`Sequencing
`Aborting Commands
`RF Operations
`Control Protocol Command and Request Messages
`Example Communication Sequence
`Tuning Time
`
`PROVISIONS FOR AUTOMATIC TEST EQUIPMENT
`General
`
`ATE Testing
`
`PROVISIONS EOR BUILT—l.N TEST EQUIPMENT {§I’I‘E)
`Introduction
`BITE Interfaces
`OMS Interfaces
`Character-Oriented CFDS Interfaces
`Bit-Oriented CFDS Interfaces
`MUICMU BITE Interfaces
`I-IFDRXI-IFDU Equipment Identification Word
`Bite Presentation
`Fault Monitor
`Self-Test Initiation
`Monitor Memory Output
`
`Airborne Subsystem Block Diagram
`HFDR Avionics Configuration A
`I-[FDR System Block Diagram
`I-[FDR Standard Interwiring
`HFDR Top Connector Layout
`I-{FDR Middle Connector Layout
`I-IFDR Bottom Connector Layout
`ARINC 600 Size 2 Connector - I-IFDR Rear View
`
`I-IFDU Avionics Configuration B
`(Using ARINC 719 HF XCVR With Discrete
`Voicea'Data Control}
`HFDU Avionics Configuration B
`(Using ARINC 719 HP XCVR With ARINC 429
`Voicel'Data Control)
`
`26
`26
`26
`26
`26
`26
`26
`26
`26
`27
`2'.’
`27
`27
`27
`28
`
`28
`29
`29
`29
`30
`30
`30
`30
`31
`31
`45
`49
`
`S0
`
`S0
`
`5 1
`
`51
`52
`S2
`52
`S2
`S2
`52
`52
`S3
`
`S4
`55
`56
`57-61
`62
`63
`64
`65
`
`66
`
`6')‘
`
`vi
`
`BOHNG
`BOEING
`Ex. 1040, p. 8
`Ex.1040,p.8
`
`

`
`ITEM
`
`ATTACHMENTS
`
`3- 1 C
`
`3-1D
`3-2
`3-3A
`3-3B
`3-3C
`3-3D
`4-1A
`
`APPENDICES
`
`ARINC CI-IARACTERISTIC 753
`
`TABLE OF CONTENTS
`
`SUBJECT
`
`HFDU Avionics Configuration B (Using HF XCVR
`ARINC 559A Type)
`HFDU System Block Diagram
`HFDU Standard Interwiring
`HFDU Top Connector Layout
`HFDU Middle Connector Layout
`HFDU Bottom Connector layout
`ARINC 600 Size 2 Connector - HFDU Rear View
`HF Data Control Panel Standard Interwiring
`HF Data Control Panel Connector Layout
`Coupler Standard Interwiring
`Coupler Connector Layout
`Notes Applicable to Standard Interwiring
`Environmental Test Categories Per DO-160C
`Maintenance System Codes
`USB Selectivity
`Typical Test Procedures
`Typical Message Transfer Diagram
`Coupler CMC Flight Data
`
`HF Transmission Requirements
`ACARS MU-HFDU MSK Interface
`ARINC 429 Control Word Formats for the HFDR
`Documents List
`Acronym List
`
`BOHNG
`BOEING
`Ex. 1040, p. 9
`Ex.1040,p.9
`
`

`
`BOEING
`BOEING
`Ex. 1040, p. 10
`EX. 1040, p. 10
`
`

`
`ARINC CI-IARACTERISTIC 753 7 Page 1
`
`1.0 INTRODUCTION
`
`1.1 Pugpose of This Document
`
`The HFDL system should have two main modes:
`
`form and fit
`the physical
`This document contains
`interface definition and a
`dimensions,
`the electrical
`description of the functional operation of the airborne
`components of the High Frequency Data Link (HFDL)
`communications system. An overview of the associated
`ground system is also provided. The protocols used in
`the HFDL system are defined in ARINC Specification 635
`"I-IF Data Link Protocols".
`
`The intent of this document is to provide general and
`specific design guidance for
`the development
`and
`installation of the airborne equipment. As such,
`this
`guidance covers. the desired operational capability of the
`HFDL system and the standards necessary to achieve
`interchangeability of the airborne hardware. The HP Data
`Link system has various modes of operation which are
`described more fully in Chapters 3, 4 and 5.
`
`COMMENTARY
`
`this
`should note that
`Equipment manufacturers
`document aims
`to encourage them to produce
`maintenance-free,
`high performance
`equipment.
`They are at liberty to accomplish this by the use of
`design techniques they consider
`to be the most
`appropriate.
`Their airline customers are more
`interested in the end result
`than in the means to
`achieve it.
`
`1.2 Relationship to Other Documents
`
`functionality into the
`This Characteristic introduces
`components of the HFDL by way of reference. Many of
`these
`references
`are
`to other Airline Electronic
`Engineering Committee
`(AEEC) documents.
`The
`designer should use the most current version of the
`referenced document unless a specific version is given.
`A list of referenced documents is provided in Appendix D
`for the readers convenience.
`
`1.3 System Overview
`
`The HFDL System consists of the Airborne HFDL
`System Configuration described in Section 1.3.1 and the
`Ground System Configuration described in Section 1.3.2.
`
`1.3.1 Airborne HFDL System Configgration
`
`The HFDL avionics system hardware consists of an I-IF
`Data Unit (HFDU) or an integrated voice/data I-IF Data
`Radio (HFDR). The I-IFDR provides either voice or data
`communications services in a simplex mode on demand.
`The HFDU interfaces with a conventional analog Single
`Side Band (SSB) HF transceiver already installed in the
`aircraft to provide voice or data communications services
`in a simplex mode on demand also.
`This document
`assumes that the airborne components implementing HF
`Data Link are arranged as shown in Attachments 2
`through 4 and that
`they function within the system
`operating rules specified in ARINC Specification 635,
`ARINC Specification 637, and ARINC Specification 638.
`
`— the Data Mode for digital data transmission as
`described throughout
`this document and ARINC
`Specification 635 ,
`
`- the Voice Mode, which is identical in function and
`control as the existing HF Voice Radios, according
`to ARINC Characteristic 719.
`
`As an HF Packet Communications (I-IFPAC) bridge, the
`High Frequency Data Link (HFDL) system is an integral
`part of the I-IFPAC/Aeronautical Telecommunication
`Network (ATN) communications protocol suite. Detailed
`background of HFPAC/ATN can be found in ARINC
`Specifications 635, 637 and 638.
`
`COMMENTARY
`
`The use of the HFDL system (Attachments 2
`through 4),
`for sole means of ATN operation
`depends on the integrity and availability requirements
`set forth by world wide agencies. Aeronautical
`operators planning to implement ATN capability may
`need to install additional equipment.
`
`the HFDL avionics
`Depending on the selected mode,
`system operates with a Communications Management Unit
`(CMU) (see ARINC Characteristic 748), a Management
`Unit (MU) (see ARINC Characteristics 597, 724 and
`7248, and ARINC Specification 618), a Centralized Fault
`Display Interface Unit (CFDIU) (see ARINC Report 604)
`or Onboard Maintenance System (OMS) (see ARINC
`Report 624).
`
`The Aircraft Communications Addressing and Reporting
`System (ACARS) Management Unit
`(MU)
`or
`Communications Management Unit (CMU) is the onboard
`router for the Aeronautical Telecommunications Network
`(ATN). As such, all application messages intended for
`transmission to the ground are sent onboard to the MU or
`CMU, which in—turn has the responsibility to determine
`the most efficient subnetwork over which to transmit the
`packet, and to route the packet accordingly. The MU or
`CMU also implements
`any management protocols
`required to ensure the continued and correct operation of
`the various bridges located onboard the aircraft.
`
`1.3.2 Ground System Configpration
`
`The aeronautical I-IF subnetwork provides air}ground data
`and voice communications capability. Ground service is
`provided by a network of HF ground stations strategically
`located to cover major oceanic air routes as well as
`continental areas.
`
`The HFDL air/ground subnetwork provides primarily
`Airline Operational Control
`(AOC) and Air Traffic
`Control (ATC) data and voice communications services.
`Optional services, FAX and voice patch, may also be
`available at some ground stations.
`
`BOEING
`BOEING
`Ex. 1040, p. 11
`EX. 1040, p. 11
`
`

`
`ARINC CHARACTERISTIC 753 - Page 2
`
`1.0 INTRODUCTION [cont’d1
`
`1.4 Terms
`
`Antenna: Built-In Antenna; not considered as part of the
`I-IFDR
`
`CFDS:
`
`Central Fault Display System
`
`Coupler: Antenna tuning device to match the antenna
`impedance to the 50 ohm coaxial transmission
`line.
`
`I-IF DataNoice
`HFDL: High Frequency Data Link;
`Communication Subnetwork AirfGround.
`
`I-IFDR: High Frequency Data Radio; used for
`airborne HF Transceiver.
`
`the
`
`The HFDU
`I-IFDU: High Frequency Data Unit.
`contains the Modem for the system when the
`Modem is a separate LRU.
`
`OMS:
`
`On-Board Maintenance System
`
`1.5 Interchange-abiligg
`
`System interchangeability, as defined in Section 2.0 of
`ARINC Report 607, "Guidance for Designers of Airborne
`Electronic Equipment“,
`is desired for the I-[FDR and
`HFDU. The standards necessary to ensure this level of
`interchangeability are set
`forth in Chapter 2 of this
`document.
`
`1.6 Regglatogg Aggrovals
`
`all applicable regulatory
`The equipment must meet
`requirements. Manufacturers are urged to obtain all
`necessary information for such regulatory approval. This
`information is not contained in this characteristic, nor is
`it available from ARINC.
`
`BOEING
`BOEING
`Ex. 1040, p. 12
`EX. 1040, p. 12
`
`

`
`2.0 INTERCHANGEABILITY STANDARDS
`
`ARINC CHARACTERISTIC 753 - Page 3
`
`2.1 Introduction
`
`This chapter sets forth the specific form factor, mounting
`provisions, interwiring, input and output interfaces and
`power supply characteristics desired for the HF Data
`Radio and HF Data Unit. These standards will permit the
`parallel, but independent design of compatible equipment
`and airframe installations.
`
`Unit interchangeability is required for the HF Data Radio,
`HF Data Unit, and. Antenna Coupler,
`regardless of
`manufacturing source.
`
`COMMENTARY
`
`In order to achieve the full benefit of the economics
`
`the industry desires that
`offered by these changes,
`any provisions for backwards compatibility with
`earlier generations of HF Communications equipment
`described by ARINC ‘719 be provided as basic
`provisions.
`
`The ARINC 753 transceiver (HFDR) is pin- and function-
`compatible with the ARINC 719 transceiver. When an
`HF Data Radio is installed in an ARINC 719 slot,
`(replacing an ARINC 719 transceiver) it should operate
`with ARINC 719 radio functionality. An HF Data Unit
`attached to this array would be required to obtain I-IF
`Data. Link functionality.
`
`2.2 Form Factor, Connector, and Index Pin Coding
`
`The HFDR and HFDU should comply with the
`dimensional standards in ARINC Specification 600, "Air
`Transport Avionics Equipment Interfaces (NIC Phase 1)“,
`for the 6 MCU and 4 MCU form factors respectively.
`The HFDR and HFDU should also comply with ARINC
`Specification 600 standards with respect
`to weight,
`racking attachments,
`front and rear projections and
`cooling.
`
`COMMENTARY
`
`The only form factor defined in this Characteristic is
`the Modular Concept Unit (MCU) defined in ARINC
`Specification 600.
`Packaging of the HFDR in
`accordance with ARINC Specification 404A was not
`considered desirable.
`However,
`some retrofit
`installations into aircraft racking for ARINC 404A
`equipment are expected.
`
`The HFDR and HFDU should each be provided with a
`low insertion force, Size 2 Shell ARINC Specification 600
`service
`connector.
`This connector, which should
`accommodate service interconnections in its middle plug
`(MP)
`and
`top
`plug
`(TP)
`inserts
`and
`power
`interconnections in its bottom plug (BP) insert, should be
`located on the center grid of the HFDR and HFDU rear
`panel.
`Index pin code 10 should be used for the HFDR.
`Index pin code 20 should be used for the HFDU. The pin
`coding for
`the HFDR and HFDU are depicted in
`Attachments 2-3D and 3—3D respectively.
`
`If bench testing of the HFDR and HFDU with Automatic
`Test Equipment
`(ATE)
`necessitates
`interconnect
`capabilities that are not covered by the pin assignments on
`the service connector set forth in Attachments 2-3A
`through 2-3C and 3—3A through 3~3C (including pins
`TP4-A through TP4D which are designated for unspecified
`ATE function use) an auxiliary connector should be
`provided whose type and location are selected by the
`equipment manufacturer. As this auxiliary connector will
`not be used while the HFDR or HFDU is installed in the
`aircraft,
`it should be provided with a cover to ensure
`protection from damage, contamination, ete., during that
`time. The manufacturer should observe the standards of
`ARINC Specification 600 when choosing the location for
`the connector. Also, other than accommodating the needs
`for equipment identification by the ATE described in
`Section 8 of this document, the manufacturer is free to
`make whatever use of both the service connector ATE
`pins and the auxiliary connector pins he wishes.
`
`COMMENTARY
`
`is specified to permit
`The auxiliary connector
`completion of the interface without recourse to the
`use of individual "test leads" from the ATE, each of
`which has to be clipped, or otherwise secured, to a
`test point on the equipment.
`
`2.3 Standard Interwiring
`
`The standard interwiring to be installed for the HFDR and
`HFDU are set
`forth in Attachments 2-2 and 3-2
`
`respectively. This interwiring is designed to provide the
`degree of interchangeability specified in Section 1.5 of
`this Characteristic.
`
`COMMENTARY
`
`The standardized
`Why Standardize Interwiring?
`interwiring is perhaps the heart of all ARINC
`Characteristics. It is this feature which allows the
`airline customer to complete his negotiation with the
`airframe manufacturer so that the latter can proceed
`with engineering and initial
`fabrication prior to
`airline
`commitment on a
`specific
`source of
`equipment.
`This
`provides
`the
`equipment
`manufacturer with many valuable months in which to
`put
`the
`final
`"polish"
`on his
`equipment
`in
`development.
`
`COMMENTARY
`
`The reader is cautioned to give due consideration to
`the specific notes in Attachment 5 as they apply to
`the
`standard interwiring.
`Manufacturers
`are
`cautioned not to rely on special wires, cabling or
`shielding for use with particular units because they
`will
`not
`exist
`in
`a
`standard
`installation.
`Furthermore, manufactures are encouraged to utilize,
`for ATE purposes, only those pins designated for
`ATE, and not make use of pins not currently defined
`or left for customer definition.
`
`BOEING
`BOEING
`Ex. 1040, p. 13
`EX. 1040, p. 13
`
`

`
`ARINC CHARACTERISTIC 753 - Page 4
`
`2.0 INTERCHANGEABILITY SI ANDARDS §cont’d[
`
`2.4 Power Circuitfl
`
`2.4.1 Primggg Power Input
`
`The HFDR should he designed to accept 115 Vac, 400
`Hz, three phase power. The I-{FDR should be protected
`by a 5 ampere circuit breaker in each phase. The HFDU,
`if installed, should be designed to accept 115 Vac, 400
`Hz, single phase power. The HFDU should be protected
`by a single 2 ampere circuit breaker.
`See ARINC
`Characteristic 413A, "Guidance for Aircraft Electrical
`Power Utilization and Transient Protection".
`
`2.4.2 Power Cogtrol Circuitg/_
`
`The primary power to the HF transceiver should not
`normally be controlled by a master onfoff switch.
`It
`should be noted that no onfoff switches will be needed in
`
`installations. A master on/off power switching
`most
`capability should be provided as an option. When this
`option is selected, power input to the transceiver should
`be accomplished using the pins reserved for switched
`power.
`
`2.4.3 Common Ground
`
`The wires designated as “Common Ground" (or as chassis
`ground) are used for the DC ground return to the aircraft
`structure and may be grounded to the chassis of the
`equipment if the manufacturer so desires. In any event,
`they will be grounded to the aircraft structure. They
`should not be used as common returns for any circuits
`carrying AC currents.
`
`2.4.4 Internal Circuit Protection
`
`the equipment should automatically resume
`conditions,
`normal operation when the frequency andfor voltage
`returns within limits. Set manufacturers should provide
`their own protection. wholly within the equipment against
`the possibility of one of the three AC line circuits being
`interrupted by an aircraft electrical system power phase
`failure in the aircraft. The equipment should not be
`damaged in any way if one phase lead is opened and it is
`desirable the equipment:
`
`(a) continue to operate at reduced power, or,
`
`(la) cease operating entirely, or,
`
`(c) malfunction in such a manner as to make it evident
`to the crew that such a failure has occurred, in order
`to guard against attempted continued operation which
`is not providing satisfactory communications.
`
`5 stem Functions
`
`d Si
`
`Characteristics
`
`A list of the system functions and signal characteristics
`required to ensure the desired level of interchangeability
`for the l-IFDR and HFDU are set forth in Chapters 4, 5
`and 6 of this document and ARINC Specification 635.
`
`2.6 Environmental Conditions
`
`The HFDL Line Replaceable Units (LRUs) should be
`specified environmentally in terms of the requirements of
`RTCA Document DO-160C, "Environmental Conditions
`and Test Procedures
`for Airborne Electronic
`and
`Electrical Equipment and instruments". Attachment 6 to
`this document
`tabulates
`the relevant
`environmental
`categories.
`
`The basic master power protection means for the HFDR
`will be external to the unit and utilize a standard circuit
`
`2.? Cooling
`
`breaker rating. Within the equipment, no master power
`protection means
`is
`to
`be
`provided,
`although
`subdistribution circuit protection is acceptable where the
`set manufacturer feels this would improve the overall
`reliability of the equipment.
`
`these fuses
`If internal protection by fuses is employed,
`should not be accessible when the set is installed in the
`aircraft radio rack, but should be replaceable only when
`the gquipment goes through the service shop.
`
`If such subdistribution circuit protection is by means of
`circuit bfiers, the majority of airlines prefer that these
`be accessible on the front panel of the equipment so that
`they can be reset in service.
`
`2.4.5 Abnormal Power
`
`The I-IFDL equipment should accept power variations
`without adverse effects upon equipment performance.
`Refer to ARINC Report 413A, "Guidance for Aircraft
`Electrical Power Utilization and Transient Protection" or
`ARINC Report 609,
`"Design Guidance for Aircraft
`Electrical Power Systems". The equipment should be of
`such design that it will not be damaged by power supply
`frequencies andior voltages below the minimum or
`exceeding the maximum specified operating voltage and
`frequency, and if operation is interrupted under these
`
`The I-IFDR and HFDU should be designed to accept, and
`airframe manufacturers should configure the installation
`to provide forced air cooling as defined in ARINC
`Specification 600.
`The standard HFDR installation
`should provide an air flow rate of 57.2 kgfhr of 40 °C
`(max.) air and the unit should not dissipate more than an
`average of 260 watts of power. The standard I-IFDU
`installation should provide an air flow rate of 22 kgfhr of
`40 °C (max.) air and the unit should not dissipate more
`than an average of 100 watts of power. The coolant air
`pressure drop through the HFDR should be 25 i 5 mm
`of water and 5 1 5 mm of water through the HFDU at
`standard conditions. The HFDR and HFDU should be
`designed to expend this pressure drop to maximize the
`cooling effect. Adherence to the pressure drop standard
`is needed to allow interchangeability of the equipment.
`Continuous transmitter operation without ARINC cooling
`is permissible as long as the internal blower operates
`continuously and the ambient air temperature does not
`exceed 55°C.
`
`COMMENTARY
`
`Although the I-IFDR and HFDU are packaged in
`accordance with ARINC Specification 600, some
`retrofit installations will be made into aircraft racking
`designed in accordance with ARJNC Specification
`404A. The cooling provisions of these racking
`
`BOEING
`BOEING
`Ex. 1040, p. 14
`EX. 1040, p. 14
`
`

`
`2.0 INTERCHANGEABILITY STANDARDS !cont’d[
`
`ARINC CHARACTERISTIC 753 - Page 5
`
`standards were intentionally established such that
`ARINC 600 equipment would be compatible with
`ARINC 404A racking. Thus, the HFDR and HFDU
`cooling provisions are compatible with ARINC 404A
`aircraft racking.
`
`The HFDR and/or HFDU designer should consider
`that
`the HFDR and HFDU will be expected to
`operate without substantially lower reliability in an
`aircraft installation in which cooling is not available.
`A loss of cooling should not cause total loss of
`functionality, although a partial reduction in output
`power is acceptable.
`
`COMMENTARY
`
`The specified cooling air flow rate is based on an
`estimated average power dissipation. However, it
`should be noted that the power dissipation of the
`HFDR during transmission will be higher than the
`estimated average. Thus, the specified air flow rate
`will be less than the rate recommended in ARINC
`
`Specification
`dissipation.
`
`600
`
`(NIC)
`
`for
`
`the maximum
`
`failures in aircraft due to inadequate
`Equipment
`thermal management have plagued the airlines for
`many years.
`In Section 3.5 of ARINC Specification
`600 they have written down everything they believe
`airframe and equipment suppliers need to know to
`prevent such problems in the future. They regard
`this material as "required reading" for all potential
`suppliers of I-IFDR/HFDU and aircraft installation.
`
`2.9.2 Standard "(_)pen"
`
`is characterized by a
`signal
`The standard "open"
`resistance of 100,000 ohms or more with respect to signal
`common.
`
`COMMENTARY
`
`In many installations, a single switch is used to
`supply a logic input to several LRUs. One or more
`of these LRUs may utilize a pul1~up resistor in its
`input circuitry. The result is that an "open" may be
`accompanied by the presence of +27.5 Vdc nominal.
`The signal could range from 12 to 36 Vdc.
`
`2.9.3 Standard "Ground"
`
`A standard "ground" signal may be generated by either a
`solid state or mechanical type switch. For mechanical
`switch—type circuitry a resistance of 10 ohms or less to
`signal common would represent the "ground" condition.
`Semiconductor circuitry should exhibit a voltage of 3.5
`Vdc or less with respect
`to signal common in the
`"ground" condition.
`
`2.9.4 Standard "Applied Voltage" Output
`
`The standard "applied voltage" is defined as having a
`nominal value of +27.5 Vdc.
`‘This voltage should be
`considered to be "applied" when the actual voltage under
`the specified load conditions exceeds 18.5 volts (+36 Vdc
`maximum) and should be considered to be "not applied"
`when the equivalent
`impedance to the voltage source
`exceeds 100,000 ohms.
`
`2.8 Grounding and Bonding
`
`2.9.5 Standard Discrete Input
`
`The attention of equipment and airframe manufacturers is
`drawn to the guidance material
`in Section 3.2.4 of
`ARINC Specification 600 as well as Section 6 and
`Appendix 2 of ARINC Specification 404A on the subject
`of equipment and radio rack grounding and bonding.
`
`2.9 Standardized Si galling
`
`inputs and outputs from the
`The standard electrical
`systems should be in the form of a digital format or
`switch contact. Standards should be established exactly to
`assure the desired interchangeability of equipment.
`
`Certain basic standards established herein are applicable
`to all signals. Unless otherwise specified the signals
`should conform with the standards set
`forth in the
`subsections below.
`
`2.9.1 ARINC 429 DITS Data Bus
`
`ARINC Specification 429 "Mark 33 Digital Information
`Transfer System (DITS)" is the controlling document for
`data word formats,
`refresh rates,
`resolutions,
`etc.
`Material in this document on these topics is included for
`reference purpos

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket