Flashing a firmware on Mac OS seems to only work on 0.2.0 and previous.
All versions released after (0.2.11, 0.2.12, 0.2.12-RC2) are not able to flash the firmware:
The flight controller goes into DFU mode but then nothing happens.
0.2.0 seems to work fine even flashing the latest firmware.

Known issue: "Switching to PID Profile 2 or 3 (profile 1 or 2 in CLI) has been known to hang the USB connection, requiring unplug/replug."

This happens with changing Rate Profile as well. But very little.

Windows 10 Home edition
Configurator: 0.3.4

• re: emuflight/EmuFlight#436
• mode tab automatically works
• need semver checking for removal in pid-tab.

Note that the OSX Configurator does not work with OSX Catalina. I'm not sure on this, but I believe this version of the OS does not allow for 32 bit programs to run. The OSX fork would have to be written in 64 bit. If you have any insight on this, I'd appreciate it. I'm stuck with Betaflight until this is resolved one way or another.

Both spektrum and the ghost system,use srxl2 bidirectional communication. Please add srxls2 support so both systems can be used.

Configurator 0.3.2 doesn't start since yesterday. I double click it and it remains on the bar, minimized. I tried to remove and reinstall it, issue still exists.

is there any hope or any word at all on emuflight using sharkbyte? I would love to switch all of my quads to emu but my favorites I run with the sharkbyte system and I would love love love to see support for that. thank you! cheers.

I can connect to the Emuflight 0.2.0 GUI, but to flash this new version, once I hit flash, it closes the USB connection. I did load the CP drivers, and it still doesn’t work. Frustrating.

MAC OSX running Sierra I believe. Worked with EMU 0.1.0

Hello..

I updated my MATEKF411RX FC to Emuflight then i checked my battery is saying 0v when i plug the battery

checked the resource on EmuFlight CLI it was ADC_BATT B00 and i changed it to A01 its still not working

it is working on BetaFlight as A01

her is my resources on Emu CLI:

resource

resource BEEPER 1 C15
resource MOTOR 1 B08
resource MOTOR 2 A00
resource MOTOR 3 B10
resource MOTOR 4 B07
resource PPM 1 A03
resource PWM 1 A02
resource PWM 2 A09
resource PWM 3 A10
resource SERIAL_TX 1 A09
resource SERIAL_TX 2 A02
resource SERIAL_RX 1 A10
resource SERIAL_RX 2 A03
resource LED 1 C13
resource RX_BIND_PLUG 1 B02
resource SPI_SCK 1 A05
resource SPI_SCK 2 B13
resource SPI_SCK 3 B03
resource SPI_MISO 1 A06
resource SPI_MISO 2 B14
resource SPI_MISO 3 B04
resource SPI_MOSI 1 A07
resource SPI_MOSI 2 B15
resource SPI_MOSI 3 B05
resource ADC_BATT 1 B00
resource ADC_CURR 1 B01
resource OSD_CS 1 B12
resource SPI_PREINIT_IPU 1 A04
resource SPI_PREINIT_IPU 2 A15
resource SPI_PREINIT_IPU 3 B12
resource RX_SPI_CS 1 A15

i hope somebody helps me

by the way LED_Strip was A00 and i changed to be my MOTOR 2 .. and the motors work just fine .. all my problem is on ADC_BATT

thanks

• Can't found 'SHFSS' option in 'SPI Bus Receiver Provider'

spiRxTypes.push(
                    'FRSKY_X',
                    'A7105_FLYSKY',
                    'A7105_FLYSKY_2A',
                    'NRF24_KN',
                    'SHFSS'
                );

$ yarn test
yarn run v1.17.3
$ karma start test/karma.conf.js
17 09 2019 11:03:24.135:WARN [filelist]: All files matched by "/home/USER/Downloads/EmuConf/EmuConfigurator/node_modules/chai/chai.js" were excluded or matched by prior matchers.
17 09 2019 11:03:24.212:INFO [karma-server]: Karma v4.2.0 server started at http://0.0.0.0:9876/
17 09 2019 11:03:24.213:INFO [launcher]: Launching browsers ChromeHeadlessNoSandbox with concurrency unlimited
17 09 2019 11:03:24.220:INFO [launcher]: Starting browser ChromeHeadless
17 09 2019 11:03:25.216:INFO [HeadlessChrome 77.0.3865 (Linux 0.0.0)]: Connected on socket 1VhSCQFP_S7gVpo7AAAA with id 25317085
HeadlessChrome 77.0.3865 (Linux 0.0.0): Executed 13 of 13 SUCCESS (0.079 secs / 0.05 secs)
TOTAL: 13 SUCCESS
Done in 2.13s.

$ yarn gulp release --linux64 
yarn run v1.17.3
$ gulp release --linux64
[ '/usr/bin/node',
  '/home/USER/Downloads/EmuConf/EmuConfigurator/node_modules/.bin/gulp',
  'release',
  '--linux64' ]
Building for platform(s): linux64.
[11:02:10] Using gulpfile ~/Downloads/EmuConf/EmuConfigurator/gulpfile.js
[11:02:10] Starting 'release'...
[11:02:10] Starting 'clean_release'...
[11:02:10] Starting 'clean_apps'...
[11:02:10] Starting 'clean_dist'...
[11:02:10] Finished 'clean_release' after 17 ms
[11:02:10] Finished 'clean_apps' after 17 ms
[11:02:10] Finished 'clean_dist' after 183 ms
[11:02:10] Starting 'dist_src'...
[11:02:10] Finished 'dist_src' after 319 ms
[11:02:10] Starting 'dist_changelog'...
[11:02:10] Finished 'dist_changelog' after 2.61 ms
[11:02:10] Starting 'dist_yarn'...
[1/4] Resolving packages...
[2/4] Fetching packages...
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
[11:02:12] Finished 'dist_yarn' after 1.87 s
[11:02:12] Starting 'dist_locale'...
[11:02:12] Finished 'dist_locale' after 48 ms
[11:02:12] Starting 'dist_libraries'...
[11:02:12] Finished 'dist_libraries' after 23 ms
[11:02:12] Starting 'dist_resources'...
[11:02:12] Finished 'dist_resources' after 83 ms
[11:02:12] Starting 'getHash'...
[11:02:12] 90a16c2 
[11:02:12] Finished 'getHash' after 11 ms
[11:02:12] Starting 'writeChangesetId'...
[11:02:12] Finished 'writeChangesetId' after 15 ms
[11:02:12] Starting 'apps'...
Error building NW apps: Error: write EPROTO 139875219755520:error:141A318A:SSL routines:tls_process_ske_dhe:dh key too small:../ssl/statem/statem_clnt.c:2156:

[11:02:12] The following tasks did not complete: release, <parallel>, <series>, apps
[11:02:12] Did you forget to signal async completion?
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I know the ZIP file is available, but i don't want that. i want to compile a .deb to "install".
I am able to compile the old ButterFlight/butterflight-configurator.

Thank you

Hi, i could not install the .deb file ??
Something wrong with it?

MXLinux 19.2

/J

• emuflight/EmuFlight#443
• need GUI implementation

Hi,

I wan't to inform you about a bug I'm facing on the last 0.3.3 configurator :

While going into the CLI, the "Building autocomplete cache" always fails, and I can't get a "diff all" running correctly until the end: it stops randomly before the end. See attached screenshot.
This happen with both win32 and win64 builds, and with all my quadcopter, and I always uninstall and delete the "emuflight" folder before installing another version.

Rolling back to 0.3.2 solve the issue.

Can you help ?
Thank you

Hello,
Does not work with Macos X Catalina the latestversion. The Emuflight configurator does not run.
Thank You very much for your help.

Known issue: "Switching to PID Profile 2 or 3 (profile 1 or 2 in CLI) has been known to hang the USB connection, requiring unplug/replug."

This happens with changing Rate Profile as well. But very little.

Windows 10 Home edition
Configurator: 0.3.4

Minor Bug

The Configurator allows using two UARTs for Serial Rx.

The RX (TBS Crossfire Nano) is on UART 1. Default Settings for the FC (I tried the HolyBro Kakute F7 this time) is UART 6. So, I activated Serial RX for UART 1 and deactivated it for UART 6, hit save. After a reboot I saw Serial Rx activated for both UARTs, 1 and 6. Which might be a conflicting setting and should be rejected.

Well, I tried flying with it, and it did.

serial

serial 0 64 115200 57600 0 115200
serial 6 1024 115200 57600 0 115200

I experience occasional hangups of the configurator when switching from the "PID Tuning Tab" to another tab. The configurator just keeps showing the PID Tuning Tab. I could not figure out the pattern of the hangup. It just sometimes occurs for no real reason.

Workaround: disconnect and reconnect.

Hi ! Hope you're doing great ? :)

I'm trying to bind my meteor65 using F411RX on the latest stable version of emuflight 0.3.1

on betaflight i can successfully bind using :
ACCST D16
CH1-8
RxNum 63

and pasting thoose lines into the cli of betaflight :
set rx_spi_protocol = FRSKY_X_LBT
set frsky_spi_tx_id = 87,158
set frsky_spi_offset = -36
set frsky_spi_bind_hop_data = 2,50,100,150,200,15,65,115,165,215,30,80,132,180,230,45,95,145,195,10,60,110,160,210,25,75,125,175,225,40,90,140,190,5,55,105,155,205,20,70,120,170,220,35,85,135,185,255,255,255
set frsky_x_rx_num = 63

to gather thoose informations i did :
bind_rx, then after something like 1 min, I checked that my frsky_spi_bind_hop_data array was full of numbers then enter save, and voilà

so, i tryed pasting them into emu like this:
set rx_spi_protocol = FRSKY_X
set frsky_spi_tx_id = 87,158
set frsky_spi_offset = -36
set frsky_spi_bind_hop_data = 2,50,100,150,200,15,65,115,165,215,30,80,132,180,230,45,95,145,195,10,60,110,160,210,25,75,125,175,225,40,90,140,190,5,55,105,155,205,20,70,120,170,220,35,85,135,185,255,255,255
set frsky_x_rx_num = 63

but it wont work, i tryed the bind command and letting the radio bind for something like 2 mins then save, but nothing happen, do you have any idea on what is happening ?

Thanks for your help !

Everything else works, including CLI that shows all the tasks are running, but when I click on the PID tab everything is blank, not just zeros, but blank. I can toggle values and change them, but there is nothing in the boxes under presets or anything.

Using 2.12 configurator and 2.0 Emuflight firmeware with the Kakute HD F7 fork (since the current release does not have the Kakute HD F7 option)... The "ARM" tab shows my radio commands and they correspond with the channel map BUT the color of the "ARM" mode doesnt change and I cannot arm my quad (default settings). The arm error messages are MSP and ARM switch (when enabled).

Export gyro data to GoPro GPMF file for reelsteady, this would allow us to use our turtle or runcam split camera or DJI FPV system HD recording and input them into the reelsteady go software and get supper smooth camera footage with out the need for a GoPro. Reelsteady said the emu flight guys are looking into making a tool.

#In 3D mode, the logic of the motor is reversed, and when I reverse it, the plane goes into a death roll, similar to the propeller or motor rotation in the wrong direction.

#Step 1: Activate the 3D mode.
Step 2: Activate ARM.
Step 3: Climb the aircraft to a certain height.
Step 4: Turn the plane upside down and lower the throttle to the reverse state.
Step 5: Bugs appear.

#I hope the 3D mode will work properly.

#target: IFLIGHT_SUCCEX_E_F7(emuflight0.4.0)

#Windows10

Thank you for reading!

emuflight/EmuFlight#460

Describe the bug
RSSI channel is not being saved (CLI and GUI - same thing).
There is some workaround (rssi_adc should be off in a first place), but it is not a proper fix I think.

To Reproduce
as in this video:
https://www.youtube.com/watch?v=x-qdaVpmn5o

Expected behavior
RSSI channel should be saved but it is not.

Additional context
It is old issue with a known workaround but it should not behave like this anyways - I think.

When trying to copy a Profile in the PID Tuning Tab, the settings are not copied to the target profile.

To reproduce, go into the PID Tuning Tab. Choose the profile you want to copy. Klick on "Copy profile values". Choose a Profile, where you want to copy the current settings to. (Press Save). Switch to the profile you chose to copy the settings to. You will see, that the copy did not work.
The same procedure works for Rateprofiles though.

Configurator is emuflight 0.2.0.

I tried to install it several times on my tinyhawk. And once I plug the battery, the song doesn't finish and it starts to beep forever.

Really look forward to try it :)

I've tried downloading the Mac version several times. I've gotten a very slow download that stalled and when it did finish I got a damaged file error.

Downloading the Windows version also stalls.

Profile changes when switching from 4S to 6S, but not 6S to 4S.

Video explanation: https://user-images.githubusercontent.com/56646290/145840775-22abb903-a00c-459b-bc40-12060a5eba16.mp4

Found by @teklust5401

After flash the Modula 7 crazybeef3fr windows 10 not recognise the Modula 7

just got my ClracingF7 2.1 working on Emuflight after several tries
since the board uses User 1 for vtx power will need to put this in cli
set pinio_box =40,255,255,255

None of the available versions work with Mojave.
Is there any configuration required for perfect operation? I tried to install on Mojave version 10.14.6

Hi everyone,

Can you add T-motor F7 Hd firmware on Emuflight ? Or can i upload "Tmotor F7" target for testing before ?

Thanks for your help and your works 👍

EmuConfigurator is currently very crashy on macOS Big Sur 11.x
BetaFlight Configurator has the same issue and have tracked/fixed it here, can this fix get pulled into EmuConfigurator?
betaflight/betaflight-configurator#2274

MacBook Pro 2020 M1, macOS 11.1, EmuConfigurator 0.3.5

Hi devs,

Is it possible to have a target for the matek F722 Mini
here on betaflight : https://raw.githubusercontent.com/betaflight/unified-targets/master/configs/default/MTKS-MATEKF722MINI.config

https://www.drone-fpv-racer.com/matek-flight-controller-f722-mini-se-6817.html

Thanks :)

Configurator: 0.3.5
Firmware: EMUF 0.3.3
Target: IFRC_IFLIGHT_F745_AIO (test target)
Windows 10

When I do a diff all or dump all, the data stops at about 3/4 of the way down. When I scroll back up in history, then the rest of the data is at the top.

I'm not sure if this is a firmware issue, as it looks like it is the way the configurator shows the data it receives.

My diff as is:

= 70
set yaw_srate = 70
set das_yaw_with_roll_input = 0
set das_roll_with_yaw_input = 0
set roll_pitch_mag_expo = 0
set rate_center_sensitivity = 100
set rate_end_sensitivity = 100
set rate_center_correction = 10
set rate_end_correction = 10
set rate_center_weight = 0
set rate_end_weight = 0
set tpa_rate_p = 75
set tpa_rate_i = 125
set tpa_rate_d = 65
set tpa_breakpoint = 1600
set throttle_limit_type = OFF
set throttle_limit_percent = 100
set vbat_comp_type = OFF
set vbat_comp_ref = 37

# rateprofile
rateprofile 5

set thr_mid = 50
set thr_expo = 0
set rates_type = BETAFLIGHT
set roll_rc_rate = 100
set pitch_rc_rate = 100
set yaw_rc_rate = 100
set roll_expo = 0
set pitch_expo = 0
set yaw_expo = 0
set roll_srate = 70
set pitch_srate = 70
set yaw_srate = 70
set das_yaw_with_roll_input = 0
set das_roll_with_yaw_input = 0
set roll_pitch_mag_expo = 0
set rate_center_sensitivity = 100
set rate_end_sensitivity = 100
set rate_center_correction = 10
set rate_end_correction = 10
set rate_center_weight = 0
set rate_end_weight = 0
set tpa_rate_p = 75
set tpa_rate_i = 125
set tpa_rate_d = 65
set tpa_breakpoint = 1600
set throttle_limit_type = OFF
set throttle_limit_percent = 100
set vbat_comp_type = OFF
set vbat_comp_ref = 37

# restore original rateprofile selection
rateprofile 0

# save configuration
save
# diff all

# version
# EmuFlight / IFRC_IFLIGHT_F745_AIO (IFRC) 0.3.3 Feb 14 2021 / 16:48:23 (ae6a0bd2a) MSP API: 1.50

board_name 
manufacturer_id 
mcu_id 003e003c3039510c34323433
signature 

# reset configuration to default settings
defaults nosave

# name
name Protek 35

# resources

# mixer

# servo

# servo mix


# feature
feature -AIRMODE
feature MOTOR_STOP
feature TELEMETRY
feature LED_STRIP
feature OSD

# beeper
beeper -GYRO_CALIBRATED
beeper -ARMING_GPS_FIX
beeper -GPS_STATUS
beeper -READY_BEEP
beeper -DISARM_REPEAT
beeper -CAM_CONNECTION_OPEN
beeper -CAM_CONNECTION_CLOSED

# beacon
beacon RX_LOST
beacon RX_SET

# map
map TAER1234

# serial
serial 1 64 115200 57600 0 115200
serial 6 8192 115200 57600 0 115200

# led
led 0 0,0::L:0
led 1 1,0::L:0
led 2 2,0::L:0

# color

# mode_color
mode_color 5 0 0
mode_color 5 1 0
mode_color 5 2 0
mode_color 5 3 0
mode_color 5 4 0
mode_color 5 5 0

# aux
aux 0 0 0 1700 2100 0 0
aux 1 1 1 1700 2100 0 0
aux 2 13 2 1675 2075 0 0
aux 3 28 7 1700 2100 0 0
aux 4 31 3 1700 2100 0 0
aux 5 35 5 1700 2100 0 0
aux 6 39 4 1700 2100 0 0

# adjrange
adjrange 0 0 6 900 1200 12 6 0 0
adjrange 1 0 6 1300 1625 12 6 0 0
adjrange 2 0 6 1700 2100 12 6 0 0

# rxrange

# vtx

# rxfail

# master
set imuf_roll_q = 8500
set imuf_pitch_q = 8500
set imuf_yaw_q = 8500
set imuf_sharpness = 1
set acc_calibration = 69,15,-9
set mag_hardware = NONE
set rssi_scale = 200
set serialrx_provider = FPORT
set serialrx_inverted = ON
set airmode_start_throttle_percent = 35
set serialrx_halfduplex = ON
set current_meter = ADC
set battery_meter = ADC
set yaw_motors_reversed = ON
set osd_warn_arming_disable = ON
set osd_warn_batt_not_full = ON
set osd_warn_batt_warning = ON
set osd_warn_batt_critical = ON
set osd_warn_visual_beeper = ON
set osd_warn_crash_flip = ON
set osd_warn_esc_fail = ON
set osd_warn_core_temp = OFF
set osd_warn_rc_smoothing = ON
set osd_warn_dji = OFF
set osd_rssi_alarm = 35
set osd_rssi_pos = 2115
set osd_tim_2_pos = 2455
set osd_flymode_pos = 429
set osd_throttle_pos = 2423
set osd_vtx_channel_pos = 2082
set osd_current_pos = 2433
set osd_altitude_pos = 2103
set osd_avg_cell_voltage_pos = 2401
set vtx_channel = 3
set vtx_power = 3
set vtx_freq = 5780

# profile
profile 0

set dterm_lowpass_hz_roll = 100
set dterm_lowpass_hz_pitch = 100
set dterm_lowpass_hz_yaw = 100
set dterm_lowpass2_hz_roll = 250
set dterm_lowpass2_hz_pitch = 250
set dterm_lowpass2_hz_yaw = 250
set smart_dterm_smoothing_roll = 75
set smart_dterm_smoothing_pitch = 75
set smart_dterm_smoothing_yaw = 75
set witchcraft_roll = 6
set witchcraft_pitch 

Hi Guys,

i've some trouble flashing EmuFlight to My RevoltOSD.

The configurator starts and upon connecting the Revolt OSD we can see that it is in DFU mode.

However upon choosing Flash Firmware -> nothing happens and the status says "USB device successfully closed" without flashing the board.

Anyone who can help me out?

Thanks in advance!

Emuflight 0.3.1
Frsky RXSR
Fport

It was ok before I installed 0.3.1 today morning.

I copied only OSD values from old version.

Once I disarm it not arming again until I re-insert battery.
Also after disarm in 30 seconds Taranis says: "Sensor lost" and that is it.

Also the most terrifying thing, that you can't beep or turn on "Turtle Mode".

I am using the following FC and cannot get the video to work properly. On the Configurator 0.3.2, I am using the following version: # EmuFlight / CLRACINGF7 (CLR7) 0.3.1 May 19 2020 / 04:35:57 (9366544) MSP API: 1.47. I have it configured and the quad will arm properly; however, I cannot get the video to get power from the FC using the USER1 mode. Here is the DIFF ALL:
Entering CLI Mode, type 'exit' to return, or 'help'

# version
# EmuFlight / CLRACINGF7 (CLR7) 0.3.1 May 19 2020 / 04:35:57 (9366544) MSP API: 1.47

board_name 
manufacturer_id 
mcu_id 002d00203338510b39393832
signature 

# reset configuration to default settings
defaults nosave

# name
name EMU CLRF7

# resources

# mixer

# servo

# servo mix


# feature
feature TELEMETRY
feature OSD

# beeper

# beacon
beacon RX_LOST
beacon RX_SET

# map

# serial
serial 0 32 115200 57600 0 115200
serial 2 2048 115200 57600 0 115200

# led

# color

# mode_color

# aux
aux 0 0 4 900 1200 0 0
aux 1 27 3 1775 2100 0 0
aux 2 13 3 900 1200 0 0
aux 3 19 1 1300 1700 0 0
aux 4 35 1 1825 2100 0 0

# adjrange

# rxrange

# vtx

# rxfail

# master
set gyro_lowpass_hz_roll = 130
set gyro_lowpass_hz_pitch = 130
set gyro_lowpass_hz_yaw = 130
set imuf_roll_q = 5500
set imuf_pitch_q = 5500
set imuf_yaw_q = 5500
set imuf_sharpness = 4000
set acc_calibration = -69,27,-18
set rssi_channel = 16
set fpv_mix_degrees = 30
set serialrx_provider = SBUS
set min_throttle = 1070
set use_unsynced_pwm = OFF
set motor_pwm_protocol = DSHOT600
set motor_pwm_rate = 480
set vbat_scale = 160
set beeper_dshot_beacon_tone = 5
set yaw_motors_reversed = ON
set tlm_halfduplex = OFF
set osd_units = IMPERIAL
set osd_warn_arming_disable = ON
set osd_warn_batt_not_full = ON
set osd_warn_batt_warning = ON
set osd_warn_batt_critical = ON
set osd_warn_visual_beeper = ON
set osd_warn_crash_flip = ON
set osd_warn_esc_fail = ON
set osd_warn_core_temp = OFF
set osd_vbat_pos = 2092
set osd_rssi_pos = 2061
set osd_flymode_pos = 2368
set osd_throttle_pos = 2082
set osd_vtx_channel_pos = 2420
set osd_crosshairs_pos = 2285
set osd_ah_sbar_pos = 234
set osd_ah_pos = 234
set osd_mah_drawn_pos = 2071
set osd_craft_name_pos = 2440
set osd_altitude_pos = 2102
set osd_warnings_pos = 449
set osd_disarmed_pos = 2400
set osd_core_temp_pos = 506
set vtx_band = 1
set vtx_channel = 4
set vtx_power = 4
set vtx_low_power_disarm = ON
set vtx_freq = 5805
set vcd_video_system = PAL

# profile
profile 0

set dterm_lowpass_type = BIQUAD
set dterm_lowpass_hz_roll = 140
set dterm_lowpass_hz_pitch = 140
set dterm_lowpass_hz_yaw = 140
set dterm_lowpass2_hz_roll = 0
set dterm_lowpass2_hz_pitch = 0
set dterm_lowpass2_hz_yaw = 0
set witchcraft_roll = 0
set witchcraft_pitch = 0
set spa_roll_p = 100
set spa_roll_i = 100
set spa_roll_d = 100
set spa_pitch_p = 100
set spa_pitch_i = 100
set spa_pitch_d = 100
set spa_yaw_p = 100
set spa_yaw_i = 100
set spa_yaw_d = 100
set feathered_pids = 0
set i_decay = 6
set emu_boost = 250
set emu_boost_yaw = 250
set emu_boost_limit = 50
set emu_boost_limit_yaw = 50
set p_pitch = 70
set i_pitch = 60
set d_pitch = 34
set p_roll = 74
set i_roll = 60
set d_roll = 34
set p_yaw = 90
set d_yaw = 12

# profile
profile 1


# profile
profile 2


# restore original profile selection
profile 0

# rateprofile
rateprofile 0

set roll_rc_rate = 192
set pitch_rc_rate = 192
set yaw_rc_rate = 192
set roll_expo = 72
set pitch_expo = 72
set yaw_expo = 77
set roll_srate = 77
set pitch_srate = 77
set yaw_srate = 77
set tpa_rate_p = 60
set tpa_rate_i = 100
set tpa_rate_d = 70
set tpa_breakpoint = 1650

# rateprofile
rateprofile 1


# rateprofile
rateprofile 2


# rateprofile
rateprofile 3


# rateprofile
rateprofile 4


# rateprofile
rateprofile 5


# restore original rateprofile selection
rateprofile 0

# save configuration
save

Fred29: I have a request for update, can you add message (popup) when after fresh flash accelerometer not calibrate, i have not see it and i think is very useful.
What do you think about this?

When you turn expert mode to always on, the betaflight vtx patches show up under release and release candidates

Just noticed there is no description in the '?' help bubble popup for the description for Anti Gravity (in PID tuning)

Bug 1: ARM does not light-up.

Bug 2: mode does not light-up in relation to range-setting until after saved.

https://youtu.be/fVGScZqkaNA

I just flashed Emuflight 0.1.0 on the CrazybeeF4FR flight controller in my Eachine Trashcan, but I'm having trouble with the connection to my X9D+ 2019 after binding in FRSKY_X (D16) mode.

Directly after flashing I went to the CLI and bound with frsky_bind. After power cycling, the connection keeps constantly dropping and recovering every second or so, with my radio giving "Telemetry lost"/"Telemetry recovered"/"RSSI critical" warnings. In the Receiver tab, I see the minimum Throttle position going from 885 tot 1000 (the channel minimum), so I think it was bound correctly.

I have already tried binding with telemetry ON and OFF, but this doesn't make a difference. Flashing back to Betaflight also solves the issue, so I suspect its not a hardware issue.

Any suggestions? Below is a diff all

# 

# diff all

# version
# EmuFlight / CRAZYBEEF4FR (C4FR) 0.1.0 Sep 16 2019 / 22:02:00 (3956d2f50) MSP API: 1.40

board_name 
manufacturer_id 
mcu_id 003d000b3239511334393435
signature 

# reset configuration to default settings
defaults nosave

# name

# resources

# mixer

# servo

# servo mix


# feature

# beeper

# beacon

# map

# serial

# led

# color

# mode_color

# aux

# adjrange

# rxrange

# vtx

# rxfail

# master
set frsky_spi_tx_id = 173,146
set frsky_spi_offset = -56
set frsky_spi_bind_hop_data = 6,74,144,214,49,119,189,24,94,164,234,69,139,209,44,114,184,19,89,159,229,64,136,204,39,109,179,14,84,154,224,59,129,199,34,104,174,9,79,149,219,54,124,194,29,99,169,255,255,255
set frsky_x_rx_num = 8

# profile
profile 0


# profile
profile 1


# profile
profile 2


# restore original profile selection
profile 0

# rateprofile
rateprofile 0


# rateprofile
rateprofile 1


# rateprofile
rateprofile 2


# rateprofile
rateprofile 3


# rateprofile
rateprofile 4


# rateprofile
rateprofile 5


# restore original rateprofile selection
rateprofile 0

# save configuration
save
# 

Hi,

Pid Tuning TAB:
Preset menu at the bottom there are 2 profiles "default" one of them is ( correct me if I'm wrong ) the true default setting, the other is with slightly different LPF filters.

What I'm asking is to change the names to only default only for the one of the two that is exactly with the same numbers as defaults .

I hope that is clear, let me know if you need further explanation,

Best Regards,

Simone (Simofly Fpv )

• under the assumption this is due to old drivers both firmware/configurator side.
• also consider memory-leak.
• pidloop a factor.
• timeout options?
• opening ticket because it's been circumvented only by unplug/replug and this is annoying especially during development.