-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fatal:you need to specify a tag name #1220
Comments
In case Librealsense is having a conflict with your kernel, I would recommend instead installing librealsense through the RSUSB "backend" method, which requires an internet connection. It is not dependent on Linux versions, kernel versions or patches, so you do not need to apply the patch script.
If you do not have it, you can visit the link below, go to the 'Assets' list at the bottom of its page and download the source-code zip file. Then un-zip it. https://github.com/IntelRealSense/librealsense/releases/tag/v2.33.1
If you do not have a Build folder, use the command below whilst in the Librealsense root folder to create one and navigate to it: mkdir build && cd build
cmake ../ -DFORCE_RSUSB_BACKEND=true -DCMAKE_BUILD_TYPE=release -DBUILD_EXAMPLES=true -DBUILD_GRAPHICAL_EXAMPLES=true |
@MartyG-RealSense how can I do.And thanks for adviance |
The USB REC overflow error suggests that more data is being generated than the USB can handle. You could try adding enable_infra2:=false to your roslaunch statement to disable infrared2 and free up USB bandwidth. For example: roslaunch realsense2_camera rs_camera.launch enable_infra2:=false Doronhi the RealSense ROS wrapper developer has said "It will have no effect on the depth quality. It only disable the infra2 images' transmission via the USB port. They are still taken and the depth is calculated using them inside the device". |
How often do the control_transfer returned messages appear? Once a minute, or more often? |
@MartyG-RealSense |
@Jenny0420 , Are you familiar with RViz? To see the picture you need to do the following on RViz: |
@doronhi |
@Jenny0420 Do you still require assistance with this case please or can it now be closed? Thanks! |
Thanks so much for the update! |
@doronhi @MartyG-RealSense |
My understanding is that if libralsense is built from packages on Jetson instead of source code - as referenced by Doronhi in #1110 (comment) - then the build will also be based on the RSUSB backend. So building from the dedicated Jetson packages instead of source code may not be a solution if RSUSB gives you performance degradation. The Jetson installation instructions do though offer the option of a non-RSUSB build from source code with the V4L Native Backend, which has a dedicated patch script patch-realsense-ubuntu-L4T.sh instead of the 'patch-realsense-ubuntu-lts.sh' one used on x86 / x64 non-RSUSB source code builds. In regard to the Doronhi comment that you linked to at #2068 (comment) - Intel made updates to the RSUSB backend in librealsense 2.50.0 that are described in IntelRealSense/librealsense#9821 There was a recent report though from a RealSense user that said that they had RSUSB problems with 2.50.0 that disappeared if they used the previous SDK version 2.49.0. As there is not a matching ROS wrapper version for 2.49.0 though, then I would recommend using 2.48.0. |
raspberry 4 4G
ubuntu 18.04 LTS
kernel: 5.3.0-1026-raspi2
I need run my relasense d435 on ros melodic
I have download the librealsense v2.33.1
when I run " ./scripts/patch-realsense-ubuntu-lts.sh"
as this picture
Can anyone please give me some suggestion on how to solve the problem ?
Thank you in advance.
The text was updated successfully, but these errors were encountered: