In air mode, when I try to do a little quick roll the quad goes crazy and keep rolling. It will also reset the FC (not sure if some sort of circuit protection kicks in due to motors drawing too much current).

Out of air mode, the quad will just do a little quick roll no problem.

FC: Diatone Mamba F722 mini mk2
ESC: Diatone Mamba F60PRO
Betaflight FW 4.2

Log 002 shows the 'non air mode' roll


Log 003 shows the 'in air mode' roll

Not sure where to start, wanted to see if there's anything I should look at before trying to start over from scratch and reflash/reset Betaflight

edit: sorry looks like i couldn't upload the log files to this forum so here's a google drive link:

https://drive.google.com/drive/folders/1...sp=sharing

air mode will cause larger electrical spikes..... To me it sounds like your FC or ESC is on its last leg.

In airmode if you do a quick throttle punch like 0 to 100% immediately and quick throttle CUTS 100% to 0% immediately... does the same thing happen?

Try making sure all the solder joints are perfect and all the wires are seated firmly.

When you flip with air mode the electrical spike is gonna be higher than if you flip without airmode... and it seems lik that extra bit of noise is crashing your ESC or your FC..... this is my theory anyway.

So that's why I ask if the same thing happens with quick throttle cuts and punches...... if it does, then whatr I'm thinking is most likely what is happening.....

Thanks, I'll try to give that a try if I have some time tomorrow, otherwise will probably have to wait until the weekend to mess with it.

Also I didn't realize I couldn't upload the log files when I made the original post, so I edited it to add a link to a google drive folder with them in it.

https://drive.google.com/drive/folders/1...sp=sharing

if the flightcontroller isnt loosen or vibrate by itself while fly;i guess full throttle and full cut, happens in roll of death is more likely motor desync.
increase your idle speed in bf configurator another solution could be settup motortiming to high in blheli suite.

So I did manage to try 0-100% throttle today a few times. The first couple of tries it acted fine but it eventually did the same thing. The motor RPMs went crazy and the ESC and/or FC reset itself.

Also no problems while doing it not in air mode.

Tried a less aggressive prop and still have the issue. Tried going to stock rates and still have the problem.

I think i will try to reflash Betaflight next. Then possibly revert to Betaflight 4.0 (which is what the FC came with) if still have issues.


Last resort I guess I will just order another FC and ESC

could it be motor desync? motor timing ? hmmm...

Have you tried turning off rpm filtering

(13-Aug-2020, 10:19 PM)hugnosed_bat Wrote: if the flightcontroller isnt loosen or vibrate by itself while fly;i guess full throttle and full cut, happens in roll of death is more likely motor desync.
increase your idle speed in bf configurator another solution could be settup motortiming to high in blheli suite.

(14-Aug-2020, 04:02 PM)ivanwong1989 Wrote: could it be motor desync? motor timing ? hmmm...

motor timing is at 22 degrees. I'll try putting it back to 16. For de-sync I was under the impression that the motor will end up stopping, not spinning out of control?

also I tried turning down Ramp up Power to 30% but didn't seem to help.

(14-Aug-2020, 06:57 PM)voodoo614 Wrote: Have you tried turning off rpm filtering

I haven't yet. I'll give it a shot hopefully today or tomorrow.

I don't think a motor desync results in the resetting of the ESC/FC.

Sounds like what I suspected before..... I'm gonna make up a term and call it a "Soft short". I don't know exaclty what is is happening electronically but I've had this happen before.. either an ESC port or the FC itself can handle normal flight but as soon as you do a flip or really punch it and get large electrical spike it shorts out the whole system resulting in a system reset.

I hate to say it but i think you have a hardware fault and are going to need a replacement. Of course i could be wrong so try everything you can in the software before giving up, but I've experienced what you're experiencing before and replacing my 4-1 ESC fixed it.....

The thing that really sucks is that for me when this happened one single motor kept smoking so I knew it was the ESC....... for you.... it could be the ESC OR the FC, and I truly don't know how to tell without getting a new one of each and swapping until you eliminate the culprit.....

When this happens maybe you can can feel the motors... if one motor is much hotter than the others then it's highly likely it will be the fault of the ESC.... but if there is NOT one single hot motor it still won't mean it's NOT the ESC..... so the situation kinda sucks.

Hopefully I'm wrong and you just have a loose wire or somethign simple that we are not thinking about. I would try everything from shutting off RPM filter, to re-soldering and reseating wires all the way down to powering the VTX straight from the battery lead instead of the FC.

So turning off RPM filtering sort of seemed to help. I could maybe get in a flip or two before it would start freaking out again.

Today I also tried out some batteries with higher C-rating and it seemed to be able to go a few more times before starting to freak out. It also seems like this pack doesn't sag as much, and the voltage stayed up quite a bit longer than the other ones.

Couldn't get too much testing since the last incident left me with a broken arm on the quad. Fixed it but not before it got dark, so will try some more tomorrow.

I'm wondering if it might be my motor/prop/battery combination? iFlight Xing 2208 2450kv with 5x4.3x3 on 4S.

I'm considering trying some 2306 motors due to lighter weight and seem to be a little less amp hungry.

(16-Aug-2020, 05:23 AM)fakts13 Wrote: So turning off RPM filtering sort of seemed to help. I could maybe get in a flip or two before it would start freaking out again.

Today I also tried out some batteries with higher C-rating and it seemed to be able to go a few more times before starting to freak out. It also seems like this pack doesn't sag as much, and the voltage stayed up quite a bit longer than the other ones.

Couldn't get too much testing since the last incident left me with a broken arm on the quad. Fixed it but not before it got dark, so will try some more tomorrow.

I'm wondering if it might be my motor/prop/battery combination? iFlight Xing 2208 2450kv with 5x4.3x3 on 4S.

I'm considering trying some 2306 motors due to lighter weight and seem to be a little less amp hungry.

I think 2306 motors are more amp hungry than 2208 motors.... 

It also has a LOT more to do with the propellers than you might think as well.

Here check this site out.

https://www.miniquadtestbench.com/motor-explorer.html


But if it IS because the amps are spiking too high it means there is a hardware fault somewhere so it's really never gonna be too safe for you..... Eventually, if it is  hardware issue, that piece of hardware is going to die on you during large spike... whether in a crash or w.e it may be.

tried changing out the ESC and the motors, to Hobbywing xrotor 60amp and iFlight Xing 2306 2450kv with no real luck.

I notice the BB logs always cut off before I can really see anything that would let me know what's going on.

Probably going to try changing the FC later this week and hope that's the problem...

did you try raising idlespeed?

as you told, desync will be a stopping motor. it will be displayed in the logfile as 100% throttle input on the particular motor. de fc try to recover.
its not realy possibel to tell if a motor stop or does increase, it wont stay in the air. a runaway is more what would happen if one motor does increase rpm faulty.

idle % was put at 8% with dynamic idle set at 28 I think.

I'm fairly certain motors didn't stop/stall. fairly certain it was closer to runaway motor as instead of doing one flip/roll, it would go out of control and flip/roll a bunch of times while resetting the FC and/or ESC

a desyn or idle problem could look like this:

seems missunderstand your issue