[ROS-2] Average rate of transform between the odom and the base link is slow
Hey,
I'm using the differential drive plugin to simulate a robot in ROS 2. The distro used is Rolling.
I wanted transform between the odom and the base_footprint of the robot, so I use the lookup transform from tf2. Eventually I was not able to determine it because of the warning I had:
"odom" passed to canTransform argument target_frame - frame does not exist
Note that I also had a waitTransform()! I further went a bit deep and I found that the transformation between the "odom" and the "baselink" is being published very slow. Here is the output of the tf2monitor:
``` [INFO] [1631802573.358697219] [tf2monitormain]: Waiting for transform odom -> basefootprint: Invalid frame ID "odom" passed to canTransform argument targetframe - frame does not exist Gathering data on odom -> basefootprint for 10 seconds... RESULTS: for odom to basefootprint Chain is: odom -> base_footprint Net delay avg = 3.10486e+08: max = 1.6318e+09
Frames:
Frame: base_footprint, published by
What could be the reason for it?
Asked by pmuthu2s on 2021-09-20 06:59:44 UTC
Comments