nlamprian's profile - activity

That is when gazebo starts commanding the joints, which means there is something wrong with your model. Without having

That is when gazebo starts commanding the joints, which means there is something wrong with your model. Without having

Here is the last link. A TimerQueueCallback instance is created each time an iteration is scheduled for execution.

It's next_expected that gets updated. current_expected gets its value from next_expected when a TimerQueueCallback insta

It's next_expected that gets updated. current_expected gets its value from next_expected when a TimerQueueCallback insta

current_expected is computed after the callback is called. But that is only relevant when the timer jumps. In normal ope

Check that listener.cpp is in the specified directory and has the correct name.

I'll refer to roscpp, but I expect the same goes for rospy. You can use ros::package::getPath("<my-package-name>"

Given that everything is inside the nodelet class (and so the publisher is a member variable), there isn't much to consi

First of all, you can't do the processing in the callback, because it will (potentially) block the other nodelets. Here

The tags for the tag_rot and tag_trans don't have a / at the end: ... default="0 -0.28 -0.1 0 0 0" />

The problem is that you have left the fixed frame to map. RViz doesn't know where to place the point cloud, since the map -> velodyne transform doesn't exist. So, either use the static_transform_publisher in tf to publish that transform, or just change the frame in rviz to velodyne.

You need to use the command attribute, like so: <param name="port" command="identify_port.py device1" />. This will set the output of your script as the value of port.

Don't forget that the script should be in your PATH and have execute permission.

I don't have personal experience with this. Maybe someone else can help you better.

This error comes from the client. You are calling 2 times set_succeeded on the server, so the client complains, as the second time the action is already in a terminal state. You should call the set_X methods only once.

You can't with rqt_plot. But you can with rqt_multiplot. It's far superior to rqt_plot with many great features.

Notice how you are not assigning anything with the received message msg.

You haven't defined the constructor of the class, i.e. replace ; with {}.

The node doesn't need to know about the bag file. The code expects images on a topic. So, you just have to playback the bag file and subscribe to the right topic. See, here. You can also use the rqt_bag tool to examine the bag file.

sensor_msgs::PointCloud is a plain message type. There are no special member functions like get_points_size.

With the -j option, you specify the number of threads to use when compiling. See here.