Doug,

It's like you guys only have one excuse, the file is corrupt. And you
stick with that excuse despite the fact the file passes all security
checks. If the file really

The default security check run by the 3UT15256.exe download utility
displays:

Log Data Integrity OK
Signature Data Integrity OK
Security OK

The Valicam2.exe displays:

Log Data Integrity OK
Signature Data Integrity OK
Security OK

Page 10 on the 302, shows 'good seal'


So, again, I say the web interface is broken, and It was broken last
year when the 'Take-Off Location' field was added to the form. I wish
someone would look into fixing the web interface, or you could just
send me another email telling me my file is corrupt.

Sincerely,
David Walsh



Doug Haluza wrote:
I see that you are using a Cambridge C302 logger. The SSA-OLC committe
has isolated a problem with the C302 where the logs show a security
violation when checked with Valicam2.exe, but the logger display shows
the security seal is good. We had one case where the user sent the C302
back to Cambridge, and they were able to download a good log file at
the factory using the newer v2.57 version of the Cambridge utilities.
So we are advising people to try to download the log again using the
newer software to get a valid claim. Unfortunately Cambridge still has
not posted this software version to their web site yet, so you will
need to contact Cambridge directly to obtain it.

If you are having this problem with your C302, you will see the
following when you run Valicam2.exe, or in the OLC Flight Info page:

Log Data Integrity OK
Signature Data Integrity OK
Security Fail

Assuming that your security flag is still good, you will need to
download the file again with the new software and run Valicam2.exe
again to check the file. If this does not work, you should contact
Cambridge, because you may need to send your C302 back for service.
Note that this problem is intermittent, and does not always happen with
the same logger every flight. We actually had one case where only every
other flight log was affected.

Paul Remde has more detailed info at his site:

http://www.soarmn.com/cumulus/cai/Ho...%20-%20302.pdf

As for why this is a problem this year, and not last year, OLC was
letting all Cambridge logs slide on the validation checks because of
the GPS-NAV proprietary *.CAI validation challenge. Once the GPS-NAV
workaround was in place, OLC started checking all Cambridge logs in
November of 2005. Initially there were a lot of problems with the
GPS-NAV validation, but once these were sorted out, we discovered the
C302 security flag issue. Now this is the biggest OLC validation
problem in the US.

Note that OLC is using the same FAI/IGC DOS validation software that
Official Observers and NAC representatives (the Badge Lady in the US)
are required to use. So, this C302 validation problem affects badge and
record claims and Barron Hilton Cup as well--It is not just an OLC
thing. Actually, it is a good thinig we discovered it in the OLC,
before too many people lost badge and record claims to this bug.