From jimr@maia.usno.navy.mil Tue Jul 28 07:50:18 EDT 1998
Received: (from jimr@localhost) by maia.usno.navy.mil (8.8.6 (PHNE_14041)/8.7.3) id HAA16029 for gpst@maia; Tue, 28 Jul 1998 07:49:04 -0400 (EDT)
From: Jim Ray (USNO 202-762-1444) 
Message-Id: <199807281149.HAA16029@maia.usno.navy.mil>
Subject: RE: Clock Resets at USNO (fwd)
To: gpst@maia.usno.navy.mil
Date: Tue, 28 Jul 1998 7:49:03 EDT
X-Mailer: Elm [revision: 212.4]
Status: RO

[This message from Larry Young (JPL) provides insight into the operation
of AOA TurboRogue receivers, which might be generally useful for others
in the IGS/BIPM timing project.  My thanks to Larry for his advice. --Jim]


Forwarded message:

Date: 27 Jul 98 16:42:04 -0700
From: Larry Young 
Subject: RE: Clock Resets at USNO
To: Jim Ray 
Reply-To: Larry Young 

Jim,

Very good results. I'm impressed with the stability/precision of your
time interval counter! 

As a clarification, the TurboRogues are only meant to reset their clocks
if:
1. The clock has drifted off by 0.030 seconds (never happens with good
clocks)
2. The receiver has received a "clock set" command. This occurs if power
is turned off/on, or for some other reason (antenna disconnected?,
glitch?) the receiver has lost enough satellites so that it cannot generate a
position solution for long enough to fall into "open sky mode', where it
assumes it has the wrong position and time. This latter occurance can be
reduced in "clock" mode (found in the nav parameters menu), since in clock mode
only one satellite has to be tracked to generate solutions. You should
also set the RAIM condition to "on-danger" in the same menu.

Good work! I also like your change to more stable antenna cable.

Cheers,
Larry