Hi John,

There is a strong theory that when a single flight log fails, the cause is a
bug in the 302 when the memory gets full and wraps. I am trying to get
Cambridge to fix it. I hope they will.

I'll be documenting the bug and the work-around in my next Cumulus Soaring,
Inc. newsletter. Basically, as long as you clear the memory every now and
then (once per season would be enough for most glider pilots) there is no
way the bug can bite you. The procedure for clearing the 302's memory is
documented he
http://www.cumulus-soaring.com/cai_d...g_Presentation

A friend here in MN recently had a flight log failure that cost him a state
record. He had the logger set to log every second - which made the
potential for the problem 4 times worse that it would be with a 4 second
logging interval. I have since set the interval to 4 seconds and cleared
the memory in his logger (with his permission of course). When the logging
interval is set to 4 seconds the logger has enough memory for 100 hours.

Good Soaring,

Paul Remde
Cumulus Soaring, Inc.
http://www.cumulus-soaring.com

"BB" wrote in message
...
I flew on July 13 producing a normal header
ACAM3H9
HFDTE130708
HFFXA050
HFPLTPILOT: John H. Cochrane
HFGTYGLIDERTYPE:ASW-27B
HFGIDGLIDERID:BB
HFDTM100GPSDATUM:

However, on July 5, I got the dreaded "security fail" -- even though
the security seal (screen 9) shows "good". Yes, rebooted everything,
downloaded over and over again with the cambridge program, tried again
next week -- all to no avail. The 13th downloads normally. If this is
a related bug or others are experiencing the same thng I'd like to
know, especially with nationals only 2 weeks away.

John Cochrane