achuwilson's profile - activity

Thank You. It was exactly the issue. Upgrading to 1.13.2 version of control toolbox solved the problem.

I am using a simulated PR2 in ROS Indigo (Ubuntu 14.04). While running

roslaunch pr2_gazebo pr2_empty_world.launch

the head of PR2 turns back and the arms get twisted and rotates continously. Also it is not possible to control the simulated PR2 using keyboad teleop package. It was working fine untill all the ros-indigo packages were updated through synaptic package manager .

It happens when the pr2_default_controllers are up and running. Simulation with no controllers makes no issues.

It should work. I have worked with simulated Hokoyu laser scanners, in vrep, then exported the data from vrep as pointcloud into ROS, then used pointcloud_to_laserscan package to output a scan

yes sure, u need openni, Kinect outputs a pointcloud , then using the package pointcloud_to_laserscan (depthimage_to_laserscan in ROS Hydro), you have to fake it as a laserscanner.

See the Dynamixel tutorials http://wiki.ros.org/dynamixel_controllers/Tutorials

Also have a look at the code of CLAM Arm http://correll.cs.colorado.edu/clam/

Yeah. I beleive it is possible and you can run navigation stack with Sharp's IR scanner, although the resolution may not be good as the default methods. See the following links

http://www.showusyoursensors.com/2010/08/ros-and-other-ramblings.html

This is how its done in Pi-Robot

http://www.youtube.com/watch?v=6oDrO5EKU5w

http://www.pirobot.org/blog/0014/

and here is some code

http://code.google.com/p/vanadium-ros-pkg/source/browse/trunk/arbotix/src/arbotix_sensors/lidar.py?spec=svn19&r=19

Try Turtlebot

http://wiki.ros.org/Robots/TurtleBot

http://www.turtlebot.com/

Hi, I too had the same issues. it was caused by an older version of pcl standalone installation. So i uninstalled all PCL, Openni packages, then removed a ppa of pcl from synaptic. Now it works fine

I have generated an arm navigation package for a 7 DOF arm using the Planning Description Configuration Wizard, and everything works fine except disabling constrain in roll and pitch. Even though the check-box is un-ticked,the end-effector always maintains the roll, pitch and yaw. So the number of IK solutions are limited, since the end-effector may not be able to maintain the orientation at the given position. Has anyone else faced such kind of problems before?

I too had the same issues with my custom arm navigation . Did you find out a solution ?

Hi, using an Arduino would be great while beginning the actual hardware implementation of a robot running ROS. You can write a ROS node running in arduino, subscribing and publishing topics from and to the other nodes running on a computer.

The rosserial package helps a lot in accomplishing this. The arduino will be connected to a USB port of the computer and all the motors, sensors and such stuff can be interfaced with arduino. I am a beginner in ROS and presently working on a personal robot named chippu as a hobby project. More details, including all the codes can be had from my blog