@Verloop, I think there are a couple of parts at play here.
Manufacturer: Pixhawk is a trademark and it seems every version of “Pixhawk” are made by different companies. That said you should expect different levels of support depending on the company that is manufacturing whatever version is being sold. It might be advisable to consider the manufacturer when choosing a flight controller, no matter the marketing number.
Maturity: The Pixhawk 2.1 is quite mature and well documented and supported. Any newer board is considerablely less tested and mature. This does not make it inherently bad but know the risks.
Actually the XT-60 connectors can probably handle more continuous current than the board itself. Running 120 amps thru 10AWG wiring is not realistic. Look at the size of the battery cables on your car to handle a starter motor that draws 100-200 amps. Does anybody actually think you can put one of those power modules inline to the starter in your car and start your car with it?
The 120A “rating” on the power module is what is the joke. It might handle that for a couple seconds before it overheats and permanently damages the tiny shunt on it. But those couple seconds are not going to hurt XT60 connectors.
Unfortunately other unscrupulous manufacturers and organizations use version numbering in the product name as a marketing tactic intentionally misleading consumers to inferior products. They know people will naturally assume version 4 is leaps and bounds better than version 2.1. And most consumers know very little about the hardware they’re buying to even know better if they read beyond the name.
I noticed that ProfiCNC / Hex has wisely stopped using numbers in their products. It has a name, like the Cube Black, Cube Orange, etc. So “those other guys” can’t create a Cube v5 tomorrow and pretend it is better.
Sorry. There seems to be confusion as to what “Pixhawk” is. Pixhawk is PX4. ArduPilot just runs on the PX4 hardware, which has historically been based on PX4 reference designs. But it doesn’t have to be. ArduPilot can run on darn near anything. ArduPilot is not officially related to Pixhawk in any way, shape or form. It is just one trademarked family of controllers that it CAN run on.
So comparing Pixhawk 4 to Pixhawk 2.1 (now “Cube”) is not a valid comparison. They are not the same thing. The Pixhawk 4 is not a new version of the Pixhawk 2.1. The Pixhawk 4 is the newest version of the PX4 reference design. It was designed to run PX4 - ArduPilot was ported to run on that board. ArduPilot supports over 20 different boards and that number is growing all the time.
Anybody can do a custom board and run ArduPilot on it. If you need starting schematics go to PX4io and use the PX4 reference design (have to give them credit for using it and adhere to the license for it). Or design your own from scratch.
If you want to sell it, it’s up to you to market it. ArduPilot is not in the hardware business.
I think a lot of the confusion stems from the fact that the Cube makers originally used the Pixhawk trademark, so it was associated with Pixhawk and called Pixhawk 2.1. But they are trying to get away from that and rebranded it “The Cube”.
So the Cube and Pixhawk 4 are two totally different vendors. The Pixhawk 4 is a PX4 reference design - it is manufactured by HolyBro. The future of the Cube will likely be independent of PX4 - it is manufactured by ProfiCNC/Hex.
There is, however, significant differences in the hardware in the Pixhawk 4. It has a more powerful processor with double the RAM of the fmuv3. It has dual IMU’s instead of 3, single baro and compass instead two, etc… The fmuv3 design went overboard with multiple sensors that really do no good because the internal compasses can’t be used anyway in most cases. It’s hard enough to get two IMU’s to agree, much less three. Baro failure or drift problems can failover to GPS, etc… So fmuv5 went away from that.
I just wanted to make some points for anyone else reading this thread. But first I want to say that I have absolutely no experience with the Pixhawk 4 and I’m currently using a Cube which is working perfectly.
That being said, I am actively researching and collecting data on ALL flight controllers that can run Ardupilot.
Why do I find the Pixhawk 4 interesting?
As @ChrisOlson mentioned, it uses a newer, faster processor, has more RAM, and is based on fmuv5 instead of fmuv3
At 15g, its LIGHT. This is important to me because I’m trying to design and build drones with extended flight times for photography, cinematography, and search and rescue.
The design is interesting because, as @Verloop mentioned, it has a rather large power management board. However, it looks to me like this board is also your power distribution and servo connection board. Someone please correct me if I’m wrong, but it doesn’t look like there are any servo connections/outputs on the flight controller itself, but there’s a 10 pin cable that runs to the power board and you connect your ESC/servo wires to it. If that’s true, it sounds to me like another way to save weight, and have less wiring.
The missing GPS units sound like a vendor issue completely unrelated to the actual performance of the Pixhawk 4 itself. @Verloop please let us know if you go ahead and actually test this flight controller. Also, please confirm if the flight controller itself has no servo connections.
Just to eliminate any confusion others coming to this thread might have, here’s the Pixhawk 4:
First of all, yes, the missing GPS is vendor related. Actually, they responded to our email about the missing item and it now turns out is is NOT standard included, although the picture on the website during ordering shows what will be included in the package. So today I will order 2 GPS units.
Secondly, yes, the flight controller doesn’t have servo connections.
Personally I think that is an advantage. I think many times people want to power all servos from the servo rail on the Pixhawk. It simply cannot handle the currents drawn for larger servos on bigger airplanes.
The servo connectors are on the Power Module board and they also include 2 smaller extension boards, so you can chose your option.
But another problem is that I cannot find any information on the pinout of the connectors on the flight controller. How to determine rx and tx on the telemetry connectors for example.
I Googled all over the place, nothing…
I will go ahead and test, but currently not as a priority. I need to make up my mind whether to make the transition from Cube to Pix4.
You’re correct on that. But I don’t personally like that design. It’s quite messy IMO. I like the servo rail built in on the board like the Cube or CUAV V5 has. These controllers don’t power from the servo rail anyway anymore and the design of the rail is such that it will handle modern HV servos with no problems (I fly them in helicopters).
To me, that external servo rail/board is just another point of failure that does not stand up long-term, at least in helicopters. I have yet to ever have a problem with a built-in servo rail on APM’s, Pixhawk1, Cube, CUAV V3 or V5.
I have a Pixhawk Mini (now discontinued) that I briefly tested in helicopters. It has an external servo rail like the Pixhawk4. I decided that controller might be ok for multi-rotor aircraft but I didn’t like it for heli’s. The IMU damping in it is not all that good.
I also have a Pixhawk4 but I haven’t flown and tested it yet.
FYI, the Pixhawk4 can only run ChibiOS builds on ArduPilot - it is not supported by the NuttX firmware builds. The firmware for it is the generic fmuv5 build. On PX4 the Pixhawk4 runs NuttX.