Re: Low Goal Defense
 

You are over thinking this. Since:

A BALL is considered SCORED in an ALLIANCE’S GOAL if
A. a ROBOT causes one (1) of their ALLIANCE’S BALLS to cross completely through the opening(s) of one (1) of
their ALLIANCE’S GOALS without intervening human contact,
B. the ALLIANCE ROBOT last in contact with the BALL was entirely between the TRUSS and their ALLIANCE’S
HIGH GOALS, and
C. the BALL is not in contact with any ROBOT from that ALLIANCE.

This means you can simply push into a low goal, you have to launch/throw into the front, side top of the low goal. I think this is harder than people think. Defense on low goals is easy, put stationary robot with a 20 inch extension by the corner and that low goal is un-scorable. - However that leaves the other low and both high goals open, plus your defensive robot isn't helping your alliance score points.

Re: Low Goal Defense
 

Considering that deflections are specifically called out as not being possessions, and thus legal, yes, I would say that remaining stationary prevents any penalty.

Re: Low Goal Defense
 

This is a very interesting take on the definition of SCORED. I am assuming that you meant to say "can't" as the 4th word in your description. If not, I apologize for analyzing something that you did not intend to say.

I am pretty sure that a ball which a robot pushes into the low goal will still be considered SCORED. In this situation, after the pushing robot has moved away:
A. The BALL is completely through the opening of one GOAL
B. the ALLIANCE ROBOT last in contact with the BALL is entirely between the TRUSS and their ALLIANCE’S
HIGH GOALS
C. the BALL is not in contact with any ROBOT from that ALLIANCE.

Hence, all of the criteria for SCORED are met, and the BALL will be considered SCORED.

In a different scenario: a robot pushes the BALL into the GOAL with a fist-like mechanism that extends into the GOAL. As long as the fist is touching the BALL, the BALL is not considered SCORED since it is in contact with the ROBOT. As soon as the contact is broken however, the BALL will be considered SCORED.

Re: Low Goal Defense
 

in rule 3.1.4 c in game manual, it states"a ball is considered scored in an alliances goal, if the ball is not in contact with any robot from that alliance", does anyone understand thios rule. is it simply that the ball must be fully disengaged from the robot at games end?

Re: Low Goal Defense
 

Due to team update #1, this is no longer legal. Good thoughts though.

see:

http://frc-manual.usfirst.org/Updates/0#term127

or this thread

http://www.chiefdelphi.com/forums/sh...hreadid=124255

Re: Low Goal Defense
 

Erm ... not quite true.

The low goal can still be blocked by an extension IN FRONT of the low goal, just not into the low goal.

Re: Low Goal Defense
 

With team update 1, you can extend to go around, but not within. I believe that was an earlier strategy? To help burgeon this strategy, If you put a slide drive, and build a robot that could block a goal on either side, you could just strafe side to side, going in the direction of the opposing robot. Put a vertical extension on this bad boy and you'll also be blocking the high goals as well. I think this is brilliant.

Re: Low Goal Defense
 

What does game's end have to do with a ball being considered scored?

If a ball enters an alliance's goal, it needs to not be in contact with any robot on that alliance to score. That simple.

The rule you may have been thinking of is R7, in 4.1.7, which simply says that you have to be able to remove the ball while the robot is unpowered.

Re: Low Goal Defense
 

So no there is an explicit rule saying you can't do that