I changed the receiver and the TX antenna I thot might be bad

Ok correct me if I'm wrong but I believe I should loose signal from the stock dji setup before I lose signal from the crsf and I'm getting rssi critical warnings in places never before so I think there is an issue with the TX because I changed everything else but maybe this is what I get out of this setup

Yes. The Crossfire Micro TX should get you way further than the image in the DJI goggles. I'm running my Micro TX V1 on 100mW and have no problems flying out to ~600 metres on that power level.

Check that you haven't accidentally locked the latency to 150Hz.

How would I check that and also I'm down loading the latest version for beta flight do I flash that to my FC or some thing like that ? I really havent gotten into that part i usually fly what it comes with but I would like to tune it up a little to get it to fly a lil better I think I've studied almost all of bardwells videos so I'm ready but I seen that popup or whatever that said I wasn't using the latest version of bf so here we are

To check the latency setting, power on the Crossfire Nano RX receiver then switch on your transmitter. Then run the Crossfire LUA script on your transmitter and select "XF Nano RX" from the list. The 3rd item down id the "RF Profile". Make sure that is set to "Dynamic" and NOT "150Hz".

What power level is your Crossfire module set to, and is it set to use dynamic power?

To update Betaflight you run the Firmware Flasher in Betaflight Configurtator. However, before you do that make sure you run the "diff all" command in the CLI and save the output to a file somewhere safe on your computer. If you have no reason to update Betaflight then I would just leave it for now until you've fixed the RC Link issues, unless your FC is on a really old version of Betaflight.

The rd is on dynamic tx set to 250mw set to dynamic

# Betaflight / FURYF4OSD (FY4O) 3.5.7 Mar 15 2019 / 21:56:07 (e9130527c) MSP API: 1.40

Is this what version by my FC is using this is the beginning of the dump file

(17-Oct-2020, 05:30 PM)joey Wrote: The rd is on dynamic tx set to 250mw set to dynamic

In that case you shouldn't be getting any range issues. Are you using the 915MHz frequency setting on the Micro TX?

(17-Oct-2020, 05:32 PM)joey Wrote: # Betaflight / FURYF4OSD (FY4O) 3.5.7 Mar 15 2019 / 21:56:07 (e9130527c) MSP API: 1.40

Is this what version by my FC is using this is the beginning of the dump file

That is quite an old version. It might be worth you flashing the FC to the latest version of Betaflight which is 4.2.3. Make sure you keep a copy of the "diff all" as previously mentioned. Because you are 4 whole versions behind, it is going to be safest to just set up all the configuration again manually from scratch on Betaflight 4.2.3. If you post the "diff all" we can tell you what existing settings can be safely transferred across.

# diff all

# version
# Betaflight / FURYF4OSD (FY4O) 3.5.7 Mar 15 2019 / 21:56:07 (e9130527c) MSP API: 1.40

board_name FURYF4OSD
manufacturer_id
mcu_id 0027003e3339470f37343535
signature

# reset configuration to default settings
defaults nosave

# name

# resources

# mixer

# servo

# servo mix


# feature
feature TELEMETRY
feature LED_STRIP
feature AIRMODE

# beeper

# beacon
beacon RX_SET

# map
map TREA1234

# serial
serial 0 0 115200 57600 0 115200
serial 2 64 115200 57600 0 115200
serial 5 1 115200 57600 0 115200

# led

# color

# mode_color

# aux
aux 0 0 0 1825 2100 0 0
aux 1 13 0 1375 1625 0 0
aux 2 35 1 1825 2100 0 0

# adjrange
adjrange 0 0 3 900 2100 12 3 0 0

# rxrange

# vtx

# rxfail

# master
set acc_calibration = -86,14,-366
set rssi_channel = 8
set serialrx_provider = CRSF
set min_throttle = 1070
set use_unsynced_pwm = OFF
set motor_pwm_protocol = DSHOT600
set motor_pwm_rate = 480
set vbat_scale = 109
set yaw_motors_reversed = ON
set small_angle = 180
set osd_vbat_pos = 342
set osd_rssi_pos = 2546
set osd_vtx_channel_pos = 323
set osd_warnings_pos = 2313
set osd_disarmed_pos = 2251
set vtx_band = 5
set vtx_channel = 6
set vtx_power = 4
set vtx_freq = 5843

# profile
profile 0

set dterm_notch_cutoff = 0

# profile
profile 1


# profile
profile 2


# restore original profile selection
profile 0

# rateprofile
rateprofile 0

set roll_rc_rate = 120
set pitch_rc_rate = 120
set yaw_rc_rate = 120
set roll_expo = 10
set pitch_expo = 10
set yaw_expo = 10

# rateprofile
rateprofile 1

set roll_rc_rate = 70
set pitch_rc_rate = 70
set yaw_rc_rate = 70
set roll_expo = 30
set pitch_expo = 30
set yaw_expo = 30

# rateprofile
rateprofile 2

set roll_rc_rate = 60
set pitch_rc_rate = 60
set yaw_rc_rate = 60
set roll_expo = 30
set pitch_expo = 30
set yaw_expo = 30

# rateprofile
rateprofile 3


# rateprofile
rateprofile 4


# rateprofile
rateprofile 5


# restore original rateprofile selection
rateprofile 0

# save configuration
save

---

and yes on the 915

You hardly have any customisation applied in Betaflight 3.5.7 and the ones you do are mostly transferrable. So flash Betaflight 4.2.3 to your FC with the "Full chip erase" option switched on, then connect and select "Apply Custom Defaults", then calibrate the Accelerometer. then go to the CLI tab and copy/paste the following block of commands into the text box and press <ENTER>.

ok but like I said ive never done a flash before and im sure I cant just google how to flash a mamba f405 fc

Look on YouTube for Joshua Bardwell betaflight setup. He explains what to do to flash the FC

ok done now a test flight right?

(17-Oct-2020, 07:51 PM)joey Wrote: ok done now a test flight right?

Yep, that sounds like the next logical step

think there is a chance of that fixing my range issue ?