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

SAE 2011 High Efficiency IC Engines Symposium - Session 3 - Advanced Diesel Engine Technologies Presenter Andrew Brown, Delphi Corp.

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.

Some the OBD-II regulations have been around for a long time or seem to be intuitively obvious. It is easy to assume to assume that everyone knows how to implement them correctly, that is, until someone actually reads the words and tries to do it. Most often, these issues come up when modifying existing OBD features, not when creating completely new ones. This presentation contains a few examples of features that should have been easy to implement, but turned out not to be easy or simple. Presenter Paul Algis Baltusis, Ford Motor Co.

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

Vehicle electrification is shaping the future of automotive mobility in terms of automotive power and propulsion. The market for New Energy Vehicles (HEV/PHEV/REEV/EV) as well as clean vehicle technologies is expected to grow steadily driven by government regulations mandating increased fuel economy and lower emissions. The fastest growth in this market will be in Asia Pacific, most notably China. The Chinese government has made its intentions clear on how important it considers the development and consumer purchase of hybrid and electric vehicles. The mandate is that by year 2012, vehicle manufacturers produce at least 500,000 units (or 5%) per year of their total output as hybrid and/or electric. All Chinese vehicle manufacturers must have at least one HEV or EV model in the market by the same year. Thus far China has invested over US$3.5 billion to stimulate the production of NEVs and the necessary infrastructure to support them.

Low Voltage Electric Drives are becoming very attractive for various applications in the Turf, Construction and Agricultural products being engineered today. Determining what the Customer Support Requirements are for Maintenance and Repair for the Life Cycle of the products is critical to the initial design process. Presenter Russell Christ

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.

The introduction of hybrid and plug-in hybrid electric vehicles has resulted in the introduction of battery systems into the realm of OBD II diagnostics. After a high-level overview of battery systems, general battery system fault responses are discussed, as well as which of these might be OBD faults. The alignment of the OBD regulations and DTC assignment in systems with large numbers of similar/identical components is discussed, along with apparent conflicts between existing OBD regulations and the physical realities of battery systems in HEVs and PHEVs. Presenter Dyche Anderson, Ford Motor Co.

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

This presentation shows the SCADE System product line for systems modeling and generation based on the SysML standard and the Eclipse Papyrus open source technology. SCADE System has been developed in the framework of Listerel, a joint laboratory of Esterel Technologies, provider of the SCADE�, and CEA LIST, project leader of the Eclipse component, Papyrus. From an architecture point of view, the Esterel SCADE tools are built on top of the SCADE platform which includes both SCADE Suite�, a model-based development environment dedicated to critical software, and SCADE System enabling model-based system engineering. SCADE System includes Papyrus, an open source component (under EPL license), integrated in the modeling platform of Eclipse. Using this integrated modeling platform, both system and software teams share the same environment for system development. Furthermore, other model-based tools can be added to the environment, due to the use of Eclipse.

The presentation provides an overview about the activities of Eurocae Working Group 72 (WG-72) starting with a brief synopsis of the context which suggested why such a committee should be established in 2006. It then goes into further detail about the drivers for the work of the committee, which call for the products to be delivered. It addresses some of the challenges with respect to its users. It points out that one of the lessons the committee learned was importance of the focus on the users, such that the products provide their maximum utility. Hence, the users should better be among the participants to achieve this objective. Other industries have dealt with the subject of Information System (or Cyber-Physical) Security long before this industry was forced to consider it. Consequently there are many industry standards and national or international norms, which may help to develop what is deemed needed for Civil Aviation.

Cyber security in the aviation industry, especially in relation to onboard aircraft systems, presents unique challenges in its implementation and management. The cyber threat model is constantly evolving and will continually present new and different challenges to the aircraft operator in responding to new cyber threats without either invoking a lengthy software update and re-certification process or limiting aircraft-to-ground communications to the threatened system or systems. This presentation discusses a number of system architectural options and developing technologies that could be considered to enhance the aircraft cyber protection and defensive capabilities of onboard systems as well as to minimize the effort associated with certification/re-certification. Some of these limit the aircraft?s vulnerabilities or in cyber terms, its ?threat surface?.