-
Notifications
You must be signed in to change notification settings - Fork 90
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
PointCloud rate issue (CustomFormat) #39
Comments
@Eragon123, I am facing the same issue with my AVIA. I am also facing an issue with the IMU. My IMU rate is only at 60Hz. May I know what changes you did to get the expected IMU rate? |
Have you been solve it? I have the same question with you |
1 similar comment
Have you been solve it? I have the same question with you |
I solved the imu problem, but the lidar custom message still cannot reach 10hz, but strangely, another computer can reach it |
There seems to be an issue with the Custom PointCloud Format. When I select
xfer_format = 1
then for apublish_freq
of 50Hz I only get around 27-30Hz and for apublish_freq
of 10Hz an actual lidar pointcloud rate on the/livox/lidar
topic of 6.5Hz.The imu publish frequency always seems to match the expected frequency of
What does work:
xfer_format = 0
the published pointcloud frequency matches the expected lidar publish frequency (e.g. 50Hz) and the CPU usage is also ~5% similar to the ROS1 driver.Possible problem source(s):
FillPointsToCustomMsg
function, the rate for the Custom PointCloud reaches the expected 50Hz or 10Hz respectively. The CPU usage in this scenario also goes down to only ~6%.I have already tried speeding up the
FillPointsToCustomMsg
function in various ways without any effect on the publish frequency. My understanding is, that with 50packets per published PointCloud and 96 points per packet the loop inside theFillPointsToCustomMsg
function does 12Million steps per second. However the same function in the ROS1 Driver works just fine!Notes:
ros2 topic hz
200Hz
Thanks for any help!
The text was updated successfully, but these errors were encountered: