Page 1 of 6   1 2 3 > last >>
Bookmark this page: Add We have an unexpected problem     to Yahoo MyWeb Add We have an unexpected problem     to Google Bookmarks Add We have an unexpected problem     to Windows Live Add We have an unexpected problem     to Del.icio.us Digg We have an unexpected problem    ! Add We have an unexpected problem     to Netscape
  •  
  • Subject
  • Author
  • Date
If you were  Registered and logged in, you could reply and use other advanced thread options
Posted by Sam Wormley on October 17, 2006, 11:47 pm


We have an unexpected problem...

Think back to 21 August 1999 at 0 UTC, the world experienced
its first GPS Week Number Rollover... at the time Trimble was
recommending for the Scoutmaster...

"Trimble recommends that users who wish to navigate during the GPS
week rollover period reset the receiver prior to operation, and plan
on waiting at least 30 minutes before using the system for
navigation. This will give the system time to collect a full, new
almanac and will minimize navigation problems thereafter.

A reset can be accomplished by performing the following actions:
Place the unit on a flat surface.
Turn the unit off.
Press the following 3 keys:
Down Arrow
Up Arrow
Return
Turn the unit on while holding down these 3 keys.
The display should show this message after the copyright message:
Memory wiped
Turn the unit off.

The ScoutMaster may now be used for normal navigation. Allow 30
minutes for almanac collection and satellite acquisition before use."

I found on that fateful night that, by just turning the unit on without
erasing the memory, the Scoutmaster GPS receiver at first tried to search
for the wrong SVs, and eventually started checking for all of them. Once
it found one... it started loading a new almanac which takes a minimum
of 12.5 minutes. I've never has a problem until a few days ago... the
date is reading March of 1987. And I'm not the only one noticing this
problem!

Suggestions and comments are welcome.

-Sam Wormley



Posted by quandong nut on October 18, 2006, 1:52 am



>We have an unexpected problem...
>Think back to 21 August 1999 at 0 UTC, the world experienced
>its first GPS Week Number Rollover... at the time Trimble was
>recommending for the Scoutmaster...
(snip)

>I found on that fateful night that, by just turning the unit on without
>erasing the memory, the Scoutmaster GPS receiver at first tried to search
>for the wrong SVs, and eventually started checking for all of them. Once
>it found one... it started loading a new almanac which takes a minimum
>of 12.5 minutes. I've never has a problem until a few days ago... the
>date is reading March of 1987. And I'm not the only one noticing this
>problem!
>Suggestions and comments are welcome.

Some sort of rollover in the GPSr itself? Or an internal software issue?

Posted by nitespark on October 18, 2006, 3:01 pm




Sam Wormley wrote:

> I found on that fateful night that, by just turning the unit on without
> erasing the memory, the Scoutmaster GPS receiver at first tried to search
> for the wrong SVs, and eventually started checking for all of them. Once
> it found one... it started loading a new almanac which takes a minimum
> of 12.5 minutes. I've never has a problem until a few days ago... the
> date is reading March of 1987. And I'm not the only one noticing this
> problem!
>
> Suggestions and comments are welcome.
>

Sam,
I have a Quest II in the car and it is showing the correct date & time.
Very quick acquisition also.


Posted by Sam Wormley on October 18, 2006, 4:33 pm


nitespark wrote:
>
>
> Sam Wormley wrote:
>
>> I found on that fateful night that, by just turning the unit on without
>> erasing the memory, the Scoutmaster GPS receiver at first tried to search
>> for the wrong SVs, and eventually started checking for all of them. Once
>> it found one... it started loading a new almanac which takes a minimum
>> of 12.5 minutes. I've never has a problem until a few days ago... the
>> date is reading March of 1987. And I'm not the only one noticing this
>> problem!
>> Suggestions and comments are welcome.
>
> Sam,
> I have a Quest II in the car and it is showing the correct date & time.
> Very quick acquisition also.
>

I don't doubt that most GPSRs have the correct date and time... All
my other Trimble receivers do... I'm trying to thing what event in the
last month might have confused the Trimble Scoutmaster's algorithm...
at what might be a solution.


Posted by nitespark on October 18, 2006, 7:20 pm




Sam Wormley wrote:
> nitespark wrote:
>
>> Sam Wormley wrote:
>>> I found on that fateful night that, by just turning the unit on without
>>> erasing the memory, the Scoutmaster GPS receiver at first tried to
>>> search
>>> for the wrong SVs, and eventually started checking for all of them. Once
>>> it found one... it started loading a new almanac which takes a minimum
>>> of 12.5 minutes. I've never has a problem until a few days ago... the
>>> date is reading March of 1987. And I'm not the only one noticing this
>>> problem!
>>> Suggestions and comments are welcome.
>> Sam,
>> I have a Quest II in the car and it is showing the correct date &
>> time. Very quick acquisition also.
>
> I don't doubt that most GPSRs have the correct date and time... All
> my other Trimble receivers do... I'm trying to thing what event in the
> last month might have confused the Trimble Scoutmaster's algorithm...
> at what might be a solution.
>

FWIW, I got my trusty Garmin GPS V out and dusted it off. Been awhile
since I turned it on and it seem as through it took a bit longer to
acquire, once it did, the clock and date were right on. Your message
piqued my curiosity. It would seem there is some anomaly specific to
your Trimble.


Page 1 of 6   1 2 3 > last >>