All Posts (11086)

Sort by
3D Robotics

This isn't exactly a UAV product, but Jay Graves, who runs Hobby Lobby, emailed to say that they've just released a First Person View (FPV) kit, which looks very nice. FPV is a combo of a videocamera in the plane, an onboard wireless video transmitter, a ground receiver and video goggles. The point: you put on the goggles and you can see the perspective from the plane itself, which is the closest thing most of us will get to actually flying a real plane.

Along with sharing some imaging technology with our UAVs, FPVs often use autopilots because they can fly further away than you can see from the ground. When pilots get lost or lose the wireless connection (and thus their view), the autopilots can bring the planes back into range.

The initial kit, which costs $549, has the basics and looks like quite a good deal (Hobby Lobby has a great reputation, and the company that makes the equipment, Intelligent Flight, is one of the best in the business). But if you happen to be independently wealthy, you might want to wait for some forthcoming accessories that will complete the full FPV experience: a pan-tilt camera mount, which can be connected to a gyro in your video goggles so the camera will turn where you're looking; an On Screen Display that integrates telemetry data into the video stream (and has a basic "return home" GPS-only autopilot for very stable aircraft), and a directional antenna that can greatly increase the range.

I wouldn't be surprised if all that together runs over $1,000, so it's a bit out of our range. But if you can afford it, this is the ultimate RC experience.

Read more…
3D Robotics

New PicoPilot groundstation software

UNAV's Dave Perry emailed me with the news that they've just released a new groundstation program for their low-cost PicoPilot line of autopilots.

From the description: "The PICO-GS program performs four basic functions: 1. Provides a graphical view of your waypoints on the map image. 2. Permits "point-n'click" waypoint programming on the map image. 3. Provides realtime GPS tracking and flight data on the map image ( requires a radio modem ) 4. Includes the standard PICOPILOT line item editor." It costs $100 for a CD and a license key for a single installation. They're sending me a review copy, so I'll give you a hands-on report as soon as I get it.

Read more…
3D Robotics

Bay Area UAV Fly-In: POSTPONED

I thought I'd checked everything for our proposed fly-in this coming weekend: airfield availability, weather, technology ready to fly. But I missed the most obvious conflict: it's MOTHER'S DAY! Given that I've been traveling for past week and we have five little kids, you can imagine that it would earn me no points at home to leave my wife with the children again while I go flying with the boys. So I'm afraid I'm going to have to postpone this. I know that some of you are going to be coming up for the Where 2.0 conference (which I'll be speaking at), so if you've still got you heart set on flying I can probably recommend some places to do it. But I won't be able to join you. Huge apologies for being an idiot and catching it so late. We'll reschedule for June or July. Best, Chris
Read more…

Learning to develop an DIY autopilot

http://www.sparkfun.com/commerce/product_info.php?products_id=707"/>

I have ordered my first development kit. This will be a "baby steps" project. I am in the process of learning how to program PIC. Not sure yet what program language is going to be the best. I would like to get as much advice as I can use. Chris Anderson warned me that this development platform is not for beginners, so I will be gaining the necessary experience in order to hopefully build an reliable stable autopilot.Those of you that have been down this road are probably amused at all the mistakes you already spot and foresee in my approach, but at this point ignorance is quite bliss,,,and who knows how much fun I will have pulling the last few strands of hair from it's precarious perch in the quest for autonomous flight?
Read more…
100KM

BasicX auto pilot

This is a journal for a BasicX AP I've been working on for the last month:i received my BasicX processor the first week of April and spent the next week pounding out the code .i then spent the next week simulating and adding a few niceties like way point and setup files.the next two weeks was spent waiting for the gps module and other parts .spent the last week making a proto board and a few changes to the gps parser to work with the gpstoday 5-5-08 first test flight : things went very well and it performed better then expected (wee haa!!)ok a few features of my ap:no distance restrictionscan fly any ware in the worldunlimited WPseasy set up file ie trim,ectuses spherical geometry in the nav routine instead of flat plain approximation5-8-08test fly ; changed "P" to 0.5 with very nice results flight path much straighter between wps5-9-08hardware list1x ettrex 32 cannel 5hz gps modual1x BX-241x DE-SWADJ reg from dimension engineering1x 5v LDO reg3x 0.1 uf caps1x 100 uf cap2x 1k ohm resistors1x parallax servopal1x tact button (reset)staight pin connectors1x small perfboard1x fma FS-8 failsafe reciever and copilot (stabilization)5-16-08changed gps serial comm , pumped up to 5hz update looptest flight went good ,some oscillations in yaw5-17-08changed cg ,changed prop to 10x7 ,cg got rid of yaw problem , flew in 15-20 mph winds , worked better then expected , noticed 35 deg + dog tracking on cross wind leg, no missed wp no "turn arounds"will turn up P slightly untill it oscillats and will try Ziegler-nichols method on PID loop5-18-08 flew for 15min "no hands" burned 750 ma noticed some trubble turning left against wind5-19-08 changed to figure 8 pattern, changed gain to 0.75, little left trim in auto mode, flew for 10min before rain5-21-08 demo flight for snohomish co. search and rescue. went well
Read more…

Finally started work on my UAV

I've had it in my mind for some time now to build a UAV. I liked Chris' builds with the Predator airframes and noted his concerns about the larger of the two Predators not having enough power or control authority. Now that I've managed to get my hands on a Predator, you guys get to suffer through my build log.I stripped the airframe down by removing the stock 380 brushed motor, ESC and associated wiring and weighed the airframe...14.5 oz for the 75in wingspan version. I decided to power it with an E-flite 1020kV Park 480 outrunner. I figure if it has the power to 3D a 30oz plane it'll be plenty to push the Predator from waypoint to waypoint. I've used this motor in a few 3D parkflyers and, thanks to my fondness of 3D flight in general, I like to have power "on tap". :-) Initial thrust testing with the 9x6 Master Airscrew prop is enough to send the Predator into a vertical climb...more appropriately, deliver groceries to the moon. :-)To mount the 480 I cut 1.5 in off the fuse, sanded the fuse nice and square, then epoxied triangle stock to the inside of the fuse (where the stock 380 once resided) to give more surface area on which to install the new firewall. I made the firewall from some ply, marked the mounting hole locations, drilled for blind nuts, cut the shank of the blind nuts down to the right height for the thickness of the ply, then cut recesses in the fuse material and triangle stock to allow the firewall to sit flush against the fuse. A little more epoxy and the firewall was attached to the fuse.After the epoxy cured I sanded the firewall to follow the contour of the fuse (was initially squared off from the scroll saw) bolted the 480 in place, and threw a 9x6 prop on to help determine which landing gear would be best suited for the plane. Great Planes .60 size gear seems to have a nice track width and should be tall enough to clear a 9 to 10 inch prop.The next thing to figure out is the nose gear. Ideally I'd like to have steerable nose gear but with that comes added weight and a loss of interior fuse space.The V-tail will likely get rebuilt so that the control surfaces consume a larger portion of the wing chord. I can see why Chris said the tail surfaces needed to be improved, they seem suited to a racer more than a slow, lumbering aircraft like a Predator. I don't intend to build new tail sections just yet, I want to see how she flies as I have her configured for now.If all goes as planned I should be able to conduct the initial airframe flight tests this coming weekend. Installing electronics in this airframe is a breeze...except for fishing the motor wires through the fuse. For initial airframe testing I'll be using my DX7 or DX6i. I have a JR 8103 that I plan to use when I make the switch to autonomous mode, along with an E-flite ESC and a Thunder Power 3-cell Li-Po.
Read more…

The Horror of Blimps

At the Maker Faire, the story on the intertubes about the HORROR of blimps came up. For those of you who haven't read it, head over here.I decided to make a DIY blimp today. My 1 year old son's recent love of balloons is a pretty good excuse.
Read more…
3D Robotics

Here's our latest, greatest BlimpDuino (Arduino-clone autonomous blimp controller) board: double-sided, silkscreened neatly laid out and otherwise in much better shape. Shown above is the top side (inside the gondola) of the new board (right) compared to the old one (left).

I'll be showing this at Maker Faire tomorrow and Sunday. Below is the bottom side of the old (left) and new (right) boards. Differences include putting all the chips inside the gondola ("top") and just the IR sensors, the on/off and reset switches and the FTDI programming port on the outside ("bottom")

You can buy these boards for $12.50 each here. You'll also need to buy a Boarduino kit ($17.50) for the Ardunino components. Other parts required: --On/off switch --One of these capacitors --And one of these capacitors --4 IR receivers --2 motor driver chips If you want to fab the PCB boards yourself, here are the Eagle files: Schematic and PCB layout. These are probably the last through-hole board design we'll make, since we've pretty much got this board where we want it. After this, we'll be moving to a much smaller surface-mount design using a whole new design with more sensors, LEDs for directional feedback and a more powerful processor. But that will take a while and in the meantime, the current BlimpDuino board is a great starter platform for blimp robotics. The Arduino code to run it is here.
Read more…
3D Robotics

After my impetuous outburst about the limitations of the Parallax Basic Stamp platform, Parallax co-founder Ken Gracey was kind enough to respond directly in the comments. Excerpt:

The BASIC Stamp product line will continue to be developed by Parallax. But most of the improvements we make to the product line pertain to documentation, operating speed and memory, and the addition of commands. You won't be seeing a floating point library built into the BASIC Stamp.

If you want to have true simultaneous processing with another high-level language, my suggestion is to use the Propeller. You seem to already know that processor so I'll skip listing the specifications. We aim to make the Prop very easy to use by publishing our educational tutorials (see Propeller Education on this page). The forums supporting the Propeller are very active. Supporting the growth of the Propeller is a big priority for Parallax and we back our position by responding to customer requests. In this case, you've got a complete floating point library to use. There's also a BS2 library for the Propeller in case the user wants to continue using something they've already learned.

He and I also had a good phone chat where we talked more about the options. Here's my bullet-point report from that, and summarizing the comments above:

  • The Basic Stamp platform continues to be staple of electronic education in schools and will be for years to come. It's still growing in terms of its usage base.
  • That said, the technology is not going to evolve much more. The things we want, such as floating point, C-like variable handling and significant increases in memory, are not planned for the Basic Stamp architecture.
  • Instead, Parallax recommends that we shift to the Propeller chip, which has both everything we need and reflects the direction that Parallax as a company is going.
  • Although Propeller is not currently as easy to learn as the Basic Stamp, Parallax is working hard to improve that. One thing in particular that will help a lot is a forthcoming serial debug window facility like that of the Basic Stamp. This will let you use the PC as a display screen for the chip's output and otherwise get real-time data on variables and program operation. Finally, it will be possible to write a simple "hello world" program for the Propeller and see "hello world" on your screen, rather than just a blinking LED.

As a result, this is what I propose for DIYDrones:

  1. We complete the Basic Stamp autopilot so that it works perfectly as it is, both as a teaching tool and for those who currently have the Basic Stamp hardware and want to keep it.
  2. After that is done, however, we will not develop it further.
  3. We will instead port the Basic Stamp autopilot code to the open source Arduino platform. All future development of our "entry-level DIY autopilot" will be on that platform
  4. After that, we will port the code to the Propeller platform and then encourage better programmers than me to help collectively build an open source "pro-grade" autopilot project on it. This is a big job (just ask Dean Goedde, who used the Propeller for his awesome AttoPilot commerical autopilot), so I'm looking for volunteers to help take it on. Anybody out there want to try their hand at the future of embedded computing (8-core, 32-bit, object-oriented parallel processing)?
  5. To that end, Parallax has kindly offered to donate $500 worth of Propeller gear to DIYDrones. If you want it and can make a public commitment to starting and sharing an autopilot project here (and can demonstrate that you've got the coding experience to pull that off), I'll work with Parallax to give you the gear of your choice up to that dollar limit. Please respond in the comments.
Read more…
3D Robotics

UAV as "drug mule"?

Post by Ian Powell noted without comment (edited for clarity): "Two people emailed be about building them a UAV to travel large distances. After making some enquiries, I determined they wanted: 10kg carrying capacity speed 100km per hour distance 3000 km a drug mule uav!!!!!!!!!!!! It seems to me that this website has sparked an interest from the wrong people just as the diy mini sub is been regulated by the gov because of the same problem."
Read more…
3D Robotics

DIYDrones @ MakerFaire this weekend

DIYDrones is going to be at Maker Faire this weekend in San Mateo. We're going to be in the Wired/GeekDad booth (yes, I wear lots of hats), booth 166 in the Expo Hall (click on the map for detail), all day Sat and Sun. We'll be showing: --The BlimpDuino --The Mindstorms UAV --The Basic Stamp UAV --The Lego Mindstorms FIRST Tech Challenge competition kit (first time seen on the West Coast!) . Also, our rocket friends will be there in our booth with a 22-foot Delta Rocket that has to been seen to be believed. If you think the amateur UAV guys are nuts, you should see the amateur rocketry guys. They also seem to have unlimited budgets (it helps that some of them are VCs!) I'll be giving a live demo of the Lego UAV at the Maker Main Stage on Sunday at 1:30. Come by and say hi! Oh, BTW, I''ve got five free tickets left. If you want one, PM me (envelope icon) and I'll leave a ticket in Will Call for the first five people who ask. I'll confirm if you're one of the first five, so if you don't get a message, you'll just have to pay to get in like everyone else ;-)
Read more…
3D Robotics

UAVs in the Smithsonian

From News.com: "Starting last week, the National Air and Space Museum at the Smithsonian Institution is recognizing that 21st-century technology in an exhibition titled "Military Unmanned Aerial Vehicles." Pictured here in the museum are three of the six UAVs on display (from top to bottom): the RQ-3A Darkstar, the MQ-1L Predator A, and the X-45A Joint Unmanned Combat Air System. In the gallery pages that follow, we'll provide a look at all six aircraft in the field."
Read more…
3D Robotics
I was debugging some code on the Basic Stamp Autopilot this evening, trying to figure out why the navigation function isn't working right. The debug results were mystifying--variables that should have been +-128 were giving crazy values like 64526. And then it hit me: The Basic Stamp doesn't really know the difference between an unsigned word variable (all 16 bits used) and a signed word (first bit is the +/- bit). You can adjust your debug displays to compensate for that (using SDEC --signed decimal-- format rather than DEC), but in other cases you just need avoid signed integers. For instance, it can't do comparisons ("if x < y") with signed variables when the value is less than 0. That's because it sees something like -30 (which should be less than 0) as 65432 [or whatever], which is more than 0. I'm sure there's some clever work-around on this, but that explains why all the math is funky in the navigation routine--I ported it over from C, where variables are handled properly, and forgot that Basic Stamps can really only handle operations on positive integers correctly. I think the solution is probably to add 256 or something to all data so that all the results of our calculations will be in positive territory, and then subtract 256 at the end to make it all right again, but I'll have to work it out on paper before I can be sure. If I were to do the Basic Stamp autopilot all over again, I'd do it on the Arduino, which has no trouble with proper variables, floating point math and everything else (in fact, I may port it over to Arduino soon). I know Basic Stamp is a great hardware platform for learning embedded programming, but its limited variable space and bare-bones programming language is showing its age. For those of you who have been frustrated with my Basic Stamp code, my apologies. It's going to take me another week or two to fix this.
Read more…
3D Robotics

Autonomous blimp ("BlimpDuino") demo

This is a short demo of our "BlimpDuino", a toy RC blimp that has been turned into an autonomous aerial robot driven by an Arduino open source embedded processors. It uses an ultrasonic sensor to maintain altitude and IR sensors to detect a ground-based IR beacon. This demo just shows the blimp circling the beacon and maintaining altitude. Eventually this will become a <$70 modkit that you can buy, but we've got a lot of work to do before then.
Read more…
3D Robotics

Using a neural network to fly a heli

Jack Crossfire's daily updates on his autonomous helicopter project are alway fascinating, but today's is even more impressive than most. It describes how he uses a neural network to take the inputs from his acceleromters, gyros, magnetometers and GPS and turns that all into an output to the heli that keeps it stable in any direction. Here are some more diagrams, but check out the full post to also see his analysis of how cheap real-time GPS is getting and the possibility of using cheap optical mouse sensors for position hold.

Read more…
Have beaten the light painting algorithm to death. These are movies of some words being painted by autopilot. The 35mm sensor captures the entire flight from underneath. Then the flight recording is shown in Google Earth.Painting text in this confined space is the hardest thing the computer does. It requires a third entry in our gain schedule for velocity.P=1.0 Vmax=2m/s satisfy radius=2m for painting textP=1.0 Vmax=1m/s satisfy radius=5m for hoveringP=100 Vmax=4m/s satisfy radius=5m for forward flight.
Light painting VIKA from heroine worshipper on Vimeo.
Light painting LION from heroine worshipper on Vimeo.These are the still photos.

3689301302?profile=original

3689301245?profile=original

3689301365?profile=original

Ning is the only game in town for 13megapixel photo downloads. Right click & view image to get the Ning bling.
Read more…
3D Robotics
Jeff Johnson and I are speaking about amateur UAVs and imaging/mapping at the WHERE 2.0 conference in Silicon Valley on May 12-14, and we thought it would be fun to have a UAV fly-in beforehand. [UPDATE: this has been postponed. See this post for more] I've got an airfield available at the former Alameda Naval Air Station nearly Oakland (right across the Bay Bridge from San Francisco) and could fly on the afternoons of Sunday, May 11th or Monday, May 12. Standard safety rules apply, but we'd love to have any DIYDrones friends join us. After-flying drinks are on me! If you're in the Bay Area and would like to fly, watch or just hang out, please leave your name and preferred date in the comments below.
Read more…
3D Robotics

New world record for autonomous soaring

Dan Edwards, a grad student at North Carolina State University, has set a new world's record for an autonomous glider flying without power from thermal to thermal. On April 18th, his 5m glider flew 29.4 miles cross country in a flight that lasted 68 minutes, entirely without power or manual control. The glider uses a Cloudcap Piccolo off-the-shelf autopilot, but the really smart stuff was the thermal seeking algorithm, which you can read more about here. Dan narrates the record-setting flight: "The first flights were quite uneventful and downright disappointing. Perhaps with the low humidity and low wind, the thermals were just not organized. Adam tried valiently to catch just one medium thermal to maintain altitude and break through the low-level stuff. No birds were out flying and the completely blue sky was an ominous omen that the air just wasn't moving up today. But Blipmaps predicted today would be a 400ft/min thermal day at 2pm, so were holding our breath. Finally around 1:30 we had success catching a single good thermal. Almost immediately, we moved over to auto-soaring and Adam watched as the plane climbed out on its own to over 3000ft. At this point, we decided it was time to get in the truck and move out. The first turn is a roughly 2mi flight over a swamp, but 3000ft is about appropriate to safely make it beyond the swamp even if we found no other thermals. I set the aircraft to track waypoint 0, officially starting the flight around the XC course. The plane crossed the start road at 1:47pm. Off we darted in the little pickup. The plane had worked itself now to over 4000ft, so we were quite confident starting down the first leg. Adam coordinated with Craig to drive ~45mph in order to get in front and stay in front of the plane (we like looking backwards to the plane). After moving through waypoint 0, the vario was calling mostly sink and dutifully speed to fly let the plane move out and stretch its speed legs. What seemed very quick, we made the first turn at 1:51pm and the plane was cooking. It cruised downwind East for leg 2 also without stopping, blowing down the course and hitting turn 2 at 1:55pm, completing the first 4.0 miles in 8 minutes. At this point, we were a bit nervous, hoping the plane would be able to find another thermal to gain some of the altitude back. From last flight test, we tweaked values on a curve that defined what strength thermal the plane would stop for at various altitudes. This curve was designed to keep the aircraft over 2500ft and cap out a bit over 4000ft. As the plane descended after turn 2, the minimum strength threshold came down and the ALOFT code saw a small upcoming thermal, then latched into it, and then proceeded to start orbiting. The thermal did get better as the plane got higher, so it stayed above the up-moving minimum threshold as the plane climbed higher. At once again over 4000ft, the thermal finally was mighty strong still, but the moving threshold said it was time to move on, so the plane turned out of the thermal and started along the course again. This is how it went ... stop and watch the plane thermal, see the soaring mode unlatch, hear the plane leave the lift and start hitting sink, watch the plane start picking up speed and moving quickly to the next thermal, hear the lift getting better and check what the current minimum threshold was, stop and watch the plane thermal. After completing lap 1, the plane was way in the sky at over 3000ft, so we decided it was safe to commence another lap. And then we completed another lap and realized we were still carrying 3000ft at the end and decided to go for yet another! Batteries were holding steady. On lap 3 about 1/3 of the way through, the plane went through a monster hole of sink and sped up to between 35 and 45kts airspeed. This was also the downwind leg, so we had to chase forward at 65mph in the truck. The plane lost a whole lot of its altitude and was the lowest yet, around 2300ft. I started having visions of landing out. But then the plane made a little lurch, the vario stopped drooping low tones, and speed to fly slowed up a bit. Almost all of a sudden, we heard the vario start chirping. The plane pulled into an orbit and the vario was happy, very happy. In fact, the energy rate readings I was getting were off-scale high, pegging my meter over 19.7ft/s (6m/s) climb-rate! It only held this rate for several seconds, but now I know I need to up my limit! This thermal put us well back up to 4300ft and we knew we had lap 3 in the bag. It was also about this time we made a call that we knew we had enough altitude to make the field. So, I hit the "soaring off" button, still leaving speed to fly and other stuff active. This allowed the plane to not worry about stopping to orbit, but created a dolphin-soaring type cruise. A few minutes later, we were back to the start/finish line and crossed the threshold at 2:55pm exactly. Whew! I need to clarify and state for the record I did not touch the soaring computer this ENTIRE flight except for two times: 1. activate soaring mode; 2. deactivate soaring mode. The ENTIRE flight was on autopilot control, all 29.4 miles. On the Piccolo Command Center, the most I did was remove the hold waypoints as we approached them, because they were not needed for this version of flying the course. This did not affect the aircraft's flying and certainly would not have helped anyway. For the record, 29.4miles was autonomous and fully computer-controlled soaring. "
Read more…
3D Robotics
This was my first year at the FIRST Robotics Championships, and I was blown away. More than 20,000 kids and coaches from 1,500 teams from around the world came to Atlanta to compete in the Georgia Dome. They brought more than a 1,000 robots and a dizzying array of team costumes, mascots and pit crews. Imagine a cross between the NCAA basketball championships, the Daytona 500 and the Westinghouse Science Fair, all in a huge arena that's was the site of an Olympics and running for three days of frenetic competition. Mind-blowing and incredibly inspiring. I was there at the LEGO booth demoing my new Mindstorms UAV, which was getting a good bit of attention even with so many competing robots around me (aside from our blimps, which we only showed off in private, it was the only flying robot there). The above is my favorite moment, when Kjeld Kirk Kristiansen, the deputy chairman of LEGO (and the reigning member of the family that started it) and Dean Kamen, the founder of FIRST (and the inventor of the Segway), came by for a demo. I told them that the idea came to me when I was looking to do something that had never been done with Mindstorms before. It's a tribute to the creativity of the Mindstorms community that this required leaving the ground! Next stop (for someone else): space ;-) This picture comes from a great photo gallery of shots from the competition that Lego's Maureen Reilly took. The hardware I used for the Mindstorms UAV was a prototype of the gear that will be in next year's FIRST Tech Challenge competition kit, replacing the VEX robotics kit that has been used to date. This has been very controversial, not least because of the investment in time and money people have made in VEX. But it's clearly the right way to ensure that the competition continues to move with the times (adding a 32 bit processor, bluetooth and a suite of powerful sensors). The old VEX kits were designed mostly for remote control ("teleoperated") bots, while the new ones are more better suited for autonomous bots. To my mind, if it's not autonomous, it's not really a robot, so this move is welcome and perhaps even overdue. But autonomous robotics is harder and the Mindstorms-based platform (with aluminum parts and servos and motors) is still new, so in the limited trials I saw people were still struggling to get the bots to complete the challenges. I suspect that LEGO will tweak the kit by adding some more powerful motors and a slightly less difficult course to ensure that next year's proper launch is a success. But for the rest of us, the introduction of servos, motors and the rest of the real robotics world to Mindstorms is a huge gift. You ain't seeing nothing yet!
Read more…