PowerFLARM 2.60 beta available

[[email protected]]

Hi all,

Please see http://powerflarm.aero/index.php/en/knowledge-and-support

and the PowerFLARM forum: http://flarm.invisionzone.com/index.php?showforum=6

The new release adds notably IGC format logging and obstacle warnings (database
for Alps available). Please see the release notes for details. Note that
we'll charge a fee for future obstacle database updates.

A note on PCAS range issues:
We did identify and fix a bug which caused low PCAS range, especially
on Brick devices. Testing showed that for a number of devices, the problem
is fixed in 2.60. However, we also have reports where the problem persists.
We still decided to release 2.60 because of the added features.

If your PCAS range problems persist after the 2.60 update, please be in
touch on support (at) flarm.com, ideally providing an IGC log of
your flight!

For any questions or feedback, please use the forum or the above support
email address!

Best regards
--Gerhard

--
Dr. Gerhard Wesp
Development Manager, Avionics
FLARM Technology GmbH
Switzerland
CH-020.4.033.059-8

[Craig Funston[_2_]]

On Tuesday, October 30, 2012 3:03:02 AM UTC-7, wrote:
> Hi all,
>
>
>
> Please see http://powerflarm.aero/index.php/en/knowledge-and-support
>
>
>
> and the PowerFLARM forum: http://flarm.invisionzone.com/index.php?showforum=6
>
>
>
> The new release adds notably IGC format logging and obstacle warnings (database
>
> for Alps available). Please see the release notes for details. Note that
>
> we'll charge a fee for future obstacle database updates.
>
>
>
> A note on PCAS range issues:
>
> We did identify and fix a bug which caused low PCAS range, especially
>
> on Brick devices. Testing showed that for a number of devices, the problem
>
> is fixed in 2.60. However, we also have reports where the problem persists.
>
> We still decided to release 2.60 because of the added features.
>
>
>
> If your PCAS range problems persist after the 2.60 update, please be in
>
> touch on support (at) flarm.com, ideally providing an IGC log of
>
> your flight!
>
>
>
> For any questions or feedback, please use the forum or the above support
>
> email address!
>
>
>
> Best regards
>
> --Gerhard
>
>
>
> --
>
> Dr. Gerhard Wesp
>
> Development Manager, Avionics
>
> FLARM Technology GmbH
>
> Switzerland
>
> CH-020.4.033.059-8

Thanks Gerhard and the FLARM team.

Craig

[bumper[_4_]]

Likewise, thanks Gerhard.

I note that in the 2.60 download and manual .pdf, you are referring to the "brick" as the "core". Guess the terms are interchangable.

best,

bumper

[[email protected]]

Gerhard,

Thanks so much for the update. I flew with it on Sunday and my PCAS range when from .9nm to over 4 nm.

John

[[email protected]]

> I note that in the 2.60 download and manual .pdf, you are referring to the "brick" as the "core". Guess the terms are interchangable.

That's correct, yes. Consequence of a naming decision a bit late
in the development process...

Best
--Gerhard

[David Reitter]

On Tuesday, October 30, 2012 6:03:02 AM UTC-4, wrote:

> on Brick devices. Testing showed that for a number of devices, the problem
> is fixed in 2.60. However, we also have reports where the problem persists.

May I say that your responsiveness to the bug reports and your postings on this newsgroup make me much more likely to buy a PowerFlarm for the 2013 season.
(Still waiting for the logger!)

Smart renaming decision.

[Karl Kunz[_2_]]

The logger on the portable is functional (I don't know about the brick) with the 2.60 update. See the read file that comes with the 2.6 upgrade file.


On Thursday, November 1, 2012 10:47:59 AM UTC-7, David Reitter wrote:
> On Tuesday, October 30, 2012 6:03:02 AM UTC-4, wrote:
>
>
>
> > on Brick devices. Testing showed that for a number of devices, the problem
>
> > is fixed in 2.60. However, we also have reports where the problem persists.
>
>
>
> May I say that your responsiveness to the bug reports and your postings on this newsgroup make me much more likely to buy a PowerFlarm for the 2013 season.
>
> (Still waiting for the logger!)
>
>
>
> Smart renaming decision.

[Richard[_9_]]

On Thursday, November 1, 2012 1:30:55 PM UTC-7, Karl Kunz wrote:
> The logger on the portable is functional (I don't know about the brick) with the 2.60 update. See the read file that comes with the 2.6 upgrade file.
>
>
>
>
>
> On Thursday, November 1, 2012 10:47:59 AM UTC-7, David Reitter wrote:
>
> > On Tuesday, October 30, 2012 6:03:02 AM UTC-4, wrote:
>
> >
>
> >
>
> >
>
> > > on Brick devices. Testing showed that for a number of devices, the problem
>
> >
>
> > > is fixed in 2.60. However, we also have reports where the problem persists.
>
> >
>
> >
>
> >
>
> > May I say that your responsiveness to the bug reports and your postings on this newsgroup make me much more likely to buy a PowerFlarm for the 2013 season.
>
> >
>
> > (Still waiting for the logger!)
>
> >
>
> >
>
> >
>
> > Smart renaming decision.

Logger also works on the Brick.

Richard
www.craggyaero.com