Have you done this method with success? Seems like everyone is dead set on AutoVE, but this method seems to be the way to go when you are commanding 14.7:1.
Do you also want to disable closed loop mode?
Have you done this method with success? Seems like everyone is dead set on AutoVE, but this method seems to be the way to go when you are commanding 14.7:1.
Do you also want to disable closed loop mode?
Enable {B4206} and disable LTFT's.
IMO use LTFT's instead.
It will take longer but it's what you want anyways
and you can leave PE on.
This method is for RTCS and IIRC was not intended for WOT/PE mode.
When PE comes on STFT's go to 1.00,
no adjustment will be made by multiplying by 1.
CLSD tuning with LTFTs
This method should not be use with RTACS.
512k RoadRunner Firmware 12.14R
FlashScan V2 Bootblock V2.07.04 Firmware V2.07.22 EFILive V7.5.7 (Build 191) V8.2.1 (Build 181)
LC-1 WBO2
_________________________________________________
I take it as he used strim feedback from the o2 sensors. It seems as though enabling B4206 would give me a watered down version of how much the VE table is actually off..?
If I am understanding correctly, this will put me back in open loop right?
Why do you prefer using LTFTs instead of this method if it takes longer?
He did post whether or not to enable {B4206}
I just assumed you would need to other wise you will be
in OL and the whole point of using "strim feedback from the o2 sensors"
would be mute.
I could be wrong though.
Why do you prefer using LTFTs instead of this method if it takes longer?It will give you a smoother VE table than OLSD on the street.It will take longer but it's what you want anyways and you can leave PE on.
LTFT or OLSD in steady state are the preferred method for VE tuning.
Personally I have found OLSD to be inconsistent because of IAT, altitude, load% ect.
Last edited by mr.prick; June 13th, 2009 at 05:35 AM.
512k RoadRunner Firmware 12.14R
FlashScan V2 Bootblock V2.07.04 Firmware V2.07.22 EFILive V7.5.7 (Build 191) V8.2.1 (Build 181)
LC-1 WBO2
_________________________________________________
Ok,
I went in and followed the instructions for the STFT fixer and went out and made a few logs. What I am trying to figure out is if
A. Am I logging this correctly to get good data?
B. Am I applying this correctly to the VE?
C. Are my STFT supposed to be that far different between bank 1 and 2 or is one of my sensors bad?
03 z06 auto
ver7.5.5 custom OS5
415 ci
239/255 .624 lift LSr grind
16psi
Meth injection
PLX WB02
I would like to add a calc_pid to this:
This multiplier is based on STFTs when they are active,PHP Code:
#Units Low High Fmt Expression
#------------ ------ ------ ------ -----------------------------------------
*CLC-00-044
factor 0.0 2.0 .2 "iff({CALC.STRIM}*{CALC.BEN1}={CALC.BEN1},{CALC.BEN1}*1,{CALC.STRIM}*1)"
# ===============================================================================================
CALC.RTACS_STFT F044 CLC-00-044 factor Fuel "RTACS BEN w/STFT"
when PE mode becomes active the multiplier is based on BEN.
The original PID works only when STFTs are active,
once PE mode becomes active the multiplier is 1.00
This prevents any fuel from being added/subtracted in PE mode.
This will allow you to shape the VE table with STFTs and BEN at the
same time but only when each is active. (STFT or BEN)
Last edited by mr.prick; October 13th, 2009 at 04:58 PM.
512k RoadRunner Firmware 12.14R
FlashScan V2 Bootblock V2.07.04 Firmware V2.07.22 EFILive V7.5.7 (Build 191) V8.2.1 (Build 181)
LC-1 WBO2
_________________________________________________
I know this thread is dead but maybe somebody will help. I'm trying to use this method and I can't get past the first step. I opened the sae_generic.txt file and I can't find the section to modify. I have looked through the whole file several times. Also, since I'm using an LS1B instead of an E38 I would imagine I should be looking for a similar line using LS1B instead. Is this method still viable in 2015? Did the sae_generic.txt file change in the current version? Lost and confused like always...
E38/E67 and later do not have VE...
Also, should really create your pids in calc_pids.txt to avoid losing them when sae_generic.txt gets overwritten on each V7 software update.
Thanks for the help once again joecar. I guess I wasn't very clear. I'm not sure what text to put where in the file. I'll take your word on using calc_pids.txt instead of sae_generic.txt. I know E38s don't have a VE table but the first post in this thread talks about finding "# E38 VE..." in sae_generic.txt. It's not in the file and I don't think that's what I would be looking for any way since I'm using an LS1B. I'm really trying to understand this but it's a bit over my head at this point still.