PowerFlarm offers new Version, PowerFlarm Fusion Includes Many newstandard Features!

On Friday, 20 November 2020 at 16:10:40 UTC, Moshe Braner wrote:

"The firmware expiration date is not related to the aircraft specific
update cycle/date. The firmware will not expire as long as the firmware
is kept up-to-date according to the AMP. The expiry is always at least
12 months plus a few months of margin in the future when downloaded from
flarm.com."

"If the annual update cycle has expired but the firmware has not yet
expired, the device will in most cases continue to work until firmware
expiry."

"After the expiration date, the system will issue a continuous hard
warning and will not operate."

What is meant by firmware expiry date, since this is different from annual update expiry date?

Personally I don't intend to explore how my device behaves when not updated - I have it updated annually during the ARC process, although I did not know it was a requirement until I read that above from Martin Gregorie. I don't normally use the igc files from my device (igc files are uploaded by wifi from my LX9000 to SeeYou Cloud before I get out of the glider, so much more convenient), but I do extract and look at one at the start of the year to check that it is now using the latest firmware.

Incidentally, I did pay for the 2nd aerial option, and having a European device it should transmit as well as receive. I flew with that setup for two seasons before discovering that the 2nd aerial option was not active and the blade aerial on the bottom of the glider was not doing anything. The unit had been provided incorrect and was then sorted out by the UK supplier Navboys. To the best of my knowledge it now works - but I don't actually know whether it does.

To the best of my knowledge it now works - but I don't actually know whether it does.


Take a recent Flarm flight log and upload it to the Flarm analyzer. It will show you the results for the A and the B antenna...



http://flarm.com/support/tools-softw...ange-analyzer/

On Friday, 20 November 2020 at 19:51:05 UTC, wrote:
To the best of my knowledge it now works - but I don't actually know whether it does.
Take a recent Flarm flight log and upload it to the Flarm analyzer. It will show you the results for the A and the B antenna...

http://flarm.com/support/tools-softw...ange-analyzer/

I normally use igc files from my LX9000 which don't work with that tool. The LX range analyser does not give me the individual antenna information. I just tried a file from my PF which did have readings from the two antennae - good news. Less good was that one seemed to have very poor range - I don't know which antenna that was. However, the CARP file analyser (Continuous Analyzer of Radio Performance - new to me, apparently accumulates range data from multiple flights) did not appear to find any data, and I had to use the 'Classic Analyser' although my firmware version was 6.82 and the website said CARP should work from 6.80 - so I was only seeing data from one flight, whereas what I got from the LX9000 appeared to be from multiple flights and just showed decent all round reception (minimum of 10k all round).

On Friday, November 20, 2020 at 7:18:38 PM UTC-5, waremark wrote:
I normally use igc files from my LX9000 which don't work with that tool. The LX range analyser does not give me the individual antenna information. I just tried a file from my PF which did have readings from the two antennae - good news. Less good was that one seemed to have very poor range - I don't know which antenna that was. However, the CARP file analyser (Continuous Analyzer of Radio Performance - new to me, apparently accumulates range data from multiple flights) did not appear to find any data, and I had to use the 'Classic Analyser' although my firmware version was 6.82 and the website said CARP should work from 6.80 - so I was only seeing data from one flight, whereas what I got from the LX9000 appeared to be from multiple flights and just showed decent all round reception (minimum of 10k all round).

@waremark - a week ago, you said there did not appear to be any Continuous Range Analysis information in your .igc files. Did you activate the feature? Here's what I put in flarmcfg.txt (I comment it all so I have an idea of what is going on). Anything starting with # is a comment, starting with $ is an instruction to the FLARM.

###########
#Continuous Range Analysis
#must be turned on with reset command
#remove # to reset - load flarmcfg.txt to flarm
############
$PFLAN,S,RESET

If you leave your flarmcfg.txt file like this it resets the stats on every flight, so you have to make it a comment afterwards #$PFLAN,S,RESET then save flarmcfg.txt.

After putting flarmcfg.txt into my flarm, I move the file to a folder on the USB stick so I have it available and the FLARM doesn't 'see' it on following flights.

The information on this is from para 8.17 of FTD-012 Data Port Interface Control Document (ICD) 7.12 (not easily available I'll grant you).

Dan
2D

On Friday, 27 November 2020 at 16:20:03 UTC, Dan Daly wrote:
On Friday, November 20, 2020 at 7:18:38 PM UTC-5, waremark wrote:
I normally use igc files from my LX9000 which don't work with that tool..
.........
The LX range analyser does not apparently accumulates range data from multiple flights) did not appear to find any data,

@waremark - a week ago, you said there did not appear to be any Continuous Range Analysis information in your .igc files. Did you activate the feature? Here's what I put in flarmcfg.txt (I comment it all so I have an idea of what is going on). Anything starting with # is a comment, starting with $ is an instruction to the

The information on this is from para 8.17 of FTD-012 Data Port Interface Control Document (ICD) 7.12 (not easily available I'll grant you).

Dan
2D


Thanks, Mark

waremark wrote on 11/30/2020 5:39 AM:
On Friday, 27 November 2020 at 16:20:03 UTC, Dan Daly wrote:
On Friday, November 20, 2020 at 7:18:38 PM UTC-5, waremark wrote:
I normally use igc files from my LX9000 which don't work with that tool..
.........
The LX range analyser does not apparently accumulates range data from multiple flights) did not appear to find any data,

@waremark - a week ago, you said there did not appear to be any Continuous Range Analysis information in your .igc files. Did you activate the feature? Here's what I put in flarmcfg.txt (I comment it all so I have an idea of what is going on). Anything starting with # is a comment, starting with $ is an instruction to the

The information on this is from para 8.17 of FTD-012 Data Port Interface Control Document (ICD) 7.12 (not easily available I'll grant you).

Dan
2D


Thanks, Mark
If you use the FLARM configurtion tool, it will ask you if you want to reset the range data.

--
Eric Greenwell - Washington State, USA (change ".netto" to ".us" to email me)
- "A Guide to Self-Launching Sailplane Operation"
https://sites.google.com/site/motorg...ad-the-guide-1

On Fri, 20 Nov 2020 11:44:25 -0800, waremark wrote:

Personally I don't intend to explore how my device behaves when not
updated - I have it updated annually during the ARC process, although I
did not know it was a requirement until I read that above from Martin
Gregorie.

Mark, for at least the last 2-3 years my club's inspectors have verbally
checked when I'd last updated the FLARM firmware, but at my glider's most
recent annual (March 2020) I noticed it is now on the checklist.



--
--
Martin | martin at
Gregorie | gregorie dot org

"I think my experience would apply to almost any Schleicher glider - they all use essentially
the same fuselage, starting with the ASW24, which do not have carbon in the nose."

The fuselage mold may be the same, but the layup in newer gliders is carbon fiber.

I found a major improvement in range when I moved from a single antenna over the glareshield to dual antennas on the canopy sides of my ASW-27.

I did Range Analysis on six installations and documented the results in the 2019 Free Flight. Look for Antenna Placement:

http://sac.ca/index.php/en/free-flig...ight-vol-libre

George Haeh wrote on 11/20/2020 1:42 PM:
"I think my experience would apply to almost any Schleicher glider - they all use essentially
the same fuselage, starting with the ASW24, which do not have carbon in the nose."

The fuselage mold may be the same, but the layup in newer gliders is carbon fiber.

I found a major improvement in range when I moved from a single antenna over the glareshield to dual antennas on the canopy sides of my ASW-27.

I did Range Analysis on six installations and documented the results in the 2019 Free Flight. Look for Antenna Placement:

http://sac.ca/index.php/en/free-flig...ight-vol-libre

Are you certain the ASW27 has carbon fiber in the nose (the area besides the pilot's feet)? It
was designed at the same time as the ASH26E, which doesn't have any carbon in that area. Same
question for the ASW28, ASG29, etc - I'm wondering when/if the addition of carbon in the nose
began.


--
Eric Greenwell - Washington State, USA (change ".netto" to ".us" to email me)
- "A Guide to Self-Launching Sailplane Operation"
https://sites.google.com/site/motorg...ad-the-guide-1

There's talk the early 27s didn't have significant carbon fiber in the nose cone.

That the PowerFLARM range analysis with a single glareshield antenna in my later build 27 shows poor coverage convinces me there's carbon fiber below. Visual examination shows lots of black stuff in the nose cone.