《ARINC-629P1-5-1999.pdf》由会员分享，可在线阅读，更多相关《ARINC-629P1-5-1999.pdf（166页珍藏版）》请在三一文库上搜索。
1、MULTI-TRANSMITTER DATA BUS PART 1 TECHNICAL DESCRIPTION ARINC SPECIFICATION 629P1-5 PUBLISHED: MARCH 31, 1999 AN A DOCUMENT Prepared by AIRLINES ELECTRONIC ENGINEERING COMMITTEE Published by AERONAUTICAL RADIO, INC. 2551 RIVA ROAD, ANNAPOLIS, MARYLAND 21401 This document is based on material submitt
2、ed by various participants during the drafting process. Neither AEEC nor ARINC has made any determination whether these materials could be subject to valid claims of patent, copyright or other proprietary rights by third parties, and no representation or warranty, expressed or implied is made in thi
3、s regard. Any use of or reliance on this document shall constitute an acceptance thereof “as is“ and be subject to this disclaimer. Boeing is a known holder of patents that apply to ARINC Specification 629.Parties involved with designing equipment to meet this standard are advised that it may be nec
4、essary to license the associated technologies through: Corporate Patent Office Boeing P.O. Box 3700 Seattle, WA 98124-2207 Copyright 1996 by AERONAUTICAL RADIO, INC. 2551 Riva Road Annapolis, Maryland 21401-7465 USA ARINC SPECIFICATION 629-4 MULTI-TRANSMITTER DATA BUS PART 1 TECHNICAL DESCRIPTION Pu
5、blished: April 1, 1996 Prepared by the Airlines Electronic Engineering Committee Specification 629Adopted by the Airlines Electronic Engineering Committee: September 25, 1989 Specification 629-1Adopted by the Airlines Electronic Engineering Committee: August 9, 1991 Specification 629-2Adopted by the
6、 Airlines Electronic Engineering Committee: October 10, 1991 Specification 629-3Adopted by the Airlines Electronic Engineering Committee: October 21, 1994 Specification 629-4Adopted by the Airlines Electronic Engineering Committee: November 2, 1995 ARINC SPECIFICATION 629 TABLE OF CONTENTS ITEMSUBJE
7、CTPAGE 1.0INTRODUCTION1 1.1Purpose of This Document1 1.2Relationship to ARINC Specifications 419 and 4291 1.3ARINC Specification 629 Basic Philosophy1 1.3.1Basic Protocol - Protocol BP1 1.3.2Combined Mode Protocol - Protocol CP2 1.3.3Compatibility/Interchangeability2 1.3.4Data Rate2 1.4Organization
8、of This Specification2 1.5Guidance for Using This Specification2 1.6Effects on LRU Interchangeability3 1.7Environmental Factors3 1.8Related Documents3 2.0BUS DESIGN OVERVIEW4 2.1Classes of Service4 2.1.1Basic Protocol Operation - Protocol BP4 2.1.2Combined Mode Protocol Operation - Protocol CP4 2.1.
9、3File Transfer Data4 2.2Message Transfer Modes4 2.2.1Broadcast Data4 2.2.2Directed Data4 2.3Classes of Data Transfer4 2.4Data Types5 2.4.1Binary Data5 2.4.2Alphanumeric Data5 2.4.3Discrete Data5 2.4.4Extended Binary5 2.4.5Real Numbers5 2.4.6Byte Data5 2.4.7Graphic Data5 2.5Message Timing5 2.5.1Bit R
10、ate5 2.6Error Management5 2.6.1Terminal-to-Terminal Errors5 2.6.2System-to-System Errors5 2.7Bus Integrity6 3.0PHYSICAL LAYER7 3.1Introduction7 3.1.1Section Overview7 3.1.2Scope of the Physical Layer Specification7 3.2System Level Requirements7 3.2.1Special Considerations7 3.3Physical Layer Signalli
11、ng Specification (Terminal Controller to SIM Interface)7 3.3.1Terminal Controller Signalling7 3.3.1.1Bus Quiet Indication7 3.3.1.2Modulation8 3.3.1.3Message Synchronization8 3.3.1.4Wordstring Format8 3.3.1.4.1Label Word Format9 3.3.1.4.1.1Label Word Synchronization9 3.3.1.4.2Data Word Format9 3.3.1.
12、4.2.1Data Word Synchronization9 3.3.1.4.3Error Detection/Parity Bit9 3.3.1.5Inter-wordstring Gap9 3.3.2Terminal Controller-SIM Interface Signals9 3.3.2.1Transmit Waveform Characteristics9 3.3.2.2Receive Waveform Characteristics10 3.3.2.3Collision and Error Indication10 3.3.2.4Physical Bus Quiet Indi
13、cation10 3.3.2.5Wrap Around Delay10 iii ARINC SPECIFICATION 629 TABLE OF CONTENTS ITEMSUBJECTPAGE 3.4Physical Layer Entities12 3.4.1Entity Overview12 3.4.2Current Mode Bus12 3.4.2.1General Characteristics12 3.4.2.2Serial Interface Module (SIM)12 3.4.2.2.1Transmit Function12 3.4.2.2.2Receive Function
14、14 3.4.2.2.3Current Mode Physical Bus Quiet Detection14 3.4.2.2.4Waveform Integrity Checking14 3.4.2.2.4.1Transmit Integrity Check14 3.4.2.2.4.2Receive Integrity Check14 3.4.2.2.5SIM Fault Management14 3.4.2.2.5.1CMC Channel Selection14 3.4.2.2.5.2CMC Mode Switching14 3.4.2.2.5.3CMC Power Shutdown14
15、 3.4.2.2.6SIM BITE Routine15 3.4.2.3Stub Cable Specification15 3.4.2.4Current Mode Coupler (CMC)16 3.4.2.4.1Transmit Function16 3.4.2.4.2Receive Function16 3.4.2.4.3CMC Power Supply16 3.4.2.4.4CMC Channel Selection16 3.4.2.4.5CMC Mode Selection16 3.4.2.4.6CMC Bus Interface16 3.4.2.4.7CMC Installatio
16、n16 3.4.2.5Bus Cable16 3.4.2.5.1General Characteristics16 3.4.2.5.2Bus Cable Termination16 3.4.3Fiber Optic Mode Bus16 3.4.3.1Fiber Optic Media Common Characteristics17 3.4.3.1.1Fiber Optic Media Terminal Input/Output Ports17 3.4.3.1.2Fiber Optic Media Data Rate20 3.4.3.1.3System Minimum Inter-messa
17、ge Gap20 3.4.3.1.4Fiber Optic Media Wavelength and Spectral Bandwidth20 3.4.3.1.5Modulation Format20 3.4.3.1.5.1Data Code20 3.4.3.1.5.2Pre-Pre-Sync Sync Pulse20 3.4.3.1.5.3Label Word Sync Pattern23 3.4.3.1.5.4Data Word Sync Modulation23 3.4.3.1.5.5End of Message Modulation Format23 3.4.3.1.6Wrap Aro
18、und Time23 3.4.3.1.7FOSIM Maximum Rated Optical Input Power23 3.4.3.1.8FOSIM Self-Monitoring of Pulses23 3.4.3.2Fiber Optic Transmitter (FOTX) Characteristics23 3.4.3.2.1FOTX Peak Output Power23 3.4.3.2.2FOTX Maximum Residual Power27 3.4.3.2.3FOTX Maximum Leakage Power27 3.4.3.2.4FOTX Output Wavefor
19、m27 3.4.3.2.5FOTX to Protocol Electrical Interface27 3.4.3.2.5.1FOTX Option A27 3.4.3.2.5.2FOTX Option B29 3.4.3.2.5.3FOTX Option C29 3.4.3.3Fiber Optic Receiver (FORX) Characteristics29 3.4.3.3.1FORX Input Signal Levels29 3.4.3.3.2FORX Inter-Message Dynamic Range30 3.4.3.3.3FORX Input Waveform30 3.
20、4.3.3.4FORX Dark Bus Condition30 3.4.3.3.5FORX Bus Quiet Condition30 3.4.3.3.6FORX Bit Error Rate30 iv -,-,- ARINC SPECIFICATION 629 TABLE OF CONTENTS ITEMSUBJECTPAGE 3.4.3.3.7FORX Collision Response30 3.4.3.3.8FORX to Protocol Electrical Interface32 3.4.3.3.8.1FORX Option A32 3.4.3.3.8.2FORX Option
21、 B32 3.4.3.3.8.3FORX Option C32 3.4.3.4Fiber Optic Transmission Media Characteristics32 3.4.3.4.1Fiber Physical Characteristics32 3.4.3.4.2Fiber Numerical Aperture35 3.4.3.4.3Fiber Chromatic and Modal Dispersion35 3.4.3.4.4Fiber Optic Transmission Media Attenuation35 3.4.3.4.5Optical Impulse Respons
22、es35 3.4.3.4.6Media Propagation Delay35 3.4.3.4.7Leakage Light Level35 3.4.3.5Tables of Characteristics35 3.4.4Voltage Mode Bus35 4.0MEDIA ACCESS CONTROL SUBLAYER38 4.1Introduction38 4.2Basic Protocol - Protocol BP38 4.2.1Logic Definition - Protocol BP38 4.2.1.1Transmit Interval (TI)38 4.2.1.2Synchr
23、onization Gap (SG)39 4.2.1.3Terminal Gap (TG)39 4.2.1.4Flow Chart - Protocol BP39 4.2.2Timing Considerations - Protocol BP39 4.2.3Transmit Operation - Protocol BP41 4.3Combined Mode Protocol - Protocol CP41 4.3.1Logic Definition - Protocol CP41 4.3.1.1Transmit Interval (TI)42 4.3.1.2Periodic Synchro
24、nization Gap (PSG)42 4.3.1.3Concatenation Event (CE)42 4.3.1.4Aperiodic Synchronization Gap (ASG)43 4.3.1.5Terminal Gap (TG)43 4.3.1.6Aperiodic Access Time-out (AT)43 4.3.1.7Periodic Transmission (Level 1)43 4.3.1.8Aperiodic Transmission (Level 2)44 4.3.1.8.1Level 2 Operation44 4.3.1.8.2Level 3 Oper
25、ation44 4.3.1.9Flow Chart - Protocol CP45 4.3.2Timing Considerations - Protocol CP45 4.3.2.1Periodic Transmission (Level 1)45 4.3.2.2Aperiodic Transmission (Level 2)47 4.3.2.3Aperiodic Transmission (Level 3)47 4.3.3Transmit Operation - Protocol CP48 4.4Common Elements48 4.4.1Data Synchronization48 4
26、.4.2Error Detection (Parity)49 4.4.3Terminal Monitoring49 4.4.4Collision Recovery49 4.4.5Receive Operation49 4.4.6Physical - Terminal Reconfiguration50 4.5Additional MAC Requirements for OSI Communications50 4.5.1MAC Frame Format50 4.5.1.1Elements of the MAC Frame50 4.5.1.1.1Address Fields50 4.5.1.1
27、.1.1Address Designation50 4.5.1.1.1.2Source Address Field51 4.5.1.1.1.3Destination Address Field51 4.5.1.1.2Protocol Indication Field51 v ARINC SPECIFICATION 629 TABLE OF CONTENTS ITEMSUBJECTPAGE 4.5.1.1.3Word Count Field51 4.5.1.1.4Data Field51 4.5.1.1.5Frame Check Sequence Field51 4.5.1.2Invalid M
28、AC Frame51 4.5.1.3Frame Check Sequence Validation51 4.5.2MAC Service51 4.5.2.1Primitives Used for MAC Service51 4.5.2.1.1MA UNITDATA.request51 4.5.2.1.2MA UNITDATA STATUS.indication52 4.5.2.1.3MA UNITDATA.indication52 5.0NON-OSI DATA TRANSFER54 5.1Introduction54 5.2Frame Definition54 5.3Non-OSI Broa
29、dcast Message Structure54 5.3.1Label54 5.3.2Channel Identification54 5.3.3Data Status55 5.3.3.1Status Reporting55 5.3.3.1.1System Status Word55 5.3.3.1.2Function Status Reporting56 5.3.3.2Parameter Validity56 5.3.4Word Count56 5.3.5Protocol Indication56 5.3.6Information56 5.3.7Frame Check Sequence56
30、 5.3.7.1Error Detection Algorithms57 5.4Non-OSI Unacknowledged Directed Transfer Message Structure57 5.4.1Source Address57 5.4.2Channel Identification57 5.4.3Destination Address57 5.4.4Data Status57 5.4.4.1Status Reporting57 5.4.5Protocol Indication58 5.4.6Word Count58 5.4.7Information Identifier58
31、5.4.8Information58 5.4.9Frame Check Sequence58 5.4.10Frame Check Sequence Validation58 6.0LOGICAL LINK CONTROL (LLC) SUBLAYER59 6.1Introduction59 6.2LLC Types and Class of Procedure59 6.2.1Types of LLC Operation59 6.2.2LLC Classes59 6.3Frame Structure59 6.3.1Bit Order59 6.3.2Data Unit59 6.4System Pa
32、rameters59 6.5Application of System Parameters59 ATTACHMENTSSUBJECTPAGE 1ACoupler Grounding and Shielding System60 1B-1Terminal Controller (TC) Serial Interface Module (SIM) Interface61 1B-2Specification of TXO/TXN and RXI/RXN Timing62 1CSubsystem (LRU/LRM) - Serial Interface Module (SIM) Interface6
33、3 vi ARINC SPECIFICATION 629 TABLE OF CONTENTS ATTACHMENTSSUBJECTPAGE 1DSerial Interface Between Current Mode Coupler and Stub Cable64 1ESignal Parameters65 1E-1ARINC 629 Waveform Templates for SIM-Coupler Interface66 1E-2Waveform Template: SIM Output to Transmit Stub67 1E-3Waveform Template: SIM In
34、put from Receive Stub68 1E-4Waveform Template: Coupler Input from Transmit Stub69 1E-5Waveform Template: Coupler Output to Receive Stub70 1E-6Waveform Template: Coupler Output to Bus Cable71 1E-7Waveform Template: Coupler Input From Bus Cable72 1E-8Coupler Power Supply Voltage Normal Mode73 1E-9Coup
35、ler Power Supply Voltage Received Only Mode74 1E-10Transmit Signal Amplitude Measurement75 1E-11Passive Coupler Test Circuit76 1E-12Passive Coupler Test Waveforms77 1E-13Coupler Reflected Impedance78 1FCurrent Mode Coupler and Bus Medium - Waveshapes and Timing79 1GExample Current Mode Coupler Packa
36、ging80 1HCurrent Mode Coupler Package Outline81 1ICurrent Mode Coupler Mounting Footprint82 2General Word Formats and Encoding Examples83 3APeriodic Mode Timing Diagram - Protocol BP85 3BAperiodic Mode Timing Diagram - Protocol BP86 4Example of a Message87 4AMessage Example88 4BWord Formats89 4CModu
37、lation Formats90 5AReceive Personality PROM (RPP) Cell Structure91 5BTransmit Monitor92 5CError Flags93 5DProtocol Monitoring94 6System Identification/Channel Identification (CID) Bit Definition95 7AProtocol CP - Access Protocol Summary96 7BProtocol CP - Overall Terminal Access State Diagram97 7CPro
38、tocol CP - Level 1 (Periodic) Access State Diagram98 7DProtocol CP - Level 2 (Aperiodic) Access State Diagram99 7EProtocol CP - Level 3 (Aperiodic) Access State Diagram100 8AProtocol CP Timing - Overall101 8BProtocol CP Timing - Level 1102 8CProtocol CP Timing - Level 2103 8DProtocol CP Timing - Lev
39、el 3104 9AExample of System Status Word Transmissions105 9BExample of Parameter Validity Word Transmission106 10Non-OSI Unacknowledged Directed Message Format107 11OSI Message Format108 12Non-OSI Broadcast Message Format109 13Syntax of Messages on Bus for a Single Terminal110 14Glossary112 15Timer O
40、peration117 APPENDICESSUBJECTPAGE 1References Documents122 2International Standards Organization Code #5123 3Example of Data Transfer124 4AExample of Transmit Personality PROM (XPP) Format Independent Mode Schedule125 4BExample of Transmit Personality PROM (XPP) Format Block Mode Schedule126 4CTrans
41、mit Personality PROM (XPP) Cell Structures127 4DXPP Label Structure128 4EXPP Address Structure129 4FXPP Transmit Word Mode and Transmit Word Count Control130 4GXPP Transmit Interrupt Structure131 4HXPP Variable Wordstring Structure132 vii ARINC SPECIFICATION 629 TABLE OF CONTENTS APPENDICESSUBJECTPA
42、GE 4IXPP Transmit Personality Prom (XPP) Synchronization133 5AReceive Personality PROM (RPP) Cell Structures134 5BRPP Address Structure135 5CAddress Generation With No Offset136 5DAddress Generation Without MPP137 5EAddress Generation Using MPP138 5FRPP Offset Table Diagram139 5GRPP Receive Mode, Me
43、ssage String Count and Receive Word Count -140 Internal Control 5HRPP - SG, TI, and TG Locations141 5IReceive Interrupt142 5JUse of RIV for Local Address Decoding143 6Protocol CP - Example Subsystem - Transmitter Dedicated Hardware144 for Levels 2 and 3 viii -,-,- ARINC SPECIFICATION 629 - Page 1 1.
44、0 INTRODUCTION 1.1 Purpose of This Document This document defines the aviation industry standards for transfer of digital data between avionics system elements using multiple access, bi-directional protocol.This standard is applicable to inter-system and intra-system communication. It defines the ch
45、aracteristics necessary to interface with a general purpose data bus for universal communication. It is intended to be used in conjunction withARINCCharacteristicswhichdefineavionics equipment. This document refers to Part 2 of ARINC Specification 629 which is an Application Guide for using the bus.
46、 It refers to Part 3 of ARINC Specification 629 which is an example format for defining data labels and wordstring formats.Part 4 is a compatibility Test Plan.Parts 2 through 4 are in draft form at the time of this writing. ARINC Specification 629 was developed to provide an efficient data distribut
47、ion system resulting in a reduction in the amount of airplane wiring and equipment interfaces. It is intended to advance the implementation of systems requiring voluminous and rapid data exchange such as centralized maintenance equipment. In general, judicious implementation of the system definition
48、 as provided by ARINC Specification 629 will provide a cost effective solution to overall avionics system design and integration. 1.2 Relationship to ARINC Specifications 419 and 429 ARINCSpecification419,“DigitalDataSystem Compendium,“ is a catalog of the elements of the several digital transmissio
49、n systems that have been applied during the emergent period of digital avionics. It has been used extensively prior to the adoption of ARINC Specification 429, “Mark 33 Digital Information Transfer System (DITS)“ in 1977. ARINC Specification 419 standards are no longer expected to be used for new designs. At the time of this writing, ARINC Specification 429 is the prevalent data bus in use, and it is expected that it will continue to be used in future designs.Airplane digital systems which conform to ARINC Sp