Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Control loop missed its desired rate of 20.0000Hz... the loop actually took 0.1200 seconds

asked 2021-10-07 09:45:55 -0600

harish556
74 ●17 ●27 ●34

when i start my navigation stack when i give 2d pose estimate i get this error

Ignoring initial pose in frame "odom"; initial poses must be in the global frame, "map"

then when i give 2d nav goal i get these errors

 WARN] [1633615470.911036041, 31.705000000]: Control loop missed its desired rate of 20.0000Hz... the loop actually took 0.1200 seconds

and the robot starts rotating a one place

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2021-10-08 08:04:59 -0600

divyam.rastogi
36 ●1 ●4 ●3

The first warning occurs because probably your Fixed Frame is set to odom in Rviz. If you change it to the map frame, the warning should go away. If you do not have a map frame, then you can just publish a static transform from odom to map.

The second warning just tells you that you want the control loop to run at 20Hz i.e, 0.05 sec but actually it took 0.12 secs. You can just reduce your control frequency to 5 Hz or use a more powerful computer.

The in place rotation part can happen due to many reasons and you need to provide more information about how you set up your robot. It is most likely not related to the two warnings you mentioned.

edit flag offensive delete link

add a comment

Question Tools

2 followers

Stats

Asked: 2021-10-07 09:45:55 -0600

Seen: 454 times

Last updated: Oct 08 '21

Control loop missed its desired rate of 20.0000Hz... the loop actually took 0.1200 seconds edit

1 Answer

Question Tools

Stats

Related questions

Control loop missed its desired rate of 20.0000Hz... the loop actually took 0.1200 seconds