![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#8
|
|||
|
|||
![]()
On Friday, 8 April 2016 08:16:04 UTC+2, Alex wrote:
I don't see what's not load and clear about "update once a year to the current version and your fine". So what I understand from that statement is: I update to the latest current version "X" on the 1st of January 2017. FLARM then release version "Y" a day later on the 2nd January 2017 which other users upgrade to. I will be able to run on version "X" for 365 days (1st January 2017 to 1st January 2018) with full compatibility with users running version "Y". Therefore it is possible for two different versions of FLARM to have full compatibility with each other for an entire year. If that is not the case then that statement is as clear as mud. |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Information for all users of Flarm, OEM FLARM supplier and Flarm PowerFlarm | [email protected] | Soaring | 28 | March 12th 16 04:31 AM |
Flarm IGC files on non-IGC certified Flarm? | Movses | Soaring | 21 | March 16th 15 09:59 PM |
SW developers: FLARM protocol version 6 reminder | Dave Nadler | Soaring | 0 | May 24th 12 02:49 PM |
FLARM: update to software version 5.00 available | pilot | Soaring | 1 | February 22nd 11 05:27 PM |
IGC-approval issued for the IGC version of Flarm | Ian Strachan | Soaring | 0 | March 10th 08 04:09 PM |