need help: new xml files for upcoming ECUFlash release
#168
Evolved Member
iTrader: (6)
I made several more revisions to the 88590015 xml file and evo9base xml:
1) Now has correct target idle tables
2) jcsbanks knock tables
3) Slight revision to table names in "turbo dual boost solenoid" tables
If no one has any substantiative objections, this will be the final for the next release of ECUFlash. I wanted to get the ISCV tables fixed up, but I'm burned out for now, so I'll save that for another ECUFlash release down the road.
tephra and al\lupo, if you could convert to your ROMs, then I'll submit the package to Colby.
Would be great if someone could step up to do the Evo 8s. I'd do it, but I'm strapped for time as it is.
1) Now has correct target idle tables
2) jcsbanks knock tables
3) Slight revision to table names in "turbo dual boost solenoid" tables
If no one has any substantiative objections, this will be the final for the next release of ECUFlash. I wanted to get the ISCV tables fixed up, but I'm burned out for now, so I'll save that for another ECUFlash release down the road.
tephra and al\lupo, if you could convert to your ROMs, then I'll submit the package to Colby.
Would be great if someone could step up to do the Evo 8s. I'd do it, but I'm strapped for time as it is.
I just tried openning the file on my tuning laptop and got the same results. It will not open.
Last edited by nj1266; Dec 17, 2008 at 09:17 AM.
#169
Just realized that I hadn't posted all the latest revised xmls in one place. The zip attachment has all the new xml files. These are all the revised xmls that will show up in the next version of ECUFlash. Thanks to al\lupo (EDM Evo 9), tephra (ADM Evo 9), and gear head (USDM Evo 8 96940011, and 96530006) for helping.
Besides the new and fixed tables in these xmls, Colby is working on a new feature to allow custom table entries to be stored in a standalone xml file. This will allow users to easily update to new base definitions whenever a new version of ECUFlash is released. Until Colby has that ready, I have cobbled together a way to do this without any needed changes to the ECUFlash program. The first step is to create the "mods.xml" file that will hold all your custom definitions. The easiest way to make this file is to
A) Make a copy you current xml file and name it: "XXXXXXXX_mods.xml", where XXXXXXXX is your ROM ID, (e.g., 88590015).
B) Open the file and change the xmlid from "<xmlid>XXXXXXXX</xmlid>" to "<xmlid>XXXXXXXX_mods</xmlid>".
C) Change the "<include>evoXbase</include>" to "<include>evoXbase_20081101</include>" ("X" should be change to 7 or 9).
D) Delete all the tables except the custom ones that you have added.
E) Copy over the new xml file for your ROM from the attached zip file
F) Open the file, and you will see:
"<!-- **<include>XXXXXXXX_mods</include>** -->"
Remove the "<!-- **" and "** -->", and then save the file.
Launch ECUFlash (if it was already running, close it and relaunch it), and all your custom definitions should show up along with the revised and new tables.
For ECUFlash 1.29 users, no problem to change to "Little" endian. Everything except the Periphery Bits tables will work.
EDIT: I rezipped the files and attached the archive. This was done on a PC using the WinXP built-in zip utility. (I'm pretty sure the other archive was also done using the built-in zip utility, but redoing it anyhow.)
Besides the new and fixed tables in these xmls, Colby is working on a new feature to allow custom table entries to be stored in a standalone xml file. This will allow users to easily update to new base definitions whenever a new version of ECUFlash is released. Until Colby has that ready, I have cobbled together a way to do this without any needed changes to the ECUFlash program. The first step is to create the "mods.xml" file that will hold all your custom definitions. The easiest way to make this file is to
A) Make a copy you current xml file and name it: "XXXXXXXX_mods.xml", where XXXXXXXX is your ROM ID, (e.g., 88590015).
B) Open the file and change the xmlid from "<xmlid>XXXXXXXX</xmlid>" to "<xmlid>XXXXXXXX_mods</xmlid>".
C) Change the "<include>evoXbase</include>" to "<include>evoXbase_20081101</include>" ("X" should be change to 7 or 9).
D) Delete all the tables except the custom ones that you have added.
E) Copy over the new xml file for your ROM from the attached zip file
F) Open the file, and you will see:
"<!-- **<include>XXXXXXXX_mods</include>** -->"
Remove the "<!-- **" and "** -->", and then save the file.
Launch ECUFlash (if it was already running, close it and relaunch it), and all your custom definitions should show up along with the revised and new tables.
For ECUFlash 1.29 users, no problem to change to "Little" endian. Everything except the Periphery Bits tables will work.
EDIT: I rezipped the files and attached the archive. This was done on a PC using the WinXP built-in zip utility. (I'm pretty sure the other archive was also done using the built-in zip utility, but redoing it anyhow.)
Last edited by mrfred; Dec 21, 2008 at 07:41 AM.
#170
Evolved Member
iTrader: (3)
Im unable to open up the zip file as well... Uuggghh now my work comp wont open up zip files either... damn it dawg! WTF is going on here? just all of the sudden on 2 of my comps now (desktop @ work/laptop for tuning), Im unable to open up zip files... I also DL/installed winzip...
freaking killing me...
freaking killing me...
#171
Im unable to open up the zip file as well... Uuggghh now my work comp wont open up zip files either... damn it dawg! WTF is going on here? just all of the sudden on 2 of my comps now (desktop @ work/laptop for tuning), Im unable to open up zip files... I also DL/installed winzip...
freaking killing me...
freaking killing me...
#176
Evolved Member
iTrader: (26)
Join Date: Oct 2007
Location: Colorado Springs, CO
Posts: 1,989
Likes: 0
Received 0 Likes
on
0 Posts
Whoa...
Just downloaded the new ECUFlash and I was blown away... LOL
Lost all my mods and crap so I've been spending a few hours searching and finding the XML to re-insert.
Reason being, I was running on an AEM EMS for a few months and paid no attention to the Flashing stuff. Now that I decided to go back to stock ECU, I've had to learn all over again.
-E
Just downloaded the new ECUFlash and I was blown away... LOL
Lost all my mods and crap so I've been spending a few hours searching and finding the XML to re-insert.
Reason being, I was running on an AEM EMS for a few months and paid no attention to the Flashing stuff. Now that I decided to go back to stock ECU, I've had to learn all over again.
-E
#177
Whoa...
Just downloaded the new ECUFlash and I was blown away... LOL
Lost all my mods and crap so I've been spending a few hours searching and finding the XML to re-insert.
Reason being, I was running on an AEM EMS for a few months and paid no attention to the Flashing stuff. Now that I decided to go back to stock ECU, I've had to learn all over again.
-E
Just downloaded the new ECUFlash and I was blown away... LOL
Lost all my mods and crap so I've been spending a few hours searching and finding the XML to re-insert.
Reason being, I was running on an AEM EMS for a few months and paid no attention to the Flashing stuff. Now that I decided to go back to stock ECU, I've had to learn all over again.
-E
#178
#179
Evolved Member
iTrader: (26)
Join Date: Oct 2007
Location: Colorado Springs, CO
Posts: 1,989
Likes: 0
Received 0 Likes
on
0 Posts
Yeah, it's been a while...
-E
P.S. LMAO!! That backup folder sure had it all in there. Shhh, don't tell my wife...
Last edited by Wicked E; Dec 17, 2008 at 10:43 PM.
#180
Evolved Member
iTrader: (3)
I just tried to open the new zip from al/lupo and still Nathan!
Drama...