Hondata

- serial number of your FlashPro
- FlashPro Manager version (not 'the latest')
- the calibration (as an attachment)
- a datalog of a problem (as an attachment)
- what sort of vehicle you have
- what sort of ECU you are using
- anything about the car which has been modified from stock which may affect the ECU (don't include what sort of rims you have nor stereo etc).
- a specific description of the problem


FP-S2K-US-30034

Version 1.1.1.0

No calibration – Car is scheduled to tuned Monday next week.

2006 S2000

Honda with Kraftwerks reflash

J’s Racing header, Invidea tp and catback exhaust

Threw a CEL today and looked at it via the Flashpro manager. There was no DTC code or description under the DTC’s Tab but under the Emissions Tab MIL = On as well as Number of DTC’s = 1.

There is no DTC tab or Emissions tab in FlashPro Manager. To see the error codes you must be datalogging and open the Error codes window.

Shouldn't these codes also be retrievable in the Online OBDII Diagnostics under the DTC tab like what is shown in the "help" section on OBDII?

So, if I'm reading this correctly, you can only see the codes in a datalog? Sorry, I'm confused on how to retrieve the codes.

glagola1 wrote:Hello?

The initial explanation seemed to make sense to me. Put the key to 'on', start the dataloging process and open the errors window.

Ohhhhhhh.... I'll try it!

VitViper wrote:

glagola1 wrote:Hello?

The initial explanation seemed to make sense to me. Put the key to 'on', start the dataloging process and open the errors window.

OK, I just did what you suggested. No codes appeared in the error code box. OBDII still shows 1 DTC.

????

Well, I bought a pocket OBDII scanner and I'm getting a P2A00 code.

Fun

Please post a datalog and a the calibration you are using. We have been unable to reproduce what you are describing. It may be that you have an O2 sensor problem and may need to follow the helms Manual for troubleshooting. This is not somethign we have seen before.

Yeah, I'm beginning to think I have a separate 02 sensor problem because I'll throw that code after about 30 miles of driving regardless of what tune I use.

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.

Here's the datalog I took where I caught the CEL in action.

I had a CEL for a couple days, so I hooked up the FlashPro to check the codes. Unfortunately, the CEL must have just turned off.

However, when I went to Online -> OBDII diagnostics, FlashPro Manager showed me that there were 5 DTC's, but would NOT tell me what they were! I clicked Refresh several times, but the list just stays blank. I can see OBDII data on the other tabs, like RPM, temps, etc., but I can't figure out how to get it to tell me what the 5 DTC's are!

I see above that maybe I should try clicking the Datalog button before viewing them, but that just seems kind of weird.

I went back to try it again while datalogging, and it didn't help. I still can't figure out what the DTC's are from.

You have to datalog and click on the error codes window.

Spunkster wrote:You have to datalog and click on the error codes window.

I did do that. In fact, if you look at the image above, you can see part of the Error Codes window right behind the OBDII diagnostics window, and right behind that is the Graphs window, which was capturing a datalog as I clicked Print-Screen.