PDA

View Full Version : I tried the new twist on tuning. Can someone look at my log.



Bill00Form
February 11th, 2012, 02:03 PM
This was my first attempt at the auto tune and wanted to know if my VE table makes sense. Some of the values seem a little low. This is a 427 firebird, tfs 235 heads, 6 speed, with an 85mm MAF. Thanks

12665

joecar
February 12th, 2012, 07:27 AM
Please post your calc_pids.txt file.

Bill00Form
February 12th, 2012, 09:05 AM
Ok, here it is. I also went to the track and logged a run with my current tune. I will include that log. Appears that it's lean until I get into the throttle and then it goes rich. Great weather today other than a strong head wind. Real unusual for it to be so cool during the day in south florida. I had a new best 60 foot (1.58) but it doesn't run like it once did. Ran a 10.75 at 129.95 with a case of coke, cooler and ice in the back.

thanks again for the help.

joecar
February 12th, 2012, 05:23 PM
Did you use CALC.VET.% or CALC.VET.g*K/kPa...?

Can you post the tun file that produced the log file Log_0001race#1.efi in post #3.

Looks to me like the MAF is not corrected, and possibly also the VE.

Bill00Form
February 13th, 2012, 01:38 AM
I tried to change to value rather than percent so the engine size doesn't have to be entered in the scan software.

The first log was based on a changed ve table, changed injector flow rate, change cylinder volume value and changes recomended by forum notes. I did wonder after if I should make the rpm threshold for airflow calculation from 4000 to 400.

The second log (race) should have been my original tune.

Bill00Form
February 13th, 2012, 06:33 AM
I need to verify the scanning tune file tonight. On one I removed the tuning adjustments for scanning and adjusted the MAF table based on my tuning log.

My original tune wasn't adjusted for cylinder volume and had a value of 2000 for the rpm threshold for airflow calculation.

Bill00Form
February 13th, 2012, 01:15 PM
The scanned tune file was the correct one. thanks

joecar
February 13th, 2012, 03:27 PM
So 00FORM110409NorrisTune255tires373_0001.tun (http://forum.efilive.com/attachment.php?attachmentid=12672&d=1329136677) produced Log_0001race#1.efi (http://forum.efilive.com/attachment.php?attachmentid=12668&d=1329076765)...?


In both tun files I see these out-of-range warnings:


Out of Range calibration summary: 06:21:15 pm, Monday Feb 13, 2012

Engine Calibration.Spark.General
{B5919} Optimal Timing, contained one or more out of range values when loaded.

Engine Diagnostics
{C6002} Engine DTC MIL Enablers, contained one or more out of range values when loaded.


You can fix those as follows:
- first change the blue dog-eared cells to some in-range non-max/non-min value, and save file, exit tunetool;
- then open file, and set those cells to the desired values (which will be in-range, and save file.

Bill00Form
February 13th, 2012, 03:33 PM
yes to your question.

joecar
February 13th, 2012, 03:36 PM
After you fix the OOR values, save the file (do Save As so the suffix bumps to _0002), cal flash it, and do another iteration...

this time take screenshots of the scantool maps (VE and MAF) and post them here.

I think what was happening is that in your initial attempt you may have not covered enough operating range, so then when you raced you got divergence.

joecar
February 13th, 2012, 03:42 PM
yes to your question.Ok, your VE table looks ok...

so then look at post #10.

Also, to more easily correlate log files to tune files, do this:
- name your tune files something like this: xyz_0001, xyz_0002, etc.
- name your log files something like this: xyz_0001_000x, xyz_0002_000x, etc. where x increments.

[ e.g. so you know xyz_0002_nnnn.efi came from xyz_0002.tun ]

Bill00Form
February 13th, 2012, 04:47 PM
Thanks Joe,

Would you confirm that when I'm scanning for adjustment of both the MAF and VE table I still change the rpm threshold for airflow calculation to 400?

joecar
February 13th, 2012, 05:02 PM
Yes, B0120 threshold set to 400 rpm is fine.

The idea is to disable the VE thru-out the operating range... 400 rpm is below idle (cranking speed).

Bill00Form
February 17th, 2012, 06:31 AM
thanks, how/when do I do the sreen shots?

joecar
February 17th, 2012, 07:27 AM
thanks, how/when do I do the sreen shots?See post #10 here: Hosting-an-Image (http://forum.efilive.com/showthread.php?3064-Hosting-an-Image&p=157777#post157777)

Take screenshots of the scantool VE (CALC.VET) and MAF (CALC.SELBEN) maps (i.e. just before applying them to B0101 and B5001 in the tunetool).

Make sure you apply the transient filter prior to taking the screenshots.

Bill00Form
February 18th, 2012, 08:44 AM
Here is my log from today. I eliminated the out of range items in the tune file and uploaded it in the car.

I will try to figure out how to do the screen shots. Thanks

Bill00Form
February 18th, 2012, 10:51 AM
Here are the screen shots

joecar
February 18th, 2012, 06:32 PM
Those values in those maps look reasonable.

You should add an extra decimal digit of precision to the SELBEN MAF map (see Precision on the Data tab).

Be sure to apply the transient filter and remove empty cells (those with low cell count; there'a a button for this).

Also, you can make your SELBEN MAF map have a narrower appearance by setting the cell size (see on the Cell tab).


I'll look at your log file before Monday (using the same calc pids file as in post #3 above, right?).

:)

Bill00Form
February 19th, 2012, 01:32 AM
Thanks again. I made no changes to the text file. At some point, I did add the wide band afr value pid but I can't recall if it was after the first post. That was the only change.

I setup the filtering as suggested in one of the posts. There were filters for engine temperature, throttle position change w/in a specific time, lamda over 1.06(?) and rpm below 800. I thought I entered a cell count filter but don't see it right now. I'll have to check later.

Bill00Form
February 19th, 2012, 01:57 AM
ok, under map properties, i set a minimum of 15 as not to be considered empty.