voxl_mpa_to_ros2 camera_interface timestamp
-
Heya,
I just found out something that's causing me issues with my TF's in ROS2. Shouldn't the timestamp of the ROS2 msgs be constructed from both nanosecs and secs?
In the camera_interface.cpp only the nanosecs field is populated causing the timestamp to be incompatible with any ROS2 time conventions.
This however is not the case in the imu_interface.cpp which works as intended.
Thought I would point it out!
-
@smilon ,
I believe you are correct! Thank you. We will double check this and fix.
-
@Alex-Kushleyev Great! Please ping me here whenever you have this updated because current workaround is kinda ugly :S. Thanks a lot!
-
@smilon , we have a merge request that is being tested - https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-to-ros2/-/merge_requests/8/diffs?commit_id=a128608d0ad1e4c417edc7013f9bbbf9665b754b#diff-content-bbec15f81097cb24d4e021ae03a1c7aa01ff13d6
Can you please take a look and help confirm this is what you are expecting?
Thank you
-
@smilon You can find an updated package here: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-mpa-to-ros2_0.0.2-202402291159_arm64.deb. This should work fine with SDK 1.1.2.
-
Dear @Alex-Kushleyev, @Eric-Katzfey this did the trick! Thanks for the quick fix!! Everything works as expected now.
-
@smilon, great! thank you for bringing this issue to our attention in the first place.
-
Hi guys sorry for getting this thread up again,
i am experiencing same issue with my cameras and qvio ros2 topics
time stamp rests after few seconds , time stamp of seconds stays at zerosec 0 STUCK AT ZERO nsec 3300161870 REACHING TO 3 BILLION (3 SECONDS) frame_id "tracking" height 480 width 640 encoding "mono8" is_bigendian 0 step 640
any fixes that match SDK 1.1.3 ?
-
@jacob-yaacubov Are you able to use the deb provided above with the fix? i'll check when it will officially be in SDK
-
@Alex-Kushleyev i have used the dev branch in the voxl-mpa_to_ros2
and this branch has a fix , built it from source
-
@jacob-yaacubov , FYI, this fix will be in 1.2.0 release which is in testing now