12-18-2018, 08:11 PM
|
#29
|
|
Senior Member
Join Date: Jul 2018
Drives: 2017 Toyota 86
Location: CA, USA
Posts: 235
Thanks: 21
Thanked 33 Times in 29 Posts
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
|
Quote:
Originally Posted by Mr_Eyo
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?

|
Correcting the Cal ID def didn't fix it. Now flashing a tune with the rear O2 corrections disabled.
|
|
|