heyyyyy! yeah I think this AIO is one of the hand full that are doing it at the moment. It is going to kinda of come full circle though as other vendors change up the gyro they have been using for something more available or economic.
heyyyyyy! I was gonna tell you, hopefully I have a Saturday during the day stream coming up soon that you should be able to catch at an appropriate time, lol.
Yeah, it is getting more and more that way for sure. I have been messing with quicksilver lately, and I gotta say I kinda like it. Maybe some day I will get around to trying Fettec.
I upgraded Betaflight Configurator to the latest version (it was 10.9.0 but seems like release candidate or something) and gyro fixed. Took me half a day to figure out
It sounds like maybe they fixed your target in a newer version and that upgrade got you access to it :) They have been fixing a ton of them lately...now we just have to see how long it lasts before the board manufacturers change something up to break them again, lol.
Thanks, this helped, but the BF devs didn't seem to appreciate the input: "Our policy is that only original target drivers are to be included on unified target or board configurations.
You saved my Bacon! I just got a Mob8, and I was having a super hard time getting my gyro and accelerometer to work. This fixed it in no time, and I'm running 4.4.2 with ELRS 3.0! Thanks again, and I have subbed.
So I followed the instructions by the way? I'm upgrading my flight controller so that I can use express ELRS 3 But when I use my c l I dump I get a lot of errors
yeah the config differences between 4.3 and 4.4 will for sure throw some errors. they depreciated lots of lines in 4.4, so just read through the error lines and try to determine if anything that is having a problem is actually important to your config. Most of the time the ones I get are for things like the barrometer or magnetometer, so not too critical. There are also some online tools that can go through your CLI dump and tell you what may or may not be 4.4 safe.
i thought i would do the same to babyape v1 now i have a red light back flashing in the middle of the board and a gyro ..cheers i just goto put a rx on it to see if i fixed it from knocking that cap off (electronic magnifying,just hard to solder tiny things :)cheers again mate
Heck yeah man!!! hopefully that cap is all good now and you can get it back in the air. I bet there are a whole lot of people out there with what they think are dead boards on 4.4 who could probably get them back to life with a different gyro driver!
I was wondering who was going to make a video on this. I guess it's just us cheapskates using these cheap boards so the bigger channels with big bucks haven't seen it. LOL!
lol, yeah I went with this board for the 15A's and because I could afford to use it! Sometimes being small potatoes lets me take a look at things a little differently, and I do enjoy it :)
One question: Would it be ok to just get 4.3.0 version of the board that I am using (SPEEDYBEEF7MINI) instead of doing it the long way? Does getting 4.3.0 give access to gyro and accelorometer?
So technically, going back to BF 4.3 on any board that was around when 4.3 was current firmware should fix the gyro issue. They load all of the gyro drivers in that version, so this whole thing where the right one isn't loaded doesn't become a problem. It does depend though...since if a board was new when 4.4 was the most current, they might not have a 4.3 target for it as it didn't exist at the time.
when i load the "Core only" firmware in BF 4.5 - "status" in CLI shows me BMI270. And i can see the drone in the Setup Tab moving correct. But when i write "USE_ACCGYRO_BMI270" in custom defines it wont load the firmware online without showing me errors in the log. Is there another Define in BF 4.5 ? The link in your description is dead :( I have a BETAFPV Meteor75 pro with BetafpvF411RX Board target. Also when i try reflash to 4.2.11 with my backup the gyro makes troubles. only in core only mode everything seems ok.
That is a good question! BF actually broke the release notes section that would have all of the answers in their Wiki, but all of the references I can find say that core is just a cut to the bone version of the firmware with minimal features and all of the driver defines. I have asked for a full list of what features are or are not included so I can be more clear, but I haven't gotten anything on it yet. Suffice it to say though, there are going to be some cases where flashing core means losing something that the pilot is expecting to be in the 4.4 firmware hex.
Please help me a lot.. I went through an unbelievable number of threads and unfortunately I did not find a solution. I have a Happymodel Mobula 8 - CRAZYBEEF4FR (FrSky). Vezre 4.4 works according to your instructions, but in this version the SPI-rx FrSky no longer works and as soon as I load the frimeware that supports SPI (4.0.0) I don't have the ICM42688P gyro again... So now either I have the fw 4.4 gyro ICM42688P working, but I can't control the drone, or I have the fw 4.0.0 communicating with the transmitter, but I probably don't fly much without the gyro either. Can you help me? Thank you in advance
I have this problem, with this small exception, yours says it's factory settings, what gyro model do you have, mine says - locked, do you have any idea how to unlock it? it is definitely not damaged because it worked before uploading the new version.
I have decent up-close eyesight but still use a cheap magnifying thing on a stand bought from our dear friends at Amazon. Now… which one of the three hundred components on this board am I looking for…😂🤣
lol, I literally have to touch my eyeball on things if I want to see them. I really do need one of those stands or a digital microscope for this kind of stuff. Its the small one, on the back, by the other small ones :p
When you load up the core firmware, do you see that MPU6000 in there when you run the CLI status? If so it for sure has one, but I will say vendors do swap them out pretty often so you may have seen any number of different gyros while running the core package. Whichever one shows up in the cli status while you have core loaded though is for sure the one you will want to use.
@@BaconNinjaFPV thanks for the great content - I am pretty annoyed I havent seen anyone else talking about this, It flew fine on 4.3 I was just flashing for HD OSD canvas
You my friend are a legend for putting this video up. Fixed the problem with my darwin 15a elrs. I couldnt get the accelerometer to work on 4.4 as I needed the elrs 3.0 so I wouldn't have to flash my controller just to fly this 2s tiny whoop. Not tested to see if anything else works, but so far its a great start! And I now have the knowledge to add the custom defines which I may need again! Thank you sooo much!
This doesn't only help those behind, also helps ourselves if we flash it again later 😆Great video there, makes this much more approchable for people who are new to compiling and debugging. I had a tinywhoop that I flashed to 4.4, it was basically unflyable, and yup on checking it out today the gyro was out. Just before I lodged the issue for it, I checked the discord and ran into mention of it (and also this video in the chat), so tried reflashing 4.4 today, and it was magically fixed! 💪
Thank you, and you are absolutely correct! It does make it easier next time we have to flash another one of these boards! Really glad to hear they got the target modified too. I was wondering how quickly that would happen after someone put in an issue on one....figured it might take a good while, lol.
@@BaconNinjaFPV Looking at the github issues for betaflight unified-targets , it looks like they are pretty quick... once the correct defines are identified it looks like they pretty much patch it straight away within a day or two, since it's a trivial task. The hard part is getting the information needed, which seems to be a lot easier now that the message is getting out (especially with the nice support link stuff to make it a copy and paste affair).
could you walk me through the steps you took, because although i read the gyro mpu6500 in the script, when flashed it still didnt fix the missing gyro in BF.
@@micsherwood4930 Even when you flash the "core only" build? If it's missing there, you probably want to double-check if your particular FC has a MPU6500 or not. If it does have a MPU6500 but isn't finding it with a regular cloud build, you want to make sure you are inputting both the GYRO_SPI_MPU6500 and ACC_SPI_MPU6500 as custom defines for the cloud build.
Thank you MBN. This video helped me in so many ways. It bothered me when you said that people on the internet don't like you....for whatever reason. I've been following you for a while, and in all that time your content is aimed at helping the community. The majority of your videos are you trying to help the FPV community, especially pertaining to technical issues, and you have never spoken ill of anyone. You have given me many reasons to appreciate you, and never one to dislike you. Don't stop being you MBN. 😎 Oh shit I forgot STAY GREASY 😀
I am so glad it helped you out!!! The thing about having a presence on the internet is that everyone is shaped by their own experiences and it is so much harder to see the person on the other side as a real human being. Some of those people's experiences are more friendly than others, lol. Its ok though, because I do this stuff so that people can get the help they need and learn to love this hobby and that is the important part for me :) Even if all I ever got were dislikes, I would still just keep on having fun and chugging along. It really does help to hear that other pilots get use out of the info though, because it just makes everything that much more worth it for me :) I really appreciate you!!!!
unfortunately back in those versions we didn't have any way to do custom defines without just compiling the whole thing on our own and generating a hex to import into the flasher :( Maybe give it a shot with 4.4 though and see if you can get it to work with some custom defines!
What board you have in that thing? I know this isn't isolated to just the darwin board I used for this demo of it, just any vendor who changes up a gyro and doesn't have their target modified first, but I would sure love to have a list in my head of some that are doing it for sure. Always helps when I see a question about something similar scroll by oh the beginner facebook groups!
@Bacon Ninja FPV it was the baby ape aio same one your using in ur video although it showed a gyro no matter wat onfig it kept just Flippin out wud not get off the ground
Dont flash unless you have a specific reason to... What if my specific reason was that I was following your budget build video and you told me to flash the most recent version of betaflight? All sass aside, thank you for the work you do for us!
ok, so it sounds like you flashed 4.4, lost your gyro, then hit reset? is that correct? If so, reset actually clears all of the custom defaults for your board so it basically unplugs all of the pins from the processor since nothing is mapped anymore :( You will want to get your board into boot loader mode and flash 4.4 again then start over with trying to get the gyro back using custom defines. It can be a real pain sometimes unfortunately.
@Bacon Ninja FPV yeah. I see that. I'll be finding someone to send it to. I'm in Knoxville so I have and a bunch of people that I can go to for help, but not till after the weekend
Well hopefully it is just this you have going on with it! I hadn't had it happen to me on any of the other boards I own until the Darwin showed up for a build I am doing...then bam, no gyro, lol.
@@BaconNinjaFPV I'll have to give it a try! This was a tinyhawk II that did it, also Matek target. Good to know since I've got a darwin tinyape on the way.
This video save my ass last night but after I get everything got my gyro back now I have six initials beeps and then the two instead of three beeps is there reason for this lol
You’re amazing!!! Tonight marks the second night that I sat for hours trying to figure out what got messed up when I put the new board in my TinyHawk 2 freestyle before I came across your life saving video. I’ve learned from my mistakes and the next time I have a problem my search is going to include bacon ninja. Thanks so much for all that you do!
@@BaconNinjaFPV I had a hard time figuring out how to get the board position and motors spinning the right way too because the board is for the TinyHawk 2 and the freestyle so I had to turn it 90 degrees which I don’t think I could’ve fixed without flashing. Unfortunately after I finally got all of that figured out and working right something happened that is causing it lose telemetry. As soon as it has power it finds telemetry and then instantly loses telemetry then finds it then loses it over and over and over till I get too annoyed and unplug it. It didn’t start doing till right around when I had everything else working right so no clue what I did…. I eventually gave up on it last night and haven’t tried again yet today. If you any ideas I’d love to hear them! Thank you!
I cannot get into bootloader anymore on 4.4 with no gyro and getting the windows message "device not recognised" each time. I suppose the incorrect BF 4.4 version messed up the bootloader software of my CrazyF411 AIO (Target MatekF411RX) Although. I can connect into configurator just fine, no way to connect into DFU. The ImpulseRC and Zadig softwares and reboots did not help. Tried configurator 10.9 and 10.8 to get back to BF 4.3 official and manufacturer's .hex. Would you have any more ideas or should I raise the issue on Github?
I finally got the bootloader working after disconnecting all uart devices, uninstalling all com devices and updating with STM32 driver manually. Lots of reboots in between and running ImpulseRC driver fixer in the end. This stuff is not straight forward ...
Yep that is excactly the same board I had to find it and type it in but worked great flew great then caught on fire on bench while doing some osd setup had about 12 flights on baby ape getting a mamba aio tomorrow will be installing that
My Darwin elrs just did same thing after flashing to 4.4. I originally flashed to betafpv1280 and got no gyro so then flashed to matek f411rx and got it back
nice! Yeah I think the Matek target is the one they recommend for that one on the website and lots of people have put in betaflight support tickets on it so they have that target nice and fixed up now :)
The Grease is so timely! Just built the jitterbug from your other video... PERFECT timing. Really appreciate it, sir! Coffee coming your way for all the help recently.
Very informative video. Haven't had issues, yet. This will save people headaches. 👍😎 I have an electronic microscope, and I use head mounted magnifying glasses. My eyesight is old and poopy. Just retired, to put things in perspective. 🧓
I hope it does save a few at least one extra headache, lol. Also, I envy your electronic microscope! I really do need to get one because my eye sight is poopy as well.
@@BaconNinjaFPV I got it as a Christmas gift from my kids. It's the Andonstar AD249S-M, very reasonable latency. Checked by a friend who does surface mount repairs. 👍🤓
you might double check the syntax and formatting in your custom defines line. I had that happen a few times when I was figuring out how to put it all in there and get it to work.
Dammit Bacon! I went through all of this with the DarwinFPV board you had in your hand last month.. Slightly confused, I did manage to work my way through it, and now I know even more for next time this happens!
lol, well at least I was only a month late! :p I actually had this issue pop up in the discord and we worked through it there, but coincidentally I had the exact same board in the mail while we were working through it over there. I figured there was no way I couldn't do a video on it when it everything just lined up like that, lol.
did you ever get it working? I know it took me a couple of days to see this :( If you followed along and it took everything as it should, that gyro should be showing up. You might try rolling back to BF 4.3 or 4.2 and seeing if that gets your gyro going again, although you will be missing some features like expresslrs 3.x if you happen to be using that version of the board.
You are very welcome! Hopefully we see most of the missing gyro, barometer, OSD, and flash stuff worked out over the next few months....and hopefully vendors start cooling it with mid stream hardware changes, lol.
Hopefully that is all it is! In other firmware versions where we didn't have the cloud build, boards doing this would have gone straight in the trash, lol.
Great Video. I have had this happen and I got around it by using configurator 10.8 to flash the 4.4 firmware. I then went back to configurator 10.9 before making any changes.
That is a nice way to do it too! I believe what that is doing is loading up the core only distribution since 10.8 doesn't have the cloud build options. That will at least get it running!
This video saved my drone. Thank you for what you do is great too see someone helping the noobs like me I’m pretty new too flying I’m loving it got me few drones and playing sim trying to get my skills up. anytime I have a question you always have a video out there with the info I need. Got a fan in me look forward too see what you do next.
This got me a few weeks ago. What a pain in the ass it was. It was the darwin as well. I have 2 of them. It's all good now. But again, what a pain in the ass.
I wish I had made it a few weeks ago!! I actually saw someone in the Discord have this issue with this particular board and I had just happened to have one on order for an Odonata build, so I figured I would just two birds one stone this thing. lol
@@BaconNinjaFPV It worked!! 🥳 thank you so much! U really explained this well and now I know a lot more about betaflight! The board I have is very new and hopefully now they will fix it for others 😎
Thank you Bacon! I bought my very first drone a half hour ago, hadn’t even gotten to fly it yet and flashed betaflight.. just kidding, great video bro! 😁
Thank You Bacon!!! My Tiny Ape Has Gyro & Acc once again! Just got it, was kind of getting frustrated till I watched your Video. Thank You from South Fla!
I know this is off topic but just wanted to let you know that something magical happened the other night. Def not where I wanna be but I know I'll get there now. Thanks for everything Bacon!
@@BaconNinjaFPV it was alot of things really. Being able to use my actual radio was huge! But your bat analogy and just thinking of the kwad like a UFO helped a ton too. I'm just glad I can say, hey I wanna fly between those trees and actually accomplish it. I'm so happy! Sky's the limit now. Literally.
Great video! Thanks for all the info. I was lucky enough to had a backup of all the configurations, so I just flashed the old firmware and restored everything, but now that I saw this video, I am calm to flash the latest firmware :) Thanks again
Dude, this is fantastic. Thank you so much for taking the time to make this! It took me way too long to give up trying to fix this on my own. Lo and behold, you had the answer and explained everything very thoroughly. Thank you!
