why you can't tune latency via the maf translation table

welaish · **Joined:** Tue Apr 29, 2014 4:48 am **Posts:** 946

I had the same issue recently, wasted a lot of fuel and mileage on logging. Installed FPR and modified Fuel lines. Nothing Worked.

Then I replaced the MAF sensor by a new one. everything went back to normal +7 and -7 (Short term)

ride5000 · **Joined:** Thu Aug 03, 2006 2:40 pm **Posts:** 1934

Kodename47 wrote:

ride5000 wrote:

ecuedit is far from perfect but i found it to be an amazing tool for analyzing and manipulating log data and incorporating those results directly into the rom.

This is why I suggested the above, it has most if not all of the benefits of Ecuedit but is free.

nice excel work!

the big difference is being able to navigate the surface of a map and have a separate window display data that fits that cell, but that's outside the scope of this thread (and more towards general map editing). i agree for the discussion at hand the method you've shown is absolutely equivalent.

Kim · **Joined:** Thu Jun 07, 2012 2:11 am **Posts:** 25

ride5000 wrote:

so after reducing latency by 30us (1.16 to 1.13ms) and decreasing the injector scale 3% (from 650 to 630cc/min) i got the following data from the drive home...

(assuming 30us = 3%)... Just wondering how you came to the 3% decrease? (was that a value you got from ecuedit graphing, or just a trial and error?). And you decrease all the latency values for all voltages?

Did changing your injector scaling/latency have any side-effects (such as needing to re-do your MAF scaling?)

trez0r · **Posted:** Sat Oct 14, 2017 11:49 am

Hey ride5000,
I know it's been a while, but when searching for that perfect latency, what error across the mafV rows did you settle on and called it a day in the end? I assume it wasn't perfect 0% across all IPW for any given mafV?

RomRaider

why you can't tune latency via the maf translation table

Who is online