Search Results

This paper describes a novel approach for modeling an automotive HVAC unit. The model consists of black-box models trained with experimental data from a self-developed measurement setup. It is capable of predicting the temperature and mass flow of the air entering the vehicle cabin at the various air vents. A combination of temperature and velocity sensors is the basis of the measurement setup. A measurement fault analysis is conducted to validate the accuracy of the measurement system. As the data collection is done under fluctuating ambient conditions, a review of the impact of various ambient conditions on the HVAC unit is performed. Correction models that account for the different ambient conditions incorporate these results. Numerous types of black-box models are compared to identify the best-suited type for this approach. Moreover, the accuracy of the model is validated using test drive data.

Today's automotive software integration is a static process. Hardware and software form a fixed package and thus hinder the integration of new electric and electronic features once the specification has been completed. Usually software components assigned to an ECU cannot be easily transferred to other devices after they have been deployed. The main reasons are high system configuration and integration complexity, although shifting functions from one to another ECU is a feature which is generally supported by AUTOSAR. The concept of a Virtual Functional Bus allows a strict separation between applications and infrastructure and avoids source code modifications. But still further tooling is needed to reconfigure the AUTOSAR Basic Software (BSW). Other challenges for AUTOSAR are mixed integrity, versioning and multi-core support. The upcoming BMW E/E-domain oriented architecture will require all these features to be scalable across all vehicle model ranges.

a practice-oriented approach for an accelerated product development and product design process for mechatronic systems is presented. The handling of complex and versatile product data to perform this process is shown in the area of electrical drives and actuators in cars. It is discussed, how the coordination of all the necessary disciplines as development, design, testing field, specification and release management should be software supported and PDM integrated. The advantages and benefits of the presented methods are shown on particular examples. The necessary software modules are introduced, showing that the realized solution gives both opportunities - the integration into a PDM backbone and at the same time an independent communication within department and/or company. The practical way, to realize the expert-specific needs of the development department, which is not possible with a general PDM system is pointed out.

Over the past decades, interior noise from wind noise or engine noise have been significantly reduced by leveraging improvements of both the overall vehicle design and of sound package. Consequently, noise sources originating from HVAC systems (Heat Ventilation and Air Conditioning), fans or exhaust systems are becoming more relevant for perceived quality and passenger comfort. This study focuses on HVAC systems and discusses a Flow-Induced Noise Detection Contributions (FIND Contributions) numerical method enabling the identification of the flow-induced noise sources inside and around HVAC systems. This methodology is based on the post-processing of unsteady flow results obtained using Lattice Boltzmann based Method (LBM) Computational Fluid Dynamics (CFD) simulations combined with LBM-simulated Acoustic Transfer Functions (ATF) between the position of the sources inside the system and the passenger’s ears.

Nowadays, a continually growing system complexity due to the development of an increasing number of vehicle concepts in a steadily decreasing development time forces the engineering departments in the automotive industry to a deepened system understanding. The virtual design and validation of individual components from subsystems up to full vehicles becomes an even more significant role. As an answer to the challenge of reducing complete hardware prototypes, the virtual competence in NVH, among other methods, has been improved significantly in the last years. At first, the virtual design and validation of objectified phenomena in analogy to hardware tests via standardized test rigs, e.g. four poster test rig, have been conceived and validated with the so called MBS (Multi Body Systems).

The potential to reduce the cost of embedded software by standardizing the application behavior for Automotive Body and Comfort domain functions is explored in this paper. AUTOSAR, with its layered architecture and a standard definition of the interfaces for Body and Comfort application functions, has simplified the exchangeability of software components. A further step is to standardize the application behavior, by developing standard specifications for common Body and Comfort functions. The corresponding software components can be freely exchanged between different OEM/Tier-1 users, even if developed independently by multiple suppliers. In practice, individual OEM users may need to maintain some distinction in the functionality. A method of categorizing the specifications as ‘common’ and ‘unique’, and to configure them for individual applications is proposed. This allows feature variability by means of relatively simple adapter functions.

This paper presents an object-oriented method customized for a tool-assisted development of car software components. Tough market conditions motivate smart software development. ASCET SD is a tool to generate target code from graphic specifications, avoiding costly programming in C. But ASCET lacks guidelines on what to do, how to do it, in what order, like a fully equipped kitchen without a cooking book. Plans to employ the tool for BMW vehicle software sparked off demand for an adequate, object-oriented real-time methodology. We show how to scan the methodology market in order to adopt an already existing method for this purpose. The result of the adaptation of a chosen method to ASCET SD is a pragmatic version of ROOM, which we call BROOM. We present a modeling guidebook that includes process recommendations not only for the automotive sector, but for real-time software development in general.

Two models for the forecast of road traffic emissions, independently developed in parallel, are comparatively presented and assessed: EPROG developed by BMW and enlarged by VDA for a national application (Germany) and FOREMOVE, developed for application on European Community scale. The analysis of the methodological character of the two algorithms proves that the models are fundamentally similar with regard to the basic calculation schemes used for the emissions. The same holds true as far as the significant dependencies of the emission factors, and the recognition and incorporation of the fundamental framework referring to traffic important parameters (speeds, mileage and mileage distribution etc) are concerned.

Increasing demand for utilities like navigation systems or user-defined electronic phonebooks on one hand and sophisticated engine and gear controls on the other hand leads to growing bus load between distributed local control units. This paper shows the benefits and the characteristics of various state of the art data-compression algorithms and their impact on typical automotive multiplex dataclasses. The evaluation and optimization of promising algorithms can be done via a proposed “communications prototyping”-approach. The hardware/software components of such a rapid prototyping package are outlined. Finally, first performance results of suitable data-compression measures are presented.

This paper describes the first results from the AutoMoDe project (Automotive Model-based Development), where an integrated methodology for model-based development of automotive control software is being developed. The results presented include a number of problem-oriented graphical notations, based on a formally defined operational model, which are associated with system views for various degrees of abstraction. It is shown how the approach can be used for partitioning comprehensive system designs for subsequent implementation-related tasks. Recent experiences from a case study of an engine management system, specific issues related to reengineering, and the current status of CASE-tool support are also presented.

Multicore-based ECUs are increasingly used in embedded automotive software systems to allow more demanding automotive applications at moderate cost and energy consumption. Using a high number of parallel processors together with a high number of executed software components results in a practically unmanageable number of deployment alternatives to choose from. However correct deployment is one important step for reaching timing goals and acceptable latency, both also a must to reach safety goals of safety-relevant automotive applications. In this paper we focus at reducing the complexity of deployment decisions during the phases of allocation and scheduling. We tackle this complexity of deployment decisions by a mixed constructive and analytic approach.

Timing evaluation methods help to design a robust and extendible E/E architecture (electric/electronic). BMW has introduced the systematic application of such methods in the E/E design process within the last three years. Meanwhile, most of the architectural changes are now verified by a tool-based, automatic real-time analysis. This has increased the accuracy of the network planning and productivity of the BMW network department. In this paper, we give an overview of the actual status of timing evaluations in BMW's E/E architecture design. We discuss acceptance criteria, analysis metrics, and design rules, as far as these are related to timing. We look specifically at automation options, as these improve the productivity further. We will see that timing analysis has matured and should be mandatory for application in mass production E/E architecture development. At the same time, there is room for future improvements.

Increasing demand for dynamically controlled safety features, passenger comfort, and operational convenience in upper class automobiles requires an intensive use of electronic control units including software portions. Modeling, simulation, rapid prototyping, and verification of the software need new technologies to guarantee passenger security and to accelerate the time-to-market of new products. This paper presents the state-of-the-art of the design methods for the development of electronic control unit software at BMW. These design methods cover both discrete and continuous system parts, smoothly integrating the respective methods not merely on the code level, but on the documentation, simulation, and design level. In addition, we demonstrate two modeling and prototyping tools for discrete and continuous systems, namely Statemate and MatrixX, and discuss their advantages and drawbacks with respect to necessary prototyping demands.

How can car manufacturers, which are primary mechanical engineers, become software specialists? This is a question of prime importance for car electronics in the future. Modern vehicles offer a large number of electronic and software based functions to achieve a high level of safety, fuel economy, comfort, entertainment and security which are developed under pressure of regulations, of consumers needs and of competitive time to market aspects. This contribution draws a picture, what could be important in future for in car communication and information system in terms of development process, HW & SW architectures, partnerships in automotive industry and security of industrial properties. For this purpose the automotive development is reviewed and actual examples of system designs are given.

This paper presents the challenges in automotive electronics. Considering the deficiencies of the current ECU (electronic control unit) design process, a new design process is outlined. This design process mainly focuses on the independence of the ECU hardware architecture development and the software function development.

From an acoustical point of view, the integration of seatbelt retractors in a vehicle is a real challenge that has to be met early in the vehicle development process. The buzz and rattle noise of seat belt retractors is a weak yet disturbing interior noise. Street irregularities excite the wheels and this excitation is transferred via the car body to the mounting location of the retractor. Ultimately, the inertia sensor of the locking mechanism is also excited. This excitation can be amplified by structural resonances and generate a characteristic impact noise. The objective of this paper is to describe a simulation method for an early development phase that predicts the noise-relevant low frequency local modes and consequently the contact of the retractor with the mounting panel of the car body via the finite element method.

The German funded project ARAMiS included work on several demonstrators one of which was a multicore approach on large scale software integration (LSSI) for the automotive domain. Here BMW and Audi intentionally implemented two different integration platforms to gain both experience and real life data on a Hypervisor based concept on one side as well as using only native AUTOSAR-based methods on the other side for later comparison. The idea was to obtain figures on the added overhead both for multicore as well as safety, based on practical work and close-to-production implementations. During implementation and evaluation on one hand there were a lot of valuable lessons learned about multicore in conjunction with safety. On the other hand valuable information was gathered to make it finally possible to set up a cost model for estimation of potential overhead generated by different integration approaches for safety related software functions.