RomRaider

the front o2 consistently reads .1-.5 rich compared to my wideband and I'm not sure how to proceed. The wideband is accurate, or at least it should be since I air calibrated it today. I figure I might be able to just rescale the factory o2 based off the wideband, but that doesn't seem to be a thing in practice and feels more shade tree than I'd like so I'm open to suggestions.

Probably coincidental, but the factory map also reads 14.3-14.5 engine off and I am at sea level. May be a nitpick but wow does it drive me up the wall.

04 wrx
carberry, maf
hybrid engine, no cc match
oem o2 sensor
aem uego wideband

Fine Learning Knock Correction = - 6,33?

is your front o2 still in the header or in the downpipe? from what I remember you have to move it to the downpipe when running carberry because the rom uses jdm/group n latencies and is more accurate

Front o2 is still in the headers, the wideband is in the downpipe. Do you mean the injector latencies?

Good ole phantom knock, at least it was the last time I listened with the det cans.

no, jdm cars which is what the rom is based on have the front o2 in the downpipe from the factory. udsm and jdm roms scale the front o2 differently

if you still have a catted uppipe you need to get rid of that because it will throw off afr's when you move the sensor

I did see that the front o2s are scaled differently, so I've been using the o2 scaling from jon7009's basemap https://www.romraider.com/forum/viewtopic.php?f=28&t=20304. If it is just a matter of different scaling, would rescaling it off the wideband be a sensible thing to do?

Otherwise, is the standard solution to this to just relocate the front o2? If so, I would assume that the wideband stays were it is in the downpipe and I add a second bung to it for the front o2.

personally I really like having the o2 in the downpipe, I found not only the carberry scaling to be very accurate (down to 11.1) in all of my cars, it will also last longer not being torched in the header. 2 bungs in the downpipe would be the best however it's up to you, you can change the scaling and it'll probably work ok

Good to know about the carberry scalings being reliable, though it makes me curious why jon7009 would change them. I'm going to update the scaling and report back, but I think I'm going to swap the o2 sensor locations with and get some data with both scalings. Don't really know what I'd be looking for but my curiosity is piqued.

Just an update - I used the carberry o2 scalar with +.1 and that appears to have the o2 sensors in lockstep. I haven't tried switching the o2s, which I still might do when I have a bit more time.

I also don't have datalogs because in my infinite wisdom, at the same time as fixing the scalar I reverted my injector latencies and was chasing my tail on my suddenly good sensors but wacked fueling.

Kinda curious, what could cause an o2 sensor to have this kind of error? Even if it is just a case of a failing sensor, I would've expected errors or inaccuracies beyond just a static offset, and a relatively small one at that.