Functional Operation
SYSTEM DESCRIPTION AND FUNCTIONAL OPERATIONGENERAL DESCRIPTION
The on-board OBDII/EUROIII diagnostics incorporated with the PCM controller are intended to assist the field technician in repairing vehicle problems by the quickest means.
FUNCTION OPERATION
Fuel Control (gas)
The PCM controls the air/fuel ratio of the engine by varying fuel injector on time. Mass air flow is calculated by the speed density method using engine speed and manifold absolute pressure (IAT is a modifier in Speed Density).
Different fuel calculation strategies are used depending on the operational state of the engine. During crank mode, a prime shot fuel pulse is delivered followed by fuel pulses determined by a crank time strategy. Cold engine operation is determined via an open loop strategy until the O2 sensors have reached operating temperature. At this point, the strategy enters a closed loop mode where fuel requirements are based upon the state of the O2 sensors, engine speed, MAP, throttle position, air temperature, battery voltage, and coolant temperature.
On-board Diagnostics
The PCM has been programmed to monitor any circuit or system that has an effect on vehicle emissions, or is used by the PCM to determine the proper functionality of these systems. This monitoring is called "on-board diagnosis."
Certain criteria or, "arming conditions", must be met for a trouble code to be entered into the PCM memory. The criteria may be a range of: engine rpm, engine temperature, and/or input voltage to the PCM. If a problem is detected with a monitored circuit, and all of the criteria or arming conditions are met, a trouble code will be stored in the PCM.
It is possible that a trouble code for a monitored circuit may not be entered into the PCM memory even though a malfunction has occurred. This may happen because one of the trouble code criteria (arming conditions) has not been met.
The PCM compares input signal voltages from each input device with specifications (the established high and low limits of the range) that are preprogrammed for that device. If the input voltage is not within specifications and other trouble code criteria (arming conditions) are met, a trouble code will be stored in the PCM memory.
The On Board Diagnostics have evolved to the second Generation of Diagnostics referred to as OBDII/EUROIII. These OBDII/EUROIII Diagnostics control the functions necessary to meet the requirements of California OBDII/EUROIII and Federal OBD regulations. These requirements specify the inclusion of a Malfunction Indicator Light (MIL) located on the instrument panel for all 1994 and subsequent model-year passenger cars, light duty trucks, and medium-duty vehicles. The purpose of the MIL is to inform the vehicle operator in the event of the malfunction of any emission systems and components which can affect emissions and which provide input to, or receive output from, the PCM.
OBDII/EUROIII Monitor Operation:
The following table summarizes the various OBDII monitors operation.
Transmission Control
The automatic transmission used on this vehicle is a 30RH model, non electronic controlled. Connections to the PCM are limited to the Torque Converter Clutch, Park Neutral Switch, and Vehicle Speed Sensor.
Torque Converter Electronics
The torque converter contains a converter clutch mechanism. The converter clutch is an electronically controlled mechanism that engages in 3rd gear. The PCM grounds the TCC Solenoid Control circuit to lock up the torque converter. The torque converter is not a serviceable component. It should be replaced as an assembly when: diagnosis indicates a malfunction has occurred, or when a major malfunction allows debris to enter the converter.
Other Controls
Charging System
The charging system is turned ON when the engine is started and ASD relay energized. When the ASD relay is ON, ASD output voltage is supplied to the ASD sense circuit at the PCM. This voltage is connected in some cases, through the PCM and supplied to one of the generator field terminals (Generator Source +). All others, the Generator field is connected directly to the ASD output voltage. The amount of current produced by the generator is controlled by the Electronic Voltage Regulator (EVR) circuitry, in the PCM. Battery temperature is determined either by IAT, Ambient or Battery temperature sensor. This temperature along with sensed line voltage is used by the PCM to vary battery charging. This is accomplished by cycling the path to ground to the other generator field terminal (Generator field driver).
Speed Control
The PCM controls vehicle speed by operation of the speed control servo vacuum and vent solenoids. Energizing the vacuum solenoid applies vacuum to the servo to increase throttle position. Operation of the vent solenoid slowly releases the vacuum allowing throttle position to decrease. A special dump solenoid allows immediate release of throttle position caused by braking, cruise control turn OFF; shifting into neutral, excessive RPM (tires spinning) or ignition key OFF.
Fuel Vapor Recovery System (duty Cycle Purge Control) Gas Engine
Duty Cycle Purge is a system that feeds fuel gases from the purge canister and gasoline tank into the throttle body for mixing with incoming air. Metering of the gases is performed by duty cycling the purge solenoid by the PCM.
The system is disabled during wide-open throttle conditions and while the engine is below a specified coolant temperature. When engine temperature becomes greater than a calibrated parameter, duty cycle purge is delayed for a calibrated time. Once purge delay is over, purge will be ramped in to soften the effect of dumping additional fuel into the engine.
The PCM provides a modulated 5 Hz signal (at closed throttle) or 10 Hz signal (at open throttle) to control this system. Modulation of the signal is based upon a calculated air flow (based upon known fuel flow through the injector at a given pulse width and RPM) and is adjusted to compensate for changes in flow due to varying engine vacuum.
Non-monitored Circuits
The PCM does not monitor the following circuits, systems, and conditions even though they could have malfunctions that result in driveability problems. A diagnostic code may not be displayed for the following conditions. However, problems with these systems may cause a diagnostic code to be displayed for other systems. For example, a fuel pressure problem will not register a diagnostic code directly, but could cause a rich or lean condition. This could cause an oxygen sensor, fuel system, or misfire monitor trouble code to be stored in the PCM.
- Engine Timing - The PCM cannot detect an incorrectly indexed timing chain, camshaft sprocket, or crankshaft sprocket. The PCM also cannot detect an incorrectly indexed distributor or Cam Sensor.(*)
- Fuel Pressure - Fuel pressure is controlled by the fuel pressure regulator. The PCM cannot detect a clogged fuel pump inlet filter, clogged in-line filter, or a pinched fuel supply.(*)
- Fuel Injectors - The PCM cannot detect a clogged fuel injector, a sticking pintle, or that an incorrect injector is installed.(*)
- Fuel Requirements - Poor quality gasoline can cause problems such as hard starting, stalling, and stumble. Use of methanol-gasoline blends may result in starting and driveability problems. (See individual symptoms and their definitions in Glossary of Terms).
- PCM Grounds - The PCM cannot detect a poor system ground. However, a diagnostic trouble code may be stored in the PCM as a result of this condition.
- Throttle Body Air Flow - The PCM cannot detect a clogged or restricted air cleaner inlet or filter element.(*)
- Exhaust System - The PCM cannot detect a plugged, restricted, or leaking exhaust system.(*)
- Cylinder Compression - The PCM cannot detect uneven, low, or high engine cylinder compression.(*)
- Excessive Oil Consumption - Although the PCM monitors the exhaust oxygen content through the oxygen sensor when the system is in a closed loop, it cannot determine excessive oil consumption.
NOTE: Any of these conditions could result in a rich or lean condition causing an oxygen sensor trouble code to be stored in the PCM, or the vehicle may exhibit one or more of the driveability symptoms listed in the Table of Contents.
SKIS Overview
The Sentry Key Immobilizer System (SKIS) is an immobilizer system designed to prevent unauthorized vehicle operation. The system consists of Sentry Key Immobilizer Module (SKIM) sends a PCI Bus message to the engine controller indicating ignition key status. Upon receiving this message the PCM will terminate engine operation or allow the engine to continue to operate.
SKIM On-board Diagnostics
The SKIM has been programmed to transmit and monitor many different coded messages as well as PCI Bus messages. This monitoring is called "On- Board Diagnosis".
Certain criteria must be met for a diagnostic trouble code to be entered into the SKIM memory. The criteria may be a range of Input voltage, PCI Bus message, or coded messages to the SKIM. If all of the criteria for monitoring a circuit or function are met and a fault is sensed, a diagnostic trouble code will be stored in the SKIM memory.
SKIS Operation
When ignition power is supplied to the SKIM, the SKIM performs an internal self-test. After the self-test is completed, the SKIM energizes the antenna (this activates the transponder chip) and sends a challenge to the transponder chip. The transponder chip responds to the challenge by generating an encrypted response message using the following:
- Secret Key - This is an electronically stored value (identification number) that is unique to each SKIS. The secret key is stored in the SKIM, PCM, and all ignition key transponders.
- Challenge - This is a random number that is generated by the SKIM at each ignition key cycle. The secret key and challenge are the two variables used in the algorithm that produces the crypto algorithm to receive, decode and respond to the message sent by the SKIM. After responding to the coded message, the transponder sends a transponder ID message to the SKIM. The SKIM compares the transponder ID to the available valid ignition key codes in the SKIM memory (8 key maximum:). After validating the key, the SKIM sends a PCI Bus message called a "Seed Request" to the engine controller then waits for a PCM response. If the PCM does not respond, the SKIM will send the seed request again. After three failed attempts, the SKIM will stop sending the seed request and store a trouble code. If the PCM sends a seed response, the SKIM sends a valid/invalid key message to the PCM. This is an encrypted message that is generated using the following:
- VIN - Vehicle Identification Number
- Seed - This is a random number that is generated by the PCM at each ignition key cycle.
The VIN and seed are the two variables used in the rolling code algorithm that encrypts the "valid/invalid key" message. The PCM uses the rolling code algorithm to receive, decode and respond to the valid/invalid key message sent by the SKIM. After sending the valid/invalid key message the SKIM waits 3.5 seconds for a PCM status message from the PCM. If the PCM does not respond with a valid key message to the SKIM, a fault is detected and a trouble code is stored. The SKIS incorporates a warning lamp located in the instrument cluster. The lamp receives power and ground from the instrument cluster. The lamp is actuated when the SKIM sends a PCI Bus message to the instrument cluster requesting the lamp ON. The SKIM will request warning lamp illumination for:
- Bulb checks at ignition ON
- To alert the vehicle operator to a SKIS malfunction
- Customer key programming mode
For all faults except transponder faults and VIN mismatch, the lamp remains on steady. In the event of a transponder fault the light flashes at a rate of 1 Hz (once per second). If a fault is present the lamp will remain ON or flashing for the complete ignition cycle. If a fault is stored in SKIM memory which prevents the system from operating properly, the PCM will allow the engine to start and run (for two seconds) up to six times. After the sixth attempt the PCM will not allow engine to start.