I'm working with a LT1 computer with an unknown history, it appears to have a modified .bin file.
I'm using EEHack to read the PCM. Attached are the files I'm working with. I'm curious why there are about 3000 undefined parameters read file vs. library file.
Is it possible the undefined parameters are due to the way EEHack reads the PCM?
dave w
Eehack fills ram memory 0-2000 on both sides with 00s. Otherwise there are small differences on tside, and couple on eside.
If the differences are between 0-2000 and 10000-12000 area are you can just ignore them.
A couple addresses above 2000 and a couple addresses above 12000 are undefined:
2015
2016
12015
12016
Thoughts?
dave w
2015 & 2016.JPG
12015 & 12016.JPG
those be the checksums. 2015-2016 for one eeprom, 12015-12016 for the other.
i'll point as far as the ram goes that it's possible to download the ram contents with eehack (0-0x2000)
there's a checkbox for it, i just find it kind of a useless thing to do for tuning so i figured i'd save some time, i'm actually not sure why any tool would do that by default, and not sure why the ordinary bin format for $EE contains that data region since it's not EEPROM data that you can modify.
they can be different from one read to the next depending on what the engine was doing before you read the bin, so comparing data in that region doesn't have any sane use.
Thank youOriginally Posted by steveo
If you're curious about what's actually different, I would recommend that you use a more complete XDF than the one you're currently using. I personally use EEXTRA v0.003, which I have attached to this post for reference. The result of running a difference scan using this XDF instead makes it clear that those parameters are far from undefined:
Best of luck with your project!
1990 Corvette (Manual)
1994 Corvette (Automatic)
1995 Corvette (Manual)
Thank YouIf you're curious about what's actually different, I would recommend that you use a more complete XDF than the one you're currently using. I personally use EEXTRA v0.003, which I have attached to this post for reference. The result of running a difference scan using this XDF instead makes it clear that those parameters are far from undefined:
Best of luck with your project!
Posting Permissions
Reply With Quote
Bookmarks