Hello,

I searched for "math parser" here and only found a short post from 15 years ago. A quick search online got me to the Math Parser Functions page but I haven't yet read any MS forum posts. Creating a custom filter looks easy but I am signed in on my HTPC with only a few, older data logs. It looks like I can load multiple log files into MLV and limit VE Analyzer adjustments to only use data close to 70F MAT (100% density in my curve). I didn't get any errors when I typed "MAT Min 66 Max 74" but these log files start around 80F and only goes higher, I need to check on my tuning laptop.

Fuel VE and idle VE tables are close and it runs great but I want to really dial it in. Then only tune again if/when I upgrade injectors and/or the turbo and exhaust. This year I richened the fuel VE table after installing the new, higher flowing FM manifold and outlet pipe. It's leaned back out and close again but last year my tuning sessions felt like a game of ping pong. It would adjust slightly leaner one day, then slightly richer the next time I tuned. My thought was as temps are dropping this Fall, to take multiple days/weeks of data logs and only allow data near 70F to adjust the table, then slightly smoothing and leaving it. EGO can adjust from there. Maybe then I could start reading plotted data charts looking for trends to slightly tweak the MAT curve to further reduce EGO corrections?

Does my custom filter look to be correct, am I missing anything? Thank you.

 

After a little more research it looks like my custom filter would need to read [MAT] > 65 && [MAT] < 75. That should filter out making VE changes outside of 66F - 74F MAT. I can download SDcard logs from longer drives over the next 2-3 weeks and load them into MLV using that filter. It's been a while so my memory might have faded but it felt like data logs from hotter days led to fuel VE being adjusted richer and cooler days data adjusted the table leaner. It felt like VE Analyzer wasn't taking air density corrections into account.