I just got my Mobula 7 Frsky model to use with my Qx7. RX binds properly and talks to Qx7 until I connect to beta flight then it is unstable and tx keeps alternating “telemetry lost/telemetry found “ and on the receiver page on beta flight the first four channels fluctuate all over. I checked all the settings in beta flight and they all match the instructions they sent. They did include a note : receiver signal will be unstable while the MSP(connect to beta flight) which it is but didn’t say what to do about it. Obviously I can’t enable any modes or anything. I tried rebooting a couple of times and rebinding but no luck. If I could arm it a least I could fly in Acro.

I m thinking it’s an issue with this latest version 4.0 beta flight that it came with because I have never had one do this before. In the mean time I would at least like to fly it . Isn’t there some combination of control stick movement you can do to arm it? I did a search but couldn’t find it.

Sorry, can't really offer a lot of help as mine still hasn't shipped yet but you can find all the Betaflight stick commands on the following web page:-

https://github.com/martinbudden/betaflig...ontrols.md

What mode are you binding it in? D8 or D16? And do you have the standard non-EU FrSky version or have you got the one with the FrSky XM+ EU-LBT receiver in? (sorry, can't remember what country you're located in).

Betaflight 4.0 is still in beta so I'm surprised that a consumer product is being shipped with beta firmware. I would probably be inclined to flash the latest release firmware (3.5.3) to it and see if that resolves your issue. There is no specific target for the Crazybee F3 Pro boards so I assume that your FrSky version is just using the same CRAZYBEEF3FR (CBFR) target as the non-pro boards. You'll be able to tell if you type the "version" command into the CLI. If you revert back to BF 3.5.3 then don't forget to take a backup of the current config first by running the "dump" and also the "diff all" commands and saving the output to a text file so you can go back to BF 4.0 again and re-apply the original config if you want/need to.

Yes mine is the is the non Uk Frsky version (I live in Washington state USA) I did bind it in D16 according to the instructions. I did find how to arm it with throttle/yaw stick and it flys fine but only in Acro because I can’t enable anything in beta flight. I would like to angle until I got used to it though.

When mine arrives I can see if it exhibits the same behaviour but I'll have to bind mine in D8 mode because I bought the non-EU FrSky one like you and that is the only way to bind it to an EU-LBT transmitter which is what I have.

Did you try flashing the firmware to Betaflight 3.5.3 to see if it eliminated the issue? If not then I would certainly try doing that.

I was finally able to get flight modes activated. It still go between lost and found rx telemetry which is really irritating to listen to but if you wait long enough in the modes page they eventually work. It flys pretty well but flight time in the 2s mode is pretty short and I don’t have a 450 1s for it yet

(25-Nov-2018, 09:16 PM)Garrace Wrote: I was finally able to get flight modes activated. It still go between lost and found rx telemetry which is really irritating to listen to but if you wait long enough in the modes page they eventually work. It flys pretty well but flight time in the 2s mode is pretty short and I don’t have a 450 1s for it yet

hi Garrace, i have the same issue, my mobula7  came with betaflight v4.0,( i dont understand why is it like that when i cant even find BFv4.0 on the stable list from BF configurator) have the annoying beeps when connected to usb and the non stop telemetry lost/telemetry found, so annoying, i tried flashing to betaflight 3.5.3 but rx just stays the same, telemetry lost/telemetry found keeps persisting, i cant adjust my sticks on betaflight and i was only able to flash it on my macbook, using my desktop cant go to DFU using bl on cli, but i was able to flash it on my macbook using that command on CLI,  is it hardware problem, the FC? now it binds to my QX7 but wont arm and just keeps beeping, pls help 
thanks a lot

I had the same issue with a different receiver. Turns out I flashed the wrong firmware (EU instead of FCC)

It'll also do this continuous telemetry lost/telemetry found if you somehow switch your Taranis from internal RF to external RF

I gave up on arming with the switch on my qx7 that I use for my other Quads. It shows up on modes page but is never activated and switch doesn’t move. I set it up on my tx same way as all the rest. So I just arm and disarm with throttle low/yaw right/left which is fine. I was able to get angle and horizon mode working but that’s where I ran out of patience and just been flying (and breaking it Lol)

(25-Nov-2018, 05:05 AM)Garrace Wrote: I m thinking it’s an issue with this latest version 4.0 beta flight that it came with because I have never had one do this before. In the mean time I would at least like to fly it . Isn’t there some combination of control stick movement you can do to arm it? I did a search but couldn’t find it.

Mine did this as well. I was still able to enable ARM,FLIGHT MODES, WND FLIP OVER, you just have to take your time .
F.K.

Yeah I was eventually able to get everything I wanted working just irritating to listen to the tx. Mine flys best outside as my house is pretty small and this thing breaks pretty easily if it hits a wall or the floor. Throttle is really touchy on 2s so been flying mostly on 1s and still has plenty of power at least for me.

I've just stumbled across something that you guys might find useful, or anyone else who has the same issues as described in this thread.

The information below is for the Crazybee F3 non-Pro FC but the Pro version is based on the same architecture and uses the same Betaflight firmware as the non-Pro version, so this information very likely applies to the Crazybee F3 Pro FC as well. I've highlighted the parts of interest in red. What it's essentially saying that if you enable the Betaflight telemetry feature, you can experience problems. This may go some way to explaining some of the issues experienced by members in this thread. To avoid such issues, the recommendation is to disable telemetry on the FrSky versions of the Crazybee F3 flight controller:-

Quote:FAQ & Known Issues

FRSKY Version:

• To bind to your Taranis, you need to be running the non-eu OpenTX version, which allows you to use the required D8 setting to bind to the RX. The factory default BF receiver mode is FRSKY_X, so remember to configure this if needed.
  
• FrSky X (8 / 16 channels) and FrSky D (8 channels) work both reliably, including in combination with crash flip / Dshot beacon, as long as the TELEMETRY feature is disabled; Basic telemetry information like RSSI and battery voltage will be sent even when the TELEMETRY feature is disabled;
  
• On FrSky D, the TELEMETRY feature causes occasional dropouts, depending on how many sensors (BARO, GPS, ...) are enabled, probably due to a timing overrun;
  
• On FrSky X, the TELEMETRY feature causes hard lockups due to a bug in the telemetry generation code. 
  

The source of the above information can be found at the following link: https://github.com/betaflight/betaflight...BeeF3FR.md

Wish I had seen this BEFORE I ordered this thing ! Video off to Get FPV ... Want full refund on the unit and all accessories !! Batteries canopy extra frame all of it ! ! Re posting link to this on RC Fourms I hope that is ok because THEY DIDN'T HAVE THIS INFORMATION !! Damnit !

I am totally new to this and it has been challenging.  I bought the Mobula 7 and a Taranis X7 to learn how to fly.  I was able to put the latest OPEN TX on the X7 and I was able to flash the controller to  CRAZYBEEF3FR Name/Version: 3.5.6 Binary: betaflight_3.5.6_CRAZYBEEF3FR.hex.  I am not sure this is the correct one, but I think so.
I was able to bind to the receiver, but I get the same problem mentioned with total unstable telemetry in Betaflight, it keeps turning on and off.  In the motors section I can't get the motors to spin although when I move the Mobula it shows movement on the Betaflight screen so there is some connection.  I can't get BHELISUITE to connect to flash the escs.  It connects but says it can't find esc 1 or any others, also won't spin motors.  The other super pesky thing is that when you plug in the battery, no USB connected, the Mobula just starts continuously beeping.  Clearly I am doing something wrong or some setting is wrong. There are so many layers of software.  I configured the UARTS in Betaflight as it says in the manual.  Any suggestions would be greatly appreciated.