Real-Time Measurement and Control

cancel
Showing results for 
Search instead for 
Did you mean: 

cRIO 9057 Corrupted

Hello everyone,

we have several cRIO-9057 controllers installed on the same subnet.
All of them are reachable and work correctly except one.

A few days ago I noticed that this unit had stopped generating RT and FPGA logs, and after checking from NI-MAX I realized that it now fails any software installation, format, or image deploy operation from NI-MAX or RAD Utility.

The process always stops with messages like:

“Error -2147220304 at nisyscfg.lvlib:Restart.vi”

or

“Installation failed while transferring files to remote host. Either the disk on the remote host has become damaged or your software installation is corrupt.”

I can still:

  • Ping and connect to the target from NI-MAX

  • Access files via FTP and the embedded Web interface

Other identical cRIOs on the same network (with the same software stack and configuration) work fine.
The ni-rt.ini file looks normal and almost identical to the working units.

Unfortunately, the device is installed on a plant over 1200 km away, so I can’t switch to safe mode manually or use a recovery USB on site right now.
I would like to try anything that could help recover the RT startup or remount the filesystem remotely, if possible.

Any suggestion for remote diagnostics or possible fixes would be greatly appreciated.

Thanks

0 Kudos
Message 1 of 4
(92 Views)

Bumping Thread

0 Kudos
Message 2 of 4
(65 Views)

I would be inclined to try to get somebody local just to go and have a look at - LEDs, and see if there is anything obvious physical - perhaps they could do the safe mode switch or remove IO modules just in case, or physical power cycle. I presume it worked ok before this, so question would be what could have changed - something with networking ?

Consultant Control Engineer
www-isc-ltd.com
0 Kudos
Message 3 of 4
(59 Views)

Hello Scrizzo88,

To answer your question, it is possible that some local or network firewalls are blocking communication. The first appropriate step to take would be to try the cRIO with another host PC or using an ethernet cable, if possible, to verify if the issue is related to the PC or the device itself.

If this does not help you can try to:

  • Manually install the NI Linux RT Image and feeds from NI MAX: Remote Devices >> cRIO Target>> Software >> Right click >> Add/Remove Software. 
  • If other targets do normally use the same PC and network, it might be specific units that have some OS level corruption. Try restoring factory settings: Restore NI Linux RT Target to Factory Default Configuration

Have a good day,
Hugo

0 Kudos
Message 4 of 4
(33 Views)