Quantcast
Channel: ROS Answers: Open Source Q&A Forum - RSS feed
Viewing all 670 articles
Browse latest View live

Issues with catkin_ws/src

$
0
0
I don't know what is wrong, but everytime I follow a tutorial and have to use the catkin workspace src folder or similar then I get an issue. I'm in doubt can this issue be solved? what can I do to fix it? Or do I have to reinstall ROS? Just an example but this is everytime I try with anything: kevin@kevin-Lenovo:~$ cd dev/catkin_ws/src/ bash: cd: dev/catkin_ws/src/: No such file or directory is the issue the location? /home/kevin/ros/catkin_ws I use ROS Indigo and Ubuntu 14.04 trusty I'll be so grateful if someone can help me solve this. I would love to learn ROS. Thanks have a great day to all. btw I'm trying to run ROS with arduino through ros-serial: $ sudo apt-get install ros-indigo-rosserial-arduino $ sudo apt-get install ros-indigo-rosserial $ cd dev/catkin_ws/src/ $ git clone https://github.com/ros-drivers/rosserial.git $ cd dev/catkin_ws/ $ catkin_make $ catkin_make install $ source install/setup.bash

source setup.bash in install space does not work when deployed onto different machine

$
0
0
I install my catkin workspace on machine A to a directory (e.g. `/home/usera/catkin_ws/install`) and would like to use it on machine B in a different location (let's say a different user home, e.g. `/home/userb/catkin_ws/install`). My setup uses another workspace in /opt/overlay/ that is overlayed. Now, on machine A everything works fine, when I source the setup.bash (therefore I check the ROS_PACKAGE_PATH, which is `/home/usera/catkin_ws/install/share:/opt/overlay/share:/opt/ros/kinetic/share`). Unfortunately, on machine B, sourcing setup.bash does not work, the ROS_PACKAGE_PATH is `opt/overlay/share:/opt/ros/kinetic/share`. I have found the following ROS answers: - http://answers.ros.org/question/243124/deploy-ros-package/?answer=243140#post-id-243140 - http://answers.ros.org/question/226581/deploying-a-catkin-package/?answer=226725#post-id-226725 So apparently ROS uses absolute paths and I need to mirror the install location in machine A to machine B, in order to get the install space working on machine B. So my questions are: - Is there a way to deploy the install space to machine B to a different location than on machine A (no location mirroring)? - If not, what is the advantage of having absolute paths? As this makes deployment of ROS binaries via an install space very cumbersome in my opinion.

Having trouble recompiling ROS Source / What to do when you have two versions of ROS installed?

$
0
0
Good morning, I have successfully installed ROS Indigo from source following the instructions at: http://wiki.ros.org/indigo/Installation/Source Everything works great as far as I can tell, the installation succeed without errors. I am trying to verify that I am running off of the source install rather than the installation I had on my computer previously(regular indigo v. source indigo). I attempted to test this by editing a std:cout in rosout.cpp so that I would see a change at the beginning of a log after I recompiled. It did not change though. This is how I recompiled after making the changes to rosout.cpp: ./src/catkin/bin/catkin_make_isolated --pkg rosout --force-cmake Then I ran: roscore rosrun turtlesim turtlesim_node rosrun turtlesim turtle_teleop_key to regenerate some log files. The log files did not change though which leads me to believe that I didn't compile the source code correctly, or I a not running my turtlesim example off of the source installation. Some Info: dev@dev-VirtualBox:/opt$ printenv | grep ROS ROS_ROOT=/opt/ros/indigo/share/ros ROS_PACKAGE_PATH=/opt/ros/indigo/share:/opt/ros/indigo/stacks ROS_MASTER_URI=http://localhost:11311 ROSLISP_PACKAGE_DIRECTORIES= ROS_DISTRO=indigo ROS_ETC_DIR=/opt/ros/indigo/etc/ros I am not sure how to confirm / solve those issues. Does anyone know if I should be adding something to my bashrc? Thanks!

catkin_make -j2

$
0
0
Hi, Me and a fellow student is working on an Autonomous boat project, and while building catkin folders, we struggled with normal use of catkin_make. Tutorials referred to the option -j2 as argument. What does this actually do? we are using a raspberry pi 3b with ubuntu mate. Thanks - Andreas

How can I solve catkin error: "use of old-style cast"?

$
0
0
Catkin gives me an error on some third-party header files, which I included in my code. The error message says, the code was using old-style casts. I know, that the error results from the compiler option -Werror=old-style-cast, but I wasn't able to find an easy workaround without removing the flag from my CMakeLists.txt. I would like to allow old-style casts temporarily by passing the right compiler option to catkin_make or catkin build, but all my attempts have failed so far.

why my Python code is running?

$
0
0
I playing alot with :::ROS and I realize this: I can modify my Python app and start it again by doing: > $rosrun mypkg mypython.py no need to go back to catkin workspace and do catkin_make but if I do that (catkin_make) everything works too... then what is the sense behind the **catkin_make** command

Is the Tag in Package.xml redundant?

$
0
0
Am learning :::ROS from here: http://wiki.ros.org/ROS/Tutorials/WritingPublisherSubscriber%28c%2B%2B%29 but is not 100% clear to me what is this in the package.xml file > find_package(catkin REQUIRED> COMPONENTS roscpp rospy std_msgs> genmsg) I need to do **REQUIRED** and **COMPONENTS**, but hold on, is not a **roscpp** required too? what belowns to **REQUIRED** and what to **COMPONENTS** ??? Thanks!

Failure processing 'collada_parser' while building catkin workspace. ROS indigo on Rasberry Pi Jessie.

$
0
0
For the past couple of days I have been following [This guide](http://wiki.ros.org/ROSberryPi/Installing%20ROS%20Indigo%20on%20Raspberry%20Pi) to install ROS indigo on my Raspberry Pi 2 with debian Jessie. I followed the guide without encountering any difficulties... until I started building the Catkin workspace. While processing the 87th package, it threw me an error saying: Failed to process package 'collada_parser' I have looked around multiple forums and tried some potential solutions including ldconfig -v But none seem to work. There is one part of the guide which I didn't follow which was to [patch collada_urdf](https://github.com/ros/robot_model/issues/12). I'm not sure if this is the cause of this error since I am getting a failure with 'collada_parser' and not 'collada_urdf'. The output pertaining to the collada_parser failure is as follows: /home/pi/ros_catkin_ws/src/robot_model/collada_parser/src/collada_parser.cpp:1168:47: error: ‘class urdf::Link’ has no member named ‘visual’ /home/pi/ros_catkin_ws/src/robot_model/collada_parser/src/collada_parser.cpp:1169:18: error: ‘class urdf::Link’ has no member named ‘collision’ /home/pi/ros_catkin_ws/src/robot_model/collada_parser/src/collada_parser.cpp:1169:47: error: ‘class urdf::Link’ has no member named ‘visual’ /home/pi/ros_catkin_ws/src/robot_model/collada_parser/src/collada_parser.cpp: In member function ‘void urdf::ColladaModelReader::_ExtractRobotAttachedActuators(ColladaDOM150::domArticulated_systemRef)’: /home/pi/ros_catkin_ws/src/robot_model/collada_parser/src/collada_parser.cpp:2039:40: error: ‘class urdf::Joint’ has no member named ‘limits’ /home/pi/ros_catkin_ws/src/robot_model/collada_parser/src/collada_parser.cpp:2040:37: error: ‘class urdf::Joint’ has no member named ‘limits’ /home/pi/ros_catkin_ws/src/robot_model/collada_parser/src/collada_parser.cpp:2041:29: error: ‘class urdf::Joint’ has no member named ‘limits’ /home/pi/ros_catkin_ws/src/robot_model/collada_parser/src/collada_parser.cpp: In member function ‘boost::shared_ptr urdf::ColladaModelReader::_getJointFromRef(xsToken, daeElementRef)’: /home/pi/ros_catkin_ws/src/robot_model/collada_parser/src/collada_parser.cpp:2434:29: error: request for member ‘find’ in ‘((urdf::ColladaModelReader*)this)->urdf::ColladaModelReader::_model.boost::shared_ptr::operator->()->urdf::ModelInterface::joints_’, which is of non-class type ‘int’ /home/pi/ros_catkin_ws/src/robot_model/collada_parser/src/collada_parser.cpp:2434:59: error: request for member ‘end’ in ‘((urdf::ColladaModelReader*)this)->urdf::ColladaModelReader::_model.boost::shared_ptr::operator->()->urdf::ModelInterface::joints_’, which is of non-class type ‘int’ /home/pi/ros_catkin_ws/src/robot_model/collada_parser/src/collada_parser.cpp:2437:38: error: request for member ‘find’ in ‘((urdf::ColladaModelReader*)this)->urdf::ColladaModelReader::_model.boost::shared_ptr::operator->()->urdf::ModelInterface::joints_’, which is of non-class type ‘int’ CMakeFiles/collada_parser.dir/build.make:62: recipe for target 'CMakeFiles/collada_parser.dir/src/collada_parser.cpp.o' failed make[2]: *** [CMakeFiles/collada_parser.dir/src/collada_parser.cpp.o] Error 1 CMakeFiles/Makefile2:387: recipe for target 'CMakeFiles/collada_parser.dir/all' failed make[1]: *** [CMakeFiles/collada_parser.dir/all] Error 2 Makefile:138: recipe for target 'all' failed make: *** [all] Error 2 <== Failed to process package 'collada_parser': Command '['/opt/ros/indigo/env.sh', 'make', '-j4', '-l4']' returned non-zero exit status 2 Reproduce this error by running: ==> cd /home/pi/ros_catkin_ws/build_isolated/collada_parser && /opt/ros/indigo/env.sh make -j4 -l4 Command failed, exiting. Any help would be greatly appreciated.

git strategy for catkin and package folders

$
0
0
I am new to ROS and the catkin tool. I have read the tutorials and try to understand how to work with the ROS file structure and tools. Let's say my application will consist of home grown packages a,b and c. workspace_folder/ src/ CMakeLists.txt/ package_a/ package_b/ package_c/ 1. I could place these packages in separate git repositories, but I feel that would be inconvenient as the number grows and as many of them will be very application specific. 1. Should I place the src folder in git instead? What about the CMakeLists.txt file then? I guess that file is system specific. 1. Or do you recommend to make the full work space folder as repository and just make git ignore the build and devel folders? For each solution I am interested in the instructions that a new developer would need to checkout and build the application. For instance I am somewhat in doubt about what catkin (e.g. catkin init work space) does behind the scenes and how much of this should be in git. Thanks for any advice

Code::Blocks and ROS Setup - rospack export returns empty line

$
0
0
Hi all, I'm trying to integrate Code::Blocks with the [actionlib_tutorials](http://wiki.ros.org/actionlib_tutorials/Tutorials) package to no avail. I'm using the [ROS IDEs Wiki](http://wiki.ros.org/IDEs#CodeBlocks) page for Code::Blocks and I'm getting a blank line when using: > rospack export --lang=cpp --attrib=cflags PackageName > rospack export --lang=cpp --attrib=lflags PackageName I've created the package using catkin tools and have successfully run *catkin build* in the package root. My ROS_PACKAGE_PATH is: >/TigerBotWS/TigerBot/src/actionlib_tutorials:/opt/ros/kinetic/share And using tree on my package looks like the following: >> . ├── build >>│   ├── actionlib_tutorials >>│   └── catkin_tools_prebuild >>├── devel >>│   ├── etc >>│   ├── lib >>│   └── share >>├── logs >>└── src >>│   └── actionlib_tutorials Any idea as to why the cflags attribute from rospack export might be blank? Thanks in advance. (P.S. There was a previous topic about this [here](http://answers.ros.org/question/190307/code-blocks-and-catkin-indigo/). The tutorial is points to did not solve my issue hence the re-post)

error: opencv2/core/core.hpp No such file or directory

$
0
0
I am working with ROS kinetic on ubuntu 16.04 after a system update with Software-Updater i get an error while catkin_make-ing. worked like a charm before. In file included from /home/alexander/git/human_detector/catkin_ws/src/human_detector/src/background.cpp:3:0: /opt/ros/kinetic/include/cv_bridge/cv_bridge.h:43:33: fatal error: opencv2/core/core.hpp: Datei oder Verzeichnis nicht gefunden (No such file or directory) compilation terminated. get this for every file i included cv_bridge.... edit: i dont know if its important but i found the update history from that point in time when things stopped working Start-Date: 2017-03-23 14:29:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.153' Install: libappstream4:amd64 (0.10.6-1~ubuntu16.04.2, automatic), libstemmer0d:amd64 (0+svn585-1, automatic) Upgrade: ros-kinetic-interactive-markers:amd64 (1.11.3-0xenial-20170227-161835-0800, 1.11.3-0xenial-20170308-212223-0800), ros-kinetic-rqt-gui-py:amd64 (0.3.2-0xenial-20170227-152338-0800, 0.3.2-0xenial-20170308-221141-0800), ros-kinetic-opencv3:amd64 (3.2.0-2xenial-20170226-170515-0800, 3.2.0-4xenial-20170315-013656-0700), ros-kinetic-eigen-stl-containers:amd64 (0.1.6-0xenial-20170217-220112-0800, 0.1.8-0xenial-20170310-121851-0800), ros-kinetic-tf2-msgs:amd64 (0.5.15-0xenial-20170227-131925-0800, 0.5.15-0xenial-20170308-183301-0800), ros-kinetic-geometric-shapes:amd64 (0.5.2-0xenial-20170227-142025-0800, 0.5.2-0xenial-20170310-122242-0800), ros-kinetic-rospy:amd64 (1.12.7-0xenial-20170227-142222-0800, 1.12.7-0xenial-20170308-183940-0800), ros-kinetic-desktop:amd64 (1.3.0-0xenial-20170302-223605-0800, 1.3.0-0xenial-20170316-165147-0700), ros-kinetic-roslaunch:amd64 (1.12.7-0xenial-20170227-143335-0800, 1.12.7-0xenial-20170308-192730-0800), ros-kinetic-rqt-tf-tree:amd64 (0.5.6-0xenial-20170302-220927-0800, 0.5.6-0xenial-20170308-221819-0800), ros-kinetic-rqt-moveit:amd64 (0.5.6-0xenial-20170302-221012-0800, 0.5.6-0xenial-20170308-221859-0800), ros-kinetic-visualization-marker-tutorials:amd64 (0.10.1-0xenial-20170227-143139-0800, 0.10.1-0xenial-20170308-193413-0800), ros-kinetic-ros-base:amd64 (1.3.0-0xenial-20170227-160140-0800, 1.3.0-0xenial-20170308-211001-0800), ros-kinetic-roslisp:amd64 (1.9.20-0xenial-20170227-132204-0800, 1.9.20-0xenial-20170308-184833-0800), ros-kinetic-ros-comm:amd64 (1.12.7-0xenial-20170227-155832-0800, 1.12.7-0xenial-20170308-210535-0800), ros-kinetic-nodelet-topic-tools:amd64 (1.9.9-0xenial-20170227-155019-0800, 1.9.9-0xenial-20170308-195955-0800), ros-kinetic-ros-core:amd64 (1.3.0-0xenial-20170227-155952-0800, 1.3.0-0xenial-20170308-210730-0800), ros-kinetic-rqt-console:amd64 (0.4.7-0xenial-20170302-215342-0800, 0.4.7-0xenial-20170308-222005-0800), ros-kinetic-tf2-ros:amd64 (0.5.15-0xenial-20170227-160309-0800, 0.5.15-0xenial-20170308-210920-0800), ros-kinetic-rospy-tutorials:amd64 (0.7.1-0xenial-20170227-144304-0800, 0.7.1-0xenial-20170308-193605-0800), ros-kinetic-rqt-pose-view:amd64 (0.5.6-0xenial-20170302-221102-0800, 0.5.6-0xenial-20170308-221802-0800), ros-kinetic-diagnostic-common-diagnostics:amd64 (1.8.10-0xenial-20170227-163638-0800, 1.8.10-0xenial-20170308-214054-0800), ros-kinetic-rqt-logger-level:amd64 (0.4.7-0xenial-20170302-214359-0800, 0.4.7-0xenial-20170308-221845-0800), ros-kinetic-topic-tools:amd64 (1.12.7-0xenial-20170227-144325-0800, 1.12.7-0xenial-20170308-193558-0800), ros-kinetic-roslib:amd64 (1.13.5-0xenial-20170227-130826-0800, 1.13.5-0xenial-20170308-181854-0800), ros-kinetic-diagnostic-msgs:amd64 (1.12.5-0xenial-20170227-131424-0800, 1.12.5-0xenial-20170308-182759-0800), ros-kinetic-rosgraph-msgs:amd64 (1.11.2-0xenial-20170227-131933-0800, 1.11.2-0xenial-20170308-183114-0800), ros-kinetic-robot-model:amd64 (1.12.7-0xenial-20170227-163412-0800, 1.12.7-0xenial-20170310-123927-0800), ros-kinetic-roslz4:amd64 (1.12.7-0xenial-20170227-143629-0800, 1.12.7-0xenial-20170308-182349-0800), libc6-dbg:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7), appstream:amd64 (0.9.4-1ubuntu2, 0.10.6-1~ubuntu16.04.2), libc6-dev:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7), ros-kinetic-rosmsg:amd64 (1.12.7-0xenial-20170227-152432-0800, 1.12.7-0xenial-20170308-194441-0800), ros-kinetic-eigen-conversions:amd64 (1.11.8-0xenial-20170227-140332-0800, 1.11.8-0xenial-20170308-191208-0800), ros-kinetic-resource-retriever:amd64 (1.12.2-0xenial-20170227-141639-0800, 1.12.2-0xenial-20170308-184725-0800), ros-kinetic-rosservice:amd64 (1.12.7-0xenial-20170227-152738-0800, 1.12.7-0xenial-20170308-194759-0800), libwbclient0:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.3, 2:4.3.11+dfsg-0ubuntu0.16.04.5), ros-kinetic-joint-state-publisher:amd64 (1.12.7-0xenial-20170227-143026-0800, 1.12.7-0xenial-20170308-192419-0800), ros-kinetic-ros:amd64 (1.13.5-0xenial-20170227-140935-0800, 1.13.5-0xenial-20170308-190952-0800), ros-kinetic-kdl-parser:amd64 (1.12.7-0xenial-20170227-144926-0800, 1.12.7-0xenial-20170308-194201-0800), ros-kinetic-control-msgs:amd64 (1.4.0-0xenial-20170227-133229-0800, 1.4.0-0xenial-20170308-183651-0800), ros-kinetic-rviz-plugin-tutorials:amd64 (0.10.1-0xenial-20170227-203301-0800, 0.10.1-0xenial-20170309-010413-0800), ros-kinetic-bond:amd64 (1.7.18-0xenial-20170227-131410-0800, 1.7.18-0xenial-20170308-182743-0800), ros-kinetic-rosout:amd64 (1.12.7-0xenial-20170227-142920-0800, 1.12.7-0xenial-20170308-192416-0800), ros-kinetic-bondcpp:amd64 (1.7.18-0xenial-20170227-142154-0800, 1.7.18-0xenial-20170308-191846-0800), ros-kinetic-tf2:amd64 (0.5.15-0xenial-20170227-141723-0800, 0.5.15-0xenial-20170308-192216-0800), ros-kinetic-trajectory-msgs:amd64 (1.12.5-0xenial-20170227-132341-0800, 1.12.5-0xenial-20170308-183509-0800), ros-kinetic-rqt-py-common:amd64 (0.4.7-0xenial-20170302-214959-0800, 0.4.7-0xenial-20170308-210625-0800), ros-kinetic-geometry:amd64 (1.11.8-0xenial-20170227-163348-0800, 1.11.8-0xenial-20170308-214546-0800), ros-kinetic-turtle-actionlib:amd64 (0.1.10-0xenial-20170227-160128-0800, 0.1.10-0xenial-20170308-210711-0800), ros-kinetic-rqt-rviz:amd64 (0.5.6-0xenial-20170227-170212-0800, 0.5.6-0xenial-20170308-221154-0800), ros-kinetic-ros-tutorials:amd64 (0.7.1-0xenial-20170227-151242-0800, 0.7.1-0xenial-20170308-193952-0800), ros-kinetic-pr2-description:amd64 (1.12.0-0xenial-20170227-203136-0800, 1.12.0-0xenial-20170309-003548-0800), ros-kinetic-tf-conversions:amd64 (1.11.8-0xenial-20170227-161512-0800, 1.11.8-0xenial-20170308-213602-0800), ros-kinetic-viz:amd64 (1.3.0-0xenial-20170302-222252-0800, 1.3.0-0xenial-20170315-050401-0700), ros-kinetic-nav-msgs:amd64 (1.12.5-0xenial-20170227-131914-0800, 1.12.5-0xenial-20170308-183252-0800), ros-kinetic-stereo-msgs:amd64 (1.12.5-0xenial-20170227-132512-0800, 1.12.5-0xenial-20170308-184013-0800), ros-kinetic-pluginlib-tutorials:amd64 (0.1.10-0xenial-20170227-144849-0800, 0.1.10-0xenial-20170308-193419-0800), ros-kinetic-collada-parser:amd64 (1.12.7-0xenial-20170227-145024-0800, 1.12.7-0xenial-20170308-194222-0800), ros-kinetic-common-tutorials:amd64 (0.1.10-0xenial-20170227-161423-0800, 0.1.10-0xenial-20170308-214804-0800), ros-kinetic-visualization-msgs:amd64 (1.12.5-0xenial-20170227-132221-0800, 1.12.5-0xenial-20170308-183526-0800), ros-kinetic-rqt-service-caller:amd64 (0.4.7-0xenial-20170302-215600-0800, 0.4.7-0xenial-20170308-223053-0800), libc6:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7), ros-kinetic-bond-core:amd64 (1.7.18-0xenial-20170227-143123-0800, 1.7.18-0xenial-20170308-192230-0800), ros-kinetic-nodelet:amd64 (1.9.9-0xenial-20170227-142544-0800, 1.9.9-0xenial-20170308-192127-0800), ros-kinetic-rosbuild:amd64 (1.13.5-0xenial-20170227-130940-0800, 1.13.5-0xenial-20170308-182204-0800), ros-kinetic-collada-urdf:amd64 (1.12.7-0xenial-20170227-161415-0800, 1.12.7-0xenial-20170310-123104-0800), locales:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7), ros-kinetic-qt-dotgraph:amd64 (0.3.4-0xenial-20170227-144131-0800, 0.3.4-0xenial-20170308-200807-0800), ros-kinetic-roswtf:amd64 (1.12.7-0xenial-20170227-155539-0800, 1.12.7-0xenial-20170308-210221-0800), ros-kinetic-rqt-topic:amd64 (0.4.7-0xenial-20170302-214823-0800, 0.4.7-0xenial-20170308-221728-0800), ros-kinetic-librviz-tutorial:amd64 (0.10.1-0xenial-20170227-170217-0800, 0.10.1-0xenial-20170308-220506-0800), ros-kinetic-rqt-bag:amd64 (0.4.7-0xenial-20170302-214220-0800, 0.4.7-0xenial-20170308-221724-0800), ros-kinetic-urdf-tutorial:amd64 (0.2.4-0xenial-20170227-203605-0800, 0.2.4-0xenial-20170309-004251-0800), ros-kinetic-map-msgs:amd64 (1.13.0-0xenial-20170227-132427-0800, 1.13.0-0xenial-20170308-183714-0800), ros-kinetic-rqt-common-plugins:amd64 (0.4.7-0xenial-20170302-220038-0800, 0.4.7-0xenial-20170315-042717-0700), ros-kinetic-smach-ros:amd64 (2.0.0-2xenial-20170227-160322-0800, 2.0.0-2xenial-20170308-210823-0800), ros-kinetic-diagnostic-analysis:amd64 (1.8.10-0xenial-20170227-152428-0800, 1.8.10-0xenial-20170308-194629-0800), ros-kinetic-rosbag-storage:amd64 (1.12.7-0xenial-20170227-151648-0800, 1.12.7-0xenial-20170308-191526-0800), ros-kinetic-rqt-dep:amd64 (0.4.7-0xenial-20170302-214625-0800, 0.4.7-0xenial-20170308-222101-0800), ros-kinetic-rqt-robot-steering:amd64 (0.5.6-0xenial-20170227-152857-0800, 0.5.6-0xenial-20170308-221740-0800), ros-kinetic-rqt-reconfigure:amd64 (0.4.7-0xenial-20170302-215527-0800, 0.4.7-0xenial-20170308-222128-0800), ros-kinetic-turtlesim:amd64 (0.7.1-0xenial-20170227-142249-0800, 0.7.1-0xenial-20170308-184307-0800), ros-kinetic-pluginlib:amd64 (1.10.4-0xenial-20170227-141336-0800, 1.10.4-0xenial-20170308-184727-0800), samba-libs:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.3, 2:4.3.11+dfsg-0ubuntu0.16.04.5), ros-kinetic-rqt-gui:amd64 (0.3.2-0xenial-20170227-151914-0800, 0.3.2-0xenial-20170308-220648-0800), ros-kinetic-genpy:amd64 (0.6.4-0xenial-20170227-125221-0800, 0.6.5-0xenial-20170308-181016-0800), ros-kinetic-gencpp:amd64 (0.5.4-0xenial-20170217-220520-0800, 0.5.5-0xenial-20170308-180846-0800), ros-kinetic-diagnostics:amd64 (1.8.10-0xenial-20170227-164039-0800, 1.8.10-0xenial-20170308-215424-0800), ros-kinetic-python-qt-binding:amd64 (0.3.2-0xenial-20170227-140247-0800, 0.3.2-0xenial-20170308-185848-0800), libc-bin:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7), ros-kinetic-rviz-python-tutorial:amd64 (0.10.1-0xenial-20170227-203325-0800, 0.10.1-0xenial-20170309-010454-0800), ros-kinetic-diagnostic-aggregator:amd64 (1.8.10-0xenial-20170227-144422-0800, 1.8.10-0xenial-20170308-193714-0800), ros-kinetic-qt-gui-cpp:amd64 (0.3.4-0xenial-20170227-144634-0800, 0.3.4-0xenial-20170308-201126-0800), ros-kinetic-nodelet-tutorial-math:amd64 (0.1.10-0xenial-20170227-143008-0800, 0.1.10-0xenial-20170308-192533-0800), ros-kinetic-robot-state-publisher:amd64 (1.13.4-0xenial-20170227-163055-0800, 1.13.4-0xenial-20170308-213249-0800), ros-kinetic-message-filters:amd64 (1.12.7-0xenial-20170227-144623-0800, 1.12.7-0xenial-20170308-193633-0800), ros-kinetic-mk:amd64 (1.13.5-0xenial-20170227-140241-0800, 1.13.5-0xenial-20170308-185836-0800), ros-kinetic-geometry-tutorials:amd64 (0.2.2-0xenial-20170227-201846-0800, 0.2.2-0xenial-20170309-004442-0800), ros-kinetic-tf:amd64 (1.11.8-0xenial-20170227-160826-0800, 1.11.8-0xenial-20170308-211336-0800), ros-kinetic-message-runtime:amd64 (0.4.12-0xenial-20170227-125728-0800, 0.4.12-0xenial-20170308-181648-0800), ros-kinetic-rosunit:amd64 (1.13.5-0xenial-20170227-140141-0800, 1.13.5-0xenial-20170308-182205-0800), ros-kinetic-rqt-robot-monitor:amd64 (0.5.6-0xenial-20170302-220922-0800, 0.5.6-0xenial-20170308-221854-0800), ros-kinetic-actionlib-tutorials:amd64 (0.1.10-0xenial-20170227-160053-0800, 0.1.10-0xenial-20170308-210743-0800), ros-kinetic-sensor-msgs:amd64 (1.12.5-0xenial-20170227-132053-0800, 1.12.5-0xenial-20170308-183152-0800), ros-kinetic-rqt-plot:amd64 (0.4.7-0xenial-20170302-215403-0800, 0.4.7-0xenial-20170308-221732-0800), ros-kinetic-executive-smach:amd64 (2.0.0-2xenial-20170227-160504-0800, 2.0.0-2xenial-20170308-211014-0800), ros-kinetic-rosnode:amd64 (1.12.7-0xenial-20170227-155211-0800, 1.12.7-0xenial-20170308-205752-0800), ros-kinetic-interactive-marker-tutorials:amd64 (0.10.1-0xenial-20170227-163213-0800, 0.10.1-0xenial-20170308-213733-0800), ros-kinetic-xacro:amd64 (1.11.2-0xenial-20170227-202651-0800, 1.11.2-0xenial-20170308-205557-0800), ros-kinetic-rqt-msg:amd64 (0.4.7-0xenial-20170302-215655-0800, 0.4.7-0xenial-20170308-222109-0800), ros-kinetic-rqt-nav-view:amd64 (0.5.6-0xenial-20170302-221108-0800, 0.5.6-0xenial-20170308-221855-0800), ros-kinetic-turtle-tf2:amd64 (0.2.2-0xenial-20170227-160838-0800, 0.2.2-0xenial-20170308-211349-0800), ros-kinetic-robot:amd64 (1.3.0-0xenial-20170227-203125-0800, 1.3.0-0xenial-20170316-162847-0700), ros-kinetic-rqt-shell:amd64 (0.4.7-0xenial-20170302-214957-0800, 0.4.7-0xenial-20170308-222127-0800), ros-kinetic-rostest:amd64 (1.12.7-0xenial-20170227-143945-0800, 1.12.7-0xenial-20170308-193235-0800), ros-kinetic-std-msgs:amd64 (0.5.11-0xenial-20170227-131008-0800, 0.5.11-0xenial-20170308-182154-0800), ros-kinetic-rqt-gui-cpp:amd64 (0.3.2-0xenial-20170227-150837-0800, 0.3.2-0xenial-20170308-201916-0800), ros-kinetic-geometry-msgs:amd64 (1.12.5-0xenial-20170227-131438-0800, 1.12.5-0xenial-20170308-182846-0800), ros-kinetic-rqt-image-view:amd64 (0.4.7-0xenial-20170302-214513-0800, 0.4.7-0xenial-20170315-031747-0700), ros-kinetic-qt-gui:amd64 (0.3.4-0xenial-20170227-144119-0800, 0.3.4-0xenial-20170308-200814-0800), libsmbclient:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.3, 2:4.3.11+dfsg-0ubuntu0.16.04.5), ros-kinetic-rosconsole:amd64 (1.12.7-0xenial-20170227-140945-0800, 1.12.7-0xenial-20170308-182447-0800), ros-kinetic-rosconsole-bridge:amd64 (0.4.4-0xenial-20170227-144251-0800, 0.4.4-0xenial-20170308-191658-0800), ros-kinetic-rviz:amd64 (1.12.4-0xenial-20170227-162335-0800, 1.12.4-0xenial-20170308-212658-0800), ros-kinetic-rqt-runtime-monitor:amd64 (0.5.6-0xenial-20170227-152853-0800, 0.5.6-0xenial-20170308-221732-0800), ros-kinetic-nodelet-core:amd64 (1.9.9-0xenial-20170227-155431-0800, 1.9.9-0xenial-20170308-201828-0800), ros-kinetic-cv-bridge:amd64 (1.12.4-0xenial-20170227-144540-0800, 1.12.4-0xenial-20170315-022155-0700), ros-kinetic-rospack:amd64 (2.3.2-0xenial-20170227-125456-0800, 2.3.3-0xenial-20170308-181000-0800), ros-kinetic-roscpp-tutorials:amd64 (0.7.1-0xenial-20170227-142305-0800, 0.7.1-0xenial-20170308-184203-0800), ros-kinetic-smach-msgs:amd64 (2.0.0-2xenial-20170227-132245-0800, 2.0.0-2xenial-20170308-184416-0800), ros-kinetic-rqt-srv:amd64 (0.4.7-0xenial-20170302-215828-0800, 0.4.7-0xenial-20170308-222551-0800), libc-dev-bin:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7), ros-kinetic-urdf:amd64 (1.12.7-0xenial-20170227-144630-0800, 1.12.7-0xenial-20170308-193748-0800), ros-kinetic-rqt-top:amd64 (0.4.7-0xenial-20170302-214750-0800, 0.4.7-0xenial-20170308-221921-0800), ros-kinetic-shape-msgs:amd64 (1.12.5-0xenial-20170227-132058-0800, 1.12.5-0xenial-20170308-183503-0800), multiarch-support:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7), ros-kinetic-rqt-publisher:amd64 (0.4.7-0xenial-20170302-215515-0800, 0.4.7-0xenial-20170308-221658-0800), ros-kinetic-filters:amd64 (1.7.4-1xenial-20170227-144350-0800, 1.7.5-0xenial-20170316-161632-0700), ros-kinetic-bondpy:amd64 (1.7.18-0xenial-20170227-142734-0800, 1.7.18-0xenial-20170308-191818-0800), ros-kinetic-rqt-bag-plugins:amd64 (0.4.7-0xenial-20170302-215443-0800, 0.4.7-0xenial-20170308-221929-0800), ros-kinetic-message-generation:amd64 (0.4.0-0xenial-20170227-125711-0800, 0.4.0-0xenial-20170308-181930-0800), ros-kinetic-self-test:amd64 (1.8.10-0xenial-20170227-144914-0800, 1.8.10-0xenial-20170308-194158-0800), ros-kinetic-rqt-robot-dashboard:amd64 (0.5.6-0xenial-20170302-221346-0800, 0.5.6-0xenial-20170308-222215-0800), ros-kinetic-rqt-web:amd64 (0.4.7-0xenial-20170302-214856-0800, 0.4.7-0xenial-20170308-222020-0800), ros-kinetic-image-transport:amd64 (1.11.12-0xenial-20170227-145007-0800, 1.11.12-0xenial-20170308-193939-0800), ros-kinetic-common-msgs:amd64 (1.12.5-0xenial-20170227-141659-0800, 1.12.5-0xenial-20170308-191814-0800), ros-kinetic-dynamic-reconfigure:amd64 (1.5.46-0xenial-20170227-152924-0800, 1.5.46-0xenial-20170308-195045-0800), ros-kinetic-actionlib-msgs:amd64 (1.12.5-0xenial-20170227-131404-0800, 1.12.5-0xenial-20170308-182735-0800), ros-kinetic-rqt-launch:amd64 (0.4.7-0xenial-20170302-215518-0800, 0.4.7-0xenial-20170308-222146-0800), ros-kinetic-rqt-robot-plugins:amd64 (0.5.6-0xenial-20170302-222158-0800, 0.5.6-0xenial-20170309-014549-0800), ros-kinetic-visualization-tutorials:amd64 (0.10.1-0xenial-20170227-203916-0800, 0.10.1-0xenial-20170309-013808-0800), ros-kinetic-rostopic:amd64 (1.12.7-0xenial-20170227-152427-0800, 1.12.7-0xenial-20170308-194406-0800), ros-kinetic-kdl-conversions:amd64 (1.11.8-0xenial-20170227-141855-0800, 1.11.8-0xenial-20170308-192335-0800), ros-kinetic-rqt-py-console:amd64 (0.4.7-0xenial-20170302-214937-0800, 0.4.7-0xenial-20170308-221851-0800), ros-kinetic-rosbag:amd64 (1.12.7-0xenial-20170227-152113-0800, 1.12.7-0xenial-20170308-194018-0800), ros-kinetic-qt-gui-py-common:amd64 (0.3.4-0xenial-20170227-144114-0800, 0.3.4-0xenial-20170308-200834-0800), ros-kinetic-rqt-graph:amd64 (0.4.7-0xenial-20170302-214543-0800, 0.4.7-0xenial-20170308-221654-0800), ros-kinetic-diagnostic-updater:amd64 (1.8.10-0xenial-20170227-144402-0800, 1.8.10-0xenial-20170308-193704-0800), ros-kinetic-tf2-kdl:amd64 (0.5.15-0xenial-20170227-160816-0800, 0.5.15-0xenial-20170308-211829-0800), ros-kinetic-roscpp:amd64 (1.12.7-0xenial-20170227-141340-0800, 1.12.7-0xenial-20170308-183157-0800), ros-kinetic-actionlib:amd64 (1.11.8-0xenial-20170227-155556-0800, 1.11.8-0xenial-20170308-210216-0800), ros-kinetic-std-srvs:amd64 (1.11.2-0xenial-20170227-131132-0800, 1.11.2-0xenial-20170308-182013-0800), ros-kinetic-turtle-tf:amd64 (0.2.2-0xenial-20170227-162241-0800, 0.2.2-0xenial-20170308-212918-0800), ros-kinetic-laser-geometry:amd64 (1.6.4-0xenial-20170227-161515-0800, 1.6.4-0xenial-20170308-212122-0800), ros-kinetic-rqt-action:amd64 (0.4.7-0xenial-20170302-215758-0800, 0.4.7-0xenial-20170308-222551-0800), ros-kinetic-tf2-py:amd64 (0.5.15-0xenial-20170227-145116-0800, 0.5.15-0xenial-20170308-193928-0800) End-Date: 2017-03-23 14:30:15

Navigation stack runs slow when installed from source

$
0
0
I need to modify the `costmap_2d` source code for my project. I downloaded the latest navigation stack source from github (v1.12.13 as of today). I copied the source code (all the navigation packages) into my workspace and compiled it by executing `catkin_make -DCMAKE_BUILD_TYPE=Release`. However, when I give a goal to robot it gives me warnings `Map loop missed its desired rate of ...`, and robot's movement is very slow and unstable. (I do not get any warnings before giving the goal). The performance of navigation stack in general became very slow after I installed it from source. I do not get any warning and the robot moves smoothly if I remove the navigation packages from my catkin workspace and use the packages that came with ros installation (which are also v1.12.13). One difference between source compiled executables and the original executables (one that came with ros installation) is as follow. `file` command gives different output: Source installed executables: `ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=ea5a688fc0b62bec71a5a6e7ac53c4a7bb209916, not stripped` Original executables (ones that come with ros installation): `ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=138405beffc40400b5633927fa54e64062834c63, stripped` Also, source compiled executables have bigger size than the corresponding original executables. I am using ros indigo with ubuntu 14.04. Let me know if you need more information.

How can I config the network to install ROS in my VM?

$
0
0
am doing:> $wget http://packages.ros.org/ros.key -O - | sudo apt-key add - and I get : > --2017-03-29 15:38:00-- (try: 2) http://packages.ros.org/ros.key> Connecting to packages.ros.org> (packages.ros.org)|64.50.236.52|:80...> connected. HTTP request sent, awaiting> response... Read error (Connection> reset by peer) in headers.

Failing to install cv_bridge

$
0
0
Hey, I keep failing to install cv_bridge on my raspberry pi. I have tried everything, but can't figure out what I did wrong. - Git source: [https://github.com/ros-perception/vision_opencv](https://github.com/ros-perception/vision_opencv) - Commando to clone: $git clone -b kinetic https://github.com/ros-perception/vision_opencv - openCV version: 2.4.9 - error message: `/home/pi/ros_ws/src/vision_opencv/cv_bridge/src/module_opencv2.cpp:124:16: error: cannot declare variable ‘g_numpyAllocator’ to be of abstract type ‘NumpyAllocator’ NumpyAllocator g_numpyAllocator; ^ /home/pi/ros_ws/src/vision_opencv/cv_bridge/src/module_opencv2.cpp:71:7: note: because the following virtual functions are pure within ‘NumpyAllocator’: class NumpyAllocator : public cv::MatAllocator ^ In file included from /usr/include/opencv2/core.hpp:59:0, from /usr/include/opencv2/core/core.hpp:48, from /home/pi/ros_ws/src/vision_opencv/cv_bridge/include/cv_bridge/cv_bridge.h:43, from /home/pi/ros_ws/src/vision_opencv/cv_bridge/src/module.hpp:22, from /home/pi/ros_ws/src/vision_opencv/cv_bridge/src/module_opencv2.cpp:35: /usr/include/opencv2/core/mat.hpp:409:23: note: virtual cv::UMatData* cv::MatAllocator::allocate(int, const int*, int, void*, size_t*, int, cv::UMatUsageFlags) const virtual UMatData* allocate(int dims, const int* sizes, int type, ^ /usr/include/opencv2/core/mat.hpp:411:18: note: virtual bool cv::MatAllocator::allocate(cv::UMatData*, int, cv::UMatUsageFlags) const virtual bool allocate(UMatData* data, int accessflags, UMatUsageFlags usageFlags) const = 0; ^ /usr/include/opencv2/core/mat.hpp:412:18: note: virtual void cv::MatAllocator::deallocate(cv::UMatData*) const virtual void deallocate(UMatData* data) const = 0; ^ /home/pi/ros_ws/src/vision_opencv/cv_bridge/src/module_opencv2.cpp: In function ‘int convert_to_CvMat2(const PyObject*, cv::Mat&)’: /home/pi/ros_ws/src/vision_opencv/cv_bridge/src/module_opencv2.cpp:206:11: error: ‘class cv::Mat’ has no member named ‘refcount’ m.refcount = refcountFromPyObject(o); ^ vision_opencv/cv_bridge/src/CMakeFiles/cv_bridge_boost.dir/build.make:77: recipe for target 'vision_opencv/cv_bridge/src/CMakeFiles/cv_bridge_boost.dir/module_opencv2.cpp.o' failed make[2]: *** [vision_opencv/cv_bridge/src/CMakeFiles/cv_bridge_boost.dir/module_opencv2.cpp.o] Error 1 CMakeFiles/Makefile2:10272: recipe for target 'vision_opencv/cv_bridge/src/CMakeFiles/cv_bridge_boost.dir/all' failed make[1]: *** [vision_opencv/cv_bridge/src/CMakeFiles/cv_bridge_boost.dir/all] Error 2 Makefile:127: recipe for target 'all' failed make: *** [all] Error 2 `

Why autocomplete not always working

$
0
0
sometimes it works sometimes not... i am learning how to create a package using ROS tools, autocomplete is one of the most gentle features... but sometimes I do: > rosclient@rosclient-VirtualBox:~/catkin_ws$ rosrun bos looking for a autocomplete in my new package name bosca but not always working.. why?

sudo apt install catkin not working.

$
0
0
Hi, I'm a newbie, so sorry if this is really obvious. I'm following the Tutorials instructions having just installed ROS on Ubuntu Mate. The current step says > $ cd ~/catkin_ws/> $ catkin_make but when I enter "catkin_make" terminal returns > The program 'catkin_make' is currently not installed. You can install it by typing:> sudo apt install catkin So I do that, and get > Reading package lists... Done> Building dependency tree> Reading state information... Done> Some packages could not be installed. This may mean that you have> requested an impossible situation or if you are using the unstable> distribution that some required packages have not yet been created> or been moved out of Incoming.> The following information may help resolve the situation:>> The following packages have unmet dependencies:> catkin : Depends: python-catkin-pkg but it is not going to be installed> E: Unable to correct problems, you have held broken packages. It then ends at that. How can I fix this and continue with the tutorials?

rplidar_ros step by step for get map

$
0
0
Hello, I have a simple question ... i want to get map from RPLidar laser scan but i get confused in google and for now i don't know how i can implement that i install ros using below **command** sudo apt-get install ros-indigo-desktop-full and then run below command for define ros directory and commands for ubuntu(14.04) and it's ok(before that commands not define in terminal such as roscd,roscore,...) source /opt/ros/indigo/setup.bash after this step i clone(donwload) ros_rplidar from this web page [ https://github.com/robopeak/rplidar_ros ] , in this page robopeak prepare a tutorial of **How to build rplidar ros package** but i don't know what is catkin's workspace and why catkin_make don't work for me ? is there any good tutorial about this in step by step because i can't find that.

catkin_package(INCLUDE_DIRS include) vs. include_directories(include)

$
0
0
Hi, What does the `catkin_package` call do when you specify `include` as an `INCLUDE_DIRS` and is that the same as specifying `include` inside of `include_directories`? There is a short explanation on the template CMakeLists.txt file but it doesn't mention anything about the two above methods being the same effectively (if at all they are)? If they are not the same then what is the purpose of each individual one. Thank you.

Unwanted prefix getting added to CMAKE_PREFIX_PATH

$
0
0
Hi, I am using ROS Indigo. The problem is very simple. I unset the `CMAKE_PREFIX_PATH` variable. I `source /devel/setup.bash`. I get an unwanted prefix `/home//devel` added to my `CMAKE_PREFIX_PATH.` echo $CMAKE_PREFIX_PATH /home//devel:/home//catkin_ws/devel:/opt/ros/indigo I didn't do any changes to `devel/setup.bash` or `devel/setup.sh`. What could be the cause? and How to avoid it? Thank you.

Problem debugging ROS nodes on Mac OS X

$
0
0
Hello Community, I am on Mac OS X 10.11.4, ROS Jade and have some strange problems debugging ROS nodes with gdb or lldb. Namely, debugger is not able to locate ROS related shared libraries. Here is gdb output for example: Starting program: /Users/plistov/EPFL/ROS/ros_catkin_ws/devel_isolated/test_package/lib/test_package/ekf_node dyld: Library not loaded: libtf2_ros.dylib Referenced from: /Users/plistov/EPFL/ROS/ros_catkin_ws/devel_isolated/test_package/lib/test_package/ekf_node Reason: image not found Program received signal SIGTRAP, Trace/breakpoint trap. 0x00007fff5fc01075 in ?? () While DYLD_LIBRARY_PATH points to the folder containing this lib. Furthermore, I did not manage to launch standard ROS nodes. Rosbag for instance: (gdb) exec-file rosbag "/Users/plistov/EPFL/ROS/ros_catkin_ws/install/bin/rosbag": not in executable format: File format not recognised I have not experienced any problems debugging non-ROS related applications on my computer before. I, therefore, will very appreciate any hint or advice. Thanks, Peter
Viewing all 670 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>