"Robots don't quit!"

[Xanawatt]

I did not start this thread because we have a current problem; however, this error has popped up several times over the course of the season and we were always able to find what was causing it. What happens, for those unfamiliar with the error is that the robot code appears to deploy correctly, but when you start up driverstation, there is either no code, or there is code. When there appears to be code, starting teleop causes the code to crash and "Robots don't quit!" is printed to the driverstation error log. The code then turns green again and the same thing happens. We have determined that the cause of this error is that two or more objects are assigned to the same port on the roboRIO. From research, I have found that there are more reasons that this could be thrown. Can someone please explain exactly what "Robots don't quit!" means? Also, is the first scenario that I described part of this too or is that a completely different error?

[Mark McLeod]

I think "Robots don't quit" is just related to when the user code gets far enough to complete initialization, but then later crashes.
The roboRIO automatically restarts crashed user code, so a persistent code error will cause the user code to keep restarting over and over again.

[TimTheGreat]

Originally Posted by Mark McLeod

I think "Robots don't quit" is just related to when the user code gets far enough to complete initialization, but then later crashes.
The roboRIO automatically restarts crashed user code, so a persistent code error will cause the user code to keep restarting over and over again.

From what I understand, a better message for the error would be "Robots shouldn't quit." It means the robot has stopped running, and basically the program has concluded. "Robots don't quit" means your code has stopped, but real "robots don't quit." They should keep running.

[Mark McLeod]

The "Robots Don't Quit" message might only be issued when the code has successfully completed restarting and it notices that it has been restarted.
That would make it accurate.
Or maybe "I get knocked down, but I get up again, cause nothin's going to keep me down."
Repeat as required...

[Dan Waxman]

Most of the time this is just because your code through an exception -- there can be a number of reasons why this happened, and I can't comment on that without seeing your code, but that's usually the cause of the message.