Skip to content

2.0.0rc16
Compare
Choose a tag to compare
@steveatinfincia steveatinfincia released this 13 Aug 05:04
2.0.0rc16
d6e87e8

This is a release candidate for Open.HD 2.0, there will be at least 1-2 more to fix a few issues.

If you don't want to risk upgrading and encountering a problem, wait for the stable release.

Downloads

Note: Downloads removed temporarily due to a bug in the image, wait for rc17

  • Stretch
    • Still provided for people using the old OSD while we port it to Buster
  • Buster
    • Required for Compute Module 3+, or Pi4, but works on all pi models
    • Only supports the new QOpenHD OSD at the moment, the old OSD is being ported and will be there soon

Changes in 2.0.0rc16

  • Update QOpenHD to 0.4.0b11
    • Fix upper/lower bars
    • Replace heading widget with more efficient code
    • Ladder tweaks
    • Horizon bar tweaks
    • Add detailed Mavlink telemetry stats in the lower right of the status panel
      • Use them to see if you are missing some telemetry messages, they should all be changing constantly
    • Automatically enable Mavlink telemetry messages on Ardupilot flight controllers (may work on PX4 as well)
      • You no longer need to edit Ardupilot's SRx_EXTRA parameters like the OpenHD wiki says
    • Add a simpler speed widget (for Norbert)
      • Note: this widget doesn't have settings in the settings file at the moment, will be added in the next release
    • Add settings file support on ground, Android, Windows, Mac, Linux (iOS is coming soon)
      • On the ground, the new /boot/qopenhd.conf file allows control over everything, just edit the file and reboot
      • Note: you must let the ground station boot at least once so it can create the settings file
      • On other platforms you can use the new Manage tab in the settings area to save or restore the settings from a file
      • If you load a settings file on mobile/desktop platforms you must restart the app. On Android the app will do it for you.
      • You can use the same file on any platform
      • Note that the file is not just widget layout, but all settings. We will make it possible to export/import widget layouts so you can share them with other people soon.
      • The file is self-updating. If we add new settings, you don't have to manually keep it up-to-date. On the ground this is entirely automatic, on other platforms just load and save the settings file again.
  • Add setting to force plain 802.11 data frames on Realtek cards
    • This is a temporary option for anyone having issues with telemetry on any Realtek card
    • To enable it, set FORCE_REALTEK_TELEMETRY_DATA_FRAME=Y in the openhd settings file on air and ground
  • Fix Seek thermal script not loading the settings file
  • Fix openhdvid script
  • Add date to file path for recording in openhdvid
  • Internal changes
    • Additional wifi drivers (not tested yet, so we aren't advertising any of them as features)
    • Deduplicate rssitx frame construction

Test notes

  • Air-side power stats (voltage/current from external sensors) may not be arriving in QOpenHD at the moment
  • Report problems with interference/corruption on the screen, but first:
    • Make sure the wifi card(s) power supply is adequate, if you have them directly connected to USB they may not be getting the proper voltage/current even if the Pi itself is not showing a low voltage warning
    • Try to track down and exclude any external interference first, for example nearby devices transmitting on any frequency
    • Try removing any extra USB devices that may cause USB bus problems (pi4 should not be affected, pi3/zero might be due to the single USB bus on the processor)
    • If you're sure that a new release may be causing video problems, see what the CPU usage was at the time (either on the OSD, or better yet via ssh in htop, where you might be able to spot a specific process using too much CPU time)
    • There have been reports that Pi4 HDMI can interfere with wifi frequencies, including the hotspot, but there are some things we can change to prevent this from happening
  • The boot screen may flicker for a moment when a TX is connected to the ground, this is expected at the moment (there is a bug in a system library we use)
  • The boot screen and QOpenHD may not show up on Raspberry Pi Zero on the Buster releases, this is not intentional it will be resolved in a minor update (2.0.x) once 2.0 stable is released
  • The first few messages may not show up on the boot screen at the moment
  • The size of OSD elements in QOpenHD is fairly small on high resolution screens, HiDPI is not currently being detected automatically. If necessary you can increase the scale in the QOpenHD settings panel under App->Screen. This will be configurable through a settings file soon for those won't don't have or want a mouse/touchscreen connected to your ground station
  • Video may stutter or freeze when ground recording to SD card is enabled with VIDEO_TMP=sdcard
    • This is an old problem, the settings file has had a note about it for probably a year or more
    • A temporary solution is to use VIDEO_TMP=memory instead
    • Will be resolved soon by separating the recording system from the rest of the video pipeline so it can't affect live flight
  • Some parts of the old OSD may be reversed when Vector Open Telemetry is in use (#283)
Assets 2