9. Relocalization User Guide
9.1 Description
Odin1 Lite supports the following operating modes, switched via the ROS service device_mode:
| mode | Mode | Description |
|---|---|---|
| 0 | Standby | Standby |
| 1 | Normal | Normal operation (default) |
| 2 | Upgrade | Upgrade mode |
| 3 | SLAM | Mapping mode; driver also switches the algorithm to Build mode |
| 4 | Relocation | Relocalization mode; driver also switches the algorithm to Reloc mode |
| 5 | ReMap | Relocalization + incremental mapping mode; extends the map on the loaded map |
Relocalization / ReMap are provided jointly by the ROS Driver and the algorithm deb package (
manifold-lc-sdk). When only the ROS Driver is deployed, the device can output point cloud, image, IMU and odometry data normally, but cannot run mapping, relocalization or incremental mapping algorithms.Please ensure the firmware has been upgraded to the latest version.
9.2 Usage Tutorial
9.2.1 Prerequisites
- A ROS Driver matching the device firmware version has been obtained, built and started.
-
A
manifold-lc-sdkalgorithm deb package matching the current host platform has been installed:# Run the detection script on the host running the ROS Driver chmod +x download_lc_sdk.sh ./download_lc_sdk.sh # Download the deb package marked RECOMMENDED in the script output, then install sudo dpkg -i manifold-lc-sdk_<version>_<architecture>.debThe detection script is located at download_lc_sdk.sh. The script only outputs applicable download links and will not automatically download or install the deb package.
-
A usable map file has been saved through SLAM mode, and its host local path is confirmed.
-
Load the ROS environment in the terminal where the ROS Driver was started or in a new terminal:
cd ~/catkin_ws source install/setup.bash
9.2.2 Mapping (SLAM)
# Step 1: Switch to SLAM mapping mode
ros2 service call /manifold/device0/device_mode \
odin_ros_driver_rev1/srv/DeviceMode "{mode: 3}"
# Step 2: Move the device to collect map data...
# Step 3: Save the map after collection
ros2 service call /manifold/device0/save_map \
odin_ros_driver_rev1/srv/SaveMap "{path: '/tmp/odin_map.bin'}"
# Step 4: Switch back to Normal mode
ros2 service call /manifold/device0/device_mode \
odin_ros_driver_rev1/srv/DeviceMode "{mode: 1}"
❗ Do not exit the driver directly with
Ctrl+Cduring mapping; you must callsave_mapto save the map first.
9.2.3 Relocalization
# Step 1: Switch to relocalization mode
ros2 service call /manifold/device0/device_mode \
odin_ros_driver_rev1/srv/DeviceMode "{mode: 4}"
# Step 2: Load the previously saved map
ros2 service call /manifold/device0/load_map \
odin_ros_driver_rev1/srv/LoadMap "{path: '/tmp/odin_map.bin'}"
# Step 3: Move the device and wait for relocalization to succeed...
# Step 4: After relocalization completes, switch back to Normal
ros2 service call /manifold/device0/device_mode \
odin_ros_driver_rev1/srv/DeviceMode "{mode: 1}"
9.2.4 Confirming Relocalization Results
A successful load_map service response only means the map has been loaded by the algorithm session. After loading, please move the device for a distance, and confirm whether relocalization has converged according to the application-side localization status and pose output.
⚠️ Odin1 Lite cannot complete relocalization while stationary; please do not judge relocalization failure when the device is stationary.
9.3 Notes
- Map saving depends on the loop-closure algorithm session being ready (device connected and calibration available); if the session is not ready, the service returns a non-zero
error_code. modeoutside the 0–5 range returnskInvalidArgument.- Device not connected returns
kNotInitialized. - Please use
ros2 service listto confirm the actual service name; in v3.x the device model no longer appears in topic/service paths.
← Previous Chapter:Firmware Upgrade | Next Chapter:Relocalization Map Acquisition Guide →