-
Notifications
You must be signed in to change notification settings - Fork 315
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
tf::TransformBroadcaster didn't broadcast the transform of the marker to /tf #61
Comments
I had a similar issue. Have you find out why this would happen? |
I experience the same. It is fixed when I echo the marker or an other topic on the terminal (in my case |
Is there anyway to have this work without manually subscribing to the pose? |
@QuantuMope as @TaekedeHaan pointed out. The transform is only published when there is a subscription to one of the topics. It was designed such a way, as the ARuCo marker detection is computationally intensive(#92). You could write a ROS node that subscribes to one of the topics, at the instance you need the transform published. |
It would be great to mention this in the readme, as it seems that every new person (including myself) first spends a few hours figuring this out |
i also encountered the same issue |
I'm using ros kinetic and realsense. The package successfully locate the marker as I checked /aruco_single/result and /aruco_single/transform. But the strange thing is /tf topic is empty although "br.sendTransform(stampedTransform)" in the code. Has any one met this problem before? Thanks a lot.
The text was updated successfully, but these errors were encountered: