Bunch of orange cubes start to fail

Cube Autopilot
1

Dear,

we are using the cube black and oranges in our fleet for drone shows. They are very reliable! Kudos. Though lately we have been plagued with an issue:

[MAV 174:1] Config Error: fix problem then reboot
[MAV 174:1] Config error: Board Validation $CHECK_BARO1_PRESEN
[MAV 174:1] T Failed
[MAV 174:1] Config Error: fix problem then reboot
[MAV 174:1] Config error: Board Validation $CHECK_BARO1_PRESEN
[MAV 174:1] T Failed
…

We have already 4 that are failing like that. And we have no idea why. They fly happely and correctly do shows, but suddenly we try to use them again and are greeted with this error message. We started with one such cube. That could be a fluke, so we didn’t think a lot about it. We investigated and for some reason the barometer is bad. So we voided warranty and replaced it, which worked.

Though now we have already 4 of those and we don’t want to replace all those barometers and voiding warranty. It starts to look systematic and therefor we are now investigating what the reason is.

Does CubePilot has experience with this error? Is this maybe a problem in a specific batch of orange cubes? Or do you have any idea how this can be triggered, so we can make sure we don’t have more cubes dying on us.

Thanks!

2

What firmware did you install?
It looks like you loaded an old parameter file from one of your Cube Blacks.
That is not a supported function.

3

Currently we have ardupilot 4.1.5 on it. But I can try stable.
So you think there is a wrong setting in the parameter file? Interesting, I have not though about that.
Do you know which? Or should it be solved by resetting all parameters? (How can I do that?)

Thanks!

4

I don’t think the parameters are the problem.

I updated to 4.4.0 and tried all parameter reset options in
https://ardupilot.org/copter/docs/common-parameter-reset.html

But sadly without avail; I’m still getting the error:

[MAV 001:1] ArduCopter V4.4.0 (502702df)
[MAV 001:1] ChibiOS: 1ec9f168
[MAV 001:1] CubeOrange 0032004B 3230510B 34373234
[MAV 001:1] RCOut: Initialising
[MAV 001:1] motors not allocated
[MAV 001:1] Config Error: fix problem then reboot
[MAV 001:1] Config Error: Board Validation $CHECK_BARO1_PRESEN
[MAV 001:1] T Failed
[MAV 001:1] Config Error: fix problem then reboot
[MAV 001:1] Config Error: Board Validation $CHECK_BARO1_PRESEN
[MAV 001:1] T Failed

5

@Hannes_Verschore Have these Cubes been opened?
Is this issue on CubeOranges or CubeBlacks or both?
Can you enable LOG_DISARMED and share the logs?

6

Sorry about the delay.

The cubes have not been opened and the issue is present on Cube Orange and blacks.

I’ve tried running with LOG_DISARMED, but wasn’t able to get a log out of it. Could it be that the logging didn’t start because of the error. I’ll let one of my engineers try next week again.