Add offset-timestamp param#109
Open
LihanChen2004 wants to merge 1 commit intoros:ros2from
Open
Conversation
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
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.
I have added a new parameter
offset_timestampto thejoint_state_publisher.Here’s an explanation of why I needed this parameter, and I believe other developers might also find it useful.
My robot setup is as follows: the
gimbal_yawandgimbal_pitchare actuable, and their attitude is obtained via the IMU sensor on the embedded development board. The data is then transmitted to the NUC via UART as aJointStatetype. I use thejoint_state_publisherandrobot_state_publisherto publish the full vehicle’s TF data.One subtle issue is that there is a delay in the data transfer from the embedded development board to the NUC (approximately 0.008 seconds in our system based on testing). Although this delay is small, the real-time nature of our development work makes it impactful. It causes an apparent lag in the transformation of the
gimbal_pitchsensor intochassis(or other fixed world coordinate frame). After adding theoffset_timestamp, the issue was significantly mitigated.