I have a problem with Arduplane 3.x and Mission Planner. When I run Arduplane 3.x I am getting a "Bad Baro Health" message in the Flight Data HUD and when I run the "airpressure" test in the CLI I get a "not healthy" message. This only occurs with Arduplane 3.x and when I roll back to 2.78b everything behaves as expected.
1. These symptoms are identical with 2 different APM 2.5 boards and an HK Pilot Mini.
2. The 3.3v regulator is OK on all 3 boards.
3. The baro works fine running Arducopter 3.1.5 and Arduplane 2.78b and no fault messages occur.
4. There are 2 attached dataflash logs from 2 different boards and when the NTUN->Alt is graphed it is as expected showing the board being moved vertically
5. When "Scaled_Pressure" is graphed in APM Planner2 it displays OK.
Does anyone have any suggestions?
Replies
See my comments in this thread.
http://ardupilot.com/forum/viewtopic.php?f=102&t=9531&p=301...
Thanks, Grant.
Hello,
Even I have the exact same issue. I had started a forum post here: http://ardupilot.com/forum/viewtopic.php?f=102&t=9531
The thread's last reply was on Sep. 2014; I havent flown since. Even with APM:Plane 3.2.3, I have the 'Bad Baro health' error message.
How do you bring this to the notice of the developers?
Thanks,
Madhu.
I will have a look.
Thanks, Grant.
Exactly same issue but with pixhawk. Works fine in arducopter and arduplane2.xx, but not in arduplane 3.xx
Sandy, I have the same issue, glad to know you documented it so good. Despite Bad Baro... messages, baro seems to work fine.