Firmware red cube

Hi,

I wanted to install the Px4 firmware via QGC. But I get an error that the correct board cannot be found. Any ideas. The information from the cube red shows that it is compatible with px4. But on the PX4 firmware git page the cube red is not mentioned as an asset. I tried to install manually the px4_fmu-v3_default.px4 file. But I receive an error on board ID mismatch.

Any ideas? Regards, Jasper

@sidbh one for you.

To start with, I would strongly suggest using Ardupilot. Though there is work going on to add PX4 support, Ardupilot is much more advanced and has significantly more support.

The cube Red hardware is ready. Example code for Ardupilot works.

But you need to decide how your needs line up with the current development path of the Ardupilot team, and work towards a solution.

Cube red is not plug and play, it is a new structure that many UAV developers are working on and there will be many paths chosen.

Ardupilot is open source and it’s 100% up to you to choose how you use it or modify your software.

The hardware, is fit for purpose and we are looking forward how people use it.

1 Like

@sidbh

Hi Thanks for answering.
I believe my assumption is correct that no PX4 firmware is available for the red cube. I also found this thread wrt Qgroundcontrol and the red cube, Cube Red has two flight controllers in the box. QGC can only see one of them on Windows. · Issue #11365 · mavlink/qgroundcontrol · GitHub. Via UDP I can connect to both vehicles (vehicle 1 and vehicle 3). I would expect that when I connect to the red cube via UDP and QGC I only see one vehicle instead of two. But I believe this is something to be fixed by the QGC developers? Any timings on the Px4 timeline?

When I flash the Red Cube with the latest ArduPilot firmware, both the primary and secondary controller. I’m able to set up the red cube with the following configuration:

  • GPS connected and functional to the primary controller
  • RC and PWM outputs connected and functional to the secondary controller.
    However, it seems that the CPU’s are not working together since I cannot arm the primary controller, due to no manual control (RC connected to secondary). However, the architecture describes that there is a communication between the two, cubepilot-docs/.gitbook/assets/Chart-20240202-04.png at master · CubePilot/cubepilot-docs · GitHub. I would expect to only connect to the primary and launch my operations from there. Because the primary has all the sensors for it, 1 xcompass, 2xbarometer and 3xIMU. From the secondary controller I can arm the vehicle when I disable the parameter that allows arming without GPS (ARMING_CHECK).
    Do you have more information to setup the red cube from only the primary controller?