Skip to content

dRonin 2016-10-04.1 Release ("Quixote")
Compare
Choose a tag to compare
@mlyle mlyle released this 12 Oct 01:59
· 2209 commits to next since this release
Release-20161004.1
b543ac3

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.

Assets 7
Loading