Hi, I have a gps/mag that also happens to have barometer - all of this is on (1) UART MSP connection - and the sensor is on top of the craft, open to the wind. Admittedly, I just realized that this sensor has a baro and have had several flights so far with no issue because, luckily, Ardupilot considers the FC baro as the primary. To add to that, I conformal coated over the entire sensor when I thought it was just a gps/mag.
I started to realize the issue when exporting my logs to Dashware and noticed the altimeter guage bouncing around like a drunk sailor. My csv log export shows two separate baro entry lines sequentially, one for each baro and they are wildly apart in readings - for obvious reasons.
I can figure out how to ignore the second baro in my log exports, but I’m nervous that Aruplane will, at some point, under some circumstance, use the second/external baro reading and drive the plane into the ground. Any way to tell Arduplane to ignore or disable it?
Cheers!
Edit: Corrected the connection type to MSP.