A aviation & planes forum. AviationBanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » AviationBanter forum » rec.aviation newsgroups » Soaring
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Flarm Target direction



 
 
Thread Tools Display Modes
  #21  
Old June 4th 21, 08:32 PM posted to rec.aviation.soaring
Robert S
external usenet poster
 
Posts: 11
Default Flarm Target direction

On Friday, June 4, 2021 at 9:49:52 AM UTC-5, 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

I don't have a LX but I do feed my FLARM data to both a Butterfly display and an xcsoar based flight computer display and it works perfectly. I use the FLARM RJ-45 output to go to the Butterfly display and I use the FLARM DB9 output to go to the computer. Are you trying to drive both devices from just one of the FLARM outputs in a daisy chain fashion? Another thought is to check the various protocols you're using to send data to your devices. In my case I have both FLARM data channels running at 57k bps. Your Butterfly display should automatically discover and configure itself for the proper data rate so no reason to use anything less than the maximum speed. I have the RJ45 channel (output 1) sending FLARM and GPS data in default format and the DB9 channel (output 2) sending just FLARM data in format 7 (My computer gets its GPS data from a 302 vario). The FLARM config statements that set all of that up a
$PFLAC,S,NMEAOUT2,73
$PFLAC,S,BAUD2,5
$PFLAC,S,NMEAOUT1,1
$PFLAC,S,BAUD1,5

Robert
Ads
  #22  
Old June 4th 21, 10:57 PM posted to rec.aviation.soaring
Ramy[_2_]
external usenet poster
 
Posts: 601
Default Flarm Target direction

I am doing the same, using both of my powerflarm ports.
Powerflarm can certainly support multiple displays, in fact it also drives my XCSoar, so a total of 3 devices connected to it.
As for antenna position as other recommendations and tips, flarm provided detail recommendations, the problem is that it requires investing time to research or money for a professional installation. Since most of us install ourselves and don’t utilize the B antenna, the results vary significantly. But I found out that most installation are adequate for most situations.

Ramy

On Friday, June 4, 2021 at 12:32:12 PM UTC-7, wrote:
On Friday, June 4, 2021 at 9:49:52 AM UTC-5, 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

I don't have a LX but I do feed my FLARM data to both a Butterfly display and an xcsoar based flight computer display and it works perfectly. I use the FLARM RJ-45 output to go to the Butterfly display and I use the FLARM DB9 output to go to the computer. Are you trying to drive both devices from just one of the FLARM outputs in a daisy chain fashion? Another thought is to check the various protocols you're using to send data to your devices. In my case I have both FLARM data channels running at 57k bps. Your Butterfly display should automatically discover and configure itself for the proper data rate so no reason to use anything less than the maximum speed. I have the RJ45 channel (output 1) sending FLARM and GPS data in default format and the DB9 channel (output 2) sending just FLARM data in format 7 (My computer gets its GPS data from a 302 vario). The FLARM config statements that set all of that up a
$PFLAC,S,NMEAOUT2,73
$PFLAC,S,BAUD2,5
$PFLAC,S,NMEAOUT1,1
$PFLAC,S,BAUD1,5

Robert

  #23  
Old June 5th 21, 12:55 AM posted to rec.aviation.soaring
Dan Marotta
external usenet poster
 
Posts: 4,601
Default Flarm Target direction

While it's not the ideal solution, I connected my Powerflarm portable to
both my ClearNav and to a Dell Streak running XCSoar using a simple Cat
5 cable splitter.* A better way would to use a powered splitter,
something like THIS
https://www.mouser.com/ProductDetail/Brainboxes/SW-005?qs=BJlw7L4Cy7944%2FIWYfp8eA%3D%3D&mgh=1.
I never had any trouble using THESE
https://smile.amazon.com/Ethernet-Splitter-Canbuau-Internet-Connector/dp/B08PDY3R1K/ref=sxin_11_ac_d_pm?ac_md=1-0-VW5kZXIgJDEw-ac_d_pm&cv_ct_cx=ethernet+splitter&dchild=1&keywor ds=ethernet+splitter&pd_rd_i=B08PDY3R1K&pd_rd_r=0d 1afd36-68d6-4077-84b0-d097178c87ee&pd_rd_w=wicTd&pd_rd_wg=RcYgU&pf_rd_p= fbf6011c-6632-49e8-9631-4e76f7f44920&pf_rd_r=G7TPFYQ87SSCNWN228Y4&psc=1&qi d=1622850900&sr=1-1-22d05c05-1231-4126-b7c4-3e7a9c0027d0.


Dan
5J

On 6/4/21 8:49 AM, 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

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Boulton Paul Defiant pics 2 [3/7] - Defiant TT Mk III target tug, number N1697; RAF Desford, May 1944. The wind-driven generator provided power for the target winch.jpg (1/1) Miloch Aviation Photos 0 September 10th 18 03:25 PM
trying to work out how you connect the flarm view 57 to mini box flarm running a V7 and Oudie Michael Marshall[_2_] Soaring 3 April 10th 16 04:13 AM
trying to work out how you connect the flarm view 57 to mini box flarm running a V7 and Oudie Michael Marshall[_2_] Soaring 0 April 8th 16 08:57 PM
Information for all users of Flarm, OEM FLARM supplier and Flarm PowerFlarm [email protected] Soaring 28 March 12th 16 04:31 AM
Flarm IGC files on non-IGC certified Flarm? Movses Soaring 21 March 16th 15 09:59 PM


All times are GMT +1. The time now is 07:33 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2022, Jelsoft Enterprises Ltd.
Copyright 2004-2022 AviationBanter.
The comments are property of their posters.