Open gyt290811 opened 1 year ago
I meet this issue, too. In future if it will be solved , could some one can reply @me. Very Very Very thanks.
I meet this issue, too. In future if it will be solved , could some one can reply @me. Very Very Very thanks.
I have solved this issue. Chang a usb3.2 gen2 line. It is because of usb port or usb line
This ROS node is built on the Azure Kinect SDK. The SDK is not supported on Linux beyond 18.04 (https://github.com/microsoft/Azure-Kinect-Sensor-SDK/issues/1263). With the Azure Kinect DK being end of life, the sdk will not be supported on 20.04 or later.
Describe the bug I am using an MCU external hardware to trigger the Azure Kinect DK(only one camera) in the
Sub external sync
(slaver mode), and it can be successfully triggered in the SDK. When using the [official ROS package]wired_sync_mode=0
(https://github.com/microsoft/Azure_Kinect_ROS_Driver) without modifying anything, it can run. However, after changing thewired_sync_mode=2
inkinect_rgb.launch
, the ROS package cannot run properly and and I encounter the error([FATAL] [1691069372.183638523]: Failed to poll cameras: node cannot continue.) shown in the screenshot.Expected behavior Azure Kinect DK is waiting to work until pulse trigger.
Logs [ WARN] [1691069368.183421662]: Camera calibration file /home/yc/.ros/camera_info/azure_kinect_rgb_000863414212_1536P.yaml not found. [ INFO] [1691069368.183456550]: using default calibration URL [ INFO] [1691069368.183473747]: camera calibration URL: file:///home/yc/.ros/camera_info/azure_kinect_ir_000863414212_NFOV_UNBINNED.yaml [ INFO] [1691069368.183495708]: Unable to open camera calibration file [/home/yc/.ros/camera_info/azure_kinect_ir_000863414212_NFOV_UNBINNED.yaml] [ WARN] [1691069368.183515008]: Camera calibration file /home/yc/.ros/camera_info/azure_kinect_ir_000863414212_NFOV_UNBINNED.yaml not found. [ INFO] [1691069368.183793842]: IMU started [FATAL] [1691069372.183638523]: Failed to poll cameras: node cannot continue. [k4a_nodelet_manager-4] process has finished cleanly log file: /home/yc/.ros/log/c3e91d08-3201-11ee-922d-292bbb9d97a8/k4a_nodelet_manager-4*.log
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context