ArticleslgStudy

computer science

On-board diagnostics

On-board diagnostics is a computer science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand On-board diagnostics rather than just read about it. In short: 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.

On-board diagnostics — main illustration
On-board diagnostics — illustration

Key takeaways

  • On-board diagnostics belongs to computer science; place it in that map before memorising details.
  • Learn the definition first, then one example that makes the definition concrete.
  • Connect On-board diagnostics to a quantity you can measure, compute or draw — that is where exam questions come from.
  • Reproduce the core statement of On-board diagnostics from memory before moving on to harder problems.

Reference excerpt

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. 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.

History 1968: Volkswagen introduces the first on-board computer system, in their fuel-injected Type 3 models. This system is entirely analog with no diagnostic capabilities. 1975: Bosch and Bendix EFI systems are adopted by major automotive manufacturers to improve tailpipe (exhaust) emissions. These systems are also analog, though some provide rudimentary diagnostic capability through factory tools, such as the Kent Moore J-25400, compatible with the Datsun 280Z, and the Cadillac Seville. 1980: General Motors introduces the first data link on their 1980 Cadillac Eldorado and Seville models. Diagnostic Trouble Codes (DTCs) are displayed through the electronic climate control system's digital readout when in diagnostic mode. 1981: General Motors introduced its "Computer Command Control" system on all US passenger vehicles for model year 1981. Included in this system is a proprietary 5-pin ALDL that interfaces with the Engine Control Module (ECM) to initiate a diagnostic request and provide a serial data stream. The protocol communicates at 160 baud with Pulse-width modulation (PWM) signaling and monitors all engine management functions. It reports real-time sensor data, component overrides, and Diagnostic Trouble Codes. The specification for this link is as defined by GM's Emissions Control System Project Center document XDE-5024B. 1982: RCA defines an analog STE/ICE (simplified test equipment for internal combustion engines) vehicle diagnostic standard used in the CUCV, M60 tank and other military vehicles of the era for the US Army. 1986: General Motors introduces an upgraded version of the ALDL protocol, which communicates at 8192 baud with half-duplex UART signaling on some models. 1988: The California Air Resources Board (CARB) requires that all new vehicles sold in California from 1988 onward have some basic OBD capability (such as detecting problems with fuel metering and exhaust gas recirculation.) These requirements are generally referred to as "OBD-I", though this name is a retronym applied after the introduction of OBD-II. The data link connector and its position are not standardized, nor is the data protocol. The Society of Automotive Engineers (SAE) recommends a standardized diagnostic connector and set of diagnostic test signals. ~1994: Motivated by a desire for a state-wide emissions testing program, the CARB issues the OBD-II specification and mandates that it be adopted for all cars sold in California starting in model year 1996 (see CCR Title 13 Section 1968.1 and 40 CFR Part 86 Section 86.094). The DTCs and connectors suggested by the SAE are incorporated into this specification. 1996: The OBD-II specification is made mandatory for all passenger cars and petrol-powered light trucks with a gross vehicle weight rating less than 8,500 lb (3,900 kg) in the United States. The OBD-II specification is also made mandatory for all petrol-powered vehicles with California emissions with a gross vehicle weight rating up to 14,000 lb (6,400 kg). 1997: The OBD-II specification is made mandatory for California emissions diesel-engined vehicles with a gross vehicle weight rating up to 14,000 lb (6,400 kg). 2001: The European Union makes EOBD mandatory for all petrol vehicles sold in the European Union, starting in MY2001 (see European emission standards Directive 98/69/EC). 2004: The European Union makes EOBD mandatory for all diesel vehicles sold in the European Union. All petrol-powered vehicles in the United States with a gross vehicle weight rating of up to 14,000 lb (6,400 kg) are required to have OBD-II. 2006: All vehicles manufactured in Australia and New Zealand are required to be OBD-II compliant after January 1, 2006. All vehicles in the United States of 14,000 lb (6,400 kg) gross vehicle weight rating and under are required to have OBD-II. 2007: All California emissions vehicles over 14,000 lb (6,400 kg) gross vehicle weight rating are required to support EMD/EMD+ or OBD-II. 2008: All cars sold in the United States are required to use the ISO 15765-4 signaling standard (a variant of the Controller Area Network (CAN) bus). 2008: Certain light vehicles in China are required by the Environmental Protection Administration Office to implement OBD (standard GB18352) by July 1, 2008. Some regional exemptions may apply. 2010: Required phase-in of the OBD-II specification to all vehicles with a gross vehicle weight rating of 14,000 lb (6,400 kg) and above was initiated in the United States. This was completed by the 2013 model year. Vehicles that did not have OBD-II during this time period were required to have EMD/EMD+.

Standard interfaces

ALDL

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.

… excerpt ends here. Continue reading the full article.

Illustrations

On-board diagnostics illustration
On-board diagnostics: Female OBD-II connector on a car
Female OBD-II connector on a car
On-board diagnostics: Female OBD-II type A connector pinout – front view
Female OBD-II type A connector pinout – front view
On-board diagnostics: Female OBD-II type B connector pinout – front view. Wire placement is identical to type A, but the center groove is split in two.
Female OBD-II type B connector pinout – front view. Wire placement is identical to type A, but the center groove is split in two.
On-board diagnostics: Multi-brand vehicle diagnostics system handheld Autoboss V-30 with adapters for connectors of several vehicle manufacturers.[35]
Multi-brand vehicle diagnostics system handheld Autoboss V-30 with adapters for connectors of several vehicle manufacturers.[35]

Worked examples

Example 1 — a first encounter with On-board diagnostics

Start with the simplest possible case. Write down what On-board diagnostics claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In computer science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to On-board diagnostics before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about On-board diagnostics ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of On-board diagnostics

In research
On-board diagnostics appears in computer science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry
Engineering practice reuses On-board diagnostics in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom
On-board diagnostics is common in secondary-school and first-year university syllabi. It links to neighbouring topics Automotive technologies, Fleet management, Industrial computing, so understanding it makes those chapters shorter.
In everyday life
Look for On-board diagnostics outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study On-board diagnostics in 20 minutes

  1. Read the reference excerpt below once, without taking notes.
  2. Close the page and write down what On-board diagnostics means in your own words.
  3. Compare your version with the excerpt and mark what you missed.
  4. Work through the three examples above with pen and paper.
  5. Explain On-board diagnostics out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is On-board diagnostics in simple terms?

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 stan…

Why does On-board diagnostics matter?

Because it connects several computer science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study On-board diagnostics?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on On-board diagnostics.

Tags

  • Automotive technologies
  • Fleet management
  • Industrial computing
  • Vehicle security systems

Keep exploring