ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
![]() | 1 | initial version |
I'm not sure is this your issue or not as I never use sick_tim pkg. But I think the issue is in the transform :
Requested time 806.12... but the latest data is at time 806.08... when looking up transform from frame [odom] to frame [map]
Take a look at tf and time
I suspect that you use ros::Time::now().
You should use ros::Time(0) instead to get the latest available transform in the buffer. Because there is a travel time in between sending the transform and receiving it in the buffer.
![]() | 2 | No.2 Revision |
I'm not sure is this your issue or not as I never use sick_tim pkg. But I think the issue is in the transform :
Requested time 806.12... but the latest data is at time 806.08... when looking up transform from frame [odom] to frame [map]
Take a look at tf and time
I suspect that you use ros::Time::now().
You should use ros::Time(0) instead to get the latest available transform in the buffer. Because there is a travel time in between sending the transform and receiving it in the buffer.
![]() | 3 | No.3 Revision |
I'm not sure is this your issue or not as I never use sick_tim pkg. But I think the issue is in the transform :
Requested time 806.12... but the latest data is at time 806.08... when looking up transform from frame [odom] to frame [map]
Take a look at tf and time )
I suspect that you use ros::Time::now().
You should use ros::Time(0) instead to get the latest available transform in the buffer. Because there is a travel time in between sending the transform and receiving it in the buffer.
![]() | 4 | No.4 Revision |
I'm not sure is this your issue or not as I never use sick_tim pkg. But I think the issue is in the transform :
Requested time 806.12... but the latest data is at time 806.08... when looking up transform from frame [odom] to frame [map]
I suspect that you use ros::Time::now().
You should use ros::Time(0) instead to get the latest available transform in the buffer. Because there is a travel time in between sending the transform and receiving it in the buffer.
![]() | 5 | No.5 Revision |
I'm not sure is this your issue or not as I never use sick_tim pkg. But I think the issue is in the transform :
Requested time 806.12... but the latest data is at time 806.08... when looking up transform from frame [odom] to frame [map]
Take a look at tf and time
I suspect that you use ros::Time::now().
You should use ros::Time(0) instead to get the latest available transform in the buffer. Because there is a travel time in between sending the transform and receiving it in the buffer.
![]() | 6 | No.6 Revision |
I'm not sure is this your issue or not as I never use sick_tim pkg. But I think the issue is in the transform :
Requested time 806.12... but the latest data is at time 806.08... when looking up transform from frame [odom] to frame [map]
I suspect that you use ros::Time::now().
You should use ros::Time(0) instead to get the latest available transform in the buffer. Because there is a travel time in between sending the transform and receiving it in the buffer.
![]() | 7 | No.7 Revision |
I'm not sure is this your issue or not as I never use sick_tim pkg. But I think the issue is in the transform :
Requested time 806.12... but the latest data is at time 806.08... when looking up transform from frame [odom] to frame [map]
Take a look at tf and timetime : http://wiki.ros.org/tf/Tutorials/tf%20and%20Time%20(C%2B%2B)
I suspect that you use ros::Time::now().
You should use ros::Time(0) instead to get the latest available transform in the buffer. Because there is a travel time in between sending the transform and receiving it in the buffer.
![]() | 8 | No.8 Revision |
I'm not sure is this your issue or not as I never use sick_tim pkg. But I think the issue is in the transform :
Requested time 806.12... but the latest data is at time 806.08... when looking up transform from frame [odom] to frame [map]
Take a look at tf and time : http://wiki.ros.org/tf/Tutorials/tf%20and%20Time%20(C%2B%2B)
I suspect that you use ros::Time::now().
You should use ros::Time(0) instead to get the latest available transform in the buffer. Because there is a travel time in between sending the transform and receiving it in the buffer.
Alternatively you can use ros::Time::now() - delay
EDIT:
See the change log
adjust time stamp - last scan point = now ==> first scan point = now - 271 * time increment - also just assume 0.001 s USB latency between scanner and PC for now this avoids TF ExtrapolationExceptions (cannot project into future)
![]() | 9 | No.9 Revision |
I'm not sure is this your issue or not as I never use sick_tim pkg. But I think the issue is in the transform :
Requested time 806.12... but the latest data is at time 806.08... when looking up transform from frame [odom] to frame [map]
Take a look at tf and time : http://wiki.ros.org/tf/Tutorials/tf%20and%20Time%20(C%2B%2B)
I suspect that you use ros::Time::now().
You should use ros::Time(0) instead to get the latest available transform in the buffer. Because there is a travel time in between sending the transform and receiving it in the buffer.
Alternatively you can use ros::Time::now() - delay
EDIT:
See the change log
adjust time stamp - last scan point = now ==> first scan point = now - 271 * time increment - also just assume 0.001 s USB latency between scanner and PC for now this avoids TF ExtrapolationExceptions (cannot project into future)
Did you download the latest version ?
![]() | 10 | No.10 Revision |
I'm not sure is this your issue or not as I never use sick_tim pkg. But I think the issue is in the transform :
Requested time 806.12... but the latest data is at time 806.08... when looking up transform from frame [odom] to frame [map]
Take a look at tf and time : http://wiki.ros.org/tf/Tutorials/tf%20and%20Time%20(C%2B%2B)
I suspect that you use ros::Time::now().
You should use ros::Time(0) instead to get the latest available transform in the buffer. Because there is a travel time in between sending the transform and receiving it in the buffer.
Alternatively you can use ros::Time::now() - delay
EDIT:
See the change log
adjust time stamp - last scan point = now ==> first scan point = now - 271 * time increment - also just assume 0.001 s USB latency between scanner and PC for now this avoids TF ExtrapolationExceptions (cannot project into future)
Did you download the latest version ?
![]() | 11 | No.11 Revision |
I'm not sure is this your issue or not as I never use sick_tim pkg. But I think the issue is in the transform :
Requested time 806.12... but the latest data is at time 806.08... when looking up transform from frame [odom] to frame [map]
Take a look at tf and time : http://wiki.ros.org/tf/Tutorials/tf%20and%20Time%20(C%2B%2B)
I suspect that you use ros::Time::now().
You should use ros::Time(0) instead to get the latest available transform in the buffer. Because there is a travel time in between sending the transform and receiving it in the buffer.
Alternatively you can use ros::Time::now() - delay
EDIT:
See the change log
adjust time stamp - last scan point = now ==> first scan point = now - 271 * time increment - also just assume 0.001 s USB latency between scanner and PC for now this avoids TF ExtrapolationExceptions (cannot project into future)
You may try increasing the time difference e.g. the 271 to 350
![]() | 12 | No.12 Revision |
I'm not sure is if this is your issue or not as I never use sick_tim pkg.
pkg.
But I think the issue is in the transform :
Requested time 806.12... but the latest data is at time 806.08... when looking up transform from frame [odom] to frame [map]
Take a look at tf and time : http://wiki.ros.org/tf/Tutorials/tf%20and%20Time%20(C%2B%2B)
I suspect that you use ros::Time::now().
You should use ros::Time(0) instead to get the latest available transform in the buffer. Because there is a travel time in between sending the transform and receiving it in the buffer.
Alternatively you can use ros::Time::now() - delay
EDIT:
See the change log
adjust time stamp - last scan point = now ==> first scan point = now - 271 * time increment - also just assume 0.001 s USB latency between scanner and PC for now this avoids TF ExtrapolationExceptions (cannot project into future)
You may try increasing the time difference e.g. the 271 to 350