Autonomous logistics
 

In previous years' games that I've been familiar with (back to 2008) it has generally been the case that each team's autonomous program generally didn't interfere with another team's autonomous program (Lunacy did somewhat, by design)

This year, however, is significantly different. Shoot baskets, tipping coop or alliance bridges are the obvious things to do of course, but all the teams on your alliance are (potentially) trying to make use of the same resources (baskets, bridges) at the same time. Of course, one of those teams can use Kinect to help avoid collisions via human input, but what about the other two teams? I've not heard much discussion here about other strategies surrounding this issue.

Re: Autonomous logistics
 

We're going with the path we always do... program in several options, and set which one to use with configurable switches after talking with our alliance partners.

Re: Autonomous logistics
 

Is it possible/legal to have autonomous selection switches be on the driver station, or is it not possible to have the autonomous logic sense driver station switches, hence forces such switches to be on the robot itself ?

Re: Autonomous logistics
 

It is perfectly legal to use the cypress board for driver station I/O. We have done that in the past with great succsess. Program your code to give you several autonomous options and then select which one you want to run via a selector switch. We use a 6-position rotary switch to give us up to 6 choices.

Re: Autonomous logistics
 

If you mean to select an autonomous mode on your driver station after you establish comms but before the match starts, then yes

Re: Autonomous logistics
 

I would suggest using the driver station digital I/O due to it can't be bumped, i'd do physical if you run out of space. Also the digital is included and thus cheaper.