UAV Systems Engineering · Interactive simulation · M1-L6

UAV System Architecture Builder

Wire a complete UAV system from sensors to motors, read the interface behind every link, and let the design rules tell you what is missing.

UAV Fundamentals and System Architecture
Established engineering
Runs entirely in your browser

What you are looking at

The diagram has five layers: Sensors → Perception → State estimation → Planning and supervision → Flight control. Select a block to read what it does and what it may connect to. Select a link to see its message type, typical rate, coordinate frame, design notes and typical failure. Add links with the From and To menus (or load a preset architecture) and read the check report on the right.

Only interfaces that exist in the catalogue can be created. Try connecting the camera directly to PX4’s EKF2: the builder explains why that does not exist.

Try this

Load “Autonomous, GNSS-dependent” and read the warnings. Which single failure takes it down?
Build a GNSS-denied design from the “Basic GNSS UAV” preset by adding only the interfaces you need. Aim for zero errors and as few warnings as you can justify.
Select the link from the fusion estimator to EKF2. Which frame conversion does the note require, and which parameters does it name?
Remove the link from the fusion estimator to the supervisor. What does the checker say, and which lesson in module 8 explains why it matters?
Compare the “Vision-aided” and “LiDAR-inertial” presets: list the failure modes in the link inspector that differ between camera and LiDAR.

Model and its limits

Included: 15 blocks, 25 interfaces and the design rules that the checker applies: a state estimate must reach the controller; autonomy needs a setpoint stream; odometry nodes need their sensor and inertial coupling; position must not depend on GNSS alone if GNSS-denied operation is required; GNSS-independent sources should be diverse; and navigation health must reach a supervisor.

Not included: timing, bandwidth and power budgets (module 7), and every possible architecture. Rates are typical and must be checked against datasheets. PX4 topic names follow the px4_msgs / uXRCE-DDS conventions of recent PX4 releases and can change between versions: confirm against the PX4 documentation for the version you fly.

Related lessons

Saved in this browser and synced to your account when you are signed in.

Back to Module 1 · UAV track overview