2018:Controls

Overall Concepts

NES

NES Dimensions:

• Width: 10’’
• Length: 8’’
• Height: 3.5’’

Controls Dimensions:

• Width: 16’’
• Length: 14’’
• *Height: 6.5’’

Details

• Controller ports on front will be USB for the actual controllers
• Where the white turns gray is where the system will fold open
• When the laptop turns on or controls are plugged in, the light next to the power button will turn on
• Video ports on side will be where the ethernet plug will be
• Nintendo "case" should fold open to the left
• Xbox controllers can fit on top of the laptop.

NES Cartridge

Details

• Custom stickers on cartridge
• Folds out from the left side of the “notch” of the cartridge

To do

Not Started

• The control dimensions right now are exactly 14" deep, we should probably reduce that by 1/2".
• Add in a handle design (overall thought is handle on the back), need to add detail.
• Add the cutout for the LED next to the buttons.
• Figure out hinge concept for box, get hinge on order.
• Also need hinge design for the cartridge door.
• Need to come up with a latch to keep controls closed.
• Concept for the power cord?
• Finalize model
• Create drawings for Harris
• Overall paint and letter scheme (low priority).

In Process

• Finish the cutouts for the USB ports.
• Add detail into the metalwork.

Completed

• Select High-level Concept, work details in the concepts to help make the selection. [NES]
• Find out (in general) does the laptop and necessary parts (2 extra little boards (for buttons and something else), power supply, broken switches, and controllers.) fit in the controls box (not exact).[Yes, Xbox controllers can fit on top of the layptop]
• Make sure the control box fits in the driver station (measurement requirements found in game manual).
• Figure out where the NES opens up so that the laptop screen can be seen.
• Go through "controls"-related stuff in the shop and gather things we think we might want to use (buttons, switches, latches, etc.)
• Create a storage area for our stuff in the shop, we'll need a box or something to hold our parts.
• Talk to drive team and figure out what kind of control (Xbox, joysticks, etc.) they want this year. [Josh & Carol said to go with XBOX controllers]
• Brainstorm Ideas for Controls and record them.
• Figured out how the NES will open [To the left]
• CAD'd the NES
• Figured out the control box can fit the necessary parts such as the laptop and the broken switches.
• Found out that the control box fits the driver station requirements. (14in = 14in)

Useful Links

• Subteam Student/Mentor Photos
• Zero Delay USB Joystick Encoder
• http://exposantana.com/img/nes-measurements.jpg
• https://ibin.co/2pzZhDM2hmF8.png
• https://grabcad.com/library/nintendo-entertainment-system

Meeting Minutes

1/10

Attendees: Zach, Kyle, Jameson, Parker, Eric, Byers

Work Completed: Brainstormed ideas for control sets. 

1/11

Attendees: Kyle

Work Completed: An attempt was made, but overall nothing got done.

1/13

Attendees: Zach(left early), Kyle, Adrian

Work Completed: CAD'd the NES to the dimensions above. Began gathering materials. Allocated shelf space in shop closet.

1/14

Attendees: Kyle and Aidan

Work Completed: Figured out the control box can fit the necessary parts such as the laptop and the broken switches; Found out the control box fits the driver station requirements (14in = 14in); began the final NES CAD

1/16

Attendees: Eric, Parker, Adian, Adrian, Jameson

Work Completed: Researched some handle ideas, added button cutouts and started to add USB ports to base, found a nintendo font, decided which way the controls should open (to the left), determined that we should be able to store the joysticks either on the laptop or in the top half of the chassis.

1/17

Attendees: 

Work Completed: 

1/18

Attendees: 

Work Completed: 

1/20

Attendees: 

Work Completed: 

1/21

Attendees: 

Work Completed: 

1/23

Attendees: 

Work Completed: 

1/24

Attendees: 

Work Completed: 

1/25

Attendees: 

Work Completed: 

1/27

Attendees: 

Work Completed: 

1/28

Attendees: 

Work Completed: 

1/30

Attendees: 

Work Completed: 

1/31

Attendees: 

Work Completed: 

2/1

Attendees: 

Work Completed: 

2/3

Attendees: 

Work Completed: 

2/4

Attendees: 

Work Completed: 

2/6

Attendees: 

Work Completed: 

2/7

Attendees: 

Work Completed: 

2/8

Attendees: 

Work Completed: 

2/9

Attendees: 

Work Completed: 

2/10

Attendees: 

Work Completed: 

2/11

Attendees: 

Work Completed: 

2/12

Attendees: 

Work Completed: 

2/13

Attendees: 

Work Completed: 

2/14

Attendees: 

Work Completed: 

2/15

Attendees: 

Work Completed: 

2/16

Attendees: 

Work Completed: 

2/17

Attendees: 

Work Completed: 

2/18

Attendees: 

Work Completed: 

2/19

Attendees: 

Work Completed: 

2/20

Attendees: 

Work Completed: 

Controls Rules

8.10 OPERATOR CONSOLE

R97. The Driver Station software provided on the National Instruments website is the only application permitted to specify and communicate the operating mode (i.e. Autonomous/Teleoperated) and operating state (Enable/Disable) to the ROBOT. The Driver Station software must be revision 18.0 or newer. Teams are permitted to use a portable computing device of their choice (laptop computer, tablet, etc.) to host the DRIVER Station software while participating in competition MATCHES.

R98. The OPERATOR CONSOLE, the set of COMPONENTS and MECHANISMS used by the DRIVERS and/or HUMAN PLAYER to relay commands to the ROBOT, must include a graphic display to present the Driver Station diagnostic information. It must be positioned within the OPERATOR CONSOLE so that the screen display can be clearly seen during Inspection and in a MATCH.

R99. Devices hosting the Driver Station software must only interface with the Field Management System (FMS) via the Ethernet cable provided at the PLAYER STATION (e.g. not through a switch). Teams may connect the FMS Ethernet cable to their Driver Station device directly via an Ethernet pigtail, or with a single-port Ethernet converter (e.g. docking station, USB-Ethernet converter, Thunderbolt-Ethernet converter, etc.). The Ethernet port on the OPERATOR CONSOLE must be easily and quickly accessible. Teams are strongly encouraged to use pigtails on the Ethernet port used to connect to the FMS. Such pigtails will reduce wear and tear on the device’s port and, with proper strain relief employed, will protect the port from accidental damage.

R100. The OPERATOR CONSOLE must not Section 8 ROBOT Rules V2 96 of 127 A. be longer than 60 in. (~152 cm) B. be deeper than 14 in. (~35 cm) (excluding any items that are held or worn by the DRIVERS during the MATCH) C. extend more than 6 ft. 6 in. (~198 cm) above the floor D. attach to the FIELD (except as permitted by G19) There is a 54 in. (~137 cm) long by 2 in. (nominal) wide strip of hookand-loop tape (“loop” side) along the center of the PLAYER STATION support shelf that should be used to secure the OPERATOR CONSOLE to the shelf, per G19. See Section 3.6.1 PLAYER STATION for details. Please note that while there is no hard weight limit, OPERATOR CONSOLES that weigh more than 30 lbs. (~13 kg.) will invite extra scrutiny as they are likely to present unsafe circumstances.

R101. Other than the system provided by the ARCADE, no other form of wireless communications shall be used to communicate to, from, or within the OPERATOR CONSOLE. Examples of prohibited wireless systems include, but are not limited to, active wireless network cards and Bluetooth devices. For the case of the FIRST Robotics Competition, a motion sensing input device (e.g. Microsoft Kinect) is not considered wireless communication and is allowed.

R102. OPERATOR CONSOLES shall not be made using hazardous materials, be unsafe, cause an unsafe condition, or interfere with other DRIVE TEAMS or the operation of other ROBOTS.

Archives

• 2017:Controls
• 2016:Controls
• 2015:Electrical Controls Subteam
• 2014:Electrical Controls Subteam
• 2013:Electrical Controls Subteam
• 2012:Electrical Controls
• 2011:Electrical Controls
• 2010:Electrical Controls
• 2009:Electrical Controls
• 1846:Electrical Controls