When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Just comment after seeing only U 2100 code.
A look at the DTC List shows 4 U 2100 Codes.
They all say essentially the same thing.
Configuration missing in various ways.
Based on intermittent connection thought to be linked to cooling,
seems the Module is faulty and can't Decode its own address after it is in service some time and heats up.
If that would be the case, the PCM sees it as missing because it does not answer when being addressed.
Good luck.
I just finished verifying that pin 13 and 24 both have power and pins 1 and 14 are both grounded. FORScan does not find the GWM. I left the battery disconnected for 3 hrs before attempting this check and the faults are still showing and FORScan will only connect to the HS-CAN(pic attached).
As mentioned before, it appears that after 'something cools down' everything works. After using the vehicle, the communication faults return. I am going to leave the battery disconnected and leave the vehicle sit overnight and I should be able to connect to all of the modules again tomorrow after everything has 'cooled off'. Perhaps I will be able to do the PIM then, but I honestly don't believe that is the problem. Any input is greatly appreciated.
Are you doing all this with the new module or the old one?
It is almost like your interface is not auto-switching to MS-CAN so it can see the rest of the modules. I have an old ELM327 with a manual HS-MS switch and this is how it looks until I actually switch to MS and then it can see the rest of the modules.
Are you doing all this with the new module or the old one?
It is almost like your interface is not auto-switching to MS-CAN so it can see the rest of the modules. I have an old ELM327 with a manual HS-MS switch and this is how it looks until I actually switch to MS and then it can see the rest of the modules.
Thank you for your response.
I did all of the above with the old module and tried with the new one as well. I'll try to explain and have made 3 videos to help illustrate. After the truck sits for a period of time with the power disconnected be it the battery or the BCM fuse-12, everything starts up and operates normally. To be clear, I'm not sure the power needs to be disconnected. I believe if the system is simply left idle for a period of hours, it 'resets' in some way and all the modules start communicating again until it's used and then the communication drops again.
I can connect FORScan to all of the modules and clear the DTCs. The only remaining DTC after clearing is the one GWM U2100 for incomplete setup. After a short period of time using the truck, it will have communication issues first with the ABS/Activetrac/Hill descent and then after a few minutes all the rest of the non-HS-CAN modules will stop communicating. I have to let it sit for hours again, before it will start with everything functioning normal again. This same condition takes place with both modules, the old and the new. There is no difference at all. The same series of events and the same DTCs. I have both an older ELM367 cable with the HS/MS switch and a brand new OBDlinkX cable, both work correctly after several hours of letting the truck sit and both fail in the same manner. The problem is clearly something else other than the cable or the GWMs, as I can replicate the exact issue using either of the GWMs or cables, interchangeably.
The old module worked for over a year and 1/2 with no issues and this happened all of a sudden. I do not believe that the GWM DTC for lack of a successful configuration that shows up after DTC clear on both GWMs is the issue. The videos I am attached are as follows: I just reconnected the battery and turned the ignition on attached to the old module. Everything starts normally and you can see that it connects to all modules and produces all the same communication DTCs shown in a previous video, same as before. I cleared the DTCs with only the GWM DTC remaining as has been the case and then quickly shut the ignition off, disconnected from the old GWM and connected to the new GWM. After restarting, FORScan made it past the HS-CAN and as it reaches the HUD module, you can hear the communication faults start to happen with the audible chimes and then it loses connection. I tried to scan again and it will only connect to the HS-CAN. I then shut the ignition off, reconnected back to the old GWM and it will only connect to the HS-CAN. There is clearly something about it sitting with the power off for some time and then everything works fine. As the different modules are used, a communication fault occurs which triggers a shut down of all the modules that are not a part of the HS-CAN. It appears as though all of the modules that are having an issue are routed through the BCM, Is it possible that there is an issue with the BCM and as it's being used, it starts having communication issues and that's what is causing this?
I've read for hours and while I can replicate the issue, I've not been able to find another example of this same issue before. Any input is greatly appreciated. Thank you
I think you have to conclude the replacement is faulty in some way or not in specs for the system being tried in from the same BCM signal addressing.
With all power removed, all that is possible is a drain of stored charges and a clearing of Memory that is continuously variable and not Semi permeant protected Memory.
Good luck.
After installing the new GWM, were you able to perform the PMI? It won't work correctly without writing the proper As-builts to the module and then rebooting it.
After installing the new GWM, were you able to perform the PMI? It won't work correctly without writing the proper As-builts to the module and then rebooting it.
Thank you for your continued responses.
Take care of your back, gentleman. Was finally able to get some things done. I did the PMI on the New GWM. GWM configuration DTC is now gone. Issues are not resolved, but I have been able to consistently connect to all of the modules via the New GWM. I cleared the DTCs, then rescanned, here are the DTCs that are appearing:
Edit: I had not started the vehicle, only cycled the ignition. Doing so, I was able to consistently connect to all of the modules, and the above DTCs show. Upon starting the vehicle, the ABS/Activetrac/Hill descent faults appeared and I was no longer able to connect to all of the modules, only the HS-CAN as before, and then the following DTCs appeared. There is clearly a connection to when the vehicle is starting and attempting to access these other modules that seems to cause the issue. I think we're getting closer:
I would start looking at the RCM. U0151:87 has the most occurences at 200. BCM Fuse-35 (5 A) provides the power to the RCM. Many of the modules require a message from the RCM soon after the RUN is initiated. If something with the RCM or the RCM wiring is causing the issue, this would be consistent with the issues starting after an engine start. If the problem upsets the HS2-CAN bus, which the RCM uses, this could explain the dropping of most of the other modules. The following modules all communicate over th HS2-CAN bus: ABS, C-CM, HUD, IPMA, IPMB, OCSM, PSCM, RCM, SCCM, TBM, and TCCM.
The RCM is located under the floor console so checking the wiring will require removing the floor console. There are a lot of circuits to and from the RCM, but power, ground, and the HS2-CAN bus wires are the important ones to check.
Here is the list of your DTCs:
PCM U1012:00-AF
Invalid Internal Control Module Monitoring Data Received from ABS System Control
175 occurences
APIM U023B:00-2B
Lost Communication with IPMB
43 occurences
APIM U024B:00-2B
Lost Comminucation with SCMG
43 occurences
APIM U024C:00-2B
Lost Comminucation with SCMH
43 occurences
PAM U0253:00-2B
Lost Communication with APIM
43 occurences
PAM U0252:00-2B
Lost Communication with Lighting Control Module-B (TRM)
43 occurences
BCM U0137:87-0A
Lost Communication with TBM: Missing Message
10 occurences
BCM U0252:87-0A
Lost Communication with Lighting Control Module-B (TRM): Missing Message
10 occurences
FCIM U0452:82-0A
Invalid Data Received from RCM: Sequence counter incorrect/not updated
10 occurences
C-CM U0401:86-AF
Invalid Data Received from PCM: Signal Invalid
175 occurences
ABS U0155:00-0A
Lost Communication with IPC
10 occurences
RCM B1202:01-8B
Restraint System Passener Enable Indicator: General Electrical Failure
139 occurences
RCM B00D5:01-8B
Restraint System Passenger Disable Indicator: General Electrical Failure
139 occurences
IPC U0415:82-0A
Invalid Data Received from ABS Control Module: Sequence counter incorrect/not updated
10 occurences
IPC U045A:82-0A
Invalid Data Received from PAM: Sequence counter incorrect/not updated
10 occurences
IPC U023A:00-0A
Lost Communication with IPMA
10 occurences
IPC U0102:00-0A
Lost Communication with TCCM
10 occurences
IPC U0137:00-0A
Lost Communication with TBM
10 occurences
APIM U0151:00-2B
Lost Communication with RCM
43 occurences
APIM U0155:00-2B
Lost Communication with IPC
43 occurences
PAM U0121:00-68
Lost Communication with ABS Control Module
104 occurences
PAM U0131:00-68
Lost Communication with PSCM
104 occurences
PAM U0212:00-68
Lost Communication with SCCM
104 occurences
PAM U0401:00-68
Invalid Data Received from PCM
104 occurences
BCM U0212:87-48
Lost Communication with SCCM: Missing Message
72 occurences
BCM U0151:87-C8
Lost Communication with RCM: Missing Message
200 occurences
BCM U0121:87-48
Lost Communication with ABS Control Module: Missing Message
72 occurences
BCM U0131:87-48
Lost Communication with PSCM: Missing Message
72 occurences
BCM U0252:87-48
Lost Communication with Lighting Control Module-B (TRM): Missing Message
72 occurences
Another thought. Before pulling the floor console to check the wiring, see if you can perform a self-test of the RCM.
Thank you for your response.
The RCM does not come up as one of the options to do a self-test. Here's what I see:
I checked the RCM fuse and it's good. I'm not sure my back is going to allow me to remove the floor console. Here are the current codes:
Anything else I might be able to look at that could be causing this, before I try to figure out if I can get the floor console out by myself? Thank you again.
Anything else I might be able to look at that could be causing this, before I try to figure out if I can get the floor console out by myself? Thank you again.
If your back allows it, have a real good look at the wiring harnesses at the front of the truck. Look at the ABS, PSCM, and C-CM. Maybe some rodent damage to a harness. Wouldn't be the first.