Description
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 state RTKServiceState.TRANSMITTING
and rtkCenter.addRTKLocationInfoListener
will have RTKLocation.positioningSolution
of FIXED_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
rtkCenter.customRTKManager.destroy()
rtkCenter.destroy()
// and
SDKManager.getInstance().destroy()
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?