EmuConfigurator 0.3.3
This EmuConfigurator supports 0.1.0, 0.2.0-RC1, and 0.3.X.
Edit: Some Windows® users reported increased CLI-tab buffer issues, so new downloads with _fixed
in the filename were added. _All Windows® users should use the _fixed
version. As a convenience, we now have .zip
files for Windows® that do not require installation.
Changlog:
- Fix PID-tab breakage if preset-files are missing and disconnected from Internet.
- Fix OSX Flashing.
- rateDynamics sliders.
- Miscellaneous fixes, verbiage (en), links and back-end dependency upgrades.
- Support for future firmware (0.3.2+) dShot2400/4800.
Tips:
- Save a
dump all
from any existing Flight Controller configurations. Reference it for resources, OSD, serial, etc. - You must re-tune for EmuFlight 0.3.X . Do not use 0.2.0 PID's. Do not use another flightware's PIDs.
- Most all tuning options can be set using the OSD!
Imperative:
- Flash with full-chip erase.
- DJI devices may bypass USB arming block, DO NOT attempt arming DJI component based quads while plugged into Configurator with propellers mounted. This is always how things should be done, but be warned that DJI will cause arming to be allowed in the Configurator!
- DJI [in]compatibility: https://github.com/emuflight/EmuFlight/wiki/DJI
- Helio/Strix will require a newer IMUF binary which is not backward-compatible to older EmuFlight. Flash IMUF first, then EmuFlight second. IMUF releases: https://github.com/emuflight/imu-f/releases
Update Fonts:
- New v2 fonts must be uploaded to your FC for firmware 0.3.0. Note that some FC require vbatt power to save correctly.
- Old v1 font crosshairs are also fixed for anyone stuck on old versions (0.1.0, 0.2.0).
Known issues:
- Stick Point Attenuation (SPA) values are saved in PID profiles, not rate-profiles.
- Switching to PID Profile 2 or 3 (
profile 1
or2
in CLI) has been known to hang the USB connection, requiring unplug/replug. - CLI's
Building AutoComplete Cache
sometimes stalls. Unplug/replug. Make sure to have flashed with full-chip erase. - Foreign language translations are highly out-of-date.
- Windows users: It is highly recommended to
Un-Install
prior EmuConfigurator versions and deleteC:\Program Files\Emuflight\
due to this inherited bug. Always use theinstall/uninstall/upgrade
process. - OSX Users: Depending on your OSX, you may be required to un-quarantine the Configurator download or installed App.
xattr -d com.apple.quarantine emuflight-configurator_0.3.*_macOS.dmg
orsudo xattr -dr com.apple.quarantine /Applications/EmuFlight\ Configurator.app
- Linux users: require working udev rules and group-membership.
Please report Configurator-specific bugs to
Please report Firmware-specif bugs to
--