![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]()
My understanding is that the logger is an extra cost option on later
PowerFlarm Core Pure hardware. Without this option enabled, the unit will NOT produce flight logs. Bob On Mon, 9 Mar 2015 09:55:05 -0700 (PDT), Movses wrote: I'm somewhat confused with the functionality of the flarm core in regards to producing flight traces. I was never able to obtain a trace from my Flarm Core Pure. I put the usb drive in, turn it on, wait for the light to settle to green, turn it off, pull the drive - nothing. Updating settings from the drive does work, so I'm reasonably confident that the drive is being recognized. Now, the unit does not have the IGC certification enabled. Originally I thought it simply meant that the traces produces would not be properly signed to be recognized as valid, but now I start questioning whether a non-IGC enabled Flarm produces logs at all? I don't need to use the Flarm as a logger, but I did want to feed a file to the range analyzer to evaluate antenna placement. Does anybody have an experience with this? Thanks, Movses |
#2
|
|||
|
|||
![]()
If that's the case, how are we supposed to verify performance with the range tool?
On Monday, March 9, 2015 at 12:19:56 PM UTC-7, Bob Gibbons wrote: My understanding is that the logger is an extra cost option on later PowerFlarm Core Pure hardware. Without this option enabled, the unit will NOT produce flight logs. Bob I'm somewhat confused with the functionality of the flarm core in regards to producing flight traces. I was never able to obtain a trace from my Flarm Core Pure. I put the usb drive in, turn it on, wait for the light to settle to green, turn it off, pull the drive - nothing. Updating settings from the drive does work, so I'm reasonably confident that the drive is being recognized. Now, the unit does not have the IGC certification enabled. Originally I thought it simply meant that the traces produces would not be properly signed to be recognized as valid, but now I start questioning whether a non-IGC enabled Flarm produces logs at all? I don't need to use the Flarm as a logger, but I did want to feed a file to the range analyzer to evaluate antenna placement. Does anybody have an experience with this? Thanks, Movses |
#3
|
|||
|
|||
![]()
Have you loaded a flarmcfg.txt file?
Have you inserted a USB drive and turned power off/on with it inserted? Which firmware are you using in the CORE? |
#4
|
|||
|
|||
![]()
On Monday, March 9, 2015 at 5:01:42 PM UTC-4, Dan Daly wrote:
Have you loaded a flarmcfg.txt file? Have you inserted a USB drive and turned power off/on with it inserted? Which firmware are you using in the CORE? Is your USB drive USB 2.0, formatted FAT, and less than 32 GB? |
#5
|
|||
|
|||
![]()
You must not be using the USB stick at the end of each flight.
I think the key is that you must shut off the FLARM, then insert the USB memory stick, then turn the FLARM back on and it downloads the just flown flight log. I flew with my PowerFLarm for the first time last summer, did this action, and every log was transfered to the USB memory stick and I posted them that evening on OLC. |
#6
|
|||
|
|||
![]()
On Monday, March 9, 2015 at 2:55:07 PM UTC-7, wrote:
You must not be using the USB stick at the end of each flight. I think the key is that you must shut off the FLARM, then insert the USB memory stick, then turn the FLARM back on and it downloads the just flown flight log. I flew with my PowerFLarm for the first time last summer, did this action, and every log was transfered to the USB memory stick and I posted them that evening on OLC. The answers to this is pretty much all previous questions is yes... To my best knowledge: - configuration file is uploaded - usb stick in, then power on, monitor led, power off when done. - not sure on firmware, will give this another try when I get to the airport next time. Sigh.. I'm a software engineer, I'm usually the one who's good with this stuff ![]() |
#7
|
|||
|
|||
![]()
On Mon, 09 Mar 2015 23:41:34 -0700, Movses wrote:
On Monday, March 9, 2015 at 2:55:07 PM UTC-7, wrote: You must not be using the USB stick at the end of each flight. I think the key is that you must shut off the FLARM, then insert the USB memory stick, then turn the FLARM back on and it downloads the just flown flight log. I flew with my PowerFLarm for the first time last summer, did this action, and every log was transfered to the USB memory stick and I posted them that evening on OLC. A standard FLARM typically holds up to the last ten flight logs in its internal memory. If its an LX RedBox FLARM, when you put the SD card in and turn it on, ALL the logs that aren't already recorded on the card are written to it. The red LED flashes while its doing this. Its quite slow, taking noticeably more time to write several logs than just one. Since all FLARMs run the same software, they should all do the same. I'd be surprised if the PowerFLARM doesn't do it too. -- martin@ | Martin Gregorie gregorie. | Essex, UK org | |
#8
|
|||
|
|||
![]()
As an uninterested party, I've got to ask: How is this update
information requirement disseminated? The reason I ask is that, two days ago, someone at Moriarty told me that he had to figure out why his Flarm didn't work. I told him that I'd seen on RAS that there's a mandatory update required. I would have thought all owners would have been notified. On 3/10/2015 12:41 AM, Movses wrote: On Monday, March 9, 2015 at 2:55:07 PM UTC-7, wrote: You must not be using the USB stick at the end of each flight. I think the key is that you must shut off the FLARM, then insert the USB memory stick, then turn the FLARM back on and it downloads the just flown flight log. I flew with my PowerFLarm for the first time last summer, did this action, and every log was transfered to the USB memory stick and I posted them that evening on OLC. The answers to this is pretty much all previous questions is yes... To my best knowledge: - configuration file is uploaded - usb stick in, then power on, monitor led, power off when done. - not sure on firmware, will give this another try when I get to the airport next time. Sigh.. I'm a software engineer, I'm usually the one who's good with this stuff ![]() -- Dan Marotta |
#9
|
|||
|
|||
![]()
Hi Movses,
I suspect that the USB flash drive is not compatible for some reason. Perhaps it is formatted using FAT instead of FAT32 or vice versa. Or perhaps it is too large in regard to capacity. What is the capacity of the USB flash drive? It is my understanding that the PowerFLARM Core and Core Pure units will always log a flight that is accepted by the OLC. The IGC enable and a calibration make them valid for badges and most records. Best Regards, Paul Remde Cumulus Soaring, Inc. ____________________________________ "Movses" wrote in message ... On Monday, March 9, 2015 at 2:55:07 PM UTC-7, wrote: You must not be using the USB stick at the end of each flight. I think the key is that you must shut off the FLARM, then insert the USB memory stick, then turn the FLARM back on and it downloads the just flown flight log. I flew with my PowerFLarm for the first time last summer, did this action, and every log was transfered to the USB memory stick and I posted them that evening on OLC. The answers to this is pretty much all previous questions is yes... To my best knowledge: - configuration file is uploaded - usb stick in, then power on, monitor led, power off when done. - not sure on firmware, will give this another try when I get to the airport next time. Sigh.. I'm a software engineer, I'm usually the one who's good with this stuff ![]() |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Flarm to MIO 400 | [email protected] | Soaring | 1 | January 23rd 15 06:05 PM |
IGC Flight Recorders using Flarm firmware - New DLL file forvalidating IGC flight data files | Ian Strachan | Soaring | 0 | July 20th 14 07:28 PM |
FLARM IGC files: erasable? | [email protected][_2_] | Soaring | 5 | May 20th 13 07:46 PM |
FLARM for SAR | FLARM | Soaring | 57 | November 21st 12 07:21 PM |
FLARM | Robert Hart | Soaring | 50 | March 16th 06 11:20 PM |