-
Notifications
You must be signed in to change notification settings - Fork 177
NTRIP RTK Cleanup? #553
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
Comments
Agent comment from YIGUI LIU in Zendesk ticket #140704: The Pilot 2 APP doesn't integrate the MSDK, so we can't know their implementation method. Best Regards, °°° |
Hello,
I already have similar retry logic in this code in an attempt to work
around but it will still remain in DISCONNECTED state.
…On Wed, Apr 23, 2025 at 12:19 AM DJI ***@***.***> wrote:
Agent comment from YIGUI LIU in Zendesk ticket #140704
<https://djisdksupport.zendesk.com/agent/tickets/140704>:
Dear Developer,
The Pilot 2 APP doesn't integrate the MSDK, so we can't know their
implementation method.
You can try to add a retry mechanism. For example, close the RTK service
via stopNetworkRTKService and then start it again via
startNetworkRTKService.
Best Regards,
DJI Innovations SDK Technical Support Team
*°°°*
—
Reply to this email directly, view it on GitHub
<#553 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEQSOPQRFMQ7JO3AMZX2G32245GLAVCNFSM6AAAAAB3UWVITCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRTGMYDAMZXGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
*dji-dev* left a comment (dji-sdk/Mobile-SDK-Android-V5#553)
<#553 (comment)>
Agent comment from YIGUI LIU in Zendesk ticket #140704
<https://djisdksupport.zendesk.com/agent/tickets/140704>:
Dear Developer,
The Pilot 2 APP doesn't integrate the MSDK, so we can't know their
implementation method.
You can try to add a retry mechanism. For example, close the RTK service
via stopNetworkRTKService and then start it again via
startNetworkRTKService.
Best Regards,
DJI Innovations SDK Technical Support Team
*°°°*
—
Reply to this email directly, view it on GitHub
<#553 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEQSOPQRFMQ7JO3AMZX2G32245GLAVCNFSM6AAAAAB3UWVITCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRTGMYDAMZXGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I'm writing to inquire about recommended steps for application cleanup. I have a specific use case where the Pilot 2 app behaves different from mine, so I'm hoping for some guidance since the pilot 2 is performing better.
The place where I notice a difference is using NTRIP RTK connections.
In Pilot 2, I can enable RTK, set it to NTRIP provider, save NTRIP settings, and pilot 2 will connect, with FIX positioning.
Where I notice an issue is if I power off and back on the drone once in this state, when I do so Pilot 2 sometimes doesn't reconnect and positioning never becomes fixed.
The simplest way around this is to close Pilot 2 by swiping away, and then reopen. I can then see RTK FIX re-establish after some time.
In my app, I can follow these same steps but with API calls:
RTKCenter.setAircraftRTKModuleEnabled(true, ...)
RTKCenter.setRTKReferenceStationSource(NTRIP_NETWORK_SERVICE, ...)
RTKCenter.customRTKManager.customNetworkRTKSettings = ...
RTKCenter.customRTKManager.startNetworkRTKService(...)
When I monitor
RTKCenter.customRTKManager.addNetworkRTKServiceInfoListener
I reach stateRTKServiceState.TRANSMITTING
and
rtkCenter.addRTKLocationInfoListener
will haveRTKLocation.positioningSolution
ofFIXED_POINT
If I then power off and on the vehicle sometimes I get stuck in
RTKServiceState.DISCONNECTED
just like in Pilot 2.However closing my app does not fix this, subsequent app sessions will still show
RTKServiceState.DISCONNECTED
state.I've tried invoking the following APIs when my app is closed
This however doesn't seem to fix the issue. Can you please advice what calls Pilot 2 could be making that help with the resolution of this issue?
The text was updated successfully, but these errors were encountered: