Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mini3 Pro keeps disconnecting when running sample App. #427

Open
petered opened this issue Sep 22, 2024 · 9 comments
Open

Mini3 Pro keeps disconnecting when running sample App. #427

petered opened this issue Sep 22, 2024 · 9 comments

Comments

@petered
Copy link

petered commented Sep 22, 2024

I'm running the sample app on the RC-Pro with the Mini3 Pro.

The drone keeps disconnecting and reconnecting approximately every 5 seconds (see screenshots). I can open the "Default Layout" - but the video will freeze every few seconds. So the Sample app is unusable.

Interesting observation: The Sample app DOES stay connected if you run it AFTER running DJI-Fly.

  • If I open DJI fly and connect to the drone - DJI-Fly connects just fine.
  • If I then close DJI fly and restart the sample app - the sample app now stays connected.
  • If I then close the sample app and start it AGAIN - now it has the disconnection problem
  • If I continue restarting the sample app, it will always have the disconnection problem, until I open DJI-Fly again.
    I've now tried this about 10 times and it is reliable - the sample app only connects properly the first time you run it after running DJI Fly.

20240922_141522
20240922_141552

@dji-dev
Copy link
Contributor

dji-dev commented Sep 23, 2024

Agent comment from SHENRONG.LE in Zendesk ticket #117875:

Dear developers,
Hello, thank you for contacting DJI Innovation.

The Mini 3 Pro has frequent disconnection problems when running the sample application on RC Pro, the possible causes and solutions are as follows:
1, application port conflict: The DJI Pilot application on the RC Pro remote may occupy the port, causing the sample application to not connect properly.
2, remote control and application compatibility issues: There may be compatibility issues between the RC Pro remote control and the sample application, resulting in an unstable connection.
3,It is necessary to forcibly stop the DJI Pilot app in the setting interface to use the MSDK app, otherwise the port of MSDK will be preempted by the DJI Pilot app, resulting in the MSDK V5 app failing to recognize the remote control. Restart the sample application after forcibly stopping the DJI Pilot app. This problem is caused by the design of the remote control firmware.

I hope our solution can help you, thank you for your email, wish you a happy life!
Best Regards,
Dji innovation SDK technical support

°°°

@petered
Copy link
Author

petered commented Sep 23, 2024

Thank you for your reply.

Re: 1/3: To be clear - The bug happens when running the MSDK Sample app ALONE - without DJI-Fly running in the background. So there shouldn't be a conflict between apps - because there is only one application running at a time.

Re: 2: Maybe - but the connection works fine just after running DJI fly - so in principle the RC-Pro and Mini3 Pro can work together running the sample app. There is just a bug somewhere which keeps interrupting the connection (unless you run the app right after running DJI-Fly).

Here is a video where I reproduce the issue: https://photos.app.goo.gl/4HJfSm1jZqhPJDzz5

@dji-dev
Copy link
Contributor

dji-dev commented Sep 24, 2024

Agent comment from SHENRONG.LE in Zendesk ticket #117875:

Dear developers,
Hello, thank you for contacting DJI Innovation.

I picked up a known inclusion issue, which is currently documented, that DJI FLY and MSDK are in conflict

I hope our solution can help you, thank you for your email, wish you a happy life!
Best Regards,
Dji innovation SDK technical support

°°°

@petered
Copy link
Author

petered commented Sep 24, 2024

Thank you for your reply - but it looks like there has been some miscommunication of the issue.

The problem is not about conflict between the Sample App and DJI Fly.

If you look at the video, you'll see that:

  • The sample app (alone) does not work [using RC-Pro and Mini3-Pro]. The drone keeps disconnecting.
  • If you run DJI fly, the sample app will work once after that.
  • ... And if you open the sample app again, it stops working.

Running DJI-Fly before the Sample App actually makes it work.

--- 来自ChatGPT的翻译 - 请原谅任何错误。 ---

问题不在于Sample App和DJI Fly之间的冲突。

如果你看视频,你会发现:

  • 单独使用Sample App时(使用RC-Pro和Mini3-Pro),无人机会不断断开连接。
  • 如果运行DJI Fly,Sample App在之后会运行一次。
  • ... 但是如果再次打开Sample App,它又停止工作了。

在运行Sample App之前运行DJI Fly,实际上会让它工作。

@dji-dev
Copy link
Contributor

dji-dev commented Sep 25, 2024

Agent comment from SHENRONG.LE in Zendesk ticket #117875:

Dear developers,
Hello, thank you for contacting DJI Innovation.

About the conflict between msdk and DJI Fly, here is the feedback first

I hope our solution can help you, thank you for your email, wish you a happy life!
Best Regards,
Dji innovation SDK technical support

°°°

@petered
Copy link
Author

petered commented Sep 27, 2024

Added notes on this - I'll update this comment as I debug. I'm trying to understand what controls this "hidden state" that makes the Sample app work or not work.

Hypothesis: DJI Fly, on exit, puts RC-Controller in working state, and Sample App leaves it in broken state.

Experiments (I've disabled auto-startup of DJI fly on the RC-Pro for these)

  1. Restart both drone and controller, run sample app: NO PROBLEM [surprising - we didn't previously run DJI fly]
  2. -> Stop sample app and run it again: NO PROBLEM [surprising - Sample app didn't put it in problem-state]
  3. -> Stop sample app and run it again: still NO PROBLEM [interesting - it stays in working state]
  4. -> Run DJI fly, close DJI Fly, run Sample app again: NO PROBLEM
  5. -> Run Sample app again, now there's the PROBLEM
  6. -> Run Sample app again, PROBLEM
  7. -> Run Sample app again, PROBLEM
  8. -> Restart Drone, run Sample app again, PROBLEM
  9. -> Run Sample app again, PROBLEM
  10. -> Run DJI fly, close DJI Fly, run Sample app again: NO PROBLEM
  11. -> Run Sample app again, PROBLEM
  12. -> Restart controller, run sample app again PROBLEM
  13. -> Restart both drone and controller, run sample app: PROBLEM [surprising - state seemed the same as in (1) but different result - maybe state persists across restarts]
  14. -> Run DJI fly, close DJI Fly, run Sample app again: NO PROBLEM
  15. -> Run Sample app again, PROBLEM
  16. -> Run DJI Fly, restart controller, run Sample app again PROBLEM [lesson - "fixed" state left by DJI fly did not persist across restart]
  17. -> Run DJI Fly, restart drone and controller, run sample app again PROBLEM

Hypothesis was proven wrong on experiment 1, but it holds true from experiments 4 on...

What we've discovered so far..

  • Sample app ALWAYS works after DJI-Fly (as long as RC-Pro has not been restarted)
  • The "ALWAYS works after DJI-Fly" does not hold across restart of RC-Pro
  • Sample app MAY work after restart WITHOUT running DJI-Fly first (it's either random or there's some rule we don' understand)... The one time it did this, it kept working when we kept re-running sample app.

So - I'm currently baffled. Will update this as more evidence trickles in...

@antonymarion
Copy link

Hi @petered, we have a RC Pro and a mini 3 Pro using Last Dji Sample release.

As far as I remember, on Last release the was no stability issue. I will ask for people in team to check it twice for you.

Regards,

@petered
Copy link
Author

petered commented Sep 28, 2024

Ah thanks Antony, that's good info - so going back one release may fix the problem. Ok - will post any discoveries to this thread.

@antonymarion
Copy link

I am not sure which release you are using, but on last release (5.10), I noticed only that: #411

So basically, it seems to me that crash/instability issues were fixed when drone was flying and not connected to a pc with USB.

But when testing with USB it was as chaotic as before.

Since the mini 3 PRO is now with a member of our team, I will let him test it again to confirm this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants