Search Results

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.

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.

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 presents an after-treatment architecture combining a close coupled NOx trap and an under floor NOx trap. Instead of simply increasing the volume of the catalyst, we propose to broaden the active temperature window by splitting the LNT along the exhaust line. In order to design this architecture, a complete 1D model of NOx trap has been developed. Validated with respect to experimental data, this model has been useful to define the two volumes of LNT, making significant savings on the test bench exploitation. However, one of the main difficulties to operate the proposed architecture is the NOx purge and sulfur poisoning management. In order to optimize the NOx and sulfur purge launches, we have developed a control strategy based on an embedded reduced LNT model. These strategies have been validated on different driving cycles, by the means of simulation and of vehicle tests using rapid prototyping tools.

The energy management of a hybrid vehicle defines the vehicle power flow that minimizes fuel consumption and exhaust emissions. In a combined hybrid the complex architecture requires a multi-input control from the energy management. A classic optimal control obtained with dynamic programming shows that thanks to the high efficiency hybrid electric variable transmission, energy losses come mainly from the internal combustion engine. This paper therefore proposes a sub-optimal control based on the maximization of the engine efficiency that avoids multi-input control. This strategy achieves two aims: enhanced performances in terms of fuel economy and a reduction of computational time.

State of the art demonstrates that weight of vehicle increases with length of car body. Integration of powertrain in mid rear underfloor location enables to shorten car body by more than 0,5m and to save partially heavy longitudinal members. Underfloor integration of power train induces higher stance floor for more conviviality of passengers visibility. Safety factors are improved by lowering gravity centre, better repartition of front / rear masses during braking, easier management of crash by straighter and higher front longitudinal members and free front space. Space frame architecture simplifies light weight technologies application by using 2D bended aluminum profiles. Low investment is ensured by minimising castings application to suspension attachments and interlinking upperbody to underbody. Floor and external panels are designed for aluminum sheet stampings.

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.

The electric power required in automotive systems is quickly reaching a level that significantly impacts costs and fuel consumption. This drives the need to reconsider an electric energy management function. Fast evolving factors such as increasing power usage, and stricter engine management and reliability requirements necessitate a global vehicle approach to energy management. Innovations such as new powernet concepts (42 volt or dual voltage systems), new component technologies (high-performance energy storage, high efficiency and controllable generators), and global electronic and software architecture concepts will enable this new energy management concept. This paper describes key issues to maximize energy availability with reasonable components.

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.

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 following VAN concept led by a vehicle analysis: electrical architecture must not be basically changed in order to be cost effective; efficiency, interoperability and safety aspects must be rigorously respected to avoid lack of quality. As a consequence VAN solutions meet the requirement set concerning wiring, transceivers, protocol controllers and software services. Each of these solutions is optimized to assure safety and easy use. VAN transceivers support multiplexed applications - even high speed application - with conventional wiring. VAN controllers offer a large diversity of services, so allow the minimization of network load, of CPU load, with a high Real Time efficiency. Moreover their structure is very open to diagnosis requirements. VAN softwares provide simple, reliable, reusable mechanisms of sharing, exchange and synchronization. Such mechanisms minimize cost development and guarantee safety proofs in the liability context.