chapter-6

Download as pdf or txt
Download as pdf or txt
You are on page 1of 31

Ethio -Automotive Short Term Training Center

Module Tittle: Maintain, repair and diagnosing


vehicle electronic control engine management
problems.
Chapter - 6:- ON BORD DIAGNOSTIC (OBD)
Prepared by ; Abebe Neguse (Msc)
On-Board Diagnostic System (OBD)
 Device which take data from ECU

 OBD systems give the vehicle owner or repair technician


access to the status of the various vehicle subsystems
problem.

 Modern automotive computer systems are designed to detect


problems and indicate where they might be located.

 This has greatly simplified the troubleshooting of complex


automotive systems
 OBD classified based on generation
1. OBD I Systems
2. OBD II System
OBD I Systems (1988-1995)
 Most early on-board diagnostic systems can only check
a limited number of items.
 Able to detect a problem in a circuit, but unable to
determine the type of problem (faulty wiring, defective
component etc.)
 There was little standardize
 Each manufacturer used different connectors,
terminology, and trouble codes
OBD II System (after 1996)
 Designed to more efficiently monitor the
condition of hardware and software that affect
emissions.
 Diagnostics can detect part weakening, not just
complete failure.
 OBD II standardized data link connectors,
trouble codes, terminology, and scan tool
capabilities(16 port).
Malfunction Indicator Lamp (MIL)
 The MIL should come on when the ignition switch is turned
on (engine not running).
 When the engine is started, the MIL should go off.
 If the light remains on, it indicates that the diagnostic system
has detected a malfunction or abnormality in the diagnostic
system.
 The technician can then use a scan tool to retrieve
information

 Continuous illumination means the trouble should


be repaired at the owner’s convenience.

 A blinking MIL means the trouble could damage the


catalytic converter and should be fixed immediately.

 An alternating MIL means the problem is


intermittent.
Diagnostic Trouble Codes (DTC)
 Digital signals produced and stored by the computer.
 Parameters include sensor voltage or resistance range,
actuator current flow, and actuator movement
 For OBD I it is two digit (12)(ET1 and E1 make short)
 For OBD II it is five digit (PO1OO)
Standard (SAE)
Parts
CO1OO
component

System
 Service manual chart that shows different trouble code
numbers and possible problems and causes
Data Link Connector
 Multi pin terminal used to link the scan tool to the
computer
 OBD I connectors came in various shapes, sizes, and
locations
 OBD II connectors are standardized 16-pin connectors
located under the dash
1. Manufacturer discretion
2. Bus positive Line
3. Manufacturer discretion
4. Chassis ground
5. Signal ground
6. CAN high
7. K-line
8. Manufacturer discretion
9. Manufacturer discretion
10. Bus negative Line
11. Manufacturer discretion
12. Manufacturer discretion
13. Manufacturer discretion
14. CAN low
15. L-line
16. Battery voltage
Diagnostic Connector Location
 OBD II connector is located below the dash and center
console.
 Early located next to the fuse box and behind the dash
Connecting the Scan Tool
 Adapters are sometimes needed between the scan tool
connector and the data link connector on OBD I systems
 May require a separate power cord connection
to the battery or cigarette lighter
Failure Types
problem only Computer system failures can be
grouped into two general types:
 Hard failure
 problem that is always present
 Soft failure
occurs when certain conditions are present
(intermittent)
 soft failure codes will be stored in memory for
30–50 ignition or warm-up cycles.
Failure types can be further broken down into four
categories:
 General circuit failure
 circuit or component has a fixed value,
no output, or an output that is out of
specifications.
 Low-input failure
 voltage, current, or frequency is below
normal operating parameters.
 High-input failure
 signal has more voltage, more current, or a
higher frequency than normal.
 Improper range/performance failure
 sensor or actuator is producing values
slightly lower or higher than normal.
 device is still functioning, but not as well as
it should.
 OBD II systems have this capability.
How to Use an OBD Scanner

1. Connect The Scanner


Your OBD scanner will have a connection cable
with a 16-pin trapezoidal plug at the end. This
plug goes into your vehicle’s OBD port, also
referred to as the diagnostic link connector
(DLC).
2. Turn The Key
Insert your key in the ignition, but don’t start the
engine. Instead, turn your key only to the point where
the car’s power comes on. This will activate the OBD
computer, so your scanner can communicate with it.
Depending on your scanner, you’ll see a visual message
letting you know the link is being established.
3. Type In Your Vehicle Identification Number
Some OBD scanners will automatically detect what type
of vehicle you’re scanning. Others will require you to
enter that information manually. Some scanners will
simply have a menu for selecting the make and model.
Alternatively, you may have to enter your vehicle
identification number (VIN)
4. Locate Your OBD Codes
Now that you’re connected, you’re ready to read
your codes. How exactly you do this will be
different depending on the scanner. In most cases,
you’ll find the codes in the menu under “Codes” or
“Trouble Codes.” With many scanners, you’ll be
able to view active and pending OBD codes
separately. An active code represents a current
issue causing your Check Engine light to
illuminate.
5. Read Your Codes
At this point, you’re ready to read any OBD codes
that appear on your screen. Each code consists of
five characters, and each character has its meaning.
The first character specifies what area of the car is
having trouble. The most common one is P, which
indicates a problem with your powertrain system. C
indicates a problem with the chassis, such as your
brakes. B covers any issue with the vehicle’s body,
including safety devices like airbags. U, meanwhile,
means that there’s a problem with the car’s
communication system.
Erasing Trouble Code
 Removes the stored codes from computer
memory after system repairs have been made.
 Codes should be erased after service to
prevent misdiagnosis in the future.
 On OBD II vehicles, codes may need to be
cleared to extinguish the MIL lamp.
There are various ways to erase trouble codes from the
computer:
 Use a scan tool
 This is the best way
 Disconnect the battery ground cable or unplug the
fuse to the ECM
 will erase radio, seat, clock, and ECM adaptive
strategy memories.
 After clearing codes, re-energize on-board
diagnostics to verify that no codes are present.
 This will help to verify your repair.
How we use OBD
Future in Launch CRP909, 2023 scanner
Thank u for
ur
attention

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy