Total timing with 87 octane, 2002 5.3 Z71 Silverado
#11
Am using fuel trims, with copy, paste special x 1/2.lop..
I actually have a hardwired AEM wideband, that I know can be used with the HPTuners, but again, it goes back to me not keeping current with the abilities of both me and the software. In other words, I have absolutely no idea how to tune using wideband AFR error....sad but true.
I can't upload the VE tuning "tune" until I'm back at work tomorrow.
I actually have a hardwired AEM wideband, that I know can be used with the HPTuners, but again, it goes back to me not keeping current with the abilities of both me and the software. In other words, I have absolutely no idea how to tune using wideband AFR error....sad but true.
I can't upload the VE tuning "tune" until I'm back at work tomorrow.
#12
BTW, I tried running it in open loop, and it was so lean, that my wideband was pegged lean...
I did some quick reading, and it looks like connecting the MPVI to my AEM wideband is very simple. I just need to run a 2 wire jumper harness over to the console area that can allow me to quick connect to the HPT.
I did some quick reading, and it looks like connecting the MPVI to my AEM wideband is very simple. I just need to run a 2 wire jumper harness over to the console area that can allow me to quick connect to the HPT.
#13
TECH Senior Member
iTrader: (2)
It happens, the first time I went open loop wideband tuning it was in the 16-17 range while driving, no big deal at low rpm cruise speeds.
After the first 15-20min log of getting data and putting it towards the VE table it brought everything right back down to 15ish. Only took me like 3 maybe 4 log files to get my VE dialed in.
After the first 15-20min log of getting data and putting it towards the VE table it brought everything right back down to 15ish. Only took me like 3 maybe 4 log files to get my VE dialed in.
#14
It happens, the first time I went open loop wideband tuning it was in the 16-17 range while driving, no big deal at low rpm cruise speeds.
After the first 15-20min log of getting data and putting it towards the VE table it brought everything right back down to 15ish. Only took me like 3 maybe 4 log files to get my VE dialed in.
After the first 15-20min log of getting data and putting it towards the VE table it brought everything right back down to 15ish. Only took me like 3 maybe 4 log files to get my VE dialed in.
Sorry to be a pest, but OPEN LOOP is where I should be, when I get the wideband sync'ed with my HPTuners, correct?
I attached my last "tune" TRY, which I literally threw in the recycle bin (and put it back to my old tune for now), because it just wasn't falling into line for me..., and the VE tuning flash I am using, below...
I appreciate the help... I feel like an idiot for having the software and the wideband, and just not keeping up with it...
Last edited by rel3rd; 02-01-2017 at 09:58 AM.
#15
TECH Senior Member
iTrader: (2)
If you are using the wideband to tune it, yeah you want to disable closed loop and the fuel trims. Even disable COT and DFCO so they don't skew things.
Once things are tuned you can enable closed loop and fuel trims again then see how it runs. Making minor adjustments from there.
Once things are tuned you can enable closed loop and fuel trims again then see how it runs. Making minor adjustments from there.
#16
If you are using the wideband to tune it, yeah you want to disable closed loop and the fuel trims. Even disable COT and DFCO so they don't skew things.
Once things are tuned you can enable closed loop and fuel trims again then see how it runs. Making minor adjustments from there.
Once things are tuned you can enable closed loop and fuel trims again then see how it runs. Making minor adjustments from there.
The wideband hookup will have to wait a bit. I "think" I have the proper settings in my configs, but if it's anything like my past luck, probably not...lol.
#17
Just to update...
I gave it one last try yesterday after work...
The VE still seems to want those big numbers.
VE tuning flash has the MAF, LTFT, PE, all disabled.
Had to tweak and reflash 4, maybe 5 times.
Truck kept running noticeably better and better after each flash.
Majority of my VE logs showed negative fuel trims, so I re-enabled the MAF, LTFT's, and PE, and logged the drive to work this morning.
LTFT's were -5% or less (most -4%)
STFT's were averaging -2% to -3%
WOT AFR was right at commanded of 12.2 according to my wideband (not connected through HPTuners)
I'm guessing the VE numbers want to be where they are?
One log, just for the heck of it, I set the ones that are 120-130 at 90, and the whole log was RED, adding 25 or more % fuel...
attached my VE tuning flash, and my current "finished" tune, with LTFT's, PE, and MAF all back in play.
Any feedback?
I gave it one last try yesterday after work...
The VE still seems to want those big numbers.
VE tuning flash has the MAF, LTFT, PE, all disabled.
Had to tweak and reflash 4, maybe 5 times.
Truck kept running noticeably better and better after each flash.
Majority of my VE logs showed negative fuel trims, so I re-enabled the MAF, LTFT's, and PE, and logged the drive to work this morning.
LTFT's were -5% or less (most -4%)
STFT's were averaging -2% to -3%
WOT AFR was right at commanded of 12.2 according to my wideband (not connected through HPTuners)
I'm guessing the VE numbers want to be where they are?
One log, just for the heck of it, I set the ones that are 120-130 at 90, and the whole log was RED, adding 25 or more % fuel...
attached my VE tuning flash, and my current "finished" tune, with LTFT's, PE, and MAF all back in play.
Any feedback?
#18
Mod with training wheels
iTrader: (16)
Probably a good time to check fuel pressure and spark plugs/gap. And as close as that truck is to stock, I would re-enable LTFT. Because the engine must meet steady state criteria before updating LTFT cells, the upstream O2 sensor relocation will have minimal effect. As far as spark goes, it is possible to add too much without getting knock. Too much ignition timing at 'low' engine load will induce negative torque on the crank before the mixture detonates.
#19
Probably a good time to check fuel pressure and spark plugs/gap. And as close as that truck is to stock, I would re-enable LTFT. Because the engine must meet steady state criteria before updating LTFT cells, the upstream O2 sensor relocation will have minimal effect. As far as spark goes, it is possible to add too much without getting knock. Too much ignition timing at 'low' engine load will induce negative torque on the crank before the mixture detonates.
I attached 2 logs...one from the drive home yesterday, and one from drive into work today...trims look to be pretty good, aren't they? Todays, (2work.2.3.2017) a bit smoother and consistent than even yesterday's.
Last edited by rel3rd; 02-03-2017 at 05:56 AM.
#20
Mod with training wheels
iTrader: (16)
I only have LTFT's disabled in the "VE Tuning" tune above. I have it enabled in the regular, current tune.
I attached 2 logs...one from the drive home yesterday, and one from drive into work today...trims look to be pretty good, aren't they? Todays, (2work.2.3.2017) a bit smoother and consistent than even yesterday's.
I attached 2 logs...one from the drive home yesterday, and one from drive into work today...trims look to be pretty good, aren't they? Todays, (2work.2.3.2017) a bit smoother and consistent than even yesterday's.
The following users liked this post:
rel3rd (02-03-2017)