There is one case on the OLC now where alternate flights from the same
logger show good/bad/good/bad security. Cambridge has requested the
unit be returned for flash replacement. One suggestion is that the
problem may be related to the memory wraparound where old logs are
deleted to make room for a new log. If so, erasing the logger memory
before it fills up may help, but this is speculation and has not been
confirmed. This would be consistent with your experience, though.

Andy wrote:
Doug Haluza wrote:
My 302 was delivered to me with this problem. I put up with it for a
year because my contest logs were still accepted. I then returned the
302 to Cambridge for sealing. Late last year it happened again - 302
display reporting good seal but log showed bad security and was
rejected by OLC. Again I returned it for reseal but only at the end of
season and continued to download my logs. I think they reported
security fail. I used my model 25 for OLC claims and didn't lose any
flights.

I later was very surprised that a review of my 302 logs using Aero
Explorer Plus showed that the security problem only showed on one day
and that subsequent logs were ok. It seems the problem healed itself
and I didn't need to return it. I'll go back and check again if there
is interest in pooling data to fix the problem

I use GlideNav II for download but also tried the CAI pda utility.
Neither gave a good security report for the problem flight.

Andy (GY)