Issue with DiagnosticsKey.SYSTEM_STATUS after changing RTK mode on MSDK 4.17
CompletedDear DJI Support Team,
I hope this message finds you well. I am writing to report an issue we have encountered with the DiagnosticsKey.SYSTEM_STATUS using MSDK version 4.17. Below are the details and steps to reproduce the bug:
Scenario 1:
- Wait for the status to become "Ready to GO (GPS)";
- Open the DJI Pilot 2 application;
- Enable RTK mode;
- Close the DJI Pilot 2 application.
In this scenario, we received a status of "Ready to GO (GPS)" despite the DJI Pilot 2 application indicating a status of "Unable to takeoff".
Scenario 2:
- Open the DJI Pilot 2 application;
- Connect to the D-RTK2 and ensure it has an RTK Fixed state (connected, green color);
- Close the DJI Pilot 2 application;
- Move the D-RTK2 station under a roof so it loses the RTK Fixed status.
In this scenario, we also received a status of "Ready to GO (GPS)" even though the DJI Pilot 2 application showed "Unable to takeoff". Additionally, the drone could not be armed, as evidenced by the red LED indicators on the drone's arms.
Affected Equipment:
- Drone: DJI M300 (issue consistently reproducible on this model)
- MSDK Version: 4.17
We would appreciate your assistance in investigating this issue. Please let us know if any additional information is required or if there are any recommended steps to resolve this.
Thank you for your prompt attention to this matter.
-
You have previously submitted a similar issue. I will combine the situation you described with your previous submission for processing. Could you please provide some video materials to help us understand the specific performance? Here is the upload link: https://pan-sec.djicorp.com/s/6e5JEocSHJbm3LZ The password is dji123. -
You can use the code below to obtain the system status of the device. It has been verified to be essentially consistent with Pilot 2. private CompositeSubscription subscription = new CompositeSubscription(); LogicManager.getInstance().init(); FPVTipLogic.getInstance().init(); LogicManager.getInstance().startFPVTipLogic(); subscription.add(LogicEventBus.getInstance().register(FPVTipLogic.FPVTipEvent.class) .observeOn(AndroidSchedulers.mainThread()) .subscribe(fpvTipEvent -> flightStatusTV.setText("Status:"+fpvTipEvent.getMessage().getTitle() + "/" + fpvTipEvent.getMessage().getDescription())));
Please sign in to leave a comment.
Comments
4 comments