-
Notifications
You must be signed in to change notification settings - Fork 698
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
What impact does autoware have on lidar point clouds in terms of bandwidth transmission? #6920
Comments
@The-wind-rises-2023 |
@knzo25 are you able to share your DDS parameter and/or network settings? |
Mostly we use this And tune as needed depending on our sensors. Other than that, MTU size on the interface. |
Hello @idorobotics . Did you tested with new DDS configs? Is this documentation fixed your problems ? |
cc @knzo25 |
I think you meant to mention @The-wind-rises-2023 |
This pull request has been automatically marked as stale because it has not had recent activity. |
@The-wind-rises-2023 |
Checklist
Description
When we tested on a dual ORin device, we found that when one ORin runs a semi-solid lidar driver, the point cloud frequency will decrease after the other ORIN starts autoware.
Expected behavior
Normal point cloud frequency:10hz
Actual behavior
Only 7hz
Steps to reproduce
One of the dual orins runs the radar driver, and the other orin observes the point cloud frequency before and after starting autoware.
Versions
Jetpack5.1.2 Docker autoware1.0 ros humble
Possible causes
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: