• FLARM "seeing" same aircraft

    From Moshe Braner@21:1/5 to All on Fri Jul 14 11:53:10 2023
    There is a FLARM setting to avoid it "seeing" a Mode-S transponder in
    the same aircraft (transmitting the same ID). Does that setting also
    cause FLARM to ignore FLARM transmissions with the same ID? In case one
    has two FLARM-compatible devices in the same aircraft.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dan Daly@21:1/5 to Moshe Braner on Fri Jul 14 10:20:14 2023
    On Friday, July 14, 2023 at 11:53:13 AM UTC-4, Moshe Braner wrote:
    There is a FLARM setting to avoid it "seeing" a Mode-S transponder in
    the same aircraft (transmitting the same ID). Does that setting also
    cause FLARM to ignore FLARM transmissions with the same ID? In case one
    has two FLARM-compatible devices in the same aircraft.

    If there are two FLARMs with the same ID, either within one aircraft/glider, or if two gliders with the same ID (usually someone borrows the USB stick to update their FLARM firmware), the two FLARMs go into random mode, and if you are looking at the OGN
    or Glidertracker.org, you will see the position of the FLARM target bounce between the positions of the two gliders (I don't know if you'd be able to notice the difference of two within one glider). I suspect but haven't found in the documentation that
    having the two gliders with a single ID within range of another FLARM must confuse the warning picture. I have pictures of what it looks like on the OGN - a sawtooth jumping back and forth between targets every few seconds.

    I cannot picture a situation where one might have more than one FLARM-compatible device in the same aircraft. Could you give an example?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Kerry Kirby@21:1/5 to Dan Daly on Mon Aug 7 17:59:28 2023
    On Friday, July 14, 2023 at 1:20:17 PM UTC-4, Dan Daly wrote:
    On Friday, July 14, 2023 at 11:53:13 AM UTC-4, Moshe Braner wrote:
    There is a FLARM setting to avoid it "seeing" a Mode-S transponder in
    the same aircraft (transmitting the same ID). Does that setting also
    cause FLARM to ignore FLARM transmissions with the same ID? In case one has two FLARM-compatible devices in the same aircraft.
    If there are two FLARMs with the same ID, either within one aircraft/glider, or if two gliders with the same ID (usually someone borrows the USB stick to update their FLARM firmware), the two FLARMs go into random mode, and if you are looking at the
    OGN or Glidertracker.org, you will see the position of the FLARM target bounce between the positions of the two gliders (I don't know if you'd be able to notice the difference of two within one glider). I suspect but haven't found in the documentation
    that having the two gliders with a single ID within range of another FLARM must confuse the warning picture. I have pictures of what it looks like on the OGN - a sawtooth jumping back and forth between targets every few seconds.

    I cannot picture a situation where one might have more than one FLARM-compatible device in the same aircraft. Could you give an example?

    Dan would that not be like mine? An S80 and a Craggy Ultimate. Both are hooked to the Flarm core. ( or going from one device to another not sure) anyway I have a trig 22 and many times in the flight I have to shut the Trig on and off otherwise I am
    about to crash into myself. I have reset the config 3 times with my hex code but it soon reverts to seeing myself as a conflict. I probably need a therapist.

    Kerry

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dan Daly@21:1/5 to All on Mon Aug 7 19:07:15 2023
    Hi Kerry, in this case, two different gliders with the same 6-digit hex code. Are you using the latest flarm firmware (7.21, released in May)? I find a lot less nuisance alerting problems, and the old problem of a towplane with FLARM and Transponder
    alerting the towed glider has pretty well vanished at the club since we went to version 7.20.
    We haven't seen the self-alerting problem on any of the 3 gliders with transponders and PowerFLARM (2 Trigs and an old Mode C) for a few PowerFLARM versions.
    Are you at the latest version of Trig software?
    Cheers
    Dan

    Dan would that not be like mine? An S80 and a Craggy Ultimate. Both are hooked to the Flarm core. ( or going from one device to another not sure) anyway I have a trig 22 and many times in the flight I have to shut the Trig on and off otherwise I am
    about to crash into myself. I have reset the config 3 times with my hex code but it soon reverts to seeing myself as a conflict. I probably need a therapist.

    Kerry

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)