Connecting lap top to CAI 302

On Jun 6, 8:42*am, Cliff Hilty
wrote:
At 13:24 06 June 2011, Westbender wrote:

Do you have the switch in the correct position on the back of the 302.
Slide it towards the connection type that you're using. Either towards
the serial port or towards the USB port.

I just tried to connect to a *friends 302 via a serial cable and port on
the computer (IBM thinkpad running XP) and using SeeYou older editon at
least 5 years Old. Using connection wizard under files in seeyou, I get
connected and see all of the log files (7 or so) on the screen. Our
original intent was to delete the files so it would not be overwriting and
not giving a OLC valid file when he downloaded his log from the connected
PDA. First it does not have a "delete" option and second it locks up
while trying to "download" *any flight log. Now it was VERY hot out
yesterday while we were trying this and my computer was acting up so we
quit. But I have a few questions, should the seeyou software be able to
delete the files after downloading and two should he be having a
validation problem if the 302 is overwriting its full memory? And three
can the memory be full after just 7 flights?

CH

302 memory never fills up it wraps and records for ever and ever and
ever.

However the 302 will sometimes give a file security error. It is now
widely believed that this error is caused at the time the recording
wraps back to the begining of memory.

Email me off group for help in clearing logs. However now the error is
happened it won't happen again until the memory wraps the next time so
no real need to do anything now.

Andy

Thanks for the ideas. Switch position was not the culprit. I am
working with Jeff at R-Track Technology to get the drivers for the USB
port. Also am going to try and download a driver for the USB-RS232
adapter I already have and have used in the past. In the mean time, I
found a computer with a RS-232 port and was able to download the
flights. So, I am good to go for now.

CH - I have also run into the memory wrapping feature that causes a
security fail. For me, it happend on a single flight. its possible
that it could happen after only 7 flights, if they were long flights
and the sample rate was high (mine is set at 4 sec.) I do not know of
a way to make the file secure and get it to pass the checks. if you
don't wipe the memory of the 302, you run the risk of losing a flight
(OLC, Badge, and possibly contest - though I'd hope they would still
score you, since it is a known problem and you can still read the
flight file.)