Search Results

Honda R&D Technical Review is a periodical containing research papers related to Honda R&D Center activities worldwide that cover automobile, motorcycle, power products, aircraft engine, and other fundamental technologies. Honda Motor offers a book for the April 2021 issue with 104 pages containing 12 papers focusing on the following latest topics: Technology for Prediction of Contactor Noise for Electric-powered Vehicle Batteries Reduction of Internal Resistance in High Capacity Lithium-ion Batteries with 3D Lattice-structured Electrode Predictive Technique for Seat Belt Submarining Injury by Triaxial Iliac Load Cell

The Aerospace Technical Paper Collection is a family of technical papers as either an annual subscription (current papers, archived papers, or both) or a perpetual collection (1906-1997). This collection is perfect for aerospace engineers, managers, or educators who need access to the most current content covering today's most relevent topics. Please contact one of our sales representatives to learn more and start your subscription today! SAE Sales Team customersales@sae.org 1-888-875-3976 (U.S. and Canada) 1-724-772-4086 (Outside the U.S.)

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 standard is to provide a method for packaging aircraft software parts for distribution using contemporary media or by electronic distribution. This project intends to standardize and provide guidance for the storage of floppy based software, currently packaged in media set parts. This standard format can be then stored or distributed on a single physical media member (CD-ROM), or by electronic crate. The obsolescence of floppy disks drive an urgent need for this guidance.

The purpose of this standard is to provide a source of definitions of terms and acronyms commonly used in the air transport maintenance community for test and evaluation with an emphasis on terms applicable to BITE.

This standard defines a common configuration report format that can be retrieved from an aircraft for use by ground tools and maintenance personnel. Reports will be generated in Extensible Markup Language (XML) format and structured as defined by this document. Several optional elements and attributes are defined to allow flexibility for a given report. This standard provides aircraft manufacturers, regulatory agencies, and airlines a format standard for aircraft configuration reporting, and facilitates automated comparison of configuration data reports (e.g., authorized versus as flying, 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 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.

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.

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.

Software content within commercial vehicles is growing exponentially. Emissions requirements, multiplexed communications, hybrid-electric technologies, active suspensions and smart sensors are amongst the technologies driving the increase in embedded code. Presenter Christoph Braeuchle , MKS Software, Inc.

The amount of software, computation and logic embedded into the vehicle systems is increasing. Testing of complex real time embedded systems using Hardware in Loop (HIL) simulations across different vehicle platforms has been a challenge. Data driven testing enables a qualitative approach to test these complex vehicle systems. It consists of a test framework wherein the test logic and data are independent of the HIL test environment. The data comprises variables used for both input values and output verification values. This data is maintained in a database or in the form of tables. Each row defines an independent test scenario. The entire test data is divided into three categories, High, Medium and Low. This feature gives the advantage of leveraging the same set of test data from Unit Level Testing phases to the Integration Test phase in the V-Cycle of software development. A data driven test approach helps the reuse of tests across vehicle platforms.

These advanced checks have resulted in development of many new diagnostic monitors, of varying types, and a whole new internal software infrastructure to handle tracking, reporting, and self-verification of OBD related items. Due to this amplified complexity and the consequences surrounding a shortfall in meeting regulatory requirements, efficient and thorough validation of the OBD system in the powertrain control software is critical. Hardware-in-the-Loop (HIL) simulation provides the environment in which the needed efficiency and thoroughness for validating the OBD system can be achieved. A HIL simulation environment consisting of engine, aftertreatment, and basic vehicle models can be employed, providing the ability for software developers, calibration engineers, OBD experts, and test engineers to examine and validate both facets of OBD software: diagnostic monitors and diagnostic infrastructure (i.e., fault memory management).

The Focus Electric is Ford�s first full-featured 5 passenger battery electric vehicle. The engineering team set our sights on achieving best-in-class function and efficiency and was successful with an EPA certified 1XX MPGe and range XXX then the facing competition allowing for a slightly lower capacity battery pack and larger vehicle without customer trade-off. We briefly overview the engineering method and technologies employed to deliver the results as well as sharing some of the functional challenges unique to this type of vehicle. Presenter Charles Gray, Ford Motor Co.

The rapid pace of recent progress in vehicle electrification technologies points to a bright future for electric-drive vehicles, but uncertainty regarding future technical trajectories and uncertainty in consumer response make possible a multitude of electric-drive vehicle futures. This presentation will examine a range of these possible electric-drive futures as a function of different technology and pricing scenarios. An exploration of initial conditions, market uptake, and resulting social benefits will show how HEV and PEV technology enable the attainment of stringent vehicle efficiency goals and unlock potential for lower-carbon futures. Presenter Jacob Ward, Department Of Energy