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" <[email protected]> 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 <[email protected]> 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 > > [email protected] > > To check or change subscription details, visit: > > http://lists.internode.on.net/mailman/listinfo/aus-soaring > > _______________________________________________ > Aus-soaring mailing list > [email protected] > To check or change subscription details, visit: > http://lists.internode.on.net/mailman/listinfo/aus-soaring
_______________________________________________ Aus-soaring mailing list [email protected] To check or change subscription details, visit: http://lists.internode.on.net/mailman/listinfo/aus-soaring
