search

IntelRealSense / realsense-ros

ROS Wrapper for Intel(R) RealSense(TM) Cameras
http://wiki.ros.org/RealSense
Apache License 2.0
2.56k stars 1.75k forks source link

Cannot transform data showing"control_transfer returned error, index: 768, error: No data available, number: 61" with D435i #1162

Closed DanLCJ closed 4 years ago

DanLCJ commented 4 years ago

Operating System | Ubuntu 16.04 LTS Kernel | 4.15.0-66-generic ROS | kinetic 1.12.14

I have installed the librealsense2 packages and realsense-ros. Everything works correctly in realsense-viewer, but when I try to run 'roslaunch realsense2_camera rs_camera.launch', it seems that no data is returned. I assume I have installed an incorrect version of something alone the way. Here is my output below(I don't know how to adjust the format). Any suggestions?

SUMMARY

PARAMETERS

NODES /camera/ realsense2_camera (nodelet/nodelet) realsense2_camera_manager (nodelet/nodelet)

ROS_MASTER_URI=http://localhost:11311

process[camera/realsense2_camera_manager-1]: started with pid [32677] process[camera/realsense2_camera-2]: started with pid [32678] [ INFO] [1586601113.299678522]: Initializing nodelet with 8 worker threads. [ INFO] [1586601113.341707071]: RealSense ROS v2.2.13 [ INFO] [1586601113.341743521]: Running with LibRealSense v2.33.1 [ INFO] [1586601113.365734343]:
11/04 18:31:53,685 WARNING [140115629172480] (types.cpp:49) hwmon command 0x4f failed. Error type: No data to return (-21). 11/04 18:31:53,686 WARNING [140115629172480] (ds5-motion.cpp:463) IMU Calibration is not available, see the previous message [ INFO] [1586601113.738022140]: Device with serial number 902512070115 was found.

[ INFO] [1586601113.738081280]: Device with physical ID 4-1-9 was found. [ INFO] [1586601113.738122293]: Device with name Intel RealSense D435I was found. [ INFO] [1586601113.738996768]: Device with port number 4-1 was found.

[ INFO] [1586601113.801746310]: JSON file is not provided [ INFO] [1586601113.801762964]: ROS Node Namespace: camera [ INFO] [1586601113.801781270]: Device Name: Intel RealSense D435I [ INFO] [1586601113.801797186]: Device Serial No: 902512070115 [ INFO] [1586601113.801818116]: Device physical port: 4-1-9 [ INFO] [1586601113.801841824]: Device FW version: 05.11.11.100 [ INFO] [1586601113.801870049]: Device Product ID: 0x0B3A [ INFO] [1586601113.801896727]: Enable PointCloud: Off [ INFO] [1586601113.801943562]: Align Depth: Off [ INFO] [1586601113.801966709]: Sync Mode: Off [ INFO] [1586601113.802024679]: Device Sensors: [ INFO] [1586601113.802086588]: Stereo Module was found. [ INFO] [1586601113.802114342]: RGB Camera was found. [ INFO] [1586601113.802141766]: Motion Module was found. [ INFO] [1586601113.802179842]: (Fisheye, 0) sensor isn't supported by current device! -- Skipping... [ INFO] [1586601113.802201873]: (Fisheye, 1) sensor isn't supported by current device! -- Skipping... [ INFO] [1586601113.802216771]: (Fisheye, 2) sensor isn't supported by current device! -- Skipping... [ INFO] [1586601113.802240366]: (Pose, 0) sensor isn't supported by current device! -- Skipping... [ INFO] [1586601113.802278839]: num_filters: 0 [ INFO] [1586601113.802302934]: Setting Dynamic reconfig parameters. [ INFO] [1586601118.711545975]: Done Setting Dynamic reconfig parameters. [ INFO] [1586601118.744919923]: depth stream is enabled - width: 640, height: 480, fps: 30, Format: Z16 [ INFO] [1586601118.745126894]: infra1 stream is enabled - width: 640, height: 480, fps: 30, Format: Y8 [ INFO] [1586601118.745298568]: infra2 stream is enabled - width: 640, height: 480, fps: 30, Format: Y8 [ INFO] [1586601118.772367251]: color stream is enabled - width: 640, height: 480, fps: 30, Format: RGB8

[ INFO] [1586601118.775735545]: Expected frequency for depth = 30.00000 [ INFO] [1586601118.802831300]: Expected frequency for infra1 = 30.00000 [ INFO] [1586601118.827301473]: Expected frequency for infra2 = 30.00000 [ INFO] [1586601118.851213205]: Expected frequency for color = 30.00000

[ INFO] [1586601118.928627349]: insert Depth to Stereo Module [ INFO] [1586601118.928707448]: insert Color to RGB Camera [ INFO] [1586601118.928740254]: insert Infrared to Stereo Module [ INFO] [1586601118.928778424]: insert Infrared to Stereo Module [ INFO] [1586601118.928816208]: insert Gyro to Motion Module [ INFO] [1586601118.928851182]: insert Accel to Motion Module [ INFO] [1586601119.187584675]: SELECTED BASE:Depth, 0 [ INFO] [1586601119.234877541]: RealSense Node Is Up! 11/04 18:31:59,321 WARNING [140115523401472] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61 11/04 18:31:59,402 WARNING [140115523401472] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61 11/04 18:31:59,484 WARNING [140115523401472] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61 11/04 18:31:59,545 WARNING [140115523401472] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61 11/04 18:31:59,626 WARNING [140115523401472] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61 11/04 18:31:59,807 WARNING [140115523401472] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61 11/04 18:39:51,587 WARNING [140115523401472] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11 11/04 18:41:16,374 WARNING [140115523401472] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11 11/04 18:41:17,455 WARNING [140115523401472] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11

MartyG-RealSense commented 4 years ago

@doronhi the RealSense ROS wrapper developer has the following advice about the meaning of the control_transfer returned errors:

"The warning message "control_transfer returned error" reflects communication error with the device that is resolved by repeating the attempt. These messages are still under investigation but as long as they appear only now and then, say at the beginning of the run, they can safely be ignored for now".

"If the message "messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11" is continuous, that is appears multiple times per second, then it is not good. It suggest a real communication problem between the code and the device and can have effects".

What computer hardware are you using please (PC / Mac / Linux / Raspberry Pi / Jetson etc).

DanLCJ commented 4 years ago

@MartyG-RealSense I use Linux 16.04 LTS with intel i7

MartyG-RealSense commented 4 years ago

The errors are likely not related to a low computer specification if you have an i7 computer. At 640x480 resolution, you are not putting a heavy processing load on the computer either.

Your RealSense ROS and Librealsense versions (2.2.13 ROS, 2.33.1 Librealsense) are also correctly matched.

Do you know which firmware version your camera is using please? Firmware version 5.12.3.0 is recommended for the SDK that you are using. You can update the camera to the latest firmware by going to the 'More' icon at the top of the RealSense Viewer's side-panel and selecting the menu option 'Install Recommended Firmware'. You do not need a firmware file to do this, as the latest version of the firmware is bundled inside the SDK.

image

DanLCJ commented 4 years ago

@MartyG-RealSense I update my firmware just like you said as soon as your response, and now the firmware version is : 05.12.03.00, but it has no change launching rs_camera.launch. I notice that the output shows "IMU Calibration is not available", and others outputs don't have this information, is that the main problem?

MartyG-RealSense commented 4 years ago

If the IMU on the D435i has not been calibrated by the user then some programs may display this [-21] error. My understanding is that it should not be a problem if you are not accessing the IMU and its gyro and accelerometer sensors though.

Are you using the official short cable that was supplied with the camera please or are you using a cable of your own choice? RealSense needs a high quality cable, especially if the cable is 2 meters or more in length, and performance can degrade or the camera disconnect if an own-choice cable is not of sufficient quality.

DanLCJ commented 4 years ago

@MartyG-RealSense I use the official cable, now I'm truly comfused:(

MartyG-RealSense commented 4 years ago

Don't worry, this is a useful process because each new piece of information and answered question narrows down the possible causes for the problem. So it is very helpful. Thanks for your patience!

As the camera works fine for you in the RealSense Viewer, it is likely a problem related to the ROS wrapper. This would also suggest that you are not experiencing problems with power supply instability on your computer's USB ports, otherwise that would affect the camera's performance in the RealSense Viewer.

When you receive the control_transfer returned errors in the log, do they generate continuously or stop shortly after launch?

DanLCJ commented 4 years ago

It will generate continuously and after a few moments, output change into "(messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11" and then generate continuously.

MartyG-RealSense commented 4 years ago

Okay, thanks. It does sound like a more serious problem than just a short "hiccup" on the connection at launch then.

Are you able to use Rviz to check the camera output? Despite the log messages, if the camera output appears in Rviz then it should mean that the ROS topics are being published correctly.

DanLCJ commented 4 years ago

Camera output can appear in proper topic, I can show you screenshots later.

MartyG-RealSense commented 4 years ago

Ok, thank you very much. It is a good sign that you are getting the image topic published successfully.

DanLCJ commented 4 years ago

image I use RViz to check my camera output and it seems it has no problem about image topic.

ashirsat commented 4 years ago

Hey,

I read in the ROS documentation for real sense that you need realsense 2 packages and not realsense packages for the camera series that you have. Might be something that you would have tried earlier. But if not try it.

Aniket

On Sat, Apr 11, 2020 at 10:32 DanLiu0809 notifications@github.com wrote:

[image: image] https://user-images.githubusercontent.com/40844774/79050523-24d59000-7c5d-11ea-82a7-12274b54ab06.png I use RViz to check my camera output and it seems it has no problem about image topic.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/IntelRealSense/realsense-ros/issues/1162#issuecomment-612472338, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABO2QJXEMVQVSWAGUDJ634TRMCSRJANCNFSM4MF6NHRA .

-- Regards, Aniket Shirsat

Mechanical Graduate Arizona State University| Ira A. Fulton Schools of Engineering School for Engineering of Matter Transport and Energy Cell:(480)371-8843 Portfolio http://seelio.com/aniketshirsat http://www.linkedin.com/in/shirsataniket https://twitter.com/intent/follow?original_referer=https%3A%2F%2Fabout.twitter.com%2Fresources%2Fbuttons&region=follow_link&screen_name=AniketRShirsat&tw_p=followbutton

MartyG-RealSense commented 4 years ago

@DanLiu0809 Thanks for the RViz image!

@doronhi the ROS wrapper developer may be the best person to advise about how to deal with your log messages, based on the facts established about your situation earlier in this discussion. I have linked him into this discussion. I hope that the messages are not disruptive to your use of ROS in the meantime.

MartyG-RealSense commented 4 years ago

@ashirsat Thanks for your input! @DanLiu0809 is using realsense2_camera, which is the appropriate ROS package for the D435i camera (part of the 400 Series cameras).

image

ashirsat commented 4 years ago

Oops sorry about that. Missed that part.

On Sat, Apr 11, 2020 at 11:07 MartyG-RealSense notifications@github.com wrote:

@ashirsat https://github.com/ashirsat Thanks for your input! @DanLiu0809 https://github.com/DanLiu0809 is using realsense2_camera, which is the appropriate ROS package for the D435i camera (part of the 400 Series cameras).

[image: image] https://user-images.githubusercontent.com/41145062/79051345-98f54100-7c27-11ea-982e-d4acf6a7ad98.png

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/IntelRealSense/realsense-ros/issues/1162#issuecomment-612479871, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABO2QJSTMZTC73OZ4IVAP3TRMCWWXANCNFSM4MF6NHRA .

-- Regards, Aniket Shirsat

Mechanical Graduate Arizona State University| Ira A. Fulton Schools of Engineering School for Engineering of Matter Transport and Energy Cell:(480)371-8843 Portfolio http://seelio.com/aniketshirsat http://www.linkedin.com/in/shirsataniket https://twitter.com/intent/follow?original_referer=https%3A%2F%2Fabout.twitter.com%2Fresources%2Fbuttons&region=follow_link&screen_name=AniketRShirsat&tw_p=followbutton

MartyG-RealSense commented 4 years ago

@ashirsat No problem at all. It's great when community members are willing to help each other out!

MartyG-RealSense commented 4 years ago

@DanLiu0809 Were you able to resolve your problem, please? This case will be closed after 7 days from the time of writing this message if there are no further comments. Thank you.

yiiizuo commented 4 years ago

@ashirsat Thanks for your input! @DanLiu0809 is using realsense2_camera, which is the appropriate ROS package for the D435i camera (part of the 400 Series cameras).

@MartyG-RealSense Can I run it through D435? I have the same problem as@DanLiu0809

MartyG-RealSense commented 4 years ago

@17602357904 Using D435 with realsense2_camera is fine.

yiiizuo commented 4 years ago

@DanLiu0809 Did you solve the problem? Can you give your way？

DanLCJ commented 4 years ago

@17602357904 I actually cannot solve this problem still, but I try avoiding this problem by adding exacting topic to my rviz in terminal. It seems this problem is because the data from D435i cannot find a proper port to output[my partial opinion].

DanLCJ commented 4 years ago

Now I'm trying to change the environment, like I upgrade my OS to Ubuntu 18.04 and also ROS from Kinetic to Melodic, to see whether it has some different changes.

yiiizuo commented 4 years ago

@DanLiu0809 Thanks for your answer.How to add strict theme to rviz in terminal to avoid this problem? If you have made any progress, please notify me. Thank you very much!

doronhi commented 4 years ago

I am trying to understand your issue @DanLiu0809, although it seems obvious to other people... You mention that using RViz you can see the topics fine so, is the issue the warnings that appear continuously? What did you mean by "adding exacting topic to my rviz in terminal"? What exactly is the problem you try to avoid? Due to the whole covid-19 issue it will probably take me a long while to check on this issue again. My sincere apologies.

DanLCJ commented 4 years ago

@doronhi That's OK and thanks for your comment! I use rtabmap to do the SLAM things, and when I start the camera node, I get these warning notice continuously; if I don't stop the terminal, it will repeat this warning. But when I open rviz to check the camera, it can get the pictures rightfully with RGBD and depth graphs; when I launch rtabmap launchfile then, rtabmap can work properly and camera-node has the same warning repeating. At first I think maybe several essential-libs are not installed, but since rviz and rtabmap can both work properly, I'm truly comfusing. If you have any suggestions please contact me. Thank you.

doronhi commented 4 years ago

I tested the latest version with librealsense PR#6150 on my VMWare machine (Ubuntu 18.04). I counted 1277 occurrences of "control_transfer returned error..." in 19 hours run. That's an average of around 1 warning per minute. Is this the approximate rate you also see? I didn't see any operative problem caused by it. That's been said, I'll look into it and see how to handle or remove this warning which is annoying in the best scenario and troubling otherwise. Until that time, if the rate the warnings appear for you is something similar to my testings, I believe you can carry on safely with your work.

DanLCJ commented 4 years ago

OK it seems that the appearing rate of this warnings is the same of yours, and it has not influenced my work recently. I'll close this issue and hope you can fix this warning notice soon. Thanks again!

sadransh commented 4 years ago

I experienced similar issue on d435 ( like what @doronhi told) on firmware 05.09.02.00. On d435i(with firmware 05.12.02.100) this happened and no output e.g. on /d400/color/image_raw : 

 04/06 18:14:02,670 WARNING [547161854336] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 04/06 18:14:03,145 WARNING [547161854336] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 04/06 18:14:04,834 WARNING [546903667072] (uvc-device.cpp:644) interrupt event received: 1, 3, 0, 7, 0, 13, 
[ WARN] [1591312445.016228104]: Hardware Notification:USB CAM overflow,1.59131e+12,Error,Hardware Error
 04/06 18:14:06,894 WARNING [546903667072] (uvc-device.cpp:644) interrupt event received: 1, 3, 0, 7, 0, 13, 
[ WARN] [1591312447.056337641]: Hardware Notification:USB CAM overflow,1.59131e+12,Error,Hardware Error
 04/06 18:14:08,946 WARNING [546937237888] (uvc-device.cpp:644) interrupt event received: 1, 3, 0, 7, 0, 13, 
[ WARN] [1591312449.091244113]: Hardware Notification:USB CAM overflow,1.59131e+12,Error,Hardware Error
 04/06 18:14:10,982 WARNING [547203817856] (uvc-device.cpp:644) interrupt event received: 1, 3, 0, 7, 0, 13, 
[ WARN] [1591312451.123730312]: Hardware Notification:USB CAM overflow,1.59131e+12,Error,Hardware Error
 04/06 18:14:13,034 WARNING [546937237888] (uvc-device.cpp:644) interrupt event received: 1, 3, 0, 7, 0, 13, 
[ WARN] [1591312453.155249039]: Hardware Notification:USB CAM overflow,1.59131e+12,Error,Hardware Error
 04/06 18:14:15,086 WARNING [547203817856] (uvc-device.cpp:644) interrupt event received: 1, 3, 0, 7, 0, 13, 
[ WARN] [1591312455.192474103]: Hardware Notification:USB CAM overflow,1.59131e+12,Error,Hardware Error
 04/06 18:14:17,138 WARNING [546903667072] (uvc-device.cpp:644) interrupt event received: 1, 3, 0, 7, 0, 13, 
[ WARN] [1591312457.227373933]: Hardware Notification:USB CAM overflow,1.59131e+12,Error,Hardware Error
 04/06 18:14:19,190 WARNING [547203817856] (uvc-device.cpp:644) interrupt event received: 1, 3, 0, 7, 0, 13, 
[ WARN] [1591312459.262550902]: Hardware Notification:USB CAM overflow,1.59131e+12,Error,Hardware Error
 04/06 18:14:21,242 WARNING [546937237888] (uvc-device.cpp:644) interrupt event received: 1, 3, 0, 7, 0, 13, 
[ WARN] [1591312461.295108942]: Hardware Notification:USB CAM overflow,1.59131e+12,Error,Hardware Error
 04/06 18:14:23,294 WARNING [546903667072] (uvc-device.cpp:644) interrupt event received: 1, 3, 0, 7, 0, 13, 
[ WARN] [1591312463.340762645]: Hardware Notification:USB CAM overflow,1.59131e+12,Error,Hardware Error
 04/06 18:14:25,342 WARNING [546937237888] (uvc-device.cpp:644) interrupt event received: 1, 3, 0, 7, 0, 13, 
[ WARN] [1591312465.378150815]: Hardware Notification:USB CAM overflow,1.59131e+12,Error,Hardware Error
 04/06 18:14:27,406 WARNING [546903667072] (uvc-device.cpp:644) interrupt event received: 1, 3, 0, 7, 0, 13, 
[ WARN] [1591312467.418816322]: Hardware Notification:USB CAM overflow,1.59131e+12,Error,Hardware Error
 04/06 18:14:29,458 WARNING [547203817856] (uvc-device.cpp:644) interrupt event received: 1, 3, 0, 7, 0, 13,
MartyG-RealSense commented 4 years ago

@sadransh The USB CAM overflow error suggests that there is a greater volume of data being processed by the USB system than it can handle. This may be related to the particular computer hardware that you are using, and the same program may not produce the errors on a different computer.

You may be able to reduce the strain put on the USB by adding to your roslaunch statement the instruction enable_infra2:=false to disable the Infra2 channel.

It saves on USB transportation and kernel work, according to Doronhi the RealSense ROS wrapper developer. Doronhi adds "It will have no effect on the depth quality. It only disables the infra2 images' transmission via the USB port. They are still taken and the depth is calculated using them inside the device.".

sadransh commented 4 years ago

@MartyG-RealSense Thanks for the answer, yes I am using Jetson TX2, I have already turned off both infras. The point is just switching from d435i(with firmware 05.12.02.100) to d435 (firmware 05.09.02.00) resolves the USB CAM overflow without any other changes( on d435 just some control_transfer error every minute). And I think it's kind of weird.

other information for my device : kernel version 4.9.1xx-tegra ubuntu 18.04 Jetson TX2 on Jetpack 4.3 liberalsense 2.32.1 ( installed using apt-get) relasense-ros cloned from development branch a few days ago.

MartyG-RealSense commented 4 years ago

@sadransh Doronhi the RealSense ROS developer has said that if you are only receiving a control_transfer returned warning at a rate of about one a minute then it is safe to work with the ROS wrapper, and he has been looking at how to handle or remove the warning.

https://github.com/IntelRealSense/realsense-ros/issues/1162#issuecomment-624129592

Regarding the USB CAM Overflow errors: a couple of RealSense users had continuously-generating errors disappear this week by upgrading to the new 5.12.5 firmware. It may be worth trying that with your D435i. Then you have still got the D435 and its 05.09.02.00 firmware as backup if the firmware upgrade does not make a difference.

Eslamrady42 commented 4 years ago

I have exact the same error !!

victorll998 commented 3 years ago

@MartyG-RealSense I have encounter this issue with an average rate of 3 sec. Could you have a look into my situation?

I have two d455 and t265 running on Intel NUC (i7). I tested with the cables in box and a powered USB hub. When only one d455 and t265 connected, the control_transfer returned error has been refrained after a few second when nodes initialize. But when I tried to connect two d455 and t265, one of the d455 would retain the control transfer error at a high frequency while the other d455 is fine.

camera 1 continue to give me the error 

SUMMARY
========

PARAMETERS
 * /cam_1/realsense2_camera/accel_fps: -1
 * /cam_1/realsense2_camera/accel_frame_id: cam_1_accel_frame
 * /cam_1/realsense2_camera/accel_optical_frame_id: cam_1_accel_optic...
 * /cam_1/realsense2_camera/align_depth: False
 * /cam_1/realsense2_camera/aligned_depth_to_color_frame_id: cam_1_aligned_dep...
 * /cam_1/realsense2_camera/aligned_depth_to_fisheye1_frame_id: cam_1_aligned_dep...
 * /cam_1/realsense2_camera/aligned_depth_to_fisheye2_frame_id: cam_1_aligned_dep...
 * /cam_1/realsense2_camera/aligned_depth_to_fisheye_frame_id: cam_1_aligned_dep...
 * /cam_1/realsense2_camera/aligned_depth_to_infra1_frame_id: cam_1_aligned_dep...
 * /cam_1/realsense2_camera/aligned_depth_to_infra2_frame_id: cam_1_aligned_dep...
 * /cam_1/realsense2_camera/allow_no_texture_points: False
 * /cam_1/realsense2_camera/base_frame_id: cam_1_link
 * /cam_1/realsense2_camera/calib_odom_file: 
 * /cam_1/realsense2_camera/clip_distance: -2.0
 * /cam_1/realsense2_camera/color_fps: -1
 * /cam_1/realsense2_camera/color_frame_id: cam_1_color_frame
 * /cam_1/realsense2_camera/color_height: -1
 * /cam_1/realsense2_camera/color_optical_frame_id: cam_1_color_optic...
 * /cam_1/realsense2_camera/color_width: -1
 * /cam_1/realsense2_camera/confidence_fps: -1
 * /cam_1/realsense2_camera/confidence_height: -1
 * /cam_1/realsense2_camera/confidence_width: -1
 * /cam_1/realsense2_camera/depth_fps: -1
 * /cam_1/realsense2_camera/depth_frame_id: cam_1_depth_frame
 * /cam_1/realsense2_camera/depth_height: -1
 * /cam_1/realsense2_camera/depth_optical_frame_id: cam_1_depth_optic...
 * /cam_1/realsense2_camera/depth_width: -1
 * /cam_1/realsense2_camera/device_type: 
 * /cam_1/realsense2_camera/enable_accel: False
 * /cam_1/realsense2_camera/enable_color: True
 * /cam_1/realsense2_camera/enable_confidence: True
 * /cam_1/realsense2_camera/enable_depth: True
 * /cam_1/realsense2_camera/enable_fisheye1: False
 * /cam_1/realsense2_camera/enable_fisheye2: False
 * /cam_1/realsense2_camera/enable_fisheye: False
 * /cam_1/realsense2_camera/enable_gyro: False
 * /cam_1/realsense2_camera/enable_infra1: False
 * /cam_1/realsense2_camera/enable_infra2: False
 * /cam_1/realsense2_camera/enable_infra: False
 * /cam_1/realsense2_camera/enable_pointcloud: False
 * /cam_1/realsense2_camera/enable_pose: False
 * /cam_1/realsense2_camera/enable_sync: False
 * /cam_1/realsense2_camera/filters: spatial,temporal,...
 * /cam_1/realsense2_camera/fisheye1_frame_id: cam_1_fisheye1_frame
 * /cam_1/realsense2_camera/fisheye1_optical_frame_id: cam_1_fisheye1_op...
 * /cam_1/realsense2_camera/fisheye2_frame_id: cam_1_fisheye2_frame
 * /cam_1/realsense2_camera/fisheye2_optical_frame_id: cam_1_fisheye2_op...
 * /cam_1/realsense2_camera/fisheye_fps: -1
 * /cam_1/realsense2_camera/fisheye_frame_id: cam_1_fisheye_frame
 * /cam_1/realsense2_camera/fisheye_height: -1
 * /cam_1/realsense2_camera/fisheye_optical_frame_id: cam_1_fisheye_opt...
 * /cam_1/realsense2_camera/fisheye_width: -1
 * /cam_1/realsense2_camera/gyro_fps: -1
 * /cam_1/realsense2_camera/gyro_frame_id: cam_1_gyro_frame
 * /cam_1/realsense2_camera/gyro_optical_frame_id: cam_1_gyro_optica...
 * /cam_1/realsense2_camera/imu_optical_frame_id: cam_1_imu_optical...
 * /cam_1/realsense2_camera/infra1_frame_id: cam_1_infra1_frame
 * /cam_1/realsense2_camera/infra1_optical_frame_id: cam_1_infra1_opti...
 * /cam_1/realsense2_camera/infra2_frame_id: cam_1_infra2_frame
 * /cam_1/realsense2_camera/infra2_optical_frame_id: cam_1_infra2_opti...
 * /cam_1/realsense2_camera/infra_fps: -1
 * /cam_1/realsense2_camera/infra_height: -1
 * /cam_1/realsense2_camera/infra_rgb: False
 * /cam_1/realsense2_camera/infra_width: -1
 * /cam_1/realsense2_camera/initial_reset: False
 * /cam_1/realsense2_camera/json_file_path: 
 * /cam_1/realsense2_camera/linear_accel_cov: 0.01
 * /cam_1/realsense2_camera/odom_frame_id: cam_1_odom_frame
 * /cam_1/realsense2_camera/ordered_pc: False
 * /cam_1/realsense2_camera/pointcloud_texture_index: 0
 * /cam_1/realsense2_camera/pointcloud_texture_stream: RS2_STREAM_COLOR
 * /cam_1/realsense2_camera/pose_frame_id: cam_1_pose_frame
 * /cam_1/realsense2_camera/pose_optical_frame_id: cam_1_pose_optica...
 * /cam_1/realsense2_camera/publish_odom_tf: True
 * /cam_1/realsense2_camera/publish_tf: True
 * /cam_1/realsense2_camera/rosbag_filename: 
 * /cam_1/realsense2_camera/serial_no: 043422252203
 * /cam_1/realsense2_camera/tf_publish_rate: 0.0
 * /cam_1/realsense2_camera/topic_odom_in: odom_in
 * /cam_1/realsense2_camera/unite_imu_method: 
 * /cam_1/realsense2_camera/usb_port_id: 
 * /rosdistro: noetic
 * /rosversion: 1.15.9

NODES
  /cam_1/
    realsense2_camera (nodelet/nodelet)
    realsense2_camera_manager (nodelet/nodelet)

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

setting /run_id to aa0d55fe-abd8-11eb-9336-09217049c0b5
process[rosout-1]: started with pid [23469]
started core service [/rosout]
process[cam_1/realsense2_camera_manager-2]: started with pid [23476]
process[cam_1/realsense2_camera-3]: started with pid [23477]
[ INFO] [1620023262.345482099]: Initializing nodelet with 8 worker threads.
[ INFO] [1620023262.416752428]: RealSense ROS v2.2.22
[ INFO] [1620023262.416778443]: Built with LibRealSense v2.42.0
[ INFO] [1620023262.416790908]: Running with LibRealSense v2.42.0
[ INFO] [1620023262.436847633]:  
[ INFO] [1620023262.551867033]: Device with serial number * was found.

[ INFO] [1620023262.551903262]: Device with physical ID 2-2.2-6 was found.
[ INFO] [1620023262.551914050]: Device with name Intel RealSense D455 was found.
[ INFO] [1620023262.552201380]: Device with port number 2-2.2 was found.
[ INFO] [1620023262.552221755]: Device USB type: 3.2
[ INFO] [1620023262.553290865]: getParameters...
[ INFO] [1620023262.576237792]: setupDevice...
[ INFO] [1620023262.576256226]: JSON file is not provided
[ INFO] [1620023262.576262414]: ROS Node Namespace: cam_1
[ INFO] [1620023262.576285174]: Device Name: Intel RealSense D455
[ INFO] [1620023262.576301647]: Device Serial No: *
[ INFO] [1620023262.576307642]: Device physical port: 2-2.2-6
[ INFO] [1620023262.576312908]: Device FW version: 05.12.13.50
[ INFO] [1620023262.576318280]: Device Product ID: 0x0B5C
[ INFO] [1620023262.576330684]: Enable PointCloud: On
[ INFO] [1620023262.576335357]: Align Depth: Off
[ INFO] [1620023262.576341192]: Sync Mode: On
[ INFO] [1620023262.576365876]: Device Sensors: 
[ INFO] [1620023262.595513946]: Stereo Module was found.
[ INFO] [1620023262.605558917]: RGB Camera was found.
[ INFO] [1620023262.605742608]: Motion Module was found.
[ INFO] [1620023262.605760666]: (Confidence, 0) sensor isn't supported by current device! -- Skipping...
[ INFO] [1620023262.605772284]: Add Filter: spatial
[ INFO] [1620023262.606121245]: Add Filter: temporal
[ INFO] [1620023262.606420971]: Add Filter: pointcloud
[ INFO] [1620023262.606703641]: num_filters: 3
[ INFO] [1620023262.606717299]: Setting Dynamic reconfig parameters.
 03/05 16:27:42,950 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11
 03/05 16:27:43,028 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
[ INFO] [1620023263.142969824]: Done Setting Dynamic reconfig parameters.
[ INFO] [1620023263.143315334]: depth stream is enabled - width: 848, height: 480, fps: 30, Format: Z16
[ INFO] [1620023263.144031117]: color stream is enabled - width: 1280, height: 720, fps: 30, Format: RGB8
[ INFO] [1620023263.144053350]: setupPublishers...
[ INFO] [1620023263.145098161]: Expected frequency for depth = 30.00000
[ INFO] [1620023263.160099817]: Expected frequency for color = 30.00000
[ INFO] [1620023263.169803601]: setupStreams...
[ INFO] [1620023263.191124117]: insert Depth to Stereo Module
[ INFO] [1620023263.191211562]: insert Color to RGB Camera
[ INFO] [1620023263.256879785]: SELECTED BASE:Depth, 0
[ INFO] [1620023263.263746077]: RealSense Node Is Up!
 03/05 16:27:43,337 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 300, error: No data available, number: 3d
 03/05 16:27:43,387 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 300, error: No data available, number: 3d
[ WARN] [1620023263.519449911]: 
 03/05 16:27:43,519 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:43,570 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:43,620 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:43,671 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:43,722 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 300, error: No data available, number: 3d
 03/05 16:27:43,773 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:43,823 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:43,874 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:43,926 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:44,077 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:44,629 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:44,780 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:48,234 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:50,285 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:51,335 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:51,386 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:53,437 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:54,487 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:55,538 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:57,589 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:58,640 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:59,691 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:28:00,742 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:28:11,798 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:28:14,850 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:28:24,906 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:28:27,958 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:28:33,011 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:28:38,064 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:28:41,116 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:28:44,167 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:28:48,219 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:28:51,271 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:28:53,323 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:29:08,380 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:29:12,433 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11
 03/05 16:29:15,484 WARNING [140381029353216] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11

camera 2 is fine

SUMMARY
========

PARAMETERS
 * /cam_2/realsense2_camera/accel_fps: -1
 * /cam_2/realsense2_camera/accel_frame_id: cam_2_accel_frame
 * /cam_2/realsense2_camera/accel_optical_frame_id: cam_2_accel_optic...
 * /cam_2/realsense2_camera/align_depth: False
 * /cam_2/realsense2_camera/aligned_depth_to_color_frame_id: cam_2_aligned_dep...
 * /cam_2/realsense2_camera/aligned_depth_to_fisheye1_frame_id: cam_2_aligned_dep...
 * /cam_2/realsense2_camera/aligned_depth_to_fisheye2_frame_id: cam_2_aligned_dep...
 * /cam_2/realsense2_camera/aligned_depth_to_fisheye_frame_id: cam_2_aligned_dep...
 * /cam_2/realsense2_camera/aligned_depth_to_infra1_frame_id: cam_2_aligned_dep...
 * /cam_2/realsense2_camera/aligned_depth_to_infra2_frame_id: cam_2_aligned_dep...
 * /cam_2/realsense2_camera/allow_no_texture_points: False
 * /cam_2/realsense2_camera/base_frame_id: cam_2_link
 * /cam_2/realsense2_camera/calib_odom_file: 
 * /cam_2/realsense2_camera/clip_distance: -2.0
 * /cam_2/realsense2_camera/color_fps: -1
 * /cam_2/realsense2_camera/color_frame_id: cam_2_color_frame
 * /cam_2/realsense2_camera/color_height: -1
 * /cam_2/realsense2_camera/color_optical_frame_id: cam_2_color_optic...
 * /cam_2/realsense2_camera/color_width: -1
 * /cam_2/realsense2_camera/confidence_fps: -1
 * /cam_2/realsense2_camera/confidence_height: -1
 * /cam_2/realsense2_camera/confidence_width: -1
 * /cam_2/realsense2_camera/depth_fps: -1
 * /cam_2/realsense2_camera/depth_frame_id: cam_2_depth_frame
 * /cam_2/realsense2_camera/depth_height: -1
 * /cam_2/realsense2_camera/depth_optical_frame_id: cam_2_depth_optic...
 * /cam_2/realsense2_camera/depth_width: -1
 * /cam_2/realsense2_camera/device_type: 
 * /cam_2/realsense2_camera/enable_accel: False
 * /cam_2/realsense2_camera/enable_color: True
 * /cam_2/realsense2_camera/enable_confidence: True
 * /cam_2/realsense2_camera/enable_depth: True
 * /cam_2/realsense2_camera/enable_fisheye1: False
 * /cam_2/realsense2_camera/enable_fisheye2: False
 * /cam_2/realsense2_camera/enable_fisheye: False
 * /cam_2/realsense2_camera/enable_gyro: False
 * /cam_2/realsense2_camera/enable_infra1: False
 * /cam_2/realsense2_camera/enable_infra2: False
 * /cam_2/realsense2_camera/enable_infra: False
 * /cam_2/realsense2_camera/enable_pointcloud: False
 * /cam_2/realsense2_camera/enable_pose: False
 * /cam_2/realsense2_camera/enable_sync: False
 * /cam_2/realsense2_camera/filters: spatial,temporal,...
 * /cam_2/realsense2_camera/fisheye1_frame_id: cam_2_fisheye1_frame
 * /cam_2/realsense2_camera/fisheye1_optical_frame_id: cam_2_fisheye1_op...
 * /cam_2/realsense2_camera/fisheye2_frame_id: cam_2_fisheye2_frame
 * /cam_2/realsense2_camera/fisheye2_optical_frame_id: cam_2_fisheye2_op...
 * /cam_2/realsense2_camera/fisheye_fps: -1
 * /cam_2/realsense2_camera/fisheye_frame_id: cam_2_fisheye_frame
 * /cam_2/realsense2_camera/fisheye_height: -1
 * /cam_2/realsense2_camera/fisheye_optical_frame_id: cam_2_fisheye_opt...
 * /cam_2/realsense2_camera/fisheye_width: -1
 * /cam_2/realsense2_camera/gyro_fps: -1
 * /cam_2/realsense2_camera/gyro_frame_id: cam_2_gyro_frame
 * /cam_2/realsense2_camera/gyro_optical_frame_id: cam_2_gyro_optica...
 * /cam_2/realsense2_camera/imu_optical_frame_id: cam_2_imu_optical...
 * /cam_2/realsense2_camera/infra1_frame_id: cam_2_infra1_frame
 * /cam_2/realsense2_camera/infra1_optical_frame_id: cam_2_infra1_opti...
 * /cam_2/realsense2_camera/infra2_frame_id: cam_2_infra2_frame
 * /cam_2/realsense2_camera/infra2_optical_frame_id: cam_2_infra2_opti...
 * /cam_2/realsense2_camera/infra_fps: -1
 * /cam_2/realsense2_camera/infra_height: -1
 * /cam_2/realsense2_camera/infra_rgb: False
 * /cam_2/realsense2_camera/infra_width: -1
 * /cam_2/realsense2_camera/initial_reset: False
 * /cam_2/realsense2_camera/json_file_path: 
 * /cam_2/realsense2_camera/linear_accel_cov: 0.01
 * /cam_2/realsense2_camera/odom_frame_id: cam_2_odom_frame
 * /cam_2/realsense2_camera/ordered_pc: False
 * /cam_2/realsense2_camera/pointcloud_texture_index: 0
 * /cam_2/realsense2_camera/pointcloud_texture_stream: RS2_STREAM_COLOR
 * /cam_2/realsense2_camera/pose_frame_id: cam_2_pose_frame
 * /cam_2/realsense2_camera/pose_optical_frame_id: cam_2_pose_optica...
 * /cam_2/realsense2_camera/publish_odom_tf: True
 * /cam_2/realsense2_camera/publish_tf: True
 * /cam_2/realsense2_camera/rosbag_filename: 
 * /cam_2/realsense2_camera/serial_no: 053122250128
 * /cam_2/realsense2_camera/tf_publish_rate: 0.0
 * /cam_2/realsense2_camera/topic_odom_in: odom_in
 * /cam_2/realsense2_camera/unite_imu_method: 
 * /cam_2/realsense2_camera/usb_port_id: 
 * /rosdistro: noetic
 * /rosversion: 1.15.9

NODES
  /cam_2/
    realsense2_camera (nodelet/nodelet)
    realsense2_camera_manager (nodelet/nodelet)

ROS_MASTER_URI=http://localhost:11311

process[cam_2/realsense2_camera_manager-1]: started with pid [23655]
process[cam_2/realsense2_camera-2]: started with pid [23656]
[ INFO] [1620023266.560183621]: Initializing nodelet with 8 worker threads.
[ INFO] [1620023266.625776454]: RealSense ROS v2.2.22
[ INFO] [1620023266.625797485]: Built with LibRealSense v2.42.0
[ INFO] [1620023266.625804678]: Running with LibRealSense v2.42.0
[ INFO] [1620023266.646971673]:  
[ WARN] [1620023266.652993967]: Device 1/3 failed with exception: failed to set power state
 03/05 16:27:46,652 ERROR [140139590305536] (handle-libusb.h:95) failed to claim usb interface: 0, error: RS2_USB_STATUS_BUSY
 03/05 16:27:46,652 ERROR [140139615483648] (sensor.cpp:523) acquire_power failed: failed to set power state
 03/05 16:27:46,652 WARNING [140139615483648] (rs.cpp:306) null pointer passed for argument "device"
 03/05 16:27:46,729 WARNING [140139598698240] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
[ INFO] [1620023266.879249627]: Device with serial number * was found.

[ INFO] [1620023266.879277967]: Device with physical ID 2-2.4-7 was found.
[ INFO] [1620023266.879291941]: Device with name Intel RealSense D455 was found.
[ INFO] [1620023266.879571566]: Device with port number 2-2.4 was found.
[ INFO] [1620023266.879589393]: Device USB type: 3.2
[ INFO] [1620023266.880768568]: getParameters...
[ INFO] [1620023266.906465297]: setupDevice...
[ INFO] [1620023266.906497494]: JSON file is not provided
[ INFO] [1620023266.906507559]: ROS Node Namespace: cam_2
[ INFO] [1620023266.906521207]: Device Name: Intel RealSense D455
[ INFO] [1620023266.906530823]: Device Serial No: *
[ INFO] [1620023266.906538913]: Device physical port: 2-2.4-7
[ INFO] [1620023266.906550059]: Device FW version: 05.12.13.50
[ INFO] [1620023266.906559594]: Device Product ID: 0x0B5C
[ INFO] [1620023266.906569666]: Enable PointCloud: On
[ INFO] [1620023266.906579291]: Align Depth: Off
[ INFO] [1620023266.906589052]: Sync Mode: On
[ INFO] [1620023266.906625332]: Device Sensors: 
[ INFO] [1620023266.929115065]: Stereo Module was found.
[ INFO] [1620023266.939533201]: RGB Camera was found.
[ INFO] [1620023266.939829890]: Motion Module was found.
[ INFO] [1620023266.939856109]: (Confidence, 0) sensor isn't supported by current device! -- Skipping...
[ INFO] [1620023266.939875602]: Add Filter: spatial
[ INFO] [1620023266.940198596]: Add Filter: temporal
[ INFO] [1620023266.940502859]: Add Filter: pointcloud
[ INFO] [1620023266.940789485]: num_filters: 3
[ INFO] [1620023266.940802794]: Setting Dynamic reconfig parameters.
[ INFO] [1620023267.368512013]: Done Setting Dynamic reconfig parameters.
[ INFO] [1620023267.368907470]: depth stream is enabled - width: 848, height: 480, fps: 30, Format: Z16
[ INFO] [1620023267.369645111]: color stream is enabled - width: 1280, height: 720, fps: 30, Format: RGB8
[ INFO] [1620023267.369668962]: setupPublishers...
[ INFO] [1620023267.370824259]: Expected frequency for depth = 30.00000
[ INFO] [1620023267.386364551]: Expected frequency for color = 30.00000
[ INFO] [1620023267.396254492]: setupStreams...
[ INFO] [1620023267.417498629]: insert Depth to Stereo Module
[ INFO] [1620023267.417546521]: insert Color to RGB Camera
[ INFO] [1620023267.466236248]: SELECTED BASE:Depth, 0
[ INFO] [1620023267.471884995]: RealSense Node Is Up!
 03/05 16:27:47,550 WARNING [140139598698240] (messenger-libusb.cpp:42) control_transfer returned error, index: 300, error: No data available, number: 3d
[ WARN] [1620023267.680723885]: 
 03/05 16:27:47,681 WARNING [140139598698240] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:47,731 WARNING [140139598698240] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:47,782 WARNING [140139598698240] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:47,832 WARNING [140139598698240] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:47,883 WARNING [140139598698240] (messenger-libusb.cpp:42) control_transfer returned error, index: 300, error: No data available, number: 3d
 03/05 16:27:47,933 WARNING [140139598698240] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:47,985 WARNING [140139598698240] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:48,035 WARNING [140139598698240] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:48,085 WARNING [140139598698240] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:53,244 WARNING [140139598698240] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:55,295 WARNING [140139598698240] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:55,345 WARNING [140139598698240] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:56,396 WARNING [140139598698240] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:56,446 WARNING [140139598698240] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
 03/05 16:27:58,498 WARNING [140139598698240] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
MartyG-RealSense commented 3 years ago

Hi @victorll998 I am not involved in cases related to T265. Could you repost your question as a new case with T265 included in the message title using the green New Issue button on the front page of the forum please so that the appropriate RealSense team member can handle the case? Thanks!

https://github.com/IntelRealSense/realsense-ros/issues