CRIO ghosting

[Greg McKaskle]

I'd like to focus on the robot enabled when you didn't intend it to be first.

If there is a way for this to happen, please try to give me steps. The DS shouldn't enable without a robot attached. The robot is told its state. I do not know of a way for it to coerce the DS to enable. The field can cause the DS to enable, but your DS must be connected to the field for that to happen. There are odd corner cases such as when you are developing on a cRIO and start new code while running existing code. As far as I've seen, when new code on the robot takes over from old code, the FRC Communication task tells the DS and the new program is disabled even if the old one.

Are you sure that someone didn't enable the robot from the DS? F1 is the shortcut to enable the robot, by the way. Enter key is the shortcut to disable, and space is the shortcut to Estop.

As for the other symptoms. If you attach code, I can give it a look and see if anything jumps out.

Greg McKaskle