my logged timing doesn't match what's in the map. on lower loads there's minimum 1 degree difference and on peak loads I see logged timing 2-3 degrees lower compared to map timing. thought it was some interpolation issue, so put a block of 3's at peak load, got 1* in log. put 0's, got -2* etc.
timing trim vs air temp is zeroed out except first and last cells. in evoscan I've touched nothing, just installed it and ticked 'timing adv.' in eval it says x-20, request ID says 06. using rom 96530706 v7. any help is appretiated

 

Log "timing map ".

Look for a periphery bit that pulls timing too. Weird unknown timing pull at cruise which I found ends up more than just cruise. Also verify if your rom bases timing from uncompensated or compensated load

 

If there is no knock the only other modifier I can think of is intake air temp. Didnt disable the knock sensor and end up on the low octane map?

 

https://www.evolutionm.net/forums/sh...age=5&t=628272

See if there's any help there

 

211ratsbut
I have that wierd bit disabled

Aaron, knock was max 2 counts, that won't pull whole 2* timing I think
as about intake temps, as I've posted in op, timing trim vs air temp is zeroed out except first and last cells. and there isn't such low or high temps outside to touch that thresholds

 

Remember that you have to compensate your load values with baro to read your timing maps correctly...
Cheers.

 

Does your 2byte-to-1byte multiplier in the rom match evo's and formula? EGR advance at cruise will add timing above the timing map if you see an advanced timing variance in that area.

-Jamie

 

yes, formulas are same

it's an evo4, doesn't have egr system at all from factory, but I don't remember if I have disabled that from rom

 

Log timing map have you done that? It helped me ...

 

no, haven't got the chance to log yet mate

and what will I get from logging it ?


p.s. just opened evoscan and there's no such item named 'timing map' in the list o_o

(2.7 version)

 

try mut33 and same formula as timing adv.

Look to see if your timing map matches your timing adv. If so then there is an error some where else. If the timing map matches where your load and rpm represent then you have something that is modifying timing advance.