Skip to content

dRonin 2016-01-20 release ("renatus")
Compare
Choose a tag to compare
@mlyle mlyle released this 27 Jan 03:40
· 4162 commits to next since this release
Release-20160120.3
26641ee

This is the first stable release of the dRonin flight controller firmware. We've been flying and having a lot of fun with this, and hope you will too!

This software is provided without any warranty. Use at your own risk!

The dRonin project is a fork of Tau Labs/OpenPilot flight firmware. The following changes have occurred since the previous Tau Labs endomorphism release:

  • Safety: Corrections to arm-switch configuration have been made to prevent inadvertent arming.
  • Safety: Reliability improvements to SBus protocol and switch arming.
  • Safety: OpenLRS synchronization and reliability improvements when used with the internal radio in Sparky2 or Revolution flight controllers.
  • Safety: Fix a stack overflow in attitude task relevant to navigation use cases.
  • Safety: Prevent uncommanded arming when input ranges are configured to invalid values.
  • Safety: Prevent invalid pulse lengths in OneShot configurations when flight controller is unable to keep up.
  • Safety: Prevent motors spinning up when "Test outputs" is left checked and the vehicle setup wizard is used.
  • Direct native support for BrainFPV flight controller.
  • Support for the Lumenier LUX flight controller.
  • Autotune is much more reliable and accurate.
  • Autotune now works on F1 targets (Naze32 and CC3D).
  • Adjustments to make return-to-home initial climb more intuitive and robust.
  • Improvements to event processing to reduce system jitter and improve system performance.
  • Support for VTX configuration on BrushedSparky flight controller.
  • Support for Multiwii Serial Protocol (MSP) to allow use of mwosd on-screen displays.
  • Support for displaying flight controller alarms and reset reasons on on-screen displays.
  • AltitudeHold-- maximum climb and descent rates may be configured separately.
  • Various corrections to helicopter support, including improvements to collective curve support.
  • PicoC support is restored on Colibri and FlyingF4.
  • New 16666Hz PWM output rate as preferred value for brushed flight controllers-- tradeoff between resolution and speed.
  • Flight controller resources freed, allowing full support for navigation on Sparky1 F3 platform.
  • Adjustments to gyro rate and filter defaults on many targets to make more sense.
  • Improvements to deadbands and ranges across all flight modes
  • Correctness fixes to battery module and analog-to-digital conversion.
  • OpenLRS telemetry of battery data now works correctly.
  • On-screen display of imperial units corrected.
  • Naze32 now supports battery monitoring, ADC, and the board setup wizard.
  • Ground control system improvements:
    • The audio-notification module may again be enabled.
    • The UAV object browser now has search functionality.
    • XML UAV object export now produces output that is easier to compare with outside tools (diff).
    • Input wizard behavior is improved-- will no longer generate short ranges or unbalanced switch channels.
    • Various usability, reliability, performance, and presentation improvements.
    • There is a crash reporting system on Windows and Linux environments.
    • "AutoTown", a cloud-sharing environment for autotune results.
    • GCS is much less likely to hang / become unresponsive on OS X.
    • Usage reporting infrastructure.
    • Crash reporting infrastructure on Mac OS X and Linux.
    • Branding / project name changes and improvements.
  • Python API is enhanced to support enums, direct pySerial communication with flight boards, etc.
  • Build: It is now considerably easier to set up a build environment on Windows.
  • Build: Packaging and reproducibility improvements.
  • Advanced: Actuator curve fitting option allows climb/descent
  • Advanced: OpenLog support on select targets

Errata:

  • This is Release-20160120.3, the first hotfix release of Renatus. Minor issues with helicopter support, throttle reversal, firmware in Debian package, and BrainFPV alarms were corrected.
  • If you are having problems after updating the firmware, e.g., the flight controllers is in a reboot-loop, erase all settings in your flight controller as follows:
    • In the GCS, go to the firmware screen and click Rescue, then connect your flight controller to USB. In the lower-right corner of the firmware screen, there is a "partition browser". Right click on the "Settings" patition and select "Erase". After the partition has been erased, click on "Boot" and your flight controller will have been reset to factory defaults.
    • It is generally possible to apply a .uav file of settings exported from Tau Labs to dRonin flight boards.
  • If using older Intel integrated graphics on Windows, you may need to follow this procedure to start GCS.
  • If you receive the message "The program cannot start because MSVCR120.dll is missing from your computer," you must download the Microsoft Visual C++ runtime to proceed. This is not usually necessary because most computers have installed software that requires this before.
  • Autotune on CC3D requires careful attention to input configuration because of memory limitations. Unused control types should not be enabled (e.g. disable PPM if you are using S.Bus). It's recommended you not configure over 5 input channels, too. In the next release we'll try to have more resources available so this is less critical.
  • Naze32 support is still early. There is no support for flashing boards in GCS. There is also currently no support for Naze32 rev6.
  • For Linux you will have to install .udev rules for the device. The .deb package attempts to do this automatically. To do this manually, download the udev permissions file and then run sudo cp _package.udev /etc/udev/rules.d/45-dronin-permissions.rules && sudo udevadm control --reload-rules
  • The Mac OS X artifact is unsigned; it is necessary to open Applications, right-click on dRonin GCS and select Open on the first launch.
Assets 7
Loading