To fly DJI drones with UgCS desktop the mobile companion UgCS for DJI is required

Download UgCS for DJI for Android

Release notes for UgCS v.4.8 (728)

New Features

• Implemented quick route renaming. Routes can now be quickly renamed by clicking on the name in the route card without having to go into route parameters.

Changes

• The safe trajectory type has been removed. Together with that, the ability to choose the trajectory type in the route parameters window has been removed as well. All existing and future routes will be calculated using the “Straight” trajectory type.
  For SDK users - Route.trajectoryType field is now deprecated. You must not fill it. If UgCS receives a non-empty Route.trajectoryType it will raise an error: "The field 'trajectoryType' is deprecated."

Fixes

• Fixed a bug from UgCS 4.7 where, when planning a route for Ardupilot vehicles, incorrect turn types were displayed instead of the default Straight / Spline.
• Fixed an issue where sometimes DJI L1 wouldn't stop data recording at the end of a LiDAR Area or LiDAR Corridor segment.
• Camera profile fixes:
  • Profile settings for DJI M2EA thermal camera have been updated to achieve the correct flight height for thermal photogrammetry.
  • DJI Zenmuse X7 focal length value has been updated.
• Improvements in overall application stability.

---

 

Release notes for UgCS v.4.7 (685)

New Features

• Undo/redo operations have been introduced. Ctrl+Z and Ctrl+Y keyboard shortcuts can be used in addition to new buttons in the top bar.
      

• For Ardupilot vehicles, the ability to add additional telemetry fields from MAVLink messages has been introduced. Added telemetry fields are displayed in the telemetry table widget of UgCS and in UgCS Telemetry Viewer.

Changed

• Parrot Anafi support has been discontinued. Parrot VSM and the Parrot Anafi vehicle profiles have been removed from UgCS.
• Desktop shortcuts have been simplified. From now on by default UgCS installer creates only a single UgCS shortcut on the desktop.

Fixes

• Fixed an issue where during route creation "Next" button was sometimes disabled even when a vehicle profile was selected.
• Improvements in overall application stability.
   

---

 

Release notes for UgCS v.4.6 (535)

Fixes

• Fixed an issue where on ArduCopter firmware v.4.1 or newer the drone would rotate clockwise in each turn no matter the direction.
• Fixed an issue where UgCS 4.6.520 would start with an error after an upgrade if the previously installed version contained a manually created vehicle profile with one of the following names: 'Tundra', 'DJI Mavic 2 Enterprise Advanced', 'Fleet Sim Quad', 'DSS F450', 'Parrot Anafi'.

Changes

• Updated Chinese localization.

---

 

Release notes for UgCS v.4.6 (520)

New Feature

• When an aircraft goes offline, it is now still displayed on the map until UgCS is restarted. Hovering the mouse over the aircraft will display the last known latitude and longitude.
  
• A new "Pattern" tool has been introduced. It allows creating a figure-eight LiDAR calibration pattern that can be used within the flight plan. It should be used before each LiDAR area (or LiDAR corridor) segment.
  

Changes

• DJI Matrice 300 RTK now performs the "Circle" segment much smoother. This feature requires UgCS for DJI v.2.34 or newer.
• "Turn type" parameter has been removed from the "Circle" tool. From now on, UgCS chooses the best turn type supported by the aircraft to fly the circle segment as smoothly as possible.
• In the compact telemetry card, the ground speed is now displayed instead of the vertical speed. Vertical speed and other telemetry data are available in the expanded telemetry card.
• A part of the activated license code is now visible in the "License" window. This allows users with multiple licenses to understand which one has been activated.
  
• "Facade scan" tool has been renamed to "Vertical scan" tool.
• In the "Pattern" command parameters window, the "Height" parameter (which defines the bounds of the figure) has been renamed to "Length" so as to never confuse it with the flight altitude.

Fixes

• Log4J vulnerability CVE-2021-44228 has been fixed.
• The error message that is displayed to the user when they try to upload non-georeferenced images as a map layer has been made more understandable.

---

 

Release notes for UgCS v.4.5 (411)

Added

• Added profile for TUNDRA drone.
• DJI Zenmuse L1 recording control (requires UgCS for DJI v.2.33 or newer).
  • From now on, UgCS automatically starts data recording on DJI Zenmuse L1 at the first waypoint of a 'Lidar area' (or 'Lidar corridor') segment and stops data recording at the last waypoint of the segment. A corresponding icon is displayed in the hint for the first and the last waypoint of the segment:
    
    Fig.1 - UgCS - A tooltip for a waypoint with LiDAR recording action
     
  • Also, if it is required to start/stop data recording at a specific waypoint, it can be done using the new 'lidar recording control' action - which is available for waypoints only.
    
    Fig.2 - UgCS - New action added to control LiDAR's recording
     

Changed

• In future it is not required to restart the UgCS server after activation to connect UgCS for DJI via the 'direct connection' option.

• LiDAR tools:

  • Additional hints will help to avoid common mistakes during mission planning for LiDAR.

  • In future each newly created 'Lidar corridor' or a 'Lidar area' segment has the 'Set camera attitude' action with 'Tilt'=90. It is possible to change or remove this action if special settings required.

  • Profiles of 'DJI Zenmuse H20/H20T', 'DJI Zenmuse L1', 'DJI Zenmuse P1' are attached to the 'DJI Matrice 300' profile. New users don't have to attach them manually.

Fixed

• 3D objects weren't imported from some .kmz files.

• An "incorrect input format" error occurred while importing a route for some files exported from the previous versions of UgCS.

• Sometimes, messages in the route calculation log contained wrong number of waypoints.

• Improvements of overall software’s stability.
   

---

 

Release notes for UgCS v.4.4 (382) - hotfix #4

Added

• Introduced the ability to create a LiDAR corridor from KMZ/KML.
• Camera profile for DJI Zenmuse L1.
• [!no full support!] Vehicle profile for DJI Mavic 2 Enterprise Advanced.

Changed

• Outer corner flight path changed for 'Corridor' and 'LiDAR corridor'.
  
• Export options for altitude when exporting a route as a KML:
  • AMSL
  • Relative to ground under 1st waypoint - allowing this exported KML route to be imported and used in DJI Pilot or Autel Explorer

• LiDAR corridor:
  • The algorithm produced a wrong number of passes when 'Side distance' is provided directly but 'Camera' parameter is not empty.
  • The algorithm produced double loops for some turns.
    
  • Sometimes, visual artifacts (like a wavy line) were displayed near turn points.

---

 

Release notes for UgCS v.4.4 (337) - hotfix #3

Added

• For DEMs with a resolution higher than 3 m, the flight path height calculated by UgCS may be not accurate enough. We added 'elevation.pathfindingResolution.default' parameter in 'ucs.properties' file. Reducing the value (default value is 3 meters) increases flight path height precision but takes more time to process the route.

Changed

• The 'Camera' parameter is now optional for 'Lidar Area' and 'Lidar Corridor' tools. If 'Camera' is provided then UgCS takes into account not only FOV of the LIDAR (provided in the 'FOV' parameter of the tool) but also FOV of the camera and chooses the smallest one. Otherwise, UgCS takes into account only FOV of the LIDAR.

Fixed

• For 'Lidar Area' and 'Lidar Corridor' tools:
  • The altitude on loops (added by the tools for sharp corners) may be less than the safe distance over terrain. From now on if a flight altitude on a loop is lower than the safe distance over terrain, UgCS doesn't add this loop to the flight path.
  • The wrong length is displayed in the tooltip for segments with curved lines.
    Duplicated warnings about max descent rate exceeded.
• Minor bug fixes.

---

 

Release notes for UgCS v.4.4 (273) - hotfix #2

Fixed

• Issues with Corridor mapping and LIDAR corridor tools
  • Sometimes altitude calculated in AMSL mode, did not ensure required GSD.
  • Extra passes were created
  • Path with AGL altitude did not correctly followed terrain
  • Issue with calculated camera trigger interval (time/distance) which did not ensure required forward overlap.
• Issues with LIDAR area tool
  • The upload of a route failed due to the error: "Corner radius must be in range from 0.2 to 1,000."
  • The calculation of a route failed due to the error "Can't calculate coordinate for specified location."
• Issue with the calculation of a route due to error "Automatic calculation of camera trigger distance is not supported for this algorithm."
• Minor bug fixes.

---

 

Release notes for UgCS v.4.4 (235) - hotfix #1

Fixed

• Corridor segments with photo camera ignored the set altitude type and generated all segments with AMSL.
   

---

 

Release notes for UgCS v.4.4 (232)

New tools for LIDAR surveying for UgCS ENTERPRISE license
(currently, supported for DJI M300, M600, M210/200 drones only)

• “Lidar area” and “Lidar corridor” tools, although look similar to “Photogrammetry” and “Corridor”, provide additional functionality unlocking the full potential of LIDAR surveying:
  • loops on the turn, reducing shaking of the sensor;
  • area buffer, improving coverage on area borders;
  • an ability to specify side distance manually, or calculate it in UgCS based on the camera FOV and LIDAR’s FOV;
  • the “Corner radius” parameter;
  • visualization of curve lines of the flight path.
• The new command “Pattern” simplifies LIDAR calibration. It can be executed before/after executing a mission and at any time in the middle. UgCS supports the two most popular IMU calibration patterns: U-figure and Eight. You can change pattern size, altitude, and flight speed if required.
  Note: The “Pattern” command and the “Corner radius” parameter require UgCS for DJI 2.30 or newer.
   

More new features

• An ability to control Parrot ANAFI with a joystick
   

Changed

• The calculation algorithm of Photogrammetry and Area Scan segments has been redesigned to avoid flying out of the polygon boundary.
• Important! If you update UgCS from a previous version, check your missions thoroughly for any changes!
• The flight path on overshoots has changed. From now on, decreasing the ground elevation on overshoots does not change the flight path above this area.
• Performance improvements.
• Toolbar icons updated.
• For all DJI vehicle profiles, the "Min distance between waypoints" parameter has been increased to 1 meter.
   

Fixed

• The error ‘Could not parse the KML file’ occurred when importing a KML file with multiple layers.
• Minor bug fixes.
   

UgCS Manuals (PDF)