All Posts (11086)

Sort by
3D Robotics
Judging from this thread, Paparazzi is a complete nightmare to implement, despite the new availability of pre-built boards. The insistence that it has to run under Linux doesn't help. I have huge respect for the technical accomplishments of the Paparazzi team, but it sounds like some all-important hand-holding for regular folks has been lost along the way. [UPDATE: Speaking of Paparazzi, this Hong Kong company has fabbed thousands of Paparazzi PCBs (is the market for difficult-to-use open source autopilots really that big???) and has some very good deals on Tiny 2.11s ($185 for the kit including 4Hz GPS)]
Read more…
3D Robotics
Dave Perry from UNAV writes in with some news: "UNAV has been working with the US Commerce Dept. for the past six months to re-classify our PICOPILOT-RTL (Return To Launch) product. We claimed that since the -RTL could not be programmed with user waypoints, it should be classified separately. Friday, we finally received the classification; 7A994. This classification requires the -RTL to have an export license only for AT ( terrorism sponsoring ) countries. This ruling is significant because it means the US government recognizes the difference between "programmable" and "return to launch" autopilots.Now we can export the PICOPILOT-RTL to almost any country without an export license. Of course, any autopilot that can be programmed with user waypoints remains classified as 9A012, requiring an export license to all countries except CANADA. I might point out that the regulations make no distinction between hobby and commercial autopilots, so the export of amateur (DIY) autopilots must comply with the US export regulations and have an export license. " [Chris here: I think it's going to be interesting to see how the regulators consider open source hardware, autopilot kits and autopilot components. I note that the Autopilot/IMU "development board" that SparkFun sells, which is fully programmable and much more capable than the RTL, is not export controlled. Neither is the impressive pre-made Paparazzi autopilot. An oversight? Or are such "development boards" not considered autopilots? And since each of these are just the combination of an IMU, a embedded processor and GPS, all of which aren't export controlled, what if you just buy the three bits and put them together yourself, downloading open source code from a site like ours to make it all work together? Obviously there's little the regulators can do about that, and the point of sites like DIY Drones is to make that very process of doing-it-yourself as simple as possible. In a world where many of the components of an autopilot, from accelerometers to GPS, can be found in any cell phone, is it really possible to regulate the sale of autopilots like weapons anymore? No one's come after us for selling an autopilot PCB (nor should they). When we sell it with the components pre-soldered, like the SparkFun or Paparazzi boards, can we just call it a "development board" and similarly escape regulation? Does it matter if the software is pre-loaded or not? Does the fact that none of us--the creators of the Sparkfun, Paparazzi or ArduPilot autopilots--are companies (we're just amateurs, mostly working in the open source realm) make a difference? Even if it did, what about the companies that are actually making and selling the boards for us, such as SparkFun or BatchPCB? Are they responsible for knowing what these boards do and all the regulations concerned? Lots of question....]
Read more…
3D Robotics
The AUVSI organizers have offered to get us a flying field in San Diego for an amateur UAV fly-in on Sunday, June 8th, the day before their big annual UAV conference and expo starts. Before I take them up on this, I want to gauge interest: are you in the San Diego area or going there for AUVSI and might want to fly on that Sunday? (BTW, I'm giving a keynote at AUVSI, talking about the rise of open source and amatuer UAV development)
Read more…

NEW UAV FOR PENTAGON

This looks interesting! As seen in the Polular Mechanics South African versionLooks promising in regard to my thoughts on the "Drug issue"Does anybody have any info on specs and such like.
Read more…
3D Robotics

A DIY Drones Milestone: 1,000 members!

Today we hit another nice milestone in the growth of DIY Drones: 1,000 people have signed up to participate. In the ten months this site has been running, it has grown to an average of 1,000 unique visitors and 5,000 page views a day. Over that period, we've had a total of about 200,000 unique visitors and nearly three quarters of million page views. We add new members at a rate of about 50 a week (after we clear out the occasional russian mail-order-brides!). All told, I believe we are now the largest amateur UAV community on the web, which is not bad for less than a year! Going forward, I'd like to bring in more of you to help steer this site and expand it. If you'd like to be a co-moderator here, which is to say have administrator privileges, just PM me (little envelope icon) and we can talk about what that entails. If I can get one or two solid contributors to manage this site with me (we all have day jobs, of course, so this is just to keep the volume up while any one of us is swamped with other things), I think we'll be able to grow it even faster yet. I'm happy to share the Google AdSense revenues with my co-editors--it won't make you rich, but it's a nice little payback for what is otherwise an all-too-expensive hobby ;-)
Read more…
3D Robotics
After our presentations last week at Where 2.0, our Pict'Earth friends stuck around for the weekend to do another mapping mission over the Googleplex (this now seems to be a rite of passage in our community--my original mission is here). As usual, they used an EasyStar and a Nokia N95 cameraphone, and their own proprietary image stitching software. The results are excellent, and you can see a medium-res version of the whole campus superimposed on the satellite imagery in OpenAerialMap here. Screenshot (click to enlarge):

Read more…
3D Robotics
The Government Accounting Office has released a new report on the issue of introducing UAVs into the national airspace for routine operations. Nothing very new or illuminating, but I'm glad that they noted that the lack of a clear regulatory path is hindering commercial development. Words that do not appear anywhere in the report: "amateur", "non-commercial", "recreational" and "open source". Although the report makes many good points, it also gets a bit silly at times, such as noting that although airlines have locked security doors protecting the cockpit, there are no such standard security measure protecting the doors to the trailers of UAV ground station. Although that may be true, most of the big UAVs are operated from inside secure facilities, and the ones that aren't tend to be pretty small. Certainly nothing like a jet full of fuel. News coverage here.
Read more…
3D Robotics

HOW-TO: Make your own PCB

Confused by all this talk about Eagle PCB files, schematics, "fabs" and all that? Until about three months ago, so was I. But with a lot of late nights and hand-holding from Jordi, I finally figured it out and now find the fast-growing DIY hardware world mind-blowingly cool. Now you can zip up the learning curve a lot faster than I did by checking out this excellent new PCB fabbing tutorial by SparkFun.
Read more…
3D Robotics
From our friends at Pict'Earth, a neat hack to keep your directional antenna pointed the right way and monitor your wireless video while your plane is in the air. I was going to say it was "cool" but I realized that my wife would probably disagree (indeed, she'd have serious doubts about her life's choices if she ever caught me wearing it!) But it certainly does seem useful, especially for those secluded flying places away from the public eye ;-)
Read more…
3D Robotics

Dave from UNAV sent over the above GPS simulation results from a search and rescue pattern test for the upcoming Australian Outback Challenge contest. The course is 5x2 miles and Dave used the new PicoPilot groundstation software to plot the waypoints and monitor the simulation results.

It looks like there may be as many as 10 teams using PicoPilots in the Outback Challenge this year. Plus many using other commercial and DIY autopilots, no doubt. This year, the contest's second, promises to be far more competitive than last year. Anybody going who wants to file a report for DIYDrones?

Read more…

UAV #1

This was my first UAV.

It was the simplest, cheapest UAV possible: a magnet. It couldn't fly very high, it couldn't follow waypoints, it couldn't carry much of a payload, it was even more unstable than a helicopter, but it could fly as long as PG&E didn't have a rolling blackout.The guidance system was as simple as can be. Just pulse the throttle when too low or high. Scale the duty cycle based on the time between boundary conditions for lead compensation. A side magnet could move it sideways.Later on, discovered wings. Wings had huge advantages over a magnet.But, after the spare parts consumed $500 of rent doing nothing, decided there would be no other use for them & it was time to rebuild the magnet UAV. The hall effect sensor no longer works. It'll take some time to track one of those down.
Read more…

The Current Project

So my current project is to scratch build a small QuadCopter. The physical structure is allready built in a preliminary form, and it will do just fine for preliminary testing. Currently, its made of square wood dowel and Speed 400 size motors with an old NiMH pack. Its too heavy to hover with the battery, but I can still get it all working with low altitude testing. When I've got the software stable, then Ill invest in some proper hardware and do it right.The software is the real challenge. I'm going with the Propeller chip by Parallax for the core, so I should have more then enough power (the multi-core architecture will be great I think). I'm going to be muxing in software, so that will pretty much eat one of my 8 cores. Then I'm thinking of having two main components of the software architecture. 1 core will act as the master for the stabilization subcompoennt. 1 core will act as the master for the control subcomponent. Each of these will probably manage one or two others to provide enough horsepower to get their various tasks done. I dont know assembly, and while I intend to learn, I'm going to try to write this all in Spin. So as it goes now, here is the distribution of the propeller's 8 cores:1: Muxing1: Sensor Input and Scaling/Data Manipulation1: Stabalization1: Control________4 Total so farThe muxing core will simply manage what is providing output to the ESCs. I suppose it will just have a short loop which it will constantly be running. The sensor cog will constantly update the global variables with new values and do all the necessary math and scaling to get the correct values. I may leave a cog open so I can spawn it to run PID loops when necessary (just so I dont need to eat up one of them that is already in use). I think that I will have a cog devoted entirely to keeping the vehicle stable and hovering. Then, to move, I will just add an offset from the control cog to the target angle that the stabilization cog will be working toward. The control cog will do the actual navigation math.Ill update as it goes along,Borge
Read more…
3D Robotics

The decision to port the Basic Stamp autopilot to Arduino turned out to be an unexpected opportunity to make something really cool. I've taken Jordi's open source RC multiplexer/failsafe board, and mashed it up with an Arduino clone to create "ArduPilot", perhaps the cheapest autopilot in the world. ($110! That's one-third the price of Paparazzi)

Here's what it is:

A custom PCB with an embedded processor (ATMega168) combined with circuitry to switch between RC control and autopilot control (that's the multiplexer/failsafe, otherwise known as a "MUX"). This controls navigation (following GPS waypoints) and altitude by controlling the rudder and throttle. These components are all open source. This autopilot is fully programmable and can have any number of GPS waypoints (including altitude) and trigger camera or other sensors

As with the Basic Stamp autopilot, to make a fully autonomous aircraft you need to combine this navigation autopillot with a stabilization system, for which we turn to our old friend, the FMA Co-Pilot (off-the-shelf infrared sensors and control board to keep the plane flying level), which controls the ailerons and elevator.

By using Jordi's MUX, which allows us to switch from autopilot to manual RC control in hardware, we gain several advantages over the Basic Stamp:

1) Because the switching isn't handled by the processors, we don’t need to drive servos in real time, which means we don't need stand-alone servo driver chips (thus a simpler board)

2) We also don't need “mirroring” subroutines to pass through servo commands in RC mode (simpler code)

3) Don’t need power regulator, since we’re using regulated output from the RC receiver (simpler board)

4) The built-in MUX failsafe is cheaper and simpler than using a stand-alone one.

I've taken a quick pass at the schematic and PCB (Eagle 5.0 format) for ArduPilot, although this will evolve as we go through the hardware testing cycle: Schematic, PCB board. You can buy the board here. Arduino code coming soon in alpha now.

All together, this can be the basis of a sub-$500 UAV:

Autopilot:

--ArduPilot PCB: $10

--Boarduino kit + FTDI cable: $35 (subtract $17.50 if you already have a FTDI cable)

--PicoSwitch: $20 (we'll probably build this in the board in the next rev)[UPDATE: Jordi's now incorporated that into the board above. It's a TinyAVR chip ("IC3", $2.75) and its associated programming interface jumpers ("ISP")]

--EM-406 GPS module: $60

--Multiplexer chip : $1

--8 Samtec TSW-108-25-G-T-RA right angle servo connectors (available as a free sample): $0

(That's a $110 autopilot, thanks to the open source hardware. By comparison, the Basic Stamp version of this, with processor, development board and failsafe board, would run you $300, and it's not as powerful)

Stabilization:

--FMA Co-Pilot: $70

Plane and RC equipment:

--Hobbico SuperStar (includes motor, battery and ESC): $109

--6-Channel radio system (with proportional control for channel 6, to calibrate FMA system): $109

--Three servos: $45

TOTAL: $440
Read more…
3D Robotics

For very small UAVs, especially those used indoors, an interesting way to navigate is using a technique called "optical flow". Basically, it's the way flies see: they detect motion rather than resolve images. As you move, the objects closest to you appear to move the fastest, which for a camera chip means pixels shifting position faster.

The video above is from a Swiss team that have used optical flow to steer indoor blimps and microlight aircraft (video here). They've got pretty fancy equipment and lots of money--but is there a way to do the same on the cheap? Yes. It turns out that the sensor on an optical mouse (you probably have a few laying around) can do the job. Here are instructions on how to take the chip from an old mouse and connect it to a Basic Stamp (an Arduino would work even better) and create a low-budget optical flow sensor. Taking the dx, dy information from that and using it to drive the airplane's servos or actuators to move in the opposite direction from the highest optical flow should be a pretty easy matter. The only tricky thing is integrating the mouse chip and processor into a package no larger and heavier than the RC receiver that this optical autopilot replaces. The schematic on the mouse chip to Basic Stamp circuit is below:

Read more…
Developer

Open Source MUX Antifail System by me

Has been pass a long time since my last post, and well, I have been very busy. Anyway I have a good gift for all the community and I hope you will enjoy it, is my final version of my MUX antifail system. Chris Anderson already talk about this, you can see it here.This device let you switch between automode or manual mode just using 1 channel of your remote control. My Antifail system is a little bit complex, the idea was to make it very flexible and you can adapt it to any homemade solution.. For example you can choose between a pull down or pull up resistor, and if you make contact with any servo activated device in the correct pins will let you switch between modes or if you system only have a TTL pin to send the signal you can use it with no problems… in other cases if you have weird pico-switch that is just a transistor that makes ground, anyway, you can use it, (maybe I confuse everybody now), this is just an introduction, but I will explain it in detail after.And off course if open source and almost free, (just 7 dlls for board), a commercial one will cost you about $50 dlls.Let me explain about the labels of the PCB:SA1,2,3,4= Servos Port A (Input): Input of servos in port A.SB1,2,3,4= Servos Port B (Input): Input of servos in port B.S1,2,3,4= Servos Outputs.PWR_SEL= Power Select Jumper: Let you choose from where you want to obtain the power to move the output servos, if you place the jumper in the pins 1 and 2 you will take the power from the receiver connected to input port A, and if you put the jumper in pins 2 and 3 you will obtain the power from the receiver connected to input Port B.IC_PWR= IC power select: This jumper let you choose from where you want to take the power to supply the multiplexor chip, if you place the jumper in pins 1 and 2 (SRV), you will obtain the power from the receiver selected in PWR_SEL, but in case that the receiver exceeds 5.5 volts, you will need to place the jumper in the pins 2 and 3 (VIN), and connect a 5 volts battery in the VIN jumper.VIN= Voltage In: Here is where you suppose to connect the 5 volts battery. Careful with the polarity =).RES_SEL= Resistance Selector : Here you can choose between a pulldown or pullup resistor, if you choose pulldown resistor, the autopilot will be disable by the default, until you send a 5 Volts signal. If you select the pullup resistor, the autopilot will be activated by default, until you ground it.PICO= PICO Switch, is where you suppose to connect a switch activated by a servo signal (connected to channel 5 of your remote control). The pin 1 is ground, the pin 2 is the mode selector (manual mode or auto mode) and the pin 3 is 5Volts. If you selected the pulldown resistor mode you will need to make contact between the pin 2 and 3 to activate or deactivate the autopilot,. In case that you selected the pullup resistor mode, you will need to ground the pin2 to activated or deactivate the autopilot, you can use any ground you want, but I already put you a ground pin, and is the pin1 =).In case that you have system that will send a TTL signal, like a microcontroller or something, you should connect the output pin of your MCU and connect it to the “PICO pin 2” (the middle one), and connect the ground of the MCU to the MUX Ground, in this case the ground pin (PICO pin 1).Just to rectify if the pin 2 of the PICO jumper is set to LOW or ground, the input port A will be redirected to the output port (you can connect here your receiver or you autopilot). If the pin is set to HIGH or 5 volts, the input ports B will be redirected to the output ports, instead the input port A. This will let you switch between to controllers (autopilot and the remote control receiver).LED1= Tells you when autopilot is activated or vise versa..LED2= Tells you when the system is powered..

Well I hope is enough… If I made a grammatical mistake (like always) just tell me, hehe.To order a PCB from PCBbatch.com click here.

About the Pico Switch, you can buy it from here:http://www.dimensionengineering.com/PicoSwitch.htmOr you can make you own, the switch is from radioshack:
Use it by your own risk!!, if you plane crash i don't know anything, i don't even exist for you, but if you plane is a successful, all the credit is mine off course =P
Read more…