On-board diagnostics (OBD) is a term referring to a vehicle's self-diagnostic and reporting capability. In the United States, this capability is a requirement to comply with federal emissions standards to detect failures that may increase the vehicle tailpipe emissions to more than 150% of the standard to which it was originally certified. [1] [2]
OBD systems give the vehicle owner or repair technician access to the status of the various vehicle sub-systems. The amount of diagnostic information available via OBD has varied widely since its introduction in the early 1980s versions of onboard vehicle computers. Early versions of OBD would simply illuminate a tell-tale light if a problem was detected, but would not provide any information as to the nature of the problem. Modern OBD implementations use a standardized digital communications port to provide real-time data and diagnostic trouble codes which allow malfunctions within the vehicle to be rapidly identified.
![]() |
GM's ALDL (Assembly Line Diagnostic Link) is sometimes referred to as a predecessor to, or a manufacturer's proprietary version of, an OBD-I diagnostic starting in 1981. This interface was made in different varieties and changed with power train control modules (aka PCM, ECM, ECU). Different versions had slight differences in pin-outs and baud rates. Earlier versions used a 160 baud rate, while later versions went up to 8192 baud and used bi-directional communications to the PCM. [15] [16]
The regulatory intent of OBD-I was to encourage auto manufacturers to design reliable emission control systems that remain effective for the vehicle's "useful life". [17] The hope was that by forcing annual emissions testing for California starting in 1988, [18] and denying registration to vehicles that did not pass, drivers would tend to purchase vehicles that would more reliably pass the test. OBD-I was largely unsuccessful, as the means of reporting emissions-specific diagnostic information was not standardized. Technical difficulties with obtaining standardized and reliable emissions information from all vehicles led to an inability to implement the annual testing program effectively. [19]
The Diagnostic Trouble Codes (DTC's) of OBD-I vehicles can usually be found without an expensive scan tool. Each manufacturer used their own Diagnostic Link Connector (DLC), DLC location, DTC definitions, and procedure to read the DTC's from the vehicle. DTC's from OBD-I cars are often read through the blinking patterns of the 'Check Engine Light' (CEL) or 'Service Engine Soon' (SES) light. By connecting certain pins of the diagnostic connector, the 'Check Engine' light will blink out a two-digit number that corresponds to a specific error condition. The DTC's of some OBD-I cars are interpreted in different ways, however. Cadillac petrol fuel-injected vehicles are equipped with actual onboard diagnostics, providing trouble codes, actuator tests and sensor data through the new digital Electronic Climate Control display.
Holding down 'Off' and 'Warmer' for several seconds activates the diagnostic mode without the need for an external scan tool. Some Honda engine computers are equipped with LEDs that light up in a specific pattern to indicate the DTC. General Motors, some 1989–1995 Ford vehicles (DCL), and some 1989–1995 Toyota/Lexus vehicles have a live sensor data stream available; however, many other OBD-I equipped vehicles do not. OBD-I vehicles have fewer DTC's available than OBD-II equipped vehicles.
OBD 1.5 refers to a partial implementation of OBD-II which General Motors used on some vehicles in 1994, 1995, & 1996. (GM did not use the term OBD 1.5 in the documentation for these vehicles — they simply have an OBD and an OBD-II section in the service manual.)
For example, the 1994–1995 model year Corvettes have one post-catalyst oxygen sensor (although they have two catalytic converters), and have a subset of the OBD-II codes implemented. [20]
This hybrid system was present on GM B-body cars (the Chevrolet Caprice, Impala, and Buick Roadmaster) for 1994–1995model years, H-body cars for 1994–1995, W-body cars (Buick Regal, Chevrolet Lumina (for 1995 only), Chevrolet Monte Carlo (1995 only), Pontiac Grand Prix, Oldsmobile Cutlass Supreme) for 1994–1995, L-body (Chevrolet Beretta/Corsica) for 1994–1995, Y-body (Chevrolet Corvette) for 1994–1995, on the F-body (Chevrolet Camaro and Pontiac Firebird) for 1995 and on the J-Body (Chevrolet Cavalier and Pontiac Sunfire) and N-Body (Buick Skylark, Oldsmobile Achieva, Pontiac Grand Am) for 1995 and 1996 and also for North American delivered 1994–1995 Saab vehicles with the naturally aspirated 2.3.
The pinout for the ALDL connection on these cars is as follows:
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 |
For ALDL connections, pin 9 is the data stream, pins 4 and 5 are ground, and pin 16 is the battery voltage.
An OBD 1.5 compatible scan tool is required to read codes generated by OBD 1.5.
Additional vehicle-specific diagnostic and control circuits are also available on this connector. For instance, on the Corvette there are interfaces for the Class 2 serial data stream from the PCM, the CCM diagnostic terminal, the radio data stream, the airbag system, the selective ride control system, the low tire pressure warning system, and the passive keyless entry system. [21]
An OBD 1.5 has also been used in the Ford Scorpio since 95. [22]
OBD-II is an improvement over OBD-I in both capability and standardization. The OBD-II standard specifies the type of diagnostic connector and its pinout, the electrical signalling protocols available, and the messaging format. It also provides a candidate list of vehicle parameters to monitor along with how to encode the data for each. There is a pin in the connector that provides power for the scan tool from the vehicle battery, which eliminates the need to connect a scan tool to a power source separately. However, some technicians might still connect the scan tool to an auxiliary power source to protect data in the unusual event that a vehicle experiences a loss of electrical power due to a malfunction. Finally, the OBD-II standard provides an extensible list of DTCs. As a result of this standardization, a single device can query the on-board computer(s) in any vehicle. This OBD-II came in two models OBD-IIA and OBD-IIB. OBD-II standardization was prompted by emissions requirements, and though only emission-related codes and data are required to be transmitted through it, most manufacturers have made the OBD-II Data Link Connector the only one in the vehicle through which all systems are diagnosed and programmed. OBD-II Diagnostic Trouble Codes are 4-digit, preceded by a letter: P for powertrain (engine and transmission), B for body, C for chassis, and U for network.
The OBD-II specification provides for a standardized hardware interface — the female 16-pin (2x8) J1962 connector, where type A is used for 12-volt vehicles and type B for 24-volt vehicles. Unlike the OBD-I connector, which was sometimes found under the bonnet of the vehicle, the OBD-II connector is required to be within 2 feet (0.61 m) of the steering wheel (unless an exemption is applied for by the manufacturer, in which case it is still somewhere within reach of the driver).
SAE J1962 defines the pinout of the connector as:
1 | Manufacturer discretion GM: J2411 GMLAN/SWC/Single-Wire CAN. | 9 | Manufacturer discretion GM: 8192 baud ALDL where fitted. |
---|---|---|---|
2 | Bus positive Line SAE J1850 PWM and VPW | 10 | Bus negative Line SAE J1850 PWM only (not SAE 1850 VPW) |
3 | Manufacturer discretion Ethernet TX+ (Diagnostics over IP) | 11 | Manufacturer discretion Ethernet TX- (Diagnostics over IP) |
4 | Chassis ground | 12 | Manufacturer discretion Ethernet RX+ (Diagnostics over IP) |
5 | Signal ground | 13 | Manufacturer discretion Ethernet RX- (Diagnostics over IP) |
6 | CAN high (ISO 15765-4 and SAE J2284) | 14 | CAN low (ISO 15765-4 and SAE J2284) |
7 | K-line (ISO 9141-2 and ISO 14230-4) | 15 | L-line (ISO 9141-2 and ISO 14230-4) |
8 | Manufacturer discretion Activate Ethernet (Diagnostics over IP) | 16 | Battery voltage (+12 Volt for type A connector) |
The assignment of unspecified pins is left to the vehicle manufacturer's discretion. [24]
The European on-board diagnostics (EOBD) regulations are the European equivalent of OBD-II, and apply to all passenger cars of category M1 (with no more than 8 passenger seats and a Gross Vehicle Weight rating of 2,500 kg, 5,500 lb or less) first registered within EU member states since January 1, 2001 for petrol-engined cars and since January 1, 2004 for diesel engined cars. [25]
For newly introduced models, the regulation dates applied a year earlier – January 1, 2000 for petrol and January 1, 2003, for diesel.
For passenger cars with a Gross Vehicle Weight rating of greater than 2500 kg and for light commercial vehicles, the regulation dates applied from January 1, 2002, for petrol models, and January 1, 2007, for diesel models.
The technical implementation of EOBD is essentially the same as OBD-II, with the same SAE J1962 diagnostic link connector and signal protocols being used.
With Euro V and Euro VI emission standards, EOBD emission thresholds are lower than previous Euro III and IV.
Each of the EOBD fault codes consists of five characters: a letter, followed by four numbers. [26] The letter refers to the system being interrogated e.g. Pxxxx would refer to the powertrain system. The next character would be a 0 if complies to the EOBD standard. So it should look like P0xxx.
The next character would refer to the sub system.
The following two characters would refer to the individual fault within each subsystem. [27]
The term "EOBD2" is marketing speak used by some vehicle manufacturers to refer to manufacturer-specific features that are not actually part of the OBD or EOBD standard. In this case "E" stands for Enhanced.
JOBD is a version of OBD-II for vehicles sold in Japan.
The ADR 79/01 (Vehicle Standard (Australian Design Rule 79/01 – Emission Control for Light Vehicles) 2005) standard is the Australian equivalent of OBD-II. It applies to all vehicles of category M1 and N1 with a Gross Vehicle Weight rating of 3,500 kg (7,700 lb) or less, registered from new within Australia and produced since January 1, 2006 for petrol-engined cars and since January 1, 2007 for diesel-engined cars. [28]
For newly introduced models, the regulation dates applied a year earlier – January 1, 2005 for petrol and January 1, 2006, for diesel. The ADR 79/01 standard was supplemented by the ADR 79/02 standard which imposed tighter emissions restrictions, applicable to all vehicles of class M1 and N1 with a Gross Vehicle Weight rating of 3500 kg or less, from July 1, 2008, for new models, July 1, 2010, for all models. [29]
The technical implementation of this standard is essentially the same as OBD-II, with the same SAE J1962 diagnostic link connector and signal protocols being used.
In North America, EMD and EMD+ are on-board diagnostic systems that were used on vehicles with a gross vehicle weight rating of 14,000 lb (6,400 kg) or more between the 2007 and 2012 model years if those vehicles did not already implement OBD-II. EMD was used on California emissions vehicles between model years 2007 and 2009 that did not already have OBD-II. EMD was required to monitor fuel delivery, exhaust gas recirculation, the diesel particulate filter (on diesel engines), and emissions-related powertrain control module inputs and outputs for circuit continuity, data rationality, and output functionality. EMD+ was used on model year 2010-2012 California and Federal petrol-engined vehicles with a gross vehicle weight rating of over 14,000 lb (6,400 kg), it added the ability to monitor nitrogen oxide catalyst performance. EMD and EMD+ are similar to OBD-I in logic but use the same SAE J1962 data connector and CAN bus as OBD-II systems. [8]
Five signaling protocols are permitted with the OBD-II interface. Most vehicles implement only one of the protocols. It is often possible to deduce the protocol used based on which pins are present on the J1962 connector: [30]
All OBD-II pinouts use the same connector, but different pins are used with the exception of pin 4 (battery ground) and pin 16 (battery positive).
OBD-II provides access to data from the engine control unit (ECU) and offers a valuable source of information when troubleshooting problems inside a vehicle. The SAE J1979 standard defines a method for requesting various diagnostic data and a list of standard parameters that might be available from the ECU. The various available parameters are addressed by "parameter identification numbers" or PIDs which are defined in J1979. For a list of basic PIDs, their definitions, and the formula to convert raw OBD-II output to meaningful diagnostic units, see OBD-II PIDs. Manufacturers are not required to implement all PIDs listed in J1979 and they are allowed to include proprietary PIDs that are not listed. The PID request and data retrieval system gives access to real time performance data as well as flagged DTCs. For a list of generic OBD-II DTCs suggested by the SAE, see Table of OBD-II Codes. Individual manufacturers often enhance the OBD-II code set with additional proprietary DTCs.
Here is a basic introduction to the OBD communication protocol according to ISO 15031. In SAE J1979 these "modes" were renamed to "services", starting in 2003.
$01
shows current sensor live data from PIDs ("Parameter IDs"). See OBD-II PIDs#Service_01 for an extensive list.$02
makes Freeze Frame data accessible via the same PIDs. [33] See OBD-II PIDs#Service_02 for a list.$03
lists the emission-related "confirmed" diagnostic trouble codes stored. It either displays numeric, 4 digit codes identifying the faults or maps them to a letter (P, B, U, C) plus 4 digits. See #OBD-II_diagnostic_trouble_codes.$04
is used to clear emission-related diagnostic information. This includes clearing the stored pending/confirmed DTCs and Freeze Frame data. [34] $05
displays the oxygen sensor monitor screen and the test results gathered about the oxygen sensor. There are ten numbers available for diagnostics: $01
Rich-to-Lean O2 sensor threshold voltage$02
Lean-to-Rich O2 sensor threshold voltage$03
Low sensor voltage threshold for switch time measurement$04
High sensor voltage threshold for switch time measurement$05
Rich-to-Lean switch time in ms$06
Lean-to Rich switch time in ms$07
Minimum voltage for test$08
Maximum voltage for test$09
Time between voltage transitions in ms$06
is a Request for On-Board Monitoring Test Results for Continuously and Non-Continuously Monitored System. There are typically a minimum value, a maximum value, and a current value for each non-continuous monitor.$07
is a Request for emission-related diagnostic trouble codes detected during current or last completed driving cycle. It enables the external test equipment to obtain "pending" diagnostic trouble codes detected during current or last completed driving cycle for emission-related components/systems. This is used by service technicians after a vehicle repair, and after clearing diagnostic information to see test results after a single driving cycle to determine if the repair has fixed the problem. See #OBD-II_diagnostic_trouble_codes.$08
could enable the off-board test device to control the operation of an on-board system, test, or component.$09
is used to retrieve vehicle information. Among others, the following information is available: $0A
lists emission-related "permanent" diagnostic trouble codes stored. As per CARB, any diagnostic trouble codes that is commanding MIL on and stored into non-volatile memory shall be logged as a permanent fault code. See #OBD-II_diagnostic_trouble_codes.Various tools are available that plug into the OBD connector to access OBD functions. These range from simple generic consumer level tools to highly sophisticated OEM dealership tools to vehicle telematic devices.
A range of rugged hand-held scan tools is available.
Mobile device applications allow mobile devices such as cell phones and tablets to display and manipulate the OBD-II data accessed via USB adaptor cables or Bluetooth adapters plugged into the car's OBD II connector. Newer devices on the market are equipped with GPS sensors and the ability to transmit vehicle location and diagnostics data over a cellular network. Modern OBD-II devices can therefore nowadays be used to for example locate vehicles, monitor driving behavior in addition to reading Diagnostics Trouble Codes (DTC). Even more advanced devices allow users to reset engine DTC codes, effectively turning off engine lights in the dashboard; however, resetting the codes does not address the underlying issues and can in worst-case scenarios even lead to engine breakage where the source issue is serious and left unattended for long periods. [36] [37]
An OBD-II software package when installed in a computer (Windows, Mac, or Linux) can help diagnose the onboard system, read and erase DTCs, turn off MIL, show real-time data, and measure vehicle fuel economy. [38]
To use OBD-II software, one needs to have an OBD-II adapter (commonly using Bluetooth, Wi-Fi or USB) [39] plugged in the OBD-II port to enable the vehicle to connect with the computer where the software is installed. [40]
A PC-based OBD analysis tool that converts the OBD-II signals to serial data (USB or serial port) standard to PCs or Macs. The software then decodes the received data to a visual display. Many popular interfaces are based on the ELM327 or STN [41] OBD Interpreter ICs, both of which read all five generic OBD-II protocols. Some adapters now use the J2534 API allowing them to access OBD-II Protocols for both cars and trucks.
In addition to the functions of a hand-held scan tool, the PC-based tools generally offer:
The extent that a PC tool may access manufacturer or vehicle-specific ECU diagnostics varies between software products [42] as it does between hand-held scanners.
Data loggers are designed to capture vehicle data while the vehicle is in normal operation, for later analysis.
Data logging uses include:
Analysis of vehicle black box data may be performed periodically, automatically transmitted wirelessly to a third party or retrieved for forensic analysis after an event such as an accident, traffic infringement or mechanical fault.
In the United States, many states now use OBD-II testing instead of tailpipe testing in OBD-II compliant vehicles (1996 and newer). Since OBD-II stores trouble codes for emissions equipment, the testing computer can query the vehicle's onboard computer and verify there are no emission related trouble codes and that the vehicle is in compliance with emission standards for the model year it was manufactured.
In the Netherlands, 2006 and later vehicles get a yearly EOBD emission check. [46]
Driver's supplementary vehicle instrumentation is instrumentation installed in a vehicle in addition to that provided by the vehicle manufacturer and intended for display to the driver during normal operation. This is opposed to scanners used primarily for active fault diagnosis, tuning, or hidden data logging.
Auto enthusiasts have traditionally installed additional gauges such as manifold vacuum, battery current etc. The OBD standard interface has enabled a new generation of enthusiast instrumentation accessing the full range of vehicle data used for diagnostics, and derived data such as instantaneous fuel economy.
Instrumentation may take the form of dedicated trip computers, [47] carputer or interfaces to PDAs, [48] smartphones, or a Garmin navigation unit.
As a carputer is essentially a PC, the same software could be loaded as for PC-based scan tools and vice versa, so the distinction is only in the reason for use of the software.
These enthusiast systems may also include some functionality similar to the other scan tools.
OBD II information is commonly used by vehicle telematics devices that perform fleet tracking, monitor fuel efficiency, prevent unsafe 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. [49] 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. [50]
OBD-II diagnostic trouble codes (DTCs) [51] [52] are five characters long, with the first letter indicating a category, and the remaining four being a hexadecimal number. [53]
The first character, representing category can only be one of the following four letters, given here with their associated meanings. (This restriction in number is due to how only two bits of memory are used to indicate the category when DTCs are stored and transmitted). [53]
The second character is a number in the range of 0–3. (This restriction is again due to memory storage limitations). [53]
The third character may denote a particular vehicle system that the fault relates to. [51]
Finally the fourth and fifth characters define the exact problem detected.
Researchers at the University of Washington and University of California examined the security around OBD and found that they were able to gain control over many vehicle components via the interface. Furthermore, they were able to upload new firmware into the engine control units. Their conclusion is that vehicle embedded systems are not designed with security in mind. [54] [55] [56]
There have been reports of thieves using specialist OBD reprogramming devices to enable them to steal cars without the use of a key. [57] The primary causes of this vulnerability lie in the tendency for vehicle manufacturers to extend the bus for purposes other than those for which it was designed, and the lack of authentication and authorization in the OBD specifications, which instead rely largely on security through obscurity. [58]
A controller area network (CAN) is a vehicle bus standard designed to enable efficient communication primarily between electronic control units (ECUs). Originally developed to reduce the complexity and cost of electrical wiring in automobiles through multiplexing, the CAN bus protocol has since been adopted in various other contexts. This broadcast-based, message-oriented protocol ensures data integrity and prioritization through a process called arbitration, allowing the highest priority device to continue transmitting if multiple devices attempt to send data simultaneously, while others back off. Its reliability is enhanced by differential signaling, which mitigates electrical noise. Common versions of the CAN protocol include CAN 2.0, CAN FD, and CAN XL which vary in their data rate capabilities and maximum data payload sizes.
A vehicle bus is a specialized internal communications network that interconnects components inside a vehicle. In electronics, a bus is simply a device that connects multiple electrical or electronic devices together. Special requirements for vehicle control such as assurance of message delivery, of non-conflicting messages, of minimum time of delivery, of low cost, and of EMF noise resilience, as well as redundant routing and other characteristics mandate the use of less common networking protocols. Protocols include Controller Area Network (CAN), Local Interconnect Network (LIN) and others. Conventional computer networking technologies are rarely used, except in aircraft, where implementations of the ARINC 664 such as the Avionics Full-Duplex Switched Ethernet are used. Aircraft that use Avionics Full-Duplex Switched Ethernet (AFDX) include the B787, the A400M and the A380. Trains commonly use Ethernet Consist Network (ECN). All cars sold in the United States since 1996 are required to have an On-Board Diagnostics connector, for access to the car's electronic controllers.
Society of Automotive Engineers standard SAE J1939 is the vehicle bus recommended practice used for communication and diagnostics among vehicle components. Originating in the car and heavy-duty truck industry in the United States, it is now widely used in other parts of the world.
A data logger is an electronic device that records data over time or about location either with a built-in instrument or sensor or via external instruments and sensors. Increasingly, but not entirely, they are based on a digital processor, and called digital data loggers (DDL). They generally are small, battery-powered, portable, and equipped with a microprocessor, internal memory for data storage, and sensors. Some data loggers interface with a personal computer and use software to activate the data logger and view and analyze the collected data, while others have a local interface device and can be used as a stand-alone device.
Chip tuning is changing or modifying an erasable programmable read only memory chip in an automobile's or other vehicles electronic control unit to achieve superior performance, whether it be more power, cleaner emissions, or better fuel efficiency. Engine manufacturers generally use a conservative electronic control unit map to allow for individual engine variations, as well as infrequent servicing and poor-quality fuel. Vehicles with a remapped electronic control unit may be more sensitive to fuel quality and service schedules.
Motronic is the trade name given to a range of digital engine control units developed by Robert Bosch GmbH which combined control of fuel injection and ignition in a single unit. By controlling both major systems in a single unit, many aspects of the engine's characteristics can be improved.
OBD-II PIDs are codes used to request data from a vehicle, used as a diagnostic tool.
A check engine light or malfunction indicator lamp (MIL), is a tell-tale that a computerized engine-management system used to indicate a malfunction or problem with the vehicle ranging from minor to serious. Found on the instrument panel of most automobiles, it usually bears the legend engine, check engine, service engine soon, maintenance required, emiss maint, or a pictogram of an engine—and when illuminated, it is typically an amber or red color.
Renix was a joint venture by Renault and Bendix that designed and manufactured automobile electronic ignitions, fuel injection systems, electronic automatic transmission controls, and various engine sensors. Major applications included various Renault and Volvo vehicles. The name became synonymous in the U.S. with the computer and fuel injection system used on the AMC/Jeep 2.5 L I4 and 4.0 L I6 engines.
VCDS is a Microsoft Windows-based software package, developed and produced by Ross-Tech, LLC since May 2000. It is primarily used for diagnostics and adjustments of Volkswagen Group motor vehicles, including Volkswagen Passenger Cars, Audi, Bentley (limited), Lamborghini (limited), SEAT, and Škoda automobiles, along with Volkswagen Commercial Vehicles.
Digifant is an Engine Management System operated by an Engine Control Unit that actuates outputs, such as fuel injection and ignition systems, using information derived from sensor inputs, such as engine speed, exhaust oxygen and intake air flow. Digifant was designed by Volkswagen Group, in cooperation with Robert Bosch GmbH.
Assembly Line Diagnostic Link, Assembly Line Data Link, or ALDL is a proprietary on-board diagnostics system developed by General Motors before the standardization of OBD-2. It was previously called Assembly Line Communications Link or ALCL. The two terms are used interchangeably.
OBDuino is an open source trip computer design based on the Arduino platform. An OBDuino may be assembled and customised by an electronics hobbyist; it displays information such as instantaneous fuel economy, engine tuning parameters etc. on an LCD.
The Lucas 14CUX is an automotive electronic fuel injection system developed by Lucas Industries and fitted to the Rover V8 engine in Land Rover vehicles between 1990 and 1995. The system was also paired with the Rover V8 by a number of low-volume manufacturers such as TVR, Marcos, Ginetta, and Morgan.
The data link connector (DLC) is the multi-pin diagnostic connection port for automobiles, trucks, and motorcycles used to interface a scan tool with the control modules of a given vehicle and access on-board diagnostics and live data streams.
An automotive scan tool (scanner) is an electronic tool used to interface with, diagnose and, sometimes, reprogram vehicle control modules.
The ELM327 is a programmed microcontroller produced for translating the on-board diagnostics (OBD) interface found in most modern cars. The ELM327 command protocol is one of the most popular PC-to-OBD interface standards and is also implemented by other vendors.
OpenXC is a hardware and software API for automobiles developed by Ford Bug Labs and proposed as an open standard.
The Modular Engine Management System, or MEMS, is an electronic control system used on engines in passenger cars built by Rover Group in the 1990s. As its name implies, it was adaptable for a variety of engine management demands, including electronically controlled carburetion as well as single- and multi-point fuel injection. The abbreviations "SPi" and "MPi" refer to the single-point and multi-point injection configurations, respectively.
Unified Diagnostic Services (UDS) is a diagnostic communication protocol used in electronic control units (ECUs) within automotive electronics, which is specified in the ISO 14229-1. It is derived from ISO 14230-3 (KWP2000) and the now obsolete ISO 15765-3. 'Unified' in this context means that it is an international and not a company-specific standard. By now this communication protocol is used in all new ECUs made by Tier 1 suppliers of Original Equipment Manufacturer (OEM), and is incorporated into other standards, such as AUTOSAR. The ECUs in modern vehicles control nearly all functions, including electronic fuel injection (EFI), engine control, the transmission, anti-lock braking system, door locks, braking, window operation, and more.
{{cite magazine}}
: Cite magazine requires |magazine=
(help){{cite book}}
: CS1 maint: date and year (link)