@@ -22,29 +22,34 @@ ArduPilot exposes "sensor" type data over DDS, that usually corresponds to a phy
2222 <th >Topic Name</th >
2323 <th >Topic Type</th >
2424 <th >Description</th >
25+ <th >Default Frequency</th >
2526 </tr >
2627 <tr >
2728 <td >ap/navsat/navsat0</td >
2829 <td >sensor_msgs/msg/NavSatFix</td >
2930 <td >This is the reported GPS sensor position from the GPS subsystem.
3031 TODO It will include a frame ID as instance number</td >
32+ <td >GPS-driven</td >
3133 </tr >
3234 <tr >
3335 <td >ap/battery</td >
3436 <td >sensor_msgs/msg/BatteryState</td >
3537 <td >This sends the battery state for each enabled battery.
3638 The battery instance is available in the frame ID.
37- Each enabled battery will be have data published.
39+ Each enabled battery will be have data published.</td >
40+ <td >1 Hz</td >
3841 </tr >
3942 <tr >
4043 <td >ap/imu/experimental/data</td >
4144 <td >sensor_msgs/msg/IMU</td >
4245 <td >This is the high rate IMU data from the IMU that is currently used in the EKF.</td >
46+ <td >200 Hz</td >
4347 </tr >
4448 <tr >
4549 <td >ap/airspeed</td >
4650 <td >geometry_msgs/msg/Vector3Stamped</td >
4751 <td >This is the 3D airspeed estimate of the vehicle in body frame.</td >
52+ <td >30 Hz</td >
4853 </tr >
4954 </tbody >
5055 </table >
@@ -60,32 +65,38 @@ Pose, Rates, and Coordinates
6065 <th >Topic Name</th >
6166 <th >Topic Type</th >
6267 <th >Description</th >
68+ <th >Frequency</th >
6369 </tr >
6470 <tr >
6571 <td >ap/gps_global_origin/filtered</td >
6672 <td >geographic_msgs/msg/GeoPointStamped</td >
67- <td >This is the filtered AHRS's inertial navigation origin. This is NOT the same ask the HOME location.
73+ <td >This is the filtered AHRS's inertial navigation origin. This is NOT the same ask the HOME location.</td >
74+ <td >1 Hz</td >
6875 </tr >
6976 <tr >
7077 <td >ap/twist/filtered</td >
7178 <td >geometry_msgs/msg/TwistStamped</td >
7279 <td >This is the filtered AHRS's velocity in the local ENU frame relative to home.</td >
80+ <td >30 Hz</td >
7381 </tr >
7482 <tr >
7583 <td >ap/pose/filtered</td >
7684 <td >geometry_msgs/msg/PoseStamped</td >
7785 <td >This is the filtered AHRS's pose in the local ENU frame relative to home.</td >
86+ <td >30 Hz</td >
7887 </tr >
7988 <tr >
8089 <td >ap/geopose/filtered</td >
8190 <td >geographic_msgs/msg/GeoPoseStamped</td >
8291 <td >This is the filtered AHRS's pose (position+orientation) in global coordinates</td >
92+ <td >30 Hz</td >
8393 </tr >
8494 <tr >
8595 <td >ap/tf_static</td >
8696 <td >tf2_msgs/msg/TFMessage</td >
8797 <td >AP broadcasts its known static transforms on this topic.
8898 The transforms include the GPS sensor offsets relative to the vehicle origin.</td >
99+ <td >N/A</td >
89100 </tr >
90101 </tbody >
91102 </table >
@@ -101,16 +112,19 @@ Time
101112 <th >Topic Name</th >
102113 <th >Topic Type</th >
103114 <th >Description</th >
115+ <th >Frequency</th >
104116 </tr >
105117 <tr >
106118 <td >ap/time</td >
107119 <td >builtin_interface/msg/Time</td >
108120 <td >This sends time from AP's real time clock.</td >
121+ <td >100 Hz</td >
109122 </tr >
110123 <tr >
111124 <td >ap/clock</td >
112125 <td >rosgraph_msgs/msg/Clock</td >
113126 <td >This sends time from AP's real time clock in a format suitable for aligning ROS time of a companion computer.</td >
127+ <td >100 Hz</td >
114128 </tr >
115129 </tbody >
116130 </table >
0 commit comments