Page 6 of 7   < 4 5 6 > last >>
Bookmark this page: Add Y2K 10 Bug with Geko 201 to Yahoo MyWeb Add Y2K 10 Bug with Geko 201 to Google Bookmarks Add Y2K 10 Bug with Geko 201 to Windows Live Add Y2K 10 Bug with Geko 201 to Del.icio.us Digg Y2K 10 Bug with Geko 201! Add Y2K 10 Bug with Geko 201 to Netscape
  •  
  • Subject
  • Author
  • Date
If you were  Registered and logged in, you could reply and use other advanced thread options
Posted by Andreas Weller on February 9, 2010, 6:25 pm


On 09.02.2010 14:19, Rick Richardson wrote:
> the date is calculated wrong. But making it even worse, almanac data
> is also lost.

I just hooked my Geko to gpsd using the serial interface and NMEA
output. It even delivers wrong NMEA data...

xgps screenshot: http://www.andreas-weller.de/usenet/Geko201-NMEA-output.png


Regards,
Andreas Weller

Posted by Andreas Weller on February 9, 2010, 3:06 pm


On 08.02.2010 13:12, rene wrote:
> Same prob over here (Belgium) with my geko 201 .

Please contact your local support (00 32 2672 5254) and let us know
their answer or if they have any solution for this issue.


Regards,
Andreas Weller

Posted by Diogenes on March 17, 2010, 2:20 pm


> Hi.
> There seems to be a year 2010 bug with my Garmin Geko 201.
> When switching it on date and time are calculated wrong. But making it
> even worse almanac data is also lost. So it needs to search for all
> satellites whenever it is turned on. Indeed the whole celestial
> mechanics is wrong: trying to display sunset results in a hung up geko -
> I needed to remove the batteries to switch it off.
> First I thought this problems might be caused by a broken buffer
> battery. But I tried it using two Geko 201 with different firmware
> versions. The problem is repeatable with both devices.
> On the Garmin web-page there's nothing about this - no FAQ entry, no
> Firmware update...
> Would you please check whether your Garmin is also affected? May be only
> the german firmware is affected. Or it's a fundamental problem with the
> phasetrac12 chipset used in this series of GPS devices.
> I sent an e-mail to Garmin (US and EU) but sadly no reply yet :-(
> Regards,
> =A0 Andreas Weller


Sad to see that a month after Garmin has recognized this issue (which
also affects my device) and a solution/firmware update has been
announced, nothing of that has happened. I mean, of course these
things are /old/, as in really, really old, and I understand any
engineer who has developed anything for this device is now retired or
working for Google, and any engineer currently in their employment
must at first dig his way through the docs, and I understand if they
prefer hoping for the problem to simply go away.

On the other hand we are talking a substantial number of sets that
were in perfect working order, and have absolutely satisfied their
various owners, who have therefore functioned as multipliers for years
recommending the name Garmin to anyone asking their advice (at least
the same is true in my case). So if I was them, I'd put a little
effort into keeping it that way.

Posted by Rick Richardson on March 17, 2010, 4:10 pm


Date: Wed, 17 Mar 2010 11:24:14 -0500
To: Rick Richardson
Subject: RE: Geko 201

Hello,

I just asked about this problem this morning. As of right now, we
still do not
have a fix for it. We are still working on it.

Best Regards,

Damon Aldridge
Outdoor/Fitness Support

Garmin International
1200 E 151st St
Olathe, KS 66062

Posted by Diogenes on March 17, 2010, 4:21 pm


> Date: Wed, 17 Mar 2010 11:24:14 -0500
> To: Rick Richardson
> Subject: RE: Geko 201
> Hello,
> I just asked about this problem this morning. =A0As of right now, we
> still do not
> have a fix for it. =A0We are still working on it.
> Best Regards,
> Damon Aldridge
> Outdoor/Fitness Support
> Garmin International
> 1200 E 151st St
> Olathe, KS =A066062

Damon,

thanks for the prompt update. Obviously not what we hoped for, but
good to hear we are still on your radar!

Thomas

Page 6 of 7   < 4 5 6 > last >>
Related Posts
  • Subject
  • Posted In
  • Date