STAR TekInfo

STI Home

Body And Accessories

Chassis & Drivetrain

Volume 1

Diagnostic Manual, Chassis and Drivetrain,
Volume 3

Printable version

LOCATION:

0 Connection and Use of Test Equipment > 3/1 Connecting Hand-Held Tester or Impulse Counter...

Connecting Hand-Held Tester or Impulse Counter Scan Tool, Reading and Erasing Diagnostic Trouble Code Memory


Observe all system specific instructions listed in the "Preparation for Test" section of each Test Program. Diagnostic trouble codes (DTC's) which have been stored due to testing or the disconnection of lines must be erased from the diagnostic trouble code memory at the end of testing.

Connect Hand-Held Tester (HHT) according to connection diagram:

See 3/5, 6
The following functions can be performed according to the instructions on the display:
a) Reading/erasing DTC memory
b) Reading actual values
c) Performing activations
d) Programming control modules

Connect Impulse Counter Scan Tool (according to connection diagram).
LED "U-Batt" must light up in the display.
If LED does not light up, check:
a) Voltage supply.
b) Impulse counter scan tool fuse.

DTC readout is no longer possible using the impulse counter scan tool, with some systems, please review 12 in each system section prior to starting the DTC readout for the system being checked.

1.

2.
Read Diagnostic Trouble Code Memory
a) Ignition: ON
b) Press start button for 2 to 4 seconds.
c) Read and record diagnostic trouble code (DTC).
d) Press start button again for 2 to 4 seconds.
e) Read and record DTC.
Repeat steps d) and e) until the first DTC reappears.

Clear Diagnostic Trouble Code Memory 1)
a) Press start button for 2 to 4 seconds (DTC appears)
b) Wait 3 seconds, then press start button for 6 to 8 seconds, thereby erasing the previously displayed DTC from memory.
c) Each stored DTC must be erased individually.

1) Erasing of stored diagnostic trouble codes must begin within 20 seconds of reading the DTC. After 20 seconds, the DTC can no longer be erased. Erasing procedure can be restarted by performing DTC memory readout after the fault is again displayed.