Open kkk3449 opened 1 month ago
Thanks for your feedback. sick_multiscan.launch
is the configuration file for SICK multiScan100 lidars. It cannot be used to merge the scan data from two NAV350 devices.
To run two NAV350 lidars, follow the FAQ example and start sick_scan_xd twice with different ip addresses, topics and frame ids:
roslaunch sick_scan_xd sick_nav_350.launch nodename:=sick_nav_350_front hostname:=192.168.127.31 cloud_topic:=cloud_front laserscan_topic:=scan_front frame_id:=nav_350_front
roslaunch sick_scan_xd sick_nav_350.launch nodename:=sick_nav_350_rear hostname:=192.168.127.32 cloud_topic:=cloud_rear laserscan_topic:=scan_rear frame_id:=nav_350_rear
You can then use e.g. the front lidar for slam by providing your system's transform chain in a hector slam configuration file like test_200_slam_ros1_hector.launch. The static_transform_publishers in the hector launch file define the 6D poses (position and orientation) of your lidars relative to a robot frame and must be adapted to your setup. See https://github.com/SICKAG/sick_scan_xd/blob/develop/doc/slam.md for details.
Hello, I want to merge two NAV350 units for autonomous robot navigation. The IP and port of the NAV350s mounted on the robot are as follows.