The main project goal was to complete a working prototype for an Autonomous Foosball Table (AFT), where a human player faces a robotic opponent. From the human perspective of the game, the foosball table is very similar to a regular table. The player(s) on the human side are controlled via a series of four handles that can be moved in and out and rotated to move the players linearly across the playing field and to kick the ball towards the opponent's goal. The autonomous side consists of:

> Eight servo motors used to manipulate the handles of the foosball table
> A microcontroller to activate the servo motors and communicate with the computer
> An over-head mounted webcam to track the ball and players
> A computer to process the webcam images, implement artificial intelligence, and communicate with the microcontroller

Budget constraints for the prototype slowed the project some and kept its functionality to a minimum. Proper motors to move the players at a competitive speed were found to be very expensive, so lower-end servos had to be used.

While this particular implementation was limited by cost and time, a larger gear ratio would yield a faster playing robot, although doing so would cost more than the $500 base price (price without power supply & computer).

Step 1: Assembling the Motor Control Board

The attached images are a full circuit schematic as well as a picture of the final product for the motor control board. All of these required parts may be purchased at most major online electronics stores (including Digi-Key and Mouser. As a side note, all of the parts used here were through hole, and thus, the parts may be assembled on a protoboard/breadboard, or using the attached PCB design. A much smaller package could be created by using a number of surface mount parts.

When we implemented, the design, we split the motor controls into 2 circuits, though there is no advantage to doing so other than any particular cabling scheme used. The small blue board implements the PWM control circuitry, which is basically just a clocked PIC-12F with some specialized code.

Step 2: Servo Motor Assembly

Two different types of servos are used. First, the lateral motion is controlled by a group of four high-torque servos: Robotis Dynamixel Tribotix AX-12. These four run on a single serial line and provide amazing functionality. The high torque enables these servos to be geared in such a way that provides a high tangential velocity for lateral movement. We were able to find a set of 3.5 inch gears and tracks to go with them from Grainger at a cost of about $10 for each. The servos provide torque overload protection, an individual servo addressing scheme, quick communications, internal temperature monitoring, two-way communications, etc. The downside of these servos is that they're expensive and not very fast (though gearing helps them). So in order to get faster motion for kicking, Hitec HS-81s are used. The HS-81s are relatively inexpensive, have a decently fast angular velocity, and are easy to interface (standard PWM). The HS-81s only rotate 90 degrees, however (though it is possible -- and not recommended -- to attempt to modify them to 180 degrees). Additionally, they have internal nylon gears that strip easily if you attempt to modify the servo. It would be worth the money to find a 180 degree rotating servo that has this type of angular velocity.

The entire system is tied together with pieces of medium-density fiberboard (MDF) and high-density fiberboard (HDF). This was chosen for its low cost (~$5 for a 6'x4' sheet), ease of cutting, and ability to interface with virtually any surface. A more permanent solution would be to machine aluminum brackets to hold everything together. The screws holding the PWM servos in place are standard machine screws (#10s) with hex nuts holding them from the other side. 1mm metric machine screws, about 3/4" in length, hold the AX-12 into the MDF that connects the two servos together. A double-action drawer track holds the entire assembly down and in-line with the track.

Step 3: Software

The last step is to install all of the software used on the machine. This consists of a few individual pieces of code:

> The code run on the image processing PC
> The code run on the PIC-18F microcontroller
> The code run on each of the PIC-12F microcontrollers

There are two prerequisites to install on the image processing PC. The image processing is done through the Java Media Framework (JMF), which is available through Sun here. Also available through Sun, the Java Communications API is used to communicate to the motor control board, across the serial port on the computer. The beauty of using Java is that it *should* run on any operating system, though we used Ubuntu, a linux distribution. Contrary to popular opinion, the processing speed in Java isn't too bad, especially in basic looping (which vision analysis uses quite a bit).

As seen in the screenshot, both the ball and the opponent players are tracked on each frame update. In addition, the outline of the table is located visually, which is why blue painters tape was used to create a visual outline. Goals are registered when the computer cannot locate the ball for 10 consecutive frames, typically indicating the ball fell into the goal, off the playing surface. When this happens, the software initiates a sound-byte to either cheer itself or boo the opponent, depending on the direction of the goal. A better system, though we did not have the time to implement it, would be to use a simple infrared emitter/sensor pair to detect the ball falling into the goal.

All of the software used in this project is available in a single zip file, here. To compile the Java code, use the javac command. The PIC-18F and PIC-12F code is distributed with Microchip's MPLAB software.

Step 4: Webcam Mount

A Philips SPC-900NC webcam was used, though it is not recommended. The specs for this camera were falsified either by the engineering or sales staff at Philips. Instead, any cheap webcam would do, so long as it is supported by the operating system. For more information regarding the use of webcams under linux, check out this page.

We measured the distance required by the webcam's focal length to fit the entire foosball table in the frame. For this camera model, that number turned out to be just over 5 feet. We used shelving racks available from any major hardware store to build a mount for the camera. The shelving racks extend upward from each of the four corners of the table and are cross-braced by angled aluminum brackets. It is very important that the camera is centered and has no angular rotation, since the software assumes the x- and y-axis are aligned to the table.

Step 5: Conclusion

All of the related project files can be downloaded at this site. A backup of the majority of the site content can be found here, at my personal web host. This includes the final report, which has a marketing analysis as well as things we would change, our original goals and a list of what specs were actually attained. The project is NOT meant to be the most competitive player in the world. It is a good tool to show more of the steps used in designing such a beast as well as a decent prototype of this type of robot built for an incredibly low cost. There are other such robots in the world, and certainly, many of them would "beat" this robot. This project was designed by a group of four electrical/computer engineers at Georgia Tech as a senior design project. No help was received by any mechanical engineers and no third-party funding was used. It was a great learning process for us all and a decent use of senior design course time.

I would like to thank
> Dr. James Hamblen, our section advisor, for his continuous help in technical strategies
> Dr. Jennifer Michaels, the lead professor, for not discouraging us from attempting a more ambitious project
> James Steinberg and Edgar Jones, the senior design lab administrators, for constant help in ordering parts, troubleshooting, and the finding the "cool stuff" to throw into the project at low cost and high functionality
> And of course, the other three members of my team, of which, none of this would have been possible: Michael Aeberhard, Evan Tarr, and Nardis Walker.
i am awesome at foosball! <br>in a championship game series, I won the most matches but lost the final games, so I lost.
I always loved autonomous objects...especially competitive ones. some other organizations that have done autonomous objects are FIRST ROBOTICS CHAMPIONSHIPS, and DARPA. check these out and fall in love... or look at the popsci.com for amazing news about technology. i am a electrical engineer from the first robotics championships. currently a student soon will mentor other students in programming, wiring, and electronics. and I hope to join the DARPA teams someday<br><br>
This is a really cool instructable. Thank you for showing people how to do something so advanced. With understanding of modern technology, anything is possible and we can begin solving the problems of the world!
very nice work. this is a proof of concept and someday you may be able to use a system that could beat a descent human opponent. maybe strong magnets placed in a certain order of polarity at set distances inside the poles of the foosball table could be paired with a computer controlled electromagnet in order to move the poles. ur reply to this will probabally make this idea look stupid.. oh well
edit: in my above post it says computer controlled magnet, by that i mean a set of magnets for each pole.
no there are only magnets with both poles, north and south. unipolar magnets have so far not been discovered.
Let me be the first to say that your project is so cool! I am quite a good programmer myself, but this is kind of advanced which is very interesting to me. I have a web cam, had c++ Programming before, and have a Foosball table. I am complete! I can make my own one now! Thanks for the help. I'm sure "Eric Wilhelm" will love to hear about this. I will spread the word for you. Again this is really awesome!
Could the author elaborate on what gears / motors / other parts could be improved on if the budget fo rthe project could be exceeded? For example,w hat model of motor to use for a faster player movement, or what model of server will do the full 180 degree kick?
My gosh, this is great—and how generous of you to go to the considerable trouble to make an Instructable so you could share it with everybody. To those of you complaining that the AI can be improved—well, build one, improve it, and post about it here! (How do you spell "collaboration"?)
can you make it track a person???
That's quite a mind-boggling schematic, especially since I can't even solder.
Excellent job guys! Vision with mechanics always presents extra trouble! I worked on a similiar project myself with some classmates in college:<br/><a rel="nofollow" href="https://www.instructables.com/id/Automated-Pool-Table/">RoboPoolTable</a><br/>
nice!!! but it seems to lag a little.
Great Job
i give u major props for makeing that
wow looks very complicated but it is definitely worth it coz it sooo cool!
I think there's a typo on this page. You said something about thanking the other 'three' members of your team.
"> And of course, the other three members of my team, of which, none of this would have been possible: Michael Aeberhard, Evan Tarr, and Nardis Walker." No typo. the three members are listed clearly, I don't get what you mean. The three first thanked persons were not in the team.
etarr was one of the members on the team (evan tarr). his comment was a joke, as one of the members did a bit less than the others ;)
Uhh... what happened to the video? It says that the video isnt available anymore.
can that program be used to track anything? if yes, how do I compile it, or how do I use it? I don't want the output part, just the tracking
This is impressive!
Very nice work! Getting a robot to even hit a ball is impressive. I've seen many people that couldn't do that! But, being a Foos junkie, I'm pretty sure any players could skunk it 9-0. For a real tracking system vision wouldn't work, real shots can not be seen, you have to know where it has to go and race it or block the long leaving the short or middle wide open. But, as I said, Impressive work!
Cool stuff the amount of work you have put in to it shows
Very nice of you to release the source, I look forward to reading it. Well, I understand that it can't work too fast with a just a webcam locating the ball. Most of these use infrared.
what does this have to do with a laser?
Well done- Look awesome, Could be a bit smother with a faster camera. :-)
Awesome! Now if only I had the stuff to build it...
Looks fun, but I don't have the money for such a project, maybe when I am slightly older, and have sustainable employment (and my parents don't make me put my money earned in the bank).
@kkinney:<br/>The robot is very limited by the mechanical design, but it's still pretty intimidating playing against it. It does a pretty good job defensively, as the software attempts to cut off the angle to the goal. Unfortunately, the offensive capabilities are rather unimpressive. The kicks are a little too slow and inaccurate.<br/><br/>@jcampbell:<br/>As exciting as robot-on-robot action sounds, it would be pretty silly to have 2 of the same robots playing against eachother. I think it would be interesting, however, to make a competition like <a rel="nofollow" href="http://www.robocup.org/">robocup</a>, but with foosball<br/>
Spiff! How well does it do against a moderate carbon based player?
So when do you build a second unit so two machines can play against each other? Sounds like a setting for some fun research...
Is there a way to run the software on a Mac?
The software is written in Java, whic is operating system independent. However, it utilizes the Java Media Framework and the Java Serial Communications API. Anytime you use something like that for hardware controls, it tends to get more OS-dependent. We didn't test the software on a indows PC or a Mac because we had no reason to. Some software changes may be necessary for a Mac implementation, though they are Unix-based, so it may not be too significant.
We came up with the idea in the first week or so of the semester and announced our intentions by the first of September. We did a demo of the final project December 8. So a about 3 months from concept to implementation with a 4 person team. There was a llloooottt of writing for the course though, so I would say only about 70% of our time was doing technical stuff.
that's incredible. how long did it take you to come up with idea and make it?
I heard about something like this at an MSOE camp this summer. Really Cool!
it's awesome!
Awesome, looks amazingly difficult..
This is awesome - Great job!

About This Instructable




More by eski:Autonomous Foosball Table 
Add instructable to: