Issue with Incorrect RTK NTRIP State After Remote Controller Connection Loss and Reconnection (MSDK v5.7.0)
已完成Dear DJI Support Team,
I hope this message finds you well. I'm reaching out regarding a concerning issue we've encountered related to the RTK NTRIP functionality on our systems utilizing MSDK v5.7.0. We have observed an incorrect state change in the NTRIP service after a specific sequence of events involving a loss and reestablishment of the connection between the remote controller and the aircraft.
Here's a detailed scenario outlining the problem:
- Connection to NTRIP server successfully established.
- Positioning enabled and the NTRIP service state is confirmed as READY.
- Link with both remote controller and aircraft is lost.
- Upon successfully reestablishing the link between the aircraft and remote controller, the NTRIP service state inexplicably changes to DISABLED.
We have attempted to listen to the actual state using the specific key "RtkBaseStationKey.KeyRTKCustomNetworkServiceState," but unfortunately, the listener for this key does not seem to be functional, rendering it ineffective in determining the accurate state of the NTRIP service.
This inconsistency in the NTRIP service state following a loss and reconnection presents a significant operational challenge for us, affecting the reliability and functionality of our systems that rely on RTK positioning.
We kindly request your urgent assistance in addressing this issue. It's critical for our operations to ensure the correct and consistent behavior of the RTK NTRIP service even after a connection loss and subsequent reconnection between the remote controller and the aircraft.
Any insights, guidance, or updates to resolve this issue would be greatly appreciated. If further details or logs are required to assist in troubleshooting, please let us know, and we'll provide them promptly.
Thank you very much for your prompt attention to this matter. We look forward to your assistance in resolving this issue as soon as possible.
-
I would like to kindly request your assistance in verifying whether version 5.6 is affected by the aforementioned issue. It has come to our attention that there is a known bug in RTK that may potentially lead to this problem. We anticipate that this issue will be resolved in the upcoming version.
请先登录再写评论。
评论
5 条评论