IMPORTANT: Fixed Imu hz in non cuda and added imu values for cuda#24
Open
MatteGombia wants to merge 3 commits into
Open
IMPORTANT: Fixed Imu hz in non cuda and added imu values for cuda#24MatteGombia wants to merge 3 commits into
MatteGombia wants to merge 3 commits into
Conversation
To not lose the decimal numbers
Unit is 25 microseconds as documentation says
changxingshuo
force-pushed
the
master
branch
from
226e55f to
3346e74
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The imu was published every packet because the timestamp considered was the one of the packet itself. Now it publishes the value just when the values are updated. Furthermore, The function DecodePacket never returns 1, so the imu callback was never called in the cuda version.
The timestamp of the message has been updated with the correct imu timestamp.
This pull request solves partially the issue #37 and fully the #25 (and probably #36) of https://github.com/HesaiTechnology/HesaiLidar_ROS_2.0