[DocHardinger]

Hi. Sometimes if i switch flight modes(for example: stabilized mode -> position hold) the copter stops all motors and falls out of the sky...after about 2 seconds it restabilize itself. If i then switch flightmode back sometimes the same behavior...

Anyone know this problem? Any ideas how to solve this?

[TheOtherCliff]

It sounds like either your radio is loosing connection or your flight mode switch is not configured correctly.

Look on the Input tab at FlightMode with everything powered up, and change the flight mode and watch.

[DocHardinger]

Seems to work correctly...any other ideas? Will try to log everything on next testflight...

[TheOtherCliff]

If you are logging and it happens with logging enabled, there will be some things in it that can be looked at.

RC inputs will show bad values, the flight mode will change, etc.

You can experiment with this by switching off the transmitter.

Look in the System -> DataObjects, in ManualControlCommand (Channel and FlightModeSwitchPosition).  You may want to increase the logging rate for these things, but careful to not over do it or it will swamp the telemetry channel.

For a test you might reconfigure the FC failsafe to be Attitude mode with throttle a little below hover power (on a fully charged battery).  Careful.  If you set this too high and loose RC signal it will fly away.  Also, the motors will continue to spin after landing and that means props chewing things on the way down, props tangled in things and burned motors and ESCs and starting a fire.  If it is an RC link issue and that causing an FC failsafe, this will change it from "drop" to "come down slowly" and you will at least know that is your problem.

[DocHardinger]

Where can i increase the logging rate? Escpecially for the input channels? If i do increase the update interval to 20ms in  scopes the graph is smoother but update seems still be a second...

And i discovered when siwtching flight mode Stab status went orange for about one seconds it says "Time Out waiting for an attitude update"...
And Event Status went orange for about one second when switching flightmode to VR and it says "There were problems with UAVObjects events or Callbacks"...


Update:
So after erasing the board and redo all setups except calibration, stab and event stays green now when switching flight mode...Dont know why but it seems to work now...will test it outside when the weather gets better ;-)

Update 2:
Seems to be a problem with update time for "Actuator command"...before erasing everything "MaxUpdateTime" was over 5000ms, now its 9ms. Anyone know why that time was so high before erasing everything?

[TheOtherCliff]

Update rate is part of the MetaData.  System page.  Click the eye at the top and enable metadata.

Now you can go for instance to the metadata for ManualControlCommand and increase the rate.

Generally, when you increase rates, you must increase the OpLink baud rate (both sides) too.  Config page; OpLink tab.