mirror of
https://github.com/Livox-SDK/livox_ros_driver.git
synced 2023-04-06 15:49:55 +08:00
Update README.md
This commit is contained in:
livox
GitHub
18
README.md
18
README.md
@@ -12,7 +12,7 @@ For ROS installation, please refer to the ROS installation guide :
|
||||
|
||||
[ROS installation guide](https://www.ros.org/install/)
|
||||
|
||||
    ***Note:***
|
||||
    ***Note : ***
|
||||
|
||||
    (1) Be sure to install the full version of ROS (ros-distro-desktop-full);
|
||||
|
||||
@@ -30,7 +30,7 @@ For ROS installation, please refer to the ROS installation guide :
|
||||
|
||||
`git clone https://github.com/Livox-SDK/livox_ros_driver.git ws_livox/src`
|
||||
|
||||
    ***Note:***
|
||||
    ***Note : ***
|
||||
|
||||
    Be sure to use the above command to clone the code to the local, otherwise it will compile error due to the file path problem.
|
||||
|
||||
@@ -57,7 +57,7 @@ For ROS installation, please refer to the ROS installation guide :
|
||||
|
||||
      When the connection status of the device specified in the configuration file is configured to enable connection (true), the livox_ros_driver will only connect to the device specified in the configuration file;
|
||||
|
||||
    ***Note:***
|
||||
    ***Note : ***
|
||||
|
||||
    (1) the json configuration file is in the "ws_livox/src/livox_ros_driver/config" directory;
|
||||
|
||||
@@ -75,7 +75,7 @@ For ROS installation, please refer to the ROS installation guide :
|
||||
|
||||
    
|
||||
|
||||
    ***Note:***
|
||||
    ***Note : ***
|
||||
|
||||
    X in the figure above corresponds to 1 in MID-100_Left/MID-40/Horizon/Tele products, 2 in MID-100_Middle, and 3 in MID-100_Right.
|
||||
|
||||
@@ -106,7 +106,7 @@ All internal parameters of Livox_ros_driver are in the launch file. Below are de
|
||||
| multi_topic | If the LiDAR device has an independent topic to publish pointcloud data<br>0 -- All LiDAR devices use the same topic to publish pointcloud data<br>1 -- Each LiDAR device has its own topic to publish point cloud data | 0 |
|
||||
| xfer_format | Set pointcloud format<br>0 -- Livox pointcloud2(PointXYZRTL) pointcloud format<br>1 -- Livox customized pointcloud format<br>2 -- Standard pointcloud2 (pcl :: PointXYZI) pointcloud format in the PCL library | 0 |
|
||||
|
||||
    ***Livox_ros_driver pointcloud data detailed description :***
|
||||
    ***Livox_ros_driver pointcloud data detailed description : ***
|
||||
|
||||
1. Livox pointcloud2 (PointXYZRTL) point cloud format, as follows :
|
||||
|
||||
@@ -182,7 +182,7 @@ In the "ws_livox/src/livox_ros_driver/launch" path, there are two json files, li
|
||||
| imu_rate | Int | Push frequency of IMU sensor data<br>0 -- stop push<br>1 -- 200 Hz<br>Others -- undefined, it will cause unpredictable behavior<br>Currently only Horizon supports this, MID serials do not support it | 0 |
|
||||
| extrinsic_parameter_source | Int | Whether to enable extrinsic parameter automatic compensation<br>0 -- Disable automatic compensation of LiDAR external reference<br>1 -- Automatic compensation of LiDAR external reference | 0 |
|
||||
|
||||
    ***Note:***
|
||||
    ***Note : ***
|
||||
|
||||
    When connecting multiple LiDAR, if you want to use the external parameter automatic compensation function, you must first use the livox viewer to calibrate the external parameters and save them to LiDAR.
|
||||
|
||||
@@ -216,7 +216,7 @@ In the "ws_livox/src/livox_ros_driver/launch" path, there are two json files, li
|
||||
| enable_connect | Boolean | Whether to connect to this Hub<br>true -- Connecting to this Hub means that all LiDAR data connected to this Hub will be received<br>false -- Prohibition of connection to this Hub means that all LiDAR data connected to this Hub will not be received | false |
|
||||
| coordinate | Int | Coordinate<br>0 -- Cartesian<br>1 -- Spherical | 0 |
|
||||
|
||||
    ***Note:***
|
||||
    ***Note : ***
|
||||
|
||||
    (1) The configuration parameters enable_connect and coordinate in the Hub configuration item "hub_config" are global and control the behavior of all LiDARs. Therefore, the LiDAR related configuration in the Hub json configuration file does not include these two contents.
|
||||
|
||||
@@ -230,7 +230,7 @@ Prepare a GPS device to ensure that the GPS can output UTC time information in G
|
||||
|
||||
[Timestamp synchronization](https://github.com/Livox-SDK/Livox-SDK/wiki/Timestamp-Synchronization)
|
||||
|
||||
    ***Note:***
|
||||
    ***Note : ***
|
||||
|
||||
    (1) The time stamp synchronization function of livox_ros_driver is based on the LidarSetUtcSyncTime interface of Livox-SDK, and only supports GPS synchronization, which is one of many synchronization methods of livox devices.
|
||||
|
||||
@@ -260,7 +260,7 @@ livox_ros_driver only supports the timestamp synchronization function when conne
|
||||
| baudrate_index | Int | Baud rate of serial device<br>0 -- 2400 <br>1 -- 4800 <br>2 -- 9600 <br>3 -- 19200 <br>4 -- 38400 <br>5 -- 57600 <br>6 -- 115200 <br>7 -- 230400 <br>8 -- 460800 <br>9 -- 500000 <br>10 -- 576000 <br>11 -- 921600 | 2 |
|
||||
| parity_index | Int | parity type<br>0 -- 8bits data without parity<br>1 -- 7bits data 1bit even parity<br>2 -- 7bits data 1bit odd parity<br>3 -- 7bits data 1bit 0, without parity | 0 |
|
||||
|
||||
## 7. Convert lvx point cloud data file (v1.0 / v1.1) to rosbag file
|
||||
## 7. Convert lvx point cloud data file (v1.0/v1.1) to rosbag file
|
||||
|
||||
livox_ros_driver supports the conversion of lvx pointcloud data files to rosbag files. Use the command as follows :
|
||||
|
||||
|
||||
Reference in New Issue
Block a user