Powertrain

The powertrain used in this vehicle consists of a twin cam V6 engine mated to a 4T65-E electronically controlled transaxle. The powertrain has electronic controls to reduce exhaust emissions while maintaining excellent driveability and fuel economy. The Powertrain Control Module (PCM) is the heart of this control system.

The Powertrain Control Module is designed to maintain exhaust emission levels to Federal or California standards while providing excellent driveability and fuel efficiency. Review the components and wiring diagrams in order to determine which systems are controlled by the PCM. The PCM monitors numerous engine and vehicle functions. The following are some of the functions that the PCM controls:

Powertrain Control Module Function

The PCM constantly looks at the information from various sensors and other inputs, and controls systems that affect vehicle performance and emissions. The PCM also performs diagnostic tests on various parts of the system. The PCM can recognize operational problems and alert the driver via the Malfunction Indicator Lamp (MIL). When the PCM detects a malfunction, it stores a Diagnostic Trouble Code (DTC). The problem area is identified by the particular DTC that is set. The Control Module supplies a buffered voltage to various sensors and switches. The input and output devices in the control module include an analog to digital converters, signal buffers, counters, and output drivers. The output drivers are electronic switches which complete a ground circuit when turned on. Most PCM controlled components are operated via output drivers. The PCM monitors these driver circuits for proper operation, and in most cases, can set a DTC corresponding to the controlled device if a problem is detected.

Torque Management

Torque Management is a function of the PCM that reduces engine power under certain conditions. Torque management is performed for three reasons:

The PCM uses manifold vacuum, intake air temperature, spark retard, engine speed, engine coolant temperature, A/C clutch status, and EGR valve position to calculate engine output torque. It then looks at torque converter status, transaxle gear ratio, and brake switch inputs and determines if any torque reduction is required. If torque reduction is required, the PCM retards spark as appropriate to reduce engine torque output. In the case of abusive maneuvers, the PCM may also shut off fuel to certain cylinders to reduce engine power.

There are five instances when engine power reduction is likely to be experienced

In the first two instances, the driver is unlikely to even notice the torque management actions. In the other cases, engine power output will be moderate at full throttle.

When the PCM determines that engine power reduction is required, it calculates the amount of spark retard necessary to reduce power by the desired amount. This spark retard is then subtracted from the current spark advance. In the case of abusive maneuvers, the PCM will momentarily disable fuel injectors to obtain the necessary amount of torque reduction.

Traction Control

Traction Control is a function of the PCM and the EBTCM that reduces front wheel slip during acceleration by applying the front brakes and reducing engine power. Refer to ABS Description in Antilock Brake System Delco VI or ABS Description in Antilock Brake System Bosch 5.3 for an explanation of the EBTCMs role in traction control. The PCM continuously sends out a PWM signal that indicates the torque output of the powertrain. This signal, referred to as the Delivered Torque signal, is used by the EBTCM to determine what action is required when it sees the front wheels slipping. The EBTCM may decide to apply the front brakes only or apply the front brakes and request reduced torque output from the powertrain. The EBTCM requests reduced torque using another PWM signal. This signal, referred to as the Desired Torque signal, is used by the PCM to determine if the EBTCM is requesting reduced torque output from the powertrain. The PCM reduces engine torque by adjusting ignition timing.

Desired Torque will normally be a 90 percent duty cycle signal to the PCM. When the EBTCM decides to request reduced engine power, it decreases the duty cycle of the Desired Torque signal by the amount of torque reduction required (90 percent duty cycle means no torque reduction, 10 percent duty cycle means 100 percent torque reduction). The PCM responds by shutting off fuel to one or more cylinders depending on the percent torque reduction requested. The PCM will not shut off any fuel injectors if any of the following conditions are present

The disabled fuel injectors will be re-enabled one by one as the need for traction control ends.

Several DTCs disable traction control when set. They will also trigger a TRACTION OFF light or message. The PCM traction control override also disables traction control and triggers the message. To diagnose a Traction Off light/message, diagnose any DTCs set first. Then check the traction control override and, if active, deactivate the override. If the TRACTION OFF light/message is still present, refer to Diagnostic System Check - ABS in Antilock Brake System Delco VI or Diagnostic System Check - ABS in Antilock Brake System Bosch 5.3 for further diagnosis.

UART Serial Data

Two methods of data transmission are used. One method involves a Universally Asynchronous Receiving/Transmitting (UART) protocol. UART is an interfacing device that allows the on board computer to send and receive serial data. Serial data refers to information which is transferred in a linear fashion - over a single line, one bit at a time. A data bus is the electronic pathway through which serial data travels. The UART receives data in a serial format, converts the data to parallel format, and places them on the data bus (which is recognizable to the on board computer). This method had been the common strategy for establishing a communication link between the on board control module and the off board monitor/scanner since 1981. UART is sometimes used to communicate between modules within the vehicle.

Class II Serial Data

The Class 2 serial data circuit allows the control modules to communicate with each other. The modules send a series of digital signals pulsed from high to low voltage (approximately 7 volts to 0 volts). These signals are sent in variable pulse widths of one or two bits. A string of these bits creates a message that is sent in a prioritized data packet. This allows more than one module to send messages at the same time without overloading the serial data line. The speed, or BAUD rate, at which the control modules communicate depends on the message content. Large message content lowers the BAUD rate while small message content increases the BAUD rate. The average BAUD rate is approximately 10.4 Kbps (10,400 bits per second). When the key is ON, each module sends a State of Health message to the other control modules using the class 2 serial data line. This ensures that the modules are working properly. When the module stops communicating, a loss of the state of health message occurs. The control modules that expect to receive the message detect the loss, and will set a loss of communication DTC.

Data Link Connector (DLC)

The provision for communicating with the control module is the Data Link Connector (DLC). It is usually located under the instrument panel. The DLC is used to connect to a scan tool. Some common uses of the scan tool are listed below:

Service Engine Soon/Malfunction Indicator Lamp (MIL)

The Service Engine Soon/Malfunction Indicator Lamp (MIL) is located in the Instrument Panel Cluster (IPC). The MIL is controlled by the PCM and is used to indicate that the PCM has detected a problem that affects vehicle emissions, may cause powertrain damage, or severely impacts driveability.

Trip

A trip is an interval of time during which the diagnostic test runs. A trip may consist of only a key cycle to power up the PCM, allow the diagnostic to run, then cycle the key off to power down the PCM. A trip may also involve a PCM power up, meeting specific conditions to run the diagnostic test, then powering down the PCM. The definition of a trip depends on the diagnostic. Some diagnostic tests run only once per trip (i.e., catalyst monitor) while other tests run continuously during each trip (i.e., misfire, fuel system monitors).

Warm-up Cycle

The PCM uses warm-up cycles to run some diagnostics, and to clear any diagnostic trouble codes (DTCs). A warm-up cycle occurs when the engine coolant temperature raises 22 degrees C (40 degrees F) from start-up. The engine coolant must also achieve a minimum temperature of 71 degrees C (160 degrees F). The PCM counts the number of warm-up cycles in order to clear the Malfunction Indicator Lamp (MIL). The PCM will clear the DTC(s) when 40 consecutive warm-up cycles occur without a malfunction.

Diagnostic Trouble Code Display

DTCs can only be displayed with the use of a scan tool.

Diagnostic Trouble Codes (DTCs)

The PCM is programmed with test routines that check the operation of the various systems the PCM controls. Some tests check internal PCM functions. Many tests are run continuously. Other tests run only under specific conditions (referred to as Conditions for Running the DTC). When the vehicle is operating within the conditions for running a particular test, the PCM checks certain parameters and determines whether or not the values are within an expected range. Which parameters and what values are considered outside the range of normal operation are listed as Conditions for Setting the DTC. When the Conditions for Setting the DTC are true, the PCM executes the Action Taken When the DTC Sets. Some DTCs alert the driver via the MIL or a message. Other DTCs do not trigger a driver warning, but are stored in memory. Refer to the DTC Type Table for a complete list of PCM DTCs and what driver alerts they trigger. The PCM also saves data and input parameters when most DTCs are set. This data is stored in Freeze Frame and/or Failure Records.

DTC's are categorized by type. The DTC type relates to how the MIL operates and how the fault data is stored when a particular DTC fails. In some cases there may be exceptions to this structure. Therefore, it is important to read the Action Taken When the DTC Sets and Conditions for Clearing the MIL/DTC in the supporting text when diagnosing the system.

The following list describes the general characteristics of each DTC type:

DTC Status

When the scan tool displays a DTC, the status of the DTC is also displayed. The following DTC statuses will be indicated only when they apply to the DTC that is set.

Fail This Ign. (Fail This Ignition): Indicates that this DTC failed during the present ignition cycle.

Last Test Fail: Indicates that this DTC failed the last time the test ran. The last test may have run during a previous ignition cycle if an A or B type DTC is displayed. For type C DTCs, the last failure must have occurred during the current ignition cycle to appear as Last Test Fail.

MIL Request: Indicates that this DTC is currently requesting the MIL. This selection will report type B DTCs only when they have requested the MIL. (failed twice).

Test Fail SCC (Test Failed Since Code Clear): Indicates that this DTC that has reported a failure since the last time DTCs were cleared.

History: Indicates that the DTC is stored in the PCMs History memory. Type B DTCs will not appear in History until they have requested the MIL (failed twice). History will be displayed for all type A DTCs and type B DTCs (which have requested the MIL) that have failed within the last 40 warm-up cycles. Type C DTCs that have failed within the last 40 warm-up cycles will also appear in History.

Not Run SCC (Not Run Since Code Clear): DTCs will be listed in this category if the diagnostic has not run since DTCs were last cleared. This status is not included with the DTC display since the DTC can not be set if the diagnostic has not run. This information is displayed when DTC Info is requested using the scan tool.

Clearing Diagnostic Trouble Codes

Use a scan tool to clear DTCs from the PCM memory. Disconnecting the vehicle battery to clear the PCM memory is not recommended. This may or may not clear the PCM memory and other vehicle system memories will be cleared. Do not disconnect the PCM connectors solely for clearing DTCs. This unnecessarily disturbs the connections and may introduce a new problem. Before clearing DTCs the scan tool has the capability to save any data stored with the DTCs and then display that data at a later time. Capture DTC info before beginning diagnosis (refer to Capturing DTC Info). Do not clear DTCs until you are instructed to do so within a diagnostic procedure.

Many PCM DTCs have complex test and failure conditions. Therefore, simply clearing DTCs and watching to see if the DTC sets again may not indicate whether a problem has been corrected. To verify a repair after it is complete, you must look up the test conditions and duplicate those conditions. If the DTC runs and passes, chances are good that the problem is fixed.

Freeze Frame Data

Government regulations require that engine operating conditions be captured whenever the MIL is illuminated. The data captured is called Freeze Frame data. The Freeze Frame data is very similar to a single record of operating conditions. Whenever the MIL is illuminated, the corresponding record of operating conditions is recorded as Freeze Frame data. A subsequent failure will not update the recorded operating conditions.

The Freeze Frame data parameters stored with a DTC failure include the following:

Freeze frame data can only be overwritten with data associated with a misfire or fuel trim malfunction. Data from these faults take precedence over data associated with any other fault. The Freeze Frame data will not be erased unless the associated history DTC is cleared.

Failure Records Data

In addition to Freeze Frame data the PCM may also store Failure Records data when a DTC reports a failure. Unlike Freeze Frame data, Failure Records data can be stored by DTC's that DO NOT illuminate the MIL.

Freeze Frame, Failure Records data may be retrieved through the Diagnostic Trouble Code menu on scan tool. If more than one DTC is set review the odometer or engine run time data located in the Freeze Frame, Failure Records info to determine the most current failure.

Keep in mind that once Freeze Frame or Failure Record is selected, the parameter and input data displayed will look just like the normal PCM data except the parameters will not vary since it is displaying stored data.

Important: Always capture the Freeze Frame and Failure Records information with the scan tool BEFORE proceeding with diagnosis. Clearing DTC's, disconnecting the battery, disconnecting PCM or body connectors or procedures performed during diagnosis may ERASE or overwrite the stored Freeze Frame and Failure Records data. Loss of this data may prevent accurate diagnosis of an intermittent or difficult to set DTC.

Capturing DTC Info (Capture Info)

Selecting this option on the scan tool allows the technician to record the Freeze Frame and Failure Records that may be stored in the PCMs memory. Capture DTC info before beginning diagnosis. This is a step in the OBD System Check. At the end of the diagnostic tables, you are instructed to clear DTCs, verify that the repair was successful and then to review captured information. The captured information will contain any additional DTCs and related data that was stored originally (if multiple DTCs were stored).

Storing And Erasing Freeze Frame Data

Government regulations require that engine operating conditions be captured whenever the MIL is illuminated. The data captured is called freeze frame data. The freeze frame data is very similar to a single record of operating conditions. Whenever the MIL is illuminated, the corresponding record of operating conditions is recorded to the freeze frame buffer.

Each time a diagnostic test reports a failure, the current engine operating conditions are recorded in the freeze frame buffer. A subsequent failure will update the recorded operating conditions. The following operating conditions for the diagnostic test which failed typically include the following parameters:

Freeze frame data can only be overwritten with data associated with a misfire or fuel trim malfunction. Data from these faults take precedence over data associated with any other fault. The freeze frame data will not be erased unless the associated history DTC is cleared.

Storing and Erasing Failure Records Data

When a PCM DTC sets, the PCM does several things. Among them is to save useful data and input parameter information for service diagnosis. This information is referred to as Freeze Frame, Failure Records. You will see references to these in many PCM DTC diagnostic tables because this information can be useful in pinpointing a problem even if the problem is not present when the vehicle is in the service bay.

Freeze Frame, Failure Records data may be retrieved through the DTC menu on scan tool. If more than one DTC is set review the odometer or engine run time data located in the Freeze Frame, Failure Records info to determine the most current failure.

Keep in mind that once Freeze Frame or Failure Record is selected, the parameter and input data displayed will look just like the normal PCM data except the parameters will not vary since it is displaying stored data.

Capturing DTC Info (Capture Info)

Selecting this option on the scan tool allows the technician to record the Freeze Frame and Failure Records that may be stored in the PCMs memory. This can be useful if the PCM or battery must be disconnected and later review of the stored information may be desired.

PCM Snapshot Using A Scan Tool

The scan tool can be set up to take a 'snapshot' of the parameters available via serial data. The Snapshot function records live data over a period of time. The recorded data can be played back and analyzed. The scan tool can also graph parameters singly or in combinations of parameters for comparison. The snapshot can be triggered manually at the time a symptom is noticed, or set up in advance to trigger when a DTC sets. An abnormal value captured in the recorded data may point to a system or component that needs to be investigated further. The snapshot will remain in the scan tool memory even after the tool is disconnected from it's power source. Refer to the scan tool user instructions for more information on the Snapshot function.