At 15:40 05 January 2011, mattm wrote:
On Jan 5, 9:11=A0am, Andy wrote:
On Jan 4, 10:01=A0pm, mattm wrote:



On Jan 4, 3:07=A0pm, Andy wrote:

This may be of interst to those who have ordered PowerFLARM:

http://flarm.net/support/updates/index_en.html

This part is very worrying to me:

"When is the next scheduled service update due?
Since its creation FLARM has maintained scheduled updates,
initially
in a one year cycle, in 2006 a two year cycle, and last time in
2008
=
a
three year cycle. As the technology matures, we further extend
this
period to now four years, i.e. March 1, 2015. This is more
convenient
for some users, but slows down the innovation cycle, possibly
delayin=
g
the use in new applications."

Surely FLARM cannot believe that they will deliver in April fully
functional and bug free software for PowerFLARM. =A0Will owners
have
=
to
live with any bugs or missing functionality until 2015?

Is there some path by which PowerFLARM will be updated
independently
of the main FLARM firmware update schedule?

Andy

I'll also point out that the FLARM protocol is patented, and
supplied
to the vendors
as software that they include in their units. =A0The fact that
PowerFLARM will
come out with a stable and working FLARM protocol version is good
news.
The software that handles ADS-B and transponder traffic is separate
from
the supplied FLARM software indicated in the notice quoted above.
=A0If
there's
any problems in that part it can be updated immediately.

-- Matt

Are you suggesting that PowerFLARM uses a partitioned architecture, or
that that these "non FLARM" functions are handled by a separate
processor? =A0 If not, there will be one firmware load that supports
all
functions. =A0Of course it's reasonable to expect that the firmware
load
for PowerFLARM will be device specific.

I'm still hoping that someone close to the project will say what
functionality will be in the first delivery and what schedule is
planned for adding any functionality that is not included.

How are you so certain about the maturity of FLARM software. =A0Did
you
read the part about the significant changes to =A0RF protocols and the
difficulties in getting adequate in service test time? =A0It would not
surprise me bit if this RF change pulls resources away from PowerFLARM
new features.

Just in case anyone doubts my enthusiasm for PowerFLARM I'll go on
record as having ordered two. =A0That's why I would like more
information on what to expect when.

Andy

The terms of the FLARM patent are that FLARM supplies code to vendors
of FLARM hardware that implements the protocol. The code is meant to
be imbedded in the firmware for the hardware. Additional function
beyond
the protocol (user interface, ADS-B, etc.) is up to the individual
vendor.
When the FLARM protocol gets updated then Butterfly will make an
updated firmware available. They can also update the firmware
independently
if needed for some other reason.

The RF changes (the new frequency for the US?) is a very minor change.
FLARM already runs on different frequencies in different parts of the
world.

-- Matt
Can someone explain the differences between the Vaon MRX and the FLARM ?