simROS.getTime() returns incoherent values
Posted: 12 Sep 2019, 08:29
Hello all,
When I call simROS.getTime(), I get incoherent values, that goes back and forth and are very different from the values I get with the rest of my ROS components:
If I relaunch V-REP, I get completely different resuls:
For instance, ros::Time::now() returns 1568272409.795527935 on other nodes.
Roscore is launched (before V-REP), the ROS parameter /use_sim_clock not set or set to false. Start and stop the simulation has no impact.
I use V-REP 3.5.0-rev6 and ROS kinetic, on Ubuntu 16.04.
Does someone has a clue on this?
Thanks!
When I call simROS.getTime(), I get incoherent values, that goes back and forth and are very different from the values I get with the rest of my ROS components:
Code: Select all
> simROS.getTime()
406881952.0000326
> simROS.getTime()
406216352.0000326
> simROS.getTime()
407266656.0000326
> simROS.getTime()
406437504.0000326
> simROS.getTime()
407428336.0000326
> simROS.getTime()
406847232.000032
Code: Select all
> simROS.getTime()
3624673344.0000324
> simROS.getTime()
3626354448.0000324
> simROS.getTime()
3625708496.0000324
> simROS.getTime()
3625451328.0000324
> simROS.getTime()
3625753696.0000324
Roscore is launched (before V-REP), the ROS parameter /use_sim_clock not set or set to false. Start and stop the simulation has no impact.
I use V-REP 3.5.0-rev6 and ROS kinetic, on Ubuntu 16.04.
Does someone has a clue on this?
Thanks!