Litchi Waypoint Mission to DJI Fly Waypoint Mission Converter
Instructions
Instructions
This web application can be used to convert a Litchi mission CSV file into a
DJI Fly (all models) of DJI Pilot 2 (all models) waypoint KMZ file. The
instructions below were created after reading how others have uploaded
missions to DJI Fly for their Mavic 3 / Air 3 / Mini 4 Pro. If you see any
details that are not correct or incomplete, please let me know so that I can
refine these instructions.
Create a mission using Litchi's Mission Hub
A mission can be created like any other Litchi mission then exported as a CSV file.
Note that some parameters (Mission speed, Path mode, Finish action, et.) are not stored in the CSV file. As a result, they must be manually set here or in the DJI Fly app.
In page one of the Litchi Waypoint Mission to DJI Fly Waypoint Mission page:
Set the desired "Signal Lost Action" to either continue the mission or to execute the normal "Signal Lost" action.
Set the mission flight speed in meters per second.
Use the file chooser to upload your Litchi CSV file.
Generate the mission and review the resulting parameters.
Warning: file_get_contents(litchiToDji3Instr2.html): failed to open stream: No such file or directory in /home/wesbarri/litchiutilities.com/public_html/litchiToDji.php on line 43
This web application can be used to convert a Litchi mission CSV file into a
DJI Fly (all models) or DJI Pilot 2 (all models) waypoint KMZ file.
Once created, the KMZ file must be uploaded to the "waypoint" folder on the
device running DJI Fly. If using DJI Pilot 2, the import function can be used
to upload the KMZ file. Detailed instructions are available from the
"Instructions" button above.
Things you should know about this application
DJI Fly was not designed for mission uploads. Therefore, some extra steps
must be performed to upload missions. This process may be too complicated for
the casual user.
Differences between Litchi Missions and DJI Fly Missions:
Mission Path: It is important to understand that the resulting DJI Fly waypoint mission
will not follow the exact path of the Litchi waypoint mission. This is
because Litchi and DJI use different methods to generate a curved mission
flight path. The differences between Litchi and DJI flight paths are
described here.
Waypoint Actions: DJI's implementation of waypoint actions in DJI Fly is very limited. Like
Litchi, the WPML language does support multiple actions at one waypoint and
allows them to be specified sequentially. However, when one waypoint has
multiple actions (like are used in my Panorama Mission), DJI Fly continues to
execute those actions sequentially as the drone flies away from that waypoint.
Headings: Litchi has two ways to define the heading and gimbal pitch angles at a waypoint:
Heading and Gimbal Pitch (Focus POI or Interpolate) settings
Rotate aircraft and Tilt Camera waypoint actions
DJI Fly has one way to define heading or gimbal pitch angles using "action groups" and "actions". Converting between the Litchi method and the DJI Fly method is not always well-defined and may produce unexpected results.
Large Missions: It has been reported that the DJI RC or RC2 can become
sluggish when working with large missions. This is due to the DJI Fly map
display. If you experience sluggishness, minimize the map display. Once the
map display is minimized, DJI Fly will become responsive again.
NOTE: If you encounter any abnormalities flying a
converted Litchi mission, please let me know.
Allow Straight Lines
Litchi allows the path mode of waypoint missions to be set to either "Curved
Turns" or "Straight Lines". The WPML language used in DJI Fly also allows
either straight lines or curved turns to be specified. However, for unknown
reasons, DJI's implementation of waypoints in DJI Fly does not allow one to
specify either straight lines or curved turns and all waypoint missions
created in DJI Fly are executed using curved turns. Therefore, by default,
this converter will convert all missions to use curved turns.
This checkbox has been added to override this default behavior. By checking
this checkbox, the "useStraightLine" parameter will be set to true in the WPML
code of the KMZ file. However, doing so will cause the waypoint mission to be
displayed incorrectly (wonky like a spiderweb [example 1, example 2]) in DJI Fly. Even so, I have
been told by several users that the mission will be executed correctly with
straight lines even though DJI Fly's display of the mission is incorrect.
Heading Mode
When 'Toward POI or Interpolate' is selected, the existence of a POI for any
waypoint will result in the heading mode being set to "toward POI" at that
waypoint. Otherwise, the heading mode is set to "smooth transition" and the
specified heading angle is used at that waypoint.
When 'Follow Wayline' is selected, every waypoint will have its heading mode
set to "follow wayline" regardless of the existence of either a POI or heading
angle defined at any waypoint.
When 'Manual' is selected, manual control of the aircraft heading will be
allowed throughout the flight regardless of the existence of either a POI or
heading angle defined at any waypoint.
Updates
2023-02-06: Reworked the Google Elevation API code that handles "Above Ground" waypoint heights.
This converter can now read a CSV file created with semi-colons used as delimiters instead of commas. This enables it to be able to read a file created by Grid Mission Designer (ancient.land).
In addition to Litchi CSV files, one can now upload and convert KML files
containing a 3D path.