Cambridge 302A Data integrity.

Hi,

I have just received my 302A back from a barograph calibration and now
the flight logs that I download returns an error message 'Security
Fail'. It still gives me an igc file that I can up load to OLC but the
flight remains greyed out with a message that the 'log file not
valid' . I have messed with the turnpoint database since it came back
from R Track so I am not sure what it might be.

Any ideas?

Bob

7U

Bob wrote:
Hi,

I have just received my 302A back from a barograph calibration and now
the flight logs that I download returns an error message 'Security
Fail'. It still gives me an igc file that I can up load to OLC but the
flight remains greyed out with a message that the 'log file not
valid' . I have messed with the turnpoint database since it came back
from R Track so I am not sure what it might be.

Any ideas?

Yes, your 302A is no longer electronically sealed. It needs to go back
to Cambridge or their local agent to be resealed.

Marc

On Jun 3, 2:48 pm, Bob wrote:
Hi,

I have just received my 302A back from a barograph calibration and now
the flight logs that I download returns an error message 'Security
Fail'. It still gives me an igc file that I can up load to OLC but the
flight remains greyed out with a message that the 'log file not
valid' . I have messed with the turnpoint database since it came back
from R Track so I am not sure what it might be.

Any ideas?

Bob

7U


My mdoel 20 gps/logger was just recently returned to Cambridge for
repair because I was getting the security failure. The files now
should as security when viewed with the Cambridge utility but OLC
still shows them as invalid.

wrote:
On Jun 3, 2:48 pm, Bob wrote:
Hi,

I have just received my 302A back from a barograph calibration and now
the flight logs that I download returns an error message 'Security
Fail'. It still gives me an igc file that I can up load to OLC but the
flight remains greyed out with a message that the 'log file not
valid' . I have messed with the turnpoint database since it came back
from R Track so I am not sure what it might be.

Any ideas?

Bob

7U


My mdoel 20 gps/logger was just recently returned to Cambridge for
repair because I was getting the security failure. The files now
should as security when viewed with the Cambridge utility but OLC
still shows them as invalid.


That would be a different problem.

Looking at your file posted on OLC, it appears to be just a normal
..igc file, rather than the munged-up abomination required by OLC
when using a model 10, 20, or 25. You need to use a utility that
combines the .cai and the .igc into another file called .igc.
Here's a link: http://www.abqsoaring.org/misc_files/CAI_fix.htm
The flight analysis software packages can also do it automatically,
sometimes with patches required.

-Dave

On Jun 6, 5:19 am, David Kinsell wrote:
wrote:
On Jun 3, 2:48 pm, Bob wrote:
Hi,

I have just received my 302A back from a barograph calibration and now
the flight logs that I download returns an error message 'Security
Fail'. It still gives me an igc file that I can up load to OLC but the
flight remains greyed out with a message that the 'log file not
valid' . I have messed with the turnpoint database since it came back
from R Track so I am not sure what it might be.

Any ideas?

Bob

7U

My mdoel 20 gps/logger was just recently returned to Cambridge for
repair because I was getting the security failure. The files now
should as security when viewed with the Cambridge utility but OLC
still shows them as invalid.

That would be a different problem.

Looking at your file posted on OLC, it appears to be just a normal
.igc file, rather than the munged-up abomination required by OLC
when using a model 10, 20, or 25. You need to use a utility that
combines the .cai and the .igc into another file called .igc.
Here's a link: http://www.abqsoaring.org/misc_files/CAI_fix.htm
The flight analysis software packages can also do it automatically,
sometimes with patches required.

-Dave- Hide quoted text -

- Show quoted text -

Thanks Dave!