![]() |
Quote:
|
Quote:
|
Quote:
On ECUtek you fill the table with values of 1, RR is 0. The IAT compensation isn't a simple hot/cold +/- as it reverses as air volume increases too. I would return the stock table when you've done calibration. |
Quote:
|
Quote:
|
Well I've done a couple set of CL and OL logs, and input them into vgi's tool (thanks btw for that). and one thing I noticed is my CL corrected MAF scale has hardly any corrections, maybe two points that are barely off. But when I do OL and there are a lot of corrections, and the corrections are mainly in the middle of MAF scale curve where as the CL corrections are only at the beginning and the end. My question is should I be combining the cl/ol corrections together? Also does this sound normal?
|
Quote:
might be worth just applying the CL corrections, then check the OL again after that. Yes sometimes you have to average them. The CL corrections should be somewhere around what your LTFT are the OL corrections will be the difference between the AFR measured and AFR commanded (in OL fuel tables). Make sure you do the logs at similar temperatures, wide temp variations will cause problems. If you could do them around 20-25 C this is ideal as that is where their is no temp compensations applied not always possible though. |
Thanks, I have been using Airboy's spreadsheet to find my AFR error %, what are you using for that? And unfortunately I have been doing all my logging after work when its about 32C, so maybe I should redo everything in the morning. After I get the MAF scale down is it worth looking at injector scaling with stock fuel system?
|
Quote:
When VGI utility came out re-did some more logs and just imported them into his utility (tactrix logs) with the OL fuel tables and MAF values , in less than 5 minutes it did what took hours and came up with same results. now I'd just use vgi utility for both ol/cl its magic. As long as you do logs at same temps it should be fine, just not some at 10c and others at 30c for the one calculation. |
Can I point out that to ensure you add the max/min correction % into the OL section. You will always get a big error shortly after the throttle opens and you do not want this to be used for corrections. The tool is set to 200% by default, what I'd do is load in the log like that, look at the data at the top of the columns and have a quick check over what seems a good limit to set. Clear the run data and load in the same log with the limit set to a sensible value, I usually shoot for 7.5-10%. That should help with the lump you get around 3v.
I also set OL min and CL max to 3v. |
Seeing as this is most relevant thread I thought I'd add this here. For those that have been wondering how to do the PI/DI scaling. This is a spreadsheet tool I've put together:
https://dl.dropboxusercontent.com/u/...libration.xlsx If you have any form of MAF scaled maps, use that to create 2 identical maps. 1 with 100% PI and the other with 0% PI, although I leave the standard ratio above 5200. Go and log data on each as if you were doing CL scaling. On my tool, input the MAF scale and use this for @vgi's tool as well. Then copy the corrected MAF scale (only the g/s with no smoothing) into my spreadsheet for both DI and PI results into the New PI/DI columns and voila.... As the MAF tool adjusts all values below the lowest recorded MAFv by the same correction factor, I find it's best to remove any duplicate error values in the low RPM range. Then use the % difference chart to work out where to set the max and min range as to avoid erroneous data having an impact on the injector scalar. You then can select which injector set to adjust if necessary. I would choose the range with the most positive trims/error, or whichever is the higher line on the graph. I would always look for the ideal correction to be at the higher voltage range as at lower voltage the PI system can have latency error as well. This will become obvious if the lines drift apart or get closer the nearer you get to 0v. I've also included a couple of columns for you to paste the DI fuel rail pressure for any adjustments you may want to make later. The last 2 tabs are for you to keep an eye on how much MAF variation your map has from the OEM map. This will allow you to see if there are other issues, like if you're bumping up the whole curve etc. Paste your MAFv range into the OEM adjusted column and it will calculate the correct g/s. Then paste your current scale into the current ROM columns. Any questions then please ask. |
I just went and took a nice hour long log to start scaling my MAF and then went to use Vgi's java app only to find I didn't log RPM. It might be worth noting that in the first post under procedure @steve99
It was stupid of me but I literally just logged what you had listed. Also can someone confirm what does OFT call the commanded AFR? Is it Equivalence RC? |
Quote:
|
Quote:
|
| All times are GMT -4. The time now is 03:38 AM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.
User Alert System provided by
Advanced User Tagging v3.3.0 (Lite) -
vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.