Search Results

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.

Safety-critical embedded software has to satisfy stringent quality requirements. One such requirement, imposed by all contemporary safety standards, is that no critical run-time errors must occur. Runtime errors can be caused by undefined or unspecified behavior of the programming language; examples are buffer overflows or data races. They may cause erroneous or erratic behavior, induce system failures, and constitute security vulnerabilities. A sound static analyzer reports all such defects in the code, or proves their absence. Sound static program analysis is a verification technique recommended by ISO/FDIS 26262 for software unit verification and for the verification of software integration. In this article we propose an analysis methodology that has been implemented with the static analyzer Astrée. It supports quick turn-around times and gives highly precise whole-program results.

The new aerial communication protocol “Controller Area Network” (CAN) efficiently supports distributed realtime control in automotive applications. In order to unload CPUs from high-speed message transfer, dedicated CAN hardware handles messages up to the communication object level. In multiplex wiring message rates are one to two orders of magnitude lower, allowing to implement the upper communication level more cost-effectively in software. This reduces CAN interface hardware to bitwise protocol handling only. It may be incorporated even into low-end microcontrollers without significantly increasing chip size. Thus the same CAN protocol supports the entire range of serial automotive communication, matching implementation costs to requirements at each performance level.

In recent times, the software portion and the complexity of software within automotive electronic control units have grown noticeably and continue to grow. In order to get a grip on the software complexity and the amount of customer-specific software variants, a modeling concept for a structured and easily extensible software architecture is needed. This concept should efficiently support the formation of variants and code reuse without increasing runtime and memory space overhead. In this paper, we present our approach to such a modeling concept: The object-oriented modeling concept OMOS and its application to signal conditioning of vehicle control systems.

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.

Current exhaust gas emission regulations can only be well adhered to through optimal interplay of combustion engine and exhaust gas after-treatment systems. Combining a modern diesel engine with several exhaust gas after-treatment components (DPF, catalytic converters) leads to extremely complex drive systems, with very complex and technically demanding control systems. Current engine ECUs (Electronic Control Unit) have hundreds of functions with thousands of parameters that can be adapted to keep the exhaust gas emissions within the given limits. Each of these functions has to be calibrated and tested in accordance with the rest of the ECU software. To date this task has been performed mostly on engine test benches or in Hardware-in-the-Loop (HiL) setups. In this paper, a Software-in-the-Loop (SiL) approach, consisting of an engine model and an exhaust gas treatment (EGT) model, coupled with software from a real diesel engine ECU, will be described in detail.

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.

This paper describes the concept of the operating system ERCOS (Embedded Real-time Control Operating System). ERCOS has been specially designed to meet the functionality and performance requirements in the area of automotive applications. The ever increasing functional requirements for modern electronic control units are introducing considerable complexity in the area of software development. It is well known that real-time operating systems provide powerful means to handle complex functions under real-time constraints. Past experience, however, has shown that the efficiency and flexibility of operating systems was very often inadequate for automotive applications. To overcome these insufficiencies the operating system ERCOS has been designed with dedicated support for automotive requirements. This has been achieved by supplementing the run-time part of the operating system by powerful off-line tools.

Todays injection systems for diesel engines work with highly sophisticated mechanical governors. But only by electronic control of diesel injection systems will it be possible to comply with the emission regulations and to achieve better performance. In 1986 BOSCH started volume production of Electronic Diesel Control (EDC). This paper will concentrate on the electronic control unit (ECU) as it was designed for use in passenger cars. The production ECU and the planned next-step ECU are outlined, explaining hardware and software. An outlook of development goals of the future EDC control-units is given.

This paper shows that the functional integration of Electronic Throttle Control (ETC) into the engine control strategy allows improvements of emissions and fuel economy without making compromises in respect of driveability. A cost effective way for realizing ETC is the integration of the control electronics into the engine control unit (ECU). The paper describes the consequences of such an integration for the ECU hardware and software. Special attention is given to the ETC related safety aspects. Another chapter discusses different technologies for the throttle actuator drive. This is followed by a brief description of a suitable control strategy for a throttle actuator. Finally the paper gives also an overview about current status and development trends of accelerator pedal sensors necessary for ETC.

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.