NEWB needs a little help

Mario65

Hotrodicus Supersonicus
I have the truck running pretty good . I have an ostrich and aldl cable, data master, tuner pro. I have a bin I want to make some minor changes to and I have spent some serious time loooking at this bin on tuner pro and I cant see a thing that I can change. I think I need a xdf file also. As you can tell I havent got a clue. I have spent some time reading and I think its best if I get someone to steer me to a basic info page so I can get the changes made.

I have figured out how to upload and download the bin to and from ostrich but thats it.

I look at the code 59 page and it looks greek. I read the tunerpro help and I cant get past the load an xdf file.

Help?
I just want to figure out how to upload a bin to tunerpro and make some changes and then upload it to the ostrich. I know I will want to know more later but I cant even get that going.

I am not exactly mentally challenged but I am beginning to wonder now.

Please?
mario
 

bezerk

New member
Re: NEWB needs a little help

that xdf file doesn't work. atleast i had a problem getting it to work, so i used one from tooky
 

JSM

Active member
Re: NEWB needs a little help

What do you mean didn't work? First that XDF is only going to work properly with a code59 bin. So if you have an ultimate bin or stock it won't work exactly right.

What bin are you starting with Mario?
 

Mario65

Hotrodicus Supersonicus
Re: NEWB needs a little help

Man!
Thanks for all the repsonses.
I dont have an xdf file. I really don't know how it even relates to the BIN.
I am using MAV87's 75# code 59 bin.
Mav has the idle in gear too lean for me and he also has the knock retard disabled. Simple stuff I want to be able to do.
I have a wideband.

thanks

mario
 

Aeroking

e.i.
Re: NEWB needs a little help

the XDF isolates certain parts of the BIN file, so that you can modify them in Tunerpro. Without it, you have no way of altering the BIN.
 

Mario65

Hotrodicus Supersonicus
Re: NEWB needs a little help

the XDF isolates certain parts of the BIN file, so that you can modify them in Tunerpro. Without it, you have no way of altering the BIN.

Ok so XDF is just a file that allows you to alter the BIN per the code like 58 vs 59. So I upload the bin I am working on and then I download the code59 xdf and use it in tunerpro with the bin to alter the bin?
 

JSM

Active member
Re: NEWB needs a little help

XDF is a road map for tunerpro so tunerpro can display the "chip" in information you can understand. Think of it as a translater and your traveling in France, and you don't speak french.

Not do you any good to have a french translator in spain (code59 -vs- code58 -vs- one for a chevy citation).

Gotta have the right XDF in order to understand the info, when you send the bin back to the truck it already knows how to read the data, so the truck doesn't need the XDF.
 

sytyguy

Moderated User
Re: NEWB needs a little help

Here's a quick little screen capture I just did. Sorry for the crappy video/editing....wanted to get this up quick. Also, you'll notice that I loaded a $58 xdf in the video.....only bin I had handy was an old $58 one of mine.

Original video - Download
Video with explanations - Download

Please right-click and save as.....don't stream.
 

turbodig

Active member
Re: NEWB needs a little help

Beating the explanation to death....


The .bin is the actual data that the ECM needs... including the software that tells the engine computer what to do, as well as the actual data telling how much fuel, timing, etc to apply.

Code $59 is different software... Sorta like running Windows XP on your PC, vs. Windows 98.
$58 is the GM internal designation for the stock code, as used in our trucks and Turbo Sunbirds.

The .xdf is the road map that tells Tunerpro where to find the various stuff (fuel tables, timing tables, etc) in the .bin file. Tunerpro works with lots of different vehicles (Syty to Subie and everything in between), so there are *many* different .xdf files out there. Code59 offers 2 xdf files, a "regular" and a "simple". The simple file is a good one to start with, since it doesn't have as much stuff defined in it, and is a bit easier to read. Either one will work with the current released code59 bins.

An .ads file is the file that tells Tunerpro how to speak to the ALDL link for retrieving engine data, which is specific to each vehicle too. You'll find lots of different .ads files for different vehicles as well.

So, to get started, you'll need a:

.bin file (You have that from Mav)
.xdf file (Either the 1.3 regular or the 1.0 simple)
.ads file (the 1.1 .ads file)

Best place to get these, is here:
http://www.code59.org/forum/forum.asp?FORUM_ID=54


And, a general reminder for new folks... it's part of the license agreement for using code59 to post your bins back to the code59 community, once you get your setup dialed in where you like it. Sharing is good.
 

Mario65

Hotrodicus Supersonicus
Re: NEWB needs a little help

Beating the explanation to death....


The .bin is the actual data that the ECM needs... including the software that tells the engine computer what to do, as well as the actual data telling how much fuel, timing, etc to apply.

Code $59 is different software... Sorta like running Windows XP on your PC, vs. Windows 98.
$58 is the GM internal designation for the stock code, as used in our trucks and Turbo Sunbirds.

The .xdf is the road map that tells Tunerpro where to find the various stuff (fuel tables, timing tables, etc) in the .bin file. Tunerpro works with lots of different vehicles (Syty to Subie and everything in between), so there are *many* different .xdf files out there. Code59 offers 2 xdf files, a "regular" and a "simple". The simple file is a good one to start with, since it doesn't have as much stuff defined in it, and is a bit easier to read. Either one will work with the current released code59 bins.

An .ads file is the file that tells Tunerpro how to speak to the ALDL link for retrieving engine data, which is specific to each vehicle too. You'll find lots of different .ads files for different vehicles as well.

So, to get started, you'll need a:

.bin file (You have that from Mav)
.xdf file (Either the 1.3 regular or the 1.0 simple)
.ads file (the 1.1 .ads file)

Best place to get these, is here:
http://www.code59.org/forum/forum.asp?FORUM_ID=54


And, a general reminder for new folks... it's part of the license agreement for using code59 to post your bins back to the code59 community, once you get your setup dialed in where you like it. Sharing is good.


I know it sounds simple but then its an all new world for me. I have looked at some of this stuff and I feel really encouraged about the video and the information here. I really I think I should have this nailed today.

As far as MAV's bin its a great running bin but it needs a little tweeking for my truck and it really needs the knock retard reactivated for the normal guy like myself.

There is no question I will post to that code 59 75# thread what I did and why and a link to my my setup/mods. With the 2 or 3 changes I really think its going to be the best 75# bin out there to start from.

Thanks for the patience and all the info all of you have provided so far.

I'll post once I open it up.

thanks
 

JSM

Active member
Re: NEWB needs a little help

You won't find any code59 member suggest any bin posted is the "hot" ticket and no changes needed. They are all base information to hopefully get you close, along with the tools and advice to let you dial it in to your specific truck.

We all started thinking a chip was something you ate with salsa so don't feel bad.
 

sytyguy

Moderated User
Re: NEWB needs a little help

The knock retard is a simple one. Here's how:

Once you have the bin and the xdf loaded, scroll down under the spark section of the constants/scalars until you start seeing the ESC stuff. Look for 3 main constants:

KESCOOL
KRPMKNOB
KRETARDM

KESCOOL is the minimum coolant temp that the ECM has to see before it starts reading knock data and adjusting for it.
KRPMKNOB is the minimum engine rpm that the ECM has to see before it starts reading knock data and adjusting for it.
KRETARDM is the maximum amount of knock retard that the ECM will compensate for.

What this all means is that if your value in KESCOOL is too high and the engine temp never reached it, you'll have a tune with no knock retard. Same applies for KRPMKNOB in respect to engine rpm. And if you have too low of a value in KRETARDM, the ECM will only help with that amount (e.g. 10 degrees of actual knock and only 4 degrees allowed in KRETARDM will mean there's still knock that the ECM can't do anything about.)

Stock for these constants are:

KESCOOL - 24.5 degC
KRPMKNOB - 737 RPM
KRETARDM - 12.66

It's common practice to bump KRETARDM up to the max (around 18 degrees).
 

bezerk

New member
Re: NEWB needs a little help

What do you mean didn't work? First that XDF is only going to work properly with a code59 bin. So if you have an ultimate bin or stock it won't work exactly right.

What bin are you starting with Mario?

i know that, i used the $58 file and the bins. i thought i got it from turbodig it's site with a link at code 59.org. might have been the 59 file with a 58 name.
 

Mario65

Hotrodicus Supersonicus
Re: NEWB needs a little help

I got it working

thanks

Which one is the one to add more fuel at a stop in gear?

Any recommended changes in increment to move from 15.5 to 13.8 AFR or so? I am using xdf code 59 1.3
 

sytyguy

Moderated User
Re: NEWB needs a little help

I got it working

thanks

Which one is the one to add more fuel at a stop in gear?

Any recommended changes in increment to move from 15.5 to 13.8 AFR or so?

F29

kPa range - 40-70
RPM range - 800-1200

Bump value 2 pts at a time and verify WB readings. Doing this while emulating makes it easy.

My advice is to set idle rpm (3 tables - F13, F18, F19 - Batt Volt, Idle in gear, Idle in P/N, respectively) to desired rpm.....iron out timing in F1, F2, F3 (F1 is usually the one that needs the most work).....then start working out the fueling. Remember to check for any nasty fueling transitions that might occur when going from P/N to D (with lights on, A/C on, wheel turn full lock, etc....). Put it under a heavy load, shift into D, and make sure the AFRs look good with no stalling. If stalling or heavy stumble, work on F29. If problems occur when going from D to P/N, work on F29C.

Idle is easy, but teaches you tons how the truck reacts to tune changes.....which will be VERY helpful later on.
 
Last edited:
Top