Search Results

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.

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.

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.

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.

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 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.

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 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 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 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.

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.

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.

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.

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.

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 manufacturers of passenger cars increasingly assign development and production of complete subsystems to the supplying industry. A brake system supplier has to give predictions about system quality and performance long time before the first prototypical system is built or even before the supplier gets the order for system development. Nowadays, the usage of computer-aided system design and simulation is essential for that task. This article presents a tool designed to support the development process. A special focus will be on how to define quality. A formal definition of quality is provided, illustrated and motivated by two examples.

This paper will describe the procedures that will enhance the possibilities of qualitative evaluation of headlamp light distributions. A basis will be the description of a light distribution coming only from reflector geometries, i.e. headlamps with clear outer lens design. Further steps of evaluation, as visualization and homogeneity analysis become more and more important for a headlamp evaluation. The recently developed tools can support both the headlamp manufacturer and the car manufacturer in finding a common understanding in headlamp performance of a projected car at a very early stage of development.

Actual research results in the automotive field show that there is a big potential in increasing active and passive safety by implementing intelligent driver assisting systems. Realizing such safety related system functions requires an electronic system without mechanical or hydraulic backup to de-couple the human interface from the vehicle functions, e.g., steering and braking. Safety critical functions without mechanical backup enforce new requirements in system design. Any faulty behavior of a component within the system must not lead to a malfunction of the overall system. Consequently in the system design fault-tolerance mechanisms in real time must be introduced. Active replication of a functional node is a proper solution to guarantee this real time fault-tolerance. Redundancy management of the functional nodes can be implemented by fail-silent replicas, i.e. a node behaves correctly or does not produce any output at all.