Hi

 

Im stuck, im trying to get to work a 2018 Equinox BCM in a 2019 Equinox, i already changed the PIN and vin in the used module but still doesn't accept the 2019 new calibrations.

 

Can someone throw me a hint on what's the missing step, been looking information for a couple weeks now but nothing.

 

thanks you so much

will you mind to explain little more about error or reason why new calibrations are not accepted? got any log or pictures to share?

 

55 minutes ago, Last Captain said:

will you mind to explain little more about error or reason why new calibrations are not accepted? got any log or pictures to share?

 

Im offsite rn, ill do another try tomorrow and will upload the files

program onlins sps,, you alraedy change vin,, it will work if 2018 is same hardware to 2019,, once bcm vin/pin change it must be work,,, same as bcm swaping memory,, 

 

Original VIN, donor VIN and PNs of BCM will help to understand the issue.

Morning everyone, this is what i got it almost feels like the hardware is not compatible i can reprogram with original calibration but cant reprogram with the 2019 calibration

spslog.txt

Extra info:

 

VIN OF THE NEW VEHICLE: 3GNAXUEV4KL288534 2019 Equinox

VIN OF THE OLD VEHICLE: 3GNAXHEV6JS574445 2018 Equinox

 

PIN OF THE NEW VEHICLE: 3627

PIN OF THE OLD VEHICLE: 7473

 

5 Bytes SEED: 46 26 9E F4 06

Key: 02 3A 09 AA 52 

Guys quick update, i was able to turn the theft light off, the car doesn't crank but idk it have lot of sensors disconnected i'll update later when all the disconnected stuff are fixed.

 

BTW i still not able to change the calibration to 2019 it looks like the files of 2019 has some kind of verification that the 2018 BCM doesn't pass.

What PN of Utilfile use SPS?

11 minutes ago, _mrv_ said:

What PN of Utilfile use SPS?

I dont understand the question, this is the info of the BCM, the vin is from 2019 beacuse i changed it but still wont program the 2019 calibration files

 

 

 

 

this is the 2019 calibration

 

 

 

this is the 2018 calibration files

spslog.txt This is for my last try to flash the 2019 calibration 

 

i found this comparison in the log

11 hours ago, diyhobby said:

i found this comparison in the log

It is OK. DPC compares current version of OpSW and new.

 

Quote

UtilityFileStatus Step = 0D, OpCode = B0
  13:18:23.552<[.H..]00 00 02 41 36 00 FE DF 00 00 D9 D8 00 01 23 28 00 CE 5F B9 41 4B 00 1F .. [4090] FramePad 
  13:18:23.552>[.H..]00 00 02 41 [0004] TxDone 
  13:18:24.420>[.H..]00 00 06 41 7F 36 78 [0007]

 

Positive response on Step 0D should be 76.

You should see in log next string

Quote

13:18:2x.xxx>[.H..]00 00 06 41 76 [0005]

 

 ... but BCM return Negative response $7F

Quote

13:18:24.420>[.H..]00 00 06 41 7F 36 78 [0007]

 

This Return Code ($78) means "Request Correctly Received-Response Pending"

 

It seems like BCM "froze" after that. Because of there was not any response from BCM after timeout

 

Quote

* Timeout Condition:  ECU DID NOT RESPOND - Invoke RETRY LOGIC!

 

And lets see below, DPS (according to Utility File) send new request for Security Access

Quote

UtilityFileStatus Step = 04, OpCode = 27
  13:19:04.446<[.H..]00 00 02 41 27 01 [0006] FramePad 
  13:19:04.446>[.H..]00 00 02 41 [0004] TxDone

 

And there was not any response too

Quote

* Timeout Condition:  ECU DID NOT RESPOND - Invoke RETRY LOGIC!

 

So... I have only one idea. The length of this block "13:18:23.552<[.H..]00 00 02 41 36 00 FE DF 00 00 D9 D8 00 01 23 28 00 CE 5F B9 41 4B 00 1F .. [4090]" is more then BCM expected.

 

Could you try to reflash with MY18 cals and provide log.

@_mrv_ Hey man, had to change vin back to stock for it to flash 2018.

 

 

line 1827

 

Quote

UtilityFileStatus Step = 0F, OpCode = B0
  11:38:38.763<[.H..]00 00 02 41 36 00 FE DD C0 80 00 00 00 00 80 07 32 00 FF FF FF FF FF FF .. [4090] FramePad 
  11:38:38.763>[.H..]00 00 02 41 [0004] TxDone 
  11:38:39.529>[.H..]00 00 06 41 76 [0005] 
  11:38:39.534<[.H..]00 00 02 41 36 00 FE DD D0 70 00 00 2B 5E C8 01 E1 59 EA 05 80 FF 04 00 .. [0968] FramePad 
  11:38:39.534>[.H..]00 00 02 41 [0004] TxDone 
  11:38:39.721>[.H..]00 00 06 41 76 [0005] 
UtilityFileStatus Step = 10, OpCode = 34
  11:38:39.721<[.H..]00 00 02 41 34 00 00 00 0F F6 [0010] FramePad 
  11:38:39.723>[.H..]00 00 02 41 [0004] TxDone 
  11:38:39.741>[.H..]00 00 06 41 74 [0005] 
UtilityFileStatus Step = 11, OpCode = B0
  11:38:39.751<[.H..]00 00 02 41 36 00 FE DF 00 00 4B F7 00 02 22 00 05 04 FA 57 41 42 05 11 .. [2378] FramePad 
  11:38:39.751>[.H..]00 00 02 41 [0004] TxDone 
  11:38:40.203>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.249>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.288>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.296>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.304>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.343>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.384>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.391>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.400>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.408>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.451>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.458>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.467>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.474>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.483>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.522>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.530>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.540>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.548>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.589>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.626>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.667>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.707>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.716>[.H..]00 00 06 41 7F 36 78 [0007] 
  11:38:40.740>[.H..]00 00 06 41 76 [0005] 

 

spslog 2018 vin.txt

You can use DPS from here. And you will not have to change the VIN every time

35 minutes ago, _mrv_ said:

You can use DPS from here. And you will not have to change the VIN every time

Yes but i want to program the 2019 calibration but still cant, do you think using the utility file from 2018 and using the calibration from 2019 will work?

This is the 2019 calibration from DPS, i think it just a hardware compatibility issue. Im done with this just going to buy a new module and make sure is the correct part number

dpslog.Txt

It will useful to see DPS log from MY18. I still think that issue with OPsw. Lengths of OPsw from MY18 and MY19 are different.

On 3/9/2023 at 2:19 AM, _mrv_ said:

It will useful to see DPS log from MY18. I still think that issue with OPsw. Lengths of OPsw from MY18 and MY19 are different.

Hey man, quick update i was doing everything right, i called to the dealership and got the correct part number (the one that was in the car was in fact incorrect) i suppose there was some hardware incompatibility that doesnt allow to load the calibration, any ways problem is solved, replaced with the correct part number, programmed and boom!

 

Thanks for your help man, i appreciate it

Great