Skip to content

Nightly 2020-3-1

Pre-release
Pre-release
Compare
Choose a tag to compare
@steveatinfincia steveatinfincia released this 02 Mar 15:32
nightly-2020-3-1
343d76c

Known issues

  • Video still has jitter in this release, don't fly with it
    • A new video decoder/renderer has already been written to replace the current one, it will be integrated soon (#57)
  • App can be started more than once on Windows/Linux (#61)
    • This is unintentional and will be fixed soon
  • Autohide for PiP may not be working correctly everywhere yet (#59)
    • This may cause PiP to always hide or stay visible all the time on some platforms
    • This is completely fixed in the new video decoder/renderer being worked on (#57), scheduled to be merged next week
  • Charts are currently disabled until they can be verified not to affect rendering
  • If you see a message like "Mavlink command failed" on the screen, you need to update the OpenHD image on the air and ground to at least nightly-2020-3-1
    • The message will be removed in the next release
  • GPIO user interface is temporary, will be replaced soon with something nicer
    • GPIOs will support custom names and possibly custom icons, and may be triggerable from the main OSD screen rather than requiring the detail panel to be open
    • Keep in mind that the GPIO numbering is based on the processor GPIO numbers, not pin numbers
    • So GPIO5 means BCM5, not pin 5
    • If you need a good reference for the GPIO numbers, see https://pinout.xyz/

Changes

  • Fix crash
  • Fix widgets showing up black
  • Fix PiP background frame changing with the widget text color
  • Fix GPIOs toggling back on or off after tapping checkboxes
    • Make sure you are using OpenHD image nightly-2020-3-1 or newer
  • Fix unintentional disconnect from the microservice router
  • Reload the air GPIO status for each pin if the air side reboots or a command fails
  • Add support for reliable Mavlink commands
    • QOpenHD will retry the command up to 5 times within a time limit of 1 second until the other side (flight controller, microservices) acknowledges receiving the command and that the command was successful
    • Supporting reliable mavlink commands is also a requirement for adding support for waypoints, running missions, and configuring flight controller parameters
  • Start tracking flight controller boot time
    • Will be used to autoload parameters and missions properly when the flight controller connects or reboots
Assets 5
Loading