Vex Pushback | NVHS

SC1

Last 5 seconds is a grace period to make sure no rules are being broken

You can’t take advantage of the last 5 seconds

The less advantageous ruling is given if robot is in between two states

SC2

For block to be scored, it needs to:

1. Touch the inside surfaces

2. Not touch the robot

3. Not in contact with the floor

SC3

Control Zone is Controlled if:

1. Scored block is entirely within control zone

2. Follows scored conditions of a regular block

SC4

A robot is considered parked if:

1. Not touching floor

2. Not contacting any field elements aside(e.g. a block)

3. Within vertical bounds

SC5

Autonomous Bonus:

1. Immediately after match ends

2. Parked bonus not included

3. Major/minor violations = no bonus

4. Both alliances commit violation = no bonus

SC6

AWP:

1. 7 blocks scored

2. Scored in 3 different goals

3. 3 block removed from loader

4. Neither bots contacting parking zone barrier

G1 - G4

1. Treat everyone with respect

2. Build/code yourself

3. Common sense

4. A student can only belong on one team, and robot should represent THEIR skill level

SG1

To start match, robot must be:

1. 18 × 18

2. Not contacting blocks, other robots, goals, or loaders

3. Stationary

4. Contacting alliance barrier

SG2

Horizontal expansion limit is 22”

SG3

Vertical expansion limit is 22”

SG5

One block as a preload for each robot

• Can not be contacting another robot, goal, or loader

• Same alliance color

SG6

You can hold/touch as many blocks as you want

SG9

If a block goes out of the field, the driver can reintroduce it:

• Blocks can only be added during DCP

• Blocks can not be touched by the robot before they are added to the loader

• Only robots can take blocks out of the loader via the bottom opening

SG10

Robots can’t reach inside the goals, but can add/remove blocks from open sections

SG11

Park zones are protected in last 20 seconds. The other team can not touch the park zone or the robots which are inside it.

T1

1. Scorekeepers can only advise head referee

2. Head referee has to give the specific rule being violated for major or minor violations

3. Event partner cannot change ruling

4. Qualification match must be watched by a certified head referee

5. Skills match must be watched by a certified scorekeeper

T3

Drive team members can appeal head referees ruling immediately, however:

1. Once they make an official ruling, it is final

2. No video/photo can be used

3. Only head referees can explain the violation

4. Drive team members must stay in the alliance station(head referee can choose to talk to them at another place or time)

T11

Each team will have at least 6 qualification matches

• Suggested is 8-10(standard to championship event)

• When in a league, there are 3 sessions, 1 week apart

  • 2-4 qualifications matches per sessions, culminating in a final

T13

Team rankings are determined by:

1. Average Win Points scored

2. Average Autonomous Points scored

3. Average Strength of Schedule Points

4. Highest & second highest match score

5. Random draw

T16

Alliance selection rule

Each team can only be invited once to join one alliance

T22

Skills ranking based on:

1. Sum of highest autonomous coding skills scored and driving skills score

2. Highest autonomous skills scored

3. Second-highest autonomous skills score

4. Sum of highest skills stop times

5. Highest autonomous coding skills, skills stop time

6. Third highest driving and autonomous skills scores

7. If there is a tie

   1. Points earning for filled control zones

   2. Number of blocks earned in goals

   3. Points for parking

8. Step #9 is repeated

9. Worst case: tie-breaker

T23

Global skills ranking based on:

1. Highest robot skills score

2. Highest autonomous skills score

3. Highest driving skills score

4. Highest sum of skills stop times

5. Highest autonomous coding skills, skills stop time

6. Highest driving skills, skills stop time

7. Earliest posting of highest autonomous coding and driving skills scores

R3

1. Significant changes will need to be re-inspected

2. All possible robot configurations must be inspected

3. Teams may be requested to a spot-check and will be removed from the field until the robot passes inspection(no-show)

4. If a head referee deems a robot as violating inspection after a match, only that match will be afffected

5. If the robot has not passed an inspection, they will be deemed a no-show for their match

6. Inspections rules are enforced at the discretion of the head referee

R4

1. Any violation of the robot rules will disallow the team from playing

2. Purposefully circumventing the rules might get you disqualified and reported

R12

88 W total

R19

1. Anything that can damage the field or field elements is not allowed

2. Anything that can pose a hazard to people is not allowed

3. Anything that can cause entanglement with another robot

4. No 3D printed robot parts that actually serve a purpose

5. No parts from other vex games

6. No V5 beta parts

R20

The below non-Vex elements are allowed:

1. Color filters for color sensors

2. Non-aerosol lubricants

3. Anti-static compound

4. Hot glue

5. Unlimited amounts of rope and string

6. Cable management items(commerically available)

7. Rubber bands

8. Pneumatics

9. Zipties

10. Micro-SD cards

11. Cooling spray

12. Cleaners

R22

Limited amount of tape allowed

• Label wires

• Prevent leaks

• Connect ends of cables

• Non-functional

R25

Limited amount of custom plastic is allowed:

• 12 pieces

• Each piece can’t be larger than 4 × 8 × 0.07

• Present all pieces during inspection

• Plastic may be physically altered

• Legal plastic: PMMA, Polycarbonate, Delrin

• Vex plastic sheets are allowed

• Not applicable to 3D printed parts