Skip to content

Fix handling of DFMxB sondes, and handling of encrypted RS41s
Compare
Choose a tag to compare
@darksidelemm darksidelemm released this 15 Dec 04:43
· 1155 commits to master since this release
v1.2.3
0ac0315
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Patch release to:

  • Allow DFM sondes with a 0xB ID code (most likely DFM-17 sondes) to be processed.
  • Fix issues with encrypted RS41 sondes not being blocked correctly due to the new automatic frequency correction features.

Important Note
In the next release (v1.3.0), the way Graw DFM sondes are handled will change. Graw have stated that the method that the radiosonde-decoding community currently uses to determine radiosonde types is not valid, particularly for the new DFM-17 radiosondes.
As such, I will be moving away from including the identified DFM sonde type in the generated callsign (for both Habhub and APRS), and only include it in the comment field.

On Habhub, DFM callsigns will change from DFM09- to DFM-. The format of DFM callsigns used on APRS is still to be agreed upon with developers of other radiosonde decoding software, to ensure we are consistent.

As this change is going to result in many duplicate sondes appearing on various maps as users upgrade, we will be immediately blocking all DFM sonde uploads to Habhub from versions older than v1.3.0 as soon as this version is released. Unfortunately it is not possible to do the same for APRS, so there is likely to be a large amount of duplicate sondes on radiosondy.info and similar sites for a while.

Please report any problems encountered either on the mailing list, or by raising an issue on this repository.

PLEASE DO NOT USE THE GITHUB GENERATED RELEASE ZIP FILES - USE THE INSTALLATION/UPDATE STEPS DESCRIBED IN THE WIKI

Assets 2
Loading