Forcing autonomous to run
 

When I was trying to test some autonomous code on our old robot, to make a very long story short, I learned that you must have a competition port switch/dongle (or short it out with a paperclip; be sure to understand the pinout first; thank you Intellitek support!).

Anyway, I've got it working now through shorting, but I was pulling my hair out over it when I first started testing. I used a tether cable and changed the team number to 0000 and autonomous would run fine, the terminal window would show it running, but the motors would not turn (they worked fine in operator control, and in auton after I shorted the competition port - not a code problem). I'm curious if this is some sort of safety thing, or its not supported anymore with the robot controller, easyc, or what. I've noticed with the vex system that if the remote isn't on you can't drive the motors so I thought there might be something similar on the FRC now.

Re: Forcing autonomous to run
 

Were the OI and RC still connected when the team was set to 0000? I don't think this feature is used very often I know we never tested for it.

Re: Forcing autonomous to run
 

I followed the 2005/06 (Couldn't find a 2007 version; I'm using this on an 06 controller anyway) RC Reference Guide. It describes the following:
As I described above, it did seem to work, outputting print statements as it was supposed to, although unable to actually run motors.