Quote:
Originally Posted by 73TORANA!
Thanks Steve,
I set the #AF3 tables in rom raider to "0" and went for a drive. It made a big difference. The Command AFR in C/L cruise is 14.89 - .2 logging error is 14.69 and the actual AFR is 14.58 with minor fluctuations as it was with the factory headers. The actual AFR reading is a lot more stable as well. Thanks for your help in clearing this up for me. I did feel the second O2 was for catt efficiency, its makes sense. I recon setting #AF3 to zero will most probably also help with LTFT learning. Cheers
|
This is interesting. But does it actually affect commanded AFR though, as @
steve99 mentioned that it shouldn't.
Quote:
Originally Posted by steve99
Also in cruise mode the ecu also looks at the rear 02 senspr and apples a coreection to afr known as #AF3 correction, this is not reflected in commaned afr logged parameter.
|