Quantcast
Channel: ROS Answers: Open Source Q&A Forum - RSS feed
Viewing all 598 articles
Browse latest View live

Running cuda-memcheck on nodelets

$
0
0
Has anyone successfully managed to run `cuda-memcheck` on a nodelet project? I have: `cuda-memcheck` starts, but then on the first: I get an error. My output looks like this: ============ CUDA-MEMCHECK [INFO] [timestamp]: Initializing nodelet with 8 worker threads. [nodelet_dir/my_nodelet] escalating to SIGTERM How can one get this to work? My nodelets work fine without `cuda-memcheck`.

roslaunch Python arg substitution finds wrong package folder path?

$
0
0
I've recently played around with [Python expressions as substitution args in launch files](http://wiki.ros.org/roslaunch/XML#substitution_args) (on 16.04 AMD64/Kinetic/current .debs). I encountered a curious problem during doing so. When trying to generalize this line: the following expression works: However, it has to be noted that I have to use the deprecated `xacro.py` here, as the `xacro` executable is not found. Investigating further I noted that $(find xacro) returns `/opt/ros/kinetic/lib/xacro` as a path, where also the `xacro` executable is located. In contrast to this $(eval find('xacro')) returns `/opt/ros/kinetic/share/xacro` as a path, where only the `xacro.py` executable is located. My expectation was that both calls to find should work identically, but apparently, this is not the case. My questions hence are: - Is this expected behavior or a bug? - Is there some other way to get to the "right" folder with the `xacro` executable while using Python substitution args in roslaunch?

Problem with GP7 MotoROS

$
0
0
Hi, I am new with ROS. I am currently using a GP7 robot and a YRC1000 controller, and following the tutorial I got a problem. All steps worked, until the 2.Usage. I followed all the steps, even changing the joint_names but when I do the roslaunch, i got this error : started roslaunch server http://ubuntu:40354/ SUMMARY ======== PARAMETERS * /robot_ip_address: 192.168.255.1 * /rosdistro: indigo * /rosversion: 1.11.21 NODES / joint_state (motoman_driver/robot_state) joint_trajectory_action (industrial_robot_client/joint_trajectory_action) motion_streaming_interface (motoman_driver/motion_streaming_interface) auto-starting new master process[master]: started with pid [8664] ROS_MASTER_URI=http://localhost:11311 setting /run_id to 726dbf1c-956a-11e8-9786-000c293ae231 process[rosout-1]: started with pid [8677] started core service [/rosout] process[joint_state-2]: started with pid [8691] process[motion_streaming_interface-3]: started with pid [8695] process[joint_trajectory_action-4]: started with pid [8696] [ERROR] [1533114505.924699714]: Failed to find topic_list parameter [ERROR] [1533114505.962896918]: Failed to find topic_list parameter I am confused with the urdf file, because when i change the joint names, with the 2.1 Joint Naming from the tutorial, it seems like nothing is changing. In addition I can ping the robot, and I try to do the tricks from "Support Motoman Yaskawa gp-7 model" Thank you for your help

Roslaunch cannot locate rtamap node (Kinetic/jetsontx2)

$
0
0
I'm new in ROS and have installed rtabmap and rtamap-ros via apt in a jetsonTx2. i did a launch file with the zed wrapper, my package and the rtabmap-ros and it can not locate the node. This is the launch file: Then i ran the launch file without the zed_wrapper and my package and the problem still "alive". This is the terminal output: ERROR: cannot launch node of type [rtabmap_ros/rtabmap]: can't locate node [rtabmap] in package [rtabmap_ros] ERROR: cannot launch node of type [rtabmap_ros/rtabmapviz]: can't locate node [rtabmapviz] in package [rtabmap_ros] when i run it like the [tutorial](http://wiki.ros.org/rtabmap_ros/Tutorials/HandHeldMapping) or type in the terminal: $roscore $rosrun rtabmap_ros rtabmap i don't have problems. in the last line of my .bashrc i have source /opt/ros/kinetic/setup.bash and in the new terminal i do: ~/foo/catkin_ws$ source devel/setup.bash

Running a raspberry pi(wiring pi) node with roslaunch

$
0
0
I am having trouble to run a node present in /ros_workspace/devel/lib/blink where blink is the package and this directory contains the blink executable, this executable is ran with root permission, I dont understand the work around with roslaunch with such files. How can I run this with one roslaunch with other nodes in the bot. Please let me know any other info that maybe needed to solve this. thank you.

Gazebo9 Ros Melodic

$
0
0
Hello I have a gazebo launch problem I wanted to launch my_model_world.launch It should open gazebo with my robot model and everything looks ok in gazebo but terminal shows: [ERROR] [1534163227.741349859]: SpawnModel: Failure - model name my_model already exist. I'm new in ROS and I don't know what is going on

roscd can't find packages

$
0
0
hi , i'm using ros indigo and suddenly after reboot my pc i can't run some package , for example when i try to type : "roscd turtle " and use the tab touch keyboard it gives only these packages turtle_actionlib/ turtlebot_description/ turtle_tf/ turtlebot_capabilities/ turtlesim/ turtle_tf2/ so why it can't detect turtlbot_teleop and other packages ?

respawn parameter problem

$
0
0
Hi I am starting my launchfiles using this tutorial http://wiki.ros.org/roslaunch/API%20Usage (Part2). I have problem when I configured node parameter respawn = True in my launch file. Launch is not able to respawn node automatically when node is shutdown. I don't think this is normal behavior. Thank you for your help.

How to launch a node with it's dependencies have started

$
0
0
I have 5 launch file. Some node must start when some nodes have started , or they cannot work. If all the nodes are written by myself, it is easy to deal with. But now, I use some packages like moveit, whose code is not in my workspace and I donnot want to rewrite it : https://github.com/ros/ros_comm/issues/1491#issuecomment-414695741

roslaunch via gdb not working

$
0
0
Hi I am trying to run roslaunch with gdb I followed the instructions in [here](http://wiki.ros.org/roslaunch/Tutorials/Roslaunch%20Nodes%20in%20Valgrind%20or%20GDB) and changed from: to I'm getting an error RLException: Roslaunch got a No such file or directory error while attempting to run gdb -ex run --args /home/avnerm/catkin_ws/devel/lib/my_mapping/my_mapping_node __name:=my_mapping_node __log:=/home/avnerm/.ros/log/bf9af474-a593-11e8-b43e-74d02b912ce1/my_mapping_node-1.log Please make sure that all the executables in this command exist and have executable permission. This is often caused by a bad launch-prefix When I run the gdb command directly from the terminal the program runs ok., e.g. gdb -ex run --args /home/avnerm/catkin_ws/devel/lib/my_mapping/rm_mapping_node __name:=rm_mapping_node So I assume it is some setting that is needed for roslaunch I tried setting "`export ROS_HOSTNAME=localhost`" as recommended in one of the sites but this didn't help. How can I run roslaunch via gdb? Thanks, Avner

Introduction to tf tutorial: Second turtle does not follow the first one. (No errors)

$
0
0
I've been following http://wiki.ros.org/tf/Tutorials/Introduction%20to%20tf - I started with installing everything with the following command: $ sudo apt-get install ros-kinetic-ros-tutorials ros-kinetic-geometry-tutorials ros-kinetic-rviz ros-kinetic-rosbash ros-kinetic-rqt-tf-tree Luckily everything was already installed and I got this output: Reading package lists... Done Building dependency tree Reading state information... Done ros-kinetic-geometry-tutorials is already the newest version (0.2.2-0xenial-20180809-184418-0800). ros-kinetic-ros-tutorials is already the newest version (0.7.1-0xenial-20180809-153903-0800). ros-kinetic-rosbash is already the newest version (1.14.3-0xenial-20180809-134025-0800). ros-kinetic-rqt-tf-tree is already the newest version (0.5.8-0xenial-20180809-162041-0800). ros-kinetic-rviz is already the newest version (1.12.16-0xenial-20180809-192423-0800). The following package was automatically installed and is no longer required: python-libxml2 Use 'sudo apt autoremove' to remove it. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Now, when I launch `roslaunch turtle_tf turtle_tf_demo.launch` - I get no errors or warnings: ... logging to /home/snowden/.ros/log/3f67ef12-a810-11e8-bcd4-8ca982221578/roslaunch-snowden-Inspiron-N5010-17760.log Checking log directory for disk usage. This may take awhile. Press Ctrl-C to interrupt Done checking log file disk usage. Usage is <1GB. started roslaunch server http://snowden-Inspiron-N5010:41377/ SUMMARY ======== PARAMETERS * /rosdistro: kinetic * /rosversion: 1.12.13 * /scale_angular: 2.0 * /scale_linear: 2.0 * /turtle1_tf_broadcaster/turtle: turtle1 * /turtle2_tf_broadcaster/turtle: turtle2 NODES / sim (turtlesim/turtlesim_node) teleop (turtlesim/turtle_teleop_key) turtle1_tf_broadcaster (turtle_tf/turtle_tf_broadcaster.py) turtle2_tf_broadcaster (turtle_tf/turtle_tf_broadcaster.py) turtle_pointer (turtle_tf/turtle_tf_listener.py) ROS_MASTER_URI=http://localhost:11311 process[sim-1]: started with pid [17777] process[teleop-2]: started with pid [17778] process[turtle1_tf_broadcaster-3]: started with pid [17779] process[turtle2_tf_broadcaster-4]: started with pid [17786] process[turtle_pointer-5]: started with pid [17795] Reading from keyboard --------------------------- Use arrow keys to move the turtle. After a brief moment, the second turtle revolves a little bit: ![C:\fakepath\turtle.gif](/upfiles/15351936242633419.gif) According to the tutorial, if I start moving the first turtle, the second turtle should follow it, but as visible in the GIF, nothing happens, it just stays as is. FWIW, my `turtle_tf_demo.launch` file looks like this: I'm running ROS Kinetic on Xubuntu 16.04 LTS (xenial). Here is the output of `env | grep 'ROS'`: ROS_DISTRO=kinetic ROS_ETC_DIR=/opt/ros/kinetic/etc/ros ROS_PACKAGE_PATH=/home/snowden/catkin_ws/src/beginner_tutorials:/home/snowden/catkin_ws/src/husky_highlevel_controller:/home/snowden/catkin_ws/src/ros_best_practices/ros_package_template:/home/snowden/catkin_ws/src/teleop_twist_keyboard:/opt/ros/kinetic/share ROS_VERSION=1 ROS_ROOT=/opt/ros/kinetic/share/ros ROS_MASTER_URI=http://localhost:11311 ROSLISP_PACKAGE_DIRECTORIES=/home/snowden/catkin_ws/devel/share/common-lisp Also, I'd be around if you need any more info. Is there something wrong on my side? Thanks in advance! :-)

roslaunch terminal split screen

$
0
0
Hello, i am launching over a launch file several nodes in new shells as shown here: I wanna start the first two nodes in a terminal with splitted view, but was not able to do so with guake, byobu, yakuake or screen, since they do have just shortcuts to split the screens. Does somebody have suggestion or encountered a similar challenge? Thank you very much! Michael

rosversion error when trying to run roscore

$
0
0
Hello, when I try to run the roscore or start my project launch file I get the following error: ... logging to /home/nvidia/.ros/log/1c5e18a0-aae7-11e8-8e0e-00044b8d24bd/roslaunch-tegra-ubuntu-30432.log Checking log directory for disk usage. This may take awhile. Press Ctrl-C to interrupt Done checking log file disk usage. Usage is <1GB. Traceback (most recent call last): File "/usr/local/bin/rosversion", line 7, in from rospkg.rosversion import main ImportError: No module named rosversion Invalid tag: Cannot load command parameter [rosversion]: command [rosversion roslaunch] returned with code [1]. Param xml is The traceback for the exception was written to the log file The ROS environment variables command `env | grep ROS` gives me the following: ROS_ROOT=/opt/ros/kinetic/share/ros ROS_PACKAGE_PATH=/home/nvidia/EVObot/src:/opt/ros/kinetic/share ROS_MASTER_URI=http://localhost:11311 ROSLISP_PACKAGE_DIRECTORIES=/home/nvidia/EVObot/devel/share/common-lisp ROS_DISTRO=kinetic ROS_ETC_DIR=/opt/ros/kinetic/etc/ros The `rosversion -d` command gives me the same error but actually on ROS Hydro 1.12.13. The strange thing is, I did not change anything ROS related and it worked correctly before the strange error. It seems there is a problem with the rosversion-file but it contains the following code: #!/usr/bin/python2.7 # -*- coding: utf-8 -*- import re import sys from rospkg.rosversion import main if __name__ == '__main__': sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0]) sys.exit(main()) I'm grateful for any help!

Respawn entire launch file

$
0
0
Hi all, I learned that respawn Tag in a launch file lets a single node being restarted if it crashes. Further, the required tag if set true, stops the entire launch if a particular important node closes. Is it also possible to respawn all nodes in a launch file if a particular important node closes and needs to geht respawned? Thank you for your Help.

roslaunch and NVidia profiling

$
0
0
Has anyone had any success getting NVidia profiling tools and ROS to play well together? At the moment, the best I can do is profile all processes, but that only reports memory copies to and from host, and some OpenCV (copy to and from `cv::Mat` and `cv::cuda::GpuMat`). My custom kernels are never profiled (yes, I have explicit `cudaProfilerStart()/Stop()` calls) and trying to use `launch-prefix="nvprof"` or directly profiling `roslaunch` never gets me anywhere except errors about being unable to load some nodelets. Any suggestions as to what I might be doing wrong? I'm on Ubuntu 16.04.

i have rplidar a3 launch error(error code -6)

$
0
0
I have an error for rplidar a3. SUMMARY ======== PARAMETERS * /rosdistro: indigo * /rosversion: 1.11.21 * /rplidarNode/angle_compensate: True * /rplidarNode/frame_id: laser * /rplidarNode/inverted: False * /rplidarNode/scan_mode: Sensitivity * /rplidarNode/serial_baudrate: 256000 * /rplidarNode/serial_port: /dev/ttyUSB0 NODES / rplidarNode (rplidar_ros/rplidarNode) rviz (rviz/rviz) auto-starting new master process[master]: started with pid [4082] ROS_MASTER_URI=http://localhost:11311 setting /run_id to e480e554-b499-11e8-80d3-e0d55eaaa97a process[rosout-1]: started with pid [4095] started core service [/rosout] process[rplidarNode-2]: started with pid [4103] process[rviz-3]: started with pid [4113] [ INFO] [1536543369.462962123]: RPLIDAR running on ROS package rplidar_ros. SDK Version:1.7.0 RPLIDAR S/N: 6BF39AF2C1EA9FC0A2EB92F1F8203C02 [ INFO] [1536543369.966742531]: Firmware Ver: 1.24 [ INFO] [1536543369.966776559]: Hardware Rev: 6 [ INFO] [1536543369.967689753]: RPLidar health status : 0 [ INFO] [1536543370.582106429]: current scan mode: Sensitivity, max_distance: 25.0 m, Point number: 15.9K , angle_compensate: 4 terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc [rplidarNode-2] process has died [pid 4103, exit code -6, cmd /opt/ros/indigo/lib/rplidar_ros/rplidarNode __name:=rplidarNode __log:=/home/ksj/.ros/log/e480e554-b499-11e8-80d3-e0d55eaaa97a/rplidarNode-2.log]. log file: /home/ksj/.ros/log/e480e554-b499-11e8-80d3-e0d55eaaa97a/rplidarNode-2*.log It is the same error as above. Please provide a solution to this problem. Thank you.

Files not found when launching from remote PC

$
0
0
When trying to use a launchfile to launch ROS nodes on two seperate machines, the remote PC cannot find the files I want to launch. I have also installed both packages on both machines for testing purpouses. The files is can be launched on both PC's, but when I try to launch them remotely, they're not found. I have looked at a lot of other people using ROS on two machines, but I cannot seem to find any solution to this problem. Any suggestions/help is appreciated. All necessary files is listed below. EDIT: I have tried launching the turtlesim teleop node on the remote PC, a node that is native in ROS. This works with no problem, so the problem lies in custom made nodes. EDIT: Added the "printenv" variables from manually **Main launch file** **hosts.machine** The file structure is identical on the two machines, and both env.sh files is located at the same location. **env.sh on tegra_a** #!/usr/bin/env sh # generated from catkin/cmake/templates/env.sh.in if [ $# -eq 0 ] ; then /bin/echo "Usage: env.sh COMMANDS" /bin/echo "Calling env.sh without arguments is not supported anymore. Instead spawn a subshell and source a setup file manually." exit 1 fi # ensure to not use different shell type which was set before CATKIN_SHELL=sh # source setup.sh from same directory as this file _CATKIN_SETUP_DIR=$(cd "`dirname "$0"`" > /dev/null && pwd) . "$_CATKIN_SETUP_DIR/setup.sh" export ROS_WS=/home/nvidia/catkin_ws export ROS_KINETIC=/etc/ros/kinetic source $ROS_WS/devel/setup.bash source $ROS_KINETIC/setup.bash export PATH=$ROS_ROOT/bin:$PATH export ROS_PACKAGE_PATH=$ROS_PACKAGE_PATH:$ROS_WS export ROS_MASTER_URI=http://10.42.0.28:11311/ export ROS_HOSTNAME=10.42.0.28 exec "$@" **env.sh on tegra_b** #!/usr/bin/env sh # generated from catkin/cmake/templates/env.sh.in if [ $# -eq 0 ] ; then /bin/echo "Usage: env.sh COMMANDS" /bin/echo "Calling env.sh without arguments is not supported anymore. Instead spawn a subshell and source a setup file manually." exit 1 fi # ensure to not use different shell type which was set before CATKIN_SHELL=sh # source setup.sh from same directory as this file _CATKIN_SETUP_DIR=$(cd "`dirname "$0"`" > /dev/null && pwd) . "$_CATKIN_SETUP_DIR/setup.sh" export ROS_WS=/home/nvidia/catkin_ws export ROS_KINETIC=/etc/ros/kinetic source $ROS_WS/devel/setup.bash source $ROS_KINETIC/setup.bash export PATH=$ROS_ROOT/bin:$PATH export ROS_PACKAGE_PATH=$ROS_PACKAGE_PATH:$ROS_WS export ROS_MASTER_URI=http://10.42.0.28:11311/ export ROS_HOSTNAME=10.42.0.29 exec "$@" **Output when launching the launchfile** nvidia@nvidia:/opt/ros/kinetic$ roslaunch r18dv_tf_publisher test_launch.launch ... logging to /home/nvidia/.ros/log/3dfcc3a4-fba0-11e7-8f39-00044b8da45f/roslaunch-nvidia-8089.log Checking log directory for disk usage. This may take awhile. Press Ctrl-C to interrupt Done checking log file disk usage. Usage is <1GB. started roslaunch server http://10.42.0.28:33233/ remote[10.42.0.29-0] starting roslaunch remote[10.42.0.29-0]: creating ssh connection to 10.42.0.29:22 /usr/lib/python2.7/dist-packages/Crypto/Cipher/blockalgo.py:141: FutureWarning: CTR mode needs counter parameter, not IV self._cipher = factory.new(key, *args, **kwargs) launching remote roslaunch child with command: [env ROS_MASTER_URI=http://10.42.0.28:11311/ /opt/ros/kinetic/env.sh roslaunch -c 10.42.0.29-0 -u http://10.42.0.28:33233/ --run_id 3dfcc3a4-fba0-11e7-8f39-00044b8da45f] remote[10.42.0.29-0]: ssh connection created SUMMARY ======== PARAMETERS * /rosdistro: kinetic * /rosversion: 1.12.12 MACHINES * tegra_a * tegra_b NODES / heading_controller (r18dv_simple_heading_controller/r18dv_simple_heading_controller_node) tf_broadcaster (r18dv_tf_publisher/tf_broadcaster) auto-starting new master process[master]: started with pid [8104] ROS_MASTER_URI=http://10.42.0.28:11311/ setting /run_id to 3dfcc3a4-fba0-11e7-8f39-00044b8da45f process[rosout-1]: started with pid [8117] started core service [/rosout] process[tf_broadcaster-2]: started with pid [8128] [10.42.0.29-0]: launching nodes... [10.42.0.29-0]: ROS_MASTER_URI=http://10.42.0.28:11311/ [10.42.0.29-0]: ERROR: cannot launch node of type [r18dv_simple_heading_controller/r18dv_simple_heading_controller_node]: can't locate node [r18dv_simple_heading_controller_node] in package [r18dv_simple_heading_controller] [10.42.0.29-0]: ... done launching nodes **printenv when manually ssh'ing into tegra_b:** XDG_SESSION_ID=1 TERM=xterm-256color SHELL=/bin/bash ROS_ROOT=/opt/ros/kinetic/share/ros SSH_CLIENT=10.42.0.28 51856 22 ROS_PACKAGE_PATH=/home/nvidia/catkin_ws/src:/opt/ros/kinetic/share ROS_MASTER_URI=http://10.42.0.28:11311 SSH_TTY=/dev/pts/4 USER=nvidia LD_LIBRARY_PATH=/usr/lib:/usr/lib/aarch64-linux-gnu LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36: MAIL=/var/mail/nvidia PATH=/opt/ros/kinetic/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin QT_QPA_PLATFORMTHEME=appmenu-qt5 PWD=/home/nvidia/Documents LANG=en_US.UTF-8 ROSLISP_PACKAGE_DIRECTORIES=/home/nvidia/catkin_ws/devel/share/common-lisp SHLVL=1 HOME=/home/nvidia ROS_DISTRO=kinetic PYTHONPATH=/home/nvidia/catkin_ws/devel/lib/python2.7/dist-packages:/opt/ros/kinetic/lib/python2.7/dist-packages LOGNAME=nvidia ROS_IP=10.42.0.29 SSH_CONNECTION=10.42.0.28 51856 10.42.0.29 22 PKG_CONFIG_PATH=/home/nvidia/catkin_ws/devel/lib/pkgconfig:/opt/ros/kinetic/lib/pkgconfig LESSOPEN=| /usr/bin/lesspipe %s CMAKE_PREFIX_PATH=/home/nvidia/catkin_ws/devel:/opt/ros/kinetic XDG_RUNTIME_DIR=/run/user/1001 LESSCLOSE=/usr/bin/lesspipe %s %s XAUTHORITY=/home/nvidia/.Xauthority ROS_ETC_DIR=/opt/ros/kinetic/etc/ros _=/usr/bin/printenv OLDPWD=/home/nvidia **printenv in the env.sh file on the tegra_b:** MAIL=/var/mail/nvidia SSH_CLIENT=10.42.0.28 53326 22 USER=nvidia ROS_PACKAGE_PATH=/opt/ros/kinetic/share:/home/nvidia/catkin_ws/src SHLVL=1 LD_LIBRARY_PATH=/opt/ros/kinetic/lib:/opt/ros/kinetic/lib ROS_ETC_DIR=/opt/ros/kinetic/etc/ros HOME=/home/nvidia ROS_IP=10.42.0.29 ROS_DISTRO=kinetic LOGNAME=nvidia _=/usr/bin/env PKG_CONFIG_PATH=/opt/ros/kinetic/lib/pkgconfig XDG_SESSION_ID=9 PATH=/opt/ros/kinetic/share/ros/bin:/opt/ros/kinetic/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games XDG_RUNTIME_DIR=/run/user/1001 LANG=en_US.UTF-8 ROS_ROOT=/opt/ros/kinetic/share/ros ROSLISP_PACKAGE_DIRECTORIES= ROS_KINETIC=/etc/ros/kinetic SHELL=/bin/bash ROS_WS=/home/nvidia/catkin_ws ROS_MASTER_URI=http://10.42.0.28:11311/ PWD=/home/nvidia SSH_CONNECTION=10.42.0.28 53326 10.42.0.29 22 PYTHONPATH=/opt/ros/kinetic/lib/python2.7/dist-packages CMAKE_PREFIX_PATH=/opt/ros/kinetic

Adding arguments via command line during roslaunch

$
0
0
Hi! I want to add command line arguments while calling my launch file in the bash, just like how I add it while running the node via rosrun. For eg. `rosrun pkg_name executable_name /home/user/Documents/my_file.yml /home/user/Pictures/` The closest answer I found to solve my problem was [this](https://answers.ros.org/question/277622/roslaunch-command-line-args/). My launch file looks like this and the command looks like this `roslaunch launch_file.launch my_args:="/home/user/Documents/my_file.yml" ` However, I get the following error: `Invalid roslaunch XML syntax: not well-formed (invalid token): line 3, column 90 The traceback for the exception was written to the log file`. I also wanted to know how can I access these command line arguments in my python script. Is it just sys.argv[0]? I also have another c++ node which needs command line arguments. So, in short, I want to launch these two nodes with the respective command line arguments. I would be really thankful if someone could provide an example launch file to solve the above problem. Thanks!

roslaunch command line args

$
0
0
Read through all the tutorials, but couldn't find the answer to this one. I have a ROS node executable, which I can run like this:> ./my_node -arg1 -arg2 I can also start it using roslaunch and a my_launch.launch file: > roslaunch my_launch.launch How do I specify arg1 and arg2 when starting using roslaunch? I.e. how do I get arg1 and arg2 to show up in argc and argv?

Reading vector from launch file does not work in Indigo

$
0
0
Hi to all, I'm facing an issue while reading a vector parameter from launch file in ROS Indigo. I set the parameter in my launch file in the private namespace of my node as; And I'm trying to read it as described [here](http://wiki.ros.org/roscpp/Overview/Parameter%20Server#Retrieving_Lists) or [in this previous answer](https://answers.ros.org/question/206146/arrays-ros-launch-file/): ros::NodeHandle nh("~"); std::vector x0; nh.getParam("x0", x0); but if I try to print the size of the vector it tells me 0. From the [roslaunch param documentation](http://wiki.ros.org/roslaunch/XML/param) it seems that parameters which are not scalar numbers or literal booleans are interpreted as strings. Why is there such inconsistency between the types that I can read from the parameter server and the parameters that I can set from a launch file? How can I solve this problem? Thanks to all in advance.
Viewing all 598 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>