Search Results

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.

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.

Engine Start/Stop systems reduce CO₂ emissions by turning off the combustion engine at vehicle standstill. This avoids the injection of fuel that would otherwise be needed simply to overcome internal combustion engine losses. As a next development step, engine losses at higher vehicle speeds are to be addressed. During deceleration, state-of-the-art engine technology turns off fuel injection as soon as the driver releases the gas pedal, thus the combustion engine is motored by the vehicle. The engine's drag torque could be desired by the driver, e.g., as a brake assist during downhill driving. However, quite frequently the driver wishes to coast at almost constant speed. Similar to Start/Stop operation, in such situations fuel is injected to simply overcome the combustion engine's drag torque. An operation mode referred to as "Free-Wheeling" reduces CO₂ emissions under such coasting conditions by disconnecting the combustion engine from the powertrain and by turning it off.

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.

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.

The conventional measurements to describe the photometric quality of headlamps usually only comprise the luminous flux and the illuminance (resp. the luminous intensity) in several measuring points given by Type Approval Legislation. Practically, these photometric measurements do not describe the visual impression of a headlamp light distribution sufficiently, neither in lab nor in real street geometry. With the clear outer lens headlamps introduced recently, filament images are projected directly onto the screens or streets, thus giving new impulses to research. Starting from the established photometric practice, other types of measurements and physiological fundamentals will be discussed. The basic tools to make physical measurement and physiological impression comparable, e.g. in terms of homogeneity, are shown.

Time Triggered CAN (TTCAN) is an extension of the well-known CAN protocol, introducing to CAN networks time triggered communication and a system wide global network time with high precision. Time Triggered CAN has been accepted as international standard ISOCD11898-4. The time triggered communication is built upon the unchanged standard CAN protocol. This allows a software implementation of the time triggered function of TTCAN, based on existing CAN ICs. The high precision global time however requires a hardware implementation. A hardware implementation also offers additional functions like time mark interrupts, a stopwatch, and a synchronization to external events, all independent of software latency times. The TTCAN testchip (TTCAN_TC) is a standalone TTCAN controller and has been produced as a solution to the hen/egg problem of hardware availability versus tool support and research.

In view of tight emission standards, injection strategies to reduce raw HC-emissions during the cold starting of port fuel injected engines are evaluated in this study. The relevance of spray targeting and atomization is outlined in the first part of this paper. The foundation and performance of different injector concepts with respect to spray characteristics are discussed. Laboratory experiments demonstrate that concepts relying on auxiliary energy, such as air-assistance, fuel heating and injection at elevated system pressures, are capable of producing spray droplet sizes in the SMD-range of 25μm. For future injection strategies aimed at the compliance of SULEV emission levels, this target value is considered to be essential. In the second part of this paper, emission tests of selected injector concepts are carried out using a V6-3.2I ULEV engine operated both in a vehicle and on a test bench.

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.

Many software functions currently available in the engine control units have been developed for several years (decades in some cases), reengineered or adapted due to new requirements, what may add to their inherent complexity an unnecessary complication. This paper deals with the study and implementation of a software reengineering strategy for the embedded domain, which is in transfer from research department to product development, here applied to improve maintainability of flex fuel functions. The strategy uses the SCODE “Essential Analysis”, an approach for the embedded system domain. The method allows to reduce the system complexity to the unavoidable inherent problem complexity, by decomposing the system into smaller sub problems based on its essential physics. A case study was carried out to redesign a function of fuel adaptation. The analysis was performed with the support of a tool, which covers all the phases of the method.

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.

Industry standards and practices define a number of mathematical and physical methods to estimate the cargo carrying volume capacity of a vehicle. While some have roots dating back decades, others try to assess the utility of the space for cargo by subjective measurements. Each these methods have their own inherent merits and deficiencies. The purpose of this paper is to highlight the differences in calculated cargo volume amongst the following practices: Society of Automobile Engineers (SAE) J1100[1] International Organization for Standardization (ISO 3832)[2], Global Car manufacturer's Information Exchange group (GCIE)[3], Consumer Reports[4]. This paper provides a method and associated rationale for constructing a new cargo volume calculation practice that attempts to harmonize these procedures into a more contiguous practice. This homologation will benefit publishing industry, vehicle manufacturers and customers alike.

The release of ISO 26262 is only about three months after the 2011 World Congress. However, there are still some contentious aspects that can introduce challenges or cause a disproportionate effort. In this paper, we will show how to avoid these problems. ISO 26262 provides a detailed method for classifying the Automotive Safely Integrity Level (ASIL) of in-vehicle electronic systems. However, the ASIL value for a specific function/product can vary significantly across the industry. Applying a lower level than the industry norm can cause substantial liability problems. Applying a higher level can initiate an “arms race” with competitors. This is particularly true if there are no vehicle-related reasons for choosing the higher level or if it doesn't make the product any safer. To encourage international harmonization, this paper will define ASIL classifications for the main automotive components. Most functions/products are currently being developed using parts of existing products.

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.

A numerical and corresponding experimental study was undertaken to identify the ability to accurately predict combustion performance using our 3-D numerical tools for a direct-injection homogeneous-charge engine. To achieve a significant range of combustion rates, the evaluation was conducted for the engine operating with and without enhanced charge motion. Five charge motion configurations were examined, each having different levels of swirl and tumble flow leading to different turbulence generation and decay characteristics. A detailed CFD analysis provides insight into the in-cylinder flow requirements as well as the accuracy of the submodels. The in-cylinder air-fuel distribution, the mass-averaged swirl and tumble levels along with mean flow and turbulent kinetic energies are calculated throughout the induction and compression processes.

The car industry has reached a point where electronic systems, which were so far essentially autonomous, begin to grow together to a Car-Wide Web. The main driving force is the demand for more safety, security, and comfort implemented economically. Already various parties are working on control networks. In the long run, vehicle motion and dynamic systems, safety, security, comfort as well as mobile multimedia systems will integrate and reach out for the vision of accident-free, comfortable, and well-informed driving. As a foundation for a Car-Wide Web, Bosch is developing an open architecture called CARTRONIC. The essence of CARTRONIC is to define structuring rules, modeling rules and patterns for total, integrated control of vehicles. The rules and patterns allow the mapping of high-level functions onto several physical implementations, for instance one logical description of functional connections could be created for cars with different equipment packages.