Config Error: fix problem then reboot

Cube Autopilot
1

Is my cube dead?

I have a cube black in a large X8. It was on 4.0.7. It has not flown in years and I was trying to get it back up and running. I was replacing the telemetry set up with some RFD900X and a TXMOD we recently got.

I recently started getting the SB2 warning when starting Mission Planner. I’ve made sure my parameters are set per SB2. I think my cube is of the age where it would be impacted.
(BRD_TYPE == 3,EK2_IMU_MASK == 7,(or EK3_IMU_MASK == 7 if using EKF3),INS_USE == 1,INS_USE2 == 1,INS_USE3 == 1 ) On 4.4.1 I had EK3 and on 4.0.7 it was EK2.

I also upgrade to 4.4.1. I got the following messages:

  • 10/8/2023 10:38:17 AM : Config Error: fix problem then reboot
  • 10/8/2023 10:38:12 AM : Config Error: fix problem then reboot
  • 10/8/2023 10:38:07 AM : Config Error: fix problem then reboot
  • 10/8/2023 10:38:02 AM : Config Error: fix problem then reboot
  • 10/8/2023 10:38:00 AM : motors not allocated
  • 10/8/2023 10:38:00 AM : RCOut: Initialising
  • 10/8/2023 10:38:00 AM : CubeBlack 00250028 32375110 31383938
  • 10/8/2023 10:38:00 AM : ChibiOS: 17a50e3a
  • 10/8/2023 10:38:00 AM : ArduCopter V4.4.1 (e010f979)
  • 10/8/2023 10:38:00 AM : motors not allocated
  • 10/8/2023 10:38:00 AM : RCOut: Initialising
  • 10/8/2023 10:38:00 AM : CubeBlack 00250028 32375110 31383938
  • 10/8/2023 10:38:00 AM : ChibiOS: 17a50e3a
  • 10/8/2023 10:38:00 AM : ArduCopter V4.4.1 (e010f979)
  • 10/8/2023 10:37:59 AM : motors not allocated
  • 10/8/2023 10:37:59 AM : RCOut: Initialising
  • 10/8/2023 10:37:59 AM : CubeBlack 00250028 32375110 31383938
  • 10/8/2023 10:37:59 AM : ChibiOS: 17a50e3a
  • 10/8/2023 10:37:59 AM : ArduCopter V4.4.1 (e010f979)
  • 10/8/2023 10:37:57 AM : Failed
  • 10/8/2023 10:37:57 AM : Config Error: Board Validation $CHECK_IMU0_PRESENT

I tried going back to 4.0.7 and now get

  • 10/8/2023 10:25:48 AM : Check BRD_TYPE: Failed to init CubeBlack - sensor
  • 10/8/2023 10:25:45 AM : Check BRD_TYPE: Failed to init CubeBlack - sensor
  • 10/8/2023 10:25:44 AM : Initialising APM
  • 10/8/2023 10:25:42 AM : Check BRD_TYPE: Failed to init CubeBlack - sensor
  • 10/8/2023 10:25:39 AM : Check BRD_TYPE: Failed to init CubeBlack - sensor
  • 10/8/2023 10:25:39 AM : Initialising APM
  • 10/8/2023 10:25:38 AM : Frame: OCTA_QUAD
  • 10/8/2023 10:25:38 AM : RCOut: PWM:1-12
  • 10/8/2023 10:25:38 AM : CubeBlack 00250028 32375110 31383938
  • 10/8/2023 10:25:38 AM : ChibiOS: d4fce84e
  • 10/8/2023 10:25:38 AM : ArduCopter V4.0.7 (0bb18a15)
  • 10/8/2023 10:25:36 AM : Check BRD_TYPE: Failed to init CubeBlack - sensor
  • 10/8/2023 10:25:35 AM : Frame: OCTA_QUAD
  • 10/8/2023 10:25:35 AM : RCOut: PWM:1-12
  • 10/8/2023 10:25:35 AM : CubeBlack 00250028 32375110 31383938
  • 10/8/2023 10:25:35 AM : ChibiOS: d4fce84e
  • 10/8/2023 10:25:35 AM : ArduCopter V4.0.7 (0bb18a15)
  • 10/8/2023 10:25:35 AM : Frame: OCTA_QUAD
  • 10/8/2023 10:25:35 AM : RCOut: PWM:1-12
  • 10/8/2023 10:25:35 AM : CubeBlack 00250028 32375110 31383938
  • 10/8/2023 10:25:35 AM : ChibiOS: d4fce84e
  • 10/8/2023 10:25:35 AM : ArduCopter V4.0.7 (0bb18a15)

I have tried clearing the firmware by resetting parms to default then updating to Plane 4.4.1 and then back to Copter4.4.1. I get the same errors. Even when I am on Plane 4.4.1 I see the same issue.

In reading some older posts I checked HW ID page and I don’t think it is picking up any of the sensors.

HWID screen shows

I have screen shots of the HWID screen from some time ago and this is what it use to look like.

I have tried various combinations of resetting parameters, reloading old parameters, but no matter what I have tried I seems to be stuck on these errors.

I have several other old black cubes and they seem fine. Any ideas would be greatly appreciated.

Thanks!

2

I had problem with SB2 showing when micro-sd card was faulty…

3

Thanks I have tried 2 different SD cards both scan disk. Original was 8gb and the seconds was a 32gb. It did write to both creating an APM folder.

4

Hello, I am facing the same issue and I went through the forum and tried every possible ways to solve the issues, changing the firmware above and below 4.4.0 and flashing it , changed it to beta, stable and dev firmwares. Still the problem exists. Should it be hardware problem. if so should I not able to solve this issues without replacing the new? Please help.

5

Unfortunately I never found a solution to mine. If you bought it recently I would contact the vendor and try to work with them. In my case it was a very old cube, we replaced it with a new one. Despite the issue with the one it is still the best hardware out there I think.

6

@oschefer Thank you for the reply, may I know what causes this error and what are the preventive action should be take care in future.