SirNickity:
Bingo. Bring that max 6000 pulses-per-second down to a more reasonable number by dividing by (e.g.) 2, 3, or 6. That relaxes the demand on the AVR handling interrupt requests considerably. High dividers trade reduced resolution for less processing time. Assuming you're just looking for a heads-up display for RPM, you don't need single-revolution precision anyway.
Actualy it is for data loging.
The log will be used to judge the sailor behavior.
SirNickity:
(Although, in retrospect, it looks like this is basically what Nick was suggesting by using the timer input to fire once every however-many pulses.)
Agree.
But as I state above, i'm not good enough to understand His code.
I never play with timer before.
I only have 2 weeks to finish the project, including all server side programming.
Sincerely
-bino-