Search Results

Fuel economy of two-wheelers is an important factor influencing the purchasing psychology of the consumer within the emerging markets. Additionally, air pollution being a major environmental topic, there is a rising concern about vehicle emissions, especially in the big cities and their metropolitan areas. Potentially, the relatively expensive engine management systems are providing more features and value in comparison to the carburettor counterpart. The combustion system analysis is carried out on a 125 cm3 motorcycle engine and the subsequent numerical simulation comparing the carburettor and the Electronic (Port) Fuel Injection which provides a basis to establish the fuel consumption benefit for the electronic injection systems [1].

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.

Software-in-the-Loop (SiL) test environments are the ideal virtual platforms for enabling continuous-development, -integration, -testing -delivery or -deployment commonly referred as Continuous-X (CX) of the complex functionalities in the current automotive industry. This trend especially is contributed by several factors such as the industry wide standardization of the model exchange formats, interfaces as well as architecture definitions. The approach of frontloading software testing with SiL test environments is predominantly advocated as well as already adopted by various Automotive OEMs, thereby the demand for innovating applicable methods is increasing. However, prominent usage of the existing monolithic architecture for interaction of various elements in the SiL environment, without regarding the separation between functional and non-functional test scope, is reducing the usability and thus limiting significantly the cost saving potential of CX with SiL.

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.

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.

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.

A new physical layer for automobile class B communication networks is based on simple galvanic connections. Only ten passive external components per node are needed to perform reliable data transmission inside the hostile car environment. Every single fault related to the bus will be detected and diagnosed by every node, where a software controlled logic assures continuous data flow.

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.

The development in electronics for automotive application shows a high speed of improvement over the last 20 years regarding downsizing of all components. This could be achieved despite the harsh environmental conditions we find in vehicles, especially in the engine compartment. Big changes have always required the development of new technologies regarding the production of electronic components. The paper shows technologies which are right now under development to allow the next steps regarding downsizing as well as some examples of possible applications. There is also information regarding the current obstacles for improvements beyond this point as well as basic ideas how to overcome some of them.

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.

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.

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.

A major trend in modern vehicle control is the increase of complexity and interaction of formerly autonomous systems. In order to manage the resulting network of more and more integrated (sub)systems Bosch has developed an open architecture called CARTRONIC for structuring the entire vehicle control system. Structuring the system in functionally independent components improves modular software development and allows the integration of new elements such as integrated starter/generator and the implementation of advanced control concepts as drive train management. This approach leads to an open structure on a high level for the design of advanced vehicle control systems. The paper describes the integration of the spark-ignition (SI) engine management system (EMS) into a CARTRONIC conform vehicle coordination requiring a new standard interface between the vehicle coordination and the EMS level.

Connecting microcontrollers, sensors and actuators by several communication systems is state of the art within the electronic architectures of modern vehicles. The communication among these components is widely based on the event triggered communication on the Controller-Area-Network (CAN) protocol. The arbitrating mechanism of this protocol ensures that all messages are transferred according to the priority of their identifiers and that the message with the highest priority will not be disturbed. In the future some mission critical subnetworks within the upcoming generations of vehicle systems, e.g. x-by-wire systems (xbws), will additionally require deterministic behavior in communication during service. Even at maximum bus load, the transmission of all safety related messages must be guaranteed. Moreover it must be possible to determine the point of time when the message will be transmitted with high precision.

Automotive product lines promote reuse of software artifacts such as architectures, designs and implementations. System architectures, and especially software architectures, are difficult to create due to the need to support variations. Traditional approaches emphasize the identification and description of generic components, which makes it difficult to support variations among products. The paper proposes an approach for transforming a software architecture to product design through using patterns in a four-way refinement and evolution process. The paper investigates how patterns may be used to verify the conceptual integrity in the view integration procedure to support software sharing in an open automotive system.

This study reports on laser-based diagnostics to temporally track the evolution of liquid and gaseous fuel in the cylinder of a direct injection production type Diesel engine. A two-dimensional Mie scattering technique is used to record the liquid phase and planar laser-induced fluorescence of Diesel is used to track both liquid and vaporised fuel. LIF-Signal is visible in liquid and gas phase, Mie scattering occurs only in zones where fuel droplets are present. Distinction between liquid and gaseous phase becomes therefore possible by comparing LIF- and Mie-Signals. Although the information is qualitative in nature, trends of spray evolution are accessible. Within this study a parametric variation of injection pressure, in-cylinder conditions such as gas temperature and pressure as well as piston geometry are discussed. Observations are used to identify the most sensitive parameters and to qualitatively describe the temporal evolution of the spray for real engine conditions.

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.

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.

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.