Skip to content

Hesai LiDAR SDK 2.0

  • Software
  • Perception
  • Driver or SDK

A C++ SDK for receiving and parsing point cloud data from Hesai LiDAR sensors, online over the network or offline from PCAP files.

Made by Hesai Technology, China (checked on github.com/HesaiTechnology (opens in a new tab)).

Source on GitHub: github.com/HesaiTechnology/HesaiLidar_SDK_2.0 (opens in a new tab). Facts read at commit 534c707 (opens in a new tab).

Licenses

Code
BSD-3-Clause (opens in a new tab)

Read by Robotheca from LICENSE (opens in a new tab) (BSD-3-Clause) at commit 534c707 (opens in a new tab), on 16 Oct 2026.

Commercial use
Yes

What it does

  • Parses live point cloud and fault data streamed by Hesai lidars, and can also parse recorded PCAP files offline.
  • Supports a broad range of Pandar, OT, QT, XT, AT, FT and JT lidar models, listed in a compatibility table.
  • Offers optional point cloud visualization through PCL, saving to PCD files, and coordinate transformation.
  • Can filter packets by source IP and port to separate data from several lidars, and run two SDK instances in parallel.
  • Provides optional GPU acceleration, multi-threaded parsing, per-point timestamps, and PTC API commands for lidar configuration.
  • Builds with CMake; the SDK can be compiled without OpenSSL when PTCS communication is not needed.

Written by Robotheca from the project's README (opens in a new tab) at commit 534c707.

Getting started

Difficulty
Intermediate
Hardware it needs, as the project states it
Operating systems: Ubuntu 16/18/20/22.04 and Windows 10. Compilers: CMake 3.8.0 or later with G++ 7.5 or later on Ubuntu, or MSVC 2019 or later on Windows. Optional dependencies: PCL for visualization, libpcap for PCAP files, and OpenSSL for TLS/mTLS PTCS communication.

Maintenance

Status
Maintained: a commit in the last 12 months
Newest commit
27 Apr 2026 on master
Latest release
v2.0.12 (27 Apr 2026)

Checked on GitHub on 16 Oct 2026.

Robots that can run it

No robot on Robotheca is linked to it yet. Links come from a robot's robot.yaml, from its dependency files read as text, or from Robotheca's editors.

Robotheca lists software as a reference: nothing is hosted or run here, and every fact links to where it was read.