SoftRF version mb179

[Moshe Braner]

On the T-Beam, if equipped with a buzzer, it now plays a short rising two-tone sound when a GNSS fix is achieved.

Also, added a FANET style ID method.  So you can choose these ID methods:

* ICAO ID - also need to enter the ID in the "aircraft ID" setting

* Device ID: it will transmit "8" followed by the last 5 hex digits of the chip ID

* FANET ID : it will transmit "87" followed by the last 4 hex digits of the chip ID

Note that in FANET transmissions there are a separate "vendor ID" (2 hex digits) and "aircraft ID" (4 hex digits).  If using "device ID", the "vendor ID" will be "8x", where 'x' is the fifth hex digit of the chip ID, i.e., not a fixed "vendor ID".  If using "FANET ID method" the vendor ID will be a fixed "87".

Note also that SoftRF will use the same ID for all protocols, i.e., if you choose "FANET ID method" then FLARM and ADS-L and OGNTP transmissions will use the "87xxxx" ID.  Even if this other protocol is the only one (no alt-protocol).

In my view all tracking data of a given aircraft should be combined, and that requires that all data sources use the same ID.  That is why SoftRF will use the same ID for all protocols.  Although some tracking methods (e.g., some OGN viewers) will separate the data based on the type of transmission (e.g., FANET vs. FLARM) even if they use the same ID. Conversely, some systems (Puretrack?) may allow combining data from different IDs if somehow registered to "the same aircraft".

And some systems processing FANET data may allow filtering on the "vendor ID", thus having it be variable ("8x") may be a downside of using "device ID".  And if you choose ICAO ID, that will cause the "vendor ID" in the FANET transmission to be the first 2 hex digits of the ICAO ID, even more variable!

Having only 4 hex digits to be specific for the aircraft (in "FANET ID method") increases the chance of a duplicate ID, e.g., within the OGN device database which has over 20,000 entries.

So overall there is no clear answer to the question of what's the best type of ID to use.  That is why I made it possible to choose either.  Let me know what works best for you, and why.

Definitely, if you do not use FANET, stick with "device ID", or even better, ICAO ID if your aircraft has one.

Note: if you already registered your 8xxxxx device ID with any tracking system, and you decide to switch to "FANET ID method", you will need to update you registration.