Skip to content

Commit de6e825

Browse files
committed
update rqt_reconfigure image in README.md
1 parent 5ff2cd3 commit de6e825

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

README.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -98,6 +98,10 @@ Setting *unite_imu_method* creates a new topic, *imu*, that replaces the default
9898
- **clip_distance**: remove from the depth image all values above a given value (meters). Disable by giving negative value (default)
9999
- **linear_accel_cov**, **angular_velocity_cov**: sets the variance given to the Imu readings. For the T265, these values are being modified by the inner confidence value.
100100
- **hold_back_imu_for_frames**: Images processing takes time. Therefor there is a time gap between the moment the image arrives at the wrapper and the moment the image is published to the ROS environment. During this time, Imu messages keep on arriving and a situation is created where an image with earlier timestamp is published after Imu message with later timestamp. If that is a problem, setting *hold_back_imu_for_frames* to *true* will hold the Imu messages back while processing the images and then publish them all in a burst, thus keeping the order of publication as the order of arrival. Note that in either case, the timestamp in each message's header reflects the time of it's origin.
101+
- **topic_odom_in**: For T265, add wheel odometry information through this topic. The code refers only to the *twist.linear* field in the message.
102+
- **calib_odom_file**: For the T265 to include odometry input, it must be given a [configuration file](https://github.com/IntelRealSense/librealsense/blob/master/unit-tests/resources/calibration_odometry.json). Explanations can be found [here](https://github.com/IntelRealSense/librealsense/pull/3462). The calibration is done in ROS coordinates system.
103+
- **publish_odom_tf**: If True (default) publish TF from odom_frame to pose_frame.
104+
101105

102106
### RGBD Point Cloud
103107
Here is an example of how to start the camera node and make it publish the RGBD point cloud using aligned depth topic.
@@ -119,7 +123,7 @@ The following command allow to change camera control values using [http://wiki.r
119123
```bash
120124
rosrun rqt_reconfigure rqt_reconfigure
121125
```
122-
<p align="center"><img src="https://user-images.githubusercontent.com/40540281/52912434-30783180-32ba-11e9-8ab8-b08be5eba434.PNG" /></p>
126+
<p align="center"><img src="https://user-images.githubusercontent.com/40540281/55330573-065d8600-549a-11e9-996a-5d193cbd9a93.PNG" /></p>
123127

124128
### Work with multiple cameras
125129
Here is an example of how to start the camera node and streaming with two cameras using the [rs_multiple_devices.launch](./realsense2_camera/launch/rs_multiple_devices.launch).

0 commit comments

Comments
 (0)