What I meant by that is the sensor doesn't care what fuel your using or what % ethanol you have in your fuel, Its always going to read stoich of that particular fuel at 1.0 lambda.
What I meant by that is the sensor doesn't care what fuel your using or what % ethanol you have in your fuel, Its always going to read stoich of that particular fuel at 1.0 lambda.
You could use this (like Mr.Prick suggested): 14.7 / {GM.AFR} * {EXT.WO2LAM1}
Or you could instead log GM.EQIVRATIO and use this: {GM.EQIVRATIO} * {EXT.WO2LAM1}
And I would display WBO2EQ1 = 1 / {EXT.WO2LAM1} on the dash/chart to avoid confusion...
After using EQ units for a while you get used to them, you'll like EQ better than AFR.
Personally I use BEN as a reference,
I don't care what the AFR is at the moment as much as I care if it is what it should be.
I don't worry about this anymore.
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
_________________________________________________
Has anyone ever got a FJO wideband to read serial into the V2? I bought a universal cable from taq and hooked up the wires tonight but I get Controller not found.
I swapped Tx and Rx and still the same Controller not found message.
I thought I read somewhere that FJO's serial would not work, yet I see that its supported in the V2 for serial WB02 and Paul said it is supported as well ?
Last edited by vetteboy2k; August 4th, 2009 at 03:50 AM.
Measuring the analog voltage not connected = 4.41 and connected = 4.11 therefor the offset 4.11/4.41=.931973 How would I enter that into my calc pid. It keeps coming up as an invalid. Below is the error. How should I have this calculated or written in the calc pid to show properly?
FJO Analog AFR {CALC.AFR_FJO}
Expression:
AFR = ({EXT.AD1} / .931973) * 2.5 + 8.75
is NOT valid because:
Syntax error: ".", position 14.
PID value cannot be determined because
the following error would occur:
Expression not valid: Syntax error: ".", position 14.
***Looks like I got it, it needed a 0 in front of the decimal AFR = ({EXT.AD1} / 0.931973) * 2.5 + 8.75
Last edited by vetteboy2k; August 9th, 2009 at 10:13 AM.
You may want to calibrate your AD's or at least check them,
you shouldn't need to add an offset for the V2.
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
_________________________________________________
can somebody make a sticky about how to edit the Calcuated.Pids the right way and how to write formulas.
thanks
01 GMC Sierra 1500 SLE 5.3 cam swap
Tuned by ME (COS 5 - running strong and smooth)
Calculated PIDs:
showthread.php?t=132
showthread.php?t=130
showthread.php?t=10
Based on the formula för a liear equation (y = kx + n), in this case, I would use "n" to adjust for any offset.
So the equation in your case would translate into:
y = lambda
k = line slope
x = voltage
n = vertical offset = the point at the y-axis where the line crosses it
So by adjusting the n-number, you could offset the whole line up or down.
If you have an analog voltage number from the manufacturer for e.g. not connected/connected, I would just compare it with your current reading and insert that offset on to the n-value that was current for you base line lambda calibration.
Is that making any sense?