Cut out on cc3d again about betaflight HOT 63 CLOSED

hmmm same thing happening here on cc3d atom..Random dropouts... Josh recommended altering rxfail to 3h... i have done this and give it a try tomorrow

from betaflight.

i thought it was losing RC command... I did a blackbox log a couple of weeks ago, and there was a spike in the rc command inputs which led me to believe i maybe had a loose ppm signal wire, i resoldered. my ppm, i am using a flysky receiver 8 channel that has been proved to be real reliable so far.. i also got a pwm ppm convertor this i have used on my naze32 with no problem. and i am not flying out of range as we are only talking here a few metres line of site... happen on fast yaws, and even on just a hover.. so it seems its not just me hope you can help Boris or suggest any further tests i can do....this happened before air mode on previous versions of betaflight too.. thanks Al

from betaflight.

Maybe but just maybe there is huge amount of jitter on CC3D. From what you are saying there @handsomejackuk indicates something like that.
try "set rc_smoothing = off" and see if that solves the spiking RC commands.

from betaflight.

thanks Boris... i will try that and report back when we get some dry weather her to get out to fly.... Keep up the great work,,,

from betaflight.

Hi first off all Boris. Your firmware is superb had it on naze32 and completely transform my craft, recently broke the naze and moved to a backup CC3D board. And can confirm like handsomejack I have motor shut down when enabling air mode after I do a loop or roll. Ive bought another naze but thought Id share for the ongoing development. Super work once again Boris keep it up.

from betaflight.

#44

I Noticed that when i disabled the motor arm switch it all seemed okay.. i also changed the cut of time to 0secs

from betaflight.

Thanks for sharing all this, but to me the issue doesnt seem to be in the code. All other targets just work and quite a few folks I know dont have the issue on their CC3D

Could you also try 2.1.6 to see if the problem is still there on your boards.

from betaflight.

I have a question for people with this problems. Could you check loop time in GUI when you reset board byt hardware or software few times ? It is constant 1000us with +/-5 ? I found that my MPU-6000 sometimes start with bad initialization and works with 8KHz without sample divider so gyro sync does not work properly. Solution for me is bigger delays in mpu6000AccAndGyroInit() 15ms instead 1ms.

from betaflight.

@marbalon and others
Can you verify that the issue is the low delay?

from betaflight.

I can confirm this happens on my custom board with MPU-6000, but problem occurs occasionally. But with more delays in init fix the problem in 100%. It is easy to see this in loop time info but I made some dumps using logic analyzer.

Edit. this happens more often when you reset board using GUI, after power up sometimes it is OK, sometimes is not.

from betaflight.

After I had some odd problems with my copter today aswell (CC3D running 2.1.6) i fund this thread and had a look at the loop time. It is as you described the problem @marbalon the loop time sometimes spikes up to something over 2000 and is not stable in general.
how did you implement the bigger delays in mpu6000AccAndGyroInit()? i´d like to try that.

from betaflight.

I just put this delays in code and compile. But the problem is that if bad initialization occurs you shoul see loop time is less then 1000us.

from betaflight.

hm,
after connecting with the latest version of betaflight my cycle time is between 995 ... 10200
I am not a bit concerned if this is the right firmware for my cc3d. Although I am looking forward using it
Is it save to do so?

from betaflight.

The looptime fluctuations are related to the vusb port.. try again with a ftdi on either of the 2 usarts.

from betaflight.

Ah I hoped it was something that I did "wrong" ;)

from betaflight.

Just connected via FTDI and its between 1008...994

from betaflight.

is the vusb port the onboard usb one...? as i dont use that, I only use main port with an ftdi for flashing and running a bluetooth adaptor... as my usb port is hidden inside my zmr lowrider frame...(main port next to flexi port)... would there be any advantage / disadvantage to disabling the main usb connection an cc3d atom... sorry not got back to testing any more as been a bit il with flu.. back again soon....

from betaflight.

Yes i meant the onboard usb.. it should not matter as long as there is nothing connected to it.

from betaflight.

More info, I tried with and without OPBL on Betaflight 2.1.6 and in both instances the board would crash (all motors full stop) in flight. Flashed back to CF 1.11.0 and 8 batteries with no cut outs. Are there any suggestions as to something I can try to get it stable on CC3D? I've tried two different boards and same thing.

I'm thinking of ordering Motolab Tornado's to replace CC3d's thoughts? I see Boris flies the Tornado would this be my best bet for a stable Betaflight platform?

from betaflight.

I think If beta is not going to support CC3D they should just be more open.... After all buisness is buisness

from betaflight.

@MrKarver
Can you try on Cleanflight 1.12 with gyro_sync enabled.

@henn1001
Is there an issue with CC3D? Your works fine right?

from betaflight.

@borisbstyle
I flashed 1.12 and enabled gyro_sync = ON the cycle time was hovering around 1000. That resulted in about 3 times more "cutouts" and it wasn't flyable. I then set gyro_sync_denom = 2 and it was stable. Burned up 4 batteries testing with no trouble at all over many USB connects/disconnects/reboots/config changes. Seemed great.

Do we just have some bad samples of the CC3D that wont run 1 to 1 with the gyro? I'm having the same result with 2 different CC3D's both from good suppliers.

1.12 with gyro_sync enabled feels very nice on the sticks!

from betaflight.

Haven´t flown that much lately because of the weather but i did 5 flights with airmode and at least 30 with the version pre air mode and never noticed anything strange...

from betaflight.

Hi i also have an issue with the bf 2.1.5 and 2.1.6 .
I had 2.1.3 on all of my quads without any problem i have one cc3d and one atom. I updated from 2.1.3 to 2.1.5 on one of my quads and setet and got everything to work except the motors no matter what i do they want spin. i tried my second quad with 2.1.3 there were no problems. i flashed it with 2.1.5 and the same thing there they wont spin not with the tx or the program.
Have looked around and my english aint to good and i have never entered anything in the cli so i dont know how to do things there.
And i cant find anything about this problem.
Have a hard time thinking its only me this is happening to. and on 2 of my quads so right now i wont flash my other ones before i can get these 2 to work.

I hope someone here can help me.

Best Regards
Morgan

from betaflight.

@borisbstyle
Just for fun I flashed another CC3D with current Betaflight. So this is controller is number 3. Same thing flies for a bit then randomly cuts out. Much better than the 1.12 with gyro_sync_denom set to 1 that would crash every 20 sec or so but still at least once a battery.

@cyberbaloo77
I'm sorry to hear your having issues but it sounds like your having a different problem. The issue we are talking about here is that the flight controller will run the motors for a bit and then shut them off.

from betaflight.

Than there must be an issue with cc3d and interrupt stuff of it if you
experience the same on cf 1.12 when you enable it.
Op 29 dec. 2015 19:56 schreef "MrKarver" [email protected]:

@borisbstyle https://github.com/borisbstyle
Just for fun I flashed another CC3D with current Betaflight. So this is
controller is number 3. Same thing flies for a bit then randomly cuts out.
much better than the 1.12 with gyro_sync_denom set to 1 that would crash
every 20 sec or so but still at least once a battery.

@cyberbaloo77 https://github.com/cyberbaloo77
I'm sorry to hear your having issues but it sounds like your having a
different problem. The issue we are talking about here is that the flight
controller will run the motors for a bit and then shut them off.

—
Reply to this email directly or view it on GitHub
https://github.com/borisbstyle/betaflight/issues/64#issuecomment-167853031
.

from betaflight.

In 1.12 if I set gyro_sync_denom = 2 it works fine.

from betaflight.

Ok i manage to fix my problem somehow :) So now i dont going to disturb u anymore :)

from betaflight.

And in betaflight when you put gyro_lpf to off?
Op 29 dec. 2015 20:13 schreef "MrKarver" [email protected]:

In 1.12 if I set gyro_sync_denom = 2 it works fine.

—
Reply to this email directly or view it on GitHub
https://github.com/borisbstyle/betaflight/issues/64#issuecomment-167856046
.

from betaflight.

Flew just 1 pack on the latest Betaflight on a cc3d board with no issues at all. First I thought its just a problem in "Air" mode. Actually i flew like 6 flights so far and everything went fine. No expert here but if i can help with some infos or settings i am glad to help.

from betaflight.

On cc3d you need to reset all settings on any transition between 2.2.0 and
other firmwares. Maybe thats why strange thing happened.
Op 30 dec. 2015 03:43 schreef "MrKarver" [email protected]:

@borisbstyle https://github.com/borisbstyle
I had to add a pic for this one. I flashed to 2.2.0 and the result is I
get ACC and Gyro data in GUI, receiver inputs react as expected in GUI but
when I arm (either with an AUX ch or using yaw right) 3 motors go to full
throttle and one stays at idle. As you can see the throttle on the radio is
at idle. Tried both CC3D's and exact same result. Am I missing something?
Also nothing changed setting gyro_lpf = OFF. Apart from that nothing else
seems unusual. Definitely not flyable though.
[image: image1]
https://cloud.githubusercontent.com/assets/16183604/12045569/2cb0e60a-ae5b-11e5-8cdc-6d011b70c19e.JPG

—
Reply to this email directly or view it on GitHub
https://github.com/borisbstyle/betaflight/issues/64#issuecomment-167922006
.

from betaflight.

@borisbstyle
I am using Cleanflight Configurator 1.1.0 to flash using a FTDI and I select "Full chip erase" on the flash utility screen. I have also used the Flash Loader Demonstrator erase and flash with the same result.

from betaflight.

CC3D motors at full throttle is being discussed here https://github.com/borisbstyle/betaflight/issues/88

from betaflight.

@borisbstyle
2.2.0 RC2 6 batteries in and no cut outs with gyro_lpf to off. With Gyro_lpf = 188HZ cut outs occur.

from betaflight.

CC3D on a tricopter 2.2.0 RC2 - 3 batteries and no cut out. Everything OK.

from betaflight.

I'm having the same cut outs issues with every version above 2.1.3 I'm currently testing 2.2.0 rc2 seems better but occasionally I'm still getting cutouts with Gyro_lpf=off . also have anyone experienced spikes on RC command when 2khz is enabled?. in my case I think is related to rc commands sometimes I see some glitches in the rc command probably causing the quad to disarm in mid air :(.

from betaflight.

spike in rc command is usually skipped loop by blackbox. Blackbox than
writes the 2 values in same loop. Look for 7loop counter in blackbox to
verify
Op 1 jan. 2016 18:33 schreef "maddust" [email protected]:

I'm having the same cut outs issues with every version above 2.1.3 I'm
currently testing 2.2.0 rc2 seems better but occasionally I'm still getting
cutouts with Gyro_lpf=off . also have anyone experienced spikes on RC
command when 2khz is enabled?. in my case I think is related to rc commands
sometimes I see some glitches in the rc command probably causing the quad
to disarm in mid air :(.

—
Reply to this email directly or view it on GitHub
https://github.com/borisbstyle/betaflight/issues/64#issuecomment-168318478
.

from betaflight.

Hello, i see that when i power on the board, the looptime is between 488 and 501, but sometimes it start to fluctuate between 480 and 560, seems when i switch to air mode, or when i disarm and change pid controller

from betaflight.

Thats normal cause CC3D uses VCP to connect with configurator. Thats not
the case when you fly
Op 2 jan. 2016 22:43 schreef "Nikybiasion" [email protected]:

Hello, i see that when i power on the board, the looptime is between 488
and 501, but sometimes it start to fluctuate between 480 and 560, seems
when i switch to air mode, or when i disarm and change pid controller

—
Reply to this email directly or view it on GitHub
https://github.com/borisbstyle/betaflight/issues/64#issuecomment-168430038
.

from betaflight.

so is there a CC3D issue or not?

If issue exists even on cleanflight with gyro sync activated please report it there too. It is still questionable weather there is a real issue or not?

from betaflight.

I've resoldered the esc to fc and motor and the issue seems disappeared. But i've only test with one lipo.

from betaflight.

I just flashed my CC3D with 2.2.0 RC2. I've run about 20 batteries through it on Open Pilot without issue. Never tried regular CleanFlight. I got everything up and running quick, but my first hover quickly ended in a cut out. Tried again today and I had two cut outs in about 2 minutes of hovering. I'm using everything from MyRCMart: CC3D, Little Bees 20A, etc. TX and RX are a Taranis and D4R. Also using most stock settings. I haven't touched sync, filters, or anything like that.

To get it working again, I think I just have to let it sit for a second. I tried dis-arming, re-arming, and changing modes quickly, but nothing worked except waiting about 5 or 10 seconds.

I'll try some settings changes and report back with details.

from betaflight.

Hi Boris,

I tried with gyro lpf = OFF and the FC disarmed just after armed (BF 2.2.0 Final)
It's a CC3D atom

I confirm that Cleanflight 1.10 doesn't have this issue. I haven't tried newest CF because I can't flash .hex files.
I have 2 CC3D with this problem.

There is a previous BF version that this issue does not happen?

from betaflight.

6 lipo and no issues for me after i've resoldered esc to fc
cc3d from myrcmart
gyro_lpf = off dterm_cuthz=0
acc|baro|mag_hardware = 1
receiver x4r-sb
littlebee 20a

from betaflight.

@nikybiasion

I'll try these configurations and test. Thanks!
One of my CC3D is from myrcmart too.

from betaflight.

Tried those above configs over two batteries hovering:
I lost horizon and acro modes. Only Air mode is available. Not sure if this is normal? I was assuming i t was from the hardware settings changes.
I have even worse cut outs now. I'm going to reflash and reset everything and see what happened.

from betaflight.

@nikybiasion
You should try 1.12 release cleanflight. I do recommend to be cautious with older cleanflight releases due to many failsafe bugs

@Rhoxa
When you disable accelerometer of course level modes dissapear

from betaflight.

I just made some bench tests (with quad in my hands). With gyro lpf = off the motors spins up suddenly and slows down again in a short period of time (frequently).
The looptime is around 500 (2kz), but I still get cut outs.
I checked blackbox and there is no spikes in any graphs

I don't wanna rollback to cleanflight, nor librepilot ;-(

from betaflight.

Solved my problem. I did a few things at once in a last ditch effort. First I got rid of my 5V BEC and put in a new PBD with 5V and 12V on it, this of course involved re-soldering my ESCs as mentioned above. Then I erased everything and re-flashed betaflight. I sat at the TX graph screen and noticed once in a while one my Aux channels was spiking randomly at about the same frequency I was having my drop outs before. This same aux channel was the switch I used for arming and it was spiking out of the range I used for arming. I expanded my arming range to be pretty big (~1400 to max).

Hovered two batteries with no drop outs so far. Now I just need to figure out the spike I guess.

from betaflight.

Ok guys so far no issues discovered. I have plenty of good CC3D feedback and all issues seem user related.
I can understand when few users have simillar issue it is easy to think it is software related.
Running cleanflight has also different frequency/looptime so the issue could be harder to reproduce.

I actually have 5 quads and one of the quads had occassional drop outs out of sky. One of the ESC wires was touching some of the FC components and that ESC was freaking out. Moving the wire from FC simply solved the issue.
The bottom line is that dropouts out of sky are in 99,9% of cases always hardware failure.

from betaflight.

I have moved away from the CC3d's to SP Racing flight controllers. I loaded 2.3.0 today on a CC3d and I am still seeing input command spikes. Since using a switch/aux ch. for arming (I do for 3d setup) I get cut outs.

from betaflight.

@MrKarver @borisbstyle

I have the same issue with CF 1.12-RC1 and a CC3D board, sudden cut outs. I can confirm that I only get this behaviour with gyro_sync=on. I tested it several times switching between on and off, and it's consistent. The motors usually cut out under 2 minutes when gyro_sync=on. Tried both gyro_lpf=188Hz and 42Hz, and both produced cut outs when gyro_sync=on.

@marbalon

I tried increasing the delays in mpu6000AccAndGyroInit() from 1us to 15us (or did you really mean ms?) but that didn't solve the cut outs. Has it worked for you?

from betaflight.

A quick update: using gyro_sync on with gyro_denom=2 seems to fix or at least drastically reduce the cut outs. Haven't had one yet, but will keep testing.

from betaflight.

@borisbstyle @MrKarver @Rhoxa

Ok, so this is really an issue with the aux channels glitching, which disarms the copter if you use an aux switch for arming. The glitch only happens with gyro_sync=on and gyro_sync_denom=1. Otherwise, no glitch and no disarming.

The glitch takes the channel out of range and disarms it.

@borisbstyle

I tried rc_smoothing=off, but no effect.

Any ideas? CPU overload at 1KHz?

from betaflight.

that is nothing new. CC3D has a timer clash on PPM

see this issue. It is waiting for someone to be fixed
https://github.com/borisbstyle/betaflight/issues/127

from betaflight.

As I have 2 CC3Ds with this issue and I use swtich for arming, I'll try to change settings to arming via stick and test!

Thanks!!!!

from betaflight.

@borisbstyle

Thanks for the heads up!

from betaflight.

I changed from switch arming to stick arming (+ idle up for airmode) with success. 2 lipos with no disarming!

Thanks!!!

from betaflight.

I have this issue on Naze32 rev6.

from betaflight.

My naze rev6 is doing this too

from betaflight.

Can you see the glitch on the live channel view like in the image I posted above?

from betaflight.

Edu , from Brasil ?! hehe
My problems was solved here , i look and detect a faulty littlebee , always he hits fullpower , desync and restart .
for me its solved , thanks !

from betaflight.

Glad you got it solved. Yes, Edu from Brasil, rs.

from betaflight.