Results 1 to 15 of 37

Thread: 2002 OS 12212156 .xdf

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Electronic Ignition!
    Join Date
    Sep 2014
    Posts
    13
    Incredible work! I'm trying to understand how to lookup calibration locations to hopefully contribute to these XDF. Not easy learning for a guy like me with no hardware background.
    Saw some more calibration options were added to these collections of 12212156 XDF that seem to be missing in the 12202088 XDF (thanks for the fuel gauge calibration!!). There are a few more I'm hoping to find. (Coil dwell settings? End of injection timing?)
    I know you consider this a beta, and you've warned about the transmission calibrations. I'll be trying these XDF for my "LS" project this winter (24x Corvette LT1 with 4L60E). I'll be taking a closer look through these XDF in the next few months.
    Wow, dzidaV8 - incredible work!!!

  2. #2
    Carb and Points!
    Join Date
    Nov 2014
    Posts
    8
    Be careful with these, I just bricked two 411 pcm's last week with what appears to be checksum errors. I will no longer be using these XDFs.

  3. #3
    Fuel Injected!
    Join Date
    Jan 2012
    Location
    Poland
    Posts
    147
    I'm sorry to hear that you bricked your PCMs, I tested only a few parameters on a real PCM, but the checksums appeared to calculate correctly. Please send the original and modified bins along with a change log to e-mail address that I sent you so I could see where the problem is.

    To be sure the checksums are correct before you flash, you can open the modified bin in free EFIlive tuner and check.
    Last edited by dzidaV8; 10-20-2016 at 06:36 PM.

  4. #4
    Carb and Points!
    Join Date
    Nov 2014
    Posts
    8
    Thanks I'll give that a try next time. I was able to lift the chip's and recover the PCMs last week. I'll try and get your the BINs I flashed to them shortly.

  5. #5
    Fuel Injected! babywag's Avatar
    Join Date
    Dec 2011
    Posts
    219
    Quote Originally Posted by dzidaV8 View Post
    I'm sorry to hear that you bricked your PCMs, I tested only a few parameters on a real PCM, but the checksums appeared to calculate correctly. Please send the original and modified bins along with a change log to e-mail address that I sent you so I could see where the problem is.To be sure the checksums are correct before you flash, you can open the modified bin in free EFIlive tuner and check.
    I also tried using these, just a VATS change results in an incorrect checksum.
    Tony

    '88 Jeep Grand Wagoneer (aka Babywag)
    '67 Jeep J3000
    '07 Dodge Magnum SRT8

  6. #6
    Fuel Injected!
    Join Date
    Jun 2014
    Posts
    229
    Quote Originally Posted by babywag View Post
    I also tried using these, just a VATS change results in an incorrect checksum.
    There are 8 segments of code in the PCM, and 8 related Checksums that must be calculated. The 7 calibration segments have straight forward Checksum calculations.

    The Operating System (OS) uses a unique Checksum calculation. It sums the entire areas before, and after, the 7 calibration segments (it skips over these), and also excludes the last 16 bit placeholder at the very end. The native Tunerpro Checksum plug-in can't properly calculate the OS Checksum.

    There is an LS1 Checksum plug-in available for Tunerpro on the Delcohacking website that will calculate the OS Checksum, but it will only work with 512 Kb PCMs.

    Attached below is a link.

    https://pcmhacking.net/forums/viewtopic.php?f=3&t=3845
    Last edited by LRT; 11-26-2016 at 06:12 AM.

  7. #7
    Fuel Injected!
    Join Date
    Jun 2014
    Posts
    229
    Can't seem to fix the spacing in the above post ... makes it a bit hard to read.


    *** had to switch from the WYSISYG editor, to the standard editor ***
    Last edited by LRT; 11-20-2016 at 11:58 PM.

  8. #8
    Fuel Injected! babywag's Avatar
    Join Date
    Dec 2011
    Posts
    219
    Quote Originally Posted by LRT View Post
    There are 8 segments of code in the PCM, and 8 related Checksums that must be calculated. The 7 calibration segments have straight forward Checksum calculations. The Operating System (OS) uses a unique Checksum calculation. It sums the entire areas before, and after, the 7 calibration segments (it skips over these), and also excludes the last 16 bit placeholder at the very end. The native Tunerpro Checksum plug-in can't properly calculate the OS Checksum. There is an LS1 Checksum plug-in available for Tunerpro on the Delcohacking website that will calculate the OS Checksum, but it will only work with 512 Kb PCMs, and is accurate for most (but not all) operating systems. Attached below is a link. https://pcmhacking.net/forums/viewtopic.php?f=3&t=3845
    Dimented's .xdf did correctly calculate (fix) the bad checksum for system section, even though it isn't correct for 12212156 os.
    I don't have the plugin installed. I did not look @ the .xdf difference on how the checksum is calculated.

    I played around some more and also got an incorrect checksum when trying to change some transmission items.
    Right now as it is the .xdf(s) will likely brick the pcm if it is used.
    Last edited by babywag; 11-20-2016 at 05:19 AM.
    Tony

    '88 Jeep Grand Wagoneer (aka Babywag)
    '67 Jeep J3000
    '07 Dodge Magnum SRT8

  9. #9
    Fuel Injected!
    Join Date
    Jun 2014
    Posts
    229
    Trying to use DIY tuning software is a little dangerous, unless you are an advanced user.

    While I applaud the effort put forth by dzidaV8 in working on the XDF for the 12212156 OS, there are errors and omissions in the current draft version. There is no Checksum in the Transmission Calibration XDF. There is a Checksum in the Transmission Options XDF.

    So depending on which of these you were using, that would explain one of the checksum issues that you experienced. The OS Checksum is very important to have in place. Sometimes a read or write will change the code ever so slightly, which requires that the checksum to be accurately recalculated.
    Last edited by LRT; 11-20-2016 at 11:58 PM.

Similar Threads

  1. Replies: 16
    Last Post: 03-05-2024, 04:17 AM
  2. Replies: 8
    Last Post: 07-18-2022, 06:03 PM
  3. Replies: 5
    Last Post: 07-07-2016, 11:05 PM
  4. Replies: 5
    Last Post: 09-12-2015, 07:42 PM
  5. 2002 blazer
    By mdj in forum TunerPro OBDII
    Replies: 1
    Last Post: 03-28-2013, 10:19 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •