View Single Post
  #2  
Old October 6th 12, 05:19 AM posted to rec.aviation.soaring
noel.wade
external usenet poster
 
Posts: 681
Default PowerFLARM Range Issues - Part Two with info from todays flights

Mark and others -

Its been said many times in a few forums and websites (and I'm annoyed
they do not include it on a big red or yellow piece of paper in the
box):
YOU MUST NOT USE THE PowerFLARM UNITS (Brick or Portable) RIGHT "OUT
OF THE BOX". You *MUST* apply a configuration file, with your
aircraft's ID value in the config file. This is CRITICAL!!!

The reason is this: ADS-B (and thus FLARM) tracks your glider based on
your airplane's unique ICAO value. There are instructions on how to
find this and apply it to your config file. If you do not do this,
your FLARM will use a "default" (dummy) identifier. FLARM ignores
every signal with the same identifier as your own, to keep from
alerting you about your own position (for example, if you have a
transponder or install ADS-B out).

That means every other FLARM that is still set to the "default"
identifier will be ignored (because they all match) and you will never
see them on your FLARM display!! And the "other guy" will never see
you on his/her display!! Very, very bad.

[And yes, this is one area where I think the PowerFLARM folks could do
a better job with documentation and warning the purchaser. On the one
hand, its a complicated device that's doing a lot and its not a simple
install - so people should read instructions carefully. But on the
other hand you have to expect in this day and age that people are
going to assume something is "Plug and Play" unless you warn them off
- strongly.]

--Noel