Fred Eduardo's profile - activity

Yeah! after seeing your video I figured it out. My desktop could reach the Pr2 (Of course), but c1 could not reach my desktop. So I just added it to the hosts file and now everything works. Thanks a lot man! awesome talk!

Well, tuckarms work just fine. Could this be a network problem just for the controllers? Cause, on the desktop, using pr2_interactive_manipulation, Rviz shows correct information/states of the robot, so it receives data on the network. When I click 'move right arm', however, then it doesnt work.

@pr1023:~$ rosrun pr2_controller_manager pr2_controller_manager list
base_controller ( running )
base_odometry ( running )
head_camera_trigger ( running )
head_traj_controller ( running )
l_arm_controller ( running )
l_forearm_cam_trigger ( running )
l_gripper_controller ( running )
laser_tilt_controller ( running )
projector_controller ( running )
projector_trigger ( running )
prosilica_inhibit_projector_controller ( running )
r_arm_controller ( running )
r_forearm_cam_trigger ( running )
r_gripper_controller ( running )
torso_controller ( running )

these are my controllers. is it how it is supposed to be or am I missing something?

Hey Guys, I am trying to do some demos on a real Pr2, but I cant make it move it arms.

At first, I tried http://wiki.ros.org/pr2_interactive_m... And there occurs no error, robot comes up and on my desktop, rviz shows up all Ok, but then when I try to move its arms to the front or so it doesnt move.

So I tried something even more basic: pr2_props On Robot roslaunch pr2_props pr2_props.launch And on the desktop rosrun pr2_props hug

But I keep getting this message on a loop:

[ INFO] [1413233159.293564120]: Waiting for the joint_trajectory_action server
[ INFO] [1413233164.293692161]: Waiting for the joint_trajectory_action server
[ INFO] [1413233169.293832716]: Waiting for the joint_trajectory_action server
[ INFO] [1413233174.293930410]: Waiting for the joint_trajectory_action server

Any ideas what it could be?

@pr1023:~$ rosrun pr2_controller_manager pr2_controller_manager list
base_controller ( running )
base_odometry ( running )
head_camera_trigger ( running )
head_traj_controller ( running )
l_arm_controller ( running )
l_forearm_cam_trigger ( running )
l_gripper_controller ( running )
laser_tilt_controller ( running )
projector_controller ( running )
projector_trigger ( running )
prosilica_inhibit_projector_controller ( running )
r_arm_controller ( running )
r_forearm_cam_trigger ( running )
r_gripper_controller ( running )
torso_controller ( running )

these are my controllers. is it how it is supposed to be or am I missing something?

Hey guys, I am trying to port oculus_rviz_plugins to work with Oculus Rift DK2, so the first step is to build it with new SDK, Then I am going to replace old to new functions from the new API. So I have OculusSDK in my home, then I 'make' it with no errors, and then tried to catkin_make oculus_rviz_plugins in my catkin_ws, but I always get the following. It cant find the SDK. I suppose I didnt build OculusSDK properly. How can I do it? newbie here.

CMake Error at oculus_rviz_plugins/CMakeLists.txt:17 (FIND_PACKAGE):
  Could not find module FindOculusSDK.cmake or a configuration file for
  package OculusSDK.

  Adjust CMAKE_MODULE_PATH to find FindOculusSDK.cmake or set OculusSDK_DIR
  to the directory containing a CMake configuration file for OculusSDK.  The
  file will have one of the following names:

    OculusSDKConfig.cmake
    oculussdk-config.cmake



CMake Error at /opt/ros/groovy/share/catkin/cmake/catkin_package.cmake:156 (message):
  catkin_package() DEPENDS on 'OculusSDK' which must be find_package()-ed
  before.  If it is a catkin package it can be declared as CATKIN_DEPENDS
  instead without find_package()-ing it.
Call Stack (most recent call first):
  /opt/ros/groovy/share/catkin/cmake/catkin_package.cmake:98 (_catkin_package)
  oculus_rviz_plugins/CMakeLists.txt:23 (catkin_package)


-- Configuring incomplete, errors occurred!
make: *** [cmake_check_build_system] Error 1
Invoking "make cmake_check_build_system" failed

Thanks!

Yeah, I just installed pr2-* and ros-groovy-pr2-* and now my diagnosis is all green. Thanks a lot Hendrix!

I tried all above, No work.

I then tried apt-get install --reinstall ros-groovy-joystick-drivers and no work. I tried reinstall pr2-core-groovy and network, stilll no work. i dont what else to do.

I was using catkin_make on top of ws, figured I had to do make on pr2_surrogate folder for some reason. Sorry, newbie here :)

Hey Guys,

I am trying to use pr2_surrogate with oculus dk1. I get the oculus working with rviz and the kinect rendering to it, but I can't get the robot head to follow the head tracking. After I initialize robot.launch I get the following:

ERROR: cannot launch node of type [pr2_surrogate/head_pointer]: can't locate node [head_pointer] in package [pr2_surrogate] ERROR: cannot launch node of type [pr2_surrogate/arm_mover]: can't locate node [arm_mover] in package [pr2_surrogate] ERROR: cannot launch node of type [pr2_surrogate/arm_mover]: can't locate node [arm_mover] in package [pr2_surrogate]

Any ideias on what it could be?

Yeah I am pretty sure rviz_plugins simply does not support DK2. I am new to ros and rviz so I don't have the expertise, but I really want develop these patches for the dk2 to work on rviz. Anybody else willing to work on it? You guys think simply porting it to use the new oculus sdk might be enough?

Hey guys, I was having some issues with the kinect on the pr2 and so I had to uninstall and reinstall openni. I now get the kinect working (roslaunch / ros commands in general work), but somehow I think I messed up the bash configuration on the Pr2 machine. Now all commands robot start/stop, robot users etc, are not found.

I tried source again /opt/ros/groovy/setup.bash but nothing seems to work.

Also, right when I ssh into the pr2 machine AND when I type /bin/bash, I get the following:

-bash: /usr/bin/check-ssh-keys: No such file or directory Sourcing /etc/ros/setup.bash -bash: /etc/ros/setup.bash: No such file or directory

Do you guys know any workaround for this issue?

I am having the same issue here, can you please clarify what you deleted from /lib/udev/rules.d to solve it? and what about /etc/udev/rules.d?

I have the following at /etc/udev/rules.d : 70-persistent-cd.rules 70-persistent-net.rules 90-oculus-groovy.rules READM and at /lib/udev/rules.d I have a bunch of rules, but nothing related to the oculus.