[Loadstone] GPS Clock Seems to Have Stopped Ticking

gary odonoghue gary.odonoghue at btinternet.com
Wed Jun 6 08:42:46 BST 2007


Hi, I'm using an n73 with a holux gp slim 240 and I get the "clock stopped
ticking" message quite a bit with the new 0.68 version 

-----Original Message-----
From: loadstone-bounces at loadstone-gps.com
[mailto:loadstone-bounces at loadstone-gps.com] On Behalf Of Shawn Kirkpatrick
Sent: 05 June 2007 09:43
To: loadstone at loadstone-gps.com
Subject: Re: [Loadstone] GPS Clock Seems to Have Stopped Ticking


Well, after looking at the loadstone code I don't see why this should be 
happening any more frequently than it did before. If this happens in a 
predictable manner then a log of what the gps is sending might be useful. 
You et the clock stopped ticking message if the receiver hasn't sent a 
packet for more than 5 seconds. Normally the gps receiver is sending 
multiple packets every second. The only thing I can think of is that maybe 
these receivers are getting put in to power save mode or there's some kind 
of rf interference with the bluetooth connection. With a bit more data I'm 
sure we'll figure this out.

On Mon, 4 Jun 2007, Cathomas J|rg wrote:

> same with my Garmin 10x
>
>
> I get this message in Loadstone 0.68 more frequently with a Royaltec 
> RBT-2000.  I don't know if it has to do with the newer version or my 
> experiments with a QStarz QBT-118.
>
>
> Mike Hanson
>
>
> _______________________________________________
> Loadstone mailing list
> Loadstone at loadstone-gps.com 
> http://www.loadstone-gps.com/mailman/listinfo/loadstone
>
> _______________________________________________
> Loadstone mailing list
> Loadstone at loadstone-gps.com 
> http://www.loadstone-gps.com/mailman/listinfo/loadstone
>



__________ NOD32 2312 (20070606) Information __________

This message was checked by NOD32 antivirus system. http://www.eset.com



More information about the Loadstone mailing list