We have half a dozen venues, each with a computer installation with 3 femto bolts. At one particular location, we are having issues with one of the depth cameras, it is failing in both our software and the orbbec viewer with the error:
[05/05 13:35:10.700228][error][15260][MSDEConverterDevice.cpp:101] Depth engine create and initialize failed,retCode:103
Details:
Host machine is Windows 10/11.
Orbbec Femto Bolt SN CL83842001C
FW Version 1.1.2
SDK Version 2.2.8
Connection: USB3.1
No temperature issues, no dropped hardware. Plugged in with USB and power, solid white LED on back. The client reports the FRONT LED flashes orange when the depth camera is engaged.
In Orbbec viewer (version: OrbbecViewer - 20260128 19:46:59 - V1.10.35-main), the RGB camera for this unit works fine, but when you try to view the depth camera, it never shows up. The other two Femto Bolts attached to the computer have working RGB AND Depth cameras.
This is the log for the orbbec viewer session:
http://kortham.net/temp/STL-Venue-Try2-OrbbecSDK.log.txt
Note the lines (line 1140 onward)
Depth engine create and initialize failed,retCode:103
Note at line 1792, a different camera successfully loads the depth engine.
We are aware camera CL8A842013Y is using USB2.1. That Depth camera works fine, although it runs at 5fps instead of 30. We’re going to have a technician fix that connection. I don’t think it’s related to the issue with CL83842001C.
All three Femto Bolts show up in the windows USB device tree- the depth and rgb cameras show up three times each.
I looked into retCode:103 and see it here in your source code:
OrbbecSDK_v2
src/device/femtobolt/rawphase/depthengine/k4aplugin.h#L232
The firmware 1.1.2 is slightly out of date. I see 1.1.3 on the website. All 3 cameras are on 1.1.2, so I don’t expect updating one (or all) of them will help, but I’m willing to try it.
This issue has persisted for a few weeks across multiple reboots.
As a FATAL_ERROR_UPDATE_CALIBRATION_FAILED. Is this a failed piece of hardware, or a cable issue?