Resource temporarily unavailable, number: 11 #9985
Comments
|
Hi @kongxin22 There is no need to apologize :) control_transfer returned errors are usually not caused by a camera hardware failure but instead by a communication problem such as camera data temporararily not being received by the computer's USB port. If the messages are only occurring occasionally (for example, once or twice a minute) and are not disrupting the correct operation of the camera then they can be safely ignored. An Asic Temperature is not valid! warning is also usually not a cause for concern if it occurs infrequently. |
|
@MartyG-RealSense But the statements on my terminal are only "Resource temporarily unavailable, number: 11",which appear one by one.And there are other problems on another computer: 22/11 22:51:26,811 WARNING [140535454770944] (backend-v4l2.cpp:1358) Pixel format 36315752-1a66-a242-9065-d01814a likely requires patch for fourcc code RW16! I have tried to reinstall the SDK,but there was no luck.I am worried because the troubles occurred so suddenly. |
|
Your English is very good, so don't worry! The warning message that you experienced is of the 'control_transfer returned' type. 'Resource temporarily unavailable' describes the kind of control_transfer returned warning that it is. WARNING [140271777982208] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11 The 'IMU Calibration is not available' warning suggests that the D455's internal IMU hardware component (called the Motion Module in the RealSense Viewer) has not been calibrated using Intel's IMU calibration tool since the camera was purchased. This is not a serious problem though. https://dev.intelrealsense.com/docs/imu-calibration-tool-for-intel-realsense-depth-camera The warning 'Pixel format 36315752-1a66-a242-9065-d01814a likely requires patch for fourcc code RW16!' suggests that if you built the SDK using Linux and you built it from source code then the Linux kernel was not patched during the installation process. I note though that the SDK was working normally for you at first and then suddenly having problems. This suggests that the SDK was installed correctly. What are your problems on the other computer, please? |
|
@MartyG-RealSense |
|
If the camera streams appear to be operating normally then you could ignore the control_transfer returned messages. If you wish to try to reduce them though then you could test whether the number of messages reduce if you use a lower resolution. For example, setting 640x480 and 30 FPS for the depth stream in the RealSense Viewer tool.
|
|
@MartyG-RealSense |
|
Yes, if it is not causing you problems then you can ignore the warnings without worry. They may be related to the USB hardware on that particular computer. |
|
Hi @kongxin22 Do you require further assistance with this case, please? Thanks! |
|
Hi, I'm having a similar problem on a Lenovo T480s and a VR capable NUC (although I am running L515). Tried both v2.48 and v2.5 also and still getting the same problem. The messages appear constantly, both on realsense-viewer and ROS. |
|
Hi @wilsonz91 In ROS, do the messages still occur if you add initial_reset:=true to your roslaunch instruction to reset the camera at launch. For example: roslaunch realsense2_camera rs_camera.launch initial_reset:=true |
|
Hi @MartyG-RealSense, sadly, yes it does |
|
@wilsonz91 Are you able to stream the camera images in the Viewer and in RViz in ROS without apparent negative impact on performance? If you can then I would repeat the advice given to @kongxin22 above to simply ignore the messages. |
|
I'll have to check on that. Could I ask regarding the ROS timestamp seen on the image/depth messages: are they from the camera time or the time they are published? or would image 4 shows up timestamp 0003? |
|
In the RealSense ROS wrapper, Global Time is enabled by default for 400 Series cameras (including the D455). Doronhi the RealSense ROS wrapper developer provides advice about Global Time in regard to timestamps and how it aligns device time with system time at IntelRealSense/realsense-ros#796 Global Time is discussed further in detail at #4505 In regard to your specific question about timestamp numbering, I don't know unfortunately. |
|
Hi @MartyG-RealSense ,I have taken your advice to ignore the "Resource temporarily unavailable, number: 11" and "No data available, number: 61".But I find that when I run a script,which need to collect data from the camera,similar problem occurred:No device connected. |
|
Hi @kongxin22 If the problem can be solved sometimes by USB unplug-replug then it suggests that the camera hardware is okay and the problem may be elsewhere, such as in the USB system (either the USB port of the computer, the port's USB controller or the USB cable). Are you using the official 1 meter USB cable supplied with the camera or a longer USB cable of your own choice, please? |
|
Hi @kongxin22 and @wilsonz91 Do you require further assistance with this case, please? Thanks! |
|
Hi @MartyG-RealSense, thanks for the information. I'm ignoring the warnings for now. |
|
Thanks very much @wilsonz91 for the update of your particular situation! |
|
Case closed due to no further comments received. |
Issue Description
I'm so sorry that a new problem occurs.At first everything went well,but suddenly something happened like these:
21/11 16:43:00,257 WARNING [140271777982208] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11
21/11 16:43:01,343 ERROR [140271650064128] (ds5-options.cpp:88) Asic Temperature value is not valid!
21/11 16:29:51,418 WARNING [140271777982208] (messenger-libusb.cpp:42) control_transfer returned error, index: 300, error: No data available, number: 3d
Is my camera broken?I'm so worried!
PS:I have not installed the librealsense-ros.
The text was updated successfully, but these errors were encountered: