I’ve not had the chance to use a Pixhawk product - all of my ArduPilot work has been with an Orange Cube.
I was speaking with a development team today who does use the latest Holybro Pixhawk products and the subject of Dshot came up.
On the Cube carrier boards, Dshot has to be connected to Aux ports. But as the Pixhawks don’t have these, I was wondering if perhaps the “main” ports on the Pixhawk products were different than the “main” ports on the Cube products - allowing the assignment of Dshot connections to “main” ports on a Holybro Pixhawk product.
I found this post from about 2 years ago that seems to imply that Dshot works on the Pixhawk “main” ports.
Can someone please clarify this subject for me - and maybe point me to documentation that describes the differences (if any) in the Main and Aux ports between Cube and Pixhawk products?
Thank you @geofrancis - I’m admittedly under-educated about the traditional Pixhawk products and architecture.
The team I was speaking with is using the Holybro Pixhawk-4 and Pixhawk-6C. Both these have a port labeled FMU PWM OUT and I/O PWM OUT.
Would I be correct in guessing that the FMU PWM OUT is the same as the MAIN OUT on the Cube, and that I/O PWM OUT is the same as AUX OUT on the Cube?
I recall reading that on the Cube the MAIN OUT ports operate at a higher/different frequency than the AUX OUT port - and as such make them unsuitable for connections to servos. Does this sound about right?
Also - I recall reading that the PWM frequencies can be set by parameters - but I can’t remember if that’s for both MAIN and AUX ports.
Lastly - the Cube’s use of Aux-5 and Aux-6 as relays, typically used for camera shutters - is there something equivalent to this on the Pixhawk Aux ports?
I apologize for asking such rudimentary questions - and appreciate your kind response.
That’s very helpful regarding the GPIO - I should have read the 4.2 release notes more carefully.
I’ve just implemented my first 4-in-1 ESC running BLHeli32 - and using Dshot - with an Orange Cube.
The issue with the Orange Cube’s inability to perform “passthrough” on Aux-1 - is a nuisance - but manageable. When I need to use passthrough for BLHeliSuite32 I simply move motor-1 from Aux-1 to Aux-5 and remap the servo parameters. BLHeliSuite32 then finds all ESC’s just fine.
I asked if I could simply use Aux-2 through Aux-5 to avoid the issue, but I’m told that Dshot requires use of certain ports and that using Aux-2 through Aux-5 is not allowed. I think it’s a firmware issue. As long as I know the rules, I’m happy to follow them…
Back to Pixhawk architecture - it appears that they support 8 Aux ports instead of the Cube’s 6 Aux ports. Really interesting. It seems that only four Aux ports on the Pixhawk support Dshot. And there’s no mention of an issue with passthrough. With only four ports supporting Dshot, it appears that hexa and octa copters aren’t supported.
Flight controllers usually have groups of pins tied to specific timers so usually on a pixhawk 1and i belive the pixhawk cubes aux1-4 share a timer and 5+6 share a timer. So you could have dshot on aux 2345 but not without also limiting aux 1 and 6 to dshot output since they are in the same timer group.