-
Notifications
You must be signed in to change notification settings - Fork 18
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
Depth camera stops working #140
Comments
How many cameras have this issue? After the problem occurs, if you power off the camera and then power it back on, does the issue still persist? |
This error is caused by an exception when reading parameters from the camera. |
3 out of 8 cameras developed this problem. The problem persists even after restarting. I tried it with different cables as well. Is it possible that it's a hardware issue? Somewhere I remember seeing that it's not recommended to write the MultiDeviceSyncConfig to the device too often so that the flash memory doesn't stop working. And I have done this only a very few times. But could this be a possible cause? |
I'm encountering the same issue. Similarly, I've only run the config a handful of times. |
I'm working on a setup where I run multiple (up to 8) Bolts synchronized and triggered by an external trigger. I have the setup working, but after some time, some of the Bolts started developing problems. They can only use the color camera and have no output on the depth/ir cameras. I tried it from the SDK (v1.10.12) and OrbbecViewer as well. When running the code I get the following error in the logs (this is the output of the DepthViewer example). What does this error code mean? Is it a software or hardware issue?
Some more context: other Bolts work well when using them alone or with other Bolts, the problematic ones don't work in either case, even when they are the only device plugged in.
The text was updated successfully, but these errors were encountered: