Hi all! Here's an update on the project. I've now done some light test flying. I'm not very experienced flying drones and only been flying simple ready-to-fly drones with a lot of built-in flying support. Alt. hold etc. etc. This made it quite hard now at first. Struggled to keep a certain altitude and make smooth landings. But after turning Airmode off and Angle mode on it became much easier in every way. I'm happy to report the drone seem to work as it should and has a lot of power (propably too much for me, lol). I've now decided to change over to iNav as I've come to realize (after what's been said here and from watching some tutorials on youtube) that iNav has the kind of support features/functions I need right now. Like Altitude hold and more robust GPS functionality. Not sure when I'll be flashing and changing, but soon I guess. I can save all settings in Betaflight and if I flash back I can just restore, right? I've installed https://github.com/iNavFlight/inav-configurator/releases/tag/2.5.0-RC2 and hope that'll do. Will probably be following
Attached you find a pic of the build in it's current form. I've also ordered a buzze with built-in lipo to help me find the damn thing when it get's lost in the woods. More to come!
Very frustrating! My version of the Omnibus FCB isn't in the iNav firmware list. What can I do to get around this? I really want to move to iNav. See list of attached firmware versions. I have the Omnibus F4 V5.
Cool! Thanks for the quick reply. Before I do, can you just tell me the reasoning/logic behind picking that firmware version? Do you just know it's compatible or what? Is there a resource for looking this stuff up?
My GPS isn't working correctly in iNav, which I feel is at least a bit strange as it does in Betaflight. As it works in BF I suspect it's connected correctly. I have a RadioLink M8N SE100 GPS and an Omnibus F4 V5 FC flashed to Omninbus F4 Pro. The magnetometer works fine in iNav and I've set GPS on the correct UART with the correct baudrate (57600) and activated it with UBLOX protocol, just as my settings in Betaflight. Pre-arming checks give me a fail for "Hardware health" when the GPS tries to activate, which means I can't even arm. I found a statment in a github comment saying "This board have bidirectional inverters, betaflight deal with it, Inav not." which gives me the shivers. I really hope I don't have to switch out my entire FCB just to get a fully wokring GPS unit to work in iNav? I really hope I'm doing something worng here, so it won't come down to that.
So, I never had much luck after moving to iNav. A few flying hick-ups made it smash into the ground. Should have sticked with Betaflight. Killed a bunch of props. Had problems starting it after and when I was to move back to Betaflight I had a mishap where the USB-cable touched a parts of the FCB while the battry was plugged in....ligtning and smoke. My first thought iwas the that FCB is messed up. I see throttle levels go up when I move the BG engine controllers, but no motors start). Things works exept no engins starting when I'm connect to iNav via USB, but when I run on battery the FCB don't light up and I get no transmitter/receiver connection. But when I plug in the battery the PDB light up and the engines twich, as they do when they get power and initiate. When plugged in with USD to the iNav app I get green checks on everything, even the sensors on the sensor tag are all ok.
Somthing with the power distribution on the FCB I think.
The thing is, I don't know if the ESC's are ok or not...or the PDB for that matter. Anyway to diagnose ESC's, FCB or PDB?
Maybe it's just the PDB and/or ESC's that are gone. What should I do about this mess? Just get an FCB first?
...then switch out ESC's and PDB if things don't work? Maybe a bundle is the way to go? PDB with built in ESC's? Any good?
I still think it probably just the FCB, and changing to another Omnibus F4 V5 would be cheap and get me back in the air quickly (as I know the board now), but I have the feeling there's better options out there.
I'm going to use this as an opportunity to upgrade to stuff that works properly in both Betaflight and iNav.
I don't want to by the latest and most expensive stuff, I just want things that are proven to work well with the other components I have and well.. As much in-flight support for easy cruising as possible is something I look for, no racing. Very bad day! But hey, here we go again...
Apart from the injured Omnibus F4 V5, these are my main components:
Model: UR10. About 30 sencond later, it will beep in 90DB and LED would be light in white. Built-in Battery & LED Light & Gyro Attitude Sensor. While drone have dropped out and quad's battery is still kepping, about 30 sencond later, the buzzer would.
Another WILD ride and for what it's worth here's my 2 cents:
Why would you ever consider replacing the flight controller before the GPS?
Surely if you're having issues with the GPS you replace it? With the more expensive FCB with more solderpoints xD?
Seems like you just need a GPS which doesn't require inversion?
Kudos on wanting to know WHY thst firmware version was correct: teach a man to fish etc!!
Glad you got it fixed though, but in regard to frying the flight controller (RIP my friend, I'll keep in mind to be ultra careful when plugging in!!!!!!!) I already got some sparks when I tried to plug the balance leads into my multi-pack- charger board the wrong way around....
GPS is alright. Something wasn't working well with the firmware + my FC in iNav. Frying the FCB was a pure a sloppy mistake of course, have a multimeter, know how to use it. lol Will probably work much better with a all Matek setup, with an FCB that has specific version support in both iNav abd BF.