Isn't the entire point of these things that they fly themselves? That's why we call them drones and not R/C helis, right?
Why can't I just click "go" on my GUI, and never purchase a TX? Or can I and the distinction just isn't explained in a place that I've found it?
Here (.au) I'm technically not allowed to fly FPV (where I'm watching a camera view from the air thru goggles or on a screen) without having another person ready to immediately take manual control who's watching/flying "LOS" (line of sight) and complying with the regular model aircraft pilot rules.
Practically nobody actually does this, but almost everybody holds some form of manual controller and is ready to take their goggles off or look away from the screen and fly the drone manually as a regular model aircraft.
If you _want_ to "just click go on the GUI", at least some of the DJI stuff will allow you to do that. I've got a DJI Spark that I can connect/control via wifi from an iPad, and software that lets me define a mission and just click fly without needing a controller. There's still an advantage to having the controller though, it's radio as way better range than an iPad's wifi, the wifi drops out and I lose the video link (while the drone keeps flying its uploaded mission) at a hundred or so meters. If the drone and the iPad both connect instead to the DJI controller, I'll get reliable video at well over 1km. One other reason I almost always use the controller is I'm much happier launching/landing in tight locations if I fly the last few meters manually. I'll sit on the back ledge of the car boot and land 1m away from the car flying manually, but I don't trust the drone/GPS quite enough to do that, and will always find a fairly large (at least 10mx10m or so if I can) area to let it land in if it's flying totally autonomously.
You absolutely _can_ build an ArduPilot drone that takes commands and tries to fly a mission end-to-end without intervention, but without a real-time TX link of some form, you are in hot water when it fails.
They assume you have a transmitter, because a majority of non parrot drone users are flying analog.
We lost that fight a long time ago.
(And I'm not even sure we were "right" to be honest. The term "drone" got used back in WW2 era for radio controlled aircraft used for target practice. There sure as hell were not autonomous... https://en.wikipedia.org/wiki/Radioplane_OQ-2 )
Spot on.
However, it's a nice way to lure you into building a quad: just put some motors on, and you're good to go.
Fly once, crash, and then go actually build a proper quad.
In typical indoor use (can't get more than a few meters high, unlikely to go faster than a few m/s), this'll crash way more than one time before it show any signs of damage to anything except the (replaceable) props. (Sure, you won't be handing it down to your grandkids in your will, but it's not as disposable as "fly once, crash, throw it away"...)
Just some pointers if you want to do this:
- you need some companion computer on your drone.
- GPS alone is not precise enough, you'll get wierd drifts from it all the time, you want something like RTK GPS to be able to keep stuff together.
- If you want your positioning to relie on vision, get a global shutter camera, a rolling shutter will make your life harder than it needs to be.
About vibration dampening, if you look at the maiden flight here https://discuss.ardupilot.org/t/ardubee-a-ready-to-fly-micro...
Don't you think the untuned ArduBee was flying already nicely?
The graph of the postfilter acc and gyro is not so bad, the new Dynamic Notch Filter technics in Ardupilot is working so good. Furthermore, the best in his class IMU is put in the center of the frame, where the single 18650 battery, the most of the mass, is fixed in place.
A small <250g drone is in the $70-$100 price range, although you will also need a $70+ radio transmitter or some heavy hacking to control it. Most of the (hundreds) of supported control boards are not open hardware in the schematics sense, but some are.
The all-in-one PCB integration strategy is cute, but I really don't think it's a great approach from a crash-recovery point of view.