[stephmak]

Thanks for your suggestions guys,

@Joe Ross: We will try not cancelling the deploy when we are ready for a another test in a few minutes (mech and electrical have the 'bot right now).

@VARobot: Yes, we do have a second cRIO, but because it is a cRIO from LogoMotion, and thus much bigger, we do not have the space for it on a more permanant basis. If it is a fatal cRIO problem, considering our state scrimmage is in a few days and bag-and-tag in a week, we are in a pretty bad spot. Is there any way it is not a fatal cRIO issue? I have seen the exact error codes I listed in several other threads, and have seen possible solutions there. I do not mean to disrespect or dismiss your help, in fact I am very grateful for it. I just want to avoid having to buy another cRIO if at all possible.
Can anybody else weigh in here?