Demo Bot Controls: Difference between revisions
Programming (talk | contribs) (Added list of cases to discuss) |
Programming (talk | contribs) No edit summary |
||
| Line 31: | Line 31: | ||
Controler Chosen: http://www.amazon.com/Logitech-Wireless-Gamepad-Support-Vibration/dp/B0041RR0TW/ref=dp_cp_ob_e_title_0<br> | Controler Chosen: http://www.amazon.com/Logitech-Wireless-Gamepad-Support-Vibration/dp/B0041RR0TW/ref=dp_cp_ob_e_title_0<br> | ||
<br> | Secondary controls - ~10 in wide, 6 in tall, 2 in deep<br> | ||
<br> | |||
Hard Case - http://www.amazon.com/Zeikos-ZE-HC36-Medium-Hard-Case/dp/B001HJTK5Y $35 18 x 13.5 x 6.5 inches<br> | Hard Case - http://www.amazon.com/Zeikos-ZE-HC36-Medium-Hard-Case/dp/B001HJTK5Y $35 18 x 13.5 x 6.5 inches<br> | ||
Revision as of 15:15, 16 August 2011
Ideas:
Number of Drivers
Mobility of controls
Child locks/public driver mode
using joysticks/controllers:
controlers:
more modern/familiar
wireless capability
more compact
easier to move between 1 and 2 driver
harder to damage
easier to remember
simple
joysticks: not likely
precision
accurate representation
simple
control board:
customizable
difficult to remember/learn
labelable
difficult to create
task/learning
visual feedback
number of joysticks/controllers
"inside" locks
Decisions:
Must have option for 2 drivers: shows typical team opperation
Must have option to control core by single dirver: lack of students at a demo
requirements:
use laptop
use c-rio
integrate e-stop button
actions:
drive tank style base
shoot at variable speeds
aim shooter (vertical)
curve balls via bias (maybe)
turn on and off LED's
child locks:
limit speeds
set ball power
stop drivetrain button on secondary
(if used) disable curve
difficult to access
Controler Chosen: http://www.amazon.com/Logitech-Wireless-Gamepad-Support-Vibration/dp/B0041RR0TW/ref=dp_cp_ob_e_title_0
Secondary controls - ~10 in wide, 6 in tall, 2 in deep
Hard Case - http://www.amazon.com/Zeikos-ZE-HC36-Medium-Hard-Case/dp/B001HJTK5Y $35 18 x 13.5 x 6.5 inches
