ADX XFD help needed

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

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

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.

Post from 84elky


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

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

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.

What file did you open? And with what program?

Quote:

---

Originally Posted by ralmo94

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.

Quote:

---

Originally Posted by MO LS Noobie

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.

Quote:

---

Originally Posted by Pulse_GTO

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

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

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

Quote:

---

Originally Posted by ralmo94

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

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.

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.

TunerPro will not save BIN because of checksum errors. UP cant load file with checksum errors because it is not saved. Looks like I picked the wrong year to give up drinking.

When you open the stock bin file in UP, You should be able to see what the OS is. We need to have that to be able to help you navigate.
If you post your bin up I could take a look at it for you.
I don't know where to direct you until we have the OS.
Once the OS is determined, fan temps should be an easy affair.

You can also skip the xdf part and edit the bin in Universal patcher.

Open the bin in tuner->file->open bin->switch to category view->3rd tab icon->scroll to Fan_Control category

Look for
ECT_Fan1_High_Threshold
ECT_Fan1_Low_Threshold
ECT_Fan2_High_Threshold
ECT_Fan2_Low_Threshold

Adjust the threshold to your specification, than save bin from file->save bin as.

Thanks, I'll try it. I have changed the OS to 12587603

I cannot seem to figure out how to post the link to the BINs.

Quote:

---

Originally Posted by MO LS Noobie

Thanks, I'll try it. I have changed the OS to 12587603

---

So are you using your existing tune, or starting over with a stock bin?

Quote:

---

Originally Posted by MO LS Noobie

I cannot seem to figure out how to post the link to the BINs.

---

if you click reply to thread, scroll down, you will see a button that says manage attachments.
then a pop up will appear and you can add attachments.

Uploaded to Attachment 17644 Initial Tune, Sensitive throttle, speedo inaccurate, fans run all times

Attachment 17643 OS change, now runs rich

Was the other tune dialed in?
Universal Patcher opened both of them?
I can probably help you dial speedo in.
What gear ratio and tire hight.
And how far is it off?

Quote:

---

Originally Posted by ralmo94

Was the other tune dialed in? On initial tune, Fuel trims were pretty close, slight pinging when cold. Sensitive throttle, speedo inaccurate, fans run all times
Universal Patcher opened both of them? Yes, only had roblems when I tried to edit them myself
I can probably help you dial speedo in. What gear ratio and tire hight. And how far is it off?

---

After OS change, Speedo is pretty close now. Runs rich after OS change, about 20%, dies on cold start. Pings badly cold. Throttle modulation is very much improved.

1 Was the other tune dialed in? On initial tune, Fuel trims were pretty close, slight pinging when cold. Sensitive throttle, speedo inaccurate, fans run all times

2 Universal Patcher opened both of them? Yes, only had problems when I tried to edit them myself

3 I can probably help you dial speedo in. What gear ratio and tire hight. And how far is it off? After OS change, Speedo is pretty close now. Runs rich after OS change, about 20%, dies on cold start. Pings badly cold. Throttle modulation is very much improved.

So if you want to move forward with the new bin and new OS, you should copy the injector settings from the first file, to reflect the 30lb injectors
in universal Patcher, you cAn open both bins at the same time even though the os is different, and switch between bin A and bin B.
I be-leave the table you want to copy over is injector_slope*04
The first bin has values that are 4 something and the new bin has values of 3 something.
this should get you close

Thank you very much for your time and concern. I do not seem to be able to make even minor changes becuse of checksum errors. I have tried opening two BINs but cannot even figure that out. I must wait for for my tuner to have time to help me, I guess I need someone to hold my hand. I appologize for my ignorance.

Did you try universal patcher? That's what I would use. Not tuner pro.
Tuner pro would need a different xdf for each OS.

Bear with me, as I try it again.
1 Open TunerPro program
2 Open XDF file (definitions?)
3 Open BIN
4 Make changes
5 Save under new file name
Problem is I cannot save because of checksum errors

Just saw this reply after I already responded. I"ll try UPath again,

In the tuner screen, File>open Bin Select a bin. Then repeat for the 2nd bin. you will now have bin A and bin B in UP
Click the 3rd tab then type "inj" in the search
then when you click on A or B you can see the values from the selected bin, and make changes
You can also view both at the same time

Maybe picture will help

That does help. thank you. Just got a modified BIN from my Tuner. Attached the file. I will try it later this afternoon and reporty back

This one is real close. Lowered spark advance and entered the correct injectors. Excellent place to start.

Quote:

---

Originally Posted by MO LS Noobie

This one is real close. Lowered spark advance and entered the correct injectors. Excellent place to start.

---

Glad to hear!