Search Results

Automotive embedded systems have become very complex, are strongly integrated, and the safety-criticality and real-time constraints of these systems raise new challenges. The OSEK/VDX standard provides an open-ended architecture for distributed real-time capable units in vehicles. This is supported by the OSEK Implementation Language (OIL), a language aiming at specifying the configuration of these real-time operating systems. The challenge, however, is to ensure consistency of the concept constraints and configurations along the entire product development. The contribution of this paper is to bridge the existing gap between model-driven systems engineering and software engineering for automotive real-time operating systems (RTOS). For this purpose a bidirectional tool bridge has been established based on OSEK OIL exchange format files.

Worldwide OBD legislation has and will be tightened drastically. In the US, OBD II for PC and the introduction of HD OBD for HD vehicles in 2010 will be the next steps. Further challenges have come up with the introduction of active exhaust gas aftertreatment components to meet the lower future emission standards, especially with the implementation of combined DPF-De-NOx-systems for PC and HD engines. Following such an increase in complexity, more comprehensive algorithms and software have to be developed to cope with the legislative requirements for exhaust gas aftertreatment devices. The calibration has to assure the proper functionality of OBD under all driving situations and ambient conditions. The increased complexity can only be mastered when new and efficient tools and methodologies are applied for both algorithm design and calibration. Consequently, OBD requirements have to be taken into account right from the start of engine development.