[daveapplemotors]

When you calibrate your TX do you switch flight modes--Normal, IU1 and IU2?

[suzali]

No, I didn't. I dont have any different flightmodes programmed in the tx in this phase of testing.

[TheOtherCliff]

Those health errors deserve a closer look.

Do you use always armed for one flight mode and a normal arming for the other mode?

The only reasons I can think of that you would get this motor glitch (and even negative collective) in one mode and not the other are:
- The FC reboots in the bad mode.
- The channel positions themselves were causing errors.  This might be possible if one end of the mode switch was close to an invalid value and the problem mode was on the invalid value.
- The channel positions add up to an invalid value.  This used to happen with old PPM radios if the sum of all the pulses in the pulse train was too long.  I have an old RC brand 1 Tx and brand 2 Rx that have this problem.
- The glitchless mode ignores the error.  When you are running it in "manual" are you also "always armed"?  Really a stretch here.

You could look at Firmware -> FlightTime.  If it goes to zero right after the glitch, the FC rebooted.

You could set up some GCS scopes to watch things like:
- all ManualControlCommand.Channel (may jump to invalid values).
- SystemStats.EventSystemWarningID 
- StacksMonitor, see if any non-zero stacks go to zero right in that time frame

It may be a hardware problem.  I don't like to say that.  Is this an OP CC3D or a clone, and if clone, where did you get it?  I trust OP CC3D's.  I have heard of a very few bad CC3D clones.

[suzali]

What happens if you raise the neutral value on collective a little ?
And the low value to just above the low on throttle?

Have done all this, no change :-(

[suzali]

Do you use always armed for one flight mode and a normal arming for the other mode?

No arming in all modes by 'yaw right'. I never use always armed.

- The channel positions add up to an invalid value.  This used to happen with old PPM radios if the sum of all the pulses in the pulse train was too long.  I have an old RC brand 1 Tx and brand 2 Rx that have this problem.

I use a Lemon dsm2 Rx and a Turnygy 9x with OpenTX 2.0. I'll try another tx today.

You could look at Firmware -> FlightTime.  If it goes to zero right after the glitch, the FC rebooted.

Will check next time

[suzali]

I'm just wondering about the yellow sign:

[suzali]

I think  I'll go crazy

Reinstalled FW.
Changed TX and RX.
No change at all   

[SamSam]

1) I looked  at your UAV file. seems good to me, to rule out your CC3d Hardware is not defective... do you have a quad to try it on... heli setup is always tricky, quad setup is straight forward.

2) i have attached my trex compatible UAV file, but this is for open pilot ver 15.02.02. if you are willing to use open pilot firmware you can upload this uav. throttle and collective on same stick. arm- roll-right, . this file is guaranteed to fly,(no 3D flying though) i have been flying since July 2015

[suzali]

thx SamSam.
I don't want to use my Hexacopter for experiments with maybe faulty hardware
I'll go the second way using the openilot fw.

[suzali]

Problem is gone with openflight fw 


I had orderered a new CC3D, as they are very cheap meanwhile at aliexpress (less than 10 EUR). It came today. Build it in, flashed librepilot FW and configured it for my heli. Believe it or not: same old problem with stalling motor in automatic mode. So I can definitely say my board was not faulty.

I was so happy finding librepilot, now it looks as if I'll have to go back to openpilot without any support 

[daveapplemotors]

I just loaded your UAV onto a spare board.

go into System / HW / Channel Number and switch channel 5 and 6. 5 should be flight mode and 6 collective. You may have to redo Manual Calibration or something else to make that work, I don't know.

[TheOtherCliff]

There are some guys out there that have working setups.  One way to figure this out would be to start with a working UAV file (as absolutely few things changed as possible to start with) and change a few things at a time until the problem showed up.  Then change those one at a time and figure out exactly what change causes the problem.

From all the very strange things that happen (collective goes negative, motor stops, motor restarts without moving the Tx stick, momentary system health warnings, etc.) it sounds like it could even be a program crash / reboot.  CC3D is very low on memory, and I'm not aware of what has and has not been tested for "out of memory" with some of the extras (e.g. Camera Gimbal, GPS, TxPID, etc.) that are available.

[suzali]

@daveapplemotors: just changed channels --> same result   

[daveapplemotors]

How about grabbing one of my UAV files. I am using satellites but do you want me to get a recent radio UAV? I switch to sats recently.

What ever file you use:

Before you connect the flight battery change all the System / Actuator Settings / Channel Max values to 1650 if over 1800 and up to 1350 if they are lower. Same for Channel Min values. Increase them gradually while working in System with flight battery connected. (I don't like the Swash Leveling routine in Configuration / Vehicle because it crashes servos at top speed).
OR
Copy and paste your Max, Neutral and Min values for the first 4 channels.

Then
do Configuration / Inputs / Manual Calibration of TX

If you change only those data it should work.

I feel your pain. I spent a week or two on my first CC3D board last May before I could test fly.

[suzali]

How about grabbing one of my UAV files. I am using satellites but do you want me to get a recent radio UAV?

Thx. I'll give that a try. Please attach / send a UAV.