[alex42]

New information: it seems it is a communications problem. Yesterday the problem returned, and we have now reimaged the cRIO twice without fixing it. However, the code disappears much less when we are connecting directly to the cRIO than when we use wireless. It's a really weird connection problem, though, since the DS swears the connection to the cRIO is solid at all times. So it's apparently a connection problem such that the connection is never actually lost, and it's exacerbated by but not caused by connecting wirelessly rather than directly.