Having trouble logging fuel trims lately as they are stuck at zero, both in stand-alone logging as well as evoscan. Anyone run into this before?

 

All the trims are 0 or just the idle or cruise?

You need to drive it a while after pulling power.

 

Idle and Cruise is all I watch, I haven't logged STFT's in a while I'll see what's happening there.

I haven't pulled power in about a few months, that one is obvious(but thanks)

 

my evoscan got messed up on me once and stopped logging the baro and my wideband randomly (and just those two). uninstalling / reinstalling fixed it.

 

^Good to know but again, they are zero in both evoscan AND standalone logging.

 

isn't the standalone logging set up through evoscan?

 

No, just a config file on the local SD card.

 

If your rear 02 is disabled, there will be no fuel trims.

If your front O2 is bad or disconnected, there will be no fuel trims.

 

This statement is 100% false. The Front 02 is used for trims. You can remove, disable or run a bad Rear O2 sensor without affecting trims what so ever.

 

^Good to know! I thought that it was odd rear o2 would affect anything...I'm using mine to log my LC-1 if that matters at all.

Does anyone know the RequestID for mode23 to log front o2 sensor voltage? STFT does indeed bounce around just fine but LTFT Idle is stuck at zero and LTFT cruise seems to have found a new home at -0.976563, but that has been stuck there for the last few weeks.

 

I know there is 1 disable for an O2 sensor that kills the trims - maybe it is in the CT9A section though.

 

Your tune is just that good Scheides

 

lol!

 

Yes the rear O2 kills the trims but on the ct9a though. Didn't see what section I was in. Sorry.

 

ever solve this?