Thread: FLARM for SAR
View Single Post
  #2  
Old November 16th 12, 03:14 AM posted to rec.aviation.soaring
pcool
external usenet poster
 
Posts: 69
Default FLARM for SAR

What FLARM is doing is simply crypting the traffic info in their IGC logs.
All applications using FLARM data can do the same, the traffic information
is the same.
I am pretty sure that what a PNA receives is the same stuff that FLARM is
saving (encrypted) in the IGC.

The point here is that most pilots send to OLC their logs saved by LX,
Zander, Winpilot, Seeyou, LK8000, Xcsoar, etc.etc. and not necessarily from
their flarm units. For a SAR investigation you do need all logs from the
flarm units around, and this requires an active action to collect these logs
from pilots in the day of the accident.
Even knowing how to decrypting the IGC by FLARM, you still need to ask all
pilots to provide their Flarm logs, not their LX, Zander, etc.etc logs.

So, for SAR purposes knowing the encoding is not enough, you do need all
pilots to provide IGC logs from Flarm.
Then, why flarm is encoding-shuffling-cyphering these SAR valuable
informations, is beyond my understanding.
The only reason I can spot is they want to maintain a privileged position on
this matter, as they did with the communication protocol. After all, Flarm
units are about safety, SAR is safety, and this is a "safety" market, with a
monopolistic leader.

That's it..





"Don Johnstone" wrote in message
. com...

At 11:20 15 November 2012, Tobias Bieniek wrote:
It seems that FLARM ultimately took the wrong decision...

Two weeks ago Andrea Schlapbach from FLARM contacted me via email to
discus=
s how we would want to use these data sentences. In the initial email he
al=
ready clearly stated that "they had no interest in publishing the data
form=
at" and would only "share the format with a few interested and suited
partn=
ers". "Suited partners" in their definition are those that are able to
keep=
the format a secret.

In my answer I explained that XCSoar and SkyLines are both open source
appl=
ications and that keeping a secret in open source code isn't really
possibl=
e. I also asked what their intentions are for keeping the format a

secret,
=
but unfortunately that question was never answered. My second email
answeri=
ng some follow-up questions and asking the same thing again was never
answe=
red either.

I feel very sorry that FLARM has become such a closed-up proprietary
compan=
y. I don't see any reason for keeping the data format a secret and I
certai=
nly hope that they reconsider this non-sense at some point. The only two
re=
asons I can see for this is: a) they want to use the data commercially at
s=
ome point or b) they are logging data that contains private data that
shoul=
dn't be logged in the first place. If they would really care about these
SA=
R reasons they would simply open up their format so that any public party
c=
ould use them...


Surely all you need is a qualified software engineer to read the output,
which you may have noticed is broadcast, and compare the raw output to what
is displayed in many of the magic apps that use it. It's called reverse
engineering, if you want to be posh or hacking if you don't. You can then
work out what the data sentences consist of and decde them. I spent many
years happily working doing just that some years ago, not with FLARM I
hasten to add.