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

What impact does autoware have on lidar point clouds in terms of bandwidth transmission? #6920

Closed
3 tasks done
The-wind-rises-2023 opened this issue May 5, 2024 · 8 comments
Assignees
Labels
component:sensing Data acquisition from sensors, drivers, preprocessing. (auto-assigned)

Comments

@The-wind-rises-2023
Copy link

Checklist

  • I've read the contribution guidelines.
  • I've searched other issues and no duplicate issues were found.
  • I'm convinced that this is not my fault but a bug.

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

@knzo25
Copy link
Contributor

knzo25 commented May 7, 2024

@The-wind-rises-2023
We experience that phenomena not only on Jetson devices but on other ECUs, desktops, etc.
Usually you need to tune your dds and network adapter settings.
This not really an autoware issue but general ROS/particular driver issue

@idorobotics
Copy link

@knzo25 are you able to share your DDS parameter and/or network settings?

@knzo25
Copy link
Contributor

knzo25 commented May 7, 2024

Mostly we use this
https://autowarefoundation.github.io/autoware-documentation/main/installation/additional-settings-for-developers/

And tune as needed depending on our sensors. Other than that, MTU size on the interface.

@meliketanrikulu meliketanrikulu added the component:sensing Data acquisition from sensors, drivers, preprocessing. (auto-assigned) label May 9, 2024
@meliketanrikulu
Copy link
Contributor

Hello @idorobotics . Did you tested with new DDS configs? Is this documentation fixed your problems ?

@idorobotics
Copy link

Hello @idorobotics . Did you tested with new DDS configs? Is this documentation fixed your problems ?

cc @knzo25

@knzo25
Copy link
Contributor

knzo25 commented May 10, 2024

I think you meant to mention @The-wind-rises-2023

Copy link

stale bot commented Jul 9, 2024

This pull request has been automatically marked as stale because it has not had recent activity.

@stale stale bot added the status:stale Inactive or outdated issues. (auto-assigned) label Jul 9, 2024
@vividf
Copy link
Contributor

vividf commented Jul 23, 2024

@The-wind-rises-2023
Kindly ping.
If the problem is solved, I would like to close this issue.

@stale stale bot removed the status:stale Inactive or outdated issues. (auto-assigned) label Jul 23, 2024
@vividf vividf closed this as completed Aug 16, 2024
@vividf vividf self-assigned this Aug 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component:sensing Data acquisition from sensors, drivers, preprocessing. (auto-assigned)
Projects
None yet
Development

No branches or pull requests

5 participants