-
Notifications
You must be signed in to change notification settings - Fork 392
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
Non-static transform from base_link to camera #496
Comments
Hi @MikeWrockAIS In your case you can simply change the type of joint between In this way the |
Does it have to be the |
It depends on your configuration. You should modify the ZED URDF according to how the camera is linked on the robot. The important thing is that the chain |
It seems like once a valid transform from camera to base link is acquired mCamera2BaseTransfValid is set to true. Since the transform is only updated if mCamera2BaseTransfValid is false, I don't see how providing an up to date TF tree helps. Perhaps I should set mCamera2BaseTransfValid to false or simply remove the if statement and call getCamera2BaseTransform() every time? |
Yes, in your case you must update it at every cycle so you must remove the check. |
awesome, thanks a lot |
I keep the issue open as reminder for the feature to be added |
I have a smilar issue, tomorrow I will open a new issue and add the details. |
I noticed that even though you can set the frame in which to publish the ZED's odometry information, the current TF is not used. For example: if the camera is on a moving arm, when the arm moves the camera will publish odometry as if base_link moved, ignoring the current base_link to camera transform. Is there any way to tell the zed-wrapper the camera moves relative to base link during operation?
The text was updated successfully, but these errors were encountered: