View Single Post
  #27   Spotlight this post!  
Unread 14-03-2016, 00:03
GreyingJay GreyingJay is online now
Robonut
AKA: Mr. Lam
FRC #2706 (Merge Robotics)
Team Role: Mentor
 
Join Date: Mar 2015
Rookie Year: 2015
Location: Ottawa, Canada
Posts: 766
GreyingJay has a reputation beyond reputeGreyingJay has a reputation beyond reputeGreyingJay has a reputation beyond reputeGreyingJay has a reputation beyond reputeGreyingJay has a reputation beyond reputeGreyingJay has a reputation beyond reputeGreyingJay has a reputation beyond reputeGreyingJay has a reputation beyond reputeGreyingJay has a reputation beyond reputeGreyingJay has a reputation beyond reputeGreyingJay has a reputation beyond repute
Re: Banging the driver station

Quote:
Originally Posted by Abrakadabra View Post
Thank you for the detailed explanation. I feel your pain on the flaky Dashboard readings. We too were struck with this bug in Week One - several times the autonomous just didn't run at all, even though the drivers swore it was selected on the SmartDashboard. It seems there may be a timing issue, whereby you have to wait until your DS is connected to the field before you make any Dashboard selections. We're just hoping it gets figured out before our next event in Week Five.
My team opted for a hardware solution as we have heard a few horror stories like this before.

We installed this on our robot:

http://www.robotshop.com/en/rotary-e...module-v1.html

Using the analog input we can read 12 discrete positions which we are using to select our auto mode. There's no way to specify parameters as in a Dashboard solution but so far we have managed without. We could always install more switches
Reply With Quote