raspet's profile - activity

overview network karma followed questions activity

2021-07-31 22:58:48 -0500	received badge	● Famous Question (source)
2018-05-10 04:18:47 -0500	received badge	● Notable Question (source)
2017-05-04 06:41:21 -0500	received badge	● Popular Question (source)
2017-04-21 10:12:36 -0500	commented answer	how to point and click on rviz map and output the position. It is published at /clicked_point
2017-03-02 09:47:02 -0500	commented question	how to install geometry_msgs on raspberry pi What is your operative system? I encountered lots of problems for raspbian and switched to ubuntu mate 14.04 and everything worked like a charm
2017-03-01 02:33:29 -0500	received badge	● Enthusiast
2017-02-22 06:34:36 -0500	answered a question	Unable to build dependancy with package in stack The problem was indeed that the package was rosbuild, after migrating it to catkin the package is found and can be called within the launch file.
2017-02-22 04:50:28 -0500	commented question	Unable to build dependancy with package in stack Spot on! Did not think about that, I will try to migrate it. Thanks! The package was found here link text I can prob look at the similar package (without PLS support) here link text? Best regards!
2017-02-21 08:35:50 -0500	asked a question	Unable to build dependancy with package in stack Hi and thanks for a great forum! This is my first question, hope I have the correct tags and so forth. So, I am trying to build a launch package connecting several packages. Building dependancies and launching nodes directly under the catkin_ws works fine but when I try to depend to "sicktoolbox_pls_wrapper" I receive: `Cmake Error at /opt/ros/kinetic/share/catkin/cmake/catkinConfig.cmake:83 (find_package): Could not find a package configuration file provided by "sicktoolbox_pls_wrapper" with any of the following names:` `sicktoolbox_pls_wrapperConfig.cmake sicktoolbox_pls_wrapper-config.cmake` The package is found with roscd and rospack find, I can also run the nodes in sicktoolbox_pls_wrapper with rosrun. Could the fact that the package is found in a stack be the problem? I have also tried to build with the dependency directed to the stack without success. Does anyone have an idea? Thanks!