• Mavlink drones can now fly TTF missions with the altimeter connected to the SkyHub
• Mavlink drones can now be configured using the SkyHub config file
• The SkyHub altimeter can be configured with CPM GUI

• Improve GNSS output precision
• FT742 anemometer driver reports embedded compass state
• The default minimal altitude for the altimeter was changed from 0.5 to 1 meter
• Fix missing messages in the CPM console under the high load
• The Skyhub checks uploaded missions for at least one Rangefinder point
• Fix the true depth header which the Echologger writes into SEGY files

• Laser Falcon driver may get stuck on the startup.

• Supports DJI M350 RTK and DJI M300 RTK drones
• License required for SkyHub functions, existing customers should request a license file from SPH Engineering or a reseller
• Support for FT42 anemometer with multi instances
• Improved performance for MR72 obstacle detector
• Improved performance for NRA24 altimeter

• Improved position.csv log file structure
• Reduced number of records in position.csv log file
• Improved correction of RTK coordinates
• Reduced CPU load for MagNIMBUS and SENSYS MagDrone R1 drivers
• Problems with communication with sensors

• Supports DJI M350 RTK and DJI M300 RTK drones
• License required for SkyHub functions, existing customers should request a license file from SPH Engineering or a reseller
• Support for FT42 anemometer with multi instances
• Improved performance for MR72 obstacle detector
• Improved performance for NRA24 altimeter

• Improved position.csv log file structure
• Reduced number of records in position.csv log file
• Improved correction of RTK coordinates
• Reduced CPU load for MagNIMBUS and SENSYS MagDrone R1 drivers

• Support missions without AGL waypoints
• Check altimeter range at all flight stages
• DJI M350 RTK drones support
• True Terrain Following (TTF) route planning in UgCS, including waypoint altitudes using "rangefinder" altitude type
• Support of routes with a mix of AGL, AMSL and "rangefinder" altitudes
• MagNIMBUS (QuSpin QTFM Gen-2) magnetometer vector add-on support
• Sensys MagDrone R1 magnetometer support
• Geolux LX-80 water level sensor support
• Geolux RSS-2-300 surface velocity radar support

• Reject mission with negative rangefinder altitude values
• Fixed OA activation speed threshold
• Improved Magnimbus performance in multi-instance configuration
• Reduced time lag for the recorded data
• Correct zero point for the GPR SEG-Y log files
• Add the next waypoint index column into the position.csv and MagNIMBUS logs
• Wind sensor FTT372 does not use an embedded compass any more

• DJI M350 RTK drones support
• True Terrain Following (TTF) route planning in UgCS, including waypoint altitudes using "rangefinder" altitude type
• Support of routes with a mix of AGL, AMSL and "rangefinder" altitudes
• MagNIMBUS (QuSpin QTFM Gen-2) magnetometer vector add-on support
• Sensys MagDrone R1 magnetometer support
• Geolux LX-80 water level sensor support
• Geolux RSS-2-300 surface velocity radar support

• Reduced time lag for the recorded data
• Correct zero point for the GPR SEG-Y log files
• Add the next waypoint index column into the position.csv and MagNIMBUS logs
• Wind sensor FTT372 does not use an embedded compass any more

Dropped support for old sensors

• Geonics EM38-MK2 metal detector
• Geonics EM-61conductivity meter
• Attollo Wasp laser altimeter
• Lightware SF11/C laser altimeter
• Radarteam Cobra Plug-In GPR

• Support for multiple scalar widgets was added
• Support for QuSpin Gen-2 magnetometer added
• Possible to install CPM into an existing directory

• Fixed saving of TTF configuration
• Fixed Skyhub logs download

• Removed support for SkyHub v2

• New SkyHub ROS-based SDK for third-party modules development
• Improved Lightware SF-30/D altimeter support: reduced time lag, filtering support
• Added support for Ainteins US-D1 altimeter
• Automatically select altitude source depending on the aircraft simulation state for TTF and GH modes
• The pulse delay value for Radsys Zond Aero LF GPR determined with Prism software can be used in SkyHub configuration as is
• Echo sounders parameters are aligned with the vendor’s manual: FREQUENCY_HZ becomes INTERVAL_S. Values must be changed from Hz to seconds.