Don't think I'm complaining....

In general, the whole area of UAV development is still pretty disorganized, particularly, I come from another forum, and have been developing a high payload scratch built quad using some famous cloned boards.

And they work well, and specifically are low cost. But it costs an arm and a leg to find good support and proper documentation.

Here things are different, I can see that. A fantastic business model, extensive professional grade technical input, a good range of product choices, and healthy and solid turnkey product mix.

But for someone like me say, coming from outside, even though highly technically experienced and knowledgable of the field, it's quite difficult to get a grasp of what a particular product really is.

The pixHawk struck me as a very interesting platform. I want to get into it. I develop scratch built almost always... a quirk. But after 2 or 3 days on the internet I'm still not really sure what the pixhawk actually is.

The getting started page brought me a long way. I have loaded the imu_autopilot to my linux from github...

but what IS the pixhawk. does it include the computer vision system, do I need more support for that, is the imu_autopilot, just the base firmware,? do you need to load an app on top?

There are a lot of questions, and although I know that a LOT of work has gone into it, I still feel the same documentary disorganization as the rest of the industry.

I'm not trying to be a party pooper. I mention this becasue maybe, from inside, these shortfalls are not seen. Maybe many good developers are being lost because it's just too jumbled to piece together cleanly.

It's not a technology problem. That is very clear. And solid. and refreshing. and it's about time.

It's a problem of product documentation. Especially when the development is so diversified.

So please don't be offended. I wanted to share the view of a newcomer trying to come in.

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • I think one of the problems is that there is no solid link between hardware and software.  The Pixhawk is a piece of hardware.  You can put any software on it that you want.  Make it what you want.  Start from scratch if you want. ;)

    There are I believe two developed softwares that you can use.  The software developed by ETH who developed the hardware (I think this is what imu_autopilot is?).  Or you can use Arducopter or APM3.1, which is developed by a group of developers with close ties to 3DR which is the manufacturer of the hardware.

    I don't think the Pixhawk has anything to do with vision systems.

This reply was deleted.

Activity

DIY Robocars via Twitter
May 15
DIY Robocars via Twitter
May 14
DIY Robocars via Twitter
May 13
DIY Robocars via Twitter
RT @f1tenth: Say hi to our newest #F1TENTH creation for @ieee_ras_icra next week in Philly. It’s going to be huge! 😎 🔥 @AutowareFdn @PennEn…
May 13
DIY Robocars via Twitter
May 11
DIY Robocars via Twitter
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Noticed my car zigzagged in last run. It turned out to be the grass stuck in the wheel and made the odometry less accura…
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Test my car. RTK GPS worked great. Thanks @emlid for their support. https://t.co/EkQ6qmjmWR
May 8
DIY Drones via Twitter
RT @chr1sa: @kane That's @diydrones circa 2009. Still have a box of those Canon cameras that we used to strap into planes, just like this.…
May 3
DIY Robocars via Twitter
RT @chr1sa: Our next @diyrobocars race is going to be outside at a real RC racetrack in Fremont on May 28. Fully autonomous racing, head-to…
Apr 30
DIY Robocars via Twitter
RT @f1tenth: Our Spring 2022 F1TENTH course @PennEngineers is coming to an end with a head-to-head race as a big finale. So proud of our st…
Apr 26
DIY Robocars via Twitter
RT @DanielChiaJH: I wrote a thing! Throughout the development of my @diyrobocars car I've been using @foxglovedev Studio to visualize and d…
Apr 23
DIY Robocars via Twitter
RT @SmallpixelCar: My new car for high speed. Low body, everything ( @NVIDIAEmbedded Jetson Xavier NX, @emlid RTK GPS, IMC) under the deck…
Apr 23
DIY Robocars via Twitter
Apr 21
DIY Robocars via Twitter
RT @f1tenth: F1TENTH Race training setup @PennEngineers for our upcoming ICRA2022 @ieee_ras_icra competition. @OpenRoboticsOrg @IndyAChalle…
Apr 21
DIY Robocars via Twitter
RT @fatcatFABLAB: Proud to be hosting a restarted DIY Robocars NYC Meetup April 26. Come by if you want to talk about and race self-driving…
Apr 17
More…