Open Source RoboticsRobots, software & learning

Livox SDK2

Software

C/C++ interfaces and samples for network communication with supported Livox lidar devices. [1] [2] [4]

Installation & first result →Official websiteGetting started

For
Robotics developers evaluating the selected source workflow [1] [2] [4]
Hardware
Livox HAP and Mid-360 examples [1]
Source rights
Named licenses are documented by part. Review licenses

Source researched · Not tested by us
Sources checked · Research details

Licenses & related hardware

Requirements · Research details and dates

On this page

Overview

Livox SDK2 provides C/C++ interfaces and samples for communicating with supported Livox lidars, including model-specific workflows for HAP and Mid-360. It supplies host software rather than open lidar hardware or sensor firmware. Select the actual device model and protocol/configuration before interpreting a sample as an acquisition recipe. [1]

The README lists Ubuntu 18.04 or later and Windows 10/11, a C++11 compiler and CMake 3 or later. Its Ubuntu build creates a build directory, runs CMake and make, then optionally installs libraries/headers. Windows instructions use Visual Studio 2019 with the selected architecture. Those are upstream routes, not builds reproduced in this review. [1]

The quick-start executable requires a JSON configuration path. The README names hap_config.json and mid360_config.json for model-specific configuration and describes host/lidar addresses and ports. Choose the HAP or MID360 section, then inspect host_net_info.host_ip, lidar_ip and the separate lidar_net_info and host_net_info port values. Matching a configuration does not mean making host and lidar ports identical; reconcile the actual model, host interface and addresses. Logger configuration and firmware upgrade are separate operations; no device settings or firmware were changed here. [1]

The inspected main function rejects missing arguments and SDK initialization failure, then registers point-cloud, optional IMU and device-information callbacks. Its device-information callback actively requests normal work mode, double-echo data, ESC speed, point-cloud frequency and special time filtering. Review those requests against the selected model; this review does not establish their success. Point-cloud and IMU diagnostic printing is commented out, so enable suitable logging or add actual data handling to confirm receipt. The sample sleeps before normal termination; its final message/zero exit status alone cannot establish valid packets. Confirm actual callback data and the selected lidar state when attempting acquisition. These are source-based prerequisites, not observed capture results. [4]

The actual LICENSE.txt grants MIT for the portions it identifies and includes separate third-party notices. That is narrower than a blanket grant for every dependency; purchased sensors and firmware retain separate terms. No SDK compilation, network session, point-cloud or IMU capture, firmware upgrade, calibration or performance test was performed. The bounded next step is matching one model's JSON/network configuration and inspecting the callback path before running the sample on real hardware. [1] [2] [4]

Is this for you?

Known limitations
  • Scoped SDK MIT declaration does not open the lidar hardware or firmware.
  • Sample init/callback registration and normal termination do not prove packets or calibrated point clouds were received.
  • Device model and firmware/network compatibility need exact configuration; no capture or upgrade run.
  • Quick-start device callback issues configuration commands; diagnostic point/IMU printing is commented out. Init or normal exit does not prove packet reception.

Editorial assessment of bounded source evidence; no runtime, fit, manufacturing or compatibility proof.

[1] [2] [4] · Editorial assessment

What you need

Operating system
  • Ubuntu 18.04 or later; Windows 10/11, as upstream documents (not independently tested).

Source-reported requirement/configuration, not a tested installation, compatibility matrix or measured runtime result.

[1]

Languages / runtimes
  • C/C++ API; C++11 compiler required by the documented setup.

Source-reported requirement/configuration, not a tested installation, compatibility matrix or measured runtime result.

[1]

Dependencies
  • Documented Ubuntu18.04+ or Windows10/11, C++11 compiler and CMake3+
  • Compatible Livox lidar, model-specific JSON configuration and matched host/IP/ports

[1] [2] [4]

Compute for the workload
  • Documented x86 or ARM host architecture; no quantified CPU/RAM/VRAM minimum established.

Source-reported requirement/configuration, not a tested installation, compatibility matrix or measured runtime result.

[1]

Installation & first result

Open the upstream getting-started guide [1] [2] [4]

  • Inspect the pinned implementation and select the exact configuration described in the article.
  • Follow the chosen upstream environment/build route, resolving the listed dependencies before runtime or hardware integration.

Editorial assessment of bounded source evidence; no runtime, fit, manufacturing or compatibility proof.

[1] [2] [4] · Editorial assessment

Installation

Build the selected Livox SDK2 source with CMake/make on the documented host, then inspect the model-specific HAP/MID360 JSON and quick-start callback before connecting; no build or device operation reproduced.

Source-reported requirement/configuration, not a tested installation, compatibility matrix or measured runtime result.

[1] [4]

Hardware, models & data

Supported hardware
  • Livox HAP and Mid-360 examples; exact model/firmware/network pairing must be checked.

Source-reported requirement/configuration, not a tested installation, compatibility matrix or measured runtime result.

[1]

What we checked

Pinned source and selected artifact structure review only; no dependency installation, upstream build, native CAD/kernel/fit/strength validation, fabrication, wiring, calibration, simulation, powered operation or performance testing. Original archives stay private.

Not yet established

  • Requirements: host computer

Updates

Upstream last updated
Not established
Latest release
Not established
Profile updated
Nov 1, 2026
Sources last checked
Nov 1, 2026
Next review
Dec 1, 2026
Reviewed revision
c0796f0

Source files and licenses

Distinct inspectable robotics software/data workflow with specific contribution and bounded next source-investigation step; not performance or physical-build certification.

LayerAvailability / license
softwareavailable · MIT (identified portions)
LICENSE.txt grants MIT for the portions it identifies and includes separate third-party notices. Sensor hardware, firmware and external dependencies retain separate terms. [4] [2]
documentationavailable · MIT (identified portions)
LICENSE.txt grants MIT for the portions it identifies and includes separate third-party notices. Sensor hardware, firmware and external dependencies retain separate terms. [1] [2]

Outside the selected contribution; no separate released layer claimed.

References

Each source links to the exact revision we read. “Used for” shows where this page relies on it.

Correction guidance · Discussion is not enabled · Profile format 0.7.0-draft.5

Change history