ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange

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.

Revision history [back]

I was facing the same issue and realized that it happened because my node runs before gazebo simulation is ready. So, for me the solution was to simply run the node that contains ros::Time::now only after the gazebo simulation is ready and running.

I guess this is because ros::Time::now().toSec() gets the time of simulation that you see in gazebo, that's why it has to be run after running gazebo.

I hope this helps

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.

Powered by Askbot version 0.10.2