-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
The D435 set color exposure will effect the ir exposure? #3698
Comments
The two sensors should not be influencing each other. |
@dorodnic it can work well both of them in the RealSense Viewer. But the cameras have different firmware version.the good one version is 05.08.15.00 and the bad one is 05.10.06.00. Should i update the firmware version both of them? |
Okay... I revert the bad one firmware to the 05.08 that is can work normally... So what does the meaning of update? It really make a serious bug. @dorodnic |
@doronhi I was tested the SDK2.19 with the firmware version 05.11.100 and i found that the ir image will twinkle when i startup the program.I really don't konw where i was wrong and it confuse me for few day.We use the same code all the time. I really need your help right now. |
@dorodnic By the way, it can work well in the Realsesen-Viewer.Is my code wrong? |
Hi @Gitlaber, To clarify: |
Not see any issue about your partial code. I don't observe this issue. |
I found the firmware version down 05.10 that both cameras can work normally. If the firmware above 05.10 change the color exposure will effect the ir. |
@Gitlaber Suggest to modify below two lines. The sensor order might be not reliable. You can refer to the code snippet in #2637 to check the sensor type and then configure the exposure. auto colorSensors = profile.get_device().query_sensors()[1]; |
@RealSenseCustomerSupport Okay... But I personally think it must be the firmware version's problem. Because I use the same coding :
"The bad one" and "The good one" both can log the their information. After I downgraded "The bad one" to the 05.08.15.00, it can be used normally. |
@Gitlaber I tried your code snippet on win10 and Ubuntu16.04 with librealsense v2.21.0 but sorry that I couldn't reproduce your issue with FW 5.10.6 and 5.11.4. The exposure control of RGB and IR are independent seen from my result. |
@Gitlaber Any update from your side with the modifications about sensor order? Did you still get the issue? Looking forward to your update. Thanks! |
@Gitlaber Will close the ticket if you have no other questions. Thanks! |
Have you tested both USB2 and USB3? We've seen some issues that show on USB2 but not USB3 regarding exposure on 5.10.x firmware |
Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):
All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)
Issue Description
We want to set deduce the color camera's exposure and do that, but we find one of the D435 ir camera also be changed exposure when we deduce the color. Another is work correctly, anyone had met this question? It is the camera is broken?
Using the same code as it:
` auto colorSensors = profile.get_device().query_sensors()[1];
auto irSensor = profile.get_device().query_sensors()[0];
The bad one:
The good one:
The text was updated successfully, but these errors were encountered: