MSNS extra AFR tables

[ovlov760]

overlooked this old thread about it.
http://www.turbobricks.com/forums/showthread.php?t=28027&page=1&pp=25
Is the AFR table used instead or along with the VE table? Does it really work? Being able to just enter a AFR into the table and let it fly seems to good to be true. Is there anyways to for MT to generate a VE table based on a AFR table?

[the poi]

think of it like standard EGO correction, but with variable setpoints. It'll use your maps, and trim fuel to the target AFR. I liked it a lot, I could tune in really cold weather, and when the maps would "naturally" be a little richer during hot weather, they can trim to the targets. It works great for taking care of natural "bugs" like that - heat, barometer, fuel mix differences...

and although there isn't a native way to get MT to make an AFR table matched VE table, that is the idea behind the Matt Dupuis/Poi spreadsheet :) You do a lot of datalogging, drop the gathered data into the spreadsheet, and then it will analyze your actual AFR's against a "map" of target AFR's, and suggest new VE bins. Repeat the process a couple times, nd you end up witha pretty solid map

[nohbudi]

think of it like standard EGO correction, but with variable setpoints. It'll use your maps, and trim fuel to the target AFR. I liked it a lot, I could tune in really cold weather, and when the maps would "naturally" be a little richer during hot weather, they can trim to the targets. It works great for taking care of natural "bugs" like that - heat, barometer, fuel mix differences...

and although there isn't a native way to get MT to make an AFR table matched VE table, that is the idea behind the Matt Dupuis/Poi spreadsheet :) You do a lot of datalogging, drop the gathered data into the spreadsheet, and then it will analyze your actual AFR's against a "map" of target AFR's, and suggest new VE bins. Repeat the process a couple times, nd you end up witha pretty solid map

gimme

[the poi]

sigged yo