Subscribe PointCloud2 topic gives error #1181
Comments
|
Hi @brsbilgin It looks like this case may be related to an issue with synthetic stream errors that does not have a clear solution at the time of writing this. I will quote some advice from that discussion that was provided by @doronhi the RealSense ROS wrapper developer: "The "Out of frame resources!" message and the "Exception...processing callback!" could be related to ... lack of system resources - the app can't keep up with the incoming flow of images. For that you can reduce frame rate and resolution. Building with CUDA support should really help in that case on NVidia machines". A RealSense user gave advice on testing whether reducing frame rate would help by adjusting the FPS in the launch file: |
|
Hi @MartyG-RealSense . I will check the #1161 . |
|
@brsbilgin Okay, thank you very much for the update. I look forward to hearing from you again after you have read #1161 |
|
I also get the following when launching with pointcloud on, on a Jetson Nano. I first get the control transfer error when launching the node (I know the devs are aware of this) and then when I visualize the pointcloud in rviz I start getting the callback error (which I imagine has to do with the framerate/resolution). This callback error, however, doesn't happen all the time, could it be affected by whatever there is in the scene? Also, if I kill the node using ctrl+c and then try and launch it again, I start getting uvc device warnings and Hardware Errors. (See second code snippet) Second time running the node: |
|
@jorgemia The link below has advice from @doronhi the RealSense ROs wrapper developer about the set of errors that you are receiving. Like you and the Nano, the user in that case similarly had a low-power single board computer (the Up Board - the original humble-spec model and not the later and more powerful Up Squared). |
Closed
|
@jorgemia Do you still require further assistance with the errors that you were experiencing, please? |
|
@MartyG-RealSense just waiting for the errors to be fixed. |
|
You could try disabling the infra2 channel to save some processing, by using enable_infra2:=false 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". If you are able to successfully generate a point cloud but are continuously generating errors, a "dirty" workaround may be to disable on-screen error logging in ROS. IntelRealSense/librealsense#6347 (comment) Other advice I could give has already been posted earlier in this discussion, unfortunately. |
|
Regarding the stream start failure on the second run, I encountered something similar and fixed it in #1202 . I didn't manage to check it on Jetson Nano yet. Will be happy to know if it fixed it for you. |
|
@doronhi yes that PR fixed the issue I used to encounter on a second run! Thanks! FYI though, I get the follow libusb warning when shutting down the node now: |
|
Case closed due to no further comments received. @jorgemia please create a new issue if you are still receiving a libusb warning and require support for that issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I start to subscribe /camera/depth/color/points topic it starts give error on bellow. When I stopped read topic it stops to give error.
25/04 22:18:16,033 ERROR [546022039936] (synthetic-stream.cpp:48) Exception was thrown during user processing callback!
25/04 22:18:16,100 WARNING [546022039936] (types.cpp:49) Out of frame resources!
25/04 22:18:16,100 ERROR [546022039936] (synthetic-stream.cpp:48) Exception was thrown during user processing callback!
25/04 22:18:16,133 WARNING [546022039936] (types.cpp:49) Out of frame resources!
25/04 22:18:16,133 ERROR [546022039936] (synthetic-stream.cpp:48) Exception was thrown during user processing callback!
25/04 22:18:16,399 WARNING [546022039936] (types.cpp:49) Out of frame resources!
25/04 22:18:16,400 ERROR [546022039936] (synthetic-stream.cpp:48) Exception was thrown during user processing callback!
25/04 22:18:16,433 WARNING [546022039936] (types.cpp:49) Out of frame resources!
25/04 22:18:16,433 ERROR [546022039936] (synthetic-stream.cpp:48) Exception was thrown during user processing callback!
25/04 22:18:16,500 WARNING [546022039936] (types.cpp:49) Out of frame resources
The text was updated successfully, but these errors were encountered: