pcmhacking.net

XDF Archive

All files from random sources, and are unverified. Use at your own risk.

I have started documenting the xdf for what each one is for ive never used these codes myself as im from NZ so forgive me if they are wrong in certian places feel free to let me know and ill make changes.

just found a heap of us xdf's on the net enjoy ill be adding them slowly there are so many i think im about half way through lol

well i think thats all of them now its all i have anyway.bins is the next job theres heaps of them too

As far as the ECM used in USA I have all the XDF, ADX, bin files and some wiring diagrams all sorted by their ECM number at:
http://www.gearhead-efi.com/Fuel-Inject ... Tuner-Info

HTH!

Here is XDF I made for OS OS12212156 used mainly in 2002 LS1 PCMs.
I have checked most of the parameters and checksum calculation against EfiLive, so the attached XDF should be 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 unpack the .dll file and save it in the C:\My Documents\TunerPro Files\Plugins folder.

Thanks for contributing! It looks like thats my checksum plugin you've used there. Note that I later realised Tunerpro's native checksum was fine for calibration segments when setup as 2's compliment sum and the plugin is only needed for the code segment when you implement code patches as the area to sum is not contigous and the plugin skips over the bits that are not included.

antus wrote:Thanks for contributing! It looks like thats my checksum plugin you've used there. Note that I later realised Tunerpro's native checksum was fine for calibration segments when setup as 2's compliment sum and the plugin is only needed for the code segment when you implement code patches as the area to sum is not contigous and the plugin skips over the bits that are not included.

Yes, I know that for just calibration changes the 2'compliment checksums are enough, but added your plugin anyway for a good measure. The plan is to add more features in the future, I'm working on the disassembly to add boost capability. I have 5.3 LS motor that will be turbocharged and I'd rather learn something and try to program the patches than just pay for the software.

Updated version of 12212156 OS XDF:

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.