Slashdot Mirror


Open Design for ~$800 Swarm Robots

An anonymous reader writes "There are lots of multi-robot designs out there. Most are either research platforms well over $2K (often $10K or more), or are hobbyist bots under $400 with tiny brains and few sensors. But George Mason University's new FlockBots wiki is interesting. They're trying to pack as much functionality as possible into a roughly $800, 7" mobile swarmbot, and publish the design and software as a free and open spec. So far their design includes a wireless 200MHz Gumstix Linux computer, a camera, range and bump sensors, wheel encoders, a can gripper, and lots more. It's a great-looking design and I think the cost could drop to $500 with vendors doing consolidation."

23 of 106 comments (clear)

  1. Comment removed by account_deleted · · Score: 2, Funny

    Comment removed based on user account deletion

  2. Military applications? by CyricZ · · Score: 4, Interesting

    I wonder if we'll see freedom fighters in countries like Iraq and Afghanistan start to use robots like these such as weapons (assuming these researchers do succeed in keeping the cost low). Indeed, considering the US military's increased use of drones and unmanned combat vehicles, it is doubtful that those they are fighting against will not soon resort to employing he same methodologies.

    This particular device uses Linux, which brings up another question: should developers of open source software license their software so as to prevent it from being used in such killing devices? Or should freedom trump such an argument?

    --
    Cyric Zndovzny at your service.
    1. Re:Military applications? by cranos · · Score: 3, Insightful

      Nope not a chance. Part of the reason why the insurrgency has been so successful is the low tech aspect. This is something the US found and the forgot about in Vietnam. In a straight up battle, the US probably has the best technology in the world, against simple devices such as road side bombs and car/truck bombs they don't know what to do.

    2. Re:Military applications? by hoggoth · · Score: 5, Funny

      > should developers of open source software license their software so as to prevent it from being used in such killing devices?

      This is a great thought. By forbidding using open source software in killing devices we will cause great numbers of lawyers to approach the fighters to serve notice of the lawsuits. The fighters, of course, are already killing people and killing a few lawyers that get in their way won't bother them.

      Killers use up their inventory of killing robots.
      Software developers feel good about being on the moral high-road.
      Lawyers die.

      It's a win-win situation.

      --
      - For the complete works of Shakespeare: cat /dev/random (may take some time)
    3. Re:Military applications? by Admiral+Burrito · · Score: 4, Insightful
      This particular device uses Linux, which brings up another question: should developers of open source software license their software so as to prevent it from being used in such killing devices?

      Somehow, I doubt that people who would use the software for such purposes would be dissuaded by the licensing conditions.

    4. Re:Military applications? by Profane+MuthaFucka · · Score: 2, Insightful

      We should not restrict anybody from using software. If we allowed restrictions then everybody would have their favorite restriction.

      -no military uses
      -no Taliban can use this software
      -no al Queda can use this software
      -no Nazis
      -no Republicans
      -no vegetarians
      -no meat eaters
      -no SUV drivers
      -everybody but Martha Stewart

      and so on. Pretty soon what was free isn't so free. That's because restrictions and freedom and opposing concepts. When in doubt, go with freedom. Some people will do things don't agree with with their freedom, but if you try to stop them from doing these disagreeable things with their freedom, you are the DEVIL.

      --
      Fascism trolls keeping me up every night. When I starts a preachin', he HITS ME WITH HIS REICH!
    5. Re:Military applications? by hernick · · Score: 2, Insightful

      Open Source must be free for all or else it isn't Free. Should the GPL include a clause that prevents military contractors, neo-nazis, child molesters and Bill Gates from using the software ?

      Never. We cannot exclude a single group from using Free software. This would be a desecration of the Freedom that the software stands for. Also, every OSS author would use the license as a political platform to condemn people at random: "This software cannot be used by Southern Baptists, Wahhabists and the followers of Ayn Rand."

      --- By having read this post, you have already agreed to the Mostly Open Posting License. You are hereby granted the generous authorisation to read this post, but only if you are not a Witch, the daughter of Bill Gates or a fat-cat billionnaire. If you have read this post illegally, in defiance of this read-through license, you must paypal ten thousand american dollars to the author of this post, before Big Ben has sounded the upcoming call of midnight.

    6. Re:Military applications? by B3ryllium · · Score: 2, Funny

      I'll take "Before and After" for $2000, Alex.

  3. Interesting equipment choice by Sv-Manowar · · Score: 4, Insightful

    Its interesting that they chose to pair the Gumstix with the Acroname Brainsem. I've been working with the brainstem for mobile robotics as part of CSCS and found it extremely flexible for robotics development. In what we've been doing, we used the brainstem chained to Zaurus PDA's, to achieve a similar linux control environment for the actual board (as the TEA language used to program the brainstem is somewhat restrictive). This platform seems like a great way for people to start out with a known good set of equipment, something that would really have helped us when getting started. (We had a whole load of teething issues getting the PDA's and brainstems talking, not to mention creating working combinations of servos)

    1. Re:Interesting equipment choice by belphegore · · Score: 2, Informative

      I think they haven't yet got a Robostix, which we designed to be a replacement for the Brainstem at a much lower price, with a better feature set, and better gumstix integration. Still not much there on the software side for Robostix, but all your normal AVR tools should work great, and control of the robostix from userspace on the gumstix is just around the corner.

    2. Re:Interesting equipment choice by awkScooby · · Score: 2, Informative
      My Robostix was ordered last week, and should arrive next week. We'll be evaluating it to see how good a fit it is for the FlockBots, and how much effort there will be in switching to it (soldering ~40 pins per board adds up).

      If nothing else, I look forward to a microcontroller that can keep up with the quadrature wheel encoders. Having to use polling on the Brainstem was less than ideal -- we had to slow the bots down a whole lot.

    3. Re:Interesting equipment choice by Anonymous Coward · · Score: 2, Interesting

      The problem with sonar is that it eats batteries like there's no tomorrow. That's fine if you're runnng off of lead acid or li-poly like the bigger bots, but these guys are trying to run the bot for 4 hours off of a pack of 5 A's. Sonar's not feasible for this, but the excellent SHARP IR rangers they're using *are* feasible for it.

  4. Like some anonymous coward said... by myowntrueself · · Score: 2, Funny

    When the time comes to start smashing up robots, count me in!

    --
    In the free world the media isn't government run; the government is media run.
  5. Deterrent in the Field of Robotics by kai.chan · · Score: 5, Insightful

    Having an Open Design is well and good, but I think there is still one main factor that prevents the field of robotics from flourishing. The problem stems from the lack of standard in both the development of the software, hardware, and mechanics.

    Since there is no standard, someone can be using Microcontroller A with Motion Controller X using Programming Language N. Then finally combining these electronics with Servo K. When drivers for Motion Controller X has already been written under Programming Language M, developers have to spend time porting the code for another language for a different microprocessor, which might or might not work with the Servo.

    When there are so many variables in robotics without any standard, a lot of development time are wasted either porting code, finding minor differences between devices and motors that causes incompatibilities, or choosing non-optimal parts for ease of implementation. In order for the field of robotics to advance at a faster rate, there needs to be a more standardized open environment in the software, hardware, and mechanical aspect.

    1. Re:Deterrent in the Field of Robotics by kai.chan · · Score: 2, Insightful

      You completely missed the point of my post. The basic IEEE standards that you are refering to do not help the advancement of robotics.

      For example, I wrote code for a motion controller to drive some motors, with UART, serial, all adhering to these standards. But guess what would happen to that code when the motion controller needs to be changed? I have to write new drivers for the new motion controller following the manufacturer's specifications. After writing the driver, there begins a process of testing.

      Everyday electronics might have standards, but these standards that you are refering to does not mean that every microcontroller will have a Watchdog Timer, and not every motion controller will have the same states to drive motors.

  6. WTF?! by MukiMuki · · Score: 2, Funny

    No "traveling beowulf" jokes?

    Not a single Skynet reference?

    Where the hell AM I?!

  7. Before they're loose... by nxtr · · Score: 2, Funny

    Make sure the switch is set to 'serve', not 'kill'.

  8. Can gripper? by Tablizer · · Score: 2, Funny

    ...seems the ultimate goal is to fetch another beer without leaving the couch (and without organizing the fridge). AI has officially arrived when that has happened.

  9. only you by jeffehobbs · · Score: 2, Interesting


    Cheap swarm robots? Hopefully they can find the room to post this somewhere in their workspace.

    ~jeff

  10. Another approach... by Jesrad · · Score: 2, Informative

    I can think of another sort of open source robots that cost well under $100.

    --
    Maybe we deserve this world ?
  11. You can shave a lot off that $800 by Rxke · · Score: 2, Interesting

    if you're willing to do some soldering.

    A look at the list reveals some of the off-the-shelf stuff is very pricey (like the battery charger, boy oh boy, what a rip-off.)

    I guess we'll see people come up with homebrew solutions to expensive off-the-shelf parts, and bring the price down to, say $400, easily.
    Might be an interesting project to follow.

  12. Idea for a complementary bot by goodEvans · · Score: 2, Interesting

    What you need is another, similar bot with a flat top and a forklift-type arrangement on front. Then you can get a lifter bot and a normal bot working in cooperation to get stuff onto a table etc.

    Now imagine a tower of these things...

    ps. I think I've just worked out where this idea came from. Remember the episode of Futurama, where Fry, Leela and Bender are trying to escape from the robot planet, and the robots chasing them start stacking themselves on top of one another, before crashing to the ground because the bottom one slipped on the shipment of lugnuts?

  13. Sea Swarm by Anonymous Coward · · Score: 2, Interesting

    I'm working on an underwater version. Bigest obstacle is communications. Blue-green LED (as opposed to infrared for use above water) gets good bandwidth but fallback to modulated 50kHz when link fails is a royal PITA. Power requirements aren't too bad as B&W camera with blue-green light source sees pretty well under water. Failsafe for dead main battery is valvewhich opens when power is lost allowing bladder to inflate and fish to float, belly up, like a dead fish. Beacon on belly mounted antenna runs on it's own battery which is connected when valve opens. Basic RDF to locate the dead fish.

    Not ready yet so no pix. Perhaps another 18 months ...