ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

64db.xml can be found in the file calibration file in stick member. the 64e_points.launch file can be got by just modifying 32e_points.launch

when run "rosrun velodyne_pointcloud gen_calibration.py 64db.xml" , should make the command run in the 64db.xml 's dictionary.

there are also two matters should be paid attention if want to make it work: a, make sure "sudo ifconfig eth0 192.168.3.100" succeed( chech it by "ifconfig -a",look at whether eth0 becomes 192.168.3.100). There is a problem here: eth0 may not become "192.168.3.100" after "sudo ifconfig eth0 192.168.3.100", I may do this several times.

b, "roslaunch velodyne_pointcloud 64e_points.launch calibration:=/home/user/64db.yaml" "user" should be user's name, my user's name is exbot.

64db.xml can be found in the file calibration file in stick member. the 64e_points.launch file can be got by just modifying 32e_points.launch

when run "rosrun velodyne_pointcloud gen_calibration.py 64db.xml" , should make the command run in the 64db.xml 's dictionary.

there are also two matters should be paid attention if want to make it work: a, make sure "sudo ifconfig eth0 192.168.3.100" succeed( chech it by "ifconfig -a",look at whether eth0 becomes 192.168.3.100). There is a problem here: eth0 may not become "192.168.3.100" after "sudo ifconfig eth0 192.168.3.100", I may do this several times.

b, "roslaunch velodyne_pointcloud 64e_points.launch calibration:=/home/user/64db.yaml" "user" should be user's name, my user's name is exbot.

64db.xml can be found in the file calibration in stick member. the 64e_points.launch file can be got by just modifying 32e_points.launch

when run "rosrun velodyne_pointcloud gen_calibration.py 64db.xml" , should make the command run in the 64db.xml 's dictionary.

there are also two matters should be paid attention if want to make it work: a, make sure "sudo ifconfig eth0 192.168.3.100" succeed( chech it by "ifconfig -a",look at whether eth0 becomes 192.168.3.100). There is a problem here: eth0 may not become "192.168.3.100" after "sudo ifconfig eth0 192.168.3.100", I may do this several times.times(For the ifconfig issue , do “sudo ifdown eth0” and then after a few seconds do “sudo ifup eth0”. After change the interface config you may have to force it to read the new config changes by shutting it down and bringing it back up , and then the problem can be solved).

b, "roslaunch velodyne_pointcloud 64e_points.launch calibration:=/home/user/64db.yaml" "user" should be user's name, my user's name is exbot.