You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I have two Femot Bolt depth cameras updated to firmware 1.1.2 and connected via multisync cables and a daisy chain hub. I am trying to configure the depth trigger delay but the secondary device depth delay is being ignored whe using Orbbec Viewer version 2.1.1-main
Reproduction Steps
Connect the two cameras via USB and multi-sync cable config.
Run two instances of the Orbbec viewer. Connect one to the primary device and the other to the secondary.
Run Orbbec Viewer and connect to secondary device.
Enter Device Control . Synchronization Configuration:
Set mode to secondary
Depth Delay to 160uS
Write settings
Viewer says multi-sync config succeed! but the Depth delay value is reset ot 0uS
On starting depth stream, output is correctly paused until the Primary stream is started. However, on starting the primary stream, depth is started on the secondary but suffers from interference as there is no delay between Primary and Secondary.
Expected behavior
I expect the Depth delay setting to be stored and used to separate the image captures.
System Environment:
Windows 11
x86_64
OrbbecViewer_v2.1.1_202412201710_b40e003_win_x64
Device Information:
Model: Femto Bolt
Firmware Version: 1.1.2
Additional context
Setting the delay using the k4aviewer appears to work OK. My final objective is to set it using the SDK but this also seems to suffer the same problem as the Orbbec Viewer.
The text was updated successfully, but these errors were encountered:
I'm following these instructions, specifically Appendix IV for the Femto Bolt but
On my primary
The trigger out enable control is off and disabled. (But don't think this is an issue)
On my secondary, on opening it comes up as:
Which says Mode secondary_synced even though this is not one of the drop down options
When I change this to select Secondary and put in a value of 160us for depth delay then press write:
It says write mutli sync succeeded but changes the depth delay to 0us.
On starting the depth stream it does wait for the primary stream to also be started but the picture looks like the depth cameras are interfering (increased and pulsing noise present)
It does appear to work properly if I follow these instructions: k4a wrapper multisync
so the k4a wrapper somehow makes it work properly.
But my objective is to get it to work from the SDK and this shows the same problem as the Orbbec Viewer. Please advise how I can make it work.
Describe the bug
I have two Femot Bolt depth cameras updated to firmware 1.1.2 and connected via multisync cables and a daisy chain hub. I am trying to configure the depth trigger delay but the secondary device depth delay is being ignored whe using Orbbec Viewer version 2.1.1-main
Reproduction Steps
Connect the two cameras via USB and multi-sync cable config.
Run two instances of the Orbbec viewer. Connect one to the primary device and the other to the secondary.
Run Orbbec Viewer and connect to secondary device.
Enter Device Control . Synchronization Configuration:
Set mode to secondary
Depth Delay to 160uS
Write settings
Viewer says multi-sync config succeed! but the Depth delay value is reset ot 0uS
On starting depth stream, output is correctly paused until the Primary stream is started. However, on starting the primary stream, depth is started on the secondary but suffers from interference as there is no delay between Primary and Secondary.
Expected behavior
I expect the Depth delay setting to be stored and used to separate the image captures.
System Environment:
Windows 11
x86_64
OrbbecViewer_v2.1.1_202412201710_b40e003_win_x64
Device Information:
Additional context
Setting the delay using the k4aviewer appears to work OK. My final objective is to set it using the SDK but this also seems to suffer the same problem as the Orbbec Viewer.
The text was updated successfully, but these errors were encountered: