View Single Post
  #2  
Old September 13th 04, 07:38 AM
unt
external usenet poster
 
Posts: n/a
Default


Hi

If data transfer is causing over-run errors, then a slower Baud rate
should help. As the volume of data is not that high the overhead in
using a slower connection is not that great.


I tested this with the LX20 programs - no success. The LX400 program has
only 9600 and it is not possible to change. It is a really old one.

Many IGC-Approved Flight Recorders allow you the set the baud rate to a
speed other than the default (Volkslogger, Filser, Colibri, SDI and LX
for example). The default speed is not the same for all recorders.

Having changed the speed in the recorder, you must change the speed in
the program. This is done with a parameter when calling the DATA-???.EXE
DOS program. The usual form is -b4800 for 4800 baud etc.


I used the data-fil.exe program to fiddle with the logger file download - no
success, it sopps after about 10 seconds. Lxnavigation has made a program
called Downloader, which works for the LX20 et. al. But not for the old
LX400. That's the reason why I'm trying with the PoketDOS and the original
software from Filser.

At the moment I only see a solution in programming on my own with SuperWaba
(Java based and portable for Windows CE and Palm OS with the same source).
There is an example for Garmin GPS and I have the data structur files
received from lxnavigation for the LX400. I hope the winter is long enough !
;-)

René.