I am currently running a pixhawk on Arduplane version 3.3.0beta2 and have just setup a new plane. I did all the basic tuning and have the plane flying very well in FBWA, airspeed sensor calibrated, min and max speeds set, and would like to start tuning the L1 Nav.
The issue I am having is in any auto mode the plane does not have any clue what way it is going and it goes crazy. I tested RTL and 2 different auto missions an dhave the same problem both times.
Each time I get bad compass health errors, but, even with bad compass health errors it should be able to revert to GPS data and atleast be able to complete a circle.
I thought originally it was a motor interference issue, but, on the ground the compass works perfect at all levels of throttle and even when fluctuating throttle.
The compass calibration has been done multiple times and on the ground the compass points perfectly in the direction the plane is facing.
The Pixhawk is a genuine 3DR with the genuine GPS/Compass module.
The only things I can think of is the RFD900 radio's are too close to the GPS/Compass? they are about 10 inches from eachother, but, there is no issue on the ground and the RFD900 is transmitting that whole time.
The only other issue I can think of is possibly the BEC on the ESC that is powering the pixhawk is not a stable voltage supply and is causing interference that is messing with the I2C port? We have a twin engine plane and are using one BEC for powering the pixhawk (6s so can't use the 3DR power module) and one BEC powering the servo rail.
Here's some Tlogs, rlogs, and .bins of the problem.
Any help is greatly appreciated!
Replies
Finally after 3 days of frustration figured it out! A sharp solder joint was poking through the heat shrink and shorting two of the GPS wires. For some reason there was no signs of an issue besides when it was in the air reporting bad compass health and unusually low HDOP numbers (<.7)
Good detective work!