dRonin 2018-02-12.2 release ("Wired")

@mlyle mlyle released this Feb 13, 2018 · 528 commits to next since this release

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.

dRonin 2017-07-17 Release ("Neat")

@mlyle mlyle released this Jul 17, 2017 · 983 commits to next since this release

It's been a long time coming--- but we're pleased to announce the new "Neat" release of the dRonin flight controller firmware and ground control station.

A lot has changed, so please read the release notes carefully.

Please see the documentation at: http://dronin.org/docs/

@jhitesma has produced an excellent upgrading video that you may want to watch if this is your first time upgrading dRonin.

Jump ahead to: Changes / Errata & troubleshooting

Major changes since last release:

  • Core flight firmware improvements
    • "NeoTune" next generation cross-correlation based tune algorithm yields better results-- even in the presence of vibration and other anomalies.
    • Improved sensor filtering implemented in the Sensor module.
    • Improvements to attitude estimation performance in the presence of vibration.
    • Support 4WIF passthrough for ESC programming across 'MSP' protocol interface.
    • Improvements to realtime behavior and removal of jitter.
    • Mixer architecture changes improve performance and allow custom mixers that use "accessory" data across outputs (and lays the groundwork for future control improvements).
    • Several fixes made to telemetry/configuration protocol performance across flight and GCS.
  • Changes in supported targets
    • Support added for PikoBLX micro flight controller
    • Support added for Seriously Pro F3 EVO ("SPRF3E") and various clones (e.g. FrSky XSRF3E). Note that only the "EVO" SPRF3 variants are supported.
    • REMOVED SUPPORT FOR F1 FLIGHT CONTROLLERS (CC3D, NAZE). Use "Artifice" for these controllers.
  • Target improvements
    • Support for WS2811/2812 LEDs added to select F3 targets (Lux, SPRF3E)
    • DShot using DMA implemented for OSD targets (original Brain, Seppuku, and BrainRE1)
    • Improvements to on screen display reliability on original Brain and Seppuku flight controllers.
    • Various improvements to the AQ32 target: flash erase, DAC annunciation, and WS2811 features. However, PWM RX support was removed.
    • Moved all Invensense targets to a common, improved sensor driver.
    • Simulation/flyingpi: move to OS-native threading model instead of embedding ChibiOS; put the simulator binaries for ARM and x86 in the Linux packages.
  • External hardware support
    • Support for TBS Crossfire receiver protocol
    • Preliminary support for OmniPreSense millimeter-wave radars.
    • Improvements to IBus protocol reliability.
  • Miscellaneous
    • Simple UI added for annunciator (LED, buzzer) settings.
    • Various bugfixes and performance improvements.
    • Improvements to UI styling.

Errata & Troubleshooting

  • THIS RELEASE REMOVES SUPPORT FOR F1 FLIGHT CONTROLLERS (CC3D, NAZE). 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 XP is no longer supported; Windows Vista or later is required for operation.
  • Windows: If you are on Windows Vista, 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.9 ("Mavericks") 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: NOTE THE UDEV RULES HAVE CHANGED ONCE AGAIN you will 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-20170717.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.

dRonin 2017-02-13.1 Release ("Artifice")

@mlyle mlyle released this Mar 9, 2017 · 1742 commits to next since this release

Woot-- with the imminent release of new hardware-- it's time to kick this release out the door.

This was a little bit longer than our normal release cycle (4 months), and we spent some of the time distracted with hardware... but here we are, with plenty of new stuff.

Please see the documentation at: http://dronin.readme.io

@jhitesma has produced an excellent upgrading video that you may want to watch if this is your first time upgrading dRonin!.

Note: This is a hotfix to the Artifice release which corrects a major regression in the BrainRE1 target where LED support did not work, and includes some other minor fixes.

Jump ahead to: Changes / Errata & troubleshooting

Major changes since last release:

  • Support for Seppuku flight controller added.
  • BrainFPV fixed a critical bug in the RE1 target which caused in-flight resets when there were glitches in the vertical sync signal.
  • Improved accuracy of BMP280 altimeters in the driver.
  • Accuracy of attitude estimation for on-screen display and leveling modes improved on F3/F4 targets.
  • Stabilization module improved to reject noise and compensate for jitter better.
  • Autotune improved: measurement consistency was increased and F3/F4 targets now capture advanced data that will be used in the next generation of the algorithm.
  • Preliminary support added for DShot 300/600/1200 on all targets.
  • Preliminary support for DAC audio on Seppuku target-- audio telemetry and "beep" alarms.
  • Added support for WS2811 LEDs on BrainRE1, Seppuku, Revolution, Quanton.
  • Added new "AcroDyne" flight mode that allows dynamic acceleration at high stick deflection.
  • Corrected an issue lowering telemetry link performance-- both directly attached USB and radio/serial links.
  • Camera tilt angle for reprojection can now be set using TxPID module.
  • Fixed a regression with CC3D PWM input and OneShot/high frequency output.
  • Improvements to ESC calibration safety and interoperability with recent BLHeli.
  • BrainRE1 was updated to use the proper buzzer infrastructure like other targets.
  • Improvements to input wizard and receiver activity framework.
  • RFM22B/TauLink/OpLink RSSI is now available as an RSSI source.
  • Removed the PicoC language and existing waypoint persistence mechanisms in anticipation of future work.
  • LightTelemetry improved for better utilization of slow telemetry links.
  • Usability: Setup wizard added support for additional receiver types (SRXL, iBus)
  • Usability: Input pane shows status of RC inputs.
  • Usability: Switches are shown better in Input Wizard.
  • Usability: Improved tool-tips and descriptions of UAV objects in many places.
  • Usability: GCS now prevents from being started multiple times at once and associated anomalous behavior.
  • Usability: Improvements to wiring diagrams in GCS.
  • Improvements to various behavior on Raspberry Pi / FlyingPIO target.
  • Infrastructure/developer improvements: cleanup, upgrade to Qt5.8, etc.
  • Various crashes and defects fixed in GCS.

Errata & Troubleshooting

  • 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 XP is no longer supported; Windows Vista or later is required for operation.
  • Windows: If you are on Windows Vista, 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.9 ("Mavericks") 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: NOTE THE UDEV RULES HAVE CHANGED ONCE AGAIN 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 . Also please ensure your user is in both the plugdev and dialout groups as is appropriate for your distribution.
  • Naze32: support is still early. There is no support for flashing boards in GCS. The procedure to flash a Naze32 is here. Note that this doesn't upgrade your settings.

dRonin 2016-10-04.1 Release ("Quixote")

@mlyle mlyle released this Oct 12, 2016 · 2155 commits to next since this release

Hey again everyone! Time for a new release!

We've run a quick release cycle — less than 2.5 months — but we still have plenty of goodies for everyone.

Please see the documentation at: http://dronin.readme.io

@jhitesma has produced an excellent upgrading video that you may want to watch if this is your first time upgrading dRonin!

Note: that this is a minor hotfix that improves appearance in a couple of places (taskbar and BrainRE1 hardware config appearance) and corrects an issue with the input wizard.

Jump ahead to: Changes / Errata & troubleshooting

Major changes since last release:

  • Support for 'ExpoM' allows more intuitive and better control of stick response. Please see the documentation on configuring rates here
  • Support cut-down versions of Revolution flight controller that do not have advanced sensors.
  • Control deadbands allow having lower gains when errors are very low. This lowers wear on actuators / servos on planes, and can improve propwash-induced wiggles on multirotors.
  • Initial support for buzzer on DTFc, Lux, Quanton, and Naze32 targets.
  • Preliminary support for direct-character OSD on AQ32 and forthcoming targets with onboard MAX7456/AB7456 OSD IC.
  • Support different blink/buzzer error codes for flight alarms from annunciator subsystem.
  • Preliminary support added for "FlyingPi" Raspberry Pi shield and running the flight code directly on Raspberry Pi 2 and 3.
  • Preliminary support to run on PlayUAVOSD hardware, receiving MSP data and displaying advanced graphical OSD.
  • IPv6 support on simulator/control sockets.
  • Upgrader and cloud service was improved so that upgrade now works correctly to/from most development builds.
  • S.Port telemetry reliability is improved on F3 flight controllers.
  • Acroplus integral handling significantly improved.
  • Support additional UART/alternate multiport configuration on BrainRE1.
  • Support for 560Hz / 760us centerpoint servos on output pane.
  • Remaining flight time estimates from the battery subsystem are improved.
  • Receiver activity detection used in the input wizard is improved, particularly in the cases when RSSI channels are injected.
  • Handle cases where timer resources used for PPM clash with output channels somewhat better (CC3D, Sparky2).
  • Core controls: latency from manual input to actuators has been significantly reduced, especially on high-update-rate radios.
  • A common driver is now used for most Invensense sensors.
  • There is a functional crash-reporting system for the GCS on all three platforms, helping us to improve reliability of the ground suite.
  • GCS is now built with MSVC on Windows and includes the Visual C runtime and software OpenGL for platforms that need it.
  • Many, many usability and reliability improvements to the ground control suite.

Errata & Troubleshooting

  • Windows: Windows XP is no longer supported; Windows Vista or later is required for operation.
  • Windows: If you are on Windows Vista, 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.9 ("Mavericks") 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: NOTE THE UDEV RULES HAVE CHANGED 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 . Also please ensure your user is in both the plugdev and dialout groups as is appropriate for your distribution.
  • Buzzer: existing bootloaders do not know about the buzzer and do not drive it, which can result in a beep or spooky ghost noises during flashing operations. Also, some Naze32 buzzers are unsupported because they have the opposite polarity from modern Naze (and will always beep).
  • SUMD: Ranges have changed for higher resolution and consistency with other protocols. Be sure to recalibrate your radio if using SUMD.
  • Naze32: support is still early. There is no support for flashing boards in GCS. The procedure to flash a Naze32 is here. Note that this doesn't upgrade your settings.