(messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61 #1510
Comments
|
Hi @kristfrizh If you are receiving the control_transfer returned warning only several times during launch and then they stop, or they occur one or two times a minute after launch, then this warning can be safely ignored. You can check in RViz to see whether the topics are being published correctly despite the warnings. If this warning is generating continuously though then it can indicate a serious communication problem with the device. It is also worth bearing in mind that whilst RealSense 400 Series cameras are not interfered with by other cameras that are non-RealSense, the 400 Series can interfere with non-RealSense cameras in return. This issue seems to be based on how close the cameras are to each other, as a lidar camera and 400 Series camera have been used successfully on minature robotic boats called roboats, with the 400 Series camera on the base of the boat and a Velodyne lidar mounted on an elevated position at the top of the boat. |
|
Hii MartyG
thank you for your reply
eventhough it just several times but it affect to my topic.
sometimes, the topic are not created and sometime it can be created.
Is it because the data rate too much to handle?
is there any way to fix it?
maybe provide a new usb hub?
or maybe can i use LAN to usb to provide a new hub?
(sory i am not quite expert with computer architecture, i am just guessing
what work and dont work)
…On Thu, Nov 19, 2020 at 7:07 PM MartyG-RealSense ***@***.***> wrote:
Hi @kristfrizh <https://github.com/kristfrizh> If you are receiving the *control_transfer
returned* warning only several times during launch and then they stop, or
they occur one or two times a minute after launch, then this warning can be
safely ignored. You can check in *RViz* to see whether the topics are
being published correctly despite the warnings.
If this warning is generating continuously though then it can indicate a
serious communication problem with the device.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1510 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQKBDOOFIYLYSWL5GG4HV6TSQUC7NANCNFSM4T3HPU5Q>
.
|
|
A good starting point in an investigation is to try adding a instruction to the end of your roslaunch statement that performs a reset of the 400 Series camera at launch. The term to add is: initial_reset:=true |
|
Hi @kristfrizh Do you require further assistance with this case, please? Thanks! |
|
Hii Marty
sory for long updated
the behaviour still occurring.
I still not understand why the error happens
can you explain or give link?
what i thought the error happens because the data rate is way too high in
those bus,
do you have others suggestions?
should i buy a ethernet to USB module to create a new hub? (idk if it will
works or no)
thank you
really appreciate your response and help
Regards
…On Thu, Nov 26, 2020 at 3:05 PM MartyG-RealSense ***@***.***> wrote:
Hi @kristfrizh <https://github.com/kristfrizh> Do you require further
assistance with this case, please? Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1510 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQKBDOKA3MTZYACYR4DWYHLSRYD3ZANCNFSM4T3HPU5Q>
.
|
|
Hi @kristfrizh Can you confirm if you have tried a hardware reset and still have the problem, please? |
|
Hii marty |
|
Hi @kristfrizh I was not referring to resetting by physically unplugging the camera from the USB port, but instead adding a command to the roslaunch instruction that automatically resets the camera upon launch. |
|
Hi @MartyG-RealSense I have the same issue. I added the command initial_reset:=true to the end of my roslaunch statement as you suggested but nothing changed. Do you have any other suggestions ? |
|
Hi @koikonomou Are you able to edit the FPS values inside the launch file to use 15 FPS instead of 30 to see if the reduction in FPS makes a difference to the number of control_transfer returned errors please? |
|
hii marty, sory for the long update. thank you for your hospitality |
|
Thanks very much for the update @kristfrizh |
|
Adding a note to keep this case open for a further time period. |
1 similar comment
|
Adding a note to keep this case open for a further time period. |
Hi i have the same problem, how i can reduce the FBS? |
|
Hi @Haitham96 You can define a different FPS by editing the arg values in a roslaunch file. |
i tried to do reduce the fps to 15/6 , but i got the same error: ... logging to /home/haitham/.ros/log/17f6f94a-3fea-11eb-a4ad-40b0760db710/roslaunch-cggc-corsair270r-22894.log started roslaunch server http://cggc-corsair270r:40355/ SUMMARYPARAMETERS
NODES ROS_MASTER_URI=http://localhost:11311 process[camera/realsense2_camera_manager-1]: started with pid [22909] [ INFO] [1608198907.413640157]: Device with physical ID 2-2-22 was found. [ INFO] [1608198913.618063978]: Device with physical ID 2-2-23 was found. How i can fix it? |
|
If control_transfer returned is generating continuously even after launch then it can indicate that there is a serious communication problem with the device. I see that you have tried initial_reset already. Does the launch improve if you add enable_sync:=true to your roslaunch instruction? |
No, i have the same errors: ... logging to /home/haitham/.ros/log/17f6f94a-3fea-11eb-a4ad-40b0760db710/roslaunch-cggc-corsair270r-25900.log started roslaunch server http://cggc-corsair270r:36635/ SUMMARYPARAMETERS
NODES ROS_MASTER_URI=http://localhost:11311 process[camera/realsense2_camera_manager-1]: started with pid [25915] [ INFO] [1608200159.231594358]: Device with physical ID 2-2-30 was found. [ INFO] [1608200165.453622253]: Device with physical ID 2-2-31 was found. |
|
Thank you very much for the information. Are the topics published correctly in RViz despite the control_transfer returned warnings? |
What you are mean by topics published correctly in RViz ? |
|
ROS has an interface called RViz that allows camera data to be displayed visually, a bit like the RealSense Viewer in librealsense. If you are not familiar with using RViz in ROS, another way to check if the data is being published is to use a rostopic echo command: rostopic echo /camera/depth/image_rect_raw/header |
i tried to run this command rostopic echo /camera/depth/image_rect_raw/header and i got no output
|
|
Can you provide the roslaunch instruction that you are using please. |
haitham@cggc-corsair270r:~$ roslaunch realsense2_camera rs_camera.launch initial_reset:=true enable_sync:=true started roslaunch server http://cggc-corsair270r:34263/ SUMMARYPARAMETERS
NODES ROS_MASTER_URI=http://localhost:11311 process[camera/realsense2_camera_manager-1]: started with pid [30711] [ INFO] [1608203386.881809772]: Device with physical ID 2-2-38 was found. [ INFO] [1608203393.106740106]: Device with physical ID 2-2-39 was found. I also tried with fps 15: haitham@cggc-corsair270r:~$ roslaunch realsense2_camera rs_camera.launch initial_reset:=true depth_fps:=15 infra_fps:=15 color_fps:=15 enable_sync:=true started roslaunch server http://cggc-corsair270r:39717/ SUMMARYPARAMETERS
NODES ROS_MASTER_URI=http://localhost:11311 process[camera/realsense2_camera_manager-1]: started with pid [31003] [ INFO] [1608203438.858150388]: Device with physical ID 2-2-39 was found. [ INFO] [1608203445.046302510]: Device with physical ID 2-2-40 was found. with fps = 6 started roslaunch server http://cggc-corsair270r:33913/ SUMMARYPARAMETERS
NODES ROS_MASTER_URI=http://localhost:11311 process[camera/realsense2_camera_manager-1]: started with pid [31294] [ INFO] [1608203541.329238338]: Device with physical ID 2-2-40 was found. [ INFO] [1608203547.558414889]: Device with physical ID 2-2-41 was found. |
|
I meant the instruction that is used to launch, not the log. Like this: roslaunch realsense2_camera rs_camera.launch |
in my previous answer i wrote each instruction with its output. The instruction i used are:
with fps=15:
with fps=6
|
|
Okay, so you got no output when you checked if publishing was occurring using rostopic echo /camera/depth/image_rect_raw/header. And I assume that you get no output either with a simple roslaunch instruction with no additional customization flags: roslaunch realsense2_camera rs_camera.launch Do you receive camera data normally in the RealSense Viewer program in librealsense? |
|
i didn't install RealSense Viewer program, just installed realsense-ros according to these instruction. haitham@cggc-corsair270r:~$ roslaunch realsense2_camera rs_camera.launch started roslaunch server http://cggc-corsair270r:42157/ SUMMARYPARAMETERS
NODES ROS_MASTER_URI=http://localhost:11311 process[camera/realsense2_camera_manager-1]: started with pid [32505] [ INFO] [1608205302.065479302]: Device with physical ID 2-2-42 was found. |
|
|
|
Could you try using the Add button at the bottom of the side panel to add a topic to view please? |
there is no depth_registered feature |
|
That topic refers to a different point cloud example to this one. Try adding camera/color/image_raw |
yes, it's works thank you |
|
Hi @kristfrizh Do you require further assistance with this case, please? Thanks! |
|
Case closed due to no further comments received. |
|
@MartyG-RealSense I am working on the L515 in Ros. I am able to launch the node and am able to visualize the depth image using RQT. I am not able to get any messages when I enable the poincloud filters despite the |
|
Hi @senoa95 I am not involved in cases related to the L515 camera model. Could you post your question as a new case please and include 'L515' in the message title. You can do this by visiting the front page of this forum at the link below and clicking the green New Issue button. Thanks! |
|
Hey @MartyG-RealSense, I have the same issue with D435. Camera actually works fine, but spams the output with those warning messages: It didn't happen with the same HW ca. 6 months ago, so I believe it's the realsense library update that causes the issue. |
|
Hi @alex-makarov If the control_transfer returned errors only occur at launch, or at a rate of one or two per minute after launch, then they can be safely ignored. You could also try adding an instruction to the end of your roslaunch instruction to reset the camera at launch: Initial_reset:=true |
|
@MartyG-RealSense , thanks for responding so quickly. No, it happens continuously at high rate (you can see it in my example). It doesn't stop. I've added the "initial_reset" parameter but it doesn't help. (it actually does help with another issue that camera cannot be initialized on start quite often, but not with this one :) ) |
|
Okay, next please try reducing FPS from 30 to 15 with these roslaunch instructions: depth_fps:=15 color_fps:=15 |
|
@MartyG-RealSense that seems to help, thanks. I only have a bunch of warnings at startup now. Is it a resource utilization issue? I'm using D435 on NVIDIA Jetson Nano. |
|
The control_transfer returned error, when it continuously generates, can indicate a serious communication problem with the device. It may be that the USB controller cannot keep up with the rate that camera data is arriving when 30 FPS is used, especially if depth and color are published at the same time. You could also check your CPU usage in an Ubuntu tool such as htop to see whether the CPU processing load is approaching 100% utilization. |
|
Hi all, I had similar problems, what fixed it for me was using :
|
|
Thanks very much @jcnwholland for sharing the solution that worked for you! |
Hii
I try to combine camera with lidar in one robot
I use laserscan_merger and depthimage_to_laserscan.
I keep getting the same error like this
19/11 17:18:51,423 WARNING [139747262609152] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
I have see some error like this in issues but i have not find the solution.
this error also effect to my topic from laser realsense that sometimes appear and something not appear.
My assume that , this error occured because the data rate is faster than capacity data rate usb?
or anything else wrong?
any suggestion please?
My realsense is D435 and i use minicomputer linux 18.04
Thank you
regards
The text was updated successfully, but these errors were encountered: