Bizarre cRIO Server Errors (FDIO)

[JamesTerm]

Originally Posted by compwiztobe

We applied this patch, and rebuilt and redeployed our code. It appeared to improve the problem at first in that it gave the same FDIO errors as we saw previously, about as frequently as we had been getting the timeout errors, and we did not appear to be hanging.

Try this one https://www.dropbox.com/s/dbpv32qii7...sDustinFix.zip
I've spent quite a bit of time testing this, and it's an interesting twist of fate that both Dustin and My patch compliment each other for best results during booting of cRIO. For one client stress it works perfectly... for a 3 client stress it did show one error but recovers just fine. This patch divides a new critical section to restrict the main robot's get/put calls to a localized scope that was easier to manage... basically I wanted to minimize the work to just put the variables and get out without interference with I/O critical section operations. There is also a sleepless thread fix in there as well. This is still unofficial, but I think it is good enough to at least get some testing.