need help: new xml files for upcoming ECUFlash release
#196
Evolving Member
iTrader: (3)
Small correction on the 96530006 file. The 96530006 file shows the following for the IPW Adder:
<table name="IPW comp starting" address="3822">
<table name="Coolant Temperature" address="69be"/>
</table>
Code in the evo7base file:
<table name="Cranking Enrichment IPW Adder (Main)" category="Fuel" type="2D" level="2" scaling="TimeInjCranking">
<table name="Coolant Temperature" type="Y Axis" elements="8" scaling="Temp"/>
</table>
<table name="Cranking Enrichment IPW Adder (Unused)" category="Fuel" type="2D" level="2" scaling="TimeInjCranking">
<table name="Coolant Temperature" type="Y Axis" elements="8" scaling="Temp"/>
</table>
With the original code the IPW adder will not show in Ecuflash. If I change the ROM xml to match the base xml it shows.
Also can someone review and let me know the correct address for the IPW table. I read mattjn talk about 3732 and 3742. Just need verification so we can get it added.
<table name="IPW comp starting" address="3822">
<table name="Coolant Temperature" address="69be"/>
</table>
Code in the evo7base file:
<table name="Cranking Enrichment IPW Adder (Main)" category="Fuel" type="2D" level="2" scaling="TimeInjCranking">
<table name="Coolant Temperature" type="Y Axis" elements="8" scaling="Temp"/>
</table>
<table name="Cranking Enrichment IPW Adder (Unused)" category="Fuel" type="2D" level="2" scaling="TimeInjCranking">
<table name="Coolant Temperature" type="Y Axis" elements="8" scaling="Temp"/>
</table>
With the original code the IPW adder will not show in Ecuflash. If I change the ROM xml to match the base xml it shows.
Also can someone review and let me know the correct address for the IPW table. I read mattjn talk about 3732 and 3742. Just need verification so we can get it added.
<table name="IPW comp starting" address="3822">
<table name="Coolant Temperature" address="69be"/>
</table>
I seem to get funky values when using the 3732 and 3742 addresses.
Set up mods file as such.....
<rom>
<romid>
<xmlid>96530006_Mods</xmlid>
</romid>
<include>evo7base_20081101</include>
--------ADD DEFS HERE------
</rom>
#201
EvoM Guru
iTrader: (6)
96530006:
Code:
<scaling name="TimeInjCranking" units="ms" toexpr="x*0.008" frexpr="x/0.008" format="%.1f" min="0" max="500" inc="1" storagetype="uint16" endian="big"/> <table name="Cranking Enrichment IPW Adder (Main)" address="58d0" category="Fuel" type="2D" scaling="TimeInjCranking"> <table name="Coolant Temperature" address="69d8" type="Y Axis" elements="9" scaling="Temp"/> </table> <table name="Cranking Enrichment IPW Adder (Unused)" address="38e8" category="Fuel" type="2D" scaling="TimeInjCranking" > <table name="Coolant Temperature" address="69d8" type="Y Axis" elements="9" scaling="Temp"/> </table>
#207
Evolved Member
iTrader: (6)
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.)
Another question, the evo7base and evo9base has a "_20081101" file name. Do I have to remove that from the name if I am using the old fashioned method of copying from my xml into yours?
thanks
#208
mrfred, if I want to do this the old fashioned way w/o creating an xml_mod file, can I simply take my mods from my current xml and add them to the ones you provided?
Another question, the evo7base and evo9base has a "_20081101" file name. Do I have to remove that from the name if I am using the old fashioned method of copying from my xml into yours?
thanks
Another question, the evo7base and evo9base has a "_20081101" file name. Do I have to remove that from the name if I am using the old fashioned method of copying from my xml into yours?
thanks
Yes, old fashioned way is fine.
Do not change the file names. In case you are wondering, do not delete the older "evo9base.xml" and "evo7base.xml" files.