Search Results

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.

ARINC 814 defines an XML encoding and compression standard for aviation. It is based on the Open Geospatial Consortium (OGC) Binary XML document. Binary XML encoding is extended in a way that is both flexible and robust. Compression is added on top of the binary encoding. ARINC 814 is expected to be used with Aeronautical Databases, in particular, ARINC Specification 813: Embedded Interchange Format for Terrain Databases, ARINC Specification 815: Embedded Interchange Format for Obstacle Databases, and ARINC Specification 816: Embedded Interchange Format for Airport Mapping Database.

Virtual testing is a method that simulates lab testing using multi-body dynamic analysis software. The main advantages of this approach include that the design can be evaluated before a prototype is available and virtual testing results can be easily validated by subsequent physical testing. The disadvantage is that accurate specimen models are sometimes hard to obtain since nonlinear components such as tires, bushings, dampers, and engine mounts are hard to model. Therefore, virtual testing accuracy varies significantly. The typical virtual rigs include tire and spindle coupled test rigs for full vehicle tests and multi axis shaker tables for component tests. Hybrid simulation combines physical and virtual components, inputs and constraints to create a composite simulation system. Hybrid simulation enables the hard to model components to be tested in the lab.

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.

Real-time simulation of truck and trailer combinations can be applied to hardware-in-the-loop (HIL) systems for developing and testing electronic control units (ECUs). The large number of configuration variations in vehicle and axle types requires the simulation model to be adjustable in a wide range. This paper presents a modular multibody approach for the vehicle dynamics simulation of single track configurations and truck-and-trailer combinations. The equations of motion are expressed by a new formula which is a combination of Jourdain's principle and the articulated body algorithm. With the proposed algorithm, a robust model is achieved that is numerically stable even at handling limits. Moreover, the presented approach is suitable for modular modeling and has been successfully implemented as a basis for various system definitions. As a result, only one simulation model is needed for a large variety of track and trailer types.

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 number of electronically controlled systems in commercial vehicles is increasing rapidly. Much of this electrical content is controlled using ECUs (Electronic Control Units) which share information using some type of networking technology, such as a CAN bus running the SAE J1939 protocol. Presenter Jeffrey Craig, Vector CANtech Inc.