Failed attempts to switch to Femto Bolts

Depthkit Depthkit Studio
1

Continuing the discussion from Femto Bolt installation issues:

Another failed attempt to successfully connect 4-8 Femto Bolts. Some still report as USB 2.1 despite following advised Femto Bolt Issues

Please recommend what else we can check. We are stumped at this point!! If possible can we please arrange a 1-2-1 online consultation? Hopefully this is still covered by my licence agreement?

  1. We have now reverted to the Orbbec v1.0.9 firmware on all sensors, compatible with DepthKit Studio (and not the latest Orbbec release).

  2. We have ensured all cable connections and power are securely connected.

  3. All cable extensions are DepthKit recommended Startech USB extension USB3AAEXT10M or 5M.

  4. All sensors are attached using the Femto Bolt factory supplied usb cables.

  5. DepthKit Studio software is v8.0.1 running on top of the range Dell laptop which was proven to support 6-8 Azure Kinect.

  6. 2 off 4 x USB cables connected to Sonnet Echo Express SEL Thunderbolt 3 with 4 x https://www.startech.com/en-us/cards-adapters/pexusb3s44v

connected to Laptop’s Thunderbolt 3 20Gbs port. Same as for Azure Kinect.

  1. All Femto Bolts synchronised using the recommended Ethernet 5e cables and DepthKit Studio Femto Bolt recommended configuration.

One Orbbec Sync Hub Pro(power supply & cable not included), USB power supply, and USB Type-C power cablefor up to 9 sensors.

2

@Terence - Can you confirm that for each sensor with a USB 2.x connection, you exited Depthkit, launched Orbbec Viewer, and used it to restart the sensor (as described in the documentation), multiple times if necessary? When using StarTech extender cables inline with the Femto Bolt sensors, we have always been able to re-establish a proper USB 3.x connection, which remains valid across system restarts.

Alternatively, we have also re-established valid USB 3.x connections by

  • disconnecting all sensors from the computer
  • powering all sensors off
  • waiting 10 seconds
  • powering all sensors on
  • Connecting one sensor to the computer.
  • Waiting 10-15 seconds for the sensor to establish the connection.
  • Confirming that the sensor is fully connected in Orbbec Viewer or Depthkit
  • Repeating this connection, waiting, and confirmation of connection with each sensor until all sensors are connected.

We acknowledge that this is frustrating, and are exploring the newer versions of the Orbbec SDK to try to improve the sensor connection stability. As you can see in Orbbec’s GitHub, this is still an open issue, so an absolute fix doesn’t yet exist.

It’s also worth mentioning that we have not tested the Sonnet Thunderbolt PCIe adapter you are using, and that though it worked seamlessly with the Azure Kinect, slight differences in the connection topology could be causing an issue when using it with the Bolt sensors.

Regarding a 1-on-1 support session, I’ll email you to coordinate.