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

USB2.1 infra-red exposure issue for short exposure times (<70usec) #2497

Closed
m0oz opened this issue Oct 9, 2018 · 4 comments
Closed

USB2.1 infra-red exposure issue for short exposure times (<70usec) #2497

m0oz opened this issue Oct 9, 2018 · 4 comments
Assignees

Comments

@m0oz
Copy link

m0oz commented Oct 9, 2018

Required Info
Camera Model D435
Firmware Version 05.10.03.00
Operating System & Version Linux (Ubuntu 16)
Kernel Version (Linux Only) 4.15.0
Platform PC
SDK Version 2.16.0
Language C++
Segment Robot

Issue Description

When connected to a USB2.1 port one cannot set the depth exposure time shorter than 70usec.
Exp times shorter than 70usec will lead to artifacts and over-exposed frames.

Steps to Reproduce

  • Connect a D435 to a USB 2.1 port and open realsense-viewer
  • Enable infra1 stream and set "enable auto exposure" to OFF
  • Set exposure time to something like 100usec and you get unaffected frames
  • Set exposure time to any value lower than 70usec and the frame becomes over-exposed (it looks brighter than at 100usec) and will show artifacts.

ATTENTION: When using a USB3.2 port we could not observe this issue

USB2.1, 90usec exposure USB3.2, 90usec exposure
usb2 1-90us usb3 2-90us
USB2.1, 60usec exposure USB3.2, 60usec exposure
usb2 1-60us usb3 2-60us

USB2.1, 1usec exposure, artifacts (salt and pepper)

usb2 1-1us

@RealSense-Customer-Engineering
Copy link
Collaborator

[Realsense Customer Engineering Team Comment]
Hello @m0oz,

Thank you for pointing out this issue! We were able to replicate the issue with RealSense Viewer and will work to create a fix shortly.
Please stay tuned, will update this issue when fix is implemented.

@m0oz
Copy link
Author

m0oz commented Oct 15, 2018

@RealSense-Customer-Engineering
Thank you for putting it on the list. I am looking forward to any news. If you figure out when the fix is released I'd be happy for a heads up ;)
We are having a hard time to capture usable data outdoors
(At least as long as this October stays this sunny here)

@mhkabir
Copy link

mhkabir commented Dec 6, 2018

@RealSense-Customer-Engineering Any updates?

@RealSense-Customer-Engineering
Copy link
Collaborator

[Realsense Customer Engineering Team Comment]
Hello @mhkabir, and @m0oz,

We added errata in this document: https://www.intel.com/content/dam/support/us/en/documents/emerging-technologies/intel-realsense-technology/RealSense-D400-Series-Spec-Update.pdf

Please review errata document, specifically "DSO-10603" for this issue.

Attached picture is newly added errata.

Thank you!

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

4 participants