The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Theoretical this is a good idea but only theoretical.
The first problem here would be how to act if the Master is not reachable for sometime.
The second problem how to compensated latency's in a network.
And last but not least how to handle the all the time request in terms of CPU and bandwidth load.
So as you can see, using a well known technology is introducing less problems. Of course your basic idea is right and will work on a single system robot. It just will not scale well until the new solution takes care about a load of small thinks. By side of this the current idea of starting not from zero allows you to know at which date and time your data was recorded. This is important for scientific work as well as for debugging.
What really would be create is to have a install package or tool from ros which would make the synchronisation easier. May someone takes some time and includes a roschrony or so ;-) .
For those who need help to install a time server take a look here.
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.
