Obdsm1102 16
Obdsm1102 16
Obdsm1102 16
Misfire Monitor......................................................................................8
NVLD II Overview...................................................................................... 16
Temperatures Used................................................................................... 68
Ratio Calculation........................................................................................ 68
The Catalyst Efficiency Monitor uses an oxygen sensor after the catalyst to infer the hydrocarbon efficiency based on
oxygen storage capacity of the ceria and precious metals in the wash coat. Under normal, closed-loop fuel conditions,
high efficiency catalysts have significant oxygen storage. This makes the switching frequency of the rear HO2S very
slow and reduces the amplitude of those. As catalyst efficiency deteriorates due to thermal and/or chemical deterioration,
its ability to store oxygen declines and the post-catalyst HO2S signal begins to switch more rapidly with increasing
amplitude. The predominant failure mode for high mileage catalysts is chemical deterioration (phosphorus deposition on
the front brick of the catalyst), not thermal deterioration.
The Integrated Air/Fuel Catalyst Monitor assesses the oxygen storage capacity of a catalyst after a fuel cut event. The
monitor integrates how much excess fuel is needed to drive the monitored catalyst to a rich condition starting from an
oxygen-saturated, lean condition. Therefore, the monitor is a measure of how much fuel is required to force catalyst
breakthrough from lean to rich. To accomplish this, the monitor runs during fuel reactivation following a Decel Fuel Shut
Off (DFSO) event. The monitor completes after a calibrated number of DFSO monitoring events have occurred. The IAF
catalyst monitor can be used with either a wide range O2 sensor (UEGO) or a conventional switching sensor (HEGO).
The monitor runs during reactivation fueling following an injector cut. The diagram below shows examples of one DFSO
event with a threshold catalyst and with a Full Useful Life catalyst where:
2
CATMN_IAF_SUM
Fuel (lbm)
0.012
1.5 0.01
0.008
1
0.006
0.004
0.5
0.002
0 0
0 0.2 0.4 0.6 0.8 1 1.2 1.4 1.6 1.8 2
Tim e (sec)
2 LAM
CATMN_IAF_SUM 0.012
Fuel (lbm)
1.5 0.01
0.008
1
0.006
0.004
0.5
0.002
0 0
0 0.2 0.4 0.6 0.8 1 1.2 1.4 1.6 1.8 2
Tim e (sec)
In the example above, CATMN_IAF_SUM is much larger because it takes a substantial amount of fuel to break though a
high oxygen storage threshold catalyst.
There are two sets of entry conditions into the IAF catalyst monitor. The high level entry conditions determine that the
monitor would like to run following the next injector fuel cut event. The lower level entry conditions determine that the fuel
cut-off event was suitable for monitoring and the monitor will run as soon as the injectors come back on.
o The base monitor entry conditions have been met (ECT, IAT, cat temp, fuel level, air mass)
o The catalyst/rear O2 has been rich at least once since the last monitor event.
Rear HO2S sensors can be located in various ways to monitor different kinds of exhaust systems. In-line engines and
many V-engines are monitored by individual bank. A rear HO2S sensor is used along with the front, fuel-control HO2S
sensor for each bank. Two sensors are used on an in-line engine; four sensors are used on a V-engine. Some V-
engines have exhaust banks that combine into a single underbody catalyst. These systems are referred to as Y-pipe
systems. They use only one rear HO2S sensor along with the two front, fuel-control HO2S sensors. Y-pipe system
systems use three sensors in all. For Y-pipe systems which utilize switching front O2 sensors, the two front HO2S
sensor signals are combined by the software to infer what the HO2S signal would have been in front of the monitored
catalyst. The inferred front HO2S signal and the actual single, rear HO2S signal is then used to calculate the switch ratio.
Most vehicles monitor less than 100% of the catalyst volume often the first catalyst brick of the catalyst system. Partial
volume monitoring is done on LEV and LEV-II vehicles in order to meet the 1.75 * emission-standard threshold for
NMHC and NOx. The rationale for this practice is that the catalysts nearest the engine deteriorate first, allowing the
catalyst monitor to be more sensitive and illuminate the MIL properly at lower emission standards.
Many applications that utilize partial-volume monitoring place the rear HO2S sensor after the first light-off catalyst can or,
after the second catalyst can in a three-can per bank system. (A few applications placed the HO2S in the middle of the
catalyst can, between the first and second bricks.)
The Integrated A/F catalyst monitor was designed to allow monitoring 100% of the catalyst volume. It can be used for
both partial and full volume monitoring.
Vehicles with the Integrated Air/Fuel catalyst monitor employ an improved version of the EWMA algorithm.
The EWMA logic incorporates several important CARB requirements. These are:
Fast Initial Response (FIR): The first 4 tests after a code clear will process unfiltered data to quickly
indicate a fault. The FIR will use a 2-trip MIL. This will help the service technician determine that a
fault has been fixed.
Step-change Logic (SCL): The logic will detect an abrupt change from a no-fault condition to a fault
condition. The SCL will be active after the 4th catalyst monitor cycle and will also use a 2-trip MIL.
This will illuminate the MIL when a fault is instantaneously induced.
Normal EWMA (NORM): This is the normal mode of operation and uses an Exponentially
Weighted Moving Average (EWMA) to filter the catalyst monitor test data. It is employed after the
4th catalyst test and will illuminate a MIL during the drive cycle where the EWMA value exceeds the
fault threshold. (1 trip MIL).
The catalyst monitor results are converted to a ratio for Mode $06 reporting to keep the same look and feel for the
service technician. The equation for calculating the Mode $06 monitor result is:
Good catalyst reactivation fuel is intended to represent what the monitor would measure for a green catalyst.
** NOTE: In this document, a monitor or sensor is considered OK if there are no DTCs stored for that component or
system at the time the monitor is running.
The method used for engine misfire detection is based on evaluating the engine speed fluctuations; it is commonly
referred to as Engine Roughness. Engine torque is a function of engine speed, engine load, and the moment of inertia.
In order to detect a misfiring cylinder, the torque of each cylinder is evaluated by using the crankshaft position signal to
measure the time between sensor wheel teeth for each ignition event. This time is a measure of the mean value of the
speed of this angular segment. A change in engine torque also results in a change in engine speed. In addition, different
road surfaces, pot holes etc. will affect engine speed. Because mean engine speed is used to detect misfire, the effects
caused by road surfaces have to be eliminated. The misfire monitor consists of following main parts:
Data acquisition:
The duration of the crankshaft segment for each cylinder is measured continuously, every combustion cycle.
Crankshaft sensor wheel adaptation software is used to "learn" and correct for mechanical inaccuracies in the crankshaft
position wheel tooth spacing. To prevent any fueling or combustion differences from affecting the correction factors,
learning is done during decel-fuel cutout. When operating in decel-fuel cutout within a defined engine speed range,
misfire monitoring is suspended and adaptation of the sensor wheel tolerances takes place. The adaptation values are
stored in memory and used as correction factors for the calculation of the engine roughness.
The engine roughness is derived from the differences of the segment durations. Different statistical methods are used to
distinguish between normal changes of the segment duration and the changes due to misfiring.
Misfire Determination:
Misfire detection is performed by comparing the calculated engine roughness value for each cylinder to the engine
roughness threshold (a table value). If the threshold is exceeded, a misfire is detected and the counter is incremented.
This counter counts the number of misfires for all cylinders. In addition, a cylinder specific counter is also incremented.
The engine roughness threshold can be adjusted to account for the following factors to prevent false misfire indications:
If engine coolant temperature is very cold, the engine roughness threshold is adjusted by a coolant temperature
dependent factor.
If cold start emission reduction actions are active for improved catalyst warm-up (elevated idle speed, spark
retard, VVT timing, etc), the engine roughness threshold is adjusted by a catalyst warm-up dependent factor.
fIn the misfire monitoring strategy performs cylinder cut-off (turning off the fuel injector), the engine roughness
thresholds are generated by a separate table.
Rough road conditions can induce crankshaft speed changes via the drive train and result in false misfire
indications. When these conditions are detected, misfire detection is temporarily suspended for a calibratable
time period. After this time, with no rough road conditions present, misfire monitoring will resume.
The sum of the cylinder misfire counters is evaluated every 1000 rev period and compared to a single threshold value to
indicate an emission-threshold malfunction, which can be either a single 1000 rev exceedence from startup or four
subsequent 1000 rev exceedences on a drive cycle after start-up.
The cylinders with the highest misfire rate are flagged. If the misfire occurs again on a subsequent driving cycle, the MIL
is illuminated and a cylinder specific fault is stored.
The weighted sum of the cylinder misfire counters is evaluated every 200 revolution period and compared to a table of
threshold values to indicate a catalyst-damaging malfunction. The MIL is illuminated immediately. (The MIL blinks at a 1
Hz rate.)
The cylinders with the highest misfire rate are flagged. If one of the cylinder-specific counters is exceeding the catalyst
damage threshold the following actions take place:
4. The fuel injector to the misfiring cylinder is turned off (a maximum of one cylinder)
Similar Conditions
When the engine management system recognizes a failure in the misfire or fuel systems, the engine management
system is required to record the conditions present when the fault occurred. These conditions recorded include engine
speed, engine load (MAF), and warm up status of the first event that resulted in the storage of a code. These conditions
stored are referred to as similar conditions.
Once the similar conditions are meant without a failure in the misfire or fuel system, the flag is set to 1. Once this flag is
set the driving cycle counter for that failure can be decrement.
The code and stored freeze frame conditions may be erased if similar conditions are not encountered during the next 80
driving cycles immediately following the initial detection of the malfunction.
The MIL is extinguished after three consecutive cycles in which similar conditions have been encountered without
exceeding the fuel system diagnostic thresholds.
Start
No
Calculation:
ER_AV (Engine Roughness)
THD_ER_AV (Engine Roughness Threshold)
ER Value <
No
threshold
Yes
Monitoring Exception
Yes
Condition ?
No
No Misfire ?
Yes
Misfire Statistics
Fault Processing
This vehicle utilizes an engine off natural vacuum evaporative system integrity check that tests for 0.020" diameter leaks
while the engine is off and the ignition key is off. The Natural Vacuum Leak Detection II (NVLD II) evap system integrity
check uses a pressure switch to detect evap system leaks.
The correlation between pressure and temperature in a sealed system is used to generate a vacuum in the tank when
the temperature drops. If a sufficient temperature drop of 8C (14.5 F) is detected for a minimum time of 2 hours, the
vacuum level in the tank will exceed 0.04 psi and therefore close the NVLD II switch. If the switch closes the system is
considered to be leak free. Therefore, if the switch does not close within these conditions, a leak is detected.
The NVLD II evaporative system monitor consists of an NVLD II module, the Canister Purge Solenoid (CPS) and
software in the ECM that enables/disables the monitor, determines fault status and manages fault code storage, Mode
$06 data, Mode $09 data, etc.
The NVLD II monitor performs a small (0.020) leak check during engine off and a large leak check during engine
running. The NVLD II module incorporates a pressure switch and temperature sensor so the monitor also includes a
complete series of auxiliary checks to confirm the integrity of the mechanical and electrical components that make up the
entire evap monitoring system. The NVLD II module is powered after the ignition key is turned off so that the entire ECM
does not have to be powered to perform the engine-off small leak check. This saves a considerable amount of current
draw from the battery.
- 0.020 small leak detection enablement and fault decision (engine off)
- Large leak/fuel cap off detection enablement and fault decision (engine running)
The small leak (0.020 diameter) monitor evaluates the data collected from the NVLD II-module during the ignition key
off/engine off phase. After key off, a leak free evap system will generate a vacuum condition in the fuel tank as the fuel
cools down. If the pressure switch in the NVLD II module remains closed for a sufficient time (typically 10 minutes), the
monitor passes.
If a temperature drop of 8C was observed over at least 2 hours with no significant increase in fuel tank vacuum since
start of the ignition key off/engine off phase, (i.e. the pressure switch has not closed for the minimum time), a small leak
is detected. (P0456)
If the diagnostic entry conditions are not met, no diagnostic results are obtained (no call).
The overall evap monitor diagnostics are shown in the diagram below. The 0.020: dia leak monitor data is collected by
the NVLD II module during ignition off and evaluated by the ECM during engine-on. The NVLD-II module diagnostics are
performed during ignition on and ignition off.
NVLD II module diagnostic operation is divided into three operational modes, which are entered depending on external
conditions.
o Engine On mode: The NVLD II module receives and responds to a communication request from the ECM.
These requests are sent during engine run operation. On a key on event, a Wakeup-Request is sent to
establish communication between to NVLD II module and ECM.
o Diagnostic mode: At the end of a driving cycle (ECM powerlatch active), the NVLD II module receives a
Diagnosis-Request to go into "diagnostic mode" and perform engine-off switch and temperature monitoring for
very small leak detection.
o Off mode: When diagnostic mode is finished or conditions for very small leak detection are not met, the NVLD
II module receives a Sleep-Request and goes into "Off mode";
In diagnostic mode, after an initial delay time has elapsed, the temperature and switch position are checked every 10
minutes and two separate conditions for small leak detection are determined by checking if the calibrated temperature
difference between the actual temperature and the minimum temperature is met for at least 2 hours. If this occurs, a
corresponding condition flag is set.
I
The large leak monitor is divided into two paths depending on the NVLD II pressure switch position determined at the
start of the test. If the switch is already closed, the system is considered not to have a large leak, (as long as the NVLD II
switch is not stuck in the closed position). This is determined by opening the CPS during the power-latch phase (i.e.
engine stopped) to relieve the vacuum in the tank and force the switch to open. If the switch does not open within a
defined time, a mechanical switch error is detected. In order to know that the CPS valve will open and allow the vacuum
to be released, the CPS check is done after the switch is detected as closed.
If the switch is open at the start of the diagnostic test, the canister purge solenoid is opened with a defined maximum
flow through the CPS valve. As soon as a minimum flow is achieved, the switch position is monitored. If the switch
closes within a defined time, the system is considered not to have a large leak. Also the CPS valve must be functioning
properly and the NVLD II switch is not stuck in one position.
If the switch does not close, the proper functioning of the CPS valve is checked. Depending on the result of this check,
the detection of the large leak or CPS valve error is complete.
The canister purge valve plausibility checks ensure that the canister purge valve is able to be open to purge the canister.
If not an error canister purge valve stuck closed is reported.
The canister purge valve plausibility checks can be done in three ways:
- When NVLD II module switch closed during large leak test
- When Canister load higher than a threshold during a calibrated time
- With Canister purge valve control (intrusive test).
The canister purge valve control can act in via flow request or pwm request. The main difference between the two tests
is the following.
- With PWM control CPS check make intrusive test into the ECM functionality and the reaction expected when
the CPS valve opens, is engine parameter deviations.
- With FLOW control, CPS check we make non intrusive test into the ECM functionality and the reaction expected
when the CPS valve opens is no engine parameter deviations.
The canister purge valve control test can be done several times before an error is reported.
BARO 75 kPa
Time at Idle 4 seconds
Stable idle rpm 100 rpm
Stable idle torque 5 Nm
Vehicle speed 0.6 mph
Additional malfunctions that are to be identified as part of the evaporative system integrity check are as follows:
The Canister Purge Solenoid circuit is checked for opens and shorts (P0444, P0458, P0459)
Note that a CPS that is stuck closed will generate a P0455, and a CPS that is stuck open will generate a P0496.
The ECM receives the FLI signal via the CAN data link from the instrument cluster. The Fuel Level Input is checked for
out of range values, opens and shorts. If the FLI signal is stuck, a P0460 is set. The ECM calculates the amount of fuel
being consumed by accumulating fuel pulse width. If the there is an insufficient corresponding change in fuel tank level,
a P0460 DTC is set. Finally, the Fuel Level Input is checked for noisy readings. If the FLI input changes rapidly, a P0461
DTC is set.
The closed loop fuel strategy uses O2 sensors for feedback. The fuel equation includes short and long term fuel trim
modifiers:
A conventional O2 sensor (not a wide-range sensor) can only indicate if the mixture is richer or leaner than
stoichiometric. During closed loop operation, short term fuel trim values are calculated by the ECM using oxygen sensor
inputs in order to maintain a stoichiometric air/fuel ratio. The ECM is constantly making adjustments to the short term fuel
trim, which causes the oxygen sensor voltage to switch from rich to lean around the stoichiometric point. As long as the
short term fuel trim is able to cause the oxygen sensor voltage to switch, a stoichiometric air/fuel ratio is maintained.
When initially entering closed loop fuel, SHRTFT starts 1.0 and begins adding or subtracting fuel in order to make the
oxygen sensor switch from its current state. If the oxygen sensor signal sent to the ECM is greater than 0.45 volts, the
ECM considers the mixture rich and SHRTFT shortens the injector pulse width. When the cylinder fires using the new
injector pulse width, the exhaust contains more oxygen. Now when the exhaust passes the oxygen sensor, it causes the
voltage to switch below 0.45 volts, the ECM considers the mixture lean, and SHRTFT lengthens the injector pulse width.
This cycle continues as long as the fuel system is in closed loop operation.
O2 sensor voltage
As fuel, air, or engine components age or otherwise change over the life of the vehicle, the adaptive fuel strategy learns
deviations from stoichiometry while running in closed loop fuel. Corrections are only learned during closed loop
operation, and are stored in the ECM as long term fuel trim values (LONGFT). They may be stored into a rpm/load table.
LONGFT values are only learned when SHRTFT values cause the oxygen sensor to switch. If the average SHRTFT
value remains above or below stoichiometry, the ECM learns a new LONGFT value, which allows the SHRTFT value
to return to an average value near 1.0. LONGFT values are stored in Keep Alive Memory as a function of air mass. The
LONGFT value displayed on the scan tool is the value being used for the current operating condition.
As components continue to change beyond normal limits or if a malfunction occurs, the long-term fuel trim values will
reach a calibratable rich or lean limit where the adaptive fuel strategy is no longer allowed to compensate for additional
fuel system changes. Long term fuel trim corrections at their limits, in conjunction with a calibratable deviation in short
term fuel trim, indicate a rich or lean fuel system malfunction. To meet the PCV monitoring requirements, the fuel system
monitor is evaluated at idle to detect disconnection of the PCV intake manifold hose.
Note that Positive Crankcase Ventilation monitoring occurs at idle. A disconnected PCV hose will result in a lean
condition at idle that will be detected by the fuel monitor.
The diagram below shows the calibratable areas where fuel monitor learning takes place during closed loop fuel control.
Multiplicative/slope
learning areas
Similar Conditions
When the ECM recognizes a failure in the misfire or fuel systems, the software stores the conditions present when the
fault occurred. These conditions recorded include engine speed, engine load (MAF), and warm up status of the first
event that resulted in the storage of a DTC. These stored conditions are referred to as similar conditions. If the similar
conditions are met without a failure in the misfire or fuel system, a flag is set to 1 which allows the driving cycle counter
for that failure to decrement. Any misfire or fuel system DTCs are erased if similar conditions are not encountered during
the next 80 driving cycles immediately following the initial detection of the malfunction. The MIL is extinguished after
three consecutive driving cycles in which similar conditions have been encountered without exceeding the misfire or fuel
system diagnostic thresholds.
Yes Yes
Set the failure symptom and Set the failure symptom and
Increment the concerned time Increment the concerned time
counter counter
Yes Yes
End
Error detection in additive or
low multiplicative adaptation
learning area
Yes Yes
Set the failure symptom and Set the failure symptom and
Increment the concerned time Increment the concerned time
counter counter
Yes Yes
End
Error detection in case of
lambda control - dead stop
The upstream oxygen sensor circuit monitor detects if the HO2S sensor voltage is above or below a calibratable
threshold or if it is not active, (lack of switching) or stuck at the bias voltage.
The upstream oxygen sensor monitor detects if the HO2S signal circuit voltage is:
Open circuit causing the signal circuit voltage to be inactive or stuck at the bias voltage.
This additional check is performed because there are two different possible root causes for this symptom at engine start.
The upstream signal voltage can be inactive (stuck at the bias voltage) because of an open circuit, or because of a weak
HO2S heater. These cases are described below:
An open circuit power integral starts and activates the open circuit diagnosis to check if a real open circuit is present or if
the P016A was set because of a weak O2 sensor heater.
If the power integral exceed its limit, the signal is checked again. If the signal voltage is still stuck at the bias voltage and
the internal resistance is above a calibrated limit, a P0130 is stored for an open circuit.
The open circuit power integral starts and the signal is checked again. The power integral is calibrated based on low
activity of the signal voltage with a weak heater. After the power integral exceeds its limit, and the upstream voltage is
outside the open circuit limits, if no real open circuit present, the P0053 for the heater rationality upstream is stored.
Start
No
Monitoring conditions
fulfilled?
Yes
Yes
Error counter
>= threshold ?
Yes
Fault processing
Start
NO
NO
increment OC power integral
Power Integral
35000 j
NO
YES
Power Integral
>35000 j
OC check
YES
NO
OC OC check
Error
NO
YES Heater rationality
OC
Error Up-stream (fast path)
P0130 error directly stored
YES
A fuel control routine drives the air/fuel ratio around stoichiometry at a calibratable frequency and magnitude. This
produces a predictable oxygen sensor signal amplitude and duration used to evaluate the response time and frequency
response of the sensor.
At each cycle, the lean and the rich duration are measured and accumulated separately. After a calibrated number of
cycles are exceeded, the accumulated lean and rich durations and periods are compared to the expected durations and
periods.
Actual rich to lean switch time is compared to expected rich to lean switch time (as a function of MAF)
Actual lean to rich switch time is compared to expected lean to rich switch time (as a function of MAF)
Actual rich to lean switch period is compared to expected rich to lean switch period (as a function of MAF & RPM)
Actual lean to rich switch period is compared to expected lean to rich switch period (as a function of MAF & RPM)
For proper function of the oxygen sensor, the sensor element must be heated. A non functioning heater delays the
sensor readiness for closed loop control and thus influences emissions. The signal for the O2 sensor heater is pulse-
width modulated. The oxygen sensor heater circuit monitor detects the following malfunctions by evaluating the error
information received from the heater power driver in the ECM: heater short circuit to battery, short circuit to ground, and
open circuit.
Heater Performance
This monitor determines the rationality of the upstream(or downstream) O2 sensor heater fault if the measured upstream
(or downstream) O2 sensor resistance is lower than the predetermined threshold after a number of monitoring cycles
have been carried out. Note: If the rationality test stores an error (P0053) then an additional P-code is stored
automatically (P016A).
Start
No
Monitoring conditions
fulfilled?
Yes
Short cut
or
broken line
No
detected by the
No
hardware?
Yes
Error counter
>= threshold ?
Yes
Fault processing
The downstream oxygen sensor circuit monitor detects the HO2S sensor voltage is above or below a calibratable
threshold or if it is not active, stuck at some voltage.
The downstream oxygen sensor monitor detects if the HO2S signal circuit voltage is shorted to ground (low signal),
signal circuit voltage is high (high signal), or an open circuit causing the signal circuit voltage to be inactive or stuck at
some voltage.
Sensor signal plausibility and signal activity monitoring is performed during coasting conditions during fuel cut-off
(Slow Response). A malfunction is also detected, if the sensor signal is permanently above the minimum
threshold.
Star t
No
Moni toring Condi tions?
Yes
No
Er ror Cou nter > = Threshold ?
Y es
O2 S ens or
Sensor Connection M alfunction
- Signal Line Short to B attery V oltage
- Signal Line Short to G round
- Signal Line Break
This non intrusive diagnosis can detect the sluggish behavior of the rich/lean switch times during the transition to decel
fuel cut-off. The malfunction thresholds are a function of MAF and signal band limits.
Monitoring function:
After the enable conditions are met and DFCO is determined to be active, the current downstream O2 voltage is
monitored and stored. If the stored value is above a calibratable threshold, and MAF is within a calibratable window, the
test is started.
Once the sensor voltage drops a calibratable percentage of the stored value, a timer is started. This timer is then
stopped when the voltage drops a calibratable percentage of that stored value. At this point the test is determined to be
valid and the diagnostic counter is incremented by one.
The switching time value is then converted to a weighted value. This process is repeated for a calibratable number of
DFCO events. Each time the diagnostic counter is incremented the weighted value is added to a total value. At the end
of the maximum number of DFCO events, the total value is divided by the number of DFCO events and another value is
developed. This value is then compared to a threshold. If the value exceeds the threshold the sensor is determine to be
slow and the corresponding fault code is stored.
Start
Monitoring
Conditions
No
Fuel Cut-Off Phase
Yes
Yes No
Downstream O2 Volts
> .3 < .5 Volts
No
Error Time > 100 ms
Yes
Fault
Processing
For proper function of the oxygen sensor, the sensor element must be heated. A non functioning heater delays the
sensor readiness for closed loop control and thus influences emissions. The signal for the O2 sensor heater is pulse-
width modulated. The oxygen sensor heater circuit monitor detects the following malfunctions by evaluating the error
information received from the heater power driver in the ECM: heater short circuit to battery, short circuit to ground, and
open circuit.
Heater Performance
The monitoring strategy is based on the comparison of the O2 sensor heater resistance to an absolute threshold during
deceleration conditions where the exhaust temperature is sufficiently low as to cause the sensor ceramic temperature to
fall outside normal operating levels in cases where the heating power is insufficient.
The cooling energy of the exhaust gas is calculated and compared to a calibrated threshold. The heater monitor is active
if the calculated energy is equal or exceeds the threshold. Then the O2 sensor heater is compared to a calibrated
threshold. If the heater resistance is equal or exceeds the threshold, an O2 sensor heater malfunction is detected.
The rear bias control (also called FAOSC Fore/Aft Oxygen Sensor Control) system is designed to compensate for any
bias shifts (offsets) using the downstream HO2S sensor. This can occur due to a shift in the upstream oxygen sensor, or
an exhaust system leak between the pre and post O2 sensors. The "FAOS" monitor looks for any bias shifts at the
stoichiometric point of the front sensor lambda curve. If the front sensor has developed a bias beyond the point for which
it can be compensated for, lean (P2096) or rich (P2097) fault codes will be set.
Start
No
Calculate
I-share of fuel trim control
Monitoring conditions
fulfilled?
Yes
No Start Timer
No
I-share < min. threshold
or
I-share > max. threshold?
Yes
Error counter
increment
Error counter
>= threshold ?
Yes
Fault processing
The coolant thermostat monitor is designed to detect a thermostat that is slow to open or is stuck open. It is based on the
comparison of the measured Engine Coolant Temperature (ECT) sensor signal and the calculated ECT model. The ECT
model calculation is depending on engine load/speed and the intake air temperature.
A malfunctioning coolant thermostat is detected if the calculated ECT model has exceeded the thermostat opening
temperature and the measured ECT sensor signal remains below a threshold (the highest diagnostic enable
temperature).
To prevent false DTCs, conditions for low load, long deceleration duration and Intake Air Temperature (IAT) during the
monitoring period are checked. If the monitoring conditions are met, the thermostat DTC is set; otherwise the thermostat
monitor is suspended for the current driving cycle.
A comparison between the measured coolant temperature and the warmed-up temperature is done after a specific
time interval. The interval itself is based on the coolant temperature model.
As soon as the model temperature exceeds the thermostat opening temperature and all other monitoring conditions are
fulfilled at the same time, a valid diagnosis occurs.
At that time, if the measured coolant temperature is higher than warmed-up temperature, the thermostat is considered to
be a normal thermostat. If the measured coolant temperature is lower than warmed-up temperature, the thermostat is
considered to be stuck open.
START
Continuous calculation of
Coolant Temperature
Model TCO_SUB
Monitoring conditions at
start
Yes
No ECT-sensor signal
> threshold 1
No No
TCO_SUB Yes
model value
> threshold 1
Yes
Monitoring
Diagnosis disabled for this
No conditions at end of
DC
monitoring
Yes
ECT-sensor signal
Yes Thermostat OK
> threshold 2
No
Thermostat faulty
Fault Processing
The Cold Start Emission Reduction (CSER) Component Monitor works by validating the operation of the components of
the system required to achieve the cold start emission reduction strategy, namely retarded spark timing and elevated idle
airflow.
When the CSER strategy is enabled, the idle air control system will request a higher idle rpm, elevating engine airflow.
When the CSER strategy is enabled, the idle air control system will request a retarded spark timing, increasing engine
airflow.
If the VCT cam phasing is used during a cold start to improved catalyst heating, the VCT system is checked functionally
by monitoring the closed loop cam position error correction. If the proper cam position cannot be maintained and the
system has an advance or retard error greater than the malfunction threshold, a cold start emission reduction (CSER)
VCT control malfunction is indicated (P052B (Bank 1).
Integrated difference between camshaft actual position and camshaft setpoint 100 deg crank
The Cold Start Emission Reduction System Monitor was introduced for the 2007 MY on vehicles that meet the LEV-II
emission standards. It replaces the Cold Start Emission Reduction Component Monitor. The Cold Start Emission
Reduction (CSER) Monitor detects the lack of catalyst warm up resulting from a failure to apply sufficient CSER during a
cold start. It does this by using the inferred catalyst temperature model to determine how closely the actual catalyst
temperature follows the expected catalyst temperature during a cold start. How closely the actual temperature follows
the expected temperature is reflected in a ratio which is compared with a calibratable threshold.
Temperatures Used
The actual catalyst temperature is the same inferred catalyst temperature that is used by other portions of the engine
control system, including the CSER control system. The inputs to this actual temperature are measured engine speed,
measured air mass, and commanded spark.
The expected catalyst temperature is calculated using the same algorithm as the actual catalyst temperature, but the
inputs are different. Desired engine speed replaces measured engine speed, desired air mass replaces measured air
mass, and desired cold start spark replaces commanded spark. The resulting temperature represents the catalyst
temperature that is expected if CSER is functioning properly.
Ratio Calculation
A ratio is calculated to reflect how closely the actual temperature has followed the expected temperature. This ratio is
the difference between the two temperatures at a certain time-since-start divided by the increase in expected
temperature over the same time period. The ratio, then, provides a measure of how much loss of catalyst heating
occurred over that time period.
This ratio correlates to tailpipe emissions. Therefore applying a threshold to it allows illumination of the MIL at the
appropriate emissions level. The threshold is a function of ECT at engine start.
During the first 15 seconds of a cold start, the monitor checks the entry conditions, counts time in idle, and observes
catalyst temperature.
If the expected change in catalyst temperature is large enough, the monitor calculates the ratio as described above.
Otherwise the monitor does not make a call.
The monitor then begins the waiting period, which lasts from the time the ratio is calculated (15 seconds after engine
start) until 300 seconds after engine start. This 5-minute wait allows time to diagnose other components and systems
that affect the validity of the catalyst temperature model. During this waiting period, there are no constraints on drive
cycle and the monitor cannot be disabled without turning off the key.
At the end of the waiting period, if no other faults that could compromise the validity the catalyst temperature model are
found, the monitor compares the ratio to the threshold.
If the ratio exceeds the threshold, the monitor considers the test a fail, and the monitor is complete.
If the ratio falls below the threshold, the monitor determines whether the idle time was sufficient. If so, it considers the
test a pass and the monitor is complete. If idle time was not sufficient, the monitor does not make a call and does not
complete. This prevents tip-ins from resulting in false passes.
Variable Valve / Cam Timing (VVT/VCT) enables rotation of the camshaft(s) relative to the crankshaft (phase-shifting) as
a function of engine operating conditions. With Dual Equal VCT, both intake and exhaust camshafts are retarded from
the default, fully advanced position to increase EGR residual and improve fuel economy by reducing intake vacuum
pumping losses. The residual charge for NOx control is obtained by backflow through the late-closing exhaust valve as
the piston begins its intake stroke.
The VCT system hardware consists of a control solenoid and a pulse ring on the camshaft. The ECM calculates relative
cam position using the CMP input to process variable reluctance sensor pulses coming from the pulse ring mounted on
the camshaft. Each pulse wheel has N + 1 teeth where N = the number of cylinders per bank.
The ECM continually calculates a cam position error value based on the difference between the desired and actual
position and uses this information to calculate a commanded duty cycle for the VVCT solenoid valve. When energized,
engine oil is allowed to flow to the VCT unit thereby advancing and retarding cam timing.
The difference between the actual cam position and the target cam position is checked. The target position has to be in a
limited stable range for a certain time. If the actual position is near the target (calibratable range) the diagnosis is ok,
otherwise not. This will be checked by calculating two integrals (reset integral and failure integral). Both integral values
have the same thresholds
If the failure integral reaches this threshold at first, an anti-bounce counter is started; otherwise the counter will be
decremented. If the counter exceeds an adjustable limit, the appropriate DTC will be stored.
Fade
away Reset integral = Failure integral =
allowed deviation * dt deviation * dt Failure
dt OK dt
Time
Setpoint stable Allowed Setpoint stable Allowed
deviation deviation
Diagnostic condition 1 1
0 0
Start
NO
All monitoring
conditions true?
YES
NO Setpoint nearly
stable in a small
range?
YES
CAM position
inside the allowed
deviation range?
YES
NO
Failure integral Reset integral
calculated calculated
NO YES NO YES
Threshold Threshold
reached? reached?
NO Counter
exceeds lim.?
YES
Fault
processing
The response of the actual position on a target position change, which has to be big and quick enough, is evaluated. The
set point and camshaft position are saved at the beginning of a set point change. If this change over a time is big enough
(gradient), the camshaft phasing change is evaluated. If the change after the diagnostic time is smaller than a threshold,
a slow response is detected, and if the value is greater, then there is no malfunction. By detecting a malfunction, an anti-
bounce counter is incremented otherwise the counter will be decremented. If the counter exceeds an adjustable limit, the
appropriate DTC will be stored.
Example 1:
Setpoint
Window
size =
In dyn. function
window of eng.
speed
Out of
dyn.
window
Time Const. time interval
Example 2:
Set-point
Cam. position
Setpoint
~stable
Min. Min.
cam. setpoi
Diagno
Start
NO
All monitoring
conditions true?
YES
Setpoint stable
for certain time?
NO
YES
NO Setpoint change
big enouhg?
YES
NO
Anti bounce Anti bounce counter
counter increment decrement
NO Counter
exceeds lim.?
YES
Fault
processing
This diagnostic monitors whether the mean camshaft signal is within a plausible range during the reference position
adaptation. The reference position adaptation is enabled if the target camshaft position is the reference one. This occurs
after every engine start or during engine operation depending on the engine operating state.
A mean camshaft position is calculated from several camshaft signals. If the mean camshaft position is outside the
hysteresis area, an incorrect camshaft reference position is detected. If this position is within the hysteresis, area, then
there is no malfunction. After detecting a malfunction, an anti-bounce counter is incremented; otherwise the counter is
decremented. If the counter exceeds an calibrated threshold, the appropriate DTC will be stored.
Example 1:
Example
Adjust.
INLET
range Wrong
Failure camshaft
reference
Hys. ADC Hys. RTD
position
Valve
lift
TDC CRK
Example 2:
Ref. Adaptation
Out of range
Mean camshaft position
Wrong camshaft
Theoretical camshaft position reference position
recognised
Allowed hysteresis ADC/RTD
Start
NO
All monitoring
conditions true?
YES
Ref. adaptation
finished?
NO
YES
NO
Anti bounce Anti bounce counter
counter increment decrement
NO Counter
exceeds lim.?
YES
Fault
processing
The Electronic Throttle Control (ETC) system uses a strategy that delivers engine or output shaft torque, based on
driver demand, utilizing an electronically controlled throttle body. ETC strategy was developed mainly to improve fuel
economy. This is possible by decoupling throttle angle (produces engine torque) from pedal position (driver demand).
This allows the powertrain control strategy to optimize fuel control and transmission shift schedules while delivering the
requested engine or wheel torque.
No Effect on Drivability A loss of redundancy or loss of a non-critical input could result in a fault that does
not affect drivability. The ETC light will turn on, but the throttle control and torque
control systems will function normally.
RPM Guard w/ Pedal In this mode, torque control is disabled due to the loss of a critical sensor or ECM
Follower fault. The throttle is controlled in pedal-follower mode as a function of the pedal
position sensor input only. A maximum allowed RPM is determined based on pedal
position (RPM Guard.) If the actual RPM exceeds this limit, spark and fuel are used
to bring the RPM below the limit. The ETC light and the MIL are turned on in this
mode and the corresponding trouble code will be stored.
RPM Guard w/ Default In this mode, the throttle plate control is disabled due to the loss of Throttle Position,
Throttle the Throttle Plate Position Controller, or other major Electronic Throttle Body fault.
A default command is sent to the TPPC, or the H-bridge is disabled. Depending on
the fault detected, the throttle plate is controlled or springs to the default (limp
home) position. A maximum allowed RPM is determined based on pedal position
(RPM Guard.) If the actual RPM exceeds this limit, spark and fuel are used to bring
the RPM below the limit. The ETC light and the MIL are turned on in this mode and
the corresponding trouble code will be stored.
RPM Guard w/ Forced This mode is caused by the loss of 2 or 3 pedal position sensor inputs due to
High Idle sensor, wiring, or ECM faults. The system is unable to determine driver demand,
and the throttle is controlled to a fixed high idle airflow. There is no response to the
driver input. The maximum allowed RPM is a fixed value (RPM Guard.) If the actual
RPM exceeds this limit, spark and fuel are used to bring the RPM below the limit.
The ETC light and the MIL are turned on in this mode and the corresponding
trouble code will be stored.
Shutdown If a significant processor fault is detected, the monitor will force vehicle shutdown by
disabling all fuel injectors. The ETC light and the MIL are turned on in this mode
and the corresponding trouble code will be stored.
Note: Vehicle shutdown does not increase emissions; therefore the MIL is not
required to be illuminated for this fault.
Ignition ON
Adaptation Necessary
Start Routine Adaptation Routine
No Yes
Yes No
Spring Test-Upper Position Stop
Check- OK
No
Yes Yes
Engine Started
No
No Spring Test-Upper Position
Stop Check- OK
Yes
No
Spring Test-Upper Position Stop 2nd check for Limp Home =
Check- OK OK
Yes
No 2nd check for Limp Home = OK
Yes
No
Yes Engine Started
No
No
Yes Yes
nd
2 check for Limp Home =
OK
Adaptation of Lower Position
No Stop Check- OK
Yes
Yes
No
No
Yes
The ETC Motor Control Circuit diagnostics are able to detect a short circuit to power, a short circuit to ground and an
open circuit. The diagnostic is initialized after a module reset or a Key ON. After initialization (Key "ON"), the following
are all reset: The diagnostic conditions, the symptom, the counter, and the failure stored in the Error Management.
The circuit diagnostics execute every 10 milliseconds and are continuous. A short circuit can only be detected when the
H-bridge switches are open, so the condition for the each short circuit is calculated during all ranges of the PWM.
The ETC motor control circuit diagnostic is activated between a battery voltage range. This is to eliminate false low limit
voltage detection. The deactivation threshold for the ETC motor control circuit diagnostic is typically calibrated to a low
voltage.
This diagnostic checks if the throttle spring is working correctly and if the throttle limp home position can be achieved.
The diagnostic is performed at the beginning of every driving cycle at ignition "Key ON" position. The throttle body spring
check is executed as part of the start routine and is carried out with every Key ON of the engine control unit. More
specifically the spring check is run during the TPS adaptation routine. The routine includes the following:
Limp-home position check
Adaptation of the limp-home position
Upper return spring check
The start routine is only carried out when the adaptation conditions are maintained, (Key "ON" / Engine Running). The
diagnostic will report when a spring-check error occurs, which includes the upper or lower return spring limits.
There is a throttle position set-point, calibratable, used for the upper return spring check. The TPS set-point should be
approximately 10 greater than the limp-home position.
After the adaptation of the lower mechanical stop, the set point is used for the lower return spring check. The objective is
to adjust the throttle in a position between the lower limit and limp-home. Without this set point, the throttle could stick in
the lower mechanical stop after the adaptation. A typical value of 2 is recommended.
After the initial engine start and / or component change, the characteristic Potentiometer values for the limp home
position and the lower mechanical stop are learned within an adaptation routine. The values are stored at the end of the
driving cycle in the non-volatile memory. If the conditions are not fulfilled, the malfunction errors (DTC's) are stored.
Due to the electrical and mechanical tolerances of the ETC system, the sensor characteristic has to be learned and the
ETC system controller must adapt. The TPS adaptation is executed as part of the start routine and is carried out the very
first time there is a Key ON of the engine control unit at the vehicle assembly plant or when the engine control unit is
changed in service.
Due to the electrical and the mechanical tolerances of the throttle position system, the sensor characteristic has to be
learned. The adaptation and diagnosis of the lower mechanical stop and limp-home position occurs within the adaptation
routines. The adapted lower mechanical stop and the upper check position are used for the calculation of TPS channel
1. The upper mechanical stop is not learned. During the TPS adaptation no limitation of the throttle position set-point is
active. The learned value for the limp-home position, the lower mechanical stop and the TPS channel1 values are stored
at the end of each driving cycle as non-volatile.
The first step is the adaptation of the limp-home position. The actuator is without current and is forced by spring power to
the limp home position. During the adaptation all the voltage values must be in the adaptation windows. A hysteresis is
set up around each of the first recorded values (TPS 1 and 2). If all the TPS values are with in this hysteresis during a
calibrated time, then the adaptation values are determined from the first and last value for each TPS. If a TPS value is
outside the hysteresis, then the process is started over for both TPS channels. The learning function is limited by a
calibratable time. An adaptation error is detected if the adaptation could not be carried out during the maximum time.
The next step is the adaptation of the lower mechanical stop. The throttle is driven into the lower mechanical stop by
switching on the position controller and gradually decreasing the set point. As soon as the mechanical stop is reached,
the adaptation of the lower mechanical stop for all TPS input channels is started. The adaptation procedure is the same
as the limp-home position except the calibration values are different. As with the limp-home position, if the maximum
adaptation time is exceeded, an adaptation error is indicated.
Now the lower return spring is checked. The throttle is positioned between lower mechanical stop and limp-home by
switching on the position controller and increasing the set point gradually until a calibrated set point for testing the lower
return spring is reached. An adaptation error is indicated if the throttle does not reach the requested position in a defined
time limit. Then the ETC power stage is switched off and the throttle has to return by spring power to the limp-home
position or a return spring error is indicated.
Next is the adaptation of the amplification from the TPS measuring amplifier (TPS 1 channel). The controller is switched
on and the set point is gradually increased and the throttle is moved to a position above limp-home until the calibrated
set point for the adaptation of the measuring amplifier is reached. An adaptation error is indicated if the throttle does not
reach the requested position in a defined time limit.
The final step is the check of the upper return spring. The throttle is gradually driven further away from limp home
position until a calibrated set point for the upper spring check is reached. An adaptation error will be indicated if the
throttle does not reach the requested position in a defined time limit. The ETC power stage is switched-off and the
throttle has to return by spring power to the limp-home position, or an upper return spring error is indicated.
If all of the adaptations and checks pass, the learned value for the limp-home position, the lower mechanical stop and
the TPS channel 1 values are stored at the end of each driving cycle in non-volatile memory. This provides the initial
control settings for the next Key ON.
The task of this diagnostic is to detect a throttle valve error or a jammed ETC actuator. The diagnosis observes the ETC
position controller system deviation dependent on the gradient of the throttle position setpoint. The anti-bounce of the
error detection is done by the generic error management. The increment and decrement value of the anti-bounce
counters can be calibrated.
Additionally the PWM output of the digital position controller is monitored by this diagnosis function. If the moving mean
value exceeds a defined diagnosis threshold than an error will be indicated.
The diagnostic first observes the TPS sensor signal difference relative to the throttle position set point. If the difference is
determined to be greater than a calibrated value, a control error is indicated. If the control system is unable to reach a
set point within a calibrated time after multiple attempts, a jammed ETC actuator is indicated. In very low temperatures it
is possible that the throttle actuator may become jammed by ice. If this is detected, an attempt to remove the ice will be
made by varying the controller set point. The throttle position set point is varied by a rectangle function (Note: During
active icebreaking engine speed limitation is requested!). If the ice-breaking is not successful after a defined number of
pulses, the throttle position set point will be limited in lower or upper direction depending on the detected ice location. If
the actual throttle position exceeds a defined threshold during limitation in the closed-throttle direction, then an additional
error entry will be made with fault reaction of ETC power stage switch-off and engine speed limitation.
A second part of the diagnostic is to check the PWM output of the ETC systems position controller. If the moving-mean
value of the PWM output exceeds a calibrated diagnostic threshold, then an error will be indicated.
Note: For all the above DTCs, in addition to the MIL, the ETC light will be on for
the fault that caused the FMEM action.
Sensors OK
Analog inputs such as Intake Air Temperature (P0112, P0113), Engine Coolant Temperature (P0117, P0118), Mass Air
Flow (P0102, P0103), and Throttle Position (P0122, P0123) P0222, P0223) are checked for opens, shorts, or rationality
by monitoring the analog -to-digital (A/D) input voltage.
The IAT rationality test determines if the IAT sensor is producing an erroneous temperature indication within the normal
range of IAT sensor input.
Typical Intake Air Temperature Sensor Cold Start Plausibility Entry Conditions
Entry condition Minimum Maximum
Engine off time 6.7 h
Abs | Engine Coolant Temperature at start minus Intake Air Temp at start | 18 C
Block heater not present
engine run time 240 s
Actual Air Flow - Modeled Airflow for part throttle test > 18 to 25% AND lambda correction <-22.5% OR
Actual Air Flow - Modeled Airflow for part throttle test < 18 to -25% AND lambda correction > -22.5%
The MAF and TP sensors are cross-checked to determine whether the sensor readings are rational and appropriate for
the current operating conditions. (P0068)
The engine off timer function is obtained via a CAN message from the instrument panel cluster. There are multiple parts
to the diagnosis of the engine off timer.
The first is performed by the instrument panel cluster. If the engine off time is invalid, the CAN message is set to
FFFFh. This is trigger a fault unless the battery has been recently disconnected.
The next diagnosis checks the availability of engine off time from CAN before engine start. Once detected, this
failure can only be reset by a key off to on transition or ECU reset.
The final diagnostic verifies that the engine off timer itself is plausible as compared to a global timer.
The Idle Speed Control system is functionally checked by monitoring the closed loop idle speed correction required to
maintain the desired idle rpm. If the proper idle rpm cannot be maintained and the system has a high rpm (+100) or low
rpm error (-200) greater than the malfunction threshold, an Idle Speed malfunction is indicated. (P0506, P0507) If an idle
speed deviation occurs during cold start, a P050A will be stored as part of the cold start monitoring strategy.
Two basic diagnostic tests are performed on each knock sensor circuit continuity tests and a knock processing chip
tests.
Due to the design of the knock sensor input circuitry, after filtering and integration, a short to battery, short to
ground, or open circuit all result is a low knock signal voltage. This voltage is compared to a noise signal
threshold (function of rpm) to determine knock sensor circuit high and circuit low faults.
Another indication of a sensor failure is the standard deviation of the signal noise which decreases when there is
a failure. The knock signal standard deviation is compared to a threshold (function of rpm).
The knock signal processing chip SPI bus is checked to make sure it is not off. This would indicate there is no
communication between the main processor and the chip used as the interface the knock sensor.
The purpose of the diagnosis shall be to detect electrical faults as defined by OBD I requirements.
The signal of the altitude pressure sensor on the A/D-input of the microcontroller is checked.
The purpose of this diagnosis function is to detect all major failures, which can happen between the ECU output
and ignition coils.
The diagnosis is performed separate for each ignition coil. The feedback signal from the specific ignition coil
(following the firing order) is evaluated by the microcontroller.
Ignition Coil:
DTCs P0351 Ignition Coil A Primary Control Circuit Open
P2301 Ignition Coil A Primary Control Circuit High
P0352 Ignition Coil B Primary Control Circuit Open
P2304 Ignition Coil B Primary Control Circuit High
Monitor execution Continuous within entry conditions
Monitor Sequence None
Sensors OK Oposite Coil errors
Monitoring Duration 50 ms
A P0340/P0365 malfunction is indicated if no signal edge is detected for a calibratable time between two expected
camshaft signal edges. A P0341/P0366 malfunction is indicated if the camshaft position is outside of the calibrated range
specified for the engine. A P0344/P0369 malfunction is detected if a tooth segment period is too short.
A P0335 malfunction is indicated if there is no crankshaft signal detected. A P0336 malfunction is indicated if a camshaft
signal is present (engine is spinning) but a crankshaft signal is not present, or the number of teeth detected is incorrect,
or if the time between teeth is implausible.
DPS6 is a fully automatic 6 speed transmission made up of manual transmission gearing, combined with electro-
mechanical actuators, and conventional automatic transmission controls.
Twin Clutch
Actuators with
E-motors
Shift drums
with E-
motors
Twin Dry
Clutches
Clutch
3 phase electric motor rotates a screw driven fulcrum that controls clutch position (and torque). There
are end stops at the full open and full closed positions
Each motor phase has a hall position sensor that combine to provide a relative position the system
must sweep the clutch full open to full closed, then count increments on the sensors to know position. It
takes many rotations of the motor to sweep the clutch from fully open to fully closed.
Spring that returns the clutch to the full open position if the motor is turned off.
1. Shift Drum A controls the shift forks that engage 1st, 3rd and 5th gear
2. Shift Drum B controls the shift forks that engage Reverse, 2nd, 4th and 6th gear
Shift drum with groove that controls the position of shift forks
3 phase electric motor that controls the position of the shift drum
Hall sensor system that knows the position of the motor within a rotation, used to calculate the shift
drum angular position (the shift drum motor rotates 61.44 times for a single revolution of the shift drum)
55 deg Neutral between 1st and 3rd Neutral between R and 2nd
135 deg Neutral between 3rd and 5th Neutral between 2nd and 4th
DPS6 is range by wire with mechanical Park. DPS6 uses a dual PWM output (at 250 Hz) TRS where one signal is the
inverse of the other and the sum of the two signals add up to 100%. Each signal is tested for frequency errors (P0706 /
P2801), duty cycle out of range low (P0707 / P2802) and duty cycle out of range high (P0708 / P2803). There is also a
correlation error (P2805) if the two signals do not add up to 100%.
Speed Sensors
Input 1 Speed Sensor (I1SS) detects input shaft 1 speed, connected to clutch 1 and the odd gears (1st, 3rd and 5th).
I1SS is tested for power supply faults (P06A6), circuit failures detected by the TCM hardware (P0715), erratic signal
(P0716), and lack of signal (P0717).
Input 2 Speed Sensor (I2SS) detects input shaft 2 speed, connected to clutch 2 and the even gears (R, 2nd, 4th and
6th). I2SS is tested for power supply faults (P06A7), circuit failures detected by the TCM hardware (P2765), erratic signal
(P2766), and lack of signal (P2767).
Output Speed Sensor (OSS) detects output speed. OSS is tested for power supply faults (P06A8), circuit failures
detected by the TCM hardware (P0720), erratic signal (P0721), and lack of signal (P0722).
Note: because DPS6 is "Dry clutch" the only transmission fluid is for splash lube (no pump, no pressure control
solenoids), so DPS6 does not have a temperature sensor.
Transmission Outputs
2. Clutch B motor controls clutch B torque capacity. The Clutch B system is tested for:
a. ATIC faults (P087A) the ATIC is an internal TCM component that controls motor current.
b. Hall sensor faults (P087B) each phase has a hall sensor that provides motor position information
c. Sequence faults (P087E) as the motor rotates it generates an defined pattern from the 3 hall sensors,
if the sequence of hall sensor patterns is off this code sets.
d. Open circuit (P090A)
e. Short to ground (P090C)
f. Short to power (P090D)
g. Clutch functionally stuck off (P07A4)
h. Clutch functionally stuck on (P07A5)
4. Shift drum A motor controls the shift forks that engage 1st, 3rd and 5th gear. The system is tested for:
a. ATIC faults (P2836) the ATIC is an internal TCM component that controls motor current.
b. Sequence faults (P283A) as the motor rotates it generates an defined pattern from the 3 hall sensors,
if the sequence of hall sensor patterns is off this code sets.
c. Open circuit (P285F)
d. Short to ground (P2861)
e. Short to power (P2862)
f. Stuck in gear (P072B, P072D, P072F, P073B)
g. Position error (P2837) includes blocked motor, or any failure that results in the TCM losing confidence
in the relative position of the shift drum.
The TCM monitors itself by using various software monitoring functions. The TCM is monitored for:
a. If a RAM Read/Write error is detected during initialization, a P0604 fault code will be stored
b. the flash ROM is checked using a checksum calculation. If the checksum is incorrect during a P0605 fault
will be stored
c. CPU performance is monitored for incorrect instructions or resets, if detected a P0607 fault code is set
The TCM receives information from the ECM via CAN. If the CAN link fails the TCM no longer has torque or engine
speed information available. The TCM will store a U0073 fault code if the CAN Bus is off. The TCM will store a U0100
fault code if it doesnt receive any more CAN messages from the ECM. A U0401 fault codes will be stored if the ECM
received invalid/faulted information for the following CAN message items: engine torque, pedal position.
System voltage:
the TCM monitors system voltage and stores fault codes if it is out of range low (P0882) or out of range high (P0883).
These thresholds are set based on hardware capability.
The On-Board Diagnostic (OBD) Executive is a portion of the PCM strategy that manages the diagnostic trouble codes
and operating modes for all diagnostic tests. It is the "traffic cop" of the diagnostic system. The Diagnostic Executive
performs the following functions:
Sequence the OBD monitors such that when a test runs, each input that it relies upon has already been
tested. For 2008 MY and beyond ISO 14229 programs, the OBD monitors are no longer sequenced by the
diagnostic executive.
Controls and co-ordinates the execution of the individual OBD system monitors: Catalyst, Misfire, EGR, O2,
Fuel, AIR, EVAP and, Comprehensive Component Monitor (CCM). For 2008 MY and beyond ISO 14229
programs, the execution of the OBD monitors is no longer controlled and coordinated by the diagnostic
executive.
Stores freeze frame and "similar condition" data.
Manages storage and erasure of Diagnostic Trouble Codes as well as MIL illumination.
Controls and co-ordinates the execution of the On-Demand tests: Key On Engine Off (KOEO) Key On Engine
Running (KOER).
Performs transitions between various states of the diagnostic and powertrain control system to minimize the
effects on vehicle operation.
Interfaces with the diagnostic test tools to provide diagnostic information (I/M readiness, various J1979 test
modes) and responses to special diagnostic requests (J1979 Mode 08 and 09).
Tracks and manages indication of the driving cycle which includes the time between two key on events that
include an engine start and key off.
The diagnostic executive also controls several overall, global OBD entry conditions.
The battery voltage must fall between 11.0 and 18.0 volts to initiate monitoring cycles.
The engine must be started to initiate the engine started, engine running, and engine off monitoring cycles.
The Diagnostic Executive suspends OBD monitoring when battery voltage falls below 11.0 volts.
The Diagnostic Executive suspends monitoring of fuel-system related monitors (catalyst, misfire, evap, O2,
AIR and fuel system) when fuel level falls below 15%. For 2005 MY and beyond, the execution of the fuel
related OBD monitors is no longer suspended for fuel level by the diagnostic executive.
The diagnostic executive controls the setting and clearing of pending and confirmed DTCs.
A pending DTC and freeze frame data is stored after a fault is confirmed on the first monitoring cycle. If the
fault recurs on the next driving cycle, a confirmed DTC is stored, freeze frame data is updated, and the MIL
is illuminated. If confirmed fault free on the next driving cycle, the pending DTC and freeze frame data is
erased on the next power-up.
Pending DTCs will be displayed as long as the fault is present. Note that OBD-II regulations required a
complete fault-free monitoring cycle to occur before erasing a pending DTC. In practice, this means that a
pending DTC is erased on the next power-up after a fault-free monitoring cycle.
After a confirmed DTC is stored and the MIL has been illuminated, three consecutive confirmed fault-free
monitoring cycles must occur before the MIL can be extinguished on the next (fourth) power-up. After 40
engine warm-ups, the DTC and freeze frame data is erased.
A permanent DTC is stored when a confirmed DTC is stored, the MIL has been illuminated, and there are
not yet six permanent DTCs stored.
After a permanent DTC is stored, three consecutive confirmed fault-free monitoring cycles must occur
before the permanent DTC can be erased.
After a permanent DTC is stored, one confirmed fault-free monitoring cycle must occur, following a DTC
reset request, before the permanent DTC can be erased. For 2010MY and beyond ISO 14229 programs a
driving cycle including the following criteria must also occur, following the DTC reset request, before a
permanent DTC can be erased:
o Cumulative time since engine start is greater than or equal to 600 seconds;
o Cumulative vehicle operation at or above 25 miles per hour occurs for greater than or equal to
300 seconds (medium-duty vehicles with diesel engines certified on an engine dynamometer may
use cumulative operation at or above 15% calculated load in lieu of at or above 25 miles per hour
for purposes of this criteria); and
o Continuous vehicle operation at idle (i.e., accelerator pedal released by driver and vehicle speed less
than or equal to one mile per hour) for greater than or equal to 30 seconds.
A permanent DTC can not be erased by a battery disconnect. Additionally, its confirmed DTC counterpart
will be restored after completion of the system reset (battery reconnect).
Exponentially Weighted Moving Averaging is a well-documented statistical data processing technique that is used to
reduce the variability on an incoming stream of data. Use of EWMA does not affect the mean of the data; however, it
does affect the distribution of the data. Use of EWMA serves to filter out data points that exhibit excessive and
unusual variability and could otherwise erroneously light the MIL.
New Average = [New data point * filter constant] + [( 1 - filter constant ) * Old Average]
This equation produces an exponential response to a step-change in the input data. The "Filter Constant" determines
the time constant of the response. A large filter constant (i.e. 0.90) means that 90% of the new data point is averaged in
with 10% of the old average. This produces a very fast response to a step change. Conversely, a small filter constant
(i.e. 0.10) means that only 10% of the new data point is averaged in with 90% of the old average. This produces a
slower response to a step change.
When EWMA is applied to a monitor, the new data point is the result from the latest monitor evaluation. A new average
is calculated each time the monitor is evaluated and stored in Non Volatile Memory (NVRAM). This normally occurs
each driving cycle. The MIL is illuminated and a DTC is stored based on the New Average store in NVRAM.
In order to facilitate repair verification and DDV demonstration, 2 different filter constants are used. A fast filter
constant is used after DTCs are erased and a normal filter constant is used for normal customer driving. The fast
filter is used for 2 driving cycles after DTCs are erased, and then the normal filter is used. The fast filter allows for
easy repair verification and monitor demonstration in 2 driving cycles, while the normal filter is used to allow up to 6
driving cycles, on average, to properly identify a malfunction and illuminate the MIL. This feature is called Fast Initial
Response (FIR). The fast filter is always calibrated to 1.0 which means that the EWMA is effectively disabled because
the new average is 100% of the new data point. Since the EWMA is effectively disabled, it takes twp driving cycles to
set the MIL. The first driving cycle with a fault will set a pending DTC; the second driving cycle will set a confirmed code
and illuminate the MIL.
The other unique feature used with EWMA is called Step Change Logic (SCL). This logic detects an abrupt change
from a no-fault condition to a fault condition. This is done by comparing the new data point to the EWMA old average. If
the two points differ by more than a calibrated amount (i.e. the new data point is outside the normal distribution), it
means that a catastrophic failure has occurred. The fast filter is then used in the same manner as for the FIR feature
above. Since the EWMA is effectively disabled, it takes twp driving cycles to set the MIL. The first driving cycle with a
fault will set a pending DTC; the second driving cycle will set a confirmed code and illuminate the MIL. The SCL
becomes active after the 4th "normal" monitoring cycle to give the EWMA a chance to stabilize.
During "normal" EWMA operation, a slower filter constant is used. The "normal filer" allows the MIL to be illuminated in
1 to 6 driving cycles. A confirmed code is set and the MIL is illuminated as soon as the EWMA crosses the malfunction
threshold. There is no pending DTC because EWMA uses a 1-trip MIL.
In order to relate filter constants to driving cycles for MIL illumination, filter constants must be converted to time
constants. The mathematical relationship is described below:
The evaluation period is a driving cycle. The time constant is the time it takes to achieve 68% of a step-change to an
input. Two time constants achieve 95% of a step change input.
EWMA with FIR and SCL has been incorporated in the IAF catalyst monitor. There are 3 parameters that determine the
MIL illumination characteristics.
Fast filter constant (0.9999), used for 2 driving cycles after DTCs are cleared (FIR) and for Step Change Logic (SCL)
Normal filter constant( typically 0.4), used for all subsequent, normal customer driving
Number of driving cycles to use fast filter after DTC clear (set to 2 driving cycles)
Several examples for a typical catalyst monitor calibration are shown in the tables below. The first example does not
show SCL in order to better illustrate the EWMA calculation and the 1-trip MIL.
The readiness function is implemented based on the J1979 format. A battery disconnection or clearing codes using a
scan tool results in the various I/M readiness bits being set to a not-ready condition. As each non-continuous monitor
completes a full diagnostic check, the I/M readiness bit associated with that monitor is set to a ready condition. This
may take one or two driving cycles based on whether malfunctions are detected or not. The readiness bits for
comprehensive component monitoring, misfire and fuel system monitoring are immediately considered complete since
they are continuous monitors.
The OBD-II diagnostic communication messages utilize an industry standard 500 kbps CAN communication link.
The instrument cluster on some vehicles uses the same CAN data link to receive and display various types of
information from the ECM. For example, the engine coolant temperature information displayed on the instrument cluster
comes from the same ECT sensor used by the ECM for all its internal calculations.
These same vehicles use the CAN data link to illuminate the MIL rather than a circuit, hard-wired to the ECM. The ECM
periodically sends the instrument cluster a message that tells it to turn on the MIL, turn off the MIL or blink the MIL. If the
instrument cluster fails to receive a message within a 5-second timeout period, the instrument cluster itself illuminates the
MIL. If communication is restored, the instrument cluster turns off the MIL after 5 seconds. Due to its limited capabilities,
the instrument cluster does not generate or store Diagnostic Trouble Codes.
Closed loop fuel control is enabled (with a delay) at the start of a driving cycle and can be temporary inhibited (open
loop) during the driving cycle. The turn-on delay at the start of a driving cycle is described by the following enable
conditions:
the upstream oxygen sensor is functional, i.e. the upstream HO2S operating temperature has been reached
a calibrated delay time, after end of engine start, has elapsed
the engine coolant temperature (if used) must have exceeded a calibrated threshold or the modeled engine
coolant temperature (substitute for a faulty temperature sensor minimum) must have exceeded a calibrated
threshold after a calibrated period of time
Closed loop fuel operation is also inhibited during a driving cycle when any of the following conditions exist:
During fuel cut-off or cylinder shut-off
When catalyst over temperature protection is active.
Full load enrichment active.
When Catalyst purge is active.
Closed loop lambda control is inhibited during a driving cycle if any of the following errors exist:
a catalyst damaging misfire rate
Upstream HO2S sensor malfunction present
current airflow
(peak airflow at WOT@STP as a function of rpm) * (BARO/29.92) * SQRT(298/(AAT+273))