I need help to identifiy the problem with my copter. Could someone please help me to analyse my log file?
The full story:
In February my copter crashed during a mission after the RTL comand and landed with 19 m/s in the field. It first yawed away and lost altitude. When I tried to rescue it in loiter and stabilize I first managed to bring it back ~100 m into my direction but then it yawed away again and lost height. I could not rescue it with loiter, brake, RTL or stabilize full thorttle, it just smeared off.
I originally thought this was due to interferences on the site because I had problems on several days at this site but not on others. Also I had problems to process my RTK GPS logs because of a teribble signal to noise ratioon the ground and in the air. I had to fly there to get the data and it was very far from people, so the risk was justified in case you think I’m stupid (I am because I did it for free for a student but that is another story).
I have now rebuild the copter and replaced the motors and after testing the flight controller and the motors etc. on the ground I did several successful hoverflights this morning. Then I went to the field for a mapping flight and there I faced again several problems (the copter did yaw away, it did not respond to throttle input, it did not hold altitude in loiter mode) and I could not fly. After some trials I finally crashed again… . I also saw that the motors randomly do not spinn up during motor test.
I have several ideas what could be the problem (+ = likely, o = maybe, - = not so likely)
- something is wrong with my transmitter or my receiver
1.1. my transmitter is damaged and does not transmit the singnals (-)
1.2 my receiver is damagend and sends wrong information (o)
1.3 I some how messed up the channels and calibration of the tx/rx (o)
- the flight controller is damaged (o)
- the flight controller is wrongly configured (+)
3.1 problems with the pwm output (+)
- the escs are damaged (+)
- the escs are not calibrated anymore (o)
Any help is very much appreciated, thank you!