Skip to content

Commit 510183e

Browse files
committed
Update ROS-API with new set of world origin service
1 parent 6be0c71 commit 510183e

File tree

1 file changed

+11
-1
lines changed

1 file changed

+11
-1
lines changed

docs/40-api/01-uav_ros_api.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -172,6 +172,7 @@ Please refer to [estimation_manager.launch.py](https://github.com/ctu-mrs/mrs_ua
172172
| **service** | **description** | **service type** |
173173
|-------------------------------------|-------------------------------|-----------------------------------------------------------------------|
174174
| estimation_manager/change_estimator | switch to a desired estimator | [mrs_msgs/String](https://ctu-mrs.github.io/mrs_msgs/interfaces/srv/String.html) |
175+
| estimation_manager/set_world_origin | set a new world origin | [mrs_msgs/ReferenceStampedSrv](https://ctu-mrs.github.io/mrs_msgs/interfaces/srv/ReferenceStampedSrv.html) |
175176

176177
## Transform manager
177178

@@ -182,13 +183,22 @@ The [TransformManager](../50-features/01-managers/index.md#transformmanager) han
182183
| **TF** | **description** | **example usage** |
183184
|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|
184185
| fcu_untilted_origin | (heading only) fcu frame with removed tilts (z-axis is aligned with the gravity vector) | commanding UAV in body frame disregarding tilts |
185-
| world_origin | origin position defined by the world file, ENU orientation, based on UTM estimators (GPS, RTK, etc.), does not exist for non-UTM estimators | commanding UAV localized by UTM-based estimator in a locally defined coordinate world |
186+
| world_origin | origin position defined initially by the world file or set with the `estimation_manager/set_world_origin` service, ENU orientation, based on UTM estimators (GPS, RTK, etc.), does not exist for non-UTM estimators | commanding UAV localized by UTM-based estimator in a locally defined coordinate world |
186187
| local_origin | origin pose defined by the initial pose of the UAV (including orientation), exists for all estimators | commanding UAV w.r.t. initial pose, universal frame that is always available |
187188
| fixed_origin | origin pose defined by the initial estimator, origin does not move after estimator switch, odometry in this frame jumps after estimator switch | commanding UAV w.r.t. initial estimator frame, universal frame that is always available |
188189
| stable_origin | origin pose defined by the initial estimator, origin jumps after estimator switch, odometry in this frame is smooth without jumps | mapping position of detected objects invariant to estimator switching |
189190
| utm_origin | origin position defined by the intersection of the equator and the zone's central meridian, ENU orientation | commanding UAV in absolute metric coordinates regardless of the current world file |
190191
| mapping_origin_tf | origin position and heading defined by initialization of a SLAM algorithm, origin tilt around x and y axes optionally defined by custom topic | mapping of environment using a SLAM that cannot estimate orientation |
191192

193+
### Provided services
194+
195+
| **service** | **description** | **service type** |
196+
|-------------------------------------|-------------------------------|-----------------------------------------------------------------------|
197+
| transform_manager/set_world_origin | set a new world origin | [mrs_msgs/ReferenceStampedSrv](https://ctu-mrs.github.io/mrs_msgs/interfaces/srv/ReferenceStampedSrv.html) |
198+
199+
>**NOTE**: This service is called internally by the `Estimation Manager` when calling the `estimation_manager/set_world_origin` service. This will only update the world origin for the TF sources, not the world origin in the Estimation Manager. To keep both managers in sync, always call the service in the Estimation Manager.
200+
201+
192202

193203
## Trajectory generation
194204

0 commit comments

Comments
 (0)