Posts: 11 Threads: 1 Likes Received: 0 in 0 posts Likes Given: 2 Joined: Apr 2020 Reputation: 0 Hey!
I got into FPV couple months ago and I fly on daily basis. I did some upgrades on my 5 inch quad already but most of them were just replacements (not really hard to figure them out). I'm thinking about buying a FrSky R9M and Rapidfire module to extend my range and feel safer when flying in places where I really wouldn't like to lose the signal.
The problem I'm having is that I'm not sure, how I'll install the reciever and connect it to my flight controller. I have Cleanflight SP Racing MOF3 v1 flight controller on my quad and I'd like to connect R9 slim+ reciever to it. I don't have enough knowledge to do the upgrade on my own. I'd like to ask you guys to recommend me some literature (papers, books, videos...) where I can learn from. Any similar guides or even your help would be very nice.
Thanks for your answers and have a lovely day.
flyer555 ![[-]](https://intofpv.com/images/collapse.png) • Posts: 668 Threads: 31 Likes Received: 208 in 158 posts Likes Given: 95 Joined: Feb 2019 Reputation: 14 Don't worry, you have the knowledge. Connecting the r9 to the FC should be at the same tx and rx pads. What will give the extended range is between receiver and transmitter. The rapidfire module is for you goggles, so for that, also think about some nice antennas and a powerful vtx, with 800mw or 600mw at least for the maximum range, penetration or peace of mind. You should also had gps to the build. That requires some custom firmware for the f3. Posts: 214 Threads: 9 Likes Received: 110 in 76 posts Likes Given: 34 Joined: May 2019 Reputation: 6 16-Apr-2020, 01:54 PM (This post was last modified: 16-Apr-2020, 01:54 PM by Flickeryvision.) Go with crossfire! Get a TBS crossfire Micro TX (or the big one if you have the $$$) instead of the r9m and a TBS fusion instead of rapid fire (they perform about the same, but with the fusion module and crossfire (and a tbs vtx) you will be able to streamline your whole setup in the future. You will love them so much I promise. Google them, check some reviews and I'm sure you will be convinced (or not  ). TBS ( team black sheep) makes some of the best stuff in the industry, especially for long range. They have great support and great products. disclaimer: I am a TBS fanboy.. FOR GOOD REASON! Posts: 11 Threads: 1 Likes Received: 0 in 0 posts Likes Given: 2 Joined: Apr 2020 Reputation: 0 16-Apr-2020, 02:00 PM (This post was last modified: 16-Apr-2020, 02:13 PM by flyer555.) Maiden Flight, thanks for your answer. I was looking at all the things that need to be connected (picture below), that is what worried me. ![[Image: FniHypy.png]](https://i.imgur.com/FniHypy.png) I know where to connect VCC, TX, RX and GND pins, but I'm not sure for the S. PORT, S BUS in, S BUS out and RSSI out. I honestly have no idea what those words mean (yet). I just heard of them quite a couple of times. I need to do more research on that. So, probably I need to connect all of them, right? Btw, I'm currently running a FS IA6B reciever, which I'm planning to replace. It has three wires connected to the FC with a connector. I have a good understanding and everything for rapidfire. Also, I'm currently running vtx with 200 mW. You think I should upgrade that as well? GPS is also something I'll add in the future. Thanks again  EDIT: I'm running a Pagoda on my quad, another Pagoda and Realacc triple feed patch antenna on my goggles. • Posts: 21,397 Threads: 593 Likes Received: 9,029 in 6,683 posts Likes Given: 1,428 Joined: Jun 2018 Reputation: 795 If you want run an R9M module on your transmitter and an R9 Slim+ receiver on your quad, you need to do the following:- - Make sure you are on an up-to-date version of OpenTX (I recommend installing the latest version which as of today is 2.3.7 - see HERE). When you flash OpenTX, in the settings for your radio profile you need to tick the "flexr9m" option (see HERE).
- Make sure you flash the R9M module with the latest version of the FLEX firmware.
- Make sure you flash the R9 Slim+ receiver with the latest version of the FLEX firmware (the FPORT version).
- If your SP Racing FC is still on Cleanflight then I highly recommend that you update it to the last version of Betaflight 3.x which is 3.5.7 (HERE) so you can make use of the FPORT protocol which Cleanflight doesn't support. To keep things simple I would avoid Betaflight 4.x on an F3 flight controller because some features have been removed so the firmware will fit in the flash memory of the F3 MCU.
- Wire the VCC and GND pins from the CON1 connector on the Slim+ to a 5V and GND pad respectively on your SP Racing FC.
- Wire the S.Port pin from the CON1 connector on the Slim+ to the TX pad of a spare unused UART on your SP Racing FC.
- In the Ports tab of Betaflight Configurator switch "Serial RX" ON for the UART you chose in (6) and make sure "Serial RX" is switched OFF for all other UARTs.
- Then run the following block of commands in the Betaflight Configurator CLI...
Code: feature -RX_PPM
feature -RX_PARALLEL_PWM
feature RX_SERIAL
set serialrx_provider = FPORT
set serialrx_halfduplex = ON
set serialrx_inverted = ON
save
Then bind your R9M module to your R9 Slim+ and check for stick movements in the Betaflight Configurator Receiver tab. Job done  • Posts: 11 Threads: 1 Likes Received: 0 in 0 posts Likes Given: 2 Joined: Apr 2020 Reputation: 0 (16-Apr-2020, 03:16 PM)SnowLeopardFPV Wrote: If you want run an R9M module on your transmitter and an R9 Slim+ receiver on your quad, you need to do the following:-
- Make sure you are on an up-to-date version of OpenTX (I recommend installing the latest version which as of today is 2.3.7 - see HERE). When you flash OpenTX, in the settings for your radio profile you need to tick the "flexr9m" option (see HERE).
- Make sure you flash the R9M module with the latest version of the FLEX firmware.
- Make sure you flash the R9 Slim+ receiver with the latest version of the FLEX firmware (the FPORT version).
- If your SP Racing FC is still on Cleanflight then I highly recommend that you update it to the last version of Betaflight 3.x which is 3.5.7 (HERE) so you can make use of the FPORT protocol which Cleanflight doesn't support. To keep things simple I would avoid Betaflight 4.x on an F3 flight controller because some features have been removed so the firmware will fit in the flash memory of the F3 MCU.
- Wire the VCC and GND pins from the CON1 connector on the Slim+ to a 5V and GND pad respectively on your SP Racing FC.
- Wire the S.Port pin from the CON1 connector on the Slim+ to the TX pad of a spare unused UART on your SP Racing FC.
- In the Ports tab of Betaflight Configurator switch "Serial RX" ON for the UART you chose in (6) and make sure "Serial RX" is switched OFF for all other UARTs.
- Then run the following block of commands in the Betaflight Configurator CLI...
Code: feature -RX_PPM
feature -RX_PARALLEL_PWM
feature RX_SERIAL
set serialrx_provider = FPORT
set serialrx_halfduplex = ON
set serialrx_inverted = ON
save
Then bind your R9M module to your R9 Slim+ and check for stick movements in the Betaflight Configurator Receiver tab.
Job done Thanks! I think this should help a lot I'll post here if I encounter some issues or have any additional questions. • Posts: 1,798 Threads: 57 Likes Received: 254 in 227 posts Likes Given: 102 Joined: Aug 2019 Reputation: 12 (16-Apr-2020, 04:16 PM)flyer555 Wrote: Thanks! I think this should help a lot
I'll post here if I encounter some issues or have any additional questions. You should take the advice and go with a crossfire unit though. We were just tlaking in another thread about how R9 is always giving peopele issues and how everyone that gets an R9 system usually ends up getting crossfire eventually. So to save some money... save more money and get crossfire ;D 'Ignore' is the route word of Ignorant.
• Posts: 11 Threads: 1 Likes Received: 0 in 0 posts Likes Given: 2 Joined: Apr 2020 Reputation: 0 (16-Apr-2020, 08:50 PM)bLoWsMokE Wrote: You should take the advice and go with a crossfire unit though. We were just tlaking in another thread about how R9 is always giving peopele issues and how everyone that gets an R9 system usually ends up getting crossfire eventually. So to save some money... save more money and get crossfire ;D Hey, thanks for your advice. Would you be so kind and paste a link of the thread. I'd be more than happy to read it. • Posts: 1,798 Threads: 57 Likes Received: 254 in 227 posts Likes Given: 102 Joined: Aug 2019 Reputation: 12 (17-Apr-2020, 06:18 AM)flyer555 Wrote: Hey, thanks for your advice. Would you be so kind and paste a link of the thread. I'd be more than happy to read it. Oh jeeze it's buried somewhere in the beginners section on the first page... it's not actually related to exactly that topic... it kinda just devolved into a minimal discussion about it..... Maybe snow or voodoo remembers which thread..... just check the ones that have to do with a TX or maybe the one about "getting more range" suttin like that. It's buried in there. 'Ignore' is the route word of Ignorant.
• Posts: 11 Threads: 1 Likes Received: 0 in 0 posts Likes Given: 2 Joined: Apr 2020 Reputation: 0 (16-Apr-2020, 03:16 PM)SnowLeopardFPV Wrote: If you want run an R9M module on your transmitter and an R9 Slim+ receiver on your quad, you need to do the following:-
- Make sure you are on an up-to-date version of OpenTX (I recommend installing the latest version which as of today is 2.3.7 - see HERE). When you flash OpenTX, in the settings for your radio profile you need to tick the "flexr9m" option (see HERE).
- Make sure you flash the R9M module with the latest version of the FLEX firmware.
- Make sure you flash the R9 Slim+ receiver with the latest version of the FLEX firmware (the FPORT version).
- If your SP Racing FC is still on Cleanflight then I highly recommend that you update it to the last version of Betaflight 3.x which is 3.5.7 (HERE) so you can make use of the FPORT protocol which Cleanflight doesn't support. To keep things simple I would avoid Betaflight 4.x on an F3 flight controller because some features have been removed so the firmware will fit in the flash memory of the F3 MCU.
- Wire the VCC and GND pins from the CON1 connector on the Slim+ to a 5V and GND pad respectively on your SP Racing FC.
- Wire the S.Port pin from the CON1 connector on the Slim+ to the TX pad of a spare unused UART on your SP Racing FC.
- In the Ports tab of Betaflight Configurator switch "Serial RX" ON for the UART you chose in (6) and make sure "Serial RX" is switched OFF for all other UARTs.
- Then run the following block of commands in the Betaflight Configurator CLI...
Code: feature -RX_PPM
feature -RX_PARALLEL_PWM
feature RX_SERIAL
set serialrx_provider = FPORT
set serialrx_halfduplex = ON
set serialrx_inverted = ON
save
Then bind your R9M module to your R9 Slim+ and check for stick movements in the Betaflight Configurator Receiver tab.
Job done Hey, I finally found time and spent a day setting this up. I did step by step of what you told me to do. I successfully bound the R9M module to the R9 Slim+. After that, I checked stick movements in Betaflight and there is no response. So, my guess would be that I need to set up something in Betaflight, so FC can correctly read from UART3 TX port, where S. Port of Slim+ is connected? Any other ideas? I haven't taken any pictures yet because there are many things that I could've taken a picture of... So, could someone maybe be so kind and tell me what to post here so you guys can help me out. I'd really appreciate it. Thanks! • Posts: 21,397 Threads: 593 Likes Received: 9,029 in 6,683 posts Likes Given: 1,428 Joined: Jun 2018 Reputation: 795 Can you please run both the "dump" and "diff all" commands in the Betaflight Configurator CLI tab and copy/paste the results back here.
Please also post some photos of the wiring and connections between your receiver and flight controller. • Posts: 11 Threads: 1 Likes Received: 0 in 0 posts Likes Given: 2 Joined: Apr 2020 Reputation: 0 (01-Sep-2020, 10:26 AM)SnowLeopardFPV Wrote: Can you please run both the "dump" and "diff all" commands in the Betaflight Configurator CLI tab and copy/paste the results back here.
Please also post some photos of the wiring and connections between your receiver and flight controller. Sure. First the outputs of the commands: dump Code: # dump
# Betaflight / SPRACINGF3 (SRF3) 4.0.6 Sep 1 2019 / 01:05:57 (2a64051a2) MSP API: 1.41 / FEATURE CUT LEVEL 6
batch start
name -
resource BEEPER 1 C15
resource MOTOR 1 A06
resource MOTOR 2 A07
resource MOTOR 3 A11
resource MOTOR 4 A12
resource MOTOR 5 B08
resource MOTOR 6 B09
resource MOTOR 7 A02
resource MOTOR 8 A03
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 A00
resource SONAR_TRIGGER 1 B00
resource SONAR_ECHO 1 B01
resource LED_STRIP 1 A08
resource SERIAL_TX 1 A09
resource SERIAL_TX 2 A14
resource SERIAL_TX 3 B10
resource SERIAL_TX 4 NONE
resource SERIAL_TX 5 NONE
resource SERIAL_TX 6 NONE
resource SERIAL_TX 7 NONE
resource SERIAL_TX 8 NONE
resource SERIAL_TX 9 NONE
resource SERIAL_TX 10 NONE
resource SERIAL_TX 11 B05
resource SERIAL_TX 12 B01
resource SERIAL_RX 1 A10
resource SERIAL_RX 2 A15
resource SERIAL_RX 3 B11
resource SERIAL_RX 4 NONE
resource SERIAL_RX 5 NONE
resource SERIAL_RX 6 NONE
resource SERIAL_RX 7 NONE
resource SERIAL_RX 8 NONE
resource SERIAL_RX 9 NONE
resource SERIAL_RX 10 NONE
resource SERIAL_RX 11 B04
resource SERIAL_RX 12 B00
resource I2C_SCL 1 B06
resource I2C_SCL 2 NONE
resource I2C_SDA 1 B07
resource I2C_SDA 2 NONE
resource LED 1 B03
resource LED 2 NONE
resource LED 3 NONE
resource SPI_SCK 1 NONE
resource SPI_SCK 2 B13
resource SPI_SCK 3 NONE
resource SPI_MISO 1 NONE
resource SPI_MISO 2 B14
resource SPI_MISO 3 NONE
resource SPI_MOSI 1 NONE
resource SPI_MOSI 2 B15
resource SPI_MOSI 3 NONE
resource ESCSERIAL 1 A00
resource CAMERA_CONTROL 1 NONE
resource ADC_BATT 1 A04
resource ADC_RSSI 1 B02
resource ADC_CURR 1 A05
resource ADC_EXT 1 NONE
resource BARO_CS 1 NONE
resource COMPASS_CS 1 NONE
resource COMPASS_EXTI 1 C14
resource FLASH_CS 1 B12
resource GYRO_EXTI 1 C13
resource GYRO_CS 1 NONE
mixer QUADX
mmix reset
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
smix reset
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 TELEMETRY
feature RSSI_ADC
feature AIRMODE
feature ANTI_GRAVITY
feature DYNAMIC_FILTER
beeper GYRO_CALIBRATED
beeper RX_LOST
beeper RX_LOST_LANDING
beeper DISARMING
beeper ARMING
beeper ARMING_GPS_FIX
beeper ARMING_GPS_NO_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_CLOSE
beeper RC_SMOOTHING_INIT_FAIL
beacon -RX_LOST
beacon -RX_SET
map AETR1234
serial 0 1 115200 57600 0 115200
serial 1 0 115200 57600 0 115200
serial 2 64 115200 57600 0 115200
aux 0 0 1 1475 2100 0 0
aux 1 27 0 1475 2100 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 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
adjrange 15 0 0 900 900 0 0 0 0
adjrange 16 0 0 900 900 0 0 0 0
adjrange 17 0 0 900 900 0 0 0 0
adjrange 18 0 0 900 900 0 0 0 0
adjrange 19 0 0 900 900 0 0 0 0
adjrange 20 0 0 900 900 0 0 0 0
adjrange 21 0 0 900 900 0 0 0 0
adjrange 22 0 0 900 900 0 0 0 0
adjrange 23 0 0 900 900 0 0 0 0
adjrange 24 0 0 900 900 0 0 0 0
adjrange 25 0 0 900 900 0 0 0 0
adjrange 26 0 0 900 900 0 0 0 0
adjrange 27 0 0 900 900 0 0 0 0
adjrange 28 0 0 900 900 0 0 0 0
adjrange 29 0 0 900 900 0 0 0 0
rxrange 0 1000 2000
rxrange 1 1000 2000
rxrange 2 1000 2000
rxrange 3 1000 2000
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 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
display_name -
set gyro_hardware_lpf = NORMAL
set gyro_sync_denom = 3
set gyro_lowpass_type = BIQUAD
set gyro_lowpass_hz = 150
set gyro_lowpass2_type = PT1
set gyro_lowpass2_hz = 150
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 dyn_notch_range = AUTO
set dyn_notch_width_percent = 8
set dyn_notch_q = 120
set dyn_notch_min_hz = 150
set dyn_lpf_gyro_min_hz = 150
set dyn_lpf_gyro_max_hz = 450
set gyro_filter_debug_axis = ROLL
set acc_hardware = NONE
set acc_lpf_hz = 10
set acc_trim_pitch = 0
set acc_trim_roll = 0
set acc_calibration = -20,-24,51
set align_mag = DEFAULT
set mag_bustype = I2C
set mag_i2c_device = 1
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 = I2C
set baro_spi_device = 0
set baro_i2c_device = 1
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 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 fpv_mix_degrees = 0
set max_aux_channels = 14
set serialrx_provider = FPORT
set serialrx_inverted = ON
set airmode_start_throttle_percent = 25
set rx_min_usec = 885
set rx_max_usec = 2115
set serialrx_halfduplex = ON
set adc_device = 2
set adc_vrefint_calibration = 0
set adc_tempsensor_calibration30 = 0
set adc_tempsensor_calibration110 = 0
set blackbox_p_ratio = 32
set blackbox_device = SPIFLASH
set blackbox_record_acc = ON
set blackbox_mode = NORMAL
set min_throttle = 1035
set max_throttle = 1990
set min_command = 1000
set dshot_idle_value = 550
set dshot_burst = OFF
set use_unsynced_pwm = OFF
set motor_pwm_protocol = ONESHOT125
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 = 270
set gimbal_mode = NORMAL
set bat_capacity = 0
set vbat_max_cell_voltage = 430
set vbat_full_cell_voltage = 410
set vbat_min_cell_voltage = 330
set vbat_warning_cell_voltage = 350
set vbat_hysteresis = 1
set current_meter = ADC
set battery_meter = ADC
set vbat_detect_cell_voltage = 300
set use_vbat_alerts = ON
set use_cbat_alerts = OFF
set cbat_alert_percent = 10
set vbat_cutoff_percent = 100
set force_battery_cell_count = 0
set vbat_lpf_period = 30
set ibat_lpf_period = 10
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 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 deadband = 0
set yaw_deadband = 0
set yaw_control_reversed = OFF
set pid_process_denom = 2
set runaway_takeoff_prevention = ON
set runaway_takeoff_deactivate_delay = 500
set runaway_takeoff_deactivate_throttle_percent = 20
set tlm_inverted = OFF
set tlm_halfduplex = ON
set frsky_vfas_precision = 0
set hott_alarm_int = 5
set pid_in_tlm = OFF
set report_cell_voltage = OFF
set telemetry_disabled_sensors = 491520
set ledstrip_visual_beeper = OFF
set ledstrip_visual_beeper_color = WHITE
set ledstrip_grb_rgb = GRB
set ledstrip_profile = RACE
set ledstrip_race_color = ORANGE
set ledstrip_beacon_color = WHITE
set ledstrip_beacon_period_ms = 500
set ledstrip_beacon_percent = 50
set ledstrip_beacon_armed_only = 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_fail_safe = ON
set osd_warn_launch_control = ON
set osd_warn_no_gps_rescue = ON
set osd_warn_gps_rescue_disabled = 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_ah_max_pit = 20
set osd_ah_max_rol = 40
set osd_ah_invert = OFF
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_motor_diag_pos = 234
set osd_craft_name_pos = 234
set osd_display_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_flight_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_esc_tmp_pos = 234
set osd_esc_rpm_pos = 234
set osd_esc_rpm_freq_pos = 234
set osd_rtc_date_time_pos = 234
set osd_adjustment_range_pos = 234
set osd_flip_arrow_pos = 234
set osd_log_status_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 osd_stat_max_g_force = OFF
set osd_stat_max_esc_temp = OFF
set osd_stat_max_esc_rpm = OFF
set osd_stat_min_link_quality = OFF
set osd_stat_flight_dist = OFF
set osd_stat_max_fft = OFF
set task_statistics = ON
set debug_mode = NONE
set rate_6pos_switch = OFF
set pwr_on_arm_grace = 5
set scheduler_optimize_rate = OFF
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 displayport_msp_col_adjust = 0
set displayport_msp_row_adjust = 0
set esc_sensor_halfduplex = OFF
set esc_sensor_current_offset = 0
set led_inversion = 0
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 flash_spi_bus = 2
set rcdevice_init_dev_attempts = 6
set rcdevice_init_dev_attempt_interval = 1000
set rcdevice_protocol_version = 0
set rcdevice_feature = 0
set gyro_1_bustype = I2C
set gyro_1_spibus = 0
set gyro_1_i2cBus = 1
set gyro_1_i2c_address = 0
set gyro_1_sensor_align = CW270
profile 0
set dyn_lpf_dterm_min_hz = 150
set dyn_lpf_dterm_max_hz = 250
set dterm_lowpass_type = BIQUAD
set dterm_lowpass_hz = 150
set dterm_lowpass2_type = PT1
set dterm_lowpass2_hz = 100
set dterm_notch_hz = 0
set dterm_notch_cutoff = 0
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 = 0
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 = OFF
set iterm_windup = 100
set iterm_limit = 400
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 = 67
set i_pitch = 50
set d_pitch = 36
set f_pitch = 0
set p_roll = 46
set i_roll = 50
set d_roll = 32
set f_roll = 0
set p_yaw = 80
set i_yaw = 45
set d_yaw = 0
set f_yaw = 0
set angle_level_strength = 50
set horizon_level_strength = 50
set horizon_transition = 75
set level_limit = 55
set horizon_tilt_effect = 75
set horizon_tilt_expert_mode = OFF
set use_integrated_yaw = OFF
set integrated_yaw_relax = 200
set d_min_roll = 22
set d_min_pitch = 26
set d_min_yaw = 0
set d_min_boost_gain = 27
set d_min_advance = 20
set motor_output_limit = 100
set auto_profile_cell_count = 0
set launch_control_mode = NORMAL
set launch_trigger_allow_reset = ON
set launch_trigger_throttle_percent = 20
set launch_angle_limit = 0
set launch_control_gain = 40
rateprofile 0
set thr_mid = 50
set thr_expo = 0
set rates_type = BETAFLIGHT
set roll_rc_rate = 155
set pitch_rc_rate = 155
set yaw_rc_rate = 175
set roll_expo = 12
set pitch_expo = 12
set yaw_expo = 7
set roll_srate = 70
set pitch_srate = 70
set yaw_srate = 60
set tpa_rate = 50
set tpa_breakpoint = 1500
set throttle_limit_type = OFF
set throttle_limit_percent = 100
set roll_rate_limit = 1998
set pitch_rate_limit = 1998
set yaw_rate_limit = 1998
batch end
diff all Code: # diff all
# Betaflight / SPRACINGF3 (SRF3) 4.0.6 Sep 1 2019 / 01:05:57 (2a64051a2) MSP API: 1.41 / FEATURE CUT LEVEL 6
batch start
defaults nosave
mcu_id 001f00235734571420363930
feature -RX_PPM
feature RX_SERIAL
serial 2 64 115200 57600 0 115200
aux 0 0 1 1475 2100 0 0
aux 1 27 0 1475 2100 0 0
set acc_hardware = NONE
set acc_calibration = -20,-24,51
set serialrx_provider = FPORT
set serialrx_inverted = ON
set serialrx_halfduplex = ON
set min_throttle = 1035
set max_throttle = 1990
set align_board_yaw = 270
profile 0
set p_pitch = 67
set i_pitch = 50
set d_pitch = 36
set f_pitch = 0
set p_roll = 46
set i_roll = 50
set d_roll = 32
set f_roll = 0
set p_yaw = 80
set i_yaw = 45
set d_min_roll = 22
set d_min_pitch = 26
profile 1
profile 2
profile 0
rateprofile 0
set roll_rc_rate = 155
set pitch_rc_rate = 155
set yaw_rc_rate = 175
set roll_expo = 12
set pitch_expo = 12
set yaw_expo = 7
set yaw_srate = 60
rateprofile 1
rateprofile 2
rateprofile 3
rateprofile 4
rateprofile 5
rateprofile 0
save
I'm adding some photos as well: wiring R9 Slim plus to the FC (red wire to +, black wire to - and green wire to TX... everything on UART3) ![[Image: s56YwDh.png]](https://imgur.com/s56YwDh.png) wire colors on R9 Slim plus (red for Vcc, black for GND and green for S. Port) ![[Image: k2ans8a.png]](https://imgur.com/k2ans8a.png) green LED lid on R9 Slim plus (bound) ![[Image: 2cBVA20.png]](https://imgur.com/2cBVA20.png) Indication on the radio ![[Image: vdCU7Ct.png]](https://imgur.com/vdCU7Ct.png) Thanks for you effort and time in advance • Posts: 21,397 Threads: 593 Likes Received: 9,029 in 6,683 posts Likes Given: 1,428 Joined: Jun 2018 Reputation: 795 All of your wiring and Betaflight settings look correct. Did you definitely flash the FPORT firmware to the Slim+? What version and file name did you flash? • Posts: 11 Threads: 1 Likes Received: 0 in 0 posts Likes Given: 2 Joined: Apr 2020 Reputation: 0 (01-Sep-2020, 10:20 PM)SnowLeopardFPV Wrote: All of your wiring and Betaflight settings look correct. Did you definitely flash the FPORT firmware to the Slim+? What version and file name did you flash? Firmware download link: https://www.frsky-rc.com/r9-slim-plus/ I had problems with binding when I downloaded the ACCESS firmware. So, I tried with ACCST firmware (version 190201) and successfully bound it. Firmware filename: R9Slim_FLEX_Fport.frk Should I download ACCESS firmware? • Posts: 21,397 Threads: 593 Likes Received: 9,029 in 6,683 posts Likes Given: 1,428 Joined: Jun 2018 Reputation: 795 The firmware you've used should work (assuming that you also flashed the latest 190117 version of the ACCST firmware to your R9M module).
You definitely ticked the "flexr9m" option in OpenTX before you flashed it to your transmitter didn't you? • |
