ZeXx86 wrote:
Hi,
the issues in the log are nothing too important - it just indicates that configured mechanical limits could be too small.
For example if you can see Cyclic Ring activated it mean that there was not enough room to perform that fast rotation.
This can be due to small limit - Aileron / Elevator Range or too high Rotation rate value.
Regarding Rudder Limit Reached this can signalize that the model require higher RPM otherwise tail might not handle some harder maneuver. It could also mean that configured Rotation rate is too high or that Rudder Limits are too small or that RPM is too low.
If you are moving with the sticks at the ground then this events are not important at all.
If High vibration event is logged then it is saved in the memory of the unit. Until the log is opened you will see a different behavior of the swashplate initialization.
For odd Aileron behavior you might play with Cyclic Gain, Elevator Filter and Rudder settings. Very often if rudder is not holding perfectly it will transfer the movement to other axis - aileron.
Thanks for your reply,
The lines I worried about are “ data not available” ,
Is it about the receiver connection?
I increased the elevator filter to 3 due to bounce back after elevator commands,
Should I increase the aileron gain to hold it better?
I’m going to check the tail as well.
Thanks