Re: [Aus-soaring] date problem - older loggers

[Mike Borgelt]

At 11:02 AM 1/12/2014, you wrote:
you know guys, I understand all of the update now etc and perhaps we 
have to do so because of the interconnection of all things now with 
satellites internet etc etc but I still have a more than 30 year old 
transisior radio (AmFm, swtichable between 9 hz and 10 hz spacing) 
that I have taken all around the world over the last 30 years! 6 
inches by 1.5 by 3.5. It still works and i still use it   -   cant 
see why I wont be using it in another 20 years. I really hate this 
age of consumerism. and the above is of course irrelevant. ron





"all change is bad" Dr Sheldon Cooper  - The Big Bang Theory.



Mike




Borgelt Instruments - design & manufacture of quality soaring 
instrumentation since 1978

www.borgeltinstruments.com
tel:   07 4635 5784 overseas: int+61-7-4635 5784
mob: 042835 5784:  int+61-42835 5784
P O Box 4607, Toowoomba East, QLD 4350, Australia  ___
Aus-soaring mailing list
Aus-soaring@lists.internode.on.net
To check or change subscription details, visit:
http://lists.internode.on.net/mailman/listinfo/aus-soaring

Re: [Aus-soaring] date problem - older loggers ~ A New Panel suggested!

[Mike Borgelt]

What I would really like in one 58 mm hole is a new 'Smart'  vario that has
a NETTO option and outputs to a USB plug:  5 volts, NMEA data for airspeed
[yes airspeed]  into the Nexus7  [with a plug to integrate  FLARM ].  Anyone
got one?



 Just use a B600/B800. It has netto (or relative). We'll supply an 
adapter cable for a Firefly (good name!) serial to Bluetooth device 
and you can send that data to the Nexus 7 by BT.


Of course if the you want  a REAL netto you'll need the Dynamis 
module for the B600/B800 (available in new year). The netto there 
doesn't care about bugs on the wings or if you are under power even, 
as it effectively measures the polar in real time. Also wind vector 
smoothly and continuously in real time. New pilot interface coming 
too as an add on.



Agreed on the compass in gliders. Only time I ever looked at one in a 
glider was in the early days of GPS when it was amazing to see that 
the turnpoint over the nose was in fact on the bearing indicated by 
the GPS (or near enough). Never before or since. In the power plane 
it could be used to hang a pair of fluffy dice as it is high on the 
windscreen center pillar. That is its only use near as I can tell as 
we have 4 GPS units when we fly plus pilotage.


Mike






I don't want to muck around with IOIO and would be happy to have the FLARM
[audio and indicator] directly into the NEXUS 7 [or NEXUS 7 2017 update when
it is released].

Alan Wilson
Canberra.

PS. Then my simple instrument panel would look like: NEXUS 7, 'Smart' Vario
[or 2] on top, ASI, Altimeter below,  radio, with a FLARM box behind the
panel somewhere.   And do we really need a compass on manufacturers 'minimum
equipment' lists: it is almost 2015!

Tin Hat on...

http://www.onlinecontest.org/olc-2.0/gliding/flightbook.html?sp=2015&st=olcp
&rt=olc&pi=22975 and most of my logs since 2006 are from car GPS.  Logs from
an SNAV are often rejected!



-Original Message-
From: aus-soaring-boun...@lists.internode.on.net
[mailto:aus-soaring-boun...@lists.internode.on.net] On Behalf Of Ron Sanders
Sent: Monday, 01 December, 2014 1:17 AM
To: Discussion of issues relating to Soaring in Australia.
Subject: Re: [Aus-soaring] date problem - older loggers

Regards how widespread this is Pam i do not know but i have two volksloggers
that tell me it is 1995.

ron S

On 29 November 2014 at 16:11, pam  wrote:
> Please be aware that some older Flight Recorders have a problem with
> the DATE - they think it is 1995.
>
> This is coming from the older Garmin engines in some FRs- so far
> Cambridge 20, 25, older 302s, Volksloggers, Zander models have been
identified.
>
> Ask the agent for your FR if they can fix the problem.
>
> Ian Macphee can fix Cambridge untis - call him.
>
> Here is something from a recent thread on Aus-Soaring:
>
> Ian Mc Phee Tue, 11 Nov 2014 12:49:51 -0800
>
> All the model 20 Cambridge camera box loggers have this garmin gps 25
>
> engine as well as early aluminium case 302 vario (not the newer black
> case
>
> ones).  Many now are displaying this March 1995 date yet are still
>
> acquiring satellites & navigating which I find strange.
>
>
>
> At this stage I am replacing 302s with a garmin GPS15 engine which is
>
> smaller but with adapter fits.
>
>
>
> I can replace the GPS25 battery and then reset the clock (adding UTC
> time
>
> and lat and long approx & maybe they will kick start again) but is a
> real
>
> pain.
>
>
>
> Anyhow if you have a Cambridge mod 20 or non black case 302 then check
> date
>
> and if 1995 you WILL have issues.
>
>
>
> I ask the question how many electronic items do you have 20 years old?
> Not
>
> many I suspect. The model 10 brick box is over 20 yrs old and most
> model 20
>
> loggers are over 15 years old.
>
>
>
> So maybe upgrade time is coming and remember all vario makers have
> made
>
> significant improvements in varios over the years.
>
>
>
> Ian Mcphee
>
>>>
>
>>>
>
> You will need to send the Volkslogger to some-one who can reset the
> memory
>
> inside the GPS and at the same time replace the internal battery or
> upgrade
>
> to a new logger.
>
> See post from several years ago from on Aus-Soaring.
>
>
>
> I found this post which indicates that the engine is a Garmin GPS25.
>
> Just to wrap things up, this problem has beep traced to the Garmin GPS
>
> Engine. The GPS25 engine has a battery which maintains some memory and
>
> also runs the Real Time Clock when the device is not in use,
> recharging
>
> during normal operation.
>
>
>
> When the GPS25 battery is low (which happens more often the older the
>
> logger is), memory in the GPS 

Re: [Aus-soaring] date problem - older loggers

[Ron Sanders]

you know guys, I understand all of the update now etc and perhaps we
have to do so because of the interconnection of all things now with
satellites internet etc etc but I still have a more than 30 year old
transisior radio (AmFm, swtichable between 9 hz and 10 hz spacing)
that I have taken all around the world over the last 30 years! 6
inches by 1.5 by 3.5. It still works and i still use it   -   cant see
why I wont be using it in another 20 years.

I really hate this age of consumerism.

and the above is of course irrelevant.

ron

On 1 December 2014 at 05:40, Tim Shirley  wrote:
> Hi all,
>
> Although typically this can be resolved by replacement of the internal
> battery (and then keeping it charged), the reality is that this will be an
> ongoing and random problem - because the failure occurs after the internal
> battery fails or is allowed to run flat.
>
> It is possible that the IGC Sporting Code will be amended to allow this date
> change to be accepted for some levels of validation, though I doubt it would
> be changed sufficiently to allow the validation of a record claim, and
> changes do take some time.
>
> However, the bottom line is that it is really time to consider an upgrade.
> I don't think anyone can expect an item of electronic equipment to last for
> ever, and these have lasted far longer than most.
>
> Cheers
>
> Tim Shirley
>
> tra dire é fare c' é mezzo il mare
>
> On 1/12/2014 1:17 AM, Ron Sanders wrote:
>
> Regards how widespread this is Pam i do not know but i have two
> volksloggers that tell me it is 1995.
>
> ron S
>
> On 29 November 2014 at 16:11, pam  wrote:
>
> Please be aware that some older Flight Recorders have a problem with the
> DATE – they think it is 1995.
>
> This is coming from the older Garmin engines in some FRs- so far Cambridge
> 20, 25, older 302s, Volksloggers, Zander models have been identified.
>
> Ask the agent for your FR if they can fix the problem.
>
> Ian Macphee can fix Cambridge untis – call him.
>
> Here is something from a recent thread on Aus-Soaring:
>
> Ian Mc Phee Tue, 11 Nov 2014 12:49:51 -0800
>
> All the model 20 Cambridge camera box loggers have this garmin gps 25
>
> engine as well as early aluminium case 302 vario (not the newer black case
>
> ones).  Many now are displaying this March 1995 date yet are still
>
> acquiring satellites & navigating which I find strange.
>
>
>
> At this stage I am replacing 302s with a garmin GPS15 engine which is
>
> smaller but with adapter fits.
>
>
>
> I can replace the GPS25 battery and then reset the clock (adding UTC time
>
> and lat and long approx & maybe they will kick start again) but is a real
>
> pain.
>
>
>
> Anyhow if you have a Cambridge mod 20 or non black case 302 then check date
>
> and if 1995 you WILL have issues.
>
>
>
> I ask the question how many electronic items do you have 20 years old? Not
>
> many I suspect. The model 10 brick box is over 20 yrs old and most model 20
>
> loggers are over 15 years old.
>
>
>
> So maybe upgrade time is coming and remember all vario makers have made
>
> significant improvements in varios over the years.
>
>
>
> Ian Mcphee
>
> You will need to send the Volkslogger to some-one who can reset the memory
>
> inside the GPS and at the same time replace the internal battery or upgrade
>
> to a new logger.
>
> See post from several years ago from on Aus-Soaring.
>
>
>
> I found this post which indicates that the engine is a Garmin GPS25.
>
> Just to wrap things up, this problem has beep traced to the Garmin GPS
>
> Engine. The GPS25 engine has a battery which maintains some memory and
>
> also runs the Real Time Clock when the device is not in use, recharging
>
> during normal operation.
>
>
>
> When the GPS25 battery is low (which happens more often the older the
>
> logger is), memory in the GPS engine sometimes gets partially corrupted,
>
> in a way that the GPS is not able to detect.
>
>
>
> Therefore, the GPS thinks it is 1,024 weeks (about 19.6 years) before
>
> present date.
>
>
>
> The solution is to replace the GPS battery (in order to reduce the
>
> probability of a re-occurrence), and reset the memory inside the GPS so
>
> that it knows in which 19.6 year epoch it is. This is not something the
>
> user can do.
>
>
>
> It has nothing to do with the Volkslogger Internal Battery, but it is
>
> perhaps worth thinking about taking the opportunity of replacing it
>
> during the repair.
>
>
>
> Sounds like the GPS date rollover problem affecting older GPS units, where
>
> the date wraps around every 1024 weeks.  Here, 8 Nov 2014 minus 1024 weeks
>
> is 25 March 1995.  The problem should have first appeared on 21 August 1999.
>
> See http://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs
>
>
>
>
> ___
> Aus-soaring mailing list
> Aus-soaring@lists.internode.on.net
> To check or change subscription details, visit:
> http://lists.internode.on.net/mailman/listinfo/aus-soaring
>
> 

Re: [Aus-soaring] date problem - older loggers ~ A New Panel suggested!

[Alan Wilson]

I have to agree with Ian Mc Phee's  comment below: " I ask the question how
many electronic items do you have 20 years old?  Not  many I suspect. The
model 10 brick box is over 20 yrs old and most  model 20
 loggers are over 15 years old."   And the associated boxes require perhaps
3 @ 78 mm holes of valuable instrument panel space.  

Software and systems have made HUGE leaps since 1995.  A cockpit with a good
vario and a cheap PDA with XCSoar is a really effective arrangement. A $200
Nexus stand alone installation at $200 [JBHifi] does heaps more and much
more simply and meets most competition requirements. A $50 car GPS from Aldi
is good and easy to adapt.Just bin systems that are more than 10 years
old and your life will be much simpler!  [of course the suck/blow ASI
and altimeter is retained].  Hard to see in sunlight, yes, but all I really
want is a Green up arrow on the LHS and I can see that.  All the other hard
to see numbers can be deciphered occasionally.

[If you really think you can beat a world record you will need to spend $$$
on certifications]

It is time for greater instrument panel integration.

What I would really like in one 58 mm hole is a new 'Smart'  vario that has
a NETTO option and outputs to a USB plug:  5 volts, NMEA data for airspeed
[yes airspeed]  into the Nexus7  [with a plug to integrate  FLARM ].  Anyone
got one? 

I don't want to muck around with IOIO and would be happy to have the FLARM
[audio and indicator] directly into the NEXUS 7 [or NEXUS 7 2017 update when
it is released].

Alan Wilson
Canberra.

PS. Then my simple instrument panel would look like: NEXUS 7, 'Smart' Vario
[or 2] on top, ASI, Altimeter below,  radio, with a FLARM box behind the
panel somewhere.   And do we really need a compass on manufacturers 'minimum
equipment' lists: it is almost 2015!

Tin Hat on...

http://www.onlinecontest.org/olc-2.0/gliding/flightbook.html?sp=2015&st=olcp
&rt=olc&pi=22975 and most of my logs since 2006 are from car GPS.  Logs from
an SNAV are often rejected!



-Original Message-
From: aus-soaring-boun...@lists.internode.on.net
[mailto:aus-soaring-boun...@lists.internode.on.net] On Behalf Of Ron Sanders
Sent: Monday, 01 December, 2014 1:17 AM
To: Discussion of issues relating to Soaring in Australia.
Subject: Re: [Aus-soaring] date problem - older loggers

Regards how widespread this is Pam i do not know but i have two volksloggers
that tell me it is 1995.

ron S

On 29 November 2014 at 16:11, pam  wrote:
> Please be aware that some older Flight Recorders have a problem with 
> the DATE - they think it is 1995.
>
> This is coming from the older Garmin engines in some FRs- so far 
> Cambridge 20, 25, older 302s, Volksloggers, Zander models have been
identified.
>
> Ask the agent for your FR if they can fix the problem.
>
> Ian Macphee can fix Cambridge untis - call him.
>
> Here is something from a recent thread on Aus-Soaring:
>
> Ian Mc Phee Tue, 11 Nov 2014 12:49:51 -0800
>
> All the model 20 Cambridge camera box loggers have this garmin gps 25
>
> engine as well as early aluminium case 302 vario (not the newer black 
> case
>
> ones).  Many now are displaying this March 1995 date yet are still
>
> acquiring satellites & navigating which I find strange.
>
>
>
> At this stage I am replacing 302s with a garmin GPS15 engine which is
>
> smaller but with adapter fits.
>
>
>
> I can replace the GPS25 battery and then reset the clock (adding UTC 
> time
>
> and lat and long approx & maybe they will kick start again) but is a 
> real
>
> pain.
>
>
>
> Anyhow if you have a Cambridge mod 20 or non black case 302 then check 
> date
>
> and if 1995 you WILL have issues.
>
>
>
> I ask the question how many electronic items do you have 20 years old? 
> Not
>
> many I suspect. The model 10 brick box is over 20 yrs old and most 
> model 20
>
> loggers are over 15 years old.
>
>
>
> So maybe upgrade time is coming and remember all vario makers have 
> made
>
> significant improvements in varios over the years.
>
>
>
> Ian Mcphee
>
>>>
>
>>>
>
> You will need to send the Volkslogger to some-one who can reset the 
> memory
>
> inside the GPS and at the same time replace the internal battery or 
> upgrade
>
> to a new logger.
>
> See post from several years ago from on Aus-Soaring.
>
>
>
> I found this post which indicates that the engine is a Garmin GPS25.
>
> Just to wrap things up, this problem has beep traced to the Garmin GPS
>
> Engine. The GPS25 engine has a battery which maintains some memory and
>
> also runs the Real Time Clock when the device is not in use, 
> recharging
>
> during normal operation.
>

Re: [Aus-soaring] date problem - older loggers

[Tim Shirley]

Hi all,

Although typically this can be resolved by replacement of the internal 
battery (and then keeping it charged), the reality is that this will be 
an ongoing and random problem - because the failure occurs after the 
internal battery fails or is allowed to run flat.


It is possible that the IGC Sporting Code will be amended to allow this 
date change to be accepted for some levels of validation, though I doubt 
it would be changed sufficiently to allow the validation of a record 
claim, and changes do take some time.


However, the bottom line is that it is really time to consider an 
upgrade.  I don't think anyone can expect an item of electronic 
equipment to last for ever, and these have lasted far longer than most.


Cheers

/Tim Shirley/

/tra dire é fare c' é mezzo il mare/

On 1/12/2014 1:17 AM, Ron Sanders wrote:

Regards how widespread this is Pam i do not know but i have two
volksloggers that tell me it is 1995.

ron S

On 29 November 2014 at 16:11, pam  wrote:

Please be aware that some older Flight Recorders have a problem with the
DATE – they think it is 1995.

This is coming from the older Garmin engines in some FRs- so far Cambridge
20, 25, older 302s, Volksloggers, Zander models have been identified.

Ask the agent for your FR if they can fix the problem.

Ian Macphee can fix Cambridge untis – call him.

Here is something from a recent thread on Aus-Soaring:

Ian Mc Phee Tue, 11 Nov 2014 12:49:51 -0800

All the model 20 Cambridge camera box loggers have this garmin gps 25

engine as well as early aluminium case 302 vario (not the newer black case

ones).  Many now are displaying this March 1995 date yet are still

acquiring satellites & navigating which I find strange.



At this stage I am replacing 302s with a garmin GPS15 engine which is

smaller but with adapter fits.



I can replace the GPS25 battery and then reset the clock (adding UTC time

and lat and long approx & maybe they will kick start again) but is a real

pain.



Anyhow if you have a Cambridge mod 20 or non black case 302 then check date

and if 1995 you WILL have issues.



I ask the question how many electronic items do you have 20 years old? Not

many I suspect. The model 10 brick box is over 20 yrs old and most model 20

loggers are over 15 years old.



So maybe upgrade time is coming and remember all vario makers have made

significant improvements in varios over the years.



Ian Mcphee

You will need to send the Volkslogger to some-one who can reset the memory

inside the GPS and at the same time replace the internal battery or upgrade

to a new logger.

See post from several years ago from on Aus-Soaring.



I found this post which indicates that the engine is a Garmin GPS25.

Just to wrap things up, this problem has beep traced to the Garmin GPS

Engine. The GPS25 engine has a battery which maintains some memory and

also runs the Real Time Clock when the device is not in use, recharging

during normal operation.



When the GPS25 battery is low (which happens more often the older the

logger is), memory in the GPS engine sometimes gets partially corrupted,

in a way that the GPS is not able to detect.



Therefore, the GPS thinks it is 1,024 weeks (about 19.6 years) before

present date.



The solution is to replace the GPS battery (in order to reduce the

probability of a re-occurrence), and reset the memory inside the GPS so

that it knows in which 19.6 year epoch it is. This is not something the

user can do.



It has nothing to do with the Volkslogger Internal Battery, but it is

perhaps worth thinking about taking the opportunity of replacing it

during the repair.



Sounds like the GPS date rollover problem affecting older GPS units, where

the date wraps around every 1024 weeks.  Here, 8 Nov 2014 minus 1024 weeks

is 25 March 1995.  The problem should have first appeared on 21 August 1999.

See http://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs




___
Aus-soaring mailing list
Aus-soaring@lists.internode.on.net
To check or change subscription details, visit:
http://lists.internode.on.net/mailman/listinfo/aus-soaring

___
Aus-soaring mailing list
Aus-soaring@lists.internode.on.net
To check or change subscription details, visit:
http://lists.internode.on.net/mailman/listinfo/aus-soaring


___
Aus-soaring mailing list
Aus-soaring@lists.internode.on.net
To check or change subscription details, visit:
http://lists.internode.on.net/mailman/listinfo/aus-soaring

Re: [Aus-soaring] date problem - older loggers

[Ian Mc Phee]

Ron very widespread and 100% with Garmin GPS 25 engines I believe.

I think it is time tp upgrade to something more modern like a Nano however
eventually Cambridge 20 camera logger & early 302 s will get sorted out.  I
am awaiting 8 batteries I found in Australia & rest from DigiKey in USA
plus new Garmin GPS15xL engines from USA set to work in Cambridge 302s (not
just off the shelf unfortunately)

I have Cambridge sr no 001 model 10 brick logger (worlds first ever logger)
and eventually I will get it going again.

As a suggestion to official observers (please confirm) I say write down
time and date in the recorder and the actual UTC time and date before
flight and in intrium send a statement in with badge claim and just maybe
the claims officer will be kind in view of circumstances.  The date is
slowly moving forward from march 1995.  This will not apply to records I
assume.

This is a GARMIN issue (not Cambridge or Voltslogger) that knowbody knew
about it till recently.

For those that know him Klaus Keim in Germany has researched  the Garmin 25
issue and started refitting internal batteries a few years ago. Klaus was
in South Africa for many years and has made him very resourceful and
discards nothing.

Hope this explains.

Ian Mcphee
On 01/12/2014 1:18 AM, "Ron Sanders"  wrote:

> Regards how widespread this is Pam i do not know but i have two
> volksloggers that tell me it is 1995.
>
> ron S
>
> On 29 November 2014 at 16:11, pam  wrote:
> > Please be aware that some older Flight Recorders have a problem with the
> > DATE – they think it is 1995.
> >
> > This is coming from the older Garmin engines in some FRs- so far
> Cambridge
> > 20, 25, older 302s, Volksloggers, Zander models have been identified.
> >
> > Ask the agent for your FR if they can fix the problem.
> >
> > Ian Macphee can fix Cambridge untis – call him.
> >
> > Here is something from a recent thread on Aus-Soaring:
> >
> > Ian Mc Phee Tue, 11 Nov 2014 12:49:51 -0800
> >
> > All the model 20 Cambridge camera box loggers have this garmin gps 25
> >
> > engine as well as early aluminium case 302 vario (not the newer black
> case
> >
> > ones).  Many now are displaying this March 1995 date yet are still
> >
> > acquiring satellites & navigating which I find strange.
> >
> >
> >
> > At this stage I am replacing 302s with a garmin GPS15 engine which is
> >
> > smaller but with adapter fits.
> >
> >
> >
> > I can replace the GPS25 battery and then reset the clock (adding UTC time
> >
> > and lat and long approx & maybe they will kick start again) but is a real
> >
> > pain.
> >
> >
> >
> > Anyhow if you have a Cambridge mod 20 or non black case 302 then check
> date
> >
> > and if 1995 you WILL have issues.
> >
> >
> >
> > I ask the question how many electronic items do you have 20 years old?
> Not
> >
> > many I suspect. The model 10 brick box is over 20 yrs old and most model
> 20
> >
> > loggers are over 15 years old.
> >
> >
> >
> > So maybe upgrade time is coming and remember all vario makers have made
> >
> > significant improvements in varios over the years.
> >
> >
> >
> > Ian Mcphee
> >
> >>>
> >
> >>>
> >
> > You will need to send the Volkslogger to some-one who can reset the
> memory
> >
> > inside the GPS and at the same time replace the internal battery or
> upgrade
> >
> > to a new logger.
> >
> > See post from several years ago from on Aus-Soaring.
> >
> >
> >
> > I found this post which indicates that the engine is a Garmin GPS25.
> >
> > Just to wrap things up, this problem has beep traced to the Garmin GPS
> >
> > Engine. The GPS25 engine has a battery which maintains some memory and
> >
> > also runs the Real Time Clock when the device is not in use, recharging
> >
> > during normal operation.
> >
> >
> >
> > When the GPS25 battery is low (which happens more often the older the
> >
> > logger is), memory in the GPS engine sometimes gets partially corrupted,
> >
> > in a way that the GPS is not able to detect.
> >
> >
> >
> > Therefore, the GPS thinks it is 1,024 weeks (about 19.6 years) before
> >
> > present date.
> >
> >
> >
> > The solution is to replace the GPS battery (in order to reduce the
> >
> > probability of a re-occurrence), and reset the memory inside the GPS so
> >
> > that it knows in which 19.6 year epoch it is. This is not something the
> >
> > user can do.
> >
> >
> >
> > It has nothing to do with the Volkslogger Internal Battery, but it is
> >
> > perhaps worth thinking about taking the opportunity of replacing it
> >
> > during the repair.
> >
> >
> >
> > Sounds like the GPS date rollover problem affecting older GPS units,
> where
> >
> > the date wraps around every 1024 weeks.  Here, 8 Nov 2014 minus 1024
> weeks
> >
> > is 25 March 1995.  The problem should have first appeared on 21 August
> 1999.
> >
> > See http://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs
> >
> >
> >
> >
> > ___
> > Aus-soaring mailing list
> > Aus-soaring@lists.internode.on.net

Re: [Aus-soaring] date problem - older loggers

[Ron Sanders]

Regards how widespread this is Pam i do not know but i have two
volksloggers that tell me it is 1995.

ron S

On 29 November 2014 at 16:11, pam  wrote:
> Please be aware that some older Flight Recorders have a problem with the
> DATE – they think it is 1995.
>
> This is coming from the older Garmin engines in some FRs- so far Cambridge
> 20, 25, older 302s, Volksloggers, Zander models have been identified.
>
> Ask the agent for your FR if they can fix the problem.
>
> Ian Macphee can fix Cambridge untis – call him.
>
> Here is something from a recent thread on Aus-Soaring:
>
> Ian Mc Phee Tue, 11 Nov 2014 12:49:51 -0800
>
> All the model 20 Cambridge camera box loggers have this garmin gps 25
>
> engine as well as early aluminium case 302 vario (not the newer black case
>
> ones).  Many now are displaying this March 1995 date yet are still
>
> acquiring satellites & navigating which I find strange.
>
>
>
> At this stage I am replacing 302s with a garmin GPS15 engine which is
>
> smaller but with adapter fits.
>
>
>
> I can replace the GPS25 battery and then reset the clock (adding UTC time
>
> and lat and long approx & maybe they will kick start again) but is a real
>
> pain.
>
>
>
> Anyhow if you have a Cambridge mod 20 or non black case 302 then check date
>
> and if 1995 you WILL have issues.
>
>
>
> I ask the question how many electronic items do you have 20 years old? Not
>
> many I suspect. The model 10 brick box is over 20 yrs old and most model 20
>
> loggers are over 15 years old.
>
>
>
> So maybe upgrade time is coming and remember all vario makers have made
>
> significant improvements in varios over the years.
>
>
>
> Ian Mcphee
>
>>>
>
>>>
>
> You will need to send the Volkslogger to some-one who can reset the memory
>
> inside the GPS and at the same time replace the internal battery or upgrade
>
> to a new logger.
>
> See post from several years ago from on Aus-Soaring.
>
>
>
> I found this post which indicates that the engine is a Garmin GPS25.
>
> Just to wrap things up, this problem has beep traced to the Garmin GPS
>
> Engine. The GPS25 engine has a battery which maintains some memory and
>
> also runs the Real Time Clock when the device is not in use, recharging
>
> during normal operation.
>
>
>
> When the GPS25 battery is low (which happens more often the older the
>
> logger is), memory in the GPS engine sometimes gets partially corrupted,
>
> in a way that the GPS is not able to detect.
>
>
>
> Therefore, the GPS thinks it is 1,024 weeks (about 19.6 years) before
>
> present date.
>
>
>
> The solution is to replace the GPS battery (in order to reduce the
>
> probability of a re-occurrence), and reset the memory inside the GPS so
>
> that it knows in which 19.6 year epoch it is. This is not something the
>
> user can do.
>
>
>
> It has nothing to do with the Volkslogger Internal Battery, but it is
>
> perhaps worth thinking about taking the opportunity of replacing it
>
> during the repair.
>
>
>
> Sounds like the GPS date rollover problem affecting older GPS units, where
>
> the date wraps around every 1024 weeks.  Here, 8 Nov 2014 minus 1024 weeks
>
> is 25 March 1995.  The problem should have first appeared on 21 August 1999.
>
> See http://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs
>
>
>
>
> ___
> Aus-soaring mailing list
> Aus-soaring@lists.internode.on.net
> To check or change subscription details, visit:
> http://lists.internode.on.net/mailman/listinfo/aus-soaring

___
Aus-soaring mailing list
Aus-soaring@lists.internode.on.net
To check or change subscription details, visit:
http://lists.internode.on.net/mailman/listinfo/aus-soaring

[Aus-soaring] date problem - older loggers

[pam]

Please be aware that some older Flight Recorders have a problem with the
DATE - they think it is 1995.

This is coming from the older Garmin engines in some FRs- so far Cambridge
20, 25, older 302s, Volksloggers, Zander models have been identified.

Ask the agent for your FR if they can fix the problem.

Ian Macphee can fix Cambridge untis - call him.

Here is something from a recent thread on Aus-Soaring:

Ian Mc Phee
  Tue, 11 Nov 2014 12:49:51 -0800
  

All the model 20 Cambridge camera box loggers have this garmin gps 25
engine as well as early aluminium case 302 vario (not the newer black case
ones).  Many now are displaying this March 1995 date yet are still
acquiring satellites & navigating which I find strange.
 
At this stage I am replacing 302s with a garmin GPS15 engine which is
smaller but with adapter fits.
 
I can replace the GPS25 battery and then reset the clock (adding UTC time
and lat and long approx & maybe they will kick start again) but is a real
pain.
 
Anyhow if you have a Cambridge mod 20 or non black case 302 then check date
and if 1995 you WILL have issues.
 
I ask the question how many electronic items do you have 20 years old? Not
many I suspect. The model 10 brick box is over 20 yrs old and most model 20
loggers are over 15 years old.
 
So maybe upgrade time is coming and remember all vario makers have made
significant improvements in varios over the years.
 
Ian Mcphee

>> 

>> 

You will need to send the Volkslogger to some-one who can reset the memory

inside the GPS and at the same time replace the internal battery or upgrade

to a new logger.

See post from several years ago from on Aus-Soaring.

 

I found this post which indicates that the engine is a Garmin GPS25.

Just to wrap things up, this problem has beep traced to the Garmin GPS

Engine. The GPS25 engine has a battery which maintains some memory and

also runs the Real Time Clock when the device is not in use, recharging

during normal operation.

 

When the GPS25 battery is low (which happens more often the older the

logger is), memory in the GPS engine sometimes gets partially corrupted,

in a way that the GPS is not able to detect.

 

Therefore, the GPS thinks it is 1,024 weeks (about 19.6 years) before

present date.

 

The solution is to replace the GPS battery (in order to reduce the

probability of a re-occurrence), and reset the memory inside the GPS so

that it knows in which 19.6 year epoch it is. This is not something the

user can do.

 

It has nothing to do with the Volkslogger Internal Battery, but it is

perhaps worth thinking about taking the opportunity of replacing it

during the repair.

 

Sounds like the GPS date rollover problem affecting older GPS units, where
the date wraps around every 1024 weeks.  Here, 8 Nov 2014 minus 1024 weeks
is 25 March 1995.  The problem should have first appeared on 21 August 1999.

See http://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs

 

___
Aus-soaring mailing list
Aus-soaring@lists.internode.on.net
To check or change subscription details, visit:
http://lists.internode.on.net/mailman/listinfo/aus-soaring