Club Projects

• BotShop Manual – BotShop User Manual
• BotShop II

• IGVC – Intelligent Ground Vehicle Competition entry
• X3P – Experimental Pink Plastic PowerWheels
• Underwater ROV II – “Fire under the Ice” Competition
• RoboMagellan – RoboMagellan Competition entry, dubbed “SpyBot”
• Hexor – Six-legged walker
• Sensor Motes – ME/CPE Senior Project: Wireless Sensors
• RoboRodentia 2009 – Entry for IEEE-CS's RoboRodentia Competition during Open House (in April)
• Xiphos Board – Darron's senior project to improve upon the PolyBot board. The club will start producing them for Fall 2009.
• Auto Heli – Autonomous Helicopter Project.

• Seiko Robotic Arm - donated to the club by REC Solar

• RoboRodentia 2008 – Entry for IEEE-CS's RoboRodentia Competition during Open House
• TANK – Antonio Hernandez's and Ben Davini's RoboRodentia 2008 entry
• Ender – Darron Baida's RoboRodentia 2007 entry
• Triple Threat – Club RoboRodentia 2007 entry
• Spybot – Early incarnation of SpyBot - a general purpose robot and RoboMagellan entry
• BotShop Summary – Fall 2006 BotShop Summary
• Sidekick – Club RoboRodentia 2006 entry
• Caddy/ALF – Club RoboRodentia 2005 entry
• Sandwich Board – Our missing sandwich board for Dexter Lawn
• Ultrex Ox – Animated mechanical ox at Sinsheimer Field
• Underwater ROV – MarineTech ROV Competition

Here are some guidelines to help you get a new project off the ground:

1. Come up with an idea! Most of us are brainstorming new ideas all the time, so this should be pretty easy. The better project ideas usually have a well defined goal, which is why robot competitions often work very well.
2. Suggest the idea to the club. Make an announcement at a club meeting or on the club mailing list and get a feel for how much interest there seems to be in the project. Timing is a factor to consider here. If everyone in the club is already busy working on one or two bots you might not get much response.
3. Schedule your first meeting. Pick a place and time when the most number of interested members can meet (Tip: Use the overlay feature of Google Calendar to find common free time). Be sure to post the time that you decide on the club Calendar (ask the current webmaster to post it for you or give you access to the calendar).
4. Pick a name. This sounds trivial, but will greatly simplify administrative tasks if you decide on a codename early on. For example, Microsoft decided on the code name longhorn long before deciding to release the product under the name Windows Vista. Try to pick a creative codename that is eight or fewer characters and has no weird punctuation.
5. Create a Google Group. You can ask the current webmaster to create a group for you, or you can create it yourself. Get people who are interested in your project to join the Google Group. Be sure to place a Google Group join form on your page to make it easy for people to subscribe (look at the code for another project to see how to do this or ask the current webmaster for help.
6. Start documenting and collaborating. It's never too early, and with DokuWiki it couldn't be easier. Just add a line to the Active Projects section above using the project's codename to start a new namespace. For example:

   [[mycodename:start|My Codename]] -- One line description of the project