jmheath357
Senior Member
- Joined
- Feb 13, 2026
- Threads
- 3
- Messages
- 58
- Reaction score
- 44
- Location
- Phoenix, AZ
- Vehicle(s)
- 2025 Honda Civic Type R
Hey, just as a heads up. You may or may not know or maybe cleared this with Derek first, but typically you have to record all 4 of those logs back-to-back directly after uploading the tune on the same drive cycle. They are not supposed to be done separately on different days as the ECU will have already gone through it's learning process and it won't be accurate data being sent back to Derek. I know the ECU's are different between the Accord and the R, but his instructions are the same for both so I'm sure the same principles apply. When having my Accord tuned by him I had asked this exact question and this was his response:Update on my fuel system install, pasted from another thread. This is the summarized version:
We had a few questions on the XDI HPFP flex line that got answered along the way. Both ends of the line are identical, it's rated across all fuel types (including ethanol, race gas, methanol, even hydrogen in motorsport use, though XDI doesn't publicly advertise fuel compatibility to protect their manufacturer’s IP), and 3 1/2 threads engagement into the fuel rail is normal, hand-snug is really all these need before a final wrench pass.
Install came back together clean, checked every fitting before first start, no leaks at the HPFP, and it settled into a smooth idle after the initial crank cycles as expected. Idled 15 minutes with no codes, then took it for a shakedown drive on the basemap with no inconsistencies.
Logging is now underway for DRob ahead of the dyno. Got a 60-mile drive in with the 15-minute steady cruise and WOT 3rd-gear pull from 2000rpm both logged, still need to recapture the 15-minute stop-and-go (FlashPro missed it twice) and the cold start/idle log (FlashPro missed this as well), planning to grab both tomorrow. Full tune on Shell 93 and Ethanol is expected in the next 1-3 weeks.
![]()
![]()
![]()
![]()
![]()
![]()
Me: "Why is it that you ask to drive the car/perform the datalogs immediately after flashing it with a new tune and not drive it around any first? Just curious."
Him: "I need to see the ECU learn fuel trims and monitor the behavior of knock control movement. If I don't see it happen, I can't make changes that affect them accurately."
So you would likely need to reflash the ECU again and do all the logs in the same drive cycle as he asks for, unless he told you otherwise of course.
And those missed logs are exactly why I would also recommend doing the logs with your laptop connected to the Flashpro and record from there. That way you can see for absolute certain you are actually recording and there won't be any issues there. I was worried about missing logs too so that's what I decided on doing so that can't happen. Plus, you won't have to download them from the Flashpro since they will already be on your computer so it's one less step too. But if you really just don't want to carry your computer around when recording, hold you hand under the Flashpro and you will see when it's not recording the blue light will have a short fast blink and when you are recording it will be a slow longer blink. Just some tips if you weren't already aware. Ignore me if you were aware. lol
Looking forward to seeing how everything goes on the dyno!