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

在use_lidar_clock为false的情况下,decoder_RS16的timestamp解算存在小问题 #22

Open
tzccg0 opened this issue Oct 27, 2021 · 0 comments

Comments

@tzccg0
Copy link

tzccg0 commented Oct 27, 2021

Screenshot from 2021-10-27 10-17-20
从文档上来看,block1的first firing的第一个点和second firing的第一个点timestamp差为55.5us,因为decoder没有做比较细致的处理,每个firing的时间戳都是一样的,所以理论上packet里面第16个点和第17个点的时间戳差为55.5us

Screenshot from 2021-10-27 10-09-54
但现在是一样的

Screenshot from 2021-10-27 10-10-15
第32个点和第33个点的时间戳差约为55.5us

Screenshot from 2021-10-27 10-10-30
第48个点和第49个点的时间戳差约为55.5us
所以推测第一个block计算时间戳的代码存在一些小问题

(其实在计算时间戳的时候,用到了std::chrono::system_clock::now(),这样会引入decoder代码运行带来的微小的时间误差,是不是传入一个base_timestamp,直接用硬件理论上消耗的时间来计算更为合理?)

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

1 participant