DOCSLIB.ORG

Appendix a Data Transfer in Digital Aircraft Systems

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Appendix a Data Transfer in Digital Aircraft Systems Appendix A Data Transfer in Digital Aircraft Systems A.1 Serial Interfaces A large number of sensors in the airframe and engine systems require only a low volume data transfer between the sensors, the microcontroller and the central processor. Because every computer depends on the communica- tion with peripheral devices, it contains components for data transfer with external equipment. Prevalent on PCs as well as on industrial, scientific and consumer devices is the RS-232 (EIA-232) serial port as a means of control, monitoring and low volume data transfer. One port can connect to only one peripheral device. A serial port transmits and receives data one bit at a time over one wire. While it takes longer to transfer data this way, only a few wires are re- quired. Two way (full duplex) communication is available with only three separate wires, one to transmit, one to receive and a common ground wire. The RS-232 specifications include numerous additional control lines, which are used for special applications only. Generally processors internally use 8-, 16-, 32-, or 64-bit parallel data buses for faster processing. Thus data intended for transmission on a serial data line has to be converted from a parallel to a serial data stream. Like- wise data received has to be converted from a serial to a parallel data stream. These conversions can be performed by applying appropriate soft- ware, which is a method generally used on microcontrollers. A specific piece of hardware that converts data between a parallel bus and an RS-232 interface in both directions is the UART (Universal Asyn- chronous Receiver-Transmitter). The RS-232 serial port is an asynchro- nous device. For an asynchronous transmission its start is identified by a start bit and the end by one and a half or two stop bits. The data bits are sent to the receiver after a start bit. Such a data character usually consists of 7 or 8 bits. A parity bit may optionally be transmitted after the data. The transmitter and the receiver must agree on the number of data bits and the transfer rate. After converting a character to be transmitted from parallel to serial, the UART adds the start and stop bits and sends the result to the se- 200 Appendix A Data Transfer in Digital Aircraft Systems rial port. Every character received is stored, the start and stop bits are re- moved and the character is converted from serial to parallel. Then it is ready to be read by the processor. The UART usually does not directly generate or receive the external signaling levels (voltages) that are used between the devices. An interface is used to convert the logic level signals of the UART to the external sig- naling levels. All signals are measured in reference to a common ground. A positive voltage between 3 and 15 V represents a logical 0 and a nega- tive voltage between -3 and -15 V a logical 1. This switching between positive and negative is called bipolar. The zero state is not defined and is considered to be a faulty condition (this happens when the device is not operating). The dead area between +3 and -3 V is designed to absorb noise. By employing the RS-232 specification, use is made of a mature and universally available PC technology. If higher noise immunity, higher data transfer rates and more complex networks are necessary, one of two other serial interfaces is used. These are the (TIA/EIA) RS-422 and RS-485. These use two twisted wires for the data transmission. On one line a true signal is transmitted and on the other an identical signal but of opposite polarity. This produces opposing currents and magnetic fields, thus mini- mizing the emitted electromagnetic interference by cross-canceling the op- posite fields around each wire pair. Furthermore noise is coupled to both wires of the pair in the same way and thus is common to both signals. As the receiver evaluates the difference between the voltages of both wires, the effect of the noise is eliminated. This noise immunity allows for trans- missions at higher data rates and over longer distances. (TIA/EIA) RS-422 allows one transmitter to connect unidirectionally (simplex) to up to 10 receivers. Due to the lack of bidirectional capabilities allowing multipoint connections, the (TIA/EIA) RS-485 standard was cre- ated to add this capability. Its standards only describe the electrical proper- ties of the network. No transmission protocol is specified in the standard. However, several field bus standards in use specify RS-485 as electrical standard of data transmission. Among these are Profibus and Interbus-S. These widely used and proven standards can readily be adapted. RS-485 meets the requirements for a truly multi-point communication network. The standard specifies up to 32 transmitters and receivers. In a four-wire network one node is the master and all the others are slaves. The master node communicates to all slave nodes. All slave nodes communicate only with the master node. The slave nodes never listen to another slave’s re- sponse to the master. The master commands a response from only one slave at a time and thus prevents data collision. Adopting the RS-485 inter- A.2 Data Buses 201 face allows to take advantage of the widely used industrial field bus tech- nology, for which plenty of proven hardware and software is available. A.2 Data Buses A.2.1 ARINC 429 The ARINC 429 avionic data bus was specifically designed for use in civil transport aircraft and introduced in 1977. It defines how avionic devices and systems can communicate with each other. The specifications define the electrical and data characteristics and as well the protocols to be used. ARINC 429 is a unidirectional (Simplex) data bus using only one transmit- ter and at least one and not more than 20 receivers. The data bus consists of a screened twisted pair of wires with the screens usually connected to ground at both ends. Like the RS-422 and RS-485 interfaces always identical signals but of opposite polarity are transmitted along the two wires. This secures the noise immunity already described. The modulation is also bi-polar but different to the RS-422 and RS-485 interface standards. A logic state 1 is represented by a high state, which after one half of the bit length returns to zero. A logic state 0 is rep- resented by a low state, which after one half of the bit length returns to zero. This principle eliminates the need for a synchronization signal and thus the need for start and stop bits. The transmission voltage is 10±1 V between the wires. If one wire is +5 V, the other is -5 V and vice versa. Data is transmitted serially in 32-bit words. Thus the transmitter is transmitting 32-bit words or the null state. Each 32-bit word is separated by an interword gap of four bit-times. The ARINC 429 specifications define a high data rate of 100 kbps ±1% and a low data rate between 12.0 and 14.5 kbps. Each bus always operates either at high or low speed. The transmitter converts parallel binary words into 32-bit words. The receiver will convert these 32-bit serial words into parallel binary words readable by the processor to which it is connected. Bits 1 through 8 of a 32-bit word contain a system address label (SAL). This label not only de- fines a parameter but also the data type and therefore the rule how the 23 of the remaining 24 bits have to be interpreted. Three protocols are defined in ARINC 429 standards. These protocols are for the transmission of nu- meric data, discrete data and data files. The standard defines many fixed labels, which also define how the data is presented. Thus all manufacturers of different pieces of equipment al- 202 Appendix A Data Transfer in Digital Aircraft Systems ways have a common basis on which data is presented. The receivers are programmed to look for only that data which is relevant to its operation. Relevant data is identified by the label. The last bit is always the parity bit. Odd parity is specified. That means, that there must be an odd number of “1” bits in the 32-bit word. The parity bit is set according to the number of “1” bits. Since the ARINC 429 data bus transmits data in only one direction it is extremely reliable. There is a very low probability of data conflicts or data corruption. Thus it has become the mainstay of federated avionics archi- tectures. A.2.2 ARINC 629 The ARINC 629 data bus was originally developed and patented by Boe- ing and integrated into the Boeing 777 design. In 1989 it was released as an ARINC specification. Cost concerns about this avionic specific bus sys- tem and the emerging popularity of Ethernet technology have prevented further ARINC 629 implementation after the B777 development. Never- theless this standard initiated the move from the federated avionics archi- tecture – supported by the ARINC 429 bus – to the higher levels of inte- gration of the integrated modular avionics architecture. ARINC 629 is a bidirectional distributed control bus capable of support- ing up to 120 users. A 2 Mbps serial data transmission rate is specified for a twisted pair of conductors. Thus it is 20 times faster than an ARINC 429 bus. Each coupling to an ARINC 629 data bus is made via an ARINC 629 transmitter/receiver terminal.
Load more

Recommended publications
  • Fly-By-Wire - Wikipedia, the Free Encyclopedia 11-8-20 下午5:33 Fly-By-Wire from Wikipedia, the Free Encyclopedia
    Fly-by-wire - Wikipedia, the free encyclopedia 11-8-20 下午5:33 Fly-by-wire From Wikipedia, the free encyclopedia Fly-by-wire (FBW) is a system that replaces the Fly-by-wire conventional manual flight controls of an aircraft with an electronic interface. The movements of flight controls are converted to electronic signals transmitted by wires (hence the fly-by-wire term), and flight control computers determine how to move the actuators at each control surface to provide the ordered response. The fly-by-wire system also allows automatic signals sent by the aircraft's computers to perform functions without the pilot's input, as in systems that automatically help stabilize the aircraft.[1] Contents Green colored flight control wiring of a test aircraft 1 Development 1.1 Basic operation 1.1.1 Command 1.1.2 Automatic Stability Systems 1.2 Safety and redundancy 1.3 Weight saving 1.4 History 2 Analog systems 3 Digital systems 3.1 Applications 3.2 Legislation 3.3 Redundancy 3.4 Airbus/Boeing 4 Engine digital control 5 Further developments 5.1 Fly-by-optics 5.2 Power-by-wire 5.3 Fly-by-wireless 5.4 Intelligent Flight Control System 6 See also 7 References 8 External links Development http://en.wikipedia.org/wiki/Fly-by-wire Page 1 of 9 Fly-by-wire - Wikipedia, the free encyclopedia 11-8-20 下午5:33 Mechanical and hydro-mechanical flight control systems are relatively heavy and require careful routing of flight control cables through the aircraft by systems of pulleys, cranks, tension cables and hydraulic pipes.
    [Show full text]
  • Teledyne Lecroy Product Line Card
    Product Line Card OSCILLOSCOPES Learn More: teledynelecroy.com/oscilloscope LabMaster 10 Zi-A WaveMaster 8 Zi-B (SDA Models) (SDA/DDA 8 Zi-B) Bandwidth 20 GHz to 65 GHz 4 GHz to 30 GHz Resolution 8-bit resolution, 8-bit resolution, 11-bit with enhanced resolution 11-bit with enhanced resolution Rise Time 6.5 ps to 19.3 ps 15.5 ps to 95 ps Channels Up to 80, 4, (Analog+Digital+Sensor) 80 + 18 4 + 18 Display 15.3" WXGA Touch Screen 15.3" WXGA Touch Screen Standard Memory 32 Mpts/Ch 32 Mpts/Ch (64 Mpts/Ch) (64 Mpts/Ch) Maximum Memory† Up to 1024 Mpts Up to 512 Mpts Sample Rate Up to 160 GS/s Up to 80 GS/s MSO Characteristics† 3 GHz, 12.5 GS/s, 3 GHz, 12.5 GS/s, (Digital Channels) 18 Ch 18 Ch Trigger Types Edge, Width, Glitch, Pattern, Runt, Slew Rate, Edge, Width, Glitch, Pattern, Video, HDTV, Interval (Period), Dropout, Qualified, Cascade (Sequence) Trigger, Runt, Slew Rate, Interval (Period), Dropout, Qualified, Cascade High-speed Serial Trigger† (Sequence) Trigger, High-speed Serial Trigger† † Serial Data TD: 80-bit NRZ, 8b/10b, 64b/66b TD: 80-bit NRZ, 8b/10b, 64b/66b, RS-232, UART Trigger (T) D: 64b66b, 8b/10b, ARINC 429, Audio, TD or TDME: 100Base-T1, CAN, CAN FD, CAN FD Symbolic, Decode (D) CAN, CAN FD, CAN FD Symbolic, DigRF 3G, DigRF v4, I2C, LIN, MIL-STD-1553, SPI, Measure / Graph (M) ENET, ENET 10G, Fibre Channel, I2C, LIN, TD or TDxx: Audio (TDG), FlexRay (TDMP) Eye Diagram (E) Manchester, MDIO, MIL-STD-1553, NRZ, PCIe, RS-232.
    [Show full text]
  • ICE PROTECTION Incomplete
    ICE PROTECTION GENERAL The Ice and Rain Protection Systems allow the aircraft to operate in icing conditions or heavy rain. Aircraft Ice Protection is provided by heating in critical areas using either: Hot Air from the Pneumatic System o Wing Leading Edges o Stabilizer Leading Edges o Engine Air Inlets Electrical power o Windshields o Probe Heat . Pitot Tubes . Pitot Static Tube . AOA Sensors . TAT Probes o Static Ports . ADC . Pressurization o Service Nipples . Lavatory Water Drain . Potable Water Rain removal from the Windshields is provided by two fully independent Wiper Systems. LEADING EDGE THERMAL ANTI ICE SYSTEM Ice protection for the wing and horizontal stabilizer leading edges and the engine air inlet lips is ensured by heating these surfaces. Hot air supplied by the Pneumatic System is ducted through perforated tubes, called Piccolo tubes. Each Piccolo tube is routed along the surface, so that hot air jets flowing through the perforations heat the surface. Dedicated slots are provided for exhausting the hot air after the surface has been heated. Each subsystem has a pressure regulating/shutoff valve (PRSOV) type of Anti-icing valve. An airflow restrictor limits the airflow rate supplied by the Pneumatic System. The systems are regulated for proper pressure and airflow rate. Differential pressure switches and low pressure switches monitor for leakage and low pressures. Each Wing's Anti Ice System is supplied by its respective side of the Pneumatic System. The Stabilizer Anti Ice System is supplied by the LEFT side of the Pneumatic System. The APU cannot provide sufficient hot air for Pneumatic Anti Ice functions.
    [Show full text]
  • Chapter 76 Engine Controls
    ENGINE CONTROLS XL-2 AIRPLANE CHAPTER 76 ENGINE CONTROLS P/N 135A-970-100 Chapter 76 REVISION ~ Page 1 of 18 ENGINE CONTROLS XL-2 AIRPLANE Copyright © 2009 All rights reserved. The information contained herein is proprietary to Liberty Aerospace, Incorporated. It is prohibited to reproduce or transmit in any form or by any means, electronic or mechanical, including photocopying, recording, or use of any information storage and retrieval system, any portion of this document without express written permission of Liberty Aerospace Incorporated. Chapter 76 P/N 135A-970-100 Page 2 of 18 REVISION ~ ENGINE CONTROLS XL-2 AIRPLANE Table of Contents SECTION 76-00 GENERAL 5 SECTION 00-01 FADEC SYSTEM DESCRIPTION AND FUNCTIONAL OVERVIEW 6 SECTION 00-02 HEALTH STATUS ANNUNCIATOR AND POWER TRANSFER CHECK PROCEDURES 7 FADEC POWER TRANSFER CHECK 8 SECTION 76-10 POWER CONTROL 11 SECTION 10-01 POWER (THROTTLE) CABLE REMOVAL AND REPLACEMENT 12 THROTTLE CABLE REMOVAL 13 THROTTLE CABLE INSTALLATION 14 THROTTLE CABLE RIGGING PROCEDURE 15 SECTION 76-20 EMERGENCY SHUTDOWN 17 P/N 135A-970-100 Chapter 76 REVISION ~ Page 3 of 18 ENGINE CONTROLS XL-2 AIRPLANE PAGE LEFT INTENTIONALLY BLANK. Chapter 76 P/N 135A-970-100 Page 4 of 18 REVISION ~ ENGINE CONTROLS XL-2 AIRPLANE Section 76-00 General This chapter provides a descriptive overview of the control systems for the IOF- 240-B engine installed on the airplane. Detailed information for routine line maintenance for each engine subsection or system is provided in the appropriate chapter. More detailed information for repairs and maintenance on systems and components specific to the IOF-240B engine FADEC system are provided in the current release of the Teledyne Continental Motors Maintenance Manual for IOF- 240-B series engines, TCM p/n: M-22.
    [Show full text]
  • ARINC Protocol Tutorial
    ARINC Protocol Tutorial Copyrights ARINC Protocol Tutorial Manual Copyright 2000 Condor Engineering, Inc. This software product is copyrighted and all rights are reserved. The distribution and sale of this product are intended for the use of the original purchaser only per the terms of the License Agreement. This ARINC Protocol Tutorial Manual is copyrighted and all rights are reserved. This document may not, in whole or part, be; copied; photocopied; reproduced; translated; reduced or transferred to any electronic medium or machine-readable form without prior consent in writing from Condor Engineering, Inc. Microsoft is a registered trademark of Microsoft Corporation Windows is a registered trademark of Microsoft Corporation ARINC Protocol Tutorial (1600100-0027) Document Date: 07 June, 2000 Document Revision: 1.04 Condor Engineering, Inc. 101 W. Anapamu Street Santa Barbara, CA 93101 (805) 965-8000 (805) 963-9630 (fax) [email protected] (email) http:\www.condoreng.com Contents and Tables Contents Chapter 1 ARINC 429 Tutorial Introduction....................................................................................................1 About ARINC................................................................................................2 What is ARINC 429?...............................................................................2 ARINC 429 Usage ...................................................................................3 ARINC 429 Electrical Characteristics..........................................................3
    [Show full text]
  • Ensure Increased Reliability with ARINC 429 IP Core for FPGA
    Ensure increased reliability with ARINC 429 IP Core for FPGA DO-254 compliant offering with multichannel ARINC 429 transmitter/receiver core Overview Cyient IP Core Features ARINC 429 specification defines the standard • Developed according to DO-254 (DAL-A) requirements for the transfer of engineering data guidelines between avionics systems on commercial aircraft • Two transmitters and eight receivers with supporting high speeds of up to 100 kHz as well loopback mode for self -testing as speeds as low as 12.5 kHz. The ARINC protocol • Portable to Microsemi, Intel/Altera, Lattice, or supports more than 46 meters. Xilinx FPGA families The Cyient ARINC 429 IP Core is developed for • Supports standard line drivers and receivers FPGA with multiple transmitters and receivers and • Parity checking for Tx and Rx is compliant with Design Assurance Level (DAL) • Programmable labels (up to eight different labels) A requirements. It receives data from an external • Programmable label filtering and SDI check microcontroller through SPI lines and transmits • SPI interface to the microcontroller 32-bit data word (encoded serial data) through the ARINC line driver. ARINC429 IP Core receives • Programmable data rates for each channel: 12.5 serial data from the ARINC line receiver and or 100 kbps transmits 32-bit decoded data word to an external • Detection of parity, label, SDI, and data errors microcontroller. Fig. 1 | ARINC 429 Board FPGA RX FIFO RxHi 8 Arinc ARINC RX RxLow Line Receivers Parity Check SDI & Label Check SPI TX FIFO Micro Controller Micro TxHi 2 Arinc ARINC TX Tx Low Line Control and Status Registers and Status Control Drivers Parity Gen Error Injection Fig.
    [Show full text]
  • Arinc 429 Converter Logic & Interface
    NEXSYS® Component Technology ARINC 429 CONVERTER LOGIC & INTERFACE The ARINC 429 Converter component is an 8-pin logic and interface device developed (IN 1) (GND) (RXA) (FAIL) as a part of our NEXSYS® Component Technology. This single-bit, single-label ARINC 429 Converter can replace the need for a dedicated ARINC converter box. The ARINC 429 (RXB) (IN 2) (28 V) (OUT) Converter can be configured inside a VIVISUN® High Capacity switch body or inside a stand- alone NEXSYS Module for use behind the panel. The ARINC 429 Converter can be combined SR429/1M with electromechanical switches and other NEXSYS components to create a custom configuration that uniquely addresses the designer’s specific functional requirements. The ARINC 429 Converter is designed and tested in accordance with MIL-PRF-22885 and DO-160. SR429/1M • Industry first innovation - ARINC 429 converter inside VIVISUN annunciator, switch or NEXSYS Module • Simple unit with no software, firmware or programmable logic • No external decoder box required to achieve annunciation based on data bit • Accommodates two additional discrete inputs to provide “fail” monitoring • Includes watchdog timer with selectable buffer times to monitor validity of incoming ARINC data stream • Ideally suited for ADS-B out pilot interface requirements • Included in MIL-PRF-22885/108 VIVISUN® High Capacity Body as shown contains ARINC 429 Converter, single switch pole and 4-pin NEXSYS component NEXSYS® Module as shown contains ARINC 429 Converter Data Sheet: DS-4291M-17 www.appliedavionics.com OVERVIEW ARINC 429 CONVERTER ARINC 429 Converter (SR429/1M) Figure 1: Block Diagram The ARINC 429 Converter (SR429/1M) component can be configured inside a VIVISUN® annunciator, switch or NEXSYS® Module.
    [Show full text]
  • The Market for Aviation APU Engines
    The Market for Aviation APU Engines Product Code #F644 A Special Focused Market Segment Analysis by: Aviation Gas Turbine Forecast Analysis 2 The Market for Aviation APU Engines 2011 - 2020 Table of Contents Executive Summary .................................................................................................................................................2 Introduction................................................................................................................................................................2 Methodology ..............................................................................................................................................................2 Trends..........................................................................................................................................................................3 The Competitive Environment...............................................................................................................................3 Market Statistics .......................................................................................................................................................3 Table 1 - The Market for Aviation APU Engines Unit Production by Headquarters/Company/Program 2011 - 2020 ..................................................5 Table 2 - The Market for Aviation APU Engines Value Statistics by Headquarters/Company/Program 2011 - 2020.................................................10 Figure 1 - The Market
    [Show full text]
  • Fly-By-Wire: Getting Started on the Right Foot and Staying There…
    Fly-by-Wire: Getting started on the right foot and staying there… Imagine yourself getting into the cockpit of an aircraft, finishing your preflight checks, and taxiing out to the runway ready for takeoff. You begin the takeoff roll and start to rotate. As you lift off, you discover your side stick controller is not responding correctly to your commands. Panic sets in, and you feel that you’ve lost total control of the aircraft. Thanks to quick action from your second in command, he takes over and stabilizes the aircraft so that you both can plan to return to the airport under reversionary mode. This situation could have been a catastrophe. This happened in August of 2001. A Lufthansa Airbus A320 came within less than two feet and a few seconds of crashing during takeoff on a planned flight from Frankfurt to Paris. Preliminary reports indicated that maintenance was performed on the captain’s sidestick controller immediately before the incident. This had inadvertently created a situation in which control inputs were reversed. The case reveals that at least two "filters," or safety defenses, were breached, leading to a near-crash shortly after rotation at Frankfurt’s Runway 18. Quick action by the first officer prevented a catastrophe. Lufthansa Technik personnel found a damaged pin on one segment of the four connector segments (with 140 pins on each) at the "rack side," as it were, of the avionics mount. This incident prompted an article to be published in the 2003 November-December issue of the Flight Safety Mechanics Bulletin. The report detailed all that transpired during the maintenance and subsequent release of the aircraft.
    [Show full text]
  • MIL-STD-1553 IP Core
    ARINC 429 IP Core for FPGAs ARINC429IP ARINC 429 IP Core with modular transmitters and receivers Compact, Robust, Reliable MIL-STD-IP-Cores Key Features and Benefits ARINC 429 specification compatible Separated channels for ARINC 429 Data Transmit and Receive 32 bits wide, programmable depth, separated FIFO buffers for transmit and receive Includes noise filtering mechanism to enhance receiver robustness Programmable data rate on each channel (12.5/100 Kbps) Programmable label recognition with 256 Labels for each Receiver Programmable parity: Even, Odd or No-parity (32nd bit as data) FIFO full/empty indication Supports standard ARINC 429 line drivers/receivers with two bits data and slope bit controls Multiple running clock options to reduce design time domains Small FPGA area utilization Modular architecture allowing flexible implementations. Any number of transmitters and receivers available in a single Netlist. Provided with full verification environment Based on vendor and technology independent VHDL code Rx_Data_rd RX_P Rx_Data Rx_Data_valid RX_N Rx_Control Rx_Label_w Tx_Data e Rx_Label ARINC429IP-RX Tx_Data_we Rx_Labels_Table_rdy ARINC429IP-R Tx_Control Rx_Labels_Table_rst ARINC 429 TX_P Tx_FIFO_Full ARINC429IP-TX ReceiverARINC 429 More products from Sital: Rx_FIFO_Full Receiver Tx_FIFO_Empty TX_N Rx_FIFO_Empty Tx_FIFO_NumOfWords ARINCA 429 MIL-STD-1553 IP Core, DDC® Slope Rx_FIFO_NumOfWords Transmitter compatible with local bus interface Clk MIL-STD-1553 IP Cores for simple Clk ResetN ResetN BC/RT/MT Applications. 1 1 2 2 MIL-STD-1553 Discrete Components n m Transceiver MIL-STD-1553 Testers. MIL-STD-1553 Design Services Designed from ground up for use in aerospace, avionics and military, Sital's IP ARINC 429 IP Core products, offer uniquely compact, robust and reliable solutions for any PLD/FPGA PCI IP core and ASIC device.
    [Show full text]
  • C-130J Super Hercules Whatever the Situation, We'll Be There
    C-130J Super Hercules Whatever the Situation, We’ll Be There Table of Contents Introduction INTRODUCTION 1 Note: In general this document and its contents refer RECENT CAPABILITY/PERFORMANCE UPGRADES 4 to the C-130J-30, the stretched/advanced version of the Hercules. SURVIVABILITY OPTIONS 5 GENERAL ARRANGEMENT 6 GENERAL CHARACTERISTICS 7 TECHNOLOGY IMPROVEMENTS 8 COMPETITIVE COMPARISON 9 CARGO COMPARTMENT 10 CROSS SECTIONS 11 CARGO ARRANGEMENT 12 CAPACITY AND LOADS 13 ENHANCED CARGO HANDLING SYSTEM 15 COMBAT TROOP SEATING 17 Paratroop Seating 18 Litters 19 GROUND SERVICING POINTS 20 GROUND OPERATIONS 21 The C-130 Hercules is the standard against which FLIGHT STATION LAYOUTS 22 military transport aircraft are measured. Versatility, Instrument Panel 22 reliability, and ruggedness make it the military Overhead Panel 23 transport of choice for more than 60 nations on six Center Console 24 continents. More than 2,300 of these aircraft have USAF AVIONICS CONFIGURATION 25 been delivered by Lockheed Martin Aeronautics MAJOR SYSTEMS 26 Company since it entered production in 1956. Electrical 26 During the past five decades, Lockheed Martin and its subcontractors have upgraded virtually every Environmental Control System 27 system, component, and structural part of the Fuel System 27 aircraft to make it more durable, easier to maintain, Hydraulic Systems 28 and less expensive to operate. In addition to the Enhanced Cargo Handling System 29 tactical airlift mission, versions of the C-130 serve Defensive Systems 29 as aerial tanker and ground refuelers, weather PERFORMANCE 30 reconnaissance, command and control, gunships, Maximum Effort Takeoff Roll 30 firefighters, electronic recon, search and rescue, Normal Takeoff Distance (Over 50 Feet) 30 and flying hospitals.
    [Show full text]
  • ARINC Protocol Summary
    ARINC Protocol Summary Part Number: 10011-00000-A1 Cage Code: 4RK27 ● NAICS: 334119 Alta Data Technologies LLC 4901 Rockaway Blvd, Building A Rio Rancho, NM 87124 USA (tel) 505-994-3111 ● www.altadt.com i CUSTOMER NOTES: Document Information: Rev A1 – Release Date: 7 April 2010 Note to the Reader and End-User: This document is provided for information only and is copyrighted by Alta Data Technologies. While Alta strives to provide the most accurate information, there may be errors and omissions in this document. Alta disclaims all liability in document errors and any product usage. By using an Alta product, the customer or end user agrees (1) to accept Alta’s Standard Terms and Conditions of Sale, Standard Warranty and Software License and (2) to not hold Alta Members, Employees, Contractors or Sales & Support Representatives responsible for any loss or legal liability, tangible or intangible, from any document errors or any product usage. The product described in this document is not US ITAR controlled. Use of Alta products or documentation in violation of local usage, waste discard and export control rules, or in violation of US ITAR regulations, voids product warranty and shall not be supported. This document may be distributed to support government programs and projects. Third party person, company or consultant distribution is not allowed without Alta’s written permission. AltaCore, AltaCore-1553, AltaCore-ARINC, AltaAPI, AltaView and AltaRTVal are Trademarks of Alta Data Technologies LLC, Rio Rancho, New Mexico USA Contact: We welcome comments and suggestions. Please contact us at 888-429-1553 (toll free in US) or 505- 994-3111 or visit our web site for support submit forms at www.altadt.com or email us at [email protected] or [email protected].
    [Show full text]