You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`default_pub_rate_us`| 100.0 | Default interval the time manager will publish to the `clock` topic (in microseconds) |
165
-
|`real_time_multiplier`| 1.0 | Multiplier for configuring faster or slower than real time simulations. E.g. set to 2 to run 2 times as fast as real time|
162
+
|`real_time_multiplier`| 1.0 | Multiplier for configuring faster or slower than real time simulations |
166
163
167
164
!!! example "Pub rate example"
168
165
@@ -182,8 +179,24 @@ This is done by configuring the parameters associated with the `time_manager` no
182
179
### SIL Board
183
180
184
181
### Sensors
182
+
The `sensors` module is responsible for generating simulated sensor measurements based on the current true state.
183
+
These sensor measurements are published to the `/simulated_sensors/XXX` topics, where `XXX` is each sensor, i.e. `imu/data` or `baro`, etc.
184
+
185
+
The `sensors` node adds noise, walk, and biases to each sensor measurement to simulate the real-world data.
186
+
See the code for more information on how the noise is added.
187
+
188
+
Note that the `sensors` node subscribes to the `forces_and_moments` topic (for the IMU measurement), the truth states, and the `status` topic.
189
+
The `status` topic is used to approximate when the motors are spinning so high-frequency noise can be added to the gyros.
190
+
191
+
Also note that the `sensors` node could have been implemented as a separate node for each sensor.
192
+
If you are adding a new sensor (e.g. camera), you could either change the `sensor` source code or create an entirely separate ROS2 node for your sensor.
185
193
186
194
### Forces and Moments
195
+
!!! danger "TODO"
196
+
continue here... This page is still under construction. Check back soon!
0 commit comments