Go to Post Screwing up is part of the game. Iterating, testing, and analyzing your failures separates the great from the average. - Jon Stratis [more]
Home
Go Back   Chief Delphi > Technical > Technical Discussion
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
 
 
Thread Tools Rating: Thread Rating: 3 votes, 5.00 average. Display Modes
Prev Previous Post   Next Post Next
  #9   Spotlight this post!  
Unread 02-05-2015, 00:40
Abhishek R Abhishek R is offline
Registered User
FRC #0624
Team Role: Alumni
 
Join Date: Mar 2013
Rookie Year: 2012
Location: Texas
Posts: 892
Abhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond repute
Re: Custom Driver Stations

We use two of the Logitech Gamepads. The buttons make it great to assign functions to, and are very easy to pick up. It also gives you some freedom of movement behind the glass.

While I agree, one driver is better than two because there is no lapse in communication, for some of our robots it's just not feasible. In 2012 and 2014, almost everything was done by the driver due to the automation of the robot in picking up and firing the balls, but because in 2013 we had to adjust angles, shooter speeds, and in 2015 the elevator and intake system made things too complex for the driver to handle (our manipulator had multiple sets of buttons - we basically had a shift key on the copilot gamepad).

Automation has been one of our team's strengths due to the hard work of our programmers, and that really lightens up a lot of the minute things the driver has to worry about.

I will say, the best way to assign robot functions to the drivers is like this, in my opinion: first, put all the robot drivetrain functions on the driver's side, and everything else on the copilot's side. Then, start moving robot functions from the manipulator to the driver until it impacts the driver's ability to maneuver the robot. For example, if you are using a gamepad, the first function assigned to the driver is the drivetrain to the two joysticks. Then, let's say you want the driver to be able to shoot, so you put that on a trigger. Then say you want the driver to be able to drop the intake to pick up a ball as well, but for whatever reason you are out of triggers, so you have to put it on one of the buttons. Since the driver will have to move their thumb off the drive stick to press the button, that function should be left with the copilot/manipulator.

We experiment with driver stations and setups all the time (this year we had a dual monitor setup!), so feel free to ask us any questions you may have.
__________________
2012 - 2015 : 624 CRyptonite
Team Website
 


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 04:30.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi