2022:Controls: Difference between revisions

From 1511Wookiee
Jump to navigationJump to search
Tag: visualeditor
Tag: visualeditor
Line 150: Line 150:
<span style="font-size:large">1/18</span>
<span style="font-size:large">1/18</span>


Attendees: Colin, Sam, Eric  
Attendees: Colin, Sam, Eric, Noah


Work Completed:  
Work Completed:  

Revision as of 16:54, 18 January 2022

About how much everything weights

  • The Laptop: 6.12 lbs.
  • The Metal Base with Controls: 5.09 lbs. x2
  • The Controller (as PS5 or Xbox): 0.5 lbs. x2
  • The Suitcase: 7.3 lbs.
  • Everything will sum up to about 17.3 lbs. (if u add plus one more metal base and one more controller)

LED lights idea's

  • The question marks mean that the driver or the team would decide what they would want.
Combo 1
Combo 2
Combo 3

Broken switches controls layout (CAD)

File:Controls v7 (Better Layout).iptFile:Controls v6.5 layout alternate.ipt

Possible switches we would need

Measurements for switches

Overall Concept

Ideas

To do

  • At diner prepare to present the model and explain everything to the people. Answer peoples questions if they have any. take in notes on comments or what they think we should add.

Not Started

In Process

Completed

  • Using PS4/PS5 (or Xbox if PS not possible) for primary driver [was confirmed with Isaac on 1/15/22]
  • PS4/PS5 control works with Windows 10 (PS4 to PC; PS5 to PC)
  • If you haven't before check out the controls in the closet.
  • Brainstorm themes/concepts, be ready Saturday to share.
  • Research joysticks.
  • If we are going to do a swerve drive we need to understand how it will be controlled.
  • Keep finding switches we are going to use look over what we have in the shop put them in a separate box so we know we have to use them, such as collecting data sheets and measurements. Put them in the wiki.
  • After we present(didn't present yet), we should give the suitcase back to Niccole, and put the pieces inside back in place.

Controls Assignments

Aux

Aux (not fully done) ideas

Drive

Drive (not sure if its done) ideas

Bling

Useful Links

PSoC Creator IDE

Toolkits and Board Driver Install

  • Get controls2019 from SVN
  • Run: vcredist_x86.exe
  • Run: USBSerialSDKSetup.exe (do Typical install; at end run Updater and maek sure you have the latest stuff)
  • Run: CY8CKIT04942xxSetupOnlyPackage_revSA.exe (do Typical install; at end run Updater and make sure you have the latest stuff)
  • While you press and hold the SW1 Prog button on the cypress board, plug in the USB cable to the PC (it will take a while for it to install 5 drivers).

Build/Program

  • Open PSoC Creator (Start -> Programs -> Cypress -> PSoC Creator -> PSoC Creator)
  • Open project: File -> Open -> Project/Workspace; then browse to Desktop/FRC2020/trunk/controls/SCB_Bootloader/SCB_Bootloader.cywrk)
  • Build project: Build -> Build All Projects
  • While you press and hold the SW1 Prog button on the cypress board, plug in the USB cable to the PC
  • Download Boot Loader:
  • open programmer: Tools -> Bootloader Host
  • set 'File' to C:\Users\Robotics\Desktop\FRC2020\trunk\controls\SCB_Bootloader\Bootloadable Blinking LED.cydsn\CortexM0\ARM_GCC_541\Debug\Bootloadable Blinking LED.cyacd
  • select the com port for the cypress board
  • set Baud to 115200; Data Bits 8; Stop Bits 1; Parity None
  • download program: Actions -> Program

Meeting Minutes

1/15

Attendees: Colin, Sam, Olga, Mr. Byers

Work Completed:

  • confirmed primary controller
  • looked at controls from prior years
  • sketching concepts

1/16

Attendees: Colin, Sam, Olga, Noah, Eric.

Work Completed:

  • Found suitcase
  • Found way to make suitcase work
  • confirmed that we are using two controllers ( probably ps5 )
  • Worked out design
  • Got measurements
  • Started CAD work
  • measured buttons

1/18

Attendees: Colin, Sam, Eric, Noah

Work Completed:

  • Basic design for control plate made in CAD.

1/19

Attendees:

Work Completed:

1/20

Attendees:

Work Completed:

1/22

Attendees:

Work Completed:

1/23

Attendees:

Work Completed:

1/25

Attendees:

Work Completed:

1/26

Attendees:

Work Completed:

1/27

Attendees:

Work Completed:

1/29

Attendees:

Work Completed:

1/30

Attendees:

Work Completed:

2/1

Attendees:

Work Completed:

2/2

Attendees:

Work Completed:

2/3

Attendees:

Work Completed:

2/5

Attendees:

Work Completed:

2/6

Attendees:

Work Completed:

2/8

Attendees:

Work Completed:

2/9

Attendees:

Work Completed:

2/10

Attendees:

Work Completed:

2/12

Attendees:

Work Completed:

2/13

Attendees:

Work Completed:

2/15

Attendees:

Work Completed:

2/16

Attendees:

Work Completed:

2/17

Attendees:

Work Completed:

2/19

Attendees:

Work Completed:

2/20

Attendees:

Work Completed:

Controls Rules

9.9 OPERATOR CONSOLE R901 *Use the specified Driver Station Software. The Driver Station Software provided by National Instruments (install instructions found here) is the only application permitted to specify and communicate the operating mode (i.e. AUTO/TELEOP) and operating state (Enable/Disable) to the ROBOT. The Driver Station Software must be version 22.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 MATCHES.

R902 *The OPERATOR CONSOLE must have a visible display. The OPERATOR CONSOLE, the set of COMPONENTS and MECHANISMS used by the DRIVERS and/or HUMAN PLAYERS to relay commands to the ROBOT, must include a graphic display to present the Driver Station Software 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.

R903 *Connect FMS Ethernet directly to the OPERATOR CONSOLE. Devices hosting the Driver Station Software must only interface with the FMS via the Ethernet cable provided at the DRIVER STATION (e.g. not through a switch). Teams may connect the FMS Ethernet cable to the device running the Driver Station Software 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.

R904 *OPERATOR CONSOLE physical requirements. The OPERATOR CONSOLE must not A. be longer than 5 ft. (~152 cm), B. be deeper than 1 ft. 2 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, or D. attach to the FIELD (except as permitted by G301).

There is a 4 ft. 6 in. (~137 cm) long by 2 in. (nominal) wide strip of hook-and-loop tape (“loop” side) along the center of the DRIVER STATION support shelf that should be used to secure the OPERATOR CONSOLE to the shelf, per G301. See DRIVER 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.

R905 *FIELD wireless only. Other than the system provided by the FIELD, 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.

R906 *No unsafe OPERATOR CONSOLES. 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

Retrieved from "https://wiki.penfieldrobotics.com/wiki/index.php?title=2022:Controls&oldid=11391"