←
Full Stack Flight27 posts
Full Stack Flight avatar

Full Stack Flight

@FullStackFlight

Making drone engineering understandable. Open-source flight tech, build guides, and new hardware. Join the community and build with us!

◷ Joined October 2026▧ 25 Photos and videos
Full Stack Flight avatar
Full Stack Flight@FullStackFlight·Nov 13

Want to understand how a stick movement changes the motor outputs? Centauri's @micropython source lets you follow the sensor readings, control calculations, and motor commands. You can study the same code that flies the aircraft in our videos! 4/5

Post attachment
Full Stack Flight avatar
Full Stack Flight@FullStackFlight·Nov 13

The pilot sends a command. The motion sensor measures what the drone is doing. The flight controller adjusts the motor outputs to correct the difference. Centauri repeats that control loop 250 times per second. Those little corrections keep it flying! 3/5

Post attachment
Full Stack Flight avatar
Full Stack Flight@FullStackFlight·Nov 13

The airframe is 3D-printed. Inside are the Pico, a motion sensor, a radio, and the electronics that control four brushless motors. Building it brings several kinds of engineering onto one workbench: mechanical design, wiring, electronics, and software. 2/5

Post attachment
Full Stack Flight avatar
Full Stack Flight@FullStackFlight·Nov 13

What keeps a quadcopter balanced while its four motors pull it through the air? On Centauri, a @Raspberry_Pi Pico runs flight-controller code written in @micropython. Meet the drone, part two of our introduction to the Centauri ecosystem! 🧵 1/5

0:15
Full Stack Flight avatar
Full Stack Flight@FullStackFlight·Nov 12

Why did we write all of Centauri in Python/MicroPython? So someone with basic Python can follow how pilot inputs become motor commands, then try changes themselves! We prioritized readable code and hands-on learning over squeezing out every bit of performance.

Post attachment
Full Stack Flight avatar
Full Stack Flight@FullStackFlight·Nov 9

With the ground plane attached: 178 METERS! More than 3x the range in this test, just from adding those wire arms. This suggests an insufficient ground plane was limiting my antenna setup. Excited to try it on the drone next!

Post attachment
Full Stack Flight avatar
Full Stack Flight@FullStackFlight·Nov 9

First, without the ground plane: packets stopped arriving at about 58 meters. Link made this easy to check on foot. No need to fly the drone just to find out where reception drops off! Then back to the transmitter to add the wire...

Post attachment
Full Stack Flight avatar
Full Stack Flight@FullStackFlight·Nov 9

For the test, I added the ground plane to the TRANSMITTER antenna, not Link. The transmitter stayed in place while I walked away with Link, my handheld radio monitor, watching for incoming packets. One walk without the wire, then one with it.

Post attachment
Full Stack Flight avatar
Full Stack Flight@FullStackFlight·Nov 9

I made a simple ground plane: two wire arms, each extending 17.3cm from the center. That's a quarter wavelength at 433.8MHz. It contacts the antenna connector's ground. Shown here on Link to illustrate how it attaches, not how I tested it. 2/5

Post attachment
Full Stack Flight avatar
Full Stack Flight@FullStackFlight·Nov 9

About $0.02 of wire tripled the range in today's Centauri radio test! I'd been puzzled by the limited range of my homebuilt drone's radio link. Turns out the antenna's ground plane deserved a closer look. Here's what I tried!

Post attachment
Full Stack Flight avatar
Full Stack Flight@FullStackFlight·Nov 5

34 minutes and 50 seconds of flight time yesterday. Putting Centauri v2 through its paces. 💪

0:20