ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2016-07-08 13:34:22 -0500 | received badge | ● Popular Question (source) |
2016-07-08 13:34:22 -0500 | received badge | ● Notable Question (source) |
2016-07-08 13:34:22 -0500 | received badge | ● Famous Question (source) |
2016-05-31 02:54:17 -0500 | received badge | ● Enthusiast |
2016-05-31 02:54:17 -0500 | received badge | ● Enthusiast |
2016-05-19 00:45:46 -0500 | asked a question | Kobuki : device does not (yet) available on this port, waiting... Hi, I am currently going through the tutorial of Kokubi, but I cannot even finish the keyboard teleoperation. I have connected the usb, and checked the connections: ubuntu@tegra-ubuntu:~$ lsusb Bus 002 Device 009: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Bus 002 Device 004: ID 1d27:0601 ASUS Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Bus 002 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:07dc Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Obviously the first one shows kobuki is connected. However, ubuntu@tegra-ubuntu:~$ ls -n /dev | grep kobuki ubuntu@tegra-ubuntu:~$ and I run: roslaunch kobuki_node minimal.launch --screen got: NODES / diagnostic_aggregator (diagnostic_aggregator/aggregator_node) mobile_base (nodelet/nodelet) mobile_base_nodelet_manager (nodelet/nodelet) auto-starting new master process[master]: started with pid [17229] ROS_MASTER_URI=http://localhost:11311 setting /run_id to f22f08fc-c0b1-11d3-a516-00044b25b4e5 process[rosout-1]: started with pid [17242] started core service [/rosout] process[mobile_base_nodelet_manager-2]: started with pid [17250] process[mobile_base-3]: started with pid [17258] process[diagnostic_aggregator-4]: started with pid [17261] Could any one help to find out the reason? Thank you, Bin |