Hey everyone whats up? Sorry to double post, i didnt know where this would best fit. but anyways, feel free to delete one of the posts where it doesnt belong

I am going to start doing some tuning with a buddy and need to know which bin file to start out as a base map with.

We will be using TunePro RT with an ostrich emulator, lc-1 wideband and a chip burner. I am not sure yet what else will be needed to start tuning. Do you know what will be needed for datalogging with TunerPro RT?

Im not sure of my ecm code yet. I will check that tomorrow, but if need be, i will swap to a 227 or 230. ecm is from a 91 tpi setup.

but anyways, i have loaded up tunerpro RT and the only .bin files are "apyp" and "arap"

i know neither of those is a .bin file for my setup that will work well enough as a basemap, so does anybody know which .bin file will suffice as a good basemap for a 5.7L TPI? My motor is no longer a tpi setup, i removed it and installed a holley stealth ram.

thanks everyone

also, my car is a manual. setup is in my sig

 

You need to start reading the stickies, and read the stickies some more and then some more after that. It will hurt your eyes at first but eventually something will seep through and trigger a light bulb in your head.

Start making small changes at first with constants and then work your way up to changing stuff that will affect the way the engine will perform, like SA tables and the VE tables.

If you do not know what a SA table and VE table is, go back and look through the stickies until you find the abbreviations.

Your setup should be a 730 ECM, which I think is the $8D XDF (mask).

Most of the bins are available at Moates website, and I would look there first. Do a search and try to find a bin for your automatic or manual setup. You need an ALDL cable to datalog and a laptop.

I use an old Compaq 1750 with a 500mhz processor for datalogging and chip burning so it doesnt have to be state of the art.

I would start looking for the spark tables and fueling of a LT1 setup, since yours is more like an LT1 intake than a TPI intake.

 

big help man, i appreciate it! Ill check out moates website for some .bin files. I didnt know they had a bin library. I have been looking for one all night. I thought they were just a supplier of their tuning/chipping goods, i had no idea they were a forum as well.

you sound pretty knowledgable. Have you ever used tunerpro rt?

 

Since you have a programmer you can pull the bin off the stock MEMCAL, with the use of an adaptor (HDR1 from moates.net) or make your own, I've seen a few different ideas on making these adaptors.

Save as some uniaque bin name, usually what the BCC is written on the EPROM is a good name. You can load this bin to TP RT and then find out exactly what mask it is, by looking at it in hex. Under "tools > Advanced > Hex Editor" You can also use the short cut ctrl+H. Your programmer software should also have a place to view the hex, sometimes refered to as a "buffer".

Look at the first line, bit 8, which is 9 places over from the left (hex starts at 00 ), should be 8D. You can then use the correct xdf (mask) to view and make changes to the bin.

 

Use it all the time, Moates and Magnus (Tunerpro) are both members of this site and are both smart cookies.

Tunerpro is an excellent program and I highly recommend getting used to it, it doesnt take much adjustment if you know how to use and modify fields in Excel.

I know there are other packages out there but I personally have a G1 in my toy and a G3 in my daily driver, and use a Burn1 to do chip burning. If I had the cash I would get an Ostrich too, even a used one.

 

So why is the mask important? What happens if the wrong mask is used?

 

It's VERY important because the mask (xdf, ecu, etc.) is basically the road map to the bin, and will display the values in the bin correctly. Not all bins use the same locations for the tables and constants, etc. There are a few commonly used locations, like 0x08 for the mask bit, and a few others like the checksum.

Using the wrong xdf, will not display the items correctly and so when you think you're adjusting one thing, you'll actually be chaging something else.

 

Alright, so I have another question now. The mask is important for the way the car runs...... I understand that now. The $8D mask is for 90-92 tpi camaros/firebirds using the 1227730 ecm correct?

Well right now I have an ECM from Arizona tpi, and they put a chip in it based on the specs I gave them on my setup. This ECM doesn't have a code on the casing that has anything close to 1227730, so I don't know what type of ECM it is or what program they used for the chip. This was also the chip I had for my tpi setup.....I have now swapped to a stealth ram, but I have done nothing to modify the tune.

My question is, what mask do I need to run for the stealth ram? Still the $8d even though it is for tpi? I know it will need to have a closer fuel and ignition table from an ls1 bin, but what's the easiest way to go about doing that? Can I simply upload the $8D xdf definition on tp rt and then open up an aujp bin and simply copy/paste maps from a ls1?

I also need to know what bin to start tuning with for a 350 with stealth ram installed.....an aujp? This is based on that I have to start from scratch.

Last question is where can I/how do I get a $8d definition into tp rt? The only one that comes with the program is for an 89 model year ($6e). I know tp's website has a link to the $6D definition but when I click on it, it is just a page of code. How do I download it and be able to open it in tp rt by simply clicking on xdf -> open bin definition?

Sorry for all of the questions, I just need some answers.

Thanks

 

The ECM or car doesn't care about the xdf.

The xdf is important to decipher the bin and make sure that when you are adjusting the VE table, you really are adjusting the VE table. Different bins that use different masks can use different locations within the bin for similar information. Basically the order or the organization of the bits and bytes in the bin can change and using the proper matching xdf (mask) ensures that you are adjusting what you think you're adjusting.

AUJP is $8D, so that would be a matching xdf to the bin. I'm not sure if it was a typo at the end of your post or not, but $6D can not be used in place of $8D. To download the file, if it just opens the file in note pad when you click on it, is to right click and then "save target as".

I bet your ECM starts with a 161 number, which would be a newer or replacement version of another ECM, such as the '7730.

Some code can be swapped between different ECMs.
I.E. $58/$59 can be used in the '7749, '7730, '7727.

If I were in your shoes I would use $8D (should be what you are running currently), but I would look into using S_AUJP, which is AUJP, that has been modified to have WBO2 sensor input, and expanded upper VE tables, along with a few other things I don't recall right now.

The code really doesn't care what the engine has for parts, just as long as the proper inputs and outputs are used to satisfy the ECM.

As an example I'm using $59, which is a modified version of $58, that was originally used on the 4.3 turbo in Syclones and Typhoons along with the 2.0L turbo in the Sunbirds. I am using this code on a 2.8L Nissan inline 6 cylinder, in a 1973 Datsun 240Z, about as far from what it was originally intended to be used on as can be.
Using AUJP or S_AUJP on your Stealth Ram V8 should already be close.

 

Yeah it was a typo.....I meant $8d

Where can I get the s_aujp bin? And thanks for claryfying the xdf. I now understand it!!

And when you say it should be close, you mean that the fuel and spark tables will need to changed only slightly if not at all?

So just to clarify......once I get this s_aujp bin, I can open the $8D definition then open the s_aujp bin in tuner-pro and then start tuning?

 

You can download the S_AUJP bin and supporting files from moates.net. Look on the main page and then near the bottom of the navigation menu should be "file uploads and downloads" or something like that, sign it, the name and pass word are provided, and then browse the different folders to find it.

S_AUJP v4 is the lastest and will be in a zip file, that will come with the matching xdf and ads files.

You should be able to figure out the reast to open each file in TP RT.

 

Yes, and the Mask as was explained to me by Vader:

"The “mask” file is simply an interpreter of the memory locations within the PROM. Delco Electronics programmed the older ECM for the 1985 models with one architecture for memory addresses. When the newer ECM was used in 1986 (and subsequently, through 1989) there was more memory available for program, and thus more capability. For the first year, a given set of memory locations was used to assign various functions. For whatever reason (likely what was presumed as more efficient processing) the memory allocation was altered for the 1987 version. In the 1988-89 versions, a different architecture was used, and was likely considered more suitable for the order in which functions were processed and the I/O was updated.

Therefore, the 1986 models use one memory offset and resultant hex locations for the various functions. That code offset is commonly referred to as “32" or, as in hexadecimal, “$32" Mask ID Code. For the 1987 models, the address locations are encoded by “32B” or in hex, “$32B” Mask ID. For 1988 and 1989, the Mask ID is “6E” (“$6E” in hex) and is the last iteration for the original MAF equipped engines."

You are going to have to use the $8D program or an equivalent Speed Density program. A $6E mask is for Mass Air Flow systems and would be incompatible.

Start with a BIN that you feel comfortable with that will run comfortably on a T5 manual setup. Since you have a T56 that would better suit you since it will probably run better than a tune that setup for autos. I have done mostly MAF tuning so the ones with SD tunes will probably have better information. I thinkthe AUJP is for automatics. I have had good luck with the AXXD 305 T5 bin.

Making the Stealth Ram run nice, well, thats getting into advanced stuff in tuning. Tuning the VE tables is something you are going to have to learn by searching, reading and rereading the various posts about it and also the stickies.

After you read it to death, eventually a light will start to blink in your mind about why you are changing the different fields a certain amount and to achieve what purpose.

Go to Moate's website and download the mask (definition) you want and save it to your computer.

Copy and paste the MASK you downloaded into the Tunerpro's BIN DEFINITIONS folder, and copy and paste the BIN you want into the BIN folder. Then when you load Tunerpro go to the menu for XDFs and open the $8D to load it.

Now when you open the bin you are working on, the XDF will tell the program how to find various parameters in the code in the right places.

 

Well then I have another question.......if the aujp is for autos, and I use it, how will it affect the way my car runs?

 

S_AUJP has a flag that can be switched on an off to change from auto to manual. Option Word 3 - Bit 2

I don't have this switch defined in $8D though.

 

So your saying I can change from auto to manual by opening up the s_aujp in tp rt and change the setting? Or do I actually have to change it in the code of the bin file?

But either way I do it, the xdf won't comprehend the bin file because the $8D doesn't have the code to support it? Is that what you meant when you said you didn't have it defined?

 

Yes and yes.

Yes you can change the Flag from auto to manual and the ECM will be aware that items like TCC clutch lockup and other auto parameters are not going to be used while you have the flag enabled.

The difference between using an auto setup and a manual bin is that the manual bin has already been tuned to idle, come to a stop and just everyday driving that we take for granted. The auto bin may or may not make it idle funny, try to stall when you roll to a stop and idle rough. You may have great success with Super AUJP.

The XDF is just an overlay telling Tunerpro and the ECM where to find information within the BIN. Like a blueprint, or a schematic. If you want to modify something, you first have to know where in the memory to find it.

Different XDF's have different options in them, and can be edited to add additional options to find more and more things within the BIN that can be modified. His version might not have the option added into it.

Flags, constants and tables... you need to start reading the stickies.