DangTran's profile - activity

@cskbala I believe that both libgazebo_ros_gpu_laser and libgazebo_ros_laser.so only capture 2D scan information (althou

Hi there, have you found the solution for this problem?

Update link: https://pointclouds.org/documentation/sac__segmentation_8hpp_source.html

Hi, I believe that some components in Boost will work fine, but not all of them. I wonder have you experienced some code

Neither. When running the Gazebo, there will be a world frame initialized, position of the robot is already identified

Instead of describing theoretical concepts, I will explain in my intuitive way: There are 3 special frames that you usu

Hi, I just want to add a more explicit code on how to use pub.getNumSubscribers() answered by @dornhege. If you want to

Where did you put the two above lines? Btw, current_state is the PARENT stage of grasp_generator stage. So can you try d

Usually, trajectory is the results from the planner, of course you can design a trajectory manually, it is quite tedious

There is no gazebo plugin for ackermann-controller currently according to what I know. But probably there are some inter

Yes, I updated the answer

To sum thing up, the controller file arm_controller_ur3.yaml is follows: arm_controller: type: position_controllers/J

@gvdhoorn I totally agree with you. My answer emphasizes more on the difference in application scenarios rather than fu

To sum thing up, the controller file arm_controller_ur3.yaml is follows: arm_controller: type: position_controllers/J

If you want to control robot's joint, such as shoulder_pan_joint=0.1, you can do that by sending command to topic, then

arm_controller used for trajectory position_controllers/JointTrajectoryController, while joint_group_position_controller

What is arm_controller?

publishTrajectoryLine(...) visualize the green trajectory line. while publishTrajectoryPath(...) visualize the simulate

Thanks for a quick response. I am working with a lab-server that has been developed in ROS-Kinetic in 16.04 for a long t

Alternation for `call_async()` in service client for ROS2-Ardent Hi all, I new to ROS2 and try to follow the ROS2-tutor

Look like this one is what you are looking for? (https://github.com/simlei/cookiecutter-ros-python)

Hi all,

Have anyone experienced a weird behavior below when working with pluginlib? Could you please help me understand the problem?

I trying to work with pluginlib by following the wiki-tutorial. By installing pluginlib-tutorials using sudo apt install ros-kinematic-pluginlib-tutorials, the main node works fine and normal.

But to build the same package from source, the error Segmentation fault (core dumped) keep appearing everytime adding <pluginlib_tutorials_ plugin="${prefix}/polygon_plugins.xml" /> in the package.xml file.

I can successfully initialize the pluginlib::ClassLoader object, but without "Plugin Description File" in the package.xml, I can not create plugin-instances.

My workspace setting:

test_ws/
└── src
    ├── pluginlib_tutorials_
    │   ├── CMakeLists.txt
    │   ├── include
    │   │   └── pluginlib_tutorials_
    │   │       ├── polygon_base.h
    │   │       └── polygon_plugins.h
    │   ├── package.xml
    │   ├── polygon_plugins.xml
    │   └── src
    │       ├── polygon_loader.cpp
    │       └── polygon_plugins.cpp

package.xml:

<buildtool_depend>catkin</buildtool_depend>
  <build_depend>pluginlib</build_depend>
  <build_depend>roscpp</build_depend>
  <exec_depend>pluginlib</exec_depend>
  <exec_depend>roscpp</exec_depend>
  <export>
    <pluginlib_tutorials_ plugin="${prefix}/polygon_plugins.xml" /> 
  </export>

Could anyone please help me?

For anyone having problems with multiple version dependency when working in ROS, this link may useful. The example demon

I finally understand the problem and fixed it successfully: The main reason is ros::package::xxx() compatible with boost

Segfault in pluginlib-tutorial whenever adding Plugins-Description-File between <export> tags Hi all, Have anyon