Closed 72chen closed 1 year ago
Agent comment from yating.liao in Zendesk ticket #87381:
Could you provide us with a video for confirmation? It seems that we haven't encountered the same issue. Here is the upload address.:https://pan-sec.djicorp.com/s/BAAgAZfxqawjLkm
In addition, may I know what version of Pilot 2 you are using?
°°°
I have upload the video. The Pilot 2 app is up to date.
Agent comment from yating.liao in Zendesk ticket #87381:
You can try entering Settings --> App and force stop MSDK V5. At this point, Pilot 2 should be able to function normally. From the video, it seems that the MSDK App has not been completely cleared.
°°°
But MSDK 5.4.0 Demo works fine . I don't think forcing a stop is what users want. Can you do a more in-depth examination of MSDK 5.5.0 ?
Agent comment from yating.liao in Zendesk ticket #87381:
We are considering the possibility of implementing MSDK and Pilot 2 coexistence, so this issue may be completely resolved later.
°°°
@dji-dev, any news on the MSDK and Pilot 2 coexistence? Would this also apply for the DJI Fly app? This feature would greatly help on creating background integrations without needing to create your own flight app.
We anticipate that the coexistence of Pilot 2 and MSDK on the remote controller will be implemented in version 5.6.
@dji-lyt What about the DJI Fly app? Will it also coexist?
The coexistence of pilot and MSDK has been implemented in version 5.6.
Hi @tukez ,The DJI FLY was not specifically adapted in this version. I'm curious to know if you're still experiencing any interference issues after updating to version 5.6.
@dji-lyt Yes there is still interference with DJI Fly in 5.6.
I think this should be considered as a new requirement. Could you please submit a new request for this? I will follow up on the conflict issues caused by DJI Fly.
After running the up-to-date SDK demo app on M3T and shutdown it when Aircraft connected for a while. The DJI Pilot2 could't work fine then , same as my app.