One additional tip for NOGYRO that I overlooked. If your FC has a gyro with ribbon cable connecting it, then the ribbon cable may be damaged or disconnected. In this case, you might be able to replace the cable or the gyro, instead of scrap the entire FC.
Amazing. I just built a Phantom with a naked vista and i couldnt figure out why it wouldnt arm. Well, I go to the other Bardwell video to add Betaflight warnings to DJI goggles and find "calib" warning. Come to this video, and in just a couple minutes i find out that it wont freakin arm because ITS SITTING ON TOP OF MY FAN BECAUSE I DONT WANT TO OVERHEAT MY NAKED VISTA, AND MY FAN IS VIBRATING THE GYRO. Thanks Joshua.
I actually had an issue with arming after a short flight the other day and was super happy to see this series. I connected to betaflight and realized all the setting had been erased. It was like it was a brand new fc. I have no idea why it cleared all my settings but at least I don't need a new fc as of right now.
The calib error can also occur if you have high electrical or EMF noise, for example because of a noisy 5V supply , or if you gyro is super close to your 4in1 ESC.
Elwin van der Meer I totally agree. I fixed a Calib Flag on a Betaflight F4 board by going from Vbat power input to an external 5V bec. So don’t throw away your FC just yet!
@@mcrubens But that way you don't have vbat in your OSD. The BEC on your FC is no good and you should demand warranty of the seller for a faulty FC. If you are trying 32KHz I can recommend among others Airbot OmniNXT and Matek 32KHz FC's. Beware of crippled fakes so best order direct from manufacturer.
i did fix a brand new board that someone gave me that had a[ no gyro] flag by sticking it in a small toaster oven on top of a piece of tinfoil and turning oven to 450 deg .i placed a1 inch thin piece of solder wire beside it on foil and when it melted ,which once hot melted quik, i turned off oven let cool ...AMAZING!!!!!SUCCESS...
I came across another fix for NOGYRO (and probably other flags). Although its probably not a very common thing to happen, if in tuning your drone though Betaflight you endup copying CLI dumps into your FC, make sure they are correct for your, well, everything. At least for the BetaFPV drones, the company has all the default CLI dumps for each model. If you are experiencing issues like NOGYRO, try installing the default CLI dump for your model and take a look at the CLI Status again.
i had just crashed my drone when i watched this video, turns out a small piece of wet tree leaf was on the chip, i cleaned it with a toothbrush and it works perfectly now
I had a Calib flag, that I couldn't get rid of, on my betaflight F7 board. After saving FC settings, I (re)flashed my latest firmware. I checked status and the Calib flag was gone. Reloaded settings, disconnected betaflight, and it armed..👍🏼
Joshua - First, thank you for putting this together. I almost didn’t get started in this hobby because it can become so technical. I bought a quad and enjoyed flying. Just that simple. Then when I started to build and buy advanced quads the headache started. Without your work, Blue Falcon and others I would have given up and almost did. I still have a brand new quad I haven’t figured out yet, but I will. All this stuff is just too much. It is like using your credit card, I don’t want to answer 5 stupid questions, I just want to buy it. We need an "I just want to fly the darn thing" setting in quad software. There needs to be a base config standard.
Yeah I had no gyro problems like many others on two HGLRC F428 boards new out of the box. Reflowing wouldn't work reliably. Third one I purchased a few months later works ok.
Blue falcon (RIP) has a video on replacing processor, or pretty much any surface mount component on your FC. Holy crap, I would never attempt that. But very interesting to watch. I would have never thought you could do that.
Never underestimate the Glitch Gremlin and those electronic ghosts...^^ And lol we actually had someone have the gyro not calibrating a couple days ago. Turned out later the gyro took *really* long to calibrate, like over 1 minute... o_O Oh one more thing, I have the same issue with my barometer - after a crash it stopped working and now is intermittently showing wrong numbers but mostly zero. A case where reflowing might do the trick but I'm way more experienced now with soldering than I was back when I put my Geforce 270 into the kitchen oven because I had read about it. So I'm not gonna stick my FC into the oven, mostly thanks to you (and Ben Heck...) xD
good timing on the vid, i just got my freestyle quad up to 3.5.1 and had trouble getting it armed. the flag numbers in the info tab help a little , but reading the CLI status really just spells it out. i had min check wrong and the betaflight connection also blocking it.
I had a situation just last week where I took my quad out for a hike, and when I finally got to the spot I was going to fly, I only got the esc power up tones (no signal confirmation tones) saw the "NOGYRO" flag. Quad wouldn't arm. Power cycled the quad, still no signal confirmation tones and "NOGYRO" flag was still there. Went into my OSD menu, hit "Save+Reboot", got random sparatic esc tones, and afterwards my quad armed and operated as usual. Was really weird.
Another thing, that causes NOGYRO flag is when one somehow shifts gyro_to_use to the wrong gyro. This happened to me with Omnibus nano v6, where therer is only one gyro, but it is mapped to the "SECOND" gyro position. I flashed the FC, but overlooket to stick this specific command to cli (set gyro_to_use = SECOND), when I was restoring my FC config. Spent some thrilling time to figure it out. I thought I fried gyro somehow )))
Mr bardwell, a few days ago I bought from grtfpv an happymodel x12 aio 5 in one with spi frsky when I plugged into betaflight some time, most of the time the gyro and accelerometer icons are in gray and in some cases they are on. I first thought it was that I was using betaflight 10.07 and it said that using an older version of betaflight could corrupt the firmware, I updated betaflight, I flashed the fiemware as you explained and it still does the same. One thing to mention is that when I autodetected the first time the board it said it was crazybee4sx1280 and its supposed to be an crazybee4fr, I tried flashing both and always happens and when I trie to bind it wont bind the only binding possible was with d16 mode in a taranis x9 lite. Could you help me some how?. I am from argentina therefore its a little complicated to send the board to getfpv. Regards and thank you in advance. Juan
I have found my no gyro error is intermittent. Tried to fly a few days ago on lunch and no joy. Watched your video and before I looking into the steps you mentioned I plugged in and armed, everything was fine. The correct version of BF is installed. Thinking the board is just on hospice.
Hi. I have problem with calib flag but only when i connect 4s battery. When i fly with 3s everything is normal but on 4s gyro is making some sort of vibration even if drone is not moving
I have this issue ...sometimes arming without any problem, sometimes not and I get (CALIB) msg The sound when I connect the battery with the quad normal What should I do to solve this????
Hi, I just build my first HDV DJI build using the KakuteF7 HDV&Tekko32 F3 4in1 45A ESC STACK . ... I have a strange issues of arming ... the quad will only arm when I am connected to USB to the Betaflight configurator (and the battery) and enabling the motors as well ... if I disconnect the USB cable and disconnect and reconnect the battery I get arming code 8 CALIB .... any idea what is going on ?
Well still no gyro and it's a brand new nazgul BNF. F's in the chat. It happened after I flashe to old BF version so I can install the factory dump CLI. After that all good, except the gyro is not detected. If I update the firmware to BF 4.4 I can see the gyro but it's really weird because the frequency is 3.2 kHz and not the usual 8 kHz. Very confused on what to do. Need to write to iFlight.
I think I understand now why people are replacing their Jesus portraits on the wall to Bardwell's. I have like 1 week of debugging this stupid calib message, and nobody ever mentioned that it has got renamed in beta. What's interesting it did arm when I didn't strap the battery on the drone, just put it down on the next to it, but when I strapped it there, it just refused to arm. Maybe it picked up something from the battery, magnetic field, or something.
Hey Josh I got the CALIB flag when I use a 5s lipo but not when I use 4s lipo. Going to take it back down to 8k/8k and see if that fixes it. Wondering if you heard of going up in cell causing this issue before?
Where is the accelerometer on a Mobula7? And could it get broken or go bad from a crash? I was noticing last night that if I had it level on my screen and turned it upside down and on my screen it was like upside down on like a 45 degree angle but I had it level upside down.
hello josua. . thanks for your very effective video. . . But I have another kind of problem. . while until now the GPS worked. . after the betaflight update 3. 5. 0 when I insert the gps with the stick as before the motors stop and the drone drops. . with the same GPS features as version 3. 4. 0. . . do you have any idea? maybe you need to change the SANITY RESCUE. . . ? THANK YOU
ooH NO.i THINK I SHOULD BUY A NEW FLIGHT CONTROLLER. i CRASHED IN THE SNOW: IVE DRYIED EVERZTHING; but the quad wont arm. and in betaflight is says no gyro/Acc found :(((
Damn... I'm a moron... tried hand launching out of a field of wet grass after treking to the top of the hill as you do and "calib"..... damn I am over the moron threshold Fo Sho lol, Thanks for the very helpful info I shall walk of shame away, to my totally fine quad...
What do i need to do when i plug my quad into the computer and betaflight shiws that its rotating at the z axis, but the quad isnt moving?Its a broken board?
Thank you@@JoshuaBardwell! Unfortunately it wont arm for some reason but i check out your "wont arm" videos and ill try it again a few days later Hopefully it will work
At the higher voltage there is more gyro noise which puts the gyro over the edge. The underlying issue is that there's too much gyro noise. It might mean the gyro is going bad. But IMO the TH2 is marginal on 2s anyway so just stick t 1s and you'll be OK.
My LarvaX wouldn't arm after I moved the guts over to a toothpick frame and I lowered the gyro update frequency to 4kHz instead of 8 and now it arms fine. Any explanation of that? EDIT: JK that still didnt fix it, have the CALIB error. hmm
my old FC is seriously pro f3 and recently everytime I set gyro and loop into 4Khz and 4 Khz it wont arm instead I have to reduce it to 4Khz and 2Khz is this normal?
I've tried 4k/4k on my SPRacingF3 with BF3.4 and it still arms but the CPU load is seriously high. What do the 'Arming disable flags' say when you enter 'status' in CLI while your FC doesn't arm? If it says LOAD this is because BF 3.4 is using more CPU power than the earlier versions. You can try turning off some features you think are less important than the 2K PID loop.
Thank You Jannes and yes jannes after i turn off baro , magneto and blackbox like you've suggested, now I am able to armed the quad. I remember that JB already warn us in one of his video when introducing the btfl3.4 that it will takes a lot of CPU power when applied in F3 board, but I don't realize that this is an example of F3 board behaviour when it lack of CPU power. Thank you again Jannes for your help.
Mr JB You make this for me?... Im gonna try different firmwares because its still being so dumb.. I got i working by putting an adjustable Regulator between 4in1 power and fc and adjusting it. It hovers but did a death roll after tried a couple of flips in horizon mode... 😔 Its the mini f4 osd from bangood btw and i think its the omnibus F4 i flashed it too.. Still scratching my head about it.
Sounds like a esc issue , I would try a different 4in1 . Something's going on with the regulator in the 4in1. I don't think there's anything wrong with the fc
hello jos,i use f3 6dof fc - airbot bumpbees 30a esc and racerstar 2600kv. the problem is quad death roll, what should i do. any setup with betaflight can help me?
If you lowered digital idle percent, raise it back up again. If it's at default, raise it a little bit... like maybe to 5% or 5.5% but not higher. Often, death-roll is caused by mechanical damage to a motor or ESC. If the quad always rolls the same direction then the motor or ESC it rolls towards is suspicious.
It means you are on F3 and you can't see the text string version of the flags. I'm pretty sure this video shows how to decipher the number you're getting: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-3mOeL8f1dMM.html
No what had happened was I reset the settings in the setup and now it won't beep, flash colors or anything and there is no gyro. So its going back to Amazon and it was like that when it got here 🤫
I think it is the same flags as we are talking about here but I don't recognize those exact strings so I wonder if you are using something other than Betaflight.
Is there a way to disable the gyro so you can get it to arm and use the FC on something like a fan boat or hovercraft? still have control for a motor or two and maybe a servo, but no accelerometer and no gyro. (having the magnetometer and voltage info in OSD would be cool feature on watercraft/ hmmm -prolly should be asking @petersripol
You cannot disable the gyro. The FC will not work without a gyro. But you could simply pass through aux channels to an ESC to give you direct control of the ESC.
I know this sounds stupid but go back to 3.1.7 Firmware and see if it'll arm because sometimes the new releases don't support the board software and that some of the bug fixes they need to look into. Most of the time you're good all the way up to 3.2 firware with most boards! Also check your min throttle and receivers tab in betaflight because if you're using Spektrum dx6 I like the older style it'll only go to a 1955 and 1055 on the minimum and if it's not below 1050 in receivers tab then it won't arm. Raise it to 10 60 or higher and see if it arms
I tried both of the steps u recommend, I think my esc is the problem. I got this quad second hand as the original owner had nothing but problems. I replaced the fc and tried to arm it in its factory settings and no go. I see all of the functions work properly in beta flight. Arm tab turns yellow. But the motors do not spool. Hence why I think it’s the esc 4n1.
Kframe FPV most times the connection betweeen the fc and the esc is broken on the HGLRC stacks due to crashes. You can rip those lousy connectors off and do some wires soldered in between the fc and the esc.
When i conect batery to my drone start beep otherwise and i cant arm..then i want conect to betaflight and i cant...No configuration received within 10 seconds, communication failed what that mean?what i must do?
Daniel, make sure you have the correct Comm Port set up. There are lots of videos on setting up Comm Ports for Betaflight. See if you can connect to Betaflight WITHOUT a battery attached.
cavman7 i had conect before but sometimes i cant just like now...when i wont fly i must turn on transmiter and then a quad and quad start beep and i cant fly...i had that problem before and then gone but now starts again and i cant fly...my board is sp racing f3...i dont now what to do
Daniel Katić If the problem is intermittent, then it could be a loose connection somewhere or you might need to re-flash your firmware. See if you can connect to get it to connect on Betaflight and then check/wiggle the connections on your FC and see if it disconnects.
Hey, I have a problem with my gyro... When I connect my fc to betaflight via USB everything works perfect. But when the battery is connected, the gyro just 'fries' and does not respond... Please help me
