Use Gazebo LaserScan message instead of direct LaserShape access
Max Schwarz
Branch: xqms/velodyne_simulator:timestamp_fix
Branch: DataspeedInc/velodyne_simulator:master
Merged
Merged pull request
Merged in xqms/velodyne_simulator/timestamp_fix (pull request #2)
Previously, we would use the time stamp of the last LaserScan message (LastUpdateTime), but with newer data. Now, the timestamp and data are synchronized, since they come from the same LaserScanStamped message.
This fixes issue #7.
I did not test with Gazebo2 yet, since I don't have it available right now.