|
| 1 | +--- |
| 2 | +title: Livox MID360 |
| 3 | +pagination_label: Livox MID360 |
| 4 | +description: Livox MID360 |
| 5 | +--- |
| 6 | + |
| 7 | +:::warning |
| 8 | +This page is describing the upcoming ROS2 version of the MRS UAV System (however, it may be still outdated). If you are looking for ROS1 version of the docs, follow to https://ctu-mrs.github.io/docs/1.5.0/introduction/. |
| 9 | +::: |
| 10 | + |
| 11 | +# Ouster |
| 12 | + |
| 13 | +## Installation |
| 14 | + |
| 15 | +The Ouster driver is part of the full installation of the MRS UAV System. |
| 16 | +If you are still missing it, run |
| 17 | +```bash |
| 18 | +sudo apt install ros-jazzy-livox-ros-driver2 |
| 19 | +``` |
| 20 | + |
| 21 | +## Finding out IP address of the sensor |
| 22 | + |
| 23 | +You have to first find out what is the IP address of your Livox lidar, so you can use it later as the parameter to the driver's launchfile. Livox lidars used by MRS and F4F have their IP addresses set statically in the network `192.168.1.1/24`. First, to see the sensor on your network, you have to set the static IP address of your ethernet interface. Here is the example: |
| 24 | + |
| 25 | + |
| 26 | + |
| 27 | +Now you can run the `nmap` command, to search the network for sensor device: |
| 28 | + |
| 29 | +```bash |
| 30 | +$ nmap -sn 192.168.1.1/24 |
| 31 | +``` |
| 32 | + |
| 33 | +You should get the output similar to this: |
| 34 | + |
| 35 | +```bash |
| 36 | +Starting Nmap 7.94SVN ( https://nmap.org ) at 2025-10-24 14:59 CEST |
| 37 | +Nmap scan report for hermiodth (192.168.1.20) |
| 38 | +Host is up (0.00028s latency). |
| 39 | +Nmap scan report for 192.168.1.121 |
| 40 | +Host is up (0.0010s latency). |
| 41 | +Nmap done: 256 IP addresses (2 hosts up) scanned in 2.61 seconds |
| 42 | +``` |
| 43 | + |
| 44 | +Here, we can see our sensor has IP address `192.168.1.121`. |
| 45 | + |
| 46 | +## Startup |
| 47 | + |
| 48 | +```bash |
| 49 | +ros2 launch livox_ros_driver2 livox.launch.py custom_config:=./config/livox.yaml json_config:=./config/mid360_1.json |
| 50 | +``` |
| 51 | + |
| 52 | +- the **custom_config** specifies a custom configuration file |
| 53 | +- the **json_config** specifies the proprietary json config file |
| 54 | + |
| 55 | +Example config file can be found within the [sources](https://github.com/ctu-mrs/livox_ros_driver2/tree/ros2/config) or in |
| 56 | +```bash |
| 57 | +/opt/ros/jazzy/share/livox_ros_driver2/config |
| 58 | +``` |
0 commit comments