Results 1 to 15 of 37

Thread: 2002 OS 12212156 .xdf

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Fuel Injected!
    Join Date
    Jan 2012
    Location
    Poland
    Posts
    147

    2002 OS 12212156 .xdf

    Hello everyone! Some time ago i've been asking if there was any progress on 12212156 OS .xdf files. As apparently there have been none, I went ahead and made them myself.

    [EDIT]
    I have fixed the checksum issue in beta xdf version reported in below posts, and reworked the definitions into a single, complete XDF file. Also added some new parameters.
    I have checked most of the parameters against EfiLive, also checksum calculation, so the attached XDF should be finally safe to use. Hovewer, I take no responsibility if something goes wrong and you brick your PCM!

    Naming convention matches Efilive for easy cross reference of parameters. It's best to use Parameter Category view for this XDF.

    You can select between metric and imperial units by selecting level view in Visibility Toolbar:
    Show Only Level 1 - Metric units,
    Show Only Level 2 - Imperial units.
    In version 1, only vehicle speed is selectable between KPH/MPH with above option.

    For this XDF to properly calculate checksums, you must first download attached "512Kb PCM OS Checksum Plugin.zip" file, unpack the .dll file and save it in the C:\My Documents\TunerPro Files\Plugins folder.
    The OS checksum plugin was written by Antus.

    Don't be scared by bricked PCMs reported below - the initial release issues have all been fixed!

    Version 2 changes:
    - Fixed wrong conversion for some Speedometer parameters.

    Version 3 changes:
    - Fixed wrong labels in C6001 and C6002,
    - Added Idle Learing parameters,
    - Added Hardware and Software Knock Sensor parameters,
    - Added Oil Pressure parameters,
    - Fixed End of Injection Timing calculations,
    - Other minor fixes and clean-ups.

    Version 4 changes:
    New categories, better parameter descriptions, more organized category view,
    Added new parameters:
    - Cranking VE Baro Multiplier and Calibration Temperature,
    - Commanded Fuel For Extended Cranking,
    - MAF Airmass Filter,
    - Dynamic Airflow parameters,
    - VE Correction parameters,
    - Priming Pulses parameters,
    - PE enable parameters,
    - LTFT deadband, update rate, and filters,
    - Idle STFT parameters,
    - Torque Management parameters,
    - Coil Dwell Time parameters,
    - Shift Light parameters

    Version 5 changes:
    - fixed issues with B4610 and B4359 from post #19,
    - some minor category and clean-up changes

    Version 6 changes:
    - update for 2020, added a LOT of parameters!
    - Class II messaging parameters added
    - A/C control parameters
    - Oil level and life parameters
    and many more!
    Attached Files Attached Files
    Last edited by dzidaV8; 08-06-2020 at 02:23 PM. Reason: New XDF files

  2. #2
    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!!!

  3. #3
    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.

  4. #4
    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.

  5. #5
    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.

  6. #6
    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

  7. #7
    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.

  8. #8
    Carb and Points!
    Join Date
    May 2020
    Age
    44
    Posts
    9
    Thank you for your time dzidaV8!

  9. #9
    Carb and Points!
    Join Date
    Jan 2021
    Posts
    1
    Is there a way to get this xdf file in a bin format? Yeah

  10. #10
    Electronic Ignition! 30bird's Avatar
    Join Date
    Apr 2021
    Location
    Puckerbrush KS
    Posts
    17
    dzidaV8
    Man thank you so much for the work you did on those files I was thinking I had to learn Mandarin reading the hex from my OS 9373372 bin
    By the way
    隒̀碬̀粬̀肬̀ translated The other products are available in the following markets
    am going to attempt to OS flash it as soon as I am comfortable with the process.
    Last edited by 30bird; 04-30-2021 at 09:33 PM.

  11. #11
    Electronic Ignition! 30bird's Avatar
    Join Date
    Apr 2021
    Location
    Puckerbrush KS
    Posts
    17
    Quote Originally Posted by Bigtoyz97 View Post
    Is there a way to get this xdf file in a bin format? Yeah
    Don't take this wrong, I am trying to help... Bigtoy97
    My understanding is that the .bin file is the raw hexadecimal data containing the operating system and all the settings from an ECM in that one compact file.
    The .xdf file is like a key/map of the data in the bin file so you can edit or change things that the computer monitors and controls.
    Then you can save the edited bin file and flash it to your ECM.
    But of course it is not just super simple, because there are so many easy ways you can do this wrong,
    edit some thing wrong, or use the wrong bin, XDF, hardware files,
    or the write is interrupted during the flash you can easily "brick" your vehicles computer
    (Brick is a computer nerd term meaning your computer would only be useful as a brick)
    It seems by your question that you may need to do some more research (or I do) not trying to troll you.
    I am probably only a few posts ahead of where you are.
    Some one please correct me if I am wrong.

  12. #12
    Administrator
    Join Date
    May 2011
    Location
    Lakes Region, NH
    Age
    54
    Posts
    3,844
    30bird, you are correct.

    Generally, a .bin file refers to the calibration, the calibration and code file read from the vehicle computer, saved in a binary format.

    An xdf file is a definition file that tells the tuning software Tunerpro how to represent the information in the bin file in (somewhat) human readable terms.

Similar Threads

  1. Replies: 16
    Last Post: 2 Weeks Ago, 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
  •