[jbarchuk]

This is really a simple generic CC3D Q but since I'm applying it to a fixed wing I ask it here rather than multirotor where there are many more topics and people. MAYBE it's not impossible that the problem is fixed wing-specific? I tend to doubt it but at the moment I'm stumped.

The only other thing I can think of is that I'm not cycling power and plugging/unplugging things in the right order.

Synopsis: In Input - Stabilization Modes Configuration I'm trying to set a mode to manual-manual-manual. It initially WORKS but later Saving to the CC3D it's not 'sticking.'

I'm sure that my flight mode switch setup is working. When I switch my Tx mode switch I see the CC3D blinky rate on the CC3D change. In GCS Input - Flight Mode Switch Settings - Pos 1/2/3 reflects my change on the Tx switch. Cool.

Here's the exact order that I'm doing things, from an 'all power off all plugs unplugged' state...

Turn on Tx.
Plug battery power into plane -- wait for the blinkies on CC3D to settle down.
Plug in USB.

At that point the current setup in CC3D is downloaded to PC and displayed in GCS. Cool.

In GCS - Input - Stabilization Modes Configuration I change Pos 3 to manual-manual-manual.

Now here's a CRITICAL POINT!! In Pos 1 (attitude-attitude-axislock) when I shake the plane the FC is actively working the surfaces. Cool. WHEN I SWITCH TO Pos 3 THE ACTIVE STABILISATION STOPS!! I wiggle the plane and there's -no- action on the surfaces from the FC. VERY COOL!! Yes the Tx actively controls the surfaces. Very cool. Home free, eh? Not quite. 

I click Save and the icon changes to Red telling my that I need to cycle power on the CC3D.

Unplug USB.
Unplug plane battery.
I even power down the Tx.

Turn on Tx.
Plug battery into plane.
Set Pos 3 (manual) but it's NOT manual mode. I wiggle the plane and it FC is in control and the surfaces wiggle.  Not cool.

I'm can't think of where to go with this next.

[jbarchuk]

I don't know if this might be vaguely related to me previous Q about flight modes not sticking. It's a different 'sticking' issue so in that sense similar.

I have a pizza box flyer that flies very slowly at a very high AoA.

I initially did a level calibration flat on the ground and that seemed to work.

But I need the in-flight AoA to be around 20 deg. (That's an intuitive guess for first flights.)

So I set the plane on the floor and use a phone app to tip the nose up to 20 deg.. The Flight Data screen says the nose is severely tipped up. Cool.

I press the Level button and let it do its thing. There's no clear and obvious 'done' message but when the progress bar says 100% and it doesn't do anything else for a few minutes I figure that's it.

The Flight Data screen says the horizon is level with the nose still tipped way up! Cool!

I press Save and get the Red-X button so I know I need to cycle power on the FC. Power up Tx. Power up plane.

I have two pieces of evidence that the 'level' isn't set to '20 deg.'

I plug in USB and after the FC blinkies settle down I set the plane down and the Flight Data screen says the plane is level when it's physically level. When I tip the nose up to the 'preferred level' of 20 deg it says it's severely pitched up.

The other thing is that I half expect that when the plane is physically level the elevons -should- be tipped up. Meaning that even though the plane is not moving the FC is trying the get the nose up.

Any clues?

[f5soh]

Hi,

Please post your config file and i look if i can reproduce here.
File > Export UAV settings

Laurent

Edit: Joined the two posts, same issue.

Save from FlightMode tab or save in Attitude tab do not need a reboot and should not display a red cross. If show a red cross there is something wrong...

[jbarchuk]

A detail on the Red-X warning. Of the two kinds of Saves I tried the warning was a little different. The first problem about changing the Flight Mode produced a -brief- Red-X, then changed to the checkmark. The Level change displayed a solid Red-X that never changed.

I made two slight changes to my procedure. I'm using a tower style PC. I was using a front panel USB port, and also using a USB extension cable so I could set the plane on the floor. I know either of those two things can sometimes produce problems. So I put a small table next to the PC and used a single back panel USB port. Unfortunately that caused to positive results. 

I'll add the *.uav here as an attachment.

Thanks much for your interest.

[f5soh]

Found

After you set the Arming setting to "Always Armed" you cannot save settings.

[jbarchuk]

Bingo! Thanks. Now I remember that detail but it's been a while. All Saves work now. Still having an 'issue' but I need to explore more before I ask another Q.