-
Notifications
You must be signed in to change notification settings - Fork 551
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
Detected not valid consecutive stamps #1156
Comments
Here are some more logs. The ingoing messages are the same, rgb, depth, camera info with synced time stamps, but every so often the odom throws the error:
|
What means Looking at this log:
There is a delay over 200 ms between the consecutive images. If you do |
Hi Mathieu,
Thanks so much for taking a look at this! I wasn't able to fix the problem
but I was still able to do the demo I wanted to do.
I will close this ticket for now.... :)
Thanks again for your time
…On Sat, May 25, 2024 at 6:08 PM matlabbe ***@***.***> wrote:
What means pre-processed images? Are some same images published on same
topic name? You can check with ros2 topic info
/bam_BAMDENAILER/camera_top/aligned_depth_to_color/image_raw/preprocessed
to see if there is more than one publisher for that topic.
Looking at this log:
[rgbd_odometry-7] [INFO] [1716442766.304188074] [bam_BAMDENAILER.rgbd_odometry]: Odom: quality=222, std dev=0.000424m|0.038764rad, update time=0.040266s
[rgbd_odometry-7] [WARN] [1716442766.304773995] [bam_BAMDENAILER.rgbd_odometry]: Odometry: Detected not valid consecutive stamps (previous=1716442766.219197s new=1716442766.219197s). New stamp should be always greater than previous stamp. This new data is ignored.
[rgbd_odometry-7] [INFO] [1716442766.516892608] [bam_BAMDENAILER.rgbd_odometry]: Odom: quality=153, std dev=0.000410m|0.038614rad, update time=0.032296s
There is a delay over 200 ms between the consecutive images. If you do ros2
topic hz
/bam_BAMDENAILER/camera_top/aligned_depth_to_color/image_raw/preprocessed,
has it a stable rate?
—
Reply to this email directly, view it on GitHub
<#1156 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGZUQL3J5TT7X6OLE3WNM4TZEEYZNAVCNFSM6AAAAABIE5JQJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZRHA3DCMBUGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hello!
I am having an undesirable behaviour I was hoping you could help with!
I am using a intel real sense d405. I am sending rgb, depth and camera info straight to an RGBD odometry node.
The headers on the rgb, depth and camera info are synced perfectly. The odometry node however throws an error because the "stamps should always be greater"
The node is only subscribed to the rgb, depth and info topic.
The odometry does work, but it doesn't seem to be tracking well as I move the object, and I thought this is perhaps caused by it dropping the data, as per the error message,
Thank you for help!!
The text was updated successfully, but these errors were encountered: