New
20150922-f069ece425
- Navigation, return-to-home, and path following significantly improved.
- New targets added: Naze32/OpenNaze and AeroQuad32 (aq32).
- TauLinkModule and ground-side UAVO to FrSky telemetry bridging support added.
- It is now possible to build the GCS in MSVC. The packaging infrastructure has not been updated for this, but future releases will be built with MSVC for enhanced performance and stability.
- Helicopter support improved; many bugfixes were made.
- It is possible to also use the throttle stick to control altitude in position hold mode, by manually setting vtolpathfollowersettings.LoiterAllowAltControl and ThrottleControl to True.
- A new "zippy loiter" mode is available when in position-hold mode. The pitch/roll inputs can control moderately aggressive multirotor position changes, and when stick is neutral it holds position. The GPS and position control loop is still coupled at all times, but it feels much more interactive than it did before.
- An "AcroPlus" flight mode, similar to Acro+ in OpenPilot and other projects, was added. Large stick inputs become direct actuator activation.
- Gyro lowpass filters are now target and sampling frequency independent, and configurable in a UAVO in terms of cutoff frequency in Hz (StabilizationSettings.GyroCutoff). Helicopter and large multirotor users may want to decrease this value; 250-size and smaller often benefit from increasing it. (Default tuning is for the most part general purpose, though).
- Flight modes display properly in minimosd-extra over MavLink.
- The GCS is now built using QT 5.5.
- Sparky2 now uses ChibiOS.
- On many targets, a missing external magnetometer no longer results in a boot panic.
- FrSky support updated to work better with newer OpenTX, and various encoding improvements were made.
- SPI runs at faster speed on some targets, reducing CPU consumption
- The default PPM pin on CC3D was changed to match OpenPilot convention; there's still a setting for existing boards that uses the old pin but it is not compatible with OneShot.
- Various cleanups were made for developers; code and make infrastructure de-duplicated some.
- Various small GCS bugfixes and enhancements were made.
- "RevoMini" target improved. PicoC support returns. This requires a new bootloader.
- Small changes were made to default tuning. Default tuning is still intended to be quite conservative but closer to working well for more users.
- TxPid now covers various nav/vtolpathfollower parameters.
- Removal of obsolete/unmaintained targets-- revolution prototype, freedom.
Known issues:
- Naze32 support is still early. The board setup wizard doesn't function; there is no ADC support yet; there is no support for flashing boards in GCS.
- OpenLRS reliability. Increased number of channels from default (more than 6) definitely causes OpenLRS failsafe / motor interruptions. There is possible reliability issues with the default configuration, too. Most likely the cause is that we are too quick to failsafe compared to "real" OpenLRS modules/code.
- For Linux you will have to install .udev rules for the device. This is the likely cause if you cannot connect to it. To do this download the udev permissions file from here and then run sudo cp taulabs.udev /etc/udev/rules.d/45-taulabs-permissions.rules && sudo udevadm control --reload-rules
- For Windows if you have any connectivity issues, please uninstall all the drivers associated with your hardware and reboot.
- FlyingF3 does not have enough memory to save telemetry rate settings for all object