Search Results

The reduction of vehicle exhaust particle emissions is a success story of European legislation. Various particle number (PN) counters and calibration procedures serve as tools to enforce PN emission limits during vehicle type approval (VTA) or periodical technical inspection (PTI) of in-use vehicles. Although all devices and procedures apply to the same PN-metric, they were developed for different purposes, by different stakeholder groups and for different target costs and technical scopes. Furthermore, their calibration procedures were independently defined by different stakeholder communities. This frequently leads to comparability and interpretation issues. Systematic differences of stationary and mobile PN counters (PN-PEMS) are well-documented. New, low-cost PTI PN counters will aggravate this problem. Today, tools to directly compare different instruments are scarce.

Autonomous driving systems and connected mobility are the next big developments for the car manufacturers and their suppliers during the next decade. To achieve the high computing power needs and fulfill new upcoming requirements due to functional safety and security, heterogeneous processor architectures with a mixture of different core architectures and hardware accelerators are necessary. To tackle this new type of hardware complexity and nevertheless stay within monetary constraints, high performance computers, inspired by state of the art data center hardware, could be adapted in order to fulfill automotive quality requirements. The European Processor Initiative (EPI) research project tries to come along with that challenge for next generation semiconductors. To be as close as possible to series development needs for the next upcoming car generations, we present a hybrid semiconductor system-on-chip architecture for automotive.

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.

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.

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.

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.

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.

A new simulation tool was established and approved by TRW as part of the continuous improvement of the development process. This tool allows the OEM and the system supplier to keep high quality even with further reduced development times. The introduction of the tool in a side air-bag development program makes it possible to ensure high development confidence with a reduced number of vehicle crash tests and late availability of interior component parts.

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.

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.

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.

The new generation of drive-by-wire systems currently under development has demanding requirements on the electronic architecture. Functions such as brake-by-wire or steer-by-wire require continued operation even in the presence of component failures. The electronic architecture must therefore provide fault-tolerance and real-time response. This in turn requires the operating system and the communication layer to be predictable, dependable and composable. It is well known that this properties are best supported by a time-triggered approach. A consortium consisting of German and French car manufacturers and suppliers, which aims at becoming a working group within the OSEK/VDX initiative, the OSEKtime consortium, is currently defining a specification for a time-triggered operating system and a fault-tolerant communication layer.1 The operating system and the communication layer are based on applicable interfaces of the OSEK/VDX standard.

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.

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.

The environmental impact of the automobile and its components is of growing importance not only in public debates but also in the complex decision making process regarding future car concepts. To calculate the environmental compatibility of car components BMW has developed various quantifying instruments and a holistic Life-Cycle Analysis (LCA) approach. The development phase significantly affects the entire life-cycle of a product. Suitable design criteria, recycling requirements and in-house standards have therefore been developed and established. One of the most important objectives in optimizing the environmental compatibility of the automobile is the realization of intelligent lightweight concepts. This means one has to find the most appropriate solution in terms of ecology and economy. Due to modern development processes car manufacturers and their suppliers have to intensify their cooperation also in this area.

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.

As more automobile designs utilizing serial multiplex network protocols such as SAE J1850 and CAN go into production, automotive system designers must now seek ways to lower the cost of the multiplex communication devices used in order to allow the number of components communicating across the multiplex bus to expand. The first generation of J1850 multiplex devices were designed as the different versions of the protocol were being developed and as a result seem better suited for use as development tools rather than for use in cost-sensitive production applications. As the next generation of multiplex devices is being defined, a hard look needs to be taken at the actual system requirements for communication on a multiplex bus.