Howdy,
Just wanted to see if anyone else has had similar issues.
Over the last two weeks, I've had two sessions where the BGT-31 has stopped logging data at exactly 10am AEST.
I thought it might have just been my device, but another Southerly Buster in GPS Team Challenge- Fireman Sam, had exactly the same thing occur.
Just curious to see if anyone else had anything like this happen??
The dates of the sessions which failed were:
10am on 14/10/2013
10am on 27/10/2013
Did those GPS's travel any type of distance (over say 300km) sometime in the last few weeks or have they not been used in quite a few months?
Over the years the Sandy Point speed comp's have experienced quite a few lock-ups by various people, but never really understood why. Then last summer we determined that if you have traveled a good distance without allowing your GPS to "settle", then there is high likelihood that that it would freeze -> a possible cause for this was that the SpeedGenie was enabled, at the same time the GPS decided to perform an almanac update.
So the advice was, "make sure you allow your GPS to sync with the satellites (say 1hr) if you are travelling far or haven't used it in a long time".
As for the specific time of day, not sure about that one... only question would be "when was the GPS used last?"
Were going to try switching one to "gps on" and not fix and see if we can get the same result. Both units haven't travelled that far and have been used far too much 
in the local area.
The 10am thing may be a sat dropping out ????
Select to expand quotekato said..
Were going to try switching one to "gps on" and not fix and see if we can get the same result. Both units haven't travelled that far and have been used far too much in the local area.
The 10am thing may be a sat dropping out ????
one should never use the "on fix" option... I used to have tracks to show that it is broken... and you shouldn't need to, as the 2GB is plenty of storage space.
The only other option that I can think of that relates to 10am, might be again due to an almanac update but coinciding with midnight-UTC (aka 10am local time).
10am seems a little early for being on the water... did they freeze while in use?
In any case I'd suggest letting them sit for about 1 hr before use.
Hey Mathew and Kato,
Thanks for the info.
I checked the trackpoints and we had 7-8 sateliites visible.
I just found the same thing happened at the same time on Sunday's session with another GPS- (Robbie K)
Here's my trackpoints @ 9.59.59am
911 Sat Oct 26 23:59:58 EST 2013 145.7463828 -38.6395748 1.019 Km 88 Cm 1 0.1 0.2 7 1.00 3.18 1.72 1.75 147.10 OK
912 Sat Oct 26 23:59:59 EST 2013 145.7463862 -38.6395823 1.019 Km 0 Cm 86401 0.0 -0.0 7 1.00 0.00 0.00 0.00 166.05 OK
Here's ROBBIE_k's
360 Sat Oct 26 23:59:56 EST 2013 145.7463049 -38.6393681 653.12 meters 77 Cm 1 0.1 -0.0 7 1.00 2.76 1.49 1.36 170.60 OK
361 Sat Oct 26 23:59:57 EST 2013 145.7463052 -38.6393750 653.12 meters 0 Cm 86403 -0.0 -0.0 7 1.00 0.00 0.00 0.00 177.00 OK
The number underlined is the Time value (in seconds) which if you divide by 360 gives you the equivalent of 24 hours. I wonder if we are getting tripped over because of the timezone shift and the roll over to a new day on Greenwich Mean Time...
Mick
Ok found the source of the issue..
its the software...gpsar pro...doesnt like sessions which span over a day (eg midnight at GMT)
Tried the session on ka72 and then in realspeed and I could get data off both.
All good....crisis averted 
Open the trackpoint table in GPsar then delete the 2 lines at GMT midnight . Then refresh the speed results to see your whole session. Just hope those 2 lines aren't your 2sec peak.
There is probably a setting somewhere in GPSar where you can say what timezone you are in, and then you won't have this issue. There is in GPSResults. ka72.com takes a guess what timezone you are in based on your coordinates.
As a (Queensland) software developer, anything odd that happens at 10am just screams Midnight GMT issues to me.
Select to expand quoteDylan72 said..
There is probably a setting somewhere in GPSar where you can say what timezone you are in, and then you won't have this issue. >>>>>
Yep, up the top under "settings" there is a timezone select menu.
