Search Results

This specification covers premium quality bolts and screws made of 6Al - 4V titanium alloy.

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.

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

ARINC 800 is the first industry standard intended for characterization of aviation-grade high-speed (Gbps) Ethernet links. The test methods are based on realistic representation of cabin networks. The notional cabling architecture is based on IFE seat distribution using multiple intermediate disconnects. Sequential testing is supported by building up number of connectors in the link. Test guidelines for mixed intermediate cable lengths are provided.

This document defines general practices for testing the physical layer of a fiber optic cable system. It is the intention of this document to outline proven practices for engineers and technicians engaged in testing and supporting fiber optic cable systems in aircraft. This document defines general practices for testing the physical layer of a fiber optic cable system. It is the intention of this document to outline proven practices for engineers and technicians engaged in testing and supporting fiber optic cable systems in aircraft.

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.

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

Research in plug in vehicles (PHEV and BEV) has of course been ongoing for decades, however now that these vehicles are finally being produced for a mass market an intense focus over the last few years has been given to proper evaluation techniques and standard information to effectively convey efficiency information to potential consumers. The first challenge is the development of suitable test procedures. Thanks to many contributions from SAE members, these test procedures have been developed for PHEVs (SAE J1711 now available) and are under development for BEVs (SAE J1634 available later this year). A bigger challenge, however, is taking the outputs of these test results and dealing with the issue of off-board electrical energy consumption in the context of decades-long consumer understanding of MPG as the chief figure of merit for vehicle efficiency.

Edgewater Computer Systems Inc. product RTEdge Platform 1.2 is a software toolset supporting proof based engineering, implementation and deployment of software components, built using the RTEdge AADL Microkernel modeling subset. This is a small subset of the AADL component model and execution semantics, covering threads and thread-groups communicating solely through asynchronous event ports and through explicitly shared data ports. Threads behavior is expressed as state machines and dispatch run time semantics is encoded in a Run-time Executive, enforcing pre-emptive priority dispatch based on statically assigned event priorities, with ceiling priority protocol access to shared data. This simple AADL microkernel semantic core can support all dispatch policies, communication and synchronization mechanisms of a fully fledged AADL run time environment, permitting the systematic use of the RTEdge static analysis tools for AADL compliant software components.

The use of Engine Health Management (EHM) systems has been growing steadily in both the civilian and the military aerospace sectors. Barring a few notable exceptions (such as certain temperature and thrust margin monitoring) regulatory authorities around the world have not required these systems to be certified in any way. This is changing rapidly. New airframes and engines are increasingly being designed with the assumption that EHM will be an integral part of the way customers will operate these assets. This leads to a need for better guidelines on how such systems should be certified. The SAE E-32 committee on Propulsion System Health Monitoring is leading an industry-wide effort to develop a set of guidelines for certifying EHM systems.

Plug-In Hybrid and Extended Range Electric Vehicle's have quickly become the focus of many OEM's and suppliers. Existing regulations and test procedures did not anticipate this rapid adoption of this new technology, resulting in many product development challenges. The lack of clear requirements is further complicated by CARBs consideration of CO2 inclusion in their next light duty OBD regulation. This presentation provides an overview of the regulatory requirements for OBD systems on hybrid vehicles that intend to certify in California. Near term challenges for EREV?s and PHEV?s are discussed, including concerns with the existing denominator and warm-up cycle calculations. Some proposals are made to address these concerns. Presenter Andrew Zettel, General Motors Company