[Bot190]

Something that doesn't seem to be understood by many so far is the differences between disabling and e-stopping the robot.

Disable - Stops the execution of code for now
E-Stop - Changes robot state to disabled and sets something in the cRIO that prevents it from being enabled again.

Under normal (non-competition usage) there is no reason for the functionality of the e-stop button. Unless it does something I'm unaware of, it disables the robot in the same way as the disable button. Disabling the robot until a power cycle serves little purpose other than to slow development down considerably.

I seem to remember a time where the space button disabled the robot and the enter button e-stopped the robot. This only changed last year, causing a fair amount of confusion among team members.
If both buttons are actually necessary, a way to either switch the mapping or select your own mapping would be extremely helpful.