12216125 xdf help

[vr4play]

Thanks for all the reply's. I was able to change that code and run it through Universal Patcher and not have any checksum errors. I will try and load to the truck after work and report back.

[Gampy]

Thanks for all the reply's. I was able to change that code and run it through Universal Patcher and not have any checksum errors. I will try and load to the truck after work and report back.

For clarity, you hex edited the value at address 0x1EFDA to 02, then used UP to correct the checksum ??

[vr4play]

I changed the hex from 03 to 02 at address 0x1EFDA and saved the file. I opened it with UP and in the log it showed all the checksums as ok so I didn't change anything there.

[ironduke]

I changed the hex from 03 to 02 at address 0x1EFDA and saved the file. I opened it with UP and in the log it showed all the checksums as ok so I didn't change anything there.

I'd do a hex compare between the original file and the one you just changed.. should have changed the checksum..

the hex editor I use if I only change 1 digit of the byte then it doesn't register it as a change so if I save it like that it doesn't keep the change, I need to type out 03 or 02.. I can't just click on the 2 or the 3... hard to explain I guess but it should have changed the checksums..

[vr4play]

I would like to thank everyone who helped, especially ironduke for posting the proper address. I was able to successfully flash the PCM with no errors and the fans come on when the AC pressure reaches it's set point. I can't explain why I didn't have to do anything with the checksums but it appears to have worked fine. I was a little nervous about bricking the PCM but it went smooth. I'm using WINHEX as my hex editor. I got it a long time ago when I used to burn chips for Mitsubishi's. There were no checksums in those ECU's. Just make a change and reburn the chip. I'm just glad I don't have to worry about burning up the compressor when trying to defrost the windows in the morning. Thanks again.

[Gampy]

Success is always good to hear ...

As Ironduke stated, that change should have invalidated the checksum.

Checksum pre edit ...

Code: Select all

 OS          Checksum 1: A36B [OK] Checksum2: 6553 [stock]
 EngineCal   Checksum 1: 6232 [OK] Checksum2: 1F89 [modded]
 EngineDiag  Checksum 1: DD9D [OK] Checksum2: 1A48 [stock]
 TransCal    Checksum 1: E4A4 [OK] Checksum2: 822A [stock]
 TransDiag   Checksum 1: B1C8 [OK] Checksum2: 9670 [stock]
 Fuel        Checksum 1: 7D59 [OK] Checksum2: E7CB [stock]
 System      Checksum 1: 1C87 [OK] Checksum2: E301 [modded]
 Speedometer Checksum 1: 3368 [OK] Checksum2: 2F57 [stock]

Checksum post edit ...

Code: Select all

 OS          Checksum 1: A36B [OK] Checksum2: 6553 [stock]
 EngineCal   Checksum 1: 6232 [OK] Checksum2: 1F89 [modded]
 EngineDiag  Checksum 1: DD9D [OK] Checksum2: 1A48 [stock]
 TransCal    Checksum 1: E4A4 [OK] Checksum2: 822A [stock]
 TransDiag   Checksum 1: B1C8 [OK] Checksum2: 9670 [stock]
 Fuel        Checksum 1: 7D59 [OK] Checksum2: E7CB [stock]
 System      Checksum 1: 1C87, Calculated: 1D87 [Fail] Checksum2: 8BF7 [modded]
 Speedometer Checksum 1: 3368 [OK] Checksum2: 2F57 [stock]

[ironduke]

Figured it out.. He modded the first file he posted that had a bad checksum to begin with..

I guess in some cases 2 wrongs do make a write... heh heh heh...

and yes,, the write instead of right was intentional...

Glad it worked out for ya..

[antus]

Thats good to hear. For the record the changes I posted turned out to be for 12212156. I had a 12212156 OS mislabeled as 12216125 in my bin correction. I only noticed when I went to flash the bin from this thread and pcm hammer told me...

[04:27:22:227] PCM operating system ID: 12212156
[04:27:22:233] File operating system ID: 12216125

[Gampy]

Thats good to hear. For the record the changes I posted turned out to be for 12212156. I had a 12212156 OS mislabeled as 12216125 in my bin correction. I only noticed when I went to flash the bin from this thread and pcm hammer told me...

[04:27:22:227] PCM operating system ID: 12212156
[04:27:22:233] File operating system ID: 12216125

Sweet ...

Looking at a 12212156 binary it looks sane, that gives us two ...

And to accumulate the findings ...
A/C Type
OsID 12216125 @0x1EFDA
OsID 12212156 @0x1E686

Values
00 - serial
01 - serial cycling
02 - analog
03 - analog cycling
04 - Passive
05 - not fitted