1. Forum
  2. Usenet
  3. REC.AVIATION.SOARING

  • Re: Flarm Target direction

    From [email protected]@21:1/5 to Jonathan St. Cloud on Fri May 5 00:36:07 2023
    On Friday, June 4, 2021 at 4:49:52 PM UTC+2, Jonathan St. Cloud wrote:
    I could not feed Flarm information to both the Butterfly Vario and the LX 9070. Flarm kept losing the configure. Richard disconnected my Butterfly from the Flarm and problem solved. I am wondering how I could you have both Butterfly and LX operational
    with Flarm at the same time? Thanks in advance.
    On Thursday, June 3, 2021 at 10:10:25 AM UTC-7, Ramy wrote:
    Roy,

    Even with carbon blocking there should have been an alarm. The carbon reduces range but should not completely block. If this was the reason this is a strong case for installing B antenna in the belly. It would have been worthwhile to send both igc
    files from each powerflarm to flarm team to analyze, as it includes log data for all other flarms it receives. It could be a flarm display configuration issue. Unfortunately there is no standard nor best practice as of how to configure your display
    effectively. Every one configures differently, and some just keep factory defaults which are often wrong. I have both my old butterfly display and my LX9000 and the butterfly display provides more warnings than my LX9000. It should be fixed in the next
    LX Firmware release.

    Ramy
    On Thursday, June 3, 2021 at 9:54:58 AM UTC-7, Roy B. wrote:
    Further to the continued need for old fashioned "mark one eyeball" is recognition that Flarm does not work in all geometrical situations.
    I was an unwitting participant in a comp near miss where 2 gliders (both with correctly configured, non stealth set Flarms) failed to detect an imminent collision with the two gliders approaching each other 45 degrees off of head on and one
    slightly higher than the other. It was over in a matter of seconds, and fortunately we saw each other at the last moment, he pulled and I pushed, and he passed close over me. Neither of our Flarms gave any warning. In our talk about it afterwards we
    theorized that the carbon underbelly of the higher glider blocked the transmissions between the two Flarm antennas (both of which were mounted on our glare shields). Both Flarms continued to work properly throughout the competition.
    ROY


    Did you ever solved this?


    I have the same issue with a Classic Flarm (2 ports), the Flarm sends GPS sentences over the RJ45 as long the Butterfly isn't connected.
    As soon as I connect it, only $PFLAU sentences are sent over the line, I need to disconnect the Butterfly and reboot the Flarm to solve this.

    What does a Y-splitter electrically do? Only cutting the TX line of the display?

    I'm still wondering why the Butterfly needs to do this, the dispay also shows "reconfiguring Flarm".




    Bert

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Moshe Braner@21:1/5 to [email protected] on Fri May 5 13:53:34 2023
    On 5/5/2023 3:36 AM, [email protected] wrote:
    On Friday, June 4, 2021 at 4:49:52 PM UTC+2, Jonathan St. Cloud wrote:
    I could not feed Flarm information to both the Butterfly Vario and the LX 9070. Flarm kept losing the configure. Richard disconnected my Butterfly from the Flarm and problem solved. I am wondering how I could you have both Butterfly and LX operational
    with Flarm at the same time? Thanks in advance.
    On Thursday, June 3, 2021 at 10:10:25 AM UTC-7, Ramy wrote:
    Roy,

    Even with carbon blocking there should have been an alarm. The carbon reduces range but should not completely block. If this was the reason this is a strong case for installing B antenna in the belly. It would have been worthwhile to send both igc
    files from each powerflarm to flarm team to analyze, as it includes log data for all other flarms it receives. It could be a flarm display configuration issue. Unfortunately there is no standard nor best practice as of how to configure your display
    effectively. Every one configures differently, and some just keep factory defaults which are often wrong. I have both my old butterfly display and my LX9000 and the butterfly display provides more warnings than my LX9000. It should be fixed in the next
    LX Firmware release.

    Ramy
    On Thursday, June 3, 2021 at 9:54:58 AM UTC-7, Roy B. wrote:
    Further to the continued need for old fashioned "mark one eyeball" is recognition that Flarm does not work in all geometrical situations.
    I was an unwitting participant in a comp near miss where 2 gliders (both with correctly configured, non stealth set Flarms) failed to detect an imminent collision with the two gliders approaching each other 45 degrees off of head on and one slightly
    higher than the other. It was over in a matter of seconds, and fortunately we saw each other at the last moment, he pulled and I pushed, and he passed close over me. Neither of our Flarms gave any warning. In our talk about it afterwards we theorized
    that the carbon underbelly of the higher glider blocked the transmissions between the two Flarm antennas (both of which were mounted on our glare shields). Both Flarms continued to work properly throughout the competition.
    ROY


    Did you ever solved this?


    I have the same issue with a Classic Flarm (2 ports), the Flarm sends GPS sentences over the RJ45 as long the Butterfly isn't connected.
    As soon as I connect it, only $PFLAU sentences are sent over the line, I need to disconnect the Butterfly and reboot the Flarm to solve this.

    What does a Y-splitter electrically do? Only cutting the TX line of the display?

    I'm still wondering why the Butterfly needs to do this, the dispay also shows "reconfiguring Flarm".




    Bert


    Wouldn't be hard to build your own custom cable, that would disconnect
    the data direction Butterfly->FLARM. But first find out whether there
    is a setting in the Butterfly to disable its reconfiguring of the FLARM.

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