-
Notifications
You must be signed in to change notification settings - Fork 406
Update wrapper #918
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
Update wrapper #918
Conversation
- `pub_frame_rate` now controls the `InitParameters::grab_compute_capping_fps` parameter of the ZED SDK instead of controlling the frequency of a parallel thread. It's not a Dynamic parameter anymore. - Change `general/camera_flip` parameter to string: 'AUTO', 'ON', 'OFF' - Change 'general/verbose' from bool to integer
* Add `pos_tracking/set_gravity_as_origin` parameter * Add `pos_tracking/pos_tracking_mode` parameter.
Add parameter 'pos_tracking/set_as_static'
mattrouss
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When setting the depth mode to NONE in common.yaml, the 3D features are not visible in the rviz sample as expected. However the video view does not display the video as depicted here:
I can also reproduce in the ROS 2 rviz sample as well. Is it possible to still have the video view with depth_mode = NONE? It seems like the camera is not working, but the image topics do actually work.
|
That's a correct behavior. You must change |
|
Instead of changing the module entirely, would it be possible to set the frame to base_link only for the camera module? And will doing so impact the display of the other modules like object detection or skeleton tracking? |
|
That's not the usual way of using RVIZ. I prefer to leave it to |
|
Yes |
|
Modification pushed, but it's in the repository |


Port to ROS Wrapper the main improvements from the ROS 2 Wrapper