Synchronization Issues

If you have encountered synchronization issues with your sensors, first reference the icon key below to learn what each icon represents, and then proceed to the sensor-specific troubleshooting sections further below.

Synchronization Status

Global Sync Indicators (3D Viewport):

(Hidden): If Femto Bolts are being used, there will be no global sync icon shown until the sensors are started and the sync configuration is discovered by Depthkit.

🔗: This link icon indicates that the sensors are hardware synchronized.

→🔗: This link icon indicates that external hardware sync mode enabled with the Azure Kinect. Sensors will start producing frames when the external sync signal is received. See the External Sync section of the Azure Kinect DK Sensor sync page for more details.

: This warning icon indicates that sync cables are not properly configured for one or more sensors. When using Femto Bolts, you must start streaming first before Depthkit can detect this issue. See the individual sync status icons next to each sensor to narrow down which sensors are misconfigured.

: This wait icon indicates that one or more sensors are waiting to receive sync signal. If you are intending to use external sync with the Azure Kinect, you can expect to see this before you start the sync generator. If this lasts more than a few seconds, check the individual sync status icons next to each sensor to narrow down which sensors are not receiving sync.

Sensor Synchronization Indicators (Sensor Configurations Pane)

⬤ : A filled circle indicates that this sensor is connected, and once the sync configuration is detected, this indicates that the sensor is in Subordinate mode. For Femto Bolt sensors, synchronization status will be determined when streaming starts.

⭐ : A star indicates that this sensor was determined to be the Control/Primary sensor.

⭘ : An empty circle indicates that this sensor is disconnected. This sensor will not be included when Depthkit starts streaming. If this sensor is an Azure Kinect in the middle of the daisy-chain configuration and is intended to supply sync signal from its Sync Out port to another connected sensor, either reconnect the sensor to the PC, or reconfigure the sync cables to bypass this sensor.

⭘⭘ : (Azure Kinect only) Two empty circles indicates Sensor is in Standalone mode. No sync cables are detected. Connect sync cables to sensors to ensure hardware sync.

⭗⭘ : (Azure Kinect Only) Two circles with the left circle containing an arrow indicates that this sensor has a cable connected to its Sync Input, but no cable connected to it's Sync Output, and that this sensor will start in Subordinate mode. If this sensor is intended to be the last subordinate sensor in the daisy chain, then this is correct - If not check the connection of the cable plugged into this sensor's Sync Out port.

⭘⭗ : (Azure Kinect only) Two circles with the right circle containing an arrow indicates that this sensor has a cable connected to its Sync Output, but no cable connected to it's Sync Input and that this sensor will start in Control mode.. If this sensor is intended to be the Control sensor and is the first sensor in the daisy chain, then this is correct - If not check the connection of the cable plugged into this sensor's Sync Input port.

⭗⭗ : (Azure Kinect only) Two circles with both containing an arrow indicates that this sensor has a cable connected to its Sync Input and Output ports. If this sensor is intended to be in the middle of the daisy chain, then this is correct. This sensor will start in Subordinate mode.

⏳: This wait icon indicates that this sensor is waiting to receive sync signal. This may appear if a subordinate sensor has a cable plugged into its Sync Input port, but there is no signal coming from that connection. Check the cables connected to this sensors to ensure that they are plugged into the sensor's sync input, as well as the Sync Hub Pro Secondary port (Femto Bolt) or the Sync Out port of the previous sensor (Azure Kinect).

⚠️ : This warning icon indicates that there is one or more of the following issues issue with the sensor. Hover over the icon to reveal a tooltip with more information.

• No sync cables are detected, which will cause the sensor to incorrectly start in Standalone mode.
• The sensor has lost one of the connections to its sync port(s). Connect sync cables to sensors to ensure hardware sync.
• The sensor has an outdated firmware - See the Sensor firmware page for more information.
• The sensor has a slow USB connection - See the Femto Bolt Issues page for more information.

Expand the Sensor details in the Sensor Configurations panel to see more details for troubleshooting:

Femto Bolt Synchronization

Sync Configuration Could Not Be Detected

If Depthkit displays this message that states that it cannot determine the sync topology of your sensors, a number of things might be the cause, including disconnected or improperly connected cables.

To troubleshoot:

• Check the connections of the sync adapters and CAT-5e cables at both ends to ensure every sensor is properly connected.
• Confirm that one of your sensors is connected to the Sync Hub Pro's Primary sync port.
• If using two Sync Hub Pros, confirm that the CAT-5e cable connecting the Hub-to-Hub ports of the two Sync Hub Pros is properly connected.
• If using two Sync Hub Pros, confirm that only one of the hubs has a sensor plugged into the Primary sync port, and that the sync port of the other hub is unoccupied.

If the configuration still is not detected, you can disconnect the sensors and reintroduce them one at a time to isolate which sensor(s) introduce the issue to the system:

• Unplug all sensors from the computer.
• Power off all sensors.
• Wait 10 seconds.
• Power on all sensors.
• Connect one sensor to the computer.
• Wait 10-15 seconds for the sensor to establish the connection.
• Confirm that the sensor appears, and that all sensors can start streaming in Depthkit's Studio Calibration & Capture tab.
• Repeat connecting, waiting, and confirming streaming for each sensor until all sensors are connected.
• If streaming fails once a sensor is connected, confirm that that sensor's USB connection and firmware are correct.