- My installing procedure about turtlebot2 on neotic (ubuntu 20.04 focal)
- You need to install this first.
- Details see kobuki.sh
# create workspace
mkdir ./kobuki_ws/src/ -p
cd ./kobuki_ws/src/
# clone some source code
sh ./kobuki.sh
# make
cd ../
catkin_make
# source
source ./devel/setup.bash
- Only clone the
yujinrobot/kobuki
repo andcatkin_make
it will generateCould not find a package configuration file provided by "kobuki_msgs"
, so addyujinrobot/kobuki_msgs
. - Then error messages turn to
Could not find a package configuration file provided by "yocs_controllers"
, with referenced from install_basic.sh, it needs to cloneyujinrobot/yujin_ocs
. - Same,
Could not find a package configuration file provided by "kobuki_dock_drive"
, addyujinrobot/kobuki_core
. - Same,
Could not find a package configuration file provided by "ecl_mobile_robot"
, with referenced from kobuki_core.rosinstall, addstonier/ecl_*
. - Finally,
source ./devel/setup.bash
and finish.
All turtlebot packages are fully stable on ROS Melodic so if you want to have those in a Noetic Distribution you may want to clone all the repositories in you catkin workspace and compile them in you enviroment. If you install all needed dependencies you should not have any problem since, generally speaking, any package stable in Melodic is likely to work properly under Noetic.
- Details see turtlebot2.sh
# create workspaces
mkdir ./turtlebot2_ws/src/ -p
cd ./turtlebot2_ws/src/
# setup envroinment of mkbuki
source <xxx>/kobuki_ws/devel/setup.bash
# clone some source code
sh ./turtlebot2.sh
# make
cd ..
catkin_make
# source
source ./devel/setup.bash
- These procedures are almost same with https://github.com/gaunthan/Turtlebot2-On-Melodic.
- If
kobuki
is not be installed first, it will generate some errors:Could not find a package configuration file provided by "kobuki_driver"
. turtlebot/turtlebot_viz
installrviz
forturtlebot_rviz_launchers
.
roslaunch turtlebot_bringup minimal.launch
roslaunch turtlebot_teleop keyboard_teleop.launch
roslaunch turtlebot_rviz_launchers view_robot.launch
- Kobuki : device does not (yet) available, is the usb connected?.
Then do the obvious – make sure kobuki is turned on (leds should be active on the kobuki) and the cable is plugged in. If you are sure about both of these, check to see that your system has had the udev rule applied for /dev/kobuki
ls -n /dev | grep kobuki # nothing
rosrun kobuki_ftdi create_udev_rules
ls -n /dev | grep kobuki # has one