Cannot specify empty namespace to multisense.launch

Issue #35 wontfix
Ryohei Ueda created an issue

Cannot specify empty namespace when I call multisense.launch

$ roslaunch multisense_bringup multisense.launch ip_address:= launch_robot_state_publisher:=false namespace:=""
... logging to /home/jskuser/.ros/log/aa89fec8-ad16-11e4-bad4-00031d0c7c5c/roslaunch-fuji-13345.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server


 * /multisense/multisense_driver/sensor_ip
 * /multisense/multisense_driver/sensor_mtu
 * /multisense/multisense_driver/tf_prefix
 * /rosdistro
 * /rosversion

    color_laser_publisher (multisense_ros/color_laser_publisher)
    multisense_driver (multisense_ros/ros_driver)


core service [/rosout] found
process[multisense/multisense_driver-1]: started with pid [13356]
[ INFO] [1423145378.923197415]: hardware does not support a laser
process[multisense/color_laser_publisher-2]: started with pid [13363]
[ INFO] [1423145379.773622236]: camera frame id: /multisense/left_camera_optical_frame
^C[multisense/color_laser_publisher-2] killing on exit
[multisense/multisense_driver-1] killing on exit

Comments (2)

  1. Matt Alvarado

    Hi Ryohei,

    It appears that roslaunch does not register empty string arguments. The best way to run the MultiSense ROS driver with an empty namespace is to use rosrun directly. For example the following command would work for your application.

    rosrun multisense_ros ros_driver _tf_prefix:="" _sensor_ip:=""

    Matt Alvarado
    Carnegie Robotics

  2. Chris Osterwood

    This is a limitation with ROS, not specific to our ROS driver. Closing issue as "won't fix" and recommend using Matt's rosrun suggestion.

  3. Log in to comment