I helped with a previous quadrotor build (Instructable here), and after flying it I decided I wanted to make my own. I had an idea to make a miniature one comprising a single printed circuit board that is both its structural frame and its electronics motherboard. The end result was "4pcb", a 138-gram micro quadrotor. I designed it in EAGLE, soldered it, and tested it over the course of a few months. Here's some video of it flying, after a lot of control tuning (see Step 13) and practice:
More flight video in the final Step!
The idea of making a PCB-based quadrotor isn't unique (see links below for other examples), and 4pcb definitely isn't the smallest (see the Picopter Instructable for a really tiny one). But I think it strikes a good balance between size, cost, buildability, and flyability. It's also one of the only PCB quadrotors with integrated brushless motor drivers, so there's no need to wire up external ESCs. And it runs on XBee digital radios, so there's no RC receiver or servo-style wiring.
4pcb Specifications:
Size: 6.50" (165mm) motor center-to-center distance, diagonally
Battery: 3S (11.1V), 370mAh, 20-40C Lithium Polymer
Motors: HXM1400-2000 "hexTronik 5gram Brushless Outrunner 2000kv"
ESCs: Toshiba TB6588FG "3-Phase Full-Wave PWM Driver for Sensorless DC Motors"
Props: 4x2.5 (2), 4x2.5R (2)
Controller: Arduino Pro Mini 328 - 5V/16MHz
IMU: Pololu MinIMU-9
Radio: XBee Series 1
Total Weight: 138g
Additional Payload: <30g
Flight Time @138g: 8min
4pcb is a "low level" quadrotor build, by which I mean that there are very few black box components. The frame, motor control, flight control, radio interface, and ground station UI are all developed from component or sub-module level. Depending on your level of experience and interest, you may want to take a different approach where you buy commercial modules for some parts and DIY others. (I included links to some kits and modules below.) This Instructable includes all the files and information you would need to build one completely from scratch.
There are a few small changes I would make if I did a second version of the board, but overall, I think it could make a good standalone project or, even better, a great starting point for your own modifications! (6pcb hexrotor, anyone?) Here are some resources that you might find useful, whether you are building this particular quadrotor or a different multirotor:
Other Quadrotor Instructables:
quadrotor - Custom frame with Arduino-based controller.
RC Quadrotor Helicopter - Off-the-shelf frame with custom controller.
Picopter - A very tiny custom PCB quadrotor.
Multirotor Frame Kits:
HobbyKing
ArduCopter
Multirotor Controller Kits:
HobbyKing (based on KK Multicontroller)
MultiWii
ArduPilot
OpenPilot CopterControl
Complete Solutions:
Parrot AR.Drone - Very stable iPhone-controlled quad.
General Multirotor Resources:
RCGroups Miniature Quadrotor Thread
DIY Drones Quadcopter Forum
OpenPilot Multirotor Forum
PID Tuning for Multirotor (OpenPilot TV)
Mini Quads (5" props)
TinyCopter (custom build)
BabyCopter (custom build)
Turnigy Integrated PCB Micro-Quad (KIT) (commercial)
Blade mQX (commercial)
Micro Quads (4" props):
4pcb (custom build)
Kawaiicopter (custom build)
Nano Quads (3" props):
Nanocopter (custom build)
Nano quadcopter wii (custom build)
Pico Quads (2" props):
Walkera QR Ladybird (commercial)
CrazyCopter (custom build)
Picopter (custom build)
Chibicopter (custom build)
NC-ONE (custom build)
My Pages:
4pcb and other Flying Things
The Balance Filter - Merging accelerometer and gyro signals.
Remove these ads by
Signing UpStep 1: The Setup: Parts, Tools, Software, and Files
4pcb_ARD (folder) - Arduino project (Arduino 0022, .pde).
4pcb_EAG (folder) - EAGLE board files and libraries (EAGLE 6.0.0 Light Edition).
4pcb_EXE (folder) - Ground station executable (requires .NET Framework 2.0 or later).
4pcb_GRB (folder) - Gerber files for PCB printing.
4pcb_VB (folder) - Ground station source (Visual Basic Express 2008 or later).
4pcb_BOM.xlsx - Bill of material in Excel format.
4pcb_DIR.jpg - Coordinate system of quadrotor and IMU.
4pcb_EXT.pdf - Details of external connections.
4pcb_IMU.jpg - Image showing vibration mounting and wiring of Pololu minIMU-9.
4pcb_SCH.pdf - PDF schematic of the board.
Bill of Materials / Cost:
The Bill of Materials (4pcb_BOM.xlsx) lists all the components required to put together one PCB quadrotor and ground station. The total cost to build the quadrotor is about $240. The ground station consists of a USB game controller, an XBee radio, and and XBee-to-USB adapter. If you don't already have these, they add an aditional $80 or so.
Soldering:
This board requires a good amount of surface-mount soldering, including passives as small as 0603 and four TSOP36 ICs. They can all be hand-soldered (no BGA or leadless).
Additional Tools and Hardware:
- Wire (22AWG and 28AWG stranded would work) and wire cutters/strippers.
- Solder braid for cleaning up bridges.
- FTDI cable for programming the Arduino Pro Mini.
- Hex key set.
- Double-sided foam mounting tape.
Software:
-EAGLE
If you want to modify the printed circuit board, you'll need EAGLE v6.0.0 or later. You can download it here. The free "Light Edition" is sufficient, even though the outline of the board is larger than 100x80mm limit (see Step 2). You will also need EAGLE to reference the board layout when placing components. (e.g. Type "show R32" in the board window command line to figure out where to put resistor R32.) There are no designators on the board itself.
-Arduino
The flight controller is written in the Arduino IDE. You can download the latest version from here. Make sure you set the board type to "Arudino Pro Mini (5V/16MHz) w/ ATmega328".
-Visual Basic Express (Optional)
The ground station is programmed in Visual Basic Express. If you want to modify the ground station software, you can download the free edition, Visual Basic Express 2010 from here.
-.NET Framework
The ground station requires the .NET Framework runtime files. (Unfortunately, this makes it Windows-only.) These files come with Visual Basic 2010, so if you plan on modifying the ground station software, there's no need to download them separately. If you just want to run the ground station executable, you can download the .NET Framework runtime files from here.
-Processing? (Optional)
Although I haven't done so myself, it is possible to port the ground station software over to Processing, which would make it compatible with other operating systems. To read from the USB game controller, there is a third-party library called ProCONTROLL. I did some work with this for a XBee-based robot controller, the details of which are here. This could be a good starting point for making a non-Windows ground station.
4pcb_DOC.zip1 MB























































Visit Our Store »
Go Pro Today »




i am new to this so was wondering if there are any books/literature you would suggest to better how this particular system works as a whole and how each of its parts interact with each other? also, if one wanted the altitude feedback and return to horizontal position, would it be just as easy as rewriting some of the code for the Arduino board or would some extra hardware/electronics such as the gyros be required as well? Thanks!!
I'm working on a similar project with a much larger form factor (Turnigy Talon v1) and we're having massive trouble with vibration on our gyro. I have the picture of your foam mounting but I can't really tell how it's set up. Is the sensor board weighted and set on top of a foam loop, or is the gray foam wrapped around something?
Thanks.
I also have a Talon v1...it's a great frame. But yeah I haven't had much luck with mounting the controller or IMU directly to it. Some kind of isolation is needed.
You provide excellent specs on components.
Bill
The total maximum thrust should be 2-3x greater than total weight, so that you have plenty of extra thrust available for maneuvering and stability. I think on this quad it was much closer to 1x when I was using the 7.4V battery. Switching to 11.1V made it closer to 2x, which improved the stability a lot.
http://www.hobbyking.com/hobbyking/store/__11895__Turnigy_nano_tech_370mah_3S_25_40C_Lipo_Pack.html
so i had abt module laying around so i thought hey why cant we make a bt quadrocopter instead of an r/c?(cheaper u can get two modules for like 15 $ at ebay one for transmitter and another for reciever
most probably ill make this one and maybe make an instructable for u guys
by the way awesome instructable(this) well explained well done!!!
Bluetooth would be cool, but the range isn't as good as the XBee Pro. It would be perfect for indoor use though, and then you don't need an adapter for your computer if it already supports Bluetooth. Or maybe a smartphone-based controller. That would certainly bring the cost down.
You can try KiCad Open Source solution instead of Eagle.
Best regards from Uruguay!
Tabaré
Extremely detailed Instructable +10
I'm not sure about putting the accelerometer and gyro on-board, though, because they wouldn't be isolated from mechanical vibrations.
Have you tried using any Kalman filtering?
If I wanted to merge in more data, such as the magnetometer, or GPS, I might consider using a Kalman filter.
This is more like a Masters Thesis than an Instructable. Need a new website for Incredible Instructibles. I don't think I've ever given 5 stars before.
This is awesome work, well done!
But when u say it doesn't fly itself, what do you mean? It cant be as bad as trying to fly a traditional helicopter can it? Does it at least self stabilise? Keeping itself in the air, but just wander in all directions?
Im also curious about control differences between the early days and now after refinement? When you started off, could it be held in the air by someone with great flying experience, or was it simply uncontrollable by anyone? I would suspect it was unflyable, so how long was it before it was flyable by anyone?
I think these factors are important for anybody making these, like me at some point, to know what piloting skills and technical tweaking, trimming was required, etc. as I am no engineer like you clearly are.
thanks!
For example, my PCB quad can't do this:
http://www.youtube.com/watch?v=zBTW54SPU5g
The AR.Drone uses image processing, ultrasonic sensors, and a much more sophisticated flight control algorithm to self-stabilize in {x, y, z} in addition to {pitch, yaw, roll}. Since I only use inertial sensors, they don't know the difference between standing still and moving at a constant velocity. This is the physical reason why it drifts around with no inputs.
Some of the commercial multirotor controller kits are approaching or surpassing the sophistication of the AR.Drone, by going beyond inertial sensors and incorporating ultrasonic, GPS, barometry, optical flow (or full image processing). The ArduPilot and OpenPilot CopterControl boards can do these things.
On the other extreme is the KK Mulitcontroller (link in the Intro): it has gyros, only, and can't self-level. If you take your fingers off the sticks, the quad holds its current attitude but won't return to horizontal.
In terms of flight experience required, my quad is closer to the KK board, but with self-leveling. Adding down-facing sonar and closed-loop altitude hold to it would help reduce the pilot's workload a lot, I think. I have one sitting in a box that I haven't gotten to use yet. It's also a small quad, which makes it harder to fly I think. Big quads move slower and it's easier to react to what they're doing.
Looking at the flight test videos, #1 and #2 were unflyable by anyone, I think. Just too twitchy. #3 would be flyable with a lot of practice. #4 and #5 are unflyable for other reasons (bad motor, new IMU with bad settings). #6-#9 are all flyable with practice. In its present state, I've handed it off to people with helicopter/quad flight experience and they can handle it right away. I've also handed it off to people with no experience and the results vary. Most people can keep it in the air for a short period of time, but have trouble controlling either the altitude or the yaw. (If it yaws away, it's easy to get disoriented.)
The fact that your design self levels, but drifts, is good enough as far as Im concerned!
Throttle control isnt an issue either, but if I were to make one from your designs I'd definitely use a non-centring joystick/joypad, or have it centred at zero thrust. But thats just me.
Brilliant, thanks!