12587603 XDF Checksum problems

[yoheer]

Hey
I use 3 different xdf files

Operating System 12587603 - 1Mb PCM - 2004 model year.xdf

12587603_RC1.xdf

12587603+AC.xdf

Plus I use 2 plugins (Located in documents/tunerpro files/plugins)

1Mb PCM OS Checksum Plugin.dll

GM-P01-P59-checksum-plugin.dll

The first xdf works perfect (It's locked for modifying.)

I have problems using the 2nd xdf file.
After modifying saving and trying to write PCMHammer says that there is bad OS segment (The very first line after choosing modded bin)
The picture is an example. It's not my screenshot.

hammer.jpg

12587603+AC.xdf allows to change OS checksum value manually, but I think this is not the right way.
How to solve the problem?

[antus]

2 ways

1) If you are not editing adding a code patch, remove the os checksum calculator completely, as that segment wont change for normal tuning.
2) Set up the XDF like this, and select the working plugin.

[yoheer]

Antus, thank you VERY MUCH!
I just tried second way. It works!!!
Today I wasted 7 hours sitting in a car and trying to make a correct file and flash the pcm. And it was just kicking my butt

[yoheer]

Btw is it ok that i make some parameter mods, but checksum changes in OS segment?

[antus]

It does sound suspicious, I'd check exactly what changed against another XDF or app. Or tell us what your changing and post up the address which changes in the bin and I can validate it. Calibration changes are not using in the OS segment. Can you post up a before and after bin?

[Duck1]

Having issues with tunnerpro. I get a checksum error when saving bin files. I tried re-save of a virgin file I read from my daily driver, no changes received same message. Pcm hammer program now says file is corrupt and will damage pcm. I'm new to this sorry for my ignorance

[B52Bombardier1]

Do you have all of the correct plug ins installed for Tuner Pro RT? Did you edit your BIN OS file using the correct XDF file? This second question seems to be what bites most people.

Rick

[antus]

Ideally, unless your installing OS patches (most people are not), if the XDF isnt locked (many are) you can delete the OS checksum an then make your edits again in a new copy of the file. The OS checksum and plugins concept kind of got legs of its own and created more problems than it solved. Calibration changes DO NOT require the OS checksum to be updated and re-written, most XDFs do not have any data fields that necessitates that sum.