Skip to content
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

D400 On-chip self-calibration crashes realsense viewer and works only on 30 fps on rs-depth-quality #6393

Closed
ArviSyrjanen opened this issue May 14, 2020 · 8 comments

Comments

@ArviSyrjanen
Copy link

ArviSyrjanen commented May 14, 2020


Required Info
Camera Model D435i
Firmware Version 5.12.3
Operating System & Version Linux Ubuntu 18
Kernel Version (Linux Only) 4.15.0
Platform PC
SDK Version 2.34.0

Hello!

Im trying to use the On-chip self-calibration feature, but when using it through realsense-viewer GUI, the program hangs and never recovers.
Screenshot from 2020-05-14 15-42-59

I did manage to use the self-calibartion feature through the rs-depth-quality application.
Screenshot from 2020-05-14 15-54-43

But even then I can only use the rate of 30 fps, if any other frame rate is chosen the calibration stops at 0% and never finishes.
Screenshot from 2020-05-14 15-55-10

This prevents me from using the 256x144 resolution for self-calibration recommended in the documentation, which is available only in 90 fps.
Screenshot from 2020-05-14 15-56-13

@MartyG-RealSense
Copy link
Collaborator

MartyG-RealSense commented May 14, 2020

There is an ongoing issue with SDK version 2.34.0 dating back to this SDK version's release at the end of March 2020, where the error message "get_device_time_ms() took too long (more then 2 mSecs)" can be generated continuously in the log window at the bottom of the Viewer window and On-Chip Calibration freezes the Viewer when the "Apply Now" button is clicked.

I have experienced both of these problems myself in Windows 10 and still do. Ubuntu and MacOS users have also encountered it. Reports of it have not been widespread, suggesting that some may be affected by it whilst others are not.

A fix for get_device_time_ms() was developed in a Pull Request but it has not passed merging into the RealSense SDK yet.

#6150

In the meantime, if you are affected by these errors then I recommend using the earlier SDK version 2.33.1 if possible until the get_device_time_ms() situation is rectified. I apologise that that this can cause difficulty if you need to use features introduced in 2.34.0 such as OpenVINO face detection within the RealSense Viewer.

@RealSenseCustomerSupport
Copy link
Collaborator


Hi @ArviSyrjanen
As to the issue about on-chip calibration hangs with Ubuntu 18.04
Thanks for your input. we will looking into this issue
by the way, could you confirm the kernel version you are using?
$uname -r
eg. 5.3.x ?

@ArviSyrjanen
Copy link
Author

ArviSyrjanen commented May 15, 2020

The kernel version is 4.15.0.

And I don't believe its the on-chip calibration that is necessarily the problem, as I can do it through the rs-depth-quality application. Just that the Viewer application crashes when I try to do it. Also as I stated, I can only do the on-chip calibration via. rs-depth-quality when the camera frame rate is set to 30. I have tried to do the on-chip calibration only with these two GUIs.

@RealSenseSupport
Copy link
Collaborator

@ArviSyrjanen
Yes, also able to duplicate the issue with my Ubuntu PC (18.04) with different camera sku (D415, D435).. We will looking into this issue definitely.

Hi @agrunnet , is there anything we need to configure or limitation that running on-chip calibration on Ubuntu 18.04

@agrunnet
Copy link
Contributor

From a programming perspective you need to make sure you use the poling mode and not the interrupt mode. (This is one of the flags in the call).

@RealSenseSupport
Copy link
Collaborator

Hi @ArviSyrjanen

before have newer version of viewer with the fix

you can either running 2.34 viewer on win10 PC

or running 2.33.1 viewer on your ubuntu PC #6231

@RealSenseCustomerSupport
Copy link
Collaborator


Hi @ArviSyrjanen,
There a fix that already commit to the latest development branch
you can check the detail from this pull request
#6427
best

@RealSenseSupport
Copy link
Collaborator

The Realsense SDK (build 2.35) is just released which has the fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants