Hi all.
I'm new to this forum so I hope I'm posting in the right area.
I purchased a APM 2.6 plus ublox GPS/compass unit from 3DR.
I connected to Mission Planner and uploaded the firmware for APM:copter. All looked fine.
Next morning the unit would no longer connect to Mission Planner, but I was able to upload new firmware. To cut a long story short, it was the 3.3 volt regulator that had blown. I hooked a new regulator up externally and supplied the 3.3 volt power directly to pin 1 on the i2c connector.
This fixed all issues except I'm getting "bad compass health" and in the CLI i'm getting a compass init failure.
The weird thing is, I can do a compass calibration and that seems to work fine.
I measured 3.3 volts of power getting into the compass and the GPS has a 3D lock.
Could anyone please tell me if I can tell if my compass is faulty or the APM board. All other internal devices seem to work. Gyro barometer etc. Before the regulator fix, I was getting dataflash errors and no connection in Mission Planner, so my fix seemed to work.
Any help would be most welcome.
Thanks.
Replies
If its something I'm doing then fine. I would be happy.
When this new board turned up, all I did was plug into USB, upload firmware and try compass. Its difficult to see how anything could be messed up.
I'm pritty good with electronics in general and have an amateur radio license, so I would like to think i'm not a complete idiot.
I was running a NAZA before and it worked well. I swapped out to the APM for the open source and reprogrammability side of things.
Shane.
There has to be something to this. People have used and made apm work....we have to just be doing something wrong??
-
1
-
2
of 2 Next