Why is my Turtlebot 3 SLAM not working properly?

edit

@davidem I have already tried using slam with "roslaunch turtlebot3_slam turtlebot3_slam.launch slam_methods:=gmapping" , it worked as it should, therefore the center of the screen is discovered. Problem is, that mapping stops working correctly as i start to move with robot using teleoperation.

I need to understand what you mean by "stops working correctely". The map doesn't get updated? The readings of the laser do not match the actual obstacles? Also, are you using a 3D world in a simulator like Gazebo or a 2D world in a simulator like Stage? Please edit your question to provide as much information as possible

@davidem I am using a real device and i try to map a room, i tried simulated world in gazebo before, and gmapping was working with no problems. By "stops working correctly" i meant that the map is always updating but for example if i go one meter forward, then i rotate 180 degrees and return one meter back, the map will update in a new grey places (and not in the same already discovered place). Doing this all over again gets my map bigger over time (even if i'm always in the same place).

Does this problem happen in the simulation aswell? Have you tried? My suggestion is that you go through the Robotis tutorials for the Turtlebot3 if you haven't. First, understand deeply the navigation stack using a simulated environment, the different nodes, what they offer, what do they need and what configuration is required. Deploying a real robot shouldn't be much of a difference.

@davidem Well yes, i have tried the simulation. The problem is only in the real environment only with the waffle turtlebot. The burger in the real environment is working as in the simulation, therefore odometry shows exact location. Also rotating quickly with the waffle makes map messy, but rotating quickly with burger does no harm to map.