Search Results

This paper discusses our experiences on the implementation and benefits of using the Hardware-In-the-Loop (HIL) systems for Powertrain control system software verification and validation. The Visteon HIL system integrated with several off-the-shelf diagnostics and calibration tools is briefly explained. Further, discussions on test automation sequence control and failure insertion are outlined The capabilities and advantages of using HIL for unit level software testing, open loop and closed-loop system testing, fault insertion and test automation are described. HIL also facilitates Software and Hardware Interface validation testing with low-level driver and platform software. This paper attempts to show the experiences with and capabilities of these HIL systems.

The Controls and Software Engineering Team at BorgWarner Drivetrain Systems has successfully employed model-based software development for the past several years. Their drivetrain system control software, developed using MATLAB/Simulink/Stateflow, and autocoded using TargetLink, is on the road in many passenger vehicle applications. Using these tools, BorgWarner has realized the widely recognized benefits of model-based design; such as increased speed to market, improved quality, and reduced complexity. Validating algorithms early through simulation and rapid prototyping, then translating them to production software through automatic code generation has proven very successful for BorgWarner. When starting with model-based design, the BorgWarner team focused on developing the core application control algorithms in the modeling environment. Lower-level software such as I/O drivers, the task scheduler, and communication logic was still hand-coded.

Model-based software development and automatic production code generation have become increasingly established in recent years. The aerospace industry and other industries, such as automotive, have widely adopted and successfully deployed these methods in many different series production programs worldwide. This brought various benefits, such as a reduction in development times and improved quality due to more precise specifications, and early verification and validation by means of simulation. Model-based development is a general purpose development approach which can be applied to a wide variety of applications. Safety-critical systems, like found in aerospace applications to a large extent, but also found increasingly more often in other industries, like automotive or medical devices, pose special additional requirements to this process. This paper describes how model-based design and automatic production code generation can be applied to the development of safety-critical software.

Over the last few years the introduction of explicit system and software architecture models (e.g. AUTOSAR models) has led to changes in the automotive development process. The ability to simulate these models on a PC will be decisive for the acceptance of such approaches. This would support the early verification of distributed ECU and software systems and could therefore lead to cost savings. This paper describes an implementation of such an approach which fits into current development processes.

It is not news anymore when somebody talks about increasing software content in today's vehicles, transportation systems and machinery. The software content and complexity has grown so tremendously and rapidly that even the most advanced product/software development techniques leave more to desire in view of evolving product life-cycles, feature content and need for development efficiency. Model-Based Design (MBD) techniques and V-Cycle based development processes address the significant need for managing complexity, and to some extent, efficiency in product development. Further efficiency in the development process can be achieved by enabling virtual validation of software components. The virtual validation environment for software not only has the ability to run the software component as a standalone unit for performance validation, but is also extended to the validation of the performance of the entire embedded software of an ECU, multiple ECUs and the entire system.