Thanks for the info; we'll play with that tomorrow afternoon (our solution was to install on a whole different driver station, that got us nice and clean <grin>).
We haven't tested bob's theory yet, but I just noticed something odd. In reviewing our code on bitbucket, I saw that the 'I' in our variable string was apparently a Unicode character of an I with double umlauts. It appears that perhaps a student accidentally got WindRiver to inject an unusual character into the string we were setting as a boolean.
So that may be another source of the crash we were seeing.
Just to improve future google searches, when we see these crashes, we get an exception message Error on FDIO read, and then hard to read error messages. Which is explained well here:
http://www.chiefdelphi.com/forums/sh...d.php?t=113071
Our behavior from there is not clear; it seems as though sometimes we lose all robot function, and sometimes the robot continues to work.
Does anyone have a sense of whether or not adding a try/catch block around network puts would help avoid a robot shut down?
Cheers,
Jeremy