Maintaining Stable Centipède RTK Connectivity in the Mobile SDK

I am currently using the mobile SDK and trying to connect to the RTK network Centipede. However, I’m encountering an issue where the RTK Healthy status in my application becomes false after initially being true. This behavior occurs after I leave the DJI Pilot 2 app, where the RTK network appears to connect and function properly.

In my application, the connection persists for only 10 minutes, maintained by the Maintain Accuracy Mode, but the RTK Healthy status remains false.

Last week, I ran a test and observed that the RTK network reconnected automatically when I returned to the DJI Pilot 2 app. Here are the detailed steps of what I did:

1. Connect to the RTK Centipède Network via DJI Pilot 2:
   I initially connected the RTK Centipède network using the DJI Pilot 2 app, and everything worked fine.

2. Stop DJI Pilot 2 and Switch to My Application:
   After ensuring the RTK connection was good, I closed the DJI Pilot 2 app and launched my own application.

3. RTK Status in My Application:
   In my application, the RTK remained active for 10 minutes, thanks to the Maintain Accuracy Mode.

4. Return to DJI Pilot 2 Within 10 Minutes:
   Before the 10-minute period ended, I reopened the DJI Pilot 2 app. At this point, the RTK status was still in Maintain Accuracy Mode.

5. Automatic Reconnection:
   Upon returning to the DJI Pilot 2 app, the RTK status switched from Maintain Accuracy Mode to Connected without me performing any additional actions. It appeared to automatically reconnect to the RTK Centipède network.

I’d like to understand how this automatic reconnection is handled within the DJI Pilot 2 app and how I can replicate this behavior in my SDK application to ensure the RTK network connection is established and maintained without frequent disconnections.

Could you provide guidance on initiating and sustaining a stable RTK network connection through the SDK?