Po case opat zdravim!....
Tak po obetovani nikolkych tyzdnov zivota som sa nakoniec dostal k vysledku s CC3D, problem je v tom, ze OpenPilot prestal davno podporovat stary hardware CC3D, ale Cina to stale aj nadalej klonuje a to je dovod preco boli odstranene z internetu VSETKY manualy a helpy ako nastavit CC3D....
Vdaka Bohu sa stale nachadzaju utrzky informacii po inych forach vdaka ktorym som bol uspesny:
- je mozne obratit Throttle (Futaba system) takze hra so standardom (pisal som o tom v inom vlakne), dokonca sa da
"natiahnut" alebo "skratit" interval, napr: input 1150..1850 z RX na 1000..2000, pripadne reverz na 2000..1000
- je mozne nastavit pre lietadlo FailSafe ze lietadlo zostane kruzit vo vzduchu a ocakavam ze prirodzene "sadne" ked dojde bateria - prehodi sa do modu riadeneho horizontalneho letu do kruhu...
zaver: som s tym nadseny!
a tu su VSETKY informacie z ktorych som cerpal (vlastny navod este nedavam, je to prilis cerstve a stalo to vela namahy

pokial bude niekto mat otazku rad odpoviem, myslim si ze za tych par tyzdnov co sa venujem lietadlam koli
6r synovcovi som celkom pokrocil

*************************************************************************************
urob erase pomocou rescue!
SAVE funguje iba pri beziacom TX - platne signaly na RX, cakaj vzdy 20 sekund po kliknuti
Throttle musi byt dole aby fungovalo SAVE (-1 ALEBO NEUTRAL 0 ? )
Musi byt Always Disarmed aby zapisal SAVE
Po zapise Always Armed & timeout 0 sa musi urobit power off/on inak nearmuje
Upload&Erase cakaj 1 minutu
Trottle neutral musi byt 10..20 vo vnutri intervalu na strane minimum (1000,1020,2000)
Ak nebude armovat skus zopakovat Vehicle Config
ESC throttle sa da konfigurovat cez manual test output, zakliknute a tahat z max do min po 2x beep z esc do 5 sekund!
(CC3D je napajane z usb a pripaja sa baterka koli ESC)
Skontroluj throttle v datach ci ide -1..0..1 a nie 0..1, da sa vidiet aj na grafickom
zobrazeni, po malom posune z nuly by mal skocit do stredu a zvysok linearne do max
(urob wizzardom kalibraciu a pozri co tam da, daj do stredu aj throotle ako ziada! )
Pozri ci nie je nejaka chyba v konfiguracii kde je NO LINK okno vo firmware tab
pripadne v dataobjects SystemAlarms
When you have an error (here with config) you can click on AlarmSubStatus and see complementary info about error
**********************************************************************************
Also if your RcTransmitter is not stable (temperature, voltage) you can increase the minimal value for Throttle (like +5) and with that you are sure the "-1" value is ok, be sure your neutral still 10/15 up from mini
*********************************************************************************
MOJA SKUSENOST:
TO FIX: With the CC3D attached to the usb I go to Firmware, Halt the board, Erase the settings, reload the firmware. Then, I go to the Vehicle Setup Wizard and go through the complete setup from start to finish including the setup for the Transmitter. I save the settings, then I change the arming settings from "always disarmed" to "Roll Right" and hit save. (IMPORTANT: if you test right now, it will not work, roll right does not arm the motors, you will be frustrated) !!!!!!!!!To completely fix, you have to disconnect the power from BOTH the USB port AND the battery. Upon powering up the board, Roll right arms the motors and you can fly.!!!!!!!!!!!!!
TO BREAK: Go to RC Input Screen, push Manual Calibration Button. It resets the arming setting to 'always disarmed'. At this point, it's broken, the only way to power up the motors is to select "always armed".
Administrator (FlyMeARiver) is correct, unless you go to the firmware tab and start by erasing the settings, nothing will fix this situation.
*********************************************************************************
PLEASE READ! KOREKTNY RESET:
Uninstall any previous versions of OpenPilot GCS
Install the latest OpenPilot GCS version you just downloaded
Open OpenPilot GCS to the Firmware Tab
With the board unplugged, click the Rescue button
Connect the board
(There's a chance that the new drivers might not finish installing before the timer runs out. If this happens, wait until the drivers finish their install, then unplug the board, click Rescue again, connect the board and continue)
and click the Erase Settings button
Wait approximately 30 seconds
Click the Auto Update buttton and follow the on-screen instructions
Click on the Welcome Tab (at this stage you can continue with the Vehicle Setup Wizard or you can cancel out of it for manual setup.)
Click on Vehicle Setup Wizard and follow the on-screen instructions. You can skip the Upgrade step since you already updated your FW (the wizard will be updated soon to include Erase Settings).
**********************************************************************************
If I were you, I'd erase all settings using rescue mode on the Firmware tab and start fresh.
***********************************************************************************
- move all sticks at max on every directions (switches included), it defines max/min values for every channel,
- center all sticks and throttle at 0 : it defines neutral point,
- Stop manual calibration : !!!!!!!!!!!!note that Throttle is automaticaly increased a little from normal neutral value to be sure that 0 value or negative value is reached or arming can't be done...!!!!!!!!!!!!!!!!!!
- Save
**********************************************************************************
Make sure when setting your flight modes, that you aren't using cruise control with rate. I think that was the one you can't use cruise control with. If you set it, then your motors won't arm. This happen to me and took me a min to figure out.
Check your flight modes.
*******************************************************************************
Mine was something like:
From FMS Pos. 1, 2, 3 Stabilize 1, 2, 3 = Bank 1 to:
-- Pos. 1/Stab1/Bank1
-- Pos. 2/Stab2/Bank2
-- Pos. 3/Stab3/Bank3
Stab Mode Config:
Stab 1 = Atti/Atti/Manual/Cruise Control
Stab 2 = Atti/Atti/Manual/Cruise Control
Stab 3 = Rate/Rate/Manual/Cruise Control
Not working/arming afterwards but when I redo Vehicle Config it will work (same settings above) again.
********************************************************************************
Let me add something as well. Yaw: Manual with Thrust: CruiseControl will not arm as well.
*******************************************************************************
Maybe I missed it reading here, but first thing I would do is look at the system health in your flight data tab. If you see "config" red, that you have some error in your config. If it's green you need to search elsewhere.
*********************************************************************************
When the board is set to always armed, then you cannot save anything. So make sure that is not the case.
*********************************************************************************
Another thing - some transmitters drift when they get warm. Maybe everything is sweet when you're inside where it is cooler, but when you're out in the sun, the Tx warms up and the end points can vary such that your low throttle is now out of range of the set "low".
If this happens again, go to the Inputs tab and bump up the throttle neutral a count or two. That should help.
********************************************************************************
One VERY important thing to remember is when erasing all settings on the firmware tab, the CC3D takes around 15 to 20 seconds to complete the process. It is not fast like a revo which is a few seconds.
You MUST leave it to reconnect on it's own.
I have found out that some people click the button and then remove and reinsert the USB plug to start again.
Just wait for it.
Also - when saving settings, wait a few seconds before you disconnect.
**************************************************************************************
RodersNZ - Thanks for posting. I'll wait 20 seconds between saving the data and clicking disconnect... Then wait another 20 seconds before removing the Cable..
***********************************************************************************
Make sure you don't have any of the autonomous features set on the Flight Mode switch settings (position hold, altitude hold, path follower, etc). They aren't usable with the CC3D, and will cause an error and prevent arming.
***********************************************************************************
"What are your flight modes set to? a screenshot would be nice. Have you got cruise control set on anything other than attitude or rattitude? If you have you will not be able to arm
**********************************************************************************
You can check if values from sticks are ok.
Go in UAVbrowser tab > Data > ManualControlCommand
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
To allow arming, Throttle should be equal to -1 at minimal position and Yaw (for example) need +1 / -1 values at full stick left/right
***********************************************************************************
You can read the values for throttle (and yaw assuming typical setup) on
system -> data objects -> ManualControlCommand
Throttle must be -1 and yaw must be +-1 for the typical arming sequence
It also won't arm if there is an alarm. Look in system -> data objects -> SystemAlarms
to determine if there is an alarm and what it is on.
*********************************************************************************
You also need to drop the maximum value on your throttle curve to something like 0.9. Search forums for "throttle curve" to see reasons why.
********************************************************************************
I found that if you have thrust set to AltitudeVario or AltitudeHold the motors wont arm .. but in CruiseControl or Manual they will.
********************************************************************************
I found the only Thrust option that will permit arming is Manual.
********************************************************************************
Make sure you don't have "cruise control" set to any mode that isn't stabilize or rattitude.
********************************************************************************