Help! Car went into limb mode after basemap upload

[k20z_vtech_8k]

Hi,

Requesting for help, please.

Very new to Hondata. Literally got the Flashpro the this week. Flashed a basemap with some minor edit today. The car was fine and able to rev >3k for the first 15 min of driving. No issue at all for that trip. The car cooled down for 4 hours ish. Trying to drive home (2nd trip) and the car went into limp mode in the first 5 mins of driving.

The car went into limp mode once the car revs above 3K. It cuts fuel and no power. Check engine light went on. I'm able to drive home with the rev under 3k rpm. First thing I did is read the diagnostic code using Hondata flashpro, and surprisingly no error code. It just gave me the ECU part number pretty much in Flashpro Diagnostic. Error code window is empty.

Then, I did "return ECU to stock" with hondata flashpro manager. The check engine light disappeared. Right now, I just parked the car. Didn't drive it. Honestly nervous at this point. But able to rev to more 4k without fuel cut in neutral.

Any help or suggestions would be appreciated. Had no clue why the heck the car would go to limp mode with just a Hondata provided K&N vs SRI basemap...

Situation and conditions:
- Hondata flashpro mini bluetooth version. Got it brand new from Hybrid Racing
- Car is 2006 8th Gen Civic Si, with the K&N v2 SRI. No other power mod. Stock header, throttle body, intake manifold, exhaust. Only changed the K&N exhaust
- The car runs fine with the K&N v2 SRI for a decade before flashing. Had the car for almost 2 decades, no check engine light issue. Very certain it's related to the engine tune just uploaded today. Nothing wrong with the car before uploading the tune.
- I used the K&N v2 SRI basemap calibration, and modified the following in flashpro:
- Reduced rev limit from 8600 rpm to 8400rpm in Rev Limits (just to be safe)
- Selected MAP and uncheck MAF in Fuel under Calibration window (Google search suggested to use MAP)
- Disabled Rev Hang by unchecking "Overrun throttle opening (rev hang) enabled" in Throttle under Calibration window
- Checked the battery voltage when the car is off. It's 12.47V. Google search says 75% battery state of charge. Doesn't look bad.
- Did a battery voltage droop test a few days ago. The transient droop goes down to 10.47V when starting the engine. The battery seems ok to me.

I did notice when using the long USB cable that come with the Hondata flashpro, it sometimes has trouble powering on the device where Windows and Flashpro Manager doesn't detect flashpro (with the X mark next to to flashpro). If I use a very short USB C to USB C cable, it consistently powers on the Flashpro. I'm not sure if the Flashpro voltage drop was too high with the long USB C cable, but I thought Flashpro is powered by the OBDII plug...

Thoughts?

[k20z_vtech_8k]

I google searched a bit and Gemini suggested that the battery voltage could be low and potentially corrupting some bits during data transfer? That said, the flashpro ECU tune size is only 22KB. How can 22KB consumes that much power? At most mA I would think.

Also, why is the 1st 15 mins of the trip ok, but after shutting off the engine for a few hours, the following trip starts to go into limp mode? If the data transfer is corrupted that bad, wouldn't my first trip throws out error code already?

I'm very perplexed, but I'm new to Hondata, so I could be something wrong here. Any help would be much appreciated.

[k20z_vtech_8k]

Also, after "return ECU to stock" I used another ODBII tool to read the engine error code and there's none...

[Spunkster]

If the check engine light is on you need to datalog and look at the error codes window. This needs to be done while the check engine light is still on and before shutting the engine off.

[k20z_vtech_8k]

No idea how to do datalogging yet, but will try to get the error code when the check engine light turns on.

[k20z_vtech_8k]

Today, I uploaded the K&N v2 SRI basemap (AFM unchecked and MAP checked) again after I returned ECU to stock yesterday.

Attached are the two datalogging.

One my first trip, just last like time, there was no check engine light, but the Error Code "P0101 Mass or Volume Circuit Range Performance Problem" did pop up in Flashpro manager during datalogging.

On my second trip, roughly 5 mins in, the engine cut fuel at 3k rpm and went into limp mode and the check engine light stayed on. There's no additional error code and I still see the P0101 Error Code.

Any help would be much appreciated.

[Spunkster]

It sounds like this calibration needs additional tuning if it is throwing this error.

[k20z_vtech_8k]

But why though? Isn't the hondata K&N v2 SRI basemap supposed to be very mild and work for all 8th civic Si? Hm...

Any idea what the issue is and what needs to be tuned?

Would there be any concerns to use the MAF fuel option with the Hondata K&N v2 SRI basemap?

[k20z_vtech_8k]

I read many pages of 8th Gen Si section on this forum last night. Sounds like some say to use MAP, we need to disable "P0101" in ODBII tests in Misc under Calibration? Is that correct?

[k20z_vtech_8k]

My limp mode is now gone!

I've gone to the MISC tab and disabled P0101. Drove multiple 15 mins trip or so, and so far no check engine light nor P0101 code popping up in datalogging.

Are we supposed to disable P0101 is MISC with K&N v2 SRI basemap with MAP for 8th Gen Civic Si?

[Spunkster]

It shouldn't if it is tuned correctly to my knowledge.

[k20z_vtech_8k]

Ah ok. Maybe disabling P0101 is just to get error code gone to look into the issue above 3k rpm and get it fixed.

Attached are my datalogs. 2 with K&N SRI basemap exhibiting knock count.

Had 2 trips with K&N v2 SRI basemap, 30 mins drive ish. One time (Trip 5) shows 3 knock count on cylinder 2. The other one (Trip 6) shows knock count of 3 at cylinder 2 and 28 at cylinder 4. When the knock count jumps, it happens at around 3.2k rpm. No knock outside of 3.2k to 3.3k rpm at all.

Just to check if it's my fuel injector, spark plugs etc, or the tune, I returned ECU to stock, and had 2x 50 mins drive, and in both cases the knock count are all 0 for all cylinders, which means the knock is definitely attributed to the K&N v2 SRI basemap. I have the datalogs if uploaded is needed.

Any idea what I should tune, e.g. part throttle tuning (MAP), to reduce the knock count, with the K&N vs basemap?

Any idea why there are so many knock count just with K&N SRI basemap?

[Spunkster]

You should try reducing the timing in the areas you are getting knock.