I haven't heard of an 8600 rev limit on any of the AP2 reflashes or FlashPro calibrations. I think they are all 8500 RPMs. However, I would bet that if you retarded timing starting at 8400 RPM's, it may not have any effect before 8500 RPMs in 1st gear at WOT due to the delay in the RPM calculation.

 

Yes. Actually, you'll want to edit all the ignition above 8100 rpm to negative.

 

I just set my timing to the most negative number that FlashPro Manager would allow (-10) ffrom 8400 on up (rev limit is 8500), and added 10% more fuel for the same range.

When I went for a test drive, it did seem to soften the rev limitter. However, when I viewed the datalogs, I was surprised to see that my IGN values were still +11 degrees. Is this a bug in the FlashPro Manager, or a hard coded minimum in the ECU for that RPM value? I see IGN values below +11 in other parts of the RPM range, and even a few negatives ...

 

I just datalogged my brother's 100% stock '06 S2000, and see that it does not retard timing at all. The engine is also bouncing as high as 8400 in 3rd gear.

 

[QUOTE=gernby,Dec 18 2009, 03:17 PM] Is this a bug in the FlashPro Manager, or a hard coded minimum in the ECU for that RPM value?

 

I use to shift when racing without removing my feet off the gas pedal. Is there any danger by shifting it at 8500 rpm with the stock map that hondata release with the flashpro? Because I'm really not well with the idea of changing anything in the table... Would you recommand me to bring down a little bit the rev limiter? And If I shift at 8100 for example still with the gas on, I guess there is not a by difference because by the time I shift the engine hit 8500 rpm... is it less damageable than shifting at 8450 with the gas on (just befor rev limiter)

Thanks, because I don't to hurt my engine!

 

If you keep the throttle pedal mashed between shifts, then you could easily pass 8800 RPMs before the ECU cuts fuel. The ECU doesn't seem to calculate RPMs very quickly, so it over-shoots.

 

^^ i don't think it would go that high. Usually you forcibly run into those rpms with car momentum and slow reactions to rpm calculations by the ecu.

The highest my si has revved with an 8600 rev limit set is 8890 rpms.

That's banging off the limiter in 3rd gear during datalogging.

Now when you "no lift shift" like he's talking about, you press the clutch and the car bounces the limiter with no load. It wouldn't be as harsh nor go as far as forcibly running into it with momentum from the car.

With that said, i try hard not to hit the rev limiter when datalogging as there's no point. Usually when i try not to hit the 8600 limiter, i rev to about 84-8500.

 

I'm not following your logic regarding momentum. The momentum while accellerating actually helps prevent the engine from overrevving so high. In first gear, the engine revs so quickly that I would expect it to overrev quite a bit more than it would in 2nd or 3rd. I wouldn't expect it to overrev much at all in 5th gear since the revs climb so slowly.

My engine overrevs by over 200 RPMS while accellerating in 3rd gear, so I could see it easily overrevving by more than 300 RPMs in neutral.

 

Dang, this whole time I thought there was some buffer built into the overrun. All the scca guys I know redline the hell out of it.

I'm not sure prelude99's question was responded to: does the flash map take this into effect, the 8200 -20? or do I have to do all of that?