Tephra..... on the additional maps you found ign#2 looks just like the timing I get on my E9 during a cold start and drive. When cold (40*) my 9 is coppy and sluggish. Logging the car shows its using about 50% of the timing it has been programed for.

I don't know if this is a cat lite off emissoins thing or not but it sucks. Others have the same problem and it would be nice to fix.

https://www.evolutionm.net/forums/sh...d.php?t=303378

 

Yes- I know Hamish. I love what he has done to help the mitsi community and Ive always paid for his software.

 

Jeff, it might also be part of that advance table depending on what rpm you were seeing the problems at.

 

so are we saying the evo has the capability to act like the Subaru?

ie advance up until knock/map limits and then hold there?

sorry I must have missed this but whats the deal with low/hi det maps?

 

Not sure how fast it reacts, but yeah thats the general idea. I have just started testing the USDM stuff to see what the triggers are for adding timing and how fast it will drop. I havent had any knock with the 4* added in and I have been able to log it changing less than the 4* that is blocked in. I am gonna add a custom request to log exactly how much its adding and when its doing it. Conversely I have the high det map set to -2* in case of malfunction.

 

If you add say, 4* to the map it shows less than 4* increase with corresponding logs?

 

This could possibly be the cure for my funky 3k knock, that is if it's really some sort of timing advance up to a knock point. I've tried everything I can think of (other than changing these specific timing advance maps) and it never goes away. Even when I flashed back to stock I still have it (rather annoying too), and have even tried dropping around 8* of timing in a very large area (it only made it worse). That being said, do you think that this table denotes actual timing advance (in degrees that is listed) or just a knock point that lets timing ramp up until it hits that certain specified count and drops timing?

 

I am trying to see how much it adds and how fast it adds. I theorize that it will try to add as much as possible until it gets some knock and then stops and backs up. From how I understand what Monsta has done as well, thats how it works. I realised last night I dont know how to get a custom request through the MUT table based on just the table addy.

 

My feeling is that there will be something like the "Octane Number" which ramps up under no knock conditions and interpolates. It proberly will react alot quicker than the "octane number" or they would have just made adjustments to the main ignition maps.

The reason why I think that it doesnt react as quickly as the suby ecu, is that its this is funny little map that we have just found out how it works after like 2 yrs with being able to flash. IF it was a real main ignition offset map, it would have being defined as such much earlier.

My theory on why they even added it was for the varied climates and fuels that their vehicles end up being utilised.
With the stock map adjusted in ONLY a light load-cruise area, I think that they really wanted all that extra timing in those areas for throttle response, economy, but didnt want the loud pinging that would happen as people pull off the lights with bad fuel in hot climates.

Very high load areas were left at zero because the main maps would be enough for most stock vehicle situations.

As we have tuned our cars for exactly the fuel, climate, and mods we have- we will be able to use that extra map for that extra fine tuning etc that we may want.

If you had a funny knock problem that was caused by something like heatsoak, which comes and goes depending on the traffic, you could use the high det map to reduce timing in that area instead of the octane number moving slowly to get rid of the knock.

Im super stoked about how well it works with different octanes- of course I prefer to keep boost pressure the same for both 91 and 93 and just adjust timing. That just make it even easier for me to use this map.

Once we know how quickly the map works, Im sure it would work fine for upping the boost for 93oct and still have the timing advancing.


So--- quicker than octane adjustment BUT slower than Suby offset maps.

 

If there is a tutorial on how to calculate the MUT value of a given address I would log it (adding it to my MUT table, probably as 4x value) to see how much its adding at a given load/knock value and see how fast its reacting.

Anyone know what I mean? I can explain it but I dont know exactly what I need to look for if this is a disassembly solution or something else.

 

Another thing on the subject (but off topic), has anyone ever reviewed a timing retard of -10º between shifts?

This is w/o any registered knock and will occur only occasionally. Someone mentioned it could be a transmission safeguard

 

Regarding the subaru's IAM I am sure the evo ecu has this fetaure. Ecutek can display this information. I saw it myself while I was getting my evo tuned with ecutek. It is the same as subarus i believe. 1 indicates that no timing is pulled. as 1 goes down (i.e..0.96) the ecu pulls some timing. I believe this does not happen only because of knock but also other factors such as high intake temps on a dyno (from high boost and not efficient I/C). this is the reason why some tuners like to tune on the road. all cars lower their IAM on the dyno after a few runs (even with no knock)

 

What do you want to log?

 

Mrfred, the timing values on the low det table would be swell, so I can see how much timing its adding based on all the variables I am logging at the same time. I am not worried about the high det table for the time being.

 

try MUT33 or MUT04 - they are MUT's associated with IGN control