Skip to content
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 frsky_x lockup #6172

Closed
brycedjohnson opened this issue Jun 19, 2018 · 47 comments

Comments

Projects
None yet
@brycedjohnson
Copy link
Contributor

commented Jun 19, 2018

Example of the issue and my cat grooming. At about 1:02 you can see the on time stop incrementing at 1:33. If you were flying it would fall out of the air. Seen this issue with Matek411RX and crazybeeFR F3.

https://www.youtube.com/watch?v=GtK06Mvrtwc

The debug info is the spi_frsky_x debugging. I was walking around out of the room and holding the antenna so it might have missed some packets. Not sure if that causes the issue to happen more?

In this issue I was looking at the root cause and it seemed like it was related to smartport telemetry:
#5576 (comment)

Haven't tried disabling the telemetry slidered on the configurator. That may stop this from happening, but you loose telemetry.

You can also switch to frsky_d and it doesn't have this issue.

Diff all is the same as from #6171

@mikeller

This comment has been minimized.

Copy link
Member

commented Jun 20, 2018

FrSky D still has a problem with occasional lockups when telemetry is on as well - it seems to be tied to the pre-existing CPU load, i.e. it happens more often if faster loop times are used.

Recommendation: Do not use telemetry when using FrSky SPI RX.

@brycedjohnson

This comment has been minimized.

Copy link
Contributor Author

commented Jun 20, 2018

I haven't had any lockups on frsky D and telemetry on pre-3.4RCs, but I was only running at 4k/4k.

@mikeller

This comment has been minimized.

Copy link
Member

commented Jun 21, 2018

@brycedjohnson: Interesting. My suspicion is that the lockups are caused by the generation of telemetry frames taking up too much time, and causing the SPI RX to get out of synch. If this is the case, then whether or not it's happening on a given setup will be dependent on the MCU type, and also on the number of present / activated features.

@JamilFayad

This comment has been minimized.

Copy link

commented Jun 21, 2018

Hey I am facing the same problems it is just locking up and I'm losing controls mid-air. That's not good at all. It is not falling out of the sky tho as someone noted here before. https://youtu.be/RA1teE-yYfc
Provided is a link to the DVR footage recorded as such issues were faced. Important moments to note out in the video is the 26th second, 41st, and 2 minutes and 15 seconds into the video. Any recommendations so I could have this flying the way it should? Thanks :)

@pkruger

This comment has been minimized.

Copy link
Contributor

commented Jun 23, 2018

I have the same problem. Didn't see this ticket and got a replacement FC from Banggood, still have the issue. Tried different option PID loop and Gyro speeds, also tried disabling telemetry, but it made no difference.

@JamilFayad

This comment has been minimized.

Copy link

commented Jun 23, 2018

I personally asked for a refund when banggood offered a replacement and I got my money back. Though my problem with this FC wasn't just that and that's probably why. I ended up just switching my entire FC with an FrSky XSRF4O which is an fc with an integrated receiver however its PDB-less so I had to use a Matek PDB that was hanging around. Haven't tested it yet nevertheless as far as reviews can go, I was told that this FC is a lot better and doesn't seem to encounter such problems so I am expecting good results on a fine day. Will update you tho for sure :)

@Ask1me

This comment has been minimized.

Copy link

commented Jun 24, 2018

I'm sorry if this is Out Of Topic, I stressed Out becouse of this problems :

My board FC CrazybeeF3 BNF Frysky,
my latest firmware : betaflight_3.3.3_crazybeeF3FR (Stable)
SPI_Rx Support Receiver Mode

I accidently choosing wrong SPI Reciever Provider to A7105_Flysky_2A and save it

now my FC can not connect to USB anymore, everytime connect it is says " Unkown USB device (Device descriptor request Failed) for windows 10"

is there any suggestions to fix it? please help me anyone..

@stale

This comment has been minimized.

Copy link

commented Jul 24, 2018

This issue / pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week.

@stale stale bot added the Inactive label Jul 24, 2018

@pkruger

This comment has been minimized.

Copy link
Contributor

commented Jul 28, 2018

This is still an issue, it can't be closed because it has not been fixed - yet.

@stale stale bot removed the Inactive label Jul 28, 2018

@mikerc2017

This comment has been minimized.

Copy link

commented Aug 8, 2018

midelic who create version FC integrade FRSKY . i think he can fix it . Matek fc using his code .

@H4xus

This comment has been minimized.

Copy link

commented Aug 13, 2018

I found this when searching and wanted to add that I'm still experiencing this with Betaflight 3.5 RC2.

Flash target: CRAZYBEEF3FR
Board model: Racerstar Crazybee F3 Flight Controller
ESC protocol: D600
FrSky protocol: D16 (8 channel with telemetry)
4K/4K loop timings.

D8 works fine, even with telemetry. I've not had any dropouts. However with D16 8 channel and telemetry my quadcopter falls out of the sky seemingly randomly, and I can only re-establish a link when I power cycle the flight controller.

I will disable telemetry and test tonight.

@H4xus

This comment has been minimized.

Copy link

commented Aug 13, 2018

Update:

D16 working now with no failsafes/rx failure after 6 packs when disabling telemetry both on the Taranis when binding, and within Betaflight. I still get RSSI, which is all I really want.

About to fly another 6. Will report back if things change, but this workaround appears to be ok so far.

@mikeller

This comment has been minimized.

Copy link
Member

commented Aug 14, 2018

@H4xus: You should also get battery voltage in A1.

@pd5dj

This comment has been minimized.

Copy link

commented Sep 2, 2018

Hi all, I just stumbled on this page looking for the "drop out of the sky" issue..

What is the best thing to do lately?
I have the CrazyBee F3 FR FC, (snapper7)
BF 3.3.0 installed right now.
Bind in D16 mode
I have tried D8 mode, but when arming, it directly disarms.

@mikeller

This comment has been minimized.

Copy link
Member

commented Sep 2, 2018

@pd5dj: Update to 3.5.0. FrSky D works with telemetry, FrSky X works with telemetry off.

@pd5dj

This comment has been minimized.

Copy link

commented Sep 3, 2018

@mikeller

This comment has been minimized.

Copy link
Member

commented Sep 3, 2018

@pd5dj: You will have to make sure the feature 'TELEMETRY' is enabled. And you might have to rescan the sensors.

@pd5dj

This comment has been minimized.

Copy link

commented Sep 3, 2018

@mikeller

This comment has been minimized.

Copy link
Member

commented Sep 4, 2018

Hmm, I've seen this before, and I think there was a bug causing this at some stage. But that got fixed in 3.5.

@H4xus

This comment has been minimized.

Copy link

commented Sep 6, 2018

I was still seeing it in Betaflight 3.5 RC2, and just tested again with 3.5. Still get lockups with telemetry on, fine without.

@mikeller

This comment has been minimized.

Copy link
Member

commented Sep 7, 2018

@H4xus: Yes, this has not yet been identified / fixed.

@19Gerhard85

This comment has been minimized.

Copy link

commented Sep 24, 2018

Yesterday I flew 10+ packs on the Crazybee F3. After 5 packs I had a "failsafe", the rebooted and the status message in OSD display "BADRX".

  • Board: CRAZYBEEF3FR
  • Betaflight Version: 3.5.1
  • Rx Mode: D8 w/ Telemetry
  • ESC Protocol: DSHOT600
  • Enabled Features: OSD, TELEMETRY
  • PID Loop: 4k/4k
@mikeller

This comment has been minimized.

Copy link
Member

commented Sep 24, 2018

@19Gerhard85: For now, try disabling TELEMETRY - the voltage will still be received on the TX as A1.

@jdedonato1

This comment has been minimized.

Copy link

commented Sep 30, 2018

I have the latest firmware 3.5.1. 2 quads using the target MATEKF411RX. Tried D8 and D16. D8 with telemetry still doesn't work. D16 telemetry works. One quad ( this one is a brushed) will keep at full throttle randomly and would cause a runaway so can go outdoors ( mostly when crashing) and one falls out of sky for no reason. I just lose all control and it freaks out( brushless on dshot600). Please tell me this will be fixed and I will be able to use telemetry

@jflyper

This comment has been minimized.

Copy link
Contributor

commented Sep 30, 2018

@jdedonato1 We at least your CLI diff output to say anything meaningful.

@jflyper

This comment has been minimized.

Copy link
Contributor

commented Sep 30, 2018

@jdedonato1
At least, local bench test (no flight test) with a bare MATEKF411RX flashed with 3.5.1 basically works with
D8 : OK
D16 Ch1-8 Telem On : OK

Although issue involves in-flight failure, your issue with D8 suggest there is something wrong with your setup.

@jdedonato1

This comment has been minimized.

Copy link

commented Sep 30, 2018

@stale

This comment has been minimized.

Copy link

commented Oct 30, 2018

This issue / pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week.

@stale stale bot added the Inactive label Oct 30, 2018

@stale

This comment has been minimized.

Copy link

commented Nov 6, 2018

Automatically closing as inactive.

@stale stale bot closed this Nov 6, 2018

@enhemh

This comment has been minimized.

Copy link

commented Jan 4, 2019

I'm sorry if this is Out Of Topic, I stressed Out becouse of this problems :

My board FC CrazybeeF3 BNF Frysky,
my latest firmware : betaflight_3.3.3_crazybeeF3FR (Stable)
SPI_Rx Support Receiver Mode

I accidently choosing wrong SPI Reciever Provider to A7105_Flysky_2A and save it

now my FC can not connect to USB anymore, everytime connect it is says " Unkown USB device (Device descriptor request Failed) for windows 10"

is there any suggestions to fix it? please help me anyone..

same here... any fix ?

@eitama

This comment has been minimized.

Copy link

commented Jan 23, 2019

To bad it's closed, d16 is still being used by default on mobula7 quads, which made me mess up my frame.

@ijarboe

This comment has been minimized.

Copy link

commented Jan 27, 2019

I'm sorry if this is Out Of Topic, I stressed Out becouse of this problems :
My board FC CrazybeeF3 BNF Frysky,
my latest firmware : betaflight_3.3.3_crazybeeF3FR (Stable)
SPI_Rx Support Receiver Mode
I accidently choosing wrong SPI Reciever Provider to A7105_Flysky_2A and save it
now my FC can not connect to USB anymore, everytime connect it is says " Unkown USB device (Device descriptor request Failed) for windows 10"
is there any suggestions to fix it? please help me anyone..

same here... any fix ?

I did the same thing to a different board. DId anyone find a fix to this?

@mikeller

This comment has been minimized.

Copy link
Member

commented Jan 27, 2019

@enhemh, @ijarboe: Connect the two tiny 'boot' pads on the board, then connect USB - the board will be recognised in DFU mode - flash the correct firmware, and you'll be good to go.

@ijarboe

This comment has been minimized.

Copy link

commented Jan 27, 2019

@enhemh, @ijarboe: Connect the two tiny 'boot' pads on the board, then connect USB - the board will be recognised in DFU mode - flash the correct firmware, and you'll be good to go.

I can get the board in DFU mode but no matter what firmware I flash it will not pull up betaflight afterwards even after disconnecting and reconnecting the usb.

@mikeller

This comment has been minimized.

Copy link
Member

commented Jan 29, 2019

@ijarboe: Ok. Have you tried flashing with the 'Full Chip Erase' option enabled?

@ijarboe

This comment has been minimized.

Copy link

commented Jan 29, 2019

@mikeller

This comment has been minimized.

Copy link
Member

commented Jan 29, 2019

@ijarboe: In that case it looks like the board was damaged by flashing an incorrect firmware - with the SPI RX this is a possibility.

@Protonus

This comment has been minimized.

Copy link

commented Feb 28, 2019

I am having this issue with a brand new Eachine Trashcan with the FrSky SPI FC, the CRAZYBEEF4 PRO FR (target CrazybeeF4FR). This quad ships on OpenTX 4.0.0 out of the box. I have an FrSky X-Lite, running OpenTX 2.2.3. If I bind as D16 with Telemetry enabled in Betaflight, this issue occurs.

The FC locks up when this happens, as the LED scanner rear lightbar on the Trashcan also stops moving, and it will not reconnect to r/c until it's power cycled. On my very first battery of real flight time, I had 3 distinct events of this where it would fall out of the sky and telemetry would be lost as soon as it happened, while it was only about 60 feet away. I've even had this happen while the quad was plugged in to USB with no batteries in!

Turning OFF Telemetry in Betaflight, seems to stop the the lockups of the FC; however, I still get "stutters" where the quad will lose power for a brief moment or I'll lose control of it for a moment.

If however I change it to FRSKY_D (D8) instead of the stock FRSKY_X (D16) under Receiver configuration on the Configuration page of Betaflight, and then pair my radio in D8 mode to it instead, all problems stop, and it flies as expected, no stutters, no lockups.

Though the issue may be related to OpenTX, this seems like a problem in Betaflight to me with these SPI FC's.

There is a thread on this here: https://www.rcgroups.com/forums/showthread.php?3244881-Dropouts-In-D16-Mode-With-Telemetry-On-In-SPI-Receiver-Flight-Controllers

@Asizon

This comment has been minimized.

Copy link
Contributor

commented Feb 28, 2019

the problem of temeletry at the moment has no solution, even so Frsky_X with D16 works perfectly for me with the latest builds.

@Protonus

This comment has been minimized.

Copy link

commented Mar 1, 2019

the problem of temeletry at the moment has no solution, even so Frsky_X with D16 works perfectly for me with the latest builds.

What version of OpenTX do you run and on what Radio? In researching this and reading reports, it's looking like it's an issue on OpenTX 2.2.2 and newer, and not being reported on 2.2.1 and older.

@Asizon

This comment has been minimized.

Copy link
Contributor

commented Mar 1, 2019

2.2.3,and 2.2.2 OK, X9D +

@Asizon

This comment has been minimized.

Copy link
Contributor

commented Mar 1, 2019

Also,now is LBT available for Frsky_X

@Asizon

This comment has been minimized.

Copy link
Contributor

commented Mar 1, 2019

Some fixes:
#7345

@MacGWik

This comment has been minimized.

Copy link

commented Mar 6, 2019

Hello, I have a question about this too.
Is the locks up problem only happen on SPI RX ?
Because I want to use my xm+ on the crazybee f4 on trashcan, can I use the D16 with RSSI on ?
Or just go with the D8 with RSSI on ?

@SebastiaanRutgers

This comment has been minimized.

Copy link

commented Apr 2, 2019

Flew 3 packs on my Snapper7 yesterday (CrazybeeF3) with betaflight 4.0RC4 and bound with LBT Frsky_X. Worked like a charm but had 1 hard lockup in 3 packs. Had to do a power cycle to get the quad to do anything again. This was with telemetry feature enabled.

@fOmey

This comment has been minimized.

Copy link

commented Apr 2, 2019

CrazybeeF4 plagued with the same lockups.. 4.0 RC5, SPI Frsky_X, telemetry enabled.. first pack in lock up.. without telemetry enabled, nice clean flight.

EDIT: I've tried disabling all the sensors and the lockup still occurs if telemetry is enabled..

@deepdigger

This comment has been minimized.

Copy link

commented Apr 7, 2019

@fOmey I have the same problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.