After many false starts, I was finally able to update the firmware on my XGPS160 to 1.3.0 using the new version of the iPhone SkyPro app (2.2.0) on an iPhone 4. What seemed to work was to delete the app, reboot the phone and reload the app. In the meantime, I had also updated the iPhone OS to 7.1.1...

Interesting, thanks. What device was this captured with? I thought VBox Sport had the same Bluetooth issue that XGPS is having (on iOS 7.1+).

The speed delivered by GPS sensors is not derived from position changes but the so called Doppler effect. Wouldn't it make sense to calculate GPS speed from the position fixes, if that is more accurate? Related: it appears that certain laps have a slower lap time but a faster reported average speed...

Any update on this (now that I have an XGPS160 on the way)?

Aesco48, nice video. Which version of phone do you use and how do you mount it? I mount my phone to the roll bar so I can see my hands but there is so much vibration as I go to higher rpm's that the video is not much good. I use a Ram mount on my harness bar. It gets some vibration and lots of wind...

Yes it would help a lot to be able to go from the lap chart to a particular lap. And to auto-tag laps in the lap list that have a fastest sector.

gplracerx wrote:The best sectors are colored red on the laps bar chart, IIRC.

Yea but there's now way to quickly get to the details for each of those laps or even identify them by lap number, AFAIK.

It would be nice, then, to be able to turn off the numbers as they are distracting. I love the laps chart but when something like traffic throws off a lap, it makes the numbers largely irrelevant. One would better see the progression in laps if the numbers showed time relative to the reference lap/s...

Thanks for the reply. It would make more sense to me for that to show the change from the reference or from the best sector. And I think using some consistent reference would be more useful for comparing laps to one another.

In the upcoming LapTimer version 17.5 I have included sector to sector change times (faster / slower) following the suggestion above. This should actually be exactly the table seen elsewhere. Virtual best calculation is improved too and will be less fragile in case not all laps show the same number...