Quote:
Originally Posted by CanAutM3
For me, a lap timer/data logger function is more relevant and much more useful as a learning tool. They seem to have improved the ///M lap timer app, but we have not seen much about it yet. I mostly hope they brought back the sampling rate to something that is actually useful (the previous lap timer was downgraded to 1Hz at some point).
|
I used it over the weekend for the first time in my F92. I got as far as exporting my mpower file and extracting it to see all the .far files (each one is 123k for 13:02 of recording, so about 160 bytes per second for each collection point). I didn't get as far as decoding the .far files to see the data yet. I think I saw someone had published a python script at github that should be able to convert them to csv, though. Perhaps I'll do a write-up once I take a look, but feel free to PM me if you want the file.
Looking at the recording through the app, it's much more than 1Hz. I can see the time displayed is incrementing somewhere between 25 and 33, and it seems to be holding onto data points in the display on the graph for 3 of those cycles, so looking at something between 8 and 11 hz at a minimum based on that.
The only issue I really had with the recording was that the gps seemed to be off when I got near some heavy fencing on the track. Nothing crazy, but a little inaccuracy that was very noticeable (about 50 ft) in my heatmap at 2 corners, and my line vs the satellite image along a wall.