This has quickly become my most-frequented forum on evom, so I thought it would be most productive to post this question here, instead of where most of the 'noise' tends to be.

Anyway, Al (Dynoflash) wrote this comment in the thread where he was getting bashed pretty hard for setting the LO and HO maps the same:

"On the 8's in certain applications it is importnat to set the maps the same to overcome some things which are going on inside the stock ecu.

Many people who have read about this method INCORRCETLY have asserted that when you fix the tmiing maps the same the ecu can not pull timing in the event of knock and this perception is TOTALLY INCORRECT. In fact when you set the two maps the same the ecu can and will pull just as mch timing jst as qucikly as if you have two different maps. The knock control is uneffected by fixing the maps the same and the reason for fixing them the same has nothing to do with knock corection what so ever."

Okay, so my question is, for those of you who have spent a lot of time tuning, is Al's comment correct? If so, how does the ECU determine how much timing to pull? I think most people assume that as knock count increases, the ECU slowly interpolates from the HO timing/fuel maps to the LO maps. After it reaches a certain knock level, you're completely into the LO maps. Al's comment implies that these maps do not necessarily work this way, but rather that there is some other logic to determine how much timing to pull, independent of the LO map settings. If so, what does the LO map really do? And how much timing is pulled for each knock count?

And, what "some things are going on" that need this sort of correction?

Any advice/ideas/discussion would be appreciated.

-Rob

 

I thought there was an octane number and each count of knock would cause this number to "decay", as in decrease. If the number reaches zero then the ECU switches to the low octane maps.

As for setting both low and high maps the same, I have yet to read a compelling reason why that is a good idea. You have two safety nets - the low octane maps and the knock sensors. Why take one of them away?

 

Okay Spectre, so what your saying is that there are two separate methods for pulling timing:

1.) As knock count increases, octane number is decremented. If octane number gets down to 0, the ECU switches from HO maps to LO maps.

2.) As knock count increases, the ECU has some logic that pulls timing (whether it be linearly related, some simple look up table, a function of rpm/coolant temp/air temp/boost, or whatever). The point is that as knocks increase, the ECU determines how much timing to pull independent of the LO maps. (it's just an offset from the HO maps)

Sound about right?

I wonder, does anyone know what new variables will be included in 0.9 version of EvoScan? I know LOAD won't be there, but I'm wondering if we've found any of the others (like octane or vehicle speed). I'll try to also post this question in a more appropriate forum on OpenECU.net.

 

The ECU can definitely pull timing independant of your high and low timing maps. Those maps are just a target value and the ECU only reaches that target if everything else appears to be running smoothly. I'm also not so sure if you want to say it's an "offset" from whichever map you are in. I believe we're not sure yet if it is just an offset, or a completely unique calculation.

There has been an addition for Octane to be read in the current version of EvoScan, basically it's an updated Data.XML file which adds the hex value for the location of the octane reading. I'll try and remember where that file was on here, but it's in one of the threads somewhere. Try a search for "Data.xml".

 

Thanks for the tip! I didn't realize that we could add channels to the logger. I had heard references to .XML files, but always thought that was just for fine tuning the calculations or mapping it to a different vehicle (DSM, etc.).

 

Yup! We can add channels to the logger. As we figure out which hex codes correspond to which readings, they can be added right in.

Replace this Data.xml file with your current file and you will have octane readings available:

 

^ that Data.xml file is courtesy of MalibuJack, btw

 

Where can I get a free XML editor? I would like to move the data sequence around so that they log in the order that I want them to.

 

right click -> open with -> notepad




.....or http://www.xmlcooktop.com/ if you like colors

 

Thanks, Stew. I found that file in the Octane thread, and educated myself by searching under 'data.xml'. So, I noticed that file doesn't have vehicle speed or afr in it. Are those variables still not necessarily verified?

Is there a list anywhere of confirmed new channels, or is the only certain one Octane Number at this point?

Sorry this thread has drifted off topic a bit, but it's useful for us newbies.

 

Some data on pulled timing on my '03 Evo: https://www.evolutionm.net/forums/sh...d.php?t=214146

l8r)

 

I posted my latest data.xml tonight.

https://www.evolutionm.net/forums/at...chmentid=95476

On my JDM Evo IX it adds:

3 bar MAP sensor
AFR map lookup value (128=14.7:1)
Vehicle speed
Octane number

You'll be missing the MAP sensor, or boost readings on it depending on the model you have.

New version of load calculation (experimental) is abs(2550*(injectorpulsewidth-0.4)/AFRMAP), but this would go in Excel only.

0.4 is an approximation to the 14.4V injector lag time on the US Evo 8 & 9.

 

I have a dynoflash 9 Base map in my evo and what I did was load that and maps 2-3 I loaded the stock maps from and it seems to be working good. I went from 230ish to 285whp on a DD Dyno and huge TQ. The only problem with the maps is it is in the 9-10 range so it's very rich but other then that the car moves out. I will say I have seen the maps flip on the dyno before and you will lose HP and go rich very fast and in the same run it flipped back to the more aggressive map. Do what I did, load the dynoflash map and if it's that bad it will flip maps, if not it will stay in the high power map.

 

deleted...

 

So how do I do that - to get the 0 - 255 octane # log for my Evo scan with the Data.xml from Jack and Banks? Sorry - ADD