You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Camera Model | {D455} |
| Firmware Version | (05.13.00.50) |
| Operating System & Version | {Linux (Ubuntu 20.04) |
| Kernel Version (Linux Only) | (5.15.0-122-generic) |
| Platform | PC |
| SDK Version | {2.50.0} |
| Language | {C/C#/labview/nodejs/opencv/pcl/python/unity } |
| Segment | {Robot } |
Issue Description
<Describe your issue / question / feature request / etc..>
I'm currently experiencing at least these two issues below with the SDk:
Unable to use the on_chip calibration function in the SDK for internal reference calibration. This problem is encountered when using it in the SDK
And after this problem, the SDK will not recognize the device unless the device is rebooted.
And after rebooting, the camera's imaging became very bad. The only way to get back to the original state is by rebooting several times
So I don't dare to try more
Then I tried to use depth_auto_calibration_example.py in example for internal calibration, but it still doesn't work, as shown here
Do you know of any other method that can be used to perform an internal reference calibration of the realsense d455? Please let me know.
2.When I start the SDK, the error message is constantly generated in the terminal where the SDK is launched, like this
When I start the SDK, the error message is constantly generated in the terminal where the SDK is launched, like this
And it keeps writing to the uvcdynctrl-udev.log file in /var/log, knowing that it takes up the entire root directory space. What is the reason for this?
The text was updated successfully, but these errors were encountered:
Hi @YiKang-Liu On-Chip calibration tends to work better in the 2.49.0 version of librealsense (the version before the 2.50.0 one that you are currently using). This is because there were a number of changes to the design of the on-chip calibration system in 2.50.0 that cause errors on some computers.
I would recommend installing librealsense 2.49.0 if possible. However, do not change your firmware driver version. 5.13.0.50 is the absolute minimum firmware that the D455 camera model is supported on, and you will likely cause your D455 to become inoperable if you install an older firmware than 5.13.0.50.
Alternatively, you could explore using the alternative Dynamic Calibration tool. Page 14 onwards of the user guide for the tool provides information about installing it on Ubuntu.
| Camera Model | {D455} |
| Firmware Version | (05.13.00.50) |
| Operating System & Version | {Linux (Ubuntu 20.04) |
| Kernel Version (Linux Only) | (5.15.0-122-generic) |
| Platform | PC |
| SDK Version | {2.50.0} |
| Language | {C/C#/labview/nodejs/opencv/pcl/python/unity } |
| Segment | {Robot } |
Issue Description
<Describe your issue / question / feature request / etc..>
I'm currently experiencing at least these two issues below with the SDk:
And after this problem, the SDK will not recognize the device unless the device is rebooted.
And after rebooting, the camera's imaging became very bad. The only way to get back to the original state is by rebooting several times
So I don't dare to try more
Then I tried to use depth_auto_calibration_example.py in example for internal calibration, but it still doesn't work, as shown here
Do you know of any other method that can be used to perform an internal reference calibration of the realsense d455? Please let me know.
2.When I start the SDK, the error message is constantly generated in the terminal where the SDK is launched, like this
When I start the SDK, the error message is constantly generated in the terminal where the SDK is launched, like this
And it keeps writing to the uvcdynctrl-udev.log file in /var/log, knowing that it takes up the entire root directory space. What is the reason for this?
The text was updated successfully, but these errors were encountered: