Notices
ECU Flash

New Maps for Evo 7 and 9

Thread Tools
 
Search this Thread
 
Old Nov 1, 2008 | 07:30 AM
  #226  
evo828's Avatar
Evolving Member
 
Joined: Apr 2007
Posts: 195
Likes: 1
From: Slovakia
Originally Posted by logic
It's there now; looks like it was a problem with the "+" signs and spaces in the filename. Guys, stick to underscores for separators, k?
I've put updated 96530006 and evo7base on 96530006 wiki page - including the primer tables.

http://evoecu.logic.net/wiki/96530006#Download


direct link:
http://evoecu.logic.net/images/4/42/...s_20081101.zip
Reply
Old Nov 1, 2008 | 11:54 AM
  #227  
fixem2's Avatar
Evolved Member
iTrader: (30)
 
Joined: Dec 2003
Posts: 929
Likes: 0
From: USA
File shows corrupted after download
Reply
Old Nov 1, 2008 | 11:57 AM
  #228  
logic's Avatar
Evolved Member
iTrader: (2)
 
Joined: Apr 2003
Posts: 1,022
Likes: 7
From: Berkeley, CA
Opens just fine over here.
Reply
Old Nov 1, 2008 | 12:12 PM
  #229  
Jorge T's Avatar
Evolved Member
iTrader: (18)
 
Joined: May 2004
Posts: 1,494
Likes: 1
From: Houston, TX
corrupted here
Reply
Old Nov 3, 2008 | 12:10 AM
  #230  
acamus's Avatar
Evolved Member
 
Joined: Mar 2008
Posts: 730
Likes: 3
From: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Originally Posted by Mattjin
I have been doing alot of map discovery for my Evo7 GT-A (80700010) and have started to find the same maps for the more common definitions that we see here in Australia. Please test the maps carefully before fully implementing them. Also some of the scale ranges for these vehicles were not immediately obvious in the disassembly so they may need to be corrected, but the values I have used are the same as those working on my definition.

All need the "Enrich" scale which is actually a mislabelled timing trim scale. Most defs have it, if not add this line.

<scaling name="Enrich" units="deg" toexpr="x-128" frexpr="x+128" format="%.0f" min="-128" max="128" inc="1" storagetype="uint8" endian="big"/>


For the Evo 9 - 88580015

<table name="Ignition Trim vs Engine Temp" category="Timing" address="3c80" type="2D" level="2" scaling="Enrich">
<table name="Engine Temp" address="71ca" type="X Axis" elements="8" scaling="Temp"/>
</table>

<table name="Ignition Trim vs Air Temp" category="Timing" address="3c8e" type="2D" level="2" scaling="Enrich">
<table name="Air Temp" address="71ca" type="X Axis" elements="8" scaling="Temp"/>
</table>

<table name="Ignition Trim Unknown (High Temp?)" category="Timing" address="3c9c" type="2D" level="2" scaling="Enrich">
<table name="Temp" address="6f30" type="X Axis" elements="5" scaling="Temp"/>
</table>

<table name="Ignition Trim vs Air Temp Active Above Load" category="Timing" address="3ca8" type="2D" level="2" scaling="Load8">
<table name="Engine Speed" address="6c82" type="X Axis" elements="10" scaling="RPM"/>
</table>

<table name="Warmup Retard Temp Control" category="Timing" address="3cb8" type="2D" level="2" scaling="uint8">
<table name="Engine Temp" address="807a" type="X Axis" elements="8" scaling="Temp"/>
</table>

<table name="Decel Fuel Cut Delay #1" category="Fuel" address="3d92" type="2D" level="2" scaling="uint8">
<table name="Load" address="70a2" type="X Axis" elements="7" scaling="Load"/>
</table>

<table name="Decel Fuel Cut Delay #2" category="Fuel" address="3da6" type="2D" level="2" scaling="uint8">
<table name="Load" address="70a2" type="X Axis" elements="7" scaling="Load"/>
</table>

<table name="Decel Fuel Cut Ignition Retard" category="Fuel" address="3dc6" type="2D" level="2" scaling="Timing">
<table name="Engine Speed" address="6d56" type="X Axis" elements="10" scaling="RPM"/>
</table>
Some corrections to the above "Warmup Retard Temp Control" is actually amount of interpolation between taken Ignition value from ignition maps and Warm up ignition map.

for 88590015 it looks like

<scaling name="Weigth Factor" units="%" toexpr="x/255*100" frexpr="(x/100*255)" format="%.1f" min="0" max="130" inc="0.1" storagetype="uint8" endian="big"/>
<scaling name="Warm Up Ignition" units="degrees" toexpr="x-128" frexpr="(x+128)" format="%.0f" min="-61" max="61" inc="1" storagetype="int8" endian="big"/>


<table name="Warm up ignition interpolation amount" category="Timing" type="2D" address="3CB8" scaling="Weigth Factor">
<table name="Coolant Temperature" type="X Axis" address="804C" elements="8" scaling="Temp"/>
</table>

<table name="Warm up ignition" category="Timing" type="3D" address="3AA9" swapxy="true" scaling="Warm Up Ignition">
<table name="Engine Load" address="6f2c" elements="21"/>
<table name="RPM" address="6efa" elements="20"/>
</table>
Reply
Old Nov 3, 2008 | 08:30 AM
  #231  
mrfred's Avatar
EvoM Guru
iTrader: (50)
 
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Originally Posted by acamus
Some corrections to the above "Warmup Retard Temp Control" is actually amount of interpolation between taken Ignition value from ignition maps and Warm up ignition map.

for 88590015 it looks like

<scaling name="Weigth Factor" units="%" toexpr="x/255*100" frexpr="(x/100*255)" format="%.1f" min="0" max="130" inc="0.1" storagetype="uint8" endian="big"/>
<scaling name="Warm Up Ignition" units="degrees" toexpr="x-128" frexpr="(x+128)" format="%.0f" min="-61" max="61" inc="1" storagetype="int8" endian="big"/>


<table name="Warm up ignition interpolation amount" category="Timing" type="2D" address="3CB8" scaling="Weigth Factor">
<table name="Coolant Temperature" type="X Axis" address="804C" elements="8" scaling="Temp"/>
</table>

<table name="Warm up ignition" category="Timing" type="3D" address="3AA9" swapxy="true" scaling="Warm Up Ignition">
<table name="Engine Load" address="6f2c" elements="21"/>
<table name="RPM" address="6efa" elements="20"/>
</table>
Hi acamus,

We got those worked out already. tephra has worked out the exact details of many of the other timing trim maps as well.
Reply
Old Nov 3, 2008 | 10:29 AM
  #232  
acamus's Avatar
Evolved Member
 
Joined: Mar 2008
Posts: 730
Likes: 3
From: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
see below

Last edited by acamus; Nov 3, 2008 at 10:31 AM.
Reply
Old Nov 3, 2008 | 10:30 AM
  #233  
acamus's Avatar
Evolved Member
 
Joined: Mar 2008
Posts: 730
Likes: 3
From: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
I see, why I do not know about them?
I would say that double-checking does not hurt
Reply
Old Nov 3, 2008 | 10:47 AM
  #234  
mrfred's Avatar
EvoM Guru
iTrader: (50)
 
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Originally Posted by acamus
I see, why I do not know about them?
I would say that double-checking does not hurt
Agreed. Unfortunately, most of these new findings are getting spread across many different threads.
Reply
Old Nov 3, 2008 | 01:32 PM
  #235  
Mattjin's Avatar
Thread Starter
Evolved Member
 
Joined: Apr 2008
Posts: 604
Likes: 0
From: Sydney, Australia
It is sounding like someone should compile all of the map findings and post a more complete XML definition range for the common cars. The only trouble is that we need to agree on labelling for the maps. Everyone seems to have their own way of labelling the maps which can add to confusion of exactly what does what. There must be alot of newbies out there with multiple maps pointing to the same addresses.
Reply
Old Nov 3, 2008 | 06:40 PM
  #236  
troe666's Avatar
Evolving Member
 
Joined: Aug 2006
Posts: 130
Likes: 0
From: Adelaide, South Australia
hi guys,
I have an australian-delivered evo 9 and want to enable this periphery bits table to turn off that CEL from my exhaust/O2.

which XML do I use? I need MIVEC, etc, everything table-wise the latest ecutek version has, so that I dont lose anything, I just want to read my ECU, edit the periphery bits table, re-image , in a loss-less sense.

can I achieve this at this stage?
Reply
Old Nov 4, 2008 | 12:32 AM
  #237  
tephra's Avatar
EvoM Guru
15 Year Member
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
u can't

u can however run my V5.10 MOD, leave your rear02 connected and enable the 'rear 02 simulator' in the mod... that will get rid of the CEL
Reply
Old Nov 4, 2008 | 01:50 PM
  #238  
Mattjin's Avatar
Thread Starter
Evolved Member
 
Joined: Apr 2008
Posts: 604
Likes: 0
From: Sydney, Australia
Hey Dave, do you think you can patch up 80700010 for me with the CEL on knock and map switching? You can PM or email me if you need anything. Already has NLTS (automatic - haha) and no ICS.
Reply
Old Nov 5, 2008 | 07:22 AM
  #239  
dudical26's Avatar
Evolved Member
iTrader: (17)
 
Joined: Nov 2005
Posts: 2,544
Likes: 0
From: NNJ
Originally Posted by Mattjin
It is sounding like someone should compile all of the map findings and post a more complete XML definition range for the common cars. The only trouble is that we need to agree on labelling for the maps. Everyone seems to have their own way of labelling the maps which can add to confusion of exactly what does what. There must be alot of newbies out there with multiple maps pointing to the same addresses.
That why we built the Wiki. I started a page on the wiki for findings related to cold start fuel and another for cold start timing. That way we can share our findings in one place.

http://evoecu.logic.net/wiki/ECU_Development
Reply
Old Nov 5, 2008 | 01:23 PM
  #240  
Mattjin's Avatar
Thread Starter
Evolved Member
 
Joined: Apr 2008
Posts: 604
Likes: 0
From: Sydney, Australia
So we should start a thread asking everyone to combine and discuss these tables after we find their functions, and then agree an what we will call them. The difficult part I suppose is that there are differences between the roms, and no one person can test all of them.

It is also a warning for the newbies who go and add every map that someone posts, with alot of the postings not 100% confirmed. I know I am almost certain of the maps I post because I spend alot of time checking and rechecking that the map responds as it says, but that doesnt mean I cant make mistakes too. It's only a few months ago that I was saying "what's an IDA Pro" :-)

I am also getting some more headway on finding the real maps that handle the accel enrichment, in so far as the maps functions. Alot are already found by others but some are either mis-labelled or not completed. There are alot of maps linked to this area so finding the function of all of them is going to take some time.

While doing some work on this yesterday I found something rather weird. There seems to be an ignition trim that I have not tracked down yet. With fixed, locked timing maps I can watch the timing advance while under decel enleanment (decreasing throttle opening, but not closed). It is something in the order of 5 to 6 degrees depending on what I do with the throttle. I noticed this while trying to track down if the ecu does any advance or retard under accel enrich conditions.
Reply



All times are GMT -7. The time now is 08:30 AM.