hansolo's profile - activity

Unlike killing a single node, apparently, kill all causes another issue. Please refer to this issue.

Unlike killing a single node, apparently, _kill all_ causes another issue. Please refer to this issue.

Comment on the last edit: Another walkaround might be cloning ros_comm, or just its ros_node folder into catkin workspac

Thank you for creating the issue in ros_comm. Anyway, when that issue is solved this question will become obsolete, so l

Oh, just noticed that you closed it for being a duplicate, but it is not. The other question asks whether they can kill

Thank you for editing the answer there. I will put the solution also here as it is not exactly the same question.

Cannot locate node of type [rosnode] in package [rosnode] In ros-noetic, ubuntu 20.04, I am launching the following rosl

Cannot locate node of type [rosnode] in package [rosnode] In ros-noetic, ubuntu 20.04, I am launching the following rosl

This should work: <node pkg="topic_tools" type="mux" name="mux_cmdvel" args="sel_cmdvel joystick/cmd_vel cmd_vel mux:

<node pkg="topic_tools" type="mux" name="mux_cmdvel" args="sel_cmdvel joystick/cmd_vel cmd_vel mux:=mux_cmdvel"> T

I had the same problem, having installed the ROS extension on VSCode. I created a workspace file under ~/catkin_ws, I co

There are suggested answers to this problem under another question.

I had the same problem, having installed the ROS extension on VSCode. I created a workspace file under ~/catkin_ws, I co

Note, in Melodic, BufferCore doesn't have a lookup_transform method. Instead it is named tf_buffer.lookup_transform_core

Note, in Melodic, BufferCore doesn't have a lookup_transform method. Instead it is named tf2_py.lookup_transform_core().

It is too old, I am not fully sure. Do you mean that the universal-robot package installed through apt-get may be run in

Yes, it should be alright as long as you update the TF information. You should publish the latest pose of the arm base t

MoveIt is generally used to control manipulator chains (e.g. robot arm). You can attach a robot arm on a mobile robot by

For me it was indentation mismatch in a yaml file.

I have a launch file with:

  <arg name="INTENSITY" default="1.2" />
  <param name="my_intensity" type="double" value="$(arg INTENSITY)" />

The same launch file starts a ROS node, my_node . In my_node's main method I have the following, to get that parameter:

  ros::init(argc, argv, "my_node");
  ros::NodeHandle nh;
  string param_name;
  if(!nh.searchParam("/my_intensity", param_name) ){
    ROS_ERROR("Can't find param.");
    return -1;
  }

  double it;
  ros::param::get(param_name, it);  

  ROS_INFO("Intensity is %f.", it);
  ...

Running this prints Intensity is 0.0.. Although when I run rosparam get /my_intensity in a terminal window I get the correct value (1.2).

When I change the type of it to string, what I get is an empty string. The same approach always worked for my other nodes. So I am really confused. What may be causing this behavior?

Thank you.

System: Ubuntu 16.04, ros-kinetic.

Ok, I found the reason after poking some more. The same node was subscribing to a topic with the same name (my_intensity

Can't get double parameter in node (C++) I have a launch file with: <arg name="INTENSITY" default="1.2" /> &l

We can export and import Moveit scene objects to/from a text file (*.scene) using the RViz GUI (picture below). I would like to do the same automatically, so that the scene will be loaded on start. I am aware of the option of creating collision objects by code, however I want to have a more maintainable approach (data over code).

Is there a way to save/load Moveit planning scene objects to/from text, using C++ API or using an existing ros node/service?

System: Ubuntu 16.04, ROS-Kinetic

Moveit import scene from text automatically We can export and import Moveit scene objects to/from a text file (*.scene)

Moveit import scene from text automatically We can export and import Moveit scene objects to/from a text file (*.scene)

Moveit import scene from text automatically We can export and import Moveit scene objects to/from a text file (*.scene)