MSDV Regsiter fail

Completed
Follow
Godfrey from Hammer

Hi, 

i'm trying to integrate the msdk v5.1.1 to with mavic3 Smart Controller 
But after i call 

SDKManager.getInstance().registerApp()

Its always return For first time registration, app should be connected to Internet. But my application and the smart controller should have the well internet connection. 

FYI - I had try the 5.1.1 sample app on it. The drone keep connect & disconnect and the camera streaming view is very laggy.

Regards, 
Godfrey

 

0

Comments

7 comments

Date Votes
  • Godfrey from Hammer

    FYR

    My aircraft firmware veresion  05.01.0203
    Controller version  02.00.0210 

    0
    Comment actions Permalink
  • DJI Developer Support
    The MSDK v5.1.1 only supports Mavic 3 Enterprise series but not Mavic 3. The keep connect and disconnect because you havn't disable the DJI official app, please read the below article link. Link：https://sdk-forum.dji.net/hc/en-us/articles/5318937433497-Why-the-connection-of-RC-Pro-or-RC-Plus-is-unstable-
    0
    Comment actions Permalink
  • Godfrey from Hammer

    Thanks very much for your information. 

    Beside that i still got one more question about the start simulator 

    When i try to start the simulator with the following method 

    SimulatorManager.getInstance().enableSimulator

    sometimes it will return error and only comes with an error code only. May i know where can i find the error code meaning table ? 

     

    0
    Comment actions Permalink
  • DJI Developer Support
    You should get the description of the error and print it out. Normally it is your flight mode switch isn't P or N. You havn't take off.
    0
    Comment actions Permalink
  • Godfrey from Hammer

    i didn't got any error message but only the code. Even when i try to start the waypoint mission, its only return error code with "DEFINE11" and "null" in description and "null" in hints

    0
    Comment actions Permalink
  • DJI Developer Support
    I have gotten DEFINE11 sometimes as well. This is because the MSDK hasn't correctly translate the error from the firmware to a human readable message. We are dealing with the error now and it will be fixed in the 5.2.0.
    0
    Comment actions Permalink
  • Godfrey from Hammer

    Thanks a lot! look forward to the 5.2.0

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post