Skip to content

v1.6.1 - iMet-50/54 & M10 decoder fixes, Web Interface Updates

Compare
Choose a tag to compare
@darksidelemm darksidelemm released this 01 Apr 00:21
· 300 commits to master since this release
3e0d8ef

This release brings the following updates:

  • Decoders: Fix a bug in the handling of iMet-50/54 data.
  • Decoders: Fix a bug that occurred when decoding M10 radiosondes with the 'save raw data' setting was enabled. (Thanks @rs1729 !)
  • Decoders: Rebase M20 decoder, to better handle improbable PTU values. Note that the M20 decoder also decodes the new PS-20 pilot-sonde, though it is still reported as a M20 as the telemetry formats are the same. (Thanks @rs1729 !)
  • Web Interface: Add customisable fields to the Historical View table. (Thanks @AstroTaka !)
  • Web Interface: Possible stability improvements for the main Web Interface page, should result in the page hanging less often.

Other Known Issues:

  • iMet-1 serial number generation still has issues, and will result in iMet-1 sondes being assigned 3-4 different serial numbers throughout the flight. This is due to the iMet-1 telemetry repeating data across multiple frames, and there's no easy fix (Thanks InterMet...). iMet-4 sondes should not be affected.

There are no configuration file changes in this release.

Note: We are aware that new installations may display the following message on startup:

The WebSocket transport is not available, you must install a WebSocket server that is compatible with your async mode to enable it. See the documentation for details. (further occurrences of this error will be logged with level INFO)

This can be safely ignored. The web interface should still continue to work as usual. Eventually we will figure out how to suppress it...

The pre-built Docker Image is now the recommended way to setup radiosonde_auto_rx on a new station. Using Docker avoids issues with updates to dependencies, and allows for fixes relating to system packages to be easily pushed out to users.

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