Camera not working or detected
Q1: The camera is connected, but when I launch the Orbbec Viewer tool on Ubuntu system, it doesn’t detect the device.
Add sudo permissions when you launch the Orbbec Viewer tool.
Q2: The camera is connected, Orbbec Viewer tool cannot detect the camera device after a period of use, but the camera device can be detected in the system terminal with “lsusb” command.
Disconnect the camera USB port and reconnect it.
Q3: Camera is connected to the USB3.0 port, but it is incorrectly identified as USB2.0.
First, you can check whether the USB cable and the host port are USB3.0 compliant and make sure the USB connector is fully plugged in;
Then, disconnect the camera USB port and reconnect it smoothly.
Q4: Orbbec Viewer tool doesn’t detect the device after you restart the host.
Maybe you restrat the host straightly without closing the data streams. If you want to restart the host, please close all the data streams first.
Q5: When you run the Orbbec Viewer tool on a brand-new Ubuntu 22.04 system, the camera doesn’t work.
First, you should grant permissions to the installation file in the Orbbec Viewer directory. To do this, you could enter the path of the script file and then execute the command “sudo chmod 777 install.sh”;
Second, proceed to execute command “sudo ./install.sh”;
Lastly, run Orbbec Viewer with the command “sudo ./OrbbecViewer”.
Q6: How to get the log of hardware level?
Here are three ways to get the log.
- Turn on the “heartbeat” switch in Orbbec Viewer;
- By API,device->setBoolProperty(OB_PROP_HEARTBEAT_BOOL, true);
- By configuration file, config the “DefaultHeartBeat” as 1. The file is located at ./SDK/Config
Q7: When the camera is connected to the USB2.0 port, the camera identification may take a long time.
We recommend using the USB3.0 port and the corresponding USB cable;
If you use the USB2.0 port or USB2.0 cable, camera identification takes about 20 seconds.
Function
Q1: The display resolution in metadata is half of the set resolution or less.
Switching off the decimation filter can solve this issue. You can find it in: Depth => Advanced Control => Decimation Filter.
Q2: Failed to switch to another depth preset when any data stream is started.
If you want to switch to another depth preset, please close all the data streams first.
Q3: When depth, IR left, IR right and RGB are streaming at the same time, there may be some frame loss. This problem may exist on some hosts.
High-end hosts are essential for simultaneously streaming depth, IR left, IR right and RGB data due to rapid memory access required for high-throughput data transmission via USB connection. If low-end hosts are deployed or hosts are heavily loaded, start with fewer than four data streams to ensure more reliable data transmission.
We recommend the following configuration to you:
Ubuntu 20.04/22.04 i7-7700 CPU@3.60GHz x64 8GB, or above.
Q4: Set another IR resolution when depth data stream is started，it may cause some data streams error with a low probability.
If you want to set another resolution, please close all the data streams first.
Q5: In “Orbbec Viewer-Device Control-Preset-Factory Calib” mode, there are many resolutions of depth and IR data stream cannot be started.
The “factory calib” only supports specific resolution. It is an internal production mode and is therefore not recommended for general use.
Q6: Point cloud may not be built accurately if you mirror, flip or rotate the depth/color data stream in the previous step, it will also lead to align mode error.
Mirror, flip, or rotate is seen as illegal operation for pointcloud preview. Please restore to original state and try again.
Q7: Start the depth and IR stream immediately when you switch to another depth preset, it may fail with a low probability.
The tool will reload some parameters when you switch to another depth preset, we advise waiting 3 seconds before starting the data stream.
Q8: In linux, if you press “Ctrl+C” on the terminal to exit the Orbbec Viewer, it may fail to start the depth and IR stream when you restart Orbbec Viewer immediately.
It takes time for the Viewer to exit, we advise waiting for 3 seconds before restarting it.
Q9: In linux, if you connect two or more cameras on one low-end host, it may fail to start all the cameras and all the data stream.
You can try to increase the system buffer size to solve this problem.
Try to execute “sudo sh -c ‘echo 128> /sys/module/usbcore/parameters/usbfs_memory_mb”.
Q10: Color data stream cannot be started after updating the firmware.
The RGB firmware update was unsuccessful; please try updating it again.
