How to find the problem of kinect when rostopic echo get nothing

asked 2012-12-12 22:50:46 -0500

Albert K
291 ●36 ●45 ●52

updated 2016-10-24 09:01:42 -0500

ngrennan
1 ●1 ●1

I plugin the kinect.

roslaunch openni_launch openni.launch

rosrun rviz rviz

setup the msg type [PointCloud2]

and topic [/camera/depth/points]

and the reference frame [/camera_depth_frame]

But the status indicates no messages received. How can I make sure it's the problem from kinect or from openni?

modified)

To clarify my problem:

I do rostopic echo [topic] and get nothing. It may not be the problem of Rviz and the viewing tools. I doubt this is the hardware and driver problem, and possibly the graphic card driver? This problem happened on my laptop while my desktop worked fine. Both of them are Ubuntu 12.04 and Fuerte. I got bumblebee on my laptop but not on the desktop.

Some messages appear in the shell where I roslaunch openni_launch openni.launch :

[ERROR] [1355549619.381311998]: Tried to advertise a service that is already advertised in this node [/camera/depth_registered/image_rect_raw/compressedDepth/set_parameters]
[ERROR] [1355549619.393316233]: Tried to advertise a service that is already advertised in this node [/camera/depth_registered/image_rect_raw/compressed/set_parameters]
[ERROR] [1355549619.406856824]: Tried to advertise a service that is already advertised in this node [/camera/depth_registered/image_rect_raw/theora/set_parameters]
[ INFO] [1355549620.217247774]: Number devices connected: 1
[ INFO] [1355549620.217803421]: 1. device on bus 003:05 is a Xbox NUI Camera (2ae) from Microsoft (45e) with serial id 'A00365A18349102A'
[ INFO] [1355549620.219848686]: Searching for device with index = 1
[ INFO] [1355549620.260220331]: Opened 'Xbox NUI Camera' on bus 3:5 with serial number 'A00365A18349102A'
[ INFO] [1355549620.280287325]: rgb_frame_id = '/camera_rgb_optical_frame' 
[ INFO] [1355549620.280362638]: depth_frame_id = '/camera_depth_optical_frame' 
[ WARN] [1355549620.284242802]: Camera calibration file /home/albert/.ros/camera_info/rgb_A00365A18349102A.yaml not found.
[ WARN] [1355549620.284296968]: Using default parameters for RGB camera calibration.
[ WARN] [1355549620.284377146]: Camera calibration file /home/albert/.ros/camera_info/depth_A00365A18349102A.yaml not found.
[ WARN] [1355549620.284421645]: Using default parameters for IR camera calibration.

I think that these warnings and errors shouldn't result in such problem. Besides, the info may tell us that the device driver is fine.

How to solve this? Thanks~

edit retag flag offensive close merge delete

Comments

Does rostopic echo /camera/depth/points print anything?

Saphrosit ( 2012-12-13 00:49:48 -0500 )edit

2

I have met the same problem. In my case, it prints nothing.

sam ( 2012-12-13 14:53:51 -0500 )edit

add a comment

1

answered 2012-12-13 09:58:02 -0500

autorover
93 ●1 ●2 ●6

updated 2012-12-13 09:58:23 -0500

An easier way to see if the data from the Kinect is being received by the drivers and computer than by setting up rviz is with the command rosrun image_view image_view image:=/camera/rgb/image_color, which should display an RGB image from the Kinect camera if the driver is functioning properly. Remember to have roscore and the driver running in the background. More information is on the openni_launch page.

edit flag offensive delete link

Comments

I have met the same problem. In my case, it shows the window but without any image.

sam ( 2012-12-13 14:55:43 -0500 )edit

It looks like another way to take and display the sensor data from the topic, but the situation is that rostopic echo get nothing.

Albert K ( 2012-12-14 05:07:58 -0500 )edit

assuming that you are using fuerte and have downloaded openni_launch and openni_camera, I would suggest trying alternate USB ports for the kinect and potentially even reinstalling those drivers. Seems that you are doing the right things, so just fiddle around a bit more.

autorover ( 2012-12-15 19:08:19 -0500 )edit

add a comment

0

answered 2012-12-13 19:23:49 -0500

snakehaihai
28 ●4 ●5 ●8

try rosrun openni_camera openni_node and then see it in RVIZ with reference frame to openni frame

edit flag offensive delete link

Comments

According to the wiki page of ros, openni_launch openni.launch seemed to be a better approach for those 3D sensor. Most applications need the additional information from openni.launch rather than a single node, so this is an unavoidable problem to be solved.

Albert K ( 2012-12-14 05:04:12 -0500 )edit

add a comment

0

answered 2012-12-13 10:32:31 -0500

Steve
1 ●1

If you are on latest 12.04 I have had issues with getting openni to work. The driver itself appears to be the issue not ROS. In order to get a working system I ended up changing to 12.10. Unfortunately this means I need to use Groovy as trying to compile Fuerte from source isn't really a straight forward or well documented process.

edit flag offensive delete link

Comments

Actually, I've test it on both my desktop and my laptop, but only desktop worked. Both of my computer are Ubuntu 12.04 and with Fuerte installed. I think the version of Ubuntu might not be so important.

Albert K ( 2012-12-14 04:46:50 -0500 )edit

add a comment

How to find the problem of kinect when rostopic echo get nothing

Comments

3 Answers

Comments

Comments

Comments

Question Tools

Stats

Related questions

How to find the problem of kinect when rostopic echo get nothing edit

Comments

3 Answers

Comments

Comments

Comments

Question Tools

Stats

Related questions

How to find the problem of kinect when rostopic echo get nothing