Skip to content
Trending eventDeveloping

livox_gz_sim: Livox Mid-360 and HAP simulation for Gazebo Harmonic

1 reports1 reporting sourcesUpdated 2 hours ago

Overview

Event synthesis

mathai released livox_gz_sim, a Gazebo Harmonic plugin that simulates Livox Mid-360 and HAP lidars. It uses recorded non-repetitive scan patterns to build coverage over frames, publishes messages in the livox_ros_driver2 format with per-point timestamps, simulates the Mid-360's IMU at 200 Hz, and adds range/angle noise and reflectivity from datasheets. The tool is GPU agnostic (unlike existing CUDA-dependent options), supports multiple sensors and configurable rates, and allows world resets. Stacks like FAST-LIO run unchanged because the output matches the driver.

Generated from attributed reports · Updated 1 hours ago

Event evidence and corrections

0 attributed source owners. Ownership does not establish independent confirmation. Quantities are reported separately and are never added together.

Environment: simulation
Supporting report

“livox_gz_sim: Livox Mid-360 and HAP simulation for Gazebo Harmonic”

Exact source · revision 2

Source owner not reported

Reported quantity · percent: 0 other · Basis not reported
Supporting report

“or Publishes livox_ros_driver2/CustomMsg or PointCloud2 in the driver’s 26-byte layout ( xfer_format 0/1), with per-point timestamps Simulates the Mid-360’s IMU at 200 Hz Adds range and angle noise from the datasheet, and reflectivity (0–255) from <laser_retro> Supports multiple sensors, configurable publish rate and downsampling, and world resets Because the output matches the driver, stacks like FAST-LIO run on it”

Exact source · revision 2

Source owner not reported

Reported quantity · hours: 0 other · Basis not reported
Supporting report

“or Publishes livox_ros_driver2/CustomMsg or PointCloud2 in the driver’s 26-byte layout ( xfer_format 0/1), with per-point timestamps Simulates the Mid-360’s IMU at 200 Hz Adds range and angle noise from the datasheet, and reflectivity (0–255) from <laser_retro> Supports multiple sensors, configurable publish rate and downsampling, and world resets Because the output matches the driver, stacks like FAST-LIO run on it”

Exact source · revision 2

Source owner not reported

Reported quantity · robots: 0 other · Basis not reported
Supporting report

“or Publishes livox_ros_driver2/CustomMsg or PointCloud2 in the driver’s 26-byte layout ( xfer_format 0/1), with per-point timestamps Simulates the Mid-360’s IMU at 200 Hz Adds range and angle noise from the datasheet, and reflectivity (0–255) from <laser_retro> Supports multiple sensors, configurable publish rate and downsampling, and world resets Because the output matches the driver, stacks like FAST-LIO run on it”

Exact source · revision 2

Source owner not reported

Reported quantity · trajectories: 0 other · Basis not reported
Supporting report

“or Publishes livox_ros_driver2/CustomMsg or PointCloud2 in the driver’s 26-byte layout ( xfer_format 0/1), with per-point timestamps Simulates the Mid-360’s IMU at 200 Hz Adds range and angle noise from the datasheet, and reflectivity (0–255) from <laser_retro> Supports multiple sensors, configurable publish rate and downsampling, and world resets Because the output matches the driver, stacks like FAST-LIO run on it”

Exact source · revision 2

Source owner not reported

Report timeline

Follow attributed reports and material updates.

11/1
  1. ROS Discourse — Community updatesSignal
    livox_gz_sim: Livox Mid-360 and HAP simulation for Gazebo Harmonic

    mathai released livox_gz_sim, a Gazebo Harmonic plugin that simulates Livox Mid-360 and HAP lidars. It uses recorded non-repetitive scan patterns to build coverage over frames, publishes messages in the livox_ros_driver2 format with per-point timestamps, simulates the Mid-360's IMU at 200 Hz, and adds range/angle noise and reflectivity from datasheets. The tool is GPU agnostic (unlike existing CUDA-dependent options), supports multiple sensors and configurable rates, and allows world resets. Stacks like FAST-LIO run unchanged because the output matches the driver.

Event coverage history

There is not enough continuous observation data to show a trend.

Timezone · UTC

Article dates follow your selected timezone. Briefing editions use Hong Kong time (UTC+8).