You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem with: roslaunch openni_launch openni.launch
ROS Melodic installed from source on RockPro64 board on Ubuntu 18.04.
I suspect this is due to not having the driver installed properly, which I seem to be unable to install on this platform. The SensorKinect driver installation results in the system telling me the arch64 or something like that, is not found. I assume that means the driver is not supported on this platform but I'm not sure. Is there something for a driver I should use that is more up to date than this https://github.com/avin2/SensorKinect ?
I confirmed Kinect Xbox 360 has enough power and works fine when I plug it into skanect on my laptop.
lsusb shows:
Bus 005 Device 007: ID 045e:02ae Microsoft Corp. Xbox NUI Camera
Bus 005 Device 005: ID 045e:02b0 Microsoft Corp. Xbox NUI Motor
Bus 005 Device 006: ID 045e:02ad Microsoft Corp. Xbox NUI Audio
How should I troubleshoot further?
rock64@rockpro64:~/turtlebot_melodic_ws$ roslaunch openni_launch openni.launch
... logging to /home/rock64/.ros/log/84d01db8-517f-11e9-aabc-9cefd5fdd5ab/roslaunch-rockpro64-8999.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.
process[camera/camera_nodelet_manager-1]: started with pid [9014]
process[camera/driver-2]: started with pid [9015]
process[camera/rgb_debayer-3]: started with pid [9016]
process[camera/rgb_rectify_mono-4]: started with pid [9017]
process[camera/rgb_rectify_color-5]: started with pid [9022]
process[camera/ir_rectify_ir-6]: started with pid [9024]
process[camera/depth_rectify_depth-7]: started with pid [9035]
process[camera/depth_metric_rect-8]: started with pid [9040]
[ INFO] [1553794779.708520778]: Initializing nodelet with 4 worker threads.
process[camera/depth_metric-9]: started with pid [9051]
process[camera/depth_points-10]: started with pid [9057]
process[camera/register_depth_rgb-11]: started with pid [9063]
process[camera/points_xyzrgb_sw_registered-12]: started with pid [9073]
[ INFO] [1553794779.839760437]: No devices connected.... waiting for devices to be connected
process[camera/depth_registered_sw_metric_rect-13]: started with pid [9077]
process[camera/depth_registered_rectify_depth-14]: started with pid [9084]
process[camera/points_xyzrgb_hw_registered-15]: started with pid [9092]
process[camera/depth_registered_hw_metric_rect-16]: started with pid [9099]
process[camera/depth_registered_metric-17]: started with pid [9106]
process[camera/disparity_depth-18]: started with pid [9112]
process[camera/disparity_registered_sw-19]: started with pid [9121]
process[camera/disparity_registered_hw-20]: started with pid [9124]
process[camera_base_link-21]: started with pid [9130]
process[camera_base_link1-22]: started with pid [9131]
process[camera_base_link2-23]: started with pid [9137]
process[camera_base_link3-24]: started with pid [9143]
[ INFO] [1553794782.840642615]: No devices connected.... waiting for devices to be connected
[ INFO] [1553794785.841515084]: No devices connected.... waiting for devices to be connected
The text was updated successfully, but these errors were encountered:
Problem with: roslaunch openni_launch openni.launch
ROS Melodic installed from source on RockPro64 board on Ubuntu 18.04.
I suspect this is due to not having the driver installed properly, which I seem to be unable to install on this platform. The SensorKinect driver installation results in the system telling me the arch64 or something like that, is not found. I assume that means the driver is not supported on this platform but I'm not sure. Is there something for a driver I should use that is more up to date than this https://github.com/avin2/SensorKinect ?
I confirmed Kinect Xbox 360 has enough power and works fine when I plug it into skanect on my laptop.
lsusb shows:
Bus 005 Device 007: ID 045e:02ae Microsoft Corp. Xbox NUI Camera
Bus 005 Device 005: ID 045e:02b0 Microsoft Corp. Xbox NUI Motor
Bus 005 Device 006: ID 045e:02ad Microsoft Corp. Xbox NUI Audio
How should I troubleshoot further?
rock64@rockpro64:~/turtlebot_melodic_ws$ roslaunch openni_launch openni.launch
... logging to /home/rock64/.ros/log/84d01db8-517f-11e9-aabc-9cefd5fdd5ab/roslaunch-rockpro64-8999.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://192.168.1.132:37526/
SUMMARY
PARAMETERS
NODES
/camera/
camera_nodelet_manager (nodelet/nodelet)
depth_metric (nodelet/nodelet)
depth_metric_rect (nodelet/nodelet)
depth_points (nodelet/nodelet)
depth_rectify_depth (nodelet/nodelet)
depth_registered_hw_metric_rect (nodelet/nodelet)
depth_registered_metric (nodelet/nodelet)
depth_registered_rectify_depth (nodelet/nodelet)
depth_registered_sw_metric_rect (nodelet/nodelet)
disparity_depth (nodelet/nodelet)
disparity_registered_hw (nodelet/nodelet)
disparity_registered_sw (nodelet/nodelet)
driver (nodelet/nodelet)
ir_rectify_ir (nodelet/nodelet)
points_xyzrgb_hw_registered (nodelet/nodelet)
points_xyzrgb_sw_registered (nodelet/nodelet)
register_depth_rgb (nodelet/nodelet)
rgb_debayer (nodelet/nodelet)
rgb_rectify_color (nodelet/nodelet)
rgb_rectify_mono (nodelet/nodelet)
/
camera_base_link (tf2_ros/static_transform_publisher)
camera_base_link1 (tf2_ros/static_transform_publisher)
camera_base_link2 (tf2_ros/static_transform_publisher)
camera_base_link3 (tf2_ros/static_transform_publisher)
ROS_MASTER_URI=http://localhost:11311
process[camera/camera_nodelet_manager-1]: started with pid [9014]
process[camera/driver-2]: started with pid [9015]
process[camera/rgb_debayer-3]: started with pid [9016]
process[camera/rgb_rectify_mono-4]: started with pid [9017]
process[camera/rgb_rectify_color-5]: started with pid [9022]
process[camera/ir_rectify_ir-6]: started with pid [9024]
process[camera/depth_rectify_depth-7]: started with pid [9035]
process[camera/depth_metric_rect-8]: started with pid [9040]
[ INFO] [1553794779.708520778]: Initializing nodelet with 4 worker threads.
process[camera/depth_metric-9]: started with pid [9051]
process[camera/depth_points-10]: started with pid [9057]
process[camera/register_depth_rgb-11]: started with pid [9063]
process[camera/points_xyzrgb_sw_registered-12]: started with pid [9073]
[ INFO] [1553794779.839760437]: No devices connected.... waiting for devices to be connected
process[camera/depth_registered_sw_metric_rect-13]: started with pid [9077]
process[camera/depth_registered_rectify_depth-14]: started with pid [9084]
process[camera/points_xyzrgb_hw_registered-15]: started with pid [9092]
process[camera/depth_registered_hw_metric_rect-16]: started with pid [9099]
process[camera/depth_registered_metric-17]: started with pid [9106]
process[camera/disparity_depth-18]: started with pid [9112]
process[camera/disparity_registered_sw-19]: started with pid [9121]
process[camera/disparity_registered_hw-20]: started with pid [9124]
process[camera_base_link-21]: started with pid [9130]
process[camera_base_link1-22]: started with pid [9131]
process[camera_base_link2-23]: started with pid [9137]
process[camera_base_link3-24]: started with pid [9143]
[ INFO] [1553794782.840642615]: No devices connected.... waiting for devices to be connected
[ INFO] [1553794785.841515084]: No devices connected.... waiting for devices to be connected
The text was updated successfully, but these errors were encountered: