Thanks for contacting Intel customer support.
Can you please send me a picture of your camera?
Also can you please run lsusb | grep 8086 and share with me the results?
Thanks for your understanding.
My camera is Creative VF0800.
No output for "lsusb | grep 8086".
You can check the result for lsusb:
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 008: ID 041e:4099 Creative Technology, Ltd
Bus 003 Device 007: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The camera device is not showing up in the kernel logs so it doesn't look like it is being detected. Make sure that you are connecting the camera to a USB 3 port using the original cable that came with the development kit. Also try connecting it to a Windows 10 PC and check the Device Manager. Does Device Manager say F200 or SR300. The Creative VF0800 cameras can be F200 or SR300 and this is an old model that looks like an F200. The F200 camera is not recognized by the RealSense SDK 2.0.
I am glad to know you have found a solution for the issue. Still if you want us to assist you troubleshoot the inestability issue of your camera we can assist you with this issue. We will need you to send us the SDK logs of your camera. Here are the instructions to obtain the SDK logs:
- You will need to download and install the Intel® RealSense™ SDK. Click here for detailed instructions with screen shots on collecting SDK logs.
- If you are using the SR300 or F200 cameras download and install the RealSense SDK Essentials package from here. If you are using the R200 camera, download the RealSense SDK R2 from here.
- Run the SDK debug tool by executing "C:\Program Files (x86)\Intel\RSSDK\bin\x64\SDK_Info.exe" as an Administrator.
- In the SDK_Info tool, navigate to the Logging Tab.
- Click “Enable All Logs” button
- Reproduce the issue by running whatever app is causing the failure (make sure not to close sdk_info, it can be minimized, closing sdk_info will stop the logging).
- After the failure has occurred return to SDK_Info and click “Save” button (in sdk_info logging tab).
- Zip the created directory and attach it to your reply.