View Single Post
  #1   Spotlight this post!  
Unread 03-12-2012, 22:17
F22Rapture's Avatar
F22Rapture F22Rapture is offline
College Student, Mentor
AKA: Daniel A
FRC #3737 (4H Rotoraptors)
Team Role: Mentor
 
Join Date: Jan 2012
Rookie Year: 2012
Location: Goldsboro, NC
Posts: 476
F22Rapture has a brilliant futureF22Rapture has a brilliant futureF22Rapture has a brilliant futureF22Rapture has a brilliant futureF22Rapture has a brilliant futureF22Rapture has a brilliant futureF22Rapture has a brilliant futureF22Rapture has a brilliant futureF22Rapture has a brilliant futureF22Rapture has a brilliant futureF22Rapture has a brilliant future
Implementing a switchable control scheme

Our team would like to be able to switch between control schemes (for the drivetrain) as a way to easily find out what our potential drivers are most comfortable with. There's also potential situations on the field where we might want to switch to tank for a maneuver with the push or click of a button. The problem is, I really have no idea how to translate this into code. Some of the stuff is obvious, such as using a SendableChooser, but the rest is questionable. I have a few ideas, but no way to test them since our cRIO died and we're awaiting a replacement.

We're using command-based, fyi.

To the teams that have done this before: how did you do it?
And to people who haven't: what do you feel is the best way to accomplish this?
__________________
Research is what I’m doing when I don’t know what I’m doing.
- Wernher von Braun
Attending: Raleigh NC Regional