I Heart Robotics's profile - activity

Also, you could reinstall Ubuntu from the TurtleBot ISO image. http://www.neautomation.com/blog/posts/turtlebot-hydro-r0.html

The "Icon" is part of some external debian packages.

https://launchpad.net/~neautomation/+...

https://github.com/turtlebot-mfg

Something like the following used to work in electric but in fuerte it incorrectly yields /opt/ros/fuerte/share/roslaunch/bin/roslaunch instead of /opt/ros/fuerte/bin/roslaunch

std::string roslaunch_path = ros::package::getPath("roslaunch");
sprintf (roslaunch_bin_path, "%s/bin/roslaunch", roslaunch_path.c_str ());

In electric

$rospack find roslaunch 
/opt/ros/electric/stacks/ros_comm/tools/roslaunch
$ls /opt/ros/electric/stacks/ros_comm/tools/roslaunch/bin/roslaunch
/opt/ros/electric/stacks/ros_comm/tools/roslaunch/bin/roslaunch

In Fuerte

$rospack find roslaunch 
/opt/ros/fuerte/share/roslaunch
$ls /opt/ros/fuerte/share/roslaunch
manifest.xml  resources

Is this the desired behavior? If so how do we find the location of the roslaunch binary? Is there a roslaunch API that is stable so we don't need to exec() roslaunch?

Is there a way to get ROS Answers to send an email when a question is posted with a specific tag?

Update: Where is the tags listed in 'allow only selected tags' set?

Hack attached to ticket

Is it currently possible to build android_app_chooser from source on fuerte?

Does it use the current build of ROSJava or does it need the JNI-based Java client library?

Should we just wait until the new version of ROSJava is a bit more stable?

What is the currently preferred method for a complete source build of ROS Fuerte?

This URL does not seem to work. http://packages.ros.org/cgi-bin/gen_rosinstall.py?rosdistro=fuerte&variant=desktop-full&overlay=no

If you already have patches, the best thing to do is to find the correct bug tracker for your package and create a bug report and attach your patch to the bug report.

If it is urgent, you can then email ros-users@code.ros.org with the bug id which helps make sure nothing gets lost.

Many package's bug trackers are on http://kforge.ros.org/projects/

For example if you have a TurtleBot related problem, bug reports can be submitted to http://kforge.ros.org/turtlebot/trac

Also many packages and stack list the tracker in their documentation such as http://ros.org/wiki/ros_comm which has a bug tracker at https://code.ros.org/trac/ros/newticket?component=ros_comm&type=defect&&ros_comm

Thanks for the help! I have patchified things and made some adjustments. Please post feedback on the patch to the ticket.

The ckermit connands are "set line /dev/ttyUSB0", "set speed 57600", "set carrier-watch off","connect". After that power cycle the create.

These may be different problems. If you have the right port set and nothing is working it might be hardware. I would suggest using kermit to connect to the serial port at 57600 baud and power cycle the create. If the hardware is working it should display something.

http://kforge.ros.org/turtlebot/trac/ticket/134

This is now in the ticket system. http://kforge.ros.org/turtlebot/trac/ticket/134

Yes! That was one of our design goals.

/turtlebot_node/cmd_vel [unknown type] I'm not in front of a robot at the moment but unknown type sounds wrong. Have you tried debugging with roswtf?

That sounds like your kernel driver. You want the device name that shows up in ifconfig. it is usually eth0 or wlan0 or eth1

However you are right that on the TurtleBot you should just need to run the service. You can however stop the service and start roscore manually but that it probably just complicating matters.

However if you start roscore, then start roslaunch, then restart roscore, the nodes you launched with roslaunch may not reconnect properly. If I recall correclty, Dynamic reconfigure reconnects, but image_view will not.

I'm not sure if this is helpful, but here goes. You should be able to run roscore independent of roslaunch, though there are some nuances. roslaunch will start roscore if it is not already running. If you start roscore, then start roslaunch then stop roslaunch, roscore will keep running.

If that works, 'roscd turtlebot_bringup/upstart && sudo ./install.bash wlan0' should install the proper scripts in /etc. Replace wlan0 with the correct name for your wifi device. http://ros.org/wiki/Robots/TurtleBot/Robot%20Install#Configure_Upstart