O2B Voltage / O2Bv Behaviour

[berk]

Hi,

Just wondering what a "normal" readout looks like for the O2B voltage, in this case the 2016+ turbo civic.

Quick background; I've had a custom tune for years with zero issues, Ltrim never strays a couple percent from zero. Just recently, I pulled up the app to see it at -3%. Over a couple days this eventually became -12%. The engine "feels and sounds healthy", I can't imagine any mechanical reason it would need to pull so much fuel (but I am welcome to ideas!). Brand-new O2 sensor yields no different. Pressurized everything from the inlet pipe, nothing leaking on the outside.

However, I noticed one sensor that appears on the app, but not in datalogs: "O2Bv". The only mention of this in the documentation is on a table of supported sensors but that "not all sensors can be datalogged from every ECU". When viewing this sensor live, the value jumps back and forth from 0.0v to 5.0v, and sometimes settles around 4.7v around idle and 3.0v under throttle. On a cold start, this value is pretty stable, but after a few minutes it becomes sporadic again. If I were to take an educated guess, something is warming up, faulting out, and the ECU might be averaging this as a lower voltage than normal, and pulling fuel in response.

So, my question here is; is it normal for the O2B voltage to jump all over the place rather than be a relatively consistent reading?

The only other mention of this sensor online is here where someone is experiencing the same symptom with no answer. I also can't refer to previous datalogs because the sensor isn't recorded... I've attached two new ones anyways in case it helps, and a video of the sensor value jumping all over the place is here. Any information about this would greatly help in knowing if air is somehow escaping or if I have an electrical issue!

[Spunkster]

Where are you seeing ODBv?

[berk]

O2Bv is visible as a live value in the head unit app and the mobile app, but not recorded in data logs for some reason. I'll more clearly link the video showing O2Bv fluctuating again. My Flash Pro is also on the latest firmware version.

[Spunkster]

That is not a valid channel to datalog. When you open FlashPro manager and have a calibration open and datalog, only the sensor listed in the sensor window can be viewed.

[berk]

Not a valid channel to data log in just the programming of the Flash Pro or not a valid channel to retrieve from the ECU (but still OK to view live)?

With the convenience of logging or not, I'm just curious to know if the values I'm seeing are common behavior on these vehicles or indicative of a specific problem.

[Spunkster]

its not a valid value to datalog.