8. Firmware Upgrade
Odin1 Lite provides two upgrade methods: HTTP Dashboard (recommended) and SDK command-line tool.
8.1 Firmware Acquisition
Please obtain the latest firmware package and corresponding release notes from the download page below.
| Item | Information |
|---|---|
| Firmware download page | https://version.manifoldtech.cn/download/o1l |
| File format | .bin (common for HTTPS OTA / SDK CLI) |
8.2 Firmware Update Content
For firmware version update notes, please contact Liuxing technical support.
8.3 Matching ROS Driver Update Content (v3.7.0 / 20261016)
- Added loop-closure visualization topics, publishing loaded map, key-frame correction result, optimization result and odometry trajectory.
- Added ReMap mode (
device_mode=5,OdinDeviceModeaddskReMap): supports map extension based on a loaded map; host-side loop_closure switches to ReMap, firmware data source processing is consistent with SLAM;SaveMap/LoadMapdescriptions updated to support ReMap; added corrected loop-closure point cloud publishing. - Restored
map_cloudcallback registration; RViz distinguishes loaded, corrected and optimized point clouds with a three-layer color scale, and displays continuous odometry trajectory. - Fixed
map_cloudcoordinate frame and RViz trajectory residual time; restored SDK algorithm control and callback mutex separation. - ROS service return messages and logs now use
OdinResultStrenum names instead of raw error codes. - Added
ExployMaploop-closure map export interface: loop-closure plugin ABI, SDKExployMapAPI and ROS1/ROS2exploy_mapservice are fully transparent; specific export format determined by plugin. - Added static libraries for openssl and crypto.
Important Changes Since v3.2.0
- v3.6.0 / 2026-09-30:
- Added FFmpeg H.264 decoder runtime hardware acceleration auto-detection and dynamic decoder discovery (NVDEC/CUVID/VAAPI/VDPAU), with automatic fallback to software decoding when hardware decoding fails.
- Added VAAPI/VDPAU hardware decoding support (Intel/AMD GPU), and support for specifying device nodes via environment variables
ODIN_CUDA_DEVICE/ODIN_VA_DEVICE/ODIN_VDPAU_DEVICE. - Added optional libyuv integration to accelerate YUV→BGR conversion (H.264/JPEG decoding and NV12 composition paths, approximately 7× faster than libswscale/OpenCV); can be disabled at runtime with
ODIN_DISABLE_LIBYUV=1. - Added device-specific launch files
odin1Lite.launch(.py)(single RGB) andodin2Special.launch(.py)(binocular RGB). - Breaking change: topic/service naming removed the device model segment; the per-device prefix changed from
/{topic_prefix}/{model}/device{N}/to/{topic_prefix}/device{N}/(e.g.,/manifold/ODIN2/device0/→/manifold/device0/). device_onlinemessage JSON added device model field;device_offlinechanged from pure SN string to JSON.
- v3.2.0 / 2026-08-22:
- Removed
control_command.yaml; data stream switches migrated to launch parameters. - Added
set_channel_config/get_channel_configandset_post_process_config/get_post_process_configservices, supporting batch hot switching. - Added
opencv_undistort_node. - Added
cloud/rawrow filter parametersenable_row_filter/min_row. - Fixed point cloud transport plugin
point_cloud_transport.
- Removed
- v3.1.0 / 2026-08-13:
- Breaking change: launch parameter
operating_moderenamed todevice_mode. - Breaking change:
image_formatoptions adjusted, removedyuyv/nv21/rgb24, addedh264; now supportsmjpeg|h264. - Breaking change:
sensor_modedefault changed from1(High Peak) to-1(do not send, keep device current mode). - Breaking change: default
frame_idvalues for each sensor changed to semantic names (lidar,camera0,camera1,imu, etc.). - Added ROS services:
set_sync_mode/get_sync_mode,set_adaptive_param/get_adaptive_param,reset_initial_pose,restore_default_config,get_ptp_sync_status,set_diag_monitor. - Added device-side filter launch parameters and
tf_publish_rate.
- Breaking change: launch parameter
- v3.0.x and earlier: Initial v3.x firmware support, dense depth / colored point cloud nodes, point cloud reprojection, Jetson/Rockchip MJPEG hardware decoding, ROS2 Jazzy support.
8.4 Upgrade Method 1: HTTP Dashboard (Recommended)
⚠️ Do not run the ROS driver during upgrade, and do not power off. It is recommended to use a stable wired network.
- Open a browser and visit
http://192.168.1.251:8080(keep PC and device in the same subnet). - Open the Update page, and drag the firmware package
.bininto the upload area (or click to select). - The system will automatically verify the signature and install; a progress bar will be displayed during the process.
- After installation, the device restarts automatically; after the Dashboard becomes accessible again, enter the Dashboard page to verify:
- Whether the firmware version is updated to the target version
- Whether the device serial number is consistent
- Whether temperature / frame rate are back to normal ranges
8.5 Upgrade Method 2: SDK Command-line Tool
Suitable for server / automated deployment scenarios. Prerequisite: SDK has been built (module/sdk_api/build/odin_upgrade).
# Auto-discover device and upgrade
./build/odin_upgrade /path/to/firmware_v<version>.bin
# Specify device IP
./build/odin_upgrade /path/to/firmware.bin --device 192.168.1.251
# Specify discovery timeout
./build/odin_upgrade /path/to/firmware.bin --timeout 5000
The upgrade link is based on mTLS mutual authentication + Ed25519 signature, fully encrypted; signature verification failure will immediately abort installation without damaging the device.
8.6 Calibration File Management (Also HTTPS-based)
- HTTP Dashboard → Dashboard → Calibration File Management: upload / download
camera_calib_<SN>.yaml -
Command-line tool:
# Get calibration ./build/odin_get_calibration --device 192.168.1.251 --output ./camera_calib.yaml # Write calibration ./build/odin_send_calibration ./camera_calib.yaml --device 192.168.1.251
← Previous Chapter:Odin1 Lite Quick Start (Ubuntu) | Next Chapter:Relocalization User Guide →