cRIO 9035 suddenly stopped scanning I/O

[hman750]

Our cRIO 9035 was running fine when it suddenly stopped scanning the I/O yesterday, after which the program just pops up error messages (...timeout, cannot [read input#/write output#]) one after another, going through the entire I/O in it sequence.

Any idea what may have happened, here? It was running fine when this suddenly happened. It was not being programmed, but was running so as to monitor the input values from its 0-20mA input module.

[VA.KI]

Hello hman750,

What do you mean by "stopped scanning the I/O"?

Are the LEDs on the controller blinking with some sequence?

[hman750]

It simply quit reading the inputs for some reason. It wasn't reading or writing digital I/O, either, nor the analog outputs. The CPU was still running and talking with the LabView console program on the laptop, but it refused to do any I/O read/write at all. 

We shut the system off for 2 days after that. Upon repowering on Monday, it worked again. It continued working for another month after that.

My advice: do NOT use cRIO for mission-critical applications. It is neither reliable, nor consistent in its execution.

[VA.KI]

Actually cRIOs are not for that and doesn't have certifications.

If MTBF info is critical for customer they contact to support, and only few C series modules have "mission-critical" licenses.