OLC Submissions and Cambridge 302

Be advised that we have identfied a problem with the C302 where
valicam2.exe reports "Log Data Integrity OK, Signature Data Integrity
OK, Security Fail" which indicates a bad security seal, even though the
C302 reports that the security seal is good. All we know so far is that
it has happened on a C302 that has produced good logs before without
any known cause (i.e. it wasn't tampered with). Suspected causes are
nearly full memory, and not using the datacam2.exe DOS download
program, but we have not been able to isolate this yet. So if you have
had this problem, please post your story to help us understand the
problem.

Whenever you download an IGC file from the C302 (or any IGC logger) and
want to use it for OLC or FAI badges and records, you must run the IGC
DOS validation program to make sure you have a valid log file. Do this
before you erase the flight from the logger memory. If the file does
not pass validation, download it again, using a different computer if
necessary. If you are using a windows program to download, and still
get an invalid log, try the DOS version of the download program.

Hi,

I recommend using the Cambridge 300 Utility on a Pocket PC or PC first. It
is very easy to use and will work 99.9999% of the time. If it fails, try
again. If it fails multiple times then try the DOS program. It would
probably work equally well using Pocket DOS on a Pocket PC.

Good Soaring,

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

"Doug Haluza" wrote in message
oups.com...
Be advised that we have identfied a problem with the C302 where
valicam2.exe reports "Log Data Integrity OK, Signature Data Integrity
OK, Security Fail" which indicates a bad security seal, even though the
C302 reports that the security seal is good. All we know so far is that
it has happened on a C302 that has produced good logs before without
any known cause (i.e. it wasn't tampered with). Suspected causes are
nearly full memory, and not using the datacam2.exe DOS download
program, but we have not been able to isolate this yet. So if you have
had this problem, please post your story to help us understand the
problem.

Whenever you download an IGC file from the C302 (or any IGC logger) and
want to use it for OLC or FAI badges and records, you must run the IGC
DOS validation program to make sure you have a valid log file. Do this
before you erase the flight from the logger memory. If the file does
not pass validation, download it again, using a different computer if
necessary. If you are using a windows program to download, and still
get an invalid log, try the DOS version of the download program.

Doug Haluza wrote:
Be advised that we have identfied a problem with the C302 where
valicam2.exe reports "Log Data Integrity OK, Signature Data Integrity
OK, Security Fail" which indicates a bad security seal, even though the
C302 reports that the security seal is good. All we know so far is that
it has happened on a C302 that has produced good logs before without
any known cause (i.e. it wasn't tampered with). Suspected causes are
nearly full memory, and not using the datacam2.exe DOS download
program, but we have not been able to isolate this yet. So if you have
had this problem, please post your story to help us understand the
problem.

Whenever you download an IGC file from the C302 (or any IGC logger) and
want to use it for OLC or FAI badges and records, you must run the IGC
DOS validation program to make sure you have a valid log file. Do this
before you erase the flight from the logger memory. If the file does
not pass validation, download it again, using a different computer if
necessary. If you are using a windows program to download, and still
get an invalid log, try the DOS version of the download program.


Sounds exactly like the problem I had. I was downloading to an Ipaq
using the CAI supplied PDA download program. CAI said they saw a
problem like this maybe once every year or two. It then happened again
after another 9 or 10 flights. Cambridge didn't suggest trying a DOS
download, but instead replaced the flash memory. Problem hasn't
recurred, but I have had only a handful of flights since the repair, and
the repair did give an empty memory, so if that was the problem you
wouldn't see it again for quite a while.

Doug Haluza wrote:
Be advised that we have identfied a problem with the C302 where
valicam2.exe reports "Log Data Integrity OK, Signature Data Integrity
OK, Security Fail" which indicates a bad security seal, even though the
C302 reports that the security seal is good. All we know so far is that
it has happened on a C302 that has produced good logs before without
any known cause (i.e. it wasn't tampered with). Suspected causes are
nearly full memory, and not using the datacam2.exe DOS download
program, but we have not been able to isolate this yet. So if you have
had this problem, please post your story to help us understand the
problem.

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)

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)