merlin.oz

I have been evolving my 88580013 files for improved readability and understanding. In no particular order:

<!-- *** Sensor Calibration *** -->

<table name="Coolant Temp Scaling" address="ae6a">
<table name="Coolant Temp Sensor Raw" address="af1c"/>
</table>

<table name="IAT Scaling" address="b070">
<table name="Intake Air Temp Sensor Raw" address="b106"/>
</table>

<table name="Airflow/Hz Raw Scaling" address="2d06">
<table name="MAF Hz" address="6eac"/>
</table>

<table name="Airflow/Hz Offset Raw" address="1112"/>

<table name="MAF Compensation" address="2d22">
<table name="MAF Hz" address="6eac"/>
</table>

<table name="MAF Sensor Filtering" address="1108"/>

<table name="MAF Size" address="110c"/>

Helps un-clutter the fuel section and gets all the sensor stuff together.



<!-- *** IC SPRAY *** -->
<table name="IC Min-RPM" address="2080"/>

<table name="IC Min-Water Temp" address="2082"/>

<table name="IC Max-Speed" address="2086"/>

<table name="IC Min-TPS" address="2098"/>

<table name="IC Min-Air Temp" address="209c"/>

<table name="IC Min-Load" address="2088"/>

<table name="IC Time" address="28c6"/>
Short title allows readability in the tiny window allowed.



<table name="ECU Periphery0 (FAA) Bits" category="Periphery" address="faa" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>bit.15 .</data>
<data>bit.14 .</data>
<data>bit.13 .</data>
<data>bit.12 .</data>
<data>bit.11, 1= Enable Ign Adv, 0=Disable EGR Test .</data>
<data>bit.10 .</data>
<data>bit.09, 1=Enable Warmup Ign Tables .</data>
<data>bit.08 .</data>
<data>bit.07, 1=Enable High Oct Ign Map Lookup and many other subroutines .</data>
<data>bit.06, 1=Enable WG solenoid? Enable Speed Limit Test .</data>
<data>bit.05 .</data>
<data>bit.04 .</data>
<data>bit.03, 0=Disable Immobilizer function .</data>
<data>bit.02 .</data>
<data>bit.01, 0=Disable Rear O2 Test .</data>
<data>bit.00 .</data>
</table>
</table>
Spaced like this improves legibility (to me anyway).

EDIT:
OK, that last bit did not come out right. The idea is to include spaces and a .(dot) at the end to get the whole table spaced evenly.

travman

iTrader: (26)

Wonderful...awaiting details, this would help make updating to new "updated xml's much easier.

gear head

iTrader: (3)

Great idea....I think I just figured out how you did this.


Build a seperate Mods xml. & include the evo7base

<rom>
<romid>
<xmlid>96530006_Mods</xmlid>
</romid>

<include>new_evo7base</include>


Include the Mods xml in the ROM xml.

<include>96530006_Mods</include>

mrfred

iTrader: (50)

That's it.

fixem2

iTrader: (30)

Gear head and mrfred, in my spare time I have been trying to convert the xml mrfred posted to a 96530006 version. May have to post a file with something for others to review, because I am not sure what all is Evo 9 specific, besides MIVEC and mulitple ignition tables. If someone is already doing this activity, please let me know.

mrfred

iTrader: (50)

jumperalex had talked about updating all the Evo 8 xml files, but haven't heard anything recently. If you post the revised xml, I could probably take some time to review it. Don't suppose you'd also want to do 96940011 while you're at it would you? Kinda curious because I'm sure there are quite a few people with '05 Evo 8's not running the tephra 96530006.

Jumperalex

Yeah sadly just as I was getting into it life grabbed me by the scruff and dragged me off. I've been able to lurk occasionally but have had no time to work XML stuff. I'll also admit that I'm out of my knowedge set in converting 9 stuff to 8 stuff. I haven't been keeping good enough track of what has been going on to know which tables are what.

gear head

iTrader: (3)

I actually have a evo7base that's just about complete. Like you I'm having a hard time trying to figure out what is specific to the 9 & 8.

Another question....

There are a ton of "new" tables for the 96530006 & 96940011 as well as other ROMs.....what should be included?

I'm all for making the effort, it would be a shame for the 8's to get left in the dust.

fostytou

iTrader: (15)

Be careful if you try this... I was trying it backwards at first (including mods in the evo9_[date] xml file) and things weren't showing up. When I tried it the correct way my processor usage jumped to 100% for a few minutes and the ecuflash process was taking up 560mb... never showed up. Now the laptop is acting weird. I'm going to restart to try to fix everything...

fostytou

iTrader: (15)

PS... I'm using 1.40

Yeah, it took a restart and a re-install to get back on track. This method still isn't working for me though... can someone give a better example?

I have 88590015_mods.xml

Then I have 88590015.xml with only this line changed


evo9base_20080530.xml is unmodified.

The options I get show up like I haven't done anything at all. This is working like it did when I started using mrfred's defs where I need to add things to the base file for them to show up anywhere.

mrfred

iTrader: (50)

The "<include>evo9base_20080530</include>" line has to be in both the 88590015.xml file and in the 88590015_mods.xml file.

al\lupo

Here it is 88840016 as mrfred specs.

mrfred

iTrader: (50)

Thank you. Still waiting to hear from tephra. ;-)

C6C6CH3vo

iTrader: (9)

So the main goal here is to have an ECUFlash version with more accurate and newly defined tables for ALL Xml ID types so the basic flash enthusiast like me will have automatic access to them?

mrfred

iTrader: (50)

Yep.