Search Results

A full understanding and characterization of the near-field of diesel sprays is daunting because the dense spray region inhibits most diagnostics. While x-ray diagnostics permit quantification of fuel mass along a line of sight, most laboratories necessarily use simple lighting to characterize the spray spreading angle, using it as an input for CFD modeling, for example. Questions arise as to what is meant by the “boundary” of the spray since liquid fuel concentration is not easily quantified in optical imaging. In this study we seek to establish a relationship between spray boundary obtained via optical diffused backlighting and the fuel concentration derived from tomographic reconstruction of x-ray radiography. Measurements are repeated in different facilities at the same specified operating conditions on the “Spray A” fuel injector of the Engine Combustion Network, which has a nozzle diameter of 90 μm.

The field of automotive engineering has devoted much research to reduce fuel consumption to attain sustainable energy usage. Friction reductions in powertrain components can improve engine fuel economy. Quantitative accounting of friction is complex because it is affected by many physical aspects such as oil viscosity, temperature, surface roughness and component rotation speed. The purpose of this paper is two-fold: first, to develop a useful tool for evaluating the friction in engine and accessories based on test data; second, to exercise the tool to evaluate the fuel economy gain in a drive cycle for several friction reduction technologies.

This paper is part of a larger body of experimental and computational work devoted to studying the role of close-coupled post injections on soot reduction in a heavy-duty optical engine. It is a continuation of an earlier computational paper. The goals of the current work are to develop new CFD analysis tools and methods and apply them to gain a more in depth understanding of the different in-cylinder environments into which fuel from main- and post-injections are injected and to study how the in-cylinder flow, thermal and chemical fields are transformed between start of injection timings. The engine represented in this computational study is a single-cylinder, direct-injection, heavy-duty, low-swirl engine with optical components. It is based on the Cummins N14, has a cylindrical shaped piston bowl and an eight-hole injector that are both centered on the cylinder axis. The fuel used was n-heptane and the engine operating condition was light load at 1200 RPM.

Health Ready Components are essential to unlocking the potential of Integrated Vehicle Health Management (IVHM) as it relates to real-time diagnosis and prognosis in order to achieve lower maintenance costs, greater asset availability, reliability and safety. IVHM results in reduced maintenance costs by providing more accurate fault isolation and repair guidance. IVHM results in greater asset availability, reliability and safety by recommending preventative maintenance and by identifying anomalous behavior indicative of degraded functionality prior to detection of the fault by other detection mechanisms. The cost, complexity and effectiveness of the IVHM system design, deployment and support depend, to a great extent, on the degree to which components and subsystems provide the run-time data needed by IVHM and the design time semantic data to allow IVHM to interpret those messages.

Shadowgraph/schlieren imaging techniques have often been used for flow visualization of reacting and non-reacting systems. In this paper we show that high-speed shadowgraph visualization in a high-pressure chamber can also be used to identify cool-flame and high-temperature combustion regions of diesel sprays, thereby providing insight into the time sequence of diesel ignition and combustion. When coupled to simultaneous high-speed Mie-scatter imaging, chemiluminescence imaging, pressure measurement, and spatially-integrated jet luminosity measurements by photodiode, the shadowgraph visualization provides further information about spray penetration after vaporization, spatial location of ignition and high-temperature combustion, and inactive combustion regions where problematic unburned hydrocarbons exist. Examples of the joint application of high-speed diagnostics include transient non-reacting and reacting injections, as well as multiple injections.

Tracer-based PLIF temperature diagnostics have been used to study the distribution and evolution of naturally occurring thermal stratification (TS) in an HCCI engine under fired and motored operation. PLIF measurements, performed with two excitation wavelengths (277, 308 nm) and 3-pentanone as a tracer, allowed investigation of TS development under relevant fired conditions. Two-line PLIF measurements of temperature and composition were first performed to track the mixing of the fresh charge and hot residuals during intake and early compression strokes. Results showed that mixing occurs rapidly with no measureable mixture stratification remaining by early compression (220°CA aTDC), confirming that the residual mixing is not a leading cause of thermal stratification for low-residual (4-6%) engines with conventional valve timing.

The United States Department of Transportation (USDOT) and the Crash Avoidance Metrics Partnership-Vehicle Safety Communications 2 (CAMP-VSC2) Consortium (Ford, General Motors, Honda, Mercedes-Benz, and Toyota) initiated, in December 2006, a three-year collaborative effort in the area of wireless-based safety applications under the Vehicle Safety Communications-Applications (VSC-A) Project. The VSC-A Project developed and tested Vehicle-to-Vehicle (V2V) communications-based safety systems to determine if Dedicated Short Range Communications (DSRC) at 5.9 GHz, in combination with vehicle positioning, would improve upon autonomous vehicle-based safety systems and/or enable new communications-based safety applications.

Model-Based Development processes in the automotive industry typically use high-level modeling languages to build the reference models of embedded controllers. One can use formal verification tools to exhaustively verify these design models against their requirements, ensuring high quality models and a reduction in the cost and effort of functional testing. However, there is a gap, in terms of processes and tools, between the informal requirements and the formal specifications required by the verification tools. In this paper, we propose an approach that tries to bridge this gap by (i) identifying the verifiable requirements through a categorization process, (ii) providing a set of templates to easily express the verifiable requirements, and (iii) generating monitors that can be used as specifications in design verification tools. We demonstrate our approach using the Simulink Design Verifier tool for design verification of Simulink/Stateflow models.

In order to improve understanding of the primary atomization process for diesel-like sprays, a collaborative experimental and computational study was focused on the near-nozzle spray structure for the Engine Combustion Network (ECN) Spray D single-hole injector. These results were presented at the 5th Workshop of the ECN in Detroit, Michigan. Application of x-ray diagnostics to the Spray D standard cold condition enabled quantification of distributions of mass, phase interfacial area, and droplet size in the near-nozzle region from 0.1 to 14 mm from the nozzle exit. Using these data, several modeling frameworks, from Lagrangian-Eulerian to Eulerian-Eulerian and from Reynolds-Averaged Navier-Stokes (RANS) to Direct Numerical Simulation (DNS), were assessed in their ability to capture and explain experimentally observed spray details. Due to its computational efficiency, the Lagrangian-Eulerian approach was able to provide spray predictions across a broad range of conditions.

To cope with the increasing number of advanced features (e.g., smart-phone integration and side-blind zone alert.) being deployed in vehicles, automotive manufacturers are designing flexible hardware architectures which can accommodate increasing feature content with as fewer as possible hardware changes so as to keep future costs down. In this paper, we propose a formal and quantitative definition of flexibility, a related methodology and a tool flow aimed at maximizing the flexibility of an automotive hardware architecture with respect to the features that are of greater importance to the designer. We define flexibility as the ability of an architecture to accommodate future changes in features with no changes in hardware (no addition/replacement of processors, buses, or memories). We utilize an optimization framework based on mixed integer linear programming (MILP) which computes the flexibility of the architecture while guaranteeing performance and safety requirements.

When considering the addition of radio frequency reception and transmission equipment to the suite of electronics already installed on a modern motor vehicle, numerous issues must be considered and tested to ensure reliable and safe operation not only of the additional equipment but the vehicle itself. This paper addresses some of the major issues and suggests modest design and testing practices that will accomplish the desired reliability and safety. The modest design and testing proposed addresses good engineering practices of electrically bonding metallic surfaces of the vehicle, grounding equipment, shielding signal cables, introducing filters, and appropriately separating cables into bundles.

To address the growing need for detailed chemistry in engine simulations, new software tools and validated data sets are being developed under an industry-funded consortium involving members from the automotive and fuels industry. The results described here include systematic comparison and validation of detailed chemistry models using a wide range of fundamental experimental data, and the development of software tools that support the use of detailed mechanisms in engineering simulations. Such tools include the automated reduction of reaction mechanisms for targeted simulation conditions. Selected results are presented and discussed.

The US Air Force (USAF) has evolved a policy for the acquisition of fighter jet engines (FJE). In the 1970s and 1980s that policy placed a premium on FJE performance primarily measured by the metric: thrust/engine weight. In the 1990s, the USAF policy changed from an emphasis on performance to reduced life-cycle cost with a premium on sustainment. This paper reports the results of a study of how the USAF and Corporation Alpha (Alpha) have adapted their processes, practices, and policies to design, develop, manufacture, test, and sustain a family of FJEs. Each member of the family of FJEs is sequentially linked relative to insertion of technology designed to reduce sustainment costs. In addition to the technology linkages, the development of the family of FJEs selected for this case study is also tracked relative to US Department of Defense and USAF policy and industry design, build, and maintain processes, methods, and tools.

Key fobs, also known as remote keys or remote transmitters, have become a common piece of equipment in today's vehicle, being ubiquitous in every market segment. Once limited to remote locking and unlocking operations, today's key fobs can be used to control many comfort and security features beyond locking and unlocking, such as alarm system operation, vehicle locate, approach lighting, memory seat recall, and remote starting systems. Key fobs are designed to be easy to use as well as easy to carry and transport in personal containers, such as purses, pockets, wallets, and the like. Accordingly, as with other personal effects, key fobs and other portable remote devices can be lost or misplaced or can be otherwise difficult to find. Even with careful tracking of a remote device, children and pets, among other factors, can make location difficult. Moreover, multiple remote devices are often distributed with each vehicle.

The usage of multi-body dynamics tools for the prediction of vehicle system/sub-system loads, has significantly reduced the need to measure vehicle loads at proving grounds. The success of these tools is limited by the quality of the digital representations being used to simulate the physical test roads. The development of these digital roads is not a trivial task due to the large quantity of data and processing required. In the end, the files must be manageable in size, have a globally common format, and be simulation-friendly. The authors present a methodology for the development of high quality 3-dimensional (3-D) digital proving ground profiles. These profiles will be used in conjunction with a multi-body dynamics software package (ADAMS) and the FTire™ model. The authors present a case study below.

As an innovative electric vehicle with some new approaches to energy usage and vehicle performance balance, the Chevy Volt required a special relationship between the OEM and tire supplier community. This paper details this relationship and how advanced tools and technology were leveraged between OEM and supplier to achieve tire component and overall vehicle performance results.

For many years, the computer aided math model has been the foundation for lowering cost and reducing time to market for many manufacturing industries. The automotive industry applies a variety of tools and methods to evaluate the expected vehicle performance to a forever expanding set of requirements. These mathematical predictions of performance are then repeated for both a set of design cycles and a multitude of vehicles in the product portfolio. This paper presents a CAE perspective of the unique problems of the large scale virtual vehicle engineering factory and a set of solutions. Different strategies to create the various complex math models required are explored. These strategies include using COTS FEA pre-processers, producing FEA models internal to the CAD tools, as well as custom built tools, macros and process automation tools.

As part of standardizing the global portfolio, General Motors (GM) created an electrical architecture that will support the GM global product feature set. Introduced in 2009, this common electrical architecture is already being applied to multiple platforms in GM's regional engineering centers. The electrical architecture will be updated regularly to address the needs of new features in the automotive market and to take advantage of the latest technology advancements. The functional requirements of these new features result in technology challenges. In addition, many new features may result in challenges to the vehicle electrical architecture or the vehicle development process. The challenges have been evaluated so that needs and initiatives can be better understood.

Automotive HW/SW architectures are becoming increasingly complex to support the deployment of new safety, comfort, and energy-efficiency features. Such architectures include several software tasks (100+), messages (1000+), computational and communication resources (70+ CPUs, 10+ buses), and (smart) sensors and actuators (20+). To cope with the increasing system complexity at lowest development and product costs, highest safety, and fastest time to market, model-based rapid-prototyping development processes are essential. The processes, coupled with optimization steps aimed at reducing the number of software and hardware resources while satisfying the safety requirements, enable reduction of the system complexity and ease downstream testing/validation efforts. This paper describes a novel model-based design exploration and optimization process for the deployment of a set of software tasks on a dual-processor control module implementing a fail-safe strategy.

Vehicle development typically occurs by independently documenting requirements for individual subsystems, then packaging these subsystems into the vehicle and testing the feature operation at a higher level, across multiple subsystems. Many times, this independent development process results in integration problems at the vehicle level, such as incomplete feature execution, unexpected operation and information disconnects. The development team is left to debug and create inefficient patches at the vehicle level due to time constraints and / or planned release dates. Without architecting solutions at the feature level, miscommunication of expected feature operation leads to wasted time, re-work and customer dissatisfaction. While the development of vehicle level technical specifications provide feature expectations at the vehicle level, they do not solve the problem of how this operation is to be applied across multiple systems.