carlosjoserg's profile - activity

Hi there, it is reported here: https://github.com/RobotWebTools/rosbridge_suite/issues/544 You'll find a temporal solut

You should give decision_making a try as well.

Hi Mario,

I know it is a very old question, but I'm actually looking for a reason why this package is not in the standard release of indigo, since it was in hydro, to see if there was some reason.

Here there was a PR (already merged) that allows it to be used in Ubuntu 14.04/Indigo, and in fact, I have been using it from source. But it'd be nice to have it within the official release.

So the answer is that it is supported on indigo, but somehow it is not available in the official release.

Best, Carlos

Indeed. As stated in the answer, I confirm that for those using Travis CI, the solution is to use language: generic, so pyenv is not installed. Thanks again.

Nevermind my previous comment, it looks like a CI-related issue.

Hi there, I'm using CI, and up there, python is 2.7.10, and throws the same error reported here. Package python-catkin-pkg is correctly installed, here is the build log. In my PC, python is 2.7.6 and everything runs well. Any idea?

http://www.quora.com/What-are-the-cor...

I'm interested in this as well. I haven't been able to configure a build, since the default env is 12.04 in drone.io as well.

Hi there, many thanks, I was looking exactly this! It worked for me! But changed: 'std::vector<std::string> topics;' -> 'std::string topic("tf");', 'rosbag::View view(bag, rosbag::TopicQuery(topics));' -> rosbag::View view(bag, rosbag::TopicQuery(topic));', and deleted 'topics.push_back("/tf");'

True, for the LWR 4+. Just to say, we found more useful creating a custom plugin (of course, using the gazebo_ros_control plugin as a template) to add stuff to the sim interface, see our suggested class hierarchy: https://github.com/CentroEPiaggio/kuk...

Yes, indeed. All hardware (except the head) packages you see in the robot follow this diagram, and on top, MoveIt! is already configured to make the most of the controllers.

Oh, and this is our setup

I'm aware of the issue since I have a similar setup, only that twice. I solved it in a more natural and easy way, and you don't loose the coupling of the hand and arm in gazebo, which otherwise would be bad for dynamics, since the arm wouldn't account for the hand weight and inertia. However it requires (not so complicated and not conflicting) changes in the gazebo_ros_control plugin and in the transmission_interface package.

Take a look at this issue, where I propose the answer.

suppose we will only know if the person that posted the OP says something. however, I was having exactly the same error, but it is also true that it might be caused by another cause. thanks for the catkin_lint link

Yes, I know and I usually use it, but still keep forgetting to update the package.xml if add a new dependency. Thanks.

Problem solved.

In general, I have the bad habit of forgetting about the package.xml when starting developing a package. In fact, I copied the CMakeLists.txt, and not the package.xml (don't try that at home)

I added the code below and the problem was gone.

<build_depend>controller_interface</build_depend>
<build_depend>hardware_interface</build_depend>
<build_depend>control_toolbox</build_depend>
<build_depend>realtime_tools</build_depend>
<run_depend>controller_interface</run_depend>
<run_depend>hardware_interface</run_depend>
<run_depend>control_toolbox</run_depend>
<run_depend>realtime_tools</run_depend>

The thing is a bit more strange since I have another HW interface from which I copied the CMakeLists.txt and that does not give that error. Any ideas?

I'm having the same problem. I'm using Indigo on 14.04 and ros control cloned.

Then, I have a HW interface, and in the CMakeLists.txt I need to add the controller_manager package. When I comment the inclusion of the package it compiles and gives a linking error, naturaly.