There are only a few FPV-UA-cam channels who can do it right! and I will try to offer them as well... I think you are one of the only few, the way you speak, and how you're doing the presentation... are very clear! I was very impressed!... I think you have what it takes to teach others, because you know how to explain things to the last detail... I would like you to consider making a series on basic FPV electronics, which is one of the things that keep away new people from joining the FPV... and I'll explain myself: In all the UA-cam channels, everyone talks about building, throwing all sorts of explosive words and concepts into the air???... but wait a minute guys, what is PDB? what all the components on the board are? what is a Resistor? for example... that's what I had to deal with and still??? Thank you and happy holidays!
hei, what about flysky ? after first flight i am having issues, it just drops down from the sky mid-flight. It does not lose connection to transmitter. Thanks !
I have the issue of my Mobula 7 falling out the sky for no reason with an XM+ Rx soldered on. Its the EU option of the full kit with charger etc. Any fixes for that by chance?
Seems like all whoop board with FRSKY SPI in D16 has this issue. Ive had this happen with EVERY whoop board with the SPI receiver for the past year. Thanks for posting this video!
My mobula 7 vilently snaps pitching backward and yawing right or left whenever I give it hard trottle. It also will throttle up when throttle is cut. The nose doesn't wonder or anything but the motors rpm's increase when cutting throttle. Only happens in beta flight 4.2 with rpm filtering. No issues in 4.0. I've tried, the past 5 previous BLheli-s firmwares, all the dmag and timing settings in blheli. I've tried every setting, filtering, tpa, idle speed, no flitering, crazy high filtering, 0 dterms, 100 determs, 4-5 different cli dumps from other people. And, I've even tried 4 new motors. I can't figure it out... Any thoughts?
I have the crazybee x f4. when I arm it, the motors spin fine, but as soon as I try to take off, or use any of the sticks, it takes off like 2-3 inches, spinning, then falls out of the sky. the only 2 times it doesn't do this are,1: if i move the throttle really fast to like a quarter, then back down, the motors will spin up slightly, then go back to idle, and 2: if I push the throttle all the way up, the quad goes about 10 inches up, and falls. After it falls, I have to disarm the quad, then rearm it, to get the motors to spin at idle again. I cannot find anything about this problem, any help is appreciated!!!!
I never was able to get mine to bind in D8. It just wasn't having it. I've had it in D16 channel 1 - 8 since it arrived two weeks ago. Flown ~50 packs, no problems so far.
Hey joshua, my mobula7 vtx goes disconnected soon as it takes off, so switching to cheap box goggle and it does the same.. .... I use hdo goggle and rapidfire..... But when the vtx and fc is cold and connect with the box before the rapidfire, it seems like the video stays on.....this vtx is second one that I've received from rdq and they said i can't get a replacement of the whole drone.. .... Can you please help me whats causing this? The rapidfire works really good on my beebrain lite but it sucks with mobula7....
My UR65 which uses the same had this issue. Was easy to tell it was FC lockup as the OSD paused when it happened, timer stopped etc. My CPU utilisation was also at 50% with air ode dynamic filter etc on, so adjusting my pid loop numbers a little helped bring that under control too. UR65 uses the CrazybeeF3
I noticed that in my old Mobula7 with an updated Betaflight firmware the frsky_spi_offset = -56. When I bought a new M7 with firmware from the manifacturer, the frsky_spi_offset = -38. What is frsky_spi_offset?
JOSHUA, I got my mobula 7 about a week ago . I haven't had any failsafe probs, but it does seem to twitch a little on 1s smooth as silk on 2s, really having a blast a ground the house.. I'm flying the props that came on it, maybe switching them out will help on 1s.
Me and a friend both have two Mobula7 and they never give me or him a issue when connected to a taranis x9D, but when connected to the X-lite controller we both have the drop out issue. i have changed the X-lite to D8 and seems fine so far, but to me seems like the x-lite is causing us the problem.
my mobula is somewhere between here and china... one month and two weeks so far since ordering.hopefully every bug will be worked out by the time it shows up
This is why I just buy from an RC shop that's in the same country as I'm in, it wasn't even more expensive than say banggood and I got it next day delivery.
My BetaFPV F4 brushed board was plagued by the same lockup problem. I have not had any lockup in the last couple weeks after switching to FrSky_D & D8.
Hi Joshua, thank you this helped me. I went down to 3.5.4 and thought it helped, good to know this was the answer instead. Are you running stock bf 4.0.0 pids on your mob? My motors are and have always been hot on the mob, wondering if its just normal that 2s tiny motors get hot...
I too have flown about 40 packs with D16 & FRSKY & DSHOT600 and telemetry and not seen the problem. Only mod I recall making was lower frequency to 4 & 4 because I was having betaflight configurator sometimes disconnect and the 4/4 setting lowered the FC's CPU load (as measured in the bottom of beta flight status area.
I have been having that problem with my beta 65 and 75x. I had started to wonder if it is my radio. I know they are not spi but was wondering if they were not true frsky receivers but a knockoff. I hate to put new receivers in them. My tiny hawk has to be on for about 30 seconds in the first pack to avoid it freaking out as well. Any ideas? Taranis plus.
This has been happening to me a lot in my Beta75. It will drop out of the air but the motors will be stuck at full throttle until I come over and power cycle. Should I try this on my quad too?
I had worked on fixing this bug in betaflight awhile back. It isn't so much a failsafe as the board locking up. Smartport telemetry is causing it. Turning on telemetry in frsky_x d16 will fix it.
Worked with D8, but even though I disable telemetry in Config it still pops up on my radio, and then it goes "telemetry los-telemetry rec-rssi low-telemetry-telemetry recover" and its getting SO ANNOYING.
I had this problem and figured the fix out by changing to the 8 channel. All was good for one day and then it died completely. Wish I could figure out how to install an R-XSR and forget it. The board boots fine and looks good in beta flight, just no receiver. A video on how to install the R-XSR would be great!
Hutty FPV flash your TX with a non EU OpenTX, keep your module as LBT. Then you get access to D8 in LBT, although I just reflashed all my stuff to FCC and I’m in the UK
I have the Mobula 7 with the Frsky EU-LBT board add on and my front and rear LEDs dont come on. Is it the same for you? If I bind to the main board in D8 mode they do work, but then I wont be in EU LBT mode
@@jasonhnash05 @Joshua bardwell I'm on the LBT frsky and at first I did what the manual said to turn on uart 3 rx and sbus hold bind button on the xm and bind and it all worked bottom board and xm all lit up and got telemetry ,but today I went on BF and changed to spi and frsky x and it won't bind ,so I put it back to serial sbus and sbus and can bind the xm but no lights on the bottom board now and no telemetry. It flys but got no bleeps off the board so I don't know what's happening with it😱🤯
Joshua, I'm trying to decide on the 100 to 150 dollar 2s tiny whoop but I really want something to just train with and leave my GoPro on the ground. I like the Mobula7 and Beta75x. I want to fly mainly outside. My wife is afraid I'm going to break something. I just want something to learn FPV. I've built a nice 5" Alien and I have a Hero 7 Black my awesome wife got me. So, what would be your choice for a little FPV pre-built for FrSky for outside to learn on?
The Beta 75X is for outdoors only in my opinon. It is powerful and heavy which means you don't have the throttle resolution and control you need to fly it indoors, even if you use a throttle limit. The Mobula 7 is a great quad for indoors with a 50% throttle limit, and outdoors at full throttle. But it still isn't as controllable indoors as a 1S whoop. The Acrobee Lite is a great quad for indoors only.
@@JoshuaBardwell look what I just opened when the wife and I got to Chincoteague Virginia tonight. www.getfpv.com/beta75x-2s-brushless-whoop-micro-quadcopter-xt30-frsky.html?adpos=1o1&scid=scplp9415&sc_intid=9415&gclid=Cj0KCQiAjZLhBRCAARIsAFHWpbE5toh1-LiNPWco_rom1g5fo86UBqSw42MM-eMWjXiv0l8 I couldn't paste the real picture. Now I wait to get home to the QX7
Hi Joshua, I have exactly the same problem (minute 1:10) But I have FlySky transmitter (bit.ly/2IcJb2L here my receiver setting screen) Also I turned off telemery function but it didn't help. Can you help me?
The same happens to me with the UK65. I did some research and it seems to be a well documented issue with the flight controller / SPI combination. Another workaround that worked for some was to change to Dshot 300, and 4K/4K. Unfortunately it didn’t work for me so I just lost LUA scripts. I can live with that.
Mobula 7 question: I chopped my 2.4 antenna in a crash. Woops. I think there is enough left to cut back the shield and make a new one. Can anyone measure how long the exposed core is on theirs? I'm guessing the same as any other 2.4g antenna except I don't remember mine being that long. Thanks in advance for any help.
Adam Hixon although this reply comes really late, maybe somebody want’s to know: 300 / frequency (2.4) / 4 in mm. So for 2.4GHz the exposed core has to be about 31.25mm long.
I am not having the issue and have flown 20 packs in mine and I am running it in D16. I am flying 1S all the time and wonder if that is a factor for some unknown reason.
I installed Lua scripts in my quad and BANG this started to happen! So I turned off telemetry and I am fine again now! So what is the reason for this happening?
The perfect solution. Thank you for making this post. I had the same problem with my tiny whoop SPI receivers. Turning off telemetry fixed my feel safe issue.
Unfortunately you should disable telemetry feature completely in D8 too until SPI receiver bug will be fixed. Don't worry about telemetry loss - you still receive RSSI and battery voltage (A1 sensor) in transmitter. Map those two to voice alarms and fly like nothing was changed. Yes, Betaflight LUA scripts will not work though. But SmartAudio still works and you can still change VTX channel via OSD. Yes, we know that F3 is a bit slow for BF 4.0 :) Switching to DShot300 free up CPU cycles for PID loop. Should help against accidental falling from sky.
I've been having similar problems with my Mobula 7 but I'm not of FRSky, I'm on FlySky. I also have it on D3 and i have the 4k and 4k. I also can't get the telemetry on the OSD even though it's on.
I just hooked up an rxsr and works great, Joshua could you help me figure out how to add softserial to the firmware so I can split the same user for sbus and smart audio
Eachine US/UK 65 is having the same issue on random quads. some of my friends fly great on D16 and some of them have this exact issue or other stutters. Is D8 is it but is really a "fix" it workaround? There have been some betaflight D16 bugs out there that didn't really get great attention
Hey JB I have a question I am a complete noob and whenever I come out of angle mode and go to Acro it pitches forward on its own I have to constantly pitch it back to level it out any suggestions on what could be wrong accelerometer Maybe?
I am going to guess you used the trim switches to trim out angle mode, and now when you go to acro mode your channels are not centered at 1500. Center your channels at 1500 in the Receiver tab. Then use accelerometer trim to trim out the angle mode: ua-cam.com/video/otJNzZrE-yk/v-deo.html
If you are trying to bind in D16 mode, then try D8. If you are in D8, try D16. Where do you live? Does your Taranis have EU / LBT firmware? If your Mobula has US / FCC firmware, then you cannot bind to EU / LBT firmware.
I just got one of the new versions of the mobula 7 and it beeps constantly, and doesn't arm after binding in d16. Is this the issue you are talking about in the video?
its weird how several people suffer from this while others don't. i've got 4 of these FC's (crazybee f3 pro spi frsky board) and I use d16 on all of them (qx7) with no drop out.. ::shrug::
it depends on the settings, telemetrie on/off, dshot300/600, 8k / 4k and so on. I am sure you will be able to reproduce the bug with different settings
that's my point. this is a false correlation. it's an incidental fix (for some) that doesn't identify what the actual problem is. dshot 600, telemetry on, 8/4 (and 4/2 on my 1103 build), dynamic filter (on or off), anti-grav on or off, etc. BF 3.4, 3.5... I've gone through it all and have not seen this problem. etc. even if I'm pushing the cpu idle % high. that's why it's "weird".
It's a problem...trust me. I've had this issue and a lot of others have also. I did this fix last week and it solved the problem. This has been floating around FB for about two weeks! Thanks for the video JB!
I have one of the first Mobula7 to be shipped over a month ago but as I fly EU software I ordered the EU version which comes with a xm+ receiver.......I had the same problem and thought it was the receiver but changed it to another one but the problem still exists every now and again I didn't realise this was a known problem I just thought it was just mine !! So is there a fix flying Frsky EU version anybody would know of as the xm+ doesn't use d16 or d8 protocol ?
Joshua, thank you for the video! I have a DSMX receiver and I'm having the same problem.. falling out of the sky for no reason, then a lot of cussing! : ) Can you recommend the fix with DSMX in Betaflight? Thanks
If it's a discrete DSMX receiver then I think it must be a regular failsafe. Check antennas. Swap receiver. If it happens on multiple quads then the transmitter is suspect.
Hey Joshua, after reading some of the comments, I have to ask: what’s the ruling on this? Is it a receiver issue, or a processor utilization issue that can be fixed by disabling features or degrading performance metrics?
You can get basic telemetry from the receiver like RSSI and A2 battery voltage. You could try setting the Ports tab to FrSky telemetry (not SmartPort). That's what I used to use before D16 receivers came along.
I'm sorry but i've not clearly understood which solution is the best!!! changing the receiver type in betaflight how affects the usability of the drone? JB said something about failsafe and smart audio!!! can anyone explain me? and what about the other option someone commented of disabling the telemetry? which of the two option is the best? thank you for the help PS: god save JB and it's video!!!
Joshua Bardwell thank you very much for your answer!!! I have another question... online I found someone who said that disabling the telemetry works with bf3.5 but with bf4.0 he tried everything but the only solution that has worked is to installing a xm+ receiver... have you found this "fw compatibility" too?
Strange: Once I did this I changed the My radio setting to D8 and instantly my radio said!!! Telemetry recovered. I have powers cycled both and retested both are in d 8 mode and I have Telemetry!?
Joshua Bardwell unless you want the best Angle mode settings for Betaflight, the ability to switch rate profiles automatically when you switch modes and things like not using D16... Then yeah, no need. All kidding aside, the M7 is probably my number 1 request to do a specific DIFF and setup guide for, but nobody sends me stuff for free usually. The good news is other than PIDs and filters, you can take the Tinyhawk guide I did and I'm guessing it would set it up pretty good. If I ever get an M7, then I'll do one for sure. Right now I'm pretty stoked on the NBD Beebrain LITE, so stay tuned.
The PM V3 UR65 guide seems a good place to start for the M7. The PIDs don't seem right, though, Beta75X PIDs seem to work better, it would be nice to get a dialed-in M7 tune for it. Agree with Qreacher that there are lot of good things in PM beyond the basic tune. Just switching to props out cleans up a lot.
Thanks for this video.. I was getting pissed with all the falling out of the sky. I thought it might be too much CPU usage causing it. Do you think that going back to BF 3.5.4 would fix the issue?
Joshua, great that you published this fix, but...... Why is the FRSKY_X protocol freezing the FC with the SPI_RX support and the FRSKY_D protocol doesn't do that? Personally I doubt that this is an issue of this particular FC and I am more than suspicious that this is another Betaflight issue. But I don't have any proof for my opinion.....
Might be a v1 issue. No lockouts yet on my v2 (more resilient frame) in D16. Anyone with a v2 confirmed with this issue. Kinda bad you need to lose telemetry to fix it if you have the problem. However, the model still flies great and you can use OSD to warn you of low voltage. I just need more batteries to fly more often :D
I'm having thr issue with a new one on x12 v2 board on frsky.....having a nightmare I ordered elrs radio amd recievers to hopefully install serial rx and get away from fr sky.....this thing has been a nightmare from the get....took me 4 days to get it bound and now it drops out the sky and says rf loss like every 10 sec when flying....what a headache and waste
There are only a few FPV-UA-cam channels who can do it right! and I will try to offer them as well...
I think you are one of the only few, the way you speak, and how you're doing the presentation... are very clear! I was very impressed!... I think you have what it takes to teach others, because you know how to explain things to the last detail...
I would like you to consider making a series on basic FPV electronics, which is one of the things that keep away new people from joining the FPV... and I'll explain myself:
In all the UA-cam channels, everyone talks about building, throwing all sorts of explosive words and concepts into the air???... but wait a minute guys, what is PDB? what all the components on the board are? what is a Resistor? for example... that's what I had to deal with and still???
Thank you and happy holidays!
THANK YOU JB ,WAS DEFINITELY WONDERING WHAT THE ISSUES WERE , YOURE ON POINT MY TEACHER..
when u mean full time job also u mean work on chrismass day !!!! hard working bardwell its on !!! happy FELIZ NAVIDAD JOTA BE !!!!
Dude, believe me: you're always your worse boss. 😕
For flysky version do you have improvements to make? Thanks
hei, what about flysky ? after first flight i am having issues, it just drops down from the sky mid-flight. It does not lose connection to transmitter. Thanks !
i have the same problem. mine worked for about two months ant then happend the same. have you fixed it? thank you.
Did you figure out a fix? Mine drops mid-flight with Flysky as well. It happens really close to transmitter, so I don’t think it’s a signal issue.
Same issue for me any solutions?
Same here, please help!
Found a solution about flysky?
Does anyone else have a problem where you cant fly for more than ~20sec and it says battery low?
Hi im having this problem, but im already in D8 mode(FrSky D) how did your model go after the change?
my mobula 7 is flysky and doing this so what do i do to fix it for flysky,im using the flysky fs-i6 transmitter
I have the issue of my Mobula 7 falling out the sky for no reason with an XM+ Rx soldered on. Its the EU option of the full kit with charger etc. Any fixes for that by chance?
Turn on the Warning OSD element then when it drops it will give an error code that says why. My guess is RXLOSS which means you're having failsafe.
@@JoshuaBardwell Thank you for your reply, Much appreciated.
Me too... I don't know why ! Did you solved the problem ?
I cannot get them to fly they start up but cut off soon as you throttle up I have 2 do the exact same thing
Seems like all whoop board with FRSKY SPI in D16 has this issue. Ive had this happen with EVERY whoop board with the SPI receiver for the past year. Thanks for posting this video!
Joshua, I believe that this same exact thing was happening to my SNAPPER-7!
My mobula 7 vilently snaps pitching backward and yawing right or left whenever I give it hard trottle. It also will throttle up when throttle is cut. The nose doesn't wonder or anything but the motors rpm's increase when cutting throttle. Only happens in beta flight 4.2 with rpm filtering. No issues in 4.0. I've tried, the past 5 previous BLheli-s firmwares, all the dmag and timing settings in blheli. I've tried every setting, filtering, tpa, idle speed, no flitering, crazy high filtering, 0 dterms, 100 determs, 4-5 different cli dumps from other people. And, I've even tried 4 new motors. I can't figure it out... Any thoughts?
I have the crazybee x f4. when I arm it, the motors spin fine, but as soon as I try to take off, or use any of the sticks, it takes off like 2-3 inches, spinning, then falls out of the sky. the only 2 times it doesn't do this are,1: if i move the throttle really fast to like a quarter, then back down, the motors will spin up slightly, then go back to idle, and 2: if I push the throttle all the way up, the quad goes about 10 inches up, and falls. After it falls, I have to disarm the quad, then rearm it, to get the motors to spin at idle again. I cannot find anything about this problem, any help is appreciated!!!!
I made a longer RX antenna wire that hangs down and I get great range.
I stuck my antenna up through and into the camera canopy works great
I never was able to get mine to bind in D8. It just wasn't having it. I've had it in D16 channel 1 - 8 since it arrived two weeks ago. Flown ~50 packs, no problems so far.
Me too seems it jitters just a little on 1s, but I like 2s anyway
I wasn't able to bind mine in d8 either.
I couldnt get mine to bind eithre in D8, glad im not the only one, I thought I was going crazy haha.
Did y’all try to put it in FRSKY D in the configuration tab?
Really nice, JB. 😊
I've seen that before. Looks to be a common problem with those boards. 😕
I have exactly the same problem but i´m using a Flysky transmitter. Which receiver type should i change to (minute 1:46) in betaflight?
If you are not using a built-in SPI receiver, then I don't know how to fix the issue.
Just got one of these but binded to my radiomaster t8 pro in fysky d and I get low rx only 5 feet away anyone with any tips tia
Hello Joshua, could you tell me what configuration has the sensor and voltage of betaflight for mobula7? Thanks for your videos, greetings from Spain.
Hey joshua, my mobula7 vtx goes disconnected soon as it takes off, so switching to cheap box goggle and it does the same.. .... I use hdo goggle and rapidfire..... But when the vtx and fc is cold and connect with the box before the rapidfire, it seems like the video stays on.....this vtx is second one that I've received from rdq and they said i can't get a replacement of the whole drone.. .... Can you please help me whats causing this? The rapidfire works really good on my beebrain lite but it sucks with mobula7....
I have the same issue on the Betafpv 75X. and i think its a similar problem. ill try it in D8 see if it makes any difference
Did you fix it? Mind telling me what happened?
My trashcan got the same problem as the mobula. Whats the whole deal with the d8 and telemetry and failsafe?
It's the Crazybee FC that has the problem. Or specifically, betaflight has the problem with the Crazybee FC.
@@JoshuaBardwell van you tell me what find of telemetry can we get in trashcan with d8?
happy holidays, jb!!
Mine is doing this with an xm+ rx, and ideas as it's not an internal receiver built into the fc?
Look at the ultimate comment before you
This has been plaguing me on a beta65 build, thank you so much!
Happy holidays everyone. As usual great video. Thanks!!
Iv had this issue with the brushed versions this this board. This fixed it, thank you!
My UR65 which uses the same had this issue. Was easy to tell it was FC lockup as the OSD paused when it happened, timer stopped etc.
My CPU utilisation was also at 50% with air ode dynamic filter etc on, so adjusting my pid loop numbers a little helped bring that under control too. UR65 uses the CrazybeeF3
Hey Joshua, I seem to have the same issue but with my new Mobula 6 with elrs. Do you have any tips on this?
I noticed that in my old Mobula7 with an updated Betaflight firmware the frsky_spi_offset = -56. When I bought a new M7 with firmware from the manifacturer, the frsky_spi_offset = -38. What is frsky_spi_offset?
JOSHUA, I got my mobula 7 about a week ago . I haven't had any failsafe probs, but it does seem to twitch a little on 1s smooth as silk on 2s, really having a blast a ground the house.. I'm flying the props that came on it, maybe switching them out will help on 1s.
Me and a friend both have two Mobula7 and they never give me or him a issue when connected to a taranis x9D, but when connected to the X-lite controller we both have the drop out issue. i have changed the X-lite to D8 and seems fine so far, but to me seems like the x-lite is causing us the problem.
my mobula is somewhere between here and china... one month and two weeks so far since ordering.hopefully every bug will be worked out by the time it shows up
Nope, they don't do firmware upgrades in the hold of a ship in the pacific HaHa LOL
This is why I just buy from an RC shop that's in the same country as I'm in, it wasn't even more expensive than say banggood and I got it next day delivery.
@@jasondonavich2758 at the time, no one had them. they too were waiting for them to get in stock from china.
@@aaaaaaaaaassssssssdf that's why I waited for my local place to get them. Would rather wait and get excellent customer service for the same price.
My mobula 7 is dropping out of sky and then gives an "IR Error" and then will only fly at half power.
I'm thinking I have a newer version. Inside CLI I have an October date. Never had a problem.
JOSHUA , HAVE A VERY MERRY CHRISTMAS.
I'm glad my d16 mode works fine lol thanks for the fix for people with the problem!
great vid as always JB, and a happy holidays/new year to you and the family too. In kwad news... Have they sent you the trashcan yet? looks the goods.
Good thing I dont have the frsky one then.
Happy holidays to you JB
My BetaFPV F4 brushed board was plagued by the same lockup problem. I have not had any lockup in the last couple weeks after switching to FrSky_D & D8.
Hi Joshua, thank you this helped me. I went down to 3.5.4 and thought it helped, good to know this was the answer instead.
Are you running stock bf 4.0.0 pids on your mob? My motors are and have always been hot on the mob, wondering if its just normal that 2s tiny motors get hot...
I too have flown about 40 packs with D16 & FRSKY & DSHOT600 and telemetry and not seen the problem. Only mod I recall making was lower frequency to 4 & 4 because I was having betaflight configurator sometimes disconnect and the 4/4 setting lowered the FC's CPU load (as measured in the bottom of beta flight status area.
I have been having that problem with my beta 65 and 75x. I had started to wonder if it is my radio. I know they are not spi but was wondering if they were not true frsky receivers but a knockoff. I hate to put new receivers in them. My tiny hawk has to be on for about 30 seconds in the first pack to avoid it freaking out as well. Any ideas? Taranis plus.
This has been happening to me a lot in my Beta75. It will drop out of the air but the motors will be stuck at full throttle until I come over and power cycle. Should I try this on my quad too?
Please Stop for one moment your great work my friend.
Have a nice Christmas Time bro.
I had worked on fixing this bug in betaflight awhile back. It isn't so much a failsafe as the board locking up. Smartport telemetry is causing it. Turning on telemetry in frsky_x d16 will fix it.
Interesting. But I love telemetry!!!!!!
Does this only happen with frsky or does it also do it on flysky too?
Worked with D8, but even though I disable telemetry in Config it still pops up on my radio, and then it goes "telemetry los-telemetry rec-rssi low-telemetry-telemetry recover" and its getting SO ANNOYING.
Try this: put it back into D16 mode, but when you bind, choose "1-8 telemetry off" instead of "telemetry on".
So where do I find “1-8 telemetry off”? On my radio? Or in betaflight?
I had this problem and figured the fix out by changing to the 8 channel. All was good for one day and then it died completely. Wish I could figure out how to install an R-XSR and forget it. The board boots fine and looks good in beta flight, just no receiver.
A video on how to install the R-XSR would be great!
Thank you.. I'm still wating for mine to come in so good to know.
What about if your in the uk with LBT and there for don’t have D8 mode?
Hutty FPV flash your TX with a non EU OpenTX, keep your module as LBT. Then you get access to D8 in LBT, although I just reflashed all my stuff to FCC and I’m in the UK
If you aren't using the SPI rx then this exact issue doesn't affect you.
I have the Mobula 7 with the Frsky EU-LBT board add on and my front and rear LEDs dont come on. Is it the same for you? If I bind to the main board in D8 mode they do work, but then I wont be in EU LBT mode
@@jasonhnash05 @Joshua bardwell I'm on the LBT frsky and at first I did what the manual said to turn on uart 3 rx and sbus hold bind button on the xm and bind and it all worked bottom board and xm all lit up and got telemetry ,but today I went on BF and changed to spi and frsky x and it won't bind ,so I put it back to serial sbus and sbus and can bind the xm but no lights on the bottom board now and no telemetry. It flys but got no bleeps off the board so I don't know what's happening with it😱🤯
Could this be a problem with the 75X too? My 75X does the same thing. My Mobula is in the mail.
what is that bar on the top of the screen?
Joshua, I'm trying to decide on the 100 to 150 dollar 2s tiny whoop but I really want something to just train with and leave my GoPro on the ground. I like the Mobula7 and Beta75x. I want to fly mainly outside. My wife is afraid I'm going to break something. I just want something to learn FPV. I've built a nice 5" Alien and I have a Hero 7 Black my awesome wife got me. So, what would be your choice for a little FPV pre-built for FrSky for outside to learn on?
The Beta 75X is for outdoors only in my opinon. It is powerful and heavy which means you don't have the throttle resolution and control you need to fly it indoors, even if you use a throttle limit.
The Mobula 7 is a great quad for indoors with a 50% throttle limit, and outdoors at full throttle. But it still isn't as controllable indoors as a 1S whoop.
The Acrobee Lite is a great quad for indoors only.
@@JoshuaBardwell look what I just opened when the wife and I got to Chincoteague Virginia tonight. www.getfpv.com/beta75x-2s-brushless-whoop-micro-quadcopter-xt30-frsky.html?adpos=1o1&scid=scplp9415&sc_intid=9415&gclid=Cj0KCQiAjZLhBRCAARIsAFHWpbE5toh1-LiNPWco_rom1g5fo86UBqSw42MM-eMWjXiv0l8 I couldn't paste the real picture. Now I wait to get home to the QX7
Hi Joshua, I have exactly the same problem (minute 1:10) But I have FlySky transmitter (bit.ly/2IcJb2L
here my receiver setting screen) Also I turned off telemery function but it didn't help.
Can you help me?
Same problem here
same problem here. have you found a solution ?
Found a solution, have you fixed that? Thank you
do you Found a solution?
The same happens to me with the UK65. I did some research and it seems to be a well documented issue with the flight controller / SPI combination. Another workaround that worked for some was to change to Dshot 300, and 4K/4K. Unfortunately it didn’t work for me so I just lost LUA scripts. I can live with that.
hey dude im having this issue also with my uk/us65 have you managed to find away around it?
Captain Whysall I just changed to D8, 8k/8k. Never had the problem again. The downside is that you can’t use LUA scripts.
@@sebastiansombra sweet im on dshot300, d8,8k/8k with the telemetry feature off! fingers crossed it works!
It will! If not, try different combinations like 8k/2k etc.
I do have telemetry on BTW
Mobula 7 question: I chopped my 2.4 antenna in a crash. Woops. I think there is enough left to cut back the shield and make a new one. Can anyone measure how long the exposed core is on theirs? I'm guessing the same as any other 2.4g antenna except I don't remember mine being that long. Thanks in advance for any help.
Adam Hixon although this reply comes really late, maybe somebody want’s to know:
300 / frequency (2.4) / 4 in mm. So for 2.4GHz the exposed core has to be about 31.25mm long.
I am not having the issue and have flown 20 packs in mine and I am running it in D16. I am flying 1S all the time and wonder if that is a factor for some unknown reason.
I installed Lua scripts in my quad and BANG this started to happen! So I turned off telemetry and I am fine again now! So what is the reason for this happening?
just disable telemetrie this will fix it too. I still hope the fix the spi bug which has been there since forever
The perfect solution. Thank you for making this post. I had the same problem with my tiny whoop SPI receivers. Turning off telemetry fixed my feel safe issue.
Unfortunately you should disable telemetry feature completely in D8 too until SPI receiver bug will be fixed. Don't worry about telemetry loss - you still receive RSSI and battery voltage (A1 sensor) in transmitter. Map those two to voice alarms and fly like nothing was changed. Yes, Betaflight LUA scripts will not work though. But SmartAudio still works and you can still change VTX channel via OSD.
Yes, we know that F3 is a bit slow for BF 4.0 :) Switching to DShot300 free up CPU cycles for PID loop. Should help against accidental falling from sky.
@@KrotowX please if you want help me to understand what happen here!!! ua-cam.com/video/FShZ4xt-Z94/v-deo.html
I've been having similar problems with my Mobula 7 but I'm not of FRSky, I'm on FlySky. I also have it on D3 and i have the 4k and 4k.
I also can't get the telemetry on the OSD even though it's on.
Josh Hi there, I was just going to ask if you don’t have the problem do you think it will develop later on or should I be all good?
As was posted below, turn off the telemetry on any of your SPI receivers and the problem should go away.
I just hooked up an rxsr and works great, Joshua could you help me figure out how to add softserial to the firmware so I can split the same user for sbus and smart audio
Search my channel for "matek F405 Smartport"
Gosh! Take a Break, it's Christmas. You've earned some free time...
Merry Christmas josh
Eachine US/UK 65 is having the same issue on random quads. some of my friends fly great on D16 and some of them have this exact issue or other stutters. Is D8 is it but is really a "fix" it workaround? There have been some betaflight D16 bugs out there that didn't really get great attention
At least 4 issues with FrSky X SPI on github. Latest fixed in 4.0 #6996
I get a twitch every 5 seconds with 1S or 2S. Tried disabling telemetry, dshot300, 4k 4k. And nothing fixed it until I bound in D8 mode.
i get failsafe when its close bad rx comes up but ok far away
Hey JB I have a question I am a complete noob and whenever I come out of angle mode and go to Acro it pitches forward on its own I have to constantly pitch it back to level it out any suggestions on what could be wrong accelerometer Maybe?
I am going to guess you used the trim switches to trim out angle mode, and now when you go to acro mode your channels are not centered at 1500.
Center your channels at 1500 in the Receiver tab.
Then use accelerometer trim to trim out the angle mode: ua-cam.com/video/otJNzZrE-yk/v-deo.html
I need help, I buy One and a try and try bind and dont can
If you are trying to bind in D16 mode, then try D8. If you are in D8, try D16.
Where do you live? Does your Taranis have EU / LBT firmware? If your Mobula has US / FCC firmware, then you cannot bind to EU / LBT firmware.
I just got one of the new versions of the mobula 7 and it beeps constantly, and doesn't arm after binding in d16. Is this the issue you are talking about in the video?
No, that's a different issue :-(
its weird how several people suffer from this while others don't. i've got 4 of these FC's (crazybee f3 pro spi frsky board) and I use d16 on all of them (qx7) with no drop out.. ::shrug::
it depends on the settings, telemetrie on/off, dshot300/600, 8k / 4k and so on. I am sure you will be able to reproduce the bug with different settings
that's my point. this is a false correlation. it's an incidental fix (for some) that doesn't identify what the actual problem is. dshot 600, telemetry on, 8/4 (and 4/2 on my 1103 build), dynamic filter (on or off), anti-grav on or off, etc. BF 3.4, 3.5... I've gone through it all and have not seen this problem. etc. even if I'm pushing the cpu idle % high. that's why it's "weird".
maybe only seen on 1S? i never fly 1S on this board. only difference I can think of that I haven't gone through.
@@Mewted its an overload of the cpu its just freezes. so all settings matter ;-)
It's a problem...trust me. I've had this issue and a lot of others have also. I did this fix last week and it solved the problem. This has been floating around FB for about two weeks! Thanks for the video JB!
That’s exactly what mine was doing. I was about to buy a new flight controller for it. Thank you
I have one of the first Mobula7 to be shipped over a month ago but as I fly EU software I ordered the EU version which comes with a xm+ receiver.......I had the same problem and thought it was the receiver but changed it to another one but the problem still exists every now and again I didn't realise this was a known problem I just thought it was just mine !! So is there a fix flying Frsky EU version anybody would know of as the xm+ doesn't use d16 or d8 protocol ?
If you're having this issue and NOT using the built-in SPI receiver, then I honestly don't know what the cause or fix is.
Joshua, thank you for the video! I have a DSMX receiver and I'm having the same problem.. falling out of the sky for no reason, then a lot of cussing! : ) Can you recommend the fix with DSMX in Betaflight? Thanks
If it's a discrete DSMX receiver then I think it must be a regular failsafe. Check antennas. Swap receiver. If it happens on multiple quads then the transmitter is suspect.
@@JoshuaBardwell Thank you Joshua! I'll troubleshoot and see if I can determine the problem. Thanks again for the pointers!!
Hasn't happened to me and it's set on frsky x... Weird..
Hey Joshua, after reading some of the comments, I have to ask: what’s the ruling on this? Is it a receiver issue, or a processor utilization issue that can be fixed by disabling features or degrading performance metrics?
It's a CPU issue I believe, but I don't think CPU utilization is the cause.
If we switch to FrSkyD will we be able to get telemetry back?
You can get basic telemetry from the receiver like RSSI and A2 battery voltage. You could try setting the Ports tab to FrSky telemetry (not SmartPort). That's what I used to use before D16 receivers came along.
I'm sorry but i've not clearly understood which solution is the best!!! changing the receiver type in betaflight how affects the usability of the drone? JB said something about failsafe and smart audio!!! can anyone explain me? and what about the other option someone commented of disabling the telemetry? which of the two option is the best? thank you for the help
PS: god save JB and it's video!!!
If disabling telemetry works for you, then I would prefer to keep the D16 receiver.
Joshua Bardwell thank you very much for your answer!!! I have another question... online I found someone who said that disabling the telemetry works with bf3.5 but with bf4.0 he tried everything but the only solution that has worked is to installing a xm+ receiver... have you found this "fw compatibility" too?
long story short. It works thank you so much.
I guess I'll go ahead and buy this, I heard there's a v2 with a better frame.
Yes! The v2 frame is a must upgrade.
Strange: Once I did this I changed the My radio setting to D8 and instantly my radio said!!! Telemetry recovered. I have powers cycled both and retested both are in d
8 mode and I have Telemetry!?
D8 mode does have telemetry, but it is not SmartPort. It is an older kind of telemetry and is not as functional.
Good to know, will keep that in mind
Does spektrum also suffer from this issue and if so is there a fix?
I'm not sure about the spektrum version.
Never had this problem on my dsmx version
I'll be trying this on my uk65 and ur65
Hey JB I'm having the same issue on my tinyhawk will this work??
No because Tinyhawk doesn't use SPI connected receiver.
What do you think of putting the project mockingbird V3 on the Mobula7?
I don't think it really needs it. It is powerful enough to fly great on baic tunes.
@@JoshuaBardwell I've seen videos that the project gets rid of washouts and propwash.
Joshua Bardwell unless you want the best Angle mode settings for Betaflight, the ability to switch rate profiles automatically when you switch modes and things like not using D16... Then yeah, no need.
All kidding aside, the M7 is probably my number 1 request to do a specific DIFF and setup guide for, but nobody sends me stuff for free usually.
The good news is other than PIDs and filters, you can take the Tinyhawk guide I did and I'm guessing it would set it up pretty good.
If I ever get an M7, then I'll do one for sure.
Right now I'm pretty stoked on the NBD Beebrain LITE, so stay tuned.
The PM V3 UR65 guide seems a good place to start for the M7. The PIDs don't seem right, though, Beta75X PIDs seem to work better, it would be nice to get a dialed-in M7 tune for it. Agree with Qreacher that there are lot of good things in PM beyond the basic tune. Just switching to props out cleans up a lot.
Thanks for this video.. I was getting pissed with all the falling out of the sky. I thought it might be too much CPU usage causing it. Do you think that going back to BF 3.5.4 would fix the issue?
No, I don't think so. It's a bug in the SPI receiver code.
Didn’t have any problems with my M7. But thank you.
Does the fix work with EU firmware? I have the same problem
With EU firmware you have an on board XM+ receiver so this fix does not apply. This fix only applies to the SPI receiver.
@@JoshuaBardwell But my Mobula7 has exatcly the same problem. What can I do to fix this? Lower PID loop freqency?
Thanks for this big j
Joshua, great that you published this fix, but......
Why is the FRSKY_X protocol freezing the FC with the SPI_RX support and the FRSKY_D protocol doesn't do that?
Personally I doubt that this is an issue of this particular FC and I am more than suspicious that this is another Betaflight issue. But I don't have any proof for my opinion.....
I do agree it's a Betaflight issue, and many others say so as well. Nevertheless, if this lets me fly, that's all I care about.
Thanks for the information
Your the man! Thank You!
Love you Josh! My Trash is flying..
Might be a v1 issue. No lockouts yet on my v2 (more resilient frame) in D16.
Anyone with a v2 confirmed with this issue.
Kinda bad you need to lose telemetry to fix it if you have the problem. However, the model still flies great and you can use OSD to warn you of low voltage.
I just need more batteries to fly more often :D
I'm having thr issue with a new one on x12 v2 board on frsky.....having a nightmare I ordered elrs radio amd recievers to hopefully install serial rx and get away from fr sky.....this thing has been a nightmare from the get....took me 4 days to get it bound and now it drops out the sky and says rf loss like every 10 sec when flying....what a headache and waste
Hmm I never had this issue...and flew about 75 packs through it and flying about 200 meters
Agreed. D16, no prob.
now my RSSI is 0 ? Hmmmm
I’ve got dozens of packs through my mobula... haven’t seen this hmmm