Captiva |
||||||||
|
|
|
|||||||
| • | Perform the Diagnostic System Check - Vehicle prior to using this diagnostic procedure. |
| • | Review Strategy Based Diagnosis for an overview of the diagnostic approach. |
| • | Diagnostic Procedure Instructions provides an overview of each diagnostic category. |
Circuit | Short to Ground | Open/High Resistance | Short to Voltage | Signal Performance |
|---|---|---|---|---|
B+ | U2206 | U2206 | -- | -- |
Ignition | U2206 | U2206 | -- | -- |
Low Speed GMLAN Serial Data | 1 | U2206 | 1 | -- |
Mid Speed GMLAN Serial Data (+) | 2 | U2206 | 2 | -- |
Mid Speed GMLAN Serial Data (-) | 2 | U2206 | 2 | -- |
Ground | -- | U2206 | -- | -- |
1. Scan Tool Does Not Communicate with Low Speed GMLAN Device 2. Scan Tool Does Not Communicate with Mid Speed GMLAN Device | ||||
The serial data circuit is the means by which the control modules in the vehicle communicate with each other. Once the scan tool is connected to the serial data circuit through the data link connector (DLC), the scan tool can be used to monitor each control module for diagnostic purposes and to check for diagnostic trouble codes (DTCs). When the ignition switch is in RUN, each control module communicating on the serial data circuit sends a state of health (SOH) message to ensure that the control module is operating properly. When a control module stops communicating on the serial data circuit, for example if the control module loses power or ground, the SOH message it normally sends on the serial data circuit disappears. Other control modules on the serial data circuit, which expect to receive that SOH message, detect its absence; those control modules in turn set a DTC associated with the loss of SOH of the non-communicating control module. The DTC is unique to the control module which is not communicating and one or more control modules may set the same exact code. A loss of serial data communications DTC does not represent a failure of the control modules that contain the stored code.
| • | The system voltage is between 9–16 V. |
| • | The vehicle power mode master requires serial data communication to occur. |
A supervised periodic message that includes the transmitter module availability has not been received.
Specific subsystems will not function.
| • | A current DTC clears when the malfunction is no longer present. |
| • | A history DTC clears when the module ignition cycle counter reaches the reset threshold of 50, without a repeat of the malfunction. |
| • | Sometimes, while diagnosing a specific customer concern or after a repair, you may notice a history U-code present. However, there is no associated "current" or "active" status. Loss-of- communication U-codes such as these can set for a variety of reasons. Many times, they are transparent to the vehicle operator and technician, and/or have no associated symptoms. Eventually, they will erase themselves automatically after a number of fault-free ignition cycles. This condition would most likely be attributed to one of these scenarios: |
| - | A control module on the data communication circuit was disconnected while the communication circuit is awake. |
| - | Power to one or more control modules was interrupted during diagnosis. |
| - | A low battery condition was present, so some control modules stop communicating when battery voltage drops below a certain threshold. |
| - | Battery power was restored to the vehicle and control modules on the communication circuit did not all re-initialise at the same time. |
| - | If a loss-of-communication U-code appears in history for no apparent reason, it is most likely associated with one of the scenarios above. These are all temporary conditions and should never be interpreted as an intermittent fault, causing you to replace a part. |
| • | A control module may have a U-code stored in history that does not require any repairs. Issues with late or corrupted messages between control modules can be temporary with no apparent symptom or complaint; this does not mean the control module is faulty. Do not replace a control module based only on a history U-code. |
| • | Do not replace a control module reporting a U-code. The U-code identifies which control module needs to be diagnosed for a communication issue. |
| • | Use Data Link References to determine if the control module uses high, mid, or low speed GMLAN serial data communications. |
| • | Some control modules may not have internal protection for specific control circuits and may open a B+ or ignition fuse. If a fuse is open and the B+ or ignition circuit is not shorted to ground, ensure none of the control circuits are shorted to ground before replacing the control module. |
Note: Use the schematic to identify the control module B+, ignition, ground, and serial data circuit terminals.
| ⇒ | If greater than the specified range, test the ground circuit for an open/high resistance. |
| ⇒ | If the test lamp does not illuminate, test the B+ circuit for a short to ground or an open/high resistance. If the circuit fuse is open, test the control circuits of the driver information centre for a short to ground. If the circuits test normal, replace the driver information center. |
| ⇒ | If the test lamp does not illuminate, test the ignition circuit for a short to ground or an open/high resistance. If the circuit fuse is open, test the control circuits of the driver information centre for a short to ground. If the circuits test normal, replace the driver information center. |
| • | DLC low speed GMLAN serial data terminal 1 |
| • | DLC mid speed GMLAN serial data terminal 3 or 11 |
| ⇒ | If greater than the specified range, test the serial data circuit for an open/high resistance between the driver information center and the control module setting the DTC or a serial data splice pack. |
Perform the Diagnostic Repair Verification after completing the diagnostic procedure.
| • | Control Module References for control module replacement, programming and setup |
| © Copyright Chevrolet. All rights reserved |
