Page 1 of 7   1 2 3 > 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 January 24, 2010, 6:34 am


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,
Andreas Weller

Posted by Craig Wallace on January 25, 2010, 8:05 pm


On 24/01/2010 11:34, Andreas Weller wrote:
> 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 :-(

My Geko 201 is still working fine, as usual. I've used it a few times in
the last week or so, including for a run today.
I'm using firmware version 2.60.
I've tried setting the language to German, it still all works fine,
including displaying sunset times etc.

--
Craig Wallace
http://craig.neogeo.org.uk
http://www.neogeo.org.uk

Posted by Bernhard Fischer on January 27, 2010, 3:52 pm


Craig Wallace schrieb:
> My Geko 201 is still working fine, as usual. I've used it a few times in
> the last week or so, including for a run today.
> I'm using firmware version 2.60.
> I've tried setting the language to German, it still all works fine,
> including displaying sunset times etc.

The problem with my Geko 201 is the date, not the time. Each track
segment is recorded with a differing date, some are ok and others years
in the past or future. To verify this scroll to the page where you see
the recorded track and select the option "Pan Track Log". Then you can
move back and forth with the Up/Down buttons. Time and date of the
recorded track point is displayed below the map.

Regards,
Bernhard


Posted by Andreas Weller on January 27, 2010, 8:17 pm


Andreas Weller schrieb:
> I sent an e-mail to Garmin (US and EU) but sadly no reply yet :-(

Today I received a reply from Garmin germany:
the bug is non reproducible for them. They admit this error may only
affects few devices. Therefore there's no bug-fix available.

So unfortunately Garmin doesn't recognize responsibility for their
products. They simply shift issues onto customers.
The lesson is clear: if there will be any new Garmin device I can also
pick an US or far east import as Garmin's german support not nearly
justifies the 40% surcharge.


Regards,
Andreas

Posted by Andreas Weller on January 27, 2010, 8:36 pm


> I sent an e-mail to Garmin (US and EU) but sadly no reply yet :-(

Today I received a reply from Garmin germany:
the bug is non reproducible for them. They admit this error may only
affect few devices. Therefore there's no bug-fix available.

Unfortunately Garmin doesn't recognize responsibility for their
products. They simply shift issues onto customers.
The lesson is clear: if I will buy a new Garmin device I can also
pick an US or far east import as Garmin's german support not nearly
justifies the 40% surcharge.


Regards,
Andreas

Page 1 of 7   1 2 3 > last >>