Chief Delphi - Team Update 2-07

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)

- General Forum (http://www.chiefdelphi.com/forums/forumdisplay.php?f=16)

- - Team Update 2-07 (http://www.chiefdelphi.com/forums/showthread.php?t=126002)

Team Update 2-07

Quote:

General Updates

The 2014 Inspection Bill of Materials (BOM) Template has been posted on the Game Manual homepage.

The Shipping Crate Construction document has been updated on the Game Manual homepage.

Section 3.1.2: MATCH Logistics

If an ALLIANCE’s BALL becomes stuck in an ALLIANCE’S ROBOT, the ALLIANCE may signal to the Head Referee that the BALL is “dead” (specifics regarding the signaling process are yet to be determined). At this point, the Head Referee will suspend the CYCLE (TRUSS and CATCH points are maintained, ASSIST accruals are voided) and re-illuminate the PEDESTAL, beginning another CYCLE for that ALLIANCE. If the ALLIANCE has not yet begun a CYCLE, the Head Ref will illuminate the PEDESTAL to begin the first CYCLE for the ALLIANCE. If the dead BALL is freed, that BALL must be removed from the FIELD through one of the ALLIANCE’S GOALS or by passing to an ALLIANCE HUMAN PLAYER before the ALLIANCE can earn any more points. Each ALLIANCE is allowed to indicate one (1) BALL as “dead” per MATCH.

Section 3.2.3: General Rules

G12

An ALLIANCE may not POSSESS their opponent’s BALLS. The following criteria define POSSESSION :

“carrying” (moving while supporting BALLS in or on the ROBOT or holding the BALL in or on the ROBOT),
“herding” (repeated pushing or bumping),
“launching” (impelling BALLS to a desired location or direction via a MECHANISM in motion relative to the ROBOT), or
“trapping” (overt isolation or holding one or more BALLS against a FIELD element or ROBOT in an attempt to shield them).

Violation: TECHNICAL FOUL per instance. If extended, another TECHNICAL FOUL. If strategic, RED CARD for the ALLIANCE.

Examples of BALL interaction that are not POSSESSION are

A. “bulldozing” (inadvertently coming in contact with BALLS that happen to be in the path of the ROBOT as it moves about the FIELD) and

B. “deflecting” (a single hit to or being hit by a BALL that bounces or rolls off the ROBOT or a BALL slips through the grips of a ROBOT without arresting the BALL'S momentum).

A BALL that becomes unintentionally lodged on a ROBOT will be considered POSSESSED by the ROBOT. It is important to design your ROBOT so that it is impossible to inadvertently or intentionally POSSESS an opponent’s BALL.

Section 3.2.6: ROBOT-ROBOT Interaction

G29

An ALLIANCE may not pin an opponent ROBOT for more than five (5) seconds. A ROBOT will be considered pinned until the ROBOTS have separated by at least six (6) ft. The pinning ROBOT(S) must then wait for at least three (3) seconds before attempting to pin the same ROBOT again. Pinning is ~~transitory~~ transitive through other objects.

Violation: TECHNICAL FOUL

Section 4.5: Material Utilization

R18

At an Event, Teams may have access to a static set of FABRICATED ITEMS that shall not exceed 30 45 lbs to be used to repair and/or upgrade their ROBOT. Items made at an Event do not count towards this weight limit.

For Teams attending 2-Day Events, these FABRICATED ITEMS may be used during the Robot Access Period and/or brought to the Event, but the total weight may not exceed 30 45 lbs. FABRICATED ITEMS constructed during the Robot Access Period and bagged with the ROBOT are exempt from this limit.

Items exempt from this limit are:

the OPERATOR CONSOLE,
BUMPERS, and
any ROBOT battery assemblies (as described in R5-A).

Section 4.6: BUMPER Rules

R21-D

BUMPERS must be constructed as follows (see Figure 4-8):…

be covered with a rugged, smooth cloth.

Silk or bedding are not considered rugged materials. 1000D Cordura is recommended. Tape (e.g. gaffer's tape) matching the BUMPER color is allowed to patch small holes on a temporary basis.

Section 4.8: Power Distribution

R31

The only legal source of electrical energy for the ROBOT during the competition, the ROBOT battery, is one of the following approved 12VDC non-spillable lead acid batteries:

Enersys (P/N: NP18-12)
MK Battery (P/N: ES17-12)
Battery Mart (P/N: SLA-12V18)
Sigma (P/N: SP12-18)
Universal Battery (P/N: UB12180)
Power Patrol (P/N: SLA1116)
Werker Battery (P/N: WKA12-18NB)
Power Sonic (P/N: PS-12180 NB)
Yuasa (P/N: NBP18-12B)

Gaffers tape is legal to patch bumpers.

Re: Team Update 2-07

The way I read that update, the following could occur, which I don't think the GDC intended:

Three balls are pre-loaded, none of them are scored in autonomous. One is picked up during teleop, and gets 'stuck.' Alliance declares ball dead. Two balls are still rolling on the field. Ref lights up pedestal to start the first cycle. This is consistent with the update.

I suspect they should have said the ref won't light it up until all autonomous balls are either scored or declared dead (of course, only one can be declared dead.)

In the mean time, if you want to get a cycle going early after having a bad time at Auto, just load one ball and declare it dead.

Even if that fix is made, the following scenario is possible:

One ball is left unscored after auto, and rolls to the far end of the field, so that it needs to be taken across the field to score. (No humans are stationed nearby) A working robot could load the ball, declare it dead so that a higher scoring ball (the cycle ball) can be introduced and then score the dead ball (for no points) after making the cross field trip. Meanwhile, the new cycle ball is already inbounded and maybe had toss/catch points before the dead ball is cleared off the field.

What if a dead ball comes loose and finds its way into the opponent's low goal via an unlucky bounce? That is not an approved way to clear a dead ball (must be only by giving it to human or putting it into the alliance's goal.) So technically, this is equivalent to a second stuck ball and the team is done scoring for the match.

Re: Team Update 2-07

45lb.s worth of witholding allowance?! :eek:

A full 50% increase over what we had previously, up to nearly 40% of our total weight. Wonder if this is motivated by the worse than usual snow delays that have hammered much of the east coast.

Re: Team Update 2-07

Quote:

Originally Posted by Lil' Lavery (Post 1339390)

Yes it was. See the 2/5 blog.

Re: Team Update 2-07

Quote:

Originally Posted by luckof13 (Post 1339392)

Yes it was. See the 2/5 blog.

Sorry, you lose track of things when you're in the middle of the ocean for a few days. :o

Re: Team Update 2-07

Another problem solved by Frank in a fairly uniform, easy to enforce, fair way to deal with the random bad weather. Slight penalty to teams that spend the first hours bolting on the extra parts but a big win overall.

Another plus 1 for Frank and his team. Could this be the start of a wave of simple, common sense like solutions sweeping across the nation?