Table of Contents
Advertisement
GENERAL INFORMATION
pre-test screens will help with this for MONITOR
DTC's), this is called a TRIP. All OBDII/Euro Stage
III OBD DTCs will be set after one or in some cases
two trip failures, and the MIL will be turned on.
These DTC's require three successful, no failures,
TRIPS to extinguish the MIL, followed by 40
warm-up cycles to erase the DTC. For further
explanation of TRIPS, Pre-test screens, Warm-up
cycles, and the use of the DRBIII , refer to the On
Board Diagnostic training booklet #81-699-97094.
3.3.2 INTERMITTENT CODE
A diagnostic trouble code that is not there every
time the PCM checks the circuit is an intermittent
DTC. Most intermittent DTC's are caused by wiring
or connector problems. Defects that come and go
like this are the most difficult to diagnose; they
must be looked for under specific conditions that
cause them. The following checks may assist you in
identifying a possible intermittent problem:
•
Visually inspect related wire harness connectors.
Look for broken, bent, pushed out, or corroded
terminals.
•
Visually inspect the related harnesses. Look for
chafed, pierced, or partially broken wire.
•
Refer to any technical service bulletins that may
apply.
•
Use the DRBIII data recorder or co-pilot.
3.3.3 STARTS SINCE SET COUNTER
The start since set counter counts the number of
times the vehicle has been started since codes were
last set, erased, or the battery was disconnected.
The reset counter will count up to 255 start counts.
The number of starts helps determine when the
trouble code actually happened. This is recorded by
the PCM and can be viewed on the DRBIII
STARTS since set.
When there are no trouble codes stored in mem-
ory, the DRBIII will display NO DTC's Detected
and the reset counter will show STARTS since clear
= XXX.
3.3.4 DISTANCE SINCE MI SET
The Euro Stage III OBD directive requires that
the distance traveled by the vehicle while the MI is
activated must be available at any instant through
the serial port on the standard data link connector.
This feature works as follows:
1. If the MI is illuminated due to a fault, the
distance count is updated (i.e. it is counting).
2. If there is a stale MI fault (i.e. the fault is still
frozen in memory but the MI has been extin-
guished due to 3 good trips), the distance count is
held (i.e. frozen).
3. If the distance count is being held due to (Item
2.) and the fault is cleared, the distance is
cleared (set to zero).
4. If the distance count is being held due to (Item
2.) and another MI occurs, the distance count is
reset (to) and begins updating anew.
5. If a fault occurs while the MI is already illumi-
nated due to a previous fault (the distance count
is updating), then the distance count continues
to update w/out interruption.
6. If the MI is flashing due to active misfire and
there is an active fault (i.e. matured fault for
which 3 good trips have not occurred), the dis-
tance count behaves as the MI in ON.
7. If the MI is flashing due to active misfire and
there is no active fault (i.e. the MI is flashing for
a 1 malf.), the distance count behaves as if the
MI is off (because it is not yet a matured fault).
8. The distance count is cleared whenever the fault
is cleared. (Via 40 warm up cycles, or via scan
tool).
3.4 USING THE DRBIII
Refer to the DRBIII user's guide for instructions
and assistance with reading DTC's, erasing DTC's,
and other DRBIII functions.
3.5 DRBIII ERROR MESSAGES AND
BLANK SCREEN
Under normal operation, the DRBIII will dis-
play one of only two error messages:
– User-Requested
Requested COLD Boot
If the DRBIII
message, record the entire display and call the Star
as
Center for information and assistance. This is a
sample of such an error message display:
ver: 2.14
date: 26 Jul93
file: key_itf.cc
date: Jul 26 1993
line: 548
err: 0x1
User-Requested COLD Boot
Press MORE to switch between this display
and the application screen.
Press F4 when done noting information.
3.5.1 DRBIII DOES NOT POWER UP
If the LED's do not light or no sound is emitted at
start up, check for loose cable connections or a bad
cable. Check the vehicle battery voltage (data link
12
WARM
Boot
or
should display any other error
User-
Advertisement
Table of Contents
