Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[cob_scan_unifier] LookupError on start up #268

Closed
fmessmer opened this issue Mar 4, 2016 · 3 comments · Fixed by #324
Closed

[cob_scan_unifier] LookupError on start up #268

fmessmer opened this issue Mar 4, 2016 · 3 comments · Fixed by #324

Comments

@fmessmer
Copy link
Contributor

fmessmer commented Mar 4, 2016

Appears once on startup, probably simply requires a sleep after tf::TransformListener initialization (for filling the buffer):

Node: /scan_unifier
Time: 16:05:39.612337463 (2016-03-04)
Severity: Error
Published Topics: /rosout, /scan_unified

Lookup would require extrapolation into the past.  Requested time 1457103936.557201524 but the earliest data is at time 1457103937.074180613, when looking up transform from frame [base_laser_front_link] to frame [base_link]

Location:
/u/fxm/git/care-o-bot/src/cob_driver/cob_scan_unifier/src/scan_unifier_node.cpp:LaserScan scan_unifier_node::unifieLaserScans:252

Also, unifieLaserScans should be unifyLaserScans 😉

@ipa-nhg
Copy link
Contributor

ipa-nhg commented Apr 22, 2016

I had the same issue during the cob4-5 setup. But in this case the error appears constantly and not only just once on startup. Checking the visualization (RVIZ), I notified that the errors loggin corresponded to a wrong transformation/scanner lecture. The driver mixed the header and the data of the messages, for example the data read by the scan_front were transformed to the scan_right frame. After set the loop_rate of the driver to 10Hz, it is working properly. @ipa-bnm any ideas?

@mgruhler
Copy link
Contributor

mgruhler commented Feb 8, 2017

@ipa-nhg do you remember why you had to set the loop rate to 10 Hz here?

@fmessmer
Copy link
Contributor Author

@ghost ghost mentioned this issue Mar 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants