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
In short the driver is publishing incorrect time stamp! I used mobile Sony Z2.
Martin sugested this
Regarding the wrong timestamp: Since your timestamp is almost exactly twice the actual value, I suspect that ImuPublisher.java#L173-L175 are responsible. The code assumes that event.timestamp is in nanoseconds of uptime, but some devices (e.g., the Nexus 4) instead put the exact timestamp (since 1970-01-01) in there.
Regards
Anas
The text was updated successfully, but these errors were encountered:
Hello,
This request is based on the discussion here :http://answers.ros.org/question/203408/strange-imu-stamp-time/?answer=203412#post-id-203412.
In short the driver is publishing incorrect time stamp! I used mobile Sony Z2.
Martin sugested this
Regarding the wrong timestamp: Since your timestamp is almost exactly twice the actual value, I suspect that ImuPublisher.java#L173-L175 are responsible. The code assumes that event.timestamp is in nanoseconds of uptime, but some devices (e.g., the Nexus 4) instead put the exact timestamp (since 1970-01-01) in there.
Regards
Anas
The text was updated successfully, but these errors were encountered: