Skip to content

v1.7.1 - Bugfixes for iMet sondes, Record RS41 mainboard type and cal data

Compare
Choose a tag to compare
@darksidelemm darksidelemm released this 07 Oct 08:37
· 219 commits to master since this release
145979e

This is mainly a bug-fix release to resolve the iMet decoding issues from v1.7.0, though I have taken the opportunity to add some functionality to log and upload additional information for Vaisala RS41's.

Recently updated PCBs have been spotted in RS41s launched from Vaisala HQ in Helsinki, Finland. These new PCBs seem to have a mainboard version number of RSM424 (compared to RSM412 for the older models), and have a newer STM32 microcontroller and uBlox-10 GPS receiver. auto_rx will now upload the mainboard version information to SondeHub, where it will be visible on the tracker and help identify newer RS41 versions as they are rolled out!

This release brings the following updates:

  • RS41 Decoding: Extract the RS41 Mainboard model number and firmware version, and upload these to SondeHub. This will allow us to keep track of the rollout of the new RSM42x 'refreshed' RS41 mainboards. If the mainboard version is not RSM412 (the 'standard' RS41 mainboard), then it will also be shown in the 'other' column on the web interface.
  • RS41 Decoding: Upload complete subframe (calibration) data to SondeHub, and optionally save it to disk.
  • iMet Decoding: Fix issue where iMets were detected as iMet-1 sondes when wideband_sondes was enabled.
  • iMet Decoding: Fix bug where iMet telemetry with XDATA included was not being uploaded to SondeHub.
  • Web Interface: If a sonde has XDATA, the type is now displayed as -XDATA instead of -Ozone.
  • Log files & general: Log files will now have -XDATA appended to the sonde type instead of -Ozone if XDATA is present.

Configuration File Changes this release:

  • Added save_cal_data option, which saves Vaisala RS41 raw calibration data to disk. Refer here for details.

Warning: Users running 'native' installs may need to upgrade their version of the flask library and dependencies, otherwise you will see an error along the lines of ModuleNotFoundError: No module named 'werkzeug.middleware'. If you installed python3-flask via your system package manager, you will need to run:

$ sudo apt-get remove python3-flask
$ sudo pip3 install -U flask flask-socketio

Users of the Docker image will not have this issue, as all the appropriate package versions are included in the image.

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.

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)

While this does not cause issues and auto_rx will continue to function, this can be resolved by installing the simple-websocket Python package. If you are using Docker, this will be included from the v1.6.2 release. Otherwise, you may need to run:

sudo pip3 install simple-websocket

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