Main Page
|
Course Admin
|
Course Resources
|
Rules & Regulations
|
Team Profiles
|
Photo Gallery
|
Contact Info
 
  You are here: RoboFlag Main Page > Team Profiles


 

The teams participating in the RoboTag course are comprised of fourth-year engineering students from the Department of Electronics and the Department of Computer and Systems Engineering from the Faculty of Engineering and Design at Carleton University. The teams are as follows:



The Sentinels

The Sentinels will be building a robot called "Morpheus" with the expectation that as much as they try to destroy it through misguided efforts, it will prevail. You can check out their webpage at http://www.geocities.com/robo_flag/.

Morpheus will be using stepper motors, a custom stepper motor driver that John's going to build, and a combination of sonar, infrared rangefinders, and a secret (and very cool) bumper system. The Sentinels are using an expansion board to solve the I/O shortage, and are going to use a sophisticated subsumption behaviour architecture.



John, Steven, and Nathalie
(click for more pictures)

Team members:




Team -1

Team -1, named for their lack of a third group member, is attempting the project with only two group members! They've decided to call their robot "Larry". I don't know why. Check out their webpage at http://www.engsoc.org/~bford/.

Larry will be powered with DC gearhead motors driven from the H-Bridge on the HandyBoard, and will be wearing a skirt - a bump skirt, that is. Brian has developed a simple (yet sophisticated) finite state machine navigation strategy that just might work. PICs are being used to solve the I/O shortage in a serial communication exercise I'm impressed with.



Rob and Brian
(click for more pictures)

Team members:




Team PlayBot

Team PlayBot ("Adult Engineering Entertainment") will be designing a robot named "Bingo". I'm sure it'll wear something naughty. Their excellent team webpage is: http://chat.carleton.ca/~jtrudgen/.

Bingo will be using stepper motors and a 293/298 driver, interfaced to the HandyBoard via a PIC. Quan's going to be using a subsumption behaviour architecture to implement a pretty cool (and proprietary) flag acquisition plan. Jaymeson is working on an amazingly cool turret that will track the flags and other robots. The expansion board is being used to solve the I/O shortage.



Jaymeson and Quan
(click for more pictures)

Team members:




The Titans

The Titans will be building a robot called "Maximus". I imagine it will be a gladiator of sorts. They have an excellent webpage at http://www.TitansRoboFlag.com.

Maximus will be using three nifty "omni-wheels" and DC gearhead motors to translate (not move) around the arena. Yes, that's a foam bumper you see there, folks. Tony's planning a hybrid subsumption and FSM system for the command and control. Chatlaine has come up with one of the simplest and most efficient methods of grabbing the flag that I've heard.



Chatelaine, Tony, and Reid
(click for more pictures)

Team members:




The Pathfinders

The Pathfinders aren't associated with the Girl Guides of Canada. While they may insist that they aren't 12-15 year old girls, I suggest that you make that call yourself. They're building a robot named "cookie". Get it? Girl guides? Cookie? Aahaha. Their webpage is located at http://www.engsoc.org/~tunabear/roboflag/.

Cookie will be powered by a huge pair of stepper motors, controlled by a custom driver that Jason's going to be building. He plans on using surface mount components and soldering the PCB himself! These guys have a very cool idea for their bump sensors. They're going to be using the expansion board to solve the I/O shortage. Tun's developing bronze, silver, and gold plans for navigation. I like the silver plan.



Andrew, Jason, and Tun
(click for more pictures)

Team members:




The "A" Team

The "A" Team has decided to build a robot with a mohawk. The 'bot will be called "B. A. Baracus", who Mr. T plays in the series. They have an excellent webpage at http://www.hld.ca/a-team/.

BA will be powered by some amazingly strong cordless screwdriver motors that stall at some incredible 3.5A (each!). Driving these giants will be the responsibility of a custom PCB that Mark is developing, featuring some serious heat sinks. The "A" Team is also the only team to use a non-HandyBoard microcontroller. They're using the OOPIC system, with the I2C network protocol, so they don't have any of the I/O shortage problems the HandyBoard folks do.



Thusha, Dan, and Mark
(click for more pictures)

Team members:






Each team has three members performing the following roles:

Electrical Designer - this position is typically based around the electronics and hardware design requirements of the robot. The designer might be responsible for:

  • designing and building a motor control board
  • designing and building a grabbing mechanism
  • testing and interfacing sensors with the HandyBoard
  • designing and implementing a power distribution plan
  • helping to build the robot

Software Designer - this position is typically based around the software and control design requirements of the robot. The designer might be responsible for:

  • researching and implementing navigation algorithms
  • testing and interfacing sensors with the HandyBoard
  • designing and implementing strategy (very, very tough)
  • helping to build the robot

Manager & Systems Designer - this position is typically based around the team management and systems interface design requirement of the robot. The manager & systems designer might be responsible for:

  • organizing team meetings, tracking budgets, raising money
  • planning strategies, deciding on time & effort initiatives
  • designing and interfacing components and sensors
  • helping to build the robot

It is important to note that all students will contribute to areas outside their selected field of expertise. For example, the software designer will definitely be expected to lend a hand soldering, measuring, and testing. The electrical designer may be required to write some assembly language code to interface with a particular sensor.


 
 
Main Page
|
Course Admin
|
Course Resources
|
Rules & Regulations
|
Team Profiles
|
Photo Gallery
|
Contact Info