ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2017-10-04 08:28:38 -0500 | received badge | ● Favorite Question (source) |
2016-01-18 04:28:32 -0500 | received badge | ● Nice Answer (source) |
2015-06-29 19:42:13 -0500 | received badge | ● Nice Answer (source) |
2015-04-17 04:43:31 -0500 | commented question | Setting class method callback from within object (C++) Please post the calling code as well. |
2015-04-13 17:07:02 -0500 | received badge | ● Nice Answer (source) |
2015-04-13 16:10:08 -0500 | received badge | ● Self-Learner (source) |
2015-04-13 10:24:14 -0500 | received badge | ● Enthusiast |
2015-04-12 16:48:56 -0500 | received badge | ● Teacher (source) |
2015-04-12 16:41:35 -0500 | answered a question | Kinect v2 "No devices connected..." I've tried everything. I had the same issue with a kinect v1 and the freenect stack. Try to change the permissions of the usb bus |
2015-04-12 16:33:41 -0500 | answered a question | Indigo Installation, Environment setup The file /opt/ros/indigo/setup.bash is part of the package ros-indigo-catkin, make sure it is installed. That package is one of the most basic ones in ros, so I suppose something went wrong during installation and I advice you to purge ros (like mentioned in the answer before) and re-install ros. |
2015-04-12 14:14:25 -0500 | received badge | ● Editor (source) |
2015-04-12 14:05:02 -0500 | answered a question | ros on google nexus 5 Thank you for testing. Did you run apt-get upgrade or other updates on your phone? Are you sure the bind script is executed and /usr is mounted? The output shall look like: Is there a /usr/lib/python2.7/py_compile.py? To fix your system you could try: If that fails you could try What do you plan with the phone. Depending on your input I will improve the installation howto. |
2015-04-12 11:45:15 -0500 | received badge | ● Famous Question (source) |
2015-04-10 05:33:53 -0500 | answered a question | Start multiple nodes at boot and give access to ports You are addressing three different problems. First is system startup: To set permissions the clean way would be udev - rules. The quick way is change /etc/rc.local The next point is starting your ros nodes: take a look at the roslaunch documentation. And the last is start problem of your application on desktop level: I would create a bash script which starts two terminals (I suggest xterm, because it is quite easily scriptable) which automatically start roslaunch and another terminal with the python script. Depending on your desktop environment you can call the script at startup of the graphical system. |
2015-04-09 12:55:58 -0500 | received badge | ● Great Question (source) |
2015-04-09 12:42:23 -0500 | received badge | ● Notable Question (source) |
2015-04-08 23:15:06 -0500 | received badge | ● Good Question (source) |
2015-04-08 18:11:26 -0500 | received badge | ● Popular Question (source) |
2015-04-08 08:21:41 -0500 | received badge | ● Nice Question (source) |
2015-04-08 07:26:26 -0500 | received badge | ● Student (source) |
2015-04-08 07:18:29 -0500 | asked a question | ros on google nexus 5 Hi, I just installed ros on a google nexus 5 using Ubuntu touch as operation system for the phone. The results are currently promising, hence I like to share them. I wrote down the steps to perform and want to create a wiki page someday. Currently I have a running ros on the phone and can communicate with ros core (running remote control of the turtlesim on the phone). The next steps I like to add are:
Is there something I missed? What is interesting for you? Do you have technical remarks and hints, especially the hacks. Is there something to test? Regards, Georg Changelog:
Introduction This guide describes how to install ros on a google nexus 5 smartphone with Ubuntu touch. When the guide was written (15 / 04) I used the development version for Ubuntu phone (vivid). After installation android will be erased completely. I did not test the phone functionality of Ubuntu touch but suppose that LTE is working. The precondition for the installation is a working wireless environment with dhcp and a PC with installed Ubuntu (I used 14.10 utopic). Installation of Ubuntu touch on the phone First it is necessary to install Ubuntu Phone on the device. For installation I used the guide here [ https://developer.ubuntu.com/en/start... ] without big problems. To flash the device the following command sets the phone into developer mode and adds a password. Sometimes the flashing does not succeed and fails without error, when that happens it is necessary to retry the above command. If you are no developer yet make sure to get one and set your password (described in the how to above). The next step is to make the image on the phone writable. The device reboots and you can configure ssh. Enabling ssh: Copy your public key to the Phone: Now you can look up your IP on the phone and use ssh to connect: adb shell ip addr show wlan0|grep inet ssh phablet@ubuntu-phablet [or IP] You are ready to start the installation of ros: Installation of ros When you ssh on the phone it behaves like a normal Ubuntu vivid. Preparation of the device Unfortunately the partitions of the phone are unhandy for our purposes. The root partition has a size of about 2GB which is not sufficient to install ros. It was not possible to find a tidy way to re-size the root partition, hence I used the hack found here [ http://askubuntu.com/questions/514913... ], which copys /usr and /opt into the home partition and binds them ... (more) |
2015-04-06 20:54:02 -0500 | commented answer | Building indigo on 14.10 Using that trick dependency checking passed. Unfortunately gazebo is still missing for compilation hence it fails. I couldn't find a clean way to install gazebo using ubuntu tools (apt dependencies broken) so it was necessary to take it directly from http://gazebosim.org/ . Version 5 seems to work. |
2015-04-06 20:54:01 -0500 | answered a question | Building indigo on 14.10 I had some issues with the installation of the PCL. Adding the ppa solved it for me. |
2015-04-06 13:29:09 -0500 | received badge | ● Supporter (source) |