Skip to content

dRonin 2018-02-12.2 release ("Wired")
Compare
Choose a tag to compare
@mlyle mlyle released this 13 Feb 06:52
· 582 commits to next since this release
Release-20180212.2
020e58f
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.

We've taken our time with the "Wired" release of dRonin, and hope you enjoy flying it just as much as we have enjoyed making it.

As always, please read the release notes, and see the documentation at: http://dronin.org/docs/

Please note that incorrect artifacts were briefly released, so this is a hotfix

Jump ahead to: Changes / Errata & troubleshooting

Major changes since last release:

As always, there's many small bug and usability fixes. But beyond that:

  • Core controls changes:
    • Introduced a "velcompass" mode for planes that cannot get a good compass calibration. Uses the direction of travel (bearing) as heading.
    • Antiwindup math is now properly used on inner (rate) loop, reducing overshoot.
    • Static dT value provides a small noise improvement to PID control.
    • Efficiency improvements (reduced CPU use, more deterministic control latency) achieved by collapsing most sensor tasks into callbacks and overall sensor monitor into stabilization task.
    • Autotune's calculation of yaw parameters has been significantly improved.
    • Autotune's resource utilization has been reduced by eliminating the autotune task.
    • Preliminary support for 3D flight (reverse thrust) added.
    • The throttle curve on the vehicle pane has been removed, because it does not play well with 3D flight or autonomous modes. If a throttle curve is desired, please use the one on your radio.
    • Small improvements have been made to the fixed wing path follower.
  • New functionality:
    • Buzzer can be controlled through an accessory channel.
    • Arming/disarming logic has been rewritten and is considerably safer.
    • Improvements to graphical OSD menus: corrections to menu bar displays, setting of camera angle, setting of battery capacity.
    • D-shot commands now supported, including sending "buzzer" values to motors.
    • RSSI is now lowpass-filtered so that it bounces around less.
    • 4WIF/ESC passthrough version number was increased to eliminate warning in blhelisuite 32.
    • RGB LED brightness is now dimmed to 33% when connected to USB.
    • Improvements have been made to telemetry (e.g. GCS connection) performance and reliability.
    • Improved performance of MS5611 pressure sensor.
  • Target support:
    • More variants of sensors and SPI flash supported on Revolution target; now most OmniBusF4 clones work.
    • Improvements were made to OmnibusF4 / Revolution WS28xx LED handling
    • Support added for most OmniBusF3 variants.
  • Behind the scenes:
    • Moved to Qt5.9.2 and newer flight compiler.
    • Preliminary support for loadable binary code extensions (not usable by end-users yet).
    • Python API was extended with proper object request APIs, XML canonicalization, multi-instance objects, etc.
    • Flight and GCS build properly with GCC 6 & 7.
    • Removed lots of duplicate code and makefile, and simplified the build system.
  • Support for running on larger embedded systems (flightd/flyingpi)
    • 64 bit compilation support added
    • Direct connection to receiver without flyingpio is now possible
    • Improvements to output and cross-compilation
    • Preliminary support for outside flight dynamics simulation (FlightGear, YaSim, etc)

Errata & Troubleshooting

  • You will probably need to reconfigure your craft's arming setting.
  • No support for F1 flight controllers. Use "Artifice" for these controllers.
  • USB/F4: A long-standing bug prevents reconnecting the flight controller by USB without a FC reset (e.g. when powered by external power). This can worsen communications when using a flaky USB cable. We intend to devote significant effort to fixing this soon.
  • Windows: Windows 7 or later is now required.
  • Windows: If you are on Windows 7 or 8 and receive a message "api-ms-win-crt-runtime-l1-1-0.dll is missing from your computer," please see https://support.microsoft.com/en-us/kb/2999226
  • Windows: If you are unable to communicate with the flight controller after plugging it in, please see this procedure for a possible solution.
  • OS X: OS X Version 10.11 ("Yosemite") or later is required to run GCS.
  • OS X: the application is unsigned; it is necessary to open Applications, right-click on dRonin GCS and select Open on the first launch.
  • Linux: You may have to install .udev rules for the device. The .deb package attempts to do this automatically. To do this manually (e.g. from the tarfile), download the rules and then sudo cp dronin-linux_Release-20180212.udev /etc/udev/rules.d/45-dronin-permissions.rules && sudo udevadm control --reload-rules . Also please ensure your user is in both the plugdev and dialout groups as is appropriate for your distribution.
Assets 8
Loading