Training Log Archive: Jagge

Pretty hard run forest run without warmup. Wohoo, knee is getting better! But HR figures may tell more about my current fitness than my knee.

Continued with bike, Better not run too much too soon.

Next week there will be some O for sure.

20 sec jogging + 10 sec walking x 20 plus some walking as warmup. First virtually painless running steps since Jukola. New beginning.

Online result system test biking:
http://www.yokuppi.net/online/oresultblues.cgi?cla...

Page should auto refresh one per minute. My nick should pop up in 30 minutes (as a started competitor) and I should finish about hour later.

(Should work if bluetooth range is good enough between living room window and bike storage door).

Today we bought touch sreen lap top for my dad. While we installed all kind of software and set up bt gps connections and stuff like that Topias tried to touch the screen several times. We did not let him because sceen would get dirty. We should have let him test it, because after all the hard work we found the touch sreen defective and we had to take the device back and get replacement.

Event: Yökuppi 5 Lahti, Kukkila-Paimela
 

Some details of the system I have been working on:

Codename OResultBlues, electronic online/offline/intermediate time timing system for orienteering trainings (and add on intermediate times for races).

Basic idea is use cell phones, web and bluetooth devices to trigger competitors start, visits at intermediate controls and finishing. Runners carry BT device, basicly any device as long as it broadcasts it's hex adress constantly. BT GPS loggers, cell phones, bt hands free ear plugs, what ever. I perfer BT gps loggers, because you can download routes too after the actual run. Cell phone triggers start time (device dissappears out of bt range and stays there for given amount of minutes, default 15). Finish and intermediate times are triggered by being in range. System can be used with SI, Emit, pin punching or no punching at all events.

Start time options are:
- pre-defined start times
- bt triggered start time
- bt triggered start time rounded to neares sharp minute

Setup options:

1) one phone as combined start& finish, offline. NO cell network needed, result are can be seen at phones screen and exported to file. Start and finish must be at same location or you must be able to transport phone from start to finish in time.

2) one phone as combined start& finish, offline. Same as pervious but results are posted to web on the fly. So results can be seen both in the phone app and web.

3) several phones, online. Start phone, combined start&finish or pre defined start times. Intermediate phones and finish phone. Or one can have no fisnih phone and use this only as online intermediate timing system.

Phone app is python script, runs on s60 Nokia 2nd edition and forward. Server side is perl script at the moment, not quite finished yet and some features are missing, but can already be used.

Drawbacks:
- timing is based on BT scans, those take over 10 seconds, and also bt range may vary so accuracy of triggered times is about 10 seconds. OK for trainings and intermediate times and maybe unofficial web times, but not good for any race timing.

Download:
http://www.routegadget.net/oresultblues/oresultblu...

Test site:
http://www.routegadget.net/oresultblues/oresultblu...

I'll post some screen shots later.

Using it is pretty easy. For example on the start&finish mode iyou just turn it on, leave it at start / finish. After the event you have results on your phone. If you dont register devices (give real runner names) you have results for device hex addresses.

According to my watch my yesterday's biking took 54:08. Alpha version of my automatic online timing system spit time 54:07 to it's web page. I am happy with that.