asbird's profile - activity

Gazebo freezes when inserting a custom model. When I'm trying to insert a custom model (I've tried few of them) in forma

Gazebo freezes when inserting a custom model. When I'm trying to insert a custom model (I've tried few of them) in forma

Gazebo freezes when inserting a custom model. When I'm trying to insert a custom model (I've tried few of them) in forma

Line intersection In my code I am clustering a cloud into many clusters, for each cluster I extract all of the lines. M

So as you can see on the code I'm creating two subscribing nodes:

1. Subscribing from laser scanner
2. Subscribing /tf which is result of transformation /odom -> /robot

In this code I'm using tf2_sensor_msgs to transform point_cloud (which is just /mybot/laser/scan transformed into point_cloud) with do_transform_cloud()using /tf and publish it to topic /laserPointCloud.

My problem is that when I'm publishing it to RVIZ i can see some kind of vibrations of the subscribed point_cloud. I was thinking that it may be because frequency of publishing /mybot/laser/scan is 40Hz and of the /tf 30 but I've made two separate scripts to publish pointcloud at 30Hz (to be the same as /tf using rate.sleep()) and it didn't help (the vibrations appeared like in the given code).

Ubuntu:18.04 LTS / ROS: Melodic

Hello, I'm new to rviz and I encountered a problem while i was trying to run project from this repo . When im working on Gazebo i can see a whole model of the robot but when i try to do the same on Rviz i can see only laser scanner model.

Full code is available HERE. The only thing I've changed is when i was trying to run for example gazebo i had errors which were saying that something is wrong with mybot.xacro, I've changed the type of point separated values were typed from

 <box size=".4 .2 .1"/>

to

<box size="0.4 0.2 0.1"/>

end everything work fine except the thing i cant see the model in Rviz.

I'm working on Ubuntu 18.05 LTS

ImportError: libpcl_keypoints.so.1.7: cannot open shared object file: No such file or directory I'm trying to use PCL li

@tfoote Everything work's perfectly, you can post your comment as an answer and I'll mark it. Thank you for your time an

The problem was that both /gazebo and /robot_state_publisher were publishing /tf and my callback for /tf subscribing nod

The problem was that both /gazebo and /robot_state_publisher were publishing /tf and my callback for /tf subscribing nod

The problem was that both /gazebo and /robot_state_publisher were publishing /tf and my callback for /tf subscribing nod

@tfoote I've edited my answer

The problem was that both /gazebo and /robot_state_publisher were publishing /tf and my callback for /tf subscribing nod

The problem was that both /gazebo and /robot_state_publisher were publishing /tf and my callback for /tf subscribing nod

The problem was that both /gazebo and /robot_state_publisher were publishing /tf and my callback for /tf subscribing nod

Yes, now I can see that /gazebo and /robot_state_publisher nodes are publishing /tf .

Yes now I can see that /gazebo and /robot_state_publisher nodes are publishing /tf .

Yes now I can see that /gazebo and /robot_state_publisher are publishing /tf .

I've figured out that when i echo the /tf without rviz turned on it shows how x, y, z and rotation changes but when i tu

I've found the problem, this node in RViZ.launch file was causing this. <node name="robot_state_publisher" pkg="robo

I've found the problem, this node in RViZ.launch file was causing this. <node name="robot_state_publisher" pkg="robo

Vibrating point cloud in rviz. So as you can see on the code I'm creating two subscribing nodes: Subscribing from la

I've found the problem, this node in RViZ.launch file was causing this. <node name="robot_state_publisher" pkg="robo

I needed to extract laser_scan in order to transform it into the other frame so i can apply an algorithm in python to th

I've found the problem, RViZ was causing these vibrations but I don't know why...

Vibrating point cloud in rviz. So as you can see on the code I'm creating two subscribing nodes: Subscribing from la