Claviger
Aspiring Student
- Joined
- Jul 25, 2014
- Messages
- 6,934
- Location
- Olympia Washington
- Ride
- '21 Z H2, '14 R3R, '02 Daytona 955i
For those interested in doing it yourself, or who are nowhere near a dyno, I figured I'd show how I do it and how you can adapt the bike quickly.
WARNINGS -
o If at any time you see AFRs in the 15.5:1 or leaner range that's a problem, stop, add fuel to that RPM/TPS area of the table in PC-V, about 10% and start again.
o The more power you make, the harder this is to do! It's very very difficult to do on my bike, for example, at the 70% and higher TPS values I'm either accelerating very quickly, or, I'm traveling at go to jail speeds if using 5th gear.
o Use high octane gas, and if you have it, add 6oz of Torco Accelerator to a full tank of fuel to end up with 95/96 octane. This will prevent most knocking while the engine's at it's highest risk, during early tuning efforts. More Accelerator is not necessary so do not go dumping the whole can in lol.
o I am a HOBBYIST and my methods are MINE. They're what I've come up with that works for me over the years on various vehicles. This will get the bike into a state it can be ridden safely and running fairly well.
o There WILL be more power to be found when put on a dyno and tuned by a pro (which is why I take it to get it's final tune when I'm satisfied that I'm fairly close). I am positive this will be cringe worthy for pro's who do it on a dyno, which allows it to be done much quicker, safer, and more accurately.
Initial Adaptation:
Set the AT target something like below and go ride the bike with the closest starting TuneECU tune you have loaded, eg if tuning Reband/Sidewinder/Brute/Viking pipes but you only have a CES tune, that's fine. If tuning a Carp 240 kit and you only have the CES tune that's not close enough!! Give the AT 20% enrichment and 10% enleanment authority. For this ride, you want little traffic, and a road where you can hold the throttle at various positions without getting run over or a ticket. I like using 5th gear and holding a throttle position for each TPS column in PC-V e.g. 1%, 2%, 3% ---- 50%. 5th will slow the data rate down enough for the AT algorithm to do it's thing, climbing a hill helps even more. You want to sweep through each TPS setting a few times, like 3-5 at a minimum.
Trying to tune using 1st and 2nd gear is nearly useless over 10% throttle because the rate of gain for RPM is just too high for the AT to be accurate.
Now stop, accept all trims and then make your PC-V Target AFR table look like this:
Now you need to datalog.
Datalogging Portion:
o POD-300 - enable logging of the following at a minimum (don't try to log everything, it'll fill the memory quickly) - Injector Duty Cycle, AFR, RPM, TPS
o Set the sample rate to "raw" or maximum, whichever it's named, but you want the fastest possible speed.
Go ride the bike, doing the same thing you did during initial adaptation, but datalog the ride in the POD-300. Ensure you end the log before turning the bike off, I've had corruption issues when forgetting to do so.
So now pull the datalog off the POD-300 using the Power Core POD-300 Device Manager "export to WinPEP 8 Data Center" option. I set up my WinPEP8 to look like this:
What you want to look for is areas of constant throttle position that sweep through RPMs. Then go into the PC-V software and add the amount of fuel or remove it to hit the AFR you're after.
For example, in the above photo, I'm working with the 2% TPS column and 2750 RPM bin. To find the percentages you'll want to use Lambda to AFR conversion to estimate the % to add/remove. Lambda is a percentage, so 5% fueling adjustment should be about 0.7 AFR shift.
So for the above log, I will add 5% fuel to the 2% TPS and 2750 RPM bin to bring the AFR down to around 14:1 instead of 14.7.
You want to do this for all the areas that have a 0 in the Target AFR table you set earlier. This might take 2 or 3 sessions to get it dialed in right. Don't try to manually tune the log file areas that the AT is still active, those areas in the Target AFR table that are not 0s. You'll end up over compensating, because the AT will have made some adjustment already.
As you work through the whole table, slowly put 0s into the Target AFR table more and more until you're satisfied with your work. It is time consuming and the whole process is predicated on having a tune that is close enough to be ridden around in the first place.
WARNINGS -
o If at any time you see AFRs in the 15.5:1 or leaner range that's a problem, stop, add fuel to that RPM/TPS area of the table in PC-V, about 10% and start again.
o The more power you make, the harder this is to do! It's very very difficult to do on my bike, for example, at the 70% and higher TPS values I'm either accelerating very quickly, or, I'm traveling at go to jail speeds if using 5th gear.
o Use high octane gas, and if you have it, add 6oz of Torco Accelerator to a full tank of fuel to end up with 95/96 octane. This will prevent most knocking while the engine's at it's highest risk, during early tuning efforts. More Accelerator is not necessary so do not go dumping the whole can in lol.
o I am a HOBBYIST and my methods are MINE. They're what I've come up with that works for me over the years on various vehicles. This will get the bike into a state it can be ridden safely and running fairly well.
o There WILL be more power to be found when put on a dyno and tuned by a pro (which is why I take it to get it's final tune when I'm satisfied that I'm fairly close). I am positive this will be cringe worthy for pro's who do it on a dyno, which allows it to be done much quicker, safer, and more accurately.
Initial Adaptation:
Set the AT target something like below and go ride the bike with the closest starting TuneECU tune you have loaded, eg if tuning Reband/Sidewinder/Brute/Viking pipes but you only have a CES tune, that's fine. If tuning a Carp 240 kit and you only have the CES tune that's not close enough!! Give the AT 20% enrichment and 10% enleanment authority. For this ride, you want little traffic, and a road where you can hold the throttle at various positions without getting run over or a ticket. I like using 5th gear and holding a throttle position for each TPS column in PC-V e.g. 1%, 2%, 3% ---- 50%. 5th will slow the data rate down enough for the AT algorithm to do it's thing, climbing a hill helps even more. You want to sweep through each TPS setting a few times, like 3-5 at a minimum.
Trying to tune using 1st and 2nd gear is nearly useless over 10% throttle because the rate of gain for RPM is just too high for the AT to be accurate.
Now stop, accept all trims and then make your PC-V Target AFR table look like this:
Now you need to datalog.
Datalogging Portion:
o POD-300 - enable logging of the following at a minimum (don't try to log everything, it'll fill the memory quickly) - Injector Duty Cycle, AFR, RPM, TPS
o Set the sample rate to "raw" or maximum, whichever it's named, but you want the fastest possible speed.
Go ride the bike, doing the same thing you did during initial adaptation, but datalog the ride in the POD-300. Ensure you end the log before turning the bike off, I've had corruption issues when forgetting to do so.
So now pull the datalog off the POD-300 using the Power Core POD-300 Device Manager "export to WinPEP 8 Data Center" option. I set up my WinPEP8 to look like this:
What you want to look for is areas of constant throttle position that sweep through RPMs. Then go into the PC-V software and add the amount of fuel or remove it to hit the AFR you're after.
For example, in the above photo, I'm working with the 2% TPS column and 2750 RPM bin. To find the percentages you'll want to use Lambda to AFR conversion to estimate the % to add/remove. Lambda is a percentage, so 5% fueling adjustment should be about 0.7 AFR shift.
So for the above log, I will add 5% fuel to the 2% TPS and 2750 RPM bin to bring the AFR down to around 14:1 instead of 14.7.
You want to do this for all the areas that have a 0 in the Target AFR table you set earlier. This might take 2 or 3 sessions to get it dialed in right. Don't try to manually tune the log file areas that the AT is still active, those areas in the Target AFR table that are not 0s. You'll end up over compensating, because the AT will have made some adjustment already.
As you work through the whole table, slowly put 0s into the Target AFR table more and more until you're satisfied with your work. It is time consuming and the whole process is predicated on having a tune that is close enough to be ridden around in the first place.
Last edited: