Synchronizing system time

[christenbc]

I have a doubt regarding the fix proposal you give:

To fix this:
go to "Service" -> "Configuration" -> "System settings" -> "Time settings" -> "Set device time on robot"
Afterwards, the ROS software on the robot will restart, so you'll have to start move_base again (see below).

I don't know at what "Service" you are making reference. Do you mean with that to access the web interface of the robot and access the configuration from there? i.e. "System" -> "Settings" -> "Date & Time" ?

Because I tried that and I still get errors when I try to:
rosrun gmapping slam_gmapping scan:=/scan map:=/gmapping/map

Warning: TF_OLD_DATA ignoring data from the past for frame odom at time 1.54393e+09 according to authority unknown_publisher
Possible reasons are listed at http://wiki.ros.org/tf/Errors%20explained
         at line 277 in /tmp/binarydeb/ros-kinetic-tf2-0.5.18/src/buffer_core.cpp

And
rosrun tf tf_monitor

RESULTS: for all Frames

Frames:
Frame: /back_laser_link published by unknown_publisher Average Delay: -3603.23 Max Delay: 0
Frame: /base_footprint published by unknown_publisher Average Delay: -3603.12 Max Delay: 0
Frame: /base_link published by unknown_publisher Average Delay: -3603.23 Max Delay: 0
Frame: /camera_floor_depth_optical_frame published by unknown_publisher Average Delay: -3603.12 Max Delay: 0
Frame: /camera_floor_link published by unknown_publisher Average Delay: -3603.23 Max Delay: 0
Frame: /front_laser_link published by unknown_publisher Average Delay: -3603.24 Max Delay: 0
Frame: /imu_link published by unknown_publisher Average Delay: -3603.24 Max Delay: 0
Frame: /odom published by unknown_publisher Average Delay: -3603.3 Max Delay: 0
Frame: bl_caster_rotation_link published by unknown_publisher Average Delay: 0.0347947 Max Delay: 0.0939313
Frame: bl_caster_wheel_link published by unknown_publisher Average Delay: 0.0347972 Max Delay: 0.0939345
Frame: br_caster_rotation_link published by unknown_publisher Average Delay: 0.0347989 Max Delay: 0.0939366
Frame: br_caster_wheel_link published by unknown_publisher Average Delay: 0.0348004 Max Delay: 0.0939391
Frame: fl_caster_rotation_link published by unknown_publisher Average Delay: 0.034802 Max Delay: 0.0939414
Frame: fl_caster_wheel_link published by unknown_publisher Average Delay: 0.0348036 Max Delay: 0.0939437
Frame: fr_caster_rotation_link published by unknown_publisher Average Delay: 0.0348052 Max Delay: 0.0939455
Frame: fr_caster_wheel_link published by unknown_publisher Average Delay: 0.0348074 Max Delay: 0.0939473
Frame: imu_frame published by unknown_publisher(static) Average Delay: 0 Max Delay: 0
Frame: left_wheel_link published by unknown_publisher Average Delay: 0.0348088 Max Delay: 0.0939493
Frame: right_wheel_link published by unknown_publisher Average Delay: 0.0348104 Max Delay: 0.0939515
Frame: surface published by unknown_publisher(static) Average Delay: 0 Max Delay: 0
Frame: us_1_frame published by unknown_publisher(static) Average Delay: 0 Max Delay: 0
Frame: us_2_frame published by unknown_publisher(static) Average Delay: 0 Max Delay: 0

All Broadcasters:
Node: unknown_publisher 219.438 Hz, Average Delay: -3123.87 Max Delay: 0.0869416
Node: unknown_publisher(static) 1e+08 Hz, Average Delay: 0 Max Delay: 0

Could you help me fix this issue?
Where can I find the "Service" you make reference?

[mintar]

Since you closed the issue, I guess you found it. I'm still posting this here for future reference:

The "Service" etc. I was making reference to are steps in the 1.9.13 web interface. You're using version 2.x of the MiR software, where the web interface was drastically changed, so your steps will be different.

[christenbc]

Yes, that's fine. I thought that also and changed the time settings through the web interface. Thanks for the reply.