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.
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:
Cube Red is a mature hardware, but the community support in the software is still early days.
It is not a plug and play device, and will require Ardupilot collaboration with experienced developers.
Definitely use Ardupilot and Mission Planner as the software paths, its too early for PX4, and the focus is definitely ardupilot.
At this stage it is two autopilots… how you choose to use them is up to you. a future software will also allow you to use it as a standard cube.
Hi,
For me both cores will need to collaborate because I need 8 PWM outputs, which goes via the IO STM32H7 (2nd core). While the primary core has all the good stuff (compass, barometer etc.). I understand that the HW is mature but that the SW still needs development to have the device functional as one standard cube instead of two separate entities.
I’m not an experienced Ardupilot pilot developer and I’m hesitant to rely on beta software versions for my systems. One of the main reasons to choose the red cube was the double-precision and the available ethernet port. I wished that the SW was more mature to better suit my application.
Many thanks for the follow up of this topic.
Regards, Quincy
All cubes have double precision FP… it’s the same processor as orange.
Orange has Ethernet with the CubeNode eth as the interface, and is mature and cheaper anyway.
I really recommend you use Ardupilot and orange plus.
Heading down a developer path and going blending edge is not advisable on a commercial project.
What you are trying to do with Red, is treat it as an Orange… but it’s not an orange and serves a different purpose.
