Harry's GPS Suite Forum

Hi Harry et al.,
I have been having multiple problems getting HLT to work at all. Here's my setup and then my problem:

OBDlink MX Wifi
DUAL GPS 150 (and I just got a brand new one yesterday in the mail - the old one I accidently bricked when I inadvertantly updated firmware which was a downgrade that doesn't work!)
Iphone 4 - no SIM card though (I am just using it for HLT, not as a phone)
Track - Thunderhill (last time 2 mile, today 5 mile with cyclone)

I don't know if its not recognizing the track but 3 weeks ago, it didn't record anything most of the day - except one session. Today I got nothing - although both times when I pulled into pits it claimed it was still recording and I had to manually cancel. I got nothing in the lap list though. This is incredibly frustrating. I checked my setup against someone else - looked in the sensor list and the only difference I saw vs. his was the dual default delay was 1.5s in mine and 0.7s in his. So I changed to 0.7 - no difference.

I tried mounting the iphone in the windshield instead of not visible to the outside. That didn't help.

I'm wondering if part of the problem is the Dual - I did try one session last time not using it and I think that worked. I can't recall exactly.

I just saw a note on your compatability page about multiple sensors requiring iphone 4s or better - is that my problem?

Like I said, last time I was able to get one session of laps so the setup obviously can work. But I don't know what I did different that session versus any other session.

Scott

My idea was to mount the iphone in the car (not visible to GPS) and use the Dual. The

Hi,

The sensor delay has no impact. For the iPhone4, OBD data may generate trouble because the device is probably not able to handle OBD traffic fast enough. The GPS side will usually not be the issue as data is coming with a timestamp of origin - which allows to process it even if very late.

The two major reasons for missed triggers (and this is the problem you are most probably facing) are the track set is not loaded or corrupted (manually changed), or GPS reception is bad. Both items are actually checked by LapTimer itself. It will display a red alert, tap it to get a problem description plus help to work around.

For the 3 weeks ago session, the problem might have been the copy protection issue we had with 19.0.0 - but this is fixed since 19.0.1 Please make sure you have updated the app to a later version!

- Harry

I don't recall seeing any alerts - I'm assuming I would have noticed them. The weather was not cloudy and my Dual GPS was mounted in the front on the dash open to the windshield so I assume there should have been no issue with visibility to satellites.

Is there any log that would have been retained that I could send?

Also, I hadn't updated the app for a while - I'm pretty sure I had version 19 but I don't know which sub-version. I just got the version you updated yesterday but that was after I had done my track day.

Is there some way to reliably test this setup while around town? For instance, set up my own trigger points? How accurate do the trigger points have to be? I'm wondering if the trigger points set by whomever set up the track initially was with a lower quality GPS that may have been off (although I would expect that many people would have complained by now).

A few more bits of info - I was looking at this thread and thought I had exactly the same issue (mine is the same set up as his) viewtopic.php?f=9&t=641&hilit=POI+detection&start=10 , but then he said he updated the Dual firmware and it worked fine. In my case, I just got a brand new Dual device from them after I accidentally bricked mine and I know the new one works as it worked fine with the Dual iPhone app.

The other thing - maybe I need to set the POI detection to wide?

Someone else mentioned having old tracks still loaded? Well, I've got a bunch of versions of tracks loaded from the area. None of the others are particularly close though - but I ran Thunderhill 2 mile course 3 weeks prior and then Thunderhill 5 mile course yesterday. Both were loaded. The start/finish is on the 3mile (same as 5 mile) start. I don't think I had the 3 mile course loaded though. Do I purge the GPS to delete that track? I couldn't find another way to delete.

For Thunderhill - we have 7 configurations in the database. While one of the recent configurations has not been used, older ones show up to 36 thousand laps recorded. In case you want us to check a configuration, please let us know which one you used.

The alert is a red alert sign shown in the navigation bar in top of the screen. It is no prompt.

To test LapTimer off track, just use the New Track assistant and drive around the block. It is easy and guided.

- Harry

Sorry, I updated my last message with the versions I used. Can you reread that message?
Unfortunately, I'm 3 hours drive away from the track and I won't be going back for another month or so.

2 mile has 1500 and 5 mile with cyclone has 3000 laps recorded. These are not high numbers but the configurations have been introduced late in 2014 and are probably not used that often... So it is not a clear indicator it is perfect, but it should capture at least a few laps...

You do not need to set detection to Wide, this setting is used automatically in case the triggers defined for the track set have a driving direction defined.

Back to conflicting tracks: you need to differentiate between a track definition (= track set or a set of triggers and POIs) and actual recordings. While you must not have loaded conflicting track definitions at the same time, you can keep your recordings for different configurations without any issue. To remove conflicts it is actually easiest to trust LapTimer: load the configuration you plan to drive next from Add-ons or Load Track. LapTimer will load it and check for conflicts afterwards. In case it find conflicting track definitions it will promote you and recommend to purge these conflicting track sets. Confirm and LapTimer will take care you have a conflict free setup.

As LapTimer needs to make the connection between software (virtual) and reality, there are many reasons things can go wrong. I doubt you will find the issue by comparing too many posts here on the forum. It is really best and easy to define your track around the block and verify it works now that you have more insights.

- Harry