2008 Scheduled Update Information
How do I update? 1
When will the update software be available? 1
How does the 2008 update process work? 1
What if I do not update by May 1, 2008? 1
I can’t figure it out! 1
Is the update free? 2
Do I need to know the serial number to update? 2
Why scheduled, mandatory updates? 2
When is the next scheduled service update due? 2
How about other manufacturer's devices? 2
How do I get the latest news about FLARM? 2
Look outside! 3
Advanced “Privacy” mode -> renamed to “Stealth mode” 4
Improved transmission confidentiality, integrity verification , and discontinuation of ID hopping 4
Temporary, stationary obstacle profile 4
How do I update?
The free software is available from www.flarm.com/support/ after February 26, 2008
If your device has an SD card reader, you only need a suitable SD card and a PC with SD card reader.
Otherwise you need an IGC standard serial cable, as used to read out all other modern flight recorders.
Detailed update instructions will come with the update software. The actual update process only takes a few seconds.
Hint: Most FLARM shipped after 2006 have an SD card slot. Check for a small slit on the face or side of the unit.
When will the update software be available?
Release date for version v4.00 is February 26, 2008.
How does the 2008 update process work?
Users may update their devices at any time once the update is available. Devices with v3.xx firmware will remain fully functional up to May 1, 2008. Updated devices will remain fully compatible with v3.xx firmware devices until May 1, 2008. This means that updates must be done anytime during March or April 2008.
The following restrictions apply for devices with v3.xx firmware:
After the end of February, the device will power up with a recoverable error, indicated by blinking lights and error code 0x11. The user may click this away (or simply wait 30 seconds) and the device will work as always.
On May 1, 2008 the devices with v3.xx (i.e. no update done) will refuse to start-up as compatibility is not given. This is indicated by permanently displaying the error code 0x11 (see manual for details).
Also on May 1, 2008 the new features and algorithms automatically get activated.
Beta versions of the firmware as it will run after May 1, 2008 are available to interested parties on a restrictive level and will not interfere or interoperate with the rest of the FLARM network.
What if I do not update by May 1, 2008?
Your FLARM will start up with a permanent error code. You need to do a firmware update prior to using it.
There will be no alerts and others will not receive your signal!
I can’t figure it out!
Your friendly local FLARM distributor is there to help you. See the list at www.flarm.com/contact/
For tough problems, send email to
Is the update free?
Yes. Firmware to maintain the core functionality will always be available for free.
Do I need to know the serial number to update?
Nope.
Why scheduled, mandatory updates?
The ability to update the whole network without being limited by constraints of the past is one of the key features of FLARM and has allowed it adapt to rapidly expanding requirements. Many parts of aircraft require scheduled maintenance, this is not a concept which is new to aviation.
Improved and new features in the v4.00 firmware release that would not be possible without a firmware update in all devices of the FLARM network (see next pages for more detailed explanation of some items):
- Increased range for the use of amplifiers and high-gain antennas and increased performance for aircraft operation in close proximity of each other (team flying aircraft, helicopters, UAV)
- New, advanced “Stealth Mode” to prevent abuse in glider competitions
- Network wide data transport through addition of mesh network features
- Temporary obstacles (via radio transmission from stationary, specially configured obstacle FLARM’s)
- Improved transmission confidentiality and integrity verification
- Discontinuation of ID hopping
- Bandwidth improvements according to recommendations by 3rd party R&D
See www.flarm.com/news/presscoverage/wsl_8232.pdf (German original) or
www.flarm.com/news/presscoverage/efficacy_warning_system_lds2007.pdf (English translation)
The obstacle database is constantly being updated and expanded. Users are encouraged to update their devices frequently for maximum safety.
When is the next scheduled service update due?
Since its creation FLARM has maintained scheduled updates, initially in a one year cycle, since 2006 a two year cycle. As the technology matures, we extend this period. This is more convenient for some users, but slows down the innovation cycle, possibly delaying the use in new applications.
v4.0 update, 2008 / v5.0 update , 2011Firmware update available / February 26, 2008 / October 1 2010
Device shows error at startup, but remains fully functional / March 1, 2008 / January 1, 2011
Automatic RF protocol change / May 1, 2008 / March 1, 2011
meomatic (May h 2008)
How about other manufacturer's devices?
All FLARM compatible devices, independent of type and manufacturer, run the same core hard- and firmware and are therefore compatible by design. This document applies to all of them.
Compatible manufacturers and their products are:
LX Navigation / RedBox, LX 7007, LX 8000, Colibri Flarm (full IGC approval), MiniBoxTriadis / FLOICE: with voice-Intercom output
Ediatec / ECW 100: 57mm with beeper -Intercom output
RF Developments
(Australia and New Zealand) / OzFlarm, MiniOz
Artronic / to be announced
FLARM Technology / Original FLARM
in March 08 with IGC approval up to diamond badge and ENL sensor
Please visit www.flarm.com/product/ for an updated list of compatible products.
How do I get the latest news about FLARM?
Please sign up to our mailing list at:
lists.flarm.com/mailman/listinfo/user-list_flarm.com
The list is moderated, we will not give your mail address away for non FLARM purposes and we will keep the number of sent mails to a minimum. Please use the forums at www.flarm.com/forum/ for any type of discussions.
Look outside !
Never rely on FLARM. A vigilant effective lookout is required at all times!
Advanced “Privacy” mode -> renamed to “Stealth mode”
To prevent abuse of the received data in competitions (which is an IGC requirement) FLARM has since 2004 included a “Privacy” mode where not all the received information is forwarded to the serial data-port and therefore is not available to external, graphical displays or PDA’s.
For the mandatory 2008 update, “Privacy” mode is further refined with the following goals:
· Discourage temporary powering off of FLARM during competitions
· Discourage use of “Privacy” mode outside competitions
Modification for the mandatory, scheduled 2008 update:
The guiding principle is that the pilot will not receive more information than what he has visually available anyway.
a) Renaming to “Stealth mode” as this better describes the purpose and operation. We clearly promote its non-usage.
b) The status and any changes of the "Stealth mode" is recorded in the IGC file as an L-record (LFLA STEALTH [ON / OFF]) and is therefore protected by the G-record. Consequently a competition authority can easily enforce the use (or non use) if desirable.
c) Manual changes to "Stealth mode" during flight are delayed by five minutes
d) Full reciprocity: A pilot that enables “Stealth mode” will get the information as if all other aircraft had enabled “Stealth mode”, independent of their actual setting.
e) If FLARM is disabled for more than three minutes during flight, other aircraft are treated as if in "Stealth mode" for the first five minutes, independent of their actual setting.
f) Targets with enabled “Stealth Mode” are only displayed in NEAREST and are available on the serial data-port as a PFLAA message, if they meet at least one of the following requirements:
- target is a threat
- target is within 100m horizontal and 50m vertical
- target is within 1000m horizontal and 200m vertical and within ±45° of own flight track.
g) If a PFLAA message is issued according to the rules above, all fields in Italic are empty:
PFLAA,<AlarmLevel>,<RelativeNorth>,<RelativeEast>,<RelativeVertical>,<IDType>,<ID>,<Track>,
<TurnRate>,<GroundSpeed>,<ClimbRate>,<AcftType>
h) <RelativeVertical> degraded with random white-noise in the order of magnitude of (distance / 50) , as long as target is not a threat.
Improved transmission confidentiality, integrity verification , and discontinuation of ID hopping
Currently the central processing module of FLARM parses all radio messages received that match the network address as well as pass a two bytes error detection check done by the transceiver module. However the error detection routines offered by the transceiver itself are restricted, what - on very rare occasions - can cause the processing of random data. Furthermore manufacturers for devices using serial data from Flarm-compatible devices (e.g. PDA’s, voice-interfaces and displays) have since long asked to replace the random ID hopping option intended to comply with competition rules and to augment privacy (see above) with an alternative approach where ID’s – if available – are guaranteed to be stable.
Modification:
Remove ID hopping option in serial message PFLAC,,ID and instead include adding additional error detection encoding and encryption on the radio message to verify and ensure its correctness and integrity, but.
Temporary, stationary obstacle profile
A FLARM can be configured to broadcast stationary obstacle information. Other FLARMs, fitted in aircraft, will be warned before entering the airspace in vicinity of this static object.
Possible usage scenarios are:
· Winch launch areas
· Temporary transportation (cable railway)
· Shooting ranges
February 2008 1.0 2/4