View Full Version : Question on Tuning with AutoVE tutorial
kwhiteside
June 30th, 2009, 01:22 PM
I've went the the whole process now and must admit my AFR is now getting close to commanded and my idle problems seem to have gone away.
My question is about using the MAP Averages to tweak the VE table. The manual says to repeat as necessary till the averages are right around 1 everywhere. I made another 30 minute log while runing my modified Original Tune per the manual, Original_Tune_0000.tun and am thinking I need to adjust my VE table with the logged BEN Map to keep tweeking it till just right. I have questions about this process. If you look at my BEN Map below for the 4000 rpm range, all the average values are 1.0. So when multiplying, nothing should change. That is not the case. If I copy with labels, then paste > paste and multiply with labels, the 4000 rpm range does change as do many other cells that have no values in them. I've also shown the before I paste VE table then the after I paste VE table from the multiplied values of the BEN Map. What am I doing wrong here? The changes should be very subtle as most of my average values are already 1.0.
Also notice the 4 cells for MAP 15 and RPM 2800 to 4000. Those cells are so high that they take the VE table cells thru the roof.
mr.prick
June 30th, 2009, 01:33 PM
open the map's properties and increase the precision on the data tab.
you will see that 1.0 is not equal to 1.
5.7ute
June 30th, 2009, 01:33 PM
You need to up the precision in the map to at least 2 decimal places. Using only the 1 decimal point you will not see the 2% variation from 1.0 that you are after.
Click on edit map properties, hit the data tab & change precision to 2.
As for the low map areas that are reading high these need to be filtered out. It will be due to DFCO becoming active & giving you an extremely lean reading.
kwhiteside
June 30th, 2009, 02:21 PM
You need to up the precision in the map to at least 2 decimal places. Using only the 1 decimal point you will not see the 2% variation from 1.0 that you are after.
Click on edit map properties, hit the data tab & change precision to 2.
As for the low map areas that are reading high these need to be filtered out. It will be due to DFCO becoming active & giving you an extremely lean reading.
Ahhhh, after changing the precision to 3, I can now follow the calculations. Thanks for that guys.
Now, should I apply this to my VE table and flash it up, then drive and log some more? What about those 4 really high cells? Ignore them? what caused that?
Ken . . .
5.7ute
June 30th, 2009, 02:28 PM
Ahhhh, after changing the precision to 3, I can now follow the calculations. Thanks for that guys.
Now, should I apply this to my VE table and flash it up, then drive and log some more? What about those 4 really high cells? Ignore them? what caused that?
Ken . . .
Have you applied a filter set to the data log? If yes what are your filters? Do you lift your foot completely off the throttle to deccellerate?
Without seeing your log file I can only guess.
mr.prick
June 30th, 2009, 02:32 PM
It depends on whats going on there and what the cell count is.
It looks like either DFCO is on or you need a little more fuel when
the throttle is snapped closed.
I always ignore that area because usually I hit there when the throttle slams shut
coming out of PE and the cell count is low.
If that is throttle closed decel with DFCO off I would add a little bit of fuel there.
You should not have holes or peaks there.
Also the cells in the top right corner look like you turned off the car before stopping the log, exclude RPM less than 400RPM to your filter.
kwhiteside
June 30th, 2009, 02:35 PM
Have you applied a filter set to the data log? If yes what are your filters? Do you lift your foot completely off the throttle to deccellerate?
Without seeing your log file I can only guess.
Yes, I filtered the low temp and under 50 cell counts out like in the tutorial.
When slowing down fast in traffic I lift completely and go clutch. Oh, and I've also have been practicing some heel toe blips ( gotta work on the driver too ) I put my log in if you want to open it.
kwhiteside
June 30th, 2009, 02:37 PM
Also the cells in the top right corner look like you turned off the car before stopping the log, exclude RPM less than 400RPM to your filter.
Right you are sir. You're like a visionary. I'll exclude them.
kwhiteside
June 30th, 2009, 02:38 PM
Argghh, wish I could figure out how to turn that signature off by default
kwhiteside
June 30th, 2009, 02:48 PM
It looks like either DFCO is on or you need a little more fuel when
the throttle is snapped closed.
DFCO comes on in those ranges from .8 up to 1.5
5.7ute
June 30th, 2009, 03:04 PM
Add to your filter set excluding where TP is less than 1%. Also forget heel toe blips etc when trying to get data. You will just bring errors in that will need filtering out later. Good steady state data is the key when doing the autove process.
kwhiteside
June 30th, 2009, 03:20 PM
Add to your filter set excluding where TP is less than 1%. Also forget heel toe blips etc when trying to get data. You will just bring errors in that will need filtering out later. Good steady state data is the key when doing the autove process.
OK, I'm going to scrap this log and do another without blips and keep it smooth. But I'm heading down the right path to flash this up right?
At this point I still have c2901 and c2903 set to 1. Which parameters define weather the MAF is on or off? I ran the AutoVE with the MAF plugged in so it would get the IAT, but I think some setting from the tutorial caused the MAF to error out even though plugged in. I'm trying to figure out what the AutoMAF piece is. Somebody said, turn MAF back on and keep going thru process. Please elaborate for me.
Thanks for working with me BTW
5.7ute
June 30th, 2009, 04:24 PM
C2901/C2903 set to 1 will fail the maf as you have done, while still allowing you to use the IAT sensor.
To do automaf once you have dialled in autoVE turn C2901/C2903 back to stock. B0120 to 400. (This will make the PCM run exclusively off the maf.) Make a map to copy the maf tables & do the same as AutoVE except this time you are paste/multiplying the Ben factor to the maf transfer curve.
kwhiteside
June 30th, 2009, 10:18 PM
Thanks for all your help guys. My car is going back up in the air tonight for brake ducts. I should be back in tune mode on Friday. I think I understand what you have described. Hopefully I can figure out the MAF / MAP process.
So after this I should be pretty much have a base tune? Is this the process the pro tuners use, but replacing my street driving / logs / map with dyno runs / logs / maps ?
joecar
July 1st, 2009, 02:35 AM
You're on the right path, as posters above indicated...:cheers:
Failing the MAF (you should see a MAF DTC, one of P0101, P0102, P0103) causes the PCM to failover to the VE table (allowing you to tune it).
Check that you do get one of those DTC's.
A pro tuner may do this if he spends a few days with your car @ $600+ per day... as a matter of time, the pro tuner will not be able to hone everything in like you would (you have much more time on your car than a pro tuner would have)... in all fairness, the pro tuner has to pay the rent so he has to push several cars thru each day.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.