D455f depth issue
We are using D455f. But we met depth issues like images attached. May you help us to clear this issue for our product? If you need any more information, please let us know. We will come back to you as soon as possible.
-
Hi Ryan Lee What distance is the camera from the observed surface, please? It is recommended that a D455f is placed at least 60 cm away. This is because RealSense cameras have a minimum depth sensing distance that varies depending on the model of camera, and if the camera is moved closer to a surface than the recommended minimum distance then the depth image starts to break up in a way similar to your kindly provided image.
If the camera is closer to the observed surface than 60 cm then the camera's minimum distance can be reduced with the Disparity Shift setting to enable the camera to move closer before the image starts breaking up, at the expense of a reduced observable maximum depth distance as the Disparity Shift value is increased.
-
Hi Ryan Lee Do you require further assistance with this case, please? Thanks!
-
Thanks very much for the RealSense Viewer image. Let's next test whether the camera's infrared dot pattern emitter could be causing the black dots. Please go to the Stereo Module > Controls section of the Viewer and click on the drop-down menu beside the 'Emitter Enabled' option, and set it to 'Off' to disable the emitter.
Do the black dots then disappear from the depth image?
-
There is too much depth detail lost when the emitter and its light output is disabled to tell whether the holes are resulting from the emitter's projected dot pattern. It does seem though that it is much better for image quality to have the emitter enabled even if it results in the small holes.
Does the image quality in the Viewer become satsfactory if you open the list of post-processing filters and enable the Hole-Filling filter?
-
Hi,
First of all thank you so much about your dedicated help.
Above is the image that appears when using the settings you sent. Is the data being received correctly?
However, we are using the exact same environment, the same PC, and the same cable, but since the depth data is coming in differently just because the camera is different, we suspect there is a problem with the camera.
Will this issue be resolved by doing this? The depth data comes in differently even when using a camera with the same specifications.
Could you help us some more about our question?
Best regards,
Ryan.
-
The image looks correct, with blue shading on the surfaces near to the camera and shifting from blue to yellow / orange to red (the furthest-away surfaces) as the distance of surfaces from the camera increases.
When you say 'the camera is different', does this mean that you have tested with more than one camera? If you have, what is the model of the other camera, please? Is it a D455f or another RealSense model?
-
Hi,
We have three. One D455f with issue so we are talking about. And one D455f normal. and one D435i. two D455f and D435i are same performance. only one of D455f had an issue we were talking about. We would like to be more clear about this issue. such as the reason and whether we can meet this kind of issue often or not.
1. D455f that I own (camera currently having issues)
2. D455f camera used in another project (normal)
3. D435i camera used in another project (normal)
Best regards,
Ryan.
-
Please try using the instructions at the link below to reset the affected camera in the RealSense Viewer to its factory-new calibration values.
https://github.com/realsenseai/librealsense/issues/11596#issuecomment-1490647753
Please sign in to leave a comment.
Comments
14 comments