On Dec 8, 5:40*am, Andy wrote:
On Dec 7, 5:34*pm, Darryl Ramm wrote:

Cambridge is still working on this AFAIK

Who would that be? *I thought everyone at Cambridge involved with
software and hardware development had moved on. * I hope that'd not
true but I know that most of the people I have ever had contact with
are gone.

I have never erased my 302 and it has recorded well over 500 hours at
2 second interval. *I have experienced the security fail problem I
think twice. *It's interesting that a security fail on one flight will
not usually give a security fail on the next or subsequent flights.
Sending it back is probably a waste of money unless you need a
calibration. * If the log memory was full for the one with security
fail it was still full for the subsequent flights.

Since Cambridge had a date/time math error in the utility code I
wonder if there is a date/time problem in the 302. *Anyone willing to
post the start/end dates/times of any 302 logs with security fail?

Andy

There are different symptoms and probably different causes. The
security fails I have experienced do not go away if you retry or use
different download tools and all subsequent flight will fail. As I
noted on my blog but should have said inline, if you see a bad seal
message on the device that is a different problem - a real bad seal
that needs to be fixed.

There was no obvious date/time problem on failed logs. An example
flight with such a security fail is here
http://www.onlinecontest.org/olc-2.0...htId=482183925

So again if I saw a fail like this I would definitly take the
precaution of erasing the log memory before the next flight.

Darryl