error control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11 while trying slam #1663
Comments
|
@demoncoderad Did you get chance to try if any issue to run RealSenseViewer? And also noticed that the USB type is USB2. If it's not intended to be USB2, please check USB cable or USB port to make it USB3 connection. |
|
Hi, it works good in realsense viewer. I have a USB 3 and USB 2 port so I plugged in the T265 (afaik) in USB 3 and D435 on Usb 2 |
|
@demoncoderad Is the issue existing if you only connect T265 or D435 only? Thanks for your feedback! |
|
Hi, You did not specify what machine you have but still, since the viewer works well for you, I would recommend removing the ros-melodic-realsense2-camera installation and build realsense2_camera from source. It will link with the librealsense2 version already installed on your machine (v4l backend), the same one realsense-viewer uses. |
|
Thanks, i'll look into it @doronhi |
|
@demoncoderad With the suggestions from doronhi, any update from your side? Thanks! |
|
Hello, I report the same problem on Jetson Nano with L515. ErrorIn Jetson Nano, with L515 only, the same error happens continuously as below:
Symptoms
ConditionOnly realsense-ros application is executed on the Jetson Nano. EnvironmentJetson Nano ARM64 4GB RAM BuildI've built |
|
@demoncoderad Any update from your side? Looking forward to your reply. Thanks! @bigbellmercy As your issue happened on different camera and platforms, could you please create another issue to track it separately so the clue will be more clear? Thanks! |
Yes, a new issue was created as #1758. Thanks. |
|
@bigbellmercy Thanks for your quick action! We'll look into that. |
|
@demoncoderad Sorry that we didn't get response from you for weeks, and this issue will be closed at this point. Please create another ticket if you still have questions or issues. Thanks! |
|
was this solved, I am having the same issue, I am getting the same message:
at first I get some pointcloud from the D435 but then it stops, I am using a Jetson Nano, I could make it work about a year ago, along with the T265 but now I am stuck with this. |
|
This bug still persists |
|
Same issue here. Running Realsense on ROS Noetic with Ubuntu20.04 and Turtlebot |
|
@YXGuan @ingramator @sasilva1998, I encountered the same problem and after a bunch of hours spent online, I read realsense engineers are still working on that issue, and in some cases, that error message can be ignored. Also, what I did was reset the camera upon launch. |
|
I am running ROS2 Galactic on Ubuntu 20.04 and I was experiencing this same error message. The issue was that the realsense2 camera node was trying to publish the raw point clouds over the WiFi network to a desktop computer that was running rviz2 (in ROS2, two computers running ROS2 nodes on the same local network will automatically detect publishers/subscribers because of DDS. You can change this behavior by changing the ROS_DOMAIN_ID). I imagine if you are running ROS1, you might experience the same error message if you are trying to publish the raw point cloud over a WiFi network (but you would have had to manually change the ROS_MASTER_URI in ROS1). This network issue was strange to track down for me, so I imagine that might be why this issue still exists. It worked fine when I used the realsense-viewer program, but failed when running the ROS2 node. I second guessed the USB 3 cable and the camera hardware, but in the end the only difference I could really point to was that ROS2 was performing network operations and the realsense-viewer wasn't. tldr: make sure you aren't publishing the camera's raw point clouds over a WiFi network. |
Hey!
So I am trying to do a slam thingy. I am doing this for a showcase currently (i'll use the D435 and T265 for more after my exams) where I just have to show that it can walk around and it gives in text the directions for going from x point in map to a point y. That I somehow am able to do with help of https://neilyoung.serveblog.net/ But I wish to have Object avoidance, and when I saw this I thought this might be quick easy way to get it done. But im facing some problems, after installing this and running
roslaunch realsense2_camera rs_camera.launchi get a warning03/02 20:30:26,300 WARNING [139819288090368] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11and it doesn't go further. I would appreciate some help. I'm using Ubuntu 18.04 and installed with the same steps just changing ros-kinetic to ros-melodic.here's the full output
`
... logging to /home/adityarc/.ros/log/833fd1a6-6630-11eb-b16a-dc85dea045af/roslaunch-pop-os-6296.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://pop-os:34391/
SUMMARY
PARAMETERS
NODES
/camera/
realsense2_camera (nodelet/nodelet)
realsense2_camera_manager (nodelet/nodelet)
auto-starting new master
process[master]: started with pid [6310]
ROS_MASTER_URI=http://localhost:11311
setting /run_id to 833fd1a6-6630-11eb-b16a-dc85dea045af
process[rosout-1]: started with pid [6321]
started core service [/rosout]
process[camera/realsense2_camera_manager-2]: started with pid [6324]
process[camera/realsense2_camera-3]: started with pid [6325]
[ INFO] [1612364417.421709404]: Initializing nodelet with 2 worker threads.
[ INFO] [1612364423.415631857]: RealSense ROS v2.2.21
[ INFO] [1612364423.415943751]: Built with LibRealSense v2.41.0
[ INFO] [1612364423.416156711]: Running with LibRealSense v2.41.0
[ INFO] [1612364423.445426621]:
[ INFO] [1612364423.626210386]: Device with serial number 927522072103 was found.
[ INFO] [1612364423.626391562]: Device with physical ID 3-1-4 was found.
[ INFO] [1612364423.626481639]: Device with name Intel RealSense D435 was found.
[ INFO] [1612364423.627252090]: Device with port number 3-1 was found.
[ INFO] [1612364423.627343695]: Device USB type: 2.1
[ WARN] [1612364423.627440190]: Device 927522072103 is connected using a 2.1 port. Reduced performance is expected.
[ INFO] [1612364423.649062062]: getParameters...
[ INFO] [1612364423.742118620]: setupDevice...
[ INFO] [1612364423.742172830]: JSON file is not provided
[ INFO] [1612364423.742196098]: ROS Node Namespace: camera
[ INFO] [1612364423.742333286]: Device Name: Intel RealSense D435
[ INFO] [1612364423.742365289]: Device Serial No: 927522072103
[ INFO] [1612364423.742384977]: Device physical port: 3-1-4
[ INFO] [1612364423.742402619]: Device FW version: 05.12.10.00
[ INFO] [1612364423.742420880]: Device Product ID: 0x0B07
[ INFO] [1612364423.742437929]: Enable PointCloud: Off
[ INFO] [1612364423.742454295]: Align Depth: Off
[ INFO] [1612364423.742469952]: Sync Mode: Off
[ INFO] [1612364423.742722711]: Device Sensors:
[ INFO] [1612364423.778927733]: Stereo Module was found.
[ INFO] [1612364423.793653146]: RGB Camera was found.
[ INFO] [1612364423.793878601]: (Confidence, 0) sensor isn't supported by current device! -- Skipping...
[ INFO] [1612364423.794022876]: num_filters: 0
[ INFO] [1612364423.794132165]: Setting Dynamic reconfig parameters.
[ INFO] [1612364424.266699282]: Done Setting Dynamic reconfig parameters.
[ INFO] [1612364424.297250159]: depth stream is enabled - width: 640, height: 480, fps: 30, Format: Z16
[ INFO] [1612364424.299079091]: color stream is enabled - width: 640, height: 480, fps: 30, Format: RGB8
[ INFO] [1612364424.299484410]: setupPublishers...
[ INFO] [1612364424.337762894]: Expected frequency for depth = 30.00000
[ INFO] [1612364424.494324012]: Expected frequency for color = 30.00000
[ INFO] [1612364424.533627699]: setupStreams...
[ INFO] [1612364424.556888751]: insert Depth to Stereo Module
[ INFO] [1612364424.556989185]: insert Color to RGB Camera
03/02 20:30:24,610 WARNING [139819288090368] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11
[ INFO] [1612364424.660969509]: SELECTED BASE:Depth, 0
[ INFO] [1612364424.681647468]: RealSense Node Is Up!
03/02 20:30:24,746 WARNING [139819288090368] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11
03/02 20:30:24,797 WARNING [139819288090368] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11
03/02 20:30:24,949 WARNING [139819288090368] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11
03/02 20:30:25,026 WARNING [139819288090368] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11
03/02 20:30:25,077 WARNING [139819288090368] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11
03/02 20:30:25,232 WARNING [139819288090368] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11
03/02 20:30:25,282 WARNING [139819288090368] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11
03/02 20:30:25,435 WARNING [139819288090368] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11
03/02 20:30:25,485 WARNING [139819288090368] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11
03/02 20:30:26,250 WARNING [139819288090368] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11
03/02 20:30:26,300 WARNING [139819288090368] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11
^C[camera/realsense2_camera_manager-2] killing on exit
[camera/realsense2_camera-3] killing on exit
[rosout-1] killing on exit
[master] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
done
`
The text was updated successfully, but these errors were encountered: