Not sure which forum this topic belongs in but here goes.
I use a Garmin GLO external bluetooth GPS sensor. It connects easily to Laptimer and when I check the GPS settings in the menu, I see that it is transmitting or reading at about a 6 - 8 Hz rate.
But when I look at my lap data, every lap always shows External @1.0 Hz. I did 61 laps last week and every lap showed the same rate.
What is the explanation for that?
Thanks in advance.
GPS readings.
Re: GPS readings.
I'm not completely sure about this, but I guess it's because the GLO is not implemented into Laptimer and uses the location services instead of direct NMEA like Dual or VBOX.
Re: GPS readings.
Something is off. I checked the map today with GPS showing a 8-9 refresh rate. The map location only works if I have the phone location services on. Turn them off and I get no map location on Laptimer.
I hate to spend money on a different GPS system, because otherwise, the Garmin GLO seems to work well.
I hate to spend money on a different GPS system, because otherwise, the Garmin GLO seems to work well.
Re: GPS readings.
Upon further reflection...
I'm using a Samsung Note 2 with Android 4.3
The phone has plenty of horsepower to process data
The phone connects easily via BT with the Garmin GLO
The GPS screen in Laptimer indicates a connection, plenty of satelites, and a 8-9hz refresh rate.
On the track last Friday I did not turn off the phone's location services.
Every lap detail report showed external@1hz
# of fixes per lap was pretty consistent. It's a 2.5mile track. My fastest lap had 239 fixes (2:08) My slowest lap (2:22) had 285 fixes.
Today, while testing this at home, when I turned off the phones location services, the map in Laptimer did not work. I pressed the location icon and nothing happened.
In conclusion - the phone connects to the BT, Laptimer GPS screen is reading signals from the BT, but the program appears to be using the internal GPS for actual recording.
I'm pretty clueless when it comes to technology, but it appears to be a programming issue in Laptimer.
I haven't had a chance to try it at the track since last week, this time turning off the phone's location services, but if the map won't work just with the external, it seems doubtful the laptimer will work either.
Maybe Harry can provide an answer for us?
I'm using a Samsung Note 2 with Android 4.3
The phone has plenty of horsepower to process data
The phone connects easily via BT with the Garmin GLO
The GPS screen in Laptimer indicates a connection, plenty of satelites, and a 8-9hz refresh rate.
On the track last Friday I did not turn off the phone's location services.
Every lap detail report showed external@1hz
# of fixes per lap was pretty consistent. It's a 2.5mile track. My fastest lap had 239 fixes (2:08) My slowest lap (2:22) had 285 fixes.
Today, while testing this at home, when I turned off the phones location services, the map in Laptimer did not work. I pressed the location icon and nothing happened.
In conclusion - the phone connects to the BT, Laptimer GPS screen is reading signals from the BT, but the program appears to be using the internal GPS for actual recording.
I'm pretty clueless when it comes to technology, but it appears to be a programming issue in Laptimer.
I haven't had a chance to try it at the track since last week, this time turning off the phone's location services, but if the map won't work just with the external, it seems doubtful the laptimer will work either.
Maybe Harry can provide an answer for us?
Re: GPS readings.
I decided to check this also as my s3 is also running android 4.3. My results are just like yours but i never noticed it. Qstarz 818xt 10hz shows external 1 hz on every lap. Hope its just labelled wrong
Re: GPS readings.
The problem though is that the number of fixes seem far too low for a 10hz refresh rate. Unless I don't understand the refresh rate which is entirely possible. But 240 give or take fixes in just over 2 minutes seems way low to me.BoomSpoon wrote:I decided to check this also as my s3 is also running android 4.3. My results are just like yours but i never noticed it. Qstarz 818xt 10hz shows external 1 hz on every lap. Hope its just labelled wrong
Re: GPS readings.
Forget about my post, didn't know you were talking about HLT on Android. What I said would have been a iOS only problem.
Re: GPS readings.
While the update rate displayed may be wrong (it is a complex calculation as it need to cope with lots of different timing behavior and filter compression effects), the number of fixes should be roughly the number of seconds multiplied by the update rate. So if you read 239 fixes for a 2:08 lap, 1 Hz is stored only. I just ran some quick tests with the current Android release and it stores 10 Hz for the XGPS160, and 20 Hz for the VBOX. I have no Qstarz 818xt available, but will try my GLO once it is charged again. I'll come back on this.
@futurz and @BoomSpoon, just to verify: you have paired your QStarz / GLO with the smartphone and have no helper apps installed fiddling around with GPS? You have added the sensors in LapTimer's Sensor List using the +BT button and the sensors show up as connected (green) with an update rate > 5 Hz?
- Harry
@futurz and @BoomSpoon, just to verify: you have paired your QStarz / GLO with the smartphone and have no helper apps installed fiddling around with GPS? You have added the sensors in LapTimer's Sensor List using the +BT button and the sensors show up as connected (green) with an update rate > 5 Hz?
- Harry
Re: GPS readings.
Hi again,
I have been able to reproduce the issue for the GLO, it will be fixed in version 18.0.6. Problem has been it used an unexpected format for the UTC time. It is well possible, the same issue applies for the Qstarz, but I can't test it from here.
@BoomSpoon: once 18.0.6 is available (approximately in 1 hour from now) andyou find the time, please record a short lap with your Qstarz connected and 10 Hz GPS update rate displayed. No need to do this on track / street, as long as you have a GPS fix, it can be done everywhere. Enable manual operation first: LapTimer -> Settings -> Behavior -> Manual Timing -> ON; now change to Timer view. You will see a large red "Start" button. Press it, wait some seconds, press the large free "Stop" button; switch to Lap List and search for your short manual lap; select and check you see "External @ 10.0 Hz" in the GPS Sensor row. Thanks!
- Harry
I have been able to reproduce the issue for the GLO, it will be fixed in version 18.0.6. Problem has been it used an unexpected format for the UTC time. It is well possible, the same issue applies for the Qstarz, but I can't test it from here.
@BoomSpoon: once 18.0.6 is available (approximately in 1 hour from now) andyou find the time, please record a short lap with your Qstarz connected and 10 Hz GPS update rate displayed. No need to do this on track / street, as long as you have a GPS fix, it can be done everywhere. Enable manual operation first: LapTimer -> Settings -> Behavior -> Manual Timing -> ON; now change to Timer view. You will see a large red "Start" button. Press it, wait some seconds, press the large free "Stop" button; switch to Lap List and search for your short manual lap; select and check you see "External @ 10.0 Hz" in the GPS Sensor row. Thanks!
- Harry
Re: GPS readings.
Correct, I have the helper app installed because I used it for Race Chrono but I closed it with a forced stop before using HLP. It did a test with it on yesterday and it seems to cause some interference so I did a force stop. Everything shows up correctly in the sensor list.Harry wrote:While the update rate displayed may be wrong (it is a complex calculation as it need to cope with lots of different timing behavior and filter compression effects), the number of fixes should be roughly the number of seconds multiplied by the update rate. So if you read 239 fixes for a 2:08 lap, 1 Hz is stored only. I just ran some quick tests with the current Android release and it stores 10 Hz for the XGPS160, and 20 Hz for the VBOX. I have no Qstarz 818xt available, but will try my GLO once it is charged again. I'll come back on this.
@futurz and @BoomSpoon, just to verify: you have paired your QStarz / GLO with the smartphone and have no helper apps installed fiddling around with GPS? You have added the sensors in LapTimer's Sensor List using the +BT button and the sensors show up as connected (green) with an update rate > 5 Hz?
- Harry