Yes it is. So you were able to replicate it? What would cause this? A borked BCM? At first I though it could have been that plug that was shorting out or something.
(Sorry for the delayed reply. I just now noticed your edit to expand yesterday's reply.) This may not be something you want to pursue if you've already decided to replace the BCM, but I'll mention it anyway, in case it provides any insight whatsoever....
Having never seen a module fail to honor a well-formed command from me (or from the software I'm using -- GDS2 in this case), I can only speculate. But...
Bearing in mind that my GDS2 tests were done with a "random" VIN, it looks like the BCM on a 2021 Sierra 3.0L Duramax is on the normal CAN bus (pins 6 & 14 of the DLC).
So, focusing on just the BCM for the moment, is it correctly reporting
status information in GDS2? For example, does it show something like the "
Driver Window Main Control Down Switch" as "
Active" when you manually activate the switch? If so, then you know that the BCM's connection to the CAN bus is working, so the BCM should be honoring any of the commands that GDS2 is sending, assuming that GDS2 is sending the proper, well-formed commands. I saw control commands (Service $AE, as mentioned previously) going out on the CAN bus when I tested this, so unless your GDS2 is behaving badly, I don't think there's any issue from the GDS2 side.
Also, with your hardware+software setup, can you send
any commands to
any other module on the vehicle's normal CAN bus and have it work as expected, (i.e. just to rule out the possibility of something more broken than just the BCM communication)?
If the random VIN I used is appropriate enough, you should have the following modules on the normal (pins 6 & 14) CAN bus:
- Engine Control Module
- Glow Plug Control Module
- Transmission Control Module
- Trailer Tire Pressure Indicator Module
- Brake System Control Module
- Body Control Module
- Serial Data Gateway Module - Processor 1
- Instrument Cluster
- Telematics Communication Interface Control Module
Picking something safe and appropriate, can you send control commands to
any of them without GDS2 reporting some sort of failure?
BTW, when doing GDS2 tests, it's always helpful for me to know the exact VIN, if you feel inclined to share that. Unlike with Tech2/Tech2Win (where it seems that the VIN is essentially irrelevant), GDS2 wisely uses the VIN to decipher some important information. Feel free to put zeros in the last several VIN characters to retain some anonymity (or just PM it to me). It's also useful to know how to answer any of the GDS2 questions (i.e. about various components present that are not determined from a VIN) that you would have encountered when first connecting to this vehicle, if you can remember any of that.
Gonna look for a BCM today. And because I have other modules reporting that they can't talk to the SDGM, I'll look for that too.
If your Sierra is like the one I "faked" to GDS2, then there are 2 "processor" components to the "SDGM" (Serial Data Gateway Module) on this vehicle -- one on the normal CAN bus and one on the SWCAN bus (pin #1 on the DLC). So it might be interesting to know which modules cannot talk to the SDGM and if they're all on the same bus.
While I was using SPS and GDS2, the truck kept giving me a "Low battery voltage, start engine" warning message despite me having a charger connected, the DMM showing over 14V and the dash gauge going all over the place. I think this points more towards the BCM. And while running, the gauge and my ScanGauge II will go above 15V but I think it's not reporting the proper voltage.
If you decide to dig any deeper on this issue, there should be at least one PID somewhere that reports the system voltage. I don't know about this vehicle, but oftentimes, several modules will report a value. It might be helpful to find and monitor one or more of those PIDs, just to see what they think the supply voltage is.