Air 3 S / RC-N3 – “Waypoint Flight Suspended” after KMZ import (DroneLink export workflow)

Unknown Unknown

I’ve been testing the Air 3 S with the RC-N3 controller using DroneLink’s GroundLink → KMZ → DJI Fly workflow and have repeatedly hit a hard stop at mission execution.

Setup

  • Aircraft: DJI Air 3 S (firmware 01.00.0400)

  • Controller: RC-N3 (firmware 01.00.0200)

  • Mobile device: Android phone running DJI Fly v1.19.0

  • Workflow: Create mission in DroneLink → Convert to DJI Waypoints → Export KMZ → Import into DJI Fly

Observed behaviour

  • The KMZ imports successfully, displays all waypoints correctly, and passes initial validation.

  • When “Start Mission” is pressed, DJI Fly shows “Error performing flight – Waypoint Flight Suspended.”

  • Manual flight and camera control work normally, so this appears to be a firmware-level block rather than a GPS or RC problem.

File inspection

  • The exported .wpml includes enabled tags for gimbalRollRotateEnable, gimbalYawRotateEnable, and the turn mode toPointAndPassWithContinuityCurvature.

  • The Air 3 S firmware may not permit those parameters in externally generated missions; removing them might allow partial execution, though I haven’t confirmed yet.

Additional context

  • I previously held a DroneLink Premium subscription for a Mavic Air 2 and was very happy with the results.

  • I later upgraded to the Expert tier so I could continue running autonomous missions with the Air 3 S, but I’ve been unable to do so using the same planning workflow.

  • I have, however, been able to run the same mission geometry successfully using both Waypoint Map (subscription service) and DJI Mapper (free service).

  • That suggests the aircraft and controller are functioning normally and that the failure is specific to how DroneLink’s GroundLink export is interpreted by DJI Fly.

Question
Has anyone successfully executed a GroundLink-generated KMZ mission on an Air 3 S / RC-N3 using DJI Fly (not the RC 2 / RC Pro controllers)?
If so, could you share:

  • Firmware / app versions

  • Any parameters you disabled in the .wpml

  • Whether DJI Fly displayed the same “Waypoint Flight Suspended” message before launch

I’m trying to determine whether this is a current SDK v5 limitation or a correctable parameter conflict within the KMZ.

Thanks in advance for any advice.

0

Comments

8 comments

Date Votes
  • Comment author
    Jim McAndrew Dronelink Staff

    Please share the original dronelink mission before you converted it.

    1
  • Comment author
    Unknown Unknown
    • Edited

    Thanks for the support Jim. 

    Here’s the recreated mission before conversion to KMZ (link below).  

    For privacy reasons I’ve recreated the mission with the take-off point moved slightly from the original location, but no flight parameters have been altered.  This mission geometry is identical in structure to the one that produced the “Waypoint Flight Suspended” message after KMZ export and import into DJI Fly.

    https://app.dronelink.com/drone_work_d3/ballaruk_bushland/plan/UaQB20fCCbxjEujMBbtP/Sm4gMYZUm6j9P9lcol7Z 

    Mission summary:
    Planned at 87 m AGL over Ballaruk Bushland, area ≈ 2.9 ha.
    Overlap/Sidelap: 75 % / 70 %.
    Camera preset: Air 2 (24 mm eq.) | Gimbal pitch –90°.
    Capture mode: Photo → Single | Interval 2 s | Priority = Distance.
    Target speed: ≈ 32 km/h (9 m/s).
    Action on finish: Return Home.
    Pattern: Normal grid | Reference = Take-off location.


     

    1
  • Comment author
    Jim McAndrew Dronelink Staff

    Looks like it’s the same issue as described here: https://support.dronelink.com/hc/en-us/community/posts/44455006607507

    1
  • Comment author
    Mike (Arizona Wyldwest) Dronelink Expert Dronelink Expert

    I had a feeling this issue would come again and it looks like more and more are now. Maybe a note in the support section to explain that 0° heading won’t work on mapping component. Possibly a link to the thread which explains how to get it to work. Just a thought.

    1
  • Comment author
    Jim McAndrew Dronelink Staff

    I put out a fix for this, just refresh the web app to see if it works. After looking at it again, it appears that sometimes Dronelink would generate angles slightly above 180 or below -180 (when mapping direction was set to 0) and DJI Fly did not like this.

    1
  • Comment author
    Unknown Unknown

    Thanks Jim, that fixed it straight away.  The mission now loads and runs correctly on the Air 3 S and I would never have found that on my own.  I really appreciate how quickly you responded and issued the fix: less than a day from problem to solution is pretty impressive! 

    I just wanted to confirm for clarity that photo capture still needs to be started manually before running the mission.
    I saw a note in the “Onboard DJI Waypoint Missions, Convert and Export to KMZ” guide that says interval photos for DJI Fly app missions need to be started manually.  That's still the correct approach right? 

    0
  • Comment author
    Jim McAndrew Dronelink Staff

    The camera function has not changed.

    1
  • Comment author
    Unknown Unknown

    Thanks for closing this out :-D 

    0

Please sign in to leave a comment.