Rapid bike evo fueling management, anyone dealt with these?

Dopey

Registered
Joined
Jul 13, 2017
Messages
2,107
Reaction score
3,718
So I had a kawi z1000 come into my shop the other day for a full akro exhaust install and a few other things one of which was a fuel manager. Instead of the usual power commander I was handed a "Rapid bike evo". Having never seen this I had to do a little research and found it to be pretty cool compared to the basic pc5. It had what's called auto adaptability which is kind of like auto time except it changes the parameters on its own so no more having to find long stretches of road to hold the bike at certain high speeds in order to log it and change it yourself later like @Mythos had spoke about in some of his posts. Does anyone have any experience with using these and have real world feedback? Seems like it may be a good option to give to some of my customers over a power commander if I know they are worth it and do what they are advertised to do.

Mythos

Registered
Joined
Feb 4, 2009
Messages
5,225
Reaction score
7,094
The reason to hold a selected throttle position when acquiring AFR data is so that you will tune every cell in the column for that throttle position. This is for the purpose of knowing what cells have been tuned and which have not. It's just a lot more directed and thorough. Obviously, only the cells in the TP column you are tuning will have trims generated if you stay only at that throttle position. In addition to maintaining one throttle position, I also deselected all other columns in the map so there was no way they could inadvertently be changed while doing tuning runs for the column I was focussed on tuning. Once you're done tuning one TP column, you SAVE the fueling you created to the permanent map in the PC5 and move on with tuning the next TP column in the same way. If you changed throttle positions while you were doing a tuning run and you had all cells in all columns activated for tuning, you would be gathering data for cells all over the map. It would be impossible to know which cells were left untuned. Two other points that pertain to DJ Auto Tune is that A) its sample rate is pretty slow and B) it doesn't produce accurate trims when backing off the throttle. Those are also reasons to limit your tuning to one TP column at a time, you do run after run until Auto Tune narrows in on the perfect trims only for the column you are working on. If you allowed Auto Tune to make trims all over the map, it would get very confusing. I believe my method of tuning one throttle position with Auto Tune is usally used to tune on a dyno as well.

DJ Auto Tune is capable of tuning as you ride the bike. You can enable it to change fueling all over the map as you ride. However, I have seen how it bounces the AFR up then down then up then down while I ride the bike normally. The reason is that I never hold a steady throttle position when I ride. Auto Tune isn't fast enough to keep up with how much I change throttle positions and it overwrites with faulty trims when backing out of the throttle. The only time Auto Tune works in real time is when I am cruising straight down a highway, then it takes Auto Tune about 3 seconds to get enough samples to create a stable AFR. With Auto Tune enabled while you ride, the trims it generates are applied to the map but they are not saved to the map at all (unless you manually save them with a laptop on the bike and I think you can also save with a POD-300). This is a good thing because as I described, the trims DJ Auto Tune generates during normal sport riding are useless. It's too slow to generate perfect trims while the TP and RPM are both changing faster than it can sample.

So there's why you focus on one throttle position with DJ Auto Tune. Also, I believe tuners do the same on a dyno even though they must have a far better sensors than the O2 sensor provided with DJ Auto Tune.

Sounds like Rapid Bike Evo has the ability to tune while you ride like DJ Auto Tune does. If it samples 300 times per second, it might work while you ride. I forget the exact number but it's only about 12 samples per second for DJ Auto Tune. Bazazz was slightly slower with 8 samples/second.

If the Rapid Bike Evo can sample fast enough, I wouldn't worry so much about doing tuning runs. I'd just get on the bike and ride and let the Evo do it's thing. If there are rpm/TP zones in the map where the engine rarely ever runs, no big deal, those cells will get adjusted if and when the rider operates the engine in those ranges of TP and rpm. I'm not saying there would be no reason for thorough, purposeful, focussed tuning but it would be a lot less necessary if the tuning system was lightening fast like we would hope they all would be.

There was a guy on here who was familiar with tuning equipment that was affordable and far superior to DJ. Was it @Dennis ? LOL I bring him up every time this topic arrises.

My advice is to stick with the tried and true DJ systems if you ever want to do dyno tuning. I've been through it with Bazzaz and now they're gone. No telling what less known equipment will become obsolete. If you're only going to self tune, go with the systems that work well because I have heard those systems do exist. ...I'm just not sure which ones they are.

Dennis

Registered
Joined
Feb 28, 2006
Messages
2,071
Reaction score
2,281
@Mythos , I'm familiar with Maxx ECU, but it is a totally standalone ECU. There are 5 or 6 variations of them at different cost and capabilities. It is definitely not as simple as a piggyback system, but it is far superior and makes life so much easier. There are other brands of standalones also. These ECU's are capable of doing real time AFR adjustments on the fly. You may be very familiar with these, sorry if this is elementary education for you, no insult intended.

Edit: I'm also familiar with EE and Woolich which I think are pretty well understood here. Woolich will do autotune from a log file.

202mphbusa

Registered
Joined
Oct 30, 2006
Messages
2,961
Reaction score
5,631
remember no matter HOW FAST a ECU can read and respond
the info it is getting (O2) is downstream and after the fact and can be TOO after the fact under HARD boost

Dennis

Registered
Joined
Feb 28, 2006
Messages
2,071
Reaction score
2,281
remember no matter HOW FAST a ECU can read and respond
the info it is getting (O2) is downstream and after the fact and can be TOO after the fact under HARD boost
I dunno about TOO after the fact, but I like to be telling the ECU my fuel demand such that I am about 3-4% fat so corrections are small and only pulling fuel. You don't want to be a mile off and asking the ECU to fix everything. Then there are the correction speed & limits to consider. I run up to 28 pounds of boost on my buddy's bike and lambda control seems to do ok. It will certainly make higher boost and I don't have any concerns with lambda control. If the map is junk and you don't have lambda control on you can also have a bad day. I also run EGT protection on my nitrous bike but haven't come close to the limit.

202mphbusa

Registered
Joined
Oct 30, 2006
Messages
2,961
Reaction score
5,631
to semi quote daveO
How many firing cycles in a second? how many seconds for the exhaust pulse to reach the O2?
More then 3-4 firing cycles? how long to hurt something?
add ANY ecu response time and it is AFTER the fact
TOO long after? many many variables there how far off? rich or lean?
Too rich where O2 reads lean?
(he had numbers he calculated)

Dennis

Registered
Joined
Feb 28, 2006
Messages
2,071
Reaction score
2,281
11k rpms is 92 Hz firing rate. ECU is 1000 Hz. I have my lambda control running 20 Hz. A perfect map that needs no adjustment is the best. A less than perfect map that gets real-time correction is better than not having real-time correction. I've never been too rich that the sensor reads lean. I've had nitrous turned on but the bottle off and been so fat the bike breaks up down track and the lambda told the right story. You have to understand that the sensor is measuring oxygen, not fat/lean so on a shift kill it will spike lean even though it is fat because no oxygen was consumed.
Back
Top