Introduction; Tool Diagram - AutoXray CodeScout 2500 Manual De Usuario

Tabla de contenido
Idiomas disponibles

Idiomas disponibles

INTRODUCTION

The diagnostics were all proprietary to each vehicle manufacturer and were used for
diagnosing and repairing their own systems. OBD-I requires a malfunction indicator
lamp (MIL) or check engine light that relates to faulty electronic systems within the
engine control system. The MIL/Dash Indicator is usually amber or red in color.
OBD-I systems have to be able to store diagnostic trouble codes (DTCs) when a fault
has occurred and set the MIL on. Once the fault code disappears the code can be
lost and the MIL turned off. Different manufacturers were able to implement different
techniques as this was not in the legislation.
Description of OBD-II
CARB found that by the time an emission system component fails and causes the MIL
to illuminate, the vehicle may have been emitting excess emissions for some time.
The manufacturers had to develop new powertrain control module (PCM) self-
diagnostic strategies in response to increased diagnostic requirements from CARB.
The latest regulations developed by CARB and accepted by the EPA are designated
OBD-II.
The Federal Clean Air Act Amendments of 1990 requires that all vehicles sold in the
United States meet OBD-II requirements by the 1996 model year. The first OBD-II
systems appeared on selected vehicle types in 1994.
Some important OBD-II requirements are:
• Vehicle service information available to all technicians.
• Standardization of Terms (use of SAE J-1930 recommended terms).
• OBD-II requires a common diagnostic link connector (DLC) and specifies its
location in the vehicle.
• Generic scan tool.
• Generic emission-related diagnostic trouble codes (DTCs).
• Very specific malfunction indicator light (MIL) illumination protocol.
One very important part of the OBD-II requirements is that technical service
information for emissions related components and systems, which could affect the
vehicle's emission levels, will be available to all technicians; not just OEM dealership
technicians.
This allows all technicians to better understand how the systems recognize faults and
set the DTCs. The technician can now make a repair and verify the repair by exactly
duplicating the criteria that is required for the DTC to be set.
6
Menu Button
Read Button
Power Button
Navigate Left Button
Navigate Down Button
Cable connection
Your CodeScout will:
• Read the OBD-I and OBD-II codes off of your engine's computer .
• Provide on-screen definitions of generic and manufacturer specific diagnostic trouble
codes (DTCs).
• Provide readiness test status for emissions testing on OBD-II vehicles.
• Reset the check engine light on supported vehicles.
INTRODUCTION

Tool Diagram

Clear Button
Navigate Up Button
Enter Button
Navigate Right Button
SET-UP & OPERATION
General Information
7

Capítulos

Tabla de contenido
loading

Tabla de contenido