Ask Your Question

damjan's profile - activity

2019-06-24 13:02:47 -0500 commented answer AMCL: No laser scan received

Glad to have helped! :) That LaserScan timeout error is actually quite misleading.

2019-06-23 15:08:43 -0500 edited answer AMCL: No laser scan received

Your _odom_frame parameter should actually be _odom_frame_id and you are missing the _base_frame_id parameter, i.e., i t

2019-06-23 15:08:01 -0500 edited answer AMCL: No laser scan received

Your _odom_frame parameter should actually be _odom_frame_id and you are missing the _base_frame_id parameter, i.e., i t

2019-06-23 15:07:11 -0500 answered a question AMCL: No laser scan received

Your _odom_frame parameter should actually be _odom_frame_id and you are missing the base_frame_id parameter, i.e., i th

2019-06-19 02:08:47 -0500 commented question AMCL: No laser scan received

Could you post the output of rosnode info /amcl, rostopic info /amazon_warehouse_robot/laser/scan and rostopic info /ama

2019-06-18 15:15:36 -0500 commented question AMCL: No laser scan received

Could you post the output of rosnode info /amcl, rostopic info /amazon_warehouse_robot/laser/scan and rostopic info /ama

2019-06-18 14:08:09 -0500 commented question AMCL: No laser scan received

Could you post the output of rosnode info /amcl, rostopic info /amazon_warehouse_robot/laser/scan and /amazon_warehouse_

2018-12-16 10:26:08 -0500 received badge  Notable Question (source)
2018-12-16 10:26:08 -0500 received badge  Famous Question (source)
2018-10-28 05:56:23 -0500 commented answer ROS driver for SICK NAV350?

We are not using the NAV with ARM SBCs, so I can't provide any specific information at the moment. I suggest you open a

2017-11-09 12:49:08 -0500 received badge  Nice Answer (source)
2017-07-11 08:45:43 -0500 commented answer Is there a procedure for removing obsolete documentation?

I'm unable to delete the page (can't see a "Delete" button and deleting all content and saving is disabled). Should I op

2017-07-11 08:40:13 -0500 commented answer Is there a procedure for removing obsolete documentation?

Should I open up a thread on discourse.ros.org to discuss this further? I think a documented wiki page removal procedure

2017-07-11 08:38:45 -0500 commented answer Is there a procedure for removing obsolete documentation?

Should I open up a thread on discourse.ros.org to discuss this further, I think a documented wiki page removal procedure

2017-07-11 08:38:31 -0500 commented answer Is there a procedure for removing obsolete documentation?

Should I open up a thread on discourse.ros.org to discuss this further, I think a documented wiki page removal procedure

2017-07-11 08:37:46 -0500 commented answer Is there a procedure for removing obsolete documentation?

I I'll open up a thread on discourse.ros.org to discuss this further, I think a documented wiki page removal procedure i

2017-07-11 08:33:50 -0500 commented answer Is there a procedure for removing obsolete documentation?

I've reviewed all three pages and I still feel the one I mention is obsolete. However, I have another concern now, which

2017-07-11 05:11:09 -0500 received badge  Popular Question (source)
2017-07-10 03:36:27 -0500 commented answer Is there a procedure for removing obsolete documentation?

I'm actually be in favor of removing it completely, as I think it duplicates information better presented here and here

2017-07-09 10:15:34 -0500 asked a question Is there a procedure for removing obsolete documentation?

Is there a procedure for removing obsolete documentation? As a specific example, this tutorial is heavily outdated (stil

2017-06-30 06:10:01 -0500 received badge  Necromancer (source)
2017-05-19 02:40:08 -0500 commented question rqt segmentation fault following tutorials

@juakofz If you feel like my answer below (based on the comment from @CIRobotics) solves the issue, can you please accep

2017-04-16 17:05:38 -0500 answered a question rqt segmentation fault following tutorials

Had this same issue, and the fix proposed by @CIRobotics in comments worked for me too. I'll just elaborate on the exact steps I took to resolve it.

The issue is caused by newer versions of packages (python-pyqt5 and python-sip) installed by the Cura PPA. The following steps solved the issue for me:

  1. Uninstall the newer package versions that were installed from the PPA:

    sudo apt remove python-pyqt5 pyton3-pyqt5 python-sip python3-sip sip-dev

  2. Remove the PPA:

    sudo rm /etc/apt/sources.list.d/thopiekar-ubuntu-cura-xenial.list sudo apt update

  3. Reinstall ros-kinetic-desktop-full

    sudo apt install ros-kinetic-desktop-full

  4. Check with sudo apt autoremove for any other packages that were broken by the downgrade and install or autoremove them as necessary.

A more elegant solution might be to use the ppa-purge tool as described here, however, I discovered that link after I had already fixed the issue, so I could not try it out.

Of course, the drawback of the above solution is that you will not be able to use the Cura software on your Xenial system. I'm dual-booting Windows, so I'll just install the Windows version. I'm currently not aware of a more elegant solution.

2017-04-11 15:09:19 -0500 commented question rqt Plugins segfault

Seems related to this question

2015-09-24 03:13:23 -0500 received badge  Great Answer (source)
2015-09-24 03:13:23 -0500 received badge  Guru (source)
2015-09-22 12:53:32 -0500 received badge  Famous Question (source)
2015-09-22 09:19:12 -0500 answered a question Build error in orocos_kdl when building Indigo from source on Debian 8.0 (Jessie)

Turns out, the problem was a previous installation of Eigen (probably from source), which wasn't cleaned up correctly. There was an invalid /usr/share/cmake/Eigen-3.0.1/eigen-config.cmake file which was setting Eigen_INCLUDE_DIRS instead of Eigen_INCLUDE_DIR (which orocos_kdl was expecting). The result was that the include flag for Eigen was set to -I instead of -I/usr/include/eigen3. Unfortunately the first error message led me way off the right trail.

2015-07-27 14:11:34 -0500 received badge  Notable Question (source)
2015-06-03 00:44:43 -0500 answered a question collada-dom-dev installation problem on raspberry pi while installing ROS indigo

Does

sudo apt-get install libboost-filesystem-dev libxml2-dev

solve the problem?

2015-06-02 12:05:39 -0500 commented question Build error in orocos_kdl when building Indigo from source on Debian 8.0 (Jessie)

Neither distcc nor ccache are installed on the Debian machine.

2015-06-02 12:05:04 -0500 commented question Build error in orocos_kdl when building Indigo from source on Debian 8.0 (Jessie)

Ubuntu 12.04 is using gcc 4.6, Ubuntu 14.04 is using gcc 4.8 and Debian Jessie is using 4.9. I can build orocos_kdl on both Ubuntu versions without problems, but the build fails on Debian. I have also installed gcc 4.8 on Debian and tried building with that, but I get the same error.

2015-06-01 19:56:31 -0500 received badge  Popular Question (source)
2015-06-01 16:32:30 -0500 commented question Build error in orocos_kdl when building Indigo from source on Debian 8.0 (Jessie)

I would say no, unless they are turned on automatically by CMake/catkin, because I haven't turned them on manually, but I'll check tomorrow when I get back to work. Thanks for helping me out with this!

2015-06-01 04:38:24 -0500 commented question Build error in orocos_kdl when building Indigo from source on Debian 8.0 (Jessie)

The disk is only 30% used, the directory is created. Also, CMake version doesn't seem to be the issue. I have tried CMake 2.8.9 and 3.0.2, both work on Ubuntu Precise, none work on Debian Jessie. The one difference I notice is that the file build order is different on the two systems. I'm stumped

2015-06-01 04:38:24 -0500 received badge  Commentator
2015-05-31 19:11:04 -0500 asked a question Build error in orocos_kdl when building Indigo from source on Debian 8.0 (Jessie)

I am trying to build ROS Indigo from source on Debian Jessie, following these instructions. So far, I have successfully built the ros_comm variant and can run roscore. I'm now trying to build the robot variant. 20 of 116 packages get built successfully, but the build fails when it gets to 'orocos_kdl'. Here is the full error output:

==> Processing plain cmake package: 'orocos_kdl'
==> Creating build directory: 'build_isolated/orocos_kdl/install'
==> Building with env: '/opt/ros/indigo/env.sh'
==> cmake /home/larics/ros_catkin_ws/src/orocos_kinematics_dynamics/orocos_kdl -DCMAKE_INSTALL_PREFIX=/opt/ros/indigo -DCMAKE_BUILD_TYPE=Release -G Unix Makefiles in '/home/larics/ros_catkin_ws/build_isolated/orocos_kdl/install'
-- The C compiler identification is GNU 4.9.2
-- The CXX compiler identification is GNU 4.9.2
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
Orocos KDL version  (1.3.0)
Build type set to 'Release' by user.
-- Eigen found (include: /usr/include/eigen3)
-- Performing Test HAVE_STL_CONTAINER_INCOMPLETE_TYPES
-- Performing Test HAVE_STL_CONTAINER_INCOMPLETE_TYPES - Success
-- Configuring done
-- Generating done
-- Build files have been written to: /home/larics/ros_catkin_ws/build_isolated/orocos_kdl/install
==> make -j2 -l2 in '/home/larics/ros_catkin_ws/build_isolated/orocos_kdl/install'
Scanning dependencies of target orocos-kdl
[  3%] [  3%] Building CXX object src/CMakeFiles/orocos-kdl.dir/segment.cpp.o    
Building CXX object src/CMakeFiles/orocos-kdl.dir/chainiksolvervel_pinv_givens.cpp.o
c++: error: CMakeFiles/orocos-kdl.dir/segment.cpp.o: No such file or directory    
c++: error: CMakeFiles/orocos-kdl.dir/chainiksolvervel_pinv_givens.cpp.o: No such file or directory
src/CMakeFiles/orocos-kdl.dir/build.make:54: recipe for target 'src/CMakeFiles/orocos-kdl.dir/chainiksolvervel_pinv_givens.cpp.o' failed
make[2]: *** [src/CMakeFiles/orocos-kdl.dir/chainiksolvervel_pinv_givens.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
src/CMakeFiles/orocos-kdl.dir/build.make:77: recipe for target 'src/CMakeFiles/orocos-kdl.dir/segment.cpp.o' failed
make[2]: *** [src/CMakeFiles/orocos-kdl.dir/segment.cpp.o] Error 1
CMakeFiles/Makefile2:121: recipe for target 'src/CMakeFiles/orocos-kdl.dir/all' failed    
make[1]: *** [src/CMakeFiles/orocos-kdl.dir/all] Error 2
Makefile:117: recipe for target 'all' failed
make: *** [all] Error 2
<== Failed to process package 'orocos_kdl': 
 Command '['/opt/ros/indigo/env.sh', 'make', '-j2', '-l2']' returned non-zero exit status 2

Reproduce this error by running:
==> cd /home/larics/ros_catkin_ws/build_isolated/orocos_kdl && /opt/ros/indigo/env.sh make -j2 -l2

Command failed, exiting.

I can't really understand what went wrong, seems like segment.cpp.o and chainiksolvervel_pinv_givens.cpp.o do not get built correctly, but I don't understand why. Copying the whole orocos_kdl folder to my other machine running Ubuntu Precise and building it there works flawlessly. I'm suspecting it might have something to do with the CMake version (Debian has CMake 3.0, while Ubuntu has 2.8.9).

Any help will be greately appreciated!

EDIT 1: I have been digging around ... (more)

2014-12-09 18:16:40 -0500 commented answer "apt-get source" for packages.ros.org?

This does not seem to work for me. I'm running Hydro on 12.04, e.g., both

apt-get source ros-hydro-gmapping

and

apt-get source ros-hydro-slam-gmapping

return E: Unable to find a source package for ros-hydro-slam-gmapping.

Am I missing something?

2014-10-20 20:13:18 -0500 marked best answer Is there a tf:MessageFilter in the tf Python API?

The tf::MessageFilter Tutorial shows the C++ API. Does this functionality exist in the Python API?

Doing a quick search:

grep -i -R --include=*.py messagefilter .

from the tf folder doesn't yield any results.

Best, damjan

2014-10-20 20:13:06 -0500 received badge  Great Question (source)
2014-10-02 04:03:25 -0500 received badge  Enthusiast
2014-07-02 09:11:02 -0500 answered a question ROS driver for SICK NAV350?

A colleague of mine made a NAV driver+ROS wrapper recently, based on the sicktoolbox code. It's available here:

sicktoolbox fork

sicktoolbox_wrapper fork

The code needs some tyding up and there are a several hardcoded things, but we're currently using it on a project and it works :)