Mobile-SDK-Android-V5 icon indicating copy to clipboard operation
Mobile-SDK-Android-V5 copied to clipboard

Bug on M350 – Virtual Joysticks Unresponsive in P Mode

Open victor-cornis opened this issue 9 months ago • 3 comments

Hello,

I'm encountering a bug only on the M350 (MSDK V5.10) when using virtual joysticks to send flight commands. I have isVirtualStickEnable = true, isVirtualStickAdvancedModeEnabled = true and currentFlightControlAuthorityOwner = Unknown, but when I send commands, the drone refuses to move, even though I'm in P mode.

This bug does not happen consistently, but when it does, the only workaround I've found is to switch to S mode, then back to P mode. Aside from switching modes, nothing else has changed—my autopilot continues sending the same flight commands, yet the virtual joysticks only start working again after the mode switch.

This issue does not occur on the M300 or M3E. I am flying close to obstacles (around 5 to 7 meters), and I wonder if this could be blocking the autopilot. However, it's strange that simply switching from S to P mode restores joystick functionality.

Best regards, Victor

victor-cornis avatar Feb 25 '25 13:02 victor-cornis

Agent comment from YIGUI LIU in Zendesk ticket #130256:

Dear Developer, Hello and thank you for reaching out to DJI Innovations.

Flight Mode Switching: After switching back from S mode to P mode, the function of the virtual joystick returns to normal, which may be related to the reset of the flight mode status. The switch between S mode and P mode may reinitialize certain flight control parameters, thus solving the problem.

Obstacle Sensing: Since you are flying close to obstacles (5 to 7 meters away), it is possible that the drone's obstacle avoidance system or sensors detect the obstacles, thus restricting the movement of the drone. You can check the settings of the obstacle avoidance system.

Flight Control Authority: The "Unknown" displayed for currentFlightControlAuthorityOwner may indicate that the status of the flight control authority is unclear. Ensure that the flight control authority is correctly assigned before sending virtual joystick commands.

Try to reproduce your problem using the MSDK sample app.

We hope that our solution meets your needs satisfactorily. We appreciate your email and wish you a wonderful day! Best Regards, DJI Innovations SDK Technical Support Team

°°°

dji-dev avatar Feb 26 '25 10:02 dji-dev

Dear DJI Innovations SDK Technical Support Team,

Thank you very much for your response.

  • I have checked that obstacleAvoidance is set to the minimum.
  • I have also tried enabling/disabling the obstacle sensors, but this did not resolve the issue.
  • I will now look into the Flight Control Authority and test with the MSDK sample app. I will get back to you if the issue is resolved or if it persists.

Wishing you an excellent day.

Best regards,

Victor

victor-cornis avatar Feb 26 '25 12:02 victor-cornis

Agent comment from YIGUI LIU in Zendesk ticket #130256:

Dear Developer, Glad to receive your reply.

Okay, I hope you can locate the problem and resolve it soon.

We appreciate your email and wish you a wonderful day! Best Regards, DJI Innovations SDK Technical Support Team

°°°

dji-dev avatar Feb 27 '25 07:02 dji-dev