![realflight 7 acro mode realflight 7 acro mode](https://i.ytimg.com/vi/OoB9V9w9QB8/maxresdefault.jpg)
In situations like this, it is not realistic.
REALFLIGHT 7 ACRO MODE CODE
I am sorry if you felt I was dismissing your concern but since this code is so complex, I don’t always trust what a bench test tells me. So I will get his flight data and see if I can determine what is happening. He had mentioned in a PM that he encountered an unrecoverable situation when testing acro leveling mode. Recently and I have been working the Vbar mode that he mentioned. As I said, they share the same attitude controller. I guess you could pull the props but I suspect you would encounter the same behavior. Now with multirotors, you cannot see this behavior like heli’s can with the swashplate. After motor interlock is enabled the flight control laws determine the target attitude from the pilots inputs and attempt to drive the heli to that target attitude. Up to that point, the target attitude is set to the current attitude so when you move and release the stick the swashplate follows your stick.
REALFLIGHT 7 ACRO MODE FULL
The reason you only see this behavior with motor interlock enabled is due the motor interlock causes the full full flight control system to be operational. My suggested throttle curve settings would yield a curve that looks like this, which looks very reasonable for an electric helicopter running ~61% throttle Suggested based on your old curve would be: So these will have to be set to get the desired power. This is what you have in the param export from your 3.6.7 version: These were your throttle curve settings from the 3.5 param file So if you have upgraded from 3.5 to 3.6, but have not actually flown 3.6, also make sure you verify the throttle curve settings are right. Even the throttle curve is different between the two versions of firmware, and I notice you are using Mode 3 throttle curve control in the parameter file you posted from 3.5. So I just wanted to make sure you know that the tuning parameters provided are for Copter 3.6 and newer. But the param file you posted was from Copter 3.5. I don’t understand if and why this is a problem for you… I’m sorry for my incompetence but all this is new for me… My board has installed the last firmware suggested from my Mission planner…