2012:Shooter and Collector 01.15 - Revision history

Programming: added link to comparison between drag

2012-01-16T01:20:37Z

added link to comparison between drag

← Older revision		Revision as of 17:20, 15 January 2012
Line 5:		Line 5:
	'''End time:'''		'''End time:'''

	'''Members present:''' Alex W, Mike M, Alex R, Mollie, Ciana, Matthieu, Jake, Danny, Manuel,		'''Members present:''' Alex W, Mike M, Alex R, Mollie, Ciana, Matthieu, Jake, Danny, Manuel,

	'''Members Attending Next Meeting:'''		'''Members Attending Next Meeting:'''
Line 27:		Line 27:
	**With 70 degree shooting angle, the robot would be able to shoot from the fender, key and mid-field with a variable shooting speed of 5-12 m/sec. You can score from any of these positions on any of the three hoop levels with the exception of the top hoop from the fender.		**With 70 degree shooting angle, the robot would be able to shoot from the fender, key and mid-field with a variable shooting speed of 5-12 m/sec. You can score from any of these positions on any of the three hoop levels with the exception of the top hoop from the fender.
	**With the turret placed 30 inches off the ground and 32 inches from the front of the robot, the shooter would need a minimum angle of 47 degrees to shoot over a defending robot of a height of 60 inches.		**With the turret placed 30 inches off the ground and 32 inches from the front of the robot, the shooter would need a minimum angle of 47 degrees to shoot over a defending robot of a height of 60 inches.
	*Projectile Sim		*Projectile Sim
	**Cleaned up code, made it easier to put a trajectory into Excel.		**Cleaned up code, made it easier to put a trajectory into Excel.
	**Comparison between drag and draglessness []		**Comparison between drag and draglessness [http://www.penfieldrobotics.com/wiki/images/0/0c/Bedraggled_v_Dragless.xls Comparison spreadsheet]

	= Materials Needed =		= Materials Needed =

Programming: projectile sim update

2012-01-16T01:15:38Z

projectile sim update

← Older revision		Revision as of 17:15, 15 January 2012
Line 1:		Line 1:
	= Attendance =		= Attendance =

	'''Start time:''' 10:00		'''Start time:''' 10:00

	'''End time:'''		'''End time:'''

	'''Members present:''' Alex W, Mike M, Alex R, Mollie, Ciana, Matthieu, Jake, Danny		'''Members present:''' Alex W, Mike M, Alex R, Mollie, Ciana, Matthieu, Jake, Danny, Manuel,

	'''Members Attending Next Meeting:'''		'''Members Attending Next Meeting:'''
Line 11:		Line 11:
	= Tasks Completed =		= Tasks Completed =

	*Planned conveyor path		*Planned conveyor path
	*Must go over drive train motors		*Must go over drive train motors
	*Looked at hand off between stage three of conveyor and shooter (Mind the Gap!)		*Looked at hand off between stage three of conveyor and shooter (Mind the Gap!)
	*Tasks In Progress		*Tasks In Progress

Line 27:		Line 27:
	**With 70 degree shooting angle, the robot would be able to shoot from the fender, key and mid-field with a variable shooting speed of 5-12 m/sec. You can score from any of these positions on any of the three hoop levels with the exception of the top hoop from the fender.		**With 70 degree shooting angle, the robot would be able to shoot from the fender, key and mid-field with a variable shooting speed of 5-12 m/sec. You can score from any of these positions on any of the three hoop levels with the exception of the top hoop from the fender.
	**With the turret placed 30 inches off the ground and 32 inches from the front of the robot, the shooter would need a minimum angle of 47 degrees to shoot over a defending robot of a height of 60 inches.		**With the turret placed 30 inches off the ground and 32 inches from the front of the robot, the shooter would need a minimum angle of 47 degrees to shoot over a defending robot of a height of 60 inches.
	*~~task~~		*Projectile Sim
			**Cleaned up code, made it easier to put a trajectory into Excel.
			**Comparison between drag and draglessness []

	= Materials Needed =		= Materials Needed =

Mechanical1 at 00:39, 16 January 2012

2012-01-16T00:39:39Z

← Older revision		Revision as of 16:39, 15 January 2012
Line 1:		Line 1:
	= Attendance =		= Attendance =

	'''Start time:'''		'''Start time:''' 10:00

	'''End time:'''		'''End time:'''

	'''Members present:'''		'''Members present:''' Alex W, Mike M, Alex R, Mollie, Ciana, Matthieu, Jake, Danny

	'''Members Attending Next Meeting:'''		'''Members Attending Next Meeting:'''
Line 11:		Line 11:
	= Tasks Completed =		= Tasks Completed =

	*~~task~~		*Planned conveyor path
	**sub-task		*Must go over drive train motors
	**sub-task		*Looked at hand off between stage three of conveyor and shooter (Mind the Gap!)
	*~~task~~		*Tasks In Progress

	= Tasks In Progress =

	*Beater bar requirements <br>Fixed position inside the frame/ stationary position <br>1 speed forward, 1 speed reverse (not full speed?) <br>measurements (must stay inside the frame) <br>As close to frame perimeter as possible, preferably coincident with it <br>Material ideas: Wheel traction tread, drawer liner, surgical tubing wrapped about the bar <br>Sturdy and easily replaceable (under five minutes to replace it) <br>Inside the frame or deployable? MUST BE INSIDE SEE #1<br>Sensor feedback; <br>Ball sensor - know when one is entering the system -- possibly? Depends on how close we can get one for the conveyers<br>NO status of spinning depends on # of balls currently in feeder, and whether there is a ball in front of robot. (accuracy?)<br>DOESN'T MATTER AT THIS POINT Should beater bar spin constantly if there are less than 3 balls in robot, or only spin if < 3 balls and there is a ball in front of robot?<br>		*Beater bar requirements <br>Fixed position inside the frame/ stationary position <br>1 speed forward, 1 speed reverse (not full speed?) <br>measurements (must stay inside the frame) <br>As close to frame perimeter as possible, preferably coincident with it <br>Material ideas: Wheel traction tread, drawer liner, surgical tubing wrapped about the bar <br>Sturdy and easily replaceable (under five minutes to replace it) <br>Inside the frame or deployable? MUST BE INSIDE SEE #1<br>Sensor feedback; <br>Ball sensor - know when one is entering the system -- possibly? Depends on how close we can get one for the conveyers<br>NO status of spinning depends on # of balls currently in feeder, and whether there is a ball in front of robot. (accuracy?)<br>DOESN'T MATTER AT THIS POINT Should beater bar spin constantly if there are less than 3 balls in robot, or only spin if < 3 balls and there is a ball in front of robot?<br>

Mechanical1 at 20:16, 15 January 2012

2012-01-15T20:16:54Z

← Older revision		Revision as of 12:16, 15 January 2012
Line 18:		Line 18:
	= Tasks In Progress =		= Tasks In Progress =

	*Beater bar requirements ~~<br>~~<br>Fixed position inside the frame/ stationary position <br>1 speed forward, 1 speed reverse (not full speed?) <br>measurements (must stay inside the frame) <br>As close to frame perimeter as possible, preferably coincident with it <br>Material ideas: Wheel traction tread, drawer liner, surgical tubing wrapped about the bar <br>Sturdy and easily replaceable (under five minutes to replace it) <br>Inside the frame or deployable? MUST BE INSIDE SEE #1<br>Sensor feedback; <br>Ball sensor - know when one is entering the system -- possibly? Depends on how close we can get one for the conveyers<br>NO status of spinning depends on # of balls currently in feeder, and whether there is a ball in front of robot. (accuracy?)<br>DOESN'T MATTER AT THIS POINT Should beater bar spin constantly if there are less than 3 balls in robot, or only spin if < 3 balls and there is a ball in front of robot?<br>		*Beater bar requirements <br>Fixed position inside the frame/ stationary position <br>1 speed forward, 1 speed reverse (not full speed?) <br>measurements (must stay inside the frame) <br>As close to frame perimeter as possible, preferably coincident with it <br>Material ideas: Wheel traction tread, drawer liner, surgical tubing wrapped about the bar <br>Sturdy and easily replaceable (under five minutes to replace it) <br>Inside the frame or deployable? MUST BE INSIDE SEE #1<br>Sensor feedback; <br>Ball sensor - know when one is entering the system -- possibly? Depends on how close we can get one for the conveyers<br>NO status of spinning depends on # of balls currently in feeder, and whether there is a ball in front of robot. (accuracy?)<br>DOESN'T MATTER AT THIS POINT Should beater bar spin constantly if there are less than 3 balls in robot, or only spin if < 3 balls and there is a ball in front of robot?<br>
	**Wings / bridge requirements <br>Are solid/straight from tip back to frame edge to prevent balls from getting trapped behind, and prevent outward bending <br>Starts within the frame perimeter, and deploys to outside the frame perimeter <br>Has no active gathering mechanism -- just simple wings <br>Enables to retreive balls from wall and corners - Guide the balls to the beater bar without moving <br>But CORNER is a big problem with wings down; coming in perpendicular to a wall is difficult as well<br>Able to lower a ramp from its balanced position to a position low enough for us to climb <br><br>Deploys and retracts in under 2 seconds (Motor / Pneumatic?) <br><br>Sturdy and easily replaceable (under five minutes to replace it) <br>Sensor feedback; <br>Could mount sensor for sensing ball in front of robot, only if beater bar should not spin constantly --- probably not necessary -- battery power drain will be limited on brush -- also very dangerous<br>/ If motor operated: Detecting if wings are all the way down (if (sensorOn == true) stop motor to lower wings)<br>(accuracy of sensors?)<br>Limit switches or similar for actuation limits (if not using pneumatics)<br>Position sensor on the actuation axel (get wing's angle of deployment, if driven by motor)<br>		**Wings / bridge requirements <br>Are solid/straight from tip back to frame edge to prevent balls from getting trapped behind, and prevent outward bending <br>Starts within the frame perimeter, and deploys to outside the frame perimeter <br>Has no active gathering mechanism -- just simple wings <br>Enables to retreive balls from wall and corners - Guide the balls to the beater bar without moving <br>But CORNER is a big problem with wings down; coming in perpendicular to a wall is difficult as well<br>Able to lower a ramp from its balanced position to a position low enough for us to climb <br><br>Deploys and retracts in under 2 seconds (Motor / Pneumatic?) <br><br>Sturdy and easily replaceable (under five minutes to replace it) <br>Sensor feedback; <br>Could mount sensor for sensing ball in front of robot, only if beater bar should not spin constantly --- probably not necessary -- battery power drain will be limited on brush -- also very dangerous<br>/ If motor operated: Detecting if wings are all the way down (if (sensorOn == true) stop motor to lower wings)<br>(accuracy of sensors?)<br>Limit switches or similar for actuation limits (if not using pneumatics)<br>Position sensor on the actuation axel (get wing's angle of deployment, if driven by motor)<br>
	**Conveyor requirements		**Conveyor requirements
Line 26:		Line 26:

	*<br>Camera:<br>location for camera on turret for targeting<br>Tasks to Complete		*<br>Camera:<br>location for camera on turret for targeting<br>Tasks to Complete
	*Math model		*Math model
	**With 70 degree shooting angle, the robot would be able to shoot from the fender, key and mid-field with a variable shooting speed of 5-12 m/sec. You can score from any of these positions on any of the three hoop levels with the exception of the top hoop from the fender.		**With 70 degree shooting angle, the robot would be able to shoot from the fender, key and mid-field with a variable shooting speed of 5-12 m/sec. You can score from any of these positions on any of the three hoop levels with the exception of the top hoop from the fender.
	**With the turret placed 30 inches off the ground and 32 inches from the front of the robot, the shooter would need a minimum angle of 47 degrees to shoot over a defending robot of a height of 60 inches.		**With the turret placed 30 inches off the ground and 32 inches from the front of the robot, the shooter would need a minimum angle of 47 degrees to shoot over a defending robot of a height of 60 inches.
	*task		*task

Mechanical1 at 19:55, 15 January 2012

2012-01-15T19:55:29Z

← Older revision		Revision as of 11:55, 15 January 2012
Line 23:		Line 23:
	**Work around the drivetrain components<br>contain no more than 3 balls<br>3 separate segments independantly controlled<br>speeds at shooter must be very consistent<br>transport ball through conveyor for X amount of time + capability of reverse direction (?)<br>Sensor feedback; 1 on each conveyor belt + 1 at entrance to feeder to avoid accidents. (accuracy?)<br>		**Work around the drivetrain components<br>contain no more than 3 balls<br>3 separate segments independantly controlled<br>speeds at shooter must be very consistent<br>transport ball through conveyor for X amount of time + capability of reverse direction (?)<br>Sensor feedback; 1 on each conveyor belt + 1 at entrance to feeder to avoid accidents. (accuracy?)<br>
	*Turret:<br>280° of rotation minimum<br>+/- 1° precision<br>receive balls from conveyor<br>mechanical hardstops		*Turret:<br>280° of rotation minimum<br>+/- 1° precision<br>receive balls from conveyor<br>mechanical hardstops
	*<br>Shooter:<br>impart backspin (~~variable~~?)<br>2 independent wheels		*<br>Shooter:<br>impart backspin (fixed?)<br>2 independent wheels

	*<br>Camera:<br>location for camera on turret for targeting<br>Tasks to Complete		*<br>Camera:<br>location for camera on turret for targeting<br>Tasks to Complete
	*~~task~~		*Math model
	**~~sub~~-~~task~~		**With 70 degree shooting angle, the robot would be able to shoot from the fender, key and mid-field with a variable shooting speed of 5-12 m/sec. You can score from any of these positions on any of the three hoop levels with the exception of the top hoop from the fender.
	**~~sub-task~~		**With the turret placed 30 inches off the ground and 32 inches from the front of the robot, the shooter would need a minimum angle of 47 degrees to shoot over a defending robot of a height of 60 inches.
	*task		*task

Mechanical1 at 19:42, 15 January 2012

2012-01-15T19:42:26Z

← Older revision		Revision as of 11:42, 15 January 2012
Line 21:		Line 21:
	**Wings / bridge requirements <br>Are solid/straight from tip back to frame edge to prevent balls from getting trapped behind, and prevent outward bending <br>Starts within the frame perimeter, and deploys to outside the frame perimeter <br>Has no active gathering mechanism -- just simple wings <br>Enables to retreive balls from wall and corners - Guide the balls to the beater bar without moving <br>But CORNER is a big problem with wings down; coming in perpendicular to a wall is difficult as well<br>Able to lower a ramp from its balanced position to a position low enough for us to climb <br><br>Deploys and retracts in under 2 seconds (Motor / Pneumatic?) <br><br>Sturdy and easily replaceable (under five minutes to replace it) <br>Sensor feedback; <br>Could mount sensor for sensing ball in front of robot, only if beater bar should not spin constantly --- probably not necessary -- battery power drain will be limited on brush -- also very dangerous<br>/ If motor operated: Detecting if wings are all the way down (if (sensorOn == true) stop motor to lower wings)<br>(accuracy of sensors?)<br>Limit switches or similar for actuation limits (if not using pneumatics)<br>Position sensor on the actuation axel (get wing's angle of deployment, if driven by motor)<br>		**Wings / bridge requirements <br>Are solid/straight from tip back to frame edge to prevent balls from getting trapped behind, and prevent outward bending <br>Starts within the frame perimeter, and deploys to outside the frame perimeter <br>Has no active gathering mechanism -- just simple wings <br>Enables to retreive balls from wall and corners - Guide the balls to the beater bar without moving <br>But CORNER is a big problem with wings down; coming in perpendicular to a wall is difficult as well<br>Able to lower a ramp from its balanced position to a position low enough for us to climb <br><br>Deploys and retracts in under 2 seconds (Motor / Pneumatic?) <br><br>Sturdy and easily replaceable (under five minutes to replace it) <br>Sensor feedback; <br>Could mount sensor for sensing ball in front of robot, only if beater bar should not spin constantly --- probably not necessary -- battery power drain will be limited on brush -- also very dangerous<br>/ If motor operated: Detecting if wings are all the way down (if (sensorOn == true) stop motor to lower wings)<br>(accuracy of sensors?)<br>Limit switches or similar for actuation limits (if not using pneumatics)<br>Position sensor on the actuation axel (get wing's angle of deployment, if driven by motor)<br>
	**Conveyor requirements		**Conveyor requirements
	**Work around the drivetrain components<br>contain no more than 3 balls<br>3 separate segments independantly ~~controled~~<br>speeds at shooter must be very consistent<br>transport ball through conveyor for X amount of time + capability of reverse direction (?)<br>Sensor feedback; 1 on each conveyor belt + 1 at entrance to feeder to avoid accidents. (accuracy?)<br>		**Work around the drivetrain components<br>contain no more than 3 balls<br>3 separate segments independantly controlled<br>speeds at shooter must be very consistent<br>transport ball through conveyor for X amount of time + capability of reverse direction (?)<br>Sensor feedback; 1 on each conveyor belt + 1 at entrance to feeder to avoid accidents. (accuracy?)<br>
	*Turret:<br>280° of rotation<br>+/- 1° precision<br>receive balls from conveyor<br>mechanical hardstops		*Turret:<br>280° of rotation minimum<br>+/- 1° precision<br>receive balls from conveyor<br>mechanical hardstops
	*<br>Shooter:<br>impart backspin<br>2 independent wheels		*<br>Shooter:<br>impart backspin (variable?)<br>2 independent wheels
	*<br>Camera:<br>location for camera on turret for targeting<br>Tasks to Complete		*<br>Camera:<br>location for camera on turret for targeting<br>Tasks to Complete
	*task		*task

Mechanical1 at 17:42, 15 January 2012

2012-01-15T17:42:47Z

← Older revision		Revision as of 09:42, 15 January 2012
Line 20:		Line 20:
	*Beater bar requirements <br><br>Fixed position inside the frame/ stationary position <br>1 speed forward, 1 speed reverse (not full speed?) <br>measurements (must stay inside the frame) <br>As close to frame perimeter as possible, preferably coincident with it <br>Material ideas: Wheel traction tread, drawer liner, surgical tubing wrapped about the bar <br>Sturdy and easily replaceable (under five minutes to replace it) <br>Inside the frame or deployable? MUST BE INSIDE SEE #1<br>Sensor feedback; <br>Ball sensor - know when one is entering the system -- possibly? Depends on how close we can get one for the conveyers<br>NO status of spinning depends on # of balls currently in feeder, and whether there is a ball in front of robot. (accuracy?)<br>DOESN'T MATTER AT THIS POINT Should beater bar spin constantly if there are less than 3 balls in robot, or only spin if < 3 balls and there is a ball in front of robot?<br>		*Beater bar requirements <br><br>Fixed position inside the frame/ stationary position <br>1 speed forward, 1 speed reverse (not full speed?) <br>measurements (must stay inside the frame) <br>As close to frame perimeter as possible, preferably coincident with it <br>Material ideas: Wheel traction tread, drawer liner, surgical tubing wrapped about the bar <br>Sturdy and easily replaceable (under five minutes to replace it) <br>Inside the frame or deployable? MUST BE INSIDE SEE #1<br>Sensor feedback; <br>Ball sensor - know when one is entering the system -- possibly? Depends on how close we can get one for the conveyers<br>NO status of spinning depends on # of balls currently in feeder, and whether there is a ball in front of robot. (accuracy?)<br>DOESN'T MATTER AT THIS POINT Should beater bar spin constantly if there are less than 3 balls in robot, or only spin if < 3 balls and there is a ball in front of robot?<br>
	**Wings / bridge requirements <br>Are solid/straight from tip back to frame edge to prevent balls from getting trapped behind, and prevent outward bending <br>Starts within the frame perimeter, and deploys to outside the frame perimeter <br>Has no active gathering mechanism -- just simple wings <br>Enables to retreive balls from wall and corners - Guide the balls to the beater bar without moving <br>But CORNER is a big problem with wings down; coming in perpendicular to a wall is difficult as well<br>Able to lower a ramp from its balanced position to a position low enough for us to climb <br><br>Deploys and retracts in under 2 seconds (Motor / Pneumatic?) <br><br>Sturdy and easily replaceable (under five minutes to replace it) <br>Sensor feedback; <br>Could mount sensor for sensing ball in front of robot, only if beater bar should not spin constantly --- probably not necessary -- battery power drain will be limited on brush -- also very dangerous<br>/ If motor operated: Detecting if wings are all the way down (if (sensorOn == true) stop motor to lower wings)<br>(accuracy of sensors?)<br>Limit switches or similar for actuation limits (if not using pneumatics)<br>Position sensor on the actuation axel (get wing's angle of deployment, if driven by motor)<br>		**Wings / bridge requirements <br>Are solid/straight from tip back to frame edge to prevent balls from getting trapped behind, and prevent outward bending <br>Starts within the frame perimeter, and deploys to outside the frame perimeter <br>Has no active gathering mechanism -- just simple wings <br>Enables to retreive balls from wall and corners - Guide the balls to the beater bar without moving <br>But CORNER is a big problem with wings down; coming in perpendicular to a wall is difficult as well<br>Able to lower a ramp from its balanced position to a position low enough for us to climb <br><br>Deploys and retracts in under 2 seconds (Motor / Pneumatic?) <br><br>Sturdy and easily replaceable (under five minutes to replace it) <br>Sensor feedback; <br>Could mount sensor for sensing ball in front of robot, only if beater bar should not spin constantly --- probably not necessary -- battery power drain will be limited on brush -- also very dangerous<br>/ If motor operated: Detecting if wings are all the way down (if (sensorOn == true) stop motor to lower wings)<br>(accuracy of sensors?)<br>Limit switches or similar for actuation limits (if not using pneumatics)<br>Position sensor on the actuation axel (get wing's angle of deployment, if driven by motor)<br>
	**Conveyor requirements		**Conveyor requirements
	**Work around the drivetrain components<br>contain no more than 3 balls<br>3 separate segments independantly controled<br>speeds at shooter must be very consistent<br>transport ball through conveyor for X amount of time + capability of reverse direction (?)<br>Sensor feedback; 1 on each conveyor belt + 1 at entrance to feeder to avoid accidents. (accuracy?)<br>		**Work around the drivetrain components<br>contain no more than 3 balls<br>3 separate segments independantly controled<br>speeds at shooter must be very consistent<br>transport ball through conveyor for X amount of time + capability of reverse direction (?)<br>Sensor feedback; 1 on each conveyor belt + 1 at entrance to feeder to avoid accidents. (accuracy?)<br>
	*~~task~~		*Turret:<br>280° of rotation<br>+/- 1° precision<br>receive balls from conveyor<br>mechanical hardstops
			*<br>Shooter:<br>impart backspin<br>2 independent wheels
	= Tasks to Complete =		*<br>Camera:<br>location for camera on turret for targeting<br>Tasks to Complete

	*task		*task
	**sub-task		**sub-task

Mechanical1 at 17:41, 15 January 2012

2012-01-15T17:41:51Z

← Older revision		Revision as of 09:41, 15 January 2012
Line 1:		Line 1:
	= Attendance =		= Attendance =

	'''Start time:''' ~~10:00AM~~		'''Start time:'''

	'''End time:''' ~~9:00PM~~		'''End time:'''

	'''Members present:''' ~~Mike Montemalo, Cianna, Matthew~~		'''Members present:'''

	'''Members Attending Next Meeting:''' ~~Hopefully the same~~		'''Members Attending Next Meeting:'''

	= Tasks Completed =		= Tasks Completed =

	*~~Design Completed for Wing/actuator~~		*task
	*-Determine Motors
	*-Determine Start and match geometryTasks In Progress
	*Determine Material
	*-Lexan
	*-Sheet Metal
	*Beater bar requirements <br><br>Fixed position inside the frame/ stationary position <br>1 speed forward, 1 speed reverse (not full speed?) <br>measurements (must stay inside the frame) <br>As close to frame perimeter as possible, preferably coincident with it <br>Material ideas: Wheel traction tread, drawer liner, surgical tubing wrapped about the bar <br>Sturdy and easily replaceable (under five minutes to replace it) <br>Inside the frame or deployable? MUST BE INSIDE SEE #1<br>Sensor feedback; <br>Ball sensor - know when one is entering the system -- possibly? Depends on how close we can get one for the conveyers<br>NO status of spinning depends on # of balls currently in feeder, and whether there is a ball in front of robot. (accuracy?)<br>DOESN'T MATTER AT THIS POINT Should beater bar spin constantly if there are less than 3 balls in robot, or only spin if < 3 balls and there is a ball in front of robot?<br>
	**sub-task		**sub-task
	**sub-task		**sub-task
			*task

			= Tasks In Progress =

			*Beater bar requirements <br><br>Fixed position inside the frame/ stationary position <br>1 speed forward, 1 speed reverse (not full speed?) <br>measurements (must stay inside the frame) <br>As close to frame perimeter as possible, preferably coincident with it <br>Material ideas: Wheel traction tread, drawer liner, surgical tubing wrapped about the bar <br>Sturdy and easily replaceable (under five minutes to replace it) <br>Inside the frame or deployable? MUST BE INSIDE SEE #1<br>Sensor feedback; <br>Ball sensor - know when one is entering the system -- possibly? Depends on how close we can get one for the conveyers<br>NO status of spinning depends on # of balls currently in feeder, and whether there is a ball in front of robot. (accuracy?)<br>DOESN'T MATTER AT THIS POINT Should beater bar spin constantly if there are less than 3 balls in robot, or only spin if < 3 balls and there is a ball in front of robot?<br>
			**Wings / bridge requirements <br>Are solid/straight from tip back to frame edge to prevent balls from getting trapped behind, and prevent outward bending <br>Starts within the frame perimeter, and deploys to outside the frame perimeter <br>Has no active gathering mechanism -- just simple wings <br>Enables to retreive balls from wall and corners - Guide the balls to the beater bar without moving <br>But CORNER is a big problem with wings down; coming in perpendicular to a wall is difficult as well<br>Able to lower a ramp from its balanced position to a position low enough for us to climb <br><br>Deploys and retracts in under 2 seconds (Motor / Pneumatic?) <br><br>Sturdy and easily replaceable (under five minutes to replace it) <br>Sensor feedback; <br>Could mount sensor for sensing ball in front of robot, only if beater bar should not spin constantly --- probably not necessary -- battery power drain will be limited on brush -- also very dangerous<br>/ If motor operated: Detecting if wings are all the way down (if (sensorOn == true) stop motor to lower wings)<br>(accuracy of sensors?)<br>Limit switches or similar for actuation limits (if not using pneumatics)<br>Position sensor on the actuation axel (get wing's angle of deployment, if driven by motor)<br>
			**Conveyor requirements
			**Work around the drivetrain components<br>contain no more than 3 balls<br>3 separate segments independantly controled<br>speeds at shooter must be very consistent<br>transport ball through conveyor for X amount of time + capability of reverse direction (?)<br>Sensor feedback; 1 on each conveyor belt + 1 at entrance to feeder to avoid accidents. (accuracy?)<br>
	*task		*task

Mechanical1 at 17:41, 15 January 2012

2012-01-15T17:41:14Z

← Older revision		Revision as of 09:41, 15 January 2012
Line 1:		Line 1:
	= Attendance =		= Attendance =

	'''Start time:'''		'''Start time:''' 10:00AM

	'''End time:'''		'''End time:''' 9:00PM

	'''Members present:'''		'''Members present:''' Mike Montemalo, Cianna, Matthew

	'''Members Attending Next Meeting:'''		'''Members Attending Next Meeting:''' Hopefully the same

	= Tasks Completed =		= Tasks Completed =

	*~~task~~		*Design Completed for Wing/actuator
			*-Determine Motors
			*-Determine Start and match geometryTasks In Progress
			*Determine Material
			*-Lexan
			*-Sheet Metal
			*Beater bar requirements <br><br>Fixed position inside the frame/ stationary position <br>1 speed forward, 1 speed reverse (not full speed?) <br>measurements (must stay inside the frame) <br>As close to frame perimeter as possible, preferably coincident with it <br>Material ideas: Wheel traction tread, drawer liner, surgical tubing wrapped about the bar <br>Sturdy and easily replaceable (under five minutes to replace it) <br>Inside the frame or deployable? MUST BE INSIDE SEE #1<br>Sensor feedback; <br>Ball sensor - know when one is entering the system -- possibly? Depends on how close we can get one for the conveyers<br>NO status of spinning depends on # of balls currently in feeder, and whether there is a ball in front of robot. (accuracy?)<br>DOESN'T MATTER AT THIS POINT Should beater bar spin constantly if there are less than 3 balls in robot, or only spin if < 3 balls and there is a ball in front of robot?<br>
	**sub-task		**sub-task
	**sub-task
	*task

	~~= Tasks In Progress =~~

	*Beater bar requirements <br><br>Fixed position inside the frame/ stationary position <br>1 speed forward, 1 speed reverse (not full speed?) <br>measurements (must stay inside the frame) <br>As close to frame perimeter as possible, preferably coincident with it <br>Material ideas: Wheel traction tread, drawer liner, surgical tubing wrapped about the bar <br>Sturdy and easily replaceable (under five minutes to replace it) <br>Inside the frame or deployable? MUST BE INSIDE SEE #1<br>Sensor feedback; <br>Ball sensor - know when one is entering the system -- possibly? Depends on how close we can get one for the conveyers<br>NO status of spinning depends on # of balls currently in feeder, and whether there is a ball in front of robot. (accuracy?)<br>DOESN'T MATTER AT THIS POINT Should beater bar spin constantly if there are less than 3 balls in robot, or only spin if < 3 balls and there is a ball in front of robot?<br>
	**Wings / bridge requirements <br>Are solid/straight from tip back to frame edge to prevent balls from getting trapped behind, and prevent outward bending <br>Starts within the frame perimeter, and deploys to outside the frame perimeter <br>Has no active gathering mechanism -- just simple wings <br>Enables to retreive balls from wall and corners - Guide the balls to the beater bar without moving <br>But CORNER is a big problem with wings down; coming in perpendicular to a wall is difficult as well<br>Able to lower a ramp from its balanced position to a position low enough for us to climb <br><br>Deploys and retracts in under 2 seconds (Motor / Pneumatic?) <br><br>Sturdy and easily replaceable (under five minutes to replace it) <br>Sensor feedback; <br>Could mount sensor for sensing ball in front of robot, only if beater bar should not spin constantly --- probably not necessary -- battery power drain will be limited on brush -- also very dangerous<br>/ If motor operated: Detecting if wings are all the way down (if (sensorOn == true) stop motor to lower wings)<br>(accuracy of sensors?)<br>Limit switches or similar for actuation limits (if not using pneumatics)<br>Position sensor on the actuation axel (get wing's angle of deployment, if driven by motor)<br>
	**sub-task		**sub-task
	*task		*task

Mechanical1 at 17:40, 15 January 2012

2012-01-15T17:40:23Z

← Older revision		Revision as of 09:40, 15 January 2012
Line 1:		Line 1:
	= Attendance =		= Attendance =

	'''Start time:'''		'''Start time:'''

	'''End time:'''		'''End time:'''

	'''Members present:'''		'''Members present:'''

	'''Members Attending Next Meeting:'''		'''Members Attending Next Meeting:'''

	= Tasks Completed =		= Tasks Completed =
Line 18:		Line 18:
	= Tasks In Progress =		= Tasks In Progress =

	*Beater bar requirements <br><br>Fixed position inside the frame/ stationary position <br>1 speed forward, 1 speed reverse (not full speed?) <br>measurements (must stay inside the frame) <br>As close to frame perimeter as possible, preferably coincident with it <br>Material ideas: Wheel traction tread, drawer liner, surgical tubing wrapped about the bar <br>Sturdy and easily replaceable (under five minutes to replace it) <br>Inside the frame or deployable? MUST BE INSIDE SEE #1<br>Sensor feedback; <br>Ball sensor - know when one is entering the system -- possibly? Depends on how close we can get one for the conveyers<br>NO status of spinning depends on # of balls currently in feeder, and whether there is a ball in front of robot. (accuracy?)<br>DOESN'T MATTER AT THIS POINT Should beater bar spin constantly if there are less than 3 balls in robot, or only spin if < 3 balls and there is a ball in front of robot?<br>		*Beater bar requirements <br><br>Fixed position inside the frame/ stationary position <br>1 speed forward, 1 speed reverse (not full speed?) <br>measurements (must stay inside the frame) <br>As close to frame perimeter as possible, preferably coincident with it <br>Material ideas: Wheel traction tread, drawer liner, surgical tubing wrapped about the bar <br>Sturdy and easily replaceable (under five minutes to replace it) <br>Inside the frame or deployable? MUST BE INSIDE SEE #1<br>Sensor feedback; <br>Ball sensor - know when one is entering the system -- possibly? Depends on how close we can get one for the conveyers<br>NO status of spinning depends on # of balls currently in feeder, and whether there is a ball in front of robot. (accuracy?)<br>DOESN'T MATTER AT THIS POINT Should beater bar spin constantly if there are less than 3 balls in robot, or only spin if < 3 balls and there is a ball in front of robot?<br>
	**~~sub~~-~~task~~		**Wings / bridge requirements <br>Are solid/straight from tip back to frame edge to prevent balls from getting trapped behind, and prevent outward bending <br>Starts within the frame perimeter, and deploys to outside the frame perimeter <br>Has no active gathering mechanism -- just simple wings <br>Enables to retreive balls from wall and corners - Guide the balls to the beater bar without moving <br>But CORNER is a big problem with wings down; coming in perpendicular to a wall is difficult as well<br>Able to lower a ramp from its balanced position to a position low enough for us to climb <br><br>Deploys and retracts in under 2 seconds (Motor / Pneumatic?) <br><br>Sturdy and easily replaceable (under five minutes to replace it) <br>Sensor feedback; <br>Could mount sensor for sensing ball in front of robot, only if beater bar should not spin constantly --- probably not necessary -- battery power drain will be limited on brush -- also very dangerous<br>/ If motor operated: Detecting if wings are all the way down (if (sensorOn == true) stop motor to lower wings)<br>(accuracy of sensors?)<br>Limit switches or similar for actuation limits (if not using pneumatics)<br>Position sensor on the actuation axel (get wing's angle of deployment, if driven by motor)<br>
	**sub-task		**sub-task
	*task		*task