FLARM - Which version do I need to be on?

I corresponded with Flarm a few months ago about this and after a couple of clarification replies I think that I understood what they were doing:

Major updates (currently V6.xx) we know about and need to be loaded by the specified date and are not interoperable with earlier major versions.

Minor updates (e.g. all V6.xx) are interoperable but each one stops working 2 years after release (or when a major update is required if sooner). The logic is that if all owners do what Flarm recommend and update with the currently available software annually at glider inspection time then, no matter when in the year they do so, that version will operate, and be interoperable with every other Flarm following the same guidelines, for at least a year (major updates excepted). If we forget to update software altogether the Flarm unit *will stop working* 2 years after the release date of the installed version - or at the next major version change.

In the past Flarm had two types of Updates, MINOR and MAJOR.

MINOR update (X.06) generally covered smaller enhancements and bugfixes. A lot of these concerned small glitches in third party devices effecting only few users. In most cases these updates could be ignored, because they did not effect your device or concerned non essential feature additions. Often major releases were accomponied with multiple ensuing minor versions to fix previously undetected bugs.

MAJOR updates (6.XX) were/are the mandatory updates. These included changes to the communication protocoll and/or major changes to the collision avoidance algorithm. Major updates were planned to fixed dates years in advance and strictly mandatory. Flarm chose this update scheme because it allowed full flexibility in improving the software at minimal effort, because it was not necessary ensure compatibility to obsolete software versions. This update scheme was one of the major success factors for Flarm, because it facilitated a steep development curve while keeping cost low. The unfortunate drawback is that it is not the most user friendly approach.

After a lot of user complaints Flarm decided to change the update scheme last year. Instead of mandatory release dates at changing intervals and explaining about major and minor versions, they simplfied things to one easy to understand message: "Dear pilot, download a current Flarm version once a year and do the update. Don't bother with version details or compatibility - we will take care of everything else."

As I understand the new update scheme, no more big bang major updates are planned. Possibly Flarm software has matured sufficiently so that non compatible big bang major versions are no longer needed. Maybe they have found more elegant time triggered ways to implement compatibility related updates across the fleet within the current rolling update scheme. Incase the need for a new big bang major version becomes apparent, necessary provisons (new big bang date) can be reintroduced via the current update scheme within 365 days. I expect Flarm will try to avoid this in the future, because it is usually accompanied by a wave of user upsets. But, I have to concede, I am only guessing...

Since the PowerFlarm core is my primary GPS engine and data logger I wish they would only disable the Flarm functions and not the entire unit when it needs a software update. If they go out of business my core will be a brick literally.

Welcome to the new Millennium where
your glider is a mini Datacenter requiring a
System Administrator.

Me, I just make sure everything is updated
at the beginning of the season: Flarm,
display, vario, flight computer...

And keep an eye out for interim updates,
some of which are not announced.

Welcome to the new Millennium where
your glider is a mini Datacenter requiring a
System Administrator.

Me, I just make sure everything is updated
at the beginning of the season: Flarm,
display, vario, flight computer...

And keep an eye out for interim updates,
some of which are not announced.