New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

spi rx twitch while flying in d16 mode #5576

Closed
turboed13b opened this Issue Mar 30, 2018 · 135 comments

Comments

Projects
None yet
@turboed13b

turboed13b commented Mar 30, 2018

Crazybee flight controller with spi-rx. D16 mode causes twitching while flying. Dshot600 mode causes failsafe while in d16 mode.

D8 mode works fine in multishot but in dshot600 it arms then immediately disarms with a telemetry lost from tx.

@mikeller

This comment has been minimized.

Member

mikeller commented Mar 30, 2018

This sounds a lot like CPU overload. What loop frequencies are you using? Have you tried reducing them? A diff would help, just like it says in the text you get when opening an issue.

@turboed13b

This comment has been minimized.

turboed13b commented Mar 30, 2018

I have tried 4k/4k. Previously on 3.3 then flashed 3.4 to see if it fixed it with no luck. The twitch only happens in d16 mode almost feels like a failsafe but quickly comes back. Dshot makes the twitch worse and occasionally fully failsafes and I have to unplug the quad to get it to fly again.

# Betaflight / CRAZYBEEF3FR (CBFR) 3.4.0 Mar 27 2018 / 19:22:44 (7ad4bbfa0) MSP API: 1.39
name BLACKHORSE
resource MOTOR 1 B09
resource MOTOR 2 B08
resource MOTOR 3 A02
resource MOTOR 4 A03

feature -TELEMETRY
feature DYNAMIC_FILTER
map TAER1234
aux 0 0 0 1700 2100 0
aux 1 1 1 900 1300 0
aux 2 28 1 1700 2100 0
aux 3 30 0 1700 2100 0
aux 4 35 2 1700 2100 0
set align_gyro = CW270FLIP
set gyro_sync_denom = 2
set gyro_notch1_hz = 0
set gyro_notch2_hz = 0
set align_acc = CW270FLIP
set acc_trim_pitch = 4
set acc_calibration = -29,-75,114
set min_check = 1010
set rssi_channel = 8
set fpv_mix_degrees = 10
set rx_min_usec = 850
set rx_max_usec = 2150
set rx_spi_protocol = FRSKY_D
set motor_pwm_protocol = MULTISHOT
set bat_capacity = 250
set vbat_max_cell_voltage = 44
set vbat_min_cell_voltage = 29
set vbat_warning_cell_voltage = 32
set yaw_motors_reversed = ON
set pid_process_denom = 1
set osd_warnings = 63
set osd_cap_alarm = 250
set osd_vbat_pos = 2455
set osd_rssi_pos = 2433
set osd_craft_name_pos = 2442
set osd_warnings_pos = 329
set frsky_spi_tx_id = 32,14
set frsky_spi_offset = -26
set frsky_spi_bind_hop_data = 1,146,56,201,111,21,166,76,223,131,41,186,96,6,151,61,206,116,26,171,81,226,136,48,191,101,11,156,66,211,121,31,178,86,231,141,51,196,106,16,161,71,216,126,36,181,93,0,0,0
set frsky_x_rx_num = 1
profile 0

set dterm_lowpass_type = PT1
set dterm_setpoint_weight = 200
set p_pitch = 70
set i_pitch = 75
set p_roll = 65
set i_roll = 70
set p_yaw = 90
set i_yaw = 70
set p_level = 70
rateprofile 0

set roll_rc_rate = 114
set pitch_rc_rate = 114
set yaw_rc_rate = 108
set roll_srate = 71
set pitch_srate = 71
set yaw_srate = 60

# 
@mikeller

This comment has been minimized.

Member

mikeller commented Mar 30, 2018

Try lowering your loop timings to 4k/2k to see if this improves things. Since the RX stack is run on the flight controller MCU, it will require some of the processing power, and it's sensitive to CPU overload. FrSky X (D16) is a lot more complex in terms of telemetry, which causes it to use more CPU cycles than FrSky D (D8).

@turboed13b

This comment has been minimized.

turboed13b commented Mar 31, 2018

OK I tried 4k/2k and 2k/2k and it is not working still.

@mikeller

This comment has been minimized.

Member

mikeller commented Mar 31, 2018

Thanks for testing. Sounds like a resource issue. Can you please post the output of a resource list and a dma list?

@turboed13b

This comment has been minimized.

turboed13b commented Mar 31, 2018

resource BEEPER 1 C15
resource MOTOR 1 B09
resource MOTOR 2 B08
resource MOTOR 3 A02
resource MOTOR 4 A03
resource SERIAL_TX 3 B10
resource SERIAL_RX 3 B11
resource LED 1 B03
resource RX_BIND_PLUG 1 A09
resource SPI_SCK 1 A05
resource SPI_SCK 2 B13
resource SPI_MISO 1 A06
resource SPI_MISO 2 B14
resource SPI_MOSI 1 A07
resource SPI_MOSI 2 B15
resource ADC_BATT 1 A00
resource ADC_CURR 1 A01

# dma

DMA:
DMA1 Channel 1: ADC
DMA1 Channel 2: FREE
DMA1 Channel 3: FREE
DMA1 Channel 4: FREE
DMA1 Channel 5: FREE
DMA1 Channel 6: FREE
DMA1 Channel 7: FREE
DMA2 Channel 1: FREE
DMA2 Channel 2: FREE
DMA2 Channel 3: FREE
DMA2 Channel 4: FREE
DMA2 Channel 5: FREE
@turboed13b

This comment has been minimized.

turboed13b commented Mar 31, 2018

IO
A00: ADC_BATT
A01: ADC_CURR
A02: MOTOR 3
A03: MOTOR 4
A04: MPU_CS
A05: SPI_SCK 1
A06: SPI_MISO 1
A07: SPI_MOSI 1
A08: RX_SPI
A09: RX_BIND
A10: LED
A11: FREE
A12: FREE
A13: FREE
A14: FREE
A15: FREE
B00: FREE
B01: OSD_CS
B02: FREE
B03: LED 1
B04: FREE
B05: FREE
B06: FREE
B07: FREE
B08: MOTOR 2
B09: MOTOR 1
B10: FREE
B11: FREE
B12: RX_SPI_CS 2
B13: SPI_SCK 2
B14: SPI_MISO 2
B15: SPI_MOSI 2
C13: MPU_EXTI
C14: FREE
C15: BEEPER
F00: FREE
F01: FREE
F04: FREE

# dma list

DMA:
DMA1 Channel 1: ADC
DMA1 Channel 2: FREE
DMA1 Channel 3: FREE
DMA1 Channel 4: FREE
DMA1 Channel 5: FREE
DMA1 Channel 6: FREE
DMA1 Channel 7: FREE
DMA2 Channel 1: FREE
DMA2 Channel 2: FREE
DMA2 Channel 3: FREE
DMA2 Channel 4: FREE
DMA2 Channel 5: FREE
@mikeller

This comment has been minimized.

Member

mikeller commented Mar 31, 2018

That looks like it was done when Dshot was not enabled (because it's not using any DMA for Dshot). Can you do it again please, with Dshot enabled?

@turboed13b

This comment has been minimized.

turboed13b commented Mar 31, 2018

IO
A00: ADC_BATT
A01: ADC_CURR
A02: MOTOR 3
A03: MOTOR 4
A04: MPU_CS
A05: SPI_SCK 1
A06: SPI_MISO 1
A07: SPI_MOSI 1
A08: RX_SPI
A09: RX_BIND
A10: LED
A11: FREE
A12: FREE
A13: FREE
A14: FREE
A15: FREE
B00: FREE
B01: OSD_CS
B02: FREE
B03: LED 1
B04: FREE
B05: FREE
B06: FREE
B07: FREE
B08: MOTOR 2
B09: MOTOR 1
B10: FREE
B11: FREE
B12: RX_SPI_CS 2
B13: SPI_SCK 2
B14: SPI_MISO 2
B15: SPI_MOSI 2
C13: MPU_EXTI
C14: FREE
C15: BEEPER
F00: FREE
F01: FREE
F04: FREE

# Dma list

DMA:
DMA1 Channel 1: ADC
DMA1 Channel 2: FREE
DMA1 Channel 3: FREE
DMA1 Channel 4: FREE
DMA1 Channel 5: MOTOR 3
DMA1 Channel 6: FREE
DMA1 Channel 7: MOTOR 4
DMA2 Channel 1: MOTOR 1
DMA2 Channel 2: FREE
DMA2 Channel 3: FREE
DMA2 Channel 4: FREE
DMA2 Channel 5: MOTOR 2
@mikeller

This comment has been minimized.

Member

mikeller commented Mar 31, 2018

Ok, I suspect there is a resource conflict between the DMA that is used for the SPI RX and the DMA used for motor 3.
I have reshuffled the DMA for Dshot and squeezed into 2 DMAR channels: #5590.

@turboed13b: Can you please try this:
betaflight_3.4.0_CRAZYBEEF3FR.zip (requires a full chip erase / restore for all settings to take)

@turboed13b

This comment has been minimized.

turboed13b commented Mar 31, 2018

That fixed dshot in d8 mode it flies now.

Second problem with dshot in d16 mode and failsafe/twitches are still present. When it failsafes I can't rearm.

I did remap my motors so 1/2 are switched and 3/4 switched. I don't know if that was what is causing the problem with d8 mode.

@turboed13b

This comment has been minimized.

turboed13b commented Mar 31, 2018

I tested multishot in d16 and the twitches are still there also.

@turboed13b

This comment has been minimized.

turboed13b commented Mar 31, 2018

Alright so I found the root of the problem for d8 mode and dshot. That new hex file did not fix it after I setup all my modes.

When I setup flip over after crash in the modes tab it does the arm and disarm problem. The mode doesn't have to be yellow either. Simply setting up the mode causes the problem.

@mikeller

This comment has been minimized.

Member

mikeller commented Mar 31, 2018

Ha. That means that the firmware on the on board ESCs is too old, and can not handle the 'normal' / 'reversed' commands that are sent on arming when crash flip is enabled. Try updating the ESC firmware to 16.67 or 16.7 first, then try again.

(Also, if the hex file I sent you works this will be an improvement anyway, as it optimises the resource usage.)

@turboed13b

This comment has been minimized.

turboed13b commented Mar 31, 2018

I am on 16.7

@mikeller

This comment has been minimized.

Member

mikeller commented Mar 31, 2018

Ok. This is weird then. There is no difference between crash flip being disabled and enabled, except for the commands that are sent when arming, and 16.7 can handle these.

Have you tried Dshot300? (Just taking pot shots here, but there are some ESCs with slow MCU that can't handle Dshot600.)

@turboed13b

This comment has been minimized.

turboed13b commented Mar 31, 2018

Just tried dshot300 and it didn't work. Messed with lower loop times also. This is in d8 mode.

It does work in d16 mode and flip over crash works also but it has the twitch and failsafe issue. I think it has something to do with the rx. I get telemetry lost and telemetry recovered as soon as i hit the arm switch.

@mikeller

This comment has been minimized.

Member

mikeller commented Mar 31, 2018

I am a bit puzzled here. Both FrSky D and FrSky X were tested on another F3 board design, with Dshot, and confirmed to work fine there. This looks like this is an issue inherent to this board's design. Maybe @githubDLG can provide us with a known good configuration for this board?

@turboed13b

This comment has been minimized.

turboed13b commented Mar 31, 2018

I tried pretty much every setting. I ordered a couple more boards to see if this one is just faulty.

@githubDLG

This comment has been minimized.

Contributor

githubDLG commented Apr 4, 2018

hi, guys~~ @mikeller @turboed13b @brycedjohnson
i am here now , sorry for being late. 😜
Crazybee flight controller with spi-rx. D16 mode causes twitching while flying. Dshot600 mode causes failsafe while in d16 mode.
D8 mode works fine in multishot but in dshot600 it arms then immediately disarms with a telemetry lost from tx.

Yes,yes~~ Actually, we have already know twitch and d8/d16 arm/disarm issue, and Flysky SPI rx seems also suffered twitch issue... We have disscued this problems in slack. 😂

And , don't be worrid about them , i think our BF devs will fix it soon ~~😂

@githubDLG

This comment has been minimized.

Contributor

githubDLG commented Apr 4, 2018

And , @turboed13b
I tried pretty much every setting. I ordered a couple more boards to see if this one is just faulty.
Do not do that, i'm seriously~~~ 😂
I strongly recommand you that, fly with D8 first, and wait for D16 to be fixed 😂

@brycedjohnson

This comment has been minimized.

Contributor

brycedjohnson commented Apr 4, 2018

@turboed13b are you in Europe the EU lbt firmware on your taranis? I don't think that is supported on this board yet. D8 would work in that case.

Also dshot 600 isn't recommended with the L esc firm firmware although I know you already tired that.

I have been getting a few random failsafes but I haven't tracked it down. Might be a FC lockup because my time stops incrementing on the OSD.

Also it might be getting swamped if you are less then 1m away. I can see that issue when I hold the taranis next to the board.

Just brainstorming, could packet loss be causing the twitch? How did the spi-rx deal with a bad packet?

I'll upload my config to see if there are any differences later.

@turboed13b

This comment has been minimized.

turboed13b commented Apr 4, 2018

I am in the U.S. D16 mode works but it is pretty much impossible to fly with the twitching and failsafes.

I am flying d8 mode in dshot600 right now without any problems. I just can't enable dshot motor reversal it won't arm.

@brycedjohnson

This comment has been minimized.

Contributor

brycedjohnson commented Apr 4, 2018


# diff all
# Betaflight / CRAZYBEEF3FR (CBFR) 3.4.0 Mar 31 2018 / 18:16:36 (14d1c52cf) MSP API: 1.39
defaults nosave
name Bryce[\]^_

feature AIRMODE
aux 0 0 0 1200 2100 0
aux 1 1 2 1200 2100 0
aux 2 13 1 1700 2100 0
aux 3 35 1 1300 1700 0
aux 4 36 3 1700 2100 0
set gyro_sync_denom = 2
set gyro_notch1_hz = 0
set gyro_notch1_cutoff = 0
set gyro_notch2_hz = 0
set gyro_notch2_cutoff = 0
set acc_calibration = -37,-89,50
set min_check = 1010
set max_check = 1990
set dshot_idle_value = 900
set motor_pwm_protocol = DSHOT300
set bat_capacity = 260
set vbat_max_cell_voltage = 45
set vbat_min_cell_voltage = 28
set vbat_warning_cell_voltage = 29
set vbat_scale = 113
set beeper_dshot_beacon_tone = 4
set yaw_motors_reversed = ON
set small_angle = 180
set pid_process_denom = 1
set osd_warnings = 63
set osd_vbat_pos = 385
set osd_rssi_pos = 40
set osd_tim_1_pos = 54
set osd_tim_2_pos = 2455
set osd_flymode_pos = 333
set osd_throttle_pos = 225
set osd_vtx_channel_pos = 352
set osd_current_pos = 2400
set osd_mah_drawn_pos = 353
set osd_craft_name_pos = 2441
set osd_gps_speed_pos = 218
set osd_gps_lon_pos = 82
set osd_gps_lat_pos = 65
set osd_gps_sats_pos = 51
set osd_home_dir_pos = 302
set osd_home_dist_pos = 303
set osd_compass_bar_pos = 266
set osd_altitude_pos = 247
set osd_pid_roll_pos = 423
set osd_pid_pitch_pos = 455
set osd_pid_yaw_pos = 487
set osd_debug_pos = 1
set osd_power_pos = 321
set osd_pidrate_profile_pos = 345
set osd_warnings_pos = 2056
set osd_avg_cell_voltage_pos = 2433
set osd_pit_ang_pos = 257
set osd_rol_ang_pos = 289
set osd_battery_usage_pos = 465
set osd_disarmed_pos = 138
set osd_nheading_pos = 311
set osd_nvario_pos = 279
set osd_esc_tmp_pos = 82
set osd_esc_rpm_pos = 472
set osd_rtc_date_time_pos = 2048
set osd_stat_max_spd = OFF
set osd_stat_endbatt = ON
set osd_stat_bb_no = OFF
set osd_stat_rtc_date_time = ON
set vcd_video_system = 2
set frsky_spi_tx_id = 72,197
set frsky_spi_offset = -18
set frsky_spi_bind_hop_data = 6,219,199,179,159,139,119,99,79,59,39,19,234,214,194,174,154,136,114,94,74,54,34,14,229,209,189,169,149,129,109,89,69,49,29,9,224,204,184,164,144,124,104,84,64,44,24,0,0,0
set frsky_x_rx_num = 5
profile 0

set crashflip_motor_percent = 50
set dterm_setpoint_weight = 254
set p_pitch = 80
set p_roll = 80
set i_roll = 50
set d_roll = 35
set p_yaw = 80
set p_level = 120
set level_limit = 60

profile 0
rateprofile 0

set roll_expo = 20
set pitch_expo = 20
set yaw_expo = 20
set roll_srate = 80
set pitch_srate = 80
set yaw_srate = 80
rateprofile 1

rateprofile 2

rateprofile 3

rateprofile 4

rateprofile 5

rateprofile 0
save
# ```
@brycedjohnson

This comment has been minimized.

Contributor

brycedjohnson commented Apr 4, 2018

https://youtu.be/O5LdPWjdUuM

I had a failsafe - maybe a FC lockup at ~3:55. Notice that the RTC stops incrementing and the current and voltage readings stay the same. I also can't rearm or do anything until I poweroff.

@turboed13b

This comment has been minimized.

turboed13b commented Apr 13, 2018

Let me know if you guys get it figured out.

@githubDLG

This comment has been minimized.

Contributor

githubDLG commented Apr 13, 2018

Okay~~

@evnngsky

This comment has been minimized.

evnngsky commented Apr 18, 2018

Moreover, I found motor run without arm in my case(D16, DSHOT600). It should hurt me!!!!!

@matthew-sutterlin

This comment has been minimized.

matthew-sutterlin commented May 9, 2018

Hello fellow programmers, are there any more recent hex's or are the ones from last week the ones i should try?? im curious if the 3.4 hex's mateksys is posting on their site are from this thread.

@slekkas

This comment has been minimized.

slekkas commented May 9, 2018

@matthew-sutterlin

It seems like no one is bothering with this any more. Most people I know who were unlucky enough to get the Matek F411-One have stopped using it and Banggood won't give refunds as you can't really prove there's a problem.

Have you had any luck with the hex files you've tried so far?

@Rennkopter

This comment has been minimized.

Rennkopter commented May 9, 2018

Be patient. As already mentioned before, they working on it. I want to fly this great FC also in its full function!
When something great falls out of the sky, it always hits face first....

@brycedjohnson

This comment has been minimized.

Contributor

brycedjohnson commented May 9, 2018

@slekkas Did d8 with Dshot not work for you with turtle and beeper with a recent hex? No reason it shouldn't.

If you aren't willing to debug and test stuff how it isn't helpful to have you commenting in this thread spreading inaccurate information.

I have 2 matek-F411-one, one of which is in a quad flying great with D8, turtle, beeper, dshot 600. And 2 The other is at my desk to debug. Also have 2 crazybee F3 boards, on that I'm flying almost everyday. Realize everyone here is working to fix this in their free time.

@matthew-sutterlin I would grab the hexes from here these are what I have been flying. #5576 (comment). Fly it in D8 mode for now unless you want to help debug. Thanks!

@mikeller

This comment has been minimized.

Member

mikeller commented May 9, 2018

@slekkas: Please be understanding that all of us here are doing this only in their spare time, and this means that progress can some time be held up by people having other commitments. @brycedjohnson is working on #5707, which should fix FrSky D, including crash flip mode. There is more work needed to track down the problems with FrSky X, but @brycedjohnson has got that under way as well in #5741.

@slekkas

This comment has been minimized.

slekkas commented May 9, 2018

@brycedjohnson
@mikeller

Gentleman I didn't say anything inaccurate. The fact is that it's not working as it's supposed to be. I'm currently in Europe and using D8 is illegal. I'm in the computer industry as well and I understand these things are not easy to debug. But I do hope and wish this will be fixed soon so I can enjoy the quad I built in its full potential. That said I'm not demanding anything.

Regarding me helping I tried enabling the Blackbox but unfortunately it seems the Matek F411-One doesn't have one or I don't know how to enable it.

@brycedjohnson

This comment has been minimized.

Contributor

brycedjohnson commented May 9, 2018

@slekkas You said "It seems like no one is bothering with this any more" And implied that turtle and the beeper weren't working on the the recent hexes. I have been looking at this and turtle mode and beeper are working on the recent hexes.

Right you you are just muddying up a debug thread and taking time that could have gone toward fixing the bug.

The hex above betaflight_3.4.0_MATEKF411RX_combo_nosport.hex.zip should work for D16 without lockups by disabling some smartport stuff in the code, but completely at your own risk. I don't really have time to support debugging by people unless they have a little more experience for now.

Without flying an easy way to test is just plug in the USB and turn on the taranis. If you haven't lost telemetry after 10 minutes then it probably won't lock up in flight on you.

@Rennkopter

This comment has been minimized.

Rennkopter commented May 9, 2018

@slekkas just thinks you are the manufacturer. ...mateksys.com points to that github discussion.

@matthew-sutterlin

This comment has been minimized.

matthew-sutterlin commented May 10, 2018

@brycedjohnson thanks for the effort, its appreciated!

@Rennkopter Yea same here, i found this github issue as its now on the front page on almost every store (manufacturer included) that sells the mateksys f411-one. I shall test the most recent hexes hopefully tonight at latest tomorrow with blackbox and report back my findings as well if that would be helpful

@maxxb1

This comment has been minimized.

maxxb1 commented May 13, 2018

I just have read this whole issue, and I had the same issues as the others today with the old 3.3 version. I already installed the new 3.4 to test in the next days. But how do I enable the right debug mode?
if I type in CLI: "set debug_mode=" there are a lot of options. What do i need to set that it helps you guys to figure out the problems?
cheers

Edit: flew about 10 packs with the new firmware without any failsafes anymore. But unfortunately turtle mode doesn’t work at all?! Blheli 16.7 is installed and turtle mode worked with the old fc. 🤔

@jasonchi38

This comment has been minimized.

jasonchi38 commented May 15, 2018

Same issues here, hoping to see a fix soon. Might have to return the FC for F405CTR instead.

@marz71

This comment has been minimized.

marz71 commented May 24, 2018

Hi guys! I would like to add that I also have similar problems described here. Betaflight / MATEKF411RX (M41R) 3.3.2 May 4, ESC 1-4 A-H-15, 16.7, Dshot600, taranis 9xd. Low rssi values, glitches now and then, sudden failsafe activation(?), telemetry comes and goes.

First flight with the quad.
https://www.youtube.com/watch?v=OrTsfR19z1g&feature=youtu.be
Forward to 2:35. Trying to hoover and keeping it steady. The sudden full throttle wasn't me.

So switching to D8 and using multishot will solve problems for now?

@maxxb1

This comment has been minimized.

maxxb1 commented May 24, 2018

I’m using D8 with dshot 600 with the new firmware from above with no problems anymore. Flew up to 800m straight out with still 40% rssi.(with xjt Module in tg9x)

And I also set up debug mode for rx signal. Not a single package lost on any of my latest flights.

@slekkas

This comment has been minimized.

slekkas commented May 24, 2018

@maxxb1

I'm using the same but I still can't use nice features like turtle mode and esc buzzer.

Are you using them?

@maxxb1

This comment has been minimized.

maxxb1 commented May 24, 2018

@slekkas
I have normal buzzer, so no problem there but turtle mode also don’t work for me 🤷🏼‍♂️

@slekkas

This comment has been minimized.

slekkas commented May 24, 2018

@maxxb1

I also resulted to normal buzzer but why install extra parts and do extra soldering when we bought a premium product to be able to use all its features?

The developers here do their best to help but Matek should have replaced the fc's. Banggood won't give me a refund as there can be no actual picture of the problem and Matek won't even answer my emails asking them to send me a F405-CTR or something that actually works.

@waumand

This comment has been minimized.

waumand commented May 24, 2018

@brycedjohnson hi ! I'm using the Snapper7, with CrazyBeeF3FR, and your hex (15 days ago) is very good ! All working well in D8 (turtle, deeper star wars, D600, etc). Some "trouble" sometimes to arm (motors don't want to spin so disarm and arm again, but just 5 secs max of trouble, after it's fine !

I see that you modify again your folk, is there any change interesting for me ? If yes, do you have a new/better build ?

Another question : what about ButterFlight, is these bugs exist there ? No fix for them ? I'm looking at ButterFlight in the futur, but now Betaflight it's ok for me =)

@slekkas

This comment has been minimized.

slekkas commented May 25, 2018

So maybe with the latest update on D8 it works better but I still get the random failsafes now and then.

https://youtu.be/fKPoK9LpMLk

@brycedjohnson

This comment has been minimized.

Contributor

brycedjohnson commented May 25, 2018

@slekkas What was your RSSI doing? Antennas is good shape? I haven't had any D8 failsafe issues on my Matek411rx board or crazybee F3. If you had DVR that is probably more helpful HD footage. From the HD you can't really narrow down the cause. Also ESC buzzer and turtle are working unlike what you mentioned above.

@waumand Butterflight doesn't have fixes for any of these issues. On my fork I was rebasing my changes to master, but there weren't any improvements.

@marz71 You'll have to grab the latest hexes from this thread until the changes get pulled in.

Everyone else,
I spent some time trying to figure out D16 smartport telemetry issue (the last remaining issue), but don't have any progress...

@githubDLG

This comment has been minimized.

Contributor

githubDLG commented May 26, 2018

@brycedjohnson Then thanks for your awsome work!!!!

@mikeller mikeller added this to the Betaflight v3.4 milestone May 26, 2018

@marz71

This comment has been minimized.

marz71 commented May 28, 2018

I have tried the betaflight_3.4.0_MATEKF411RX_combo_nosport.hex.zip. I switched to D8 and I can for sure see some difference. My telemetry is not so much on/off anymore. Unfortunately I discovered problem with one of the motors and could not fly. I'm waiting for new motors before I can test more.
But I noticed still low RSSI values. I walked away about 50 meters and the there was a pile of earth between me and the drone. Nothing heavy, some vegetations too. I received warnings about week signals on my radio.
Is this an issue that is been worked on? Please let us know if we can help with anything.

@adronfpv

This comment has been minimized.

adronfpv commented May 28, 2018

@marz71 I have also tried that hex with D8. No twitches and no failsafes at close distances. I also get very low rssi values during flighy but I have not tried it's range. At least this hex is better than with the old hex.

Most of the times I have flown with this hex and then land and disarm I see in the OSD that mi lowest rssi was 30 or lower but I didn't get failsafe so maybe the rssi values are not well calibrated and so it can fly longer distances but I don't really know.

@markusbrand

This comment has been minimized.

markusbrand commented May 28, 2018

@brycedjohnson - just to confirm. Since switching to D8 - I don't get failsafes anymore. Run already about 20 packs, without twiches and other receiver related issues. Range is the same like typical XSR receiver (maybe a little more jumps in the RSSI values - but not sure). Also Motor-Beeper is working with your hex-file provided above. Thanks for your effort, but still waiting for a final version with D16 fixed.

@slekkas

This comment has been minimized.

slekkas commented May 28, 2018

@markusbrand

Which board are you using? Maybe depending on the board there's different issues.

It was exactly the same as you with my Matek F411-One board. At D16 it kept dropping. After I switched to D8 I flew 20 times without any problems but occasionally it will still drop out if the sky. No problems with my antennas. I tried different esc's, resolder everything multiple times. It flies fine for a very long time but then suddenly drops. Like you mentioned the rssi is low even when I'm very close to the quad. You can see it in the video below where I'm sitting two meters behind it just before takeoff and it's 85-87 rssi.

I ordered another board as I like to fly in locations that are difficult to retrieve the quad so this makes me feel very insecure.

The board would be great if worked as intended and I hope eventually the problems will be solved and I'll be able to use it on another build.

The devs are doing the best they can and I appreciate the fact that at least they made it working.

https://youtu.be/W0PcHnmGjn4

@markusbrand

This comment has been minimized.

markusbrand commented May 29, 2018

@slekkas
This is the board I purchased: https://www.banggood.com/Matek-System-F411-One-30_5x30_5mm-F4-Flight-Controller-AIO-OSD-5V-BEC-Current-Sensor-for-RC-Drone-p-1276184.html

I don't have low RSSI during start. I got 99 when I'm close to the quad. If I'm too close (1 meter or less) there is this RSSI problem that you lose connection, but this issue is with all frsky XSR receivers as well - so no problem.

In your video you have constantly low RSSI values. I'm around 60 RSSI when I'm really far away (1 km). I'll do some DVR recording and post it here.

From the image of your quad it seems that your antenna position should be fine as well.

@mikeller

This comment has been minimized.

Member

mikeller commented Jun 10, 2018

@turboed13b: This has been addressed in #6076. Can you please close this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment