I have been trying to program my SDGM and keep getting an error message when programing side 2 it appears to be Can Bus 5 not communicating with the Radio. I look at the radio and the Vin number is missing the leading 1 in the vin number in the radio (so showing a 16 digit vin). Anyone know if this could be my problem? It is Global A and that is the only thing I can see that would keep it from completing the programing sequence. If this is my problem anyone know how to correct the VIN? I have downloaded the USB files from SPS and updated those and the program software but it will not correct the VIN

On radio the vin is always not complete. The 16 Digits are ok for the radio.

Interesting, I wonder why I can't program the second side of the SDGM

Post the DPS Log txt file for when you got the error.

I will look for that when I get back to it!

Troy, I did not get a DPS log since I was programming with SPS but here is the error message I get when trying to program side 2 of the module, side one programs fine. I spoke with Techline support and they won't help me since the vehicle is considered rebuilt but did mention wrong part or calibration. When I got the vehicle the keys were missing and I put in new keys and reprogrammed the immobilizer, it starts and drives but the dash is like a Christmas tree. Currently I put in a module from another 21 truck and it works fine, runs and drives no error lights but the keys have to be in the cup to start. I can't program the keyless entry module without updating the SDGM. Wonder if I should try using DPS to just change the VIN of the SDGM that is working that might allow me to program the rest.

5 hours ago, Dano said:

Troy, I did not get a DPS log since I was programming with SPS but here is the error message I get when trying to program side 2 of the module, side one programs fine. I spoke with Techline support and they won't help me since the vehicle is considered rebuilt but did mention wrong part or calibration. When I got the vehicle the keys were missing and I put in new keys and reprogrammed the immobilizer, it starts and drives but the dash is like a Christmas tree. Currently I put in a module from another 21 truck and it works fine, runs and drives no error lights but the keys have to be in the cup to start. I can't program the keyless entry module without updating the SDGM. Wonder if I should try using DPS to just change the VIN of the SDGM that is working that might allow me to program the rest.

It's hard to analyse the issue with the limited information provided by the SPS error response. OpCode B0 means Block Transfer To Ram, which may mean the SPS client is having problems writing the data to the module's memory. Normmaly the opCode 53, which means compare data is executed before the opCode B0, the SPS client will compare the data that's in the calibration file and whats already written to the module. If the calibration file code is incompatible with the code stored in the module, the SPS client will execute opCode EE, which means end with error.

My best guess is that the used module you're trying to program wasn't taken from the same spec vehicle as the one you're repairing. You said you only have a 16 digit VIN for the module. You can try using GM GDS2 diagnostic software "Module Diagnostics" then "Identification Information" option, which should display the full 17 digit VIN, then input the VIN in this website https://www.vindecoderz.com/, which will inform you about the vehicle model and year the module was taken from.

GM GDS2 Identification Information

What device are you using? I'm going to take a guess but it's an MDI clone? If so, you're not going to be able to program it through SPS (looking at a utility right now that aligns with what you're showing). Either way, more information is needed.

Troy, Thanks for your response and information, that is the best information I have gotten about the codes on SPS.

The module I was trying to program is a brand new virgin Serial Data Gateway Module from GM. The SDGM module that is working without programming has a different VIN and came from the same model and year truck, but the programming in it, is allowing the vehicle to operate normally except for the keyless entry and proximity start. So, I am not messing with that module unless it would be to change the VIN to the vehicle that I am having trouble programming the new SDGM.

My understanding was that SPS programming looks for VIN numbers in the other modules which are all 100% correct except the Radio is missing the first Digit, even after reprogramming. But based on other comments that may be normal. So, I am stumped.

Codebuilder: I am using a VCX FD interface with ACDelco Tech stream SPS and can program my 2022 corvette and my 2019 Yukon, with no issues so I am confident it is not the interface.

9 minutes ago, Dano said:

Troy, Thanks for your response and information, that is the best information I have gotten about the codes on SPS.

The module I was trying to program is a brand new virgin Serial Data Gateway Module from GM. The SDGM module that is working without programming has a different VIN and came from the same model and year truck, but the programming in it, is allowing the vehicle to operate normally except for the keyless entry and proximity start. So, I am not messing with that module unless it would be to change the VIN to the vehicle that I am having trouble programming the new SDGM.

My understanding was that SPS programming looks for VIN numbers in the other modules which are all 100% correct except the Radio is missing the first Digit, even after reprogramming. But based on other comments that may be normal. So, I am stumped.

Codebuilder: I am using a VCX FD interface with ACDelco Tech stream SPS and can program my 2022 corvette and my 2019 Yukon, with no issues so I am confident it is not the interface.

100% that's your issue. The VCX has an issue with the buffer. Can you zip up your SPS Cache folder? If you have DPS I can build you a file that will program it. This is a common issue with clone devices. The only way otherwise to program it is to get a genuine MDI 2. You should include the log (it's under C:\Users\[username]\SPS and I can't remember which log it is there, might be in \SPSDebug) but I can almost bet you'll see repeated transmit calls and then it just errors out.

Codebuilder: Interesting, I will take a look for the file. Strange it programs other modules and just not that one?

14 minutes ago, Dano said:

Codebuilder: Interesting, I will take a look for the file. Strange it programs other modules and just not that one?

Yeah, there's a few you're going to hit with that. There's a few other posts that I've helped people with this same issue. They've defined different packet sizes in different utilities so some you'll encounter, some you won't. I have a VNCI and it has the same issue. My genuine MDI 2, no problems at all. You should be able to program most modules though.

Codebuilder:

Attached is the zip file from SPS if it is the right one? It looks like it is seeing something in the network it didn't expect to see?

spsDebug.20251113101731.zip

Can you do me a favour, delete the SPSCache and SPSDebug, try to program it again then send me the SPSDebug files again?

think in radio and sdgm vin get populated during setup part

Codebuilder - I read through an earlier thread you and Lyubomir were active on about the K56 and VCX essentially having the same problem I am experiencing, so I am going to look for another MIDI clone to program it. Do you have a recommendation?

Reading the Thread, it looks like you even tried to bench test it and it failed side B programming with nothing else connected.

I am wondering since I have a working module even though it has a different set of VIN#s if I can just immobilize the vehicle and get my key fobs working wirelessly so I don't have to put the key in the cup to start the vehicle or use the key to lock/unlock? Or would that just fail due to different VIN's from the other modules?

On 11/26/2025 at 6:20 AM, Dano said:

Codebuilder - I read through an earlier thread you and Lyubomir were active on about the K56 and VCX essentially having the same problem I am experiencing, so I am going to look for another MIDI clone to program it. Do you have a recommendation?

Reading the Thread, it looks like you even tried to bench test it and it failed side B programming with nothing else connected.

I am wondering since I have a working module even though it has a different set of VIN#s if I can just immobilize the vehicle and get my key fobs working wirelessly so I don't have to put the key in the cup to start the vehicle or use the key to lock/unlock? Or would that just fail due to different VIN's from the other modules?

99% I believe that's what's likely happening, the issue is your SPSDebug you sent me has too many files. That's why I wanted to see if you could delete the SPSCache and SPSDebug folders, attempt again, then zip those up. Can you also screenshot the calibration numbers screen that shows the file #. It'll make life easier (although I don't remember there being a lot).

Well, it allowed me to immobilize with the current SDGM another thing I learned is you can't properly immobilize with dead remote batteries! Everything worked but no wireless key functions, as it turns out, the new keys I bought had the batteries installed upside down and were dead, replaced the batteries correctly re-immobilized and everything now works, even with the wrong vin in the gateway module, so I am going to leave well enough alone and move on to other things. Thanks for all of your suggestions and support!

I wish I could find a site this informative about Lexus and Toyota! I have a Smart Key Module issue that is driving me nuts, was hit by lightning and shorting out the network but still starts the car. I cloned the eeprom to a new module and can't get it to work, the original module works but the clone won't. I can only find 1 eeprom on the board so assuming Toyota must have some other memory circuit I can't find/figure out.

Dani: Did you ever try the genuine MDI 2 ? I ask because I have 100% the exact same situation. VCX FD. 2021 Silverado 1500. Processor two fails program with exact same errors. Codebuilder sounds like he knows and has seen this so I’m about to order one