COMMAND_DENIED when running keyboard-mavsdk-test.py

[BINFLCY]

Hello, thank you for providing this great project! I encountered an issue when trying to run the keyboard-mavsdk-test.py script. When I press the r key to arm the drone, I receive a COMMAND_DENIED error. The full error log is as follows:
zj@zj-Z390-UD:~/ws_offboard_control$ source ~/px4-venv/bin/activate cd ~/PX4-ROS2-Gazebo-YOLOv8 python keyboard-mavsdk-test.py pygame 2.6.1 (SDL 2.28.4, Python 3.10.12) Hello from the pygame community. https://www.pygame.org/contribute.html Waiting for drone to connect... -- Connected to drone! Task exception was never retrieved future: <Task finished name='Task-3' coro=<getKeyboardInput() done, defined at /home/zj/PX4-ROS2-Gazebo-YOLOv8/keyboard-mavsdk-test.py:12> exception=ActionError(<mavsdk.action.ActionResult object at 0x74557f9c55a0>, 'arm()')> Traceback (most recent call last):

[BINFLCY]

[monemati]

@BINFLCY Hi, I am not sure if the problem is from MAVSDK part or the integration with QGC is causing the problem. Please try to do the process without QGC to check if script is working or not.

[BINFLCY]

Thank you very much for your response and guidance. I truly appreciate your help—it means a lot to a beginner like me.

Following your suggestion, I tried controlling the system with the keyboard without using QGC. I found that the issue still occurs when pressing the "R" key, as it raises the error: raise ActionError(result, "arm()"). However, the "L" key works as expected, displaying "Flight Mode: LAND."

When using QGC, the "L" key also works properly, with the log showing: "landing at current position." This leads me to believe that the communication is functioning normally.

I also attempted the solution mentioned in this issue, which suggests manually arming the vehicle via QGC. However, the arm command doesn’t seem to have any effect in my case.

[monemati]

@BINFLCY If you already tried without QGC and the arming issue is still there, my next guess is you are using the new version of PX4 firmware which is v1.16 (I have v1.15 on my machine). You can try to use the v1.15 firmware version and see if everything is okay or not. You can also check this issue in PX4 repo.

[BINFLCY]

Thank you so much for your patient guidance! I’m thrilled to share that I’ve successfully achieved flight—what an incredible moment! This is truly an amazing project, and I’m deeply impressed by the thought and effort you’ve put into it.

As part of the process, I made some modifications, such as downloading PX4 version 1.15.2 and editing the default.sdf file. Moving forward, I plan to incorporate a large model into the project to enable it to describe the scenes captured by the drone. I’m really excited about the possibilities ahead.

Once again, thank you for your remarkable contributions and dedication to open source. It’s truly inspiring!

[BINFLCY]

Uploading default.txt…