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.

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.

Because of the rapidly increasing amount of electronic components and busses in a vehicle, the use of gateways in Electronic Control Units (ECUs) becomes more important. The upcoming question is how to design an optimal gateway. This paper describes a method for designing an optimal automotive gateway in an FPGA by using Evolutionary Algorithms (EAs). The complete gateway functionality is diagrammed in a specification graph which consists of a function graph and an architecture graph. The function graph describes the complete functionality of the gateway. The architecture graph shows the variety of the different implementation options of the mapped function graph. Each gateway task in the function graph can be realized either in a parallel way (different kinds of hardware implementations) or in a sequential way (software on a microprocessor core).

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.

Increasing vehicle complexity, broader vehicle variety, and global vehicle projects are a major challenge to all global vehicle manufacturers. Common vehicle projects not only require a common E/E-architecture in order to share components, but also a common diagnostic strategy. On-board and off-board strategies have been developed to achieve this goal. This paper will explain the importance of ISO-standardization, common networking & diagnostic architectures and standardized access to vehicle electronics. Also the need for a common diagnostic process chain throughout engineering, manufacturing and service, and the need for harmonized vehicle standards between passenger cars and heavy duty trucks will be addressed.

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.

1 A recent breakthrough in understanding the origin of ion signals from operating combustion engines [12] led to a new approach in integrating advanced ion current sensing into a compact ignition system. Thus it is now possible to continuously monitor mixture, ignition and combustion properties through online ion current recordings via a novel AC technique. In this paper this AC technique is compared to the standard DC technique and its known drawbacks: expensive high voltage components, sensitivity to plug fouling and expensive electronics. The AC technique is based on the specific properties of the electrical field of spark plugs being characterized by a point source with an extreme inhomogeneity of the electrical field due to the small center electrode. This causes a distinct diode characteristic of the ion signal: very low signals for negative voltages and high signals for positive ion sensing voltages, respectively.

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.

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.

The EU SPARC Project (Secure Propelled Vehicle with Advanced Redundant Control) has developed a new system architecture that enables effective application of driver assisted systems in an X-by-wire powertrain. A major challenge in the conception of such a system is development of a reliable electrical energy supply. A simulation is the most important tool for enabling the fundamental aspects to work, as for example, a dimensioning of the powernet. This article explains our approach in this SPARC simulation. We provide suggestions through examples of how to find simulation solutions for powernet dimensioning, as well as for the conception and validation of energy management strategies.

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.

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.