New Butterfly Display Software 3.2.1 released

[Marc - Butterfly Avionics]

Hi,

thanks for the feedback we received from you here in R.A.S regarding Butterfly Display software.

I am happy to tell you today that the team has been able to nearly implement all of the requested changes. The new version 3.2.1 features the following changes:

• full menu is always available (also in flight)
• short beep if display switches from no-traffic-screen to radar
• new aircraft selection style for better readability
• hide Target ID if selected aircraft is out of range
• fixed digit width for UTC time
• bigger signs for relative altitudes and climb rates
• selecting targets also in nearest mode, selection switches back to nearest target after 10 seconds

Please find the new version here: http://www.butterfly-avionics.com/index.php/en/support-english

Update instructions can be found here: http://www.butterfly.aero/support/ButterflyDisplay_SoftwareChangelog.pdf

Additionally we have released a new and significantly reworked manual: http://www.butterfly.aero/support/ButterflyDisplay_EN_EU.pdf

Best regards and again thanks for your feedback!

Marc
Butterfly Avionics

[[email protected]]

Thank you, Marc.

Now....what about bringing the Butterfly Vario display up to this level of sophistication?

Guy

[[email protected]]

Agree. The traffic display for the vario is inadequate.

Chris

[jfitch]

On Friday, July 26, 2013 9:48:54 AM UTC-7, wrote:
> Agree. The traffic display for the vario is inadequate.
>
>
>
> Chris

I'd settle for just the alarm screen.

All the other stuff is better displayed on a PDA anyway, wouldn't hurt to have it on the vario but I'd rather look at the PDA.

[[email protected]]

On Friday, July 26, 2013 4:15:57 PM UTC-5, jfitch wrote:
> On Friday, July 26, 2013 9:48:54 AM UTC-7, wrote:
>
> > Agree. The traffic display for the vario is inadequate.
>
> >
>
> >
>
> >
>
> > Chris
>
>
>
> I'd settle for just the alarm screen.
>
>
>
> All the other stuff is better displayed on a PDA anyway, wouldn't hurt to have it on the vario but I'd rather look at the PDA.

Marc,
I guess I messed up installing the update announced above. I loaded the .bfd file on my 2GB stick that I normally use for flight downloads. After inserting it into the Core I pressed the display button and turned PFlarm on. It loaded a file from the memory stick and after a while the display changed from UPDATE MODE WAITING to ... LOADING.
That was displayed for what that seemed like 10 min. Since the memory card war not being read (no lights flickering), I turned the PFlarm off and tried to load again. Now the display has ....Waiting on immediately with the word flashing. Taking out the memory stick, the display only shows the Butterfly with some text but the unit does not boot up into acquiring satellites.
What to do?

Thanks, Herb

[Marc - Butterfly Avionics]

Hi Herb,

to me this sounds like your PF configuration got lost and now the display does not receive data from the PF. Its very hard to actually crash the display during update process, I don't think that this has happened.

Please review your config-file, you can use the tool we have on our website: http://www.butterfly-avionics.com/index.php/en/products/powerflarm-en/powerflarm-core-config-en

Best regards
Marc

[Andy[_1_]]

Today I updated by brick to 3.3.1 and my Butterfly display to 3.2.1.

At first, operation seemed normal and PCAS targets were displayed ok. Just a few minutes later the display went into a reset loop which had a 2-5 sec period. The loop was a cycle between the display boot screen and a "radar" display with a single ADS-B target.

The problem was seen in "knob at bottom" orientation. I changed orientation but no ADS-B targets seen since then.

I'll continue to monitor this and will report if I learn anything new. I'd suggest not using this firmware for flight until the problem is understood..

Andy

[Andy[_1_]]

Changed to knob at right orientation. Waited for ADS-B target to be displayed. ADS-B target(s) displayed ok. While ADS-B target displayed, selected knob at bottom orientation. Immediately entered reset loop.

Andy

[Luke Szczepaniak]

On 08/11/2013 4:17 PM, Andy wrote:
> Changed to knob at right orientation. Waited for ADS-B target to be displayed. ADS-B target(s) displayed ok. While ADS-B target displayed, selected knob at bottom orientation. Immediately entered reset loop.
>
> Andy
>


I did my first flight with display fw 3.2.1 (portrait orientation) on
Saturday. After about two hours the display went into the cycle mode as
describe above for a few minutes, it then stopped cycling and resumed
normal operation. The PowerFLARM core (fw 3.31) did not cycle, just the
display.

Luke

[Dan Daly[_2_]]

I upgraded to Butterfly display 3.2.1 last week, with current Core firmware 3.00 (according to the PowerFLARM US website). I have checked connections, re-downloaded the update, re-inserted it IAW the normal procedure, and I get the cycling problem reported above (3 flights, about 14 hours of flying).. 3 other FLARM equipped aircraft say they see me properly, and I intermittently see them (when it cycles through that screen). I have been in contact with my dealer, and Butterfly, and they are investigating. For those who wonder what the 'cycling' looks like, I posted a you tube video, which I sent the link for to the factory: http://www.youtube.com/watch?v=u37YjIT9P-A.

After 3 e-mails back and forth to support, they suggest swapping displays with a known good one (a good idea, I don't know why that didn't occur to me); I will do that this weekend. Joachim is being very helpful from the AIR Store at Butterfly Avionics GmbH & Garrecht Avionik GmbH...

The following paragraph should probably be in another thread, but...
I guess I shouldn't have been surprised when the update to the PowerFLARM firmware was not announced to the registered users, or that it is unclear whether the 3.31 PowerFLARM update is for all users, just those in Europe, or only those with the Transponder issue (i.e., are there bug fixes in the change from 3.00 to 3.31?). If there was an 'announcement' here, I missed it and apologize in advance. The Core/Brick is a generally good product sorely lacking in communication to the users (one man's opinion). One comment - the Brick is bigger in volume than the Portable, and it takes a lot of space, which is confusing since it has less in it (that is, no batteries). If it could be re-engineered to be smaller vertically (may require antennae and the other connectors to be on opposite ends), it would be a much easier to install in gliders with very limited space behind the panel.

The display update fixes the clock font problem (thank you Butterfly), and the new fonts are much more readable; the new range selections are also good. So, an 'attaboy' goes to Butterfly for the changes and the announcement on ras, and once the cycling problem is addressed, all will be good with the display. I'll post the results of the swap here when it's done.

Dan
2D (Canada)

[Ramy]

I am aware of orhers who have the same issue. I have the in panel display and havent noticed this issue so maybe iy affects only the rectangular displays. Perhaps the most important enhancement in this version and the main reason to upgrade once the reboot issue is resolved is the short beep to alert whenever Powerflarm detects new traffic (screen switches from butterfly to radar). This significantly improves situational awarness.

Ramy

[Andy[_1_]]

What oriemtation is your display?

What target type was displayed when the reset loop was active?

Andy

[Dan Daly[_2_]]

Vertical. Displaying one FLARM target, one transponder, no ADS-B.

[Marc - Butterfly Avionics]

Dear All,

thanks a lot for your feedback. Sorry for the kind-of-late response, partly our team is on vacation and I also have been away for 3 days (eMail support is always available and Joachim and the team will answer all questions of course).

As a first workaround, please downgrade to version 3.2, download here:
- update software: http://www.butterfly-avionics.com/support/BD32.zip
- PF update file: http://www.butterfly-avionics.com/support/bfd_3_2.bfw

We guess that the issue only occurs in portrait mode in the external version of the display. We will release a bug-fix as soon as we have found the problem.

Sorry fore the trouble, best regards
Marc

[Marc - Butterfly Avionics]

Hi Guys,

we found the bug and it is resolved in the latest version. The bug appears in portrait mode and only with "feet" set up as units for relative altitude.

We are going to release the new version as soon as we hear positive results from our testers. If you wish to test this not released BETA version, please download it here:
- update software: http://www.butterfly-avionics.com/support/Butterfly_Display_3_2_2_2332.exe
- PF update file: http://www.butterfly.aero/support/bfd_3_2_2_2332.bfw

I look forward to receiving your feedback!

Best regards and thanks for the quick feedback and help in finding this
Marc

Disclaimer: The version posted is BETA (that is unfinished and untested software) and may not work as expected. Only test it if very familiar with your aircraft and in low traffic situations. If you experience an increase in workload due to testing, switch your collision warning unit off.

[[email protected]]

Hi Marc
Thanks for the quick follow-up.
I will test this weekend and report back.

ThreeUniform.

[Andy[_1_]]

Loaded beta. Observed FLARM, PCAS, and ADS-B targets in various combinations while in knob at bottom orientation. No resets seen.

Thanks,

Andy

[Andy[_1_]]

On Thursday, August 15, 2013 10:40:28 PM UTC-7, Andy wrote:
> Loaded beta. Observed FLARM, PCAS, and ADS-B targets in various combinations while in knob at bottom orientation. No resets seen. Thanks, Andy

p.s.
Why is plus sign blue (cyan?) but minus sign is black? Why would the sign be a different colour from the number it is associated with?


Andy

[Luke Szczepaniak]

Marc, I flew with 3.2.2 today, seems to work fine.

Luke

[[email protected]]

Same here.
3.2.2 seems to work fine (2 flights this weekend)
Thank Marc for the quick resolve.

With respect to the sign:
In my opinion, the plus sign is redundant.
It would be clearest if there was only a minus sign in case of negative altitude difference and no sign in case of positive altitude difference.

[Andy[_1_]]

"It would be clearest if there was only a minus sign in case of negative altitude difference and no sign in case of positive altitude difference. "

Those that developed the internationally recognized standards for CDTI and TCAS would not agree with you.

Andy

[Dan Daly[_2_]]

I haven't had the chance to fly with 3.2.2 yet, but I must say I am optimistic.

As for the plus/minus debate, my personal preference would be a little arrow pointing down if it is below me, and a little arrow pointing up if it's above me. I prefer arrows/needles to text.

Dan
2D (Canada)

[Luke Szczepaniak]

On 08/20/2013 9:58 AM, Dan Daly wrote:
> I haven't had the chance to fly with 3.2.2 yet, but I must say I am optimistic.
>
> As for the plus/minus debate, my personal preference would be a little arrow pointing down if it is below me, and a little arrow pointing up if it's above me. I prefer arrows/needles to text.
>
> Dan
> 2D (Canada)
>
>
>
10+ hrs without the issue reappearing.

Luke

[Andy[_1_]]

On Tuesday, August 20, 2013 6:58:30 AM UTC-7, Dan Daly wrote:
> I haven't had the chance to fly with 3.2.2 yet, but I must say I am optimistic. As for the plus/minus debate, my personal preference would be a little arrow pointing down if it is below me, and a little arrow pointing up if it's above me. I prefer arrows/needles to text. Dan 2D (Canada)

Arrows are used to indicate target climbing or descending. There are standards for presenting traffic data. Please let's not invent a completely new and conflicting user interface.

Andy

[John Carlyle]

On Tuesday, August 20, 2013 12:06:06 PM UTC-4, Andy wrote:
> On Tuesday, August 20, 2013 6:58:30 AM UTC-7, Dan Daly wrote:
>
> > I haven't had the chance to fly with 3.2.2 yet, but I must say I am optimistic. As for the plus/minus debate, my personal preference would be a little arrow pointing down if it is below me, and a little arrow pointing up if it's above me. I prefer arrows/needles to text. Dan 2D (Canada)
>
>
>
> Arrows are used to indicate target climbing or descending. There are standards for presenting traffic data. Please let's not invent a completely new and conflicting user interface.
>
>
>
> Andy

A question for PowerFLARM - I'm using a PowerFLARM brick (firmware 3.31) with a Butterfly 57 mm display (firmware 3.2.1). My alerts are 99% PCAS types.. While I get altitude difference and range, I do not see any climbing or descending arrows on the alert screen.

This behavior is unlike what my Zaon PCAS produced. Are there any plans to implement such arrows?

-John, Q3

[Dan Daly[_2_]]

On Thursday, August 15, 2013 11:27:27 AM UTC-4, Marc - Butterfly Avionics wrote:
> Hi Guys,
>
>
>
> we found the bug and it is resolved in the latest version. The bug appears in portrait mode and only with "feet" set up as units for relative altitude.
>
>
>
> We are going to release the new version as soon as we hear positive results from our testers. If you wish to test this not released BETA version, please download it here:
>
> - update software: http://www.butterfly-avionics.com/support/Butterfly_Display_3_2_2_2332.exe
>
> - PF update file: http://www.butterfly.aero/support/bfd_3_2_2_2332.bfw
>
>
>
> I look forward to receiving your feedback!
>
>
>
> Best regards and thanks for the quick feedback and help in finding this
>
> Marc
>
>
>
> Disclaimer: The version posted is BETA (that is unfinished and untested software) and may not work as expected. Only test it if very familiar with your aircraft and in low traffic situations. If you experience an increase in workload due to testing, switch your collision warning unit off.

I flew 2 flights, 3 hours, Butterfly display 3.2.2 beta, flarmnet america_0019bd.bfn, flarm firmware 3.31. Display vertical, in feet, and it worked perfectly. Problem solved.

Dan
2D

[[email protected]]

> A question for PowerFLARM - I'm using a PowerFLARM brick (firmware 3.31) with a Butterfly 57 mm display (firmware 3.2.1). My alerts are 99% PCAS types. While I get altitude difference and range, I do not see any climbing or descending arrows on the alert screen.

John,

thanks for the suggestion. I'll put it on our TODO list, but at the moment
we have more important issues.

Best
--Gerhard

[kirk.stant]

On Monday, August 26, 2013 6:50:50 AM UTC-5, wrote:

> thanks for the suggestion. I'll put it on our TODO list, but at the moment
>
> we have more important issues.
>
>
>
> Best
>
> --Gerhard

Gerhard, please look at the way the ZAON MRX displays PCAS targets (which I believe conforms with the standards for displaying traffic - Andy chime in?):

Distance (approximate), altitude difference (with leading + or -), and trend arrow up or down indicating whether the target is climbing or descending. Without a bearing to the threat, altitude and what it's doing becomes the most important data needed to find and avoid the threat, and all this data is available - it just needs to be displayed IN BIG DIGITS/SYMBOLS so us old guys can see it better!

I use a PF core in my glider and my MRX in club towplanes/gliders. I consider both to be essential bits of kit these days.


Kirk
66