Here is one of the threads people are pointing you to... https://www.evolutionm.net/forums/ec...ing-trims.html

The only thing is... I don't think they are right, at least where it applies to the IX. There are a different amount of load/RPM cells in both of those tables for me and neither scale changed when I rescaled my ECU.

I have a bog for the first ~minute of the car running at really low load, but its generally fine as soon as I'm moving. I don't go anywhere near 100 load until I'm all warm and fuzzy though. This has been happening since before I rescaled.

EDIT: See post ~28 below

 

^ Yea... the ignition maps aren't the cause. This is a common EVO9 issue even when nearly stock. It's not really a problem because it goes away a minute later but you can tell the car is grumpy.

 

i think they are trying to get me here to the periphery bits so i can disable IGN WARMUP RETARD
https://www.evolutionm.net/forums/ec...hery-bits.html

 

Mattjin,
ROM ID 88590015 (Evo9)

let me know where these warm up ignition tables are please thank you!

 

You don't need him or me... they should be in the default ecuflash 1.41 defs

"Percent Low Temp Timing Trim vs Coolant Temp" - Timing section.

 

There is also the cold timing addition map, and most likely the temperature lockout of the MIVEC.

 

What about the "Base Low Engine Temp Trim" table? It is a timing table that retards timing in low RPM values. I belive it is there to rapidly warm up the CAT. If you re-scaled your timing to have higher load values, you essentially move some of the retarded timing values to cells that could cause issues.

I too had the same problem. Once I adjusted the table stated above, all is good to go. Also, different cams do not require as much negative timing to get the same result as stock cams when it comes to heating up the cat quickly.

If you are not running a cat, like most of us, the need for cold start ignition timing retard isn't necessary. The car will just take a few more minutes to get to operating temperature.

 

A HA! this is it! thats what i was lookin for. I updated my defs to v1.41 and there was the table you speak of. I zeroed all 3 of them and no more bogging!!!
Sweet, car feels like it should. I dont have a cat to warm up, so I zeroed the maps. If i still had a cat i would have probably put some effort into just decreasing the amount fo retard so that i would still warm the cat up faster, yet still get rid of the annoying bogging.

thanks again!

 

I hate to tell you this now, but if you want them completely gone all-together it is probably better to disable via the periphery than by zeroing out the maps. It also may serve some other function other than warming up the cat, but that is debatable (you shouldn't/can't run your car as hard when cold). I personally just lowered the trim % in the areas where I was having trouble.

 

Wow.... I've been away from this forum too long.

I'm glad that worked out.... Now here's the catch... I need to turn this off via periphery but I'm using ECUFlash 1.30 and I don't want to upgrade as I have an older cable.

Do you have a link that will work for me?

 

I think 1.35 shouldn't have any issues with the older cables, but I could be wrong. You should also be able to get the cable upgraded for free.

Worst case you can calculate the non-bit version for the periphery based off of what you already have. I believe mrfred posted a spreadsheet that should automatically calculate the proper value in his detailed mapping of periphery bits thread.

 

I adjusted my table to make the car run better. Big cams don't like tons of negative timing.

 

I apologize, I was looking through a few maps and found that the EGR advance is, in fact, on the same scale as the other timing table. In my rom it is labeled "High Oct EGR-Enabled Advance". There is one for low octane advance also, but it is simply zeroed out.

My apologies, the other tables I was looking at were 'EGR Duty', 'Base Timing Trim vs Load and RPM', and something else.