Complete manual download BMW 528i 1998 E39 Manual PDF

Downloaded from www.Manualslib.com manuals search engine
OBD-3
On-Board
~iactnosticsl
Additional MIL information:
A fault code is stored within the ECM upon the first
occurrence of a fault in the system being checlted.
Two complete consecutive drive cycles with the iault
present illuminate the MIL. The exception to the two-fault
requirement is a catalyst-damaging fault, which illuminates
the MIL immediately.
If the second drive cycle was not complete and the fault
was not checked, the ECM counts the third drive cycle as
the next consecutive drive cycle. The MIL illuminates
if the
system is checked and the fault is still present.
Once the MIL is illuminated, it remains illuminated until the
vehicle completes three consecutive drive cycles without
detecting a fault.
0 An existing fault code is cleared from memory
automatically when the vehicle completes
40 consecutive
drive cycles without the fault being detected.
In order to automatically clear a catalyst-damaging fault from
memory, the condition underwhich the fault occurred must be
evaluated for 80 consecutive drive cycles without the fault
reoccurring.
A generic scan tool connected to the BMW data link
connector (DLC) or OBD
I1 plug can display diagnostic trouble
codes (DTCs), along with the conditions associated with the
illumination of the MIL. Using a more advanced or
BMW-
dedicated scan tool, additional proprietary information is
normally available.
Scan tool and scan tool display
The complexity of the OBD I1 system requires that all
diagnostics begin by connecting a scan tool to the vehicle.
Aftermarltet scan tools can be connected to either the 16-pin
OBD
I1 plug or the 20-pin BMW DLC in the engine
compartment
(ii installed). Data from the OBD II plug may be
limited, depending on scan tool and vehicle.
OBD
I1 standards reouire that the 16-oin OBD I1 oluo be
located within three
(3) feet of the driier and not're&ire any
tools to access.
Starting with June 2000 production, the 20-pin BMW DLC,
previously located in the engine compartment, was
discontinued. Diagnostic, coding and programming functions
are incorporated into the OBD
II plug, located under left side
of dashboard.
On cars built up to 06
/ 2000: when accessing emissions
related DTCs through the 16-pin OBD
I1 plug, malte sure the
BMW 20-oin DLC
caD is installed.

Downloaded from www.Manualslib.com manuals search engine
- -
On-Board Diagnostics
Professional diagnostic scan tools available atthe time of this
printing include the BMW factory tools
(DISplus, GTI,
MoDiC) and a small number of aftermarket BMW-specific
tools. See
020 Maintenance.
In addition to the professional line of scan tools, inexpensive
generic OBD
II scan tool software programs and handheld
units are readily available. Though limited, they are
nonetheless powerful diagnostic tools. These tools read live
data streams and freeze frame data as well as a host of other
valuable diagnostic data.
Diagnostic monitors
Diagnostic monitors run tests and checks on specific
emission control systems, components, and functions.
A complete drive cycle is requiredforthe tests to bevalid. See
Drive cycle in this repair group. The diagnostic monitor
signals the
ECM of the loss or impairment of the signal or
component and determines if a signal or sensor is faulty
based on
3 conditions:
* Signal or component shorted to ground
Signal or component shorted to
B+
Signal or component missing (open circuit)
The OBD
II system monitors all emission control systems that
are installed. Emission control systems vary by vehicle model
and year. For example, a vehicle may not be equipped with
secondary air injection, so no secondary air readiness code
would be present.
OBD
II software monitors the following:
Oxygen sensors
Catalysts
Engine misfire
- Fuel tank evaporative control system
Secondary air injection Fuel system
Oxygen sensor monitoring. When driving conditions allow,
response rate and switching time of each oxygen sensor is
monitored. The oxygen sensor heater function is also
monitored. The OBD
II system differentiates between
precataylst and post-catalyst oxygen sensors and reads each
one individually. In order
forthe oxygen sensor to be
effectively monitored, the system must be in closed loop
operation.

Downloaded from www.Manualslib.com manuals search engine
OBD-6
On-Board Diagnostics
Fuel system monitoring. This monitor looks at the fuel
delivery needed (long
/short term fuel trim) for proper engine
operation based on programmed data. If too much or not
enough fuel is delivered over a predetermined time, a DTC is
set and the MIL illuminates.
Fuel trim refers to adiustments to base fuel schedule.
Lono- ., term fuel trim refers to gradual adjustments to the fuel
calibration adjustment as compared to short term fuel trim.
Long term fuel trim adjustments compensate for gradual
changes that occur over time.
Fuel system monitoring monitors the calculated injection time
(ti) in relation to enginespeed, load and precatalyticconverter
oxygen
sensor(s) signals.
Using this data, the system optimizes fuel delivery for all
engine operating conditions.
Evaporative system monitoring. This monitor checks the
the fuel storage system and related fuel lines for leaks. It can
detect very small leaks anywhere in the system.
A leak detection unit (LDP or DMTL) is used to pressurize the
evaporative control system on a continuous basis (as the
drive cycle allows) and to
check system integrity.
Drive cycle
The OED II drive cycle is an important concept in
understanding OBD
II requirements. The purpose of the drive
cycle is to run ail of the emission-related on-board diagnostics
over a broad range of driving conditions.
A drive cycle is considered complete when all of the
diagnostic monitors have run their tests without interruption.
~ora drive cycle to be initiated, the vehicle must be started
cold and brought up to
1 60°F and at least 40°F above its
original starting temperature.
Readiness codes
Inspection/maintenance (I/M) readiness codes are mandated
as part of OBD
II. The readiness code is stored aftercomplete
diagnostic monitoring of specified components and systems
is carried out. The readiness code function was designed to
prevent manipulating an
I/M emission test procedure by
clearing faults codes or disconnecting the ECM or battery.

Downloaded from www.Manualslib.com manuals search engine
On-Board Diagnostics
Readiness codes indicate whether the OED Ii system is
actually ready to monitor the various emission control
systems on the vehicle. The vehicle must complete a drive
cycle to set readiness codes. The code is binary:
0 for ready
1 for not ready
f
4 The parameters which are monitored for readiness are:
llM readiness codes
1. Catalyst efficiency
2. Catalyst heating
3. Fuel tank evaporative control
4. Secondary air injection
5.
NC refrigerant
6. Oxygen sensors
7. Oxygen sensor heaters
8. Exhaust gas recirculation
Readiness codes are set to 1 (not ready) in the following
cases:
~9~~.f~[<+t~t~p:,~;:#j~~{]~y~ ,,... , , 8701Dbd001
The battery or ECM is disconnected.
When
all zeros are displayed, the system has established
DTCs are erased after completion of repairs and a drive
cycle is not completed.
readiness. Readiness codes
can be displayed using BMW
and aftermarket scan tools.
An
OED II scan tool can be used to determine IIM readiness.
Diagnostic trouble codes (DTCs)
SAE standard J2012 mandates a 5-digit diagnostic trouble
code (DTC) standard. Each digit represents a specific value.
Emission related DTCs
start with the letter P for power train.
When the engine service
light (MIL) is illuminated it indicates
that a DTC has been stored.
DTCs are stored as soon as they occur, whether or not the
engine service light illuminates.
DTCs store and display a time stamp.
DTCs record the current fault status: Present, not currently
present, or intermittent.