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

Parameter odom_frame_id is not used in ros2-development #2602

Open
elanius opened this issue Jan 19, 2023 · 4 comments
Open

Parameter odom_frame_id is not used in ros2-development #2602

elanius opened this issue Jan 19, 2023 · 4 comments

Comments

@elanius
Copy link

elanius commented Jan 19, 2023

Why is param odom_frame_id not used anymore? There is only a default value which is "odom_frame".
I usually use just "odom", and now I cannot overwrite it.

In the readme file, this parameter is mentioned.
Another misinformation is related to base_frame_id, which now appends parameter value to the camera_name.

@MartyG-RealSense
Copy link
Collaborator

Hi @elanius What ROS launch instruction are you using with the ros2-development wrapper, please? Also, which RealSense camera model are you using?

@MartyG-RealSense
Copy link
Collaborator

Hi @elanius Do you require further assistance with this case, please? Thanks!

@elanius
Copy link
Author

elanius commented Jan 27, 2023

Hi @MartyG-RealSense. Now, I use only published odom messages and generate TF by myself. But at least it should be fixed in README.md to be clear for developers that the name for odom frame is fixed. The same is true for base_frame_id, which behaves differently as it is written.

@MartyG-RealSense
Copy link
Collaborator

MartyG-RealSense commented Jan 27, 2023

I will label this case as Enhancement so that it can be looked at by RealSense ROS team members responsible for documentation at a future date. The case should be kept open, but you do not need to take further action. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants