# Micro-ROS telemetry: what a 100 Hz target does—and doesn’t—prove

**URL:** <https://discourse.openrobotics.org/t/micro-ros-telemetry-what-a-100-hz-target-does-and-doesn-t-prove/59079>\
**Category:** Projects\
**Created:** [October 23, 2026, 12:59am UTC](https://discourse.openrobotics.org/t/micro-ros-telemetry-what-a-100-hz-target-does-and-doesn-t-prove/59079 "2026-10-23T00:59:23Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![RoboTechJournal](https://avatars.discourse-cdn.com/v4/letter/r/aeb1de/32.png) [@RoboTechJournal](https://discourse.openrobotics.org/u/RoboTechJournal)\
**Post date:** [October 23, 2026, 12:59am UTC](https://discourse.openrobotics.org/t/micro-ros-telemetry-what-a-100-hz-target-does-and-doesn-t-prove/59079/1 "2026-10-23T00:59:23Z")

</div>

A nominal 100 Hz timer doesn’t prove deterministic end-to-end delivery, especially over Wi-Fi. Measure jitter, dropped messages and Agent outages on your actual hardware. RoboTech Journal’s ESP32-S3/STM32 example is illustrative and untested; the guide explains the reference setup and caveats: [micro-ROS on ESP32 and STM32: Telemetry Guide | RoboTechJournal](https://robotechjournal.com/posts/micro-ros-esp32-stm32-telemetry/)

What measurements do you use to validate the full path from MCU to ROS 2 host?