They go by many names, P01, P59, VPW, '0411 etc. Also covering E38 and newer here.
Gampy
Posts: 2333 Joined: Sat Dec 15, 2018 7:38 am
Post
by Gampy » Mon Jan 10, 2022 4:25 pm
We thank ya sir!
So, does that involve removing just the OS xdfchecksum node,
Code: Select all
<XDFCHECKSUM uniqueid="0x47C4">
<title>1 - Operating System Checksum</title>
<REGION>
<pluginmoduleid>9a53f579-d1c9-40c6-8691-7a54fa789d3b</pluginmoduleid>
<datastart>0x0</datastart>
<dataend>0x7FFFD</dataend>
<datasizebits>0x10</datasizebits>
<storeaddress>0x500</storeaddress>
<calculationmethod>0x0</calculationmethod>
</REGION>
</XDFCHECKSUM>
and that makes it not do the checksum for the OS which is not needed, because no code changes were done ...
Intelligence is in the details!
It is easier not to learn bad habits, then it is to break them!
If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
antus
Site Admin
Posts: 8250 Joined: Sat Feb 28, 2009 8:34 pm
cars: TX Gemini 2L Twincam TX Gemini SR20 18psi Datsun 1200 Ute Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Contact:
Post
by antus » Mon Jan 10, 2022 4:58 pm
That is correct, provided the other segments use the built in tunerpro algorithms (tunerpro default checksum plugin, twos compliment), which the XDFs I've seen do. They could use the same plugin as the OS segment and get the right result, but then you'd need the plugin for artificial reasons. If they do have a 3rd party plugin, setting it up as i've described and not changing the addresses will remove the dependency. The plugin is needed for the OS because tunerpro cant handle a non-contiguous segment like the OS segment natively. Calibration segments are contiguous and so are fine.
Gampy
Posts: 2333 Joined: Sat Dec 15, 2018 7:38 am
Post
by Gampy » Mon Jan 10, 2022 5:05 pm
Sweet, Thank ya!
Gotcha on the each <xdfchecksum> node could have it's own <pluginmoduleid> node ...
Intelligence is in the details!
It is easier not to learn bad habits, then it is to break them!
If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
12ramhemi
Posts: 14 Joined: Thu Jan 06, 2022 3:37 am
cars: 95 jeep yj doing ls swap, 2012 ram
Post
by 12ramhemi » Tue Jan 11, 2022 4:52 am
I got a copy of an 01 camaro bin from a friends car that was stock. It's a different os but even with the right xdf it's doing the same. So I tested a 059 pcm by just deleting vats and saving it. Its does the same thing there too.
So the plugin should fix this ?
I really appreciate the help with this all.
antus
Site Admin
Posts: 8250 Joined: Sat Feb 28, 2009 8:34 pm
cars: TX Gemini 2L Twincam TX Gemini SR20 18psi Datsun 1200 Ute Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Contact:
Post
by antus » Tue Jan 11, 2022 8:23 am
Either install the plugin, or edit the xdf header in tunerpro and remove the operating system checksum.
Pcmhammer wont flash a file with a bad checksum, so there is a layer of validation there.
Attachments
os checksum delete.png (70.94 KiB) Viewed 1886 times
12ramhemi
Posts: 14 Joined: Thu Jan 06, 2022 3:37 am
cars: 95 jeep yj doing ls swap, 2012 ram
Post
by 12ramhemi » Mon Jan 17, 2022 12:10 pm
Still having the same issue. I will try to edit xdf header.
antus
Site Admin
Posts: 8250 Joined: Sat Feb 28, 2009 8:34 pm
cars: TX Gemini 2L Twincam TX Gemini SR20 18psi Datsun 1200 Ute Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Contact:
Post
by antus » Mon Jan 17, 2022 3:16 pm
I wish we did have a better archive for XDFs but this is what I would use for 12212156. It does not require a plugin.
Attachments
Operating System 12212156 - 512Kb PCM - 2002 model year noplugin.xdf
(603.23 KiB) Downloaded 114 times
12ramhemi
Posts: 14 Joined: Thu Jan 06, 2022 3:37 am
cars: 95 jeep yj doing ls swap, 2012 ram
Post
by 12ramhemi » Sat Feb 05, 2022 1:37 am
Thank you Antus. This worked great.
My issue ended up being TunerPro itself. I had to uninstall it and then reinstall to get it to work correctly.