Search Results

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.

BMW, DaimlerChrysler, Motorola and Philips present their joint development activity related to the FlexRay communication system that is intended for distributed applications in vehicles. The designated applications for powertrain and chassis control place requirements in terms of availability, reliability and data bandwidth that cannot be met by any product currently available on the market under the testing conditions encountered in an automobile. A short look back on events so far is followed by a description of the protocol and its first implementation as an integrated circuit, as well as its incorporation into a complete tool environment.

The automakers that comprise MOST® describe the reasons for this decision. First, they present the automobile industry's needs relative to multimedia networks in vehicles. Then, they present the different aspects of the MOST® technology. Multimedia networks are used in the electronics market, but they do not meet the technical and industrial constraints of the automobile electronics, which is why six automakers are working on most technology under the aegis of ""Most Cooperation.'' The transmission rate is a decisive aspect in the selection of a multimedia network. The rate of sound and video applications require fiber optics. The multimedia network rate must be adequate for a vehicle equipped with the maximum number of options, but the maximum rate is limited by the number of passengers.

This paper presents new comfort and convenience features in the luxury segment and focuses especially on Comfort Access and iDrive. The Comfort Access System offers the customer the possibility of unlocking the vehicle without active use of a key, of starting the engine and at the end of the journey of locking the car again. The aim of the iDrive concept was to enable intuitive operation of the various functions with simultaneously improved ergonomics. Both, a monitor and a controller with its variable haptic are the concept’s innovation. In addition, this paper also discusses future ECU (Electronic Control Unit) networks for body electronics. The focus is on package-driven ECU network architecture, having many functions developed by different suppliers on a single ECU.

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.

Handling characteristics, ride comfort and active safety are customer relevant attributes of modern premium vehicles. Electronic control units offer new possibilities to optimize vehicle performance with respect to these goals. The integration of multiple control systems, each with its own focus, leads to a high complexity. BMW and ITK Engineering have created a tool to tackle this challenge. A simulation environment to cover all development stages has been developed. Various levels of complexity are addressed by a scalable simulation model and functionality, which grows step-by-step with increasing requirements. The simulation environment ensures the coherence of the vehicle data and simulation method for development of the electronic systems. The article describes both the process of the electronic control unit (ECU) development and positive impact of an integrated tool on the entire vehicle development process.

The increasing number of local control units in automotive systems led to growing emphasis on developing and using multiplex systems. For reasons of price and robustness the use of asynchronous and slow multiplex systems is preferred. Since the communication volume now reaches critical dimensions in peak load situations during the use of those systems, new concepts on different communication levels have to be developed. Due to the use of many different message types (wide range of message length) and the statistical dependence of the communication behaviour of control units (e.g. question-answer-combinations), the application of standard methodologies is only partly suitable for a performance analysis of automotive multiplex systems.

The individual development process for distributed, communicating electronic control units hinders the integration of Automotive systems and increases the overall costs. In order to facilitate such applications, services and protocols for Communication, Network Management, and Operating System must be standardized. The aim of the OSEK project is to work out a respective specification proposal in cooperation with several car manufacturers and suppliers. This will permit a cost-effective system integration and support the portation of system functions between different electronic control units.

The increasing complexity of communication protocols for asynchronous multiplex systems requires the use of simulation during the optimisation of these protocols or the integration of other control units. Consideration of realistic communication behaviour of the connected control units is essential for performance analysis of multiplex systems. For a first pass, the use of simple statistical distributions (e.g. Poisson distribution) is suitable to get some simulation results. A better way to get realistic results is the approximation of empirical communication data through the use of more complex statistical distribution (e.g. mixed Erlang distributions). In this paper several approaches for the approximation of empirical data are presented. Beside simple statistical distributions (with one parameter), the use of more complex statistical distributions is discussed and methods for the identification of their parameters are 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.

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 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.

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.

The permanently increasing number of convenience and safety functions leads to higher complexity of in-car electronics and the rapidly growing amount of sensors, actuators and electronic control units places higher demands on high- speed data communication protocols. Safety-critical systems need deterministic protocols with fault-tolerant behavior. The need for on-board diagnosis calls for flexible use of bandwidth and an ever-increasing number of functions necessitates a flexible means of extending the system. None of the communication solutions available on the market until now (like CAN or TTP) have been able to fulfill all these demands. To solve these problems, BMW together with several semiconductor companies has developed a new protocol for safety-critical applications in automotive vehicles.