Search Results

For electric vehicles the ability for regenerative braking reduces the use of friction brakes. Particularly on the rear axle of vehicles with reduced dynamic requirements such as urban vehicles, this can offer a potential for downsizing or, in extreme cases, even the elimination of the friction brakes on the rear axle. Due to the fact that the rear axle service brakes also represent the typical parking brake location in SoA (State-of-Art) vehicles, a rigorous rethinking of the parking brake concept is necessary to incorporate safe vehicle standstill management for such novel brake system topology. This research study introduces a novel parking brake design that covers SoA but also legal requirements while retaining potentials associated with the elimination of the rear service brakes such as cost and packaging.

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.

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.

India has one of the highest growth rates of individual mobility in the world, as well as one of the largest numbers of road casualties. Modern active safety systems are slowly becoming established in the Indian passenger car market. The intension of this study is to investigate the effectiveness of the car safety feature Electronic Stability Control (ESC) for India. The Indian accidents has to be analysed to identify the reliable root cause. For this purpose, passenger car Loss of Control accidents were investigated in more detail with the aim of estimating the safety potential of ESC for India. A methodology is developed to extrapolate the in-depth accident database of Road Accident Sampling System for India (RASSI) to the entire accident situation in India. Loss of Control accidents are analysed with regard to their root causes, crash consequences and contributing factors.

The ongoing changes in the development of new power trains and the requirements due to driver assistance systems and autonomous driving could be the enabler for completely new brake system configurations. The shift in the brake load collective has to be included in the systems requirements for electric vehicles. Many alternative concepts for hydraulic brake systems, even for decentralized configurations, can be found in the literature. For a decentralized system with all state of the art safety functionalities included, four actuators are necessary. Therefore, the single brake module should be as cost-effective as possible. Previous papers introduced systems which are for example based on plunger-like concepts, which are very expensive and heavy due to the needed gearing and design. In this paper a comparison between a state of the art hydraulic brake system using an electromechanical brake booster, and a completely new decentralized hydraulic brake concept is presented.

This paper describes how distributive computing along with statistical subsystem simulation can be applied to produce near production ready embedded vehicle software and calibrations. Coupling distributive computing and statistical simulation was first employed over a decade ago at General Motors to design and analyze propulsion subsystem hardware. Recently this method of simulation has been enhanced extending its capabilities to both test embedded vehicle code as well as develop calibrations. A primary advantage of this simulation technique is its ability to generate data from a statistically significant population of subsystems. The result is the acquisition of an optimal data set enabling the development of a robust design now including both embedded code and calibrations. Additionally it has been shown that there are significant economic advantages in terms of time and cost associated with this type of development when compared to traditional method.

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.

The Side View Assist is the World’s first rider assistance system for two-wheelers. This is a Blind Spot Warning system, which uses four ultrasonic sensors to monitor the surrounding of the rider. Whenever there is a vehicle (i.e. a car, truck, or another motorbike) in the rider’s blind spot, the technology warns the rider with an optical signal close to the mirror. This will allow the rider to avoid a collision when changing lanes. In the current vehicle application, Side View Assist is active at speeds ranging from 25 to 80 kilometers per hour and supports riders whenever the difference in relative speed to other road users is small. The system helps to improve safety especially in cities, where heavy traffic makes it necessary to change lanes more often. Originally such systems have been developed for cars and different system solutions for cars have been in serial production for several years. The challenge was to adapt these systems so they would work for two-wheelers as well.

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.

New technologies like alternative power trains and driver assistance systems have a big impact on brake system development. Most of the development work aims at the improvement of the actuation and modulation components of the brake system. The basic hydraulic network remained nearly the same over decades and still has to meet these new requirements. Previous papers have focused mainly on studying the behavior of single components, like for example the brake hose fluid consumption in detail. Other papers studied the complete system but simplified it extremely, so that some relevant effects are neglected. In this work, one focus is to study the influence of single relevant components, like the hydraulic unit and the hoses on the overall system performance. For this measurements with a complete hydraulic brake system, including a state of the art electromechanical brake booster and single component measurements for identification, are conducted.

Automotive vehicles today consist of very complex network of electronic control units (ECU) connected with each other using different network implementations such as Controller Area Network (CAN), FlexRay, etc. There are several ECUs inside a vehicle targeting specific applications such as engine, transmission, body, steering, brakes, infotainment/navigation, etc. comprising on an average more than 50 ECUs executing more than 50 million lines of software code. It is expected to increase exponentially in the next few years. Such complex electric/electronic (E/E) architecture and software calls for a comprehensive, flexible and systematic development and validation environment especially for a system level or vehicle level development. To achieve this goal, we have built a virtual multi-ECU high fidelity cyber-physical multi-rate cosimulation that closely resembles a realistic hardware based automotive embedded system.

Anti-lock Braking Systems (ABS) for motorcycles have already contributed significantly to the safety of powered two-wheelers (PTW) on public roads by improving bike stability and controllability in emergency braking situations. In order to address further riding situations, another step forward has been achieved with Motorcycle Stability Control (MSC) system. By combining ABS, electronically combined braking system (eCBS), traction control and inertial sensors even in situations like braking and accelerating in corners the riders' safety can be improved. The MSC system controls the distribution of braking and traction forces using an algorithm that takes into account all available vehicle information from wheels, power train and vehicle attitude. With its ability to control fundamental vehicle dynamics, the MSC system will be a basis for further development and integration of comprehensive safety systems.

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.

Motorized two wheelers, also known as powered two wheelers (PTW) are the most common mode of transportation in India. Around one in four deaths that occurred on the roads in India in 2012 involved a motorcyclist, according to Ministry of Road Transport and Highways. This constitutes the highest contributor for fatal accidents in India [1]. The European Transport Safety Council (ETSC) analysis shows the risk of a motorcyclist having a fatal accident is 20 times greater than for a car driver travelling the same route [2]. An investigation conducted by Bosch looked at the accident database of Road Accident Sampling System for India (RASSI). This investigation revealed interesting facts about the Indian motorcycle accident situation, such as root causes of powered two wheeler collisions and riders behaviour including their braking patterns during the pre-crash phase of the accident.

In the year of 2012 in India the total number of accidents with injuries is registered by Ministry of Road Transport and Highway with 490,383 out of which injured people are 509,667 and fatalities are 138,258 [1]. Nearly 17% of the fatalities are occupants of passenger cars which constitute the second highest contributor for fatal accidents in India [1]. In order to understand the root causes for car accidents in India, Bosch accident research carried out a study based on in-depth accidents collected in India. Apart from other accident contributing factors e.g. infrastructure the driver behaviour and his actions few milliseconds just prior to the crash is an extremely important and a key valuable data for the understanding of accident causation. Further on it supports also the development of modern automotive safety functions. Hence this research was undertaken to evaluate the benefit of the state-of-the art vehicle safety systems known as Antilock Braking System (ABS).

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.

Software quality is one of the biggest concerns of the automotive industry. Releasing a product with defects and having a recall can have enormous direct and indirect cost for an automotive OEM. In order to improve software quality is not sufficient to only increase the number of tests. It is extremely important to establish more sophisticated tests that can cover corner cases which are not unveiled during normal operation. Typically, corner cases are very difficult to test as those are often only triggered when the underlying hardware fails or the software gets unexpectedly corrupted. How to test those cases, to make sure that the right SW routines are executed and that the system moves back on time to a safe state? Fault-injection methods are typically used to cover a subset of these tests. However, there are quite some limitations on how effective and cost efficient existing methods can be applied for a more extensive coverage.

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