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

Cut at specific angle mode causes shifts in the packets #521

Open
msz-rai opened this issue Jun 1, 2023 · 0 comments
Open

Cut at specific angle mode causes shifts in the packets #521

msz-rai opened this issue Jun 1, 2023 · 0 comments
Labels

Comments

@msz-rai
Copy link
Contributor

msz-rai commented Jun 1, 2023

Please complete the following information:

  • OS and Version: Ubuntu 22.04
  • ROS Version: Humble
  • Downloaded from Official Repository:
  • Version: 2.3.0-1jammy.20230426.083248

Describe the bug
When setting cut_angle parameter to 2*Pi, the very first point cloud that is published has more points than expected (it consumes the first UDP packet from the next lidar rotation). The next point cloud counts are correct, but they are shifted by one UDP packet (the point cloud starts with the second UDP packet of the rotation and ends with the first UDP packet from the next lidar rotation).

I have presented this behavior in the video. VLP16 with 0.4 azimuthal resolution is located in the cube. Cube changes its position every 0.5 seconds.

velodyne_cut_angle_bug.webm

To Reproduce
I am working in simulation, so it may take time to set up the environment. I can provide a PCAP file.

Expected behavior
The driver in the cut at specific angle mode should track the azimuth delta between packets, and check whether the next packets would exceed the value of the cut_angle parameter.

@msz-rai msz-rai added the bug label Jun 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant