Thank you Joshua Bardwell! I just had this problem after a couple of months of flying fine with my Omnibus F4 Pro V3 board. I was at my first ever race and threw a SD card in the FC. It seemed to be at about the same place on the course each time that the quad kept jittering and pitching backwards until it dropped and crashed. It only took 2 practice rounds and 2 race rounds until your video clicked in my brain. After I finally turned off the DMA, I was finally able to finish a race! You saved my sanity (or what was left at that point).
Thanks for this! Just installed the Matek f405 in one of my quads and was super dissapointed about how BAD it flew. Went home and started looking around in rcgroups and found the link to this video. Tried it out and sure enough she rips balls now
Thank You Sir !!!! I have been fighting this very problem for weeks. I will be going back to my scrap pile and recovering some F4 boards I thought might be bad. Thanks for all the information you share and the work you do.
I just had this problem with my Wizard X220s, saved me a lot of hassle since I didn't get any useful responses at RCgroups since I'm a bit late to the Wizard craze. Thanks!
funny story, i have the original omnibus and the original board had an issue from factory motor 3 was 4 and motor 4 was 3 on the motor pins. so after updating to BF3.1.7 i tried to fly and it flipped over, i checked the motor rotation, prop placement, board orientation, accelerometer calibration just when i was ready to put it into a hydraulic press, crack a beer and smile i went into the motors tab, and sure enough M1 was right, M2 was spot on, spin up motor 3 and would you believe motor 4 spun up, and with that said motor 4 was in fact motor 3. i was so confused. so i went back and watched Bardwell's video on resource mapping and didnt even have to take it apart to move that motor signal wire. i was a happy camper! thanks Bardwell!
bingo! been trying to figure this out for days. my flytower has the omnibus f4 with on board SD. First time I put a card in my quad slightly rolled left then darted to the ground. thanks for the tip. you the man
Thanks Joshua, very useful to know. I have both F3 and F4 Omnibuses (Omnibii?) and will try the fix on both. I'm not getting those sorts of jitters, I'm getting involuntary extra rolls after a commanded roll and occasional spins of death so I'll give it a try.
yes!!!!! finally someone that has this problem also, been trying to figure this out. looked everywhere and nothing. I got so excited about it I didn't even get to watch the video yet hahaha. told the wife and she has seen it do it also and started to do the shake hahahahah. thanks for the video, I'm going to watch it now hahaha
Yeah I pit mine down to 1k like he said, ran ok for a few flights. then started to do it again. but mine never crashed tho. Just shook like hell and started to fly up when shaking really bad for like 10 sec, then it would just stop and fly fine again for a few flights. but I don't have that prob no more bc last week it took a total shit on me and wouldn't turn on at all, all lights went out, checked everything and couldn't find what happen. sooooo I said f-This and bought a bettaflight f3 last Thursday from my ppl at racedayquads and they had it to me by sat morning, and I live in pa. love it, very easy to do. clean. best pid' s and gyros on black box I have ever had.. not even joking about that.
Todd Beal I just changed out a dys f4 AIO to the Matek f405. dys f4 was horrible. So far Matek seems to fly pretty good and I wanted to experiment with 32k/16k
Yeah I haven't got to that fc yet. but I know the only problem I have with any of there boards is the sodder pads rip of so easily. I'm not sure how that fc is, but I'm just saying for the pdb 3 of them have done it for me, reason why I went with the f3, basicly all in one
only thing I don't like about the f3 is where the black box card reader is on it, sucks trying to get it out or put it in. have to use needle nose pliers to get it out. take the one uart out or move that compositor that's in front of it to the back of it.
Thanks for this. I have two identical F4 Omnibus builds and one glitches out randomly during flight. I recently swapped from 4-in-1 to individual ESCs and a PDB (which routes signal wires), and I thought it might be noise getting to the signal lines. I will be testing this fix when I get home.
I can't test this fix as I'm currently grounded, due to a flip out in air mode but my copter was doing this before I began trying to tune it out. I managed to get it to quieten down a lot by reducing the D on P & R but when in air mode whenever I try to do a flip or roll it flips out. But this didn't happen in Acro mode, which I thought strange. Once the new Chameleon frame arrived I will test. Thanks Joshua, it is appreciated.
Is it possible this could affect the f3 Omnibus board as well? because as of right now I'm fighting what looks to be the same issues... Never seen it b4 and I'm scratching my head... Going to try is and see what happens :)
Thanks for the video. My issue was caused by trying to power the LED strip through my flight board. Thinking bad LED strip or faulty regulator on my FC. was driving my crazy and was the last thing I check of course...
Hey I have a problem where my drone is all good connected to the computer, the motors spin no desync at all, but as soon as I use the transmitter and arm it at first it seems ok but when you push the throttle up motors go crazy also they overheat real quick and the drone turns in yaw direction like it jitters, does anyone know what the problem is ( fyi i changed the motors and escs, I updated firmware but nothing works still the same problem) Thank you
Have you checked the 5v output on your omnibus f4 pro? I checked the voltage on my motor 1 pins and am only showing 4.38v using a fresh 14.8v battery. Only wires that are on the board are my + and - going to my battery, no current wire or anything else, I was just checking my new board. Will this cause a problem? Do I possibly have a defective f4 board?
I flashed Betaflight replacing clean flight on a brushed micro quad and it said success at the end of the flash. I tried to connect immediately after that and it wouldn't connect. Now I can't get it to boot up. Only the blue light comes on solid now and no red flashing light whether I plug in battery or USB. It will not boot up and I can't reflash either. It's on the Eachine EX 110. It was flying OK before the flash but I like Betaflight better and was told that any controller running Cleanflight can be reflashed to use Betaflight. I can't even flash Cleanflight back to it. Is it bricked?
how can i check if my motors ports are working on Omnibus F4 betaflight(my motor stopped and the esc is ok,motors ok,but my f4 dont show motor on bl heli and wont spin on betaflight pls help.
Hooked up my board, everything works perfect except ibus. It will send signals intermittently. I have no idea what is wrong. Evolution tx, ia6c rx. Why won't this work? I receive bat voltage through the controller so I know they are synced. Any ideas.
Sad thing is, most FPV'ers are too young to really appreciate what you're saying there! PS I had a SoundBlaster Pro. It was awesome but cost me $400 back in 1991 LOL!
Hahaa... yeah my comedy is not for people under 30... unless they've been molested or had cancer. I had a GUS Max, which worked with all the awesome PC Demoscene stuffs, plus my beloved fasttracker II. I eventually ran two (while they were still ISA!) under slackware for multi-track recording which barely worked sometimes. That was some difficult DMA jenga!
mistercohaagen can you imagine millenials coping with dip switches, I/O jumpers, ISA and EISA? and modifying ini files to cope with the changed base I/O addresses? LOL.
My PikoBlx FC in my self constructed 95mm quad (The Hawk) has a similar DMA conflict! Although I am having installed a 4 in 1 ESD which is DSHOT600 capable I cant use it because: - 1st I am flying all my copters with my Aurora9 and ppm RX's (there is no serial RX for the Aurora on the market.??..) - 2nd I have a LED strip installed and would need exactly resource remapping for motor1 to the LED pin on the PicoBlx to enable DHOT600 This is why I have configured the FC back to Multishot.....
Hi Joshua. I'm struggling with an issue. I'm using 317 betaflight. I changed resources for 3 and 4 motor with no problem. I'm using omnibusf4 for a micro f2c. I have firmware updated for my frisky xmplus. Board rotated 90 to the left. I set acc and gyro to 270. So...i arm but motors don't spin up even though it is set to. I give throttle and can hover. I hover for a few seconds but then it shoots forward and upside down crash at hover throttle. Any ideas?
Thanks Joshua for this info. I have a question for you. One of my builds has an Omnibus F3 that exhibits the same tendencies. The only thing it lacks from the example given in the video is the actual drop out. So I guess I'm asking if this has been reported on the F3?
Dear Joshua, your video's are very educational and intersting to watch. Woul like to give you an extra thumbs up on that. However I am missing 1 topic. I know you are quad person but many are trying to build a Tri with the F4. I watch and read all there is about re-mapping sources but ther is alos talk of analog and digital servo's and timers etc. Could you please show us how to do the tail servo. In addition: The Omnibus F4 can handle up to 8 motors but does not have enough fysical connection options ? Why is that ? Hoping for your expert answer... Greetings and good luck to you.
I would say, if you want to build a tricopter, you have to run Triflight, David Windestal's fork of Cleanflight. It has special options for tuning the tail servo that makes a tricopter fly as good as it possibly can.
what fix would you recommend for my emax magnum stack that runs the omibus f4 . It connects fine but when i try to flash the FC it doesnt show it on the com port. IS this a common problem with this board? thanks and great videos as always.
I have a question. I have a airbot F4 micro flight controller. and it will not acknowledge the throttle signal unless I plug in a USB and then it will acknowledge and stay working. but that is the only way I can fly , I have to plug in the battery and then plug in the USB to my quad and then unplug the USB and then I can fly. I consider myself halfway knowledgeable, but I am not sure why this is happening.
Hey Joshua great video. Was this the bug you spoke of in the previous video "Death of F1 boards." I'm doing a build for a customer and I suggested this board to him. I hope I didn't steer him wrong. I also fly omnibus.
I had that moment with my quad with omnibus f4 in it. Instead of that moment, I got problem with its GYRO then. After it crashed, the gyro is error by seeing it in my goggle. I couldn't arm the quad and the message "no gyro" appeared in gogge display. I tried restart the quad by plug-unplug it then it works again. Can you guys helm me? What makes it so? That makes me afraid to fly my quad again before i could found the problem.
Running official 3.3. I freefell from 150ft due to my inputs being ignored after a throttle punch (within 100 feet), it continued on for a couple seconds till I hit the failsafe(Qx7) I then attempted to rearm and "catch" it did rearm but too late, surprisingly nothing broke, not even a blade. Osd didn't work and only displayed random letters. Bb did not record as I did not insert SD card. I reflashed to 3.25 and strapped the drone to a 4X4 and gunned the hell out of it with tons of throttle stabs- no failsafes/glitch, osd works. Using a Hobbywing F4 with OmnibusF4SD target, Dalrc engine with 3A BEC, 5v feeds 200mw VTX and XM+ RX, cam powered from Vbat. Going to attempt flight tomorrow, hoping it was a firmware bug I read on RC groups someone with an OmibusF4 and 3.3 had exact thing happen, someone wrote it off as a tx/rx glitch, I'm not buying it, I couldn't disarm, but my switch failsafe worked? I have the RX set to "no pulses" and my FC RX failsafe is "lead balloon mode". Weird stuff, frightening too because I had around 15 seconds of no control over my quad. If she flies sweet with 3.25, I'm giving 3.3 a hard pass.
Just thought of something, bb faulted due to no sd card, wondering if onboard flash size is too small and somehow it tried to log data and freaked out the board due to insufficient memory causing some kind of conflict. But isn't BB flash separate from EPROM? Maybe just a firmware update glitch?
I figured that. I'm going to eat my words, but I DO think it was a RX issue, I was flying around, punching out a little bit, then went off away from me and at low throttle, and boop! failsafe- it STILL could be another component such as noise in the system since I'm running beefy motors. Oh well, I'll throw in another XM+ rx and see if that solves my issues, I'ts directly soldered to the board via stubby pins and I made sure the joints were nice and shiny. I also flew old blue that is the same frame/similar setup and had zero issues- this will be the first bad FRsky RX go bad on me- also, antennas are tightly connected, so that isn't it. Since it's down, I downloaded Butterflight and see if the hype is real.
Joshua with the Asgard F4 V2 FC I have a few issues. Spektrum RX & OSD The FC came loaded with BF OMNIBUSF4 3.0.1 1st issue you already answered for me I did get UART6 to 3.3v by removing the default bridge on 5v and bridging the 3v 2nd issue is UART6 must be inverted or opposite of what my DSX Rx likes because its not recognized. I downloaded official BF 3.1.7 target OMNIBUSF4 and flashed it and still UART6 does not recognize RX Somehow on GitHub I found downloaded and flashed a build by Boris.B BF 3.2 #1253 target OMNIBUSF4 I now am in business my RX is recognized and I finished my build but now the oddity is BF configurator can not detect my battery voltage 0.0v and my OSD is there but no data. No matter what I change BF to display in the OSD it will change in the configurator but does not reflect the change in my goggles. so my issues stand as: when I am on 3.1.7 everything works with OSD and Voltage reading does show in BF configurator but RX is not recognized when I am on 3.2 build #1253 my RX now works but my OSD gets no data and BF configurator shows 0.0v battery. I don't now how to get 3.1.7 to change UART6 from inverted to non-inverted or vise-versa. The commands I found online say syntax error when I try them. I know your busy but was wondering what you would do if you were me? Is Boris.B someone that can be reached if need be? Thanks Jim..
You are running 3.2, which is a pre-alpha build. It's not surprising that some features don't work. I suppose vBat and OSD are not working in that build and target. That's the risk of running a pre-alpha build.
Thanks, but a few days too late for myself. my quad flew great until I tried to log some blackbox. that's when it flipped out now the board won't power up, one green led turns on but fades in very slowly, no connection to the computer, the casing to the SD card holder heats up.
+Casey Pinochi casing to the SD card holder heating up means you have a short. On the BFF3 if you fly without an SD card installed the casing can be crushed and contact Vcc. The board is likely dedtriyed.
Boards are definitely toast, but the casing was intact, happened to 2 boards only after actually logging BB(boards may or may not have been clones) guess that's what I get for trying to go cheap, buy quality, spend now, save later, lol
I have an omnibus f4 OSD AIO and it did this crap this weekend. but mine doesn't have an SD card slot on it.. any ideas? I really hate this board as I can't get ESC pass-through to work nor can I flash the firmware. May just replace it with something better.
lol I've had omnibus f4 pro for while and like it, I did have either flight controller go bad or was fault or esc burning out and #2 motor input on board quit working. wish I knew how to fix it
oh shit my bff3 is doing the same shaking but its stops and im able to recover and not crash do you think i can fix my problems with this fix? its doing it ramdom and 2 to 3 times in a pack
Hello! I really like your videos and feel like you are the best person to learn from! Your new vids are awesome keep flying! :) However I got an issue with my F4 pro v3 flight board. My drone crashed and I had no idea why. I tried to plug in battery and something started smoking. I found that it is the U4 unit. Next to it there is a C7 resistor and it came of somehow (at least one "leg"). I soldered it back carefully and tried to plug it in again and it started smoking again. I removed the burnt U4 unit. Now I am wondering what funcion will I missing. Maybe you know that (?) :) The FlightB turns on and looks like its still working.
Better to not get omnibus. davidhkblog1.blogspot.com/2017/06/fixing-omnibus-f4-pro-over-heat-and.html?showComment=1541408154194&fbclid=IwAR0DAE2uii9O1eEEXnDitEB6WSsGw1E3e22xpCHsfqDY9nb8yP7uv2E_HJM#c6956157706785268210
Hey Joshua so just put new motors on my build and I am getting a lot of jello in fpv cam I checked and all components in build and they seem to be secure... what parameters in bf can cause jello just wondering how to possibly tune it out... jello seem to be the worst with throttle punches
Josh, I have this in version 3 but cannot get the buzzer to work. It is enabled under the configuration tab. Can you help please? Dont want to fly with a buzzer.
Joshua Bardwell I installed a buzzer on the buzzer pins and connected to a switch on my taranis, aux 3! However, the switch works, the blue light on the FC blinks but no sound.
If the FC light is blinking, then everything is working except the buzzer. Either the buzzer is broke, the FC is broke, or the wiring isn't right. Make sure you bought a self-driven piezo buzzer and not a passive buzzer.
Hi Joshua, what would you expect to see in a blackbox log if this was happening? I'm getting the same shaking and inversion, but logging shows heavy rc command inputs that aren't coming from me! Happy to share the log :) Thanks!
Ok that's not happening in my case, the rc commands seem to go crazy at the time of the issue and there don't seem to be any gaps in the log- its on a Matek F4. I don't think it could be a faulty IMU if the rc commands seem to match the quads change in attitude, any ideas what else it could be? :)
Transmitter gimbals borked. 1. It's not failsafe because rcCommand would freeze up. 2. It's not a bad gyro because you see rcCommand freaking out. Therefore: it must be that the FC is getting garbage data from the receiver. Possibly the receiver is borked but especially with serial protocols that isn't likely. So the most likely cause is your gimbals are borked. Check the output monitor screen on your transmtiter.
Thanks, I'll check them out - its a brand new Taranis X7 though! If you have some time would you be able to look through the two logs please? Both are about 30 seconds long , thanks! I don't have video of the flight unfortunately
Have you ever come across this issue on a board without an sd slot or with blackbox logging turned off? I am experiencing the same thing, minus the crash, with a DYS f4 aio.
I have an ARTOWER F4 PLUS 2.0 Flytower Omnibus FC... which lead me to this video. I'm currently experiencing an issue where the copter just "drops dead" during hover testing at random times. Motors will just stop and bam, right to the ground it falls. All lights remain on. It will not re-arm either. I've tried connecting it to the computer after an event like this occurs and it's dead to the world. I tried blackbox logging just to see if it would tell me anything. Interestingly enough in betaflight 3.2.0 with this board and sdcard_dma = ON, I do not get any shaking at all, just figured I would mention that. Presence of a microsd card or not, however, makes no difference with this "sudden stop" issue I'm having. Do you have any advice on how I should debug this? Basically I feel as though the FC is crashing/freezing.... I am going to disable DMA tomorrow and see what happens, but remember, I haven't even been using the blackbox except once to test.
Hmm... I've already replaced the receiver; and it's wired up to a 3 pin connector that seems to fit snugly. Every time this happens the receiver light is fully on and responsive to the radio being turned on/off. I should have mentioned that. Thanks for the fast reply! I don't know what my next step would be. Would a failsafe event though prevent me from connecting it to betaflight until reboot/restart of the quad? That is what struck me as strange. I should test this...
For science, just now I tried powering it on, ensuring I was bound, and unplugged the receiver from the copter entirely. Surely that would cause a failsafe event, total and complete loss of receiver. Connected right up to betaflight with no problems. There is something going on with this FC and I can't put my finger on it... I wish there was a way to have more detailed logs that might lead me to what's going on.
G'day Josh, thank you for another informative video. I've been banging my head against this issue for the last few days trying to figure out if it's worth keeping the Omnibus F4 Pro I have or if I'm better off throwing it in the garbage. I have been reading all over the net and it is looking more and more like the DMA conflict issue could be a problem with the F4 chip and may not be something that the devs can fix. Have you heard any more info on these issues and have you had it occur at all with other F4 boards like the Holybro or Matek F4s?
With DMA off I'm still getting some funny behavior with random and quite infrequent glitching of the motors. Something like 1/10th of a second full or no throttle glitch making the quad jump or sink. If I turn logging off completely this glitching disappears. It's super annoying! Just had a look on the Matek site and it looks like they are confirming it as an issue on the F405 (www.mateksys.com/?portfolio=f405-osd). This is a pretty major issue. I'm surprised it's not getting more attention. It's worth noting that I've been using a Flip32 F4 special edition from RTFQ that has a data flash chip instead of a SD card for logging and in 3-4 months of flying it I have never had any issues whilst running both Dshot600 and logging concurrently. I wonder if the Holybro Kakute F4 is also immune to these issues due to using a data flash chip instead of the SD card?
I haven't ever experienced the issue...yet. Has anyone reported this happening on an F3 Omnibus? I could turn off scard_dma just to be safe, I suppose.
Im having a issue with Acro mode. Stable and Horizon mode work perfect but acro will fly good for a few seconds the the stick inputs will randomly change. Pitch forward will roll left, pitch backwards will pitch forward and so on with the rest of the stick inputs. only thing that does not change is yaw and thrust. Sorry I am a newbe and this is my first build.. PLEASE HELP
I literally can't think of a single thing that would cause this. Find a more experienced pilot who can get more information about what is going on is my advice :-)
Hi JB I hope U can help. I got problem with my OSD all screen shows VVVVVVVVVVVVVV omnibus F4 v3 SD betaflight 3.2 ich thing I put on change VVVVV to different character , in the background I can see camera signal any idea ?
Hey JB!! My issue is not entirely related to this video, but I'm hopeful you can help. I just received the Furibee Darkmax 220 with the Flytower Omnibus F4 SD FC. The receiver binds to my Taranis just fine, but I get no response on the Betaflight receiver tab. All the setup seems correct: SBUS selected, serial RX mapped to UART1 per the instructions... Any ideas? Re flash the newest BF version? Try a different UART? Many thanks!
If SBUS is selected and serial RX is on the correct UART, then it should work. If it doesn't work, then double check the wiring. Then if it still doesn't work, start re-examinign your assumptions. Do you definitely have an SBUS receiver? Is UART1 definitely the correct one?
Hello! I have the darkmax and had the same issue. You need to turn off UART1 and enable UART6. It is incorrectly configured from the factory. I hope this helps.
I have this Board and read a couple weeks ago about the DMA issue but the issue I have is that I turn SD card and black box on but when I go into black box it doesn't give me the SD card option just either to an onboard log or a third part device but I know there should be a third option, any ideas please?
Pardon me for not doing my work XD So the limit for logging is 4gb. And so my problem probably was the bad card. I also set dma of and down for 8k logging to 1. well see now.
I just installed the omnibus board In to my quad and was flying but it randomly falls out of the sky I will hear 3 beeps then it will just disarm and it happens randomly. What’s the problem? It’s not like this problem it just beeps and then disarms? And I did everything in this video I have no idea?
i have that flight controller and something similar happened to me once a while back. i thought it was a desync or something but it hasnt happened since so i forgot about it. anyway thank you for the tip i will do this!
I''m using the Kaktute F4 AIO controller and i'm getting the same problem, however i'm writing to the built in memory instead of an SD Card. Also my video and OSD will cut out as well. This does not happen when blackbox is disabled!!!! Also there is no SD_DMA options in the CLI, probably as the board doesn't have an SD reader.
I agree that the sdcard_dma option only appears if you have an SD card reader. If you are using Dshot, switch the Multishot and that should resolve any DMA conflict with the motors.
Can someone help me, i added the dys omnibus f4 flight controller to my drone and i have an xm+ receiver bound to my taranis qx7 and in the receiver tab on betaflight the stick values wont move. Ive gone into the ports and tried changing somethings but to no avail.
It works fine up to 10 to 15 log files. If I don't format my sd card after 10 to 15 logs, it stops working and just creates corrupted log files. The log files look empty in Blackbox Explorer but they actually have some data inside. If I open them with notepad I can only see UUUU characters and no binary. I have tried it with 2 microsd cards. My logging rate is 250Hz and the cards are class 10.
Does anyone have an answer to get ibus on the omnibus F4 pro V2. I know blue falcon project has a video but it doesn't work for the pro. I would prefer not to run ppm. Pppplllease Help
That's exactly the reason why there are DMA priorities you can set for each stream. However it seems developers don't necessarily know how to use those.
Well if you are so smart, start making pull requests. This is an open source project and everyone is doing the best they can. The use of DMA to control motors is relatively new with the advent of Dshot so it's not surprising that there are some growing pains. Or maybe the vendor just screwed up the mapping of DMA channels on this particular board? Remember that the mapping of timers and DMA channels to resources is not controlled by the BF devs and varies from board to board.
Argh. Sorry... I guess I came off a little defensive. It always bugs me when somebody is critical of these guys. They work so freaking hard for basically no concrete reward, and since it's an open source project, I can't help but feel that anybody who is critical and who then doesn't contribute is being really hypocritical.
Joshua Bardwell it didn't meant to insult or decrease the importance of contributors to the project. I highly value open source projects, the problem in this particular situation is that there is no equal amount of HW devs contributions as to other higher level portions of the code. BF is complex system especially because it's baremetal and everything have to coexist. I had already issues with DMA priorities on the BF before: essentially ADC was taking over UART TX or RX and the result was many corrupted packets. Unfortunately devs ignored my message on that.
If the DMA motor control usage is new to DSHOT, then another potential work-a-round might be to cut back to multi-shot. Just a wild guess. Perhaps useful for those who need the most reliable logging. Just read the github postings on the issue. Seems the issue may be a CPU bug(fault!), triggered by more than two simultaneous DMA operations. If so the only fix possible is to never ever use DMA for more than two simultaneous tasks/jobs, in the firmware. So the new DSHOT is exposing this issue, because it's (presumably) an additional use of DMA in the system. Hmm.
@Midwest FPV mine turned out be simple. The motor direction was wrong. It's not enough just to have 2 CW and 2 CCW. The directions of spin must match what you see in Betaflight. But you probably already know that....There are quad groups on Facebook and they are good about answering your questions. Squadrone is one
I'm watching your flight tutorial for few days my doubt us that can learn how to fly with my phone with same for free rider. it is app version there it two joystick on phone screen and not with a radio
You will learn to fly a simulator on your phone, but thats far away from real fling with a transmitter in your hands. Try to play simulators at least with a transmitter, this will really teach you how to fly.
mine doesn't crash just shakes crazy on throttle ups. soft mounted fc and replaced motors with brotherhobby 2206x2450kvs and it stopped it. hmmmm motors cause vibrations?
ive builts 5 betaflight f3 quads lately that does somewhat the same. all 5 drop the back left motor on 100% throttle. tried fw all the way back to 3.0. diff escs and firmwares. diff motors.
Thank you Joshua Bardwell! I just had this problem after a couple of months of flying fine with my Omnibus F4 Pro V3 board. I was at my first ever race and threw a SD card in the FC. It seemed to be at about the same place on the course each time that the quad kept jittering and pitching backwards until it dropped and crashed. It only took 2 practice rounds and 2 race rounds until your video clicked in my brain. After I finally turned off the DMA, I was finally able to finish a race! You saved my sanity (or what was left at that point).
"and now your copter won't crash any more"
That's a bit optimistic. :D
LOL.
Joshua Bardwell would this be something Boris and the Betaflight team could sort out in the future firmware updates?
Thanks for this! Just installed the Matek f405 in one of my quads and was super dissapointed about how BAD it flew. Went home and started looking around in rcgroups and found the link to this video. Tried it out and sure enough she rips balls now
Thank You Sir !!!!
I have been fighting this very problem for weeks. I will be going back to my scrap pile and recovering some F4 boards I thought might be bad.
Thanks for all the information you share and the work you do.
I remember looking for this problem a few months back on your slack. had it last night once but not every time I did a BB log. thanks for the help!
thumbs up for the flip out impression at 0:45. It seems silly, but it really helps describe the situation and is very informative.
Thank you Josh for this little gem of information. This may have saved me a heap of head scratching.
I just had this problem with my Wizard X220s, saved me a lot of hassle since I didn't get any useful responses at RCgroups since I'm a bit late to the Wizard craze. Thanks!
Me too now can't get it to arm
funny story, i have the original omnibus and the original board had an issue from factory motor 3 was 4 and motor 4 was 3 on the motor pins. so after updating to BF3.1.7 i tried to fly and it flipped over, i checked the motor rotation, prop placement, board orientation, accelerometer calibration just when i was ready to put it into a hydraulic press, crack a beer and smile i went into the motors tab, and sure enough M1 was right, M2 was spot on, spin up motor 3 and would you believe motor 4 spun up, and with that said motor 4 was in fact motor 3. i was so confused. so i went back and watched Bardwell's video on resource mapping and didnt even have to take it apart to move that motor signal wire. i was a happy camper! thanks Bardwell!
Thank you so much for responding to all of my comments. You are the best!
bingo! been trying to figure this out for days. my flytower has the omnibus f4 with on board SD. First time I put a card in my quad slightly rolled left then darted to the ground. thanks for the tip. you the man
0:46 That moment you get a stroke
Thanks Joshua, very useful to know. I have both F3 and F4 Omnibuses (Omnibii?) and will try the fix on both. I'm not getting those sorts of jitters, I'm getting involuntary extra rolls after a commanded roll and occasional spins of death so I'll give it a try.
Nice! thank you (I'm the one who wrote you that super long email about this a few days ago)
Yep. It was your email that finally inspired me to make this video.
Joshua: Quick CLI tip: Up-arrow cycles through previous commands so you can just edit instead of having to retype everything.
yes!!!!! finally someone that has this problem also, been trying to figure this out. looked everywhere and nothing.
I got so excited about it I didn't even get to watch the video yet hahaha. told the wife and she has seen it do it also and started to do the shake hahahahah.
thanks for the video, I'm going to watch it now hahaha
Dude, my quad that I just installed a Matek f405 in was totally useless till i turned dma off.
Yeah I pit mine down to 1k like he said, ran ok for a few flights. then started to do it again.
but mine never crashed tho. Just shook like hell and started to fly up when shaking really bad for like 10 sec, then it would just stop and fly fine again for a few flights.
but I don't have that prob no more bc last week it took a total shit on me and wouldn't turn on at all, all lights went out, checked everything and couldn't find what happen.
sooooo I said f-This and bought a bettaflight f3 last Thursday from my ppl at racedayquads and they had it to me by sat morning, and I live in pa.
love it, very easy to do. clean. best pid' s and gyros on black box I have ever had.. not even joking about that.
Todd Beal I just changed out a dys f4 AIO to the Matek f405. dys f4 was horrible. So far Matek seems to fly pretty good and I wanted to experiment with 32k/16k
Yeah I haven't got to that fc yet. but I know the only problem I have with any of there boards is the sodder pads rip of so easily.
I'm not sure how that fc is, but I'm just saying for the pdb 3 of them have done it for me, reason why I went with the f3, basicly all in one
only thing I don't like about the f3 is where the black box card reader is on it, sucks trying to get it out or put it in. have to use needle nose pliers to get it out.
take the one uart out or move that compositor that's in front of it to the back of it.
Who's my buddy? Thanks, Bardwell!
Thanks for this.
I have two identical F4 Omnibus builds and one glitches out randomly during flight. I recently swapped from 4-in-1 to individual ESCs and a PDB (which routes signal wires), and I thought it might be noise getting to the signal lines. I will be testing this fix when I get home.
awesome as usual joshua, currently installing two of these FC's so good to know before the first flight.
I love the way you say flip out
keep up the good work dude
An excellent oscillation impression!
I had this issue with my LUXv2, thanks for the video.
I can't test this fix as I'm currently grounded, due to a flip out in air mode but my copter was doing this before I began trying to tune it out. I managed to get it to quieten down a lot by reducing the D on P & R but when in air mode whenever I try to do a flip or roll it flips out. But this didn't happen in Acro mode, which I thought strange. Once the new Chameleon frame arrived I will test. Thanks Joshua, it is appreciated.
DMA CONFLICT!!!! What are we, back in the i386 days? are we setting IRQ jumpers next ? Very interesting issue.
my matek f405-osd fc has got the same harlem shake feature.. thanks for sharing, hope it's gone now :-)
Is it possible this could affect the f3 Omnibus board as well? because as of right now I'm fighting what looks to be the same issues... Never seen it b4 and I'm scratching my head... Going to try is and see what happens :)
Easy to find out right?
Thanks for the video.
My issue was caused by trying to power the LED strip through my flight board. Thinking bad LED strip or faulty regulator on my FC. was driving my crazy and was the last thing I check of course...
Hey I have a problem where my drone is all good connected to the computer, the motors spin no desync at all, but as soon as I use the transmitter and arm it at first it seems ok but when you push the throttle up motors go crazy also they overheat real quick and the drone turns in yaw direction like it jitters, does anyone know what the problem is ( fyi i changed the motors and escs, I updated firmware but nothing works still the same problem) Thank you
Can you turn it off for the UART:s as well? What BF version?
Have you checked the 5v output on your omnibus f4 pro? I checked the voltage on my motor 1 pins and am only showing 4.38v using a fresh 14.8v battery. Only wires that are on the board are my + and - going to my battery, no current wire or anything else, I was just checking my new board. Will this cause a problem? Do I possibly have a defective f4 board?
Hard to say. 4.38 is low enough that some 5v accessories will have problems. I wouldn't use the board until that was fixed.
thanks for sharing so much essential infos!
I flashed Betaflight replacing clean flight on a brushed micro quad and it said success at the end of the flash. I tried to connect immediately after that and it wouldn't connect. Now I can't get it to boot up. Only the blue light comes on solid now and no red flashing light whether I plug in battery or USB. It will not boot up and I can't reflash either. It's on the Eachine EX 110. It was flying OK before the flash but I like Betaflight better and was told that any controller running Cleanflight can be reflashed to use Betaflight. I can't even flash Cleanflight back to it. Is it bricked?
how can i check if my motors ports are working on Omnibus F4 betaflight(my motor stopped and the esc is ok,motors ok,but my f4 dont show motor on bl heli and wont spin on betaflight pls help.
When you plug in the XT60, pay attention to the motor tones.
ruclips.net/video/_hkzm8ZXsxE/видео.html
Hooked up my board, everything works perfect except ibus. It will send signals intermittently. I have no idea what is wrong. Evolution tx, ia6c rx. Why won't this work? I receive bat voltage through the controller so I know they are synced. Any ideas.
DMA conflict? That's what you get for running a SoundBlaster. Get a Gravis Ultrasound!
Sad thing is, most FPV'ers are too young to really appreciate what you're saying there! PS I had a SoundBlaster Pro. It was awesome but cost me $400 back in 1991 LOL!
Hahaa... yeah my comedy is not for people under 30... unless they've been molested or had cancer. I had a GUS Max, which worked with all the awesome PC Demoscene stuffs, plus my beloved fasttracker II. I eventually ran two (while they were still ISA!) under slackware for multi-track recording which barely worked sometimes. That was some difficult DMA jenga!
mistercohaagen can you imagine millenials coping with dip switches, I/O jumpers, ISA and EISA? and modifying ini files to cope with the changed base I/O addresses? LOL.
Simon Wallace or typing on a real keyboard beyond the letters "w, a, s and d"... no not really.
I had the same AWE32 for about 10 years until I got my first AMD K7, no ISA. Time for an Audigy!
My PikoBlx FC in my self constructed 95mm quad (The Hawk) has a similar DMA conflict!
Although I am having installed a 4 in 1 ESD which is DSHOT600 capable I cant use it because:
- 1st I am flying all my copters with my Aurora9 and ppm RX's (there is no serial RX for the Aurora on the market.??..)
- 2nd I have a LED strip installed and would need exactly resource remapping for motor1 to the LED pin on the PicoBlx to enable DHOT600
This is why I have configured the FC back to Multishot.....
Thanks for the video Joshua. Does this affect the v1 Omnibus F4 that does not have an SD reader? The V1 has onboard memory for blackbox. Thanks
I'm not sure. It can affect multiple boards, I have just heard the most about it from Omnibus F4 users.
Hi Joshua. I'm struggling with an issue. I'm using 317 betaflight. I changed resources for 3 and 4 motor with no problem. I'm using omnibusf4 for a micro f2c. I have firmware updated for my frisky xmplus. Board rotated 90 to the left. I set acc and gyro to 270. So...i arm but motors don't spin up even though it is set to. I give throttle and can hover. I hover for a few seconds but then it shoots forward and upside down crash at hover throttle. Any ideas?
Thanks Joshua for this info.
I have a question for you. One of my builds has an Omnibus F3 that exhibits the same tendencies. The only thing it lacks from the example given in the video is the actual drop out.
So I guess I'm asking if this has been reported on the F3?
I'm getting spins of death on 2 of my Omnibus F3 quads so I'm going to try this fix out on those too. We'll see how it goes.
I suppose it's possible but it was specifically mentioned on the F4. Anyway, turn sdcard_dma off and if that fixes it, you diagnosed the problem.
Just checked all of my Omnibus F3's and they all have sdcard_dma off by default. Oh well.
Dear Joshua, your video's are very educational and intersting to watch. Woul like to give you an extra thumbs up on that. However I am missing 1 topic. I know you are quad person but many are trying to build a Tri with the F4. I watch and read all there is about re-mapping sources but ther is alos talk of analog and digital servo's and timers etc. Could you please show us how to do the tail servo. In addition: The Omnibus F4 can handle up to 8 motors but does not have enough fysical connection options ? Why is that ? Hoping for your expert answer... Greetings and good luck to you.
I would say, if you want to build a tricopter, you have to run Triflight, David Windestal's fork of Cleanflight. It has special options for tuning the tail servo that makes a tricopter fly as good as it possibly can.
Does KAKUTEF4 have this problem? As you may know, it has a built-in 128Mb chip for Blackbox logging, so I wonder if that would solve DMA conflict.
+Alex Docasar I'm not sure.
what fix would you recommend for my emax magnum stack that runs the omibus f4 . It connects fine but when i try to flash the FC it doesnt show it on the com port. IS this a common problem with this board? thanks and great videos as always.
Download the ImpluseRC Driver Fixer app. Run it. Push the bootloader button on your FC and plug in USB while holding the button down.
Joshua Bardwell thanks fixed it it right up.
I have a question. I have a airbot F4 micro flight controller. and it will not acknowledge the throttle signal unless I plug in a USB and then it will acknowledge and stay working. but that is the only way I can fly , I have to plug in the battery and then plug in the USB to my quad and then unplug the USB and then I can fly. I consider myself halfway knowledgeable, but I am not sure why this is happening.
+Carlos Flanders no clue, sorry.
Hi Why does my Omnibus F4 Flashing with blue light and when i connect there is no respond from Flightcontroller?
Hey Joshua great video. Was this the bug you spoke of in the previous video "Death of F1 boards." I'm doing a build for a customer and I suggested this board to him. I hope I didn't steer him wrong. I also fly omnibus.
+Vincent Paolo the big I referred to is related to getting telemetry and SBUS working with FrSky.
I had that moment with my quad with omnibus f4 in it. Instead of that moment, I got problem with its GYRO then.
After it crashed, the gyro is error by seeing it in my goggle. I couldn't arm the quad and the message "no gyro" appeared in gogge display. I tried restart the quad by plug-unplug it then it works again.
Can you guys helm me? What makes it so? That makes me afraid to fly my quad again before i could found the problem.
Running official 3.3. I freefell from 150ft due to my inputs being ignored after a throttle punch (within 100 feet), it continued on for a couple seconds till I hit the failsafe(Qx7) I then attempted to rearm and "catch" it did rearm but too late, surprisingly nothing broke, not even a blade.
Osd didn't work and only displayed random letters. Bb did not record as I did not insert SD card.
I reflashed to 3.25 and strapped the drone to a 4X4 and gunned the hell out of it with tons of throttle stabs- no failsafes/glitch, osd works.
Using a Hobbywing F4 with OmnibusF4SD target, Dalrc engine with 3A BEC, 5v feeds 200mw VTX and XM+ RX, cam powered from Vbat.
Going to attempt flight tomorrow, hoping it was a firmware bug I read on RC groups someone with an OmibusF4 and 3.3 had exact thing happen, someone wrote it off as a tx/rx glitch, I'm not buying it, I couldn't disarm, but my switch failsafe worked? I have the RX set to "no pulses" and my FC RX failsafe is "lead balloon mode".
Weird stuff, frightening too because I had around 15 seconds of no control over my quad. If she flies sweet with 3.25, I'm giving 3.3 a hard pass.
Just thought of something, bb faulted due to no sd card, wondering if onboard flash size is too small and somehow it tried to log data and freaked out the board due to insufficient memory causing some kind of conflict.
But isn't BB flash separate from EPROM? Maybe just a firmware update glitch?
Dataflash and program memory are separate.
I figured that. I'm going to eat my words, but I DO think it was a RX issue, I was flying around, punching out a little bit, then went off away from me and at low throttle, and boop! failsafe- it STILL could be another component such as noise in the system since I'm running beefy motors. Oh well, I'll throw in another XM+ rx and see if that solves my issues, I'ts directly soldered to the board via stubby pins and I made sure the joints were nice and shiny.
I also flew old blue that is the same frame/similar setup and had zero issues- this will be the first bad FRsky RX go bad on me- also, antennas are tightly connected, so that isn't it.
Since it's down, I downloaded Butterflight and see if the hype is real.
Joshua with the Asgard F4 V2 FC I have a few issues. Spektrum RX & OSD
The FC came loaded with BF OMNIBUSF4 3.0.1
1st issue you already answered for me I did get UART6 to 3.3v by removing the default bridge on 5v and bridging the 3v
2nd issue is UART6 must be inverted or opposite of what my DSX Rx likes because its not recognized.
I downloaded official BF 3.1.7 target OMNIBUSF4 and flashed it and still UART6 does not recognize RX
Somehow on GitHub I found downloaded and flashed a build by Boris.B BF 3.2 #1253 target OMNIBUSF4
I now am in business my RX is recognized and I finished my build but now the oddity is BF configurator can not detect my battery voltage 0.0v and my OSD is there but no data. No matter what I change BF to display in the OSD it will change in the configurator but does not reflect the change in my goggles.
so my issues stand as:
when I am on 3.1.7 everything works with OSD and Voltage reading does show in BF configurator but RX is not recognized
when I am on 3.2 build #1253 my RX now works but my OSD gets no data and BF configurator shows 0.0v battery.
I don't now how to get 3.1.7 to change UART6 from inverted to non-inverted or vise-versa. The commands I found online say syntax error when I try them.
I know your busy but was wondering what you would do if you were me? Is Boris.B someone that can be reached if need be?
Thanks Jim..
You are running 3.2, which is a pre-alpha build. It's not surprising that some features don't work. I suppose vBat and OSD are not working in that build and target. That's the risk of running a pre-alpha build.
Thanks, but a few days too late for myself. my quad flew great until I tried to log some blackbox. that's when it flipped out now the board won't power up, one green led turns on but fades in very slowly, no connection to the computer, the casing to the SD card holder heats up.
+Casey Pinochi casing to the SD card holder heating up means you have a short. On the BFF3 if you fly without an SD card installed the casing can be crushed and contact Vcc. The board is likely dedtriyed.
Boards are definitely toast, but the casing was intact, happened to 2 boards only after actually logging BB(boards may or may not have been clones) guess that's what I get for trying to go cheap, buy quality, spend now, save later, lol
I have an omnibus f4 OSD AIO and it did this crap this weekend. but mine doesn't have an SD card slot on it.. any ideas? I really hate this board as I can't get ESC pass-through to work nor can I flash the firmware. May just replace it with something better.
lol I've had omnibus f4 pro for while and like it, I did have either flight controller go bad or was fault or esc burning out and #2 motor input on board quit working. wish I knew how to fix it
oh shit my bff3 is doing the same shaking but its stops and im able to recover and not crash do you think i can fix my problems with this fix? its doing it ramdom and 2 to 3 times in a pack
Hello! I really like your videos and feel like you are the best person to learn from! Your new vids are awesome keep flying! :)
However I got an issue with my F4 pro v3 flight board. My drone crashed and I had no idea why. I tried to plug in battery and something started smoking. I found that it is the U4 unit. Next to it there is a C7 resistor and it came of somehow (at least one "leg"). I soldered it back carefully and tried to plug it in again and it started smoking again. I removed the burnt U4 unit. Now I am wondering what funcion will I missing. Maybe you know that (?) :) The FlightB turns on and looks like its still working.
Better to not get omnibus.
davidhkblog1.blogspot.com/2017/06/fixing-omnibus-f4-pro-over-heat-and.html?showComment=1541408154194&fbclid=IwAR0DAE2uii9O1eEEXnDitEB6WSsGw1E3e22xpCHsfqDY9nb8yP7uv2E_HJM#c6956157706785268210
I'm experiencing this on a F4 pro we're my quad will just fall out of the sky out of no were. Will this work for the pro versions as well?
+SteveO4478 yes.
Hey Joshua so just put new motors on my build and I am getting a lot of jello in fpv cam I checked and all components in build and they seem to be secure... what parameters in bf can cause jello just wondering how to possibly tune it out... jello seem to be the worst with throttle punches
Alex Dalton D, but it's more likely that you have one motor which is out of balance
MrMario616 all 4 brand new emax 2205 also jello is in fpv camera
MrMario616 figured it out man the props were scrap put new props on and night and day difference
Josh, I have this in version 3 but cannot get the buzzer to work. It is enabled under the configuration tab. Can you help please? Dont want to fly with a buzzer.
+Roland Burrows you mean motor buzzer?
Joshua Bardwell I installed a buzzer on the buzzer pins and connected to a switch on my taranis, aux 3! However, the switch works, the blue light on the FC blinks but no sound.
If the FC light is blinking, then everything is working except the buzzer. Either the buzzer is broke, the FC is broke, or the wiring isn't right.
Make sure you bought a self-driven piezo buzzer and not a passive buzzer.
Joshua Bardwell thank you. Wiring was wrong! 😒
Hi Joshua, what would you expect to see in a blackbox log if this was happening? I'm getting the same shaking and inversion, but logging shows heavy rc command inputs that aren't coming from me! Happy to share the log :)
Thanks!
The main thing you would see in this specific case is that blackbox logging cuts out entirely at the same time the quad flips out.
Ok that's not happening in my case, the rc commands seem to go crazy at the time of the issue and there don't seem to be any gaps in the log- its on a Matek F4. I don't think it could be a faulty IMU if the rc commands seem to match the quads change in attitude, any ideas what else it could be? :)
Transmitter gimbals borked.
1. It's not failsafe because rcCommand would freeze up.
2. It's not a bad gyro because you see rcCommand freaking out.
Therefore: it must be that the FC is getting garbage data from the receiver. Possibly the receiver is borked but especially with serial protocols that isn't likely. So the most likely cause is your gimbals are borked. Check the output monitor screen on your transmtiter.
Do you have video and BB log of this event? It might make a good video.
Thanks, I'll check them out - its a brand new Taranis X7 though! If you have some time would you be able to look through the two logs please? Both are about 30 seconds long , thanks!
I don't have video of the flight unfortunately
Have you ever come across this issue on a board without an sd slot or with blackbox logging turned off? I am experiencing the same thing, minus the crash, with a DYS f4 aio.
I have never personally experienced this issue.
Hmmm, yeah I didn't think so. I need to do a log and test OS42 to rule out a DMA conflict, my next guess is the gyro is crapping out.
I've had this happen to me a couple times on the BetaFlight F3 board. Good to know. Is there anything else that could be causing it?
Also wondering if it's bad to keep debug set to gyro after I have filters tuned.
+Boomotang debug gyro will slightly increase your logging data. It's no big deal.
I have an ARTOWER F4 PLUS 2.0 Flytower Omnibus FC... which lead me to this video. I'm currently experiencing an issue where the copter just "drops dead" during hover testing at random times. Motors will just stop and bam, right to the ground it falls. All lights remain on. It will not re-arm either. I've tried connecting it to the computer after an event like this occurs and it's dead to the world. I tried blackbox logging just to see if it would tell me anything.
Interestingly enough in betaflight 3.2.0 with this board and sdcard_dma = ON, I do not get any shaking at all, just figured I would mention that. Presence of a microsd card or not, however, makes no difference with this "sudden stop" issue I'm having. Do you have any advice on how I should debug this? Basically I feel as though the FC is crashing/freezing.... I am going to disable DMA tomorrow and see what happens, but remember, I haven't even been using the blackbox except once to test.
Refusal to rearm is a strong indication that you are having failsafe events. Check your receiver and its connection to the FC.
Hmm... I've already replaced the receiver; and it's wired up to a 3 pin connector that seems to fit snugly. Every time this happens the receiver light is fully on and responsive to the radio being turned on/off. I should have mentioned that. Thanks for the fast reply! I don't know what my next step would be. Would a failsafe event though prevent me from connecting it to betaflight until reboot/restart of the quad? That is what struck me as strange. I should test this...
If the receiver stays green then the likely cause is the signal wire to the FC.
I'm not sure whether failsafe would prevent connecting to USB or not.
For science, just now I tried powering it on, ensuring I was bound, and unplugged the receiver from the copter entirely. Surely that would cause a failsafe event, total and complete loss of receiver. Connected right up to betaflight with no problems. There is something going on with this FC and I can't put my finger on it... I wish there was a way to have more detailed logs that might lead me to what's going on.
Is your bed extraordinarily wide or is it the camera? Looks like you could fit about 5 people in it!
+Simon Cheers its a queen. This is a hotel.
+Simon Cheers Oh, I see. It's two beds.
Does it interfere with the motor 2 output specifically? I've been having this problem with my omnibus f3 ever since flashing BF 3.1.
It makes sense that it would interfere with one specific motor output, since the motors never share the same DMA channel as each other.
G'day Josh, thank you for another informative video. I've been banging my head against this issue for the last few days trying to figure out if it's worth keeping the Omnibus F4 Pro I have or if I'm better off throwing it in the garbage.
I have been reading all over the net and it is looking more and more like the DMA conflict issue could be a problem with the F4 chip and may not be something that the devs can fix. Have you heard any more info on these issues and have you had it occur at all with other F4 boards like the Holybro or Matek F4s?
It doesn't occur exclusively on the Omnibus, I know that for sure. I don't know if there is any fix for it other than to turn sdcard DMA off.
With DMA off I'm still getting some funny behavior with random and quite infrequent glitching of the motors. Something like 1/10th of a second full or no throttle glitch making the quad jump or sink. If I turn logging off completely this glitching disappears. It's super annoying!
Just had a look on the Matek site and it looks like they are confirming it as an issue on the F405 (www.mateksys.com/?portfolio=f405-osd). This is a pretty major issue. I'm surprised it's not getting more attention.
It's worth noting that I've been using a Flip32 F4 special edition from RTFQ that has a data flash chip instead of a SD card for logging and in 3-4 months of flying it I have never had any issues whilst running both Dshot600 and logging concurrently.
I wonder if the Holybro Kakute F4 is also immune to these issues due to using a data flash chip instead of the SD card?
I've had this problem before, but I thought I narrowed it down to an ESC issue on my build. I'm using a Omnibus F4 Pro
Brilliant! Thank you.
I assume this is only a problem if you use Dshot which uses DMA?
That would make a lot of sense.
Stephen Gibb I have 2 copters using this board and oneshot125 and I never had this problem until I upgraded to dshot. Go figure.
hi joshua i am wanting to get a new FC but I cant decide between the omnibus f4 pro v2 or the xracer f4. which one would u recomend?
Omnibus I guess because ti has built in PDB. For use with a 4-in-1 maybe the Xracer.
Is this issue only happening with the F4 Omnibus? And is it only happening with Betaflight? I'm running iNAV 1.7.1 on an F3 Omnibus.
+Nihilistic One turn off sdcard_dma and see. Report back.
I haven't ever experienced the issue...yet. Has anyone reported this happening on an F3 Omnibus? I could turn off scard_dma just to be safe, I suppose.
Im having a issue with Acro mode. Stable and Horizon mode work perfect but acro will fly good for a few seconds the the stick inputs will randomly change. Pitch forward will roll left, pitch backwards will pitch forward and so on with the rest of the stick inputs. only thing that does not change is yaw and thrust. Sorry I am a newbe and this is my first build.. PLEASE HELP
I literally can't think of a single thing that would cause this. Find a more experienced pilot who can get more information about what is going on is my advice :-)
Thank you Joshua. I will do some more research.
Which is the best omnibus f4 fc?
Airbot f4 or dys f4? Pro or V2/V3?
is there any difference?
+emrah no name Airbot F4 has no osd.
Has this issue been fixed in Betaflight 3.2.0?
Unknown
Hi JB
I hope U can help. I got problem with my OSD all screen shows VVVVVVVVVVVVVV
omnibus F4 v3 SD betaflight 3.2 ich thing I put on change VVVVV to different character , in the background I can see camera signal
any idea ?
Re-upload the font.
Thank you very much. Now I see something, and I learned something today :) again thanx
Thank you JB! I wasted hours of my life trouble shooting this until I found this comment.
Hey JB!! My issue is not entirely related to this video, but I'm hopeful you can help. I just received the Furibee Darkmax 220 with the Flytower Omnibus F4 SD FC. The receiver binds to my Taranis just fine, but I get no response on the Betaflight receiver tab. All the setup seems correct: SBUS selected, serial RX mapped to UART1 per the instructions... Any ideas? Re flash the newest BF version? Try a different UART? Many thanks!
If SBUS is selected and serial RX is on the correct UART, then it should work. If it doesn't work, then double check the wiring. Then if it still doesn't work, start re-examinign your assumptions. Do you definitely have an SBUS receiver? Is UART1 definitely the correct one?
Hello! I have the darkmax and had the same issue. You need to turn off UART1 and enable UART6. It is incorrectly configured from the factory. I hope this helps.
Thanks John!! I'm hopeful that will solve the problem.
I had the same prob. It should on UART6, not UART1 like the manual incorrectly states.
Crisp, I'm wondering, have you flown your darkmax at all, and how is your experience? are you getting any random drops?
so I turn off black box when I get it and I'm all good. I never use it so I should be all good?
If you don't use black box, there shouldn't be an issue.
Ok thanks
I have this Board and read a couple weeks ago about the DMA issue but the issue I have is that I turn SD card and black box on but when I go into black box it doesn't give me the SD card option just either to an onboard log or a third part device but I know there should be a third option, any ideas please?
Is SDCard enabled in "Features"?
Joshua Bardwell yes it is and black box...been racking my brains on this and scouring the net for support...hope you can help 👍🏼
Here are the options I have..._plus.google.com/photos/..._
Here is my brand new SD card inserted....
Here are my options on the black box menu..._plus.google.com/photos/..._
i have this board from banggood but mine wont logg. ust makes a 4gb file that i cant use :/
+vazza69 is sdcard option turned on in Features, like I showed?
Yeah and its set to sd in cli to. I don't get the wobbling when i fly either..
Okay now i thing it was a crappy sd card. now i have a nes one and i get a log folder but i always get a big file named freespace. ??? Know of that?
Pardon me for not doing my work XD So the limit for logging is 4gb. And so my problem probably was the bad card. I also set dma of and down for 8k logging to 1. well see now.
I had 2 Omnibus that did this...one burned itself up...shoot..I threw them away and went to the Matek F405 boards...
This is happing to me but I have a naze32 it just started happening today out of no where how do I fix this?
To be honest if I had sudden trouble with a Naze 32 today, I would consider replacing it. Betaflight hasn't supported F1 chips in several versions.
Hahah yeah ordered the omnibus f4 thanks. Hopefully it don’t do this but at least I’ll know how to fix it.
I just installed the omnibus board In to my quad and was flying but it randomly falls out of the sky I will hear 3 beeps then it will just disarm and it happens randomly. What’s the problem? It’s not like this problem it just beeps and then disarms? And I did everything in this video I have no idea?
i have that flight controller and something similar happened to me once a while back. i thought it was a desync or something but it hasnt happened since so i forgot about it. anyway thank you for the tip i will do this!
I thought my Betaflight F3 FC was faulty as my quad was acting like a sick cat!
wierd my betaflight does not have a DMA cli command lol
and everything sdcard and blackbox is turned on.
Some boards don't seem to have it. Also, some earlier versions of betaflight don't have it.
Can confirm that sdcard_dma=off is the fix. 29 days and counting with no issues.
This issue happens with BFF3 as well.
I''m using the Kaktute F4 AIO controller and i'm getting the same problem, however i'm writing to the built in memory instead of an SD Card. Also my video and OSD will cut out as well. This does not happen when blackbox is disabled!!!!
Also there is no SD_DMA options in the CLI, probably as the board doesn't have an SD reader.
I agree that the sdcard_dma option only appears if you have an SD card reader.
If you are using Dshot, switch the Multishot and that should resolve any DMA conflict with the motors.
I shall give that a go.
Please email me joshuabardwell@gmail.com to let me know if switching to multishot fixes the issue, okay?
Didn't work :(
email sent.
Can someone help me, i added the dys omnibus f4 flight controller to my drone and i have an xm+ receiver bound to my taranis qx7 and in the receiver tab on betaflight the stick values wont move. Ive gone into the ports and tried changing somethings but to no avail.
CarelessMedia make sure to select Serial and SBUS in the configuration tab.
I did
CarelessMedia What version of Betaflight are you using? Right now, 3.1.7 doesn't work, I have mine on version 3.1.6
CarelessMedia Also, you need to connect your receiver to UART1 as it has the required hardware inverter for FrSky receivers.
Thank you so much for the advise
I've been blaming that on the rx this whole time!!
it fixes the crash but sd logging doesn't work after 10-15 flights, logs are empty
+windrides it should still work even without DMA. Are you sure you have sdcard turned on in the options.
It works fine up to 10 to 15 log files. If I don't format my sd card after 10 to 15 logs, it stops working and just creates corrupted log files. The log files look empty in Blackbox Explorer but they actually have some data inside. If I open them with notepad I can only see UUUU characters and no binary. I have tried it with 2 microsd cards. My logging rate is 250Hz and the cards are class 10.
Why my quad falls off the sky exclusively on front flips ._.
+MrCineris a front motor is defective.
Does anyone have an answer to get ibus on the omnibus F4 pro V2. I know blue falcon project has a video but it doesn't work for the pro. I would prefer not to run ppm. Pppplllease Help
Can you not just solder to any UART RX pad?
the pro doesn't extra uart pads
it just has pwm pads
I'm going to try the J5 port. that's for the reply. I know your a busy guy. p.s. u the man! lol
Thanks!
0:12 looks about like what happened to my quad when a prop exploaded mid-flight
That's exactly the reason why there are DMA priorities you can set for each stream. However it seems developers don't necessarily know how to use those.
Well if you are so smart, start making pull requests. This is an open source project and everyone is doing the best they can. The use of DMA to control motors is relatively new with the advent of Dshot so it's not surprising that there are some growing pains. Or maybe the vendor just screwed up the mapping of DMA channels on this particular board? Remember that the mapping of timers and DMA channels to resources is not controlled by the BF devs and varies from board to board.
Argh. Sorry... I guess I came off a little defensive. It always bugs me when somebody is critical of these guys. They work so freaking hard for basically no concrete reward, and since it's an open source project, I can't help but feel that anybody who is critical and who then doesn't contribute is being really hypocritical.
Joshua Bardwell it didn't meant to insult or decrease the importance of contributors to the project. I highly value open source projects, the problem in this particular situation is that there is no equal amount of HW devs contributions as to other higher level portions of the code. BF is complex system especially because it's baremetal and everything have to coexist. I had already issues with DMA priorities on the BF before: essentially ADC was taking over UART TX or RX and the result was many corrupted packets. Unfortunately devs ignored my message on that.
Also DMA priorities are not an issue in this case, it's something else apparently
If the DMA motor control usage is new to DSHOT, then another potential work-a-round might be to cut back to multi-shot. Just a wild guess. Perhaps useful for those who need the most reliable logging.
Just read the github postings on the issue. Seems the issue may be a CPU bug(fault!), triggered by more than two simultaneous DMA operations. If so the only fix possible is to never ever use DMA for more than two simultaneous tasks/jobs, in the firmware. So the new DSHOT is exposing this issue, because it's (presumably) an additional use of DMA in the system. Hmm.
I have a problem with mine taking off at arm
@Midwest FPV mine turned out be simple. The motor direction was wrong. It's not enough just to have 2 CW and 2 CCW. The directions of spin must match what you see in Betaflight. But you probably already know that....There are quad groups on Facebook and they are good about answering your questions. Squadrone is one
I'm watching your flight tutorial for few days my doubt us that can learn how to fly with my phone with same for free rider. it is app version there it two joystick on phone screen and not with a radio
+Lalith Kishore no you cannot lean to fly that way. Not very effectively.
You will learn to fly a simulator on your phone, but thats far away from real fling with a transmitter in your hands.
Try to play simulators at least with a transmitter, this will really teach you how to fly.
just putting one of these on a new build (Chameleon) so thanks
hopefully they will fix it
mine does that with my betaflight f3 fc
mine doesn't crash just shakes crazy on throttle ups. soft mounted fc and replaced motors with brotherhobby 2206x2450kvs and it stopped it. hmmmm motors cause vibrations?
ive builts 5 betaflight f3 quads lately that does somewhat the same. all 5 drop the back left motor on 100% throttle. tried fw all the way back to 3.0. diff escs and firmwares. diff motors.
damn, just got one Omnibus F4 AIO.
A excellent board. Never had this problem with the two copters I fly with Omnibus F4. Gonna do the fix anyway. You're good : )
Do you use blackbox in your quads?)
I hope betaflight developers will do smth to fix it in software.
I would not say I use it but it is enabled.
Quad under the influence M DMA lol
Here is the issue on github: github.com/betaflight/betaflight/issues/2631