Search Results

This paper will first introduce and classify the basic principles of architecture-driven software development and will briefly sketch the presumed development process. This background information is then used to explain extensions which enable current behavior modeling and code generation tools to operate as software component generators. The generation of AUTOSAR software components using dSPACE's production code generator TargetLink is described as an example.

Today, hardware-in-the-loop (HIL) simulation is common practice as a testing methodology for electronic control units (ECUs). An essential criterion for the efficiency of an HIL system is the availability of powerful test automation having access to all of its hardware and software components (including I/O channels, failure insertion units, bus communication controllers and diagnostic interfaces). The growing complexity of vehicle embedded systems, which are interconnected by bus systems (like CAN, LIN or FlexRay), result in hundreds or even thousands of tests that have to be done to ensure the correct system functionality. This is best achieved by automated testing. Automated testing usually is performed by executing tests on a standard PC, which is interconnected to the HIL system. However, higher demands regarding timing precision are hard to accomplish. As an example, ECU interaction has to be captured and responded to in the range of milliseconds.

Due to tougher legislation on exhaust emissions reduction and the consumer demand for more power and mobility and less fuel consumption, the functionality in today's engine management systems continues to grow. The electronic engine control units (ECUs) have to perform more control tasks using new sensors and actuators, along with the corresponding self-diagnostics (OBD, on-board diagnosis). All this leads to continuously increasing demands on automated hardware-in-the-loop (HIL) test systems. HIL technology has advanced in parallel to the ECUs, and is today an indispensable tool for developing automotive electronics. This paper therefore aims to provide a comprehensive and state-of-the-art survey of HIL test systems for engine controllers. First of all, a brief introduction to the ECU's functionality is given.

Electric drives are growing in importance in automotive applications, especially in hybrid electric vehicles (HEV) and in the vehicle dynamics area (steering systems, etc.). The challenges of real-time hardware-in-the-loop (HIL) simulation and testing of electric drives are addressed in this paper. In general, three different interface levels between the electric drive and the hardware-inthe-loop system can be distinguished: the signal level (1), the electrical level (2) and the mechanical level (3). These interface levels, as well as modeling and I/O-related aspects of electric drives and power electronics devices, are discussed in detail in the paper. Finally, different solutions based on dSPACE simulator technology are presented, for both hybrid vehicle and steering applications.

Validating control units with hardware-in-the-loop (HIL) simulators is an established method for quality enhancements in automotive software. It is primarily used for testing applications, but in view of increased networking between electronic control units, it can also be used for testing communication scenarios. The testing of electronic control unit (ECU) communication often includes only positive testing. Simple communication nodes are used for this, and communication analyzers are used for verifying communication up to the physical level. However, it is not only an ECU's positive communication behavior that has to be tested, but also its correct behavior in the event of communication errors. In HIL communication scenarios, it is not only possible to emulate the missing bus nodes (restbus simulation) with a link to real-time signals; correct ECU behavior in the event of communication errors can also be tested.

In modern vehicles the architecture of electronics is growing more and more complex because both the number of electronic functions – e.g. implemented as software modules – as well as the level of networking between electronic control units (ECUs) is steadily increasing. This complexity leads to greater propagation of failure symptoms, and diagnosing the causes of failure becomes a new challenge. Diagnostics aims at detecting failures such as defect sensors or faulty communication messages. It is subdivided into diagnosis algorithms on an ECU and algorithms running offboard, e.g. on a diagnostic tester. These algorithms have to complement each other in the best possible way. While in the past the diagnosis algorithm was developed late in the development process, nowadays there are efforts to start the development of such algorithms earlier – at least in parallel to developing a new feature itself. This would allow developers to verify the diagnosis algorithms in early design stages.

Model-based development and autocoding have become common practice in the automotive industry over the past few years. The industry is using these methods to tackle a situation in which complexity is constantly growing and development times are constantly decreasing, while the safety requirements for the software stay the same or even increase. The debate is no longer whether these methods are useful, but rather on the conditions for achieving optimum results with them. From the experiences made during the last decade this paper shows some of the key factors helping to achieve success when introducing or extending the deployment of automatic code generation in a model-based design process.

Function models have a well-established position in automotive software development. Formal system models, on the other hand, are rare. This article describes the various aspects of function and system models, focusing mainly on AUTOSAR-compatible models. It also depicts the challenges for future overall models that combine the function models and the system model, and the resulting benefits, such as early system verification via PC-based simulations.

Hardware-in-the-loop (HIL) testing is used by commercial vehicle original equipment manufacturers (OEMs) in several fields of electronics development. HIL tests are a part of the standard development process for engine and machine control systems. For electronic control units (ECUs), not only the HIL test of the hardware but also the controller software validation is very important. For hardware diagnostics validation, a dynamic simulation of the real system could be omitted and an open-loop test of the controller is sufficient in most cases. For most controller software validation including OBD (on-board diagnosis) tests, detailed but real-time capable models have to be used. This article describes the needs and challenges of models in hardware-in-the-loop (HIL) based testing, taking into account the wide range of commercial and off-highway vehicles.

This presentation focuses on several examples of partnerships between tool suppliers and embedded software developers in which state-of-the-art tools are used to optimize a variety of electric and hybrid vehicle architectures. Projects with Automotive OEMs, Tier One Suppliers as well as with academic institutions will be described. Due to the growing complexity in multiple electronic control units (“ECUs”) inter-communicating over numerous network bus systems, combined with the challenge of controlling and maintaining charges for electric motors, vehicle development would be impossible without use of increasingly sophisticated tools. Hybrid drive trains are much more complex than conventional ones, they have at least one degree of freedom more.

Model-based software development is increasingly being used to develop software for electronic control units (ECUs). When developing safety-related software, compared to non-safety-related software development, additional requirements specified by relevant safety-standards have to be met. Meeting these requirements should also be considered to be best practices for non-safety-related software. This paper introduces a model-based reference workflow for the development of safety-related software conforming to relevant safety-standards such as IEC 61508 and ISO 26262. The reference workflow discusses requirements traceability aspects, software architecture considerations that help to support modular development and ease the verification of model parts and the code generated from those model parts, and the selection and enforcement of modeling and coding guidelines.

In future cars, mechanical and hydraulic components will be replaced by new electronic systems (x-by-wire). A failure of such a system constitutes a safety hazard for the passengers as well as for the environment of the car. Thus electronics and in particular software are taking over more responsibility and safety-critical tasks. To minimize the risk of failure in such systems safety standards are applied for their development. The safety standard IEC 61508 has been established for automotive electronic systems. At the same time, automatic code generation is increasingly being used for automotive software development. This is to cope with today's increasing requirements concerning cost reduction and time needed for ECU development combined with growing complexity. However, automatic code generation is hardly ever used today for the development of safety-critical systems.

Permanently increasing software complexity of today's electronic control units (ECUs) makes testing a central and significant task within embedded software development. While new software functions are still being developed or optimized, other functions already undergo certain tests, mostly on module level but also on system and integration level. Testing must be done as early as possible within the automotive development process. Typically ECU software developers test new function modules by stimulating the code with test data and capturing the modules' output behavior to compare it with reference data. This paper presents a new and systematic way of testing embedded software for automotive electronics, called MTest. MTest combines the classical module test with model-based development. The central element of MTest is the classification-tree method, which has originally been developed by the DaimlerChrysler research department.

Automotive manufacturers and suppliers of electronic control units (ECUs) will be challenged more and more in the future to reduce costs and the time needed for ECU development. At the same time, increasing requirements concerning exhaust gas emissions, drivability, onboard diagnostics and fuel consumption have led to the growing complexity of modern engines and the associated management systems. As a result, the number and complexity of control parameters and look-up tables in the ECU software is increasing dramatically. Thus, in powertrain applications especially, calibration development has become a time-consuming and cost-intensive stage in the overall ECU development process. This paper describes the current situation in calibration development and shows how the new dSPACE Calibration System will face this situation. It provides an overview of the main benefits of the tool, which has been designed in close cooperation with calibration engineers.

Due to the continuously increasing number of electronic control units (ECUs) in modern cars, and their growing complexity, automated tests not only of single ECUs but also of interconnected ECUs have become an important step in the development of automotive electronics. These tasks require new test systems. This paper describes the problems engineers face when developing and testing today's car electronics, as well as a high-end hardware-in-the-loop (HIL) tool set (hardware, software, models) applied to the testing of four networked ECUs for engine management, vehicle dynamics control, automatic transmission, and an active suspension system. The tool set comprises general features needed for HIL tests, like automated code generation for real-time models using MATLAB/Simulink and a comprehensive set of dedicated hardware (processor and I/O hardware).

This paper discusses the standards that can currently be applied to production code generators and examines five standards in detail: OSEK/VDX, MISRA C, ISO/IEC 15504 (SPiCE), which is compared to ‘CMM for Software’, and IEC 61508. The issues involved in meeting these standards or integrating them in production code generators are discussed. The suitability of automatic production code generation in safety-critical applications is described, taking the TargetLink production code generator from dSPACE as an example.

Due to the rapidly increasing number of electronic control units (ECUs) in modern vehicles, software and ECU testing plays a major role within the development of automotive electronics. To ensure effective as well as efficient testing within the whole development process, a seamless transition in terms of the reusability of tests and test data as well as powerful and efficient means for developing and describing tests are required. This paper therefore presents a new integration approach for modern test development and test management. Besides a very easy-to-use way of describing tests graphically, the main focus of the new approach is on the management of a large number of tests, test data, and test results, allowing close integration into the automotive development processes.

This paper describes challenges and possible solution of hybrid electrical vehicles test systems with a special focus on hardware-in-the-loop (HIL) test bench. The degree of novelty of this work can be seen in the fact that development and test of ECU for hybrid electrical powertrains can move more and more from mechanical test benches with real automotive components to HIL test systems. The challenging task in terms of electrical interface between an electric motor ECU and an HIL system and necessary real-time capable simulation models for electric machines have been investigated and partly solved. Even cell balancing strategies performed by battery management systems (BMU) can be developed and tested using HIL technology with battery simulation models and a precise cell voltage simulation on electrical level.

Automotive technology is rapidly changing with electrification of vehicles, driver assistance systems, advanced safety systems etc. This advancement in technology is making the task of validation and verification of embedded software complex and challenging. In addition to the component testing, integration testing imposes even tougher requirements for software testing. To meet these challenges dSPACE is continuously evolving the Hardware-In-the-Loop (HIL) technology to provide a systematic way to manage this task. The paper presents developments in the HIL hardware technology with latest quad-core processors, FPGA based I/O technology and communication bus systems such as Flexray. Also presented are developments of the software components such as advanced user interfaces, GPS information integration, real-time testing and simulation models. This paper provides a real-world example of implication of integration testing on HIL environment for Chassis Controls.

Model-based development is the established way of developing embedded control algorithms, especially for safety-critical applications. The aim is to improve development efficiency and safety by developing the software at a high abstraction level (the model) and by generating the implementation (the C code) automatically from the model. Although model-based development focuses on the models themselves, downstream artifacts such as source code or executable object code have to be considered in the verification stage. Safety standards such as ISO 26262 require upper bounds to be determined for the required storage space or the execution time of real-time tasks, and the absence of run-time errors to be demonstrated. Static analysis tools are available which work at the code level and can prove the absence of such errors. However, the connection to the model level has to be explicitly established.