EmuConfigurator 0.3.0
Pre-release
Pre-release
This EmuConfigurator supports 0.1.0, 0.2.0-RC1, and 0.3.0.
NEWS: Last moment bugs found from last minute mods -- Use pid-tab with caution, fixes are in progress. "news" will be modified and binaries uploaded when complete. Do not modify dynamic filter or antigravity via GUI until fixed. presets are modifying new features, please do this in CLI after every preset:
set dynamic_gyro_notch_q = 250
set dynamic_gyro_notch_min_hz = 150
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.0 . 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!
- 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 (
profile 1
in CLI) has been known to hang the USB connection, requiring unplug/replug. - When disconnected from the Internet, PID and other values sometimes may not populate in the PID Tuning tab. Configurator only checks online/offline at startup. If you open while online, then leave into the field (offline), then PID tab is sure to fail.
- 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.0_macOS.dmg
orsudo xattr -dr com.apple.quarantine /Applications/EmuFlight\ Configurator.app
- The OSX build may or may not fail to flash firmware. We are reviewing/verifying. Strong apologies if so, but you may have to use an alternate method of flashing until this is fixed (Windows or Linux). Consider a Virtual-Machine for running another OS. Some have reported other flightware Configurators (CleanFlight, iNav, BetaFlight) will flash EmuFlight, but this is also not verified fully. EmuFlight is provided without warranty of any kind, so be cautious.
- Linux users: require working udev rules and group-membership.
Please report bugs using the GitHub Issue Tracker
--