Comments (7)
The problem is that we cannot use $(find cob_bringup)
within the env-loader
part of the machine
-tag as it gets resolved before being passed to the remote PC!
Thus, if an overlay of cob_robots
exists on the b1-PC, "/u/user-name/git/care-o-bot/src/cob_robots/cob_bringup/env.sh" is passed over to the remote PC, e.g. h32.
However, if no overlay exists on the remote-PC, this file does not exist, and cob_bringup/robot.launch
will fail...
In #462, I tried to make the env-loader-script a launch argument and tried to use ~/.bashrc
which is a relative path and could be resolved to the remote-PCs local .bashrc
which can be different from the b1-PC .bashrc
....
However, according to here the env-script needs to be a shell script. (Passing ~/.bashrc
fails with
fxm@cob4-2-b1:~$ roslaunch cob_bringup robot.launch robot:=cob4-1
... logging to /u/fxm/.ros/log/eb99b746-fc8e-11e5-b1a9-eca86bff61c1/roslaunch-cob4-2-b1-9337.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
WARNING: disk usage in log directory [/u/fxm/.ros/log] is over 1GB.
It's recommended that you use the 'rosclean' command.
started roslaunch server http://cob4-2-b1:46077/
remote[cob4-2-t2-0] starting roslaunch
remote[cob4-2-t2-0]: creating ssh connection to cob4-2-t2:22
launching remote roslaunch child with command: [env ROS_MASTER_URI=http://cob4-2-b1:11311 /u/fxm/git/care-o-bot/src/cob_robots/cob_bringup/env.sh roslaunch -c cob4-2-t2-0 -u http://cob4-2-b1:46077/ --run_id eb99b746-fc8e-11e5-b1a9-eca86bff61c1]
remote[cob4-2-t2-0]: ssh connection created
remote[cob4-2-t1-1] starting roslaunch
remote[cob4-2-t1-1]: creating ssh connection to cob4-2-t1:22
launching remote roslaunch child with command: [env ROS_MASTER_URI=http://cob4-2-b1:11311 /u/fxm/git/care-o-bot/src/cob_robots/cob_bringup/env.sh roslaunch -c cob4-2-t1-1 -u http://cob4-2-b1:46077/ --run_id eb99b746-fc8e-11e5-b1a9-eca86bff61c1]
remote[cob4-2-t1-1]: ssh connection created
remote[cob4-2-h32-2] starting roslaunch
remote[cob4-2-h32-2]: creating ssh connection to cob4-2-h32:22
launching remote roslaunch child with command: [env ROS_MASTER_URI=http://cob4-2-b1:11311 ~/.bashrc roslaunch -c cob4-2-h32-2 -u http://cob4-2-b1:46077/ --run_id eb99b746-fc8e-11e5-b1a9-eca86bff61c1]
remote[cob4-2-h32-2]: ssh connection created
remote[cob4-2-s1-3] starting roslaunch
remote[cob4-2-s1-3]: creating ssh connection to cob4-2-s1:22
remote[cob4-2-h32-2]: env: /u/fxm/.bashrc: Permission denied
[cob4-2-h32-2] process has died
launching remote roslaunch child with command: [env ROS_MASTER_URI=http://cob4-2-b1:11311 /u/fxm/git/care-o-bot/src/cob_robots/cob_bringup/env.sh roslaunch -c cob4-2-s1-3 -u http://cob4-2-b1:46077/ --run_id eb99b746-fc8e-11e5-b1a9-eca86bff61c1]
remote[cob4-2-s1-3]: ssh connection created
remote[cob4-2-t3-4] starting roslaunch
remote[cob4-2-t3-4]: creating ssh connection to cob4-2-t3:22
launching remote roslaunch child with command: [env ROS_MASTER_URI=http://cob4-2-b1:11311 /u/fxm/git/care-o-bot/src/cob_robots/cob_bringup/env.sh roslaunch -c cob4-2-t3-4 -u http://cob4-2-b1:46077/ --run_id eb99b746-fc8e-11e5-b1a9-eca86bff61c1]
remote[cob4-2-t3-4]: ssh connection created
[cob4-2-t3-4] killing on exit
[cob4-2-s1-3] killing on exit
[cob4-2-t1-1] killing on exit
[cob4-2-t2-0] killing on exit
remote roslaunch failed to launch: cob4-1-h1
The traceback for the exception was written to the log file
from cob_robots.
I don't have a good solution yet, but maybe we could put the env.sh
from cob_bringup
into a folder that can be accessed by all users, e.g. /opt/care-o-bot
.
We would need to put this file there when setting up a PC afresh...or let the robot users install the env.sh
into this folder instead of into ${CATKIN_PACKAGE_SHARE_DESTINATION}
from cob_robots.
If I understood right , please @ipa-fmw correct me if I am wrong, the use of a 32 bits machine is temporal. The issue with the sound driver and 64 linux system should be solved soon. I don't think that make sense put effort on that. what about use for the moment the /opt/ros/indigo/env.sh
?? or the release version of cob_sound is out-of-date?
My upstart installation also create a env.sh file, that with a full cob installation will be copied to /etc/ros/$ROS_DISTRO/cob.d/setup/cob.d/setup/env.sh
for all the cob-pcs : https://github.com/ipa320/setup_cob4/blob/master/upstart/upstart_install.sh#L30 . But some modifications will be needed to use it. And from my point of view, is not nice use a global path (hardcoded) on cob_bringup....robot.xml
from cob_robots.
Has this been solved?
Still using the 32bit machine? What about user management?
@ipa-nhg please comment and close (if applicable)
from cob_robots.
in cob4-7 we're not using a 32-bit ubuntu on the head pc any more.
from cob_robots.
I guess then this can be closed...
from cob_robots.
It can be closed. Actually it is already done, it was needed in case that you source a different workspace and start something remotely, for further info see #537
from cob_robots.
Related Issues (20)
- cob4-7: head axis error HOT 8
- [Enhancement] Update xacro's according to latest syntax HOT 2
- Move base home offset configuration to cob_calibration_data
- Use CMake-Macro to retrieve sub-dir-list HOT 2
- Enable heartbeat producer for Schunk arms
- cob3-6 files missing HOT 6
- verify use of image_proc in indigo/kinetic HOT 1
- base_controller not running correctly in simulation HOT 10
- upload_robot.launch HOT 7
- cob3-2 tray not moving (0) HOT 7
- urdf_tutorial not compatible with the current cobs URDF (2) HOT 1
- review camera coordinate frames HOT 5
- [diagnostics_aggregator] fix aggregator groups for c++-based hz-monitor HOT 1
- Error while doing moveit setup assistance HOT 3
- cleanup after canopen migration of all robots using base_drive_chain
- use laser_filter pipeline for scanner HOT 20
- cob_bringup 0.6.11 in kinetic fails on debian builds HOT 3
- delete EOL robots and EOL packages HOT 12
- raw3-x :Costmap2DROS transform timeout and Could not get robot pose, cancelling reconfiguration
- Prepare cob4-25 for Noetic Upgrade HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cob_robots.