pic: Haven't got a clue for 'how to' climb for 30 points? Here's one

[NOV8R]

CalTran, Your points are well taken. Perhaps the biggest reason of all against doing it is : If you can reliably show you can score 30 points every match, as soon as you leave the safety of the pyramid your dead. Every robot on the opposing alliance is going to be focused on making sure you don't get back to the pyramid. Keeping you from climbing is the same as them scoring 30 points.

[cmrnpizzo14]

Originally Posted by NOV8R

CalTran, Your points are well taken. Perhaps the biggest reason of all against doing it is : If you can reliably show you can score 30 points every match, as soon as you leave the safety of the pyramid your dead. Every robot on the opposing alliance is going to be focused on making sure you don't get back to the pyramid. Keeping you from climbing is the same as them scoring 30 points.

Do you think that a team who is that dependent on their strategy would allow themselves to be blocked away from the pyramid all game? I would only hope that the drivers are able to free themselves just enough to get back to the pyramid or that another alliance bot would be able to take the blocker off for a few seconds.

I guess that I am basically saying, do you think that you could prevent a robot from getting to the largest object on the field for a long enough time that it stops their climb without sacrificing defense on what are hopefully that alliances "main" scoring robots (the shooters).

[Brandon Zalinsky]

I think your mecanums might be on backwards- the rollers form a 0 instead of an X.

[45Auto]

Originally Posted by nov8r

If you can reliably show you can score 30 points every match, as soon as you leave the safety of the pyramid your dead. Every robot on the opposing alliance is going to be focused on making sure you don't get back to the pyramid. Keeping you from climbing is the same as them scoring 30 points.

Question 1 - Why leave the safety of the pyramid if all you need is the 30 points?

Question 2 - What do you think the other robots on my alliance are going to be doing?

Stopping you from stopping me from scoring 30 points is the same as them scoring 30 points and you scoring 0!

Either way, my alliance wins by 30 points!

[NOV8R]

Good eye Brandon, Right now the drive train is not hooked up and is only dead weight to make CG manipulation work. If you're keeping up with the discussion the question is do we even need to make it work. The robot rules say you have to have a 'mobility' system. They don't say it has to be functional. As it stands now our match strategy is to position the robot at the start of the match inside the pyramid with the arm touching the first rung. Then in autonomous the robot will climb to the first rung and hang. When teleop begins it will climb to the second rung, transition to the outside and finish the match hanging in level 3. The sticky wicket right now continues to be climbing speed. During the 2 minutes of teleop it's dicey completing the L3 climb, hence starting in autonomous. We're looking at other climbing motor/gearbox combos to make the climb faster. The current climb mechanism is a 36 inch 1/2 inch 0.25 lead screw run by an AM-0915 gearmotor. That spins the lead screw at close to 200 rpm climbing at 50 inches per minute. We're looking at using a BAG motor/Vex Pro gearbox setup.

[Alpha Beta]

Originally Posted by NOV8R

The robot rules say you have to have a 'mobility' system. They don't say it has to be functional.

Is a mobility system that doesn't make the robot mobile really a mobility system?

On the other hand isn't vertical mobility still mobility?

R01
Each registered FRC team may enter only one (1) ROBOT into the 2013 FRC. The ROBOT must be built by the FRC Team to perform specific tasks when competing in ULTIMATE ASCENT. The ROBOT must include all of the basic systems required to be an active participant in the game – power, communications, control, mobility, and actuation. The ROBOT implementation must obviously follow a design approach intended to play ULTIMATE ASCENT (e.g. a box of unassembled parts placed on the FIELD, or a ROBOT designed to play a different game would not satisfy this definition).

[NOV8R]

Good question Aaron. I guess I was stuck thinking of mobility in the horizontal plane. We're playing with 'how much' weight we need to make the CG manipulation work. Less weight also translates to faster climb. We are going to have wheels of some sort even though they may be static. I can see us now trying to convince an inspector where the bumper zone is if we didn't have them.

[Brandon Zalinsky]

Originally Posted by NOV8R

Good eye Brandon, Right now the drive train is not hooked up and is only dead weight to make CG manipulation work. If you're keeping up with the discussion the question is do we even need to make it work. The robot rules say you have to have a 'mobility' system.

Ok, cool. I didn't read through the rest of the replies, my bad. Hook some ungeared RS550s to those puppies, post it on CD, and have a field day with the replies. On a more serious note, what is the perimeter of your robot right now? It looks pretty small.

[NOV8R]

Hi Brandon, The robot is 24 x 15 inches (78 inch perimeter). It's the smallest robot we could make and get all the required components in. All the components (cRio, power dist board, battery, digital sidecar, h bridge etc) are all inside. Needless to say it's a little cramped. I'll take some pictures of the inside of it in the next few days and post them. Getting everything inside was very similar to the pictures of people trying to cram too much stuff in a small suitcase. The only thing we didn't have to do was sit on it to close the lid.