Dear community,
The arming process goes through a lot of check until the arming is successful which is good but what if the API allow the arming to be hold since arming is good to keep until you decide when you launch. Not sure if this question.
I have looked into drone.action.hold() but this is the closed I can find to hold the state of the drone.
Shall I raise it as a feature request i the github or ?
The drone get armed and after 10 seconds it stops spinning and all is lost ( gained stated)
Also is the solution to launch to a certain location or takeoff to certain hight and invoke action “hold”.
The sample from python “goto.py” has an inifinite loop to keep the thread live and disallow the main thread to exist
I have tried it and it seems there is the below message
Staying connected, press Ctrl-C to exit
Status: INFO: Disarmed by auto preflight disarming
Staying connected, press Ctrl-C to exit
Staying connected, press Ctrl-C to exit
I was looking at the params protocol to be sent
The below code after drone get connected is not being implemented by the server
drone.param_server.provide_param_float(“COM_DISARM_PRFLT”, 10000)
The default is still 10 second as per specification above and the min is 0.1 second
also as per documentaiton, to disable the disarm by default we can add negative number
drone.param_server.provide_param_float(“COM_DISARM_PRFLT”, -1.0)
The above also does not have any effect and still the message appears as below
Status: INFO: Disarmed by auto preflight disarming
Did I miss any mavlink protocol params ? Shall I raise it as an issue with detailed steps ?
Please advice ?