driving, as well as for remote diagnostics and by Pay-As-You-Drive insurance. Although originally not intended for the above purposes, commonly supported OBD II data such as vehicle speed, RPM, and fuel level allow GPS-based fleet tracking devices to monitor vehicle idling times, speeding, and over-revving. By monitoring OBD II DTCs a company can know immediately if one of its vehicles has an engine problem and by interpreting the code the nature of the problem. It can be used to detect reckless driving in real time based on the sensor data provided through the OBD port. This detection is done by adding a complex events processor (CEP) to the backend and on the client's interface. OBD II is also monitored to block mobile phones when driving and to record trip data for insurance purposes. OBD-II diagnostic trouble codes OBD-II diagnostic trouble codes (DTCs) contain 1 letter and 4 numbers, and are divided into the following categories: First character (B, C, P, U) B – Body (includes air conditioning and airbag) (1164 codes) C – Chassis (includes ABS and brake fluid) (486 codes) P – Powertrain (engine, transmission and ignition) (1688 codes) U – Network (wiring bus) (299 codes) Second character (0,1) 0 – indicates the generic OBD2 code. 1 – usually refers to the Manufacturer Specific Code. Third character (1 to 8) 1 – Fuel and Air Metering 2 – Fuel and Air Metering (Injector Circuit) 3 – Ignition System or Misfire 4 – Auxiliary Emission Controls 5 – Vehicle Speed Control & Idle Control System 6 – Computer Output Circuit 7 – Transmission 8 – Transmission Fourth and fifth characters 00, 01, 03 indicate special faults Other numbers (in combination with the second character) indicate specific issues Standards documents SAE standards documents on OBD-II J1962 – Defines the physical connector used for the OBD-II interface. J1850 – Defines a serial data protocol. There are 2 variants: 10.4 kbit/s (single wire, VPW) and 41.6 kbit/s (2 wire, PWM). Mainly used by US manufacturers, also known as PCI (Chrysler, 10.4K), Class 2 (GM, 10.4K), and SCP (Ford, 41.6K) J1978 – Defines minimal operating standards for OBD-II scan tools J1979 – Defines standards for diagnostic test modes J2012 – Defines standards trouble codes and definitions. J2178-1 – Defines standards for network message header formats and physical address assignments J2178-2 – Gives data parameter definitions J2178-3 – Defines standards for network message frame IDs