News:

When asking for technical help at the very least let us know the version of firmware you are running.
Cliff's Calibration (Mapping) Guide is a MUST READ: http://www.vemssupport.com/forum/index.php/topic,97.0.html

Main Menu

WBO2 - lost reading under boost.....

Started by Pet, April 21, 2009, 05:08:03 PM

Previous topic - Next topic

Pet

Hi, I have a problem when I am under boost, I lost reading from WBO2 as you can see from picture. Do you know, where should be a problem ? The sensor is about 2years old and was running with LC1 kit. Also sensor is about 50-60cm far from turbo, so imho there is no problem with overheating. Maybe I registred, when Lambda was too low, about 0.75 (I am tuning VE maps now), then the reading was canceled for some time, then was recovered again.
Thx for the reply.


GintsK

LC1 ?! On VEMS? Why?

For LC-1 it is normal to loose signal when it needed under load. Not good product.

Pet

#2
No no, I am not using LC1 with VEMS, but only sensor, which was working with LC1 (on Megasquirt) before. Now is connected directly to the VEMS.. In normal (small boosts and <100kPa area) conditions is reading ok.

[email protected]

Do you know anyone with a sensor you could try a test on?

GintsK

#4
Hm. You use AFR(WBO2) channel. It is calculated (is it cofigurated? How?). What shows Lambda channel, which is taken directly from ECU?

Pet

Lambda channel goes directly from VEMS, AFR channel is calculated by Megaloviewer...
So here is my WBO setting, should be here something wrong ?



or I tried yesterday this setting (default WBO setting from 1.073 full package), maybe it was better, but my ntb battery was low, so I'll log more data today.



Pet

So maybe it's a litlle bit better with WBO settings nr. 2, but still after some time in boost goes Lambda reading to the hell. Next week I'll try another sensor....


[email protected]

Hang on, you're using an old wideband on a VEMS ECU?  (This is the forum for the gauge).
Well first off if you didnt use the setting defined here: http://195.159.109.134/vemsuk/forum/index.php/topic,55.0.html
You won't be getting correct readings - and may have damaged the sensor's heater.
Plus the calibration will be way off.
And you cannot calibrate a dirty sensor.
The calibration value defines the level of accuracy away from 1.0lambda so with the correct settings and a good sensor, that figure should be correct.  The rest should just be considered noise.