Inconsistent simulation with MSDK SimulatorManager.enableSimulator versus DJI Assistant 2 (Enterprise Series)

Completed

Follow

Adam Ward

• July 19, 2024 23:32

I'm trying to run some tests using the MSDK v5.  In order to run my tests I want to do so via simulator. I found that using DJI Assistant 2 on OSX will work for these cases, however i'd prefer if I can just programmatically turn on simulation to remove the manual effort and speed up my development.

My test is fairly simple right now:

FlightControllerKey.KeyHomeLocation.create().set(...)
WaypointMissionManager.getInstance().pushKMZFileToAircraft(...)
WaypointMissionManager.getInstance().startMission(...)

As I mentioned these work fine with the Assistant app, however if I try to run

val settings = InitializationSettings.createInstance(LocationCoordinate2D(0.00000000,0.00000000), 20)
SimulatorManager.getInstance().enableSimulator(settings, callback)

instead of doing all the setup to run assistant on my machine the simulator API says that enable was successful. However trying to set home location to the same Lat/Long returns 

ErrorImp{errorType='CORE', errorCode='SET_HOME_LOCATION_DIS_TOO_FAR', innerCode='', description='null', hint='error code = -516'}

Is there some other way to acchieve this? as I'd eventually like to be able to invoke some other APIs to perform return home and run different features in my test suite.

0

• 

  DJI Developer Support

  • July 22, 2024 08:44

  The message SET_HOME_LOCATION_DIS_TOO_FAR means that the new return point you set is too far from the current position of the drone. Did you also set the default position of the drone to LocationCoordinate2D(0.00000000,0.00000000) during actual testing?

  0

  Comment actions Permalink

Please sign in to leave a comment.