I think “Dave” might be right, the Rc has to have a radio or tether downlink before it will initalize, even in autonomous mode. Therefore the OI must be powered during the autonomous control segment. It would then only make sense that the reset button would work during the autonomous segment.
However, I wonder wether or not scratch pad ram is erased during a RC hot reset? If its not you could potentially create a secondary “safe” AI program that will load when a “dirty” byte is in a given scratch pad slot, that way if your primary AI routine fails for whatever reason, you could set the robot to automatically use a “safe” default type routine.
I might be of on the reset button and scratchpad, but it might be worth a shot.
Keep in mind the “intent” of the rules. In my opinion this is cheating. FIRST isn’t a law firm and even if they were, loop holes would exist. I think we should all go with what FIRST intended this restriction to mean.
How are we supposed to know that they didn’t knowingly left a loophole to promote creativity in attacking the problem? I think that we should ask FIRST directly if using the RC Reset, or the other reset button (E-Stop? P-Stop?) to cycle through programs is legal.
*Originally posted by cybermind *
**How are we supposed to know that they didn’t knowingly left a loophole to promote creativity in attacking the problem? I think that we should ask FIRST directly if using the RC Reset, or the other reset button (E-Stop? P-Stop?) to cycle through programs is legal. **
I’ve already considered this and brought it to FIRST’s attention. I am still waiting for a response.