Skip to content

Publish continuous ESAD state telemetry - #2

Open
ryanjAA wants to merge 1 commit into
Dronecode:mainfrom
ryanjAA:continuous-esad-state-telemetry
Open

ryanjAA wants to merge 1 commit into
Dronecode:mainfrom
ryanjAA:continuous-esad-state-telemetry

Conversation

@ryanjAA

@ryanjAA ryanjAA commented Jul 28, 2026 •

Copy link
Copy Markdown

Summary

  • Publish HEARTBEAT and current ESAD_STATE at 1 Hz
  • Preserve immediate ESAD_STATE responses after ARM and SAFE requests
  • Update the direct host test to ignore buffered periodic state messages
  • Use the supported STM32 Uart implementation for the NUCLEO-F103RB link
  • Document continuous state reporting and the verified memory footprint

Validation

  • NUCLEO-F103RB firmware compiled successfully with STM32 Arduino core 3.0.0
  • Firmware uses 15 percent flash and 10 percent RAM
  • Python host tools passed bytecode compilation
  • Firmware flashed successfully to a connected NUCLEO-F103RB
  • AAGS (our QGC) continuously displayed fresh ESAD Safe telemetry beyond its five second freshness threshold

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant