Well that was interesting. In a quite, rough and ready, measurement, I got the FPS of the arrow out of my bow.
Using the method from here - https://www.youtube.com/watch?v=tazuavGL6g8
So to explain - Using my iPhone placed at exactly 1/2 way, between the arrow point as the string hits the string stop, i.e. 1'21"" from the front of the riser, and the face of the target, 20 feet total distance.
I recorded a "Voice Memo" which is the sound, of me loading up the arrow, aiming, releasing and the arrow hitting the target. I recorded 5 shots and they were all, almost the same.
Then I sent the voice memo to my mac and load it into an app called Ocenaudio.
Zooming into and selecting the bit, of the sound wave, that is, the string hitting the string stop and the arrow hitting the target, gives a duration in seconds, which is accurate to 3 decimal places.
The formula I use then, is 20 feet / 0.085 seconds = 235.294 FPS which I'm quite happy with.
The Bow I ordered, was specced at 329 FPS IBO and 30~70 lbs draw weight.
The one I received, from the research I've done, is 320 FPS IBO and 30~60 lbs draw weight.
I understand the following:
I've dialled the weight back to about 40 lbs for now, apparently I lose around 17 FPS per 10 lbs down from 60 lbs. So 34 FPS
Also lose around 10 FPS due to using a 29″ draw length rather than 30″
And lose around 22 FPS due to using a 425 grain arrow rather than the 350 used in IBO testing (I don't know my arrows grain weight so I'll take the 425 as read)
Lose around 5 FPS due to extra accessories on the string and around 3 FPS due to imperfections in human release mechanics.
Ideally my calculated reading should be 246 FPS, but it's close enough to the rough and ready, reading of 235 FPS I measured. So that's OK for me.
Once I've got the new sight and got good at the shooting side, with practise, practise, practise, I'll dial it up to 60 lbs and 30" and see if I can get near 300 FPS.
Bookmarks