I am new to quads, but RC heli’s, Electronics, programming etc are nothing new to me.
However, I’ve been looking at this all day and can only come to the conclusion this issues only happens when collecting IMU data, maybe the overhead is just too great to log and control together?
I have built an X frame Quad, D2830-11 1000kv Brushless Motor, Turnigy Multistar 30 Amp Multi-rotor Brushless ESC 2-4S, 10 x 4.5 Props, AMP 2.5 (HobbyKing Version), UBLOX LEA-6H GPS, External Compass, 433Mhz GCS Link.
CompassMot = 3% when I checked it.
I am now trying to look at vibration issues.
I have done 3 tests today in an attempt to prove that the twitching is only when logging IMU data.
Logging ATT - CTUN - CURR - D32 - DU32 - EV - IMU - MODE - MOT - MSG
I have tried removing MOT from this combination and it was the same.
Logging ATT - CTUN - CURR - D32 - DU32 - EV - MODE - MSG
Needs tuning, perhaps a few slight twitches but nothing as bad.
Logging ATT - CTUN - CURR - D32 - DU32 - ERR - EV - GPS - MODE - MSG - NTUN
I have submitted 3 video’s and all three logs to support this.
I have read that IMU, NTUN, and MOTORS Logging does have a significant overhead, however the result is not validated with an expected outcome of doing so.
Just a thought whilst writing this, maybe I should log PM?
Do you think the vibrations are OK, should I move onto Auto Tune and accept the twitching is due to the logging of the IMU data or do you think there is something wrong here?