Flarm picking up my transponder

I have a similar problem on tow behind a tow plane with newly installed ADS-B out. The glider Flarm goes nuts. Any fixes for this (besides shutting something off)?
ROY

I have a similar problem on tow behind a tow plane with newly installed ADS-B out. The glider Flarm goes nuts. Any fixes for this (besides shutting something off)?

I've seen that as well. A warning for an approaching tow plane seems useful, but for one at the other end of a 200 foot tow rope, not so much.

Is some place to look in a log to see what happened?

You might want to try putting the towplane PowerFLARM ICAO on FlarmNet and subsequently loading the current FlarmNet database on your Flarm display.

On Friday, April 24, 2020 at 11:51:16 AM UTC-4, Roy B. wrote:
I have a similar problem on tow behind a tow plane with newly installed ADS-B out. The glider Flarm goes nuts. Any fixes for this (besides shutting something off)?
ROY

Are you updated to the current version? They have continually worked at reducing nuisance alarms from the tug. Version 7 (withdrawn for North America due to problems associated with Mode C alerts) was supposed to have fixed more ADS-B/FLARM problems (look at the release notes). 6.83 is current for PowerFLARM CORE and Portable assuming you are in North America.

Send an e-mail to and let them know you'd like this fixed.

On Friday, April 24, 2020 at 10:03:30 AM UTC-6, wrote:
I have a similar problem on tow behind a tow plane with newly installed ADS-B out. The glider Flarm goes nuts. Any fixes for this (besides shutting something off)?

I've seen that as well. A warning for an approaching tow plane seems useful, but for one at the other end of a 200 foot tow rope, not so much.

Is some place to look in a log to see what happened?

You'd think that with all the sophisticated algorithms FLARM uses to predict collisions, that they could also figure out a way to identify a tow plane that was towing a glider and not make it alarm.

You'd think that with all the sophisticated algorithms FLARM uses to predict collisions, that they could also figure out a way to identify a tow plane that was towing a glider and not make it alarm.

Or have a button to push that says "Got it - now shut up"
ROY

Adding the tow plane to flarmnet is a good idea so you can identify it. We did this for our tow plane successfully.
However this has no influence on alarms since the powerflarm core itself does not know anything about flarmnet. The flarmnet is only used by the flarm display.
I been following up with flarm team on the ADSB alarm issue but this got stalled when our club halt operation.

Ramy

I thought you had to be on a collision course to sound a Flarm alarm.Â*
Dragging at the end of a rope hardly meets that condition.

On 4/24/2020 1:07 PM, Roy B. wrote:
You'd think that with all the sophisticated algorithms FLARM uses to predict collisions, that they could also figure out a way to identify a tow plane that was towing a glider and not make it alarm.

Or have a button to push that says "Got it - now shut up"
ROY


--
Dan, 5J

Adsb is handled differently than flarm protocall. Its just altitude and proximity so yes at the other end of the rope it is a target. But mine was solved with the powerflarm update mentioned earlier in this thread.

CH

At 22:57 24 April 2020, wrote:
Adsb is handled differently than flarm protocall. Its just altitude and
proximity so yes at the other end of the rope it is a target. But mine
was
solved with the powerflarm update mentioned earlier in this thread.

CH


Is tne tug set correctly in its config.txt file? Tug should have acft=2 .
This define
it as a tug. Easy to check when out of lockdown. Look at a downloads file
and
and should have a file flarmdev, look for acft=