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.).

This document specifies how application to application navigation is managed on tablet EFB devices. Topics include: inter-application navigation for users, blending of multiple applications into a single workflow, single data entry with data shared across applications.

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.

This standard sets forth the desired characteristics of Aviation Ku-band Satellite Communication (Satcom) and Ka-band Satcom Systems intended for installation in all types of commercial air transport aircraft. The intent of this characteristic is to provide guidance on the interfaces, form, fit, and function of the systems. This document also describes the desired operational capability of the equipment needed to provide a broadband transport link that can be used for data, video, and voice communications typically used for passenger communications and/or entertainment. The systems described in this characteristic are not qualified, at this writing, for aviation safety functions.

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 2 provides aviation ground system gateway considerations necessary to transition to the Internet Protocol Suite (IPS). ARINC 858 Part 2 describes the principles of operation for an IPS gateway that enables ACARS application messages to be exchanged between an IPS aircraft and a ground ACARS host. ARINC 858 Part 2 also describes the principles of operation for an IPS gateway that enables OSI-based application messages to be exchanged between an IPS host and an OSI end system. This product was developed in coordination with ICAO WG-I, RTCA SC-223, and EUROCAE WG-108.

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 "Diagnostics and Prognostics: Proactive Maintenance and Failure Prevention" (21:04), Delphi engineers explain how they leverage the growing number of sensors and computing power in vehicles to diagnose and proactively solve emerging mechanical or electronic problems, before a breakdown occurs. This video also looks at the next generation of automotive telematics, with HEM Data demonstrating how in-vehicle data acquisition is used to monitor the inner workings of vehicles.

Main topics are the development and the build-up of an 18ton hybrid truck with a parallel hybrid drivetrain. With this truck it is possible to drive up to 3 kilometers in the pure electric driving mode. Presenter Andreas Eglseer, Engineering Center Steyr GmbH & Co. KG

The automotive industry continues to develop new powertrain technologies aimed at reducing overall vehicle level fuel consumption. This paper discusses the development of a new highly efficient parallel hybrid transmission for use in transversely installed powertrains for FWD applications. FEV is developing a new 7-speed hybrid transmission for transverse installation. The transmission with a design torque of 320 Nm is based on AMT (automated manual transmission) technology and uses a single electric motor. The innovative gearset layout combines the advantages of modern AMTs such as best efficiency, low costs and few components (reduced part count) with full hybrid capabilities and electric torque support during all gear shifts. Furthermore, the gear set layout allows for very short shift-times due to the favorable distribution of inertias. Other features include an A/C compressor being electrically driven by the electric motor of the transmission during engine start/stop phases.

Powertrain Systems development is facing unprecedented challenges driven by the convergence of many factors: increasing government regulations for tailpipe emissions, diagnostics and fuel economy, increased competition, shorter development cycles, and tighter program budgets. Using telematics and information technology to automate the evaluation of a system�s robustness enables engineers to focus their time on problem areas during their normal development process and launch with quality. This presentation will use real world examples to detail how this methodology was jointly applied by Control-Tec and Ford Motor Company to identify and improve the system performance of Ford�s Air-Fuel Imbalance Monitor before production. Presenter Bill Leisenring, Control-Tec LLC

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.

The growing need for an efficient worldwide airspace system management, generated by an increasing traffic load, requires new capabilities for air-ground data communication technologies. In order to cope with these requirements, the Federal Aviation Administration (FAA), EUROCONTROL, and the International Civil Aviation Organization (ICAO) have jointly made specific recommendations for candidate technologies for the airport surface communication network. In the SESAR project, the Aeronautical Mobile Airport Communication System (AeroMACS) technology is being developed in such a way to provide next generation broadband and wireless data communications for airport surface applications (i.e. Air Traffic Control ? ATC, Airline Operational Communications ? AOC, and surface vehicles services).

“Spotlight on Design: Insight” features an in-depth look at the latest technology breakthroughs impacting mobility. 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. Automated driving is made possible through the data acquisition and processing of many different kinds of sensors working in unison. Sensors, cameras, radar, and lidar must work cohesively together to safely provide automated features. In the episode “Automated Vehicles: Converging Sensor Data” (8:01), engineers from IAV Automotive Engineering discuss the challenges associated with the sensor data fusion, and one of Continental North America’s technical teams demonstrate how sensors, radars, and safety systems converge to enable higher levels of automated driving.