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 |
Hi, I'm not sure, if I understand you question in details, but I this you need to share your packages and scripts over the network.
ROS can communicate over the network but not sharing packages and programs.
You need a mechanism to sharing binaries over the network.
Possible solutions:
central fileserver, with shared binaries (samba or nfs). Clients can mount and use central data.
central development repository like git. Clients can checkout central repository data .
Push central or development data via script to clients, e.g. via scp or rsync.
Happy sharing ros data
Cheers Chrimo
ps: please correct me, if I'm wrong
| | 2 | No.2 Revision |
Hi,
Hi,
I'm not sure, if I understand you question in details, but I this you need to share your packages and scripts over the network.
ROS can communicate over the network but not sharing packages and programs.
You need a mechanism to sharing binaries over the network.
Possible solutions:
central fileserver, with shared binaries (samba or nfs). Clients can mount and use central data.
central development repository like git. Clients can checkout central repository data .
Push central or development data via script to clients, e.g. via scp or rsync.
Happy sharing ros data
Cheers Chrimo
ps: please correct me, if I'm wrong
| | 3 | No.3 Revision |
Hi,
I'm not sure, if I understand you question in details, but I this you need to share your packages and scripts over the network.
ROS can communicate over the network but not sharing packages and programs.
You need a mechanism to sharing binaries over the network.
Possible solutions:
central fileserver, with shared binaries (samba or nfs). Clients can mount and use central data.data (e.g. your catkin_ws.
central development repository like git. Clients can checkout central repository data .
Push central or development data via script to clients, e.g. via scp or rsync.
Happy sharing ros data
Cheers Chrimo
ps: please correct me, if I'm wrong
| | 4 | No.4 Revision |
Hi,
I'm not sure, if I understand you question in details, but I this you need to share your packages and scripts over the network.
ROS can communicate over the network but not sharing packages and programs.
You need a mechanism to sharing binaries over the network.
Possible solutions:
central fileserver, with shared binaries (samba or nfs). Clients can mount and use central data (e.g. your catkin_ws.
central development repository like git. Clients can checkout central repository data .
Push central or development data via script to clients, e.g. via scp or rsync.
In the easiest case and you have packages already distributed, you need to set ROS_MASTER_URI=http://roscore:11311
Happy sharing ros data
Cheers Chrimo
ps: please correct me, if I'm wrongwrong.
| | 5 | No.5 Revision |
Hi,
I'm not sure, if I understand you question in details, but I this think you need to share your packages and scripts over the network.
ROS can communicate over the network but not sharing packages and programs.
You need a mechanism to sharing binaries over the network.
Possible solutions:
central fileserver, with shared binaries (samba or nfs). Clients can mount and use central data (e.g. your catkin_ws.
central development repository like git. Clients can checkout central repository data .
Push central or development data via script to clients, e.g. via scp or rsync.
In the easiest case and you have packages already distributed, you need to set ROS_MASTER_URI=http://roscore:11311
Happy sharing ros data
Cheers Chrimo
ps: please correct me, if I'm wrong.
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.
