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.

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

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

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

We report here results from first year of the BMW MINI E deployment. BMW deployed 450 MINI E?s to North America. Nearly 50% were leased by households in Los Angeles and the New York area. PH&EV Center researchers surveyed MINI E drivers throughout their year with the vehicles, focusing on the experiences of 50 households who volunteered for more detailed interviews. We report here their experiences with driving electric vehicles, adaptions to daily range limitations, and using electricity as a fuel. Presenter Thomas Turrentine, Univ. of California-Davis

ECOtality North America, in partnership with the Idaho National Laboratory (INL), Nissan North America, General Motors, and over 40 government, electric utility, and private organizations, has launched a large-scale demonstration of electric vehicle charging infrastructure. This demonstration, called The EV Project, will deploy more than 15,000 level 2 and DC fast chargers in private residence, commercial, and public locations in seven market areas in Arizona, California, Oregon, Tennessee, Texas, Washington state, and Washington, D.C. The EV Project will also include a total of 5,700 Nissan Leaf battery electric vehicles and 2,600 Chevrolet Volt extended range electric vehicles, operated by consumers and fleets in each of the market areas. This demonstration, which is funded by the U.S. Department of Energy�s (DOE) Vehicle Technologies Program, represents the largest ever deployment of electric vehicles and charging infrastructure.

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.

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

Many manufacturing companies want to apply AFP technology to complex high-curvature part shapes. As new AFP machine technologies are developed to specifically apply material over complex shapes, new and innovative NC programming approaches are needed to successfully, reliably, and accurately apply material with good consolidation, while meeting the fiber direction and coverage requirements. A big issue with AFP is the production rate vs. part complexity. Most complex shapes can be created with a single .125? wide strip (tow) of material. But the production time would be impractically long. So machine builders create 6, 8, 16, even 32 tow AFP heads, and use the widest tow possible for the highest laydown rates. But then wide compaction rollers on these systems have difficulty consolidating material over curved surfaces, and the minimum steering radius of wider tows challenge the software?s ability to meet the layup requirements.

In recent years, all major microprocessor manufacturers are transitioning towards the deploymenet of multiple processing cores on every chip. These multi-core architectures represent the industry consensus regarding the most effective utilization of available silicon resources to satisfy growing demands for processing and memory capacities. Porting off-the-shelf software capabilities to multi-core architectures often requires significant changes to data structures and algorithms. When developing new software capabilities specifically for deployment on SMP architectures, software engineers are required to address specific multi-core programming issues, and in the ideal, must do so in ways that are generic to many different multi-core target platforms. This talk provides an overview of the special considerations that must be addressed by software engineers targeting multi-core platforms and describes how the Java language facilitates solutions to these special challenges.

This paper presents an extension of our earlier work on Cummins Vehicle Mission Simulation (VMS) software. Previously, we presented VMS as a Windows based analysis tool to simulate vehicle missions quickly and to gauge, communicate, and improve the value proposition of Cummins engines to customers. Presenter Nagesh Belludi, Cummins Inc.