2015:Electrical Controls Subteam: Difference between revisions

From 1511Wookiee
Jump to navigationJump to search
No edit summary
No edit summary
Line 99: Line 99:


=== Determine which board to use for the joystick interface ===
=== Determine which board to use for the joystick interface ===
 
<ul style="margin-left: 40px;">
*Cypress is mostly a USB-Serial and PSoC test board, it doesn't really have what we need.
<li>Cypress is mostly a USB-Serial and PSoC test board, it doesn't really have what we need.</li>
*'''LaunchPad''' has digital and analog inputs. There are built-in pull down resistors, so wiring switches will be easy. There are sample programs including joysticks already setup to use with the Dashboard; the source code is available so it can be modified. Also, form factor is much better for using the contorls.
<li>'''LaunchPad''' has digital and analog inputs. There are built-in pull down resistors, so wiring switches will be easy. There are sample programs including joysticks already setup to use with the Dashboard; the source code is available so it can be modified. Also, form factor is much better for using the contorls.</li>
*[http://processors.wiki.ti.com/index.php/MSP430_LaunchPad_Operator_Interface_for_FIRST_Robotics_Competition?DCMP=univ-en&HQS=robotics-FRClaunchpad <font color="#0066cc">http://processors.wiki.ti.com/index.php/MSP430_LaunchPad_Operator_Interface_for_FIRST_Robotics_Competition?DCMP=univ-en&HQS=robotics-FRClaunchpad</font>]
<li>[http://processors.wiki.ti.com/index.php/MSP430_LaunchPad_Operator_Interface_for_FIRST_Robotics_Competition?DCMP=univ-en&HQS=robotics-FRClaunchpad <font color="#0066cc">http://processors.wiki.ti.com/index.php/MSP430_LaunchPad_Operator_Interface_for_FIRST_Robotics_Competition?DCMP=univ-en&HQS=robotics-FRClaunchpad</font>]</li>
</ul>


= Meeting Minutes =
= Meeting Minutes =

Revision as of 16:51, 14 January 2015

Design

Driver #1's side of controls will be able to slide to the right and cover the laptop. This provides for narrow controls for transport. This will have a lock to is doesn't accidentally slide apart during transport.

The intent is to have a simple release mechanism.

Handles on each end for carrying.


2 joysticks for driver #1

  • Y-axis: move robot forward/backwards
  • X-axis: move robot left/right
  • trigger: shift?
  • button 2: lower center wheel


1 joystick for driver #2

  • Y-axis: move lower grip up/down; controls speed of movement
  • trigger: pulled means lower grips are closed (if needed, flip broken switch which means click trigger to close)
  • trigger: released means lower grips are open (if needed. flip broken switch which means click button 2 to open)
  • button 4: close upper grips
  • button 5: open upper grips
  • button 3: possibly use for 'level 3' preset, so tote is high enough to put on top of 2 totes created by human player
  • button 6 (or 8): pull RC grabber back in
  • button 7 (or 9): release RC grabber to get can
  • button 6/7: could be used for presets (means 8/9 used for RC grabber)


N broken switches


1 3-way toggle for autonomous

  • up: a pre-picked auto-mode
  • center: no auto
  • down: use auto-mode that is selected on SmartDashboard


Future Use

  • 3-way toggle for future use (maybe picking which driver opens/closes grips)
  • TBD


Laptop for Dashboard



To do

Not yet started

  • Find data sheets and parts: 3 position switches, broken switches, handles, Gas Shock (McMastercarr 9416k23)
  • Lights?

Started but Needs Work

  • Sheet metal drawings for boxes

Research latching mechanism