Old 09-21-14, 10:32 PM
Senior Member
bitingduck's Avatar
Join Date: Jan 2005
Posts: 3,166
Mentioned: 3 Post(s)
Tagged: 0 Thread(s)
Quoted: 40 Post(s)
Likes: 0
Liked 0 Times in 0 Posts
Originally Posted by carleton View Post
Thanks, bitingduck, for the split timer idea.

I have a UI with two buttons that a observer will tap as each rider crosses the start/finish line.

The back-end arrays have this data in them. I had it write out the Rider, Rider's Lap, Split time, Lap time, Lap Avg Speed, and Lap Avg Cadence. I have to flesh out the latter two values later this week. I'll need gear and track length as inputs, but that's not hard.

As you can see in this 6 lap race, Rider 2 went out hot but rider 1 caught him on lap 3 and continued on to win.

I'll make a much more user friendly output. But, I'm happy to have the buttons logging as expected
That was fast!!

As far as bluetooth-- don't use BLE, it's useful for trackers like tile where you want the battery to last a year, but you don't need that. Crank up the power as much as you can! 100 m range will cover anything on a 250 m track. Doing 200 m times (e.g. with two tapes) in a 333 or larger could be tricky, but if regular bluetooth will cover a longer range you should be ok.
Track - the other off-road
bitingduck is offline