Bad Baro Health / Bad Gyro Health

Maybe the logs from a bench test would be enough to diagnoses the problem.

Same issue. Dont have a gps so cannot comment on that aspect but the pressure sensor has the same problem, unless i install arducopter 3.xx or arduplane2.xx. With Arduplane 3.xx installed airpressure does NOT work, gives bad health.
Thank you

Hello,

I have attached the dataflash log from my APM2.6.

I flashed APM:Plane 3.1.1 and let the APM sit on the table.

Please let me know if this is fine.

[attachment=0]Arduplane 3.1.1.log[/attachment]

Thanks,
Madhu.

Hello,

Just to test a wild theory, I uploaded APM:Copter 3.1.5 to my APM and the baro test works flawlessly.

Any idea whats going on?

Thanks,
Madhu.

Hello,

Can anyone shed some light here?

Thanks,
Madhu.

I also experienced the same thing. the message was “not healthy”. When I changed the firmware to 3.03, the airpressure test workin, but the values doesn’t changed. Finally I upload the lastArducopter firmware, and the baro test is working without problems.
Is the last APM Plane firmware is safe?

Hello ArduPilot team,

What other information would you need to resolve this issue?

Thanks,
Madhu.

Hello,

Does anyone have any idea that may help resolve this problem?

It looks like I am not the only one facing this.

Thanks,
Madhu.

When will 3.1.2 be out?

Mike,

I dont even think anyone is looking at this. :frowning: :frowning: :frowning: :frowning: :frowning: :frowning: :frowning:

Regards,
Madhu.

I have Bad Baro Health also, but the warning only shown for about 10 to 15 Seconds. Is the warning only shown on that period of time only?

I just discovered that I have the same problem guys.
Appreciate the hard work from the tech team and I hope there comes a solution soon.
Cheers.

Metal objects near test área will affect APM sensors…

copter.ardupilot.com/wiki/prearm_safety_check/

Hello all,

I have come back from a hiatus and uploaded APM:Plane 3.2.3 onto my APM 2.6.

Same issue. Mission planner reports Bad Baro Health.

I have attached some Log files of me moving the APM vertically about 5 times.

Can anyone please have a look at them and tell me if my APM is flight safe?

Thanks,
Madhu.

I will have a look.
Thanks, Grant.

I have been unable to replicate this. I have tried with the latest
APM:Plane code on my APM2.5 both with the GPS connected and the GPS
disconnected but I can’t get the “Bad Baro Health” message to stay in
the hud. It comes and then goes after the calibration is completed as
expected.

@Madhu - Can I confirm you have a GPS connected? Have you installed
the latest version of MissionPlanner?
Do you need to move your APM vertically to trigger the issue or does
the “Bad Baro Health” message appear immediately when you power your APM and
never go away? Please replicate the issue and let the APM run for 2
minutes. Then please attach BOTH the tlog from MissionPlanner and the
data flash log (.BIN)?

@zhoter - this is normal as the APM goes through a barometer calibration on startup by default.

@feket663 - the latest Plane release 3.2.3 is as safe as we can make
it :slight_smile:

Thanks, Grant.

I also noticed you had your magnetometer disabled i.e. MAG_ENABLE=0. Any reason for that?
The code will set this to 0 if it doesn’t find a magnetometer. Did you have one plugged in?
Thanks, Grant.

[quote=“gmorph”]
@Madhu - Can I confirm you have a GPS connected? Have you installed
the latest version of MissionPlanner?
Do you need to move your APM vertically to trigger the issue or does
the “Bad Baro Health” message appear immediately when you power your APM and
never go away? Please replicate the issue and let the APM run for 2
minutes. Then please attach BOTH the tlog from MissionPlanner and the
data flash log (.BIN)?[/quote]

Grant,

I did not have the GPS connectd since I was in the basement
I do have the latest version of misison planner installed
I dont have to move the APM; Here is what happens after I click on the connect button:

  1. the Bad Baro health message appears on the HUD
  2. about a minute or so later, the message disappears.

i can understand if this is pre-calibration; but, why would the CLI (prior to 3.2.3 but after 2.78B) show not healthy?

I have attached logs to this post.

Thanks,
Madhu.

The CLI is being depricated and I never use it myself. If the message is disappearing on the HUD then I’d say the baro is being calibrated correctly and all is well.

Thanks, Grant.

[quote=“gmorph”]The CLI is being depricated and I never use it myself. If the message is disappearing on the HUD then I’d say the baro is being calibrated correctly and all is well.

Thanks, Grant.[/quote]

Grant,

Thanks a million for your input. However, did you get a change to go through the files?

Thanks,
Madhu.