CTS Sedan RWD V6-3.0L (2010)
Information Bus: Symptom Related Diagnostic Procedures
Scan Tool Does Not Communicate with Low Speed GMLAN Device
Scan Tool Does Not Communicate with Low Speed GMLAN Device
Diagnostic Instructions
*
Perform the Diagnostic System Check - Vehicle (See: Testing and Inspection/Initial Inspection and Diagnostic Overview/Diagnostic System
Check - Vehicle) prior to using this diagnostic procedure.
*
Review Strategy Based Diagnosis (See: Testing and Inspection/Initial Inspection and Diagnostic Overview/Strategy Based Diagnosis) for an
overview of the diagnostic approach.
*
Diagnostic Procedure Instructions (See: Testing and Inspection/Initial Inspection and Diagnostic Overview/Diagnostic Procedure Instructions)
provides an overview of each diagnostic category.
Diagnostic Fault Information
Circuit/System Description
Modules connected to the low speed GMLAN serial data circuit monitor for serial data communications during normal vehicle operation. Operating
information and commands are exchanged among the modules when the ignition switch is in any position other than OFF. The low speed GMLAN serial
data circuit uses JX 201 and JX 301 as common connection points between some modules and the data link connector (DLC).
Diagnostic Aids
*
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're
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 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-initialize 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.
*
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.
*
Communication may be available between the BCM and the scan tool with the high speed GMLAN serial data system inoperative. This condition
is due to the BCM using both the high and low speed GMLAN systems.
*
An open in the low speed GMLAN serial data circuit between the splice pack and a module will only affect that specific module. This type of
failure will set a loss of communication DTC for each module effected, and the other modules will still communicate.
*
An open in the DLC ground circuit terminal 5 will allow the scan tool to operate but not communicate with the vehicle. When the scan tool
attempts to communicate with the vehicle a message "no CANdi module detected" will be displayed.
*
An open between the DLC and JX 201 will only effect the communication with the scan tool. The vehicle modules will still communicate, and the
vehicle will start.
*
The engine will not start when there is a total malfunction of the low speed GMLAN serial data circuit.
*
Technicians may find various Local Area Network (LAN) communication Diagnostic Trouble Codes (DTC) and no low speed GMLAN
communications with the scan tool.
These conditions may be caused by the installation of an aftermarket navigation radio module (see bulletins). Some customers may comment of
one or more of the following concerns:
-
Vehicle will not crank.
-
Vehicle cranks but will not start.
