Problem with ArduPlane V2.70 and APM 2.5

[GoogleCodeExporter]

When I boot up Mission Planner 1.2.35 mav 1.0 and access the Terminal, 
everything appears to be connected fine. I am connected at 115200. 

The output in the terminal is as followed:
Open com port
Init ArduPlane V2.70
Free RAM: 2894

and then it sends ? and list all the commands (logs, setup, test, reboot, help).

I then type in reboot (There are many other issues but I figured this might be 
the best way to show the problem).

When I type in reboot I get the following error in the output:
Calibrating barometer PANIC: AP_Bravo::read unsuccessful for more than 500ms in 
AP_Bravo:: calibrate [1].

Does anyone know why I would be getting this error? I have done a Reset from 
the setup screen in the terminal but still have the same issue. Any suggestions 
would be grateful. 

Original issue reported on code.google.com by bgkyle...@gmail.com on 5 Mar 2013 at 2:21

[GoogleCodeExporter]

I wanted to add additional information here. If I connect to the terminal 
interface, go into the testing menu and type in airpressure that is where I get 
the error. The output says:

Uncalibrated relative airpressure
Hit Enter to Exit.
Calibrating barometer - PANIC: AP_Baro:: read unsuccessful for more than 500ms 
in AP_Baro::calibrate [1]. 

So it seems there is something wrong with the air pressure sensor. Is there a 
way to disable the air pressure sensor to possibly get my device working?

Original comment by bgkyle...@gmail.com on 5 Mar 2013 at 5:01

[GoogleCodeExporter]

I am actually having the same issue so if anyone has a remedy to this, it would 
be ideal.

Original comment by Moore.Ma...@gmail.com on 28 Mar 2013 at 7:48

[GoogleCodeExporter]

Same issue here and this 1.4 board was on a quadcopter working fine. I decided 
to put it in a plane and installed 2.7.1 and then it gets stuck initializing 
reporting the same error as above:
AP_Baro::read unsuccessful for more than 500ms in AP_Baro

I'm sure the baro is working because it doesn't complain on the copter.

Original comment by stevetor...@gmail.com on 16 Apr 2013 at 2:03

[GoogleCodeExporter]

I get this error too. As well as problems with APM going into failsafe even 
with RC connection. Read here:
http://diydrones.com/forum/topics/wired-apm-2-5-behavior-need-some-help

Original comment by tub...@gmail.com on 1 May 2013 at 10:57

[GoogleCodeExporter]

I have same issue on HobbyKing Apm 2.7.
I measured 5v on i2c connector, so  I throuht it was blown out 3.3V regulator. 
After I changed it I still have 5v on i2c connector and same issue. I even have 
5v when regulator is removed. On output of a new regulator I have 3.3v ( I did 
not test this on original regulator - maybe the regulator replacement was 
useless ).

Any idea?

Original comment by m...@michalfoksa.net on 9 Oct 2014 at 3:19