You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the timestamp of IMU have two kinds of base number, sometime the secs of timestamp is like 1608015601, sometime the secs of timestamp is like 3216031523
#1569
Closed
TouchDeeper opened this issue
Dec 15, 2020
· 5 comments
I find a strange phenomenon. the timestamp of IMU has two kinds of the base number. sometimes I start the realsense node, the secs of the timestamp is like 1608015601, but there are also sometimes I start the realsense node, the secs of the timestamp is like 3216031523. The Global time of Motion Module showed in realsense-viewer is like 1608015601, and I guess the timestamp like 1608015601 is what I want since if the timestamp is like 3216031523, I will have timestamp related error when using Kalibr to process camera-imu joint calibration. I have posted the isue in Kalibr repository.
Could you please provide some advice to keep the secs of the timestamp of IMU in 1608015601 like number? Thans a lot.
The launch file I used to start the realsense node is:
The two methods that worked for RealSense users in that discussion to correct the timestamps are to add initial_reset:=true to the end of the roslaunch instruction, or to enable global time.
@MartyG-RealSense
Hi
Thanks for your reply. Adding <arg name="initial_reset" default="true"/> solve my issue.
I want to know what the initial_reset do. In addition, I recommend you can write a parameter explanation document that explant what teach parameter do, this document will be very popular and useful. Thanks again.
initial_reset performs a hardware reset of the camera at launch, similar to the Hardware Reset option in the RealSense Viewer and the hardware_reset() programming instruction in librealsense.
The RealSense ROS wrapper front page has a section with a list of launch commands that includes initial_reset:
I'm sorry I forget the parameters page. I have calibrated the realsense d435i successfully. I recorded this process and the problems encountered and solutions. To thank you, I shared this document in my repository. I hope it will help other people.
Hello,
I find a strange phenomenon. the timestamp of IMU has two kinds of the base number. sometimes I start the realsense node, the secs of the timestamp is like 1608015601, but there are also sometimes I start the realsense node, the secs of the timestamp is like 3216031523. The
Global time
of Motion Module showed inrealsense-viewer
is like 1608015601, and I guess the timestamp like 1608015601 is what I want since if the timestamp is like 3216031523, I will have timestamp related error when using Kalibr to process camera-imu joint calibration. I have posted the isue in Kalibr repository.Could you please provide some advice to keep the secs of the timestamp of IMU in 1608015601 like number? Thans a lot.
The launch file I used to start the realsense node is:
the output of terminal when I start the realsense node is:
The text was updated successfully, but these errors were encountered: