Kel's profile - activity

Ok, so I blew away my build and devel and catkin_make again. I also switched from the ros fork to you aleeper git, and it works fine. So not sure if it was my environment or something in the hydro-devel branch of the ros fork. Probably my workspace :) Thanks for the help!

Could this be a problem with the udev rules? When I downloaded the source and catkin_made, it did not place the 99-hydra-indigo in my udev folder. I had to do it manually.

So I didn't realize that the line of code was removed that said something like "First message recieved, everything should be working now" However, I get nothing from rostopic echo /hydra_joy

Hello,

I recently upgraded my razer_hydra install to the indigo branch, and made sure that the udev rules were properly installed. Now when I run the command:

roslaunch razer_hydra hydra.launch publish_tf:=true

I get the output:

process[razer_hydra_driver-1]: started with pid [8245]
[ INFO] [1405699624.237070758]: Using filter corner frequency of 3.0 Hz
[ INFO] [1405699624.255034176]: Setting pivot offset [0.040, 0.000, 0.000]
[ INFO] [1405699624.255136486]: Setting grab offset [0.120, 0.000, 0.000]
[ INFO] [1405699624.255200864]: Sending messages using the 'grab' frame.
[ INFO] [1405699624.255261153]: Publishing frame data to TF.
[ INFO] [1405699624.279980897]: opening hydra on /dev/hydra
[ INFO] [1405699624.280525075]: starting stream... (first packet takes a few seconds)

and the process hangs there.

Has anyone else had this problem? When I was using the hydro branch, things worked fine.

Thanks! Kel

Hi Guys,

I just dual booted Xubuntu 12.04 along side my existing Ubuntu 10.10 install, and proceeded to to a fresh install of fuerte (on 12.04) by following the instructions on the install tutorial.

I then installed openni_kinect (which installs openni_tracker).

I have a Kinect attached (which works fine on 10.10/electric) and fired up the openni_tracker with the command "rosrun openni_tracker openni_tracker".

I get the following error:

"ERROR 1338827753.716401344: Find user generator failed: This operation is invalid!"

I am wondering if I didn't set up my environment properly, or if there is an xml file missing somewhere.

Please let me know if you have any ideas.

Thanks!

Kel

Hi Guys,

I am trying to use tf::TransformTFToEigen with a TF listener.

I have both eigen2 and eigen3 installed.

The error I get is "'eigen2_Transform3d' is not a member of Eigen". I was assuming that including <tf_conversions tf_eigen.h=""> would pull in any eigen dependencies, as that is what happens in tf_eigen.cpp.

Here is my code:

 #include <ros/ros.h>
 #include "std_msgs/String.h"
 #include "std_msgs/Float32.h"
 #include <tf_conversions/tf_eigen.h>
 #include <tf/transform_listener.h>

 int main(int argc, char** argv){
   ros::init(argc, argv, "openni_tracker_listener");

   ros::NodeHandle node;

   tf::TransformListener listener;

   Eigen::eigen2_Transform3d t;

   ros::Rate rate(10.0);

   while (node.ok()){

     tf::StampedTransform transform;

     try{
       listener.lookupTransform( "/right_hand", "/left_hand",  
                            ros::Time(0), transform);
       tf::TransformTFToEigen(transform,t);

     }catch (tf::TransformException ex){
       ROS_ERROR("%s",ex.what());
     }
     ros::spinOnce();
     rate.sleep();
   }
   return 0;
 };

Thanks for the help!

Kel

Thanks! And I just ignore the warning about the packages not being authenticated?

Hi Guys,

I am trying to install ROS Hydro from source on my fresh install of 13.10. The reason being is I have be a shiny new laptop with a Haswell chip that REALLY doesn't play nice with previous versions of gcc before 4.8.

Anyways, I was going through the source install tutorial

http://wiki.ros.org/hydro/Installation/Source

and it mentions that you need to grab the source list for this distribution:

If you have trouble installing the packages in the command above, make sure you have added the packages.ros.org debian repository to your apt source lists as described starting here: hydro/Installation/Ubuntu#hydro.2BAC8-Installation.2BAC8-Sources.Setup_your_sources.list

The problem is that there is no source list for saucy on the page mentioned. I know that there are no debian packages for saucy, but where are the source lists so I can install things like python-rosdep etc. Do I need to compile those from source too?

I know that people have managed to get this working, just not sure how. Thanks for the help!

Cheers, Kel

The Oculus SDK had actually installed the udev rules to /lib/udev/rules.d. Once I removed it, it works perfectly. Thanks so much for the help! I really appreciate it! Cheers, Kel

The Oculus SDK had actually installed the udev rules to /lib/udev/rules.d. Once I removed it, it works perfectly. Thanks so much for the help! I really appreciate it! Cheers, Kel

Hello,

I am trying to get the Oculus Rift working with rviz using the oculus_rviz_plugin and the oculus_sdk packages. I have tried a couple of ways and nothing seems to work.

I am running Ubuntu 12.04, ROS Hydro.

I started by grabbing the oculus drivers (0.2.4) from the oculus dev website. With their demo, I see video fine, and the head tracker works fine. (I did this with mirrored screens, one being the oculus and one being my monitor). One thing to note, the device config utility that came with the oculus drivers show "no device found" even though the device was clearly enumerated in the command line output, and the demo worked as expected.

I then installed the debian packages for the rviz plugin and oculus sdk, set the oculus as a separate monitor, and ran rviz. When I loaded in the OculusDisplay plugin, I get the following output:

OVR::DeviceManagerThread - running (ThreadId=0x7fc780051700).
OVR::DeviceManager - initialized.
OVR::DeviceManager - shutting down.
OVR::DeviceManagerThread - exiting (ThreadId=0x7fc780051700).

and the plugin status shows an error with the message "No Oculus device found!".

I have tried both connecting the oculus with DVI and HDMI (via a dvi to hdmi cable, my graphics card doesn't have hdmi natively). I have tried several usb ports (2.0 and 3.0).

I have also tried compiling both rviz and oculus_rviz_plugin from source (both from hydro-devel) with the same behavior.

Could it be that I messed things up by running the configure script that came with the Oculus SDK from their website?

What confounds me is that the oculus example (though the config utility, and rviz, report no device) works fine with video and perfect head tracking.

Has anyone experienced similar? Let me know if you need more information.

Any help would be appreciated.

Cheers!

Kel

Hi All,

I have a few of the new WiiMotion Plus (wiimote with built in Motion Plus) and I am trying to use the wiimote package with ROS Electric on Ubuntu 10.10.

So far, everything complies and runs fine, but after the wiimote is paired successfully, the terminal hangs.

So I get this:

kel@wyvern:~$ rosrun wiimote wiimote_node.py 
Press buttons 1 and 2 together to pair (within 6 seconds).
    (If no blinking lights, press power button for ~3 seconds.)
[INFO] [WallTime: 1349991095.467468] Pairing successful.
[INFO] [WallTime: 1349991095.778693] Checking presence of Nunchuk attachment ...ignore two possibly following error msgs.
[INFO] [WallTime: 1349991096.424111] Wiimote activated.
[INFO] [WallTime: 1349991097.831141] Calibration successful.
[INFO] [WallTime: 1349991097.834870] Wiimote IMU publisher starting (topic /imu/data).
[INFO] [WallTime: 1349991097.838450] Wiimote joystick publisher starting (topic wiijoy).
[INFO] [WallTime: 1349991097.842090] Wiimote state publisher starting (topic /wiimote/state).
[INFO] [WallTime: 1349991097.845175] Wiimote feedback listener starting (topic /joy/set_feedback).
[INFO] [WallTime: 1349991097.847821] Wiimote calibration service starting (topic /imu/calibrate).
[INFO] [WallTime: 1349991097.850338] Wiimote latched is_calibrated publisher starting (topic /imu/is_calibrated).

Upon looking at the broadcasted topic

rosrun wiimote wiimote_node.py

The command

rostopic list

yields

/imu/data
/imu/is_calibrated
/joy
/joy/set_feedback
/rosout
/rosout_agg
/wiimote/state

but with

rostopic echo /wiimote/state

I get the following output which just repeats and does not update:

header: 
  seq: 15218
  stamp: 
    secs: 1349991257
    nsecs: 428798675
  frame_id: ''
angular_velocity_zeroed: 
  x: -0.00130943628
  y: 0.0351647001
  z: -0.03612565737
angular_velocity_raw: 
  x: 7997.0
  y: 7972.0
  z: 7957.0
angular_velocity_covariance: [0.00011399123056619373, 0.0, 0.0, 0.0, 0.00067874597259235758, 0.0, 0.0, 0.0, 0.0002800379404909577]
linear_acceleration_zeroed: 
  x: -0.408610416667
  y: 0.0
  z: 9.80665
linear_acceleration_raw: 
  x: 126.0
  y: 128.0
  z: 152.0
linear_acceleration_covariance: [0.0, 0.0, 0.0, 0.0, 15.954666742512758, 0.0, 0.0, 0.0, 0.0]
nunchuk_acceleration_zeroed: 
  x: 0.0
  y: 0.0
  z: 0.0
nunchuk_acceleration_raw: 
  x: 0.0
  y: 0.0
  z: 0.0
nunchuk_joystick_zeroed: [0.0, 0.0]
nunchuk_joystick_raw: [0.0, 0.0]
buttons: [False, False, False, False, False, False, False, False, False, False, False]
nunchuk_buttons: [False, False]
LEDs: [False, False, False, False]
rumble: False
ir_tracking: 
  - 
    x: -1.0
    y: -1.0
    ir_size: -1
  - 
    x: -1.0
    y: -1.0
    ir_size: -1
  - 
    x: -1.0
    y: -1.0
    ir_size: -1
  - 
    x: -1.0
    y: -1.0
    ir_size: -1
raw_battery: 112.0
percent_battery: 53.8461532593
zeroing_time: 
  secs: 1349991097
  nsecs: 830956935
errors: 0
---

All that changes is the time-stamp and the seq number in the header. Also, I am holding the wiimote within a few feet of the bluetooth dongle so I don't think it is a distance problem.

Let me know if you have any ideas, I think I am pretty close, but any help would be awesome.

Thanks very much :D

Kel