Unfortunately I am side tracked by another problem, flying model planes. Once sorted I will resume and tell you of my progress with the quads and fitting a GPS. Have ordered a Flip-Omnibus F3, once it arrives it will replace the Flip FC controller that has has developed some weird flight characteristics. I guess the F3 boards are now entry level for us mere humans.

Some problems solved, some remain. Note I try to solve the problems and only ask for help as a last resort.
I have two OmnibusF3 FCs, one from Banggood and one from RTF the suppliers of genuine Omnibus FC. I deiced to work with the first one and flashed it with iNav, easy as. Configured it as quad then fitted it to a frame (550 mm) which previously hosted a Flip 32 FC. The first thing was to power the FC, followed some instructions which instantly fried the regulator on the FC, more research shows this to be a bit of a problem with the clone boards. Don't know about the genuine ones as it is still in its packaging. Much to my surprise the first FC still works so after much more reading I took a punt on connecting a 5V power source as the instructions must have been translated about 6 times before they arrived in English, but behold it now works. So back to the computer and the motor test, work fine using the sliders in iNav but it will not arm. I have now arrived at the point where I need help.

I use a Taranis TX and X4R-SB RX configured for serial connection (works fine)
In the configure tab I have set Enable motor and servo output to ON 
In the Receiver tab all outputs work as programmed the important parameter for throttle is Min Thr 990, Max Thr 2010

So I hope someone can show me the error of my ways.

"So I hope someone can show me the error of my ways."

Hank, should have gone with drugs............cheaper and easier...................at least that's the conclusion I've come to with my own S500 kit build.

"should have gone with drugs............cheaper and easier...................at least that's the conclusion I've come to with my own S500 kit build."

At my age the only drugs you take are blood pressure, and anti inflammatory pills. You need a challenge so S500 kit sounds like one. The problem is firmware/software related not frame related, trust me. iNav is the one to use works with my BeeRotor F3 (same size frame) so it must work with an Omnibus F3, it will be a switch somewhere that causes the problem.

Hm difficult to tell... acc not calibrated? Or is it maybe searching for any sensors that it can't find? What is min_check set to (in CLI)?

Thanks fftunes, The accelerometer calibration has been carried out successfully, see the health check



The min_check in the CLI is 1100

Hope the information help to solve the problem.

Hi fftunes and others, the board arms when using stick arming, will NOT arm via a switch, going out to test fly the beast right now. 

That was an experience that I have not had before. Once it left the ground it was all over the place totally uncontrollable crashing upside down. A tethered test proved that all the inputs worked correctly, i.e. Pitch forward the rear motors lifted off, pitch back the front motors reacted same with roll, did not test yaw. It would start the shake violently and this increased rapidly, lucky I managed to kill the motors B4 harm was done. Any clues? There is no GPS or magnetometer fitted, at the moment it as basic as setup can get. I always take it one step at a time. The FC is flashed with inav_1.7.1_OMNIBUS.hex. My BeeRotorF3 is flashed with inav_1.7.0_SPRACING.hex and behaves perfectly. Hope that someone can point me to a solution other than throwing it in the bin.

That could be caused by excessive vibration.

I don't know if black box logging is available in iNav as I've never used it, but if you can take a black box log, it should tell you what is happening.

(18-Jun-2017, 05:39 AM)Hank Deucker Wrote: Hi fftunes and others, the board arms when using stick arming, will NOT arm via a switch, going out to test fly the beast right now. 

I find that weird... did you make the "active zone" for the arm mode large enough? Leave at least 75-100 units around from where the channel sits at (hope you know how i mean).

Regarding the "tazmanian devil" freak-out, double-check the simple things first - motor direction, prop direction, also check yaw (without props)... Mistakes happen to everyone of us once in a while.

Of course unseen is right as well, excessive noise is very bad. Did you use any sort of soft-mounting? When in doubt, you could check if lowered PIDs improve behaviour, say half P and maybe zero D. Just for hover checks.

I don't know filter defaults for iNav... a log file would really help.

Thank you both fftunes and unseen. First just a general statement fftune you deserve an Oscar for your description of how my quad behaved yesterday “Tasmanian devil freak out” just perfect and I still laugh every time it comes to mind. I give it 12 out of 10! 
Now to each individual point: unseen I use a vibration damper with each quad build, the one I use is:
https://www.banggood.com/CC3D-Mini-APM-C...71905.html
There maybe better ones just let me know. iNav has blackbox and uses a micro SD card I will let you know when I get the first result.
fftunes you ask “did you make the "active zone" for the arm mode large enough? Leave at least 75-100 units around from where the channel sits at (hope you know how i mean).” unfortunately I do NOT know what you mean, I will research “active zone” and see what turns up. I have check the rotation and and props and yes I often make mistakes and shut up about them or I would look totally silly. Naturally I will check the PID suggestion and let you know as for log file is that the same as a blackbox file?
I think I will start a new thread in the “350mm + Multirotors & Arial Filming Platform when I may find some people familiar with iNav, and I have also noticed that both of you gentlemen give advise in this section so I won’t feel totally lost. I may even be able to help some others in that area.

For the arm mode, i meant like, when the aux channel switch is in armed position and sending 1500 for example, don't set the mode "borders" to 1475-1525, but instead like 1400-1600, or even more.

Oh and i didn't invent the "Tazmanian devil" description it has been used quite often in betaflight threads, and not always because of user error... yes it is a very good description of when things go awfully wrong.

I thought had solved the "Tasmanian Devil freak out" but unfortunately not so. I opened the Modes tab in iNav and found that nothing was set, I forgot to click SAVE.  I reset the modes including the arming sequence for arming by switch and this worked so I assume that the flight modes would work as well. Not so!

https://www.dropbox.com/s/8vm5avonbu35gr...6.TXT?dl=0 

I had blackbox working and I hope that it can be examined. It is short because the flight lasted only a few seconds but may give a clue to what maybe happening. I also hope I finally figured out how to put blackbox file on Dropbox, it sure is a steep learning curve, why do they write instructions for teenagers not retired souls?

The next thing I will try is to set the Ps to half and Ds to zero as fftunes suggested.

Set the P and D values as suggested but the end result was the same it is still a wild beast. I have looked at the log file with both CleanFlight and BetaFlight balckbox. I can't interpret the output but the CF one had lots more squiggly lines than the BF one, hope someone cam make some sense out of it all.

I think you need the iNav version of BB explorer. Has to be downloaded from github afaik... I'll check it out later, haven't used it myself yet.

---

Anyway, there has to be something wrong... Did you check board orientation again? If you move the quad, does it move the same on screen?