problems with SPI FR

[ALFJAVIVI]

Describe the bug

With RC4, RC5 and RC6 RC problems with Spi Fr.
Rxloxx in Rc4 and RC5 at distances of 10 to 15m and with RC6 the distance is about 25m for an hour with which the RC works best is in RC3.
The FC is a crazybeex FR versions v1 and v2

To Reproduce

that the rc signal is coo in 4.3 Rc3

Expected behavior

that the range of the RC signal is coo Rc3

Flight controller configuration

  # REPLACE THIS LINE BY THE OUTPUT OF YOUR `diff`

  # REPLACE THIS LINE BY THE OUTPUT OF YOUR `resource show all`

Flight controller

crazybeex FR

Other components

No response

How are the different components wired up

No response

Add any other context about the problem that you think might be relevant here

No response

[daleckystepan]

Can you please send us log with RC6 firmware, debug mode set to rx_timing? (if you have openlager or similar device)

Please send also at least output of diff command.

PRs that are related:

• Frsky range check issues #11536

I did tests with CrazybeeF4FR and TX16S MPM. FrskyX2 LBT and I have no issues.
I also tried low power mode and put my quad inside a pot. Nothing unusual. I need to put my quad into pot, set TX16S in low power mode and move to different room under shielding to get RX loss. RSSI in Configurator around 30 %.

It still works OK with RSSI around 40 % in BF and 50dB on TX16s. Missing packets but still no failsafe.

[ALFJAVIVI]

Good morning this fc crazybeex FR does not have a black box El mar., 26 abr. 2022 18:26, Štěpán Dalecký ***@***.***> escribió:

…

Can you please send us log with RC6 firmware, debug mode set to rx_timing? — Reply to this email directly, view it on GitHub <#11560 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AY4YCQI2GXKBA6LBXOMUAGTVHAKLFANCNFSM5UMBVYOQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[bike797]

my quad(SPI FR) is the same. Short range with rc 4 5 6.

[daleckystepan]

Can you please paste your diff?

[bike797]

diff

# 

# diff all

# version
# Betaflight / STM32F411 (S411) 4.3.0 Apr 25 2022 / 01:03:20 (9d71184) MSP API: 1.44
# config: manufacturer_id: HAMO, board_name: CRAZYBEEF4FR, version: a074838b, date: 2021-06-14T21:36:54Z

# start the command batch
batch start

# reset configuration to default settings
defaults nosave

board_name CRAZYBEEF4FR
manufacturer_id HAMO
mcu_id 004500683339510839363632
signature 

# name: Mobula6

# feature
feature -RX_PARALLEL_PWM
feature -AIRMODE
feature MOTOR_STOP
feature TELEMETRY

# serial
serial 1 2048 115200 57600 0 115200

# map
map TAER1234

# aux
aux 0 0 0 1700 2100 0 0
aux 1 1 1 900 1300 0 0
aux 2 2 1 1300 1700 0 0
aux 3 13 2 1700 2100 0 0
aux 4 28 1 1300 2100 0 0
aux 5 35 2 1300 2100 0 0
aux 6 35 3 1300 2100 0 0

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

# master
set gyro_lpf1_static_hz = 350
set gyro_lpf2_static_hz = 700
set dyn_notch_count = 1
set dyn_notch_q = 500
set gyro_lpf1_dyn_min_hz = 350
set gyro_lpf1_dyn_max_hz = 700
set acc_calibration = 39,-76,-197,1
set mag_hardware = NONE
set baro_hardware = NONE
set fpv_mix_degrees = 35
set blackbox_device = NONE
set dshot_bidir = ON
set motor_pwm_protocol = DSHOT300
set motor_poles = 12
set failsafe_delay = 4
set failsafe_recovery_delay = 20
set ibata_scale = 1175
set yaw_motors_reversed = ON
set small_angle = 180
set simplified_gyro_filter_multiplier = 140
set report_cell_voltage = ON
set osd_warn_batt_not_full = OFF
set osd_warn_batt_warning = OFF
set osd_warn_esc_fail = OFF
set osd_warn_core_temp = OFF
set osd_rssi_alarm = 30
set osd_rssi_dbm_alarm = -95
set osd_cap_alarm = 100
set osd_vbat_pos = 2456
set osd_rssi_pos = 2145
set osd_link_quality_pos = 161
set osd_rssi_dbm_pos = 128
set osd_tim_1_pos = 33
set osd_tim_2_pos = 2081
set osd_flymode_pos = 2401
set osd_throttle_pos = 2361
set osd_vtx_channel_pos = 2099
set osd_current_pos = 2423
set osd_mah_drawn_pos = 2392
set osd_craft_name_pos = 2433
set osd_debug_pos = 65
set osd_pidrate_profile_pos = 2330
set osd_warnings_pos = 14441
set osd_avg_cell_voltage_pos = 408
set osd_battery_usage_pos = 65
set osd_disarmed_pos = 2442
set osd_esc_tmp_pos = 2093
set osd_esc_rpm_pos = 257
set osd_rtc_date_time_pos = 73
set osd_flip_arrow_pos = 2349
set osd_core_temp_pos = 2088
set osd_stat_rtc_date_time = ON
set osd_stat_tim_1 = ON
set osd_stat_max_spd = OFF
set osd_stat_endbatt = ON
set osd_stat_battery = ON
set osd_stat_bbox = OFF
set osd_stat_bb_no = OFF
set osd_stat_max_g_force = ON
set debug_mode = FFT
set cpu_overclock = 120MHZ
set vtx_band = 5
set vtx_channel = 7
set vtx_power = 2
set vtx_low_power_disarm = ON
set vtx_freq = 5880
set vcd_video_system = NTSC
set frsky_spi_tx_id = 35,43,2
set frsky_spi_offset = -17
set frsky_spi_bind_hop_data = 0,43,86,129,172,215,23,66,109,152,195,3,46,89,132,175,218,26,69,112,155,198,6,49,92,135,178,221,29,72,115,158,201,9,52,95,138,181,224,32,75,118,161,204,12,55,98,0,0,0
set gyro_1_align_yaw = 900
set name = Mobula6

profile 0

# profile 0
set dterm_lpf1_dyn_min_hz = 105
set dterm_lpf1_dyn_max_hz = 210
set dterm_lpf1_static_hz = 105
set dterm_lpf2_static_hz = 210
set anti_gravity_gain = 5000
set iterm_relax = RPY
set pidsum_limit = 1000
set p_pitch = 94
set i_pitch = 5
set d_pitch = 48
set f_pitch = 250
set p_roll = 90
set i_roll = 160
set d_roll = 80
set f_roll = 240
set p_yaw = 43
set i_yaw = 94
set f_yaw = 240
set angle_level_strength = 0
set horizon_level_strength = 0
set horizon_transition = 0
set d_min_roll = 60
set d_min_pitch = 0
set dyn_idle_min_rpm = 70
set simplified_master_multiplier = 200
set simplified_dterm_filter_multiplier = 140

profile 1

profile 2

# restore original profile selection
profile 0

rateprofile 0

# rateprofile 0
set roll_rc_rate = 15
set pitch_rc_rate = 15
set yaw_rc_rate = 15
set yaw_srate = 75
set roll_level_expo = 5
set pitch_level_expo = 5

rateprofile 1

rateprofile 2

rateprofile 3

rateprofile 4

rateprofile 5

# restore original rateprofile selection
rateprofile 0

# save configuration
save
# 

[mitcht]

This is "me too", but I can say I've just compiled a hex using master with target CrazyBeeF4FR and as of the date of this post. I can confirm dropout at 10m when using Frsky D 8 (Moblite7). Dropout occurs around 50, drops to 0. I've tried overcloxk, normal clock, dshot_bitbang = true, less filters, attempt to lower cpu usage, tried forcing FrskyX (no luck) and just about every combination of things you could think of. No luck. Was fine on 4.2. I'll be available to build specific branches if needed. No need to compile a hex for me. I can also help code, if you can help me dial into the correct place to make adjustments! That sounds silly but I'm not super familiar with the structure of the project yet.

[daleckystepan]

Thank you for data. I will retest with your settings.

[daleckystepan]

Look at debug[0] peaks. Each peak means connection issue. It is nearly unusable on D8. No low power mode and distance between quad and TX around 2-3 m. Fine tuning done on my TX16S.

[Professor77]

I have the same issue with my Hamo Crazybeef4fr
Radio is frsky x-lite on D8. Have not tried it with Frsky X or LBT.

[daleckystepan]

Please retest with X2 mode. It is still not ideal but it seems to be better. At least X2 has significantly less frame loss during my tests.

[joeyw007]

This is an odd duck of an issue. I had failsafe, not range issues with the following boards after fresh installing RC4 or RC5. The CrazybeeX FR v2.2, CrazybeeX FR v1.0, Crazybee F4 Lite, CrazyF411, CrazyF411 Pro, Nanohawk, Nanohawk X, Tinyhawk II FS, Tinyhawk II Race and Tinyhawk III boards. PR 11536 was hammered out, tested and merged which fixed the failsafe issue but apparently there is still some sort of issue although I am not experiencing it nor loss of range. In fact D8 has never worked better after merging PR 11536 with master for RC6 release. Also everything was fine and functional in RC3 as well as 4.2.11. Quite a contradiction. I am using a T12 Pro Hall running OpenTX 2.3.14. All tests, range testing and flight testing, were done with factory reset radio with new model that was frequency tuned. The quads were freshly configured, no diffs or dumps carried from one RC to the next. Configurations were left as default as possible obviously some settings need to be changed to get into the air but only personalization and VTX settings. As of the last several days I've been flying RC6 on all these boards quite frequently with no issues at all. It appears there is a sort of anomaly causing issue.

[ALFJAVIVI]

So I understand that from RC6 to D8 the RC problems have been solved? At the moment I am going in RC3 and D16 and for the moment everything is fine to one that I do notice that the RSSI of the betaflight OSD is not very stable since it goes up and down very fast to a point where I have not had any RXLOXX moving away more than 100 meters has never dropped the RSSI below 35. El lun., 2 may. 2022 15:02, Joey Whitaker ***@***.***> escribió:

…

This is an odd duck of an issue. I had failsafe, not range issues with the following boards after fresh installing RC3, RC4 or RC5. The CrazybeeX FR v2.2, CrazybeeX FR v1.0, Crazybee F4 Lite, CrazyF411, CrazyF411 Pro, Nanohawk, Nanohawk X, Tinyhawk II FS, Tinyhawk II Race and Tinyhawk III boards. PR 11536 was hammered out, tested and merged which fixed the failsafe issue but apparently there is still some sort of issue although I am not experiencing it nor loss of range. In fact D8 has never worked better after merging PR 11536 with master for RC6 release. Also everything was fine and functional in RC3 as well as 4.2.11. Quite a contradiction. I am using a T12 Pro Hall running OpenTX 2.3.14. All tests, range testing and flight testing, were done with factory reset radio with new model that was frequency tuned. The quads were freshly configured, no diffs or dumps carried from one RC to the next. Configurations were left as default as possible obviously some settings need to be changed to get into the air but only personalization and VTX settings. As of the last several days I've been flying RC6 on all these boards quite frequently with no issues at all. It appears there is a sort of anomaly causing issue. — Reply to this email directly, view it on GitHub <#11560 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AY4YCQP26OQNUMJ6LWJPY4LVH7G77ANCNFSM5UMBVYOQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[joeyw007]

I ran debug mode on RX_TIMING and got this but I'm not having any issues at all. Kinda weird, yeah. Thought some info from someone with fully normal functioning D8 on RC6 might be helpful. RX distance measured 3 meters.

.