Harry's GPS Suite Forum

Had an autocross this past weekend and ran your laptimer v18.2 with the following..

iTouch 5
BT1A
Dual XGPS160

Video was recorded properly and OBDII data and GPS signals appeared to be good on the screen. Afterwords all the data files all ended up listing good data for only the first line. the next 500+ lines in each data file were wrong and identical (small sample below).

605 1 10-Aug-14 34:22.7 0 32.78179 -117.117287
606 1 10-Aug-14 51:16.0 42882286.23 32.62818 -116.96042
607 1 10-Aug-14 51:16.0 42882286.23 32.62818 -116.96042
608 1 10-Aug-14 51:16.0 42882286.23 32.62818 -116.96042
609 1 10-Aug-14 51:16.0 42882286.23 32.62818 -116.96042

It was the first time I had tried the BT1A before I had been using a WiFi link for OBD data. I was just wondering if you had any ideas.

The CSV(?) export looks corrupted, the time column in particular. I have seen a similar log some days ago and are curious how this format can be generated... Can you please export that lap to .CSV and .HLPTRL and let me know which language setting your iPod has?

- Harry

The iPod is in English..

Here is the CSV file. The HRPTRL is to big to attach here.

I also emailed both files to your email address..

Hi,

The data recorded and sent is not usable. It seems the second time stamp could not be processed correctly, which generated an "underflow" and blocked further updates. Not sure if this is due to some time stamp jump from the GPS, or has a different source. Oddly, it is not possible to reconstruct this after the fact.

The export format is fine, I got irritated by the snippet you added above. The data included in the CSV file looks like the code quote below. Format is fine, but content is not usable as written above.
In case you have some more information on the context, I'd be interested in. The above fixes shows UTC times of 20:56.38.80 and 01:51:16.00, the lap itself has a timestamp 13:56:38.00 local time. It seems you are at the west coast, so it should be UTC-7? What type of trigger did you use for the AX? Standing Go or standard Go?

I'm sorry for any inconvenience.

- Harry

I am on the West coast and we are at UTC -8 right now.
The trigger was the standing go.
Drove up to the line - hit staged on the screen - and took off.
The video was properly started, captured and stopped with the start and finish triggers

I tried some manual start logs today and they all worked without issue. I will set some triggers and try them again sometime this weekend