Week 05 · overview
Week 05: Flight Controllers, Signals, and Wiring Discipline
This week, you will build signal path trace for a bounded Drone Engineering scenario. The work stays in classroom-safe analysis, supplied evidence, simulation, planning, and documentation. It does not authorize real flight or unsupervised hardware work.
The engineering problem
A drone arms inconsistently after a receiver cable is moved during maintenance.
The core idea is that the flight controller is the nervous system, but wiring decides whether the signals arrive cleanly. Students will connect that idea to receivers, IMUs, GPS modules, ESCs, telemetry radios, and power modules connect through defined signal and power paths.
Evidence you keep
| Sequence | Evidence artifact |
|---|---|
| Lesson 1 | Mechanism explanation and first evidence table |
| Lesson 2 | Boundary note and no-go or revision condition |
| Lesson 3 | Review-ready decision table |
| Flight Log | Signal path trace with limitation statement |
Vocabulary and decision lens
Important language this week includes: system boundary, evidence, limitation, no-go condition, revision rule, and flight controllers, signals, and wiring discipline.
Decision lens: freeze the wiring state, document the signal path, inspect labels, then change one controlled variable at a time.
Approximate time: 3 to 4 class periods, about 160 to 200 minutes of reading, analysis, evidence writing, and review.