Kill Switch for missions?

Hi

Is there are (safe) way to abort script out in the field?

For example, should pushing the RC throttle lever to the left (manual disarming of the drone) abort mission?

I ask because, after executing the precision_landing_single_aruco.py script, the drone failed to takeoff even though the props were spinningat significant revs …

Since trying to pull the drone’s power cables apart (during active prop spin) was not really an option, I basically waited about 10 minutes for the battery to discharge …

Regards
Ben

Oh, & I also pressed: ‘ctrl + z’ in Python’s command line to attempt to abort, but this doesn’t work …

This can be broken into three different questions.

1 Despite arming the drone, why did it not take off?

This could be due to :

a. Insufficient power (most likely). The battery was not sufficiently charged or you used a battery with an inadequate c-rating, which addresses the maximum current that can be delivered to the motors. Ensure the battery is fully charged before flight. An easy way to do this is to attach a lipo battery checker.

Also monitor the state of the battery with Mission Planner.

b. Overweight. The thrust/weight must be adequate to achieve lift off. Weigh the drone all up weight (AUW) before flying. The battery might have been too big for these hobby drones.

c. The props were installed upside down, so no upward lift could be generated.

d. The ESCs were not properly calibrated.

e. The PIDs were not properly tuned (unlikely).

f. The drone was snagged on something on the ground.

2 How to stop the python script? Instead use Ctrl-C. Dronekit might ignore Ctrl-Z so it won’t cleanly terminate. Alternatively, use the Mission Planner Arm/Disarm button in the Actions Tab of the Flight Data Screen.

3 How to stop the motors? Move the throttle stick down and left. You can also set up the transmitter with a kill switch. There are several options. See these:

https://discuss.ardupilot.org/t/disarm-in-flight-and-emergency-stop-feature/121944

https://www.youtube.com/watch?v=-Db4u8LJE5w

2 Likes

Solved; the issue was:

“c. The props were installed upside down, so no upward lift could be generated.”

I should’ve known that this was the case particularly as a noisy whoozing sound was being generated at high revs …

1 Like

That’s cool that there’s a arm/disarm button in Mission Planner :+1:

This is a tricky one and I have experienced several times lol. This one, and incorrect prop direction, e.g., clockwise vs counter clockwise orientation.

1 Like

Yeah … all them poor insects :mosquito:; they probably thought there was an earthquake or something occurring, given all that downward thrust that was being produced :relieved_face: