Difference between revisions of "RunBot: a Robogame Robot"

From AIRWiki
Jump to: navigation, search
m
m
Line 23: Line 23:
 
* January 2011: vision implemented, robogame implemented.
 
* January 2011: vision implemented, robogame implemented.
 
* March 2011 Robogame tests.
 
* March 2011 Robogame tests.
 
==== Schedule ====
 
 
* June 2011 Thesis draft.
 
* June 2011 Thesis draft.
 +
 +
 +
{{#ev:youtube|B9Um3ZY3bL4}}
 +
 +
*[http://www.youtube.com/watch?v=B9Um3ZY3bL4 External link]
 +
 +
<iframe width="425" height="349" src="http://www.youtube.com/embed/B9Um3ZY3bL4?hl=en&fs=1" frameborder="0" allowfullscreen></iframe>

Revision as of 15:21, 15 July 2011

RunBot: Robogame Robot Development
Image of the project RunBot: a Robogame Robot
Short Description: Development of a robot suitable to implement highly interactive robogames in a home environment
Coordinator: AndreaBonarini (andrea.bonarini@polimi.it)
Tutor: AndreaBonarini (andrea.bonarini@polimi.it)
Collaborator: MartinoMigliavacca (migliavacca@elet.polimi.it)
Students: AnilKoyuncu (koyuncua@yahoo.com)
Research Area: Robotics
Research Topic: Robot development, Robogames
Start: 2010/01/11
End: 2011/08/22
Status: Active
Level: Ms
Type: Thesis

Aim of this project is the development of a robot suitable to implement highly interactive robogames in a home environment. This will be used in the Robogames research line to implement even more interesting games. This is also an experiment in the new development line of research, where user needs and costs are considered as a primary source for specification to guide robot development.

Status

  • July 2010: robot designed, mice odometry designed and partially tested,
  • August 2010: mechanical basis implemented
  • November 2010: controller implemented, smart camera installed, mice odometry implemented and installed.
  • January 2011: vision implemented, robogame implemented.
  • March 2011 Robogame tests.
  • June 2011 Thesis draft.


<iframe width="425" height="349" src="http://www.youtube.com/embed/B9Um3ZY3bL4?hl=en&fs=1" frameborder="0" allowfullscreen></iframe>