FlashPro O2 cat delete
Does anyone know if this was addressed in the new version of FlashProManager (1.1.2.6)? The help file mentioned something about it correcting something related to a couple diagnostic codes, but I don't remember what the diagnostic codes were.
We put 250 miles on the car and about 10 cold/hot driving cycles without reproducing the DTC. Since this was a code relating to the primary o2 sensor, not the secondary, I don't want to disable the code until we understand what the exact cause it. The next step would be to try a known good primary o2 sensor.
Originally Posted by 05S2k02Si,Dec 2 2009, 05:23 PM
Just a thought...assuming that the Hondata test car is a Cali car, is there any difference in the ECU's? California vs the rest of the US.?
Brian
Brian
So this is a primamary O2 issue?
If I revert back to the stock map then this should theoretically go away since this was the only change I've made.
I thought this was a secondary O2 issue because of my test pipe.
I'll see if I get the code I use to get or if it's still this new one.
If I revert back to the stock map then this should theoretically go away since this was the only change I've made.
I thought this was a secondary O2 issue because of my test pipe.
I'll see if I get the code I use to get or if it's still this new one.
What version of FlashPro Manager are you guys using? Were you using one of the Beta versions? I found a problem with 1.1.2.6 yesterday that Hondata said has been in the Beta versions for a while. I wonder if you guys might have been leaning out your fuel tables too much because of the bug.
Note that I went from 1.1.1 to 1.1.2.6, and skipped the many beta versions.
http://www.hondata.com/forum/viewtopic.php?t=10463
Note that I went from 1.1.1 to 1.1.2.6, and skipped the many beta versions.
http://www.hondata.com/forum/viewtopic.php?t=10463
I'm using 1.1.2.6 and was using .5 before that but I've been using the stock hondata tuned map. I did play with the tune a bit yesterday but reverted back. My AF was staying around 13-14 but noticed it was going all the way down to 8 at wot so that's when I went back to the Hondata stock tuned map.
btw is the problem fixed in .7?
btw is the problem fixed in .7?
The problem does seem to be fixed in .7, but as a professional software developer for a large company, I can't stress how important it is to stay away from beta versions. For something like this to go unnoticed, it seems that Hondata doesn't have much of a testing budget.







