Hello,
I have a couple of static_transform_publishers from the TF2 package running. How is it possible that a node complains about extrapolating into the future, when it tries to lookup a transformation from a random element to the static one? In my [understanding](http://wiki.ros.org/tf2/Migration), the static-transforms should be valid for all eternity, so why would you complain about timing issues?
A further explanation about my setup:
I have 2 Kinects and I am using those in my moveIt setup to create the Octomap.
As explained [here](http://answers.ros.org/question/192871/tf-extrapolation-into-future-wierd-chain/), moveIt complains about extrapolation into the future while looking up a transform from my robot to the cameras.
My first solution was to write a python node, which would handle all the publishing instead of seperate static_transform_publishers from the old TF. There, I could date the transformations back in time to avoid those issues.
Now I read about the static transforms in TF2 and implemented all the camera transformations like this:
↧