Work around RGBXYZ stream hangs (issue #25) #38
Closed
Conversation
This file contains 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
Apparently, this is triggered when the depth_image_proc/register nodelet fails with a TF2 'timestamp is in the future' error and doesn't publish the registered depth image properly. This seems to cause the ROS Synchronizer filter to choke. Work around by moving the published timestamp further into the future.
|
@mkhansen-intel Yes, go ahead. |
mdhorn
added a commit
to mdhorn/realsense
that referenced
this pull request
Jul 13, 2016
Add Project Contribution Conditions
doronhi
pushed a commit
that referenced
this pull request
Feb 18, 2021
Add service to reset driver and catch more exceptions when shutting down device.
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.
Fixes Issue: #25
Changes proposed in this pull request:
Apparently, this is triggered when the depth_image_proc/register nodelet
fails with a TF2 'timestamp is in the future' error and doesn't publish
the registered depth image properly. This seems to cause the ROS
Synchronizer filter to choke.
Work around by moving the published timestamp further into the future.