Thread: FLARM Range
View Single Post
  #6  
Old June 16th 15, 02:40 PM posted to rec.aviation.soaring
Papa3[_2_]
external usenet poster
 
Posts: 753
Default FLARM Range

I've found FLARM to be really frustrating to work with because it hasn't always been obvious what various configuration "do". That includes both the basic configuration and especially settings required to operate with various displays. I've RTFM, but the Manual is a little quiet on the Config File.

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



On Tuesday, June 16, 2015 at 6:19:39 AM UTC-4, Andy Blackburn wrote:
On Monday, June 15, 2015 at 10:13:51 PM UTC-7, Ramy wrote:
On Monday, June 15, 2015 at 7:26:32 PM UTC-7, John Carlyle wrote:
Just to muddy the waters further, I got 50% increase in range running my same config file (with the exception of changing to protocol 7 from 6) with the new firmware AND a new PowerFlarm Core. All antennas were identical, just the hardware, firmware and protocol change were made.

-John, Q3

On Monday, June 15, 2015 at 8:58:50 PM UTC-4, Andy Blackburn wrote:
I was pretty surprised as I didn't think the config file would have , but there are some small differences in parameters that should not have any effect that I would predict. There was a change in the protocol from 6 to 7 - apparently that is important but I just put it in by rote copying as I have not read the spec. I didn't keep track of the config file from last year as I tried a lot of things to get PCAS nuisance alarms to go away. It was either this file ('Before', below) or one pretty close to it.

-- bigsnip

It works now and it clearly didn't before - every flight showed range of ~1km immediately after changing to FW v6 and every flight since reconfig has shown the same range I had last year, prior to FW v6 upgrade (~8.5 km). The comparison I posted was two consecutive days at a contest flying with the same 17 gliders, so while there are always subtle differences in who you are flying close to and at what combinations of angles, it's about as close to a controlled experiment as you are going to get.

I have heard talk and read posts from other pilots reporting range problems after upgrading to FW v6, so I thought I'd post what worked for me..

Andy
9B


In my case I suspect the reduction was due to *adding* a Flarm B antenna. I did not put it in optimal place, so perhaps it made things worse. It definitly did not improve coverage in the blind spot, while (I suspect) may have reduced coverage in the best direction. The reduction wasnt nearly as bad as Andy described, only about 30%. After removing the B antenna, I am now getting pretty much the same reception as before during the 3 flights I made since, averaging 7km. However these flights were made in different locations and with different gliders, so not exactly a controlled experiment, but I dont feel like I have a problem now. I did not change the config file and dont see anything in my config file that I think needs to be changed. Andy you mention changing protocol 6 to 7, but I assume you refer to the firmware and not configuration right?

Ramy


The reference to Protocol 7 (vs 6) is in the NMEAOUT commands:

$PFLAC,S,NMEAOUT2,71

and

$PFLAC,S,NMEAOUT1,71

I'm going to have to look up what it refers to in the spec. Now I'm wondering if something got corrupted when I did the firmware upgrade or if the existing config file somehow got overwritten.

The degradation in range was immediate, obvious and was resolved just as quickly and obviously with a new config file. That new file didn't try to change anything in the setup, though may have had some subtle differences in instructions. Because of my installation, the original config file was hand-built with advice from Flarm tech support, not downloaded off of the tool, so it's possible that something I was allowed to do in the old firmware stopped working in v6.

Gremlins...

9B