RoboWiki - Recent changes [en]

Rambler

2010-09-09T17:16:13Z

Team Members:

← Older revision		Revision as of 17:16, 9 September 2010
(One intermediate revision not shown)
Line 12:		Line 12:

	= Current Tasks =		= Current Tasks =
-	* Remove the Propeller and use the Arduino Mega microcontroller	+	* Week 1:
-	* Verify all servos correctly move	+	** Clean chassis (Remove gunk, stickers, unneeded hardware)
-	* Verify wiring	+	** Repair any mechanical failures (fix joins, tighten bolts, etc)
-	* Create the sensor "head" (a rotating head that has both range and light sensors)	+	** [http://todbot.com/blog/2009/04/11/tiny-servos-as-continuous-rotation-gearmotors/ Modify a continuous servo] to give a position / resistance ratio
-	* Redo the padded / rubber foot pads	+	** Move three of the six legs using an Arduino
-	* Clean surface, but do not repaint	+	* Week 2:
-	* Remove buttons / high-leg state sensors	+	** Make sure we can get a reliable analog value feed-back from a continuos servo
-	* Create a sensor / head package	+	** Interface with an Arduino Mega
-	* Put out the flame using the solenoid / compressed air technology	+	* Genearl Tasks
-	* Implement a wall following	+	** Remove the Propeller and use the Arduino Mega microcontroller
-	* Have a remote control option	+	** Verify all servos correctly move
-	* Have wireless control	+	** Verify wiring
-	* Implement a zero-degree turn	+	** Create the sensor "head" (a rotating head that has both range and light sensors)
-	* Find a servo controller that can support all major servos	+	** Redo the padded / rubber foot pads
-	* Find a good power management utility	+	** Clean surface, but do not repaint
		+	** Remove buttons / high-leg state sensors
		+	** Create a sensor / head package
		+	** Put out the flame using the solenoid / compressed air technology
		+	** Implement a wall following
		+	** Have a remote control option
		+	** Have wireless control
		+	** Implement a zero-degree turn
		+	** Find a servo controller that can support all major servos
		+	** Find a good power management utility

		+	= Team Members =
		+	* [[Jillian Newhall]]
		+	* [[Jeremy Bridon]]
		+	* ''More...''
	[[Category:Hardware]]		[[Category:Hardware]]

IGVC Developer's Guide

2010-09-09T01:13:47Z

Installing Player from Repositories:

← Older revision		Revision as of 01:13, 9 September 2010
Line 36:		Line 36:
	This command will download Player and Stage, as well as all of the dependencies and development libraries required to program for and run Player. To compile our code, you'll need a few extra programs. The following packages should provide the rest of the dependancies needed for our code.		This command will download Player and Stage, as well as all of the dependencies and development libraries required to program for and run Player. To compile our code, you'll need a few extra programs. The following packages should provide the rest of the dependancies needed for our code.

-	<pre>su -c "yum install cmake opencv-devel gtk2-devel"</pre>	+	<pre>su -c "yum install cmake opencv-devel gtk2-devel gearbox-devel"</pre>

	== Installing Player from Source ==		== Installing Player from Source ==

Starcraft 2 Tournament

2010-09-08T01:16:13Z

Participant Roster:

← Older revision		Revision as of 01:16, 8 September 2010
Line 28:		Line 28:
	''Add your full name, game name, and the race (or random) you will be playing as''		''Add your full name, game name, and the race (or random) you will be playing as''
	* Jeremy Bridon - Maudit - Terran		* Jeremy Bridon - Maudit - Terran
-	* Ivo Pavlov - ~~ClumsyPyro101~~ - Zerg	+	* Ivo Pavlov - ClumsyPyro - Zerg
	* ''Etc...''		* ''Etc...''

Starcraft 2 Tournament

2010-09-08T01:03:40Z

Created page with 'The Penn State Robotics Club will be hosting an open Starcraft 2 tournament on October 16th (Saturday) 2010 as a club social event. All are welcomed to enter the competition, clu…'

New page

The Penn State Robotics Club will be hosting an open Starcraft 2 tournament on October 16th (Saturday) 2010 as a club social event. All are welcomed to enter the competition, club member or not. Tell your friends and family; you can even remotely play the game! There might be free food and drinks. Winners simply get the reward of being awesome; the club can't afford giving out prizes outside of official club competitions. If patch 1.1 is not out by the time of the event, we will delay it until its official release for balancing reasons.

If you would like to register, please contact [[Jeremy Bridon]] or simply add yourself to the list! '''YOU MUST''' register at least 30 minutes before the competition! '''No exception'''

The event manager / staff will be [[Jeremy Bridon]], but is not a referee. Contact him if you have questions / issues.

= Competition Rules =
''Please read these carefully:''
* General Rules:
** Tournament will start at 2:30 pm in Hammond room 312 on October 16th
** Open to the public - anyone can register!
** Must register a minimum of 30 minutes before the competition
** You must declare a race (or random) when registering
** You must give us (the tournament staff) your friend code
** No Starcraft: BroodWar support, though you are more than welcomed to play some with friends in the same room!
* Game Rules:
** All matches are 1v1
** Winners of each match is based on a "best of three" round-scheme
** Headphones & mice are recommended, but not required
** Active players must play outside of the main tournament room - this is to prevent "screen peeking"
** Active players cannot be given advice during a match - friends may not shout suggestions
* Special Rules:
** No cheating - we reserve the right for disqualification without justification for possible cheating
** No bad behavior - we reserve the right for disqualification without justification for bad behavior / poor sportsmanship
** Be polite - not a rule, just a general note

= Participant Roster =
''Add your full name, game name, and the race (or random) you will be playing as''
* Jeremy Bridon - Maudit - Terran
* Ivo Pavlov - ClumsyPyro101 - Zerg
* ''Etc...''

WalkerBot

2010-09-06T21:06:09Z

Current Tasks:

← Older revision		Revision as of 21:06, 6 September 2010
(One intermediate revision not shown)
Line 34:		Line 34:
	*** Good example of a Cad-based solution: http://i187.photobucket.com/albums/x228/ncabalos/legConfig.jpg		*** Good example of a Cad-based solution: http://i187.photobucket.com/albums/x228/ncabalos/legConfig.jpg
	*** The above implementation in hardware: http://www.hbrobotics.org/wiki/index.php5/Image:QUAD20b.jpg		*** The above implementation in hardware: http://www.hbrobotics.org/wiki/index.php5/Image:QUAD20b.jpg
		+	*** Most flexible system seen thus far: http://www.hexapodrobot.com/forum/viewtopic.php?f=11&t=331
		+	*** High-torque robot: http://www.youtube.com/watch?v=guM1tXfgIjw&feature=related
	* Prototype in some AutoCAD - Start sketching models up		* Prototype in some AutoCAD - Start sketching models up
	** ''In progress''		** ''In progress''

Capture The Flag

2010-09-06T19:37:17Z

← Older revision		Revision as of 19:37, 6 September 2010
(One intermediate revision not shown)
Line 1:		Line 1:
-	[[Image:~~Arena2008~~.~~jpg~~\|~~frame~~\|The ~~2008~~ Arena Layout. ~~Not yet finalized~~.]]	+	[[Image:Arena2010.png\|thumb\|The 2010 Arena Layout. Source file can be found [http://psurobotics.org/files/CTFMaze.psd here].]]
	''Contest will be hosted at the end of Fall 2010.''		''Contest will be hosted at the end of Fall 2010.''

Line 8:		Line 8:
	== General Rules ==		== General Rules ==

-	[[Image:Flag.png\|frame\|left\|The 2007 Flag Design]]	+	[[Image:Flag.png\|frame\|left\|The 2007 Flag Design - the 2010 flag will be better designed, but will retain the same shape.]]
-	# '''General Rules:''' Each robot will be given two time trials, each lasting a maximum of 3 minutes. The robot will start in its base and try to successfully get into the opposite base, recover a flag, and return the flag to its base. If this is completed in less than the allotted time, the fastest robot will win. Otherwise, the team that acquires the most points will be victorious. Details of scoring can be found in the "General Bonuses and Deductions" section.	+	# '''General Rules:''' Each robot will be given two time trials, each lasting a maximum of 5 minutes. The robot will start in its base and try to successfully get into the opposite base, recover a flag, and return the flag to its base. If this is completed in less than the allotted time, the fastest robot will win. Otherwise, the team that acquires the most points will be victorious. Details of scoring can be found in the "General Bonuses and Deductions" section.
	# '''Robot Size:''' While in its starting position, the robot must exceed no more than 12" in height, 12" in length, and 12" in width. At any point during the competition, the robot must not exceed 18" by 18" by 18". Failure to adhere will result in disqualification for the round. There is no weight restriction.		# '''Robot Size:''' While in its starting position, the robot must exceed no more than 12" in height, 12" in length, and 12" in width. At any point during the competition, the robot must not exceed 18" by 18" by 18". Failure to adhere will result in disqualification for the round. There is no weight restriction.
	# '''Robot Starting Position:''' The robot must always start fully inside its home base, facing any direction. See "Arena" for base size and location. It cannot start while in contact with the flag.		# '''Robot Starting Position:''' The robot must always start fully inside its home base, facing any direction. See "Arena" for base size and location. It cannot start while in contact with the flag.
Line 17:		Line 17:
	# '''Modification between Rounds:''' Robots maybe be re-programmed or modified in any way between rounds. Table space (however limited) will be available at the site of the competition.		# '''Modification between Rounds:''' Robots maybe be re-programmed or modified in any way between rounds. Table space (however limited) will be available at the site of the competition.
	# '''Restricted Areas:''' A robot may not exit the arena at any time during competition.		# '''Restricted Areas:''' A robot may not exit the arena at any time during competition.
-		+	# '''Flag Placement:''' The flag may be placed in either the standard location (see the 2010 CTF Maze Design image), but can be moved directly between the ramps for an "easier level" of difficulty. If a team chooses to do this, a 40 second penalty will be added to the total time.

	== Time Trial ==		== Time Trial ==

File:Arena2010.png

2010-09-06T19:32:37Z

uploaded "[[File:Arena2010.png]]"

New page

Anthony Cascone

2010-09-06T00:22:18Z

← Older revision		Revision as of 00:22, 6 September 2010
Line 1:		Line 1:
-	''Last updated ~~May 6th~~, ~~2008~~''	+	''Last updated September 5th, 2010''

	[[Image:ACHeadshot.jpg\|frame\|I need an updated picture]]		[[Image:ACHeadshot.jpg\|frame\|I need an updated picture]]
-	I joined the club in 2005 and served as the secretary for that year. The year after, I had the opportunity to help the club as the president with the focus of building membership. I lucked out that year by having a great group of students join the club and take charge. At the end of my term as president, I graduated and applied to grad school at Penn State and continued to support the club during my first year as a ~~master~~ student.	+	I joined the club in 2005 and served as the secretary for that year. The year after, I had the opportunity to help the club as the president with the focus of building membership. I lucked out that year by having a great group of students join the club and take charge. At the end of my term as president, I graduated and applied to grad school at Penn State and continued to support the club during my first year as a masters student.

	== General Information ==		== General Information ==
Line 10:		Line 10:
	* Projects:		* Projects:
	** [[Mini Grand Challenge]]		** [[Mini Grand Challenge]]
-	** AUVSI [[IGVC]]	+	** AUVSI [[IGVC]] 2008, 2009, 2010, 2011.
	** New Student Recruitment/Education		** New Student Recruitment/Education

	* Office:		* Office:
-	** ~~104 Engineering Unit C~~	+	** 16 Applied Science Building

	* Website:		* Website:

WalkerBot

2010-09-05T21:10:21Z

← Older revision		Revision as of 21:10, 5 September 2010
(One intermediate revision not shown)
Line 6:		Line 6:
	WalkerBot is a four-legged (quadruped robot) [[Tabletop Robotics\|table-top robot]] used for generic applications & research. The goal is to make it an open-source hardware and software design, such that it is fully reproducible. It also uses current proven technologies developed within the club, such as the [[Arduino]] microcontroller to keep things as simple as possible.		WalkerBot is a four-legged (quadruped robot) [[Tabletop Robotics\|table-top robot]] used for generic applications & research. The goal is to make it an open-source hardware and software design, such that it is fully reproducible. It also uses current proven technologies developed within the club, such as the [[Arduino]] microcontroller to keep things as simple as possible.

-	[[Image:Design1_WalkerBot.png\|~~frame~~\|Solid view of the prototype robot.]]	+	[[Image:Design1_WalkerBot.png\|thumb\|Solid view of the prototype robot.]]

-	[[Image:Design2_WalkerBot.png\|~~frame~~\|X-Ray view internals of the prototype robot.]]	+	[[Image:Design2_WalkerBot.png\|thumb\|X-Ray view internals of the prototype robot.]]

	= Project Goals =		= Project Goals =

File:Design2 WalkerBot.png

2010-09-05T20:59:53Z

uploaded a new version of "[[File:Design2 WalkerBot.png]]"

New page

File:Design1 WalkerBot.png

2010-09-05T20:59:47Z

uploaded a new version of "[[File:Design1 WalkerBot.png]]"

New page

File:Design2 WalkerBot.png

2010-09-05T20:56:28Z

uploaded "[[File:Design2 WalkerBot.png]]"

New page

WalkerBot

2010-09-05T20:56:09Z

Description:

← Older revision		Revision as of 20:56, 5 September 2010
Line 5:		Line 5:
	= Description =		= Description =
	WalkerBot is a four-legged (quadruped robot) [[Tabletop Robotics\|table-top robot]] used for generic applications & research. The goal is to make it an open-source hardware and software design, such that it is fully reproducible. It also uses current proven technologies developed within the club, such as the [[Arduino]] microcontroller to keep things as simple as possible.		WalkerBot is a four-legged (quadruped robot) [[Tabletop Robotics\|table-top robot]] used for generic applications & research. The goal is to make it an open-source hardware and software design, such that it is fully reproducible. It also uses current proven technologies developed within the club, such as the [[Arduino]] microcontroller to keep things as simple as possible.
		+
		+	[[Image:Design1_WalkerBot.png\|frame\|Solid view of the prototype robot.]]
		+
		+	[[Image:Design2_WalkerBot.png\|frame\|X-Ray view internals of the prototype robot.]]

	= Project Goals =		= Project Goals =

Rambler

2010-09-05T19:53:32Z

← Older revision		Revision as of 19:53, 5 September 2010
(One intermediate revision not shown)
Line 1:		Line 1:
		+	Rambler was created by [[Dan Magagnosc]] and [[Andy Wilson]] in 2008 for the Firefighting Robot Competition in the Walking Division. It won third place in its division and the Versa valve challenge for that year. You can see a video of it in the competition [http://www.youtube.com/watch?v=jnUatnY1jQo here in Trinity].
	[[Image:Rambler.png\|frame\|Rambler at the Trinity event.]]		[[Image:Rambler.png\|frame\|Rambler at the Trinity event.]]
-	~~Rambler was created by Dan and Andy in 2008 for the Firefighting Robot Competition in the Walking Division. It won third place in its division and the Versa valve challenge.~~

-	[~~http://www~~.~~youtube.com/watch?v=jnUatnY1jQo Video: Testing Rambler~~]	+	The robot is officially becoming the club's [[Trinity Firefighting Competition]] legacy robot. [[Jeremy Bridon]] will be leading the legacy team for the 2010-2011 academic year along with the side research project [[WalkerBot]].

		+	= Description =
		+
		+	Ramber is a six-legged robot whose two front and back have two degrees of freedom, while the middle two legs only have one. The robot was designed for simplicity and consistent movement. The device is contained within a cubic foot and used to be controlled by a Parallax Propeller, but is now being interfaced with an [[Arduino]] Mega. In total, there are ten (10) continuous servos.
		+
		+	= Project Goals =
		+	Rambler, for 2010-2011, must accomplish all of the following goals: '''win''', '''cheap''', '''stable''', and '''easily reproducible'''!
		+
		+	= Current Tasks =
		+	* Remove the Propeller and use the Arduino Mega microcontroller
		+	* Verify all servos correctly move
		+	* Verify wiring
		+	* Create the sensor "head" (a rotating head that has both range and light sensors)
		+	* Redo the padded / rubber foot pads
		+	* Clean surface, but do not repaint
		+	* Remove buttons / high-leg state sensors
		+	* Create a sensor / head package
		+	* Put out the flame using the solenoid / compressed air technology
		+	* Implement a wall following
		+	* Have a remote control option
		+	* Have wireless control
		+	* Implement a zero-degree turn
		+	* Find a servo controller that can support all major servos
		+	* Find a good power management utility

	[[Category:Hardware]]		[[Category:Hardware]]

WalkerBot

2010-09-05T19:50:27Z

← Older revision		Revision as of 19:50, 5 September 2010
(One intermediate revision not shown)
Line 8:		Line 8:
	= Project Goals =		= Project Goals =

-	WalkerBot must accomplish all of the following goals: '''cheap''', '''stable''', and '''easily reproducible'''!	+	WalkerBot must accomplish all of the following goals: '''win''', '''cheap''', '''stable''', and '''easily reproducible'''!
	* Open-source hardware and software (Similar to the Arduino platform)		* Open-source hardware and software (Similar to the Arduino platform)
	* Cheap, targeting $250 US per robot instance		* Cheap, targeting $250 US per robot instance
Line 18:		Line 18:
	* Least amount of servos needed		* Least amount of servos needed
	* "Off the shelf" materials		* "Off the shelf" materials
		+	* Create the sensor "head" (a rotating head that has both range and light sensors)

	= Current Tasks =		= Current Tasks =

User:Barkerlaidora4flb

2010-09-03T05:25:18Z

New user account

New page

User:Whisperbrand10e7

2010-09-03T03:26:37Z

New user account

New page

User:Tyleraxerunnere4pn

2010-09-03T01:28:33Z

New user account

New page

User:Runeredeemerdelgadohm0e

2010-09-02T23:29:17Z

New user account

New page

User:Chasebludbearerutzm

2010-09-02T21:28:38Z

New user account

New page

User:Doomhammerco6g

2010-09-02T19:26:18Z

New user account

New page

User:Bloodbrewmr3m

2010-09-02T17:20:25Z

New user account

New page

User:Saithirim1980b2mr

2010-09-02T15:06:40Z

New user account

New page