PowerFLARM USB 3 cables and ConnectMe to PowerFLARM through V7

I would like to second Morteza's frustration with file transfer and task declaration on the brick. This is a headless device with no interface at all. if there was no need to interact with it, that would be fine, but It needs a front end of some kind to make it usable.

This is an IGC approved logger, and declaring a task by putting an edited text file on a USB stick, then transferring it by power cycling the whole thing and waiting for a blinking light you can't see to turn green..is appalling. At a minimum the user needs feedback that no mistakes were made.

For retrieving log files, should I dedicate a USB stick to the brick so it doesn't download every flight in memory each time the stick is inserted? if the stick is almost full of other stuff, what will happen? does it download newest flight files first and gracefully stop when it runs out of USB memory? Should I use a different stick for firmware updates, or is it ok to have the firmware upgraded every time I power cycle the brick if I forget to remove the config file? Should I give my dedicated USB stick to the contest scorer filled with irrelevant flights? Or should I erase all the repeatedly downloaded old flights off the contest USB stick each day?

Please, please fix this. ConnectMe works with almost every modern logger. It runs on PDAs and Oudie's, and laptops. It already has a decent interface and most pilots know how to use it. It's free, and it's already written and widely distributed. It would be a big win for your customers if you could make it work. Yes, the USB stick works, but your great product and your customers deserve a little better.

Matt

Thanks Matt,

you're asking some valid questions. I'll make sure they'll get answered
in future releases of the manual.

We're aware that not all the functionality of PF is available
for all the possible 'User Interfaces' (BF, FlarmView etc...), we're working
with the manufacturers to get them added. Feel free to direct
relevant feedback also to the display/flight computer etc. manufacturers.

re task declarations: Can be done via the RS232, should work with any
tool that already supported Classic FLARM. Manually editing flarmcfg.txt
was never considered a use case for the average user.

re IGC readout:
- Use a dedicated USB stick. Delete/backup your flights once per year,
it'll never get full (or how much do you fly? It can
be shared with F/W; the update is skipped if already installed.
- Power cycle is no longer needed with the BF display 3.2, other displays
should follow.

Contest scoring: Did you ever have a problem with a
contest scorer not accepting multiple flights on a stick? IGC files
are (intentionally) named so that the sorting order corresponds to the
chronology of flights. So it's easy to pick out the last one.

Best
--Gerhard (FLARM dev mgr)

My experience (core hooked up to SN10B and Oudie2, all with latest software) has been totally painless. Although I haven't declared a task in 13 years, my SN10 had no problem sending the R9 race tasks to the core on every flight last week at Moriarty. After each flight, using the Butterfly display and the same USB stick, it downloaded the latest flight in seconds, with positive feedback on the display of the status of the download. And Winscore doesn't care what else you have on your memory stick as long as the flight for the day is there.

I am EXTREMELY