Search Results

This SAE Standard provides performance and general design requirements and related test procedures for a combination tail and floodlamp for use on industrial wheeled equipment that may be operated on public roads.

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 costs, improving quality, safety or environmental impact, and achieving regulatory compliance. Sensors are essential to the safety, efficiency, and dependability of modern vehicles. Crash sensors can anticipate a collision faster than humans would, and tire pressure sensors can alert the driver or pilot in case action is needed. In the episode "Sensors: Advanced Safety" (20:36) Continental engineers look at the evolution of passive safety systems, discuss the changes in sensors over the last ten years and what is coming next. Engineers at Meggitt demonstrate how tire pressure monitoring system sensors for aerospace are built and tested.

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

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

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

SAE 2011 High Efficiency IC Engines Symposium - Session 1- Pathways to High Efficiency Presenter Rolf D. Reitz, Univ. of Wisconsin

When vehicles share certain information wirelessly via Dedicated Short Range Communications (DSRC), they enable a new layer of electronic vehicle safety that, when needed, can generate warnings to drivers and even initiate automatic preventive actions. Vehicle location and velocity provided by Global Navigation Systems (GNSS), including GPS, are key in allowing vehicle path estimation. GNSS is effective in accurately determining a vehicle's location coordinates in most driving environments, but its performance suffers from obstructions in dense urban environments. To combat this, augmentations to GNSS are being contemplated and tested. This testing has been typically done using a reference GNSS system complimented by expensive military-grade inertial sensors, which can still fail to provide adequate reference performance in certain environments.

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.

Rapid control prototyping (RCP) is a widely used technique for verifying a controller's functional behavior. Typically, RCP uses a target processor with ample processing power and memory, which makes the technique attractive for engineers exploring new concepts. Presenter Thomas Erkkinen, MathWorks Inc.