When will my portable powerFLARM have its logger functionality?

Hi, Tim,

Thanks for sending your dll file. I'm responding here so others can see what transpired afterwards.

I downloaded your file, unzipped it, and put it in the directory where my copy of IGCshell.exe resides. When I execute IGCshell, I get a message that "the specified module could not be found", and when I look at the available instruments in the drop-down box only Acme, Erixx, Volkslogger and the original 1.4 Flarm instruments are available.

Here's the specifics about what I've done to get to this point:

1. I'm running Win XP Pro SP 3 on a Lenovo T400 laptop. The IGCshell program was never present on this computer until this morning.
2. I downloaded from http://www.fai.org/gnss-recording-devices/free-software the zip file for the IGC Shell Program (dated 08 August 2012).
3. I created a C:/IgcDll folder, ran Unzip on the IGC Shell.zip file, selected "all files in archive" and "use folder names", pointed to C:/ and pushed the extract button. Accessing the C:/IgcDll folder, I verify that the IGCshell.exe and the IGC-XXX.dll files are present (plus a lot of other files).
4. I downloaded from http://www.fai.org/gnss-recording-devices/free-software the FR manufacturer dlls for Garrecht (dated 06 Sep 2011), for IMI (dated 29 Aug 2012), for the old Flarm (dated 05 Aug 2012, and for the updated Flarm (dated 14 Feb 2013), and put them into the C:/IgcDll folder. Accessing the C:/IgcDll folder, I verify that the igc-gcs.dll, the igc-imi.dll, the igc-fla.dll, and the igc-fla2.dll files are present.
5. I run the IGCshell.exe file by double left clicking on that name inside the c:/IgcDll folder using Windows explorer, and I get a message that "the specified module could not be found". When I look at the available instruments in the drop-down box only Acme, Erixx, Volkslogger and the original 1.4 Flarm instruments are available. There is no difference in this behavior if I use Cmd, change to the c:/igcdll folder, type in IgcShell and hit return.

On Friday, March 1, 2013 4:10:26 PM UTC-5, Tim Newport-Peace wrote:
In article , John
Carlyle writes

Hi, Tim,

Thanks for sending your dll file. I'm responding here so others can see what
transpired afterwards.

I downloaded your file, unzipped it, and put it in the directory where my copy
of IGCshell.exe resides. When I execute IGCshell, I get a message that "the
specified module could not be found", and when I look at the available
instruments in the drop-down box only Acme, Erixx, Volkslogger and the original
1.4 Flarm instruments are available.

Here's the specifics about what I've done to get to this point:

1. I'm running Win XP Pro SP 3 on a Lenovo T400 laptop. The IGCshell program
was never present on this computer until this morning.
2. I downloaded from http://www.fai.org/gnss-recording-devices/free-software
the zip file for the IGC Shell Program (dated 08 August 2012).
3. I created a C:/IgcDll folder, ran Unzip on the IGC Shell.zip file, selected
"all files in archive" and "use folder names", pointed to C:/ and pushed the
extract button. Accessing the C:/IgcDll folder, I verify that the IGCshell.exe
and the IGC-XXX.dll files are present (plus a lot of other files).
4. I downloaded from http://www.fai.org/gnss-recording-devices/free-software
the FR manufacturer dlls for Garrecht (dated 06 Sep 2011), for IMI (dated 29 Aug
2012), for the old Flarm (dated 05 Aug 2012, and for the updated Flarm (dated 14
Feb 2013), and put them into the C:/IgcDll folder. Accessing the C:/IgcDll
folder, I verify that the igc-gcs.dll, the igc-imi.dll, the igc-fla.dll, and the
igc-fla2.dll files are present.
5. I run the IGCshell.exe file by double left clicking on that name inside the
c:/IgcDll folder using Windows explorer, and I get a message that "the specified
module could not be found". When I look at the available instruments in the
drop-down box only Acme, Erixx, Volkslogger and the original 1.4 Flarm
instruments are available. There is no difference in this behavior if I use Cmd,
change to the c:/igcdll folder, type in IgcShell and hit return.

Tim, I'd appreciate it if you'd run through these steps and see what you get.

Best regards,
John


Hi John,

I have tried on two PCs now (Both XP-Pro SP3) and I cannot reproduce
your problem.

Is anyone else in this group having the same problem?

Best wishes,
Tim.
--
Tim Newport-Peace

Hi, Tim,

Thanks to Marc Ramsey, the problem I was having with the FAI dll for PowerFLARM (see above) has been solved. Unlike the other dlls I got from the FAI for Volkslogger, Erixx and the original FLARM, the PowerFLARM dll needs a Microsoft C++ library, MSVCR100.DLL. My machine didn’t have this library in a place where the PowerFLARM dll could find it.

If you get an error message and then cannot see a listing in the drop-down box for PowerFLARM when running IGCshell after the PowerFLARM dll is added, you can get around it in two ways. First, as I did, search your computer for the 753kB file MSVCR100.DLL, copy it and paste it into the folder where IGCshell and the PowerFLARM dll reside. Second, as Marc suggests, install the 4.9 MB Microsoft Visual C++ 2010 Redistributable Package, either x86 or x64 version, depending on what OS you're running:
x86: http://www.microsoft.com/en-us/downl...s.aspx?id=5555
x64: http://www.microsoft.com/en-us/downl....aspx?id=14632

The best solution, of course, would be for FLARM to re-write the PowerFLARM dll so it does not require this library, since it cannot be guaranteed that every machine out there will have it.

-John, Q3

Thanks for the detailed description John, R&D has been notified.
FLARM

For the older FLARM units, Flarmtool is used to update firmware and preferences or download IGC files. The current version is 2.0 with firmware 5.09. Using the Flarmtool program is easy.
Will there eventually be a tool for the PowerFLARM?
Jim

On Saturday, March 2, 2013 5:19:20 PM UTC-5, JS wrote:
For the older FLARM units, Flarmtool is used to update firmware and preferences or download IGC files. The current version is 2.0 with firmware 5.09. Using the Flarmtool program is easy.

Will there eventually be a tool for the PowerFLARM?

Jim

Ehh ? Easier than just copying the firmware onto a USB stick
or uSD card ???

Next release will shortly after we get the IGC approval (='real soon now')



For "Real Soon Now" read "Now!"


http://www.ukiws.demon.co.uk/GFAC/ap...powerflarm.pdf



So is V2.71 firmware available now or is this something that is coming soon ?

Hi Karl,

There was a post by FLARM a day or 2 ago stating that the new firmware has
not been released yet but will be in the next few weeks. Also, they are
working to resolve the issue with the hardware version on the approval
document. They have given assurances that all PowerFLARM units delivered
with a security seal on them should be upgradeable without the need to send
them in.

Paul Remde
Cumulus Soaring, Inc.
____________________________

"Karl Kunz" wrote in message
...


Next release will shortly after we get the IGC approval (='real soon
now')



For "Real Soon Now" read "Now!"


http://www.ukiws.demon.co.uk/GFAC/ap...powerflarm.pdf



So is V2.71 firmware available now or is this something that is coming soon
?

Evidently I shouldn't have mentioned that Flarmtool does uploads. From other peoples experiences with flight logs, the downloading part appears to have gone backwards from the simple use of Flarmtool or SeeYou with Swiss or Australian FLARMs.
Jim

On Saturday, March 2, 2013 5:51:44 PM UTC-8, Dave Nadler wrote:
On Saturday, March 2, 2013 5:19:20 PM UTC-5, JS wrote:

For the older FLARM units, Flarmtool is used to update firmware and preferences or download IGC files. The current version is 2.0 with firmware 5.09. Using the Flarmtool program is easy.



Will there eventually be a tool for the PowerFLARM?



Jim



Ehh ? Easier than just copying the firmware onto a USB stick

or uSD card ???

The best solution, of course, would be for FLARM to re-write the PowerFLARM dll so it does not require this library, since it cannot be guaranteed that every machine out there will have it.

Hi John,

My development machine has about a dozen copies of MSVCR100.dll (not all
the same, btw...), which is why this problem went unnoticed.

I updated the FLARM IGC tools as you suggested and it is available for
download he
http://flarm.com/support/updates/fla...ools-1.5.1.zip

Thanks for the heads-up!

Best
--Gerhard (dev mgr FLARM and PowerFLARM)

So, even if we record an IGC file with the PowerFLARM, there's no way at the moment to validate it.

Logs from PowerFLARM 2.60 should just validate OK in OLC and any other
system which validates Classic FLARM logs. You can also use the command line
tool vali-flarm-nonigc.exe. If it doesn't, please let us
know at info at flarm dot com.

The IGC shell and DLLs will be relevant only for the next version with strong security which was just approved by the IGC/GFAC.

Best
--Gerhard (dev mgr FLARM + PowerFLARM)