EEHACK XDF gives "item not defined" during compare

[lance_mn]

I've got the most recent XDF found here:
http://fbodytech.com/eex-tunerpro-definition/

When I compare the differences between my BIN files (from a 95 z28) using the "compare" tool, I see several addresses that say "Item not defined," which means that something changed but the XDF doesn't have a definition for that address.

IMPORTANT NOTE: I used this exact same XDF file when making these changes between bins in the first place!

This is making me extremely nervous as a cherry-pick differences from one tune into another using the compare tool. Perhaps important things were changed in these unknown fields, which also need to be brought along with the changes I'm cherry-picking - or any other issue one can imagine with not knowing what's inside these fields.

I can't be the only one having this issue - anybody tuning an LT1 and using the compare tool with the eehack XDF should be having these issues as well. Is there a known solution? Is there a more up-to-date XDF not currently hosted at fbodytech.com ??

halppp!

[lionelhutz]

User jthompson122183 here created a version called EEXTRA with even more stuff mapped, but many of the additions have no documentation about what they do.

Here's a link to a thread about it, but not sure if there are even newer versions posted in other places.

http://www.gearhead-efi.com/Fuel-Injection/showthread.php?6260-94-95-EE-xdf-(EEXTRA)'


Otherwise, this is why you generally want to pick the right starting bin so you know the basics of the bin are what you want and these unknown differences won't mess you up.

[steveo]

which means that something changed but the XDF doesn't have a definition for that address.

don't be so sure.

for starters, keep in mind $EE bins include a dump of RAM

any 'unmapped stuff' between 0x0000 to 0x2000 and 0x10000 - 0x12000 is not real prom data and just represents the state of ram on the ECM when the bin was read

i bet you'll find your unknowns are there.

there is no secret crap that people (or GM) was tuning between different EE bins, and the advanced variables in EEX and EEXtra are generally not in any bins that you'll find floating around, so don't worry too much about hidden variables

[lance_mn]

don't be so sure.

for starters, keep in mind $EE bins include a dump of RAM

any 'unmapped stuff' between 0x0000 to 0x2000 and 0x10000 - 0x12000 is not real prom data and just represents the state of ram on the ECM when the bin was read

i bet you'll find your unknowns are there.

there is no secret crap that people (or GM) was tuning between different EE bins, and the advanced variables in EEX and EEXtra are generally not in any bins that you'll find floating around, so don't worry too much about hidden variables

Thanks a million steveo. You're the man.

[1project2many]

there is no secret crap that people (or GM) was tuning between different EE bins

You mean like the Super Duper "Prototype" calibration supposedly discovered by a pro tuner on a GM CD years ago? :rolleye:

I've seen it. It's not even a grail shaped beacon (https://www.youtube.com/watch?edufilter=NULL&v=nMUnbNPCoSw).