|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
Is the cRIO dead?
Our team's cRIO II has just recently stopped working, and has gone into Safe Mode. I am unable to see it on the network, along with it not being detected in the cRIO imaging tool. This exact problem occurred last year, and I remember doing something with the reset button, but that's all I can recall. I have tried a normal network cable along with a crossover cable, both with no luck. What is wrong with the cRIO, and how can I recover from this issue?
|
|
#2
|
|||
|
|||
|
Re: Is the cRIO dead?
UPDATE - After about an hour of cajoling the cRIO, I was able to get it to show up in NI MAX and do a format (the firmware had gone corrupt), but now I cannot get the cRIO imaging tool to image it. Something about an invalid path (I don't have the error with me, but there was a question mark somewhere in it when it said invalid path) - Is there a way to reimage it with NI MAX? MAX works fine, the FRC imager does not. Also, the imager does not report that any modules are installed, while they are. What would cause this? Has the cRIO gone bad?
|
|
#3
|
|||
|
|||
|
Re: Is the cRIO dead?
The imager doesn't actually see the modules, it is the existing image that publishes that info. Until the cRIO has a relatively modern image, it won't report the modules.
Does the image tool ever see the cRIO? Does it start imaging and them fail part-way in? Greg McKaskle |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|