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

PowerFLARM protocol version 6



 
 
Thread Tools Display Modes
  #1  
Old September 4th 12, 03:14 PM posted to rec.aviation.soaring
kirk.stant
external usenet poster
 
Posts: 1,260
Default PowerFLARM protocol version 6

Ok, I finally picked up a couple of ADS-B targets Monday evening - first what appeared to be a bizjet, then an AA (American Airlines?) into STL.

Got the same bug where the ADS-B callsign (AA1) sticks at the bottom of the display after the track is gone. Annoying, but not a big deal.

With my antenna in the car (hanging from the mirror), I'm getting initial PCAS hits at about 3 miles, but they then hang on until reaching the 5 mile PCAS limit set in the config file (9250m). It does seem that the PFB has a delay identifying and displaying PCAS track at first.

On first look, I would say the Butterfly people need to tweak their PCAS display a bit for the US market: the distance ring needs to be thicker (and green if no conflict (above/below), the altitude font needs to be bigger, and it would be nice if there was a digital readout of range on the side.

I would like a single beep when the display changes to show traffic and whenever a new track is displayed, then maybe 3 beeps when traffic gets close enough to be a threat.

Also, a nice enhancement would be the capability to display local time in the center of the display (below the UTC time, in a bigger font) when not on the radar display. Add a config to set UTC offset, and choice of 12 or 24 hour clock. And make that goofy red butterfly smaller!

As previously mentioned in another thread somewhere - it's definitely worth your time to play with this thing on the ground before flying with it - too bad there isn't a simulation mode to show all the various displays.

Kirk
66
  #2  
Old September 4th 12, 03:34 PM posted to rec.aviation.soaring
Andy[_1_]
external usenet poster
 
Posts: 1,565
Default PowerFLARM protocol version 6

On Sep 4, 7:14*am, "kirk.stant" wrote:

Glad you see ADS-B targets now.

re"On first look, I would say the Butterfly people need to tweak their
PCAS display a bit for the US market: the distance ring needs to be
thicker (and green if no conflict (above/below), "

The PCAS range ring goes red when indicating a conflict. Thanks to
the local helicopter traffic I have photos of that. Trouble is that,
when the conflict exist, the range ring is very small and not very
attention getting. It does not auto scale change and perhaps it
should.

I have also seen the dedicated warning screen for a helicopter
overflight. Maybe that one was ADS-B out equipped. Unfortunately was
not fast enough to get a picture.

To really understand how this display works we either need much better
documentation or a PC based simulator that can drive the display
directly. I'm thinking of setting up a few static test cases but
don't plan on taking on anything more ambitious than that.

Andy (GY)
  #3  
Old September 4th 12, 06:11 PM posted to rec.aviation.soaring
kirk.stant
external usenet poster
 
Posts: 1,260
Default PowerFLARM protocol version 6

On Tuesday, September 4, 2012 9:34:43 AM UTC-5, Andy wrote:
" The PCAS range ring goes red when indicating a conflict. Thanks to the local helicopter traffic I have photos of that. Trouble is that, when the conflict exist, the range ring is very small and not very attention getting."

That's what I'm seeing too. And the red sometimes turns to black after awhile, then becomes red again when it refreshes the target info, apparently.

Bottom line - the warning cues for a near (altitude & slant range) PCAS target are poor at present, but should be fixable.

Hope Butterfly and/or PowerFLARM USA is reading this.

Kirk
66
  #4  
Old September 4th 12, 08:28 PM posted to rec.aviation.soaring
Ramy
external usenet poster
 
Posts: 746
Default PowerFLARM protocol version 6

On Tuesday, September 4, 2012 10:11:46 AM UTC-7, kirk.stant wrote:
On Tuesday, September 4, 2012 9:34:43 AM UTC-5, Andy wrote:

" The PCAS range ring goes red when indicating a conflict. Thanks to the local helicopter traffic I have photos of that. Trouble is that, when the conflict exist, the range ring is very small and not very attention getting."



That's what I'm seeing too. And the red sometimes turns to black after awhile, then becomes red again when it refreshes the target info, apparently.



Bottom line - the warning cues for a near (altitude & slant range) PCAS target are poor at present, but should be fixable.



Hope Butterfly and/or PowerFLARM USA is reading this.



Kirk

66


I doubt Butterfly or Powerflarm USA is reading this, otherwise they would have responded. They should provide a forum for such discussion which they will monitor. However some of the readers such as Dave are affiliated with PowerFlarm so hopefully can discuss those issues with them. There was definitely feedback with the antenna installation issues. Speaking of which, I am getting very good reception (5+ miles in front,2+ miles behind)with my antennas installed in the nose of my 27 which is carbon free, so before you decide to stick a bulky antenna in front of your eyes, I suggest experimenting with cleaner installation.

Ramy
  #5  
Old September 5th 12, 06:30 PM posted to rec.aviation.soaring
Baer
external usenet poster
 
Posts: 2
Default PowerFLARM protocol version 6

Am 04.09.2012 21:28, schrieb Ramy:

I doubt Butterfly or Powerflarm USA is reading this, otherwise they
would have responded. They should provide a forum for such discussion
which they will monitor.

.........

Ramy


There is a Flarm forum since many years at http://www.flarm.ch (to be
more specific: http://flarm.invisionzone.com/ )
But it is absolutely useless to ask or propose there anything. Look at
the dates of the last posts.
I made a proposal at 'PowerFLARM' January 18th 2011. Since then there
are 1138 views but no answer or feedback. I would have noproblem if they
would tell me that the idea is stupid. But I would lke to be taken serious.
My opinion: forget them!

Bear
  #6  
Old September 5th 12, 07:39 PM posted to rec.aviation.soaring
Jim[_32_]
external usenet poster
 
Posts: 49
Default PowerFLARM protocol version 6

On Tuesday, September 4, 2012 3:28:07 PM UTC-4, Ramy wrote:
On Tuesday, September 4, 2012 10:11:46 AM UTC-7, kirk.stant wrote:

On Tuesday, September 4, 2012 9:34:43 AM UTC-5, Andy wrote:




" The PCAS range ring goes red when indicating a conflict. Thanks to the local helicopter traffic I have photos of that. Trouble is that, when the conflict exist, the range ring is very small and not very attention getting."








That's what I'm seeing too. And the red sometimes turns to black after awhile, then becomes red again when it refreshes the target info, apparently.








Bottom line - the warning cues for a near (altitude & slant range) PCAS target are poor at present, but should be fixable.








Hope Butterfly and/or PowerFLARM USA is reading this.








Kirk




66




I doubt Butterfly or Powerflarm USA is reading this, otherwise they would have responded. They should provide a forum for such discussion which they will monitor. However some of the readers such as Dave are affiliated with PowerFlarm so hopefully can discuss those issues with them. There was definitely feedback with the antenna installation issues. Speaking of which, I am getting very good reception (5+ miles in front,2+ miles behind)with my antennas installed in the nose of my 27 which is carbon free, so before you decide to stick a bulky antenna in front of your eyes, I suggest experimenting with cleaner installation.



Ramy

Hey Ramy, is the range you reported for PCAS or Flarm reception? I have my PB antennas in the nose of my all glass glider and have great PCAS range but very poor Flarm range.

-Jim
  #7  
Old September 6th 12, 04:40 AM posted to rec.aviation.soaring
Ramy
external usenet poster
 
Posts: 746
Default PowerFLARM protocol version 6

It is the other way for me. I normally see Flarm traffic way before I get the PCAS alert from the same glider, if at all. Both antennas are located in the nose so this can't be an antenna installation issue.

Ramy
  #8  
Old September 8th 12, 03:01 AM posted to rec.aviation.soaring
Fox Sierra
external usenet poster
 
Posts: 11
Default PowerFLARM protocol version 6

Ramy, could you please post a picture or diagram of your antenna installation in the '27 nose?
Thanks in advance!
Fernando Silva ('FS')
 




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
PowerFLARM Brick and PowerFLARM Remote Display Manuals Available Paul Remde Soaring 30 May 25th 12 11:58 PM
SW developers: FLARM protocol version 6 reminder Dave Nadler Soaring 0 May 24th 12 02:49 PM
Any news on the "brick" version of PowerFlarm from the SSA convention? Andrzej Kobus Soaring 7 February 8th 12 04:29 PM
Bizjet protocol JS Soaring 5 September 4th 06 06:29 AM


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


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