Mission 07 / SITL / TELEMETRY
UAS Simulation and Programming
Interpret a synthetic sensor snapshot and learn how software-in-the-loop testing keeps early experiments inside simulation.
Briefing
Read a software-in-the-loop telemetry snapshot
Software-in-the-loop (SITL) runs flight-control software against simulated sensors and a simulated vehicle. This starter teaches telemetry interpretation only; it does not control hardware.
Keep the boundary clear
PX4 and ArduPilot provide their own simulation workflows. A local SITL setup is separate infrastructure that must be installed and configured by the learner. The browser lesson here is an approximation with a fixed invented snapshot, not a flight simulator or connection to either project.
Read state, not just numbers
Telemetry may contain armed state, flight mode, GPS quality, attitude, and battery estimates. Interpret each field in context. A `hold` mode does not prove the simulated vehicle is stationary, and a sensor value is not a safety guarantee.
Test and inspect
A safe software workflow records the initial state, runs a bounded scenario, inspects the generated log, and checks expected behavior. MAVLink is a message protocol used by many autopilot systems; this introductory example uses a plain synthetic JSON snapshot instead of a live telemetry stream.
Practical exercise
Run the mission
Run the parser against the synthetic snapshot and report the armed state and flight mode.
Progressive hint
Read the `armed` and `mode` keys. Normalize the result to `armed=false,mode=hold`.
Need another hint?
The snapshot is disarmed and in HOLD mode. Convert booleans and mode labels to lowercase.
Run the starter to see observable output. Code is saved in this browser.
Pyodide · Python in WebAssembly · isolated short-lived browser worker
Knowledge check
What does SITL mean in this course?
Official project references