ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

HeZlah's profile - activity

overview network karma followed questions activity
2018-08-08 01:43:46 -0500 received badge ● Famous Question (source)
2018-07-27 14:58:44 -0500 received badge ● Famous Question (source)
2018-07-27 14:58:44 -0500 received badge ● Notable Question (source)
2018-07-27 14:58:44 -0500 received badge ● Popular Question (source)
2018-07-16 15:07:48 -0500 received badge ● Famous Question (source)
2018-07-16 15:07:48 -0500 received badge ● Notable Question (source)
2017-06-27 10:48:30 -0500 received badge ● Notable Question (source)
2017-06-22 00:35:19 -0500 received badge ● Famous Question (source)
2017-06-02 12:41:22 -0500 received badge ● Popular Question (source)
2017-04-27 06:21:14 -0500 asked a question Where on the kinect does camera_link refer to?

Where on the kinect does camera_link refer to? I have my kinect setup on my robot using openni and gmapping. Everything

2017-04-21 00:38:30 -0500 received badge ● Enthusiast
2017-04-20 08:03:40 -0500 edited question freenect_launch fails on kinetic installed from source raspberryPi/Jessie

freenect_launch fails on kinetic installed from source raspberryPi/Jessie HI all, I have found a bunch of other similar
2017-04-20 08:00:04 -0500 edited question freenect_launch fails on kinetic installed from source raspberryPi/Jessie

freenect_launch fails on kinetic installed from source raspberryPi/Jessie HI all, I have found a bunch of other similar
2017-04-20 07:59:08 -0500 edited question freenect_launch fails on kinetic installed from source raspberryPi/Jessie

freenect_launch fails on kinetic installed from source raspberryPi/Jessie HI all, I have found a bunch of other similar
2017-04-20 07:53:39 -0500 edited question freenect_launch fails on kinetic installed from source raspberryPi/Jessie

freenect_launch fails on kinetic installed from source raspberryPi/Jessie HI all, I have found a bunch of other similar
2017-04-20 07:41:59 -0500 asked a question freenect_launch fails on kinetic installed from source raspberryPi/Jessie

freenect_launch fails on kinetic installed from source raspberryPi/Jessie HI all, I have found a bunch of other similar
2017-04-19 08:47:03 -0500 received badge ● Popular Question (source)
2017-04-15 23:04:59 -0500 commented answer Best way to add new package to ROS that was installed from source (rosinstall_generator)

And then sudo ./src/catkin/bin/catkin_make_isolated --install -DCMAKE_BUILD_TYPE=Release --install-space, and it should build and install only newpackage?
2017-04-15 23:03:27 -0500 commented answer Best way to add new package to ROS that was installed from source (rosinstall_generator)

Weird, I don't know why it always rebuilds everything then..So I should be able to : rosinstall_generator newpackage --deps --exclude RPP | wstool merge -t src - then wstool update -t src
2017-04-15 21:52:19 -0500 asked a question Best way to add new package to ROS that was installed from source (rosinstall_generator)

HI all,

I have built ROS kinetic from source on my pi using the instructions http://wiki.ros.org/ROSberryPi/Instal...

What is the best way for me to install an additional package without needing to recompile the entire workspace? The last section in the installation guide describes how to add additional packages, however that just adds them to the workspace and then catkin make will rebuild everything.

The rosinstall_generator page makes it clear how I can generate a rosinstall file for packages not in the current environment (I guess this is what I want?) however this just adds them to the workspace and again, catkin make rebuilds everything.

So is there a way to get catkin_make_isolated to just build and install new packages? Or should I be creating a new workspace and use the --exclude RPP to get the new packages I want to install? The latter sounds messy, I would rather just have one workspace with my entire build.
2017-04-05 07:39:12 -0500 commented answer [Solved]Can not launch a remote node from launch file

This is absolutely correct, solution is edited into original post. And yes I would usually use (and am now) absolute paths. That path was just an artifact of my frustrated debugging.

Thanks for your help!
2017-04-05 07:36:34 -0500 commented question [Solved]Can not launch a remote node from launch file

Yes, it is exactly what you wrote and you lead me to my solution. Thank you! I solved it at the last minute before I went off on business and wrote the [solved] update to my post on mobile-- It was being a pain and would not let my mark your post as the correct answer. That is fixed now. Thanks!
2017-04-05 07:32:29 -0500 received badge ● Supporter (source)
2017-04-05 07:32:27 -0500 received badge ● Scholar (source)
2017-04-05 07:32:16 -0500 received badge ● Notable Question (source)
2017-04-04 09:34:53 -0500 received badge ● Popular Question (source)
2017-04-04 09:29:59 -0500 received badge ● Editor (source)
2017-03-30 08:47:37 -0500 asked a question [Solved]Can not launch a remote node from launch file

EDIT: SOLVED

In .bashrc I had

export ROS_IP=`hostname -I`

which apparently puts a space after the IP. So that caused the IP and port to be split into two.

Hi all,

I am having troubles launching a remote node from a launch file. I have a raspberry pi based mobile robot, which runs a node responsible for setting velocities and publishing encoder odometer (wheel_motor_controller_node).

I would like to start this node from a launch file on my Ubuntu 16.04 machine. The launch file looks like this:

<launch>

<machine name="rosPi" address="192.168.1.32" env-loader="~/ch-bot_ws/devel/env.sh" user="pi" />

<param name="ch_bot_model" command="xacro '$(find ch_bot_description)/urdf/ch_bot.xacro'" />

<node machine="rosPi" pkg="ch_bot" name="wheel_motor_controller_node" type="wheel_motor_controller_node" />

</launch>

However I get a weird error, as if it is trying to pass the ssh port in as a launch file or something:

roslaunch ch_bot_description launch.launch
... logging to /home/hez/.ros/log/e4cd3d32-12ce-11e7-bad8-b827eb948adf/roslaunch-hez-VirtualBox-18713.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.

xacro: Traditional processing is deprecated. Switch to --inorder processing!
To check for compatibility of your document, use option --check-order.
For more infos, see http://wiki.ros.org/xacro#Processing_Order
started roslaunch server http://192.168.1.5 :39884/
remote[192.168.1.32-0] starting roslaunch
remote[192.168.1.32-0]: creating ssh connection to 192.168.1.32:22, user[pi]
/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://192.168.1.32:11311 ~/ch-bot_ws/devel/env.sh roslaunch -c 192.168.1.32-0 -u http://192.168.1.5 :39884/ --run_id e4cd3d32-12ce-11e7-bad8-b827eb948adf]
remote[192.168.1.32-0]: ssh connection created
remote[192.168.1.32-0]: [:39884/] is not a launch file name
The traceback for the exception was written to the log file

[192.168.1.32-0] killing on exit
remote roslaunch failed to launch: rosPi
The traceback for the exception was written to the log file

My env.sh looks like this:

#!/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. Inste$
  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"
#. ~/ch-bot_ws/devel/setup.sh
exec "$@"

Note I tried replacing the entire env.sh with the commented line before the exec, just to make sure it was running the correct setup.

I think I have done something wrong in the launch file.. But I have no idea what. It seems to look like all of the examples and tutorials I have seen - albeit minimal.

Any help would be greatly ... (more)
2016-04-24 06:05:03 -0500 asked a question Moving a package from one machine to another

I have seen a few similar questions around however none that help me.

I have created a package on one machine, now I wish to move it to another machine however I am not sure what is required to do so. I originally created the package using catkin_create_pkg.

I have copied the package from /src on the current machine to /src on the new machine. catkin_make successfully builds the package.

However no ros commands can see the package (roscd, rosrun, etc)

I have my environment sourced correctly. I can create new packages using catkin_create_pkg in the same /src directory and they work.

Is there something that catkin_create_pkg does outside the /src folder, or is there something else I need to change in my package to make it portable? I have seen many install instructions just say to just clone a git repo into /src and then catkin_make.
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.
about | faq | help | privacy policy | terms of service
Powered by Askbot version 0.10.2