What's the deal with these Fuel Trim values?....VAG-COM block 032

[hernandez3011]

I've been having a misfire issue lately. I did a LONG data log today after getting out of work. I drove for about 45 minutes while logging blocks 003, 031, and 032. I never cleared any codes but for some reason my fuel trim values remained at 0 all across the board for the entire ride home. I didn't see one flunctuation on my data sheet.

I did pulls up to 6k RPM and experienced these misfire.....there's no way the trim values would remain at zero the entire time.

I've known that this is not normal at all. Is my primary 02 sensor bad?

Anyone with more knowledge can you give me a hand? Thanks in advance fellas

[LEGO]

Mine were all 0s once. Ended up being a bad primary o2 sensor. Changed that out and it fixed the problem. Ended up being like -1.6 and -2 or something like that. Don't know if that's your problem though.

[walky_talky20]

What were the values in block 031?

One should be Lambda actual and the other should be lambda spec (target AFR). The target should change quite a bit when going into boost. If the target doesn't change, something is up with the log or the software or something.

[hernandez3011]

My personal laptop is at my house and I'm at home right now. Block 31 looked good, it would increase with boost as it should. I'm going to lean toward bad primary 02 sensor because i've noticed a code for that sensor stating "response too slow" b1 s1
The only thing that kept me from getting a new o2 sensor was that when I cleared the code it would take days for it to return.

I'll post logs later today