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

Is it available to use not hard-sychronoized lidar camera system ? #52

Open
lovelychaean opened this issue Jan 24, 2025 · 2 comments
Open

Comments

@lovelychaean
Copy link

I have a spinning lidar (ouster) and camera, but we don't have hard-synchorizing board (STM32, ...)
Can I use this sensors for fast lvio2?

@ustc-flicar
Copy link

I have successfully run Fast-LIVO2 with a Velodyne HDL-32 LiDAR, a camera and xsens IMU:
https://github.com/ustc-flicar/ustc-flicar.github.io

Image

Given that the Ouster LiDAR (with n internal IMU) is functionally similar, it should also be compatible with Fast-LIVO2 when used alongside a camera.

I recommend using an STM32 or FPGA for hardware synchronization, as accurate time sync is important for Fast-LIVO2’s performance.

@xuankuzcr
Copy link
Member

Thanks @ustc-flicar for the explanation and the nice results. What he said is absolutely correct.
It’s recommended to use the hard-synchronized data, but if that’s not feasible, you can fill in the time_offset section in the config file and provide the correct time delay. This approach can still yield good results.

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

3 participants