Closed 130s closed 10 years ago
Temporary fix worked was (by @k-okada):
RTCTREE_NAMESERVERS=hiro014:15005
roslaunch hrpsys_ros_bridge collision_detector.launch MODEL_FILE:=/opt/jsk/etc/HIRONX/model/main.wrl CONF_FILE:=
rospack find hironx_ros_bridge/conf/kawada-hironx.conf nameserver:=hiro014
sorry for late replay, https://github.com/start-jsk/rtmros_common/pull/461 will fix this problem
On Thu, May 1, 2014 at 10:43 PM, Isaac Isao Saito notifications@github.comwrote:
Temporary fix worked was:
- Set robot's host name in environment variable: RTCTREE_NAMESERVERS=hiro014:15005
- Specify nameserver as an argument like: roslaunch hrpsys_ros_bridge collision_detector.launch MODEL_FILE:=/opt/jsk/etc/HIRONX/model/main.wrl CONF_FILE:=rospack find hironx_ros_bridge/conf/kawada-hironx.conf nameserver:=hiro014
— Reply to this email directly or view it on GitHubhttps://github.com/start-jsk/rtmros_common/issues/453#issuecomment-41910708 .
Trying to give
nameserver
as an argument toroslaunch
command (below I added enter to the 1st line to fold the long line).roslaunch hironx_ros_bridge hironx_ros_bridge.launch nameserver:=hiro014
is running on another terminal.I modified
hrpsys_ros_bridge/launch/collision_detector.launch
as follows but no good.