I've been flying with a Pixhawk for a little while and probably getting away with the minimum amount of knowledge required to make it work.#
After a recent crash (which involved the Pixhawk) due to a lack of elevator authority (see the DIY drones discussion here: http://diydrones.com/group/pixhawk/forum/topics/could-you-please-help-analyse-this-pixhawk-crash-with-log?xg_source=activity) I decided that I wanted to make sure everything was a'ok with the Pixhawk prior to flying again.
I've recently completed a new plane build and am now installing the Pixhawk. Unfortunately a few error messages have come up and I was wondering if there is a problem with the Pixhawk itself (perhaps due to the crash or just that it's broken) or with my set up.
For background I have gone through the Wizard set up in Mission Planner but still have the below issues unfortunately. If you are able to help then that would be amazing! :)
The issues are:
1. Compass issues - error compass variance and bad compass health - the error compass variance seems to come up randomly and generally when I'm moving the board around. The bad compass health seems to also come up randomly although I'm not sure if it's ever present as when I take the board outside to acquire a GPS signal the bad compass health message seems to stick around.
For background I have the Pixhawk pointing to 270 degrees clockwise to the direction of movement and the compass pointing in the direction of movement and therefore 90 degrees clockwise relative to the Pixhawk.
I've therefore set AHRS_ORIENTATION to 6 (Yaw270) and COMPASS_ORIENT to 2 (Yaw90).
I've gone through the compass calibration and it seems to be accepting this.
2. Bad gyro health - this has only come up once and I read here (https://3drobotics.zendesk.com/hc/en-us/articles/201771859-What-to-do-if-I-m-getting-a-Bad-Gyro-Health-warning-on-my-Ground-Station-) that it could be due to a blown 3.3V regulator on the board. I have tested the outer pins on the I2C connector and am getting 4.90V when it seems that this should be reading 3.3V?
Could this also be affecting the compass as it is plugged into the I2C connector?
3. Velocity variance - this is also only occasional and I notice that when I click on the EKF button in Mission Planner that usually the velocity bar is either 0 or very close to it. However, at certain times this does jump up to above 0.8 when it causes a failsafe failure on this parameter.
Thanks for taking the time to read through this and any thoughts you have on any of the issues would be much appreciated.