11. Maintenance and Troubleshooting
11.1 Routine Maintenance
- Cleaning specifications:
- Use an air blower to remove dust from the lens.
- Use a clean soft cloth to wipe the device housing.
- ⚠️ Do not use corrosive solvents to wipe the window glass; corrosive solvents will destroy the glass surface coating. When corrosive solvents enter through the edge gaps of the window glass, they will corrode the waterproof adhesive on the glass, leading to waterproof failure. Prohibited corrosive solvents include but are not limited to: alcohol, isopropanol, white spirit, turpentine, etc.
- Storage conditions:
- Temperature: -20℃ ~ 60℃
- Humidity: < 85% RH
11.2 Common Troubleshooting
For more issues, see 13. FAQ.
| Symptom | Possible Cause | Solution |
|---|---|---|
| No response after power-on | Power supply abnormality | Check 12 V adapter output, whether DC jack is fully inserted, whether aviation plug is locked |
ping 192.168.1.251 fails | PC and device in different subnets / network cable / Ethernet port issue | Set PC Ethernet port to 192.168.1.x/24; restart Ethernet port; replace network cable |
| HTTP Dashboard inaccessible | Port 8080 blocked by firewall / device not fully started | Disable firewall or allow port 8080; wait ~30 s and retry |
| No data output after driver runs | UDP broadcast blocked by firewall / network not in same subnet | Allow UDP 60000–60010; confirm PC and device are in the same subnet. Device discovery, NIC selection and UDP ports are handled automatically by the SDK; no device_ip configuration is needed |
| RViz reports TF transform failure | Device original TF frequency is low, timestamps cannot be interpolated | Set tf_publish_rate:=50 when starting the driver; recommended range 50–200 Hz, 0 disables timed retransmission |
post_process_node crashes when publishing first frame | System OpenCV is inconsistent with the OpenCV linked by ROS cv_bridge | Rebuild vision_opencv / cv_bridge in the current workspace to match the system OpenCV, see 13. FAQ |
| Relocalization keeps failing | Device stationary / wrong map file path / algorithm session not ready | Move the device; check the bin file path; confirm manifold-lc-sdk is installed and map services are called in the correct mode |
| Severe mapping / relocalization drift or packet loss | NIC receive buffer insufficient / UDP packet loss | Enlarge buffers before starting the driver: sudo sysctl -w net.core.rmem_max=16777216 net.core.rmem_default=8388608 net.core.netdev_max_backlog=50000 |
ros2 service call no response | Wrong service name (case mismatch) | Use ros2 service list to confirm the actual service name; in v3.x the device model no longer appears in topic/service paths |
← Previous Chapter:Relocalization Map Acquisition Guide | Next Chapter:Technical Specifications →