A recent posting by Ian Macphee on the Aus-soaring list says that there
was an older aluminum color case version of the 302, and a newer black
case version. Supposedly the black units don't have the date problem
because they don't use the GPS25. It may just be age of batteries, but
I'm curious if the failures have been following this pattern.

I have a black case unit, just tested as good. Clock had drifted by 8
minutes prior to lock, then corrected itself. Unit probably built 2006
or 2007, battery might have been replaced recently, not sure.

-Dave



On Fri, 05 Dec 2014 02:49:36 +0000, David Kinsell wrote:

On Thu, 04 Dec 2014 18:08:27 -0800, tom wrote:

I wonder if the affected FR manufacturers could add a mod to detect a
timestamp prior to "now" and munge it to the current epoch?

Interesting idea, but quite hypothetical when it comes to Cambridge.

Garrecht Avioncs seems to have source code for the GPS module, and
intends to provide a fix in that code for their Volksloggers. It should
be straightforward to add another 20 years of life that way.

As the details of the problem have come out, it's become clear that the
fix being applied to Cambridge units isn't very good and won't make them
as reliable as they were prior to November. Probably makes more sense
to just go buy a Nano or something similar if you need to replace the
logging capability.

-Dave