Documentation of my Summer Internship in UAV embedded systems and autonomous flight at the Department of Electrical Engineering, IIT Jammu, under Dr. Sudhakar Modem. This repo captures the engineering knowledge, configuration workflows, and design reasoning behind building and commissioning a Pixhawk/ArduPilot-based quadcopter.
This repo is structured the way I'd want a systems reference to be structured if I had to onboard someone else onto the same hardware: architecture first, protocols second, configuration procedures third, failure modes last. Each doc is written to stand alone as a reference, not just to summarize what happened.
graph TD
subgraph Power
BAT[LiPo Battery] --> PM[Power Module]
PM --> FC[Flight Controller]
PM --> ESC1[ESC x4]
end
subgraph Sensing
IMU[IMU: Accel + Gyro] --> FC
BARO[Barometer] --> FC
MAG[Magnetometer/Compass] --> FC
GPS[GPS Module] --> FC
end
subgraph Control_Loop["Control Loop (400 Hz+)"]
FC -->|PWM| ESC1
ESC1 --> M1[Motor 1 CW]
ESC1 --> M2[Motor 2 CCW]
ESC1 --> M3[Motor 3 CW]
ESC1 --> M4[Motor 4 CCW]
end
subgraph Command_Link
RX[RC Receiver] -->|SBUS/PPM| FC
TX[RC Transmitter] -.RF.-> RX
TEL[Telemetry Radio] <-->|UART 57.6k/915MHz| FC
GCS[Mission Planner GCS] <-->|MAVLink| TEL
end
style FC fill:#f96,stroke:#333,stroke-width:2px
Core principle governing this whole system: the flight controller runs a closed-loop feedback system at 400+ Hz -> read sensors -> estimate state (attitude/position) -> compare against commanded setpoint -> compute correction -> output PWM to ESCs. Every subsystem below exists to feed that loop accurate data or to carry pilot/GCS intent into it.
UAV-Flight-Controller-Systems/
├── README.md
├── docs/
│ ├── 01-quadcopter-architecture.md Hardware fundamentals & component theory
│ ├── 02-flight-controllers.md Pixhawk 2.4.8 vs Cube Orange, IMU/sensor fusion
│ ├── 03-ardupilot-configuration.md Firmware, calibration, flight modes, MAVLink
│ ├── 04-parameter-reference.md Key ArduPilot parameters & tuning notes
│ ├── 05-assembly-and-preflight.md Build log, wiring, pre-arm checklist
│ └── 06-troubleshooting-guide.md Failure modes & diagnostic workflow
├── assets/ Photos, diagrams
└── resources/
└── references.md Primary sources & further reading
| Component | Spec / Notes |
|---|---|
| Flight Controllers | Pixhawk 2.4.8 (open-source, STM32F4), Cube Orange (redundant IMUs, STM32H7) |
| Firmware | ArduPilot (ArduCopter) |
| GCS | Mission Planner |
| Frame | Quadcopter (X configuration), 4x BLDC motors + ESCs |
| Sensors | Accelerometer, Gyroscope, Barometer, Magnetometer, GPS+Compass module |
| Power | LiPo battery → Power Module (voltage/current sensing) → PDB → ESCs |
| RC Link | FlySky-class transmitter/receiver, PPM/SBUS to FC |
| Telemetry | Radio telemetry pair (915/433 MHz) for real-time GCS link |
Communication interfaces used on the FC: UART, I2C, SPI, CAN, PWM, USB — see docs/02-flight-controllers.md for what each one physically carries.
- Sensor fusion — combining noisy/drifting accelerometer, gyro, magnetometer, barometer, and GPS data into a single reliable attitude/position estimate (EKF-based in ArduPilot)
- Real-time embedded control loops — 400 Hz+ stabilization loop with PID-based correction driving PWM to ESCs
- Redundancy & fault tolerance — Cube Orange's multi-IMU architecture and how sensor-failure detection works
- Ground-to-air telemetry protocol (MAVLink) — how GCS ↔ FC state sync happens over a lossy RF link
- Safety-critical firmware design — pre-arm checks, failsafe cascades (RC loss, GPS loss, battery failsafe, geofence)
- Systems integration — six independently-designed subsystems (power, sensing, actuation, RF command, telemetry, GCS software) that must agree on timing, voltage levels, and protocol before the vehicle is flight-safe
| I want to... | Go to |
|---|---|
| Understand how lift/attitude control actually works | docs/01-quadcopter-architecture.md |
| Compare Pixhawk 2.4.8 vs Cube Orange | docs/02-flight-controllers.md |
| See the firmware flash → calibrate → arm workflow | docs/03-ardupilot-configuration.md |
| Look up what a specific ArduPilot parameter does | docs/04-parameter-reference.md |
| See the build log and pre-flight checklist | docs/05-assembly-and-preflight.md |
| Diagnose a specific failure (won't arm, toilet-bowling, etc.) | docs/06-troubleshooting-guide.md |
This work was carried out during my Summer Internship at the Department of Electrical Engineering, IIT Jammu, under the supervision of Dr. Sudhakar Modem. All conceptual and hardware groundwork referenced here builds on the official ArduPilot, CubePilot, and MAVLink documentation - see resources/references.md.
