diannay's profile - activity

Hi,

After reading the URDF and robot / joint state publisher related tutorials, I am able to see the joint messages published by the joint state publisher, but the velocity and effort fields are empty.(I am currently running ros-diamondback on linux) Then looking into the pr2_controller_manager tutorials, I was able to use the JointVelocityController Plugin (configured it to correspond the joints in my urdf file) and launched a spawner type pr2_controller_manager node taking these JointVelocityController as an argument. But using rostopic info on this node, it does not have any subscribed or published topics. What are some ways to generate these velocity and effort fields? I am trying to use the environment_server of motion_planning_common which requires valid joint messages with velocity components for collision detection but keep seeing the invalid joint state error mesesage.

From the rviz wiki, it seems intensity is related to colour? What type of information is encoded in the intensity of a point in a point cloud?

Hi all,

I am running ros-diamonback on linux and having been going through the motion_planning_environment tutorials and but am struggling in seeing the visualization of collision maps in rviz as I cannot see it as a topic that I can enable and add. I know that I do have a collision map topic that is issued between the collision_map_self_occ node and the environment_server node. I have an intel graphics card and am aware that it is not that compatible with rviz...not sure if that's an issue here, but is there a work around for this?

Also, everytime I try to use the "mapping' plugin and the "articulation' plugin rviz instantaneously crashes.

Hi,

Using the swissranger_camera node connecting through ethernet (running linux using ros- diamondback), I consistently see points along the edges of the field of vision of the swissranger when there are no obstacles in the way(see the following link to a picture of this) The points near the vertex of the cone by the sensor have an evident abundance of these points from an unknown source. The sensor has ~5m range and this weird noise we see is <~2m in front of the sensor where it is in a obstacle-free environment. Are there any suggestions to what is causing this problem and any solutions to this?

http://i54.tinypic.com/111qyqu.png

Hi,

I was wondering if there are any existing stable support for collision detection in ROS and if any, possibly some that are using the octree of the Octomap library and allows for visualization in RVIZ? Currently it seems that collision detection through the motion_planning_environment stack has been placed into motion_planning_common; is motion_planning_common stable to use still? And if so, are there any resources such as tutorials that are available for setting up a self defined robot instead of the PR2?

Thanks in advance!

Hi all,

I am running on the diamondback on a linux and am having problems when connecting the Swissranger (4k) using swissranger_camera found at http://www.ros.org/wiki/swissranger_c... . I have followed the respective tutorial and have noticed that the udev settings had to be changed for the "usb" method of transmission; is there an equivalent when using the ethernet?

Currently I get an error msg as such

usb_set_debug: Setting debugging level to 255 (on) usb_os_find_busses: Found 007 usb_os_find_busses: Found 006 usb_os_find_busses: Found 005 usb_os_find_busses: Found 004 usb_os_find_busses: Found 003 usb_os_find_busses: Found 002 usb_os_find_busses: Found 001 usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 001 on 007 error obtaining child information: Operation not permitted usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 001 on 006 error obtaining child information: Operation not permitted usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 001 on 005 error obtaining child information: Operation not permitted usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 001 on 004 error obtaining child information: Operation not permitted usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 001 on 003 error obtaining child information: Operation not permitted usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 002 on 002 skipping descriptor 0xFF skipping descriptor 0xB skipped 2 class/vendor specific endpoint descriptors skipped 7 class/vendor specific interface descriptors skipping descriptor 0x25 skipped 1 class/vendor specific endpoint descriptors skipped 19 class/vendor specific interface descriptors usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 001 on 002 error obtaining child information: Operation not permitted error obtaining child information: Operation not permitted usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 001 on 001 error obtaining child information: Operation not permitted usb_set_debug: Setting debugging level to 0 (off) What steps should I take to config this to use ethernet?

Thanks in advance!

Hi,

In terms of stability we have not yet made any claims for any of the arm navigation stacks, including motion_planning_common. A good deal of this software will be being released as stable in our forthcoming e-turtle release. As part of the e-turtle release we have been developing a number of tools that attempt to make it easier to interact with the software. Among these is an auto-configuration tool that should make it easier to get all of our software working for a new robot. If you are interested you can try out the new tutorial, though it will require installing some software from our unstable debians. The tutorial is here: tutorial. Again, this won't be stable until the e-turtle release, but definitely the easiest way forward to trying out our software.

In terms of displaying detected collisions in rviz we don't currently have a tool that will do that out of the box. We're working on something like that, but it won't be available for a little while.

This is typically a sensor-dependent "brightness" of return, representing some quality of measurement: energy returned, pixel value, etc. Sometimes it can look like a greyscale brightness. See the images on the right here to view some images produced by a laser scanner returning intensities.

Just be aware that sometimes it isn't human color dependent. Some materials reflect IR laser beams very well but appear black to our eyes.