I am brand new to racing quads but was excited enough to know i wanted to get a good well-known transmitter rig to roll with on future quads. So I made the tremendous MISTAKE of buying an "ARF" eachine wizard x220s so i could have a Taranis QX7. I'd like to think had i settled for the lame controller the RTF came with, I wouldn't be in this mess.

As an absolute noob, i figured, how hard could it be to slap on a compatible receiver to go with my Taranis QX7 right? And with the eachine wizard being a very popular beginner quad, you would think i could get a clear answer on the configuration using the also critically acclaimed frsky r-xsr receiver right? Learning to solder was no issue despite having little experience, so I was able to solder what i think is correct and even get it bound to the transmitter.  This was already after hours of research and finally finding ... The guy was even telling me what commands to enter with betaflight so it was a sure fire thing with my exact hardware right? WRONG!

So I'm still stuck. Basically the past day or so has been spent frantically googling Omnibus F4 V3, frsky r-xsr, betaflight configurations, all that in every possible combination. Most other videos claiming to have a solution were just having epiphanies about forgetting to connect the sbus bridge, which i had already done in the first place thanks to this MirkoFPV guy (from the video). 

I know betaflight has been in cahoots with frsky about this receiver and has made a special fport protocol, but guess what, even after flashing that version of the FW, i can't get it to work either. All the inversion command nonsense i'm totally aware of as well, and doesn't seem to be doing anything to help despite endless trial and error with all possible permutations. 

Through this whole process of trying to enter functional territory, i've already learned way more than i expected to. I updated the FW on my QX7 transmitter which went smoothly, as well as the receiver firmware, which gave me my f.port protocol. There's one possibility I haven't tried and it has to do with the signal inversion. But it's such a tiny soldering job I want to make sure It's necessary before i risk destroying my receiver, which i believe is the source of all my issues since i opted to go with full telemetry for obvious reasons.

In regards to the pic attached: I still have all the wires attached to the FC in the same way. But since taking that pic, I've tried to move the smartport wire (yellow in the case of the r-xsr), to the "P" pad of my receiver (the "uninversion" hack) since i have read that you need to use some kind of softserial port. But I'm still stuck beyond belief. I've ruled out everything in both configurations, there has to be something vital that i've overlooked i just have no clue. 

This is my first quad and i've had to learn all of this new stuff about drone electronics despite having never been in the air yet (outside of simulators and whatever auto-level piece of junk that just left me wanting more). I'm ambitious to get started in the FPV world and haven't given up since I am naturally more ambitious on solving my tech problems. but the satisfaction of reaching a solution is frustratingly nonexistent and i don't want this to rule out staying with the racing / freestyle niche of droning. Thanks for taking the time to read!

Might you post a screenshot of your PORTS and CONFIGURATION tabs in BetaFlight?

I cannot tell if you have the RX and radio bound...

The good news is that you have the SBUS (green) wire of the R-XSR correctly connected to the SBUS pad of the Omnibus and the S.PORT (yellow) wire connected to the TX pad of UART1 on the Omnibus. The one thing I will say is that UART1 is also reserved for MSP communication on the USB port so I would probably avoid using that for anything unless you run out of spare UART ports. Are there any other spare unused UARTs on the board you can use instead? If you can it just avoids any type of UART conflict.

Forgetting the SmartPort telemetry for now, with the receiver switched on and bound to the Taranis, are any of the channel values in the Receiver tab of the Betaflight Configurator changing when you move the sticks?

Can you please do the following:-

1. Post a screenshot of the Ports tab in the Betaflight Configurator.
   
2. Go to the CLI tab in Betaflight Configurator and run the command "dump" followed by the "diff all" command and then paste the results back here.
   

Also, what firmware do you currently have installed on the R-XSR? Is it the standard SBUS firmware or the the F.PORT firmware?

(17-Sep-2018, 09:30 PM)kaitylynn Wrote: Might you post a screenshot of your PORTS and CONFIGURATION tabs in BetaFlight?

I cannot tell if you have the RX and radio bound...

(17-Sep-2018, 09:31 PM)SnowLeopardFPV Wrote: The good news is that you have the SBUS (green) wire of the R-XSR correctly connected to the SBUS pad of the Omnibus and the S.PORT (yellow) wire connected to the TX pad of UART1 on the Omnibus. The one thing I will say is that UART1 is also reserved for MSP communication on the USB port so I would probably avoid using that for anything unless you run out of spare UART ports. Are there any other spare unused UARTs on the board you can use instead? If you can it just avoids any type of UART conflict.

Forgetting the SmartPort telemetry for now, with the receiver switched on and bound to the Taranis, are any of the channel values in the Receiver tab of the Betaflight Configurator changing when you move the sticks?

Can you please do the following:-

1. Post a screenshot of the Ports tab in the Betaflight Configurator.
   
2. Go to the CLI tab in Betaflight Configurator and run the command "dump" followed by the "diff all" command and then paste the results back here.
   

Also, what firmware do you currently have installed on the R-XSR? Is it the standard SBUS firmware or the the F.PORT firmware?

I really appreciate the quick replies. Attached the ports and configuration screenshots. and here's what i got for dump / diff all commands i put dashes between the two commands 

# dump

# version
# Betaflight / OMNIBUSF4SD (OBSD) 3.5.1 Sep  8 2018 / 05:40:39 (d9fb5ca13) MSP API: 1.40

board_name OMNIBUSF4SD
manufacturer_id 

# name
name Dankfly5000

# resources
resource BEEPER 1 B04
resource MOTOR 1 B00
resource MOTOR 2 B01
resource MOTOR 3 A03
resource MOTOR 4 A02
resource MOTOR 5 A01
resource MOTOR 6 A08
resource MOTOR 7 NONE
resource MOTOR 8 NONE
resource SERVO 1 NONE
resource SERVO 2 NONE
resource SERVO 3 NONE
resource SERVO 4 NONE
resource SERVO 5 NONE
resource SERVO 6 NONE
resource SERVO 7 NONE
resource SERVO 8 NONE
resource PPM 1 B08
resource PWM 1 B08
resource PWM 2 B09
resource PWM 3 C06
resource PWM 4 C07
resource PWM 5 C08
resource PWM 6 C09
resource PWM 7 NONE
resource PWM 8 NONE
resource SONAR_TRIGGER 1 A01
resource SONAR_ECHO 1 A08
resource LED_STRIP 1 B06
resource SERIAL_TX 1 A09
resource SERIAL_TX 2 NONE
resource SERIAL_TX 3 B10
resource SERIAL_TX 4 NONE
resource SERIAL_TX 5 NONE
resource SERIAL_TX 6 C06
resource SERIAL_TX 7 NONE
resource SERIAL_TX 8 NONE
resource SERIAL_TX 9 NONE
resource SERIAL_TX 10 NONE
resource SERIAL_TX 11 NONE
resource SERIAL_TX 12 NONE
resource SERIAL_RX 1 A10
resource SERIAL_RX 2 NONE
resource SERIAL_RX 3 B11
resource SERIAL_RX 4 NONE
resource SERIAL_RX 5 NONE
resource SERIAL_RX 6 C07
resource SERIAL_RX 7 NONE
resource SERIAL_RX 8 NONE
resource SERIAL_RX 9 NONE
resource SERIAL_RX 10 NONE
resource SERIAL_RX 11 A09
resource SERIAL_RX 12 NONE
resource INVERTER 1 NONE
resource INVERTER 2 NONE
resource INVERTER 3 C09
resource INVERTER 4 NONE
resource INVERTER 5 NONE
resource INVERTER 6 C08
resource INVERTER 7 NONE
resource INVERTER 8 NONE
resource INVERTER 9 NONE
resource INVERTER 10 NONE
resource INVERTER 11 NONE
resource INVERTER 12 NONE
resource I2C_SCL 1 NONE
resource I2C_SCL 2 NONE
resource I2C_SCL 3 NONE
resource I2C_SDA 1 NONE
resource I2C_SDA 2 NONE
resource I2C_SDA 3 NONE
resource LED 1 B05
resource LED 2 NONE
resource LED 3 NONE
resource RX_BIND 1 NONE
resource RX_BIND_PLUG 1 NONE
resource TRANSPONDER 1 NONE
resource SPI_SCK 1 A05
resource SPI_SCK 2 B13
resource SPI_SCK 3 C10
resource SPI_MISO 1 A06
resource SPI_MISO 2 B14
resource SPI_MISO 3 C11
resource SPI_MOSI 1 A07
resource SPI_MOSI 2 B15
resource SPI_MOSI 3 C12
resource ESCSERIAL 1 B08
resource CAMERA_CONTROL 1 NONE
resource ADC_BATT 1 C02
resource ADC_RSSI 1 A00
resource ADC_CURR 1 C01
resource ADC_EXT 1 NONE
resource BARO_CS 1 B03
resource COMPASS_CS 1 NONE
resource SDCARD_CS 1 B12
resource SDCARD_DETECT 1 B07
resource PINIO 1 NONE
resource PINIO 2 NONE
resource PINIO 3 NONE
resource PINIO 4 NONE
resource USB_MSC_PIN 1 NONE
resource FLASH_CS 1 B12
resource OSD_CS 1 A15
resource SPI_PREINIT_IPU 1 A04
resource SPI_PREINIT_IPU 2 B12
resource SPI_PREINIT_IPU 3 B03
resource SPI_PREINIT_IPU 4 A15
resource SPI_PREINIT_IPU 5 NONE
resource SPI_PREINIT_IPU 6 NONE
resource SPI_PREINIT_IPU 7 NONE
resource SPI_PREINIT_IPU 8 NONE
resource SPI_PREINIT_IPU 9 NONE
resource SPI_PREINIT_IPU 10 NONE
resource SPI_PREINIT_IPU 11 NONE
resource SPI_PREINIT_OPU 1 NONE
resource SPI_PREINIT_OPU 2 NONE

# mixer
mixer QUADX

mmix reset


# servo
servo 0 1000 2000 1500 100 -1
servo 1 1000 2000 1500 100 -1
servo 2 1000 2000 1500 100 -1
servo 3 1000 2000 1500 100 -1
servo 4 1000 2000 1500 100 -1
servo 5 1000 2000 1500 100 -1
servo 6 1000 2000 1500 100 -1
servo 7 1000 2000 1500 100 -1

# servo mix
smix reset



# feature
feature -RX_PPM
feature -INFLIGHT_ACC_CAL
feature -RX_SERIAL
feature -MOTOR_STOP
feature -SERVO_TILT
feature -SOFTSERIAL
feature -GPS
feature -RANGEFINDER
feature -TELEMETRY
feature -3D
feature -RX_PARALLEL_PWM
feature -RX_MSP
feature -RSSI_ADC
feature -LED_STRIP
feature -DISPLAY
feature -OSD
feature -CHANNEL_FORWARDING
feature -TRANSPONDER
feature -AIRMODE
feature -RX_SPI
feature -SOFTSPI
feature -ESC_SENSOR
feature -ANTI_GRAVITY
feature -DYNAMIC_FILTER
feature RX_SERIAL
feature SOFTSERIAL
feature TELEMETRY
feature OSD

# beeper
beeper GYRO_CALIBRATED
beeper RX_LOST
beeper RX_LOST_LANDING
beeper DISARMING
beeper ARMING
beeper ARMING_GPS_FIX
beeper BAT_CRIT_LOW
beeper BAT_LOW
beeper GPS_STATUS
beeper RX_SET
beeper ACC_CALIBRATION
beeper ACC_CALIBRATION_FAIL
beeper READY_BEEP
beeper MULTI_BEEPS
beeper DISARM_REPEAT
beeper ARMED
beeper SYSTEM_INIT
beeper ON_USB
beeper BLACKBOX_ERASE
beeper CRASH FLIP
beeper CAM_CONNECTION_OPEN
beeper CAM_CONNECTION_CLOSED
beeper RC_SMOOTHING_INIT_FAIL

# beacon
beacon GYRO_CALIBRATED
beacon -RX_LOST
beacon RX_LOST_LANDING
beacon DISARMING
beacon ARMING
beacon ARMING_GPS_FIX
beacon BAT_CRIT_LOW
beacon BAT_LOW
beacon GPS_STATUS
beacon -RX_SET
beacon ACC_CALIBRATION
beacon ACC_CALIBRATION_FAIL
beacon READY_BEEP
beacon MULTI_BEEPS
beacon DISARM_REPEAT
beacon ARMED
beacon SYSTEM_INIT
beacon ON_USB
beacon BLACKBOX_ERASE
beacon CRASH FLIP
beacon CAM_CONNECTION_OPEN
beacon CAM_CONNECTION_CLOSED
beacon RC_SMOOTHING_INIT_FAIL

# map
map AETR1234

# serial
serial 20 1 115200 57600 0 115200
serial 0 0 115200 57600 0 115200
serial 2 0 115200 57600 0 115200
serial 5 64 115200 57600 0 115200
serial 30 32 115200 57600 0 115200

# led
led 0 0,0::C:0
led 1 0,0::C:0
led 2 0,0::C:0
led 3 0,0::C:0
led 4 0,0::C:0
led 5 0,0::C:0
led 6 0,0::C:0
led 7 0,0::C:0
led 8 0,0::C:0
led 9 0,0::C:0
led 10 0,0::C:0
led 11 0,0::C:0
led 12 0,0::C:0
led 13 0,0::C:0
led 14 0,0::C:0
led 15 0,0::C:0
led 16 0,0::C:0
led 17 0,0::C:0
led 18 0,0::C:0
led 19 0,0::C:0
led 20 0,0::C:0
led 21 0,0::C:0
led 22 0,0::C:0
led 23 0,0::C:0
led 24 0,0::C:0
led 25 0,0::C:0
led 26 0,0::C:0
led 27 0,0::C:0
led 28 0,0::C:0
led 29 0,0::C:0
led 30 0,0::C:0
led 31 0,0::C:0

# color
color 0 0,0,0
color 1 0,255,255
color 2 0,0,255
color 3 30,0,255
color 4 60,0,255
color 5 90,0,255
color 6 120,0,255
color 7 150,0,255
color 8 180,0,255
color 9 210,0,255
color 10 240,0,255
color 11 270,0,255
color 12 300,0,255
color 13 330,0,255
color 14 0,0,0
color 15 0,0,0

# mode_color
mode_color 0 0 1
mode_color 0 1 11
mode_color 0 2 2
mode_color 0 3 13
mode_color 0 4 10
mode_color 0 5 3
mode_color 1 0 5
mode_color 1 1 11
mode_color 1 2 3
mode_color 1 3 13
mode_color 1 4 10
mode_color 1 5 3
mode_color 2 0 10
mode_color 2 1 11
mode_color 2 2 4
mode_color 2 3 13
mode_color 2 4 10
mode_color 2 5 3
mode_color 3 0 8
mode_color 3 1 11
mode_color 3 2 4
mode_color 3 3 13
mode_color 3 4 10
mode_color 3 5 3
mode_color 4 0 7
mode_color 4 1 11
mode_color 4 2 3
mode_color 4 3 13
mode_color 4 4 10
mode_color 4 5 3
mode_color 5 0 9
mode_color 5 1 11
mode_color 5 2 2
mode_color 5 3 13
mode_color 5 4 10
mode_color 5 5 3
mode_color 6 0 6
mode_color 6 1 10
mode_color 6 2 1
mode_color 6 3 0
mode_color 6 4 0
mode_color 6 5 2
mode_color 6 6 3
mode_color 6 7 6
mode_color 6 8 0
mode_color 6 9 0
mode_color 6 10 0
mode_color 7 0 3

# aux
aux 0 0 0 900 900 0 0
aux 1 0 0 900 900 0 0
aux 2 0 0 900 900 0 0
aux 3 0 0 900 900 0 0
aux 4 0 0 900 900 0 0
aux 5 0 0 900 900 0 0
aux 6 0 0 900 900 0 0
aux 7 0 0 900 900 0 0
aux 8 0 0 900 900 0 0
aux 9 0 0 900 900 0 0
aux 10 0 0 900 900 0 0
aux 11 0 0 900 900 0 0
aux 12 0 0 900 900 0 0
aux 13 0 0 900 900 0 0
aux 14 0 0 900 900 0 0
aux 15 0 0 900 900 0 0
aux 16 0 0 900 900 0 0
aux 17 0 0 900 900 0 0
aux 18 0 0 900 900 0 0
aux 19 0 0 900 900 0 0

# adjrange
adjrange 0 0 0 900 900 0 0 0 0
adjrange 1 0 0 900 900 0 0 0 0
adjrange 2 0 0 900 900 0 0 0 0
adjrange 3 0 0 900 900 0 0 0 0
adjrange 4 0 0 900 900 0 0 0 0
adjrange 5 0 0 900 900 0 0 0 0
adjrange 6 0 0 900 900 0 0 0 0
adjrange 7 0 0 900 900 0 0 0 0
adjrange 8 0 0 900 900 0 0 0 0
adjrange 9 0 0 900 900 0 0 0 0
adjrange 10 0 0 900 900 0 0 0 0
adjrange 11 0 0 900 900 0 0 0 0
adjrange 12 0 0 900 900 0 0 0 0
adjrange 13 0 0 900 900 0 0 0 0
adjrange 14 0 0 900 900 0 0 0 0

# rxrange
rxrange 0 1000 2000
rxrange 1 1000 2000
rxrange 2 1000 2000
rxrange 3 1000 2000

# vtx
vtx 0 0 0 0 900 900
vtx 1 0 0 0 900 900
vtx 2 0 0 0 900 900
vtx 3 0 0 0 900 900
vtx 4 0 0 0 900 900
vtx 5 0 0 0 900 900
vtx 6 0 0 0 900 900
vtx 7 0 0 0 900 900
vtx 8 0 0 0 900 900
vtx 9 0 0 0 900 900

# rxfail
rxfail 0 a
rxfail 1 a
rxfail 2 a
rxfail 3 a
rxfail 4 h
rxfail 5 h
rxfail 6 h
rxfail 7 h
rxfail 8 h
rxfail 9 h
rxfail 10 h
rxfail 11 h
rxfail 12 h
rxfail 13 h
rxfail 14 h
rxfail 15 h
rxfail 16 h
rxfail 17 h

# master
set align_gyro = DEFAULT
set gyro_hardware_lpf = NORMAL
set gyro_32khz_hardware_lpf = NORMAL
set gyro_sync_denom = 1
set gyro_lowpass_type = PT1
set gyro_lowpass_hz = 100
set gyro_lowpass2_type = PT1
set gyro_lowpass2_hz = 300
set gyro_notch1_hz = 0
set gyro_notch1_cutoff = 0
set gyro_notch2_hz = 0
set gyro_notch2_cutoff = 0
set gyro_calib_duration = 125
set gyro_calib_noise_limit = 48
set gyro_offset_yaw = 0
set gyro_overflow_detect = ALL
set yaw_spin_recovery = ON
set yaw_spin_threshold = 1950
set gyro_use_32khz = OFF
set dyn_notch_quality = 70
set dyn_notch_width_percent = 50
set align_acc = DEFAULT
set acc_hardware = AUTO
set acc_lpf_hz = 10
set acc_trim_pitch = 0
set acc_trim_roll = 0
set acc_calibration = 21,83,-110
set align_mag = DEFAULT
set mag_bustype = I2C
set mag_i2c_device = 2
set mag_i2c_address = 0
set mag_spi_device = 0
set mag_hardware = AUTO
set mag_declination = 0
set mag_calibration = 0,0,0
set baro_bustype = SPI
set baro_spi_device = 3
set baro_i2c_device = 0
set baro_i2c_address = 0
set baro_hardware = AUTO
set baro_tab_size = 21
set baro_noise_lpf = 600
set baro_cf_vel = 985
set baro_cf_alt = 965
set mid_rc = 1500
set min_check = 1050
set max_check = 1900
set rssi_channel = 0
set rssi_src_frame_errors = OFF
set rssi_scale = 100
set rssi_offset = 0
set rssi_invert = OFF
set rc_interp = AUTO
set rc_interp_ch = RPYT
set rc_interp_int = 19
set rc_smoothing_type = INTERPOLATION
set rc_smoothing_input_hz = 0
set rc_smoothing_derivative_hz = 0
set rc_smoothing_debug_axis = ROLL
set rc_smoothing_input_type = BIQUAD
set rc_smoothing_derivative_type = BIQUAD
set fpv_mix_degrees = 0
set max_aux_channels = 14
set serialrx_provider = FPORT
set serialrx_inverted = ON
set spektrum_sat_bind = 0
set spektrum_sat_bind_autoreset = ON
set airmode_start_throttle_percent = 32
set rx_min_usec = 885
set rx_max_usec = 2115
set serialrx_halfduplex = OFF
set adc_device = 2
set input_filtering_mode = OFF
set blackbox_p_ratio = 32
set blackbox_device = SDCARD
set blackbox_record_acc = ON
set blackbox_mode = NORMAL
set min_throttle = 1070
set max_throttle = 2000
set min_command = 1000
set dshot_idle_value = 100
set dshot_burst = ON
set use_unsynced_pwm = OFF
set motor_pwm_protocol = DSHOT300
set motor_pwm_rate = 480
set motor_pwm_inversion = OFF
set motor_poles = 14
set thr_corr_value = 0
set thr_corr_angle = 800
set failsafe_delay = 4
set failsafe_off_delay = 10
set failsafe_throttle = 1000
set failsafe_switch_mode = STAGE1
set failsafe_throttle_low_delay = 100
set failsafe_procedure = DROP
set align_board_roll = 0
set align_board_pitch = 0
set align_board_yaw = 0
set gimbal_mode = NORMAL
set bat_capacity = 0
set vbat_max_cell_voltage = 43
set vbat_full_cell_voltage = 41
set vbat_min_cell_voltage = 33
set vbat_warning_cell_voltage = 35
set vbat_hysteresis = 1
set current_meter = ADC
set battery_meter = ADC
set vbat_detect_cell_voltage = 30
set use_vbat_alerts = ON
set use_cbat_alerts = OFF
set cbat_alert_percent = 10
set vbat_cutoff_percent = 100
set vbat_scale = 110
set vbat_divider = 10
set vbat_multiplier = 1
set ibata_scale = 400
set ibata_offset = 0
set ibatv_scale = 0
set ibatv_offset = 0
set beeper_inversion = ON
set beeper_od = OFF
set beeper_frequency = 0
set beeper_dshot_beacon_tone = 1
set yaw_motors_reversed = OFF
set crashflip_motor_percent = 0
set 3d_deadband_low = 1406
set 3d_deadband_high = 1514
set 3d_neutral = 1460
set 3d_deadband_throttle = 50
set 3d_limit_low = 1000
set 3d_limit_high = 2000
set 3d_switched_mode = OFF
set servo_center_pulse = 1500
set servo_pwm_rate = 50
set servo_lowpass_hz = 0
set tri_unarmed_servo = ON
set channel_forwarding_start = 4
set reboot_character = 82
set serial_update_rate_hz = 100
set accxy_deadband = 40
set accz_deadband = 40
set acc_unarmedcal = ON
set imu_dcm_kp = 2500
set imu_dcm_ki = 0
set small_angle = 25
set auto_disarm_delay = 5
set gyro_cal_on_first_arm = OFF
set gps_provider = NMEA
set gps_sbas_mode = AUTO
set gps_auto_config = ON
set gps_auto_baud = OFF
set gps_ublox_use_galileo = OFF
set gps_rescue_angle = 32
set gps_rescue_initial_alt = 50
set gps_rescue_descent_dist = 200
set gps_rescue_ground_speed = 2000
set gps_rescue_throttle_p = 150
set gps_rescue_throttle_i = 20
set gps_rescue_throttle_d = 50
set gps_rescue_velocity_p = 80
set gps_rescue_velocity_i = 20
set gps_rescue_velocity_d = 15
set gps_rescue_yaw_p = 40
set gps_rescue_throttle_min = 1200
set gps_rescue_throttle_max = 1600
set gps_rescue_throttle_hover = 1280
set gps_rescue_sanity_checks = RESCUE_SANITY_ON
set gps_rescue_min_sats = 8
set deadband = 0
set yaw_deadband = 0
set yaw_control_reversed = OFF
set pid_process_denom = 4
set runaway_takeoff_prevention = ON
set runaway_takeoff_deactivate_delay = 500
set runaway_takeoff_deactivate_throttle_percent = 25
set tlm_inverted = ON
set tlm_halfduplex = ON
set frsky_default_lat = 0
set frsky_default_long = 0
set frsky_gps_format = 0
set frsky_unit = IMPERIAL
set frsky_vfas_precision = 0
set hott_alarm_int = 5
set pid_in_tlm = OFF
set report_cell_voltage = OFF
set ibus_sensor = 1,2,3,0,0,0,0,0,0,0,0,0,0,0,0
set smartport_use_extra_sensors = OFF
set ledstrip_visual_beeper = OFF
set ledstrip_grb_rgb = GRB
set sdcard_dma = OFF
set osd_units = METRIC
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 = ON
set osd_rssi_alarm = 20
set osd_cap_alarm = 2200
set osd_alt_alarm = 100
set osd_esc_temp_alarm = -128
set osd_esc_rpm_alarm = -1
set osd_esc_current_alarm = -1
set osd_core_temp_alarm = 70
set osd_ah_max_pit = 20
set osd_ah_max_rol = 40
set osd_tim1 = 2560
set osd_tim2 = 2561
set osd_vbat_pos = 234
set osd_rssi_pos = 234
set osd_tim_1_pos = 234
set osd_tim_2_pos = 234
set osd_remaining_time_estimate_pos = 234
set osd_flymode_pos = 234
set osd_anti_gravity_pos = 234
set osd_g_force_pos = 234
set osd_throttle_pos = 234
set osd_vtx_channel_pos = 234
set osd_crosshairs_pos = 205
set osd_ah_sbar_pos = 206
set osd_ah_pos = 78
set osd_current_pos = 234
set osd_mah_drawn_pos = 234
set osd_craft_name_pos = 234
set osd_gps_speed_pos = 234
set osd_gps_lon_pos = 234
set osd_gps_lat_pos = 234
set osd_gps_sats_pos = 234
set osd_home_dir_pos = 234
set osd_home_dist_pos = 234
set osd_compass_bar_pos = 234
set osd_altitude_pos = 234
set osd_pid_roll_pos = 234
set osd_pid_pitch_pos = 234
set osd_pid_yaw_pos = 234
set osd_debug_pos = 234
set osd_power_pos = 234
set osd_pidrate_profile_pos = 234
set osd_warnings_pos = 2377
set osd_avg_cell_voltage_pos = 234
set osd_pit_ang_pos = 234
set osd_rol_ang_pos = 234
set osd_battery_usage_pos = 234
set osd_disarmed_pos = 234
set osd_nheading_pos = 234
set osd_nvario_pos = 234
set osd_esc_tmp_pos = 234
set osd_esc_rpm_pos = 234
set osd_rtc_date_time_pos = 234
set osd_adjustment_range_pos = 234
set osd_core_temp_pos = 234
set osd_stat_rtc_date_time = OFF
set osd_stat_tim_1 = OFF
set osd_stat_tim_2 = ON
set osd_stat_max_spd = ON
set osd_stat_max_dist = OFF
set osd_stat_min_batt = ON
set osd_stat_endbatt = OFF
set osd_stat_battery = OFF
set osd_stat_min_rssi = ON
set osd_stat_max_curr = ON
set osd_stat_used_mah = ON
set osd_stat_max_alt = OFF
set osd_stat_bbox = ON
set osd_stat_bb_no = ON
set task_statistics = ON
set debug_mode = NONE
set rate_6pos_switch = OFF
set cpu_overclock = OFF
set pwr_on_arm_grace = 5
set vtx_band = 4
set vtx_channel = 1
set vtx_power = 1
set vtx_low_power_disarm = OFF
set vtx_freq = 5740
set vtx_pit_mode_freq = 0
set vtx_halfduplex = ON
set vcd_video_system = AUTO
set vcd_h_offset = 0
set vcd_v_offset = 0
set max7456_clock = DEFAULT
set max7456_spi_bus = 3
set displayport_msp_col_adjust = 0
set displayport_msp_row_adjust = 0
set displayport_max7456_col_adjust = 0
set displayport_max7456_row_adjust = 0
set displayport_max7456_inv = OFF
set displayport_max7456_blk = 0
set displayport_max7456_wht = 2
set esc_sensor_halfduplex = OFF
set esc_sensor_current_offset = 0
set led_inversion = 0
set dashboard_i2c_bus = 2
set dashboard_i2c_addr = 60
set camera_control_mode = HARDWARE_PWM
set camera_control_ref_voltage = 330
set camera_control_key_delay = 180
set camera_control_internal_resistance = 470
set camera_control_inverted = OFF
set rangefinder_hardware = NONE
set pinio_config = 1,1,1,1
set pinio_box = 255,255,255,255
set usb_hid_cdc = OFF
set usb_msc_pin_pullup = OFF
set flash_spi_bus = 2
set rcdevice_init_dev_attempts = 4
set rcdevice_init_dev_attempt_interval = 1000

# profile
profile 0

set dterm_lowpass_type = PT1
set dterm_lowpass_hz = 100
set dterm_lowpass2_hz = 200
set dterm_notch_hz = 0
set dterm_notch_cutoff = 160
set vbat_pid_gain = OFF
set pid_at_min_throttle = ON
set anti_gravity_mode = SMOOTH
set anti_gravity_threshold = 250
set anti_gravity_gain = 5000
set feedforward_transition = 0
set acc_limit_yaw = 100
set acc_limit = 0
set crash_dthreshold = 50
set crash_gthreshold = 400
set crash_setpoint_threshold = 350
set crash_time = 500
set crash_delay = 0
set crash_recovery_angle = 10
set crash_recovery_rate = 100
set crash_limit_yaw = 200
set crash_recovery = OFF
set iterm_rotation = ON
set smart_feedforward = OFF
set iterm_relax = OFF
set iterm_relax_type = GYRO
set iterm_relax_cutoff = 11
set iterm_windup = 40
set iterm_limit = 150
set pidsum_limit = 500
set pidsum_limit_yaw = 400
set yaw_lowpass_hz = 0
set throttle_boost = 5
set throttle_boost_cutoff = 15
set acro_trainer_angle_limit = 20
set acro_trainer_lookahead_ms = 50
set acro_trainer_debug_axis = ROLL
set acro_trainer_gain = 75
set p_pitch = 50
set i_pitch = 50
set d_pitch = 27
set f_pitch = 60
set p_roll = 46
set i_roll = 45
set d_roll = 25
set f_roll = 60
set p_yaw = 65
set i_yaw = 45
set d_yaw = 0
set f_yaw = 60
set p_level = 50
set i_level = 50
set d_level = 75
set level_limit = 55
set horizon_tilt_effect = 75
set horizon_tilt_expert_mode = OFF
set abs_control_gain = 0
set abs_control_limit = 90
set abs_control_error_limit = 20

# rateprofile
rateprofile 0

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 tpa_rate = 10
set tpa_breakpoint = 1650
set throttle_limit_type = OFF
set throttle_limit_percent = 100


------------------------------------------------------------------------------------------------

# diff all

# version
# Betaflight / OMNIBUSF4SD (OBSD) 3.5.1 Sep  8 2018 / 05:40:39 (d9fb5ca13) MSP API: 1.40

board_name OMNIBUSF4SD
manufacturer_id 
mcu_id 001e00303436470133373838
signature 

# reset configuration to default settings
defaults nosave

# name
name Dankfly5000

# resources
resource SERIAL_RX 11 A09

# mixer

# servo

# servo mix


# feature
feature -RX_PARALLEL_PWM
feature -ANTI_GRAVITY
feature -DYNAMIC_FILTER
feature RX_SERIAL
feature SOFTSERIAL
feature TELEMETRY

# beeper

# beacon

# map

# serial
serial 5 64 115200 57600 0 115200
serial 30 32 115200 57600 0 115200

# led

# color

# mode_color

# aux

# adjrange

# rxrange

# vtx

# rxfail

# master
set acc_calibration = 21,83,-110
set serialrx_provider = FPORT
set serialrx_inverted = ON
set dshot_idle_value = 100
set motor_pwm_protocol = DSHOT300
set tlm_inverted = ON

# 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

(17-Sep-2018, 09:30 PM)kaitylynn Wrote: Might you post a screenshot of your PORTS and CONFIGURATION tabs in BetaFlight?

I cannot tell if you have the RX and radio bound...

agh the ports screenshot wouldn't post. I have UART6 set for serialRX and a softserial port activated with Smartport Telemetry. And of course the USB config/msp on.

the receiver is definitely giving me the solid green indicating its bound and i get RSSI and RxBt readings off the receiver, but that's it, i know there should be more. You can't really tell the green light is on in the pic.

You probably got asked too many questions and it doesn't look like you responded to the one about the R-XSR firmware question which is important before analysing your dump config values. Did you revert the R-XSR back to standard SBUS firmware, or are you still running F.PORT firmware on it?

(17-Sep-2018, 10:19 PM)SnowLeopardFPV Wrote: You probably got asked too many questions and it doesn't look like you responded to the one about the R-XSR firmware question which is important before analysing your dump config values. Did you revert the R-XSR back to standard SBUS firmware, or are you still running F.PORT firmware on it?

Whoops you're right lol. I have not reverted the FW back to SBUS. It didn't occur to me to try that, probably because fport is the latest thing that would require different wiring in my case. I'll give that a shot.

Yes. F.PORT is the new kid on the block. It's the route I intend to go with mine in the coming weeks and while I know all the theory behind it and how to set it up, I don't currently have any proven real world experience of doing that (yet).

SBUS and S.PORT are proven technologies that most will have already set up and can probably better advise you on or help you to troubleshoot. If you wanted to use F.PORT you would need to completely disconnect the green SBUS wire from the flight controller and connect the yellow S.PORT wire to the SBUS pad on the flight controller instead (the original green SBUS wire becomes redundant with F.PORT firmware installed).

If you go back to SBUS firmware on the receiver, do the following:-

1. Leave the green SBUS wire connected to the SBUS pad on the flight controller (as it already is), but move the yellow S.PORT wire to the TX3 pad instead assuming that nothing else is connected to that. This will then avoid any potential UART1 conflicts with both MSP and S.PORT trying to use the same UART.
   
   
2. Run the following commands in the CLI to turn off SoftSerial (you don't need it as you are using the ununverted S.PORT signal direct from the P pad on the R-XSR), and to correct your receiver settings for SBUS firmware...
   
   
   Code:

   feature -SOFTSERIAL
set serialrx_provider = SBUS
set serialrx_inverted = OFF
save
   
   
3. In the Ports tab do the following:
   -> Make sure UART6 has "Serial Rx" switched on with all other values disabled.
   -> If you have "Telemetry Output" set against UART1, set it back to disabled.
   -> Make sure the UART3 port has "Telemetry Output" set as SmartPort with an AUTO baud rate and all other values disabled.
   

I think that's it  

Let us know if you get any problems after doing that.

(17-Sep-2018, 11:36 PM)SnowLeopardFPV Wrote: Yes. F.PORT is the new kid on the block. It's the route I intend to go with mine in the coming weeks and while I know all the theory behind it and how to set it up, I don't currently have any proven real world experience of doing that (yet).

SBUS and S.PORT are proven technologies that most will have already set up and can probably better advise you on or help you to troubleshoot. If you wanted to use F.PORT you would need to completely disconnect the green SBUS wire from the flight controller and connect the yellow S.PORT wire to the SBUS pad on the flight controller instead (the original green SBUS wire becomes redundant with F.PORT firmware installed).

If you go back to SBUS firmware on the receiver, do the following:-

1. Leave the green SBUS wire connected to the SBUS pad on the flight controller (as it already is), but move the yellow S.PORT wire to the TX3 pad instead assuming that nothing else is connected to that. This will then avoid any potential UART1 conflicts with both MSP and S.PORT trying to use the same UART.
   
   
2. Run the following commands in the CLI to turn off SoftSerial (you don't need it as you are using the ununverted S.PORT signal direct from the P pad on the R-XSR), and to correct your receiver settings for SBUS firmware...
   
   feature -SOFTSERIALset serialrx_provider = SBUSset serialrx_inverted = OFFsave
3. In the Ports tab do the following:
   -> Make sure UART6 has "Serial Rx" switched on with all other values disabled.
   -> If you have "Telemetry Output" set against UART1, set it back to disabled.
   -> Make sure the UART3 port has "Telemetry Output" set as SmartPort with an AUTO baud rate and all other values disabled.
   

I think that's it  

Let us know if you get any problems after doing that.

I am happy to report that for the first time ever, i am seeing movement in Betaflight. This took me DAYS to achieve, it must have been that yellow wire!! I had to set it to TAER for some reason because the sticks were reversed initially. But now it's fine. I'll let you know if i have more issues getting it armed after creating a switch for it as any smart flier should. This process of simply getting it to do anything in betaflight has been such an ongoing ordeal, i can't thank you enough!!!

(18-Sep-2018, 12:27 AM)nintendude7cubed Wrote: I am happy to report that for the first time ever, i am seeing movement in Betaflight. This took me DAYS to achieve, it must have been that yellow wire!! I had to set it to TAER for some reason because the sticks were reversed initially. But now it's fine. I'll let you know if i have more issues getting it armed after creating a switch for it as any smart flier should. This process of simply getting it to do anything in betaflight has been such an ongoing ordeal, i can't thank you enough!!!

Great news  At least now you can hopefully get out flying  

Yeah, TAER is the default value in OpenTX on the Taranis. I've actually done it the other way round and configured my Taranis to use a default of AETR so that for any new models I set up in the Taranis, it will use AETR as a default which matches the default in BetaFlight (or the value that appears when you select "FrSky / Futaba / Hitec" from the Channel map dropdown). It doesn't actually matter which way you do it as long as they match.

When you're first starting out in this hobby, all the stuff you seem to need to learn is enough to fry your brain  I've completely lost count of the literally (no exaggeration) hundreds of hours of time I have spent watching videos and reading articles related to the hobby over the past 6 months.

(18-Sep-2018, 12:41 AM)SnowLeopardFPV Wrote: Great news  At least now you can hopefully get out flying  

Yeah, TAER is the default value in OpenTX on the Taranis. I've actually done it the other way round and configured my Taranis to use a default of AETR so that for any new models I set up in the Taranis, it will use AETR as a default which matches the default in BetaFlight (or the value that appears when you select "FrSky / Futaba / Hitec" from the Channel map dropdown). It doesn't actually matter which way you do it as long as they match.

When you're first starting out in this hobby, all the stuff you seem to need to learn is enough to fry your brain  I've completely lost count of the literally (no exaggeration) hundreds of hours of time I have spent watching videos and reading articles related to the hobby over the past 6 months.

It's been like that for me, just condensed over two weeks with every spare moment of my life being dedicated to trying to figure out how to fly this thing. I exhausted every source on the Omnibus f4 controller specifically, flight controllers in general, frsky receivers and their differences. It's been nuts. But it has also sucked me into the culture so quickly and i'm still ambitious that my flight skill will justify a future more powerful build. Just gotta wait until tomorrow since i just missed the daylight today on trying to figure this out. But on the bright side, it just so happens that my runcam finally came today, so i'll be able to record 1080p right from the beginning. I'm still sitting here shocked that my drone can finally work independently from betaflight after all this time! It's reassembled and ready to go! I can't wait! Thanks again!!!

Too dark to fly outside? Bah...fly it in your living room   

Only JOKING...please don't even think about doing that!! 

(18-Sep-2018, 01:27 AM)SnowLeopardFPV Wrote: Too dark to fly outside? Bah...fly it in your living room     

Only JOKING...please don't even think about doing that!! 

LOL...dang, a 5" indoors would carry a very high potential DISASTER.  Shredding plants, shrieking cats, chopped up walls and scraped up halls

My family banned the flight of anything other than Tiny Whoops and they have to have cowled props.  The ESC tones are enough to bring the family to their feet!

nintendude7cubed, glad you were able to make it see reason and work! It can be supremely frustrating to have issues crop up in the beginning and even when you are seasoned they often are not fun. IntoFPV is a great place to work through them, I wanted to take a moment to welcome you to the forums!

(18-Sep-2018, 01:38 AM)kaitylynn Wrote: LOL...dang, a 5" indoors would carry a very high potential DISASTER.  Shredding plants, shrieking cats, chopped up walls and scraped up halls

My family banned the flight of anything other than Tiny Whoops and they have to have cowled props.  The ESC tones are enough to bring the family to their feet!

Yeah...I've seen more than enough videos of people who've never flown a drone in their life before with their brand new DJI Mavic Pro or Phantom 4, too impatient to wait for daylight or until the weather subsides after unboxing it, and thinking it's a good idea to try flying it inside. When it can't lock onto a GPS signal from inside the house and it drops into ATTI mode they have no idea what to do, and you can probably guess what happens next