Getting mutiple issues in Intel Realsense Camera. #13100
Comments
|
How to fix these error when realsense camera is activated? Kernel version=5.15.0-113-generic |
|
Hi @ShreyasKuntnal You do not need to set global_time_enabled to true as it is already enabled by default on 400 Series cameras such as D435i. The If you do not need the Infra2 stream then you can disable it to reduce the processing burden, as it is not required for streaming Infra1. Likewise, if you do not need depth-color aligned images then set align_depth to False to further reduce processing, as alignment is calculated on the computer and not the camera hardware. Please also check whether the depth and color streams are being published in RViz, as sometimes they can be displayed normally in RViz even if control_transfer warnings are generating continuously in the log. |
|
Have i installed right version of dkms for particular kernel and librealsense version?
I get these errors as soon as I start realsense-viewer. What are these, Is there need to fix these or ignoring can be ok? |
|
The firmware version 5.13.0.50 is correct for librealsense 2.50.0. As you have 2.50.0, it looks as though you have the correct DKMS package version. Are you using the official 1 meter USB cable supplied with the camera or a cable of your own choice? Is the RGB stream of the Viewer able to be enabled despite the RGB-related errors in the Viewer log? Is there improvement if you reset your camera's calibration to its factory-new default settings in the Viewer using the instructions at #10182 (comment) |
|
I use the default cable that's provided by intel. With respect to camera calibration, this is how it looks. |
|
To unlock the Write Table button on the Camera Calibration window, you need to enable the Stereo Module (the depth stream) before opening the window. You can then click on Write Table to reset the camera's calibration to its defaults. In general, if streams are behaving normally when enabled despite warning / error messages in the log then the messages can be ignored. |
|
If I do camera calibration reset, is there a need to do imu calibration again. |
|
There is not information available on whether the reset affects IMU calibration. However, if data stored in a part of the camera called the calibration table has become corrupted then it can prevent the camera from working correctly. Clicking the Write Table button overwrites the old calibration table with a new one, so it can enable the camera to work correctly if a corrupted calibration table was the cause of the problems. |
|
Did Camera calibration and restarted the realsense-viewer still these errors persist.
If we can fix the same the lets work on it or else as u said we can ignore lets ignore |
|
Yes, I recommend ignoring the errors if performance of the streams is not being negatively affected. |
|
Oh ok so even this error |
|
You are very welcome. The VIDIOC error suggests a conflict between librealsense and the kernel, but if the streams are performing normally then it is likely just a momentary hiccup that can be ignored. Thanks very much for the update! |
I tried mutiple issue threads but fed up with these mutiple issues.
When I do reaslsense launch, i am getting these issues:
roslaunch realsense2_camera rs_camera_edited.launch global_time_enabled:=true initial_reset:=trueCan you please help me with resolving these issues?
The text was updated successfully, but these errors were encountered: