GENERIC
PID
DIAGNOSIS
BY KARL SEYFERT
52
September 2007
short-term and long-term fuel trim values, oxygen sensor voltages, engine and
intake air temperatures, MAF or MAP
values, rpm, calculated load, spark timing and diagnostic trouble code (DTC)
count. Freeze frame data and readiness
status also are available in OBD II
generic mode. A generic scan tool also
should be able to erase trouble codes
and freeze frame data when commanded to do so.
Data coming to the scan tool through
the mandated OBD II generic interface
may not arrive as fast as data sent over
one of the dedicated data link connector (DLC) terminals. The vehicle manufacturer has the option of using a
faster data transfer speed on other DLC
pins. Data on the generic interface also
may not be as complete as the information youll get on many manufacturer-
September 2007
53
specific or enhanced interfaces. For example, you may see an engine coolant
temperature (ECT) value in degrees on
the OBD II generic parameter identification (PID) list. A manufacturerspecific data list may display ECT status
in Fahrenheit or Celsius and add a separate PID for the ECT signal voltage.
In spite of these and other limitations,
OBD II generic mode still contains
many of the trouble codes, freeze frame
data and basic datastream information
needed to solve many emissions-related
issues.
There are nine modes of operation
described in the original J1979 OBD II
standard. They are:
This scan tool also allows the user to graph some PIDs,
while continuing to display the others in conventional
numeric format. Due to OBD IIs refresh capabilities on
some vehicles, its best to limit your PID choices to
those directly related to your diagnostic approach.
This photo illustrates how far PID data collection and display have come. Several
hundred thousand techs are still using the original Snap-on brick (on the left),
which displays a limited amount of PID data on its screen. Scrolling up or down
revealed more PIDs. The color version on the right brought graphing capability to
the brick, and extended the products life span by several years.
54
September 2007
Establish a Baseline
If youre repairing a vehicle that has
stored one or more DTCs, make sure
you collect the freeze frame data before
erasing the stored codes. This data can
56
September 2007
58
September 2007
The PCM uses this information to calculate the amount of fuel that should be
delivered to achieve the desired air/fuel
mixture. Check the MAF sensor for accuracy in various rpm ranges, including
wide-open throttle (WOT), and compare it with the manufacturers recommendations.
When checking MAF sensor read-
Heres a peek at some of the additional PID data thats available on latemodel vehicles. This screen capture
was taken from a CAN-enabled 2005
vehicle, and includes PIDs for EVAP
PURGE, FUEL LEVEL and WARM-UPS, as
well as familiar PIDs like BARO. This
much PID data in generic mode should
aid in diagnosis when manufacturerspecific PID data is not available.
ings, be sure to identify the unit of measurement. The scan tool may report the
information in grams per second (gm/S)
or pounds per minute (lb/min). Some
technicians replace the sensor, only to
realize later that the scan tool was not
set correctly. Some scan tools let you
change the units of measurement for
different PIDs so the scan tool matches
the specification in your reference manual. Most scan tools let you switch easily
between Fahrenheit and Celsius temperature scales, for example. But MAF
specs can be confusing when the scan
tool shows lb/min and we have a spec
for gm/S. Here are a few common conversion formulas, in case your scan tool
doesnt support all of these units of
measurement:
Degrees Fahrenheit 32 5/9 Degrees Celsius
Degrees Celsius 9/5 + 32 Degrees Fahrenheit
lb/min 7.5 gm/S
gm/S 1.32 lb/min
The Manifold Absolute Pressure
(MAP) Sensor PID, if available, indicates manifold pressure, which is used
by the PCM to calculate engine load.
The reading is normally displayed in
inches of mercury (in./Hg). Dont confuse the MAP sensor parameter with intake manifold vacuum; theyre not the
same. Use this formula: barometric
Vehicle Speed Sensor (VSS) and Throttle Position Sensor (TPS) PIDs for accuracy. These parameters can also be
used as reference points to duplicate
symptoms and locate problems in
recordings.
Most PID values can be verified by
a voltage, frequency, temperature,
vacuum or pressure test. Engine
coolant temperature, for example, can
be verified with a noncontact temperature tester, while intake manifold vacuum can be verified with an accurate
vacuum gauge. Electrical values also
should be tested with a DVOM. If the
electrical value exists at the sensor but
not at the appropriate PCM terminal,
then the component might be experiencing a circuit fault.
Calculated Values
Calculated scan tool values can cause a
lot of confusion. The PCM may detect a
failed ECT sensor or circuit and store a
DTC. Without the ECT sensor input,
Circle #31
September 2007
59
Also be aware that when a component such as an oxygen sensor is disconnected, the PCM may substitute a default value into the datastream displayed
on the scan tool. If a PID is static and
doesnt track with engine operating conditions, it may be a default value that
merits further investigation.
Circle #32
Circle #33
Circle #35
Circle #34
Graphing Data
If youve ever found it difficult to compare several parameters at once on a
small scan tool screen, graphing PIDs is
an appealing proposition. Graphing
multiple parameters at the same time
can help you compare data and look for
individual signals that dont match up to
actual operating conditions.
Although scan tool graphing isnt
equivalent in quality and accuracy to a
lab scope reading, it can provide a comparative analysis of the activity in the
two, three, four or six oxygen sensors
found in most OBD II systems.
Many scan tools are capable of storing a multiple-frame movie of selected
PIDs. The scan tool can be programmed
to record a movie after a specific DTC
is stored in the PCM. Alternatively, the
scan tool movie might be triggered
manually when a driveability symptom
occurs. In either case, you can observe
the data or download it and print it later. Several software programs let you
download a movie, then plot the values
in a graphical display on your computer
monitor.
60
September 2007
52
March 2005
INTERPRETING
GENERIC
SCAN DATA
BY BOB PATTENGALE
the number of potential generic parameters to more than 100. Fig. 2 on page
56 shows data from a CAN-equipped
2005 Dodge Durango. As you can see,
the quality and quantity of data has increased significantly. This article will
identify the parameters that provide the
greatest amount of useful information
and take a look at the new parameters
that are being phased in.
No matter what the driveability issue happens to be, the first parame-
March 2005
53
Fig. 1
54
March 2005
Fig. 2
56
March 2005
Fig. 3
sensor in real time. The PCM receives the data from the oxygen sensor, processes it, then reports it to the
scan tool. Also, a fundamental OBD
II generic limitation is the speed at
which that data is delivered to the
scan tool. In most cases, the fastest
possible data rate is approximately 10
times a second with only one parameter selected. If youre requesting
and/or displaying 10 parameters, this
slows the data sample rate, and each
parameter is reported to the scan tool
just once per second. You can achieve
the best results by graphing or displaying data from each oxygen sensor
separately. If the transition seems
slow, the sensor should be tested with
a lab scope to verify the diagnosis before you replace it.
Engine Speed (RPM) and Ignition Timing Advance can be used
to verify good idle control strategy.
Again, these are best checked using a
graphing scan tool.
The RPM, Vehicle Speed Sensor
(VSS) and Throttle Position Sensor
(TPS) should be checked for accuracy.
Additional OBD II
Parameters
Now, lets take a look at the more recently introduced OBD II parameters.
These parameters were added on 2004
CAN-equipped vehicles, but may also
be found on earlier models or nonCAN-equipped vehicles. For example,
the air/fuel sensor parameters were
available on earlier Toyota OBD II vehicles. Fig. 2 was taken from a 2005
Dodge Durango and shows many of
the new parameters. Parameter descriptions from Fig. 2 are followed by
the general OBD II description:
FUEL STAT 1 Fuel System 1
Status: Fuel system status will display
more than just Closed Loop (CL) or
Open Loop (OL). You might find one
March 2005
57
Fig. 4
58
March 2005
Fig. 5
60
March 2005
value for this parameter. The blue circle highlights the equal sign (=), indicating that more than one ECU supports this parameter and similar values
have been received for this parameter.
Another possible symbol is the exclamation point (!), indicating that no responses have been received for this
parameter, although it should be supported. This information will be useful
in diagnosing problems with data on
the CAN bus.
As you can see, OBD II generic data
has come a long way, and the data can
be very useful in the diagnostic process.
The important thing is to take time to
check each parameter and determine
how they relate to one another.
If you havent already purchased an
OBD II generic scan tool, look for
one that can graph and record, if possible. The benefits will immediately
pay off. The new parameters will take
some time to sort out, but the diagnostic value will be significant. Keep
in mind that the OBD II generic
specification is not always followed to
the letter, so its important to check
the vehicle service information for
variations and specifications.
Visit www.motor.com to download
a free copy of this article.
DATASTREAM
IN-DEPTH
ANALYSIS
BY SAM BELL
We began this two-part article with a
discussion of preliminary OBD II datastream
analysis, conducted with the engine off.
Were going deeper this time, to explain
the value of datastream information
collected with the engine running.
August 2008
37
bit higher than BARO. The generic interface allows calculated values, but
never substituted values.
So, what are we looking for, now that
weve finally started the engine? The
specific answer, of course, will depend
largely on the details of the customer
complaint and/or DTC(s) that are
stored. We might, for example, be focusing on fuel trim numbers (and trends) if
our code suggests an underlying air/fuel
metering problem. We might be looking
most closely at engine coolant temperature, and time-until-warm measurements when that seems warranted. Perhaps our problem lies in the evap area,
or involves EGR flow. But ultimately, it
doesnt matter what the specific issue is;
well have to focus in on the systemic interactions that determine the overall
characteristics of a particular data set.
Heres a concrete example to illustrate what I mean. The vehicle in question is a 1999 Chevy Venture minivan
with the 3.4L V6. There was a DTC
38
August 2008
When evaluating a
fuel trim trouble
code, one of the
first steps must
always be to verify
that the oxygen
sensor (on which the
DTC is based) is
functioning correctly.
Graphical representations of scan data movies can speed analysis. As an added bonus,
using your scanners flight recorder mode allows you to concentrate on your driving. The
data set here clearly points to a lack of adequate fuel volume. This graphical representation is derived from the exact same movie capture seen in the chart on the previous page.
ing found the idle lambda at a ridiculously low value of .85 (indicating a mixture with 15% more fuel than needed), I
was not surprised to see that the O2 sensor didnt register a rich condition until
the engine was very nearly flooded with
propane. When I removed the purge
hose, engine rpm climbed and the engine smoothed out, while lambda
marched toward the stoichiometric ideal
value of 1.00. Once the faulty O2 sensor
was replaced, all aspects of driveability
improved, and the minivan returned to
its previous fuel consumption levels.
Dynamic tests verify DTC accuracy.
In some instances, we may be able to
utilize bidirectional controls embedded
within our scan tool packages to actuate
various components. In other cases, we
may need to improvise, using signal
simulators, power probes, jumpers,
propane or just good, old-fashioned test
driving as required to initiate change
within the system were working on.
(Im not saying that it will always be as
actual root fault and, of course, problems that set appropriate codes yet are
still really hard to diagnose.)
August 2008
39
Monitors 1.01
ost MOTOR readers have at least a passing familiarity with the concept of OBD II monitor
completion status. Even so, a brief refresher may be
in order. OBD II monitors are simply formalized sets
of self-tests all related to a particular system or
component.
Continuous monitors. With a few very rare exceptions (mostly for 1998 and earlier models), the
so-called continuous monitors always show up as
complete, done or ready. Take this status report with a grain of salt. Unplug the IAT sensor, start
the engine and check that the Comprehensive
Component Monitor readiness status shows complete. Is the MIL on? Are there any pending codes?
How long would you have to let the vehicle idle before it will trip the MIL and show a P0113 (IAT Sensor Circuit Voltage High) DTC?
As it turns out, depending on the specific make,
model and powertrain package, there are several
specific criteria that must be met before the code
will set. In one instance, the PCM must detect a VSS
signal of 35 mph or more and an ECT value of 140F
or more, the calculated IAT must be less than 38F
and all of these conditions must be met for at least
180 seconds of continuous duration, during which
no other engine DTCs are setall while MAF is less
than 12 grams per second. (This particular example,
incidentally, is a two-trip code. Some other manufacturers may make this and other DTCs under the
component monitors jurisdiction into one- or twotrip codes, sometimes with even more complicated
entry criteria.)
Continuous monitors include the comprehensive
component monitor, the fuel monitor and the misfire monitor. Each monitor runs continuously when
conditions are appropriate, but not during all actual driving. For example, the misfire monitor is often
suspended during 4WD operation, since feedback
through the axles over rough roads might cause
uneven disruption of the CKP signals, which could
40
August 2008
otherwise be misidentified as misfires. Similarly, extremely low fuel tank levels may suspend both misfire and fuel system monitors to avoid setting a
DTC for running out of gas.
Noncontinuous monitors. As I pointed out last
month, its important to note the readiness status of
the other, noncontinuous monitors as well. These are
the monitors whose status will change to incomplete, not ready or not done when the codes
are cleared. If a vehicle arrives at your shop showing
one or more incomplete monitors, its likely that
someone has already cleared the codes before it got
to you. (There are a few vehiclesfor example, some
1996 Subaruswhich may reset monitor status to incomplete at every key-off, or other vehicles which
may have certain monitors which cannot be made to
run to completion in normal driving, such as the evap
monitor on some Toyota Paseos.) If a vehicle shows
up with incomplete monitors, however, you should
certainly document that fact on your work order and
be sure to advise the customer that theres a very real
possibility that one or more other codes may recur after the current repair has been completed. For more
on this subject, see my article How Not to Get MILStoned in the April 2004 issue of MOTOR.
More importantly, for our present purposes, the
existence of incomplete monitors means that you
may not be getting the whole picture as to what
ails the vehicle youre looking at. Keep an open
mind, remembering that there may be other, as yet
unknown issues hidden behind that incomplete
monitor, and try not to rush your diagnosis. As
mentioned in last months installment, there may
be some valuable data accessible via Mode 6 even
if the monitor is not complete, but there is a very
real possibility that Mode 6 data for any incomplete monitor may turn out to be unreliable. And,
of course, dont overlook any pending DTCs. Remember, these do not illuminate the MIL, so you
must seek them out on your own.
actually need. Three or four are usually sufficient. This is your version of
the filmmakers high-speed action
trick, as you get more updates per
unit time the fewer PIDs you select.
With several hundred possible PIDs
from which to choose, its just too
Lights Out?
42
August 2008
DATASTREAM ANALYSIS
The net result is that we may have to clear the current
DTCs and extinguish the MIL before our test drive can
bear fruit. (But again, please be sure to read and record
all the freeze frame data, the status of all monitors, the list
of both current and pending DTCs and any available
Mode 6 data before clearing the MIL (see Lights Out?
on page 42).
Well need to drive long enough to let the monitors in
question reach completion. In some cases, this may require
an extended period of time. Many Ford products, for example, normally require a minimum of a six-hour cold-soak before the evap monitor can run, although there may be ways to
force this issue in some instances. Many Chrysler oxygen sensor monitors run only after engine shut-down (with key off),
so that no amount of driving will ever bring them to completion. Certain monitors, and apparently even certain scan tools,
may require a key-off sequence before the monitor status will
update from incomplete to complete. MOTOR offers an excellent resource to help you understand these detailsthe OBD
II Drive Cycle CD Version 7.0, available from your local
MOTOR Distributor (1-800-4A-MOTOR).
In some cases, local weather conditions may make monitor
completion seem impossible until a later date, usually because of ambient temperature requirements, although sometimes as a result of road conditions. In most cases, however, it
will still be possible to complete the monitor by running the
vehicle on a lift or dynamometer. This option may occasionally result in setting, say, an ABS code, but most monitors can
be run to completion swiftly and successfully on a lift. This
option may also offer a safer, faster alternative to actual driving, as trees and telephone poles are less likely to jump in
front of a vehicle on a stationary lift.
Circle #22
44
August 2008
Conclusions
Proper in-depth datastream analysis
can often light the way toward correct
diagnosis of driveability concerns.
Recording all available DTCs, pending
DTCs, freeze frame data and Mode 5
and Mode 6 results before clearing any
DTCs is essential. Specific setting criteria for each DTC are manufacturerdetermined, regardless of whether the
code assigned is generic or manufacturer-specific. Freeze frame data sets
can be used to recreate the operating
conditions under which a previous failure occurred and can help illuminate
the conditions under which certain
self-tests are conducted. Mode 5 and
Mode 6 test results can help in analyzing the type and extent of certain failures. KOEO datastream analysis can
sometimes reveal sensor faults or rationality concerns that might otherwise be
overlooked.
Looking at KOEO and KOER datastream on a regular basis makes knowngood values familiar. Once you know
When trying to
resolve a MIL-on
complaint, its
critical to first
review the exact
code-setting
criteria and the
operating
conditions as
revealed in the
freeze frame data.
Circle #23
August 2008
45
28
July 2006
SUCCESSFUL
MAF
SENSOR
Photoillustration by Harold Perry; photos courtesy Wells Manufacturing Corp.
DIAGNOSIS
BY SAM BELL
A broad range of seemingly unrelated or
contradictory driveability complaints
may arise from MAF sensor
performance faults. Use this guide to
navigate out of a diagnostic thicket or,
better still, to avoid one entirely.
entering an engines combustion chambers must be seen by the MAF sensor. This means that any vacuum or air
leak downstream of the sensor will result in insufficient fuel metering, causing a lean condition in open-loop operation and higher-than-normal fuel trim
values in closed-loop. When we encounter a MAF sensor-equipped vehicle exhibiting these symptoms, we need
July 2006
29
Fig. 1
includes at least three sustained WOT
accelerations. (Its not necessary to
speed to accomplish a sustained WOT
acceleration. Rather than a WOT snap
from idle, an uphill downshift at 20 to
30 mph is usually sufficient. The WOT
prescription can be met at throttle
openings as low as 50% to 70%.) The
BARO PID should update from its default reading by the end of the third
WOT acceleration. If its now close to
your local barometric pressure, the
MAF sensor is not likely to be faulty. If
BARO is not close, try one of the cleaning techniques explained in the sidebar
Keeping It Clean on page 34, then
again reset KAM and take a test drive. If
the BARO is still out of range, a replacement MAF sensor is in your customers
future. Unfortunately, in many 2002 and
later Fords, the calculated BARO PID is
supplanted by a direct BARO reading
Fig. 3
30
July 2006
Fig. 2
taken from a sensor incorporated into
the ESM (EGR System Management)
valve, greatly lessening its diagnostic value for our current purposes.
If the oxygen sensor monitor status
showed INCOMPLETE above, youll
have to verify O2 sensor accuracy and
performance before performing the
KAM reset procedure. Use a 4- or 5-gas
analyzer to determine whether the
air/fuel ratio is correct in closed-loop
operation. The notes about lambda ()
below should help.
Outside of the Ford family, MAF
sensor diagnosis is more difficult. Large
fuel trim correctionseither positive or
negativeare often the only initial
pointer to MAF sensor problems.
Again, any and all air leaks downstream
of the MAF sensor must be repaired
first. Since accurate fuel trim corrections depend on correct O2 sensor out-
Fig. 4
Fig. 5
it.) Use your scan tool to record critical
data PIDs and graph them for analysis.
Here are a couple of examples:
In Fig. 1 on page 30, taken during a
period of closed-loop operation, shortterm fuel trims (blue and green traces)
for each bank were above 13% at 1100
rpm (red trace), yet dropped sharply
negative at 3600 rpm, proving that inadequate fuel delivery was not the problem.
The values indicated in the legend boxes correspond to the readings obtained
Fig. 6
at the indicated cursor position (vertical
black line). The vertical white line indicates the trigger point for the recording.
Subsequent diagnostics focused on the
MAF sensor and the PCV system.
Take a look at the scan data graph
shown in Fig. 2. It shows a car whose
faulty fuel pump was unable to deliver
sufficient fuel under high load conditions. Notice the very low O2 sensor
readings (displayed in blue) corresponding to the cursor (black vertical
32
July 2006
mass confusion that may arise under hard acceleration when longterm negative fuel trim corrections,
learned in closed-loop under lowflow-rate conditions, are applied
precisely when positive fuel trim corrections would be more appropriate.
So, for example, when the system
goes to open-loop during hard acceleration where the MAF is already
underreporting airflow by up to
30%, the PCM may subtract an additional 10% to 15% (LTFT) from the
normal fuel delivery calculation,
leaving the system as much as 45%
leaner than desired!
In midrange operation, the two
effects (surface area and insulative
properties) may roughly cancel each
out, with fuel trims being more or
less normal. Additionally, the exact
chemistry and configuration of dirt
buildups can vary, changing the balance of power between the surface
area and insulative effects.
Fig. 7
here suggests, but does not prove, that
the MAF sensor is functioning well under these conditions. If the airflow report was consistently increased or decreased by the same factor, say 10% or
even 50%, the shape of its graph would
remain the same.
Consider the additional plots presented in Fig. 7 above. Does the extra
data shed any light on the MAF sensors
accuracy? Or is this just an example of
too much information?
Since short-term and long-term fuel
Keeping It Clean
34
July 2006
Fig. 8
biased oxygen sensors may cause similar
symptoms. Without appropriate testing,
its hard to distinguishjust by drivingamong certain ignition or knock
sensor faults and MAF sensor malfunctions. Additionally, since MAF sensors
are somewhat pricey, many technicians
are afraid to condemn them, fearing either the customers or the boss wrath if
their diagnosis is not borne out. Perhaps
Circle # 27
36
July 2006
20
July 2014
Photoillustration: Harold A. Perry; images: Thinkstock, David Kimble, Sun & General Motors
BY SAM BELL
A resourceful diagnostician knows
complicated and expensive equipment
isnt always needed. Tools with a narrower
focus, combined with an enlightened
approach, allow him to get the job done.
GENERIC DATASTREAM
generic datastream stems from the requirement that it not display substituted
values. While many so-called enhanced
interfaces offer access to a greater number of data PIDs, some of these may reflect substituted values not based on
current operating data. For example,
most Chrysler products will substitute a
reasonable guess for the actual intake
manifold vacuum value when the MAP
sensor is unplugged. If you look in the
enhanced datastream, youll see that
value varying quite believably as you rev
the engine or drive the vehicle. If you
look at MAP_Volts, however, youll see
a fixed value reflecting reference voltage (Vref) for the sensor circuit. But
how often do you actually look at that
PID instead of the vacuum reading?
While substituted values are prohibited in the generic datastream, calculated
values are not. Thus, for example, an
ECT PID of 40F reflects the calculated temperature of an open ECT sensor circuit. In such cases, Toyota, for example, has for many years, then substituted a value of 176F in its enhanced
datastream, but not in the generic data.
In our unplugged Chrysler MAP sensor
example above, using a generic interface, youd see an unmoving value of
something in the neighborhood of
255kPa or higher, corresponding to a
boost pressure of about 25 psi above atmospheric.
As a technical consultant to our state
EPA, several times a year I encounter
vehicles which have failed our OBD II
plug & play state emissions test for a
MIL-on condition with one or more current DTCs that simply do not appear in
the enhanced interface, but which are
readily retrieved using a generic hookup. Im afraid I cant shed a lot of light
on why this would occur since, clearly, it
should not. Thus far, I have not encountered this issue in any 2008 or later vehicles. There seem to be a few makes
July 2014
21
22
July 2014
These two screen shots show the 60 lines of generic data available from a
known-good 2014 Mazda CX-5, as captured via a Snap-on SOLUS Ultra scan tool.
starting with a model year 2005 phasein, several new parameters have been
added to the original generic data list.
These include both commanded and actual fuel-rail pressure, EGR command
and EGR error calculation, commanded
purge percentage, commanded equivalence ratio and a host of others, including many diesel-specific PIDs.
In-use counters may also indicate
how many times each of the various onboard monitors has run to completion
since the codes were last cleared. The
list on page 24 includes most of the
generic PIDs currently in widespread
use. However, since not all manufacturers support all PIDs, and since their
choices may vary by model, engine
and/or equipment, the list given here
represents only a portion of the PIDs
24
July 2014
Generic PIDs
LTFT_x (per bank) - long-term
fuel trim
VSS - vehicle speed sensor
HO2SBxSy - heated oxygen
sensor, Bank x, Sensor y, such
as B1S2 for a bank 1 downstream sensor
IGN_ADV - ignition timing,
measured in crankshaft degrees
SAS or SEC_AIR - commanded
secondary air status off/on; may
include information such as atmosphere, upstream or downstream of converter, commanded on for diagnostic purposes
RUN_TIME - seconds since last
engine start; some manufacturers stop the count at 255
seconds
DISTANCE TRAVELED WITH
MIL ON in miles or km
FRP - fuel rail pressure relative
to intake manifold pressure
FRP_G - fuel rail pressure,
gauge reading
O2Sx_WR_lambda(x) - wide
range air/fuel sensor, bank x,
equivalence ratio (0-1.999) or
voltage (0-7.999)
EGR - commanded EGR percentage
EGR_ERR - deviation of sensed
or calculated position from
commanded position, percent
PURGE - commanded percentage
FUEL_LVL - fuel level input percentage; can provide especially
invaluable information in freeze
frame diagnostics of misfire
codes set under ran-out-ofgas conditions; unfortunately,
not universally implemented
WARMUPS - number of warmups since codes cleared; a
warm-up is an ECT increase of
at least 40F in which the ECT
reaches at least 160F
DIST SINCE CLR - distance
since codes cleared
EVAP_PRESS - evaporative system pressure
26
July 2014
Glossary
battery is disconnected and all capacitors are discharged.
PID - parameter identification; a value found in current or freeze frame
data; may indicate a sensor reading,
calculated value or command status.
In a nongeneric (enhanced) interface,
may indicate a substituted value.
$- or -$ - prefix or suffix indicating
that an alphanumeric string is hexadecimal (presented in base 16.) The
J1979 specifications which establish
the OBD II protocol are written using
hexadecimal notation throughout.
Datastream - a set of PID values, DTCs,
test results and/or PDTCs; the display
of such data on or via a scan tool.
Freeze frame - a set of PID values indicating then-current data written
into the PCMs memory when a DTC
Beyond PIDS
Circle #16
28
July 2014
Circle #17
July 2014
29
Driveability Corner
New PIDs provide additional information that can be included in
your diagnostic efforts. But before it can be used, you must understand how it was obtained and what its intended to represent.
Mark
Warren
smwarren@motor.com
he commanded equivalence
(EQ) ratio parameter (PID) is
required in the generic datastream on all passenger vehicles since 2008 (see the EQ to
air/fuel ratio [AFR] matrix on
the next page and the SAE definition in the
box on page 13). An EQ of 1 equals 14.7:1
AFR. This PID should reflect the commanded air/fuel ratio. That being said,
there are no Bank1 and Bank2 EQ ratio
PIDs, and cant the EQ or AFR be different for each bank? Are the two averaged?
Yipes! How is this going to work on a
vehicle?
This test was performed on a 2010 Toyota
Tacoma with a 4.0L engine. Its important
to note that this may not be representative
of other vehicles; this is one test. Also, this
test is not intended to be critical of any implementation of the EQ PID. I think the
problem is in the original definition of this
10
February 2015
Data Analysis
Remember that the air/fuel ratio
sensors (charts 2 and 3) read high
when lean and low when richthe
opposite of the O2 sensors that are
[
{