Harry's GPS Suite Forum

Hi All, perhaps someone can help me figure out what's going on.

I was driving at Mazda Raceway Laguna Seca yesterday, and my best session was from 3:48 - 4:09 PM in the PST time zone (UTC - 8).

3:00 PM PST = 23:00 UTC, and 4:00 PM PST = 00:00 UTC the next day.

So, during my session, the day changed in UTC, and Harry's Lap Timer lost that entire lap, and a portion of the lap before it.

In my CSV export, I see the last time stamp before the change over looking like this:

LAPINDEX,DATE,TIME,TIME_LAP,...
46,12-FEB-14,23:59:42.62,103.390000,...

Then the next data point is:
48,13-FEB-14,00:01:27.09,0.000000,...

Approximately 1 minute and 27 seconds are missing, which thoroughly confuses the overlay renderer I'm using (RaceRender 3). On the iPhone, the missing lap, 47, only has a lap time, but no GPS data available.

This was my best session ever, and the missing lap is precisely the one I'm interested in. Is there any way to recover this?

We just found and fixed this bug in LapTimer v18 beta testing. The "West Coast bug" - named by the region it appears, is indeed related to crossing UTC 0 and happens with NMEA integrated GPSes only. Workaround: restart LapTimer shortly after UTC 0 and it will work again.

I'm sorry for the lost lap - at least the problem will go away soon...

- Harry

PS: this problem dates back to the very first version of LapTimer...

Cool, glad to hear that it's fixed. It turns out that it lost precisely the one lap which had the UTC roll over. No problem, I created a fake lap in the CSV file which made RaceRender happy.