I'm not very computer literate, so please bear with me. Let's say I'm using TunerPro with one of the 6E masks.......we'll call it XDF "A". Then, lets say I've found another XDF I'll call "B". Let's also say that each of these XDFs has one or more parameters the other doesn't have.

My specific question is: "B" has a parameter that "A" doesn't have that I'd like to use; so if I save a new bin changing over from "A" to "B" will that erase anything that that I've modified on a parameter that the new XDF does not have?

I get the concept of my common parameters being changed unless I "copy from compare" or otherwise use another copy function, I'm just unsure of parameters that aren't shared between the XDFs.

I tend to think a new bin saved under a different XDF will only contain that XDF's information, but I'd like to know for sure. I tried to locate a compare function for XDFs, but I couldn't find anything.

TIA & Happy Thanksgiving!

 

If the xdf address has been hacked and defined it will show in a .bin comparison if not just the undefined address. Once the .bin has been modified weather the xdf shows the what is at the address it is still modified in the code.

 

Thanks for your reply. So if I understand this correctly, a parameter would hold as changed, it would just show up as "item not defined" in comparing bins?

 

you got it

 

You can also open 2 TunerPros, copy one XDF paremeter and add it to another so you have one complete mask/XDF. As long as each paremeter was entered correctly from the hack in first place.

But be very careful with $6E XDF floating around. One has spark bias built into spark table and one does not, so one spark advance table shows 9.84 degrees more timing then other.

 

Thanks very much EagleMark, I'll give that a shot even tho it's very probably beyond my capabilities. The masks I'm using are the 6E from your site, the 6Eexpanded I *think* I snagged from here, and GTA's 6E which is named GTA 165 6E 9-21-07.

Do you offhand know which has the spark bias? Thanks!

 

I don't remember? But it cost a guy a lot... Usually if we find an issue we fix it, but in this case I don't recall and there are a lot of files floating around from other places. Most TunerPro XDF do not have warm spark bias taken out of main spark advance tables so that is what we probably ended up doing?

Just look at your spark advance table in one XDF and compare to the other XDF. One will be approx 10* more in all cells. He took the more aggresive spark table and put it in other XDF. Adding ten degrees across the table of an already aggresive spark advance.

Some guys take out warm spark bias not knowing it would add 9.84 degrees to entire spark advance table.

One XDF in paticular $42 5.7L bin has 9.84 warm spark bias and 7.4L bin has 0 warm spark bias !

Mixing and matching XDF or bins for that matter is not a good idea.

Just be careful!

 

as long as you stay with one XDF, it won't make a difference, since if the table is setup correctly, it will subtract the value from the PROM location, not assume it's either 10 or 0.

 

Thanks for weighing in on this guys, I'm just going to stick with GTA's XDF since it has all the parameters I've been using.

Happy Thanksgiving to all!