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.

ROS time starts at 90

asked 2020-01-13 03:34:01 -0500

davidem
83 ●16 ●25 ●28

I am working with ROS Melodic on Ubuntu 18.04, using Gazebo as virtualizer and a Turtlebot.
So far, with every simulation I ran, I used the so-called turtlebot_house.world that came with installing the ROBOTIS Turtlebot3 simulations package.
When I use that world, ROS time correctely starts at 0.00 secs.
Recently, I defined my own world using the Gazebo world editor tool as described in this video. When I launch a simulation in my world, ROS time starts at approx 90.00 secs: I can see this in the stdout shell and also getting the time inside my scripts.

I have no clue in what's wrong nor what to do to provide further details. The same issue also happens across PCs.

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2020-01-13 03:44:36 -0500

davidem
83 ●16 ●25 ●28

Found the solution myself: gotta say it's definetly awkward, but for some reason my exported world had these four parameters:

<sim_time>92 36000000</sim_time>
<real_time>92 561712388</real_time>
<wall_time>1578849264 106447901</wall_time>
<iterations>92036</iterations>

I just commented them out and the time correctely starts at 0.00

edit flag offensive delete link

add a comment

Question Tools

2 followers

Stats

Asked: 2020-01-13 03:34:01 -0500

Seen: 79 times

Last updated: Jan 13 '20

ROS time starts at 90 edit

1 Answer

Question Tools

Stats

Related questions

ROS time starts at 90