![]() |
Quote:
|
Quote:
|
Quote:
|
Quote:
What sort of temperature ranges are you seeing? What you could do is widen the x axis rather than change the values in the table. |
Quote:
|
Quote:
|
|
Quote:
|
Quote:
|
Are there really only 4 LTFT ranges for this car? I know on my STI there were LTFT A, B, C, D, each with a progressively higher g/s range (I *think* D was >40 g/s), and then D would be what was applied during open loop WOT, so although the fuel trims weren't linear with mass flow rate it still attempted to account for that.
Disclaimer here - I'm only monitoring fuel trims from the Torque app, which is reported as "LTFT1", so not sure if that has anything to do with it. I feel like I see a lot more than 4 ranges of fuel trims. It almost seems that there's a crossover around 3k rpm... if I'm cruising at under 3k rpm at a given highway load, and then speed up to over 3k rpm, the fuel trim changes although the flow range is constant. It goes from postive something to negative something. Maybe port/DI transitions? |
Quote:
I suggest you do not mess with your log files at all. Just click on 'Load Log' when it promts you if you would 'like to reset column name or filters' click yes and makes sure all is set correctly: select your columns, set filters to filter out non-OL data, click ok. When you select Throttle Open Angle depending on what tuning solution you use you can use Trottle Position or Accelerator Pedal Angle. It's preset at 85% but I STRINGLY suggest you should take a look at the log curve and determine when transition happens from OpenLoop to CloseLoop and vice-versa for the parameter you decided to use. Eg. http://i846.photobucket.com/albums/a...ns-filters.png After you click OK the columns for different WOT runs populated. If you see too few data rows - that means at a brief point you had full throttle but you probably didn't do WOT run to redline. I would suggest to copy last column wot run data over the column with few data rows. If you still have WOT run columns empty and have more logs - just repeat the process except this time you can skip setting column names (unless you changed column names :) ) and filters. so, click on 'Load Log', click 'no' to the prompt to reset columns/filters. You should see more WOT columns populated. you can have up to 12 WOT runs loaded. if you have pasted current MAF scaling already then just click 'go' PS you can play with finetuning the filters or ask Kodename47 for best settings - he has spent a lot time on that. PPS @everyone Please, if you have gone through Usage tab and if something is not clear or is not covered - send me revised Usage text once you've learned whatever was not clear or not covered. you're getting helped, so pls help others. |
|
Quote:
|
@ML if you're trying to do logging to make changes ensure you stick to 1 main principle and you can use 1 log for both OL and CL: Only go WOT when logging a complete pull. You only really need 2/3 for the tool to work properly. For CL changes you only need partial throttle and I tend to try and vary pedal movement to change the throttle plate angle but rarely go above 3.5k. I find using different gears and slowly going up the range works quite well.
I think the setting you really need to look at is the AFR Error +/-%. If you don't change that, your tip in throttle will show massive positive trims and artificially raise your curve. If your NA I would have it set exactly as @vgi posted above. What I would do is load in your runs with the filter set to default (200) and then look at the individual runs and see what the maximum genuine error is throughout the curve. If you're NA it should be no more than 5-10%. If that's the case, clear the run data, reload the log but change the filter to just above the max genuine error and the resultant curve will fall back into place. |
| 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.