start-jsk / jsk_apc

Other
36 stars 35 forks source link

kinect2をつなげると以下のエラーになる #1042

Closed ban-masa closed 8 years ago

ban-masa commented 8 years ago

学科PCを利用。 sheetaでも同じエラーが出ている気がします。 rosrun libfreenect2 Protonect はRGB画面は表示されている。デプスは出ていないように見える。

$ roslaunch kinect2_bridge kinect2_bridge.launch
... logging to /home/mech-user/.ros/log/a467747c-ca42-11e5-a00d-e8b1fce9990e/roslaunch-test1-pc-592.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://test1-pc:59414/

SUMMARY
========

PARAMETERS
 * /kinect2/nodelets: [{'type': 'kinect...
 * /kinect2_bridge/base_name: kinect2
 * /kinect2_bridge/base_name_tf: kinect2
 * /kinect2_bridge/bilateral_filter: True
 * /kinect2_bridge/calib_path: /home/mech-user/r...
 * /kinect2_bridge/depth_device: -1
 * /kinect2_bridge/depth_method: default
 * /kinect2_bridge/edge_aware_filter: True
 * /kinect2_bridge/fps_limit: -1.0
 * /kinect2_bridge/jpeg_quality: 90
 * /kinect2_bridge/max_depth: 12.0
 * /kinect2_bridge/min_depth: 0.1
 * /kinect2_bridge/png_level: 1
 * /kinect2_bridge/publish_tf: False
 * /kinect2_bridge/queue_size: 5
 * /kinect2_bridge/reg_devive: -1
 * /kinect2_bridge/reg_method: default
 * /kinect2_bridge/sensor: 
 * /kinect2_bridge/use_png: False
 * /kinect2_bridge/worker_threads: 4
 * /kinect2_points_xyzrgb_hd/queue_size: 5
 * /kinect2_points_xyzrgb_qhd/queue_size: 5
 * /kinect2_points_xyzrgb_sd/queue_size: 5
 * /rosdistro: indigo
 * /rosversion: 1.11.16

NODES
  /
    kinect2 (jsk_topic_tools/standalone_complexed_nodelet)

ROS_MASTER_URI=http://localhost:11311

core service [/rosout] found
process[kinect2-1]: started with pid [614]
[ INFO] [1454504426.681142796]: [int main(int, char**)] i_nodelet 0
parameter:
        base_name: kinect2
           sensor: 
        fps_limit: -1
       calib_path: /home/mech-user/ros_ws/ws_jsk_apc/src/iai_kinect2/kinect2_bridge/data/
          use_png: false
     jpeg_quality: 90
        png_level: 1
     depth_method: default
     depth_device: -1
       reg_method: default
       reg_devive: -1
        max_depth: 12
        min_depth: 0.1
       queue_size: 5
 bilateral_filter: true
edge_aware_filter: true
       publish_tf: false
     base_name_tf: kinect2
   worker_threads: 4

terminate called after throwing an instance of 'std::system_error'
  what():  Invalid argument
[kinect2-1] process has died [pid 614, exit code -6, cmd /opt/ros/indigo/lib/jsk_topic_tools/standalone_complexed_nodelet __name:=kinect2 __log:=/home/mech-user/.ros/log/a467747c-ca42-11e5-a00d-e8b1fce9990e/kinect2-1.log].
log file: /home/mech-user/.ros/log/a467747c-ca42-11e5-a00d-e8b1fce9990e/kinect2-1*.log
[kinect2-1] restarting process
process[kinect2-1]: started with pid [687]
[ INFO] [1454504426.921079986]: [int main(int, char**)] i_nodelet 0
^C[kinect2-1] killing on exit
parameter:
        base_name: kinect2
           sensor: 
        fps_limit: -1
       calib_path: /home/mech-user/ros_ws/ws_jsk_apc/src/iai_kinect2/kinect2_bridge/data/
          use_png: false
     jpeg_quality: 90
        png_level: 1
     depth_method: default
     depth_device: -1
       reg_method: opencl
       reg_devive: -1
        max_depth: 12
        min_depth: 0.1
       queue_size: 5
 bilateral_filter: true
edge_aware_filter: true
       publish_tf: false
     base_name_tf: kinect2
   worker_threads: 4

terminate called after throwing a
wkentaro commented 8 years ago

You can try

roslaunch kinect2_bridge kinect2_bridge.launch depth_method:=cpu reg_method:=cpu
wkentaro commented 8 years ago

Reopen this if you have still the error.