Butterfly display (displaying a big red logo under normal flight conditions)

On Thursday, October 17, 2013 6:58:59 PM UTC-4, Ramy wrote:
I have hundreds of hours with transponder and PF without a single false alarm. None of the 50 pilots or so that flying in our region with both PF and transponder are reporting this issue. So it is time for you to conclude this is likely a unique issue with your setup or send your PF to repair.



Ramy

Ramy,
I have Trig 22 and unfortunately I don't have flawless operation. I hear beeps alerting me to my own transponder (from time to time not consistently with errors in a log file failed to detect own transponder or something like that). Are you suggesting that some of us have faulty units?

I am going to mount soon the PF in my other glider that also has a transponder (different make) and see if I still get false alerts.

On Thursday, October 17, 2013 3:58:59 PM UTC-7, Ramy wrote:
I have hundreds of hours with transponder and PF without a single false alarm. None of the 50 pilots or so that flying in our region with both PF and transponder are reporting this issue. So it is time for you to conclude this is likely a unique issue with your setup or send your PF to repair.



Ramy

But are you, and the 50 others you cite, using the PF portable? Not that I suspect there is any difference in this respect.

Did you read the firmware release notes that describe the failure to detect co-altitude targets. If so, why do you dismiss FLARM's own assertion that there is an issue?

Wonderful that you have no false alerts but don't you have any concern that the manufacturer knows that co-altitude targets, the only ones that can hit you, may not be detected?

Andy

My "own transponder" functionality works just fine and I never get a self
alert.

I'm not sure what it's doing early in the flight - pressing the right switch
to the left, it shows a transponder code of 4707 (IIRC) and, shortly later,
it shows 1202, my squawk. It's fine after that.

"Andy" wrote in message
...
On Wednesday, October 16, 2013 8:34:06 PM UTC-7, Ramy wrote:

"After the early PCAS issues were resolved"

PCAS issues are still not resolved if you fly with a transponder. The fix
for continous "own ship" alerting appears to have been to inhibit reporting
of co-altitude targets. My portable still does not perform the function it
was purchased for (traffic awareness and collision warning for my airplane).

I hope the "other issues" the FLARM team are working on include making PCAS
work. That functionality is long overdue.


Andy

On Thursday, October 17, 2013 5:15:14 PM UTC-7, Dan Marotta wrote:
My "own transponder" functionality works just fine and I never get a self

alert.



I'm not sure what it's doing early in the flight - pressing the right switch

to the left, it shows a transponder code of 4707 (IIRC) and, shortly later,

it shows 1202, my squawk. It's fine after that.



"Andy" wrote in message

...

On Wednesday, October 16, 2013 8:34:06 PM UTC-7, Ramy wrote:



"After the early PCAS issues were resolved"



PCAS issues are still not resolved if you fly with a transponder. The fix

for continous "own ship" alerting appears to have been to inhibit reporting

of co-altitude targets. My portable still does not perform the function it

was purchased for (traffic awareness and collision warning for my airplane).



I hope the "other issues" the FLARM team are working on include making PCAS

work. That functionality is long overdue.





Andy

I used to notice the same with my MRX. When you fly close to another aircraft it will throw off both the squawk code and altitude for a while, until it eventually correct itself, or if you recycle the power. The same (for altitude) does not happen with PF PCAS.

Ramy

At 16:06 18 September 2013, RuudH wrote:
Hello all,
The Butterfly screen that indicates Flarm or PowerFlarm operation
isnormal
, but is not receiving other traffic within range, is depicted on
https://d=
l.dropboxusercontent.com/u/35654093/butterfly-no-traffic.png.
A big red indication (butterfly logo) that is not described in the
manual.
A big red indication usually is an indication of any abnormal situation in
a cockpit, especially in a cockpit of a power-plane.
For this reason I have asked the developers of Butterfly to remove the big
red butterfly from the screen during flight, because it's distracting
pilots attention.
This is the answer that I received a few days ago from Butterfly:
-------------------------------------------------------------
Aktualisiert von: Joachim Fetzer, 16. Sep 09:11 (CEST):
Hello Ruud,
thanks for your email.
We know that a red logo is not optimal in an aircraft cockpit but its the
logo of our company. We will not remove it, sorry.
For any questions we are happy to assist you.
Best wishes,
Joachim Fetzer
AIR Store
Butterfly Avionics GmbH & Garrecht Avionik GmbH
-------------------------------------------------------------
Obviously displaying their logo is more important than an optimal
indication in a cockpit...

Will the red logo be change to - air avionics (black)
http://www.air-avionics.com/air/images/air-avionics.png ?