(01-Mar-2022, 11:21 AM)SnowLeopardFPV Wrote: It will all depend on the ESC you are using with the FC. Some of them attempt to "talk" to the FC on that line even if you don't have ESC telemetry configured on UART6 in the Ports tab of Betaflight Configurator, especially if you are using a BLHeli_32 ESC. A couple of years ago another member had a similar problem getting a Crossfire receiver to work on UART6 of the same model of FC. Removing that ESC harness wire to RX6 solved the issue.

I first time hear that but let me try if that cant cause any damage. Esc is blheliS 100%, if i dont get it work, whats left for me? Is there any way to make softserial port in other pads?

(01-Mar-2022, 12:07 PM)matinikfpv Wrote: Is it safe to do? If i do that, will fc and esc work okay?

Yes. It's just the ESC telemetry wire. You don't even have ESC telemetry configured on your FC and even if you did it is pretty useless these days. All it gives you is motor RPM and ESC temperature in the OSD of your goggles only. Most people don't even bother with it. Your ESC doesn't need that wire to function.

(01-Mar-2022, 12:32 PM)SnowLeopardFPV Wrote: Yes. It's just the ESC telemetry wire. You don't even have ESC telemetry configured on your FC and even if you did it is pretty useless these days. All it gives you is motor RPM and ESC temperature in the OSD of your goggles only. Most people don't even bother with it. Your ESC doesn't need that wire to function.

Okay, i will try that after i finish work. I will update you, thanks

(01-Mar-2022, 12:32 PM)SnowLeopardFPV Wrote: Yes. It's just the ESC telemetry wire. You don't even have ESC telemetry configured on your FC and even if you did it is pretty useless these days. All it gives you is motor RPM and ESC temperature in the OSD of your goggles only. Most people don't even bother with it. Your ESC doesn't need that wire to function.

Bro it is working now, thank you very much for this, i appreciate it. Why this happens? I dont know how it work now when i cut rx6 from esc, so weird
I have strange problem now, my external beeper beeps when i arm quad and when i disarm, that is strange too, do you know what could be problem?

(01-Mar-2022, 04:37 PM)matinikfpv Wrote: Bro it is working now, thank you very much for this, i appreciate it. Why this happens? I dont know how it work now when i cut rx6 from esc, so weird

No problem

It happens because the ESC is trying to "talk" to the FC on that wire in order to negotiate telemetry data connection. It knows that the ESC is listening on the RX6 connection because you have enabled MSP or Serial RX options enabled, so it is trying to establish if the FC is asking for ESC telemetry data on that UART by trying to talk to it. That data negotiation talk from the ESC is interfering with and getting jumbled up with negotiation talk from the MSP / Serial RX data device that was also connected to RX6, so neither device is able to establish a data connection to the FC. The rule of thumb is that you should only ever have one device connected to a UART, otherwise you will run into problems like this.

(01-Mar-2022, 04:37 PM)matinikfpv Wrote: I have strange problem now, my external beeper beeps when i arm quad and when i disarm, that is strange too, do you know what could be problem?

The beeps are normal when arming and disarming the quad. It's for safety reasons and also to inform you of the arming status. For instance if you have GPS module connected the beep pattern on arming will let you know if the GPS had established a successful 3D satellite fix or not. So the beeps are nothing to worry about.

(01-Mar-2022, 05:20 PM)SnowLeopardFPV Wrote: No problem

It happens because the ESC is trying to "talk" to the FC on that wire in order to negotiate telemetry data connection. It knows that the ESC is listening on the RX6 connection because you have enabled MSP or Serial RX options enabled, so it is trying to establish if the FC is asking for ESC telemetry data on that UART by trying to talk to it. That data negotiation talk from the ESC is interfering with and getting jumbled up with negotiation talk from the MSP / Serial RX data device that was also connected to RX6, so neither device is able to establish a data connection to the FC. The rule of thumb is that you should only ever have one device connected to a UART, otherwise you will run into problems like this.


The beeps are normal when arming and disarming the quad. It's for safety reasons and also to inform you of the arming status. For instance if you have GPS module connected the beep pattern on arming will let you know if the GPS had established a successful 3D satellite fix or not. So the beeps are nothing to worry about.

Cheers mate, thanks a lot! Happy flying
Im happy now

(01-Mar-2022, 05:20 PM)SnowLeopardFPV Wrote: No problem

It happens because the ESC is trying to "talk" to the FC on that wire in order to negotiate telemetry data connection. It knows that the ESC is listening on the RX6 connection because you have enabled MSP or Serial RX options enabled, so it is trying to establish if the FC is asking for ESC telemetry data on that UART by trying to talk to it. That data negotiation talk from the ESC is interfering with and getting jumbled up with negotiation talk from the MSP / Serial RX data device that was also connected to RX6, so neither device is able to establish a data connection to the FC. The rule of thumb is that you should only ever have one device connected to a UART, otherwise you will run into problems like this.


The beeps are normal when arming and disarming the quad. It's for safety reasons and also to inform you of the arming status. For instance if you have GPS module connected the beep pattern on arming will let you know if the GPS had established a successful 3D satellite fix or not. So the beeps are nothing to worry about.

Hi guys!

I Have the exact same problem with the exact same hardware, except the GPS is not mounted yet. I also have the V1 DJI googles. I have rooted the Vista together with the googles and installed the WTFOS software to activate the MPS OSD. But i cant get the OSD parameters in the googles it is so strange and frustating. I even tried to solder the extra ground for signal on the board but without luck. Can anyone maybe help me?

(27-Jun-2023, 08:22 PM)Hersleb1991 Wrote: I Have the exact same problem with the exact same hardware, except the GPS is not mounted yet. I also have the V1 DJI googles. I have rooted the Vista together with the googles and installed the WTFOS software to activate the MPS OSD. But i cant get the OSD parameters in the googles it is so strange and frustating. I even tried to solder the extra ground for signal on the board but without luck. Can anyone maybe help me?

First of all, putting the root hack and WTFOS aside for now, if you switch on the "Custom OSD" option in your DJI FPV Goggles do you get any telemetry data values showing up, and with a LiPo plugged in do their values changes (i.e. battery voltage, battery mAh etc.). This will help us to ascertain if you have a UART comms issue between the FC and the Vista.

In addition to answering the above question, can you please run both the "dump" and "diff all" commands in the Betaflight Configurator CLI tab and copy/paste the results back here.

hi guys i have the same problem with my new vista air unit, i rooted, wtf os but my BF osd not shopwing at all, i use UART1
here my diff
# 

# diff all

# version
# Betaflight / STM32F7X2 (S7X2) 4.4.0 Feb  1 2023 / 23:20:45 (4605309d8) MSP API: 1.45

# config: YES

# start the command batch
batch start

# reset configuration to default settings
defaults nosave

board_name IFLIGHT_BLITZ_F722
manufacturer_id IFRC
mcu_id 001f00343438511436383538
signature 

# name: Hileud Cau

# feature
feature LED_STRIP

# serial
serial 0 131073 115200 57600 0 115200

# beacon
beacon RX_LOST
beacon RX_SET

# led
led 0 0,0::C:13
led 1 1,0::C:13
led 2 2,0::C:13
led 3 3,0::C:13
led 4 4,0::C:13

# color
color 5 91,0,255
color 6 108,0,255

# aux
aux 0 0 0 900 1275 0 0
aux 1 1 4 1725 2100 0 0
aux 2 13 3 1725 2100 0 0
aux 3 35 1 1725 2100 0 0
aux 4 36 5 1725 2100 0 0

# rxrange
rxrange 0 988 2011
rxrange 1 988 2011
rxrange 2 990 2011
rxrange 3 988 2011

# vtxtable
vtxtable bands 5
vtxtable channels 8
vtxtable band 1 BOSCAM_A A CUSTOM  5865 5845 5825 5805 5785 5765 5745 5725
vtxtable band 2 BOSCAM_B B CUSTOM  5733 5752 5771 5790 5809 5828 5847 5866
vtxtable band 3 BOSCAM_E E CUSTOM  5705 5685 5665    0 5885 5905    0    0
vtxtable band 4 FATSHARK F CUSTOM  5740 5760 5780 5800 5820 5840 5860 5880
vtxtable band 5 RACEBAND R CUSTOM  5658 5695 5732 5769 5806 5843 5880 5917
vtxtable powerlevels 4
vtxtable powervalues 25 200 400 800
vtxtable powerlabels 25 200 400 800

# rxfail
rxfail 5 s 1500

# master
set dyn_notch_count = 1
set dyn_notch_q = 500
set dyn_notch_min_hz = 120
set acc_lpf_hz = 10
set acc_calibration = 10,10,22,1
set baro_hardware = NONE
set rc_smoothing_auto_factor = 140
set rc_smoothing_setpoint_cutoff = 25
set rc_smoothing_feedforward_cutoff = 25
set min_throttle = 1068
set dshot_idle_value = 450
set dshot_bidir = ON
set motor_pwm_protocol = DSHOT600
set failsafe_switch_mode = STAGE2
set bat_capacity = 1300
set vbat_max_cell_voltage = 420
set yaw_motors_reversed = ON
set small_angle = 180
set gps_sbas_mode = AUTO
set gps_auto_baud = ON
set gps_ublox_use_galileo = ON
set gps_set_home_point_once = ON
set gps_rescue_ground_speed = 800
set gps_rescue_throttle_max = 1800
set gps_rescue_throttle_hover = 1350
set gps_rescue_allow_arming_without_fix = ON
set report_cell_voltage = ON
set osd_warn_bitmask = 32765
set osd_rssi_alarm = 25
set osd_rssi_dbm_alarm = -90
set osd_rssi_pos = 112
set osd_link_quality_pos = 2092
set osd_link_tx_power_pos = 65
set osd_rssi_dbm_pos = 2124
set osd_tim_2_pos = 2071
set osd_flymode_pos = 2445
set osd_anti_gravity_pos = 2113
set osd_g_force_pos = 2049
set osd_throttle_pos = 2455
set osd_vtx_channel_pos = 2081
set osd_current_pos = 385
set osd_mah_drawn_pos = 2402
set osd_craft_name_pos = 2410
set osd_gps_speed_pos = 2133
set osd_gps_lon_pos = 16
set osd_gps_lat_pos = 2
set osd_gps_sats_pos = 2165
set osd_home_dir_pos = 2222
set osd_home_dist_pos = 2197
set osd_compass_bar_pos = 2059
set osd_altitude_pos = 18487
set osd_power_pos = 388
set osd_pidrate_profile_pos = 2054
set osd_warnings_pos = 14633
set osd_avg_cell_voltage_pos = 2221
set osd_pit_ang_pos = 2209
set osd_rol_ang_pos = 2241
set osd_battery_usage_pos = 9
set osd_disarmed_pos = 2379
set osd_up_down_reference_pos = 201
set osd_ready_mode_pos = 2316
set osd_log_status_pos = 385
set osd_gps_sats_show_hdop = ON
set osd_displayport_device = MSP
set osd_canvas_width = 30
set osd_canvas_height = 13
set debug_mode = GYRO_SCALED
set vtx_band = 5
set vtx_channel = 8
set vtx_power = 4
set vtx_freq = 5917
set vcd_video_system = HD
set rpm_filter_fade_range_hz = 100
set craft_name = Hileud Cau
set pilot_name = Ariefjoe800

profile 0

# profile 0
set profile_name = Karate
set dterm_lpf1_dyn_expo = 10
set p_pitch = 59
set i_pitch = 106
set d_pitch = 58
set f_pitch = 158
set p_roll = 51
set i_roll = 92
set d_roll = 53
set f_roll = 138
set d_min_roll = 43
set d_min_pitch = 46
set feedforward_averaging = 2_POINT
set feedforward_smooth_factor = 60
set feedforward_jitter_factor = 12
set dyn_idle_min_rpm = 35
set dyn_idle_p_gain = 35
set simplified_pids_mode = RP
set simplified_d_gain = 145
set simplified_pi_gain = 115
set simplified_dmax_gain = 70
set simplified_feedforward_gain = 115
set simplified_pitch_d_gain = 95
set simplified_pitch_pi_gain = 110

profile 1

# profile 1
set profile_name = Supafly
set dterm_lpf1_dyn_min_hz = 0
set dterm_lpf1_dyn_max_hz = 0
set dterm_lpf1_dyn_expo = 0
set p_pitch = 51
set i_pitch = 69
set d_pitch = 35
set f_pitch = 137
set i_roll = 60
set d_roll = 33
set i_yaw = 60
set d_min_roll = 33
set d_min_pitch = 35
set feedforward_averaging = 2_POINT
set feedforward_smooth_factor = 45
set feedforward_jitter_factor = 10
set dyn_idle_min_rpm = 25
set simplified_i_gain = 75
set simplified_d_gain = 110
set simplified_dmax_gain = 0
set simplified_pitch_d_gain = 95
set simplified_pitch_pi_gain = 110

profile 2

# profile 2
set profile_name = Default

profile 3

# restore original profile selection
profile 1

rateprofile 0

# rateprofile 0
set rateprofile_name = max900
set thr_expo = 20
set roll_rc_rate = 15
set pitch_rc_rate = 15
set yaw_rc_rate = 20
set roll_expo = 50
set pitch_expo = 50
set yaw_expo = 30
set roll_srate = 90
set pitch_srate = 90
set yaw_srate = 90
set throttle_limit_type = SCALE

rateprofile 1

# rateprofile 1
set rateprofile_name = max720
set roll_rc_rate = 15
set pitch_rc_rate = 15
set yaw_rc_rate = 20
set roll_expo = 50
set pitch_expo = 50
set yaw_expo = 30
set roll_srate = 72
set pitch_srate = 72
set yaw_srate = 72
set throttle_limit_type = SCALE

rateprofile 2

rateprofile 3

# restore original rateprofile selection
rateprofile 1

# save configuration
save
#