still no luck i did get the car to idle after i put my injector scaling to 232 with my current latancies and i had to push on the throttle in order to get it to start other then that it wouldnt turn over and when i reved up due to me pushing down on the throttle as i was letting go i wanted to die it was able to idle after a while but my afr was 10 to the low scaling and when i tried with a higher scaling i didnt want to idle even after me pushing on the throttle but i got a log of it and it kept on connection and disconnecting as the car was wanting to die so ill send them to you

 

Thanks for the log.

Seems there is a condition stoping the timing axis from loading correctly I'll look into what the heck is going on there. I also see blips in the AFR but the fuel actually looks like it got fixed. So possibly 1 down and 1 to go?

I'll see if i can't beg tephra to give me a hand

 

no prob glad one things is done just need to get the other fix man i gotta put my excitement to use this rom off for a lil longer haha and yea i hope he does two heads are better then one lol

 

Just incase this hasnt been touched on. When we load a whole new rom into our ecus its the same as unhooking the battery ie: the car has to relearn to idle everytime we flash between roms. Have you guys been taking this into account?

 

It really has more problems than just that timing is sky high which is a major issue. Its not properly getting the timing from the table at this point.

 

OK gotcha wierd.. Ok so I have a question for you. So I know for sure that with my tuned lancer rom for some reason the ecu takes values from much higher load cells in the fuel table than what I am logging. So now with this evo rom is it going to do the same thing or should it act just as an evo and I can now use 1byte load values for both timing and fuel tables?

 

Absolutely log 1byte load for logging it just takes the 2byte load and does a little math to make it fit in a 1 byte spot.

Calculated load is probably best set up for a 2.0L car anyways it should get very strange on a 2.4L.

You ever get your knock sensor happy? I found the knock values for a regular lancer they are a bit different than an evo.

 

Not yet I have kinda put tuning on the backburner been spending all of my free time clearing my land I aquired to get ready to build . I lowered my timing enough to allow me to dd with mild accel without major issue but I am still getting regular knock counts of 7-9 at wot and my timing is on average 3-6 degrees lower than my lancer rom throughout my operating range. One thing I dont understand is I have my open loop tables set identical to my lancer rom however with my lancer rom if I do even mild accell my WB drops to around 12.5 afrs but with my evo rom I can go wot and it consistently seems to not go into open loop until I hit 2500 rpms. Now I can adjust the table in the lower rpm range but dont understand why this would be? Especially since they are already set lower than the stock evo values so shouldn't it go into open loop even sooner than if I left them stock?

 

Ah the best table to modify is the open loop vs load one just set 500 and 1000rpm to like 50% and set the rest to 10%. This should put you in near always full time open loop minus the idle portion.

Something might be up with your maf scaling if you aren't going into open loop with full throttle at any rpm. Means the load is too low to induce open loop.

 

Ok that sounds like a good idea I will try that and see what happens that will make things much easier. I will have to doublecheck my logs but if I remember correctly it consistently switched into open loop around either 120 or 130 load.

 

Link I sent you an email with a request to log a couple items.

My thoughts right now tell me something is messing with the timing map address. If its some unknown code resetting it I'll just move it to a new vector.

The log doesn't have to be very long just a quick couple seconds of idle.

 

yea i got it and got the rom ready to be put on the car when i get off work tomorrow around 5 and dont worry the logs will be short if evoscan keeps messing up

 

Just don't let the car rev too much the timing is screwed up so I don't want to induce engine damage.

 

Ok so I have a question kinda off the subject again. I am (for now) running my lancer rom again until I can get some race gas and test the knock sensor with the evo rom, however I love the evo rom because it idles just slightly higher than with the lancer rom which fixes my small studder so which table to I adjust to raise the idle slightly after the car has warmed up?

 

The Lancer ROM has 3 tables for idle that are temperature based you can set. They are A/C on, drive and neutral. Adjust the neutral idle map from 750 to, say, 850. I believe 850 is what the Evos are set to idle at.