Wideband and Evoscan Don't Match
#1
Wideband and Evoscan Don't Match
Hope someone can help me out. The wideband is an Autometer that was recently installed (but I've had on my old Evo for 4-5+ years) - installed from one car to another, and working perfectly before that. The o2 sensor itself is less than a year old. It seems to be reading right at the gauge, though I am running lean during cruise (15.4+).
While taking logs to tune the car, the wideband reading you get from Evoscan seems to be incorrect. I've tuned through this method for about 6 years now, and this has never happened before. So while the wideband reading at the gauge will bounce all around as usual, the wideband reading in evoscan sits at 10.0588235294118, 10.0294117647059, etc., or 10 flat and just sits there for extended periods of time.
FYI, the formula I have in Evoscan reads 10.00+(16.00-10.00)*x/204 , which is what I've had my wideband formula at for at least 4 years. Even if the formula were wrong, the evoscan read of the wideband shouldn't just sit at solid values for extended periods of time. Thoughts?
While taking logs to tune the car, the wideband reading you get from Evoscan seems to be incorrect. I've tuned through this method for about 6 years now, and this has never happened before. So while the wideband reading at the gauge will bounce all around as usual, the wideband reading in evoscan sits at 10.0588235294118, 10.0294117647059, etc., or 10 flat and just sits there for extended periods of time.
FYI, the formula I have in Evoscan reads 10.00+(16.00-10.00)*x/204 , which is what I've had my wideband formula at for at least 4 years. Even if the formula were wrong, the evoscan read of the wideband shouldn't just sit at solid values for extended periods of time. Thoughts?
Trending Topics
#9
Evolving Member
Did you find a solution kyoo? I'm having same issue with my AEM UEGO. Reads from 9.5, to like 10.9. Used to work fine, but I dont have the exact formula I used before. Right now its 0.03913*x+9.5
#10
Evolving Member
I often run into this issue when the ground(s) for the wideband are separate from the ECU grounds. You get a voltage offset between the wideband and ECU. If possible, wire wideband ground to a sensor ground or if not possible, to another ECU ground wire. Most of the time I've had the wideband read different than what the ECU was displaying, this was the case.
#11
Evolving Member
I often run into this issue when the ground(s) for the wideband are separate from the ECU grounds. You get a voltage offset between the wideband and ECU. If possible, wire wideband ground to a sensor ground or if not possible, to another ECU ground wire. Most of the time I've had the wideband read different than what the ECU was displaying, this was the case.
#12
Evolving Member
#14
I check the "External Wideband A/F Ratio" display item in evoscan to show AFR for the AEM, which works for me, maybe try that.
#15
Evolving Member
Doesn't the AEM use a serial output to report AFR to evoscan? That means there should be no formula for an AEM, since evoscan should just use the value its getting from the serial connection directly.
I check the "External Wideband A/F Ratio" display item in evoscan to show AFR for the AEM, which works for me, maybe try that.
I check the "External Wideband A/F Ratio" display item in evoscan to show AFR for the AEM, which works for me, maybe try that.