EmuConfigurator 0.4.3

EmuConfigurator 0.4.3

Warning

DJI components bypass Configurator safety-checks. Do not attempt arming while connected to Configurator with LiPo plugged. Always remove propellers and use a smoke-stopper for extra safety.

• Adds support for EmuFlight 0.4.3
• Full list of changes: 0.4.3...0.4.1

Contributors: @nerdCopter @mricho @Alden-wrk
Additional thanks to @iNavFlight and @betaflight for ported/modified GPL code dealing with MSP-Display-Port.

Changes in this Release:

4ef2498be	dependabot[bot]	2024-06-20	Bump socket.io from 4.5.2 to 4.7.5 (#527)
5175d8fa1	nerdCopter	2024-05-31	fix CLI error red (#526)
1b2648d87	Alden-wrk	2024-05-15	ADD APM32 MCU USB_DFU (#524)
f265109e3	nerdCopter	2024-04-30	fix URL links (#522)
20b9663bb	nerdCopter	2024-04-30	version bump 0.4.3 (#521)
b25d0c223	nerdCopter	2024-04-30	MSP 1.54 support (#510)
d77b095c8	nerdCopter	2024-04-30	add missing discord icon (#518)
5414e2961	dependabot[bot]	2024-04-21	Bump decode-uri-component from 0.2.0 to 0.2.2 (#479)
e893cb16d	dependabot[bot]	2024-04-21	Bump es5-ext from 0.10.53 to 0.10.64 (#514)
ab50a62de	dependabot[bot]	2024-04-21	Bump follow-redirects from 1.15.1 to 1.15.5 (#505)
e72d9e6ac	dependabot[bot]	2024-04-21	Bump socket.io-parser from 4.2.1 to 4.2.4 (#496)
964970c7d	dependabot[bot]	2024-04-21	Bump get-func-name from 2.0.0 to 2.0.2 (#495)
a3dc565b4	dependabot[bot]	2024-04-21	Bump semver from 5.7.1 to 5.7.2 (#494)
0fe528973	dependabot[bot]	2024-04-21	Bump ua-parser-js from 0.7.31 to 0.7.37 (#493)
c0777fb5c	dependabot[bot]	2024-04-21	Bump qs from 6.5.2 to 6.5.3 (#481)
c8bd4d259	nerdCopter	2024-04-21	OSD tab - unhide Core/ESC temperature elements form non-export-mode (#515)
60bd0d99d	nerdCopter	2024-04-20	add Discord link/log and and update landing page (#512)
4379eb689	nerdCopter	2024-04-11	Remove Patreon; replace with Open-Source statement (#511)
66eb2a7b0	nerdCopter	2024-02-07	modding HDZero PR #449 to revert to 5bit compatible OSD element positioning. (#500)
67ecb6b50	nerdCopter	2024-02-07	HDZero OSD support in configurator (#449)
605ad0953	nerdCopter	2023-12-20	[gh actions] use date as tag for dev-unstable dev-master (#502)
245dad45a	nerdCopter	2023-12-19	[gh actions] fix artifacts for release/dev-testing (#501)
5205a8b20	nerdCopter	2023-12-19	OSD tab - programmatically hide unused OSD profiles from UI (#499)
8e9d2d6e4	nerdCopter	2023-12-06	force macos github actions to work (#489)
c2892e2dc	nerdCopter	2023-12-01	node 12 ; osx fix (#488)
97d72a1a0	dependabot[bot]	2022-11-05	Bump karma from 6.3.4 to 6.4.1 (#471)
6f15c4dd6	nerdCopter	2022-07-29	bump version 0.4.1 (#467)

EmuConfigurator 0.4.1

EmuConfigurator 0.4.1

WARNING: DJI components bypass Configurator safety-checks. Do not attempt arming while connected to Configurator with LiPo plugged. Always remove propellers and use a smoke-stopper for extra safety.

Notice: Windows reporting virus. There is no virus. This is a false-positive.

Changelog:

• Integrated iforce2d.net's MixerCalc (with permission).
• Analog VTX tab (3 years late).
• minor fixes & dependency updates.
• Full list of changes (0.4.0...0.4.1)

Delayed:

• HDZero support is not yet released. You may find working HDZero test-builds by joining Discord (https://discord.gg/BWqgBg3).

Tips:

• Save a dump all from any existing Flight Controller configurations. Reference it for resources, OSD, serial, etc.
• Upgrading from 0.4.0, no need to full-chip erase. Upgrading from any earlier version requires full-chip erase.
• Most all tuning options can be set using the OSD!
• Reference firmware release notes, EmuFlight wiki and EmuConfigurator wiki for additional information.
• Join Discord for help: https://Discord.gg/BWqgBg3

EmuFlight Logo in OSD/Fonts:

• Fonts should be uploaded to your FC. Note that some FC require vbatt power to save correctly.

Known issues:

• Stick Point Attenuation (SPA) values are saved in PID profiles, not rate-profiles.
• Switching to PID Profile 2 or 3 (profile 1 or 2 in CLI) has been known to hang the USB connection, requiring unplug/replug. PID loop speed seems to affect this
• CLI Building AutoComplete Cache sometimes stalls requiring Unplug/Replug. Make sure to have flashed with full-chip erase. If it repeatedly fails, consider disabling AutoComplete.
• CLI buffer sometimes fails (Windows only). Optionally, disable AutoComplete and restart Configurator.
• Foreign language translations are highly out-of-date.
• Windows users: It is highly recommended to Un-Install prior EmuConfigurator versions and delete C:\Program Files\Emuflight\ due to this inherited bug. Use the install/uninstall/upgrade process. However, you may prefer to use the zip-file releases since they do not require installation.
• 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 or sudo xattr -dr com.apple.quarantine /Applications/EmuFlight\ Configurator.app
• Linux users: require working udev rules and group-membership. (EmuConfigurator>Wiki).

Please report Configurator-specific bugs to

• https://github.com/emuflight/EmuConfigurator/issues

Please report Firmware-specific bugs to

• https://github.com/emuflight/EmuFlight/issues

Thank you

• Thanks to EmuFlight contributors, testers, and enthusiasts.
• Thanks to freedom loving developers around the world whom release source-code under the GPL license for reuse and modification.
• Thanks to iforce2.net's Chris C. for allowing reuse and modification of his MixerCalc.
• Please check CREDITS.txt for code-contributors.

--

Changes Summary:

6f15c4dd bump version 0.4.1
608b07f1 Bump thenify from 3.3.0 to 3.3.1 (#466)
58d55353 Bump object-hash from 2.0.3 to 3.0.0 (#435)
a4ffe2ae Bump plist from 3.0.1 to 3.0.6 (#463)
58fbe279 Bump copy-props from 2.0.4 to 2.0.5 (#460)
9e2b075d Bump follow-redirects from 1.14.1 to 1.15.1 (#452)
d7c21caf Bump ajv from 6.12.0 to 6.12.6 (#430)
145d76fa Bump engine.io from 4.1.1 to 4.1.2 (#420)
c2e4d787 Bump jbox from 1.3.2 to 1.3.3 (#415)
82ee4c13 VTX tab - fix power level offset proper (#462)
409bbac9 VTX tab - fix power level offset (#461)
aeacc5f2 connect/flash remains disabled until ports list populated (#458)
5df3f721 VTX tab (#457)
85efd27f add ImpulseRC Driver Fixer Link (#454)
953a8972 nwjs 0.50.3 (#453)
7964aa9f integrated iforce2d.net mixercalc (#447)
4ca52f33 Allow IMUF W less than 3 (Off) for 0.3.3+ (MSP 1.50+) (#425)
c6717aa5 update dependencies (#411)
94fc4ae0 Bump path-parse from 1.0.6 to 1.0.7 (#402)
1598f861 ajust rateDynamics sliders width to allow value 100+ visible in number field (#409)
8b9a62b1 Do not list firmware release >= 1.0.0 (#408)
ddf3ccc5 Upgrade to GitHub-native Dependabot (#350)
a41cd617 bump version 0.4.0 (#403)

EmuConfigurator 0.4.0

EmuConfigurator 0.4.0

WARNING: DJI components bypass Configurator safety-checks. Do not attempt arming while connected to Configurator with LiPo plugged. Always remove propellers and use a smoke-stopper for extra safety.

Notice: Windows reporting virus. There is no virus. This is false-positive. Suspect outdated node_modules which cannot be upgraded at the moment.

• VirusTotal Report 64bit
• VirusTotal Report 32bit

Windows 11 users, please note there is a separate Windows11 version here. We need testing and feedback please.

Changelog:

• Support for 0.4.0 Features
• Minor 3rd party dependency update
• Less obtrusive logo in CLI

Tips:

• Save a dump all from any existing Flight Controller configurations. Reference it for resources, OSD, serial, etc.
• Most all tuning options can be set using the OSD!
• Reference firmware release notes, EmuFlight wiki and EmuConfigurator wiki for additional information.
• Join Discord for help: https://Discord.gg/BWqgBg3

Fonts:

• Fonts should be uploaded to your FC for firmware 0.3.X+. Note that some FC require vbatt power to save correctly.

Known issues:

• Stick Point Attenuation (SPA) values are saved in PID profiles, not rate-profiles.
• Switching to PID Profile 2 or 3 (profile 1 or 2 in CLI) has been known to hang the USB connection, requiring unplug/replug. PID loop speed seems to affect this
• CLI Building AutoComplete Cache sometimes stalls requiring Unplug/Replug. Make sure to have flashed with full-chip erase. If it repeatedly fails, consider disabling AutoComplete.
• CLI buffer sometimes fails (Windows only). Optionally, disable AutoComplete and restart Configurator.
• Foreign language translations are highly out-of-date.
• Windows users: It is highly recommended to Un-Install prior EmuConfigurator versions and delete C:\Program Files\Emuflight\ due to this inherited bug. Use the install/uninstall/upgrade process. However, you may prefer to use the zip-file releases since they do not require installation.
• 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 or sudo xattr -dr com.apple.quarantine /Applications/EmuFlight\ Configurator.app
• Linux users: require working udev rules and group-membership. (EmuConfigurator>Wiki).

Please report Configurator-specific bugs to

• https://github.com/emuflight/EmuConfigurator/issues

Please report Firmware-specific bugs to

• https://github.com/emuflight/EmuFlight/issues

--

Changes in this Release:

a41cd61 bump version 0.4.0 (#403)
8282a63 MSP 1.51 / Presets 0.4.0 (#391)
4e9a1e2 MSP 1.51 UI (#389)
31ef1ce MSP 1.51 MSPHelper.js (#386)
262133b Github Actions building - separate artifacts by OS (#394)
387db80 transparent background image in CLI (#397)
2b24ce8 Bump gulp-yarn from 2.0.0 to 3.0.0 (#381)
7fa9244 Bump gulp-zip from 5.0.2 to 5.1.0 (#379)
83db09b bump version 0.3.6 (#387)

EmuConfigurator 0.3.6

EmuConfigurator 0.3.6

WARNING: DJI components bypass Configurator safety-checks. Do not attempt arming while connected to Configurator with LiPo plugged. Always remove propellers and use a smoke-stopper for extra safety.

Notice: Windows reporting virus. There is no virus. This is false-positive. Suspect outdated node_modules which cannot be upgraded at the moment.

• VirusTotal Report 64bit
• VirusTotal Report 32bit

Changelog:

• Fix LED dialog
• Fix for OSX BigSur
• Prevent targets listing twice
• Cleaner EmuFlight Logo
• IMUF per-axis only in expert-mode.
• Protect from unsupported MSP in newer release.
• Backend & 3rd-party dependency updates.
• This is an interim release until 0.4.0 is ready.

Tips:

• Save a dump all from any existing Flight Controller configurations. Reference it for resources, OSD, serial, etc.
• Most all tuning options can be set using the OSD!
• Reference firmware release notes, EmuFlight wiki and EmuConfigurator wiki for additional information.
• Join Discord for help: https://Discord.gg/BWqgBg3

Fonts:

• Fonts should be uploaded to your FC for firmware 0.3.X. Note that some FC require vbatt power to save correctly.

Known issues:

• Stick Point Attenuation (SPA) values are saved in PID profiles, not rate-profiles.
• Switching to PID Profile 2 or 3 (profile 1 or 2 in CLI) has been known to hang the USB connection, requiring unplug/replug. PID loop speed seems to affect this
• CLI Building AutoComplete Cache sometimes stalls requiring Unplug/Replug. Make sure to have flashed with full-chip erase. If it repeatedly fails, consider disabling AutoComplete.
• CLI buffer sometimes fails (Windows only). Optionally, disable AutoComplete and restart Configurator.
• Foreign language translations are highly out-of-date.
• Windows users: It is highly recommended to Un-Install prior EmuConfigurator versions and delete C:\Program Files\Emuflight\ due to this inherited bug. Use the install/uninstall/upgrade process. However, you may prefer to use the zip-file releases since they do not require installation.
• 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 or sudo xattr -dr com.apple.quarantine /Applications/EmuFlight\ Configurator.app
• Linux users: require working udev rules and group-membership. (EmuConfigurator>Wiki).

Please report Configurator-specific bugs to

• https://github.com/emuflight/EmuConfigurator/issues

Please report Firmware-specific bugs to

• https://github.com/emuflight/EmuFlight/issues

--

Changes in this Release:

83db09b bump version 0.3.6 (#387)
745a525 Limit UI for MSP max-version supported (#383)
533d6f0 Bump short-unique-id from 3.2.3 to 4.3.3 (#373)
37ef772 Bump marked from 2.0.0 to 2.0.7 (#372)
2d131cd Bump temp from 0.9.1 to 0.9.4 (#371)
ce98f16 expert per-axis imuf (#378)
75afbfd IMUF expert-mode (per-axis)  vs basic-mode (single Q, LPF) (#376)
0522016 locale/en for CRSFv3 24 aux channels (#345)
c03250a slightly better GitHub action (#375)
a038e10 Update issue templates (#368)
9186682 bring emu logo from R to TM (#357)
bbbedc1 Update messages.json (#367)
8fe0066 Bump karma from 6.1.1 to 6.3.3 (#369)
8c0ef90 Bump ws from 7.4.2 to 7.4.6 (#366)
f2c7843 Bump sinon from 9.0.3 to 9.2.4 (#365)
aec4fef Bump jbox from 1.2.0 to 1.3.2 (#363)
a893007 Prevent target list from loading twice on app launch with show unstable is not selected (#362)
ec442b7 Bump i18next from 19.8.7 to 20.3.0 (#358)
52595ab [Security] Bump hosted-git-info from 2.8.8 to 2.8.9 (#354)
ef1238f Bump follow-redirects from 1.13.0 to 1.14.1 (#355)
2487a7e [Security] Bump lodash from 4.17.20 to 4.17.21 (#352)
f981255 [Security] Bump y18n from 3.2.1 to 3.2.2 (#340)
9f45f88 Bump chai from 4.2.0 to 4.3.4 (#337)
807a2bf [Security] Bump yargs-parser from 5.0.0 to 5.0.1 (#335)
7ef3f60 GitHub Actions Draft Releases to dev-unstable and dev-master (#351)
ae7f4e8 html code block cleanup for pid_tuning.html (#344)
bd58b23 nw.js -- updates NWjs for linux/OSX, fixes OSX BigSur. retains OLD NWjs for Windows (#310)
53229ce Bump tslib from 2.0.1 to 2.1.0 (#321)
261b395 Bump karma from 5.2.3 to 6.1.1 (#320)
845d45f [Security] Bump marked from 1.2.8 to 2.0.0 (#318)
002f30f Bump short-unique-id from 3.0.4 to 3.2.3 (#316)
7738d05 Bump makensis from 0.21.2 to 0.23.4 (#315)
5626ee3 Bump dot-prop from 5.3.0 to 6.0.1 (#313)
1a28fd2 Bump fs-extra from 9.0.1 to 9.1.0 (#312)
d7cf70f Bump i18next from 19.7.0 to 19.8.7 (#311)
e7acb3b Bump marked from 1.1.1 to 1.2.8 (#308)
556e38d [Security] Bump socket.io from 2.3.0 to 2.4.1 (#307)
c091349 [Security] Bump ini from 1.3.5 to 1.3.8 (#297)
23eca5f Bump yarn from 1.22.5 to 1.22.10 (#278)
52bde8b Bump karma from 5.2.2 to 5.2.3 (#276)
331b629 Bump del from 5.1.0 to 6.0.0 (#275)
52d7ca6 Fix LED color sliders, no longer closes when hover away from color (#306)
6fc837b 0.3.5 EmuConfigurator version bump (#305)

EmuConfigurator 0.3.5

EmuConfigurator 0.3.5

WARNING: DJI components bypass Configurator safety-checks. Do not attempt arming while connected to Configurator with LiPo plugged. Always remove propellers and use a smoke-stopper for extra safety.

Changelog:

• PID/Tuning Presets now work with iRelax and dBoost values for EmuFlight 0.3.2+
• OSD CRSF Widgets for 0.3.2+
• OSD Percent mAh used widget for 0.3.3+
• IRC GHOST protocol selector for 0.3.3+
• Hide NFE from PID-tab for 0.3.3+ because it's now on an aux-mode switch.
• Some minor backend stuff

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!
• Reference firmware release notes, EmuFlight wiki and EmuConfigurator wiki for additional information.
• Join Discord for help: https://Discord.gg/BWqgBg3

Fonts:

• v2 fonts should be uploaded to your FC for firmware 0.3.X. Note that some FC require vbatt power to save correctly.
• 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 or 2 in CLI) has been known to hang the USB connection, requiring unplug/replug. PID loop speed seems to affect this
• CLI Building AutoComplete Cache sometimes stalls requiring Unplug/Replug. Make sure to have flashed with full-chip erase. If it repeatedly fails, consider disabling AutoComplete.
• CLI buffer sometimes fails (Windows only). Optionally, disable AutoComplete and restart Configurator.
• Foreign language translations are highly out-of-date.
• Windows users: It is highly recommended to Un-Install prior EmuConfigurator versions and delete C:\Program Files\Emuflight\ due to this inherited bug. Use the install/uninstall/upgrade process. However, you may prefer to use the zip-file releases since they do not require installation.
• 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 or sudo xattr -dr com.apple.quarantine /Applications/EmuFlight\ Configurator.app
• Linux users: require working udev rules and group-membership.

Please report Configurator-specific bugs to

• https://github.com/emuflight/EmuConfigurator/issues

Please report Firmware-specific bugs to

• https://github.com/emuflight/EmuFlight/issues

--

EmuConfigurator 0.3.4

EmuConfigurator 0.3.4

WARNING: DJI components bypass Configurator safety-checks. Do not attempt arming while connected to Configurator with LiPo plugged. Always remove propellers and use a smoke-stopper for extra safety.

Changelog:

• Allow sharpness=0 for EmuFlight 0.3.2 and IMUF 250
• Add iTerm Relax fields for EmuFlight 0.3.2
• Add DBoost fields for EmuFlight 0.3.2
• 3rd party dependency updates

Notes:

• For now, CRSF OSD Widgets still show as "UNKNOWN".
• For now, Presets will reset iTerm-Relax and DBoost to firmware defaults.

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!
• Reference firmware release notes, EmuFlight wiki and EmuConfigurator wiki for additional information.
• Join Discord for help: https://discord.gg/gdP9CwE

Fonts:

• New v2 fonts should be uploaded to your FC for firmware 0.3.X. 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 or 2 in CLI) has been known to hang the USB connection, requiring unplug/replug.
• CLI Building AutoComplete Cache sometimes stalls requireing Unplug/Replug. Make sure to have flashed with full-chip erase.
• CLI buffer sometimes fails (Windows only). Optionally, disable AutoComplete and restart Configurator.
• Foreign language translations are highly out-of-date.
• Windows users: It is highly recommended to Un-Install prior EmuConfigurator versions and delete C:\Program Files\Emuflight\ due to this inherited bug. Use the install/uninstall/upgrade process. However, you may prefer to use the zip-file releases since they do not require installation.
• 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 or sudo xattr -dr com.apple.quarantine /Applications/EmuFlight\ Configurator.app
• Linux users: require working udev rules and group-membership.

Please report Configurator-specific bugs to

• https://github.com/emuflight/EmuConfigurator/issues

Please report Firmware-specific bugs to

• https://github.com/emuflight/EmuFlight/issues

--

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 or 2 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 delete C:\Program Files\Emuflight\ due to this inherited bug. Always use the install/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 or sudo xattr -dr com.apple.quarantine /Applications/EmuFlight\ Configurator.app
• Linux users: require working udev rules and group-membership.

Please report Configurator-specific bugs to

• https://github.com/emuflight/EmuConfigurator/issues

Please report Firmware-specif bugs to

• https://github.com/emuflight/EmuFlight/issues

--

EmuConfigurator 0.3.2

This EmuConfigurator supports 0.1.0, 0.2.0-RC1, and 0.3.X.

Changlog: 0.3.2 failsafe option for gpsrescue fix / Dynamic_filter fix

• *** Please make fresh install of Emuflight 0.3.1

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!
• 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 delete C:\Program Files\Emuflight\ due to this inherited bug. Always use the install/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 or sudo xattr -dr com.apple.quarantine /Applications/EmuFlight\ Configurator.app
• The OSX build may or may not fail to flash firmware. We are reviewing/verifying. Someone reported you must click "Flash" twice. Once for DFU mode, and another to flash. Strong apologies if yours fails, 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

• https://github.com/emuflight/EmuConfigurator/issues

--

EmuConfigurator 0.3.1

This EmuConfigurator supports 0.1.0, 0.2.0-RC1, and 0.3.0.

Changlog: 0.3.1 Dynamic_Notch feature and min/Q values bugfix.

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 delete C:\Program Files\Emuflight\ due to this inherited bug. Always use the install/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 or sudo 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

• https://github.com/emuflight/EmuConfigurator/issues

--

EmuConfigurator 0.3.0

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 delete C:\Program Files\Emuflight\ due to this inherited bug. Always use the install/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 or sudo 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

• https://github.com/emuflight/EmuConfigurator/issues

--