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 |
| 2012-09-12 21:43:01 -0500 | received badge | ● Famous Question (source) |
| 2012-09-12 21:43:01 -0500 | received badge | ● Notable Question (source) |
| 2012-02-03 12:52:39 -0500 | received badge | ● Popular Question (source) |
| 2011-12-17 11:58:56 -0500 | answered a question | (Turtlebot) Easier way to check power button status of iRobot Create I have also found that the LED near the power button to not be a reliable power status indicator. It's very easy to add a real power on/off status LED by connecting an LED to the cargo bay connector pin 8 (switched 5VDC) and pin 21 (ground). Be sure to also add a resistor (180ohm to 330 ohm) in series with the the LED to limit current to, and protect the LED. |
| 2011-12-17 11:06:13 -0500 | commented question | Android Control not working after upgrading to Electric-Turtle Fergs, I just received a bunch of ros-electric-turtle updates via apt and was surprised to that your android_teleop changes were not included in the updates. |
| 2011-12-11 10:15:08 -0500 | marked best answer | Android Control not working after upgrading to Electric-Turtle The "base.launch" file previously started the EKF filter (which would publish /odom->/base_link transfrom). That launch file has been merged into minimal.launch (as that transform is needed very often, and we were trying to reduce the number of launch files). It looks like a number of launch files in the /apps directory didn't get updated, I'll get those patches pushed into mercurial tomorrow. The lack of movement, is probably due to a different change: we've stopped mapping "cmd_vel" into "turtlebot_node/cmd_vel" as it's really the wrong thing to do. So, it is likely that turtlebot_node/cmd_vel is still running around somewhere (although I can't seem to find it). In the meantime, you should be able make this work with a relay: UPDATE: As of today, 12/05, changes have been committed to the turtlebot_apps stack which shuold fix this problem. |
| 2011-12-11 02:28:21 -0500 | commented question | Android Control not working after upgrading to Electric-Turtle Fergs, thanks for your answers. After restarting everything the chirp app is now working. As for Teleop, I'm pretty sure that it's not a breaker issue as the in-line green LED on cord of the Kinect toggles and the "Follower" application works. |
| 2011-12-09 13:13:14 -0500 | commented answer | Android Control not working after upgrading to Electric-Turtle Never mind... I found your changes and figured out how to get the turtlebot_apps source via mercurial. |
| 2011-12-09 12:18:24 -0500 | commented answer | Android Control not working after upgrading to Electric-Turtle I installed electric from source, source setup.bash and ran rosmake -a. I'm still seeing the same error and base.launch is still being included in android_teleop.launch. I'm now guessing that rosinstall does not pull from the mercurial repo. Is there a way to tell it to do so? |
| 2011-12-02 13:22:19 -0500 | commented answer | Android Control not working after upgrading to Electric-Turtle Thanks. I will give it a try tomorrow. |
| 2011-11-28 13:12:47 -0500 | answered a question | Android Control not working after upgrading to Electric-Turtle I just tried your (Fergs) recommendation of using relay but I still get no motion. Displays cmd_vel values as you expected. Currently where to change /turtlebot_node/cmd_vel to /cmd_vel eludes me. Also, will your update be available via apt-get or do I need to go another route to pickup such changes? |
| 2011-11-27 05:08:52 -0500 | asked a question | Android Control not working after upgrading to Electric-Turtle Is it just me or does the Android Control not work after upgrading to Electric-Turtle? Below are the relevant sections of the logs and messages from me launching android_teleop.launch from the command line. Removing the follow offending line "<include file="$(find turtlebot_bringup)/base.launch"/>" from android_teleop.launch gets me a bit further. The android_teleop application now successfully launches and Kinect camera works but I can not navigate around using the controls. It seems that turtlebot_bringup/base.launch no longer exists in Electric. Was it just removed, renames or replaced? Please let me know if I should create a ticket for this under turtlebot_apps and if there is anything else that I can do. James Ronald while processing /opt/ros/electric/stacks/turtlebot/turtlebot_bringup/base.launch: Update: I installed electric-turtle from source and replaced turtlebot_apps with turtlebot_apps from mercurial tip which includes Ferg's updates. The controls that move the base now work but there there is no video. The issue seems to be with openni_camera. Also chirp app (Moo) seems to be broken: |
| 2011-07-28 12:59:19 -0500 | answered a question | Error in ROS Install on Pandaboard: 'E: Package 'mercurial' has no installation candidate' Try "sudo apt-get install mercurial" by itself. Your results look strange. It looks like you thought you typed mercurial but entered mercurialll instead. Did you correct it in some places when you posted your message? |
| 2011-07-12 04:47:17 -0500 | received badge | ● Good Answer (source) |
| 2011-07-12 04:47:17 -0500 | received badge | ● Enlightened (source) |
| 2011-07-06 11:36:09 -0500 | received badge | ● Autobiographer |
| 2011-07-04 20:14:40 -0500 | received badge | ● Nice Answer (source) |
| 2011-07-04 07:03:36 -0500 | commented answer | Installing turtlebot software on beagleboard. That's strange. Perhaps the SVN repository was not available when you tried. The SVN repository seems fine now. I would just try deleting and running rosinstall again. |
| 2011-07-04 06:55:45 -0500 | commented answer | Installing turtlebot software on beagleboard. Brian, I'm still very interested. Which packages (openni-dev, ps-engine, nite-dev, turtlebot-robot and dependencies? Let me know if I can help. |
| 2011-07-02 17:04:26 -0500 | received badge | ● Teacher (source) |
| 2011-07-02 07:24:57 -0500 | received badge | ● Editor (source) |
| 2011-07-02 07:13:02 -0500 | answered a question | Installing turtlebot software on beagleboard. Installing ROS Diamondback turtlebot-robot variant on BeagleBoard xM running Ubuntu 11.04 from SourceThis is a work in progress and is only meant to supplement the existing TurtleBot tutorials. Install Ubuntu packages on BeagleBoard xMsudo apt-get install build-essential python-yaml cmake subversion wget python-setuptools mercurial Install rosinstallsudo easy_install -U rosinstall Install ROS diamondback variant turtlebot-robot:rosinstall ~/ros "http://packages.ros.org/cgi-bin/gen_rosinstall.py?rosdistro=diamondback&variant=turtlebot-robot&overlay=no" Set up your environment.echo "source ~/ros/setup.bash" >> ~/.bashrc Use rosmake to build the various ROS and TurtleBot packages:I am still working on the best way the make all the necessary packages. You may want to install the following Ubuntu packages in advance:sudo apt-get install python-serial libglut3-dev libcppunit-dev graphviz libxext-dev python-sip-dev libcurl4-openssl-dev unzip libxml2-dev python-wxgtk2.8 libqhull-dev libhdf5-serial-dev joystick libusb-1.0-0-dev flex autoconf libusb-dev automake bluez bison python-bluez libgtk2.0-dev libbluetooth-dev Missing packages from Ubuntu natty arm repositories:The openni-dev, ps-engine (I'm sure that there are others) packages are not currently available from Ubuntu natty arm repositories. Without these packages the Kinect does not work but you can drive the TurtleBot around using the keyboard or joystick. |
| 2011-06-04 13:19:45 -0500 | received badge | ● Supporter (source) |
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.