felix k's profile - activity

Have you tried removing the sys.exit() call? This might indeed create a loop

When are you pressinc Ctrl+C and expecting it to quit but it doesn't? During the sleep() or during the reset_world()?

Traversing a robot in a prespecified path Hi! Last day i was trying out an experiment to traverse a robot in a pre speci

How to use dynamic_reconfigure for /gazebo vs. /gazebo_gui? I'm starting Gazebo 7 via ROS Kinetic, which is working fine

There is an even older, but more active, related question: https://answers.ros.org/question/10852/playing-back-large-f

Explanation of rospy.Rate() I am looking for an explanation of rospy.rate(), I have looked it in the documentation and i

The pr2_robot stack page links to kforge/pr2_robot for the sources, for every distro, but it states new issues should be reported on github/pr2_robot. As there also is the full and newer (?) source, and with the general move to github in mind, I'm confused if the source link is correct and to be used?

I saw the diagnostics stack, but is there a package that actually reacts on those diagnostic messages in terms of issuing a given message or shell command?

I'd like to shutdown the robot PC if the battery goes low (which the OS isn't aware of), and thought using diagnostics would be the right way.

Is there a prepared solution to that, or do I have to write a special node?

As what I read it should be possible to put the kinect pointcloud into the collider node, and then put the published costmap into the environment_server of planning_environment.

I see both pointcloud and costmap in rviz, but the validity checker ignores it. Regarding to rosnode, the environment_server isn't listening to a collision_map typed topic at all.

What I configured:

• In my once generated planning_scene_warehouse_viewer_robotname[_real].launch I set use_collision_map to true.
• I had to remove the 4-line-include<include file="$(find > planning_environment)/launch/environment_server.launch"> and run it separately, because else one node keeps crying and nothing works:

[ INFO] [1332518882.807188537, 1332518882.801862955]: Waiting for environment 
server planning scene registration service /register_planning_scene
[ INFO] [1332518882.935278639, 1332518882.932450056]: waitForService: Service 
[/register_planning_scene] has not been advertised, waiting...

I am trying to compile ros_gui or rviz on Xubuntu 11.10 within current electric, but without any success.

I did the usual clone for rviz, and a roslocate info with rosinstall for ros_gui. Everywhere the package or rosdep python-qt-bindings is referenced, but apart from this kforge project it's kind of inexistent. And it does not work. What have I done wrong?

Maybe this output helps:

$ rosdep satisfy rviz
Failed to find rosdep libqt4-dev for package rviz on OS:ubuntu version:oneiric
Failed to find rosdep qt4-qmake for package rviz on OS:ubuntu version:oneiric
Failed to find rosdep libqt4-opengl-dev for package rviz on OS:ubuntu version:oneiric
Failed to find rosdep python-qt-bindings for package rviz on OS:ubuntu version:oneiric
error in processing scripts ABORTING: Rosdeps [u'libqt4-dev', u'qt4-qmake', u'libqt4-opengl-dev', u'python-qt-bindings'] could not be resolved
Failed to find rosdep libqt4-dev for package rviz on OS:ubuntu version:oneiric
Failed to find rosdep qt4-qmake for package rviz on OS:ubuntu version:oneiric
Failed to find rosdep libqt4-opengl-dev for package rviz on OS:ubuntu version:oneiric
Failed to find rosdep python-qt-bindings for package rviz on OS:ubuntu version:oneiric
The following rosdeps are not installed but are required [u'libqt4-dev', u'qt4-qmake', u'libqt4-opengl-dev', u'python-qt-bindings']

I want to use the arm_navigation_warehouse with our real robot and I don't get along this error. As the warehouse tutorial states, I start the planning_scene_warehouse_viewer_scitos_haw_schunk.launch from my wizard-created package.

I specify the trajectory action service and check Use Robot Data. Accepting this config loads the planning_scene_warehouse_viewer, so long so usual. But after creating a new.. planning scene, I get the following errors:

[ERROR] [x.300639468, x.297759056]: Setting planning scene state to NULL
[ERROR] [x.300739768, x.297759056]: Setting planning scene state to NULL
[ WARN] [x.301398800, x.297759056]: Incomplete robot state in setPlanningScene
[ERROR] [x.301461209, x.297759056]: Setting planning scene state to NULL
[ERROR] [x.301492785, x.297759056]: Setting planning scene state to NULL
[ERROR] [x.303755538, x.297759056]: Something wrong with planning scene

However, the next window for the planning scene opens, but trying to create a new Motion Plan Request quits the viewer:

[planning_scene_warehouse_viewer-9] process has died [pid 9602, exit code -11].

If I enable debug level for those parts:

/planning_scene_warehouse_viewer:ros.planning_models
/planning_scene_warehouse_viewer:ros.urdf

.. before clicking new.., I also get this five times (for every joint?) before the [ WARN] from above:

[DEBUG] [x.643684884, x.637037992]: Transform angle is 0 axis x 1 axis y 0 axis z 0

Does anyone know what's up or how to investigate further?

"Something wrong with planning scene" code line

"Incomplete robot state in setPlanningScene" code line

I have a Fedora14 machine on our robot and a Fedora14 workstation. High level and visualization nodes are run on the workstation. The communication is working unless I activate the firewalls.

I want to try to activate the firewalls and set up a VPN between those machines, as the network is a bigger one. So I'm needing a probably simple bidirectional VPN which forwards packets to each other machine through the VPN.

I never set up a VPN, and couldn't find instructions I get along with. Are there any advices how to proceed?

In the future another workstation may be introduced and needed simultaneously, if that's significant.

Hello, I'm using ROS on fedora12 in user space, thanks for your help.

1. Calling rosmake on a package mostly compiles all needed packages including basics like roscpp again, though they have been built already. Why can't it see that those packages didn't change at all?

2. Therefore I put a ROS_NOBUILD in every pkg that needs more than a blink to build. Updating through rosinstall ~/ros seems to leave this flag, which prevents the updates from being built. Shouldn't there be an option to do remove the flag if reasonable, or perhaps better a way for rosmake to ignore this flag when called after updating rosinstall? Or where am I wrong?