Search Results

Multicore processor are well established in classical and tablet personal computers for some year. Such processors use more then one central core for computation and allow to integrate more computational power with smaller costs. However more than 90% of all processors worldwide are not placed in classical IT but are empedded in bigger systems like in modern vehicles or airplanes. Such systems face a very high demand in terms of safety, security an reliability which hinders the use of multicores in such systems. The funded project ARAMiS faces these demands and has the goal to enable the usability of multicore systems in the domains automotive and avionics, as well as later also railway. ARAMiS is the basis for higher traffic safety, traffic efficiency and comfort.

In ride comfort as well as driving dynamics, the behavior of the vehicle is affected by several subsystems and their properties. When analyzing the suspension, especially the characteristics of the main spring and damper but also rubber bushings are of main importance. Still, the properties of the different components are dependent on the present operating conditions. Concerning rubber bushings, several effects have already been investigated, e.g. dependencies of the transfer function of frequency, amplitude or load history. In this context influences of changes in temperature are often neglected. However, in the following research, the focus specifically lies on determination and analysis of the temperature dependency of rubber bushings. For this purpose, initially the relationship between properties of pure rubber and rubber bushings is described, which serves as a basis for correlating respective temperature dependencies.

With the introduction of the ISO26262 automotive safety standard there is a burden of proof to show that the processing elements in embedded microcontroller hardware are capable of supporting a certain diagnostic coverage level, depending on the required Automotive Safety Integrity Level (ASIL). The current mechanisms used to provide actual metrics of the Built-in Self Tests (BIST) and Lock Step comparators use Register Transfer Level (RTL) simulations of the internal processing elements which force faults into individual nodes of the design and collect diagnostic coverage results. Although this mechanism is robust, it can only be performed by semiconductor suppliers and is costly. This paper describes a new solution whereby the microcontroller is synthesized into a large Field Programmable Gate Array (FPGA) with a test controller on the outside.

The integration of mixed-criticality software according to safety standards like ISO 26262 generates new, parasitic mutual effects within the involved software architectures. In this situation, established schedule design patterns like RMS fail to deliver both efficiency and safety, in particular the freedom of interference. In today's practice of building a schedule, certain such measures to fulfill these safety requirements can conflict with efficiency requirements. The target of this paper is to present a sound approach of how to solve such requirement conflicts and to build up schedules that are safe and also efficient. We present a general early-stage procedure to build safe, certifiable, and efficient schedules. The procedure is based on the established design patterns and adds guidelines on how to exploit additional options in both schedule design and software partitioning. This procedure was validated against typical real-world systems and one example is presented.

This study deals with the experimental investigation of the mechanical properties of a lithium-ion pouch cell and its modelling in an explicit finite element simulation code. One can distinguish between ‘macroscopic’ and ‘microscopic’ modelling approaches. In the ‘macroscopic’ approach, one material model approximates the behaviour of multiple inner cell layers. In the ‘microscopic’ approach, which is used in the present study, all layers and their interactions are modelled separately. The cell under study is a pouch-type lithium-ion cell with a liquid electrolyte. With its cell chemistry, design, size and capacity it is usable for automotive applications and can be assembled into traction batteries. One cell sample was fully discharged and disassembled, and its components (anode, cathode, separator and pouch) were examined and measured by electron microscopy. Components were also tensile tested.

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.

This paper proposes end-to-end protection mechanisms to be added to a generic FlexRay network in order to achieve fault detection and integrity levels sufficient for a SIL3 fail safe communication system. The mechanisms are derived from the random hardware failure modes to be considered for communication controllers according to IEC 61508. Mechanisms provided by the FlexRay protocol are pointed out. Additional features necessary to fulfil the requirements are discussed. It is shown how to calculate the failure rate probabilities of the CRC used as a safety code with respect to EN 50159.

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.

In open jet wind tunnels with high blockage ratios a sharp rise in drag is observed for models approaching the nozzle exit plane. The physical background for this rise in drag will be analyzed in the paper. Starting with a basic analysis of the dependencies of the effect on model and wind tunnel properties, the key parameters of the problem will be identified. It will be shown using a momentum balance and potential flow theory that interaction between model and nozzle exit can result in significant tunnel-induced gradients at the model position. In a second step, a CFD-based investigation is used to show the interaction between nozzle exit and a bluff body. The results cover the whole range between open jet and closed wall test section interaction. The model starts at a large distance from the nozzle, then moves towards the nozzle, enters the nozzle and is finally completely inside the nozzle.

The ever increasing use of electronics in modern vehicles has not stopped at comfort systems such as power seats and power windows. Every conventional system that requires operating force will eventually be replaced by a self-powered version. One such item is the electromechanical parking brake of the new Audi A8, offering a host of new features. Despite the many options for new functions, it is nevertheless important to keep the driver in mind. Being engineers, one tends to overlook that not all customers share our excitement for gadgets and overly complicated technical features.

The reference pressures are determined in automotive wind tunnels by measurement of pressures and pressure differences at upstream positions along the wind tunnel nozzle. For closed wall wind tunnels usually the so called nozzle method is used, where the volume flux is calculated from a pressure difference measured at the nozzle contour and a calibration factor determined in the empty test section. For open jet wind tunnels a choice is available between nozzle and plenum method. For the plenum method the reference static pressure is taken from the plenum chamber and the dynamic pressure also refers to the plenum conditions. The static reference pressure in closed wall tunnels is calculated by subtracting the dynamic pressure from the total pressure in the settling chamber. In this paper, the definitions and the differences between the two methods are discussed in detail.

Driven by the growing internet and remote connectivity of automobiles, combined with the emerging trend to automated driving, the importance of security for automotive systems is massively increasing. Although cyber security is a common part of daily routines in the traditional IT domain, necessary security mechanisms are not yet widely applied in the vehicles. At first glance, this may not appear to be a problem as there are lots of solutions from other domains, which potentially could be re-used. But substantial differences compared to an automotive environment have to be taken into account, drastically reducing the possibilities for simple reuse. Our contribution is to address automotive electronics engineers who are confronted with security requirements. Therefore, it will firstly provide some basic knowledge about IT security and subsequently present a selection of automotive specific security use cases.

Developers of safety-critical real-time systems have to ensure that their systems react within given time bounds. Ideally, the system is designed to provide sufficient computing power and network bandwidth, is cost efficient and provides the necessary safety level. To achieve this goal, three challenges have to be addressed. First, it must be possible to account for timing during early development stages in the architecture exploration phase. Second, during software development, timing behavior and the effects of software changes on timing must be observable. Third, there must be a technology for formally verifying the final timing behavior for industry-size applications. In this article we present a comprehensive methodology for dealing with timing which addresses all three issues based on state-of-the-art commercial tools.

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.

For a long time, tools and methods for automotive E/E design were mostly in the domain of academic researches only. Recently, OEMs have started adopting selected contributions, because (very soon) it will become quite costly NOT to apply them. The first step is establishing centralized data storage for all design data. At present, selecting appropriate abstraction levels and design methods that get fed by and feed the data is the task at hand. In this paper, we summarize recent progress in this selection process with a focus on performance; which is a key aspect for architecture generation. Our contribution provides incremental progress from both ends of the mentioned gap (requirements vs. architecture vs. implementation) towards one another. The presentation is created around the IMES project [21] considering centralized data storage. However, the overall approach is based on established standards and common design patterns as much as possible.

More electronic vehicle functions lead to an exponentially growing degree of software integration in automotive ECUs. We are seeing an increasing number of ECUs with mixed criticality software. ISO26262 describes different safety requirements, including freedom from interference and absence from error propagation for the software. These requirements mandate particular attention for mixed-criticality ECUs. In this paper we investigate the ability to guarantee that these safety requirements will be fulfilled by using established (deadline monitoring) and new error detection mechanisms (execution time monitoring). We also show how these methods can be used to build up safe and efficient schedules for today's and future automotive embedded real time systems with mixed criticality software.

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.

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.

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.

Systems and network integration is a major challenge, and systematic analysis of the complex dynamic timing effects becomes key to building reliable systems. Very often, however, systematic analysis techniques are (considered) too restrictive with respect to established design practice. In this paper we present lessons learned from real-world case studies, in which OEMs have used the new SymTA/S scheduling analysis technology to evaluate different network choices with minimum effort. Thanks to its flexibility and supplier independence, SymTA/S can be applied in non-ideal situations, where other, more restricted technologies are inherently limited. Finally, we put the technology into relation with ongoing standardization activities.