Thanks for your response. Can you clarify the following:
1.) What do you mean? Should I actually use the /cmd/takeoff command with some custom CommandTOL args? Or should I simply use /rc/override 100% of the time to handle the entire takeoff, flying and landing?
2.) Similarly, for landing should I use land mode and the /cmd/land command or should I instead use /rc/override command to land the drone (e.g., slowly decrease the throttle via /rc/override until it gets to 0)? Is a specific approach preferred? If so, what are the pros and cons?
3.) If using the land mode and land command, should the throttle, pitch, etc. arguments all be set to 0 and then execute the land command one single time? Will that trigger the drone to automatically slowly descend until it touches ground and then automatically stop? Or is it more complicated than that?
4.) Is this the mavros approach you'd recommend for a simple takeoff, hover in place at X feet in air, and then land (I don't have a GPS module)?
- set mode to stabilize
- arm drone
- use takeoff command
- use rc override as needed to position the drone in air
- set land mode and use land command to land drone when desired
- disarm drone