IGC files & Linux

Hello,

I am new joiner on Linux and I tried KFLOG software. Unfortunately,
this software has obsolete data files and has not been updated since
years.

Another one is GPLIGC, but this one is difficult to install
(especially the stuff named Perl-KT).

How are linux users (lovers?) reading and managing their IGC files?

Many thanks for your kind help.
Bruno

On Apr 6, 6:49*am, nimbus wrote:
Hello,

I am new joiner on Linux and I tried KFLOG software. Unfortunately,
this software has obsolete data files and has not been updated since
years.

Another one is GPLIGC, but this one is difficult to install
(especially the stuff named Perl-KT).

How are linux users (lovers?) reading and managing their IGC files?

Many thanks for your kind help.
Bruno


SeeYou reportedly runs fine under wine on Linux. See threads on the
Naviter support forum.


Or, especially if you find you have any reason for real Windows, you
can go the whole hog (hog being a good description for Windows) and
run SeeYou on Windows using VMware Workstation or similar products
under Linux. Personally I run SeeYou under VMware Fusion on Windows XP
on my Mac PowerBook Pro.


Darryl

On Apr 6, 9:49*am, nimbus wrote:

I am new joiner on Linux and I tried KFLOG software. Unfortunately,
this software has obsolete data files and has not been updated since
years.

I'm using the Cumulus software on my Linux n800 handheld, which comes
from the kflog.org website. I'm planning on trying out KFlog on a KDE
desktop later this month.

Can you tell me a little more about what you mean by "obsolete data
files"? Do you mean airspace and topography files? My understanding
is that kflog uses the same data files as Cumulus, and the Cumulus
data files I have are perfectly recent. Dave Springfold told me
yesterday that he updated the Southern Ontario airspace file in the
last week or two, but the newest one posted at http://soaringweb.org/SUA/NA/
is still from 4 March 2009. (He changed the radius and center of
"Heavy Metal Alley" between Waterloo and Guelph.)

I think perhaps you're reading the wrong kflog documentation, or
you've got a different definition of "obsolete" than I do.

Cheers,

Rob

On Mon, 06 Apr 2009 06:49:13 -0700, nimbus wrote:

Hello,

I am new joiner on Linux and I tried KFLOG software. Unfortunately, this
software has obsolete data files and has not been updated since years.

Another one is GPLIGC, but this one is difficult to install (especially
the stuff named Perl-KT).

How are linux users (lovers?) reading and managing their IGC files?

I'm running RedHat Fedora 8 and Wine 1.1.9, installed from the Fedora
repository, on the box I use to manage and store flight logs.

I have an EW model D logger and an old copy of EWView 3.08 for Win95:
- the EW downloader installed correctly and manages all aspects of
the logger. It downloads logs, clears memory, sets declarations and
the clock and reports battery voltage.

However, it will only work with a 'real' serial port either on the
mother board or an adapter card. It does not work with a USB serial
adapter.

- EWView more or less runs. It displays waypoints etc and plots the
flight, but crashes if I ask for the baro plot or flight stats.
It shows raw data but is flaky about managing or drawing tasks.

I also have a PNA (Binatone X.350) running XCSoar 5.2.2 off an SD card.
Loading programs and files onto the SD card is simple drag 'n drop. so is
pulling logs off the SD card. XCSoar generates IGC logs but EWView
doesn't like them and crashes.

I'm currently looking for a replacement for EWView, preferably something
that runs as a native Linux application. So far I've only found GPLIGC
and igcview, but the latter has an applet that doesn't want to run on my
system. It looks rather like my choice is between GPLIGC and rolling my
own as a Java application.

HTH


--
martin@ | Martin Gregorie
gregorie. | Essex, UK
org |

I like KFLOG very much but the application needs data files.

What concerns ground or map terrain, the old file published in 2001
are still OK. Terrains do not change as fast as the weather....

But what concerns the use of waypoints and airspace, the files seems
to be designed for the very fisrt version of KFLOG. I has some
problems running KFLOG with those.

Another point, is the fact that data files have a kfl extension. What
is the content of this file? The file format in not yet clear to me. I
had the idea to manually updated those files.
As I don't know how the data format is designed, it is nearly
impossible to have fresh data.

Another missing functionality is the lack of engine noise reading.
But I still needs a few days to play with the tool to analyse it
further into the details.

Bruno

At 19:59 06 April 2009, Martin Gregorie wrote:
On Mon, 06 Apr 2009 06:49:13 -0700, nimbus wrote:

Hello,

I am new joiner on Linux and I tried KFLOG software. Unfortunately,
this
software has obsolete data files and has not been updated since years.

Another one is GPLIGC, but this one is difficult to install
(especially
the stuff named Perl-KT).

How are linux users (lovers?) reading and managing their IGC files?

I'm running RedHat Fedora 8 and Wine 1.1.9, installed from the Fedora
repository, on the box I use to manage and store flight logs.

I have an EW model D logger and an old copy of EWView 3.08 for Win95:
- the EW downloader installed correctly and manages all aspects of
the logger. It downloads logs, clears memory, sets declarations and
the clock and reports battery voltage.

However, it will only work with a 'real' serial port either on the
mother board or an adapter card. It does not work with a USB serial
adapter.

Which Version of EW downloader are you using? At
http://www.edavies.nildram.co.uk/ew/...dows-uploader/ there is a
version 0523X for use with USB adaptors.

But check which version of the cable you have. Looking at:
http://www.spsys.demon.co.uk/images/ewcable.gif make sure it is NOT
modified for RTS signalling (see note).

Or the problem might be the model of Adaptor you are using. Some won't
work on Native Windows either. In my experiance Belkin is the best bet.


Tim Newport-Peace >
Skype: specialist_systems
http://www.spsys.demon.co.uk/icom.htm

On Apr 6, 6:00*pm, nimbus wrote:

Another point, is the fact that data files have a kfl extension. What
is the content of this file? The file format in not yet clear to me. I
had the idea to manually updated those files.
As I don't know how the data format is designed, it is nearly
impossible to have fresh data.

I haven't tried KFlog myself yet, but I would think that the current
version now supports the new data file formats described at
http://www.kflog.org/fileadmin/user_...ulus-maps.html

Then again, I may be in for a rude awakening. Have you tried asking
on the KFlog mailing list at http://www.kflog.org/kflog/ ? I've just
signed up.

Cheers,

Rob.

On Apr 6, 6:00*pm, nimbus wrote:
I like KFLOG very much but the application needs data files.

What concerns ground or map terrain, the old file published in 2001
are still OK. Terrains do not change as fast as the weather....

But what concerns the use of waypoints and airspace, the files seems
to be designed for the very fisrt version of KFLOG. I has some
problems running KFLOG with those.

Another point, is the fact that data files have a kfl extension. What
is the content of this file? The file format in not yet clear to me. I
had the idea to manually updated those files.
As I don't know how the data format is designed, it is nearly
impossible to have fresh data.

Another missing functionality is the lack of engine noise reading.
But I still needs a few days to play with the tool to analyse it
further into the details.

Bruno

Hmm. I might take a look at the data files sometime this week. If
worse comes to worse one could always look at the source and determine
the format from there. If there is a source for updated data
available in any easily parseable format it should be relatively
simple to update the KFLOG data files.

Mike

Fresh data files are important....

I like KFLOG very much because it offers just what I need i.e. seeing
my flight path over terrain. All the other functionalities i.e.
offered by other tools such as SeeYou, Strepla etc....are also nice
but not absolutely necessary.

Bruno

On Mon, 06 Apr 2009 23:00:04 +0000, Tim Newport-Peace wrote:

Which Version of EW downloader are you using? At
http://www.edavies.nildram.co.uk/ew/...dows-uploader/ there is a
version 0523X for use with USB adaptors.

That's the one.

The problem was that no matter what I did it couldn't find any
/dev/ttyUSB* devices though it has no trouble with /dev/ttyS[0-5], which
are happily mapped as COM1 to COM6.

Before you ask, yes I am on the wine-users mailing list and no, they
couldn't suggest a workround. The usual suggestion (symlinking /dev/
ttyUSB0 to ~/.wine/dosdevices/COM1 didn't help, but the other
suggestion (buy a serial adapter card) worked like a dream and was
surprisingly inexpensive - /dev/ttyS[01] are permanently in use, so not
available for downloading the logger.

FWIW my USB-serial adapter is the model pfranc used to sell in 2004 and
has worked just fine with native Linux programs (both minicom and my own
C code). At the time I bought it, the Belkin wasn't out and all the other
makes had issues.

IIRC the Wine problem has to do with Wine not having equivalents of the
usual Windows USB device drivers and (of course) the Windows drivers
don't work in the Linux environment.


--
martin@ | Martin Gregorie
gregorie. | Essex, UK
org |