Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi Device Sync Issue (Timestamps are far from right on specific devices) #85

Open
nivesh48 opened this issue Nov 5, 2024 · 2 comments

Comments

@nivesh48
Copy link

nivesh48 commented Nov 5, 2024

I am trying to sync two femto mega devices from external trigger, using the two_device_sync_save_data.py script. I am following the default stream settings just to test. The timestamps on the saved images are way off.

color_1_17076276
color_0_17076306

If you just see the above instance where the difference in the closest timestamps of saved images are 3-4 seconds off each. The timestamp for each image itself is not appropriate?

Why are the timestamps of each device so inconsistent from one another. Does this require any firmware update, the current version I’m using is 1.27.0

Additionally, device.get_depth_work_mode_list() returns device not supported

@zhonghong322
Copy link
Contributor

1、Is the multi-device sync hub connected correctly?
https://www.orbbec.com/docs/set-up-cameras-for-external-synchronization_v1-2/

2、I will also try to replicate the issue you reported

3、device.get_depth_work_mode_list() ,Gemini2 Series support,Mega unsupport.

@nivesh48
Copy link
Author

nivesh48 commented Nov 7, 2024

@zhonghong322, yes, we use multi-camera synchronization Hub for this and followed the details provided in https://www.orbbec.com/docs/set-up-cameras-for-external-synchronization_v1-2/.

Also, on a side note what are the depth modes supported by Femto Mega? I believe a detailed documentation of repo would help better.
I am so unsure how the setup with a sync box is ending up with random time stamps?

Below are some details regarding my implementation:

Config file:
{ "devices": [ { "serial_number": "CL2T441003F", "config": { "mode": "PRIMARY", "depth_delay_us": 0, "color_delay_us": 0, "trigger_to_image_delay_us": 0, "trigger_out_enable": true, "trigger_out_delay_us": 0, "frames_per_trigger": 1 } }, { "serial_number": "CL2T44100AX", "config": { "mode": "SECONDARY", "depth_delay_us": 160, "color_delay_us": 0, "trigger_to_image_delay_us": 160, "trigger_out_enable": true, "trigger_out_delay_us": 0, "frames_per_trigger": 1 } } ] }

In OrbbecSDKConfig_v1.0.xml config file i have made changes to memory buffer. I am using software mode for depth alignment. I would like to know if there's a way to reset the device clocks to system clock before streaming or in anyway can we reset the clock?

Also, does the firmware version have any impact? Our cameras are on version 1.2.7

Pretty weird that sometimes it only grabs frames from one camera (same system and software versions) using two_device_sync_save.py file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants