Giving up on command CMD_RUN_OP_MODE(10413) after 11 attempts

[sgeffner22]

We have a robot that takes many seconds (~5) before it has completed its initialization. We have found that, if we push INIT, and then push Start before our initialization has completed, then we will see the following error on the driver station:

Giving up on command CMD_RUN_OP_MODE(10413) after 11 attempts

This message shows in a popup message that remains on the screen, even after the driver app is killed. (We don't know how to make it go away short of rebooting the DS phone.)

Once we've seen this message, the driver station and/or robot controller get into some kind of bad state in which subsequent attempts to start an opmode result in the robot controller executing a "restart robot"; as far as I can tell, no additional opmodes can be run successfully. I believe we've been able to get out of that state by killing both apps, though we might have needed to reboot the robot and/or DS phone. (In any case, we have needed to reboot the DS phone to make the error message disappear.)

For now, we're training our drivers not to be in such a rush to press Start ;)

[sgeffner22]

One note: we saw this message again with a different error code (that I didn't catch). In this case the message faded off the screen after about 10 seconds. It occurred when we pushed INIT, but then tried to switch opmodes before the first opmode was completed initializing.