Search Results

This paper presents an overview of the evolution & revolution of automotive E/E architectures and how we at Bosch, envision the technology in the future. It provides information on the bottlenecks for current E/E architectures and drivers for their evolution. Functionalities such as automated driving, connectivity and cyber-security have gained increasing importance over the past few years. The importance of these functionalities will continue to grow as these cutting-edge technologies mature and market acceptance increases. Implementation of these functionalities in mainstream vehicles will demand a paradigm shift in E/E architectures with respect to in-vehicle communication networks, power networks, connectivity, safety and security. This paper expounds on these points at a system level.

The development of future automotive electronic systems requires new concepts in the software architecture, development methodology and information exchange. At Bosch an XML and MSR based technology is applied to achieve a consistent information handling throughout the entire software development process. This approach enables the tool independent exchange of information and documentation between the involved development partners. This paper presents the software architecture, the specification of software components in XML, the process steps, an example and an exchange scenario with an external development partner.

Car Periphery Supervision (CPS) systems comprise a family of automotive systems that are based on sensors installed around the vehicle to monitor its environment. The measurement and evaluation of sensor data enables the realization of several kinds of higher level applications such as parking assistance or blind spot detection. Although a lot of similarity can be identified among CPS applications, these systems are traditionally built separately. Usually, each single system is built with its own electronic control unit, and it is likely that the application software is bound to the controller's hardware. Current systems engineering therefore often leads to a large number of inflexible, dedicated systems in the automobile that together consume a large amount of power, weight, and installation space and produce high manufacturing and maintenance costs.

This paper describes the concept of the Diagnostic System Management DSM which introduces an improved object-oriented software architecture in order to meet the high performance and reliability requirements of automotive On-Board Diagnostic Systems (OBD). DSM handles standard tasks and offers services to integrate diagnostic and control functions. This architecture enables the flexible composition of system-independent, reusable function implementations. Hence a distributed software development and software sharing are supported. The module DSM consists of a Fault Code Memory, an Inhibit Handler, a Validator and a Function Scheduler. Special care has been taken to achieve robustness against EMI effects. Bosch will use DSM in the future powertrain control systems.

Mathematical modelling has proved to be a valuable tool for understanding the performance of diesel injection systems. There are several programs for the simulation of conventional injection equipment, but up to now it has been very expensive to simulate new concepts of injection equipment. Therefore a general program system for simulation of transient hydraulic processes - especially in diesel injection systems - has been developped. By this system, any new injection equipment can be simulated user-friendly and without needing to write new programs. The differential equations are solved by mathematical methods, which promise stability in all conditions and offer short calculation times. Since 1983 the program system has been applied to a lot of non-conventional and conventional injection systems and has proved its reliability.

AUTOSAR (AUTomotive Open System ARchitecture) is a worldwide standard for automotive basic software in line with an architecture that eases exchange and transfer of application software components between platforms or companies. AUTOSAR provides the standardized architecture together with the specifications of the basics software along with the methodology for developing embedded control units for automotive applications. AUTOSAR matured over the last several years through intensive development, implementation and maintenance. Two main releases (R3.2 and R4.0) represent its current degree of maturity. AUTOSAR is driven by so called core partners: leading car manufacturers (BMW, Daimler, Ford, GM, PSA, Toyota, Volkswagen) together with the tier 1 suppliers Continental and Bosch. AUTOSAR in total has more than 150 companies (OEM, Tier X suppliers, SW and tool suppliers, and silicon suppliers) as members from all over the world.

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.

The car industry has reached a point where electronic systems, which were so far essentially autonomous, begin to grow together to a Car-Wide Web. The main driving force is the demand for more safety, security, and comfort implemented economically. Already various parties are working on control networks. In the long run, vehicle motion and dynamic systems, safety, security, comfort as well as mobile multimedia systems will integrate and reach out for the vision of accident-free, comfortable, and well-informed driving. As a foundation for a Car-Wide Web, Bosch is developing an open architecture called CARTRONIC. The essence of CARTRONIC is to define structuring rules, modeling rules and patterns for total, integrated control of vehicles. The rules and patterns allow the mapping of high-level functions onto several physical implementations, for instance one logical description of functional connections could be created for cars with different equipment packages.

The continuously increasing performance of modern automotive microelectronics is leading to ever more complex open and closed-loop control functions. Rigid mechanical connections a broken down and electronics applied to make them controllable. Among the examples are camshaft control, or future systems for variable valve-lift control. In addition, the individual systems in the vehicle, such as engine management, transmission-shift control, and ABSR will be networked with one another. The result is a system alliance which communicates through a car-wide web. The major challenge posed by this development in the future, lies in still being able to reliably control the complexity of the system alliance from the point of view of reliability and safety. This means that the suitable sensor and actuator basis, together with an architecture having fixed configuration rulings and matching development methods, are indispensable.

In order to master the increasing complexity of electrical/electronic (E/E) systems in vehicles, E/E architecture design has become an established discipline. The task of the E/E architecture design is to come up with solutions to challenging and often contradictory requirements such as reduced cost and increased flexibility / scalability. One way to optimize the E/E architecture in terms of cost (electronics & wiring harness) is to integrate functions. This can be done by either combining functions from multiple ECUs into a single ECU or by introducing Domain Control Units. Domain Control Units provide the main software functionality for a vehicle domain, while relegating the basic functions of actuator control to connected intelligent actuators. Depending on the different market segments (low price, volume and premium) and the different vehicle domains, the actual usage of Domain Control Units can be quite different and sometimes questionable.

Dynamic route guidance is a main feature when discussing traffic telematics systems. At the present time, several system concepts are in the development or implementation stage. The key elements of dynamic route guidance systems are illustrated in the following. Two approaches could be used when designing the system architecture: 1. Centralized routing in traffic information centers combined with on-board terminals. 2. Mobile routing by on-board navigation units which use information received from traffic information centers. The different approaches are presented in this paper. The influences on component design and the effects on communication needs are discussed. This leads to the “hybrid” system architecture which is presented including implementation examples.

Signals in Automotive Communication Networks often represent safety relevant information. Therefore, automotive network protocols provide multiple powerful mechanisms for error detection and for error reporting. The objective is to ensure that on average less than one undetected error occurs during the lifetime of a vehicle. This places an upper bound on the residual error probability of the communication network. The determination of this residual error probability requires new methods in order to account for the interaction of the various error detection mechanisms. This paper presents an analysis method that has been developed for the investigation of the CAN protocol. This comprehensive investigation distinguishes two types of errors that contribute most significantly to the residual error probability of the CAN protocol. Errors of one type transform stuffbits into information bits or vice versa, and are related to the use of variable bit stuffing.

The development of vehicle communication networks is challenged not only by the increasing demand in data exchange and required data rate but also the need to connect the vehicle to external sources for personal connectivity of driver and car to infrastructure applications. Solutions are required to master complexity of in-vehicle communication networks, e.g. diagnostic access, flashing of Electronic Control Units, the data backbone connecting the vehicle domains and the data transfer of cameras. Safety (data transfer) and security (violation) issues of the communication networks gain more importance especially by introducing interfaces to external sources either via mobile devices or by connecting the vehicle to other external sources, e.g. Internet and Car to Infrastructure applications. The Internet Protocol (IP) appears to be an ideal solution to address these challenges, especially in connection with an Ethernet physical layer for fast data transfer.

As automobiles become increasingly smarter, the need to understand within the automotive software the physical behavior of its parts is growing as well. The laws of physics governing such behavior are mostly formulated as differential equations, which today are usually created or obtained from various modeling tools. For solving them, the tools offer several solvers to satisfy the requirements of different problems. E.g. simple and fast explicit low order solvers for non-stiff problems and more complex implicit solvers for stiff problems. Though the modeling and code generation features as available in such tools are desirable for embedded automotive software, they cannot be used directly due to special restrictions with respect to hard realtime constraints. One such restriction is the organization of automotive software in components complying with the AUTOSAR standard which is not widely supported by the modeling tools.

Many software functions currently available in the engine control units have been developed for several years (decades in some cases), reengineered or adapted due to new requirements, what may add to their inherent complexity an unnecessary complication. This paper deals with the study and implementation of a software reengineering strategy for the embedded domain, which is in transfer from research department to product development, here applied to improve maintainability of flex fuel functions. The strategy uses the SCODE “Essential Analysis”, an approach for the embedded system domain. The method allows to reduce the system complexity to the unavoidable inherent problem complexity, by decomposing the system into smaller sub problems based on its essential physics. A case study was carried out to redesign a function of fuel adaptation. The analysis was performed with the support of a tool, which covers all the phases of the method.

The particulate emissions can be reduced by increasing injection pressure. The NOx-emission can be lowered to the required amount with a retarded injection-begin. These measures raise fuel consumption by approximately 8-10 %. To avoid blue smoke from the cold engine, it is advantageous that the fuel injection is advanced during the warm-up period. These statements apply for injection systems with unit injectors as well as for pump-line-nozzle-systems. In this paper, the pump-line-nozzle-system will be described. With this system, injection pressures of 1200 to 1400 bar at the injection nozzle are reached. The injection-begin can be changed with a control-sleeve in-line pump. The injection-begin and fuel quantity can be flexibly and accurately adjusted by means of an electronic governor.

In the next 20 years the share of small electric vehicles (SEVs) will increase especially in urban areas. SEVs show distinctive design differences compared to traditional vehicles. Thus the consequences of impacts of SEVs with vulnerable road users (VRUs) and other vehicles will be different from traditional collisions. No assessment concerning vehicle safety is defined for vehicles within European L7e category currently. Focus of the elaborated methodology is to define appropriate test scenarios for this vehicle category to be used within a virtual tool chain. A virtual tool chain has to be defined for the realization of a guideline of virtual certification. The derivation and development of new test conditions for SEVs are described and are the main focus of this work. As key methodology a prospective methodical analysis under consideration of future aspects like pre-crash safety systems is applied.

The release of ISO 26262 is only about three months after the 2011 World Congress. However, there are still some contentious aspects that can introduce challenges or cause a disproportionate effort. In this paper, we will show how to avoid these problems. ISO 26262 provides a detailed method for classifying the Automotive Safely Integrity Level (ASIL) of in-vehicle electronic systems. However, the ASIL value for a specific function/product can vary significantly across the industry. Applying a lower level than the industry norm can cause substantial liability problems. Applying a higher level can initiate an “arms race” with competitors. This is particularly true if there are no vehicle-related reasons for choosing the higher level or if it doesn't make the product any safer. To encourage international harmonization, this paper will define ASIL classifications for the main automotive components. Most functions/products are currently being developed using parts of existing products.

In the automotive industry a growing number of mono-functional control units with increasing complexity on one hand and requirements for reduced power con-sumption and mounting space on the other hand are enforcing an architectural change of the car electronics. Computer platforms with a client/server architecture are candidates to reduce the number of control units drastically followed by a reduction of costs, space and better integration possibilities for enhanced func-tionalities as well as additional services. The problem which comes up now if those architectures are coming to the cars is to cope with software complexity and reliability issues under the aspect of continuously evolving hardware infrastructure. To understand the problems better, the Corporate Engineering within Robert Bosch GmbH has build a multifunctional look-and-feel demonstrator in a first step using a component-based software architecture on a standard PC-platform. Experiences are reported.

Time Triggered CAN (TTCAN) is an extension of the well-known CAN protocol, introducing to CAN networks time triggered communication and a system wide global network time with high precision. Time Triggered CAN has been accepted as international standard ISOCD11898-4. The time triggered communication is built upon the unchanged standard CAN protocol. This allows a software implementation of the time triggered function of TTCAN, based on existing CAN ICs. The high precision global time however requires a hardware implementation. A hardware implementation also offers additional functions like time mark interrupts, a stopwatch, and a synchronization to external events, all independent of software latency times. The TTCAN testchip (TTCAN_TC) is a standalone TTCAN controller and has been produced as a solution to the hen/egg problem of hardware availability versus tool support and research.