Search Results

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.

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.

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.

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.