Search Results

This ARINC Standard specifies the ARINC 758 Mark 2 Communications Management Unit (CMU) as an on-board message router capable of managing various datalink networks and services available to the aircraft. Supplement 4 adds Ethernet interfaces, per ARINC Specification 664 Part 2. This will allow the CMU to communicate with IP based radio transceivers (e.g., L-Band Satellite Communication Systems (Inmarsat SwiftBroadband (SBB) and Iridium Certus), ACARS over IP, AeroMACS, etc.).

The purpose of this document is to provide an overview of data networking standards recommended for use in commercial aircraft installations. These standards provide a means to adapt commercially defined networking standards to an aircraft environment. It refers to devices such as bridges, switches, routers and hubs and their use in an aircraft environment. This equipment, when installed in a network topology, can optimize data transfer and overall avionics performance.

The purpose of this document is to evaluate Communication, Navigation, and Surveillance (CNS) Distributed Radio architectures and the feasibility of distributing the RF and systems processing sections to ensure the following: Reduce cost of equipment Reduce Size, Weight, and Power (SWaP) Ease of aircraft integration Growth capability built into the design Maintain or improve system availability, reliability, and maintainability It provides a framework to determine whether it is feasible to develop ARINC Standards that support CNS distributed radio architectures.

This document describes the technical requirements, architectural options, and recommended interface standards to support an Autonomous Distress Tracking (ADT) System intended to meet global regulatory requirements for locating aircraft in distress situations and after an accident. This document is prepared in response to International Civil Aviation Organization (ICAO) and individual Civil Aviation Authorities (CAAs) initiatives.

The purpose of this document is to provide guidelines for integrating previously standalone cabin systems such as cabin management systems, In-Flight Entertainment (IFE) systems, In-Flight Connectivity (IFC) systems, galley systems, surveillance systems, etc. Resource sharing between systems can reduce airline costs and/or increase functionality. But, as systems expose their internal resources to external systems, the risk of an intrusion that could degrade function and/or negatively expose the supplier’s or airline’s brand increases. This document provides a recommended IP networking design framework between aircraft systems to reduce the operational security threats while still supporting the necessary intersystem routing.

This document defines a standard implementation for strong client authentication and encryption of Wi-Fi-based client connections to onboard Wireless LAN (WLAN) networks. WLAN networks may consist of multi-purpose inflight entertainment system networks operating in the Passenger Information and Entertainment System (PIES) domain, dedicated aircraft cabin wireless networks or localized Aircraft Integrated Data (AID) devices operating in the Aircraft Information Services (AIS) domain. The purpose of this document is to focus on the client devices requiring connections to these networks such as electronic flight bags, flight attendant mobile devices, onboard Internet of Things (IoT) devices, AID devices (acting as clients) and mobile maintenance devices. Passenger devices are not within the focus of this document.

ARINC Report 686 represents the consensus of industry to prepare a roadmap migration from IPv4 to IPv6. This document describes airline objectives (air and ground side when possible) towards the development and introduction of IPv6. There are three distinct elements considered: 1) the applications for addressing aspects 2) the communication network(s) over which the applications are running for the IP protocol level itself and associated features, and 3) the physical link(s) the network(s) interface.

The difficulty in locating crash sites has prompted international efforts for alternatives to quickly recover flight data. This document describes the technical requirements and architectural options for the Timely Recovery of Flight Data (TRFD) in commercial aircraft. ICAO and individual Civil Aviation Authorities (CAAs) levy these requirements. The ICAO Standards and Recommended Practices (SARPs) and CAA regulations cover both aircraft-level and on-ground systems. This report also documents additional system-level requirements derived from the evaluation of ICAO, CAA, and relevant industry documents and potential TRFD system architectures. It describes two TRFD architectures in the context of a common architectural framework and identifies requirements. This report also discusses implementation recommendations from an airplane-level perspective.

This document defines a secure Wi-Fi distribution network installed in the aircraft passenger cabin for passenger and crew use. Carry-on Portable Electronic Devices (PEDs) such as smart phones, tablets, and laptops may use this network to access public internet services provided on the aircraft.

ARINC Specification 848 is a functional standard based on a protocol specification profile for a secured network interface. The purpose is to define a common method of initiating a mutually authenticated tunnel between an aircraft service and its Enterprise service. ARINC Specification 848 defines a standard implementation for securing the communications between an onboard Local Area Network (LAN) and an Enterprise LAN on the ground. Various aircraft network architectures and various air to ground communication channels (aka media) are accommodated in this document. For example, L-band Satellite Communication (Satcom), Ku/Ka-band Satcom, Gatelink Cellular, and Gatelink are considered.

ARINC 858 Part 1 defines the airborne data communication network infrastructure for aviation safety services using the Internet Protocol Suite (IPS). ARINC 858 builds upon ICAO Doc 9896, Manual on the Aeronautical Telecommunication Network (ATN) using Internet Protocol Suite (IPS) Standards and Protocol. IPS will extend the useful life of data comm services presently used by operators, e.g., VDL, Inmarsat SBB, Iridium NEXT, and others. It represents the evolutionary path from ACARS and ATN/OSI to the end state: ATN/IPS. ARINC 858 includes advanced capabilities such as aviation security and mobility. This product was developed in coordination with ICAO WG-I, RTCA SC-223, and EUROCAE WG-108.

"Spotlight on Design" features video interviews and case study segments, focusing on the latest technology breakthroughs. Viewers are virtually taken to labs and research centers to learn how design engineers are enhancing product performance/reliability, reducing cost, improving quality, safety or environmental impact, and achieving regulatory compliance. In the episode "Automated Vehicles: Sensors and Future Technologies" (24:31), highly automated driving is looked at in detail as the culmination of years of research in automotive technology, sensors, infrastructure, software, and systems integration. Real-life case studies show how organizations are actually developing solutions to the challenge of making cars safer with less driver intervention. IAV Automotive Engineering demonstrates how a highly automated vehicle capable of lane changing was created.

The presentation describes the aerodynamic development and optimization process of the three different new models of the Audi A6/A7 family. The body types of these three models represent the three classic aerodynamic body types squareback, notchback and fastback. A short introduction of the flow structures of these different body types is given and their effect on the vehicle aerodynamic is described. In order to achieve good aerodynamic performance, the integration into the development process of the knowledge about these flow phenomena and the breakdown of the aerodynamic resistance into its components friction- and pressure drag as well as the induced drag is very important. The presentation illustrates how this is realized within the aerodynamic development process at Audi. It describes how the results of CFD simulations are combined with wind tunnel measurements and how the information about the different flow phenomena were used to achieve an aerodynamic improvement.

Given the fast changing market demands, the growing complexity of features, the shorter time to market, and the design/development constraints, the need for efficient and effective verification and validation methods are becoming critical for vehicle manufacturers and suppliers. One such example is fault-tree analysis. While fault-tree analysis is an important hazard analysis/verification activity, the current process of translating design details (e.g., system level and software level) is manual. Current experience indicates that fault tree analysis involves both creative deductive thinking and more mechanical steps, which typically involve instantiating gates and events in fault trees following fixed patterns. Specifically for software fault tree analysis, a number of the development steps typically involve instantiating fixed patterns of gates and events based upon the structure of the code. In this work, we investigate a methodology to translate software programs to fault trees.

From 2009 until present Toyota has had a demonstration program of Prius PHV which is comprised of 600 vehicles throughout Japan, Europe and in the US. The vehicles were given to government agencies, corporations, utility companies and private individuals to use. With these demo units Toyota wanted to understand the market reaction and real world impact of plug-in technology on gasoline displacement with increased use of electricity as a fuel. This presentation shows that approximately 50% of fuel was saved using the PHVs in the US. An experiment in Toyota City shows that if public infrastructure is optimized to be convenient and located where people normally park, there is a potential to achieve an ideal fuel savings of 61%. The demonstration program shows that plug-in technology in fact saves fuel and that the proper infrastructure can optimize the fuel savings of plug-in hybrids. Presenter Avernethy Francisco, Toyota

By introducing the concept of a separation between graphics and logic, interpreted run time architecture, and defined communication protocol, the ARINC 661 standard has addressed many of the concerns that aircraft manufacturers face when creating cockpit avionics displays. However, before kicking off a project based on the standard, it is important to understand all aspects of the standard, as well as the benefits and occasional drawbacks of developing with ARINC 661 in mind. This white paper will first provide an overview of ARINC 661 to clarify its concepts and how these relate to the development process. The paper will also describe the benefits of using a distributed development approach, and will outline practical, real world considerations for implementing an ARINC 661-based solution. Finally, readers will learn how commercial tools can be used to simplify the creation of displays following the standard to speed development and reduce costs.

An overview of Daimler?s progression to advance powertrain technology in a growth industry shows many different solutions to improvement in transportation. Daimler continues to make breakthroughs in technology development and application building on 125 years of automotive development. Optimization of current powertrains will enable a significant gain in CO2/mi reductions, that dependent on product mix can be augmented with additional technologies. There is however no bypass to some form of electrification, enabling efficiency gains and alternative forms of power supply. Development of hybrid powertrains continues in an established manner and enhanced development of further electrified powertrains are in development. Organizationally and technically, significant skills and adjustments need to continue to be undertaken enabling OEMs and in particular the supply base to develop optimized solutions efficiently. The outlook is bright for novel component development and innovation.

Toyota is researching and developing several advanced vehicle powertrain technologies that increase fuel efficiency and decrease the environmental impact of consumer transportation. This presentation will describe the Toyota Plug-In Hybrid (PHV) architecture, its major components, the Toyota PHV Demonstration program, and the benefits of the Toyota approach to Plug-In hybrids. The current Toyota PHV features all electric driving for approximately 13 miles, while maintaining the fuel economy of Prius even when the vehicle is in hybrid mode. The vehicle that will be available in 2012 will also be affordable, allowing many customers to enjoy the benefits of electric drive. Presenter Avernethy Francisco, Toyota Motor Engineering & Manufacturing

There are several variables to consider when specifying a hydraulic hybrid system in a commercial vehicle. Parameters which can be controlled include various component sizes and some hybrid system calibration parameters. Presenter Paul Schwark, Bosch Rexroth AG

Use of airborne high resolution digital sensor imagery is ever increasing. Color HDTV, infrared cameras and radar are examples of such sensors. And they are becoming increasingly used for mission purposes by the military, police, customs and coast guard onboard helicopters and fixed wing aircraft. These users have requirements for onboard presentation, analysis and storage. Use of weather radars and other similar types of sensors are flight oriented applications in major types of aircraft. Another application is the integration of cockpit and cabin surveillance systems onboard commercial airlines. Cabin surveillance systems, growing from cockpit door cameras to complete cabin surveillance, will use several cameras. The purpose is to acquire and store imagery from un-normal events including unruly passengers and eventual terrorists. The primary intentions are security awareness in the cockpit as well as collecting evidence for a potential prosecution.