ADX XFD help needed

[MO LS Noobie]

Hi, new to LS swaps but not OEM systems, been professional mechanic for 40 years.

Recently installed 05 LQ9 DBW in my 99 Denali 4X4 4L60E. Fresh bearings, rings, Summit Stage 1 cam, LS6 valve springs, 2010 truck intake w/35 lb/hr injectors, initial tune by Brendan (LT1Swap.com). Engine really woke the old girl up. Trying to do final tuning on my own. Using LS Droid, and TunerPro RT. PCM out of 05 Silverado for the Analog A/C signal SVC# 12589462. OS# 12592618, and BIN 12585950. TunerPro needs ADX or XFD file to load BIN (I think). Still trying to sort it all out.

As I understand it, the Operating System is the firmware with the vehicle specifics, the BIN is the binary code of the actual operating parameters, and the Service # is the hardware of the PCM. I think tha ADX files interpret the BIN files so we can work on (modify) them. Please correct me if I am misinformed.

I have the BIN, so all I need is the correct ADX or XFD file to make adjustments in TunerPro? HELP

I would really appreciate any help/advice/tricks, etc.
Jeff

[ralmo94]

yes the bin is the file on the pcm. It's in HEX, engineering computer language.
The XDF decodes the file into tables, scalers, and flags, so we can make adjustments.
So to make changes you need an XDF.
The ADX is for deciphering the data stream to get a datalog.

The XDF is based on the operating system number

You might check out universal patcher to see if it will read your bin.
It's a relatively new tool for LS PCM's that can create an XDF for tunnerpro, or be used independent for editing flashing and datalogging.

www.universalpatcher.net

[ralmo94]

When you begin to look at things with an XDF, there are a lot of things going on and can look intimidating.
I would start with getting the correct injector settings if you have them.
84Elky wrote a good writeup on injector settings.

After that to dial the fuel in, you need to work with the VE table.
But to do so we have to set the code for the MAF, so it will fail it and run in speed density.
Easiest way is to change the frequency high that is reported as a bad MAF sensor to a low value around 1 he's
Make sure the corresponding code is set to fault on 1st error. DON NOT change to NO ERROR REPORTED.
After VE table is dialed in within 5% you can reenable the MAF
Then make changes to the MAF table.
Before you make any changes to your bin, what I recommend is to save file as, then give it a different name.
When you are done tunnerpro will Create a text file that documents all the changes you made.
If you do this evertime it's easy to keep track of what your last bin was Incase you mess something up it's easier than trying to undo what you did.

[ralmo94]

Post from 84elky


http://www.gearhead-efi.com/Fuel-Inj...light=injector

[MO LS Noobie]

Thank you ralmo94. I'll check out those links.

[MO LS Noobie]

Opened file, no idea what I am looing at. NOT a programmer or coder. Do understand the items such as VE, PW, LT and ST Trim, ECT etc. Sorry for the beginner questions, searched archives, did not find the answers.

[ralmo94]

What file did you open? And with what program?

[MO LS Noobie]

What file did you open? And with what program?

So I need the XDF files to edit in TunerPro. I opened www.universalpatcher.net and have no idea what I am looking at. Is there a tutorial? As far as I know 12589462 and 12589463 are the same, but 462 uses analog a/c request, where 463 uses serial data. Is it possible they use the same XDF files? They both show the same BIN 12585950.

[Pulse_GTO]

So I need the XDF files to edit in TunerPro. I opened www.universalpatcher.net and have no idea what I am looking at. Is there a tutorial? As far as I know 12589462 and 12589463 are the same, but 462 uses analog a/c request, where 463 uses serial data. Is it possible they use the same XDF files? They both show the same BIN 12585950.

The two part numbers you are listing are for the hardware. It's the operating system number that needs to match the XDF.

[MO LS Noobie]

The two part numbers you are listing are for the hardware. It's the operating system number that needs to match the XDF.

Thanks Pulse_GTO. Operating System is the BIN? Both have a BIN 12585950.bin. So I need to match the BIN to an XDF?
Where do I get that? Sorry for my ignorance. Jeff

[ralmo94]

The OS is stored in the BIN.
If you open it with an XDF. In tuner pro, there should be a segment that displays the OS. IF IT IS THE CORRECT ONE.

Universal patcher, look for the file called launcher

[ralmo94]

See this thread I posted showing how to get an XDF from Universal Patcher
http://www.gearhead-efi.com/Fuel-Inj...3016#post93016

[MO LS Noobie]

See this thread I posted showing how to get an XDF from Universal Patcher
http://www.gearhead-efi.com/Fuel-Inj...3016#post93016

Thank you ralmo 94, I think that is what I needed

[MO LS Noobie]

Obviously in way over my head. Was able to open UL and got generated XDF x–É Opened it in TP and get more info than I know what to do with. The tutorial links don't seem to open properly. Just trying to adjust fan temperatures, try to save new files and get checksum errors. Thanks for helping.

[ralmo94]

Universal patcher is supposed to fix checksum errors.
In tuner pro, you can go to tools at the top, parameter finder
And search for the settings you need to adjust.
What OS did UP say your bin is?
If it is an OS somebody else has already created an XDF for it will be a lot easier to navigate, and there will be a checksum file for it.