Search Results

The three major challenges in the power electronics in hybrid and electric vehicles are: System cost, power density and reliability. High temperature power device and packaging technologies increases the power density and reliability while reducing system cost. Advanced Silicon devices with synthesized high-temperature packaging technologies can achieve junction temperature as high as 200C (compared to the present limitation of 150C) eliminating the need for a low-temperature radiator and therefore these devices reduces the system cost. The silicon area needed for a power inverter with high junction temperature capability can be reduced by more than 50 - 75% thereby significantly reducing the packaging space and power device and package cost. Smaller packaging space is highly desired since multiple vehicle platforms can share the same design and therefore reducing the cost further due to economies of scale.

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.

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.

Trans Tech recently debuted the all-electric eTrans school bus providing a total zero emission school bus. The presentation will demonstrate Smith Electric Vehicles and their history with electric vehicles. The presentation will help ensure that everybody has an idea of what the electric school bus will do and to dispel any rumors about the vehicle. Presenter Brian S. Barrington, Trans Tech. Bus

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.

With nearly 220,000 vehicles, the United States Postal Service (USPS) has the largest non-military vehicle fleet in the world. This fleet requires over a billion dollars of fuel annually, and this figure does not include contracted vehicles. As a part of the business strategy, the USPS has embraced and invested in alternative fueled vehicles since 1899, when the first recorded use of an electric vehicle for USPS service was performed as a technology evaluation in Cleveland, OH. As part of a technology evaluation of advanced vehicle systems, the USPS has partnered with the DOE?s Vehicle Technology Program (VTP) to benchmark and quantify the capabilities of five vehicles in meeting specific Urban Route Delivery requirements, both with dynamometer and in-service testing. The all electric vehicle conversions have been developed by established electric vehicle systems manufacturers representing various perspectives on meeting the vehicle specific operation objectives.

With the introduction of the Chevrolet Volt, the Electrification of the Automobile begins in earnest, by offering a car that runs off of grid energy that has mass market appeal. The Volt offers a vehicle which is driven primarily by electricity under ?real world? driving conditions, while not presenting the driver with inconvenient choices about range and recharge time, or the disconcerting experience of a real possibility of becoming stranded. The Voltec powertrain arrangement enables the Volt to be an Extended Range Electric Vehicle, or E-REV and gives full performance utilizing only electrical energy from the grid for most driving, and a seamless transition to gasoline energy for longer and less frequent trips to maintain full vehicle utility. General Motors and its suppliers has had to the lead developments of fundamental component technologies that were not addressed by earlier, more simple hybridization work.

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 System Architecture Virtual Integration (SAVI) program is a collaboration of industry, government, and academic organizations within the Aerospace Vehicle System Institute (AVSI) with the goal of structuring a new integration process that relies on a single-truth architectural framework. The SAVI approach of Integrate, then Build provides a modern distributed development environment which arrests the propagation of requirements errors through the development life cycle. It does so by capturing design assumptions and shared properties of the system design in an authoritative, annotated architectural model. This reference model provides a common, analyzable framework for confirming that system requirements remain complete, consistent, and correct at all levels of system decomposition. Core concepts of SAVI include extensive use of model-based system engineering tools and use of a single-truth reference architectural model.

By introducing the concept of a separation between graphics and logic, interpreted run time architecture, and defined communication protocol, the ARINC 661 standard has addressed many of the concerns that aircraft manufacturers face when creating cockpit avionics displays. However, before kicking off a project based on the standard, it is important to understand all aspects of the standard, as well as the benefits and occasional drawbacks of developing with ARINC 661 in mind. This white paper will first provide an overview of ARINC 661 to clarify its concepts and how these relate to the development process. The paper will also describe the benefits of using a distributed development approach, and will outline practical, real world considerations for implementing an ARINC 661-based solution. Finally, readers will learn how commercial tools can be used to simplify the creation of displays following the standard to speed development and reduce costs.

The aerospace industry has long sought a solution for storing maintenance history information directly on aircraft parts. In 2005 leading airframe manufacturers determined that passive Radio Frequency Identification (RFID) technology presented a unique opportunity to address this industry need. Through the efforts of the Air Transport Association (ATA) RFID on Parts Committee and SAE International testing standards and data specifications are in place to support the broad adoption of passive RFID for storing parts history information directly on aircraft parts. The primary focus of the paper will be on the SAE AS-5678 environmental testing standard for passive RFID tags intended for aircraft use. Detail will be provided to help aerospace manufacturers understand their role and responsibilities for current programs and understand how this may impact their parts certification process.

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.

The OBD approval process can be a frustrating time for both manufacturer and ARB staff. For manufacturers, a long approval process can sometimes mean accepting deficiencies prematurely in exchange for an approval. For ARB staff, they are inundated with highly technical information which they must review, garner understanding of and then apply their experience to evaluate it for compliance. OBD approval anxiety can be minimized, if not avoided, when manufacturers understand ARB�s expectations. This presentation will take you through some unwritten rules and common pitfalls which can impede the approval process, thus providing a guideline to a less painful and more efficient certification document review and approval. Presenter Mark Frank, Winterpark Engineering Llc

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.

PRESENTATION ABSTRACT (ROI Approval BOE021811-122) REVIEW OF UPDATED AEROSPACE RECOMMENDED PRACTICES ARP5061A, Guidelines for Testing and Support of Aerospace, Fiber Optic, Inter-Connect Systems RATIONALE: A single source document to capture current best practices, methods, test equipment, and materials that support fiber optic interconnect systems including high-density applications deployed in Aerospace platforms. SCOPE: This presentation will describe how the ARP5061 document provides the maintainer unique guidelines for optical performance testing of short haul fiber optic inter-connect systems used in aerospace vehicles. The focus of this document is to establish common pre and post installation test methods, equipment, materials, and troubleshooting methodologies. QUALIFICATIONS AND TRAINING STANDARDS: The repair and maintenance of a fiber optic system should ONLY BE PERFORMED by qualified personnel.

Can you become a visionary or are you born one? How does a visionary capture an opportunity and makes it a successful business? Are engineers more qualified to solve technical problems or run companies? SAE's "The Visionary's Take" addresses these and many other questions, by talking directly with those who have dared to tackle difficult engineering problems, and create real-life products out of their experience. In these short episodes, Sanjiv Singh and Lyle Chamberlain, respectively CEO and Chief Engineer from Near Earth Autonomy, talk about their experience in creating a brand-new company in the UAV world. Founded in 2011, Near Earth Autonomy brought together a group of engineers and roboticists, looking for unconventional solutions to very hard logistics problems, presenting danger to human life. The answers were developed by pushing technology to a higher level, testing quickly and often, and keeping an open mind to alternative ways of framing engineering challenges.