Autel AutoLink AL319 User manual

Table of Contents
1. SAFETY PRECAUTIONS AND WARNINGS.............................................. 1
2. GENERAL INFORMATION.......................................................................... 2
2.1 ON-BOARD DIAGNOSTICS (OBD) II ............................................................. 2
2.2 DIAGNOSTIC TROUBLE CODES (DTCS)........................................................ 2
2.3 LOCATION OF THE DATA LINK CONNECTOR (DLC) .................................... 3
2.4 OBD II READINESS MONITORS .................................................................... 4
2.5 OBD II MONITOR READINESS STATUS......................................................... 5
2.6 OBD II DEFINITIONS .................................................................................... 6
2.7 OBD II MODES OF OPERATION.................................................................... 7
3. USING THE SCAN TOOL............................................................................ 10
3.1 TOOL DESCRIPTION .................................................................................... 10
3.2 SPECIFICATIONS.......................................................................................... 11
3.3 ACCESSORIES INCLUDED............................................................................. 11
3.4 NAVIGATION CHARACTERS ........................................................................ 11
3.5 KEYBOARD.................................................................................................. 12
3.6 POWER ........................................................................................................ 12
3.7 SYSTEM SETUP ............................................................................................ 12
3.8 ABOUT......................................................................................................... 20
3.9 VEHICLE COVERAGE .................................................................................. 21
3.10 PRODUCT TROUBLESHOOTING.................................................................... 22
4. OBD II DIAGNOSTICS ................................................................................ 24
4.1 READING CODES ......................................................................................... 25
4.2 ERASING CODES.......................................................................................... 28
4.3 LIVE DATA .................................................................................................. 30
4.4 VIEWING FREEZE FRAME DATA ................................................................. 31
4.5 RETRIEVING I/M READINESS STATUS......................................................... 32
4.6 VIEWING VEHICLE INFORMATION.............................................................. 38
4.7 EXITING THE OBDII TEST......................................................................... 40
5. READY TEST ................................................................................................ 41
5.1 GENERAL INFORMATION ............................................................................ 41
5.2 TEST TOOL APPLICATION........................................................................... 42
5.3LED AND TONE INTERPRETATION.............................................................. 44
6. WARRANTY AND SERVICE...................................................................... 46
6.1 LIMITED ONE YEAR WARRANTY................................................................ 46
6.2 SERVICE PROCEDURES................................................................................ 46

1
1. Safety Precautions and Warnings
To prevent personal injury or damage to vehicles and/or the scan
tool, read this instruction manual first and observe the following
safety precautions at a minimum whenever working on a vehicle:
Always perform automotive testing in a safe environment.
Wear safety eye protection that meets ANSI standards.
Keep clothing, hair, hands, tools, test equipment, etc. away from
all moving or hot engine parts.
Operate the vehicle in a well ventilated work area: Exhaust gases
are poisonous.
Put blocks in front of the drive wheels and never leave the vehicle
unattended while running tests.
Use extreme caution when working around the ignition coil,
distributor cap, ignition wires and spark plugs. These
components create hazardous voltages when the engine is
running.
Put the transmission in PARK (for automatic transmission) or
NEUTRAL (for manual transmission) and make sure the parking
brake is engaged.
Keep a fire extinguisher suitable for gasoline/chemical/ electrical
fires nearby.
Don’t connect or disconnect any test equipment while the
ignition is on or the engine is running.
Keep the scan tool dry, clean, free from oil/water or grease. Use a
mild detergent on a clean cloth to clean the outside of the scan
tool, when necessary.

2
2. General Information
2.1 On-Board Diagnostics (OBD) II
The first generation of On-Board Diagnostics (called OBD I) was
developed by the California Air Resources Board (ARB) and
implemented in 1988 to monitor some of the emission control
components on vehicles. As technology evolved and the desire to
improve the On-Board Diagnostic system increased, a new generation
of On-Board Diagnostic system was developed. This second generation
of On-Board Diagnostic regulations is called "OBD II".
The OBD II system is designed to monitor emission control systems
and key engine components by performing either continuous or
periodic tests of specific components and vehicle conditions. When a
problemis detected, the OBD II system turns on a warning lamp (MIL)
on the vehicle instrument panel to alert the driver typically by the
phrase of “Check Engine” or “Service Engine Soon”. The system will
also store important information about the detected malfunction so
that a technician can accurately find and fix the problem. Here below
follow three pieces of such valuable information:
1) Whether the Malfunction Indicator Light (MIL) is
commanded 'on' or 'off';
2) Which, if any, Diagnostic Trouble Codes (DTCs) are stored;
3) Readiness Monitor status.
2.2 Diagnostic Trouble Codes (DTCs)
OBD II Diagnostic Trouble Codes are codes that are stored by the
on-board computer diagnostic system in response to a problem found
in the vehicle. These codes identify a particular problem area and are
intended to provide you with a guide as to where a fault might be
occurring within a vehicle. OBD II Diagnostic Trouble Codes
consists of a five-digit alphanumeric code. The first character, a letter,
identifies which control system sets the code. The other four
characters, all numbers, provide additional information on where the
DTC originatedand the operating conditions that caused it to set. Here
below is an example to illustrate the structure of the digits:

3
2.3 Location of the Data Link Connector (DLC)
The DLC (Data Link Connector or Diagnostic Link Connector) is the
standardized 16-cavity connector where diagnostic scan tools
interface with the vehicle's on-board computer. The DLC is usually
located 12 inches from the center of the instrument panel (dash),
under or around the driver’s side for most vehicles. If Data Link
Connector is not located under dashboard, a label should be there
telling location. For some Asian and European vehicles, the DLC is
located behind the ashtray and the ashtray must be removed to access
the connector. If the DLC cannot be found, refer to the vehicle’s
service manual for the location.
Identifying specific
malfunctioning
section of the
systems
Systems
B=Body
C=Chassis
P=Powertrain
U=Network
Code Type
Generic (SAE):
P0, P2, P34-P39
B0, B3
C0, C3
U0, U3.
Manufacturer Specific:
P1, P30-P33
B1, B2
C1, C2
U1, U2
Sub-systems
1= Fuel and Air Metering
2= Fuel and Air Metering
3= Ignition System or Engine
Misfire
4= Auxiliary Emission Controls
5= Vehicle Speed Control and Idle
Controls
6= Computer Output Circuits
7= Transmission Controls
8= Transmission Controls
DTC Example
P 0 2 0 2
Identifying specific
malfunctioning
section of the
systems

4
2.4 OBD II Readiness Monitors
An important part of a vehicle’s OBD II system is the Readiness
Monitors, which are indicators used to find out if all of the emissions
components have been evaluated by the OBD II system. They are
running periodic tests on specific systems and components to ensure
that they are performing within allowable limits.
Currently, there are eleven OBD II Readiness Monitors (or I/M
Monitors) defined by the U.S. Environmental Protection Agency
(EPA). Not all monitors are supported by all vehicles and the exact
number of monitors in any vehicle depends on the motor vehicle
manufacturer’s emissions control strategy.
Continuous Monitors -- Some of the vehicle components or systems
are continuously tested by the vehicle’s OBD II system, while others
are tested only under specific vehicle operating conditions. The
continuously monitored components listed below are always ready:
1）Misfire
2）Fuel System
3）Comprehensive Components (CCM)
Once the vehicle is running, the OBD II system is continuously
checking the above components, monitoring key engine sensors,
watching for engine misfire, and monitoring fuel demands.
Non-Continuous Monitors -- Unlike the continuous monitors, many
emissions and engine system components require the vehicle to be
operated under specific conditions before the monitor is ready. These

5
monitors are termed non-continuous monitors. For different ignition
type engines, the available monitors are different too.
The following monitors are to be used for spark ignition engines
only:
1) EGR System
2) O2 Sensors
3) Catalyst
4) Evaporative System
5) O2 Sensor Heater
6) Secondary Air
7) Heated Catalyst
The following monitors are to be used for compression ignition
engines only:
1) EGR System
2) NMHC Catalyst
3) NOx Aftertreatment
4) Boost Pressure System
5) Exhaust Gas Sensor
6) PM Filter
2.5 OBD II Monitor Readiness Status
OBD II systems must indicate whether or not the vehicle’s PCM’s
monitor system has completed testing on each component.
Components that have been tested will be reported as “Ready”, or
“Complete”, meaning they have been tested by the OBD II system.
The purpose of recording readiness status is to allow inspectors to
determine if the vehicle’s OBD II system has tested all the
components and/or systems.
The power-train control module (PCM) sets a monitor to “Ready” or
“Complete” after an appropriate drive cycle has been performed. The
drive cycle that enables a monitor and sets readiness codes to “Ready”
varies for each individual monitor. Once a monitor is set as “Ready”
or “Complete”, it will remain in this state. A number of factors,

6
including erasing of diagnostic trouble codes (DTCs) with a scan tool
or a disconnected battery, can result in Readiness Monitors being set
to “Not Ready”. Since the three continuous monitors are constantly
evaluating, they will be reported as “Ready” all of the time. If testing
of a particular supported non-continuous monitor has not been
completed, the monitor status will be reported as “Not Complete” or
“Not Ready.”
In order for the OBD monitor system to become ready, the vehicle
should be driven under a variety of normal operating conditions.
These operating conditions may include a mix of highway driving and
stop and go, city type driving, and at least one overnight-off period.
For specific information on getting your vehicle’s OBD monitor
system ready, please consult your vehicle owner’s manual.
2.6 OBD II Definitions
Powertrain Control Module (PCM) -- OBD II terminology for the
on-board computer that controls engine and drive train.
Malfunction Indicator Light (MIL) -- Malfunction Indicator Light
(Service Engine Soon, Check Engine) is a term used for the light on
the instrument panel. It is to alert the driver and/or the repair
technician that there is a problem with one or more of vehicle's
systems and may cause emissions to exceed federal standards. If the
MIL illuminates with a steady light, it indicates that a problem has
been detected and the vehicle should be serviced as soon as possible.
Under certain conditions, the dashboard light will blink or flash. This
indicates a severe problem and flashing is intended to discourage
vehicle operation. The vehicle onboard diagnostic system can not turn
the MIL off until necessary repairs are completed or the condition no
longer exists.
DTC -- Diagnostic Trouble Code (DTC) that identifies which section
of the emission control system has malfunctioned.
Enabling Criteria -- Also termed Enabling Conditions. They are the
vehicle-specific events or conditions that must occur within the
engine before the various monitors will set, or run. Some monitors
require the vehicle to follow a prescribed “drive cycle” routine as part

7
of the enabling criteria. Drive cycles vary among vehicles and for
each monitor in any particular vehicle.
OBD II Drive Cycle -- A specific mode of vehicle operation that
provides conditions required to set all the readiness monitors
applicable to the vehicle to the “Ready” condition. The purpose of
completing an OBD II drive cycle is to force the vehicle to run its
onboard diagnostics. Some form of a drive cycle needs to be
performed after DTCs have been erased from the PCM’s memory or
after the battery has been disconnected. Running through a vehicle’s
complete drive cycle will “set” the readiness monitors so that future
faults can be detected. Drive cycles vary depending on the vehicle and
the monitor that needs to be reset. For vehicle specific drive cycle,
consult the vehicle’s Owner’s Manual.
Freeze Frame Data -- When an emission related fault occurs, the
OBD II system not only sets a code but also records a snapshot of the
vehicle operating parameters to help in identifying the problem. This
set of values is referred to as Freeze Frame Data and may include
important engine parameters such as engine RPM, vehicle speed, air
flow, engine load, fuel pressure, fuel trim value, engine coolant
temperature, ignition timing advance, or closed loop status.
2.7 OBD II Modes of Operation
Here is a basic introduction to the OBD II communication protocol.
Mode byte: The first byte in the stream is the mode number. There
are 9 modes for diagnostic requests, so this first byte is from 1 to 9.
The first byte in the response data bytes is this same number plus 64.
For example, a mode 1 request would have the first data byte = 1,
and the response would have the first data byte = 65. Here is a brief
description of the modes:
Mode $01 - Identifies the Powertrain information and shows
current data available to the scan tool. This data includes: DTCs
set, status of on-board tests and vehicle data such as engine RPM,
temperatures, ignition advance, speed, air flow rates, and closed loop
status for fuel system.

8
Mode $02 - Displays Freeze Frame data. Same data as in mode 1,
but it was captured and stored when a malfunction occurred and a
DTC was set. Some of the PIDs for mode one are not implemented
in this mode.
Mode $03 - Displays the type of powertrain or emission related
DTCs stored by a 5 digit code identifying the faults. There may be
more than one response message if there are more trouble codes than
will fit in the data bytes of the response message, or if there are more
than one ECU computer responding.
Mode $04 - Used to clear DTCs and Freeze Frame data. This
clears all diagnostic trouble codes that may be set including freeze
frame data and readiness monitors.
Mode $05 - Displays oxygen sensor test results. This mode
displays the oxygen sensor monitor screen and the test results
gathered about the oxygen sensor.
There are ten numbers available for diagnostics:
1. $01 Rich-to-Lean O2 sensor threshold voltage
2. $02 Lean-to-Rich O2 sensor threshold voltage
3. $03 Low sensor voltage threshold for switch time
measurement
4. $04 High sensor voltage threshold for switch time
measurement
5. $05 Rich-to-Lean switch time in ms
6. $06 Lean-to Rich switch time in ms
7. $07 Minimum voltage for test
8. $08 Maximum voltage for test
9. $09 Time between voltage transitions in ms
Mode $06 - Non-Continuously Monitored Systems test results.
There are typically a minimum value, a maximum value, and a
current value for each non-continuous monitor. This data is optional,
and it is defined by a given vehicle make if it’s used.
Mode $07 - A request for DTCs (pending) from Continuously
Monitored Systems after a single driving cycle has been
performed to determine if repair has fixed a problem. This is

9
used by service technicians to verify repair was performed properly
and after clearing diagnostic trouble codes.
Mode $08 - This Special Control Mode requests control of the
on-board system, test, or component bi-directionally (where
applicable). This mode is manufacturer specific.
Mode $09 - Reports vehicle information. This information includes
vehicle VIN number and calibration information stored in the vehicle
ECUs.
Mode $0A - Requests emission-related Diagnostic Trouble Codes
with Permanent status. This mode is required for all
emissions-related DTCs. The presence of permanent DTCs at an
inspection without the MIL illuminated is an indication that a proper
repair was not verified by the on-board monitoring system.