MAF Scaling - Open/Closed Loop Fueling info

[Toyota John]

I was able to get my trims down to + or - 5% which is way better then what it was stock. Seems to have fixed my driveablity problems with the lean spot transitioning from closed loop to open loop after shifting. I have more work on my MAF scale to get the trims lower but at least now I don't have to use my custom F'ed up fuel map I made to minimized the transition area. I found the IAT compensation map that you said to disable for logging. What are the other compensation maps I should disable while MAF logging? Also what is the best way to blend closed loop and open loop MAF scales together?

[Kodename47]

Originally Posted by Toyota John

I was able to get my trims down to + or - 5% which is way better then what it was stock. Seems to have fixed my driveablity problems with the lean spot transitioning from closed loop to open loop after shifting. I have more work on my MAF scale to get the trims lower but at least now I don't have to use my custom F'ed up fuel map I made to minimized the transition area. I found the IAT compensation map that you said to disable for logging. What are the other compensation maps I should disable while MAF logging? Also what is the best way to blend closed loop and open loop MAF scales together?

Other table worth doing is the Engine Load Compensation table.

The easy way to do the OL and CL scale is to do the OL part 1st and then use the new scale from that and put it as the CL original MAF scale. If you use the cut off voltage option to ensure that there's no cross over then it works fine. You can also use the spreadsheet I posted a while back: MAF Smoothing Spreadsheet.

[phrosty]

Originally Posted by Kodename47

Discount any data that has a low count, I would look for at least 15-25 minimum for reliable data.

What I do is count the number of seconds spent in that MAF bin. Also, because I lerp the correction between two bins (I believe vgi's tool does this too), if 90% of the correction goes in bin A, 10% in bin B, the bins will also get the same proportion of time associated with them, so A would get 90% of 0.1 seconds and B would get 10% of 0.1 seconds, etc.

[Toyota John]

Originally Posted by Kodename47

Other table worth doing is the Engine Load Compensation table.

The easy way to do the OL and CL scale is to do the OL part 1st and then use the new scale from that and put it as the CL original MAF scale. If you use the cut off voltage option to ensure that there's no cross over then it works fine. You can also use the spreadsheet I posted a while back: MAF Smoothing Spreadsheet.

Ok so I would run the closed loop first, than open loop and then with the finished open loop add that to the closed loop scale and run closed loop again? Would there be any benefit to disabling the accel enrichment for the logging as well?

[Kodename47]

Originally Posted by Toyota John

Ok so I would run the closed loop first, than open loop and then with the finished open loop add that to the closed loop scale and run closed loop again? Would there be any benefit to disabling the accel enrichment for the logging as well?

Go and do one log and collect all the data you need for both OL and CL. Do your OL scaling 1st, then paste the corrected MAF scale from that into the current MAF scale for the CL screen. Just make sure the areas that are being corrected don't overlap by using the MAF Voltage Maximum parameter.


I've not diabled the accel enrichment, the idea is to be smooth with the pedal for the CL and you filter out excessive trims in OL which means that there is no need to.


Feel free to upload a log and I'll put it through to see how it compares with your result. Sometime the key is to not use too many filters to check over your data, use the range of graphs to visualise it and then re-run the log and reduce the filters to suit.

[Toyota John]

Originally Posted by Kodename47

Go and do one log and collect all the data you need for both OL and CL. Do your OL scaling 1st, then paste the corrected MAF scale from that into the current MAF scale for the CL screen. Just make sure the areas that are being corrected don't overlap by using the MAF Voltage Maximum parameter.


I've not diabled the accel enrichment, the idea is to be smooth with the pedal for the CL and you filter out excessive trims in OL which means that there is no need to.


Feel free to upload a log and I'll put it through to see how it compares with your result. Sometime the key is to not use too many filters to check over your data, use the range of graphs to visualise it and then re-run the log and reduce the filters to suit.

Ok seems to be good now. Trims are under 3%+or-. Most are +or-1%. The +or- 3% seems to show up under throttle changes which I think is normal? Thank you for your help this fixed my lean spot transitioning from closed loop to open loop and the after shifting stumble is gone. Good work on the MAF scaling program @vgi. Thank you for your hard work.

[troek]

i noticed my LTFT is -7 to -10 at idle, so im gona give this a try. very useful thread.

[Kodename47]

Originally Posted by troek

i noticed my LTFT is -7 to -10 at idle, so im gona give this a try. very useful thread.

Note which injectors are at use at idle. It changes depending on the coolant temperatures which may impact the results.

[troek]

hmm i didnt have that channel selected to data log. this is at idle while fully warmed up(190 coolant temp).

[Kodename47]

Here's an idle log I did a while back:





FYI:
1 - PI
2 - DI
3 - Both

[troek]

cool, thanks. so after 62 degrees it stayed at DI?
when i try to load a datalog with VGIs program, i get this error "Error parsing number at line 2: java.lang.NumerFormatException: For input string: "OpenFlash Data File 1"

i logged all the channels quoted in the OP. is my log the wrong file format?

[steve99]

Originally Posted by troek

cool, thanks. so after 62 degrees it stayed at DI?
when i try to load a datalog with VGIs program, i get this error "Error parsing number at line 2: java.lang.NumerFormatException: For input string: "OpenFlash Data File 1"

i logged all the channels quoted in the OP. is my log the wrong file format?

The first 2 or 3 lines of the log file contain some rubbish just delete them just leave the headers for the data like ol/cl rpm mafv

ect

Vgi program does no like it :-)

[Kodename47]

Originally Posted by troek

cool, thanks. so after 62 degrees it stayed at DI?
when i try to load a datalog with VGIs program, i get this error "Error parsing number at line 2: java.lang.NumerFormatException: For input string: "OpenFlash Data File 1"

i logged all the channels quoted in the OP. is my log the wrong file format?

Try removing the rows above the column headers.

[troek]

Originally Posted by Kodename47

Try removing the rows above the column headers.

i read that on the usage tab, and for some reason it didnt register until you mentioned it. thanks!