PowerFLARM firmware v3.00 released (feature complete)

[FLARM]

This release is feature complete and includes IGC approved recording, update of remote display, Garmin TIS output and various performance enhancements.
The firmware is the same for both Portable and Core (new name for 'Brick') and is strongly recommended for all units.
For update file and release notes, please go to http://powerflarm.us/manuals-software-updates-and-release-notes/

While there, please also take your time to register your device to receive important announcements.

Stand by for information on how to purchase the ENL (Engine Noise Level) feature.

[Mike the Strike]

It's April 38th in Switzerland already?

;)

Mike

Seriously - that's great news!

[FLARM]

On Wednesday, May 8, 2013 9:44:50 PM UTC-7, Mike the Strike wrote:
> It's April 38th in Switzerland already?
>
>
>
> ;)
>
>
>
> Mike
>
>
>
> Seriously - that's great news!

It has been out a while, as release candidate.

[Andy[_1_]]

The release notes state "All US PowerFLARM are automatically licensed for:
* IGC approval (IGC)
* Second FLARM antenna connection (RFB)

Will you please confirm that all US PowerFLARM are automatically licensed for Garmin TIS. I have used this feature and wish to continue to use it.

thanks

Andy

[Craig R.]

I just upgraded my POWERFlarm software to ver. 3.0 on my PF core (brick) and then my 57mm Butterfly display to ver. 3.1 through the PF. The positive is that both worked. The negative would fill volumes. My only comment is for the product guys; we can’t read your minds! Spell it out when writing installation instructions.

from PF 3.0 notes:
Firmware, licence and/or obstacle database update on Core:
– Copy relevant file(s) (xxx.FW, yyy.LIC, zzz.OB2) to USB stick.
– Connect stick to Core.
– Switch on system.
– Verify status LED flashes RED/GREEN.
– Wait until LED turns solid GREEN (or RED in case of no GPS reception).

Seems simple enough.

First. I downloaded the PF zip file to my computer and extracted it. I copied only the xxx5648.fw file to a new 16 GB memory stick. Stuck the stick in my core and powered up. Nothing. The core light went from orange to green. No green/red upload indicators. I powered down and detached my 57mm Butterfly display. I had issues last time upgrading my PF software and the attached display caused the problem. Inserted stick, powered up... nada. Redid everything from scratch. Nothing. Ok, getting ****ed. Took out an old 256 MB memory stick, copied the files to it, and IT WORKED. The difference besides memory size? The first memory stick was formatted to NTFS and the second was FAT32. I’ve looked around to see if there are any issues stated about the USB memory format or stick size. I didn’t find any. Now, since most of us are not tech geeks, this issue should be one of the line items in the installation instructions!

Second, the upload only worked with the 57mm BF display disconnected (another line item to add to the installation instructions).

Third, after the installation, I inspected the memory stick and the core had downloaded a FLARMcfg file on it. I checked it out to see the data with the new range limits. Interesting.

Fourth. Time for the Butterfly software upgrade. I went to the Butterfly website, Butterfly Avionics, and looked under their Support tab.

From the Butterfly display manual:
Butterfly firmware/FlarmNET update on Core:
1. Copy Butterfly firmware (.bfw) and/or flarmnet (.bfn) to a USB stick.
2. Connect stick to Core.
3. Switch on system with BF display knob pressed.
4. Verify BF display goes into UPDATE MODE with 'WAITING', then 'LOADING'.
5. Wait until BF display restarts (can take up to two minutes).

Three options under BF display.
Firmware version 3.1 / Update file for POWERFlarm / Changelog 3.1
Now it seems pretty obvious to use the Update file for POWERFlarm. Click on it and you get a text file. I was not expecting the .bfw to be a txt file, but anyway, I tried saving it and my browser wants to save the link. Butterfly, why not have the file download and properly save on our computer as a .bfw file (zip file at least) when we click it? Hmmm. For those interested, here is the link ( http://www.butterfly.aero/support/bfd_3_1.bfw ) I do a “save as” through my browser and get the file properly saved as a .bfw file. I copied the file on my memory stick. Following the above instructions, the file loads properly in a minute or two.

Lastly, remembering the cfg file I saw, I decided to upload a new one with my current information including my .igc file info. Go here if you want it done for you. http://www.butterfly-avionics.com/tools/pf_core_config.php Upload as per the PF manual.

All in all, a fairly simple process if properly instructed. It baffles me why these instructions aren’t done in a very detailed step by step method (go there, do this) with precise wording instead of tossing out a couple of steps and letting the customer figure out details that you assume we know. Remember, most of us are NOT engineers or tech geeks and have no desire to be one. Spend the extra 30 minutes and write it properly!

[[email protected]]

Craig,

thanks for your feedback. I'll make sure a note about USB sticks goes
into the manual. FWIW, about 95% of sticks we tested with work, many
of the remaining 5% being 'USB 3' sticks.

Forwarding your message to Butterfly as well.

Best
--Gerhard

[[email protected]]

> Will you please confirm that all US PowerFLARM are automatically licensed for Garmin TIS. I have used this feature and wish to continue to use it.

Yes, they are. The note on the website is incomplete.

Best
--Gerhard

[Craig R.]

> thanks for your feedback. I'll make sure a note about USB sticks goes
> into the manual. FWIW, about 95% of sticks we tested with work, many
> of the remaining 5% being 'USB 3' sticks.

> --Gerhard


Gerhard, This precisely makes my point. If there are approximately 5% failures in the upgrade process from not using a proper USB stick, then the instructions / manual should state what exact stick to use.
Example only (I don't have a clue what the actual specific hardware minimums are):
Portable USB memory for use with POWERFlarm
-2.0 compatibility only
-formatted only FAT or FAT32
-size no larger than xxx MB/GB

Leaving the information generic and incomplete makes for some upgrade failures and lots of frustration for customers that didn't have to happen. This extends beyond software upgrades to hardware installation. Why not eliminate the failures by being detailed on what will work and how to do it? Your customer will appreciate it! Regards, Craig

[Renny[_2_]]

On Thursday, May 9, 2013 7:50:23 PM UTC-6, Craig R. wrote:
> I just upgraded my POWERFlarm software to ver. 3.0 on my PF core (brick) and then my 57mm Butterfly display to ver. 3.1 through the PF. The positive is that both worked. The negative would fill volumes. My only comment is for the product guys; we can’t read your minds! Spell it out when writing installation instructions.
>
>
>
> from PF 3.0 notes:
>
> Firmware, licence and/or obstacle database update on Core:
>
> – Copy relevant file(s) (xxx.FW, yyy.LIC, zzz.OB2) to USB stick.
>
> – Connect stick to Core.
>
> – Switch on system.
>
> – Verify status LED flashes RED/GREEN.
>
> – Wait until LED turns solid GREEN (or RED in case of no GPS reception)..
>
>
>
> Seems simple enough.
>
>
>
> First. I downloaded the PF zip file to my computer and extracted it. I copied only the xxx5648.fw file to a new 16 GB memory stick. Stuck the stick in my core and powered up. Nothing. The core light went from orange to green. No green/red upload indicators. I powered down and detached my 57mm Butterfly display. I had issues last time upgrading my PF software and the attached display caused the problem. Inserted stick, powered up... nada. Redid everything from scratch. Nothing. Ok, getting ****ed. Took out an old 256 MB memory stick, copied the files to it, and IT WORKED. The difference besides memory size? The first memory stick was formatted to NTFS and the second was FAT32. I’ve looked around to see if there are any issues stated about the USB memory format or stick size. I didn’t find any. Now, since most of us are not tech geeks, this issue should be one of the line items in the installation instructions!
>
>
>
> Second, the upload only worked with the 57mm BF display disconnected (another line item to add to the installation instructions).
>
>
>
> Third, after the installation, I inspected the memory stick and the core had downloaded a FLARMcfg file on it. I checked it out to see the data with the new range limits. Interesting.
>
>
>
> Fourth. Time for the Butterfly software upgrade. I went to the Butterfly website, Butterfly Avionics, and looked under their Support tab.
>
>
>
> From the Butterfly display manual:
>
> Butterfly firmware/FlarmNET update on Core:
>
> 1. Copy Butterfly firmware (.bfw) and/or flarmnet (.bfn) to a USB stick.
>
> 2. Connect stick to Core.
>
> 3. Switch on system with BF display knob pressed.
>
> 4. Verify BF display goes into UPDATE MODE with 'WAITING', then 'LOADING'..
>
> 5. Wait until BF display restarts (can take up to two minutes).
>
>
>
> Three options under BF display.
>
> Firmware version 3.1 / Update file for POWERFlarm / Changelog 3.1
>
> Now it seems pretty obvious to use the Update file for POWERFlarm. Click on it and you get a text file. I was not expecting the .bfw to be a txt file, but anyway, I tried saving it and my browser wants to save the link. Butterfly, why not have the file download and properly save on our computer as a .bfw file (zip file at least) when we click it? Hmmm. For those interested, here is the link ( http://www.butterfly.aero/support/bfd_3_1.bfw ) I do a “save as” through my browser and get the file properly saved as a .bfw file. I copied the file on my memory stick. Following the above instructions, the file loads properly in a minute or two.
>
>
>
> Lastly, remembering the cfg file I saw, I decided to upload a new one with my current information including my .igc file info. Go here if you want it done for you. http://www.butterfly-avionics.com/tools/pf_core_config.php Upload as per the PF manual.
>
>
>
> All in all, a fairly simple process if properly instructed. It baffles me why these instructions aren’t done in a very detailed step by step method (go there, do this) with precise wording instead of tossing out a couple of steps and letting the customer figure out details that you assume we know. Remember, most of us are NOT engineers or tech geeks and have no desire to be one. Spend the extra 30 minutes and write it properly!

Craig,
Thanks for all of your help on this! It will help many other folks in loading up the new FW. One question on this statement you made....

"Lastly, remembering the cfg file I saw, I decided to upload a new one with my current information including my .igc file info. Go here if you want it done for you. http://www.butterfly-avionics.com/tools/pf_core_config.php Upload as per the PF manual."

Is the cfg file required in order to successfully load the 3.0 FW or is it optional?

Thanks again for all of your help and taking the time to write up this procedure.
Renny

[Craig R.]

> Is the cfg file required in order to successfully load the 3.0 FW or is it optional?

> Renny

Nope. Uploaded PF 3.0 with the (real) old cfg file on the core. I did the new cfg file after both upgrades were completed. Haven't flown yet, but I'm comfortable all will be ok.

Craig

[Renny[_2_]]

On Friday, May 10, 2013 3:26:21 PM UTC-6, Craig R. wrote:
> > Is the cfg file required in order to successfully load the 3.0 FW or is it optional?
>
>
>
> > Renny
>
>
>
> Nope. Uploaded PF 3.0 with the (real) old cfg file on the core. I did the new cfg file after both upgrades were completed. Haven't flown yet, but I'm comfortable all will be ok.
>
>
>
> Craig

Great..I was able to load my portable fine yesterday and tomorrow we will load a brick/core....
Thanks again - Renny

[Sean F (F2)]

How do you add your pilot data for the logger. I see no obvious options in the UI.

Sean

[Paul Remde]

Hi Sean,

I believe you are using a PowerFLARM Portable - right? I just looked
through the menus in a PowerFLARM Portable and I don't see any way to set
the pilot data for the logger using the user interface. Therefore you would
need to enter that data into a configuration file, put the file onto a
microSD card, and power-up the Portable with the card installed. Ideally
the configuration file would be the only file in the root directory of the
microSD card.

The easiest way to create the configuration file is to use the web tool
here:
http://www.butterfly-avionics.com/index.php/en/products/powerflarm-en/powerflarm-core-config-en
The web site says the configuration files are for PowerFLARM Core units, but
the files also work with PowerFLARM Portable units.

Best Regards,

Paul Remde
Cumulus Soaring, Inc.
_______________________________________

"Sean F (F2)" wrote in message
...

How do you add your pilot data for the logger. I see no obvious options in
the UI.

Sean

[[email protected]]

On Sunday, May 12, 2013 9:21:36 AM UTC-5, Paul Remde wrote:
> Hi Sean,
>
>
>
> I believe you are using a PowerFLARM Portable - right? I just looked
>
> through the menus in a PowerFLARM Portable and I don't see any way to set
>
> the pilot data for the logger using the user interface. Therefore you would
>
> need to enter that data into a configuration file, put the file onto a
>
> microSD card, and power-up the Portable with the card installed. Ideally
>
> the configuration file would be the only file in the root directory of the
>
> microSD card.
>
>
>
> The easiest way to create the configuration file is to use the web tool
>
> here:
>
> http://www.butterfly-avionics.com/index.php/en/products/powerflarm-en/powerflarm-core-config-en
>
> The web site says the configuration files are for PowerFLARM Core units, but
>
> the files also work with PowerFLARM Portable units.
>
>
>
> Best Regards,
>
>
>
> Paul Remde
>
> Cumulus Soaring, Inc.
>
> _______________________________________
>
>
>
> "Sean F (F2)" wrote in message
>
> ...
>
>
>
> How do you add your pilot data for the logger. I see no obvious options in
>
> the UI.
>
>
>
> Sean

Paul and Sean,

I created the config file as you suggested and the pilot data is all in igc-file. Uploaded yesterday's flight to OLC from PFlarm and got green dots for security, thank you Urs(3.0 firm ware). Great day to test the logger yesterday here in Chicago, 337 mi in 5h15!

Herb

[[email protected]]

Thanks for the instructions on updating core and butterfly. All went well with core but when I restarted with display button pressed, display went to "waiting" but never went to " loading". Any suggestions?

[Paul Remde]

Hi,

Make sure the filename and extension are correct. The extension seems to get
changed during the download.

Best regards,

Paul Remde
_________________

wrote in message
...

Thanks for the instructions on updating core and butterfly. All went well
with core but when I restarted with display button pressed, display went to
"waiting" but never went to " loading". Any suggestions?

[FLARM]

Updated US / AUS manuals are now available at:
http://powerflarm.us/manuals-software-updates-and-release-notes/

[Matt Herron Jr.]

Last weekend I flew with the PF core upgraded to 3.00 and an Oudie upgraded to 4.40.004. A V7 connects the two together (Firmware 2.02). All the flight stuff worked fine, but I still got the error -9 when attempting to download the flight from the core via the Oudie ConnectMe program.

ConnectMe recognizes the PF and displays it SN, Vers. No., etc. but will not download the flight file. It is really inconvenient to have to plug in a USB stick under the hood and try to see the light on the brick flashing. I guess I could unscrew my glare shield after every flight, but I don't want to.

Both Naviter and PowerFlarm think this should work, and both companies have error logs from when it doesn't. It would be wonderful if they could get it working! Has anyone else had any luck?

Thanks in advance,

Matt

[Paul Remde]

Hi Matt,

I hear what you're saying, and I do hope they get it working soon... but I
sincerely think you're going about it the hard, slow way. A serial flight
log download takes minutes. Using a USB Flash Drive takes seconds. The
PowerFLARM Core (Brick) units were supplied with USB extension cables
designed for panel mounting. If you use a USB Flash drive that has a
built-in LED that flashes to indicate when it is working (mine is a Sony) -
I really think you'll be all set.

A friend has proposed the idea of using a fiber-optic cable to bring the
Core's LED out to the panel. I don't know whether or not that will work,
but it is an interesting idea. He's looking into it.

Best Regards,

Paul Remde
Cumulus Soaring, Inc.
______________________________________________

"Matt Herron Jr." wrote in message
...

Last weekend I flew with the PF core upgraded to 3.00 and an Oudie upgraded
to 4.40.004. A V7 connects the two together (Firmware 2.02). All the
flight stuff worked fine, but I still got the error -9 when attempting to
download the flight from the core via the Oudie ConnectMe program.

ConnectMe recognizes the PF and displays it SN, Vers. No., etc. but will not
download the flight file. It is really inconvenient to have to plug in a
USB stick under the hood and try to see the light on the brick flashing. I
guess I could unscrew my glare shield after every flight, but I don't want
to.

Both Naviter and PowerFlarm think this should work, and both companies have
error logs from when it doesn't. It would be wonderful if they could get it
working! Has anyone else had any luck?

Thanks in advance,

Matt

[Matt Herron Jr.]

Paul,

While it is certainly easier to "go with the flow", I find that very little of significance is accomplished that way. The better solution for file transfer is via my Oudie where I can pick only the file I want transferred, and know when it is completed without looking under the hood for a blinking light to stop. While it might be harder in the short run to pursue this path, it is the "right" thing to do, and I know the manufactures of both products will rise to the challenge with a little encouragement.

We need this solution guys. PowerFlarm is mature enough to start getting rid of the bandaids now. Great Job!, and I look forward to the usability improvements that will make it a pleasure to use, both in the air and on the ground.

Matt

[Dave Nadler]

On Wednesday, May 15, 2013 11:43:05 PM UTC-4, Matt Herron Jr. wrote:
> I guess I could unscrew my glare shield after every flight,
> but I don't want to.

Get one of these:
http://www.frontx.com/pro/p1011_036.html

Oudie will hopefully display (nearly instantaneous)
IGC file download progress information.

Hope that helps,
Best Regards, Dave

[Andrzej Kobus]

On May 16, 8:10*am, Dave Nadler > wrote:
> On Wednesday, May 15, 2013 11:43:05 PM UTC-4, Matt Herron Jr. wrote:
> > I guess I could unscrew my glare shield after every flight,
> > but I don't want to.
>
> Get one of these:http://www.frontx.com/pro/p1011_036.html
>
> Oudie will hopefully display (nearly instantaneous)
> IGC file download progress information.
>
> Hope that helps,
> Best Regards, Dave

I have a brick and I still can't update a config file or firmware with
this cable because I don't see the LED on the unit. I actually need to
take off the canopy. Is there solution to this problem coming?
Shouldn't a display show this LED status through the communication
protocol. This a big pain in the rear end.

[Luke Szczepaniak]

Andrzej et all..

Turn off the flarm, plug in the USB stick, turn on the flarm, wait for
the display to go to the standard view (butterfly with gps and tx boxes)
- the update is done, pull out the USB go fly and have fun. No need to
watch the LED. If you want to verify the update was completed, turn off
the flarm, turn it back on and hit the display knob during boot up to
get flarm info. Installing the panel mounted USB extension makes life
even easier.

Don't let the tech drive you nuts, you will enjoy flying a lot more :-)

Luke

[Eric Greenwell[_4_]]

Andrzej Kobus wrote, On 5/16/2013 5:58 AM:
> On May 16, 8:10 am, Dave Nadler > wrote:
>> On Wednesday, May 15, 2013 11:43:05 PM UTC-4, Matt Herron Jr. wrote:
>>> I guess I could unscrew my glare shield after every flight,
>>> but I don't want to.
>>
>> Get one of these:http://www.frontx.com/pro/p1011_036.html
>>
>> Oudie will hopefully display (nearly instantaneous)
>> IGC file download progress information.
>>
>> Hope that helps,
>> Best Regards, Dave
>
> I have a brick and I still can't update a config file or firmware with
> this cable because I don't see the LED on the unit. I actually need to
> take off the canopy. Is there solution to this problem coming?
> Shouldn't a display show this LED status through the communication
> protocol. This a big pain in the rear end.

Firmware _updates_ are rare, so that is a small inconvenience. Updating
the config file doesn't need any LED watching. It's not an "update", it
just reads a tiny file into the box. Just leave the USB stick in the
unit all the time, and it will read the file automatically in a fraction
of second as it starts up - no need to monitor it.

--
Eric Greenwell - Washington State, USA (change ".netto" to ".us" to
email me)
- "Transponders in Sailplanes - Feb/2010" also ADS-B, PCAS, Flarm
http://tinyurl.com/yb3xywl

[Dan Daly[_2_]]

I use this panel pass-through, and it works well: "NEUTRIK - USB A/B Pass Thru Black D-Type". I have a usb stick with a flashing LED to indicate it is accessing.

I would be nice if there were a menu item, perhaps below the one where you set it to download IGC files, where you could end recording and then download IGC files to the USB stick without cycling power. I have to turn off everything, then boot my 7007 (provides power to the Core) in order to get the IGC file out.

I am happy that I can transfer declarations from my Dell Streak/XC Soar via IOIO to the Core - very handy.

[Luke Szczepaniak]

On 05/16/2013 10:52 AM, Dan Daly wrote:
> I use this panel pass-through, and it works well: "NEUTRIK - USB A/B Pass Thru Black D-Type". I have a usb stick with a flashing LED to indicate it is accessing.
>
> I would be nice if there were a menu item, perhaps below the one where you set it to download IGC files, where you could end recording and then download IGC files to the USB stick without cycling power. I have to turn off everything, then boot my 7007 (provides power to the Core) in order to get the IGC file out.
>
> I am happy that I can transfer declarations from my Dell Streak/XC Soar via IOIO to the Core - very handy.
>
There is an IGC flight download menu item in the new display firmware,
it seems to work fine.

Luke

[Dave Nadler]

On Thursday, May 16, 2013 8:58:46 AM UTC-4, Andrzej Kobus wrote:
> I have a brick and I still can't update a config file or firmware with
> this cable because I don't see the LED on the unit. I actually need to
> take off the canopy. Is there solution to this problem coming?
> Shouldn't a display show this LED status through the communication
> protocol. This a big pain in the rear end.

Stop whining and follow the instructions.
Yes, display units report the status of software updates,
IGC file downloads, etc...

Really now...

[[email protected]]

On Thursday, May 16, 2013 10:11:09 AM UTC-5, Dave Nadler wrote:
> On Thursday, May 16, 2013 8:58:46 AM UTC-4, Andrzej Kobus wrote:
>
> > I have a brick and I still can't update a config file or firmware with
>
> > this cable because I don't see the LED on the unit. I actually need to
>
> > take off the canopy. Is there solution to this problem coming?
>
> > Shouldn't a display show this LED status through the communication
>
> > protocol. This a big pain in the rear end.
>
>
>
> Stop whining and follow the instructions.
>
> Yes, display units report the status of software updates,
>
> IGC file downloads, etc...
>
>
>
> Really now...

Uh, Oh, Dave is getting angry! However, I agree with him. Downloading a flight trace is so easy. Turn off the brick, insert usb-stick, turn it back on and wait until the normal butterfly thingy is displayed with green status boxes. The unit will only download files that are not already on the stick and it beats the 4800 baud rate that I get with ConnectMe out of my 302 by a factor of 20.
Herb

[kirk.stant]

On Thursday, May 16, 2013 5:32:32 PM UTC+2, wrote:

>
> Uh, Oh, Dave is getting angry! However, I agree with him. Downloading a flight trace is so easy. Turn off the brick, insert usb-stick, turn it back on and wait until the normal butterfly thingy is displayed with green status boxes. The unit will only download files that are not already on the stick and it beats the 4800 baud rate that I get with ConnectMe out of my 302 by a factor of 20.
>
> Herb

No, Dave is getting frustrated, and I agree with him! If you upgrade the display software and look at the stupid thing - IT HAS AN IGC FILE DOWNLOAD FEATURE! So stick in the free USB extender, route it so you can reach it without taking your glider apart, then after your incredible flight, WITHOUT CYCLING THE PFB POWER, stick in your fancy thumb drive with the pretty lights, go to the igc file download menu, and get your stinking file so you can rush to post it on OLC to the amazement of the unwashed masses and adoration of the breathless groupies...

I would say RTFM, but of course the M isn't quite up to date yet...

Sheesh, don't you guys know any 14 year olds?

Kirk
66

[[email protected]]

> A friend has proposed the idea of using a fiber-optic cable to bring the
>
> Core's LED out to the panel. I don't know whether or not that will work,
>
> but it is an interesting idea. He's looking into it.

Paul, I've done this. You need to get good quality fiber optic multi-strand and it works pretty well. There is some loss but under a shadowed part of the panel, you can see it just fine. The trick is to make a coupling for the fiber at the LED end.
Darren

[Dave Nadler]

On Thursday, May 16, 2013 12:11:24 PM UTC-4, wrote:
> > A friend has proposed the idea of using a fiber-optic cable to bring the
> > Core's LED out to the panel. I don't know whether or not that will work,
> > but it is an interesting idea. He's looking into it.
>
> Paul, I've done this. You need to get good quality fiber optic
> multi-strand and it works pretty well. There is some loss but under
> a shadowed part of the panel, you can see it just fine. The trick is
> to make a coupling for the fiber at the LED end.
>
> Darren

Guys, you really don't need the LEDs.
Any display device *should* echo the relevant status messages.

[Dan Daly[_2_]]

>
> No, Dave is getting frustrated, and I agree with him! If you upgrade the display software and look at the stupid thing - IT HAS AN IGC FILE DOWNLOAD FEATURE! So stick in the free USB extender, route it so you can reach it without taking your glider apart, then after your incredible flight, WITHOUT CYCLING THE PFB POWER, stick in your fancy thumb drive with the pretty lights, go to the igc file download menu, and get your stinking file so you can rush to post it on OLC to the amazement of the unwashed masses and adoration of the breathless groupies...
>
> I would say RTFM, but of course the M isn't quite up to date yet...>
>
> Sheesh, don't you guys know any 14 year olds?
>
> Kirk
>
> 66

AFAIK, I have updated to the latest of both display and core fw. There is a menu item for "IGC Download" - On and Off. I have it on. My understanding is not that this forces a download, rather, that it has the core send the file to the USB stick or not. The new manual (3.0 US) says
quote
To read out the flights to the USB stick:
ï‚· Switch CORE OFF after flight (allow at least 2 minutes after landing to avoid losing data).
ï‚· Connect USB stick to CORE.
ï‚· Switch CORE ON.
ï‚· Observe Status LED (flashing RED/GREEN) or progress indication on display to verify flights are being copied.
ï‚· Wait until system has started up normally after copying flights.
ï‚· Disconnect USB stick.

Some displays or flight computers allow reading out flights without switching the CORE OFF after the flight. Please refer to your system’s documentation for details.

PowerFLARM CORE-Manual 3.00 US, page 15ff

unquote.

I did RTFM. If it's accurate, you're wrong; I have tried what you suggest and it does not work - the IGC files do not appear on my stick unless I cycle the power.

Thank you for your wise words; they really helped.

[Dave Nadler]

On Thursday, May 16, 2013 4:29:39 PM UTC-4, Dan Daly wrote:
> I did RTFM. If it's accurate, you're wrong; I have tried
> what you suggest and it does not work - the IGC files do
> not appear on my stick unless I cycle the power.

Put the cursor on the "download IGC" choice and push the button.
Works great, Kirk is absolutely right.
This *should* be in the Butterfly documentation;
no idea if that has been updated.

[Mike the Strike]

There's a general rule that the best products are intuitive to use and don't need an instruction manual to operate, at least for basic functions. That's why Apple is so successful - ever read an iPhone or iPad manual - I think not!!

In Flarm's case, the product is so complex and counter-intuitive that you technical wonks can't even agree what the manual says! What chance do I have of getting mine installed and working by the start of Region 9?

Mike

[Richard[_9_]]

On Thursday, May 16, 2013 3:48:58 PM UTC-7, Mike the Strike wrote:
> There's a general rule that the best products are intuitive to use and don't need an instruction manual to operate, at least for basic functions. That's why Apple is so successful - ever read an iPhone or iPad manual - I think not!! In Flarm's case, the product is so complex and counter-intuitive that you technical wonks can't even agree what the manual says! What chance do I have of getting mine installed and working by the start of Region 9? Mike

Mike,

I will be there to help you. So chances are fair to good.

Richard
www.craggyaero.com

[Dave Nadler]

On Thursday, May 16, 2013 6:48:58 PM UTC-4, Mike the Strike wrote:
> There's a general rule that the best products are intuitive to use
> and don't need an instruction manual to operate

And you really think you should be able to install a complex radio
product in an aircraft without RTFM ? Yikes.
We have met the enemy...

[Andrzej Kobus]

On May 16, 1:58*pm, Dave Nadler > wrote:
> On Thursday, May 16, 2013 12:11:24 PM UTC-4, wrote:
> > > A friend has proposed the idea of using a fiber-optic cable to bring the
> > > Core's LED out to the panel. *I don't know whether or not that will work,
> > > but it is an interesting idea. *He's looking into it.
>
> > Paul, I've done this. You need to get good quality fiber optic
> > multi-strand and it works pretty well. *There is some loss but under
> > a shadowed part of the panel, you can see it just fine. *The trick is
> > to make a coupling for the fiber at the LED end.
>
> > Darren
>
> Guys, you really don't need the LEDs.
> Any display device *should* echo the relevant status messages.

The designers of PowerFlarm must have intended to put this LED on a
Christmas tree but they confused it with PowerFlarm brick and now we
have LED there that is not needed. Great!

[kirk.stant]

It's too bad the PowerFLARM display doesn't have an attitude indicator on it and a direct link to an online glider-for-sale site - then we could have a really good thread going!

Seriously, it can be frustrating, but if you ensure you have the correct files for updating the PF and display - making SURE you check the file name because Windows 7 WILL try to stick a .txt on it - the install is easy.

And if you have a Butterfly External display (the one that comes standard with the PF Core), you will no longer have to power cycle the PF to download.

And for Mike Stringfellow - With an Oudie, it is literally plug and play. The hardest part of installing the Flarm system is finding a place for all the antennas!

Let's all go flying!

Kirik
66

[[email protected]]

Am Donnerstag, 16. Mai 2013 05:43:05 UTC+2 schrieb Matt Herron Jr.:
> Last weekend I flew with the PF core upgraded to 3.00 and an Oudie upgraded to 4.40.004. A V7 connects the two together (Firmware 2.02). All the flight stuff worked fine, but I still got the error -9 when attempting to download the flight from the core via the Oudie ConnectMe program.

Matt,

I don't know Oudie very well, but PowerFLARM does not support flight download via
the RS232 connection. We might add that at a laster stage, but it's *not*
on our top priority list right now. USB download is faster and modern displays
will allow you to initiate a download after the flight without power cycling
PowerFLARM (BF 3.1 display). The Oudie folks might want to implement that as well *hint hint*.

Progress indication is also implemented in newer display versions, so the
PowerFLARM Core LED becomes less important.

If you have no access to the USB slot, I'd suggest an extension cable.

Hope you guys are getting some good lift!

Best
--Gerhard (FLARM dev mgr)

[Eric Greenwell[_4_]]

Mike the Strike wrote, On 5/16/2013 3:48 PM:
> There's a general rule that the best products are intuitive to use
> and don't need an instruction manual to operate, at least for basic
> functions. That's why Apple is so successful - ever read an iPhone
> or iPad manual - I think not!!
>
> In Flarm's case, the product is so complex and counter-intuitive that
> you technical wonks can't even agree what the manual says! What
> chance do I have of getting mine installed and working by the start
> of Region 9?

You likely had decades of experience using computers before you
encountered an iPad. Collision avoidance systems - not so many.

--
Eric Greenwell - Washington State, USA (change ".netto" to ".us" to
email me)
- "Transponders in Sailplanes - Feb/2010" also ADS-B, PCAS, Flarm
http://tinyurl.com/yb3xywl

[Eric Greenwell[_4_]]

Andrzej Kobus wrote, On 5/16/2013 4:59 PM:
> On May 16, 1:58 pm, Dave Nadler > wrote:
>> On Thursday, May 16, 2013 12:11:24 PM UTC-4, wrote:
>>>> A friend has proposed the idea of using a fiber-optic cable to bring the
>>>> Core's LED out to the panel. I don't know whether or not that will work,
>>>> but it is an interesting idea. He's looking into it.
>>
>>> Paul, I've done this. You need to get good quality fiber optic
>>> multi-strand and it works pretty well. There is some loss but under
>>> a shadowed part of the panel, you can see it just fine. The trick is
>>> to make a coupling for the fiber at the LED end.
>>
>>> Darren
>>
>> Guys, you really don't need the LEDs.
>> Any display device *should* echo the relevant status messages.
>
> The designers of PowerFlarm must have intended to put this LED on a
> Christmas tree but they confused it with PowerFlarm brick and now we
> have LED there that is not needed. Great!

My guess: one reason it's there is to give the pilot indication when
he's using a flight computer for the display, as they may not bother to
show update messages.

--
Eric Greenwell - Washington State, USA (change ".netto" to ".us" to
email me)
- "Transponders in Sailplanes - Feb/2010" also ADS-B, PCAS, Flarm
http://tinyurl.com/yb3xywl

[Craig Funston[_2_]]

On Friday, May 17, 2013 1:58:35 AM UTC-7, kirk.stant wrote:
> It's too bad the PowerFLARM display doesn't have an attitude indicator on it and a direct link to an online glider-for-sale site - then we could have a really good thread going!
>
>
>
> Seriously, it can be frustrating, but if you ensure you have the correct files for updating the PF and display - making SURE you check the file name because Windows 7 WILL try to stick a .txt on it - the install is easy.
>
>
>
> And if you have a Butterfly External display (the one that comes standard with the PF Core), you will no longer have to power cycle the PF to download.
>
>
>
> And for Mike Stringfellow - With an Oudie, it is literally plug and play. The hardest part of installing the Flarm system is finding a place for all the antennas!
>
>
>
> Let's all go flying!
>
>
>
> Kirik
>
> 66

RAS seems to serving perfectly well as an "Attitude Indicator". Happy Friday, let's go fly now.

Craig

[swinkelj]

Op donderdag 16 mei 2013 16:52:43 UTC+2 schreef Dan Daly:
> I use this panel pass-through, and it works well: "NEUTRIK - USB A/B Pass Thru Black D-Type". I have a usb stick with a flashing LED to indicate it is accessing.
>
>
>
> I would be nice if there were a menu item, perhaps below the one where you set it to download IGC files, where you could end recording and then download IGC files to the USB stick without cycling power. I have to turn off everything, then boot my 7007 (provides power to the Core) in order to get the IGC file out.
>
>
>
> I am happy that I can transfer declarations from my Dell Streak/XC Soar via IOIO to the Core - very handy.

Hi Dan,

Did you buy your IOIO adapter, or did you make this yourself?

Thanks,
Joop