[Kflog-user] Suggestion for KFlog: Flarm integration (new try)
eggert.ehmke at berlin.de
Thu Aug 4 10:13:57 CEST 2011
thanks for comments. Answers below.
On Thursday 04 August 2011 09:25:02 flieger-axel at web.de wrote:
> > I started some basic integration of Flarm devices. As a beginning, I
> > implemented an export function that allows to export the flarmcfg.txt
> > file. As
> Maybe you can add a date and time stamp into the first line to see when the
> file was created?
Good idea. Will add that. BTW, the flarmcfg that I attached to the last mail
contains only Unix line separators. In the Flarm Dataport Manual it is
requested that each line is terminated by 0A0D characters. I changed that in
> > a next step the upload of the task data via the serial interface makes
> > sense.
> > Before I start to check in the updates I want to discuss the approach.
> > I added a new plugin for the Flarm device. A file export is not
> > supported
> > up
> > to now by other recorder plugins. But because the format is device
> > specific,
> > it makes sense to have this function in the recorder plugin itself. I
> > implemented it as virtual method that is marked "not supported" by the
> > other
> > plugins. Because it works on local file, no actual recorder connection
> > is
> > required. Because the format of the flarmcfg.txt file is similar to the
> > upload
> > data, we can expect to reuse this function.
> Yes that is a good idea to make it in this manner.
> > Currently the file is written to the home directory of the user. But of
> > course
> > we could write it directly to a mounted sd card.
> We can provide a save dialog to the user, that he can select his preferred
> destination for the Flarm file storage.
Will add a file save dialog.
> > In the user interface, the new plugin appears as recorder type FLarm.
> > The
> > created lib is libkfrfla. The export function is part of the Declaration
> > screen. It is disabled (but visible) for all other recorders. See
> > attached screen shots. The created flarmcfg.txt (zipped) is also
> > attached.
> > Please comment and let me know if this approach is ok for you.
> I think that would be a good enhancement of KFLog.
Ok so I will start to add these additions. As for a license issue: in the
Flarm Dataport Manual this text is contained:
Note that this document as well as the interface described with it are
proprietary and copyright protected. Any non-licensed use, dissemination,
copying, implementation, reverse engineering or decompilation of the
FLARM data port communication protocol or parts of it is forbidden by law and
will be prosecuted. FLARM is an internationally registered trademark and can
not be used without license.
Please let us know about your products and designs that use FLARM’s data
To be on the safe side I will contact the Flarm developer mailing list and
anounce our activities.
More information about the Kflog-user