Description
Following procedures are functional tests of EEC-V system. These basic test steps must be followed in sequence to avoid misdiagnosis.
- Visual Check
- Equipment Hookup
- KOEO (Key On Engine Off) SELF-TEST
- KOER (Key On Engine Running) SELF-TEST
- Computed Timing Check
- Continuous Memory Self-Test
GENERIC OBD-II PARAMETER IDENTIFICATION (PID)
Turn ignition switch to OFF position. Ensure test equipment is properly attached. Program scan tester using the following steps
- Select vehicle and engine selection menu (optional). see scheme 3
- Select year, engine, model and any additional information requested by scan tester (optional).
- Select GENERIC OBD-II OPTIONS. Press CONT button if monitors are not complete.
- Select PID/DATA MONITOR.
- Turn ignition on or start engine and allow to idle.
- Follow operating instructions from scan tester menu.
- Select PIDs and press START.
NON-GENERIC OBD-II PARAMETER IDENTIFICATION (PID)
Turn ignition switch to OFF position. Ensure test equipment is properly attached. Program scan tester using the following steps
- Select vehicle and engine selection menu. see scheme 3
- Select year, engine, model and any additional information requested by scan tester.
- Select GENERIC OBD-II OPTIONS. Press CONT button if monitors are not complete.
- Select DIAGNOSTIC DATA LINK.
- Select PCM - POWERTRAIN CTRL MODULE.
- Select DIAGNOSTIC TEST MODES.
- Select PID DATA MONITOR AND RECORD.
- Turn ignition on or start engine and allow to idle.
- Follow operating instructions from scan tester menu.
- Select PIDs and press START.
HARDWARE LIMITED OPERATIONAL STRATEGY (HLOS)
If a number of system or sensor failures are present and PCM is not receiving enough information to operate, PCM will switch to HLOS mode. PCM will output fixed values to allow operation of vehicle. Driveability concerns will be present. PCM will not output diagnostic trouble codes in this mode.
OBD-II OVERVIEW & SENSOR ILLUSTRATION DESCRIPTION
The California Air Resources Board (ARB) began regulation of On Board Diagnostic (OBD) systems for vehicles sold in California beginning with the 1988 model year. The first phase, OBD I, required monitoring of the fuel metering system, Exhaust Gas Recirculation (EGR) system, and additional emission-related components. The Malfunction Indicator Lamp (MIL) was required to light and alert the driver of the malfunction and the need for service of the emission control system. The MIL must be labeled CHECK ENGINE or SERVICE ENGINE SOON. A fault code or Diagnostic Trouble Code (DTC) is associated with the MIL identifying the specific area of the fault.
The OBD system was proposed by the California ARB to improve air quality by identifying vehicles exceeding emission standards. Passage of the federal Clean Air Act Amendments in 1990 has also prompted the Environmental Protection Agency (EPA) to develop on board diagnostic requirements. California ARB OBD-II regulations will be followed until 1999 when the federal regulations will be used.
The OBD-II system meets government regulations by monitoring the emission control system. When a system or component exceeds emission thresholds or a component operates outside of tolerance, a DTC will be stored and the MIL will be turned on.
The OBD-II monitors detect system faults and initiate DTC setting and MIL activation. Fault detection strategy and MIL operation are associated with drive cycles. See OBD-II DRIVE CYCLE . A DTC is stored in the PCM keep alive random access memory when a fault is first detected. In most cases the MIL is turned on after two consecutive drive cycles with the fault existing.
The DTC is cleared after 40 engine warm-up cycles without the fault being detected once the MIL is turned off. Once a monitor turns on the MIL, it will require 3 consecutive drive cycles without a fault for the MIL to turn off. The operation of each of the OBD-II monitors is discussed in detail within this section.
The on board diagnostic computer program in the electronic Engine Control (EC) system Powertrain Control Module (PCM) coordinates the OBD-II self-monitoring system. This program controls all the monitors and interactions, DTC and MIL operation, freeze frame data and scan tool interface. OBD-II Inspection Maintenance (IM) readiness DTC P1000 indicates that not all of the OBD-II monitors have been completed since the PCM's keep alive random access memory was last cleared. In certain states, it may be necessary to operate the vehicle until DTC P1000 is erased from the PCM in order to purchase a vehicle license.
Freeze frame data describes stored engine conditions such as state of the engine, state of fuel control, spark, rpm, load, and warm-up status at the point the first fault is detected. Previously stored conditions will be replaced only if a fuel or misfire fault is detected. This data is accessible with the scan tool to assist in repairing the vehicle.
This section provides a general description of each OBD-II monitor. In these descriptions, the monitor strategy, hardware, testing requirements and methods are presented together to provide an overall understanding of each monitor operation. An illustration for each monitor is also provided to aid in the description. Refer to illustration (Scheme 1) These illustrations should be used as typical examples and are not intended to represent all the possible configurations.
Each illustration depicts the Powertrain Control Module (PCM) as the main focus with the primary inputs and outputs for each monitor. The icons to the left of the PCM represent the inputs (for icon identification, refer to illustration. (Scheme 2)) used by each of the monitor strategies to enable or activate the monitor. The components and subsystems to the right of the PCM represent the hardware and signals used while performing the tests and the systems being tested. see scheme 6 The catalyst efficiency monitor illustration has numerous components and signals involved and is shown generically. When referring to the illustrations, match the numbers to the corresponding numbers in the monitor descriptions for a better comprehension of the monitor and associated Diagnostic Trouble Codes (DTCs). These monitor descriptions are intended as general information only. See DRIVE CYCLES for detailed testing instructions for each monitor. These icons are used in the illustrations of the OBD-II monitors and throughout this section.
Scheme 1
Scheme 2
The purpose of the OBD-II drive cycle is to execute the OBD-II monitors and identify any concerns with the OBD-II system. The DTC P1000 code will be erased of all OBD-II monitors have completed during the OBD-II drive cycle. The scan tool will be used to observe the status of each OBD-II monitor at the completion of the OBD-II drive cycle. The completion status of the Exhaust Gas Recirculation (EGR), Heated Oxygen Sensor (HO2S), Evaporative Emission (EVAP), Secondary Air Injection (AIR) (if applicable) and catalyst efficiency monitors can be monitored during the OBD-II drive cycle by viewing the ON-BOARD READINESS menu on the scan tool. For the procedure of each OBD-II drive cycle, see MONITOR REPAIR VERIFICATION DRIVE CYCLES under DRIVE CYCLES.