[SOLVED] Need help with Log analysis

[kgnkazanci]

Hi there,

I set up my new trex 550L dominator today, and I tuned the flight parameters within first 2 flights. Then I flew it and connected to the pc to get logs.
Is there anyone who can explain what do these error logs mean? There is no evidence of erratic behavior of the unit except two instances;
1- The initialization was like something different.
2- There was aileron shift while doing elevator tictocs.

Any help will be greatly appreciated.
Thanks

[ZeXx86]

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.

[kgnkazanci]

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

[ZeXx86]

I have just missed the Receiver signal lost at the end. This could be a problem.

Are you turning off the radio before the battery is unplugged?
If so, this could be a problem.

Alternatively if there are static discharges coming from the belt they can be the most apparent due to take off and landing. This could cause signal loses.

If you are using FrSky radios then this can be just because radio is too lose to the receiver.

[kgnkazanci]

I have just missed the Receiver signal lost at the end. This could be a problem.

Are you turning off the radio before the battery is unplugged?
If so, this could be a problem.

Alternatively if there are static discharges coming from the belt they can be the most apparent due to take off and landing. This could cause signal loses.

If you are using FrSky radios then this can be just because radio is too lose to the receiver.

I tried the fail safe with turning off the tranmitter first at the and of the flight.
My radio is Spektrum dx9, and heli is trex 550L.

Is “data not available” dangerous to fly with?

[ZeXx86]

Ah, in that case it is not a problem at all.

No, it is not dangerous. During battery disconnection the log was not just fully saved (voltage dropped too quickly).
But since this is just from the beginning of the flight any log data are not that important.

[kgnkazanci]

Alright, what a relief I thought that there was something dangerously wrong, it's great to hear that it's OK

Thanks for your support