| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Hello, I am trying to do autonomous navigation with a real robot. Whenever I move the robot or rotate it with teleop, the laser scans move with the robot. I have checked the tf, it is proper still the problem keeps occurring. Can anyone please tell me what could be the reason for it and how to solve it ?
With your config, rviz is transforming each point of the laser scan from the scan frame to the odom frame. This requires that the base_link frame is being updated accurately, because the typical transform chain is scan->base_link->odom.
Your likely problem is that the base_link does not actually match where the physical robot moved, so the rendering of the scan in the rviz window appears wrong.
Ok seems like that is the issue. Actually the lidar sensor is mounted at a height on the robot and is swiveling to create a 3D point cloud after which I am using the octomap server package to get a 2D occupancy grid map. Could thus issue be due to the lidar being mounted at a height and swiveling or as you said it is likely due to mis-match of base_link with the actual physical movement of robot ?
Again, you haven't provided enough information to know how that swiveling relates to the pose of the lidar sensor. The base_link->scan transform must accurately describe the zero-degree ray of the lidar scan.
Ok so here are the transforms I am publishing -
1.) Static transform from laser->laser_tilt_plate (the moving plate on which the lidar sensor is mounted).
2.) Python script publishing the rotating transform from laser_tilt_plate->laser_base_plate (the fixed plate to which the moving plate is connected).
3.) Static transform from laser_base_plate->base_link of robot.
4.) Static transform from base_link->base_footprint of robot.
The swivel angle is 45 degrees and the lidar sensor is at -90 degrees yaw orientation just like shown in this image link - https://pbs.twimg.com/media/EeaADs6Wk... The side facing the laptop is the front side in my case.
I don't understand your description of the transforms. The image you linked appears to show a laser beam that rotates around a single axis (the robot's z axis, which points up toward the ceiling.) What does "the swivel angle is 45 degrees" mean?
Ok so this is how the lidar is swiveling - https://twitter.com/lethic1/status/14... Only difference in my case is the lidar is swiveling only 45 degrees from the horizontal position of the moving plate and towards one direction, the side facing the pc screen as can be seen in the link.
OK, thanks - I understand the lidar beam's motion now. Your transforms seem reasonable. I have no more suggestions at this point.
Asked: 2022-01-14 01:22:21 -0500
Seen: 439 times
Last updated: Jan 15 '22
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
Please edit your description and explain the problem with more detail - it's unclear what you mean by "the laser scans move with the robot". Are you using rviz or the gazebo GUI? What
Fixed Framehave you selected in rviz? Are you using a map? Does the map move when the robot moves, or is the map fixed in place in the rviz window?Ok sorry, so I am using rviz for visualizing the scans and have selected the fixed frame as odom in rviz. Yes, I want to do mapping but first I wanted to check if the tf is set properly for the robot. So whenever I am moving the robot using teleop, the laser scan walls move along with it which should not be happening right. I have checked the tf tree but do not find any issue in that since everything is shown connected in the tf tree. Also when I ticked the tf option in rviz to see the relation between transform of all frames, I noticed that on doing teleop, there is no relative motion between odom and base_footprint. Later on I went ahead with mapping also and noticed that the map does not move with the robot but when I rotate the robot the map starts getting ...(more)