Using XDF from older OS (7603 on 6960)
Using XDF from older OS (7603 on 6960)
I have a 2004 Flex Tahoe that came with 7603. I installed e-fans and modified the PCM using the XDF found here for that OS and flashed via PCM Hammer. All good. Awesome, in fact.
However, a while back I swapped fuel pumps and it never registers full after a refill. There's a fuel calibration available - 12597473: New calibration to correct fuel gauge not reading full when fuel tank is filled. I couldn't figure out how to flash just the calibration via SPS/Techline - it wanted me to also upgrade the OS to 12606960. Prior to putting in the e-fans and modified 7603, I flashed the full she-bang to a spare PCM and filled up with gas. Gauge registered full!
My question is this - can I use the 7603 XDF to perform the same parameter modifications for fans to the 6960 OS? I compared the outputs using a diff tool of TunerPro "Save data to text file" functionality of both unmodified BIN and can tell there are differences, but the "fan" section lines up perfectly. I made the modifications and saved the bin file successfully and PCM Hammer says the checksums are ok. Just wondering if I'm asking for trouble or if all will be fine. I'd really like to have a full fuel gauge.
OS 12606960 replaces 12585950 and 12587603 - which one would think they're from the same lineage.
However, a while back I swapped fuel pumps and it never registers full after a refill. There's a fuel calibration available - 12597473: New calibration to correct fuel gauge not reading full when fuel tank is filled. I couldn't figure out how to flash just the calibration via SPS/Techline - it wanted me to also upgrade the OS to 12606960. Prior to putting in the e-fans and modified 7603, I flashed the full she-bang to a spare PCM and filled up with gas. Gauge registered full!
My question is this - can I use the 7603 XDF to perform the same parameter modifications for fans to the 6960 OS? I compared the outputs using a diff tool of TunerPro "Save data to text file" functionality of both unmodified BIN and can tell there are differences, but the "fan" section lines up perfectly. I made the modifications and saved the bin file successfully and PCM Hammer says the checksums are ok. Just wondering if I'm asking for trouble or if all will be fine. I'd really like to have a full fuel gauge.
OS 12606960 replaces 12585950 and 12587603 - which one would think they're from the same lineage.
Re: Using XDF from older OS (7603 on 6960)
I don’t know the answer, but I’m interested to know what you find out.
LS1 Boost OS V3 Here. For feature suggestions post in here Development Thread. Support future development ->Patreon.
Re: Using XDF from older OS (7603 on 6960)
The standard answer is NO ... The XDF must match the OsID!
However, sometimes similar oses partially align until the point of a newly inserted parameter, then from that point on the addresses will be off by the inserted parameter size ...
If I knew exactly what parameters you change, I would look them up and see if the addresses match each other.
-Enjoy
However, sometimes similar oses partially align until the point of a newly inserted parameter, then from that point on the addresses will be off by the inserted parameter size ...
If I knew exactly what parameters you change, I would look them up and see if the addresses match each other.
-Enjoy
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!
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!
Re: Using XDF from older OS (7603 on 6960)
I guess that is a bug with earlier version of firmware you have. Updating via sps to latest version for your bin should fix that bug.
Than you can use Universal patcher to add the e-fans mod.
viewtopic.php?f=42&t=7753
Than you can use Universal patcher to add the e-fans mod.
viewtopic.php?f=42&t=7753
Re: Using XDF from older OS (7603 on 6960)
What do you mean? I used SPS to try and update just the fuel calibration on 7603 but it forced me to update OS, too.kur4o wrote:I guess that is a bug with earlier version of firmware you have. Updating via sps to latest version for your bin should fix that bug.
Than you can use Universal patcher to add the e-fans mod.
viewtopic.php?f=42&t=7753
Also, made a few edits to 6960 using 7603 xdf and Universal Patcher corrected checksums. Good tool, thanks for your efforts.
Re: Using XDF from older OS (7603 on 6960)
You are headed for a soft bricking the pcm, with possible engine fireworks.
Sps won`t allow fuel segment update only, because fuel segment is tied to newer OS and will likely not work with older OS. Just update the file per vin and than retune with universal patcher.
Look at the screenshot.
Sps won`t allow fuel segment update only, because fuel segment is tied to newer OS and will likely not work with older OS. Just update the file per vin and than retune with universal patcher.
Look at the screenshot.
Re: Using XDF from older OS (7603 on 6960)
Ok, modified the stock 6960 bin with Universal Patcher.
What does it mean when the logs show a patch loaded (flex, lean cruise)? Stock is L59 flex.
Also, for grins, did a hex compare between the TunerPro with 7603 XDF bin of same OS (6960) and the Universal Patcher. I'm not skilled but the differences could be attributed to something I might have missed in setting parameter values between the two softwares. Seems close, but I am not even a beginner at this point.
What does it mean when the logs show a patch loaded (flex, lean cruise)? Stock is L59 flex.
Code: Select all
Reading Platform config: p01-p59-platform.xml [OK]
Loading file: p01-p59.xml [OK]
Importing tableseek...Seeking tables... (TableSeek-p01-p59.xml) Done
Importing TableSeek tables... [OK]
Importing DTC codes... [OK]
Loading file: C:\PCMSTUFF\Universal Patcher\Patches\E38VATS_OFF_v2.xmlpatch
Description: Disable VATS on e38 PCM
Incompatible patch, current configfile: p01-p59, patch configile: e38
Incompatible patch, current configfile: p01-p59, patch configile: e38
Incompatible patch, current configfile: p01-p59, patch configile: e38
Loading file: C:\PCMSTUFF\Universal Patcher\Patches\LC_defaultTables2.xmlpatch
Description: INstall stock lean cruise tables on your bin
Importing DTC codes... [OK]
Table: LC_Fuel_Delta
Patch is compatible
Loading file: C:\PCMSTUFF\Universal Patcher\Patches\p01-p59 NO VATS (PWM).xmlpatch
Description: Disable VATS
Importing DTC codes... [OK]
Table: VTD_Configuration-PWM
Loading file: C:\PCMSTUFF\Universal Patcher\Patches\p01-p59 NO VATS.xmlpatch
Description: Disable VATS
Importing DTC codes... [OK]
Table: VTD_Configuration
Patch is compatible
Loading file: C:\PCMSTUFF\Universal Patcher\Patches\p01-p59 VATS (PWM).xmlpatch
Description: Enable VATS
Importing DTC codes... [OK]
Table: VTD_Configuration-PWM
Loading file: C:\PCMSTUFF\Universal Patcher\Patches\p01-p59 VATS.xmlpatch
Description: Enable VATS
Importing DTC codes... [OK]
Table: VTD_Configuration
Patch is compatible
Loading file: C:\PCMSTUFF\Universal Patcher\Patches\P01-P59-flexfuel.xmlpatch
Description: This patch adds values to flexfuel tables, if OS have flexfuel support
Importing DTC codes... [OK]
Table: Crank_Afterstart_Time
Patch is compatible
Loading file: C:\PCMSTUFF\Universal Patcher\Patches\P59-LeanCruise.xmlpatch
Description: Lean cruise P59 2001 ->
Data found at address: 0002ADE6
Patch is compatible
Loading file: C:\PCMSTUFF\Universal Patcher\Patches\P59-Remove-LeanCruise.xmlpatch
Description: REMOVE Lean cruise P59 2001 ->
Patch is already applied, data found at: 0002ADE6
Saving to file: C:\12606960-UP.bin
Fixing Checksums:
OS
Checksum 1: 08FE [OK]
Checksum 2: 0F63 [Not saved]
EngineCal
Checksum 1: 609F => 5D6C [Fixed]
Checksum 2: 495D [Not saved]
EngineDiag
Checksum 1: 7840 [OK]
Checksum 2: 2196 [Not saved]
TransCal
Checksum 1: EFF7 [OK]
Checksum 2: 08BD [Not saved]
TransDiag
Checksum 1: E4E5 [OK]
Checksum 2: 7245 [Not saved]
Fuel
Checksum 1: F611 [OK]
Checksum 2: 85BB [Not saved]
System
Checksum 1: 2207 => E60F [Fixed]
Checksum 2: CADF [Not saved]
Speedometer
Checksum 1: 163E [OK]
Checksum 2: D6BB [Not saved]
Done.
Re: Using XDF from older OS (7603 on 6960)
mattbta,
After you upgraded to 12606960 and before you modified it, did you create a backup ??
And are you willing to share it ??
Thanks
-Enjoy
After you upgraded to 12606960 and before you modified it, did you create a backup ??
And are you willing to share it ??
Thanks
-Enjoy
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!
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!
Re: Using XDF from older OS (7603 on 6960)
Yes, I have unmodified bin files for both 7603 and 6960 from my Tahoe I can share. What is the preferred method to do so?Gampy wrote:mattbta,
After you upgraded to 12606960 and before you modified it, did you create a backup ??
And are you willing to share it ??
Thanks
-Enjoy
Re: Using XDF from older OS (7603 on 6960)
It's perfectly fine to attach them here ...
Thank you
-Enjoy
Thank you
-Enjoy
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!
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!