2013:Climber Subteam

Climber Design

2 hook like arms with hooks in the center of them

Controls: 

Put arms up

put arms down

controls are put arms in climbing positions 

1 pair of sensors for each arm

• Sensors activate when in contact with pyramid 

2 motors for climbing, and 2 servos for leaning forward

Is there speed control?

`

We should have the ability to abort a climb

**************************************
NOTE: the following is based on the outcome of the programming team going through the sub-system and review they had will electrical and the operator controls sub-teams on 1/26. This needs to be reviewed to make sure these notes concur with what everyone took away. This will also need to be reviewed by strategy.
**************************************

For aligning the pyramid, the "V" sensor is not enough. The robot may still be too far to the right or left. If too far right/left, then only one side of the arms would grab the bars. Additional sensors will be placed on the fixed arms, at the height of the level 1 horizontal bars. In order to climb, the "V" sensor and both arms sensors will need to be tripped; this will give 3 points of contact and 'guarntee' alignment for climbing.

The drivers will be responsible for engaging the "V" sensor and deploying the arms; this can be done in either order. The aux driver will then press and hold a button to climb. The robot will preform the entire climb. This means, the robot will automatically turn to get both arm sensors tripped (i.e. auto align the robot to the pyramid), then move the lifting arms up, then pull the robot to level 1, then move lifting arms to next level, then pull robot to level 2, and so on until at level 3. If the driver wants to abort the climb, they just release the button. This allows the driver stop the climb at any level and abort if they see something wrong. The button can be re-pressed and the robot will continue the climb, if possible.

TBD: So we do not violate the 54" rule, the shooter will need to be in the home position before climbing. This means the "Deploy" for the arms will not work unless the shooter is at the required angle.

Sensors:

Area	Type	Description	Operation	Notes
Fixed Arms	(2) TBD	Detects when the arms are in position for the robot to hang and is being hung.	The sensors are tripped when the arm has 'snapped' against the horizontal bar after just riding up and over it; meaning the robot can now be lowered onto the bars and be hung. The sensor will remain tripped while the robot is hung (TBD).	To minimize inputs, the sensors will be 'and' together.
Moving Arms	(2) TBD	Detects when the arms are in position for the robot to be pulled up.	The sensors are tripped when the arm has 'snapped' against the horizontal bar after just riding up and over it; meaning the arms can be lowered and the robot pulled up to the next level.	To minimize inputs, the sensors will be 'and' together.
Fixed Arms Alignment	(2) TBD	Used to align the robot prior to climbing	The sensors are the height of the level 1 horizontal bars and are tripped when the edge of the arm is in contact with the harizontal bar. Both sensors need to be tripped before climbing will occur.	Need to be separate inputs.
"V"	TBD	Detects when pryamid leg is in the "V"	Is tripped when the leg is far enough into the "V" that climbing can begin. And stays engaged when the leg is all the way into the "V".
Arm Track Top	TBD	Detects when lifting arms are at the top of the track	This is at the limit of travel. Software will kill the motor power if this is tripped.
Arm Track Bottom	TBD	Detects when lifting arms are at the bottom of the track	This is at the limit of travel. Software will kill the motor power if this is tripped.
Arm Motor Shaft	TBD (Encoder OR Pot)	Detects arm motors moving	Used to control the speed of the motors. The torque will be different: 1) no load just moving arms up and lowering the first inch or so to latch on the bar; 2) when lifting the robot up the leg; 3) lifting the robot over the knuckle.

Motors/Servors/Actuators:

Type	Description	Operation	Notes
CIM (2)	Moves the lifting arms	If not in lift broken mode, the encoder and a PID are used to control the moving of the arms. If in lift broken mode, buttons on the joystick will be used to drive the motor at a constant speed.
Servors (2)	Deploys the arms	Releases pins that are holding both arms, so the arms are extended and can be used for climbing.

Lights (on robot):

Area	Type	Description	Operation	Notes
		"V" engaged	Will be 'green' when pryamid leg is in the "V".	Possibly re-use "have 1 disc" light; light means "V" when climber side is the 'front'
		Arms aligned	Will be 'green' when both Fixed Arm Alignment sensors are tripped	Possibly re-use "have 2 discs" light; light means "arms alilgned" when climber side is the 'front'
		Level Acheived	Will be 'green' when the Fixed Arm sensors are tripped; which means the robot is hung (or would be if power lost and robot would 'fell' the inch or so as the arm catch)	Possibly re-use "have 3 discs" light; light means "level acheived" when climber side is the 'front'
		TBD - Done climbing	TBD - Will be 'green' when the auto-climb is done and at level 3	TBD - Possibly re-use "have 4 discs" light; light means "done climbing" when climber side is the 'front'. Or just flash all the lights to be fancy.

Climber's Engineering Notebook

Week 1

• 1/10
• 1/12

Week 2

• 1/13
• 1/15
• 1/16
• 1/17
• 1/19

Week 3

• 1/20
• 1/22
• 1/23
• 1/24
• 1/26

Week 4

• 1/27
• 1/29
• 1/30
• 1/31
• 2/02

Week 5

• 2/03
• 2/05
• 2/06
• 2/07
• 2/08
• 2/09

Week 6

• 2/10
• 2/11
• 2/12
• 2/13
• 2/14
• 2/15
• 2/16
• 2/17
• 2/18
• 2/19

Engineering Notebook Templates Available at:Engineering_Notebook_Template

Please Label All Notebook Pages 2013:Climber XX.XX to avoid confusion.