Blimp UAV: handling navigation indoors
The blimp UAV project is moving along nicely. We've picked a general size and selected most of the components. We've now decided to go with a PIC processor, rather than the Stamp, Propeller, or ATMega168 that we've been using here to date because you can get PICs in faster speeds and with more memory, something we'll need for expandability down the road. My partners in this project also have a lot of custom PIC development tools, so since they're going to do most of the work I'm happy to take their suggestion. The big deal this week is that our IR navigation system, Evolution Robotic's NorthStar, arrived. This is the DevKit, which isn't cheap ($1,800) but we only need one and the idea is that we can build a board that has the receiver built in and a cheap transmitter kit. We're hoping to keep the cost to users of both under $100.
The kit that arrived is for NorthStar 1.0, and now that Evolution Robotics has announced Northstar 2.0 at CES, I can disclose that that's actually what we've been planning to use all along. But the dev kit for that one isn't ready yet, so we're building the first prototype on 1.0 and then upgrading the necessary parts and code when 2.0 arrives.
Here's the basic overview of how NorthStar 1.0 works:
And here's what's in the dev kit:
First, it comes in two nifty cases, one for the IR transmitters (shown above) and one for the IR receiver:
Here's what's inside the transmitter case (click for bigger picture and readable text):
Here's what's insider the receiver case:
Here's what the receiver looks like, attached to the PC interface that's used for testing:
Here's what the receiver looks like placed on the BlubberBot circuit board, which is about the size of the one we're going to use (this one is based on the Arduino platform, but ours isn't very different). This is the front of the board, hanging from the bottom of the blimp:
And here's the NorthStar receiver that I've placed on the back to get a sense of scale:
You'll note a challenge that we'll have to overcome. NorthStar 1.0 (and one of options on NorthStar 2.0) is based around the idea that IR transmitters would beam spots on the ceiling and the receiver would be placed to look up and navigate from those. But our blimps are going to be used in gymnasiums and other large rooms where the ceiling is too far away to see. So we'll want to navigate based on direct line of sight from the transmitters.
So where should we mount the receiver? If we mount it facing down, it will lose sight of the beacons when it's close to the ground. Facing to any side means that it won't be able to see any beacons not on that side. We could use two receivers, one on each side and hope that one's always in sight of a beacon, but this introduces complicated hand-off problems as the blimp rotates.
Roomba, the robot vacuum cleaner from iRobot, uses a similar system to get back to its charging base, but rather than spots on the ceiling or trying to keep facing an IR beacon, it uses a cone-shaped mirror that bounces IR from any angle down to a horizontal ring of IR sensors:
What if we mounted one of these on top of the NorthStar reciever and then placed the package horizontally below the blimp? We'd use two direct IR beacons in the room, rather than projecting spots on the ceiling (that just means taking the diffusing lenses off the IR transmitters).
We'll have to play with the system a bit to see if that works, but for now that's the plan. BTW, with a third IR transmitter, it's possible to get altitude, too, but the math on that is kinda gnarly, so we're using an ultrasonic sensor firing down for now.
-
Comment by Jack Crossfire on January 23, 2008 at 12:08pm -
The Atmels do 20 MIPS. Have only seen the 8 bit PIC's do 12 MIPS. Wonder why Northstar bothered with a projection + reflection method instead of just having 2 light sources. Wonder if it works in an extremely small, cramped $1/2 million apartment.
-
3D Robotics Comment by Chris Anderson on January 23, 2008 at 12:15pm -
I'm not sure which PIC we'll be choosing, but my partners have a lot experience with them and are sure it will do the trick. As for the NorthStar reflection system, it's the best way to ensure that you've always got line of sight for ground-based bots (you can see more of the ceiling than any point on the ground, since obstructions tend to be on ground level.
But NorthStar 2.0 allows direct line of sight, too, which is what we'll use since the ceilings in a gym are too high. Ultimately, that will allow us to extract z-dimension information, too, which may allow us to dispense with the ultrasonic sensor we're using for altitude.
To carry all the gear, you need at least a four-foot blimp. That means a pretty big living room at least, to give it room to maneuver.
-
Comment by Peter Klemperer on February 7, 2008 at 1:47am -
Have you looked at this system for beacon location?
http://www.pololu.com/catalog/product/701
-
3D Robotics Comment by Chris Anderson on February 7, 2008 at 8:17am -
I haven't, but looking at it now, I can see two problems:
Max range: 15 feet
Native resolution: +- 90 degrees (just four sensors, on on each side)
On the last point they recommend that you rotate the robot back and forth to calculate the differential signal from two or three adjacent sides, so you can increase that angular resolutions, but that's obviously not an option for a blimp.
-
Comment by Howard Gordon on February 7, 2008 at 8:38am -
I hadn't seen the Pololu board before - that's exactly the system we used for IR on the first version of our robot, though I think the IR emitters and detectors we used, Vishay TSAL6200 and TSOP1736, perhaps had a better range. I did some early range tests and easily got 30-40ft. The big issue was that while the detectors had a very wide field of view, the emitter beacon was only 30-degrees wide, so you needed an array of emitters to provide wider coverage. In any case, this is a cheap and effective approach - the detectors cost less than $1.00 each and the emitters cost around $0.10.
-
3D Robotics Comment by Chris Anderson on February 7, 2008 at 8:43am -
Weight is a huge issue with blimps. I don't think that the multiple boards approach would work. We think we've got a much better solution with NorthStar, which is super light and has a +-2 degree native resolution in our tests
-
Comment by Howard Gordon on February 7, 2008 at 9:07am
-
Are the iRobot sensors available ? Do you have any specs ? The issue there is that while the detector has a wide field of view, the sensor is probably somewhat planar, perhaps +-15 degrees, so you'd need a stack of emitters aligned vertically in order to make certain they can be seen from different blimp heights.
-
3D Robotics Comment by Chris Anderson on February 7, 2008 at 10:12am -
I don't know about the iRobot sensors, but the Evolution Robotics ones we use are designed to project a spot on the ceiling, which can be seen from any angle. We're need to test them more to see what the implications are of direct line of sight with the beacons. We're told it should work.
Comment
Social Networking
Top Content
Contests
Season Two of the Trust Time Trial (T3) Contest has now begun. The fourth round is an accuracy round for multicopters, which requires contestants to fly a cube. The deadline is April 14th.A list of all T3 contests is here.
Groups
-
ArduPlane User Group
719 members
-
Agricultural UAVs
155 members
-
Moderators
24 members
-
ArduRover User Group
205 members
-
Spanish arducopter Users
88 members
Advertisement
© 2013 Created by Chris Anderson.
Powered by
You need to be a member of DIY Drones to add comments!
Join DIY Drones