Search Results

The trend towards even more sophisticated driver assistance systems and growing automation of driving sets new requirements for the robustness and availability of the involved automotive systems. In case of an error, today it is still sufficient that safety related systems just fail safe or silent to prevent safety related influence of the driving stability resulting in a functional deactivation. But the reliance on passive mechanical fallbacks in which the human driver taking over control, being inevitable in such a scenario, is expected to get more and more insufficient along with a rising degree of driving automation as the driver will be given longer reaction time. The advantage of highly or even fully automated driving is that the driver can focus on other tasks than controlling the car and monitoring it’s behavior and environment.

This paper describes how a safety-oriented software development could look like as soon as an appropriate standard exists which is applicable for the automotive industry. Such a standard is currently being developed which is a tailoring of the safety standard IEC61508. The IEC61508 is generic and not specific for any industry. It allows tailoring of the complete safety lifecycle for specific domains. This paper focuses mainly on the software lifecycle of the evolving standard for the automotive industry. With regard to the development process the objectives of each phase are explained and it is described how these can be achieved by using certain techniques and measures.

The anti-lock braking system (ABS) is a widespread driver assistance system which allows a short braking distance while simultaneously maintaining the stability and steerability of the car. Vehicles with electric single-wheel drive offer many possibilities of improving the energy efficiency and the braking performance during ABS braking. In this paper, two different ways of including the electric machines in the ABS are analyzed in detail: the damping of torsional drive train vibrations in combination with recuperation and the dynamic split of the braking torque, where the hydraulic braking torque is kept constant and the dynamic modulation of the braking torque is performed by the electric machines. The damping algorithm is developed on the basis of a linearized model of the drive train and the tire-road contact by using state feedback and pole placement methods. Simulation results with a detailed multi-body system show the effectiveness of the control algorithms.

GTL (Gas-To-Liquid) fuel is well known to improve tailpipe emissions when fuelling a conventional diesel vehicle, that is, one optimized to conventional fuel. This investigation assesses the additional potential for GTL fuel in a GTL-dedicated vehicle. This potential for GTL fuel was quantified in an EU 4 6-cylinder serial production engine. In the first stage, a comparison of engine performance was made of GTL fuel against conventional diesel, using identical engine calibrations. Next, adaptations enabled the full potential of GTL fuel within a dedicated calibration to be assessed. For this stage, two optimization goals were investigated: - Minimization of NOx emissions and - Minimization of fuel consumption. For each optimization the boundary condition was that emissions should be within the EU5 level. An additional constraint on the latter strategy required noise levels to remain within the baseline reference.

Fully variable valve trains provide comprehensive means of adjustment in terms of variable valve timing and valve lift. The efficiency of the engine is improved in the operating range and in return, an increasing complexness of the mechanical design and control engineering must be handled. For optimization and design of these kinds of complex systems, detailed simulation models covering different physical domains, i.e. mechanics, hydraulics, electrodynamics and control are needed. Topic of this work is the variable valve train named Audi valvelift system (AVS) e.g. used in the Audi 2.8l V6 FSI engine. The idea of AVS is to use different cam lobes at different operating points. Each intake valve can be actuated by a large and a small cam. For full load, the two inlet valves are opened by the large cam profile - ideal for high charge volumes and flow speeds in the combustion chamber. Under partial load, the small cam profiles are used.

More and more high-level algorithms are emerging to improve the existing systems in a car. Often these algorithms only need a platform with a bus connection and some resources such as CPU time and memory space. These functions can easily be integrated into existing systems that have free resources. This paper describes some encapsulation techniques and mechanisms that can be used in the automotive domain. The discussion also takes into account the additional resources consumed on the microcontroller to meet these requirements and by the software to implement the encapsulation mechanisms. Overviews of some general concepts of software-architectures that provide encapsulation are also shown.

The increased pressure for power, space, and cost reduction in automotive applications together with the availability of high performance, automotive qualified multicore microcontrollers has lead to the ability to engineer Domain Controller ECUs that can host several separate applications in parallel. The standard automotive constraints however still apply, such as use of AUTOSAR operating system, support for legacy code, hosting OEM supplied code and the ability to determine warranty issues and responsibilities between a group of Tier 1 and Tier 2 vendors who all provide Intellectual Property to the final production ECU. Requirements for safety relevant applications add even more complexity, which in most current approaches demand a reconfiguration of all basic software layers and a major effort to redesign parts of the application code to enable co-existence on the same hardware platform. This paper outlines the conflicting requirements of hosting multiple applications.

The German funded project ARAMiS included work on several demonstrators one of which was a multicore approach on large scale software integration (LSSI) for the automotive domain. Here BMW and Audi intentionally implemented two different integration platforms to gain both experience and real life data on a Hypervisor based concept on one side as well as using only native AUTOSAR-based methods on the other side for later comparison. The idea was to obtain figures on the added overhead both for multicore as well as safety, based on practical work and close-to-production implementations. During implementation and evaluation on one hand there were a lot of valuable lessons learned about multicore in conjunction with safety. On the other hand valuable information was gathered to make it finally possible to set up a cost model for estimation of potential overhead generated by different integration approaches for safety related software functions.

ISO 26262 is the actual standard for Functional Safety of automotive E/E (Electric/Electronic) systems. One of the challenges in the application of the standard is the distribution of safety related activities among the participants in the supply chain. In this paper, the concept of a Safety Element out of Context (SEooC) development will be analyzed showing its current problematic aspects and difficulties in implementing such an approach in a concrete typical automotive development flow with different participants (e.g. from OEM, tier 1 to semiconductor supplier) in the supply chain. The discussed aspects focus on the functional safety requirements of generic hardware and software development across the supply chain where the final integration of the developed element is not known at design time and therefore an assumption based mechanism shall be used.

In the context of the ARAMiS project, AUDI AG contributed the development of a multi-core demonstrator based on car functions already in production. For this demonstrator, these legacy car functions were ported from single-core platforms to a multi-core platform to gain real world close-to-production experience while utilizing the new technology. For complex functions with high demands for computational resources, it may be necessary to distribute computation over several cores. In this context, we investigated the parallelization of a legacy sequential AUTOSAR function. A main contribution of this work is an analysis of mechanisms provided by AUTOSAR, their limitations and, possible remedy. This paper will point out observations and experiences during the development of this demonstrator and show practical solutions for parallelization in an AUTOSAR environment.

Multicore-based ECUs are increasingly used in embedded automotive software systems to allow more demanding automotive applications at moderate cost and energy consumption. Using a high number of parallel processors together with a high number of executed software components results in a practically unmanageable number of deployment alternatives to choose from. However correct deployment is one important step for reaching timing goals and acceptable latency, both also a must to reach safety goals of safety-relevant automotive applications. In this paper we focus at reducing the complexity of deployment decisions during the phases of allocation and scheduling. We tackle this complexity of deployment decisions by a mixed constructive and analytic approach.

Audi's successful 3.6 L V8 twin turbo Le Mans engine of 2000 has been developed to fuel direct injection (FSI®). Most of the modifications have been done in the area of the cylinderhead. Simulation and flow test bench work helped to define the basic parameters. The FSI® engine has a reduction in fuel consumption of 8 - 10 %, up to 9 % more torque throughout the entire speed range and much better driveability.

The increasing complexity of automotive functions which are necessary for improved driving assistance systems and automated driving require a change of common vehicle architectures. This includes new concepts for E/E architectures such as a domain-oriented vehicle network based on powerful Domain Control Units (DCUs). These highly integrated controllers consolidate several applications on different safety levels on the same ECU. Hence, the functions depend on a strictly separated and isolated implementation to guarantee a correct behavior. This requires middleware layers which guarantee task isolation and Quality of Service (QoS) communication have to provide several new features, depending on the domain the corresponding control unit is used for. In a first step we identify requirements for a middleware in automotive DCUs. Our goal is to reuse legacy AUTOSAR based code in a multicore domain controller.

With the ever increasing amount of available software processing resources in a vehicle, more and more high-level algorithms are emerging to improve the existing systems in a car. Often these algorithms only need a platform with a bus connection and some resources such as processing power and memory space. These functions are predestined to be integrated into existing systems that have free resources. This paper will examine the role of time protection in these multi-algorithm systems and describe what timing protection means and why it is required. The processing time will be partitioned to the different processing levels like interrupts, services and tasks. The problems of timing protection will be illustrated as well as its limitations. The conflict between real-time requirements and timing protection will be shown. Finally Autosar will be examined with focus on timing protection and applicability in actual development projects.

A reliable environment perception is a requirement for safe automated driving. For evaluating and demonstrating the reliability of the vehicle’s environment perception, field tests offer testing conditions that come closest to the vehicle’s driving environment. However, establishing a reference ground truth in field tests is time-consuming. This motivates the development of a procedure for learning the vehicle’s perception reliability from fleet data without the need for a ground truth, which would allow learning the perception reliability from fleet data. In Berk et al. (2019), a method based on Bayesian inference to determine the perception reliability of individual sensors without the need for a ground truth was proposed. The model utilizes the redundancy of sensors to learn the sensor’s perception reliability. The method was tested with simulated data.