Arming without an RC transmitter

General
1

Hi, I’m using ArduCopter 4.6.3.
I have a Python GUI for basic drone movements (pymavlink).

Until now, while using an RC transmitter, I was able to use the drone without any issues
The issue is that now I don’t want to use an RC transmitter (I turned it off), but the controller refuses to arm.

I followed the steps from https://ardupilot.org/copter/docs/common-gcs-only-operation.html, but no success.

  1. I disabled RC in parameters.

  2. I disabled pre-arm checks and some other things.

  3. I made sure not to take too many seconds between arming and takeoff.

  4. I get the same behavior whether I try to arm with my GUI, Mission Planner, or Mavproxy.

  5. I don’t get any warnings in Mission Planner or Mavproxy (i think is nor a prearm check)

  6. I get arming confirmation, and then it immediately disarms. (The beeps sound, but the propellers don’t spin, it immediately disarms)

    image

  7. I can only arm if, when I turn on the drone, the RC transmitter is also turned on, and then I turn it off

thanks

2

It might help others (more knowledgeable than myself) if you provide a full parameter list.

While I doubt it’s the issue, what is ARMING_CHECK set to?

Good luck.

3

Re-enable your arming checks.

4

i try 3 options. with arming_check all disable (=0) , enable all (=1) and enable all checkbox (=1048063). whit no diferences

with arming_check=0 i have a new log

image

this are my parameters

params_no_rc.param (19.5 KB)

6

Okay, it’s working now!

I had changed DISARM_DELAY=1 with a specific intention. I’m going to land on a moving vehicle, and I wanted the drone’s blades to not spin for a long time once it detects touchdown.

From what I see, it also affects the disarmed → armed transition. Indeed, I reduced the takeoff command time, but never below 1 second. Now I have the takeoff set to 5 seconds after arming, and DISARM_DELAY=10 (default). And it works correctly.

In future tests, I’ll reduce both times as much as possible.

Thanks.

1 Like