Search Results

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.

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.

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.

The importance of electronics, especially software, has greatly increased over the last few years. Efforts to maintain a high level of software quality have made testing an important part of the development process. With the advent of model-based development, testing methods can be used not only on code level, but also on model level. Next to test execution itself, test development is seen as the most time- and cost-intensive part of the testing process. This paper outlines and classifies current approaches to model-based test development, with the aim of providing guidelines for test developers for choosing the method best suited to the type of system under test and the test objective.

Increasing productivity along the development and verification process of safety-related projects is an important aspect in today’s technological developments, which need to be ever more efficient. The increase of productivity can be achieved by improving the usability of software tools and decreasing the effort of qualifying the software tool for a safety-related project. For safety-critical systems, the output of software tools has to be verified in order to ensure the tools’ suitability for safety-relevant applications. Verification is particularly important for test automation tools that are used to run hardware-in-the-loop (HIL) tests of safety-related software automatically 24/7. This qualification of software tools requires advanced knowledge and effort. This problem can be solved if a tool is suitable for developing safety-related software. This paper explains how this can be achieved for a COTS test automation tool.

Hardware-in-the-loop (HIL) simulation is now a standard component in the vehicle development process as a method for testing electronic control unit (ECU) software. HIL simulation is used for all aspects of development, naturally including safety-relevant functions and systems. This applies to all test tasks (from function testing to release tests, testing a single ECU or an ECU network, and so on) and also to different vehicle domains: The drivetrain, vehicle dynamics, driver assistance systems, interior/comfort systems and infotainment are all tested by HIL simulation. At the same time, modern vehicles feature more and more safety-related systems such as Adaptive Cruise Control, Electronic Stability Program, Power Assisted Steering, and Integrated Chassis Management.