View Single Post
Old 12-18-2018, 04:22 PM   #28
Mr_Eyo
Senior Member
 
Join Date: Jul 2018
Drives: 2017 Toyota 86
Location: CA, USA
Posts: 231
Thanks: 21
Thanked 33 Times in 29 Posts
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
Quote:
Originally Posted by steve99 View Post
you commanded AFR is not logging correctly what calid is your tune ? are you using OFT V4 tunes ?

commanded afr may be being offset by the rear 02 sensor readings can you log AF#3 ? or alternative disable rear 02 sensor corre ctions by zeroing the two AF#3 correction tables

the rest looks ok, but i think your problem is just logging is incorrect for your rom/tune

http://www.ft86club.com/forums/showthread.php?p=2909412
Thanks for the comments. I Just checked my defs in RomRaider and found I had the wrong one at the top (ZA1JN10D, my car is ZA1JK00D and it was the next one down). I think these logging quirks started around the same time I downloaded that def. Could writing a tune with the following year's def cause this? AFAIK, the logger would be using the ZA1JK00D defs, right?

I'm not sure I'm understanding your linked forum post, so let me see if I have it right. If the correct cal ID doesn't fix this, you're saying I can set the limits for my AF #3 sensor to 0/0, even if my RomRaider def puts it in a different group ("ALPHA AF 3 (Rear O2 Sensor)", not "Fueling - AF Correction/Learning") from what was shown in your screen cap?
Mr_Eyo is offline   Reply With Quote