Skip to content
This repository has been archived by the owner on Jan 24, 2018. It is now read-only.

Incorrect time-stamp in slam /odom topic #19

Open
mmoore13 opened this issue Aug 22, 2017 · 1 comment
Open

Incorrect time-stamp in slam /odom topic #19

mmoore13 opened this issue Aug 22, 2017 · 1 comment

Comments

@mmoore13
Copy link

Running roslaunch realsense_ros_slam demo_slam.launch and rostopic echo /odom displays messages with the following header format:

---
header: 
  seq: 813
  stamp: 
    secs: 186413771
    nsecs:         0
  frame_id: odom

The time-stamp here is not as expected.

Changing

odom.header.stamp = ros::Time(feTimeStamp);

to

odom.header.stamp = ros::Time(feTimeStamp / 1000);

seems to resolve the issue, yielding:

---
header: 
  seq: 102
  stamp: 
    secs: 1503427819
    nsecs: 480166912
  frame_id: odom

Line 380 looks like it should also be changed in the same way.

@dashneptune
Copy link

It would be nice if this could get fixed, this was causing calls to Time::now to get out of range of 32 bit for me and was causing the SLAM demo to fail

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants