Vic's profile - activity

Well, code doesn't lie, sometime our interpretation does. Do you have the possibility to launch the system with and with

I'm working in a quite big project in ROS 1, Noetic. In this project, some code need Eigen 3.4.9. However, some other code needs tf2, including eigen conversions. When compiling with both of them, I have the same errors than compiling with Eigen 3. Is there a way to make this work?

Let's look at the top of the file <arg name="velocity_control" default="false"/> I think that if you launch wi

Let's look at the top of the file <arg name="run_demo_traj" default="false"/> <arg name="effort_control"

Let's look at the top of the file <arg name="run_demo_traj" default="false"/> <arg name="effort_control" defau

Did you try to loop? Something along the line of rate = rospy.Rate(10) while not rospy.is_shutdown(): sm.execute()

Did you try to loop? Something along the line of rate = rospy.Rate(10) while not rospy.is_shutdown(): sm.execute(

Did you try to loop? Something along the line of rate = rospy.Rate(10) while not rospy.is_shutdown(): sm.execute(

Strong statement indeed. Let me reformulate. A callback's execution time should be less than your node's rate.

I think his limits come more from heavy callback than python/C++ raw performances

Because there are other tasks in the original program that require execution time Try not overloading your callback

Because there are other tasks in the original program that require execution time Try not overloading your callback

First, what purpose serves sleeping in your callback? Right now, each message will be put in a queue that waits for the

Those are flags used for compiling. -j4 indicate you want to compile using 4 cores of your CPU (https://askubuntu.com/q

Those are flags used for compiling. https://earthly.dev/blog/make-flags/ -j4 indicate you want to compile using 4 cores

Those are flags used for compiling. https://earthly.dev/blog/make-flags/ -j4 indicate you want to compile using 4 cores

Setting args="/dev/ttyUSB0" solved the issue. Thanks.

I am trying to automate a rosrun into a roslaunch. My command is shown below:

rosrun robotiq_2f_gripper_control Robotiq2FGripperRtuNode.py /dev/ttyUSB0

Problem:

I can not find a way to pass my argument as a parameter. The source code uses sys.argv[1] as the command line parameter. Is there a way to make this work in a launch file?

This is what I tried:

<launch>
    <node pkg="robotiq_2f_gripper_control" type="Robotiq2FGripperRtuNode.py" name="Robotiq2FGripperRtuNode" output="screen">
    <param name="device" value="/dev/ttyUSB1" />
</launch>

However, the execution is similar to mistyping the name of the device port in the rosrun command. I can edit the source code. Furthermore, I know that I could call the rosrun command in a .sh script, but I would appreciate using the proper tool for the job.

Offending package: TAMS-Group/robotiq

Thank you for your answer. Will try it out and let you know if that solve my problem.

What you can try : rostopic echo your "goal_pose" topic. The callback won't be called if the topic is never published

What you can try : - rostopic echo your "goal_pose" topic. The callback won't be called if the topic is never published

Could you please format the code? It is a bit hard to read

How to set parameters names for python nodes in roslaunch I'm trying to automatize a rosrun into a roslaunch. My command

Thanks for the answer. Are there any ressource on how to build from source on the system tf2?

TF2-Eigen 3.4 compatibility I'm working in a quite big project in ROS 1, Noetic. In this project, some code need Eigen 3

I'm trying to do the same as this example : https://answers.ros.org/question/3952...

The function is documented here : http://docs.ros.org/en/jade/api/rosli...

I created a minimum reproductible example of my problem, which I tested both on Kinetic and Noetic :

test.cpp :

#include <iostream>
#include <ros/package.h>

int main(int argc, char **argv)
{
   std::cout << "Hello, world!" << std::endl;
   std::string testString = ros::package::getPath("testPath");
   std::cout << "Package path is "  << testString << std::endl;
}

Package.xml :

<?xml version="1.0"?>
<package format="2">
<name>testPath</name>
<version>0.0.0</version>
<description>The testPath package</description>

<maintainer email="victor@todo.todo">victor</maintainer>

<license>TODO</license>


<buildtool_depend>catkin</buildtool_depend>
<build_depend>roscpp</build_depend>
<build_depend>roslib</build_depend>
<build_export_depend>roscpp</build_export_depend>
<build_export_depend>roslib</build_export_depend>
<exec_depend>roscpp</exec_depend>
<exec_depend>roslib</exec_depend>

<export>
  <!-- Other tools can request additional information be placed here -->

</export>
</package>

CmakeList :

cmake_minimum_required(VERSION 3.0.2)
project(testPath)

find_package(catkin REQUIRED COMPONENTS
  roscpp
  roslib
)
catkin_package(
#  INCLUDE_DIRS include
#  LIBRARIES testPath
#  CATKIN_DEPENDS roscpp roslib
#  DEPENDS system_lib
)

include_directories(
# include
  ${catkin_INCLUDE_DIRS}
)

## Declare a C++ library
# add_library(${PROJECT_NAME}
#   src/${PROJECT_NAME}/testPath.cpp
# )

add_executable(${PROJECT_NAME}_node src/test.cpp)

The linking error I'm getting :

undefined reference to « ros::package::getPath(std::__cxx11::basic_string<char, std::char_traits<char="">, std::allocator<char> > const&) »

Any leads on how to make this work?

As @gvdhoorn pointed, I was missing the target_link_libraries in CmakeList.txt

Unable to link ros::package::getPath I'm trying to do the same as this example : https://answers.ros.org/question/39523/

You were right. Adding target_link_libraries(${PROJECT_NAME}_node ${catkin_LIBRARIES} ) in the CmakeLists.txt fix

If your node is started before the topic is running, you can create a subscriber and a static boolean in your callback (

Unable to link ros::package::getPath I'm trying to do the same as this example : https://answers.ros.org/question/39523/