So last night I was doing some tuning on my car.

In my logs all of the logged AFR map values were nothing close to the values in my actual map's.

Any idea what might cause this?

 

they will never be true values... even timing

 

Read the "how to tune an evo" thread thats stickied at the beginning of this section. A great resource for newcomers.

 

May want to read before you tinker with your car...

 

If you disabled leanspool, they should be at least half ways close if everything is right -- no boost leaks, accurate MAS, correct injector settings in your tune, etc.

 

If it wasn't obvious from what jrohner said, you need lean spool disabled and correct MAF Scaling for it to be close. Things like open filters, hard intake pipes, and all kinds of other goodness will throw it off. The numbers in that table are only an equation-based representation of a number between 1-255.

 

Agreed that actual values will never match map values. But when I first read the OP, I thought he was referring to AFRMAP (loggable value in evoscan). That should match, or at least be real close.

edit: I forgot to say that if you are talking about AFRMAP, the logged value may need to be divided by 128 to read correctly.

 

dragging this slightly off topic here, What purpose is AFRMAP supposed to serve? I've never really paid much attention to it.

 

I assume you mean the AFRMap feature in evoscan? Its so you know which value is in the cell you are currently in basically. Not used all that much since Map Tracer was created.

 

AFRMAP is the value of the number in the fuel table the car is using at the point in time its logged. So litterally if your fuel map says 10.2 at 200 Load at 3500RPM your ARRMAP will read 10.2 in evoscan/equivalent.

 

If your timing isn't matching your maps you either have knock or a compensation map kicking in. Most likely knock.

 

Got it thanks

 

Why is map tracer in Evoscan is scaled from 0 - 100, when actual maps are scaled from 0 - 300

 

you have to right click on the gray area at the bottom and load your corresponding XML/HEX file for it to show up with the proper scaling.

 

Agreed I was gonna post this too, Good thing I read the whole thread!