“There is no such thing as Pixhawk Platform”, now you really confusing me. So this web site https://pixhawk.org/ " The open standards for drone hardware" doesn’t define Pixhawk hardware is based on?
And to me ArduPilot is the software…so your comment has really confused me.
I also beg to disagree with you on your marketing analysis of Pixhawk “or” call it Ardupilot Hardware not having a built in OSD including platforms such as Pixhawk 2.1 a.k.a cube. a.k.a Orange, “or” PX4 etc. God knows who comes with up all these naming conventions.
I prefer Pxhawk over other FC’s for multiple reasons (History, comfort to use etc.). One commercial application we do is to provide cell tower inspections services. I run a company that builds Verizon and AT&T cell towers and installing 4G and now 5G antennas nationwide, besides catering to utility companies for inspections.
In the old days the technician would take 300 pictures of the job completion which you send to some back office engineer who evaluates the quality of work finds out that the guy missed few pics. Now the tech has to climb up the tower and take pics again.
The new model is that we provide live streaming of video either via a drone, or handled device. The live stream need lat and long data superimposed on the video and there is some other proprietary data we want to display down the road. Plus reduces the man power in the field to fly the UAV.
As the DJI platform is getting banned in the US (Typically used e.g. in this industry in the past) the demand for other reliable FCs such as Pixhawk for commercial application is growing.
We incorporated UAvionics ADS-B in Pixhawk 2.1 Orange, so why can’t we incorporate OSD data over lay? (required for many other applications and we are not talking hobbies here) One less device to fail mid air in my opinion and there are many other functionalities we can add in OSD overlay.
Just my two cents.