FlashPro O2 cat delete
01-22-2010, 03:48 PM
#51
Originally Posted by crazysupratt,Jan 22 2010, 05:41 PM
can you guys post up your a/f logs...i'm wondering if you guys are running too rich?
01-22-2010, 08:58 PM
#52
Community Organizer
Originally Posted by gernby,Jan 22 2010, 04:46 PM
Did he disable the secondary O2, or just load the Hondata calibration as it was?
02-01-2010, 05:31 AM
#53
Well, here's an update:
My check engine light would go off after a few drive cycles and then it would pop back on shortly. So while it was in one of those off cycles I started datalogging every drive to see if I could catch the precise moment the CEL occurred. Sure enough. I had a hunch that it would happen when I was driving around the VTEC engagement point but with light throttle.
So I look at the AF maps and on the low cam it got a bit rich but not super rich. So I leaned that out and while creating that map the firmware updated it self. I also noticed that the parameters for the VTEC pressure were now editable where before they were not. So I was able to adjust the range for VTEC based on RPM and MAP. (why the heck is the MAP in Bar but it's in PSI in the rest of the software?)
Anyway, with these 3 changes, I have not been able to get the CEL to come back on. I'm pretty sure it's fixed.
Yay. No more worries about legality for STR (auto-x) and having a CEL on the dash.
My check engine light would go off after a few drive cycles and then it would pop back on shortly. So while it was in one of those off cycles I started datalogging every drive to see if I could catch the precise moment the CEL occurred. Sure enough. I had a hunch that it would happen when I was driving around the VTEC engagement point but with light throttle.
So I look at the AF maps and on the low cam it got a bit rich but not super rich. So I leaned that out and while creating that map the firmware updated it self. I also noticed that the parameters for the VTEC pressure were now editable where before they were not. So I was able to adjust the range for VTEC based on RPM and MAP. (why the heck is the MAP in Bar but it's in PSI in the rest of the software?)
Anyway, with these 3 changes, I have not been able to get the CEL to come back on. I'm pretty sure it's fixed.
Yay. No more worries about legality for STR (auto-x) and having a CEL on the dash.
02-01-2010, 06:22 AM
#54
Originally Posted by glagola1,Feb 1 2010, 08:31 AM
Yay. No more worries about legality for STR (auto-x) and having a CEL on the dash.
02-01-2010, 06:29 AM
#55
Nope, the reflash is a legal mod... and a damn good one for us.
Also, the Stock Equivalent threw the code. I really don't know what fixed the code. I doubt it was the fuel table tuning. I think it may have something to do with the firmware update or the vtec pressure editing... I just don't know.
Also, the Stock Equivalent threw the code. I really don't know what fixed the code. I doubt it was the fuel table tuning. I think it may have something to do with the firmware update or the vtec pressure editing... I just don't know.
02-01-2010, 09:34 AM
#56
Former Sponsor
Join Date: Jul 2001
Location: Torrance
Posts: 164
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by glagola1,Feb 1 2010, 06:31 AM
Why the heck is the MAP in Bar but it's in PSI in the rest of the software?
02-01-2010, 11:43 AM
#59
Community Organizer
Originally Posted by glagola1,Feb 1 2010, 06:31 AM
Well, here's an update:
My check engine light would go off after a few drive cycles and then it would pop back on shortly. So while it was in one of those off cycles I started datalogging every drive to see if I could catch the precise moment the CEL occurred. Sure enough. I had a hunch that it would happen when I was driving around the VTEC engagement point but with light throttle.
So I look at the AF maps and on the low cam it got a bit rich but not super rich. So I leaned that out and while creating that map the firmware updated it self. I also noticed that the parameters for the VTEC pressure were now editable where before they were not. So I was able to adjust the range for VTEC based on RPM and MAP. (why the heck is the MAP in Bar but it's in PSI in the rest of the software?)
Anyway, with these 3 changes, I have not been able to get the CEL to come back on. I'm pretty sure it's fixed.
Yay. No more worries about legality for STR (auto-x) and having a CEL on the dash.
My check engine light would go off after a few drive cycles and then it would pop back on shortly. So while it was in one of those off cycles I started datalogging every drive to see if I could catch the precise moment the CEL occurred. Sure enough. I had a hunch that it would happen when I was driving around the VTEC engagement point but with light throttle.
So I look at the AF maps and on the low cam it got a bit rich but not super rich. So I leaned that out and while creating that map the firmware updated it self. I also noticed that the parameters for the VTEC pressure were now editable where before they were not. So I was able to adjust the range for VTEC based on RPM and MAP. (why the heck is the MAP in Bar but it's in PSI in the rest of the software?)
Anyway, with these 3 changes, I have not been able to get the CEL to come back on. I'm pretty sure it's fixed.
Yay. No more worries about legality for STR (auto-x) and having a CEL on the dash.
With my friend's CR, he took it to Honda and they said they would change his O2 sensor.
02-01-2010, 03:25 PM
#60
Here's a link to the Hondata forum where I've posted my datalog. It's the one that I caught the CEL at the end.
Maybe Gernby can take a look.
http://www.hondata.com/forum/viewtop...?p=45182#45182
Maybe Gernby can take a look.
http://www.hondata.com/forum/viewtop...?p=45182#45182