HappyKasper
Member
- First Name
- Kasper
- Joined
- May 15, 2024
- Threads
- 2
- Messages
- 10
- Reaction score
- 9
- Location
- Durham, NC
- Car(s)
- Integra 2024 Type S
- Thread starter
- #1
I had an AWESOME day today taking my ~3000mi Type S to the track - Jzilla at Barber in Alabama.
Here's my (still embarrassing) best lap:
After a very pleasant 8 hour drive in last night, I spent all day and two full fuel tanks at the track today (measured consumption of the second - 10 gallons burned in the 70 miles I drove in the afternoon).
30 minutes into the 40 minute "happy hour" session at the end of the day (previous sessions had been 20min each), I was cresting the hill at the end of the Carousel and felt the power stutter. My first thought was traction control (which I'd fully disabled), but then the dashboard lit up with failure lights and I nearly forgot to brake into the hairpin as I tried to understand what was going on. I couldn't accelerate out of the hairpin - the car seemed to be limited to 10mph or so (I never looked at the actual speed), and I limped back to the pits.
I was at 5 bars of engine heat, and it was the hottest part of the day, and I'd run longer than in any previous session, so I first suspected limp mode being triggered by excessive temperature (oil or otherwise). Once I drove around the pits a bit and power cycled the car, limp mode went away but the check engine light remained, along with a message about a fuel system issue and a rev match issue. Shortly thereafter, my fuel indicator went from two bars to one bar - I hadn't realized I was at such low fuel until I got into limp mode, because I'd filled up less than 70 miles prior.
I'd stupidly left my OBD scanner at home so I went to an AutoZone to clear the codes and to see this:
I did some hard accelerations after clearing the codes and the light hasn't returned - so I suspect the turbo underboost was secondary to the fuel pressure fault, i.e. I had a brief moment of fuel starvation due to the G-forces of the track and it triggered both of these codes.
Some chance remains that I blew a leak in the turbo/exhaust system but I suspect the G-induced fuel starvation was the real culprit. I'm back at the track tomorrow, and we'll see if the issue recurs!
Here's my (still embarrassing) best lap:
After a very pleasant 8 hour drive in last night, I spent all day and two full fuel tanks at the track today (measured consumption of the second - 10 gallons burned in the 70 miles I drove in the afternoon).
30 minutes into the 40 minute "happy hour" session at the end of the day (previous sessions had been 20min each), I was cresting the hill at the end of the Carousel and felt the power stutter. My first thought was traction control (which I'd fully disabled), but then the dashboard lit up with failure lights and I nearly forgot to brake into the hairpin as I tried to understand what was going on. I couldn't accelerate out of the hairpin - the car seemed to be limited to 10mph or so (I never looked at the actual speed), and I limped back to the pits.
I was at 5 bars of engine heat, and it was the hottest part of the day, and I'd run longer than in any previous session, so I first suspected limp mode being triggered by excessive temperature (oil or otherwise). Once I drove around the pits a bit and power cycled the car, limp mode went away but the check engine light remained, along with a message about a fuel system issue and a rev match issue. Shortly thereafter, my fuel indicator went from two bars to one bar - I hadn't realized I was at such low fuel until I got into limp mode, because I'd filled up less than 70 miles prior.
I'd stupidly left my OBD scanner at home so I went to an AutoZone to clear the codes and to see this:
I did some hard accelerations after clearing the codes and the light hasn't returned - so I suspect the turbo underboost was secondary to the fuel pressure fault, i.e. I had a brief moment of fuel starvation due to the G-forces of the track and it triggered both of these codes.
Some chance remains that I blew a leak in the turbo/exhaust system but I suspect the G-induced fuel starvation was the real culprit. I'm back at the track tomorrow, and we'll see if the issue recurs!
Sponsored