Two questions:

1. Is it safe to run 40-41* advanced timing?
2. What is EGR advancement? How do I define these maps? I searched under EGR and did not find good thread.

Thanks

 

Use these xml files:

https://www.evolutionm.net/forums/sh...39#post5720239

Note that it might be necessary to reduce or remove the developer level.

 

My two examples are evo 8's. Evo 9's might be different because of Mivec.

I have done some small testing on the dyno with 40* advancement at cruise with Evo 9's with no knock/issues. However I have not done enough real-world testing to confirm it.

 

Heres what I am currently running w/... A combination of MRFREDs cruising area, and NJ's wot area!

http://i347.photobucket.com/albums/p...nt/newmaps.jpg

I just realized I left out my HOM out. Im running 15.4-15.7 from 20 to 80 load and 1500 to 4000 rpm.

 

You do NOT have an AFR meter. You really do not know what your AFR is. The numbers that we enter in the fuel map are NOT the same as the numbers that we log.

Let us say that I am driving in cruise and I start seeing 15.9+:1 on my XD-1 gauge, then I slightly lift off the gas to bring it down.

Since you do not have an AFR meter w/gauge and you encounter what I hypothetically encountered, you will continue driving and the AFR will keep getting leaner and your car would detonate.

Do you have the knockCEL map from Tephra to tell if you are knocking? I have that in my rom and it is set at 3 counts so I can tell if I encounter knock.

An AFR meter and a knockCEL patch are a MUST when doing this.

 

Here is the timing map. The mivec map is the same one I posted in the mivec thread and in the tune your Evo thread. The 26.2 was with 70/30 freeway/street driving before I disabled closed loop. I am hoping it should be around 28 on the next tank.

 

How much timing advance at cruise is too much? At such low loads, knock will be a non-issue so it's possible to over-advance and not know it...

 

Do these xml files work with ECUflash 1.29a, or do I need to upgrade to another version?

 

Just have to change the endian tag to "little". I was using 1.29a for a long while because of the incompatibility of later ECUFlash versions with my cable. I eventually called Colby, and he set me up with a free fix for the cable. I recommend that you do the same because newer versions of ECUFlash have several bug fixes and have new cabability to read individual bits which makes it much easier to change the periphery values.

 

Wondering the same, although I am finding that I can cause some knock at loads as low as 70.

 

ok, so you're basically at 28.8 deg of MIVEC advance in the cruise cells (50-100 load and 2000-4000 rpm). That's quite a bit more MIVEC advance than what I run. I may try upping the values in my tune.

 

Also keep in mind that the timing numbers that are entered in the load cells are suggestive numbers. The actual logged numbers can be higher/lower. I think keeping the timing numbers below 40* is safe.

My main concern is when I go WOT with this map will the timing/afr transition trigger knock. If I can use this same map for both fuel economy and WOT runs, then it would be ideal.

 

The numbers in the timing table are lower bound numbers in absence of knock. When the EGR system kicks in, additional timing is added to these base values in a small range of cells. When you get my xml files installed, you'll see the tables.

I am wondering the same about knock when I got WOT. I have yet to try goint WOT as I'm trying to see what peak mileage I can get for my typical daily driving routine (without the normal WOT jaunts).

 

I actually just made the open loop load/throttle tables, and made the change to my high octane map last night, but havent flashed the car yet, because of this reason!
No I dont have a WB nor do I have Tephras knock cell patch.
I understand what youre saying, but it seems like every1 is using the same values / or very near the same values. 15.3-15.7 I even used YOUR cruising area in my HOM, NJ. I figured this should be O.K.

 

mrfred,

I used your xml files, but noticed that the table that allows Evo 9s to control idle is missing. The two tables that are in there do not control idle IIRC. There was a third one that was defined by forum members, but I cannot see it.

This is the code for it:

<table name="Actual Desired Idle RPM" category="Idle" address="3d24" type="2D" scaling="RPM8">
<table name="Engine Temp" address="70c2" type="Y Axis" elements="8" scaling="Temp"/>
</table>