$CHECK_BARO0_PRESEN Error on Cube Orange+

Cube Autopilot
1

Hi All,

I’ve recently encounter an error on 2 out of 3 Orange + Cubes. When I power on the cube, I get an error message: $CHECK_BARO0_PRESEN

image
image511×270 7.85 KB

I’ve seen other similar posts, like this one, and this one, and my presenting issue is essentially the same. I didn’t see any clear resolution shared - there were mentions of opening the cube and finding faulty pins, etc… But I also wanted to add one additional item I tested.

For diagnostic purposes, I disabled the board validation by setting BRD_OPTIONS=128. Then rebooted the cube… and everything boots perfectly fine. The error is gone, and all BARO readings are stable and accurate, BARO_Health=1. If the BARO is actually operating correctly, why is it failing the board validation on startup?

For some background:

  • The first cube that failed with this error was on a drone that I was testing in the lab. I had been working on it all morning (testing a companion computer setup), power cycling as needed for test purposes, and on one power cycle, the cube threw this error message out. Nothing had changed on the cube, no params…
  • The second one is on a system that was out flying all day, stored in the back of a truck overnight (at around 32F outside temp), and when I brought it inside in the morning, the first boot threw this error message. I thought maybe temp, or humidity or condensation might be at play… so I let it warm up for 2 hours, then rebooted. Same issue still.

Since the previous posts over a year ago, have there been any new insights into this issue, or do I need to RMA these two cubes and hope the issue isnt present on the new ones I get?

Thanks!