RCM FAULT REPORTING USING DTCS AND TSB 07-12-3

BIT-MAPPED PARAMETER IDENTIFIERS (PIDS)—

SERVICE TIPS

2003-2006 Lincoln LS
FORD:
2006 Zephyr
2001-2007 Crown Victoria
2007 MKZ
2002-2007 Taurus
2003-2005 Aviator
2004-2007 Focus
2003-2007 Navigator
2005-2007 Five Hundred, Freestyle, Mustang
2006-2007 Mark LT
2006-2007 Fusion
2001-2003 Explorer Sport MERCURY:
2001-2007 Explorer Sport Trac 2001-2007 Grand Marquis
2002-2003 Windstar 2002-2005 Sable
2002-2007 Explorer 2005-2007 Montego
2003-2007 Expedition 2006-2007 Milan
2004-2007 F-150, Freestar 2002-2007 Mountaineer
2005-2007 Escape Hybrid, Escape 2004-2007 Monterey
2007 E-Series 2005-2007 Mariner
2006-2007 Mariner Hybrid
LINCOLN:
2001-2007 Town Car

This article supersedes TSB 07-7-8 to update the SERVICE TIPS

vehicle application.
DTCs And Associated Fault PIDs Description
ISSUE Many of the continuous memory and on-demand
Various 2001-2007 vehicles are equipped with a DTCs that can be present in the RCM provide
restraints control module (RCM) that report general fault information and require accessing the
diagnostic trouble codes (DTCs) which provide associated bit-mapped PIDs (fault PIDs) to identify
general fault information. These DTCs require the specific concern. DTCs that use fault PIDs are
accessing the associated bit-mapped PIDs (fault conceptually different from conventional DTCs.
PIDs) to identify the specific fault. Most 2001-2006
Workshop Manuals (WSM) were written using New Conventional DTCs identify a specific concern for a
Generation STAR Tester (NGS) terminology and given component and point to a particular diagnostic
navigation which does not translate well when using path. In the diagnostic path, PIDs are sometimes
Integrated Diagnostic System (IDS), Portable used to determine the root cause.
Diagnostic Software (PDS) or Worldwide Diagnostic
System (WDS). DTCs that use fault PIDs do not identify the specific
concern. The DTC identifies the component(s) or
ACTION type of component(s) in which the concern exists.
Refer to the Service Tips to assist with navigation The next level, fault PIDs, identifies the specific
of both the WSM and the scan tool being used. device and fault condition. Fault PIDs are available
for both on-demand (active) and continuous memory
(historic or intermittent) DTCs. A scan tool must be
used to view the DTCs and their fault PIDs. The
table lists those DTCs that are supported by
associated fault PIDs. (Figures 1-5)

NOTE: The information in Technical Service Bulletins is intended for use by trained, professional technicians with the knowledge, tools, and equipment to do
the job properly and safely. It informs these technicians of conditions that may occur on some vehicles, or provides information that could assist in proper
vehicle service. The procedures should not be performed by “do-it-yourselfers”. Do not assume that a condition described affects your car or truck. Contact a
Ford, Lincoln, or Mercury dealership to determine whether the Bulletin applies to your vehicle. Warranty Policy and Extended Service Plan documentation
determine Warranty and/or Extended Service Plan coverage unless stated otherwise in the TSB article.The information in this Technical Service Bulletin
(TSB) was current at the time of printing. Ford Motor Company reserves the right to supercede this information with updates.The most recent information is
available through Ford Motor Company’s on-line technical resources.

Copyright  2007 Ford Motor Company Online Publication Date June 6, 2007 PAGE 1
 TSB 07-12-3 (Continued)

VIEWING FAULT PIDS USING SCAN TOOLS

4. To view the fault PIDs associated with a
WSM Direction to FLAG DTC/View Fault PIDs continuous memory DTC:
The information in viewing fault PIDs in the WSM a. Toolbox
has evolved over the years as the scan tools have
transitioned. Examples of how the WSM may direct b. DataLogger
you to view fault PIDs are: c. Modules
• FLAG DTC XXXXX/Record All Flagged Faults
(2001-2006 WSMs) d. RCM
• View and Record DTC XXXXX Fault PIDs (2007 5. Monitor all “_CM” PID(s) matching the DTC
WSM) present; follow diagnostic procedure for the PID
• DataLogger/View and Record DTC XXXXX Fault that reads “FAULT”.
Pids (2008 and future WSMs) • For example, a B2296 fault is present. In
DataLogger the fault PID 2296_18_CM PID
In each instance the direction is the same (view
reads “FAULT” indicating a front internal
fault PIDs to identify the specific component and
crash sensor fault.
fault condition) but how they are accessed by the
scan tools, as well as the scan tool terminology, will IDS/PDS Fault PID Naming Conventions
vary.
The fault PIDs as displayed on IDS/PDS uses a
FLAG the DTC - View the Fault PIDs strategy associating it with the DTC. For example,
the fault PIDs 2296_18_OD and 2296_18_CM break
For example, the “Flag” DTC feature is specific to
down as follows:
NGS/NGS+. When using IDS/PDS it is necessary to
view the fault PIDs from DataLogger. • 2296 - The DTC number minus the “B” (body) or
“C” (chassis) designation.
Using IDS/PDS • 18 - An identifier used to distinguish between
NOTE each of the fault PIDs associated with the DTC.
WHEN USING IDS/PDS, MOVE THE CURSOR • OD - Identifies the fault PID as an on-demand
OVER THE PID OR SELECT THE PID TO fault.
DISPLAY ITS DEFINITION AT THE BOTTOM OF • CM - Identifies the fault PID as a continuous
THE SCREEN. WHEN USING PDS, HIGHLIGHT memory (intermittent) fault.
OR MOVE THE STYLUS OVER THE PID TO SEE
THE PID DEFINITION. NOTE
THE DTCS AND FAULT PIDS SUPPORTED BY A
1. Perform a self test of the RCM and/or OCS VEHICLE WILL VARY DEPENDING ON VEHICLE
module to retrieve on-demand and continuous EQUIPMENT.
memory DTCs.
Table lists each of the fault PIDs as displayed on
2. To view the fault PIDs associated with an IDS/PDS and their description. (Figures 1-5)
on-demand DTC:
WARRANTY STATUS: Information Only
a. Toolbox
b. DataLogger
c. Modules
d. RCM
3. Monitor all “_OD” PID(s) matching the DTC
present; follow diagnostic procedure for the PID
that reads “FAULT”.
• For example, a B2296 fault is present. In
DataLogger the fault PID 2296_18_OD PID
reads “FAULT” indicating a front internal
crash sensor fault.

PAGE 2
Figure 1 - Article 07-12-3

PAGE 3
Figure 2 - Article 07-12-3

PAGE 4
Figure 3 - Article 07-12-3

PAGE 5
Figure 4 - Article 07-12-3

PAGE 6
Figure 5 - Article 07-12-3

PAGE 7