About

Welcome to the largest community for amateur Unmanned Aerial Vehicles! 

This community is the birthplace of ArduPilot, the world's first universal autopilot platform (planes, multicopters of all sorts and ground rovers). Today the Pixhawk autopilot runs a variety of powerful free and open UAV software systems, including:

  • PX4, a pro-quality open source copter, plane, rover and VTOL software stack from the Linux Foundation's Dronecode Project
  • ArduCopter, open source multicopter and heli UAV software
  • ArduPlane, open source software for planes of all types
  • ArduRover, open source software for ground-based vehicles

Microsurvey FieldGenius at 30% !


Microsurvey FieldGenius both for Android and Windows is now at 30% OFF only at Aeromao. FieldGenius is a mature, professional and full featured data collection software that also happens to be easy to use.

 MicroSurvey FieldGenius has become one of the most powerful and productive data collection software within the surveying industry. It can be partnered with many GPS receivers on a number of data collectors. 

12643937258?profile=RESIZE_400x FieldGenius is the ideal software/app to go with Emlid Reach GNSS receivers for the advanced user!

 Code-free linework, smart points, and live graphics make FieldGenius the choice of organizations that value productivity.

  • Code-free linework
  • Best-in-class user interface
  • Works on more displays/devices
  • Productivity tasks
  • Calculation tools
  • Part of the perfect…
Read more…

TFmini-S can be used with PixHawk for the purpose of obstacle avoidance.

  1. TFmini-SSettings:

Note: Frame rate should be set to 250Hz, see the details in chapter 7.4 “frame rate” and changing the communication interface.

The default communication of TFmini-S is TTL, IIC and TTL uses the same cable, so please set TFmini-S to IIC communication first, see detail commands in product manual.

We take two TFmini-S as an example in this passage and set the address 0x10 and 0x11 separately.

  1. PixHawk Connection:

See the connection details in PixHawk manual and TFmini-S manual, we take example for connecting

PixHawk flight controller:

12629947677?profile=RESIZE_710x

Figure 1: Schematic Diagram of…

Read more…

Latest Activity

Eric Matyas replied to Eric Matyas's discussion Free Music / SFX Resource for Drone Videos - Over 1800 Tracks
""GRUMPY SLIMEBALL FROM OUTER SPACE" is this week's brand new free-to-use-with-attribution music track.

You can download it in Mp3 format from my new Sci-Fi 13 page:
https://soundimage.org/sci-fi-13/

As always, it's 100% free to use with…"
yesterday
Miami Car Rental updated their profile
yesterday
williamwordsworth replied to Gareth Rens's discussion UAV for photogrammetry / surveys
"For achieving accurate results in UAV photogrammetry, incorporating Ground Control Points (GCPs) is essential. GCPs are markers with known coordinates on the ground that significantly enhance the accuracy of aerial surveys. Placing GCPs…"
Monday
clay_global updated their profile
Monday
williamwordsworth replied to Sandy Sound's discussion PIXHAWK FW3.5.2 + Canon S100 CHDK Mapping Troubleshooting UPDATED
"It sounds like you're encountering issues with your 3DR EAI S100 Lua script and CHDK settings after a long break from mapping. Make sure all camera settings in the CHDK menus align with your Lua script, especially critical ones like RAW capture and…"
Monday
Joel Meijering posted a discussion
Hello fellow drone enthausiasts,I build and work with drones, specifically for photogrammetry applications.What has got me scratching my head for the longest time, is that is seems that all solutions I can find on the market have the drone (either…
Monday
Mark Wilsonn updated their profile
Monday
daria panratova replied to Tetracells Inc.'s discussion World's Largest 3D Printer
"If you’re in e-commerce business and looking for help with development, you might be interested in reading this https://www.vtlabs.org/agile-ecommerce-development/"
Monday
Steve replied to Brian Heckle's discussion Building with arduino along with possibly a pi, and communicating with sbus.
"Looks like it could become an interesting project"
Monday
Steve posted a discussion
Hello,I have been always active in fixed wing.One of my friends asked me to look in, the chances a quadcopter can survive a defect engine, or motor controller ?The Frame should carry a 5kg sensor package, so, we are talking about a pretty heavy…
Monday
Rittu Ronald, williamwordsworth, Moamen Mohamed and 2 more joined diydrones
Sunday
Santiago Perez liked Santiago Perez's profile
Saturday
Santiago Perez updated their profile
Saturday
Santiago Perez updated their profile photo
Saturday
Santiago Perez and DS Hesh are now friends
Saturday
The_Spy and Ashwin joined diydrones
Friday
Reed Moore, Azwir Azis, Valentin Spirov and 2 more joined diydrones
Jun 19
Eric Matyas replied to Eric Matyas's discussion Free Music / SFX Resource for Drone Videos - Over 1800 Tracks
"Hey Everyone,

Here' a brand new track on my brand new Sci-Fi 13 page:

"SEWER CREEPERS DOWN THE DRAIN"
https://soundimage.org/sci-fi-13/

Fun stuff!

Need some custom music created? Give me a shout! My contact information is on my site. :-)

Keep…"
Jun 18
nick rymer posted a discussion
We are trying to get a Hexacopter (Tarot X6 frame) with a Pixhawk Cube Orange+, Arducopter v4.5.1, Castle Creations DMR 30/40 ESCs and Tarot 5008 KV:340 motors, 18in CF props, in flight condition. The only thing that is non-standard, is we have a 2…
Jun 18
Thomas Marsh is now a member of diydrones
Jun 16
More…

Site Rules

"Because $10,000 $5,000 $1,000 is too much to pay for an autopilot, especially one that doesn't do exactly what you want."

An Unmanned Aerial Vehicle (UAV, colloquially known as a "drone") is basically an aerial robot. As we define it, it is capable of both remotely controlled flight (like a regular RC aircraft) and fully-autonomous flight, controlled by sensors, GPS, and onboard computers performing the functions of an autopilot. Our UAVs include airplanes, helicopters, quadcopters and blimps. Most of them are under five pounds, and some of them (especially the blimps) can be used indoors.

We are focused on non-commercial ("recreational") projects by amateurs, although pros are always welcome too. Reasons to make your own UAV range from a fun technical challenge, student contests, aerial photography and mapping (what we call "GeoCrawling"), and scientific sensing. We are primarily interested in civilian, not military, UAV uses here.

If you're new to all this, start here.

DIY Drones is a community based on the Ning social networking platform, and anybody who registers (it's free and easy) can post their own blog entries like this one on the front page, along with starting discussions in the sidebar at left or uploading videos below that. Your registration gives you the ability to do a lot on the site--so feel free to post anything you think will be of interest to this community!

There are other amateur sites out there, from the discussion forums of RC Groups to individual blogs, but DIY Drones is explicitly built as a social network, which means that the community is as important as the content. We're also focused on the most accessible end of the amateur UAV world, with the aim of potentially including high school students.

This means we emphasize amateur UAV projects that are:

  1. Simple: The aim of this project is to create new amateur UAV platforms, including those that could be used for a FIRST-like contest appropriate for students. While we're at it, we'll make amateur UAV development easier for everyone.
  2. Cheap: The target cost of all of our platforms is less than $1,000. You can buy a very good autopilot system for $10,000, but that's not our approach. Cheaper is better, especially with students and schools.
  3. Safe: We follow the current interpretation of the FAA guidelines on small UAVs. Recreational use (non-commercial), under 400 ft altitude, line of sight, "pilot in the loop" and onboard safety systems that always allow for manual control in the case of malfunction. We're building experimental platforms that demonstrate autonomy and the capacity to do real useful UAV work, but we test them in controlled settings. If you want to fly miles out of sight or map cities, we're going to assume you've got the proper FAA clearance or we don't want to know about it.
  4. Participatory: Share and others will share with you. That means that whenever possible, we open source our code and post it online. Everything on this site is published under a Creative Commons "attribution" license, which means that anyone can use or repost it, as long as they give credit to the original author.
  5. Civil: This is a community site of peers helping each other. Bad behavior, from rudeness to foul language, will be deleted. Generosity and kindness is often rewarded with reciprocal behavior and help.

Here are the full set of Site Policies:
 
  1. Civility is paramount. Treat others with respect, kindness and generosity. Some of our most expert members are people who were once total n00bz but were helped and encouraged by others, and are now repaying the favor with the next generation. Remember the Golden Rule. Don't be a jerk to anyone, be they other members, moderators or the owners. This is not a public park, and you have no constitutionally-mandated right to free speech. If you're creating a hostile or unpleasant environment, you'll be warned, then if it continues you'll be suspended.
  2. No discussion of politics or religion. This is not the place to discuss your views on the wisdom of military use of UAVs, any nation's foreign policy, your feelings about war, or anything else that is inclined to turn into a political debate. It is our experience that the rules for good dinner party conversation--no discussion of politics and religion--apply to online communities, too. DIY Drones aims to bring people together, and we find that discussions of politics and religion tend to polarize and drive people apart. There are plenty of other places to discuss those topics online, just not here.
  3. Ask questions in the discussion forum; inform others in blog posts. Submitted blog posts that are just questions and should have been posted in the discussion forum will not be approved. The moderators may or may not message you with the text so you can repost in the right area. To avoid losing your post, put it in the right place from the start.
  4. Blog posts are for informative topics of broad interest to the community. They must start with a picture or video, so the image appears on the front page on the site and gives a sense of the topic as well as inviting people to click in for more. Videos should be embedded (paste the embed code in the HTML tab, not the Rich Text tab). The post should also include links where appropriate. Don't make people do a Google search for what you're talking about if you can provide a link. 
  5. The Discussion Forum is for questions and tech support. We prefer to do all tech support in public, so that others can follow along. If you have a problem, please describe your particular system setup completely, ideally with a photograph, and pick the right forum tags so that others can find the thread later.
  6. No discussion of military or weaponized applications of UAVs. This site is just about amateur and civilian use.
  7. No discussion of illegal or harmful use of UAVs will be tolerated. Responsible use of UAVs is at the core of our mission. That means conforming with all laws in the United States, where this site is based, and insisting that our members elsewhere follow the laws of their own countries. In addition, we feel that part of our responsibility it to help the relevant authorities understand what's possible with amateur UAVs, so they can make better-informed policies and laws. So we have encouraged all relevant regulators, defense agencies and law enforcement agencies to become members here and even participate to help them do that, and many have. In addition, if we see any discussion of UAV use that we feel is potentially illegal or intended to do harm, we will bring it to the attention to the relevant authorities, and will comply with any legal request they make for information about users (although we don't know much that isn't public; see the next item).
  8. Promote safe flying. Moderators may delete postings that they decide are unsafe or promote unsafe activity. This is a judgement call, since it is also healthy to have public discussion about why certain activities are unsafe, but the decision as to whether to leave a post or edit/delete it is at the moderators' discretion. 
  9. Your privacy is protected, up to a point: This is a social network, so everything you write and post here is public, with certain exceptions: 1) Your private messages are private. Administrators are unable to see them, nor can anyone else other than the recipient. Members must not make private messages public without the explicit permission of everyone involved. 2) Your IP address is private. We are hosted on Ning, which controls the server logs. DIY Drones administrators can only see your username and email address; they cannot see your password and do not have access to your account.
  10. Do not publish personal emails or PMs without permission. This is a violation of expected confidentiality (that's why they're called "personal messages") and is grounds for banning.
  11. Do not type in ALL CAPS. It's considered SHOUTING. Posts in all caps will be deleted by the moderators.
  12. Absolutely no personal attacks. It's fine to disagree, but never okay to criticize another member personally.
  13. Share. Although we are not limited to open source projects, the ones that tend to get the most participation tend to be open source. Don't wait until your code or design is "finished"--post it as it is, and you may find that others will help you finish it faster. The best way to contribute is with your creativity--we love data, code, aircraft designs, photos of UAV projects, videos of flights and build logs. Post early and often!
  14. Keep comments open: Authors of blog posts and discussion threads technically have the option to close their comments or approve them before they appear, but we ask members not to do that. We want to encourage a free flow of conversation and blocking or delaying comments only interferes with that. The Moderators are standing by to ensure the conversation remains on-topic and civil, so please leave your comments open and let them do their job.