Quote:
Originally Posted by JacobD
Before you try something like this, you might want to be careful because FIRST might give you problems when they see that. They have the enable/disable functionality for safety reasons. I understand that you might want to enable/disable from a wireless remote, but consider safety first.
|
Quote:
Originally Posted by matthewdenny
Anything that interferes with the fields ability to disable a robot would be a bin no no.
|
This wouldn't interfere with the enabling and disabling of the FMS. The robot still has to be connected to and initially enabled from a driver station, and it still can be disabled (it can
always be disabled if everything is working as it should, FIRST makes sure of this). Enabling starts the user code on the cRIO, and surrounding your code with this if/else doesn't let your actual code start once the bot is enabled from the DS until your Boolean is flipped. It interferes with the FMS's ability to get your robot to move, but so would putting a robot on the code without any code or just not touching your controls, which is legal. You'd have to go
deep into WPILib to let your bot actually do stuff while it was disabled by the DS, and I'm not even sure if it's possible at all with FIRST's firmware.
And plus, OP said this was for a demo bot, so while safety is definitely
more of a concern than at competition,
if safety is preserved FIRST legality is close to irrelevant.