OSEK

OSEK is an industry standards group and means literally " Open systems and their interfaces for the electronics in the motor vehicle ." OSEK is a trademark of Continental AG, previously to 2007 the company Siemens AG.

Development

The committee, founded in 1993 consists of various automotive manufacturers, their suppliers and software houses. The founding members were BMW AG, Daimler -Benz AG ( now Daimler AG), Adam Opel AG, Volkswagen, Robert Bosch GmbH, Siemens AG and the Institute for Industrial Information Technology of the University of Karlsruhe (TH).

In 1994, we joined with the French established in 1988 VDX Initiative ( Vehicle Distributed Executive) consisting of PSA ( Peugeot, Citroën) and Renault together. Since then reads the official name OSEK / VDX. Today The founding members form the Steering Committee.

Concept

The most important standard that this body has created is OSEK OS. OS stands for Operating System or German operating system. It is a specification of a real-time operating system for embedded components, like the other standards also mainly for use on real-time systems in the automotive electronics.

Other standards of OSEK body next to OSEK OS are OSEK OIL, OSEK ORTI, OSEK COM and OSEK -NM, and OSEK -TIME.

  • OSEK OIL provides a description of linguistic fields OIL stands for OSEK Implementation Language. In this language, operating system objects are created and described, such as Tasks, interrupts, resources, and alarms. OIL provides a standardized way to describe required operating system services for an application. Making the switch between different OSEK - OS - compliant operating systems should be facilitated.
  • OSEK ORTI defines the communication of an OSEK - OS operating system with a debugger. ORTI means OSEK Runtime Interface. A debugger is therefore in a position to internal states of the operating system, such as the states of tasks to display.
  • OSEK COM describes the communication between parts of the program. These program components may be implemented both as a control on different devices that are connected to each other through a network.
  • OSEK NM describes inter alia, to control devices may shut down within a car. NM stands for Network Management. Background is that all active control devices in the car consume electricity. Many of these control devices have to work even with the ignition key removed, so that, for example, even then can close the (electrical) sunroof. If these control units but constantly remain active, the vehicle battery will be empty when it was parked a long time. Therefore, these control devices are turned off after the vehicle is parked over the network. Furthermore, OSEK -NM responsible for all the tasks to deal with the management of the network that connects the control units, very often a CAN bus. Here is over, for example, communicated to the individual control unit, the role he has in the existing network, and who are its neighbors, etc.
  • OSEK -TIME specifies a standard for time -triggered real-time operating systems. OSEK -TIME callback functions are processed with a higher priority than configured in OSEK OS tasks.

Major parts of the OSEK / VDX specifications were transferred to an ISO standard. This bears the official number 17356 and includes OSEK / VDX OS 2.2.2, OSEK / VDX COM 3.0.3, OSEK / VDX NM 2.5.3 and OSEK / VDX OIL 2.5, as well as the so-called Binding Specification 1.4. 2, which describes the interaction of the individual parts. ORTI is not part of the ISO standard.

The work of the OSEK bodies are continued in the 2003 launched AUTOSAR project.

419464
de