MAF Scaling - Open/Closed Loop Fueling info

[Kodename47]

Originally Posted by 1Cor10:23

Anyone have a direct link / mirror to VGI tool? RR website is down...thanks!

Download from Github

https://github.com/vimsh/mafscaling

[RustySocket]

Originally Posted by Kodename47

The reason you can't copy Excel direct to Romraider is that it expects the top left cell to contain [Table2D]. You can use excel if you offset the top row 1 to the right and add that in. It'll look odd at the 2 rows won't line up but it'll work Obviously the Copy Romraider option does that for you. See what happens if you do that and then paste to Excel....

You'll never get a log with just CL. There are multiple reasons the ECU switches to OL. Throttle angle, speed and the OL fuel map are all factors. Realistically I doubt you'll get much reliable data above 2.5V.
@solidONE just use the log stats screen if you want to start playing with IAT compensations. I do everything in that tab, including MAF changes. It's quite powerful.

So when I'm using the VGI tool (notice some of your work is included in there as well ) should I set the MAF voltage filter to 2.5, 3.0 or 5? when working on the closed loop MAF scaling. Obviously I could take the log and remove all the OL data in Excel first. I'm just trying to grasp how the tool works and the best way to get a good MAF scale for my sensor.

[Kodename47]

Originally Posted by RustySocket

So when I'm using the VGI tool (notice some of your work is included in there as well ) should I set the MAF voltage filter to 2.5, 3.0 or 5? when working on the closed loop MAF scaling. Obviously I could take the log and remove all the OL data in Excel first. I'm just trying to grasp how the tool works and the best way to get a good MAF scale for my sensor.

The whole idea of the tool is that there is no need to do anything in excel 1st. The filter is really there so you don't overlap if you're scaling both. The minimum cell count will ensure no changes happen if there's not enough data in the upper voltages. If you're just doing the CL scale then you can leave set high.

[RustySocket]

Originally Posted by Kodename47

The whole idea of the tool is that there is no need to do anything in excel 1st. The filter is really there so you don't overlap if you're scaling both. The minimum cell count will ensure no changes happen if there's not enough data in the upper voltages. If you're just doing the CL scale then you can leave set high.

OK, so that makes sense, Leave the voltage at 5 and the minimum cell count will remove data that is noise. Should I just leave the minimum cell count at 30 then? I'm assuming the cell count is not just total individual data points but actual contiguous blocks of data within a given time stamp?

[Kodename47]

Originally Posted by RustySocket

OK, so that makes sense, Leave the voltage at 5 and the minimum cell count will remove data that is noise. Should I just leave the minimum cell count at 30 then? I'm assuming the cell count is not just total individual data points but actual contiguous blocks of data within a given time stamp?

It's just individual data points. If you think you're getting good data, reduce the dV/dt filter, I usually use 0.3 or 0.35. It will massively reduce the data but make it far more reliable, you need a long log though. You can always rerun the same file with different filters to see how it changes the results. Also, I do set max AFR to 16 so that I capture as much data as possible.

[1Cor10:23]

Originally Posted by Kodename47

Might I add that vgi's scaling tool is designed to be able to scale open loop even if LTFTs are being applied so if you collect enough data you can do a complete OL and CL scale in one. Meaning you should be able to get the car running on point in one go without having to go and re-flash/reset the ECU.

Could you brake down how you would approach this?

My hypothesis is...

-6x WOT pulls
-30 minutes cruising highway
-15 minutes in parking lot (still necessary?)
-rest miscellaneous driving around town

When putting into VGI, would you chop up the log for OL to just include the 6 pulls and nothing else? Or just use the full log for both in one go?

If just upload the full log in one go, would I be correct in assuming you put in baseline MAF scaling into both the OL and CL tab and then load the datalog into both the OL and CL tab, and then generate on rescale tab?

Thank you!

[Kodename47]

Originally Posted by 1Cor10:23

Could you brake down how you would approach this?

My hypothesis is...

-6x WOT pulls
-30 minutes cruising highway
-15 minutes in parking lot (still necessary?)
-rest miscellaneous driving around town

When putting into VGI, would you chop up the log for OL to just include the 6 pulls and nothing else? Or just use the full log for both in one go?

If just upload the full log in one go, would I be correct in assuming you put in baseline MAF scaling into both the OL and CL tab and then load the datalog into both the OL and CL tab, and then generate on rescale tab?

Thank you!

Realistically you only need a couple of WOT pulls and 30 mins of normal driving. The more you get of either then the better the data will be though. Sitting at idle is rather unnecessary. You don't have to cut up any of the logs (except to remove the headers in OFT). The OL portion only looks for WOT data anyway.

Put your current scale into the CL tab and see what the Max V that has been corrected. Then copy that scale into the OL tab and ensure that the Min V is set above the corrected area from the CL scale so there is no double correction. Then smooth out the cross over area as there is likely to be differences.

[1Cor10:23]

@Kodename47

3 Quick questions:

1. On max and min v, I thought you should set those beforehand to around 3?

2. Also, would it be safer to scale for CL first and flash again before going WOT for OL logging just in case the base MAF scale is quite a bit off? I'm going to scale for Perrin's 3" CAI using their supplied table as a base.

3. Do you need the car to "learn" new tune before logging for MAF scaling? I will have to flash the Perrin supplied MAF scale first.

Thanks!

Sent from my SM-N920W8 using Tapatalk

[Kodename47]

Originally Posted by 1Cor10:23

@Kodename47 on max and min v, I thought you should set those beforehand to around 3?

Sent from my SM-N920W8 using Tapatalk

You could, that's a valid option. I just look at the point where it decides to stop making corrections on one and then set the limit on the other. You can easily see that in the graphs.

[1Cor10:23]

@Kodename47 Ok, that totally make sense. Sorry, I added a few more questions to the above post while you were responding! I think I'm getting very close to getting a grasp of everything, read the entire thread once over and have a few gaps in understanding in post above...

Thanks!

[Kodename47]

Originally Posted by 1Cor10:23

2. Also, would it be safer to scale for CL first and flash again before going WOT for OL logging just in case the base MAF scale is quite a bit off? I'm going to scale for Perrin's 3" CAI using their supplied table as a base.

3. Do you need the car to "learn" new tune before logging for MAF scaling? I will have to flash the Perrin supplied MAF scale first.

2. It honestly doesn't matter.

3. No need to let it learn, the LTFT+STFT should pretty much result in the same outcome.

[vgi]

Originally Posted by solidONE

What if you only want to process high intake temp data? That would be cool if they also had a min temp setting as well. Can come in useful for tuning for high temp and to do MAF IAT compensation tweaking for specific temp ranges.

MAF scaling should not be done with high IATs due to IAT compensation, thus there is no min filter.

If you want to play with IAT compensations you should use IAT Comp tab which is a different tool within the program.

Or as Kodename has suggested you could use a bit more manual approach and use Stats Tab. Pretty much anything can be done with that one but it's more involving process.

I haven't been here for a while, so the best way is to pm me. Better yet, pm @KOdename, he has played/tweaked his car a lot and knows way more

[solidONE]

Any foreseeable problems using @vgi's tool with multiple logs patched together as one large log? There will me multiples of the same time cells depending on how many logs you patch together.

[Kodename47]

Originally Posted by solidONE

Any foreseeable problems using @vgi's tool with multiple logs patched together as one large log? There will me multiples of the same time cells depending on how many logs you patch together.

You can load multiple logs into it, no need to join them up