search

ros-drivers / freenect_stack

libfreenect based ROS driver
http://ros.org/wiki/freenect_stack
35 stars 52 forks source link

freenect broke my kinect (?) #22

Closed lucbettaieb closed 5 years ago

lucbettaieb commented 9 years ago

Was trying to get my Kinect streaming a pointcloud into rviz. When I launched freenect.launch from freenect_launch and went into rviz and selected the PointCloud2 type and selected the appropriate topic, everything froze, the program crashed, and now my Kinect is unresponsive. (The green lights aren't even turning on when I plug it in)

Previously to me doing this, I tried openni with no success. I added a rules file to my udev folder and restarted the udev service so things would work. Here's all of the std out from the launch.

luc@machina:/etc/udev/rules.d$ roslaunch freenect_launch freenect.launch 
... logging to /home/luc/.ros/log/8dfc837c-5b51-11e5-988a-f46d0458fe49/roslaunch-machina-5503.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://machina:58826/

SUMMARY
========

PARAMETERS
 * /camera/camera_nodelet_manager/num_worker_threads: 4
 * /camera/depth_rectify_depth/interpolation: 0
 * /camera/depth_registered_rectify_depth/interpolation: 0
 * /camera/disparity_depth/max_range: 4.0
 * /camera/disparity_depth/min_range: 0.5
 * /camera/disparity_registered_hw/max_range: 4.0
 * /camera/disparity_registered_hw/min_range: 0.5
 * /camera/disparity_registered_sw/max_range: 4.0
 * /camera/disparity_registered_sw/min_range: 0.5
 * /camera/driver/data_skip: 0
 * /camera/driver/debug: False
 * /camera/driver/depth_camera_info_url: 
 * /camera/driver/depth_frame_id: camera_depth_opti...
 * /camera/driver/depth_registration: False
 * /camera/driver/device_id: #1
 * /camera/driver/diagnostics_max_frequency: 30.0
 * /camera/driver/diagnostics_min_frequency: 30.0
 * /camera/driver/diagnostics_tolerance: 0.05
 * /camera/driver/diagnostics_window_time: 5.0
 * /camera/driver/enable_depth_diagnostics: False
 * /camera/driver/enable_ir_diagnostics: False
 * /camera/driver/enable_rgb_diagnostics: False
 * /camera/driver/rgb_camera_info_url: 
 * /camera/driver/rgb_frame_id: camera_rgb_optica...
 * /rosdistro: indigo
 * /rosversion: 1.11.13

NODES
  /camera/
    camera_nodelet_manager (nodelet/nodelet)
    debayer (nodelet/nodelet)
    depth_metric (nodelet/nodelet)
    depth_metric_rect (nodelet/nodelet)
    depth_points (nodelet/nodelet)
    depth_rectify_depth (nodelet/nodelet)
    depth_registered_rectify_depth (nodelet/nodelet)
    disparity_depth (nodelet/nodelet)
    disparity_registered_hw (nodelet/nodelet)
    disparity_registered_sw (nodelet/nodelet)
    driver (nodelet/nodelet)
    points_xyzrgb_hw_registered (nodelet/nodelet)
    points_xyzrgb_sw_registered (nodelet/nodelet)
    rectify_color (nodelet/nodelet)
    rectify_ir (nodelet/nodelet)
    rectify_mono (nodelet/nodelet)
    register_depth_rgb (nodelet/nodelet)
  /
    camera_base_link (tf/static_transform_publisher)
    camera_base_link1 (tf/static_transform_publisher)
    camera_base_link2 (tf/static_transform_publisher)
    camera_base_link3 (tf/static_transform_publisher)

auto-starting new master
process[master]: started with pid [5515]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to 8dfc837c-5b51-11e5-988a-f46d0458fe49
process[rosout-1]: started with pid [5528]
started core service [/rosout]
process[camera/camera_nodelet_manager-2]: started with pid [5545]
process[camera/driver-3]: started with pid [5546]
[ INFO] [1442284154.221490359]: Initializing nodelet with 4 worker threads.
process[camera/debayer-4]: started with pid [5582]
process[camera/rectify_mono-5]: started with pid [5596]
process[camera/rectify_color-6]: started with pid [5613]
process[camera/rectify_ir-7]: started with pid [5627]
process[camera/depth_rectify_depth-8]: started with pid [5641]
process[camera/depth_metric_rect-9]: started with pid [5655]
process[camera/depth_metric-10]: started with pid [5677]
process[camera/depth_points-11]: started with pid [5691]
process[camera/register_depth_rgb-12]: started with pid [5722]
[ INFO] [1442284154.472231155]: Number devices connected: 1
[ INFO] [1442284154.472291398]: 1. device on bus 000:00 is a Xbox NUI Camera (2ae) from Microsoft (45e) with serial id 'A00367901904037A'
[ INFO] [1442284154.472942464]: Searching for device with index = 1
process[camera/points_xyzrgb_sw_registered-13]: started with pid [5752]
process[camera/depth_registered_rectify_depth-14]: started with pid [5768]
process[camera/points_xyzrgb_hw_registered-15]: started with pid [5785]
process[camera/disparity_depth-16]: started with pid [5812]
process[camera/disparity_registered_sw-17]: started with pid [5865]
process[camera/disparity_registered_hw-18]: started with pid [5886]
process[camera_base_link-19]: started with pid [5909]
process[camera_base_link1-20]: started with pid [5934]
process[camera_base_link2-21]: started with pid [5946]
process[camera_base_link3-22]: started with pid [5972]
[ INFO] [1442284155.565020561]: Starting a 3s RGB and Depth stream flush.
[ INFO] [1442284155.565191080]: Opened 'Xbox NUI Camera' on bus 0:0 with serial number 'A00367901904037A'
[ WARN] [1442284159.191446580]: Could not find any compatible depth output mode for 1. Falling back to default depth output mode 1.
[ INFO] [1442284159.192613384]: Stopping device RGB and Depth stream flush.
[ INFO] [1442284159.198437862]: rgb_frame_id = 'camera_rgb_optical_frame' 
[ INFO] [1442284159.198478594]: depth_frame_id = 'camera_depth_optical_frame' 
[ WARN] [1442284159.208604632]: Camera calibration file /home/luc/.ros/camera_info/rgb_A00367901904037A.yaml not found.
[ WARN] [1442284159.208677857]: Using default parameters for RGB camera calibration.
[ WARN] [1442284159.208720059]: Camera calibration file /home/luc/.ros/camera_info/depth_A00367901904037A.yaml not found.
[ WARN] [1442284159.208753471]: Using default parameters for IR camera calibration.
[ INFO] [1442284224.682958508]: Device timed out. Flushing device.
[ INFO] [1442284224.683885508]: Starting a 3s RGB and Depth stream flush.
terminate called after throwing an instance of 'std::runtime_error'
  what():  freenect_process_events error
[camera/camera_nodelet_manager-2] process has died [pid 5545, exit code -6, cmd /opt/ros/indigo/lib/nodelet/nodelet manager __name:=camera_nodelet_manager __log:=/home/luc/.ros/log/8dfc837c-5b51-11e5-988a-f46d0458fe49/camera-camera_nodelet_manager-2.log].
log file: /home/luc/.ros/log/8dfc837c-5b51-11e5-988a-f46d0458fe49/camera-camera_nodelet_manager-2*.log
^C[camera_base_link3-22] killing on exit
[camera_base_link2-21] killing on exit
[camera_base_link1-20] killing on exit
[camera_base_link-19] killing on exit
[camera/disparity_registered_hw-18] killing on exit
[camera/disparity_registered_sw-17] killing on exit
[camera/disparity_depth-16] killing on exit
[camera/points_xyzrgb_hw_registered-15] killing on exit
[camera/depth_registered_rectify_depth-14] killing on exit
[camera/points_xyzrgb_sw_registered-13] killing on exit
[camera/register_depth_rgb-12] killing on exit
[camera/depth_points-11] killing on exit
[camera/depth_metric-10] killing on exit
[camera/depth_metric_rect-9] killing on exit
[camera/depth_rectify_depth-8] killing on exit
[camera/rectify_ir-7] killing on exit
[camera/rectify_color-6] killing on exit
[camera/rectify_mono-5] killing on exit
[camera/debayer-4] killing on exit
[camera/driver-3] killing on exit
[rosout-1] killing on exit
[master] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
done

Maybe my kinect was just faulty? Any idea as to what happened? Let me know if any more info is required.

lucbettaieb commented 9 years ago

@piyushk : any idea as to what may have happened?

piyushk commented 9 years ago

@lucbettaieb Sorry to hear about the non-functioning Kinect! I'm afraid I have no idea, as I've never experienced hardware failure while running this driver. The fact that openni did not work in the first place does not seem promising.

lucbettaieb commented 9 years ago

@piyushk Dang, well; If I find anything out I'll re-open the ticket. Thanks.

fdcqsjn commented 9 years ago

Hi,I have the same problem.and when I use

roslaunch openni_launch openni.launch

then use rviz,kinect worked.

lucbettaieb commented 9 years ago

Interesting, I'll give it a try.

Robinroy-peter commented 7 years ago

i got below error but my kinect is working perfect...early a time its worked but now its show this error...freenect_launch working normaly without error but if i run rviz its show the below error please help me

[ INFO] [1499883433.167600440]: Stopping device RGB and Depth stream flush. terminate called after throwing an instance of 'std::runtime_error' what(): freenect_process_events error [camera/camera_nodelet_manager-1] process has died [pid 3479, exit code -6, cmd /opt/ros/kinetic/lib/nodelet/nodelet manager name:=camera_nodelet_manager log:=/home/robinrobotics/.ros/log/2f69a2e2-672d-11e7-9a3a-4cbb583d50df/camera-camera_nodelet_manager-1.log]. log file: /home/robinrobotics/.ros/log/2f69a2e2-672d-11e7-9a3a-4cbb583d50df/camera-camera_nodelet_manager-1*.log

josephcoombe commented 6 years ago

I got a similar error with Ubuntu 16.04 ROS Kinetic Xbox 360 Kinect - Model 1414

process[camera/camera_nodelet_manager-1]: started with pid [31300]
process[camera/driver-2]: started with pid [31301]
process[camera/rgb_debayer-3]: started with pid [31302]
process[camera/rgb_rectify_mono-4]: started with pid [31303]
process[camera/rgb_rectify_color-5]: started with pid [31316]
process[camera/ir_rectify_ir-6]: started with pid [31328]
process[camera/depth_rectify_depth-7]: started with pid [31343]
process[camera/depth_metric_rect-8]: started with pid [31360]
process[camera/depth_metric-9]: started with pid [31363]
process[camera/depth_points-10]: started with pid [31381]
[ INFO] [1529679797.580395988]: Initializing nodelet with 4 worker threads.
process[camera/register_depth_rgb-11]: started with pid [31398]
process[camera/points_xyzrgb_sw_registered-12]: started with pid [31412]
process[camera/depth_registered_sw_metric_rect-13]: started with pid [31426]
process[camera/depth_registered_rectify_depth-14]: started with pid [31442]
process[camera/points_xyzrgb_hw_registered-15]: started with pid [31457]
process[camera/depth_registered_hw_metric_rect-16]: started with pid [31475]
process[camera/depth_registered_metric-17]: started with pid [31496]
process[camera/disparity_depth-18]: started with pid [31515]
process[camera/disparity_registered_sw-19]: started with pid [31535]
process[camera/disparity_registered_hw-20]: started with pid [31548]
process[camera_base_link-21]: started with pid [31564]
process[camera_base_link1-22]: started with pid [31578]
process[camera_base_link2-23]: started with pid [31584]
process[camera_base_link3-24]: started with pid [31601]
[ INFO] [1529679797.793835112]: Number devices connected: 1
[ INFO] [1529679797.793876165]: 1. device on bus 000:00 is a Xbox NUI Camera (2ae) from Microsoft (45e) with serial id 'B00364212508033B'
[ INFO] [1529679797.795062244]: Searching for device with index = 1
[ INFO] [1529679798.101286493]: Starting a 3s RGB and Depth stream flush.
[ INFO] [1529679798.101385056]: Opened 'Xbox NUI Camera' on bus 0:0 with serial number 'B00364212508033B'
[ WARN] [1529679798.913528981]: Could not find any compatible depth output mode for 1. Falling back to default depth output mode 1.
[ INFO] [1529679798.922463857]: rgb_frame_id = 'camera_rgb_optical_frame' 
[ INFO] [1529679798.922501712]: depth_frame_id = 'camera_depth_optical_frame' 
[ WARN] [1529679798.933344418]: Camera calibration file /home/joseph/.ros/camera_info/rgb_B00364212508033B.yaml not found.
[ WARN] [1529679798.933398102]: Using default parameters for RGB camera calibration.
[ WARN] [1529679798.933451016]: Camera calibration file /home/joseph/.ros/camera_info/depth_B00364212508033B.yaml not found.
[ WARN] [1529679798.933490316]: Using default parameters for IR camera calibration.
[ INFO] [1529679801.462710576]: Stopping device RGB and Depth stream flush.
terminate called after throwing an instance of 'std::runtime_error'
  what():  freenect_process_events error
[camera/camera_nodelet_manager-1] process has died [pid 31300, exit code -6, cmd /opt/ros/kinetic/lib/nodelet/nodelet manager __name:=camera_nodelet_manager __log:=/home/joseph/.ros/log/20e22f20-7620-11e8-95d0-3065ec753340/camera-camera_nodelet_manager-1.log].
log file: /home/joseph/.ros/log/20e22f20-7620-11e8-95d0-3065ec753340/camera-camera_nodelet_manager-1*.log
lucbettaieb commented 6 years ago

Hey guys, this was an issue regarding running freenect and then my kinect literally not turning on anymore. Is that what happened to you?

lucbettaieb commented 6 years ago

Looking in the source, this looks like it might be related to the device not being recognized. I'm going to reopen this to see if there can be an explanation.

lucbettaieb commented 6 years ago

@piyushk Any idea if this line is related to a hardware failure?

https://github.com/ros-drivers/freenect_stack/blob/44a573e6176fe357fb61326dd36a7d207d4c98c6/freenect_camera/include/freenect_camera/freenect_driver.hpp#L95

GmGniap commented 6 years ago

I'm getting errors like this (both laptop & Rpi ROS Kinetic version) , do you find any solutions ? When I search on web , some said it's bcoz of memory allocation(not enough memory error) . I think I'm being mad with this shit error :')

lucbettaieb commented 6 years ago

What kind of raspberry pi are you using? I'd not be surprised if it's because there's not enough memory on the board.

frannecki commented 6 years ago

Have you ever considered usb autosuspend? I've had a similar problem and finally solved it. Just look at this post it might help https://devtalk.nvidia.com/default/topic/746596/embedded-systems/usb3-port-not-providing-continuous-power-/post/4239121/#4239121

frannecki commented 6 years ago

Have you ever considered usb autosuspend? I've had a similar problem and finally solved it. Just look at this post it might help https://devtalk.nvidia.com/default/topic/746596/embedded-systems/usb3-port-not-providing-continuous-power-/post/4239121/#4239121

I think you need to copy the link and open it in a new tab

jiusan0327 commented 4 years ago

hello,i meet the same problem......i use vmware ,yesterday i use rgbg+ros+kinectv1 works ; but in the second day, the errors out: two situation here: 1. i launch freenect , then loop [ INFO] [1605787660.980057731]: Starting a 3s RGB and Depth stream flush.[ INFO] [1605787663.981905634]: Stopping device RGB and Depth stream flush. 2. i launch freenect , it first works ; but when i launch ORB_SLAM2 with ROS ,the terminal of freenect also loop Starting........Stopping.....,and terminal of ORB_SLAM2 's image window is black

czr23648 commented 1 year ago

I found the question about it,For this error,because you use the USB2.0 interface，you have to USB3.0 or obove.