1
11/13/2020
AT 17701 – Engine& Vehicle
Management System
SESSION 42
2
11/13/2020
Unit V – Fault Diagnosis
System
SESSION 11
3
Recap of session 41
• Monitors and readiness flags
• Misfire detection
11/13/2020
4
OBD summary
OBD monitoring applies to systems which are most likely to cause an increase in harmful
exhaust emission, namely
all main engine sensors;
fuel system;
ignition system;
EGR system.
11/13/2020
5
OBD2
The main features of OBD2 are, therefore, as follows:
malfunction of emission relevant components to be detected when emission threshold
values are exceeded;
storage of failures and boundary conditions in the vehicle’s fault memory;
diagnostic light (MIL) to be activated in case of failures;
readout of failures with generic scan tool.
11/13/2020
6
OBD2
increased power of micro controllers - number of important developments could be added with
the introduction of OBD2 - catalyst efficiency monitoring, misfire detection, canister purge and
EGR flow rate monitoring - additional benefit was the standardisation of diagnostic equipment
interfaces.
Another feature of OBD2 is that the prescribed thresholds at which a fault is deemed to have
occurred are in relation to regulated emission limits.
The basic monitor function is as follows:
monitoring of catalyst efficiency, engine misfire and oxygen sensors function such that crossing
a threshold of 1.5 times the emission limit will record a fault;
monitoring of the evaporation control system such that a leak greater than the equivalent leak
from a 0.04 inch hole will record a fault.
11/13/2020
7
The main features of an OBD2 compliant system (as compared to OBD1) are as follows :
pre- and post-catalyst oxygen sensors to monitor conversion efficiency;
much more powerful ECU with 32 bit processor;
ECU map data held on EEPROMs such that they can be accessed and manipulated via an
external link; no need to remove ECU from vehicle for software updates or tuning;
more sophisticated EVAP system, can detect minute losses of fuel vapour;
EGR systems with feedback of position/flow rate;
sequential fuel injection with MAP and MAF sensing for engine load.
11/13/2020
OBD2 system showing the main components of a gasoline direct injection system 8
11/13/2020
MIL activation logic for detected malfunctions
To avoid wrong detections, the legislation allows verification of the detected failure.
The failure is stored in the fault memory as a pending code immediately after the first recognition but the
9
MIL is not activated.
The MIL will be illuminated in the third driving cycle, in which the failure has been detected; the failure
is then recognised as a confirmed fault.
MIL healing
The MIL may be deactivated after three subsequent sequential driving cycles during which the monitoring
system responsible for activating the MIL ceases to detect the malfunction, and if no other malfunction
has been identified that would independently activate the MIL.
Healing of the fault memory
The OBD system may erase a fault code, distance travelled and freeze frame information if the same fault
is not re-registered in at least 40 engine warm-up cycles.
11/13/2020
Freeze frame
This is a feature that can assist in the diagnosis of intermittent faults.
10
Upon determination of the first malfunction of any component or system, ‘freeze frame’
engine conditions present at the time must be stored in the computer memory.
Stored engine conditions must include, but are not limited to,
calculated/derived load value;
engine speed;
fuel trim values (if available);
fuel pressure (if available);
vehicle speed (if available);
coolant temperature;
intake manifold pressure (if available);
closed or open-loop operation (if available);
the fault code which caused the data to be stored.
11/13/2020
11
End of session 42
11/13/2020
