OSDK sample mission not working with bigger increment value

Completed

Comments

9 comments

  • DJI Developer Support
    1、If you are testing in the DJI Assistant2 simulator, please restart the simulator and try again. 2、Please provide a complete PSDK running log, let's confirm the uploaded waypoint information first.
    0
    Comment actions Permalink
  • Mina Enayat

    Thank you for your kind supportive reply,
    1- yes, I am using Assistant2 and I have tried restarting it with no luck.
    2- Here is the OSDK log (I have added some printout lines to track what is changing the AckErrorCode but was not successful (nothing else is changed other than the "increment" value):

    Enter increment (default is 0.000001): 
    0.00001
    AckError issue, Line2188, ack.data became 0  Entry: cmd_set=3, cmd_id=16, len=17, seqNumber=9, Data value: 0

    STATUS/1 @ printInfo, L206: Mission Manager status: 

    STATUS/1 @ printInfo, L207: There are 1 waypt missions and 0 hotpoint missions
    Initializing Waypoint Mission..
    Waypoint created at (LLA): 0.869367     -1.695190     10.000000
    Creating Waypoints..
    Waypoint created at (LLA): 0.869367     -1.695190     10.000000
     WPaddPointAdd issue, Line2137, ack.data became 0  
    STATUS/1 @ getErrorCodeMessage, L754: uploadWaypoints
    STATUS/1 @ getCMDSetMissionMSG, L997: MISSION_SUCCESS
    dji_ack in mission L772Waypoint created at (LLA): 0.869372     -1.695181     11.000000
     WPaddPointAdd issue, Line2137, ack.data became 1  
    STATUS/1 @ getErrorCodeMessage, L754: uploadWaypoints
    STATUS/1 @ getCMDSetMissionMSG, L997: MISSION_SUCCESS
    dji_ack in mission L772Waypoint created at (LLA): 0.869367     -1.695172     12.000000
     WPaddPointAdd issue, Line2137, ack.data became 2  
    STATUS/1 @ getErrorCodeMessage, L754: uploadWaypoints
    STATUS/1 @ getCMDSetMissionMSG, L997: MISSION_SUCCESS
    dji_ack in mission L772Waypoint created at (LLA): 0.869357     -1.695172     13.000000
     WPaddPointAdd issue, Line2137, ack.data became 3  
    STATUS/1 @ getErrorCodeMessage, L754: uploadWaypoints
    STATUS/1 @ getCMDSetMissionMSG, L997: MISSION_SUCCESS
    dji_ack in mission L772Waypoint created at (LLA): 0.869352     -1.695181     14.000000
     WPaddPointAdd issue, Line2137, ack.data became 4  
    STATUS/1 @ getErrorCodeMessage, L754: uploadWaypoints
    STATUS/1 @ getCMDSetMissionMSG, L997: MISSION_SUCCESS
    dji_ack in mission L772Waypoint created at (LLA): 0.869357     -1.695190     15.000000
     WPaddPointAdd issue, Line2137, ack.data became 5  
    STATUS/1 @ getErrorCodeMessage, L754: uploadWaypoints
    STATUS/1 @ getCMDSetMissionMSG, L997: MISSION_SUCCESS
    dji_ack in mission L772Waypoint created at (LLA): 0.869367     -1.695190     10.000000
     WPaddPointAdd issue, Line2137, ack.data became 6  
    STATUS/1 @ getErrorCodeMessage, L754: uploadWaypoints
    STATUS/1 @ getCMDSetMissionMSG, L997: MISSION_SUCCESS
    dji_ack in mission L772Uploading Waypoints..
    initAck after WPupload:Entry: cmd_set=3, cmd_id=16, len=17, seqNumber=9, Data value: 0
    AckError issue, Line2188, ack.data became 199  
     StartAck:Entry: cmd_set=3, cmd_id=18, len=17, seqNumber=17, Data value: 199

    STATUS/1 @ getErrorCodeMessage, L754: runWaypointMission
    STATUS/1 @ getCMDSetMissionMSG, L997: MISSION_SUCCESS
    dji_ack in mission L772AckError issue, Line2188, ack.data became 0  
    STATUS/1 @ removePackage, L471: Remove package 0 successful.AckError issue, Line2188, ack.data became 0  
    STATUS/1 @ reset, L570: Reset Subscription Successful.

    Thank you again for your help.

    0
    Comment actions Permalink
  • Mina Enayat

    Just to clarify, in the successful mission run, after the upload is complete (you can see the line "Uploading Waypoints.." where upload is completed) the "starting Waypoint Mission" message should pop up. Instead in this case the Data value of the startAck becomes a nonzero value in calling 

    ACK::ErrorCode startAck =
    vehicle->missionManager->wpMission->start(responseTimeout);
     
    I cannot find out the reason and where this is happening!
    0
    Comment actions Permalink
  • Mina Enayat

    I found out that the 199 Data value refers to "too far from home location" error. If it is correct, I have two questions: 1- the farthest waypoints from home location in the case of "increment=0.000005" (which also fails to fly) is around 50 meters away, connecting through 3 other waypoints, which should be allowable!
    Am I missing something!?

    0
    Comment actions Permalink
  • DJI Developer Support
    "too far from home location" means waypoint is too far away from home point. Please confirm the simulator coordinate point on DJI Assistant2, usually select the start point coordinates of the waypoint.
    0
    Comment actions Permalink
  • Mina Enayat

    Thank you for your reply.
    The home location (start point of the mission) as you can see above is ((LLA): 0.869367     -1.695190     10.000000) and you can find the rest of the waypoints in the log above. Their pairwise distance doesn't exceed 65 meters and the farthest waypoint from home location is also less than 100 meters away. The total length of the path is about 260 meters. These numbers seem reasonable and within the allowable range (the batteries are full).
    I have also tried an increment of 0.000005 but got the same error. (the distances in this case are almost half)

    0
    Comment actions Permalink
  • DJI Developer Support
    Please provide a screenshot of the settings of the DJI Assistance2 simulator, and export the drone log when the problem is reproduced through the DJI Assistance2 log export interface. And please send it to dev@dji.com by email. We will check the status of the drone.
    0
    Comment actions Permalink
  • Mina Enayat

    Your kind support is greatly appreciated.
    an email has been sent with the requested info.

    0
    Comment actions Permalink
  • Gary

    Is this issue resolved? I am facing the same error on M210 with OSDK 3.9 in simulation.

    What is the resolution?

    0
    Comment actions Permalink

Please sign in to leave a comment.