OLC Submissions and Cambridge 302

Thanks Marc;

Have you tried running these applications under PocketDOS on a PDA?

Seems it would be nice to not have to connect a laptop each time.

Scott

scooter wrote:
Thanks Marc;

Have you tried running these applications under PocketDOS on a PDA?

Seems it would be nice to not have to connect a laptop each time.

I've used the Cambridge-supplied PDA utility to download for several
years, with no problems. You can get it from their web site.

Marc

Use the 302 utility program available from CAI to download to the PDA:
http://www.cambridge-aero.com/300ser...ity%20Programs

The utility program reports validation, so am not sure about whether
following up with valicam is still needed.

-Tom

5Z wrote:
Use the 302 utility program available from CAI to download to the PDA:
http://www.cambridge-aero.com/300ser...ity%20Programs

The utility program reports validation, so am not sure about whether
following up with valicam is still needed.

I've never had an IGC file that validates when downloaded using the
Cambridge PDA utility, that later fails to validate with valicam2. The
paranoid (like myself), will always later verify a file using valicam2,
if they want to be certain of proper flight documentation for
badge/record (or for that matter, OLC) purposes.

The one thing you absolutely do not want to do, is download from a 302
(or other approved flight recorders) using, for (a not quite random)
example, SeeYou, and send the resulting IGC file off without verifying it...

Marc

Marc Ramsey wrote:
5Z wrote:
Use the 302 utility program available from CAI to download to the PDA:
http://www.cambridge-aero.com/300ser...ity%20Programs

The utility program reports validation, so am not sure about whether
following up with valicam is still needed.

I've never had an IGC file that validates when downloaded using the
Cambridge PDA utility, that later fails to validate with valicam2. The
paranoid (like myself), will always later verify a file using valicam2,
if they want to be certain of proper flight documentation for
badge/record (or for that matter, OLC) purposes.

The one thing you absolutely do not want to do, is download from a 302
(or other approved flight recorders) using, for (a not quite random)
example, SeeYou, and send the resulting IGC file off without verifying it...

Now hold on here, I have a CAI 302, I use the CAI Utility program
2.56 and download my flight to my PDA, to my flash card. When I get
home, I take it from my flash card to See You, then I submit it to the
OLC, using See You. I don't have any problems, not last year, year
before, or this year. I also use my 302 for contests, no problems.
Also, last year, set numerous State records. No problem. When I power
up my panel, and the 302 is turned on, I watch the 303 window for the
checks that the 302 goes thur before I go fly. When I download the
flight from the 302, using the CAI Utility progam, I get a windows
message, telling me everything is OK. I am not a software hacker, just
use it like it was designed for, and will be very happy when my new
glider gets here, so I can go fly and start posting flights on the OLC.
What I do hope for, is some year the OLC folks come up with a OLC
contest for those of us who would like to declare turnpoints before we
go flying, maybe giving us bonus points for declared completed tasks,
thus, we show we can plan a flight before we just go flying and skylark
around the sky. I do enjoy skylarking around the sky, and find using
the OLC helps me practice, by trying to get the most from the day. BUT
for me, declaring a task, and competing it, is very rewarding, just as
contest flying is, when completing the called task results in good
results. I now am rambling, which I wouldn't be, if my new glider would
of gotten here on time. As you all can see, I am not happy about my new
glider not being here. Never trust a salesman, period. The reason for
no early contest reports is.....yep.....no new glider. Salesman know so
much before they get your money, then afterwards, they know nothing.
Sorta like those 3 monkeys.......see no, hear no, speak no, they just
sit around and scratch, belch, and fart........Thermal tight, Soar
high, Fly safe, # 711.

Marc Ramsey wrote:
The one thing you absolutely do not want to do, is download from a 302
(or other approved flight recorders) using, for (a not quite random)
example, SeeYou, and send the resulting IGC file off without verifying it...

Too bad there isn't a requirement for a checksum in addition to the G
record. The checksum would validate the integrity of the file without
the overhead and "proprietariness" of validating the security of the
file.

-Tom

Actually, there is some kind of internal issue with some of the 302's.
Doesn't seem to be all but some do seem to develop this same problem
over time. Guy in my club had the same problem (Fails Security but
unit says seal is fine). Had to send in the unit to get it corrected.
Talked to Gary K and he said they had a problem and could fix it but
the units had to be sent in. Worked for my friends 302 anyway.

-Mark

wrote:
Actually, there is some kind of internal issue with some of the 302's.
Doesn't seem to be all but some do seem to develop this same problem
over time. Guy in my club had the same problem (Fails Security but
unit says seal is fine). Had to send in the unit to get it corrected.
Talked to Gary K and he said they had a problem and could fix it but
the units had to be sent in. Worked for my friends 302 anyway.

-Mark

Do you know what they did to correct it? With mine, they told me I
needed to replace the flash memory (which I did, at some expense).

Nope. They just had him send it in and it was fixed under warranty.
The only thing he paid for was a charge for calibration.

-Mark