FLARM Range

On Tuesday, June 16, 2015 at 9:19:36 AM UTC-7, Andy Blackburn wrote:
On Tuesday, June 16, 2015 at 6:40:50 AM UTC-7, Papa3 wrote:

Is there another document that has more detail on configuration file values/settings?

You can read the FLARM Dataport Specification. Here is a link to v6.

http://www.ediatec.ch/pdf/FLARM_Data...ual_v6.00E.pdf

To get v7, you need to send request to: . It's technical and mostly targeted at developers. Apparently, there is a Configuration Manual in the works.

Here is link to an annotated configuration file that helps explain some key things. Any line beginning with a # is commented out and won't be executed by your FLARM.

https://drive.google.com/open?id=0Bw...ZTQ&authuser=0

9B

In the V6 dataport manual, it says that anything set to 71 is going to revert to 1 at the next power up.

On Tuesday, June 16, 2015 at 9:41:53 AM UTC-7, jfitch wrote:

In the V6 dataport manual, it says that anything set to 71 is going to revert to 1 at the next power up.

Apparently that's different for the new v7 Protocol - but I have not seen the new spec. Also apparently the protocol that needs to be used may depend on the device that's connected -- and some devices configure the protocol themselves.

Wheeeee! Fun!

9B

Fun - Exactly!! The marked up config file supplied as an example doesn't actually relate to some of the options in the updated Configuration Tool.

I spent hours at Mifflin trying to get Karl Striedieck's Flarm Core to speak with his FlarmView. Tried bare-bones "default" and multiple other variations, but it never seemed to work completely. Part of the problem was several variables changing at once (Powerflarm software version update, config file update, Flarmview update).

On Tuesday, June 16, 2015 at 3:25:56 PM UTC-4, Andy Blackburn wrote:
On Tuesday, June 16, 2015 at 9:41:53 AM UTC-7, jfitch wrote:

In the V6 dataport manual, it says that anything set to 71 is going to revert to 1 at the next power up.

Apparently that's different for the new v7 Protocol - but I have not seen the new spec. Also apparently the protocol that needs to be used may depend on the device that's connected -- and some devices configure the protocol themselves.

Wheeeee! Fun!

9B

On Tuesday, June 16, 2015 at 1:04:41 PM UTC-7, Papa3 wrote:
Fun - Exactly!! The marked up config file supplied as an example doesn't actually relate to some of the options in the updated Configuration Tool.


Yeah. Between what's in the (now 1 version behind) Dataport Specification, the (partly out of date) commented FLARMCFG.TXT file, some undocumented configuration commands I got last year and the (hopefully) upcoming Configuration Manual, I hope to get a better handle on this. Obviously not all of those things are going to be 100% consistent. The interplay between PowerFLARM firmware and the various device firmware updates also makes it pretty challenging without some inside knowledge - or known good configurations - to work with.

It's a pretty sophisticated piece of technology. I'm thankful it works as well as it does.

9B