FlashPro for CTR tuning results

8yourv8 said:

Is there a upgraded fuel pump for our cars yet because im dataloging 92 percent on the dyno during pulls.

Click to expand...

not that we're aware of at this time.

Just installed the RV6 catless DP, currently running the 93 IC/DP improved throttle tune. Going to run 100 octane tune soon and since i like the improved throttle response i wanted to run the 100 octane tune and select this mod when i upload, has anybody ran this combo with that mod turned on? Or know if it would cause any CEL’s or anything

PhAzE7 said:

Just installed the RV6 catless DP, currently running the 93 IC/DP improved throttle tune. Going to run 100 octane tune soon and since i like the improved throttle response i wanted to run the 100 octane tune and select this mod when i upload, has anybody ran this combo with that mod turned on? Or know if it would cause any CEL’s or anything

Click to expand...

I don't see why the improved throttle response would cause a CEL. all this "improved throttle response" does is target higher torque values at lower throttle input than the standard throttle response.

Example, targeting 250ft lb at 3000 rpm on 30% throttle input on standard response while you'd target the same torque figure at the same rpm but at a 15% throttle input. Giving the same torque amount at a higher throttle input gives the feeling of a delayed response compared to having it on a lower input.

Does anyone know how turn the boost down on a tuned map?

8yourv8 said:

Does anyone know how turn the boost down on a tuned map?

Click to expand...

The bosch ecu is based off of torque target so boost isn't really at a set amount. It will use a combination of parameters such as boost, ignition timing, etc in order to obtain the torque target you set.
The only way for you to "lower" the boost would be to lower your torque target on the torque tables so the ecu doesn't require as much boost in order to hit the torque you are trying to target.

boosted180sx said:

The bosch ecu is based off of torque target so boost isn't really at a set amount. It will use a combination of parameters such as boost, ignition timing, etc in order to obtain the torque target you set.
The only way for you to "lower" the boost would be to lower your torque target on the torque tables so the ecu doesn't require as much boost in order to hit the torque you are trying to target.

Click to expand...

That explains alot because i went to the dyno last week and the car made crazy power on just a flash and filter upgrade. But the torque was really high and the boist hit 26.5 on my data log.

Any updates coming soon?

PhAzE7 said:

Just installed the RV6 catless DP, currently running the 93 IC/DP improved throttle tune. Going to run 100 octane tune soon and since i like the improved throttle response i wanted to run the 100 octane tune and select this mod when i upload, has anybody ran this combo with that mod turned on? Or know if it would cause any CEL’s or anything

Click to expand...

I've got a similar set up and ran the 100 octane. At that time I was getting CEL and limp mode, but Hondata has since then released an update to prevent CEL. Forget the code.

PhAzE7 said:

Just installed the RV6 catless DP, currently running the 93 IC/DP improved throttle tune. Going to run 100 octane tune soon and since i like the improved throttle response i wanted to run the 100 octane tune and select this mod when i upload, has anybody ran this combo with that mod turned on? Or know if it would cause any CEL’s or anything

Click to expand...

Oh yeah go back to page 22 and 23 where I posted about the CEL

CTR941 said:

Oh yeah go back to page 22 and 23 where I posted about the CEL

Click to expand...

Yeah All good i have been running this setup and haven’t had any CELs since,

@Hondata I live in colorado springs, is there any tunner that you would recommend around here? or I should drive to Cali? rather not

theangelofspace15 said:

@Hondata I live in colorado springs, is there any tunner that you would recommend around here? or I should drive to Cali? rather not

Click to expand...

Import Sports in Denver. Ask for Steve.

@Hondata
I got a 2018 CW for 5 months now,installed the K-tuned DP/FP a few days ago and CEL came up on me yesterday. Also got AFE intake , Now I know I can have that fixed with Hondata flash pro however didn’t anticipate doing that until After winter in Toronto.
Is it ok for me to drive with the CEL on for a while?
Otherwise , where do u suggest I should send the ecu for jailbreaking. Can i trust the local Hondata dealers?

http://www.hondata.com/forum/viewtopic.php?f=29&t=21708 v3.1.6 released

@Hondata I'm new here, and I just recently purchased my first performance upgradesfor my 2018 CTR. I have a PRL Downpipe, PRL intercooler, mishimoto intake, and Hondata flashpro. Last week I finally installed my jailbroken ECU and unfortunately got a P0139 error pretty quickly after I started driving again.

No biggie, as I know I can just turn it off with my flashpro. Unfortunately, that doesn't seem to be working. I'm using a 93 octane, downpipe, intercooler map with secondary O2 sensor disabled. I even went in to the closed loop section in calibrations and made sure the P0139 error was disabled.

I reflashed the ECU again to see if it was just a one off but, unfortunately, it repeatedly keeps coming back even with the P0139 code disabled. Sometimes it's in 20 miles and sometimes its in 60 miles; it just seems random. I purchased PRL's recommended Fabspeed O2 defouler yesterday to see if I can make it so no CEL code ever pops up, but I need help/advice on what's causing this or what I'm doing wrong.

This weekend I'm going to take everything off again to make sure everything is seated/sealed right and install the new O2 defouler, but I had one of my buddy's, who is a certified Honda tech, help install everything so I don't think that's the issue, especially if I should be able to turn the code off entirely using my flashpro.

Any help would be much appreciated!


**Edit**

Here's the tune I'm currently using, along with the secondary downpipe O2 sensor disabled.

As you can see, the error still pops up even when I have the error disabled in my tune.